Bug#951302: timeshift: /mnt is used programmatically
Package: timeshift Version: 19.01+ds-2 Severity: serious Dear maintainer, Please modify the timeshift program so that it does not use /mnt/timeshift or any sub-directories under /mnt. FHS 3.0 says no package allowed to access this directory directly. It is intended to use as a temporally mount point by a system administrator[1]. Please switch to /run/timeshift instead. On first run, if a user has a Btrfs root file system on an encrypted device by LUKS and choose the BTRFS option in the Setup Wizard, the program automatically creates the /mnt/timeshift/backup directory and mount there the device with the root FS. On quit, this is not rolled back. Such behavior violates the Debian Policy and potentially may cause to data loss if there is something mounted by the user on their own. [1]: https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.html#mntMountPointForATemporarilyMount mymedia@barberry:~$ LANG=C sudo timeshift-gtk First run mode (config file not found) Selected default snapshot type: BTRFS App config loaded: /etc/timeshift.json Selected default snapshot device: /dev/sdb2 /dev/dm-2 is mounted at: /mnt/timeshift/backup, options: rw,relatime,ssd,space_cache,subvolid=5,subvol=/ /dev/dm-2 is mounted at: /mnt/timeshift/backup, options: rw,relatime,ssd,space_cache,subvolid=5,subvol=/ App config saved: /etc/timeshift.json App config saved: /etc/timeshift.json mymedia@barberry:~$ sudo rm /etc/timeshift.json -- System Information: Debian Release: buster/sid APT prefers eoan-updates APT policy: (500, 'eoan-updates'), (500, 'eoan-security'), (500, 'eoan') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.0-29-generic (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE=ru (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages timeshift depends on: ii libc6 2.30-0ubuntu2 ii libcairo2 1.16.0-4 ii libgdk-pixbuf2.0-0 2.40.0+dfsg-1build1 ii libgee-0.8-20.20.2-1 ii libglib2.0-02.62.1-1 ii libgtk-3-0 3.24.12-1ubuntu1 ii libjson-glib-1.0-0 1.4.4-2 ii libvte-2.91-0 0.58.2-1ubuntu2 ii psmisc 23.2-1 ii rsync 3.1.3-6 timeshift recommends no packages. timeshift suggests no packages. -- no debconf information
Bug#922582: marked as done (FTBFS against opencv 4.0.1 (exp))
Your message dated Fri, 14 Feb 2020 05:19:08 + with message-id and subject line Bug#922582: fixed in gmic 2.4.5-1.1 has caused the Debian Bug report #922582, regarding FTBFS against opencv 4.0.1 (exp) 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.) -- 922582: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922582 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gmic Version: 2.4.5-1 Severity: important gmic's cmake file needs to be updated for Opencv4 gmic_2.4.5-1_ppc64el-2019-02-15T10:51:33Z.build.zst Description: Binary data --- End Message --- --- Begin Message --- Source: gmic Source-Version: 2.4.5-1.1 We believe that the bug you reported is fixed in the latest version of gmic, 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 922...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ying-Chun Liu (PaulLiu) (supplier of updated gmic 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, 12 Nov 2019 07:25:35 + Source: gmic Architecture: source Version: 2.4.5-1.1 Distribution: unstable Urgency: low Maintainer: Bernd Zeimetz Changed-By: Ying-Chun Liu (PaulLiu) Closes: 922582 Changes: gmic (2.4.5-1.1) unstable; urgency=low . [ Ying-Chun Liu (PaulLiu) ] * Non-maintainer upload. . [ Peter Michael Green ] * Make package build with opencv 4 (Closes: #922582) + Bump libopencv-dev build-dependency as I am not attempting to retain compatibility with older opencv versions, someone who knows the buildsystem better can do that if they wish. + Change pkg-config file for opencv from "opencv" to "opencv4". + Change/add a bunch of #include statements. Checksums-Sha1: fff47ecdbaae711e4bc11019414e00a6dea83a13 2389 gmic_2.4.5-1.1.dsc 91fd65ace24efcf00612faf5c2434d00b3049a71 18948 gmic_2.4.5-1.1.debian.tar.xz c3eba8e22645d824c82dc6fb7b7c28b94284bfb5 23664 gmic_2.4.5-1.1_source.buildinfo Checksums-Sha256: cc14f0f177fe402d18cd7628aecc416b485c834d77c55378d6eabb8abbfa69bf 2389 gmic_2.4.5-1.1.dsc a582ab70e0553a127fb37a3f4b7f0fc41f40b36579b3ed735b34760d3f31 18948 gmic_2.4.5-1.1.debian.tar.xz 878ee7aced201cc405ded526a2473eb3c658d40613b3c7f3fedd4c3780534f20 23664 gmic_2.4.5-1.1_source.buildinfo Files: 0ea518e8da08aa1f7d501830b04b4b0c 2389 graphics optional gmic_2.4.5-1.1.dsc 6af220f4b037ebc38798caf2acbfa0a6 18948 graphics optional gmic_2.4.5-1.1.debian.tar.xz 4599a1b1b6d4bd6fb66956adc8d7c456 23664 graphics optional gmic_2.4.5-1.1_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAl5GKIUTHHBhdWxsaXVA ZGViaWFuLm9yZwAKCRBEFz+hPQWIiDf/D/9o1SXGtyFmDHlAZ9MsDd71/sGWX/Sc CRmuEwz3MHA9eeDWcp83iYTG7ZQn80p4CUl/ewnU7Gdw1zSbSIc3Cb4bVjruBL9y qE2aVQKEsSKTGAT+QBIHMXlvshYiPCAQatCr0/1B5561U6sXpDhp7Y8Bu8cvlpTZ oxT2cvUGM7r4RNV/aijPRJz+Zi9KKkzhGV/TWv0LJND4Vk/SF+QJ2/+Xw16FbQH2 3XabnmDgcMli25MY1j93LJZrzMKfLnFE8xGKZhVycCxHe/wsuHbq9xrdm9lME/b+ 1AwLHJQG/GAyQRz3IqHqdsErhrTfSRPW2DksCqI8XTPMfd4qDcO6B8nAWWWvThaD dqsba8iohNPzeZE2gHgXImPxn5KIZynvykJrDHSqH2BYk6ISGNlP9IYIF8T/kJo5 3LDek1XAFhHPc3YgjfjSt4BbMqi4B3VJnxue0tFdtek493wUbp33JxMtHM6t+zHe YpB7Q7Yz0eV0weFt2sLBrOF6Wub3nDrvk0m4LG+2KNOE1NoxBcwkDiqc5lXOOnfD IhDmoJPSVFwWZhIWbirgXdfkRyIn3MGfv/D2RJTdAkm3KdtCA1mVnQcnaSnxiJKZ KYZBBJWaLqiQbYbAtJIF5MxTO9OUUa479RPGmBXlbWqJjut4Y7ymHtUj77kvwm8I sm/Zre+fX1mLRg== =kVFw -END PGP SIGNATURE End Message ---
Bug#951108: marked as done (node-opencv fails autopkg tests)
Your message dated Fri, 14 Feb 2020 02:36:46 + with message-id and subject line Bug#951108: fixed in node-opencv 6.0.0+git20190322.db093cb2-7 has caused the Debian Bug report #951108, regarding node-opencv fails autopkg 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.) -- 951108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951108 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:node-opencv Version: 6.0.0+git20190322.db093cb2-5 Severity: serious Tags: sid bullseye node-opencv fails autopkg tests: autopkgtest [21:17:08]: summary require PASS smoketestFAIL stderr: dpkg-architecture: warning: cannot determine CC system type, falling back to default (native compilation) unittest FAIL stderr: dpkg-architecture: warning: cannot determine CC system type, falling back to default (native compilation) --- End Message --- --- Begin Message --- Source: node-opencv Source-Version: 6.0.0+git20190322.db093cb2-7 We believe that the bug you reported is fixed in the latest version of node-opencv, 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 951...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ying-Chun Liu (PaulLiu) (supplier of updated node-opencv package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 14 Feb 2020 09:47:03 +0800 Source: node-opencv Architecture: source Version: 6.0.0+git20190322.db093cb2-7 Distribution: unstable Urgency: low Maintainer: Debian Javascript Maintainers Changed-By: Ying-Chun Liu (PaulLiu) Closes: 951108 Changes: node-opencv (6.0.0+git20190322.db093cb2-7) unstable; urgency=low . [ Ying-Chun Liu (PaulLiu) ] * Fix autopkgtest fail on arm64 (Closes: #951108) Checksums-Sha1: a592e7194d48b8c65839841781bde805db353cf4 2381 node-opencv_6.0.0+git20190322.db093cb2-7.dsc 2a894311494646641cd7e6ff9e05fd4f0cc6ee7b 7704 node-opencv_6.0.0+git20190322.db093cb2-7.debian.tar.xz 0a76561a8dd37b5ca61e5042f4019a0529472d92 27107 node-opencv_6.0.0+git20190322.db093cb2-7_source.buildinfo Checksums-Sha256: b6c5edaa1d409647536170c530e23fd2d9143b2aabfa1e9afc792a19228b21ca 2381 node-opencv_6.0.0+git20190322.db093cb2-7.dsc 76ec34ea4b6f668fc88498cb3cbba48b406d802ed6ae3aa3a948a9c4065b193f 7704 node-opencv_6.0.0+git20190322.db093cb2-7.debian.tar.xz aaf3db5af795683b3fd5801edec0df1bc820b4a13a1db1ba19d0469dbc9df580 27107 node-opencv_6.0.0+git20190322.db093cb2-7_source.buildinfo Files: 6a848c969e84fc1e13423dde9f03cb3c 2381 javascript optional node-opencv_6.0.0+git20190322.db093cb2-7.dsc 95ef694e3ff332c2c6eb24577875ef16 7704 javascript optional node-opencv_6.0.0+git20190322.db093cb2-7.debian.tar.xz d3e7378ba627e5996d2eb31158c2b8bb 27107 javascript optional node-opencv_6.0.0+git20190322.db093cb2-7_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAl5GAAQTHHBhdWxsaXVA ZGViaWFuLm9yZwAKCRBEFz+hPQWIiNV4D/9p7WyL84PM608OO8o4pacfEEppkGxo qgEJbEKveFnD6yALduABqjIIoK85RuTvWgrchNDS2D83D+jb6mcWSMnSkiW/bab3 ROhOcumgQ841wjtajzSEToEw/I60O+n6UUtP8FVrbvGnKSDcAjIVqXQhBLbk5mYg SRkX6zSr1hAPMZalZiQft4YsdDumxO9VKk6PW4C7EshCf42XuygHhmD/AKll73Sv lBeEJVq2ejAK2KYLOv5o45RBzRi7jACiropEse0WeXeinn8sBb2B5pkWhmonFz3W dxkHn3n8Smm8arY1jI1bPOOLRyiUAfPBzNbUmoORhJ0E7fjdH4PhpnKR7rOrgvkl CNRyfRPym5b7NAk/+1VyzQhCOjyJfJlRmSQGCmTHyUyVPjDSTc4WW2lnt4C/Hgzg JzqqJLRPihOm5PG3UqZkuEgPJBxWfMmGo2WXf7chm260h5m4kXuvy3nxk9zMHmF+ VshIgd8zTTzxDRuf8IZWqPbvw/qAwMUuxI/8dgdZZst+MVyDA0JoEtk1QI4+tNnS sU53RQs9Z7fJGiBvLeeMGi7kje51Z8rkCHjcgPu+Dgryd44Hk4uUE1nnPI+1rvJK jdG1k0nshC3jH4M1T8ro0ocGWISzISmcznOZsnLimrihqEu7wa4q0QHJrm5t3emS Pf9zAJqpLsXTEQ== =Gfdy -END PGP SIGNATURE End Message ---
Bug#936806: koji: Python2 removal in sid/bullseye
On Fri, Feb 14, 2020 at 01:30:29AM +, Holger Levsen wrote: > On Thu, Feb 13, 2020 at 08:14:11PM -0500, Sandro Tosi wrote: > > thanks! I'm gonna go ahead and file an RM bug for the following pkgs > > too: yum createrepo python-lzma yum-metadata-parser mock yum-utils > > dtc-xen deltarpm > > > > they are a closed set > > thank you for cleaning up after all of us, now that we reached containers. > (which used to be called virtualisation mainframes before... ;) > > I mean, rpm is definitly still useful to have on Debian, but yum and > friends??? They are also useful in some cases. For example if you want to use Debian-based VM to download updates for your Qubes dom0... -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? signature.asc Description: PGP signature
Bug#951108: marked as pending in node-opencv
Control: tag -1 pending Hello, Bug #951108 in node-opencv 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/js-team/node-opencv/commit/34f5092344cfc5d591ba3507d830056b3d68c814 Import Debian changes 6.0.0+git20190322.db093cb2-7 node-opencv (6.0.0+git20190322.db093cb2-7) unstable; urgency=low [ Ying-Chun Liu (PaulLiu) ] * Fix autopkgtest fail on arm64 (Closes: #951108) Signed-off-by: Ying-Chun Liu (PaulLiu) (this message was generated automatically) -- Greetings https://bugs.debian.org/951108
Processed: Bug#951108 marked as pending in node-opencv
Processing control commands: > tag -1 pending Bug #951108 [src:node-opencv] node-opencv fails autopkg tests Added tag(s) pending. -- 951108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951108 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#936806: koji: Python2 removal in sid/bullseye
On Thu, Feb 13, 2020 at 08:14:11PM -0500, Sandro Tosi wrote: > thanks! I'm gonna go ahead and file an RM bug for the following pkgs > too: yum createrepo python-lzma yum-metadata-parser mock yum-utils > dtc-xen deltarpm > > they are a closed set thank you for cleaning up after all of us, now that we reached containers. (which used to be called virtualisation mainframes before... ;) I mean, rpm is definitly still useful to have on Debian, but yum and friends??? -- cheers, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C There are no jobs on a dead planet. signature.asc Description: PGP signature
Bug#936806: koji: Python2 removal in sid/bullseye
On Sat, Feb 8, 2020 at 1:51 PM Moritz Mühlenhoff wrote: > > On Thu, Jan 30, 2020 at 01:36:33AM -0500, Sandro Tosi wrote: > > > > koji is keeping createrepo in the archive, which keeps python-lzma in > > > > the archive. > > > > > > there's also mock, yum, rpm, deltarpm and yum-metadata-parser affected by > > > this. > > > > yep i came across all of them starting from python-lzma -- do you know > > what's the status of the "RedHat infrastructure" in debian? many (if > > not all) of those tools are relatively old, not maintained (or just in > > life support mode) and most of all, python2 with no port to python3 > > available > > > > > > upgrading koji will help getting rid of some old python2 packages. > > > > > > dropping it, at least for now, seems to be the best way foreward here :/ > > > > Allright then, i'll just wait a week for allowing people to comment > > and then i'll file for koji removal. > > Since there were no further objections I've just filed a removal bug. thanks! I'm gonna go ahead and file an RM bug for the following pkgs too: yum createrepo python-lzma yum-metadata-parser mock yum-utils dtc-xen deltarpm they are a closed set (no external dependencies outside that set, tested via `dak rm -Rn list_of_pkgs`) of obsolete "redhat-related", python2, packages. Regards, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Bug#938737: u1db: Python2 removal in sid/bullseye
Moritz Mühlenhoff writes: > On Fri, Aug 30, 2019 at 07:57:06AM +, Matthias Klose wrote: >> Package: src:u1db >> Version: 13.10-6.4 >> 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. > > Hi Micah, > per Wikipedia the Ubuntu One cloud storage has been shut down many years > ago, should this simply be removed? We were not using it for Ubuntu One cloud storage, but instead as its more generic use case as "a cross-platform, cross-device, syncable database API", which we modified to have client-side encrypted database replicas and documents. However, it is not being used any longer, and should simply be removed. -- micah
Bug#951225: marked as done (schleuder: autopkgtest regression: Could not find 'sqlite3' (~> 1.4) - did find: [sqlite3-1.3.13])
Your message dated Thu, 13 Feb 2020 23:21:05 + with message-id and subject line Bug#951225: fixed in schleuder 3.4.1-4 has caused the Debian Bug report #951225, regarding schleuder: autopkgtest regression: Could not find 'sqlite3' (~> 1.4) - did find: [sqlite3-1.3.13] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 951225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951225 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: schleuder Version: 3.4.1-3 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainers, With a recent upload of schleuder the autopkgtest of schleuder fails in testing when that autopkgtest is run with the binary packages of schleuder from unstable. It passes when run with only packages from testing (it passes when run in unstable). In tabular form: passfail schleuder from testing3.4.1-3 all others from testingfrom testing I copied some of the output at the bottom of this report. I guess there is a versioned (test) dependency missing somewhere. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=schleuder https://ci.debian.net/data/autopkgtest/testing/amd64/s/schleuder/4265884/log.gz autopkgtest [10:20:11]: test upstream-tests: [--- ┌──┐ │ 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.4) - did find: [sqlite3-1.3.13] (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 `' signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: schleuder Source-Version: 3.4.1-4 We believe that the bug you reported is fixed in the latest version of schleuder, 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 951...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Georg Faerber (supplier of updated schleuder 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: Thu, 13 Feb 2020 22:59:08 + Source: schleuder Architecture: source Version: 3.4.1-4 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Georg Faerber Closes: 951225 Changes: schleuder (3.4.1-4) unstable; urgency=medium . * debian/*: - Run wrap-and-sort -abt. * debian/patches: - Relax dependency on sqlite3 in gemspec. This fixes a regression introduced in the previous release, 3.4.1-3. (Closes: #951225) - Refresh existing patches, accordingly. Checksums-Sha1: 3de5a0875a06fdd73499d147e33357212d833c16 1746 schleuder_3.4.1-4.dsc c30454f79b4939344c20a8d66b53e682d1ede99f 27856
Bug#951294: parsec47: exits with an error immediately after starting
Package: parsec47 Version: 0.2.dfsg1-9 Severity: grave Justification: renders package unusable The window opens and immediately closes. From the command line: $ parsec47 parsec47: symbol lookup error: parsec47: undefined symbol: _D3std5stdio24__T10makeGlobalS6stderrZ10makeGlobalFNbNcNdNiZS3std5stdio4File -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages parsec47 depends on: ii libbulletml0v5 0.0.6-7 ii libc62.29-10 ii libgcc-s1 [libgcc1] 10-20200211-1 ii libgcc1 1:10-20200211-1 ii libgl1 1.3.0-7 ii libgphobos76 9.2.1-28 ii libsdl-mixer1.2 1.2.12-16+b1 ii libsdl1.2debian 1.2.15+dfsg2-5 ii parsec47-data0.2.dfsg1-9 parsec47 recommends no packages. parsec47 suggests no packages. -- no debconf information
Bug#951225: marked as pending in schleuder
Control: tag -1 pending Hello, Bug #951225 in schleuder 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/ruby-team/schleuder/commit/033760b58aa9d2e8f6121fa5609a393e308c5aa4 debian/patches: Relax dependency on sqlite3 in gemspec Closes: #951225 (this message was generated automatically) -- Greetings https://bugs.debian.org/951225
Processed: Bug#951225 marked as pending in schleuder
Processing control commands: > tag -1 pending Bug #951225 [src:schleuder] schleuder: autopkgtest regression: Could not find 'sqlite3' (~> 1.4) - did find: [sqlite3-1.3.13] Added tag(s) pending. -- 951225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951225 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#948224: pillow: CVE-2020-5310 CVE-2020-5311 CVE-2020-5312 CVE-2020-5313
FWIW I'm fairly convinced that the first vulnerable version for CVE-2020-5310 is 6.0.0, which is the first release that included https://github.com/python-pillow/Pillow/commit/e91b851fdc1c914419543f485bdbaa010790719f which introduced the overflow when switching away from the safer TIFFTileSize & TIFFStripSize in the critical lines. So you can probably mark 5.4.1 as safe for CVE-2020-5310 robert.
Bug#951016: marked as done (strongswan FTBFS: missing build-depends libiptc-dev)
Your message dated Thu, 13 Feb 2020 22:21:17 +
with message-id
and subject line Bug#951016: fixed in strongswan 5.8.2-2
has caused the Debian Bug report #951016,
regarding strongswan FTBFS: missing build-depends libiptc-dev
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
951016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951016
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: strongswan
Version: 5.8.2-1
Severity: serious
Tags: ftbfs
strongswan fails to build from source in unstable, because it misses a
build dependency on libiptc-dev. The library was formerly pulled by
"something" and no longer is. The build now fails:
| checking for libiptc... no
| configure: error: Package requirements (libiptc) were not met:
|
| No package 'libiptc' found
|
| Consider adjusting the PKG_CONFIG_PATH environment variable if you
| installed software in a non-standard prefix.
|
| Alternatively, you may set the environment variables libiptc_CFLAGS
| and libiptc_LIBS to avoid the need to call pkg-config.
| See the pkg-config man page for more details.
| tail -v -n \+0 config.log
Helmut
--- End Message ---
--- Begin Message ---
Source: strongswan
Source-Version: 5.8.2-2
We believe that the bug you reported is fixed in the latest version of
strongswan, 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 951...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Yves-Alexis Perez (supplier of updated strongswan 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: Thu, 13 Feb 2020 22:46:40 +0100
Source: strongswan
Architecture: source
Version: 5.8.2-2
Distribution: unstable
Urgency: medium
Maintainer: strongSwan Maintainers
Changed-By: Yves-Alexis Perez
Closes: 951016
Changes:
strongswan (5.8.2-2) unstable; urgency=medium
.
* d/control: replace libip{4,6}tc-dev by libiptc-dev (Closes: #951016)
* d/copyright updated
Checksums-Sha1:
e08d4fa139a2fd9e9f3e47f80e72022c95356504 2981 strongswan_5.8.2-2.dsc
1256f3f04eea221b4f5fa7c05fb4729a05cbbf54 116572
strongswan_5.8.2-2.debian.tar.xz
8c51c866f9cce853ce818b11872d642b91fa29e2 16874
strongswan_5.8.2-2_amd64.buildinfo
Checksums-Sha256:
8cfd53119747ea25d938926434bbf7861be1ad5a0c049ac4df9ef3a50eb3a4cb 2981
strongswan_5.8.2-2.dsc
f0967d922d19499644f9c486ca13d9b3685cb192ef6c2aa063a2b08a62384a81 116572
strongswan_5.8.2-2.debian.tar.xz
a66462653b42dd3a59f38b8b5b2d837b28e55e3f615b4f72d36cc52b686aed35 16874
strongswan_5.8.2-2_amd64.buildinfo
Files:
ec8658f6e903c556d3edc017ad99f049 2981 net optional strongswan_5.8.2-2.dsc
328fdec1aa67c773499e2a36d6880c82 116572 net optional
strongswan_5.8.2-2.debian.tar.xz
66877a96bc5f4f6e03ce3a9603f9a35c 16874 net optional
strongswan_5.8.2-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQEzBAEBCgAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl5FyPsACgkQ3rYcyPpX
RFsm4ggAgDI5KbAfVnfaWzdXFFhr98V2p4u9sPXr51HyaMko8ZbalHycyhZqCGTf
R2kCJBLRCO47FQ9oxGbRgYfaq52OjdJkN10X4SdNulgv9AHzs6BoiJ1FkA1LN8cX
C0c/8LVTfcEEFR3dYax4Oul6gLibcgMCnRjhAMPmAgMRVePaDf8BSr5ZGlES9dgh
tDgfgmQsVwd9uGcqtj0Rao18hpziN5+sm4cfd7XQZBGVcvjClLy5wuw4xFMo6cXY
sElWDVGDC8v3/5nFx31aYGHLgp6Jp7Px9B97D+w+RCR+SXz2xun1uQutI8Irpd8E
lpe/bToH8TGycOINVYlkf8F5cWWcGg==
=gC5U
-END PGP SIGNATURE End Message ---
Processed: New version uploaded
Processing commands for cont...@bugs.debian.org: > severity 951115 normal Bug #951115 [src:ns3] ns3: FTBFS on mipsel (OOM of the linker) Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 951115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951115 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#951115: New version uploaded
severity 951115 normal thanks Hello, so I uploaded a version of this package without mipsel, and it built nicely on all architectures where its dependencies are to be found (all official architectures plus some others). Thus downgrading this bug. Thanks, Mt. signature.asc Description: PGP signature
Bug#938737: u1db: Python2 removal in sid/bullseye
On Fri, Aug 30, 2019 at 07:57:06AM +, Matthias Klose wrote: > Package: src:u1db > Version: 13.10-6.4 > 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. Hi Micah, per Wikipedia the Ubuntu One cloud storage has been shut down many years ago, should this simply be removed? Cheers, Moritz
Bug#936521: flashproxy: Python2 removal in sid/bullseye
On Fri, Aug 30, 2019 at 07:17:13AM +, Matthias Klose wrote: > Package: src:flashproxy > Version: 1.7-4 > 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 Hi, https://crypto.stanford.edu/flashproxy/ states | Status | | As of 2017, the flash proxy project is deprecated. It was deployed in Tor Browser | between 2013 and 2016, but has since been superseded by newer and more effective | pluggable transports. If you want to help support a newer circumvention system | designed along the same principles as flash proxy, please see Snowflake. Let's remove? Or is there any reason to keep it in Debian? Cheers, Moritz
Bug#950817: marked as done (archmage: FTBFS: tests fail: ModuleNotFoundError: No module named 'bs4')
Your message dated Thu, 13 Feb 2020 21:34:25 + with message-id and subject line Bug#950817: fixed in archmage 1:0.4.2.1-1 has caused the Debian Bug report #950817, regarding archmage: FTBFS: tests fail: ModuleNotFoundError: No module named 'bs4' 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.) -- 950817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950817 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: archmage Version: 1:0.4.1-2 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, archmage FTBFS in sid: https://buildd.debian.org/status/fetch.php?pkg=archmage=all=1%3A0.4.1-2=1579977169=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:26: in from bs4 import BeautifulSoup, UnicodeDammit E ModuleNotFoundError: No module named 'bs4' Andreas --- End Message --- --- Begin Message --- Source: archmage Source-Version: 1:0.4.2.1-1 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 950...@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: Thu, 13 Feb 2020 22:18:58 +0100 Source: archmage Architecture: source Version: 1:0.4.2.1-1 Distribution: unstable Urgency: low Maintainer: Mikhail Gusarov Changed-By: Mikhail Gusarov Closes: 949758 950817 Changes: archmage (1:0.4.2.1-1) unstable; urgency=low . * New upstream release. * Add missing python3-bs4 and python3-chm dependencies (Closes: #950817, #949758) Checksums-Sha1: 1bde6a00eafcd596b8b626a43450f2c24549ebd5 1776 archmage_0.4.2.1-1.dsc ff8462399a0d73568cc2be65ca610cee79c7f1b5 32233 archmage_0.4.2.1.orig.tar.gz 3b2b486cfac0225400b8e09bb8248294d4dce532 4496 archmage_0.4.2.1-1.debian.tar.xz 5e837462f58bb04ca1c859d73b56363ff755d069 5385 archmage_0.4.2.1-1_source.buildinfo Checksums-Sha256: af3ad72cb9c922980b853c574fc0eaab86d169b2fef3a3b06478ee6eeea4642e 1776 archmage_0.4.2.1-1.dsc f73d7917ce4458304d4e469389cf4155b0c1e56123c7bbde4b9338ae587917fb 32233 archmage_0.4.2.1.orig.tar.gz 7d8fc8b2775bcfbcfe05f904329dd7622d843eaf28f9f7b5dfccce9f31a7f1ab 4496 archmage_0.4.2.1-1.debian.tar.xz 2ab971f9050f2f23039b65dc08d0949a929edac8c148c0d2b842654f7facfc07 5385 archmage_0.4.2.1-1_source.buildinfo Files: 19057f3ff8ed01dcd1ddb00708c47264 1776 utils optional archmage_0.4.2.1-1.dsc f7cea8b77efe367294492f3e60de7da6 32233 utils optional archmage_0.4.2.1.orig.tar.gz 8d9dc614db6c094bf19d8a0d0dc86411 4496 utils optional archmage_0.4.2.1-1.debian.tar.xz a023f76c5c8b5dc718f54de9ede43e2e 5385 utils optional archmage_0.4.2.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEE6mdM4hvGehkaRy4s/eS3QibJkzgFAl5FvkgACgkQ/eS3QibJ kzib4QgArcu0SPAVJDQqUJQjbggJc9I8+xDb0I95i9tqzSRt1AWtBd82Rgfbceax 8r2s7BbBD2sdulw0Es0ntQfOAE1BK8hPX1cP0DLQ7X01LHREHZdzjq6xuGEPJ9vv 8iBjSkOg48Xyh9y7BFdz99nL1AIV9tHbOaMTskmInHaZtr+ZhdKM++w6O+DgE/ZW 0uQOz84WVV0fxz6tprWw7mNBJekZ5sRliOX78Q5U8U8jDyK4B0dOjOtPFhz4HexT Ni/pAZA3636BF8tnzOrx2sYO5FR9FWAtnVeYiw7zkSgi5rUlrCdD2j7KGt82ThWY zTWHmeAzPeMj0thQ1o5XkpM6DFz0tQ== =vM08 -END PGP SIGNATURE End Message ---
Bug#949758: marked as done (archmage: Missing build dependencies on python3-sgmllib3k and python3-chm)
Your message dated Thu, 13 Feb 2020 21:34:25 + with message-id and subject line Bug#949758: fixed in archmage 1:0.4.2.1-1 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.2.1-1 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: Thu, 13 Feb 2020 22:18:58 +0100 Source: archmage Architecture: source Version: 1:0.4.2.1-1 Distribution: unstable Urgency: low Maintainer: Mikhail Gusarov Changed-By: Mikhail Gusarov Closes: 949758 950817 Changes: archmage (1:0.4.2.1-1) unstable; urgency=low . * New upstream release. * Add missing python3-bs4 and python3-chm dependencies (Closes: #950817, #949758) Checksums-Sha1: 1bde6a00eafcd596b8b626a43450f2c24549ebd5 1776 archmage_0.4.2.1-1.dsc ff8462399a0d73568cc2be65ca610cee79c7f1b5 32233 archmage_0.4.2.1.orig.tar.gz 3b2b486cfac0225400b8e09bb8248294d4dce532 4496 archmage_0.4.2.1-1.debian.tar.xz 5e837462f58bb04ca1c859d73b56363ff755d069 5385 archmage_0.4.2.1-1_source.buildinfo Checksums-Sha256: af3ad72cb9c922980b853c574fc0eaab86d169b2fef3a3b06478ee6eeea4642e 1776 archmage_0.4.2.1-1.dsc f73d7917ce4458304d4e469389cf4155b0c1e56123c7bbde4b9338ae587917fb 32233 archmage_0.4.2.1.orig.tar.gz 7d8fc8b2775bcfbcfe05f904329dd7622d843eaf28f9f7b5dfccce9f31a7f1ab 4496 archmage_0.4.2.1-1.debian.tar.xz 2ab971f9050f2f23039b65dc08d0949a929edac8c148c0d2b842654f7facfc07 5385 archmage_0.4.2.1-1_source.buildinfo Files: 19057f3ff8ed01dcd1ddb00708c47264 1776 utils optional archmage_0.4.2.1-1.dsc f7cea8b77efe367294492f3e60de7da6 32233 utils optional archmage_0.4.2.1.orig.tar.gz 8d9dc614db6c094bf19d8a0d0dc86411 4496 utils optional archmage_0.4.2.1-1.debian.tar.xz a023f76c5c8b5dc718f54de9ede43e2e 5385 utils optional archmage_0.4.2.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEE6mdM4hvGehkaRy4s/eS3QibJkzgFAl5FvkgACgkQ/eS3QibJ kzib4QgArcu0SPAVJDQqUJQjbggJc9I8+xDb0I95i9tqzSRt1AWtBd82Rgfbceax 8r2s7BbBD2sdulw0Es0ntQfOAE1BK8hPX1cP0DLQ7X01LHREHZdzjq6xuGEPJ9vv 8iBjSkOg48Xyh9y7BFdz99nL1AIV9tHbOaMTskmInHaZtr+ZhdKM++w6O+DgE/ZW 0uQOz84WVV0fxz6tprWw7mNBJekZ5sRliOX78Q5U8U8jDyK4B0dOjOtPFhz4HexT Ni/pAZA3636BF8tnzOrx2sYO5FR9FWAtnVeYiw7zkSgi5rUlrCdD2j7KGt82ThWY zTWHmeAzPeMj0thQ1o5XkpM6DFz0tQ== =vM08 -END PGP SIGNATURE End Message ---
Bug#948930: closed ... (Bug#948930: fixed in python-socksipychain 2.1.0-2)
Dear maintainers, On 31-01-2020 11:54, Debian Bug Tracking System wrote: > python-socksipychain (2.1.0-2) unstable; urgency=medium [...] >* Migrate an autopkgtest to Python 3 from Python 2 (Closes: #948930) > (Closes: #938184). Unfortunately the test now fails in a different way: autopkgtest [15:55:40]: test command1: set -e ; for py in $(py3versions -r 2>/dev/null) ; do cd "$ADTTMP" ; echo "Testing with $py:" ; $py -c "import sockschain; print(sockschain)" ; done autopkgtest [15:55:40]: test command1: [--- Testing with python3.8: bash: python3.8: command not found autopkgtest [15:55:40]: test command1: ---] It seems you're missing a (test) dependency on python3-all (IIAC). Also, please, for such superficial tests, mark them as superficial, see https://salsa.debian.org/ci-team/autopkgtest/raw/master/doc/README.package-tests.rst. The same applies for the other test. Paul signature.asc Description: OpenPGP digital signature
Processed: tagging 943077
Processing commands for cont...@bugs.debian.org: > tags 943077 + pending Bug #943077 [src:fonts-lohit-deva] fonts-lohit-deva: Python2 removal in sid/bullseye Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 943077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943077 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#942622: Would the Games Team adopt Lightyears (pygame based, Python 3 port available)?
Hi all in the Games Team, One of the Debian games affected by the python3 transition is 2 Lightyears Into Space, source package name "lightyears". I've ported it to python3-pygame, and opened an upstream issue for merging it (sadly this doesn't have an upstream response yet). The Debian package isn't currently maintained by the Games Team, but one of the serious bugs is "Maintainer email address not working". I'm wondering if the Games Team would adopt it and apply my python3 port? Debian bugs: #942622 src:lightyears: Maintainer email address not working #912488 lightyears: Please migrate to python3-pygame #936945 lightyears: Python2 removal in sid/bullseye Upstream pull request: https://github.com/20kly/20kly/issues/2 https://github.com/stevecotton/20kly/tree/version1.4/python3 The Debian package's "copyright" file cleans up some of the oddities of the upstream README.md's licensing section, I'm sure it's distributable but expect it to get some questions if it went through the NEW queue. Oddities such as attributing an image as "copyright NASA" instead of saying that it's one of NASA's public domain images. I'm happy to put some effort in to fixing that. Thanks, Steve
Bug#949083: marked as done (krfb FTBFS: error: field 'm_clientActions' has incomplete type 'QHash')
Your message dated Thu, 13 Feb 2020 19:20:43 + with message-id and subject line Bug#949083: fixed in krfb 4:19.12.2-1 has caused the Debian Bug report #949083, regarding krfb FTBFS: error: field 'm_clientActions' has incomplete type 'QHash' 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.) -- 949083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949083 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: krfb Version: 4:17.08.3-1 Severity: serious Tags: ftbfs kfrb fails to build from source in unstable: | In file included from /<>/krfb/trayicon.cpp:19: | /<>/krfb/trayicon.h:44:39: error: field 'm_clientActions' has incomplete type 'QHash' |44 | QHash m_clientActions; | | ^~~ | In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:1204, | from /usr/include/x86_64-linux-gnu/qt5/QtCore/qnamespace.h:43, | from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs.h:48, | from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:46, | from /usr/include/x86_64-linux-gnu/qt5/QtCore/QObject:1, | from /usr/include/KF5/KNotifications/kstatusnotifieritem.h:24, | from /usr/include/KF5/KNotifications/KStatusNotifierItem:1, | from /<>/krfb/trayicon.h:21, | from /<>/krfb/trayicon.cpp:19: | /usr/include/x86_64-linux-gnu/qt5/QtCore/qtypeinfo.h:223:1: note: declaration of 'class QHash' | 223 | Q_DECLARE_MOVABLE_CONTAINER(QHash); | | ^~~ Also reproducible by reproducible builds: https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/krfb_17.08.3-1.rbuild.log.gz Also seen by crossqa since around September 2019: http://crossqa.debian.net/build/krfb_4:17.08.3-1_armhf_20190922042109.log Helmut --- End Message --- --- Begin Message --- Source: krfb Source-Version: 4:19.12.2-1 We believe that the bug you reported is fixed in the latest version of krfb, 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. Aurélien COUDERC (supplier of updated krfb 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: Thu, 13 Feb 2020 19:52:18 +0100 Source: krfb Architecture: source Version: 4:19.12.2-1 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers Changed-By: Aurélien COUDERC Closes: 949083 Changes: krfb (4:19.12.2-1) unstable; urgency=medium . * Team upload. . [ Sandro Knauß ] * New upstream release (18.04.1). * Update Vcs links to salsa. * Bump Standards-Version to 4.1.4 (No changes needed). * Bump debhelper build-dep and compat to 11. * Update build-deps and deps with the info from cmake * Update copyright file for new upstream. . [ Aurélien COUDERC ] * Switch debian/watch to new KDE release service URL. * New upstream release (19.12.2). (Closes: #949083) * Update build dependencies according to upstream build system: - cmake >= 3.0 - Qt >= 5.6.0 - KF5 libraries >= 5.31.0 - add libpipewire-0.2-dev build dependency * Drop patch build_against_gcc-6.patch fixed upstream. * Drop kde-l10n migration rules, not needed anymore after 2 stable releases. * Use secure copyright file specification URI. * Switch to debhelper-compat build dependency, bump compatibility level to 12. * Remove obsolete fields Contact, Name from debian/upstream/metadata (already present in machine-readable debian/copyright). * Switch from dhmk to dh --with kf5. * Borrow minimal upstream signing key from k3b. * Bump Standards-Version to 4.5.0: - Add Rules-Requires-Root: no. * Add hardening=+all build hardening flag. * Refresh debian/copyright. * Update project homepage URL. Checksums-Sha1: 8a9177ad390c5e6011a212e8d8097d343996fbf2 3083 krfb_19.12.2-1.dsc 113983b592cd5c99371c69e9e3a83db844ecf071 1276620 krfb_19.12.2.orig.tar.xz a38f9cd2e243911f593c3354e604463fc3ec5935 488 krfb_19.12.2.orig.tar.xz.asc
Bug#950485: marked as done (evolution-dev still depends on libenchant-dev instead of libenchant-2-dev)
Your message dated Thu, 13 Feb 2020 18:49:18 + with message-id and subject line Bug#950485: fixed in evolution 3.34.1-4 has caused the Debian Bug report #950485, regarding evolution-dev still depends on libenchant-dev instead of libenchant-2-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 950485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950485 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: evolution-dev Version: 3.34.1-3 Severity: grave evolution switched to enchant-2 in 3.34.1-3. However evolution-dev didn't, still depends on libenchant-dev, and pulls enchant, libenchant-dev, and libenchant1c2a. Should Depend on libenchant-2-dev instead. Thanks, Gerardo Malazdrewicz -- 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.5.0-rc5-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), LANGUAGE=es_AR:es (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages evolution-dev depends on: ii libcamel1.2-dev 3.34.3-1 ii libebackend1.2-dev 3.34.3-1 ii libedataserver1.2-dev3.34.3-1 ii libedataserverui1.2-dev 3.34.3-1 pn libenchant-dev ii libevolution 3.34.1-3 ii libgnome-desktop-3-dev 3.34.2-2 ii libgtk-3-dev 3.24.13-1 ii libwebkit2gtk-4.0-dev2.27.4-1 evolution-dev recommends no packages. evolution-dev suggests no packages. --- End Message --- --- Begin Message --- Source: evolution Source-Version: 3.34.1-4 We believe that the bug you reported is fixed in the latest version of evolution, 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 950...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laurent Bigonville (supplier of updated evolution 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: Thu, 13 Feb 2020 19:20:45 +0100 Source: evolution Architecture: source Version: 3.34.1-4 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Laurent Bigonville Closes: 950485 Changes: evolution (3.34.1-4) unstable; urgency=medium . * debian/control.in: Also switch to libenchant-2-dev for evolution-dev (Closes: #950485) Checksums-Sha1: 3927ec88ac155957f11c539194a13d38c06afbcb 3544 evolution_3.34.1-4.dsc 4a61519d7b08a49a8867438136cf4927810420f3 37088 evolution_3.34.1-4.debian.tar.xz 59b0e679b91c89906350bfe44b5e2900cc18df28 14605 evolution_3.34.1-4_source.buildinfo Checksums-Sha256: 022e114f1a14d8cba970fffb9eb15b6983fc2ffea03da001240d47ad3e46d7a8 3544 evolution_3.34.1-4.dsc 20cbcfce65988a7d8cf5dc526620a4b8a00d1b08de2aea01d96e50c78454187f 37088 evolution_3.34.1-4.debian.tar.xz 1e7475f422eebd17a4290782b326618604938fac9d92c049fcf301a60fc68eaf 14605 evolution_3.34.1-4_source.buildinfo Files: cb7ede61a6024313c5006089eb7758b9 3544 gnome optional evolution_3.34.1-4.dsc b4c33d093d9607e1910d2a5deb6b2839 37088 gnome optional evolution_3.34.1-4.debian.tar.xz 53baeedd7ca0e4e03d3b4332c252e964 14605 gnome optional evolution_3.34.1-4_source.buildinfo -BEGIN PGP SIGNATURE- iQFFBAEBCAAvFiEEmRrdqQAhuF2x31DwH8WJHrqwQ9UFAl5Fk98RHGJpZ29uQGRl Ymlhbi5vcmcACgkQH8WJHrqwQ9UXdAgAkIVI6xe2YfbqkSwe1YBvn6OOYEXVIUw5 zV8pLcT6seHAb4/8RN8LZ9T4Im1TvVLuDRy/SkE8cie3JL+2//XwXo9/qHlel7xJ kGfL6n6AsqkVjbCtUzol6Fr2ZTLFlXGVMWWBF4owjEd44E6VVW7WBMmr3czSJEgv 3fyVqhSEgXwnfinlB/UjAAb+meu3C0e5jgYuWtt9SKqByO7U7TgS3IXhAQ/mU9oH Y7txx/lYuKIiWgcZCcjXUwqrru8kBzO/GhAcOyY0KFwALR/4A3k26PT+UjCx+LIv mFEcRy57pHKNRJ/ZFmnqaCn8OBZDW0GJmwlfBF8rULAoo9MHMcSLkg== =jPUV -END PGP SIGNATURE End Message ---
Processed: severity of 951237 is important
Processing commands for cont...@bugs.debian.org: > severity 951237 important Bug #951237 [src:glibc] glibc/mips: bpo patch: mips: Fix argument passing for inlined syscalls on Linux [BZ #25523] Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 951237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951237 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#950485 marked as pending in evolution
Processing control commands: > tag -1 pending Bug #950485 [evolution-dev] evolution-dev still depends on libenchant-dev instead of libenchant-2-dev Added tag(s) pending. -- 950485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950485 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#950485: marked as pending in evolution
Control: tag -1 pending Hello, Bug #950485 in evolution 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/gnome-team/evolution/commit/ef17020d40c2a8d243dc87661b855e30ad6f0782 debian/control.in: Also switch to libenchant-2-dev for evolution-dev (Closes: #950485) (this message was generated automatically) -- Greetings https://bugs.debian.org/950485
Bug#951281: FTBFS: /usr/bin/ld: cannot find -lpthreads
Source: widelands Version: 1:20-1 Severity: serious Justification: ftbfs Tags: ftbfs Dear Maintainer, Widelands currently fails to build in Sid with the following error message: ... /usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_893c8.dir/link.txt --verbose=1 /usr/bin/cc -g -O2 -fdebug-prefix-map=/build/widelands-20=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -DCHECK_FUNCTION_EXISTS=pthread_create -Wl,-z,relro -rdynamic CMakeFiles/cmTC_893c8.dir/CheckFunctionExists.c.o -o cmTC_893c8 -lpthreads /usr/bin/ld: cannot find -lpthreads collect2: error: ld returned 1 exit status make[3]: *** [CMakeFiles/cmTC_893c8.dir/build.make:87: cmTC_893c8] Error 1 make[3]: Leaving directory '/build/widelands-20/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' make[2]: *** [Makefile:121: cmTC_893c8/fast] Error 2 make[2]: Leaving directory '/build/widelands-20/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DWL_INSTALL_BASEDIR=/usr/share/games/widelands -DWL_INSTALL_BINDIR=games -DWL_INSTALL_DATADIR=/usr/share/games/widelands/data -DWL_INSTALL_PREFIX=/usr -DOPTION_BUILD_WEBSITE_TOOLS=OFF -DCMAKE_BUILD_TYPE=Release .. returned exit code 1 make[1]: *** [debian/rules:14: override_dh_auto_configure] Error 25 make[1]: Leaving directory '/build/widelands-20' make: *** [debian/rules:10: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 I suspect the important part is "/usr/bin/ld: cannot find -lpthreads", which I suppose might be due to some underlying library change though I haven't figured it out. Saw the same error message when the package was rebuilt in Ubuntu, and I guess other packages using -lpthreads might suffer the same fate. Tried rebuilding the current upstream development version to see if it had a fix, but ran into a separate issue. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-3-amd64 (SMP w/3 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- mvh / best regards Hans Joachim Desserud http://desserud.org
Processed: [bts-link] source package gplaycli
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package gplaycli > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #950112 (http://bugs.debian.org/950112) > # Bug title: gplaycli: 502 Bad Gateway, does not work at all > # * https://github.com/matlink/gplaycli/issues/237 > # * remote status changed: open -> closed > # * closed upstream > tags 950112 + fixed-upstream Bug #950112 [gplaycli] gplaycli: 502 Bad Gateway, does not work at all Added tag(s) fixed-upstream. > usertags 950112 - status-open Usertags were: status-open. Usertags are now: . > usertags 950112 + status-closed There were no usertags set. Usertags are now: status-closed. > # remote status report for #950114 (http://bugs.debian.org/950114) > # Bug title: gplaycli: TypeError: search() got an unexpected keyword argument > 'nb_result' > # * https://github.com/matlink/gplaycli/issues/236 > # * remote status changed: open -> closed > # * closed upstream > tags 950114 + fixed-upstream Bug #950114 [gplaycli] gplaycli: TypeError: search() got an unexpected keyword argument 'nb_result' Added tag(s) fixed-upstream. > usertags 950114 - status-open Usertags were: status-open. Usertags are now: . > usertags 950114 + status-closed There were no usertags set. Usertags are now: status-closed. > # remote status report for #950116 (http://bugs.debian.org/950116) > # Bug title: gplaycli: KeyError: 'docId' --or-- 'Item not found.' > # * https://github.com/matlink/gplaycli/issues/231 > # * remote status changed: open -> closed > # * closed upstream > tags 950116 + fixed-upstream Bug #950116 [gplaycli] gplaycli: KeyError: 'docId' --or-- 'Item not found.' Added tag(s) fixed-upstream. > usertags 950116 - status-open Usertags were: status-open. Usertags are now: . > usertags 950116 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 950112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950112 950114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950114 950116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950116 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:shim
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:shim > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #925826 (http://bugs.debian.org/925826) > # Bug title: shim: ftbfs with GCC-9 > # * https://github.com/rhboot/shim/issues/161 > # * remote status changed: open -> closed > # * closed upstream > tags 925826 + fixed-upstream Bug #925826 [src:shim] shim: ftbfs with GCC-9 Added tag(s) fixed-upstream. > usertags 925826 - status-open Usertags were: status-open. Usertags are now: . > usertags 925826 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 925826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925826 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:netty
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:netty > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #950966 (http://bugs.debian.org/950966) > # Bug title: netty: CVE-2019-20444 > # * https://github.com/netty/netty/issues/9866 > # * remote status changed: (?) -> closed > # * closed upstream > tags 950966 + fixed-upstream Bug #950966 [src:netty] netty: CVE-2019-20444 Added tag(s) fixed-upstream. > usertags 950966 + status-closed There were no usertags set. Usertags are now: status-closed. > # remote status report for #950967 (http://bugs.debian.org/950967) > # Bug title: netty: CVE-2019-20445 CVE-2020-7238 > # * https://github.com/netty/netty/issues/9861 > # * remote status changed: (?) -> closed > # * closed upstream > tags 950967 + fixed-upstream Bug #950967 [src:netty] netty: CVE-2019-20445 CVE-2020-7238 Added tag(s) fixed-upstream. > usertags 950967 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 950966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950966 950967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950967 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:buzztrax
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:buzztrax > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #946861 (http://bugs.debian.org/946861) > # Bug title: buzztrax FTBFS after libfluidsynth update > # * https://github.com/Buzztrax/buzztrax/issues/87 > # * remote status changed: open -> closed > # * closed upstream > tags 946861 + fixed-upstream Bug #946861 [src:buzztrax] buzztrax FTBFS after libfluidsynth update Added tag(s) fixed-upstream. > usertags 946861 - status-open Usertags were: status-open. Usertags are now: . > usertags 946861 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 946861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946861 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#950435: marked as done (haproxy build-depends on package that has been dropped.)
Your message dated Thu, 13 Feb 2020 16:52:47 + with message-id and subject line Bug#950435: fixed in haproxy 2.1.3-1 has caused the Debian Bug report #950435, regarding haproxy build-depends on package that has been dropped. 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.) -- 950435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950435 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: haproxy Version: 2.0.12-1 Severity: serious haproxy build-depends-indep on python-mako, which is no longer built by the mako source package, it is still present in unstable as a cruft package, but is completely gone from testing. --- End Message --- --- Begin Message --- Source: haproxy Source-Version: 2.1.3-1 We believe that the bug you reported is fixed in the latest version of haproxy, 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 950...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Vincent Bernat (supplier of updated haproxy 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: Mon, 20 Jan 2020 06:53:23 +0100 Source: haproxy Architecture: source Version: 2.1.3-1 Distribution: experimental Urgency: medium Maintainer: Debian HAProxy Maintainers Changed-By: Vincent Bernat Closes: 948296 950435 Changes: haproxy (2.1.3-1) experimental; urgency=medium . * New upstream version. - BUG/MAJOR: hashes: fix the signedness of the hash inputs - BUG/MAJOR: memory: Don't forget to unlock the rwlock if the pool is empty. * d/dconv: use Python 3 to build the documentation. Closes: #948296, #950435. Checksums-Sha1: 04107a086e620320175669bf6fda21c3156154de 2301 haproxy_2.1.3-1.dsc 6904ebe6b1742d5e70592e85b1f664ac74b7280b 2675529 haproxy_2.1.3.orig.tar.gz cfebe4c9776d26f6cf45533ddf0f750545904094 68628 haproxy_2.1.3-1.debian.tar.xz f8849d4eb5882097635a3d0ce6d8982d373f1bc0 8275 haproxy_2.1.3-1_amd64.buildinfo Checksums-Sha256: 5c6fc93afdacbac2d6f0f87a51a017d580f7c66ea087960bf5949fed840e5944 2301 haproxy_2.1.3-1.dsc bb678e550374d0d9d9312885fb9d270b501dae9e3b336f0a4379c667dae00b59 2675529 haproxy_2.1.3.orig.tar.gz f820c5212b084db72590a62a57079f19e261d7c3692e022e3c64d444c978ffd9 68628 haproxy_2.1.3-1.debian.tar.xz 0972e057dae80f00bd6771096596fc5a2e2087e5613a973f3494edcf2df5629a 8275 haproxy_2.1.3-1_amd64.buildinfo Files: e6192d9ac4400c3d4f5b37cb2c42e6a4 2301 net optional haproxy_2.1.3-1.dsc bea4726d8c99f5d9bac0e62906a1f2d0 2675529 net optional haproxy_2.1.3.orig.tar.gz b931796e07bcc17a4d676d67f58097ca 68628 net optional haproxy_2.1.3-1.debian.tar.xz 8fb643a8cf200909f7660d39ef72bbc1 8275 net optional haproxy_2.1.3-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCAAwFiEErvI0h2bzccaJpzYAlaQv6DU1JfkFAl5Fey0SHGJlcm5hdEBk ZWJpYW4ub3JnAAoJEJWkL+g1NSX5qUQP+QFAZRgfTyy7u/XScy5B93pypQBhPTes lBXkh6xEEHXMPywz3pL1QPveD9TFG+ExIb1dKJkJlUe2YWSGN4cBFgx5nkEYc2Ys 8SH3k7+FJbbK4YRVB9ppeMC5TaIhJJRZITsCAKJ6Mf9PWUmeVeWakrOj/a0oU9nf 81ZombT+d426yw+BFdRzOwEYqAglccYFiggscR8Xtzbsh4okR0JtEjqf5aqjIAqK s+0q17H7Kw9k+Xj8UfuY0CU4Ai77Pfi9uPECb68lU2o0PJsyHMilQQOwy8g/gWsu +LOavsAfDq/InvhQQnftJdR5ar1LzHGMLrcFrqTPbWcXWf6HUGVwyRG0HMpSw9Xq Q/Y5EoS/qWDzR843a0x6T2QQsS5TvptYABXFCHRcHten4holfyL3NbCbBjZKRSAB VXl2joCkDtZo3KQBtZCAP96MDYjl46DBO44eS1RnQG6S/0SC+0XaWrz/qMISd4mD tZaDy8As8cIHwclUbv/AR5o+h3w52NeOezUcRcuOLE8BTtQMcARWXIV8tEz4scec MlwGD7IODxLz1xiAcY6zXGVaKLudX3+FZ8Hu35tuXf+w6qrccrBOJm/w4Mxuxwh8 KUphl4HrST6L9IBjRmEy5v83CEIm6+iEAxcCy54zGDRwxT1r5zG4e3makypwkOjb zEocwlCGlyiH =75fk -END PGP SIGNATURE End Message ---
Processed: RMs
Processing commands for cont...@bugs.debian.org: > reassign 939181 ftp.debian.org Bug #939181 [src:cycle] cycle: Python2 removal in sid/bullseye Bug reassigned from package 'src:cycle' to 'ftp.debian.org'. No longer marked as found in versions cycle/0.3.1-14 and cycle/0.3.1-15. Ignoring request to alter fixed versions of bug #939181 to the same values previously set > retitle 939181 RM: cycle -- RoQA; dead upstream; unmaintained; low popcon; > blocking py2 removal Bug #939181 [ftp.debian.org] cycle: Python2 removal in sid/bullseye Changed Bug title to 'RM: cycle -- RoQA; dead upstream; unmaintained; low popcon; blocking py2 removal' from 'cycle: Python2 removal in sid/bullseye'. > reassign 938608 ftp.debian.org Bug #938608 [src:svn-workbench] svn-workbench: Python2 removal in sid/bullseye Bug reassigned from package 'src:svn-workbench' to 'ftp.debian.org'. No longer marked as found in versions svn-workbench/1.8.2-3. Ignoring request to alter fixed versions of bug #938608 to the same values previously set > retitle 938608 RM: svn-workbench -- RoQA; dead upstream; low popcon; blocking > py2 removal Bug #938608 [ftp.debian.org] svn-workbench: Python2 removal in sid/bullseye Changed Bug title to 'RM: svn-workbench -- RoQA; dead upstream; low popcon; blocking py2 removal' from 'svn-workbench: Python2 removal in sid/bullseye'. > thanks Stopping processing here. Please contact me if you need assistance. -- 938608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938608 939181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939181 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#951151: polymake: test failure on mips64el
On 13/02/2020 13.18, David Bremner wrote: > Benjamin Lorenz writes: > >> >>> It looks like it's flint related? >> >> Yes, I think this is a bug in flint and for now I suggest disabling the >> flint-interface of polymake with the configure option --without-flint on >> mips64el. This has basically no functionality loss as polymake will use >> its own generic polynomial arithmetic instead (it will be somewhat slower). >> Currently rebuilding polymake to check the testsuite again but this will >> take some time and I will report back tomorrow. >> > > The easy thing would be to disable it everywhere. It is also possible to > do it on an architecture specific basis. Do you think the (small) added > complexity of the latter is worth it? It seems we might need some extra stuff for mips64el anyway as I see some weird segfaults even without flint (at different testcases). But I am still investigating those, backtrace seems to point to the exception handling code of libgcc / libstdc++: Program received signal SIGSEGV, Segmentation fault. parse_lsda_header (context=0x4000b9d880, p=0x260ae60 , info=0x4000b9cb50) at ../../../../src/libstdc++-v3/libsupc++/eh_personality.cc:58 58 ../../../../src/libstdc++-v3/libsupc++/eh_personality.cc: No such file or directory. (gdb) bt #0 parse_lsda_header (context=0x4000b9d880, p=0x260ae60 , info=0x4000b9cb50) at ../../../../src/libstdc++-v3/libsupc++/eh_personality.cc:58 #1 0x00400161005c in __cxxabiv1::__gxx_personality_v0 (version=, actions=, exception_class=, ue_header=0x400cfa8d50, context=0x4000b9d880) at ../../../../src/libstdc++-v3/libsupc++/eh_personality.cc:454 #2 0x0040017e33ac in _Unwind_RaiseException (exc=0x400cfa8d50) at ../../../src/libgcc/unwind.inc:118 #3 0x00400161126c in __cxxabiv1::__cxa_throw (obj=0x400cfa8d70, tinfo=0x4005e7ccf8 , dest=) at ../../../../src/libstdc++-v3/libsupc++/eh_throw.cc:90 #4 0x0040056fdfb8 in pm::lin_solve (A=..., b=...) at /usr/include/c++/9/ext/new_allocator.h:89 #5 0x00400c7a8408 in polymake::fan::remove_redundancies (f=...) at ./include/core/polymake/internal/shared_object.h:1097 ...
Bug#951139: Can someone please have a look (Was: Bug#951139: toil fails it's autopkg tests)
Hi,
in case you might have missed this. Seems to be serious to me.
Kind regards
Andreas.
On Tue, Feb 11, 2020 at 05:10:10PM +0100, Matthias Klose wrote:
> Package: src:toil
> Version: 3.23.1-1
> Severity: serious
> Tags: sid bullseye
>
> seen in https://ci.debian.net/packages/t/toil
> toil fails it's autopkg tests
>
> [...]
> autopkgtest [19:11:47]: test smoke-test: [---
> Traceback (most recent call last):
> File "/usr/bin/toil", line 11, in
> load_entry_point('toil==3.18.0', 'console_scripts', 'toil')()
> File "/usr/lib/python3/dist-packages/toil/utils/toilMain.py", line 13, in
> main
> modules = loadModules()
> File "/usr/lib/python3/dist-packages/toil/utils/toilMain.py", line 39, in
> loadModules
> from toil.utils import (toilKill,
> File "/usr/lib/python3/dist-packages/toil/utils/toilStatus.py", line 34, in
>
> from toil.jobStores.abstractJobStore import NoSuchJobStoreException,
> NoSuchFileException
> File "/usr/lib/python3/dist-packages/toil/jobStores/abstractJobStore.py",
> line
> 39, in
> from toil.job import JobException
> File "/usr/lib/python3/dist-packages/toil/job.py", line 51, in
> from toil.deferred import DeferredFunction
> File "/usr/lib/python3/dist-packages/toil/deferred.py", line 34, in
> from toil.resource import ModuleDescriptor
> File "/usr/lib/python3/dist-packages/toil/resource.py", line 43, in
> from toil.version import exactPython
> ImportError: cannot import name 'exactPython' from 'toil.version'
> (/usr/lib/python3/dist-packages/toil/version.py)
> autopkgtest [19:11:48]: test smoke-test: ---]
> autopkgtest [19:11:48]: test smoke-test: - - - - - - - - - - results - - - -
> -
> - - - - -
> smoke-test FAIL non-zero exit status 1
> autopkgtest [19:11:48]: test smoke-test: - - - - - - - - - - stderr - - - -
> - -
> - - - -
> Traceback (most recent call last):
> File "/usr/bin/toil", line 11, in
> load_entry_point('toil==3.18.0', 'console_scripts', 'toil')()
> File "/usr/lib/python3/dist-packages/toil/utils/toilMain.py", line 13, in
> main
> modules = loadModules()
> File "/usr/lib/python3/dist-packages/toil/utils/toilMain.py", line 39, in
> loadModules
> from toil.utils import (toilKill,
> File "/usr/lib/python3/dist-packages/toil/utils/toilStatus.py", line 34, in
>
> from toil.jobStores.abstractJobStore import NoSuchJobStoreException,
> NoSuchFileException
> File "/usr/lib/python3/dist-packages/toil/jobStores/abstractJobStore.py",
> line
> 39, in
> from toil.job import JobException
> File "/usr/lib/python3/dist-packages/toil/job.py", line 51, in
> from toil.deferred import DeferredFunction
> File "/usr/lib/python3/dist-packages/toil/deferred.py", line 34, in
> from toil.resource import ModuleDescriptor
> File "/usr/lib/python3/dist-packages/toil/resource.py", line 43, in
> from toil.version import exactPython
> ImportError: cannot import name 'exactPython' from 'toil.version'
> (/usr/lib/python3/dist-packages/toil/version.py)
> autopkgtest [19:11:48]: summary
> smoke-test FAIL non-zero exit status 1
>
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging
--
http://fam-tille.de
Bug#948734: marked as done (The package should be in contrib section)
Your message dated Thu, 13 Feb 2020 15:00:15 + with message-id and subject line Bug#948734: fixed in cyphesis-cpp 0.7.0~snap2~exp1 has caused the Debian Bug report #948734, regarding The package should be in contrib section 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.) -- 948734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948734 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cyphesis-cpp Version: 0.7.0~snap1 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 This package now installs the real program via snap. This shouldn't be in main. -BEGIN PGP SIGNATURE- iIYEARYIAC4WIQTiXc95jUQrjt9HgU3EhUo4GOCwFgUCXhtRIBAcemhzakBkZWJp YW4ub3JnAAoJEMSFSjgY4LAWQoQA/1NSsfzCb6E1+snvtzCQFAI0zAv/vaXD4o6c l2UzNOe4AQCFujP+3T+364kFsYAmK0Efw4rglTIhQVIFXyY2X3htAQ== =M8qs -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: cyphesis-cpp Source-Version: 0.7.0~snap2~exp1 We believe that the bug you reported is fixed in the latest version of cyphesis-cpp, 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. Olek Wojnar (supplier of updated cyphesis-cpp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 05 Feb 2020 11:58:51 -0500 Source: cyphesis-cpp Binary: cyphesis-cpp cyphesis-cpp-clients cyphesis-cpp-mason Architecture: source all amd64 Version: 0.7.0~snap2~exp1 Distribution: experimental Urgency: medium Maintainer: Debian Games Team Changed-By: Olek Wojnar Description: cyphesis-cpp - WorldForge game server (transitional package) cyphesis-cpp-clients - WorldForge game server - clients to control the server (transitio cyphesis-cpp-mason - WorldForge game server - game data for Mason (transitional packag Closes: 948734 Changes: cyphesis-cpp (0.7.0~snap2~exp1) experimental; urgency=medium . * Upload to experimental to clear NEW * Gracefully exit if unable to download Snap * Update Standards to 4.5.0 - Update cyphesis username to _cyphesis * Move to contrib since package now downloads external files (Closes: #948734) * Adjust supported architectures to match published snaps Checksums-Sha1: cc3fe80557557e33630102358064de93c1f8875f 1934 cyphesis-cpp_0.7.0~snap2~exp1.dsc 8de1cf0a5be35123085ebe97faf9ed0683fa6266 8036 cyphesis-cpp_0.7.0~snap2~exp1.tar.xz 6eaa2cd898dd94d572f5afd137cafc71afc44439 8744 cyphesis-cpp-clients_0.7.0~snap2~exp1_all.deb 298020a2eb39ebc7c535b7f72f36dd60fcf6b96e 8736 cyphesis-cpp-mason_0.7.0~snap2~exp1_all.deb 52990586403c9898f3bb5e47af9823ca23549117 6236 cyphesis-cpp_0.7.0~snap2~exp1_amd64.buildinfo 7e6a96308bce5a2f8cdd8208eb0791acaf246d28 9220 cyphesis-cpp_0.7.0~snap2~exp1_amd64.deb Checksums-Sha256: 94850fb58dd9f58a3815c2fd773968b367dffdcd3aecb10e91bfd35defbb4fdf 1934 cyphesis-cpp_0.7.0~snap2~exp1.dsc 32afa732bfd600453d8f1868dcf93ed51fac0ae62b6b88a97b398eea758e7d94 8036 cyphesis-cpp_0.7.0~snap2~exp1.tar.xz ec0682e65cd59eeda8683369108bff1c7bc40973b9e56545dcab084166b0a927 8744 cyphesis-cpp-clients_0.7.0~snap2~exp1_all.deb dac0834752e8bdd8ed9543e573a1a6a3a9f0a41d21a6d5dd86e534d8fdfa0879 8736 cyphesis-cpp-mason_0.7.0~snap2~exp1_all.deb b27baf05024c8d6baff5d431a3206a720126ea2ab60470417f53288ee00ebaf4 6236 cyphesis-cpp_0.7.0~snap2~exp1_amd64.buildinfo becdde41e0c54d07df55b5af291c79dfce069df746e5736136cd25624a442dd9 9220 cyphesis-cpp_0.7.0~snap2~exp1_amd64.deb Files: cfe08dba8b7f0236cef5b1b449461602 1934 contrib/oldlibs optional cyphesis-cpp_0.7.0~snap2~exp1.dsc 844c96d0c49305bd9691ddbfca9ef11e 8036 contrib/oldlibs optional cyphesis-cpp_0.7.0~snap2~exp1.tar.xz 129f73773deb04d50afb7084f6d9 8744 contrib/oldlibs optional cyphesis-cpp-clients_0.7.0~snap2~exp1_all.deb f887ad12008efe2c41405c1258f54915 8736 contrib/oldlibs optional cyphesis-cpp-mason_0.7.0~snap2~exp1_all.deb 25b440105c685ec9f6e7b2e6110fed07 6236 contrib/oldlibs optional cyphesis-cpp_0.7.0~snap2~exp1_amd64.buildinfo 062b6f18cbb51dd31206ca3b807e8db9 9220 contrib/oldlibs optional cyphesis-cpp_0.7.0~snap2~exp1_amd64.deb -BEGIN PGP SIGNATURE-
Bug#937750: python-feedvalidator: Python2 removal in sid/bullseye
X-Debbugs-CC: nsla...@tumbolia.org python-modules-t...@lists.alioth.debian.org On Fri, 30 Aug 2019 07:39:15 + Matthias Klose wrote: > Package: src:python-feedvalidator > Version: 0~svn1022-3 > > 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 Noah and fellow DPMT members, I found python-feedvalidator has a dead upstream, no maintainer activity in recent years, no reverse-dependencies and no build-reverse-dependencies. As a result, we should be removing it as part of the py2removal effort. I will be filing a removal bug soon. If there's any doubt, please let me know asap. -- Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#938608: RM svn-workbench
reassign -1 ftp.debian.org retitle -1 RM: svn-workbench -- RoQA; dead upstream; low popcon; blocking py2 removal
Bug#951265: ruby-vips: autopkgtest fails on arm64: expected Vips::Error but nothing was raised
Source: ruby-vips
Version: 2.0.13-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always
Dear maintainers,
Your new package ruby-vips has an autopkgtest, great. However, it fails
on arm64. I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it? (Also, please do an
additional source-only upload as we don't allow maintainer build
binaries to migrate to testing, but the infrastructure doesn't allow
binNMUs of arch:all packages).
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=ruby-vips
https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-vips/3481891/log.gz
RUBYLIB=. GEM_PATH= ruby2.5 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb
--backtrace -r ./spec/spec_helper.rb
...F
Failures:
1) Vips#call can throw errors for failed operations
Failure/Error: expect{black.resize(0.4)}.to
raise_exception(Vips::Error)
expected Vips::Error but nothing was raised
# /usr/lib/ruby/vendor_ruby/rspec/support.rb:97:in `block in
'
# /usr/lib/ruby/vendor_ruby/rspec/support.rb:106:in `notify_failure'
# /usr/lib/ruby/vendor_ruby/rspec/expectations/fail_with.rb:35:in
`fail_with'
# /usr/lib/ruby/vendor_ruby/rspec/expectations/handler.rb:40:in
`handle_failure'
# /usr/lib/ruby/vendor_ruby/rspec/expectations/handler.rb:50:in
`block in handle_matcher'
# /usr/lib/ruby/vendor_ruby/rspec/expectations/handler.rb:27:in
`with_matcher'
# /usr/lib/ruby/vendor_ruby/rspec/expectations/handler.rb:48:in
`handle_matcher'
#
/usr/lib/ruby/vendor_ruby/rspec/expectations/expectation_target.rb:65:in
`to'
#
/usr/lib/ruby/vendor_ruby/rspec/expectations/expectation_target.rb:101:in
`to'
# ./spec/vips_spec.rb:106:in `block (3 levels) in '
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:254:in
`instance_exec'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:254:in `block in run'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:500:in `block in
with_around_and_singleton_context_hooks'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:457:in `block in
with_around_example_hooks'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:464:in `block in run'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:602:in
`run_around_example_hooks_for'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:464:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:457:in
`with_around_example_hooks'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:500:in
`with_around_and_singleton_context_hooks'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:251:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:629:in
`block in run_examples'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:625:in `map'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:625:in
`run_examples'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:591:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:592:in
`block in run'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:592:in `map'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:592:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:116:in `block (3
levels) in run_specs'
# /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:116:in `map'
# /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:116:in `block (2
levels) in run_specs'
# /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1989:in
`with_suite_hooks'
# /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:111:in `block in
run_specs'
# /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:74:in `report'
# /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:110:in `run_specs'
# /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:87:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:71:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:45:in `invoke'
# /usr/bin/rspec:4:in `'
signature.asc
Description: OpenPGP digital signature
Bug#939181: RM cycle
reassign -1 ftp.debian.org retitle -1 RM: cycle -- RoQA; dead upstream; unmaintained; low popcon; blocking py2 removal
Bug#906026: Switch to Ayatana Indicators
Hi Andreas, thanks for following up on this. On Do 13 Feb 2020 13:11:50 CET, Andreas Henriksson wrote: Control: severity -1 serious Hello XFCE Maintainers, I'm bumping the severity of this bug report because the libindicators package in RC buggy and likely not going to make it for bullseye, plus the fact that this bug report has been open with patch for >1.5 years now! Apparently it needs some extra visibility or likely an NMU. Regards, Andreas Henriksson As a short update on this, let me add... The Ayatana Indicators will be a heavy dependency of the upcoming-to-Debian Unity8 desktop environment. The Unity8 packaging is funded, so I will be able to work on Ayatana Indicators in Debian in general in the context of the Unity8 packaging, as well. This said, porting over from libindicator to libayatana-indicator is the only way to go here. Furthermore, applications built against libappindicator should be ported to libayatana-appindicator. However, this is OT here, just a general info. For more info, see here: https://wiki.debian.org/Ayatana/IndicatorsTransition (I haven't updated this page for a while, but it is certainly on my (long) list). Mike -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de pgpwot1KSOE7Z.pgp Description: Digitale PGP-Signatur
Processed: block 941264 by 951258
Processing commands for cont...@bugs.debian.org: > block 941264 by 951258 Bug #941264 [php-cache-lite] phpunit breaks php-cache-lite autopkgtest: tries to write to /usr/bin/.phpunit.result.cache 941264 was not blocked by any bugs. 941264 was not blocking any bugs. Added blocking bug(s) of 941264: 951258 > thanks Stopping processing here. Please contact me if you need assistance. -- 941264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941264 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#951247: [Pkg-javascript-devel] Bug#951247: html2canvas: build-depends on removed package libjs-mocha
On Thu, Feb 13, 2020 at 11:07:01AM +0100, Xavier wrote:
> Le 13/02/2020 à 09:11, Ralf Treinen a écrit :
> > Source: html2canvas
> > Version: 0.5.0~beta4+ds1-2
> > Severity: serious
> > User: trei...@debian.org
> > Usertags: edos-uninstallable
> >
> > Hi,
> >
> > html2canvas build-depends on libjs-mocha which only exists in
> > old{old}stable.
> >
> > -Ralf.
>
> Hi,
>
> html2canvas is going to be removed from Debian. To you need it as a
> package dependency?
Hi, no I do not need it myself, I was just going through the issues found
by dose-builddebcheck.
Thanks for asking -Ralf.
Bug#951230: marked as done (linux-image-4.19.0-8-amd64: Boot Fails with LVM /usr)
Your message dated Thu, 13 Feb 2020 12:51:03 + with message-id and subject line Re: Bug#951230: linux-image-4.19.0-8-amd64: Boot Fails with LVM /usr has caused the Debian Bug report #951230, regarding linux-image-4.19.0-8-amd64: Boot Fails with LVM /usr 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.) -- 951230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951230 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 4.19.98-1 Severity: critical Justification: breaks the whole system Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Updated from Stretch to Buster * What exactly did you do (or not do) that was effective (or ineffective)? Reboot after dist-upgrade * What was the outcome of this action? Boot failure * What outcome did you expect instead? Normal boot *** End of the template - remove these template lines *** -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: VMware, Inc. product_name: VMware Virtual Platform product_version: None chassis_vendor: No Enclosure chassis_version: N/A bios_vendor: Phoenix Technologies LTD bios_version: 6.00 board_vendor: Intel Corporation board_name: 440BX Desktop Reference Platform board_version: None ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge [8086:7190] (rev 01) Subsystem: VMware Virtual Machine Chipset [15ad:1976] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B+ PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Kernel modules: shpchp 00:07.0 ISA bridge [0601]: Intel Corporation 82371AB/EB/MB PIIX4 ISA [8086:7110] (rev 08) Subsystem: VMware Virtual Machine Chipset [15ad:1976] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: vmw_vmci Kernel modules: vmw_vmci 00:0f.0 VGA compatible controller [0300]: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: vmwgfx Kernel modules: vmwgfx 00:10.0 SCSI storage controller [0100]: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI [1000:0030] (rev 01) Subsystem: VMware LSI Logic Parallel SCSI Controller [15ad:1976] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: mptspi Kernel modules: mptspi 00:11.0 PCI bridge [0604]: VMware PCI bridge [15ad:0790] (rev 02) (prog-if 01 [Subtractive decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: 00:15.0 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport Kernel modules: shpchp 00:15.1 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport Kernel
Bug#951151: polymake: test failure on mips64el
Benjamin Lorenz writes: > >> It looks like it's flint related? > > Yes, I think this is a bug in flint and for now I suggest disabling the > flint-interface of polymake with the configure option --without-flint on > mips64el. This has basically no functionality loss as polymake will use > its own generic polynomial arithmetic instead (it will be somewhat slower). > Currently rebuilding polymake to check the testsuite again but this will > take some time and I will report back tomorrow. > The easy thing would be to disable it everywhere. It is also possible to do it on an architecture specific basis. Do you think the (small) added complexity of the latter is worth it? d
Processed: Re: Switch to Ayatana Indicators
Processing control commands: > severity -1 serious Bug #906026 [lightdm-gtk-greeter] Switch to Ayatana Indicators Severity set to 'serious' from 'wishlist' -- 906026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#949303 marked as pending in vinagre
Processing control commands:
> tag -1 pending
Bug #949303 {Done: Debian FTP Masters }
[src:vinagre] vinagre: FTBFS: appstream validation fails
Added tag(s) pending.
--
949303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949303
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#951102: marked as done (iptables-restore empty line not accepted any more (regression))
Your message dated Thu, 13 Feb 2020 11:49:08 + with message-id and subject line Bug#951102: fixed in iptables 1.8.4-3 has caused the Debian Bug report #951102, regarding iptables-restore empty line not accepted any more (regression) 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.) -- 951102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951102 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: iptables Version: 1.8.4-2 Severity: grave Tags: security After upgrading from "1.8.3-2", iptables-restore handles empty lines differently and does not restore the rules. Thus old rulesets stored with save and then annotated for better readability (to avoid loads of "iptables -A" calls), do not load any more. As firewall data is ignored, this might break network access to machines or have unknown security impact on the current firewall ruleset. # iptables-restore --noflush < *nat > > -A POSTROUTING -s 10.0.0.0/16 -o usb0 -j SNAT --to-source 192.168.0.1 > COMMIT > *filter > > -A INPUT -p tcp -m tcp --dport 22 -j DROP > COMMIT > EOF iptables-restore: COMMIT expected at line 2 # iptables-restore --noflush < *nat > -A POSTROUTING -s 10.0.0.0/16 -o usb0 -j SNAT --to-source 192.168.0.1 > COMMIT > *filter > > -A INPUT -p tcp -m tcp --dport 22 -j DROP > COMMIT > EOF iptables-restore: COMMIT expected at line 5 --- End Message --- --- Begin Message --- Source: iptables Source-Version: 1.8.4-3 We believe that the bug you reported is fixed in the latest version of iptables, 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 951...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Arturo Borrero Gonzalez (supplier of updated iptables 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: Thu, 13 Feb 2020 12:20:19 +0100 Source: iptables Architecture: source Version: 1.8.4-3 Distribution: unstable Urgency: medium Maintainer: Debian Netfilter Packaging Team Changed-By: Arturo Borrero Gonzalez Closes: 949518 949576 951102 Changes: iptables (1.8.4-3) unstable; urgency=medium . [ Alberto Molina Coballes ] * [d87a98a] libiptc-dev: add Breaks and Replaces fields (Closes: #949576) . [ Arturo Borrero Gonzalez ] * [c66f003] d/patches: add -upstream-xtables-restore-empty-lines.patch (Closes: #949518, #951102) Checksums-Sha1: 6855e5a47a33d16db736cb1e230e07a6260abe36 2719 iptables_1.8.4-3.dsc 2bd50da76dc5f6d2a0a5ab19b1309256b5b9541a 65296 iptables_1.8.4-3.debian.tar.xz 665a9e5c2d210c244c4829267e7839a28078acad 8930 iptables_1.8.4-3_amd64.buildinfo Checksums-Sha256: 0d0c9ae69f984d7ad8aef1f4361e56b01dfbb3908f2640644b02c62c0623f723 2719 iptables_1.8.4-3.dsc 1d7018909d55f4f578f811ee5eff7591d91af79a6283a947d1c8c2c5f5a4ffab 65296 iptables_1.8.4-3.debian.tar.xz 246db2f866719056a6151bbf012009e37f17dab73cb32f1c3d1bceb9aaa8e854 8930 iptables_1.8.4-3_amd64.buildinfo Files: b1c340a45b30e219f0699556ee025b4e 2719 net optional iptables_1.8.4-3.dsc f5ecfac4e9b237523918d4455a048328 65296 net optional iptables_1.8.4-3.debian.tar.xz 6ed24d046354ea4bc3e1183aaae47f4e 8930 net optional iptables_1.8.4-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE3ZhhqyPcMzOJLgepaOcTmB0VFfgFAl5FMmwACgkQaOcTmB0V FfhnwA//VpbUjvSYQkdTxP97m1/1g1KZPcoGUgzN0Xt+qNhyjgUBbfKaqzsUSZMu 2ej6+4xZ+qFjKolOdnkNew/rE4BUk3mH74cKQQKChBT5ud0tNKMZru8XeVNHbUBT ajBwDrHHusdhnEod2wODH2Ip4UurkXSVgY3eeDSLLrvMYMaAqkchznSj6r693ks3 PSw+S8zDYlYO5sMIWB4B52TCuOqtmCOl2THaRt4e3+kSG6PfotgCAQdMhQ/Ki6ka XIN6dA04MGt+YJlBEBbMpAmamN6QPPgMZjCSv8nWpJKjy5nN0YCrEb+f0NjLrhtn EKGAu2bAUAbsSGZUz4rQwJjMIqPbRKpYOhfpX5UYg9E/xS4AKuIg07aNSH6xtsQe cwQ6IUHt/I5LcopQfDEXJdcvInT42cVLNXCrET4U4g+cJ5Naiqery6gBOUCmPl/g R0nS3wYVooW4/CT+7iS0UxtgDEXkNyLQl5uRGX8qS/Rzmp6gJbDdEGA5xxUr4Oxv hi1OKxFQ0YB24+Zj5dEBWBTwoa5C6KYiUwYNB3gmNgtQNAExZsZTolkHO8z5Gt5/ nUOgkCMrwqguBfA4xqu4DmVnGU9reTw3wfX6fpzSUXNaxNwp+o1irqAFXUycMqor YHDajXk8I7g2XRDrea4L08cZbGhJ05h/oUOCB52MrHabdemECEw= =EGai -END PGP SIGNATURE End Message ---
Bug#949518: marked as done (ufw: does not work with iptables-restore 1.8.4-2 (blank line in file))
Your message dated Thu, 13 Feb 2020 11:49:08 + with message-id and subject line Bug#949518: fixed in iptables 1.8.4-3 has caused the Debian Bug report #949518, regarding ufw: does not work with iptables-restore 1.8.4-2 (blank line in file) 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.) -- 949518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949518 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ufw Version: 0.36-1 Severity: grave Justification: renders package unusable ufw fails to start with iptables 1.8.4-2, even after #946289 is fixed. Downgrading to iptables 1.8.3-2 fixes this. iptables-restore (iptables-nft-restore) can no longer handle blank lines in the restored file. Jan 21 06:39:42 hostname ufw-init[39272]: iptables-restore: COMMIT expected at line 19 Jan 21 06:39:42 hostname ufw-init[39373]: ip6tables-restore: COMMIT expected at line 19 Jan 21 06:39:42 hostname ufw-init[39379]: Problem running '/etc/ufw/user.rules' Jan 21 06:39:42 hostname ufw-init[39379]: Problem running '/etc/ufw/user6.rules' Line 19 is the first blank line after the '### RULES ###' in user.rules: % sudo head -n19 /etc/ufw/user.rules *filter :ufw-user-input - [0:0] :ufw-user-output - [0:0] :ufw-user-forward - [0:0] :ufw-before-logging-input - [0:0] :ufw-before-logging-output - [0:0] :ufw-before-logging-forward - [0:0] :ufw-user-logging-input - [0:0] :ufw-user-logging-output - [0:0] :ufw-user-logging-forward - [0:0] :ufw-after-logging-input - [0:0] :ufw-after-logging-output - [0:0] :ufw-after-logging-forward - [0:0] :ufw-logging-deny - [0:0] :ufw-logging-allow - [0:0] :ufw-user-limit - [0:0] :ufw-user-limit-accept - [0:0] ### RULES ### :ufw-after-logging-forward - [0:0] :ufw-logging-deny - [0:0] :ufw-logging-allow - [0:0] :ufw-user-limit - [0:0] :ufw-user-limit-accept - [0:0] ### RULES ### % Tiny reproduction: paul@vm$ echo -ne '*filter\n:otters - [0:0]\n# this is a comment\n\n-A otters -j ACCEPT\nCOMMIT\n' > has-blank-line.txt paul@vm$ echo -ne '*filter\n:otters - [0:0]\n# this is a comment\n-A otters -j ACCEPT\nCOMMIT\n' > has-no-blank-line.txt paul@vm$ sudo iptables-restore -v -n --- End Message --- --- Begin Message --- Source: iptables Source-Version: 1.8.4-3 We believe that the bug you reported is fixed in the latest version of iptables, 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. Arturo Borrero Gonzalez (supplier of updated iptables 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: Thu, 13 Feb 2020 12:20:19 +0100 Source: iptables Architecture: source Version: 1.8.4-3 Distribution: unstable Urgency: medium Maintainer: Debian Netfilter Packaging Team Changed-By: Arturo Borrero Gonzalez Closes: 949518 949576 951102 Changes: iptables (1.8.4-3) unstable; urgency=medium . [ Alberto Molina Coballes ] * [d87a98a] libiptc-dev: add Breaks and Replaces fields (Closes: #949576) . [ Arturo Borrero Gonzalez ] * [c66f003] d/patches: add -upstream-xtables-restore-empty-lines.patch (Closes: #949518, #951102) Checksums-Sha1: 6855e5a47a33d16db736cb1e230e07a6260abe36 2719 iptables_1.8.4-3.dsc 2bd50da76dc5f6d2a0a5ab19b1309256b5b9541a 65296 iptables_1.8.4-3.debian.tar.xz 665a9e5c2d210c244c4829267e7839a28078acad 8930 iptables_1.8.4-3_amd64.buildinfo Checksums-Sha256: 0d0c9ae69f984d7ad8aef1f4361e56b01dfbb3908f2640644b02c62c0623f723 2719 iptables_1.8.4-3.dsc 1d7018909d55f4f578f811ee5eff7591d91af79a6283a947d1c8c2c5f5a4ffab 65296 iptables_1.8.4-3.debian.tar.xz 246db2f866719056a6151bbf012009e37f17dab73cb32f1c3d1bceb9aaa8e854 8930 iptables_1.8.4-3_amd64.buildinfo Files: b1c340a45b30e219f0699556ee025b4e 2719 net optional iptables_1.8.4-3.dsc f5ecfac4e9b237523918d4455a048328 65296 net optional iptables_1.8.4-3.debian.tar.xz 6ed24d046354ea4bc3e1183aaae47f4e 8930 net optional iptables_1.8.4-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE3ZhhqyPcMzOJLgepaOcTmB0VFfgFAl5FMmwACgkQaOcTmB0V FfhnwA//VpbUjvSYQkdTxP97m1/1g1KZPcoGUgzN0Xt+qNhyjgUBbfKaqzsUSZMu
Bug#949303: marked as pending in vinagre
Control: tag -1 pending Hello, Bug #949303 in vinagre 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/gnome-team/vinagre/commit/56536a073b4e158c0f2f50e801e72566745d5d94 Add debian/patches/131d151cb02245f84918f9ba5b3ef055758bcf61.patch - add releases and content_rating tags in appdata Closes: #949303 Gbp-Dch: full (this message was generated automatically) -- Greetings https://bugs.debian.org/949303
Bug#933054: marked as done (gnome-disks: segfault error 4 in libgobject-2.0.so.0.5800.3)
Your message dated Thu, 13 Feb 2020 12:41:27 +0100 with message-id <20200213114127.v43wrdysa6466...@fatal.se> and subject line no feedback -> closing has caused the Debian Bug report #933054, regarding gnome-disks: segfault error 4 in libgobject-2.0.so.0.5800.3 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.) -- 933054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933054 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-disk-utility Version: 3.30.2-3 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Looking at a USB3 attached disk, deleting partitions. It crashed. * What exactly did you do (or not do) that was effective (or ineffective)? This time (the second) I was deleting a partition. The other time, I had left it running a long SMART test on a USB-attached disk. * What was the outcome of this action? GUI gone. segfault report in dmesg. * What outcome did you expect instead? My expectation was that the GUI would remain extant, so that the operation could complete. *** End of the template - remove these template lines *** -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/20 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-disk-utility depends on: ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2 ii libatk1.0-0 2.30.0-2 ii libc62.28-10 ii libcairo21.16.0-4 ii libcanberra-gtk3-0 0.30-7 ii libdvdread4 6.0.1-1 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libglib2.0-0 2.58.3-2 ii libgtk-3-0 3.24.5-1 ii liblzma5 5.2.4-1 ii libnotify4 0.7.7-4 ii libpango-1.0-0 1.42.4-6 ii libpangocairo-1.0-0 1.42.4-6 ii libpwquality11.4.0-3 ii libsecret-1-00.18.7-1 ii libsystemd0 241-5 ii libudisks2-0 2.8.1-4 ii udisks2 2.8.1-4 gnome-disk-utility recommends no packages. gnome-disk-utility suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Given this has had no followup in the past 6 months I'm closing the bug report. Regards, Andreas Henriksson--- End Message ---
Bug#826560: node-carto: Current version is old and incompatible with recent versions of mapnik
Package: node-carto Followup-For: Bug #826560 Hi, since I needed this at $WORK and am also personally interested in this as an OSM contributor and Debian user, I took a closer look at the current state. It basically seems to require work on three packages: * node-chroma-js [1,2]: The WIP packaging from [2] doesn't seem to work even though node-catty is in e.g. Buster now. It seems that upstream used their own fork of node-catty, which added Coffescript support, and without that, the package cannot be built. However, in the meantime, upstream [3] seems to have changed to a different build system (Rollup) and also seems to use plain JavaScript now, so if no package that provides a variant that works in a browser has to be built (that would require some additional Rollup-extensions as build-time dependencies that are not in Debian, but Rollup itself is), 'simply' installing the source files from the upstream repo to the correct location might get this done. * hsluv: This is a new dependency of carto, so that needs to be packaged. There is a (dormant) ITP for the Python-version of HSLUV [4], but that seems to use a different and modified source than the JavaScript version (that gets built from the reference implementation that is written in Haxe [5], seems this was done with the Python version as well, but it was then further modified). The Haxe compiler that is in Debian is able to build the hsluv source code. Unfortunately, they don't seem to have anything like tags or source code releases, which is probably a bit tedious when packaging it. This seems to be a replacement/successor of node-husl which was in Debian before. * node-carto [6]: Once the above packages are done, node-carto can be updated to the latest upstream [7] release (1.2.0). If anybody wants to continue working on this, I can push the prototypical packaging that works for me somewhere, e.g. Salsa. The packaging is either based on the existing repos on Salsa (node-chroma-js [2], node-carto [6]) or contains a new package (hsluv). This packaging attempt is likely far from good enough to be directly used in Debian, but I guess it could serve as an 'inspiration' and to get a 'lower bound' for the work that is required to get an updated node-carto package. Kind regards Manfred [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844229 [2] https://salsa.debian.org/js-team/node-chroma-js [3] https://github.com/gka/chroma.js [4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891391 [5] https://github.com/hsluv/hsluv [6] https://salsa.debian.org/js-team/node-carto [7] https://github.com/mapbox/carto
Bug#950062: marked as done (python-babel FTBFS: fixture 'locale' not found)
Your message dated Thu, 13 Feb 2020 10:39:16 + with message-id and subject line Bug#950062: fixed in python-babel 2.8.0+dfsg.1-1 has caused the Debian Bug report #950062, regarding python-babel FTBFS: fixture 'locale' not found to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 950062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950062 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-babel Version: 2.6.0+dfsg.1-1 Severity: serious Tags: ftbfs bullseye sid ... ERRORS __ ERROR at setup of test_no_inherit_metazone_marker_never_in_output ___ file /tmp/python-babel-2.6.0+dfsg.1/tests/test_dates.py, line 769 @pytest.mark.all_locales def test_no_inherit_metazone_marker_never_in_output(locale): E fixture 'locale' not found > available fixtures: cache, capfd, capfdbinary, caplog, capsys, > capsysbinary, doctest_namespace, monkeypatch, os_environ, pytestconfig, > record_property, record_testsuite_property, record_xml_attribute, recwarn, > tmp_path, tmp_path_factory, tmpdir, tmpdir_factory > use 'pytest --fixtures [testpath]' for help on them. /tmp/python-babel-2.6.0+dfsg.1/tests/test_dates.py:769 __ ERROR at setup of test_smoke_dates __ file /tmp/python-babel-2.6.0+dfsg.1/tests/test_smoke.py, line 17 @pytest.mark.all_locales def test_smoke_dates(locale): E fixture 'locale' not found > available fixtures: cache, capfd, capfdbinary, caplog, capsys, > capsysbinary, doctest_namespace, monkeypatch, os_environ, pytestconfig, > record_property, record_testsuite_property, record_xml_attribute, recwarn, > tmp_path, tmp_path_factory, tmpdir, tmpdir_factory > use 'pytest --fixtures [testpath]' for help on them. /tmp/python-babel-2.6.0+dfsg.1/tests/test_smoke.py:17 _ ERROR at setup of test_smoke_numbers _ file /tmp/python-babel-2.6.0+dfsg.1/tests/test_smoke.py, line 27 @pytest.mark.all_locales def test_smoke_numbers(locale): E fixture 'locale' not found > available fixtures: cache, capfd, capfdbinary, caplog, capsys, > capsysbinary, doctest_namespace, monkeypatch, os_environ, pytestconfig, > record_property, record_testsuite_property, record_xml_attribute, recwarn, > tmp_path, tmp_path_factory, tmpdir, tmpdir_factory > use 'pytest --fixtures [testpath]' for help on them. /tmp/python-babel-2.6.0+dfsg.1/tests/test_smoke.py:27 ... --- End Message --- --- Begin Message --- Source: python-babel Source-Version: 2.8.0+dfsg.1-1 We believe that the bug you reported is fixed in the latest version of python-babel, 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 950...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Håvard Flaget Aasen (supplier of updated python-babel package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 12 Feb 2020 17:56:36 +0100 Source: python-babel Architecture: source Version: 2.8.0+dfsg.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Håvard Flaget Aasen Closes: 950062 Changes: python-babel (2.8.0+dfsg.1-1) unstable; urgency=medium . * Team upload [ Ondřej Nový ] * Use debhelper-compat instead of debian/compat. . [ Håvard Flaget Aasen ] * New upstream version 2.8.0+dfsg.1 Changes in new release closes: #950062 * Update URI in d/repack CLDR version 36 * d/copyright, update copyright year * d/control - Update Standards-Version to 4.5.0 - Bump debhelper to 12 - Add Rules-Requires-Root: no * Add 0002-remove-google-fonts.patch * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. * d/rules - Change buildsystem to pybuild - Create missing directory in override_dh_auto_build - Copy AUTHOR file in *.doc package, remove d/python-babel-doc.docs - Change how python versions is acquired from the shell. - Removed get-orig-source Checksums-Sha1:
Bug#951247: [Pkg-javascript-devel] Bug#951247: html2canvas: build-depends on removed package libjs-mocha
Le 13/02/2020 à 09:11, Ralf Treinen a écrit :
> Source: html2canvas
> Version: 0.5.0~beta4+ds1-2
> Severity: serious
> User: trei...@debian.org
> Usertags: edos-uninstallable
>
> Hi,
>
> html2canvas build-depends on libjs-mocha which only exists in
> old{old}stable.
>
> -Ralf.
Hi,
html2canvas is going to be removed from Debian. To you need it as a
package dependency?
Bug#949083: krfb FTBFS fixed upstream?
Le 13 février 2020 03:57:06 GMT+01:00, Debian Bug Tracking System a écrit : >Processing commands for cont...@bugs.debian.org: > >> forwarded 949083 https://phabricator.kde.org/D23059 >Bug #949083 [src:krfb] krfb FTBFS: error: field 'm_clientActions' has >incomplete type 'QHash' >Set Bug forwarded-to-address to 'https://phabricator.kde.org/D23059'. >> tags 949083 patch fixed-upstream >Bug #949083 [src:krfb] krfb FTBFS: error: field 'm_clientActions' has >incomplete type 'QHash' >Added tag(s) fixed-upstream and patch. >> thanks >Stopping processing here. > >Please contact me if you need assistance. Dear John, thanks for your research on this. The new upstream version *does* fix the FTBFS. I need to tidy up a couple more things on the package and I'll upload version 19.12.2, hopefully today. Happy hacking ! -- Aurélien
Bug#950535: [pkg-netfilter-team] Bug#950535: iptables-restore segfaults on nat table
On Thu, Feb 13, 2020 at 11:05:13AM +0100, Christoph Martin wrote: > > I choose the grave severity because the bug makes a reload of ufw fail > and then the firewall is off ! > Yes, I agree with you that it's a serious situation, but we have to determine if it's a general case of iptables (which it seems it's not) or if it's a problem with a specific ruleset. We need to determine if it's a grave severity in the iptables package in the stable branch. I'll contact with ufw maintainers to obtain more info. Thanks! Alberto
Bug#951249: marked as done (panicparse: FTBFS on arch:all)
Your message dated Thu, 13 Feb 2020 10:15:42 + with message-id and subject line Bug#951249: fixed in panicparse 1.3.0-3 has caused the Debian Bug report #951249, regarding panicparse: FTBFS on arch:all 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.) -- 951249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951249 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: panicparse Version: 1.3.0-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious Tags: ftbfs User: debian...@lists.debian.org Usertags: always-fails Dear maintainers, Your new package panicparse has an autopkgtest, great. However, it fails because your package fails to build from source on arch:all and hence the package it test depends on is not available. I copied some of the output at the bottom of this report. I also included some of the output of the build log. Currently this is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=panicparse https://ci.debian.net/data/autopkgtest/testing/amd64/p/panicparse/4146771/log.gz autopkgtest: WARNING: package golang-github-maruel-panicparse-dev is not installed though it should be autopkgtest: WARNING: package panicparse is not installed though it should be autopkgtest: WARNING: Test dependencies are unsatisfiable - calling apt install on test deps directly for further data about failing dependencies in test logs Tail of log for panicparse on all: dh clean --builddirectory=_build --buildsystem=golang --with=golang dh_auto_clean -O--builddirectory=_build -O--buildsystem=golang dh_autoreconf_clean -O--builddirectory=_build -O--buildsystem=golang dh_clean -O--builddirectory=_build -O--buildsystem=golang debian/rules binary-indep dh binary-indep --builddirectory=_build --buildsystem=golang --with=golang dh_update_autotools_config -i -O--builddirectory=_build -O--buildsystem=golang dh_autoreconf -i -O--builddirectory=_build -O--buildsystem=golang dh_auto_configure -i -O--builddirectory=_build -O--buildsystem=golang dh_auto_build -i -O--builddirectory=_build -O--buildsystem=golang cd _build && go install -gcflags=all=\"-trimpath=/<>/_build/src\" -asmflags=all=\"-trimpath=/<>/_build/src\" -v -p 4 Can't exec "go": No such file or directory at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 484. dh_auto_build: cd _build && go install -gcflags=all=\"-trimpath=/<>/_build/src\" -asmflags=all=\"-trimpath=/<>/_build/src\" -v -p 4 failed to execute: No child processes dh_auto_build: cd _build && go install -gcflags=all=\"-trimpath=/<>/_build/src\" -asmflags=all=\"-trimpath=/<>/_build/src\" -v -p 4 returned exit code 255 make: *** [debian/rules:4: binary-indep] Error 255 signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: panicparse Source-Version: 1.3.0-3 We believe that the bug you reported is fixed in the latest version of panicparse, 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 951...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Shengjing Zhu (supplier of updated panicparse 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: Thu, 13 Feb 2020 17:49:38 +0800 Source: panicparse Architecture: source Version: 1.3.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Shengjing Zhu Closes: 951249 Changes: panicparse (1.3.0-3) unstable; urgency=medium . * Team upload. * Fix Build-Depends on arch:all (Closes: #951249) * Update Standards-Version to 4.5.0 (no changes) Checksums-Sha1: 16510fa4a59675e59c468c07f2a8da04f5106bb4 1686 panicparse_1.3.0-3.dsc 145c4903e97b65c00af7326a21a80e2e27fb098b 2660 panicparse_1.3.0-3.debian.tar.xz c8f947359dd0928901ab9e078a6b7ebb5db9b761 5690 panicparse_1.3.0-3_amd64.buildinfo Checksums-Sha256: 4c0be00d14f50fcef1509f7479cae52ec0ab8645e917b8a7dbe30b3af3da9b0f 1686
Bug#950535: [pkg-netfilter-team] Bug#950535: iptables-restore segfaults on nat table
Hi Alberto, Am 13.02.20 um 10:11 schrieb Alberto Molina Coballes: > I don't understand the rule "-F PREROUTING" after a "-A ..." one. It > seems that the segfault happens in this specific case (it's a bug of > course, but not a bug with grave severity). I choose the grave severity because the bug makes a reload of ufw fail and then the firewall is off ! Christoph signature.asc Description: OpenPGP digital signature
Bug#950535: [pkg-netfilter-team] Bug#950535: iptables-restore segfaults on nat table
Hil Alberto, Am 13.02.20 um 10:11 schrieb Alberto Molina Coballes: > > Is this ruleset a real one obtained from ufw? I ask because the next one > doesn't result in segfault: > > *nat > -F PREROUTING > -F POSTROUTING > -A PREROUTING -i eth0 -p tcp --dport 22 -j REDIRECT --to-ports 1194 > COMMIT > > I don't understand the rule "-F PREROUTING" after a "-A ..." one. It > seems that the segfault happens in this specific case (it's a bug of > course, but not a bug with grave severity). Actually I stripped it down to these lines, because this is the minimum set of rules which makes it crash. In my UFW before.rules files I have several PREROUTING and POSTROUTING rules with a -F before the -A rules block in the nat table. Christoph signature.asc Description: OpenPGP digital signature
Processed: moreinfo
Processing commands for cont...@bugs.debian.org: > tags 933054 + moreinfo Bug #933054 [gnome-disk-utility] gnome-disks: segfault error 4 in libgobject-2.0.so.0.5800.3 Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 933054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933054 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#948780: yelp: FTBFS: Validation of files failed
Hi, A possible workaround for yelp FTBFS could be to add the --disable-appstream-util configure flag. This disables the validation and hopefully the parser is more relaxed during runtime and properly handles the missing field (as they where not required in the past). (Ofcourse a proper fix of adding them would be better though...) Regards, Andreas Henriksson
Bug#951249: marked as pending in panicparse
Control: tag -1 pending Hello, Bug #951249 in panicparse reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/go-team/packages/panicparse/commit/b6486f2513695fc94c6d4352f1b81f29ab80cf34 Fix Build-Depends on arch:all (Closes: #951249) (this message was generated automatically) -- Greetings https://bugs.debian.org/951249
Processed: Bug#951249 marked as pending in panicparse
Processing control commands: > tag -1 pending Bug #951249 [src:panicparse] panicparse: FTBFS on arch:all Added tag(s) pending. -- 951249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951249 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#951249: panicparse: FTBFS on arch:all
Hi Shengjing, On 13-02-2020 10:34, Shengjing Zhu wrote: > I probably don't understand what happens. I may not have been the best in describing the situation. > The package to be tested is src:panicparse, and it builds > bin:golang-github-maruel-panicparse-dev and bin:panicparse. The latest version of your package failed to build from source: https://buildd.debian.org/status/package.php?p=panicparse > Now the logs says it can't find golang-github-maruel-panicparse-dev. I believe that that's due to the right version not being available because it wasn't built. > Is there any change in debci/autopkgtest recently? I think such > problem hasn't occurred previously, and the code in autopkgtest-pkg-go > hasn't been changed for a long time. I think the problem is with the FTBFS on arch:all, as the topic of this bug tells you. Paul signature.asc Description: OpenPGP digital signature
Bug#951249: panicparse: FTBFS on arch:all
On Thu, Feb 13, 2020 at 4:33 PM Paul Gevers wrote: > > Source: panicparse > Version: 1.3.0-2 > X-Debbugs-CC: debian...@lists.debian.org > Severity: serious > Tags: ftbfs > User: debian...@lists.debian.org > Usertags: always-fails > > Dear maintainers, > > Your new package panicparse has an autopkgtest, great. However, it fails > because your package fails to build from source on arch:all and hence > the package it test depends on is not available. I copied some of the > output at the bottom of this report. I also included some of the output > of the build log. > > Currently this is blocking the migration to testing [1]. Can you please > investigate the situation and fix it? > > More information about this bug and the reason for filing it can be found on > https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation > > Paul > > [1] https://qa.debian.org/excuses.php?package=panicparse > > https://ci.debian.net/data/autopkgtest/testing/amd64/p/panicparse/4146771/log.gz > I probably don't understand what happens. The package to be tested is src:panicparse, and it builds bin:golang-github-maruel-panicparse-dev and bin:panicparse. Now the logs says it can't find golang-github-maruel-panicparse-dev. Is there any change in debci/autopkgtest recently? I think such problem hasn't occurred previously, and the code in autopkgtest-pkg-go hasn't been changed for a long time. -- Shengjing Zhu
Processed: notfixed 950535 in 1.8.3-2
Processing commands for cont...@bugs.debian.org: > notfixed 950535 1.8.3-2 Bug #950535 [iptables] iptables-restore segfaults on nat table No longer marked as fixed in versions iptables/1.8.3-2. > End of message, stopping processing here. Please contact me if you need assistance. -- 950535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950535 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#951222: scikit-learn breaks python-skbio autopkgtest: skbio.stats.distance._permdisp.permdisp
Hi Andreas, On 13-02-2020 09:31, Andreas Tille wrote: > My observation is that responses to bug reports of scikit-bio github are > not to be expected in a short time frame. Please be aware that if the issue is really with python-skbio, than the way autoremovals work with these kind of bugs against both packages will mean that it's python-skbio that will be removed from testing (as is my intention). So you have time until autoremoval removes your package from testing. Paul signature.asc Description: OpenPGP digital signature
Processed: Re: [pkg-netfilter-team] Bug#950535: iptables-restore segfaults on nat table
Processing control commands: > tag -1 moreinfo Bug #950535 [iptables] iptables-restore segfaults on nat table Added tag(s) moreinfo. -- 950535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950535 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#950535: [pkg-netfilter-team] Bug#950535: iptables-restore segfaults on nat table
Control: tag -1 moreinfo Hi Christoph, Is this ruleset a real one obtained from ufw? I ask because the next one doesn't result in segfault: *nat -F PREROUTING -F POSTROUTING -A PREROUTING -i eth0 -p tcp --dport 22 -j REDIRECT --to-ports 1194 COMMIT I don't understand the rule "-F PREROUTING" after a "-A ..." one. It seems that the segfault happens in this specific case (it's a bug of course, but not a bug with grave severity). After some tests I found this ruleset segfaults with iptables-nft-restore in several iptables releases (1.8.2-4, 1.8.3-2~bpo10+1 and 1.8.4-2) while iptables-legacy-restore executes as expected. Please, provide more info or a general ruleset to inform upstream and/or lower the severity. Thanks for reporting! Alberto
Bug#882919: marked as done (php-text-password FTBFS with phpunit 6.4.4-2)
Your message dated Thu, 13 Feb 2020 09:04:32 + with message-id and subject line Bug#882919: fixed in php-text-password 1.2.1-3 has caused the Debian Bug report #882919, regarding php-text-password FTBFS with phpunit 6.4.4-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.) -- 882919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882919 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: php-text-password Version: 1.2.1-2 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/php-text-password.html ... debian/rules override_dh_auto_test make[1]: Entering directory '/build/1st/php-text-password-1.2.1' cd Text_Password-* && \ phpunit tests PHP Fatal error: Class 'PHPUnit_Framework_TestCase' not found in /build/1st/php-text-password-1.2.1/Text_Password-1.2.1/tests/Text_Password_Test.php on line 48 debian/rules:7: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 255 --- End Message --- --- Begin Message --- Source: php-text-password Source-Version: 1.2.1-3 We believe that the bug you reported is fixed in the latest version of php-text-password, 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 882...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrius Merkys (supplier of updated php-text-password 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: Thu, 13 Feb 2020 03:46:04 -0500 Source: php-text-password Architecture: source Version: 1.2.1-3 Distribution: unstable Urgency: medium Maintainer: Debian PHP PEAR Maintainers Changed-By: Andrius Merkys Closes: 882919 Changes: php-text-password (1.2.1-3) unstable; urgency=medium . * Adding a patch to fix FTBFS with phpunit (Closes: #882919) * Updating Vcs-* tags * Wrapping and sorting * Adding myself to the list of the uploaders and debian/copyright * Bumping debhelper compat level (no changes) * Adding 'Rules-Requiles-Root: no' * Using HTTPS for the format link in debian/copyright Checksums-Sha1: 0ebfe868592619a23cd6e529107d924dc76ca8c5 2150 php-text-password_1.2.1-3.dsc c6bc0edaa552c6d0ddd5392f7c2f3b6e948d35ae 3164 php-text-password_1.2.1-3.debian.tar.xz 281c3d719fb9d21cbf953e4778a0d7e0dfd1571a 8185 php-text-password_1.2.1-3_source.buildinfo Checksums-Sha256: f24b82f001904b28c244a7e5e8a4397040f1d5021a0bb49218af774ab31cf3bf 2150 php-text-password_1.2.1-3.dsc 90f0c22cba288015777bc90d8ec1963a2f4d87fbfcdfd3c2338b5f8616f7e325 3164 php-text-password_1.2.1-3.debian.tar.xz 4625e1bfcd4aa8e5f3460d37c1bb636e71d3677acdc6f46e08d5cbe017406274 8185 php-text-password_1.2.1-3_source.buildinfo Files: a2bcb2132ed57f570f2a955625c8d39e 2150 php optional php-text-password_1.2.1-3.dsc 3e4ee41391f5523aa802ececca0b1cd7 3164 php optional php-text-password_1.2.1-3.debian.tar.xz ad1627d38ed3b53ccd75b49d96b59fdf 8185 php optional php-text-password_1.2.1-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEdyKS9veshfrgQdQe5fQ/nCc08ocFAl5FDUASHG1lcmt5c0Bk ZWJpYW4ub3JnAAoJEOX0P5wnNPKHg+4P/RFoM9sQ9LCDLzsHB1L+fiCd6sFNz2oA DoT3HT9X/a0roopxWqkRMOul28mQZd0Aj+PgkwDbIG6QRh96Zwzh1kxfRGJNBhxl W5jNBpvxFe7tg8Cs4KhzDfebRrLr7bGQ0osZqAe9sRTzU+CJEgB0RuDbNkYZGRa+ ijwGYshCNbfPEdvqRIZIA6rYBKDcLogAs/9t42LKmThydg3UEHkQkH+FwB9hba/2 ZMMAiqqQPJiX8ASOgXLfpzw7ZqDoWaVbIenszgs3rgT3ui9bhNWifMNnFEPAJFob 1GkI0YzXdL1JojBSIdtwf9zCD4N4dB2KVbhiUh2NTeZtaA6VdwF2mh+dZnvtwl9H cPah3RqosvqNpPMYNbtoo5TwKF0z68XVV1B/woTAnExw8of+lZ8MaINEWoSeH0Qa mu3I5fvIMKYNB3jc9Pvg+DKGdWgMjVWZRohVFpobK1DheqzjP3sJAHIXjt7pYGm0 KXb61xgyJs3N5Tgy3a8ORlJOdGSYD9yNNJh4trE8/SEI6a3EdaeAIfVyyvLeRxml 8NuM+wEj5e5o/HiaJR+YeiOg4Od6WtBTuIojs1gq54DztSHWIoPC+k4yhZxwdmSV 4SGj7PF3F3tmoR0SdPHhW4M/hmVcS8Oge4WmL7i84OM/BMr4anqCDP/+Hf6Ds+I/ 4cm8HRRp/b+z =zYpS -END PGP SIGNATURE End Message ---
Bug#950715: marked as done (libgcc1: upgrade from 1:9.2.1-25 to libgcc1 1:10-20200202-1 breaks gcc with gold linker)
Your message dated Thu, 13 Feb 2020 08:52:00 + with message-id <20200213085200.ga401...@espresso.pseudorandom.co.uk> and subject line Re: Bug#950715: libgcc1: upgrade from 1:9.2.1-25 to libgcc1 1:10-20200202-1 breaks gcc with gold linker has caused the Debian Bug report #950715, regarding libgcc1: upgrade from 1:9.2.1-25 to libgcc1 1:10-20200202-1 breaks gcc with gold linker 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.) -- 950715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950715 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgcc1 Version: 1:10-20200202-1 Severity: serious Upgrading libgcc1 to version >= 10 on a system breaks gcc-7, gcc-8 and gcc-9 when using the gold linker, as gcc passes the wrong path to the libgcc_s.so.1 library. All architectures are affected, example on amd64, starting from a bullseye chroot: | $ gcc -fuse-ld=gold -o hello hello.c | $ sudo apt-get install libgcc1 | Reading package lists... Done | Building dependency tree | Reading state information... Done | The following additional packages will be installed: | gcc-10-base libgcc-s1 | The following NEW packages will be installed: | gcc-10-base libgcc-s1 | The following packages will be upgraded: | libgcc1 | 1 upgraded, 2 newly installed, 0 to remove and 87 not upgraded. | Need to get 278 kB of archives. | After this operation, 381 kB of additional disk space will be used. | Do you want to continue? [Y/n] | Get:1 http://localhost:3142/debian sid/main amd64 gcc-10-base amd64 10-20200202-1 [195 kB] | Get:2 http://localhost:3142/debian sid/main amd64 libgcc-s1 amd64 10-20200202-1 [41.6 kB] | Get:3 http://localhost:3142/debian sid/main amd64 libgcc1 amd64 1:10-20200202-1 [41.6 kB] | Fetched 278 kB in 0s (25.7 MB/s) | debconf: delaying package configuration, since apt-utils is not installed | Selecting previously unselected package gcc-10-base:amd64. | (Reading database ... 35349 files and directories currently installed.) | Preparing to unpack .../gcc-10-base_10-20200202-1_amd64.deb ... | Unpacking gcc-10-base:amd64 (10-20200202-1) ... | Setting up gcc-10-base:amd64 (10-20200202-1) ... | Selecting previously unselected package libgcc-s1:amd64. | (Reading database ... 35355 files and directories currently installed.) | Preparing to unpack .../libgcc-s1_10-20200202-1_amd64.deb ... | Unpacking libgcc-s1:amd64 (10-20200202-1) ... | Setting up libgcc-s1:amd64 (10-20200202-1) ... | (Reading database ... 35358 files and directories currently installed.) | Preparing to unpack .../libgcc1_1%3a10-20200202-1_amd64.deb ... | Unpacking libgcc1 (1:10-20200202-1) over (1:9.2.1-25) ... | Setting up libgcc1 (1:10-20200202-1) ... | Processing triggers for ccache (3.7.7-1) ... | Updating symlinks in /usr/lib/ccache ... | Processing triggers for libc-bin (2.29-9) ... | $ gcc -fuse-ld=gold -o hello hello.c | /usr/bin/ld.gold: error: cannot open /usr/lib/gcc/x86_64-linux-gnu/9/libgcc_s.so.1: No such file or directory | /usr/bin/ld.gold: error: cannot open /usr/lib/gcc/x86_64-linux-gnu/9/libgcc_s.so.1: No such file or directory | collect2: error: ld returned 1 exit status | $ In turns this causes many autopktest failures: https://ci.debian.net/data/autopkgtest/testing/amd64/d/deal.ii/4202144/log.gz https://ci.debian.net/data/autopkgtest/testing/amd64/g/ghc/4202362/log.gz https://ci.debian.net/data/autopkgtest/testing/amd64/h/haskell-hgettext/4202485/log.gz https://ci.debian.net/data/autopkgtest/testing/amd64/h/haskell-hopenpgp/4202487/log.gz libgcc-s1 probably misses a Break: against the older gcc-X versions. --- End Message --- --- Begin Message --- Version: 1:10-20200211-1 On Wed, 05 Feb 2020 at 11:16:51 +0100, Aurelien Jarno wrote: > Upgrading libgcc1 to version >= 10 on a system breaks gcc-7, gcc-8 and > gcc-9 when using the gold linker, as gcc passes the wrong path to the > libgcc_s.so.1 library. This appears to have been fixed in unstable, most likely by "libgcc-sN: Move library back to /lib from /usr/lib". Starting from a bullseye environment: root@host:~# apt-get install gcc-7 gcc-8 gcc-9 ... root@host:~# for x in 7 8 9; do gcc-$x -fuse-ld=gold -ohello hello.c; done root@host:~# for x in 7 8 9; do gcc-$x -ohello hello.c; done root@host:~# apt install libgcc1 Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: gcc-10-base libgcc-s1 The following NEW packages will be installed: gcc-10-base libgcc-s1 The following packages will be upgraded: libgcc1 ... root@host:~# for x in 7 8 9; do gcc-$x
Bug#950545: marked as done (FTBFS against opencv 4.2.0)
Your message dated Thu, 13 Feb 2020 08:42:21 +
with message-id
and subject line Bug#950545: fixed in eviacam 2.1.4-2
has caused the Debian Bug report #950545,
regarding FTBFS against opencv 4.2.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
950545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950545
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eviacam
Version: 2.1.4-1
Severity: serious
Dear maintainer,
eviacam FTBFS against the latest version of OpenCV:
https://buildd.debian.org/status/package.php?p=eviacam=sid
https://buildd.debian.org/status/fetch.php?pkg=eviacam=amd64=2.1.4-1%2Bb1=1580642132=0
which looks due an API change at the first glance.
crvnormroi.cpp:449:35: error: cannot convert ‘cv::Size’ {aka ‘cv::Size_’}
to ‘const CvSize&’
449 | SetP1ResizeInteger (pImg->GetSize(), x, y);
| ~^~
| |
| cv::Size {aka cv::Size_}
crvnormroi.cpp:359:50: note: initializing argument 1 of ‘void
CNormROI::SetP1ResizeInteger(const CvSize&, int, int)’
359 | void CNormROI::SetP1ResizeInteger (const CvSize& size, const int x,
const int y)
|~~^~~~
crvnormroi.cpp: In member function ‘void CNormROI::SetP1MoveImg(const
CIplImage*, int, int)’:
crvnormroi.cpp:457:33: error: cannot convert ‘cv::Size’ {aka ‘cv::Size_’}
to ‘const CvSize&’
457 | SetP1MoveInteger (pImg->GetSize(), x, y);
|~^~
| |
| cv::Size {aka cv::Size_}
crvnormroi.cpp:369:48: note: initializing argument 1 of ‘void
CNormROI::SetP1MoveInteger(const CvSize&, int, int)’
369 | void CNormROI::SetP1MoveInteger (const CvSize& size, const int x, const
int y)
| ~~^~~~
crvnormroi.cpp: In member function ‘void CNormROI::SetP2ResizeImg(const
CIplImage*, int, int)’:
crvnormroi.cpp:465:35: error: cannot convert ‘cv::Size’ {aka ‘cv::Size_’}
to ‘const CvSize&’
465 | SetP2ResizeInteger (pImg->GetSize(), x, y);
| ~^~
| |
| cv::Size {aka cv::Size_}
crvnormroi.cpp:379:50: note: initializing argument 1 of ‘void
CNormROI::SetP2ResizeInteger(const CvSize&, int, int)’
379 | void CNormROI::SetP2ResizeInteger (const CvSize& size, const int x,
const int y)
|~~^~~~
crvnormroi.cpp: In member function ‘void CNormROI::SetCenterImg(const
CIplImage*, int, int)’:
crvnormroi.cpp:473:33: error: cannot convert ‘cv::Size’ {aka ‘cv::Size_’}
to ‘const CvSize&’
473 | SetCenterInteger (pImg->GetSize(), x, y);
|~^~
| |
| cv::Size {aka cv::Size_}
crvnormroi.cpp:389:48: note: initializing argument 1 of ‘void
CNormROI::SetCenterInteger(const CvSize&, int, int)’
389 | void CNormROI::SetCenterInteger (const CvSize& size, const int x, const
int y)
| ~~^~~~
crvnormroi.cpp: In member function ‘void CNormROI::GetCenterImg(const
CIplImage*, int&, int&)’:
crvnormroi.cpp:481:33: error: cannot convert ‘cv::Size’ {aka ‘cv::Size_’}
to ‘const CvSize&’
481 | GetCenterInteger (pImg->GetSize(), x, y);
|~^~
| |
| cv::Size {aka cv::Size_}
crvnormroi.cpp:398:48: note: initializing argument 1 of ‘void
CNormROI::GetCenterInteger(const CvSize&, int&, int&)’
398 | void CNormROI::GetCenterInteger (const CvSize& size, int& x, int& y)
| ~~^~~~
crvnormroi.cpp: In member function ‘void CNormROI::SetSizeImg(const CIplImage*,
int, int)’:
crvnormroi.cpp:489:31: error: cannot convert ‘cv::Size’ {aka ‘cv::Size_’}
to ‘const CvSize&’
489 | SetSizeInteger (pImg->GetSize(), width, height);
| ~^~
| |
| cv::Size {aka cv::Size_}
crvnormroi.cpp:408:46: note: initializing argument 1 of ‘void
CNormROI::SetSizeInteger(const CvSize&, int, int)’
408 | void CNormROI::SetSizeInteger (const CvSize& size, const int width,
const int height)
|~~^~~~
crvnormroi.cpp: In
Bug#951249: panicparse: FTBFS on arch:all
Source: panicparse Version: 1.3.0-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious Tags: ftbfs User: debian...@lists.debian.org Usertags: always-fails Dear maintainers, Your new package panicparse has an autopkgtest, great. However, it fails because your package fails to build from source on arch:all and hence the package it test depends on is not available. I copied some of the output at the bottom of this report. I also included some of the output of the build log. Currently this is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=panicparse https://ci.debian.net/data/autopkgtest/testing/amd64/p/panicparse/4146771/log.gz autopkgtest: WARNING: package golang-github-maruel-panicparse-dev is not installed though it should be autopkgtest: WARNING: package panicparse is not installed though it should be autopkgtest: WARNING: Test dependencies are unsatisfiable - calling apt install on test deps directly for further data about failing dependencies in test logs Tail of log for panicparse on all: dh clean --builddirectory=_build --buildsystem=golang --with=golang dh_auto_clean -O--builddirectory=_build -O--buildsystem=golang dh_autoreconf_clean -O--builddirectory=_build -O--buildsystem=golang dh_clean -O--builddirectory=_build -O--buildsystem=golang debian/rules binary-indep dh binary-indep --builddirectory=_build --buildsystem=golang --with=golang dh_update_autotools_config -i -O--builddirectory=_build -O--buildsystem=golang dh_autoreconf -i -O--builddirectory=_build -O--buildsystem=golang dh_auto_configure -i -O--builddirectory=_build -O--buildsystem=golang dh_auto_build -i -O--builddirectory=_build -O--buildsystem=golang cd _build && go install -gcflags=all=\"-trimpath=/<>/_build/src\" -asmflags=all=\"-trimpath=/<>/_build/src\" -v -p 4 Can't exec "go": No such file or directory at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 484. dh_auto_build: cd _build && go install -gcflags=all=\"-trimpath=/<>/_build/src\" -asmflags=all=\"-trimpath=/<>/_build/src\" -v -p 4 failed to execute: No child processes dh_auto_build: cd _build && go install -gcflags=all=\"-trimpath=/<>/_build/src\" -asmflags=all=\"-trimpath=/<>/_build/src\" -v -p 4 returned exit code 255 make: *** [debian/rules:4: binary-indep] Error 255 signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#951222: scikit-learn breaks python-skbio autopkgtest: skbio.stats.distance._permdisp.permdisp
Processing control commands: > tags -1 upstream Bug #951222 [src:scikit-learn, src:python-skbio] scikit-learn breaks python-skbio autopkgtest: skbio.stats.distance._permdisp.permdisp Added tag(s) upstream. > forwarded -1 https://github.com/biocore/scikit-bio/issues/1693 Bug #951222 [src:scikit-learn, src:python-skbio] scikit-learn breaks python-skbio autopkgtest: skbio.stats.distance._permdisp.permdisp Set Bug forwarded-to-address to 'https://github.com/biocore/scikit-bio/issues/1693'. -- 951222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951222 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#951222: scikit-learn breaks python-skbio autopkgtest: skbio.stats.distance._permdisp.permdisp
Control: tags -1 upstream Control: forwarded -1 https://github.com/biocore/scikit-bio/issues/1693 > 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? I admit I'm not sure what package needs to be fixed but in any case I've forwarded the issue to python-skbio upstream to make them aware of this. My observation is that responses to bug reports of scikit-bio github are not to be expected in a short time frame. I'm also not sure whether the upstream tag / forward for python-skbio might hide the issue from scikit-learn maintainers view - I have no idea where the issue really needs to be fixed. Kind regards Andreas. -- http://fam-tille.de
Bug#951248: origami-pdf: autopkgtest failure: output to stderr: warning: constant ::Bignum is deprecated
Source: origami-pdf Version: 2.0.0-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: always-fails Dear maintainers, Your package was removed some time ago due to bug 914333, which by now is fixed by src:netperfmeter. However, you package fails to migrate back to testing because the autopkgtest fails. I copied some of the output at the bottom of this report. 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=origami-pdf https://ci.debian.net/data/autopkgtest/testing/amd64/o/origami-pdf/3457321/log.gz autopkgtest [08:58:27]: test command1: [--- /usr/lib/ruby/vendor_ruby/origami/object.rb:28: warning: constant ::Bignum is deprecated /usr/lib/ruby/vendor_ruby/origami/object.rb:34: warning: constant ::Fixnum is deprecated /usr/lib/ruby/vendor_ruby/origami/numeric.rb:104: warning: constant ::Bignum is deprecated [0;36;49m[2019-11-20 08:58:29 +][0m [0;32;49mPDFcop is running on target `debian/tests/signed.pdf', policy = `standard'[0m [0;36;49m[2019-11-20 08:58:29 +][0m [0;35;49m File size: 5812 bytes[0m [0;36;49m[2019-11-20 08:58:29 +][0m [0;35;49m MD5: 8e8344cef61ac3179030b0cccd1df008[0m [0;36;49m[2019-11-20 08:58:29 +][0m [0;33;49m> Inspecting document structure...[0m [0;36;49m[2019-11-20 08:58:29 +][0m [0;33;49m> Inspecting document catalog...[0m [0;36;49m[2019-11-20 08:58:29 +][0m [0;39;49m . AcroForm = YES[0m [0;36;49m[2019-11-20 08:58:29 +][0m [0;33;49m> Inspecting JavaScript names directory...[0m [0;36;49m[2019-11-20 08:58:29 +][0m [0;33;49m> Inspecting attachment names directory...[0m [0;36;49m[2019-11-20 08:58:29 +][0m [0;33;49m> Inspecting document pages...[0m [0;36;49m[2019-11-20 08:58:29 +][0m [0;39;49m >> Inspecting page...[0m [0;36;49m[2019-11-20 08:58:29 +][0m [0;33;49m> Inspecting document streams...[0m [0;36;49m[2019-11-20 08:58:29 +][0m [0;32;49mDocument accepted by policy `standard'.[0m autopkgtest [08:58:29]: test command1: ---] autopkgtest [08:58:29]: test command1: - - - - - - - - - - results - - - - - - - - - - command1 FAIL stderr: /usr/lib/ruby/vendor_ruby/origami/object.rb:28: warning: constant ::Bignum is deprecated signature.asc Description: OpenPGP digital signature
Bug#951247: html2canvas: build-depends on removed package libjs-mocha
Source: html2canvas
Version: 0.5.0~beta4+ds1-2
Severity: serious
User: trei...@debian.org
Usertags: edos-uninstallable
Hi,
html2canvas build-depends on libjs-mocha which only exists in
old{old}stable.
-Ralf.
Bug#951246: genetic: build-depends on non-existing package
Source: genetic Version: 0.1.1b+git20170527.98255cb-1 Severity: serious User: trei...@debian.org Usertags: edos-uninstallable Hi, genetic build-depends on python3-multiprocess, which does not exist in the archive. -Ralf.
Processed: kazoo: autopkgtest regression
Processing control commands: > severity -1 serious Bug #933631 [src:kazoo] kazoo: autopkgtest regression Severity set to 'serious' from 'important' -- 933631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933631 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
