Bug#842288: transition: gdal

[Sebastiaan Couwenberg]

On 10/27/2016 11:58 PM, Emilio Pozuelo Monfort wrote:
> On 27/10/16 20:10, Bas Couwenberg wrote:
>> Package: release.debian.org
>> Severity: normal
>> User: release.debian@packages.debian.org
>> Usertags: transition
>>
>> Dear Release Team,
>>
>> For the Debian GIS team I'd like to transition to GDAL 2.1.2.
>>
>> Like the previous transition to GDAL 2.1.1 (#830966), there is no SONAME
>> bump, only the virtual ABI package changed to account for the C++ symbol
>> changes.
>>
>> All reverse dependencies rebuilt successfully with GDAL 2.1.2 from
>> experimental as summarized below, except mysql-workbench whose build
>> dependencies are not installable (#840786), but it's not in testing due
>> to (#839356).
>>
>> libgdal-grass doesn't need a binNMU as the 2.1.2 version will be
>> uploaded to unstable instead. liblas likewise doesn't need a binNMU,
>> the version is experimental will be moved to unstable instead.
>>
>> Please also binNMU osgearth in experimental as part of the transition.
> 
> Sounds good. Go ahead.

Thanks for the super quick feedback again!

gdal (2.1.2+dfsg-1), liblas (1.8.1-3) & libgdal-grass (2.1.2-1) have
been uploaded to unstable, and gdal was just accepted. Sometime tomorrow
the buildds should have installed the packages.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Processed: bug 842288 is forwarded to https://release.debian.org/transitions/html/gdal-2.1.2.html

[Debian Bug Tracking System]

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

> forwarded 842288 https://release.debian.org/transitions/html/gdal-2.1.2.html
Bug #842288 [release.debian.org] transition: gdal
Set Bug forwarded-to-address to 
'https://release.debian.org/transitions/html/gdal-2.1.2.html'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
842288: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842288
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#842277: transition: qtkeychain

[Emilio Pozuelo Monfort]

Control: tags -1 confirmed

On 27/10/16 17:19, Sandro Knauß wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Hi dear release team,
> 
> Now with liblibqt5keychain1 and libqtkeychain1 in the archive, we can start
> transtion the existing packages to the archive so that the new qtkeychain 
> package
> can transition to testing. The following source packages need to be rebuilt:
> 
> charmtimetracker
> owncloud-client
> 
> No changes are needed for both packages to be build with qtkeychain
> 0.7.0.
> 
> Please schedule binNMUs for the above mentioned packages on all
> architectures.

OK, go ahead and upload qtkeychain to unstable.

Cheers,
Emilio

Processed: Re: Bug#842277: transition: qtkeychain

[Debian Bug Tracking System]

Processing control commands:

> tags -1 confirmed
Bug #842277 [release.debian.org] transition: qtkeychain
Added tag(s) confirmed.

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

Bug#842262: transition: ros-geometric-shapes

[Emilio Pozuelo Monfort]

Control: tags -1 confirmed

On 27/10/16 15:43, Jochen Sprickerhof wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Hi,
> 
> I would like to transition to the new ABI of libgeometric-shapes. The only
> effected package is ros-robot-model which I maintain as well.

Ack.

Emilio

Processed: Re: Bug#842262: transition: ros-geometric-shapes

[Debian Bug Tracking System]

Processing control commands:

> tags -1 confirmed
Bug #842262 [release.debian.org] transition: ros-geometric-shapes
Added tag(s) confirmed.

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

Processed: Re: Bug#842288: transition: gdal

[Debian Bug Tracking System]

Processing control commands:

> tags -1 confirmed
Bug #842288 [release.debian.org] transition: gdal
Added tag(s) confirmed.

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

Processed: Re: Bug#842288: transition: gdal

[Debian Bug Tracking System]

Processing control commands:

> tags -1 confirmed
Bug #842288 [release.debian.org] transition: gdal
Ignoring request to alter tags of bug #842288 to the same tags previously set

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

Bug#842288: transition: gdal

[Emilio Pozuelo Monfort]

Control: tags -1 confirmed

On 27/10/16 20:10, Bas Couwenberg wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Dear Release Team,
> 
> For the Debian GIS team I'd like to transition to GDAL 2.1.2.
> 
> Like the previous transition to GDAL 2.1.1 (#830966), there is no SONAME
> bump, only the virtual ABI package changed to account for the C++ symbol
> changes.
> 
> All reverse dependencies rebuilt successfully with GDAL 2.1.2 from
> experimental as summarized below, except mysql-workbench whose build
> dependencies are not installable (#840786), but it's not in testing due
> to (#839356).
> 
> libgdal-grass doesn't need a binNMU as the 2.1.2 version will be
> uploaded to unstable instead. liblas likewise doesn't need a binNMU,
> the version is experimental will be moved to unstable instead.
> 
> Please also binNMU osgearth in experimental as part of the transition.
> 
> 
> Ben file:
> 
> title = "gdal";
> is_affected = .depends ~ /gdal-abi-2-1-[12]/
> is_good = .depends ~ "gdal-abi-2-1-2";
> is_bad = .depends ~ "gdal-abi-2-1-1";
> 
> 
> Transition: gdal
> 
>  libgdal20 (2.1.1+dfsg-5) -> libgdal20 (2.1.2+dfsg-1~exp1)
>  gdal-abi-2-1-1   -> gdal-abi-2-1-2
> 
> The status of the most recent rebuilds is as follows.
> 
>  dans-gdal-scripts  (0.23-6)   OK
>  fiona  (1.7.0.post2-1)OK
>  gazebo (7.3.1+dfsg-1) OK
>  gmt(5.2.1+dfsg-7) SKIP (no C++)
>  imposm (2.6.0+ds-3)   SKIP (no C++)
>  libcitygml (2.0-3)OK
>  liblas (1.8.1-2 / 1.8.1-3~exp1)   OK / OK
>  libosmium  (2.9.0-2)  SKIP (no C++)
>  mapcache   (1.4.1-3)  SKIP (no C++)
>  mapnik (3.0.12+ds-1)  OK
>  mapproxy   (1.9.0-3)  SKIP (no C++)
>  mapserver  (7.0.2-1)  SKIP (no C++)
>  merkaartor (0.18.3+ds-1)  OK
>  mysql-workbench(6.3.4+dfsg-3) BD-UNINST / FTBFS
>  ncl(6.3.0-11) SKIP (no C++)
>  node-srs   (0.4.8+dfsg-2) OK
>  octave-mapping (1.2.1-1)  OK
>  openscenegraph (3.2.3+dfsg1-2)OK
>  osmium (0.0~20160425-e2e4368-2)   SKIP (no C++)
>  pdal   (1.3.0-1)  OK
>  postgis(2.3.0+dfsg-3) SKIP (no C++)
>  pprepair   (0.0~20160321-87ffae5-1)   OK
>  prepair(0.7-6)OK
>  qlandkartegt   (1.8.1+ds-7)   OK
>  qmapshack  (1.7.1-1)  OK
>  rasterio   (0.36.0-1) OK
>  saga   (2.3.1+dfsg-2) OK
>  sumo   (0.27.1+dfsg1-1)   OK
>  thuban (1.2.2-11) OK
>  vtk6   (6.3.0+dfsg1-2)OK
>  xastir (2.0.8-2)  SKIP (no C++)
> 
>  grass  (7.0.5-2)  SKIP (no C++)
>  openscenegraph-3.4 (3.4.0+dfsg1-4)OK
>  osgearth   (2.7.0+dfsg-2 / 2.8.0+dfsg-1~exp1) OK / OK
>  osmcoastline   (2.1.4-1)  OK
>  otb(5.6.1+dfsg-1) OK
>  pktools(2.6.7-2)  OK
>  pyosmium   (2.9.0-1)  SKIP (no C++)
> 
>  libgdal-grass  (2.1.1-3 / 2.1.2-1~exp1)   FTBFS / OK
>  qgis   (2.14.8+dfsg-1)OK
> 
> 
> Kind Regards,
> 
> Bas
> 
> 

Bug#842288: transition: gdal

[Emilio Pozuelo Monfort]

Control: tags -1 confirmed

On 27/10/16 20:10, Bas Couwenberg wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Dear Release Team,
> 
> For the Debian GIS team I'd like to transition to GDAL 2.1.2.
> 
> Like the previous transition to GDAL 2.1.1 (#830966), there is no SONAME
> bump, only the virtual ABI package changed to account for the C++ symbol
> changes.
> 
> All reverse dependencies rebuilt successfully with GDAL 2.1.2 from
> experimental as summarized below, except mysql-workbench whose build
> dependencies are not installable (#840786), but it's not in testing due
> to (#839356).
> 
> libgdal-grass doesn't need a binNMU as the 2.1.2 version will be
> uploaded to unstable instead. liblas likewise doesn't need a binNMU,
> the version is experimental will be moved to unstable instead.
> 
> Please also binNMU osgearth in experimental as part of the transition.

Sounds good. Go ahead.

Cheers,
Emilio

Bug#842288: transition: gdal

[Bas Couwenberg]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

Dear Release Team,

For the Debian GIS team I'd like to transition to GDAL 2.1.2.

Like the previous transition to GDAL 2.1.1 (#830966), there is no SONAME
bump, only the virtual ABI package changed to account for the C++ symbol
changes.

All reverse dependencies rebuilt successfully with GDAL 2.1.2 from
experimental as summarized below, except mysql-workbench whose build
dependencies are not installable (#840786), but it's not in testing due
to (#839356).

libgdal-grass doesn't need a binNMU as the 2.1.2 version will be
uploaded to unstable instead. liblas likewise doesn't need a binNMU,
the version is experimental will be moved to unstable instead.

Please also binNMU osgearth in experimental as part of the transition.


Ben file:

title = "gdal";
is_affected = .depends ~ /gdal-abi-2-1-[12]/
is_good = .depends ~ "gdal-abi-2-1-2";
is_bad = .depends ~ "gdal-abi-2-1-1";


Transition: gdal

 libgdal20 (2.1.1+dfsg-5) -> libgdal20 (2.1.2+dfsg-1~exp1)
 gdal-abi-2-1-1   -> gdal-abi-2-1-2

The status of the most recent rebuilds is as follows.

 dans-gdal-scripts  (0.23-6)   OK
 fiona  (1.7.0.post2-1)OK
 gazebo (7.3.1+dfsg-1) OK
 gmt(5.2.1+dfsg-7) SKIP (no C++)
 imposm (2.6.0+ds-3)   SKIP (no C++)
 libcitygml (2.0-3)OK
 liblas (1.8.1-2 / 1.8.1-3~exp1)   OK / OK
 libosmium  (2.9.0-2)  SKIP (no C++)
 mapcache   (1.4.1-3)  SKIP (no C++)
 mapnik (3.0.12+ds-1)  OK
 mapproxy   (1.9.0-3)  SKIP (no C++)
 mapserver  (7.0.2-1)  SKIP (no C++)
 merkaartor (0.18.3+ds-1)  OK
 mysql-workbench(6.3.4+dfsg-3) BD-UNINST / FTBFS
 ncl(6.3.0-11) SKIP (no C++)
 node-srs   (0.4.8+dfsg-2) OK
 octave-mapping (1.2.1-1)  OK
 openscenegraph (3.2.3+dfsg1-2)OK
 osmium (0.0~20160425-e2e4368-2)   SKIP (no C++)
 pdal   (1.3.0-1)  OK
 postgis(2.3.0+dfsg-3) SKIP (no C++)
 pprepair   (0.0~20160321-87ffae5-1)   OK
 prepair(0.7-6)OK
 qlandkartegt   (1.8.1+ds-7)   OK
 qmapshack  (1.7.1-1)  OK
 rasterio   (0.36.0-1) OK
 saga   (2.3.1+dfsg-2) OK
 sumo   (0.27.1+dfsg1-1)   OK
 thuban (1.2.2-11) OK
 vtk6   (6.3.0+dfsg1-2)OK
 xastir (2.0.8-2)  SKIP (no C++)

 grass  (7.0.5-2)  SKIP (no C++)
 openscenegraph-3.4 (3.4.0+dfsg1-4)OK
 osgearth   (2.7.0+dfsg-2 / 2.8.0+dfsg-1~exp1) OK / OK
 osmcoastline   (2.1.4-1)  OK
 otb(5.6.1+dfsg-1) OK
 pktools(2.6.7-2)  OK
 pyosmium   (2.9.0-1)  SKIP (no C++)

 libgdal-grass  (2.1.1-3 / 2.1.2-1~exp1)   FTBFS / OK
 qgis   (2.14.8+dfsg-1)OK


Kind Regards,

Bas

Re: status of tzdata package in stable and oldstable

[Mert Dirik]

On 10/26/2016 09:15 AM, Erdem Bayer wrote:

2016h is in jessie now, this update was very important for turkish users.


FYI, new timezone was actually fixed in 2016g and it was already in 
jessie since the beginning of the month.


( See https://packages.qa.debian.org/t/tzdata/news/20161003T220345Z.html)

Bug#842277: transition: qtkeychain

[Sandro Knauß]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

Hi dear release team,

Now with liblibqt5keychain1 and libqtkeychain1 in the archive, we can start
transtion the existing packages to the archive so that the new qtkeychain 
package
can transition to testing. The following source packages need to be rebuilt:

charmtimetracker
owncloud-client

No changes are needed for both packages to be build with qtkeychain
0.7.0.

Please schedule binNMUs for the above mentioned packages on all
architectures.

Thank you.

Sandro Knauß

The automatic Ben file is correct:

title = "auto-qtkeychain";
is_affected = .depends ~ 
/\b(libqt5keychain0|libqtkeychain0|libqt5keychain1|libqtkeychain1)\b/;
is_good = .depends ~ /\b(libqt5keychain1|libqtkeychain1)\b/;
is_bad = .depends ~ /\b(libqt5keychain0|libqtkeychain0)\b/;


-- System Information:
Debian Release: stretch/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), 
(500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#842262: transition: ros-geometric-shapes

[Jochen Sprickerhof]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

Hi,

I would like to transition to the new ABI of libgeometric-shapes. The only
effected package is ros-robot-model which I maintain as well.

Cheers Jochen

Ben file:

title = "ros-geometric-shapes";
is_affected = .depends ~ "libgeometric-shapes1d" | .depends ~ 
"libgeometric-shapes2d";
is_good = .depends ~ "libgeometric-shapes2d";
is_bad = .depends ~ "libgeometric-shapes1d";


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.7.0-1-amd64 (SMP w/12 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Re: [debian-mysql] getting mysql-5.6 out of stretch

[Alexander Wirt]

On Thu, 27 Oct 2016, Otto Kekäläinen wrote:

> Hello!
> 
> We have not filed a mass bug report against packages regarding
> transitioning to default-mysql-*. Would you like to file it?
> I made a Lintian rule that is now in use, but a mass bug filing would
> speed things up.
Isn't that a little bit late in the release process? 

It also was for openssl.

Alex

Re: [debian-mysql] getting mysql-5.6 out of stretch

[Otto Kekäläinen]

Hello!

We have not filed a mass bug report against packages regarding
transitioning to default-mysql-*. Would you like to file it?
I made a Lintian rule that is now in use, but a mass bug filing would
speed things up.

Bug#842238: nmu: zygrib_7.0.0-4

[Maximiliano Curia]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

libnova is an ABI unstable library and as such every new upstream release 
bumps it's so version. I've just uploaded libnova 0.16 to unstable, which 
requires a rebuild of zygrib. The auto-transition can be seen here:
 https://release.debian.org/transitions/html/auto-libnova.html

Please trigger the following rebuild with --add-depends="libnova-dev (>= 0.16)"

nmu zygrib_7.0.0-4 . ANY . unstable . -m "Rebuild against libnova 0.16"

- -- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'buildd-unstable'), (500, 'testing'), (500, 'stable'), (50, 'unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

-BEGIN PGP SIGNATURE-

iQItBAEBCgAXBQJYEcASEBxtYXh5QGRlYmlhbi5vcmcACgkQxxl2mbKbIypOexAA
sNCei7lPbyz/K/l8AnEQHgANWzb9QmDfsljHJc7F6zZ9/TDn8voUj+SU+T9E+3Rs
1qXiQ6z+bEKCkJVF57HF00kubyosfyUJhF3zVxfzA27+xxjuIaE3zpvuS+VD8MTr
RFKi18D00tLpIY0sBSpoYLwONYGQ6hXdPE+YjM3Zkhs8rJ8pV/AiWhppq2QV8PrY
U/X672k0IoKiOvLdJtnsfm4XeheKLjj80fAxxJgu4lDnBNOw6qnO/yV6QwHj7lW1
dtpB+z9yAHb3o+KiRaB3pRZkeB4mwhy+NuWLkUTPRV+WHstSvfuzietajAX4cJD5
JU49/8S55CuJVanIdu8VdeSfdvdViXIesyoU6RnvM+IYW79DkUEoiCf2MwzNRZx/
fp1SLKPi1v6ZJ1m8Z5cBe3fdghFuT233/uhxfuPWyj6V0W4hivhLmR6EVxeNumSe
qAzt+hpr/VF7U0nZDtlpqH2Q/6l/Nm+G+rM4a7A6tKjPTyRbV5LGwi1wam2y5/g3
Xj3RTxS6CCKrJAozfrBp47redtP9ydrhQ7vv7igbTDH25EuuvbNl7RcffSOqRRze
S0wNN0RljawPAjiSglmWTYpk3XCLETIVSZ1InymHcvdGQhpmKc68evsAHBmIzqzh
69i8ZdUHSQEUXT/NfUTDja3P3WZSmBv9xcUyS7DjwDk=
=tjTi
-END PGP SIGNATURE-

getting mysql-5.6 out of stretch

[Andreas Beckmann]

That looks like a lot of work is left to finish the transition to mariadb:

anbe@coccia:~$ dak rm -Rn -s testing mysql-5.6  
Will remove the following packages from testing:

libmysqlclient-dev |   5.6.30-1 | amd64, arm64, armel, armhf, i386, mips, 
mips64el, mipsel, powerpc, ppc64el, s390x
libmysqlclient18 |   5.6.30-1 | amd64, arm64, armel, armhf, i386, mips, 
mips64el, mipsel, powerpc, ppc64el, s390x
libmysqld-dev |   5.6.30-1 | amd64, arm64, armel, armhf, i386, mips, mips64el, 
mipsel, powerpc, ppc64el, s390x
libmysqld-pic |   5.6.30-1 | amd64, arm64, armel, armhf, i386, mips, mips64el, 
mipsel, powerpc, ppc64el, s390x
 mysql-5.6 |   5.6.30-1 | source
mysql-client |   5.6.30-1 | all
mysql-client-5.6 |   5.6.30-1 | amd64, arm64, armel, armhf, i386, mips, 
mips64el, mipsel, powerpc, ppc64el, s390x
mysql-client-core-5.6 |   5.6.30-1 | amd64, arm64, armel, armhf, i386, mips, 
mips64el, mipsel, powerpc, ppc64el, s390x
mysql-server |   5.6.30-1 | all
mysql-server-5.6 |   5.6.30-1 | amd64, arm64, armel, armhf, i386, mips, 
mips64el, mipsel, powerpc, ppc64el, s390x
mysql-server-core-5.6 |   5.6.30-1 | amd64, arm64, armel, armhf, i386, mips, 
mips64el, mipsel, powerpc, ppc64el, s390x
mysql-source-5.6 |   5.6.30-1 | amd64, arm64, armel, armhf, i386, mips, 
mips64el, mipsel, powerpc, ppc64el, s390x
mysql-testsuite |   5.6.30-1 | all
mysql-testsuite-5.6 |   5.6.30-1 | amd64, arm64, armel, armhf, i386, mips, 
mips64el, mipsel, powerpc, ppc64el, s390x

Maintainer: Debian MySQL Maintainers 

--- Reason ---

--

Checking reverse dependencies...
# Broken Depends:
amarok: amarok
anope: anope
aolserver4-nsmysql: aolserver4-nsmysql
apophenia: libapophenia2
apr-util: libaprutil1-dbd-mysql
argus-clients: argus-client
audiolink: audiolink
bacula: bacula-common-mysql
bareos: bareos-database-mysql
biomaj: biomaj
cctools: coop-computing-tools [amd64 i386]
cfengine3: cfengine3 [amd64 arm64 armel armhf i386 mips mipsel powerpc ppc64el 
s390x]
cl-sql: cl-sql-mysql
courier-authlib: courier-authlib-mysql
cppdb: libcppdb-mysql0
ctn: ctn
cvm: cvm-mysql
cyrus-sasl2: libsasl2-modules-sql
dbf2mysql: dbf2mysql
diaspora-installer/contrib: diaspora-installer-mysql
dovecot: dovecot-mysql
emboss: emboss
emboss-lib
exim4: exim4-daemon-heavy
flow-tools: flow-tools
fnordmetric: fnordmetric
gammu: libgsmsd7
gearmand: gearman-job-server
gentle: gentle
gmysqlcc: gmysqlcc
gnash: gnash-ext-mysql
gnuais: gnuais
gnunet: gnunet
gnustep-sqlclient: libsqlclient1.7
hydra: hydra
inspircd: inspircd
isc-kea: kea-common
jabberd2: jabberd2
kannel: kannel
kannel-dev
kannel-extras
kannel-sqlbox: kannel-sqlbox
lcd4linux: lcd4linux
lcmaps-plugins-jobrep: lcmaps-plugins-jobrep-admin
libapache-mod-musicindex: libapache2-mod-musicindex
libdbi-drivers: libdbd-mysql
libgda5: libgda-5.0-mysql
libodb-mysql: libodb-mysql-2.4
libpreludedb: libpreludedb0 [amd64 armel armhf i386 mips mips64el mipsel 
powerpc s390x]
libterralib: libterralib3
libzdb: libzdb11
lighttpd: lighttpd-mod-mysql-vhost
lua-dbi: lua-dbi-mysql
lua-sql: lua-sql-mysql
mailutils: libmailutils4
mediatomb: mediatomb-common
mosquitto-auth-plugin: mosquitto-auth-plugin
motion: motion
mydumper: mydumper
myodbc: libmyodbc
mysql++: libmysql++-dev
 libmysql++3v5
mysql-connector-c++: libmysqlcppconn7v5
mysql-ocaml: libmysql-ocaml
 libmysql-ocaml-dev
mysqltcl: mysqltcl
net-snmp: snmptrapd
ntopng: ntopng [amd64 armel armhf i386 mips mipsel powerpc]
nufw: nuauth-extra
  nuauth-log-mysql
opendnssec: opendnssec-enforcer-mysql
opensmtpd-extras: opensmtpd-extras
pam-mysql: libpam-mysql [amd64 armel armhf i386 mips mips64el mipsel powerpc 
s390x]
perdition: perdition-mysql
pike7.8: pike7.8-mysql
pike8.0: pike8.0-mysql
pmacct: pmacct
poco: libpocomysql9v5
  libpocomysql9v5-dbg
postfix-gld: postfix-gld
postgresql-mysql-fdw: postgresql-9.6-mysql-fdw
pure-ftpd: pure-ftpd-mysql
pvpgn/contrib: pvpgn
python-mysqldb: python-mysqldb
python-mysqldb-dbg
python3-mysqldb
python3-mysqldb-dbg
qt4-x11: libqt4-sql-mysql
qtbase-opensource-src: libqt5sql5-mysql
redland: librdf-storage-mysql
resiprocate: repro
rsyslog: rsyslog-mysql
ruby-dataobjects-mysql: ruby-dataobjects-mysql
ruby-mysql2: ruby-mysql2
slurm-llnl: slurm-wlm-basic-plugins
soci: libsoci-mysql3.2
sope: libsope1
sphinxsearch: sphinxsearch
spotweb: spotweb
stacks: stacks-web
stardict-tools: stardict-tools
tango: tango-accesscontrol
   tango-db
tarantool-lts: tarantool-lts-mysql-module [amd64 i386]
tntdb: tntdb-mysql4v5
trafficserver: trafficserver-experimental-plugins [amd64 arm64 i386 mips mipsel 
ppc64el]
ulogd2: ulogd2-mysql
urweb: urweb [amd64 armel armhf i386 mips mipsel powerpc]
witty: libwtdbomysql39 [amd64 arm64 armhf i386 mips mips64el mipsel powerpc 
ppc64el s390x]
zoneminder: zoneminder

# Broken Build-Depends:
akonadi: libmysqlclient-dev

Bug#827061: transition: openssl

[Tino Mettler]

On Wed, Oct 26, 2016 at 10:55:19 +0200, Emilio Pozuelo Monfort wrote:

> So let's do this. Let's try to get it finished and only ship openssl 1.1. We
> still have three months until the full freeze

Hi,

packages that currently FTBFS will be removed from testing in 2 weeks. 
The freeze deadline for re-entry is January 5th.  With the migration
delay the fixed package should be uploaded until the end of December,
where may people will be on holiday I guess (both Debian and Upstream
developers).

So I think it's desirable for many maintainers to have a fixed package
in Sid before Christmas or they will have to ask for a freeze
exception. I'd be glad if this is announced more prominent, e.g on the
debian-devel-announce mailing list.

Regards,
Tino

Bug#838514: marked as done (britney: patch to speed up loop performance)

[Debian Bug Tracking System]

Your message dated Thu, 27 Oct 2016 06:04:00 +
with message-id 
and subject line Re: ITM: Britney2 branch britney-patch-bundle-2016-09 into 
master
has caused the Debian Bug report #838514,
regarding britney: patch to speed up loop performance
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.)


-- 
838514: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838514
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: britney, patch

Hi,

In Britney.write_excuses, there's a number of for loops doing slow operations 
redundantly. I've created a small patch that optimizes those loops with a good 
performance improvement. Here's some python profiling that proves the concept:

http://paste.ubuntu.com/23212621/

-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-36-generic (SMP w/8 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
>From daf514d526d47646bb15f5b0a91cd9b8abe69820 Mon Sep 17 00:00:00 2001
From: Robert Bruce Park 
Date: Tue, 20 Sep 2016 14:03:02 -0700
Subject: [PATCH] Python loop performance enhancements.

---
 britney.py | 30 +-
 1 file changed, 17 insertions(+), 13 deletions(-)

diff --git a/britney.py b/britney.py
index b28c62f..79ad49c 100755
--- a/britney.py
+++ b/britney.py
@@ -1751,59 +1751,63 @@ class Britney(object):
 should_upgrade_srcarch = self.should_upgrade_srcarch
 should_upgrade_src = self.should_upgrade_src
 
+unstable = sources['unstable']
+testing = sources['testing']
+
 # this list will contain the packages which are valid candidates;
 # if a package is going to be removed, it will have a "-" prefix
 upgrade_me = []
+upgrade_me_append = upgrade_me.append  # Every . in a loop slows it down
 
 excuses = self.excuses = {}
 
 # for every source package in testing, check if it should be removed
-for pkg in sources['testing']:
+for pkg in testing:
 if should_remove_source(pkg):
-upgrade_me.append("-" + pkg)
+upgrade_me_append("-" + pkg)
 
 # for every source package in unstable check if it should be upgraded
-for pkg in sources['unstable']:
-if sources['unstable'][pkg][FAKESRC]: continue
+for pkg in unstable:
+if unstable[pkg][FAKESRC]: continue
 # if the source package is already present in testing,
 # check if it should be upgraded for every binary package
-if pkg in sources['testing'] and not sources['testing'][pkg][FAKESRC]:
+if pkg in testing and not testing[pkg][FAKESRC]:
 for arch in architectures:
 if should_upgrade_srcarch(pkg, arch, 'unstable'):
-upgrade_me.append("%s/%s" % (pkg, arch))
+upgrade_me_append("%s/%s" % (pkg, arch))
 
 # check if the source package should be upgraded
 if should_upgrade_src(pkg, 'unstable'):
-upgrade_me.append(pkg)
+upgrade_me_append(pkg)
 
 # for every source package in *-proposed-updates, check if it should be upgraded
 for suite in ['pu', 'tpu']:
 for pkg in sources[suite]:
 # if the source package is already present in testing,
 # check if it should be upgraded for every binary package
-if pkg in sources['testing']:
+if pkg in testing:
 for arch in architectures:
 if should_upgrade_srcarch(pkg, arch, suite):
-upgrade_me.append("%s/%s_%s" % (pkg, arch, suite))
+upgrade_me_append("%s/%s_%s" % (pkg, arch, suite))
 
 # check if the source package should be upgraded
 if should_upgrade_src(pkg, suite):
-upgrade_me.append("%s_%s" % (pkg, suite))
+upgrade_me_append("%s_%s" % (pkg, suite))
 
 # process the `remove' hints, if the given package is not yet in upgrade_me
 for hint in 

Bug#842206: marked as done (nmu: Please binNMU bmusb against newer libusb-1.0)

[Debian Bug Tracking System]

Your message dated Thu, 27 Oct 2016 06:06:00 +
with message-id <93149ea2-28fd-8c76-b670-b41479715...@thykier.net>
and subject line Re: nmu: Please binNMU bmusb against newer libusb-1.0
has caused the Debian Bug report #842206,
regarding nmu: Please binNMU bmusb against newer libusb-1.0
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.)


-- 
842206: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842206
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: binnmu
Severity: normal

Hi,

bmusb can benefit strongly from being linked to libusb-1.0 (>= 2:1.0.21-1).
Do you think it would be possible to schedule a binNMU for all architectures?
Once upon a time, the format was something like

nmu bmusb_0.5.2-2 . ANY . -m "Rebuild against libusb-1.0 version with support 
for zerocopy USB."

Thanks!

/* Steinar */
-- 
Homepage: https://www.sesse.net/
--- End Message ---
--- Begin Message ---
On Wed, 26 Oct 2016 23:57:10 +0200 "Steinar H. Gunderson"
 wrote:
> Package: release.debian.org
> User: release.debian@packages.debian.org
> Usertags: binnmu
> Severity: normal
> 
> Hi,
> 
> bmusb can benefit strongly from being linked to libusb-1.0 (>= 2:1.0.21-1).
> Do you think it would be possible to schedule a binNMU for all architectures?
> Once upon a time, the format was something like
> 
> nmu bmusb_0.5.2-2 . ANY . -m "Rebuild against libusb-1.0 version with support 
> for zerocopy USB."
> 
> Thanks!
> 
> /* Steinar */
> -- 
> Homepage: https://www.sesse.net/
> 
> 

Scheduled, thanks.

~Niels--- End Message ---

Bug#842010: marked as done (nmu: daq_2.0.4-3)

[Debian Bug Tracking System]

Your message dated Thu, 27 Oct 2016 05:59:00 +
with message-id <457fbed1-2883-503a-2ace-d15f04dc5...@thykier.net>
and subject line Re: nmu: daq_2.0.4-3
has caused the Debian Bug report #842010,
regarding nmu: daq_2.0.4-3
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.)


-- 
842010: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842010
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
Control: block 837687 by -1

nmu daq_2.0.4-3 . ANY . unstable . -m "Recompile static libraries with PIE"

RC bug #837687 should be closed when the binNMUs are in unstable.
--- End Message ---
--- Begin Message ---
On Tue, 25 Oct 2016 11:53:53 +0300 Adrian Bunk  wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
> Control: block 837687 by -1
> 
> nmu daq_2.0.4-3 . ANY . unstable . -m "Recompile static libraries with PIE"
> 
> RC bug #837687 should be closed when the binNMUs are in unstable.
> 
> 

Scheduled, thanks.

~Niels--- End Message ---

Bug#841961: marked as done (nmu: ocaml_4.02.3-7)

[Debian Bug Tracking System]

Your message dated Thu, 27 Oct 2016 06:00:00 +
with message-id 
and subject line Re: nmu: ocaml_4.02.3-7
has caused the Debian Bug report #841938,
regarding nmu: ocaml_4.02.3-7
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.)


-- 
841938: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841938
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Please rebuild ocaml against the pie-enabled compiler chain, to fix an FTBFS of 
scilab package:

ocamlopt -o modelicac -I ./src/modelica_compiler -I ./src/xml2modelica  
nums.cmxa ./src/modelica_compiler/parseTree.cmx ./src/modelica_compiler/linenu
m.cmx ./src/modelica_compiler/parser.cmx ./src/modelica_compiler/lexer.cmx 
./src/modelica_compiler/precompilation.cmx ./src/modelica_compiler/compilat
ion.cmx ./src/modelica_compiler/instantiation.cmx 
./src/modelica_compiler/graphNodeSet.cmx 
./src/modelica_compiler/symbolicExpression.cmx ./src/modeli
ca_compiler/squareSparseMatrix.cmx ./src/modelica_compiler/bipartiteGraph.cmx 
./src/modelica_compiler/hungarianMethod.cmx ./src/modelica_compiler/caus
alityGraph.cmx ./src/modelica_compiler/optimization.cmx 
./src/modelica_compiler/xMLCodeGeneration.cmx 
./src/modelica_compiler/optimizingCompiler.cmx .
/src/modelica_compiler/scicosCodeGeneration.cmx 
./src/modelica_compiler/scicosOptimizingCompiler.cmx
/usr/bin/ld: /usr/lib/ocaml/libasmrun.a(fail.o): relocation R_X86_64_32 against 
symbol `caml_exn_Failure' can not be used when making a shared object;
 recompile with -fPIC
/usr/bin/ld: /usr/lib/ocaml/libasmrun.a(roots.o): relocation R_X86_64_32 
against symbol `caml_frametable' can not be used when making a shared object;
 recompile with -fPIC
...

nmu ocaml_4.02.3-7 . ANY . unstable . -m "rebuild with pie-enabled compiler 
chain"

Thanks in advance,

_g.

- -- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-1-amd64 (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/dash
Init: systemd (via /run/systemd/system)

-BEGIN PGP SIGNATURE-

iQEcBAEBCAAGBQJYDmoGAAoJEO/obGx//s+DxK0H/jgiHLrcx0gT0N6hfGuwrMO2
mvHmCcLGZKnLmDrkZzgIq+pPtC3qjjlPtBeR+VhvkCc3uPTVpHqZDil2lXmDA8sN
m+klsGk5pWiF1mxeMM37+/ts8JY6Dk+VQXzahBilNH13t21MXZnx3dfygLH/1bDq
3qQLvt8aKQ5UuhvzT/Fr/COXfuNGXsRL0sStUYlFOpg7raJNysQ6mZFXZqexlI+Y
IoUur2okpt57OJP5P7SrK1O8ciAHXb2JnhET2lxj2VmavHMmX0hfTAArsDwYMA0R
gSXyO4GaLZRXjcSazV69P/5MyGHg10yKevSSGI4JBKUAKt9g36/SBo5KW40nSks=
=4TOF
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
On Mon, 24 Oct 2016 19:21:09 +0300 Adrian Bunk  wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
> Control: block 837359 by -1
> 
> nmu ocaml_4.02.3-7 . ANY . unstable . -m "Recompile static libraries with PIE"
> 
> RC bug #837359 should be closed when the binNMUs are in unstable.
> 
> 

Scheduled, thanks.

~Niels--- End Message ---

Bug#841938: marked as done (nmu: ocaml_4.02.3-7)

[Debian Bug Tracking System]

Your message dated Thu, 27 Oct 2016 06:00:00 +
with message-id 
and subject line Re: nmu: ocaml_4.02.3-7
has caused the Debian Bug report #841938,
regarding nmu: ocaml_4.02.3-7
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.)


-- 
841938: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841938
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
Control: block 837359 by -1

nmu ocaml_4.02.3-7 . ANY . unstable . -m "Recompile static libraries with PIE"

RC bug #837359 should be closed when the binNMUs are in unstable.
--- End Message ---
--- Begin Message ---
On Mon, 24 Oct 2016 19:21:09 +0300 Adrian Bunk  wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
> Control: block 837359 by -1
> 
> nmu ocaml_4.02.3-7 . ANY . unstable . -m "Recompile static libraries with PIE"
> 
> RC bug #837359 should be closed when the binNMUs are in unstable.
> 
> 

Scheduled, thanks.

~Niels--- End Message ---

Bug#842030: marked as done (nmu: antlr_2.7.7+dfsg-7)

[Debian Bug Tracking System]

Your message dated Thu, 27 Oct 2016 05:56:00 +
with message-id <676434e5-89d4-9901-fee8-0f8aeec5c...@thykier.net>
and subject line Re: nmu: antlr_2.7.7+dfsg-7
has caused the Debian Bug report #842030,
regarding nmu: antlr_2.7.7+dfsg-7
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.)


-- 
842030: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842030
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
Control: block 837489 by -1

nmu antlr_2.7.7+dfsg-7 . ANY . unstable . -m "Recompile static libraries with 
PIE"

RC bug #837489 should be closed when the binNMUs are in unstable.
--- End Message ---
--- Begin Message ---
On Tue, 25 Oct 2016 15:06:20 +0300 Adrian Bunk  wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
> Control: block 837489 by -1
> 
> nmu antlr_2.7.7+dfsg-7 . ANY . unstable . -m "Recompile static libraries with 
> PIE"
> 
> RC bug #837489 should be closed when the binNMUs are in unstable.
> 
> 

Already done AFAICT.

~Niels--- End Message ---

Bug#842068: marked as done (nmu: tinc_1.0.29-1)

[Debian Bug Tracking System]

Your message dated Thu, 27 Oct 2016 05:57:00 +
with message-id <7147607e-5051-eb21-4968-d948198a6...@thykier.net>
and subject line Re: nmu: tinc_1.0.29-1
has caused the Debian Bug report #842068,
regarding nmu: tinc_1.0.29-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.)


-- 
842068: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842068
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

nmu tinc_1.0.29-1 . amd64 . unstable . -m "Rebuild in a clean sid environment."

Maintainer-uploaded binaries were built against libssl1.1 from
experimental.


Andreas
--- End Message ---
--- Begin Message ---
On Tue, 25 Oct 2016 19:14:11 +0200 Andreas Beckmann  wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
> 
> nmu tinc_1.0.29-1 . amd64 . unstable . -m "Rebuild in a clean sid 
> environment."
> 
> Maintainer-uploaded binaries were built against libssl1.1 from
> experimental.
> 
> 
> Andreas
> 
> 

Scheduled, thanks.

~Niels--- End Message ---