[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#712152: www.debian.org: proposed-updates page does not actually explain how do to one. Needs clarification.

Package: www.debian.org
Severity: normal

I was asked to do a stable release update, which needs an upload to
proposed-updates. I had never done one, so looked for some docs.
The top hit was the page:

But after reading that, despite being an experienced DD, I still
didn't know what I actually needed to do. Nowhere does it say "To do a
proposed-update upload, you upload to the normal debian upload
machine, as for an unstable upload, but with the Distribution in the
changes file set to the targetted 'Distribution:' ('stable', or current
stable codename). It is this suitename that sends the upload to the
correct internal queue". Or something like that.

The existing text "New packages can arrive into proposed-updates when
Debian developers upload them either to "proposed-updates"
("oldstable-proposed-updates"), or to "stable" ("oldstable")." is
clearly intended to convey this info, but that makes it sound like
'proposed-updates' is a special upload machine/place, perhaps
configured in dupload.conf or dput.cf, or maybe it's a string to go in
the 'Distribution:' field. The page is clearly written by someone who
understands the back-end, not for a user that wants to do the right
thing but is vague about how it all works. SPlitting it into 'How it
all works' and 'What to do if uploading' sections would probably work
a lot better.

I'll try to find time to rewrite the page and send a patch, but in the
meantime am filing this bug to record the issue.

-- System Information:
Debian Release: wheezy/sid
  APT prefers quantal-updates
  APT policy: (500, 'quantal-updates'), (500, 'quantal-security'), (500, 'quantal')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-35-generic (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium.  Thank you.

Reply to: