Processed: reassign 977262 to nvidia-legacy-340xx-driver, forcibly merging 976056 977262

[Debian Bug Tracking System]

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

> reassign 977262 nvidia-legacy-340xx-driver
Bug #977262 [src:linux] linux-image-5.9.0-4-amd64: nvidia-kernel cannot be 
built any more
Bug reassigned from package 'src:linux' to 'nvidia-legacy-340xx-driver'.
No longer marked as found in versions linux/5.9.9-1.
Ignoring request to alter fixed versions of bug #977262 to the same values 
previously set
> forcemerge 976056 977262
Bug #976056 {Done: Andreas Beckmann } 
[nvidia-legacy-340xx-driver] nvidia-legacy-340xx-driver: requires DRM_LEGACY, 
disabled from Linux 5.9.11 onwards
Bug #976056 {Done: Andreas Beckmann } 
[nvidia-legacy-340xx-driver] nvidia-legacy-340xx-driver: requires DRM_LEGACY, 
disabled from Linux 5.9.11 onwards
Added tag(s) moreinfo.
Bug #977262 [nvidia-legacy-340xx-driver] linux-image-5.9.0-4-amd64: 
nvidia-kernel cannot be built any more
Severity set to 'serious' from 'important'
Marked Bug as done
Added indication that 977262 affects linux-image-5.9.0-4-amd64
Marked as fixed in versions nvidia-graphics-drivers-legacy-340xx/340.108-9.
Marked as found in versions nvidia-graphics-drivers-legacy-340xx/340.108-8.
Merged 976056 977262
> thanks
Stopping processing here.

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

Bug#971713: sysstat: init or systemd file has overlapping runlevels

[Lorenzo]

On Sun, 13 Dec 2020 19:44:01 +0100
Trek  wrote:

> 
> on new installations, simply adding the correct levels (0 1 6) to the
> script should fix the bug, but to fix on upgrades you should remove
> those links before running insserv, that is adding something like that
> to postinst inside the configure step:
> 
>   # new Default-Stop (see #971713)
>   if dpkg --compare-versions "$2" le '12.4.0-2'; then
>  update-rc.d -f sysstat remove
>   fi
> 
> this will also remove any tweaking done by user, that should be
> annotated inside the NEWS.Debian file
> 
> I would like to provide you a patch, but I can't find where the init.d
> file is enabled inside the sysstat postinst, that should be:
> 
>   update-rc.d sysstat defaults
> 
> ciao!
> 

Hi,

if you are searching in the source under /debian directory, the code
that you are looking for will be written by dh-installinit in place of
the #DEBHEPLER# placeholder, during the build of the package.
To find out what the postinst will look like just compare the one in the
source with the one in the deb package in the archive.

Lorenzo

Bug#977231: marked as done (libusb-1.0-0: upgrading to 2:1.0.24-1 breaks iPhone/iPad detection and communication)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2020 06:18:25 +
with message-id 
and subject line Bug#977231: fixed in libusb-1.0 2:1.0.24-2
has caused the Debian Bug report #977231,
regarding libusb-1.0-0: upgrading to 2:1.0.24-1 breaks iPhone/iPad detection 
and communication
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
977231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977231
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libusb-1.0-0
Version: 2:1.0.24-1
Severity: important

Hi,
it seems that the recently uploaded to sid libusb version 2:1.0.24-1
breaks something when communicating with an Apple iPhone or iPad (both
running iOS 14).

The devices appear in /sys/kernel/debug/usb/devices but lsusb doesn't
see them, and the daemon use to communicate with them (usbmuxd) doesn't
see it either.

Other devices (one usb key, a Yubikey and an Android phone) seem to be
detected correctly, so maybe there's something complicated done by the
iDevices, but they work just fine when downgrading to 2:1.0.22-2.

If you need more information don't hesitate to ask (I guess you don't
have an iDevice to plug for testing).

Regards,
-- 
Yves-Alexis

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

Kernel: Linux 5.9.0-4-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libusb-1.0-0 depends on:
ii  libc6 2.31-5
ii  libudev1  247.1-4

libusb-1.0-0 recommends no packages.

libusb-1.0-0 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libusb-1.0
Source-Version: 2:1.0.24-2
Done: Aurelien Jarno 

We believe that the bug you reported is fixed in the latest version of
libusb-1.0, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 977...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated libusb-1.0 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 14 Dec 2020 06:54:15 +0100
Source: libusb-1.0
Architecture: source
Version: 2:1.0.24-2
Distribution: unstable
Urgency: medium
Maintainer: Aurelien Jarno 
Changed-By: Aurelien Jarno 
Closes: 977231
Changes:
 libusb-1.0 (2:1.0.24-2) unstable; urgency=medium
 .
   * Backport patch from upstream to fix parsing of descriptors for
 multi-configuration devices (closes: #977231).
Checksums-Sha1:
 af9ff8dd226deab00b248c23d7a1524985e31387 2144 libusb-1.0_1.0.24-2.dsc
 0a3b0bc47a52799c44081d2bd74cd589d1d543c2 12304 
libusb-1.0_1.0.24-2.debian.tar.xz
 ae8e436caa3eb3cf9abba665c45fd39ffe68edf0 5582 
libusb-1.0_1.0.24-2_source.buildinfo
Checksums-Sha256:
 2b93eb063eb46c238cd9fd229dbf2f6c516ef0f924be0e6f96207ad46ca52c3e 2144 
libusb-1.0_1.0.24-2.dsc
 1247fa74202a626180181fe51d93b0e52fe09ae79867adf64a11753ab9638076 12304 
libusb-1.0_1.0.24-2.debian.tar.xz
 0109b16c1b8f3ca5ddb4b5bf8ae7e2c5a01d95e67c5432c8846c95b8936dc95c 5582 
libusb-1.0_1.0.24-2_source.buildinfo
Files:
 02420c198bc6c49f2de1856b1e6d5b31 2144 libs optional libusb-1.0_1.0.24-2.dsc
 9c05a1fe4cc496d5c4163ef0ee7e5c02 12304 libs optional 
libusb-1.0_1.0.24-2.debian.tar.xz
 a2475df96e777866ccd9aa7f1a608537 5582 libs optional 
libusb-1.0_1.0.24-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAl/W/mEACgkQE4jA+Jno
M2uBfA/+N+GwT8644R8jJxd60GCZW26fI9NF6EUDCSt3QCl/4r5hf7g0/lZwTCsF
bu9p/dIaypzozg8ZSteRMt71BbPmGTQJ3HTzqothLYSl6rIgll+1FCv3lB0c7VyF
lhzpI/5aIOUSs+y+cYxUFSSdR0KDHzSgxFNaHzz0wdgdUIMWbPN9wGWRMb3lSBuU
WuZ+Uz16Rew0x6Fe3tnVBf3tmeBCZCHEmimquSvrrkAb8ghRMyyqo9H3JG2wWl5s
mYbThmETSzZcVLLPx+uopcRWu+q2jLz84OQiE41QJLbnPk0GGnf8JVObO1ZBwjnf
15YNsTWg+DXOljS3qXo0c/0itXiVgtivI2OZMuH5tOQwAxH3WUnKXkmhd94Wlxar
WVdE0rE8KSrwaIbubzFcJUwEDl1SlVw4eiVnuKrq7Cu+kpGiF6XCI6nVPegu4WhH

Bug#936391: marked as done (dhcpy6d: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2020 06:06:30 +
with message-id 
and subject line Bug#936391: fixed in dhcpy6d 1.0.2-1
has caused the Debian Bug report #936391,
regarding dhcpy6d: Python2 removal in sid/bullseye
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
936391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936391
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dhcpy6d
Version: 0.4.3-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:dhcpy6d

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.


--- End Message ---
--- Begin Message ---
Source: dhcpy6d
Source-Version: 1.0.2-1
Done: Axel Beckert 

We believe that the bug you reported is fixed in the latest version of
dhcpy6d, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 936...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Axel Beckert  (supplier of updated dhcpy6d package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 14 Dec 2020 06:25:15 +0100
Source: dhcpy6d
Architecture: source
Version: 1.0.2-1
Distribution: unstable
Urgency: low
Maintainer: Axel Beckert 
Changed-By: Axel Beckert 
Closes: 936391
Changes:
 dhcpy6d (1.0.2-1) unstable; urgency=low
 .
   * Prepare separating Debian packaging from upstream repo:
 + Update Vcs-* headers to point to Salsa.
 + Add debian/upstream/metadata file.
 + Generate pure Debian git history via "gbp import-dscs --debsnap",
   merge it with upstream's git history up to "debian/0.4.3-1".
 + Add a debian/gbp.conf.
   * Import upstream release 1.0.2 and parts of upstream's Python 3 based
 packaging. (Closes: #936391)
 + Upstream moved init.d script as well as systemd service file under
   debian/. The latter differs for /etc/default/dhcpy6d integration.
 + Minor wording fixes in the 0.4.2-1 changelog entry.
 + Switch packaging to Python 3 (only).
 + Bump debhelper build-dependency 

Bug#943021: marked as done (dhcpy6d: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2020 06:06:30 +
with message-id 
and subject line Bug#936391: fixed in dhcpy6d 1.0.2-1
has caused the Debian Bug report #936391,
regarding dhcpy6d: Python2 removal in sid/bullseye
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
936391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936391
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dhcpy6d
Version: 0.4.3-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ).
Please stop using Python2, and fix this issue by one of the following
actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: dhcpy6d
Source-Version: 1.0.2-1
Done: Axel Beckert 

We believe that the bug you reported is fixed in the latest version of
dhcpy6d, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 936...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Axel Beckert  (supplier of updated dhcpy6d package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 14 Dec 2020 06:25:15 +0100
Source: dhcpy6d
Architecture: source
Version: 1.0.2-1
Distribution: unstable
Urgency: low
Maintainer: Axel Beckert 
Changed-By: Axel Beckert 
Closes: 936391
Changes:
 dhcpy6d (1.0.2-1) unstable; urgency=low
 .
   * Prepare separating Debian packaging from upstream repo:
 + Update Vcs-* headers to point to Salsa.
 + Add debian/upstream/metadata file.
 + Generate pure Debian git history via "gbp import-dscs --debsnap",
   merge it with upstream's git history up to "debian/0.4.3-1".
 + Add a debian/gbp.conf.
   * Import upstream release 1.0.2 and parts of upstream's Python 3 based
 packaging. (Closes: #936391)
 + Upstream moved init.d script as well as systemd service file under
   debian/. The latter differs for /etc/default/dhcpy6d integration.
 + Minor wording fixes in the 0.4.2-1 changelog entry.
 + Switch packaging to Python 3 (only).
 + Bump debhelper build-dependency (but not compat) to 12.1.1.
 + Depend on lsb-base.
 + Move python*-dnspython from Suggests to Depends.
   * Fix upstream packaging as needed:
 + Drop 

Bug#976543: marked as done (golang-github-rcrowley-go-metrics: FTBFS on arm64,ppc64el (arch:all-only src pkg): dh_auto_test: error: cd obj-aarch64-linux-gnu && go test -vet=off -v -p 4 github.com/rcro

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2020 03:48:40 +
with message-id 
and subject line Bug#976543: fixed in golang-github-rcrowley-go-metrics 
0.0~git20180125.8732c61-3
has caused the Debian Bug report #976543,
regarding golang-github-rcrowley-go-metrics: FTBFS on arm64,ppc64el 
(arch:all-only src pkg): dh_auto_test: error: cd obj-aarch64-linux-gnu && go 
test -vet=off -v -p 4 github.com/rcrowley/go-metrics 
github.com/rcrowley/go-metrics/exp github.com/rcrowley/go-metrics/librato 
github.com/rcrowley/go-metrics/stathat returned exit code 1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
976543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976543
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-rcrowley-go-metrics
Version: 0.0~git20180125.8732c61-2
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_autoreconf -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   cd obj-aarch64-linux-gnu && go install -trimpath -v -p 4 
> github.com/rcrowley/go-metrics github.com/rcrowley/go-metrics/exp 
> github.com/rcrowley/go-metrics/librato github.com/rcrowley/go-metrics/stathat
> runtime/internal/sys
> internal/cpu
> runtime/internal/atomic
> internal/unsafeheader
> runtime/internal/math
> internal/race
> sync/atomic
> internal/bytealg
> unicode
> unicode/utf8
> encoding
> math/bits
> internal/testlog
> math
> unicode/utf16
> internal/nettrace
> runtime/cgo
> runtime
> container/list
> crypto/internal/subtle
> crypto/subtle
> vendor/golang.org/x/crypto/cryptobyte/asn1
> vendor/golang.org/x/crypto/internal/subtle
> internal/reflectlite
> sync
> internal/singleflight
> math/rand
> errors
> sort
> io
> strconv
> internal/oserror
> syscall
> vendor/golang.org/x/net/dns/dnsmessage
> bytes
> strings
> reflect
> hash
> hash/crc32
> bufio
> internal/syscall/unix
> time
> internal/syscall/execenv
> text/tabwriter
> crypto
> crypto/internal/randutil
> crypto/hmac
> crypto/rc4
> vendor/golang.org/x/crypto/hkdf
> vendor/golang.org/x/text/transform
> path
> regexp/syntax
> encoding/binary
> internal/fmtsort
> internal/poll
> context
> encoding/base64
> crypto/cipher
> crypto/sha512
> os
> crypto/ed25519/internal/edwards25519
> crypto/md5
> crypto/aes
> crypto/des
> crypto/sha1
> crypto/sha256
> encoding/pem
> fmt
> runtime/debug
> net
> path/filepath
> vendor/golang.org/x/crypto/chacha20
> io/ioutil
> vendor/golang.org/x/crypto/poly1305
> encoding/json
> log
> compress/flate
> math/big
> compress/gzip
> runtime/pprof
> encoding/hex
> net/url
> vendor/golang.org/x/crypto/chacha20poly1305
> vendor/golang.org/x/crypto/curve25519
> vendor/golang.org/x/text/unicode/bidi
> crypto/rand
> crypto/elliptic
> encoding/asn1
> crypto/ed25519
> crypto/rsa
> crypto/dsa
> vendor/golang.org/x/crypto/cryptobyte
> crypto/x509/pkix
> vendor/golang.org/x/text/secure/bidirule
> vendor/golang.org/x/text/unicode/norm
> vendor/golang.org/x/net/http2/hpack
> crypto/ecdsa
> mime
> mime/quotedprintable
> net/http/internal
> vendor/golang.org/x/net/idna
> regexp
> log/syslog
> vendor/golang.org/x/net/http/httpproxy
> net/textproto
> crypto/x509
> github.com/rcrowley/go-metrics
> vendor/golang.org/x/net/http/httpguts
> mime/multipart
> crypto/tls
> net/http/httptrace
> net/http
> expvar
> github.com/stathat/go
> github.com/rcrowley/go-metrics/librato
> github.com/rcrowley/go-metrics/exp
> github.com/rcrowley/go-metrics/stathat
>dh_auto_test -O--buildsystem=golang
>   cd obj-aarch64-linux-gnu && go test -vet=off -v -p 4 
> github.com/rcrowley/go-metrics github.com/rcrowley/go-metrics/exp 
> github.com/rcrowley/go-metrics/librato github.com/rcrowley/go-metrics/stathat
> === RUN   TestCounterClear
> --- PASS: TestCounterClear (0.00s)
> === RUN   TestCounterDec1
> --- PASS: TestCounterDec1 (0.00s)
> === RUN   TestCounterDec2
> --- PASS: TestCounterDec2 (0.00s)
> === RUN   TestCounterInc1
> --- PASS: TestCounterInc1 (0.00s)
> === RUN   TestCounterInc2
> --- PASS: TestCounterInc2 (0.00s)
> === RUN   TestCounterSnapshot
> --- PASS: TestCounterSnapshot (0.00s)
> === RUN   TestCounterZero
> --- PASS: TestCounterZero (0.00s)
> === RUN   TestGetOrRegisterCounter
> --- PASS: TestGetOrRegisterCounter (0.00s)
> === 

Bug#976543: marked as pending in golang-github-rcrowley-go-metrics

[Reinhard Tartler]

Control: tag -1 pending

Hello,

Bug #976543 in golang-github-rcrowley-go-metrics reported by you has been fixed 
in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/go-team/packages/golang-github-rcrowley-go-metrics/-/commit/22d89f6515f7fabdae307ba8911756552dee13cc


Fix test on !amd64, Closes: #976543


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/976543

Processed: Bug#976543 marked as pending in golang-github-rcrowley-go-metrics

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #976543 [src:golang-github-rcrowley-go-metrics] 
golang-github-rcrowley-go-metrics: FTBFS on arm64,ppc64el (arch:all-only src 
pkg): dh_auto_test: error: cd obj-aarch64-linux-gnu && go test -vet=off -v -p 4 
github.com/rcrowley/go-metrics github.com/rcrowley/go-metrics/exp 
github.com/rcrowley/go-metrics/librato github.com/rcrowley/go-metrics/stathat 
returned exit code 1
Added tag(s) pending.

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

Processed: bug 976543 is forwarded to https://github.com/rcrowley/go-metrics/issues/249

[Debian Bug Tracking System]

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

> forwarded 976543 https://github.com/rcrowley/go-metrics/issues/249
Bug #976543 [src:golang-github-rcrowley-go-metrics] 
golang-github-rcrowley-go-metrics: FTBFS on arm64,ppc64el (arch:all-only src 
pkg): dh_auto_test: error: cd obj-aarch64-linux-gnu && go test -vet=off -v -p 4 
github.com/rcrowley/go-metrics github.com/rcrowley/go-metrics/exp 
github.com/rcrowley/go-metrics/librato github.com/rcrowley/go-metrics/stathat 
returned exit code 1
Set Bug forwarded-to-address to 
'https://github.com/rcrowley/go-metrics/issues/249'.
> thanks
Stopping processing here.

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

Processed: Re: Bug#976509: golang-github-shirou-gopsutil: FTBFS: dh_auto_test: error: cd obj-aarch64-linux-gnu && go test -vet=off -v -p 4 github.com/shirou/gopsutil github.com/shirou/gopsutil/cpu git

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/shirou/gopsutil/issues/881
Bug #976509 [src:golang-github-shirou-gopsutil] golang-github-shirou-gopsutil: 
FTBFS: dh_auto_test: error: cd obj-aarch64-linux-gnu && go test -vet=off -v -p 
4 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
Set Bug forwarded-to-address to 'https://github.com/shirou/gopsutil/issues/881'.

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

Bug#976509: golang-github-shirou-gopsutil: FTBFS: dh_auto_test: error: cd obj-aarch64-linux-gnu && go test -vet=off -v -p 4 github.com/shirou/gopsutil github.com/shirou/gopsutil/cpu github.com/shirou/

[Reinhard Tartler]

Control: forwarded -1 https://github.com/shirou/gopsutil/issues/881

I'm having a hard time seeing bugs like this as RC-critical. Looking at
the testsuite more specifically, I strongly believe this is upstream bug
https://github.com/shirou/gopsutil/issues/881

Lucas, can you please post /proc/cpuinfo from the amd64 machine you
tested on so that we confirm that it doesn't report a modelname?

I'd concur with Andreas to disable running tests on !amd64, maybe with
something like this patch:

modified   debian/rules
@@ -10,3 +10,9 @@ export CIRCLECI := true
 
 %:
dh $@ --buildsystem=golang --with=golang
+
+
+override_dh_auto_test:
+ifneq (,$(filter $(DEB_HOST_ARCH), amd64))
+   dh_auto_test --buildsystem=golang
+endif



Alternativly, we could also disable the "problematic part" of the test until 
the upstream bug is fixed properly:

diff --git a/cpu/cpu_test.go b/cpu/cpu_test.go
index e8e0e8d..dbcaaae 100644
--- a/cpu/cpu_test.go
+++ b/cpu/cpu_test.go
@@ -85,11 +85,6 @@ func TestCpuInfo(t *testing.T) {
if len(v) == 0 {
t.Errorf("could not get CPU Info")
}
-   for _, vv := range v {
-   if vv.ModelName == "" {
-   t.Errorf("could not get CPU Info: %v", vv)
-   }
-   }
 }


In any case, I'm unconvinced that this bug is severe enough to claim it
as 'release critical' would warrant removing the package from unstable.

Processed: your mail

[Debian Bug Tracking System]

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

> Tags 976915 patch
Bug #976915 [src:service-wrapper-java] service-wrapper-java: FTBFS on ppc64el:  
[exec] wrapper.c:(.text+0x3598): undefined reference to `pow'
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#976915: (no subject)

[Logan Rosen]

Control: tags -1 patch

Subject: Re: service-wrapper-java: FTBFS on ppc64el:  [exec] 
wrapper.c:(.text+0x3598): undefined reference to `pow'
Followup-For: Bug #976915
Package: service-wrapper-java
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
Version: 3.5.30-1

Dear Maintainer,

In Ubuntu, the attached patch (from Dimitri John Ledkov ) was 
applied to achieve the following:

  * Fix as-needed linking in ppc64el and s390x per-arch Makefiles too.

Thanks for considering the patch.

Logan Rosen

-- System Information:
Debian Release: bullseye/sid
  APT prefers groovy-updates
  APT policy: (500, 'groovy-updates'), (500, 'groovy-security'), (500, 
'groovy'), (100, 'groovy-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.128-microsoft-standard (SMP w/8 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
diff -Nru service-wrapper-java-3.5.30/debian/patches/fix-as-needed-ppc.patch 
service-wrapper-java-3.5.30/debian/patches/fix-as-needed-ppc.patch
--- service-wrapper-java-3.5.30/debian/patches/fix-as-needed-ppc.patch  
2016-12-19 07:17:55.0 -0500
+++ service-wrapper-java-3.5.30/debian/patches/fix-as-needed-ppc.patch  
2017-06-20 06:22:53.0 -0400
@@ -3,10 +3,9 @@
 Author: Andreas Moog 
 Bug: https://sourceforge.net/p/wrapper/bugs/285/
 
-diff -pruN -x '*~' wrapper_3.5.25_src.orig/src/c/Makefile-linux-ppc-32.make 
wrapper_3.5.25_src/src/c/Makefile-linux-ppc-32.make
 wrapper_3.5.25_src.orig/src/c/Makefile-linux-ppc-32.make   2015-01-04 
01:21:32.915068936 +0100
-+++ wrapper_3.5.25_src/src/c/Makefile-linux-ppc-32.make2015-01-04 
01:23:18.271591362 +0100
-@@ -33,7 +33,7 @@ init:
+--- a/src/c/Makefile-linux-ppc-32.make
 b/src/c/Makefile-linux-ppc-32.make
+@@ -33,7 +33,7 @@
if test ! -d .deps; then mkdir .deps; fi
  
  wrapper: $(wrapper_SOURCE)
@@ -15,10 +14,9 @@
  
  libwrapper.so: $(libwrapper_so_OBJECTS)
${COMPILE} -shared $(LDFLAGS) $(libwrapper_so_OBJECTS) -o 
$(LIB)/libwrapper.so
-diff -pruN -x '*~' wrapper_3.5.25_src.orig/src/c/Makefile-linux-ppc-64.make 
wrapper_3.5.25_src/src/c/Makefile-linux-ppc-64.make
 wrapper_3.5.25_src.orig/src/c/Makefile-linux-ppc-64.make   2015-01-04 
01:21:32.915068936 +0100
-+++ wrapper_3.5.25_src/src/c/Makefile-linux-ppc-64.make2015-01-04 
01:23:02.287512123 +0100
-@@ -33,7 +33,7 @@ init:
+--- a/src/c/Makefile-linux-ppc-64.make
 b/src/c/Makefile-linux-ppc-64.make
+@@ -33,7 +33,7 @@
if test ! -d .deps; then mkdir .deps; fi
  
  wrapper: $(wrapper_SOURCE)
@@ -27,3 +25,25 @@
  
  libwrapper.so: $(libwrapper_so_OBJECTS)
${COMPILE} -shared $(LDFLAGS) $(libwrapper_so_OBJECTS) -o 
$(LIB)/libwrapper.so
+--- a/src/c/Makefile-linux-ppcle-64.make
 b/src/c/Makefile-linux-ppcle-64.make
+@@ -33,7 +33,7 @@
+   if test ! -d .deps; then mkdir .deps; fi
+ 
+ wrapper: $(wrapper_SOURCE)
+-  $(COMPILE) -lm -pthread $(wrapper_SOURCE) -o $(BIN)/wrapper
++  $(COMPILE) -pthread $(wrapper_SOURCE) -lm -o $(BIN)/wrapper
+ 
+ libwrapper.so: $(libwrapper_so_OBJECTS)
+   ${COMPILE} -shared $(libwrapper_so_OBJECTS) -o $(LIB)/libwrapper.so
+--- a/src/c/Makefile-linux-s390x-64.make
 b/src/c/Makefile-linux-s390x-64.make
+@@ -34,7 +34,7 @@
+   if test ! -d .deps; then mkdir .deps; fi
+ 
+ wrapper: $(wrapper_SOURCE)
+-  $(COMPILE) -lm -pthread $(wrapper_SOURCE) $(LDFLAGS) -o $(BIN)/wrapper
++  $(COMPILE) -pthread $(wrapper_SOURCE) $(LDFLAGS) -lm -o $(BIN)/wrapper
+ 
+ libwrapper.so: $(libwrapper_so_OBJECTS)
+   ${COMPILE} -shared $(libwrapper_so_OBJECTS) $(LDFLAGS) -o 
$(LIB)/libwrapper.so

Processed: closing 977306

[Debian Bug Tracking System]

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

> close 977306 5.15.0+dfsg-18
Bug #977306 [src:plplot] plplot FTBFS: dpkg-gensymbols: error: some symbols or 
patterns disappeared in the symbols file
Marked as fixed in versions plplot/5.15.0+dfsg-18.
Bug #977306 [src:plplot] plplot FTBFS: dpkg-gensymbols: error: some symbols or 
patterns disappeared in the symbols file
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#972206: marked as done (remctl FTBFS on IPV6-only buildds)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2020 01:33:57 +
with message-id 
and subject line Bug#972206: fixed in remctl 3.17-1
has caused the Debian Bug report #972206,
regarding remctl FTBFS on IPV6-only buildds
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
972206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972206
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:remctl
Version: 4.16-3
Severity: serious
Tags: sid bullseye

https://buildd.debian.org/status/fetch.php?pkg=remctl=amd64=3.16-4%2Bb7=1602646591=0

[...]
make  check-local
make[2]: Entering directory '/<>'
tests/runtests -l '/<>/tests/TESTS'

Running all tests listed in TESTS.  If any tests fail, run the failing
test program with runtests -o to see more details.

client/api..skipped (Kerberos tests not configured)
client/ccache...skipped (Kerberos tests not configured)
client/largeskipped (Kerberos tests not configured)
client/open.ok (skipped 15 tests)
client/remctl...skipped (Kerberos tests not configured)
client/source-ipskipped (Kerberos tests not configured)
client/timeout..skipped (Kerberos tests not configured)
docs/podskipped (POD syntax tests normally skipped)
docs/pod-spelling...skipped (Spelling tests only run for author)
docs/spdx-license...skipped (SPDX identifier tests normally skipped)
perl/module-version.skipped (Module version tests normally skipped)
portable/asprintf...ok
portable/daemon.ok
portable/getaddrinfook
portable/getnameinfook
portable/getopt.ok
portable/inet_aton..ok
portable/inet_ntoa..ok
portable/inet_ntop..ok
portable/mkstempok
portable/setenv.ok
portable/snprintf...ok
server/accept...skipped (Kerberos tests not configured)
server/acl..ok (skipped 4 tests)
server/acl/localgroup...ok
server/anonymousskipped (Kerberos tests not configured)
server/bind.skipped (Kerberos tests not configured)
server/config...ok
server/continue.skipped (Kerberos tests not configured)
server/emptyskipped (Kerberos tests not configured)
server/env..skipped (Kerberos tests not configured)
server/errors...skipped (Kerberos tests not configured)
server/help.skipped (Kerberos tests not configured)
server/invalid..skipped (Kerberos tests not configured)
server/logging..ok
server/misc.skipped (Kerberos tests not configured)
server/shell-misc...ok
server/ssh-parseok
server/stdinskipped (Kerberos tests not configured)
server/streamingskipped (Kerberos tests not configured)
server/sudo.ok
server/summary..skipped (Kerberos tests not configured)
server/user.skipped (Kerberos tests not configured)
server/version..skipped (Kerberos tests not configured)
style/obsolete-strings..skipped (Obsolete strings tests only run for author)
util/buffer.ok
util/gss-tokens.skipped (Kerberos tests not configured)
util/messages...ok
util/messages-krb5..ok
util/network/addr-ipv4..ok
util/network/addr-ipv6..ok
util/network/client.ok
util/network/server.MISSED 34-42 (killed by signal 14)
util/tokens.ok
util/vector.ok
util/xmallocskipped (xmalloc tests only run for author)
util/xwrite.ok (skipped 2 tests)
valgrind/logs...skipped (Not testing under valgrind)

Failed Set Fail/Total (%) Skip Stat  Failing Tests
-- --    
util/network/server   9/3426%8   --  34-42

Failed 9/1998 tests, 99.55% okay, 58 tests skipped.
Files=58,  Tests=1998,  16.15 seconds (1.09 usr + 0.33 sys = 1.42 CPU)
make[2]: *** [Makefile:4628: check-local] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [Makefile:3986: check-am] Error 2
make[1]: Leaving directory '/<>'
dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2
make: *** [debian/rules:26: binary-arch] Error 25
--- End Message ---
--- Begin Message ---
Source: remctl
Source-Version: 3.17-1
Done: Russ Allbery 

We believe that the bug you reported is fixed in the latest version of
remctl, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 

Bug#977312: marked as done (src:ivar: fails to migrate to testing for too long: FTBFS on i386)

[Debian Bug Tracking System]

Your message dated Sun, 13 Dec 2020 23:04:31 +
with message-id 
and subject line Bug#977312: fixed in ivar 1.3+dfsg-1
has caused the Debian Bug report #977312,
regarding src:ivar: fails to migrate to testing for too long: FTBFS on i386
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
977312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977312
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ivar
Version: 1.2.2+dfsg-3
Severity: serious
Tags: sid bullseye ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:ivar in its
current version in unstable has been trying to migrate for 61 days [2].
Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=ivar



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ivar
Source-Version: 1.3+dfsg-1
Done: =?utf-8?q?=C3=89tienne_Mollier?= 

We believe that the bug you reported is fixed in the latest version of
ivar, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 977...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Étienne Mollier  (supplier of updated ivar package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 13 Dec 2020 22:18:59 +0100
Source: ivar
Architecture: source
Version: 1.3+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Étienne Mollier 
Closes: 977312
Changes:
 ivar (1.3+dfsg-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version
   * Standards-Version: 4.5.1 (routine-update)
   * Run test suite in a single thread.  (Closes: #977312)
Checksums-Sha1:
 8ec3a8e0d95b066b47b7f0b8751cf382fb9196ba 2036 ivar_1.3+dfsg-1.dsc
 743fcaeac5b42311cb0d7d180932c8caeb0fcb6d 630292 ivar_1.3+dfsg.orig.tar.xz
 4ed491f61b0494756f4c9494f6e529a3c271449f 42988 ivar_1.3+dfsg-1.debian.tar.xz
 91249276ccf87aa681a0fcec8dbc7622a846686d 6882 ivar_1.3+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 7ba475a344fee225279f9b096f44548699a7fb61bf626e5060dce21c8b80 2036 
ivar_1.3+dfsg-1.dsc
 2d206795c0c3b94e41ea3d9b94d8ac1b8f3d2bbc1fd62b2c8c510475bad81ecc 630292 
ivar_1.3+dfsg.orig.tar.xz
 deff74cce3a60d44b99dc7d1e6d784c42b1c9c78a02496562cab29ef093b12f6 42988 
ivar_1.3+dfsg-1.debian.tar.xz
 bcebd49ea40857eddf9d64a8e67122e2dbda77fa58dba65c94b58faeeb014eae 6882 
ivar_1.3+dfsg-1_amd64.buildinfo
Files:
 1480f00e4129e52bbdd6bf6e640a59ea 2036 science optional ivar_1.3+dfsg-1.dsc
 c54b862be202ef61b52d8dd7a69908ce 630292 science optional 
ivar_1.3+dfsg.orig.tar.xz
 9a75e6c5f1a30d33bea62971f4e3d017 42988 science optional 
ivar_1.3+dfsg-1.debian.tar.xz
 7ba2a600c7820810c5ecb0ef26b98949 6882 science optional 
ivar_1.3+dfsg-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAl/WmVUUHHRtYW5jaWxs
QGRlYmlhbi5vcmcACgkQIdIFiZdLPpaRPQ//evhmYtQ+5EGOLcexkq9l2kuG2XpH
6zjrt9YkEsrr2OibpyyJ4RxWxRXb4IjCIEn0MtqeA9R4kWn4cWomJgBHFhcikX+T
zwj/nJ4gt/hVtpwxBjVR5KQqSomEyOC5cMJmo4TiW0Cl7+DfyMhm/s81Jqule/xM
74HWRnv+Ee94xn4F8vVXR11japQzjT7uVB2ztVKYRY41IgYTwc4FW+9vRRVWL7ki

Bug#971713: sysstat: init or systemd file has overlapping runlevels

[Trek]

On Sun, 13 Dec 2020 11:03:57 +0100
Robert Luberda  wrote:

> sysstat's init.d has the following lines in /etc/init.d/sysstat
> # Default-Start: 2 3 4 5
> # Default-Stop:
> I'm not sure how empty Default-Stop is interpreted, so I've just tried

it seems to me that on empty Default-Stop the runlevels will be copied
from Default-Start, but this is not an issue, just to better understand


> to change it to:
> # Default-Stop: 0 1 6

this seems correct


> As a result insserv displays two warnings instead of one:

before explaining the error messages, remember that init scripts and
their links are configuration files, like (almost) everything else
under /etc


> insserv: warning: current stop runlevel(s) (empty) of script `sysstat'
> overrides LSB defaults (0 1 6).

it is saying that the current stop runlevels (the /etc/rc*.d/*sysstat
links) are overriding the ones described by the LSB header (inside
the /etc/init.d/sysstat script)


> insserv: Script ssh has overlapping Default-Start and Default-Stop
> runlevels (2 3 4 5) and (2 3 4 5). This should be fixed.

the end result is that the rc*.d links are unchanged and the runlevels
still inconsistent


> As a maintainer of sysstat I have no idea what else I can do to fix
> the warning. It seems to me there is some bug in insserv. As the bug
> affects my package, and  according to the bug report "any package
> that has init.d file", I'm setting severity of this report to grave.

on new installations, simply adding the correct levels (0 1 6) to the
script should fix the bug, but to fix on upgrades you should remove
those links before running insserv, that is adding something like that
to postinst inside the configure step:

  # new Default-Stop (see #971713)
  if dpkg --compare-versions "$2" le '12.4.0-2'; then
 update-rc.d -f sysstat remove
  fi

this will also remove any tweaking done by user, that should be
annotated inside the NEWS.Debian file

I would like to provide you a patch, but I can't find where the init.d
file is enabled inside the sysstat postinst, that should be:

  update-rc.d sysstat defaults

ciao!

Bug#977312: [RFS] ivar 1.3+dfsg-1

[tony mancill]

On Sun, Dec 13, 2020 at 11:25:00PM +0100, Étienne Mollier wrote:
> Control: tag -1 pending
> 
> Greetings,
> 
> Thanks for the notice Paul, it turned out the build time test
> failed at random on amd64 as well as i386 with same symptoms.  I
> suspect several test components were attempting to access the
> same data set, or something of that taste.  When I ran the suite
> using dh_auto_test --no-parallel, I haven't been able to
> reproduce the issue seen on i386 build (nor amd64).
> 
> To Debian Med fellows, routine-update caught ivar 1.3 in the
> process; it is available for review and upload hopefully (and DM
> grant if you think relevant):
> 
>   https://salsa.debian.org/med-team/ivar/

Hi Étienne,

I am able to find your public GPG key, but I don't see it in
debian-keyring for the DM grant.  Please let me know what I'm missing
here.

In the meantime, I have uploaded the package.

Thank you for the update!
tony


signature.asc
Description: PGP signature

Processed: Re: Bug#976134: vorta: flaky autopkgtest

[Debian Bug Tracking System]

Processing control commands:

> tag -1 confirmed
Bug #976134 [src:vorta] vorta: flaky autopkgtest
Added tag(s) confirmed.

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

Bug#976134: vorta: flaky autopkgtest

[Nicholas D Steeves]

Control: tag -1 confirmed

Hi Graham,

Thank you for this bug report.  Reply follows inline:

On Mon, Nov 30, 2020 at 09:11:29AM +0200, Graham Inggs wrote:
> Source: vorta
> Version: 0.7.1-2
> Severity: serious
> X-Debbugs-CC: debian...@lists.debian.org
> User: debian...@lists.debian.org
> Usertags: flaky
> 
> Hi Maintainer
> 
> The autopkgtests of vorta are failing often.  Two of the failures
> [1][2] seem to be a time out, but there may be other problems as well.
> I've copied what I hope is the relevant part of these logs below.
> 
> Regards
> Graham
> 
> 
> [1] 
> https://ci.debian.net/data/autopkgtest/testing/arm64/v/vorta/8520699/log.gz
> [2] https://ci.debian.net/data/autopkgtest/testing/i386/v/vorta/8521042/log.gz
>
[snip much appreciated bts]

I'm speculating that ppc64el might also be affected due to
https://bugs.debian.org/977114 (mariadb via python-peewee), but I
haven't yet sat down to analyse the problem so at this point that's
just a guess.

Ubuntu has a patch that increases a timeout value (sadly not forwarded
back upstream to us), and it might be necessary to increase other
self-test timeouts--waiting longer is sometimes all it takes for a test
to succeed.


Regards,
Nicholas


signature.asc
Description: PGP signature

Bug#973848: chromium: Unsupported version, many security bugs unfixed

[David Worsham]

 Hi there,

Thank you for all of the great work on this so far!

I'm interested in helping with this effort, and very familiar with C++ code
and processes in Google code (though not specifically Chromium).  I have
gotten the 83/84 versions in unstable/experimental building locally in a
container as a sanity check.  I also have a fork on salsa to work from
now:  https://salsa.debian.org/arbreng/chromium

However, I am very new to Debian packaging and so not sure what the "ideal"
workspace setup and workflow is for this kind of work.  I just kinda made
things up as I went along yesterday.  If one of ya'll could walk me through
it that would be greatly appreciated - I only know what I learned from
the debian Wiki.  I know how to build and hack on Chromium itself -- it's
just the packaging bits that are still a bit mystifying to me.

Thanks again for all the effort!

On Sat, 12 Dec 2020 19:47:32 +0100 Michel Le Bihan 
wrote:
> Hello,
>
> Thank you for your reply. libvpx got updated in Debian, but I can't use
> it because it's missing a lib. I also had issues with harfbuzz, so I'm
> using bundled versions of those libs as you are. I also used your ozone
> patch because it is match cleaner than mine. With that I was able to
> build Chromium, but with many lint errors and many missing patches.
>
> BTW, have you tried opening a bug upstream or submitting your ozone
> patch upstream?
>
> Michel Le Bihan
>
> On Wed, 9 Dec 2020 04:34:39 + Jeff Blake  wrote:
> > On Tue, 08 Dec 2020 12:33:57 +0100 Michel Le Bihan 
wrote:
> > > Hello,
> > >
> > > I started work on updating the chromium package (you can see my work
> > > here:
> > >
https://salsa.debian.org/mimi8/chromium/-/commit/af70b14701aaf6bdb34e23af01657676e27ba5d4
>

> > ), but got stuck because `libvpx` is too old in Debian testing. It
> > > needs to be updated before I can continue work.
> > >
> > > Michel Le Bihan
> > >
> > >
> > >
> >
> > I've managed to successfully update the ungoogled-chromium debian
package [1], which is based upon
> > the official debian package.
> >
> > Until libvpx is updated (or a new release is made) you could use
Chromium's bundled version of libvpx [2].
> >
> > Feel free to have a look around my repo, as you might well encounter
some of the same problems that
> > I had in getting things to build.
> >
> >
> > Jeff Blake 
> >
> >
> > [1]
https://github.com/berkley4/ungoogled-chromium-debian/commits/87.0.4280.88
>

>
> > [2]
https://github.com/berkley4/ungoogled-chromium-debian/commit/05ffc529e685817aac8a9c5bb419daba17204a66
>

>
> >
> >
>
>
>
>

Bug#977310: marked as done (libboost1.74-dev needs Breaks+Replaces: libleatherman-dev (<< 1.12.1+dfsg-1.1~))

[Debian Bug Tracking System]

Your message dated Sun, 13 Dec 2020 22:33:35 +
with message-id 
and subject line Bug#977310: fixed in boost1.74 1.74.0-4
has caused the Debian Bug report #977310,
regarding libboost1.74-dev needs Breaks+Replaces: libleatherman-dev (<< 
1.12.1+dfsg-1.1~)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
977310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libboost1.74-dev
Version: 1.74.0-3
Severity: serious

See #975863 for background.
--- End Message ---
--- Begin Message ---
Source: boost1.74
Source-Version: 1.74.0-4
Done: Anton Gladky 

We believe that the bug you reported is fixed in the latest version of
boost1.74, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 977...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated boost1.74 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 13 Dec 2020 22:55:30 +0100
Source: boost1.74
Architecture: source
Version: 1.74.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Boost Team 
Changed-By: Anton Gladky 
Closes: 977310
Changes:
 boost1.74 (1.74.0-4) unstable; urgency=medium
 .
   * [283f917] Fix description for nowide-library
   * [fa3c8ab] Add Breaks+Replaces: libleatherman-dev (<< 1.12.1+dfsg-1.1~)
   to libbost1.74-dev. (Closes: #977310)
Checksums-Sha1:
 b83a638b3a217d8669de99bc37e71129cd77f9a6 9247 boost1.74_1.74.0-4.dsc
 449b71702040fd09f868f4458b384d48c6dc478c 365548 
boost1.74_1.74.0-4.debian.tar.xz
 ddc0779253a5f7f6a00bf05f17a8a38b74032d14 11259 
boost1.74_1.74.0-4_source.buildinfo
Checksums-Sha256:
 68598ab0fa71faca40e9239857b8ef7f4505319c7e2137689a845d4cb7473946 9247 
boost1.74_1.74.0-4.dsc
 8eaa495784bb798b684d8297c8fac7cd27cfe40786f62f7bac92c90259d9085d 365548 
boost1.74_1.74.0-4.debian.tar.xz
 509d9c8411cd11cc093c776e78be86db460e7882e274a2e1449e12f95182d58b 11259 
boost1.74_1.74.0-4_source.buildinfo
Files:
 c73ccd403addac66ce8080466ae23b11 9247 libs optional boost1.74_1.74.0-4.dsc
 6310777494f77e42493908b929ba0cf7 365548 libs optional 
boost1.74_1.74.0-4.debian.tar.xz
 2f86086ee6b56a35b94c02b89b0ee15b 11259 libs optional 
boost1.74_1.74.0-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAl/Wk4QRHGdsYWRrQGRl
Ymlhbi5vcmcACgkQ0+Fzg8+n/wZVWQ/8D94NzVv6KLilQeyFbXqtHVkWx5urz9Hg
0Expv7QY/pYwZI7KB/7E0gAD8tMZRZIykLU0bo0GrKbASTYqzczi1HTaJDGOeRAz
guSRNMib+S9wFuutZzFyAdwU3TqwF67iYU1tWVzxbrcbRzjGtZfY2hKlNtNqC8aY
r362H/8j3QU/Rf0E4pbX8juePPNpOqUalTl/KesR6UDBFQz6+R//NA/mhl4aDdNk
Po7dCX3f4E9tZ6pBVzXpWb/0ILXtNgl7+e2HN5/V6V7l5kqPFzvr1wd5RL74PaV4
1TYi+r7e57JyM+Cbu7SuiAQmDQVwHSR97m8M/wGzt+60eELAZhhjWk1bd59qZtSg
pTC3S88wt6pe1pj93bj0laZHFk+K8taqTpt/XuURlTOWf/bAoIR5/5Co5JdUYbXT
CUiSX1P2DfLPtdmiGck24uNrnMeZPUVg/mbKoZpcTLwuh668H4TgF3Xx1Nj2SCjt
oZ/RKuKCuKjIXPK4DAOiBz5FHzCKm++i7rS+id7s2BqM4Iu/r2+d5CGWTJqV2qeE
zE/GxwQKDfDdNad40F03EW7lrJX+6JLL3V0qlRMG1A67hHuLj0r8vOIPbTwgbqNb
roNCdmqKmzvBzhuso6wrcq8vO+r0gUYEwdt5gYpyivGh3IHkQ9MuS3yUEenRYLgW
n4NNb8alpNo=
=VlLW
-END PGP SIGNATURE End Message ---

Bug#975863: Merge request

[Anton Gladky]

Dear maintainers,

MR is here [1]. Please consider to accept it.

[1] https://salsa.debian.org/puppet-team/leatherman/-/merge_requests/2

Best Regards

Anton

Processed: [RFS] ivar 1.3+dfsg-1

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #977312 [src:ivar] src:ivar: fails to migrate to testing for too long: 
FTBFS on i386
Added tag(s) pending.

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

Bug#977312: [RFS] ivar 1.3+dfsg-1

[Étienne Mollier]

Control: tag -1 pending

Greetings,

Thanks for the notice Paul, it turned out the build time test
failed at random on amd64 as well as i386 with same symptoms.  I
suspect several test components were attempting to access the
same data set, or something of that taste.  When I ran the suite
using dh_auto_test --no-parallel, I haven't been able to
reproduce the issue seen on i386 build (nor amd64).

To Debian Med fellows, routine-update caught ivar 1.3 in the
process; it is available for review and upload hopefully (and DM
grant if you think relevant):

https://salsa.debian.org/med-team/ivar/

Kind Regards,
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/1, please excuse my verbosity.


signature.asc
Description: PGP signature

Bug#970497: marked as done (igraph: FTBFS on mips64el)

[Debian Bug Tracking System]

Your message dated Sun, 13 Dec 2020 22:33:16 +0100
with message-id <0b74711a-65bd-2e51-6f36-c01baab09...@rezozer.net>
and subject line igraph: FTBFS on mips64el: fixed in version 0.8.5
has caused the Debian Bug report #970497,
regarding igraph: FTBFS on mips64el
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
970497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970497
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: igraph
Severity: serious
Tags: ftbfs upstream
Justification: Policy 1.2.3

Hi,

the package does not build from source on mips64el as you can see here


https://buildd.debian.org/status/fetch.php?pkg=igraph=mips64el=0.8.2%2Bds-2=1596624159=0

Kind regards

Andreas.


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (50, 'buildd-unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.8.0-1-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
It appears that igraph 0.8.5 build well now on mips64el arch,
so I am closing the bug.
Best wishes,
Jerome

-- 
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B--- End Message ---

Bug#975814: marked as done (python-pyramid-chameleon: FTBFS: ModuleNotFoundError: No module named 'setuptools')

[Debian Bug Tracking System]

Your message dated Sun, 13 Dec 2020 21:06:29 +
with message-id 
and subject line Bug#975814: fixed in python-pyramid-chameleon 0.3-4
has caused the Debian Bug report #975814,
regarding python-pyramid-chameleon: FTBFS: ModuleNotFoundError: No module named 
'setuptools'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
975814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975814
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pyramid-chameleon
Version: 0.3-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201125 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3,sphinxdoc --buildsystem=pybuild
>debian/rules override_dh_auto_clean
> make[1]: Entering directory '/<>'
> rm -rf docs/_build
> dh_auto_clean
> I: pybuild base:232: python3.8 setup.py clean 
> Traceback (most recent call last):
>   File "setup.py", line 3, in 
> from setuptools import setup, find_packages
> ModuleNotFoundError: No module named 'setuptools'
> E: pybuild pybuild:353: clean: plugin distutils failed with: exit code=1: 
> python3.8 setup.py clean 
> dh_auto_clean: error: pybuild --clean --test-nose -i python{version} -p "3.8 
> 3.9" returned exit code 13
> make[1]: *** [debian/rules:11: override_dh_auto_clean] Error 25

The full build log is available from:
   
http://qa-logs.debian.net/2020/11/25/python-pyramid-chameleon_0.3-3_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: python-pyramid-chameleon
Source-Version: 0.3-4
Done: Nilesh Patra 

We believe that the bug you reported is fixed in the latest version of
python-pyramid-chameleon, which is due to be installed in the Debian FTP 
archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 975...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated 
python-pyramid-chameleon package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 13 Dec 2020 19:27:55 +
Source: python-pyramid-chameleon
Architecture: source
Version: 0.3-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Nilesh Patra 
Closes: 975814
Changes:
 python-pyramid-chameleon (0.3-4) unstable; urgency=medium
 .
   * Team Upload.
   [ Debian Janitor ]
   * Set upstream metadata fields: Bug-Database, Repository, Repository-Browse.
 .
   [ Ondřej Nový ]
   * d/control: Update Maintainer field with
 new Debian Python Team contact address
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa layout
 .
   [ Nilesh Patra ]
   * Add onovy's changes for 0.3-3 which seem unpushed
   * Fix doc build
   * Add python3-setuptools to Build-deps
 (Closes: #975814)
   * Bump Watch file standard to 4
   * Standards-Version: 4.5.1, debhelper-compat: 13
   * Add "Rules-Requires-Root:no"
Checksums-Sha1:
 37ed79367923b7069f4b083bddb3c25cf85fbe8f 2476 
python-pyramid-chameleon_0.3-4.dsc
 a4029af8acdf6097fdf0e67f484bbb1ccf6ed87a 5456 
python-pyramid-chameleon_0.3-4.debian.tar.xz
 b828ebc3c3e193c78a541eb75adbcb130b9dc60d 8344 
python-pyramid-chameleon_0.3-4_amd64.buildinfo
Checksums-Sha256:
 35e7e6f352737018a6be62c9974bebf780691d2f343ca6f20612017c10975a84 2476 
python-pyramid-chameleon_0.3-4.dsc
 4c46ab4052d53872a586c8386799a3147f7d6da880fae0510ebbcc41941863cb 5456 
python-pyramid-chameleon_0.3-4.debian.tar.xz
 cd8df81fce3e3cce0bbb30735760f44ce6d5e9fc88a235afaae780b8992128ac 8344 
python-pyramid-chameleon_0.3-4_amd64.buildinfo
Files:
 1a93c4a5231f1d7b13723a1252822112 2476 python optional 
python-pyramid-chameleon_0.3-4.dsc
 93ce2a202abcf04229306c0dd161334b 5456 python optional 
python-pyramid-chameleon_0.3-4.debian.tar.xz
 

Processed: src:rust-bzip2-sys: fails to migrate to testing for too long: autopkgtest regression

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.1.9-1
Bug #977314 [src:rust-bzip2-sys] src:rust-bzip2-sys: fails to migrate to 
testing for too long: autopkgtest regression
Marked as fixed in versions rust-bzip2-sys/0.1.9-1.
Bug #977314 [src:rust-bzip2-sys] src:rust-bzip2-sys: fails to migrate to 
testing for too long: autopkgtest regression
Marked Bug as done
> block -1 by 975480
Bug #977314 {Done: Paul Gevers } [src:rust-bzip2-sys] 
src:rust-bzip2-sys: fails to migrate to testing for too long: autopkgtest 
regression
977314 was not blocked by any bugs.
977314 was not blocking any bugs.
Added blocking bug(s) of 977314: 975480

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

Bug#977314: src:rust-bzip2-sys: fails to migrate to testing for too long: autopkgtest regression

[Paul Gevers]

Source: rust-bzip2-sys
Version: 0.1.7-2
Severity: serious
Control: close -1 0.1.9-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 975480

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package
src:rust-bzip2-sys in its current version in unstable has been trying to
migrate for 60 days [2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=rust-bzip2-sys




OpenPGP_signature
Description: OpenPGP digital signature

Bug#977313: src:rust-rpassword: fails to migrate to testing for too long: autopgktest regression

[Paul Gevers]

Source: rust-rpassword
Version: 4.0.5-1
Severity: serious
Control: close -1 5.0.0-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 975479

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package
src:rust-rpassword in its current version in unstable has been trying to
migrate for 60 days [2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=rust-rpassword




OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:rust-rpassword: fails to migrate to testing for too long: autopgktest regression

[Debian Bug Tracking System]

Processing control commands:

> close -1 5.0.0-1
Bug #977313 [src:rust-rpassword] src:rust-rpassword: fails to migrate to 
testing for too long: autopgktest regression
Marked as fixed in versions rust-rpassword/5.0.0-1.
Bug #977313 [src:rust-rpassword] src:rust-rpassword: fails to migrate to 
testing for too long: autopgktest regression
Marked Bug as done
> block -1 by 975479
Bug #977313 {Done: Paul Gevers } [src:rust-rpassword] 
src:rust-rpassword: fails to migrate to testing for too long: autopgktest 
regression
977313 was not blocked by any bugs.
977313 was not blocking any bugs.
Added blocking bug(s) of 977313: 975479

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

Bug#977312: src:ivar: fails to migrate to testing for too long: FTBFS on i386

[Paul Gevers]

Source: ivar
Version: 1.2.2+dfsg-3
Severity: serious
Tags: sid bullseye ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:ivar in its
current version in unstable has been trying to migrate for 61 days [2].
Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=ivar



OpenPGP_signature
Description: OpenPGP digital signature

Bug#977311: node-uglifyjs-webpack-plugin: dead upstream since July 2019

[Jonas Smedegaard]

Package: node-uglifyjs-webpack-plugin
Version: 1.3.0-9
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

node-uglifyjs-webpack-plugin is dead since 1.5 years, already carries a
patch to not actually use node-uglifyjs but node-terser, and terser will
soon see a major backwards-incompatible change that will require even
more custom hacks.

It seems this package has only one reverse dependency (webpack) and two
reverse build-dependencies (node-chai and node-webpack).

Seems it is time to replace this package with its successor,
https://github.com/webpack-contrib/terser-webpack-plugin

Setting severity to serious due to the upcoming breaking change to
node-terser.


 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl/Wee8ACgkQLHwxRsGg
ASEm7A/9Ej+JJvvILoUu8D+AwKDF/JYKYo/UDALjSYVODE81lgpQ8QkuQxsIg/yF
MKJHD/ZhPoO+MPSApY93rJ+Gsoh5N2vDtT1F7RfbI7kqq8iT08NF3cPyBirbF8Rg
ewPUP4gnRQd4bSLOesYzv1w57mESrqd+u7Cw1kPZM9c5S8k1JMTvFwTZjBrNoHu3
nMMgFgkxDO3tHOTy8verRvBfWL7UwfrecBUKTM92SswzBz03j7bj98x17Ra8WtyM
0jihm44SE6urFXJSCRc91Pbse1zG9Pi10GKqiqKKJOZl7hsZ9rGEE68e+GLU8k+L
b2cCco0THSb+1HmlI0xJsVuni6PcO+GeijW2UFuQ7Vn80STrLJ4Ots9GEuKRWbNO
meo9Q1QfcyJxhVs+XfxPTbKEJr5aipgCgCAy/M9bmuL2ltDx4vLUIokMC9NK37ZO
67WxdrOb91bbCVHisntjsRlmqf7ltUZEIx6pvyS42GW5bdBPyzoZYtqqnGWkJyDz
z52DT4Q5FROy/iZRTCyTO+vHAOnMoW7jRYQfPsyrpVn51AF+a439u8FVz6LkNAv+
nnEV1RrZ90/hwNMK4abfIN+ljPsr7LoI+sux1FeDLDerBRvAEo2pr3u9DxiPzYKU
Q1AJcIig0X+CrwwMnrpomy34W6WpQ7Qi4aPJdaAPgD5nms4Z6u0=
=9occ
-END PGP SIGNATURE-

Bug#977310: libboost1.74-dev needs Breaks+Replaces: libleatherman-dev (<< 1.12.1+dfsg-1.1~)

[Adrian Bunk]

Package: libboost1.74-dev
Version: 1.74.0-3
Severity: serious

See #975863 for background.

Bug#977308: shasta: hardcoded dependencies on boost 1.71

[Graham Inggs]

Source: shasta
Version: 0.6.0-4
Severity: serious
Tags: ftbfs

Hi Maintainer

Binary package shasta has a hardcoded dependency on
libboost-chrono1.71.0 and binary package python3-shasta has a
hardcoded dependency on libboost-program-options1.71.0.

Boost 1.71 will be removed after the Boost 1.74 transition, which is ongoing.

Regards
Graham

Bug#977309: node-less: needlessly depends on node-terser

[Jonas Smedegaard]

Package: node-less
Version: 4.1.2-7
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

node-less depends on node-terser, which will soon see a major
backwards-incompatible upgrade.

Seem to me nothing in binary package node-less actually calls "terser"
and that the runtime dependency on that Nodejs module can therefore
simply be dropped.

Setting severity to serious, because if the library interface _is_ used
then that will soon break.

(the upcoming major change affects only library interface, not arguments
to the executable uglifyjs.terser).


 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl/WdoQACgkQLHwxRsGg
ASHR+g//ePCWHgbtuA7Cb8jjumE9YwnfGgdENm5DHwrIBfGfw7rmzxyz863l8Mj5
GHFxK43ORA708D6+imEzHSTjjr6OmOXK6ES44QfkkScZrpImuo1kREBN6F6zhfAo
4Ju3vck9IfpYT2Ou01PQHp9PiieacAEqhia0iuHOVdT6Asuc7lM5Ul96HJwKiy0U
mcdrWTLkONqqihkhzJNlA33HDfsofT/x8Bg2/JPodXmhv47PZPYR6zHyi2f3LdTd
SCZElGhUDHQLCBXx3qdaxwAnBSiSyBUfHRRfiGK6NYw91TH18Fa2S1eK2krKZTbp
Clf5SOovYdRBulzt2cRbPhEvRTcINUMXOBwCfMuZEXwiqjuRNb7vqF4HuDLDfbCH
yapEYOl4ZdDs7paay/hCGNza5YiOLeIZOGl6CqMcagez2uqNib23sXglPFa3AKPF
5wusEwaKnVxH0wGrQ9xCa6ljwGbiVhOeK+POg3eDZlI7p3MKMfe8lPU7faWOV+Ny
G7dzMlSxw1AvCbEd89m1sF5w5T6+gJF72QXwlb0TfjyVPq6ZmV4V+sjToeR3Dld4
n3jEp1IxoLcPjBKVLWLDRVZ2kYjgQ0tvZNrRF98ckEeZh7vXtCKUXevGwAEEgbvm
o/mQ8Frs5jCaolKmorNeEHKfGOZCS6rUrZ0VpfLJPpXxB49+wQo=
=d6Bp
-END PGP SIGNATURE-

Processed: closing 977221

[Debian Bug Tracking System]

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

> close 977221 18.08.6+dfsg1-7
Bug #977221 [src:geophar] geophar FTBFS: Please add appropriate interpreter 
package to Build-Depends
Marked as fixed in versions geophar/18.08.6+dfsg1-7.
Bug #977221 [src:geophar] geophar FTBFS: Please add appropriate interpreter 
package to Build-Depends
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#977306: plplot FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file

[Adrian Bunk]

Source: plplot
Version: 5.15.0+dfsg-17
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=plplot

...
   dh_makeshlibs -a -a -O-Scmake
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libplplot17/DEBIAN/symbols doesn't match 
completely debian/libplplot17.symbols
--- debian/libplplot17.symbols (libplplot17_5.15.0+dfsg-17_amd64)
+++ dpkg-gensymbolsN0fXmN   2020-12-13 06:56:03.198015538 +
@@ -1,6 +1,6 @@
 libplplot.so.17 libplplot17 #MINVER#
 * Build-Depends-Package: libplplot-dev
- FontLookup@Base 5.15.0+dfsg
+#MISSING: 5.15.0+dfsg-17# FontLookup@Base 5.15.0+dfsg
  c_pl_setcontlabelformat@Base 5.15.0+dfsg
  c_pl_setcontlabelparam@Base 5.15.0+dfsg
  c_pladv@Base 5.15.0+dfsg
@@ -198,9 +198,9 @@
  plAllocDev@Base 5.15.0+dfsg
  plClearOpts@Base 5.15.0+dfsg
  plCloseFile@Base 5.15.0+dfsg
- plD_FreeType_Destroy@Base 5.15.0+dfsg
- plD_FreeType_init@Base 5.15.0+dfsg
- plD_render_freetype_text@Base 5.15.0+dfsg
+#MISSING: 5.15.0+dfsg-17# plD_FreeType_Destroy@Base 5.15.0+dfsg
+#MISSING: 5.15.0+dfsg-17# plD_FreeType_init@Base 5.15.0+dfsg
+#MISSING: 5.15.0+dfsg-17# plD_render_freetype_text@Base 5.15.0+dfsg
  plFamInit@Base 5.15.0+dfsg
  plFindCommand@Base 5.15.0+dfsg
  plFindName@Base 5.15.0+dfsg
@@ -254,7 +254,7 @@
  pl_cpcolor@Base 5.15.0+dfsg
  pl_create_tempfifo@Base 5.15.0+dfsg
  pl_create_tempfile@Base 5.15.0+dfsg
- pl_set_extended_cmap0@Base 5.15.0+dfsg
+#MISSING: 5.15.0+dfsg-17# pl_set_extended_cmap0@Base 5.15.0+dfsg
  plabort@Base 5.15.0+dfsg
  plbuf_restore@Base 5.15.0+dfsg
  plbuf_save@Base 5.15.0+dfsg
dh_makeshlibs: error: failing due to earlier errors
make: *** [debian/rules:41: binary-arch] Error 25

Bug#977305: ros-ros-comm: FTBFS with boost 1.74

[Sebastian Ramacher]

Source: ros-ros-comm
Version: 1.15.9+ds1-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

See
https://buildd.debian.org/status/fetch.php?pkg=ros-ros-comm=amd64=1.15.9%2Bds1-3=1607875323=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#977269: [Pkg-javascript-devel] Bug#977269: node-rollup-plugin-terser seems incompatible with current node-terser

[Jonas Smedegaard]

Control: severity 977269 important
Control: tags 977269 +moreinfo +unreproducible

Quoting Jonas Smedegaard (2020-12-13 20:29:46)
> Quoting Jonas Smedegaard (2020-12-13 17:22:05)
> > Quoting Xavier Guimard (2020-12-13 13:19:47)
> > > Package: node-rollup-plugin-terser
> > > Version: 7.0.2-2
> > > Severity: grave
> > > Justification: renders package unusable
> > > 
> > > When trying current rollup-plugin-terser (7.0.2)  with current
> > > node-terser (4.1.2), package is unuseable:
> > > 
> > > $ rollup -c
> > > 
> > > index.js → dist/pako.js, dist/pako.min.js...
> > > [!] (plugin terser) Error: Cannot find module 
> > > '/home/xavier/dev/debian/src/pkg-js/packages/node-pako/node_modules/terser/dist/bundle.min.js'.
> > >  Please verify that the package.json has a valid "main" entry
> > 
> > Neither node-rollup-plugin-terser nor node-terser asks for files below 
> > /home/xavier - please try locate which code did that.
> 
> Something _is_ broken with node-rollup-plugin-terser - the provided 
> error message is just not really helpful for me.
> 
> I might have a fix for the error I located - we'll see if that turns out 
> to also cure the issue you are experiencing, but for future sake please 
> try unwrap any node_modules tricks when reporting bugs, as they hide 
> ability to trace what is going on where (at least for me - I have no 
> doubt that you are fluent in your tools).

If problem persist with node-rollup-plugin-terser 7.0.2-3 then please 
try isolate a test causing the failure without node_modules wrapping.

Otherwise please close.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Processed: Re: [Pkg-javascript-devel] Bug#977269: node-rollup-plugin-terser seems incompatible with current node-terser

[Debian Bug Tracking System]

Processing control commands:

> severity 977269 important
Bug #977269 [node-rollup-plugin-terser] node-rollup-plugin-terser seems 
incompatible with current node-terser
Severity set to 'important' from 'grave'
> tags 977269 +moreinfo +unreproducible
Bug #977269 [node-rollup-plugin-terser] node-rollup-plugin-terser seems 
incompatible with current node-terser
Added tag(s) moreinfo.
Bug #977269 [node-rollup-plugin-terser] node-rollup-plugin-terser seems 
incompatible with current node-terser
Added tag(s) unreproducible.

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

Bug#976547: Bug#976535: Bug#976495: also happens on amd64, should be worked around by 1.8.20-5 but the real fix will come with 1.8.20-6

[Neil Roeth]

Attached is a minimal Docbook SGML file and a script which invokes the
commands required to make a PDF using pdfjadetex.

Thanks for looking into this.


test.sh
Description: application/shellscript


  Some Title Here
  STH
  

  Neil
  Roeth


  2020
  Neil Roeth

  
  
Introduction
This is a test.  This is only a test.  Now, back to our regularly scheduled program.
  

Bug#977269: [Pkg-javascript-devel] Bug#977269: node-rollup-plugin-terser seems incompatible with current node-terser

[Jonas Smedegaard]

Quoting Jonas Smedegaard (2020-12-13 17:22:05)
> Quoting Xavier Guimard (2020-12-13 13:19:47)
> > Package: node-rollup-plugin-terser
> > Version: 7.0.2-2
> > Severity: grave
> > Justification: renders package unusable
> > 
> > When trying current rollup-plugin-terser (7.0.2)  with current
> > node-terser (4.1.2), package is unuseable:
> > 
> > $ rollup -c
> > 
> > index.js → dist/pako.js, dist/pako.min.js...
> > [!] (plugin terser) Error: Cannot find module 
> > '/home/xavier/dev/debian/src/pkg-js/packages/node-pako/node_modules/terser/dist/bundle.min.js'.
> >  Please verify that the package.json has a valid "main" entry
> 
> Neither node-rollup-plugin-terser nor node-terser asks for files below 
> /home/xavier - please try locate which code did that.

Something _is_ broken with node-rollup-plugin-terser - the provided 
error message is just not really helpful for me.

I might have a fix for the error I located - we'll see if that turns out 
to also cure the issue you are experiencing, but for future sake please 
try unwrap any node_modules tricks when reporting bugs, as they hide 
ability to trace what is going on where (at least for me - I have no 
doubt that you are fluent in your tools).


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Processed: Re: fix package name

[Debian Bug Tracking System]

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

> found 977290 0.5.0-1
Bug #977290 [src:ros-class-loader] libclass-loader-dev has a runtime dependency 
on runtime libraries without depending on these
Marked as found in versions ros-class-loader/0.5.0-1.
> thanks
Stopping processing here.

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

Processed: Bug#939658 marked as pending in printrun

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #939658 [src:printrun] printrun: Incomplete debian/copyright?
Added tag(s) pending.

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

Bug#939658: marked as pending in printrun

[Rock Storm]

Control: tag -1 pending

Hello,

Bug #939658 in printrun reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/3dprinting-team/printrun/-/commit/f0248afe80d939c2885586ae1d0229006724de06


d/copyright: Reorganise and update to latest code

Closes: #939658


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/939658

Bug#973222: marked as done (python-smoke-zephyr: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Sun, 13 Dec 2020 18:50:00 +
with message-id 
and subject line Bug#973222: fixed in python-smoke-zephyr 2.0.1-1
has caused the Debian Bug report #973222,
regarding python-smoke-zephyr: FTBFS: dh_auto_test: error: pybuild --test -i 
python{version} -p "3.9 3.8" returned exit code 13
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
973222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973222
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-smoke-zephyr
Version: 2.0.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package python-smoke-zephyr
> dpkg-buildpackage: info: source version 2.0.0-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Samuel Henrique 
> 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:217: python3.9 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.9_smoke-zephyr/build' (and 
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.9' does not exist -- can't clean it
> I: pybuild base:217: python3.8 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.8_smoke-zephyr/build' (and 
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.8' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building python-smoke-zephyr using existing 
> ./python-smoke-zephyr_2.0.0.orig.tar.gz
> dpkg-source: info: building python-smoke-zephyr in 
> python-smoke-zephyr_2.0.0-1.debian.tar.xz
> dpkg-source: info: building python-smoke-zephyr in 
> python-smoke-zephyr_2.0.0-1.dsc
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python3.9 setup.py config 
> running config
> I: pybuild base:217: python3.8 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3.9 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.9_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/configuration.py -> 
> /<>/.pybuild/cpython3_3.9_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/utilities.py -> 
> /<>/.pybuild/cpython3_3.9_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/argparse_types.py -> 
> /<>/.pybuild/cpython3_3.9_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/job.py -> 
> /<>/.pybuild/cpython3_3.9_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/requirements.py -> 
> /<>/.pybuild/cpython3_3.9_smoke-zephyr/build/smoke_zephyr
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.8_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/configuration.py -> 
> /<>/.pybuild/cpython3_3.8_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/utilities.py -> 
> /<>/.pybuild/cpython3_3.8_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/argparse_types.py -> 
> /<>/.pybuild/cpython3_3.8_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/job.py -> 
> /<>/.pybuild/cpython3_3.8_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/requirements.py -> 
> /<>/.pybuild/cpython3_3.8_smoke-zephyr/build/smoke_zephyr
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:217: cd 
> /<>/.pybuild/cpython3_3.9_smoke-zephyr/build; python3.9 -m 
> unittest discover -v -s /<>/tests -p "[a-z]*.py"
> test_bin_b64_type (argparse_types.ArgparseTypeTests) ... ok
> test_bin_hex_type (argparse_types.ArgparseTypeTests) ... ok
> test_dir_type (argparse_types.ArgparseTypeTests) ... ok
> 

Bug#976994: ccls: autopkgtest regression in testing: FAIL: test_response (__main__.TestLSP) [$ccls/info]

[Paul Gevers]

Hi,

On 10-12-2020 15:53, Shengjing Zhu wrote:
> Can we have autopkgtest for migration of binNMU?

Bug #944458

Paul

https://bugs.debian.org/944458



OpenPGP_signature
Description: OpenPGP digital signature

Bug#957468: marked as done (libpsm2: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Sun, 13 Dec 2020 20:02:02 +0200
with message-id 
and subject line Re: Bug#957468: libpsm2: ftbfs with GCC-10
has caused the Debian Bug report #957468,
regarding libpsm2: ftbfs with GCC-10
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
957468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957468
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libpsm2
Version: 11.2.86-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/libpsm2_11.2.86-1_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
/usr/bin/ld: 
/<>/build_release/ptl_ips/ips_proto_am.o:./ptl_ips/./ptl_am/ptl_fwd.h:60:
 multiple definition of `psmi_ptl_amsh'; 
/<>/build_release/ptl_am/am_reqrep_shmem.o:./ptl_am/./ptl_am/ptl_fwd.h:60:
 first defined here
/usr/bin/ld: 
/<>/build_release/ptl_ips/ips_proto_am.o:./ptl_ips/./ptl_ips/ptl_fwd.h:66:
 multiple definition of `psmi_ptl_ips_rcvthread'; 
/<>/build_release/ptl_am/am_reqrep_shmem.o:./ptl_am/./ptl_ips/ptl_fwd.h:66:
 first defined here
/usr/bin/ld: 
/<>/build_release/ptl_ips/ips_proto_am.o:./ptl_ips/./ptl_ips/ptl_fwd.h:64:
 multiple definition of `psmi_ptl_ips'; 
/<>/build_release/ptl_am/am_reqrep_shmem.o:./ptl_am/./ptl_ips/ptl_fwd.h:64:
 first defined here
/usr/bin/ld: 
/<>/build_release/ptl_ips/ips_proto_am.o:./ptl_ips/./ptl_self/ptl_fwd.h:60:
 multiple definition of `psmi_ptl_self'; 
/<>/build_release/ptl_am/am_reqrep_shmem.o:./ptl_am/./ptl_self/ptl_fwd.h:60:
 first defined here
/usr/bin/ld: 
/<>/build_release/ptl_ips/ips_path_rec.o:./ptl_ips/./psm_utils.h:340:
 multiple definition of `psmi_faultinj_enabled'; 
/<>/build_release/ptl_am/am_reqrep_shmem.o:./ptl_am/./psm_utils.h:340:
 first defined here
/usr/bin/ld: 
/<>/build_release/ptl_ips/ips_path_rec.o:./ptl_ips/./psm_utils.h:323:
 multiple definition of `psmi_cpu_model'; 
/<>/build_release/ptl_am/am_reqrep_shmem.o:./ptl_am/./psm_utils.h:323:
 first defined here
/usr/bin/ld: 
/<>/build_release/ptl_ips/ips_path_rec.o:./ptl_ips/./psm_error.h:68:
 multiple definition of `psmi_errhandler_global'; 
/<>/build_release/ptl_am/am_reqrep_shmem.o:./ptl_am/./psm_error.h:68:
 first defined here
/usr/bin/ld: 
/<>/build_release/ptl_ips/ips_path_rec.o:./ptl_ips/./ptl_am/ptl_fwd.h:60:
 multiple definition of `psmi_ptl_amsh'; 
/<>/build_release/ptl_am/am_reqrep_shmem.o:./ptl_am/./ptl_am/ptl_fwd.h:60:
 first defined here
/usr/bin/ld: 
/<>/build_release/ptl_ips/ips_path_rec.o:./ptl_ips/./ptl_ips/ptl_fwd.h:66:
 multiple definition of `psmi_ptl_ips_rcvthread'; 
/<>/build_release/ptl_am/am_reqrep_shmem.o:./ptl_am/./ptl_ips/ptl_fwd.h:66:
 first defined here
/usr/bin/ld: 
/<>/build_release/ptl_ips/ips_path_rec.o:./ptl_ips/./ptl_ips/ptl_fwd.h:64:
 multiple definition of `psmi_ptl_ips'; 
/<>/build_release/ptl_am/am_reqrep_shmem.o:./ptl_am/./ptl_ips/ptl_fwd.h:64:
 first defined here
/usr/bin/ld: 
/<>/build_release/ptl_ips/ips_path_rec.o:./ptl_ips/./ptl_self/ptl_fwd.h:60:
 multiple definition of `psmi_ptl_self'; 
/<>/build_release/ptl_am/am_reqrep_shmem.o:./ptl_am/./ptl_self/ptl_fwd.h:60:
 first defined here
/usr/bin/ld: 
/<>/build_release/ptl_ips/ips_opp_path_rec.o:./ptl_ips/./psm_utils.h:340:
 multiple definition of `psmi_faultinj_enabled'; 
/<>/build_release/ptl_am/am_reqrep_shmem.o:./ptl_am/./psm_utils.h:340:
 first defined here
/usr/bin/ld: 
/<>/build_release/ptl_ips/ips_opp_path_rec.o:./ptl_ips/./psm_utils.h:323:
 multiple definition of `psmi_cpu_model'; 

Bug#976566: opencolorio: FTBFS: Imath.h:13:10: fatal error: OpenEXR/OpenEXRConfig.h: No such file or directory

[John Scott]

To fix this on amd64 it's sufficient to add libopenexr-dev as a build-dep.

signature.asc
Description: This is a digitally signed message part.

Bug#976940: marked as done (golang-refraction-networking-utls: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: cd obj-powerpc64le-linux-gnu && go test -vet=off -v -p 160 github.com/refr

[Debian Bug Tracking System]

Your message dated Sun, 13 Dec 2020 17:48:41 +
with message-id 
and subject line Bug#976940: fixed in golang-refraction-networking-utls 
0.0~git20201210.2179f28-1
has caused the Debian Bug report #976940,
regarding golang-refraction-networking-utls: FTBFS on ppc64el (arch:all-only 
src pkg): dh_auto_test: error: cd obj-powerpc64le-linux-gnu && go test -vet=off 
-v -p 160 github.com/refraction-networking/utls 
github.com/refraction-networking/utls/cpu 
github.com/refraction-networking/utls/testenv returned exit code 1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
976940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976940
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-refraction-networking-utls
Version: 0.0~git20201112.f7e7360-1
Severity: serious
Justification: FTBFS on ppc64el
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el

Hi,

During a rebuild of all packages in sid, your package failed to build
on ppc64el. At the same time, it did not fail on amd64.

I'm marking this bug as severity:serious since your package has only
Architecture:all binary packages, and should thus, in theory, build
everywhere. Failure to build on ppc64el might indicate a serious issue
in this package or in another package.

But feel free to downgrade or close if you believe that this is only a
build-time issue. (I would personnally prefer a severity:minor bug just to
track that the package can only be built on specific architectures.)

Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package golang-refraction-networking-utls
> dpkg-buildpackage: info: source version 0.0~git20201112.f7e7360-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Roger Shimizu 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture ppc64el
>  debian/rules clean
> dh clean --buildsystem=golang --with=golang
>dh_auto_clean -O--buildsystem=golang
>dh_autoreconf_clean -O--buildsystem=golang
>dh_clean -O--buildsystem=golang
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building golang-refraction-networking-utls using existing 
> ./golang-refraction-networking-utls_0.0~git20201112.f7e7360.orig.tar.xz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: building golang-refraction-networking-utls in 
> golang-refraction-networking-utls_0.0~git20201112.f7e7360-1.debian.tar.xz
> dpkg-source: info: building golang-refraction-networking-utls in 
> golang-refraction-networking-utls_0.0~git20201112.f7e7360-1.dsc
>  debian/rules binary
> dh binary --buildsystem=golang --with=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_autoreconf -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   cd obj-powerpc64le-linux-gnu && go install -trimpath -v -p 160 
> github.com/refraction-networking/utls 
> github.com/refraction-networking/utls/cpu 
> github.com/refraction-networking/utls/testenv
> golang.org/x/crypto/cryptobyte/asn1
> golang.org/x/crypto/internal/subtle
> github.com/refraction-networking/utls/cpu
> internal/nettrace
> crypto/internal/subtle
> unicode/utf16
> math/bits
> container/list
> runtime/internal/sys
> internal/unsafeheader
> unicode
> internal/cpu
> crypto/subtle
> vendor/golang.org/x/crypto/cryptobyte/asn1
> unicode/utf8
> internal/race
> sync/atomic
> runtime/internal/atomic
> runtime/cgo
> runtime/internal/math
> math
> internal/bytealg
> internal/testlog
> runtime
> internal/reflectlite
> sync
> internal/singleflight
> math/rand
> errors
> sort
> internal/oserror
> io
> vendor/golang.org/x/net/dns/dnsmessage
> strconv
> syscall
> crypto/internal/randutil
> hash
> bytes
> strings
> crypto/hmac
> golang.org/x/crypto/hkdf
> crypto
> crypto/rc4
> reflect
> bufio
> internal/syscall/execenv
> internal/syscall/unix
> time
> context
> internal/poll
> internal/fmtsort
> encoding/binary
> os
> encoding/base64
> crypto/ed25519/internal/edwards25519
> crypto/sha256
> crypto/sha1
> crypto/sha512
> golang.org/x/crypto/poly1305
> crypto/cipher
> crypto/md5
> golang.org/x/crypto/sha3
> encoding/pem
> crypto/des
> golang.org/x/crypto/chacha20
> crypto/aes
> path/filepath
> runtime/debug
> fmt
> net
> golang.org/x/crypto/chacha20poly1305
> io/ioutil
> os/exec
> encoding/hex
> runtime/trace
> net/url
> golang.org/x/crypto/curve25519
> flag
> 

Processed: severity of 976258 is important

[Debian Bug Tracking System]

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

> severity 976258 important
Bug #976258 [src:linux] linux: hibernation attempt results in shutdown and 
unclean filesystem
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Bug#975818: marked as done (libgtkada: FTBFS: AttributeError: 'xml.etree.ElementTree.Element' object has no attribute 'getchildren')

[Debian Bug Tracking System]

Your message dated Sun, 13 Dec 2020 17:18:37 +
with message-id 
and subject line Bug#975818: fixed in libgtkada 21.0.0.785f3cf4-2
has caused the Debian Bug report #975818,
regarding libgtkada: FTBFS: AttributeError: 'xml.etree.ElementTree.Element' 
object has no attribute 'getchildren'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
975818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975818
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgtkada
Version: 19-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201125 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> rm -f src/generated/*.ad?
> python3 contrib/binding.py \
>--gir-file=contrib/GLib-2.0.gir \
>--gir-file=contrib/GObject-2.0.gir \
>   --gir-file=contrib/Gtk-3.0.gir \
>   --gir-file=contrib/Gdk-3.0.gir \
>   --gir-file=contrib/Pango-1.0.gir \
>   --gir-file=contrib/Gio-2.0.gir \
>   --xml-file=contrib/binding.xml \
>   --ada-output=src/generated/tmp.ada \
>   --c-output=src/misc_generated.c
> no c:type defined for GtkEntryIconAccessible
> Traceback (most recent call last):
>   File "/<>/contrib/binding.py", line 3009, in 
> cl.generate(gir)
>   File "/<>/contrib/binding.py", line 2676, in generate
> extra = self.gtkpkg.extra()
>   File "/<>/contrib/binding_gtkada.py", line 436, in extra
> return extra.getchildren()
> AttributeError: 'xml.etree.ElementTree.Element' object has no attribute 
> 'getchildren'
> make[2]: *** [Makefile:139: generate] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/11/25/libgtkada_19-4_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: libgtkada
Source-Version: 21.0.0.785f3cf4-2
Done: Nicolas Boulenguez 

We believe that the bug you reported is fixed in the latest version of
libgtkada, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 975...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nicolas Boulenguez  (supplier of updated libgtkada package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 13 Dec 2020 16:37:34 +0100
Source: libgtkada
Architecture: source
Version: 21.0.0.785f3cf4-2
Distribution: unstable
Urgency: medium
Maintainer: Ludovic Brenta 
Changed-By: Nicolas Boulenguez 
Closes: 975818 976028
Changes:
 libgtkada (21.0.0.785f3cf4-2) unstable; urgency=medium
 .
   * Reupload to unstable for gnat-10 transition.
 The propagation of a patch updating python2 code closes: #975818.
   * Fix copy/paste error in upstream/metadata.
 .
   [ Simon McVittie  ]
   * Build-depend on libgdk-pixbuf-2.0-dev instead of libgdk-pixbuf2.0-dev.
 Closes: #976028.
Checksums-Sha1:
 ccf03a98b39922fa248b706eac89663d609d24dc 2654 libgtkada_21.0.0.785f3cf4-2.dsc
 e5edee29f63c819b20bdc4693cab252cc7feb9f6 22812 
libgtkada_21.0.0.785f3cf4-2.debian.tar.xz
Checksums-Sha256:
 1f9440a7ac959b95c4b0f5c8df10920721ec6f08f73d74fcaa4b964a327ab994 2654 
libgtkada_21.0.0.785f3cf4-2.dsc
 efd328b3140cbbb315fc1b7fda5c07f69f39e0804297119132d9a21cebe9d75e 22812 
libgtkada_21.0.0.785f3cf4-2.debian.tar.xz
Files:
 5ba200e4cd6635f5209057aa76524842 2654 libdevel optional 
libgtkada_21.0.0.785f3cf4-2.dsc
 dde7000f84dcb465ec8e481bcdfe99e1 22812 libdevel optional 
libgtkada_21.0.0.785f3cf4-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEYtlNMqmXIhEvWffytSqc9EkN/I0FAl/WShkTHG5pY29sYXNA
ZGViaWFuLm9yZwAKCRC1Kpz0SQ38jW8lD/wNYohlvyz2H7FeV68AR3Fz+KB+zI6e
q58C6QZEX5sBr8ruJiJav50TyPLSATia7BE7xo95T1QxOpzsITm+5jUz4kxqdSRl
wWqS+bwls7lM2JMrHdaZS4nqITt72D9GHMLrxlPKi3tKLXBRIhjslscwrfooVCBx

Bug#975129: qwt: FTBFS: qwt_painter_command.h:85:22: error: field ‘clipPath’ has incomplete type ‘QPainterPath’

[Lisandro Damián Nicanor Pérez Meyer]

On Fri, 4 Dec 2020 13:01:53 -0800 tony mancill  wrote:
> On Wed, Nov 25, 2020 at 08:35:48AM +0100, Gudjon I. Gudjonsson wrote:
> > This requires a quite simple fix. I will fix this before the weekend and 
> > then
> > start looking into version 6.1.5.
>
> Hi Gudjon,
>
> Do you mind if I upload an NMU of 6.1.4 for the simple fix?  There are a
> number of r-deps that are going to be removed from testing soon.

Please go ahead, I have been sponsoring QWT and even made the latest
binNMU, and we can't risk this many packages being removed just now.
Ping me if you need help!

Processed: fix package name

[Debian Bug Tracking System]

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

> reassign 977290 src:ros-class-loader
Bug #977290 [src:ros-classloader] libclass-loader-dev has a runtime dependency 
on runtime libraries without depending on these
Warning: Unknown package 'src:ros-classloader'
Bug reassigned from package 'src:ros-classloader' to 'src:ros-class-loader'.
No longer marked as found in versions ros-classloader/0.5.0-1.
Ignoring request to alter fixed versions of bug #977290 to the same values 
previously set
>
End of message, stopping processing here.

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

Bug#977290: libclass-loader-dev has a runtime dependency on runtime libraries without depending on these

[Matthias Klose]

Package: src:ros-classloader
Version: 0.5.0-1
Severity: serious
Tags: sid bullseye

libclass-loader-dev has a runtime dependency on runtime libraries without
depending on these.  This is seen with the current boost transition.

$ cat /usr/lib/x86_64-linux-gnu/pkgconfig/class_loader.pc
prefix=/usr

Name: class_loader
Description: Description of class_loader
Version: 0.5.0
Cflags: -I${prefix}/include
Libs:  -lclass_loader /usr/lib/x86_64-linux-gnu/libboost_thread.so.1.71.0
/usr/lib/x86_64-linux-gnu/libboost_system.so.1.71.0
/usr/lib/x86_64-linux-gnu/libPocoFoundation.so -ldl
/usr/lib/x86_64-linux-gnu/libconsole_bridge.so.0.4
Requires:

If that is really needed, then pluginlib-dev should depend on these runtime
libraries, so that transitions have a chance to identify these dependencies.

Or use pkgconfig files like everybody else:

 - -lboost_thread -lboost_system -lconsole_bridge

Processed: affects 975863

[Debian Bug Tracking System]

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

> affects 975863 src:cpp-hocon
Bug #975863 [leatherman] leatherman: /usr/include/boost/nowide/ are shipped by 
boost_1.74
Added indication that 975863 affects src:cpp-hocon
> thanks
Stopping processing here.

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

Processed: tagging 975863

[Debian Bug Tracking System]

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

> tags 975863 + ftbfs
Bug #975863 [leatherman] leatherman: /usr/include/boost/nowide/ are shipped by 
boost_1.74
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: affects 977222

[Debian Bug Tracking System]

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

> affects 977222 src:mshr
Bug #977222 [src:dolfin] dolfin: FTBFS: error: ‘min_element’ is not a member of 
‘std’; did you mean ‘tuple_element’?
Added indication that 977222 affects src:mshr
> thanks
Stopping processing here.

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

Processed: affects 975863

[Debian Bug Tracking System]

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

> affects 975863 src:slic3r
Bug #975863 [leatherman] leatherman: /usr/include/boost/nowide/ are shipped by 
boost_1.74
Added indication that 975863 affects src:slic3r
> thanks
Stopping processing here.

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

Processed: closing 976495

[Debian Bug Tracking System]

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

> close 976495 1.8.20-6
Bug #976495 [src:doxygen] doxygen: FTBFS: /usr/bin/pdflatex: Not writing to 
../html/examples/group/latex//group__group2.aux (openout_any = p).
Marked as fixed in versions doxygen/1.8.20-6.
Bug #976495 [src:doxygen] doxygen: FTBFS: /usr/bin/pdflatex: Not writing to 
../html/examples/group/latex//group__group2.aux (openout_any = p).
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#977269: [Pkg-javascript-devel] Bug#977269: node-rollup-plugin-terser seems incompatible with current node-terser

[Jonas Smedegaard]

Quoting Xavier Guimard (2020-12-13 13:19:47)
> Package: node-rollup-plugin-terser
> Version: 7.0.2-2
> Severity: grave
> Justification: renders package unusable
> 
> When trying current rollup-plugin-terser (7.0.2)  with current
> node-terser (4.1.2), package is unuseable:
> 
> $ rollup -c
> 
> index.js → dist/pako.js, dist/pako.min.js...
> [!] (plugin terser) Error: Cannot find module 
> '/home/xavier/dev/debian/src/pkg-js/packages/node-pako/node_modules/terser/dist/bundle.min.js'.
>  Please verify that the package.json has a valid "main" entry

Neither node-rollup-plugin-terser nor node-terser asks for files below 
/home/xavier - please try locate which code did that.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#976907: golang-github-boltdb-bolt: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: cd obj-powerpc64le-linux-gnu && go test -vet=off -v -p 160 -short github.com/boltdb/bolt github.co

[Nilesh Patra]

Hi Andreas,

On Sat, 12 Dec 2020 18:48:52 +0100 Andreas Henriksson  wrote:
> Hello again,
>
> So after wasting my time here I finally realized that apparently
> boltdb is archived upstream. It will not receive any fixes.
>
> Apparently golang-github-coreos-bbolt is a maintained feature-extended
> fork. We should likely encurage moving to that and get boltdb removed
> from debian.
>
> The timeout waiting for db.mmaplock that occurred in boltdb is
> apparently already fixed in bbolt, see:
> https://github.com/etcd-io/bbolt/commit/e06ec0a754bc30c2e17ad871962e71635bf94d45
>
> The pagesize issue seems to plague them both still though.
>
> See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976926
> for the bug report against bbolt.

Thanks a lot for investigating! The problem with removing this 'right now' is 
that there are a few (important) reverse-dependencies and reverse-build-deps 
that this package has.

$ reverse-depends golang-github-boltdb-bolt-dev  
Reverse-Depends
* golang-github-blevesearch-bleve-dev
* golang-github-hashicorp-nomad-dev
* golang-github-hashicorp-raft-boltdb-dev
* golang-github-influxdb-influxdb-dev


$ reverse-depends golang-github-boltdb-bolt-dev -b
Reverse-Testsuite-Triggers
* snapd

Reverse-Build-Depends
* docker-libkv
* etcd
* go-dep
* golang-github-blevesearch-bleve
* golang-github-hashicorp-raft-boltdb
* influxdb
* nomad
* snapd
* vuls

Can simply replacing the dependency in all of them with bbolt work?
This may also need upstream patching in the future.
Please let me know

Kind Regards,
Nilesh



signature.asc
Description: OpenPGP digital signature

Bug#964204: marked as done (nbsphinx: FTBFS without internet access)

[Debian Bug Tracking System]

Your message dated Sun, 13 Dec 2020 15:10:33 +
with message-id 
and subject line Bug#964204: fixed in nbsphinx 0.8.0+ds-1
has caused the Debian Bug report #964204,
regarding nbsphinx: FTBFS without internet access
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
964204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964204
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nbsphinx
Version: 0.4.3+ds-1
Severity: serious
Tags: ftbfs

This package fails to build on a system without internet access.

>From the build log:

  Notebook error:
  CellExecutionError in code-cells.ipynb:
  --
  Image(url='https://www.python.org/static/img/python-logo-large.png', 
embed=True)
  --

  [...]

  URLError: 
  
  You can ignore this error by setting the following in conf.py:
  
  nbsphinx_allow_errors = True
  
  make[1]: *** [debian/rules:20: override_dh_sphinxdoc] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:13: binary] Error 2

-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: nbsphinx
Source-Version: 0.8.0+ds-1
Done: Jerome Benoit 

We believe that the bug you reported is fixed in the latest version of
nbsphinx, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 964...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jerome Benoit  (supplier of updated nbsphinx package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 13 Dec 2020 14:31:40 +
Source: nbsphinx
Architecture: source
Version: 0.8.0+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Jerome Benoit 
Closes: 964204
Changes:
 nbsphinx (0.8.0+ds-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Jerome Benoit ]
   * New upstream minor version.
   * Debianization: WIP: depends on recent version of python3-ipywidgets
 - d/copyright:
   - copyright year tuples, update;
 - d/control:
   - debhelper, bump to version 13 (no change);
   - Standards-Version, bump to version 4.5.1 (no change);
   - Build-Depends-Indep, update;
   - python-nbsphinx-doc, Built-Using field, introduce;
 - d/rules:
   - NBSPHINX_VERSION_RELEASE variable, harden;
 - d/patches/*:
   - d/p/upstream-missing-references_bib.patch , obsoleted;
   - d/p/debianization-documentation.patch:
 - doc/conf.py, nbsphinx_allow_errors set to True (Closes: #964204);
 - refresh;
 - d/tests/control, refresh;
 - d/{python3-nbsphinx,python-nbsphinx-doc}.lintian-overrides, discard
   (no-upstream-changelog tag now unknown).
Checksums-Sha1:
 220e913fc9753ea2dbfb1c82346656b1abc3f413 3641 nbsphinx_0.8.0+ds-1.dsc
 d8352d9ed065b7a8590b5293c9f1fe6c3e244250 115312 nbsphinx_0.8.0+ds.orig.tar.xz
 73808baba473e4a96c5e76b39917f09a88c9da1a 762512 
nbsphinx_0.8.0+ds-1.debian.tar.xz
 a8e61d7b7005a67c3261387e995fc4e171774092 6639 
nbsphinx_0.8.0+ds-1_source.buildinfo
Checksums-Sha256:
 2c97970c1a18f7a93b99f62843cc534b4cef36df1079c56b943a2785696887bc 3641 
nbsphinx_0.8.0+ds-1.dsc
 e474bb770f296d7682afa820f6312075c06e8ebcb248aa81807a41cd139e4335 115312 
nbsphinx_0.8.0+ds.orig.tar.xz
 678454c4f034d965f747241f6f6643367970cb12dddbccf12c8797f5489812af 762512 
nbsphinx_0.8.0+ds-1.debian.tar.xz
 1f81d7a509c0dce7f16db8086dc6fe0129abd84eb64fe640617ad58cb58d795c 6639 
nbsphinx_0.8.0+ds-1_source.buildinfo
Files:
 84c628e2dafd74541f56a6e0ff6db601 3641 python optional nbsphinx_0.8.0+ds-1.dsc
 e630cad4b2f724e2145310051ad6d5c0 115312 python optional 
nbsphinx_0.8.0+ds.orig.tar.xz
 70060fac58cad5f99abb519a1d3d9b0d 762512 python optional 
nbsphinx_0.8.0+ds-1.debian.tar.xz
 b59ee321521adc57712f64a5bb7f6062 6639 python optional 
nbsphinx_0.8.0+ds-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQRJBAEBCgAzFiEEriiuFXEN/x2H5adiP5IZpn82xosFAl/WJq4VHGNhbGN1bHVz
QHJlem96ZXIubmV0AAoJED+SGaZ/NsaLRt0f/jnvxxX0/t6KfeHAyA7yxkG8acSL

Bug#976818: marked as done (glade: FTBFS: ERROR: Dependency "python-3.8-embed" not found)

[Debian Bug Tracking System]

Your message dated Sun, 13 Dec 2020 15:08:48 +
with message-id 
and subject line Bug#976818: fixed in glade 3.38.2-1
has caused the Debian Bug report #976818,
regarding glade: FTBFS: ERROR: Dependency "python-3.8-embed" not found
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
976818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976818
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glade
Version: 3.38.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

glade/experimental started to FTBFS with the ongoing removal of python3.8:

[...]
Determining dependency 'python-3.8-embed' with pkg-config executable 
'/usr/bin/pkg-config'
PKG_CONFIG_PATH: 
Called `/usr/bin/pkg-config --modversion python-3.8-embed` -> 1

CMake binary for MachineChoice.BUILD is not cached
None of 'CMAKE' are defined in the environment, not changing global flags.
CMake binary missing from cross or native file, or env var undefined.
Trying a default CMake fallback at cmake
Did not find CMake 'cmake'
Found CMake: NO
No CMake binary for machine 0 not found. Giving up.
Run-time dependency python-3.8-embed found: NO (tried pkgconfig)

../meson.build:153:2: ERROR: Dependency "python-3.8-embed" not found, tried 
pkgconfig
dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
--localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dauto_features=enabled 
-Dgtk_doc=true returned exit code 1
make[1]: *** [debian/rules:21: override_dh_auto_configure] Error 25


Andreas


glade_3.38.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: glade
Source-Version: 3.38.2-1
Done: Laurent Bigonville 

We believe that the bug you reported is fixed in the latest version of
glade, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 976...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated glade package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 13 Dec 2020 15:45:17 +0100
Source: glade
Architecture: source
Version: 3.38.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Laurent Bigonville 
Closes: 973648 976818
Changes:
 glade (3.38.2-1) unstable; urgency=medium
 .
   * New upstream release
 - Fix FTBFS with python >= 3.9 (Closes: #976818)
   * debian/control.in: Add Breaks/Replaces against libgladeui-2-6 (Closes: 
#973648)
   * debian/libgladeui-2-13.symbols: Add Build-Depends-Package field
Checksums-Sha1:
 6878a9250bf7d57a011b70d81166b56a8c6e4186 2512 glade_3.38.2-1.dsc
 d433fb5085c8f07d559f5a310be31238c1fdf36e 2709224 glade_3.38.2.orig.tar.xz
 d98cab4a7a97a1617be70ce9945fa3839a0be652 24276 glade_3.38.2-1.debian.tar.xz
 c9ab13181c7f2865200c8d0dcd77d9afa051a4d3 14504 glade_3.38.2-1_source.buildinfo
Checksums-Sha256:
 75fb0c57090d0fdf10c83a2c65f1aeb2f2acbd44f1261b5ea16d09e13210bcc1 2512 
glade_3.38.2-1.dsc
 98fc87647d88505c97dd2f30f2db2d3e9527515b3af11694787d62a8d28fbab7 2709224 
glade_3.38.2.orig.tar.xz
 6152f5a5a3d6facae32988b1a0b13c4e514dd6aa7175b66807a6ba44bee1fa3a 24276 
glade_3.38.2-1.debian.tar.xz
 7cb0f38d923c4ef13f2bbe6d80a165f82ddd073f07384bee0e8aeaf9850d2f02 14504 
glade_3.38.2-1_source.buildinfo
Files:
 3f3ead760c4843c62216ce7937998576 2512 gnome optional glade_3.38.2-1.dsc
 f1ac9d9b6404308efb74adc548289455 2709224 gnome optional 
glade_3.38.2.orig.tar.xz
 743a8379156f56704b8d09056325a87b 24276 gnome optional 
glade_3.38.2-1.debian.tar.xz
 760bde5aeeb4a0647d27caf0ab46977b 14504 gnome optional 
glade_3.38.2-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFFBAEBCAAvFiEEmRrdqQAhuF2x31DwH8WJHrqwQ9UFAl/WKTERHGJpZ29uQGRl
Ymlhbi5vcmcACgkQH8WJHrqwQ9W2sQf/Zbl180uqSSr75jQh33y9+DDuAy7FMz+I
gAcARg6EwxoTflw6acyIif51DincyxKrp3XqYK1X9kF1dsTOlp49+S/bB+Eln5SQ
5pAgJRZLJgLEIGzYbNpcTTRh/xvAWrVwLMABeaKgOMz/ZKcFKRoqulyWmLT2oiJO
8ttmfIUQC7mhi291XGAu4ZUe/5hfZimrVGGFKan+jNikBrtXYoLrbdT9Yg4JPtQh
LzdgK25OBa+pszDRaR7zIZcTOSNzBVs82YXDb+V+j3mJeRoghNUMwzjM+bUdWCXm

Bug#973648: marked as done (libgladeui-2-13: missing Breaks+Replaces: libgladeui-2-6)

[Debian Bug Tracking System]

Your message dated Sun, 13 Dec 2020 15:08:48 +
with message-id 
and subject line Bug#973648: fixed in glade 3.38.2-1
has caused the Debian Bug report #973648,
regarding libgladeui-2-13: missing Breaks+Replaces: libgladeui-2-6
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
973648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973648
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgladeui-2-13
Version: 3.38.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../libgladeui-2-13_3.38.1-1_amd64.deb ...
  Unpacking libgladeui-2-13:amd64 (3.38.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libgladeui-2-13_3.38.1-1_amd64.deb (--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/glade/modules/libgladegtk.so', which is also in 
package libgladeui-2-6:amd64 3.22.2-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libgladeui-2-13_3.38.1-1_amd64.deb


cheers,

Andreas


libgladeui-2-6=3.22.2-2_libgladeui-2-13=3.38.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: glade
Source-Version: 3.38.2-1
Done: Laurent Bigonville 

We believe that the bug you reported is fixed in the latest version of
glade, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 973...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated glade package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 13 Dec 2020 15:45:17 +0100
Source: glade
Architecture: source
Version: 3.38.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Laurent Bigonville 
Closes: 973648 976818
Changes:
 glade (3.38.2-1) unstable; urgency=medium
 .
   * New upstream release
 - Fix FTBFS with python >= 3.9 (Closes: #976818)
   * debian/control.in: Add Breaks/Replaces against libgladeui-2-6 (Closes: 
#973648)
   * debian/libgladeui-2-13.symbols: Add Build-Depends-Package field
Checksums-Sha1:
 6878a9250bf7d57a011b70d81166b56a8c6e4186 2512 glade_3.38.2-1.dsc
 d433fb5085c8f07d559f5a310be31238c1fdf36e 2709224 glade_3.38.2.orig.tar.xz
 d98cab4a7a97a1617be70ce9945fa3839a0be652 24276 glade_3.38.2-1.debian.tar.xz
 c9ab13181c7f2865200c8d0dcd77d9afa051a4d3 14504 glade_3.38.2-1_source.buildinfo
Checksums-Sha256:
 75fb0c57090d0fdf10c83a2c65f1aeb2f2acbd44f1261b5ea16d09e13210bcc1 2512 
glade_3.38.2-1.dsc
 98fc87647d88505c97dd2f30f2db2d3e9527515b3af11694787d62a8d28fbab7 2709224 
glade_3.38.2.orig.tar.xz
 6152f5a5a3d6facae32988b1a0b13c4e514dd6aa7175b66807a6ba44bee1fa3a 24276 
glade_3.38.2-1.debian.tar.xz
 7cb0f38d923c4ef13f2bbe6d80a165f82ddd073f07384bee0e8aeaf9850d2f02 14504 
glade_3.38.2-1_source.buildinfo
Files:
 3f3ead760c4843c62216ce7937998576 2512 gnome optional glade_3.38.2-1.dsc
 f1ac9d9b6404308efb74adc548289455 2709224 gnome optional 
glade_3.38.2.orig.tar.xz
 743a8379156f56704b8d09056325a87b 24276 gnome optional 
glade_3.38.2-1.debian.tar.xz
 760bde5aeeb4a0647d27caf0ab46977b 14504 gnome optional 
glade_3.38.2-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFFBAEBCAAvFiEEmRrdqQAhuF2x31DwH8WJHrqwQ9UFAl/WKTERHGJpZ29uQGRl
Ymlhbi5vcmcACgkQH8WJHrqwQ9W2sQf/Zbl180uqSSr75jQh33y9+DDuAy7FMz+I
gAcARg6EwxoTflw6acyIif51DincyxKrp3XqYK1X9kF1dsTOlp49+S/bB+Eln5SQ
5pAgJRZLJgLEIGzYbNpcTTRh/xvAWrVwLMABeaKgOMz/ZKcFKRoqulyWmLT2oiJO
8ttmfIUQC7mhi291XGAu4ZUe/5hfZimrVGGFKan+jNikBrtXYoLrbdT9Yg4JPtQh
LzdgK25OBa+pszDRaR7zIZcTOSNzBVs82YXDb+V+j3mJeRoghNUMwzjM+bUdWCXm
7pN/97Xg5BliQD+JNTVrVD1CxW/kYerJH5NTTE7ztN+pZ6REZleCBA==
=zQxo
-END PGP 

Bug#977283: pluginlib-dev has a runtime dependency on runtime libraries without depending on these

[Matthias Klose]

Package: src:ros-pluginlib
Version: 1.13.0-1
Severity: serious
Tags: sid bullseye

pluginlib-dev has a runtime dependency on runtime libraries without depending on
these.  This is seen with the current boost transition.

$ cat /usr/lib/x86_64-linux-gnu/pkgconfig/pluginlib.pc
prefix=/usr

Name: pluginlib
Description: Description of pluginlib
Version: 1.13.0
Cflags: -I${prefix}/include
Libs:  /usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.71.0
/usr/lib/x86_64-linux-gnu/libtinyxml2.so
Requires: class_loader rosconsole roslib


If that is really needed, then pluginlib-dev should depend on these runtime
libraries, so that transitions have a chance to identify these dependencies.

Or use pkgconfig files like everybody else:

 - -lboost_filesystem -ltinyxml2

Bug#977282: libroscpp-core-dev has a runtime dependency on runtime libraries without depending on these

[Matthias Klose]

Package: src:ros-roscpp-core
Version: 0.7.2-4
Severity: serious
Tags: sid bullseye

libroscpp-core-dev has a runtime dependency on runtime libraries without
depending on these.  This is seen with the current boost transition.

$ cat /usr/lib/x86_64-linux-gnu/pkgconfig/cpp_common.pc
prefix=/usr

Name: cpp_common
Description: Description of cpp_common
Version: 0.7.2
Cflags: -I${prefix}/include
Libs:  -lcpp_common /usr/lib/x86_64-linux-gnu/libboost_system.so.1.74.0
/usr/lib/x86_64-linux-gnu/libboost_thread.so.1.74.0
/usr/lib/x86_64-linux-gnu/libconsole_bridge.so.0.4
Requires:

$ cat /usr/lib/x86_64-linux-gnu/pkgconfig/rostime.pc
prefix=/usr

Name: rostime
Description: Description of rostime
Version: 0.7.2
Cflags: -I${prefix}/include
Libs:  -lrostime /usr/lib/x86_64-linux-gnu/libboost_date_time.so.1.74.0
/usr/lib/x86_64-linux-gnu/libboost_system.so.1.74.0
/usr/lib/x86_64-linux-gnu/libboost_thread.so.1.74.0
Requires: cpp_common

If that is really needed, then libroscpp-core-dev should depend on these runtime
libraries, so that transitions have a chance to identify these dependencies.

Or use pkgconfig files like everybody else:

 - -lboost_system -lboost_thread
 - -lboost_date_time -lboost_system


I'm only filing this for ros-roscpp-core and ros-pluginlib, however the whole
ros stack should be checked for similar issues.

Processed: Re: Bug#977109: ruby-licensee, autopkgtest failure with ruby-rugged 1.1.0

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + ftbfs
Bug #977109 [ruby-licensee] ruby-licensee, autopkgtest failure with ruby-rugged 
1.1.0
Added tag(s) ftbfs.

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

Bug#977109: ruby-licensee, autopkgtest failure with ruby-rugged 1.1.0

[Sebastian Ramacher]

Control: tags -1 + ftbfs

On 2020-12-10 23:01:05 +, peter green wrote:
> package: ruby-licensee
> Version: 8.9.2-1
> Severity: serious
> Tags: bullseye, sid
> 
> The autopkgtest for ruby-licensee is failing with ruby-rugged 1.1.0.
> 
> > GEM_PATH= ruby2.7 -e gem\ \"licensee\"
> > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1398:in `rescue in 
> > block in activate_dependencies': Could not find 'rugged' (~> 0.24) among 92 
> > total gem(s) (Gem::MissingSpecError)
> > Checked in 
> > 'GEM_PATH=/home/debci/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0'
> >  at: 
> > /usr/share/rubygems-integration/all/specifications/licensee-8.9.2.gemspec, 
> > execute `gem env` for more information
> > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1395:in `block 
> > in activate_dependencies'
> > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1384:in `each'
> > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1384:in 
> > `activate_dependencies'
> > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1366:in 
> > `activate'
> > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> > `block in gem'
> > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> > `synchronize'
> > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> > `gem'
> > from -e:1:in `'
> > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:309:in `to_specs': Could 
> > not find 'rugged' (~> 0.24) - did find: [rugged-1.1.0] 
> > (Gem::MissingSpecVersionError)
> > Checked in 
> > 'GEM_PATH=/home/debci/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0'
> >  , execute `gem env` for more information
> > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1396:in `block 
> > in activate_dependencies'
> > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1384:in `each'
> > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1384:in 
> > `activate_dependencies'
> > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1366:in 
> > `activate'
> > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> > `block in gem'
> > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> > `synchronize'
> > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> > `gem'
> > from -e:1:in `'
> 
> 
> This is blocking ruby-rugged 1.1.0 (which is needed for the libgit2 
> transition) from migrating to
> testing.

And it also fails to build with the same issue.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#977279: ploop FTBFS on armhf, i386: error: ‘%s’ directive output may be truncated writing between 2 and 2147483645 bytes into a region of size 4083

[Helmut Grohne]

Source: ploop
Version: 1.15-9
Severity: serious
Tags: ftbfs

ploop fails to build from source on armhf and i386 (presumably 32bit
architectures in general):

reproducible builds i386:
https://tests.reproducible-builds.org/debian/rbuild/unstable/i386/ploop_1.15-9.rbuild.log.gz
| delta_sysfs.c: In function 'dev_num2dev_start':
| delta_sysfs.c:304:51: error: '%s' directive output may be truncated writing 
between 2 and 2147483645 bytes into a region of size 4083 
[-Werror=format-truncation=]
|   304 |   snprintf(nbuf, sizeof(nbuf) - 1, "/sys/block/%s/%s",
|   |   ^~
| In file included from /usr/include/stdio.h:867,
|  from delta_sysfs.c:19:
| /usr/include/i386-linux-gnu/bits/stdio2.h:67:10: note: 
'__builtin___snprintf_chk' output 15 or more bytes (assuming 2147483658) into a 
destination of size 4095
|67 |   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
|   |  ^~~~
|68 |__bos (__s), __fmt, __va_arg_pack ());
|   |~
| cc1: all warnings being treated as errors

reproducible builds armhf:
https://tests.reproducible-builds.org/debian/rbuild/unstable/armhf/ploop_1.15-9.rbuild.log.gz

crossqa armhf:
http://crossqa.debian.net/build/ploop_1.15-9_armhf_20201011140323.log

A local cross build for armel has exactly the same symptom.

Helmut

Bug#977278: kaddressbook FTBFS: error: no matching function for call to ‘QPrinter::setPageMargins(int, int, int, int, QPrinter::Unit)’

[Helmut Grohne]

Source: kaddressbook
Version: 4:20.08.2-3
Severity: serious
Tags: ftbfs

kaddressbook fails to build from source on amd64 in unstable. A build
ends with:

| [ 35%] Building CXX object 
src/CMakeFiles/kaddressbookprivate.dir/printing/mike/mikesstyle.cpp.o
| cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ -DHAVE_QGPGME 
-DKCOREADDONS_LIB -DKF_DEPRECATED_WARNINGS_SINCE=0x06 
-DKF_DISABLE_DEPRECATED_BEFORE_AND_AT=0x054800 -DQT_CONCURRENT_LIB 
-DQT_CORE_LIB -DQT_DBUS_LIB -DQT_DEPRECATED_WARNINGS_SINCE=0x06 
-DQT_DISABLE_DEPRECATED_BEFORE=0x050f00 -DQT_GUI_LIB -DQT_NETWORK_LIB 
-DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_FROM_BYTEARRAY -DQT_NO_CAST_TO_ASCII 
-DQT_NO_DEBUG -DQT_NO_FOREACH -DQT_NO_KEYWORDS 
-DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_NO_SIGNALS_SLOTS_KEYWORDS 
-DQT_NO_URL_CAST_FROM_STRING -DQT_PRINTSUPPORT_LIB -DQT_STRICT_ITERATORS 
-DQT_USE_QSTRINGBUILDER -DQT_WIDGETS_LIB -DQT_XML_LIB 
-DTRANSLATION_DOMAIN=\"kaddressbook\" -DWITH_KUSERFEEDBACK -D_GNU_SOURCE 
-D_LARGEFILE64_SOURCE -Dkaddressbookprivate_EXPORTS 
-I/<>/obj-x86_64-linux-gnu/src -I/<>/src 
-I/<>/obj-x86_64-linux-gnu/src/kaddressbookprivate_autogen/include 
-I/<> -I/<>/obj-x86_64-linux-gnu 
-I/<>/src/printing -isystem /usr/include/KF5/PimCommonAkonadi 
-isystem /usr/include/KF5/pimcommonakonadi -isystem /usr/include/KF5 -isystem 
/usr/include/KF5/PimCommon -isystem /usr/include/KF5/pimcommon -isystem 
/usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
/usr/include/KF5/KIOCore -isystem /usr/include/KF5/KCoreAddons -isystem 
/usr/include/KF5/KService -isystem /usr/include/KF5/KConfigCore -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem 
/usr/include/KF5/KConfigWidgets -isystem /usr/include/KF5/KCodecs -isystem 
/usr/include/KF5/KWidgetsAddons -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include/KF5/KConfigGui 
-isystem /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
/usr/include/KF5/KAuth -isystem /usr/include/KF5/AkonadiCore -isystem 
/usr/include/KF5/KItemModels -isystem /usr/include/KF5/AkonadiWidgets -isystem 
/usr/include/KF5/KContacts -isystem /usr/include/KF5/Akonadi/Contact -isystem 
/usr/include/KF5/akonadi/contact -isystem /usr/include/KF5/KIMAP -isystem 
/usr/include/KF5/KMime -isystem /usr/include/KF5/Libkdepim -isystem 
/usr/include/KF5/libkdepim -isystem /usr/include/KF5/KaddressbookGrantlee 
-isystem /usr/include/KF5/kaddressbookgrantlee -isystem 
/usr/include/KF5/GrantleeTheme -isystem /usr/include/KF5/grantleetheme -isystem 
/usr/include/KF5/KCMUtils -isystem /usr/include/KF5/KCompletion -isystem 
/usr/include/KF5/KXmlGui -isystem /usr/include/KF5/KJobWidgets -isystem 
/usr/include/KF5/KIOWidgets -isystem /usr/include/KF5/KIOGui -isystem 
/usr/include/KF5/KWindowSystem -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -isystem 
/usr/include/KF5/AkonadiSearch -isystem /usr/include/KF5/KI18n -isystem 
/usr/include/KF5/KAddressBookImportExport -isystem 
/usr/include/KF5/kaddressbookimportexport -isystem /usr/include/KF5/prison 
-isystem /usr/include/KUserFeedback -isystem /usr/include/qgpgme -isystem 
/usr/include/gpgme++ -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fno-operator-names -fno-exceptions -Wall -Wextra 
-Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith 
-Wundef -Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type -Wvla 
-Wdate-time -Wsuggest-override -Wlogical-op -pedantic 
-Wzero-as-null-pointer-constant -fPIC -fvisibility=hidden 
-fvisibility-inlines-hidden -fPIC -fexceptions -std=gnu++14 -o 
CMakeFiles/kaddressbookprivate.dir/printing/mike/mikesstyle.cpp.o -c 
/<>/src/printing/mike/mikesstyle.cpp
| /<>/src/printing/mike/mikesstyle.cpp: In member function 
‘virtual void KABPrinting::MikesStyle::print(const List&, 
KABPrinting::PrintProgress*)’:
| /<>/src/printing/mike/mikesstyle.cpp:126:66: error: no matching 
function for call to ‘QPrinter::setPageMargins(int, int, int, int, 
QPrinter::Unit)’
|   126 | printer->setPageMargins(20, 20, 20, 20, QPrinter::DevicePixel);
|   |  ^
| In file included from 
/usr/include/x86_64-linux-gnu/qt5/QtPrintSupport/qprinter.h:46,
|  from 
/usr/include/x86_64-linux-gnu/qt5/QtPrintSupport/QPrinter:1,
|  from /<>/src/printing/mike/mikesstyle.cpp:36:
| /usr/include/x86_64-linux-gnu/qt5/QtGui/qpagedpaintdevice.h:224:10: note: 
candidate: ‘bool QPagedPaintDevice::setPageMargins(const QMarginsF&, 
QPageLayout::Unit)’
|   224 | bool setPageMargins(const QMarginsF , QPageLayout::Unit 
units);
|   |  ^~
| 

Bug#977277: libkf5calendarsupport FTBFS: error: ‘class QPrinter’ has no member named ‘orientation’

[Helmut Grohne]

Source: libkf5calendarsupport
Version: 4:20.08.2-2
Severity: serious
Tags: ftbfs

libkf5calendarsupport fails to build from source on amd64 in unstable. A
build ends with:

| [ 54%] Building CXX object 
src/CMakeFiles/KF5CalendarSupport.dir/printing/calprintpluginbase.cpp.o
| cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ 
-DKCOREADDONS_LIB -DKCalCore=KCalendarCore -DKF5CalendarSupport_EXPORTS 
-DKF_DEPRECATED_WARNINGS_SINCE=0x06 
-DKF_DISABLE_DEPRECATED_BEFORE_AND_AT=0x054600 -DKGUIADDONS_LIB 
-DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_DBUS_LIB 
-DQT_DEPRECATED_WARNINGS_SINCE=0x06 -DQT_DISABLE_DEPRECATED_BEFORE=0x050f00 
-DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_CAST_FROM_ASCII 
-DQT_NO_CAST_FROM_BYTEARRAY -DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_NO_FOREACH 
-DQT_NO_KEYWORDS -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT 
-DQT_NO_SIGNALS_SLOTS_KEYWORDS -DQT_NO_URL_CAST_FROM_STRING 
-DQT_PRINTSUPPORT_LIB -DQT_STRICT_ITERATORS -DQT_USE_QSTRINGBUILDER 
-DQT_WIDGETS_LIB -DQT_XML_LIB -DTRANSLATION_DOMAIN=\"calendarsupport\" 
-D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I/<>/obj-x86_64-linux-gnu/src 
-I/<>/src 
-I/<>/obj-x86_64-linux-gnu/src/KF5CalendarSupport_autogen/include 
-isystem /usr/include/KF5/KMime -isystem /usr/include/KF5 -isystem 
/usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
/usr/include/KF5/KIdentityManagement -isystem 
/usr/include/KF5/KIdentityManagement/kidentitymanagement -isystem 
/usr/include/KF5/KCoreAddons -isystem /usr/include/KF5/KPIMTextEdit -isystem 
/usr/include/KF5/Akonadi/Calendar -isystem /usr/include/KF5/akonadi/calendar 
-isystem /usr/include/KF5/AkonadiCore -isystem /usr/include/KF5/KItemModels 
-isystem /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/KF5/KCalendarCore -isystem /usr/include/KF5/KWidgetsAddons 
-isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/KF5/KI18n -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -isystem 
/usr/include/KF5/KCompletion -isystem /usr/include/KF5/KIOWidgets -isystem 
/usr/include/KF5/KIOGui -isystem /usr/include/KF5/KIOCore -isystem 
/usr/include/KF5/KService -isystem /usr/include/KF5/KConfigCore -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem 
/usr/include/KF5/KWindowSystem -isystem /usr/include/KF5/KJobWidgets -isystem 
/usr/include/KF5/KGuiAddons -isystem /usr/include/KF5/AkonadiWidgets -isystem 
/usr/include/KF5/KConfigWidgets -isystem /usr/include/KF5/KCodecs -isystem 
/usr/include/KF5/KConfigGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtXml 
-isystem /usr/include/KF5/KAuth -isystem /usr/include/KF5/Akonadi/Notes 
-isystem /usr/include/KF5/akonadi/notes -isystem /usr/include/KF5/KHolidays 
-isystem /usr/include/KF5/KCalUtils -isystem 
/usr/include/KF5/KCalUtils/kcalutils -isystem /usr/include/KF5/PimCommon 
-isystem /usr/include/KF5/pimcommon -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fno-operator-names 
-fno-exceptions -Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security 
-Wno-long-long -Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual 
-Werror=return-type -Wvla -Wdate-time -Wsuggest-override -Wlogical-op -pedantic 
-Wzero-as-null-pointer-constant -fPIC -fvisibility=hidden 
-fvisibility-inlines-hidden -fPIC -fexceptions -std=gnu++14 -o 
CMakeFiles/KF5CalendarSupport.dir/printing/calprintpluginbase.cpp.o -c 
/<>/src/printing/calprintpluginbase.cpp
| /<>/src/printing/calprintpluginbase.cpp: In member function 
‘QPrinter::Orientation CalendarSupport::CalPrintPluginBase::orientation() 
const’:
| /<>/src/printing/calprintpluginbase.cpp:253:33: error: ‘class 
QPrinter’ has no member named ‘orientation’; did you mean ‘Orientation’?
|   253 | return mPrinter ? mPrinter->orientation() : QPrinter::Portrait;
|   | ^~~
|   | Orientation
| make[3]: *** [src/CMakeFiles/KF5CalendarSupport.dir/build.make:382: 
src/CMakeFiles/KF5CalendarSupport.dir/printing/calprintpluginbase.cpp.o] Error 1
| make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| make[2]: *** [CMakeFiles/Makefile2:949: 
src/CMakeFiles/KF5CalendarSupport.dir/all] Error 2
| make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| make[1]: *** [Makefile:163: all] Error 2
| make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| dh_auto_build: error: cd obj-x86_64-linux-gnu && make -j1 "INSTALL=install 
--strip-program=true" VERBOSE=1 returned exit code 2
| make: *** [debian/rules:11: binary] Error 25
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2

Helmut

Bug#977108: ruby-gollum-rugged-adapter, autopkgtest failure with ruby-rugged 1.1.0

[Sebastian Ramacher]

Control: tags -1 + ftbfs

On 2020-12-10 22:57:26 +, peter green wrote:
> package: ruby-gollum-rugged-apapter
> Version: 0.4.4.2-2
> Severity: serious
> 
> The autopkgtest for ruby-gollum-rugged-adapter is failing with ruby-rugged 
> 1.1.0.
> 
> > ┌──┐
> > │ Checking Rubygems dependency resolution on ruby2.7
> >│
> > └──┘
> > 
> > GEM_PATH= ruby2.7 -e gem\ \"gitlab-gollum-rugged_adapter\"
> > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1398:in `rescue in 
> > block in activate_dependencies': Could not find 'rugged' (~> 0.25) among 60 
> > total gem(s) (Gem::MissingSpecError)
> > Checked in 
> > 'GEM_PATH=/home/debci/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0'
> >  at: 
> > /usr/share/rubygems-integration/all/specifications/gitlab-gollum-rugged_adapter-0.4.4.2.gemspec,
> >  execute `gem env` for more information
> > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1395:in `block 
> > in activate_dependencies'
> > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1384:in `each'
> > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1384:in 
> > `activate_dependencies'
> > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1366:in 
> > `activate'
> > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> > `block in gem'
> > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> > `synchronize'
> > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> > `gem'
> > from -e:1:in `'
> > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:309:in `to_specs': Could 
> > not find 'rugged' (~> 0.25) - did find: [rugged-1.1.0] 
> > (Gem::MissingSpecVersionError)
> > Checked in 
> > 'GEM_PATH=/home/debci/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0'
> >  , execute `gem env` for more information
> > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1396:in `block 
> > in activate_dependencies'
> > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1384:in `each'
> > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1384:in 
> > `activate_dependencies'
> > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1366:in 
> > `activate'
> > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> > `block in gem'
> > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> > `synchronize'
> > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> > `gem'
> > from -e:1:in `'
> 
> This is blocking ruby-rugged 1.1.0 (which is needed for the libgit2 
> transition) from migrating to
> testing.

And ruby-gollum-rugged-adapter fails to build with the same issues.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Processed: Re: Bug#977108: ruby-gollum-rugged-adapter, autopkgtest failure with ruby-rugged 1.1.0

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + ftbfs
Bug #977108 [ruby-gollum-rugged-adapter] ruby-gollum-rugged-adapter, 
autopkgtest failure with ruby-rugged 1.1.0
Added tag(s) ftbfs.

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

Processed: Re: Bug#974580: marked as done (bambootracker FTBFS on 32bit)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #974580 {Done: =?utf-8?q?G=C3=BCrkan_Myczko?= } 
[src:bambootracker] bambootracker FTBFS on 32bit
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions bambootracker/0.4.5+git20121209-1.

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

Bug#974580: marked as done (bambootracker FTBFS on 32bit)

[Sebastian Ramacher]

Control: reopen -1

The fix wasn't enough. It's probably also necessary to ensure that
librtmidi-dev is actually used.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#977269: node-rollup-plugin-terser seems incompatible with current node-terser

[Xavier Guimard]

Package: node-rollup-plugin-terser
Version: 7.0.2-2
Severity: grave
Justification: renders package unusable

When trying current rollup-plugin-terser (7.0.2)  with current
node-terser (4.1.2), package is unuseable:

$ rollup -c

index.js → dist/pako.js, dist/pako.min.js...
[!] (plugin terser) Error: Cannot find module 
'/home/xavier/dev/debian/src/pkg-js/packages/node-pako/node_modules/terser/dist/bundle.min.js'.
 Please verify that the package.json has a valid "main" entry
Error: Cannot find module 
'/home/xavier/dev/debian/src/pkg-js/packages/node-pako/node_modules/terser/dist/bundle.min.js'.
 Please verify that the package.json has a valid "main" entry
at tryPackage (internal/modules/cjs/loader.js:315:19)
at Function.Module._findPath (internal/modules/cjs/loader.js:528:18)
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:818:27)
at Function.Module._load (internal/modules/cjs/loader.js:687:27)
at Module.require (internal/modules/cjs/loader.js:903:19)
at require (internal/modules/cjs/helpers.js:74:18)
at Object. 
(/home/xavier/dev/debian/src/pkg-js/packages/node-pako/node_modules/rollup-plugin-terser/transform.js:1:20)
at Module._compile (internal/modules/cjs/loader.js:1015:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1035:10)
at Module.load (internal/modules/cjs/loader.js:879:32)


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (900, 'testing'), (500, 'unstable')

Kernel: Linux 5.9.0-4-amd64
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages node-rollup-plugin-terser depends on:
ii  node-babel77.12.9+~cs150.130.99-1
ii  node-jest-worker   26.6.3+repack+~cs61.38.31-2
ii  node-serialize-javascript  5.0.1-2
ii  node-terser4.1.2-7

node-rollup-plugin-terser recommends no packages.

node-rollup-plugin-terser suggests no packages.

-- no debconf information

Bug#977268: autopkgtest flaky on arm64

[Michael Biebl]

Package: src:puppet
Version: 5.5.22-1
Severity: serious
X-Debbugs-Cc: debian...@lists.debian.org

Hi,

it appears the autopkgtest of puppet is not really stable on arm64.

https://ci.debian.net/packages/p/puppet/testing/arm64/

I scheduled it a couple of times, as its results were blocking systemd
from testing migration. The refrence run sometimes failed, sometimes
succeeded.


Filing with severity serious, as nowadays the test results affect other
packages.

Regards,
Michael



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

Kernel: Linux 5.9.0-4-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Processed: tagging 977224, tagging 975430, tagging 975660, tagging 975672

[Debian Bug Tracking System]

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

> tags 977224 + sid bullseye
Bug #977224 [src:pokerth] pokerth FTBFS with Boost 1.74
Added tag(s) sid and bullseye.
> tags 975430 + sid bullseye
Bug #975430 {Done: Laszlo Boszormenyi (GCS) } [libcutl] 
libcutl: FTBFS against boost_1.74
Added tag(s) sid and bullseye.
> tags 975660 + sid bullseye
Bug #975660 [scram] scram: FTBFS against boost_1.74
Added tag(s) sid and bullseye.
> tags 975672 + sid bullseye
Bug #975672 [xylib] xylib: FTBFS against boost_1.74
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.

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

Processed: closing 975127

[Debian Bug Tracking System]

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

> close 975127
Bug #975127 [src:wvstreams] wvstreams: FTBFS: ./include/wvscatterhash.h:186:46: 
error: invalid use of non-static data member ‘WvScatterHashBase::xstatus’
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#977265: dds ftbfs with boost1.74

[Matthias Klose]

Package: src:dds
Version: 2.9.0-8
Severity: serious
Tags: sid bullseye ftbfs

https://buildd.debian.org/status/fetch.php?pkg=dds=amd64=2.9.0-8%2Bb1=1607781809=0

   dh_makeshlibs -a -a
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols
file: see diff output below
dpkg-gensymbols: warning: debian/libdds0/DEBIAN/symbols doesn't match completely
debian/libdds0.symbols
--- debian/libdds0.symbols (libdds0_2.9.0-8+b1_amd64)
+++ dpkg-gensymbolsxg50lx   2020-12-12 14:03:26.686048299 +
@@ -437,10 +437,10 @@
  _ZTIN5boost16exception_detail10clone_baseE@Base 0
  _ZTIN5boost16exception_detail10clone_implINS0_10bad_alloc_EEE@Base 0
  _ZTIN5boost16exception_detail10clone_implINS0_14bad_exception_EEE@Base 0
-
_ZTIN5boost16exception_detail10clone_implINS0_19error_info_injectorINS_21thread_resource_errorE@Base
0
+#MISSING: 2.9.0-8+b1#
_ZTIN5boost16exception_detail10clone_implINS0_19error_info_injectorINS_21thread_resource_errorE@Base
0
  _ZTIN5boost16exception_detail14bad_exception_E@Base 0
  _ZTIN5boost16exception_detail15error_info_baseE@Base 0
-
_ZTIN5boost16exception_detail19error_info_injectorINS_21thread_resource_errorEEE@Base
0
+#MISSING: 2.9.0-8+b1#
_ZTIN5boost16exception_detail19error_info_injectorINS_21thread_resource_errorEEE@Base
0
  _ZTIN5boost16exception_detail20error_info_containerE@Base 0
  _ZTIN5boost16thread_exceptionE@Base 0
  _ZTIN5boost21thread_resource_errorE@Base 0
@@ -460,10 +460,10 @@
  _ZTSN5boost16exception_detail10clone_baseE@Base 0
  _ZTSN5boost16exception_detail10clone_implINS0_10bad_alloc_EEE@Base 0
  _ZTSN5boost16exception_detail10clone_implINS0_14bad_exception_EEE@Base 0
-
_ZTSN5boost16exception_detail10clone_implINS0_19error_info_injectorINS_21thread_resource_errorE@Base
0
+#MISSING: 2.9.0-8+b1#
_ZTSN5boost16exception_detail10clone_implINS0_19error_info_injectorINS_21thread_resource_errorE@Base
0
  _ZTSN5boost16exception_detail14bad_exception_E@Base 0
  _ZTSN5boost16exception_detail15error_info_baseE@Base 0
-
_ZTSN5boost16exception_detail19error_info_injectorINS_21thread_resource_errorEEE@Base
0
+#MISSING: 2.9.0-8+b1#
_ZTSN5boost16exception_detail19error_info_injectorINS_21thread_resource_errorEEE@Base
0
  _ZTSN5boost16exception_detail20error_info_containerE@Base 0
  _ZTSN5boost16exception_detail25error_info_container_implE@Base 0
  _ZTSN5boost16thread_exceptionE@Base 0
dh_makeshlibs: error: failing due to earlier errors
make: *** [debian/rules:40: binary-arch] Error 25

Processed: found 975667 in 1:3.10.4+repack-1, notfound 975667 in 3.10.4+repack-1

[Debian Bug Tracking System]

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

> found 975667 1:3.10.4+repack-1
Bug #975667 [supercollider] supercollider: FTBFS against boost_1.74
Marked as found in versions supercollider/1:3.10.4+repack-1.
> notfound 975667 3.10.4+repack-1
Bug #975667 [supercollider] supercollider: FTBFS against boost_1.74
There is no source info for the package 'supercollider' at version 
'3.10.4+repack-1' with architecture ''
Unable to make a source version for version '3.10.4+repack-1'
No longer marked as found in versions 3.10.4+repack-1.
> thanks
Stopping processing here.

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

Bug#975571: marked as done (linux: No rule to make target 'scripts/module.lds' while building out-of-tree modules)

[Debian Bug Tracking System]

Your message dated Sun, 13 Dec 2020 11:00:10 +
with message-id 
and subject line Bug#975571: fixed in linux 5.10~rc7-1~exp1
has caused the Debian Bug report #975571,
regarding linux: No rule to make target 'scripts/module.lds' while building 
out-of-tree modules
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
975571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975571
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 5.10~rc4-1~exp1
Severity: important

Hi,

building out-of-tree modules againt Linux 5.10 headers in experimental fails 
with

No rule to make target 'scripts/module.lds', needed by 
'/path/to/module.ko'.  Stop.

e.g.

make[3]: *** No rule to make target 'scripts/module.lds', needed by 
'/var/lib/dkms/r8168/8.048.03/build/r8168.ko'.  Stop.

make[4]: *** No rule to make target 'scripts/module.lds', needed by 
'/var/lib/dkms/bbswitch/0.8/build/bbswitch.ko'.  Stop.

make[5]: *** No rule to make target 'scripts/module.lds', needed by 
'/usr/src/modules/nvidia-kernel/nvidia-drm.ko'.  Stop.


Andreas
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.10~rc7-1~exp1
Done: Bastian Blank 

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 975...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Blank  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 11 Dec 2020 11:16:29 +0100
Source: linux
Architecture: source
Version: 5.10~rc7-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Bastian Blank 
Closes: 975571 976635 976791 977004 977005
Changes:
 linux (5.10~rc7-1~exp1) experimental; urgency=medium
 .
   * New upstream release candidate
 .
   [ Vincent Blut ]
   * net/sched: Enable NET_SCH_ETS and NET_SCH_FQ_PIE as modules.
 .
   [ Bastian Blank ]
   * Enable SOUNDWIRE, SOUNDWIRE_INTEL, SOUNDWIRE_QCOM.
   * Enable SND_SOC_RT700_SDW, SND_SOC_RT711_SDW, SND_SOC_RT715_SDW.
 (closes: #976791)
   * [x86] Enable SND_SOC_SOF_INTEL_SOUNDWIRE_LINK.
   * [x86] Enable SND_SOC_SOF_COMETLAKE_LP_SUPPORT,
 SND_SOC_SOF_ELKHARTLAKE_SUPPORT, SND_SOC_SOF_JASPERLAKE_SUPPORT.
   * [cloud] Disable some further filesystems. (closes: #977005)
   * [cloud] Disable NET_VENDOR_MICROCHIP.
   * [cloud] Disable ICE, IGC.
   * [amd64] Make GVE module.
   * [x86] Enable X86_CPU_RESCTRL.
   * [amd64/cloud] Disable INFINIBAND_USNIC.
   * Enable PSTORE_BLK.
   * Set SQUASHFS_FILE_DIRECT, SQUASHFS_DECOMP_MULTI_PERCPU.
   * Disable EFI_VARS.
   * [x86] Enable APPLE_PROPERTIES.
   * Enable CRYPTO_ECRDSA, CRYPTO_CURVE25519, disable CRYPTO_SM2.
   * Enable CRYPTO_CFB, CRYPTO_OFB, CRYPTO_KEYWRAP, CRYPTO_ADIANTUM.
   * Enable CRYPTO_BLAKE2S, disable CRYPTO_SM3.
   * Enable CRYPTO_AES_TI, disable CRYPTO_SM4.
   * Enable CRYPTO_DRBG_HASH, CRYPTO_DRBG_CTR.
   * Enable SND_SOC_MAX98373_SDW, SND_SOC_RT1308_SDW, SND_SOC_RT5682_SDW.
   * Enable SND_SOC_INTEL_SOUNDWIRE_SOF_MACH.
   * Enable ATH11K. (closes: #977004)
   * [arm64] Enable most accelerated crypto modules. (closes: #976635)
   * [s390x] Disable IIO.
   * Enable BLK_CGROUP_IOCOST.
   * Enable CGROUP_HUGETLB.
 .
   [ Ben Hutchings ]
   * Fix missing module.lds for building out-of-tree modules (Closes: #975571)
 - debian/rules.real: Install module.lds under arch directory
 - kbuild: Look for module.lds under arch directory too
Checksums-Sha1:
 aa2dc71453f71b82eec91f878a0ff8569b1aeead 198949 linux_5.10~rc7-1~exp1.dsc
 82498d06d4ba8ab787f15634d26ecd1a2e5f0efc 121420772 linux_5.10~rc7.orig.tar.xz
 284fde5a65b01a38146a2092bfef93ebf39a2603 1257744 
linux_5.10~rc7-1~exp1.debian.tar.xz
 c48f2382add3b155e8e0ee6684efc2f6b972dfb6 5792 
linux_5.10~rc7-1~exp1_source.buildinfo
Checksums-Sha256:
 78aa2bf26d1ca1cdb3eb4a545176252f8555b6c154835fa174316d51c5d36535 198949 
linux_5.10~rc7-1~exp1.dsc
 45c3009f71d4653810de94619fdee626e95e5ea493dee0c83807ca3f11158966 121420772 
linux_5.10~rc7.orig.tar.xz
 62211d0547a05b59394a0c6b65e778a62d16b61d9e4ebb0d59806192f1571b6a 1257744 

Processed: bug 977231 is forwarded to https://github.com/libusb/libusb/issues/825

[Debian Bug Tracking System]

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

> forwarded 977231 https://github.com/libusb/libusb/issues/825
Bug #977231 [libusb-1.0-0] libusb-1.0-0: upgrading to 2:1.0.24-1 breaks 
iPhone/iPad detection and communication
Set Bug forwarded-to-address to 'https://github.com/libusb/libusb/issues/825'.
> thanks
Stopping processing here.

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

Bug#977231: libusb-1.0-0: upgrading to 2:1.0.24-1 breaks iPhone/iPad detection and communication

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sat, 2020-12-12 at 21:31 +0100, Aurelien Jarno wrote:
> > If you need more information don't hesitate to ask (I guess you don't
> > have an iDevice to plug for testing).
> 
> Indeed, I do not have such a device. As a first step, it would be nice
> if you can set the environment variable LIBUSB_DEBUG=99 and run lsusb.
> That should give us an idea why the device is ignored.

I also did a bisect run between v1.0.22 and HEAD (upstream repository) and
here's the result:

e2be556bd262cd260bebe3fc724509692537eba3 is the first bad commit
commit e2be556bd262cd260bebe3fc724509692537eba3
Author: Chris Dickens 
Date:   Wed Apr 29 12:39:35 2020 -0700

linux_usbfs: Parse config descriptors during device initialization

Do the work ahead of time and cache the results so that fetching config
descriptors becomes a trivial operation.

Signed-off-by: Chris Dickens 

 libusb/os/linux_usbfs.c | 263 ++-
- -
 libusb/version_nano.h   |   2 +-
 2 files changed, 145 insertions(+), 120 deletions(-)
bisect run success

With the following bisect log:


git bisect start
# bad: [c6a35c56016ea2ab2f19115d2ea1e85e0edae155] libusb 1.0.24
git bisect bad c6a35c56016ea2ab2f19115d2ea1e85e0edae155
# good: [0034b2afdcdb1614e78edaa2a9e22d5936aeae5d] libusb 1.0.22
git bisect good 0034b2afdcdb1614e78edaa2a9e22d5936aeae5d
# good: [48200f2cc23633899270e7c666ac7e948ead8df1] core: Fix build on linux
git bisect good 48200f2cc23633899270e7c666ac7e948ead8df1
# bad: [26611eaa494ed9e077b5b0e1f999f5ae377de958] Windows: Translate
ERROR_NO_SUCH_DEVICE to LIBUSB_TRANSFER_NO_DEVICE
git bisect bad 26611eaa494ed9e077b5b0e1f999f5ae377de958
# good: [09d0312fbb466ce2457df94e314ba1348039138d] Xcode: Update project file
git bisect good 09d0312fbb466ce2457df94e314ba1348039138d
# good: [71a3fb3faadb79c2ccff8f23f0520e4015f547f3] Android: fixes unknown
warning option from ndk build
git bisect good 71a3fb3faadb79c2ccff8f23f0520e4015f547f3
# good: [e873677b9196b191d6cdbdf9783c6d6a18379249] descriptor: Minor
improvements to the parse_descriptor() function
git bisect good e873677b9196b191d6cdbdf9783c6d6a18379249
# good: [8476804b283cfed82aec5e45301b51be3ad68e99] descriptor: Remove
usbi_get_config_index_by_value()
git bisect good 8476804b283cfed82aec5e45301b51be3ad68e99
# good: [14a302a2f55cb2e619158854f94845f2ca2c8214] sunos: Fix a number of
compiler warnings
git bisect good 14a302a2f55cb2e619158854f94845f2ca2c8214
# bad: [e2be556bd262cd260bebe3fc724509692537eba3] linux_usbfs: Parse config
descriptors during device initialization
git bisect bad e2be556bd262cd260bebe3fc724509692537eba3
# good: [e9eec3a680cad3b2c9c5213fb7d60148cf6900da] core: Narrow the types
passed to certain backend functions
git bisect good e9eec3a680cad3b2c9c5213fb7d60148cf6900da
# first bad commit: [e2be556bd262cd260bebe3fc724509692537eba3] linux_usbfs:
Parse config descriptors during device initialization

I can't just git revert the bad commit on top of master (there are conflicts),
but it's worth looking at it.

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl/V7SwACgkQ3rYcyPpX
RFvvowf7BoqO00heSNbxsg9mUSAIfadHNhDEbT9wHHK383SVYUeFO7XYvqsuH5La
WZGKYoL1FGVNm4d6xUpmiCo44FOzoVgFK1n9Oh91YPt3guPCQFb/eWXk/szafpwl
yRZ8N7ceFDcGdimVozkOIM6WQXHi3q3sH2IxzUWCzSmlpzPu/J6qkKb+6aEcBoC7
21Nq+7NhJsmtQog7Nwue2egcLucfP5VhGrz0cr5ySGY81o0tASi4ItnWzNNckKhu
Otj2IB5Oz7VbK90DAbAv9qSXmHqYu7iu6wLmI1HuvqGFKwN96Zdkfc/You8wfq1I
aaQzV26TTSFmiWniCckgK60B6MWlmw==
=4/+F
-END PGP SIGNATURE-

Processed: Re: Bug#971713: sysstat: init or systemd file has overlapping runlevels

[Debian Bug Tracking System]

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

> reassign 971713 insserv 1.21.0-1
Bug #971713 [sysstat] sysstat: init or systemd file has overlapping runlevels
Bug reassigned from package 'sysstat' to 'insserv'.
No longer marked as found in versions sysstat/12.4.0-1.
Ignoring request to alter fixed versions of bug #971713 to the same values 
previously set
Bug #971713 [insserv] sysstat: init or systemd file has overlapping runlevels
Marked as found in versions insserv/1.21.0-1.
> severity 971713 grave
Bug #971713 [insserv] sysstat: init or systemd file has overlapping runlevels
Severity set to 'grave' from 'normal'
> affects 971713 sysstat
Bug #971713 [insserv] sysstat: init or systemd file has overlapping runlevels
Added indication that 971713 affects sysstat
> thanks
Stopping processing here.

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

Bug#977260: all autopkg tests fail with boost1.74

[Matthias Klose]

Package: src:svgpp
Version: 1.3.0+dfsg1-3
Severity: serious
Tags: sid bullseye

all autopkg tests fail with boost1.74, see
https://ci.debian.net/data/autopkgtest/unstable/amd64/s/svgpp/8696315/log.gz

autopkgtest [09:09:49]:  summary
build1   FAIL stderr: In file included from
/usr/include/boost/config/header_deprecated.hpp:18,
build2   FAIL stderr: In file included from
/usr/include/boost/config/header_deprecated.hpp:18,
build3   FAIL stderr: In file included from
/usr/include/boost/config/header_deprecated.hpp:18,

Bug#977258: libssreflect-coq: ABI break by coq binNMU

[Nobuhiro Ban]

Package: libssreflect-coq
Version: 1.11.0-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I cannot use the ssreflect library in my Debian coq env (amd64 testing).

the code:
> Require Import mathcomp.ssreflect.ssreflect.

gets an error:

> Compiled library mathcomp.ssreflect.ssreflect (in file 
> /usr/lib/coq/user-contrib/mathcomp/ssreflect/ssreflect.vo) makes inconsistent 
> assumptions over library Coq.Init.Ltac



Additional information

libssreflect-coq 1.11.0-2 is built against coq 8.12.0-3+b2.
(buildd log: 
https://buildd.debian.org/status/fetch.php?pkg=ssreflect=all=1.11.0-2=1604474661=0
)

But the current coq version is 8.12.0-3+b3.

I think this package should depend on "libcoq-ocaml-",
because "coq-+" is insufficient for binNMUs.

I got the same issue before,
libssreflect-coq 1.11.0-1 (built against coq 8.12.0-3) + coq 8.12.0-3+b1.


Regards,
Nobuhiro Ban


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'stable-debug'), (500,
'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.9.0-3-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libssreflect-coq depends on:
ii  coq [coq-8.12.0+4.11.1]  8.12.0-3+b3
ii  libcoq-ocaml 8.12.0-3+b3

libssreflect-coq recommends no packages.

libssreflect-coq suggests no packages.

-- debconf-show failed

Processed: severity of 976594 is serious

[Debian Bug Tracking System]

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

> # raising to RC severity as fixed in stable but not in the upper suites
> severity 976594 serious
Bug #976594 {Done: Alexander GQ Gerasiov } [src:minidlna] 
minidlna: CVE-2020-12695
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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