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

pending important debian bugs for Klee Dienes and Ian Jackson <dpkg-maint@chiark.greenend.org.uk>

Maintainer: Klee Dienes and Ian Jackson <dpkg-maint@chiark.greenend.org.uk>
Severity:   important
Status:     pending

This mail is being sent to you because the indicated bug reports have been
marked as important for the upcoming stable relase of Debian GNU/Linux.
Important reminders are repeated bi-monthly.

An open "important" bug is grounds for delaying the release of Debian or
having that package removed from the distribution.

#17624  dpkg              dpkg: installs regular dir when .deb contains symlink !  http://www.debian.org/Bugs/db/17/17624.html
#20401  dpkg              Problems updating bo -&gt; hamm                          http://www.debian.org/Bugs/db/20/20401.html
#21182  dpkg              dpkg: dpkg can go into an infinite loop with --force-co  http://www.debian.org/Bugs/db/21/21182.html
#25405  dpkg-dev          xpm: builds libc5 package on powerpc                     http://www.debian.org/Bugs/db/25/25405.html
#25537  dpkg-dev          dpkg-dev: dpkg-genchanges does not allow &quot;-&quot;   http://www.debian.org/Bugs/db/25/25537.html
#28817  dpkg              dpkg takes no care over libdpkg                          http://www.debian.org/Bugs/db/28/28817.html
#30891  dpkg              dpkg: Patch for update-alternatives to fix jdk problems  http://www.debian.org/Bugs/db/30/30891.html
#31508  dpkg-dev          parsechangelog broken?                                   http://www.debian.org/Bugs/db/31/31508.html
#31620  dpkg              dpkg: don't use hard coded ENOENT                        http://www.debian.org/Bugs/db/31/31620.html

For more information on the bug reporting system, visit:


If you feel the bug should not be marked with a severity of "important" or a
state of "pending", instructions on changing this can be found on the
above web site.

If you no longer maintain a package, mailto:override-change@debian.org
and ask to have the "overrides" file updated to point to the new maintainer.
Please provide the name and address of the new maintainer if you know who
it is.

Please do not reply to the "nag" address unless there is a problem with the
actual messages being generated.  There is no need to copy "nag" when
altering or closing bugs since the web pages are checked each time for
the current list of outstanding bugs.

Reply to: