Bug#436726: marked as done (saslauthd: Won't start since $NAME is not set in init-scipt)

Your message dated Sat, 08 Sep 2007 03:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436726: fixed in cyrus-sasl2 2.1.22.dfsg1-15 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#436556: marked as done (cyrus-sasl2: [INTL:pt] Portuguese translation for debconf messages)

Your message dated Sat, 08 Sep 2007 03:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436556: fixed in cyrus-sasl2 2.1.22.dfsg1-15 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#433371: marked as done (cyrus-sasl2: [INTL:fr] French debconf templates translation)

Your message dated Sat, 08 Sep 2007 03:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#433371: fixed in cyrus-sasl2 2.1.22.dfsg1-15 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#439132: marked as done (cyrus-sasl2: [INTL:pt_BR] Brazilian Portuguese debconf templates translation)

Your message dated Sat, 08 Sep 2007 03:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#439132: fixed in cyrus-sasl2 2.1.22.dfsg1-15 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#438719: marked as done (cyrus-sasl2: [INTL:de] updated German debconf translation)

Your message dated Sat, 08 Sep 2007 03:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#438719: fixed in cyrus-sasl2 2.1.22.dfsg1-15 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#436726: marked as done (saslauthd: Won't start since $NAME is not set in init-scipt)

Your message dated Sat, 08 Sep 2007 03:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436440: fixed in cyrus-sasl2 2.1.22.dfsg1-15 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#436440: marked as done (sasl2-bin: saslauthd can not start, if the last config-update is denied)

Your message dated Sat, 08 Sep 2007 03:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436440: fixed in cyrus-sasl2 2.1.22.dfsg1-15 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#436440: marked as done (sasl2-bin: saslauthd can not start, if the last config-update is denied)

Your message dated Sat, 08 Sep 2007 03:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436726: fixed in cyrus-sasl2 2.1.22.dfsg1-15 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#440077: marked as done (xl2tpd: Please provide a backport for etch)

Your message dated Fri, 7 Sep 2007 20:37:58 -0400 with message-id <[EMAIL PROTECTED]> and subject line xl2tpd packages now on official backports has caused the attached Bug report 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 n

Bug#440219: marked as done (Tango Icon Theme 0.8.1 and Icon Naming Utils 0.8.6 are out)

Your message dated Fri, 07 Sep 2007 23:32:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#440219: fixed in tango-icon-theme 0.8.1-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Bug#413474: marked as done (stunnel4: configurable timeout_close in client mode ?)

Your message dated Fri, 7 Sep 2007 18:31:20 -0500 with message-id <[EMAIL PROTECTED]> and subject line TIMEOUTclose is configurable in stunnel4 has caused the attached Bug report 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

Bug#439570: marked as done (coq-float - FTBFS: /bin/sh: /usr/bin/coq_makefile: /usr/bin/ocamlrun: bad interpreter: No such file or directory)

Your message dated Fri, 07 Sep 2007 23:17:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#439570: fixed in coq 8.1.pl1+dfsg-3 has caused the attached Bug report 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

Bug#355081: marked as done (pdf manual is corrupted)

Your message dated Fri, 07 Sep 2007 23:02:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#355081: fixed in evolver 2.26c-1 has caused the attached Bug report 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 yo

Bug#329666: marked as done (mutt: imap folder changing leads to segfault)

Your message dated Sat, 8 Sep 2007 00:54:21 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#329666: mutt 1.5.16-3 fixes this problem has caused the attached Bug report 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

Bug#394489: marked as done (evolver: Please upgrade build-dep to freeglut3-dev)

Your message dated Fri, 07 Sep 2007 23:02:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#394489: fixed in evolver 2.26c-1 has caused the attached Bug report 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 yo

Bug#355082: marked as done (provide HTML doc reference to local pdf manual)

Your message dated Fri, 07 Sep 2007 23:02:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#355082: fixed in evolver 2.26c-1 has caused the attached Bug report 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 yo

Bug#440557: marked as done (icon-naming-utils: new upstream version 0.8.6)

Your message dated Sat, 8 Sep 2007 01:01:12 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#440557: fixed in icon-naming-utils 0.8.6-0.1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case i

Bug#441162: marked as done (cairo-ocaml - FTBFS: ml_cairo_bigarr.c:26: error: dereferencing pointer to incomplete type)

Your message dated Fri, 07 Sep 2007 22:32:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#441162: fixed in cairo-ocaml 20070908-1 has caused the attached Bug report 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

Bug#417064: marked as done (doesn't notice when it fails to build)

Your message dated Fri, 07 Sep 2007 22:17:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#417064: fixed in splat 1.2.0b-1 has caused the attached Bug report 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 you

Bug#439793: marked as done (nut: [INTL:pt_BR] Brazilian Portuguese debconf templates translation)

Your message dated Fri, 07 Sep 2007 22:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#439793: fixed in nut 2.2.0-2 has caused the attached Bug report 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 r

Bug#439407: marked as done (/etc/default/nut: remark for upsd while option for upsmon)

Your message dated Fri, 07 Sep 2007 22:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#439407: fixed in nut 2.2.0-2 has caused the attached Bug report 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 r

Bug#438037: marked as done (splat: not handling nostrip build option (policy 10.1))

Your message dated Fri, 07 Sep 2007 22:17:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#438037: fixed in splat 1.2.0b-1 has caused the attached Bug report 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 you

Bug#437811: marked as done (Missing udev rules file)

Your message dated Fri, 07 Sep 2007 22:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#437811: fixed in nut 2.2.0-2 has caused the attached Bug report 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 r

Bug#440524: marked as done (nut: [INTL:fr] French debconf templates translation update)

Your message dated Fri, 07 Sep 2007 22:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#440524: fixed in nut 2.2.0-2 has caused the attached Bug report 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 r

Bug#440369: marked as done (nut : [INTL:pt] Updated Portuguese translation for debconf messages)

Your message dated Fri, 07 Sep 2007 22:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#440369: fixed in nut 2.2.0-2 has caused the attached Bug report 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 r

Bug#439985: marked as done (Output of `libupsclient-config --libs' includes unresolved variable.)

Your message dated Fri, 07 Sep 2007 22:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#439985: fixed in nut 2.2.0-2 has caused the attached Bug report 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 r

Bug#417063: marked as done (FTBFS with GCC 4.3: first argument of 'int main...' should be...)

Your message dated Fri, 07 Sep 2007 22:17:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#417063: fixed in splat 1.2.0b-1 has caused the attached Bug report 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 you

Bug#441234: marked as done (nvidia-glx: Cannot load nvidia driver with linux-image-2.6.22+10)

Your message dated Fri, 7 Sep 2007 18:12:21 -0400 with message-id <[EMAIL PROTECTED]> and subject line Invalid has caused the attached Bug report 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 th

Bug#440892: marked as done (libgetopt-ocaml-dev: Dependency problem, makes package uninstallable with OCaml >= 3.10)

Your message dated Fri, 7 Sep 2007 17:43:18 -0400 (EDT) with message-id <[EMAIL PROTECTED]> and subject line Fixed in most recent upload has caused the attached Bug report 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 r

Bug#439568: marked as done (omake - FTBFS: ** omake error: write(): Bad file descriptor)

Your message dated Fri, 07 Sep 2007 21:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#439568: fixed in omake 0.9.8.5-3-2 has caused the attached Bug report 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

Bug#441258: marked as done (traceroute package doesn't include traceroute!)

Your message dated Fri, 07 Sep 2007 23:25:21 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#441258: traceroute package doesn't include traceroute! has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#441187: marked as done (mlgmp - FTBFS: tar: /build/user/mlgmp-20021123/debian/movelist: Cannot stat: No such file or directory)

Your message dated Fri, 07 Sep 2007 21:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#441187: fixed in mlgmp 20021123-12 has caused the attached Bug report 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

Bug#434728: marked as done (configuration should be in /etc/tomcat5.5)

Your message dated Fri, 07 Sep 2007 21:02:17 + with message-id <[EMAIL PROTECTED]> and subject line Bug#434728: fixed in tomcat5.5 5.5.23-1 has caused the attached Bug report 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

Bug#431704: marked as done (Policy file 50user.policy uses ${catalina.home}/webapps/ instead of ${catalina.base}/webapps/ )

Your message dated Fri, 07 Sep 2007 21:02:17 + with message-id <[EMAIL PROTECTED]> and subject line Bug#431704: fixed in tomcat5.5 5.5.23-1 has caused the attached Bug report 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

Bug#396170: marked as done (uninstallable (unsatisfiable dependency on ecj-bootstrap))

Your message dated Fri, 07 Sep 2007 21:02:17 + with message-id <[EMAIL PROTECTED]> and subject line Bug#396170: fixed in tomcat5.5 5.5.23-1 has caused the attached Bug report 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

Bug#426740: marked as done (All files under /var/lib/tomcat5.5/conf have wrong permissions)

Your message dated Fri, 07 Sep 2007 21:02:17 + with message-id <[EMAIL PROTECTED]> and subject line Bug#426740: fixed in tomcat5.5 5.5.23-1 has caused the attached Bug report 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

Bug#425020: marked as done (tomcat5.5: Does not honor empty TOMCAT5_USER)

Your message dated Fri, 07 Sep 2007 21:02:17 + with message-id <[EMAIL PROTECTED]> and subject line Bug#425020: fixed in tomcat5.5 5.5.23-1 has caused the attached Bug report 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

Bug#437963: marked as done (new upstream version needed)

Your message dated Fri, 07 Sep 2007 21:02:08 + with message-id <[EMAIL PROTECTED]> and subject line Bug#437963: fixed in libppi-perl 1.118-0.1 has caused the attached Bug report 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

Bug#434617: marked as done (tomcat5.5: Build doesn't clean up properly)

Your message dated Fri, 07 Sep 2007 21:02:17 + with message-id <[EMAIL PROTECTED]> and subject line Bug#434617: fixed in tomcat5.5 5.5.23-1 has caused the attached Bug report 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

Bug#436020: marked as done (tomcat5.5: crontest failure find: /var/log/tomcat5.5/: No such file or directory)

Your message dated Fri, 07 Sep 2007 21:02:17 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436020: fixed in tomcat5.5 5.5.23-1 has caused the attached Bug report 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

Bug#426761: marked as done (tomcat5.5: don't include auto-generated policy)

Your message dated Fri, 07 Sep 2007 21:02:17 + with message-id <[EMAIL PROTECTED]> and subject line Bug#426761: fixed in tomcat5.5 5.5.23-1 has caused the attached Bug report 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

Bug#427978: marked as done (tomcat5.5: fails to start if temp directory has too many files)

Your message dated Fri, 07 Sep 2007 21:02:17 + with message-id <[EMAIL PROTECTED]> and subject line Bug#427978: fixed in tomcat5.5 5.5.23-1 has caused the attached Bug report 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

Processed: Ack'ing and Closing old freetype1 NMU-fixed bug reports

Processing commands for [EMAIL PROTECTED]: > close 192813 Bug#192813: freetype1-tools: ttf2tfm segfaults 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Nikolaus Rath <[EMAIL PROTECTED]> > close 344439 Bug#344439: ttf2pk does n

Bug#274891: marked as done (apache2-mpm-worker: mod_autoindex listings show incorrect last-modified date)

Your message dated Fri, 7 Sep 2007 21:47:32 +0200 with message-id <[EMAIL PROTECTED]> and subject line apache2-mpm-worker: mod_autoindex listings show incorrect last-modified date has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt wi

Bug#438372: marked as done (varying installation directories)

Your message dated Fri, 7 Sep 2007 21:01:24 +0200 with message-id <[EMAIL PROTECTED]> and subject line [Build-common-hackers] Bug#438372: varying installation directories has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If th

Processed: Closing very old NMU'd bug

Processing commands for [EMAIL PROTECTED]: > # The previous maintainer forgot to ack the NMU very long ago, so I'm gonna > # close it with "close". > fixed 294850 0.50-2-2.1 Bug#294850: aspell-sv: Support for pending aspell 0.60 Bug marked as fixed in version 0.50-2-2.1. > close 294850 0.50-4 Bug

Bug#441210: marked as done (gfpoken: FTBFS: gimp script broken)

Your message dated Fri, 07 Sep 2007 17:32:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#441210: fixed in gfpoken 0.30-3 has caused the attached Bug report 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 you

Bug#441199: marked as done (hobbit-client: Client does not report test results)

Your message dated Fri, 07 Sep 2007 18:02:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#441199: fixed in hobbit 4.2.0.dfsg-3 has caused the attached Bug report 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 no

Bug#440504: marked as done (hobbit: French debconf templates translation)

Your message dated Fri, 07 Sep 2007 18:02:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#440504: fixed in hobbit 4.2.0.dfsg-3 has caused the attached Bug report 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 no

Bug#441011: marked as done (bb: manpage of bb should reside in section 6)

Your message dated Fri, 07 Sep 2007 18:02:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#441011: fixed in hobbit 4.2.0.dfsg-3 has caused the attached Bug report 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 no

Bug#440949: marked as done (hobbit: webinterface doesn't work)

Your message dated Fri, 07 Sep 2007 18:02:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#440949: fixed in hobbit 4.2.0.dfsg-3 has caused the attached Bug report 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 no

Bug#441140: marked as done (keep this anjuta in unstable)

Your message dated Fri, 7 Sep 2007 19:00:30 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#441140: keep this anjuta in unstable has caused the attached Bug report 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

Bug#439693: marked as done (hobbit : [INTL:pt] Portuguese translation for debconf messages)

Your message dated Fri, 07 Sep 2007 18:02:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#439693: fixed in hobbit 4.2.0.dfsg-3 has caused the attached Bug report 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 no

Bug#434923: marked as done (tramp: please prefer emacs22)

Your message dated Fri, 07 Sep 2007 17:48:16 + with message-id <[EMAIL PROTECTED]> and subject line Bug#434923: fixed in tramp 1:2.0.55-2 has caused the attached Bug report 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 y

Bug#436761: marked as done (tramp fails with wholenump error on xemacs21)

Your message dated Fri, 07 Sep 2007 17:48:16 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436761: fixed in tramp 1:2.0.55-2 has caused the attached Bug report 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 y

Bug#431786: marked as done (openoffice.org-core: please switch to libdb4.5)

Your message dated Fri, 07 Sep 2007 17:48:15 + with message-id <[EMAIL PROTECTED]> and subject line Bug#431786: fixed in openoffice.org 1:2.3.0~rc2-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#440910: marked as done (Segmentation fault at startup)

Your message dated Fri, 07 Sep 2007 13:18:56 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#440910: Segmentation fault at startup has caused the attached Bug report 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 n

Bug#375279: marked as done (Ekiga: no audio plugins are detected)

Your message dated Fri, 07 Sep 2007 11:17:50 -0600 with message-id <[EMAIL PROTECTED]> and subject line [ekiga] Not valid anymore has caused the attached Bug report 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 responsi

Bug#439301: marked as done (lmms: New upstream version)

Your message dated Fri, 07 Sep 2007 16:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#439301: fixed in lmms 0.3.0-1 has caused the attached Bug report 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

Bug#383406: marked as done (lmms doesn't generate menu entries)

Your message dated Fri, 07 Sep 2007 16:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#383406: fixed in lmms 0.3.0-1 has caused the attached Bug report 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

Processed: Already fixed

Processing commands for [EMAIL PROTECTED]: > close 373467 Bug#373467: Python policy transition 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to "Python Transition Mass bug" <[EMAIL PROTECTED]> > thanks Stopping processing here.

Bug#384406: marked as done (lmms: use qt i18n package)

Your message dated Fri, 07 Sep 2007 16:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#384406: fixed in lmms 0.3.0-1 has caused the attached Bug report 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

Bug#389037: marked as done (does not specify version for lmms-common)

Your message dated Fri, 07 Sep 2007 16:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#389037: fixed in lmms 0.3.0-1 has caused the attached Bug report 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

Bug#439302: marked as done (lmms: Add a debian/watch)

Your message dated Fri, 07 Sep 2007 16:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#439302: fixed in lmms 0.3.0-1 has caused the attached Bug report 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

Bug#383295: marked as done (FTBFS with GCC 4.2: -floop-optimize2 has been removed)

Your message dated Fri, 07 Sep 2007 16:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#383295: fixed in lmms 0.3.0-1 has caused the attached Bug report 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

Bug#433262: marked as done (lmms: Does not save arpeggio status)

Your message dated Fri, 07 Sep 2007 16:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#433262: fixed in lmms 0.3.0-1 has caused the attached Bug report 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

Processed: closing 441217

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.26 > close 441217 Bug#441217: rt2500-source: RT2500STA.dat not mentioned in INSTALL.debian 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any fur

Bug#441233: marked as done (CVE-2007-1888 possible code execution via sqlite_decode_binary)

Your message dated Fri, 07 Sep 2007 16:02:12 + with message-id <[EMAIL PROTECTED]> and subject line Bug#441233: fixed in sqlite 2.8.17-2.1 has caused the attached Bug report 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

Bug#439027: marked as done (apache2.2-common: /etc/init.d/apache2 doesn't consistently use apache2ctl)

Your message dated Fri, 07 Sep 2007 16:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#439027: fixed in apache2 2.2.6-1 has caused the attached Bug report 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 yo

Bug#440084: marked as done (apache2: Fixes to the NEWS file)

Your message dated Fri, 07 Sep 2007 16:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#440084: fixed in apache2 2.2.6-1 has caused the attached Bug report 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 yo

Bug#414855: marked as done (wildcard cert not working in apache 2.2)

Your message dated Fri, 07 Sep 2007 16:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#414855: fixed in apache2 2.2.6-1 has caused the attached Bug report 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 yo

Bug#439375: marked as done (Regressions from default configuration file in Apache 1.3)

Your message dated Fri, 07 Sep 2007 16:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#439375: fixed in apache2 2.2.6-1 has caused the attached Bug report 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 yo

Bug#356285: marked as done (apache2-utils: add note to manpage that htpasswd is not safe for setuid/sudo)

Your message dated Fri, 07 Sep 2007 16:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#356285: fixed in apache2 2.2.6-1 has caused the attached Bug report 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 yo

Bug#438950: marked as done (apache2.2-common: init.d is too noisy on reload)

Your message dated Fri, 07 Sep 2007 16:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#438950: fixed in apache2 2.2.6-1 has caused the attached Bug report 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 yo

Bug#441191: marked as done (pidgin-dev should depend on libpurple-dev)

Your message dated Fri, 07 Sep 2007 15:47:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#441191: fixed in pidgin 2.1.1-4 has caused the attached Bug report 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 you

Bug#432044: marked as done (geomview: A new verion of geomview was released in May)

Your message dated Fri, 07 Sep 2007 15:42:52 + with message-id <[EMAIL PROTECTED]> and subject line Bug#432044: fixed in geomview 1.9.3-1 has caused the attached Bug report 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 y

Bug#402040: marked as done (geomview: no images are displayed in the HTML version of the manual)

Your message dated Fri, 07 Sep 2007 15:42:52 + with message-id <[EMAIL PROTECTED]> and subject line Bug#402040: fixed in geomview 1.9.3-1 has caused the attached Bug report 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 y

Bug#395474: marked as done (geomview: upgrade to Geomview 1.8.2)

Your message dated Fri, 07 Sep 2007 15:42:52 + with message-id <[EMAIL PROTECTED]> and subject line Bug#395474: fixed in geomview 1.9.3-1 has caused the attached Bug report 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 y

Bug#437897: marked as done (New version of no-ip released (2.1.6))

Your message dated Fri, 07 Sep 2007 15:42:32 + with message-id <[EMAIL PROTECTED]> and subject line Bug#437897: fixed in no-ip 2.1.7-1 has caused the attached Bug report 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

Bug#328842: marked as done (no-ip: Could use debconf for configuration)

Your message dated Fri, 07 Sep 2007 15:42:32 + with message-id <[EMAIL PROTECTED]> and subject line Bug#328842: fixed in no-ip 2.1.7-1 has caused the attached Bug report 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

Bug#350391: marked as done (ITP: glest -- Free 3D fantasy real-time-strategy game)

Your message dated Fri, 07 Sep 2007 15:36:33 + with message-id <[EMAIL PROTECTED]> and subject line Bug#350391: fixed in glest 2.0.0-2 has caused the attached Bug report 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

Bug#441220: marked as done (xserver-xorg-video-intel: Please rebuild experimental version)

Your message dated Fri, 07 Sep 2007 17:37:28 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#441220: xserver-xorg-video-intel: Please rebuild experimental version has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with

Processed: Re: Bug#441202: openoffice 2.2.1-8 requires gcj (lenny) when another java present

Processing commands for [EMAIL PROTECTED]: > notfound 441202 2.2.1 Bug#441202: openoffice 2.2.1-8 requires gcj (lenny) when another java present Bug no longer marked as found in version 2.2.1. > found 441202 2.2.1-8 Bug#441202: openoffice 2.2.1-8 requires gcj (lenny) when another java present Bug

Bug#441197: marked as done (Python-gammu doesn't work with other version of gammu than built time one)

Your message dated Fri, 07 Sep 2007 14:32:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#441197: fixed in python-gammu 0.22-2 has caused the attached Bug report 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 no

Bug#439009: marked as done (gnumeric: plese change menu section to Applications/Office.)

Your message dated Fri, 07 Sep 2007 14:17:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#439009: fixed in gnumeric 1.7.12-1 has caused the attached Bug report 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

Bug#432962: marked as done (gnumeric: not binNMU safe)

Your message dated Fri, 07 Sep 2007 14:17:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#432962: fixed in gnumeric 1.7.12-1 has caused the attached Bug report 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

Bug#428629: marked as done (logcheck-database: please ignore bind "slave" views)

Your message dated Fri, 07 Sep 2007 13:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#428629: fixed in logcheck 1.2.61 has caused the attached Bug report 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 yo

Bug#412201: marked as done (/tmp: write error: No space left on device)

Your message dated Fri, 07 Sep 2007 13:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#412201: fixed in logcheck 1.2.61 has caused the attached Bug report 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 yo

Bug#441127: marked as done (lablgtk2 - FTBFS: dh_install: liblablgtk2-ocaml-dev missing files (usr/lib/ocaml/3.10.0/lablgtk2/*.cmx), aborting)

Your message dated Fri, 7 Sep 2007 15:32:54 +0200 with message-id <[EMAIL PROTECTED]> and subject line lablgtk2 2.6.0-13 fix this bug has caused the attached Bug report 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 resp

Bug#441209: marked as done (CVE-2007-4743 Incorrect fix for CVE-2007-3999)

Your message dated Fri, 7 Sep 2007 15:25:30 +0200 with message-id <[EMAIL PROTECTED]> and subject line CVE-2007-4743 Incorrect fix for CVE-2007-3999 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it i

Bug#436439: marked as done (spamd: only ignore "good" child states)

Your message dated Fri, 07 Sep 2007 13:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436439: fixed in logcheck 1.2.61 has caused the attached Bug report 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 yo

Bug#425035: marked as done (hylafax-server: missing logcheck rule)

Your message dated Fri, 07 Sep 2007 13:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#425035: fixed in logcheck 1.2.61 has caused the attached Bug report 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 yo

Bug#440123: marked as done (ignore.d.server/logcheck: please update for pam 0.99+)

Your message dated Fri, 07 Sep 2007 13:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#440123: fixed in logcheck 1.2.61 has caused the attached Bug report 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 yo

Bug#426736: marked as done (please support postfix check_helo_(ms|ns)_access)

Your message dated Fri, 07 Sep 2007 13:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#426736: fixed in logcheck 1.2.61 has caused the attached Bug report 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 yo

Bug#425642: marked as done (logcheck-database: please support postfix delay_reject=no)

Your message dated Fri, 07 Sep 2007 13:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#425642: fixed in logcheck 1.2.61 has caused the attached Bug report 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 yo

Bug#440793: marked as done (README.Debian is incorrect)

Your message dated Fri, 07 Sep 2007 12:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#440793: fixed in virtualbox-ose 1.5.0-dfsg2-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#441180: marked as done (logcheck-database: pam change needs change in logcheck-database)

Your message dated Fri, 07 Sep 2007 13:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#440123: fixed in logcheck 1.2.61 has caused the attached Bug report 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 yo

Bug#440181: marked as done (logcheck: Please ignore rsync symlink transfers)

Your message dated Fri, 07 Sep 2007 13:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#440181: fixed in logcheck 1.2.61 has caused the attached Bug report 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 yo

Processed: reopening 435173, closing 435173

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.7 > reopen 435173 Bug#435173: amarok: New subfolder under Radio Streams is discarded Bug reopened, originator not changed. > close 435173 1.4.7-1 Bug#435173: amarok: New subfolder under

Bug#435173: marked as done (amarok: New subfolder under Radio Streams is discarded)

Your message dated Fri, 7 Sep 2007 15:09:54 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#435173: Bug can be closed has caused the attached Bug report 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 respo

  1   2   >