Bug#902577: RFS: highwayhash/0~20180209-g14dedec-4
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "highwayhash" * Package name: highwayhash Version : 0~20180209-g14dedec-4 Upstream Author : [fill in name and email of upstream] * URL : [fill in URL of upstreams web site] * License : [fill in] Section : science It builds those binary packages: libhighwayhash-dev - Fast strong hash functions: SipHash/HighwayHash (development) libhighwayhash0 - Fast strong hash functions: SipHash/HighwayHash (library) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/highwayhash Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/h/highwayhash/highwayhash_0~20180209-g14dedec-4.dsc More information about hello can be obtained from http://debomatic-amd64.debian.net/distribution#unstable/highwayhash/0~20180209-g14dedec-4/buildlog Changes since the last upload: highwayhash (0~20180209-g14dedec-4) unstable; urgency=medium * Depending on build-essential to really fix autopkgtest failure. * Add watch file to monitor upstream git HEAD. * Don't override debian-watch-file-is-missing, already fixed. * Bump Standards-Version to 4.1.4 (no change).
Bug#895209: uscan: Is --copy supposed to work?
Hi Christoph, On Sun, 8 Apr 2018 14:18:07 +0200 Christoph Biedl wrote:> Package: devscripts > Version: 2.18.1 > Severity: normal > > Dear Maintainer, > > when I tried the --copy option of uscan as described in the manpage, it > didn't quite work as expected: This is indeed a bug. It looks like the --copy command was never handled. I submitted a patch to the new Salsa repo [1]. > Could you please check what is supposed to happen here? The expected behavior is that rather than creating a symlink: running uscan before patch (no --copy arg) == root@d6e5bccac41e:/debian/debug# ls -al total 33848 drwxr-xr-x 7 root root 224 Jun 28 05:15 . drwxr-xr-x 14 root root 448 Jun 28 03:30 .. drwxr-xr-x 7 root root 224 Jun 28 03:51 891047 lrwxrwxrwx 1 root root 36 Jun 28 05:15 ffdiaporama_2.1+dfsg.orig-rsc.tar.gz -> ffdiaporama_rsc_2.1.2014.0209.tar.gz lrwxrwxrwx 1 root root 36 Jun 28 05:15 ffdiaporama_2.1+dfsg.orig.tar.gz -> ffdiaporama_bin_2.1.2014.0209.tar.gz -rw-r--r-- 1 root root 16063604 Jun 28 05:15 ffdiaporama_bin_2.1.2014.0209.tar.gz -rw-r--r-- 1 root root 17669845 Jun 28 05:15 ffdiaporama_rsc_2.1.2014.0209.tar.gz The original file should be copied instead: running uscan after patch (with --copy arg) == root@d6e5bccac41e:/debian/debug# ls -al total 67424 drwxr-xr-x 7 root root 224 Jun 28 05:16 . drwxr-xr-x 14 root root 448 Jun 28 03:30 .. drwxr-xr-x 7 root root 224 Jun 28 03:51 891047 -rw-r--r-- 1 root root 17669845 Jun 28 05:16 ffdiaporama_2.1+dfsg.orig-rsc.tar.gz -rw-r--r-- 1 root root 16063604 Jun 28 05:16 ffdiaporama_2.1+dfsg.orig.tar.gz -rw-r--r-- 1 root root 16063604 Jun 28 05:16 ffdiaporama_bin_2.1.2014.0209.tar.gz -rw-r--r-- 1 root root 17669845 Jun 28 05:16 ffdiaporama_rsc_2.1.2014.0209.tar.gz If you need to use this right away then you should be able to update your local uscan.pl file with the simple addition from the patch. [1] https://salsa.debian.org/debian/devscripts/merge_requests/22 -- Lev Lazinskiy e: l...@levlaz.org w: https://levlaz.org/about-me/
Bug#902576: dataquay FTCBFS: uses the build architecture qmake
Source: dataquay Version: 0.9.1-1 Tags: patch User: helm...@debian.org Usertags: rebootstrap dataquay fails to cross build from source, because it uses the build architecture qmake. Using dh_auto_configure, you get the host architecture qmake. The attached patch implements that, but it doesn't quite make dataquay cross buildable. Please consider applying it and close this bug when doing so. The next failure reason is that dataquay runs tests during dh_auto_build and tests typically fail during cross compilation with an Exec format error, which is exactly what happens here. Thus cross builders usually pass DEB_BUILD_OPTIONS=nocheck. Since dataquay runs tests as part from dh_auto_build, the nocheck flag isn't honoured though and tests are run anyway. Could you maybe also try to figure out how to make DEB_BUILD_OPTIONS=nocheck work for dataquay? Helmut diff --minimal -Nru dataquay-0.9.1/debian/changelog dataquay-0.9.1/debian/changelog --- dataquay-0.9.1/debian/changelog 2016-07-19 12:04:15.0 +0200 +++ dataquay-0.9.1/debian/changelog 2018-06-28 07:18:48.0 +0200 @@ -1,3 +1,10 @@ +dataquay (0.9.1-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Improve cross building: Use the host qmake via dh_auto_configure. (Closes: #-1) + + -- Helmut Grohne Thu, 28 Jun 2018 07:18:48 +0200 + dataquay (0.9.1-1) unstable; urgency=medium * Update watch file. diff --minimal -Nru dataquay-0.9.1/debian/rules dataquay-0.9.1/debian/rules --- dataquay-0.9.1/debian/rules 2016-07-19 11:50:53.0 +0200 +++ dataquay-0.9.1/debian/rules 2018-06-28 07:18:47.0 +0200 @@ -10,7 +10,7 @@ dh $@ --parallel override_dh_auto_configure: - qmake dataquay.pro PREFIX=/usr LIBDIR=/usr/lib/$(DEB_HOST_MULTIARCH) + dh_auto_configure -- dataquay.pro PREFIX=/usr LIBDIR=/usr/lib/$(DEB_HOST_MULTIARCH) override_dh_auto_install: dh_auto_install
Bug#902575: phasex FTCBFS: confuses build and host architecture
Source: phasex Version: 0.14.97-2 Tags: patch User: helm...@debian.org Usertags: rebootstrap phasex fails to cross build from source, because it confuses build and host architecture. For instance, when cross building from amd64 to ppc64el, it passes --enable-amd64. The attached patch fixes that and makes phasex cross build successfully. Please consider applying it. Helmut diff --minimal -Nru phasex-0.14.97/debian/changelog phasex-0.14.97/debian/changelog --- phasex-0.14.97/debian/changelog 2013-05-27 05:23:10.0 +0200 +++ phasex-0.14.97/debian/changelog 2018-06-28 07:11:10.0 +0200 @@ -1,3 +1,10 @@ +phasex (0.14.97-2.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: fix build/host confusion. (Closes: #-1) + + -- Helmut Grohne Thu, 28 Jun 2018 07:11:10 +0200 + phasex (0.14.97-2) unstable; urgency=low * Upload to unstable. diff --minimal -Nru phasex-0.14.97/debian/rules phasex-0.14.97/debian/rules --- phasex-0.14.97/debian/rules 2013-01-13 18:15:10.0 +0100 +++ phasex-0.14.97/debian/rules 2018-06-28 07:11:08.0 +0200 @@ -1,8 +1,8 @@ #!/usr/bin/make -f -DEB_BUILD_ARCH ?= $(shell dpkg-architecture -qDEB_BUILD_ARCH) +include /usr/share/dpkg/architecture.mk -ifneq (,$(findstring amd64,$(DEB_BUILD_ARCH))) +ifneq (,$(findstring amd64,$(DEB_HOST_ARCH))) DEB_CONFIGURE_FLAGS_EXTRA=--enable-arch=amd64 endif
Bug#902574: setcd FTCBFS: uses the build architecture compiler
Source: setcd Version: 1.5-6 Tags: patch User: helm...@debian.org Usertags: rebootstrap setcd fails to cross build from source, because it uses the build architecture compiler. The easiest way of passing cross tools to make is letting dh_auto_build do it and that is sufficient for making setcd cross buildable. Please consider applying the attached patch. Helmut diff -u setcd-1.5/debian/control setcd-1.5/debian/control --- setcd-1.5/debian/control +++ setcd-1.5/debian/control @@ -2,7 +2,7 @@ Section: utils Priority: optional Maintainer: LENART Janos -Build-Depends: debhelper (>= 5) +Build-Depends: debhelper (>= 7) Standards-Version: 3.8.1 Package: setcd diff -u setcd-1.5/debian/rules setcd-1.5/debian/rules --- setcd-1.5/debian/rules +++ setcd-1.5/debian/rules @@ -10,7 +10,7 @@ build: build-stamp build-stamp: dh_testdir - $(MAKE) CFLAGS=-O2 setcd + dh_auto_build -- CFLAGS=-O2 setcd touch build-stamp clean: diff -u setcd-1.5/debian/changelog setcd-1.5/debian/changelog --- setcd-1.5/debian/changelog +++ setcd-1.5/debian/changelog @@ -1,3 +1,10 @@ +setcd (1.5-6.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: Let dh_auto_build pass cross tools to make. (Closes: #-1) + + -- Helmut Grohne Thu, 28 Jun 2018 06:59:37 +0200 + setcd (1.5-6) unstable; urgency=low * Adopting the package. (closes: #406134)
Bug#902573: firefox-esr: firefox 60.1.0esr requires nss >= 3.36.4
Package: firefox-esr Version: 60.0.1esr-2.0~fab1 Severity: serious Justification: fails to build from source (but built successfully in the past) When compiling firefox 60.1.0esr I get the following error : checking for NSS - version >= 3.36.4... no Which means the version check of nss while installing the dependencies is not up to date. -- Package-specific info: -- Addons package information -- System Information: Debian Release: 9.4 APT prefers stable-updates APT policy: (991, 'stable-updates'), (991, 'stable'), (95, 'testing'), (90, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-6-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages firefox-esr depends on: ii debianutils 4.8.1.1 ii fontconfig2.11.0-6.7+b1 ii libatk1.0-0 2.22.0-1 ii libc6 2.24-11+deb9u3 ii libcairo-gobject2 1.14.8-1 ii libcairo2 1.14.8-1 ii libdbus-1-3 1.10.26-0+deb9u1 ii libdbus-glib-1-2 0.108-2 ii libevent-2.0-52.0.21-stable-3 ii libffi6 3.2.1-6 ii libfontconfig12.11.0-6.7+b1 ii libfreetype6 2.6.3-3.2 ii libgcc1 1:6.3.0-18+deb9u1 ii libgdk-pixbuf2.0-02.36.5-2+deb9u2 ii libglib2.0-0 2.50.3-2 ii libgtk-3-03.22.11-1 ii libhunspell-1.6-0 1.6.1-2.0~fab1 ii libjsoncpp1 1.7.4-3 ii libnspr4 2:4.12-6 ii libnss3 2:3.36.1-1.0~fab1 ii libpango-1.0-01.40.5-1 ii libsqlite3-0 3.16.2-5+deb9u1 ii libstartup-notification0 0.12-4+b2 ii libstdc++66.3.0-18+deb9u1 ii libvpx4 1.6.1-3+deb9u1 ii libx11-6 2:1.6.4-3 ii libx11-xcb1 2:1.6.4-3 ii libxcb-shm0 1.12-1 ii libxcb1 1.12-1 ii libxcomposite11:0.4.4-2 ii libxdamage1 1:1.1.4-2+b3 ii libxext6 2:1.3.3-1+b2 ii libxfixes31:5.0.3-1 ii libxrender1 1:0.9.10-1 ii libxt61:1.1.5-1 ii procps2:3.3.12-3+deb9u1 ii zlib1g1:1.2.8.dfsg-5 firefox-esr recommends no packages. Versions of packages firefox-esr suggests: ii fonts-lmodern 2.004.5-3 pn fonts-stix | otf-stix ii libcanberra0 0.30-3 ii libgssapi-krb5-2 1.15-1+deb9u1 ii libgtk2.0-02.24.31-2 -- no debconf information
Bug#902572: mark binutils-avr Multi-Arch: foreign
Package: binutils-avr
Version: 2.26.20160125+Atmel3.6.1-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:gcc-avr
gcc-avr fails to cross build from source, because it fails running
avr-ld with an "Exec format error". The typical fix is marking
binutils-avr Multi-Arch: foreign and here it actually is correct,
because the architecture-dependence (the target name) is encoded into
the binary package name. Please consider applying the attached patch.
Helmut
diff -u binutils-avr-2.26.20160125+Atmel3.6.1/debian/changelog
binutils-avr-2.26.20160125+Atmel3.6.1/debian/changelog
--- binutils-avr-2.26.20160125+Atmel3.6.1/debian/changelog
+++ binutils-avr-2.26.20160125+Atmel3.6.1/debian/changelog
@@ -1,3 +1,10 @@
+binutils-avr (2.26.20160125+Atmel3.6.1-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Mark binutils-avr Multi-Arch: foreign (closes: #-1)
+
+ -- Helmut Grohne Thu, 28 Jun 2018 06:41:10 +0200
+
binutils-avr (2.26.20160125+Atmel3.6.1-1) unstable; urgency=medium
* New upstream release
diff -u binutils-avr-2.26.20160125+Atmel3.6.1/debian/control
binutils-avr-2.26.20160125+Atmel3.6.1/debian/control
--- binutils-avr-2.26.20160125+Atmel3.6.1/debian/control
+++ binutils-avr-2.26.20160125+Atmel3.6.1/debian/control
@@ -10,6 +10,7 @@
Package: binutils-avr
Section: devel
Architecture: any
+Multi-Arch: foreign
Priority: extra
Depends: ${shlibs:Depends}, ${misc:Depends}
Breaks: avr-libc (<< 1:1.8.0+Atmel3.5.0-1)
Bug#902571: gif2png FTCBFS: configures for the build architecture
Source: gif2png Version: 2.5.8-1 Tags: patch User: helm...@debian.org Usertags: rebootstrap gif2png fails to cross build from source, because it does not pass --host to ./configure. Using dh_auto_configure fixes that and makes gif2png cross buildable. Please consider applying the attached patch. Helmut diff --minimal -Nru gif2png-2.5.8/debian/changelog gif2png-2.5.8/debian/changelog --- gif2png-2.5.8/debian/changelog 2012-06-02 14:50:50.0 +0200 +++ gif2png-2.5.8/debian/changelog 2018-06-28 06:28:59.0 +0200 @@ -1,3 +1,10 @@ +gif2png (2.5.8-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: Let dh_auto_configure pass --host to ./configure. (Closes: #-1) + + -- Helmut Grohne Thu, 28 Jun 2018 06:28:59 +0200 + gif2png (2.5.8-1) unstable; urgency=low * New upstream release (Closes: 650487) diff --minimal -Nru gif2png-2.5.8/debian/rules gif2png-2.5.8/debian/rules --- gif2png-2.5.8/debian/rules 2012-06-02 11:34:24.0 +0200 +++ gif2png-2.5.8/debian/rules 2018-06-28 06:28:57.0 +0200 @@ -36,7 +36,7 @@ dh_testdir chmod 755 configure - ./configure --prefix=/usr CFLAGS="$(CFLAGS)" + dh_auto_configure -- CFLAGS="$(CFLAGS)" # Add here commands to compile the package. $(MAKE) # Create German manpages at build time, so we need only .xml in .diff.gz
Bug#902570: asm: Package rebuilt from source gets lots of empty jars
Source: asm Version: 6.0-1 Severity: serious When I build src:asm using pbuilder, the build completes without errors. However, then the generated deb file contains mostly empty jars - the only one with any real contents is asm-debug-all-6.0.jar. -- Daniel Schepler
Bug#891047: uscan: version mode "same" does not work with --download-current-version
I was able to reproduce this using the latest (2.18.3) version of uscan. I added some debugging notes, files, and steps to reproduce to this repo: https://salsa.debian.org/levlaz-guest/sid-builder/tree/debug/debug/891047 I plan on doing a bit more investigation on this bug. -- Lev Lazinskiy e: l...@levlaz.org w: https://levlaz.org/about-me/
Bug#902569: ITP: systemc-- SystemC class library
Package: wnpp Package name: sysyemc Version : 2.3.2 Upstream Author : Accellera URL : https://www.accellera.org/downloads/standards/systemc License : Apache-2.0 Section : elextronics Description: SystemC library SystemC is an HDL based on a C++ class library intended for simulations using standard C++ tools. -- أحمد المحمودي (Ahmed El-Mahmoudy) Digital design engineer GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7 GPG Fingerprints: 6E2E E4BB 72E2 F417 D066 6ABF 7B30 B496 A7EF 5761 8206 A196 2084 7E6D 0DF8 B176 BC19 6A94 EDDD A1B7 signature.asc Description: PGP signature
Bug#902568: dpkg: error: dpkg status database is locked by another process
Package: apt Version: 1.6.2 Severity: normal Dear Maintainer, During today's upgrade, I meet the following error: Unpacking apt (1.6.2) over (1.6.1) ... dpkg: error: dpkg status database is locked by another process E: Sub-process /usr/bin/dpkg returned an error code (2) Full log is, zsj@debian ~ $ apt list --upgradable Listing... Done apt/testing,unstable 1.6.2 amd64 [upgradable from: 1.6.1] apt-utils/testing,unstable 1.6.2 amd64 [upgradable from: 1.6.1] debootstrap/testing,testing,unstable,unstable 1.0.104 all [upgradable from: 1.0.103] kde-config-gtk-style/testing,unstable 4:5.13.1-1 amd64 [upgradable from: 4:5.12.5-1] libapt-inst2.0/testing,unstable 1.6.2 amd64 [upgradable from: 1.6.1] libapt-pkg5.0/testing,unstable 1.6.2 amd64 [upgradable from: 1.6.1] libkf5activitiesstats1/testing,unstable 5.47.0-1 amd64 [upgradable from: 5.46.0-1] libkf5people-data/testing,testing,unstable,unstable 5.47.0-1 all [upgradable from: 5.46.0-1] libkf5people5/testing,unstable 5.47.0-1 amd64 [upgradable from: 5.46.0-1] libkf5peoplebackend5/testing,unstable 5.47.0-1 amd64 [upgradable from: 5.46.0-1] libkf5peoplewidgets5/testing,unstable 5.47.0-1 amd64 [upgradable from: 5.46.0-1] libpkcs11-helper1/testing,unstable 1.24-1 amd64 [upgradable from: 1.23-1] libqpdf21/testing,unstable 8.1.0-1 amd64 [upgradable from: 8.0.2-3] zsj@debian ~ $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: apt apt-utils debootstrap kde-config-gtk-style libapt-inst2.0 libapt-pkg5.0 libkf5activitiesstats1 libkf5people-data libkf5people5 libkf5peoplebackend5 libkf5peoplewidgets5 libpkcs11-helper1 libqpdf21 13 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 3,716 kB of archives. After this operation, 76.8 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 https://mirrors.ustc.edu.cn/debian testing/main amd64 libapt-pkg5.0 amd64 1.6.2 [941 kB] Get:2 https://mirrors.ustc.edu.cn/debian testing/main amd64 libapt-inst2.0 amd64 1.6.2 [199 kB] Get:3 https://mirrors.ustc.edu.cn/debian testing/main amd64 apt amd64 1.6.2 [1,307 kB] Get:4 https://mirrors.ustc.edu.cn/debian testing/main amd64 apt-utils amd64 1.6.2 [420 kB] Get:5 https://mirrors.ustc.edu.cn/debian testing/main amd64 debootstrap all 1.0.104 [70.8 kB] Get:6 https://mirrors.ustc.edu.cn/debian testing/main amd64 kde-config-gtk-style amd64 4:5.13.1-1 [193 kB] Get:7 https://mirrors.ustc.edu.cn/debian testing/main amd64 libkf5activitiesstats1 amd64 5.47.0-1 [72.6 kB] Get:8 https://mirrors.ustc.edu.cn/debian testing/main amd64 libkf5peoplebackend5 amd64 5.47.0-1 [14.3 kB] Get:9 https://mirrors.ustc.edu.cn/debian testing/main amd64 libkf5people5 amd64 5.47.0-1 [57.1 kB] Get:10 https://mirrors.ustc.edu.cn/debian testing/main amd64 libkf5peoplewidgets5 amd64 5.47.0-1 [34.5 kB] Get:11 https://mirrors.ustc.edu.cn/debian testing/main amd64 libkf5people-data all 5.47.0-1 [17.2 kB] Get:12 https://mirrors.ustc.edu.cn/debian testing/main amd64 libpkcs11-helper1 amd64 1.24-1 [47.0 kB] Get:13 https://mirrors.ustc.edu.cn/debian testing/main amd64 libqpdf21 amd64 8.1.0-1 [344 kB] Fetched 3,716 kB in 3s (1,427 kB/s) Reading changelogs... Done (Reading database ... 257148 files and directories currently installed.) Preparing to unpack .../libapt-pkg5.0_1.6.2_amd64.deb ... Unpacking libapt-pkg5.0:amd64 (1.6.2) over (1.6.1) ... Setting up libapt-pkg5.0:amd64 (1.6.2) ... (Reading database ... 257148 files and directories currently installed.) Preparing to unpack .../libapt-inst2.0_1.6.2_amd64.deb ... Unpacking libapt-inst2.0:amd64 (1.6.2) over (1.6.1) ... Preparing to unpack .../archives/apt_1.6.2_amd64.deb ... Unpacking apt (1.6.2) over (1.6.1) ... dpkg: error: dpkg status database is locked by another process E: Sub-process /usr/bin/dpkg returned an error code (2) zsj@debian ~ $ -- Package-specific info: -- apt-config dump -- APT ""; APT::Architecture "amd64"; APT::Build-Essential ""; APT::Build-Essential:: "build-essential"; APT::Install-Recommends "false"; APT::Install-Suggests "0"; APT::Sandbox ""; APT::Sandbox::User "_apt"; APT::Authentication ""; APT::Authentication::TrustCDROM "true"; APT::NeverAutoRemove ""; APT::NeverAutoRemove:: "^firmware-linux.*"; APT::NeverAutoRemove:: "^linux-firmware$"; APT::NeverAutoRemove:: "^linux-image-4\.16\.0-1-amd64$"; APT::NeverAutoRemove:: "^linux-image-4\.16\.0-2-amd64$"; APT::NeverAutoRemove:: "^linux-headers-4\.16\.0-1-amd64$"; APT::NeverAutoRemove:: "^linux-headers-4\.16\.0-2-amd64$"; APT::NeverAutoRemove:: "^linux-image-extra-4\.16\.0-1-amd64$"; APT::NeverAutoRemove:: "^linux-image-extra-4\.16\.0-2-amd64$"; APT::NeverAutoRemove:: "^linux-modules-4\.16\.0-1-amd64$"; APT::NeverAutoRemove:: "^linux-modules-4\.16\.0-2-amd64$"; APT::NeverAutoRemove:: "^linux-modules-extra-4\.16\.0-1-amd64$"; APT::NeverAutoRemove:: "^linux-modules-extra-4\.16\.0-2-amd64$";
Bug#835919: devscripts: please add "--extra-packages" option to install arbitrary extra packages
Hi Chris, I started to think about this issue. > It would be nice if I could do these in one install call, hence an > "--extra-packages" option. I wanted to clarify one thing, in the use case that you outlined would you expect to pass in a list of packages as an argument after --extra-packages? -- Lev Lazinskiy e: l...@levlaz.org w: https://levlaz.org/about-me/
Bug#902567: tasksel: Please remove occurrences of "kdesudo" and coordinate with d-i
Source: tasksel
Version: 3.44
Severity: important
X-Debbugs-CC: debian-b...@lists.debian.org
Dear d-i developers and tasksel maintainers,
Package "kdesudo" has been removed in Debian since September 2017.
Tasksel still recommends non-existent "kdesudo" in task-kde-desktop. Please
consider removing this entry from "Recommends: " field.
However, I noticed the following lines in debian/control:
Package: task-kde-desktop
Architecture: all
Description: KDE
This task package is used to install the Debian desktop, featuring
the KDE desktop environment, and with other packages
that Debian users
expect to have available on the desktop.
Depends: ${misc:Depends},
task-desktop,
kde-standard,
sddm,
Recommends:
[...]
# desktop network setup
plasma-nm,
# This is configured by d-i to be used to gain root on systems with
# no root password. It is not enabled by default.
kdesudo,
# Package management.
apper,
[...]
I am wondering how d-i is handling privilege escalation with kdesudo's removal
in Debian 10. Should this entry be removed anyway or is there any
alternatives?
Thanks!
--
Regards,
Boyuan Yang
signature.asc
Description: This is a digitally signed message part.
Bug#902566: libncbi-vdb2: accidental ABI break in 2.9.1, fixed in upstream 2.9.1-1 release
Package: libncbi-vdb2 Version: 2.9.1+dfsg-1 Severity: serious Tags: upstream Justification: Policy 8.6.2 The original upstream 2.9.1 release accidentally broke binary compatibility with 2.9.0 by adding a new enum value in the middle of an implicitly numbered list. Please update to the "2.9.1-1" release, which fixes this break. Thanks! -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing'), (500, 'stable'), (300, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386, x32 Kernel: Linux 4.15.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libncbi-vdb2 depends on: ii libbz2-1.0 1.0.6-8.1 ii libc6 2.27-3 ii libmbedcrypto1 2.9.0-2 ii libmbedtls102.9.0-2 ii libmbedx509-0 2.9.0-2 ii libxml2 2.9.4+dfsg1-7 ii zlib1g 1:1.2.11.dfsg-1 libncbi-vdb2 recommends no packages. libncbi-vdb2 suggests no packages. -- no debconf information
Bug#891725: This isn't even a scrapy bug.
This failing test seems to be an issue with Python itself, rather than
Scrapy. Suggest just changing the test to match Python behavior.
This code calls through to w3lib.encoding.to_unicode, which just boils
down to this:
b"\xef\xbb\xbfWORD\xe3\xab".decode('utf-8', 'replace')
In which we can see the same results as the test:
On python 2:
>>> b"\xef\xbb\xbfWORD\xe3\xab".decode('utf-8', 'replace')
u'\ufeffWORD\ufffd'
On python 3:
>>> b"\xef\xbb\xbfWORD\xe3\xab".decode('utf-8', 'replace')
'\ufeffWORD�'
This bug is keeping python3-scrapy out of testing, can we just update
the test to accept this behavior?
Bug#902565: autofs not migrated to salsa.d.o(?)
Package: autofs Severity: normal I was trying to find the autofs source on salsa and was unable to after a fair bit of rummaging around. The old alioth repo is archived at [1]. Is it possible to migrate it to salsa, from that tar ball? Kind regards Vince [1] https://alioth-archive.debian.org/git/collab-maint/autofs.git.tar.xz
Bug#901817: libxml2 - DoS - null deref - xmlXPathCompOpEval
On Tue, 19 Jun 2018 22:39:34 +0200 Salvatore Bonaccorso wrote:> Can you please report the upstream directly in the upstream bugzilla > and once you have the bug reference, add then mark this bug here as > forwarded to the upstream one? > > https://www.debian.org/Bugs/server-control#forwarded > > Thanks already. > > Regards, Couldn't see this in GNOME bugzilla so filed: https://gitlab.gnome.org/GNOME/libxml2/issues/10 -- Sam Fowler, Red Hat Product Security
Bug#850151: emacs-goodies-el: up-to-date version of diminish-el is packaged outside of emacs-goodies-el
Control: owner -1 ! Control: tags -1 + pending Fixed in git yesterday at commit abc0e742af83942db24c4b56803484403e5314b5 signature.asc Description: PGP signature
Bug#902564: emacs-goodies-el: replace session.el with elpa-session
Package: emacs-goodies-el Version: 37.0 Severity: normal Tags: newcomer User: debian-emac...@lists.debian.org Usertags: elpafy It looks like session.el is worth preserving (there's about 42k downloads on melpa), so let's replace it with a dh-elpa based elpa-session (or similar name) package. There's an updated version on sourceforge at http://emacs-session.sourceforge.net/ -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.16.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages emacs-goodies-el depends on: ii bash 4.4.18-3 ii dpkg 1.19.0.5+b1 ii emacs1:25.2+1-7 ii emacs-gtk [emacsen] 1:25.2+1-7 ii emacsen-common 3.0.0 ii install-info 6.5.0.dfsg.1-3 Versions of packages emacs-goodies-el recommends: ii perl-doc 5.26.2-6 ii wget 1.19.5-1 emacs-goodies-el suggests no packages. -- no debconf information
Bug#902281: libgsl23: ABI breakage due to removed symbols
On 26 June 2018 at 17:11, Niko Tyni wrote: | On Tue, Jun 26, 2018 at 08:37:58AM -0500, Dirk Eddelbuettel wrote: | > On 26 June 2018 at 10:12, Niko Tyni wrote: | | > | For the record, the Perl GSL bindings package libmath-gsl-perl (can be | > | made to) work without the deprecated symbols too. It just needs a rebuild, | > | and forcing that rebuild (and the associated dependency metadata updates) | > | is the main point of SONAME bumps. | > | | > | So please don't feel obliged to carry those symbols forever because of us. | > | > I like to be similar to upstream, so consider this to be a simple but | > forceful nudge towards that rebuild on your side. | | The way to remove symbols from a shared library in Debian (or otherwise | change its ABI in an incompatible way) is to upload a version with SONAME | bumped to experimental, check that reverse dependencies still build, | file bugs if they don't, and when everything is ready enough ask for a | transition slot from the release team. They will then handle the rebuilds. | | The libmath-gsl-perl package does need a bit of work to become source | compatible with the removal of the deprecated functions. We're already | handling that in #901807 now that this issue brought it to our attention. | | > Do we know if any other packages depending on GSL use these? | | codesearch.debian.net does give some hits for at least | gsl_sf_legendre_array_size and gsl_linalg_hessenberg. I didn't check | whether they are false positives. | | Test rebuilds with the new library version need to be done anyway and | should pinpoint any such issues. | | Hope this helps, It does, it's a good strategy but I won't have any cycles for it anytime soon :-/ Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#532856: closed by Mathieu Parent (Closing " umask settings overridden by Mac OS X 10.5 (Leopard) clients")
On Mon, Jun 18, 2018 at 09:51:03PM +, Debian Bug Tracking System wrote: > Closing as this is not a bug but a configuration tuning. Sorry, what? I don't see such an explanation in the bug log. Two people said "unix extensions = no" would work around the issue. Nobody provided an actual solution to the issue. Nobody responded to the part where I said: > I had specified all documented options that describe native Linux permission > masks to be applied on files on Samba shares. The daemon ignored this > because of another implicit option being in effect, one which contradicted > those other, explicit settings. That just doesn't make sense from a user > standpoint, regardless of the rationale. A proper bug fix would be to change > the behaviour of that new option to take into account the requirements set > by old options (better), or to fully document the impact of the new option > and make it explicit (worse, but still satisfactory). Can you? -- 2. That which causes joy or happiness.
Bug#900469: firefox: Spell checker stopped working after upgrading from version 60 to 61.0~b8
Same error occurs with 61.0-1 The error message can be trigged by forcing spell checks / changing spell checking language. This occurs with the default installed en_US dict, as well as the en_AU dict installed from addons.mozilla.org. Only started on upgrade from 60.x to 61.0-1 error: file:///home/patoh/.mozilla/firefox/eskyowik.default/extensions/en...@dictionaries.addons.mozilla.org/dictionaries/en-AU.aff: cannot open error: file:///home/patoh/.mozilla/firefox/eskyowik.default/extensions/en...@dictionaries.addons.mozilla.org/dictionaries/en-AU.dic: cannot open error: file:///home/patoh/.mozilla/firefox/eskyowik.default/extensions/en...@dictionaries.addons.mozilla.org/dictionaries/en-AU.aff: cannot open error: file:///home/patoh/.mozilla/firefox/eskyowik.default/extensions/@unitedstatesenglishdictionary/dictionaries/en-US.aff: cannot open error: file:///home/patoh/.mozilla/firefox/eskyowik.default/extensions/@unitedstatesenglishdictionary/dictionaries/en-US.dic: cannot open error: file:///home/patoh/.mozilla/firefox/eskyowik.default/extensions /@unitedstatesenglishdictionary/dictionaries/en-US.aff: cannot open All files exist, and can be read by the firefox process -- Email: p...@ge3k.net IM: p...@ge3k.net Site: http://ge3k.net
Bug#902294: python-cluster 1.3.3-1.1~deb9u1 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: python-cluster Version: 1.3.3-1.1~deb9u1 Explanation: add missing dependency on pkg-resources
Bug#902325: pysurfer 0.7-2.1~deb9u1 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: pysurfer Version: 0.7-2.1~deb9u1 Explanation: add missing dependency on python-matplotlib
Bug#902319: thefuck 3.11-2.1~deb9u1 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: thefuck Version: 3.11-2.1~deb9u1 Explanation: add missing dependency on pkg-resources
Bug#902326: fastkml 0.11-2~deb9u1 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: fastkml Version: 0.11-2~deb9u1 Explanation: add missing dependency on pkg-resources
Bug#891415: psad 2.4.3-1.2~deb9u1 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: psad Version: 2.4.3-1.2~deb9u1 Explanation: add missing dependencies on net-tools and iproute2
Bug#887160: django-xmlrpc 0.1.5-6+deb9u1 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: django-xmlrpc Version: 0.1.5-6+deb9u1 Explanation: fix python3 dependencies
Bug#890791: dpkg 1.18.25 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian . Thanks for your contribution! Upload details == Package: dpkg Version: 1.18.25 Explanation: fix integer overflow in deb(5) format version parser;fix directory traversal with dpkg-deb --raw-extract; add support for riscv64 CPU; do not normalize args past a passthrough stop word in Dpkg::Getopt; parse start-stop-daemon usernames and groupnames starting with digits correctly; always use the binary version for the .buildinfo filename
Bug#896905: [PATCH] Build python3 package
This builds a python3 package for libiio
---
debian/control| 14 +-
debian/python3-libiio.install | 2 ++
debian/rules | 8
3 files changed, 23 insertions(+), 1 deletion(-)
create mode 100644 debian/python3-libiio.install
diff --git a/debian/control b/debian/control
index 9c595f9..70323d2 100644
--- a/debian/control
+++ b/debian/control
@@ -13,7 +13,8 @@ Build-Depends: bison,
libusb-1.0-0-dev [linux-any],
libusb2-dev [kfreebsd-any],
libxml2-dev,
- python-dev
+ python-dev,
+ python3-dev
Standards-Version: 4.1.4
Homepage: https://github.com/analogdevicesinc/libiio
Vcs-Browser: https://github.com/ev3dev/libiio
@@ -78,6 +79,17 @@ Description: Python bindings for libiio
.
This package contains the Python bindings for libiio.
+Package: python3-libiio
+Section: python
+Architecture: all
+Depends: libiio0 (>= ${binary:Version}), ${misc:Depends}, ${python3:Depends}
+Description: Python bindings for libiio
+ Libiio is a library that has been conceived to ease the development of
+ applications interfacing Industrial Input/Output (IIO) devices through
+ the IIO subsystem of the Linux kernel.
+ .
+ This package contains the Python bindings for libiio.
+
Package: libiio0-doc
Section: doc
Architecture: all
diff --git a/debian/python3-libiio.install b/debian/python3-libiio.install
new file mode 100644
index 000..4755228
--- /dev/null
+++ b/debian/python3-libiio.install
@@ -0,0 +1,2 @@
+usr/lib/python3.5/site-packages/*.egg-info usr/lib/python3/dist-packages
+usr/lib/python3.5/site-packages/*.py usr/lib/python3/dist-packages
diff --git a/debian/rules b/debian/rules
index 8c01998..67010ea 100755
--- a/debian/rules
+++ b/debian/rules
@@ -8,6 +8,14 @@ DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture
-qDEB_HOST_MULTIARCH)
override_dh_auto_configure:
dh_auto_configure -- -DINSTALL_LIB_DIR=/usr/lib/$(DEB_HOST_MULTIARCH)
+override_dh_auto_build:
+ dh_auto_build
+ python3 obj-$(DEB_HOST_MULTIARCH)/bindings/python/setup.py build
+
+override_dh_auto_install:
+ dh_auto_install
+ python3 obj-$(DEB_HOST_MULTIARCH)/bindings/python/setup.py install
--root=debian/tmp/ --prefix=/usr
+
override_dh_compress:
dh_compress -X.c -X.C
--
2.17.1
Bug#902343: ITP: fonts-osifont -- ISO 3098-compliant TrueType font for CAD projects
On 2018-06-25 05:44, Kurt Kremitzki wrote: > * Package name: fonts-osifont Note, that Debian already has fonts-opendin, which is probably similar.
Bug#902563: golang-github-shirou-gopsutil: FTBFS in machines not having virtualization support (?)
Package: src:golang-github-shirou-gopsutil Version: 2.18.02-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster with "dpkg-buildpackage -A" but it failed: [...] debian/rules build-indep dh build-indep --buildsystem=golang --with=golang dh_update_autotools_config -i -O--buildsystem=golang dh_autoreconf -i -O--buildsystem=golang dh_auto_configure -i -O--buildsystem=golang dh_auto_build -i -O--buildsystem=golang cd obj-x86_64-linux-gnu && go install -gcflags=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" -asmflags=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" -v -p 1 github.com/shirou/gopsutil github.com/shirou/gopsutil/cpu github.com/shirou/gopsutil/disk github.com/shirou/gopsutil/docker github.com/shirou/gopsutil/host github.com/shirou/gopsutil/internal/common github.com/shirou/gopsutil/load github.com/shirou/gopsutil/mem github.com/shirou/gopsutil/net github.com/shirou/gopsutil/process github.com/shirou/gopsutil github.com/shirou/gopsutil/internal/common github.com/shirou/gopsutil/cpu golang.org/x/sys/unix github.com/shirou/gopsutil/disk github.com/shirou/gopsutil/docker [... snipped ...] === RUN TestVirtualization --- FAIL: TestVirtualization (0.00s) host_test.go:137: Virtualization() retuns empty system or role: , host_test.go:140: Virtualization(): , === RUN TestKernelVersion --- PASS: TestKernelVersion (0.00s) host_test.go:152: KernelVersion(): 4.9.0-6-amd64 FAIL FAILgithub.com/shirou/gopsutil/host 0.020s [...] --- PASS: Test_OpenFiles (0.00s) === RUN Test_Kill --- PASS: Test_Kill (0.10s) PASS ok github.com/shirou/gopsutil/process 0.314s dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 github.com/shirou/gopsutil github.com/shirou/gopsutil/cpu github.com/shirou/gopsutil/disk github.com/shirou/gopsutil/docker github.com/shirou/gopsutil/host github.com/shirou/gopsutil/internal/common github.com/shirou/gopsutil/load github.com/shirou/gopsutil/mem github.com/shirou/gopsutil/net github.com/shirou/gopsutil/process returned exit code 1 debian/rules:10: recipe for target 'build-indep' failed make: *** [build-indep] Error 1 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 The failure is not related to using "dpkg-buildpackage -A" at all, as a similar error happens here in reproducible builds in the i386 architecture: https://tests.reproducible-builds.org/debian/rb-pkg/buster/i386/golang-github-shirou-gopsutil.html I don't even understand the purpose of the test. Following a common reasoning from Chris Lamb in similar cases: Does this failing test means the program will not work properly on machines not having virtualization support? (I don't really think so). Thanks.
Bug#902562: strace: FTBFS in stretch
Package: src:strace Version: 4.15-2 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in stretch with "dpkg-buildpackage -B" but it failed: [...] debian/rules build-arch mkdir -p build cd build; sh ../configure --prefix=/usr --build=x86_64-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking whether to enable maintainer-specific portions of Makefiles... no checking build system type... x86_64-pc-linux-gnu checking host system type... x86_64-pc-linux-gnu checking for gcc... gcc [... snipped ...] FAIL: futex === + ../strace -V + TIMEOUT=timeout -s 9 60 + timeout -s 9 60 true + exec timeout -s 9 60 ../../tests/futex.test + run_strace_match_diff -a27 + args=-a27 + [ -n -a27 -a -z -a27 ] + set -- -e trace=futex -a27 + run_prog + [ 0 -eq 0 ] + set -- ./futex + args=./futex + ./futex futex(0x7f6e5c2dbffc, 0x3, 0xfacefeed, 0xbadda7a0ca7b100d, 0x7f6e5c2dbffc, 0x9caffee1) = -1: Invalid argument + rc=1 + [ 1 -eq 77 ] + fail_ ./futex failed with code 1 + warn_ futex.test: failed test: ./futex failed with code 1 + printf %s\n futex.test: failed test: ./futex failed with code 1 futex.test: failed test: ./futex failed with code 1 + exit 1 The above is from my autobuilder, but it also fails in reproducible builds: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/strace.html I'm using linux-image-amd64 version 4.9.88-1+deb9u1 from security.debian.org. In case another package is to blame and you have to reassign, please use "affects" as well, so that this bug is still shown in the BTS web page for strace. Thanks.
Bug#901353: wmifs segfaults occasionally
Control: tags -1 fixed-upstream
On 06/11/2018 03:42 PM, ano...@users.sourceforge.net wrote:
Package: wmifs
Version: 1.8-1
I noticed that wmifs was randomly crashing on my laptop. I have no idea
how to reproduce it besides letting it run for a long time, it didn't
seem to be associated with hibernation or anything else obvious. If I
have multiple instances running, usually only one will crash while the
others continue without issue.
Running it under gdb with wmifs-dbgsym installed produced this trace:
Program received signal SIGSEGV, Segmentation fault.
_IO_fgets (buf=0x7fffd9d0 "\001", n=512, fp=0x0) at iofgets.c:47
47 iofgets.c: No such file or directory.
(gdb) bt
#0 _IO_fgets (buf=0x7fffd9d0 "\001", n=512, fp=0x0) at iofgets.c:47
#1 0x6d1f in fgets (__stream=0x0, __n=512, __s=0x7fffd9d0
"\001") at /usr/include/x86_64-linux-gnu/bits/stdio2.h:263
#2 get_statistics (devname=, ip=0x7fffdc70,
op=0x7fffdc78, is=0x7fffdc80, os=0x7fffdc88) at wmifs.c:767
#3 0x73b9 in wmifs_routine (argc=, argv=) at wmifs.c:555
#4 0x5dbe in main (argc=5, argv=0x7fffe198) at wmifs.c:367
Apparently the fopen() on wmifs.c line 766 can fail in some cases, and
that needs to be checked for to avoid passing a NULL file pointer to
fgets(). It could be as simple as inserting
if (!fp) {
return -1;
}
to match the minimal error handling on subsequent lines when an fgets() fails.
Thanks for your report!
I've just released a new upstream version (1.9) with your patch [1]. It
should get fixed in Debian soon.
[1] https://www.dockapps.net/wmifs
Bug#902559: some tests can fail if gnupg happens not to be installed
Ian Jackson writes ("Re: Bug#902559: some tests can fail if gnupg happens not
to be installed"):
> Here is a better patch. This has passed more tests. If all is well I
> will upload it shortly.
>From 03d9c0e7c24a96cd792c051026afd46a7fd02bfc Mon Sep 17 00:00:00 2001
From: Ian Jackson
Date: Wed, 27 Jun 2018 21:41:38 +0100
Subject: [PATCH v2] test suite: gdr-viagit, gdr-newupstream: do not
auto-import t-setup-gnupg.
We provide a new mechanism for individual tests to disable the
automatic t-setup-import of gnupg.
We need to add this to all the other setup/ that these import, too.
gdr-convert-gbp is particularly awkward because it wants gnupg if
$ifarchive isn't `:'. There we arrange to suppress its automatic
inclusion, but add it again by hand if appropriate.
This fixes these two tests in chroots without gnupg.
Closes:#902559.
Signed-off-by: Ian Jackson
---
debian/changelog | 2 ++
tests/lib | 12
tests/setup/gdr-convert-gbp | 3 +++
tests/setup/gdr-convert-gbp-noarchive | 1 +
tests/tests/gdr-newupstream | 1 +
tests/tests/gdr-viagit| 1 +
6 files changed, 16 insertions(+), 4 deletions(-)
diff --git a/debian/changelog b/debian/changelog
index 4d05abe3..e984276e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,8 @@
dgit (5.4~) unstable; urgency=medium
Bugfixes:
+ * test suite: gdr-viagit, gdr-newupstream: Do not spuriously
+fail if gnupg not serendipitously installed. Closes:#902559.
* Fix bug ref to #865444 in previous changelog entry.
--
diff --git a/tests/lib b/tests/lib
index bd06d20d..f3fb0dab 100644
--- a/tests/lib
+++ b/tests/lib
@@ -1134,7 +1134,11 @@ t-alt-test () {
t-git-config dgit.default.old-dsc-distro test-dummy
-case "$0" in
-*/gnupg) ;;
-*) t-setup-import gnupg ;;
-esac
+for import in ${autoimport-gnupg}; do
+ case "$0" in
+ */$import) ;;
+ *)
+ t-setup-import $import
+ ;;
+ esac
+done
diff --git a/tests/setup/gdr-convert-gbp b/tests/setup/gdr-convert-gbp
index 0b525c87..e523fd33 100755
--- a/tests/setup/gdr-convert-gbp
+++ b/tests/setup/gdr-convert-gbp
@@ -1,8 +1,11 @@
#!/bin/bash
set -e
+autoimport=
. tests/lib
. $troot/lib-gdr
+$ifarchive t-setup-import gnupg
+
t-dependencies GDR
t-tstunt-parsechangelog
diff --git a/tests/setup/gdr-convert-gbp-noarchive b/tests/setup/gdr-convert-gbp-noarchive
index dfeea3b9..1d6758b7 100755
--- a/tests/setup/gdr-convert-gbp-noarchive
+++ b/tests/setup/gdr-convert-gbp-noarchive
@@ -1,4 +1,5 @@
#!/bin/bash
+autoimport=
set -e
. tests/lib
. $troot/lib-gdr
diff --git a/tests/tests/gdr-newupstream b/tests/tests/gdr-newupstream
index cfa00523..ee987f51 100755
--- a/tests/tests/gdr-newupstream
+++ b/tests/tests/gdr-newupstream
@@ -1,5 +1,6 @@
#!/bin/bash
set -e
+autoimport=
. tests/lib
t-dependencies NO-DGIT GDR
diff --git a/tests/tests/gdr-viagit b/tests/tests/gdr-viagit
index 644d2d45..a83e622b 100755
--- a/tests/tests/gdr-viagit
+++ b/tests/tests/gdr-viagit
@@ -1,5 +1,6 @@
#!/bin/bash
set -e
+autoimport=
. tests/lib
t-dependencies NO-DGIT GDR
--
2.11.0
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Bug#902559: some tests can fail if gnupg happens not to be installed
Control: tags -1 + patch Here is a better patch. This has passed more tests. If all is well I will upload it shortly. Sean, you can probably get autopkgtest to run the new test suite against the old source code, if you want to test your backport. It may be easier to wait for 5.4 though. Ian.
Bug#860064: #860064 dnsmasq will not start after dns-root-data upgrade
On Mon, 2018-06-25 at 10:44 +0200, Christoph Martin wrote: > severity 860064 critical > On which grounds are you claiming this qualifies for critical severity? It doesn't introduce a security hole, cause severe data loss or break your whole system. I have difficulty with dnsmasq and dns-root-data being "unrelated software", particularly given that dnsmasq-base has "Recommends: dns-root-data". Regards, Adam
Bug#893054: systemd: System failed to boot after upgrade/install systemd from systemd:i386
On Sat, 24 Mar 2018 21:51:21 +0100 Michael Biebl wrote: > Control: tags -1 + moreinfo > On Mon, 19 Mar 2018 09:46:04 -0600 Jeff Ketchum wrote: > > Second issue, I have trouble getting my system to boot reliably after the > > changes. > > It is using systemd:amd64 > > Ok, so what exactly is the failure then? Please describe it in more > detail. Maybe also provide a complete, verbose boot log [1]. > > > Regards, > Michael > https://freedesktop.org/wiki/Software/systemd/Debugging/ > [1] Closing the bug report due to lack of further feedback. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#894605: systemd: System fails to suspend.
On Wed, 13 Jun 2018 18:10:41 +0200 Michael Biebl wrote: > On Mon, 9 Apr 2018 23:17:28 +0200 (CEST) "hub...@golembiowski.pl" > wrote: > > > echo "mem" > /sys/power/state suspends system correctly with possibility to > > wake > > up as expected. > > > > I run dist-upgrade regularly so I expect a number of packages upgrade > > recently. > > Unfortunately can't correlate as I was not noting down packages being > > updated. > > Found what seem to be related in #892321 mailto:892...@bugs.debian.org but > > can't > > tell if both cases are the same. > > systemd internally does basically nothing more then > echo "mem" > /sys/power/state > > What it does in addition though is send out a (D-Bus) signal that the > system is going to suspend, so userspace software can react to that. > > My guess is, that it is some other component reacting on that D-Bus > signal which triggers that problem. > > Which desktop environment are you using? > If you use a minimal desktop environment / window manager and you run > systemctl suspend > does the problem happen as well? > What if you run systemctl suspend when you are logged in on the console? Ping? Please also include the results of running SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-sleep suspend -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#902561: libvirt-daemon: libvirt injects rules into iptables that disable packet filtering
Package: libvirt-daemon Version: 3.0.0-4+deb9u3 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I set up a routed network for virtual machines with this configuration: default eabed2d7-13e3-4bde-a812-f6bb6ce881a6 * What exactly did you do (or not do) that was effective (or ineffective)? I start the virtual network with this command: # virsh net-start default * What was the outcome of this action? libvirt adds these rules to the beginning of the FORWARD chain. This completely bypasses any pre-existing rules and makes it impossible to do packet filtering for virtual machines. -A FORWARD -d 192.168.208.0/24 -o virbr0 -j ACCEPT -A FORWARD -s 192.168.208.0/24 -i virbr0 -j ACCEPT -A FORWARD -i virbr0 -o virbr0 -j ACCEPT -A FORWARD -o virbr0 -j REJECT --reject-with icmp-port-unreachable -A FORWARD -i virbr0 -j REJECT --reject-with icmp-port-unreachable * What outcome did you expect instead? Either the rules should be not added at all - or they should be added at the end of the FORWARD chain, so that they will not bypass existing rules and allow network filtering for virtual machines. *** End of the template - remove these template lines *** -- System Information: Debian Release: 9.4 APT prefers stable APT policy: (500, 'stable') Architecture: arm64 (aarch64) Foreign Architectures: armel, armhf Kernel: Linux 4.17.2 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8), LANGUAGE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages libvirt-daemon depends on: ii libapparmor12.11.0-3+deb9u2 ii libaudit1 1:2.6.7-2 ii libavahi-client30.6.32-2 ii libavahi-common30.6.32-2 ii libblkid1 2.29.2-1+deb9u1 ii libc6 2.24-11+deb9u3 ii libcap-ng0 0.7.7-3+b1 ii libdbus-1-3 1.10.26-0+deb9u1 ii libdevmapper1.02.1 2:1.02.137-2 ii libfuse22.9.7-1 ii libgnutls30 3.5.8-5+deb9u3 ii libnetcf1 1:0.2.8-1+b2 ii libnl-3-200 3.2.27-2 ii libnl-route-3-200 3.2.27-2 ii libnuma12.0.11-2.1 ii libparted2 3.2-17 ii libpcap0.8 1.8.1-3 ii libpciaccess0 0.13.4-1+b2 ii librados2 10.2.5-7.2 ii librbd1 10.2.5-7.2 ii libsasl2-2 2.1.27~101-g0780600+dfsg-3 ii libselinux1 2.6-3+b3 ii libssh2-1 1.7.0-1 ii libudev1232-25+deb9u2 ii libvirt03.0.0-4+deb9u3 ii libxen-4.8 4.8.3+xsa267+shim4.10.1+xsa267-1+deb9u8 ii libxenstore3.0 4.8.3+xsa267+shim4.10.1+xsa267-1+deb9u8 ii libxml2 2.9.4+dfsg1-2.2+deb9u2 ii libyajl22.1.0-2+b3 Versions of packages libvirt-daemon recommends: ii libxml2-utils 2.9.4+dfsg1-2.2+deb9u2 ii netcat-openbsd 1.130-3 ii qemu1:2.8+dfsg-6+deb9u4 Versions of packages libvirt-daemon suggests: ii libvirt-daemon-system 3.0.0-4+deb9u3 pn numad -- no debconf information
Bug#860064: #860064 dnsmasq will not start after dns-root-data upgrade
On Mon, 2018-06-25 at 10:44 +0200, Christoph Martin wrote: > severity 860064 critical > tags 860064 +jessie > thanks > > yesterday jessie and stretch upgraded the dns-root-data package, > which includes the new root DNSSEC keys with a time to live value > added. This is factually incorrect. Absolutely nothing changed in stretch with respect to dns-root-data since October 2017. Please don't spread misinformation. > Because auf this update and the bug in dnsmasq, every dnsmasq > installation on jessie and stretch which has dns-root-data installed > will fail to work. > > The patch in the bug report is easy and works. > > We need an urgent update for jessie and stretch. Why is an update for stretch required, given that nothing changed? Regards, Adam
Bug#875211: unarchiving 875211, reopening 875211
On Wed, Jun 27, 2018 at 10:39:41PM +0200, Helmut Grohne wrote: > unarchive 875211 > reopen 875211 > thanks I have now created a merge request [1] which brings back the switch from Qt 4 to Qt 5. [1]: https://salsa.debian.org/fonts-team/ttfautohint/merge_requests/1 -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#902560: [console-setup] Bad (thousands) separator symbol in the console font
Package: console-setup Version: 1.184 Severity: normal Hello, Unfortunately, bug 895047 is still unsolved with console-setup 1.184. Using UTF-8 French locales here. The new "narrow no-break space" seems to be also replaced anywhere else with the same "diamond" character on the console whatever language I can read is chosen. This occurs with at least Lat-15, Uni1, Uni2 and Uni3 console character sets. --- System information. --- Architecture: amd64 Kernel: Linux 4.14.52-custom Debian Release: 9.4 990 stable-updates deb.debian.org 990 stable deb.debian.org 990 proposed-updates deb.debian.org 777 stretch-backports deb.debian.org 666 testing deb.debian.org --- Package information. --- Depends (Version) | Installed ==-+- console-setup-linux| 1.184 OR console-setup-freebsd | OR hurd | xkb-data (>= 0.9) | 2.19-1+deb9u1 keyboard-configuration (= 1.184) | 1.184 liblocale-gettext-perl | 1.07-3+b1 console-setup-linux| 1.184 OR console-setup-freebsd | OR hurd | xkb-data (>= 0.9) | 2.19-1+deb9u1 keyboard-configuration (= 1.184) | 1.184 kbd (>= 0.99-12) | 2.0.4-3 OR console-tools (>= 1:0.2.3-16) | keyboard-configuration (= 1.184) | 1.184 init-system-helpers(>= 1.29~) | 1.51 OR initscripts| Package Status(Version) | Installed ===-+-=== kbd | 2.0.4-3 console-tools | console-data| 2:1.12-6 console-common | 0.7.90 gnome-control-center| systemd | 237-3~bpo9+1 Package's Recommends field is empty. Suggests (Version) | Installed -+-=== lsb-base (>= 3.0-6) | 9.20170808 locales | 2.27-3 lsb-base (>= 3.0-6) | 9.20170808 locales | 2.27-3 console-setup| 1.184
Bug#902559: some tests can fail if gnupg happens not to be installed
Control: tags -1 - patch This patch does not work properly.
Bug#902559: some tests can fail if gnupg happens not to be installed
Control: retitle -1 some tests can fail if gnupg happens not to be installed
Control: tags -1 + patch
Sean, you might want to try this patch. I still intend to fix up the
commit message, run this through my usual pre-upload tests, etc. but
it should be in sid very soon.
Ian.
>From cb8e3355cf9816b86a16108fd22405624aa5a8f4 Mon Sep 17 00:00:00 2001
From: Ian Jackson
Date: Wed, 27 Jun 2018 21:41:38 +0100
Subject: [PATCH] test suite: gdr-viagit, gdr-newupstream: do not auto-import
t-setup-gnupg. This fixes them in chroots without gnupg.
---
debian/changelog | 2 ++
tests/lib | 12
tests/setup/gdr-convert-gbp | 1 +
tests/setup/gdr-convert-gbp-noarchive | 1 +
tests/tests/gdr-newupstream | 1 +
tests/tests/gdr-viagit| 1 +
6 files changed, 14 insertions(+), 4 deletions(-)
diff --git a/debian/changelog b/debian/changelog
index 4d05abe3..79c398cf 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,8 @@
dgit (5.4~) unstable; urgency=medium
Bugfixes:
+ * test suite: gdr-viagit, gdr-newupstream: do not auto-import
+t-setup-gnupg. This fixes them in chroots without gnupg.
* Fix bug ref to #865444 in previous changelog entry.
--
diff --git a/tests/lib b/tests/lib
index bd06d20d..f3fb0dab 100644
--- a/tests/lib
+++ b/tests/lib
@@ -1134,7 +1134,11 @@ t-alt-test () {
t-git-config dgit.default.old-dsc-distro test-dummy
-case "$0" in
-*/gnupg) ;;
-*) t-setup-import gnupg;;
-esac
+for import in ${autoimport-gnupg}; do
+ case "$0" in
+ */$import) ;;
+ *)
+ t-setup-import $import
+ ;;
+ esac
+done
diff --git a/tests/setup/gdr-convert-gbp b/tests/setup/gdr-convert-gbp
index 0b525c87..7d123414 100755
--- a/tests/setup/gdr-convert-gbp
+++ b/tests/setup/gdr-convert-gbp
@@ -1,5 +1,6 @@
#!/bin/bash
set -e
+autoimport=
. tests/lib
. $troot/lib-gdr
diff --git a/tests/setup/gdr-convert-gbp-noarchive
b/tests/setup/gdr-convert-gbp-noarchive
index dfeea3b9..1d6758b7 100755
--- a/tests/setup/gdr-convert-gbp-noarchive
+++ b/tests/setup/gdr-convert-gbp-noarchive
@@ -1,4 +1,5 @@
#!/bin/bash
+autoimport=
set -e
. tests/lib
. $troot/lib-gdr
diff --git a/tests/tests/gdr-newupstream b/tests/tests/gdr-newupstream
index cfa00523..ee987f51 100755
--- a/tests/tests/gdr-newupstream
+++ b/tests/tests/gdr-newupstream
@@ -1,5 +1,6 @@
#!/bin/bash
set -e
+autoimport=
. tests/lib
t-dependencies NO-DGIT GDR
diff --git a/tests/tests/gdr-viagit b/tests/tests/gdr-viagit
index 644d2d45..a83e622b 100755
--- a/tests/tests/gdr-viagit
+++ b/tests/tests/gdr-viagit
@@ -1,5 +1,6 @@
#!/bin/bash
set -e
+autoimport=
. tests/lib
t-dependencies NO-DGIT GDR
--
2.11.0
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Bug#899021: libembperl-perl: FTBFS with Perl 5.27, unmaintained upstream
Hi Niko, Niko Tyni wrote: > > Anyone can enlighten me if this is a perl bug or, if not, which change > > caused this difference? > > Seems related to > > https://rt.perl.org/Public/Bug/Display.html?id=133301 Thanks! > so undefined behaviour that happened to change now? Ah, so it's probably that multiconcat performance optimisation. And yes, my plan is to make that no more undefined and to work on Perl 5.26 and Perl 5.28 consistently. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#902226: debian-installer-netboot-images: FTBFS in stretch, even when allowing network access
Hi theres, Le lundi, 25 juin 2018, 01.33:38 h CEST Cyril Brulebois a écrit : > Cyril Brulebois (2018-06-24): > > At first glance, it seems to me this bug could be addressed in two > > different ways, which don't seem to be too convoluted. The first way > > would be to try the s-p-u download and fall back to s download, for each > > and every download. But this could (probably only theoretically) lead to > > inconsistent downloads, mixing bits and pieces from s-p-u and from s. > > Plus plenty of errors when the default location isn't the right one. Exactly. If a pure s-p-u build fails, it's because the s-p-u debian-installer isn't built on all architectures, so the d-i-n-i s-p-u build should really fail. (acronyms ftw) > > I suppose a better way would be to figure out with an early test if the > > target version is available in s-p-u or in s, and then pick the right > > suite for all downloads. Patches for this second approach are welcome. That seems more fool-proof and consistent: download from a single suite: either from s-p-u or from stretch only, and for all archs. > I've pushed a prospective branch (pu/fix-ftbfs-in-stretch) with two commits: > https://salsa.debian.org/installer-team/debian-installer-netboot-images/com > mit/86f910f8e1e60e308747a7f53045862705b0a132 > https://salsa.debian.org/installer-team/debian-installer-netboot-images/com > mit/eb2e5b3fb437b288c4c83427fb1c0d213f7b5a5e Looks good to me, given that strategy. > Only checked with the first few architectures (still on limited bandwidth), > but that seems to do the trick. Slightly not happy about having that check > and fallback done for each and every architecture (instead of once and for > all), which could again lead to bits and pieces from both sources mixed > together); but I guess that's a reasonable compromise (no big changes needed > in the code). I've tried for some time to (ab)use make targets to modify DISTRIBUTION depending on partial calls to get_images, but failed. Given my failed attempts, I suspect your patches are the lesser evilfor solving this. But I'm not convinced that solving this is better than ensuring we only ever build "pure-stretch" or "pure-stretch-proposed-updates" d-i-n- i's. > I'll let others comment on this bug report plus proposed solution; Didier > maybe? Thanks for the explicit ping; I'm not on top of Debian things these days. Cheers, OdyX
Bug#899021: libembperl-perl: FTBFS with Perl 5.27, unmaintained upstream
On Wed, Jun 27, 2018 at 10:34:08PM +0200, Axel Beckert wrote:
> Perl 5.26:
>
> → perl -E 'my $i = 0 ; while ($i < 10) { $ii[$i++] = "ii[$i] = $i" ; say
> $ii[$i-1]; } '
> ii[0] = 0
> ii[1] = 1
[...]
> Perl 5.28:
>
> → perl -E 'my $i = 0 ; while ($i < 10) { $ii[$i++] = "ii[$i] = $i" ; say
> $ii[$i-1]; } '
> ii[1] = 1
> ii[2] = 2
> I've skimmed through perl5280delta, but haven't noticed anything which
> explains that difference.
>
> Anyone can enlighten me if this is a perl bug or, if not, which change
> caused this difference?
Seems related to
https://rt.perl.org/Public/Bug/Display.html?id=133301
so undefined behaviour that happened to change now?
--
Niko
Bug#902559: dgit in stretch-backports
Package: dgit
Version: 5.3
Sean Whitton writes ("Re: dgit in stretch-backports"):
> I prepared the backport earlier today but in a stretch chroot the test
> suite has two failures:
>
> gdr-newupstream FAIL non-zero exit status 16
> gdr-viagit FAIL non-zero exit status 16
>
> Ian, could you take a look at the log, please?
This is a bug in the test suite. Specifically, a bug in the
arrangements for working around gnupg2's insistence on timeconsumingly
converting keys when run on a gnupg1 keystore.
The test suite is trying to call gnupg even though (i) it doesn't need
to (ii) there is no gnupg in, or implied, by the test dependencies.
I will upload a fix RSN.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Bug#899021: libembperl-perl: FTBFS with Perl 5.27, unmaintained upstream
Hi,
Dominic Hargreaves wrote:
> The problem in this case might not be that hard to fix,
Basically it's patching what (so far) one test expects to output.
And I can reproduce this difference with pure perl only:
Perl 5.26:
→ perl -E 'my $i = 0 ; while ($i < 10) { $ii[$i++] = "ii[$i] = $i" ; say
$ii[$i-1]; } '
ii[0] = 0
ii[1] = 1
ii[2] = 2
ii[3] = 3
ii[4] = 4
ii[5] = 5
ii[6] = 6
ii[7] = 7
ii[8] = 8
ii[9] = 9
Perl 5.28:
→ perl -E 'my $i = 0 ; while ($i < 10) { $ii[$i++] = "ii[$i] = $i" ; say
$ii[$i-1]; } '
ii[1] = 1
ii[2] = 2
ii[3] = 3
ii[4] = 4
ii[5] = 5
ii[6] = 6
ii[7] = 7
ii[8] = 8
ii[9] = 9
ii[10] = 10
I've skimmed through perl5280delta, but haven't noticed anything which
explains that difference.
Anyone can enlighten me if this is a perl bug or, if not, which change
caused this difference?
Regards, Axel
--
,''`. | Axel Beckert , https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#902354: mirror submission for mirrordebian.una.ac.cr
On Mon, Jun 25, 2018 at 13:02:24 +, Maykol Phillips wrote: > Trace Url: > http://mirrordebian.una.ac.cr/debian/project/trace/mirrordebian.una.ac.cr > Hi, The above trace file says: > Upstream-mirror: ftp.us.debian.org we recommend against syncing from ftp..debian.org names, as the only guarantee made about them is availability over http, not rsync. Would you mind setting things up to sync from e.g. one of ftp.osuosl.org, debian.csail.mit.edu, debian.gtisc.gatech.edu or mirrors.wikimedia.org? Thanks, Julien
Bug#902518: python-tackerclient: FTBFS in buster/sid (ImportError: No module named contextlib2)
Control: reassign -1 python-cmd2 0.8.5-1 Control: retitle -1 python-cmd2: missing dependency on python-contextlib2 Control: affects -1 src:python-tackerclient On Wed, Jun 27, 2018 at 12:50:36PM +, Santiago Vila wrote: > Package: src:python-tackerclient > Version: 0.11.0-4 > Severity: serious > Tags: ftbfs >... > File "/usr/lib/python2.7/dist-packages/cmd2.py", line 111, in > from contextlib2 import redirect_stdout, redirect_stderr > ImportError: No module named contextlib2 >... > If this is really a bug in one of the build-depends, please use reassign and > affects, > so that this is still visible in the page for this package. Thanks for the report, I am reassigning this to python-cmd2 where the bug is. > Thanks. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#900832: libdbd-csv-perl: FTBFS with Perl 5.28: t/82_free_unref_scalar.t failure
On Wed, 27 Jun 2018 22:41:35 +0300, Niko Tyni wrote: > We should probably update libtext-csv-xs-perl and see if that > is enough to resolve the libdbd-csv-perl build issues. libtext-csv-xs-perl 1.36-1 uploaded. Let's see how that goes :) Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- NP: Domenica Vernossa: Figlio a Meta signature.asc Description: Digital Signature
Bug#902558: transition: imagemagick
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Imagemagick upstream break the API in stable 6 version. They are a few security bug and I prefer to go to newest pacakge in order to close the maximum of security bugs without back porting Ben file: title = "imagemagick"; is_affected = .depends ~ /libmagick-core.*-5|libmagick-wand.*-5|libmagick++.*-7/ | .depends ~ /libmagick-core.*-6|libmagick-wand.*-6|libmagick++.*-8/"; is_good = .depends ~ /libmagick-core.*-6|libmagick-wand.*-6|libmagick++.*-8/; is_bad = .depends ~ /libmagick-core.*-5|libmagick-wand.*-5|libmagick++.*-7/; -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#901900: dgit in stretch-backports
Sean Whitton writes ("Re: dgit in stretch-backports"):
> I prepared the backport earlier today but in a stretch chroot the test
> suite has two failures:
>
> gdr-newupstream FAIL non-zero exit status 16
> gdr-viagit FAIL non-zero exit status 16
>
> Ian, could you take a look at the log, please?
>
> I think these are just another gnupg failure that need not delay the
> backport, but it would be good to get your opinion on it.
I think this is something else. I always run the tests on stretch
during development so I don't think there is anything fundamentally
wrong, but the behaviour is certainly odd and does not look like the
usual gnupg2 race bugs. Looking at the error message, line 21
gpg-locked is (roughly)
$DGIT_TEST_REAL_GPG --agent-program=$DGIT_STUNT_AGENT
and this suggests that DGIT_TEST_REAL_GPG is not set. So I think the
most likely explanation is a bug in the test suite. Of course that
means that these tests were not run.
I will see if I can repro it in adt with a stretch chroot.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Bug#901807: libmath-gsl-perl: incompatible with GSL >= 2.5
On Wed, 27 Jun 2018 22:00:49 +0300, Niko Tyni wrote: > On Wed, Jun 27, 2018 at 05:34:50PM +0200, gregor herrmann wrote: > > On Tue, 26 Jun 2018 10:25:06 +0300, Niko Tyni wrote: > > When I `touch xs/*' before dh_auto_build, indeed re-swig-ification is > > skipped for all files; so on the other hand, touching swig/* should > > make sure that it happens. -- Does this make sense? Committed in git > > and pushed. > Yes, I think that makes sense, though explicitly cleaning xs/* away before > the build would be more clear IMO. But I'm fine with the current solution. Ok, I've changed debian/rules to clean the pre-built files, based on your first investigation in this area. > > I'm a bit confused here; the current upload of gsl activates the > > patch which reinstates them but the maintainer sounded like he'd > > prefer to disable the patch again? If I understood this correctly we > > should probably keep our patch, right? > Yes, agreed (even if I was confused myself earlier :) :) Thanks for the confirmations. And uploaded. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- NP: Domenica Vernossa: Figlio a Meta signature.asc Description: Digital Signature
Bug#892321: attempts to suspend failing after crash
On Mon, 18 Jun 2018 10:38:20 +0200 Daniel Pocock wrote: > > > On 18/06/18 09:51, Michael Biebl wrote: > > Am 18.06.2018 um 09:26 schrieb Daniel Pocock: > > > >> The problem: a corrupted swap partition > >> > >> Before deciding how systemd should detect that, it may first be > >> necessary to decide if it is the job of systemd or some other process to > >> detect the problem > > > > How is a swap partition relevant for suspend? > > > > > I don't know, but suspend would not work until I manually resolved the > corruption issue Please try to find out why it failed or if this was actually a red herring. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#902448: timidity: Breaks: timidity-daemon (>= 2.14.0-1~) but 2.14.0-5 is to be installed
Fixed uploaded. BTW this package is a security trap. I plan to open a few CVEs. Did you have wrd karaoke file ? I plan to drop this feature if i could not test bastien On Wed, Jun 27, 2018 at 12:59 PM, Reiner Herrmann wrote: > On Wed, Jun 27, 2018 at 12:53:05PM +0200, Guillem Jover wrote: >> > Most likely you meant to break timidity-daemon (<= 2.14.0-1~) rather >> > than (>= 2.14.0-1~). >> >> I'm not sure that'd be correct either. From the bug that this was >> supposed to fix (because the changelog description is not clear on >> what was broken and what was the fix), this seems to be a new behavior >> from timidity-daemon starting in that version, which does not play nice >> when pulseaudio is also in the system, and both fight for exclusive >> access to the sound devices. >> >> But this seems to be both a (perhaps temporary) workaround (why not >> instead try to diagnose why timidity-daemon now requires exclusive >> access to the sound devices?), and in the wrong place (if the problem >> is with pulseaudio, then either of the packages need to possibly Break >> the other, but not between timidity and timidity-daemon, I for one do >> not have pulseaudio on this particular system for example). > > I also don't think that a Break is required here at all. > If it needs to start after pulseaudio because otherwise the sound device > is blocked, maybe the Required-Start field in the init script needs to > be changed (to $all). > (Maybe that was a regression from the last upgrade that the init script > is started earlier.) > > Regards, > Reiner
Bug#902514: python-cliff: FTBFS in buster/sid (ImportError: No module named enum)
Control: reassign -1 python-cmd2 0.8.5-1 Control: retitle -1 python-cmd2: missing dependency on python-enum34 Control: affects -1 src:python-cliff On Wed, Jun 27, 2018 at 12:50:28PM +, Santiago Vila wrote: > Package: src:python-cliff > Version: 2.11.0-1 > Severity: serious > Tags: ftbfs >... > File "/usr/lib/python2.7/dist-packages/cmd2.py", line 51, in > from enum import Enum > ImportError: No module named enum >... > If this is really a bug in one of the build-depends, please use reassign and > affects, > so that this is still visible in the page for this package. Thanks for the report, I am reassigning this to python-cmd2 where the bug is. > Thanks. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#887538: libdata-validate-email-perl depends on libemail-address-perl
It looks like that there is no upstream github repository... I wrote
simple patch which ports this perl module to use Email::Address::XS.
Patch is attached.
--
Pali Rohár
pali.ro...@gmail.com
diff -Nurp Data-Validate-Email-0.06/Email.pm Data-Validate-Email-0.06/Email.pm
--- Data-Validate-Email-0.06/Email.pm 2017-10-29 16:31:54.0 +0100
+++ Data-Validate-Email-0.06/Email.pm 2018-06-27 21:08:34.630821085 +0200
@@ -6,7 +6,7 @@ use vars qw($VERSION @ISA @EXPORT @EXPOR
require Exporter;
use AutoLoader 'AUTOLOAD';
-use Email::Address;
+use Email::Address::XS 1.01;
use Data::Validate::Domain;
@ISA = qw(Exporter);
@@ -215,7 +215,7 @@ Returns the untainted address on success
=item I
-This check uses Casey West's Email::Address module to do its validation.
+This check uses L module to do its validation.
The function does not make any attempt to check whether an address is
genuinely deliverable. It only looks to see that the format is email-like.
@@ -230,12 +230,9 @@ sub is_email_rfc822{
return unless defined($value);
- #warn $Email::Address::mailbox;
-
my $address;
- if($value =~ /^$Email::Address::mailbox$/){
- #warn $&;
- $address = $&;
+ if(Email::Address::XS->parse($value)->is_valid()){
+ ($address) = $value =~ m/^(.*)$/s;
}
return $address;
diff -Nurp Data-Validate-Email-0.06/Makefile.PL Data-Validate-Email-0.06/Makefile.PL
--- Data-Validate-Email-0.06/Makefile.PL 2017-10-29 16:18:29.0 +0100
+++ Data-Validate-Email-0.06/Makefile.PL 2018-06-27 21:13:26.604696534 +0200
@@ -7,7 +7,7 @@ WriteMakefile(
'DISTNAME' => 'Data-Validate-Email',
'AUTHOR' => 'Richard Sonnen (son...@richardsonnen.com)',
'PREREQ_PM' => {
-'Email::Address' => 0,
+'Email::Address::XS' => 1.01,
'Data::Validate::Domain' => 0.04,
},
'dist' => {
diff -Nurp Data-Validate-Email-0.06/README Data-Validate-Email-0.06/README
--- Data-Validate-Email-0.06/README 2017-10-29 16:18:29.0 +0100
+++ Data-Validate-Email-0.06/README 2018-06-27 21:13:12.204604030 +0200
@@ -102,7 +102,7 @@ FUNCTIONS
Returns the untainted address on success, undef on failure.
*Notes, Exceptions, & Bugs*
-This check uses Casey West's Email::Address module to do its
+This check uses Email::Address::XS module to do its
validation.
The function does not make any attempt to check whether an
signature.asc
Description: PGP signature
Bug#887546: libnet-abuse-utils-perl depends on libemail-address-perl
I created upstream pull request for porting code to Email::Address::XS: https://github.com/mikegrb/Net-Abuse-Utils/pull/28 -- Pali Rohár pali.ro...@gmail.com signature.asc Description: PGP signature
Bug#893393: linux-image-amd64: Kernel panic on active outgoing traffic through Huawei E173 modem in NDIS (CDC) mode
Hi everybody, I'm really greatful about stumbling upon this issue, because it describes the exact same issue I've been experiencing for a while now. Basically whenever I upload file/s via. rsync/Firefox/Chromium, within several seconds my entire Linux system crashes. I've experienced this issue on Debian 10, but it also shows up on ArchLinux. In my case the modem in charge is an M.2. module Huawei ME906s (USB ID 12d1:15c1). I've also tried debugging via. kdump and I've got different kernel errors across multiple crashes and I've tried logging my debugging issue resolving problems on this gist [0]. It doesn't matter if I'm uploading files from a ramfs (/tmp/) or my SATA SSD. I'm also using modemmanager and network-manager. I switched ISP and thought the issue was resolved, but I've just tried uploading a file again and it still crashes my Linux 4.17.2-1-ARCH kernel (so I guess this is a Linux and not Debian only related issue). [0]: https://gist.github.com/norpol/d5b043d6082ace9fc232527d4835f045 or attachment # Debugging Linux Kernel Crash ## Error description: Almost everytime I'm uploading a bigger file (65MB in this case) via. my browser (Firefox, build provided by mozilla.org as `.tar.gz`), my system crashes. Issue especially happens when I'm doing different things at the same time. (Watching a video, reading email + uploading a file). System is using an SSD, bug also appears if the file is served from `/tmp`, though. -,- | -,- --- | --- OS | Debian Testing (Release Buster / 10) Kernel | `Linux 4.14.0-3-amd64 #1 SMP Debian 4.14.17-1 (2018-02-14) x86_64 GNU/Linux` CPU | `Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz` Machine | Thinkpad T560 EFI | `EFI v2.40 by Lenovo, efi: SMBIOS=0xb705e000 ACPI=0xb7ffe000 ACPI 2.0=0xb7ffe014 MPS=0xb7f48000 ESRT=0xb6aa8000` Boot method | efistub storage | Samsung SSD 840 EVO (256GB)`, LUKS (with LVM), rootfs=btrfs, homefs=ext4, cryptswap in LVM` The issue is persistent for multiple Kernel upgrades, though. Also showed up back when Debian testing was called Stretch. Issue mostly appears on file uploads via. LTE-modem. ## Actions - [ ] Intel uCode upgrade didn't help. - [ ] Vendor BIOS/uEFI upgrade didn't help. - [ ] Disabling apparmor didn't help. - [ ] Disabling/chaning IO scheduler didn't help. - [ ] Reinstalling operating system from Debian => archlinux didn't help - [ ] Disabling anything power saving related in BIOS, didn't help - See [Skylake crash bug arstechnica (2017)](https://arstechnica.com/information-technology/2017/06/skylake-kaby-lake-chips-have-a-crash-bug-with-hyperthreading-enabled/) - Basically setting c-state to 1 [might also work](https://askubuntu.com/questions/749349/how-to-set-intel-idle-max-cstate-1) Installing and setup `kdump-tools` (had to set `/proc/cmdline` => `nmi_watchdog=1`, otherwise kdump failed to load kdump kernel on crash). ## Other Early bootup BIOS warning: ``` [ +0.00] Kernel command line: initrd=\initrd.img root=/dev/mapper/system-root resume=UUID=d9506118-b9e2-49db-9385-f731ef1c8615 ro quiet splash crashkernel=384M nmi_watchdog=1 [ +0.00] PID hash table entries: 4096 (order: 3, 32768 bytes) [ +0.00] Calgary: detecting Calgary via BIOS EBDA area [ +0.00] Calgary: Unable to locate Rio Grande table in EBDA - bailing! ``` ### kdump-tools dmesg error trace Note: I have multiple crashes, this is the only one containing `[ cut here ]` section. ``` [ cut here ] WARNING: CPU: 2 PID: 2206 at /build/linux-K4nuoe/linux-4.14.17/mm/vmacache.c:102 vmacache_find+0x96/0xa0 Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp tun bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables devlink iptable_filter cdc_mbim cdc_wdm cdc_ncm snd_hrtimer snd_seq snd_seq_device cpufreq_userspace cpufreq_powersave cpufreq_conservative wireguard(O) ip6_udp_tunnel udp_tunnel binfmt_misc nls_ascii nls_cp437 vfat fat ext4 mbcache jbd2 fscrypto ecb arc4 iwlmvm snd_soc_skl snd_hda_codec_hdmi snd_soc_skl_ipc intel_rapl snd_soc_sst_ipc btusb x86_pkg_temp_thermal snd_soc_sst_dsp intel_powerclamp btrtl mac80211 btbcm snd_hda_ext_core snd_hda_codec_realtek coretemp btintel snd_soc_sst_match efi_pstore snd_hda_codec_generic kvm_intel bluetooth snd_soc_core snd_compress kvm snd_hda_intel irqbypass uvcvideo videobuf2_vmalloc intel_cstate videobuf2_memops intel_uncore videobuf2_v4l2 iwlwifi intel_rapl_perf snd_hda_codec serio_raw wmi_bmof videobuf2_core snd_hda_core efivars rtsx_pci_ms drbg cfg80211 memstick ansi_cprng snd_hwdep cdc_ether option videodev snd_pcm usb_wwan thinkpad_acpi usbnet iTCO_wdt usbserial mei_me snd_timer ecdh_generic nvram mii iTCO_vendor_support media sg crc16 joydev shpchp mei snd soundcore intel_pch_thermal rfkill battery ac evdev nf_conntrack_ipv6 nf_defrag_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nft_counter nft_ct nf_conntrack nft_meta
Bug#902453: aff4: FTBFS in buster/sid
Control: reassign 902453 src:uriparser Control: forcemerge 901955 -1 Control: affects -1 src:aff4 On Tue, Jun 26, 2018 at 10:52:24PM +, Santiago Vila wrote: > Package: src:aff4 > Version: 0.24.post1-4 > Severity: serious > Tags: ftbfs > > Dear maintainer: > > I tried to build this package in buster with "dpkg-buildpackage -A" > but it failed: > > > [...] > debian/rules build-indep > dh build-indep --with autoreconf,python2 --parallel >dh_update_autotools_config -i -O--parallel >dh_autoreconf -i -O--parallel > configure.ac:104: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected > in body > ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from... > ../../lib/autoconf/general.m4:2601: _AC_COMPILE_IFELSE is expanded from... > ../../lib/autoconf/general.m4:2617: AC_COMPILE_IFELSE is expanded from... > m4/uriparser.m4:1: URIPARSER_CHECK is expanded from... > configure.ac:104: the top level > configure.ac:104: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected > in body > ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from... > ../../lib/autoconf/general.m4:2601: _AC_COMPILE_IFELSE is expanded from... >... This is harmless. The actual error message is at the end of the configure output and before the config.log dump: ... checking for uriParseUriA in -luriparser... no configure: error: Please install uriparser 0.6.4 or later. > If this is really a bug in one of the build-depends, please use reassign and > affects, > so that this is still visible in the page for this package. Done. > Thanks. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#901355: stretch-pu: package llvm-4.0/1:4.0.1-10~deb9u1
On Wed, Jun 27, 2018 at 08:18:01PM +0100, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > It's a straightforward rebuild. The debdiff against 1:4.0.1-10 > > from buster is very simple (with an additional build conflicts > > I ran into when preparing the build). > > Please go ahead. Uploaded. Cheers, Moritz
Bug#900832: libdbd-csv-perl: FTBFS with Perl 5.28: t/82_free_unref_scalar.t failure
On Sat, Jun 09, 2018 at 02:56:04PM +0300, Niko Tyni wrote: > On Tue, Jun 05, 2018 at 07:57:47PM +0300, Niko Tyni wrote: > > Package: libdbd-csv-perl > > Version: 0.5300-1 > > Severity: important > > User: debian-p...@lists.debian.org > > Usertags: perl-5.28-transition > > Tags: upstream > > > > This package fails to build with Perl 5.28 (currently in experimental.) > > > > > > http://perl.debian.net/rebuild-logs/perl-5.28-throwaway/libdbd-csv-perl_0.5300-1/libdbd-csv-perl_0.5300-1_amd64-2018-06-05T12:44:50Z.build > > > > # Failed test 'there was an attempt to free unreferenced scalar' > > # at /usr/share/perl/5.28/Test/Builder.pm line 158. > > # Attempt to free unreferenced scalar: SV 0x55afb1de20c0, Perl > > interpreter: 0x55afb02b7260 during global destruction. > > > Test Summary Report > > --- > > t/82_free_unref_scalar.t (Wstat: 0 Tests: 409 Failed: 4) > >Failed tests: 406-409 > >Parse errors: Plan (1..405) must be at the beginning or end of the TAP > > output > > Bad plan. You planned 405 tests but ran 409. > > Files=24, Tests=1158, 4 wallclock secs ( 0.10 usr 0.03 sys + 3.32 cusr > > 0.53 csys = 3.98 CPU) > > Result: FAIL > > This is now also https://rt.perl.org/Ticket/Display.html?id=133270 ... which resulted in https://rt.cpan.org/Ticket/Display.html?id=125589 in Text-CSV_XS (already fixed on CPAN) and https://rt.cpan.org/Ticket/Display.html?id=125590 in DBI We should probably update libtext-csv-xs-perl and see if that is enough to resolve the libdbd-csv-perl build issues. -- Niko Tyni nt...@debian.org
Bug#902557: transition: Perl 5.28
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Forwarded: https://release.debian.org/transitions/html/perl5.28.html X-Debbugs-Cc: p...@packages.debian.org Control: block -1 with 899021 900832 901080 901082 901085 887687 862678 900232 902556 Dear release team, Perl 5.28 is in experimental and we'd like to get it into buster at some point, so filing this a bit pre-emptively. We've been doing test rebuilds of all reverse build dependencies of perl for a while on perl.debian.net, and things are looking pretty good, with the hairiest issue being #887687 (debconf needs qt4-perl which doesn't seem to have a bright future at all). I'm marking this bug as blocked by the handful of 5.28 related regressions we've spotted, and another handful of unrelated build failures in current sid that would prevent the necessary binNMUs. I've excluded packages not in testing, with the exception of libembperl-perl which Axel said he'll be looking at soon. We still want to do a full archive test rebuild soonish: as perl-base is essential and perl is transitively build essential, there are implicit build dependencies in the archive that we haven't covered yet. I don't expect much fallout though. I'll update this bug once we have more data. As usual, bugs are being filed with the usertag debian-p...@lists.debian.org / perl-5.28-transition . See https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=perl-5.28-transition;users=debian-p...@lists.debian.org Thanks for your work, -- Niko Tyni nt...@debian.org
Bug#887687: libsmokeqt4-dev: broken symlinks and causes qt4-perl FTBFS
On Tue, Jun 19, 2018 at 10:05:09AM -0300, Lisandro Damián Nicanor Pérez Meyer wrote: > El jueves, 14 de junio de 2018 14:45:59 -03 Niko Tyni escribió: > > On Fri, Jan 19, 2018 at 06:23:25AM +0200, Adrian Bunk wrote: > > > Package: libsmokeqt4-dev > > > Version: 4:4.14.3-1.2 > > > Severity: serious > > > Control: affects -1 src:qt4-perl > > > > > > qt4-perl FTBFS: > > > > > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/qt4-per > > > l.html > > > > > > /usr/lib/libsmokeqt3support.so and several other .so > > > links are broken. > > > > Just a note that this is going to be a blocker for Perl 5.28 transition, > > which is expected to happen in the next few months. > > > > debconf Build-Depends: libqtgui4-perl which is going to need a binNMU for > > Perl 5.28 but FTBFS because of this bug. > > > > Dear Qt/KDE maintainers: do you think qt4-perl should still be kept alive, > > or should the support in debconf be finally removed (see #629405) ? > > I see there's a prospective alternative KDE debconf frontend (#631769) > > but that seems stalled unfortunately. > > > > Copying the debconf maintainers as well. > > Hi! I have just pinged the rest of the Qt/KDE team for thoughts, as I have > never used this myself so I might not have a good view on the issue. > > I'll try to follow up soon, but please ping me again (IRC is valid too) if I > don't cam up with a reply in, let's say, 5 to 7 days. Hi, any news here? FWIW Perl 5.28.0 final was released recently and is now in experimental. It would be great to get this issue moving forward one way or another. Many thanks for your work on Debian, -- Niko Tyni nt...@debian.org
Bug#901355: stretch-pu: package llvm-4.0/1:4.0.1-10~deb9u1
Control: tags -1 + confirmed On Mon, 2018-06-11 at 23:06 +0200, Moritz Muehlenhoff wrote: > Firefox/Thunderbird ESR60 will require rustc 1.24 (which in turn > requires LLVM 4.0). llvm-4.0 is not yet in stretch, so this would > add a new package to it. ACK. Not ideal, but... > It's a straightforward rebuild. The debdiff against 1:4.0.1-10 > from buster is very simple (with an additional build conflicts > I ran into when preparing the build). Please go ahead. Regards, Adam
Bug#902556: libperl-apireference-perl: missing Perl 5.28 support
Package: libperl-apireference-perl
Version: 0.22-8
Severity: important
User: debian-p...@lists.debian.org
Usertags: perl-5.28-transition
This package fails to build with Perl 5.28 (currently in experimental).
http://perl.debian.net/rebuild-logs/perl-5.28-throwaway/libperl-apireference-perl_0.22-8/libperl-apireference-perl_0.22-8_amd64-2018-06-08T18:29:44Z.build
echo Current Perl is `perl -MConfig -we'printf("%d_%03d_%03d.pm",
$Config{PERL_REVISION}, $Config{PERL_VERSION}, $Config{PERL_SUBVERSION})'`
Current Perl is 5_028_000.pm
test -f lib/Perl/APIReference/V`perl -MConfig -we'printf("%d_%03d_%03d.pm",
$Config{PERL_REVISION}, $Config{PERL_VERSION}, $Config{PERL_SUBVERSION})'`
make[1]: *** [debian/rules:16: regenerated-stamp] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:4: build] Error 2
--
Niko Tyni nt...@debian.org
Bug#902555: radeon.4: Some fixes in the manual
Package: xserver-xorg-video-radeon
Version: 1:18.0.1-1
Severity: minor
Tags: patch
Dear Maintainer,
Summary of changes:
Remove superfluous quotation marks (") from the argument of a
single-font macro.
Use a better presentation for an ellipsis (with narrow space between
the periods).
Split long lines (> 80).
Begin a sentence on a new line if there is only one space separating
sentences.
Don't begin a sentence with a digit.
Add a comma after "e.g.".
Separate numbers from the units (with an unpaddable space).
Change - to \- if it shall be printed as a minus.
Change a two-fonts macro to an one-font macro for a
single argument.
Protect . if not an end of sentence.
Don't repeat a "long" word, but rephrase the text.
Use "tbl" to create a table, otherwise the text looks ugly with a
proportional font.
Protect . if not an end of sentence.
The patch is in the attachment.
-- System Information:
Debian Release: buster/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500,
'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.110-1 (SMP w/2 CPU cores)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1),
LANGUAGE=is_IS.iso88591 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages xserver-xorg-video-radeon depends on:
ii libc6 2.27-3
ii libdrm-radeon1 2.4.92-1
ii libudev1 238-5
ii xserver-xorg-core [xorg-video-abi-23] 2:1.19.6-1
xserver-xorg-video-radeon recommends no packages.
Versions of packages xserver-xorg-video-radeon suggests:
ii firmware-amd-graphics 20170823-1
-- no debconf information
--
Bjarni I. Gislason
--- radeon.42018-03-20 12:17:16.0 +
+++ radeon.4.new2018-06-27 01:55:21.0 +
@@ -1,13 +1,14 @@
+'\" t
.ds q \N'34'
.TH RADEON 4 "xf86-video-ati 18.0.1" "X Version 11"
.SH NAME
radeon \- ATI/AMD RADEON video driver
.SH SYNOPSIS
.nf
-.B "Section \*qDevice\*q"
+.B Section \*qDevice\*q
.BI " Identifier \*q" devname \*q
.B " Driver \*qradeon\*q"
-\ \ ...
+\ \ \&.\|.\|.\&
.B EndSection
.fi
.SH DESCRIPTION
@@ -18,7 +19,8 @@ following features:
.PD 0
.TP 2
\(bu
-Full support for 8-, 15-, 16- and 24-bit pixel depths, and for 30-bit depth on
Linux 3.16
+Full support for 8-, 15-, 16- and 24-bit pixel depths, and for 30-bit
+depth on Linux 3.16
and later;
.TP
\(bu
@@ -37,7 +39,8 @@ only available on R/RV3xx, R/RV/RS4xx, R
.SH SUPPORTED HARDWARE
The
.B radeon
-driver supports PCI, AGP, and PCIe video cards based on the following ATI/AMD
chips
+driver supports PCI, AGP, and PCIe video cards based on the following
+ATI/AMD chips
(note: list is non-exhaustive):
.PP
.PD 0
@@ -243,33 +246,43 @@ Option \*qZaphodHeads\*q \*qLVDS,VGA-0\*
will assign xrandr outputs LVDS and VGA-0 to this instance of the driver.
.TP
.BI "Option \*qColorTiling\*q \*q" "boolean" \*q
-The framebuffer can be addressed either in linear or tiled mode. Tiled mode
can provide
-significant performance benefits with 3D applications. Tiling will be
disabled if the drm
-module is too old or if the current display configuration does not support it.
On R600+
-this enables 1D tiling mode.
+The framebuffer can be addressed either in linear or tiled mode.
+Tiled mode can provide
+significant performance benefits with 3D applications.
+Tiling will be disabled if the drm
+module is too old or if the current display configuration does not support
+it.
+On R600+ this enables 1D tiling mode.
.br
The default value is
.B on
-for R/RV3XX, R/RV4XX, R/RV5XX, RS6XX, RS740, R/RV6XX, R/RV7XX, RS780, RS880,
-EVERGREEN, CAYMAN, ARUBA, Southern Islands, and Sea Islands and
+for R/RV3XX, R/RV4XX, R/RV5XX, RS6XX, RS740, R/RV6XX, R/RV7XX, RS780,
+RS880, EVERGREEN, CAYMAN, ARUBA, Southern Islands, and Sea Islands and
.B off
-for R/RV/RS1XX, R/RV/RS2XX, RS3XX, and RS690/RS780/RS880 when fast fb feature
is enabled.
+for R/RV/RS1XX, R/RV/RS2XX, RS3XX, and RS690/RS780/RS880 when fast fb
+feature is enabled.
.TP
.BI "Option \*qColorTiling2D\*q \*q" "boolean" \*q
-The framebuffer can be addressed either in linear, 1D, or 2D tiled modes. 2D
tiled mode can
-provide significant performance benefits over 1D tiling with 3D applications.
Tiling
-will be disabled if the drm module is too old or if the current display
configuration
-does not support it. KMS ColorTiling2D is only supported on R600 and newer
chips and requires
-Mesa 9.0 or newer for R6xx-ARUBA, Mesa 9.2 or newer for Southern Islands, and
Mesa
-10.1 or newer for Sea Islands.
+The framebuffer can be addressed either in linear, 1D, or 2D tiled
+modes.
+The 2D tiled mode can
+provide significant performance benefits over 1D tiling with 3D
+applications.
+Tiling will be disabled if the drm module is too old or if the current
+display configuration does not support it.
+KMS
Bug#901807: libmath-gsl-perl: incompatible with GSL >= 2.5
On Wed, Jun 27, 2018 at 05:34:50PM +0200, gregor herrmann wrote: > On Tue, 26 Jun 2018 10:25:06 +0300, Niko Tyni wrote: > When I `touch xs/*' before dh_auto_build, indeed re-swig-ification is > skipped for all files; so on the other hand, touching swig/* should > make sure that it happens. -- Does this make sense? Committed in git > and pushed. Yes, I think that makes sense, though explicitly cleaning xs/* away before the build would be more clear IMO. But I'm fine with the current solution. > I'm a bit confused here; the current upload of gsl activates the > patch which reinstates them but the maintainer sounded like he'd > prefer to disable the patch again? If I understood this correctly we > should probably keep our patch, right? Yes, agreed (even if I was confused myself earlier :) Dirk mainly wants to get rid of the divergence from upstream, and upstream is not including the deprecated functions by default. We'll see if libgsl is going to get an SONAME bump in Debian just for this (effectively creating another divergence...) or if it will be deferred to a future upstream SONAME bump. In any case, if we keep the patch we should be compatible with whatever happens. And as the deprecated functions are going away at some point, we shouldn't expose them through the Perl bindings anymore. > And I guess at least if we keep "our" patch, we don't need a > versioned build dependency? That's what I think too. -- Niko
Bug#902546: amule-daemon: crashes on start: 0.0.0.0 4712 failed - Address already in use
> !2018-06-27 17:37:30: Asio Sockets: CAsioSocketServerImpl bind to 0.0.0.0 > 4712 failed - Address already in use > 2018-06-27 17:37:30: Could not listen for external connections at > 0.0.0.0:4712! > !2018-06-27 17:37:30: Error creating UDP socket 0.0.0.0 4665 : Address > already in use > !2018-06-27 17:37:30: MuleUDPSocket: Failed to create valid Server UDP-Socket > !2018-06-27 17:37:30: Asio Sockets: CAsioSocketServerImpl bind to 0.0.0.0 > 4662 failed - Address already in use [8<] > But the ports are not in use, according to F User. are you absolutely sure there is nothing using those ports, like a stuck amule process? did u use fuser as root? did you check also via netstat? what if you reboot the machine where this is running (i know the impact of this could be high)? do you have an actual backtrace from amule (the port in use could be a red herring for some other issue)? as you said, amule has worked for you since years, weird something happened right now out of the blue that's related to the package version in stable, which we havent touched in months. -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
Bug#889854: RFS: lxml/4.2.1-1~bpo9+1 [intent to maintain bpo]
Hi Chris, On Wed, Jun 27, 2018 at 09:31:43AM +0100, Chris Lamb wrote: > tags 889854 + pending > thanks > > Hi Nicholas, > > (Shame to spend effort where upstream is so toxic, alas...). Mm, I've read a bit about it... I wonder if he'll really maintain Python 2? > Anyway, > I've uploaded: > > lxml_4.2.1-1~bpo9+1_amd64.changes > html5-parser_0.4.4-1~bpo9+1_amd64.changes > > .. to -backports. Thank you very much :-) > Calibre does not install its build-dependencies, even after installing > the results of the above builds: > > dpkg-deb: building package 'calibre-build-deps' in > '../calibre-build-deps_3.26.0+dfsg-1~bpo9+1_amd64.deb'. > > The package has been created. > Attention, the package has been created in the current directory, > not in ".." as indicated by the message above! > Selecting previously unselected package calibre-build-deps. > (Reading database ... 24786 files and directories currently installed.) > Preparing to unpack calibre-build-deps_3.26.0+dfsg-1~bpo9+1_amd64.deb ... > Unpacking calibre-build-deps (3.26.0+dfsg-1~bpo9+1) ... > Reading package lists... Done > Building dependency tree > Reading state information... Done > Correcting dependencies...Starting pkgProblemResolver with broken count: 1 > Starting 2 pkgProblemResolver with broken count: 1 > Investigating (0) debhelper:amd64 < 11.3.2~bpo9+1 @ii mK Ib > > Broken debhelper:amd64 Breaks on qt5-qmake:amd64 < none -> 5.7.1+dfsg-3+b1 > @un uN > (< 5.9.2+dfsg-8) > Considering qt5-qmake:amd64 1 as a solution to debhelper:amd64 7 > Added qt5-qmake:amd64 to the remove list > Fixing debhelper:amd64 via keep of qt5-qmake:amd64 > Investigating (0) qtbase5-dev:amd64 < none -> 5.7.1+dfsg-3+b1 @un uN Ib > > Broken qtbase5-dev:amd64 Depends on qt5-qmake:amd64 < none | > 5.7.1+dfsg-3+b1 @un uH > (= 5.7.1+dfsg-3+b1) > Considering qt5-qmake:amd64 1 as a solution to qtbase5-dev:amd64 1 > Holding Back qtbase5-dev:amd64 rather than change qt5-qmake:amd64 > Investigating (0) qtbase5-private-dev:amd64 < none -> 5.7.1+dfsg-3+b1 @un > uN Ib > > Broken qtbase5-private-dev:amd64 Depends on qtbase5-dev:amd64 < none | > 5.7.1+dfsg-3+b1 @un uH > (= 5.7.1+dfsg-3+b1) > Considering qtbase5-dev:amd64 1 as a solution to > qtbase5-private-dev:amd64 0 > Holding Back qtbase5-private-dev:amd64 rather than change > qtbase5-dev:amd64 > Investigating (0) calibre-build-deps:amd64 < 3.26.0+dfsg-1~bpo9+1 @iU mK Nb > Ib > > Broken calibre-build-deps:amd64 Depends on qt5-qmake:amd64 < none | > 5.7.1+dfsg-3+b1 @un uH > > Considering qt5-qmake:amd64 1 as a solution to calibre-build-deps:amd64 -2 > Removing calibre-build-deps:amd64 rather than change qt5-qmake:amd64 > Done >Done > Starting pkgProblemResolver with broken count: 0 > Starting 2 pkgProblemResolver with broken count: 0 > Done > The following packages were automatically installed and are no longer > required: > e2fslibs qtchooser > Use 'sudo apt autoremove' to remove them. > The following packages will be REMOVED: > calibre-build-deps > 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. > 1 not fully installed or removed. > After this operation, 10.2 kB disk space will be freed. > (Reading database ... 24790 files and directories currently installed.) > Removing calibre-build-deps (3.26.0+dfsg-1~bpo9+1) ... > mk-build-deps: Unable to install calibre-build-deps at > /usr/bin/mk-build-deps line 402. > mk-build-deps: Unable to install all build-dep packages > > No time to debug, sorry... This issue sounds like "Using backported debhelper considered tricky" ( https://lists.debian.org/debian-backports/2018/06/msg00037.html ). I believe that the reason I am not able to trigger it in my bpo chroot, is because Calibre Build-Depends on "debhelper (>= 9)" and the debhelper 11 bpo is only installed when a package requires it. My hypothesis is that your backporting chroot has 11~bpo for some other reason. Html5-parser build-deps on dh >=10, which is also fulfilled by stretch's 10.2.5. That said, I have 11.3.2~bpo9+1 installed on my main system. Is it possible that's causing a problem with the generated source package? > > Other URLS: > > > > https://mentors.debian.net/package/lxml > > https://mentors.debian.net/package/html5-parser > > https://mentors.debian.net/package/calibre > > Not sure why you linked these. Provided purely for convenience. Sincerely, Nicholas signature.asc Description: PGP signature
Bug#902554: snort FTCBFS: configures for the build architecture
Source: snort
Version: 2.9.7.0-5
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
snort fails to cross build from source, because it configures for the
build architecture. The easiest way of passing the relevant --host flag
is using dh_auto_configure. The attached patch implements that. It
doesn't make snort cross build as there are subsequent failures to be
sorted out. Please consider applying the patch anyway and close this bug
when doing so.
Helmut
diff --minimal -Nru snort-2.9.7.0/debian/changelog
snort-2.9.7.0/debian/changelog
--- snort-2.9.7.0/debian/changelog 2015-06-30 00:55:04.0 +0200
+++ snort-2.9.7.0/debian/changelog 2018-06-27 19:29:21.0 +0200
@@ -1,3 +1,11 @@
+snort (2.9.7.0-5.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Improve cross buiding: Let dh_auto_configure pass --host to ./configure.
+(Closes: #-1)
+
+ -- Helmut Grohne Wed, 27 Jun 2018 19:29:21 +0200
+
snort (2.9.7.0-5) unstable; urgency=medium
* debian/control: Depend on perl, not perl-modules (Closes: #779126)
diff --minimal -Nru snort-2.9.7.0/debian/rules snort-2.9.7.0/debian/rules
--- snort-2.9.7.0/debian/rules 2014-12-12 01:55:55.0 +0100
+++ snort-2.9.7.0/debian/rules 2018-06-27 19:29:17.0 +0200
@@ -27,9 +27,8 @@
export CFLAGS
-CONFFLAGS= --prefix=/usr \
+CONFFLAGS= \
--bindir=\$$\{exec_prefix\}/sbin \
- --mandir=\$$\{exec_prefix\}/share/man \
--enable-zlib \
--enable-ipv6 \
--enable-gre \
@@ -76,7 +75,7 @@
dh_testdir
dh_autoreconf
# Standard package configuration:
- ./configure $(CONFFLAGS)
+ dh_auto_configure -- $(CONFFLAGS)
touch $@
# Basic 'flavor' package
Bug#889854: Fwd: lxml_4.2.1-1~bpo9+1_amd64.changes REJECTED
On Wed, Jun 27, 2018 at 09:39:07AM +0100, Chris Lamb wrote: > Not sure what I did... Just forwarding here to keep the converation > altogether. > > > - Original message - > From: Debian FTP Masters > To: la...@debian.org, Matthias Klose , Nicholas D Steeves > > Subject: lxml_4.2.1-1~bpo9+1_amd64.changes REJECTED > Date: Wed, 27 Jun 2018 08:35:43 + > > > lxml_4.2.1.orig.tar.gz: Does not match file already existing in the pool. > > > binary:python-lxml is NEW. > binary:python-lxml-dbg is NEW. > binary:python-lxml-doc is NEW. > binary:python3-lxml is NEW. > binary:python3-lxml-dbg is NEW. > binary:python-lxml-doc is NEW. > binary:python-lxml-dbg is NEW. > binary:python3-lxml is NEW. > binary:python-lxml is NEW. > binary:python3-lxml-dbg is NEW. > source:lxml is NEW. It definitely wasn't your fault. My mentors upload was so long ago that I decided to just reupload with a fresh copy of the orig tarball that I've verified matches the sha256sum of the one that's already in the archive. https://mentors.debian.net/debian/pool/main/l/lxml/lxml_4.2.1-1~bpo9+1.dsc If I had to guess what happened, my gbp rebuilt the tarball. Sorry. Cheers, Nicholas signature.asc Description: PGP signature
Bug#902553: new version (2.8.0) is out and heals the annoying warning msg
Package: python-h5py Version: 2.7.1-2 Severity: normal one of the annoyances of h5py in Debian now is that a bare import leads to $> python -c 'import h5py' /usr/lib/python2.7/dist-packages/h5py/__init__.py:36: FutureWarning: Conversion of the second argument of issubdtype from `float` to `np.floating` is deprecated. In future, it will be treated as `np.float64 == np.dtype(float).type`. from ._conv import register_converters as _register_converters making into output of cmdline helpers etc... 2.8.0 seems to have no such issue: (git)hopa:~/proj/misc/h5py[tags/2.8.0^0] $> python -c 'import h5py' That is why marking it as normal bug instead of a mere wishlist Watchout for: - there is no changelog for 2.8.x: https://github.com/h5py/h5py/issues/1064 - somewhat changed behavior: https://github.com/h5py/h5py/issues/1063 (this affects python-mvpa2 -- will need to fixup for it now upstream for now, may be there is more) Cheers and thanks in advance -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (600, 'unstable'), (300, 'experimental'), (100, 'unstable-debug'), (100, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python-h5py depends on: ii libc6 2.27-2 ii libhdf5-100 1.10.0-patch1+docs-4 ii python2.7.14-4 ii python-numpy [python-numpy-abi9] 1:1.14.3-2 ii python-six1.11.0-2 python-h5py recommends no packages. Versions of packages python-h5py suggests: pn python-h5py-doc -- debconf-show failed
Bug#901900: dgit in stretch-backports
Hello, On Tue, Jun 26 2018, Jonathan Nieder wrote: > Thanks again for this pointer. dgit 5.2 has now hit testing. If > there is anything I can do to help with getting it into > stretch-backports, please don't hesitate to let me know. I prepared the backport earlier today but in a stretch chroot the test suite has two failures: gdr-newupstream FAIL non-zero exit status 16 gdr-viagit FAIL non-zero exit status 16 Ian, could you take a look at the log, please? I think these are just another gnupg failure that need not delay the backport, but it would be good to get your opinion on it. -- Sean Whitton dgit_5.2~bpo9+1_i386.build Description: Binary data signature.asc Description: PGP signature
Bug#902552: linux-image-4.17.0-trunk-amd64-unsigned: enable CONFIG_Z3FOLD
Package: src:linux Version: 4.17.2-1~exp1 Severity: normal Dear Maintainer, Please enable CONFIG_Z3FOLD. It makes higher compression possible with zswap. Thank you, -- Package-specific info: ** Version: Linux version 4.17.0-trunk-amd64 (debian-ker...@lists.debian.org) (gcc version 7.3.0 (Debian 7.3.0-23)) #1 SMP Debian 4.17.2-1~exp1 (2018-06-19) ** Command line: BOOT_IMAGE=/vmlinuz-4.17.0-trunk-amd64 root=/dev/mapper/linux-root ro resume=/dev/mapper/linux-swap transparent_hugepage=always pcie_aspm=force zswap.enabled=1 zswap.compressor=lz4 ** Tainted: E (8192) * Unsigned module has been loaded. ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: SAMSUNG ELECTRONICS CO., LTD. product_name: N150/N210/N220 product_version: Not Applicable chassis_vendor: SAMSUNG ELECTRONICS CO., LTD. chassis_version: N/A bios_vendor: Phoenix Technologies Ltd. bios_version: 06JI.M053.20100129.JIP board_vendor: SAMSUNG ELECTRONICS CO., LTD. board_name: N150/N210/N220 board_version: Not Applicable ** Loaded modules: btrfs(E) zstd_compress(E) zstd_decompress(E) xxhash(E) xor(E) raid6_pq(E) ufs(E) qnx4(E) hfsplus(E) hfs(E) minix(E) ntfs(E) vfat(E) msdos(E) fat(E) jfs(E) xfs(E) msr(E) cpuid(E) fuse(E) ip6t_REJECT(E) nf_reject_ipv6(E) xt_multiport(E) ip6table_mangle(E) ip6table_nat(E) nf_nat_ipv6(E) nf_conntrack_ipv6(E) nf_defrag_ipv6(E) ip6table_raw(E) nf_log_ipv6(E) ip6table_filter(E) ip6_tables(E) xt_recent(E) ipt_REJECT(E) nf_reject_ipv4(E) xt_comment(E) xt_conntrack(E) xt_hashlimit(E) xt_addrtype(E) xt_mark(E) iptable_mangle(E) iptable_nat(E) nf_nat_ipv4(E) nf_conntrack_ipv4(E) nf_defrag_ipv4(E) xt_tcpudp(E) xt_CT(E) iptable_raw(E) xt_NFLOG(E) nfnetlink_log(E) nf_log_ipv4(E) nf_log_common(E) xt_LOG(E) nf_conntrack_sane(E) nf_conntrack_netlink(E) nfnetlink(E) nf_nat_tftp(E) nf_nat_snmp_basic(E) nf_conntrack_snmp(E) nf_nat_sip(E) nf_nat_pptp(E) nf_nat_proto_gre(E) nf_nat_irc(E) nf_nat_h323(E) nf_nat_ftp(E) nf_nat_amanda(E) nf_nat(E) nf_conntrack_tftp(E) nf_conntrack_sip(E) nf_conntrack_pptp(E) nf_conntrack_proto_gre(E) nf_conntrack_netbios_ns(E) nf_conntrack_broadcast(E) nf_conntrack_irc(E) nf_conntrack_h323(E) nf_conntrack_ftp(E) ts_kmp(E) nf_conntrack_amanda(E) nf_conntrack(E) libcrc32c(E) iptable_filter(E) ctr(E) ccm(E) uvcvideo(E) videobuf2_vmalloc(E) videobuf2_memops(E) videobuf2_v4l2(E) videobuf2_common(E) videodev(E) media(E) btusb(E) btrtl(E) btbcm(E) btintel(E) bluetooth(E) jitterentropy_rng(E) drbg(E) ansi_cprng(E) ecdh_generic(E) iTCO_wdt(E) iTCO_vendor_support(E) coretemp(E) pcspkr(E) joydev(E) evdev(E) serio_raw(E) arc4(E) i915(E) ath9k(E) snd_hda_codec_realtek(E) ath9k_common(E) ath9k_hw(E) snd_hda_codec_generic(E) ath(E) sg(E) snd_hda_intel(E) snd_hda_codec(E) snd_hda_core(E) mac80211(E) drm_kms_helper(E) lpc_ich(E) snd_hwdep(E) cfg80211(E) snd_pcm(E) snd_timer(E) snd(E) battery(E) drm(E) soundcore(E) button(E) ac(E) i2c_algo_bit(E) shpchp(E) acpi_cpufreq(E) samsung_laptop(E) rfkill(E) video(E) zram(E) zsmalloc(E) loop(E) parport_pc(E) ppdev(E) lp(E) parport(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) crc32c_generic(E) fscrypto(E) ecb(E) crypto_simd(E) cryptd(E) glue_helper(E) aes_x86_64(E) dm_mod(E) sd_mod(E) ahci(E) libahci(E) psmouse(E) libata(E) uhci_hcd(E) i2c_i801(E) ehci_pci(E) ehci_hcd(E) scsi_mod(E) usbcore(E) sky2(E) usb_common(E) thermal(E) lz4(E) lz4_compress(E) ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx DMI Bridge [8086:a010] Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:02.0 VGA compatible controller [0300]: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: i915 Kernel modules: i915 00:02.1 Display controller [0380]: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a012] Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High Definition Audio Controller [8086:27d8] (rev 02) Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV-
Bug#902551: [cython3] Miscompilation of exception handling with global tuple as exception type (since 0.28.2-1)
Package: cython3 Version: 0.28.2-4 Severity: important Tags: patch --- Please enter the report below this line. --- cython 0.28.x-x miscompiles exception handling, if a global tuple is used as exception type. This is the upstream bug: https://github.com/cython/cython/issues/2425 This is the upstream fix: https://github.com/cython/cython/commit/7f41244db2479eaf07343c5d3b07b4183fc6877a --- System information. --- Architecture: Kernel: Linux 4.16.0-2-amd64 Debian Release: buster/sid 500 unstableftp.de.debian.org --- Package information. --- Depends (Version) | Installed =-+-== python3 (<< 3.7) | 3.6.5-3 python3 (>= 3.6~) | 3.6.5-3 python3:any (>= 3.3.2-2~) | libc6 (>= 2.14) | Recommends (Version) | Installed ==-+-=== python3-dev| 3.6.5-3 gcc| 4:7.3.0-3 Suggests(Version) | Installed =-+-=== cython-doc| -- Michael pgpgVnA2FncwY.pgp Description: OpenPGP digital signature
Bug#901927: Manpage suggestions
Hello, On Wed, Jun 27 2018, Ian Jackson wrote: > Looking at the top of git-debrebase(5), the 2nd half of INTRODUCTION > is rather discursive. Maybe add a section heading just before, > DISCUSSION or something, and put the gitk thing there ? This seems fine. If we were to add more tips in the future, we would want the dedicated section. -- Sean Whitton signature.asc Description: PGP signature
Bug#840075: How to help getting libfuse updated?
On Wed, Jun 27, 2018 at 1:09 PM Nikolaus Rath wrote: > > > Please let me know if there is anything I can do. > > > > I've a bug report and a feature request. Will post it on your Git > > repository. > > Are you still working on this, or am I looking in the wrong place for it? I > checked https://github.com/libfuse/libfuse/issues. I'm slower nowadays than I'd like to be. Especially that I've fixed three issues and sent you a pull request. Only one feature request was filed. Cheers, Laszlo/GCS
Bug#901544: Make libwx-perl build reproducible
Control: tag -1 + pending On Mon, 25 Jun 2018 22:44:23 +, Brüns, Stefan wrote: > > So maybe I picked the wrong patches or reprotest (or my reprotest > > setup) has a problem or our other patches cause issues or something > > else -- but I can't get a reproducible package locally. > You need *all* patches but the ABI patch. In the meantime, 2 more patches > were > added, as there where spurious reorderings. Sorry for not including the patches which weren't there when I last looked :) (And missing another one.) After adding 0003-Define-overload-constants-in-sorted-order.patch 0004-Define-enum-values-in-sorted-order.patch 0001-fix-incomplete-Wx_Exp.pm-due-to-missing-dependecy-in.patch reprotest (in my config) is indeed happy: INFO:reprotest:Running diffoscope: ['diffoscope', '--exclude-directory-metadata', '/tmp/tmp4skonyq7/control', '/tmp/tmp4skonyq7/experiment-1'] INFO:reprotest:No differences between /tmp/tmp4skonyq7/control, /tmp/tmp4skonyq7/experiment-1 === Reproduction successful === No differences in ./../*.deb f71312e5cd6f14f820a37fff2803b84c70dccd57d157fec9d3ab2005d9d10e4f ./../libwx-perl-dbgsym_0.9932-5_amd64.deb 9b4e24559daad9c770461d7fc4359a82505b0b52f0f243582883d40a0b55cc86 ./../libwx-perl_0.9932-5_amd64.deb Thanks again for your help. Olly, as you know the package much better than me, could you take a look as well in case some of my (other) changes might cause any issues? Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- NP: Track 12 signature.asc Description: Digital Signature
Bug#902549: chntpw FTCBFS: uses the build architecture compiler
Source: chntpw Version: 1.0-1 Tags: patch User: helm...@debian.org Usertags: rebootstrap chntpw fails to cross build from source, because it uses the build architecture compiler. The easiest way of passing cross tools to make is using dh_auto_build. After doing so, chntpw cross builds successfully. Please consider applying the attached patch. Helmut diff -u chntpw-1.0/debian/changelog chntpw-1.0/debian/changelog --- chntpw-1.0/debian/changelog +++ chntpw-1.0/debian/changelog @@ -1,3 +1,11 @@ +chntpw (1.0-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: Let dh_auto_build pass cross tools to make. (Closes: #-1) + * Remove unused/wrong INSTALL_PROGRAM variable. + + -- Helmut Grohne Wed, 27 Jun 2018 19:08:50 +0200 + chntpw (1.0-1) unstable; urgency=low * Update to latest upstream release, published in 2014-02-01 diff -u chntpw-1.0/debian/control chntpw-1.0/debian/control --- chntpw-1.0/debian/control +++ chntpw-1.0/debian/control @@ -2,7 +2,7 @@ Section: admin Priority: optional Maintainer: Javier Fernandez-Sanguino Peña -Build-Depends: debhelper (>= 5), libgcrypt11-dev | libgcrypt-dev, sharutils, quilt, dpkg-dev ( >= 1.16.1~) +Build-Depends: debhelper (>= 7), libgcrypt11-dev | libgcrypt-dev, sharutils, quilt, dpkg-dev ( >= 1.16.1~) Standards-Version: 3.9.5 Homepage: http://pogostick.net/~pnh/ntpasswd/ diff -u chntpw-1.0/debian/rules chntpw-1.0/debian/rules --- chntpw-1.0/debian/rules +++ chntpw-1.0/debian/rules @@ -17,9 +17,6 @@ ifneq (,$(findstring debug,$(DEB_BUILD_OPTIONS))) CFLAGS += -g endif -ifeq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS))) - INSTALL_PROGRAM += -s -endif ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS))) CFLAGS += -O0 else @@ -31,7 +28,7 @@ build-indep: build-stamp build-stamp: $(QUILT_STAMPFN) dh_testdir - $(MAKE) CFLAGS="$(CFLAGS)" + dh_auto_build -- CFLAGS="$(CFLAGS)" touch build-stamp clean: unpatch
Bug#902550: [firefox] Cannot use translations because the add-on is not signed
Package: firefox Version: 61.0-1 Severity: normal Installing Firefox language packs (e.g firefox-l10n-ru) didn't have an effect. I looked at Add-ons > Language packs and saw the following warning: Russian (RU) Language Pack could not be verified for use in Firefox. Proceed with caution. Disabling signature verification somewhere at about:config did solve the issue. --- System information. --- Architecture: Kernel: Linux 4.16.0-2-amd64 Debian Release: buster/sid 990 testing ftp.by.debian.org 500 unstableftp.by.debian.org --- Package information. --- Depends (Version) | Installed ===-+-=== libatk1.0-0 (>= 1.12.4) | 2.28.1-1 libc6 (>= 2.27) | libcairo-gobject2 (>= 1.10.0) | libcairo2 (>= 1.10.0) | libdbus-1-3 (>= 1.9.14) | libdbus-glib-1-2 (>= 0.78) | libevent-2.1-6(>= 2.1.8-stable) | libffi6 (>= 3.0.4) | libfontconfig1 (>= 2.12.6) | libfreetype6 (>= 2.2.1) | libgcc1 (>= 1:4.2) | libgdk-pixbuf2.0-0 (>= 2.22.0) | libglib2.0-0(>= 2.31.8) | libgtk-3-0 (>= 3.0.0) | libhunspell-1.6-0 | libjsoncpp1 (>= 1.7.4) | libnspr4 (>= 2:4.10.9) | libnss3(>= 2:3.34~) | libpango-1.0-0 (>= 1.14.0) | libsqlite3-0(>= 3.14.0) | libstartup-notification0 (>= 0.8) | libstdc++6 (>= 6) | libvpx5 (>= 1.6.0) | libx11-6| libx11-xcb1 | libxcb-shm0 | libxcb1 | libxcomposite1 (>= 1:0.3-1) | libxdamage1 (>= 1:1.1) | libxext6| libxfixes3 | libxrender1 | libxt6 | zlib1g (>= 1:1.2.11.dfsg) | fontconfig | procps | debianutils (>= 1.16) | Package's Recommends field is empty. Suggests (Version) | Installed ===-+-=== fonts-stix | 1.1.1-4 OR otf-stix| fonts-lmodern | 2.004.5-3 libgssapi-krb5-2| OR libkrb53| libcanberra0| libgtk2.0-0 | --- Output from package bug script --- -- Addons package information -- - Alexander Kernozhitsky
Bug#902534: dgit: needs a better integration story with patches-unapplied maintainer trees
Ian Jackson writes ("Re: Bug#902534: dgit: needs a better integration story
with patches-unapplied maintainer trees"):
> I think maybe the fact that I am writing this all here suggests we
> need better wording in the --overwrite section of dgit(1).
How about this ?
--overwrite[=previous-version]
Declare that your HEAD really does contain all the (wanted)
changes from all versions listed in its changelog; or, all
(wanted) changes from previous-version. This promise is needed
when your git branch is not a descendant of the version in the
archive according to the git revision history.
This option is useful if you are the maintainer, and you have
incorporated NMU changes into your own git workflow in a way
that doesn't make your branch a fast forward from the NMU.
This option is also usually necessary the first time a package
is pushed with dgit push to a particular suite. See dgit-
maint-*(7).
If previous-version is not specified, dgit will check that the
version in the archive is mentioned in your debian/changelog.
(This will avoid losing changes, even with --overwrite, unless
someone committed to git a finalised changelog entry, and then
made later changes to that version.) If previous-version is
specified, it ought to be the version currently in the archive.
[etc]
>From 99b7b3246b32cde43dca421571c06f42e00c1baf Mon Sep 17 00:00:00 2001
From: Ian Jackson
Date: Wed, 27 Jun 2018 18:22:35 +0100
Subject: [PATCH] dgit(1): Better description of --overwrite.
In particular, be clear that --overwrite (without previous-version) is
quite a weak promise: that the version you are uploading contains
everything in your changelog. It won't overwrite willy-nilly.
Somewhat apropos of discussion in #902534.
Signed-off-by: Ian Jackson
---
debian/changelog | 4
dgit.1 | 22 +++---
2 files changed, 19 insertions(+), 7 deletions(-)
diff --git a/debian/changelog b/debian/changelog
index 4d05abe3..ad5e0fe9 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,5 +1,9 @@
dgit (5.4~) unstable; urgency=medium
+ Improvements:
+ * dgit(1): Better description of --overwrite. Somewhat
+apropos of discussion in #902534.
+
Bugfixes:
* Fix bug ref to #865444 in previous changelog entry.
diff --git a/dgit.1 b/dgit.1
index f15fecf9..cbf0cde5 100644
--- a/dgit.1
+++ b/dgit.1
@@ -514,11 +514,15 @@ push will still ensure that the .dsc you upload and the
git tree
you push are identical, so this option won't make broken pushes.)
.TP
.BR --overwrite [=\fIprevious-version\fR]
-Declare that even though your git branch may not be a descendant
+Declare that your HEAD really does contain
+all the (wanted) changes
+from all versions listed in its changelog;
+or, all (wanted) changes from
+.IR previous-version .
+This promise is needed when
+your git branch is not a descendant
of the version in the archive
-according to the revision history,
-it really does contain
-all the (wanted) changes from that version.
+according to the git revision history.
This option is useful if you are the maintainer, and you have
incorporated NMU changes into your own git workflow in a way that
@@ -530,15 +534,19 @@ to a particular suite.
See
.BR dgit-maint- \fI*\fR (7) .
-.I previous-version
-ought to be the version currently in the archive. If
+If
.I previous-version
is not
specified, dgit will check that the version in the archive is
mentioned in your debian/changelog.
(This will avoid losing
-changes unless someone committed to git a finalised changelog
+changes, even with
+.BR --overwrite ,
+unless someone committed to git a finalised changelog
entry, and then made later changes to that version.)
+If
+.IR previous-version
+is specified, it ought to be the version currently in the archive.
dgit push --overwrite
will, if necessary, make a
--
2.11.0
Bug#902548: pngquant FTCBFS: many reasons
Source: pngquant
Version: 2.5.0-2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
pngquant fails to cross build from source. It starts with using the
build architecture compiler. Using dpkg's buildtools.mk fixes that as
./configure recognizes CC. Then the SSE detection checks the build
architecture, but it should check the host architecture. Finally,
./configure hard codes the build architecture pkg-config. The attached
patch fixes all of that and makes pngquant cross buildable. Please
consider applying the attached patch.
Helmut
diff --minimal -Nru pngquant-2.5.0/debian/changelog
pngquant-2.5.0/debian/changelog
--- pngquant-2.5.0/debian/changelog 2017-06-01 10:05:51.0 +0200
+++ pngquant-2.5.0/debian/changelog 2018-06-27 19:20:19.0 +0200
@@ -1,3 +1,13 @@
+pngquant (2.5.0-2.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix FTCBFS: (Closes: #-1)
++ Let SSEFLAG depend on the host architecture, not build architecture.
++ Use buildtools.mk to supply cross tools to ./configure.
++ cross.patch: Don't hard code the build architecture pkg-config.
+
+ -- Helmut Grohne Wed, 27 Jun 2018 19:20:19 +0200
+
pngquant (2.5.0-2) unstable; urgency=medium
* Fix CVE-2016-5735 (Thanks for the patch to Emilio Pozuelo
diff --minimal -Nru pngquant-2.5.0/debian/patches/cross.patch
pngquant-2.5.0/debian/patches/cross.patch
--- pngquant-2.5.0/debian/patches/cross.patch 1970-01-01 01:00:00.0
+0100
+++ pngquant-2.5.0/debian/patches/cross.patch 2018-06-27 19:18:58.0
+0200
@@ -0,0 +1,25 @@
+--- pngquant-2.5.0.orig/configure
pngquant-2.5.0/configure
+@@ -20,6 +20,7 @@
+
+ # make gcc default compiler unless CC is already set
+ CC=${CC:-gcc}
++PKG_CONFIG=${PKG_CONFIG:-pkg-config}
+
+ help() {
+ printf "%4s %s\n" "" "$1"
+@@ -147,10 +148,10 @@
+
+ find_pkgconfig() {
+ LIBNAME=$1
+-if pkg-config --exists "$LIBNAME" &> /dev/null; then
+-cflags "$(pkg-config --cflags "$LIBNAME")"
+-lflags "$(pkg-config --libs "$LIBNAME")"
+-status "$LIBNAME" "shared ($(pkg-config --modversion "$LIBNAME"))"
++if $PKG_CONFIG --exists "$LIBNAME" &> /dev/null; then
++cflags "$($PKG_CONFIG --cflags "$LIBNAME")"
++lflags "$($PKG_CONFIG --libs "$LIBNAME")"
++status "$LIBNAME" "shared ($($PKG_CONFIG --modversion "$LIBNAME"))"
+ return 0
+ fi
+ return 1
diff --minimal -Nru pngquant-2.5.0/debian/patches/series
pngquant-2.5.0/debian/patches/series
--- pngquant-2.5.0/debian/patches/series2017-05-31 22:08:30.0
+0200
+++ pngquant-2.5.0/debian/patches/series2018-06-27 19:18:06.0
+0200
@@ -1 +1,2 @@
CVE-2016-5735.patch
+cross.patch
diff --minimal -Nru pngquant-2.5.0/debian/rules pngquant-2.5.0/debian/rules
--- pngquant-2.5.0/debian/rules 2015-07-27 09:54:49.0 +0200
+++ pngquant-2.5.0/debian/rules 2018-06-27 19:17:36.0 +0200
@@ -1,6 +1,13 @@
#!/usr/bin/make -f
-SSEFLAG=$(shell if grep -q "^flags.*sse" /proc/cpuinfo ; then echo
"--enable-sse" ; else echo "--disable-sse" ; fi)
+include /usr/share/dpkg/architecture.mk
+DPKG_EXPORT_BUILDTOOLS=1
+-include /usr/share/dpkg/buildtools.mk
+ifeq ($(DEB_HOST_ARCH_CPU),amd64)
+SSEFLAG=--enable-sse
+else
+SSEFLAG=--disable-sse
+endif
%:
dh $@
Bug#902547: pulseaudio: Failed to open module sc4m_1916.so: sc4m_1916.so: cannot open shared object file: No such file or directory
Package: swh-plugins Version: 0.4.17-2 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear Maintainer, probably after the recent update of PulseAudio, the sc4m_1916 module can't be loaded anymore for some reason. It was working fine before, now I just get the following log in the terminal: pulseaudio[2698]: Failed to open module sc4m_1916.so: sc4m_1916.so: cannot open shared object file: No such file or directory pulseaudio[2698]: Failed to load LADSPA plugin: file not found pulseaudio[2698]: Failed to load module "module-ladspa-sink" (argument: "sink_name=compressor plugin=sc4m_1916 label=sc4m control=1,1.5,401,-30,20,5,12"): initialization failed. - -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (130, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.16.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages swh-plugins depends on: ii libc6 2.27-3 ii libfftw3-single3 3.3.8-1 ii libgsm1 1.0.13-4+b2 swh-plugins recommends no packages. swh-plugins suggests no packages. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE5JPPWm5C7TFDUMqpzQRoEHcbZSAFAlszxpIACgkQzQRoEHcb ZSAUpxAAwI/wQ35KB2vXo7C/+sRC7IiIVM9AhiyCOW8M3XRZpiev5RLuFmVivqqu RFDEwyYNRwGo8OpRRvGjPw8xKQIOYLiXiRTHgr09SdlZAsrtKv/fO0hS5ni2oOwW Greod+3WolxphzPr3KqYR9lhfwZtpuwsEwv7hIsjYez0hSqgRWKksHLBuIbAOJ/8 LIzeVKSZ8mxkTyxFYgWK9SPcp583RtVk3nYHM5xkdclofTojVWakY2GcaTDDWKgA LXJheIDBYxc1vczZM1MvbBRemlEOyX7LKNFLpyt0F9arPk9rXljeSxPqj31N/L3a wBJXi0tEz++fZJI2VwpAPB24ucg8BohYxIEtNhgz4kG4rpGBlvGTUZB/8vgiPFy8 CQpOpLzipvY0ILjANDWwEv4evrtOo/ITZne6ic8VZBWoD3siZKVE9BIiYAka3Mf/ xph/Js47A8QVItxBfg/p34iFnZfTo/W+9pUliO1N6tZ8tsvF2MqCM/gdkTjA9V8f 8kgl+0sY5KFizWfIAHmwisnN38BQbjO8fTFsEI7dt2gft1IFA9XFjBCfjs9ZP9dh T9n8+JwdUsxHpc4UCEQw/J9I0ePtnFGYeCmYeBMwJNBU1MPaLtnYcszGoahtkGpi fjUpU12QC/UaEUhh75CW4+FkC11Oq32F2wpSBIMaixukixbJjPA= =0uhr -END PGP SIGNATURE-
Bug#902546: amule-daemon: crashes on start: 0.0.0.0 4712 failed - Address already in use
Package: amule-daemon
Version: 1:2.3.2-1+b2
Severity: important
Dear Maintainer,
After running without peoblems for years, A Mule has stopped working:
!2018-06-27 17:37:30: Asio Sockets: CAsioSocketServerImpl bind to 0.0.0.0 4712
failed - Address already in use
2018-06-27 17:37:30: Could not listen for external connections at 0.0.0.0:4712!
!2018-06-27 17:37:30: Error creating UDP socket 0.0.0.0 4665 : Address already
in use
!2018-06-27 17:37:30: MuleUDPSocket: Failed to create valid Server UDP-Socket
!2018-06-27 17:37:30: Asio Sockets: CAsioSocketServerImpl bind to 0.0.0.0 4662
failed - Address already in use
!2018-06-27 17:37:30: ERROR: Could not listen to TCP port.
!2018-06-27 17:37:30: Port 4662 is not available. You will be LOWID
!2018-06-27 17:37:30: ERROR: ERROR Port 4662 is not available!
!2018-06-27 17:37:30: This means that you will be LOWID.
!2018-06-27 17:37:30: Check your network to make sure the port is open for
output and input.
!2018-06-27 17:37:30: Error creating UDP socket 0.0.0.0 4672 : Address already
in use
!2018-06-27 17:37:30: MuleUDPSocket: Failed to create valid Client UDP-Socket
2018-06-27 17:37:30: amuled: forking to background - see you
2018-06-27 17:37:30: Loading server.met file: /home/amule/.aMule/server.met
A fatal error has occurred and aMule has crashed.
But the ports are not in use, according to F User.
-- System Information:
Debian Release: 9.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AX.UTF-8, LC_CTYPE=en_AX.UTF-8 (charmap=locale: Cannot set
LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968), LANGUAGE=en_IE:en (charmap=locale: Cannot set LC_CTYPE to
default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages amule-daemon depends on:
ii amule-common 1:2.3.2-1
ii libboost-system1.62.0 1.62.0+dfsg-4
ii libc6 2.24-11+deb9u3
ii libcrypto++6 5.6.4-7
ii libgcc11:6.3.0-18+deb9u1
ii libpng16-161.6.28-1
ii libreadline7 7.0-3
ii libstdc++6 6.3.0-18+deb9u1
ii libupnp6 1:1.6.19+git20160116-1.2
ii libwxbase3.0-0v5 3.0.2+dfsg-4
ii zlib1g 1:1.2.8.dfsg-5
Versions of packages amule-daemon recommends:
ii amule-utils 1:2.3.2-1+b2
ii unzip6.0-21
amule-daemon suggests no packages.
-- Configuration Files:
/etc/default/amule-daemon changed:
AMULED_USER="amule"
AMULED_HOME="/home/amule"
RUN_AT_STARTUP="YES"
-- debconf information:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_IE:en",
LC_ALL = (unset),
LANG = "en_AX.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
Bug#902545: sagemath: sage 8.2-4 fails to start with error /usr/bin/env: ‘sage-python23’: No such file or directory
Package: sagemath Version: 8.2-4 Severity: grave Justification: renders package unusable Dear Maintainer, -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (800, 'testing'), (750, 'unstable'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'oldstable-updates'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages sagemath depends on: ii cysignals-tools 1.6.7+ds-1 ii cython 0.28.2-4 ii ecl 16.1.2-4+b1 ii eclib-tools 20171002-1+b2 ii f2c 20160102-1 ii fflas-ffpack 2.3.2-1~exp3 ii flintqs 1:1.0-1+b1 ii gap-core 4r8p8-3 ii gfan 0.5+dfsg-6 ii gmp-ecm 7.0.4+ds-2 ii ipython 5.5.0-1 ii iso-codes3.79-1 ii jmol 14.6.4+2016.11.05+dfsg1-3.1 ii lcalc1.23+dfsg-6+b1 ii less 487-0.1+b1 ii libatlas3-base [liblapack.so.3] 3.10.3-7 ii libblas3 [libblas.so.3] 3.8.0-1 ii libbrial-groebner3 1.2.0-2 ii libbrial31.2.0-2 ii libc62.27-3 ii libcdd-tools 094h-1+b1 ii libcliquer1 1.21-2 ii libec3 20171002-1+b2 ii libecm1 7.0.4+ds-2 ii libflint-2.5.2 2.5.2-18 ii libflint-arb22.11.1-2+b1 ii libgap-sage-44.8.8+3+20160327g69a66f0+dsx-1 ii libgcc1 1:8.1.0-8 ii libgd3 2.2.5-4 ii libgivaro9 4.0.4-2 ii libglpk404.65-2 ii libgmp10 2:6.1.2+dfsg-3 ii libgmpxx4ldbl2:6.1.2+dfsg-3 ii libgsl23 2.4+dfsg-6 ii libgslcblas0 2.4+dfsg-6 ii libiml0 1.0.4-1+b2 ii libjs-mathjax2.7.4+dfsg-1 ii libjs-three 80+dfsg2-2 ii liblapack3 [liblapack.so.3] 3.8.0-1 ii liblfunction01.23+dfsg-6+b1 ii liblinbox-1.5.2-01.5.2-1 ii liblinboxsage-1.5.2-01.5.2-1 ii liblrcalc1 1.2-2+b1 ii libm4ri-0.0.20140914 20140914-2+b1 ii libm4rie-0.0.2015090820150908-1 ii libmpc3 1.1.0-1 ii libmpfi0 1.5.3+ds-2 ii libmpfr6 4.0.1-1 ii libntl35 10.5.0-2 ii libpari-gmp-tls5 2.9.5-1 ii libplanarity03.0.0.5-1+b1 ii libpng16-16 1.6.34-1 ii libppl14 1:1.2-3 ii libpynac17 0.7.19-2 ii libratpoints-2.1.3 1:2.1.3-1+b2 ii libreadline7 7.0-5 ii librw0 0.8+ds-1 ii libsingular4 1:4.1.0-p3+ds-2+b3 ii libstdc++6 8.1.0-8 ii libsymmetrica2 2.0+ds-5 ii libzn-poly-0.9 0.9-3+b2 ii maxima-sage 5.39.0+ds-3 ii maxima-sage-doc 5.39.0+ds-3 ii maxima-sage-share5.39.0+ds-3 ii nauty2.6r10+ds-1 ii octave 4.4.0-3 ii palp 2.1-4 ii pari-doc 2.9.5-1 ii pari-galdata 0.20080411-2 ii pari-gp 2.9.5-1 ii pari-seadata 0.20090618-1 ii
Bug#902544: linux-image-4.16.0-2-amd64: Kernel installation fails when /boot is FAT partition
Package: src:linux Version: 4.16.12-1 Severity: important Dear Maintainer, when trying to install linux-image-4.16.0-2-amd64, I get the following error: # LANG=C dpkg -i /var/cache/apt/archives/linux- image-4.16.0-2-amd64_4.16.16-2_amd64.deb (Reading database ... 627533 files and directories currently installed.) Preparing to unpack .../linux-image-4.16.0-2-amd64_4.16.16-2_amd64.deb ... Unpacking linux-image-4.16.0-2-amd64 (4.16.16-2) over (4.16.12-1) ... dpkg: error processing archive /var/cache/apt/archives/linux- image-4.16.0-2-amd64_4.16.16-2_amd64.deb (--install): unable to make backup link of './boot/System.map-4.16.0-2-amd64' before installing new version: Operation not permitted dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/linux-image-4.16.0-2-amd64_4.16.16-2_amd64.deb Reason why it is unable to make the backup link is that my /boot is on EFI partition which is FAT: # mount | grep boot /dev/sda1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount- ro) Older versions showed the same error, but installation succeeded anyway. Please make the error non-fatal again (or use copy instead of link). -- Package-specific info: ** Version: Linux version 4.16.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 7.3.0 (Debian 7.3.0-19)) #1 SMP Debian 4.16.12-1 (2018-05-27) ** Command line: BOOT_IMAGE=/vmlinuz-4.16.0-2-amd64 root=/dev/mapper/delfinek-root ro cryptopts=target=delfinek_crypt,source=/dev/disk/by-partlabel/delfinek_crypt,keys=none,lvm=delfinek-root quiet acpi_backlight=acpi systemd.legacy_systemd_cgroup_controller=yes ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: LENOVO product_name: 20DL0014MC product_version: ThinkPad S1 Yoga 12 chassis_vendor: LENOVO chassis_version: None bios_vendor: LENOVO bios_version: JEET79WW (1.28 ) board_vendor: LENOVO board_name: 20DL0014MC board_version: SDK0E50512 Std ** Loaded modules: cpuid ses enclosure scsi_transport_sas uas usb_storage nf_nat_h323 nf_conntrack_h323 nf_nat_pptp nf_nat_proto_gre nf_conntrack_pptp nf_conntrack_proto_gre nf_nat_tftp nf_conntrack_tftp nf_nat_sip nf_conntrack_sip nf_nat_irc nf_conntrack_irc nf_nat_ftp cdc_acm rpcsec_gss_krb5 nfsv4 dns_resolver mmc_block tun ctr ccm nf_conntrack_netlink nfnetlink xt_addrtype br_netfilter bridge stp llc overlay xfrm_user pci_stub xfrm4_tunnel tunnel4 vboxpci(O) ipcomp xfrm_ipcomp vboxnetadp(O) esp4 vboxnetflt(O) l2tp_ppp l2tp_netlink l2tp_core ip6_udp_tunnel udp_tunnel ah4 pppox ppp_generic slhc vboxdrv(O) af_key xfrm_algo rfcomm cpufreq_userspace cpufreq_powersave cpufreq_conservative cmac bnep ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat xt_DSCP ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_limit nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack iptable_filter iptable_mangle nf_conntrack_ftp nf_conntrack crc32c_generic binfmt_misc nls_ascii nls_cp437 vfat fat btusb btrtl btbcm btintel uvcvideo videobuf2_vmalloc videobuf2_memops bluetooth videobuf2_v4l2 videobuf2_common videodev drbg ansi_cprng media ecdh_generic crc16 hid_multitouch arc4 wmi_bmof iTCO_wdt iTCO_vendor_support intel_rapl x86_pkg_temp_thermal intel_powerclamp iwlmvm kvm_intel mac80211 iwlwifi kvm irqbypass intel_cstate intel_uncore efi_pstore intel_rapl_perf joydev snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generic efivars serio_raw snd_hda_intel sg rtsx_pci_ms cfg80211 snd_hda_codec memstick snd_hda_core thinkpad_acpi tpm_tis tpm_tis_core nvram intel_pch_thermal tpm wmi intel_vbtn rfkill battery sparse_keymap rng_core snd_hwdep ac snd_pcm_oss soc_button_array snd_mixer_oss mei_me snd_pcm evdev snd_timer mei acpi_pad snd soundcore lpc_ich shpchp coretemp nfsd nfs_acl auth_rpcgss nfs lockd grace fscache sunrpc fuse loop efivarfs ip_tables x_tables autofs4 btrfs zstd_decompress zstd_compress xxhash algif_skcipher af_alg dm_crypt dm_mod raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear md_mod sd_mod wacom hid_generic usbhid hid crct10dif_pclmul crc32_pclmul crc32c_intel rtsx_pci_sdmmc ghash_clmulni_intel pcbc mmc_core aesni_intel i915 ahci libahci xhci_pci aes_x86_64 crypto_simd glue_helper xhci_hcd i2c_algo_bit cryptd libata usbcore drm_kms_helper usb_common psmouse i2c_i801 scsi_mod rtsx_pci drm video button ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Broadwell-U Host Bridge -OPI [8086:1604] (rev 09) Subsystem: Lenovo Broadwell-U Host Bridge -OPI [17aa:503e] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: bdw_uncore 00:02.0 VGA compatible
Bug#901544: Make libwx-perl build reproducible
On Donnerstag, 14. Juni 2018 22:19:45 CEST you wrote: > On Thu, 14 Jun 2018 15:34:24 +, =?UTF-8?Q?Br=C3=BCns wrote: > > libwx-perl build is still not reproducible. > > […] > > > The openSUSE version builds reproducibly for over a year. Please pick up > > the patches from: > > https://build.opensuse.org/package/show/devel:languages:perl/perl-Wx > > Thanks for the pointer. > > Unfortunately I have to admit that I'm a bit confused; my first > question is which patches exactly? I first tried with (removing our > repoducible.patch and) applying > 0001-Sort-output-of-dumped-dictionaries-for-reproducible-.patch and > 0002-Provide-overload-methods-to-XSpp-in-sorted-order.patch. > reprotest was not happy. Then I also added > 0001-fix-incomplete-Wx_Exp.pm-due-to-missing-dependecy-in.patch, but > diffoscope at the end of reprotest was still complaining. > > So maybe I picked the wrong patches or reprotest (or my reprotest > setup) has a problem or our other patches cause issues or something > else -- but I can't get a reproducible package locally. You need *all* patches but the ABI patch. In the meantime, 2 more patches were added, as there where spurious reorderings. For reproducible debug *source* packages, you also need a patched XSpp, as otherwise the generated sources include random IDs (these never end up in the binaries, the IDs are only used for #ifdefs used/removed by the C++ preprocessor). Regards, Stefan signature.asc Description: Digital Signature
Bug#902536: [Aptitude-devel] Bug#902536: Document how to detect 'newer than in the archive' installed packages
Hmmm, looks complex. Sure hope you also mention "or just use apt-show-versions ...".
Bug#902536: [Aptitude-devel] Bug#902536: Document how to detect 'newer than in the archive' installed packages
Hi Jidanni, 積丹尼 Dan Jacobson wrote: > > "AB" == Axel Beckert writes: > AB> aptitude-newer-than-in-archive: aliased to aptitude -o > "Aptitude::Pkg-Display-Limit=~i ?any-version(!~O.) !~U !~o" > All I know is > # aptitude -o Aptitude::Pkg-Display-Limit=~i search '?any-version(!~O.) !~U > !~o'|head You ignored the double quotes. Try it like this: ~ → aptitude search '~i ?any-version(!~O.) !~U !~o' i A links - Web browser running in text mode i links-dbgsym - debug symbols for links i A links2 - Web browser running in both graphics and text mode i links2-dbgsym - debug symbols for links2 i A screen - terminal multiplexer with VT100/ANSI terminal emulation i screen-dbgsym - debug symbols for screen i zsh- shell with lots of features i A zsh-common - architecture independent files for Zsh i zsh-dbgsym - debug symbols for zsh i zsh-dev- shell with lots of features (development files) i A zsh-doc- zsh documentation - info/HTML format i zsh-static - shell with lots of features (static link) i zsh-static-dbgsym - debug symbols for zsh-static Might still have some false positives, compared to apt-show-versions: ~ → apt-show-versions | fgrep newer links:amd64 2.15-1 newer than version in archive links-dbgsym:amd64 2.15-1 newer than version in archive links2:amd64 2.15-1 newer than version in archive links2-dbgsym:amd64 2.15-1 newer than version in archive ~ → apt-cache policy screen zsh screen: Installed: 4.6.2-1+b1 Candidate: 4.6.2-1+b1 Version table: 4.6.2-2~20180402224407.147 500 500 https://jenkins.grml.org/debian screen/main amd64 Packages 4.6.2-1+b1wtf1 250 250 https://www.mirbsd.org/~tg/Debs sid/wtf amd64 Packages *** 4.6.2-1+b1 990 990 https://debian.ethz.ch/debian sid/main amd64 Packages 600 https://debian.ethz.ch/debian testing/main amd64 Packages 100 /var/lib/dpkg/status zsh: Installed: 5.5.1-1+b1 Candidate: 5.5.1-1+b1 Version table: *** 5.5.1-1+b1 990 990 https://debian.ethz.ch/debian sid/main amd64 Packages 600 https://debian.ethz.ch/debian testing/main amd64 Packages 100 /var/lib/dpkg/status 5.5.1-1+0~20180417015621.399~1.gbp0bb292 500 500 https://jenkins.grml.org/debian zsh/main amd64 Packages Will probably have to update and finetune these patterns. > P.S., I hope your scripts will have non GUI versions too. So far not, but you are currently changing that. :-) Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#869146: dgit: should never add .orig to the .changes more than once
Sean Whitton writes ("Bug#869146: dgit: should never add .orig to the .changes
more than once"):
> On Tue, Jun 26 2018, Ian Jackson wrote:
> > Of course if you had followed dgit's advice you would not have
> > experienced this but :-)
>
> I must have been sure that dgit was wrong to tell me to do that in this
> case. Next time it comes up for me, I'll file a bug saying exactly why
> I think the advice was wrong. Thanks for the fix!
In this particular situation, what happened was that "git push"
failed. dgit cannot easily know whether that was because the remote
rejected the push (in which case reusing the version number for new
tags etc. is fine), or because of a network communication error (in
which case the remote may well have stored some of the data).
You can read the error message and know it's the former, so you were
right, except of course for the fact that you managed to find a
dgit bug :-). The bug would show up in other situations too.
It might be possible to do better with this by, oh, I don't know,
parsing the error messages, or something. Or by filing a bug against
git to request the ability for a remote receive hook to communicate
this kind of thing to the client. I decided that version numbers are
cheap enough that this isn't worth the effort.
HTH :-).
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Bug#869146: dgit: should never add .orig to the .changes more than once
Hello, On Tue, Jun 26 2018, Ian Jackson wrote: > Of course if you had followed dgit's advice you would not have > experienced this but :-) I must have been sure that dgit was wrong to tell me to do that in this case. Next time it comes up for me, I'll file a bug saying exactly why I think the advice was wrong. Thanks for the fix! -- Sean Whitton signature.asc Description: PGP signature
Bug#902534: dgit: needs a better integration story with patches-unapplied maintainer trees
Felipe Sateler writes ("Re: Bug#902534: dgit: needs a better integration story
with patches-unapplied maintainer trees"):
> Gah, I knew there was already a bug about this. And I have even
> participated on it! Sorry for the duplicate.
No problem. I'm dropping 842614 again because we're focusing here in
902534 very much on gbp. That's probably a useful narrowing and thus
a useful distinction between the two bugs.
> But dgit could create such ancestry, couldn't it? If dgit somehow knew the
> package incorporated the pulled changes, it could create the synthetic merge
> commit with the dgit view.
>
> Currently for gbp-maintained packages history looks like this:
>
> U1U2U3
> \ \ \
> A1A2A3
>
> Where U[N] are the gbp debian/N tags, and A[N] are the dgit archive/[N] tags.
> What I'm thinking is that dgit would do:
>
> U1-U2---U3
> \ \ \
> A1---A2--F---A3
>
> Where F would be a fake merge synthesized by dgit. I have
> deliberately left out the path from A2 to U2. It might be done via
> gbp import-orig, manual patch application, or whatever. It might be
> even that I forgot to use dgit in the last upload!
How does dgit (or anything else) know that U2 contains all the changes
in A2 ? If it constructs it itself it can know that, but otherwise
someone is going to have to tell it.
> Perhaps this is a possible middle ground: If I could tell dgit "my
> branch includes all changes in A2",
In non-split-brain mode you can do this:
git merge -s ours dgit/dgit/sid
That is you declaring that although your branch is not a descendant of
the archive, it contains all the changes in it (or, at least, all the
ones you want to keep) and that therefore it should be considered fast
forward.
That is, of course, equivalent to passing --overwrite to dgit push.
But you can do it in advance, and if you do, you won't need
--overwrite later.
The difficulty with doing this in split brain mode is that A2 does not
have a corresponding U2 known to dgit. So there is no parent you can
overwrite in advance with git merge -s ours.
If A2 is a dgit dsc import then there is a thing a bit like U2 inside
the dgit dsc import commit structure. But that sort-of-U2 doesn't
have the right ancestry. In the general case it can't do because
dgit's dsc import code cannot rely on U1 even existing, let alone
somehow being able to find it by digging into the git history.
But A2 might even be a fast-forward upload done by a dgit-using NMUer.
In that case there might be nowhere at all any commit whose tree would
correspond to the putative U2. That is likely if the NMUer made a new
patch.
I don't know what exactly happens if you say
git merge -s ours dgit/dgit/sid
if you are on a patches-unapplied branch. I'm pretty sure it will get
rid of the need to use --overwrite on the next push.
One option might be to provide a "preemptive overwrite" command to
dgit, which would do an appropriate git merge. In non split brain
modes
dgit overwrite 2
would be the same as some suitable git merge -s ours, but it would
do the same kind of checks as dgit push --overwrite=2. Then the
next dgit push wouldn't need --overwrite.
In split brain mode it would probably make a pseudomerge overwriting
the patches-unapplied dgit dsc import, if it can find one. I have no
idea what it would do if there was no such dsc import. Maybe it could
invent a root commit with a special note in it, which dgit push would
later recognise ?
But maybe the actual answer is just "you tell dgit this by putting it
in your changelog".
> perhaps dgit could generate the
> history above and then --overwrite would not be needed? Similar to
> the --force-with-lease option to `git push`, it would allow
> overriding, but only if the remote matches what we expect.
dgit push --overwrite already works like --force-with-lease. By
default it will only overwrite an archive version which is mentioned
in your d/changelog. So if someone else uploads, you aren't racing
with them: your dgit push --overwrite will spot the problem and bail.
I think this is explained under --overwrite in dgit(1).
--overwrite is still necessary because it is not possible for dgit to
tell whether the branch are on, which has a stanza for "2" in the
changelog, is actually based on the final version of "2" as it was
uploaded.
This is because a stanza for "2" might easily exist in a branch which
was about to be released - except that a last-minute bug was
discovered, and fixed. If your branch is derived from that earlier
unreleased version, it would look (if you just looked at the
changelog) to be an update which contained everything in "2". But if
you uploaded it you would undo the last-minute bugfix.
I think maybe the fact that I am writing this all here suggests we
need better wording in the --overwrite section of dgit(1).
> At least, dgit does not make this problem any harder. Having to pass
> --overwrite may *seem* like "making it harder" but what
Bug#901807: libmath-gsl-perl: incompatible with GSL >= 2.5
On Tue, 26 Jun 2018 10:25:06 +0300, Niko Tyni wrote:
> On Sun, Jun 24, 2018 at 04:02:06PM +0200, gregor herrmann wrote:
> > -my $ver2func = do(catfile(qw/inc ver2func/));
> > +my $ver2func = do('./' . catfile(qw/inc ver2func/));
> Yeah, that's better than -I. (hardcoding '/' as the directory separator is
> a bit ugly but works for us, and I see catfile is rather eager to remove
> './' if it sees it.)
Right, I also started by adding '.' to catfile() :)
> > sub is_release {
> > -return -e '.git' ? 0 : 1;
> > +return 0;
> > }
> I think I was testing all the time with inside a git checkout,
> that probably explains it. Happy if that's enough to trigger
> the rebuild. Not sure if it still looks at file mtime stamps
> and would need an explicit clean first?
Hm, good question.
They do get recreated for me in my cowbuilder chroot without any
further intervention; and when I build twice-in-a-row, a clean
happens anyway.
But in theory ... maybe ... Ok, after looking at inc/GSLBuilder.pm a
bit: It uses Module::Build's
up_to_date($source_file, $derived_file)
up_to_date(\@source_files, \@derived_files)
to check swig/FOO.i and pod/FOO.pod against the derived
xs/FOO_wrap.VERSION.c which happens to end well for us; but maybe
only because our spelling patch touches about all pod files :)
Maybe it would be safer to make sure that up_to_date() always returns
false ...
When I `touch xs/*' before dh_auto_build, indeed re-swig-ification is
skipped for all files; so on the other hand, touching swig/* should
make sure that it happens. -- Does this make sense? Committed in git
and pushed.
> > > The latter one may not turn out to be
> > > necessary if the deprecated functions get reinstated with #902281.
> > Ack.
> It looks like the deprecated symbols will be reinstated for now.
> Not sure if we still want to disable them on our side. Probably not.
I'm a bit confused here; the current upload of gsl activates the
patch which reinstates them but the maintainer sounded like he'd
prefer to disable the patch again? If I understood this correctly we
should probably keep our patch, right?
And I guess at least if we keep "our" patch, we don't need a
versioned build dependency?
> In any case, I think we should still do a swig rebuild every
> time as part of the normal package build.
Ack.
> > I've pushed your and my patches, but I'd rather have another
> > doublecheck before uploading.
> Looks good to me, thanks!
Thanks for checking!
Cheers,
gregor
--
.''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org
: :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06
`. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
`- NP: Beatles: While My Guitar Gently Weeps
signature.asc
Description: Digital Signature
Bug#902543: wine: please add StartupWMClass=foo.exe to the .desktop files
Package: wine Severity: normal Dear Maintainer, For wine applications please add StartupWMClass=foo.exe to the .desktop files it generates. See upstream bug https://bugs.winehq.org/show_bug.cgi?id=45245 for details. Thank you! -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.13.0-39-generic (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages wine depends on: pn wine64 | wine32 wine recommends no packages. Versions of packages wine suggests: pn dosbox pn playonlinux pn winbind pn wine-binfmt pn winetricks
Bug#902542: photutils: autopkgtest failure with skimage 0.14.0
Source: photutils
Version: 0.4-4
User: debian...@lists.debian.org
Usertags: needs-update
Hi Maintainer
Since the upload of skimage 0.14.0-1 to unstable, photutils has been
failing its autopkgtests [1] with several errors similar to the
following:
_ test_centroids[25.7-26.2-3.2-5.7-0.5235987755982988] _
xc_ref = 25.7, yc_ref = 26.2, x_stddev = 3.2, y_stddev = 5.7
theta = 0.5235987755982988
@pytest.mark.parametrize(
('xc_ref', 'yc_ref', 'x_stddev', 'y_stddev', 'theta'),
list(itertools.product(XCS, YCS, XSTDDEVS, YSTDDEVS, THETAS)))
@pytest.mark.skipif('not HAS_SKIMAGE')
def test_centroids(xc_ref, yc_ref, x_stddev, y_stddev, theta):
model = Gaussian2D(2.4, xc_ref, yc_ref, x_stddev=x_stddev,
y_stddev=y_stddev, theta=theta)
y, x = np.mgrid[0:50, 0:47]
data = model(x, y)
xc, yc = centroid_com(data)
> assert_allclose([xc_ref, yc_ref], [xc, yc], rtol=0, atol=1.e-3)
E AssertionError:
E Not equal to tolerance rtol=0, atol=0.001
E
E (mismatch 100.0%)
Ex: array([25.7, 26.2])
Ey: array([26.19992 , 25.700027])
Regards
Graham
[1] https://ci.debian.net/packages/p/photutils/unstable/amd64/
