gsumi_1.1.0-6_i386.changes ACCEPTED

Accepted: gsumi_1.1.0-6.diff.gz to pool/main/g/gsumi/gsumi_1.1.0-6.diff.gz gsumi_1.1.0-6.dsc to pool/main/g/gsumi/gsumi_1.1.0-6.dsc gsumi_1.1.0-6_i386.deb to pool/main/g/gsumi/gsumi_1.1.0-6_i386.deb Announcing to debian-devel-changes@lists.debian.org Thank you for your contribution to Debi

Processing of gsumi_1.1.0-6_i386.changes

gsumi_1.1.0-6_i386.changes uploaded successfully to localhost along with the files: gsumi_1.1.0-6.dsc gsumi_1.1.0-6.diff.gz gsumi_1.1.0-6_i386.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [

Bug#358506: pppoeconf adds line recursively to /etc/network/interfaces

Package: pppoeconf Version: 1.9 Severity: important Other info: Architecture: i386 Kernel Version: 2.6.15.6 Debian Relase: Testing/Unstable libc6: testing uptodate 2.3.6-3 Version of depends and other packages: gettext-base: testing uptodate 0.14.5-2 ppp: testing uptodate 2.4.4b1-1 pppoe: testi

Bug#262119: marked as done (kimberlite: FTBFS with gcc-3.4: parse error before string constant)

Your message dated Wed, 22 Mar 2006 23:35:02 +0100 with message-id <[EMAIL PROTECTED]> and subject line Fixed in kimberlite 1.1.0-3.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 your resp

Processed: Re: uudeview and CAN-2004-2265

Processing commands for [EMAIL PROTECTED]: > clone 320541 -1 -2 Bug#320541: unsafe temp file creation (CAN-2004-2265) Bug 320541 cloned as bugs 358500-358501. > reassign -1 dnprogs Bug#358500: unsafe temp file creation (CAN-2004-2265) Bug reassigned from package `uudeview' to `dnprogs'. > reassi

Bug#340159: marked as done (linuxconf-1.26r4/diajava/XColorNames.java fails DFSG #1)

Your message dated Wed, 22 Mar 2006 23:43:46 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#284865: marked as done (kimberlite: FTBFS (amd64/gcc-4.0): static declaration of 'loglevel' follows non-static declaration)

Your message dated Wed, 22 Mar 2006 23:35:02 +0100 with message-id <[EMAIL PROTECTED]> and subject line Fixed in kimberlite 1.1.0-3.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 your resp

Bug#280247: marked as done (kimberlite: FTBFS (amd64/gcc-3.4): Please use '#include ' instead of 'extern int errno;')

Your message dated Wed, 22 Mar 2006 23:35:02 +0100 with message-id <[EMAIL PROTECTED]> and subject line Fixed in kimberlite 1.1.0-3.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 your resp

Bug#241959: marked as done (kimberlite_1.1.0-3.2(unstable): FTBFS: swig errors)

Your message dated Wed, 22 Mar 2006 23:35:02 +0100 with message-id <[EMAIL PROTECTED]> and subject line Fixed in kimberlite 1.1.0-3.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 your resp

Bug#201226: marked as done (kimberlite: FTBFS: Missing files)

Your message dated Wed, 22 Mar 2006 23:28:45 +0100 with message-id <[EMAIL PROTECTED]> and subject line Fixed in kimberlite 1.1.0-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 your resp

Bug#210496: marked as done (kimberlite_1.1.0-3.1(hppa/unstable): FTBFS: non-PIC in shared object)

Your message dated Wed, 22 Mar 2006 23:32:42 +0100 with message-id <[EMAIL PROTECTED]> and subject line Fixed in kimberlite 1.1.0-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 your resp

manued-el_0.9.5-1_i386.changes ACCEPTED

Accepted: manued-el_0.9.5-1.diff.gz to pool/main/m/manued-el/manued-el_0.9.5-1.diff.gz manued-el_0.9.5-1.dsc to pool/main/m/manued-el/manued-el_0.9.5-1.dsc manued-el_0.9.5-1_all.deb to pool/main/m/manued-el/manued-el_0.9.5-1_all.deb manued-el_0.9.5.orig.tar.gz to pool/main/m/manued-el/manu

Bug#326714: acknowledged by developer (Removed)

Debian Bug Tracking System a écrit : > This is an automatic notification regarding your Bug report > #326714: kbear crashes at every file transfer, > which was filed against the kbear package. > > It has been closed by one of the developers, namely > Matej Vela <[EMAIL PROTECTED]>. > > Their explan

Bug#326714: Removed

François Valenduc <[EMAIL PROTECTED]> writes: [...] > It's true that gftp-gtk is also a good replacement but I think > kftpgrabber is better in a KDE/Qt environment. > What do you think of my proposal ? Sure. It seems Fathi BOUDRA already intends to package it for Debian; see

Processing of manued-el_0.9.5-1_i386.changes

manued-el_0.9.5-1_i386.changes uploaded successfully to localhost along with the files: manued-el_0.9.5-1.dsc manued-el_0.9.5.orig.tar.gz manued-el_0.9.5-1.diff.gz manued-el_0.9.5-1_all.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a

Bug#260476: marked as done (cscvs: Long description contains spelling error)

Your message dated Wed, 22 Mar 2006 15:19:16 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#256929: marked as done (cscvs: option --help-synonymns not recognized)

Your message dated Wed, 22 Mar 2006 15:19:16 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#119793: marked as done (memprof crashes when you try to detatch from itself)

Your message dated Wed, 22 Mar 2006 15:28:17 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#82713: marked as done ([patch] fix for listen's busy-wait behaviour, and some other dumb stuff)

Your message dated Wed, 22 Mar 2006 15:16:14 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#303477: marked as done (kmatplot: Do not release with sarge...)

Your message dated Wed, 22 Mar 2006 15:23:59 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#288069: marked as done (cscvs totla -d does not fail gracefully when tla does not support --date)

Your message dated Wed, 22 Mar 2006 15:19:16 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#320900: marked as done (FTBFS: Cannot find libXinerama)

Your message dated Wed, 22 Mar 2006 15:23:59 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#309577: marked as done (memprof: incompatible with threads (NPTL?))

Your message dated Wed, 22 Mar 2006 15:28:17 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#75025: marked as done (icecast hangs)

Your message dated Wed, 22 Mar 2006 15:16:14 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#349453: marked as done (memprof hangs just after executing profiled app)

Your message dated Wed, 22 Mar 2006 15:28:17 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#345411: marked as done (kbear: Crashes on second file transfer)

Your message dated Wed, 22 Mar 2006 15:25:42 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#326714: marked as done (kbear crashes at every file transfer)

Your message dated Wed, 22 Mar 2006 15:25:42 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#285734: marked as done (Replace kmatplot with qmatplot)

Your message dated Wed, 22 Mar 2006 15:23:59 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#288068: marked as done (cscvs: should have an option for automatic handling of moves/renames)

Your message dated Wed, 22 Mar 2006 15:19:16 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#148577: marked as done (Incomplete manpage for shout)

Your message dated Wed, 22 Mar 2006 15:16:14 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#243605: marked as done (cscvs: add an option to translate characters illegal for tla)

Your message dated Wed, 22 Mar 2006 15:19:16 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#241415: marked as done (Improve documentation regarding octave usage and scilab support)

Your message dated Wed, 22 Mar 2006 15:23:59 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#240740: marked as done (cscvs: fails with no such directory error)

Your message dated Wed, 22 Mar 2006 15:19:16 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#349295: marked as done (memprof doesn't do anything?)

Your message dated Wed, 22 Mar 2006 15:28:17 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#149164: marked as done (shout does not feed data fast enough)

Your message dated Wed, 22 Mar 2006 15:16:14 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#321120: marked as done (cscvs: can't create any cache)

Your message dated Wed, 22 Mar 2006 15:19:16 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#316975: marked as done (kmatplot wont install on sid because of dependency problems)

Your message dated Wed, 22 Mar 2006 15:23:59 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#356684: marked as done (FTBFS with G++ 4.1: misc errors)

Your message dated Wed, 22 Mar 2006 15:23:59 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#259850: marked as done (cscvs: Switch to "officially preferred" upstream branch)

Your message dated Wed, 22 Mar 2006 15:19:16 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#256921: marked as done (cscvs: Parser error: bad rlog parser, no cookie!)

Your message dated Wed, 22 Mar 2006 15:19:16 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#241631: marked as done (cscvs: curruption of binary files)

Your message dated Wed, 22 Mar 2006 15:19:16 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#174630: marked as done (icecast-client: Including ices as a replacement for orphaned shout)

Your message dated Wed, 22 Mar 2006 15:16:14 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#203087: marked as done (icecast-client: shout won't read from devices (e.g. stdin))

Your message dated Wed, 22 Mar 2006 15:16:14 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#102973: marked as done ("Read image from CD" produces corrupt images with no warnings.)

Your message dated Wed, 22 Mar 2006 14:57:08 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#339411: marked as done (dcl: "numrows" global is not used for initial tickets display, but is used when changing pages.)

Your message dated Wed, 22 Mar 2006 14:50:01 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#216294: marked as done (dcl: Postgresql createdb.sql uses erroneous syntax)

Your message dated Wed, 22 Mar 2006 14:50:01 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#218498: marked as done (gkdial: disconnecting on a busy tone crashes x server)

Your message dated Wed, 22 Mar 2006 15:01:02 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#202764: marked as done (oonsoo: oonsoo hangs when other program uses /dev/dsp)

Your message dated Wed, 22 Mar 2006 14:51:41 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#162177: marked as done (INSTALL.txt: minor omission in "2.2.1 PostgreSQL")

Your message dated Wed, 22 Mar 2006 14:50:01 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#160998: marked as done (gkdial: offers no way to edit a provider)

Your message dated Wed, 22 Mar 2006 15:01:02 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#182518: marked as done (dcl: Database Updates Not Applied)

Your message dated Wed, 22 Mar 2006 14:50:01 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#247462: marked as done (gcombust crashes)

Your message dated Wed, 22 Mar 2006 14:57:08 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#103198: marked as done (Compare funktion follows symlinks and loops)

Your message dated Wed, 22 Mar 2006 14:57:08 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#99778: marked as done ("gcombust lacks enough user-documentation")

Your message dated Wed, 22 Mar 2006 14:57:08 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#41010: marked as done (gcombust: No man page gcombust(1) available)

Your message dated Wed, 22 Mar 2006 14:57:08 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#218014: marked as done (gkdial, on a 'disconnect' command, kill the parent application (like gnome panel))

Your message dated Wed, 22 Mar 2006 15:01:02 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#220429: marked as done (python-bsddb3: new upstream release)

Your message dated Wed, 22 Mar 2006 14:47:37 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#162308: marked as done (gkdial-gnome: Dropdown list doesn't sort)

Your message dated Wed, 22 Mar 2006 15:01:02 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#301301: marked as done (gkdial: Improper copyright file)

Your message dated Wed, 22 Mar 2006 15:01:02 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#318368: marked as done (gkdial: Missing Gnome2/Freedesktop menu entry)

Your message dated Wed, 22 Mar 2006 15:01:02 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#162456: marked as done (dcl: missing file: /dcl/str/en/help/boWorkorders.newseq.php)

Your message dated Wed, 22 Mar 2006 14:50:01 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#155511: marked as done (dcl: Wrong path in /etc/dcl/apache.conf)

Your message dated Wed, 22 Mar 2006 14:50:01 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#134453: marked as done (gcombust minor bug)

Your message dated Wed, 22 Mar 2006 14:57:08 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#301306: marked as done (gkdial: Typos in err msgs)

Your message dated Wed, 22 Mar 2006 15:01:02 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#282844: marked as done (gcombust crashes on copying audio CDs)

Your message dated Wed, 22 Mar 2006 14:57:08 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#351111: marked as done (Please stop building the modules for python2.1/python2.2)

Your message dated Wed, 22 Mar 2006 14:47:37 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#222764: marked as done (DCL new version attachment trouble)

Your message dated Wed, 22 Mar 2006 14:50:01 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#323175: marked as done (rawrec: fails with "BUG: pthread_create failed:")

Your message dated Wed, 22 Mar 2006 14:53:09 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#167562: marked as done (rawrec segfaults)

Your message dated Wed, 22 Mar 2006 14:53:09 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#128714: marked as done (gcombust inhibits mkisofs's error messages!)

Your message dated Wed, 22 Mar 2006 14:57:08 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#356098: marked as done (FTBFS with G++ 4.1: extra qualification)

Your message dated Wed, 22 Mar 2006 14:51:41 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#263456: marked as done (dcl: install does not work AND there is no doc -> UNUSABLE)

Your message dated Wed, 22 Mar 2006 14:50:01 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#245877: marked as done (gkdial fails to call right provider if name contains space.)

Your message dated Wed, 22 Mar 2006 15:01:02 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#247074: marked as done (gkdial: Should have command line opt to start dialing immediately)

Your message dated Wed, 22 Mar 2006 15:01:02 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#225760: marked as done (rawrec: rawplay should set a supported sound format by default)

Your message dated Wed, 22 Mar 2006 14:53:09 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#234256: marked as done (gcombust: Reports success on cdrecord failure)

Your message dated Wed, 22 Mar 2006 14:57:08 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#131038: marked as done (gcombust: Drives that "needs to reload the media" are unuseable)

Your message dated Wed, 22 Mar 2006 14:57:08 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#139486: marked as done (gcombust: Wishlist: gcombust shuould include more info on the output window)

Your message dated Wed, 22 Mar 2006 14:57:08 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#299939: marked as done (gkdial: Double-click on "Disconnect" causes a crash)

Your message dated Wed, 22 Mar 2006 15:01:02 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#273966: marked as done (gkdial: GkDial never show connected)

Your message dated Wed, 22 Mar 2006 15:01:02 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#217938: marked as done (gkdial: using of device different from /dev/modem)

Your message dated Wed, 22 Mar 2006 15:01:02 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#193251: marked as done (gcombust: cant calculate size)

Your message dated Wed, 22 Mar 2006 14:57:08 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#291675: marked as done (gcombust: Interface size grows horizontally after one burn with cdrecord-prodvd)

Your message dated Wed, 22 Mar 2006 14:57:08 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#301302: marked as done (gkdial: Seems to abuse dh_install)

Your message dated Wed, 22 Mar 2006 15:01:02 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#182519: marked as done (dcl: Grant permissions for postgres not updated)

Your message dated Wed, 22 Mar 2006 14:50:01 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#289298: marked as done ([EMAIL PROTECTED]: gkdial override disparity])

Your message dated Wed, 22 Mar 2006 15:01:02 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 t

Bug#324607: fixed

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: memprof | 0.5.1-12 | source, i386 Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s)

Bug#315340: fixed

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: kbear | 2.1.1-13 | source, alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc Note that the package(s) have simply been removed from the tag database and may (o

Bug#285735: fixed

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: kmatplot | 0.4-8 | source, m68k kmatplot | 0.4-8+b1 | alpha, arm, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc Note that the package(s) have simply been removed from th

Bug#288216: fixed

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: soundgrab |0.9.0-2 | source, all Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) w

Bug#279526: fixed

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: icecast-client |1.4.0-6 | source, alpha, amd64, arm, hppa, hurd-i386, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc Note that the package(s) have simply been removed from the t

Bug#287992: fixed

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: gkdial | 1:1.8.0-4 | source, alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc gkdial-gnome | 1:1.8.0-4 | alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powe

Bug#305462: fixed

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: cscvs | 1.0pre25.patch.79-4 | source, all Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The pac

Bug#288267: fixed

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: gcombust | 0.1.55-2 | source, alpha, amd64, arm, hppa, hurd-i386, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc Note that the package(s) have simply been removed from the tag d

Bug#288215: fixed

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: rawrec | 0.9.98-3 | source, alpha, amd64, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc Note that the package(s) have simply been removed from the tag database and

Bug#275774: fixed

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: oonsoo | 1.2-9 | source, alpha, amd64, arm, hppa, hurd-i386, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc Note that the package(s) have simply been removed from the tag d

Bug#247231: fixed

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: dcl | 1:0.9.4.4-2 | source, all Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s)

Bug#264695: fixed

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: python-bsddb3 |3.3.0-6 | source, alpha, arm, hppa, hurd-i386, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc python-bsddb3-doc |3.3.0-6 | alpha, arm, hppa, hurd-i386, i386, i

sfront_0.87-2_i386.changes ACCEPTED

Accepted: sfront_0.87-2.diff.gz to pool/main/s/sfront/sfront_0.87-2.diff.gz sfront_0.87-2.dsc to pool/main/s/sfront/sfront_0.87-2.dsc sfront_0.87-2_i386.deb to pool/main/s/sfront/sfront_0.87-2_i386.deb Announcing to debian-devel-changes@lists.debian.org Thank you for your contribution to D

Processing of sfront_0.87-2_i386.changes

sfront_0.87-2_i386.changes uploaded successfully to localhost along with the files: sfront_0.87-2.dsc sfront_0.87-2.diff.gz sfront_0.87-2_i386.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [

  1   2   >