Bug#538542: Please rebuild against libmysqlclient16 from MySQL-5.1

[Julien BLACHE]

Christian Hammers  wrote:

Hi,

> MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
> Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
> the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
> upload a rebuilded version of your package.

FYI, OpenSER will be replaced by Kamailio once it gets out of NEW. I
don't think it'll be worth doing a source upload of OpenSER to fix
this bug.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer -  
 
 Public key available on  - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#537758: Adopting trac-mercurial

[Christoph Egger]

owner 537758 !
retitle 537758 ITA: trac-mercurial -- Mercurial version control backend for Trac
kthxbye

Hi!

I'm using trac + mercurial + this plugin in production an plan
continuing to do so. Because of this I'll adopt this package and
(probably) to collab-maint.

Thanks for your work on trac-mercurial

Christoph Egger

-- 
/"\  ASCII Ribbon : GPG-Key ID: 0x0372275D
\ /Campaign   : GPG 4096R : 0xD49AE731
 X   against HTML : Debian NM
/ \   in eMails   : http://www.debian.org/

http://www.christoph-egger.org/


signature.asc
Description: Digital signature

Processed: Adopting trac-mercurial

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> owner 537758 !
Bug #537758 {Done: John Wright } [trac-mercurial] 
trac-mercurial doesn't work with latest mercurial 1.3
Owner recorded as Christoph Egger .
> retitle 537758 ITA: trac-mercurial -- Mercurial version control backend for 
> Trac
Bug #537758 {Done: John Wright } [trac-mercurial] 
trac-mercurial doesn't work with latest mercurial 1.3
Changed Bug title to 'ITA: trac-mercurial -- Mercurial version control backend 
for Trac' from 'trac-mercurial doesn't work with latest mercurial 1.3'
> kthxbye
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#537758: Adopting trac-mercurial

[John Wright]

Hi Christoph,

On Sun, Jul 26, 2009 at 10:07:13AM +0200, Christoph Egger wrote:
> owner 537758 !
> retitle 537758 ITA: trac-mercurial -- Mercurial version control backend for 
> Trac
> kthxbye
> 
> Hi!
> 
>   I'm using trac + mercurial + this plugin in production an plan
> continuing to do so. Because of this I'll adopt this package and
> (probably) to collab-maint.

Great!  I'm glad it will be getting the attention it deserves. :)

-- 
John Wright 



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: SQLite3 bus errors on sparc reported to upstream

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 524140 http://www.sqlite.org/cvstrac/tktview?tn=3990
Bug #524140 [libsqlite3-0] libsqlite3-0: [sparc] triggers bus errors in 
libpthread from monotone testsuite
Set Bug forwarded-to-address to 'http://www.sqlite.org/cvstrac/tktview?tn=3990'.
> forwarded 538396 http://www.sqlite.org/cvstrac/tktview?tn=3990
Bug #538396 [libsqlite3-0] libsqlite3-0: Sqlite triggers bus error in apr-util 
test suite on sparc causing FTBFS
Set Bug forwarded-to-address to 'http://www.sqlite.org/cvstrac/tktview?tn=3990'.
>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#538252: pdftk can not be installed.

[Fabrice Lorrain]

Package: pdftk
Severity: normal

Hello,

I confirm this pb. pdftk is uninstalable in current sid because of
broken dependancy.

@+,

 Fab 

$ LANG=C sudo aptitude install pdftk
..
The following packages are BROKEN:
  pdftk 
0 packages upgraded, 1 newly installed, 0 to remove and 54 not upgraded.
Need to get 1048kB of archives. After unpacking 3031kB will be used.
The following packages have unmet dependencies:
  pdftk: Depends: libgcj8-1 (>= 4.2.1) but it is not installable
Unable to resolve dependencies!  Giving up...
The following packages are BROKEN:
  pdftk 
0 packages upgraded, 1 newly installed, 0 to remove and 54 not upgraded.
Need to get 1048kB of archives. After unpacking 3031kB will be used.
aptitude failed to find a solution to these dependencies.  You can solve them 
yourself by hand or type 'n' to quit.
The following packages have unmet dependencies:
  pdftk: Depends: libgcj8-1 (>= 4.2.1) but it is not installable
Resolve these dependencies by hand? [N/+/-/_/:/?] 
Abort.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (990, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-1-686 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages pdftk depends on:
ii  libc6 2.9-21 GNU C Library: Shared libraries
ii  libgcc1   1:4.4.1-1  GCC support library
pn  libgcj8-1  (no description available)
ii  libstdc++64.4.1-1The GNU Standard C++ Library v3

pdftk recommends no packages.

Versions of packages pdftk suggests:
ii  xpdf-utils   3.02-1.4+lenny1 Portable Document Format (PDF) sui



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#535092: iceweasel fails to start on sparc, bus error

[Aleksi Suhonen]

Mike Hommey wrote:

On Mon, Jun 29, 2009 at 07:30:11PM +0300, Aleksi Suhonen wrote:

Package: iceweasel
Version: 3.0.11-1
Severity: grave
Justification: renders package unusable



iceweasel fails completely to start on sparc.



Can you try again with a more recent libc ?


iceweasel 3.0.12-1 + libc6 2.9-20 seems to work now. Thanks.

--
Aleksi Suhonen / Axu TM Oy
Internetworking Consulting
Cellular: +358 45 670 2048
World Wide Web: www.axu.tm



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: tagging 537586

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # Automatically generated email from bts, devscripts version 2.10.35lenny3
> tags 537586 + pending
Bug #537586 [eglibc] fdatasync should be a cancellation point
Added tag(s) pending.
>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#538460: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538460,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538460: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538460
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cherokee
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538477: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538477,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538477: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538477
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ulogd
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538497: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538497,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538497: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538497
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538475: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538475,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538475: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538475
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: shibboleth-sp
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538456: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538456,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538456: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538456
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dsyslog
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538467: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538467,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538467: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538467
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-mysqldb
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538494: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538494,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538494: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qt4-x11
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538495: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538495,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538495: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538495
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lua-sql
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538464: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538464,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538464: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538464
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpreludedb
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538505: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538505,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538505: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538505
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tntdb
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538508: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538508,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538508: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538508
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libdbi-drivers
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538488: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538488,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538488: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538488
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mod-auth-mysql
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538492: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538492,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538492: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538492
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: poco
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#537586: marked as done (fdatasync should be a cancellation point)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:59:49 +0200
with message-id <20090726095949.ga13...@volta.aurel32.net>
and subject line Re: Bug#537586: binutils: breaks function cancellation on armel
has caused the Debian Bug report #537586,
regarding fdatasync should be a cancellation point
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
537586: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=537586
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: binutils
Version: 2.19.51.20090714-1
Severity: important

It took me a while to understand the problem. tst-cancelx4 from the GNU 
libc testsuite, when linked with binutils 2.19.51.20090704-1 or
2.19.51.20090714-1 fails with:

| cleanup handler not called for 'fdatasync'

The problem does not occur with the exact same packages but binutils
downgraded to squeeze's version (2.19.1-1).

Please find below the diff of the assembly dumps.

--- tst-cancelx4.binutils-squeeze.dump  2009-07-19 17:06:17.0 +0200
+++ tst-cancelx4.binutils-sid.dump  2009-07-19 17:06:23.0 +0200
@@ -1,15 +1,15 @@
 
-tst-cancelx4.binutils-squeeze: file format elf32-littlearm
+tst-cancelx4.binutils-sid: file format elf32-littlearm
 
 Program Header:
 0x7001 off0x21c4 vaddr 0xa1c4 paddr 0xa1c4 align 2**2
- filesz 0x0040 memsz 0x0040 flags r--
+ filesz 0x0048 memsz 0x0048 flags r--
 PHDR off0x0034 vaddr 0x8034 paddr 0x8034 align 2**2
  filesz 0x0120 memsz 0x0120 flags r-x
   INTERP off0x0154 vaddr 0x8154 paddr 0x8154 align 2**0
  filesz 0x0013 memsz 0x0013 flags r--
 LOAD off0x vaddr 0x8000 paddr 0x8000 align 2**15
- filesz 0x2208 memsz 0x2208 flags r-x
+ filesz 0x2210 memsz 0x2210 flags r-x
 LOAD off0x2ef4 vaddr 0x00012ef4 paddr 0x00012ef4 align 2**15
  filesz 0x0220 memsz 0x0268 flags rw-
  DYNAMIC off0x2f00 vaddr 0x00012f00 paddr 0x00012f00 align 2**2
@@ -87,11 +87,11 @@
 818c:  0014.word   0x0014
 8190:  0003.word   0x0003
 8194:  00554e47.word   0x00554e47
-8198:  75f26671ldrbvc  r6, [r2, #1649]!
-819c:  314e1444cmpcc   lr, r4, asr #8
-81a0:  c6e16a24strbtgt r6, [r1], r4, lsr #20
-81a4:  7a992aa6bvc fe652c44 <__bss_end__+0xfe63fae8>
-81a8:  a5126950ldrge   r6, [r2, #-2384]
+8198:  9f5d28cesvcls   0x005d28ce
+819c:  ec6c323fsfm f3, 2, [ip], #-252
+81a0:  70bbdb75adcsvc  sp, fp, r5, ror fp
+81a4:  f0334c2fundefined instruction 0xf0334c2f
+81a8:  03726112cmneq   r2, #-2147483644; 0x8004
 Disassembly of section .hash:
 
 81ac <.hash>:
@@ -2216,10 +2216,12 @@
 a1f8:  8003acb0strhhi  sl, [r3], -r0
 a1fc:  7a28svcvc   0x00fffa28
 a200:  80a8b0b0.word   0x80a8b0b0
+a204:  7a5csvcvc   0x00fffa5c
+a208:  0001andeq   r0, r0, r1
 Disassembly of section .eh_frame:
 
-a204 <__FRAME_END__>:
-a204:  .word   0x
+a20c <__FRAME_END__>:
+a20c:  .word   0x
 Disassembly of section .init_array:
 
 00012ef4 <__frame_dummy_init_array_entry>:
@@ -2405,6 +2407,22 @@
 
 00013158 :
13158:  .word   0x
+Disassembly of section .ARM.attributes:
+
+ <.ARM.attributes>:
+   0:  2d41andeq   r2, r0, r1, asr #26
+   4:  61656100cmnvs   r5, r0, lsl #2
+   8:  01006962tsteq   r0, r2, ror #18
+   c:  0023andeq   r0, r0, r3, lsr #32
+  10:  4d524105ldfmie  f4, [r2, #-20]
+  14:  4d445439cfstrdmimvd5, [r4, #-228]
+  18:  02060049andeq   r0, r6, #73 ; 0x49
+  1c:  01090108tsteq   r9, r8, lsl #2
+  20:  01140412tsteq   r4, r2, lsl r4
+  24:  03170115tsteq   r7, #1073741829 ; 0x4005
+  28:  021a0118andseq  r0, sl, #6  ; 0x6
+  2c:  Address 0x002c is out of bounds.
+
 Disassembly of section .comment:
 
  <.comment>:
@@ -5931,19 +5949,3 @@
  150:  9d24andeq   r9, r0, r4, lsr #26
  154:  9d30andeq   r9, r0, r0, lsr sp
...
-Disassembly of section .ARM.attributes:
-
- <.ARM.attributes>:
-   0:  2d41andeq   r2, r0, r1, asr #26
-   4:  61656100cmnvs   r5, r0, ls

Bug#538486: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538486,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538486: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538486
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: muddleftpd
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538483: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538483,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538483: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538483
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libyada
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538452: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538452,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538452: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538452
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bacula
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538473: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538473,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538473: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538473
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gmyth
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538514: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538514,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538514: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538514
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lcd4linux
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538454: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538454,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538454: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538454
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: amarok
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538531: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538531,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538531: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538531
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qt-x11-free
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538474: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538474,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538474: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538474
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gdal
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538490: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538490,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538490: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538490
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pdns
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538515: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538515,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538515: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538515
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mysql++
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538496: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538496,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538496: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538496
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pennmush
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538519: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538519,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538519: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538519
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mysql-ruby
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538528: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538528,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538528: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538528
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ratbox-services
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538469: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538469,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538469: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538469
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: hk-classes
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538523: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538523,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538523: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538523
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pike7.6
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538504: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538504,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538504: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538504
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: slurm-llnl
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#536998: marked as done (gnunet-fuse: FTBFS: directory.c:139: error: too few arguments to function 'GNUNET_ECRS_directory_list_contents')

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 09:47:57 +
with message-id 
and subject line Bug#536998: fixed in gnunet-fuse 0.8.0c-1
has caused the Debian Bug report #536998,
regarding gnunet-fuse: FTBFS: directory.c:139: error: too few arguments to 
function 'GNUNET_ECRS_directory_list_contents'
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
536998: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=536998
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnunet-fuse
Version: 0.8.0-4
Severity: serious
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20090713 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> gcc -DHAVE_CONFIG_H -I.  -DFUSE_USE_VERSION=26 -D_REENTRANT -I/usr/include   
> -g -O2 -Wall -W -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include   
> -D_FILE_OFFSET_BITS=64 -I/usr/include/fuse   -MT gnunet_fs-directory.o -MD 
> -MP -MF .deps/gnunet_fs-directory.Tpo -c -o gnunet_fs-directory.o `test -f 
> 'directory.c' || echo './'`directory.c
> directory.c: In function 'directory_cache_locked':
> directory.c:139: warning: passing argument 4 of 
> 'GNUNET_ECRS_directory_list_contents' from incompatible pointer type
> directory.c:139: warning: passing argument 5 of 
> 'GNUNET_ECRS_directory_list_contents' from incompatible pointer type
> directory.c:139: warning: passing argument 6 of 
> 'GNUNET_ECRS_directory_list_contents' from incompatible pointer type
> directory.c:139: error: too few arguments to function 
> 'GNUNET_ECRS_directory_list_contents'
> directory.c: In function 'gn_directory_upload_locked':
> directory.c:382: warning: passing argument 3 of 
> 'GNUNET_ECRS_directory_create' from incompatible pointer type
> directory.c:410: warning: passing argument 8 of 'GNUNET_ECRS_file_upload' 
> from incompatible pointer type
> make[2]: *** [gnunet_fs-directory.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2009/07/13/gnunet-fuse_0.8.0-4_lsid64.buildlog

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.

-- 
| Lucas Nussbaum
| lu...@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |


--- End Message ---
--- Begin Message ---
Source: gnunet-fuse
Source-Version: 0.8.0c-1

We believe that the bug you reported is fixed in the latest version of
gnunet-fuse, which is due to be installed in the Debian FTP archive:

gnunet-fuse_0.8.0c-1.diff.gz
  to pool/main/g/gnunet-fuse/gnunet-fuse_0.8.0c-1.diff.gz
gnunet-fuse_0.8.0c-1.dsc
  to pool/main/g/gnunet-fuse/gnunet-fuse_0.8.0c-1.dsc
gnunet-fuse_0.8.0c-1_i386.deb
  to pool/main/g/gnunet-fuse/gnunet-fuse_0.8.0c-1_i386.deb
gnunet-fuse_0.8.0c.orig.tar.gz
  to pool/main/g/gnunet-fuse/gnunet-fuse_0.8.0c.orig.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 536...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Baumann  (supplier of updated gnunet-fuse package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sun, 26 Jul 2009 11:33:04 +0200
Source: gnunet-fuse
Binary: gnunet-fuse
Architecture: source i386
Version: 0.8.0c-1
Distribution: unstable
Urgency: low
Maintainer: Daniel Baumann 
Changed-By: Daniel Baumann 
Description: 
 gnunet-fuse - secure, trust-based peer-to-peer framework (fuse filesystem clien
Closes: 536998
Changes: 
 gnunet-fuse (0.8.0c-1) unstable; urgency=low
 .
   * Using correct rfc-2822 date formats in changelog.
   * Tidy rules file.
   * Upgrading package to standards 3.8.1.
   * Merging upstream version 0.8.0c:
 - fixes FTBFS with newer fuse (Closes: #536998).
   * Updating year in copyright file.
   * Updating version and date in manpage header.
   * Tightening versioned build-depends on gnunet.
   * Upgrading package to standards version 3.8.2.
Checksums-Sha1: 
 6931e30204098ab712b97509162588c78f424dfd 1185 gnunet-fus

Bug#538481: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538481,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538481: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538481
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mapserver
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538516: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538516,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538516: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: proftpd-dfsg
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538491: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538491,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538491: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538491
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: perdition
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538521: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538521,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538521: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538521
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: soci
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538478: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538478,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538478: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538478
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: snort
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538461: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538461,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538461: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538461
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: asterisk-addons
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#537637: htmldoc: buffer overflow in util.cxx's set_page_size()

[Nico Golde]

Hi,
* Michael S. Gilbert  [2009-07-20 08:41]:
> hello, a security advisory has been issued for htmldoc [0].  patches
> available from gentoo [1].  please coordinate with the security team to
> prepare updates for the stable releases.  thank you.

As I mentioned in http://www.openwall.com/lists/oss-security/2009/07/25/3
this patch is incomplete, two other similar issues exist in 
the code.

Cheers
Nico
-- 
Nico Golde - http://www.ngolde.de - n...@jabber.ccc.de - GPG: 0xA0A0
For security reasons, all text in this mail is double-rot13 encrypted.


pgposw90NmalC.pgp
Description: PGP signature

Bug#538530: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538530,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538530: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538530
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: spl
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538500: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538500,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538500: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538500
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: root-system
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538476: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538476,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538476: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538476
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: redland
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538459: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538459,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538459: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cl-sql
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538538: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538538,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538538: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538538
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dspam
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538539: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538539,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538539: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538539
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: exim4
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538457: Please rebuild against libmysqlclient16 from MySQL-5.1

[Michal Čihař]

Hi

Dne Sat, 25 Jul 2009 23:24:55 +0200 (CEST)
Christian Hammers  napsal(a):

> Package: gammu
> Severity: serious
> User: pkg-mysql-ma...@lists.alioth.debian.org
> Usertag: libmysqlclient16
> 
> Hello
> 
> MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
> Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
> the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
> upload a rebuilded version of your package.

Well it looks like I already messed up last upload to unstable and I
kept libmysqlclient-dev build dep from experimental, so it is already
there. But for obvious reasons the package did not build.

-- 
Michal Čihař | http://cihar.com | http://blog.cihar.com


signature.asc
Description: PGP signature

Bug#538541: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538541,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538541: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538541
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnokii
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538540: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538540,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538540: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538540
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sqlxx
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538520: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538520,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538520: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538520
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ndoutils
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538493: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538493,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538493: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538493
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postfix
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538489: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538489,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538489: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538489
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nufw
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538458: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538458,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538458: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538458
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: courier-authlib
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538503: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538503,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538503: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538503
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sqlrelay
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#521238: stardic: Bus error on AMD64

[LIU Qi]

On Sat, Jul 25, 2009 at 12:50:20PM +0200, Andrew Lee wrote:
 > 
 > I uploaded stardict 3.0.1-6(added a pseudo binary package named stardic
 > to help users transition), but stardict package doesn't content any
 > dictionary data.
 > 
 > So now this bug is pending for your stardict-dictionary package upload.
 > Let me know if you need help.
I am sorry for the late reply. I am getting a little busy these days. I
will finish this package in the next two days. Thanks.

ps: Congratulations to you on being the official DD.

Regards,
Qi
-- 
 LIU Qi

 liuq...@gmail.com
 li...@printk.org

 PGP Key fingerprint:
  A8C0 860C D8A9 D6FC 551F
  6E2C A4AB 763B 00EC 886F



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#538455: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538455,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538455: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538455
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dovecot
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538482: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538482,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538482: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538482
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libdataobjects-mysql-ruby
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538487: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538487,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538487: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538487
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nagios-plugins
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538465: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538465,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538465: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: myodbc
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538470: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538470,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538470: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538470
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dbmail
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538472: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538472,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538472: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538472
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gambas2
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538529: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538529,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538529: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mysql-gui-tools
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538506: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538506,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538506: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538506
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: totem
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538517: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538517,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538517: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538517
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pure-ftpd
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538525: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538525,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538525: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538525
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rmysql
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538498: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538498,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538498: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538498
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lighttpd
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538522: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538522,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538522: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538522
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnade
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538462: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538462,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538462: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538462
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apr-util
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538457: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538457,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538457: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538457
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gammu
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538479: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538479,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538479: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538479
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libapache-mod-log-sql
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538453: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538453,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538453: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538453
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cvm
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538502: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538502,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538502: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538502
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sbnc
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538485: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538485,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538485: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538485
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mediatomb
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538480: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538480,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538480: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538480
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kannel
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538463: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538463,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538463: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538463
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: freeradius
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538484: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538484,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538484: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538484
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: zabbix
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538527: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538527,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538527: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538527
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wzdftpd
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538526: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538526,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538526: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mnogosearch
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538542: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538542,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538542: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538542
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openser
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538466: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538466,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538466: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538466
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pam-mysql
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538518: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538518,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538518: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ser
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538501: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538501,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538501: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538501
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rsyslog
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538499: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538499,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538499: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538499
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mysql-ocaml
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538509: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538509,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538509: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538509
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgda3
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538507: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538507,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538507: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538507
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: yate
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538471: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538471,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538471: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538471
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cyrus-sasl2
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Bug#538524: marked as done (Please rebuild against libmysqlclient16 from MySQL-5.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 11:58:51 +0200 (CEST)
with message-id <20090726095851.437552b...@lathspell.homeip.net>
and subject line Can be done via binary NMU
has caused the Debian Bug report #538524,
regarding Please rebuild against libmysqlclient16 from MySQL-5.1
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538524: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538524
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mailutils
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient16

Hello

MySQL 5.1 has just been uploaded and will replace the existing MySQL 5.0.
Once you see libmysqlclient-dev (5.1.36-3) in unstable, please replace
the build dependencies to libmysqlclient15-dev to libmysqlclient-dev and
upload a rebuilded version of your package.

thanks,

-christian- 


--- End Message ---
--- Begin Message ---
Hello

I was suggested to handle this transition via requested binary NMUs
as we already provide a libmysqlclient15-dev transition package.
So no sourcefull uploads are needed (although you could replace
the build-dep by libmysqlclient-dev somewhen in the next months).

bye,

-christian-

--- End Message ---

Processed: Re: Bug#538226: squid: Error Pages moved

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 538226 squid-langpack
Bug #538226 [squid] squid: Error Pages moved
Bug reassigned from package 'squid' to 'squid-langpack'.
Bug #538226 [squid-langpack] squid: Error Pages moved
Bug No longer marked as found in versions squid/2.7.STABLE6-2.
Bug #538226 [squid-langpack] squid: Error Pages moved
Ignoring request to alter fixed versions of bug #538226 to the same values 
previously set
> severity 538226 normal
Bug #538226 [squid-langpack] squid: Error Pages moved
Severity set to 'normal' from 'grave'

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#538226: squid: Error Pages moved

[Luigi Gangitano]

reassign 538226 squid-langpack
severity 538226 normal
thanks

Hi Ralf,
as noted in README.Debian in 2.7.STABLE6-2, error pages have been  
moved to a different package (squid-langpack) which is in common  
between squid and squid3 and updated indipendently upstream. With this  
change directory for languages are names with ISO codes. Instructions  
on needed configuration fixes are in README.Debian already.


The next version of squid-langpack will ship compatibility links for  
old-style configurations.


Regards,

L

--
Luigi Gangitano --  -- 
GPG: 1024D/924C0C26: 12F8 9C03 89D3 DB4A 9972  C24A F19B A618 924C 0C26





--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#535305: How do I revert to the old file setup and restart the controller?

[Vincent Liard]

Hi David,

If I'm not mistaken, to apply
Frederik's patch, you just have to run: "sudo
/usr/share/common-lisp/source/common-lisp-controller/common-lisp-controller.postinst
configure"

(I believe that's what worked for me.)

Vincent



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#537323: marked as done (Perhaps a critical mistake in the example for chaining with Tor?)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 12:28:32 +0200
with message-id <20090726102832.gf6...@dinghy.sail.spinnaker.de>
and subject line Re: Bug#537323: Perhaps a critical mistake in the example for 
chaining with Tor?
has caused the Debian Bug report #537323,
regarding Perhaps a critical mistake in the example for chaining with Tor?
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
537323: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=537323
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: privoxy
Version: 3.0.13-1
Justification: user security hole
Severity: grave
Tags: security

Hi.

Since the last release or so, the config template gives this as an  
example for chaining privoxy with Tor:

#  To chain Privoxy and Tor, both running on the same system,
#  you would use something like:
#
#forward-socks5   /   127.0.0.1:9050 .

AFAIK, it was always the case, that with socks5, DNS resolution  
happened locally and not via the proxy (which was the reason one  
should use socks4a).

Has this changed?

As this change could render Tor useless,.. and I found no docs whether  
the above has change in the meantime... I've marked this bug as  
security critical.

Feel free to close, if I'm wrong :-)


Thanks,
Chris.


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-heisenberg (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages privoxy depends on:
ii  adduser3.110 add and remove users and groups
ii  libc6  2.9-20GNU C Library: Shared libraries
ii  libpcre3   7.8-2 Perl 5 Compatible Regular  
Expressi

ii  logrotate  3.7.7-3   Log rotation utility
ii  lsb-base   3.2-22Linux Standard Base 3.2  
init scrip

ii  perl   5.10.0-24 Larry Wall's Practical Extraction
ii  zlib1g 1:1.2.3.3.dfsg-14 compression library - runtime

Versions of packages privoxy recommends:
ii  doc-base  0.9.3  utilities to manage  
online documen


privoxy suggests no packages.

-- no debconf information



This message was sent using IMP, the Internet Messaging Program.



--- End Message ---
--- Begin Message ---
Christoph Anton Mitterer schrieb am Freitag, den 17. Juli 2009:

> Package: privoxy
> Version: 3.0.13-1
> Justification: user security hole
> Severity: grave
> Tags: security

> Since the last release or so, the config template gives this as an  
> example for chaining privoxy with Tor:
> #  To chain Privoxy and Tor, both running on the same system,
> #  you would use something like:
> #
> #forward-socks5   /   127.0.0.1:9050 .
>
> AFAIK, it was always the case, that with socks5, DNS resolution happened 
> locally and not via the proxy (which was the reason one should use 
> socks4a).
> Has this changed?

According to the privoxy documentation this problem only occurs with
socks4, while socks4a and socks5 tunnel DNS:

| 7.5.2. forward-socks4, forward-socks4a and forward-socks5
| [...]
| The difference between forward-socks4 and forward-socks4a  is that in
| the SOCKS 4A protocol, the DNS resolution of the target hostname
| happens on the SOCKS server, while in SOCKS 4 it happens locally. 
|
| With forward-socks5 the DNS resolution will happen on the remote
| server as well. 

A short test on my local machine shows that this works as documented
using wget, while I noticed some trouble with Firefox when ShowIP is
enabled (so switch of ShowIP to be really invisible!). 
Except this only socks4a does local DNS requests.

> As this change could render Tor useless,.. and I found no docs whether  
> the above has change in the meantime... I've marked this bug as security 
> critical.
> Feel free to close, if I'm wrong :-)

As far as I can see you are wrong, so I do so.

Tscho

Roland

--- End Message ---

Bug#538233: Output file diff - the cause

[Jeffrey Ratcliffe]

2009/7/26 Robert Kawecki :
> I've generated PDF files from the same source JPEG image (exact same settings:
> JPEG 95%, downsample to 300DPI) on 2 different versions of gscan2pdf: 0.9.29
> and 0.9.27 (from Ubuntu 9.04 on my laptop).

Thanks for all your investigations.

As the PDF creation code hasn't been changed between 0.9.27 and
0.9.29, it must be PDF::API2. 0.72 seems to be OK, and 0.73 not.

I'll do some testing.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#535092: marked as done (iceweasel fails to start on sparc, bus error)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2009 12:56:17 +0200
with message-id <20090726105617.ga30...@glandium.org>
and subject line Re: Bug#535092: iceweasel fails to start on sparc, bus error
has caused the Debian Bug report #535092,
regarding iceweasel fails to start on sparc, bus error
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
535092: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=535092
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: iceweasel
Version: 3.0.11-1
Severity: grave
Justification: renders package unusable


iceweasel fails completely to start on sparc. An identical installation
on i386 works just fine. I made a new clean debian installation using
the newest unstable netboot installation image I could find to test this
in case my pre-lenny-unstable environment was somehow broken, but the
clean debian/unstable (this host) exhibits the same problem.

I don't have any plugins or similar installed, because I can't start the
browser to be able to add them.

iceweasel-dbg doesn't reveal much:

GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "sparc-linux-gnu"...
(no debugging symbols found)
(gdb) set pagination off 
(gdb) run 
Starting program: /usr/lib/iceweasel/firefox-bin -a iceweasel -safe-mode
[Thread debugging using libthread_db enabled]
Error while reading shared library symbols:
Cannot find new threads: debugger service failed
Cannot find new threads: debugger service failed
(gdb) bt full 
#0  0xf7f58f44 in *__GI__dl_debug_state () at dl-debug.c:77
No locals.
#1  0xf7f5cd14 in dl_open_worker (a=0xfff36218) at dl-open.c:366
file = 0xfff36538 "/usr/lib/iceweasel/xulrunner/libxul.so"
mode = -2147483391
new = (struct link_map *) 0x28b08
lazy = 0
i = 68
any_tls = 
call_map = 
dst = 0x0
l = 
__PRETTY_FUNCTION__ = "dl_open_worker"
#2  0xf7f580b8 in _dl_catch_error (objname=0xfff36240, errstring=0xfff3623c, 
mallocedp=0xfff36247, operate=0xf7f5cac0 , args=0xfff36218) at 
dl-error.c:178
errcode = 0
old = (struct catch * volatile) 0xfff36338
c = {objname = 0xfff36a2c "ulrunner", errstring = 0x0, malloced = 
false, env = {{__jmpbuf = {-827232, -826952, -134905712}, __mask_was_saved = 0, 
__saved_mask = {__val = {4157744864, 0 , 21, 21, 4294142176, 
0, 0, 0, 0, 4158738432, 4294142024, 93378, 21, 0, 4294967295, 32, 4294140360, 
4157561732, 0, 0, 0}
catchp = (struct catch ** const) 0xf7f7ae40
#3  0xf7f5c544 in _dl_open (file=0xfff36538 
"/usr/lib/iceweasel/xulrunner/libxul.so", mode=-2147483391, 
caller_dlopen=0x16630, nsid=-2, argc=4, argv=0xfff37904, env=0xfff37918) at 
dl-open.c:596
args = {file = 0xfff36538 "/usr/lib/iceweasel/xulrunner/libxul.so", 
mode = -2147483391, caller_dlopen = 0x16630, caller_dl_open = 0xf7f30e28, map = 
0x28b08, nsid = 0, argc = 4, argv = 0xfff37904, env = 0xfff37918}
objname = 
errstring = 
malloced = 
errcode = 
__PRETTY_FUNCTION__ = "_dl_open"
#4  0xf7f30e28 in dlopen_doit (a=0xfff364b8) at dlopen.c:67
No locals.
#5  0xf7f580b8 in _dl_catch_error (objname=0xf7f441d8, errstring=0xf7f441dc, 
mallocedp=0xf7f441d4, operate=0xf7f30da0 , args=0xfff364b8) at 
dl-error.c:178
errcode = 0
old = (struct catch * volatile) 0x0
c = {objname = 0x0, errstring = 0x0, malloced = false, env = {{__jmpbuf 
= {-826672, -826392, -134905712}, __mask_was_saved = 0, __saved_mask = {__val = 
{0, 0, 0, 0, 4294140892, 4222451713, 4294141240, 4294141240, 0, 4160154512, 1, 
0, 1, 4294142235, 0 , 4159898604}
catchp = (struct catch ** const) 0xf7f7ae40
#6  0xf7f31448 in _dlerror_run (operate=0xf7f30da0 , 
args=0xfff364b8) at dlerror.c:164
result = (struct dl_action_result *) 0xf7f441cc
#7  0xf7f30d70 in __dlopen (file=0xfff36538 
"/usr/lib/iceweasel/xulrunner/libxul.so", mode=257) at dlopen.c:88
args = {file = 0xfff36538 "/usr/lib/iceweasel/xulrunner/libxul.so", 
mode = 257, new = 0x0, caller = 0x16630}
#8  0x00016630 in ?? ()
No symbol table info available.
#9  0x00016630 in ?? ()
No symbol table info available.
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) quit
The program is running.  Exit anyway? (y or n) y


-- System Information:

Bug#527068: unowned files after purge (policy 6.8)

[Holger Levsen]

Hi,

On Freitag, 24. Juli 2009, Felix Zielcke wrote:
> Maybe we could add a debconf prompt on purge to clear all grub2 files
> from /boot/grub.

I think that would be sensible, then openldap packages do the same. (ask to 
purge the ldap database on purge and default to "no".)

I dont think this approach is sensible for all packages (=purge should 
purge..!), but for some it is.

> But I think that should default to no and so piuparts would still be not
> happy.

piuparts can be made happy by changing the piuparts source to ignore those 
files. this is done for quite some files.


regards,
Holger



signature.asc
Description: This is a digitally signed message part.