Bug#951891: open-ath9k-htc-firmware FTBFS with binutils 2.34
Hi John, Am 18.04.20 um 18:39 schrieb John Scott: >> thank you! >> >> I updated the package. > > Hi, > > I see you've fixed this upstream. firmware-ath9k-htc has been removed from > Bullseye, could you use some help with a new Debian package? Yes, I need help. I already overloaded this months, but it will be even worse in a in few months. I'll be thankful if some one can take over this task. -- Regards, Oleksij signature.asc Description: OpenPGP digital signature
Bug#954606: marked as done (golang-github-minio-minio-go: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 -short github.com/minio/minio-go github.com/minio/minio-go/pkg
Your message dated Sun, 19 Apr 2020 05:18:34 + with message-id and subject line Bug#954606: fixed in golang-github-minio-minio-go 6.0.53-1 has caused the Debian Bug report #954606, regarding golang-github-minio-minio-go: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 -short github.com/minio/minio-go github.com/minio/minio-go/pkg/credentials github.com/minio/minio-go/pkg/encrypt github.com/minio/minio-go/pkg/policy github.com/minio/minio-go/pkg/s3signer github.com/minio/minio-go/pkg/s3utils github.com/minio/minio-go/pkg/set 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.) -- 954606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954606 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-minio-minio-go Version: 6.0.45-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200321 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > # set -short param to avoid tests that access to s3.amazonaws.com > # api_functional_v4_test.go is needed for other tests to run > dh_auto_test -- -short > cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 -short > github.com/minio/minio-go github.com/minio/minio-go/pkg/credentials > github.com/minio/minio-go/pkg/encrypt github.com/minio/minio-go/pkg/policy > github.com/minio/minio-go/pkg/s3signer github.com/minio/minio-go/pkg/s3utils > github.com/minio/minio-go/pkg/set > === RUN TestPartsRequired > --- PASS: TestPartsRequired (0.00s) > === RUN TestCalculateEvenSplits > --- PASS: TestCalculateEvenSplits (0.00s) > === RUN TestGetUserMetaHeadersMap > --- PASS: TestGetUserMetaHeadersMap (0.00s) > === RUN TestHttpRespToErrorResponse > --- PASS: TestHttpRespToErrorResponse (0.00s) > === RUN TestErrEntityTooLarge > --- PASS: TestErrEntityTooLarge (0.00s) > === RUN TestErrEntityTooSmall > --- PASS: TestErrEntityTooSmall (0.00s) > === RUN TestErrUnexpectedEOF > --- PASS: TestErrUnexpectedEOF (0.00s) > === RUN TestErrInvalidBucketName > --- PASS: TestErrInvalidBucketName (0.00s) > === RUN TestErrInvalidObjectName > --- PASS: TestErrInvalidObjectName (0.00s) > === RUN TestErrInvalidArgument > --- PASS: TestErrInvalidArgument (0.00s) > === RUN TestErrWithoutMessage > --- PASS: TestErrWithoutMessage (0.00s) > === RUN TestErrorResponseComparable > --- PASS: TestErrorResponseComparable (0.00s) > === RUN TestPutObjectOptionsValidate > --- PASS: TestPutObjectOptionsValidate (0.00s) > === RUN TestValidBucketLocation > --- PASS: TestValidBucketLocation (0.00s) > === RUN TestErrorResponse > --- PASS: TestErrorResponse (0.00s) > === RUN TestSignatureType > --- PASS: TestSignatureType (0.00s) > === RUN TestBucketPolicyTypes > --- PASS: TestBucketPolicyTypes (0.00s) > === RUN TestPartSize > --- PASS: TestPartSize (0.00s) > === RUN TestMakeTargetURL > --- PASS: TestMakeTargetURL (0.00s) > === RUN TestNewBucketLocationCache > --- PASS: TestNewBucketLocationCache (0.00s) > === RUN TestBucketLocationCacheOps > --- PASS: TestBucketLocationCacheOps (0.00s) > === RUN TestGetBucketLocationRequest > --- PASS: TestGetBucketLocationRequest (0.00s) > === RUN TestProcessBucketLocationResponse > --- PASS: TestProcessBucketLocationResponse (0.00s) > === RUN TestGetObjectCore > TestGetObjectCore: core_test.go:68: skipping functional tests for the > short runs > --- SKIP: TestGetObjectCore (0.00s) > === RUN TestGetObjectContentEncoding > TestGetObjectContentEncoding: core_test.go:261: skipping functional tests > for the short runs > --- SKIP: TestGetObjectContentEncoding (0.00s) > === RUN TestGetBucketPolicy > TestGetBucketPolicy: core_test.go:338: skipping functional tests for > short runs > --- SKIP: TestGetBucketPolicy (0.00s) > === RUN TestCoreCopyObject > TestCoreCopyObject: core_test.go:401: skipping functional tests for short > runs > --- SKIP: TestCoreCopyObject (0.00s) > === RUN TestCoreCopyObjectPart > TestCoreCopyObjectPart: core_test.go:515: skipping functional tests for > short runs > --- SKIP: TestCoreCopyObjectPart (0.00s) > === RUN TestCorePutObject > TestCorePutObject: core_test.go:660: skipping functional tests for short > runs > --- SKIP: TestCorePutObject (0.00s) > === RUN TestCoreGetObjectMetadata > TestCoreGetObjectMetadata: core_test.go:756: skipping functional tests > for the short runs > --- SKIP: TestCoreGetObjectMetadata (0.00s) > === RUN
Processed: Re: Bug#958143: find: fails to honour “--” as options/arguments separator as documented
Processing control commands: > severity 958143 normal Bug #958143 [findutils] find: fails to honour “--” as options/arguments separator as documented Severity set to 'normal' from 'critical' -- 958143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958143 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#958143: find: fails to honour “--” as options/arguments separator as documented
Control: severity 958143 normal On 2020-04-19 Thorsten Glaser wrote: > Package: findutils > Version: 4.7.0-1 > Severity: critical > Justification: breaks unrelated software > $ mkdir ./-a > $ mkdir ./-a/b > $ find ./-a > ./-a > ./-a/b > $ find -- ./-a > ./-a > ./-a/b > $ find -- -a > find: invalid expression; you have used a binary operator '-a' with nothing > before it. > One normally uses the “--” precisely *because* arbitrary input shouldn’t > be confused with an option. This is even documented in the manpage: > 39ately after the last path name. The five `real' options -H, > -L, -P, -D > 40and -O must appear before the first path name, if at all. > A double > 41dash -- can also be used to signal that any remaining > arguments are not > 42options (though ensuring that all start points begin with > either `./' > 43or `/' is generally safer if you use wildcards in the list > of start > 44points). I do not think this is going to break any software not using find. Adjusting severity. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Processed: Bug#954606 marked as pending in golang-github-minio-minio-go
Processing control commands: > tag -1 pending Bug #954606 [src:golang-github-minio-minio-go] golang-github-minio-minio-go: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 -short github.com/minio/minio-go github.com/minio/minio-go/pkg/credentials github.com/minio/minio-go/pkg/encrypt github.com/minio/minio-go/pkg/policy github.com/minio/minio-go/pkg/s3signer github.com/minio/minio-go/pkg/s3utils github.com/minio/minio-go/pkg/set returned exit code 1 Added tag(s) pending. -- 954606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954606 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#954606: marked as pending in golang-github-minio-minio-go
Control: tag -1 pending Hello, Bug #954606 in golang-github-minio-minio-go 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-minio-minio-go/-/commit/83baac9b3efbc45f7b4f2a412020bd27b6d6b9b9 Disabled failing "TestIAMMalformedEndpoint" (Closes: #954606) (this message was generated automatically) -- Greetings https://bugs.debian.org/954606
Bug#956947: marked as done (ogre-1.12 build depends on cruft package swig3.0)
Your message dated Sun, 19 Apr 2020 00:19:08 + with message-id and subject line Bug#956947: fixed in ogre-1.12 1.12.5+dfsg1-1 has caused the Debian Bug report #956947, regarding ogre-1.12 build depends on cruft package swig3.0 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.) -- 956947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956947 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ogre-1.12 Version: 1.12.4+dfsg1-5 Severity: serious Tags: ftbfs swig3.0 is no longer being built by src:swig, and the cruft package in unstable is not in bullseye. --- End Message --- --- Begin Message --- Source: ogre-1.12 Source-Version: 1.12.5+dfsg1-1 Done: Simon Schmeisser We believe that the bug you reported is fixed in the latest version of ogre-1.12, 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 956...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon Schmeisser (supplier of updated ogre-1.12 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: Tue, 07 Apr 2020 21:04:19 +0200 Source: ogre-1.12 Architecture: source Version: 1.12.5+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Simon Schmeisser Closes: 956947 Changes: ogre-1.12 (1.12.5+dfsg1-1) unstable; urgency=medium . [ Simon Schmeisser ] * New upstream version * Use current version of swig (4.0) as 3.0 is no longer build in bullseye (Closes: #956947) Checksums-Sha1: cbb6263e07d8cf69208553bf3d28079624bc47b7 2622 ogre-1.12_1.12.5+dfsg1-1.dsc 73eb8fda198d3627bfc5945b7f26015a08ed9e65 8138044 ogre-1.12_1.12.5+dfsg1.orig.tar.xz b78bc191d9200057c7a653dbdc728ca8f65b30c6 32476 ogre-1.12_1.12.5+dfsg1-1.debian.tar.xz 814cc242c122332fcc9401b7d898fe24257bfdac 15461 ogre-1.12_1.12.5+dfsg1-1_amd64.buildinfo Checksums-Sha256: ac2a687a60ac36f361b103184fbf968deb1822c59680f4f82b6b2b1e25438fcf 2622 ogre-1.12_1.12.5+dfsg1-1.dsc 6f84d047e9345f7647561158030d0b2ebd6baedeff637be9e12adaf652afde8f 8138044 ogre-1.12_1.12.5+dfsg1.orig.tar.xz 1ef326897fe72538b5c5133fb2d292ec38a48ee7fef1ad947dbf9e404e346ad2 32476 ogre-1.12_1.12.5+dfsg1-1.debian.tar.xz d528e41d2c2f570458c79beef9a900371468744a2da508cec091c1cea7556d16 15461 ogre-1.12_1.12.5+dfsg1-1_amd64.buildinfo Files: a87fce1a863a0438f265aa38d6c2b694 2622 libs optional ogre-1.12_1.12.5+dfsg1-1.dsc 3962a16e0f2dff31fa8d138669956adb 8138044 libs optional ogre-1.12_1.12.5+dfsg1.orig.tar.xz 09508ce33dc106b73ec34c2c7237a889 32476 libs optional ogre-1.12_1.12.5+dfsg1-1.debian.tar.xz 211201fd0c853c33fa16171c3a4c9423 15461 libs optional ogre-1.12_1.12.5+dfsg1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEELejiDiSiH9jtG0ynfYPUBqCdweQFAl6bllAACgkQfYPUBqCd weSM8w//WH4L92469p+zQhpfyY5IrJgZ1eNgB/fwx5D66z5p3t6iwxj/kJAHoSPM LMsMY7cCDUI0ShKWmoinZvFjV7dfnuVRQQOkweOhnwFw0CYUhvj99Kcb3gHqWmnq +qAT3UwQK63sMJu9Ta7aNi7R58l4RuCxmERBjRMeaScPQ7Y+05XcrS9R5Lb8LFgC 5yvfSPa5uUuF4Iien4cPnJCxorYtcjk3h9LNgPU8IZTdLPbJ4e4Dd5ZWMpZFamHc dmJuUaFh7axEjuyrtQuZSLb9/VZZm3GD/vuVJFtb9eREuifrsJ1n6NLAAF5ugo0d 2DiKs8896ScjUkzUdpzYO3iWGGPHiwlmVWUNH/ZuDYE6cI8cga4eUVRX8+LiKR5E xxbrxXz0WQ/fLjuNuyv57UXG/9b9PTcFCEkG2vsXd/PkhfTaA09g8eDm/yZ4vp/I mjnGDrxn381oT5J0KMWHDeT1wqYDAEnY80jwPUx5AUCXfTj3JxAYEO5sLg0xw9dE HBxyldcwxOWCdxTsG3ruTe96RrN9nkd3WSvolu7BsLwsU9TAYmGHoZCghy6tUr/f QBmUZN2NBMJju6IxBa22621jcM9WhvHs7WjpT593CY4U9C7hwrnE2G9shwqaIPmB WGEG0uJrGRX21zaHWfhLNX26CLnBmIisO6WgfHO+GzxiSOWrkFI= =KK6K -END PGP SIGNATURE End Message ---
Bug#938752: marked as done (unbound: Python2 removal in sid/bullseye)
Your message dated Sat, 18 Apr 2020 23:49:10 + with message-id and subject line Bug#938752: fixed in unbound 1.10.0-1 has caused the Debian Bug report #938752, regarding unbound: 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.) -- 938752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938752 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:unbound Version: 1.9.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:unbound 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: unbound Source-Version: 1.10.0-1 Done: Robert Edmonds We believe that the bug you reported is fixed in the latest version of unbound, 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 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Robert Edmonds (supplier of updated unbound 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: Sat, 18 Apr 2020 19:29:50 -0400 Source: unbound Architecture: source Version: 1.10.0-1 Distribution: unstable Urgency: medium Maintainer: unbound packagers Changed-By: Robert Edmonds Closes: 938752 Changes: unbound (1.10.0-1) unstable; urgency=medium . [ Robert Edmonds ] * New upstream version 1.10.0 * Drop debian/patches/0002-Allow-use-of-libbsd-functions-with-configure- option-.patch (applied upstream) . [ Stuart Prescott ] * Drop Python 2 module package (Closes: #938752) Checksums-Sha1: 197e81876e0d5ac9f546550e712647f2e0707a0d 2801 unbound_1.10.0-1.dsc 2c175131f7f4c8f6fd2be4a03073d864596d0be6 5727902 unbound_1.10.0.orig.tar.gz 59865250077c83cfb208d7b4a641740792d5cdff 19380 unbound_1.10.0-1.debian.tar.xz 92ffa7d8c421d88c63466d268999152d075af592 10009 unbound_1.10.0-1_amd64.buildinfo Checksums-Sha256: 7ac3f56a099a376f7db47d1991756d52317ba3fb9a0aac9a5e3d3779d7545005 2801 unbound_1.10.0-1.dsc
Processed: found 938441 in 0.4.3-1, tagging 955156, tagging 958058, tagging 956862 ..., affects 956829 ...
Processing commands for cont...@bugs.debian.org:
> found 938441 0.4.3-1
Bug #938441 {Done: Ondřej Nový } [src:schedule] schedule:
Python2 removal in sid/bullseye
Marked as found in versions schedule/0.4.3-1 and reopened.
> tags 955156 + sid bullseye
Bug #955156 [python3-openshot] python3-openshot: Installation broken
Added tag(s) bullseye and sid.
> tags 958058 + sid bullseye
Bug #958058 [src:flex] flex: Maintainer address bounces
Added tag(s) bullseye and sid.
> tags 956862 + sid bullseye
Bug #956862 [src:ho22bus] ho22bus: Consider removing this package
Added tag(s) bullseye and sid.
> reassign 956829 libgphobos76 9.2.1-28
Bug #956829 [tumiki-fighters] tumiki-fighters: Crash with undefined symbol
Bug reassigned from package 'tumiki-fighters' to 'libgphobos76'.
No longer marked as found in versions tumiki-fighters/0.2.dfsg1-9.
Ignoring request to alter fixed versions of bug #956829 to the same values
previously set
Bug #956829 [libgphobos76] tumiki-fighters: Crash with undefined symbol
Marked as found in versions gcc-9/9.2.1-28.
> affects 956829 + tumiki-fighters
Bug #956829 [libgphobos76] tumiki-fighters: Crash with undefined symbol
Added indication that 956829 affects tumiki-fighters
> severity 956829 important
Bug #956829 [libgphobos76] tumiki-fighters: Crash with undefined symbol
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
938441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938441
955156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955156
956829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956829
956862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956862
958058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958058
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#958143: find: fails to honour “--” as options/arguments separator as documented
Package: findutils Version: 4.7.0-1 Severity: critical Justification: breaks unrelated software $ mkdir ./-a $ mkdir ./-a/b $ find ./-a ./-a ./-a/b $ find -- ./-a ./-a ./-a/b $ find -- -a find: invalid expression; you have used a binary operator '-a' with nothing before it. One normally uses the “--” precisely *because* arbitrary input shouldn’t be confused with an option. This is even documented in the manpage: 39ately after the last path name. The five `real' options -H, -L, -P, -D 40and -O must appear before the first path name, if at all. A double 41dash -- can also be used to signal that any remaining arguments are not 42options (though ensuring that all start points begin with either `./' 43or `/' is generally safer if you use wildcards in the list of start 44points). -- System Information: Debian Release: bullseye/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.5.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) Versions of packages findutils depends on: ii libc62.30-4 ii libselinux1 3.0-1+b3 findutils recommends no packages. Versions of packages findutils suggests: ii mlocate 0.26-3+b1 -- no debconf information
Bug#958085: marked as done (codeblocks FTBFS on armel/armhf: multiple definition of `typeinfo name for cbKeyBinder')
Your message dated Sat, 18 Apr 2020 21:49:07 + with message-id and subject line Bug#958085: fixed in codeblocks 20.03-3 has caused the Debian Bug report #958085, regarding codeblocks FTBFS on armel/armhf: multiple definition of `typeinfo name for cbKeyBinder' 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.) -- 958085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958085 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: codeblocks Version: 20.03-2 Severity: serious Tags: ftbfs fixed-upstream patch Forwarded: https://sourceforge.net/p/codeblocks/code/12035/tree//trunk/src/plugins/contrib/keybinder/cbkeybinder.h?diff=51421f1dc431436b6eb31d56:12034 https://buildd.debian.org/status/package.php?p=codeblocks ... libtool: link: g++ -fPIC -DPIC -shared -nostdlib /usr/lib/gcc/arm-linux-gnueabihf/9/../../../arm-linux-gnueabihf/crti.o /usr/lib/gcc/arm-linux-gnueabihf/9/crtbeginS.o .libs/cbkeybinder.o .libs/cbkeyConfigPanel.o .libs/cJSON.o .libs/clKeyboardBindingConfig.o .libs/clKeyboardManager.o .libs/configurationpanel.o .libs/json_node.o .libs/keybinder.o .libs/menuutils.o -Wl,-rpath -Wl,/<>/src/sdk/.libs ../../../sdk/.libs/libcodeblocks.so -L/usr/lib/arm-linux-gnueabihf -lwx_gtk3u_aui-3.0 -lwx_gtk3u_propgrid-3.0 -lwx_gtk3u_richtext-3.0 -lwx_gtk3u_xrc-3.0 -lwx_gtk3u_html-3.0 -lwx_gtk3u_qa-3.0 -lwx_gtk3u_adv-3.0 -lwx_gtk3u_core-3.0 -lwx_baseu_xml-3.0 -lwx_baseu_net-3.0 -lwx_baseu-3.0 -lpthread -ldl -L/usr/lib/gcc/arm-linux-gnueabihf/9 -L/usr/lib/gcc/arm-linux-gnueabihf/9/../../../arm-linux-gnueabihf -L/usr/lib/gcc/arm-linux-gnueabihf/9/../../.. -L/lib/arm-linux-gnueabihf -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/arm-linux-gnueabihf/9/crtendS.o /usr/lib/gcc/arm-linux-gnueabihf/9/../../../arm-linux-gnueabihf/crtn.o -g -O2 -fstack-protector-strong -Wl,--no-undefined -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -pthread -pthread -Wl,-soname -Wl,libkeybinder.so -o .libs/libkeybinder.so /usr/bin/ld: .libs/cbkeyConfigPanel.o:(.rodata+0x14): multiple definition of `typeinfo name for cbKeyBinder'; .libs/cbkeybinder.o:(.rodata+0x0): first defined here /usr/bin/ld: .libs/cbkeyConfigPanel.o:(.data.rel.ro+0xc): multiple definition of `typeinfo for cbKeyBinder'; .libs/cbkeybinder.o:(.data.rel.ro+0x0): first defined here collect2: error: ld returned 1 exit status make[5]: *** [Makefile:579: libkeybinder.la] Error 1 --- End Message --- --- Begin Message --- Source: codeblocks Source-Version: 20.03-3 Done: =?utf-8?q?David_Pr=C3=A9vot?= We believe that the bug you reported is fixed in the latest version of codeblocks, 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 958...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Prévot (supplier of updated codeblocks 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: Sat, 18 Apr 2020 09:47:24 -1000 Source: codeblocks Architecture: source Version: 20.03-3 Distribution: unstable Urgency: medium Maintainer: David Paleino Changed-By: David Prévot Closes: 958085 Changes: codeblocks (20.03-3) unstable; urgency=medium . * Fix FTBFS on armel/armhf (Closes: #958085) Checksums-Sha1: c9d9f0f27a653d3402b7f65fc5c9e53e142e58a8 2144 codeblocks_20.03-3.dsc c8574259e0bc53b58fb024eff75f0b124d4268f1 27324 codeblocks_20.03-3.debian.tar.xz aa69c9a95ff2bd59c7da4d844fa1ae90b3615835 16797 codeblocks_20.03-3_amd64.buildinfo Checksums-Sha256: 652f039ca5830792459d7c18ff97ea7ab57bc5f1e2a5a6be70069ec42eb3defd 2144 codeblocks_20.03-3.dsc 0fa7cf251c2ef4f374b808c8ee380296884301823224d195cc0f9c21d7bbee19 27324 codeblocks_20.03-3.debian.tar.xz f28f4bd0dd1d4dcd2699c46d5582ac8b4b93aca2f1f67a0fe5c3abce6d51ba44 16797 codeblocks_20.03-3_amd64.buildinfo Files: 3ad11e12a2da54b64351b0f32e6c3025 2144 x11 optional codeblocks_20.03-3.dsc 5fc2bc13fec212983853be8839bca7d4 27324 x11 optional codeblocks_20.03-3.debian.tar.xz 506b88d0ec92e8c35192cda864683022 16797 x11 optional codeblocks_20.03-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQFGBAEBCAAwFiEEeHVNB7wJXHRI941mBYwc+UT2vTwFAl6bcwYSHHRhZmZpdEBk
Processed: py2removal bugs severity updates - 2020-04-18 21:35:31.891219+00:00
Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html > # and https://lists.debian.org/debian-python/2019/12/msg00076.html > # and https://lists.debian.org/debian-python/2020/03/msg00087.html > # mail threads for more details on this severity update > # python-ogg is a module and has 0 external rdeps or not in testing > severity 937496 serious Bug #937496 [src:pyogg] pyogg: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 937496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937496 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: notfixed 954901 in 9.52~dfsg-1
Processing commands for cont...@bugs.debian.org:
> #unconfuse the bts
> notfixed 954901 9.52~dfsg-1
Bug #954901 {Done: Sean Whitton } [ghostscript]
ghostscript: runtime error: malloc(): invalid size (unsorted)
No longer marked as fixed in versions 9.52~dfsg-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
954901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954901
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#937791: Blocked on reverse dependencies
On 4/13/20 2:25 PM, Moritz Mühlenhoff wrote: On Sat, Feb 08, 2020 at 11:13:20AM -0800, Martin Kelly wrote: On Sat, 8 Feb 2020 10:55:23 -0800 Martin Kelly wrote: On 2/2/20 8:39 PM, Sandro Tosi wrote: should we remove this package then? or do you want to generate a python3-gmpy? I didn't realize, but it looks like this package actually does support Python 3. I had assumed we would let this package die when Python 2 dies, since the package is dead upstream since 2013. However, looking at the popcon stats, the original python GMPY is still much more popular than than python GMPY2 (3543 vs 443). So I think it's worth keeping this package. I'm working on converting it over now and should be able to get it done in the next few weeks. Is it possible to remove the AUTORM tag until this is done, or should we let it get deleted and upload a new python3-gmpy package after that? Looking further, it seems that with current versions of Python 3 (I tested with 3.7.3), the old GMPY 1.17 is no longer passing. When I run test3/gmpy_test.py, I'm getting: $ python3 test3/gmpy_test.py ... 8 items had failures: 1 of 4 in gmpy_test_cvr 4 of 126 in gmpy_test_cvr.__test__.user_errors 1 of 1 in gmpy_test_dec 2 of 2 in gmpy_test_mpf 2 of 60 in gmpy_test_mpf.__test__.binio 2 of 2 in gmpy_test_mpq 2 of 4 in gmpy_test_mpz 7 of 25 in gmpy_test_rnd.__test__.rand 1504 tests in 42 items. 1483 passed and 21 failed. ***Test Failed*** 21 failures. In contrast, the tests for GMPY 2 all succeed, so I think the author clearly intended for tests to fully pass. Since this hasn't been maintained for 7 or so years, I'm not too surprised. Given this, I think we should let this package be removed and consider resurrecting it in the future if people ask for it and someone will step up to maintain it. Sandro, is there anything more to do if I want to let this package be removed, or do I just wait for the auto-removal? Martin, what are you referring here to with "removed"? Removal from testing or unstable? The former happened automatically in the mean time, the latter needs a bug using "reportbug ftp.debian.org" Cheers, Moritz Thanks for clarifying; I filed a bug to remove this package from unstable, as it's dead upstream and all reverse dependencies are removed from unstable at this point: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958138
Bug#954684: ant-contrib: FTBFS: tests failed
On Sun, Mar 22, 2020 at 02:49:40PM +0100, Lucas Nussbaum wrote: > Source: ant-contrib > Version: 1.0~b3+svn177-11 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20200322 ftbfs-bullseye > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > Relevant part (hopefully): > > (snip) Thank you for the bug report Lucas. It looks like there are interface changes in the recent update of bcel from 6.3 to 6.4.1 [1]. > > [junit] junit.framework.AssertionFailedError: Should throw > > BuildException because 'Design is broken' with message 'Design check failed > > due to previous errors' (actual message > > 'org.apache.bcel.classfile.ClassFormatException: Invalid method signature: > > Ljava/lang/String;' instead) > > [junit] at > > net.sf.antcontrib.design.VerifyDesignTest.expectDesignCheckFailure(VerifyDesignTest.java:349) > > [junit] /<>/test/resources/design/verifydesign.xml:64: > > org.apache.bcel.classfile.ClassFormatException: Invalid method signature: > > Lmod/arraydepend2/ClassDependsOnArray; > > [junit] at > > net.sf.antcontrib.design.VerifyDesignTest.testArrayDepend2(VerifyDesignTest.java:74) We will need to either put together a patch for bcel or for ant-contrib. Cheers, tony [1] https://tracker.debian.org/news/1104326/accepted-bcel-641-1-source-into-unstable/ signature.asc Description: PGP signature
Bug#956324: Clustalo bus error on mipsel (Was: Bug#956324: python-biopython: FTBFS on mipsel)
> On Apr 17, 2020, at 22:39, Andreas Tille wrote:
>
> Hi Matthew,
>
> thanks a lot for your detailed investigation.
>
> On Fri, Apr 17, 2020 at 04:28:23PM -0700, Matthew Fernandez wrote:
>>> Program received signal SIGBUS, Bus error.
>>> 0x5556a1b8 in PairDistances (distmat=0x7fff278c, mseq=0x55692a30,
>>> pairdist_type=, bPercID=, istart=0, iend=3,
>>> jstart=0, jend=3, fdist_in=0x0,
>>> fdist_out=0x0) at pair_dist.c:346
>>> 346 NewProgress(, LogGetFP(, LOG_INFO),
>>
>> OK, let me try a little harder :)
>>
>>$ # enable debugging symbols and Address Sanitizer
>>$ CFLAGS="-g -fsanitize=address" CXXFLAGS="-g -fsanitize=address"
>> ./configure
>>…
>>$ make clean && make
>>…
>>$ ./src/clustalo -i debian/tests/biopython_testdata/f002 --guidetree-out
>> temp_test.dnd -o temp_test.aln --outfmt clustal --force
>>=
>>==30264==ERROR: AddressSanitizer: dynamic-stack-buffer-overflow on
>> address 0x7ffcfcbf5784 at pc 0x5620f0aa478c bp 0x7ffcfcbf56c0 sp
>> 0x7ffcfcbf56b8
>>WRITE of size 4 at 0x7ffcfcbf5784 thread T0
>>#0 0x5620f0aa478b in PairDistances
>> /home/matthew/clustal-omega-1.2.4/src/clustal/pair_dist.c:336
>>#1 0x5620f0a91d9f in AlignmentOrder
>> /home/matthew/clustal-omega-1.2.4/src/clustal-omega.c:835
>>#2 0x5620f0a95c04 in Align
>> /home/matthew/clustal-omega-1.2.4/src/clustal-omega.c:1221
>>#3 0x5620f0a90d76 in MyMain
>> /home/matthew/clustal-omega-1.2.4/src/mymain.c:1192
>>#4 0x5620f0a88ca2 in main
>> /home/matthew/clustal-omega-1.2.4/src/main.cpp:469
>>#5 0x7f3773d9009a in __libc_start_main ../csu/libc-start.c:308
>>#6 0x5620f0a89ad9 in _start
>> (/home/matthew/clustal-omega-1.2.4/src/clustalo+0x2dad9)
>>
>>Address 0x7ffcfcbf5784 is located in stack of thread T0
>>SUMMARY: AddressSanitizer: dynamic-stack-buffer-overflow
>> /home/matthew/clustal-omega-1.2.4/src/clustal/pair_dist.c:336 in
>> PairDistances
>>Shadow bytes around the buggy address:
>> 0x10001f976aa0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 0x10001f976ab0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 0x10001f976ac0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 0x10001f976ad0: 00 00 00 00 00 00 00 00 00 00 00 00 ca ca ca ca
>> 0x10001f976ae0: 04 cb cb cb cb cb cb cb 00 00 00 00 ca ca ca ca
>>=>0x10001f976af0:[04]cb cb cb cb cb cb cb 00 00 00 00 00 00 00 00
>> 0x10001f976b00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 0x10001f976b10: f1 f1 f1 f1 00 f2 f2 f2 f2 f2 f2 f2 00 f2 f2 f2
>> 0x10001f976b20: f2 f2 f2 f2 00 00 00 00 00 00 00 00 00 f2 f2 f2
>> 0x10001f976b30: f3 f3 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00
>> 0x10001f976b40: 00 00 00 00 00 00 f1 f1 f1 f1 00 f2 f2 f2 f2 f2
>>Shadow byte legend (one shadow byte represents 8 application bytes):
>> Addressable: 00
>> Partially addressable: 01 02 03 04 05 06 07
>> Heap left redzone: fa
>> Freed heap region: fd
>> Stack left redzone: f1
>> Stack mid redzone: f2
>> Stack right redzone: f3
>> Stack after return: f5
>> Stack use after scope: f8
>> Global redzone: f9
>> Global init order: f6
>> Poisoned by user:f7
>> Container overflow: fc
>> Array cookie:ac
>> Intra object redzone:bb
>> ASan internal: fe
>> Left alloca redzone: ca
>> Right alloca redzone:cb
>>==30264==ABORTING
>>
>> Looking at line 336 of pair_dist.c, it looks like the bound on the
>> containing loop is wrong. So let’s try adjusting that:
>>
>>$ vim src/clustal/pair_dist.c
>>$ git diff src/clustal/pair_dist.c
>>diff --git a/src/clustal/pair_dist.c b/src/clustal/pair_dist.c
>>index e6dbdc3..bb79e61 100644
>>--- a/src/clustal/pair_dist.c
>>+++ b/src/clustal/pair_dist.c
>>@@ -321,7 +321,7 @@ PairDistances(symmatrix_t **distmat, mseq_t *mseq,
>> int pairdist_type, bool bPerc
>>
>> /* FIXME: can get rid of iChunkStart, iChunkEnd now that we're
>> using the arrays */
>> iChunkStart = iend;
>>-for(iChunk = 0; iChunk <= iNumberOfThreads; iChunk++)
>>+for(iChunk = 0; iChunk < iNumberOfThreads; iChunk++)
>> {
>> iChunkEnd = iChunkStart;
>> if (iChunk == iNumberOfThreads - 1){
>>$ make
>>…
>>$ ./src/clustalo -i debian/tests/biopython_testdata/f002 --guidetree-out
>> temp_test.dnd -o temp_test.aln --outfmt clustal --force
>>=
>>==30601==ERROR: AddressSanitizer: global-buffer-overflow on address
>> 0x561188847864 at pc 0x5611886da6e7 bp 0x7fffe6d77ef0 sp 0x7fffe6d77ee8
>>READ of size 4 at 0x561188847864 thread T0
>>#0 0x5611886da6e6
Bug#958124: mrbayes: binary-all FTBFS
Control: tags -1 pending Discussing a better solution for #958125 using simde. Kind regards Andreas.
Processed: Re: Bug#958124: mrbayes: binary-all FTBFS
Processing control commands: > tags -1 pending Bug #958124 [src:mrbayes] mrbayes: binary-all FTBFS Added tag(s) pending. -- 958124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958124 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 953178
Processing commands for cont...@bugs.debian.org: > close 953178 Bug #953178 [src:rust-findshlibs] src:rust-findshlibs: fails to migrate to testing for too long Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 953178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953178 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: limit source to codeblocks, tagging 958085
Processing commands for cont...@bugs.debian.org: > limit source codeblocks Limiting to bugs with field 'source' containing at least one of 'codeblocks' Limit currently set to 'source':'codeblocks' > tags 958085 + pending Bug #958085 [src:codeblocks] codeblocks FTBFS on armel/armhf: multiple definition of `typeinfo name for cbKeyBinder' Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 958085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958085 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: passenger: FTBFS on armel and armhf
Processing commands for cont...@bugs.debian.org: > Tags 955440 +patch Bug #955440 [src:passenger] passenger: FTBFS on armel and armhf Added tag(s) patch. > Thanks Stopping processing here. Please contact me if you need assistance. -- 955440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955440 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955440: passenger: FTBFS on armel and armhf
Tags 955440 +patch
Thanks
The offending code is.
#if defined(__APPLE__) || defined(__SOLARIS__) || defined(__arm__)
// File descriptor passing macros (CMSG_*) seem to be broken
// on 64-bit MacOS X. This structure works around the problem.
struct {
struct cmsghdr header;
int fd;
} control_data;
#define EXPECTED_CMSG_LEN sizeof(control_data)
#else
char control_data[CMSG_SPACE(sizeof(int))];
#define EXPECTED_CMSG_LEN CMSG_LEN(sizeof(int))
#endif
And there is another similar block later in the file that likely suffers from
the same issue.
I took a look at a git blame in upstream git
https://github.com/phusion/passenger/blame/0ef3222e86ede97dff189de1137cca67684d4e2d/src/cxx_supportlib/Utils/IOUtils.cpp#L1128
which leads back to
https://github.com/phusion/passenger/commit/e3885d5c9e7b5403422742f193be0aa5775a84d2 but
that is just moving the offending code from MessageChannel.h to IOUtils.cpp so going to
the parent commit and blaming again takes us to
https://github.com/phusion/passenger/commit/312b5e1c65558e17cd30d1b28089078d8f614fbf
which added the arm condition to the list of conditionals and is described as "Fixed
compilation problems on Linux systems with ARM CPU".
My feeling is that the issue that upstream was trying to fix was an alignment
issue. In particular the creation of of a buffer by using char
control_data[CMSG_SPACE(sizeof(int))] means there are no alignment guarantees
on the buffer and if my reading of the macros is correct then an unaligned
buffer will lead to unaligned accesses. It looks like this bad practice may
have originated from older versions of the manpage, I note that
https://linux.die.net/man/3/cmsg_space uses a plain char array while the
manpage in Bullseye uses a union.
I have written a patch which fixes the alignment issue in the main codepath and
switches arm Linux (and any other non-apple, non-solaris arm systems) from the
alternate codepath to the main codepath. I have tested that the package builds
in raspbian bullseye-staging with the patch, I have not tested it beyond that.
I have uploaded the package to raspbian bullseye, a debdiff should appear soon
at https://debdiffs.raspbian.org/main/p/passenger/ no intent to NMU in Debian.
Bug#955638: cargo: please package recent version
Hi Ximin, Am 18.04.20 um 21:01 schrieb Ximin Luo: Sorry, I had a brain-fart here. We have 2 cargo packages, 1 (rust-cargo) that is part of our rust crate packaging ecosystem with its web of dependencies, and 1 (cargo) that explicitly embeds its dependencies to avoid this type of issue. > The latter is what you want, and I've just uploaded it too, so there should be no need to wait for the below packages. I got confused earlier because we use rust-cargo to update cargo, and I temporarily forgot my own instructions on updating the packaging. > So Thunderbird should now be unblocked on this front. thanks! In the between time I've untangled the remaining build issues (and removed the version check for cargo for now) within the latest beta and could create working packages. I uploaded these a few hours ago and TB 1:76.0~b1-1 waits for review in NEW too. I'm happy I did make some remarkable process on this! -- Regards Carsten Schoenert
Bug#955638: [Pkg-rust-maintainers] Bug#955638: Bug#955638: cargo: please package recent version
Sorry, I had a brain-fart here. We have 2 cargo packages, 1 (rust-cargo) that is part of our rust crate packaging ecosystem with its web of dependencies, and 1 (cargo) that explicitly embeds its dependencies to avoid this type of issue. The latter is what you want, and I've just uploaded it too, so there should be no need to wait for the below packages. I got confused earlier because we use rust-cargo to update cargo, and I temporarily forgot my own instructions on updating the packaging. So Thunderbird should now be unblocked on this front. Best, Ximin Ximin Luo: > Hi Carsten, cargo 0.43.1 has been packaged and source-only uploaded, however > for it to be built, it will have to wait for the following packages to clear > NEW: > > rust-bitmaps_2.1.0-1_amd64.ftp-master.upload > rust-im-rc_14.3.0-1_amd64.ftp-master.upload > rust-sized-chunks_0.6.1-1_amd64.ftp-master.upload > > I will ping them to hopefully get a bit more priority. > > Best, > Ximin > > Carsten Schoenert: >> Hello Ximin, >> >> Am 04.04.20 um 02:17 schrieb Ximin Luo: >>> Hi Carsten, it might be a couple of weeks until we get this done. >>> Have you tried just deleting the version constraint and using the >>> existing version in Debian sid? >> I've tried to figure out the right place there this version check is >> happen. In most cases this is file ./old-configure.in within the >> Thunderbird sources. But I did have no luck on this until now. I will >> look further into this part this weekend I guess, mostly the version >> checks from the Firefox environment are to strict for Thunderbird, yes. >> Most of the parts from the Firefox source are not built for Thunderbird >> but the configure script is checking this. >> >> In the long term this is always just a workaround which, if I do this, I >> need to proof deeply before uploading new packages even to experimental. >> So if you ever find time to have a look into newer cargo versions please >> keep an eye on this. >> >> It's currently really frustrating that I'm unable to build a recent >> Thunderbird Beta version due every time new version dependencies around >> Rust are popping up. This is not your fault, but shows me how complex >> and fragile the Rust ecosystem currently is. >> >> The built is just the first problem I need to solve, Mozilla has again >> changed some previously internally parts in Thunderbird and I need to >> adopt the Debian built to this again. >> > > -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git
Bug#938299: marked as done (pyvorbis: Python2 removal in sid/bullseye)
Your message dated Sat, 18 Apr 2020 18:33:05 + with message-id and subject line Bug#958057: Removed package(s) from unstable has caused the Debian Bug report #938299, regarding pyvorbis: 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.) -- 938299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938299 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pyvorbis Version: 1.5-5 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:pyvorbis 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 --- Version: 1.5-5+rm Dear submitter, as the package pyvorbis has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/958057 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#937778: marked as done (python-gcm-client: Python2 removal in sid/bullseye)
Your message dated Sat, 18 Apr 2020 18:32:15 + with message-id and subject line Bug#958048: Removed package(s) from unstable has caused the Debian Bug report #937778, regarding python-gcm-client: 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.) -- 937778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937778 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-gcm-client Version: 0.1.4-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:python-gcm-client 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 --- Version: 0.1.4-1+rm Dear submitter, as the package python-gcm-client has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/958048 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Processed: Re: Bug#860446: gravit segmentation violation
Processing control commands: > tags -1 - moreinfo unreproducible Bug #860446 [gravit] gravit: Segmentation violation on start (on i386?) Removed tag(s) moreinfo and unreproducible. > severity -1 serious Bug #860446 [gravit] gravit: Segmentation violation on start (on i386?) Severity set to 'serious' from 'normal' -- 860446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860446 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#958125: mrbayes: baseline violation on amd64 and i386
Source: mrbayes Version: 3.2.7a-1 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=mrbayes=amd64=3.2.7a-1=1587118897=0 ... checking for x86 cpuid output... unknown checking for x86-AVX xgetbv output... unknown checking for x86 cpuid 0x output... d:756e6547:6c65746e:49656e69 checking for x86 cpuid 0x8000 output... 8008:756e6547:6c65746e:49656e69 checking for x86 cpuid 0x0001 output... 306c1:2000800:fffa3203:78bfbff checking for x86 cpuid 0x0007 output... 0:7a9:0:0 checking for x86 cpuid 0x8001 output... 306c1:0:21:28100800 checking for x86-AVX xgetbv 0x output... 7:0 checking whether RDRND is supported by the processor... yes checking whether RDRND is supported by the processor and OS... yes checking whether C compiler accepts -mrdrnd... yes checking whether BMI1 is supported by the processor... yes checking whether BMI1 is supported by the processor and OS... yes checking whether C compiler accepts -mbmi... yes checking whether BMI2 is supported by the processor... yes checking whether BMI2 is supported by the processor and OS... yes checking whether C compiler accepts -mbmi2... yes checking whether ADX is supported by the processor... no checking whether MPX is supported by the processor... no checking whether PREFETCHWT1 is supported by the processor... no checking whether ABM is supported by the processor... yes checking whether ABM is supported by the processor and OS... yes checking whether C compiler accepts -mabm... yes checking whether MMX is supported by the processor... yes checking whether MMX is supported by the processor and OS... yes checking whether C compiler accepts -mmmx... yes checking whether SSE is supported by the processor... yes checking whether SSE is supported by the processor and OS... yes checking whether C compiler accepts -msse... yes checking whether SSE2 is supported by the processor... yes checking whether SSE2 is supported by the processor and OS... yes checking whether C compiler accepts -msse2... yes checking whether SSE3 is supported by the processor... yes checking whether SSE3 is supported by the processor and OS... yes checking whether C compiler accepts -msse3... yes checking whether SSSE3 is supported by the processor... yes checking whether SSSE3 is supported by the processor and OS... yes checking whether C compiler accepts -mssse3... yes checking whether SSE4.1 is supported by the processor... yes checking whether SSE4.1 is supported by the processor and OS... yes checking whether C compiler accepts -msse4.1... yes checking whether SSE4.2 is supported by the processor... yes checking whether SSE4.2 is supported by the processor and OS... yes checking whether C compiler accepts -msse4.2... yes checking whether SSE4a is supported by the processor... no checking whether SHA is supported by the processor... no checking whether AES is supported by the processor... yes checking whether AES is supported by the processor and OS... yes checking whether C compiler accepts -maes... yes checking whether AVX is supported by the processor... yes checking whether AVX is supported by the processor and OS... yes checking whether C compiler accepts -mavx... yes checking whether FMA3 is supported by the processor... yes checking whether FMA3 is supported by the processor and OS... yes checking whether C compiler accepts -mfma... yes checking whether FMA4 is supported by the processor... no checking whether XOP is supported by the processor... no checking whether AVX2 is supported by the processor... yes checking whether AVX2 is supported by the processor and OS... yes checking whether C compiler accepts -mavx2... yes checking whether AVX512-F is supported by the processor... no checking whether AVX512-CD is supported by the processor... no checking whether AVX512-PF is supported by the processor... no checking whether AVX512-ER is supported by the processor... no checking whether AVX512-VL is supported by the processor... no checking whether AVX512-BW is supported by the processor... no checking whether AVX512-DQ is supported by the processor... no checking whether AVX512-IFMA is supported by the processor... no checking whether AVX512-VBMI is supported by the processor... no ... gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -mmmx -msse -msse2 -msse3 -mssse3 -msse4.1 -msse4.2 -maes -mavx -mfma -mavx2 -mrdrnd -mbmi -mbmi2 -mabm -I/usr/include/libhmsbeagle-1 -pthread -g -std=c99 -pedantic -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -c -o mb-bayes.o `test -f 'bayes.c' || echo './'`bayes.c ... Using AX_EXT in configure.ac makes the package only run on machines compatible with whatever the buildd supports, which is the same problem as -march-native.
Bug#958124: mrbayes: binary-all FTBFS
Source: mrbayes Version: 3.2.7a-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=mrbayes=all=3.2.7a-1=1587119516=0 ... debian/rules override_dh_installdeb make[1]: Entering directory '/<>' # FIXME: That's a dirty hack by simply removing debug information in mrbayes-mpi-dbgsym # Due to the duplicated build above this is just a duplicate of mrbayes-dbgsym and creates a file conflict find debian/.debhelper/mrbayes-mpi/dbgsym-root/usr/lib/debug -name "*.debug" -delete find: ‘debian/.debhelper/mrbayes-mpi/dbgsym-root/usr/lib/debug’: No such file or directory make[1]: *** [debian/rules:37: override_dh_installdeb] Error 1
Processed: owner 957088
Processing commands for cont...@bugs.debian.org: > owner 957088 woodrow.s...@gmail.com Bug #957088 [ledmon] ledmon: libsgutils2-2 1.45 update breaks ledmon Owner recorded as woodrow.s...@gmail.com. > thanks Stopping processing here. Please contact me if you need assistance. -- 957088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957088 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952825: marked as done (rust-whoami: d/copyright issues)
Your message dated Sat, 18 Apr 2020 17:34:27 + with message-id and subject line Bug#952825: fixed in rust-whoami 0.8.1-1 has caused the Debian Bug report #952825, regarding rust-whoami: d/copyright issues 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.) -- 952825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952825 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-whoami Version: 0.7.0-1 Hello, During review in NEW I noticed that CODEOFCONDUCT.md is under a different license and has different copyright holders. -- Sean Whitton signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: rust-whoami Source-Version: 0.8.1-1 Done: Ximin Luo We believe that the bug you reported is fixed in the latest version of rust-whoami, 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 952...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ximin Luo (supplier of updated rust-whoami 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: Sat, 18 Apr 2020 18:12:20 +0100 Source: rust-whoami Architecture: source Version: 0.8.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Ximin Luo Closes: 952825 Changes: rust-whoami (0.8.1-1) unstable; urgency=medium . * Team upload. * Package whoami 0.8.1 from crates.io using debcargo 2.4.2 * Update d/copyright. (Closes: #952825) Checksums-Sha1: 1139afef2658268a6007ab18c5547fbef8dd4fef 1563 rust-whoami_0.8.1-1.dsc 454fca05260b0d4ecf9c85f2c8b94536e68ee0b2 13766 rust-whoami_0.8.1.orig.tar.gz 9370367c5c127e3bb95d3507bd0ab3de3e5d7423 10884 rust-whoami_0.8.1-1.debian.tar.xz c5078a536d343cddf9d9a3d8510496cb420603e7 7035 rust-whoami_0.8.1-1_source.buildinfo Checksums-Sha256: 162b57d19c8fd7b46587b133480f81f6ebea258f2c308463c7a69620fc21098f 1563 rust-whoami_0.8.1-1.dsc a08eb844b158ea881e81b94556eede7f7e306e4c7b976aad88f49e6e36dec391 13766 rust-whoami_0.8.1.orig.tar.gz 7e0d16a58c8867fdd904a993f4bdcc932e78aef1485335cb9f6f3d6f19977c3b 10884 rust-whoami_0.8.1-1.debian.tar.xz 957cc7791fae27723d032f732dcda7d559d89b58409ff4868e358f9ecdf4753d 7035 rust-whoami_0.8.1-1_source.buildinfo Files: 13c4ebdcf144a2acb5e58fdce2cbc5c0 1563 rust optional rust-whoami_0.8.1-1.dsc ea796f3103a4c6b3ddba944494169aa5 13766 rust optional rust-whoami_0.8.1.orig.tar.gz 6e00ba2f791988fd0b1fdb775061e066 10884 rust optional rust-whoami_0.8.1-1.debian.tar.xz 0a031782449ebcfabf8984a31cacdf73 7035 rust optional rust-whoami_0.8.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iHUEARYKAB0WIQReYinNQ9GpZ9TYcRrrH8jaRfspMAUCXps0+QAKCRDrH8jaRfsp MB58AP0aOpu2RA5iJ8YrXfTtTMn9uPWUHZd0PIaWKKsg03r3lwD/QnkLFOZbemXt T4gnsv1rjAoPWYhLqKlBOykfpUmmQA0= =Hw45 -END PGP SIGNATURE End Message ---
Bug#958081: marked as done (nanopolish: FTBFS everywhere)
Your message dated Sat, 18 Apr 2020 17:19:10 + with message-id and subject line Bug#958081: fixed in nanopolish 0.12.1-2 has caused the Debian Bug report #958081, regarding nanopolish: FTBFS everywhere 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.) -- 958081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958081 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nanopolish Version: 0.12.1-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) nanopolish FTBFS on the buildds. See https://buildd.debian.org/status/fetch.php?pkg=nanopolish=amd64=0.12.1-1=1586252670=0 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: nanopolish Source-Version: 0.12.1-2 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of nanopolish, 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 958...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated nanopolish 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: Sat, 18 Apr 2020 18:51:43 +0200 Source: nanopolish Architecture: source Version: 0.12.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 958081 Changes: nanopolish (0.12.1-2) unstable; urgency=medium . * Versioned Build-Depends against libminimap2-dev (>= 2.17+dfsg-8) (Thanks to Hamid Nassiby) Closes: #958081 Checksums-Sha1: 613b0a2b29e3d58534f0e9dedbfb8a71c9d34de4 2138 nanopolish_0.12.1-2.dsc ad19ae08e4c894f5ec0e37edbc4f22c6166c67c7 7856 nanopolish_0.12.1-2.debian.tar.xz 62472495036a7beaec8227661639692f71ebd38d 7683 nanopolish_0.12.1-2_amd64.buildinfo Checksums-Sha256: 8464d1780bda45a800c08d3afa9dae91c88ea1b467657dd8a3ebe042d0ec5c83 2138 nanopolish_0.12.1-2.dsc 83d1365a9f1c6a4030e1f564555b6c64602a43f1a09c3288189243508eff56a4 7856 nanopolish_0.12.1-2.debian.tar.xz 7f057e6e943c17db334fc65e6c1f419eb2077b7c2511dc2269c5981e66344409 7683 nanopolish_0.12.1-2_amd64.buildinfo Files: 7c16bb257b39bd53a31c7b8c0eec966d 2138 science optional nanopolish_0.12.1-2.dsc d0c418758374a5269ef9cc45d8113666 7856 science optional nanopolish_0.12.1-2.debian.tar.xz 70c98cfb2cbbeb745c70d62154523cba 7683 science optional nanopolish_0.12.1-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl6bMUURHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtERyQ/9Gr+eDKvwPXjhnKIBhHkQQltYHkYY9M4A r1rip+z5zn3Ja350osyBuQAt6Zk7hkrcYOGruIE7p9RR5BI3MYspRR4N75h3gbuV 9/liYcZSbiQIl/y6qEtBfTROQsjhUzBh75u/BJprSVEoWpzBTjZ3sEdIMPL+cBJ0 Yr4VUU8fIN4khct7ogmgyW8nKj1eVWF0xazr5XrLOxY6K+beEPLgA2/CDG+b0t8W D2gsxDZST9LXCQOlxPoOfDeWp8+mvH+pQdZd0M2fy7fdShe8v+i61Wd6cyw21ost TYdo3ZH7ACpQW1vaLJZxSWxYqty9vknSpZAS7dL/a9dvShd591jvU9Rmq1mrkUMj WR24Me+RrcQjr7e0dqf2gZZRAMqQmn7lPAft7LvJM9IxD81TeYd7E2x7u+EOTRN0 M4xV5okliAbPjeQPrJdZm/DmPcRPC5ALe1nM51G8yT9mUPaOEE6gOCT+YIYYNylQ /jRVa08hq15BHHK07J77UNjvpYh3oPZwwPDk36lX+YiXKMvgewyqlJzjAKApwYrY Rs7r63J4Wt5r9ph3fGKp5xbGnkirQVZVIGFQcdpmpd8EKbRs1kdOXgqtkLKNnj5U yEVzWP7xU1NneQGvF/lS75EHgtaEfsF9Rmuk596XJcn04zSiWq1sxPoi0ypBPKwA cQSuSh5sb8c= =7xbV -END PGP SIGNATURE End Message ---
Bug#955764: closing 955764
close 955764 version 0.43.1-1 thanks
Processed: closing 953339
Processing commands for cont...@bugs.debian.org: > close 953339 Bug #953339 [src:rust-strum-macros] src:rust-strum-macros: fails to migrate to testing for too long Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 953339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953339 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 955760
Processing commands for cont...@bugs.debian.org: > close 955760 Bug #955760 [librust-plist-dev] librust-plist-dev: dependencies unsatisfiable. Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 955760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955760 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 953687
Processing commands for cont...@bugs.debian.org: > close 953687 Bug #953687 [src:rust-structopt-derive] src:rust-structopt-derive: fails to migrate to testing for too long Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 953687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953687 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#958117: uglifyjs: dead code: keep away from bullseye
Source: uglifyjs Version: 2.8.29-6 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 UglifyJS 2 is dead upstream (no code commit since June 2017). These packages will *not* be part of Bullseye: src:uglifyjs libjs-uglify node-uglify Projects now using UglifyJS 2 can either upgrade to UglifyJS 3 or migrate to terser. UglifyJS 3 has far fewer reverse dependencies than terser, and is therefore more likely to be kept at newest release and is less likely to be problematic to backport than terser. UglifyJS 3 supports only EcmaScript 5, so more modern code need to use Babel so "dumb down" code first, where terser can process more modern dialects directly. These packages are part of UglifyJS 3: src:uglify-js libjs-uglify-js node-uglify-js uglifyjs These packages are part of terser: src:node-terser node-terser uglifyjs.terser - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl6bMpQACgkQLHwxRsGg ASEdJA//dGGTgo6m8Tngz7FgUvvjSc3oqy2KJQDki2NlwQixe03p6Mrm0yvrKJ6d rK+IgJWHTo7xjXJ23jfX2ozRmp3CYaktE17cHpTpAR3i9I0749Lh2ff7R8Hdhbj+ 1hGpKecwj/Yin4vCzmUo7gPBp4Hb5AeQSHDNMdwyOoZK5XoqSbuAefCRF8Fi2gIp 5xmKJ8Ko1mHX7Ui5K+xgYPiyRzDV4KVrTam1ZhpwhvQ9NMdfiSV+kShnxIuKUr7P W93ua4LMyg79q985IbBhfkQh6L1xPuORFr0jcApyWq1j8Abbv48ARyBqH9clyJgF dBBwZJv1vZKHkaLNWBYGJbRBb8SjFEhD/9waZ+Hqfwka5sCi+6yFBYzWEV4Z/C02 MRH0ylgBIDSDbI4MlBDNRsumPPUYTwd4SKQOM7y1gKBeHbG7xLo96mIgffnD7zvo FqPXPqjJFbY5x59ldgxr7T0eDnEnVTTHyh5HlyskntBjMQO681Zrq2F748A6I9hD mreECPEGcVK5xG5IfzXLx494bJkvv0kkbPQ8Rx+MyOwYAyXvIpt0xUhdtoOHqOV2 gIMvf/44NT+GiRTlY2ps0gexGs/8IT0Qj/Iznxeeksdb0AW6Hwslz6pZNnTPmZRN Ld45wA7Eo8gWZKnVbcGpRs0kKW3IBAcSv+mJfr+osKM/05yAUDo= =GKAL -END PGP SIGNATURE-
Processed: closing 953693
Processing commands for cont...@bugs.debian.org: > close 953693 Bug #953693 [src:rust-lscolors] src:rust-lscolors: fails to migrate to testing for too long Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 953693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953693 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 953340
Processing commands for cont...@bugs.debian.org: > close 953340 Bug #953340 [src:rust-proc-macro-hack] src:rust-proc-macro-hack: fails to migrate to testing for too long Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 953340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953340 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): closing 955764
Processing commands for cont...@bugs.debian.org: > close 955764 Bug #955764 [librust-cargo-dev] librust-cargo-dev: dependencies unsatisfiable Marked Bug as done > version 0.43.1-1 Unknown command or malformed arguments to command. > thanks Stopping processing here. Please contact me if you need assistance. -- 955764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955764 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 953341
Processing commands for cont...@bugs.debian.org: > close 953341 Bug #953341 [src:rust-no-panic] src:rust-no-panic: fails to migrate to testing for too long Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 953341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953341 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 953193
Processing commands for cont...@bugs.debian.org: > close 953193 Bug #953193 [src:rust-idna] src:rust-idna: fails to migrate to testing for too long Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 953193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953193 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 954674
Processing commands for cont...@bugs.debian.org: > close 954674 Bug #954674 [src:rust-ucd-generate] rust-ucd-generate: FTBFS: unsatisfiable build-dependency: librust-ucd-parse-0.1+default-dev (>= 0.1.4-~~) (versioned dep on a virtual pkg?) Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 954674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954674 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 953194
Processing commands for cont...@bugs.debian.org: > close 953194 Bug #953194 [src:rust-unicode-xid] src:rust-unicode-xid: fails to migrate to testing for too long Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 953194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953194 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#951891: open-ath9k-htc-firmware FTBFS with binutils 2.34
> thank you! > > I updated the package. Hi, I see you've fixed this upstream. firmware-ath9k-htc has been removed from Bullseye, could you use some help with a new Debian package? signature.asc Description: This is a digitally signed message part.
Bug#958091: wtdbg2: Baseline violation on amd64/i386 and FTBFS everywhere else
This looks like something I can fix for all architectures and still respect the baselines with SIMDe, yes. On Sat, Apr 18, 2020 at 6:26 PM Andreas Tille wrote: > Hi Adrian, > > recently Michael Crusoe injected simde which should solve the SSE issue > in a more elegant way. Michael, would you comment on this whether we > should apply this patch or rather use simde here? > > Kind regards > > Andreas. > > On Sat, Apr 18, 2020 at 02:54:12PM +0300, Adrian Bunk wrote: > > On Sat, Apr 18, 2020 at 02:44:54PM +0300, Adrian Bunk wrote: > > > Source: wtdbg2 > > > Version: 2.5-1 > > > Severity: serious > > > Tags: ftbfs patch > > > > > > https://buildd.debian.org/status/package.php?p=wtdbg2 > > > > > > ... > > > gcc: error: unrecognized command line option ‘-mpopcnt’ > > > gcc: error: unrecognized command line option ‘-msse4.2’ > > > make[1]: *** [Makefile:27: kbm2] Error 1 > > > > > > > > > Fix attached. > > > > Additionally the package should become > > Architecture: any-amd64 > > and the i386 package removed. > > > > It uses SSE (but not SSE4.2) unconditionally, so cannot be built > > on i386 without baseline violation and in any case not anywhere else. > > > > cu > > Adrian > > > > ___ > > Debian-med-packaging mailing list > > debian-med-packag...@alioth-lists.debian.net > > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging > > -- > http://fam-tille.de > -- Michael R. Crusoe
Bug#958115: marked as done (ERROR: No runner implements step with keys device, set)
Your message dated Sat, 18 Apr 2020 18:31:41 +0200 with message-id <801f72a742ddbfb0ebb8f053631a9560247819f4.camel@jff.email> and subject line Re: Bug#958115: ERROR: No runner implements step with keys device, set has caused the Debian Bug report #958115, regarding ERROR: No runner implements step with keys device, set 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.) -- 958115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958115 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: autopkgtest Version: 5.12.1 Severity: grave File: /usr/bin/autopkgtest-build-qemu -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello, with autopkgtest-build-qemu sid sid-autopkgtest-amd64.img MIRROR amd64 I get following messages: [quote] Using http://10.200.1.1:3142 as container proxy Load spec file /tmp/tmp.gpIbr1ixwI ERROR: No runner implements step with keys device, set [/quote] CU Jörg - -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (300, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.5.0-1-amd64 (SMP w/6 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages autopkgtest depends on: ii apt-utils 2.0.2 ii libdpkg-perl1.19.7 ii procps 2:3.3.16-4 ii python3 3.8.2-3 ii python3-debian 0.1.36 Versions of packages autopkgtest recommends: ii autodep8 0.22 Versions of packages autopkgtest suggests: pn lxc pn lxd ii ovmf 0.0~20200229-2 pn qemu-efi-aarch64 pn qemu-efi-arm pn qemu-system ii qemu-utils1:4.2-3 ii schroot 1.6.10-9 ii vmdb2 0.14.1-1 - -- no debconf information -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAl6bKQ8ACgkQCfifPIyh 0l1uwxAAtLP0FBAQpDtGdorKB7asnXfwn0TzRlI0kNTVBnnZV9JtxnnAagWUebiw p8PAyCGOC4OiLCj/e4WNldqUEDZfG7kURqhfPiCZmxOEKxRSAs8+D4h9PNQV+VPG DD3hDxT/4PqnWJTyhWGhRcJj1tgqmvt1s9TqR8vtAhkqIFzdcMDzLR/kNgCEQ+rf tgRKhEQ0VSHt5pivcuvoU75Sey+OqCAxqZR7n2ZdP+KPDJ7XOwqoVjgkE2Pp7HTt AXsoSm9wcLsylQWIaALH5DtO1QXTNYkNmG9hF4xgIHmwbK5IVeTaabW11mAcN1Xw +rHSONnvc7+qKe+KAVGpVXboga/jsdAUy9AKt2RJ6iCNF5jaOYw8ldBfk4H85/RT /63xHOS2aiLZoHK1sHv/ZwMwibHPFnqchNCqWe3HqCHPDigCpsGqMuakb3EqJ1KG VygJmYSXGj3G6EPVLoxaGAshY0EQ9fk+ItoRaS55ZUpQ7XEcKgaW/Kzkt+JDLrNo lqoWPk2AkJczoQsW0MR4jRwK7d8bCbHbsCxtiC1a+cxEmjC91oPnYqXaKVYYOpDC yHoNISny+3OgY4pjiIY31u2tprynW+BKp9+ktOaISorBkMFMEQb/TudLIvm2mUqA Ye/Hdx8s84YM2xoOc6r8Wh88so8Onsn8UJ7zRq4X5QWe6Gawme0= =3nDv -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Hallo, this bug was fixed in unstable. Closed. CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old pgp Key: BE581B6E (revoked since 2014-12-31). Jörg Frings-Fürst D-54470 Lieser git: https://jff.email/cgit/ Threema: SYR8SJXB Wire: @joergfringsfuerst Skype:joergpenguin Ring: jff Telegram: @joergfringsfuerst My wish list: - Please send me a picture from the nature at your home. signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#958115: ERROR: No runner implements step with keys device, set
Hallo, this bug was fixed in unstable. Closed. CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old pgp Key: BE581B6E (revoked since 2014-12-31). Jörg Frings-Fürst D-54470 Lieser git: https://jff.email/cgit/ Threema: SYR8SJXB Wire: @joergfringsfuerst Skype:joergpenguin Ring: jff Telegram: @joergfringsfuerst My wish list: - Please send me a picture from the nature at your home. signature.asc Description: This is a digitally signed message part
Bug#958091: wtdbg2: Baseline violation on amd64/i386 and FTBFS everywhere else
Hi Adrian, recently Michael Crusoe injected simde which should solve the SSE issue in a more elegant way. Michael, would you comment on this whether we should apply this patch or rather use simde here? Kind regards Andreas. On Sat, Apr 18, 2020 at 02:54:12PM +0300, Adrian Bunk wrote: > On Sat, Apr 18, 2020 at 02:44:54PM +0300, Adrian Bunk wrote: > > Source: wtdbg2 > > Version: 2.5-1 > > Severity: serious > > Tags: ftbfs patch > > > > https://buildd.debian.org/status/package.php?p=wtdbg2 > > > > ... > > gcc: error: unrecognized command line option ‘-mpopcnt’ > > gcc: error: unrecognized command line option ‘-msse4.2’ > > make[1]: *** [Makefile:27: kbm2] Error 1 > > > > > > Fix attached. > > Additionally the package should become > Architecture: any-amd64 > and the i386 package removed. > > It uses SSE (but not SSE4.2) unconditionally, so cannot be built > on i386 without baseline violation and in any case not anywhere else. > > cu > Adrian > > ___ > Debian-med-packaging mailing list > debian-med-packag...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging -- http://fam-tille.de
Bug#958115: ERROR: No runner implements step with keys device, set
Package: autopkgtest Version: 5.12.1 Severity: grave File: /usr/bin/autopkgtest-build-qemu -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello, with autopkgtest-build-qemu sid sid-autopkgtest-amd64.img MIRROR amd64 I get following messages: [quote] Using http://10.200.1.1:3142 as container proxy Load spec file /tmp/tmp.gpIbr1ixwI ERROR: No runner implements step with keys device, set [/quote] CU Jörg - -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (300, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.5.0-1-amd64 (SMP w/6 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages autopkgtest depends on: ii apt-utils 2.0.2 ii libdpkg-perl1.19.7 ii procps 2:3.3.16-4 ii python3 3.8.2-3 ii python3-debian 0.1.36 Versions of packages autopkgtest recommends: ii autodep8 0.22 Versions of packages autopkgtest suggests: pn lxc pn lxd ii ovmf 0.0~20200229-2 pn qemu-efi-aarch64 pn qemu-efi-arm pn qemu-system ii qemu-utils1:4.2-3 ii schroot 1.6.10-9 ii vmdb2 0.14.1-1 - -- no debconf information -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAl6bKQ8ACgkQCfifPIyh 0l1uwxAAtLP0FBAQpDtGdorKB7asnXfwn0TzRlI0kNTVBnnZV9JtxnnAagWUebiw p8PAyCGOC4OiLCj/e4WNldqUEDZfG7kURqhfPiCZmxOEKxRSAs8+D4h9PNQV+VPG DD3hDxT/4PqnWJTyhWGhRcJj1tgqmvt1s9TqR8vtAhkqIFzdcMDzLR/kNgCEQ+rf tgRKhEQ0VSHt5pivcuvoU75Sey+OqCAxqZR7n2ZdP+KPDJ7XOwqoVjgkE2Pp7HTt AXsoSm9wcLsylQWIaALH5DtO1QXTNYkNmG9hF4xgIHmwbK5IVeTaabW11mAcN1Xw +rHSONnvc7+qKe+KAVGpVXboga/jsdAUy9AKt2RJ6iCNF5jaOYw8ldBfk4H85/RT /63xHOS2aiLZoHK1sHv/ZwMwibHPFnqchNCqWe3HqCHPDigCpsGqMuakb3EqJ1KG VygJmYSXGj3G6EPVLoxaGAshY0EQ9fk+ItoRaS55ZUpQ7XEcKgaW/Kzkt+JDLrNo lqoWPk2AkJczoQsW0MR4jRwK7d8bCbHbsCxtiC1a+cxEmjC91oPnYqXaKVYYOpDC yHoNISny+3OgY4pjiIY31u2tprynW+BKp9+ktOaISorBkMFMEQb/TudLIvm2mUqA Ye/Hdx8s84YM2xoOc6r8Wh88so8Onsn8UJ7zRq4X5QWe6Gawme0= =3nDv -END PGP SIGNATURE-
Bug#955638: marked as done (cargo: please package recent version)
Your message dated Sat, 18 Apr 2020 15:35:58 + with message-id and subject line Bug#955638: fixed in rust-cargo 0.43.1-1 has caused the Debian Bug report #955638, regarding cargo: please package recent version 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.) -- 955638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955638 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cargo Version: 0.40.0-3 Severity: wishlist Dear Maintainer, I'm working on packaging current beta versions of Thunderbird for experimental. This is requiring a cargo version >= 1.41 (cargo --version). Could you please consider to package the most recent version at least for experimental? Thanks and regards Carsten -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-4-amd64 (SMP w/6 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cargo depends on: ii binutils 2.34-5 ii clang 1:9.0-49.1 ii clang-7 [c-compiler] 1:7.0.1-12 ii clang-8 [c-compiler] 1:8.0.1-9 ii clang-9 [c-compiler] 1:9.0.1-10 ii gcc [c-compiler] 4:9.2.1-3.1 ii gcc-6 [c-compiler]6.5.0-1 ii gcc-7 [c-compiler]7.5.0-5 ii gcc-8 [c-compiler]8.4.0-1 ii gcc-9 [c-compiler]9.3.0-8 ii libc6 2.30-4 ii libcurl3-gnutls 7.68.0-1 ii libgcc-s1 [libgcc1] 10-20200324-1 ii libgcc1 1:10-20200324-1 ii libgit2-280.28.4+dfsg.1-4 ii libssh2-1 1.8.0-2.1 ii libssl1.1 1.1.1d-2 ii rustc 1.40.0+dfsg1-5 ii zlib1g1:1.2.11.dfsg-2 cargo recommends no packages. Versions of packages cargo suggests: pn cargo-doc ii python33.8.2-2 -- no debconf information --- End Message --- --- Begin Message --- Source: rust-cargo Source-Version: 0.43.1-1 Done: Ximin Luo We believe that the bug you reported is fixed in the latest version of rust-cargo, 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 955...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ximin Luo (supplier of updated rust-cargo 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: Sat, 18 Apr 2020 16:14:45 +0100 Source: rust-cargo Architecture: source Version: 0.43.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Ximin Luo Closes: 955638 Changes: rust-cargo (0.43.1-1) unstable; urgency=medium . * Package cargo 0.43.1 from crates.io using debcargo 2.4.2 * Closes: #955638 Checksums-Sha1: 959e26135984f0a8abc37292a3008a8997824dd8 5271 rust-cargo_0.43.1-1.dsc 23ccecc5ba8cbfac61c57cbff54e5b8c1ec38633 1119258 rust-cargo_0.43.1.orig.tar.gz 69af4a094da9cc31ef953dce07be6df9e7f49b52 4744 rust-cargo_0.43.1-1.debian.tar.xz 870678fe7f2344e6a2fc5606c241fa0249cc1fac 6596 rust-cargo_0.43.1-1_source.buildinfo Checksums-Sha256: ddefb469f04ba801472fa4c7bd030e354f82e3f84db28ffb117fd209bcd7da73 5271 rust-cargo_0.43.1-1.dsc 91de5749ddcea3c283a042b67b77e2bdf68f28374cdcbfbe54e91368810d92e5 1119258 rust-cargo_0.43.1.orig.tar.gz 4f7c5d9894f7f6af29a4284bd4e2392376964c5966be1ab019ebcaca41ba29f7 4744 rust-cargo_0.43.1-1.debian.tar.xz 9682c7f8547322abbf4d01cc1f415c2671da66a7cf2cc3b68812a203324b948e 6596 rust-cargo_0.43.1-1_source.buildinfo Files: c8ab2b93d60c6dee7789c571872526c9 5271 rust optional rust-cargo_0.43.1-1.dsc 315d96ce261418e6f75b1e4e782c59ec 1119258 rust optional rust-cargo_0.43.1.orig.tar.gz ae4584d023e7093609828f957f974fa7 4744 rust optional rust-cargo_0.43.1-1.debian.tar.xz 1b43cd36d6a7883a6f2ddd705f74d8d6 6596 rust optional rust-cargo_0.43.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iHUEARYKAB0WIQReYinNQ9GpZ9TYcRrrH8jaRfspMAUCXpsZaAAKCRDrH8jaRfsp MKMYAQDb55jI8IZM1EXRIK7rkNBW3VowtNF3tIOucW3HVDgg6AD7B4mo8ucktbjR s/vy7RSR/KBaXgEm62q9g9Eh+kJmCw8= =RSCy
Bug#955638: [Pkg-rust-maintainers] Bug#955638: cargo: please package recent version
Hi Carsten, cargo 0.43.1 has been packaged and source-only uploaded, however for it to be built, it will have to wait for the following packages to clear NEW: rust-bitmaps_2.1.0-1_amd64.ftp-master.upload rust-im-rc_14.3.0-1_amd64.ftp-master.upload rust-sized-chunks_0.6.1-1_amd64.ftp-master.upload I will ping them to hopefully get a bit more priority. Best, Ximin Carsten Schoenert: > Hello Ximin, > > Am 04.04.20 um 02:17 schrieb Ximin Luo: >> Hi Carsten, it might be a couple of weeks until we get this done. >> Have you tried just deleting the version constraint and using the >> existing version in Debian sid? > I've tried to figure out the right place there this version check is > happen. In most cases this is file ./old-configure.in within the > Thunderbird sources. But I did have no luck on this until now. I will > look further into this part this weekend I guess, mostly the version > checks from the Firefox environment are to strict for Thunderbird, yes. > Most of the parts from the Firefox source are not built for Thunderbird > but the configure script is checking this. > > In the long term this is always just a workaround which, if I do this, I > need to proof deeply before uploading new packages even to experimental. > So if you ever find time to have a look into newer cargo versions please > keep an eye on this. > > It's currently really frustrating that I'm unable to build a recent > Thunderbird Beta version due every time new version dependencies around > Rust are popping up. This is not your fault, but shows me how complex > and fragile the Rust ecosystem currently is. > > The built is just the first problem I need to solve, Mozilla has again > changed some previously internally parts in Thunderbird and I need to > adopt the Debian built to this again. > -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git
Bug#958109: macs: FTBFS on amd64/unstable: ERROR: Could not find an activated virtualenv (required).
Source: macs
Version: 2.2.7.1-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Tags: fbtfs
Dear Maintainer,
macs fails to build from source in unstable/amd64:
[…]
dpkg-buildpackage: info: source package macs
dpkg-buildpackage: info: source version 2.2.7.1-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Michael R. Crusoe
dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
dpkg-source: info: using options from macs-2.2.7.1/debian/source/options:
--extend-diff-ignore=(^|/)(.*\.c)$|.*[.]egg-info/
debian/rules clean
dh clean --with python3 --buildsystem=pybuild
debian/rules override_dh_auto_clean
make[1]: Entering directory
'/home/lamby/temp/cdt.20200418155953.LXW30yzBUr.repro.macs/build-a/macs-2.2.7.1'
dh_auto_clean
I: pybuild base:217: python3.8 setup.py clean
ERROR: Could not find an activated virtualenv (required).
Traceback (most recent call last):
File "setup.py", line 103, in
main()
File "setup.py", line 41, in main
raise RuntimeError("Installing requirements failed!")
RuntimeError: Installing requirements failed!
E: pybuild pybuild:352: clean: plugin distutils failed with: exit code=1:
python3.8 setup.py clean
dh_auto_clean: error: pybuild --clean --test-pytest -i python{version} -p 3.8
returned exit code 13
make[1]: *** [debian/rules:45: override_dh_auto_clean] Error 25
make[1]: Leaving directory
'/home/lamby/temp/cdt.20200418155953.LXW30yzBUr.repro.macs/build-a/macs-2.2.7.1'
make: *** [debian/rules:14: clean] Error 2
dpkg-buildpackage: error: debian/rules clean subprocess returned exit status 2
[…]
The full build log is attached.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
macs.2.2.7.1-1.unstable.amd64.log.txt.gz
Description: Binary data
Bug#947437: flang in bullseye - llvm 11 ?
Le 18/04/2020 à 16:10, Alastair McKinstry a écrit : Hi, flang is now merged into LLVM base. I can build flang/f18 from the LLVM main install, but this targets llvm-11. Are we likely to have llvm-11 (not necessarily default) in Debian Bullseye ? what approach should be taken ? Quite likely. I think llvm 11 will be released end of 2020 / early 2021 and is already available in experimental. Cheers, Sylvestre
Bug#956166: marked as done (gnome-shell-extension-easyscreencast: uninstallable in unstable, please update for GNOME Shell 3.36.x)
Your message dated Sat, 18 Apr 2020 15:06:39 +
with message-id
and subject line Bug#956166: fixed in gnome-shell-extension-easyscreencast
1.1.0-2
has caused the Debian Bug report #956166,
regarding gnome-shell-extension-easyscreencast: uninstallable in unstable,
please update for GNOME Shell 3.36.x
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.)
--
956166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956166
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-easyscreencast
Version: 1.0.2+git20191008-1
Severity: importan
Tags: bullseye sid upstream
Control: block 954422 by -1
Forwarded: https://github.com/EasyScreenCast/EasyScreenCast/issues/247
GNOME Shell 3.36.x is currently in experimental, and should hopefully
be heading to unstable soon. Please check whether this extension is
compatible.
You'll probably want to add a Recommends or even Depends on
gnome-shell-extension-prefs, a new package split out from gnome-shell that
is meant to be taking over responsibility for enabling and disabling
extensions from gnome-tweaks (at the moment they both offer this,
but there's a gnome-tweaks merge request open to remove the duplicate
functionality).
One thing that is definitely not compatible is that this extension runs:
Main.Util.trySpawnCommandLine('gnome-shell-extension-prefs
easyscreenc...@iacopodeenosee.gmail.com');
This is no longer supported since GNOME Shell 3.36.1:
gnome-shell-extension-prefs no longer takes a UUID as a command-line
argument. Some of the Debian GNOME team have wondered whether it's
feasible to patch back in, but the code involved is surprisingly
extensive, so the answer might be no.
As far as I can tell from GNOME Shell's upstream commit history, the
preferred way to launch extension preferences in sufficiently recent
versions is to call imports.misc.extensionUtils.openPrefs(), which
was added by gnome-shell!1163. It isn't in 3.36.1, but the version
in experimental (which is halfway between upstream 3.36.1 and 3.36.2)
does have it.
To support older GNOME versions, fall back to the spawn call if
imports.misc.extensionUtils doesn't have an openPrefs method.
Sample code:
https://github.com/Tudmotu/gnome-shell-extension-clipboard-indicator/pull/203
Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-easyscreencast
Source-Version: 1.1.0-2
Done: Samuel Henrique
We believe that the bug you reported is fixed in the latest version of
gnome-shell-extension-easyscreencast, 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 956...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Samuel Henrique (supplier of updated
gnome-shell-extension-easyscreencast 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: Sat, 18 Apr 2020 15:20:03 +0100
Source: gnome-shell-extension-easyscreencast
Architecture: source
Version: 1.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers
Changed-By: Samuel Henrique
Closes: 956166
Changes:
gnome-shell-extension-easyscreencast (1.1.0-2) unstable; urgency=medium
.
* d/control: Declare compatibility with gnome 3.36 (closes: #956166)
* d/control: Add Rules-Requires-Root: no
Checksums-Sha1:
fa785d00820f70a50f0fcedae342aa187384f64f 2350
gnome-shell-extension-easyscreencast_1.1.0-2.dsc
72350575db95469ecc30cfad6497e134c00b16b4 4472
gnome-shell-extension-easyscreencast_1.1.0-2.debian.tar.xz
0da8c02a8e59a7e0fd7a615adfc31c7ff54ce86d 6007
gnome-shell-extension-easyscreencast_1.1.0-2_amd64.buildinfo
Checksums-Sha256:
e3405324860ea244ccc59feeb29a1cfd96ac67ff0d8fa2c9cafe808b14637d4d 2350
gnome-shell-extension-easyscreencast_1.1.0-2.dsc
997f31de498a7dada07a80f7d94de3d460da975c544a8e46ab3b525c5ad96057 4472
gnome-shell-extension-easyscreencast_1.1.0-2.debian.tar.xz
7a9fc39de6cbdbc3297e7f82efe60528a1233e2ae1df9f738a7ec62f2596137b 6007
gnome-shell-extension-easyscreencast_1.1.0-2_amd64.buildinfo
Files:
67ee3d3708211d1b87130c19c0f31b1a 2350 gnome optional
gnome-shell-extension-easyscreencast_1.1.0-2.dsc
fb3420464f9c0d065f4e328297ad124d 4472 gnome
Bug#938596: marked as done (sugar-write-activity: Python2 removal in sid/bullseye)
Your message dated Sat, 18 Apr 2020 15:08:23 + with message-id and subject line Bug#938596: fixed in sugar-write-activity 101-1 has caused the Debian Bug report #938596, regarding sugar-write-activity: 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.) -- 938596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938596 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:sugar-write-activity Version: 100-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:sugar-write-activity 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: sugar-write-activity Source-Version: 101-1 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of sugar-write-activity, 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 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated sugar-write-activity 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: Sat, 18 Apr 2020 16:23:08 +0200 Source: sugar-write-activity Architecture: source Version: 101-1 Distribution: unstable Urgency: medium Maintainer: Debian Sugar Team Changed-By: Jonas Smedegaard Closes: 938596 Changes: sugar-write-activity (101-1) unstable; urgency=medium . [ upstream ] * new release . [ Jonas Smedegaard ] * stop recommend gir1.2-gstreamer-1.0 gstreamer1.0-espeak * (build-)depend on python3 modules (not python); build-depend on dh-python; closes: bug#938596, thanks to Matthias Klose * watch: + simplify regular expressions; + rewrite usage comment; + use substitution strings * use debhelper compatibility level 10 (not 9) * declare compliance with Debian Policy 4.5.0 * copyright: extend coverage Checksums-Sha1: 9053b138cdde49090fe5129f23fd40e0a91c3367 2070 sugar-write-activity_101-1.dsc
Bug#938593: marked as done (sugar-read-activity: Python2 removal in sid/bullseye)
Your message dated Sat, 18 Apr 2020 14:39:59 + with message-id and subject line Bug#938593: fixed in sugar-read-activity 123-1 has caused the Debian Bug report #938593, regarding sugar-read-activity: 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.) -- 938593: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938593 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:sugar-read-activity Version: 121-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:sugar-read-activity 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: sugar-read-activity Source-Version: 123-1 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of sugar-read-activity, 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 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated sugar-read-activity 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: Sat, 18 Apr 2020 16:04:11 +0200 Source: sugar-read-activity Architecture: source Version: 123-1 Distribution: unstable Urgency: medium Maintainer: Debian Sugar Team Changed-By: Jonas Smedegaard Closes: 938593 Changes: sugar-read-activity (123-1) unstable; urgency=medium . [ upstream ] * new release(s) . [ Jonas Smedegaard ] * copyright: extend coverage * declare compliance with Debian Policy 4.5.0 * use debhelper compatibility level 10 (not 9) * stop rename locale ibo (no longer shipped upstream) * (build-)depend on python3 modules (not python); build-depend on dh-python; closes: bug#938593, thanks to Matthias Klose Checksums-Sha1: 5eb9afcb793f529109e6c4cf756bc545f8d2ff59 2103 sugar-read-activity_123-1.dsc f454e953dd84f55d3a089487c88854e57d8ed1d9 96959 sugar-read-activity_123.orig.tar.bz2
Bug#938592: marked as done (sugar-pippy-activity: Python2 removal in sid/bullseye)
Your message dated Sat, 18 Apr 2020 14:39:53 + with message-id and subject line Bug#938592: fixed in sugar-pippy-activity 75-1 has caused the Debian Bug report #938592, regarding sugar-pippy-activity: 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.) -- 938592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938592 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:sugar-pippy-activity Version: 72~dfsg-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:sugar-pippy-activity 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: sugar-pippy-activity Source-Version: 75-1 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of sugar-pippy-activity, 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 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated sugar-pippy-activity 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: Sat, 18 Apr 2020 15:37:03 +0200 Source: sugar-pippy-activity Architecture: source Version: 75-1 Distribution: unstable Urgency: medium Maintainer: Debian Sugar Team Changed-By: Jonas Smedegaard Closes: 912501 938592 Changes: sugar-pippy-activity (75-1) unstable; urgency=medium . [ upstream ] * new release(s) . [ Jonas Smedegaard ] * copyright: stop repackage upstream source: no longer includes convenience code copies of external code projects * stop rename ISO 639-2 locale ibo: dropped upstream * use code copy of python-elements (dead upstream); drop patch 2001; stop suggest python-elements * use debhelper compatibility level 10 (not 9) * declare compliance with Debian Policy 4.5.0 * watch: + simplify regular expressions; + rewrite usage comment; + use substitution strings; + use
Bug#942338: marked as done (python3-nmea2: missing Breaks+Replaces: python-nmea2)
Your message dated Sat, 18 Apr 2020 14:39:46 + with message-id and subject line Bug#942338: fixed in python-nmea2 1.15.0-1.2 has caused the Debian Bug report #942338, regarding python3-nmea2: missing Breaks+Replaces: python-nmea2 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.) -- 942338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942338 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-nmea2 Version: 1.15.0-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 'testing'. It installed fine in 'testing', then the upgrade to 'sid' 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 .../python3-nmea2_1.15.0-1.1_all.deb ... Unpacking python3-nmea2 (1.15.0-1.1) ... dpkg: error processing archive /var/cache/apt/archives/python3-nmea2_1.15.0-1.1_all.deb (--unpack): trying to overwrite '/usr/share/doc-base/python-nmea2', which is also in package python-nmea2 1.12.0-1 Errors were encountered while processing: /var/cache/apt/archives/python3-nmea2_1.15.0-1.1_all.deb cheers, Andreas python-nmea2=1.12.0-1_python3-nmea2=1.15.0-1.1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: python-nmea2 Source-Version: 1.15.0-1.2 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of python-nmea2, 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 942...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated python-nmea2 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, 13 Apr 2020 16:28:54 +0300 Source: python-nmea2 Architecture: source Version: 1.15.0-1.2 Distribution: unstable Urgency: medium Maintainer: Ulises Vitulli Changed-By: Adrian Bunk Closes: 942338 Changes: python-nmea2 (1.15.0-1.2) unstable; urgency=medium . * Non-maintainer upload. * python3-nmea2: Add the missing Breaks+Replaces: python-nmea2 (Closes: #942338) Checksums-Sha1: 54ed285330345c9d39c45ebd85f2eeeb54819ff6 1849 python-nmea2_1.15.0-1.2.dsc a58558988fd5d1297667b197c8663718926373fd 50436 python-nmea2_1.15.0-1.2.debian.tar.xz Checksums-Sha256: c3808788973cb50cb616e4ca25e63662cdf638fe8f39058fd21ca0fbfba02372 1849 python-nmea2_1.15.0-1.2.dsc 87feaaf0b3e96304d96ed705fb09a77623263391b1ea84d2a68295e4b741ef79 50436 python-nmea2_1.15.0-1.2.debian.tar.xz Files: ede0802db94a0ab9a424d748c8bd7d0c 1849 python optional python-nmea2_1.15.0-1.2.dsc 256bcc03171bb6b25d7128576eca7262 50436 python optional python-nmea2_1.15.0-1.2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl6UabgACgkQiNJCh6LY mLFzAg/6A99dGFCQfPwAHB4Q0DMr0r/7jygGI6FQn1A/K7Pl8igGujReMZ34pQxj LXRa55K4KQBkZGVXDGm7iAKVwtSBezjYaqwB5g5UgQsFcZGfWqNv2GjSIR6I2GpA qhJvNtgMAORSNYSD5OddPWCUH5MaJ3Q4wOwszLebB4ccK8CET0qiTfgn6n/60OD1 /LHwL3JwdoDZYaRNFdfLl5H2vM7EXWwbbXMLYwkaeM1ARX3n5dh+vl8VWqzEaa83 m2QPpJlumW9uFjXzx+fRS56gnqyv7YNRBsSokVjB8uSWRmgdyK91Ds4i6fp2Q+Fg d2v88AxMshRIbUl7G9gtBG9jkLkvKwaUaXkSwrA8mwScqvibC7dWrYekvg2SI4iH rp5nDXloVZrUY1G+oqAo0XLNdR0pzPIJ0GE0pJiu6ZUweTyxEjpu1rsJjoVAnyxC Xa6fXvtqlWX5Eobe6VPAyzUrZjGs1zL5d8bUeb219s2S2y9GZoBZRokgIzY+0Dky rDTE9Ytim08nejf05E92EdF/Rjej8TDA68HUdobsarQYoeGHkEBs5xxbmReeXZ1r v9ogab+1WQRUDQigXhi2mgiG4I0nJSdPP0F4G0N4TmhICtGMuO91VD+rO8V8sUNA GoBJoqg5WveLT1HmOnXwP/MW3obb8Jy5CE2W42tPqECjemTrFEs= =LKxR -END PGP SIGNATURE End Message ---
Bug#943080: marked as done (fonts-monoid: Python2 removal in sid/bullseye)
Your message dated Sat, 18 Apr 2020 14:35:44 + with message-id and subject line Bug#943080: fixed in fonts-monoid 0.61-2.1 has caused the Debian Bug report #943080, regarding fonts-monoid: 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.) -- 943080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943080 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fonts-monoid Version: 0.61-2 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: fonts-monoid Source-Version: 0.61-2.1 Done: Gunnar Hjalmarsson We believe that the bug you reported is fixed in the latest version of fonts-monoid, 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 943...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gunnar Hjalmarsson (supplier of updated fonts-monoid 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, 06 Apr 2020 17:45:00 +0200 Source: fonts-monoid Architecture: source Version: 0.61-2.1 Distribution: unstable Urgency: medium Maintainer: Debian Fonts Task Force Changed-By: Gunnar Hjalmarsson Closes: 943080 Changes: fonts-monoid (0.61-2.1) unstable; urgency=medium . * Non-maintainer upload. * Move to python3-fontforge: - Upload the commit done on the official salsa repo to move to Python3. Closes: #943080; LP: #1871140 Checksums-Sha1: a6e88e2f7ce006411bf47f0e141cdeafccf47b07 2248 fonts-monoid_0.61-2.1.dsc ba6e7bf53c98916153a37a375d5887c51912765e 5140 fonts-monoid_0.61-2.1.debian.tar.xz 762527121770979bb61c23311934cd7259808ea5 7558 fonts-monoid_0.61-2.1_amd64.buildinfo Checksums-Sha256: 855866fbda59af4c56ecfa84379a21b8970d147cdef9760326776c9c141d8d8b 2248 fonts-monoid_0.61-2.1.dsc f09b9717105d5d044c2be810e4563876a15b6b61f26550ead4b9dd51382b2167 5140 fonts-monoid_0.61-2.1.debian.tar.xz 9de46c8bd7e9e33472b556cac261949b10bd111a0c663beee7a1406a8c7779e7 7558 fonts-monoid_0.61-2.1_amd64.buildinfo Files:
Bug#947437: flang in bullseye - llvm 11 ?
Hi, flang is now merged into LLVM base. I can build flang/f18 from the LLVM main install, but this targets llvm-11. Are we likely to have llvm-11 (not necessarily default) in Debian Bullseye ? what approach should be taken ? regards Alastair -- Alastair McKinstry, , , https://diaspora.sceal.ie/u/amckinstry Misentropy: doubting that the Universe is becoming more disordered.
Bug#933001: marked as done (returns 1 to plymouth initramfs hook, breaks initramfs creation)
Your message dated Sat, 18 Apr 2020 14:07:11 -0400
with message-id
and subject line Re: Bug#933001: Acknowledgement (returns 1 to plymouth
initramfs hook, breaks initramfs creation)
has caused the Debian Bug report #933001,
regarding returns 1 to plymouth initramfs hook, breaks initramfs creation
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.)
--
933001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933001
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fontconfig
Version: 2.13.1-2
Severity: grave
After recent upgrades, initramfs update fails here. When I patch
/usr/share/initramfs-tools/hooks/plymouth with "set -x", this is what we
get. And this error handling = NOT helpfull.
+ '[' n = y ']'
+ cp -pP /usr/lib/x86_64-linux-gnu/libbsd.so.0.9.1
/var/tmp/mkinitramfs_n38cu7//usr/lib/x86_64-linux-gnu/libbsd.so.0.9.1
+ cp -a /usr/share/plymouth/themes/details
/var/tmp/mkinitramfs_n38cu7//usr/share/plymouth/themes
+ cp -a /usr/share/plymouth/themes/text
/var/tmp/mkinitramfs_n38cu7//usr/share/plymouth/themes
+ '[' -f /etc/os-release ']'
+ cp /etc/os-release /var/tmp/mkinitramfs_n38cu7/etc
+ case "${THEME_NAME}" in
+ cp /usr/share/plymouth/debian-logo.png
/var/tmp/mkinitramfs_n38cu7/usr/share/plymouth
+ mkdir -p /var/tmp/mkinitramfs_n38cu7/etc/fonts/conf.d
+ cp -a /etc/fonts/fonts.conf /var/tmp/mkinitramfs_n38cu7/etc/fonts
+ cp -rL /etc/fonts/conf.d/60-latin.conf
/var/tmp/mkinitramfs_n38cu7/etc/fonts/conf.d
+ mkdir -p /var/tmp/mkinitramfs_n38cu7/var/cache/fontconfig
+ mkdir -p /var/tmp/mkinitramfs_n38cu7/usr/local/share/fonts
+ '[' -e /usr/share/fonts/truetype/dejavu/DejaVuSerif.ttf ']'
+ mkdir -p /var/tmp/mkinitramfs_n38cu7/usr/share/fonts/truetype/dejavu
+ cp -a /usr/share/fonts/truetype/dejavu/DejaVuSerif.ttf
/var/tmp/mkinitramfs_n38cu7/usr/share/fonts/truetype/dejavu
+ cp -a /usr/share/fonts/truetype/dejavu/DejaVuSans.ttf
/var/tmp/mkinitramfs_n38cu7/usr/share/fonts/truetype/dejavu
+ fc-cache -s -y /var/tmp/mkinitramfs_n38cu7
E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
update-initramfs: failed for /boot/initrd.img-5.2.2+ with 1.
Ok, trying more verbosity, still does not work. I expect
"--really-force" to fix everything, but it doesn't.
+ fc-cache --verbose --really-force -s -y /var/tmp/mkinitramfs_OYu7kU
[/var/tmp/mkinitramfs_OYu7kU]/usr/share/fonts: caching, new cache contents: 0
fonts, 1 dirs
[/var/tmp/mkinitramfs_OYu7kU]/usr/share/fonts/truetype: caching, new cache
contents: 0 fonts, 1 dirs
[/var/tmp/mkinitramfs_OYu7kU]/usr/share/fonts/truetype/dejavu: caching, new
cache contents: 2 fonts, 0 dirs
[/var/tmp/mkinitramfs_OYu7kU]/usr/X11R6/lib/X11/fonts:
"/usr/X11R6/lib/X11/fonts": scanning error
[/var/tmp/mkinitramfs_OYu7kU]/usr/local/share/fonts: caching, new cache
contents: 0 fonts, 0 dirs
[/var/tmp/mkinitramfs_OYu7kU]/usr/share/fonts/truetype: skipping, looped
directory detected
[/var/tmp/mkinitramfs_OYu7kU]/usr/share/fonts/truetype/dejavu: skipping, looped
directory detected
/var/tmp/mkinitramfs_OYu7kU//var/cache/fontconfig: cleaning cache directory
fc-cache: failed
And now? The used font does exist!
$ debsums fonts-dejavu-core
/usr/share/doc/fonts-dejavu-core/AUTHORS OK
/usr/share/doc/fonts-dejavu-core/BUGS OK
/usr/share/doc/fonts-dejavu-core/README.mdOK
/usr/share/doc/fonts-dejavu-core/changelog.Debian.gz OK
/usr/share/doc/fonts-dejavu-core/changelog.gz OK
/usr/share/doc/fonts-dejavu-core/copyrightOK
/usr/share/doc/fonts-dejavu-core/langcover.txt.gz OK
/usr/share/doc/fonts-dejavu-core/status.txt.gzOK
/usr/share/doc/fonts-dejavu-core/unicover.txt.gz OK
/usr/share/fonts/truetype/dejavu/DejaVuSans-Bold.ttf OK
/usr/share/fonts/truetype/dejavu/DejaVuSans.ttf OK
/usr/share/fonts/truetype/dejavu/DejaVuSansMono-Bold.ttf OK
/usr/share/fonts/truetype/dejavu/DejaVuSansMono.ttf OK
/usr/share/fonts/truetype/dejavu/DejaVuSerif-Bold.ttf OK
/usr/share/fonts/truetype/dejavu/DejaVuSerif.ttf OK
EOF
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable'), (1,
'experimental-debug'), (1, 'experimental')
Bug#958105: ferm: v2.5 broke @ipfilter(), resulting in deferred=ARRAY(0x55b7a9219368) errors
Package: ferm Version: 2.5-1.1 Severity: serious Tags: upstream Dear Maintainer, Ferm got updated from v2.4 to v2.5, which brought a regression of @ipfilter() function, when used, resulting in an error. I believe the serious severity is warranted. The error makes it so that ferm doesn't apply any rules, so if you rely on ferm to setup firewall rules, your system would be unprotected. It might also break other software on the system which rely on the rules to be present. My particular issue is detailed in the upstream bug tracker https://github.com/MaxKellermann/ferm/issues/71. It looks like it was already fixed in master https://github.com/MaxKellermann/ferm/commit/cea364a246f6988c6dc7f1603586f58c11b7dc28, but the fix hasn't made it into any release yet.
Bug#949834: this is blocking listbugs on amd64
Please could this bug be tweaked to prevent the issue on other platforms ... Get:1 http://deb.debian.org/debian-security buster/updates/main amd64 firefox-esr amd64 68.7.0esr-1~deb10u1 [47.9 MB] Fetched 47.9 MB in 55s (865 kB/s) Retrieving bug reports... Done Parsing Found/Fixed information... Done critical bugs of firefox-esr (68.4.1esr-1~deb10u1 → 68.7.0esr-1~deb10u1) b1 - #949834 - [arm64] firefox-esr: illegal instruction in /usr/lib/firefox-esr/libxul.so Summary: firefox-esr(1 bug) Huge thanks, Bernie
Bug#938591: marked as done (sugar-memorize-activity: Python2 removal in sid/bullseye)
Your message dated Sat, 18 Apr 2020 13:36:03 + with message-id and subject line Bug#938591: fixed in sugar-memorize-activity 58-1 has caused the Debian Bug report #938591, regarding sugar-memorize-activity: 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.) -- 938591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938591 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:sugar-memorize-activity Version: 55-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:sugar-memorize-activity 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: sugar-memorize-activity Source-Version: 58-1 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of sugar-memorize-activity, 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 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated sugar-memorize-activity 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: Sat, 18 Apr 2020 15:16:33 +0200 Source: sugar-memorize-activity Architecture: source Version: 58-1 Distribution: unstable Urgency: medium Maintainer: Debian Sugar Team Changed-By: Jonas Smedegaard Closes: 938591 Changes: sugar-memorize-activity (58-1) unstable; urgency=medium . [ upstream ] * new release(s) . [ Jonas Smedegaard ] * use debhelper compatibility level 10 (not 9) * declare compliance with Debian Policy 4.5.0 * depend on gir1.2-telepathyglib-0.12 (not python3-telepathy) * (build-)depend on python3 modules (not python); build-depend on dh-python; closes: bug#938591, thanks to Matthias Klose * stop suggest legacy telepathy-gabble Checksums-Sha1: 6ce5e8c34fb2f21d01f1b1ea53517c421f5411c7 2106 sugar-memorize-activity_58-1.dsc ce14b11a6952e2bd97ccf9c044b269ddf46d66f1 705308
Bug#954812: [Python-modules-team] Bug#954812: pythonmagick: autopkgtest regression: cannot import name '_PythonMagick'
On April 18, 2020 10:03:01 AM UTC, Adrian Bunk wrote: >On Mon, Mar 23, 2020 at 09:43:19PM +0100, Paul Gevers wrote: >> Source: pythonmagick >> Version: 0.9.19-6 >> X-Debbugs-CC: debian...@lists.debian.org >> Severity: serious >> User: debian...@lists.debian.org >> Usertags: regression >> >> Dear maintainer(s), >> >> With a recent upload of pythonmagick the autopkgtest of pythonmagick >> fails in testing when that autopkgtest is run with the binary >packages >> of pythonmagick from unstable. It passes when run with only packages >> from testing. In tabular form: >> >>passfail >> pythonmagick from testing0.9.19-6 >> versioned deps [0] from testingfrom unstable >> all others from testingfrom testing >> >> I copied some of the output at the bottom of this report. >> >> Currently this regression is blocking the migration to testing [1]. >Can >> you please investigate the situation and fix it? >>... >> Testing with python3.7: >> + python3.7 >> Traceback (most recent call last): >> File "", line 1, in >> File "/usr/lib/python3/dist-packages/PythonMagick/__init__.py", >line >> 1, in >> from . import _PythonMagick >> ImportError: cannot import name '_PythonMagick' from 'PythonMagick' >>... > >This is not a regression in the package, the root cause is: >https://lists.debian.org/debian-release/2020/04/msg00228.html No. This one started to early to be caused by that issue. In this case the issue was that the autopkgtest was run for all installed python3 versions, but the package only builds for the default version. It's trivially fixable by making the autopkgtest run only for the default version, but it would be much better to solve it by having the package build for all supported python3 versions and running the autopkgtest against all of them. Scott K
Bug#938589: marked as done (sugar-jukebox-activity: Python2 removal in sid/bullseye)
Your message dated Sat, 18 Apr 2020 13:06:51 + with message-id and subject line Bug#938589: fixed in sugar-jukebox-activity 36-1 has caused the Debian Bug report #938589, regarding sugar-jukebox-activity: 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.) -- 938589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938589 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:sugar-jukebox-activity Version: 34-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:sugar-jukebox-activity 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: sugar-jukebox-activity Source-Version: 36-1 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of sugar-jukebox-activity, 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 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated sugar-jukebox-activity 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: Sat, 18 Apr 2020 14:45:58 +0200 Source: sugar-jukebox-activity Architecture: source Version: 36-1 Distribution: unstable Urgency: medium Maintainer: Debian Sugar Team Changed-By: Jonas Smedegaard Closes: 849092 938589 Changes: sugar-jukebox-activity (36-1) unstable; urgency=medium . [ upstream ] * new release(s) . [ Jonas Smedegaard ] * use debhelper compatibility level 10 (not 9) * declare compliance with Debian Policy 4.5.0 * (build-)depend on python3 modules (not python); build-depend on dh-python; closes: bug#849092, #938589, thanks to Sebastian Dröge and Matthias Klose Checksums-Sha1: 44f48df647d943edfa82bdf0cb04dccdb239637d 2088 sugar-jukebox-activity_36-1.dsc c628bc2a586c7036e9193eafb2059bc0e13ceadf 46149 sugar-jukebox-activity_36.orig.tar.bz2 a8ffcf1ef44dc939610d1640d362551fa8044d7c 5300
Bug#958102: exult FTBFS on architectures where char is unsigned
Source: exult Version: 1.6-1 Severity: serious Tags: ftbfs Forwarded: https://github.com/exult/exult/issues/37 https://buildd.debian.org/status/package.php?p=exult ... chunklst.cc: In constructor ‘Chunk_chooser::Chunk_chooser(Vga_file*, std::istream&, unsigned char*, int, int, Shape_group*)’: chunklst.cc:769:24: error: narrowing conversion of ‘-1’ from ‘int’ to ‘char’ [-Wnarrowing] 769 |}; |^ chunklst.cc:769:24: error: narrowing conversion of ‘-1’ from ‘int’ to ‘char’ [-Wnarrowing] chunklst.cc:769:24: error: narrowing conversion of ‘-1’ from ‘int’ to ‘char’ [-Wnarrowing] chunklst.cc:769:24: error: narrowing conversion of ‘-1’ from ‘int’ to ‘char’ [-Wnarrowing] make[3]: *** [Makefile:669: chunklst.o] Error 1
Bug#956673: marked as done (geophar: FTBFS with Python 3.8 only)
Your message dated Sat, 18 Apr 2020 12:48:48 +
with message-id
and subject line Bug#956673: fixed in geophar 18.08.6+dfsg1-3
has caused the Debian Bug report #956673,
regarding geophar: FTBFS with Python 3.8 only
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.)
--
956673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956673
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: geophar
Version: 18.08.6+dfsg1-1
Severity: serious
Tags: ftbfs bullseye sid
Hi Maintainer
Since Python 3.8 is now the only Python 3 interpreter, geophar FTBFS [1].
I've copied what I hope is the relevant part of the log below.
Regards
Graham
[1]
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/geophar.html
dh_auto_clean
E: Please add appropriate interpreter package to Build-Depends, see
pybuild(1) for details.this: $VAR1 = bless( {
'builddir' => undef,
'pydef' => '',
'pyvers' => '',
'parallel' => '16',
'py3def' => '3.8',
'cwd' => '/build/geophar-18.08.6+dfsg1',
'py3vers' => '',
'pypydef' => '',
'sourcedir' => '.'
}, 'Debian::Debhelper::Buildsystem::pybuild' );
deps: $VAR1 = [
'python3-all',
'python3-sympy',
'python3-numpy',
'python3-matplotlib',
'python3-dbus',
'python3-sip',
'python3-scipy',
'python3-pyqt5.qsci',
'python3-pyqt5.qtsvg'
];
make[1]: *** [debian/rules:15: override_dh_auto_clean] Error 25
make[1]: Leaving directory '/build/geophar-18.08.6+dfsg1'
make: *** [debian/rules:12: clean] Error 2
--- End Message ---
--- Begin Message ---
Source: geophar
Source-Version: 18.08.6+dfsg1-3
Done: Georges Khaznadar
We believe that the bug you reported is fixed in the latest version of
geophar, 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 956...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Georges Khaznadar (supplier of updated geophar 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: Sat, 18 Apr 2020 14:32:55 +0200
Source: geophar
Architecture: source
Version: 18.08.6+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar
Changed-By: Georges Khaznadar
Closes: 954432 956673
Changes:
geophar (18.08.6+dfsg1-3) unstable; urgency=medium
.
* upgraded X-Python3-Version: 3.8. Closes: #956673
* could not reproduce Bug ##954432, asked the bugreport's author to try
to erase stale configuration files, two weeks ago ... I got no
response so far; so I guess that geophar failed to start in one
particular machine in the world, and I know some other machines where
it does not fail. Now closing this bug report. Closes: #954432
Checksums-Sha1:
83c91fa57f69f86b927d2674eadfc7af15522e6b 2127 geophar_18.08.6+dfsg1-3.dsc
d3237d8703b7b3f7970338370896bb2d590b05db 16404
geophar_18.08.6+dfsg1-3.debian.tar.xz
f75e319c703a8827f0c2d9e5af80719ec2382164 11377
geophar_18.08.6+dfsg1-3_source.buildinfo
Checksums-Sha256:
6fb4a6cfc7237f95758f386f2292ed8273621ee79aff51952f7b2a091e06b880 2127
geophar_18.08.6+dfsg1-3.dsc
d78f011f42e265cbecf054a39af8f3195c65d026f9dd291e4d8950105da67fb1 16404
geophar_18.08.6+dfsg1-3.debian.tar.xz
9691d41ccf59465a2db745ac2e59c7b6a65df82755636bb309a81bc42b336a44 11377
geophar_18.08.6+dfsg1-3_source.buildinfo
Files:
44dc62feb3b43abbd255ba1a73b8462a 2127 math optional geophar_18.08.6+dfsg1-3.dsc
286f0e78cfcc6c088a05ec20cab9dce5 16404 math optional
geophar_18.08.6+dfsg1-3.debian.tar.xz
e6018c1902bb4454aabf84c960f43df9 11377 math optional
geophar_18.08.6+dfsg1-3_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJIBAEBCAAyFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAl6a87EUHGdlb3JnZXNr
QGRlYmlhbi5vcmcACgkQHCgWkHE2rjlIug/7B9fu3UxYhft+EO1xyXvLrEEC7Bsr
FVWC1d5pNCxzqJO6TyTs4xft7rhdHmVnds0Ry8e0SMEAsaA4Lx5Up0eoMj3FMWjE
OLEd5MDy6aGKlwBKHbMwozCJZUezrEuhLZUoBsrlajBoSVwVOttMacW7irM0FIxN
ffDISAVJd49h0f+xT7Uzlz0Ifa4P/wCk88CUTwESBRI49+ylFHb5DvOhpKwiUCE6
Bug#954432: marked as done (geophar: Fails to start)
Your message dated Sat, 18 Apr 2020 12:48:48 + with message-id and subject line Bug#954432: fixed in geophar 18.08.6+dfsg1-3 has caused the Debian Bug report #954432, regarding geophar: Fails to start 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.) -- 954432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954432 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: geophar Version: 18.08.6+dfsg1-1 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? Wanting to see if Geophar is useful to me. * What exactly did you do (or not do) that was effective (or ineffective)? I installed Geophar with its default dependencies from the package repository. After installing, I issued the following command in a terminal: geophar * What was the outcome of this action? After issuing the command in a terminal, the following lines were printed and the program exited: QSettings::value: Empty key passed QSettings::value: Empty key passed malloc(): unsorted double linked list corrupted Aborted * What outcome did you expect instead? The program to start and run. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages geophar depends on: ii jsmath 3.6e-2 ii python3 3.7.5-3 ii python3-kiwisolver 1.0.1-3 ii python3-matplotlib 3.1.2-2 ii python3-numpy1:1.17.4-5 ii python3-pep8 1.7.1-9 ii python3-pyqt55.14.1+dfsg-3 ii python3-pyqt5.qsci 2.11.2+dfsg-6 ii python3-pyqt5.qtsvg 5.14.1+dfsg-3 ii python3-scipy1.3.3-3 ii python3-stemmer 1.3.0+dfsg-2+b1 ii python3-sympy1.5.1-2.1 ii python3.73.7.7-1 Versions of packages geophar recommends: ii jsmath-fonts 1.3-3.1 ii libjs-mathjax 2.7.4+dfsg-1 Versions of packages geophar suggests: ii apache2 [httpd] 2.4.41-5 -- no debconf information --- End Message --- --- Begin Message --- Source: geophar Source-Version: 18.08.6+dfsg1-3 Done: Georges Khaznadar We believe that the bug you reported is fixed in the latest version of geophar, 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 954...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Georges Khaznadar (supplier of updated geophar 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: Sat, 18 Apr 2020 14:32:55 +0200 Source: geophar Architecture: source Version: 18.08.6+dfsg1-3 Distribution: unstable Urgency: medium Maintainer: Georges Khaznadar Changed-By: Georges Khaznadar Closes: 954432 956673 Changes: geophar (18.08.6+dfsg1-3) unstable; urgency=medium . * upgraded X-Python3-Version: 3.8. Closes: #956673 * could not reproduce Bug ##954432, asked the bugreport's author to try to erase stale configuration files, two weeks ago ... I got no response so far; so I guess that geophar failed to start in one particular machine in the world, and I know some other machines where it does not fail. Now closing this bug report. Closes: #954432 Checksums-Sha1: 83c91fa57f69f86b927d2674eadfc7af15522e6b 2127 geophar_18.08.6+dfsg1-3.dsc d3237d8703b7b3f7970338370896bb2d590b05db 16404 geophar_18.08.6+dfsg1-3.debian.tar.xz f75e319c703a8827f0c2d9e5af80719ec2382164 11377 geophar_18.08.6+dfsg1-3_source.buildinfo Checksums-Sha256: 6fb4a6cfc7237f95758f386f2292ed8273621ee79aff51952f7b2a091e06b880 2127 geophar_18.08.6+dfsg1-3.dsc d78f011f42e265cbecf054a39af8f3195c65d026f9dd291e4d8950105da67fb1 16404 geophar_18.08.6+dfsg1-3.debian.tar.xz 9691d41ccf59465a2db745ac2e59c7b6a65df82755636bb309a81bc42b336a44 11377
Bug#958101: daq: Frequent parallel FTBFS
Source: daq Version: 2.0.6-2 Severity: serious Tags: ftbfs patch https://buildd.debian.org/status/fetch.php?pkg=daq=armhf=2.0.6-2=1585399576=0 https://buildd.debian.org/status/fetch.php?pkg=daq=ppc64el=2.0.6-2=1585397042=0 https://buildd.debian.org/status/fetch.php?pkg=daq=m68k=2.0.6-2=1585494536=0 https://buildd.debian.org/status/fetch.php?pkg=daq=powerpc=2.0.6-2=1585558490=0 https://buildd.debian.org/status/fetch.php?pkg=daq=ppc64=2.0.6-2=1585556385=0 https://buildd.debian.org/status/fetch.php?pkg=daq=sparc64=2.0.6-2=158721=0 ... libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -Dyylval=sfbpf_lval -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fvisibility=hidden -Wall -Wwrite-strings -Wsign-compare -Wcast-align -Wextra -Wformat-security -Wno-unused-parameter -fno-strict-aliasing -fdiagnostics-show-option -pedantic -std=c99 -D_GNU_SOURCE -c sf_bpf_filter.c -o libsfbpf_la-sf_bpf_filter.o >/dev/null 2>&1 ./scanner.l:70:10: fatal error: tokdefs.h: No such file or directory 70 | #include "tokdefs.h" | ^~~ compilation terminated. libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -Dyylval=sfbpf_lval -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fvisibility=hidden -Wall -Wwrite-strings -Wsign-compare -Wcast-align -Wextra -Wformat-security -Wno-unused-parameter -fno-strict-aliasing -fdiagnostics-show-option -pedantic -std=c99 -D_GNU_SOURCE -c sf_bpf_printer.c -o libsfbpf_la-sf_bpf_printer.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -Dyylval=sfbpf_lval -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fvisibility=hidden -Wall -Wwrite-strings -Wsign-compare -Wcast-align -Wextra -Wformat-security -Wno-unused-parameter -fno-strict-aliasing -fdiagnostics-show-option -pedantic -std=c99 -D_GNU_SOURCE -c sf_nametoaddr.c -o libsfbpf_la-sf_nametoaddr.o >/dev/null 2>&1 make[3]: *** [Makefile:552: libsfbpf_la-sf_scanner.lo] Error 1 make[3]: *** Waiting for unfinished jobs mv y.tab.c sf_grammar.c mv y.tab.h tokdefs.h ... Fix attached. Description: sfbpf/Makefile.am: Don't list generated files as sources This breaks Makefile dependencies. Author: Adrian Bunk --- daq-2.0.6.orig/sfbpf/Makefile.am +++ daq-2.0.6/sfbpf/Makefile.am @@ -37,8 +37,6 @@ sfbpf-int.h \ sfbpf-int.c \ runlex.sh -nodist_libsfbpf_la_SOURCES = sf_grammar.c sf_scanner.c tokdefs.h - libsfbpf_la_CFLAGS = -Dyylval=sfbpf_lval libsfbpf_la_LDFLAGS = -version-info 0:1:0 @XCCFLAGS@
Bug#938585: marked as done (sugar-chat-activity: Python2 removal in sid/bullseye)
Your message dated Sat, 18 Apr 2020 12:36:14 + with message-id and subject line Bug#938585: fixed in sugar-chat-activity 86-1 has caused the Debian Bug report #938585, regarding sugar-chat-activity: 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.) -- 938585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938585 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:sugar-chat-activity Version: 85-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:sugar-chat-activity 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: sugar-chat-activity Source-Version: 86-1 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of sugar-chat-activity, 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 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated sugar-chat-activity 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: Sat, 18 Apr 2020 14:11:26 +0200 Source: sugar-chat-activity Architecture: source Version: 86-1 Distribution: unstable Urgency: medium Maintainer: Debian Sugar Team Changed-By: Jonas Smedegaard Closes: 938585 Changes: sugar-chat-activity (86-1) unstable; urgency=medium . [ upstream ] * new release . [ Jonas Smedegaard ] * build-depend on python-dbus * declare compliance with Debian Policy 4.5.0 * (build-)depend on python3 modules (not python); build-depend on dh-python; closes: bug#938585, thanks to Matthias Klose * use debhelper compatibility level 10 (not 9) Checksums-Sha1: 9dd801d4e5cd88a14e02bcb6f4f542e08b15cec9 2052 sugar-chat-activity_86-1.dsc 1d0386d273f44cd1e9b8c081f87849742a7096e3 536606 sugar-chat-activity_86.orig.tar.gz 390a8d9fe163674e165479e580808ad0fa572612 8808 sugar-chat-activity_86-1.debian.tar.xz
Bug#953234: marked as done (recon-ng: autopkgtest regression: /home/debci/.recon-ng/workspaces/test/data.db does not exist)
Your message dated Sat, 18 Apr 2020 12:35:37 + with message-id and subject line Bug#953234: fixed in recon-ng 5.1.1-2 has caused the Debian Bug report #953234, regarding recon-ng: autopkgtest regression: /home/debci/.recon-ng/workspaces/test/data.db does not exist 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.) -- 953234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953234 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: recon-ng Version: 5.1.1-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainers, With a recent upload of recon-ng the autopkgtest of recon-ng fails in testing when that autopkgtest is run with the binary packages of recon-ng from unstable. It passes when run with only packages from testing. In tabular form: passfail recon-ngfrom testing5.1.1-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=recon-ng https://ci.debian.net/data/autopkgtest/testing/amd64/r/recon-ng/4466158/log.gz KALI.ORG [34m[*][m No vulnerabilites found. [recon-ng][default][xssed] > back [recon-ng][default] > ERROR: /home/debci/.recon-ng/workspaces/test/data.db does not exist signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: recon-ng Source-Version: 5.1.1-2 Done: Marcos Fouces We believe that the bug you reported is fixed in the latest version of recon-ng, 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 953...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marcos Fouces (supplier of updated recon-ng 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: Wed, 25 Mar 2020 14:05:35 +0100 Source: recon-ng Architecture: source Version: 5.1.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Security Tools Changed-By: Marcos Fouces Closes: 953234 Changes: recon-ng (5.1.1-2) unstable; urgency=medium . * Update some commands in autopkgtest file. (Closes:#953234) Checksums-Sha1: 92e49bbe8775a5406192d4c77b1f1b2764fdf60d 1697 recon-ng_5.1.1-2.dsc 96062244833310bf74c70596c4a3c5f0f24f39cd 8080 recon-ng_5.1.1-2.debian.tar.xz 2e523f5ebc3ebb8a19734f3322df17a3fbc70f04 6316 recon-ng_5.1.1-2_source.buildinfo Checksums-Sha256: 881efbc9612c793434c58dd6f6b6bfc90e8e234a10a31d481591a0156a447908 1697 recon-ng_5.1.1-2.dsc 2d9a6a3a8ca34b9cf45e6dd410ff6f44df385a62e9e16d8555a4320fbe82661a 8080 recon-ng_5.1.1-2.debian.tar.xz dfde9072a1276796ab1e116d1195fa7870f801274bccc7d70b2d2a9a7518ba72 6316 recon-ng_5.1.1-2_source.buildinfo Files: 43c5e3f76adf54e46c49a30dc739203a 1697 utils optional recon-ng_5.1.1-2.dsc b3d68cacf8f5c62d718d34d84463b29e 8080 utils optional recon-ng_5.1.1-2.debian.tar.xz a1603ed6567da407c34204c42faed3cc 6316 utils optional recon-ng_5.1.1-2_source.buildinfo -BEGIN PGP SIGNATURE- Comment: Signed by Raphael Hertzog iQEzBAEBCgAdFiEE1823g1EQnhJ1LsbSA4gdq+vCmrkFAl6a8E4ACgkQA4gdq+vC mrludAgAq/30gFo59w2DjJ//jRCcFhI4DI4OWWzt0bhM3TQXxtFprmYmOU4v7fTE wxNYs5IE+0PKBHr7NNLUPlbRg++SaoSegxEDVBGHQs4P2npEoqaVJd4SgW0nMVpm bsKclM2Tkq2YzFuO/9UkOPWUcgs7KrMH5dCJ+NPPeu5K7ljmoPNCDpylFQyAoXOf Gv5TFa0ss9zaAyZ18H0tnAjHaxWK2ZvzENhofMh0ULM4XqM73Sh9gwEZsbdQIwPl ShFgQi9/wncNArsMW8ppNTU+cJWiemg05oMMgjftXN+wSGzvME0UOVSLMHxWkWAc 8eOK6olpXSgbLj1GG4f6OO26AJP7NA== =Y1KI -END PGP SIGNATURE End Message ---
Bug#954812: [Python-modules-team] Bug#954812: pythonmagick: autopkgtest regression: cannot import name '_PythonMagick'
Hi! I'm working on this issue. Currently [1], the autopkgtest (from this package) has support for py38. Using pyversion -s to test all version supported give me some troubles, for now. [1] https://salsa.debian.org/python-team/modules/pythonmagick Cheers, Arias Emmanuel @eamanu http://eamanu.com El sáb., 18 de abr. de 2020 a la(s) 07:06, Adrian Bunk (b...@debian.org) escribió: > > On Mon, Mar 23, 2020 at 09:43:19PM +0100, Paul Gevers wrote: > > Source: pythonmagick > > Version: 0.9.19-6 > > X-Debbugs-CC: debian...@lists.debian.org > > Severity: serious > > User: debian...@lists.debian.org > > Usertags: regression > > > > Dear maintainer(s), > > > > With a recent upload of pythonmagick the autopkgtest of pythonmagick > > fails in testing when that autopkgtest is run with the binary packages > > of pythonmagick from unstable. It passes when run with only packages > > from testing. In tabular form: > > > >passfail > > pythonmagick from testing0.9.19-6 > > versioned deps [0] from testingfrom unstable > > all others from testingfrom testing > > > > I copied some of the output at the bottom of this report. > > > > Currently this regression is blocking the migration to testing [1]. Can > > you please investigate the situation and fix it? > >... > > Testing with python3.7: > > + python3.7 > > Traceback (most recent call last): > > File "", line 1, in > > File "/usr/lib/python3/dist-packages/PythonMagick/__init__.py", line > > 1, in > > from . import _PythonMagick > > ImportError: cannot import name '_PythonMagick' from 'PythonMagick' > >... > > This is not a regression in the package, the root cause is: > https://lists.debian.org/debian-release/2020/04/msg00228.html > > cu > Adrian > > ___ > Python-modules-team mailing list > python-modules-t...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
Bug#954901: ghostscript: runtime error: malloc(): invalid size (unsorted)
Sorry, the file I attached in message #10 was for a different bug, unrelated to this one. Created upstream bug: https://bugs.ghostscript.com/show_bug.cgi?id=702346
Bug#956405: marked as done (ruby-enumerable-statistics: FTBFS on amd64/unstable: find: [..] No such file or directory)
Your message dated Sat, 18 Apr 2020 12:19:02 + with message-id and subject line Bug#956405: fixed in ruby-enumerable-statistics 2.0.1+dfsg-3 has caused the Debian Bug report #956405, regarding ruby-enumerable-statistics: FTBFS on amd64/unstable: find: [..] No such file or directory 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.) -- 956405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956405 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-enumerable-statistics Version: 2.0.1+dfsg-2 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Tags: fbtfs Dear Maintainer, ruby-enumerable-statistics fails to build from source in unstable/amd64: […] dh_compress -X.rb -O--buildsystem=ruby debian/rules override_dh_fixperms make[1]: Entering directory '/home/lamby/temp/cdt.20200410190019.WRLDvzI39v.ags.ruby-enumerable-statistics/ruby-enumerable-statistics-2.0.1+dfsg' dh_fixperms find debian/ruby-enumerable-statistics/usr/lib/*/rubygems-integration/*/gems/enumerable-statistics-*/yard/templates/ -type f |xargs chmod -x find: 'debian/ruby-enumerable-statistics/usr/lib/*/rubygems-integration/*/gems/enumerable-statistics-*/yard/templates/': No such file or directory chmod: missing operand Try 'chmod --help' for more information. make[1]: *** [debian/rules:16: override_dh_fixperms] Error 123 make[1]: Leaving directory '/home/lamby/temp/cdt.20200410190019.WRLDvzI39v.ags.ruby-enumerable-statistics/ruby-enumerable-statistics-2.0.1+dfsg' make: *** [debian/rules:7: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 […] The full build log is attached. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- ruby-enumerable-statistics.2.0.1+dfsg-2.unstable.amd64.log.txt.gz Description: Binary data --- End Message --- --- Begin Message --- Source: ruby-enumerable-statistics Source-Version: 2.0.1+dfsg-3 Done: Pirate Praveen We believe that the bug you reported is fixed in the latest version of ruby-enumerable-statistics, 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 956...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pirate Praveen (supplier of updated ruby-enumerable-statistics 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: Sat, 18 Apr 2020 10:33:27 + Source: ruby-enumerable-statistics Architecture: source Version: 2.0.1+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Pirate Praveen Closes: 956405 Changes: ruby-enumerable-statistics (2.0.1+dfsg-3) unstable; urgency=medium . * Remove git usage in gemspec (Closes: #956405) Checksums-Sha1: b4b1f4548175dd35ca0ee23787ccba29e41cfc92 2250 ruby-enumerable-statistics_2.0.1+dfsg-3.dsc ce16ef157575542ce880004c76140fd75e8dbc69 2896 ruby-enumerable-statistics_2.0.1+dfsg-3.debian.tar.xz 464212631a45aaff1ab2ff3d554f54fa39a7a4fb 13682 ruby-enumerable-statistics_2.0.1+dfsg-3_source.buildinfo Checksums-Sha256: 0bea88c24e65407f9dbdd8b5702340e31a6dcad23cddd7a5f7fd6b46d65e93de 2250 ruby-enumerable-statistics_2.0.1+dfsg-3.dsc aa4754b127055e46884bfc58ff65eb66bcc1977ecd0ba7b8b88bc8eb02ae5145 2896 ruby-enumerable-statistics_2.0.1+dfsg-3.debian.tar.xz 70255bce74b5cf4ca695fb65914c2f2169cbdd9cd50a919738cee7a09901ca09 13682 ruby-enumerable-statistics_2.0.1+dfsg-3_source.buildinfo Files: bb5383df6738b18f5fd532179622ba3c 2250 ruby optional ruby-enumerable-statistics_2.0.1+dfsg-3.dsc d41154fe211e8a2c5b00925247c1718a 2896 ruby optional ruby-enumerable-statistics_2.0.1+dfsg-3.debian.tar.xz 4d02925de88b9309e6dc229605c1 13682 ruby optional ruby-enumerable-statistics_2.0.1+dfsg-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE0whj4mAg5UP0cZqDj1PgGTspS3UFAl6a7EYACgkQj1PgGTsp S3VpxhAAoFO4pGNhmwoQ+qDYAsgtEdlYzopEW0YP1Smf41dWh3SHvr58jlEoWFvF
Bug#958093: daq needs a source-only upload for testing migration
Source: daq Version: 2.0.6-2 Severity: serious daq needs a source-only upload for testing migration.
Bug#958091: wtdbg2: Baseline violation on amd64/i386 and FTBFS everywhere else
On Sat, Apr 18, 2020 at 02:44:54PM +0300, Adrian Bunk wrote: > Source: wtdbg2 > Version: 2.5-1 > Severity: serious > Tags: ftbfs patch > > https://buildd.debian.org/status/package.php?p=wtdbg2 > > ... > gcc: error: unrecognized command line option ‘-mpopcnt’ > gcc: error: unrecognized command line option ‘-msse4.2’ > make[1]: *** [Makefile:27: kbm2] Error 1 > > > Fix attached. Additionally the package should become Architecture: any-amd64 and the i386 package removed. It uses SSE (but not SSE4.2) unconditionally, so cannot be built on i386 without baseline violation and in any case not anywhere else. cu Adrian
Bug#956812: marked as done (snort: Missing build dependency on libssl-dev)
Your message dated Sat, 18 Apr 2020 11:49:39 + with message-id and subject line Bug#956812: fixed in snort 2.9.15.1-2 has caused the Debian Bug report #956812, regarding snort: Missing build dependency on libssl-dev 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.) -- 956812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956812 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: snort Version: 2.9.15.1-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=snort=sid ... checking for luajit... yes checking openssl/x509.h usability... no checking openssl/x509.h presence... no checking for openssl/x509.h... no ERROR! openssl/x509.h or openssl library not found. Try compiling without openAppId using '--disable-open-appid' configure: error: "Fatal!" --- End Message --- --- Begin Message --- Source: snort Source-Version: 2.9.15.1-2 Done: =?utf-8?q?Javier_Fern=C3=A1ndez-Sanguino_Pe=C3=B1a?= We believe that the bug you reported is fixed in the latest version of snort, 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 956...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Javier Fernández-Sanguino Peña (supplier of updated snort 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: Sat, 18 Apr 2020 11:56:13 +0200 Source: snort Architecture: source Version: 2.9.15.1-2 Distribution: unstable Urgency: medium Maintainer: Javier Fernández-Sanguino Peña Changed-By: Javier Fernández-Sanguino Peña Closes: 956812 Changes: snort (2.9.15.1-2) unstable; urgency=medium . * debian/control: - Add libssl-dev as Build-Dep (Closes:#956812) - Update Standards version - Fix Git-VCS url - Make snort-doc Multi-Arch: foreign * debian/patches/documentation_debian: Document the use of /etc/default/snort Checksums-Sha1: 36f4f1a20c3f32116894322dd8264a5a48161a3c 2458 snort_2.9.15.1-2.dsc 194c45bb3b9b88480a64a027741ce47e1cc02cf8 752764 snort_2.9.15.1-2.debian.tar.xz e5f66127c4db26bd21b50149a1af4208fbe84e6a 12201 snort_2.9.15.1-2_i386.buildinfo Checksums-Sha256: 3c10718f6cbb8a038f084ebf0eac55b9bb27d2feece1be8c4c85e51bb51052bd 2458 snort_2.9.15.1-2.dsc 559b0b8621d9399f63edaddf4342613aefee76f0695c0e34150006b669129a21 752764 snort_2.9.15.1-2.debian.tar.xz c910a384be622d846536c60ff3b0af2ef32a9de48ad61a3f3aa35f9212bd08da 12201 snort_2.9.15.1-2_i386.buildinfo Files: 0929b86243aa3b619aa47810a735fbaa 2458 net optional snort_2.9.15.1-2.dsc 91a2a33ee25b4006f2352f486e496f69 752764 net optional snort_2.9.15.1-2.debian.tar.xz 658dae3d6589bbcb49fbb54fb829e5be 12201 net optional snort_2.9.15.1-2_i386.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEFQ8Kq6ttIR3DT+AOix9vSKslf5gFAl6a4DEACgkQix9vSKsl f5i9exAAq9dGZJLkh5kxCVvRuO4WDIrQaCciW2a+LakBARMXHYj8KzbS3JhK0niy WzmX0S5M3tJ0MbEgYhAA4q3qQmkbpjDOg2iGdJGardBIqQJUvuKI71jlXQ1CiyS5 4hL1tKblVsnZ0XdIf5v+ALJXoOLkc9vYl2rCQ2gDLm1d8q4A3IWfvYFNt1wrmA0r 4MBlzk8fwSWjvqbM3VoMonZW3hxRUTHr+EZ+4KTDLC90m4gcLZViRlwb/BvG258L /2th7Fa/PXuikphgo31Q320nqHvUo+ZXJw4/ZIqpDzLB83PulX38eSCUiPZbviVe gQmw1DCXKXZ/RhK8aQKaMs3zXO6Qhjj2oObEiNPnO+ofyiBple+pkqrtn6xBuD+9 Ufi+xKHSI+aE++dXacb59DW1tK+y9RF00EICfQqvU4ZhQ/ubMupC8xrrbb8q+CdT Dw4prtifYe8QJMvIBndjOzohb9WVOJyTIfcDtq3g5PQ/brI06QNMQUDIfRcnxoru aJezDMwBSyU8cUTltO5RyL/NYXg5RJpPkZohjMKpuL4YRnVUNNjUNkio6wTGFwxw XmLG7scqDMkyQz3oifEBi6Dj2q2YYvNGixv99In7pfpWiRcWIL8m30f+4UzCqHoo sJOvJ/QuLzD79OcQ+0FZIifwtaZdUBK3o46V1D/nXNJakiG5yvk= =X1QP -END PGP SIGNATURE End Message ---
Bug#958091: wtdbg2: Baseline violation on amd64/i386 and FTBFS everywhere else
Source: wtdbg2
Version: 2.5-1
Severity: serious
Tags: ftbfs patch
https://buildd.debian.org/status/package.php?p=wtdbg2
...
gcc: error: unrecognized command line option ‘-mpopcnt’
gcc: error: unrecognized command line option ‘-msse4.2’
make[1]: *** [Makefile:27: kbm2] Error 1
Fix attached.
Description: Don't build with -mpopcnt -msse4.2
This is a baseline violation on amd64 and i386,
and causes FTBFS on all other release architectures.
Author: Adrian Bunk
--- wtdbg2-2.5.orig/Makefile
+++ wtdbg2-2.5/Makefile
@@ -11,9 +11,9 @@ TIMESTAMP=$(shell date)
endif
ifeq (1, ${DEBUG})
-CFLAGS+=-g3 -W -Wall -Wno-unused-but-set-variable -O0 -DDEBUG=1
-DVERSION="$(VERSION)" -DRELEASE="$(RELEASE)" -D_FILE_OFFSET_BITS=64
-D_GNU_SOURCE -mpopcnt -msse4.2
+CFLAGS+=-g3 -W -Wall -Wno-unused-but-set-variable -O0 -DDEBUG=1
-DVERSION="$(VERSION)" -DRELEASE="$(RELEASE)" -D_FILE_OFFSET_BITS=64
-D_GNU_SOURCE
else
-CFLAGS+=-g3 -W -Wall -Wno-unused-but-set-variable -O4 -DVERSION="$(VERSION)"
-DRELEASE="$(RELEASE)" -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -mpopcnt -msse4.2
+CFLAGS+=-g3 -W -Wall -Wno-unused-but-set-variable -O4 -DVERSION="$(VERSION)"
-DRELEASE="$(RELEASE)" -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE
endif
GLIBS=-lm -lrt -lpthread -lz $(LDFLAGS)
Bug#958090: diamond-aligner 0.9.31-1 fails on architectures where char is unsigned
Package: diamond-aligner Version: 0.9.31-1 Severity: serious Tags: ftbfs Control: affects -1 src:proteinortho https://ci.debian.net/data/autopkgtest/testing/arm64/p/proteinortho/4965864/log.gz https://buildd.debian.org/status/package.php?p=proteinortho=sid ... make -j4 test make[1]: Entering directory '/<>' [TEST] Clean up all test files... [TEST] 1. basic proteinortho6.pl -step=2 test. (algorithms that are not present are skipped) [TEST] Clean up all test files... [1/12] -p=blastp+ test: passed [2/12] -p=blastp+ synteny (PoFF) test: tput: No value for $TERM and no -T specified [STDERR] Error: wrong fromat... Please make sure you only provide *.blast-graph or *.proteinortho-graph files as input... Died at .//src/BUILD/Linux_aarch64/proteinortho_summary.pl line 117, <$FH> line 2. USAGE: proteinortho2html.pl ( ...) the first argument points to the proteinortho output (tsv)-file. Any further (optional) files should be fasta files, for conversion of the identifier to a proper gene name/ describtion. The HTML output is printed to stdout, use '>' to write the html output to a file. passed [3/12] -p=diamond test: Parameter-vector : (version=6.0.15,step=0,verbose=0,debug=1,exactstep3=0,synteny=0,duplication=2,cs=3,alpha=0.5,connectivity=0.1,cpus=4,evalue=1e-05,purity=1e-07,coverage=50,identity=25,blastmode=diamond,sim=0.95,report=3,keep=0,force=1,selfblast=0,twilight=0,singles=0,clean=0,blastOptions=,nograph=0,xml=0,desc=0,tmp_path=./proteinortho_cache_test_diamond/,blastversion=unknown,binpath=,makedb=diamond makedb --in,blast=,jobs_todo=10,project=test_diamond,po_path=.//src/BUILD/Linux_aarch64,run_id=,threads_per_process=1,useMcl=0,freemem=-1) [1;31m[Error][0m [1;33m diamond failed. The most likely errorsources of this are: - no space left on device error. - outdated diamond, please update diamond or consider another -p algorithm. - the databases are missing. Maybe you ran --step=1 and removed the databases afterwards? Please rerun 'proteinortho --step=1 --force /path/to/fastas' - maybe the fasta files are mixed nucleotide and aminoacid sequences or just not suited for diamond? (For example diamond only processes protein sequences) Try 'proteinortho --step=1 --check --force /path/to/fastas'. [0m (If you cannot solve this error, please send a report to incoming+paulklemm-phd-proteinortho-7278443-iss...@incoming.gitlab.com including the parameter-vector above or visit https://gitlab.com/paulklemm_PHD/proteinortho/wikis/Error%20Codes for more help. Further more all mails to lech...@staff.uni-marburg.de are welcome) Perl exited with active threads: 3 running and unjoined 0 finished and unjoined 0 running and detached Error, could not open file test_diamond.proteinortho.tsv: No such file or directory at ./src/chk_test.pl line 6. make[1]: *** [Makefile:253: test_step2] Error 2
Processed: diamond-aligner 0.9.31-1 fails on architectures where char is unsigned
Processing control commands: > affects -1 src:proteinortho Bug #958090 [diamond-aligner] diamond-aligner 0.9.31-1 fails on architectures where char is unsigned Added indication that 958090 affects src:proteinortho -- 958090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958090 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#938584: marked as done (sugar-calculate-activity: Python2 removal in sid/bullseye)
Your message dated Sat, 18 Apr 2020 11:04:50 + with message-id and subject line Bug#938584: fixed in sugar-calculate-activity 46-1 has caused the Debian Bug report #938584, regarding sugar-calculate-activity: 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.) -- 938584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938584 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:sugar-calculate-activity Version: 45-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:sugar-calculate-activity 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: sugar-calculate-activity Source-Version: 46-1 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of sugar-calculate-activity, 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 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated sugar-calculate-activity 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: Sat, 18 Apr 2020 12:45:23 +0200 Source: sugar-calculate-activity Architecture: source Version: 46-1 Distribution: unstable Urgency: medium Maintainer: Debian Sugar Team Changed-By: Jonas Smedegaard Closes: 938584 Changes: sugar-calculate-activity (46-1) unstable; urgency=medium . [ upstream ] * new release(s) . [ Jonas Smedegaard ] * use debhelper compatibility level 10 (not 9) * declare compliance with Debian Policy 4.5.0 * (build-)depend on python3 modules (not python); build-depend on dh-python; closes: bug#938584, thanks to Matthias Klose * stop rename locale ibo (no longer shipped upstream) Checksums-Sha1: 81c2de7b074f4914b400b4665da8bbadc53358d1 2118 sugar-calculate-activity_46-1.dsc ba32304ebb7e55bb4cf45c28dd05bbbc91db8e67 173042 sugar-calculate-activity_46.orig.tar.bz2
Bug#958064: marked as done (sphinxcontrib-httpdomain: Fails to register with sphinx)
Your message dated Sat, 18 Apr 2020 11:04:43 + with message-id and subject line Bug#958064: fixed in sphinxcontrib-httpdomain 1.5.0-4 has caused the Debian Bug report #958064, regarding sphinxcontrib-httpdomain: Fails to register with sphinx 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.) -- 958064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sphinxcontrib-httpdomain Version: 1.5.0-1 Severity: grave Tags: patch Justification: renders package unusable I have been unable to use this package for a few months, but could not find what I was doing wrong, and assumed that such a basic problem would be affecting other users, but there are no bugs reported. I guess this package has no users :-) Since version 1.5.0-1, the http domain is not registered with Sphinx when loading this plugin, and therefore, all :http:* directives are ignored and discarded when generating the documentation. The problem is that this version included a patch that comes from this upstream commit[1], but it is missing the fix added a couple of days after in this other commit[2]. Just adding the commit at [2] as a patch fixes the problem. I am opening now a merge request in salsa including it. [1]: https://github.com/sphinx-contrib/httpdomain/commit/50166fc7caedccf4ce1cd58a4d130a36f27eb739 [2]: https://github.com/sphinx-contrib/httpdomain/commit/8243bb6ec1ea0f3c96e0ed6177e743963fdd908b -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.5.0-1-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: unable to detect --- End Message --- --- Begin Message --- Source: sphinxcontrib-httpdomain Source-Version: 1.5.0-4 Done: Martina Ferrari We believe that the bug you reported is fixed in the latest version of sphinxcontrib-httpdomain, 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 958...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martina Ferrari (supplier of updated sphinxcontrib-httpdomain 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: Sat, 18 Apr 2020 00:06:14 + Source: sphinxcontrib-httpdomain Architecture: source Version: 1.5.0-4 Distribution: unstable Urgency: medium Maintainer: Debian OpenStack Changed-By: Martina Ferrari Closes: 958064 Changes: sphinxcontrib-httpdomain (1.5.0-4) unstable; urgency=medium . * Import commit 8243bb6ec1ea0f3c96e0ed6177e743963fdd908b from upstream. The patch added in 1.5.0-1 had rendered the package unusable. Closes: #958064. Checksums-Sha1: 57762bc034847ee2e42afe9dc1809afad1cd53a4 2206 sphinxcontrib-httpdomain_1.5.0-4.dsc eecaf4ef2317dbffe607973db7e2621f9e080d17 4164 sphinxcontrib-httpdomain_1.5.0-4.debian.tar.xz 9e59bf9572ab030e42a06b5c99d7d0db09bee6c4 6324 sphinxcontrib-httpdomain_1.5.0-4_amd64.buildinfo Checksums-Sha256: 0d94193c9893bc88d21986c86cf2472aab48d1e47f466b3c3fcd80e04cd64580 2206 sphinxcontrib-httpdomain_1.5.0-4.dsc 2a881d668ad6fd6544ef6565db2f284bb896d124ab75f287862f13981daa1f0e 4164 sphinxcontrib-httpdomain_1.5.0-4.debian.tar.xz ca130a379d508892233e280394a5cd49bda45f62e6b371f3bba05454bfd497ba 6324 sphinxcontrib-httpdomain_1.5.0-4_amd64.buildinfo Files: 09378555f9ae5879a2258ccda9be8b1d 2206 python optional sphinxcontrib-httpdomain_1.5.0-4.dsc 5ade57f1986caf3a42b32bff2fe59b01 4164 python optional sphinxcontrib-httpdomain_1.5.0-4.debian.tar.xz c3b1de7bdeb521569534eaa00ca79aba 6324 python optional sphinxcontrib-httpdomain_1.5.0-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAl6a2kQACgkQ1BatFaxr Q/5r3g/+L+oQvlQzSjNQ8wsrqnLIGgNH++Dise4X5t3kV3Hyhar0A/ouJgFdH3YQ SVJUsHvDiMlba1YrBuG2k8p8PmY7V2HJ0xfRUJNEg4epIFH3g7TKdvnq5SSymiXs yUv3YnSlKl+Vuj5F6UaGcYCZe71qLPIENb/I9/swv0Hj+AdkyI3NAHsNoBPqOZuk
Processed: Re: xkbcomp: Internal error: Could not resolve keysym XF86FullScreen
Processing control commands:
> reopen -1
Bug #953032 {Done: Timo Aaltonen } [x11-xkb-utils]
xkbcomp: Internal error: Could not resolve keysym XF86FullScreen
'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 xorgproto/2020.1-1.
--
953032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953032
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#953032: xkbcomp: Internal error: Could not resolve keysym XF86FullScreen
Control: reopen -1 Reopening, as the same error is still thrown, as can be seen [0] in the autopkgtest runs [1] of src:awesome. [0] https://ci.debian.net/data/autopkgtest/unstable/amd64/a/awesome/5031085/log.gz [1] https://ci.debian.net/packages/a/awesome/unstable/amd64/ signature.asc Description: PGP signature
Bug#958064: sphinxcontrib-httpdomain: Fails to register with sphinx
On 4/18/20 2:40 AM, Martina Ferrari wrote: > Merge request created at > > https://salsa.debian.org/openstack-team/third-party/sphinxcontrib-httpdomain/-/merge_requests/1 > > On 18/04/2020 01:29, Martina Ferrari wrote: >> Source: sphinxcontrib-httpdomain >> Version: 1.5.0-1 >> Severity: grave >> Tags: patch >> Justification: renders package unusable >> >> I have been unable to use this package for a few months, but could not find >> what I was doing wrong, and assumed that such a basic problem would be >> affecting other users, but there are no bugs reported. I guess this package >> has >> no users :-) >> >> Since version 1.5.0-1, the http domain is not registered with Sphinx when >> loading this plugin, and therefore, all :http:* directives are ignored and >> discarded when generating the documentation. >> >> The problem is that this version included a patch that comes from this >> upstream commit[1], but it is missing the fix added a couple of days after in >> this other commit[2]. >> >> Just adding the commit at [2] as a patch fixes the problem. I am opening now >> a merge >> request in salsa including it. >> >> [1]: >> https://github.com/sphinx-contrib/httpdomain/commit/50166fc7caedccf4ce1cd58a4d130a36f27eb739 >> [2]: >> https://github.com/sphinx-contrib/httpdomain/commit/8243bb6ec1ea0f3c96e0ed6177e743963fdd908b Thanks a lot for the patch, it's uploaded! Thomas
Processed: Bug#958064 marked as pending in sphinxcontrib-httpdomain
Processing control commands: > tag -1 pending Bug #958064 [src:sphinxcontrib-httpdomain] sphinxcontrib-httpdomain: Fails to register with sphinx Added tag(s) pending. -- 958064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#958064: marked as pending in sphinxcontrib-httpdomain
Control: tag -1 pending Hello, Bug #958064 in sphinxcontrib-httpdomain 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/openstack-team/third-party/sphinxcontrib-httpdomain/-/commit/e0233aea8d3ee179d904621df2857ec104e7d806 Import commit 8243bb6 from upstream. The patch added in 1.5.0-1 had rendered the package unusable. Closes: #958064. (this message was generated automatically) -- Greetings https://bugs.debian.org/958064
Bug#938588: marked as done (sugar-imageviewer-activity: Python2 removal in sid/bullseye)
Your message dated Sat, 18 Apr 2020 10:35:59 + with message-id and subject line Bug#938588: fixed in sugar-imageviewer-activity 65-1 has caused the Debian Bug report #938588, regarding sugar-imageviewer-activity: 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.) -- 938588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938588 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:sugar-imageviewer-activity Version: 64-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:sugar-imageviewer-activity 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: sugar-imageviewer-activity Source-Version: 65-1 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of sugar-imageviewer-activity, 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 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated sugar-imageviewer-activity 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: Sat, 18 Apr 2020 11:56:18 +0200 Source: sugar-imageviewer-activity Architecture: source Version: 65-1 Distribution: unstable Urgency: medium Maintainer: Debian Sugar Team Changed-By: Jonas Smedegaard Closes: 938588 Changes: sugar-imageviewer-activity (65-1) unstable; urgency=medium . [ upstream ] * new release + port to Python 3 closes: bug#938588, thanks to Matthias Klose . [ Jonas Smedegaard ] * depend on gir1.2-telepathyglib-0.12 (not python3-telepathy) * stop rename locale ibo (no longer shipped upstream) Checksums-Sha1: 020fed1b41d5ede7160fe30a1959e736ba2e5469 2180 sugar-imageviewer-activity_65-1.dsc df9219802e6c2074431b748510fa08c202231ebc 54135 sugar-imageviewer-activity_65.orig.tar.bz2 8137732cf308576f90387ac210594c80ac6311a8 5100
Bug#958085: codeblocks FTBFS on armel/armhf: multiple definition of `typeinfo name for cbKeyBinder'
Source: codeblocks Version: 20.03-2 Severity: serious Tags: ftbfs fixed-upstream patch Forwarded: https://sourceforge.net/p/codeblocks/code/12035/tree//trunk/src/plugins/contrib/keybinder/cbkeybinder.h?diff=51421f1dc431436b6eb31d56:12034 https://buildd.debian.org/status/package.php?p=codeblocks ... libtool: link: g++ -fPIC -DPIC -shared -nostdlib /usr/lib/gcc/arm-linux-gnueabihf/9/../../../arm-linux-gnueabihf/crti.o /usr/lib/gcc/arm-linux-gnueabihf/9/crtbeginS.o .libs/cbkeybinder.o .libs/cbkeyConfigPanel.o .libs/cJSON.o .libs/clKeyboardBindingConfig.o .libs/clKeyboardManager.o .libs/configurationpanel.o .libs/json_node.o .libs/keybinder.o .libs/menuutils.o -Wl,-rpath -Wl,/<>/src/sdk/.libs ../../../sdk/.libs/libcodeblocks.so -L/usr/lib/arm-linux-gnueabihf -lwx_gtk3u_aui-3.0 -lwx_gtk3u_propgrid-3.0 -lwx_gtk3u_richtext-3.0 -lwx_gtk3u_xrc-3.0 -lwx_gtk3u_html-3.0 -lwx_gtk3u_qa-3.0 -lwx_gtk3u_adv-3.0 -lwx_gtk3u_core-3.0 -lwx_baseu_xml-3.0 -lwx_baseu_net-3.0 -lwx_baseu-3.0 -lpthread -ldl -L/usr/lib/gcc/arm-linux-gnueabihf/9 -L/usr/lib/gcc/arm-linux-gnueabihf/9/../../../arm-linux-gnueabihf -L/usr/lib/gcc/arm-linux-gnueabihf/9/../../.. -L/lib/arm-linux-gnueabihf -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/arm-linux-gnueabihf/9/crtendS.o /usr/lib/gcc/arm-linux-gnueabihf/9/../../../arm-linux-gnueabihf/crtn.o -g -O2 -fstack-protector-strong -Wl,--no-undefined -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -pthread -pthread -Wl,-soname -Wl,libkeybinder.so -o .libs/libkeybinder.so /usr/bin/ld: .libs/cbkeyConfigPanel.o:(.rodata+0x14): multiple definition of `typeinfo name for cbKeyBinder'; .libs/cbkeybinder.o:(.rodata+0x0): first defined here /usr/bin/ld: .libs/cbkeyConfigPanel.o:(.data.rel.ro+0xc): multiple definition of `typeinfo for cbKeyBinder'; .libs/cbkeybinder.o:(.data.rel.ro+0x0): first defined here collect2: error: ld returned 1 exit status make[5]: *** [Makefile:579: libkeybinder.la] Error 1
Processed: pajeng FTBFS on i386: pj_validate_simu-mardi (Failed)
Processing control commands: > block 954369 by -1 Bug #954369 [src:pajeng] src:pajeng: fails to migrate to testing for too long 954369 was not blocked by any bugs. 954369 was not blocking any bugs. Added blocking bug(s) of 954369: 958084 -- 954369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954369 958084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958084 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#958084: pajeng FTBFS on i386: pj_validate_simu-mardi (Failed)
Source: pajeng
Version: 1.3.5-1
Severity: serious
Tags: ftbfs fixed-upstream
Forwarded: https://github.com/schnorr/pajeng/issues/30
Control: block 954369 by -1
https://buildd.debian.org/status/fetch.php?pkg=pajeng=i386=1.3.5-1=1579555994=0
...
12/12 Test #12: pj_validate_simu-mardi ...***Failed0.09 sec
[Tesh/INFO] change directory to /<>/obj-i686-linux-gnu
Test suite `/<>/tests/pj_validate_simu-mardi'
[/<>/tests/pj_validate_simu-mardi:3] ./pj_dump --dot
../traces/simu-mardi.trace
[/<>/tests/pj_validate_simu-mardi:34] ./pj_dump --dot -f
../traces/simu-mardi.trace
Test suite `/<>/tests/pj_validate_simu-mardi.tesh': NOK
(>/tests/pj_validate_simu-mardi.tesh:34> returned code 1)
Output of >/tests/pj_validate_simu-mardi.tesh:34> so far:
|| PajeSimulationException: Illegal, trace is not time-ordered in (Line: 7278,
Fields: '5, Contents: '11 515.00 12 8 14')
Output of >/tests/pj_validate_simu-mardi.tesh:34> mismatch:
- digraph PajeTypes {
- "0" [shape=folder, label="0 (0)"];
- "0" -> "L1";
- "L1" [shape=folder, label="L1 (1)"];
- "L1" -> "L1-LINK4-LINK4";
- "L1" -> "L1-HOST2-LINK4";
- "L1" -> "ROUTER";
- "L1" -> "LINK";
- "L1" -> "HOST";
- "L1" -> "L1-LINK4-ROUTER7";
- "L1" -> "L1-LINK4-HOST2";
- "L1-LINK4-HOST2" [shape=rarrow, label="L1-LINK4-HOST2 (10)"];
- "L1-LINK4-ROUTER7" [shape=rarrow, label="L1-LINK4-ROUTER7 (11)"];
- "HOST" [shape=folder, label="HOST (2)"];
- "HOST" -> "power";
- "HOST" -> "SERVICE";
- "HOST" -> "PM";
- "PM" [shape=rectangle, label="PM (12)"];
- "SERVICE" [shape=rectangle, label="SERVICE (18)"];
- "power" [shape=plaintext, label="power (3)"];
- "LINK" [shape=folder, label="LINK (4)"];
- "LINK" -> "latency";
- "LINK" -> "bandwidth";
- "bandwidth" [shape=plaintext, label="bandwidth (5)"];
- "latency" [shape=plaintext, label="latency (6)"];
- "ROUTER" [shape=folder, label="ROUTER (7)"];
- "L1-HOST2-LINK4" [shape=rarrow, label="L1-HOST2-LINK4 (8)"];
- "L1-LINK4-LINK4" [shape=rarrow, label="L1-LINK4-LINK4 (9)"];
- }
+ PajeSimulationException: Illegal, trace is not time-ordered in (Line: 7278,
Fields: '5, Contents: '11 515.00 12 8 14')
Test suite `/<>/tests/pj_validate_simu-mardi.tesh': NOK
(>/tests/pj_validate_simu-mardi.tesh:34> output mismatch)
92% tests passed, 1 tests failed out of 12
Total Test time (real) = 0.44 sec
The following tests FAILED:
12 - pj_validate_simu-mardi (Failed)
Errors while running CTest
make[1]: *** [Makefile:111: test] Error 8
Processed: tagging 950662
Processing commands for cont...@bugs.debian.org:
> tags 950662 - fixed-in-experimental
Bug #950662 {Done: Andreas Tille } [src:pybel] pybel FTBFS:
test failures
Removed tag(s) fixed-in-experimental.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
950662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950662
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#938594: marked as done (sugar-terminal-activity: Python2 removal in sid/bullseye)
Your message dated Sat, 18 Apr 2020 10:04:59 + with message-id and subject line Bug#938594: fixed in sugar-terminal-activity 47-1 has caused the Debian Bug report #938594, regarding sugar-terminal-activity: 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.) -- 938594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938594 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:sugar-terminal-activity Version: 45.4-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:sugar-terminal-activity 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: sugar-terminal-activity Source-Version: 47-1 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of sugar-terminal-activity, 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 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated sugar-terminal-activity 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: Sat, 18 Apr 2020 11:36:41 +0200 Source: sugar-terminal-activity Architecture: source Version: 47-1 Distribution: unstable Urgency: medium Maintainer: Debian Sugar Team Changed-By: Jonas Smedegaard Closes: 938594 Changes: sugar-terminal-activity (47-1) unstable; urgency=medium . [ upstream ] * new release(s) . [ Jonas Smedegaard ] * (build-)depend on python3 modules (not python); build-depend on dh-python; closes: bug#938594, thanks to Matthias Klose * declare compliance with Debian Policy 4.5.0 * watch: simplify regular expressions; rewrite usage comment * use debhelper compatibility level 10 (not 9) Checksums-Sha1: a489898987e5dc5f660cf3fd300eb34593efd54e 2100 sugar-terminal-activity_47-1.dsc 87a487290a7e3f137cd4a57524091ce3b5c8590c 380470 sugar-terminal-activity_47.orig.tar.gz
Bug#954812: pythonmagick: autopkgtest regression: cannot import name '_PythonMagick'
On Mon, Mar 23, 2020 at 09:43:19PM +0100, Paul Gevers wrote: > Source: pythonmagick > Version: 0.9.19-6 > X-Debbugs-CC: debian...@lists.debian.org > Severity: serious > User: debian...@lists.debian.org > Usertags: regression > > Dear maintainer(s), > > With a recent upload of pythonmagick the autopkgtest of pythonmagick > fails in testing when that autopkgtest is run with the binary packages > of pythonmagick from unstable. It passes when run with only packages > from testing. In tabular form: > >passfail > pythonmagick from testing0.9.19-6 > versioned deps [0] from testingfrom unstable > all others from testingfrom testing > > I copied some of the output at the bottom of this report. > > Currently this regression is blocking the migration to testing [1]. Can > you please investigate the situation and fix it? >... > Testing with python3.7: > + python3.7 > Traceback (most recent call last): > File "", line 1, in > File "/usr/lib/python3/dist-packages/PythonMagick/__init__.py", line > 1, in > from . import _PythonMagick > ImportError: cannot import name '_PythonMagick' from 'PythonMagick' >... This is not a regression in the package, the root cause is: https://lists.debian.org/debian-release/2020/04/msg00228.html cu Adrian
Bug#958081: nanopolish: FTBFS everywhere
Source: nanopolish Version: 0.12.1-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) nanopolish FTBFS on the buildds. See https://buildd.debian.org/status/fetch.php?pkg=nanopolish=amd64=0.12.1-1=1586252670=0 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Processed: tagging 953064
Processing commands for cont...@bugs.debian.org: > tags 953064 + ftbfs Bug #953064 [src:odin] FTBFS on i386 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 953064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#946625: scipy debci tests
No, the blacklist appears to be preventing me from launching them. On 2020-04-18 15:08, Graham Inggs wrote: Hi Drew On Sat, 18 Apr 2020 at 08:46, Drew Parsons wrote: I've uploaded scipy 1.4 to unstable. Tests run normally on my system. Could we trigger some debci tests to check if the new version has resolved the test problem? Ideally, say, 2 a day for the next 5 days to get a sample size of 10? (unless the test failure proves reproducible every time from the start) Are you able to schedule the tests yourself using Self Service? https://ci.debian.net/user Regards Graham
Bug#958040: [debian-mysql] Bug#958040: galera-3 FTBFS on armel: test failure
Forwarded: https://github.com/codership/galera/issues/572 Thanks for looking at this! I filed it upstream as well. I am happy to take MR at https://salsa.debian.org/mariadb-team/galera-3 if you have ideas on how to fix this. Note that on Debian Sid tha main focus is already on galera-4.
