Bug#948473: Users of cain please raise your voice (Was: Bug#948473: cain: should this package be removed?)
On Sun, Jan 26, 2020 at 01:17:13AM -0500, Sandro Tosi wrote: > 2 weeks passed and nobody replied; i'm gonna file for cain removal in > the morning OK. I removed it from debian-med source code in Git (as well as all mgltools-* packages which will be removed from Debian step by step currently). Kind regards Andreas. > On Thu, Jan 9, 2020 at 4:14 AM Andreas Tille wrote: > > > > Hi, > > > > when I did my first attempt to port cain I learned that it is really > > complex to do and while I gained some ideas what to try next in another > > attempt I need to fully agree with Sandro that the maintenance will be > > hard. > > > > I hereby explicitly CC Tony from BioLinux (please also spread the word > > in the BioLinux community which unfortunately is not rising their > > opinion here very frequently) and also Ivo who is listed as other > > Uploader. I think if we do not hear from either of you in the next two > > weeks I agree with Sandro and a removal seems to be the best idea. > > > > Kind regards > > > > Andreas. > > > > On Thu, Jan 09, 2020 at 12:40:14AM -0500, Sandro Tosi wrote: > > > control: retitle -1 keep cain out of testing > > > > > > On Thu, Jan 9, 2020 at 12:12 AM Andreas Tille wrote: > > > > > > > > Hi Sandro, > > > > > > > > On Wed, Jan 08, 2020 at 09:28:16PM -0500, Sandro Tosi wrote: > > > > > > > > > > * python2-only > > > > > * no upstream release since July 2012 (not even advertized on their > > > > > HP) > > > > > * low popcon (but it's also probably part of a niche package) > > > > > > > > I once gave it a try with 2to3 but failed. I intend to give > > > > it another try later. > > > > > > > > > * one of the only 2 reverse-dependency for python-scipy > > > > > > > > For the moment I think removing cain from testing and remove > > > > Python2 version of python-scipy is OK. Cain definitely should > > > > not block progress in scipy. > > > > > > i'll ask the RT to remove it from testing from the time being, this RC > > > bug will prevent it from re-entering. > > > > > > > > It is my opinion we should remove this package from Debian; if i dont > > > > > hear back > > > > > within a week with a good reason to keep this package around, i'll > > > > > file for its > > > > > removal. > > > > > > > > If you do not agree with the method above I'm fine with the > > > > removal. > > > > > > i mean, it's fine, but is it maintainable? this is a big piece of code > > > that no upstream developer has supported in 7 and a half years. you're > > > gonna end up with a gigantic 2to3 patch and then what? what if 3.8 > > > breaks it, or 3.9? or the next numpy, etc: whos gonna maintain it? > > > > > > are there any unittests to guarantee the 2to3 conversion is ok? from a > > > quick look at the package it looks like there are exactly 0 tests, not > > > comforting :( > > > https://salsa.debian.org/med-team/cain/blob/master/debian/rules#L41 > > > > > > the ultimate question is: is it worth to keep this software in debian > > > since there's nobody outside willing to commit time and effort to > > > maintain and evolve it? are you, alone, gonna do it? > > > > > > i dont think it's a sustainable approach to just 2to3 and live to see > > > another day: this py2removal is also a good opportunity to get rid of > > > old/unused/unmaintained packages; to my eyes src:cain look like one of > > > them > > > > > > cheers, > > > -- > > > Sandro "morph" Tosi > > > My website: http://sandrotosi.me/ > > > Me at Debian: http://wiki.debian.org/SandroTosi > > > Twitter: https://twitter.com/sandrotosi > > > > > > > -- > > http://fam-tille.de > > > > -- > Sandro "morph" Tosi > My website: http://sandrotosi.me/ > Me at Debian: http://wiki.debian.org/SandroTosi > Twitter: https://twitter.com/sandrotosi > > -- http://fam-tille.de
Bug#948473: Users of cain please raise your voice (Was: Bug#948473: cain: should this package be removed?)
2 weeks passed and nobody replied; i'm gonna file for cain removal in the morning On Thu, Jan 9, 2020 at 4:14 AM Andreas Tille wrote: > > Hi, > > when I did my first attempt to port cain I learned that it is really > complex to do and while I gained some ideas what to try next in another > attempt I need to fully agree with Sandro that the maintenance will be > hard. > > I hereby explicitly CC Tony from BioLinux (please also spread the word > in the BioLinux community which unfortunately is not rising their > opinion here very frequently) and also Ivo who is listed as other > Uploader. I think if we do not hear from either of you in the next two > weeks I agree with Sandro and a removal seems to be the best idea. > > Kind regards > > Andreas. > > On Thu, Jan 09, 2020 at 12:40:14AM -0500, Sandro Tosi wrote: > > control: retitle -1 keep cain out of testing > > > > On Thu, Jan 9, 2020 at 12:12 AM Andreas Tille wrote: > > > > > > Hi Sandro, > > > > > > On Wed, Jan 08, 2020 at 09:28:16PM -0500, Sandro Tosi wrote: > > > > > > > > * python2-only > > > > * no upstream release since July 2012 (not even advertized on their HP) > > > > * low popcon (but it's also probably part of a niche package) > > > > > > I once gave it a try with 2to3 but failed. I intend to give > > > it another try later. > > > > > > > * one of the only 2 reverse-dependency for python-scipy > > > > > > For the moment I think removing cain from testing and remove > > > Python2 version of python-scipy is OK. Cain definitely should > > > not block progress in scipy. > > > > i'll ask the RT to remove it from testing from the time being, this RC > > bug will prevent it from re-entering. > > > > > > It is my opinion we should remove this package from Debian; if i dont > > > > hear back > > > > within a week with a good reason to keep this package around, i'll file > > > > for its > > > > removal. > > > > > > If you do not agree with the method above I'm fine with the > > > removal. > > > > i mean, it's fine, but is it maintainable? this is a big piece of code > > that no upstream developer has supported in 7 and a half years. you're > > gonna end up with a gigantic 2to3 patch and then what? what if 3.8 > > breaks it, or 3.9? or the next numpy, etc: whos gonna maintain it? > > > > are there any unittests to guarantee the 2to3 conversion is ok? from a > > quick look at the package it looks like there are exactly 0 tests, not > > comforting :( > > https://salsa.debian.org/med-team/cain/blob/master/debian/rules#L41 > > > > the ultimate question is: is it worth to keep this software in debian > > since there's nobody outside willing to commit time and effort to > > maintain and evolve it? are you, alone, gonna do it? > > > > i dont think it's a sustainable approach to just 2to3 and live to see > > another day: this py2removal is also a good opportunity to get rid of > > old/unused/unmaintained packages; to my eyes src:cain look like one of > > them > > > > cheers, > > -- > > Sandro "morph" Tosi > > My website: http://sandrotosi.me/ > > Me at Debian: http://wiki.debian.org/SandroTosi > > Twitter: https://twitter.com/sandrotosi > > > > -- > http://fam-tille.de -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Processed: reassign 949164 to ftp.debian.org ...
Processing commands for cont...@bugs.debian.org: > reassign 949164 ftp.debian.org Bug #949164 [src:zsi] zsi: should this package be removed? Bug reassigned from package 'src:zsi' to 'ftp.debian.org'. No longer marked as found in versions zsi/2.1~a1-4. Ignoring request to alter fixed versions of bug #949164 to the same values previously set > retitle 949164 RM: zsi -- RoQA; python2-only; leaf package; last release 14 > years ago; better alternatives exist Bug #949164 [ftp.debian.org] zsi: should this package be removed? Changed Bug title to 'RM: zsi -- RoQA; python2-only; leaf package; last release 14 years ago; better alternatives exist' from 'zsi: should this package be removed?'. > thanks Stopping processing here. Please contact me if you need assistance. -- 949164: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949164 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949859: google-apputils-python: should this package be removed?
Source: google-apputils-python Severity: serious Hello, i think we should remove google-apputils-python from debian: * last upstream release in 2014 * upstream marked[1] it as "Obsolete. Please migrate to absl-py instead." * no reverse dependencies for both py2 and py3 packages * RC-buggy since a year and a half with no action on a (simple?) bug [1] https://pypi.org/project/google-apputils/ If i dont hear back within a week with a good reason to keep this package, i'll file for its removal. Regards, Sandro -- System Information: Debian Release: 10.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, 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) LSM: AppArmor: enabled
Bug#942146: koji: CVE-2019-17109
On Thu, Jan 23, 2020 at 07:46:49PM +, Holger Levsen wrote: > On Thu, Jan 23, 2020 at 08:42:03PM +0100, Moritz Muehlenhoff wrote: > > Let's remove it in the upcoming stretch/buster point releases, then? > > seems reasonable to me. Can you please file RM bugs against release.debian.org? Typically it's best if they are done by the maintainer. Cheers, Moritz
Processed: py2removal bugs severity updates - 2020-01-26 03:35:19.616115+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 > # mail threads for more details on this severity update > # not all bin pkgs are leaf for src:python-py, lower severity > severity 938054 normal Bug #938054 [src:python-py] python-py: Python2 removal in sid/bullseye Severity set to 'normal' from 'serious' > # not all bin pkgs are leaf for src:pytest, lower severity > severity 937558 normal Bug #937558 [src:pytest] pytest: Python2 removal in sid/bullseye Severity set to 'normal' from 'serious' > # not all bin pkgs are leaf for src:python-importlib-metadata, lower severity > severity 937832 normal Bug #937832 [src:python-importlib-metadata] python-importlib-metadata: Python2 removal in sid/bullseye Severity set to 'normal' from 'serious' > # not all bin pkgs are leaf for src:python-zipp, lower severity > severity 938285 normal Bug #938285 [src:python-zipp] python-zipp: Python2 removal in sid/bullseye Severity set to 'normal' from 'serious' > # not all bin pkgs are leaf for src:backports.functools-lru-cache, lower > severity > severity 936179 normal Bug #936179 [src:backports.functools-lru-cache] backports.functools-lru-cache: Python2 removal in sid/bullseye Severity set to 'normal' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 936179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936179 937558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937558 937832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937832 938054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938054 938285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938285 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949733: [Python-modules-team] Bug#949733: python-pip: 'pip install' don't work for python2 in Debian10
Hi, I had similar issues, when I didn't clean the environment, e.g. I had a .local/lib/python2.7/site-packages When I removed that folder, I was not have problems with python-pip Cheers, Arias Emmanuel @eamanu http://eamanu.com El sáb., 25 de ene. de 2020 a la(s) 20:00, Andreas Beckmann (a...@debian.org) escribió: > > Control: tag -1 = moreinfo unreproducible > > On Fri, 24 Jan 2020 10:17:34 +0100 joanluc > wrote: > > When invoking `usr/bin/pip' with any command of it, the program crashes with > > the message : > > "Traceback (most recent call last): > > File "/usr/bin/pip", line 9, in > > from pip._internal import main > > ImportError: No module named _internal" > > Hi, > > I cannot reproduce this. The pip._internal module should be located at > /usr/lib/python2.7/dist-packages/pip/_internal/* > Are there any local environment variables on your system that alter the > python search path? > Are you using the system python command or do you have a "special" > python installation? > Is anything corrupted? (e.g. check with debsums) > > > Andreas > > ___ > 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#949029: Processed: reassign 949029 to python3.8
On 1/26/20 12:57 AM, Debian Bug Tracking System wrote: > Processing commands for cont...@bugs.debian.org: > >> reassign 949029 python3.8 > Bug #949029 [src:python-bleach] python-bleach is failing the autopkg tests > with Python 3.8 > Bug reassigned from package 'src:python-bleach' to 'python3.8'. > No longer marked as found in versions python-bleach/3.1.0-2. > Ignoring request to alter fixed versions of bug #949029 to the same values > previously set >> affects 949029 python-bleach > Bug #949029 [python3.8] python-bleach is failing the autopkg tests with > Python 3.8 > Added indication that 949029 affects python-bleach >> thanks > Stopping processing here. > > Please contact me if you need assistance. reverting that change only makes sense when it's reverted upstream, which didn't yet happen. Matthias
Bug#949780: maptool: Maptool segfaults
Hi, Taking the england-latest.osm.pbf from https://download.geofabrik.de/europe/great-britain.html it does fail with 0.5.4 after several minutes of processing with (not a segfault per say but still failing): PROGRESS9: Processed 47104 nodes (8208 out) 0 ways 62282 relations 0 tiles 7:17 181 MB PROGRESS9: Processed 47104 nodes (8208 out) 0 ways 62282 relations 0 tiles 7:47 181 MB PROGRESS9: Processed 47104 nodes (8208 out) 0 ways 62282 relations 0 tiles 8:17 181 MB worker 3 exit PROGRESS9: Processed 47104 nodes (8208 out) 0 ways 62282 relations 0 tiles 8:18 181 MB PROGRESS9: Processed 47104 nodes (8208 out) 0 ways 0 relations 0 tiles 8:18 181 MB process_multipolygons:process (thread 0) process_multipolygons:finish (thread 0) maptool: /build/navit-vwCTlu/navit-0.5.4+dfsg.1/navit/maptool/itembin.c:93: item_bin_copy_attr: Assertion `attr == attr_osm_wayid' failed. You mention in the bug there that you were able to run your pbf by compiling maptool from the git repo. What compilation flags did you use? Thanks for your help, Joseph
Bug#949780: maptool: Maptool segfaults
Hi, On Fri, Jan 24, 2020 at 2:00 PM ael wrote: > Package: maptool > Version: 0.5.3+dfsg.1-2+b1 Please try with the 0.5.4 version currently in unstable as here have been a lot of changes to maptool since 0.5.3. > This was encountered while looking at the issues with navit on wince: > see https://github.com/navit-gps/navit/issues/953#issuecomment-578313710 Are you using the debian binaries on wince? > Search down that page to see the problem with the Debian testing > maptool: > > maptool --protobuf -i > /ssdback1/ael/mapping/mkgmap/great-britain-latest.osm.pbf test.bin > > but that SEGFAULTED almost immediately after writing some empty *.tmp Could you provide the link to the .pbf or the proto and the way you build it so we can reproduce it please? It's hard to debug without more information. > I see that there is a new version in unstable but I have not tried that > version as yet. Please try with the new version. There's been a lot of changes in maptool between 0.5.3 and 0.5.4. Thanks Joseph
Bug#942858: marked as done (Doesn't support Python 3.8: SystemError: bad call flags)
Your message dated Sun, 26 Jan 2020 01:36:48 + with message-id and subject line Bug#945894: Removed package(s) from unstable has caused the Debian Bug report #942858, regarding Doesn't support Python 3.8: SystemError: bad call flags 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.) -- 942858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942858 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-leveldb Version: 0~svn68-3+b3 Severity: important User: debian-pyt...@lists.debian.org Usertags: python3.8 Importing leveldb in Python 3.8 will fail: Traceback (most recent call last): File "test/test.py", line 11, in setUp import leveldb as _leveldb SystemError: bad call flags This doesn't break the package build but should break autopkgtests. As the upstream looks dead (last release 2016), there is a patch in Fedora which I didn't test: https://src.fedoraproject.org/rpms/python- leveldb/c/57adbb30b4d4c1ee58976eaa8ca5b3cea9c516ab?branch=master -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.0-trunk-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-leveldb depends on: ii libc6 2.29-2 ii libgcc1 1:9.2.1-9 pn libleveldb1d ii libsnappy1v5 1.1.7-1+b1 ii libstdc++69.2.1-9 ii python3 3.7.5-1 python3-leveldb recommends no packages. python3-leveldb suggests no packages. --- End Message --- --- Begin Message --- Version: 0~svn68-3+rm Dear submitter, as the package python-leveldb 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/945894 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#937884: marked as done (python-leveldb: Python2 removal in sid/bullseye)
Your message dated Sun, 26 Jan 2020 01:36:48 + with message-id and subject line Bug#945894: Removed package(s) from unstable has caused the Debian Bug report #937884, regarding python-leveldb: 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.) -- 937884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937884 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-leveldb Version: 0~svn68-3 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-leveldb 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~svn68-3+rm Dear submitter, as the package python-leveldb 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/945894 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#880271: marked as done (tendermint: FTBFS: Test failures)
Your message dated Sun, 26 Jan 2020 01:24:48 + with message-id and subject line Bug#946912: Removed package(s) from unstable has caused the Debian Bug report #880271, regarding tendermint: FTBFS: Test failures 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.) -- 880271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880271 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tendermint Version: 0.8.0+git20170113.0.764091d-2 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20171030 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > --- PASS: Test2_3Majority (0.00s) > === RUN Test2_3MajorityRedux > --- PASS: Test2_3MajorityRedux (0.05s) > === RUN TestBadVotes > --- PASS: TestBadVotes (0.02s) > === RUN TestConflicts > --- PASS: TestConflicts (0.00s) > === RUN TestMakeCommit > --- PASS: TestMakeCommit (0.00s) > === RUN TestVoteSignable > --- PASS: TestVoteSignable (0.00s) > PASS > okgithub.com/tendermint/tendermint/types 0.745s > ? github.com/tendermint/tendermint/version[no test files] > dh_auto_test: cd obj-x86_64-linux-gnu && go test -v -p 1 > github.com/tendermint/tendermint/benchmarks > github.com/tendermint/tendermint/benchmarks/proto > github.com/tendermint/tendermint/benchmarks/simu > github.com/tendermint/tendermint/blockchain > github.com/tendermint/tendermint/cmd/tendermint > github.com/tendermint/tendermint/config/tendermint > github.com/tendermint/tendermint/config/tendermint_test > github.com/tendermint/tendermint/consensus > github.com/tendermint/tendermint/fail-test > github.com/tendermint/tendermint/mempool > github.com/tendermint/tendermint/node github.com/tendermint/tendermint/proxy > github.com/tendermint/tendermint/rpc/core > github.com/tendermint/tendermint/rpc/core/types > github.com/tendermint/tendermint/rpc/grpc > github.com/tendermint/tendermint/rpc/test > github.com/tendermint/tendermint/state > github.com/tendermint/tendermint/test/app > github.com/tendermint/tendermint/types > github.com/tendermint/tendermint/version returned exit code 1 > debian/rules:9: recipe for target 'override_dh_auto_test' failed The full build log is available from: http://aws-logs.debian.net/2017/10/30/tendermint_0.8.0+git20170113.0.764091d-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Version: 0.8.0+git20170113.0.764091d-2+rm Dear submitter, as the package tendermint 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/946912 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#896175: marked as done (ruby-notifier: FTBFS and Debci failure with ruby-did-you-mean 1.2.1-1)
Your message dated Sun, 26 Jan 2020 01:25:44 + with message-id and subject line Bug#949392: Removed package(s) from unstable has caused the Debian Bug report #896175, regarding ruby-notifier: FTBFS and Debci failure with ruby-did-you-mean 1.2.1-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 896175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896175 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-notifier Version: 0.5.1-2 Severity: serious Tags: buster sid https://ci.debian.net/packages/r/ruby-notifier/unstable/amd64/ https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-notifier.html ... ┌──┐ │ Run tests for ruby2.5 from debian/ruby-tests.rake│ └──┘ RUBYLIB=/build/1st/ruby-notifier-0.5.1/debian/ruby-notifier/usr/lib/ruby/vendor_ruby:. GEM_PATH=debian/ruby-notifier/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all ruby2.5 -S rake -f debian/ruby-tests.rake /usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*_spec.rb .F Failures: 1) Notifier returns first available notifier Failure/Error: expect(Notifier.notifier).to eql(Notifier::Snarl) expected: Notifier::Snarl got: Notifier::Knotify (compared using eql?) Diff: @@ -1,2 +1,2 @@ -Notifier::Snarl +Notifier::Knotify # ./spec/notifier_spec.rb:20:in `block (2 levels) in ' Finished in 0.09405 seconds (files took 0.33104 seconds to load) 10 examples, 1 failure Failed examples: rspec ./spec/notifier_spec.rb:16 # Notifier returns first available notifier /usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*_spec.rb failed ERROR: Test "ruby2.5" failed. Exiting. dh_auto_install: dh_ruby --install /build/1st/ruby-notifier-0.5.1/debian/ruby-notifier returned exit code 1 make: *** [debian/rules:15: binary] Error 1 --- End Message --- --- Begin Message --- Version: 0.5.1-2+rm Dear submitter, as the package ruby-notifier 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/949392 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: retitle 949029 to Breaking change intorduced in python3.8 3.8.1 breaks python-bleach
Processing commands for cont...@bugs.debian.org: > retitle 949029 Breaking change intorduced in python3.8 3.8.1 breaks > python-bleach Bug #949029 [python3.8] python-bleach is failing the autopkg tests with Python 3.8 Changed Bug title to 'Breaking change intorduced in python3.8 3.8.1 breaks python-bleach' from 'python-bleach is failing the autopkg tests with Python 3.8'. > thanks Stopping processing here. Please contact me if you need assistance. -- 949029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949029 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 937437, reassign 946728 to src:hugo, fixed 946728 in 0.59.1-1.1, found 949832 in 1.1.0-2.1 ...
Processing commands for cont...@bugs.debian.org:
> tags 937437 + experimental
Bug #937437 [src:pyfeed] pyfeed: Python2 removal in sid/bullseye
Added tag(s) experimental.
> reassign 946728 src:hugo 0.58.3-1
Bug #946728 {Done: Adrian Bunk }
[src:golang-github-kyokomi-emoji, src:hugo] golang-github-kyokomi-emoji breaks
hugo autopkgtest: got "I ❤ Hugo" expected "I ❤️ Hugo"
Bug reassigned from package 'src:golang-github-kyokomi-emoji, src:hugo' to
'src:hugo'.
No longer marked as found in versions hugo/0.58.3-1 and
golang-github-kyokomi-emoji/2.1.0-1.
No longer marked as fixed in versions hugo/0.59.1-1.1.
Bug #946728 {Done: Adrian Bunk } [src:hugo]
golang-github-kyokomi-emoji breaks hugo autopkgtest: got "I ❤ Hugo" expected "I
❤️ Hugo"
Marked as found in versions hugo/0.58.3-1.
> fixed 946728 0.59.1-1.1
Bug #946728 {Done: Adrian Bunk } [src:hugo]
golang-github-kyokomi-emoji breaks hugo autopkgtest: got "I ❤ Hugo" expected "I
❤️ Hugo"
Marked as fixed in versions hugo/0.59.1-1.1.
> found 949832 1.1.0-2.1
Bug #949832 [src:python-publicsuffix] src:python-publicsuffix: Should not be
released with Bullseye
Marked as found in versions python-publicsuffix/1.1.0-2.1.
> found 949824 3.4.1-2
Bug #949824 [src:schleuder] schleuder: tests fail with ruby-sqlite 1.4.2-1
Marked as found in versions schleuder/3.4.1-2.
> fixed 949736 2:2.1.3+ds1-1
Bug #949736 [enigmail] enigmail: uninstallable in stretch (since thunderbird
was upgraded to version 68 due to security upgrade)
Marked as fixed in versions enigmail/2:2.1.3+ds1-1.
> fixed 949736 2:2.1.3+ds1-4~deb10u2
Bug #949736 [enigmail] enigmail: uninstallable in stretch (since thunderbird
was upgraded to version 68 due to security upgrade)
Marked as fixed in versions enigmail/2:2.1.3+ds1-4~deb10u2.
> tags 949242 + sid bullseye
Bug #949242 {Done: gregor herrmann } [src:libsoap-wsdl-perl]
FTBFS: test failures with libtimedate-perl 2.3100-1
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
937437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937437
946728: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946728
949242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949242
949736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949736
949824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949824
949832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949832
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#949029: python-bleach is failing the autopkg tests with Python 3.8
This is due to a breaking change that was inappropriately included in python3.8 3.8.1. See: https://bugs.python.org/issue27657 https://github.com/mozilla/bleach/issues/503 Rather than "Fixed" in python-bleach, the breaking change in python3.8 should be reverted. Python3 can break python-bleach for real in 3.9. Scott K signature.asc Description: This is a digitally signed message part.
Processed: reassign 949029 to python3.8
Processing commands for cont...@bugs.debian.org: > reassign 949029 python3.8 Bug #949029 [src:python-bleach] python-bleach is failing the autopkg tests with Python 3.8 Bug reassigned from package 'src:python-bleach' to 'python3.8'. No longer marked as found in versions python-bleach/3.1.0-2. Ignoring request to alter fixed versions of bug #949029 to the same values previously set > affects 949029 python-bleach Bug #949029 [python3.8] python-bleach is failing the autopkg tests with Python 3.8 Added indication that 949029 affects python-bleach > thanks Stopping processing here. Please contact me if you need assistance. -- 949029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949029 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#944455: pgcli: missing dependency on python3-pkg-resources
Followup-For: Bug #944455 Hi, please fix this in buster, too. Andreas
Bug#949733: python-pip: 'pip install' don't work for python2 in Debian10
Control: tag -1 = moreinfo unreproducible On Fri, 24 Jan 2020 10:17:34 +0100 joanluc wrote: > When invoking `usr/bin/pip' with any command of it, the program crashes with > the message : > "Traceback (most recent call last): > File "/usr/bin/pip", line 9, in > from pip._internal import main > ImportError: No module named _internal" Hi, I cannot reproduce this. The pip._internal module should be located at /usr/lib/python2.7/dist-packages/pip/_internal/* Are there any local environment variables on your system that alter the python search path? Are you using the system python command or do you have a "special" python installation? Is anything corrupted? (e.g. check with debsums) Andreas
Processed: Re: python-pip: 'pip install' don't work for python2 in Debian10
Processing control commands: > tag -1 = moreinfo unreproducible Bug #949733 [python-pip] python-pip: 'pip install' don't work for python2 in Debian10 Added tag(s) moreinfo and unreproducible; removed tag(s) a11y. -- 949733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949733 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949850: libipmctl4: broken conffile migration, making logrotate inoperative
Package: libipmctl4 Version: 02.00.00.3673+ds-2 Severity: serious The conffile migration is broken, resulting in: /etc/cron.daily/logrotate: error: ipmctl.conf:1 duplicate log entry for /var/log/ipmctl/*log error: found error in file ipmctl.conf, skipping run-parts: /etc/cron.daily/logrotate exited with return code 1 libipmctl3 had /etc/logrotate.d/ipmctl.conf libipmctl4 has /etc/logrotate.d/ipmctl and migration doesn't work, resulting in a stray copy of the owner. The conffile must go, no matter if it has been modified or not. The package had never been a part of a Debian stable release yet, but it's been released with Ubuntu Eoan, thus papering over the problem won't work. Setting severity to RC to block testing migration. Meow! -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable'), (150, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.13-00051-g5426abd18b11 (SMP w/6 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/dash Init: sysvinit (via /sbin/init) Versions of packages libipmctl4 depends on: ii libc6 2.29-9 ii libndctl6 67-1 libipmctl4 recommends no packages. libipmctl4 suggests no packages. -- no debconf information
Processed: Raising severity of transition blocking bug
Processing commands for cont...@bugs.debian.org: > severity 948774 serious Bug #948774 [src:xdrawchem] xdrawchem: build with Open Babel 3 Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 948774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948774 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949700: marked as done (mc: extfs for .deb regression against 3:4.8.23-1 (makes it mostly unusable))
Your message dated Sat, 25 Jan 2020 21:51:41 + with message-id and subject line Bug#949700: fixed in mc 3:4.8.24-2 has caused the Debian Bug report #949700, regarding mc: extfs for .deb regression against 3:4.8.23-1 (makes it mostly unusable) 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.) -- 949700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949700 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mc Version: 3:4.8.24-1 Severity: normal $ apt-get download mc $ mc Then navigate to mc_3%3a4.8.24-1_amd64.deb and press Enter, go to CONTENTS/ and press Enter again. It’s empty. Downgrading mc and mc-data to 3:4.8.23-1 makes it work again, so it’s a regression. -- System Information: Debian Release: bullseye/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) Versions of packages mc depends on: ii libc6 2.29-9 ii libext2fs21.45.5-2 ii libglib2.0-0 2.62.4-1+b1 ii libgpm2 1.20.7-5+b1 ii libslang2 2.3.2-4 ii libssh2-1 1.8.0-2.1 ii mc-data 3:4.8.24-1 Versions of packages mc recommends: ii mime-support 3.64 ii perl 5.30.0-9 ii unzip 6.0-25 Versions of packages mc suggests: pn arj ii bzip21.0.8-2 pn dbview pn djvulibre-bin pn epub-utils ii file 1:5.38-4 ii genisoimage 9:1.1.11-3.1 ii gv [pdf-viewer] 1:3.7.4-2+b1 ii imagemagick 8:6.9.10.23+dfsg-2.1+b2 ii imagemagick-6.q16 [imagemagick] 8:6.9.10.23+dfsg-2.1+b2 pn libaspell-dev ii lynx 2.9.0dev.4-1 ii mupdf [pdf-viewer] 1.15.0+ds1-1+b1 pn odt2txt ii okular [pdf-viewer] 4:17.12.2-2.2+b2 ii poppler-utils0.71.0-6 ii python 2.7.17-2 pn python-boto pn python-tz ii texlive-binaries 2019.20190605.51237-3 ii w3m 0.5.3-37+b1 ii zip 3.0-11+b1 -- no debconf information --- End Message --- --- Begin Message --- Source: mc Source-Version: 3:4.8.24-2 We believe that the bug you reported is fixed in the latest version of mc, 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 949...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Smirnov (supplier of updated mc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 26 Jan 2020 08:23:52 +1100 Source: mc Architecture: source Version: 3:4.8.24-2 Distribution: unstable Urgency: medium Maintainer: Dmitry Smirnov Changed-By: Dmitry Smirnov Closes: 949700 Changes: mc (3:4.8.24-2) unstable; urgency=medium . * New upstream patch to fix browsing of .DEB packages (Closes: #949700). Checksums-Sha1: 267c906eaac77f5f7bfeec4fde1743e6bb9a09a2 2103 mc_4.8.24-2.dsc 33aae89a215f6f7442f311a01bfca2509d2a7b34 48024 mc_4.8.24-2.debian.tar.xz 1cf147e3ba82a6ccb2c2b85947df7d23b66dc89d 9057 mc_4.8.24-2_amd64.buildinfo Checksums-Sha256: 803f06673a920af51e4d5e8e85c13ee534011ff849f190ffe98cc1c02fbf1fc1 2103 mc_4.8.24-2.dsc d4a8b597d9213caa480dd10909bde8d455d89dbc72cb2f033d8affa52394f965 48024 mc_4.8.24-2.debian.tar.xz 9c6eb5c230662a8e2ca39b1c6c2c8214df039ff86c793ba28e41ff46df39d491 9057 mc_4.8.24-2_amd64.buildinfo Files: 69913652d4a4a0ca2a8fad0444a2b471 2103 utils optional mc_4.8.24-2.dsc ab35523f3cabc9bb9547b47cc078a74a 48024 utils optional mc_4.8.24-2.debian.tar.xz 8f83e86d997a3f74d1a1a6c01d7f36c0 9057 utils optional mc_4.8.24-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEULx8+TnSDCcqawZWUra72VOWjRsFAl4ss84ACgkQUra72VOW
Processed: found 926670 in 2.7.0+ds1-1
Processing commands for cont...@bugs.debian.org:
> found 926670 2.7.0+ds1-1
Bug #926670 {Done: Gordon Ball } [src:node-xterm]
CVE-2019-0542
Marked as found in versions node-xterm/2.7.0+ds1-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
926670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926670
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: getlive: diff for NMU version 2.4+cvs20120801-1.1
Processing control commands: > tags 932532 + patch Bug #932532 [src:getlive] getlive: Uses manual dh sequence operations that are going to be removed Added tag(s) patch. > tags 932532 + pending Bug #932532 [src:getlive] getlive: Uses manual dh sequence operations that are going to be removed Added tag(s) pending. -- 932532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932532 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#932532: getlive: diff for NMU version 2.4+cvs20120801-1.1
Control: tags 932532 + patch Control: tags 932532 + pending Dear maintainer, I've prepared an NMU for getlive (versioned as 2.4+cvs20120801-1.1) and uploaded it to DELAYED/7. Please feel free to tell me if I should delay it longer. Regards. diff -u getlive-2.4+cvs20120801/debian/rules getlive- 2.4+cvs20120801/debian/rules --- getlive-2.4+cvs20120801/debian/rules +++ getlive-2.4+cvs20120801/debian/rules @@ -5,4 +5,3 @@ -binary: build - dh binary --until dh_install +override_dh_install: install -D GetLive.pl debian/getlive/usr/bin/getlive - dh binary + dh_install diff -u getlive-2.4+cvs20120801/debian/compat getlive- 2.4+cvs20120801/debian/compat --- getlive-2.4+cvs20120801/debian/compat +++ getlive-2.4+cvs20120801/debian/compat @@ -1 +1 @@ -7 +9 diff -u getlive-2.4+cvs20120801/debian/control getlive- 2.4+cvs20120801/debian/control --- getlive-2.4+cvs20120801/debian/control +++ getlive-2.4+cvs20120801/debian/control @@ -2,7 +2,7 @@ Section: mail Priority: optional Maintainer: Martín Ferrari -Build-Depends: debhelper (>= 7) +Build-Depends: debhelper (>= 9) Standards-Version: 3.9.3 Homepage: http://getlive.sourceforge.net/ Vcs-Browser: http://canterville.mine.nu/wsvn/debian/trunk/getlive/ diff -u getlive-2.4+cvs20120801/debian/changelog getlive- 2.4+cvs20120801/debian/changelog --- getlive-2.4+cvs20120801/debian/changelog +++ getlive-2.4+cvs20120801/debian/changelog @@ -1,3 +1,13 @@ +getlive (2.4+cvs20120801-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * debian/control: bump debhelper compat to v9 for proper +dh_install support. + * debian/rules: Use override_dh_install instead of manual dh +sequence operation. (Closes: #932532) + + -- Boyuan Yang Sat, 25 Jan 2020 16:22:25 -0500 + getlive (2.4+cvs20120801-1) unstable; urgency=high * New upstream release (from CVS tree). Closes: 677005, 681511. signature.asc Description: This is a digitally signed message part
Bug#926670: marked as done (CVE-2019-0542)
Your message dated Sat, 25 Jan 2020 21:18:18 + with message-id and subject line Bug#926670: fixed in node-xterm 3.8.1-1 has caused the Debian Bug report #926670, regarding CVE-2019-0542 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.) -- 926670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926670 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-xterm Severity: grave Tags: security Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0542 Cheers, Moritz --- End Message --- --- Begin Message --- Source: node-xterm Source-Version: 3.8.1-1 We believe that the bug you reported is fixed in the latest version of node-xterm, 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 926...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gordon Ball (supplier of updated node-xterm 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, 25 Jan 2020 19:35:53 + Source: node-xterm Architecture: source Version: 3.8.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Gordon Ball Closes: 888935 909424 919077 926670 Changes: node-xterm (3.8.1-1) unstable; urgency=medium . [ Ghislain Antony Vaillant ] * Change package section to javascript * Add recommended get-orig-source target . [ Pirate Praveen ] * New upstream version 3.7.0 (Closes: #909424) * Use salsa.debian.org in Vcs-* fields * Bump debhelper compatibility level to 11 * Bump Standards-Version to 4.2.1 (no changes needed) . [ Gordon Ball ] * Convert to pkg-js-tools * Fix FTBFS bugs (Closes: #888935, #919077) * Move node-xterm to /usr/share/nodejs (from /usr/lib/nodejs) * Standards-Version 4.5.0 * Debhelper compat level 12 (and drop debian/compat) * Patch several obsolete type names caught by newer node-typescript * New upstream version 3.8.1 (the earliest version containing a fix for CVE-2019-0542, closes: #926670) * Update URLs to github.com/xtermjs/xterm.js * Drop Files-Excluded and repacking config, as the relevant files no longer exist in the tarball * Drop d/copyright stanza for src/xterm.js which no longer exists * Set Rules-Requires-Root: no Checksums-Sha1: d35b358444c46c3c9f086ae9806ef43ae9a1cd33 2163 node-xterm_3.8.1-1.dsc 777a49e64267990b22d9abe1027a3d6f01143425 287514 node-xterm_3.8.1.orig.tar.gz eedea5b609583ac7bdc6176686149c580a42e13e 4596 node-xterm_3.8.1-1.debian.tar.xz aae19a72a484a3971a321cf041444b65fff84335 10860 node-xterm_3.8.1-1_amd64.buildinfo Checksums-Sha256: 0c49f783a9b2c8cb5b056d26a184ead496134e4f32641a78db42c35173a3e7a7 2163 node-xterm_3.8.1-1.dsc 81ffa6c425126878c32dc9bcdc5dd7a5a5bc862e2ef063fc9bcbe03cf2fee31d 287514 node-xterm_3.8.1.orig.tar.gz 54d647c0e72a5a5c19a2d9ff036014d40c7e13b6e55a68e2a85b28a62c5af20b 4596 node-xterm_3.8.1-1.debian.tar.xz 6f843325df8aac09f49d8ed191ad029560b6d642676269d7ecd5649447baee66 10860 node-xterm_3.8.1-1_amd64.buildinfo Files: e2af43800a39a58e8b894891ceb2934f 2163 javascript optional node-xterm_3.8.1-1.dsc 1b561d784cc784db39cb175346210f3e 287514 javascript optional node-xterm_3.8.1.orig.tar.gz 7bb8428adbba5ff63d31f40e3bd4c368 4596 javascript optional node-xterm_3.8.1-1.debian.tar.xz 0992fd868d884defb67d800c4efd30d6 10860 javascript optional node-xterm_3.8.1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE6PwpXIa418BJ+Xuno12v+60p6N4FAl4snXkACgkQo12v+60p 6N5UDhAAlBmVxi4ftOa6NeZS140KKUMtGSVPxqGhBc1JU7csPQIia1raTfKbmNoC 6aaYCW0UhtmEwVtK2mrSS2wUrKIEuwsV0VYFLSax0ed5nOGz7BqRSIq1WGbBZnMt q9FdCeE8BnITBWGBkjl7Oa0ZTD6IiKa471hd/Q4b+iWndK3xxvxiqmXy21d0ptJy aiz8i7bo8/UMJQHnvzb8lZBo64a4YEVhOpjYjr5wtJWN0CljAVsYqVe0vu0V29zQ on8M7GyAlnNiJOudP9dRI1FOhqhYns2mRTb3IdBlTaWML85qy5eLRkb7ngy0+Dc5 o+Znywahmsc9/JhT0JsLKl4fNTxpQ8WQWtKY57KpcfA9f7htxHJbwV9Vx9nakHZt 4gOuJZjjK77dZ+fAu/QL2wu0f3ciQ6oNQO/QbJxFs0RNW8fTgkRmKBPm9DjJTOKo X686N1M5/lZZ8Ahmh80UUr4UY3ClqKubGwah5ZjTuUKdnY8RB5L5mL/CatFpU+y1 RDL4Qf5K17HrUjGVqkZXFV0Smk22FcgYCg2PayXUo3K6KoB7L/i2yV23YzTYYTTh tyvjEI7q6fMj2jxIv62qvYFdZvEKLH/fWRhjjLiV/YropJlsQsugwv4K3MFVhOvt
Bug#919077: marked as done (node-xterm FTBFS)
Your message dated Sat, 25 Jan 2020 21:18:17 + with message-id and subject line Bug#888935: fixed in node-xterm 3.8.1-1 has caused the Debian Bug report #888935, regarding node-xterm FTBFS 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.) -- 888935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-xterm Version: 2.7.0+ds1-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-xterm.html ... debian/rules override_dh_auto_build make[1]: Entering directory '/build/1st/node-xterm-2.7.0+ds1' tsc --project . src/Linkifier.ts(82,5): error TS2322: Type 'Timer' is not assignable to type 'number'. src/utils/Mouse.ts(30,80): error TS2339: Property 'parentElement' does not exist on type 'never'. make[1]: *** [debian/rules:19: override_dh_auto_build] Error 2 --- End Message --- --- Begin Message --- Source: node-xterm Source-Version: 3.8.1-1 We believe that the bug you reported is fixed in the latest version of node-xterm, 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 888...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gordon Ball (supplier of updated node-xterm 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, 25 Jan 2020 19:35:53 + Source: node-xterm Architecture: source Version: 3.8.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Gordon Ball Closes: 888935 909424 919077 926670 Changes: node-xterm (3.8.1-1) unstable; urgency=medium . [ Ghislain Antony Vaillant ] * Change package section to javascript * Add recommended get-orig-source target . [ Pirate Praveen ] * New upstream version 3.7.0 (Closes: #909424) * Use salsa.debian.org in Vcs-* fields * Bump debhelper compatibility level to 11 * Bump Standards-Version to 4.2.1 (no changes needed) . [ Gordon Ball ] * Convert to pkg-js-tools * Fix FTBFS bugs (Closes: #888935, #919077) * Move node-xterm to /usr/share/nodejs (from /usr/lib/nodejs) * Standards-Version 4.5.0 * Debhelper compat level 12 (and drop debian/compat) * Patch several obsolete type names caught by newer node-typescript * New upstream version 3.8.1 (the earliest version containing a fix for CVE-2019-0542, closes: #926670) * Update URLs to github.com/xtermjs/xterm.js * Drop Files-Excluded and repacking config, as the relevant files no longer exist in the tarball * Drop d/copyright stanza for src/xterm.js which no longer exists * Set Rules-Requires-Root: no Checksums-Sha1: d35b358444c46c3c9f086ae9806ef43ae9a1cd33 2163 node-xterm_3.8.1-1.dsc 777a49e64267990b22d9abe1027a3d6f01143425 287514 node-xterm_3.8.1.orig.tar.gz eedea5b609583ac7bdc6176686149c580a42e13e 4596 node-xterm_3.8.1-1.debian.tar.xz aae19a72a484a3971a321cf041444b65fff84335 10860 node-xterm_3.8.1-1_amd64.buildinfo Checksums-Sha256: 0c49f783a9b2c8cb5b056d26a184ead496134e4f32641a78db42c35173a3e7a7 2163 node-xterm_3.8.1-1.dsc 81ffa6c425126878c32dc9bcdc5dd7a5a5bc862e2ef063fc9bcbe03cf2fee31d 287514 node-xterm_3.8.1.orig.tar.gz 54d647c0e72a5a5c19a2d9ff036014d40c7e13b6e55a68e2a85b28a62c5af20b 4596 node-xterm_3.8.1-1.debian.tar.xz 6f843325df8aac09f49d8ed191ad029560b6d642676269d7ecd5649447baee66 10860 node-xterm_3.8.1-1_amd64.buildinfo Files: e2af43800a39a58e8b894891ceb2934f 2163 javascript optional node-xterm_3.8.1-1.dsc 1b561d784cc784db39cb175346210f3e 287514 javascript optional node-xterm_3.8.1.orig.tar.gz 7bb8428adbba5ff63d31f40e3bd4c368 4596 javascript optional node-xterm_3.8.1-1.debian.tar.xz 0992fd868d884defb67d800c4efd30d6 10860 javascript optional node-xterm_3.8.1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE6PwpXIa418BJ+Xuno12v+60p6N4FAl4snXkACgkQo12v+60p 6N5UDhAAlBmVxi4ftOa6NeZS140KKUMtGSVPxqGhBc1JU7csPQIia1raTfKbmNoC 6aaYCW0UhtmEwVtK2mrSS2wUrKIEuwsV0VYFLSax0ed5nOGz7BqRSIq1WGbBZnMt q9FdCeE8BnITBWGBkjl7Oa0ZTD6IiKa471hd/Q4b+iWndK3xxvxiqmXy21d0ptJy aiz8i7bo8/UMJQHnvzb8lZBo64a4YEVhOpjYjr5wtJWN0CljAVsYqVe0vu0V29zQ
Bug#919077: marked as done (node-xterm FTBFS)
Your message dated Sat, 25 Jan 2020 21:18:18 + with message-id and subject line Bug#919077: fixed in node-xterm 3.8.1-1 has caused the Debian Bug report #919077, regarding node-xterm FTBFS 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.) -- 919077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919077 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-xterm Version: 2.7.0+ds1-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-xterm.html ... debian/rules override_dh_auto_build make[1]: Entering directory '/build/1st/node-xterm-2.7.0+ds1' tsc --project . src/Linkifier.ts(82,5): error TS2322: Type 'Timer' is not assignable to type 'number'. src/utils/Mouse.ts(30,80): error TS2339: Property 'parentElement' does not exist on type 'never'. make[1]: *** [debian/rules:19: override_dh_auto_build] Error 2 --- End Message --- --- Begin Message --- Source: node-xterm Source-Version: 3.8.1-1 We believe that the bug you reported is fixed in the latest version of node-xterm, 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 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gordon Ball (supplier of updated node-xterm 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, 25 Jan 2020 19:35:53 + Source: node-xterm Architecture: source Version: 3.8.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Gordon Ball Closes: 888935 909424 919077 926670 Changes: node-xterm (3.8.1-1) unstable; urgency=medium . [ Ghislain Antony Vaillant ] * Change package section to javascript * Add recommended get-orig-source target . [ Pirate Praveen ] * New upstream version 3.7.0 (Closes: #909424) * Use salsa.debian.org in Vcs-* fields * Bump debhelper compatibility level to 11 * Bump Standards-Version to 4.2.1 (no changes needed) . [ Gordon Ball ] * Convert to pkg-js-tools * Fix FTBFS bugs (Closes: #888935, #919077) * Move node-xterm to /usr/share/nodejs (from /usr/lib/nodejs) * Standards-Version 4.5.0 * Debhelper compat level 12 (and drop debian/compat) * Patch several obsolete type names caught by newer node-typescript * New upstream version 3.8.1 (the earliest version containing a fix for CVE-2019-0542, closes: #926670) * Update URLs to github.com/xtermjs/xterm.js * Drop Files-Excluded and repacking config, as the relevant files no longer exist in the tarball * Drop d/copyright stanza for src/xterm.js which no longer exists * Set Rules-Requires-Root: no Checksums-Sha1: d35b358444c46c3c9f086ae9806ef43ae9a1cd33 2163 node-xterm_3.8.1-1.dsc 777a49e64267990b22d9abe1027a3d6f01143425 287514 node-xterm_3.8.1.orig.tar.gz eedea5b609583ac7bdc6176686149c580a42e13e 4596 node-xterm_3.8.1-1.debian.tar.xz aae19a72a484a3971a321cf041444b65fff84335 10860 node-xterm_3.8.1-1_amd64.buildinfo Checksums-Sha256: 0c49f783a9b2c8cb5b056d26a184ead496134e4f32641a78db42c35173a3e7a7 2163 node-xterm_3.8.1-1.dsc 81ffa6c425126878c32dc9bcdc5dd7a5a5bc862e2ef063fc9bcbe03cf2fee31d 287514 node-xterm_3.8.1.orig.tar.gz 54d647c0e72a5a5c19a2d9ff036014d40c7e13b6e55a68e2a85b28a62c5af20b 4596 node-xterm_3.8.1-1.debian.tar.xz 6f843325df8aac09f49d8ed191ad029560b6d642676269d7ecd5649447baee66 10860 node-xterm_3.8.1-1_amd64.buildinfo Files: e2af43800a39a58e8b894891ceb2934f 2163 javascript optional node-xterm_3.8.1-1.dsc 1b561d784cc784db39cb175346210f3e 287514 javascript optional node-xterm_3.8.1.orig.tar.gz 7bb8428adbba5ff63d31f40e3bd4c368 4596 javascript optional node-xterm_3.8.1-1.debian.tar.xz 0992fd868d884defb67d800c4efd30d6 10860 javascript optional node-xterm_3.8.1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE6PwpXIa418BJ+Xuno12v+60p6N4FAl4snXkACgkQo12v+60p 6N5UDhAAlBmVxi4ftOa6NeZS140KKUMtGSVPxqGhBc1JU7csPQIia1raTfKbmNoC 6aaYCW0UhtmEwVtK2mrSS2wUrKIEuwsV0VYFLSax0ed5nOGz7BqRSIq1WGbBZnMt q9FdCeE8BnITBWGBkjl7Oa0ZTD6IiKa471hd/Q4b+iWndK3xxvxiqmXy21d0ptJy aiz8i7bo8/UMJQHnvzb8lZBo64a4YEVhOpjYjr5wtJWN0CljAVsYqVe0vu0V29zQ
Bug#888935: marked as done (node-xterm FTBFS: error TS2339: Property 'parentElement' does not exist on type 'never')
Your message dated Sat, 25 Jan 2020 21:18:18 + with message-id and subject line Bug#919077: fixed in node-xterm 3.8.1-1 has caused the Debian Bug report #919077, regarding node-xterm FTBFS: error TS2339: Property 'parentElement' does not exist on type 'never' 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.) -- 919077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919077 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-xterm Version: 2.7.0+ds1-1 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-xterm.html ... debian/rules override_dh_auto_build make[1]: Entering directory '/build/1st/node-xterm-2.7.0+ds1' tsc --project . src/utils/Mouse.ts(30,80): error TS2339: Property 'parentElement' does not exist on type 'never'. debian/rules:19: recipe for target 'override_dh_auto_build' failed make[1]: *** [override_dh_auto_build] Error 2 --- End Message --- --- Begin Message --- Source: node-xterm Source-Version: 3.8.1-1 We believe that the bug you reported is fixed in the latest version of node-xterm, 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 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gordon Ball (supplier of updated node-xterm 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, 25 Jan 2020 19:35:53 + Source: node-xterm Architecture: source Version: 3.8.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Gordon Ball Closes: 888935 909424 919077 926670 Changes: node-xterm (3.8.1-1) unstable; urgency=medium . [ Ghislain Antony Vaillant ] * Change package section to javascript * Add recommended get-orig-source target . [ Pirate Praveen ] * New upstream version 3.7.0 (Closes: #909424) * Use salsa.debian.org in Vcs-* fields * Bump debhelper compatibility level to 11 * Bump Standards-Version to 4.2.1 (no changes needed) . [ Gordon Ball ] * Convert to pkg-js-tools * Fix FTBFS bugs (Closes: #888935, #919077) * Move node-xterm to /usr/share/nodejs (from /usr/lib/nodejs) * Standards-Version 4.5.0 * Debhelper compat level 12 (and drop debian/compat) * Patch several obsolete type names caught by newer node-typescript * New upstream version 3.8.1 (the earliest version containing a fix for CVE-2019-0542, closes: #926670) * Update URLs to github.com/xtermjs/xterm.js * Drop Files-Excluded and repacking config, as the relevant files no longer exist in the tarball * Drop d/copyright stanza for src/xterm.js which no longer exists * Set Rules-Requires-Root: no Checksums-Sha1: d35b358444c46c3c9f086ae9806ef43ae9a1cd33 2163 node-xterm_3.8.1-1.dsc 777a49e64267990b22d9abe1027a3d6f01143425 287514 node-xterm_3.8.1.orig.tar.gz eedea5b609583ac7bdc6176686149c580a42e13e 4596 node-xterm_3.8.1-1.debian.tar.xz aae19a72a484a3971a321cf041444b65fff84335 10860 node-xterm_3.8.1-1_amd64.buildinfo Checksums-Sha256: 0c49f783a9b2c8cb5b056d26a184ead496134e4f32641a78db42c35173a3e7a7 2163 node-xterm_3.8.1-1.dsc 81ffa6c425126878c32dc9bcdc5dd7a5a5bc862e2ef063fc9bcbe03cf2fee31d 287514 node-xterm_3.8.1.orig.tar.gz 54d647c0e72a5a5c19a2d9ff036014d40c7e13b6e55a68e2a85b28a62c5af20b 4596 node-xterm_3.8.1-1.debian.tar.xz 6f843325df8aac09f49d8ed191ad029560b6d642676269d7ecd5649447baee66 10860 node-xterm_3.8.1-1_amd64.buildinfo Files: e2af43800a39a58e8b894891ceb2934f 2163 javascript optional node-xterm_3.8.1-1.dsc 1b561d784cc784db39cb175346210f3e 287514 javascript optional node-xterm_3.8.1.orig.tar.gz 7bb8428adbba5ff63d31f40e3bd4c368 4596 javascript optional node-xterm_3.8.1-1.debian.tar.xz 0992fd868d884defb67d800c4efd30d6 10860 javascript optional node-xterm_3.8.1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE6PwpXIa418BJ+Xuno12v+60p6N4FAl4snXkACgkQo12v+60p 6N5UDhAAlBmVxi4ftOa6NeZS140KKUMtGSVPxqGhBc1JU7csPQIia1raTfKbmNoC 6aaYCW0UhtmEwVtK2mrSS2wUrKIEuwsV0VYFLSax0ed5nOGz7BqRSIq1WGbBZnMt q9FdCeE8BnITBWGBkjl7Oa0ZTD6IiKa471hd/Q4b+iWndK3xxvxiqmXy21d0ptJy
Processed: {pypy,python}-setuptools-scm are no longer built by src:setuptools-scm
Processing commands for cont...@bugs.debian.org: > severity 936179 serious Bug #936179 [src:backports.functools-lru-cache] backports.functools-lru-cache: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 937558 serious Bug #937558 [src:pytest] pytest: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 937832 serious Bug #937832 [src:python-importlib-metadata] python-importlib-metadata: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 938054 serious Bug #938054 [src:python-py] python-py: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 938285 serious Bug #938285 [src:python-zipp] python-zipp: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 936179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936179 937558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937558 937832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937832 938054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938054 938285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938285 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#888935: marked as done (node-xterm FTBFS: error TS2339: Property 'parentElement' does not exist on type 'never')
Your message dated Sat, 25 Jan 2020 21:18:17 + with message-id and subject line Bug#888935: fixed in node-xterm 3.8.1-1 has caused the Debian Bug report #888935, regarding node-xterm FTBFS: error TS2339: Property 'parentElement' does not exist on type 'never' 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.) -- 888935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-xterm Version: 2.7.0+ds1-1 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-xterm.html ... debian/rules override_dh_auto_build make[1]: Entering directory '/build/1st/node-xterm-2.7.0+ds1' tsc --project . src/utils/Mouse.ts(30,80): error TS2339: Property 'parentElement' does not exist on type 'never'. debian/rules:19: recipe for target 'override_dh_auto_build' failed make[1]: *** [override_dh_auto_build] Error 2 --- End Message --- --- Begin Message --- Source: node-xterm Source-Version: 3.8.1-1 We believe that the bug you reported is fixed in the latest version of node-xterm, 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 888...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gordon Ball (supplier of updated node-xterm 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, 25 Jan 2020 19:35:53 + Source: node-xterm Architecture: source Version: 3.8.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Gordon Ball Closes: 888935 909424 919077 926670 Changes: node-xterm (3.8.1-1) unstable; urgency=medium . [ Ghislain Antony Vaillant ] * Change package section to javascript * Add recommended get-orig-source target . [ Pirate Praveen ] * New upstream version 3.7.0 (Closes: #909424) * Use salsa.debian.org in Vcs-* fields * Bump debhelper compatibility level to 11 * Bump Standards-Version to 4.2.1 (no changes needed) . [ Gordon Ball ] * Convert to pkg-js-tools * Fix FTBFS bugs (Closes: #888935, #919077) * Move node-xterm to /usr/share/nodejs (from /usr/lib/nodejs) * Standards-Version 4.5.0 * Debhelper compat level 12 (and drop debian/compat) * Patch several obsolete type names caught by newer node-typescript * New upstream version 3.8.1 (the earliest version containing a fix for CVE-2019-0542, closes: #926670) * Update URLs to github.com/xtermjs/xterm.js * Drop Files-Excluded and repacking config, as the relevant files no longer exist in the tarball * Drop d/copyright stanza for src/xterm.js which no longer exists * Set Rules-Requires-Root: no Checksums-Sha1: d35b358444c46c3c9f086ae9806ef43ae9a1cd33 2163 node-xterm_3.8.1-1.dsc 777a49e64267990b22d9abe1027a3d6f01143425 287514 node-xterm_3.8.1.orig.tar.gz eedea5b609583ac7bdc6176686149c580a42e13e 4596 node-xterm_3.8.1-1.debian.tar.xz aae19a72a484a3971a321cf041444b65fff84335 10860 node-xterm_3.8.1-1_amd64.buildinfo Checksums-Sha256: 0c49f783a9b2c8cb5b056d26a184ead496134e4f32641a78db42c35173a3e7a7 2163 node-xterm_3.8.1-1.dsc 81ffa6c425126878c32dc9bcdc5dd7a5a5bc862e2ef063fc9bcbe03cf2fee31d 287514 node-xterm_3.8.1.orig.tar.gz 54d647c0e72a5a5c19a2d9ff036014d40c7e13b6e55a68e2a85b28a62c5af20b 4596 node-xterm_3.8.1-1.debian.tar.xz 6f843325df8aac09f49d8ed191ad029560b6d642676269d7ecd5649447baee66 10860 node-xterm_3.8.1-1_amd64.buildinfo Files: e2af43800a39a58e8b894891ceb2934f 2163 javascript optional node-xterm_3.8.1-1.dsc 1b561d784cc784db39cb175346210f3e 287514 javascript optional node-xterm_3.8.1.orig.tar.gz 7bb8428adbba5ff63d31f40e3bd4c368 4596 javascript optional node-xterm_3.8.1-1.debian.tar.xz 0992fd868d884defb67d800c4efd30d6 10860 javascript optional node-xterm_3.8.1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE6PwpXIa418BJ+Xuno12v+60p6N4FAl4snXkACgkQo12v+60p 6N5UDhAAlBmVxi4ftOa6NeZS140KKUMtGSVPxqGhBc1JU7csPQIia1raTfKbmNoC 6aaYCW0UhtmEwVtK2mrSS2wUrKIEuwsV0VYFLSax0ed5nOGz7BqRSIq1WGbBZnMt q9FdCeE8BnITBWGBkjl7Oa0ZTD6IiKa471hd/Q4b+iWndK3xxvxiqmXy21d0ptJy
Bug#891493: marked as done (numix-gtk-theme: Undocumented and very likely also broken Breaks against murrine-themes since 2.6.7-2)
Your message dated Sat, 25 Jan 2020 21:12:32 + with message-id and subject line Bug#891493: fixed in numix-gtk-theme 2.6.7-4+deb10u1 has caused the Debian Bug report #891493, regarding numix-gtk-theme: Undocumented and very likely also broken Breaks against murrine-themes since 2.6.7-2 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.) -- 891493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891493 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: numix-gtk-theme Version: 2.6.7-2 Since 2.6.7-2, numix-gtk-theme has a "Breaks: murrine-themes (<= 0.98.11)" without any mentioning (and especially without giving a reason) in debian/changelog. According to the commit message in https://salsa.debian.org/desktop-themes-team/numix-gtk-theme/commit/6eb0c14fb93ef740ef13e59551178726d4efd9b5 it's because of https://bugs.debian.org/623783 and https://bugs.debian.org/838994. But besides "Ugly workaround for #623783 and #838994" there's no real reason given, why this Breaks should workaround any of these two bugs. And I don't find any reason for this change in #623783. In #838994 there is the following dicussion, citing from the mail of Yves-Alexis Perez of 28 Sep 2016 at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838994#20: > > > > NB! I notice the recommendation is versioned. If reason for > > > > that is to avoid older versions being outright broken (e.g. due > > > > to bug#827134), then it does not work as intended (only > > > > versioned _depends_ is certain to be obeyed). Use a versioned > > > > _breaks_ instead. > > > > > > so something like: > > > > > > Recommends: murrine-themes > > > Breaks: murrine-themes (<< 0.98.1) ^^ > > > > Specifically addressing the versioning, yes. Does not address the issue > > on topic for this bugreport. > > In any case, I really don't believe that's something important enough > to lose time on it (specifically, I won't). As already stated, just > remove the packages you don't want. Please note that there is no talk about 0.98.11 but 0.98.1! Additionally, the mentioned Recommends of gtk2-engines-murrine on murrine-themes (which the suggested Breaks should complement) is versioned as ">= 0.98". Currently installing numix-gtk-theme wants to uninstall the _current_ version of murrine-themes from unstable which does not have any RC bug and which I hence does not consider broken enough to be kicked out by such a Breaks. This all leads me to the assumption that someone indeed did not "lose enough time on it" and added a Breaks against the wrong version (0.98.11 instead of 0.98.1) _and_ forgot to document it properly, too. If I'm right with this assumption, this would be a bug of severity serious and it should be fixed as follows: Fix the Breaks against murrine-themes themes to be versioned as "(<< 0.98)" or "(<<0.98.1)" and retro-actively add the missing changelog entry to 2.6.7-2. Or just drop it all again, as murrine-themes 0.98.1 and 0.98 were uploads from 2011 (and even wheezy/oldoldstable has 0.98.4) and there's probably no reason to add a Breaks against them nowadays. Or explain indepth why this Breaks should actually fix or workaround anything. It's not obvious at all and seems to do more harm than good. (If just the explaination is missing, it's probably of severity normal or minor.) -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (990, 'unstable'), (980, 'unstable-debug'), (600, 'testing'), (111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental'), (105, 'experimental-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/4 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/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages numix-gtk-theme depends on: ii gtk2-engines-murrine 0.98.2-2 ii numix-icon-theme 0~20171225-1 numix-gtk-theme recommends no packages. numix-gtk-theme suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: numix-gtk-theme Source-Version: 2.6.7-4+deb10u1 We believe that the bug you reported is fixed in the latest version of numix-gtk-theme, 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 891...@bugs.debian.org, and the
Bug#838994: marked as done (gtk2-engines-murrine: wrongly recommends murrine-themes)
Your message dated Sat, 25 Jan 2020 21:12:31 + with message-id and subject line Bug#838994: fixed in gtk2-engines-murrine 0.98.2-2+deb10u1 has caused the Debian Bug report #838994, regarding gtk2-engines-murrine: wrongly recommends murrine-themes 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.) -- 838994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838994 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gtk2-engines-murrine Version: 0.98.1.1-6 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I want to install greybird-gtk-theme, and only that theme. But due to gtk2-engines-murrine recommending murrine-themes, effectively I get a bunch of themes when I wanted only one. Package relationships are _directional_: Having murrine-themes recommend greybird-gtk-theme is sensible, because (some of) its contents has little use without the contents of that other package. Having gtk2-engines-murrine recommend recommend murrine-themes is less sensible, as its contents is perfectly usable without the contents of that other package. What would be sensible is to a) drop gtk2-engines-murrine recommends on murrine-themes, and b) have murrine-themes declare that it _enhances_ gtk2-engines-murrine (i.e. a reverse suggestion). NB! I notice the recommendation is versioned. If reason for that is to avoid older versions being outright broken (e.g. due to bug#827134), then it does not work as intended (only versioned _depends_ is certain to be obeyed). Use a versioned _breaks_ instead. - Jonas -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJX6oAuAAoJECx8MUbBoAEhj5cP/0307iXZ8YPIJkIS/4A4PgHV y2i4wWUo9gmcsR6NMA/MdoD05bCvv7sizb31uDvpSLEzC0sMa9rsKB3DT1qYIPMY zP1DrdSjw9RaZRjzjJmESHGx9o9F5xFAXlv/rW+yVWy55o5UMBpty27UP70lap4E tr0a9+P8KYnLUDmqXCSttLwc7ZGyYnQ4XcFcge1ToTCdPwCmUTBeVLSlZHCqTjpM ACpuEhyc8gOied0o5DsYiTEy4vBBHWzZgB/IZ5Ces2XcWe13i+R+sz2RNFK9UrCS 27mh98Tfw+PpZ22xbKSx0B/GHNAPojo1s5GrtKlmQFGa7euq/qPbl2V49mAYYXvb g36ycQWXeeEybhvR95xOYF6y9JMoB3QLG1cl/dxcGNKlR1bqqXacgGXMfnMzECW6 PG7FNsBgRf7jmN6tQ+LpOp9trAupzOe4YbpiSw4meIFk8Tk7l7qK3isVYAT8TcJj ynmgE21ueq+w4erJ8m1INVVXGi8+B1wDTsBY0ku6bdQf8ng7/PMUpCK6u/FtQKJx MF9iLFz1tyNtPziNCMrVlS6zKC3emrnTrX9tqmP3fz0WBOCjahifADJrIMna0Bfi a0ieNSpuCKjA94wNV4TxfEZFycr4jqqN2mBeH2JSbDRk8uIzJ6rTkkxOpDKhVoCF 2GvIntr5fxzkzXdoU7h9 =WvlS -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: gtk2-engines-murrine Source-Version: 0.98.2-2+deb10u1 We believe that the bug you reported is fixed in the latest version of gtk2-engines-murrine, 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 838...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel (supplier of updated gtk2-engines-murrine 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: Tue, 03 Dec 2019 08:47:15 +0100 Source: gtk2-engines-murrine Architecture: source Version: 0.98.2-2+deb10u1 Distribution: buster Urgency: medium Maintainer: Yves-Alexis Perez Changed-By: Mike Gabriel Closes: 838994 Changes: gtk2-engines-murrine (0.98.2-2+deb10u1) buster; urgency=medium . * debian/control: + Downgrade from R to S (gtk2-engine-themes): murrine-themes. (Closes: #838994). Checksums-Sha1: c0db16eee5b4d53dee41ae46680edfe7b01e0ace 2039 gtk2-engines-murrine_0.98.2-2+deb10u1.dsc 27998932022ca3210571a5670a7f237b930e1874 3524 gtk2-engines-murrine_0.98.2-2+deb10u1.debian.tar.xz af985e68ae3036cf18eb323e15a85c2d6cac80b3 12515 gtk2-engines-murrine_0.98.2-2+deb10u1_source.buildinfo Checksums-Sha256: 41aad452deb7b5628069690b035b4383686029ed2b5d7378c01d339a00bf5924 2039 gtk2-engines-murrine_0.98.2-2+deb10u1.dsc 7829d500ec45ef689b063e28b689b0263aaeb9bbafac7d142cb1b98a5e3db8cf 3524 gtk2-engines-murrine_0.98.2-2+deb10u1.debian.tar.xz 3628b43fe3ecb3858472ac801acf63f2c86d1a8036690cb90491b0e913675986 12515 gtk2-engines-murrine_0.98.2-2+deb10u1_source.buildinfo Files: 4e6f634864c5fca5e82c1a558f5ad1a6 2039 x11 optional gtk2-engines-murrine_0.98.2-2+deb10u1.dsc 1bcad37cd9b9296d86cfed71119d4c6d 3524 x11 optional gtk2-engines-murrine_0.98.2-2+deb10u1.debian.tar.xz
Bug#623783: marked as done (gtk2-engines-murrine: recommends murrine-themes needlessly)
Your message dated Sat, 25 Jan 2020 21:12:31 + with message-id and subject line Bug#838994: fixed in gtk2-engines-murrine 0.98.2-2+deb10u1 has caused the Debian Bug report #838994, regarding gtk2-engines-murrine: recommends murrine-themes needlessly 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.) -- 838994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838994 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gtk2-engines-murrine Severity: normal gtk2-engines-murrine recommends murrine-themes, but murrine-themes depends on gtk2-engines-murrine. this seems like an unnecesary recommendation, and prevents another theme from depending/recommending gtk2-engines-murrine without pulling in a very large recommended package. i'd think suggests might be more appropriate. live well, vagrant --- End Message --- --- Begin Message --- Source: gtk2-engines-murrine Source-Version: 0.98.2-2+deb10u1 We believe that the bug you reported is fixed in the latest version of gtk2-engines-murrine, 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 838...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel (supplier of updated gtk2-engines-murrine 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: Tue, 03 Dec 2019 08:47:15 +0100 Source: gtk2-engines-murrine Architecture: source Version: 0.98.2-2+deb10u1 Distribution: buster Urgency: medium Maintainer: Yves-Alexis Perez Changed-By: Mike Gabriel Closes: 838994 Changes: gtk2-engines-murrine (0.98.2-2+deb10u1) buster; urgency=medium . * debian/control: + Downgrade from R to S (gtk2-engine-themes): murrine-themes. (Closes: #838994). Checksums-Sha1: c0db16eee5b4d53dee41ae46680edfe7b01e0ace 2039 gtk2-engines-murrine_0.98.2-2+deb10u1.dsc 27998932022ca3210571a5670a7f237b930e1874 3524 gtk2-engines-murrine_0.98.2-2+deb10u1.debian.tar.xz af985e68ae3036cf18eb323e15a85c2d6cac80b3 12515 gtk2-engines-murrine_0.98.2-2+deb10u1_source.buildinfo Checksums-Sha256: 41aad452deb7b5628069690b035b4383686029ed2b5d7378c01d339a00bf5924 2039 gtk2-engines-murrine_0.98.2-2+deb10u1.dsc 7829d500ec45ef689b063e28b689b0263aaeb9bbafac7d142cb1b98a5e3db8cf 3524 gtk2-engines-murrine_0.98.2-2+deb10u1.debian.tar.xz 3628b43fe3ecb3858472ac801acf63f2c86d1a8036690cb90491b0e913675986 12515 gtk2-engines-murrine_0.98.2-2+deb10u1_source.buildinfo Files: 4e6f634864c5fca5e82c1a558f5ad1a6 2039 x11 optional gtk2-engines-murrine_0.98.2-2+deb10u1.dsc 1bcad37cd9b9296d86cfed71119d4c6d 3524 x11 optional gtk2-engines-murrine_0.98.2-2+deb10u1.debian.tar.xz f748e8b48480dc51bb4424041d7aee43 12515 x11 optional gtk2-engines-murrine_0.98.2-2+deb10u1_source.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAl3mEywVHHN1bndlYXZl ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxPLUQAKE8/vwyQTOKEhGEC9TU5fSB9o7q uxlYmQrg3YGni5sZNTsPaPl9zaG/bMUWHi6WWAiTql5LtphNE9dCVlWKanEpD3Pp Kc9qOTtU2bKNMqlZZSEyBlBkU8czKzi5q6wNMPUWZ4QAtRXetTV4xB4uDkqwLSsj wZ1R1b7ul9pxE6FjTX3wfjud9w2J147Qeyva7v8l41tPaXLaRAcovB2x8NzfZnU9 +Tzs3XBe0OPoo99fKL77PArLO0IOodGUI47y2CUcm34nieUar9M3YXD6CB4yAZOw jNrq2/GPwszF3ZKHzM37/C9GACwSH5qGS4BV3hg3VVhPIAnjMJ8XEve3vtLmlI47 z6GwEBKQ9nKEHbroHZK+Ih77CC1RyQcKadnZdFt0Qf+o332e9w22zR7tkWEBFb7l 2LfN1C/g5RuJ9EO5oOMYsxu6PJpWhv1iRFm3XjBqz8sGURwVKHNur28VLWkFiLP5 wqtVt31nSWEKB6iauMO0u9WTplwBjUC1+gSON0r6GOdLoIMkfXjOQuw/C97lQV3L 8Et9H+ygDCmqdgovpQQVhwf5LCW1JrlTY70QylLbTFg2R/dLYtcw5h2zzx7vJw89 iUKqNe0MO0N9jQoz3gVEIGnojzjPJhd1Lx4DzYdUoQKobDICrDvGNTCfSW1FbazI 6BIW65D7EH686POu =FEnd -END PGP SIGNATURE End Message ---
Bug#949847: syslog-ng FTBFS: configure: error: syslog-ng requires bison 3.4 or later
Source: syslog-ng Version: 3.25.1-1 Severity: serious Tags: ftbfs syslog-ng fails to build from source in unstable. A build log contains: | configure: error: syslog-ng requires bison 3.4 or later (traditional yacc is not enough). Your source tree seems to be from git, which doesn't have lib/cfg-grammar.c. Please install bison or use a distribution tarball. This seems a bit strange since it earlier finds: | checking for bison... bison -y Reproducible by reproducible builds: https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/syslog-ng_3.25.1-1.rbuild.log.gz Helmut
Bug#944696: marked as done (python-apt: relies on MD5 internally to download packages)
Your message dated Sat, 25 Jan 2020 19:03:19 +
with message-id
and subject line Bug#944696: fixed in python-apt 1.4.1
has caused the Debian Bug report #944696,
regarding python-apt: relies on MD5 internally to download packages
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.)
--
944696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944696
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-apt
Version: 1.8.4
Severity: serious
Justification: some people want to get rid of MD5Sum in indices
Hi,
While debugging a live-wrapper (lwr) failure that started occurring
(literally) overnight, I ended up discovering it was triggered by the
intel-microcode package's getting a security upgrade.
live-wrapper 0.10 isn't affected, but live-wrapper's master branch has
an extra commit that automatically enables security sources for stable
releases.
Here's the traceback for a simple build (with a local mirror but anyone
would do) with that master branch:
$ sudo lwr -d buster -m http://wodi.home/debian -f intel-microcode
[…]
DEBUG environment: LWR_MIRROR = 'http://wodi.home/debian'
DEBUG environment: LWR_EXTRA_PACKAGES = ''
DEBUG environment: LWR_BASE_DEBS = ''
DEBUG environment: LWR_DISTRIBUTION = 'buster'
DEBUG environment: LWR_FIRMWARE_PACKAGES = 'intel-microcode'
DEBUG environment: LWR_TASK_PACKAGES = ''
[…]
Downloading udebs for Debian Installer...
INFO Downloading udebs for Debian Installer...
Updating a local cache for amd64 buster ...
DEBUG Updating local cache...
CRITICAL Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/cliapp/app.py", line 193, in _run
self.process_args(args)
File "/usr/lib/python2.7/dist-packages/lwr/run.py", line 143, in
process_args
self.start_ops()
File "/usr/lib/python2.7/dist-packages/lwr/run.py", line 286, in start_ops
apt_udeb.download_udebs(exclude_list)
File "/usr/lib/python2.7/dist-packages/lwr/apt_udeb.py", line 157, in
download_udebs
self.download_apt_file(pkg_name, pool_dir, False)
File "/usr/lib/python2.7/dist-packages/lwr/apt_udeb.py", line 141, in
download_apt_file
version.fetch_binary(destdir=pkg_dir)
File "/usr/lib/python2.7/dist-packages/apt/package.py", line 867, in
fetch_binary
if _file_is_same(destfile, self.size, self._records.md5_hash):
SystemError: error return without exception set
After some debugging, it turned out that merely accessing the
self._records.md5_hash item is sufficient to reproduce this issue.
Looking at the current (as of 2019-11-14 00:27:00 UTC) indices for
buster/updates on security.debian.org, one can only see SHA256 entries
in Release and Packages files, which is likely the reason for
python-apt's explosion. I've asked #debian-ftp to add MD5Sum entries
back at least for buster/updates, and will file another bug report for
that in a moment to make sure it isn't lost.
Looking at even the most recent python-apt code in experimental (1.9.0),
MD5 still seems hardwired, e.g. in apt/packages.py's fetch_binary():
def fetch_binary(self, destdir='', progress=None):
# type: (str, AcquireProgress) -> str
"""Fetch the binary version of the package.
The parameter *destdir* specifies the directory where the package will
be fetched to.
The parameter *progress* may refer to an apt_pkg.AcquireProgress()
object. If not specified or None, apt.progress.text.AcquireProgress()
is used.
.. versionadded:: 0.7.10
"""
base = os.path.basename(self._records.filename)
destfile = os.path.join(destdir, base)
if _file_is_same(destfile, self.size, self._records.md5_hash):
logging.debug('Ignoring already existing file: %s' % destfile)
return os.path.abspath(destfile)
acq = apt_pkg.Acquire(progress or apt.progress.text.AcquireProgress())
acqfile = apt_pkg.AcquireFile(acq, self.uri, self._records.md5_hash, #
type: ignore # TODO: Do not use MD5 # nopep8
self.size, base, destfile=destfile)
acq.run()
if acqfile.status != acqfile.STAT_DONE:
raise FetchError("The item %r could not be fetched: %s" %
(acqfile.destfile, acqfile.error_text))
return os.path.abspath(destfile)
Notice the TODO on the apt_pkg.AcquireFile(), but it would probably
break in the same way as in the live-wrapper case a few lines before, on
the
Bug#902522: marked as done (sorl-thumbnail: FTBFS in buster/sid (failing tests))
Your message dated Sat, 25 Jan 2020 19:03:25 + with message-id and subject line Bug#902522: fixed in sorl-thumbnail 12.3+git20160928-2+deb9u1 has caused the Debian Bug report #902522, regarding sorl-thumbnail: FTBFS in buster/sid (failing tests) 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.) -- 902522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902522 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:sorl-thumbnail Version: 12.3+git20170708-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster with "dpkg-buildpackage -A" but it failed: [...] debian/rules build-indep dh build-indep --with python2,python3,sphinxdoc --buildsystem=pybuild dh_update_autotools_config -i -O--buildsystem=pybuild dh_autoreconf -i -O--buildsystem=pybuild dh_auto_configure -i -O--buildsystem=pybuild I: pybuild base:217: python2.7 setup.py config running config I: pybuild base:217: python3.6 setup.py config running config debian/rules override_dh_auto_build make[1]: Entering directory '/<>/sorl-thumbnail-12.3+git20170708' dh_auto_build I: pybuild base:217: /usr/bin/python setup.py build [... snipped ...] = test session starts == platform linux2 -- Python 2.7.15, pytest-3.3.2, py-1.5.3, pluggy-0.6.0 Django settings: tests.settings.pgmagick (from environment variable) rootdir: /<>/sorl-thumbnail-12.3+git20170708, inifile: setup.cfg plugins: django-3.1.2 collected 68 items tests/thumbnail_tests/test_alternative_resolutions.py . [ 1%] tests/thumbnail_tests/test_backends.py ...F.s.. [ 19%] tests/thumbnail_tests/test_commands.py [ 25%] tests/thumbnail_tests/test_engines.py ..s.ss [ 63%] tests/thumbnail_tests/test_filters.py s.s. [ 69%] tests/thumbnail_tests/test_kvstore.py . [ 70%] tests/thumbnail_tests/test_parsers.py . [ 77%] tests/thumbnail_tests/test_storage.py [ 83%] tests/thumbnail_tests/test_templatetags.py ss. [100%] === FAILURES === _ TestDescriptors.test_is_valid_image __ self = def test_is_valid_image(self): with same_open_fd_count(self): > self.ENGINE.is_valid_image(b'invalidbinaryimage.jpg') tests/thumbnail_tests/test_backends.py:99: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = raw_data = 'invalidbinaryimage.jpg' def is_valid_image(self, raw_data): blob = Blob() blob.update(raw_data) > im = Image(blob) E RuntimeError: Magick: Unable to deduce image format () reported by magick/blob.c:739 (BlobToImage) sorl/thumbnail/engines/pgmagick_engine.py:29: RuntimeError 1 failed, 59 passed, 8 skipped in 1.22 seconds debian/rules:22: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 1 make[1]: Leaving directory '/<>/sorl-thumbnail-12.3+git20170708' debian/rules:10: recipe for target 'build-indep' failed make: *** [build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 The above is how the build ends in my autobuilder and it's not necessarily the relevant part. The failure is not, however, related to using dpkg-buildpackage -A, as it also fails in reproducible builds: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sorl-thumbnail.html If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the page for this package. Thanks. --- End Message --- --- Begin Message --- Source: sorl-thumbnail Source-Version: 12.3+git20160928-2+deb9u1 We believe that the bug you reported is fixed in the latest version of sorl-thumbnail, 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 902...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian
Bug#934037: marked as done (sorl-thumbnail: FTBFS in stretch (RuntimeError: Magick: Unable to deduce image format))
Your message dated Sat, 25 Jan 2020 19:03:25 + with message-id and subject line Bug#902522: fixed in sorl-thumbnail 12.3+git20160928-2+deb9u1 has caused the Debian Bug report #902522, regarding sorl-thumbnail: FTBFS in stretch (RuntimeError: Magick: Unable to deduce image format) 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.) -- 902522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902522 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:sorl-thumbnail Version: 12.3+git20160928-2 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in stretch but it failed: [...] debian/rules build-indep dh build-indep --with python2,python3,sphinxdoc --buildsystem=pybuild dh: Compatibility levels before 9 are deprecated (level 7 in use) dh_testdir -i -O--buildsystem=pybuild dh_update_autotools_config -i -O--buildsystem=pybuild dh_auto_configure -i -O--buildsystem=pybuild dh_auto_configure: Compatibility levels before 9 are deprecated (level 7 in use) I: pybuild base:184: python2.7 setup.py config running config I: pybuild base:184: python3.5 setup.py config running config debian/rules override_dh_auto_build make[1]: Entering directory '/<>' dh_auto_build dh_auto_build: Compatibility levels before 9 are deprecated (level 7 in use) I: pybuild base:184: /usr/bin/python setup.py build running build running build_py creating /<>/.pybuild/pythonX.Y_2.7/build/sorl copying sorl/__init__.py -> /<>/.pybuild/pythonX.Y_2.7/build/sorl creating /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail copying sorl/thumbnail/compat.py -> /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail copying sorl/thumbnail/models.py -> /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail copying sorl/thumbnail/parsers.py -> /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail copying sorl/thumbnail/default.py -> /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail copying sorl/thumbnail/log.py -> /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail copying sorl/thumbnail/base.py -> /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail copying sorl/thumbnail/helpers.py -> /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail copying sorl/thumbnail/shortcuts.py -> /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail copying sorl/thumbnail/images.py -> /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail copying sorl/thumbnail/fields.py -> /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail copying sorl/thumbnail/__init__.py -> /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail creating /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/templatetags copying sorl/thumbnail/templatetags/thumbnail.py -> /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/templatetags copying sorl/thumbnail/templatetags/__init__.py -> /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/templatetags creating /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/admin copying sorl/thumbnail/admin/current.py -> /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/admin copying sorl/thumbnail/admin/__init__.py -> /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/admin creating /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/kvstores copying sorl/thumbnail/kvstores/dynamodb_kvstore.py -> /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/kvstores copying sorl/thumbnail/kvstores/redis_kvstore.py -> /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/kvstores copying sorl/thumbnail/kvstores/dbm_kvstore.py -> /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/kvstores copying sorl/thumbnail/kvstores/base.py -> /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/kvstores copying sorl/thumbnail/kvstores/cached_db_kvstore.py -> /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/kvstores copying sorl/thumbnail/kvstores/__init__.py -> /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/kvstores creating /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/migrations copying sorl/thumbnail/migrations/0001_initial.py -> /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/migrations copying sorl/thumbnail/migrations/__init__.py -> /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/migrations creating /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/conf copying sorl/thumbnail/conf/defaults.py -> /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/conf copying sorl/thumbnail/conf/__init__.py -> /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/conf creating /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/management copying sorl/thumbnail/management/__init__.py -> /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/management
Bug#949682: marked as done (Denial of Service due to cooking handling)
Your message dated Sat, 25 Jan 2020 19:02:11 + with message-id and subject line Bug#949682: fixed in modsecurity 3.0.3-1+deb10u1 has caused the Debian Bug report #949682, regarding Denial of Service due to cooking handling 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.) -- 949682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949682 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libmodsecurity3 Version: 3.0.3-1 Severity: serious Tags: security upstream A security issue was discovered by Ervin Hegedüs in Modsecurity 3.0.3. More info: https://www.trustwave.com/en-us/resources/blogs/spiderlabs-blog/modsecurity-denial-of-service-details-cve-2019-19886/ Fixed package is already in unstable. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: modsecurity Source-Version: 3.0.3-1+deb10u1 We believe that the bug you reported is fixed in the latest version of modsecurity, 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 949...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ervin Hegedus (supplier of updated modsecurity 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: Tue, 21 Jan 2020 21:52:59 + Source: modsecurity Binary: libmodsecurity-dev libmodsecurity3 libmodsecurity3-dbgsym Architecture: source amd64 Version: 3.0.3-1+deb10u1 Distribution: buster Urgency: medium Maintainer: Alberto Gonzalez Iniesta Changed-By: Ervin Hegedus Description: libmodsecurity-dev - ModSecurity v3 library component (development files) libmodsecurity3 - ModSecurity v3 library component Closes: 949682 Changes: modsecurity (3.0.3-1+deb10u1) buster; urgency=medium . * Fixes CVE-2019-19886 (Closes: #949682) Checksums-Sha1: 593200b3328a0c0c0df2238a1a0c012a8ffbb632 2138 modsecurity_3.0.3-1+deb10u1.dsc f2d657e370440f94fe85b4cf8bc55b9bed7445c5 9436 modsecurity_3.0.3-1+deb10u1.debian.tar.xz 8e8ba82f6a04b5d4429c4420d88656b218d5e52e 616272 libmodsecurity-dev_3.0.3-1+deb10u1_amd64.deb 97baf1eb33f4e5f3c47849623fe649dbe6b11500 22211488 libmodsecurity3-dbgsym_3.0.3-1+deb10u1_amd64.deb 67dc88aa3948d82f37e91bbe06ccb59b5de481d3 514324 libmodsecurity3_3.0.3-1+deb10u1_amd64.deb 05fa4edfae51dd648d1e746eafa664e537f99f26 7482 modsecurity_3.0.3-1+deb10u1_amd64.buildinfo Checksums-Sha256: ca383adb092af814d3a898dd0d7c914d8355b446920ec6a2434d80ccb96add29 2138 modsecurity_3.0.3-1+deb10u1.dsc 4cd4ea1227ac7e8c48fdb292aeb474ec8737ae08b0c38681e3996c0727b6a232 9436 modsecurity_3.0.3-1+deb10u1.debian.tar.xz e7a57aaeed5d48b058a053f35a5747408c9694acde5bbebaff117bc6cb4cfc45 616272 libmodsecurity-dev_3.0.3-1+deb10u1_amd64.deb 4447041a00c13400c006b4799a743bc222af8d8fd820306b4be1d21e7585cce2 22211488 libmodsecurity3-dbgsym_3.0.3-1+deb10u1_amd64.deb 5a5a77198b3478fa3efc8b5dec572a042629e24180b06b286538f2e22c7b47bb 514324 libmodsecurity3_3.0.3-1+deb10u1_amd64.deb c355f785e6ec283ec7a96a272103d6bb5e9e0e5f53774d559771b9709669c1e3 7482 modsecurity_3.0.3-1+deb10u1_amd64.buildinfo Files: bd2adde7a987588a9b2797054a2b4f7b 2138 libs optional modsecurity_3.0.3-1+deb10u1.dsc 6f6e1c7f87a76537ae5fa4dac31bac3a 9436 libs optional modsecurity_3.0.3-1+deb10u1.debian.tar.xz 56dbbd533a5858588f89a14d370588ba 616272 libdevel optional libmodsecurity-dev_3.0.3-1+deb10u1_amd64.deb 2e7e0ca52794e7b71db790930570334c 22211488 debug optional libmodsecurity3-dbgsym_3.0.3-1+deb10u1_amd64.deb 54dbf31ca43def2884ed7e2153cdbb27 514324 libs optional libmodsecurity3_3.0.3-1+deb10u1_amd64.deb e74ab1e6a05bb50578b189623e81e307 7482 libs optional modsecurity_3.0.3-1+deb10u1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEU0fL2D4wqetNfUvyAJszdWuaqlUFAl4sDMQACgkQAJszdWua
Bug#945602: marked as done (wrong path for constants.xml/presets.xml prevent the program from starting)
Your message dated Sat, 25 Jan 2020 19:02:18 + with message-id and subject line Bug#945602: fixed in qwinff 0.2.1-1+deb10u1 has caused the Debian Bug report #945602, regarding wrong path for constants.xml/presets.xml prevent the program from starting 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.) -- 945602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945602 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: qwinff Version: 0.2.1-1 Severity: grave Steps to reproduce the problem: - run qwinff from the desktop launcher of from a terminal emulator What happens: - An error dialog is shown with the message "Cannot load /home/user/constants.xml. The program will exit now." - In addition, when qwinff is launched from a terminal, there is the error "Failed to read file: "/home/user/constants.xml" - Clicking the "Ok" button closes the error message, but the program is in fact still running (appears in ps aux output/task managers). When run from a terminal it does not give back STDIN unless I stop/kill/Ctrl+C it Workaround: - a quick search reveals a file /usr/share/qwinff/constants.xml. Copying this file to /home/user/constants.xml makes the error message disappear. A second message is shown about missing presets.xml, the same workaround can be applied (it's also in /usr/share/qwinff/) Suggested fix: I don't know. The makefile (https://github.com/qwinff/qwinff/blob/master/Makefile#L65) explicitely says to install these files in $(DATA_PATH) so I assume this path was incorrectly set when the package was built. Rebuild and test this time :) Severity grave because the program does not work at all by default unless you find the workaround. Thank you in advance --- End Message --- --- Begin Message --- Source: qwinff Source-Version: 0.2.1-1+deb10u1 We believe that the bug you reported is fixed in the latest version of qwinff, 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 945...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated qwinff 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, 14 Jan 2020 12:22:34 -0500 Source: qwinff Architecture: source Version: 0.2.1-1+deb10u1 Distribution: buster Urgency: medium Maintainer: Gürkan Myczko Changed-By: Boyuan Yang Closes: 945602 Changes: qwinff (0.2.1-1+deb10u1) buster; urgency=medium . * debian/rules: Export DATA_PATH to fix crashing caused by incorrect file detection. (Closes: #945602) Checksums-Sha1: 90e46eb37c5208a6e769b0a7fd4027a5c69deb47 1770 qwinff_0.2.1-1+deb10u1.dsc 7443c8ffa9b3a8bce95ea3ecce203c2c64386d63 66436 qwinff_0.2.1-1+deb10u1.debian.tar.xz dc8d4b968940756d3672fb44d8da0ccbd8a1ea13 11239 qwinff_0.2.1-1+deb10u1_amd64.buildinfo Checksums-Sha256: b6e620a6e75a71dcdfcf777eb57bc138c5908dbdda2590bf3e81cc05dedd23c4 1770 qwinff_0.2.1-1+deb10u1.dsc 8d7a8a4395c4f0190484d8249fe6a092edc22debaee3e7bf7bf1c542e041 66436 qwinff_0.2.1-1+deb10u1.debian.tar.xz a2379e7ee84e6893ec9389b5be9cd7eee64ff599faef7256a3ef068014a86847 11239 qwinff_0.2.1-1+deb10u1_amd64.buildinfo Files: e651fda9447c889ccee60256092c7b09 1770 video optional qwinff_0.2.1-1+deb10u1.dsc 48d66f8b457580af71815677e6a7f50b 66436 video optional qwinff_0.2.1-1+deb10u1.debian.tar.xz c432c6ae474cb7d678b3ce7dfd65048f 11239 video optional qwinff_0.2.1-1+deb10u1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl4rdG4ACgkQwpPntGGC Ws4LXw//S2+6glk+/ZhGxL1TEQiNTevVsGp8MpXEXRIFk2SN/n+dhn5hBLfnUrtm aIqcE/k0c7nM3KuCjrj0VguRHzca2k+k1zR2qoSuqUuTJ5uu/bE6dizZ3kxmsNMT mhX4UCHsCyojNRl0StVFotAftsEcuLoaPJXf+dQ2AFPVK4I49JMcKCbp0NpRTP8N 5wjjuIDoDH8OD95K1yJTzJ1Mj6f47S5HiPrXQEOs8lxZcfzS+wJ8xepmv/GGKkLz /rOoZss+YdzA0XS/Axy+Tv7EiqEERrlKU8+HleiZVmqG1XMsgI7vtZ8FYlE+Q9Zo 65zsFSBHKwtO7EbBx65ZrltYIsmClBZXIGorKE15T0h73IMtNa0mdVTVHiH0qbRd RMsgoqwKAwpNBojsiDmnsk/oGJ96v8v57u3iyAvmecOHZf2gbijb3Vuw80xrlxT8 kdVGQwkuGNHKSOC6PwrewuoqCfE4SOBCHbO6YyCUutcF17VD8YCcbY6+/htSxVb+ 1sAaltP6+rwuHUVRn+mcq7FYMu3ZKVxiq+JmLyxy/nFhTgTtRJNH1HKPJUp2tzdw ksQWqVt0Yp5Bj7a6zGIiq0GnmKBlrZzKhXFB4fKuXkUIT0z3+/erP/X/5Z2h3GyH
Bug#944696: marked as done (python-apt: relies on MD5 internally to download packages)
Your message dated Sat, 25 Jan 2020 19:02:12 +
with message-id
and subject line Bug#944696: fixed in python-apt 1.8.4.1
has caused the Debian Bug report #944696,
regarding python-apt: relies on MD5 internally to download packages
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.)
--
944696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944696
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-apt
Version: 1.8.4
Severity: serious
Justification: some people want to get rid of MD5Sum in indices
Hi,
While debugging a live-wrapper (lwr) failure that started occurring
(literally) overnight, I ended up discovering it was triggered by the
intel-microcode package's getting a security upgrade.
live-wrapper 0.10 isn't affected, but live-wrapper's master branch has
an extra commit that automatically enables security sources for stable
releases.
Here's the traceback for a simple build (with a local mirror but anyone
would do) with that master branch:
$ sudo lwr -d buster -m http://wodi.home/debian -f intel-microcode
[…]
DEBUG environment: LWR_MIRROR = 'http://wodi.home/debian'
DEBUG environment: LWR_EXTRA_PACKAGES = ''
DEBUG environment: LWR_BASE_DEBS = ''
DEBUG environment: LWR_DISTRIBUTION = 'buster'
DEBUG environment: LWR_FIRMWARE_PACKAGES = 'intel-microcode'
DEBUG environment: LWR_TASK_PACKAGES = ''
[…]
Downloading udebs for Debian Installer...
INFO Downloading udebs for Debian Installer...
Updating a local cache for amd64 buster ...
DEBUG Updating local cache...
CRITICAL Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/cliapp/app.py", line 193, in _run
self.process_args(args)
File "/usr/lib/python2.7/dist-packages/lwr/run.py", line 143, in
process_args
self.start_ops()
File "/usr/lib/python2.7/dist-packages/lwr/run.py", line 286, in start_ops
apt_udeb.download_udebs(exclude_list)
File "/usr/lib/python2.7/dist-packages/lwr/apt_udeb.py", line 157, in
download_udebs
self.download_apt_file(pkg_name, pool_dir, False)
File "/usr/lib/python2.7/dist-packages/lwr/apt_udeb.py", line 141, in
download_apt_file
version.fetch_binary(destdir=pkg_dir)
File "/usr/lib/python2.7/dist-packages/apt/package.py", line 867, in
fetch_binary
if _file_is_same(destfile, self.size, self._records.md5_hash):
SystemError: error return without exception set
After some debugging, it turned out that merely accessing the
self._records.md5_hash item is sufficient to reproduce this issue.
Looking at the current (as of 2019-11-14 00:27:00 UTC) indices for
buster/updates on security.debian.org, one can only see SHA256 entries
in Release and Packages files, which is likely the reason for
python-apt's explosion. I've asked #debian-ftp to add MD5Sum entries
back at least for buster/updates, and will file another bug report for
that in a moment to make sure it isn't lost.
Looking at even the most recent python-apt code in experimental (1.9.0),
MD5 still seems hardwired, e.g. in apt/packages.py's fetch_binary():
def fetch_binary(self, destdir='', progress=None):
# type: (str, AcquireProgress) -> str
"""Fetch the binary version of the package.
The parameter *destdir* specifies the directory where the package will
be fetched to.
The parameter *progress* may refer to an apt_pkg.AcquireProgress()
object. If not specified or None, apt.progress.text.AcquireProgress()
is used.
.. versionadded:: 0.7.10
"""
base = os.path.basename(self._records.filename)
destfile = os.path.join(destdir, base)
if _file_is_same(destfile, self.size, self._records.md5_hash):
logging.debug('Ignoring already existing file: %s' % destfile)
return os.path.abspath(destfile)
acq = apt_pkg.Acquire(progress or apt.progress.text.AcquireProgress())
acqfile = apt_pkg.AcquireFile(acq, self.uri, self._records.md5_hash, #
type: ignore # TODO: Do not use MD5 # nopep8
self.size, base, destfile=destfile)
acq.run()
if acqfile.status != acqfile.STAT_DONE:
raise FetchError("The item %r could not be fetched: %s" %
(acqfile.destfile, acqfile.error_text))
return os.path.abspath(destfile)
Notice the TODO on the apt_pkg.AcquireFile(), but it would probably
break in the same way as in the live-wrapper case a few lines before, on
the
Bug#949571: marked as done (naev should not use the private binutils shared libraries)
Your message dated Sat, 25 Jan 2020 18:35:51 + with message-id and subject line Bug#949571: fixed in naev 0.7.0-3 has caused the Debian Bug report #949571, regarding naev should not use the private binutils shared libraries 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.) -- 949571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949571 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:naev Version: 0.7.0-2 Severity: serious Tags: sid bullseye naev should not use the private binutils shared libraries. If it cannot be dropped, then please link those statically and document it with the Built-Using tag in the binary package. --- End Message --- --- Begin Message --- Source: naev Source-Version: 0.7.0-3 We believe that the bug you reported is fixed in the latest version of naev, 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 949...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Federico Ceratto (supplier of updated naev 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, 25 Jan 2020 17:27:10 + Source: naev Architecture: source Version: 0.7.0-3 Distribution: unstable Urgency: medium Maintainer: Federico Ceratto Changed-By: Federico Ceratto Closes: 949571 Changes: naev (0.7.0-3) unstable; urgency=medium . * Remove binutils-dev build dependency (Closes: #949571) Checksums-Sha1: 6f8edea03cbadc46fc18a849e6e6c6c3788a792a 2273 naev_0.7.0-3.dsc b27726b44c0290f90a011897f1b24862b41428ba 14960 naev_0.7.0-3.debian.tar.xz f17623765f85fe28dfadce803813f549baa70980 12221 naev_0.7.0-3_amd64.buildinfo Checksums-Sha256: 2cb106e0af927901a4bf0005bca38f6386f06a2e24368f59c60b61025f9003d4 2273 naev_0.7.0-3.dsc fe45c17fffa0b526f5c2afb86715a4a10553171437dcef07b0a3e613bc4a82ba 14960 naev_0.7.0-3.debian.tar.xz f2247f08353cd6b9b65e01fd666cd6c7800a28254f087cfa46c124b3ba94 12221 naev_0.7.0-3_amd64.buildinfo Files: 43c5e6e7cedbab344349605ec3895c92 2273 games optional naev_0.7.0-3.dsc 61ef20fe5ab5c7e021c1a45b90fa7c4d 14960 games optional naev_0.7.0-3.debian.tar.xz 2596e58aca056d2978e968c97e6f1ffa 12221 games optional naev_0.7.0-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfKfd+zM5IUCMbyuWbzG8RPUXfaoFAl4sgdEACgkQbzG8RPUX faoRJQ//Tt6I9wDuhICsjhads7RPOnKiUtmqoqoS24RmFZHKRzvusguY0Q47qpne 82aK9aQy437dnHs2U+pbzpXWdsM/1m42aiVfF/oGXmXA3HIOHC3aYSFkop9QBB5E 4eZwj9HMPgrYgblG381R5WBMuUTLn+2yV3P67aFM7fL6TvH1H131eixb+g0Rlj9E D4fnsO5DVsBU3RueRoc9XUp036gfUb35EJ7ol5/+q4Qph8qQ3q8tNeJtwjvnOPSA gvvoay2UjOGr6SYtIJmdpt+oiXfwKnUnydDstS6Ng1icOEGjLM2i8+Qf9jCoBs9P TICas5+YHNIgAXW43R4mQySzx4k/zkNHAcSp6Tx4P5AtCvkCjkWYHLSLLslE8Zxo kAV7NxgtFqkeUOKN9PZ2h6Ii8tIE0ngOUdVNEZdkgHxmFzojlFZr734s5pZJbcWk ShO1Sfupha4DSOW31fQ69fluMqHZ3oz4/1yIlWNXnLvCQFWEBPZbGZ0OGX0oz2rP NrbPkxJUreFCPug6hiSm0Wda12A//7TdW0ca2LRO3pmrlNmbhMEpFDS9P/Wp3jVV jhPtNXtdpkoZsT1yH+dQ+Ood4HE86Slaz2VQ96WgwfHdSeKKdciU6vWufpiamEPw Uoo7qV/3+FKOatuHgYojZaBHJQJPLVyJNymp3nFF9uuG+z/w2R0= =0LU7 -END PGP SIGNATURE End Message ---
Bug#949758: marked as done (archmage: Missing build dependencies on python3-sgmllib3k and python3-chm)
Your message dated Sat, 25 Jan 2020 18:04:38 + with message-id and subject line Bug#949758: fixed in archmage 1:0.4.1-2 has caused the Debian Bug report #949758, regarding archmage: Missing build dependencies on python3-sgmllib3k and python3-chm 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.) -- 949758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949758 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: archmage Version: 1:0.4.1-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=archmage=all=1%3A0.4.1-1=1577227085=0 ... ERRORS _ ERROR collecting .pybuild/cpython3_3.8/build/tests/test_openclose.py _ ImportError while importing test module '/<>/.pybuild/cpython3_3.8/build/tests/test_openclose.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: tests/test_openclose.py:1: in import sys, archmage.cli, pathlib, tempfile, errno, shutil, contextlib archmage/cli.py:57: in from archmage.CHM import CHMFile, Action archmage/CHM.py:34: in from archmage.CHMParser import SitemapFile, PageLister, ImageCatcher, TOCCounter#, HeadersCounter archmage/CHMParser.py:24: in import sgmllib, urllib.request, urllib.error, urllib.parse E ModuleNotFoundError: No module named 'sgmllib' ... --- End Message --- --- Begin Message --- Source: archmage Source-Version: 1:0.4.1-2 We believe that the bug you reported is fixed in the latest version of archmage, 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 949...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mikhail Gusarov (supplier of updated archmage 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, 25 Jan 2020 18:39:41 +0100 Source: archmage Architecture: source Version: 1:0.4.1-2 Distribution: unstable Urgency: low Maintainer: Mikhail Gusarov Changed-By: Mikhail Gusarov Closes: 949758 Changes: archmage (1:0.4.1-2) unstable; urgency=low . * Add missing python3-sgmllib3k build-dependency (Closes: #949758) Checksums-Sha1: 7cabf54a0e5e6c89a9f2e10fbfad9122ed046e26 1723 archmage_0.4.1-2.dsc 6ecbeab2e391bd314c7eabb91f033a8163d91002 4448 archmage_0.4.1-2.debian.tar.xz 125075a103548ae48551e2c5e149f6e73c947998 5261 archmage_0.4.1-2_source.buildinfo Checksums-Sha256: 3b2f044a968ce15062ccff1024a8f289c94fe5ae836d638842afa31d68175f6a 1723 archmage_0.4.1-2.dsc 1be7d2ca59e1f6203a00c959b16ce8b84dc8d7d1bff9e70bafdfaea1bc2ea554 4448 archmage_0.4.1-2.debian.tar.xz ac723ebc08aa39715b7e4ab026c0f26d736437a9f885484a71f1174d61ef00f9 5261 archmage_0.4.1-2_source.buildinfo Files: cb006ece72c0cf55eaf3c0bb1d504519 1723 utils optional archmage_0.4.1-2.dsc 4281a7b4b02f04f17b13b8176743eb6a 4448 utils optional archmage_0.4.1-2.debian.tar.xz 8b9b26d091e4eca22170951aa754eb86 5261 utils optional archmage_0.4.1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEE6mdM4hvGehkaRy4s/eS3QibJkzgFAl4sfcgACgkQ/eS3QibJ kzgN6gf/SMUiiU6CpkOVnfdaRMRnexGf+NhDajVgMqsjdmrGFaZeiF8Z0Sp9YvWO 45d7wKvrf/9YKqdQDLyht9qj/GE9tVHUwvZj4WMGue89ra269SWoeNqgyVrUcngd g3POG29sRX7o9Df9+HWv1vgAzF+s5qUnLYbRlGtZN/jpnYfxMcawXXTyMF/7mYnI EQxWEQ/KKbl9GdpiTt3pu99pf9oaGm4/JKBoaN1pkGXqhvFZqzzs4gdUEC7BzHWm N/Px9khjGKxJTMeMwZQpzSiLUrUlsXLAj7WK9ACrvFscTQnvbGllozs0owEScz40 cyiRklDEHMjmbJFAk/7G754wKaentQ== =Frri -END PGP SIGNATURE End Message ---
Bug#947571: marked as pending in netpanzer
Control: tag -1 pending Hello, Bug #947571 in netpanzer 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/games-team/netpanzer/commit/4d1ed83b1617f6c4e4840b7088d57d08b3e00605 Fix build with Python3-enabled scons Closes: #947571 (this message was generated automatically) -- Greetings https://bugs.debian.org/947571
Processed: Bug#947571 marked as pending in netpanzer
Processing control commands: > tag -1 pending Bug #947571 [src:netpanzer] FTBFS with scons 3.1.2-1 Added tag(s) pending. -- 947571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947571 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 949264 in movit/1.6.3-3, fixed 949264 in movit/1.6.3-4
Processing commands for cont...@bugs.debian.org:
> found 949264 movit/1.6.3-3
Bug #949264 {Done: se...@debian.org (Steinar H. Gunderson)} [movit] nageru:
FTBFS on arm/i386/mipsel architectures
Marked as found in versions movit/1.6.3-3 and reopened.
> fixed 949264 movit/1.6.3-4
Bug #949264 [movit] nageru: FTBFS on arm/i386/mipsel architectures
Marked as fixed in versions movit/1.6.3-4.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
949264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949264
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#949835: lirc ftbfs with python 3.8
Package: src:lirc
Version: 0.10.1-6
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.8
lirc ftbfs with python 3.8:
[...]
debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
tools/lirc-lsplugins -U plugins/.libs -s | tee summary
Warning: cannot open /etc/lirc/lirc_options.conf
Plugins: 40
Drivers: 51
Errors: 0
grep -q "Errors: 0" summary && rm summary
case $(dpkg-architecture -qDEB_HOST_GNU_SYSTEM) in \
kfreebsd* | gnu) \
: ;; \
*) \
cd python-pkg/tests; \
python3 -m unittest discover && rm backend.log \
;; \
esac
.../<>/python-pkg/lirc/async_client.py:66: DeprecationWarning: The
loop argument is deprecated since Python 3.8, and scheduled for removal in
Python 3.10.
self._queue = asyncio.Queue(loop=self._loop)
/usr/lib/python3.8/asyncio/queues.py:48: DeprecationWarning: The loop argument
is deprecated since Python 3.8, and scheduled for removal in Python 3.10.
self._finished = locks.Event(loop=loop)
...E
==
ERROR: testReceiveTimeout (test_client.ReceiveTests)
Generate a TimeoutException if there is no data
--
Traceback (most recent call last):
File "/<>/python-pkg/tests/test_client.py", line 131, in
testReceiveTimeout
self.assertRaises(lirc.TimeoutException, conn.readline, 0.1)
File "/usr/lib/python3.8/unittest/case.py", line 816, in assertRaises
return context.handle('assertRaises', args, kwargs)
File "/usr/lib/python3.8/unittest/case.py", line 202, in handle
callable_obj(*args, **kwargs)
File "/<>/python-pkg/lirc/client.py", line 281, in readline
code = self._connection.readline(timeout)
File "/<>/python-pkg/lirc/client.py", line 222, in readline
start = time.clock()
AttributeError: module 'time' has no attribute 'clock'
--
Ran 7 tests in 1.136s
FAILED (errors=1)
Processed: reassign 949264 to movit
Processing commands for cont...@bugs.debian.org:
> reassign 949264 movit
Bug #949264 {Done: se...@debian.org (Steinar H. Gunderson)} [nageru] nageru:
FTBFS on arm/i386/mipsel architectures
Bug reassigned from package 'nageru' to 'movit'.
No longer marked as found in versions nageru/1.9.1-1.1.
No longer marked as fixed in versions movit/1.6.3-4.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
949264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949264
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#949834: firefox-esr: illegal instruction in /usr/lib/firefox-esr/libxul.so
Package: firefox-esr Version: 68.4.1esr-1 Severity: critical Dear maintainer: Firefox cannot be started due to an illegal instruction: $ firefox-esr -safe-mode illegal instruction valgrind /usr/bin/firefox-essr -safe-mode ... ==2805== ==2805== Invalid free() / delete / delete[] / realloc() ==2805==at 0x4849FE0: free (vg_replace_malloc.c:540) ==2805==by 0x7E0D9F7: ??? (in /usr/lib/firefox-esr/libxul.so) ==2805==by 0x7627F37: ??? (in /usr/lib/firefox-esr/libxul.so) ==2805==by 0x76281DB: ??? (in /usr/lib/firefox-esr/libxul.so) ==2805==by 0xA567F0F: ??? (in /usr/lib/firefox-esr/libxul.so) ==2805==by 0xA569227: ??? (in /usr/lib/firefox-esr/libxul.so) ==2805==by 0xA6FD98B: ??? (in /usr/lib/firefox-esr/libxul.so) ==2805==by 0xA6FDF6F: ??? (in /usr/lib/firefox-esr/libxul.so) ==2805==by 0xA6FE477: ??? (in /usr/lib/firefox-esr/libxul.so) ==2805==by 0x10E957: ??? (in /usr/lib/firefox-esr/firefox-esr) ==2805==by 0x10E09B: ??? (in /usr/lib/firefox-esr/firefox-esr) ==2805==by 0x4AE72EB: (below main) (libc-start.c:308) ==2805== Address 0x1ba65820 is in a rw- anonymous segment ==2805== disInstr(arm64): unhandled instruction 0x disInstr(arm64): ' ' ' ' ==2805== valgrind: Unrecognised instruction at address 0xa5681f0. ==2805==at 0xA5681F0: ??? (in /usr/lib/firefox-esr/libxul.so) ==2805== Your program just tried to execute an instruction that Valgrind ==2805== did not recognise. There are two possible reasons for this. ==2805== 1. Your program has a bug and erroneously jumped to a non-code ==2805==location. If you are running Memcheck and you just saw a ==2805==warning about a bad jump, it's probably your program's fault. ==2805== 2. The instruction is legitimate but Valgrind doesn't handle it, ==2805==i.e. it's Valgrind's fault. If you think this is the case or ==2805==you are not sure, please let us know and we'll try to fix it. ==2805== Either way, Valgrind will now raise a SIGILL signal which will ==2805== probably kill your program. ==2805== ==2805== Process terminating with default action of signal 4 (SIGILL) ==2805==at 0x48934AC: raise (raise.c:46) ==2805==by 0xA6ED42B: ??? (in /usr/lib/firefox-esr/libxul.so) ==2805==by 0xAEBD00F: ??? (in /usr/lib/firefox-esr/libxul.so) ==2805==by 0x580CAC8F: ??? (in /usr/lib/aarch64-linux-gnu/valgrind/memcheck-arm64-linux) ==2805== ==2805== HEAP SUMMARY: ==2805== in use at exit: 13,138,636 bytes in 66,191 blocks ==2805== total heap usage: 329,160 allocs, 285,076 frees, 48,657,728 bytes allocated ==2805== ==2805== LEAK SUMMARY: ==2805==definitely lost: 6,015 bytes in 94 blocks ==2805==indirectly lost: 36,096 bytes in 1,025 blocks ==2805== possibly lost: 1,570,965 bytes in 14,699 blocks ==2805==still reachable: 11,374,992 bytes in 49,176 blocks ==2805== of which reachable via heuristic: ==2805== length64 : 7,048 bytes in 106 blocks ==2805== newarray : 48,856 bytes in 816 blocks ==2805== multipleinheritance: 3,560 bytes in 8 blocks ==2805== suppressed: 0 bytes in 0 blocks ==2805== Rerun with --leak-check=full to see details of leaked memory ==2805== ==2805== For lists of detected and suppressed errors, rerun with: -s ==2805== ERROR SUMMARY: 22326 errors from 305 contexts (suppressed: 0 from 0) Illegal instruction -- Package-specific info: -- Addons package information -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: arm64 (aarch64) Kernel: Linux 5.4.0-3-arm64 (SMP w/4 CPU cores) 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) LSM: AppArmor: enabled Versions of packages firefox-esr depends on: ii debianutils 4.9.1 ii fontconfig2.13.1-2+b1 ii libasound21.2.1.2-2 ii libatk1.0-0 2.34.1-1 ii libc6 2.29-9 ii libcairo-gobject2 1.16.0-4 ii libcairo2 1.16.0-4 ii libdbus-1-3 1.12.16-2 ii libdbus-glib-1-2 0.110-5 ii libevent-2.1-72.1.11-stable-1 ii libffi6 3.2.1-9 ii libfontconfig12.13.1-2+b1 ii libfreetype6 2.10.1-2 ii libgcc1 1:9.2.1-22 ii libgdk-pixbuf2.0-02.40.0+dfsg-2 ii libglib2.0-0 2.62.4-1 ii libgtk-3-03.24.13-1 ii libjsoncpp1 1.7.4-3+b1 ii libnspr4 2:4.24-1 ii libnss3 2:3.45-1 ii libpango-1.0-01.42.4-7 ii libsqlite3-0 3.30.1+fossil191229-1 ii libstartup-notification0 0.12-6 ii libstdc++69.2.1-22 ii libx11-6 2:1.6.8-1 ii libx11-xcb1 2:1.6.8-1 ii
Processed: Bug#947554 marked as pending in boswars
Processing control commands: > tag -1 pending Bug #947554 [src:boswars] FTBFS with scons 3.1.2-1 Added tag(s) pending. -- 947554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947554 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949832: src:python-publicsuffix: Should not be released with Bullseye
Package: src:python-publicsuffix Severity: serious Upstream has said this module should not be used anymore. Here's an excerpt from the current package description: Deprecated Please don’t use this module. It is provided for historical reasons only. New code should instead use one of the other libraries that provide similar functionality. For example: publicsuffix2 publicsuffixlist I have packaged publicsuffix2 as a replacement and tested one of the two rdepends to verify that porting from publicsuffix to publicsuffix2 is as simples as changing the import. At this moment, publicsuffix2 is still in New, but once it is in the archive, rdepends (authheaders and bley) should be updated. Scott K
Bug#947554: marked as pending in boswars
Control: tag -1 pending Hello, Bug #947554 in boswars 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/games-team/boswars/commit/7ba3a5124c2c5072e88d63be8e2bb9ee60c1e988 Fix build with Python3-enabled scons versions Closes: #947554 (this message was generated automatically) -- Greetings https://bugs.debian.org/947554
Bug#949828: marked as done (libnetcdf-c++4-1: underlinked libnetcdf_c++4.so.1: undefined symbol: nc_*)
Your message dated Sat, 25 Jan 2020 16:05:43 + with message-id and subject line Bug#949828: fixed in netcdf-cxx 4.3.1-2 has caused the Debian Bug report #949828, regarding libnetcdf-c++4-1: underlinked libnetcdf_c++4.so.1: undefined symbol: nc_* 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.) -- 949828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libnetcdf-c++4-1 Version: 4.3.1-1 Severity: serious Control: affects -1 + src:python-escript Hi, python-escript FTBFS during a binNMU with Import error for esys.weipa /usr/lib/x86_64-linux-gnu/libnetcdf_c++4.so.1: undefined symbol: nc_get_var1_ulonglong https://buildd.debian.org/status/fetch.php?pkg=python-escript=amd64=5.4-4%2Bb1=1579900228=0 libnetcdf_c++4.so.1 uses a bunch of nc_* symbols, but is not linked against any netcdf library: ldd /usr/lib/x86_64-linux-gnu/libnetcdf_c++4.so.1 linux-vdso.so.1 (0x7ffe6adc1000) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x7fed279c3000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fed27803000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7fed277e9000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fed276a4000) /lib64/ld-linux-x86-64.so.2 (0x7fed27bf5000) Andreas --- End Message --- --- Begin Message --- Source: netcdf-cxx Source-Version: 4.3.1-2 We believe that the bug you reported is fixed in the latest version of netcdf-cxx, 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 949...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bas Couwenberg (supplier of updated netcdf-cxx 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, 25 Jan 2020 16:42:23 +0100 Source: netcdf-cxx Architecture: source Version: 4.3.1-2 Distribution: unstable Urgency: medium Maintainer: Debian GIS Project Changed-By: Bas Couwenberg Closes: 949828 Changes: netcdf-cxx (4.3.1-2) unstable; urgency=medium . * Bump Standards-Version to 4.5.0, no changes. * Add -lnetcdf to CXXFLAGS. (closes: #949828) Checksums-Sha1: 2fd0268505913d37162bb51e9dbba7b444eaacca 2331 netcdf-cxx_4.3.1-2.dsc ec603af059baec6d4ad4d43c8eac53274c6ce38d 11804 netcdf-cxx_4.3.1-2.debian.tar.xz 39fdaa7534f4939700836db3ca11627d7d8e15ce 10443 netcdf-cxx_4.3.1-2_amd64.buildinfo Checksums-Sha256: 6040ed1e9798e9d369d0f555adf0f6793362ac6d730aae14172c2c614ef012fb 2331 netcdf-cxx_4.3.1-2.dsc 2891f92040463cab33a0bf865c555e58204f2f858b419e39483ba4161f07815c 11804 netcdf-cxx_4.3.1-2.debian.tar.xz 20625ff50cd082ddc2748ffcc807b189a6dcc3f621002c1e05788ed877bed2d2 10443 netcdf-cxx_4.3.1-2_amd64.buildinfo Files: 6185e11f6bc62057971ea2a87566004a 2331 science optional netcdf-cxx_4.3.1-2.dsc 6f062027c2549363862963e01333f993 11804 science optional netcdf-cxx_4.3.1-2.debian.tar.xz d1cf1d69b03d8884888f292347ede96d 10443 science optional netcdf-cxx_4.3.1-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAl4sY8YACgkQZ1DxCuiN SvGEVA/7Bs2iSoAbASczOcDzGG3IIwgPAIPfd6gz62I1eRwMZBFa5TxdDKC3nUiZ jBebNXCR/S8hVolKwzjsOBdeJVCnA10CJLmKiOPZKjxEydsdXfyXSSgvyXDq7mgB kEO5BuquSTEteIazanCzr08SN2QXlh+wUvLteAG4IwdJ0vjA1yAHkuFGlozDjey3 p/9ZKMDwbxDBgpm+Y1kaDo4gryUMOM/w0Hc5C7a96HmbYGhucIc4DhT54q2gM6Ys v/TZPhZ9WGjGpyYUYZym6QbRI2vbhc/s2o3wfwmeWClK04c4wsrGyDhcp7dItJ4u VyZBOY8MEsDaRqhSuUH/BRosEcNGo1RR9zj54vkHT2rlHg9dmed/7p4gSOswJzNg JKgWRoJN6ohsBmJS7e1bDdsQHpuPmlanGgqS+IsCmReD/UMKGRYPC4BQzz+KoEQK nZwegt1AiNv5C06N6AzwH/d13XZs+P/IK6CwrgGbEiSYkrnVZjkwrXGvCl9FbaKr or5qt8aRA2egG2x4H+TuAa9odsP65G7T5OayZSk+b8ydv8aOfXvr9EG3ZI36PP8G O8ibSslFKoli13hF+rtHCnjU42K+MxPrPIwk6cmS7yPuTr5pRfxXZFKIamgzweFL 81Rv44K1n2AXxdJbPGjMyZ7OrFNUCux4BzOf2nfJzufwWrkJs/k= =ePsl -END PGP SIGNATURE End Message ---
Bug#949828: libnetcdf-c++4-1: underlinked libnetcdf_c++4.so.1: undefined symbol: nc_*
Control: tags -1 upstream pending Control: forwarded -1 https://github.com/Unidata/netcdf-cxx4/issues/86 On 1/25/20 4:38 PM, Andreas Beckmann wrote: > On 25/01/2020 15.40, Sebastiaan Couwenberg wrote: >> The build logs shows it downloading both the old and new libnetcdf: >> >> libnetcdf15 1:4.7.3-1 >> libnetcdf13 1:4.6.2-1+b1 > > But none of them is used by libnetcdf-c++4-1 The buildlog for netcdf-cxx shows the missing nc_* symbols as well: dpkg-shlibdeps: warning: symbol nc_get_vara_longlong used by debian/libnetcdf-c++4-1/usr/lib/x86_64-linux-gnu/libnetcdf_c++4.so.1.1.0 found in none of the libraries This is caused by -lnetcdf being included in LDFLAGS only, which doesn't result in libnetcdf.so.15 being included in the NEEDED section of the library. This is fixed by adding -lnetcdf to CXXFLAGS. I've forwarded the issue upstream and added DEB_CXXFLAGS_MAINT_APPEND to d/rules to fix the package for now. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Processed: Re: Bug#949828: libnetcdf-c++4-1: underlinked libnetcdf_c++4.so.1: undefined symbol: nc_*
Processing control commands: > tags -1 upstream pending Bug #949828 [libnetcdf-c++4-1] libnetcdf-c++4-1: underlinked libnetcdf_c++4.so.1: undefined symbol: nc_* Added tag(s) pending and upstream. > forwarded -1 https://github.com/Unidata/netcdf-cxx4/issues/86 Bug #949828 [libnetcdf-c++4-1] libnetcdf-c++4-1: underlinked libnetcdf_c++4.so.1: undefined symbol: nc_* Set Bug forwarded-to-address to 'https://github.com/Unidata/netcdf-cxx4/issues/86'. -- 949828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949828: libnetcdf-c++4-1: underlinked libnetcdf_c++4.so.1: undefined symbol: nc_*
Control: tag -1 - moreinfo
On 25/01/2020 15.40, Sebastiaan Couwenberg wrote:
> The build logs shows it downloading both the old and new libnetcdf:
>
> libnetcdf15 1:4.7.3-1
> libnetcdf13 1:4.6.2-1+b1
But none of them is used by libnetcdf-c++4-1
> Since we're currently transitioning to the new netcdf, I think this is
> just bad timing. Rebuild python-escript once the netcdf transition is
> further along, i.e. when none of the transitive build dependencies pull
> in the old netcdf.
I thought so as well, but a well designed transition should not result
in missing symbols, therefore I looked deeper.
> The build logs shows it using:
>
> libnetcdf-c++4 4.2-11+b1, has been rebuild for the transition
> libnetcdf-c++4-1 4.3.1-1, has not been rebuild for the transition
Try linking something against libnetcdf_c++4.so.1 only:
(needs only build-essential + libnetcdf-c++4-1)
$ echo 'int main() {}' > x.c
$ gcc x.c -Wl,--no-as-needed /usr/lib/x86_64-linux-gnu/libnetcdf_c++4.so.1
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libnetcdf_c++4.so.1: undefined reference
to `nc_get_var1_ulonglong'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libnetcdf_c++4.so.1: undefined reference
to `nc_get_att_uint'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libnetcdf_c++4.so.1: undefined reference
to `nc_def_var_fill'
...
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libnetcdf_c++4.so.1: undefined reference
to `nc_inq_var_endian'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libnetcdf_c++4.so.1: undefined reference
to `nc_get_var_ulonglong'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libnetcdf_c++4.so.1: undefined reference
to `nc_inq_user_type'
collect2: error: ld returned 1 exit status
Andreas
Processed: Re: Bug#949828: libnetcdf-c++4-1: underlinked libnetcdf_c++4.so.1: undefined symbol: nc_*
Processing control commands: > tag -1 - moreinfo Bug #949828 [libnetcdf-c++4-1] libnetcdf-c++4-1: underlinked libnetcdf_c++4.so.1: undefined symbol: nc_* Removed tag(s) moreinfo. -- 949828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#948378: transition: boost-python
Processing control commands: > block -1 with 949828 949829 Bug #948378 [release.debian.org] transition: boost-python 948378 was not blocked by any bugs. 948378 was not blocking any bugs. Added blocking bug(s) of 948378: 949829 and 949828 -- 948378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948378 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#949828: libnetcdf-c++4-1: underlinked libnetcdf_c++4.so.1: undefined symbol: nc_*
Processing control commands: > tags -1 moreinfo Bug #949828 [libnetcdf-c++4-1] libnetcdf-c++4-1: underlinked libnetcdf_c++4.so.1: undefined symbol: nc_* Added tag(s) moreinfo. -- 949828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949828: libnetcdf-c++4-1: underlinked libnetcdf_c++4.so.1: undefined symbol: nc_*
Control: tags -1 moreinfo On 1/25/20 3:19 PM, Andreas Beckmann wrote: > python-escript FTBFS during a binNMU with "Rebuild to pick up versioned libboost*-pyXY" apparently. > Import error for esys.weipa /usr/lib/x86_64-linux-gnu/libnetcdf_c++4.so.1: > undefined symbol: nc_get_var1_ulonglong > > https://buildd.debian.org/status/fetch.php?pkg=python-escript=amd64=5.4-4%2Bb1=1579900228=0 The build logs shows it downloading both the old and new libnetcdf: libnetcdf15 1:4.7.3-1 libnetcdf13 1:4.6.2-1+b1 Since we're currently transitioning to the new netcdf, I think this is just bad timing. Rebuild python-escript once the netcdf transition is further along, i.e. when none of the transitive build dependencies pull in the old netcdf. The build logs shows it using: libnetcdf-c++4 4.2-11+b1, has been rebuild for the transition libnetcdf-c++4-1 4.3.1-1, has not been rebuild for the transition Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#949829: pythonmagick: FTBFS against current libboost-python
Source: pythonmagick Version: 0.9.19-5 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, pythonmagick FTBFS against the current version of libboost-python: https://buildd.debian.org/status/package.php?p=pythonmagick make[2]: Entering directory '/<>/.pybuild/cpython3_3.8_pythonmagick/build' /bin/bash ./libtool --tag=CXX --mode=link g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -DBOOST_PYTHON_DYNAMIC_LIB -I/usr/include/python3.8 -avoid-version -module -L/usr/lib/x86_64-linux-gnu -Wl,-z,relro -Wl,-z,now -o _PythonMagick.la -rpath /usr/lib/python3.8/site-packages/PythonMagick pythonmagick_src/libpymagick.la helpers_src/libhelper.la -L/usr/lib/x86_64-linux-gnu -l-lboost_python3-py37 -lMagick++-6.Q16 -lMagickWand-6.Q16 -lMagickCore-6.Q16 libtool: link: g++ -fPIC -DPIC -shared -nostdlib /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/crti.o /usr/lib/gcc/x86_64-linux-gnu/9/crtbeginS.o -Wl,--whole-archive pythonmagick_src/.libs/libpymagick.a helpers_src/.libs/libhelper.a -Wl,--no-whole-archive -L/usr/lib/x86_64-linux-gnu -l-lboost_python3-py37 /usr/lib/x86_64-linux-gnu/libMagick++-6.Q16.so /usr/lib/x86_64-linux-gnu/libMagickWand-6.Q16.so /usr/lib/x86_64-linux-gnu/libMagickCore-6.Q16.so -L/usr/lib/gcc/x86_64-linux-gnu/9 -L/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu -L/usr/lib/gcc/x86_64-linux-gnu/9/../../../../lib -L/lib/x86_64-linux-gnu -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/9/../../.. -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/x86_64-linux-gnu/9/crtendS.o /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/crtn.o -g -O2 -fstack-protector-strong -Wl,-z -Wl,relro -Wl,-z -Wl,now -fopenmp -pthread -Wl,-soname -Wl,_PythonMagick.so -o .libs/_PythonMagick.so /usr/bin/ld: cannot find -l-lboost_python3-py37 collect2: error: ld returned 1 exit status make[2]: *** [Makefile:554: _PythonMagick.la] Error 1 make[2]: Leaving directory '/<>/.pybuild/cpython3_3.8_pythonmagick/build' There is as extra -l and it is trying to link against python3.7 while building for python3.8 The most recent boost1.67 update started generating additional dependencies on the virtual packages libboost-python1.67.0-pyXY, but I doubt that is related to this bug. Andreas
Bug#949828: libnetcdf-c++4-1: underlinked libnetcdf_c++4.so.1: undefined symbol: nc_*
Package: libnetcdf-c++4-1 Version: 4.3.1-1 Severity: serious Control: affects -1 + src:python-escript Hi, python-escript FTBFS during a binNMU with Import error for esys.weipa /usr/lib/x86_64-linux-gnu/libnetcdf_c++4.so.1: undefined symbol: nc_get_var1_ulonglong https://buildd.debian.org/status/fetch.php?pkg=python-escript=amd64=5.4-4%2Bb1=1579900228=0 libnetcdf_c++4.so.1 uses a bunch of nc_* symbols, but is not linked against any netcdf library: ldd /usr/lib/x86_64-linux-gnu/libnetcdf_c++4.so.1 linux-vdso.so.1 (0x7ffe6adc1000) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x7fed279c3000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fed27803000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7fed277e9000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fed276a4000) /lib64/ld-linux-x86-64.so.2 (0x7fed27bf5000) Andreas
Processed: libnetcdf-c++4-1: underlinked libnetcdf_c++4.so.1: undefined symbol: nc_*
Processing control commands: > affects -1 + src:python-escript Bug #949828 [libnetcdf-c++4-1] libnetcdf-c++4-1: underlinked libnetcdf_c++4.so.1: undefined symbol: nc_* Added indication that 949828 affects src:python-escript -- 949828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 947555
Processing commands for cont...@bugs.debian.org: > tags 947555 + pending Bug #947555 [src:btanks] FTBFS with scons 3.1.2-1 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 947555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947555 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#948876: kodi: FTBFS: something segfaults
Dear Maintainer, a short addition. I got some help that AddressSanitizer and Valgrind could be squeezed to delay returning previously free'd addresses from the allocator. Then both tools point to the mentioned first allocation directly. Kind regards, Bernhard AddressSanitizer: export ASAN_OPTIONS=quarantine_size_mb=1000 Valgrind: --freelist-vol=100 Result with unmodified Debian binaries: valgrind --tool=memcheck --track-origins=yes --num-callers=100 --freelist-vol=100 fontforge -script /home/benutzer/source/kodi/try1/kodi-17.6+dfsg1/debian/mergefonts.ff /usr/share/fonts/truetype/droid/DroidSansFallbackFull.ttf /usr/share/fonts/truetype/dejavu/DejaVuSans.ttf /home/benutzer/source/kodi/try1/kodi-17.6+dfsg1/media/Fonts/arial.ttf The glyph named Omega is mapped to U+03A9. But its name indicates it should be mapped to U+2126. ==74312== Invalid read of size 8 ==74312==at 0x55F6B69: gv_len (tottfgpos.c:3838) ==74312==by 0x5601DC9: ttf_math_dump_glyphvariant (tottfgpos.c:3979) ==74312==by 0x5601DC9: otf_dump_math (tottfgpos.c:4139) ==74312==by 0x56134C9: initATTables (tottf.c:5316) ==74312==by 0x5615006: initTables (tottf.c:5792) ==74312==by 0x561552A: _WriteTTFFont (tottf.c:6143) ==74312==by 0x5615A49: WriteTTFFont (tottf.c:6171) ==74312==by 0x54F5413: _DoSave (savefont.c:845) ==74312==by 0x54F7DCF: GenerateScript (savefont.c:1269) ==74312==by 0x55103FB: bGenerate (scripting.c:2061) ==74312==by 0x5512F0A: docall (scripting.c:9632) ==74312==by 0x551359D: handlename (scripting.c:9745) ==74312==by 0x55147B2: term (scripting.c:9983) ==74312==by 0x5514B37: mul (scripting.c:10128) ==74312==by 0x5514D4D: add (scripting.c:10174) ==74312==by 0x55150B8: comp (scripting.c:10249) ==74312==by 0x5515340: _and (scripting.c:10293) ==74312==by 0x55154E2: _or (scripting.c:10325) ==74312==by 0x55154E2: assign (scripting.c:10358) ==74312==by 0x55122FC: expr (scripting.c:10436) ==74312==by 0x55122FC: ff_statement (scripting.c:10649) ==74312==by 0x5516110: ProcessNativeScript (scripting.c:10796) ==74312==by 0x5516744: _CheckIsScript (scripting.c:10890) ==74312==by 0x5516744: CheckIsScript (scripting.c:10927) ==74312==by 0x4A165B8: fontforge_main (startui.c:1099) ==74312==by 0x4C13BBA: (below main) (libc-start.c:308) ==74312== Address 0x8f6e3600 is 0 bytes inside a block of size 40 free'd ==74312==at 0x48379AB: free (vg_replace_malloc.c:540) ==74312==by 0x55C7B19: SplineCharFreeContents (splineutil.c:5963) ==74312==by 0x55C7B7D: SplineCharFree (splineutil.c:5974) ==74312==by 0x55C7B7D: SplineCharFree (splineutil.c:5970) ==74312==by 0x55CA66D: SplineFontFree (splineutil.c:6535) ==74312==by 0x55CA66D: SplineFontFree (splineutil.c:6491) ==74312==by 0x542E147: _MergeFont (fvfonts.c:1161) ==74312==by 0x542E147: __MergeFont (fvfonts.c:1179) ==74312==by 0x542E147: MergeFont (fvfonts.c:1261) ==74312==by 0x5512F0A: docall (scripting.c:9632) ==74312==by 0x551359D: handlename (scripting.c:9745) ==74312==by 0x55147B2: term (scripting.c:9983) ==74312==by 0x5514B37: mul (scripting.c:10128) ==74312==by 0x5514D4D: add (scripting.c:10174) ==74312==by 0x55150B8: comp (scripting.c:10249) ==74312==by 0x5515340: _and (scripting.c:10293) ==74312==by 0x55154E2: _or (scripting.c:10325) ==74312==by 0x55154E2: assign (scripting.c:10358) ==74312==by 0x55122FC: expr (scripting.c:10436) ==74312==by 0x55122FC: ff_statement (scripting.c:10649) ==74312==by 0x5516110: ProcessNativeScript (scripting.c:10796) ==74312==by 0x5516744: _CheckIsScript (scripting.c:10890) ==74312==by 0x5516744: CheckIsScript (scripting.c:10927) ==74312==by 0x4A165B8: fontforge_main (startui.c:1099) ==74312==by 0x4C13BBA: (below main) (libc-start.c:308) ==74312== Block was alloc'd at ==74312==at 0x4838B65: calloc (vg_replace_malloc.c:762) ==74312==by 0x5486A1B: ttf_math_read_gvtable (parsettfatt.c:5317) ==74312==by 0x5491113: ttf_math_read_variants (parsettfatt.c:5473) ==74312==by 0x5491113: _otf_read_math (parsettfatt.c:5515) ==74312==by 0x5491113: _otf_read_math (parsettfatt.c:5493) ==74312==by 0x54A87D4: readttf (parsettf.c:5673) ==74312==by 0x54A87D4: _SFReadTTF (parsettf.c:6327) ==74312==by 0x556808E: _ReadSplineFont (splinefont.c:1141) ==74312==by 0x5569238: LoadSplineFont (splinefont.c:1379) ==74312==by 0x550B0E2: bMergeFonts (scripting.c:5600) ==74312==by 0x5512F0A: docall (scripting.c:9632) ==74312==by 0x551359D: handlename (scripting.c:9745) ==74312==by 0x55147B2: term (scripting.c:9983) ==74312==by 0x5514B37: mul (scripting.c:10128) ==74312==by 0x5514D4D: add (scripting.c:10174) ==74312==by 0x55150B8: comp (scripting.c:10249) ==74312==by 0x5515340: _and (scripting.c:10293) ==74312==by 0x55154E2: _or (scripting.c:10325) ==74312==by 0x55154E2: assign (scripting.c:10358)
Bug#949778: marked as done (ruby-oembed: autopkgtest needs update for new version of gem2deb: missing skippable restriction)
Your message dated Sat, 25 Jan 2020 13:36:33 + with message-id and subject line Bug#949778: fixed in ruby-oembed 0.12.0-3 has caused the Debian Bug report #949778, regarding ruby-oembed: autopkgtest needs update for new version of gem2deb: missing skippable restriction 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.) -- 949778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949778 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-oembed Version: 0.12.0-2 Severity: serious X-Debbugs-CC: debian...@lists.debian.org, gem2...@packages.debian.org Tags: sid bullseye User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:gem2deb Dear maintainers, With a recent upload of gem2deb the autopkgtest of ruby-oembed fails in testing when that autopkgtest is run with the binary packages of gem2deb from unstable. It passes when run with only packages from testing. In tabular form: passfail gem2debfrom testing1.0.3 ruby-oembedfrom testing0.12.0-2 all others from testingfrom testing I copied some of the output at the bottom of this report. The cause of this is that gem2deb started to exit with code 77 to indicate that there is no test to run. This is meant to be used in conjunction with the skippable restriction, to avoid giving the wrong information to the migration software. Please add the skippable restriction to your package, or better, add a real test. Currently this regression is blocking the migration of gem2deb to testing [1]. Of course, gem2deb shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in gem2deb was intended and your package needs to update to the new situation. If needed, please change the bug's severity. 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=gem2deb https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-oembed/4079292/log.gz autopkgtest [21:12:45]: test command1: gem2deb-test-runner --autopkgtest 2>&1 autopkgtest [21:12:45]: test command1: [--- ┌──┐ │ Run tests for ruby2.5: no test suite! │ └──┘ autopkgtest [21:12:45]: test command1: ---] autopkgtest [21:12:46]: test command1: - - - - - - - - - - results - - - - - - - - - - command1 FAIL non-zero exit status 77 signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: ruby-oembed Source-Version: 0.12.0-3 We believe that the bug you reported is fixed in the latest version of ruby-oembed, 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 949...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antonio Terceiro (supplier of updated ruby-oembed 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, 25 Jan 2020 10:20:41 -0300 Source: ruby-oembed Architecture: source Version: 0.12.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Antonio Terceiro Closes: 949778 Changes: ruby-oembed (0.12.0-3) unstable; urgency=medium . [ Utkarsh Gupta ] * Add salsa-ci.yml . [ Antonio Terceiro ] * Drop debian/tests/control and let autodep8 do its job (Closes: #949778) - add Testsuite: autopkgtest-pkg-ruby Checksums-Sha1: 6bb65b7fc669fdaa3d8c47824550d4785c1381dd 2023 ruby-oembed_0.12.0-3.dsc 7adb5fc18d93ab959af61b3e8230dd60a8783ada 2660 ruby-oembed_0.12.0-3.debian.tar.xz 8ae5e877ffe0fda45d2b9ed89c3bf1823bb8e847 12662 ruby-oembed_0.12.0-3_source.buildinfo Checksums-Sha256: b3846db05c6db796ebac411a87b247e256ec497f0d6869e7332b380f40d8ad01 2023 ruby-oembed_0.12.0-3.dsc 63c29dd2217e73058eb522bf4922a4f0f6673cd81288341b7b7697a98043fd8e 2660 ruby-oembed_0.12.0-3.debian.tar.xz
Bug#949824: schleuder: tests fail with ruby-sqlite 1.4.2-1
Source: schleuder Severity: serious Justification: FTBFS Hi, I'm about upload ruby-sqlite3 1.4.2-1, and schleuder now fails its tests on the dependency resolution step. ┌──┐ │ Checking Rubygems dependency resolution on ruby2.5 │ └──┘ Invalid gemspec in [schleuder.gemspec]: No such file or directory - git GEM_PATH= ruby2.5 -e gem\ \"schleuder\" /usr/lib/ruby/2.5.0/rubygems/dependency.rb:312:in `to_specs': Could not find 'sqlite3' (~> 1.3.6) - did find: [sqlite3-1.4.2] (Gem::MissingSpecVersionError) Checked in 'GEM_PATH=/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/ruby/gems/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0', execute `gem env` for more information from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1469:in `block in activate_dependencies' from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1458:in `each' from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1458:in `activate_dependencies' from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1440:in `activate' from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_gem.rb:68:in `block in gem' from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_gem.rb:67:in `synchronize' from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_gem.rb:67:in `gem' from -e:1:in `' I tried hacking it locally, and just changing ~> to >= makes it work, and all the tests pass. Please consider making the dependency check less strict. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-3-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_CRAP Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:pt:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled signature.asc Description: PGP signature
Bug#943991: marked as done (behave: failing tests with python3.8)
Your message dated Sat, 25 Jan 2020 13:04:36 + with message-id and subject line Bug#943991: fixed in behave 1.2.6-1 has caused the Debian Bug report #943991, regarding behave: failing tests with python3.8 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.) -- 943991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943991 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: behave Version: 1.2.5-3 Severity: important Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu focal ubuntu-patch Hi Vincent, The behave package fails to build from source in Ubuntu focal, because Ubuntu has begun the transition to python3.8 and behave is not source-compatible with python3.8: [...] ERROR: test_loads_hooks_and_step_definitions (test.test_runner.TestRunWithPaths) -- Traceback (most recent call last): File "/<>/.pybuild/cpython3_3.8_behave/build/test/test_runner.py", line 597, in test_loads_hooks_and_step_definitions self.runner.run_with_paths() File "/<>/.pybuild/cpython3_3.8_behave/build/behave/runner.py", line 693, in run_with_paths return self.run_model() File "/<>/.pybuild/cpython3_3.8_behave/build/behave/runner.py", line 470, in run_model self.setup_capture() File "/<>/.pybuild/cpython3_3.8_behave/build/behave/runner.py", line 424, in setup_capture self.log_capture = LoggingCapture(self.config) File "/<>/.pybuild/cpython3_3.8_behave/build/behave/log_capture.py", line 74, in __init__ fmt = logging.Formatter(fmt, datefmt) File "/usr/lib/python3.8/logging/__init__.py", line 576, in __init__ self._style.validate() File "/usr/lib/python3.8/logging/__init__.py", line 428, in validate if not self.validation_pattern.search(self._fmt): TypeError: expected string or bytes-like object [...] (https://launchpad.net/ubuntu/+source/behave/1.2.5-3/+build/17964504) Debian has not yet started the transition to python3.8 - the version of python3-defaults that adds python3.8 as supported is currently in experimental - but this will eventually become a serious bug in Debian as well once that transition begins. For the moment I have worked around the failure in Ubuntu by changing the packaging to test only against the current version of python3 and not against all supported versions, but this is a very short-term fix given that python3.8 will become the default in the next 6 months. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org diff -Nru behave-1.2.5/debian/control behave-1.2.5/debian/control --- behave-1.2.5/debian/control 2019-09-13 05:45:20.0 -0700 +++ behave-1.2.5/debian/control 2019-11-01 22:03:19.0 -0700 @@ -5,7 +5,7 @@ Uploaders: Debian Python Modules Team Build-Depends: debhelper-compat (= 12), dh-python, - python3-all, + python3, python3-hamcrest, python3-mock, python3-nose, --- End Message --- --- Begin Message --- Source: behave Source-Version: 1.2.6-1 We believe that the bug you reported is fixed in the latest version of behave, 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. Christoph Berg (supplier of updated behave 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, 25 Jan 2020 13:59:42 +0100 Source: behave Architecture: source Version: 1.2.6-1 Distribution: unstable Urgency: medium Maintainer: Vincent Bernat Changed-By: Christoph Berg Closes: 943991 Changes: behave (1.2.6-1) unstable; urgency=medium . * Team upload. * New upstream relesae. . [ Ondřej Nový ] * Bump Standards-Version to 4.4.1. . [ Michael Banck ] * debian/patches/0001-docs-disable-use-of-sphincontrib.cheeseshop.patch: Removed, no longer
Bug#946728: marked as done (golang-github-kyokomi-emoji breaks hugo autopkgtest: got "I ❤ Hugo" expected "I ❤️ Hugo")
Your message dated Sat, 25 Jan 2020 11:49:52 + with message-id and subject line Bug#946728: fixed in hugo 0.59.1-1.1 has caused the Debian Bug report #946728, regarding golang-github-kyokomi-emoji breaks hugo autopkgtest: got "I ❤ Hugo" expected "I ❤️ Hugo" 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.) -- 946728: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946728 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-kyokomi-emoji, hugo Control: found -1 golang-github-kyokomi-emoji/2.1.0-1 Control: found -1 hugo/0.58.3-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainers, With a recent upload of golang-github-kyokomi-emoji the autopkgtest of hugo fails in testing when that autopkgtest is run with the binary packages of golang-github-kyokomi-emoji from unstable. It passes when run with only packages from testing. In tabular form: passfail golang-github-kyokomi-emoji from testing2.1.0-1 hugo from testing0.58.3-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 of golang-github-kyokomi-emoji to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? 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=golang-github-kyokomi-emoji https://ci.debian.net/data/autopkgtest/testing/amd64/h/hugo/3658315/log.gz --- PASS: TestInsertIsZeroFunc (0.02s) ERROR 2019/12/13 20:32:33 failed. --- FAIL: TestTemplateFuncsExamples (1.43s) template_funcs_test.go:133: transform[0]: got "I ❤ Hugo" expected "I ❤️ Hugo" FAIL FAILgithub.com/gohugoio/hugo/tpl/tplimpl1.494s ? github.com/gohugoio/hugo/tpl/tplimpl/embedded [no test files] ? github.com/gohugoio/hugo/tpl/tplimpl/embedded/generate [no test files] [...] --- FAIL: TestEmojify (0.01s) quicktest.go:306: error: values are not equal got: "I ❤ Hugo" want: "I ❤️ Hugo" stack: /tmp/autopkgtest-lxc.v8t77u9s/downtmp/autopkgtest_tmp/obj-x86_64-linux-gnu/src/github.com/gohugoio/hugo/tpl/transform/transform_test.go:56 c.Assert(result, qt.Equals, test.expect) FAIL FAILgithub.com/gohugoio/hugo/tpl/transform 0.057s signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: hugo Source-Version: 0.59.1-1.1 We believe that the bug you reported is fixed in the latest version of hugo, 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 946...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated hugo package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 12 Jan 2020 20:21:11 +0200 Source: hugo Architecture: source Version: 0.59.1-1.1 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Adrian Bunk Closes: 946728 Changes: hugo (0.59.1-1.1) unstable; urgency=medium . * Non-maintainer upload. * Depend and build depend on the new version of golang-github-kyokomi-emoji-dev. (Closes: #946728) Checksums-Sha1: ef05769718e895b2529bb980be52110273f897d6 4608 hugo_0.59.1-1.1.dsc f47d9c0dabc5b891d2277dcc1297838914d66a14 1316928 hugo_0.59.1-1.1.debian.tar.xz Checksums-Sha256: 75b94b6b371b00b6f4ee28ee74f451ffa8b3c12b3f8e132ae3afdc7703a07327 4608 hugo_0.59.1-1.1.dsc c14c5ac305655fad6abb75e131897b14790df3db1b326cb628b78ff5e25eb540 1316928 hugo_0.59.1-1.1.debian.tar.xz Files: ce2282bf14e3a45cd4f09fdece4d8683 4608 web optional hugo_0.59.1-1.1.dsc 07d9f5965a0e10e5a9f8673be2703446 1316928 web optional hugo_0.59.1-1.1.debian.tar.xz -BEGIN PGP SIGNATURE-
Processed: Bug#949179 marked as pending in libayatana-appindicator
Processing control commands: > tag -1 pending Bug #949179 [src:libayatana-appindicator] libayatana-appindicator: FTBFS: pyversions not found + dh_install can't find your file Added tag(s) pending. -- 949179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949179 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949179: marked as pending in libayatana-appindicator
Control: tag -1 pending Hello, Bug #949179 in libayatana-appindicator 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/debian-ayatana-team/libayatana-appindicator/commit/49f921f9a74b9c9850c730591be165535b50f664 debian/rules: Stop using pyversions. Drop concept of Py2.x specific GTK-2 builds. (Closes: #949179). (this message was generated automatically) -- Greetings https://bugs.debian.org/949179
Processed: src:deal.ii: FTBFS with tbb 2020.0-2
Processing commands for cont...@bugs.debian.org: > tags 949544 + pending Bug #949544 [src:deal.ii] src:deal.ii: FTBFS with tbb 2020.0-2 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 949544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949544 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#949472 marked as pending in python-pex
Processing control commands: > tag -1 pending Bug #949472 [src:python-pex] python-pex's autopkg tests are failing Added tag(s) pending. -- 949472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949472 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949472: marked as pending in python-pex
Control: tag -1 pending Hello, Bug #949472 in python-pex 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/python-team/modules/python-pex/commit/3c64dac8ff68ba82e4fcf2cd37e70341590da7b5 Fix autopkg test (Closes: #949472). Return correct value on d/test/testsuite (this message was generated automatically) -- Greetings https://bugs.debian.org/949472
Bug#948502: marked as done (presage uses python instead of python2 in the build)
Your message dated Sat, 25 Jan 2020 10:04:26 + with message-id and subject line Bug#948502: fixed in presage 0.9.1-2.2 has caused the Debian Bug report #948502, regarding presage uses python instead of python2 in the build 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.) -- 948502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948502 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:presage Version: 0.9.1-2.1 Severity: serious Tags: sid bullseye patch presage uses python instead of python2 in the build. patch at http://launchpadlibrarian.net/459856307/presage_0.9.1-2.1ubuntu6_0.9.1-2.1ubuntu7.diff.gz --- End Message --- --- Begin Message --- Source: presage Source-Version: 0.9.1-2.2 We believe that the bug you reported is fixed in the latest version of presage, 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 948...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aron Xu (supplier of updated presage 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, 25 Jan 2020 09:31:19 + Source: presage Architecture: source Version: 0.9.1-2.2 Distribution: unstable Urgency: medium Maintainer: Matteo Vescovi Changed-By: Aron Xu Closes: 937321 948502 Changes: presage (0.9.1-2.2) unstable; urgency=medium . [ Aron Xu ] * Non-maintainer upload. * Use dh compat 10. . [ Scott Tabert ] * Remove Python subpackages (Closes: #937321, #948502) * Move Priority from extra to optional Checksums-Sha1: b60db31b212a49639a5c24c06f5750805ebc15ff 2216 presage_0.9.1-2.2.dsc ad04c5af67ae6023fe2358992952b0527397258e 7908 presage_0.9.1-2.2.debian.tar.xz bc340d7ca65142ca828814e878fbd62c3168bb91 5154 presage_0.9.1-2.2_source.buildinfo Checksums-Sha256: ab5a50e103f525a8f30d7338feb21b0c08f87da8e0019f8f615c5ede62cbfc66 2216 presage_0.9.1-2.2.dsc 554caf1d15d52ea02ca738abbee8a91000dbd13187663c1993f7907f66ef77b9 7908 presage_0.9.1-2.2.debian.tar.xz 42afbb59ca72d6187b638b981d1fa49b7de2bb0eead6f32420f7ec86bfd21cd9 5154 presage_0.9.1-2.2_source.buildinfo Files: 0c6e385772f8c6d8c5769e4fe598cfdd 2216 devel optional presage_0.9.1-2.2.dsc 712857b303e0f8f1d6487c1f9aaf3132 7908 devel optional presage_0.9.1-2.2.debian.tar.xz a7e09bb8a68e503ecbd0b542029241c9 5154 devel optional presage_0.9.1-2.2_source.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEXraik9KLDk+VcqtJ3oyCGyc+2gsFAl4sDaMACgkQ3oyCGyc+ 2gtXZgf+MYYLHc3YnErRWpmEAnug0lrq6BFVMnkRGq3J+ZquiXxI7BO7H+N/wSUB rkCUJZw8xyCj0BtuMBUsMRjy4F58+DJN7VYAxn+Qp5jb47uLJVd8q7P6xxZmdoQE nkaCbSUkdE6K3joAfX1PsFWPqDtM097zStEdExZjEGjIhHLZM3XtWBXUOExfITLT vojCPl6ueKSN5yfRwXVNmjWCzebKciWT3RPDppS/HU/V8nQV2i2xlLsUKC13D0v3 uMmDe758t/CwLBtUssZqlRWiVBDJErS/8JsuhupmF9ooXWIxoeaXBSOpXMjy6zwM a3UDB9sgSPY525sgB339Ot2tBDOlWw== =hDpo -END PGP SIGNATURE End Message ---
Bug#937321: marked as done (presage: Python2 removal in sid/bullseye)
Your message dated Sat, 25 Jan 2020 10:04:26 + with message-id and subject line Bug#937321: fixed in presage 0.9.1-2.2 has caused the Debian Bug report #937321, regarding presage: 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.) -- 937321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937321 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:presage Version: 0.9.1-2.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:presage 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: presage Source-Version: 0.9.1-2.2 We believe that the bug you reported is fixed in the latest version of presage, 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 937...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aron Xu (supplier of updated presage 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, 25 Jan 2020 09:31:19 + Source: presage Architecture: source Version: 0.9.1-2.2 Distribution: unstable Urgency: medium Maintainer: Matteo Vescovi Changed-By: Aron Xu Closes: 937321 948502 Changes: presage (0.9.1-2.2) unstable; urgency=medium . [ Aron Xu ] * Non-maintainer upload. * Use dh compat 10. . [ Scott Tabert ] * Remove Python subpackages (Closes: #937321, #948502) * Move Priority from extra to optional Checksums-Sha1: b60db31b212a49639a5c24c06f5750805ebc15ff 2216 presage_0.9.1-2.2.dsc ad04c5af67ae6023fe2358992952b0527397258e 7908 presage_0.9.1-2.2.debian.tar.xz bc340d7ca65142ca828814e878fbd62c3168bb91 5154 presage_0.9.1-2.2_source.buildinfo Checksums-Sha256: ab5a50e103f525a8f30d7338feb21b0c08f87da8e0019f8f615c5ede62cbfc66 2216 presage_0.9.1-2.2.dsc 554caf1d15d52ea02ca738abbee8a91000dbd13187663c1993f7907f66ef77b9 7908 presage_0.9.1-2.2.debian.tar.xz 42afbb59ca72d6187b638b981d1fa49b7de2bb0eead6f32420f7ec86bfd21cd9 5154
Bug#949585: mosquitto: various patches to fix Debian packaging and update to 1.6.8
I tweak 1570 to fix a build failure with musl libc
deferred/15
thanks
Gianfranco
On Fri, 24 Jan 2020 14:55:03 +0100 Gianfranco Costamagna
wrote:
> On Wed, 22 Jan 2020 13:16:05 +0100 Gianfranco Costamagna
> wrote:
> > control: tags -1 pending
> >
> > > I plan to NMU if nobody objects in the next few days!
> > >
> >
> > will go in experimental in the next 15 days if nobody objects
> >
> > (Updated debian tarball with this bug closed attached)
> >
> > G.
>
> I polished the packaging even more:
> + * Add libcares-dev dependency, to enable SRV functionality
> + * Bump std-version to 4.5.0, no changes required
> + * Simplify rules file, avoding the systemd hack in configure script
> + * Rename patches with the upstream PR number on github.
>
>
> so, I'm uploading the exp2 version on experimental in deferred queue, patch
> and debian packaging attached
>
> thanks
>
> G.
mosquitto_1.6.8-1~exp3.debian.tar.xz
Description: application/xz
diff -Nru mosquitto-1.6.8/debian/changelog mosquitto-1.6.8/debian/changelog
--- mosquitto-1.6.8/debian/changelog2020-01-24 14:19:46.0 +0100
+++ mosquitto-1.6.8/debian/changelog2020-01-25 10:47:39.0 +0100
@@ -1,3 +1,9 @@
+mosquitto (1.6.8-1~exp3) experimental; urgency=medium
+
+ * Tweak patch 1570 to fix a build failure with non-libc libraries
+
+ -- Gianfranco Costamagna Sat, 25 Jan 2020
10:47:39 +0100
+
mosquitto (1.6.8-1~exp2) experimental; urgency=medium
* Add libcares-dev dependency, to enable SRV functionality
diff -Nru mosquitto-1.6.8/debian/patches/1568.patch
mosquitto-1.6.8/debian/patches/1568.patch
--- mosquitto-1.6.8/debian/patches/1568.patch 2020-01-24 14:19:46.0
+0100
+++ mosquitto-1.6.8/debian/patches/1568.patch 2020-01-25 10:43:22.0
+0100
@@ -1,3 +1,4 @@
+Upstream-Status: Submitted [https://github.com/eclipse/mosquitto/pull/1568]
From 50bfc79cae5764a6e513b684a5eb5bef2b35c856 Mon Sep 17 00:00:00 2001
From: Gianfranco Costamagna
Date: Wed, 22 Jan 2020 12:30:25 +0100
diff -Nru mosquitto-1.6.8/debian/patches/1569.patch
mosquitto-1.6.8/debian/patches/1569.patch
--- mosquitto-1.6.8/debian/patches/1569.patch 2020-01-24 14:19:46.0
+0100
+++ mosquitto-1.6.8/debian/patches/1569.patch 2020-01-25 10:43:25.0
+0100
@@ -1,3 +1,4 @@
+Upstream-Status: Submitted [https://github.com/eclipse/mosquitto/pull/1569]
From fda932612afce2cead2fd2ca1c8ea543b2892177 Mon Sep 17 00:00:00 2001
From: Gianfranco Costamagna
Date: Wed, 22 Jan 2020 12:31:01 +0100
diff -Nru mosquitto-1.6.8/debian/patches/1570.patch
mosquitto-1.6.8/debian/patches/1570.patch
--- mosquitto-1.6.8/debian/patches/1570.patch 2020-01-24 14:19:46.0
+0100
+++ mosquitto-1.6.8/debian/patches/1570.patch 2020-01-25 10:47:33.0
+0100
@@ -1,28 +1,39 @@
-From 9a6470d31d212522a56cab94b81f99a7b6967f76 Mon Sep 17 00:00:00 2001
+Upstream-Status: Submitted [https://github.com/eclipse/mosquitto/pull/1570]
+From 775677b05190380c3736bf0dbef002ee7b9bff33 Mon Sep 17 00:00:00 2001
From: Gianfranco Costamagna
Date: Wed, 22 Jan 2020 12:29:41 +0100
Subject: [PATCH] cmake: add ADNS enable/disable dynamic support
Signed-off-by: Gianfranco Costamagna
---
- src/CMakeLists.txt | 7 +++
- 1 file changed, 7 insertions(+)
+ src/CMakeLists.txt | 8 ++--
+ 1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/src/CMakeLists.txt b/src/CMakeLists.txt
-index 7898ff5b1..11c24e2cc 100644
+index 7898ff5b1..edae76f32 100644
--- a/src/CMakeLists.txt
+++ b/src/CMakeLists.txt
-@@ -105,6 +105,13 @@ if (WITH_SYS_TREE)
+@@ -105,6 +105,9 @@ if (WITH_SYS_TREE)
add_definitions("-DWITH_SYS_TREE")
endif (WITH_SYS_TREE)
+option(WITH_ADNS
+ "Include ADNS support?" OFF)
-+if (WITH_ADNS)
-+ add_definitions("-DWITH_ADNS")
-+ set (MOSQ_LIBS ${MOSQ_LIBS} anl)
-+endif (WITH_ADNS)
+
if (CMAKE_SYSTEM_NAME STREQUAL Linux)
option(WITH_SYSTEMD
"Include systemd support?" OFF)
+@@ -137,10 +140,11 @@ set (MOSQ_LIBS ${MOSQ_LIBS} ${OPENSSL_LIBRARIES})
+ # Check for getaddrinfo_a
+ include(CheckLibraryExists)
+ check_library_exists(anl getaddrinfo_a "" HAVE_GETADDRINFO_A)
+-if (HAVE_GETADDRINFO_A)
++if (HAVE_GETADDRINFO_A AND WITH_ADNS)
++ add_definitions("-DWITH_ADNS")
+ add_definitions(-DHAVE_GETADDRINFO_A)
+ set (MOSQ_LIBS ${MOSQ_LIBS} anl)
+-endif (HAVE_GETADDRINFO_A)
++endif (HAVE_GETADDRINFO_A AND WITH_ADNS)
+
+
+ if (UNIX)
diff -Nru mosquitto-1.6.8/debian/patches/1571.patch
mosquitto-1.6.8/debian/patches/1571.patch
--- mosquitto-1.6.8/debian/patches/1571.patch 2020-01-24 14:19:46.0
+0100
+++ mosquitto-1.6.8/debian/patches/1571.patch 2020-01-25 10:43:56.0
+0100
@@ -1,3 +1,4 @@
+Upstream-Status: Submitted [https://github.com/eclipse/mosquitto/pull/1571]
From 3fe5468f1bdca1bff1d18cf43c9e338f41aa9e32 Mon Sep 17 00:00:00 2001
From: Gianfranco Costamagna
Date: Wed, 22 Jan 2020 12:39:49 +0100
Bug#937321: presage: Python2 removal in sid/bullseye
Hi, I have uploaded the NMU for removing python sub-packages, and we can wait Matteo to see how to deal with the Python porting. Also I've updated the dh compat to 10 so that the build process can proceed with more parallelism. Regards, Aron On Sat, Jan 25, 2020 at 10:33 AM Scott Talbert wrote: > > Hi Matteo, > > I don't know if you saw, but I sent you a merge request[1] to remove the > Python subpackages in presage. They don't have any rdeps and have very > low popcon so it seems reasonable to remove them now (and they can be > added back later when Python 3 support is ready). > > Let me know if you are good with this change. > > Thanks, > Scott > > [1] https://sourceforge.net/p/presage/presage-debian/merge-requests/1/ > > On Tue, 3 Dec 2019, Matteo Vescovi wrote: > > > Hi Scott, > > > > Someone approached me and volunteered to port presage to Python 3 in late > > October, but I haven't heard back since them. > > > > Let me take a look at what kind of an effort it would be to port to python > > 3: that would be my preferred option if I can find the time to do. > > > > Else, the suggestion to remove the python pieces sound like the next best > > thing, if I can't find the time to port to python 3 now, we can then later > > reintroduce the python pieces. > > > > What are the planned timelines for the python 2 removal? > > > > Cheers, > > - Matteo > > > > > > > > > > On Tuesday, 3 December 2019, 05:02:48 CET, Scott Talbert > > wrote: > > > > > > On Mon, 2 Dec 2019, Scott Talbert wrote: > > > > >> 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. > > > > > > Hi Matteo, > > > > > > Do you plan to port presage to Python 3? If not, I'll probably convert > > this > > > to an RM request as the package seems to be mostly unmaintained and is > > > blocking the removal of Python 2. > > > > Alternatively, perhaps just the Python pieces of presage can be removed, > > as those don't seem to have any rdepends? > > > > Scott > > > >
Bug#949658: Different tests for r-cran-recipes - "wrong" test prevents migration of r-cran-testthat
Hi Andreas On Fri, 24 Jan 2020 at 11:21, Andreas Tille wrote: > and I have no idea how to fix this. May be there is some unspecified > versioned Build-Depends or something like this. This is the kind of bug that autopkgtests blocking testing migration is supposed to catch. I see you uploaded r-cran-recipes 0.1.9+dfsg-2 which should migrate soon. Let's see if that improves the situation. If not, please file a new bug for r-cran-recipes and leave #949658 for r-cran-rlang. On the subject of r-cran-rlang, I notice upstream's DESCRIPTION file contains: Depends: R (>= 3.2.0) Suggests: cli, covr, crayon, magrittr, methods, pillar, rmarkdown, testthat (>= 2.3.0) This must be where the minimum version of testthat is specified, and somehow that needs to end up in debian/control or debian/tests/control. Regards Graham
Bug#949767: causes autopkgtest regression in libgpuarray
(The above debci log is misleading due to #764081; pocl also changed, and the failure goes away on using the old pocl.) It looks like this fails because it is reading the result before the computation has finished: - On a failure, the np.asarray(gr) passed to assert_allclose doesn't match cr (hence the fail), but np.asarray(gr) run manually from the debugger (i.e. later) does match cr. - Adding a time.sleep(0.1) to the test stops that test failing. - Which tests fail varies from run to run. I don't yet know if this is pocl's or libgpuarray's fault.
Bug#949703: severity of 949703 is serious, closing 949703
severity 949703 serious close 949703 thanks
Processed: tagging 893735
Processing commands for cont...@bugs.debian.org: > tags 893735 + ftbfs Bug #893735 [src:paraview] paraview FTBFS on armel/armhf: QVTKOpenGLWidget.cxx:458:3: error: 'QOpenGLFunctions_3_2_Core' was not declared in this scope Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 893735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893735 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 949703 is serious, closing 949703
Processing commands for cont...@bugs.debian.org: > severity 949703 serious Bug #949703 [src:thunderbird] thunderbird doesn' start on Sid Bug #949695 [src:thunderbird] thunderbird does not start anymore Severity set to 'serious' from 'normal' Severity set to 'serious' from 'normal' > close 949703 Bug #949703 [src:thunderbird] thunderbird doesn' start on Sid Bug #949695 [src:thunderbird] thunderbird does not start anymore Marked Bug as done Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 949695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949695 949703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949703 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
