Differences between revisions 1 and 17 (spanning 16 versions)
Revision 1 as of 2006-03-04 20:54:49
Size: 72
Editor: ?SteffenJoeris
Comment: initial release
Revision 17 as of 2006-03-09 22:06:57
Size: 4457
Editor: ?SteffenJoeris
Comment: add small cvs explanation
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
            ftpmaster-Howto
-----------------------------------------
= ftpmaster-Howto =

The dak system is located on administrator.skolelinux.no .
After you logged in on a.s.n. you have to become the katie user. If you are a ftpmaster you can use the command "sudo -u katie bash" Now you are the debadmin user and have access to the archive system.

== Configuration: ==
If it is neccessary to change a config file or a script under bin, cron or katie you have to change them first and then call "cvs diff" and "cvs commit".

== NEW Handling: ==
One of the most important jobs of the ftpmaster is to handle the NEW queue. The NEW queue are packages which are signed by a Debian-Edu Developer and passed the key check. So you don't need to check if the signature is valid or not.

The ftpmaster's task is to check the package if it is ready for Debian-Edu or not. To get a checklist you can use the Debian-Edu Archive Policy and check if it passes all points.

First change into the directory /org/ftp.skolelinux.org/queue/new/
There you find the packages.
After you have checked the package you have to run
"lisa package_xxx-x_arch.changes"

Then you can type "c" and check some important points of the packages again. After you made your decision you can either accept or reject the package.

To accept it as it is (means no changes to maintainers suggestion for override) type "a" . Then the override file is changed.
If you disagree to the maintainer and e.g. want to change the section field you can run "e". Then make your changes and the package is accepted.

If you want to reject the package type "m". Then you get a text editor (vim) and can describe the reason there.
In case of rejection please use the following template form:
{{{
Hi Maintainer, ...

... reason ...
rejected for now.
}}}

At the end of the rejection message lisa will automatically insert the text from the template which can be found under "/org/ftp.skolelinux.org/katie/templates/katie.rejected"
Please do not edit the template.

== Moving packages to other distributuins ==
Packages should be uploaded to '''etch-test''' for now. After they have been there for a while, and the maintainer and/or ftpmaster deceided to move it to '''etch''', the ftpmasters need to move them '''by hand'''. This is to make sure only stable and good packages end up in '''etch'''. The command to be executed is as follows
{{{
madison -s etch-test $package-name -S -f heidi | sudo -u katie heidi -a etch
}}}

''Don't wory about packages the are uploaded with distribution '''etch''' in their changelog, they will end up in '''etch-test''' first. :-)''

== New Accounts: ==
{{{
Please note that only drift@skolelinux.org decides to give someone account rights! If drift writes a mail to ftpmasters and tells them that a new Uploader needs an account for upload rights the ftpmaster need the gpg-key from the new Uploader.
For that purpose please write the new Uploader direclty and ask after a mail or get the key id and fingerprint from drift@skolelinux.org. }}}
If the ftpmasters are instructed to create an account they can follow this procedure:

After login on administrator.skolelinux.no they have to become katie user ("sudo -u katie bash").
Then they can use the command: "/org/ftp.skolelinux.org/bin/sabine -k ''keyid''"

After that the new account is created and the new Uploader will get a mail which informs about it and explains some configuration steps for dput/dupload.


== TODO-List for ftpmasters: ==

 1. we need a finish configuration of the ftp server to allow ftpnew.skolelinux.org/pub/UploadQueue and later maybe ftp.skolelinux.org/pub/UploadQueue
 1. We need to arrange the webserver stuff to show the new.html
 1. we need a working script for moving packages
 1. We need to create the CD's from the pools
 1. We need to fix the "Processing of *changes" mails
 1. we need to make sure that all mails go to changed-by or we have to change the maintainer field every time

== misc docu bits: ==

 * <zobel> there we go
 * <zobel> after an upload, unprocessed packages will be in /org/ftp.skolelinux.org/queue/unchecked/
 * <zobel> every 15min cron/unchecked is running
 * <zobel> if the package allready exists in the database, the package moves to accepted
 * <zobel> otherwise it moves to queue/new
 * <zobel> from there, an ftp-admin (probaply you) needs to run lisa *.changes and accept packages

== Work Session ==

April 1st&2nd
Hamburg, at h01gers place

ftpmaster-Howto

The dak system is located on administrator.skolelinux.no . After you logged in on a.s.n. you have to become the katie user. If you are a ftpmaster you can use the command "sudo -u katie bash" Now you are the debadmin user and have access to the archive system.

Configuration:

If it is neccessary to change a config file or a script under bin, cron or katie you have to change them first and then call "cvs diff" and "cvs commit".

NEW Handling:

One of the most important jobs of the ftpmaster is to handle the NEW queue. The NEW queue are packages which are signed by a Debian-Edu Developer and passed the key check. So you don't need to check if the signature is valid or not.

The ftpmaster's task is to check the package if it is ready for Debian-Edu or not. To get a checklist you can use the Debian-Edu Archive Policy and check if it passes all points.

First change into the directory /org/ftp.skolelinux.org/queue/new/ There you find the packages. After you have checked the package you have to run "lisa package_xxx-x_arch.changes"

Then you can type "c" and check some important points of the packages again. After you made your decision you can either accept or reject the package.

To accept it as it is (means no changes to maintainers suggestion for override) type "a" . Then the override file is changed. If you disagree to the maintainer and e.g. want to change the section field you can run "e". Then make your changes and the package is accepted.

If you want to reject the package type "m". Then you get a text editor (vim) and can describe the reason there. In case of rejection please use the following template form:

Hi Maintainer, ...

... reason ...
rejected for now.

At the end of the rejection message lisa will automatically insert the text from the template which can be found under "/org/ftp.skolelinux.org/katie/templates/katie.rejected" Please do not edit the template.

Moving packages to other distributuins

Packages should be uploaded to etch-test for now. After they have been there for a while, and the maintainer and/or ftpmaster deceided to move it to etch, the ftpmasters need to move them by hand. This is to make sure only stable and good packages end up in etch. The command to be executed is as follows

madison -s etch-test $package-name -S -f heidi | sudo -u katie heidi -a etch

Don't wory about packages the are uploaded with distribution etch in their changelog, they will end up in etch-test first. :-)

New Accounts:

Please note that only drift@skolelinux.org decides to give someone account rights! If drift writes a mail to ftpmasters and tells them that a new Uploader needs an account for upload rights the ftpmaster need the gpg-key from the new Uploader.
For that purpose please write the new Uploader direclty and ask after a mail or get the key id and fingerprint from drift@skolelinux.org. 

If the ftpmasters are instructed to create an account they can follow this procedure:

After login on administrator.skolelinux.no they have to become katie user ("sudo -u katie bash"). Then they can use the command: "/org/ftp.skolelinux.org/bin/sabine -k keyid"

After that the new account is created and the new Uploader will get a mail which informs about it and explains some configuration steps for dput/dupload.

TODO-List for ftpmasters:

  1. we need a finish configuration of the ftp server to allow ftpnew.skolelinux.org/pub/UploadQueue and later maybe ftp.skolelinux.org/pub/UploadQueue
  2. We need to arrange the webserver stuff to show the new.html
  3. we need a working script for moving packages
  4. We need to create the CD's from the pools
  5. We need to fix the "Processing of *changes" mails
  6. we need to make sure that all mails go to changed-by or we have to change the maintainer field every time

misc docu bits:

  • <zobel> there we go

  • <zobel> after an upload, unprocessed packages will be in /org/ftp.skolelinux.org/queue/unchecked/

  • <zobel> every 15min cron/unchecked is running

  • <zobel> if the package allready exists in the database, the package moves to accepted

  • <zobel> otherwise it moves to queue/new

  • <zobel> from there, an ftp-admin (probaply you) needs to run lisa *.changes and accept packages

Work Session

April 1st&2nd Hamburg, at h01gers place