Bug#934630: marked as done (transition: octave)
Your message dated Sat, 12 Oct 2019 07:20:39 +0200 with message-id and subject line Re: Bug#934630: transition: octave has caused the Debian Bug report #934630, regarding transition: octave 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.) -- 934630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934630 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Control: forwarded -1 https://release.debian.org/transitions/html/auto-octave.html Dear Release Team, Please schedule a transition for octave 5. Most reverse dependencies have already been updated by the Debian Octave Group and should therefore be compatible with the new version. We stand ready to NMU other reverse dependencies should the need arise. Best, -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name ⠈⠳⣄ http://www.debian.org --- End Message --- --- Begin Message --- Hi Sébastien, On 09-10-2019 11:14, Sébastien Villemot wrote: > Le mardi 08 octobre 2019 à 20:40 +0200, Paul Gevers a écrit : >> On 08-10-2019 14:07, Sébastien Villemot wrote: >>> All packages concerned by this transition are now fixed, the only >>> exception being octave-mpi. For the latter, I suggest that it be >>> removed from testing, because the fix is not obvious, and upstream has >>> to be involved. >> >> I'll hint it away. >> >> What about the two autopkgtest failures, octave-splines and octave-tsa: >> https://qa.debian.org/excuses.php?package=octave > > Thanks, I have just uploaded fixed versions for these two. And after some urgenting and removal of libsbml, this migrated. So, closing this bug. Paul signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#927172: marked as done (python-urllib3: CVE-2019-11236)
Your message dated Sat, 12 Oct 2019 04:49:09 + with message-id and subject line Bug#927172: fixed in python-urllib3 1.25.6-1 has caused the Debian Bug report #927172, regarding python-urllib3: CVE-2019-11236 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.) -- 927172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927172 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-urllib3 Version: 1.24.1-1 Severity: important Tags: security upstream Forwarded: https://github.com/urllib3/urllib3/issues/1553 Hi, The following vulnerability was published for python-urllib3. CVE-2019-11236[0]: | In the urllib3 library through 1.24.1 for Python, CRLF injection is | possible if the attacker controls the request parameter. 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-11236 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11236 [1] https://github.com/urllib3/urllib3/issues/1553 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: python-urllib3 Source-Version: 1.25.6-1 We believe that the bug you reported is fixed in the latest version of python-urllib3, 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 927...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Drew Parsons (supplier of updated python-urllib3 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, 12 Oct 2019 11:50:26 +0800 Source: python-urllib3 Architecture: source Version: 1.25.6-1 Distribution: experimental Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Drew Parsons Closes: 927172 Changes: python-urllib3 (1.25.6-1) experimental; urgency=medium . * Team upload. . [ Ondřej Nový ] * Use debhelper-compat instead of debian/compat. * Bump Standards-Version to 4.4.0. . [ Drew Parsons ] * New upstream release. - fixes CVE-2019-11236 CRLF injection vulnerability. Closes: #927172. * Standards-Version: 4.4.1 * debhelper compatibility level 12 Checksums-Sha1: 0bb877f628a4b7b6e7515292444f637e6b70ffb0 2510 python-urllib3_1.25.6-1.dsc 6c14b5baec001af6a7f23f2a6e67df1c02d7784a 248292 python-urllib3_1.25.6.orig.tar.gz 1c06dbf72b8b0be49f0217d822b622884daf7646 10180 python-urllib3_1.25.6-1.debian.tar.xz 2438a562a917a10349e49c909a9c26662a4b6d11 8241 python-urllib3_1.25.6-1_source.buildinfo Checksums-Sha256: 7182fe0d9b728b66287b66de4a4caf91f7cc2af7b4b086a8d058f1c8369b03a6 2510 python-urllib3_1.25.6-1.dsc 9a107b99a5393caf59c7aa3c1249c16e6879447533d0887f4336dde834c7be86 248292 python-urllib3_1.25.6.orig.tar.gz 202eb5ee49e8d3574887c18e76b1f2a4ecfc39834f7264fb1c89e2b457775bdf 10180 python-urllib3_1.25.6-1.debian.tar.xz e6df634ece72fd4f34a820e954afd79730d5dd509296def52fa1735e24308c64 8241 python-urllib3_1.25.6-1_source.buildinfo Files: 3418bc7cbb90f71eef62a6a5c1f5f45b 2510 python optional python-urllib3_1.25.6-1.dsc a7504a9fcb7ed4ffa482fe098c80b6d4 248292 python optional python-urllib3_1.25.6.orig.tar.gz f7161c0ecf4ae6e11e2f7bf09fc1a9ae 10180 python optional python-urllib3_1.25.6-1.debian.tar.xz b2bd9c5f9c95425d4b2bc52908d438d8 8241 python optional python-urllib3_1.25.6-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAl2hVrAUHGRwYXJzb25z QGRlYmlhbi5vcmcACgkQVz7x5L1aAfrhBw//ZKdmpkT1hUc2E6Z67/cJMkuDjda1 qTTUt793S7TLjajUH1A6Glk0cj4cTR+eg78v/YgJ3oa1k02NLVhIYppPOZDiY1kI XK8N/R/v72bKWrFky63F+stXYP/iLBBWaMphzyrbSfkGd8ZUoN0eKZMqbPnLjqbo qLROed8ad+LfTQJyDgnsowv2IS3aDJFAe9Z7ECvrKYimIc7m3x+wNc7mdwgdifOX XoZoOD/6f1fm6BOZuYG6HcM1gFbmCurkQ4stfWLJ6bbScqxFY4c4TzUwn6XG0RHn 9x7lUqSOHXSQmwwiVLUWfjNimyRNwP6eUNLfPgZqfW8wjYCbZ3w2KgKdMhZJ4ati t+2ZKPaSkYlHlJM13aOXXAcHYzAXn/3872BUG8YCduIUOD8FvggAagmjDKcEkmek BMUVyIVMFJXNz9ATGISMpOy3yJl7fZeTvzjn0j5NHwTRyLL9Yc7zNmtB/b+EWLvX icyziNbdKhujpTh4KPYnWzUET8VZDS86F01c8M6NVw9pw6bU67Jwo5MoMKCpJ+I5
Bug#930576: marked as done (vim: Gdk-CRITICAL IA__gdk_drawable_get_size: assertion 'GDK_IS_DRAWABLE (drawable)' failed)
Your message dated Sat, 12 Oct 2019 03:07:48 + with message-id and subject line Bug#930576: fixed in vim 2:8.1.2136-1 has caused the Debian Bug report #930576, regarding vim: Gdk-CRITICAL IA__gdk_drawable_get_size: assertion 'GDK_IS_DRAWABLE (drawable)' failed 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.) -- 930576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930576 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: vim Version: 2:8.1.0875-4 Severity: normal Dear Maintainer, I get those lines filling up the terminal: (gvim:11681): Gdk-CRITICAL **: 23:48:15.225: IA__gdk_drawable_get_size: assertion 'GDK_IS_DRAWABLE (drawable)' failed It happens when scrolling in the right window split when the window is splitted vertically, typically when using nerdtree. To reproduce: gvim -u NONE -U NONE -N /path/to/file/long/enough/to/be/scrolled Split the window vertically. Make right split active. Scroll. In case it matters, I'm using Mate environment and I tried to change theme but to no avail. (I have no idea what triggers this warning but I read on some Internet post that warnings similar to this one could be theme related.) Please ask for more info if needed. Thanks for forwarding if I'm knocking at the wrong door. -- Jérôme -- Package-specific info: --- real paths of main Vim binaries --- /usr/bin/vi is /usr/bin/vim.gtk /usr/bin/vim is /usr/bin/vim.gtk /usr/bin/gvim is /usr/bin/vim.gtk -- System Information: Debian Release: 10.0 APT prefers testing APT policy: (700, 'testing'), (300, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages vim depends on: ii libacl1 2.2.53-4 ii libc62.28-10 ii libgpm2 1.20.7-5 ii libselinux1 2.8-1+b1 ii libtinfo66.1+20181013-2 ii vim-common 2:8.1.0875-4 ii vim-runtime 2:8.1.0875-4 vim recommends no packages. Versions of packages vim suggests: pn ctags pn vim-doc ii vim-scripts 20180807 -- no debconf information --- End Message --- --- Begin Message --- Source: vim Source-Version: 2:8.1.2136-1 We believe that the bug you reported is fixed in the latest version of vim, 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 930...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. James McCoy (supplier of updated vim package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 11 Oct 2019 21:37:58 -0400 Source: vim Architecture: source Version: 2:8.1.2136-1 Distribution: unstable Urgency: medium Maintainer: Debian Vim Maintainers Changed-By: James McCoy Closes: 375989 917859 918672 930576 932894 939369 Changes: vim (2:8.1.2136-1) unstable; urgency=medium . * Merge upstream patch v8.1.2136 + Farsi support was removed + syntax/debcontrol.vim: Recognize "Files-Excluded(-)" fields (Closes: #932894) + Swap files are automatically deleted if the file was unmodified and the process which generated the swap file isn't running. (Closes: #375989) + Fix incorrect over-indenting when auto-indent is enabled for XML files. (Closes: #918672) + Fix indentation of bash scripts with nested if blocks. (Closes: #939369) + New popup window support, via the "popup_*()" APIs + New sound support, via the "sound_*()" APIs + "localmap", "visual", "visualextra", "visualedit", "user_commands", "multi_byte", "cmdline_compl", "insert_expand", "modify_fname", and "comments" features are now always enabled. + Fix test_compiler.vim failure when locale isn't available. (Closes: #917859) * control: + Remove obsolete versioned Build-Depends on dpkg-dev * rules: + Use dh_install --list-missing * Turn vim-gtk into a transitional package to vim-gtk3 (Closes: #930576 since the IA__gdk_drawable_get_size assertions don't happen in the GTK3
Bug#932894: marked as done (vim: please highlight the Files-Excluded field(s) in d/copyright)
Your message dated Sat, 12 Oct 2019 03:07:48 + with message-id and subject line Bug#932894: fixed in vim 2:8.1.2136-1 has caused the Debian Bug report #932894, regarding vim: please highlight the Files-Excluded field(s) in d/copyright 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.) -- 932894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932894 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: vim Version: 2:8.1.0875-5 Severity: wishlist in d/copyright, the Files-Excluded header is not highlighted. Please highligt it. Also note that there might be several Files-Excluded-$component headers in case of multi tarball packages. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: vim Source-Version: 2:8.1.2136-1 We believe that the bug you reported is fixed in the latest version of vim, 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 932...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. James McCoy (supplier of updated vim package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 11 Oct 2019 21:37:58 -0400 Source: vim Architecture: source Version: 2:8.1.2136-1 Distribution: unstable Urgency: medium Maintainer: Debian Vim Maintainers Changed-By: James McCoy Closes: 375989 917859 918672 930576 932894 939369 Changes: vim (2:8.1.2136-1) unstable; urgency=medium . * Merge upstream patch v8.1.2136 + Farsi support was removed + syntax/debcontrol.vim: Recognize "Files-Excluded(-)" fields (Closes: #932894) + Swap files are automatically deleted if the file was unmodified and the process which generated the swap file isn't running. (Closes: #375989) + Fix incorrect over-indenting when auto-indent is enabled for XML files. (Closes: #918672) + Fix indentation of bash scripts with nested if blocks. (Closes: #939369) + New popup window support, via the "popup_*()" APIs + New sound support, via the "sound_*()" APIs + "localmap", "visual", "visualextra", "visualedit", "user_commands", "multi_byte", "cmdline_compl", "insert_expand", "modify_fname", and "comments" features are now always enabled. + Fix test_compiler.vim failure when locale isn't available. (Closes: #917859) * control: + Remove obsolete versioned Build-Depends on dpkg-dev * rules: + Use dh_install --list-missing * Turn vim-gtk into a transitional package to vim-gtk3 (Closes: #930576 since the IA__gdk_drawable_get_size assertions don't happen in the GTK3 build) * Declare compliance with Policy 4.4.1, no changes needed * Move /usr/bin/vim.* into /usr/libexec/vim/ * autopkgtest: + Mark the "$variant --version" tests superficial + Add new tests which run the build time tests against the installed binary/runtime. Mark it flaky for now, since there are some tests which are more prone to fail in the LXC environment. + Run autopkgtests as a dedicated user, to avoid false negative failures with upstream tests which check permissions Checksums-Sha1: 57e20485f28e8ecb34cb023a9f5b6f73d3b43ced 2898 vim_8.1.2136-1.dsc d8f8a81ee3c1e7278909a8ddbf75534aecbe81a1 14504875 vim_8.1.2136.orig.tar.gz db2d4721e447edb0cc9141d68ab682ec866b22b6 193144 vim_8.1.2136-1.debian.tar.xz 66b567c9c2d8986cf2a48232083f4582daad7ff4 21871 vim_8.1.2136-1_amd64.buildinfo Checksums-Sha256: 03d445cf384116255e4fc0710e6ab00f838a3636ff5b0cf68e041d52791425d8 2898 vim_8.1.2136-1.dsc cdd9deae782e88c774bd636435b4d91c1fd5b3d21bdc435fa8ae451c259118a5 14504875 vim_8.1.2136.orig.tar.gz 5386add2505d5f59d3a41912553b73ad73e32526c15ff410fc8250104f84471b 193144 vim_8.1.2136-1.debian.tar.xz
Bug#918672: marked as done ([vim] XML auto indentation misbehaves (adds/removes additonal/wrong indentation))
Your message dated Sat, 12 Oct 2019 03:07:48 + with message-id and subject line Bug#918672: fixed in vim 2:8.1.2136-1 has caused the Debian Bug report #918672, regarding [vim] XML auto indentation misbehaves (adds/removes additonal/wrong indentation) 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.) -- 918672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918672 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: vim Severity: normal --- Please enter the report below this line. --- Hello. Since the last update to vim, the XML auto indentation seems to be broken and is misbehaving. This bug needs vim-nox, vim-athena or similar to appear. I.e. something where automatic XML-indentation works out of the box. Every time a tag is closed or return is pressed after a closing '>', vim indents the line one more step without taking the actual indentation into account. This only affects non-root nodes. (so all nodes except the very outer node) For example: - create a file with an .xml extension (e.g. 'vi /tmp/tmp.xml'), so the XML indentation is used. - create a root node - add another node - while entering the closing '>', the node is indented one additional step. - when pressing return after the closing '>' the node is indented another additional step. - insert the closing tag in the new line. '' - after entering the closing tags '>' the tag is indented one step back. (- pressing return/adding another line break after the closing tag again removes another level of indentation) The resulting buffer looks something like this: I would expect: Regards Andre --- System information. --- Architecture: Kernel: Linux 4.19.0-1-amd64 Debian Release: buster/sid 500 unstable-debug debug.mirrors.debian.org 500 unstable deb.debian.org 1 experimental-debug deb.debian.org 1 experimentaldeb.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. --- End Message --- --- Begin Message --- Source: vim Source-Version: 2:8.1.2136-1 We believe that the bug you reported is fixed in the latest version of vim, 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. James McCoy (supplier of updated vim package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 11 Oct 2019 21:37:58 -0400 Source: vim Architecture: source Version: 2:8.1.2136-1 Distribution: unstable Urgency: medium Maintainer: Debian Vim Maintainers Changed-By: James McCoy Closes: 375989 917859 918672 930576 932894 939369 Changes: vim (2:8.1.2136-1) unstable; urgency=medium . * Merge upstream patch v8.1.2136 + Farsi support was removed + syntax/debcontrol.vim: Recognize "Files-Excluded(-)" fields (Closes: #932894) + Swap files are automatically deleted if the file was unmodified and the process which generated the swap file isn't running. (Closes: #375989) + Fix incorrect over-indenting when auto-indent is enabled for XML files. (Closes: #918672) + Fix indentation of bash scripts with nested if blocks. (Closes: #939369) + New popup window support, via the "popup_*()" APIs + New sound support, via the "sound_*()" APIs + "localmap", "visual", "visualextra", "visualedit", "user_commands", "multi_byte", "cmdline_compl", "insert_expand", "modify_fname", and "comments" features are now always enabled. + Fix test_compiler.vim failure when locale isn't available. (Closes: #917859) * control: + Remove obsolete versioned Build-Depends on dpkg-dev * rules: + Use dh_install --list-missing * Turn vim-gtk into a transitional package to vim-gtk3 (Closes: #930576 since the IA__gdk_drawable_get_size assertions don't happen in the GTK3 build) * Declare compliance with Policy 4.4.1, no changes needed * Move /usr/bin/vim.* into /usr/libexec/vim/ * autopkgtest: + Mark the
Bug#375989: marked as done ([vim] Add more options for handling an existing swap file)
Your message dated Sat, 12 Oct 2019 03:07:48 + with message-id and subject line Bug#375989: fixed in vim 2:8.1.2136-1 has caused the Debian Bug report #375989, regarding [vim] Add more options for handling an existing swap file to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 375989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=375989 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: vim Version: 1:7.0-017+8 Severity: wishlist Hi, It would be most excelent if vim had a tiny bit of added cleverness when dealing with swap files. Here are my two specific requests: 1) vim should recognize when the swap file is unchanged from the saved file, and act accordingly (perhaps this means simply reporting that they are identical) 2) more useful than many of the other options which vim presents when a swap file is found would be an option to display a diff between the swap file and the saved file cheers, Charles -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (800, 'testing'), (70, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages vim depends on: ii libc62.3.6-13GNU C Library: Shared libraries ii libgpmg1 1.19.6-22 General Purpose Mouse - shared lib ii libncurses5 5.5-2 Shared libraries for terminal hand ii vim-common 1:7.0-017+8 Vi IMproved - Common files ii vim-runtime 1:7.0-017+8 Vi IMproved - Runtime files vim recommends no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: vim Source-Version: 2:8.1.2136-1 We believe that the bug you reported is fixed in the latest version of vim, 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 375...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. James McCoy (supplier of updated vim package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 11 Oct 2019 21:37:58 -0400 Source: vim Architecture: source Version: 2:8.1.2136-1 Distribution: unstable Urgency: medium Maintainer: Debian Vim Maintainers Changed-By: James McCoy Closes: 375989 917859 918672 930576 932894 939369 Changes: vim (2:8.1.2136-1) unstable; urgency=medium . * Merge upstream patch v8.1.2136 + Farsi support was removed + syntax/debcontrol.vim: Recognize "Files-Excluded(-)" fields (Closes: #932894) + Swap files are automatically deleted if the file was unmodified and the process which generated the swap file isn't running. (Closes: #375989) + Fix incorrect over-indenting when auto-indent is enabled for XML files. (Closes: #918672) + Fix indentation of bash scripts with nested if blocks. (Closes: #939369) + New popup window support, via the "popup_*()" APIs + New sound support, via the "sound_*()" APIs + "localmap", "visual", "visualextra", "visualedit", "user_commands", "multi_byte", "cmdline_compl", "insert_expand", "modify_fname", and "comments" features are now always enabled. + Fix test_compiler.vim failure when locale isn't available. (Closes: #917859) * control: + Remove obsolete versioned Build-Depends on dpkg-dev * rules: + Use dh_install --list-missing * Turn vim-gtk into a transitional package to vim-gtk3 (Closes: #930576 since the IA__gdk_drawable_get_size assertions don't happen in the GTK3 build) * Declare compliance with Policy 4.4.1, no changes needed * Move /usr/bin/vim.* into /usr/libexec/vim/ * autopkgtest: + Mark the "$variant --version" tests superficial + Add new tests which run the build time tests against the installed binary/runtime. Mark it flaky for now, since there are some tests which are more prone to fail in the LXC environment. + Run autopkgtests as a dedicated user, to avoid false negative failures with upstream tests which check permissions Checksums-Sha1:
Bug#939369: marked as done (vim: bash wrong auto indentation)
Your message dated Sat, 12 Oct 2019 03:07:48 + with message-id and subject line Bug#939369: fixed in vim 2:8.1.2136-1 has caused the Debian Bug report #939369, regarding vim: bash wrong auto indentation 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.) -- 939369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939369 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: vim Version: 2:8.1.0875-5 Severity: normal Hello, Since last update (vim 8.1.1401), the auto indentation function (gg=G) is acting weirdly with bash scripts. A quick example #!/bin/bash if [[ $test1 == 1 ]]; then echo $test1 while read myvar; do if [[ $myvar == 2 ]]; then echo $myvar if [[ $myvar == 3 ]]; then echo $myvar fi fi done < <(cat testfile) fi When everything is fine under stretch (vim 8.0.707) #!/bin/bash if [[ $test1 == 1 ]]; then echo $test1 while read myvar; do if [[ $myvar == 2 ]]; then echo $myvar if [[ $myvar == 3 ]]; then echo $myvar fi fi done < <(cat testfile) fi -- Package-specific info: --- real paths of main Vim binaries --- /usr/bin/vi is /usr/bin/vim.basic /usr/bin/vim is /usr/bin/vim.basic -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages vim depends on: ii libacl1 2.2.53-4 ii libc62.28-10 ii libgpm2 1.20.7-5+b1 ii libselinux1 2.9-2+b2 ii libtinfo66.1+20190803-1 ii vim-common 2:8.1.0875-5 ii vim-runtime 2:8.1.0875-5 vim recommends no packages. Versions of packages vim suggests: pn ctags pn vim-doc pn vim-scripts -- no debconf information --- End Message --- --- Begin Message --- Source: vim Source-Version: 2:8.1.2136-1 We believe that the bug you reported is fixed in the latest version of vim, 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 939...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. James McCoy (supplier of updated vim package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 11 Oct 2019 21:37:58 -0400 Source: vim Architecture: source Version: 2:8.1.2136-1 Distribution: unstable Urgency: medium Maintainer: Debian Vim Maintainers Changed-By: James McCoy Closes: 375989 917859 918672 930576 932894 939369 Changes: vim (2:8.1.2136-1) unstable; urgency=medium . * Merge upstream patch v8.1.2136 + Farsi support was removed + syntax/debcontrol.vim: Recognize "Files-Excluded(-)" fields (Closes: #932894) + Swap files are automatically deleted if the file was unmodified and the process which generated the swap file isn't running. (Closes: #375989) + Fix incorrect over-indenting when auto-indent is enabled for XML files. (Closes: #918672) + Fix indentation of bash scripts with nested if blocks. (Closes: #939369) + New popup window support, via the "popup_*()" APIs + New sound support, via the "sound_*()" APIs + "localmap", "visual", "visualextra", "visualedit", "user_commands", "multi_byte", "cmdline_compl", "insert_expand", "modify_fname", and "comments" features are now always enabled. + Fix test_compiler.vim failure when locale isn't available. (Closes: #917859) * control: + Remove obsolete versioned Build-Depends on dpkg-dev * rules: + Use dh_install --list-missing * Turn vim-gtk into a transitional package to vim-gtk3 (Closes: #930576 since the IA__gdk_drawable_get_size assertions don't happen in the GTK3 build) * Declare compliance with Policy 4.4.1, no changes needed * Move /usr/bin/vim.* into /usr/libexec/vim/ * autopkgtest: + Mark
Bug#917859: marked as done (vim FTBFS building for armel,armhf on arm64)
Your message dated Sat, 12 Oct 2019 03:07:48 +
with message-id
and subject line Bug#917859: fixed in vim 2:8.1.2136-1
has caused the Debian Bug report #917859,
regarding vim FTBFS building for armel,armhf on arm64
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.)
--
917859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917859
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:vim
Version: 2:8.1.0549-1
Severity: important
Hi!
I've been doing a full rebuild of the Debian archive, building all
source packages targeting armel and armhf using arm64 hardware. We are
planning in future to move all of our 32-bit armel/armhf builds to
using arm64 machines, so this rebuild is to identify packages that
might have problems with this configuration.
I've tried to build memleax for armel and armhf on top of arm64, and
it's failing one of its tests:
...
Executing Test_yank_move_change()
Executing Test_yank_put_clipboard()
Executing Test_z()
Executing Test_z_negative_lnum()
Executing Test_z_overflow()
Executed 417 tests
1 FAILED:
Found errors in Test_compiler():
function RunTheTest[40]..Test_compiler line 18: command did not fail: clist
function RunTheTest[40]..Test_compiler line 24: Pattern '\n 1 Xfoo.pl:3: Global
symbol "$foo" requires explicit package name' does not match
'\n11 Xfoo.pl:3: Global symbol "$foo" requires explicit package name (did you
forget to declare "my $foo"?)'
Test results:
>From test_search.vim:
Found errors in Test_incsearch_substitute_dump():
Run 1:
function RunTheTest[40]..Test_incsearch_substitute_dump[40]..VerifyScreenDump
line 18: See dump file difference: call
term_dumpdiff("Test_incsearch_substitute_03.dump.failed",
"dumps/Test_incsearch_substitute_03.dump")
Run 2:
function RunTheTest[40]..Test_incsearch_substitute_dump[40]..VerifyScreenDump
line 18: See dump file difference: call
term_dumpdiff("Test_incsearch_substitute_03.dump.failed",
"dumps/Test_incsearch_substitute_03.dump")
Flaky test failed too often, giving up
>From test_alot.vim:
Found errors in Test_compiler():
function RunTheTest[40]..Test_compiler line 18: command did not fail: clist
function RunTheTest[40]..Test_compiler line 24: Pattern '\n 1 Xfoo.pl:3: Global
symbol "$foo" requires explicit package name' does not match '\n11 Xfoo.pl:3:
Global symbol "$foo" requires explicit package name (did you forget to declare
"my $foo"?)'
TEST FAILURE
make[2]: *** [Makefile:48: report] Error 1
make[2]: Leaving directory '/<>/src/vim-basic/testdir'
make[1]: *** [Makefile:2121: scripttests] Error 2
make[1]: Leaving directory '/<>/src/vim-basic'
make: *** [debian/rules:261: build-stamp-vim-basic] Error 2
rm configure-stamp-vim-basic
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
...
I've no idea why this one particular test is failing :-(
Full build logs online at
https://www.einval.com/debian/arm/rebuild-logs/armel/FAIL/vim_2:8.1.0549-1_armel.log
https://www.einval.com/debian/arm/rebuild-logs/armhf/FAIL/vim_2:8.1.0549-1_armhf.log
-- System Information:
Debian Release: 9.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: vim
Source-Version: 2:8.1.2136-1
We believe that the bug you reported is fixed in the latest version of
vim, 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.
James McCoy (supplier of updated vim package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 11 Oct 2019 21:37:58 -0400
Source: vim
Architecture: source
Version: 2:8.1.2136-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Vim Maintainers
Changed-By: James McCoy
Closes: 375989 917859 918672 930576 932894 939369
Changes:
vim
Bug#937509: marked as done (pypureomapi: Python2 removal in sid/bullseye)
Your message dated Sat, 12 Oct 2019 02:50:38 + with message-id and subject line Bug#937509: fixed in pypureomapi 0.4-1.1 has caused the Debian Bug report #937509, regarding pypureomapi: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 937509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937509 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pypureomapi Version: 0.4-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:pypureomapi If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: pypureomapi Source-Version: 0.4-1.1 We believe that the bug you reported is fixed in the latest version of pypureomapi, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 937...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated pypureomapi 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: Fri, 04 Oct 2019 22:02:53 -0400 Source: pypureomapi Architecture: source Version: 0.4-1.1 Distribution: unstable Urgency: medium Maintainer: Dr. Torge Szczepanek Changed-By: Sandro Tosi Closes: 937509 Changes: pypureomapi (0.4-1.1) unstable; urgency=medium . * Non-maintainer upload. * Drop python2 support; Closes: #937509 Checksums-Sha1: 45b82260b01f310152680df5396d9bc87d33b3ca 1786 pypureomapi_0.4-1.1.dsc 33ef9c5dba6886f048761a3631f930ce8ed1ca07 2348 pypureomapi_0.4-1.1.debian.tar.xz 3bda01e6e9e3403d293dfbd2491370d839500a16 6085 pypureomapi_0.4-1.1_source.buildinfo Checksums-Sha256: b1fb3f725d82e6605aee1431a4bf2028ebd5f00932ab8873d7d66c9262304498 1786 pypureomapi_0.4-1.1.dsc 0cee78f7591de96e62c560db4a4226ce904db84c8020f15407feeeca0b8adc1a 2348 pypureomapi_0.4-1.1.debian.tar.xz e36cac400de8a4abc903be14b83ca40c065f08ee10b5c516c1d0508b35dc3bb8 6085 pypureomapi_0.4-1.1_source.buildinfo Files: a93db88db2a884fc9042e3a4bf939e24
Bug#938286: marked as done (python-zipstream: Python2 removal in sid/bullseye)
Your message dated Sat, 12 Oct 2019 02:34:23 + with message-id and subject line Bug#938286: fixed in python-zipstream 1.1.3-1.1 has caused the Debian Bug report #938286, regarding python-zipstream: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 938286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938286 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-zipstream Version: 1.1.3-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-zipstream If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: python-zipstream Source-Version: 1.1.3-1.1 We believe that the bug you reported is fixed in the latest version of python-zipstream, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated python-zipstream 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: Fri, 04 Oct 2019 21:44:56 -0400 Source: python-zipstream Architecture: source Version: 1.1.3-1.1 Distribution: unstable Urgency: medium Maintainer: Aigars Mahinovs Changed-By: Sandro Tosi Closes: 938286 Changes: python-zipstream (1.1.3-1.1) unstable; urgency=medium . * Non-maintainer upload. * Drop python2 support; Closes: #938286 Checksums-Sha1: 959181f63c79b9e8f70e0a1cd1cc596c27f262da 1804 python-zipstream_1.1.3-1.1.dsc 025352dab1d1e0d75d5096cfb6b8f1560859f57d 2348 python-zipstream_1.1.3-1.1.debian.tar.xz dfbc16427575b934be132f88d6a6b41bb7b347f2 6209 python-zipstream_1.1.3-1.1_source.buildinfo Checksums-Sha256: 13cf1ce2d55212e71fbb199019789bf57dc0c3c729a5dfe3ce5147754aaecd86 1804 python-zipstream_1.1.3-1.1.dsc 680481585863e9b8965c7543f638fa36240d3a31e98fee2d0a9a827d0d4a853e 2348 python-zipstream_1.1.3-1.1.debian.tar.xz e4d091b346fb56bbb2a94929d1a458a38d069ebd27a14a1b1366e64f340248b4
Bug#935281: marked as done (lepton-eda: FTBFS on amd64)
Your message dated Fri, 11 Oct 2019 22:33:58 -0400 with message-id and subject line Re: lepton-eda: FTBFS on amd64 has caused the Debian Bug report #935281, regarding lepton-eda: FTBFS on amd64 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.) -- 935281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935281 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: src:lepton-eda version: 1.9.7-2 severity: serious tags: ftbfs Hi, A binnmu of lepton-eda in unstable fails on amd64: https://buildd.debian.org/status/package.php?p=lepton-eda Cheers, Ivo --- End Message --- --- Begin Message --- lepton-eda builds fine now: https://buildd.debian.org/status/package.php?p=lepton-eda Thanks, Jeremy--- End Message ---
Bug#936278: marked as done (cdiff: Python2 removal in sid/bullseye)
Your message dated Sat, 12 Oct 2019 02:34:11 + with message-id and subject line Bug#936278: fixed in cdiff 1.0-1.1 has caused the Debian Bug report #936278, regarding cdiff: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 936278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936278 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:cdiff Version: 1.0-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:cdiff If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: cdiff Source-Version: 1.0-1.1 We believe that the bug you reported is fixed in the latest version of cdiff, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 936...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated cdiff 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: Fri, 04 Oct 2019 21:34:13 -0400 Source: cdiff Architecture: source Version: 1.0-1.1 Distribution: unstable Urgency: medium Maintainer: Michael Banck Changed-By: Sandro Tosi Closes: 936278 Changes: cdiff (1.0-1.1) unstable; urgency=medium . * Non-maintainer upload. * Drop python2 support; Closes: #936278 Checksums-Sha1: ceafa7b119aa57740fee272e0e626a6ee7933cd2 1687 cdiff_1.0-1.1.dsc dfcc2f871307375e8fead629b9b51d9ff0a8271e 1940 cdiff_1.0-1.1.debian.tar.xz 85adf2e3492531d35fb4591dd73b740662e60df2 6126 cdiff_1.0-1.1_source.buildinfo Checksums-Sha256: 18743e715f78578bde83dd6d6d1f3c060d58d5f6078754fe8a6ea69e75d8760b 1687 cdiff_1.0-1.1.dsc a473cf9b006f9913c2839e53b80ed31205126f9a50b5ca20ee2e2c4828c10dc9 1940 cdiff_1.0-1.1.debian.tar.xz 19b6e7945e77fda930293e0393bb6e72458f978ea711c41f781207638106b9fa 6126 cdiff_1.0-1.1_source.buildinfo Files: dd432873bb621ef934b2d515a305772d 1687 python optional cdiff_1.0-1.1.dsc c78571b2f76c65a992fc769263e6def5 1940 python optional
Bug#941514: marked as done (cffi: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended)
Your message dated Fri, 11 Oct 2019 23:34:07 + with message-id and subject line Bug#941514: fixed in cffi 1:0.20.1-1 has caused the Debian Bug report #941514, regarding cffi: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended 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.) -- 941514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941514 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cffi Version: 1:0.20.0-1 Severity: serious Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu eoan ubuntu-patch Dear maintainers, The texlive-generic-recommended transitional package has been dropped from texlive-base in sid. Please update your build-dependency to texlive-plain-generic instead. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org diff -Nru cffi-0.20.0/debian/control cffi-0.20.0/debian/control --- cffi-0.20.0/debian/control 2018-11-18 01:50:56.0 -0800 +++ cffi-0.20.0/debian/control 2019-10-01 12:08:40.0 -0700 @@ -9,7 +9,7 @@ sbcl, texlive-extra-utils, texlive, - texlive-generic-recommended + texlive-plain-generic Standards-Version: 4.2.1 Vcs-Browser: https://salsa.debian.org/common-lisp-team/cffi Vcs-Git: https://salsa.debian.org/common-lisp-team/cffi.git --- End Message --- --- Begin Message --- Source: cffi Source-Version: 1:0.20.1-1 We believe that the bug you reported is fixed in the latest version of cffi, 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 941...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sébastien Villemot (supplier of updated cffi 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, 12 Oct 2019 01:04:52 +0200 Source: cffi Architecture: source Version: 1:0.20.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Common Lisp Team Changed-By: Sébastien Villemot Closes: 941514 Changes: cffi (1:0.20.1-1) unstable; urgency=medium . * New upstream release * Bump to debhelper compat level 12 * Trim trailing whitespace. * Re-export upstream signing key without extra signatures. * Bump S-V to 4.4.1 * Build-Depend on texlive-plain-generic instead of obsolete texlive-generic-recommended (Closes: #941514) Checksums-Sha1: 85ee1216bde84999bbb0c61a06a5cfdbf251f32b 2329 cffi_0.20.1-1.dsc 07cfdde51a4f11b8c0e88350929d272ac800cbf3 260119 cffi_0.20.1.orig.tar.gz b59d5ffc6099cc6b02948a51ed8071d6820d1a90 488 cffi_0.20.1.orig.tar.gz.asc da226a9f340eebae86a7a513824b09a7ede32684 543724 cffi_0.20.1-1.debian.tar.xz fb0aa3cccf7cbbf5ee87329b7b2d209c543730e8 7855 cffi_0.20.1-1_amd64.buildinfo Checksums-Sha256: c23114dea8b3bf1329cb17a24efd36d450974585c434465db2bf6013fd4ecc0c 2329 cffi_0.20.1-1.dsc 6a427cc08f0418900bae8a76a690bb1c51fd61caf7efcb677d31701e0ce3ec5e 260119 cffi_0.20.1.orig.tar.gz cbe95f97a7c39477574234d779ac18b8df672b4e6a7a02a54b5b3d9118047ba6 488 cffi_0.20.1.orig.tar.gz.asc a0186d767463e656a7492645b784e86091af23cc7606092bed2896c2836a8f34 543724 cffi_0.20.1-1.debian.tar.xz 7c7c503f85ddb07b6378f154c04f38a8df82a7632424e1f0a208dd836396474c 7855 cffi_0.20.1-1_amd64.buildinfo Files: 9d3155bd5ead9353661b354137c248e2 2329 lisp optional cffi_0.20.1-1.dsc b8a8337465a7b4c1be05270b777ce14f 260119 lisp optional cffi_0.20.1.orig.tar.gz c467a9e9a90870b7fa18bfc24f107d9b 488 lisp optional cffi_0.20.1.orig.tar.gz.asc 18b4d19563acc97ebb29ea4b345f8bbd 543724 lisp optional cffi_0.20.1-1.debian.tar.xz c55212e2694a88a24ff18b64819e596f 7855 lisp optional cffi_0.20.1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAl2hDEwACgkQLOzpNQ7O vkqSBw//fLVwxBVkAAU+tVuQ0Q03nhsD/5weuvoY3Ra/sHY3P+QkN29AZkaQ6Kca n4RcVwgRY9UzX0ABCj+dX/ilC+q5BC6EgcpSPvvfNkwZIf4uDtlUT5jk0IH9Ui4z
Bug#941549: marked as done (slime: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended)
Your message dated Fri, 11 Oct 2019 23:34:14 + with message-id and subject line Bug#941549: fixed in slime 2:2.24+dfsg-2 has caused the Debian Bug report #941549, regarding slime: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended 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.) -- 941549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941549 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: slime Version: 2:2.24+dfsg-1 Severity: serious Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu eoan ubuntu-patch Dear maintainers, The texlive-generic-recommended transitional package has been dropped from texlive-base in sid. Please update your build-dependency to texlive-plain-generic instead. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org diff -Nru slime-2.24+dfsg/debian/control slime-2.24+dfsg/debian/control --- slime-2.24+dfsg/debian/control 2019-08-22 13:35:43.0 -0700 +++ slime-2.24+dfsg/debian/control 2019-10-01 15:04:52.0 -0700 @@ -7,7 +7,7 @@ Sébastien Villemot Build-Depends: debhelper-compat (= 12), dh-elpa, - texlive-generic-recommended, + texlive-plain-generic, texlive-extra-utils, texlive, texinfo, --- End Message --- --- Begin Message --- Source: slime Source-Version: 2:2.24+dfsg-2 We believe that the bug you reported is fixed in the latest version of slime, 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 941...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sébastien Villemot (supplier of updated slime 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, 12 Oct 2019 01:15:08 +0200 Source: slime Architecture: source Version: 2:2.24+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Common Lisp Team Changed-By: Sébastien Villemot Closes: 941549 Changes: slime (2:2.24+dfsg-2) unstable; urgency=medium . * Build-Depend on texlive-plain-generic instead of obsolete texlive-generic-recommended (Closes: #941549) * Bump S-V to 4.4.1 * Trim trailing whitespace. * Set upstream metadata fields: Repository. Checksums-Sha1: 12366f353a3c1af74110dd12d9e113364b6bfbbc 2208 slime_2.24+dfsg-2.dsc 312d4d6bf1e7a4093eb3bccc375526cf045572e3 18688 slime_2.24+dfsg-2.debian.tar.xz f1c6e0304cb8f1b75590057665d76e0bfdaa33d3 10561 slime_2.24+dfsg-2_amd64.buildinfo Checksums-Sha256: 24f20c26859bab0b75ffd6042f827984ea588e7489be5400a392a93974a0db6f 2208 slime_2.24+dfsg-2.dsc 991f9fb1949fd02b1f5237d7c190c6a7f5dab3769635f071bd6ef0141ffabc4b 18688 slime_2.24+dfsg-2.debian.tar.xz d1acbf44fbf80eb7eec685a03ea68b52282eadec3f11aea1b627cbc9e339 10561 slime_2.24+dfsg-2_amd64.buildinfo Files: 40fba3914da921fcbf0da0c2aad591a5 2208 lisp optional slime_2.24+dfsg-2.dsc c071efd771cf99005317db42bc2a01fb 18688 lisp optional slime_2.24+dfsg-2.debian.tar.xz 303bdf2c83bc290c6317a84c8ad15622 10561 lisp optional slime_2.24+dfsg-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIyBAEBCgAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAl2hDm4ACgkQLOzpNQ7O vkq1WA/3Y1lx+f/rAA2CY+dUSOgh5TlmLk7ayh1U8s3y4qGU5Ixo8tcmpEvH3v+v 0hUnyzbYJEt4bvuNrldUB4XFnb5WvAN9y66NK1TCvSf5udk/3k7ILPMuiKpBeaoX EJc4tfpFqPquMQPlVvWY3AOkbxzm0jbxnPUHuiHqyQOvGp2vINBkY60s98X3NnCM oNSLQOwVqzkwJWGase4gQVHoKLTHOh91A+J20XIwrR86tUkqUksYwvs4voGSAbyd SKGvtk05NtIvV9VKEd25YiuKs8jTqqLB7XC+ZAkzav0I+pmoYJko9Rgzw3eYU4M6 +E04223LROT2AZvCV4OnkaI0AHWgj0LT574XSznSp+kFjrVE74ta5T8ZB1+4qrrH peIUG3AygFIZsaS2AQCNwR1JJgnutxygw2TYN3/RAtrZT243xeup54GymALUJAbw zmjHalxdGnaBES8YNI0cK/vPnePsLPVA44rWjUzhgFZRaCdXLF967BMI1EG+4Tld XYMK6emYTjFhcMtloP1N3nXYAQIAiKUw2+/Fu4FJdDQWPsZwsCqTHcYWCi+SSudv 1+t5CLn7MMnHfQOoKG1WVkcHjqW60iRKF5mwIulc6ZhaPcY8apv4el0rQ035dA4B RO39MKMFeQa5CPr5TXHbWYs1nHfkNkOWPS242KqtlP2nyqSZ1w== =DDw8
Bug#940198: marked as done (python3-okasha-examples: missing Breaks+Replaces: python-okasha-examples)
Your message dated Fri, 11 Oct 2019 23:20:54 + with message-id and subject line Bug#940198: fixed in okasha 0.2.4-4 has caused the Debian Bug report #940198, regarding python3-okasha-examples: missing Breaks+Replaces: python-okasha-examples 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.) -- 940198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940198 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-okasha-examples Version: 0.2.4-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package python3-okasha-examples. Preparing to unpack .../python3-okasha-examples_0.2.4-3_all.deb ... Unpacking python3-okasha-examples (0.2.4-3) ... dpkg: error processing archive /var/cache/apt/archives/python3-okasha-examples_0.2.4-3_all.deb (--unpack): trying to overwrite '/usr/share/doc/python-okasha/examples/demo-themes/default/static/docbook-img/1.png', which is also in package python-okasha-examples 0.2.4-2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/python3-okasha-examples_0.2.4-3_all.deb cheers, Andreas --- End Message --- --- Begin Message --- Source: okasha Source-Version: 0.2.4-4 We believe that the bug you reported is fixed in the latest version of okasha, 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 940...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. أحمد المحمودي (Ahmed El-Mahmoudy) (supplier of updated okasha 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, 14 Sep 2019 02:55:38 +0200 Source: okasha Binary: python3-okasha python3-okasha-examples Architecture: source all Version: 0.2.4-4 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: أحمد المحمودي (Ahmed El-Mahmoudy) Description: python3-okasha - trivial WSGI web framework for Python python3-okasha-examples - trivial WSGI web framework for Python (examples) Closes: 940198 Changes: okasha (0.2.4-4) unstable; urgency=medium . * Add Breaks+Replaces: python-okasha-examples (Closes: #940198) * py3.diff: add fix for string + utf8 concatenation Checksums-Sha1: cff544750ae1b5399e4db7a3e1b18d4a48d88bdd 2135 okasha_0.2.4-4.dsc ee52ecb8216c890d5a562487a11268cc07f32cfa 18448 okasha_0.2.4-4.debian.tar.xz 28d947462f4bf192870a095eb4ca7d4e4f7835a4 6205 okasha_0.2.4-4_amd64.buildinfo d5ed780eeff158605e9b770d1325e37016ce3a21 162248 python3-okasha-examples_0.2.4-4_all.deb bfc16245a7e6ac6ce57ef332e4e85ffbfde91d35 30780 python3-okasha_0.2.4-4_all.deb Checksums-Sha256: 83ace25fe267433e932cebf44b580fc41b1e9d9ca20e09a87f18e9e6b7a4afc1 2135 okasha_0.2.4-4.dsc 0c2e2e863f15c6adbbe10833a71ec133cfbdaa99fc266cd4b96a97897e90597d 18448 okasha_0.2.4-4.debian.tar.xz f8d533a814c3663b89e2fdf3846f4ccb84a185f02634c73b66c3a7ae1a3f563d 6205 okasha_0.2.4-4_amd64.buildinfo 748ab569cca07e7758d9dbcce2d89e9da2af78e078becfe06488bc45f9a6ca86 162248 python3-okasha-examples_0.2.4-4_all.deb 36052e8e266b5206e94c3a870be2a10c8ec5cc04ef2cb7517a7879c48d29fedd 30780 python3-okasha_0.2.4-4_all.deb Files: 1f878b11993ce47ce7a07e6d0c827c50 2135 non-free/python optional okasha_0.2.4-4.dsc 43dab6c4e7651f0605eea437305587ca 18448 non-free/python optional okasha_0.2.4-4.debian.tar.xz e59963fcf0658d880b684ce50629c67b 6205 non-free/python optional okasha_0.2.4-4_amd64.buildinfo e4290c32cde21c609264410d19e1eed7 162248 non-free/python optional python3-okasha-examples_0.2.4-4_all.deb 0b7adfba3b767f6c471c456df213c251 30780 non-free/python optional python3-okasha_0.2.4-4_all.deb -BEGIN PGP SIGNATURE-
Bug#941515: marked as done (cl-asdf: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended)
Your message dated Fri, 11 Oct 2019 23:19:05 + with message-id and subject line Bug#941515: fixed in cl-asdf 2:3.3.3-3 has caused the Debian Bug report #941515, regarding cl-asdf: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended 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.) -- 941515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cl-asdf Version: 2:3.3.3-2 Severity: serious Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu eoan ubuntu-patch Dear maintainers, The texlive-generic-recommended transitional package has been dropped from texlive-base in sid. Please update your build-dependency to texlive-plain-generic instead. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org diff -Nru cl-asdf-3.3.3/debian/control cl-asdf-3.3.3/debian/control --- cl-asdf-3.3.3/debian/control2019-08-20 05:25:16.0 -0700 +++ cl-asdf-3.3.3/debian/control2019-10-01 12:28:24.0 -0700 @@ -12,7 +12,7 @@ texinfo, texlive-extra-utils, texlive, - texlive-generic-recommended, + texlive-plain-generic, sbcl Standards-Version: 4.4.0 Homepage: https://common-lisp.net/project/asdf/ --- End Message --- --- Begin Message --- Source: cl-asdf Source-Version: 2:3.3.3-3 We believe that the bug you reported is fixed in the latest version of cl-asdf, 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 941...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sébastien Villemot (supplier of updated cl-asdf 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, 12 Oct 2019 00:53:15 +0200 Source: cl-asdf Architecture: source Version: 2:3.3.3-3 Distribution: unstable Urgency: medium Maintainer: Debian Common Lisp Team Changed-By: Sébastien Villemot Closes: 941515 Changes: cl-asdf (2:3.3.3-3) unstable; urgency=medium . * Team upload * Build-Depend on texlive-plain-generic, instead of obsolete texlive-generic-recommended (Closes: #941515) * Bump S-V to 4.4.1 Checksums-Sha1: f5dda79f4fb7c56304f0e22aa2df37c4ae2de78d 2238 cl-asdf_3.3.3-3.dsc 455d30354bb76b9173973fa2f8e7e1b461e162f9 27640 cl-asdf_3.3.3-3.debian.tar.xz cd517de499545943741a463d4e13f64ce76a3532 7865 cl-asdf_3.3.3-3_amd64.buildinfo Checksums-Sha256: 1cbcd91070d31f3d8aee62fbc8c3211fc1a8b0b6bd069936def46a36f38f77d4 2238 cl-asdf_3.3.3-3.dsc a46d31c24c598785ac47f87ee672ecb8295842b8079e45f282ee3ab6aa87e1e3 27640 cl-asdf_3.3.3-3.debian.tar.xz 977afcf719798c996ea8db6bcbeec2b976988fa56e138383acea820c8075b5f7 7865 cl-asdf_3.3.3-3_amd64.buildinfo Files: 399f94f902da0dc3b929734800879d20 2238 lisp optional cl-asdf_3.3.3-3.dsc 6b96125763407fab8fb1dd8134d2c5ba 27640 lisp optional cl-asdf_3.3.3-3.debian.tar.xz 145602453d2a97a310d1c1e4ce8a72e9 7865 lisp optional cl-asdf_3.3.3-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAl2hCQAACgkQLOzpNQ7O vkogrg/+NtSh9W5BpgAV9VWfsOJgoH5AqLLsGxz4cRLVuZ5VNvIVtFNJTZWV/m23 uI7s/+OkMIS5foEoWujuD7R3aU9ro1doIVm9/9smcnLKUeE9nSq2W/bk9GLWFnsC k9ttsGu8jvkJTKeZFtjKEyqTuEWUwyQ81Q6TQhq+UXKrG/Lwtf+iNfuk5Cxcbt/P 6J/86X1H/b8JBo/rcVug6cAyP7r7OAK8vDKw5uPrBn+3eZP7zPL4DHyo0pY7X11E zJjqt71BhiihAWmsSg54xNwmKkHtatTnhbyI+C8pv99HMDPz6fHAeDF5ESTzRu/B Ud5gH/LX8uMak8tJeFmN7mb/REbhhBbRAD2Wa/Ue4h3Wk1zqGAYn/fHov/5yDo4d 4M8dc2G8o9q2cbEudnwZGu8jiirnGN8sX8hITnipu/pqQ+G/Ei4QL2O2R3PQRc2x l5cLKwTNgcU2ZEt17UibZr8qcTpuehndhnD/SR5cMtsKSdt4KsZxsQAe4l4I6f2U 7UHuwQN0Cgxoj/07Tr/AftWN5M8JdFNIOw4kCl6Sn8/tLbO0qPZ2EwHkmxhyDEei iBW+5p2Ms6pVx1ElTEVRGFfDb9j/L2H141HaN/t+rDRKDsPXp2iQqLlL9PbulOW8 p0cLKg96Vt2ZHD4+nHqz2uFeVzqg9lzSHsq5+OkMwTv8eIWr8m0= =SrtL -END PGP SIGNATURE End Message ---
Bug#942167: marked as done (RFS: okasha/0.2.4-4 [RC] -- trivial WSGI web framework for Python)
Your message dated Sat, 12 Oct 2019 00:22:51 +0200 with message-id <2019101151.gb11...@angband.pl> and subject line Re: Bug#942167: RFS: okasha/0.2.4-4 [RC] has caused the Debian Bug report #942167, regarding RFS: okasha/0.2.4-4 [RC] -- trivial WSGI web framework for Python 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.) -- 942167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942167 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: important Hello, Please sponsor the updated package okasha 0.2.4-4. It fixes the following RC bug: #940198 (serious): python3-okasha-examples: missing Breaks+Replaces: python-okasha-examples The latest entry in the Debian changelog is: okasha (0.2.4-4) unstable; urgency=medium * Add Breaks+Replaces: python-okasha-examples (Closes: #940198) * py3.diff: add fix for string + utf8 concatenation As required, I tested the package against unstable's version of lintian and it it reports: I: okasha source: testsuite-autopkgtest-missing To access further information about this package, please visit the following URL: https://mentors.debian.net/package/okasha Alternatively, it is available on Salsa: g...@salsa.debian.org:python-team/modules/okasha.git also, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/non-free/o/okasha/okasha_0.2.4-4.dsc -- أحمد المحمودي (Ahmed El-Mahmoudy) Digital design engineer GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7 GPG Fingerprints: 6E2E E4BB 72E2 F417 D066 6ABF 7B30 B496 A7EF 5761 8206 A196 2084 7E6D 0DF8 B176 BC19 6A94 EDDD A1B7 signature.asc Description: PGP signature --- End Message --- --- Begin Message --- On Fri, Oct 11, 2019 at 11:37:21AM +0200, أحمد المحمودي wrote: > okasha (0.2.4-4) unstable; urgency=medium > > * Add Breaks+Replaces: python-okasha-examples (Closes: #940198) > * py3.diff: add fix for string + utf8 concatenation ✓ > As required, I tested the package against unstable's version of lintian and it > it reports: > I: okasha source: testsuite-autopkgtest-missing I for one find that paying too much heed to informational lintian output can do more harm than good. They're disabled by default for a reason. Yet some places (like the mentors site) enable them without marking them as wishlist, thus making people think they're mandatory. Having autopkgtests is nice but many packages are hard to write meaningful tests for. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ A MAP07 (Dead Simple) raspberry tincture recipe: 0.5l 95% alcohol, ⣾⠁⢠⠒⠀⣿⡁ 1kg raspberries, 0.4kg sugar; put into a big jar for 1 month. ⢿⡄⠘⠷⠚⠋⠀ Filter out and throw away the fruits (can dump them into a cake, ⠈⠳⣄ etc), let the drink age at least 3-6 months.--- End Message ---
Bug#916419: marked as done (gkdebconf FTCBFS: uses the wrong pkg-config)
Your message dated Fri, 11 Oct 2019 22:19:03 + with message-id and subject line Bug#916419: fixed in gkdebconf 2.1.0 has caused the Debian Bug report #916419, regarding gkdebconf FTCBFS: uses the wrong pkg-config 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.) -- 916419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916419 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gkdebconf Version: 2.0.4 Tags: patch User: helm...@debian.org Usertags: rebootstrap gkdebconf fails to cross build from source, because configure.ac hard codes the build architecture pkg-config. The attached patch replaces the invocations with the PKG_CHECK_MODULES macro and makes gkdebconf cross buildable. Please consider applying the patch. Helmut diff --minimal -Nru gkdebconf-2.0.4/configure.ac gkdebconf-2.0.4+nmu1/configure.ac --- gkdebconf-2.0.4/configure.ac2018-10-22 21:11:13.0 +0200 +++ gkdebconf-2.0.4+nmu1/configure.ac 2018-12-14 06:58:18.0 +0100 @@ -15,10 +15,9 @@ AC_HEADER_DIRENT AC_HEADER_STDC -GKDEBCONF_CFLAGS=`pkg-config --cflags gtk+-2.0` +PKG_CHECK_MODULES([GKDEBCONF],[gtk+-2.0]) AC_SUBST([GKDEBCONF_CFLAGS]) -GKDEBCONF_LDFLAGS=`pkg-config --libs gtk+-2.0` -AC_SUBST([GKDEBCONF_LDFLAGS]) +AC_SUBST([GKDEBCONF_LIBS]) GLIB_GSETTINGS @@ -36,15 +35,7 @@ AC_SUBST(HTML_DIR) -gtk_doc_min_version=1.0 -AC_MSG_CHECKING([gtk-doc version >= $gtk_doc_min_version]) -if pkg-config --atleast-version=$gtk_doc_min_version gtk-doc; then - AC_MSG_RESULT(yes) - GTKDOC=true -else - AC_MSG_RESULT(no) - GTKDOC=false -fi +PKG_CHECK_MODULES([GTKDOC],[gtk-doc >= 1.0],[GTKDOC=true],[GTKDOC=false]) dnl Let people disable the gtk-doc stuff. AC_ARG_ENABLE(gtk-doc, [ --enable-gtk-doc Use gtk-doc to build documentation [default=no]], enable_gtk_doc="$enableval", diff --minimal -Nru gkdebconf-2.0.4/debian/changelog gkdebconf-2.0.4+nmu1/debian/changelog --- gkdebconf-2.0.4/debian/changelog2018-10-22 22:32:32.0 +0200 +++ gkdebconf-2.0.4+nmu1/debian/changelog 2018-12-14 06:58:18.0 +0100 @@ -1,3 +1,10 @@ +gkdebconf (2.0.4+nmu1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: Don't hard code pkg-config. (Closes: #-1) + + -- Helmut Grohne Fri, 14 Dec 2018 06:58:18 +0100 + gkdebconf (2.0.4) unstable; urgency=medium * QA upload. diff --minimal -Nru gkdebconf-2.0.4/src/Makefile.am gkdebconf-2.0.4+nmu1/src/Makefile.am --- gkdebconf-2.0.4/src/Makefile.am 2017-12-31 01:18:58.0 +0100 +++ gkdebconf-2.0.4+nmu1/src/Makefile.am2018-12-14 06:58:18.0 +0100 @@ -3,5 +3,5 @@ bin_PROGRAMS = gkdebconf -gkdebconf_LDADD = $(GKDEBCONF_LDFLAGS) +gkdebconf_LDADD = $(GKDEBCONF_LIBS) gkdebconf_SOURCES = main.c files.c interface.c debconf.c cbs.c config.c --- End Message --- --- Begin Message --- Source: gkdebconf Source-Version: 2.1.0 We believe that the bug you reported is fixed in the latest version of gkdebconf, 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 916...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yavor Doganov (supplier of updated gkdebconf package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 11 Oct 2019 23:45:51 +0300 Source: gkdebconf Architecture: source Version: 2.1.0 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Yavor Doganov Closes: 916419 925574 928698 Changes: gkdebconf (2.1.0) unstable; urgency=medium . * QA upload. . [ Helmut Grohne ] * Fix FTCBFS: Don't hard code pkg-config. (Closes: #916419) . [ Américo Monteiro ] * Update Portuguese translation (Closes: #925574). . [ Jean-Pierre Giraud ] * Update French
Bug#928698: marked as done (gkdebconf: [INTL:fr] French debconf templates translation)
Your message dated Fri, 11 Oct 2019 22:19:03 + with message-id and subject line Bug#928698: fixed in gkdebconf 2.1.0 has caused the Debian Bug report #928698, regarding gkdebconf: [INTL:fr] French debconf templates translation 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.) -- 928698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928698 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gkdebconf Severity: wishlist Tags: patch l10n Hi! Please find attached the french translation updated, proofread by the debian-l10n-french mailing list contributors. This file should be put as debian/po/fr.po in your package build tree. Kind Regards jipege fr.po.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: gkdebconf Source-Version: 2.1.0 We believe that the bug you reported is fixed in the latest version of gkdebconf, 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 928...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yavor Doganov (supplier of updated gkdebconf package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 11 Oct 2019 23:45:51 +0300 Source: gkdebconf Architecture: source Version: 2.1.0 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Yavor Doganov Closes: 916419 925574 928698 Changes: gkdebconf (2.1.0) unstable; urgency=medium . * QA upload. . [ Helmut Grohne ] * Fix FTCBFS: Don't hard code pkg-config. (Closes: #916419) . [ Américo Monteiro ] * Update Portuguese translation (Closes: #925574). . [ Jean-Pierre Giraud ] * Update French translation (Closes: #928698). . [ Yavor Doganov ] * Use dpkg-parsechangelog to derive version for AC_INIT. * Remove GConf migration code; stop recommending gconf2. * Port to GTK 3; adjust Build-Depends accordingly. * Use dpkg-query instead of accessing dpkg's internal database directly. * Update packages providing the debconf frontends. * Prompt the user if the GNOME frontend is missing. * Bump compat level to 12. * Convert the icon to PNG as AppStream does not support XPM. * Bump Standards-Version to 4.4.1; no changes needed. * Don't set LDFLAGS; unnecessary with GCC 9. * Update copyright years. * Restore Vcs fields; point to the new Salsa repository. Checksums-Sha1: 9ce79b2bea3c41d65603acf186ac7ab534bb228e 1544 gkdebconf_2.1.0.dsc edb2ec4385271be4ed85a145880b3af87177f38d 164692 gkdebconf_2.1.0.tar.xz 0057f04bab921287f4f99bdd4ef9ff6d07636df6 5515 gkdebconf_2.1.0_source.buildinfo Checksums-Sha256: 5b599b367908b136a79d68da8f20e8927f57a1ef2a111876e501fadefed5fe09 1544 gkdebconf_2.1.0.dsc 4cd2a8ed7fe26152b4287254f9529aa68bb1a4ce8190309cf19e5edec6025efa 164692 gkdebconf_2.1.0.tar.xz e52d28ff59800aab4708852962b680f790f60e2aead2be268bbf3e55b7c9401c 5515 gkdebconf_2.1.0_source.buildinfo Files: bf6cda73ee280bff6f9b4221fe58396b 1544 admin optional gkdebconf_2.1.0.dsc 1733497913b89689912fc4698a20db95 164692 admin optional gkdebconf_2.1.0.tar.xz 9f3fb5744c14cc97f12747d0e4508cb3 5515 admin optional gkdebconf_2.1.0_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl2g+oUACgkQweDZLphv fH4TZQ//VQbKXGj3u694fWVhl5Uf1jVRCtkzlUPwBMwli0q+xd9sBjS5Oe0eoND7 nr2Nq64j9/sC7HZ8F2x376T9kIJg8iYkMQxUp2iYOHbTMCj92+VfuUfpS4Vj0XTP FLehvk4V3PBBDB068fdlKYXJhCrgMtyp3RBRsHCiLrlZrCqdUEOmvtA0VC4kaRdS RRSAUpoEKYLSLZk6VjIkDDflPy6MbbTqf5ZDISpFyf8Z6TcMd73sBserEFK8yktM WOWarns84xKPo9xqI1k1CnI0iH7uTuuqULmqLQf5/dNTdj/wusfHckx1GpvX5EOa Qy0kVi3fg76cuS65ZRdoVPS2k7ygwq16r4+KA+XUWtk4/pkh6DhS/cFHZsf40Iay qW6L7b+UtHcQyRCFQ25igBEmoBCESwaZcCxnRf4H75LQYXBLayoK4ZPTm7UK+evD A0c/ctxPzTwTgcKJav7BWCgYqJVSldHu2PY997kmkTS5sUP8h1JAe4pm3v3eSUbU OpQn1X1WU8g5XRdoEHrFLlwGxVX4f//Kke0C86QhCno9fLnZgeBSbSHY46axuyHR 93K7+P0nPche+kCdAww1kBzCeAMwkAS3Gr0yQIZgVfluNjaK2eN+zpkElzbKk3K0 sTJpJ6JJdoJUvLt+T9gKHtmwmr8qYMOYtkLFB1j5AXFR+4x2SXc= =u3iH -END PGP SIGNATURE End Message ---
Bug#925574: marked as done (gkdebconf: [INTL:pt] Updated Portuguese translation - prog messages)
Your message dated Fri, 11 Oct 2019 22:19:03 + with message-id and subject line Bug#925574: fixed in gkdebconf 2.1.0 has caused the Debian Bug report #925574, regarding gkdebconf: [INTL:pt] Updated Portuguese translation - prog messages 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.) -- 925574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925574 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gkdebconf Version: 2.0.4 Tags: l10n, patch Severity: wishlist Updated Portuguese translation for gkdebconf's messages Translator: Américo Monteiro Feel free to use it. Please place this file in the "pt" directory and not in pt_PT this time For translation updates please contact 'Last Translator' -- Melhores cumprimentos/Best regards, Américo Monteiro - gkdebconf_2.0.4_pt_PT.po.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: gkdebconf Source-Version: 2.1.0 We believe that the bug you reported is fixed in the latest version of gkdebconf, 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 925...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yavor Doganov (supplier of updated gkdebconf package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 11 Oct 2019 23:45:51 +0300 Source: gkdebconf Architecture: source Version: 2.1.0 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Yavor Doganov Closes: 916419 925574 928698 Changes: gkdebconf (2.1.0) unstable; urgency=medium . * QA upload. . [ Helmut Grohne ] * Fix FTCBFS: Don't hard code pkg-config. (Closes: #916419) . [ Américo Monteiro ] * Update Portuguese translation (Closes: #925574). . [ Jean-Pierre Giraud ] * Update French translation (Closes: #928698). . [ Yavor Doganov ] * Use dpkg-parsechangelog to derive version for AC_INIT. * Remove GConf migration code; stop recommending gconf2. * Port to GTK 3; adjust Build-Depends accordingly. * Use dpkg-query instead of accessing dpkg's internal database directly. * Update packages providing the debconf frontends. * Prompt the user if the GNOME frontend is missing. * Bump compat level to 12. * Convert the icon to PNG as AppStream does not support XPM. * Bump Standards-Version to 4.4.1; no changes needed. * Don't set LDFLAGS; unnecessary with GCC 9. * Update copyright years. * Restore Vcs fields; point to the new Salsa repository. Checksums-Sha1: 9ce79b2bea3c41d65603acf186ac7ab534bb228e 1544 gkdebconf_2.1.0.dsc edb2ec4385271be4ed85a145880b3af87177f38d 164692 gkdebconf_2.1.0.tar.xz 0057f04bab921287f4f99bdd4ef9ff6d07636df6 5515 gkdebconf_2.1.0_source.buildinfo Checksums-Sha256: 5b599b367908b136a79d68da8f20e8927f57a1ef2a111876e501fadefed5fe09 1544 gkdebconf_2.1.0.dsc 4cd2a8ed7fe26152b4287254f9529aa68bb1a4ce8190309cf19e5edec6025efa 164692 gkdebconf_2.1.0.tar.xz e52d28ff59800aab4708852962b680f790f60e2aead2be268bbf3e55b7c9401c 5515 gkdebconf_2.1.0_source.buildinfo Files: bf6cda73ee280bff6f9b4221fe58396b 1544 admin optional gkdebconf_2.1.0.dsc 1733497913b89689912fc4698a20db95 164692 admin optional gkdebconf_2.1.0.tar.xz 9f3fb5744c14cc97f12747d0e4508cb3 5515 admin optional gkdebconf_2.1.0_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl2g+oUACgkQweDZLphv fH4TZQ//VQbKXGj3u694fWVhl5Uf1jVRCtkzlUPwBMwli0q+xd9sBjS5Oe0eoND7 nr2Nq64j9/sC7HZ8F2x376T9kIJg8iYkMQxUp2iYOHbTMCj92+VfuUfpS4Vj0XTP FLehvk4V3PBBDB068fdlKYXJhCrgMtyp3RBRsHCiLrlZrCqdUEOmvtA0VC4kaRdS RRSAUpoEKYLSLZk6VjIkDDflPy6MbbTqf5ZDISpFyf8Z6TcMd73sBserEFK8yktM WOWarns84xKPo9xqI1k1CnI0iH7uTuuqULmqLQf5/dNTdj/wusfHckx1GpvX5EOa Qy0kVi3fg76cuS65ZRdoVPS2k7ygwq16r4+KA+XUWtk4/pkh6DhS/cFHZsf40Iay qW6L7b+UtHcQyRCFQ25igBEmoBCESwaZcCxnRf4H75LQYXBLayoK4ZPTm7UK+evD A0c/ctxPzTwTgcKJav7BWCgYqJVSldHu2PY997kmkTS5sUP8h1JAe4pm3v3eSUbU OpQn1X1WU8g5XRdoEHrFLlwGxVX4f//Kke0C86QhCno9fLnZgeBSbSHY46axuyHR 93K7+P0nPche+kCdAww1kBzCeAMwkAS3Gr0yQIZgVfluNjaK2eN+zpkElzbKk3K0 sTJpJ6JJdoJUvLt+T9gKHtmwmr8qYMOYtkLFB1j5AXFR+4x2SXc= =u3iH -END PGP
Bug#942192: marked as done (RFS: gkdebconf/2.1.0 [QA] -- Helper to reconfigure packages with Debconf)
Your message dated Fri, 11 Oct 2019 23:56:51 +0200 with message-id <20191011215651.ga11...@angband.pl> and subject line Re: Bug#942192: RFS: gkdebconf/2.1.0 [QA] -- Helper to reconfigure packages with Debconf has caused the Debian Bug report #942192, regarding RFS: gkdebconf/2.1.0 [QA] -- Helper to reconfigure packages with Debconf 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.) -- 942192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942192 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal Dear mentors, I'm looking for a sponsor for a QA upload of the package "gkdebconf". * Package name: gkdebconf Version : 2.1.0 Upstream Author : Gustavo Noronha Silva Agney Lopes Roth Ferraz * URL : N/A * License : GPL-2+ * Vcs : https://salsa.debian.org/debian/gkdebconf Section : admin It builds this binary package: gkdebconf - Helper to reconfigure packages with Debconf To access further information about this package, please visit the following URL: https://mentors.debian.net/package/gkdebconf Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/g/gkdebconf/gkdebconf_2.1.0.dsc Changes since the last upload: * QA upload. [ Helmut Grohne ] * Fix FTCBFS: Don't hard code pkg-config. (Closes: #916419) [ Américo Monteiro ] * Update Portuguese translation (Closes: #925574). [ Jean-Pierre Giraud ] * Update French translation (Closes: #928698). [ Yavor Doganov ] * Use dpkg-parsechangelog to derive version for AC_INIT. * Remove GConf migration code; stop recommending gconf2. * Port to GTK 3; adjust Build-Depends accordingly. * Use dpkg-query instead of accessing dpkg's internal database directly. * Update packages providing the debconf frontends. * Prompt the user if the GNOME frontend is missing. * Bump compat level to 12. * Convert the icon to PNG as AppStream does not support XPM. * Bump Standards-Version to 4.4.1; no changes needed. * Don't set LDFLAGS; unnecessary with GCC 9. * Update copyright years. * Restore Vcs fields; point to the new Salsa repository. --- End Message --- --- Begin Message --- On Sat, Oct 12, 2019 at 12:08:06AM +0300, Yavor Doganov wrote: > * Package name: gkdebconf >Version : 2.1.0 > Changes since the last upload: > >* QA upload. > >[ Helmut Grohne ] >* Fix FTCBFS: Don't hard code pkg-config. (Closes: #916419) > >[ Américo Monteiro ] >* Update Portuguese translation (Closes: #925574). > >[ Jean-Pierre Giraud ] >* Update French translation (Closes: #928698). > >[ Yavor Doganov ] >* Use dpkg-parsechangelog to derive version for AC_INIT. >* Remove GConf migration code; stop recommending gconf2. >* Port to GTK 3; adjust Build-Depends accordingly. >* Use dpkg-query instead of accessing dpkg's internal database directly. >* Update packages providing the debconf frontends. >* Prompt the user if the GNOME frontend is missing. >* Bump compat level to 12. >* Convert the icon to PNG as AppStream does not support XPM. >* Bump Standards-Version to 4.4.1; no changes needed. >* Don't set LDFLAGS; unnecessary with GCC 9. >* Update copyright years. >* Restore Vcs fields; point to the new Salsa repository. ✓ -- ⢀⣴⠾⠻⢶⣦⠀ A MAP07 (Dead Simple) raspberry tincture recipe: 0.5l 95% alcohol, ⣾⠁⢠⠒⠀⣿⡁ 1kg raspberries, 0.4kg sugar; put into a big jar for 1 month. ⢿⡄⠘⠷⠚⠋⠀ Filter out and throw away the fruits (can dump them into a cake, ⠈⠳⣄ etc), let the drink age at least 3-6 months.--- End Message ---
Bug#830726: marked as done (xtrlock: CVE-2016-10894: xtrlock does not block multitouch events)
Your message dated Fri, 11 Oct 2019 19:52:58 + with message-id and subject line Bug#830726: fixed in xtrlock 2.12 has caused the Debian Bug report #830726, regarding xtrlock: CVE-2016-10894: xtrlock does not block multitouch events 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.) -- 830726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830726 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xtrlock Version: 2.8 Severity: normal Tags: upstream Dear Maintainer, xtrlock appears not to block multitouch events when the session is locked, so that any user stumbling upon a locked session can still input multitouch events. One could imagine that this could constitute a security vulnerability (requiring physical access to the machine). Steps to reproduce (on a computer with a suitably configured touchscreen): 1. Open chromium (my example of a program that processes multitouch events) and put it in fullscreen mode. 2. Check that you can pinch and zoom (put two fingers of the screen and move them closer or further apart to change the zoom level). 3. Run xtrlock to lock the session. 4. With xtrlock running, put one finger on the screen and leave it there (the mouse pointer with the xtrlock lock icon follows that finger). While doing this, perform the pinch and zoom with two other fingers. Observed result: The pinch and zoom is taken into account by chromium even though the session is locked. Expected result: The event should not be seen by chromium while the session is locked. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xtrlock depends on: ii libc6 2.22-13 ii libx11-6 2:1.6.3-1 xtrlock recommends no packages. xtrlock suggests no packages. -- debconf-show failed --- End Message --- --- Begin Message --- Source: xtrlock Source-Version: 2.12 We believe that the bug you reported is fixed in the latest version of xtrlock, 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 830...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Lamb (supplier of updated xtrlock 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: Fri, 11 Oct 2019 12:41:39 -0700 Source: xtrlock Architecture: source Version: 2.12 Distribution: unstable Urgency: medium Maintainer: Matthew Vernon Changed-By: Chris Lamb Closes: 830726 Changes: xtrlock (2.12) unstable; urgency=medium . * CVE-2016-10894: Attempt to grab multitouch devices which are not intercepted via XGrabPointer. (Closes: #830726) * Bump Standards-Version to 4.4.1. Checksums-Sha1: 9a78849e65046057a84e060b9f2c03a571de6fb8 1602 xtrlock_2.12.dsc 90fde89622bd85ad2454de1308b10499b66f00e3 20620 xtrlock_2.12.tar.xz 4e69677968fc27410bed3b0b54a0945c65a9948f 6187 xtrlock_2.12_amd64.buildinfo Checksums-Sha256: 21c9bb1a25121afc7adbd1e96694a8390544e09437d296e83a96b6245f88aa7f 1602 xtrlock_2.12.dsc 13b634dc6c23a35386e683163d2b8be76de2229e1cd7fb82517cb8e388e278ba 20620 xtrlock_2.12.tar.xz f645e51a15122f1767f25d2580bab930aa248740be79d9a941caf674c9f3207a 6187 xtrlock_2.12_amd64.buildinfo Files: 5966c685ad31b3b00fa85d674c490eb7 1602 x11 optional xtrlock_2.12.dsc 49adf9b39eed6ea717462f5171da5a30 20620 x11 optional xtrlock_2.12.tar.xz 79be2ba64b7d7d76096b3028a2aacc88 6187 x11 optional xtrlock_2.12_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAl2g2y8ACgkQHpU+J9Qx HlglMw/8DZoBlobJZYBH/wdojjimjSblfiVpQr9WuvYQ53gEIHp7tRNYWgUfkLoP p6s5TWDfyxhio15l7fqLp2J/8WG5WlW86SYqraarpDNHbftl/D1OTtTE+LpPW09a rQKIIqS/sOJ7y5ta47hFtP8n4IahASz+g4xmvUkEz1564FQD5Qy6w1zH5ChV8CKv 8FUyPISa3igAenplGPnygNY/T1ZBsQsh2v5bdIwyiuC2JRN8cxU8eXiZ91xPCrdn FWGQrebAYoESKFJD4Zw/gOg2XSodNNADbJeZ01bvEBlIuRdbgxVbH48RtDLHf6Uq
Bug#942171: marked as done (tcpdump: FTBFS on ppc64el for test ikev2pI2)
Your message dated Fri, 11 Oct 2019 19:19:25 + with message-id and subject line Bug#942171: fixed in tcpdump 4.9.3-2 has caused the Debian Bug report #942171, regarding tcpdump: FTBFS on ppc64el for test ikev2pI2 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.) -- 942171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942171 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tcpdump Version: 4.9.3-1 Severity: serious https://buildd.debian.org/status/logs.php?pkg=tcpdump=ppc64el=sid --- 1 tests failed 441 tests passed Failed test: ikev2pI2 41c41 < (v2auth: len=196 method=rsasig authdata=() )) --- > (v2auth: len=196 method=rsasig authdata=(9d7686de6fabda36c4b374135ccca0c4596fe7636e19ee71ea7d276b4230948ab529651ba1dbec39e85e506ff90b48a57611be386a5867beccde9c9971587907251df58f0c46b473d9f0abc308eb85482f08383d) )) This is similar to bug #873377 which was supposed to be fixed in V 4.9.1-2 - logs show that for v4.9.1-2 and -3 test was not run - then it was failing but not reported as an error for the global count of success ! --- End Message --- --- Begin Message --- Source: tcpdump Source-Version: 4.9.3-2 We believe that the bug you reported is fixed in the latest version of tcpdump, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 942...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Romain Francoise (supplier of updated tcpdump package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 11 Oct 2019 20:48:04 +0200 Source: tcpdump Architecture: source Version: 4.9.3-2 Distribution: unstable Urgency: medium Maintainer: Romain Francoise Changed-By: Romain Francoise Closes: 942171 Changes: tcpdump (4.9.3-2) unstable; urgency=medium . * Disable failing IKEv2 test yet again to fix build on ppc64el (again) (closes: #942171). Checksums-Sha1: d893af588769b87c34a8570ab92f06f00e53f63a 2133 tcpdump_4.9.3-2.dsc b19062776dbe8ae290ca7a2dff77ccfc1727a07d 17384 tcpdump_4.9.3-2.debian.tar.xz db1f90a6f13899de1a719d9d0d78a00c964ffa9f 5509 tcpdump_4.9.3-2_source.buildinfo Checksums-Sha256: 52c7c4b404b71bdb4be968f1a005c04372a7c871824f3c2433479e6dc0c1f8f1 2133 tcpdump_4.9.3-2.dsc e7fd0f6fc13b931b9a1cd7fce994062411e3268d3033153b35c1676ad601f6c2 17384 tcpdump_4.9.3-2.debian.tar.xz 52df7dcb0ec860737b21e905d012c4228b3cabc33f0670d1e93125edddceeafb 5509 tcpdump_4.9.3-2_source.buildinfo Files: a7cd1665586bddca1b8d2819dd9f1f1c 2133 net optional tcpdump_4.9.3-2.dsc d3dabb64bfa1a21e53cb0fb090c094bb 17384 net optional tcpdump_4.9.3-2.debian.tar.xz 33975be2ec2fb8c8b790e8ee4e66a148 5509 net optional tcpdump_4.9.3-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEvjSXQsqYfs1+d+QtrRX0NfBfli0FAl2gz9AACgkQrRX0NfBf li2yIA//VpMRX+kAPIWUoglRzFbQiXEIaR9ssjGtZSjT3+lwoktFTq05QKmDiS/2 UL6vOD62VWGbHaJOTzd8NWe9LbQC7XBlXmKY4Km75VBRjGTE+FkkVV94jYNkJdk9 hOBRs5EuBfqy7bYty24/C4NyZblMBrgnxFYL8p/ISLUnkMCEnJuaFstsNn4jgw2E JtQGnyS6nk+DrtQTP0km/vibdFacHpz26krJv9boGcJEQNI3L5KfHNUtSIaYVqW2 /bPjIbRsbwa6OCZdgm622HCTtxnGxG3fD+P1/fAjKv+ULVNwgcxbFcRZhRz9ZJWK UvcA9yRWR1VQ5/yY4VL7YWU3BWPYwJLRsWPkgGdKkpZHuRFu5Z7jiZhAIPoe9l/w WqtEtSceCOvExnE2JQCSPCskcjgqMcwe0IfkcuLkjlI13ChqqjXQG/WH/gcOrR6d IiqwL2Wd0V+qPxj349sPXieA4g70DpMMsDuczk7moleX9t87NgBP826/1IW0NbVT nK2s2q5rrMYJC6QJD6xmTejDI/Oxx2AZ+RXrBkdeQ6/c4y1lEM5AeGM54MWSGfYD GP9TpyOqAhyWfgDEOkhgGXr9fw/NX1pnUwY3tkdHiLuit3FP5iSoKMc/LUnxBWQt NLlszlfPAbO/Gs9qPAzOH2qRLqYzD72768FXL5jcd+WKaXW/8Ho= =fZGm -END PGP SIGNATURE End
Bug#942170: marked as done (Update node-buble to a version compatible with acorn 6)
Your message dated Fri, 11 Oct 2019 17:49:19 + with message-id and subject line Bug#942170: fixed in node-buble 0.19.8-1 has caused the Debian Bug report #942170, regarding Update node-buble to a version compatible with acorn 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.) -- 942170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942170 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-buble version: 0.19.4-3 Severity: important Control: block 942169 by -1 node-acorn 6 is in experimental and rollup 1.0 will soon be uploaded to experimental. Some packages using node-buble failed to build with this error. Other packaged like node-uri-js, node-d3-color etc which does not use buble built fine. --- End Message --- --- Begin Message --- Source: node-buble Source-Version: 0.19.8-1 We believe that the bug you reported is fixed in the latest version of node-buble, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 942...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pirate Praveen (supplier of updated node-buble package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 11 Oct 2019 22:48:48 +0530 Source: node-buble Architecture: source Version: 0.19.8-1 Distribution: experimental Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Pirate Praveen Closes: 942170 Changes: node-buble (0.19.8-1) experimental; urgency=medium . * Team upload . [ Julien Puydt ] * New upstream release (Closes: #942170). * Bump std-vers to 4.4.0. * Refresh patch. * Add patch to remove browser bundling. . [ Xavier Guimard ] * Bump debhelper compatibility level to 12 * Add debian/gbp.conf * Move installed files to /usr/share/nodejs . [ Pirate Praveen ] * Disable tests during build (tests need node-acorn from experimental, but build needs node-acorn from unstable) * Update dependencies (node-acorn >= 6.0 and Breaks rollup << 1.0) * Exclude .eslintrc from bin in debian/install Checksums-Sha1: 509b53a0262d3fa47f4ce51f93180e41b128ecfc 2462 node-buble_0.19.8-1.dsc 0065787a14959863a8a98a9532d9f296f269bb0f 105495 node-buble_0.19.8.orig.tar.gz 761eebc2582e74d8d9e779efcfdeeb324ed74c72 5088 node-buble_0.19.8-1.debian.tar.xz 6a9cfe7de48a225897606baa143e46b05c7b24c3 12619 node-buble_0.19.8-1_amd64.buildinfo Checksums-Sha256: 9754cda46d8376f67d910eab58dedc7ac8d3ec167bdcc839a700408943fbe67e 2462 node-buble_0.19.8-1.dsc f3ff3aa26a9948c7165ad257ee0c8d28581431e712bf5086879de0c2143d946e 105495 node-buble_0.19.8.orig.tar.gz 8b78ac4f55aebec16dd0a9e6b4c846aa61a39dcf9e96d6c4329f4bfa8f199091 5088 node-buble_0.19.8-1.debian.tar.xz b482b714e493248953736e5998e9a21235cfb11548a98247753ceea7e8634b6d 12619 node-buble_0.19.8-1_amd64.buildinfo Files: 4970a1e306b65441763fa5a0670541ea 2462 javascript optional node-buble_0.19.8-1.dsc e2ddba2f1de89439f0b122e3b79404f1 105495 javascript optional node-buble_0.19.8.orig.tar.gz 2fa08f9442eb10cdc3ecbc7fb252cdd8 5088 javascript optional node-buble_0.19.8-1.debian.tar.xz 9ac67d225afc31c0357986754eebcf1f 12619 javascript optional node-buble_0.19.8-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE/OFtr184QaN6dPMgC3aSB2Kmt4UFAl2gvHgACgkQC3aSB2Km t4UH+g/7BePjS8SvmurBWyPU0NkVm4vIBxcmc41/Guss9MjbdvNIDcOOfq0XB/lF ahB6TAeEwO86GweqWCM/S16Zj8ZiPhI1gQBZ6v5/fWXmV6dpUaUO35Lx2sqaZFnJ 5dF8XtPYEc36T5pyge6YgXE+cX2JV6Yzg8VokbT5jMMnvMa1g1UAnbCqOZd4SK4C fsH/aWsaVxxkXsP/KZn2oFTwgzW77V+UpRHcY0MWEZQrfP7FCk1C2lTcn58lYmG9 OyBMWoybmSd+Cna+XD5N5mVxzQXmfvani4oZT0zQEEwXclat6ffKvvSzfQK1I3Sm caDcocVzFnI/aOf3BjiSDZppWZxD7d75i0eVwSCLh9WMpNQ4we3hA5YKNNHFaIdK erBe5sqoQfrauMpibhzav56tc3fekE4sFL5xZTDlfOTtPmGHEMoQIqXVNT7ZbfGy AfN2VyXb1x1QUvu9kczPHz9ketov6I8KxxVYsEqhzW8MV8nyzrD/ssbT1xtoVbPB Q5SnWlLF4pBt0Q3VcD2XLcyMVvlHEdP+H7wrv1gBzjlL3jWRVgCP2WVGG6sqiTrl BmOFDnRWePA4AIC0jUMo2psopHfLoLgBbxDUFBRapVSuAUKMNOU8LXKblKaAX8AS ktuNBfgnDkdXY/cJL8FeEumSNfRWAOFdHIN6UPShwGz0zlh7N1g= =1svO -END PGP SIGNATURE End Message ---
Bug#941604: marked as done (rollup 0.56 transition: rainbow.js build fails with 'Unknown option found: moduleName, dest')
Your message dated Fri, 11 Oct 2019 17:34:52 + with message-id and subject line Bug#941604: fixed in rainbow.js 2.1.4+ds-2 has caused the Debian Bug report #941604, regarding rollup 0.56 transition: rainbow.js build fails with 'Unknown option found: moduleName, dest' 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.) -- 941604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941604 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rainbow.js version: 2.1.4+ds-1 severity: important rainbow.js fails with rollup 0.56 currently in experimental. Please update your package to work with rollup 0.56. The error message is, NODE_PATH=debian/node_modules gulp pack [16:17:26] Local gulp not found in /<> [16:17:26] Try running: npm install gulp [16:17:26] Using globally installed gulp [16:17:27] Using gulpfile /<>/gulpfile.js [16:17:27] Starting 'pack'... The following options have been renamed — please update your config: entry -> input Unknown option found: moduleName, dest. Allowed keys: input, legacy, treeshake, acorn, acornInjectPlugins, context, moduleContext, plugins, onwarn, watch, cache, preferConst, experimentalDynamicImport, experimentalCodeSplitting, preserveSymlinks, entry, external, extend, amd, banner, footer, intro, format, outro, sourcemap, sourcemapFile, name, globals, interop, legacy, freeze, indent, strict, noConflict, paths, exports, file, dir, pureExternalModules [16:17:27] 'pack' errored after 229 ms [16:17:27] Error: You must supply output.name for UMD bundles at Object.error [as default] (/usr/share/nodejs/rollup/src/utils/error.js:10:15) at umd (/usr/share/nodejs/rollup/src/finalisers/umd.js:30:24) at /usr/share/nodejs/rollup/src/Chunk.js:585:27 at process._tickCallback (internal/process/next_tick.js:68:7) I tried to fix it, but I could not. --- End Message --- --- Begin Message --- Source: rainbow.js Source-Version: 2.1.4+ds-2 We believe that the bug you reported is fixed in the latest version of rainbow.js, 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 941...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated rainbow.js package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 11 Oct 2019 19:13:04 +0200 Source: rainbow.js Architecture: source Version: 2.1.4+ds-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 941604 Changes: rainbow.js (2.1.4+ds-2) unstable; urgency=medium . * Team upload * Declare compliance with policy 4.4.1 * Update rollup parameters (Closes: #941604) Checksums-Sha1: 02adac452d4a4e76d55f3d8cf2b87ff07f696e32 2102 rainbow.js_2.1.4+ds-2.dsc 8071085b380b6d226ca5f5f2dbf63fdd79212692 8108 rainbow.js_2.1.4+ds-2.debian.tar.xz Checksums-Sha256: 48bbe1f010dac326183c795ab22a55ca1a77580fddf0a66e281c16a16722042f 2102 rainbow.js_2.1.4+ds-2.dsc 7cf06e80d1d91de7f1d530891ad1f90ebe9d9607d03c4297dd947b5739d0d851 8108 rainbow.js_2.1.4+ds-2.debian.tar.xz Files: ec2f26844fc248895fe53f4a2cc418a8 2102 javascript optional rainbow.js_2.1.4+ds-2.dsc ac030172ce805763b70665a9fa88 8108 javascript optional rainbow.js_2.1.4+ds-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl2guMkACgkQ9tdMp8mZ 7ukNEQ/+IWVZaref/Ygc66cg37aEZqH2GmJSfdTkwY+X9r4uHLkK+6sU95TH5bh1 UX7SYmtDeL59dMSX+g1ziC6BAW81NHSnc6yoRNNWTGc8rstv7nJqMLMYynKwFFGa tK+sOJHT6V7XwleMbbhX1RWNG+Pbi4StCokdS40G9/4O9UQ31hvDvClC9wHres6L wdJxyzLg9DIS5LcJmjicav4g7WxZTA/HuJs6+cmfSLPhpY4ngoRGTuvt03RFRYTJ hQXfyWcjvt9hlq+pUxOyNoWQdDh376dG45RQuWkPvhcmqF8sKEVKvecaTtBSz7FQ RuqqG/qChqcv3tKRFCJRZnFYa8/X/mfye91hKmiA/mH2lr19VKWmwxT1Ra8laYuM 5OU9FcOj4yIx+xKc+E5hAvCy20XHZRzaGBabUTiMZFhbnBbndk9cwrw0J6d2V8Cm nvT04kd36fPLaVVgbubok5DfyynLrlk2xIDxsFWVwJucdfFtbgJU/hUN0+CgRwL9 P6j/zjsDJ4WKtiVihWe849GlBm10+jmeRVe7PfAQiLBrvpT0F1K5nzcusinKaDBY LsA9fai2AkJ4A5NUX2jYpW6llcdJIqhqwR3DLQ8OXwCC0NkhUBjq37qsbcHQHFJ8 vMGm9QuKDEdn3fE36yZ2UUCe0gIhjDM+d1H6LNOoeq3DLEFOP0E= =ew2s -END PGP SIGNATURE End Message ---
Bug#942185: marked as done (netatalk FTCBFS: bare pkg-config invocation)
Your message dated Fri, 11 Oct 2019 17:34:43 + with message-id and subject line Bug#942185: fixed in netatalk 3.1.12~ds-4 has caused the Debian Bug report #942185, regarding netatalk FTCBFS: bare pkg-config invocation 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.) -- 942185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942185 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: netatalk Version: 3.1.12~ds-3 Tags: patch upstream User: debian-cr...@lists.debian.org Usertags: ftcbfs netatalk fails to cross build from source, because there is one remaining bare pkg-config invocation. All others are fine. The attached patch fixes it. Please consider applying it. Helmut --- netatalk-3.1.12~ds.orig/macros/netatalk.m4 +++ netatalk-3.1.12~ds/macros/netatalk.m4 @@ -156,7 +156,8 @@ AC_ARG_WITH([tracker-prefix], [AS_HELP_STRING([--with-tracker-prefix=PATH],[Prefix of Tracker (default: none)])], [ac_cv_tracker_prefix=$withval], - [ac_cv_tracker_prefix="`pkg-config --variable=prefix tracker-sparql-$ac_cv_tracker_pkg_version`"] + [AC_REQUIRE([PKG_PROG_PKG_CONFIG]) + ac_cv_tracker_prefix="`$PKG_CONFIG --variable=prefix tracker-sparql-$ac_cv_tracker_pkg_version`"] ) AC_ARG_WITH([tracker-install-prefix], --- End Message --- --- Begin Message --- Source: netatalk Source-Version: 3.1.12~ds-4 We believe that the bug you reported is fixed in the latest version of netatalk, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 942...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated netatalk package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 11 Oct 2019 19:11:33 +0200 Source: netatalk Architecture: source Version: 3.1.12~ds-4 Distribution: unstable Urgency: medium Maintainer: Debian Netatalk team Changed-By: Jonas Smedegaard Closes: 942185 Changes: netatalk (3.1.12~ds-4) unstable; urgency=medium . * Fix Vcs-Git URL. * Extend patch 101 to support cross-building. Closes: Bug#942185. Thanks to Helmut Grohne. * Declare compliance with Debian Policy 4.2.1. * Set Rules-Requires-Root: no. Checksums-Sha1: 446eac4f924016adb3631cc10c8f02b6d264aad1 2492 netatalk_3.1.12~ds-4.dsc 0f705927d2d76d67b6928d8ae578edc41a61b399 55216 netatalk_3.1.12~ds-4.debian.tar.xz dc3cbfba030b4d8c96bc8a70620f9a97e6107dc9 9407 netatalk_3.1.12~ds-4_amd64.buildinfo Checksums-Sha256: 5ffc2ced9f51b423d3511985e0f7a92b5be413ec3e487e0b4f05ddc80dac1d2b 2492 netatalk_3.1.12~ds-4.dsc 3868a6f9a53b0d445b8683cf1bb09e2f1c90ee3116780ab65b1b40c0385092d0 55216 netatalk_3.1.12~ds-4.debian.tar.xz 5921a6f87271e1578a1d9ee6b374f2907d9544fd2c3733965ade4cf7523759f1 9407 netatalk_3.1.12~ds-4_amd64.buildinfo Files: 461704484c8fac9b0877f1c9afd0b3f8 2492 net optional netatalk_3.1.12~ds-4.dsc 9e80a78e91076a52e776d3ee757d7f51 55216 net optional netatalk_3.1.12~ds-4.debian.tar.xz 374f24f3fcd854713c54bd74039a797f 9407 net optional netatalk_3.1.12~ds-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl2gu0QACgkQLHwxRsGg ASFKGw/6A8TDWZz4HfmG2toNVMby5ZsBw5YiaKert7P8AYIJ0Md3wn7ai/cQMN4Z xGlTA/ywobPyJNOfacsfXITIVmiu49HMx4Rip8jz9ptG7M+ntMtVX5FquN2AgN7R RA8Yl0C8uDFpcG24mz1VgE/MP3U/NAdNGu3Zm0zAOnYJj/ulSS6vpaCGaIe6EWCn X3rw58GuIrT+BNZEcWm/9L8I3H6VwwlAN9VGTHbRFaVsU24Tnu25InJhMv0c2V7e g4pwlmK2MwEYUayVjiOKWCo6XdFDFU5toSo1WyeAR43VRrnWgOy/CBFkuro7Dhy5 TTtak8Y2pYLE635Djnx8Q7Zfbd5j7fqru2BDRizWXL05E2woh9Dba9yBq+ref6/s B0lVC2M3i1p6DbgkcZ2H4VcfQmk+uTRYCeoSDTQX1+zDCD1GIXlKQa5jVOY5T44i eWjMugjBDLk5KLE0rg10CzWSBJLAYlRcN0ScG06tVXrrzwfZWBf8RMWKBa9CHwrg yNztNIELNEppjiyU2fjAKkVaTb85rFXsDFJ9Kf+CfvXXI9IAmsdbkr0lcg4jYMiy ttGYOLP2NW5ZkqfYaQ7mF0qmqrQ1dToqPp0bsv8PUxowKY7pT4unA3uZNGMnPpT+ nM5jqSbo7b/HRoJpMhL4ZuVNUg/EEnWnBoBCo2R1D8M5DZR+pRA= =Wuad -END PGP SIGNATURE End Message ---
Bug#933020: marked as done (libvirt ftbfs in unstable (configure fails))
Your message dated Fri, 11 Oct 2019 19:18:09 +0200 with message-id <20191011171807.cud53gi7n33tq...@debian.org> and subject line Re: libvirt ftbfs in unstable (configure fails) has caused the Debian Bug report #933020, regarding libvirt ftbfs in unstable (configure fails) 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.) -- 933020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933020 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src: Version: 5.0.0-4 Severity: serious Tags: sid bullseye seen on all architectures. [...] checking rbd/librbd.h usability... yes checking rbd/librbd.h presence... yes checking for rbd/librbd.h... yes checking for rbd_get_features... yes configure: error: Need glusterfs (libgfapi) for gluster storage driver --- End Message --- --- Begin Message --- Version: 5.6.0-2 On Thu, Jul 25, 2019 at 09:26:58PM +0200, Matthias Klose wrote: > Subject: libvirt ftbfs in unstable (configure fails) The latest upload seems to build, so this can be closed. Ivo--- End Message ---
Bug#937746: marked as done (python-fann2: Python2 removal in sid/bullseye)
Your message dated Fri, 11 Oct 2019 16:50:04 + with message-id and subject line Bug#937746: fixed in python-fann2 1:1.1.2+ds-2 has caused the Debian Bug report #937746, regarding python-fann2: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 937746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937746 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-fann2 Version: 1:1.1.2+ds-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-fann2 If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: python-fann2 Source-Version: 1:1.1.2+ds-2 We believe that the bug you reported is fixed in the latest version of python-fann2, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 937...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Kastner (supplier of updated python-fann2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 11 Oct 2019 17:50:26 +0200 Source: python-fann2 Architecture: source Version: 1:1.1.2+ds-2 Distribution: unstable Urgency: medium Maintainer: Christian Kastner Changed-By: Christian Kastner Closes: 937746 Changes: python-fann2 (1:1.1.2+ds-2) unstable; urgency=medium . * Drop Python 2 packages python-pyfann and python-fann2. (Closes: #937746) * d/source/lintian-overrides: Fix syntax issue * d/control: Bump Standards-Version to 4.4.1 (no changes needed) Checksums-Sha1: a91cd3424f4b3299f8df7018a0f5b8ae02d5c4c1 2050 python-fann2_1.1.2+ds-2.dsc 484343a7e97f9581b26a940de4d4eff29b879bbf 5100 python-fann2_1.1.2+ds-2.debian.tar.xz 2994cda8ea09f0c384f8ef2252a1c953b243ba49 6197 python-fann2_1.1.2+ds-2_source.buildinfo Checksums-Sha256: b315795d19c7b9fcb95c09dbb1ac83ec8b21feab8104148d613292f05e4df27e 2050 python-fann2_1.1.2+ds-2.dsc 2b6f35fddd13b0f10c60f4a3973222f80c6d031e422f227aff363123e1784eee 5100
Bug#942181: marked as done (gopher: Unnecessarily distributes empty directories)
Your message dated Fri, 11 Oct 2019 16:19:11 + with message-id and subject line Bug#942181: fixed in gopher 3.0.17.3 has caused the Debian Bug report #942181, regarding gopher: Unnecessarily distributes empty directories 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.) -- 942181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942181 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gopher Version: 3.0.17.2 Severity: minor Package gopher is shipping empty directories: -> % dpkg -c ./gopher_3.0.17.2_amd64.deb drwxr-xr-x root/root 0 2019-10-04 01:27 ./ drwxr-xr-x root/root 0 2019-10-04 01:27 ./etc/ drwxr-xr-x root/root 0 2019-10-04 01:27 ./etc/gopher/ -rw-r--r-- root/root 2458 2019-10-04 01:27 ./etc/gopher.hlp -rw-r--r-- root/root 3111 2019-10-04 01:27 ./etc/gopher.rc -rw-r--r-- root/root 1808 2019-10-04 01:27 ./etc/gopherremote.rc drwxr-xr-x root/root 0 2019-10-04 01:27 ./usr/ drwxr-xr-x root/root 0 2019-10-04 01:27 ./usr/bin/ -rwxr-xr-x root/root146816 2019-10-04 01:27 ./usr/bin/gopher -rwxr-xr-x root/root 56048 2019-10-04 01:27 ./usr/bin/gophfilt drwxr-xr-x root/root 0 2019-10-04 01:27 ./usr/sbin/ drwxr-xr-x root/root 0 2019-10-04 01:27 ./usr/share/ drwxr-xr-x root/root 0 2019-10-04 01:27 ./usr/share/doc/ drwxr-xr-x root/root 0 2019-10-04 01:27 ./usr/share/doc/gopher/ -rw-r--r-- root/root 2636 2008-03-02 16:38 ./usr/share/doc/gopher/FAQ -rw-r--r-- root/root 3438 2008-03-02 16:38 ./usr/share/doc/gopher/INSTALL.gz -rw-r--r-- root/root 2348 2008-03-02 16:38 ./usr/share/doc/gopher/PLATFORMS -rw-r--r-- root/root 2606 2008-03-02 16:38 ./usr/share/doc/gopher/README -rw-r--r-- root/root 718 2008-03-02 16:38 ./usr/share/doc/gopher/TODO -rw-r--r-- root/root 5687 2019-10-04 01:27 ./usr/share/doc/gopher/changelog.gz -rw-r--r-- root/root 15020 2008-03-02 16:38 ./usr/share/doc/gopher/client.changes.gz -rw-r--r-- root/root 3941 2008-03-02 16:38 ./usr/share/doc/gopher/clientlogging.vms.gz -rw-r--r-- root/root 1326 2019-10-04 00:16 ./usr/share/doc/gopher/copyright -rw-r--r-- root/root 1832 2008-03-02 16:38 ./usr/share/doc/gopher/object.changes drwxr-xr-x root/root 0 2019-10-04 01:27 ./usr/share/man/ drwxr-xr-x root/root 0 2019-10-04 01:27 ./usr/share/man/man1/ -rw-r--r-- root/root 3139 2019-10-04 01:27 ./usr/share/man/man1/gopher.1.gz -rw-r--r-- root/root 1642 2019-10-04 01:27 ./usr/share/man/man1/gophfilt.1.gz drwxr-xr-x root/root 0 2019-10-04 01:27 ./usr/share/man/man5/ -rw-r--r-- root/root 1350 2019-10-04 01:27 ./usr/share/man/man5/gopherrc.5.gz drwxr-xr-x root/root 0 2019-10-04 01:27 ./usr/share/man/man8/ At least we do not ./usr/share/man/man8/ and ./usr/sbin/ at this time. A sane approach is to drop debian/*.dirs and let debhelper utilities like dh_install to automatically handle directory creation. Best, Boyuan Ynag signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: gopher Source-Version: 3.0.17.3 We believe that the bug you reported is fixed in the latest version of gopher, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 942...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. John Goerzen (supplier of updated gopher package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 11 Oct 2019 11:09:18 -0500 Source: gopher Architecture: source Version: 3.0.17.3 Distribution: unstable Urgency: medium Maintainer: John Goerzen Changed-By: John Goerzen Closes: 942181 Changes: gopher (3.0.17.3) unstable; urgency=medium . * Remove empty directories. Closes: #942181. Checksums-Sha1: ebef597edb1f2a251ec0cff8f0fae3003b6042ad 1419 gopher_3.0.17.3.dsc c7cdb40dfc490d21f58c152557dccd3615dd5e3b 317859 gopher_3.0.17.3.tar.gz 85bda88250797e54b8b98b6369c8d34935393c1f 6425 gopher_3.0.17.3_amd64.buildinfo Checksums-Sha256: 53813b2316e768780621a1eb201b9cca677d1fde6e5a475c0fca36a216228ccd 1419 gopher_3.0.17.3.dsc
Bug#675432: marked as done (xterm scrolling is very slow)
Your message dated Fri, 11 Oct 2019 18:04:14 +0200 with message-id <87h84fw9oh@turtle.gmx.de> and subject line Re: Bug#675432: xterm scrolling is very slow has caused the Debian Bug report #675432, regarding xterm scrolling is very slow 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.) -- 675432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675432 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xterm Version: 278-1 Severity: normal Compared to Xterm in Squeeze, Xterm in Wheezy is very slow to scroll and update. This leads to distracting flashes and empty blocks when scrolling or refreshing the screen. What changed between Squeeze and Wheezy that would have caused this? -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-486 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xterm depends on: ii libc6 2.13-32 ii libfontconfig1 2.9.0-5 ii libice6 2:1.0.8-2 ii libtinfo5 5.9-7 ii libutempter01.1.5-4 ii libx11-62:1.4.99.901-2 ii libxaw7 2:1.0.10-2 ii libxft2 2.2.0-3 ii libxmu6 2:1.1.1-1 ii libxt6 1:1.1.3-1 ii xbitmaps1.1.1-1 Versions of packages xterm recommends: ii x11-utils 7.7~1 Versions of packages xterm suggests: pn xfonts-cyrillic -- no debconf information --- End Message --- --- Begin Message --- On 2019-10-10 15:04 -0700, David Griffith wrote: > Problem no longer manifests. I think there have been several updates > since my report such that the underlying bug has been fixed. Thanks, I am closing the bug hereby. Cheers, Sven--- End Message ---
Bug#885235: marked as done (weechat: please migrate to guile-2.2)
Your message dated Fri, 11 Oct 2019 16:04:24 + with message-id and subject line Bug#885235: fixed in weechat 2.6-2 has caused the Debian Bug report #885235, regarding weechat: please migrate to guile-2.2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 885235: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885235 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: weechat Severity: normal I'd like to remove guile-2.0 before the buster release, so please migrate to guile-2.2 when you can. Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 --- End Message --- --- Begin Message --- Source: weechat Source-Version: 2.6-2 We believe that the bug you reported is fixed in the latest version of weechat, 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 885...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bouthenot (supplier of updated weechat package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 11 Oct 2019 15:07:22 + Source: weechat Architecture: source Version: 2.6-2 Distribution: unstable Urgency: medium Maintainer: Emmanuel Bouthenot Changed-By: Emmanuel Bouthenot Closes: 885235 Changes: weechat (2.6-2) unstable; urgency=medium . * Add a patch from upstream to support Guile 2.2 (Closes: #885235) Checksums-Sha1: e9aad1377bc1b25d7cd0de8450d6866277cb51ba 3058 weechat_2.6-2.dsc b9e5126c1fe7e4730f15549e994571b89abbd970 19156 weechat_2.6-2.debian.tar.xz ff8ddd83430a1cb7bbfc571dba77d6d591048831 11839 weechat_2.6-2_source.buildinfo Checksums-Sha256: f6726af3bbf27f09fe2ebcfda67e09cae3714909c6b0523887b3b6b863fe3859 3058 weechat_2.6-2.dsc 948cd09c6e8de056358bcd0913d21af46e7c1ea9bc074293b3a2889438b97bfe 19156 weechat_2.6-2.debian.tar.xz 6fc150867af362a6e0adb2a7aeab34c12ab4a5dbe55d5b63243ed0ac2f8bf2b2 11839 weechat_2.6-2_source.buildinfo Files: 67a4dc1ebcb27e24b88dc10a3abb8f88 3058 net optional weechat_2.6-2.dsc b1d12653d7148b04582df23eb2ec3619 19156 net optional weechat_2.6-2.debian.tar.xz 9662c3fc5fb543763a4824d5a66826ec 11839 net optional weechat_2.6-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETQ1Tfow3vJnf8QuHSwd3I5KdQsMFAl2go4kACgkQSwd3I5Kd QsMOmQ//Tlmk/LacROSgsoHNzlz6pa98gef5imAKaIYbUkaZruSVEMPmYDqvTrHw aD5aJr27P/a7dVHw85DGWTt1R+85o65Z5bh4IjZ3SIXaY+9NyGjZWKgk7hgXqjna oU5CvjmCW/2JcrQfuCe3GUAurX4XfOnU6WYuCSfTRYM6qm+MLeCuBPlEPjmrDjHo 0Ob4b2NDXw87zDJhglDvGaImwJEBdRGPb6C/3Jc1dsbnRZwzW3uLF4UC+VdpN1XD 1xAQnFIwYwephYC+/opAxmA8+sx3Za/BwBjCUFBPFoHoOpWAb0seGFlga5Pnm6lw GUxSBIBalA9D8Lk4oKT89DsLbsgRm7osqX7WrwFK6SIuHUmOdmn3Zh4S7pDwRpUu k9DmsthaKyVuWPIT39m+M9YAvfa9PbRsSLFFLRZdXlPQLBqs1WAfGMSshvw+nf7F J5AejmisSKGaF3oFSRv/MneHwcfXfWodGtxkTakvBfuL5pq8Rf9RPq2o5ioVoWcI zCU3rNFPDTl1eKHjJD5uSrOeb3KJEzBQ575TJmyHILPAjmSbkh5kPQLtU5JBNtDz 7HfiQD20Qrql95v4Rd+s7BJOZ2YUo0qVi25Qft1xIXkXIcEstvNDcLSWNjBeztqA i6Q/rsoE62HBP8xh8xIiliCyQilGqF/CF8aYegIeeW8mWujeWy4= =ugst -END PGP SIGNATURE End Message ---
Bug#942183: marked as done (Fwd: memcached : FTBFS on ppc64el - missing ss command)
Your message dated Fri, 11 Oct 2019 15:49:36 + with message-id and subject line Bug#942183: fixed in memcached 1.5.19-2 has caused the Debian Bug report #942183, regarding Fwd: memcached : FTBFS on ppc64el - missing ss command 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.) -- 942183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: memcached Version: 1.5.19-1 autopkgtest fails on ppc64el with message ss not found. This command coming from package iproute2, I believe it is a missing dependency. --- End Message --- --- Begin Message --- Source: memcached Source-Version: 1.5.19-2 We believe that the bug you reported is fixed in the latest version of memcached, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 942...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Lamb (supplier of updated memcached 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: Fri, 11 Oct 2019 08:34:04 -0700 Source: memcached Built-For-Profiles: nocheck Architecture: source Version: 1.5.19-2 Distribution: unstable Urgency: medium Maintainer: Chris Lamb Changed-By: Chris Lamb Closes: 942183 Changes: memcached (1.5.19-2) unstable; urgency=medium . * Add iproute2 to autopkgtest dependencies. (Closes: #942183) * Try and ensure that memcached is running in the tests. * Bump Standards-Version to 4.4.1. Checksums-Sha1: 151727cbb91a8462060ce65373bfcdf1408d8869 1920 memcached_1.5.19-2.dsc a0f6f053b1a2f83f83ddd4e96071da61438514e1 14984 memcached_1.5.19-2.debian.tar.xz 03b44bc9133282cb222b49160e4fe481479efbc7 6099 memcached_1.5.19-2_amd64.buildinfo Checksums-Sha256: 23521b80305a8f3bddcfeb734d96144a68dd66bc8a6f6b6412ee608275421c36 1920 memcached_1.5.19-2.dsc 387e9db882822b69cb7e40579908ac233aa1dbc6ac18bf8ba0ac7112e161a645 14984 memcached_1.5.19-2.debian.tar.xz ec9bc5272a4beabcb3fd3d5190e66f48fadb7301100036b9cbcff2dc3e639c2b 6099 memcached_1.5.19-2_amd64.buildinfo Files: 735b215edf327caf729dc9ad5eb448a5 1920 web optional memcached_1.5.19-2.dsc 63d020dab57f5c0953ecf12eed1ab182 14984 web optional memcached_1.5.19-2.debian.tar.xz a6a3f6382a8ebad4ea9c768fc8d08793 6099 web optional memcached_1.5.19-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAl2goTUACgkQHpU+J9Qx HlhVOA//bfi/QfknNo0yac0ZQQXmhrkjxV/5ZtAQdHWVq6dUlV/8dcNBVSc/3h2E 0tZ6s84+5Ej8vFWASr9uSWtYrzm7aylsBo6nu23v8YddVP8Jyx7vWOvvvz4oASAv ugcAZ17gsMg7vTfkFNIfp1j5X1lSqvHbGA00Hr+cjtNQ2IPZv4Pdqiv/PxpN13Re Hy4gI7BKAZVTbdRxwPR54jDl8qAsKUHNvhLYTYGXx6r/bAjf8WkvIZZu3XwZ6MyS GWw8kJ2eTY89FqtZTSHGy1Z8djGoXVJio9kteWgdadXHzQPgBk8gLFW/g9LlhJ41 nztkRG2uVMHye10nnNoMI4lE0MRy5p1l2WoVQd8gYKFFAszvMZVXzy81fHhe1Lsb Cr4Zwc2CkmIWD8C6QPWLfaz9xNs48bTd9ahDGsajJK6Og73d7HkOcLRfhtrkubCe inpYFigwZ/VwqJUE0ddp3Gq8a42WG7YXNcYNZvK9+RYtZnX6cFDMolxN9iiW8PK3 N7nJU2Go4qTYj9wrCeWKGk4Z+RoknA8RpTTHDIE4014FOSOBMYUaoigO2Fo8gnWz 7dYpwiQaqm+LD7Qh6gY8N52tbe8JAZnjRpTnXyfGLVKh3pjNItgWoeKd4OIgFbnS Ty1jBxpdKHNVMg5eabNpKxi84o8QiI7uo0RKQRJO9Cgm3j33/v8= =OP1t -END PGP SIGNATURE End Message ---
Processed: closing 898032
Processing commands for cont...@bugs.debian.org: > close 898032 1.0.0-1 Bug #898032 [gpxviewer] Warnings upon start Marked as fixed in versions gpxviewer/1.0.0-1. Bug #898032 [gpxviewer] Warnings upon start Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 898032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898032 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#928100: marked as done (ebook2cwgui FTCBFS: strips with the wrong strip)
Your message dated Fri, 11 Oct 2019 13:19:08 + with message-id and subject line Bug#928100: fixed in ebook2cwgui 0.1.2-5 has caused the Debian Bug report #928100, regarding ebook2cwgui FTCBFS: strips with the wrong strip 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.) -- 928100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928100 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ebook2cwgui Version: 0.1.2-4 Tags: patch upstream User: helm...@debian.org Usertags: rebootstrap ebook2cwgui fails to cross build from source, because it uses the wrong strip via install -s. This also happens to break DEB_BUILD_OPTIONS=nostrip as well as generation of a -dbgsym package. If the Makefile made install substitutable, debhelper could take stripping in its own hands. The attached patch implements that and enables cross building a -dbgsym package or a nostrip package. Please consider applying it. Helmut --- ebook2cwgui-0.1.2.orig/Makefile +++ ebook2cwgui-0.1.2/Makefile @@ -5,6 +5,8 @@ VERSION=0.1.2 override DESTDIR:=$(DESTDIR)/usr +INSTALL ?= install + all: ebook2cwgui ebook2cwgui: @@ -16,14 +18,14 @@ -Wall `/wx/wx-config --libs --cxxflags` -o ebook2cwgui install: - install -d -v $(DESTDIR)/bin/ - install -d -v $(DESTDIR)/share/pixmaps/ - install -d -v $(DESTDIR)/share/man/man1/ - install -d -v $(DESTDIR)/share/applications/ - install -s -m 0755 ebook2cwgui $(DESTDIR)/bin/ - install-m 0644 ebook2cw.xpm$(DESTDIR)/share/pixmaps/ - install-m 0644 ebook2cwgui.1 $(DESTDIR)/share/man/man1/ - install-m 0644 ebook2cwgui.desktop $(DESTDIR)/share/applications/ + $(INSTALL) -d -v $(DESTDIR)/bin/ + $(INSTALL) -d -v $(DESTDIR)/share/pixmaps/ + $(INSTALL) -d -v $(DESTDIR)/share/man/man1/ + $(INSTALL) -d -v $(DESTDIR)/share/applications/ + $(INSTALL) -s -m 0755 ebook2cwgui $(DESTDIR)/bin/ + $(INSTALL)-m 0644 ebook2cw.xpm$(DESTDIR)/share/pixmaps/ + $(INSTALL)-m 0644 ebook2cwgui.1 $(DESTDIR)/share/man/man1/ + $(INSTALL)-m 0644 ebook2cwgui.desktop $(DESTDIR)/share/applications/ uninstall: rm -f $(DESTDIR)/bin/ebook2cwgui --- End Message --- --- Begin Message --- Source: ebook2cwgui Source-Version: 0.1.2-5 We believe that the bug you reported is fixed in the latest version of ebook2cwgui, 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 928...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Feenders (supplier of updated ebook2cwgui 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: Fri, 04 Oct 2019 00:00:00 +0100 Source: ebook2cwgui Architecture: source Version: 0.1.2-5 Distribution: unstable Urgency: low Maintainer: Debian Hamradio Maintainers Changed-By: Christoph Feenders Closes: 928100 933442 Changes: ebook2cwgui (0.1.2-5) unstable; urgency=low . * Switch from GTK 2 -> GTK 3 (Closes: #933442) * Corrected install strip (Closes: #928100) * Bump Standard-Version to 4.4.1 Checksums-Sha1: b24edbf011ddbb5a9d42a760c1d0624fd32f692f 1889 ebook2cwgui_0.1.2-5.dsc 8f82e7cec61258b111b4b068ad2645436600752e 3784 ebook2cwgui_0.1.2-5.debian.tar.xz Checksums-Sha256: e1b685ad3811c29b496f51981d83051f4e5927481ba3cd76f7c37ded645472c3 1889 ebook2cwgui_0.1.2-5.dsc 6a933bbd4968de0bf60d6962d767af018bf1b989671f132a043626ab9f00cdb5 3784 ebook2cwgui_0.1.2-5.debian.tar.xz Files: 3b5feec83645bc730edd91bb813a4798 1889 hamradio optional ebook2cwgui_0.1.2-5.dsc a17ee5210540621485ad30f7f864dacd 3784 hamradio optional ebook2cwgui_0.1.2-5.debian.tar.xz -BEGIN PGP SIGNATURE- iQJDBAEBCAAtFiEEZaEt9P4xrWusTXauM1X01jtYIcwFAl2gfY0PHGJhcnRtQGtu YXJzLmJlAAoJEDNV9NY7WCHMr28P/Ah04MFCdbd0HJdOnnmwwc/SL/mfcBtB/zAC Zkp7/wIYKLPtsM1PHnGyfx+hGVJRpYJ1/M0OADf+44W/2DgIgu+4yvuTdb90tRor 17Xqoe6a0nR/VriZ9dYmwKw4iE8jbFqsaxfn41G3+Vc3a3awh4OoJx0Bgw9NWabn jyyYt1YEROnpLlgJKYcmbVd51JE1/UkWLFTRw4P7+gt9XIIag0DZ9bxsKM68UcEf nzOlxSvkDFLEntIlBHKgUafeqkrbKyq8xOYFdJm46aPgHZV7pLGZed5sFwxWPGnG
Bug#933442: marked as done (ebook2cwgui: Please rebuild against wxWidgets GTK 3 package)
Your message dated Fri, 11 Oct 2019 13:19:08 + with message-id and subject line Bug#933442: fixed in ebook2cwgui 0.1.2-5 has caused the Debian Bug report #933442, regarding ebook2cwgui: Please rebuild against wxWidgets GTK 3 package 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.) -- 933442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933442 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ebook2cwgui Severity: normal Hi, Your package appears to be using the wxWidgets GTK 2 implementation. In Debian, we have had a GTK 3 implementation of wxWidgets for some time. For the bullseye release, the wxWidgets package maintainers plan to remove the GTK 2 version, so we kindly request that you switch your package to use the GTK 3 version. We have a transition tracker [1] setup to track progress. Switching to the GTK 3 version may be as simple as: 1) Update your Build-Depends libwxgtk3.0-dev -> libwxgtk3.0-gtk3-dev libwxgtk-media3.0-dev -> libwxgtk-media3.0-gtk3-dev 2) Rebuild 3) Test If everything seems to be working fine, that's probably all you need to do. There are a couple of known issues: 1) If your package uses wxGLCanvas, this doesn't currently work when running under Wayland. As a workaround, you can force use of X. See bug: [2] 2) If your package uses graphics contexts, it may encounter a problem with coordinate overflow. See bug: [3] If you have any questions, or need assistance with the conversion, please contact the wxWidgets team, team...@tracker.debian.org. [1] https://release.debian.org/transitions/html/wxwidgets3.0-gtk3.html [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900678 [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906060 --- End Message --- --- Begin Message --- Source: ebook2cwgui Source-Version: 0.1.2-5 We believe that the bug you reported is fixed in the latest version of ebook2cwgui, 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 933...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Feenders (supplier of updated ebook2cwgui 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: Fri, 04 Oct 2019 00:00:00 +0100 Source: ebook2cwgui Architecture: source Version: 0.1.2-5 Distribution: unstable Urgency: low Maintainer: Debian Hamradio Maintainers Changed-By: Christoph Feenders Closes: 928100 933442 Changes: ebook2cwgui (0.1.2-5) unstable; urgency=low . * Switch from GTK 2 -> GTK 3 (Closes: #933442) * Corrected install strip (Closes: #928100) * Bump Standard-Version to 4.4.1 Checksums-Sha1: b24edbf011ddbb5a9d42a760c1d0624fd32f692f 1889 ebook2cwgui_0.1.2-5.dsc 8f82e7cec61258b111b4b068ad2645436600752e 3784 ebook2cwgui_0.1.2-5.debian.tar.xz Checksums-Sha256: e1b685ad3811c29b496f51981d83051f4e5927481ba3cd76f7c37ded645472c3 1889 ebook2cwgui_0.1.2-5.dsc 6a933bbd4968de0bf60d6962d767af018bf1b989671f132a043626ab9f00cdb5 3784 ebook2cwgui_0.1.2-5.debian.tar.xz Files: 3b5feec83645bc730edd91bb813a4798 1889 hamradio optional ebook2cwgui_0.1.2-5.dsc a17ee5210540621485ad30f7f864dacd 3784 hamradio optional ebook2cwgui_0.1.2-5.debian.tar.xz -BEGIN PGP SIGNATURE- iQJDBAEBCAAtFiEEZaEt9P4xrWusTXauM1X01jtYIcwFAl2gfY0PHGJhcnRtQGtu YXJzLmJlAAoJEDNV9NY7WCHMr28P/Ah04MFCdbd0HJdOnnmwwc/SL/mfcBtB/zAC Zkp7/wIYKLPtsM1PHnGyfx+hGVJRpYJ1/M0OADf+44W/2DgIgu+4yvuTdb90tRor 17Xqoe6a0nR/VriZ9dYmwKw4iE8jbFqsaxfn41G3+Vc3a3awh4OoJx0Bgw9NWabn jyyYt1YEROnpLlgJKYcmbVd51JE1/UkWLFTRw4P7+gt9XIIag0DZ9bxsKM68UcEf nzOlxSvkDFLEntIlBHKgUafeqkrbKyq8xOYFdJm46aPgHZV7pLGZed5sFwxWPGnG 2OmGw2xlDKnV3vupY/R41lXKI/7GlH2wMMtOCV6hrMCLspNxqY4FmlcvxF91dkId lE2Rr2OrsJJUKuiO1COdq2OWNh7JunVNvKoPEeCXCjdwDvZpQfSm9G8oq+QniYqa KooRP/dxnep4U/N/I/sxLIabVHFFv9FhUFr5QP1jAVq0HRs/hbFxUI7STpc0rVeO hgc1gYu42JloTyiRVTPscfvDk75j39WXQTb0vqDm4KzBxuXiSka2E7/oZ6Qx62uL d1TttB4VNdQzXZ+vN38nlFl8Tfyi076zu7TGsRcbodeiCqx8vCQ0bseCiwwkBoYB wzybxO0vxjWmMR0DHD66CQaFa3b9RGlFsWzlVyWW3HR8HCvDJLYwRpneYzdRTfXf NYQDtLTW =5C07 -END PGP SIGNATURE End Message ---
Bug#932514: marked as done (gdb: Don't build against flex-old)
Your message dated Fri, 11 Oct 2019 12:19:51 + with message-id and subject line Bug#932514: fixed in gdb 8.3.1-1 has caused the Debian Bug report #932514, regarding gdb: Don't build against flex-old 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.) -- 932514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932514 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gdb Severity: normal Tags: patch Hi, as a maintainer of flex-old package I'm considering requesting removing it as obsolete and unmaintained version of flex. The gdb Build-Depends on flex-old optionally. Please build the package only against current flex by removing references to flex-old package such as changed in the following patch. --- a/debian/control +++ b/debian/control @@ -17,7 +17,7 @@ Build-Depends: gettext, bison, dejagnu, - flex | flex-old, + flex, procps, # Do we really care that much about running the Java tests? # gcj-jdk | gcj, --- End Message --- --- Begin Message --- Source: gdb Source-Version: 8.3.1-1 We believe that the bug you reported is fixed in the latest version of gdb, 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 932...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Héctor Orón Martínez (supplier of updated gdb package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 11 Oct 2019 13:26:07 +0200 Source: gdb Architecture: source Version: 8.3.1-1 Distribution: unstable Urgency: medium Maintainer: Héctor Orón Martínez Changed-By: Héctor Orón Martínez Closes: 865607 932514 Changes: gdb (8.3.1-1) unstable; urgency=medium . * New upstream version 8.3.1 (Closes: #865607) * debian/control: drop flex-old build depend. (Closes: #932514) * debian/salsa-ci.yml: add support for continous integration * debian/control: bump standards version, no changes Checksums-Sha1: 25329d2049592aff9c56e3ebd9cc3d0ae1d71409 2736 gdb_8.3.1-1.dsc 71fa4aec4b77f78ab0a869740a1b9d8bb8bfe0ec 21100320 gdb_8.3.1.orig.tar.xz 72bcd3cb437980f1f69c4ea4b2f956dc475571af 48880 gdb_8.3.1-1.debian.tar.xz f4b09aba5af3c0aae3f13c9360da1b04093b9d9e 9368 gdb_8.3.1-1_source.buildinfo Checksums-Sha256: d73ddadf6cde208a11bd644a43bed29f6d81d03ca7c7f4586566041379058c13 2736 gdb_8.3.1-1.dsc c5c49a1cc0df3ebfdb2697a5f81ee11b5150eba6863a0309ee6d86aebe8cd4ef 21100320 gdb_8.3.1.orig.tar.xz 3bae44c2bc4e42eeb5b06bcb37de33e918044c8b43eda84462b644a8628081a0 48880 gdb_8.3.1-1.debian.tar.xz 1ff6bf9c0788b5c750056be7c358dd16787b888395dd23facc93e197c05d8fd6 9368 gdb_8.3.1-1_source.buildinfo Files: 926fd4d725d7a626400bd2d97837800b 2736 devel optional gdb_8.3.1-1.dsc dafc987953bb6a2ed1d620ea6ecd5427 21100320 devel optional gdb_8.3.1.orig.tar.xz f62b26b1924c3e18fb6613350101257f 48880 devel optional gdb_8.3.1-1.debian.tar.xz 044015c93c1259c3a207d3e69fc580fb 9368 devel optional gdb_8.3.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE6Q8IiVReeMgqnedOryKDqnbirHsFAl2gbjUACgkQryKDqnbi rHui3w/8DMysfPGc277l6Pmq3ZV4dx/iLsZnuDtzOyis6J2gFMZVm47nlwKZ76go xiQE+PmspuxqkB7LdZf8xw1mYDBkDgdC+1nr1oKJyYRDKE2UpmwGrLaQQd1VPDIs iJV3/iuvJB+TFIs1/0hbv41e9K84j/P+DEXdNsvKRiqkxhJdPMSG3l2nQHNr3mL1 XxW1xq3eyCs6nCc2z+EATN2cdmE/hBD7irlFZnVxGm2rs0dB8CnDt634IBpZRS5/ o9JDrzOjDzlfyASwV5kTXjydDr4Sr51dinqB9AnP8Xt7a4Ok0/KTXvJkK5qaRm4f KcieKIk94ijGzRiM+BsrnmGzF4kn2nlMHo3zyrHqO5bImxdVbYesfZpH8VpJaSse a+3jyGQRxRMC/NLTHeEBlSg3lUVaqZtUgvXTQRYmrn6V43d1GWa2C/zJEHxAeOUz ifoSysp4T/WaAJ1xQznCDyebf+adAbsgTFn6/i51hSqMaNW1td0W5TC042Vgbv5a sVmv7lcsJkluGZ9Q9aH29XTQeGo13m3WKJD7eUyMG6O0K606r9RNz6Ac7ZGOrlpy 0YaJdIPgOzjHxQgXFDKGqRkWiX8vgFOrMu5obhxWvHFU1b1q2WSQ0lT6RcwLZM3F lUysA5QLzXLPRvG4aAFLA4D4vUEsPSGpo45zZVi+CDDE9d82tWU= =ZCRj -END PGP SIGNATURE End Message ---
Bug#865607: marked as done (gdb: CVE-2017-9778: Fail to detect invalid FDE header, can exhaust gdb process's virtual memory and terminate debug session)
Your message dated Fri, 11 Oct 2019 12:19:51 + with message-id and subject line Bug#865607: fixed in gdb 8.3.1-1 has caused the Debian Bug report #865607, regarding gdb: CVE-2017-9778: Fail to detect invalid FDE header, can exhaust gdb process's virtual memory and terminate debug session 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.) -- 865607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865607 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gdb Version: 7.7.1+dfsg-1 Severity: normal Tags: security upstream Forwarded: https://sourceware.org/bugzilla/show_bug.cgi?id=21600 Hi, the following vulnerability was published for gdb, filling a bug to track the issue and the fix status. CVE-2017-9778[0]: | GNU Debugger (GDB) 8.0 and earlier fails to detect a negative length | field in a DWARF section. A malformed section in an ELF binary or a | core file can cause GDB to repeatedly allocate memory until a process | limit is reached. This can, for example, impede efforts to analyze | malware with GDB. 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-2017-9778 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9778 Regards, Salvatore --- End Message --- --- Begin Message --- Source: gdb Source-Version: 8.3.1-1 We believe that the bug you reported is fixed in the latest version of gdb, 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 865...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Héctor Orón Martínez (supplier of updated gdb package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 11 Oct 2019 13:26:07 +0200 Source: gdb Architecture: source Version: 8.3.1-1 Distribution: unstable Urgency: medium Maintainer: Héctor Orón Martínez Changed-By: Héctor Orón Martínez Closes: 865607 932514 Changes: gdb (8.3.1-1) unstable; urgency=medium . * New upstream version 8.3.1 (Closes: #865607) * debian/control: drop flex-old build depend. (Closes: #932514) * debian/salsa-ci.yml: add support for continous integration * debian/control: bump standards version, no changes Checksums-Sha1: 25329d2049592aff9c56e3ebd9cc3d0ae1d71409 2736 gdb_8.3.1-1.dsc 71fa4aec4b77f78ab0a869740a1b9d8bb8bfe0ec 21100320 gdb_8.3.1.orig.tar.xz 72bcd3cb437980f1f69c4ea4b2f956dc475571af 48880 gdb_8.3.1-1.debian.tar.xz f4b09aba5af3c0aae3f13c9360da1b04093b9d9e 9368 gdb_8.3.1-1_source.buildinfo Checksums-Sha256: d73ddadf6cde208a11bd644a43bed29f6d81d03ca7c7f4586566041379058c13 2736 gdb_8.3.1-1.dsc c5c49a1cc0df3ebfdb2697a5f81ee11b5150eba6863a0309ee6d86aebe8cd4ef 21100320 gdb_8.3.1.orig.tar.xz 3bae44c2bc4e42eeb5b06bcb37de33e918044c8b43eda84462b644a8628081a0 48880 gdb_8.3.1-1.debian.tar.xz 1ff6bf9c0788b5c750056be7c358dd16787b888395dd23facc93e197c05d8fd6 9368 gdb_8.3.1-1_source.buildinfo Files: 926fd4d725d7a626400bd2d97837800b 2736 devel optional gdb_8.3.1-1.dsc dafc987953bb6a2ed1d620ea6ecd5427 21100320 devel optional gdb_8.3.1.orig.tar.xz f62b26b1924c3e18fb6613350101257f 48880 devel optional gdb_8.3.1-1.debian.tar.xz 044015c93c1259c3a207d3e69fc580fb 9368 devel optional gdb_8.3.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE6Q8IiVReeMgqnedOryKDqnbirHsFAl2gbjUACgkQryKDqnbi rHui3w/8DMysfPGc277l6Pmq3ZV4dx/iLsZnuDtzOyis6J2gFMZVm47nlwKZ76go xiQE+PmspuxqkB7LdZf8xw1mYDBkDgdC+1nr1oKJyYRDKE2UpmwGrLaQQd1VPDIs iJV3/iuvJB+TFIs1/0hbv41e9K84j/P+DEXdNsvKRiqkxhJdPMSG3l2nQHNr3mL1 XxW1xq3eyCs6nCc2z+EATN2cdmE/hBD7irlFZnVxGm2rs0dB8CnDt634IBpZRS5/ o9JDrzOjDzlfyASwV5kTXjydDr4Sr51dinqB9AnP8Xt7a4Ok0/KTXvJkK5qaRm4f KcieKIk94ijGzRiM+BsrnmGzF4kn2nlMHo3zyrHqO5bImxdVbYesfZpH8VpJaSse a+3jyGQRxRMC/NLTHeEBlSg3lUVaqZtUgvXTQRYmrn6V43d1GWa2C/zJEHxAeOUz ifoSysp4T/WaAJ1xQznCDyebf+adAbsgTFn6/i51hSqMaNW1td0W5TC042Vgbv5a sVmv7lcsJkluGZ9Q9aH29XTQeGo13m3WKJD7eUyMG6O0K606r9RNz6Ac7ZGOrlpy 0YaJdIPgOzjHxQgXFDKGqRkWiX8vgFOrMu5obhxWvHFU1b1q2WSQ0lT6RcwLZM3F lUysA5QLzXLPRvG4aAFLA4D4vUEsPSGpo45zZVi+CDDE9d82tWU= =ZCRj -END PGP SIGNATURE End
Bug#942169: marked as done (Update rollup to 1.0)
Your message dated Fri, 11 Oct 2019 12:04:57 + with message-id and subject line Bug#942169: fixed in node-rollup 1.0.2-1 has caused the Debian Bug report #942169, regarding Update rollup to 1.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 942169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942169 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rollup Version: 0.68.2-2 Control: block 911367 by -1 I have started the update process in master-1.0 branch. --- End Message --- --- Begin Message --- Source: node-rollup Source-Version: 1.0.2-1 We believe that the bug you reported is fixed in the latest version of node-rollup, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 942...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pirate Praveen (supplier of updated node-rollup package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 11 Oct 2019 17:11:02 +0530 Source: node-rollup Architecture: source Version: 1.0.2-1 Distribution: experimental Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Pirate Praveen Closes: 942169 Changes: node-rollup (1.0.2-1) experimental; urgency=medium . * New upstream version 1.0.2 (Closes: #942169) * Tighten dependency on node-acorn to use acorn 6.x * Use type definitions from node-acorn package * Drop acorn-import-meta component * Update lintian overrides Checksums-Sha1: 99815f219c09e4a7a5d8520f4895a65d00302d59 2866 node-rollup_1.0.2-1.dsc 1b47dcc0e0e5171f57d954351fb80a5088a8a921 3950 node-rollup_1.0.2.orig-turbocolor.tar.gz 0ca5a236b596b0dd3a30c0be72df8f85d9d6358c 527821 node-rollup_1.0.2.orig.tar.gz c065d06b1998e130a6e7b45893052465a0c67584 6968 node-rollup_1.0.2-1.debian.tar.xz b28c63908b83f723f44c0a1b560d6fbd3407277b 8663 node-rollup_1.0.2-1_amd64.buildinfo Checksums-Sha256: af3294cad8af9ee0ed33f0a822ac61a12693deb69837350692b4f2b77f7452e3 2866 node-rollup_1.0.2-1.dsc 064538dfc4da70f8bc3572710279a1e633771a980949b6cfc6eb1a7993ce0eea 3950 node-rollup_1.0.2.orig-turbocolor.tar.gz ecb39ee9e4bccd90431bdd8b1cc3e452954c0fa05ccc5a526592c811b9abef7a 527821 node-rollup_1.0.2.orig.tar.gz d34e4f1661437cb27235b98f9a7b50a2373638b0d326f6a3efb1529af472d252 6968 node-rollup_1.0.2-1.debian.tar.xz 13f98b6e52d366bdf2e7e2adbbcb647dc9f78340061e64e087a2b2912a71ccf0 8663 node-rollup_1.0.2-1_amd64.buildinfo Files: 82ac2edd1356931fdeef04486dd6afb3 2866 javascript optional node-rollup_1.0.2-1.dsc 74b068df433cadc11f3bf492b8a4d6f8 3950 javascript optional node-rollup_1.0.2.orig-turbocolor.tar.gz 08b7c2c9027c2254c77cd137228be35b 527821 javascript optional node-rollup_1.0.2.orig.tar.gz f554941b8748e1c0c884d4e3deacf11b 6968 javascript optional node-rollup_1.0.2-1.debian.tar.xz 4a0bd5c7d9ec28a321b894b93ecbf68d 8663 javascript optional node-rollup_1.0.2-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE/OFtr184QaN6dPMgC3aSB2Kmt4UFAl2gbcIACgkQC3aSB2Km t4UvBw//bPslSOaUDE07ngbBhACctNKAiPRJrKInRgWlsbShCCseEtV7yVxPU4iG OGfdCy0UVSY9Tk20aPyXqfpISgtenMkxyWzVAjU14NelM9LLdsg+4jXAYoEZUp+m 4JOj8CeBzqVVOE72B45qK9N1Wg5yYSwvz70YVDAg/pHluXdDPNg0k5Rr63J881j+ SJJX67rM87ztzOE7ZId2nDyIpTH7kS5tvbtvrdrFrVnjKUrW/iZr+HUy69PhgV56 KUk2fNYbb1zqNTmUxu4IQMze0Dbyzp4gqlDI8kzrfjF2n2j7fdQbZe07vLcpVCt2 0/lgPRyF1KafI8zrCLvfKm7YUmtLwBQntRo1K+srRhwSL1Ey2azSjph4EHk1vjju uNdq9LnGPqvQTlmQl4NFVhezMbKEId01GPzWSH4G60UYSpBM22DZhVyD6B1J+YhX ZqZyHXPY3S0Q0f06/2s0og25tIVGxXmS4CTiV+O9leudgTULz2fpZlY1Qt6vLLpP ITiqK1Dx8tcAPTLce+W5xIhAlT65taGzeDLj7ymCypIdac8pm/t/opf1lXJU9dXo P706UDTacMSrWKPgCQXrFU9L6RtemMCVm4SzmgG7FdE1isknC2JCOUNBYUVUgix8 QyoANh+Ae/r7/1D7VL5OiLgqtlrxoZbp6YUA0oeQN2QAqZMP25c= =ifyW -END PGP SIGNATURE End Message ---
Bug#795025: marked as done (systemd-udevd: Process '/lib/udev/hdparm' failed with exit code 5)
Your message dated Fri, 11 Oct 2019 13:51:00 +0200 with message-id <6e049e88-7495-5977-48a2-e41892085...@rsh2.donotuse.de> and subject line systemd-udevd: Process '/lib/udev/hdparm' failed with exit code 5 has caused the Debian Bug report #795025, regarding systemd-udevd: Process '/lib/udev/hdparm' failed with exit code 5 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.) -- 795025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795025 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: hdparm Version: 9.43-2 Severity: normal Message appears in systemd journal (journalctl) after startup. I think systemd-udevd processes '85-hdparm.rules' it runs '/lib/udev/hdparm', which produces the message. It's odd because previously the hdparm startup script (/etc/init.d/hdparm) runs and outputs 'Setting parameters of disc (none).' is no parameter blocks are in '/etc/hdparm.conf'. I am wondering why the udev/hdparm script is run at all, since it just parses hdparm.conf again and runs hdparm a second time. This bug was filed in ubuntu launchpad here: http://bugs.launchpad.net/ubuntu/+source/hdparm/+bug/1470014 -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 4.0.8-1-inter01-686-pae (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages hdparm depends on: ii libc6 2.19-19 ii lsb-base 4.1+Debian13+nmu1 Versions of packages hdparm recommends: ii powermgmt-base 1.31+nmu1 Versions of packages hdparm suggests: pn apmd -- no debconf information --- End Message --- --- Begin Message --- Version: 9.58+ds-2 Option handling is improved, now you should get at least the name of the failing option in the log file, also -B shouldn't be applied on disk without APM, see below. Default behavior for hdparm 9.58+ds-2 No config (/etc/hdparm.conf doesn't list any drives): * If disk supports APM, the defaults: - on boot, -B 254 - on power, -B 254 - on battery -B 128 -S36 (3 min) * no APM support: - hdparm will not run (no config!) If disk config is present in /etc/hdparm.conf: * disk supports APM - on boot, udev will call /lib/udev/hdparm, which in turn will call /usr/lib/pm-utils/power.d/95hdparm-apm for apm options and hdparm for other options. - on power, /usr/lib/pm-utils/power.d/95hdparm-apm - on battery, defaults -B 128 -S 36, use apm_battery and spindown_time to set non-default values * no APM support: - force_spindown_time and other options are applied, apm and spindown_time are ignored For USB or FireWere disks, APM & spindown_time options are ignored, other options are applied, force_spindown_time is applied too.--- End Message ---
Bug#858422: marked as done (Allow giving the gpx file from the command line)
Your message dated Fri, 11 Oct 2019 12:23:30 +0200 with message-id <20191011102330.GA27431@vis> and subject line Re: Bug#858422: Allow giving the gpx file from the command line has caused the Debian Bug report #858422, regarding Allow giving the gpx file from the command line 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.) -- 858422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858422 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gpxviewer Version: 0.5.2-1 Severity: wishlist Allow giving the gpx file from the command line. $ gpxviewer file.gpx --- End Message --- --- Begin Message --- Hi Dan, providing file names is possible (according to git at least since version 0.3.1). Closing accordingly. Please reopen if it doesn't work for you and provide more information. Cheers Jochen * 積丹尼 Dan Jacobson [2017-03-22 17:20]: Package: gpxviewer Version: 0.5.2-1 Severity: wishlist Allow giving the gpx file from the command line. $ gpxviewer file.gpx signature.asc Description: PGP signature --- End Message ---
Bug#940730: marked as done (alsa-utils: Add ucm support for whiskeylake sof-skl_hda_card audio)
Your message dated Fri, 11 Oct 2019 11:04:10 +
with message-id
and subject line Bug#940730: fixed in alsa-lib 1.1.8-2
has caused the Debian Bug report #940730,
regarding alsa-utils: Add ucm support for whiskeylake sof-skl_hda_card audio
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.)
--
940730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940730
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: alsa-utils
Version: 1.1.8-2
Severity: important
Tags: patch
Dear Maintainer,
* What led up to the situation?
The Lenovo X1 Carbon Gen 7 is using the whiskeylake processor and the audio is
not working on it.
A large part of this is the kernel SOF driver - for which a separate bug is
submitted - but we also need some new files under /usr/share/alsa/ucm/sof-
skl_hda_card to support the new audio devices.
* What exactly did you do (or not do) that was effective (or ineffective)?
Add the attached HiFi and sof-skl_hda_card.conf files to the
/usr/share/alsa/ucm/sof-skl_hda_card directory
* What was the outcome of this action?
Devices are correctly detected and configured.
* What outcome did you expect instead?
NA
Let me know if any questions or concerns. Thanks for all the help!
Mark
-- System Information:
Debian Release: 10.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.2.9 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8),
LANGUAGE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages alsa-utils depends on:
ii kmod 26-1
ii libasound21.1.8-1
ii libc6 2.28-10
ii libfftw3-single3 3.3.8-2
ii libncursesw6 6.1+20181013-2+deb10u1
ii libsamplerate00.1.9-2
ii libtinfo6 6.1+20181013-2+deb10u1
ii lsb-base 10.2019051400
ii whiptail 0.52.20-8
alsa-utils recommends no packages.
alsa-utils suggests no packages.
-- no debconf information
SectionUseCase."HiFi" {
File "HiFi"
Comment "Play HiFi quality Music"
}
# Use case Configuration for skl-hda-card
SectionVerb {
EnableSequence [
cdev "hw:sofsklhdacard"
cset "name='Master Playback Switch' on"
cset "name='Capture Switch' on"
]
DisableSequence [
cdev "hw:sofsklhdacard"
]
Value {
}
}
SectionDevice."Headphone" {
Comment "Headphone"
#ConflictingDevice [
#"Speaker"
#]
EnableSequence [
cdev "hw:sofsklhdacard"
cset "name='Headphone Playback Volume' 80"
#cset "name='Headphone Mic Boost Volume' 1"
cset "name='Headphone Playback Switch' on"
]
DisableSequence [
cdev "hw:sofsklhdacard"
cset "name='Headphone Playback Switch' off"
]
Value {
PlaybackPCM "hw:sofsklhdacard,0"
PlaybackChannels "2"
#JackHWMute "Speaker"
JackName "sof-skl_hda_card Headphone"
JackType "gpio"
JackSwitch "12"
JackControl "Headphone Jack"
}
}
SectionDevice."Speaker" {
Comment "Speaker"
#ConflictingDevice [
#"Headphone"
#]
EnableSequence [
cdev "hw:sofsklhdacard"
cset "name='Speaker Playback Switch' on"
cset "name='Speaker Playback Volume' 80"
]
DisableSequence [
cset "name='Speaker Playback Switch' off"
]
Value {
PlaybackPCM "hw:sofsklhdacard,0"
JackHWMute "Headphone"
PlaybackChannels "2"
}
}
SectionDevice."Bass Speaker" {
Comment "Bass Speaker"
# ConflictingDevice [
#"Headphone"
#]
EnableSequence [
cdev "hw:sofsklhdacard"
cset "name='Bass Speaker Playback Switch' on"
cset "name='Speaker Playback Switch' on"
cset "name='Speaker Playback Volume' 80"
]
DisableSequence [
cset "name='Speaker Playback Switch' off"
cset "name='Bass Speaker Playback Switch' off"
]
Value {
PlaybackPCM "hw:sofsklhdacard,0"
Bug#854213: marked as done (alsa-lib FTCBFS: Build-Depends: python-dev is not installable)
Your message dated Fri, 11 Oct 2019 11:04:10 + with message-id and subject line Bug#854213: fixed in alsa-lib 1.1.8-2 has caused the Debian Bug report #854213, regarding alsa-lib FTCBFS: Build-Depends: python-dev is not installable 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.) -- 854213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854213 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: alsa-lib Version: 1.1.3-3 Tags: patch User: helm...@debian.org Usertags: rebootstrap alsa-lib added python-dev to Build-Depends in version 1.1.3-3. Unfortunately, python-dev cannot be installed during cross compilation and is not what alsa-lib needs. What it needs, is a build architecture python and a host architecture python development package. That's usually requested via "python-dev:native, libpython-dev". After changing Build-Depends, it cross builds again. Please consider applying the attached patch after stretch is released. Helmut diff --minimal -Nru alsa-lib-1.1.3/debian/changelog alsa-lib-1.1.3/debian/changelog --- alsa-lib-1.1.3/debian/changelog 2017-01-24 12:30:46.0 +0100 +++ alsa-lib-1.1.3/debian/changelog 2017-02-05 07:15:23.0 +0100 @@ -1,3 +1,10 @@ +alsa-lib (1.1.3-4.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: Use cross-compatible python Build-Depends (closes: #-1) + + -- Helmut Grohne Sun, 05 Feb 2017 07:15:23 +0100 + alsa-lib (1.1.3-4) unstable; urgency=medium * Add copyright notes for src/topology. Thanks Thorsten Alteholz for diff --minimal -Nru alsa-lib-1.1.3/debian/control alsa-lib-1.1.3/debian/control --- alsa-lib-1.1.3/debian/control 2017-01-23 23:26:19.0 +0100 +++ alsa-lib-1.1.3/debian/control 2017-02-05 07:15:21.0 +0100 @@ -5,7 +5,7 @@ Uploaders: Jordi Mallach , Elimar Riesebieter , Luke Yelavich -Build-Depends: debhelper (>= 10), dpkg-dev (>= 1.16.1), python-dev +Build-Depends: debhelper (>= 10), dpkg-dev (>= 1.16.1), python-dev:native, libpython-dev Build-Depends-Indep: doxygen, graphviz Standards-Version: 3.9.8 Homepage: https://www.alsa-project.org/ --- End Message --- --- Begin Message --- Source: alsa-lib Source-Version: 1.1.8-2 We believe that the bug you reported is fixed in the latest version of alsa-lib, 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 854...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jordi Mallach (supplier of updated alsa-lib package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 11 Oct 2019 12:44:01 +0200 Source: alsa-lib Architecture: source Version: 1.1.8-2 Distribution: unstable Urgency: medium Maintainer: Debian ALSA Maintainers Changed-By: Jordi Mallach Closes: 854213 940730 Changes: alsa-lib (1.1.8-2) unstable; urgency=medium . * Get rid of old, unused patches. * Backport necessary ucm changes to fix audio on Lenovo X1 Carbon Gen 7 using the whiskeylake processor (thanks, Héctor Orón; closes: #940730). * Use cross-compatible python3-dev Build-Depends to fix FTCBFS (thanks, Helmut Grohne; closes: #854213). Checksums-Sha1: 91c9b8876eeb900c35f60a4e7e25ca9aced6d96d 2492 alsa-lib_1.1.8-2.dsc 5390a6ce4870bd4d9d6db4030289cd5801d77af3 34004 alsa-lib_1.1.8-2.debian.tar.xz d565efb54ab844c867bb76e6621a15d015997618 6895 alsa-lib_1.1.8-2_source.buildinfo Checksums-Sha256: d5ff6c3c56e6e230f8dfb4152637c74d4423af25aa66a6778638b37d4e8ef110 2492 alsa-lib_1.1.8-2.dsc e8bade2e13f098f0a892d7b7a864007029c54bb03df3d70e35248513247b88d1 34004 alsa-lib_1.1.8-2.debian.tar.xz 8c2b0cfe7c4182706a9e13949007ea5d49fae574d4149e71573a2c77460c00dd 6895 alsa-lib_1.1.8-2_source.buildinfo Files: 952dbf9a1195b8dc0dc42b28f11c828f 2492 libs optional alsa-lib_1.1.8-2.dsc 597c5c956ae6c7157e20897d9e1895ed 34004 libs optional alsa-lib_1.1.8-2.debian.tar.xz 7fed99d902275377238a463ee63f25fe 6895 libs optional alsa-lib_1.1.8-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE6BdUhsApKYN8KGoWJVAvb8vjywQFAl2gXfMRHGpvcmRpQGRl Ymlhbi5vcmcACgkQJVAvb8vjywR8Fg/5AQ9bCEoszsGZsFgdZgGw7k0ezccKEF65
Bug#744868: marked as done (gpxviewer: GPXViewer is not showing OSM map tiles)
Your message dated Fri, 11 Oct 2019 12:15:05 +0200 with message-id <20191011101505.GA27218@vis> and subject line Re: Bug#744868: gpxviewer: GPXViewer is not showing OSM map tiles has caused the Debian Bug report #744868, regarding gpxviewer: GPXViewer is not showing OSM map tiles 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.) -- 744868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744868 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gpxviewer Version: 0.4.3-1 Severity: important Tags: upstream Dear Maintainer, GPXViewer has recently stopped showing OSM map tiles. According to https://bugs.launchpad.net/gpxviewer/+bug/1271593 this is because OSM have changed their tile URLs. An upstream fix has been uploaded to Github. If the package could be updated when this is convenient, it would be useful. Thanks. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gpxviewer depends on: ii librsvg2-common 2.40.2-1 ii python2.7.5-5 ii python-gnome2 2.28.1+dfsg-1 ii python-gtk2 2.24.0-3+b1 ii python-osmgpsmap 0.7.3-3 ii xdg-utils 1.1.0~rc1+git20111210-7 gpxviewer recommends no packages. gpxviewer suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Hi, a long time ago you opened this bug and I was not able to reproduce it with the current version in Debian. Can you please retry and reopen in case. Cheers Jochen * Tony Green [2014-04-15 17:00]: Package: gpxviewer Version: 0.4.3-1 Severity: important Tags: upstream Dear Maintainer, GPXViewer has recently stopped showing OSM map tiles. According to https://bugs.launchpad.net/gpxviewer/+bug/1271593 this is because OSM have changed their tile URLs. An upstream fix has been uploaded to Github. If the package could be updated when this is convenient, it would be useful. Thanks. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gpxviewer depends on: ii librsvg2-common 2.40.2-1 ii python2.7.5-5 ii python-gnome2 2.28.1+dfsg-1 ii python-gtk2 2.24.0-3+b1 ii python-osmgpsmap 0.7.3-3 ii xdg-utils 1.1.0~rc1+git20111210-7 gpxviewer recommends no packages. gpxviewer suggests no packages. -- no debconf information signature.asc Description: PGP signature --- End Message ---
Bug#930742: marked as done (parted: fix MacOS boot support)
Your message dated Fri, 11 Oct 2019 10:19:39 +
with message-id
and subject line Bug#930742: fixed in parted 3.3-1
has caused the Debian Bug report #930742,
regarding parted: fix MacOS boot support
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.)
--
930742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930742
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: parted
Severity: normal
Tags: patch
Dear Maintainer,
parted does not properly handle MacOS partitions. The attached (from upstream)
fixes this.
See
http://git.savannah.gnu.org/cgit/parted.git/commit/?id=43b061e90dcdab799ecd1e822852de110673bf7e
for more detail.
-- System Information:
Debian Release: 10.0
APT prefers unreleased
APT policy: (500, 'unreleased'), (500, 'unstable'), (1, 'experimental')
Architecture: ia64
Kernel: Linux 5.0.0-trunk-mckinley (SMP w/2 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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff --git a/libparted/labels/mac.c b/libparted/labels/mac.c
index d8da941..fa4e43f 100644
--- a/libparted/labels/mac.c
+++ b/libparted/labels/mac.c
@@ -411,14 +411,14 @@ _rawpart_has_driver (const MacRawPartition* raw_part,
MacDiskData* mac_disk_data
{
MacDeviceDriver *driverlist;
uint16_t i;
- uint32_t driver_bs, driver_be, part_be;
+ uint32_t start_block, block_count;
+ start_block = PED_BE32_TO_CPU(raw_part->start_block);
+ block_count = PED_BE32_TO_CPU(raw_part->block_count);
driverlist = _disk_data->driverlist[0];
for (i = 0; i < mac_disk_data->driver_count; i++) {
- driver_bs = driverlist->block;
- driver_be = driver_bs + driverlist->size;
- part_be = raw_part->start_block + raw_part->block_count;
- if (driver_bs >= raw_part->start_block && driver_be <= part_be)
+ if (start_block == PED_BE32_TO_CPU(driverlist->block) &&
+block_count == PED_BE16_TO_CPU(driverlist->size))
return 1;
driverlist++;
}
@@ -751,11 +751,12 @@ mac_read (PedDisk* disk)
if (!ped_disk_delete_all (disk))
goto error;
- if (raw_disk->driver_count && raw_disk->driver_count < 62) {
+ if (PED_BE16_TO_CPU(raw_disk->driver_count) &&
+PED_BE16_TO_CPU(raw_disk->driver_count) < 62) {
memcpy(_disk_data->driverlist[0], _disk->driverlist[0],
sizeof(mac_disk_data->driverlist));
- mac_disk_data->driver_count = raw_disk->driver_count;
- mac_disk_data->block_size = raw_disk->block_size;
+ mac_disk_data->driver_count =
PED_BE16_TO_CPU(raw_disk->driver_count);
+ mac_disk_data->block_size =
PED_BE16_TO_CPU(raw_disk->block_size);
}
/* If _disk_analyse_block_size has increased the sector_size,
@@ -877,17 +878,16 @@ static void
_update_driver_count (MacRawPartition* part_map_entry,
MacDiskData *mac_driverdata, const MacDiskData*
mac_disk_data)
{
- uint16_ti, count_orig, count_cur;
- uint32_tdriver_bs, driver_be, part_be;
-
- count_cur = mac_driverdata->driver_count;
- count_orig = mac_disk_data->driver_count;
- for (i = 0; i < count_orig; i++) {
- driver_bs = mac_disk_data->driverlist[i].block;
- driver_be = driver_bs + mac_disk_data->driverlist[i].size;
- part_be = part_map_entry->start_block +
part_map_entry->block_count;
- if (driver_bs >= part_map_entry->start_block
- && driver_be <= part_be) {
+ uint16_ti;
+ uint32_tstart_block, block_count;
+
+ start_block = PED_BE32_TO_CPU(part_map_entry->start_block);
+ block_count = PED_BE32_TO_CPU(part_map_entry->block_count);
+
+ for (i = 0; i < mac_disk_data->driver_count; i++) {
+ if (start_block ==
PED_BE32_TO_CPU(mac_disk_data->driverlist[i].block) &&
+ block_count ==
PED_BE16_TO_CPU(mac_disk_data->driverlist[i].size)) {
+ uint16_t count_cur = mac_driverdata->driver_count;
mac_driverdata->driverlist[count_cur].block
= mac_disk_data->driverlist[i].block;
mac_driverdata->driverlist[count_cur].size
@@ -934,7 +934,6 @@ _generate_raw_part (PedDisk*
Bug#880035: marked as done (parted: fails to use negative start value for 'mkpart' command without specyfying FS-TYPE)
Your message dated Fri, 11 Oct 2019 10:19:39 + with message-id and subject line Bug#880035: fixed in parted 3.3-1 has caused the Debian Bug report #880035, regarding parted: fails to use negative start value for 'mkpart' command without specyfying FS-TYPE 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.) -- 880035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880035 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: parted Version: 3.2-18 Severity: normal Dear Maintainer, * What led up to the situation? Trying to create partition via 'mkpart' with negative START value without specyfying optional FS-TYPE. * What exactly did you do (or not do) that was effective (or ineffective)? parted -a none -s -- /dev/vda mkpart flags_backup -4M -6177s or with interactive mode: (parted) mkpart flags_backup -4M -6177s * What was the outcome of this action? Partition is not created with failure message: parted: invalid token: -4M Error: Expecting a file system type. * What outcome did you expect instead? Partition is created. -- System Information: Debian Release: 9.1 Architecture: amd64 (x86_64) Kernel: Linux 4.9.57-std-def-alt1.1 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages parted depends on: ii libc6 2.24-11+deb9u1 ii libparted23.2-18 ii libreadline7 7.0-3 ii libtinfo5 6.0+20161126-1 parted recommends no packages. Versions of packages parted suggests: pn parted-doc -- no debconf information --- End Message --- --- Begin Message --- Source: parted Source-Version: 3.3-1 We believe that the bug you reported is fixed in the latest version of parted, 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 880...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Colin Watson (supplier of updated parted 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: Fri, 11 Oct 2019 10:59:03 +0100 Source: parted Architecture: source Version: 3.3-1 Distribution: unstable Urgency: medium Maintainer: Parted Maintainer Team Changed-By: Colin Watson Closes: 880035 896171 930742 942159 Changes: parted (3.3-1) unstable; urgency=medium . * New upstream release (closes: #942159): - mkpart: Allow negative start value when FS-TYPE is not given (closes: #880035). - Fix atari label false positives (closes: #896171). - libparted: Fix MacOS boot support (closes: #930742). * Add Brian C. Lane's GPG key to debian/upstream/signing-key.asc. Checksums-Sha1: 633608a9887d06e5d9c5334fe2be75dd508259ea 3145 parted_3.3-1.dsc e639500f9587cf6fa9b0dbc08e5e760244614595 1757432 parted_3.3.orig.tar.xz 4905eb9d7f60b1f0d6a1f0cbc2f4fdd8dfe91c1f 508 parted_3.3.orig.tar.xz.asc b995e4b333ca214dea5ad8ef1b9a302560732cd9 55916 parted_3.3-1.debian.tar.xz Checksums-Sha256: 0a69a7290795561eb465fdd6beaebaec52d1bec382347de6bd54cb23231e4b7f 3145 parted_3.3-1.dsc 57e2b4bd87018625c515421d4524f6e3b55175b472302056391c5f7eccb83d44 1757432 parted_3.3.orig.tar.xz 528d2d7b73b78aef96fb1b5f09a405387408459c856a0106ed0d13da50ae1f01 508 parted_3.3.orig.tar.xz.asc 78a8bcb02f9d005ca34a32bab2175bc5560d4f54fcb92dfd85fcc9bddff1c7a0 55916 parted_3.3-1.debian.tar.xz Files: e6e4d3a9259d0e467348e759e5ad05ce 3145 admin optional parted_3.3-1.dsc 090655d05f3c471aa8e15a27536889ec 1757432 admin optional parted_3.3.orig.tar.xz f9522da55ad1a4e361724f12ab5decc1 508 admin optional parted_3.3.orig.tar.xz.asc 8206ff8d14b07f52b3d78fb12c667bc1 55916 admin optional parted_3.3-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAl2gUtMACgkQOTWH2X2G UAtn4g/6A6dFykbrkmCn6SnhioIkfpvjPR5tzknMjbZVV23gePs3PJ/3HpU6xVJt bGK8diEscvp84vW2olHA5qEoJ3DB+5oqqr+SRoqhlsfAuLw78r6tVbGC7YDvCk8B H3k9b1/HDzw63v2RLLm2nHigz9ZoP+1pySJpV6tYWAw52KLXM6uLN9FLmn6OU3mh HPaTrf/YOhYzawB4sSO899ss+0hSoLAok04W+/LxiA1da6174yLZSZobCsyisa4Z 7lJp+w4ac0wqQzKJSPymMQ+hH/YlswrUkN+Z23BSHnmnW07kX1DO8I0MDfveWt4L
Bug#896171: marked as done (parted wrongly identifies an msdos partition table as 'atari')
Your message dated Fri, 11 Oct 2019 10:19:39 + with message-id and subject line Bug#896171: fixed in parted 3.3-1 has caused the Debian Bug report #896171, regarding parted wrongly identifies an msdos partition table as 'atari' 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.) -- 896171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896171 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: parted Version: 3.2-17 I have a valid & pretty standard Windows 10 system on a hard disk with three NTFS partitions: a small boot partition, a 465 GB main partition and a small restore partition. The structure is created by fsdisk from a Clonezilla live distribution. After the partitions are created, parted identifies my partition table as "atari" with a single partition. Any other tool I throw at it correctly sees an msdos partition table and I can boot windows 10 from the disk, so it appears there is nothing wrong with the disk. Also, it reproduces on 7 different PC's (albeit with pretty identical hardware). I don't have a complete Debian system so my options are limited (no inernet access / reportbug), but this is the test I ran to reproduce the problem: 1.Run parted; it says I have an atari disk (even though it is a functional Windows 10 system) 2.Instruct parted to create a new dos partition table 3.Run parted; it says I have an msdos disk with no partitions (as expected) 4.Run sfdisk with sda-pt.sf from the Clonezilla image as input 5.sfdisk creates three NTFS partitions on the disk (as expected) 6.Run parted; it says I have an atari disk with one partition See the full log at the end of this mail. My understanding of the problem is that the code that makes parted recognize atari disks in isolated cases falsely indentifies a disk as Atari if the first blocks incidentally contain data that make (some) sense when interpreted as an Atari partition table. The chance of this happening is not high but also not zero (and apparently I got unlucky). See the parted list (Bug #3 http://lists.gnu.org/archive/html/bug-parted/2018-04/msg3.html) for a more detailed analysis. The chance of this happening should be zero because If I would use parted to change anything on this disk it would probably destroy all data on it (i.e., pretty critical). FUN FACT: If I change the size of sda2 from 975028224 to (e.g.) 975028222, the disk is no longer recognized as Atari & the problem vanishes. Some info about my system: I used the Clonezilla-live distribution alternate stable (clonezilla-live-2.5.2-31-i686) uname -a Linux zesty 4.10.0-33-generic #37-Ubuntu SMP Fri Aug 11 10:53:59 UTC 2017 i686 i686 i686 GNU/Linux dpkg --status parted Package: parted Status: install ok installed Priority: optional Section: admin Installed-Size: 156 Maintainer: Ubuntu Developers Architecture: i386 Version: 3.2-17 Replaces: fsresize, parted1.6 Depends: libc6 (>= 2.11), libparted2 (= 3.2-17), libreadline7 (>= 6.0), libtinfo5 (>= 6) Suggests: parted-doc Conflicts: fsresize, parted1.6 Description: disk partition manipulator [snip] Original-Maintainer: Parted Maintainer Team Homepage: http://www.gnu.org/software/parted sfdisk from util-linux 2.29 dpkg --list util-linux Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--= ii util-linux 2.29-1ubuntu2.1 i386 miscellaneous system utilities NOTE: I ran the same test from the GParted live distribution (gparted-live-0.31.0-1-i686), with the same results. uname -a --> Linux Debian 4.15.0-1-686 #1 SMP Debian 4.15.4-1 (2018-02-18) i686 GNU/Linux /etc/debian_version: buster/sid dpkg -- status parted: version 3.2-20.drbl1 /// LOG OF TEST PROCEDURE OUTLINED ABOVE /// sudo parted /dev/sda print Model: ATA WDC WD5000AAKX-6 (scsi) Disk /dev/sda: 500GB Sector size (logical/physical): 512B/512B Partition Table: atari Disk Flags: Number Start End SizeType File system Flags 1 8323MB 14.8GB 6446MB primary boot sudo parted -s /dev/sda mklabel msdos sudo parted /dev/sda print Model: ATA WDC WD5000AAKX-6 (scsi) Disk /dev/sda: 500GB Sector size (logical/physical): 512B/512B Partition Table: msdos Disk Flags: Number Start End Size Type File system Flags sudo sfdisk --force /dev/sda label: dos
Bug#942159: marked as done (parted: new upstream version 3.3 (signing key has changed))
Your message dated Fri, 11 Oct 2019 10:19:39 + with message-id and subject line Bug#942159: fixed in parted 3.3-1 has caused the Debian Bug report #942159, regarding parted: new upstream version 3.3 (signing key has changed) 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.) -- 942159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942159 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: parted Severity: wishlist There is a new upstream version (3.3) but uscan fails because the new version is signed by a RedHat employee instead of an Ubuntu person: parted-3.2 $ uscan uscan: Newest version of parted on remote site is 3.3, local version is 3.2 uscan:=> Newer package available from http://ftp.gnu.org/gnu/parted/parted-3.3.tar.xz gpgv: Signature made Fri 11 Oct 2019 07:54:52 AWST gpgv:using RSA key B4C6B451E4FA8B4232CA191E117E8C168EFE3A7F gpgv:issuer "b...@redhat.com" gpgv: Can't check signature: No public key uscan die: OpenPGP signature did not verify. at /usr/share/perl5/Devscripts/Uscan/Output.pm line 58. parted-3.2 $ gpg --import debian/upstream/signing-key.asc gpg: key 0x015F4DD4A70FB705: 2 signatures not checked due to missing keys gpg: key 0x015F4DD4A70FB705: "Phillip Susi " not changed gpg: Total number processed: 1 gpg: unchanged: 1 -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: parted Source-Version: 3.3-1 We believe that the bug you reported is fixed in the latest version of parted, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 942...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Colin Watson (supplier of updated parted 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: Fri, 11 Oct 2019 10:59:03 +0100 Source: parted Architecture: source Version: 3.3-1 Distribution: unstable Urgency: medium Maintainer: Parted Maintainer Team Changed-By: Colin Watson Closes: 880035 896171 930742 942159 Changes: parted (3.3-1) unstable; urgency=medium . * New upstream release (closes: #942159): - mkpart: Allow negative start value when FS-TYPE is not given (closes: #880035). - Fix atari label false positives (closes: #896171). - libparted: Fix MacOS boot support (closes: #930742). * Add Brian C. Lane's GPG key to debian/upstream/signing-key.asc. Checksums-Sha1: 633608a9887d06e5d9c5334fe2be75dd508259ea 3145 parted_3.3-1.dsc e639500f9587cf6fa9b0dbc08e5e760244614595 1757432 parted_3.3.orig.tar.xz 4905eb9d7f60b1f0d6a1f0cbc2f4fdd8dfe91c1f 508 parted_3.3.orig.tar.xz.asc b995e4b333ca214dea5ad8ef1b9a302560732cd9 55916 parted_3.3-1.debian.tar.xz Checksums-Sha256: 0a69a7290795561eb465fdd6beaebaec52d1bec382347de6bd54cb23231e4b7f 3145 parted_3.3-1.dsc 57e2b4bd87018625c515421d4524f6e3b55175b472302056391c5f7eccb83d44 1757432 parted_3.3.orig.tar.xz 528d2d7b73b78aef96fb1b5f09a405387408459c856a0106ed0d13da50ae1f01 508 parted_3.3.orig.tar.xz.asc 78a8bcb02f9d005ca34a32bab2175bc5560d4f54fcb92dfd85fcc9bddff1c7a0 55916 parted_3.3-1.debian.tar.xz Files: e6e4d3a9259d0e467348e759e5ad05ce 3145 admin optional parted_3.3-1.dsc 090655d05f3c471aa8e15a27536889ec 1757432 admin optional parted_3.3.orig.tar.xz f9522da55ad1a4e361724f12ab5decc1 508 admin optional parted_3.3.orig.tar.xz.asc 8206ff8d14b07f52b3d78fb12c667bc1 55916 admin optional parted_3.3-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAl2gUtMACgkQOTWH2X2G UAtn4g/6A6dFykbrkmCn6SnhioIkfpvjPR5tzknMjbZVV23gePs3PJ/3HpU6xVJt bGK8diEscvp84vW2olHA5qEoJ3DB+5oqqr+SRoqhlsfAuLw78r6tVbGC7YDvCk8B H3k9b1/HDzw63v2RLLm2nHigz9ZoP+1pySJpV6tYWAw52KLXM6uLN9FLmn6OU3mh HPaTrf/YOhYzawB4sSO899ss+0hSoLAok04W+/LxiA1da6174yLZSZobCsyisa4Z 7lJp+w4ac0wqQzKJSPymMQ+hH/YlswrUkN+Z23BSHnmnW07kX1DO8I0MDfveWt4L pDdXECqFVw0brnWem7zflrZjN8JR3oHMFwsw9sQjVw15Qsg4jb94FidRG2xNEs7G RksMhOb8j7X+tdXyk8CD31hBwWCW2dzO9FnAKTbJ4PExbfYcSKs2jLaBtIzwO/XL yztRaHWQKADdKXaar5XjZUYBuHcDWxpmsRdg2elWlIsfACw3EdtGzJX2zCzuIPSE
Bug#779370: marked as done (Refactor pm-utils and apmd specific functions)
Your message dated Fri, 11 Oct 2019 11:28:18 +0200
with message-id
and subject line Re: hdparm + systemd: old apm/pm-utils hooks not
working/migrated
has caused the Debian Bug report #779370,
regarding Refactor pm-utils and apmd specific functions
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.)
--
779370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779370
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: hdparm
Severity: serious
The apm/pm-utils suspend/resume functionalities, provided by shipping the
files 20hdparm and 95hdparm-apm scripts, do not work with systemd.
(missing systemd unit files)
To allow setting defaults I would suggest to support wildcards in hdparm.conf.
And ship with visible defaults like this:
# avoid excessive hard disk load-cycling
ata-* {
apm = 254
}
Maybe apm_on_battery and apm_on_ac settings?
And have those defaults switched on state changes.
--- End Message ---
--- Begin Message ---
Version: 9.58+ds-4
20hdparm is dropped in hdparm 9.58+ds-3 and suspend/resume scripts are
updated.
Wildcards are not supported, but hdparm(9.58+ds-4) follows the logic below:
No config (/etc/hdparm.conf doesn't list any drives):
* If disk supports APM, the defaults:
- on boot, -B 254
- on power, -B 254
- on battery -B 128 -S36 (3 min)
* no APM support:
- hdparm will not run (no config!)
If disk config is present in /etc/hdparm.conf:
* disk supports APM
- on boot, udev will call /lib/udev/hdparm, which in turn will call
/usr/lib/pm-utils/power.d/95hdparm-apm for apm options and hdparm
for other options.
- on power, /usr/lib/pm-utils/power.d/95hdparm-apm
- on battery, defaults -B 128 -S 36, use apm_battery and
spindown_time to set non-default values
* no APM support:
- force_spindown_time and other options are applied,
apm and spindown_time are ignored
For USB or FireWere disks, APM & spindown_time options are ignored,
other options are applied, force_spindown_time will be applied too.
There is bug, https://bugs.launchpad.net/bugs/515023
explaining why USB and FireWire drives are ignored, however the
situation might have improved since then.--- End Message ---
Processed: closing 942118
Processing commands for cont...@bugs.debian.org: > close 942118 Bug #942118 [smartmontools] SysV: fails to restart during upgrade, breaks dpkg Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 942118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942118 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#885479: marked as done (: Depends on unmaintained pygtk)
Your message dated Fri, 11 Oct 2019 09:04:55 + with message-id and subject line Bug#885479: fixed in simple-image-reducer 1.0.2+git20191008-1 has caused the Debian Bug report #885479, regarding : Depends on unmaintained pygtk 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.) -- 885479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885479 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: simple-image-reducer Version: 1.0.2-6 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject Introspection bindings (and gtk3). For more information on GObject Introspection see [1] and [2]. Please try to do this before the Buster release as we're going to try to remove pygtk this cycle. If you have any question don't hesitate to ask. [1] https://wiki.gnome.org/Projects/GObjectIntrospection [2] https://wiki.gnome.org/Projects/PyGObject On behalf of the Debian GNOME team, Jeremy Bicha --- End Message --- --- Begin Message --- Source: simple-image-reducer Source-Version: 1.0.2+git20191008-1 We believe that the bug you reported is fixed in the latest version of simple-image-reducer, 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 885...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. TANIGUCHI Takaki (supplier of updated simple-image-reducer 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: Fri, 11 Oct 2019 17:30:50 +0900 Source: simple-image-reducer Architecture: source Version: 1.0.2+git20191008-1 Distribution: unstable Urgency: medium Maintainer: Python Applications Packaging Team Changed-By: TANIGUCHI Takaki Closes: 885479 Changes: simple-image-reducer (1.0.2+git20191008-1) unstable; urgency=medium . [ Ondřej Nový ] * d/copyright: Use https protocol in Format field * d/changelog: Remove trailing whitespaces . [ TANIGUCHI Takaki ] * Bump debhelper from old 11 to 12. * Set upstream metadata fields: Repository. * Bump Standards-Version to 4.4.1 * d/rules: with python3 * New upstream version 1.0.2+git20191008 - Migrate to python3 and gio. (Closes: #885479) * d/patches: Drop * d/control: Change Maintainer to PAPT * d/salsa-ci.yml: Add Checksums-Sha1: b3837c1156c41d795e5c7a5983e9281c396461a2 2239 simple-image-reducer_1.0.2+git20191008-1.dsc 3e17644e00b15833df15a3a29b946f5112610109 23811 simple-image-reducer_1.0.2+git20191008.orig.tar.gz 051fb2c598a57d01dbb7cc0c687788e94d54526e 2404 simple-image-reducer_1.0.2+git20191008-1.debian.tar.xz 07ce927c2213bf559a7ecdbd73b7011fc36d4488 7581 simple-image-reducer_1.0.2+git20191008-1_source.buildinfo Checksums-Sha256: d8f648653f6d8e9a097be8f772829d25797ed9bac29cbf00ad57f60b708184a4 2239 simple-image-reducer_1.0.2+git20191008-1.dsc 333b179af33c9b9d33974b8a8145188a3719d6030a6e00d413491185b66f0659 23811 simple-image-reducer_1.0.2+git20191008.orig.tar.gz b74fdb4d805c05bf1f8252c6f99d1fd22bbe56cd23cf81d6e7fcfa74cecb152e 2404 simple-image-reducer_1.0.2+git20191008-1.debian.tar.xz 41d5996bb4c969abc0c72411f05b00328ee072a3eb44b773509625c92645c653 7581 simple-image-reducer_1.0.2+git20191008-1_source.buildinfo Files: edd5402d2bd2a774de7fcbdcd51115b3 2239 graphics optional simple-image-reducer_1.0.2+git20191008-1.dsc bf7b7324b56d631e060151a1048ae7f4 23811 graphics optional simple-image-reducer_1.0.2+git20191008.orig.tar.gz 28beb1b0b80a434cd913eac1940d86ed 2404 graphics optional simple-image-reducer_1.0.2+git20191008-1.debian.tar.xz e689682b238527ca3c818c334ff8ab10 7581 graphics optional simple-image-reducer_1.0.2+git20191008-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCAAwFiEE0kq/0SfNJVahPGx5zBSfbCil4lcFAl2gQY4SHHRha2FraUBk ZWJpYW4ub3JnAAoJEMwUn2wopeJXjz0QAJNGSY2g9Bxr4zRw6lxCUJ/jv6PQMjDJ xHeEttkjQI6BNr3a537lYOI9tg558frhc+8dowiMhpdH45FYpptzqEDhwq9ml+zj I7FGI60AiLco1i40gdYGnV8eyenYgU59DsuZKL9pbLrwf3glqvhkrbG3IvRnJdmX qPNDWK4wnttnKXsc263Pq34crgqjSHme6utjr/dCxOzJfZceWX2wURZAP6kUZgPJ
Bug#941949: marked as done (mark geoip-database Multi-Arch: foreign)
Your message dated Fri, 11 Oct 2019 09:04:04 +
with message-id
and subject line Bug#941949: fixed in geoip-database 20191011-1
has caused the Debian Bug report #941949,
regarding mark geoip-database Multi-Arch: foreign
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.)
--
941949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941949
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: geoip-database
Version: 20190920-1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: cross-satisfiability
Control: affects -1 + src:ipv6calc src:libgeo-ip-perl src:lua-geoip
src:syslog-ng
The affected packages fail to satisfy their cross Build-Depends, because
their dependency on geoip-database is unsatisfiable. In general,
Architecture: all packages can never satisfy cross build dependencies
unless marked Multi-Arch: foreign or annotated :native. In this case,
the foreign marking is reasonable, because geoip-database provides an
architecture-independent database and doesn't have any dependencies nor
maintainer scripts. Please consider applying the attached patch.
Helmut
diff --minimal -Nru geoip-database-20190920/debian/changelog
geoip-database-20190920/debian/changelog
--- geoip-database-20190920/debian/changelog2019-09-20 09:45:02.0
+0200
+++ geoip-database-20190920/debian/changelog2019-10-07 22:52:28.0
+0200
@@ -1,3 +1,10 @@
+geoip-database (20190920-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Mark geoip-database Multi-Arch: foreign. (Closes: #-1)
+
+ -- Helmut Grohne Mon, 07 Oct 2019 22:52:28 +0200
+
geoip-database (20190920-1) unstable; urgency=high
* New upstream release.
diff --minimal -Nru geoip-database-20190920/debian/control
geoip-database-20190920/debian/control
--- geoip-database-20190920/debian/control 2019-09-20 09:45:02.0
+0200
+++ geoip-database-20190920/debian/control 2019-10-07 22:37:32.0
+0200
@@ -10,6 +10,7 @@
Package: geoip-database
Architecture: all
+Multi-Arch: foreign
Depends: ${misc:Depends}
Recommends: libgeoip1
Description: IP lookup command line tools that use the GeoIP library (country
database)
--- End Message ---
--- Begin Message ---
Source: geoip-database
Source-Version: 20191011-1
We believe that the bug you reported is fixed in the latest version of
geoip-database, 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 941...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Patrick Matthäi (supplier of updated geoip-database
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: Fri, 11 Oct 2019 10:23:14 +0200
Source: geoip-database
Architecture: source
Version: 20191011-1
Distribution: unstable
Urgency: medium
Maintainer: Patrick Matthäi
Changed-By: Patrick Matthäi
Closes: 941949
Changes:
geoip-database (20191011-1) unstable; urgency=medium
.
* New upstream release.
* Bump Standards-Version to 4.4.1.
* Set Rules-Requires-Root to no.
* Mark geoip-database as Multi-Arch: foreign.
Closes: #941949
Checksums-Sha1:
a01019f2fb81f570a14f4b8b9f81104790e0ee2d 1835 geoip-database_20191011-1.dsc
5531defc7aa0d48207fc08dfff93f0ee2112710a 1230260
geoip-database_20191011.orig.tar.xz
f9084501577fc5e002f98cef06f0542621897d95 4764
geoip-database_20191011-1.debian.tar.xz
d1a2c2d01833314247cddd925001d391513d2c55 5682
geoip-database_20191011-1_source.buildinfo
Checksums-Sha256:
d187355071810ced815c48946496f7c50028157df59c8bc5be8a9e1b84b3d43e 1835
geoip-database_20191011-1.dsc
eea19fee1f90c31b26d4d47f4dfafa96aa8b0f60f2eb0b5c61fbcc44ebc9732e 1230260
geoip-database_20191011.orig.tar.xz
90a78e71b76d5f73dfbe131bfd39011f87f3da87fb2d4299b7f525336b96 4764
geoip-database_20191011-1.debian.tar.xz
2b114fac42b8ba6fc2b237fb485581399babeda0fd7cf442f5b47e2e9e0dcd35 5682
geoip-database_20191011-1_source.buildinfo
Files:
19fb9b75ff9918344244f551c802ae5e 1835 net optional
geoip-database_20191011-1.dsc
159479da91021d8ecfc03424733f90ba 1230260 net optional
geoip-database_20191011.orig.tar.xz
8f39df96189888cef7ada99ef4e12472 4764 net optional
geoip-database_20191011-1
Bug#939105: marked as done (gpxviewer: Python2 removal in sid/bullseye -- drop python-distutils-extra build dependency)
Your message dated Fri, 11 Oct 2019 09:04:11 + with message-id and subject line Bug#939105: fixed in gpxviewer 1.0.0-1 has caused the Debian Bug report #939105, regarding gpxviewer: Python2 removal in sid/bullseye -- drop python-distutils-extra build dependency 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.) -- 939105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939105 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gpxviewer Version: 0.5.2-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package build-depends on python-distutils-extra. Please convert the package to Python 3, using python3-distutils-extra. Thanks, Martin --- End Message --- --- Begin Message --- Source: gpxviewer Source-Version: 1.0.0-1 We believe that the bug you reported is fixed in the latest version of gpxviewer, 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 939...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jochen Sprickerhof (supplier of updated gpxviewer package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 11 Oct 2019 10:26:00 +0200 Source: gpxviewer Architecture: source Version: 1.0.0-1 Distribution: unstable Urgency: medium Maintainer: Python Applications Packaging Team Changed-By: Jochen Sprickerhof Closes: 936646 939105 941875 Changes: gpxviewer (1.0.0-1) unstable; urgency=medium . * New upstream version 1.0.0 * rewrite d/copyright * Switch maintainer to PAPT and add myself as uploader * switch to debhelper-compat and debhelper 12 * Bump policy version (no changes) * add Salsa CI * Add R³ * Drop python-gtk2 (Closes: #941875) * Switch d/s/format to 3.0 * Switch to Python 3 (Closes: #936646, #939105) Checksums-Sha1: a62bf946e0ab7e03474d3eefdf419f2043c2463b 2062 gpxviewer_1.0.0-1.dsc 740421c598e728588452830f301d9a21efece06b 60186 gpxviewer_1.0.0.orig.tar.gz 198d37478cfefe5d2916f6aa04662edd8b116a61 2916 gpxviewer_1.0.0-1.debian.tar.xz 73ae565fac2ba9e6846ef8bdd29c1b13e95af02c 6946 gpxviewer_1.0.0-1_source.buildinfo Checksums-Sha256: 372238784e0e920e8a34e19ad5f659929be74d2d808ca4429d964c7293915628 2062 gpxviewer_1.0.0-1.dsc 2541e657a3c17d7165a25cd51ea00ed873a1a0afcb42bf07cdc4cf79e25a98b8 60186 gpxviewer_1.0.0.orig.tar.gz aaed7a5121edea166657de2e328ad459daef2a8ac0edc33bdeeb66967ad21c37 2916 gpxviewer_1.0.0-1.debian.tar.xz 1c6a73a9fa49f460a787e1f1740c1eda72e069001adaa010b9acd5a1d1cf4d44 6946 gpxviewer_1.0.0-1_source.buildinfo Files: e93358c1d7e8fa467814a282ffeba9a8 2062 misc optional gpxviewer_1.0.0-1.dsc d39ced3b763b55ad3dd980a0e1a5d582 60186 misc optional gpxviewer_1.0.0.orig.tar.gz 0f17f8704f56fad0c6f6598dbd9b24c6 2916 misc optional gpxviewer_1.0.0-1.debian.tar.xz a2b468fa92249f36aa84ad546d281198 6946 misc optional gpxviewer_1.0.0-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAl2gQhQACgkQW//cwljm lDP0WQ/8DaReGfzGOlTfbSDdSnPfuraTstF+P6nk7rQ00G32LWcEOShhhn6bcnPv FW+mUW53fbeKbQ1Ao6/GOIrifzO5NpOSUVCzxaTRRgexzN5nUzzDkf5NiB+P2N4y cixQ2Y3hhd9JHh+uQmMErkQ+014ygL0EG8XKNMH+ndZwFrFZJm5BJwnQRoZax0J7 pzUbbOOjGkI520YjQnJh7UCJFoR+skdqnW9cOlVL1Dc3+5RdUtXvODD3Y4+dhQa6 EiYll9wcQzeHuhGSTaKvHQUyqehczK4P+U4/Zj1NnJo3F1mY0l1HlH5QIal7tL+7 /mdm/xaIFXhkxFU4xy8jKsV1VgPUuuQCt0ItJmKX4Lf7CSw064MgolY1qUrAKbWh v++EsWITURQYyJmtkJIp06/aPcA/CGMbXBeswxOBjKdYVrYoa9ej/+bTtm+jPdSR 4UU4uZy7nIYR4jIrS73gz4NgJHP6XSZq/MiGNu0xN/Bjvd2uXMbt6uSB1n5tI/KW bxRmFddNPTwZ8H03vPQgb981+NlvG3CA0g5qqZk6YLHWJ8e8+ISWEMOPWxVDYqHG tFOvOn7T6rKUGMTZDOJNDmjK/uV7uO7nhKPHojAIED6lW/IsIs1Rbi2fYtiQ7cGV 8mh0mUfT9DFuJ+BE/5pKIS1xLMS/B1zp56m6oMbs4+PWkMZtsfg= =Bczb -END PGP SIGNATURE End Message ---
Bug#941875: marked as done (gpxviewer: Please remove unused dependency on python-gtk2)
Your message dated Fri, 11 Oct 2019 09:04:11 + with message-id and subject line Bug#941875: fixed in gpxviewer 1.0.0-1 has caused the Debian Bug report #941875, regarding gpxviewer: Please remove unused dependency on python-gtk2 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.) -- 941875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941875 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gpxviewer Version: 0.5.2-2 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid bullseye patch The Debian GNOME team is working to remove pygtk from Debian. pygtk is a set of Python 2 bindings for GTK2. It looks like gpxviewer has already been reported to GObject Introspection and GTK3. All you have left to do for the pygtk removal is to remove python-gtk2 from gpxviewer's Depends. (I'm not actually attaching a patch here but this seems like an easy fix.) Thanks, Jeremy Bicha --- End Message --- --- Begin Message --- Source: gpxviewer Source-Version: 1.0.0-1 We believe that the bug you reported is fixed in the latest version of gpxviewer, 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 941...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jochen Sprickerhof (supplier of updated gpxviewer package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 11 Oct 2019 10:26:00 +0200 Source: gpxviewer Architecture: source Version: 1.0.0-1 Distribution: unstable Urgency: medium Maintainer: Python Applications Packaging Team Changed-By: Jochen Sprickerhof Closes: 936646 939105 941875 Changes: gpxviewer (1.0.0-1) unstable; urgency=medium . * New upstream version 1.0.0 * rewrite d/copyright * Switch maintainer to PAPT and add myself as uploader * switch to debhelper-compat and debhelper 12 * Bump policy version (no changes) * add Salsa CI * Add R³ * Drop python-gtk2 (Closes: #941875) * Switch d/s/format to 3.0 * Switch to Python 3 (Closes: #936646, #939105) Checksums-Sha1: a62bf946e0ab7e03474d3eefdf419f2043c2463b 2062 gpxviewer_1.0.0-1.dsc 740421c598e728588452830f301d9a21efece06b 60186 gpxviewer_1.0.0.orig.tar.gz 198d37478cfefe5d2916f6aa04662edd8b116a61 2916 gpxviewer_1.0.0-1.debian.tar.xz 73ae565fac2ba9e6846ef8bdd29c1b13e95af02c 6946 gpxviewer_1.0.0-1_source.buildinfo Checksums-Sha256: 372238784e0e920e8a34e19ad5f659929be74d2d808ca4429d964c7293915628 2062 gpxviewer_1.0.0-1.dsc 2541e657a3c17d7165a25cd51ea00ed873a1a0afcb42bf07cdc4cf79e25a98b8 60186 gpxviewer_1.0.0.orig.tar.gz aaed7a5121edea166657de2e328ad459daef2a8ac0edc33bdeeb66967ad21c37 2916 gpxviewer_1.0.0-1.debian.tar.xz 1c6a73a9fa49f460a787e1f1740c1eda72e069001adaa010b9acd5a1d1cf4d44 6946 gpxviewer_1.0.0-1_source.buildinfo Files: e93358c1d7e8fa467814a282ffeba9a8 2062 misc optional gpxviewer_1.0.0-1.dsc d39ced3b763b55ad3dd980a0e1a5d582 60186 misc optional gpxviewer_1.0.0.orig.tar.gz 0f17f8704f56fad0c6f6598dbd9b24c6 2916 misc optional gpxviewer_1.0.0-1.debian.tar.xz a2b468fa92249f36aa84ad546d281198 6946 misc optional gpxviewer_1.0.0-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAl2gQhQACgkQW//cwljm lDP0WQ/8DaReGfzGOlTfbSDdSnPfuraTstF+P6nk7rQ00G32LWcEOShhhn6bcnPv FW+mUW53fbeKbQ1Ao6/GOIrifzO5NpOSUVCzxaTRRgexzN5nUzzDkf5NiB+P2N4y cixQ2Y3hhd9JHh+uQmMErkQ+014ygL0EG8XKNMH+ndZwFrFZJm5BJwnQRoZax0J7 pzUbbOOjGkI520YjQnJh7UCJFoR+skdqnW9cOlVL1Dc3+5RdUtXvODD3Y4+dhQa6 EiYll9wcQzeHuhGSTaKvHQUyqehczK4P+U4/Zj1NnJo3F1mY0l1HlH5QIal7tL+7 /mdm/xaIFXhkxFU4xy8jKsV1VgPUuuQCt0ItJmKX4Lf7CSw064MgolY1qUrAKbWh v++EsWITURQYyJmtkJIp06/aPcA/CGMbXBeswxOBjKdYVrYoa9ej/+bTtm+jPdSR 4UU4uZy7nIYR4jIrS73gz4NgJHP6XSZq/MiGNu0xN/Bjvd2uXMbt6uSB1n5tI/KW bxRmFddNPTwZ8H03vPQgb981+NlvG3CA0g5qqZk6YLHWJ8e8+ISWEMOPWxVDYqHG tFOvOn7T6rKUGMTZDOJNDmjK/uV7uO7nhKPHojAIED6lW/IsIs1Rbi2fYtiQ7cGV 8mh0mUfT9DFuJ+BE/5pKIS1xLMS/B1zp56m6oMbs4+PWkMZtsfg= =Bczb -END PGP SIGNATURE End Message ---
Bug#936646: marked as done (gpxviewer: Python2 removal in sid/bullseye)
Your message dated Fri, 11 Oct 2019 09:04:11 + with message-id and subject line Bug#936646: fixed in gpxviewer 1.0.0-1 has caused the Debian Bug report #936646, regarding gpxviewer: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 936646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936646 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gpxviewer Version: 0.5.2-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:gpxviewer If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: gpxviewer Source-Version: 1.0.0-1 We believe that the bug you reported is fixed in the latest version of gpxviewer, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 936...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jochen Sprickerhof (supplier of updated gpxviewer package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 11 Oct 2019 10:26:00 +0200 Source: gpxviewer Architecture: source Version: 1.0.0-1 Distribution: unstable Urgency: medium Maintainer: Python Applications Packaging Team Changed-By: Jochen Sprickerhof Closes: 936646 939105 941875 Changes: gpxviewer (1.0.0-1) unstable; urgency=medium . * New upstream version 1.0.0 * rewrite d/copyright * Switch maintainer to PAPT and add myself as uploader * switch to debhelper-compat and debhelper 12 * Bump policy version (no changes) * add Salsa CI * Add R³ * Drop python-gtk2 (Closes: #941875) * Switch d/s/format to 3.0 * Switch to Python 3 (Closes: #936646, #939105) Checksums-Sha1: a62bf946e0ab7e03474d3eefdf419f2043c2463b 2062 gpxviewer_1.0.0-1.dsc 740421c598e728588452830f301d9a21efece06b 60186 gpxviewer_1.0.0.orig.tar.gz 198d37478cfefe5d2916f6aa04662edd8b116a61 2916 gpxviewer_1.0.0-1.debian.tar.xz 73ae565fac2ba9e6846ef8bdd29c1b13e95af02c 6946
Bug#941528: marked as done (goldencheetah: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended)
Your message dated Fri, 11 Oct 2019 08:49:42 + with message-id and subject line Bug#941528: fixed in goldencheetah 1:3.5~DEV1903-1 has caused the Debian Bug report #941528, regarding goldencheetah: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended 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.) -- 941528: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941528 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: goldencheetah Version: 1:3.5~DEV1810-1 Severity: serious Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu eoan ubuntu-patch Dear maintainers, The texlive-generic-recommended transitional package has been dropped from texlive-base in sid. Please update your build-dependency to texlive-plain-generic instead. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org diff -Nru goldencheetah-3.5~DEV1810/debian/control goldencheetah-3.5~DEV1810/debian/control --- goldencheetah-3.5~DEV1810/debian/control2019-01-04 20:30:31.0 -0800 +++ goldencheetah-3.5~DEV1810/debian/control2019-10-01 13:29:31.0 -0700 @@ -34,7 +34,7 @@ , texlive , texlive-latex-base , texlive-fonts-recommended - , texlive-generic-recommended + , texlive-plain-generic Standards-Version: 4.3.0 Vcs-Git: https://salsa.debian.org/debian/goldencheetah.git Vcs-Browser: https://salsa.debian.org/debian/goldencheetah --- End Message --- --- Begin Message --- Source: goldencheetah Source-Version: 1:3.5~DEV1903-1 We believe that the bug you reported is fixed in the latest version of goldencheetah, 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 941...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. KURASHIKI Satoru (supplier of updated goldencheetah package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 03 Oct 2019 17:35:32 +0900 Source: goldencheetah Architecture: source Version: 1:3.5~DEV1903-1 Distribution: unstable Urgency: medium Maintainer: KURASHIKI Satoru Changed-By: KURASHIKI Satoru Closes: 941528 Changes: goldencheetah (1:3.5~DEV1903-1) unstable; urgency=medium . * New upstream dev release. * New Standards-Version: 4.4.1 * Update build-dep: texlive-plain-generic. (Closes: #941528) * Fix d/watch opts. Checksums-Sha1: dd8fda5c0b9dc67af50eab6617c5baa7e6582d7e 2529 goldencheetah_3.5~DEV1903-1.dsc 2d05aac4c3e6ec09913c7227fab8abbba9220d0e 78682677 goldencheetah_3.5~DEV1903.orig.tar.gz 7f3bf68acd88440bab2d71d4e15b3f5827e5a9a0 75980 goldencheetah_3.5~DEV1903-1.debian.tar.xz a28cdf242eb45c98c35167b19f2c4e1cca9b142c 16043 goldencheetah_3.5~DEV1903-1_amd64.buildinfo Checksums-Sha256: 8f1e74ed050bdccea919f31a804ad24cb76d03627ec729367ff280a71403dff5 2529 goldencheetah_3.5~DEV1903-1.dsc 62d1f8715c9e237300ae06010f83368acbf2ea02e15fe5234c954c037dc18280 78682677 goldencheetah_3.5~DEV1903.orig.tar.gz f7ba0c45b7b873a5df44fe0cf911be3e12c74a5c7be92026a141bbdc947c7cc5 75980 goldencheetah_3.5~DEV1903-1.debian.tar.xz 3fb86261b02095033a1ba9c6898c798c910f9c54a2bd420f47d053b52eab7c43 16043 goldencheetah_3.5~DEV1903-1_amd64.buildinfo Files: c56b409cfcebe9624e1a435f57cec153 2529 misc optional goldencheetah_3.5~DEV1903-1.dsc 160e54ab47a06d98123f917da2adb7eb 78682677 misc optional goldencheetah_3.5~DEV1903.orig.tar.gz 718290044a45754f2c5c4b93b0a7e01a 75980 misc optional goldencheetah_3.5~DEV1903-1.debian.tar.xz 4736ad75f0d31c42ef91663e1e974245 16043 misc optional goldencheetah_3.5~DEV1903-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEwRyljAF1wkDVjDDI0n3eEUCi8RMFAl2f2kEACgkQ0n3eEUCi 8RNE/A//X8k40L+pIju5Fl0UJysT/biEMzY/ZWq7sw8+/07s3bnCyLgJFE/VWeP9 BDDSyQy/S623F4hJOP9wJ7YvBMxH35ixrC8BNJNvxWiTH3RI876o1ulosjPZawXb 14qpBi+yK4qQJ9apCtMeTs2ICXmDbmmG5auyBqp0ZN/CW96D2UghDA52LWpmStIT YpqWdfHHfSVKvjlyWOjWvVz/yVAFVE4IRd5ddSryyjiO4lDZIL9iQtPQcLGD+CA6
Bug#941889: marked as done (kde-spectacle: Segfaults while saving rectangular selection screenshot)
Your message dated Fri, 11 Oct 2019 10:11:15 +0200 with message-id <4990822.hrY1skZtEN@libor-nb> and subject line Re: kde-spectacle: Segfaults while saving rectangular selection screenshot has caused the Debian Bug report #941889, regarding kde-spectacle: Segfaults while saving rectangular selection screenshot 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.) -- 941889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941889 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kde-spectacle Version: 19.08.1-1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Maintainer, since upgrading from previous version, i cannot do rectangular snapshots with spectacle. Snapshot is taken, but spectacle crashes when i click "save" or "copy to clipboard" buttons. Snapshoting whole window/whole screen is ok, no crash. This is crash report, is it useful? Thanks, Libor Application: Spectacle (spectacle), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f30755df800 (LWP 14982))] Thread 4 (Thread 0x7f306bfff700 (LWP 14985)): #0 0x7f30788a0db5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f3070a1cffb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #2 0x7f3070a1cc17 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #3 0x7f307889afb7 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x7f3079ab22ef in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 3 (Thread 0x7f307305e700 (LWP 14984)): #0 0x7f3079aa38bc in read () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f3077cffcbf in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f3077cb8bfe in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3077cb9052 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f3077cb91cf in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f307a00e3e3 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f3079fbbcfb in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f3079e0bd8e in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f307a7ee545 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7f3079e15a07 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f307889afb7 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #11 0x7f3079ab22ef in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 2 (Thread 0x7f307479b700 (LWP 14983)): #0 0x7f3079aa7d2f in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f307b50acf7 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f307b50c91a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f3074f04d79 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f3079e15a07 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f307889afb7 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #6 0x7f3079ab22ef in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 1 (Thread 0x7f30755df800 (LWP 14982)): [KCrash Handler] #6 0x7f3079a3e926 in malloc () from /lib/x86_64-linux-gnu/libc.so.6 #7 0x7f3079e164b2 in QArrayData::allocate(unsigned long, unsigned long, unsigned long, QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f3079e18465 in QByteArray::reallocData(unsigned int, QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f307a8a6850 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ConfigCore.so.5 #10 0x7f307a8a70ea in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ConfigCore.so.5 #11 0x7f307a8a73f7 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ConfigCore.so.5 #12 0x7f307a8aabb0 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ConfigCore.so.5 #13 0x7f307a88fc5c in KConfig::sync() () from /usr/lib/x86_64-linux-gnu/libKF5ConfigCore.so.5 #14 0x5639904cf3d9 in ?? () #15 0x7f307ab3eefe in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f307ab00501 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7f307ab079b0 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7f3079fbd029 in
Processed: O: c-icap-modules -- C-ICAP modules
Processing commands for cont...@bugs.debian.org: > close 942163 Bug #942163 [wnpp] O: c-icap-modules -- C-ICAP modules Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 942163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942163 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#938292: marked as done (py-ubjson: Python2 removal in sid/bullseye)
Your message dated Fri, 11 Oct 2019 07:49:31 + with message-id and subject line Bug#938292: fixed in py-ubjson 0.14.0-2 has caused the Debian Bug report #938292, regarding py-ubjson: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 938292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938292 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:py-ubjson Version: 0.14.0-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:py-ubjson If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: py-ubjson Source-Version: 0.14.0-2 We believe that the bug you reported is fixed in the latest version of py-ubjson, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ondřej Nový (supplier of updated py-ubjson package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 11 Oct 2019 09:35:20 +0200 Source: py-ubjson Architecture: source Version: 0.14.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Ondřej Nový Closes: 938292 Changes: py-ubjson (0.14.0-2) unstable; urgency=medium . * Team upload. * Drop Python 2 support (Closes: #938292). Checksums-Sha1: 4629f0e0335068d3d863ae178ef8cba3da736d63 2113 py-ubjson_0.14.0-2.dsc 4eb40a4af69599ae6a6bd1faca874be0e838fb88 4864 py-ubjson_0.14.0-2.debian.tar.xz 3cc0091f9a0cd6235cd207cf045cebc801dbaa47 6657 py-ubjson_0.14.0-2_amd64.buildinfo Checksums-Sha256: 60edb16b79c7c25c2b68b633b684a90d4c111ce0042a40349a184d2553bc16c9 2113 py-ubjson_0.14.0-2.dsc 4d79970ea421376508388c5be28b07d03417506f0d53087b7e2f0fa65bd8f685 4864 py-ubjson_0.14.0-2.debian.tar.xz db9b0ef6bfdda656f728b0492fe6473a15d71eb604c83862506a2df238e469bb 6657 py-ubjson_0.14.0-2_amd64.buildinfo Files: 1d030e07493e28cf9dde7740d81e0045 2113 python optional
Bug#938228: marked as done (python-trie: Python2 removal in sid/bullseye)
Your message dated Fri, 11 Oct 2019 07:49:38 + with message-id and subject line Bug#938228: fixed in python-trie 0.2+ds-2 has caused the Debian Bug report #938228, regarding python-trie: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 938228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938228 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-trie Version: 0.2+ds-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-trie If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: python-trie Source-Version: 0.2+ds-2 We believe that the bug you reported is fixed in the latest version of python-trie, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ondřej Nový (supplier of updated python-trie package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 11 Oct 2019 09:37:31 +0200 Source: python-trie Architecture: source Version: 0.2+ds-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Ondřej Nový Closes: 938228 Changes: python-trie (0.2+ds-2) unstable; urgency=medium . * Team upload. * d/control: Set Vcs-* to salsa.debian.org * d/copyright: Use https protocol in Format field * Convert git repository from git-dpm to gbp layout * Use debhelper-compat instead of debian/compat. * Use Python 3 for building docs. * Drop Python 2 support (Closes: #938228). Checksums-Sha1: 7931645bb950199ca4fa61d928e39e9ab3f3591b 2075 python-trie_0.2+ds-2.dsc 15e81b255bbf64731b7e49870d49e9eaf9bbdfd6 2564 python-trie_0.2+ds-2.debian.tar.xz 9dae4cca76fc4964863b97676b8153e9e2b97f40 7260 python-trie_0.2+ds-2_amd64.buildinfo Checksums-Sha256: 7b1071b9fd3b757f73e2cfb8111f9b627cbef387a3ac52545019934f024eae13 2075 python-trie_0.2+ds-2.dsc
Bug#894134: marked as done (smartmontools: smartd double monitors devices when using symlinks to devices)
Your message dated Fri, 11 Oct 2019 18:09:14 +1100 with message-id <4062130.dkcQCTpKyX@deblab> and subject line Done: smartmontools: smartd double monitors devices when using symlinks to devices has caused the Debian Bug report #894134, regarding smartmontools: smartd double monitors devices when using symlinks to devices 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.) -- 894134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894134 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: smartmontools Version: 6.5+svn4324-1 Severity: normal Hi. It seems that smartd "double monitors" devices, when explicitly naming them via a symbolic link and using DEVICESCAN in the config file. Consider e.g. the following typical use case: One wants to monitor all devices, but has special settings (e.g. different temperature ranges for one e.g. a SSD which runs at higher temps than an HDD): /dev/disk/by-id/ata-Samsung_SSD_850_PRO_1TB_S252NXAG910017F-d auto -d removable -n standby,4 -a -W 0,50,60 -m root -M exec /usr/share/smartmontools/smartd-runner DEVICESCAN -d auto -d removable -n standby,4 -a -W 0,45,50 -m root -M exec /usr/share/smartmontools/smartd-runner It also makes sense to use the symbolic link /dev/disk/by-id/ata-Samsung_SSD_850_PRO_1TB_S252NXAG910017F rather than e.g. /dev/sda, as the later is not necessarily a stable name. However, with the above in smartd.conf, smartd output in syslog shows that apparently both devices /dev/disk/by-id/ata-Samsung_SSD_850_PRO_1TB_S252NXAG910017F and /dev/sda (which I assume is still auto-detected by the DEVICESCAN) are now monitored (presumably with different monitoring settings). Cheers, Chris. --- End Message --- --- Begin Message --- Package: smartmontools Version: 6.6-1 This problem has been fixed in release 6.6-1. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 894...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. signature.asc Description: This is a digitally signed message part. --- End Message ---
Processed: O: c-icap
Processing commands for cont...@bugs.debian.org: > close 942160 Bug #942160 [wnpp] O: c-icap -- ICAP server implementation Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 942160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942160 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#942098: marked as done (Wish for "mmdebstrap unstable unstable-chroot.squashfs")
Your message dated Fri, 11 Oct 2019 08:38:07 +0200
with message-id <157077588706.26294.2134134526565983274@hoothoot>
and subject line Re: Bug#942098: Wish for "mmdebstrap unstable
unstable-chroot.squashfs"
has caused the Debian Bug report #942098,
regarding Wish for "mmdebstrap unstable unstable-chroot.squashfs"
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.)
--
942098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942098
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mmdebstrap
Version: 0.5.0-1
Severity: wishlist
File: /usr/bin/mmdebstrap
It would cool if I could do an unprivileged mmdebstrap and get a .squashfs
instead of a tarball.
Sales pitch:
squashfs is a file format that can act both like an archive (replaces
.tar.xz):
unsquashfs -d foo/ foo.sq
and like a block device (replaces .iso):
sudo mount -o loop foo.sq foo/
squashfs-tools 4.4 understands SOURCE_DATE_EPOCH (reproducible builds).
Unlike .tar.xz, it is possible to list of extract a subtree without
decompressing the whole thing.
Unlike (some versions of) tar, it has sensible defaults, so you do
not get burned by forgetting --numeric-owner.
Debian Live images are squashfs-based for about a decade.
I can't read perl very well anymore, so it's not clear to me how to actually
patch this support in.
Looking at references to "@taropts", it seems like tar gets called about 4
times, and
you'd need an equivalent "mksquashfs" in each one of those cases? Yuk.
For reference, a basic usage is:
mksquashfs foo/ foo.squashfs
And a complicated horrible usage is (in bash):
# NB: with -regex, each path component is matched as a separate,
*unanchored* ERE.
# If you just pass 'usr/share/info/', it will also exclude
usr/share/zoneinfo.
exclusions=(
# Since boot/* is needed outside the squashfs, don't duplicate it
inside.
'^boot$/.'
# Filesystems created at boot time.
'^(dev|tmp|run)$/.'
'^var$/^(lock|run|tmp)$/.'
# Cryptographic keys MUST NOT be baked in.
'^etc$/^dropbear$/^dropbear_.*_host_key$'
'^etc$/^ssh$/^ssh_host_.*_key(.pub)?$'
'^etc$/^ssl$/^certs$/^ssl-cert-snakeoil.pem$'
'^etc$/^ssl$/^private$/^ssl-cert-snakeoil.key$'
# Build-time configuration and cache.
'^etc$/^machine-id$'
'^etc$/^(debian_chroot|hostname|hosts|motd(\.tail)?|resolv.conf)$'
'^etc$/^apt$/^apt.conf.d$/^10bootstrap$'
'^etc$/^network$/^interfaces$'
'^usr$/^sbin$/^policy-rc\.d$'
'^var$/^cache$/^apt$/^(src)?pkgcache\.bin$'
'^var$/^cache$/^apt$/^archives$/\.deb$'
'^var$/^cache$/^bootstrap$'
'^var$/^lib$/^apt$/^lists$/.'
'^var$/^log$/.'
# No documentation (safety net for dpkg.cfg.d/75no-docs).
'^usr$/^share$/^(doc|info|man|omf|help)$/.'
'^usr$/^share$/^gnome$/^help$/.'
)
mksquashfs target/ target/boot/filesystem.squashfs -b 1M -comp xz -Xbcj x86
-Xdict-size 100% -no-recovery -regex -e "${exclusions[@]}"
-- System Information:
Debian Release: 10.1
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates'), (500,
'proposed-updates'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-6-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8),
LANGUAGE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages mmdebstrap depends on:
ii apt 1.8.2
ii perl 5.28.1-6
ii perl-doc 5.28.1-6
Versions of packages mmdebstrap recommends:
ii arch-test 0.15-2
ii fakechroot 2.19-3.2
ii fakeroot 1.23-1
ii mount 2.33.1-0.1
ii pseudo [fakeroot] 1.9.0+git20180920-1
ii uidmap 1:4.5-1.1
Versions of packages mmdebstrap suggests:
pn binfmt-support
ii dpkg-dev 1.19.7
ii proot 5.1.0-1.3
pn qemu-user
pn qemu-user-static
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Trent,
Quoting Trent W. Buck (2019-10-11 03:18:52)
> Short version:
>
> 1. I thought you could pre-generate a dev-only.squashfs with compressor $X,
> then append files with compressor $Y. I was wrong.
>
> I think this is a show-stopper for "rootless" bootstrapping,
> which was the main reason to do mksquashfs "in" mmdebstrap.
>
> 2. For "rootful"
