Bug#825480: nmu: ant_1.9.7-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu ant_1.9.7-3 . ANY . unstable . -m "Rebuild against libgcj-bc 5.3.1-3" dw ant_1.9.7-3 . ANY . -m "libgcj-bc (>= 5.3.1-3)" libgcj-bc 5.3.1-2 had a broken shlibs file, generating an unsatisfiable dependency. Andreas
Bug#823335: transition: gdal
On 27/05/16 01:45, Sebastiaan Couwenberg wrote: > On 05/22/2016 12:20 PM, Sebastiaan Couwenberg wrote: >> On 05/21/2016 11:19 AM, Emilio Pozuelo Monfort wrote: >>> On 20/05/16 16:07, Sebastiaan Couwenberg wrote: On 05/20/2016 11:27 AM, Sebastiaan Couwenberg wrote: > On 05/14/2016 11:30 AM, Bas Couwenberg wrote: >> The vtk6 issue on mipsel remains. texlive-bin (2016.20160513.41080-1) >> fixed the FTBFS on most architectures, but still fails on mips, mipsel & >> sparc64. I've reported #824260 for this. > > texlive-bin on mipsel has been fixed, and r-base is now also available > on mipsel which should unblock the mipsel build of vtk6, but that hasn't > started yet. tex-common fails to install on mipsel preventing vtk6 builds. I've reported this in #824862. >>> >>> Thanks. We're also waiting for the d-i release, as mapnik is waiting for >>> harfbuzz which is blocked because of the udeb. >>> >>> So let's wait a couple of days and see where we stand then. >> >> The tex-common installation failure can be worked around by installing >> the context package. >> >> The vtk6 build on mipsel is now also blocked by gtk+3.0 being >> BD-uninstallable on the all architecture, a source-full upload of >> gtk+3.0 should resolve that. I've reported this issue in #824999. > > The vtk6 build for mipsel is finally here, thanks to the tex-common and > gtk+3.0 fixes in their latest uploads. And to the fact that I bumped its build priority when gtk+ got fixed :) > I did not expect the vtk6 build before the end of the weekend, so I > updated a couple of rdeps recently which haven't aged 5 days yet. > pktools, qgis & otb need one more day, and postgis needs two. qgis and otb are not in testing so are not a problem. As for pktools, I already urgented it a couple of days ago. Let's see if everything migrates in the next non-crashy britney run. Cheers, Emilio
Bug#825480: marked as done (nmu: ant_1.9.7-3)
Your message dated Fri, 27 May 2016 11:15:13 +0200 with message-id <57481021.2020...@debian.org> and subject line Re: Bug#825480: nmu: ant_1.9.7-3 has caused the Debian Bug report #825480, regarding nmu: ant_1.9.7-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.) -- 825480: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825480 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 ant_1.9.7-3 . ANY . unstable . -m "Rebuild against libgcj-bc 5.3.1-3" dw ant_1.9.7-3 . ANY . -m "libgcj-bc (>= 5.3.1-3)" libgcj-bc 5.3.1-2 had a broken shlibs file, generating an unsatisfiable dependency. Andreas --- End Message --- --- Begin Message --- On 27/05/16 09:15, Andreas Beckmann wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: binnmu > > nmu ant_1.9.7-3 . ANY . unstable . -m "Rebuild against libgcj-bc 5.3.1-3" > dw ant_1.9.7-3 . ANY . -m "libgcj-bc (>= 5.3.1-3)" > > libgcj-bc 5.3.1-2 had a broken shlibs file, generating an unsatisfiable > dependency. Scheduled. Emilio--- End Message ---
Bug#823335: transition: gdal
On 05/27/2016 11:12 AM, Emilio Pozuelo Monfort wrote: > On 27/05/16 01:45, Sebastiaan Couwenberg wrote: >> On 05/22/2016 12:20 PM, Sebastiaan Couwenberg wrote: >>> On 05/21/2016 11:19 AM, Emilio Pozuelo Monfort wrote: On 20/05/16 16:07, Sebastiaan Couwenberg wrote: > On 05/20/2016 11:27 AM, Sebastiaan Couwenberg wrote: >> On 05/14/2016 11:30 AM, Bas Couwenberg wrote: >>> The vtk6 issue on mipsel remains. texlive-bin (2016.20160513.41080-1) >>> fixed the FTBFS on most architectures, but still fails on mips, mipsel & >>> sparc64. I've reported #824260 for this. >> >> texlive-bin on mipsel has been fixed, and r-base is now also available >> on mipsel which should unblock the mipsel build of vtk6, but that hasn't >> started yet. > > tex-common fails to install on mipsel preventing vtk6 builds. I've > reported this in #824862. Thanks. We're also waiting for the d-i release, as mapnik is waiting for harfbuzz which is blocked because of the udeb. So let's wait a couple of days and see where we stand then. >>> >>> The tex-common installation failure can be worked around by installing >>> the context package. >>> >>> The vtk6 build on mipsel is now also blocked by gtk+3.0 being >>> BD-uninstallable on the all architecture, a source-full upload of >>> gtk+3.0 should resolve that. I've reported this issue in #824999. >> >> The vtk6 build for mipsel is finally here, thanks to the tex-common and >> gtk+3.0 fixes in their latest uploads. > > And to the fact that I bumped its build priority when gtk+ got fixed :) I didn't know you could do that. Thank you! >> I did not expect the vtk6 build before the end of the weekend, so I >> updated a couple of rdeps recently which haven't aged 5 days yet. >> pktools, qgis & otb need one more day, and postgis needs two. > > qgis and otb are not in testing so are not a problem. As for pktools, I > already > urgented it a couple of days ago. Let's see if everything migrates in the next > non-crashy britney run. Shouldn't postgis get an urgent hint too then? Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#823335: transition: gdal
On 27/05/16 11:20, Sebastiaan Couwenberg wrote: > On 05/27/2016 11:12 AM, Emilio Pozuelo Monfort wrote: >> On 27/05/16 01:45, Sebastiaan Couwenberg wrote: >>> On 05/22/2016 12:20 PM, Sebastiaan Couwenberg wrote: On 05/21/2016 11:19 AM, Emilio Pozuelo Monfort wrote: > On 20/05/16 16:07, Sebastiaan Couwenberg wrote: >> On 05/20/2016 11:27 AM, Sebastiaan Couwenberg wrote: >>> On 05/14/2016 11:30 AM, Bas Couwenberg wrote: The vtk6 issue on mipsel remains. texlive-bin (2016.20160513.41080-1) fixed the FTBFS on most architectures, but still fails on mips, mipsel & sparc64. I've reported #824260 for this. >>> >>> texlive-bin on mipsel has been fixed, and r-base is now also available >>> on mipsel which should unblock the mipsel build of vtk6, but that hasn't >>> started yet. >> >> tex-common fails to install on mipsel preventing vtk6 builds. I've >> reported this in #824862. > > Thanks. We're also waiting for the d-i release, as mapnik is waiting for > harfbuzz which is blocked because of the udeb. > > So let's wait a couple of days and see where we stand then. The tex-common installation failure can be worked around by installing the context package. The vtk6 build on mipsel is now also blocked by gtk+3.0 being BD-uninstallable on the all architecture, a source-full upload of gtk+3.0 should resolve that. I've reported this issue in #824999. >>> >>> The vtk6 build for mipsel is finally here, thanks to the tex-common and >>> gtk+3.0 fixes in their latest uploads. >> >> And to the fact that I bumped its build priority when gtk+ got fixed :) > > I didn't know you could do that. Thank you! > >>> I did not expect the vtk6 build before the end of the weekend, so I >>> updated a couple of rdeps recently which haven't aged 5 days yet. >>> pktools, qgis & otb need one more day, and postgis needs two. >> >> qgis and otb are not in testing so are not a problem. As for pktools, I >> already >> urgented it a couple of days ago. Let's see if everything migrates in the >> next >> non-crashy britney run. > > Shouldn't postgis get an urgent hint too then? AFAICS that doesn't depend on gdal-abi-*, only on libgdal. So it doesn't need to migrate with the rest of the packages. Cheers, Emilio
Bug#823335: transition: gdal
On 05/27/2016 11:25 AM, Emilio Pozuelo Monfort wrote: > On 27/05/16 11:20, Sebastiaan Couwenberg wrote: >> On 05/27/2016 11:12 AM, Emilio Pozuelo Monfort wrote: >>> On 27/05/16 01:45, Sebastiaan Couwenberg wrote: On 05/22/2016 12:20 PM, Sebastiaan Couwenberg wrote: > On 05/21/2016 11:19 AM, Emilio Pozuelo Monfort wrote: >> On 20/05/16 16:07, Sebastiaan Couwenberg wrote: >>> On 05/20/2016 11:27 AM, Sebastiaan Couwenberg wrote: On 05/14/2016 11:30 AM, Bas Couwenberg wrote: > The vtk6 issue on mipsel remains. texlive-bin (2016.20160513.41080-1) > fixed the FTBFS on most architectures, but still fails on mips, > mipsel & > sparc64. I've reported #824260 for this. texlive-bin on mipsel has been fixed, and r-base is now also available on mipsel which should unblock the mipsel build of vtk6, but that hasn't started yet. >>> >>> tex-common fails to install on mipsel preventing vtk6 builds. I've >>> reported this in #824862. >> >> Thanks. We're also waiting for the d-i release, as mapnik is waiting for >> harfbuzz which is blocked because of the udeb. >> >> So let's wait a couple of days and see where we stand then. > > The tex-common installation failure can be worked around by installing > the context package. > > The vtk6 build on mipsel is now also blocked by gtk+3.0 being > BD-uninstallable on the all architecture, a source-full upload of > gtk+3.0 should resolve that. I've reported this issue in #824999. The vtk6 build for mipsel is finally here, thanks to the tex-common and gtk+3.0 fixes in their latest uploads. >>> >>> And to the fact that I bumped its build priority when gtk+ got fixed :) >> >> I didn't know you could do that. Thank you! >> I did not expect the vtk6 build before the end of the weekend, so I updated a couple of rdeps recently which haven't aged 5 days yet. pktools, qgis & otb need one more day, and postgis needs two. >>> >>> qgis and otb are not in testing so are not a problem. As for pktools, I >>> already >>> urgented it a couple of days ago. Let's see if everything migrates in the >>> next >>> non-crashy britney run. >> >> Shouldn't postgis get an urgent hint too then? > > AFAICS that doesn't depend on gdal-abi-*, only on libgdal. So it doesn't need > to > migrate with the rest of the packages. postgis does indeed not depend on the virtual abi package, so it won't hinder the migration of gdal. Thank again! Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#823667: transition: poppler 0.42
Control: tags -1 confirmed On 10/05/16 14:06, Emilio Pozuelo Monfort wrote: > On 07/05/16 13:34, Pino Toscano wrote: >> Package: release.debian.org >> Severity: normal >> User: release.debian@packages.debian.org >> Usertags: transition >> >> Hi, >> >> I would like to ask a slot for a Poppler 0.42.0 transition. >> Currently there is Poppler 0.42.0 in experimental already. >> >> This transition impacts the existing poppler libraries in the following ways: >> - libpoppler57 → libpoppler60 >> >> Below it is a list of sources which are touched by the transition, and their >> situation, sorted by solutions: >> >> Sources that compile fine, and can be binNMU'ed: >> >> boomaga >> cups-filters >> gambas3 >> gdal >> gdcm >> inkscape >> ipe-tools >> libreoffice >> pdf2djvu >> pdf2htmlex >> popplerkit.framework >> texlive-bin >> texworks >> xpdf >> >> Sources that currently FTBFS: >> >> * calligra >> FTBFS for other reasons, not in testing already (can be ignored) >> >> Other cases: >> >> * derivations >> This source builds a libpoppler-based utility application which is >> only used during the build to generate other data, and no trace of >> that application are left in the resulting arch:all package. >> >> A change in poppler-glib 0.39 is the removal of an unused enum; this so >> far impacted only two sources: >> - ruby-gnome2 (#812677, fixed) >> - python-poppler (#812680) >> OTOH, this issue does not directly affect the libpoppler transition. >> >> I grouped all the bugs mentioned above (even the solved ones) with the >> following usertag: >> https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=p...@debian.org;tag=poppler-0.39 >> https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=p...@debian.org;tag=poppler-0.40 >> https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=p...@debian.org;tag=poppler-0.42 > > Let's wait for a few days until the upcoming gdal upload migrates to testing. Assuming there are no significant build regressions with the new version, you can go ahead. Cheers, Emilio
Processed: Re: Bug#823667: transition: poppler 0.42
Processing control commands: > tags -1 confirmed Bug #823667 [release.debian.org] transition: poppler 0.44 Added tag(s) confirmed. -- 823667: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823667 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#824887: transition: gl2ps
Processing control commands: > tags -1 confirmed Bug #824887 [release.debian.org] transition: gl2ps Added tag(s) confirmed. -- 824887: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824887 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#823669: marked as done (transition: ctemplate 2.3)
Your message dated Fri, 27 May 2016 12:23:51 +0200 with message-id <57482037.60...@debian.org> and subject line Re: Bug#823669: transition: ctemplate 2.3 has caused the Debian Bug report #823669, regarding transition: ctemplate 2.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.) -- 823669: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823669 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: transition Hi, I would like to ask a slot for a transition for ctemplate 2.3. ctemplate 2.3, already in experimental and building fine everywhere, bumped SONAME from libctemplate2 to libctemplate3. The transition involves the following sources: kraft mysql-workbench all of them build fine with the new ctemplate. Ben file: title = "ctemplate"; is_affected = .depends ~ "libctemplate2v5" | .depends ~ "libctemplate3"; is_good = .depends ~ "libctemplate3"; is_bad = .depends ~ "libctemplate2v5"; Thanks, -- Pino --- End Message --- --- Begin Message --- On 10/05/16 13:59, Emilio Pozuelo Monfort wrote: > Control: tags -1 confirmed > > On 07/05/16 13:43, Pino Toscano wrote: >> Package: release.debian.org >> Severity: normal >> User: release.debian@packages.debian.org >> Usertags: transition >> >> Hi, >> >> I would like to ask a slot for a transition for ctemplate 2.3. >> ctemplate 2.3, already in experimental and building fine everywhere, >> bumped SONAME from libctemplate2 to libctemplate3. >> >> The transition involves the following sources: >> >> kraft >> mysql-workbench >> >> all of them build fine with the new ctemplate. > > Go ahead. And it's over. Cheers, Emilio--- End Message ---
Bug#823335: marked as done (transition: gdal)
Your message dated Fri, 27 May 2016 12:23:11 +0200 with message-id <5748200f.80...@debian.org> and subject line Re: Bug#823335: transition: gdal has caused the Debian Bug report #823335, regarding transition: gdal 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.) -- 823335: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823335 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: transition Dear Release Team, For the Debian GIS team I'd like to transition to GDAL 2.1.0. There is no SONAME bump as for 2.0, only the virtual ABI package changed to account for the C++ symbol changes. All reverse dependencies rebuilt successfully with GDAL 2.1.0 from experimental. libgdal-grass doesn't need a binNMU as the 2.1.0 version will be uploaded to unstable instead. The initial upload to experimental is currently in NEW awaiting FTP master review. Ben file: title = "gdal"; is_affected = .depends ~ "gdal-abi-2-0-2" | .depends ~ "gdal-abi-2-1-0"; is_good = .depends ~ "gdal-abi-2-1-0"; is_bad = .depends ~ "gdal-abi-2-0-2"; Transition: gdal libgdal20 (2.0.2+dfsg-5) -> libgdal20 (2.1.0+dfsg-1) gdal-abi-2-0-2 -> gdal-abi-2-1-0 The status of the most recent rebuilds is as follows. dans-gdal-scripts (0.23-5)OK fiona (1.6.3-2) OK gazebo(7.0.0+dfsg-2) OK gmt (5.2.1+dfsg-4) OK imposm(2.6.0+ds-2)OK libcitygml(2.0-2) OK liblas(1.8.0-9) OK libosmium (2.6.1-1) OK mapcache (1.4.1-2) OK mapnik(3.0.11+ds-1) OK mapserver (7.0.1-3) OK merkaartor(0.18.2-7) OK mysql-workbench (6.3.4+dfsg-3) OK ncl (6.3.0-8) OK node-srs (0.4.8+dfsg-2) OK openscenegraph(3.2.3+dfsg1-1) OK osmium(0.0~20160124-b30afd3-1)OK pdal (1.2.0-2) OK postgis (2.2.2+dfsg-1) OK pprepair (0.0~20151110-28dca91-1)OK prepair (0.7-5) OK qlandkartegt (1.8.1+ds-5)OK qmapshack (1.6.1-2) OK rasterio (0.34.0-1) OK saga (2.2.4+dfsg-1) OK sumo (0.25.0+dfsg1-3)OK thuban(1.2.2-10) OK vtk6 (6.2.0+dfsg1-11.1 / 6.3.0+dfsg1-1~exp2) OK / OK xastir(2.0.6-4) OK grass (7.0.4-1) OK osgearth (2.7.0+dfsg-1) OK osmcoastline (2.1.3-1) OK pktools (2.6.6-1) OK pyosmium (2.6.0-1) OK libgdal-grass (2.0.2-2 / 2.1.0-1~exp1)FTBFS / OK qgis (2.14.1+dfsg-2 / 2.14.2+dfsg-1~exp1)OK / OK Kind Regards, Bas --- End Message --- --- Begin Message --- On 27/05/16 11:28, Sebastiaan Couwenberg wrote: > On 05/27/2016 11:25 AM, Emilio Pozuelo Monfort wrote: >> On 27/05/16 11:20, Sebastiaan Couwenberg wrote: >>> On 05/27/2016 11:12 AM, Emilio Pozuelo Monfort wrote: On 27/05/16 01:45, Sebastiaan Couwenberg wrote: > On 05/22/2016 12:20 PM, Sebastiaan Couwenberg wrote: >> On 05/21/2016 11:19 AM, Emilio Pozuelo Monfort wrote: >>> On 20/05/16 16:07, Sebastiaan Couwenberg wrote: On 05/20/2016 11:27 AM, Sebastiaan Couwenberg wrote: > On 05/14/2016 11:30 AM, Bas Couwenberg wrote: >> The vtk6 issue on mipsel remains. texlive-bin (2016.20160513.41080-1) >> fixed the FTBFS on most architectures, but still fails on mips, >> mipsel & >> sparc64. I've reported #824260 for this. > > texlive-bin on mipsel has been fixed, and r-base is now also available > on mipsel which should unblock the mipsel build of vtk6, but that >>>
Bug#824887: transition: gl2ps
Control: tags -1 confirmed On 21/05/16 11:54, Anton Gladky wrote: > Hi Emilio, > > no problem. Is it possible to schedule "gmsh" to be > built after "oce" during the transition? Yes, if I don't forget. BTW did you test that the rdeps build against the new version? If so, then you can go ahead and upload to unstable. Cheers, Emilio
Bug#825518: nmu: mgba_0.4.0+dfsg1-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu mgba_0.4.0+dfsg1-3 . amd64 . unstable . -m "Rebuild against ffmpeg 3.0" Old maintainer upload just passed NEW. Andreas
Bug#825523: jessie-pu: package glusterfs/3.5.2-2+deb8u1
Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu Hello, to fix the bug #824823 I would like to upload glusterfs/3.5.2-2+deb8u2 if you agree with it: diff -Naur '--exclude=.svn' tags/3.5.2-2+deb8u1/debian/changelog branches/jessie/debian/changelog --- tags/3.5.2-2+deb8u1/debian/changelog2015-07-29 23:23:00.579388299 +0200 +++ branches/jessie/debian/changelog2016-05-27 14:55:21.543800538 +0200 @@ -1,3 +1,10 @@ +glusterfs (3.5.2-2+deb8u2) jessie-proposed-updates; urgency=medium + + * Add missing glusterd hook script to glusterfs-server package. +Closes: #824823 + + -- Patrick Matthäi Fri, 27 May 2016 14:35:11 +0200 + glusterfs (3.5.2-2+deb8u1) jessie-proposed-updates; urgency=medium * Add upstream patch 02-nfs-unix-domain-socket-created-as-fifo to fix a bug diff -Naur '--exclude=.svn' tags/3.5.2-2+deb8u1/debian/glusterfs-server.install branches/jessie/debian/glusterfs-server.install --- tags/3.5.2-2+deb8u1/debian/glusterfs-server.install 2015-07-29 23:23:00.507388486 +0200 +++ branches/jessie/debian/glusterfs-server.install 2016-05-27 14:48:23.954671677 +0200 @@ -6,3 +6,4 @@ etc/glusterfs/glusterfs-georep-logrotate etc/glusterfs/gluster-rsyslog-7.2.conf etc/glusterfs/gluster-rsyslog-5.8.conf +extras/hook-scripts/S56glusterd-geo-rep-create-post.sh var/lib/glusterd/hooks/1/gsync-create/post/ -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 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)
Processed: Re: Bug#825523: jessie-pu: package glusterfs/3.5.2-2+deb8u1
Processing control commands: > tags -1 + confirmed Bug #825523 [release.debian.org] jessie-pu: package glusterfs/3.5.2-2+deb8u1 Added tag(s) confirmed. -- 825523: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825523 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#825523: jessie-pu: package glusterfs/3.5.2-2+deb8u1
Control: tags -1 + confirmed On Fri, 2016-05-27 at 14:57 +0200, Patrick Matthäi wrote: > to fix the bug #824823 I would like to upload glusterfs/3.5.2-2+deb8u2 if you > agree with it: The metadata for that bug suggests that it also affects the package in unstable. I can see from looking at the later source package that this isn't the case, but please add an appropriate fixed version to the bug (which really should have been done anyway). > diff -Naur '--exclude=.svn' tags/3.5.2-2+deb8u1/debian/changelog > branches/jessie/debian/changelog > --- tags/3.5.2-2+deb8u1/debian/changelog2015-07-29 23:23:00.579388299 > +0200 > +++ branches/jessie/debian/changelog2016-05-27 14:55:21.543800538 +0200 > @@ -1,3 +1,10 @@ > +glusterfs (3.5.2-2+deb8u2) jessie-proposed-updates; urgency=medium > + > + * Add missing glusterd hook script to glusterfs-server package. > +Closes: #824823 Please go ahead. Regards, Adam
Bug#825523: jessie-pu: package glusterfs/3.5.2-2+deb8u1
Am 27.05.2016 um 15:08 schrieb Adam D. Barratt: > Control: tags -1 + confirmed > > On Fri, 2016-05-27 at 14:57 +0200, Patrick Matthäi wrote: >> to fix the bug #824823 I would like to upload glusterfs/3.5.2-2+deb8u2 if you >> agree with it: > The metadata for that bug suggests that it also affects the package in > unstable. I can see from looking at the later source package that this > isn't the case, but please add an appropriate fixed version to the bug > (which really should have been done anyway). The only affected version is the stable version (later upstream installed the files per default). I already set the fixed header while you wrote this ;) > >> diff -Naur '--exclude=.svn' tags/3.5.2-2+deb8u1/debian/changelog >> branches/jessie/debian/changelog >> --- tags/3.5.2-2+deb8u1/debian/changelog2015-07-29 >> 23:23:00.579388299 +0200 >> +++ branches/jessie/debian/changelog2016-05-27 14:55:21.543800538 +0200 >> @@ -1,3 +1,10 @@ >> +glusterfs (3.5.2-2+deb8u2) jessie-proposed-updates; urgency=medium >> + >> + * Add missing glusterd hook script to glusterfs-server package. >> +Closes: #824823 > Please go ahead. Thanks, uploaded! > > Regards, > > Adam > -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#825530: jessie-pu: package postgresql-9.4/9.4.8-0+deb8u1
Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu Hi, please consider postgresql-9.4/9.4.8-0+deb8u1: postgresql-9.4 (9.4.8-0+deb8u1) jessie; urgency=medium * New upstream bugfix release. -- Christoph Berg Fri, 27 May 2016 14:29:53 +0200 Thanks, Christoph signature.asc Description: PGP signature
Bug#825533: jessie-pu: package postgresql-9.1/9.1.22-0+deb8u1
Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu Hi, please consider postgresql-9.1/9.1.22-0+deb8u1: postgresql-9.1 (9.1.22-0+deb8u1) jessie; urgency=medium * New upstream release: No effective changes for PL/Perl, the version must just be higher than the one in wheezy. -- Christoph Berg Fri, 27 May 2016 16:03:59 +0200 Christoph signature.asc Description: PGP signature
Bug#825518: marked as done (nmu: mgba_0.4.0+dfsg1-3)
Your message dated Fri, 27 May 2016 16:35:54 +0200 with message-id <57485b4a.7050...@debian.org> and subject line Re: Bug#825518: nmu: mgba_0.4.0+dfsg1-3 has caused the Debian Bug report #825518, regarding nmu: mgba_0.4.0+dfsg1-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.) -- 825518: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825518 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 mgba_0.4.0+dfsg1-3 . amd64 . unstable . -m "Rebuild against ffmpeg 3.0" Old maintainer upload just passed NEW. Andreas --- End Message --- --- Begin Message --- On 27/05/16 14:26, Andreas Beckmann wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: binnmu > > nmu mgba_0.4.0+dfsg1-3 . amd64 . unstable . -m "Rebuild against ffmpeg 3.0" > > Old maintainer upload just passed NEW. Scheduled. Emilio--- End Message ---
Bug#825534: jessie-pu: package backuppc/3.3.0-2
Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu Hi! Backuppc is a backup service that can be used to backup SMB shares with the help of smbclient. Unfortunately, a security update of Samba, from 2:4.1.17+dfsg-2+deb8u2 to 2:4.2.10+dfsg-0+deb8u2, broke Backuppc backups and restores because smbclient was completely rewritten with the 4.2 release. Backuppc relied on messages output by smbclient 4.1 to confirm that file transfers were ok. This patch add new regexps in Backuppc, to provide compatibility with smbclient 4.2 and more. Of course, the best would be maybe to patch smbclient, and add some code that was removed in the 4.2 release, since this update may have broken other file backup programs. Best regards, Ludovic -- System Information: Debian Release: 8.4 -- Debdiff diff -u backuppc-3.3.0/lib/BackupPC/CGI/View.pm backuppc-3.3.0/lib/BackupPC/CGI/View.pm --- backuppc-3.3.0/lib/BackupPC/CGI/View.pm +++ backuppc-3.3.0/lib/BackupPC/CGI/View.pm @@ -136,6 +136,10 @@ } $s =~ s/[\n\r]+//g; if ( $s =~ /smb: \\>/ + || $s =~ /^tar:\d+\s/ + || $s =~ /^ NTLMSSP_/ + || $s =~ /^GENSEC backend / + || $s =~ /^doing parameter / || $s =~ /^\s*(\d+) \(\s*\d+\.\d kb\/s\) (.*)$/ || $s =~ /^tar: dumped \d+ files/ || $s =~ /^\s*added interface/i diff -u backuppc-3.3.0/debian/changelog backuppc-3.3.0/debian/changelog --- backuppc-3.3.0/debian/changelog +++ backuppc-3.3.0/debian/changelog @@ -1,3 +1,13 @@ +backuppc (3.3.0-2+deb8u1) stable; urgency=medium + + * Regexps fix for smbclient >= 4.2 to avoid failing SMB backups +and set $Conf{BackupZeroFilesIsFatal} = 0 in the default config.pl. +Workaround for SMB restores: '-d' 5 is now the default for smbclient. +Added some cleanup regexps for SMB backup logs. +Closes: #820963 + + -- Ludovic Drolez Mon, 23 May 2016 6:05:17 +0200 + backuppc (3.3.0-2) unstable; urgency=low * Depends on apache2-utils diff -u backuppc-3.3.0/debian/config.pl.diff backuppc-3.3.0/debian/config.pl.diff --- backuppc-3.3.0/debian/config.pl.diff +++ backuppc-3.3.0/debian/config.pl.diff @@ -1,5 +1,5 @@ config.pl 2005-03-03 23:39:20.0 +0100 -+++ debian/backuppc/etc/backuppc/config.pl 2005-03-03 18:55:02.0 +0100 +--- config.pl 2016-05-25 19:39:59.558740903 +0200 debian/backuppc/etc/backuppc/config.pl 2016-01-06 11:49:00.0 +0100 @@ -41,7 +41,10 @@ # # Host name on which the BackupPC server is running. @@ -12,7 +12,7 @@ # # TCP port number on which the BackupPC server listens for and accepts -@@ -218,7 +218,7 @@ +@@ -224,7 +227,7 @@ # Full path to various commands for archiving # $Conf{SplitPath} = '/usr/bin/split'; @@ -21,7 +21,25 @@ $Conf{CatPath} = '/bin/cat'; $Conf{GzipPath} = '/bin/gzip'; $Conf{Bzip2Path} = '/bin/bzip2'; -@@ -1462,7 +1462,7 @@ +@@ -836,7 +839,7 @@ + # backed up. If you have shares that might be empty (and therefore an + # empty backup is valid) you should set this flag to 0. + # +-$Conf{BackupZeroFilesIsFatal} = 1; ++$Conf{BackupZeroFilesIsFatal} = 0; + + ### + # How to backup a client +@@ -1021,7 +1021,7 @@ + # redirection and pipes; put that in a script if you need it. + # + $Conf{SmbClientRestoreCmd} = '$smbClientPath $host\\$shareName' +-. ' $I_option -U $userName -E -d 1' ++. ' $I_option -U $userName -E -d 5' + . ' -c tarmode\\ full -Tx -'; + + ### +@@ -1572,7 +1575,7 @@ # Full path for ssh. Security caution: normal users should not # allowed to write to this file or directory. # @@ -30,7 +48,7 @@ # # Full path for nmblookup. Security caution: normal users should not -@@ -1919,8 +1919,8 @@ +@@ -2028,13 +2031,13 @@ #$Conf{CgiAdminUsers} = 'craig celia'; #--> administrative users are only craig and celia'. # @@ -41,16 +59,13 @@ # # URL of the BackupPC_Admin CGI script. Used for email messages. -@@ -1925,7 +1925,7 @@ - # - # URL of the BackupPC_Admin CGI script. Used for email messages. # -$Conf{CgiURL} = 'http://XX/backuppc/index.cgi'; +$Conf{CgiURL} = 'http://'.$Conf{ServerHost}.'/backuppc/index.cgi'; # # Language to use. See lib/BackupPC/Lang for the list of supported -@@ -2063,7 +2066,7 @@ +@@ -2076,7 +2079,7 @@ # dates (MM/DD), a value of 2 uses full -MM-DD format, and zero # for international dates (DD/MM). # only in patch2: unchanged: --- backuppc-3.3.0.orig/lib/BackupPC/CGI/Browse.pm +++ backuppc-3.3.0/lib/BackupPC/CGI/Browse.pm @@ -65,7 +65,7 @@ # # default to the newest backup # -if ( !defi
Bug#825534: jessie-pu: package backuppc/3.3.0-2
Control: tags -1 + moreinfo On Fri, 2016-05-27 at 16:47 +0200, Ludovic Drolez wrote: > Backuppc is a backup service that can be used to backup SMB shares with > the help of smbclient. > > Unfortunately, a security update of Samba, from 2:4.1.17+dfsg-2+deb8u2 > to 2:4.2.10+dfsg-0+deb8u2, broke Backuppc backups and restores > because smbclient was completely rewritten with the 4.2 release. > Backuppc relied on messages output by smbclient 4.1 to confirm that > file transfers were ok. > > This patch add new regexps in Backuppc, to provide compatibility with > smbclient 4.2 and more. How do any of these changes relate to the samba update? > +-$Conf{BackupZeroFilesIsFatal} = 1; > ++$Conf{BackupZeroFilesIsFatal} = 0; [...] > - # > - # URL of the BackupPC_Admin CGI script. Used for email messages. > # > -$Conf{CgiURL} = 'http://XX/backuppc/index.cgi'; > +$Conf{CgiURL} = 'http://'.$Conf{ServerHost}.'/backuppc/index.cgi'; [...] > --- backuppc-3.3.0.orig/lib/BackupPC/CGI/Browse.pm > +++ backuppc-3.3.0/lib/BackupPC/CGI/Browse.pm > @@ -65,7 +65,7 @@ > # > # default to the newest backup > # > -if ( !defined($In{num}) && defined(@Backups) && @Backups > 0 ) { > +if ( !defined($In{num}) && @Backups && @Backups > 0 ) { Regards, Adam
Processed: Re: Bug#825534: jessie-pu: package backuppc/3.3.0-2
Processing control commands: > tags -1 + moreinfo Bug #825534 [release.debian.org] jessie-pu: package backuppc/3.3.0-2 Added tag(s) moreinfo. -- 825534: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825534 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#825232: jessie-pu: package nmap/6.47.3+deb8u1
On Wed, 2016-05-25 at 22:07 +0100, Adam D. Barratt wrote: [...] > > > * Moved ndiff.py from zenmap to ndiff, added versioned Breaks/Replaces > > > (Closes: #789776, #789897) I'm assuming you've seen #825528? Regards, Adam
Processed: Re: Bug#825232: jessie-pu: package nmap/6.47.3+deb8u1
Processing control commands: > retitle -1 jessie-pu: package nmap/6.47.3+deb8u2 Bug #825232 [release.debian.org] jessie-pu: package nmap/6.47.3+deb8u1 Changed Bug title to 'jessie-pu: package nmap/6.47.3+deb8u2' from 'jessie-pu: package nmap/6.47.3+deb8u1'. -- 825232: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825232 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#825232: jessie-pu: package nmap/6.47.3+deb8u1
control: retitle -1 jessie-pu: package nmap/6.47.3+deb8u2 Oops, it turns out that I forgot to adjust the Breaks/Replaces relationship between zenmap and ndiff (#825528). A debdiff with a fix is attached. Cheers, -Hilko diff -Nru nmap-6.47/debian/changelog nmap-6.47/debian/changelog --- nmap-6.47/debian/changelog 2016-05-24 22:05:41.0 +0200 +++ nmap-6.47/debian/changelog 2016-05-27 16:09:04.0 +0200 @@ -1,3 +1,9 @@ +nmap (6.47-3+deb8u2) jessie; urgency=medium + + * Fix versioned Breaks/Depends for ndiff (Closes: #825528) + + -- Hilko Bengen Fri, 27 May 2016 17:50:57 +0200 + nmap (6.47-3+deb8u1) jessie; urgency=medium * Added upstream patch to deal with unuseable socks proxy (Closes: diff -Nru nmap-6.47/debian/control nmap-6.47/debian/control --- nmap-6.47/debian/control 2016-05-24 22:01:36.0 +0200 +++ nmap-6.47/debian/control 2016-05-27 16:05:05.0 +0200 @@ -54,8 +54,8 @@ Architecture: all Recommends: nmap Conflicts: nmap (<< ${source:Version}) -Breaks: zenmap (<< 6.47-5~) -Replaces: zenmap (<< 6.47-5~) +Breaks: zenmap (<< 6.47-3+deb8u1~) +Replaces: zenmap (<< 6.47-3+deb8u1~) Depends: ${python:Depends}, ${misc:Depends}, python-lxml, Description: The Network Mapper - result compare utility Ndiff is a tool to aid in the comparison of Nmap scans. It takes two
Bug#825232: jessie-pu: package nmap/6.47.3+deb8u1
On Fri, 2016-05-27 at 18:36 +0200, Hilko Bengen wrote: > control: retitle -1 jessie-pu: package nmap/6.47.3+deb8u2 > > Oops, it turns out that I forgot to adjust the Breaks/Replaces > relationship between zenmap and ndiff (#825528). A debdiff with a fix is > attached. Please go ahead. Regards, Adam
Bug#824887: transition: gl2ps
Thanks, have just uploaded it to unstable. Regards Anton 2016-05-27 12:30 GMT+02:00 Emilio Pozuelo Monfort : > BTW did you test that the rdeps build against the new version? If so, then you > can go ahead and upload to unstable.
Uploading linux (4.5.5-1)
I intend to upload linux version 4.5.5-1 this weekend. This includes a stable update and various security fixes. There shouldn't be any ABI bump. Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus signature.asc Description: This is a digitally signed message part
Bug#824658: jessie-pu: package jakarta-jmeter/2.11-2+deb8u1
Control: tags -1 + confirmed On Wed, 2016-05-18 at 15:55 +0200, Emmanuel Bourg wrote: > I'd like to fix the bug #795356 reported against JMeter. We basically forgot > to install 11 XML files and a DTD in the package, this breaks the creation > of test plans derived from predefined templates. This update also contains > a workaround for a regression introduced in a recent security update of > libxstream-java and breaking the parsing of the templates. Please go ahead. Regards, Adam
Processed: Re: Bug#824658: jessie-pu: package jakarta-jmeter/2.11-2+deb8u1
Processing control commands: > tags -1 + confirmed Bug #824658 [release.debian.org] jessie-pu: package jakarta-jmeter/2.11-2+deb8u1 Added tag(s) confirmed. -- 824658: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824658 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#823911: jessie-pu: package debian-security-support/2016.05.09+nmu1~deb8u1
Control: tags -1 + confirmed On Tue, 2016-05-10 at 12:41 +0200, Santiago Ruano Rincón wrote: > Please find attached the debdiff of a debian-security-support between > current version in Jessie and 2016.05.09+nmu1~deb8u1. The new version: > * updates the list of packages with particular support conditions > * updates French and Spanish l10n. > * includes a new --type earlyend to warn the user about upcoming EOLs. > * closes fixes such as: > > https://bugs.debian.org/819493 FTBFS in jessie. > https://bugs.debian.org/762594 Unify binary package along all suites. > https://bugs.debian.org/809249 Solve missing help > > This version has been uploaded to unstable and wheezy-security. Please go ahead. Regards, Adam
Processed: Re: Bug#823911: jessie-pu: package debian-security-support/2016.05.09+nmu1~deb8u1
Processing control commands: > tags -1 + confirmed Bug #823911 [release.debian.org] jessie-pu: package debian-security-support/2016.05.09+nmu1~deb8u1 Added tag(s) confirmed. -- 823911: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823911 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#822487: jessie-pu: package mathematica-fonts/17+deb8u1
Processing control commands: > tags -1 + confirmed Bug #822487 [release.debian.org] jessie-pu: package mathematica-fonts/17+deb8u1 Added tag(s) confirmed. -- 822487: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822487 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#822487: jessie-pu: package mathematica-fonts/17+deb8u1
Control: tags -1 + confirmed On Mon, 2016-04-25 at 01:05 +0200, Adam Borowski wrote: > Mathematica-fonts is a downloader for a set of fonts from Wolfram. > The version in jessie wants upstream version 7, however, it's no longer > available on their website. This makes the package uninstallable. > The proposed fix is to point the downloader to upstream version 10. > > The debdiff is quite hefty, this includes changed sha512 sums and dropping > no longer provided Type1 fonts. > > There are two unrelated changes: > * adopting the package (Maintainer: the Fonts Team, Uploader: me) > * missing dependency on wget (also RC) > > Debdiff attached, but you probably prefer git: No, we prefer seeing what you're actually proposing to upload. Please go ahead. Regards, Adam
Bug#825297: wheezy-pu: package chrony/1.24-3.1+deb7u4
Control: tags -1 + moreinfo On Wed, 2016-05-25 at 19:58 +0200, Vincent Blut wrote: > Could you please accept chrony 1.24-3.1+deb7u4 in the last wheezy point > release? > > It fixes CVE-2016-1567 which I have backported to that specific upstream > version. It is well tested since the exact same patch has been in > squeeze-lts for a while. Since wheezy-lts started, we've only been accepting wheezy uploads that are regression fixes so would need a compelling reason that this shouldn't simply be fixed via wheezy-lts (I realise this wasn't explicitly mentioned in the announcement). Regards, Adam
Processed: Re: Bug#825297: wheezy-pu: package chrony/1.24-3.1+deb7u4
Processing control commands: > tags -1 + moreinfo Bug #825297 [release.debian.org] wheezy-pu: package chrony/1.24-3.1+deb7u4 Added tag(s) moreinfo. -- 825297: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825297 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#822678: jessie-pu: package partman-ext3/86~deb8u1
On Sat, 2016-05-14 at 18:32 +0100, Adam D. Barratt wrote: > On Sat, 2016-05-14 at 19:17 +0200, Cyril Brulebois wrote: > [...] > > It might be. Having this package in a d-i release for more exposure > > might be a good idea though. I suggest we delay this until after the > > next one has been published (and tested a bit). I don't think we're > > ready for the next point release yet anyway, are we? > > Not yet, but we do need to start considering dates, as it looks like > we'll want to do the wheezy EOL point release and the next jessie point > release together, in order to avoid version skew. d-i's stretch alpha 6 was released in the meantime, and we're approaching the deadline for 8.5. Cyril, would you be happy for the package to be part of 8.5 at this point, or would you prefer to wait for 8.6? Regards, Adam
Bug#822678: jessie-pu: package partman-ext3/86~deb8u1
Adam D. Barratt (2016-05-27): > On Sat, 2016-05-14 at 18:32 +0100, Adam D. Barratt wrote: > > On Sat, 2016-05-14 at 19:17 +0200, Cyril Brulebois wrote: > > [...] > > > It might be. Having this package in a d-i release for more exposure > > > might be a good idea though. I suggest we delay this until after the > > > next one has been published (and tested a bit). I don't think we're > > > ready for the next point release yet anyway, are we? > > > > Not yet, but we do need to start considering dates, as it looks like > > we'll want to do the wheezy EOL point release and the next jessie point > > release together, in order to avoid version skew. > > d-i's stretch alpha 6 was released in the meantime, and we're > approaching the deadline for 8.5. > > Cyril, would you be happy for the package to be part of 8.5 at this > point, or would you prefer to wait for 8.6? I'm not really satisfied with the lack of any replies from Andreas, or with the limited number of days since the alpha 6 release, so I'd say delay; thanks. KiBi. signature.asc Description: Digital signature
Bug#825297: wheezy-pu: package chrony/1.24-3.1+deb7u4
On Fri, May 27, 2016 at 06:24:26PM +0100, Adam D. Barratt wrote: Control: tags -1 + moreinfo On Wed, 2016-05-25 at 19:58 +0200, Vincent Blut wrote: Could you please accept chrony 1.24-3.1+deb7u4 in the last wheezy point release? It fixes CVE-2016-1567 which I have backported to that specific upstream version. It is well tested since the exact same patch has been in squeeze-lts for a while. Since wheezy-lts started, we've only been accepting wheezy uploads that are regression fixes so would need a compelling reason that this shouldn't simply be fixed via wheezy-lts (I realise this wasn't explicitly mentioned in the announcement). Oh ok. As you said, that wasn’t really clear from the announcement that regression fixes only would be acceptable; I will get in touch with LTS folks then. Regards, Adam Thanks for your time Adam, Vincent signature.asc Description: PGP signature
Re: Bug#796823: jessie-pu: package gosa/2.7.4+reloaded2-1+deb8u2
On Wed, May 25, 2016 at 07:22:00PM +0100, Adam D. Barratt wrote: > Please go ahead. uploaded. -- cheers, Holger signature.asc Description: Digital signature
Bug#825297: marked as done (wheezy-pu: package chrony/1.24-3.1+deb7u4)
Your message dated Fri, 27 May 2016 21:30:40 +0200 with message-id <20160527193040.ge3...@betterave.cristau.org> and subject line Re: Bug#825297: wheezy-pu: package chrony/1.24-3.1+deb7u4 has caused the Debian Bug report #825297, regarding wheezy-pu: package chrony/1.24-3.1+deb7u4 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.) -- 825297: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825297 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal Tags: wheezy User: release.debian@packages.debian.org Usertags: pu Hi, Could you please accept chrony 1.24-3.1+deb7u4 in the last wheezy point release? It fixes CVE-2016-1567 which I have backported to that specific upstream version. It is well tested since the exact same patch has been in squeeze-lts for a while. The next fix is an adjustment ensuring we don’t delete the /var/lib/chrony content. That directory contains some really important data, notably the driftfile which stores the gain or loss of the system clock relative to the RTC. Deleting it each time chrony is upgraded or installed from Config-Files state was a mistake; let’s fix that! Thanks for your time, Vincent -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) diff -u chrony-1.24/ntp_core.c chrony-1.24/ntp_core.c --- chrony-1.24/ntp_core.c +++ chrony-1.24/ntp_core.c @@ -966,7 +966,8 @@ if (!KEY_KeyKnown(auth_key_id)) { test5 = 0; } else { -test5 = check_packet_auth(message, auth_key_id); +test5 = check_packet_auth(message, auth_key_id) && +auth_key_id == inst->auth_key_id; } } else { /* If we expect authenticated info from this peer/server and the packet diff -u chrony-1.24/debian/changelog chrony-1.24/debian/changelog --- chrony-1.24/debian/changelog +++ chrony-1.24/debian/changelog @@ -1,3 +1,13 @@ +chrony (1.24-3.1+deb7u4) wheezy; urgency=medium + + * Fix CVE-2016-1567: Restrict authentication of server/peer to specified +key. (Closes: #812923) + + * debian/postrm: +- Remove /var/lib/chrony on purge only. (Closes: #568492) + + -- Vincent Blut Wed, 25 May 2016 17:15:18 +0200 + chrony (1.24-3.1+deb7u3) wheezy-security; urgency=medium * With the following security bugfixes (See: #782160): diff -u chrony-1.24/debian/postrm chrony-1.24/debian/postrm --- chrony-1.24/debian/postrm +++ chrony-1.24/debian/postrm @@ -3,7 +3,6 @@ # postrm for chrony John Hasler 1998-2006 # Any possessor of a copy of this program may treat it as if it # were in the public domain. I waive all rights. -rm -f /var/lib/chrony/* if [ -x update-menus ] ; then update-menus fi diff -u chrony-1.24/debian/applied/series chrony-1.24/debian/applied/series --- chrony-1.24/debian/applied/series +++ chrony-1.24/debian/applied/series @@ -7,0 +8 @@ +14_restrict-authentication-of-server-peer-to-specified-key.patch only in patch2: unchanged: --- chrony-1.24.orig/debian/applied/14_restrict-authentication-of-server-peer-to-specified-key.patch +++ chrony-1.24/debian/applied/14_restrict-authentication-of-server-peer-to-specified-key.patch @@ -0,0 +1,24 @@ +From: Vincent Blut +Date: Tue, 02 Feb 2016 23:29:25 +0100 +Subject: ntp: restrict authentication of server/peer to specified key + +This patch fixes CVE-2016-1567 in chrony 1.24. In versions prior to 1.31.2 as +well as all releases from the 2.x branch before 2.2.1, chrony does not verify +peer associations of symmetric keys when authenticating packets, which might +allow remote attackers to conduct impersonation attacks via an arbitrary +trusted key, aka a "skeleton key". +--- + +diff -urNpa a/chrony-1.24/ntp_core.c b/chrony-1.24/ntp_core.c +--- a/chrony-1.24/ntp_core.c 2016-02-02 23:28:39.070377463 +0100 b/chrony-1.24/ntp_core.c 2016-02-02 23:01:10.414119775 +0100 +@@ -966,7 +966,8 @@ receive_packet(NTP_Packet *message, stru + if (!KEY_KeyKnown(auth_key_id)) { + test5 = 0; + } else { +-test5 = check_packet_auth(message, auth_key_id); ++test5 = check_packet_auth(message, auth_key_id) && ++auth_key_id == inst->auth_key_id; + } + } else { + /* If we expect authenticated info from this peer/server and the packet --- End Message --- --- Begin
Bug#813653: [pkg-php-pear] Bug#813653: jessie-pu: package symfony/2.3.21+dfsg-4+deb8u3
On Thu, Mar 31, 2016 at 23:43:03 +0200, Daniel Beyer wrote: > Hi Julien, > > Can you give a short update regarding the proposed > symfony/2.3.21+dfsg-4+deb8u3, fixing CVE-2016-1902? > It might be a bit late, but it would be great to have this fixed in 8.4, > which is about to be released. > > Do you need any further information from us? > I must admit that I have trouble believing that you'd need 1kloc to add a random_bytes function :( Cheers, Julien
Processed: Re: Bug#825512: jessie-pu: package policykit-1/0.105-15~deb8u1
Processing control commands: > tags -1 + confirmed Bug #825512 [release.debian.org] jessie-pu: package policykit-1/0.105-15~deb8u1 Added tag(s) confirmed. -- 825512: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825512 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#825512: jessie-pu: package policykit-1/0.105-15~deb8u1
Control: tags -1 + confirmed On Fri, 2016-05-27 at 13:06 +0200, Michael Biebl wrote: > we'd like to make a stable upload for policykit-1 in the upcoming jessie > point release. > > The policykit-1 package didn't have a new upstream release in sid, but > we backported a lot of fixes from newer upstream versions, including > quite a few CVEs and important memory leak fixes [1]. > The policykit-1 package in sid is in a much better shape then what we > have in jessie. > > We therefor think it's best to simply upload the current package from > sid, which has been cooking for a very long time, as is to stable. > > I know the debdiff is large but I think the vast majority of the changes > are stable material and it's simply unfeasible to create and test yet > another stack of patches. I would therefor urge you to consider to > accept the attached debdiff. Assuming that the resulting package has been tested on jessie, under the circumstances I'm prepared to trust your judgement. Please go ahead. Regards, Adam
Processed: Re: Bug#824872: jessie-pu: package nspr/2:4.12-2+deb8u1
Processing control commands: > tag -1 moreinfo Bug #824872 [release.debian.org] jessie-pu: package nspr/2:4.12-2+deb8u1 Added tag(s) moreinfo. -- 824872: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824872 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#824872: jessie-pu: package nspr/2:4.12-2+deb8u1
Control: tag -1 moreinfo On Fri, May 20, 2016 at 18:32:41 +0200, Guido Günther wrote: > Hi, > as put out in more detail in > > https://lists.debian.org/debian-release/2016/02/msg00753.html > > we discussed in the LTS and security team the possibility to use the > same NSS and NSPR upstream version in all suites to be able to handle > things like CVE-2014-3566 and CVE-2015-4000 in a consistent manner. > > I'd like to propose this here again via a bug report so we have easier > means of tracking/tagging. Would it be o.k. with the release team to update > nss/nspr to the versions currently in sid/testing and continue to do so > from here on. If it works out for jessie we'll do the same in LTS via > wheezy-security. > In order to increase confidence in the backports I've enabled the > internal testsuites in nspr and nss. > > If this is o.k. I'm happy to attach debdiffs and provide a matching bug > for nss as well. > Hi Guido, I'd want to see debdiffs first. And have some description of what the regression testing looks like, both of the upstream releases and of the debian packages. Cheers, Julien
Bug#820995: jessie-pu: package lvm2/2.02.111-2.2
Control: tags -1 + pending On Sat, 2016-04-23 at 16:38 +0100, Jonathan Wiltshire wrote: > Control: tag -1 confirmed - moreinfo > > On 2016-04-23 02:14, Cyril Brulebois wrote: > > Hi, > > > > Jonathan Wiltshire (2016-04-22): > >> Control: tag -1 moreinfo d-i > >> > >> On Thu, Apr 14, 2016 at 02:18:47PM +0200, Bastian Blank wrote: > >> > +lvm2 (2.02.111-3) UNRELEASED; urgency=medium > >> > + > >> > + * Set default pid directory to /run. (closes: #783120) > >> > + > >> > + -- Bastian Blank Thu, 14 Apr 2016 11:35:55 + > >> > + > >> > >> Seems sensible, but the version should be 2.02.111-2+deb8u1, and the > >> udeb needs a d-i ack. Ccing Cyril. > > > > The fact it's been added only for the deb build, while the udeb one has > > a separate set of options, makes me think d-i shouldn't be affected; so > > no objections. > > Please go ahead with a fixed version number. (Finally) uploaded and flagged for acceptance. Regards, Adam
Processed: Re: Bug#820995: jessie-pu: package lvm2/2.02.111-2.2
Processing control commands: > tags -1 + pending Bug #820995 [release.debian.org] jessie-pu: package lvm2/2.02.111-2.2 Added tag(s) pending. -- 820995: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820995 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#825523: jessie-pu: package glusterfs/3.5.2-2+deb8u1
Control: tags -1 + pending On Fri, 2016-05-27 at 15:23 +0200, Patrick Matthäi wrote: > > Am 27.05.2016 um 15:08 schrieb Adam D. Barratt: [...] > > > +glusterfs (3.5.2-2+deb8u2) jessie-proposed-updates; urgency=medium > > > + > > > + * Add missing glusterd hook script to glusterfs-server package. > > > +Closes: #824823 > > Please go ahead. > > Thanks, uploaded! Flagged for acceptance. Regards, Adam
Processed: Re: Bug#825523: jessie-pu: package glusterfs/3.5.2-2+deb8u1
Processing control commands: > tags -1 + pending Bug #825523 [release.debian.org] jessie-pu: package glusterfs/3.5.2-2+deb8u1 Added tag(s) pending. -- 825523: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825523 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
NEW changes in stable-new
Processing changes file: glusterfs_3.5.2-2+deb8u2_amd64.changes ACCEPT Processing changes file: lvm2_2.02.111-2.2+deb8u1_i386.changes ACCEPT
Bug#796823: jessie-pu: package gosa/2.7.4+reloaded2-1+deb8u2
Control: tags -1 + pending [CCs fixed to have the bug, rather than debian-release@] On Fri, 2016-05-27 at 18:44 +, Holger Levsen wrote: > On Wed, May 25, 2016 at 07:22:00PM +0100, Adam D. Barratt wrote: > > Please go ahead. > > uploaded. Flagged for acceptance. Regards, Adam
Processed: Re: Bug#796823: jessie-pu: package gosa/2.7.4+reloaded2-1+deb8u2
Processing control commands: > tags -1 + pending Bug #796823 [release.debian.org] jessie-pu: package gosa/2.7.4+reloaded2-1+deb8u2 Added tag(s) pending. -- 796823: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796823 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#825530: jessie-pu: package postgresql-9.4/9.4.8-0+deb8u1
Processing control commands: > tags -1 + pending Bug #825530 [release.debian.org] jessie-pu: package postgresql-9.4/9.4.8-0+deb8u1 Added tag(s) pending. -- 825530: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825530 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#825232: jessie-pu: package nmap/6.47.3+deb8u1
On Fri, 2016-05-27 at 17:39 +0100, Adam D. Barratt wrote: > On Fri, 2016-05-27 at 18:36 +0200, Hilko Bengen wrote: > > control: retitle -1 jessie-pu: package nmap/6.47.3+deb8u2 > > > > Oops, it turns out that I forgot to adjust the Breaks/Replaces > > relationship between zenmap and ndiff (#825528). A debdiff with a fix is > > attached. > > Please go ahead. Flagged for acceptance. Regards, Adam
Processed: Re: Bug#825533: jessie-pu: package postgresql-9.1/9.1.22-0+deb8u1
Processing control commands: > tags -1 + pending Bug #825533 [release.debian.org] jessie-pu: package postgresql-9.1/9.1.22-0+deb8u1 Added tag(s) pending. -- 825533: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#825530: jessie-pu: package postgresql-9.4/9.4.8-0+deb8u1
Control: tags -1 + pending On Fri, 2016-05-27 at 16:14 +0200, Christoph Berg wrote: > postgresql-9.4 (9.4.8-0+deb8u1) jessie; urgency=medium > > * New upstream bugfix release. Flagged for acceptance. Regards, Adam
Bug#825533: jessie-pu: package postgresql-9.1/9.1.22-0+deb8u1
Control: tags -1 + pending On Fri, 2016-05-27 at 16:30 +0200, Christoph Berg wrote: > postgresql-9.1 (9.1.22-0+deb8u1) jessie; urgency=medium > > * New upstream release: No effective changes for PL/Perl, the version must > just be higher than the one in wheezy. Flagged for acceptance. Regards, Adam
NEW changes in stable-new
Processing changes file: gosa_2.7.4+reloaded2-1+deb8u2_amd64.changes ACCEPT Processing changes file: libgd2_2.1.0-5+deb8u2_amd64.changes ACCEPT Processing changes file: libgd2_2.1.0-5+deb8u2_arm64.changes ACCEPT Processing changes file: libgd2_2.1.0-5+deb8u2_armel.changes ACCEPT Processing changes file: libgd2_2.1.0-5+deb8u2_armhf.changes ACCEPT Processing changes file: libgd2_2.1.0-5+deb8u2_i386.changes ACCEPT Processing changes file: libgd2_2.1.0-5+deb8u2_mips.changes ACCEPT Processing changes file: libgd2_2.1.0-5+deb8u2_mipsel.changes ACCEPT Processing changes file: libgd2_2.1.0-5+deb8u2_powerpc.changes ACCEPT Processing changes file: libgd2_2.1.0-5+deb8u2_ppc64el.changes ACCEPT Processing changes file: libgd2_2.1.0-5+deb8u2_s390x.changes ACCEPT Processing changes file: libgd2_2.1.0-5+deb8u3_amd64.changes ACCEPT Processing changes file: libgd2_2.1.0-5+deb8u3_arm64.changes ACCEPT Processing changes file: libgd2_2.1.0-5+deb8u3_armel.changes ACCEPT Processing changes file: libgd2_2.1.0-5+deb8u3_armhf.changes ACCEPT Processing changes file: libgd2_2.1.0-5+deb8u3_i386.changes ACCEPT Processing changes file: libgd2_2.1.0-5+deb8u3_mips.changes ACCEPT Processing changes file: libgd2_2.1.0-5+deb8u3_mipsel.changes ACCEPT Processing changes file: libgd2_2.1.0-5+deb8u3_powerpc.changes ACCEPT Processing changes file: libgd2_2.1.0-5+deb8u3_ppc64el.changes ACCEPT Processing changes file: libgd2_2.1.0-5+deb8u3_s390x.changes ACCEPT Processing changes file: nmap_6.47-3+deb8u2_amd64.changes ACCEPT Processing changes file: postgresql-9.1_9.1.22-0+deb8u1_amd64.changes ACCEPT Processing changes file: postgresql-9.4_9.4.8-0+deb8u1_amd64.changes ACCEPT
NEW changes in stable-new
Processing changes file: glusterfs_3.5.2-2+deb8u2_arm64.changes ACCEPT Processing changes file: glusterfs_3.5.2-2+deb8u2_i386.changes ACCEPT Processing changes file: glusterfs_3.5.2-2+deb8u2_powerpc.changes ACCEPT Processing changes file: glusterfs_3.5.2-2+deb8u2_ppc64el.changes ACCEPT Processing changes file: glusterfs_3.5.2-2+deb8u2_s390x.changes ACCEPT Processing changes file: lvm2_2.02.111-2.2+deb8u1_amd64.changes ACCEPT Processing changes file: lvm2_2.02.111-2.2+deb8u1_arm64.changes ACCEPT Processing changes file: lvm2_2.02.111-2.2+deb8u1_powerpc.changes ACCEPT Processing changes file: lvm2_2.02.111-2.2+deb8u1_ppc64el.changes ACCEPT Processing changes file: lvm2_2.02.111-2.2+deb8u1_s390x.changes ACCEPT Processing changes file: nmap_6.47-3+deb8u2_arm64.changes ACCEPT Processing changes file: nmap_6.47-3+deb8u2_armel.changes ACCEPT Processing changes file: nmap_6.47-3+deb8u2_armhf.changes ACCEPT Processing changes file: nmap_6.47-3+deb8u2_i386.changes ACCEPT Processing changes file: nmap_6.47-3+deb8u2_mips.changes ACCEPT Processing changes file: nmap_6.47-3+deb8u2_mipsel.changes ACCEPT Processing changes file: nmap_6.47-3+deb8u2_powerpc.changes ACCEPT Processing changes file: nmap_6.47-3+deb8u2_ppc64el.changes ACCEPT Processing changes file: nmap_6.47-3+deb8u2_s390x.changes ACCEPT Processing changes file: postgresql-9.1_9.1.22-0+deb8u1_arm64.changes ACCEPT Processing changes file: postgresql-9.1_9.1.22-0+deb8u1_armel.changes ACCEPT Processing changes file: postgresql-9.1_9.1.22-0+deb8u1_armhf.changes ACCEPT Processing changes file: postgresql-9.1_9.1.22-0+deb8u1_i386.changes ACCEPT Processing changes file: postgresql-9.1_9.1.22-0+deb8u1_mipsel.changes ACCEPT Processing changes file: postgresql-9.1_9.1.22-0+deb8u1_powerpc.changes ACCEPT Processing changes file: postgresql-9.1_9.1.22-0+deb8u1_ppc64el.changes ACCEPT Processing changes file: postgresql-9.1_9.1.22-0+deb8u1_s390x.changes ACCEPT Processing changes file: postgresql-9.4_9.4.8-0+deb8u1_arm64.changes ACCEPT Processing changes file: postgresql-9.4_9.4.8-0+deb8u1_i386.changes ACCEPT Processing changes file: postgresql-9.4_9.4.8-0+deb8u1_powerpc.changes ACCEPT Processing changes file: postgresql-9.4_9.4.8-0+deb8u1_ppc64el.changes ACCEPT Processing changes file: postgresql-9.4_9.4.8-0+deb8u1_s390x.changes ACCEPT
NEW changes in stable-new
Processing changes file: glusterfs_3.5.2-2+deb8u2_armel.changes ACCEPT Processing changes file: glusterfs_3.5.2-2+deb8u2_armhf.changes ACCEPT Processing changes file: lvm2_2.02.111-2.2+deb8u1_armel.changes ACCEPT Processing changes file: lvm2_2.02.111-2.2+deb8u1_armhf.changes ACCEPT Processing changes file: postgresql-9.1_9.1.22-0+deb8u1_mips.changes ACCEPT
NEW changes in stable-new
Processing changes file: postgresql-9.4_9.4.8-0+deb8u1_armhf.changes ACCEPT
NEW changes in stable-new
Processing changes file: postgresql-9.4_9.4.8-0+deb8u1_armel.changes ACCEPT Processing changes file: postgresql-9.4_9.4.8-0+deb8u1_mipsel.changes ACCEPT
NEW changes in stable-new
Processing changes file: glusterfs_3.5.2-2+deb8u2_mips.changes ACCEPT Processing changes file: glusterfs_3.5.2-2+deb8u2_mipsel.changes ACCEPT Processing changes file: lvm2_2.02.111-2.2+deb8u1_mips.changes ACCEPT Processing changes file: lvm2_2.02.111-2.2+deb8u1_mipsel.changes ACCEPT