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

aclocal, autoconf, autoheader and automake
by Raymond Toy 22 May '19

22 May '19

Can we get aclocal and the other tools above installed? I'm updating cmucl's site to use the latest dev version of texinfo (6.6dev) to get better support for multi-level indices. So I'm building 6.6dev locally in gitlab CI and therefore need all the autotools to build it. I guess the alternative is to make 6.6dev available somewhere on c-l.net, but that's a bit of a burden to have available on c-l.net. Hence, I"m building it myself for CI. -- Ray

2 4

(no subject)
by Dave Cooper 10 May '19

10 May '19

Hi, I just changed phones and installed Google Authenticator on the new phone, and migrated my Google code to the new authenticator. But my common-lisp.net code (and some other ones e.g. Cloudflare) are still on the old phone. But the common-lisp.net one (on the old phone) doesn't seem to work anymore. Is there a way to migrate this to a new phone without logging in (I doubt it). If not, can the admin temporarily disable my 2FA so I can get in and set it up on the new phone? -- My Best, Dave Cooper, david.cooper(a)gen.works genworks.com, gendl.org +1 248-330-2979

4 6

gitlab pages artifacts expiration?
by Raymond Toy 06 Apr '19

06 Apr '19

In, for example, https://gitlab.common-lisp.net/cmucl/cmucl-site/-/jobs/1316, there's a note on the right that the job artifacts expire in 3 mo. There's also three buttons for keep, download, and browse. So, if I run CI for the latest changes and don't touch the site again for 3 mo, all the generated pages will disappear? That would be bad if the webpages disappeared after 3 mo. It would also be annoying if I had to make changes at least once every 3 mo to keep the site up. How does this work? Googling for this didn't actually answer this question, except to say I can set expiry_in to some large value to preserve the artifacts. -- Ray

3 3

deploy failure
by Raymond Toy 08 Feb '19

08 Feb '19

I updated cmucl-site for the first time in a while, and I can't seem to deploy any more. Generating the pages works, but I get a permissions error now: https://gitlab.common-lisp.net/cmucl/cmucl-site/pipelines/762 Can someone take a look? -- Ray

3 3

gitlab account locked
by Anton Vodonosov 05 Feb '19

05 Feb '19

Hello, I'm trying to submit a ticket to CMUCL. Logging in with both GitHub and Google shows "Your account has been blocked. Please contact your GitLab administrator if you think this is an error." Trying to register by email - it says "you're already registered". Trying to reset password - no email is sent to my email. Probably that "locked" notification is related to two factor auth, but how can I setup the two factor auth if I can't login? Best regards, - Anton

3 3

Rsync not working for /cmucl/cmucl-site/public
by Raymond Toy 29 Jan '19

29 Jan '19

I noticed that www.cmucl.org wasn't updating the web pages from c-l.net. And rsync seems not to be working anymore: rsync -av rsync://common-lisp.net/pages/cmucl/cmucl-site/public/ cmucl/pages receiving incremental file list rsync: change_dir "/cmucl/cmucl-site/public" (in pages) failed: Permission denied (13) sent 8 bytes received 108 bytes 46.40 bytes/sec total size is 0 speedup is 0.00 rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1721) [Receiver=3.1.2] This used to work when I updated my back scripts a couple of weeks ago. -- Ray

2 3

Getting TeX
by Raymond Toy 26 Dec '18

26 Dec '18

Happy Holidays! I've been doing some hacking on cmucl-site and want to create a pdf file from a texinfo doc, using gitlab pages support. It appears that the TeX isn't available on the pages runner. Can we get that installed? There's no rush on this, but it would be nice to have.

1 0

How to deploy your project pages through GitLab
by Erik Huelsmann 19 Dec '18

19 Dec '18

Hi, As per my prior mail, I'm sending instructions as to how to start using GitLab to deploy your project pages (i.e. how to deploy what you would normally copy to /project/*/public_html using GitLab automation). First, the delpoyment through GitLab uses GitLab Pages which means that everything you can find about GitLab Pages based deployment of webpages (e.g. in the documentation: https://docs.gitlab.com/ee/user/project/pages/#how-it-works) applies here as well -- except for the URL on which your site will be published. Another important note is that if the directory /project/<your-project>/public_html exists, your pages will be served from that. If it doesn't, your project pages will be served from GitLab Pages, if that doesn't exist, your project pages are redirected to GitLab itself. This means that you can experiment with GitLab pages based deployment by moving your public_html directory out of the way. If your tests fail, simply move it back into place and your existing pages will be restored. *What do you need to do to use GitLab deployment?* 1. Create a GitLab repository called <project>-site in the group <project> 2. Add the content to be deployed to the repository (either static or to be built) 3. Add a '.gitlab-ci.yml' file to the repository 4. Rename the /project/<project>/public_html directory For the simplest of deployments (taking what's in the repository "as-is") see the cl-couch pages deployment repository and .gitlab-ci.yml at https://gitlab.common-lisp.net/cl-couch/cl-couch-site/. For an intermediary level deployment processing Markdown to HTML and wrapping the result in a template, see the common-lisp.net homepage generator (which we'd like to abstract into a generic tool; we can use a hand there!) at https://gitlab.common-lisp.net/clo/cl-site/. For the most complex we currently have - using Docker - see the Quickref build at https://gitlab.common-lisp.net/quickref/quickref/tree/continuous-integration ; note that this is currently on its "continuous-integration" branch. I hope it'll be adopted soon to be on the master branch. I'll add similar instructions to the c-l.net FAQ. Please feel free to follow-up with any questions you might have when you start playing around with this new feature. Regards, Erik.

2 13

Strange things happening on gitlab?
by Raymond Toy 18 Dec '18

18 Dec '18

A while ago, I noted that all commit messages are now from gitlab(a)common-lisp.net. This didn't use to happen. Commit messages used to be sent with my personal email (this one). But I also noticed just now that <project>->Settings->Integrations->Project Services->Emails-on-push->Send from committer is set to true (for cmucl). Not sure what is supposed to happen if that is not set.... Also, in https://gitlab.common-lisp.net/f2cl/f2cl/issues, the four issues each say they were created by me 3 weeks ago. I know I didn't create any f2cl issues in over a month. I think those issues are very old, possibly years. -- Ray

1 0

Re: Gitlab spam has started
by Erik Huelsmann 10 Dec '18

10 Dec '18

Hi Vladimir, On Mon, Dec 10, 2018 at 3:23 AM Vladimir Sedach <vas(a)oneofus.la> wrote: > Hello, > > Looks like two-factor authentication is not deterring the spammers: > Well, I did kind of expect that *some* spam would come through. However, what I noticed based on your signal is that I am not getting a notification about newly created projects and that it's therefor hard to monitor activity on our instance. > > > https://gitlab.common-lisp.net/Credent/icq-723073191-we-update-daily-sell-c… > > https://gitlab.common-lisp.net/Credent/icq-723073191-we-updates-daily-sell-… > > Removing the user *and* these repositories was extremely easy: one click of a button by an administrator (which includes me). > Is there some kind of moderation queue we can set up for new > projects? We can set the number of projects people can create to 0 (zero). That means that everybody who creates an account without further verification will not be able to create a repository of their own. However, that may then result in spam tickets or spam snippets being created ... > I can help moderate. > Thanks! The first step would be to identify how we can be notified of any new repositories which are being created or how we can identify users who would like to have the ability to create a new repository. We can work from there to see about the queue. I don't think there is one built-in with GitLab at the moment... > > Thank you, > Vladimir > > Regards, -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0