Bug#836447: transition: proj
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Control: forwarded -1 https://release.debian.org/transitions/html/auto-proj.html PROJ.4 4.9.3 has been released and bumps the SOVERSION from 9 to 12, requiring a transition. We've had the release candidates in experimental for a little while already, and the issues identified with those have already been fixed in unstable. Only gpx2shp needed a patch to support the renamed PI defines in projects.h from proj 4.9.3. All reverse dependencies rebuilt successfully with the new proj packages from experimental (as summarized below), except mapnik (3.0.11+ds-1) in unstable because it lacks support for Boost 1.61 (#833756), the mapnik 3.0.12 release candidates in experimental do support Boost 1.61. Mapnik 3.0.11 is scheduled for automatic removal from testing on 2016-09-21, unfortunately I don't expect the 3.0.12 final release before that time. Please also schedule binNMUs for the affected packages in experimental if those have not yet moved to unstable when the transition starts. spatialite (4.4.0~rc1-1~exp1) spatialite-tools (4.4.0~rc1-1~exp1), grass(7.0.5~rc1-1~exp1) mapnik (3.0.12~rc6+ds-1~exp2) python-mapnik(1:0.0~20160810-3a60211-1~exp1), I will move the new pdal & qgis packages from experimental to unstable today. Transition: proj libproj9 (4.9.2-3) -> libproj12 (4.9.3-1~exp1) The status of the most recent rebuilds is as follows. gpx2shp (0.71.0-4) OK libgeo-proj4-perl (1.05-3)OK libgeotiff-dfsg (1.4.2-2) OK ogdi-dfsg (3.2.0+ds-1)OK openorienteering-mapper (0.6.3-2) OK pdl (1:2.016-4) OK proj-rdnap (2008-5)OK python-pyproj (1.9.5.1-2) OK shapelib(1.3.0-8) OK sosi2osm(1.0.0-3) OK spatialite (4.3.0a-5 / 4.4.0~rc1-1~exp1) OK / OK survex (1.2.27-1) OK zygrib (7.0.0-4) OK gdal(2.1.1+dfsg-1) OK magics++(2.29.2-1) OK pyspatialite(3.0.1-11) OK spatialite-gui (2.0.0~devel2-4)OK spatialite-tools(4.3.0-2 / 4.4.0~rc1-1~exp1)OK / OK cdo (1.7.2+dfsg.1-1)OK dans-gdal-scripts (0.23-6)OK grass (7.0.4-3 / 7.0.5~rc1-1~exp1)OK / OK libosmium (2.8.0-2) OK mapcache(1.4.1-3) OK mapnik (3.0.11+ds-1 / 3.0.12~rc4+ds-1~exp1) FTBFS / OK mapproxy(1.9.0-3) OK mapserver (7.0.1-3) OK merkaartor (0.18.3-1) OK metview (4.6.7-1) OK ncl (6.3.0-11) OK otb (5.6.1+dfsg-1) OK pdal(1.3.0-1) OK postgis (2.2.2+dfsg-4) OK qlandkartegt(1.8.1+ds-6)OK qmapshack (1.6.3-1) OK saga(2.3.1+dfsg-1) OK sumo(0.27.1+dfsg1-1)OK thuban (1.2.2-11) OK vtk6(6.3.0+dfsg1-1) OK xastir (2.0.8-2) OK ifrit (4.1.2-5) OK libgdal-grass (2.1.1-2) OK osm2pgsql (0.90.1+ds-1) OK python-mapnik (1:0.0~20160531-f65767a-1 / 1:0.0~20160810-3a60211-1~exp1) OK / OK qgis(2.14.6+dfsg-1) OK therion (5.3.16-10) OK Kind Regards, Bas
Processed: transition: proj
Processing control commands: > forwarded -1 https://release.debian.org/transitions/html/auto-proj.html Bug #836447 [release.debian.org] transition: proj Set Bug forwarded-to-address to 'https://release.debian.org/transitions/html/auto-proj.html'. -- 836447: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836447 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#836447: transition: proj
Processing control commands: > tags -1 confirmed Bug #836447 [release.debian.org] transition: proj Added tag(s) confirmed. -- 836447: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836447 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#836447: transition: proj
Control: tags -1 confirmed On 03/09/16 11:29, Bas Couwenberg wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > Control: forwarded -1 > https://release.debian.org/transitions/html/auto-proj.html > > PROJ.4 4.9.3 has been released and bumps the SOVERSION from 9 to 12, > requiring a transition. > > We've had the release candidates in experimental for a little while > already, and the issues identified with those have already been fixed in > unstable. Only gpx2shp needed a patch to support the renamed PI defines > in projects.h from proj 4.9.3. > > All reverse dependencies rebuilt successfully with the new proj packages > from experimental (as summarized below), except mapnik (3.0.11+ds-1) in > unstable because it lacks support for Boost 1.61 (#833756), the mapnik > 3.0.12 release candidates in experimental do support Boost 1.61. > Mapnik 3.0.11 is scheduled for automatic removal from testing on > 2016-09-21, unfortunately I don't expect the 3.0.12 final release before > that time. > > Please also schedule binNMUs for the affected packages in experimental > if those have not yet moved to unstable when the transition starts. > > spatialite (4.4.0~rc1-1~exp1) > spatialite-tools (4.4.0~rc1-1~exp1), > grass(7.0.5~rc1-1~exp1) > mapnik (3.0.12~rc6+ds-1~exp2) > python-mapnik(1:0.0~20160810-3a60211-1~exp1), > > I will move the new pdal & qgis packages from experimental to unstable > today. > > > Transition: proj > > libproj9 (4.9.2-3) -> libproj12 (4.9.3-1~exp1) > > The status of the most recent rebuilds is as follows. > > gpx2shp (0.71.0-4) OK > libgeo-proj4-perl (1.05-3)OK > libgeotiff-dfsg (1.4.2-2) OK > ogdi-dfsg (3.2.0+ds-1)OK > openorienteering-mapper (0.6.3-2) OK > pdl (1:2.016-4) OK > proj-rdnap (2008-5)OK > python-pyproj (1.9.5.1-2) OK > shapelib(1.3.0-8) OK > sosi2osm(1.0.0-3) OK > spatialite (4.3.0a-5 / 4.4.0~rc1-1~exp1) OK / OK > survex (1.2.27-1) OK > zygrib (7.0.0-4) OK > > gdal(2.1.1+dfsg-1) OK > magics++(2.29.2-1) OK > pyspatialite(3.0.1-11) OK > spatialite-gui (2.0.0~devel2-4)OK > spatialite-tools(4.3.0-2 / 4.4.0~rc1-1~exp1)OK / OK > > cdo (1.7.2+dfsg.1-1)OK > dans-gdal-scripts (0.23-6)OK > grass (7.0.4-3 / 7.0.5~rc1-1~exp1)OK / OK > libosmium (2.8.0-2) OK > mapcache(1.4.1-3) OK > mapnik (3.0.11+ds-1 / > 3.0.12~rc4+ds-1~exp1) FTBFS / OK > mapproxy(1.9.0-3) OK > mapserver (7.0.1-3) OK > merkaartor (0.18.3-1) OK > metview (4.6.7-1) OK > ncl (6.3.0-11) OK > otb (5.6.1+dfsg-1) OK > pdal(1.3.0-1) OK > postgis (2.2.2+dfsg-4) OK > qlandkartegt(1.8.1+ds-6)OK > qmapshack (1.6.3-1) OK > saga(2.3.1+dfsg-1) OK > sumo(0.27.1+dfsg1-1)OK > thuban (1.2.2-11) OK > vtk6(6.3.0+dfsg1-1) OK > xastir (2.0.8-2) OK > > ifrit (4.1.2-5) OK > libgdal-grass (2.1.1-2) OK > osm2pgsql (0.90.1+ds-1) OK > python-mapnik (1:0.0~20160531-f65767a-1 / > 1:0.0~20160810-3a60211-1~exp1) OK / OK > qgis(2.14.6+dfsg-1) OK > therion (5.3.16-10) OK Sounds good. Please go ahead. Emilio
Bug#835170: transition: protobuf
On 02/09/16 11:48, Sebastiaan Couwenberg wrote: > protobuf (3.0.0-7) has been uploaded to unstable which contains a patch > to fix the ostinato build failure (#). > > Can you schedule a dep-wait to rebuild ostinato (0.8-1) with > libprotobuf-dev (3.0.0-7) once that's available on the buildds? Scheduled. Emilio
Bug#836447: transition: proj
On 09/03/2016 11:49 AM, Emilio Pozuelo Monfort wrote: > On 03/09/16 11:29, Bas Couwenberg wrote: >> Package: release.debian.org >> Severity: normal >> User: release.debian@packages.debian.org >> Usertags: transition >> Control: forwarded -1 >> https://release.debian.org/transitions/html/auto-proj.html >> >> PROJ.4 4.9.3 has been released and bumps the SOVERSION from 9 to 12, >> requiring a transition. >> >> We've had the release candidates in experimental for a little while >> already, and the issues identified with those have already been fixed in >> unstable. Only gpx2shp needed a patch to support the renamed PI defines >> in projects.h from proj 4.9.3. >> >> All reverse dependencies rebuilt successfully with the new proj packages >> from experimental (as summarized below), except mapnik (3.0.11+ds-1) in >> unstable because it lacks support for Boost 1.61 (#833756), the mapnik >> 3.0.12 release candidates in experimental do support Boost 1.61. >> Mapnik 3.0.11 is scheduled for automatic removal from testing on >> 2016-09-21, unfortunately I don't expect the 3.0.12 final release before >> that time. >> >> Please also schedule binNMUs for the affected packages in experimental >> if those have not yet moved to unstable when the transition starts. >> >> spatialite (4.4.0~rc1-1~exp1) >> spatialite-tools (4.4.0~rc1-1~exp1), >> grass(7.0.5~rc1-1~exp1) >> mapnik (3.0.12~rc6+ds-1~exp2) >> python-mapnik(1:0.0~20160810-3a60211-1~exp1), >> >> I will move the new pdal & qgis packages from experimental to unstable >> today. >> >> >> Transition: proj >> >> libproj9 (4.9.2-3) -> libproj12 (4.9.3-1~exp1) >> >> The status of the most recent rebuilds is as follows. >> >> gpx2shp (0.71.0-4) OK >> libgeo-proj4-perl (1.05-3)OK >> libgeotiff-dfsg (1.4.2-2) OK >> ogdi-dfsg (3.2.0+ds-1)OK >> openorienteering-mapper (0.6.3-2) OK >> pdl (1:2.016-4) OK >> proj-rdnap (2008-5)OK >> python-pyproj (1.9.5.1-2) OK >> shapelib(1.3.0-8) OK >> sosi2osm(1.0.0-3) OK >> spatialite (4.3.0a-5 / 4.4.0~rc1-1~exp1) OK / OK >> survex (1.2.27-1) OK >> zygrib (7.0.0-4) OK >> >> gdal(2.1.1+dfsg-1) OK >> magics++(2.29.2-1) OK >> pyspatialite(3.0.1-11) OK >> spatialite-gui (2.0.0~devel2-4)OK >> spatialite-tools(4.3.0-2 / 4.4.0~rc1-1~exp1)OK / OK >> >> cdo (1.7.2+dfsg.1-1)OK >> dans-gdal-scripts (0.23-6)OK >> grass (7.0.4-3 / 7.0.5~rc1-1~exp1)OK / OK >> libosmium (2.8.0-2) OK >> mapcache(1.4.1-3) OK >> mapnik (3.0.11+ds-1 / >> 3.0.12~rc4+ds-1~exp1) FTBFS / OK >> mapproxy(1.9.0-3) OK >> mapserver (7.0.1-3) OK >> merkaartor (0.18.3-1) OK >> metview (4.6.7-1) OK >> ncl (6.3.0-11) OK >> otb (5.6.1+dfsg-1) OK >> pdal(1.3.0-1) OK >> postgis (2.2.2+dfsg-4) OK >> qlandkartegt(1.8.1+ds-6)OK >> qmapshack (1.6.3-1) OK >> saga(2.3.1+dfsg-1) OK >> sumo(0.27.1+dfsg1-1)OK >> thuban (1.2.2-11) OK >> vtk6(6.3.0+dfsg1-1) OK >> xastir (2.0.8-2) OK >> >> ifrit (4.1.2-5) OK >> libgdal-grass (2.1.1-2) OK >> osm2pgsql (0.90.1+ds-1) OK >> python-mapnik (1:0.0~20160531-f65767a-1 / >> 1:0.0~20160810-3a60211-1~exp1) OK / OK >> qgis(2.14.6+dfsg-1) OK >> therion (5.3.16-10) OK > > Sounds good. Please go ahead. Thanks for the super quick feedback. I'll move proj from experimental to unstable later today after I have done the same for pdal, python-pdal & qgis. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88
Bug#836370: transition: shibboleth
I'm finished with the uploads. Xmltooling, opensaml2 and shibboleth-sp2 all built on the testing architectures. Please trigger rebuilds of shibboleth-resolver and moonshot-gss-eap (possibly also opensaml2 on powerpcspe, if you handle ports). -- Thanks, Feri
Bug#836506: nmu: fcitx-fbterm_0.2.0-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Hi, As noticed by Jeremy Bicha, fcitx-fbterm needs a rebuild to catch up with current fcitx libraries because it still depends on the transitional package fcitx-libs, thus I'm submitting this request. nmu fcitx-fbterm_0.2.0-2 . ANY . unstable . -m "Rebuild against fcitx 1:4.2.9.1-2 for correct dependencies" Regards, Aron
NEW changes in stable-new
Processing changes file: libarchive_3.1.2-11+deb8u2_multi.changes ACCEPT Processing changes file: libarchive_3.1.2-11+deb8u2_amd64.changes ACCEPT Processing changes file: libarchive_3.1.2-11+deb8u2_arm64.changes ACCEPT Processing changes file: libarchive_3.1.2-11+deb8u2_armel.changes ACCEPT Processing changes file: libarchive_3.1.2-11+deb8u2_armhf.changes ACCEPT Processing changes file: libarchive_3.1.2-11+deb8u2_i386.changes ACCEPT Processing changes file: libarchive_3.1.2-11+deb8u2_mips.changes ACCEPT Processing changes file: libarchive_3.1.2-11+deb8u2_mipsel.changes ACCEPT Processing changes file: libarchive_3.1.2-11+deb8u2_powerpc.changes ACCEPT Processing changes file: libarchive_3.1.2-11+deb8u2_ppc64el.changes ACCEPT Processing changes file: libarchive_3.1.2-11+deb8u2_s390x.changes ACCEPT Processing changes file: libidn_1.29-1+deb8u2_allonly.changes ACCEPT Processing changes file: libidn_1.29-1+deb8u2_amd64.changes ACCEPT Processing changes file: libidn_1.29-1+deb8u2_arm64.changes ACCEPT Processing changes file: libidn_1.29-1+deb8u2_armel.changes ACCEPT Processing changes file: libidn_1.29-1+deb8u2_armhf.changes ACCEPT Processing changes file: libidn_1.29-1+deb8u2_i386.changes ACCEPT Processing changes file: libidn_1.29-1+deb8u2_mips.changes ACCEPT Processing changes file: libidn_1.29-1+deb8u2_mipsel.changes ACCEPT Processing changes file: libidn_1.29-1+deb8u2_powerpc.changes ACCEPT Processing changes file: libidn_1.29-1+deb8u2_ppc64el.changes ACCEPT Processing changes file: libidn_1.29-1+deb8u2_s390x.changes ACCEPT Processing changes file: tryton-server_3.4.0-3+deb8u2_amd64.changes ACCEPT
Bug#815036: transition: msgpack-c
On Wed, Aug 31, 2016 at 05:01:33PM +0200, Emilio Pozuelo Monfort wrote: > On 27/08/16 04:39, James McCoy wrote: > > On Sat, Aug 13, 2016 at 10:10:29AM -0400, James McCoy wrote: > >> On Tue, Jun 14, 2016 at 06:17:31PM -0400, James McCoy wrote: > >>> + libdata-messagepack-perl has a fix upstream but no "stable" release > >>> including it > > > > There is now an actual upstream release with the msgpack-c changes. > > > >>> + libdata-messagepack-stream-perl could be NMUed once > >>> libdata-messagepack-perl is available. > >> > >> No activity on either of these. > >> > >> They're only used by libcatmandu-store-lucy-perl and > >> libtext-xslate-perl, which have no rdeps. Should I bump the severity of > >> these bugs or suggest removing them? > > > > I've pinged these bugs and got responses that the Perl folks would be ok > > with those two packages being removed from testing (not unstable since > > packaging was done in response to an RFP) to help the transition and > > possibly bring visibility to the needed maintenance. > > > > Given that there's been some activity upstream around these packages, > > I'm a little more confident about performing NMUs than I had been. > > > > Thoughts on how to proceed? > > Upload msgpack-c to unstable, then you bump the remaining bugs to RC. Done. The tmate maintainer is going to move the compatible version from experimental to unstable today. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#833634: jessie-pu: package apache2/2.4.10-10+deb8u6
Control: tags -1 + pending On Sun, 2016-08-28 at 14:53 +0100, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On Sun, 2016-08-07 at 13:20 +0200, Stefan Fritsch wrote: > > apache2 (2.4.10-10+deb8u6) jessie; urgency=medium > > > > * Fix race condition and logical error in init script. Thanks to Thomas > > Stangner for the patch. Closes: #822144 > > * Remove links to manpages.debian.org in default index.html to avoid > > broken robots doing a DoS on the site. Closes: #821313 > > * mod_socache_memcache: Increase idle timeout to 15s to allow keep-alive > > connections. Closes: #803035 > > * mod_proxy_fcgi: Fix wrong behavior with 304 responses. Closes: #827472 > > * Correct systemd-sysv-generator behavior by customizing some parameters. > > This fixes 'systemctl status' returning incorrect results. > > Closes: #827444 > > * mod_proxy_html: Add missing config file mods-available/proxy_html.conf. > > This is intentionally not enabled during upgrade, to make it less > > likely to break existing setups. It will be enabled by a > > a2dismod/a2enmod > > cycle, though. Closes: #827258 > > Please go ahead. Uploaded and flagged for acceptance. Regards, Adam
Bug#833345: jessie-pu: package piuparts/0.62+deb8u1
Control: tags -1 + pending On Fri, 2016-09-02 at 18:28 +, Holger Levsen wrote: > On Fri, Sep 02, 2016 at 06:58:19PM +0100, Adam D. Barratt wrote: > > Please go ahead. > > thanks, uploaded. Flagged for acceptance; thanks. Regards, Adam
Processed: Re: Bug#833634: jessie-pu: package apache2/2.4.10-10+deb8u6
Processing control commands: > tags -1 + pending Bug #833634 [release.debian.org] jessie-pu: package apache2/2.4.10-10+deb8u6 Added tag(s) pending. -- 833634: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833634 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#834326: jessie-pu: package gnupg/1.4.18-7+deb8u2
Control: tags -1 + pending Hi, On Fri, 2016-09-02 at 22:50 +0200, Salvatore Bonaccorso wrote: > Hi Adam, > > On Fri, Sep 02, 2016 at 09:10:48PM +0100, Adam D. Barratt wrote: > > Control: tags -1 - moreinfo > > > > On Fri, 2016-09-02 at 20:58 +0200, Cyril Brulebois wrote: > > > Hi, > > > > > > Adam D. Barratt (2016-09-02): > > > > On Thu, 2016-08-18 at 07:25 +0200, Salvatore Bonaccorso wrote: > > > > > Control: retitle -1 jessie-pu: package gnupg/1.4.18-7+deb8u3 > > > > > > > > > > On Sun, Aug 14, 2016 at 03:58:28PM +0200, Salvatore Bonaccorso wrote: > > > > > > I would like to propose the following hardening to src:gnupg which > > > > > > was > > > > > > found during the analysis of a vulnerability report to the security > > > > > > team > > > > > > and related to > > > > > > https://www.usenix.org/system/files/conference/usenixsecurity16/sec16_paper_razavi.pdf > > > > > > and developed by NIIBE Yutaka. The underlying problem in hardware > > > > > > cannot > > > > > > be solved in software (and thus we don't want to issue a DSA for > > > > > > it, and > > > > > > give possibly this false impression), and as pointed out by Florian > > > > > > there are some other open questions regarding the paper and the > > > > > > attacks > > > > > > described there. > > > > [...] > > > > > This all stil holds, but I have rebased the patch on top of the update > > > > > via jessie-security. > > > > > > > > Overall I think I'm happy to trust the maintainers on this, but would > > > > like a KiBi-ack due to d-i making use of at least gpgv. > > > > > > Yeah, looks sane enough; I'd be slightly happier if it could reach p-u > > > sooner rather than later (ideally before the 8th), just to make sure > > > nothing explodes within d-i. > > > > Thanks. Salvatore, please feel free to upload. > > Thanks, uploaded! Flagged for acceptance into p-u; thanks. Regards, Adam
Processed: Re: Bug#834326: jessie-pu: package gnupg/1.4.18-7+deb8u2
Processing control commands: > tags -1 + pending Bug #834326 [release.debian.org] jessie-pu: package gnupg/1.4.18-7+deb8u3 Added tag(s) pending. -- 834326: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834326 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#834327: jessie-pu: package gnupg2/2.0.26-6+deb8u1
Control: tags -1 + pending Hi, On Fri, 2016-09-02 at 22:45 +0200, Salvatore Bonaccorso wrote: > Hi Adam, > > On Fri, Sep 02, 2016 at 09:11:21PM +0100, Adam D. Barratt wrote: > > Control: tags -1 -moreinfo +confirmed > > > > On Fri, 2016-09-02 at 18:57 +0100, Adam D. Barratt wrote: > > > Control: tags -1 + moreinfo > > > > > > On Sun, 2016-08-14 at 16:00 +0200, Salvatore Bonaccorso wrote: > > > > I would like to propose the following hardening to src:gnupg2 which was > > > > found during the analysis of a vulnerability report to the security team > > > > and related to > > > > https://www.usenix.org/system/files/conference/usenixsecurity16/sec16_paper_razavi.pdf > > > > and developed by NIIBE Yutaka. The underlying problem in hardware cannot > > > > be solved in software (and thus we don't want to issue a DSA for it, and > > > > give possibly this false impression), and as pointed out by Florian > > > > there are some other open questions regarding the paper and the attacks > > > > described there. > > > > > > I'd like to treat this and the corresponding gnupg update as a unit > > > (taking both or neither) so holding for now. > > > > As that was confirmed, please go ahead. > > Thanks! Uploaded. Flagged for acceptance; thanks. Regards, Adam
Processed: Re: Bug#833595: jessie-pu: package nullmailer/1.13-1+deb8u1
Processing control commands: > tags -1 + pending Bug #833595 [release.debian.org] jessie-pu: package nullmailer/1.13-1+deb8u1 Added tag(s) pending. -- 833595: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833595 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#833595: jessie-pu: package nullmailer/1.13-1+deb8u1
Control: tags -1 + pending On Sun, 2016-08-28 at 14:29 +0100, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On Sat, 2016-08-06 at 19:45 +0200, Christian Hofstaedtler wrote: > > #831813 is an rc-bug in nullmailer, which, for some configurations, > > keeps username/passwords in the debconf db. I've fixed this in > > unstable as an NMU; Security has suggested doing the same for jessie > > in a point release. > > Please go ahead. Uploaded and flagged for acceptance. Regards, Adam
Processed: Re: Bug#834327: jessie-pu: package gnupg2/2.0.26-6+deb8u1
Processing control commands: > tags -1 + pending Bug #834327 [release.debian.org] jessie-pu: package gnupg2/2.0.26-6+deb8u1 Added tag(s) pending. -- 834327: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834327 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#833345: jessie-pu: package piuparts/0.62+deb8u1
Processing control commands: > tags -1 + pending Bug #833345 [release.debian.org] jessie-pu: package piuparts/0.62+deb8u1 Added tag(s) pending. -- 833345: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833345 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
NEW changes in stable-new
Processing changes file: apache2_2.4.10-10+deb8u6_amd64.changes ACCEPT Processing changes file: gnupg_1.4.18-7+deb8u3_allonly.changes ACCEPT Processing changes file: gnupg2_2.0.26-6+deb8u1_allonly.changes ACCEPT Processing changes file: nullmailer_1.13-1+deb8u1_source.changes ACCEPT Processing changes file: piuparts_0.62+deb8u1_amd64.changes ACCEPT Processing changes file: systemd_215-17+deb8u5_amd64.changes ACCEPT
Bug#834419: jessie-pu: package glibc/2.19-18+deb8u6
Control: tags -1 + confirmed On Thu, 2016-09-01 at 09:26 +0200, Aurelien Jarno wrote: > On 2016-08-28 16:54, Aurelien Jarno wrote: > > On 2016-08-28 14:59, Adam D. Barratt wrote: > > > On Fri, 2016-08-19 at 11:23 +0200, Aurelien Jarno wrote: > > > > On 2016-08-15 15:29, Aurelien Jarno wrote: > > > [...] > > > > > I would like to upload a new glibc package for the next jessie > > > > > release. > > > > > > > > In the meantime a new security issue (CVE-2016-6323) has been found and > > > > backported to the upstream 2.19 stable branch. I would like to also > > > > include this change into the jessie upload. You will find updated diff > > > > and debdiff attached. > > > > > > The Security Tracker suggests that the issue applies to glibc in > > > unstable and is not yet fixed there; is that correct? > > > > This is indeed correct. This fix is in our git tree ready for the 2.24-1 > > upload, but it hasn't happened yet as we are waiting for a transition > > slot (see #834855). > > The transition has started, so this issue is now fixed in unstable. Thanks; please go ahead. Regards, Adam
Processed: Re: Bug#834419: jessie-pu: package glibc/2.19-18+deb8u6
Processing control commands: > tags -1 + confirmed Bug #834419 [release.debian.org] jessie-pu: package glibc/2.19-18+deb8u6 Added tag(s) confirmed. -- 834419: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834419 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#832336: jessie-pu: package systemd/215-17+deb8u5
Processing control commands: > tags -1 + pending Bug #832336 [release.debian.org] jessie-pu: package systemd/215-17+deb8u5 Added tag(s) pending. -- 832336: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832336 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#832336: jessie-pu: package systemd/215-17+deb8u5
Control: tags -1 + pending On Sat, 2016-09-03 at 00:09 +0200, Michael Biebl wrote: > Am 02.09.2016 um 22:12 schrieb Adam D. Barratt: > > Sorry for the delays. I've been arguing with myself about the fsck fix > > as well, but I'd be happy for the remainder to be uploaded. > > Ok then, uploaded with that one particular change backed out. Thanks; flagged for acceptance into p-u. Regards, Adam
Bug#836530: nmu: lazarus_1.6+dfsg-4
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 See bug 826300 for background. glibc 2.23 broke the FreePascal stack on powerpc. The issue is now fixed in fpc, but AFAICT every package in the stack needs to be rebuild, starting with lazarus. nmu lazarus_1.6+dfsg-4 . powerpc . unstable . -m "rebuild with fpc 3.0.0+dfsg-7 to fix glibc > 2.23 related issues" Do you want me to file the binNMU requests for the rest of the stack separately, or does it work to mention it here? Please wait until lazarus has been rebuilt. (I am not sure if I got the version for hedgewars good, as it already had two NMUs before). nmu cqrlog_2.0.1-1 . powerpc . unstable . -m "rebuild with fpc 3.0.0+dfsg-7 to fix glibc > 2.23 related issues" nmu dozzaqueux_3.42-1 . powerpc . unstable . -m "rebuild with fpc 3.0.0+dfsg-7 to fix glibc > 2.23 related issues" nmu easymp3gain_0.5.0+svn135-6 . powerpc . unstable . -m "rebuild with fpc 3.0.0+dfsg-7 to fix glibc > 2.23 related issues" nmu gearhead_1.302-1 . powerpc . unstable . -m "rebuild with fpc 3.0.0+dfsg-7 to fix glibc > 2.23 related issues" nmu gearhead2_0.628-1 . powerpc . unstable . -m "rebuild with fpc 3.0.0+dfsg-7 to fix glibc > 2.23 related issues" nmu hedgewars_0.9.22-dfsg-7+b2 . powerpc . unstable . -m "rebuild with fpc 3.0.0+dfsg-7 to fix glibc > 2.23 related issues" nmu imapcopy_1.04-2 . powerpc . unstable . -m "rebuild with fpc 3.0.0+dfsg-7 to fix glibc > 2.23 related issues" nmu mricron_0.20140804.1~dfsg.1-1 . powerpc . unstable . -m "rebuild with fpc 3.0.0+dfsg-7 to fix glibc > 2.23 related issues" nmu nbc_1.2.1.r4+dfsg-1 . powerpc . unstable . -m "rebuild with fpc 3.0.0+dfsg-7 to fix glibc > 2.23 related issues" nmu optgeo_2.23-1 . powerpc . unstable . -m "rebuild with fpc 3.0.0+dfsg-7 to fix glibc > 2.23 related issues" nmu pasdoc_0.14.0-1 . powerpc . unstable . -m "rebuild with fpc 3.0.0+dfsg-7 to fix glibc > 2.23 related issues" nmu transgui_5.0.1-4 . powerpc . unstable . -m "rebuild with fpc 3.0.0+dfsg-7 to fix glibc > 2.23 related issues" nmu tuxcmd_0.6.70+dfsg-2 . powerpc . unstable . -m "rebuild with fpc 3.0.0+dfsg-7 to fix glibc > 2.23 related issues" nmu vmg_3.7.1-2 . powerpc . unstable . -m "rebuild with fpc 3.0.0+dfsg-7 to fix glibc > 2.23 related issues" nmu ztex-bmp_20120314-2 . powerpc . unstable . -m "rebuild with fpc 3.0.0+dfsg-7 to fix glibc > 2.23 related issues" Kind regards, Paul - -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (60, 'unstable'), (50, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJXyyJWAAoJEJxcmesFvXUKcv0IAMNSxVSgOjJuhmrEErF7ClXL 8ZxRwglAWIrJxUBzUUdIscjGaHtaqM4hBh7Rqr6A1r03H4ygoXluXIGnuIHSQOY4 a8mGxSgo/S1k73l+gtuPkUryAfrzUGJG54dHWrZDyE8E7fWbEpfzmDeU3huw+FZc 7ifwZg54z/15mdfgafy5VR/zd2zIT4DuqMAYtrbJ2ZlCiogecmv4PqaQQ4ywAj54 YDc1P+yNvzYa5QKYzUZEwhHutV4div1D1JY0rLqCOBoZLW1XKaVPhvDny8h2avRe EN7Q+BH6SEBXMBLW0HhIpL5QOWmjlWRRGgW+0r/hzqimuHJYV2wE4OuIkvovdMo= =UGJg -END PGP SIGNATURE-
Bug#836447: transition: proj
On 09/03/2016 12:14 PM, Sebastiaan Couwenberg wrote: > On 09/03/2016 11:49 AM, Emilio Pozuelo Monfort wrote: >> On 03/09/16 11:29, Bas Couwenberg wrote: >>> Package: release.debian.org >>> Severity: normal >>> User: release.debian@packages.debian.org >>> Usertags: transition >>> Control: forwarded -1 >>> https://release.debian.org/transitions/html/auto-proj.html >>> >>> PROJ.4 4.9.3 has been released and bumps the SOVERSION from 9 to 12, >>> requiring a transition. >>> >>> We've had the release candidates in experimental for a little while >>> already, and the issues identified with those have already been fixed in >>> unstable. Only gpx2shp needed a patch to support the renamed PI defines >>> in projects.h from proj 4.9.3. >>> >>> All reverse dependencies rebuilt successfully with the new proj packages >>> from experimental (as summarized below), except mapnik (3.0.11+ds-1) in >>> unstable because it lacks support for Boost 1.61 (#833756), the mapnik >>> 3.0.12 release candidates in experimental do support Boost 1.61. >>> Mapnik 3.0.11 is scheduled for automatic removal from testing on >>> 2016-09-21, unfortunately I don't expect the 3.0.12 final release before >>> that time. >>> >>> Please also schedule binNMUs for the affected packages in experimental >>> if those have not yet moved to unstable when the transition starts. >>> >>> spatialite (4.4.0~rc1-1~exp1) >>> spatialite-tools (4.4.0~rc1-1~exp1), >>> grass(7.0.5~rc1-1~exp1) >>> mapnik (3.0.12~rc6+ds-1~exp2) >>> python-mapnik(1:0.0~20160810-3a60211-1~exp1), >>> >>> I will move the new pdal & qgis packages from experimental to unstable >>> today. >>> >>> >>> Transition: proj >>> >>> libproj9 (4.9.2-3) -> libproj12 (4.9.3-1~exp1) >>> >>> The status of the most recent rebuilds is as follows. >>> >>> gpx2shp (0.71.0-4) OK >>> libgeo-proj4-perl (1.05-3)OK >>> libgeotiff-dfsg (1.4.2-2) OK >>> ogdi-dfsg (3.2.0+ds-1)OK >>> openorienteering-mapper (0.6.3-2) OK >>> pdl (1:2.016-4) OK >>> proj-rdnap (2008-5)OK >>> python-pyproj (1.9.5.1-2) OK >>> shapelib(1.3.0-8) OK >>> sosi2osm(1.0.0-3) OK >>> spatialite (4.3.0a-5 / 4.4.0~rc1-1~exp1) OK / OK >>> survex (1.2.27-1) OK >>> zygrib (7.0.0-4) OK >>> >>> gdal(2.1.1+dfsg-1) OK >>> magics++(2.29.2-1) OK >>> pyspatialite(3.0.1-11) OK >>> spatialite-gui (2.0.0~devel2-4)OK >>> spatialite-tools(4.3.0-2 / 4.4.0~rc1-1~exp1)OK / OK >>> >>> cdo (1.7.2+dfsg.1-1)OK >>> dans-gdal-scripts (0.23-6)OK >>> grass (7.0.4-3 / 7.0.5~rc1-1~exp1)OK / OK >>> libosmium (2.8.0-2) OK >>> mapcache(1.4.1-3) OK >>> mapnik (3.0.11+ds-1 / >>> 3.0.12~rc4+ds-1~exp1) FTBFS / OK >>> mapproxy(1.9.0-3) OK >>> mapserver (7.0.1-3) OK >>> merkaartor (0.18.3-1) OK >>> metview (4.6.7-1) OK >>> ncl (6.3.0-11) OK >>> otb (5.6.1+dfsg-1) OK >>> pdal(1.3.0-1) OK >>> postgis (2.2.2+dfsg-4) OK >>> qlandkartegt(1.8.1+ds-6)OK >>> qmapshack (1.6.3-1) OK >>> saga(2.3.1+dfsg-1) OK >>> sumo(0.27.1+dfsg1-1)OK >>> thuban (1.2.2-11) OK >>> vtk6(6.3.0+dfsg1-1) OK >>> xastir (2.0.8-2) OK >>> >>> ifrit (4.1.2-5) OK >>> libgdal-grass (2.1.1-2) OK >>> osm2pgsql (0.90.1+ds-1) OK >>> python-mapnik (1:0.0~20160531-f65767a-1 / >>> 1:0.0~20160810-3a60211-1~exp1) OK / OK >>> qgis(2.14.6+dfsg-1) OK >>> therion (5.3.16-10) OK >> >> Sounds good. Please go ahead. > > Thanks for the super quick feedback. I'll move proj from experimental to > unstable later today after I have done th
Bug#834419: jessie-pu: package glibc/2.19-18+deb8u6
On 2016-09-03 19:18, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On Thu, 2016-09-01 at 09:26 +0200, Aurelien Jarno wrote: > > On 2016-08-28 16:54, Aurelien Jarno wrote: > > > On 2016-08-28 14:59, Adam D. Barratt wrote: > > > > On Fri, 2016-08-19 at 11:23 +0200, Aurelien Jarno wrote: > > > > > On 2016-08-15 15:29, Aurelien Jarno wrote: > > > > [...] > > > > > > I would like to upload a new glibc package for the next jessie > > > > > > release. > > > > > > > > > > In the meantime a new security issue (CVE-2016-6323) has been found > > > > > and > > > > > backported to the upstream 2.19 stable branch. I would like to also > > > > > include this change into the jessie upload. You will find updated diff > > > > > and debdiff attached. > > > > > > > > The Security Tracker suggests that the issue applies to glibc in > > > > unstable and is not yet fixed there; is that correct? > > > > > > This is indeed correct. This fix is in our git tree ready for the 2.24-1 > > > upload, but it hasn't happened yet as we are waiting for a transition > > > slot (see #834855). > > > > The transition has started, so this issue is now fixed in unstable. > > Thanks; please go ahead. > Thanks, I have just uploaded it. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
NEW changes in stable-new
Processing changes file: apache2_2.4.10-10+deb8u6_arm64.changes ACCEPT Processing changes file: apache2_2.4.10-10+deb8u6_armel.changes ACCEPT Processing changes file: apache2_2.4.10-10+deb8u6_armhf.changes ACCEPT Processing changes file: apache2_2.4.10-10+deb8u6_i386.changes ACCEPT Processing changes file: apache2_2.4.10-10+deb8u6_mips.changes ACCEPT Processing changes file: apache2_2.4.10-10+deb8u6_mipsel.changes ACCEPT Processing changes file: apache2_2.4.10-10+deb8u6_powerpc.changes ACCEPT Processing changes file: apache2_2.4.10-10+deb8u6_ppc64el.changes ACCEPT Processing changes file: apache2_2.4.10-10+deb8u6_s390x.changes ACCEPT Processing changes file: gnupg_1.4.18-7+deb8u3_amd64.changes ACCEPT Processing changes file: gnupg_1.4.18-7+deb8u3_arm64.changes ACCEPT Processing changes file: gnupg_1.4.18-7+deb8u3_armhf.changes ACCEPT Processing changes file: gnupg_1.4.18-7+deb8u3_i386.changes ACCEPT Processing changes file: gnupg_1.4.18-7+deb8u3_mips.changes ACCEPT Processing changes file: gnupg_1.4.18-7+deb8u3_mipsel.changes ACCEPT Processing changes file: gnupg_1.4.18-7+deb8u3_powerpc.changes ACCEPT Processing changes file: gnupg_1.4.18-7+deb8u3_ppc64el.changes ACCEPT Processing changes file: gnupg_1.4.18-7+deb8u3_s390x.changes ACCEPT Processing changes file: gnupg2_2.0.26-6+deb8u1_amd64.changes ACCEPT Processing changes file: gnupg2_2.0.26-6+deb8u1_arm64.changes ACCEPT Processing changes file: gnupg2_2.0.26-6+deb8u1_armhf.changes ACCEPT Processing changes file: gnupg2_2.0.26-6+deb8u1_i386.changes ACCEPT Processing changes file: gnupg2_2.0.26-6+deb8u1_mips.changes ACCEPT Processing changes file: gnupg2_2.0.26-6+deb8u1_mipsel.changes ACCEPT Processing changes file: gnupg2_2.0.26-6+deb8u1_powerpc.changes ACCEPT Processing changes file: gnupg2_2.0.26-6+deb8u1_ppc64el.changes ACCEPT Processing changes file: gnupg2_2.0.26-6+deb8u1_s390x.changes ACCEPT Processing changes file: nullmailer_1.13-1+deb8u1_amd64.changes ACCEPT Processing changes file: nullmailer_1.13-1+deb8u1_arm64.changes ACCEPT Processing changes file: nullmailer_1.13-1+deb8u1_armhf.changes ACCEPT Processing changes file: nullmailer_1.13-1+deb8u1_i386.changes ACCEPT Processing changes file: nullmailer_1.13-1+deb8u1_mips.changes ACCEPT Processing changes file: nullmailer_1.13-1+deb8u1_mipsel.changes ACCEPT Processing changes file: nullmailer_1.13-1+deb8u1_powerpc.changes ACCEPT Processing changes file: nullmailer_1.13-1+deb8u1_ppc64el.changes ACCEPT Processing changes file: nullmailer_1.13-1+deb8u1_s390x.changes ACCEPT Processing changes file: systemd_215-17+deb8u5_arm64.changes ACCEPT Processing changes file: systemd_215-17+deb8u5_i386.changes ACCEPT Processing changes file: systemd_215-17+deb8u5_powerpc.changes ACCEPT Processing changes file: systemd_215-17+deb8u5_ppc64el.changes ACCEPT Processing changes file: systemd_215-17+deb8u5_s390x.changes ACCEPT
NEW changes in stable-new
Processing changes file: gnupg_1.4.18-7+deb8u3_armel.changes ACCEPT Processing changes file: gnupg2_2.0.26-6+deb8u1_armel.changes ACCEPT Processing changes file: nullmailer_1.13-1+deb8u1_armel.changes ACCEPT Processing changes file: systemd_215-17+deb8u5_armhf.changes ACCEPT Processing changes file: systemd_215-17+deb8u5_mips.changes ACCEPT Processing changes file: systemd_215-17+deb8u5_mipsel.changes ACCEPT
NEW changes in stable-new
Processing changes file: systemd_215-17+deb8u5_armel.changes ACCEPT
Bug#836571: jessie-pu: package rabbitvcs/0.16-1
Package: release.debian.org
Severity: critical
Tags: patch
User: release.debian@packages.debian.org
Usertags: pu
The attached patch fixes bug #817231 in the rabbitvcs package. This is
classified as a critical bug on the grounds that it can cause serious data loss
(e.g. loss of entire home folder). There are several reports of this actually
happening to users of the software on Debian and other systems:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817231
https://github.com/rabbitvcs/rabbitvcs/issues/127
http://askubuntu.com/questions/473433/rabbitsvn-deleted-all-my-folders
https://github.com/rabbitvcs/rabbitvcs/issues/70
Bug #817231 has now been closed in unstable. Given the nature of the bug, I
thought perhaps it should also be fixed in jessie-updates? The attached patch
acheives this. (I understand that the distribution needs to be set to jessie in
debian/changelog, rather than {jessie|stable}-updates[0].)
I am not a Debian Developer so would require a sponsor.
[0] https://lists.debian.org/debian-devel/2015/06/msg00307.html
Thanks.
Christopher Hoskin
diff -Nru rabbitvcs-0.16/debian/changelog rabbitvcs-0.16/debian/changelog
--- rabbitvcs-0.16/debian/changelog 2014-10-05 10:21:39.0 +0100
+++ rabbitvcs-0.16/debian/changelog 2016-09-04 07:09:07.0 +0100
@@ -1,3 +1,10 @@
+rabbitvcs (0.16-1.1) jessie; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix "All files in home folder removed" Applied upstream fix as patch (Closes: #817231)
+
+ -- Christopher Hoskin Sun, 04 Sep 2016 07:08:46 +0100
+
rabbitvcs (0.16-1) unstable; urgency=medium
* Team upload.
diff -Nru rabbitvcs-0.16/debian/patches/fix-817231.patch rabbitvcs-0.16/debian/patches/fix-817231.patch
--- rabbitvcs-0.16/debian/patches/fix-817231.patch 1970-01-01 01:00:00.0 +0100
+++ rabbitvcs-0.16/debian/patches/fix-817231.patch 2016-09-04 07:05:41.0 +0100
@@ -0,0 +1,38 @@
+Subject: Repository Browser export empties target folder
+ A critical bug, where when the user attempts to export files from within the
+ RabbitVCS Repository Browser to a local target folder, the contents of the
+ target folder are deleted without warning, and the export fails.
+Origin: upstream, https://github.com/rabbitvcs/rabbitvcs/pull/89/commits/b3dc98601d57d2e58e491a66b562a399ce1a
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817231
+Bug: https://github.com/rabbitvcs/rabbitvcs/issues/70
+Bug: https://github.com/rabbitvcs/rabbitvcs/issues/127
+Bug: https://github.com/rabbitvcs/rabbitvcs/issues/161
+From: abaheti
+Acked-by: Christopher Hoskin
+Last-Update: 2016-08-28
+Applied-Upstream: commit:b3dc986, https://github.com/rabbitvcs/rabbitvcs/pull/89/commits/b3dc98601d57d2e58e491a66b562a399ce1a
+
+---
+ rabbitvcs/vcs/svn/__init__.py | 6 +-
+ 1 file changed, 1 insertion(+), 5 deletions(-)
+
+diff --git a/rabbitvcs/vcs/svn/__init__.py b/rabbitvcs/vcs/svn/__init__.py
+index 96d821d..dee5e7f 100644
+--- a/rabbitvcs/vcs/svn/__init__.py
b/rabbitvcs/vcs/svn/__init__.py
+@@ -1237,11 +1237,7 @@ class SVN:
+ @param recurse: Whether or not to run a recursive checkout.
+
+ """
+-if os.path.exists(dest_path):
+-if os.path.isdir(dest_path):
+-shutil.rmtree(dest_path)
+-else:
+-os.remove(dest_path)
++revision=Revision("head")
+
+
+
+--
+2.9.3
+
diff -Nru rabbitvcs-0.16/debian/patches/series rabbitvcs-0.16/debian/patches/series
--- rabbitvcs-0.16/debian/patches/series 2014-10-05 10:12:07.0 +0100
+++ rabbitvcs-0.16/debian/patches/series 2016-09-04 07:05:41.0 +0100
@@ -1 +1,2 @@
99_setup.py.patch
+fix-817231.patch
