plr REMOVED from testing

FYI: The status of the plr source package in Debian's testing distribution has changed. Previous version: 1:8.2.0.7-2 Current version: (not in testing) Hint: Package not in unstable The script that generates this mail tries to extract removal reasons from comments in the britney hint files

xgsmlib REMOVED from testing

FYI: The status of the xgsmlib source package in Debian's testing distribution has changed. Previous version: 0.2-7 Current version: (not in testing) Hint: Package not in unstable The script that generates this mail tries to extract removal reasons from comments in the britney hint files.

treecc REMOVED from testing

FYI: The status of the treecc source package in Debian's testing distribution has changed. Previous version: 0.3.8-2 Current version: (not in testing) Hint: Package not in unstable The script that generates this mail tries to extract removal reasons from comments in the britney hint files.

libapache2-mod-annodex REMOVED from testing

FYI: The status of the libapache2-mod-annodex source package in Debian's testing distribution has changed. Previous version: 0.2.2-6 Current version: (not in testing) Hint: Package not in unstable The script that generates this mail tries to extract removal reasons from comments in the bri

connect.app REMOVED from testing

FYI: The status of the connect.app source package in Debian's testing distribution has changed. Previous version: 0.1-6 Current version: (not in testing) Hint: Package not in unstable The script that generates this mail tries to extract removal reasons from comments in the britney hint fil

Bug#405884: marked as done (netcdfg-dev fails to install when /usr/doc is a symbolic link to /use/share/doc)

Your message dated Thu, 31 Jan 2008 23:02:11 + with message-id <[EMAIL PROTECTED]> and subject line Bug#405884: fixed in netcdf 1:3.6.2-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#219592: marked as done (Fortran interface not provided for netcdf)

Your message dated Thu, 31 Jan 2008 23:02:11 + with message-id <[EMAIL PROTECTED]> and subject line Bug#278739: fixed in netcdf 1:3.6.2-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#278739: marked as done (netcdfg-dev: Fortran Support?)

Your message dated Thu, 31 Jan 2008 23:02:11 + with message-id <[EMAIL PROTECTED]> and subject line Bug#219592: fixed in netcdf 1:3.6.2-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#278739: marked as done (netcdfg-dev: Fortran Support?)

Your message dated Thu, 31 Jan 2008 23:02:11 + with message-id <[EMAIL PROTECTED]> and subject line Bug#278739: fixed in netcdf 1:3.6.2-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#427639: marked as done (netcdfg-dev: why no fortran 90 support via gfortran?)

Your message dated Thu, 31 Jan 2008 23:02:11 + with message-id <[EMAIL PROTECTED]> and subject line Bug#278739: fixed in netcdf 1:3.6.2-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#427639: marked as done (netcdfg-dev: why no fortran 90 support via gfortran?)

Your message dated Thu, 31 Jan 2008 23:02:11 + with message-id <[EMAIL PROTECTED]> and subject line Bug#219592: fixed in netcdf 1:3.6.2-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#219592: marked as done (Fortran interface not provided for netcdf)

Your message dated Thu, 31 Jan 2008 23:02:11 + with message-id <[EMAIL PROTECTED]> and subject line Bug#219592: fixed in netcdf 1:3.6.2-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#463416: Does not start

On Thu, Jan 31, 2008 at 08:33:35PM +0200, Yavor Doganov wrote: > Could you please rebuild gnustep-base with debugging Sorry, that's not necessary. It seems that something bad happens earlier. Could you please run it in gdb, with --GNU-Debug=dflt? Thanks. -- To UNSUBSCRIBE, email to [EMAIL

Bug#463416: Does not start

On Thu, Jan 31, 2008 at 07:14:35PM +0100, Vincent Fourmond wrote: > Does a gnustep daemon of some kind need to be running for Shisen.app > to work correctly ? Yes, for every GNUstep app. But gdnc should start automatically if it is not running. > I'm not running GNUStep at all (but fvwm2); c

Bug#463416: Does not start

Yavor Doganov wrote: > Vincent Fourmond wrote: >> zsh: abort Shisen > >> Versions of packages shisen.app depends on: >> pn gnustep-back0.12 (no description available) >> pn gnustep-base-runtime (no description available) >> pn gnustep-gpbs

Bug#463416: Does not start

Vincent Fourmond wrote: > > zsh: abort Shisen > Versions of packages shisen.app depends on: > pn gnustep-back0.12 (no description available) > pn gnustep-base-runtime (no description available) > pn gnustep-gpbs (no description availab

Bug#463416: Does not start

On Thu, Jan 31, 2008 at 07:36:47PM +0200, Yavor Doganov wrote: > Can you show the output of Shisen --GNU-Debug=NSDistributedNotificationCenter \ --GNU-Debug=NSMessagePort Thanks. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROT

Need your help!

Hello! My name's Evgeniya. I'm from Russia, 28 years old. Please vote for my profile here: http://foreignw0men.info/?idAff=35 Thank You Very Much!!! Evgeniya -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#463416: Does not start

Package: shisen.app Version: 1.2.0-6 Severity: important Hello, shisen.app does not start on my AMD64 box: 16:09 [EMAIL PROTECTED] ~ Shisen zsh: abort Shisen As it apparently works fine on x86 boxes, it is probably an int vs long problem. Regards, Vincent -- System Inf

Bug#461256: marked as done (caudium declares relation to ttf-bitstream-vera)

Your message dated Thu, 31 Jan 2008 09:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#461256: fixed in caudium 2:1.4.9.1-5 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

caudium_1.4.9.1-5_i386.changes ACCEPTED

Accepted: caudium-dev_1.4.9.1-5_i386.deb to pool/main/c/caudium/caudium-dev_1.4.9.1-5_i386.deb caudium-modules_1.4.9.1-5_i386.deb to pool/main/c/caudium/caudium-modules_1.4.9.1-5_i386.deb caudium-perl_1.4.9.1-5_i386.deb to pool/main/c/caudium/caudium-perl_1.4.9.1-5_i386.deb caudium-pixsl_1.4

Processing of caudium_1.4.9.1-5_i386.changes

caudium_1.4.9.1-5_i386.changes uploaded successfully to localhost along with the files: caudium_1.4.9.1-5.dsc caudium_1.4.9.1-5.diff.gz caudium_1.4.9.1-5_i386.deb caudium-modules_1.4.9.1-5_i386.deb caudium-pixsl_1.4.9.1-5_i386.deb caudium-ultralog_1.4.9.1-5_i386.deb caudium-dev_1.4.9.