Bug#919356: Licensing of include/linux/hash.h
On Mon, Feb 11, 2019 at 12:08:32AM +0100, Kristian Fiskerstrand wrote: > On 1/23/19 9:50 AM, Domenico Andreoli wrote: > > Ben Finney writes: > >> Domenico Andreoli writes: [...] > >>> the only knot left is now the license of hash.h > >>> > >>> This file is also present in the kernel [0] with an updated copyright > >>> but still without license. [...] > >> To know that work (that file) is free software, we need a clear grant of > >> some specific license, for that work. > >> > >> If the work is not free, it would be incorrect to have the work in Debian. > > > > Is it possible that for the kernel it is instead correct because it is, > > as whole, covered by its COPYING? > > > >> Alternatives, for complying with the Debian Free Software Guidelines with > >> this package, include: > >> > >> * Find a credible grant of license under some GPL-compatible free > >> license to that exact file. Document that explicit grant in the Debian > >> package. This demonstrates the work is DFSG-free. > >> > >> * Convince ???dwarves-dfsg??? upstream to replace that file with a > >> different > >> implementation (I don't know whether such an implementation exists) > >> under a license compatible with the same version of GNU GPL. Document > >> that explicit grant in the Debian package. This demonstrates the > >> modified work is DFSG-free. > >> > >> * Replace that file in Debian only, with a different implementation as > >> above. Document that explicit grant in the Debian package. This > >> demonstrates the modified Debian package is DFSG-free. > >> > >> * Move the work to the ???non-free??? area. > >> > >> * Remove the work altogether. > >> > >> Those are in descending order of (my recommended) preference. [...] > It was [pointed out] by one of our license group that [hash.h] is the > same that has a GPL-2+ in [fio] which has a signed-off-by. > > References: > [pointed out] > https://bugs.gentoo.org/677586#c1 > > [hash.h] > https://git.kernel.org/pub/scm/linux/kernel/git/axboe/fio.git/commit/hash.h?id=bdc7211e190482f0c17c109a0d90834a6611be1c Yes, the Signed-off-by is from Jens Axboe (in CC) but he's not the original author, I guess he just copied the file as Arnaldo did. The file he committed has not any reference to the license. > [fio] > https://metadata.ftp-master.debian.org/changelogs/main/f/fio/fio_3.12-2_copyright I'm afraid that this entry in wrong. I'll seek confirmation with Martin Steigerwald. Regards, Domenico -- 3B10 0CA1 8674 ACBA B4FE FCD2 CE5B CF17 9960 DE13 signature.asc Description: PGP signature
Bug#891434: grub-efi: System fails to boot after "No space left on device" on EFI variable storage
On Fri, 14 Dec 2018 10:22:49 +0100 Ralf Jung wrote: > Hi, > > > Fixing this does seem like it would be a good idea for general > > robustness against dodgy firmware (this is not the first iteration of > > problems along these lines). It would take some development work, but > > hopefully not too much. > > > > Things that GRUB can't do, as far as I can tell: > > > > * I don't think there's a way for GRUB to check whether it will be > >possible to recreate a boot entry later; as I understand it, that > >depends on various low-level details, including firmware-specific > >quirks. > > > > * Even detecting that nothing changed would require cooperation from > >efibootmgr, since the encoding of the EFI variable is an > >implementation detail there (so we can't just read it out and > >compare), and efibootmgr doesn't expose a way for GRUB to say "set > >this configuration, but only if it's different from what's already > >there". > > > > However, I think GRUB can at least manage to delete all but one entry > > from the same distributor rather than all of them, and if it finds one > > remaining entry then it can modify that rather than writing a brand new > > variable. As I understand it, that would probably be enough to fix this > > bug? > > Assuming that modification works even when the variable storage is (close to) > full, then yes, that would at least keep the device bootable which would be a > big improvement. > > Kind regards, > Ralf > > Hi Colin, Thanks for proposing this solution. :) I also think it would be a good solution for now that will hopefully avoid most of these errors. :) Thanks, ~Niels
Bug#772795: marked as done (grub installation fails on a fakeraid/sataraid/dmraid system)
Your message dated Mon, 11 Feb 2019 07:04:00 + with message-id <89f07d90-3b2d-f52b-f20b-0b3a6a5a5...@thykier.net> and subject line Re: Bug#772795: grub installation fails on a fakeraid/sataraid/dmraid system has caused the Debian Bug report #772795, regarding grub installation fails on a fakeraid/sataraid/dmraid system 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.) -- 772795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772795 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: grub-pc version: 1.99-27+deb7u2 severity: critical I had to spend a lot of time researching on the internet to finally find this https://wiki.debian.org/DebianInstaller/SataRaid and install grub manually. This was wheezy 7.7.0 DVD 1. I don't know if debian installer can detect a sataraid system and load dm-raid module manually (I'll open another bug for that). But grub installation should not fail when dmraid=true. Instead of suggesting to install on /dev/mapper grub should choose the correct devise like /dev/mapper/isw_bdfjhfbiei_Volume1 when dmraid=true is present in the kernel command line. Server model is Dell PowerEdge T20 and SATA controller is Intel C226 chipset. signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Version: 2.02~beta3-5 On Fri, 17 Feb 2017 03:00:30 GMT "Pirate Praveen" wrote: > > > Niels Thykier wrote: > > On Sun, 16 Aug 2015 08:45:37 +0200 Felix Zielcke > > wrote:>> Am Donnerstag, den 11.12.2014, 12:49 +0530 schrieb Pirate > > Praveen:>>> package: grub-pc > >>> version: 1.99-27+deb7u2 > >>> severity: critical > >>> > >>> I had to spend a lot of time researching on the internet to finally > >>> find > >>> this https://wiki.debian.org/DebianInstaller/SataRaid and install > >>> grub > >>> manually. This was wheezy 7.7.0 DVD 1. > >>> > >>> I don't know if debian installer can detect a sataraid system and > >>> load > >>> dm-raid module manually (I'll open another bug for that). But grub > >>> installation should not fail when dmraid=true. > >>> > >>> Instead of suggesting to install on /dev/mapper grub should choose > >>> the > >>> correct devise like /dev/mapper/isw_bdfjhfbiei_Volume1 when > >>> dmraid=true > >>> is present in the kernel command line. > >>> > >>> Server model is Dell PowerEdge T20 and SATA controller is Intel C226 > >>> chipset.>> Is this still a problem with jessie or got it solved?> Hi > >>> Pirate, > > > > Did you see Felix's question? > > I don't have access to that machine any more to confirm (it was a customer's > machine). > > Thanks, > > ~Niels > > Hi, I am taking the liberty of closing this bug since no one has followed up and confirmed it is still a problem since jessie. If you can reproduce it after jessie, please re-open the bug. Thanks, ~Niels--- End Message ---
Processed: closing 752381
Processing commands for cont...@bugs.debian.org: > close 752381 Bug #752381 [src:grub2] initramfs-tools: does not activate logical volume before trying to mount root filesystem on LVM Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 752381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752381 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#895317: marked as done (node-commander: FTBFS unreliable timing)
Your message dated Mon, 11 Feb 2019 06:53:22 + with message-id and subject line Bug#895317: fixed in node-commander 2.12.2-2 has caused the Debian Bug report #895317, regarding node-commander: FTBFS unreliable timing 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.) -- 895317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895317 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-commander Version: 2.12.2-1 Severity: serious Hi Maintainer Since the upload of nodejs 8.9.3, node-commander has FTBFS [1] with errors similar to the following: /usr/lib/nodejs/should/lib/assertion.js:72 throw new AssertionError(params); ^ AssertionError: expected '' to be 'SIGHUP\n' at Assertion.fail (/usr/lib/nodejs/should/lib/assertion.js:92:17) at Assertion.value (/usr/lib/nodejs/should/lib/assertion.js:164:19) at Timeout._onTimeout (/build/1st/node-commander-2.12.2/test/test.command.executableSubcommand.signals.hup.js:19:19) at ontimeout (timers.js:475:11) at tryOnTimeout (timers.js:310:5) at Timer.listOnTimeout (timers.js:270:5) make[1]: *** [debian/rules:15: override_dh_auto_test] Error 1 I believe this is similar to the unreliable timing in tests being discussed in #853035. Regards Graham [1] https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-commander.html --- End Message --- --- Begin Message --- Source: node-commander Source-Version: 2.12.2-2 We believe that the bug you reported is fixed in the latest version of node-commander, 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 895...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated node-commander package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 11 Feb 2019 07:25:48 +0100 Source: node-commander Binary: node-commander Architecture: source Version: 2.12.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 895317 Description: node-commander - Complete solution for Node.js command-line interfaces Changes: node-commander (2.12.2-2) unstable; urgency=medium . * Add upstream/metadata * Bump debhelper compatibility level to 11 * Declare compliance with policy 4.3.0 * Update VCS fields to salsa * Fix d/copyright format url * Add myself to uploaders * Increase tests timeouts (Closes: #895317) * Switch tests to pkg-js-tools Checksums-Sha1: e4d3baedf6fd693e7679b19b9fc8f79357625662 2133 node-commander_2.12.2-2.dsc c3a606ec9343f396626f34a916607a8e2ed99752 3660 node-commander_2.12.2-2.debian.tar.xz Checksums-Sha256: 78408238a74f064eee3dae0d3a9048d01add186366ac78861b73624a1ee1bcd1 2133 node-commander_2.12.2-2.dsc c6a294a935d16eddc241b99369345e24193d642e0792cacbb1eb96336137a02e 3660 node-commander_2.12.2-2.debian.tar.xz Files: 694e78675bd0284200e4886b8ef3a729 2133 javascript optional node-commander_2.12.2-2.dsc cd56755a3dcd7e55bfa6574e3d678ccc 3660 javascript optional node-commander_2.12.2-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAlxhF1QACgkQ9tdMp8mZ 7unnug//Wa4nfvMLXcl9t0RanWZHpXrtJJiqVtsCCH7dVbKRGOnq0V48ZpRBPEXu lDNqbWiPbafghc+7fnvu5nFFocrzlqAxGy1kX3MLHNvBOoV4M3vIpKEkfJHAOWN0 uv/FvqgkpSdlKLm4Ms5nE6uivIjOuzcYXdj8r6kRtP8+YeLt4xOy6UZIbhzHqvzP pqPcqdRscbB2GJFbmzljntIYPYk8M41D6LKz+9AdZvl0eURwKLskLpifUlISVqzg L8dmoJwwWz3CuvRhiR4rpMVbTuW6Q15p5yOUsYTXoFIbDkPJPdxrH6S5vYW+iMWE Y9aV52FZg42Sri/wHUnyx/LOZl1LdVId3WH5/ZpdmBeUFBT/oKkzZozpiys9w7R7 mpGvoTPr/2yEWGbhhF2TjwsnSJRqbpTasJ0hPB1JuSlEkgsM/1se3R3g+0Klelqo j1LOqCBddbu59uvdkSNJ0eGAV22h3DJfH0sMBmzrBSHfqmuybw4s5dtFfJmd8FL2 jjQRnQLDAcEgkeAzAnEkqqpCoB1nEldMB2NVveyd3RkO4hzUimQupXlESklXDmAN CaUS/RdjT6Wg6vRc1DeB4SSOsPofCoK+XfF4dmRJieI490qXkvPOQbwnOG6OV07J Ml8stIuWFZrMu60z2GIbRXx61eT1mv3pLIjqATkmoH9MGIhJj6Y= =K/DQ -END PGP SIGNATURE End Message ---
Bug#921995: marked as done (kauth: Insecure handling of arguments in helpers)
Your message dated Mon, 11 Feb 2019 06:37:36 + with message-id and subject line Bug#921995: fixed in kauth 5.54.0-2 has caused the Debian Bug report #921995, regarding kauth: Insecure handling of arguments in helpers 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.) -- 921995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921995 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:kauth Version: 5.28.0-2 Severity: grave Tags: security upstream patch Justification: user security hole See the KDE announce list [1]. It includes reference to a fix [2]. This is CVE-2019-7443. Scott K [1] https://mail.kde.org/pipermail/kde-announce/2019-February/11.html [2] https://cgit.kde.org/kauth.git/commit/?id=fc70fb0161c1b9144d26389434d34dd135cd3f4a --- End Message --- --- Begin Message --- Source: kauth Source-Version: 5.54.0-2 We believe that the bug you reported is fixed in the latest version of kauth, 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 921...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Scott Kitterman (supplier of updated kauth package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 10 Feb 2019 23:22:23 -0500 Source: kauth Architecture: source Version: 5.54.0-2 Distribution: unstable Urgency: high Maintainer: Debian/Kubuntu Qt/KDE Maintainers Changed-By: Scott Kitterman Closes: 921995 Changes: kauth (5.54.0-2) unstable; urgency=high . * Team upload. * SECURITY UPDATE: * References: - CVE-2019-7443 - https://mail.kde.org/pipermail/kde-announce/2019-February/11.html * Remove support for passing gui QVariants to KAuth helpers (Closes: #921995) Checksums-Sha1: 1b0222977fc2405ed2e414a253766c67275424b0 2545 kauth_5.54.0-2.dsc 5e1cc906491572111c913f12ab7047931dc3bddd 12128 kauth_5.54.0-2.debian.tar.xz 3b6d1b318e08a9c0a1ff65c8b0690431cbe73877 12199 kauth_5.54.0-2_source.buildinfo Checksums-Sha256: 3f0fb3ba0795bb040d7659adc773c06617304122cc3e5578a18f0ef5ac1eb2fb 2545 kauth_5.54.0-2.dsc 06016fdc8720f0212d7f94cfe2de93904b4efcabcfcd1eab943ac0fc9ee0d4f2 12128 kauth_5.54.0-2.debian.tar.xz 68742839ab23453a6882a6e55073b69e20dc1d720b854277b9d5b404dd87a38c 12199 kauth_5.54.0-2_source.buildinfo Files: e91296b4ee2f62e15ce463dc56527bca 2545 libs optional kauth_5.54.0-2.dsc 2d4f3351089e78c37fbfa47e76abfef3 12128 libs optional kauth_5.54.0-2.debian.tar.xz 17f8873cd58324698410003bb16a6e6d 12199 libs optional kauth_5.54.0-2_source.buildinfo -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJcYRKxAAoJEHjX3vua1Zrxpd0P/1tsLVq3D0lWRnwE3SNsKk6b nlU/KAm+fRD5+NochgK0ZCFFwprONnd8BbHTlW4fXE4sH9qsj3jzmbXHlmSGhhpv k36seLMAU3URjUDoAcKzzdPC+703h+tNSvHYI7E1nGwrMBBBQMeprQPV+XaI8BRn W3UX9JIuVCCHsOuRmPgh8Dtarkacryp0tC5B+rL8g/Oa02f2FRN3+cy3JUwL+as3 oObonbWLSwjc9lR/BDCKiToqTuDvPnJSFnHrkt+w3LT3V9zzB8NRG4GOVAwNQ0WN ZkxAyU0e2iFCUug8TnRzbk7wUHv5zGMfcTz2v3DXRL5ngTAdPDTxuoEMwC8T26LJ fpHZftt+mEdbBw+D0CoU8hFNAmpu6cdoLXSFQtuzopAzI1P0T1lySIaYZnfwOwkw VGUNG/HCNwiJJJf5QO0o5ds6qJimXx5zPxI/QxLpXR7zKjy3H0FqxDN/0VutLJtk s9jj0dUErYtm9Uo/ImlipAEKdsA0Jodq9+ufY5p/1Yv6Ik4IuEbYWmAqq9FndqDP czu/JOZt1ulFNYLP+OddJawEbNluaQzP9yGWV5FXk8Y6TlY4ApCjhY3lKKxUQgqu 73eXOG6CnjbPW3VZIPsK9TpXBpK17Pvek0x+fBdw49DzYttIqtK31mIBKu6OeLMS K5SuwooqIVukUiex0P4j =EGhd -END PGP SIGNATURE End Message ---
Bug#921854: Bug #921854 in gcc-arm-none-eabi marked as pending
Control: tag -1 pending Hello, Bug #921854 in gcc-arm-none-eabi reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/gcc-arm-none-eabi/commit/61b428f901cbe07acb2c9bd0ddfe2d5ac0179240 Remove b-dependencies on libisl-0.18-dev and libcloog-isl-dev Closes: #921854 (this message was generated automatically) -- Greetings https://bugs.debian.org/921854
Processed: Bug #895317 in node-commander marked as pending
Processing control commands: > tag -1 pending Bug #895317 [src:node-commander] node-commander: FTBFS unreliable timing Added tag(s) pending. -- 895317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895317 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#895317: Bug #895317 in node-commander marked as pending
Control: tag -1 pending Hello, Bug #895317 in node-commander 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-commander/commit/69fba042e837ddcde10974e247997c2752081e9a Increase tests timeouts Closes: #895317 (this message was generated automatically) -- Greetings https://bugs.debian.org/895317
Processed: Bug #921854 in gcc-arm-none-eabi marked as pending
Processing control commands: > tag -1 pending Bug #921854 [src:gcc-arm-none-eabi] outdated b-d's on libisl-0.18-dev and libcloog-isl-dev, to be removed for buster Added tag(s) pending. -- 921854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921854 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921995: Bug #921995 in kauth marked as pending
Control: tag -1 pending Hello, Bug #921995 in kauth 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/qt-kde-team/kde/kauth/commit/7c3a1fc6f2a7590fe7a12db0035e89ce1c29301b * Remove support for passing gui QVariants to KAuth helpers (Closes: #921995) * SECURITY UPDATE: * References: - CVE-2019-7443 - https://mail.kde.org/pipermail/kde-announce/2019-February/11.html * Remove support for passing gui QVariants to KAuth helpers (Closes: #921995) (this message was generated automatically) -- Greetings https://bugs.debian.org/921995
Processed: Bug #921995 in kauth marked as pending
Processing control commands: > tag -1 pending Bug #921995 [src:kauth] kauth: Insecure handling of arguments in helpers Added tag(s) pending. -- 921995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921995 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921797: marked as done (node-lru-cache: FTBFS (failing tests))
Your message dated Mon, 11 Feb 2019 06:04:28 + with message-id and subject line Bug#921797: fixed in node-lru-cache 5.1.1-4 has caused the Debian Bug report #921797, regarding node-lru-cache: FTBFS (failing tests) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 921797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921797 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:node-lru-cache Version: 5.1.1-3 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep dh_update_autotools_config -i dh_autoreconf -i debian/rules override_dh_auto_test make[1]: Entering directory '/<>' tap -R spec test/*.js test/basic.js basic â should be equal â should be equal [... snipped ...] â should be equal â should be equal â should be equal â should be equal â should be equal â should be equal â should be equal â should be equal â should be equal â should be equal â should be equal dumpLru â type is Yallist 650 passing (14s) 1 failing 1) test/foreach.js expires should be equal: Error: should be equal + expected - actual -3 +5 at Timeout._onTimeout (test/foreach.js:125:7) make[1]: *** [debian/rules:12: override_dh_auto_test] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:8: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) The build was made in my autobuilder with "dpkg-buildpackage -A" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-lru-cache.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks. --- End Message --- --- Begin Message --- Source: node-lru-cache Source-Version: 5.1.1-4 We believe that the bug you reported is fixed in the latest version of node-lru-cache, 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 921...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated node-lru-cache package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 11 Feb 2019 06:42:08 +0100 Source: node-lru-cache Binary: node-lru-cache Architecture: source Version: 5.1.1-4 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 921797 Description: node-lru-cache - least-recently-used cache object for Node.js Changes: node-lru-cache (5.1.1-4) unstable; urgency=medium . * Team upload * Add upstream/metadata * Switch tests to pkg-js-tools * Increase tests timetouts (Closes: #921797) Checksums-Sha1: 94c16b90f5c145217cd616b0d2c7c8a46afa4685 2082 node-lru-cache_5.1.1-4.dsc ad262fe693d29e5912fc615f06a12315372dee8a 3384 node-lru-cache_5.1.1-4.debian.tar.xz Checksums-Sha256: 41290d2fe1d8da5d556c2647b3e8f8c55a7ebf1e2a66935d149f5351ea9e 2082 node-lru-cache_5.1.1-4.dsc d2546194f8dba913a28834f937b7dc26c16f0061549d63819c7aac7e61577987 3384 node-lru-cache_5.1.1-4.debian.tar.xz Files: e7127ad078ca7c52a74cd0153d9dc9a4 2082 javascript optional node-lru-cache_5.1.1-4.dsc 2608231d1be196c5c74203e158efd758 3384 javascript optional node-lru-cache_5.1.1-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAlxhDC4ACgkQ9tdMp8mZ 7ulZyw//TjGNO/LzpSCQPcmFrSs7oNZn5oy/AORE8cUeJeOGA8W3nEm2d+8zePOe zgZX//gXogJlz3V75hhS4b4HtACR9crpU0U/xp0aDErAg0qBuou3aBX6Cp/3lmdY T2Dm3K5t6TQ4XQZMonFjZ2GyReHktPWVzXvMNIEI+FFMWSYZ1/4vaWZtI0bZxgkB 3lW/e+frPXvgnJEq6sqMBCueuM3EGhz0rLjxzWl2qdJdj7TqB+VRYumVS5f+Z3eN
Processed: Bug #921797 in node-lru-cache marked as pending
Processing control commands: > tag -1 pending Bug #921797 [src:node-lru-cache] node-lru-cache: FTBFS (failing tests) Ignoring request to alter tags of bug #921797 to the same tags previously set -- 921797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921797 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921797: Bug #921797 in node-lru-cache marked as pending
Control: tag -1 pending Hello, Bug #921797 in node-lru-cache 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-lru-cache/commit/f4bec3307dbe553b5bd20726694183ac96375604 Increase tests timetouts (Closes: #921797) (this message was generated automatically) -- Greetings https://bugs.debian.org/921797
Bug#921797: Bug #921797 in node-lru-cache marked as pending
Control: tag -1 pending Hello, Bug #921797 in node-lru-cache 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-lru-cache/commit/8a5e5bfb1340bf6f25b35611ffd1b787b3b3dc44 Increase tests timetouts (Closes: #921797) (this message was generated automatically) -- Greetings https://bugs.debian.org/921797
Processed: Bug #921797 in node-lru-cache marked as pending
Processing control commands: > tag -1 pending Bug #921797 [src:node-lru-cache] node-lru-cache: FTBFS (failing tests) Added tag(s) pending. -- 921797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921797 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921296: ccfits: FTBFS with upcoming doxygen 1.8.15
On 2019-02-04 10:53, Aurelien Jarno wrote: > On 2019-02-04 01:04, Paolo Greppi wrote: > > Source: ccfits > > Severity: serious > > > > Dear Maintainer, > > > > I tested your package against a draft package for doxygen 1.8.15: > > https://bugs.debian.org/919413 > > > > and it FTBFS with this error: > > make[2]: *** [Makefile:8: refman.pdf] Error 1 > > > > That actually looks like a bug in doxygen. CCfits depends on > doxygen-latex, which according to its description should provide > everything needed: > > | Package: doxygen-latex > | ... > | Description-en: Documentation system for C, C++, Java, Python and other > languages > | Doxygen is a documentation system for C, C++, Java, Objective-C, Python, > IDL > | and to some extent PHP, C#, and D. It can generate an on-line class > browser > | (in HTML) and/or an off-line reference manual (in LaTeX) from a set of > | documented source files. > | . > | This dependency package adds dependencies for all LaTeX packages required > | to build documents using the default stylesheet. > > ccfits doesn't do anything fancy, it just generates the latex file using > doxygen and then run pdflatex on it. If a dependency is missing for > that, it should be added to doxygen-latex. > ccfits is now marked for autoremoval. Sending this email to reset the autoremoval while waiting for an answer. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Bug#874276: ca-certificates-java: fails to install on armhf: Error: missing `server' JVM at `/usr/lib/jvm/java-8-openjdk-armhf/jre/lib/arm/server/libjvm.so'
Followup-For: Bug #874276 Let's try to fix this in ca-certificates-java for stretch, the openjdk-8 fix does not seem to be effective for stretch. https://bugs.debian.org/921997 Andreas
Processed: unarchiving 874276, reassign 874276 to ca-certificates-java,src:openjdk-8 ...
Processing commands for cont...@bugs.debian.org:
> unarchive 874276
Bug #874276 {Done: Matthias Klose } [openjdk-8]
ca-certificates-java: fails to install on armhf: Error: missing `server' JVM at
`/usr/lib/jvm/java-8-openjdk-armhf/jre/lib/arm/server/libjvm.so'
Bug #874434 {Done: Matthias Klose } [openjdk-8]
openjdk-8-jre-headless: uninstallable on armhf
Unarchived Bug 874276
Unarchived Bug 874434
> reassign 874276 ca-certificates-java,src:openjdk-8
Bug #874276 {Done: Matthias Klose } [openjdk-8]
ca-certificates-java: fails to install on armhf: Error: missing `server' JVM at
`/usr/lib/jvm/java-8-openjdk-armhf/jre/lib/arm/server/libjvm.so'
Bug #874434 {Done: Matthias Klose } [openjdk-8]
openjdk-8-jre-headless: uninstallable on armhf
Bug reassigned from package 'openjdk-8' to 'ca-certificates-java,src:openjdk-8'.
Bug reassigned from package 'openjdk-8' to 'ca-certificates-java,src:openjdk-8'.
No longer marked as found in versions 8u144-b01-1.
No longer marked as found in versions 8u144-b01-1.
No longer marked as fixed in versions 8u144-b01-2.
No longer marked as fixed in versions 8u144-b01-2.
> fixed 874276 openjdk-8/8u144-b01-2
Bug #874276 {Done: Matthias Klose }
[ca-certificates-java,src:openjdk-8] ca-certificates-java: fails to install on
armhf: Error: missing `server' JVM at
`/usr/lib/jvm/java-8-openjdk-armhf/jre/lib/arm/server/libjvm.so'
Bug #874434 {Done: Matthias Klose }
[ca-certificates-java,src:openjdk-8] openjdk-8-jre-headless: uninstallable on
armhf
Marked as fixed in versions openjdk-8/8u144-b01-2.
Marked as fixed in versions openjdk-8/8u144-b01-2.
> fixed 874276 ca-certificates-java/20170929
Bug #874276 {Done: Matthias Klose }
[ca-certificates-java,src:openjdk-8] ca-certificates-java: fails to install on
armhf: Error: missing `server' JVM at
`/usr/lib/jvm/java-8-openjdk-armhf/jre/lib/arm/server/libjvm.so'
Bug #874434 {Done: Matthias Klose }
[ca-certificates-java,src:openjdk-8] openjdk-8-jre-headless: uninstallable on
armhf
Marked as fixed in versions ca-certificates-java/20170929.
Marked as fixed in versions ca-certificates-java/20170929.
> found 874276 openjdk-8/8u144-b01-1
Bug #874276 {Done: Matthias Klose }
[ca-certificates-java,src:openjdk-8] ca-certificates-java: fails to install on
armhf: Error: missing `server' JVM at
`/usr/lib/jvm/java-8-openjdk-armhf/jre/lib/arm/server/libjvm.so'
Bug #874434 {Done: Matthias Klose }
[ca-certificates-java,src:openjdk-8] openjdk-8-jre-headless: uninstallable on
armhf
Marked as found in versions openjdk-8/8u144-b01-1.
Marked as found in versions openjdk-8/8u144-b01-1.
> found 874276 ca-certificates-java/20170531+nmu1
Bug #874276 {Done: Matthias Klose }
[ca-certificates-java,src:openjdk-8] ca-certificates-java: fails to install on
armhf: Error: missing `server' JVM at
`/usr/lib/jvm/java-8-openjdk-armhf/jre/lib/arm/server/libjvm.so'
Bug #874434 {Done: Matthias Klose }
[ca-certificates-java,src:openjdk-8] openjdk-8-jre-headless: uninstallable on
armhf
Marked as found in versions ca-certificates-java/20170531+nmu1.
Marked as found in versions ca-certificates-java/20170531+nmu1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
874276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874276
874434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874434
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#921995: kauth: Insecure handling of arguments in helpers
Package: src:kauth Version: 5.28.0-2 Severity: grave Tags: security upstream patch Justification: user security hole See the KDE announce list [1]. It includes reference to a fix [2]. This is CVE-2019-7443. Scott K [1] https://mail.kde.org/pipermail/kde-announce/2019-February/11.html [2] https://cgit.kde.org/kauth.git/commit/?id=fc70fb0161c1b9144d26389434d34dd135cd3f4a
Processed: tagging 790213, fixed 606979 in 1.4.3+dfsg1-1, notfixed 743208 in 3.27.0, fixed 743208 in 3.28.1-1 ...
Processing commands for cont...@bugs.debian.org:
> tags 790213 - stretch
Bug #790213 {Done: Markus Koschany } [src:osmo] osmo: depends
on libwebkitgtk-1.0-0 which is deprecated
Removed tag(s) stretch.
> fixed 606979 1.4.3+dfsg1-1
Bug #606979 {Done: Marc Dequènes (duck) } [redmine] redmine:
more secure LDAP authentication
Marked as fixed in versions redmine/1.4.3+dfsg1-1.
> notfixed 743208 3.27.0
Bug #743208 {Done: Christoph Reiter } [python3-gi]
python3-gi: Ctrl-C does not abort Gtk.main()
There is no source info for the package 'python3-gi' at version '3.27.0' with
architecture ''
Unable to make a source version for version '3.27.0'
No longer marked as fixed in versions 3.27.0.
> fixed 743208 3.28.1-1
Bug #743208 {Done: Christoph Reiter } [python3-gi]
python3-gi: Ctrl-C does not abort Gtk.main()
Marked as fixed in versions pygobject/3.28.1-1.
> tags 743208 + sid buster
Bug #743208 {Done: Christoph Reiter } [python3-gi]
python3-gi: Ctrl-C does not abort Gtk.main()
Added tag(s) buster and sid.
> tags 906214 + experimental
Bug #906214 {Done: Jeremy Bicha } [polari] polari:
conditional catch clauses are incompatible with mozjs60 (gjs 1.53.90+)
Added tag(s) experimental.
> tags 883440 + sid
Bug #883440 {Done: Jeremy Bicha } [gnome] gnome: Don't
require gtk2
Added tag(s) sid.
> tags 917746 + experimental
Bug #917746 {Done: Jonas Smedegaard } [src:uglifyjs] uglifyjs:
FTBFS: tests failures
Added tag(s) experimental.
> fixed 911386 1.3.31-1
Bug #911386 {Done: Laszlo Boszormenyi (GCS) }
[libgraphicsmagick-q16-3] libgraphicsmagick-q16-3: graphicsmagick 1.3.30 has
made formats case-sensitive at the API level
Marked as fixed in versions graphicsmagick/1.3.31-1.
> fixed 881341 2.19.3-1
Bug #881341 {Done: Alberto Garcia } [src:webkit2gtk]
webkit2gtk FTCBFS: debian/rules confuses build and host
Marked as fixed in versions webkit2gtk/2.19.3-1.
> notfixed 817802 63.0.3239.84-1
Bug #817802 {Done: Michael Gilbert } [chromium] chromium:
Scrolling over tabs doesn't work as expected.
No longer marked as fixed in versions 63.0.3239.84-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
606979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606979
743208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743208
790213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790213
817802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817802
881341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881341
883440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883440
906214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906214
911386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911386
917746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917746
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#921781: fis-gtm: FTBFS (dh_auto_configure fails)
Thank you for the patch! We encountered the same problem with the deprecation of icu-config. I will fix the upstream source ASAP. Best Regards, Amul The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
Bug#920999: marked as done (zoneminder: CVE-2019-6992)
Your message dated Mon, 11 Feb 2019 03:28:33 + with message-id and subject line Bug#920999: fixed in zoneminder 1.32.3-2 has caused the Debian Bug report #920999, regarding zoneminder: CVE-2019-6992 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.) -- 920999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920999 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zoneminder Version: 1.32.3-1 Severity: grave Tags: security upstream Forwarded: https://github.com/ZoneMinder/zoneminder/issues/2445 Hi, The following vulnerability was published for zoneminder. CVE-2019-6992[0]: | A stored-self XSS exists in web/skins/classic/views/controlcaps.php of | ZoneMinder through 1.32.3, allowing an attacker to execute HTML or | JavaScript code in a vulnerable field via a long NAME or PROTOCOL to | the index.php?view=controlcaps URI. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-6992 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6992 [1] https://github.com/ZoneMinder/zoneminder/issues/2445 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: zoneminder Source-Version: 1.32.3-2 We believe that the bug you reported is fixed in the latest version of zoneminder, 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 920...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Smirnov (supplier of updated zoneminder 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, 11 Feb 2019 13:00:00 +1100 Source: zoneminder Binary: zoneminder zoneminder-dbgsym zoneminder-doc Architecture: source amd64 all Version: 1.32.3-2 Distribution: unstable Urgency: high Maintainer: Dmitry Smirnov Changed-By: Dmitry Smirnov Description: zoneminder - video camera security and surveillance solution zoneminder-doc - video camera security and surveillance solution (documentation) Closes: 915681 920375 920999 921000 921001 Changes: zoneminder (1.32.3-2) unstable; urgency=high . * Upload to unstable. * New upstream patches: + CVE-2019-6777 (Closes: #920375). + CVE-2019-6992 (Closes: #920999). + CVE-2019-6991 (Closes: #921000). + CVE-2019-6990 (Closes: #921001). + Fix for "image size is not multiples of 12 and 64". * Removed broken symlink (Closes: #915681). * Standards-Version: 4.3.0. * Build-Depends: - libmp4v2-dev Checksums-Sha1: f1f45ac28bdd75e90f29ae2d7dd05eace70499a3 3066 zoneminder_1.32.3-2.dsc dd8f8f7f9f4e12ce3d4c69c8ab3bddcf9e7b1ec3 32232 zoneminder_1.32.3-2.debian.tar.xz 7b398bb6d111e3cdf8d36af826e5b12437ca3a55 39824624 zoneminder-dbgsym_1.32.3-2_amd64.deb 8d847f45f8c99cf16b6c58821bf1c69af62348bb 5325896 zoneminder-doc_1.32.3-2_all.deb 3f058ac3c65c3d4ad90e96dd36b382e2ec9f2004 16108 zoneminder_1.32.3-2_amd64.buildinfo cc98374d81c3f27d6853214e2d9f8433ba163430 5411004 zoneminder_1.32.3-2_amd64.deb Checksums-Sha256: 068082f0ebab9590760f84692e536bb72a52ad8fc2a0111d9d5e3fde133f544b 3066 zoneminder_1.32.3-2.dsc 95d75aa0dbf3263e01384b61b9380cade1e4b1c9a1f07dfe1d4f6a38f7ee105c 32232 zoneminder_1.32.3-2.debian.tar.xz ffb3eb7e85f883f26cc07623f61a2e45840f531955be24077fd9a89a59cf7b10 39824624 zoneminder-dbgsym_1.32.3-2_amd64.deb 11bec4d674329d4acc54b3fefe9623dcbc10495397632f380227b8cb2f4ca193 5325896 zoneminder-doc_1.32.3-2_all.deb 75d03f9fadd7cd457bb357fd5d17e774415ce90a65f1d3c4a1aeee6c79403b25 16108 zoneminder_1.32.3-2_amd64.buildinfo 24fada352e81ad5365c7ba6fe91659206efcdd45a39a06fbccf72ae9bd31a9f3 5411004 zoneminder_1.32.3-2_amd64.deb Files: 32786b42b7ef22e6312c9476e2472914 3066 net optional zoneminder_1.32.3-2.dsc caa39696302d7359696a58f569546640 32232 net optional zoneminder_1.32.3-2.debian.tar.xz 096dba1779ca8c69ac13937e6e82c7de 39824624 debug optional zoneminder-dbgsym_1.32.3-2_amd64.deb 046f98ded73930b65a40238704bdf583 5325896 doc optional zoneminder-doc_1.32.3-2_all.deb
Bug#921000: marked as done (zoneminder: CVE-2019-6991)
Your message dated Mon, 11 Feb 2019 03:28:33 + with message-id and subject line Bug#921000: fixed in zoneminder 1.32.3-2 has caused the Debian Bug report #921000, regarding zoneminder: CVE-2019-6991 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.) -- 921000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921000 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zoneminder Version: 1.32.3-1 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://github.com/ZoneMinder/zoneminder/pull/2482 Hi, The following vulnerability was published for zoneminder. CVE-2019-6991[0]: | A classic Stack-based buffer overflow exists in the zmLoadUser() | function in zm_user.cpp of the zmu binary in ZoneMinder through 1.32.3, | allowing an unauthenticated attacker to execute code via a long | username. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-6991 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6991 [1] https://github.com/ZoneMinder/zoneminder/pull/2482 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: zoneminder Source-Version: 1.32.3-2 We believe that the bug you reported is fixed in the latest version of zoneminder, 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 921...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Smirnov (supplier of updated zoneminder 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, 11 Feb 2019 13:00:00 +1100 Source: zoneminder Binary: zoneminder zoneminder-dbgsym zoneminder-doc Architecture: source amd64 all Version: 1.32.3-2 Distribution: unstable Urgency: high Maintainer: Dmitry Smirnov Changed-By: Dmitry Smirnov Description: zoneminder - video camera security and surveillance solution zoneminder-doc - video camera security and surveillance solution (documentation) Closes: 915681 920375 920999 921000 921001 Changes: zoneminder (1.32.3-2) unstable; urgency=high . * Upload to unstable. * New upstream patches: + CVE-2019-6777 (Closes: #920375). + CVE-2019-6992 (Closes: #920999). + CVE-2019-6991 (Closes: #921000). + CVE-2019-6990 (Closes: #921001). + Fix for "image size is not multiples of 12 and 64". * Removed broken symlink (Closes: #915681). * Standards-Version: 4.3.0. * Build-Depends: - libmp4v2-dev Checksums-Sha1: f1f45ac28bdd75e90f29ae2d7dd05eace70499a3 3066 zoneminder_1.32.3-2.dsc dd8f8f7f9f4e12ce3d4c69c8ab3bddcf9e7b1ec3 32232 zoneminder_1.32.3-2.debian.tar.xz 7b398bb6d111e3cdf8d36af826e5b12437ca3a55 39824624 zoneminder-dbgsym_1.32.3-2_amd64.deb 8d847f45f8c99cf16b6c58821bf1c69af62348bb 5325896 zoneminder-doc_1.32.3-2_all.deb 3f058ac3c65c3d4ad90e96dd36b382e2ec9f2004 16108 zoneminder_1.32.3-2_amd64.buildinfo cc98374d81c3f27d6853214e2d9f8433ba163430 5411004 zoneminder_1.32.3-2_amd64.deb Checksums-Sha256: 068082f0ebab9590760f84692e536bb72a52ad8fc2a0111d9d5e3fde133f544b 3066 zoneminder_1.32.3-2.dsc 95d75aa0dbf3263e01384b61b9380cade1e4b1c9a1f07dfe1d4f6a38f7ee105c 32232 zoneminder_1.32.3-2.debian.tar.xz ffb3eb7e85f883f26cc07623f61a2e45840f531955be24077fd9a89a59cf7b10 39824624 zoneminder-dbgsym_1.32.3-2_amd64.deb 11bec4d674329d4acc54b3fefe9623dcbc10495397632f380227b8cb2f4ca193 5325896 zoneminder-doc_1.32.3-2_all.deb 75d03f9fadd7cd457bb357fd5d17e774415ce90a65f1d3c4a1aeee6c79403b25 16108 zoneminder_1.32.3-2_amd64.buildinfo 24fada352e81ad5365c7ba6fe91659206efcdd45a39a06fbccf72ae9bd31a9f3 5411004 zoneminder_1.32.3-2_amd64.deb Files: 32786b42b7ef22e6312c9476e2472914 3066 net optional zoneminder_1.32.3-2.dsc caa39696302d7359696a58f569546640 32232 net optional zoneminder_1.32.3-2.debian.tar.xz 096dba1779ca8c69ac13937e6e82c7de 39824624 debug optional zoneminder-dbgsym_1.32.3-2_amd64.deb 046f98ded73930b65a40238704bdf583 5325896 doc optional zoneminder-doc_1.32.3-2_all.deb
Bug#921001: marked as done (zoneminder: CVE-2019-6990)
Your message dated Mon, 11 Feb 2019 03:28:33 + with message-id and subject line Bug#921001: fixed in zoneminder 1.32.3-2 has caused the Debian Bug report #921001, regarding zoneminder: CVE-2019-6990 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.) -- 921001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921001 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zoneminder Version: 1.32.3-1 Severity: grave Tags: security upstream Forwarded: https://github.com/ZoneMinder/zoneminder/issues/2444 Hi, The following vulnerability was published for zoneminder. CVE-2019-6990[0]: | A stored-self XSS exists in web/skins/classic/views/zones.php of | ZoneMinder through 1.32.3, allowing an attacker to execute HTML or | JavaScript code in a vulnerable field via a crafted Zone NAME to the | index.php?view=zonesaction=zoneImagemid=1 URI. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-6990 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6990 [1] https://github.com/ZoneMinder/zoneminder/issues/2444 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: zoneminder Source-Version: 1.32.3-2 We believe that the bug you reported is fixed in the latest version of zoneminder, 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 921...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Smirnov (supplier of updated zoneminder 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, 11 Feb 2019 13:00:00 +1100 Source: zoneminder Binary: zoneminder zoneminder-dbgsym zoneminder-doc Architecture: source amd64 all Version: 1.32.3-2 Distribution: unstable Urgency: high Maintainer: Dmitry Smirnov Changed-By: Dmitry Smirnov Description: zoneminder - video camera security and surveillance solution zoneminder-doc - video camera security and surveillance solution (documentation) Closes: 915681 920375 920999 921000 921001 Changes: zoneminder (1.32.3-2) unstable; urgency=high . * Upload to unstable. * New upstream patches: + CVE-2019-6777 (Closes: #920375). + CVE-2019-6992 (Closes: #920999). + CVE-2019-6991 (Closes: #921000). + CVE-2019-6990 (Closes: #921001). + Fix for "image size is not multiples of 12 and 64". * Removed broken symlink (Closes: #915681). * Standards-Version: 4.3.0. * Build-Depends: - libmp4v2-dev Checksums-Sha1: f1f45ac28bdd75e90f29ae2d7dd05eace70499a3 3066 zoneminder_1.32.3-2.dsc dd8f8f7f9f4e12ce3d4c69c8ab3bddcf9e7b1ec3 32232 zoneminder_1.32.3-2.debian.tar.xz 7b398bb6d111e3cdf8d36af826e5b12437ca3a55 39824624 zoneminder-dbgsym_1.32.3-2_amd64.deb 8d847f45f8c99cf16b6c58821bf1c69af62348bb 5325896 zoneminder-doc_1.32.3-2_all.deb 3f058ac3c65c3d4ad90e96dd36b382e2ec9f2004 16108 zoneminder_1.32.3-2_amd64.buildinfo cc98374d81c3f27d6853214e2d9f8433ba163430 5411004 zoneminder_1.32.3-2_amd64.deb Checksums-Sha256: 068082f0ebab9590760f84692e536bb72a52ad8fc2a0111d9d5e3fde133f544b 3066 zoneminder_1.32.3-2.dsc 95d75aa0dbf3263e01384b61b9380cade1e4b1c9a1f07dfe1d4f6a38f7ee105c 32232 zoneminder_1.32.3-2.debian.tar.xz ffb3eb7e85f883f26cc07623f61a2e45840f531955be24077fd9a89a59cf7b10 39824624 zoneminder-dbgsym_1.32.3-2_amd64.deb 11bec4d674329d4acc54b3fefe9623dcbc10495397632f380227b8cb2f4ca193 5325896 zoneminder-doc_1.32.3-2_all.deb 75d03f9fadd7cd457bb357fd5d17e774415ce90a65f1d3c4a1aeee6c79403b25 16108 zoneminder_1.32.3-2_amd64.buildinfo 24fada352e81ad5365c7ba6fe91659206efcdd45a39a06fbccf72ae9bd31a9f3 5411004 zoneminder_1.32.3-2_amd64.deb Files: 32786b42b7ef22e6312c9476e2472914 3066 net optional zoneminder_1.32.3-2.dsc caa39696302d7359696a58f569546640 32232 net optional zoneminder_1.32.3-2.debian.tar.xz 096dba1779ca8c69ac13937e6e82c7de 39824624 debug optional zoneminder-dbgsym_1.32.3-2_amd64.deb 046f98ded73930b65a40238704bdf583 5325896 doc optional zoneminder-doc_1.32.3-2_all.deb
Bug#921542: [Patch net 1/3] net_sched: fix a race condition in tcindex_destroy()
tcindex_destroy() invokes tcindex_destroy_element() via
a walker to delete each filter result in its perfect hash
table, and tcindex_destroy_element() calls tcindex_delete()
which schedules tcf RCU works to do the final deletion work.
Unfortunately this races with the RCU callback
__tcindex_destroy(), which could lead to use-after-free as
reported by Adrian.
Fix this by migrating this RCU callback to tcf RCU work too,
as that workqueue is ordered, we will not have use-after-free.
This change requires us to store a net pointer inside struct
tcindex_data, to avoid the known race with tc_action_net_exit().
Fixes: 27ce4f05e2ab ("net_sched: use tcf_queue_work() in tcindex filter")
Reported-by: Adrian
Cc: Ben Hutchings
Cc: Jamal Hadi Salim
Cc: Jiri Pirko
Signed-off-by: Cong Wang
---
net/sched/cls_tcindex.c | 46 -
1 file changed, 36 insertions(+), 10 deletions(-)
diff --git a/net/sched/cls_tcindex.c b/net/sched/cls_tcindex.c
index 9ccc93f257db..14e6d80dd58e 100644
--- a/net/sched/cls_tcindex.c
+++ b/net/sched/cls_tcindex.c
@@ -48,7 +48,8 @@ struct tcindex_data {
u32 hash; /* hash table size; 0 if undefined */
u32 alloc_hash; /* allocated size */
u32 fall_through; /* 0: only classify if explicit match */
- struct rcu_head rcu;
+ struct net *net;
+ struct rcu_work rwork;
};
static inline int tcindex_filter_is_set(struct tcindex_filter_result *r)
@@ -229,15 +230,23 @@ static int tcindex_destroy_element(struct tcf_proto *tp,
return tcindex_delete(tp, arg, , NULL);
}
-static void __tcindex_destroy(struct rcu_head *head)
+static void __tcindex_destroy(struct tcindex_data *p)
{
- struct tcindex_data *p = container_of(head, struct tcindex_data, rcu);
-
kfree(p->perfect);
kfree(p->h);
kfree(p);
}
+static void tcindex_destroy_work(struct work_struct *work)
+{
+ struct tcindex_data *p = container_of(to_rcu_work(work),
+ struct tcindex_data,
+ rwork);
+
+ put_net(p->net);
+ __tcindex_destroy(p);
+}
+
static inline int
valid_perfect_hash(struct tcindex_data *p)
{
@@ -258,14 +267,22 @@ static int tcindex_filter_result_init(struct
tcindex_filter_result *r)
return tcf_exts_init(>exts, TCA_TCINDEX_ACT, TCA_TCINDEX_POLICE);
}
-static void __tcindex_partial_destroy(struct rcu_head *head)
+static void __tcindex_partial_destroy(struct tcindex_data *p)
{
- struct tcindex_data *p = container_of(head, struct tcindex_data, rcu);
-
kfree(p->perfect);
kfree(p);
}
+static void tcindex_partial_destroy_work(struct work_struct *work)
+{
+ struct tcindex_data *p = container_of(to_rcu_work(work),
+ struct tcindex_data,
+ rwork);
+
+ put_net(p->net);
+ __tcindex_partial_destroy(p);
+}
+
static void tcindex_free_perfect_hash(struct tcindex_data *cp)
{
int i;
@@ -333,6 +350,7 @@ tcindex_set_parms(struct net *net, struct tcf_proto *tp,
unsigned long base,
cp->alloc_hash = p->alloc_hash;
cp->fall_through = p->fall_through;
cp->tp = tp;
+ cp->net = net;
if (p->perfect) {
int i;
@@ -477,8 +495,13 @@ tcindex_set_parms(struct net *net, struct tcf_proto *tp,
unsigned long base,
rcu_assign_pointer(*fp, f);
}
- if (oldp)
- call_rcu(>rcu, __tcindex_partial_destroy);
+ if (oldp) {
+ if (oldp->net && maybe_get_net(oldp->net))
+ tcf_queue_work(>rwork,
+ tcindex_partial_destroy_work);
+ else
+ __tcindex_partial_destroy(oldp);
+ }
return 0;
errout_alloc:
@@ -570,7 +593,10 @@ static void tcindex_destroy(struct tcf_proto *tp,
walker.fn = tcindex_destroy_element;
tcindex_walk(tp, );
- call_rcu(>rcu, __tcindex_destroy);
+ if (maybe_get_net(p->net))
+ tcf_queue_work(>rwork, tcindex_destroy_work);
+ else
+ __tcindex_destroy(p);
}
--
2.20.1
Processed: tagging 921542
Processing commands for cont...@bugs.debian.org: > tags 921542 + patch Bug #921542 [src:linux] tc qdisc kernel crash Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 921542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921542 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919477: Any reason why acl2 will not propagate now?
??? Take care, -- Camm Maguirec...@maguirefamily.org == "The earth is but one country, and mankind its citizens." -- Baha'u'llah
Processed: fixed 736479 in 1.18.0-1, fixed 768915 in 2.2.1-1, fixed 859499 in 3.0.2+ds-1~exp1 ...
Processing commands for cont...@bugs.debian.org:
> # fixup bug metadata to allow archival
> fixed 736479 1.18.0-1
Bug #736479 {Done: Petter Reinholdtsen } [insserv] insserv
code missing brackets for a conditional statement
Marked as fixed in versions insserv/1.18.0-1.
> fixed 768915 2.2.1-1
Bug #768915 {Done: Vincent Legout } [qalculate-gtk]
qalculate-gtk: move to Education/Science category
Marked as fixed in versions qalculate-gtk/2.2.1-1.
> fixed 859499 3.0.2+ds-1~exp1
Bug #859499 {Done: Roger Shimizu } [shadowsocks-libev]
shadowsocks-libev: ss-local doesn't do DNS resolving for acl bypassed domains
Marked as fixed in versions shadowsocks-libev/3.0.2+ds-1~exp1.
> reassign 812826 im-config
Bug #812826 {Done: Osamu Aoki } [ibus] ibus-x11 doesn't
process input in its incoming order
Bug #838318 {Done: Osamu Aoki } [ibus] ibus: Characters
swapped under certain circumstances
Bug #876794 {Done: Osamu Aoki } [ibus] ibus-hangul: Java
causes ibus to not work correctly (spaces incorrectly placed)
Bug reassigned from package 'ibus' to 'im-config'.
Bug reassigned from package 'ibus' to 'im-config'.
Bug reassigned from package 'ibus' to 'im-config'.
No longer marked as found in versions ibus/1.5.11-1.
No longer marked as found in versions ibus/1.5.11-1.
No longer marked as found in versions ibus/1.5.11-1.
No longer marked as fixed in versions im-config/0.31-1.
No longer marked as fixed in versions im-config/0.31-1.
No longer marked as fixed in versions im-config/0.31-1.
> fixed 812826 0.31-1
Bug #812826 {Done: Osamu Aoki } [im-config] ibus-x11 doesn't
process input in its incoming order
Bug #838318 {Done: Osamu Aoki } [im-config] ibus: Characters
swapped under certain circumstances
Bug #876794 {Done: Osamu Aoki } [im-config] ibus-hangul: Java
causes ibus to not work correctly (spaces incorrectly placed)
Marked as fixed in versions im-config/0.31-1.
Marked as fixed in versions im-config/0.31-1.
Marked as fixed in versions im-config/0.31-1.
> affects 812826 + ibus
Bug #812826 {Done: Osamu Aoki } [im-config] ibus-x11 doesn't
process input in its incoming order
Bug #838318 {Done: Osamu Aoki } [im-config] ibus: Characters
swapped under certain circumstances
Bug #876794 {Done: Osamu Aoki } [im-config] ibus-hangul: Java
causes ibus to not work correctly (spaces incorrectly placed)
Added indication that 812826 affects ibus
Added indication that 838318 affects ibus
Added indication that 876794 affects ibus
> fixed 874675 4:5.7.0-3
Bug #874675 {Done: s...@debian.org (Steve M. Robbins)} [kipi-plugins]
kipi-plugins: flickr uploader: restricts video uploads to max photo size
There is no source info for the package 'kipi-plugins' at version '4:5.7.0-3'
with architecture ''
Unable to make a source version for version '4:5.7.0-3'
Marked as fixed in versions 4:5.7.0-3.
> reassign 875977 src:hdf5 1.10.0-patch1+docs-3
Bug #875977 {Done: Gilles Filippini } [libhdf5-100]
libhdf5-100: Performs unaligned accesses on sparc64
Bug reassigned from package 'libhdf5-100' to 'src:hdf5'.
No longer marked as found in versions hdf5/1.10.0-patch1+docs-3.
No longer marked as fixed in versions hdf5/1.10.1+docs-1~exp1.
Bug #875977 {Done: Gilles Filippini } [src:hdf5] libhdf5-100:
Performs unaligned accesses on sparc64
Marked as found in versions hdf5/1.10.0-patch1+docs-3.
> fixed 875977 1.10.1+docs-1~exp1
Bug #875977 {Done: Gilles Filippini } [src:hdf5] libhdf5-100:
Performs unaligned accesses on sparc64
Marked as fixed in versions hdf5/1.10.1+docs-1~exp1.
> reassign 855810 src:hdf5 1.10.0-patch1+docs-3
Bug #855810 {Done: Gilles Filippini } [libhdf5-openmpi-100]
libhdf5-openmpi-100 doesn't work on arm64
Bug reassigned from package 'libhdf5-openmpi-100' to 'src:hdf5'.
No longer marked as found in versions hdf5/1.10.0-patch1+docs-3.
No longer marked as fixed in versions hdf5/1.10.1+repack-1~exp1.
Bug #855810 {Done: Gilles Filippini } [src:hdf5]
libhdf5-openmpi-100 doesn't work on arm64
Marked as found in versions hdf5/1.10.0-patch1+docs-3.
> fixed 855810 1.10.1+docs-1~exp1
Bug #855810 {Done: Gilles Filippini } [src:hdf5]
libhdf5-openmpi-100 doesn't work on arm64
Marked as fixed in versions hdf5/1.10.1+docs-1~exp1.
> fixed 834131 4:5.7.0-2
Bug #834131 {Done: s...@debian.org (Steve M. Robbins)} [digikam] digikam: no
video playback and no video thumbnails
Marked as fixed in versions digikam/4:5.7.0-2.
> fixed 885908 1:7.6.4-0.2
Bug #885908 {Done: John Paul Adrian Glaubitz }
[src:libgc] libgc: Please update symbols file for ia64
Marked as fixed in versions libgc/1:7.6.4-0.2.
> fixed 851924 1:7.6.4-0.2
Bug #851924 {Done: John Paul Adrian Glaubitz }
[src:libgc] libgc: Please update symbols for sh3
Marked as fixed in versions libgc/1:7.6.4-0.2.
> fixed 810605 3.27.90-1
Bug #810605 {Done: Sam Morris } [nautilus] nautilus: Crash
when logging in to flashback mode
Marked as fixed in versions nautilus/3.27.90-1.
> notfixed 863451 1.21.1-1.3
Bug #863451 {Done: Jeremy Sanders } [veusz] veusz:
Segmentation fault
No longer marked as fixed in
Bug#913580: marked as done (prometheus-nginx-vts-exporter FTBFS: too many arguments in call to prometheus.NewProcessCollector)
Your message dated Mon, 11 Feb 2019 01:34:48 + with message-id and subject line Bug#913580: fixed in prometheus-nginx-vts-exporter 0.10.3+git20180501.43b4556+ds-2 has caused the Debian Bug report #913580, regarding prometheus-nginx-vts-exporter FTBFS: too many arguments in call to prometheus.NewProcessCollector 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.) -- 913580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913580 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: prometheus-nginx-vts-exporter Version: 0.10.3+git20180501.43b4556+ds-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/prometheus-nginx-vts-exporter.html ... github.com/hnlq715/nginx-vts-exporter # github.com/hnlq715/nginx-vts-exporter src/github.com/hnlq715/nginx-vts-exporter/nginx_vts_exporter.go:377:54: too many arguments in call to prometheus.NewProcessCollector have (int, string) want (prometheus.ProcessCollectorOpts) dh_auto_build: cd build && go install -gcflags=all=\"-trimpath=/build/1st/prometheus-nginx-vts-exporter-0.10.3\+git20180501.43b4556\+ds/build/src\" -asmflags=all=\"-trimpath=/build/1st/prometheus-nginx-vts-exporter-0.10.3\+git20180501.43b4556\+ds/build/src\" -v -p 16 github.com/hnlq715/nginx-vts-exporter returned exit code 2 make: *** [debian/rules:7: build] Error 2 --- End Message --- --- Begin Message --- Source: prometheus-nginx-vts-exporter Source-Version: 0.10.3+git20180501.43b4556+ds-2 We believe that the bug you reported is fixed in the latest version of prometheus-nginx-vts-exporter, 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 913...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martín Ferrari (supplier of updated prometheus-nginx-vts-exporter 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, 11 Feb 2019 01:11:11 + Source: prometheus-nginx-vts-exporter Architecture: source Version: 0.10.3+git20180501.43b4556+ds-2 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Martín Ferrari Closes: 913580 Changes: prometheus-nginx-vts-exporter (0.10.3+git20180501.43b4556+ds-2) unstable; urgency=medium . * Team upload. * Patch code to work with new client API. Closes: #913580. * Automated fixes from cme. Checksums-Sha1: 974bdc8eec7ac3fb88d8a593c2dbc71b40e3fda6 2505 prometheus-nginx-vts-exporter_0.10.3+git20180501.43b4556+ds-2.dsc cbc5c212c28f9e6274ffabcfaeaa207146e60824 5308 prometheus-nginx-vts-exporter_0.10.3+git20180501.43b4556+ds-2.debian.tar.xz 6092c136e860e97c25cf76c1b54d3f2d6091434b 8235 prometheus-nginx-vts-exporter_0.10.3+git20180501.43b4556+ds-2_amd64.buildinfo Checksums-Sha256: 0cd27a81daceef396ec16378e388e6d2e12031e7901de780900682a013e83c16 2505 prometheus-nginx-vts-exporter_0.10.3+git20180501.43b4556+ds-2.dsc feab7f4113781cb25c6a418f26514a17a31bd1c51ac586acffe16a5ccb24254d 5308 prometheus-nginx-vts-exporter_0.10.3+git20180501.43b4556+ds-2.debian.tar.xz fdabd8e50b0fbaea072950fad2df6a45da2a3c17bb7667c4064d73e6df56faba 8235 prometheus-nginx-vts-exporter_0.10.3+git20180501.43b4556+ds-2_amd64.buildinfo Files: 14de78636962dca6dee5553564e8cebf 2505 net optional prometheus-nginx-vts-exporter_0.10.3+git20180501.43b4556+ds-2.dsc 4d25743ecc170faa9cdccac3b18d40b2 5308 net optional prometheus-nginx-vts-exporter_0.10.3+git20180501.43b4556+ds-2.debian.tar.xz 5e94bbdb486c990448c8102ab1cbd890 8235 net optional prometheus-nginx-vts-exporter_0.10.3+git20180501.43b4556+ds-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEETe94h3mvRsa9AoOeXdjgv5Gj09oFAlxgy/kACgkQXdjgv5Gj 09rmrw//e8ONJLt3gnNLUUCbd9i8czQFMBvG1aCPebuXwhgM5BbLMnAe7+WxwM81 kA2orWAuU/tfTR1TonWMTyWBaRaXfsO+V2cW7lywz9ET8xRLZE6Qo3vp2F7zQFsm Lfo06QjIvTcQmVKuxxbvUjSnGRxDM1RQwZ0trE+DkbDm3rjot0kSUZ5jDAp5AdY3 nvweSbNT4YCpZ06Roo0hbspyzLKZ9ZJbAZjVr+AM57AK561KP0ATfCSmmjDqelO8 xdigqgs1hblDMM6IX4yG1wzOZJRHQk8iDcUQCWzasQdtM8gqZLqIJ8nMIcwLjT/v oWy7+zUtBC0NZeIJRafSMSRbifzN6mV/kOsv9aSKrpIlmYC09dv0ulMlrL/jrvTw U0nu/KMkVWg4lUsvi4PmQ93wK4R3v/EwzoGfZ8zeSPqGED1pg5EYWkdfiwiux57O
Processed: Bug #913580 in prometheus-nginx-vts-exporter marked as pending
Processing control commands: > tag -1 pending Bug #913580 [src:prometheus-nginx-vts-exporter] prometheus-nginx-vts-exporter FTBFS: too many arguments in call to prometheus.NewProcessCollector Added tag(s) pending. -- 913580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913580 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#913580: Bug #913580 in prometheus-nginx-vts-exporter marked as pending
Control: tag -1 pending Hello, Bug #913580 in prometheus-nginx-vts-exporter 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/prometheus-nginx-vts-exporter/commit/8cf1b3ce8c5b3295393aa58a034396a974613890 Patch code to work with new client API. Closes: #913580. (this message was generated automatically) -- Greetings https://bugs.debian.org/913580
Bug#906855: gcu-plugin: NPAPI plugins are no longer supported by firefox-esr
Followup-For: Bug #906855 Control: tag -1 pending Hi, I just backported the fix from sid, rebuilt the package for stretch and opened a stretch-pu request. Let's see if this can still reach 9.8. https://bugs.debian.org/921983 Andreas
Processed: Re: gcu-plugin: NPAPI plugins are no longer supported by firefox-esr
Processing control commands:
> tag -1 pending
Bug #906855 {Done: Adrian Bunk } [gcu-plugin] gcu-plugin:
NPAPI plugins are no longer supported by firefox-esr
Added tag(s) pending.
--
906855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906855
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#921351: marked as done (prometheus-postfix-exporter: Init script missing)
Your message dated Mon, 11 Feb 2019 00:41:00 + with message-id and subject line Bug#921351: fixed in prometheus-postfix-exporter 0.1.2-2 has caused the Debian Bug report #921351, regarding prometheus-postfix-exporter: Init script missing 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.) -- 921351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921351 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: prometheus-postfix-exporter Version: 0.1.2-1 Severity: serious Justification: Policy 9.11 Excerpt from policy 9.11: However, any package integrating with other init systems must also be backwards-compatible with sysvinit by providing a SysV- style init script with the same name as and equivalent functionality to any init-specific job, as this is the only start-up configuration method guaranteed to be supported by all init implementations. The package violates a policy must by not providing s sysvint init script. Scott K --- End Message --- --- Begin Message --- Source: prometheus-postfix-exporter Source-Version: 0.1.2-2 We believe that the bug you reported is fixed in the latest version of prometheus-postfix-exporter, 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 921...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martín Ferrari (supplier of updated prometheus-postfix-exporter 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, 11 Feb 2019 00:05:35 + Source: prometheus-postfix-exporter Architecture: source Version: 0.1.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Martín Ferrari Closes: 921351 Changes: prometheus-postfix-exporter (0.1.2-2) unstable; urgency=medium . * Team upload. . [ Daniel Swarbrick ] * Add manpage link to systemd service . [ Martín Ferrari ] * Run wrap-and-sort -ta. * Create prometheus user. * Add rsyslog configution snippet for a dedicated log file. * Use the file log instead of systemd journal. * Run as user prometheus instead of postfix. * Add support for SysV init. Closes: #921351. * Add custom python script to support additional groups. Checksums-Sha1: 247f045e7172ae44379b7dda24400db19a3f9331 2332 prometheus-postfix-exporter_0.1.2-2.dsc 795bb4e338514808c14c6f69246527b6a6c9c4b2 5580 prometheus-postfix-exporter_0.1.2-2.debian.tar.xz ec98c28e9a335155d2961728e3eac6ba1d72d5a6 8491 prometheus-postfix-exporter_0.1.2-2_amd64.buildinfo Checksums-Sha256: a50dde727c078001ac39329395a1b234e51345b9850c5afbe351b8ca1afba375 2332 prometheus-postfix-exporter_0.1.2-2.dsc 26788e819a43bc7a21248b643977b35d1809eeb9d9fd4d0965a96c38bc12ceb0 5580 prometheus-postfix-exporter_0.1.2-2.debian.tar.xz 7ae24af0eb7bb63263d0910fdad4c199539dbe394c7828ca6e20eea03f3f06f2 8491 prometheus-postfix-exporter_0.1.2-2_amd64.buildinfo Files: 1dddf2bf374b41d4b52957d87ce5fc32 2332 net optional prometheus-postfix-exporter_0.1.2-2.dsc 85240d527b7850bd639d71c3f2db3a0a 5580 net optional prometheus-postfix-exporter_0.1.2-2.debian.tar.xz 9eeb740e739abb68ca97497a2b631826 8491 net optional prometheus-postfix-exporter_0.1.2-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEETe94h3mvRsa9AoOeXdjgv5Gj09oFAlxgvJcACgkQXdjgv5Gj 09oFdg/+IDrcmTctn1WGEOQi8bs5mforOi2/94IUAbonhDtcQQzqAKjsymLGOmIT cB5bzIwzo2/KlLMqVBcLAavXzxpUlb7/CNA1qolGzcWbrJxYtlGQBkc0F5zTyu4y fjqvDM5QclJI9MhpEszRVFZjIA/VZMgd7xGNKp85dGL51uSBJhzFjBteodmDI9QA 7g7Mi/qbx67KMS6psSd026f7VXtRga2fI5xMWHR2lHdpfcqSYMwUxteG/jpvWzpq em92kcGWk1JqpszP2S+V3bLqPx3T0e5CvHA9YUJnNCoYtNobsXRzY1uGLsaQR01X k+7HpIOcPj+nwgI3jMxDiY8PM9mo7h1EnvAdB2pEktWBLj3f5CTDnYKNwmE28NFe Bmj8O7eTDQcpkD6TiFmWHKFLLXrXl/KHWZb3doiXr8HpKNWjJWWGHoiI0q2vRrHx 1r8pRf+8+z4AeWW1p3e+h10HS8bqxLGau0Ws6QbLlbvKewabZFMIWEtD9tP6GVS+ RiVnUyXm1bjb/JiItHhOTxa0PB0zA/P2jao1ojewPRsqvVzsOW4LuV6dzIHl9UtC WcDtbU5t2WrKAh8po2TD6pYBvgzNtKJkkLgwP0oLNC6EcobQZa7tBwnKSI1y4D8L a6Usln41VZC3tkXrmkFQBMNXgWS4kNGctZbDlNeVL/hTrv6nsv0= =wfpa -END PGP SIGNATURE End Message ---
Bug#910316: marked as done (erlang-ranch FTBFS: src/ranch_ssl.erl:128: ssl:ssl_accept/2: deprecated; use ssl:handshake/2 instead)
Your message dated Mon, 11 Feb 2019 00:04:35 + with message-id and subject line Bug#910316: fixed in erlang-ranch 1.3.0-2 has caused the Debian Bug report #910316, regarding erlang-ranch FTBFS: src/ranch_ssl.erl:128: ssl:ssl_accept/2: deprecated; use ssl:handshake/2 instead 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.) -- 910316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910316 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: erlang-ranch Version: 1.3.0-1 Severity: serious Tags: ftbfs erlang-ranch fails to build from source using sbuild on unstable/amd64. A build log ends with: |debian/rules override_dh_auto_build | make[1]: Entering directory '/<>' | make SKIP_DEPS=yes | make[2]: Entering directory '/<>' | DEPEND ranch.d | ERLC ranch.erl ranch_acceptor.erl ranch_acceptors_sup.erl ranch_app.erl ranch_conns_sup.erl ranch_listener_sup.erl ranch_protocol.erl ranch_server.erl ranch_ssl.erl ranch_sup.erl ranch_tcp.erl ranch_transport.erl | compile: warnings being treated as errors | src/ranch_ssl.erl:128: ssl:ssl_accept/2: deprecated; use ssl:handshake/2 instead | make[3]: *** [erlang.mk:5069: ebin/ranch.app] Error 1 | make[2]: *** [erlang.mk:4872: app] Error 2 | make[2]: Leaving directory '/<>' | make[1]: *** [debian/rules:10: override_dh_auto_build] Error 2 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:7: build] Error 2 | dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 This is also seen by reproducible builds: https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/erlang-ranch_1.3.0-1.rbuild.log.gz Helmut --- End Message --- --- Begin Message --- Source: erlang-ranch Source-Version: 1.3.0-2 We believe that the bug you reported is fixed in the latest version of erlang-ranch, 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 910...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nobuhiro Iwamatsu (supplier of updated erlang-ranch 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, 11 Feb 2019 08:31:55 +0900 Source: erlang-ranch Binary: erlang-ranch erlang-ranch-doc Architecture: source all amd64 Version: 1.3.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Erlang Packagers Changed-By: Nobuhiro Iwamatsu Description: erlang-ranch - socket acceptor pool for TCP protocols in Erlang erlang-ranch-doc - Documentation of erlang-ranch Closes: 910316 Changes: erlang-ranch (1.3.0-2) unstable; urgency=medium . [Balint Reczey] * Remove myself from Uploaders[] [Nobuhiro Iwamatsu] * Set nowarn_deprecated_function to ssl_accept (Closes: #910316) Checksums-Sha1: 2029444195ce51650f11299610232f6b341800f6 2259 erlang-ranch_1.3.0-2.dsc c5145176b21f04dd420f8207efb705f211deb125 3300 erlang-ranch_1.3.0-2.debian.tar.xz fb85d83183fb1c37739e82cabef2f07e6667bda9 147608 erlang-ranch-doc_1.3.0-2_all.deb ffdb950ba428fd939fb1085c59c5361e728e5f6a 11138 erlang-ranch_1.3.0-2_amd64.buildinfo 2f9fab81e3c0436a7ddf23f0e07af4c6f5f37b08 58344 erlang-ranch_1.3.0-2_amd64.deb Checksums-Sha256: 7024a45129fe6aa92c7d313af64e7983e5def73b87b51eb61d82017304c25cd8 2259 erlang-ranch_1.3.0-2.dsc fa4ba945826b4f787b4a2d7aae54f2f64359fe53bf9e4104abb266d2554d0828 3300 erlang-ranch_1.3.0-2.debian.tar.xz 3806c7a64686eacf94381af2149edd3cff3abbf5d551df709f64e0e9e44ea772 147608 erlang-ranch-doc_1.3.0-2_all.deb 5b17959c8afb2107fd7f9408c9e00bc1e6c07d1f5cef077d1d2d6de3ac11f7b4 11138 erlang-ranch_1.3.0-2_amd64.buildinfo 1be14026d576c2e1aaa522a2b8110b38fa722c70c21ee808f95f0ca51373b7ca 58344 erlang-ranch_1.3.0-2_amd64.deb Files: e33abcf7a647ef82cb4809abe7947361 2259 devel optional erlang-ranch_1.3.0-2.dsc 0ab3aae9e62ca2ffe2dc03ba398c7dd2 3300 devel optional erlang-ranch_1.3.0-2.debian.tar.xz d12b1b1fc3f5f00cc7f71c51872cd93c 147608 doc optional erlang-ranch-doc_1.3.0-2_all.deb df1f5a30d7cd69af50c4ad184b696c64 11138 devel optional erlang-ranch_1.3.0-2_amd64.buildinfo 547ba160f92d1f0e123744bbba212548 58344 devel optional erlang-ranch_1.3.0-2_amd64.deb -BEGIN PGP SIGNATURE-
Bug#921990: mypy should depend on the precise version of python3-mypy
Package: mypy
Version: 0.670-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I upgraded mypy, python3-mypy did not get pulled in as dependency so it remained
as the old version.
This is what happens when I ran it.
$ mypy
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 581, in
_build_master
ws.require(__requires__)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 898, in
require
needed = self.resolve(parse_requirements(requirements))
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 789, in
resolve
raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.VersionConflict: (mypy 0.660 (/usr/lib/python3/dist-packages),
Requirement.parse('mypy==0.670'))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/bin/mypy", line 6, in
from pkg_resources import load_entry_point
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3126,
in
@_call_aside
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3110,
in _call_aside
f(*args, **kwargs)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3139,
in _initialize_master_working_set
working_set = WorkingSet._build_master()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 583, in
_build_master
return cls._build_from_requirements(__requires__)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 596, in
_build_from_requirements
dists = ws.resolve(reqs, Environment())
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 784, in
resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'mypy==0.670' distribution was not
found and is required by the application
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages mypy depends on:
ii python3 3.7.2-1
ii python3-mypy 0.660-5
mypy recommends no packages.
Versions of packages mypy suggests:
pn mypy-doc
-- no debconf information
Bug#921030: Fails to import the ansible module since its migration to Python 3
Hello Gregory, I would like to see the last version of ansible-lint shipped on Debian Buster, thus I would like to fix this bug by uploading the last 4.0.1-1 to unstable. It won't get to Buster before the release but as it will fix a RC bug, it should be ok. Are you fine with me fixing the problem? I would also like to add myself as an uploader while doing so. Thanks. -- Samuel Henrique
Bug#919356: Licensing of include/linux/hash.h
On 1/23/19 9:50 AM, Domenico Andreoli wrote: > Ben Finney writes: >> Domenico Andreoli writes: >> >>> the situation of dwarves-dfsg improved a lot over the weekend >> >> That's good to hear. What is the event you're referring to? Can you give >> a URL to something that describes this change? > > Upstream (in CC) reacted to my request of clarification and patches > have been applied upstream and on Salsa. See bug 919356 [0] (please > keep in CC). > >>> the only knot left is now the license of hash.h >>> >>> This file is also present in the kernel [0] with an updated copyright >>> but still without license. >> >> The file you show (in the Linux code base) seems likely to have an >> equivalent implementation under a different license, from some other >> code base. > > This will require research and work unlikely to be done before Buster > release. Are we going to drop this package for now? > >>> I received a private email from somebody in the kernel community who >>> already tried to contact Nadia in the past but did not get any reply. >> >> Thank you also for contacting the Linux developers forum to ask >> https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1900588.html>. > > (also in CC now) > >>> I think that pushing it to non-free is formally the right thing but I >>> actually feel it's not the right thing. >> >> To know that work (that file) is free software, we need a clear grant of >> some specific license, for that work. >> >> If the work is not free, it would be incorrect to have the work in Debian. > > Is it possible that for the kernel it is instead correct because it is, > as whole, covered by its COPYING? > >> Alternatives, for complying with the Debian Free Software Guidelines with >> this package, include: >> >> * Find a credible grant of license under some GPL-compatible free >> license to that exact file. Document that explicit grant in the Debian >> package. This demonstrates the work is DFSG-free. >> >> * Convince ‘dwarves-dfsg’ upstream to replace that file with a different >> implementation (I don't know whether such an implementation exists) >> under a license compatible with the same version of GNU GPL. Document >> that explicit grant in the Debian package. This demonstrates the >> modified work is DFSG-free. > > Arnaldo, what priority would you give to this task? > >> >> * Replace that file in Debian only, with a different implementation as >> above. Document that explicit grant in the Debian package. This >> demonstrates the modified Debian package is DFSG-free. >> >> * Move the work to the ‘non-free’ area. >> >> * Remove the work altogether. >> >> Those are in descending order of (my recommended) preference. > > Thanks, > Domenico > > [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919356 > It was [pointed out] by one of our license group that [hash.h] is the same that has a GPL-2+ in [fio] which has a signed-off-by. References: [pointed out] https://bugs.gentoo.org/677586#c1 [hash.h] https://git.kernel.org/pub/scm/linux/kernel/git/axboe/fio.git/commit/hash.h?id=bdc7211e190482f0c17c109a0d90834a6611be1c [fio] https://metadata.ftp-master.debian.org/changelogs/main/f/fio/fio_3.12-2_copyright -- Kristian Fiskerstrand OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3 signature.asc Description: OpenPGP digital signature
Bug#921794: marked as done (node-cross-spawn-async: FTBFS (failing tests))
Your message dated Sun, 10 Feb 2019 22:51:52 + with message-id and subject line Bug#921794: fixed in node-cross-spawn-async 2.2.5-3 has caused the Debian Bug report #921794, regarding node-cross-spawn-async: FTBFS (failing tests) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 921794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921794 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:node-cross-spawn-async Version: 2.2.5-2 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep dh_update_autotools_config -i debian/rules override_dh_auto_test make[1]: Entering directory '/<>' nodejs test/prepare && mocha -C -R spec test/test Copied "prepare_()%!^&;, .sh" to "()%!^&;, " cross-spawn-async 1) should support shebang in executables with /usr/bin/env 2) should support shebang in executables without /usr/bin/env 3) should support shebang in executables with relative path â should support shebang in executables with relative path that starts with `..` (1538ms) 4) should support shebang in executables with extensions â should expand using PATHEXT properly â should handle commands with spaces â should handle commands with special shell chars â should handle arguments with quotes (1744ms) â should handle empty arguments (1244ms) â should handle non-string arguments (1236ms) â should handle arguments with spaces (1196ms) â should handle arguments with \" (1237ms) â should handle arguments that end with \ (1213ms) â should handle arguments that contain shell special chars (1202ms) â should handle special arguments when using echo â should handle optional args correctly (63ms) â should not mutate args nor options â should give correct exit code (1216ms) â should work with a relative command â should emit "error" and "close" if command does not exist (1024ms) â should NOT emit "error" if shebang command does not exist (1013ms) â should NOT emit "error" if the command actual exists but exited with 1 (1012ms) 19 passing (23s) 4 failing 1) cross-spawn-async should support shebang in executables with /usr/bin/env: Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19) 2) cross-spawn-async should support shebang in executables without /usr/bin/env: Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19) 3) cross-spawn-async should support shebang in executables with relative path: Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19) 4) cross-spawn-async should support shebang in executables with extensions: Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19) make[1]: *** [debian/rules:11: override_dh_auto_test] Error 4 make[1]: Leaving directory '/<>' make: *** [debian/rules:8: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) The build was made in my autobuilder with "dpkg-buildpackage -A" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-cross-spawn-async.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks. --- End Message --- --- Begin Message --- Source: node-cross-spawn-async Source-Version: 2.2.5-3 We believe that the bug you reported is fixed in the latest version of node-cross-spawn-async, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and
Bug#878337: marked as done (node-grunt-contrib-concat: FTBFS and Debci failure with node-source-map 0.6)
Your message dated Sun, 10 Feb 2019 22:51:58 + with message-id and subject line Bug#878337: fixed in node-grunt-contrib-concat 1.0.1-3 has caused the Debian Bug report #878337, regarding node-grunt-contrib-concat: FTBFS and Debci failure with node-source-map 0.6 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 878337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878337 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-grunt-contrib-concat Version: 1.0.1-2 Severity: serious Tags: buster sid https://ci.debian.net/packages/n/node-grunt-contrib-concat/unstable/amd64/ https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-grunt-contrib-concat.html ... debian/rules override_dh_auto_test make[1]: Entering directory '/build/1st/node-grunt-contrib-concat-1.0.1' grunt test Running "clean:tests" (clean) task >> 0 paths cleaned. Running "concat:default_options" (concat) task Running "concat:custom_options" (concat) task Running "concat:handling_invalid_files" (concat) task >> Source file "invalid_file/should_warn/but_not_fail" not found. Running "concat:process_function" (concat) task Running "concat:dir" (concat) task Running "concat:overwrite_one" (concat) task Running "concat:overwrite_two" (concat) task Running "concat:sourcemap_options" (concat) task Running "concat:sourcemap2_options" (concat) task Warning: original.line and original.column are not numbers -- you probably meant to omit the original mapping entirely and only map the generated position. If so, pass null for the original mapping instead of an object with empty or null values. Use --force to continue. Aborted due to warnings. debian/rules:13: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 3 --- End Message --- --- Begin Message --- Source: node-grunt-contrib-concat Source-Version: 1.0.1-3 We believe that the bug you reported is fixed in the latest version of node-grunt-contrib-concat, 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 878...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated node-grunt-contrib-concat package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 10 Feb 2019 23:10:02 +0100 Source: node-grunt-contrib-concat Binary: node-grunt-contrib-concat Architecture: source Version: 1.0.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 878337 Description: node-grunt-contrib-concat - Concatenate files Changes: node-grunt-contrib-concat (1.0.1-3) unstable; urgency=medium . * Team upload . [ Praveen Arimbrathodiyil ] * run quilt push before grunt clean * add quilt to build deps * don't fail if patches are applied already * update description, tag patch . [ Xavier Guimard ] * Bump debhelper compatibility level to 11 * Declare compliance with policy 4.3.0 * Change section to javascript * Update VCS fields to salsa * Update debian/copyright * Add description in patch * Add upstream/metadata * Refresh patch * Fix source-map ≥ 0.6 calls (Closes: #878337) * Use pkg-js-tools for tests * Add docs/* in docs Checksums-Sha1: 6be35888e509918bf58d15767975d76f5a000424 2286 node-grunt-contrib-concat_1.0.1-3.dsc 600bfc97add31a565e2befe7d88de2c447b658fa 3180 node-grunt-contrib-concat_1.0.1-3.debian.tar.xz Checksums-Sha256: f64493085b0ceceadff9bde57a48b3e1d393eb150cbfbce745c4770d8cd067ac 2286 node-grunt-contrib-concat_1.0.1-3.dsc 3574d37f80e257ebef5aec58fba00acd3d98ca112a41b718f0b5c49e5d48084b 3180 node-grunt-contrib-concat_1.0.1-3.debian.tar.xz Files: d06e505311b21f88dbc82475e0a23693 2286 javascript optional node-grunt-contrib-concat_1.0.1-3.dsc 21e9aaa92c758c5f59754b40065e1a7b 3180 javascript optional node-grunt-contrib-concat_1.0.1-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAlxgoa8ACgkQ9tdMp8mZ 7umHVQ/+JFss/POKcZohaavxi7hKe4wpSOiW91qeAvmmJoEUKDxTsoXpxiI+Be+w
Bug#917063: marked as done (golang-gopkg-cheggaaa-pb.v2 FTBFS: FAIL: TestElementBar)
Your message dated Sun, 10 Feb 2019 22:50:20 + with message-id and subject line Bug#917063: fixed in golang-gopkg-cheggaaa-pb.v2 2.0.6-3 has caused the Debian Bug report #917063, regarding golang-gopkg-cheggaaa-pb.v2 FTBFS: FAIL: TestElementBar 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.) -- 917063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917063 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-gopkg-cheggaaa-pb.v2 Version: 2.0.6-2 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-gopkg-cheggaaa-pb.v2.html ... === RUN TestElementBar --- FAIL: TestElementBar (0.43s) element_test.go:34: Unexpected result: '⚑⚒ ⚟⚐'; want: '⚑⚒⚒⚒⚟⚐' ... --- End Message --- --- Begin Message --- Source: golang-gopkg-cheggaaa-pb.v2 Source-Version: 2.0.6-3 We believe that the bug you reported is fixed in the latest version of golang-gopkg-cheggaaa-pb.v2, 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 917...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nobuhiro Iwamatsu (supplier of updated golang-gopkg-cheggaaa-pb.v2 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, 11 Feb 2019 05:52:47 +0900 Source: golang-gopkg-cheggaaa-pb.v2 Binary: golang-gopkg-cheggaaa-pb.v2-dev Architecture: source all Version: 2.0.6-3 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Nobuhiro Iwamatsu Description: golang-gopkg-cheggaaa-pb.v2-dev - simple console progress bar for Go Closes: 917063 Changes: golang-gopkg-cheggaaa-pb.v2 (2.0.6-3) unstable; urgency=medium . * Disable a unicode test. (Closes: #917063) Add d/patches/0001-Disable-a-unicode-test.patch Checksums-Sha1: 4b7574c15ba3052494654c4413b9bbb760f83400 2350 golang-gopkg-cheggaaa-pb.v2_2.0.6-3.dsc 3d9e0d71a4f911c160a5ddfc71b7a0e45d5dc7bd 3764 golang-gopkg-cheggaaa-pb.v2_2.0.6-3.debian.tar.xz 56b013e60e42e99d4c7e8e00b085f179b2690c1b 16780 golang-gopkg-cheggaaa-pb.v2-dev_2.0.6-3_all.deb f305b83a1fe164e7611756ecdd629712b198da2d 5865 golang-gopkg-cheggaaa-pb.v2_2.0.6-3_amd64.buildinfo Checksums-Sha256: f9b93ee2cc614b7a3eff2b10594ab6834a09a53b72cd703dc6022e5f5d89d548 2350 golang-gopkg-cheggaaa-pb.v2_2.0.6-3.dsc 703706b3a28b51a307f4c33668f4c550826caf3c378605ce7bfcc829df4d5b9d 3764 golang-gopkg-cheggaaa-pb.v2_2.0.6-3.debian.tar.xz 730c2760a004005ec5b6fae890554b2d3cb2f199956543b7bb1a30b4b583b356 16780 golang-gopkg-cheggaaa-pb.v2-dev_2.0.6-3_all.deb 919cd200b4e03edd1c943ba24d3e6dd0e1d4daa349e78d96daac3b37befdbc29 5865 golang-gopkg-cheggaaa-pb.v2_2.0.6-3_amd64.buildinfo Files: 4917763bafcbb42c170e322584b4f26b 2350 devel optional golang-gopkg-cheggaaa-pb.v2_2.0.6-3.dsc 730220cfdf394e49c853edebd6b146e9 3764 devel optional golang-gopkg-cheggaaa-pb.v2_2.0.6-3.debian.tar.xz 4659b6848132ccc2c7dc492afa5ec623 16780 devel optional golang-gopkg-cheggaaa-pb.v2-dev_2.0.6-3_all.deb f24a530f3a3f833f92dec009e40ffe36 5865 devel optional golang-gopkg-cheggaaa-pb.v2_2.0.6-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEXmKe5SMhlzV7hM9DMiR/u0CtH6YFAlxgosAACgkQMiR/u0Ct H6Z8Rw/8CCp0aAN845w45LwvKDAk8pgO/Shg2u124bbcjqtjD+7gwhwEf2zVcrOg XAPheuYjsHttM881LFpLn1iabn/2ohhQHIDH22DnUTpp5KdbJvI+59NJoPfXFw59 SjcNvoowkMCzemBaQgdcdvPHNEg0CGVVqyxeV9Tf1jMh9IGG/KPy7QGRxbqiL4qG mngLf9R6wxAyuSZwfADtODP4D22itw4gO9uIItupQpkBvy8WP+d5YXqVynQ1G+0L TXebbeFG/5Lhqaj76wZ0kbHojN44OlcZfc32a91LfoaoKP67Ju/HtmWwx7ZnCeTe Pm6vGyzG4lEmT+ps65Q0EgM3cvtLEY4r0cOMhRBwWwkeyDa4WP0bHY2H9k1mb95c 8GPzvn7DxBpZdiUtaP7yq1KHaFkZ/FwMxjQKBAjDkCHYcnDJ9jzt/vHb7dJoQYsP x6xnFGN3RqM/22xFbutQnKRjv+N4EHDNBpCZAtbz20AUclJRM5hP4svvepwkadFb ayKq5cBQoYIJ+b8OkViETrKFmSu/BtlOIzCFZon15PDoTBMW+d3oZa4bnDUyyvW7 04itBUTk2Lem1/U/FefZqS7LBdYoXUYv/7gjeu9IBzED0Ux+89u6uSPEfgg8eScR k3plunFhonrM4+8A+SnycLiOHqXX6+qdYKkJWu64fzPlvEMPeSI= =xIyK -END PGP SIGNATURE End Message ---
Bug#921794: Bug #921794 in node-cross-spawn-async marked as pending
Control: tag -1 pending Hello, Bug #921794 in node-cross-spawn-async 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-cross-spawn-async/commit/e116c5bb9268d7169ced5b367588489fc597f6ad Update test timeout and use pkg-js-tools Closes: #921794 (this message was generated automatically) -- Greetings https://bugs.debian.org/921794
Processed: Bug #921794 in node-cross-spawn-async marked as pending
Processing control commands: > tag -1 pending Bug #921794 [src:node-cross-spawn-async] node-cross-spawn-async: FTBFS (failing tests) Added tag(s) pending. -- 921794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921794 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919898: Bug #919898 in ceph marked as pending
Control: tag -1 pending Hello, Bug #919898 in ceph 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/ceph-team/ceph/commit/678015acbbf7e8263212b8fd191a3ef463b4058d Add Breaks/Replaces ceph-base (<< 12.2.10+dfsg1-1~) to ceph-common This is needed because the BASH completion file was moved to ceph-common in commit 8c03624e4099ea90bf0bfc9deac43f8755c6b13f. Closes: #919898 (this message was generated automatically) -- Greetings https://bugs.debian.org/919898
Processed: Bug #919898 in ceph marked as pending
Processing control commands: > tag -1 pending Bug #919898 [ceph-common] ceph-common: missing Breaks+Replaces: ceph-base (<< 12.2.10+dfsg1-1~) Added tag(s) pending. -- 919898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919898 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 913601
Processing commands for cont...@bugs.debian.org: > close 913601 Bug #913601 [src:ceph] ceph: FTBFS on mips/el: /usr/include/c++/8/bits/atomic_base.h:304: undefined reference to `__atomic_fetch_sub_8' Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 913601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913601 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#884243: marked as done (djmount: FTBFS against upnp 1.8)
Your message dated Sun, 10 Feb 2019 22:09:43 + with message-id and subject line Bug#921982: Removed package(s) from unstable has caused the Debian Bug report #884243, regarding djmount: FTBFS against upnp 1.8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 884243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884243 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: djmount Version: 0.71-7.1 Severity: important Tags: sid buster djmount FTBFS against upnp 1.8 available in experimental: | gcc -DHAVE_CONFIG_H -I. -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I../gl -pthread -I/usr/include/upnp -D_FILE_OFFSET_BITS=64 -I/usr/include/fuse -DFUSE_USE_VERSION=22 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pthread -c device_list.c | device_list.c:42:10: fatal error: upnp/LinkedList.h: No such file or directory | #include | ^~~ | compilation terminated. | Makefile:540: recipe for target 'device_list.o' failed | make[4]: *** [device_list.o] Error 1 A full log is available at https://people.debian.org/~sramacher/logs/upnp/djmount_amd64-2017-12-12T20:36:53Z.log. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Version: 0.71-7.1+rm Dear submitter, as the package djmount has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/921982 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#849574: marked as done (gtkdataboxmm: FTBFS when built with dpkg-buildpackage -A (Makefile error))
Your message dated Sun, 10 Feb 2019 22:08:53 + with message-id and subject line Bug#921973: Removed package(s) from unstable has caused the Debian Bug report #849574, regarding gtkdataboxmm: FTBFS when built with dpkg-buildpackage -A (Makefile error) 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.) -- 849574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849574 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gtkdataboxmm Version: 0.9.4-4 Severity: serious Hello Andreas. I tried to build this package with "dpkg-buildpackage -A" but it failed: [...] Generating dot graphs using 2 parallel threads... Running dot for graph 1/17 Running dot for graph 2/17 Running dot for graph 3/17 Running dot for graph 4/17 Running dot for graph 5/17 Running dot for graph 6/17 Running dot for graph 7/17 Running dot for graph 8/17 Running dot for graph 9/17 Running dot for graph 10/17 Running dot for graph 11/17 Running dot for graph 12/17 Running dot for graph 13/17 Running dot for graph 14/17 Running dot for graph 15/17 Running dot for graph 16/17 Running dot for graph 17/17 Patching output file 1/13 Patching output file 2/13 Patching output file 3/13 Patching output file 4/13 Patching output file 5/13 Patching output file 6/13 Patching output file 7/13 Patching output file 8/13 Patching output file 9/13 Patching output file 10/13 Patching output file 11/13 Patching output file 12/13 Patching output file 13/13 lookup cache used 875/65536 hits=5229 misses=1330 finished... /usr/bin/perl -- "/usr/share/mm-common/doctool/doc-postprocess.pl" 'reference/html/*.html' /usr/bin/xsltproc --stringparam book_title 'gtkdataboxmm Reference Manual' --stringparam book_name 'gtkdataboxmm' --stringparam book_base html -o reference/gtkdataboxmm.devhelp2 "/usr/share/mm-common/doctool/tagfile-to-devhelp2.xsl" reference/gtkdataboxmm.tag make[3]: *** No rule to make target 'reference/html/classGtk_1_1Widget.html', needed by 'all-local'. Stop. make[3]: Leaving directory '/<>/doc' Makefile:564: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/<>' dh_auto_build: make -j1 returned exit code 2 debian/rules:17: recipe for target 'override_dh_auto_build-indep' failed make[1]: *** [override_dh_auto_build-indep] Error 2 make[1]: Leaving directory '/<>' debian/rules:7: recipe for target 'build-indep' failed make: *** [build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2 Ii suspect this to be a genuine "dpkg-buildpackage -A" bug, because it builds ok in reproducible builds (where plain "dpkg-buildpackage" is still the norm). Thanks. --- End Message --- --- Begin Message --- Version: 0.9.4-4+rm Dear submitter, as the package gtkdataboxmm has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/921973 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#919530: marked as done (please remove Depends on common-lisp-controller)
Your message dated Sun, 10 Feb 2019 22:08:22 + with message-id and subject line Bug#921966: Removed package(s) from unstable has caused the Debian Bug report #919530, regarding please remove Depends on common-lisp-controller 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.) -- 919530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919530 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cl-awk Version: 1-4 Severity: serious Tags: patch sid buster Control: block 913649 by -1 Dear Maintainer, Please drop the Depends on common-lisp-controller. This package is obsolete, and will not ship with Buster. It has been superseded by ASDF, which is shipped by all Common Lisp implementations in Debian. Dropping the dependency and the postinst and prerm scripts should be enough. ASDF is able to locate the files where they are installed (i.e. under /usr/share/common-lisp/). Best, -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name ⠈⠳⣄ http://www.debian.org --- End Message --- --- Begin Message --- Version: 1-4+rm Dear submitter, as the package cl-awk has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/921966 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#809252: marked as done (node-cli: CVE-2016-10538)
Your message dated Sun, 10 Feb 2019 22:07:52 + with message-id and subject line Bug#921956: Removed package(s) from unstable has caused the Debian Bug report #809252, regarding node-cli: CVE-2016-10538 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.) -- 809252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809252 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-cli Version: 0.4.4~20120516-1 Severity: critical Tags: security Dear Maintainer, The `node-cli` library makes insecure use of the following two temporary files: lock_file = '/tmp/' + cli.app + '.pid', log_file = '/tmp/' + cli.app + '.log'; These allow overwriting files that the starting-user has permission to modify. -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Version: 0.4.4~20120516-1+rm Dear submitter, as the package node-cli has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/921956 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Processed: closing 864161
Processing commands for cont...@bugs.debian.org: > close 864161 Bug #864161 [ceph-mon] ceph-mon: missing Breaks+Replaces: ceph-common (<< 10) Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 864161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864161 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#873719: [Debichem-devel] Bug#873719: /usr/bin/sc-libtool: Command not found
Hi Andreas, On Sat, Feb 09, 2019 at 03:32:25PM +0100, Andreas Beckmann wrote: > I just backported the fix to stretch, prepared a stretch-pu request and > uploaded the package: https://bugs.debian.org/921864 Many thanks! Michael
Bug#921131: CVE-2018-10897
Hi Markus! On Sun, Feb 10, 2019 at 11:15:35 +0100, Markus Frosch wrote: > I'm not sure how active Mike is currently. I'm quite active, but I have not touched the rpm/yum related packages in years since they haven't seen much upstream activity. I'm also honestly not very interested in rpm/yum currently. I should have given these packages up for adoption by now, better late than never. > Since I'm using the package in a multi distro build system, I would > proceed with uploading a fix and join as co-maintainer. > > I already created a salsa project: > https://salsa.debian.org/debian/yum-utils > > @Mike: Can I get a short approval? There is an RPM packaging team that this package should be maintained with * https://salsa.debian.org/pkg-rpm-team * https://tracker.debian.org/teams/pkg-rpm/ * https://wiki.debian.org/Teams/pkg-rpm Can you move your imported repository to the team group on salsa? There used to be a mailing list on lists.alioth.d.o, I don't think there is a replacement team list. > Also: Is the experimental upload ready for buster? I think so, I think it was only experimental because of a freeze. I suggest I file an RFA for yum-utils and Cc you, we can discuss further there, ok? Do you have any interest in the related packages createrepo, deltarpm, and yum-metadata-parser? Also thank you Holger for the nmu and fixing this bug so quickly. -- mike signature.asc Description: PGP signature
Bug#884243: djmount status, two patches and about conversion to libupnp 1.8
Control: affects 921982 + djmount Hello, On Mon, Jan 21, 2019 at 08:17:24PM +0100, Uwe Kleine-König wrote: > I will report a request to remove djmount from unstable in February > unless someone opposes (and does to work to convert it to libupnp-1.8). I did this now, but forgot to Cc: this bug. The RM bug is #921982. Best regards Uwe signature.asc Description: PGP signature
Processed: bug 921542 is forwarded to https://marc.info/?l=linux-netdev=154981389223402=2
Processing commands for cont...@bugs.debian.org: > forwarded 921542 https://marc.info/?l=linux-netdev=154981389223402=2 Bug #921542 [src:linux] tc qdisc kernel crash Set Bug forwarded-to-address to 'https://marc.info/?l=linux-netdev=154981389223402=2'. > thanks Stopping processing here. Please contact me if you need assistance. -- 921542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921542 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921979: lmfit-py: FTBFS randomly (test_covariance_matrix.test_bounded_parameters fails)
Package: src:lmfit-py Version: 0.9.11+dfsg-1 Severity: serious Tags: ftbfs patch Hello Andreas et al. I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --with python2,python3,sphinxdoc --buildsystem=pybuild dh_update_autotools_config -i -O--buildsystem=pybuild dh_autoreconf -i -O--buildsystem=pybuild dh_auto_configure -i -O--buildsystem=pybuild I: pybuild base:217: python2.7 setup.py config running config I: pybuild base:217: python3.7 setup.py config running config debian/rules override_dh_auto_build make[1]: Entering directory '/<>/lmfit-py-0.9.11+dfsg' dh_auto_build I: pybuild base:217: /usr/bin/python setup.py build running build running build_py creating /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit copying lmfit/lineshapes.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit copying lmfit/models.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit copying lmfit/jsonutils.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit copying lmfit/__init__.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit copying lmfit/printfuncs.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit copying lmfit/_ampgo.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit copying lmfit/model.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit copying lmfit/minimizer.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit copying lmfit/parameter.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit copying lmfit/confidence.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit copying lmfit/_version.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit creating /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit/ui copying lmfit/ui/__init__.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit/ui copying lmfit/ui/ipy_fitter.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit/ui copying lmfit/ui/basefitter.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit/ui UPDATING /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit/_version.py set /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit/_version.py to '0.9.11' I: pybuild pybuild:295: cp -r NIST_STRD /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build I: pybuild base:217: /usr/bin/python3 setup.py build running build running build_py creating /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit copying lmfit/lineshapes.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit copying lmfit/models.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit copying lmfit/jsonutils.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit copying lmfit/__init__.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit copying lmfit/printfuncs.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit copying lmfit/_ampgo.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit copying lmfit/model.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit copying lmfit/minimizer.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit copying lmfit/parameter.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit copying lmfit/confidence.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit copying lmfit/_version.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit creating /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit/ui copying lmfit/ui/__init__.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit/ui copying lmfit/ui/ipy_fitter.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit/ui copying lmfit/ui/basefitter.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit/ui UPDATING /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit/_version.py set /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit/_version.py to '0.9.11' I: pybuild pybuild:295: cp -r NIST_STRD /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build PYTHONPATH=. http_proxy='localhost' sphinx-build -N -bhtml doc/ build/html # HTML generator Running Sphinx v1.7.9 making output directory... loading pickled environment... not yet created loading intersphinx inventory from https://docs.python.org/2/objects.inv... loading intersphinx inventory from https://docs.scipy.org/doc/numpy/objects.inv... loading intersphinx inventory from https://docs.scipy.org/doc/scipy/reference/objects.inv... building [mo]: targets for 0 po files that are out of date building [html]:
Bug#917797:
Ah yes this was indeed fixed by 2.37-1 or something around there but we forgot to mention this bug in the changelog. Thanks for the reminder!
Processed: closing 917797
Processing commands for cont...@bugs.debian.org: > close 917797 Bug #917797 [src:snapd] snapd: FTBFS: too many arguments in call to activation.Listeners Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 917797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917797 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921953: apacheds: Further analysis
Hi. Looked at it a bit more and found the following things. ApacheDS have moved it's configuration to a dynamic schema based setup, like OpenLDAP. As part of the startup it tries to migrate the config.ldif to a folder based setup in ou=config. Since the user it runs as doesn't have write permission for /etc/apacheds it fails and then gives up starting. Additionally, once the permission issue is sorted the current systemd unit checks for the existance of the config.ldif file which will be renamed as part of the migration so it will not start the server. The patch below fixes both but I'm not sure if services are supposed to write in /etc. -- diff -ur apache-directory-server-2.0.0~M15/debian/apacheds.postinst apache-directory-server-2.0.0~M15-mod/debian/apacheds.postinst --- apache-directory-server-2.0.0~M15/debian/apacheds.postinst 2015-07-01 22:22:10.0 +0200 +++ apache-directory-server-2.0.0~M15-mod/debian/apacheds.postinst 2019-02-10 21:07:19.687924216 +0100 @@ -32,7 +32,9 @@ # Fix directory permissions chown -R $APACHEDS_USER:$APACHEDS_GROUP /var/log/apacheds || true chown -R $APACHEDS_USER:$APACHEDS_GROUP /var/lib/apacheds || true +chown $APACHEDS_USER:$APACHEDS_GROUP /etc/apacheds chown $APACHEDS_USER:$APACHEDS_GROUP /etc/apacheds/* +chmod 640 /etc/apacheds chmod 640 /etc/apacheds/* ;; diff -ur apache-directory-server-2.0.0~M15/debian/apacheds.service apache-directory-server-2.0.0~M15-mod/debian/apacheds.service --- apache-directory-server-2.0.0~M15/debian/apacheds.service 2015-07-01 22:22:10.0 +0200 +++ apache-directory-server-2.0.0~M15-mod/debian/apacheds.service 2019-02-10 21:04:28.228844408 +0100 @@ -1,7 +1,8 @@ [Unit] Description=Apache Directory Server After=network.target -ConditionPathExists=/etc/apacheds/config.ldif +ConditionPathExists=|/etc/apacheds/config.ldif +ConditionPathIsDirectory=|/etc/apacheds/ou=config [Service] Type=simple Regards, Johan
Processed: Re: Bug#920995: spatialite: hangs during virtualknn test
Processing control commands: > tags -1 fixed-upstream Bug #920995 [src:spatialite] spatialite: hangs during virtualknn test Added tag(s) fixed-upstream. -- 920995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920995 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#920995: spatialite: hangs during virtualknn test
Control: tags -1 fixed-upstream On 1/31/19 2:17 PM, Bas Couwenberg wrote: > On 2019-01-31 13:36, Andreas Beckmann wrote: >> during a test rebuild of spatialite/experimental I noticed that it hangs >> during the virtualknn test. After killing that process the build >> continued and succeeded. I think this has so far happened more than >> once, not sure if on amd64 or or i386 or both. > > I've confirmed this issue in an amd64 experimental chroot, and forwarded > the issue upstream: > > https://www.gaia-gis.it/fossil/libspatialite/tktview/2cad2f4b9df468fa062f624638d4ac6072611821 Upstream has tracked down the issue and committed a fix: https://www.gaia-gis.it/fossil/libspatialite/ci/90180e065dfdd8fa?sbs=0 A new (beta) release should be published next week, so I'll wait for that instead of adding a patch with the fix since the issue only affects the package in experimental. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Processed: Re: bugwarrior: FTBFS (failing tests)
Processing commands for cont...@bugs.debian.org:
> tag 921777 + patch
Bug #921777 {Done: Jochen Sprickerhof } [src:bugwarrior]
bugwarrior: FTBFS (failing tests)
Added tag(s) patch.
> usertag 921777 + bsp-2019-02-de-berlin
User is nico...@fjasle.eu
There were no usertags set.
Usertags are now: bsp-2019-02-de-berlin.
> thank you
Stopping processing here.
Please contact me if you need assistance.
--
921777: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921777
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#921538: Fails to start since upgrade to 1.9.0-1
Package: unbound
Followup-For: Bug #921538
I found the that problem is that 1.9.0-1 does a chroot("/etc/unbound") even
though
there is no chroot option in the config files.
Once that occurs, it cannot see files like /var/lib/unbound/root.key et alia.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.15.0-2-amd64 (SMP w/1 CPU core)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages unbound depends on:
ii adduser 3.118
ii dns-root-data 2018091102
ii libc6 2.28-6
ii libevent-2.1-6 2.1.8-stable-4
ii libfstrm0 0.4.0-1
ii libprotobuf-c1 1.3.1-1+b1
ii libpython3.73.7.2-2
ii libssl1.1 1.1.1a-1
ii libsystemd0 240-5
ii lsb-base10.2018112800
ii openssl 1.1.1a-1
ii unbound-anchor 1.8.1-1+b1
unbound recommends no packages.
Versions of packages unbound suggests:
pn apparmor
-- no debconf information
Processed: mosquitto: CVE-2018-12546 CVE-2018-12550 CVE-2018-12551
Processing control commands: > found -1 1.4.10-3+deb9u2 Bug #921976 [src:mosquitto] mosquitto: CVE-2018-12546 CVE-2018-12550 CVE-2018-12551 Marked as found in versions mosquitto/1.4.10-3+deb9u2. > found -1 1.4.10-3 Bug #921976 [src:mosquitto] mosquitto: CVE-2018-12546 CVE-2018-12550 CVE-2018-12551 Marked as found in versions mosquitto/1.4.10-3. > fixed -1 1.4.10-3+deb9u3 Bug #921976 [src:mosquitto] mosquitto: CVE-2018-12546 CVE-2018-12550 CVE-2018-12551 Marked as fixed in versions mosquitto/1.4.10-3+deb9u3. -- 921976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921976 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921976: mosquitto: CVE-2018-12546 CVE-2018-12550 CVE-2018-12551
Source: mosquitto Version: 1.5.5-1.1 Severity: grave Tags: security upstream Control: found -1 1.4.10-3+deb9u2 Control: found -1 1.4.10-3 Control: fixed -1 1.4.10-3+deb9u3 Hi, The following vulnerabilities were published for mosquitto, fixed in DSA with 1.4.10-3+deb9u3 but yet open for buster. If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2018-12546 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12546 [1] https://security-tracker.debian.org/tracker/CVE-2018-12550 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12550 [2] https://security-tracker.debian.org/tracker/CVE-2018-12551 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12551 Regards, Salvatore
Processed: tagging 921969, found 921969 in 0.5.2-426-gc5ad4e4+dfsg5-4 ...
Processing commands for cont...@bugs.debian.org: > tags 921969 + upstream Bug #921969 [src:gpac] CVE-2018-20760 CVE-2018-20761 CVE-2018-20762 CVE-2018-20763 Added tag(s) upstream. > found 921969 0.5.2-426-gc5ad4e4+dfsg5-4 Bug #921969 [src:gpac] CVE-2018-20760 CVE-2018-20761 CVE-2018-20762 CVE-2018-20763 Marked as found in versions gpac/0.5.2-426-gc5ad4e4+dfsg5-4. > found 921969 0.5.2-426-gc5ad4e4+dfsg5-3 Bug #921969 [src:gpac] CVE-2018-20760 CVE-2018-20761 CVE-2018-20762 CVE-2018-20763 Marked as found in versions gpac/0.5.2-426-gc5ad4e4+dfsg5-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 921969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921969 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#904762: marked as done (vulture: missing dependency on python3-pkg-resources)
Your message dated Sun, 10 Feb 2019 19:17:11 +
with message-id
and subject line Bug#904762: fixed in vulture 0.11-1+deb9u1
has caused the Debian Bug report #904762,
regarding vulture: missing dependency on python3-pkg-resources
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.)
--
904762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904762
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vulture
Version: 0.11-1
Severity: serious
stretch $ vulture
Traceback (most recent call last):
File "/usr/bin/vulture", line 6, in
from pkg_resources import load_entry_point
ImportError: No module named 'pkg_resources'
sid $ vulture
Traceback (most recent call last):
File "/usr/bin/vulture", line 6, in
from pkg_resources import load_entry_point
ModuleNotFoundError: No module named 'pkg_resources'
Andreas
--- End Message ---
--- Begin Message ---
Source: vulture
Source-Version: 0.11-1+deb9u1
We believe that the bug you reported is fixed in the latest version of
vulture, 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 904...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann (supplier of updated vulture package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 10 Feb 2019 02:42:08 +0100
Source: vulture
Binary: vulture
Architecture: source
Version: 0.11-1+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Python Applications Packaging Team
Changed-By: Andreas Beckmann
Description:
vulture- scans for unused ("dead") code in a Python program
Closes: 904762
Changes:
vulture (0.11-1+deb9u1) stretch; urgency=medium
.
[ Andreas Beckmann ]
* Non-maintainer upload.
* Backport the dependency fix from 0.21-1.1.
.
[ Adrian Bunk ]
* Add the missing dependency on python3-pkg-resources.
(Closes: #904762)
* Fix the test dependencies.
Checksums-Sha1:
1112fdf02b82976e3f8dc96c7fb1c2cebf531513 2113 vulture_0.11-1+deb9u1.dsc
949e61cefdfe9a2ff4cbd1c7284c2c0a6f762878 3648
vulture_0.11-1+deb9u1.debian.tar.xz
c04e4916140b651a7283debb08bd865b3422f762 6177
vulture_0.11-1+deb9u1_source.buildinfo
Checksums-Sha256:
861d765f018a11c940f61b4be18e4283bfd27e43a51416698020ebd58dc71a58 2113
vulture_0.11-1+deb9u1.dsc
b1fe777174ffef4f7d2a4932a25a74e8edad342c4bdf76b8b8782ac5b0baef64 3648
vulture_0.11-1+deb9u1.debian.tar.xz
d767a85b980dd122b33a04a4cd47a5e26378177ab98e6f8d56632c4251afcdfb 6177
vulture_0.11-1+deb9u1_source.buildinfo
Files:
e3b08a19046c86d2fc2020f4a69ab453 2113 devel optional vulture_0.11-1+deb9u1.dsc
08bd8f26db313d3477aa9984ca4248f2 3648 devel optional
vulture_0.11-1+deb9u1.debian.tar.xz
f6192a906b93bf2ab9e07025e63641d2 6177 devel optional
vulture_0.11-1+deb9u1_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAlxfg/kQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCMc/D/sEIrsOFzKjQLp92wP53Z33LjlXgtwVCqp/
EvOtCStFf4s5vMW4V/GKDN5m+/1swUZodGqUiTicFlFZuHKG6hzwEMDfJk7qpN5M
iBZQVzkXhx5C0JpWxDRNZozBhmgWtLARP0nNAjBWTXhudA5aB7oMc1kTgmKGyt/J
QPqAZdzAJ3NmJhX+MnYncTW8JEkxtBiQY/cF8/n2zcT6oMvps93GyWMJve+tVeg+
KJzZTRd0q+NUbUpzRo/nudlan1Z2WNgmCSRbmBfTs6/6aiiNObMn+OkblWDdWPdI
g++I03c7K57cEXtnCPn5N/5RiSKe7RXwuk0K7LFTMExZMSK5iWibVizxBaNT+Hnq
SFLyLSp/GlQJF9wWVLYaw17d9IgmfkRcmrz34VuOCVlUePHsO4UfHGKALnR3VPfR
ltSAgXdUR6wZQZDe7YYpcXT4lht9rNEWA6mvRzkP1PFJR5fx1sNgoflYWLbatnaE
uGHE+HwS7D1JvVsvIL3PNTVZS58V9tT5B34tYZbXSvN15WruCxpCkPssDmjk+mGe
+xTPQPnYBO6hozWm/C3bcqFr0rMACTKIFFEPhqzQvOrS8PQnHZi1uzT2KgwCB4Yw
gk0QIWMFaQpuZTZj+Y7y/xq1adPjVEmiTKJpNcOyIQap5XPNTVDuoq1pkzTsRBDM
nqMf8SNU4Q==
=vf71
-END PGP SIGNATURE End Message ---
Bug#916858: marked as done (supercollider-emacs: fails to install with xemacs21)
Your message dated Sun, 10 Feb 2019 19:17:10 +
with message-id
and subject line Bug#916858: fixed in supercollider 1:3.7.0~repack-4+deb9u1
has caused the Debian Bug report #916858,
regarding supercollider-emacs: fails to install with xemacs21
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.)
--
916858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916858
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: supercollider-emacs
Version: 1:3.7.0~repack-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 1:3.6.6~repack-2-1
Control: found -1 1:3.8.0~repack-2
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
>From the attached log (scroll to the bottom...):
Setting up supercollider-emacs (1:3.7.0~repack-4) ...
Install supercollider-emacs for xemacs21
install/SuperCollider: Handling install for emacsen flavor xemacs21
Loading /usr/share/emacs/site-lisp/debian-startup...
Loading 00debian...
Loading site-start...
Loading 00debian-vars...
Loading 50supercollider-emacs...
Error while loading 50supercollider-emacs: Invalid read syntax: "#"
Compiling /usr/share/xemacs21/site-lisp/SuperCollider/sclang-browser.el...
While compiling toplevel forms in file
/usr/share/xemacs21/site-lisp/SuperCollider/sclang-browser.el:
!! Invalid read syntax (("#"))
>>Error occurred processing sclang-browser.el:
Invalid read syntax: "#"
Compiling /usr/share/xemacs21/site-lisp/SuperCollider/sclang-dev.el...
While compiling toplevel forms in file
/usr/share/xemacs21/site-lisp/SuperCollider/sclang-dev.el:
!! Invalid read syntax (("#"))
>>Error occurred processing sclang-dev.el:
Invalid read syntax: "#"
Compiling /usr/share/xemacs21/site-lisp/SuperCollider/sclang-document.el...
Wrote /usr/share/xemacs21/site-lisp/SuperCollider/sclang-document.elc
Compiling /usr/share/xemacs21/site-lisp/SuperCollider/sclang-help.el...
While compiling toplevel forms in file
/usr/share/xemacs21/site-lisp/SuperCollider/sclang-help.el:
!! Invalid read syntax (("#"))
>>Error occurred processing sclang-help.el:
Invalid read syntax: "#"
Compiling /usr/share/xemacs21/site-lisp/SuperCollider/sclang-interp.el...
While compiling toplevel forms in file
/usr/share/xemacs21/site-lisp/SuperCollider/sclang-interp.el:
!! Invalid read syntax (("#"))
>>Error occurred processing sclang-interp.el:
Invalid read syntax: "#"
Compiling /usr/share/xemacs21/site-lisp/SuperCollider/sclang-keys.el...
While compiling toplevel forms in file
/usr/share/xemacs21/site-lisp/SuperCollider/sclang-keys.el:
!! Invalid read syntax (("#"))
>>Error occurred processing sclang-keys.el:
Invalid read syntax: "#"
Compiling /usr/share/xemacs21/site-lisp/SuperCollider/sclang-language.el...
While compiling toplevel forms in file
/usr/share/xemacs21/site-lisp/SuperCollider/sclang-language.el:
!! Invalid read syntax (("#"))
>>Error occurred processing sclang-language.el:
Invalid read syntax: "#"
Compiling /usr/share/xemacs21/site-lisp/SuperCollider/sclang-menu.el...
Wrote /usr/share/xemacs21/site-lisp/SuperCollider/sclang-menu.elc
Compiling /usr/share/xemacs21/site-lisp/SuperCollider/sclang-minor-mode.el...
While compiling toplevel forms in file
/usr/share/xemacs21/site-lisp/SuperCollider/sclang-minor-mode.el:
!! Invalid read syntax (("#"))
>>Error occurred processing sclang-minor-mode.el:
Invalid read syntax: "#"
Compiling /usr/share/xemacs21/site-lisp/SuperCollider/sclang-mode.el...
While compiling toplevel forms in file
/usr/share/xemacs21/site-lisp/SuperCollider/sclang-mode.el:
!! Invalid read syntax (("#"))
>>Error occurred processing sclang-mode.el:
Invalid read syntax: "#"
Compiling /usr/share/xemacs21/site-lisp/SuperCollider/sclang-server.el...
While compiling toplevel forms in file
/usr/share/xemacs21/site-lisp/SuperCollider/sclang-server.el:
!! Invalid read syntax (("#"))
>>Error occurred processing sclang-server.el:
Invalid read syntax: "#"
Compiling /usr/share/xemacs21/site-lisp/SuperCollider/sclang-util.el...
While compiling toplevel forms in file
/usr/share/xemacs21/site-lisp/SuperCollider/sclang-util.el:
!! Invalid read syntax (("#"))
>>Error occurred processing sclang-util.el:
Invalid read syntax: "#"
Compiling /usr/share/xemacs21/site-lisp/SuperCollider/sclang-vars.el...
Bug#921667: [pkg-lxc-devel] Bug#921667: lxc, lava-dev: lxc fails to install along lava-dev --install-recommends
On Sun, Feb 10, 2019 at 12:13:43AM +0100, Pierre-Elliott Bécue wrote: > Le samedi 09 février 2019 à 22:19:13+0100, Andreas Beckmann a écrit : > > On 2019-02-09 21:51, Pierre-Elliott Bécue wrote: > > > I'm not sure that there is something we can do regarding lxc. Am I > > > wrong? > > > > You could try to figure out why lxc explodes. > > Probably some package places some configuration file at some location > > > > > > Andreas > > > > PS: I should be able to get a shell in the chroot after the failure > > occurred, in case you want me to collect some information. > > That's a good idea. This error is not clear at all to me. I can reproduce this on a clean chroot (but not on a clean VM) > Could you please try to run the .postinst of lxc manually with a set -x? > The goal would be to check which part explodes. 8<8<8<- Setting up lxc (1:3.1.0+really3.0.3-2) ... + . /usr/share/debconf/confmodule + [ ! ] + PERL_DL_NONLAZY=1 + export PERL_DL_NONLAZY + [ ] + exec /usr/share/debconf/frontend /var/lib/dpkg/info/lxc.postinst configure debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.) debconf: falling back to frontend: Readline + . /usr/share/debconf/confmodule + [ ! 1 ] + [ -z ] + exec + [ ] + exec + DEBCONF_REDIR=1 + export DEBCONF_REDIR + upgrade configure + [ ! -z ] + [ -z ] + which apparmor_parser + [ -e /etc/apparmor.d/lxc-containers ] + apparmor_parser -r -W -T /etc/apparmor.d/lxc-containers Warning: unable to find a suitable fs in /proc/mounts, is it mounted? Use --subdomainfs to override. dpkg: error processing package lxc (--configure): installed lxc package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of lxc-templates: lxc-templates depends on lxc (>= 1:3.0.2-1~exp+1); however: Package lxc is not configured yet. dpkg: error processing package lxc-templates (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: lxc lxc-templates E: Sub-process /usr/bin/dpkg returned an error code (1) 8<8<8<- signature.asc Description: PGP signature
Bug#741464: marked as done (grub-pc-bin: freezes after "terminal_input at_keyboard")
Your message dated Sun, 10 Feb 2019 19:19:46 +
with message-id
and subject line Bug#741464: fixed in grub2 2.02+dfsg1-11
has caused the Debian Bug report #741464,
regarding grub-pc-bin: freezes after "terminal_input at_keyboard"
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.)
--
741464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741464
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grub-pc-bin
Version: 2.02~beta2-7
Severity: critical
After upgrading the grub packages and rebooting my laptop, grub
displayed the boot menu and then was hung. The countdown before
booting the default kernel was not started and grub did not accept any
keyboard input.
I had to boot a rescue system from a USB stick, chroot into my
installation and downgrade to 2.00-22 to get back to a working system.
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/sda5 / ext4 rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/sda1 /boot ext2 rw,nosuid,nodev,relatime 0 0
*** END /proc/mounts
*** BEGIN /boot/grub/device.map
(hd0) /dev/disk/by-id/ata-HTS541060G9AT00_MPB3PAXGKN2KZG
*** END /boot/grub/device.map
*** BEGIN /boot/grub/grub.cfg
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
}
terminal_input console
terminal_output console
set timeout=10
### END /etc/grub.d/00_header ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux (Kernel 3.13.6-kms)' {
echo'Loading Linux 3.13.6-kms ...'
linux /vmlinuz-3.13.6-kms root=/dev/sda5 ro quiet init=/bin/systemd
echo'Loading initial ramdisk ...'
initrd /initrd.img-3.13.6-kms
}
menuentry 'Debian GNU/Linux (Kernel 3.13.6-kms, Sysvinit)' {
echo'Loading Linux 3.13.6-kms ...'
linux /vmlinuz-3.13.6-kms root=/dev/sda5 ro quiet init 2
echo'Loading initial ramdisk ...'
initrd /initrd.img-3.13.6-kms
}
menuentry 'Debian GNU/Linux (Kernel 3.14.0-rc6-kms)' {
echo'Loading Linux 3.14.0-rc6-kms ...'
linux /vmlinuz-3.14.0-rc6-kms root=/dev/sda5 ro quiet
init=/bin/systemd
echo'Loading initial ramdisk ...'
initrd /initrd.img-3.14.0-rc6-kms
}
menuentry 'Debian GNU/Linux (Kernel 3.14.0-rc6-kms, Sysvinit)' {
echo'Loading Linux 3.14.0-rc6-kms ...'
linux /vmlinuz-3.14.0-rc6-kms root=/dev/sda5 ro quiet init 2
echo'Loading initial ramdisk ...'
initrd /initrd.img-3.14.0-rc6-kms
}
menuentry 'Debian GNU/Linux (Kernel 3.12.14-kms)' {
echo'Loading Linux 3.12.14-kms ...'
linux /vmlinuz-3.12.14-kms root=/dev/sda5 ro quiet init=/bin/systemd
echo'Loading initial ramdisk ...'
initrd /initrd.img-3.12.14-kms
}
menuentry 'Debian GNU/Linux (Kernel 3.12.14-kms, Sysvinit)' {
echo'Loading Linux 3.12.14-kms ...'
linux /vmlinuz-3.12.14-kms root=/dev/sda5 ro quiet init 2
echo'Loading initial ramdisk ...'
initrd /initrd.img-3.12.14-kms
}
menuentry 'Debian GNU/Linux (Kernel 3.10.33-kms)' {
echo'Loading Linux 3.10.33-kms ...'
linux /vmlinuz-3.10.33-kms root=/dev/sda5 ro quiet init=/bin/systemd
echo'Loading initial ramdisk ...'
initrd /initrd.img-3.10.33-kms
}
menuentry 'Debian GNU/Linux (Kernel 3.10.33-kms, Sysvinit)' {
echo'Loading Linux 3.10.33-kms ...'
linux /vmlinuz-3.10.33-kms root=/dev/sda5 ro quiet init 2
echo'Loading initial ramdisk ...'
initrd /initrd.img-3.10.33-kms
}
menuentry 'Debian GNU/Linux (Kernel 3.4.83-kms)' {
echo'Loading Linux 3.4.83-kms ...'
linux /vmlinuz-3.4.83-kms root=/dev/sda5 ro quiet init=/bin/systemd
echo'Loading initial ramdisk ...'
initrd /initrd.img-3.4.83-kms
}
menuentry 'Debian GNU/Linux (Kernel 3.4.83-kms, Sysvinit)' {
echo'Loading Linux 3.4.83-kms ...'
linux /vmlinuz-3.4.83-kms
Bug#826020: marked as done (graphite-api.service: RequireMountsFor needs to be RequiresMountsFor)
Your message dated Sun, 10 Feb 2019 19:17:09 + with message-id and subject line Bug#826020: fixed in graphite-api 1.1.3-2+deb9u1 has caused the Debian Bug report #826020, regarding graphite-api.service: RequireMountsFor needs to be RequiresMountsFor 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.) -- 826020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826020 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: graphite-api Version: 1.1.3-1 Severity: normal Hi, As the title says, the systemd service file contains a mistake. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.6.0x220-1 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages graphite-api depends on: ii adduser3.114 ii python3-cairocffi 0.7.2-1 ii python3-flask 0.10.1-2 ii python3-pyparsing 2.1.4+dfsg1-1 ii python3-six1.10.0-3 ii python3-structlog 16.0.0-1 ii python3-tz 2015.7+dfsg-0.1 ii python3-tzlocal1.2.2-1 ii python3-yaml 3.11-3+b1 pn python3:any graphite-api recommends no packages. Versions of packages graphite-api suggests: ii gunicorn3 19.5.0-1 -- no debconf information --- End Message --- --- Begin Message --- Source: graphite-api Source-Version: 1.1.3-2+deb9u1 We believe that the bug you reported is fixed in the latest version of graphite-api, 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 826...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated graphite-api package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 10 Feb 2019 02:29:37 +0100 Source: graphite-api Binary: graphite-api Architecture: source Version: 1.1.3-2+deb9u1 Distribution: stretch Urgency: medium Maintainer: Debian Graphite Group Changed-By: Andreas Beckmann Description: graphite-api - Enterprise Scalable Realtime Graphing (API-only frontend) Closes: 826020 Changes: graphite-api (1.1.3-2+deb9u1) stretch; urgency=medium . [ Andreas Beckmann ] * Non-maintainer upload. * Backport spelling fix from 1.1.3-3. (Closes: #826020) . [ Vincent Bernat ] * d/service: fix RequiresMountsFor spelling. Checksums-Sha1: c86b541c05043f46a6a540241f9cf14d64e75b75 2264 graphite-api_1.1.3-2+deb9u1.dsc ef24044f9cab222db9b813acfeb5e1cf6b46e801 4284 graphite-api_1.1.3-2+deb9u1.debian.tar.xz 75cff0719a71dbafc2e003392576afa72cdf4ae8 8048 graphite-api_1.1.3-2+deb9u1_source.buildinfo Checksums-Sha256: 3fed56180fbded3b0d29470236f20afc5e1cb508a00fa1fbd67f963929bad8b9 2264 graphite-api_1.1.3-2+deb9u1.dsc 40a87c3dd3939ea1af4ea741a9b190b3a4fd42977eeb14dcadefd999dbb5222f 4284 graphite-api_1.1.3-2+deb9u1.debian.tar.xz 4c11c4a2546bc8aeb1e27d1d459adfe9a375a447f56a1205e036c770053ca2c6 8048 graphite-api_1.1.3-2+deb9u1_source.buildinfo Files: 4417a8a19b4219edbb8378e9510659dc 2264 web extra graphite-api_1.1.3-2+deb9u1.dsc 063eecdec806b6af40bdaab5fc12c67c 4284 web extra graphite-api_1.1.3-2+deb9u1.debian.tar.xz dd673776c411590cbbd6460bc3508216 8048 web extra graphite-api_1.1.3-2+deb9u1_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAlxff4EQHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCEIYEACD8IrSV0eJgENeHklxCWT2h59w86z0xfeG b0qqmjdBMZSk0sRYNmTBbyEgrN8jP7dZ86IPrOcjmh6+F7vyqZJRZTMq8BMuej3k jflna0QVNBbUUuA+UnZoxqkY5Tnp5vk2Sbat6iuoBcoSTlCGW9DVHKvuJqdYEqCl 6mg50UcN+9pJKOHuvvAvr1ccVEZkvWH1ymWDU+whL/dpRDCKP1bVn5RbAGs98NtR tncFzJpC1bOLuvGNrSSLwdKvrQbCwDpVYn2opTydSKUh4FMiLEXdAxoov5h/EewJ 0AFE+NSc7sVFED6bKg+bp3SQbx947Gdi5mJpz2S6F+uGXOddPmudHHVRqJb6vR7C Sev51zpqzYTVbAj7AfaSGDVDlvcUOf+XHFJAMZ+hVzswWsbHm0KMHHLqglBPx2It VrbK08n0PzA/2VVyap7KkiY18bP7chahliWGKpQEALP0gdmY1Q6KLv5tMZH9ecPz OJn+6qnP7e2pkMrdLQi2OlF1bOeSpzTmRSnkcXjScd5usYbWLtRhO/xMKglBy6Wv 2VPt32tcvzT0jXptZAHclaUk21pHjtYWtO2IVVUY5AHNyag/noRYqUI04yHoEpQ/
Bug#918167: marked as done (Broken in stable)
Your message dated Sun, 10 Feb 2019 19:17:08 + with message-id and subject line Bug#918167: fixed in compactheader 2.1.6-1~deb9u1 has caused the Debian Bug report #918167, regarding Broken in stable 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.) -- 918167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918167 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xul-ext-compactheader Version: 2.1.6-1 Severity: grave The plugin is broken with Thunderbird 60 in stretch and sid, after installation it's disabled and only prints "CompactHeader is incompatible with Thunderbird 60.4". Either the version from sid could be backported or alternatively the extension could be removed from stable by the next point release. Cheers, Moritz --- End Message --- --- Begin Message --- Source: compactheader Source-Version: 2.1.6-1~deb9u1 We believe that the bug you reported is fixed in the latest version of compactheader, 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 918...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Carsten Schoenert (supplier of updated compactheader package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 05 Jan 2019 09:45:37 +0100 Source: compactheader Binary: xul-ext-compactheader Architecture: source all Version: 2.1.6-1~deb9u1 Distribution: stretch Urgency: medium Maintainer: Debian Mozilla Extension Maintainers Changed-By: Carsten Schoenert Description: xul-ext-compactheader - Thunderbird extension to reduce header size to one or two lines Closes: 918167 Changes: compactheader (2.1.6-1~deb9u1) stretch; urgency=medium . [ Carsten Schoenert ] * Rebuild for Stretch (Closes: #918167) * [93f8afe] debhelper: decrease to version available in stretch * [8fd6a50] d/compat: decrease accordingly to version 10 Checksums-Sha1: 2293bcdc19686fce07d25fb1491c07cd8b71251b 2090 compactheader_2.1.6-1~deb9u1.dsc c6d524ddb487c89ae7f8bce3633619b9413d5092 17620 compactheader_2.1.6-1~deb9u1.debian.tar.xz 7733ae3e0815fd1c3b16477607c105fdc4b440e5 7280 compactheader_2.1.6-1~deb9u1_amd64.buildinfo 40eb8b155f5502d5d75298a09e3cbc1c8573f44b 216218 xul-ext-compactheader_2.1.6-1~deb9u1_all.deb Checksums-Sha256: 2a63a0937f5a66959c191d43a118e650ff6418b49dc71cc9a000984c00b66c15 2090 compactheader_2.1.6-1~deb9u1.dsc 0bb07cafac2bf426dee4c39f067cda423e546ab82b846bc13b6aff183073ffcd 17620 compactheader_2.1.6-1~deb9u1.debian.tar.xz 8bae3d4f07ceb592ab732977d6f4167adfa64c6486316520530d66b33ed8d6c5 7280 compactheader_2.1.6-1~deb9u1_amd64.buildinfo 217c643aaaf1729d7e2b22ed13fa020991bf2043084a3ffcbd031547a2b06919 216218 xul-ext-compactheader_2.1.6-1~deb9u1_all.deb Files: bf4fca99da528a82f9bc79d154fd5d43 2090 mail optional compactheader_2.1.6-1~deb9u1.dsc d371549c6ad149b3e72d490352dc6642 17620 mail optional compactheader_2.1.6-1~deb9u1.debian.tar.xz f19ccd8bb509ecd179d7ddab4d8fd9d0 7280 mail optional compactheader_2.1.6-1~deb9u1_amd64.buildinfo 3585400d06d62b03d7b7b3bef87802af 216218 mail optional xul-ext-compactheader_2.1.6-1~deb9u1_all.deb -BEGIN PGP SIGNATURE- iQJMBAEBCAA2FiEEtw38bxNP7PwBHmKqgwFgFCUdHbAFAlxf9V0YHGMuc2Nob2Vu ZXJ0QHQtb25saW5lLmRlAAoJEIMBYBQlHR2wHkgP/2WDkqY0N9iUPwEZvRJ6GR4Z VkmwB/nwNxkWc1p/UglPRxUNoOSHaWm4vPgEIg5Sck8DUKuRIFaDj8/1t8sGQZpO ZgBId3c6qB8eh9fJv70iiE7Op20yVpebCoVvPhhJcTNuTQtr2obJgmvVvaRXYxGp KsoFPBZXaYVXQplZeNHYLVBUjOSMnfw5UAZOPiTb9yR4rHPfgmS3R9tkdgB/T1b4 ksYebyW1rEZhODyRmQGVcEcwZX9lq8GlcyKkRYoGQkd7BNncg/Bh3qaQKVoBkAgC WZdiuDcimt3NK/kTEJORKsuUUi9PK/87hojeBXLhuzbzyUs4iicJKzpG/4+NaTZI vMgtCDAkXb9nc7/QJyy8q6yVmhB7YX/hJ81laDIQQj3XG0DPS7C5/aERpChR+d9o 73TgofXmMmvAKFjCZ2kI4PNmWswYSPs/mwuECZpIEL6lGohv1zIWmPGHt1L05ays V0VPNuBAlcge8ZZDw2qtLBz9ajibCtr0/X7CZ8mkTMRJVtQNxCVikDqqPwWa08lf 2ikhAiMQGveV7X6/vsEuldzdn/eOi4M0Uw17q4UezT7+kQpOypytjkGH3pbJpA0Q 4aNTsv9sjg2xeUOrooIgAuwH0w6VAhW6+oHprvKQWwfeqOUY1wGg14XPwS6K80+h lQVicnwaKEtyQP7HCLeA =/+Pr -END PGP SIGNATURE End Message ---
Bug#917117: marked as done (grub-efi-amd64-signed: doesn't mount cryptodisk)
Your message dated Sun, 10 Feb 2019 19:19:46 + with message-id and subject line Bug#917117: fixed in grub2 2.02+dfsg1-11 has caused the Debian Bug report #917117, regarding grub-efi-amd64-signed: doesn't mount cryptodisk 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.) -- 917117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917117 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: grub-efi-amd64-bin Version: 1+2.02+dfsg1+9 Severity: critical Dear Maintainer, I'm running a UEFI system. I have GRUB_ENABLE_CRYPTODISK=y in my /etc/default/grub. Ever since 2.02+dfsg1+6, each GRUB2 update removes cryptomount call from /boot/efi/EFI/debian/grub.cfg, and thus breaks the boot: GRUB drops into a recovery shell, unable to find my root partition (which is on LVM inside LUKS). /boot/efi is where I mount the ESP partition. I don't recall if the problem existed before 2.02+dfsg1+6. This has been reported in #908162 before (against 2.02+dfsg1+6). Ostensibly fixed in 2.02+dfsg1+7, but I still experience the bug. I'm running Debian testing which only has 2.02+dfsg1+8 at the moment, so I got 2.02+dfsg1+9 from Sid. That didn't fix the problem. For now, my solution is to manually edit aforementioned grub.cfg, and add the following at the very start: set prefix=(hd0,gpt1)/efi/grub insmod luks insmod lvm cryptomount (lvm/sda2_lvm-root) These lines are removed each time grub-efi-amd64 is reinstalled. Reinstallation of grub-efi-amd64-signed doesn't touch those lines. However, if I uninstall grub-efi-amd64-signed, reinstalling grub-efi-amd64 *doesn't* remove those lines. Thank you for maintaining the package! I've been running Debian on and off for almost ten years now, and that's the first critical bug I ever encountered. Please keep up the good work! -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (600, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages grub-efi-amd64-bin depends on: ii efibootmgr 15-1 ii grub-common 2.02+dfsg1-9 grub-efi-amd64-bin recommends no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: grub2 Source-Version: 2.02+dfsg1-11 We believe that the bug you reported is fixed in the latest version of grub2, 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 917...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Colin Watson (supplier of updated grub2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 10 Feb 2019 18:53:41 + Source: grub2 Architecture: source Version: 2.02+dfsg1-11 Distribution: unstable Urgency: medium Maintainer: GRUB Maintainers Changed-By: Colin Watson Closes: 741464 917117 919012 919067 919955 921018 921249 921702 Changes: grub2 (2.02+dfsg1-11) unstable; urgency=medium . [ Colin Watson ] * Apply patches from Alexander Graf to set arm64-efi code offset to EFI_PAGE_SIZE (closes: #919012, LP: #1812317). * Upgrade to debhelper v10. * Set Rules-Requires-Root: no. * Add help and ls modules to signed UEFI images (closes: #919955). * Fix application of answers from dpkg-reconfigure to /etc/default/grub (based loosely on a patch by Steve Langasek, for which thanks; closes: #921702). . [ Steve McIntyre ] * Make grub-efi-amd64-signed recommend shim-signed (closes: #919067). . [ Jeroen Dekkers ] * Initialize keyboard in at_keyboard module init if keyboard is ready (closes: #741464). . [ John Paul Adrian Glaubitz ] * Include a.out header in assembly of sparc64 boot loader (closes: #921249). . [ Hervé Werner ] * Fix setup on Secure Boot systems where cryptodisk is in use (closes: #917117). . [ Debconf translations ] * [de] German (Helge Kreutzmann and Holger Wansing; closes: #921018). Checksums-Sha1:
Bug#888847: marked as done (grokmirror: missing dependency on python-pkg-resources)
Your message dated Sun, 10 Feb 2019 19:17:09 + with message-id and subject line Bug#47: fixed in grokmirror 1.0.0-1.1~deb9u1 has caused the Debian Bug report #47, regarding grokmirror: missing dependency on python-pkg-resources 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.) -- 47: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=47 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: grokmirror Version: 1.0.0-1 Severity: important I installed a Debian Stretch system, installed grokmirror on it and then: |$ grok-manifest -m /srv/www/manifest.js.gz -t /srv/git/ |Traceback (most recent call last): | File "/usr/bin/grok-manifest", line 5, in |from pkg_resources import load_entry_point |ImportError: No module named pkg_resources Installing `python-pkg-resources' solved the problem. Sebastian --- End Message --- --- Begin Message --- Source: grokmirror Source-Version: 1.0.0-1.1~deb9u1 We believe that the bug you reported is fixed in the latest version of grokmirror, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 888...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated grokmirror package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 10 Feb 2019 01:39:00 +0100 Source: grokmirror Binary: grokmirror Architecture: source Version: 1.0.0-1.1~deb9u1 Distribution: stretch Urgency: medium Maintainer: Adrian Alves Changed-By: Andreas Beckmann Description: grokmirror - framework to smartly mirror git repositories Closes: 47 Changes: grokmirror (1.0.0-1.1~deb9u1) stretch; urgency=medium . * Non-maintainer upload. * Rebuild for stretch. . grokmirror (1.0.0-1.1) unstable; urgency=medium . * Non-maintainer upload. * Add the missing dependency on python-pkg-resources. (Closes: #47) Checksums-Sha1: 39e2c33c9f4c01c8413362d101bf5511ee8e9fb8 2019 grokmirror_1.0.0-1.1~deb9u1.dsc 58a3a85e571bb1e702105a0c279a6852c8dad25a 2656 grokmirror_1.0.0-1.1~deb9u1.debian.tar.xz 8427ce46a8a8298b138a42b9e054292d74c8944c 6056 grokmirror_1.0.0-1.1~deb9u1_source.buildinfo Checksums-Sha256: 107683448c982bcc152257c3358f7f507a63b9d5ffb4fb7f6a8d2f360f52812f 2019 grokmirror_1.0.0-1.1~deb9u1.dsc a965406a85bdf80a13de8ee37a6c61c64ca27257c571a8e084f38375f2786ce1 2656 grokmirror_1.0.0-1.1~deb9u1.debian.tar.xz 4f4d5fc4d3f136b45c401aebf9a66c90a6eba93f8e8a3bca41cb144cabee9d7e 6056 grokmirror_1.0.0-1.1~deb9u1_source.buildinfo Files: 5fd0591950a7ae6c388fce10ffe65efc 2019 vcs optional grokmirror_1.0.0-1.1~deb9u1.dsc 6169156ba3f3dc2e057012cad524c5c8 2656 vcs optional grokmirror_1.0.0-1.1~deb9u1.debian.tar.xz 3a0021bcacb6d523463a2ea1fafb6055 6056 vcs optional grokmirror_1.0.0-1.1~deb9u1_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAlxfdA4QHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCCQYD/9IaGDcK0cEEodx7VJ4D3N3gskB5hl3ExWi wvSs/nih8LfjMsS8bZrz2oueLhliWC2vLVUF2xr/FwniSLz3uu0vIEAt+M+8xh27 6wR2YVplgEzM17uF2hM98Q3/uFTYk4+qltOKg0LtquufPQ51L08wmFRN9ssuU4Fv LDD4amVmtefCv5r86QHxH/Dtbiksk1ua3GezNpR5uK6P8rxCGDVyn1cOQPWh9fJ0 gJ+ZZW5ysE0j4Mn7c1c21VCLQsEusRGSmFXNHN6s3zVWHKuojYnZzNjzreWo5gqq Hp0k/wMvGPexAJjMr8LbGe/ED9yEcGANBKksR7UMf8ug7iaCrRoE+m024WcZ6AlW sBgVceYy3rMUjtgWULMl8sghlflFi7hrzPKReiNZuczeJFht+PhiizrU4YlWs04e T9JroTV3kVd+par8DwrFwvh7R9X7TiK3gZoYwK1rAmfWxr5wxiTSSEqNw89UH5gg kx+XI9EspVQkJDYw6Cx3sshlenSRlhkpO1JJYLxN67tfOS5hmONZhgY/sehtPNLs RoVe7rBqQrpB3JPKDpYIWylrNJB2z+XrGkNd28JPSTZeNokGFiifWsaAu2IKiKcf s2NyQPHd4KYRxrRfyRG7C6RYHPOv9OCBgpvIMtjPHSZ4+J0c2yxR/l7Oa/o96ZCM jy91+uC48A== =jbkt -END PGP SIGNATURE End Message ---
Bug#904752: marked as done (yosys: /usr/bin/yosys-smtbmc fails to run: ModuleNotFoundError: No module named 'smtio')
Your message dated Sun, 10 Feb 2019 19:17:11 + with message-id and subject line Bug#904752: fixed in yosys 0.7-2+deb9u1 has caused the Debian Bug report #904752, regarding yosys: /usr/bin/yosys-smtbmc fails to run: ModuleNotFoundError: No module named 'smtio' 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.) -- 904752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904752 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: yosys Version: 0.7-2 Severity: serious sid $ /usr/bin/yosys-smtbmc Traceback (most recent call last): File "/usr/bin/yosys-smtbmc", line 22, in from smtio import SmtIo, SmtOpts, MkVcd ModuleNotFoundError: No module named 'smtio' stretch $ /usr/bin/yosys-smtbmc Traceback (most recent call last): File "/usr/bin/yosys-smtbmc", line 22, in from smtio import SmtIo, SmtOpts, MkVcd ImportError: No module named 'smtio' Andreas --- End Message --- --- Begin Message --- Source: yosys Source-Version: 0.7-2+deb9u1 We believe that the bug you reported is fixed in the latest version of yosys, 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 904...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated yosys package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 10 Feb 2019 03:33:31 +0100 Source: yosys Binary: yosys yosys-dev yosys-doc Architecture: source Version: 0.7-2+deb9u1 Distribution: stretch Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Andreas Beckmann Description: yosys - Framework for Verilog RTL synthesis yosys-dev - Framework for Verilog RTL synthesis (development files) yosys-doc - Documentation for Yosys Closes: 904752 Changes: yosys (0.7-2+deb9u1) stretch; urgency=medium . [ Andreas Beckmann ] * Non-maintainer upload. * Backport the patch fixing the search path from 0.7-5. . [ Ruben Undheim ] * debian/patches/0010-Fix-adding-of-sys.path-in-yosys-smtbmc.patch - Fix "ModuleNotFoundError: No module named 'smtio'" (Closes: #904752) * debian/tests/smtbc: - Added CI test to check that 'yosys-smtbmc' can be started with no import errors Checksums-Sha1: 490fc8d9d135e364e836b06dcb73ae49fdee5b45 2546 yosys_0.7-2+deb9u1.dsc 52274dc69224922c874a66a8e5a9c5e4938a5867 12568 yosys_0.7-2+deb9u1.debian.tar.xz 59fb8ae70cb379815b066ff08cc98beaf1893881 6533 yosys_0.7-2+deb9u1_source.buildinfo Checksums-Sha256: 44649ac8e31702f66bfd0fe981fd53da3bb87a798a90f69f85898b8d91b525e3 2546 yosys_0.7-2+deb9u1.dsc 894f1ddad146d6eab92b13802f456c8880ff7bf6eb8273b78349908ba5d8aeaf 12568 yosys_0.7-2+deb9u1.debian.tar.xz 8cf6c612b8652fdb80dc8b90f0adbe4b123e4e42acf02e5bc0739ce48781bef3 6533 yosys_0.7-2+deb9u1_source.buildinfo Files: 06ba45a1aed748b9dba8b66b2e7684da 2546 electronics optional yosys_0.7-2+deb9u1.dsc 81a9bbe302438b2b7fe5dc042a201d77 12568 electronics optional yosys_0.7-2+deb9u1.debian.tar.xz 6b30e5bbbc230bad4115a5b07b580603 6533 electronics optional yosys_0.7-2+deb9u1_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAlxfpesQHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCNqJEACisZephdRIufmfRmfaRaVPZeSuDNmFkn35 Ut27Hk8pBZG33x07p7WnDpb+8ctQ0K/0fg/nbYK6vg9zba0+SHhlcB78V8/uDtwt 56a2spksAxlUcgJzb2CsXGCEssXugwxAQ/eEM2RnPomzlfb8M3+3ulOhTfv9CYEn rqyLJ4f2BP0QHDAubrz5SZgntbNDnIuEgMW/sO/JJEL1k9m/5X/2Tlk+3RvNXBjm nyYV/XPa+80agMfsj3a2vIPiVgZbqjFD8ip4qs0vIBtkvWZNqrHowiQHQbPlJcFl vt81SLrcl5n36SsgWPrXp7tdahf41dVK6RVA6v/QkGWx7P1fc1H1tiniYNMsYr/8 YRDduX+VrddwfsYpixa4LD3RttLHSkXJ3VgLcDTGpFadtfopvNTTsUAlEjTQo9gz So1sJpYfQpGoUiS72D4OKtYX19nJq4FSnOKsFdFW77vZejoYMEUHY5sVLwn/ZVLB EMcBaSL5Rsh84oSS/3ccUWH06R8Qe7t1+YChQG9Ou7MoXuQaSWFZTP4znXtZ2/Ot OyRsqq992K2PR/QFNAtDOfzbQXAIa3L2JX41GNb2VlhdNyWgtsyQm1Hs98jH+Sk0 t+d3xZyYtu6lghif7njUc6vSb7IblmONUSlCR3K3pyyl2fkH8yAReWKYlrshfgKA 0/cDapBPvQ== =Rv0a -END PGP SIGNATURE End Message ---
Bug#910757: marked as done (gnulib: CVE-2018-17942 heap-based buffer overflow)
Your message dated Sun, 10 Feb 2019 19:17:09 + with message-id and subject line Bug#910757: fixed in gnulib 20140202+stable-2+deb9u1 has caused the Debian Bug report #910757, regarding gnulib: CVE-2018-17942 heap-based buffer overflow 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.) -- 910757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnulib X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerability was published for gnulib. CVE-2018-17942[0]: | The convert_to_decimal function in vasnprintf.c in Gnulib before | 2018-09-23 has a heap-based buffer overflow because memory is not | allocated for a trailing '\0' character during %f processing. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2018-17942 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-17942 Patch is available here: https://github.com/coreutils/gnulib/commit/278b4175c9d7dd47c1a3071554aac02add3b3c35 Please adjust the affected versions in the BTS as needed. Regards, Markus signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: gnulib Source-Version: 20140202+stable-2+deb9u1 We believe that the bug you reported is fixed in the latest version of gnulib, 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 910...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated gnulib package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 09 Feb 2019 21:58:02 +0100 Source: gnulib Binary: gnulib git-merge-changelog Architecture: source Version: 20140202+stable-2+deb9u1 Distribution: stretch Urgency: medium Maintainer: Ian Beckwith Changed-By: Salvatore Bonaccorso Closes: 910757 Description: git-merge-changelog - git merge driver for GNU ChangeLog files gnulib - GNU Portability Library Changes: gnulib (20140202+stable-2+deb9u1) stretch; urgency=medium . * Non-maintainer upload. * vasnprintf: Fix heap memory overrun bug (CVE-2018-17942) (Closes: #910757) Checksums-Sha1: 9aab0b9b8729984acffeda2dc14308a201c65762 2192 gnulib_20140202+stable-2+deb9u1.dsc b5587c93c90e5c3dc69cdfacdf3455d64943d12a 290364 gnulib_20140202+stable-2+deb9u1.debian.tar.xz Checksums-Sha256: 7de5910cf588495d5f9543dd2a8684db6f2aec97fb5929c49d7cc095ee91fce4 2192 gnulib_20140202+stable-2+deb9u1.dsc 8529f3c565ad3f31504ebfbeab819e4f8f89cbd618987d3942b8184a8b3fa9f9 290364 gnulib_20140202+stable-2+deb9u1.debian.tar.xz Files: 24ab39e38e58470f1081ecd62fc1af9e 2192 devel optional gnulib_20140202+stable-2+deb9u1.dsc 48277af55bb4f363bf7b1a5d15c2d6d2 290364 devel optional gnulib_20140202+stable-2+deb9u1.debian.tar.xz -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAlxfP7RfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EG3AP/jpcJT3KAgWNyLnSubQW7s0dS0NkIydn sy3p9Y/bDuVAtXxCAx9Zj0uDpsy3fqbpCv6+KF9c4bKtjNc9qNOm0WL+Npuy//JI w8uMjEwDfy3mESu0AVBfvCbeUQ2tElwX5/XZPGzKlkcDriDGtqtRb7pcXzvXsNdv vBpb5EQV6oJwtJYPHCtbYY+wHSBjNuFgaLXh8kUVuI3TR8IGOsFh4OWRZ6Vm6+Ps baatrFjHz4YcNUg0XeTok7rTcJ2J4iW2HW99gsrLhwBn/LS4U8aXbqPQbe+Mfbtb l9wkcN5uMxr8z3zSKsqYophGW3Ot2hOhC6KgEXVEjV78ryZZNyRTJLpCf/dX6zgm xC8xCRTdBNBI29M17nmFq/s9ItpYow9MCPYBtiKH0zGfz6SdoeCyxoUcfXX0AX0e bCJDMY4La72vlDl5j7Z6+9ljOx+L0wJTwS4eAW3fgtu/YuJS+UgleutMAecOs6rT gAkV6T5uS9G81M8bT5AIydoyp6vQR6SVI0B0HYIJgCERUauoQQNHGV/+OJ9U94Ri 6NN/Xn0RSGf6dx6AnYqkfzx/VDpJEVg09jpFBqlGWuU16ivphj1Wc7ON/tl9RJkl mMCy/J/DxvPKqjsMs/IsdoDyDtOdfBJ3+SExoG4hzrMN3Tb7Xk1f6/CQLsvxvy9x rs31B2sP4sn8 =C0Y/ -END PGP SIGNATURE End Message ---
Processed: 921883 is due to cruft left over by vm
Processing commands for cont...@bugs.debian.org: > severity 921883 important Bug #921883 [emacspeak] emacspeak fails to byte-compile in some case Severity set to 'important' from 'serious' > retitle 921883 emacspeak should not trip over cruft from vm Bug #921883 [emacspeak] emacspeak fails to byte-compile in some case Changed Bug title to 'emacspeak should not trip over cruft from vm' from 'emacspeak fails to byte-compile in some case'. > tag 921883 - moreinfo Bug #921883 [emacspeak] emacspeak should not trip over cruft from vm Removed tag(s) moreinfo. > tag 921883 pending Bug #921883 [emacspeak] emacspeak should not trip over cruft from vm Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 921883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921883 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 892526 is grave
Processing commands for cont...@bugs.debian.org: > severity 892526 grave Bug #892526 [src:gpac] gpac: CVE-2018-7752: Stack buffer overflow in av_parsers.c Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 892526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892526 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921969: CVE-2018-20760 CVE-2018-20761 CVE-2018-20762 CVE-2018-20763
Source: gpac Severity: grave Tags: security CVE-2018-20760: https://github.com/gpac/gpac/commit/4c1360818fc8948e9307059fba4dc47ba8ad255d https://github.com/gpac/gpac/issues/1177 CVE-2018-20761: https://github.com/gpac/gpac/commit/35ab4475a7df9b2a4bcab235e379c0c3ec543658 https://github.com/gpac/gpac/issues/1186 CVE-2018-20762: https://github.com/gpac/gpac/commit/35ab4475a7df9b2a4bcab235e379c0c3ec543658 https://github.com/gpac/gpac/issues/1187 CVE-2018-20763: https://github.com/gpac/gpac/commit/1c449a34fe0b50aaffb881bfb9d7c5ab0bb18cdd https://github.com/gpac/gpac/issues/1188 Cheers, Moritz
Bug#921883: [921883] emacspeak fails to byte-compile in some case
Hi Pavel, On 10-02-2019 16:51, Pavel Kreuzt wrote: > I suppose this is for debugging and not a solution, for it keeps > failing. Attached log file. It was, yes. I am getting help on IRC from hartmans and bremner on #debian-devel, can you confirm that you have vm installed and or /etc/emacs/site-start.d/50vm.el left over? Paul signature.asc Description: OpenPGP digital signature
Bug#921542: tc qdisc kernel crash
On Sun, Feb 10, 2019 at 7:54 AM Ben Hutchings wrote: > > Control: tag -1 confirmed upstream > Control: found -1 4.20-1~exp1 > > Adrian (cc'd) reported (https://bugs.debian.org/921542) that a script > using tc could trigger a kernel crash. I've simplified the script he > provided down to: > > --- BEGIN --- > #!/bin/sh -ex > > modprobe ifb > > while true; do > tc qdisc add dev ifb0 root handle 2:0 prio bands 5 > tc qdisc add dev ifb0 parent 2:5 sfq > tc filter add dev ifb0 parent 2:0 protocol ip prio 5 handle 0 tcindex > mask 0 classid 2:5 pass_on > tc qdisc del dev ifb0 root || true > done > --- END --- > > The crash is still reproducible in 4.20 and 5.0-rc5. KASan shows a > use-after-free: Thanks for the reproducer and report! I will send a fix.
Bug#902517: marked as done (python-ofxclient: FTBFS in buster/sid (failing tests))
Your message dated Sun, 10 Feb 2019 18:19:47 +
with message-id
and subject line Bug#902517: fixed in python-ofxclient 2.0.3+git20180108-4
has caused the Debian Bug report #902517,
regarding python-ofxclient: FTBFS in buster/sid (failing tests)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
902517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902517
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-ofxclient
Version: 2.0.3+git20180108-3
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:
[...]
debian/rules build-indep
dh build-indep --with python2 --buildsystem=pybuild
dh_update_autotools_config -i -O--buildsystem=pybuild
dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config
running config
dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python setup.py build
running build
running build_py
creating
/<>/python-ofxclient-2.0.3+git20180108/.pybuild/cpython2_2.7_ofxclient/build/ofxclient
copying ofxclient/util.py ->
/<>/python-ofxclient-2.0.3+git20180108/.pybuild/cpython2_2.7_ofxclient/build/ofxclient
copying ofxclient/client.py ->
/<>/python-ofxclient-2.0.3+git20180108/.pybuild/cpython2_2.7_ofxclient/build/ofxclient
[... snipped ...]
--
Traceback (most recent call last):
File
"/<>/python-ofxclient-2.0.3+git20180108/.pybuild/cpython2_2.7_ofxclient/build/tests/secure_config.py",
line 38, in testStaysUnsecure
c = makeConfig()
File
"/<>/python-ofxclient-2.0.3+git20180108/.pybuild/cpython2_2.7_ofxclient/build/tests/secure_config.py",
line 16, in makeConfig
conf.set_secure('section1', 'password', 'PASSWORD')
File "ofxclient/config.py", line 138, in set_secure
ConfigParser.set(self, section, option, value)
File "/usr/lib/python2.7/dist-packages/backports/configparser/__init__.py",
line 1239, in set
super(ConfigParser, self).set(section, option, value)
File "/usr/lib/python2.7/dist-packages/backports/configparser/__init__.py",
line 914, in set
value)
File "/usr/lib/python2.7/dist-packages/backports/configparser/__init__.py",
line 392, in before_set
"position %d" % (value, tmp_value.find('%')))
ValueError: invalid interpolation syntax in u'%{secured}' at position 0
==
ERROR: testUnsavedOptions (tests.secure_config.IdentifySecureOptionTests)
--
Traceback (most recent call last):
File
"/<>/python-ofxclient-2.0.3+git20180108/.pybuild/cpython2_2.7_ofxclient/build/tests/secure_config.py",
line 82, in testUnsavedOptions
c = makeConfig()
File
"/<>/python-ofxclient-2.0.3+git20180108/.pybuild/cpython2_2.7_ofxclient/build/tests/secure_config.py",
line 16, in makeConfig
conf.set_secure('section1', 'password', 'PASSWORD')
File "ofxclient/config.py", line 138, in set_secure
ConfigParser.set(self, section, option, value)
File "/usr/lib/python2.7/dist-packages/backports/configparser/__init__.py",
line 1239, in set
super(ConfigParser, self).set(section, option, value)
File "/usr/lib/python2.7/dist-packages/backports/configparser/__init__.py",
line 914, in set
value)
File "/usr/lib/python2.7/dist-packages/backports/configparser/__init__.py",
line 392, in before_set
"position %d" % (value, tmp_value.find('%')))
ValueError: invalid interpolation syntax in u'%{secured}' at position 0
--
Ran 24 tests in 0.027s
FAILED (errors=11)
E: pybuild pybuild:336: test: plugin distutils failed with: exit code=1: cd
/<>/python-ofxclient-2.0.3+git20180108/.pybuild/cpython2_2.7_ofxclient/build;
python2.7 -m nose -v tests/ofxconfig.py tests/__init__.py tests/institution.py
tests/secure_config.py tests/account.py
dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned
exit code 13
debian/rules:15: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>/python-ofxclient-2.0.3+git20180108'
debian/rules:12: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
Bug#906074: marked as done (libvirt: Error connecting to graphical console)
Your message dated Sun, 10 Feb 2019 19:01:20 +0100 with message-id <87o97jfrpr@msgid.hilluzination.de> and subject line Is this fixed in libvirt 5.0.0? has caused the Debian Bug report #906074, regarding libvirt: Error connecting to graphical console 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.) -- 906074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906074 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libvirt Severity: grave Justification: renders package unusable Since version 4.6.0-1 I can not connect to a vm with graphical console: "Error connecting to graphical console: internal error: failed to parse JSON 1:59: too big integer near '18446744073709551615'" Looks like the same issue Red Hat has: "Jansson can not always parse QEMU's JSON" https://bugzilla.redhat.com/show_bug.cgi?id=1614569 Jansson has been reverted upstream: https://libvirt.org/git/?p=libvirt.git;a=commit;h=9c3dad5677883c9d1208173c054ab6d79864c31d -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.16.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- user debian-rele...@lists.debian.org usertag 906074 + bsp-2019-02-de-berlin tag 906074 + confirmed fixed 906074 libvirt/4.6.0-2 notfound 906074 libvirt/5.0.0-1 thank you Hi, Greetings from the BSP at the DCSO office in Berlin. As far as I can see, this bug has been fixed in libvirt upstream by switching JSON libraries. Please reopen if necessary. Cheers, -Hilko--- End Message ---
Processed: Is this fixed in libvirt 5.0.0?
Processing commands for cont...@bugs.debian.org: > user debian-rele...@lists.debian.org Setting user to debian-rele...@lists.debian.org (was ben...@debian.org). > usertag 906074 + bsp-2019-02-de-berlin There were no usertags set. Usertags are now: bsp-2019-02-de-berlin. > tag 906074 + confirmed Bug #906074 [src:libvirt] libvirt: Error connecting to graphical console Added tag(s) confirmed. > fixed 906074 libvirt/4.6.0-2 Bug #906074 [src:libvirt] libvirt: Error connecting to graphical console Marked as fixed in versions libvirt/4.6.0-2. > notfound 906074 libvirt/5.0.0-1 Bug #906074 [src:libvirt] libvirt: Error connecting to graphical console Ignoring request to alter found versions of bug #906074 to the same values previously set > thank you Stopping processing here. Please contact me if you need assistance. -- 906074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906074 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919646: makehuman: File base.obj is missing
On Thu, Feb 07, 2019 at 11:25:37AM -0800, Muammar El Khatib wrote: >... > Adrian, I was thinking to move makehuman to a git repository to ease > team-maintenance. I recently don't have too much time for my Debian > duties. > > Does that sound that good for you? I was merely doing QA work, unfortunately I do not have any personal interest in maintaining this package. > Best, cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Processed: tagging 852575
Processing commands for cont...@bugs.debian.org: > tags 852575 + patch Bug #852575 [powerpc-utils] powerpc-utils: Update udevadm path Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 852575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852575 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#916163: ppp FTBFS with glibc 2.28
On Wed, Jan 09, 2019 at 06:45:43PM +, Luca Boccassi wrote:
> Control: tags -1 patch
>
> On Mon, 10 Dec 2018 21:16:50 +0200 Adrian Bunk wrote:
[snip]
> > make[3]: *** [Makefile:227: pppd] Error 1
>
> Dear Maintainer,
>
> This was fixed upstream in Github:
>
> https://github.com/paulusmack/ppp/commit/3c7b86229f7bd2600d74db14b1fe5b3896be3875
>
> A backport (with a minor refresh for fuzz) is inlined below.
Hi,
I submitted a merge request with this patch to the Salsa ppp
packaging repository:
https://salsa.debian.org/debian/ppp/merge_requests/1
I also submitted another merge request to import the ppp-2.4.7 upstream
tarball's data into the pristine-tar branch:
https://salsa.debian.org/debian/ppp/merge_requests/2
Thanks to everyone for taking care of ppp in Debian!
G'luck,
Peter
--
Peter Pentchev roam@{ringlet.net,debian.org,FreeBSD.org} p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13
signature.asc
Description: PGP signature
Bug#921928: marked as done (matrix-synapse-ldap3: FTBFS in sid (Can't locate Debian/Debhelper/Sequence/python2.pm))
Your message dated Sun, 10 Feb 2019 17:34:39 + with message-id and subject line Bug#921928: fixed in matrix-synapse-ldap3 0.1.3-4 has caused the Debian Bug report #921928, regarding matrix-synapse-ldap3: FTBFS in sid (Can't locate Debian/Debhelper/Sequence/python2.pm) 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.) -- 921928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921928 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:matrix-synapse-ldap3 Version: 0.1.3-3 Severity: serious Tags: ftbfs Helo Rahul and Andrej. I tried to build this package in sid but it failed: [...] dpkg-buildpackage - dpkg-buildpackage: info: source package matrix-synapse-ldap3 dpkg-buildpackage: info: source version 0.1.3-3 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Andrej Shadura dpkg-source --before-build . fakeroot debian/rules clean dh clean --with python2,python3 --buildsystem=pybuild dh: unable to load addon python2: Can't locate Debian/Debhelper/Sequence/python2.pm in @INC (you may need to install the Debian::Debhelper::Sequence::python2 module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 /usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 9) line 1. BEGIN failed--compilation aborted at (eval 9) line 1. make: *** [debian/rules:5: clean] Error 2 dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit status 2 Something similar happens here: https://buildd.debian.org/status/package.php?p=matrix%2dsynapse%2dldap3 Seems like a missing build-depends somewhere. Thanks. --- End Message --- --- Begin Message --- Source: matrix-synapse-ldap3 Source-Version: 0.1.3-4 We believe that the bug you reported is fixed in the latest version of matrix-synapse-ldap3, 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 921...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrej Shadura (supplier of updated matrix-synapse-ldap3 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 10 Feb 2019 18:09:54 +0100 Source: matrix-synapse-ldap3 Binary: matrix-synapse-ldap3 Architecture: all source Version: 0.1.3-4 Distribution: unstable Urgency: medium Maintainer: Rahul De Changed-By: Andrej Shadura Closes: 921928 Description: matrix-synapse-ldap3 - LDAP auth provider for the Matrix homeserver Changes: matrix-synapse-ldap3 (0.1.3-4) unstable; urgency=medium . * Fix an FTBFS (Closes: #921928). Checksums-Sha1: e52b69bd88104250fa7e4cf99d582045a4cea3ca 1934 matrix-synapse-ldap3_0.1.3-4.dsc 1fd6de3e9ed78935c45c62f100c5152e4e2b04c9 3852 matrix-synapse-ldap3_0.1.3-4.debian.tar.xz 344ef480cb17cc955d3090a77c6e5bb423d9d75c 7088 matrix-synapse-ldap3_0.1.3-4_all.deb bd2578d1b9680130eb99a0128ba1e3ccfbe44bec 6323 matrix-synapse-ldap3_0.1.3-4_amd64.buildinfo Checksums-Sha256: 02b46e58dc5a8943bc052774b74fe4e2f36ca77789ef63a11612fa867ec27dfa 1934 matrix-synapse-ldap3_0.1.3-4.dsc 95bd202f9e4e9607ba1c05de6f15bf2cbd20c4ab46d8bc1e6579d5da9b52cb1d 3852 matrix-synapse-ldap3_0.1.3-4.debian.tar.xz 8e81ddf611168f8522b9c6b495bb832f590e54fdd3e3ebff8f728709df94f7b4 7088 matrix-synapse-ldap3_0.1.3-4_all.deb b03d554d42bc24dd8c3637e517b43382c5b1ac48e39c1683293edc97b91c 6323 matrix-synapse-ldap3_0.1.3-4_amd64.buildinfo Files: 6b188afd7076b0c4ee76af2749d7cce1 1934 python optional matrix-synapse-ldap3_0.1.3-4.dsc 8394634e20fc6451417e8c747fd44df6 3852 python optional matrix-synapse-ldap3_0.1.3-4.debian.tar.xz f5036651f42bb33ea1c1d386e5976bfd 7088 python optional matrix-synapse-ldap3_0.1.3-4_all.deb a0258b3c5ab8406b74ef37a18123b08a 6323 python optional matrix-synapse-ldap3_0.1.3-4_amd64.buildinfo -BEGIN PGP SIGNATURE-
Bug#892655: marked as done (node-class-utils: FTBFS and Debci failure)
Your message dated Sun, 10 Feb 2019 17:34:46 +
with message-id
and subject line Bug#892655: fixed in node-class-utils 0.3.6-1
has caused the Debian Bug report #892655,
regarding node-class-utils: FTBFS and Debci failure
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.)
--
892655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-class-utils
Version: 0.3.5-1
Severity: serious
Some recent change in unstable makes node-class-utils FTBFS and Debci fail:
https://ci.debian.net/packages/n/node-class-utils/unstable/amd64/
https://tests.reproducible-builds.org/debian/history/node-class-utils.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-class-utils.html
49 passing (1s)
2 failing
1) extend
should add `Parent.prototype` to `Ctor` instances as `_parent_`:
AssertionError [ERR_ASSERTION]: { configurable: true,
set: [Function: set],
get: [Function: get] } deepEqual Parent { a: [Function], b: [Function], c:
[Function] }
+ expected - actual
{
- "configurable": true
- "get": [Function]
- "set": [Function]
+ "a": [Function]
+ "b": [Function]
+ "c": [Function]
}
at Context. (test.js:376:12)
at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21)
at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10)
at /usr/lib/nodejs/mocha/lib/runner.js:560:12
at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14)
at /usr/lib/nodejs/mocha/lib/runner.js:366:7
at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14)
at /usr/lib/nodejs/mocha/lib/runner.js:329:7
at done (/usr/lib/nodejs/mocha/lib/runnable.js:301:5)
at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:372:7)
at Hook.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
at next (/usr/lib/nodejs/mocha/lib/runner.js:304:10)
at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:334:5)
2) extend
should access `Parent` methods through `_parent_`:
TypeError: this._parent_.upper is not a function
at Ctor.instance.upper (test.js:396:28)
at Context. (test.js:398:27)
at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21)
at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10)
at /usr/lib/nodejs/mocha/lib/runner.js:560:12
at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14)
at /usr/lib/nodejs/mocha/lib/runner.js:366:7
at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14)
at /usr/lib/nodejs/mocha/lib/runner.js:329:7
at done (/usr/lib/nodejs/mocha/lib/runnable.js:301:5)
at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:372:7)
at Hook.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
at next (/usr/lib/nodejs/mocha/lib/runner.js:304:10)
at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:334:5)
make[1]: *** [debian/rules:13: override_dh_auto_test] Error 2
--- End Message ---
--- Begin Message ---
Source: node-class-utils
Source-Version: 0.3.6-1
We believe that the bug you reported is fixed in the latest version of
node-class-utils, 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 892...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Xavier Guimard (supplier of updated node-class-utils package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 10 Feb 2019 18:19:46 +0100
Source: node-class-utils
Binary: node-class-utils
Architecture: source
Version: 0.3.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Xavier Guimard
Closes: 892655
Description:
node-class-utils - Utils for working with JavaScript classes and prototype
methods
Changes:
node-class-utils (0.3.6-1) unstable; urgency=medium
.
* Team upload
* New upstream version 0.3.6
* Bump debhelper compatibility level to 11
* Declare
Bug#850320: marked as done (mock: CVE-2016-6299: privilige escalation via mock-scm)
Your message dated Sun, 10 Feb 2019 17:25:15 + with message-id <20190210172515.dbrqyuu6zan7s...@layer-acht.org> and subject line done has caused the Debian Bug report #850320, regarding mock: CVE-2016-6299: privilige escalation via mock-scm 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.) -- 850320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850320 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mock Version: 1.3.2-1 Severity: grave Tags: patch security upstream Justification: user security hole Hi, the following vulnerability was published for mock. I'm not too familiar with it, but following the code and the applied upstream commit 1.3.2-1 should be vulnerable. CVE-2016-6299[0]: privilige escalation via mock-scm If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2016-6299 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6299 [1] https://bugzilla.redhat.com/show_bug.cgi?id=1375490 [2] https://github.com/rpm-software-management/mock/commit/8b02f43beadacf6911200b48d94e39e891a41da9 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- version: 1.3.2-1 long fixed, just never marked as done. -- tschau, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C signature.asc Description: PGP signature --- End Message ---
Processed: unarchiving 914495, forcibly merging 914495 916898, archiving 914495
Processing commands for cont...@bugs.debian.org:
> unarchive 914495
Bug #914495 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-4.18.0-3-amd64: does not boot here [i915 gen4/gen5]
Bug #914980 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-4.18.0-3-amd64: does not boot here [i915 gen4/gen5]
Bug #915178 {Done: Salvatore Bonaccorso } [src:linux] i915:
unable to handle kernel NULL pointer dereference at 0008
Bug #915641 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-4.18.0-3-amd64: driver i915 crashed on GM45 chipset.
Bug #915645 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-4.18.0-3-amd64: Kernel 4.18-0-3 boots to a blank screen
Bug #915674 {Done: Salvatore Bonaccorso } [src:linux] i915
driver crash on kernel 4.18.0-3 (buster/testing)
Bug #915954 {Done: Salvatore Bonaccorso } [src:linux]
inteldrmfb: screen black in 4.18.0-3 (works in 4.18.0-2)
Bug #916090 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-4.18.0-3-amd64: Kernel update makes system unbootable: kernel-oops
when loading "i915" module
Bug #916134 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-4.18.0-3-amd64: 4.18.0-3 fails to boot, 0-2 works.
Bug #916510 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-4.18.0-3-amd64: Absolutely no video output after i915 module is
initialized
Bug #916656 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-4.18.0-3-amd64: (i915?) BUG: unable to handle kernel NULL pointer
dereference at 0008
Bug #916718 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-4.18.0-3-amd64: Booting on Thinkpad X300 leave screen black (NULL
pointer dereference in i915 drm driver)
Bug #916899 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-4.18.0-0.bpo.3-amd64: NULL pointer dereference in i915
Bug #917280 {Done: Salvatore Bonaccorso } [src:linux]
Linux-4.18.20 fail to boot on old intel gfx card
Bug #917527 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-4.18.0-0.bpo.3-amd64: i915 module loading hangs
Unarchived Bug 914495
Unarchived Bug 914980
Unarchived Bug 915178
Unarchived Bug 915641
Unarchived Bug 915645
Unarchived Bug 915674
Unarchived Bug 915954
Unarchived Bug 916090
Unarchived Bug 916134
Unarchived Bug 916510
Unarchived Bug 916656
Unarchived Bug 916718
Unarchived Bug 916899
Unarchived Bug 917280
Unarchived Bug 917527
> forcemerge 914495 916898
Bug #914495 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-4.18.0-3-amd64: does not boot here [i915 gen4/gen5]
Bug #914980 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-4.18.0-3-amd64: does not boot here [i915 gen4/gen5]
Bug #915178 {Done: Salvatore Bonaccorso } [src:linux] i915:
unable to handle kernel NULL pointer dereference at 0008
Bug #915641 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-4.18.0-3-amd64: driver i915 crashed on GM45 chipset.
Bug #915645 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-4.18.0-3-amd64: Kernel 4.18-0-3 boots to a blank screen
Bug #915674 {Done: Salvatore Bonaccorso } [src:linux] i915
driver crash on kernel 4.18.0-3 (buster/testing)
Bug #915954 {Done: Salvatore Bonaccorso } [src:linux]
inteldrmfb: screen black in 4.18.0-3 (works in 4.18.0-2)
Bug #916090 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-4.18.0-3-amd64: Kernel update makes system unbootable: kernel-oops
when loading "i915" module
Bug #916134 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-4.18.0-3-amd64: 4.18.0-3 fails to boot, 0-2 works.
Bug #916510 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-4.18.0-3-amd64: Absolutely no video output after i915 module is
initialized
Bug #916656 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-4.18.0-3-amd64: (i915?) BUG: unable to handle kernel NULL pointer
dereference at 0008
Bug #916718 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-4.18.0-3-amd64: Booting on Thinkpad X300 leave screen black (NULL
pointer dereference in i915 drm driver)
Bug #916899 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-4.18.0-0.bpo.3-amd64: NULL pointer dereference in i915
Bug #917280 {Done: Salvatore Bonaccorso } [src:linux]
Linux-4.18.20 fail to boot on old intel gfx card
Bug #917527 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-4.18.0-0.bpo.3-amd64: i915 module loading hangs
Bug #916898 [src:linux] linux-image-4.18.0-3-amd64: kernel oops and gdm fails
to start
Set Bug forwarded-to-address to
'https://bugs.freedesktop.org/show_bug.cgi?id=108850'.
Severity set to 'important' from 'critical'
Marked Bug as done
Marked as fixed in versions linux/4.19~rc2-1~exp1.
Marked as found in versions linux/4.18.20-1 and linux/4.18.20-2~bpo9+1.
Added tag(s) fixed-upstream.
Bug #914980 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-4.18.0-3-amd64: does not boot here [i915 gen4/gen5]
Bug #915178 {Done: Salvatore Bonaccorso } [src:linux] i915:
unable to handle kernel NULL pointer dereference at 0008
Bug #915641 {Done: Salvatore Bonaccorso } [src:linux]
Bug#921131: marked as done (CVE-2018-10897)
Your message dated Sun, 10 Feb 2019 17:19:30 + with message-id and subject line Bug#921131: fixed in yum-utils 1.1.31-2.1 has caused the Debian Bug report #921131, regarding CVE-2018-10897 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.) -- 921131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921131 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: yum-utils Severity: grave Tags: security This was assigned CVE-2018-10897: https://bugzilla.redhat.com/show_bug.cgi?id=1600221 https://github.com/rpm-software-management/yum-utils/commit/7554c0133eb830a71dc01846037cc047d0acbc2c https://github.com/rpm-software-management/yum-utils/commit/6a8de061f8fdc885e74ebe8c94625bf53643b71c https://github.com/rpm-software-management/yum-utils/pull/43 Cheers, Moritz --- End Message --- --- Begin Message --- Source: yum-utils Source-Version: 1.1.31-2.1 We believe that the bug you reported is fixed in the latest version of yum-utils, 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 921...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Holger Levsen (supplier of updated yum-utils package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 10 Feb 2019 18:05:09 +0100 Source: yum-utils Architecture: source Version: 1.1.31-2.1 Distribution: unstable Urgency: medium Maintainer: Mike Miller Changed-By: Holger Levsen Closes: 921131 Changes: yum-utils (1.1.31-2.1) unstable; urgency=medium . * Non-maintainer upload. * Apply patch https://github.com/rpm-software-management/yum-utils/ commit/a792d21b55337add2327d1c7d6d000862c717eef to check for .. in remote paths. Closes: #921131 / CVE-2018-10897 Checksums-Sha1: 49a6c67d647c5688084d1cf74c0506de23032d51 1929 yum-utils_1.1.31-2.1.dsc 178461a6b6bd4db6160e695d2b9155c57f23bd6b 18856 yum-utils_1.1.31-2.1.debian.tar.xz 9bf668dd8e4838b70d296574a548b68900b99342 6295 yum-utils_1.1.31-2.1_source.buildinfo Checksums-Sha256: 18eb08d102532ea3ca193c348c5cc35e76a72c88b893fac4bd57a9e65f11fbaa 1929 yum-utils_1.1.31-2.1.dsc fbb3a69ec9b07d193755d79c545a86c4e1e405220944e30e9db6cfeef21ebef7 18856 yum-utils_1.1.31-2.1.debian.tar.xz 58f9fc58ed5b3b5e977e5f05a30d556c5bb4eb0a056c4ea8ece02300483c5718 6295 yum-utils_1.1.31-2.1_source.buildinfo Files: 2b0afc6ceff56301afae4abcf91bfbe0 1929 admin extra yum-utils_1.1.31-2.1.dsc 9088c04bfb4ab36d3a22bd530aaf952a 18856 admin extra yum-utils_1.1.31-2.1.debian.tar.xz 26b568acc158cd3db93347263236cadf 6295 admin extra yum-utils_1.1.31-2.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEuL9UE3sJ01zwJv6dCRq4VgaaqhwFAlxgWoEACgkQCRq4Vgaa qhybGg/+NszqsFxgxQBC8B36UupANUBXjT80UyMPYReS49Yb+b6kTFvXpZAeZMWz Berx5+sx2Y+y/ul2YV3zNGIVOuya1M9gXeEs4CwAOD4KZxeJptYlRs4XMuKQ/FXP fxO2JaA6hrd8mdDBM/JbNWxI72EARWTqN1RSmZ73tT792OvkpP5KJe0EZDQSIBMX SCH2Y0cKykcFus+klgw9WUzYwUU8NWz4CkVJ8LVc2G4YfkO30MCAYWYziea2rlSF fkJIQOYRo14O1hzgv8a8VJ+BSGoAVKKdNPgXtRVHpwd+I5ag4UcyCyO3oIcLvgVK ei1X8f2VJW2/vIHeDu1PK+oRhvW+VJBf1xABIbmNu5v54lMWHFLUOindXJoTvCjZ FVYv0ez8HF5Eu6UPr7jCFNXSlrCcWD34RgdN3VBjMTaidK9ALzGys0vg8ubkW+4T iADuFugs42g69en7Z+4RjipipuITcrFZlt2uGKVsRpLQmm8ldFXBY4Uhyxjbbv/o 8UdDFeOFvd5Om88ZqZfTS5LJzGQwq0UidqqACC5DRgwbethH8vjzlu0yBnysxPW4 eR28tZU/Hfj9dm5JprWO+KwQrUFVpUddRCrq+raRrKyEUYuaa4VUlVOpWP2kHlY0 2zIvna7Yn5qqKOAO+lcCjEKctIwwnWheOn6R8L4Obgb86budPCU= =1/g6 -END PGP SIGNATURE End Message ---
Bug#866122: slapd-mtread crash on ppc64{,el} in stretch/sid
On Tue, 3 Jul 2018 18:51:49 -0700 Ryan Tandy wrote: > Control: found -1 4.17.3-1 > > Hi, > > On Mon, Jul 02, 2018 at 08:42:45PM -0700, Ryan Tandy wrote: > >However it looks like it might be resolved with the kernel in > >unstable. I will run some more iterations and let you know. > > The issue still reproduces with stretch userland and the current > unstable kernel. > > It cannot be reproduced with buster's glibc because lock elision was > disabled in #878071, citing this issue. This bug has been open for over 18 months with no sign of a solution, which is really not acceptable for a release architecture. I propose to disable CONFIG_PPC_TRANSACTIONAL_MEMORY in both stretch and unstable, until a fix is available for TM. Ben. -- Ben Hutchings The world is coming to an end. Please log off. signature.asc Description: This is a digitally signed message part
Processed: severity of 918140 is important
Processing commands for cont...@bugs.debian.org: > severity 918140 important Bug #918140 [src:linux] linux-image-4.19.0-1-amd64: Samsung PM951 SSD in Dell XPS 15 9550 goes read-only Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 918140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918140 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 920547
Processing commands for cont...@bugs.debian.org: > tags 920547 - moreinfo Bug #920547 [src:linux] Crashes every few hours Removed tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 920547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920547 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921368: marked as done (Not suitable for buster, package probably unmaintained)
Your message dated Sun, 10 Feb 2019 16:50:17 + with message-id and subject line Bug#921368: fixed in node-base64id 1.0.0-1 has caused the Debian Bug report #921368, regarding Not suitable for buster, package probably unmaintained 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.) -- 921368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921368 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-base64id Version: 0.1.0-3 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages node-base64id depends on: ii nodejs 4.8.2~dfsg-1 node-base64id recommends no packages. node-base64id suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: node-base64id Source-Version: 1.0.0-1 We believe that the bug you reported is fixed in the latest version of node-base64id, 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 921...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated node-base64id package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 10 Feb 2019 17:22:42 +0100 Source: node-base64id Binary: node-base64id Architecture: source Version: 1.0.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 921368 Description: node-base64id - Node.js module that generates a base64 id Changes: node-base64id (1.0.0-1) unstable; urgency=medium . [ Mike Gabriel ] * debian/control: Drop myself from Uploaders: field. . [ Xavier Guimard ] * Bump debhelper compatibility level to 11 * Declare compliance with policy 4.3.0 * Change section to javascript * Change priority to optional * Set myself as uploader (Closes: #921368) * Add upstream/metadata * New upstream version 1.0.0 * Minimal test using pkg-js-tools * Fix install * Update VCS fields to salsa * Update debian/copyright Checksums-Sha1: 26204caa91d8992868df9b91bbfc98b2bc3479b8 2016 node-base64id_1.0.0-1.dsc f9610838302d50e8ea171c104f2aa995cd8b130f 2360 node-base64id_1.0.0.orig.tar.gz bf8d5c3ec1023cfe50f57a36c36f0edf28e42a0e 2576 node-base64id_1.0.0-1.debian.tar.xz Checksums-Sha256: 6c37248b36a0a820f012697d6b04b94c67f4dcc774687c2cd5a9b7ba05a8e05b 2016 node-base64id_1.0.0-1.dsc e64fcfa572fa40eb2f88045589c1eb6ca06aa67eab3037fd85c6899687c579f8 2360 node-base64id_1.0.0.orig.tar.gz 85f5d58c4280b39ce9459ed5f3c003245d9a4fd8a17cf11722884136f13af00f 2576 node-base64id_1.0.0-1.debian.tar.xz Files: a6388c0002b4af9ebcf4e9ffdadeb296 2016 javascript optional node-base64id_1.0.0-1.dsc 996aa60eb50deb68ea8d6aed48c75e45 2360 javascript optional node-base64id_1.0.0.orig.tar.gz 5b97b1c40d7cad3cffb932aeef0c1d06 2576 javascript optional node-base64id_1.0.0-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAlxgULcACgkQ9tdMp8mZ 7un+Yw/+PfdUM4aawMcJjtR+8to9L4CzPhufkj9KC1VsK5qzs0wcTnQ2ZRKnH3oI pJVF/o04KH1OW9AxGNGvAqmeIsOixsSN2jqAUrMjFfaB7N//2y9zPFPCLn3bhnQK 27U3y/3taMrhURnwh6S6Zy88+pJD9Cv5XPPD4hziRJd8RBJtt0DDsEJMqFPxGCux Y9C6Yc5Bs2/b7NUmCoNTIY3tzHzNp77x3M7mixFRkupVN9y5nt+VEbJ0kXvMSRye 12er/QBuxlZ+iHGzyKP4cSlMBeLp38Fq3+jIVrauYThAyBTRt3Sgz9nTV4z1GKr3 RLCTQ5o4ukmQja8LRUflS4k5tuwyEOS9tll+9IX7/pP4c95qWAecchZu7nlXOtOu SGR5E9rD1b8PTa05kkxXqtuuA+U0jaFIyoRRoS7DVCc2GjdsyMLw/YyYiE7xRMuJ
Bug#921360: marked as done (No suitable for buster, package probably unmaintained)
Your message dated Sun, 10 Feb 2019 16:50:17 + with message-id and subject line Bug#921368: fixed in node-base64id 1.0.0-1 has caused the Debian Bug report #921368, regarding No suitable for buster, package probably unmaintained 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.) -- 921368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921368 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-base64id Version: 0.1.0-3 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages node-base64id depends on: ii nodejs 4.8.2~dfsg-1 node-base64id recommends no packages. node-base64id suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: node-base64id Source-Version: 1.0.0-1 We believe that the bug you reported is fixed in the latest version of node-base64id, 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 921...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated node-base64id package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 10 Feb 2019 17:22:42 +0100 Source: node-base64id Binary: node-base64id Architecture: source Version: 1.0.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 921368 Description: node-base64id - Node.js module that generates a base64 id Changes: node-base64id (1.0.0-1) unstable; urgency=medium . [ Mike Gabriel ] * debian/control: Drop myself from Uploaders: field. . [ Xavier Guimard ] * Bump debhelper compatibility level to 11 * Declare compliance with policy 4.3.0 * Change section to javascript * Change priority to optional * Set myself as uploader (Closes: #921368) * Add upstream/metadata * New upstream version 1.0.0 * Minimal test using pkg-js-tools * Fix install * Update VCS fields to salsa * Update debian/copyright Checksums-Sha1: 26204caa91d8992868df9b91bbfc98b2bc3479b8 2016 node-base64id_1.0.0-1.dsc f9610838302d50e8ea171c104f2aa995cd8b130f 2360 node-base64id_1.0.0.orig.tar.gz bf8d5c3ec1023cfe50f57a36c36f0edf28e42a0e 2576 node-base64id_1.0.0-1.debian.tar.xz Checksums-Sha256: 6c37248b36a0a820f012697d6b04b94c67f4dcc774687c2cd5a9b7ba05a8e05b 2016 node-base64id_1.0.0-1.dsc e64fcfa572fa40eb2f88045589c1eb6ca06aa67eab3037fd85c6899687c579f8 2360 node-base64id_1.0.0.orig.tar.gz 85f5d58c4280b39ce9459ed5f3c003245d9a4fd8a17cf11722884136f13af00f 2576 node-base64id_1.0.0-1.debian.tar.xz Files: a6388c0002b4af9ebcf4e9ffdadeb296 2016 javascript optional node-base64id_1.0.0-1.dsc 996aa60eb50deb68ea8d6aed48c75e45 2360 javascript optional node-base64id_1.0.0.orig.tar.gz 5b97b1c40d7cad3cffb932aeef0c1d06 2576 javascript optional node-base64id_1.0.0-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAlxgULcACgkQ9tdMp8mZ 7un+Yw/+PfdUM4aawMcJjtR+8to9L4CzPhufkj9KC1VsK5qzs0wcTnQ2ZRKnH3oI pJVF/o04KH1OW9AxGNGvAqmeIsOixsSN2jqAUrMjFfaB7N//2y9zPFPCLn3bhnQK 27U3y/3taMrhURnwh6S6Zy88+pJD9Cv5XPPD4hziRJd8RBJtt0DDsEJMqFPxGCux Y9C6Yc5Bs2/b7NUmCoNTIY3tzHzNp77x3M7mixFRkupVN9y5nt+VEbJ0kXvMSRye 12er/QBuxlZ+iHGzyKP4cSlMBeLp38Fq3+jIVrauYThAyBTRt3Sgz9nTV4z1GKr3 RLCTQ5o4ukmQja8LRUflS4k5tuwyEOS9tll+9IX7/pP4c95qWAecchZu7nlXOtOu SGR5E9rD1b8PTa05kkxXqtuuA+U0jaFIyoRRoS7DVCc2GjdsyMLw/YyYiE7xRMuJ
Bug#921368: Bug #921368 in node-base64id marked as pending
Control: tag -1 pending Hello, Bug #921368 in node-base64id 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-base64id/commit/93c490ed5500d4895967384cb480e68ed9a11d29 Set myself as uploader Closes: #921368 (this message was generated automatically) -- Greetings https://bugs.debian.org/921368
