Bug#1054393: dns-root-data: New IPs for b.root-servers-net 2023-11-27
The root hints as published by IANA have now been updated. I've prepared a merge request here: https://salsa.debian.org/dns-team/dns-root-data/-/merge_requests/2
Bug#985017: python3-whoosh: SyntaxWarning during package installation
This issue also affects users of mailman3-web. The warning is issued when running the hourly cronjob: $ sudo -u www-data flock -n /var/run/mailman3-web/cron.hourly /usr/share/mailman3-web/manage.py runjobs hourly /usr/lib/python3/dist-packages/haystack/backends/whoosh_backend.py:734: SyntaxWarning: "is" with a literal. Did you mean "=="? if value is None or len(value) is 0: /usr/lib/python3/dist-packages/whoosh/codec/whoosh3.py:1116: SyntaxWarning: "is" with a literal. Did you mean "=="? elif fixedsize is 0: Both issues can be fixed by replacing "is" with "==" on the respective lines. Imre signature.asc Description: This is a digitally signed message part
Bug#985018: python3-django-haystack: SyntaxWarning during package installation
This issue also affects users of mailman3-web. The warning is issued when running the hourly cronjob: $ sudo -u www-data flock -n /var/run/mailman3-web/cron.hourly /usr/share/mailman3-web/manage.py runjobs hourly /usr/lib/python3/dist-packages/haystack/backends/whoosh_backend.py:734: SyntaxWarning: "is" with a literal. Did you mean "=="? if value is None or len(value) is 0: /usr/lib/python3/dist-packages/whoosh/codec/whoosh3.py:1116: SyntaxWarning: "is" with a literal. Did you mean "=="? elif fixedsize is 0: Both issues can be fixed by replacing "is" with "==" on the respective lines. Imre signature.asc Description: This is a digitally signed message part
Bug#982813: Select All does not select all text any more
I've found this also affects the new Stable (Bullseye). One workaround is to select the first line, then scroll all the way down, hold Shift and click on the last line. -- Imre Jonk System Administrator CipherMail email encryption Email encryption with support for S/MIME, OpenPGP, PDF encryption and Webmail Messenger. W: https://www.ciphermail.com/ E: i...@ciphermail.com T: +31 20 290 00 88 signature.asc Description: This is a digitally signed message part
Bug#985976: RFS: moon-lander/1:1.0-8 [QA] -- game based on the classic moon lander
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my QA upload of "moon-lander": * Package name: moon-lander Version : 1:1.0-8 Upstream Author : David J. Blood * URL : (not applicable) * License : BSD-2-Clause * Vcs : (not applicable) Section : games It builds those binary packages: moon-lander-data - Data files (sound, images) for moon-lander moon-lander - game based on the classic moon lander To access further information about this package, please visit the following URL: https://mentors.debian.net/package/moon-lander/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/m/moon-lander/moon-lander_1.0-8.dsc Changes since the last upload: moon-lander (1:1.0-8) unstable; urgency=medium . * QA upload. * Fix bug in bonus ship calculation. Patch provided by Asher Gordon. Closes: #944483. * Remove extraneous 'foo' patch from d/patches. * Make d/copyright DEP-5 compliant. * Include "missing" source for moon-lander.bin. * Bump debhelper version to >= 12. * Add desktop file keywords. Regards, -- Imre Jonk
Bug#983198: torbrowser-launcher: launcher does not detect torbrowser as installed on non-EN user session
Hi Marcelo, I can reproduce the issue, and your patch works for me. Thanks for the effort! I hope that the maintainer of torbrowser-launcher can find the time to upload a new version. Cheers, Imre signature.asc Description: This is a digitally signed message part
Bug#984735: composer: fails on installed.json format used in Composer v2
Package: composer Version: 1.8.4-1 Severity: normal Tags: patch Dear Maintainer, (resubmitting this as my previous report seems to have vanished) Composer 1.8.4-1 in Debian 10 fails on the installed.json format of Composer v2. This can be a problem for Debian 10 users who want to use software packaged for Composer 2.0.0 and up. One example of such software is SimpleSAMLphp 1.19.0. This problem has of course been fixed in the composer 2.0.9-1 package in Debian Testing, but you might want to address this in buster-proposed-updates as well. A minimal patch that enables forward compatibility with the v2 format can be found upstream: https://github.com/composer/composer/commit/ba346ef04d7cc6fdbf9423b06f51e48485d20b77 The full transcript of my Composer session can be found here: https://gist.github.com/imrejonk/07e29358c00578386783621c2f08d8ef Here is the exception trace from the transcript above: Exception trace: () at /usr/share/php/Composer/Package/Loader/ArrayLoader.php:44 Composer\Package\Loader\ArrayLoader->load() at /usr/share/php/Composer/Repository/FilesystemRepository.php:63 Composer\Repository\FilesystemRepository->initialize() at /usr/share/php/Composer/Repository/ArrayRepository.php:185 Composer\Repository\ArrayRepository->getPackages() at /usr/share/php/Composer/Plugin/PluginManager.php:256 Composer\Plugin\PluginManager->loadRepository() at /usr/share/php/Composer/Plugin/PluginManager.php:76 Composer\Plugin\PluginManager->loadInstalledPlugins() at /usr/share/php/Composer/Factory.php:384 Composer\Factory->createComposer() at /usr/share/php/Composer/Factory.php:576 Composer\Factory::create() at /usr/share/php/Composer/Console/Application.php:345 Composer\Console\Application->getComposer() at /usr/share/php/Composer/Console/Application.php:458 Composer\Console\Application->getPluginCommands() at /usr/share/php/Composer/Console/Application.php:156 Composer\Console\Application->doRun() at /usr/share/php/Symfony/Component/Console/Application.php:148 Symfony\Component\Console\Application->run() at /usr/share/php/Composer/Console/Application.php:104 Composer\Console\Application->run() at /usr/bin/composer:57 -- System Information: Debian Release: 10.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (50, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-14-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE 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 /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages composer depends on: ii jsonlint 1.7.1-1 ii php-common 2:69 ii php-composer-ca-bundle 1.1.4-1 ii php-composer-semver 1.4.2-1 ii php-composer-spdx-licenses 1.5.0-1 ii php-composer-xdebug-handler 1.3.2-1 ii php-json-schema 5.2.8-1 ii php-psr-log 1.1.0-1 ii php-symfony-console 3.4.22+dfsg-2+deb10u1 ii php-symfony-filesystem 3.4.22+dfsg-2+deb10u1 ii php-symfony-finder 3.4.22+dfsg-2+deb10u1 ii php-symfony-process 3.4.22+dfsg-2+deb10u1 ii php7.3-cli [php-cli] 7.3.19-1~deb10u1 Versions of packages composer recommends: ii git1:2.20.1-2+deb10u3 ii unzip 6.0-23+deb10u1 Versions of packages composer suggests: pn fossil pn mercurial pn php-zip ii subversion 1.10.4-1+deb10u1 -- no debconf information signature.asc Description: This is a digitally signed message part
Bug#977827: rpm: uses /usr/bin/gpg2 by default
Package: rpm Version: 4.14.2.1+dfsg1-1 Severity: normal Dear Maintainer, I tried to sign some RPM packages with rpm --addsign, but this resulted in the following error: `error: Could not exec gpg: No such file or directory` The gnupg package was installed on my system, and the gpg binary was in my PATH. The message above turned out to be a bit misleading as rpm tries to sign using /usr/bin/gpg2 by default, instead of /usr/bin/gpg. My temporary workaround is to add the flag --define='%__gpg /usr/bin/gpg'. Another option is to install the gnupg2 package which just adds a symlink. I would appreciate it if you could make rpm use the gpg binary by default. Kind regards, Imre Jonk -- System Information: Debian Release: 10.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-13-amd64 (SMP w/8 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) LSM: AppArmor: enabled Versions of packages rpm depends on: ii debugedit 4.14.2.1+dfsg1-1 ii libc6 2.28-10 ii libelf1 0.176-1.1 ii libpopt0 1.16-12 ii librpm8 4.14.2.1+dfsg1-1 ii librpmbuild8 4.14.2.1+dfsg1-1 ii librpmio8 4.14.2.1+dfsg1-1 ii librpmsign8 4.14.2.1+dfsg1-1 ii perl 5.28.1-6+deb10u1 ii rpm-common4.14.2.1+dfsg1-1 ii rpm2cpio 4.14.2.1+dfsg1-1 rpm recommends no packages. Versions of packages rpm suggests: pn alien pn elfutils ii python2.7.16-1 pn rpm-i18n pn rpm2html pn rpmlint -- no debconf information
Bug#933570: gnt-cluster manpage not found
On Wed, 31 Jul 2019 12:34:48 -0400 Antoine Beaupre wrote: > Package: manpages.debian.org > Severity: normal > > For some reason, the `gnt-cluster` manpage, part of the ganeti > package, cannot be found by manpages.debian.org The same goes for the other Ganeti manpages (e.g. ganeti(7) and gnt- backup(8)), both un buster and unstable. This is the error message that manpages.debian.org serves me: ``` Sorry, the manpage could not be rendered! Error message: open /srv/manpages.debian.org/www/buster/ganeti/ganeti.7.en.gz: no such file or directory ``` signature.asc Description: This is a digitally signed message part
Bug#935825: postfix: Race condition at start between postfix and dhcp.
I'm experiencing the same issue. Commenting out this line in /etc/resolvconf/update-libc.d/postfix solved it for me: /usr/sbin/service postfix status >/dev/null 2>&1 || exit 0 My guess is that the race condition works like this: 1. configure-instance.sh is ran through ExecStartPre before /etc/resolv.conf has been properly set up. This copies an empty /etc/resolv.conf to the Postfix chroot. 2. resolvconf sets up /etc/resolv.conf and runs /etc/resolvconf/update-libc.d/postfix. This script does nothing as the Postfix service has not been started yet. 3. The Postfix service is started through ExecStart, but still has a broken resolv.conf file in its chroot. signature.asc Description: OpenPGP digital signature
Bug#930919: dovecot: dsync broken for sieve filters
On Fri, 6 Sep 2019 19:07:43 +0200 Lukas Schwaighofer wrote: > I also got this error when migrating my configuration from stretch to > buster and added the following setting to my 10-mail.conf: > > mail_attribute_dict = file:~/dovecot-attributes Thanks Lukas, this configuration setting combined with the upstream patch also works for me. I'm using the Sieve add-on for Thunderbird to manage my sieve scripts: https://github.com/thsmi/sieve/. It would be great to see this fixed in Buster. Imre signature.asc Description: OpenPGP digital signature
Bug#941447: pipenv: AttributeError when running 'pipenv check'
Package: pipenv Version: 11.9.0-1 Severity: normal Dear Maintainer, The command 'pipenv check' fails with the following output: Checking PEP 508 requirements… Passed! Checking installed package safety… An error occurred: Traceback (most recent call last): File "/usr/lib/python3.7/runpy.py", line 193, in _run_module_as_main "__main__", mod_spec) File "/usr/lib/python3.7/runpy.py", line 85, in _run_code exec(code, run_globals) File "/usr/lib/python3/dist-packages/pipenv/patched/safety.zip/__main__.py", line 8, in File "/usr/lib/python3/dist-packages/pipenv/patched/safety.zip/click/core.py", line 722, in __call__ File "/usr/lib/python3/dist-packages/pipenv/patched/safety.zip/click/core.py", line 697, in main File "/usr/lib/python3/dist-packages/pipenv/patched/safety.zip/click/core.py", line 1066, in invoke File "/usr/lib/python3/dist-packages/pipenv/patched/safety.zip/click/core.py", line 895, in invoke File "/usr/lib/python3/dist-packages/pipenv/patched/safety.zip/click/core.py", line 535, in invoke File "/usr/lib/python3/dist-packages/pipenv/patched/safety.zip/safety/cli.py", line 52, in check AttributeError: module 'pip' has no attribute 'get_installed_distributions' This command should return information about possible security issues with the Python packages listed in the Pipfile. This issue on GitHub might be related: https://github.com/pypa/pip/issues/5243 -- System Information: Debian Release: 10.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE 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) LSM: AppArmor: enabled Versions of packages pipenv depends on: ii python3 3.7.3-1 ii python3-certifi 2018.8.24-1 ii python3-pip 18.1-5 ii python3-pkg-resources 40.8.0-1 ii python3-virtualenv15.1.0+ds-2 ii python3-virtualenv-clone 0.3.0-1.2 pipenv recommends no packages. pipenv suggests no packages. -- no debconf information
