Your message dated Sat, 03 Jan 2009 00:49:29 +0100
with message-id <[email protected]>
and subject line Changes to the DM code
has caused the Debian Bug report #502943,
regarding Missing entry in "Packages debian maintainers may update", or wrong
interpretation of GR 2007/3 "DM"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
502943: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502943
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: important
[CC'ing -project]
Hi everyone,
A couple of days ago xserver-xorg-video-openchrome 1:0.2.903+svn599-1 was
uploaded to experimental with DM-Upload-Allowed: yes; but despite this, it
still does not show up in dm-uploaders.html[1].
The new package *does* also build a, dummy transitional,
xserver-xorg-video-via package which was *not* present in experimental at the
time of the upload of -openchrome's latest version, but *does* exist in
unstable (actually in all but experimental) and is provided by a different
source package.
The GR[2] *does* state the following:
> 5. The initial policy for the use of the Debian Maintainer keyring with the
> Debian archive will be to accept uploads signed by a key in that keyring
> provided:
[...]
> * none of the packages are being taken over from other source packages
I believe at the time the implementation was made the above quoted point was
missunderstood, as it prohibits uploads by *DM*s from taking over packages
provided by another source package; and *only* that. It does not in that, nor
any other, point state that following uploads are also prohibited.
As I understand it, once a DD uploads the package which takes over another
binary package with regard to unstable the DM should be able to upload new
package versions which do also provide the new binary package.
Unless my interpretation is proved wrong (reason why -project is CCed) please
fixing the bug soon; as it would otherwise be useless the fact that I am a DM
(at least for that specific package as it is *not* going to drop the -via
transitional package before squeeze is released with it).
[1]http://ftp-master.debian.org/dm-uploaders.html
[2]http://www.debian.org/vote/2007/vote_003
Kind regards,
--
Raphael Geissert - Debian Maintainer
www.debian.org - get.debian.net
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Hey,
if you are a DM uploading your packages, please pay extra attention in
the next few days. We just changed the underlying code in our archive
software to be less awkward. While we did test that (using the help from
Eugene V. Lyubimkin (thanks)) there might be cases not covered by our
tests.
This also fixes on of the other bugs the old implementation had - DMs
should now be able to upload to experimental too. Or
proposed-updates. Basically anywhere. :)
For those interested, the *highest* available version in our archive has
to have the DM-Upload-Allowed flag to allow the DM upload to happen, we
no longer blindly assume that unstable is the suite to look in.
(If you want to blame someone, try ftpmaster. If you want to say thanks
for the changes, try Michael Casadevall, he got most of the headache
rewriting the code, and then ftpmaster for merging it.)
--
bye, Joerg
<mechanix> anyone from the MIA team around? tbm?
<Ganneff> sounds nice. how long do you have to be MIA to get into that team? :)
<mhp> you need to have a pgp key, I suppose. and no gpg one, and only a bo box
<Np237> yes, but it must be expired
pgpaxGUXddL5u.pgp
Description: PGP signature
--- End Message ---
