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

pending normal debian bugs for debian-devel@lists.debian.org



Maintainer: debian-devel@lists.debian.org
Severity:   normal
Status:     pending

This mail is being sent to you because the indicated bug reports have been
marked as overdue (i.e. has been open longer than 9 months).  Overdue
reminders are repeated monthly.

#20099  general           /etc/environment                                         http://www.debian.org/Bugs/db/20/20099.html
#20567  general           logo license outdated                                    http://www.debian.org/Bugs/db/20/20567.html
#20734  general           autoup.sh                                                http://www.debian.org/Bugs/db/20/20734.html
#20743  general           autoup.sh: wtmp, utmp and btmp                           http://www.debian.org/Bugs/db/20/20743.html
#21170  general           dpkg malfunction-unable to upgrade Debian                http://www.debian.org/Bugs/db/21/21170.html
#21464  general           bo -> hamm upgrade problems                           http://www.debian.org/Bugs/db/21/21464.html
#22016  general           general: backspace key generates ^H in X                 http://www.debian.org/Bugs/db/22/22016.html
#22184  general           hi. I'd like to point out a possible bug.                http://www.debian.org/Bugs/db/22/22184.html
#23340  general           Quite a bad error from libstdc++2.8                      http://www.debian.org/Bugs/db/23/23340.html
#23632  general           xserver and ispell missing in the hamm/sparc distributi  http://www.debian.org/Bugs/db/23/23632.html


For more information on the bug reporting system, visit:

        http://www.debian.org/Bugs/


If you feel the bug should not be marked with a severity of "normal" 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: