Bug#821343: RM: zotero-standalone-build/4.0.22-1
Le dimanche 17 avril 2016 à 22:21 +0100, Adam D. Barratt a écrit : > Control: tags -1 + jessie moreinfo > > On Sun, 2016-04-17 at 23:06 +0200, Sébastien Villemot wrote: > > > > Please remove zotero-standalone-build from jessie. The package is > > affected by > > two RC bugs (#795343, #788277) which are not easy to address via a > > minimal > > patch. > > > > I'll try to provide a backport. In the meantime, packages directly > > taken from > > stretch are working fine. > There's a reverse dependency, which would need addressing: > > Checking reverse dependencies... > # Broken Depends: > lyz: xul-ext-lyz This is a Zotero plugin for LyX. Given that zotero is currently unusable in jessie, I don't see how xul-ext-lyz could be functional. So a removal should also be warranted. -- .''`.Sébastien Villemot : :' :Debian Developer `. `' http://sebastien.villemot.name `- GPG Key: 4096R/381A7594 signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#821343: RM: zotero-standalone-build/4.0.22-1
Processing commands for cont...@bugs.debian.org: > tags 821343 + jessie Bug #821343 [release.debian.org] RM: zotero-standalone-build/4.0.22-1 Ignoring request to alter tags of bug #821343 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 821343: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821343 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#821343: RM: zotero-standalone-build/4.0.22-1
Control: tags -1 + jessie moreinfo On Sun, 2016-04-17 at 23:06 +0200, Sébastien Villemot wrote: > Please remove zotero-standalone-build from jessie. The package is affected by > two RC bugs (#795343, #788277) which are not easy to address via a minimal > patch. > > I'll try to provide a backport. In the meantime, packages directly taken from > stretch are working fine. There's a reverse dependency, which would need addressing: Will remove the following packages from stable: libreoffice-zotero-integration | 4.0.22-1 | all xul-ext-zotero | 4.0.22-1 | all zotero-standalone | 4.0.22-1 | all zotero-standalone-build | 4.0.22-1 | source Maintainer: Michele Cane --- Reason --- -- Checking reverse dependencies... # Broken Depends: lyz: xul-ext-lyz Dependency problem found. Regards, Adam
Processed: Re: Bug#821343: RM: zotero-standalone-build/4.0.22-1
Processing control commands: > tags -1 + jessie moreinfo Bug #821343 [release.debian.org] RM: zotero-standalone-build/4.0.22-1 Added tag(s) jessie and moreinfo. -- 821343: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821343 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#821343: RM: zotero-standalone-build/4.0.22-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Dear Release Team, Please remove zotero-standalone-build from jessie. The package is affected by two RC bugs (#795343, #788277) which are not easy to address via a minimal patch. I'll try to provide a backport. In the meantime, packages directly taken from stretch are working fine. Cheers, -- .''`.Sébastien Villemot : :' :Debian Developer `. `' http://sebastien.villemot.name `- GPG Key: 4096R/381A7594 signature.asc Description: PGP signature
Bug#819282: wheezy-pu: package openldap/2.4.31-2+deb7u2
Control: tags -1 -moreinfo +confirmed On Sun, 2016-04-17 at 13:22 -0700, Ryan Tandy wrote: > On Wed, Apr 13, 2016 at 09:30:13PM +0100, Adam D. Barratt wrote: > >Does a significant portion of the testsuite fail, or only a small part? > > Exactly one third of it: the same suite is run once for each of the backends > built, namely bdb, hdb, and mdb. The page size issue renders mdb totally > non-functional under the newer kernel. > > >If the latter, is it possible to only disable the affected tests? > > Actually, yes. Improved debdiff below; and sorry for not thinking of this > myself. Thanks; that looks fine to me. Regards, Adam
Processed: Re: Bug#819282: wheezy-pu: package openldap/2.4.31-2+deb7u2
Processing control commands: > tags -1 -moreinfo +confirmed Bug #819282 [release.debian.org] wheezy-pu: package openldap/2.4.31-2+deb7u2 Removed tag(s) moreinfo. Bug #819282 [release.debian.org] wheezy-pu: package openldap/2.4.31-2+deb7u2 Added tag(s) confirmed. -- 819282: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819282 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#819282: wheezy-pu: package openldap/2.4.31-2+deb7u2
On Wed, Apr 13, 2016 at 09:30:13PM +0100, Adam D. Barratt wrote: Does a significant portion of the testsuite fail, or only a small part? Exactly one third of it: the same suite is run once for each of the backends built, namely bdb, hdb, and mdb. The page size issue renders mdb totally non-functional under the newer kernel. If the latter, is it possible to only disable the affected tests? Actually, yes. Improved debdiff below; and sorry for not thinking of this myself. (The diff doesn't have as much context as I'd like: the debian/rules addition is just appended to the end of the file.) As before: - built locally on amd64, verified all three test suites were run - built on the powerpc porterbox (partch), verified bdb and hdb test suites were run but not mdb - tested amd64 binaries in a clean wheezy chroot - tested powerpc binaries in a qemu VM running wheezy (all backends) thanks, Ryan diff -u openldap-2.4.31/debian/rules openldap-2.4.31/debian/rules --- openldap-2.4.31/debian/rules +++ openldap-2.4.31/debian/rules @@ -174,0 +175,6 @@ + +# Avoid running back-mdb tests on ppc64 builders +ifeq ($(DEB_HOST_ARCH),powerpc) +override_dh_auto_test: + dh_auto_test -- BUILD_MDB=no +endif diff -u openldap-2.4.31/debian/changelog openldap-2.4.31/debian/changelog --- openldap-2.4.31/debian/changelog +++ openldap-2.4.31/debian/changelog @@ -1,3 +1,11 @@ +openldap (2.4.31-2+deb7u2) wheezy; urgency=medium + + * Disable the back-mdb test suite on powerpc to work around back-mdb tests +failing on buildds running the jessie ppc64 kernel, which uses 64KB pages. +(ITS#7713) + + -- Ryan Tandy Thu, 14 Apr 2016 20:55:33 -0700 + openldap (2.4.31-2+deb7u1) wheezy-security; urgency=high * Non-maintainer upload by the Security Team.
Bug#820731: transition: ffmpeg
On 2016-04-15 09:32:52, Emilio Pozuelo Monfort wrote: > Control: tags -1 confirmed > > On 11/04/16 21:13, Sebastian Ramacher 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-ffmpeg.html > > Control: block -1 by 803833 803844 803868 803822 803835 803866 803867 > > 807853 803813 > > > > ffmpeg 3.0 has been uploaded to experimental and bumped SONAME of all its > > shared > > libraries. The FTBFS bugs of the reverse dependencies are tracked at [1]. > > Currently the following packages FTBFS against ffmpeg 3.0: > > > > #803813 ffmpegthumbs > > #803822 gst-libav1.0 > > #803833 libavg > > #803835 libextractor > > #803844 mplayer > > #803866 vcmi > > #803867 vdr-plugin-softhddevice > > #803868 vlc > > #807853 k3b > > > > vlc will move to an embedded copy of ffmpeg 2.8 once this transition starts > > (the > > security team has been informed about this, see #803868 for details). > > > > I will ping all the bugs to upload fixes now that ffmpeg 3.0 is available in > > experimental. > > > > Please let me know once it's okay to upload ffmpeg to unstable. > > Go ahead. Uploaded … > Please bump the bugs to serious when you upload. … and bumped all to serious. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
NEW changes in oldstable-new
Processing changes file: gtk+3.0_3.4.2-7+deb7u1_mipsel.changes ACCEPT
Bug#821326: jessie-pu: package initramfs-tools/0.120+deb8u2
Package: release.debian.org Severity: normal Tags: jessie patch User: release.debian@packages.debian.org Usertags: pu This update fixes: - Regression when upgrading Linux to version 4.4+ if / or /usr is on an NVMe device (#807000) - Regression in version 0.119 if there are non-scripts (such as .svn directories) under /etc/initramfs-tools/scripts (#814965) Both of these regressions cause boot failure on the affected systems. debdiff is below. Ben. diff -Nru initramfs-tools-0.120+deb8u1/debian/changelog initramfs-tools-0.120+deb8u2/debian/changelog --- initramfs-tools-0.120+deb8u1/debian/changelog 2016-02-20 15:51:48.0 + +++ initramfs-tools-0.120+deb8u2/debian/changelog 2016-04-17 18:20:20.0 +0100 @@ -1,3 +1,12 @@ +initramfs-tools (0.120+deb8u2) jessie; urgency=medium + + * [7863219] hook-functions: Include drivers/nvme in block driver modules +(Closes: #807000) + * [fcef753] hook-functions: Create ORDER files even if there are no valid +scripts (Closes: #814965) + + -- Ben Hutchings Sun, 17 Apr 2016 18:20:09 +0100 + initramfs-tools (0.120+deb8u1) jessie; urgency=medium [ Ben Hutchings ] diff -Nru initramfs-tools-0.120+deb8u1/hook-functions initramfs-tools-0.120+deb8u2/hook-functions --- initramfs-tools-0.120+deb8u1/hook-functions 2016-02-20 15:43:54.0 + +++ initramfs-tools-0.120+deb8u2/hook-functions 2016-04-17 17:58:11.0 +0100 @@ -581,6 +581,7 @@ ;; block) copy_modules_dir kernel/drivers/block + copy_modules_dir kernel/drivers/nvme ;; ubi) modules="$modules deflate zlib lzo ubi ubifs" @@ -723,6 +724,7 @@ initdir=${DESTDIR}${scriptdir} [ ! -d ${initdir} ] && return + > ${initdir}/ORDER runlist=$(get_prereq_pairs | tsort) for crs_x in ${runlist}; do [ -f ${initdir}/${crs_x} ] || continue -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.5.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Re: initramfs-tools support for nvme in Linux 4.4+
On Sun, 2016-04-17 at 17:48 +0200, Philipp Kern wrote: > On Sun, Apr 17, 2016 at 01:16:42AM +0100, Ben Hutchings wrote: > > > > By default, initramfs-tools includes various classes of driver modules > > in the initramfs based on the directory they are installed in. In > > particular, most block drivers that don't belong to another subsystem > > such as SCSI are installed in > > /lib/modules//kernel/drivers/block. That installation > > directory is derived from the subdirectory in the Linux source tree > > that contains the driver source. > > > > Unfortunately the nvme driver moved from drivers/block to drivers/nvme > > in Linux 4.4, and initramfs-tools only knows about this since v0.121. > > So long as you install the kernel and initramfs-tools from the same > > suite, everything is fine, but if you use jessie and install a newer > > kernel from jessie-backports or build your own custom kernel, nvme will > > be missing. > > > > The obvious approach of adding initramfs-tools to jessie-backports > > won't work, as the current version requires upgrading busybox, > > e2fsprogs, klibc and (for those that still use it) sysvinit. > > > > The fix is a one-liner and works for old and new kernels. Does this > > seem suitable for inclusion in the next jessie point release? > Just considering nvme in addition to block and gracefully coping with it > not existing seems fine to me. Thanks. I'll prepare an update fixing this (#807000). I'll also fix bug #814965 - the underlying bug is old but it was harmless until a change in version 0.119 ("Always generate ORDER files in mkinitramfs"). Ben. -- Ben Hutchings Make three consecutive correct guesses and you will be considered an expert. signature.asc Description: This is a digitally signed message part
Re: initramfs-tools support for nvme in Linux 4.4+
On Sun, Apr 17, 2016 at 01:16:42AM +0100, Ben Hutchings wrote: > By default, initramfs-tools includes various classes of driver modules > in the initramfs based on the directory they are installed in. In > particular, most block drivers that don't belong to another subsystem > such as SCSI are installed in > /lib/modules//kernel/drivers/block. That installation > directory is derived from the subdirectory in the Linux source tree > that contains the driver source. > > Unfortunately the nvme driver moved from drivers/block to drivers/nvme > in Linux 4.4, and initramfs-tools only knows about this since v0.121. > So long as you install the kernel and initramfs-tools from the same > suite, everything is fine, but if you use jessie and install a newer > kernel from jessie-backports or build your own custom kernel, nvme will > be missing. > > The obvious approach of adding initramfs-tools to jessie-backports > won't work, as the current version requires upgrading busybox, > e2fsprogs, klibc and (for those that still use it) sysvinit. > > The fix is a one-liner and works for old and new kernels. Does this > seem suitable for inclusion in the next jessie point release? Just considering nvme in addition to block and gracefully coping with it not existing seems fine to me. Kind regards Philipp Kern
NEW changes in stable-new
Processing changes file: gpa_0.9.5-2+deb8u1_armel.changes ACCEPT
NEW changes in stable-new
Processing changes file: xscreensaver_5.30-1+deb8u2_armhf.changes ACCEPT
NEW changes in stable-new
Processing changes file: xscreensaver_5.30-1+deb8u2_armel.changes ACCEPT
NEW changes in oldstable-new
Processing changes file: gtk+3.0_3.4.2-7+deb7u1_armel.changes ACCEPT
NEW changes in oldstable-new
Processing changes file: gtk+3.0_3.4.2-7+deb7u1_sparc.changes ACCEPT
Bug#819797: jessie-pu: package libreoffice/1:4.3.3-2+deb8u2
Hi, On Sat, Apr 16, 2016 at 07:17:33PM +0100, Adam D. Barratt wrote: > It wasn't really very clear from your original report when the openjdk > change happened, particularly given how recently #819375 was filed. Sure. Because I didn't exactly know either. :) That's exactly why I rechecked with a "standard" stable. > Anyway, thanks for confirming; please feel free to upload. OK, running. Regards, Rene
Bug#819529: marked as done (transition: libcrypto++)
Your message dated Sun, 17 Apr 2016 10:43:23 +0200 with message-id <57134cab.7090...@debian.org> and subject line Re: Bug#819529: transition: libcrypto++ has caused the Debian Bug report #819529, regarding transition: libcrypto++ 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.) -- 819529: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819529 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 I'd like to do the libcrypto++ 5.6.1 to 5.6.3 transition. The latter is already in experimental. Affected package maintainers are noted, waiting for feedback. For the time being, I've rebuilt all affected packages on amd64: amule armory clementine murasaki pycryptopp synergy tegrarcm (non-free) All built successfully and as the libcrypto++ libraries are co-installable, binNMUs can be enough. Cheers, Laszlo/GCS --- End Message --- --- Begin Message --- On 03/04/16 13:13, Jonathan Wiltshire wrote: > Control: tag -1 confirmed > > On 2016-03-30 06:38, Laszlo Boszormenyi (GCS) wrote: >> I'd like to do the libcrypto++ 5.6.1 to 5.6.3 transition. The latter is > > Please go ahead. And it's over. Cheers, Emilio--- End Message ---
Bug#821208: (mini)transition: perl 5.22.2
Control: tags -1 confirmed On 16/04/16 19:36, Niko Tyni wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > Perl 5.22.2 is to be released on Sunday 24th April or so. > A release candidate is currently in experimental. This > is a stable update with just bugfix changes, see > http://perldoc.perl.org/perlpolicy.html#MAINTENANCE-BRANCHES for the > upstream policy. > > As usual with a Perl minor release, four packages will need a binNMU: > libpar-packer-perl > libdevel-cover-perl > libclass-xsaccessor-perl > libcommon-sense-perl > > Also, libmodule-corelist-perl and libperl-apireference-perl will need > sourceful uploads. I'll take care of the former unless somebody in > pkg-perl beats me to it. The latter will start to FTBFS until upstream > adds support for 5.22.2, but it can be removed from testing temporarily > if necessary. > > As you can see, this is a very small transition. Please let us know if > we can upload to unstable straight away when 5.22.2 is released, or if > we should hold off for some reason. You can just go ahead. Thanks. Cheers, Emilio
Processed: Re: Bug#821208: (mini)transition: perl 5.22.2
Processing control commands: > tags -1 confirmed Bug #821208 [release.debian.org] (mini)transition: perl 5.22.2 Added tag(s) confirmed. -- 821208: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821208 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
NEW changes in oldstable-new
Processing changes file: gtk+3.0_3.4.2-7+deb7u1_armhf.changes ACCEPT Processing changes file: gtk+3.0_3.4.2-7+deb7u1_mips.changes ACCEPT
NEW changes in stable-new
Processing changes file: gpa_0.9.5-2+deb8u1_armhf.changes ACCEPT