- clo-devel - mailman3.common-lisp.net

Cannot log in as vsedach@common-lisp.net after added SSH key to Gitlab
by Vladimir Sedach 15 Jul '17

15 Jul '17

Hello, I ran into a strange problem: I added a new ed25519 key to authorized_keys2, which worked fine. Then I went to Gitlab web interface and tried adding the ed25519 key, which failed because Gitlab cannot handle ed25519 keys yet. I made a new RSA key and added that in the Gitlab web interface. After this I cannot log into vsedach(a)common-lisp.net with any of the keys that were in authorized_keys2. The error message is "Permission denied (publickey)" so something must have happened to the authorized_keys file. This seems very strange. I do not think I did anything as vsedach(a)common-lisp.net that would break log-ins, which leads me to believe that it was some script in Gitlab. OTOH the new RSA key does not work either, so it might be something I did through TRAMP by accident. Can you please put this SSH key into authorized_keys: ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIDc+4x1XblOzyfHAzOCbM00FB/VglYg0PvOSL8FuQKQ/ vas(a)t43.lan. Thank you, Vladimir

3 3

common-lisp.net maintenance: ugraded - what's new?
by Erik Huelsmann 15 Jul '17

15 Jul '17

With respect to the regular services, GitLab was already receiving at least one upgrade per month and security upgrades were being installed as they were released by Debian (automatically). With the upgrade, the system is running a recent version of the Debian distribution again (Stretch). Stretch comes with Apache and Nginx versions which support HTTP/2 out of the box and as we were running common-lisp.net on TLS for a long time already, HTTP/2 is now turned on for all common-lisp.net subdomains. Mail transmission has been configured to use the official common-lisp.net certificate. The new distribution comes with a kernel which is recent enough for container support. Among the next steps, we'll research moving to Mailman3, which comes - as an option - in Docker containers and a much more modern web front-end as well as internal architecture. For those who like to know about the migration strategy for the upgrade: over the past weeks we created a copy of the VM running common-lisp.net and other services. On that copy, we ran a script for an automated upgrade. When the upgrade didn't succeed or didn't complete automatically (that is, required manual intervention), we changed the server configuration and the script. This process went on until the upgrade completed successfully and without intervention. Once successful, the configuration was tested and adjusted for the target software versions. The adjusted configuration was automatically installed after the upgrade process today, followed by a reboot to return service. The migration interval of 3 hours was based on the experience gained from this exercise. In the mean time, a separate VM was installed on the IP pointed to by common-lisp.net, ensuring that even if services would temporarily be up during the migration, no users could accidentally access those services. Thank you for your attention! Regards, -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

Heads up: common-lisp.net unavailable tomorrow morning (CET)
by Erik Huelsmann 15 Jul '17

15 Jul '17

Due to major maintenance, common-lisp.net will be unavailable tomorrow between 9 and 12am CET on Saturday July 15. Regards, Erik

1 1

Migrating common-lisp.net to Debian Stretch
by Erik Huelsmann 09 Jul '17

09 Jul '17

Hi all, Over the past weeks, I've been working on a migration from our current OS version to the current stable version as recently released by the Debian project (Stretch). While the time hadn't come to migrate earlier, today I found that the GitLab project released its Stretch packages, meaning that now all the third-party prerequisites are in place to migrate. Today I worked to automate the migration and by the end of today, I'm now able to run an automated migration without manual intervention. I'll leave a copy of the current machine running for a few days to see if it remains stable. If all goes well, it's my intent to take common-lisp.net offline for a few hours coming Saturday (Saturday July 15) in order to run the migration script on the live system instead of on a backup. Before the upgrade starts, we'll take a snapshot of the drives and make sure users won't have access to the system during the migration. Although I've run through various tests already and will continue to do more testing over the coming week, the system might have some instabilities in the days after the migration. When you experience any of those, please report here or to the admins (admin@common dash lisp dot net). Thank you for your patience and continued support/use! Regards, -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

Working on system upgrade
by Erik Huelsmann 20 Jun '17

20 Jun '17

Hi, It's nearly time for Debian Stretch to be released. When that happens (and GitLab releases packages for it), we want to upgrade the system quickly afterwards. In preparation, I'm working on trial runs for the base OS upgrade. As a consequence, performance may be degraded. To facilitate the upgrade (make it more quick), I reviewed all packages installed on the system with the purpose of removing unused ones. I've removed quite a few packages indeed (from the current production system, that is): all packages related to the X11 (server) have been removed. So have most LaTeX and LuaTeX packages. The idea behind this step is that the access provided by Common-Lisp.net is merely provided to support uploading and maintaining the static html pages -- my assumption is that that has little relationship to being able to start a desktop environment or graphics environment. If you miss packages that you depend on, don't hesitate to speak up. Please explain what you need them for and I'll make them available again. While going over the upgrade process, I'm doing the so-many-th round of configuration cleanup: due to the fact that the host has been managed by multiple people at various times in the past, each with their own approaches to managing the configuration, the configuration can be much more standardized. On each round of maintenance, that's exactly what I've been doing. Configuration is more-and-more getting in line with "how Debian intends it". Let me use this e-mail as an opportunity to ask current and future (co)maintainers to stick to it; it's often a learning curve, but saves a lot of effort on upgrades later on. There will be a pre-notification and some (planned) downtime for the system when the final cut-over arrives. For those interested in how the migration strategy and dress rehearsals work, I'm going over these steps (wash, rinse, repeat -- in other words: over and over until it works): 1. Create LVM writeable snapshots of the VM's volumes 2. Create a new VM on top of these snapshots 3. Start up the new VM with different IP and hostname settings (patched Apache config too) 4. Change the (git-versioned) /etc directory to the new target distribution version branch 5. Run dist-upgrade (and a number of additional steps) 6. Fix the configuration issues found in the resulting installation and commit (to another server) 7. Ditch the copy-VM and go back to (1) This procedure, although it's taking quite a bit of time to run the dist-upgrade, is turning out pretty effective in producing a reproducible upgrade procedure which can be repeated consistently once the production server needs to be upgraded. -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

3 4

Unable to push to f2cl or merge requests
by Raymond Toy 21 May '17

21 May '17

I used to be able to push commits to the master branch all the time. But in the last month or two something has changed and when I try to push a change to master, I get the message: remote: GitLab: You are not allowed to push code to protected branches on this project. To common-lisp.net:f2cl/f2cl.git ! [remote rejected] master -> master (pre-receive hook declined) I see that master is a protected branch. (I don't remember changing that or if it was always protected.) So I created a merge request <https://gitlab.common-lisp.net/f2cl/f2cl/merge_requests/3> <https://gitlab.common-lisp.net/f2cl/f2cl/merge_requests/3> Now it says I have to go find someone with write access to merge the request. Oddly, just a month ago, I successfully merged the requests https://gitlab.common-lisp.net/f2cl/f2cl/merge_requests/2 and https://gitlab.common-lisp.net/f2cl/f2cl/merge_requests/1. As the owner, I would think I have enough rights both to push to the protected branch and to merge my own merge requests. Any ideas? <https://gitlab.common-lisp.net/f2cl/f2cl/merge_requests/3> -- Ray

4 10

Time to consolidate static project pages into GitLab?
by Erik Huelsmann 21 May '17

21 May '17

Hi all, Since the inception of Common-Lisp.net, we have offered projects the option to log in on the host through ssh connections to manage their hosted project pages (https://common-lisp.net/project/*) As off December 2016, GitLab - the software we use to provide the majority of the repositories on the site - includes a hosting offer for static pages: https://about.gitlab.com/2016/12/24/were-bringing-gitlab-pages-to-community… I've not studied the functionality in depth, but I'm wondering: would the time have come to start moving the project pages into GitLab by using this offering and start moving away from having OS-based accounts? Would people mind or even like to move to this functionality? Regards, -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

6 12

Maintenance of closure-html
by Erik Huelsmann 03 May '17

03 May '17

Hi David, You are listed as the current maintainer of closure-html. We (the common-lisp.net admins) have been approached by Elias Martenson who wants to take over maintenance. He could not reach you (received no response?), so I'm trying to reach out and see if you are ready to share or hand over maintenance. Please let us know what we can do. Thanks in advance! Regards, Erik Common-Lisp.net maintenance

1 0

cmucl-cvs list not working
by Raymond Toy 08 Apr '17

08 Apr '17

The cmucl-cvs mailing list (misnamed since it's really the git commit list) no longer seems to be working. I did do one minor tweak to modify a user who should have been getting commit messages, but wasn't. Not sure if that was coincidental or not, but I'm no longer getting any commit messages at all. Can someone help me with that? Thanks, Ray

2 3

Volunteer
by ramxt44 . 05 Apr '17

05 Apr '17

Good Evening Lisp Folks. I am willing to help out with somethings. i know that you requested help with the trac page. I know html and css. if you think i may be able to help you ,please let me know.

1 0