List of RC-buggy source packages by maintainer/uploader

On 06/10/08 at 18:44 +0200, Alexander Reichle-Schmehl wrote:
> For maintainers (Or: For everyone with some more experience)
> ===============
> 
> It basically boils down to two things: If your packages have RC bugs open
> in "Lenny" fix them and take care, that the fix will propagate to
> "Lenny".

Hi,

Here is a list of source packages affected by RC bugs in lenny (either
fixed in unstable, or not), grouped by maintainer/uploader.

To know which bugs affect each package, use:
  http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=SOURCEPACKAGE&dist=testing
  (ie, append &dist=testing to your bug listing)

If you think that your package is listed here by mistake, please
ask. Mistakes are unlikely, so there might be something wrong with your
package.

You can get an updated list of lenny RC bugs from UDD:
http://udd.debian.net/cgi-bin/lenny_rc_by_srcpkg.cgi .
The list differs slightly from what bts.turmzimmer.net shows ; the
following bugs are affecting lenny, but are not listed on bts.tz.net:
393606 470846 476525 481072 495770 496529 496529 496859 496859 499771
499830 499830 499832 499832 499937 499937 500591
(UDD is right for those I manually checked)

==============================================================

Re: What you can do for "Lenny"

On Tuesday 07 October 2008 03:44, Alexander Reichle-Schmehl 
<tolimar <at> debian.org> wrote:
> Oh, and if you could refrain from upload new upstream versions of
> packages to "Sid", you would make all our lives easier. Some reasons:
>
> * New packages won't reach "Lenny" anyway.
> * Upload new packages to "Sid" makes it harder to get a fix into "Lenny"
>   should a new bug be found.
> * Uploading a new package makes it harder for other packages depending
>   on your package to be migrated to "Lenny".
> * You are wasting the buildd's time.

Is there any plan to fix things to allow separate uploads to testing and 
unstable for Lenny+1?

--

-- 
russell <at> coker.com.au
http://etbe.coker.com.au/          My Blog

http://www.coker.com.au/sponsorship.html Sponsoring Free Software development

Re: What you can do for "Lenny"

Le Mon, Oct 06, 2008 at 06:44:49PM +0200, Alexander Reichle-Schmehl a écrit :
> Too many release critical bugs

Hi all,

as one of the maintainer of the packages affected by the mass bug filing
named "The possibility of attack with the help of symlinks in some Debian
packages", I would like to make a comment:

Most of these bugs can only be exploited by a local user, are not
regressions, and do not permit to obtain superuser priviledges. In the
case of my package, the whole process of solving the issue in emergency
consumed a lot of time that could have been saved by adopting a simpler
workflow: report upstream, wait for the fix, and backport if necessary
or possible.

How about downgrading the severity of the bug reports to a level that
reflects the severity of the problem?

Have a nice day,

-- 
Charles Plessy
Debian Med packaging team,
Tsurumi, Kanagawa, Japan

--

-- 
To UNSUBSCRIBE, email to debian-devel-REQUEST <at> lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster <at> lists.debian.org

Fwd: What you can do for "Lenny"

---------- Forwarded message ----------
From: Alexander Reichle-Schmehl <tolimar <at> debian.org>
Date: 2008/10/6
Subject: What you can do for "Lenny"
To: debian-devel-announce <at> lists.debian.org

Hi!

You probably noticed by now, that Debian GNU/Linux 5.0 aka "Lenny" hasn't
been released in September. Well, that's a shame, but very easy to
explain: Too many release critical bugs[1].

 1: http://bts.turmzimmer.net/graph-large.png

Well, our release team coordinated several transitions, took care of
release goals, but it's pretty hard to estimate, how fast RC bugs will be
fixed, and apparently they were a bit to optimistic :(

The big question is: What can you do, to help release "Lenny" at least in
this quarter? That's pretty easy: Fix rc-bugs, take care, that the fixed
packages are migrated to "Lenny", do upgrade tests, document problems in
the release-notes. Pretty simple, isn't it?

For users (or better: For everyone)
=========

Even as a "simple user" (aren't we all just users?) you may help getting
"Lenny" released. Some things you can do:

* If you are running stable (aka "Etch"), you could consider

Fwd: What you can do for "Lenny"

---------- Forwarded message ----------
From: Alexander Reichle-Schmehl <tolimar <at> debian.org>
Date: 2008/10/6
Subject: What you can do for "Lenny"
To: debian-devel-announce <at> lists.debian.org

Hi!

You probably noticed by now, that Debian GNU/Linux 5.0 aka "Lenny" hasn't
been released in September. Well, that's a shame, but very easy to
explain: Too many release critical bugs[1].

 1: http://bts.turmzimmer.net/graph-large.png

Well, our release team coordinated several transitions, took care of
release goals, but it's pretty hard to estimate, how fast RC bugs will be
fixed, and apparently they were a bit to optimistic :(

The big question is: What can you do, to help release "Lenny" at least in
this quarter? That's pretty easy: Fix rc-bugs, take care, that the fixed
packages are migrated to "Lenny", do upgrade tests, document problems in
the release-notes. Pretty simple, isn't it?

For users (or better: For everyone)
=========

Even as a "simple user" (aren't we all just users?) you may help getting
"Lenny" released. Some things you can do:

* If you are running stable (aka "Etch"), you could consider
 upgrading to "Lenny" and see, if everything works fine. Currently there
 are no detailed release notes documenting the procedure, so you best
 way to test upgrades are to:

 1. Make backups
 2. Change your /etc/apt/sources.list
 3. Run aptitude update to get information about new packages
 4. Run aptitude install dpkg aptitude apt to install the newest package
    management
 5. Run aptitude full-upgrade

 If something goes wrong / something unexpected happens, please report
 it. If you already know a specific package, report a bug against that
 package. If you don't know, please report a bug describing the problem
 you experienced to the upgrade-reports package. If your problem is
 something, which can't be fixed properly, but should be documented
 (e.g. hardware support regressions, packages no longer available)
 please report a bug against the release-notes package (Bonus points if
 you not only report the bug, but also supply a paragraph to be added to
 the release notes).

* Speaking of the release notes[2]: You can take a look at the bugs reported
 against the release notes and see if you can help there, e.g. by
 writing a paragraph describing a problem.

  2: http://bugs.debian.org/release-notes

* Install the package devscripts[3] (you'll need the version provided by
 backports.org[4], and run the script rc-alert --include-dists TU. You'll
 get a list of release critical bugs open for one of the packages you
 have installed. Guessing that you have them installed, because you are
 using them and are interested in them, you should have a very high
 interest to get this bugs fixed :)

  3: http://packages.debian.org/devscripts
  4: http://www.backports.org/

 You can try to help, by trying to reproduce them and reporting that to
 the bug report. There are even some easy bugs, where the maintainer
 hasn't found the time, yet to fix it. Bug 497290[5] for example didn't
 need deep technical skills. It just needed someone with some time to
 collect the needed data for the copyright file.

  5: http://bugs.debian.org/497290

* If you speak a language other than English, you might consider joining
 the translation efforts. While it is to late to translate the
 debian-installer or the installation guide to a new language for
 "Lenny" (perhaps for the next release then?), you could start
 translating the release notes to a not yet supported language. If you
 are willing to do so (which can be quite time consuming, especially in
 the final phase), please contact either your localization team[6] or the
 debian doc mailing list[7] if there's no local mailing list.

  6: http://lists.debian.org/i18n.html
  7: http://lists.debian.org/debian-doc/

See? Even as a "simple user" without deeper technical knowledge you can
help us getting "Lenny" in shape to be released. If you have technical
knowledge: Very good! You might want to read the next section, too, and
see what applies to you, there :)

For maintainers (Or: For everyone with some more experience)
===============

It basically boils down to two things: If your packages have RC bugs open
in "Lenny" fix them and take care, that the fix will propagate to
"Lenny". If your packages don't have RC bugs open, fix someone else's RC
bug. Surely you don't think, the release team will fix the remaining rc
bugs, do you? And surely you understand, that your shiny rc bug free
packages are kind of useless, if they aren't released?

To search for bugs to be fixed, take a look at the unofficial rc bugs
thingy[8]. The URL lists RC bugs open in both "Sid" and "Lenny". Obviously
they should be fixed ASAP. If no one takes care about these packages,
they might be removed from "Lenny" (if possible).

 8: http://bts.turmzimmer.net/details.php?bydist=both&sortby=packages&fullcomment=on

Again: Try to reproduce the bug, try fix it, upload an NMU (or send your
patch to the bug report and search for an sponsor). You'll notice, that
some of these bugs already have a patch. In that case, your job would be
to test the patch, report that to the bug report and offer to sponsor an
NMU.

Another interesting list is the list of rc bugs open only in "Lenny"[9].
These bugs have been fixed, but the fix hasn't propagated to "Lenny",
yet. Normally, the release team will grant freeze exceptions for these
packages if possible. However, if the changes to the fixed version are
quite grave or the package in "Sid" depends on a newer package than in
"Lenny" that's not possible. In these cases look out for packages marked
as "need tpu upload" or similar.

 9: http://bts.turmzimmer.net/details.php?bydist=lenny-only&sortby=packages&fullcomment=on

Oh, and if you could refrain from upload new upstream versions of
packages to "Sid", you would make all our lives easier. Some reasons:

* New packages won't reach "Lenny" anyway.
* Upload new packages to "Sid" makes it harder to get a fix into "Lenny"
 should a new bug be found.
* Uploading a new package makes it harder for other packages depending
 on your package to be migrated to "Lenny".
* You are wasting the buildd's time.

And of course you should spend your time fixing rc bugs anyway ;)

Best regards,
 Alexander "To send out release announcements I do everything" Reichle-Schmehl

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFI6kCBBxd04ADYzRYRAhQ1AJ91zj+R9iiZdPUzywyRQqyotWFE3wCfbK2I
U3COcUjPAH4ELolxBgDbjGk=
=MdTy
-----END PGP SIGNATURE-----

-- 
പ്രവീണ്‍ അരിമ്പ്രത്തൊടിയില്‍
<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call, if you are unable to speak?
(as seen on /.)
Join The DRM Elimination Crew Now!
http://fci.wikia.com/wiki/Anti-DRM-Campaign

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFI6kCBBxd04ADYzRYRAhQ1AJ91zj+R9iiZdPUzywyRQqyotWFE3wCfbK2I
U3COcUjPAH4ELolxBgDbjGk=
=MdTy
-----END PGP SIGNATURE-----

_______________________________________________
To unsubscribe, email ilugc-request@... with 
"unsubscribe <password> <address>"
in the subject or body of the message.  
http://www.ae.iitm.ac.in/mailman/listinfo/ilugc