clo-devel

clo-devel@common-lisp.net

2 participants
609 discussions

[clo-devel] The clo project on common-lisp.net.
by Erik Enge 10 Oct '06

10 Oct '06

Ok, one more thing. The "clo" project on common-lisp.net is the project to manage the site itself. Originally it was common-lisp.org, so that's where we get the c-l-o from. Now its CVS tree hosts the webpages you see when you visit http://common-lisp.net/ and its trac instance has our TODO list: http://trac.common-lisp.net/clo So there are some people subscribed to clo-devel that care about how we admin the box so I usually CC this list whenever I discuss these matters. Thanks, Erik.

1 0

[clo-devel] Perennial admin issue with cvs pserver on common-lisp.net
by Erik Enge 10 Oct '06

10 Oct '06

I wanted to share this with you and make it available on the mailinglist because it took me a few minutes to figure out and it's a stupid issue so I don't want you to waste any time on it. The cvs pserver passes all repositories that it wants to serve, on the command line. Thus, how many repositories you can serve is limited by how many characters you can pass on the command line. This is really silly because there's already a config file where it can read this from (/etc/cvsd/cvsd.conf). I haven't found a way around it. So, every now and then, someone will complain that pserver checkouts (anonymous cvs access) doesn't work. Usually there will be some "pam_auth token not released" error of some sort. What I do then is that I edit the /etc/cvsd/cvsd.conf file and remove all projects who are using svn, darcs or arch (I check the project page, they usually announce this) until cvs pserver works again. Then it works until I have added enough projects to make it break again at which point I go back and revise which of the new projects aren't using CVS. I don't have a longterm fix for that one yet but it's probably something we need to address over the next year. One possible solution is to symlink /project to /p which will drastically shorten the arguments to cvsd on the command line but this would mean that anonymous CVS users would have to specify anonymous@common-lisp.net:/p/project/cvsroot and SSH CVS users would still use :/project/project/cvsroot - that's probably going to confuse the hell out of alot of people. Erik.

1 0

[clo-devel] More information about admining common-lisp.net.
by Erik Enge 10 Oct '06

10 Oct '06

Now that you have the passwords you can start approving any projects that come in. Usually there's one or two a week so don't expect to be busy. ;-) You should subscribe to the admin, clo-devel and system-notification mailinglists if you haven't already. Thanks again, Erik.

1 0

[clo-devel] common-lisp.net admins
by Erik Enge 10 Oct '06

10 Oct '06

Hi guys, thanks for volunteering to help me out. I'm starting a new job this week and it'll be hectic over the next few months. I really like what common-lisp.net provides to the community so I figure instead of risking anything I wanted to reach out and get some help. I will continue to pay for the server from the donated money so you don't have to worry about that part. To give you an idea, here's what's required on a week-to-week basis: - monitor system-notifications@ mailinglist for warnings about diskspace or integrit failures (integrit is similar to tripwire) - run /custom/bin/add-user.sh and /custom/bin/add-project.sh - on occasion run /custom/bin/add-trac.sh - run /custom/bin/update-integrit whenever you change something That's mostly it. To figure out what the server is doing you can start by visiting /etc/crontab and see all processes that are ran every day. Mostly everything just works but there are a good bit of things actually running. People will mail requests to admin@ for a new project. Our job is to make sure they give us all information we need (licence, project name, project members and any GPG keys) and then run the appropriate scripts. I usually go ahead and approve projects as long as the license is open-source although if there's another Common Lisp project out there with the exact name I will want to get in touch with that person first and see what's going on (see the admin list archives for cl-screen, for an example). I'll send you guys an encrypted email with the root password shortly but I will not CC the list for that one. Please feel free to call me on 770-906-7641 if you have any questions and I can't be reached by email. Since we will now be three admins we have introduced a race condition about approving projects. I suggest as a policy the person approving/creating a project replies immediately to that request saying something like "Ok, I'll take care of this" so the other admins know not to try anything. Opinions welcome, of course. Lastly, it's not too late to back out if this is more than you think you signed up for, no hard feelings. Thanks, Erik.

1 0

[clo-devel] Darcs howto
by Charlie Burrows 18 Sep '06

18 Sep '06

Hi, I wanted to download the cl-opengl projects but I don't know how to use darcs. I notice that the FAQ has summaries for cvs and svn but not for darcs. Can anyone fix this/send me a short summary. I'm going to get around to reading the darcs docs but I thought maybe there's be an easy howto out there. Cheers, Charlie

2 2

[clo-devel] Re: cl-net website toasted?
by Erik Enge 06 Sep '06

06 Sep '06

On 9/6/06, Drew Crampsie <drewc(a)tech.coop> wrote: > In trying to back up the filesystem using a snapshot we had to restart > the server, and cl-net's front page seems to have gone to bit-heaven. > > We've seen this before, and IIRC it was an easy fix, but i don't know how :) Seems fine to me. Can you describe the problem? In the future, please do such things outside daylight hours (or as reasonably outside as you can) so we avoid service interruption during the day when people who have donated money to run the site are trying to use it. Thanks, Erik.

1 0

[clo-devel] Sorry for the noise: setting up a svn repository
by Marco Antoniotti 31 Jul '06

31 Jul '06

Hi sorry for the noise, but I need to (finally) set up SVN repository for one of my projects (common-math). Is there anybody who can hand held me on this? thanks Marco PS. I have set up svn repositories on my machine but not with web access etc etc. -- Marco Antoniotti

2 1

[clo-devel] regarding the provision of a PGP key in a project request
by Sean Champ 28 Jul '06

28 Jul '06

Hello, I have been mulling over how I might approach the distribution of some code that I have intended would be publicly avaialble, and the distribution of some project-locatable material that I consider as it being relevant in regards to Common Lisp; though the latter material has not been made in coincidence with software beside it, but I consider that it is likely to be made, as so. While that is not what is the subject of this email, but I mean it as some exposition. I had noticed that the page http://common-lisp.net/project-intro.shtml , in regards to a request for the registration of a project, includes an explanation: That when one would request an allocation of resources for a project at common-lisp.net, one must provide the public complement of a PGP key pair, of which one's own would be the private key. I've yet to have endeavored to have 'gotten' a key onto the Debian keyring. Time ago, there had appeared to be a likely cause as that I would, but it was not firstly pursued by me. Since then, the slime debian package has been taken over by another maintainer, and developed in more. I am not certain of what would be the premise on which I would endeavor to have a key registered onto the Debian keyring, presently. I am aware that there is an object referred to as a keyring, and that a keyring can be utilized in cojunction with crypotgaphic systems, then in conjunction with procedures for message signing, as in the case of GPG-signed email. (I understand, wholly, it is my responsability, if I would endeavor to undrestand how the mechanisms for such are supposed to operate, as when operated across shell commands and such-and-such of conventional software applications. I recognize that it is feasible that the mechanisms for such would be operated, more directly than with shell commands, when operated in a Common Lisp programming environment; perhaps a proposal for such might be more fit to a common-lisp-crypsec list.) While I hope that there will be opportunity to discuss how crypotgraphic systems would be implemented in Common Lisp, but my first question would be: In regards to the public GPG key that would be provided in a request for a project, must that key have been registered in a public keyring? and must the key be marked as to be 'trusted' of anyone? (I realize, those questions might be redundant. If a key was available on a public keyring, and if that keyring would be available as by way of a public key service, then one could send a description of the means by which the key would be accessed of that key service, rather than having to send the key in the mail, and rather than requiring the other to download the key, also via internet email) Separately, then, in a question addressed more directly onto to the operations of a key system: I am wondering if the keyring provided at http://common-lisp.net/keyring.asc would be able to contain key revocation markers. (I am not aware of what is the internal structure of a keyring, but that it would probably contain public keys for people) Should it occur that the integrity of a private key would be violated, such that that key would be the private complement to a public key that would have been registered to the keyring at common-lisp.net, then oneself (and only the person who provided the key) oneself should be able to mark that key as it being invalid. Thirdly, then, most directly: I would like to voice an inquiry, as for what are the means by which a key added to that keyring would be marked as invalid -- like, as for what would be the means by which a key revocation certificate (?) would be delivered on a key made to that keyring, and verified as that it was delivered by whom had delivered the original key. (I am assuming that that would consittue the mechanism for it, to invalidate a key in that keyring). Fourthly, a question: Regarding the public key that would be provided on a project request, then if the project-request will be accepted, will that public key be added onto the keyring at http://common-lisp.net/keyring.asc ? I had assumed that it would be, but I should like to know, without assumption. (Like, I am wondering about how the key would be used, as would be provided in coincidence with the project-request.) I know that the Debian development system includes the mechanism of a key service. (I am not immediately sure of how it is interfaced, and how it is operated, but I trust that they've documentation about it.) If I would have a key registered onto that key service, I wonder if that might suffice, either beside to or in lieu of that I would send a key, also, by email. I am aware that to have a key trusted onto Debian development, I would have to have that key marked as to be trusted, marked by someone who may verify my identity, onto that key -- for example, someone at a local Linux Users Group, and presumably, someone whom would already have a trusted public key. (I am aware that there is a Free/Open Source Users Group, locally. My not being much familiar with the group, however, I have been wary of trying to find out how this would be approached, there -- how to get a key marked as 'trusted', there -- but I am certain that it may come to be worked out.) That appears to be the end of the questions I find cause to ask on the mater. It is good to see if there are key systems being operated in regards to projects at common-lisp.net. I will admit that I have avoided bothering about email singing. Yet, taking the matter seriously, I've grounds enough as to ensure a verification of my identity on messages that I have sent. If personal email fraud is not conventional, but it is possible; it might take something of a directed attack, to pull off, but there is no cause to wait around for such. If I have not made a matter sufficiently clear, in what I have endeavored to address, above, then on inquiry, I may be glad to clarify. I would like to avoid comment, however, as about why I would find cause to state such a matter, explicitly. I look forward to the prospect of hosting a project at Common-Lisp.net Thank you -- Sean Champ

3 2

[clo-devel] [PATCH] Make project prefix configurable
by Erik Huelsmann 07 Jul '06

07 Jul '06

Hi! I've created the attached patch to disable the project prefix in notification mails because I'm a user of the common-lisp.net site which uses Trac for bug tracking for hosted projects which choose to do so. All lists get a list prefix prepended by Mailman, so that all tickets lists have a double prefix: both mailman and trac prepend a prefix containing the project name. If this could be turned off in Trac, there wouldn't be a need to change per-list settings in Mailman, so, I submit this patch hoping it (or a variant) will get committed. bye, Erik.

2 3

[clo-devel] darcsweb
by Julian Stecklina 06 Jul '06

06 Jul '06

Hello, currently the darcs repositories are hardcoded into darcsweb's config. What about mandating a standard location for darcs repos, like /project/*/darcs/* (which can be a symlink), and have a cron-job pick up darcs repositories and update the /usr/lib/cgi-bin/darcsweb/config.py? This would reduce the administrative overhead to about zero, if a maintainer decides to keep a `stable' and a `current' branch of his project. On a related sidenote: Could someone please add the following to darcsweb's config.py? class blitzblog: reponame = 'blitzblog' repodesc = 'blitzblog blog engine' repodir = '/project/blitzblog/public_html/darcs/blitzblog/' repourl = 'http://www.common-lisp.org/project/blitzblog/darcs/blitzblog/' repoencoding = 'utf8' Regards, -- Julian Stecklina Being really good at C++ is like being really good at using rocks to sharpen sticks. - Thant Tessman

2 2

← Newer
1
...
46
47
48
49
50
51
52
...
61
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

clo-devel