Processed: your mail
Processing commands for cont...@bugs.debian.org: > severity 980472 grave Bug #980472 [libhamlib4] cubicsdr: CubicSDR crashes after lauch! (same effect on 2 clean bullseye OS) Severity set to 'grave' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 980472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980472 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#991015: Acknowledgement (cannot execute due to incorrect shebang line)
This bug seems to be, in part, due to a potentially (?) broken ruby upgrade behaviour. I've been running unstable on this laptop for ~6 years, but still had ii ruby2.1 [ruby-interpreter] 2.1.5-4 ii ruby2.2 [ruby-interpreter] 2.2.4-1 installed as my only ruby interpreters. These are no longer available in unstable, and ruby2.1 was last available in: ruby2.1| 2.1.5-2+deb8u3 | oldoldstable | source, amd64, armel, armhf, i386 Will users upgrading from buster to bullseye will encounter a similar issue if they've dist-upgraded from jessie to stretch to buster? -- |)|/ Ryan Kavanagh | 4E46 9519 ED67 7734 268F |\|\ https://rak.ac | BD95 8F7B F8FC 4A11 C97A signature.asc Description: PGP signature
Bug#991015: cannot execute due to incorrect shebang line
Package: asciidoctor Version: 2.0.12-2 Severity: grave asciidoctor cannot be executed because its shebang line is wrong rak@zeta:~$ sudo apt install asciidoctor [...] Setting up ruby-asciidoctor (2.0.12-2) ... Setting up asciidoctor (2.0.12-2) ... Processing triggers for man-db (2.9.4-2) ... rak@zeta:~$ asciidoctor bash: /usr/bin/asciidoctor: /usr/bin/ruby: bad interpreter: No such file or directory rak@zeta:~$ head -n1 /usr/bin/asciidoctor #!/usr/bin/ruby rak@zeta:~$ ls /usr/bin/ruby ls: cannot access '/usr/bin/ruby': No such file or directory -- System Information: Debian Release: 11.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-7-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_CPU_OUT_OF_SPEC, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages asciidoctor depends on: ii ruby-asciidoctor2.0.12-2 ii ruby2.1 [ruby-interpreter] 2.1.5-4 ii ruby2.2 [ruby-interpreter] 2.2.4-1 asciidoctor recommends no packages. asciidoctor suggests no packages. -- no debconf information -- |)|/ Ryan Kavanagh | 4E46 9519 ED67 7734 268F |\|\ https://rak.ac | BD95 8F7B F8FC 4A11 C97A signature.asc Description: PGP signature
Processed: Re: Bug#990622: bitlbee-plugin-facebook: The plugin does not start
Processing control commands: > severity -1 important Bug #990622 [bitlbee-plugin-facebook] bitlbee-plugin-facebook: The plugin does not start Severity set to 'important' from 'serious' > notforwarded -1 Bug #990622 [bitlbee-plugin-facebook] bitlbee-plugin-facebook: The plugin does not start Unset Bug forwarded-to-address -- 990622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990622 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#990622: bitlbee-plugin-facebook: The plugin does not start
control: severity -1 important control: notforwarded -1 Hello Adrian, others, On Mon 12 Jul 2021 at 01:37PM +03, Adrian Bunk wrote: > On Sun, Jul 11, 2021 at 11:03:14PM -0700, Sean Whitton wrote: >> Hello Adrian, > > Hi Sean, > >> Thanks for looking into this, but are you sure that [1] is this bug? >> The original reporter saw the error ERROR_QUEUE_UNDERFLOW but [1] is >> about ERROR_QUEUE-OVERFLOW. >>... > > I might be wrong on that. > > I was searching the BTS for bugs that should be RC but weren't. > While looking at upstream for this bug, I saw this upstream issue. > > If the package is not generally broken and works for you, > feel free to lower the severity again. > > If my guess on what upstream issue matches the problem was wrong, > please ignore it. Thank you for your reply. I can't verify whether or not the plugin is actually broken because my ordinary bitlbee server, and one I just set up on my laptop, are both hitting this bug: https://github.com/bitlbee/bitlbee-facebook/issues/105 https://github.com/bitlbee/bitlbee-facebook/issues/108 I'm downgrading the severity and dropping the 'forwarded' until someone is able to confirm that the plugin is unusable and it is indeed the upstream _OVERFLOW bug. -- Sean Whitton signature.asc Description: PGP signature
Processed: Re: autopkgtest fails with rails 6 in experimental
Processing control commands: > severity -1 important Bug #966212 [ruby-js-image-paths] autopkgtest fails with rails 6 in experimental Severity set to 'important' from 'serious' -- 966212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966212 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966212: autopkgtest fails with rails 6 in experimental
Control: severity -1 important Sat, 25 Jul 2020 00:29:54 +0530 Pirate Praveen wrote: > This package's autopkgtest and rebuilds failed with rails 6 currently in > experimental. rails 6 will be uploaded to unstable in a weeks time, so > please make sure this package is ready for rails 6. The severity of > this bug will be raised to serious after rails 6 is uploaded to > unstable. Its only reverse dependency diaspora now embeds rail 5 so we can ignore this version check. I will keep the bug open if somoene wants verify rails 6 compatibility or if upstream confirms it. I have relaxed the dependency with a patch for now.
Processed: no issue in bullseye
Processing commands for cont...@bugs.debian.org: > # broken by openjdk-11 in unstable, as long as it doesn't migrate... > tags 991006 bullseye-ignore Bug #991006 [src:openjdk-11-jre-dcevm] openjdk-11-jre-dcevm: autopkgtest broken by openjdk-11 in unstable Added tag(s) bullseye-ignore. > thanks Stopping processing here. Please contact me if you need assistance. -- 991006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991006 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#989103: pulseaudio crashes on startup
Hi Hideki, On Mon, 21 Jun 2021 02:45:15 +0900 Hideki Yamane wrote: > On Mon, 7 Jun 2021 22:37:11 +0300 Igor Kovalenko > wrote: > > I confirm this is a regression in pulseaudio-14.0, fixed in pulseaudio > > master now. > > > > https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/576 > > Thank you, let's patch for debian package, then. > I've attached patches not MR, since some commits were already done > in master branch. We're approaching the bullseye full freeze. Do you intent to upload this NMU soon? Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: tagging 990359
Processing commands for cont...@bugs.debian.org:
> tags 990359 + patch
Bug #990359 {Done: Thomas Goirand } [websockify]
python3-websockify: rebind.so not found (when used in program wrapper mode)
Ignoring request to alter tags of bug #990359 to the same tags previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
990359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990359
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#991006: openjdk-11-jre-dcevm: autopkgtest broken by openjdk-11 in unstable
Source: openjdk-11-jre-dcevm Version: 1.0.11+9-2 Severity: serious https://ci.debian.net/data/autopkgtest/testing/amd64/o/openjdk-11-jre-dcevm/13559634/log.gz ... autopkgtest [12:12:28]: test java-version: java -dcevm -version autopkgtest [12:12:28]: test java-version: [--- # # A fatal error has been detected by the Java Runtime Environment: # # Internal Error (classLoader.cpp:1217), pid=3385, tid=3390 # guarantee(JImageResourcePath != NULL) failed: function JIMAGE_ResourcePath not found # # JRE version: (11.0.12+6) (build ) # Java VM: Dynamic Code Evolution 64-Bit Server VM (11.0.11-internal+0-adhoc.buildd.openjdk-11-jre-dcevm-11.0.119, mixed mode, sharing, tiered, unknown gc, linux-amd64) # No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /tmp/autopkgtest-lxc.xdpuhkvl/downtmp/build.zk5/src/hs_err_pid3385.log # # bash: line 1: 3385 Aborted bash -ec 'java -dcevm -version' 2> >(tee -a /tmp/autopkgtest-lxc.xdpuhkvl/downtmp/java-version-stderr >&2) > >(tee -a /tmp/autopkgtest-lxc.xdpuhkvl/downtmp/java-version-stdout) autopkgtest [12:12:30]: test java-version: ---] autopkgtest [12:12:30]: test java-version: - - - - - - - - - - results - - - - - - - - - - java-version FAIL non-zero exit status 134
Bug#986815: marked as done (CVE-2021-21375 CVE-2020-15260)
Your message dated Mon, 12 Jul 2021 18:02:15 + with message-id and subject line Bug#986815: fixed in ring 20190215.1.f152c98~ds1-1+deb10u1 has caused the Debian Bug report #986815, regarding CVE-2021-21375 CVE-2020-15260 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.) -- 986815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986815 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ring Severity: grave Tags: security X-Debbugs-Cc: Debian Security Team ring bundles pjproject, so it's probably also affected by CVE-2021-21375? Advisory for pjproject is https://github.com/pjsip/pjproject/security/advisories/GHSA-hvq6-f89p-frvp Patch: https://github.com/pjsip/pjproject/commit/97b3d7addbaa720b7ddb0af9bf6f3e443e664365 Cheers, Moritz --- End Message --- --- Begin Message --- Source: ring Source-Version: 20190215.1.f152c98~ds1-1+deb10u1 Done: Thorsten Alteholz We believe that the bug you reported is fixed in the latest version of ring, 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 986...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Alteholz (supplier of updated ring package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 22 Apr 2021 19:03:02 +0200 Source: ring Architecture: source Version: 20190215.1.f152c98~ds1-1+deb10u1 Distribution: buster Urgency: high Maintainer: Debian VoIP Team Changed-By: Thorsten Alteholz Closes: 986815 Changes: ring (20190215.1.f152c98~ds1-1+deb10u1) buster; urgency=high . * Non-maintainer upload by the LTS Team. * CVE-2021-21375 (Closes: #986815) The embedded copy of pjproject is affected by this CVE. Due to bad handling of two consecutive crafted answers to an INVITE, the attacker is able to crash the server resulting in a denial of service. Checksums-Sha1: cc459f514624fd91fe53e25b1978133afbc62b6e 3234 ring_20190215.1.f152c98~ds1-1+deb10u1.dsc 5a90a143194506b9d5fe3195490d0486ae400be9 12536 ring_20190215.1.f152c98~ds1-1+deb10u1.debian.tar.xz bb88c2d98e8703f5393ffab82cf07810fd2521b5 26116 ring_20190215.1.f152c98~ds1-1+deb10u1_amd64.buildinfo Checksums-Sha256: ad23bf1f82d55f4000d4a6d8522ce06fcec7a49e90c6a8c8b64e8cab0741036e 3234 ring_20190215.1.f152c98~ds1-1+deb10u1.dsc b6b9f6da17602cc572daecc26b1500ac120de683fd4ee615408839dff2c73d0f 12536 ring_20190215.1.f152c98~ds1-1+deb10u1.debian.tar.xz 8444f702a28c62fad39f0d6bfc6ea08b17f5e2794fa9181ea4eac19463920561 26116 ring_20190215.1.f152c98~ds1-1+deb10u1_amd64.buildinfo Files: 50a5f7ace32a6370dfa32525f6db4852 3234 comm optional ring_20190215.1.f152c98~ds1-1+deb10u1.dsc efdd7c182302124c346ee597a6dec2fa 12536 comm optional ring_20190215.1.f152c98~ds1-1+deb10u1.debian.tar.xz 1ae297d9021db39f7612209428f4e72c 26116 comm optional ring_20190215.1.f152c98~ds1-1+deb10u1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKnBAEBCgCRFiEEYgH7/9u94Hgi6ruWlvysDTh7WEcFAmDGhGFfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYy MDFGQkZGREJCREUwNzgyMkVBQkI5Njk2RkNBQzBEMzg3QjU4NDcTHGRlYmlhbkBh bHRlaG9sei5kZQAKCRCW/KwNOHtYR0y5EACcV8ggYaDq7GHvOAFB5Fyk2aJdP6Bx Xc0Kl24fwIcqlt5H+7oxyW7TqYiaUy+gvzIW+lF3AHVezeJnmozAd6Baful5QLoM M3bqYobgb4af47sqC0RQnIRgVxyXtYvAwgoXZUPGbDuub4G/R2DxOumpE0BtsVmQ RN5IH+yq2or6WB9R4V/73UrwwaSYFTOcQhU3fNkuyLMIlosqSNBRNZjQrEV7N15i 2g2xpE5TFcX0PPF5r3kNm793v3htfnVRnSQpd5iF9R5B89I/YFSBvgBjbgVmTb38 dwag/D5GYw7MxWeLMZ7Oq9HznXG3SUGAy1FJOXp93uqP7uYiLlKeSUTKwYHdGJTB K7UW/hJH+lwlU8mHBs/ryvd1XuvuuG34Eer/227XnIgKbh9PlbPJD8yujGWaNmKe Gv40thkoTnBI9steXelPw6ZP77pueTjNyy2j15wbJoma7hVGucx31WefccE6hlao 2/8sVYT7IO+9DaPahwSs9XZFqmrMn+vHkuRmWiB8OvFjV1d3G2CKeHLNUsXnxx5d TdoPpJ0vaxWxHLs3LMtyu7nwe2zn8xX4XE5paS+hzqWHNphrL8fEFyHL3RFiV3rD YA7Whye8yUb4cBkygUu4rtu7+wK+DWdynhWhNNZOuCTTl5Flo4FkEQ1+N0DOLdvR 2K8k6oQHiXiZAw== =UXLU -END PGP SIGNATURE End Message ---
Bug#990359: python3-websockify: rebind.so not found (when used in program wrapper mode)
Hi Thomas, hi Jochen, On Mo 12 Jul 2021 09:34:02 CEST, Thomas Goirand wrote: On 7/12/21 8:11 AM, Jochen Sprickerhof wrote: Control: -1 patch Hi Thomas, the attached patch fixes this for me, can you take care of uploading or should I? Cheers Jochen Hi Jochen, Thanks for the patch, I uploaded version -3 of websockify including it. I'm not sure how this will behave with multiarch, however, obviously we already have the issue with the rebind.o file, so I don't think its more harmful than previously. Cheers, Thomas Goirand (zigo) thanks for fixing this so promptly. Mike -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de pgp6G3qrIks9i.pgp Description: Digitale PGP-Signatur
Processed: The *manpage* is not fixed
Processing commands for cont...@bugs.debian.org: > severity 989251 minor Bug #989251 [src:pmount] pmount: Manpage lists maintainer with email address that is not reachable. Bug #989254 [src:pmount] project: Maintainer email of package `pmount` seems wrong. Severity set to 'minor' from 'serious' Severity set to 'minor' from 'serious' > notfixed 989251 0.9.23-4 Bug #989251 [src:pmount] pmount: Manpage lists maintainer with email address that is not reachable. Bug #989254 [src:pmount] project: Maintainer email of package `pmount` seems wrong. No longer marked as fixed in versions pmount/0.9.23-4. No longer marked as fixed in versions pmount/0.9.23-4. > thanks Stopping processing here. Please contact me if you need assistance. -- 989251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989251 989254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989254 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#991003: kpatch-dkms: fails to build module for Linux 4.19.0-17 or newer: find_symbol is no longer exported by the kernel
Package: kpatch-dkms Version: 0.6.0-0.2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts kpatch-dkms fails to build a module for the latest kernel in stable. For more context on this change in the kernel, please see the corresponding bug in iptables-netflow-dkms: https://bugs.debian.org/990123 DKMS make.log for kpatch-0.6.0 for kernel 4.19.0-17-amd64 (x86_64) Mon Jul 12 17:13:04 UTC 2021 make: Entering directory '/var/lib/dkms/kpatch/0.6.0/build/kmod' make -C core clean make[1]: Entering directory '/var/lib/dkms/kpatch/0.6.0/build/kmod/core' rm -f -Rf .*.o.cmd .*.ko.cmd .tmp_versions *.o *.ko *.mod.c \ Module.symvers make[1]: Leaving directory '/var/lib/dkms/kpatch/0.6.0/build/kmod/core' make -C core make[1]: Entering directory '/var/lib/dkms/kpatch/0.6.0/build/kmod/core' make -C /lib/modules/4.19.0-17-amd64/build M=/var/lib/dkms/kpatch/0.6.0/build/kmod/core kpatch.ko make[2]: Entering directory '/var/lib/dkms/kpatch/0.6.0/build/kmod/core' make[2]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule. CC [M] /var/lib/dkms/kpatch/0.6.0/build/kmod/core/core.o /var/lib/dkms/kpatch/0.6.0/build/kmod/core/core.c: In function 'kpatch_find_external_symbol': /var/lib/dkms/kpatch/0.6.0/build/kmod/core/core.c:661:8: error: implicit declaration of function 'find_symbol'; did you mean 'sprint_symbol'? [-Werror=implicit-function-declaration] sym = find_symbol(name, NULL, NULL, true, true); ^~~ sprint_symbol /var/lib/dkms/kpatch/0.6.0/build/kmod/core/core.c:661:6: warning: assignment to 'const struct kernel_symbol *' from 'int' makes pointer from integer without a cast [-Wint-conversion] sym = find_symbol(name, NULL, NULL, true, true); ^ cc1: some warnings being treated as errors make[5]: *** [/usr/src/linux-headers-4.19.0-17-common/scripts/Makefile.build:309: /var/lib/dkms/kpatch/0.6.0/build/kmod/core/core.o] Error 1 make[4]: *** [/usr/src/linux-headers-4.19.0-17-common/Makefile:1738: kpatch.ko] Error 2 make[3]: *** [Makefile:146: sub-make] Error 2 make[2]: *** [Makefile:8: all] Error 2 make[2]: Leaving directory '/usr/src/linux-headers-4.19.0-17-amd64' make[1]: *** [Makefile:13: kpatch.ko] Error 2 make[1]: Leaving directory '/var/lib/dkms/kpatch/0.6.0/build/kmod/core' make: *** [Makefile:7: all] Error 2 make: Leaving directory '/var/lib/dkms/kpatch/0.6.0/build/kmod' Andreas
Bug#991000: bareos-database-common: fails to upgrade from buster: ERROR: invalid value for parameter "client_min_messages": "fatal"
Package: bareos-database-common Version: 17.2.7-2.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'buster'. It installed fine in 'buster', then the upgrade to 'sid' fails. (There is no bareos in bullseye, so the buster bareos packages were kept installed during the upgrade to bullseye. But the postgresql cluster was upgraded from 11 to 13.) >From the attached log (scroll to the bottom...): Setting up bareos-database-common (17.2.7-2.1) ... Warning: failed to get "dbname" from config, using default value "bareos", see /tmp/bareos-config.9027.log Warning: failed to get "dbuser" from config, using default value "bareos", see /tmp/bareos-config.9027.log (config) dbc_go() bareos-database-common configure 2004. dbc_config() bareos-database-common configure 2004. dbc_set_dbtype_defaults() . dbc_detect_installed_dbtype() pgsql. _dbc_detect_installed_dbtype() pgsql. dbc_register_debconf() . dbc_read_package_config() . dbc_preseed_package_debconf() . dbc_config() bareos-database-common configure 2004. dbc_set_dbtype_defaults() pgsql. dbc_detect_installed_dbtype() pgsql. _dbc_detect_installed_dbtype() pgsql. dbc_register_debconf() . dbc_get_app_pass() . dbconfig-common: writing config to /etc/dbconfig-common/bareos-database-common.conf creating database backup in /var/cache/dbconfig-common/backups/bareos-database-common_2004.2021-07-12-01.24.18. applying upgrade sql for 2004 -> 2171. error encountered processing /usr/share/dbconfig-common/data/bareos-database-common/upgrade/pgsql/2171: NOTICE: table "tmpmergefilenameintofiletable" does not exist, skipping setval (1 row) ERROR: invalid value for parameter "client_min_messages": "fatal" HINT: Available values: debug5, debug4, debug3, debug2, debug1, log, notice, warning, error. dbconfig-common: bareos-database-common configure: aborted. dbconfig-common: flushing administrative password dpkg: error processing package bareos-database-common (--configure): installed bareos-database-common package post-installation script subprocess returned error exit status 1 Processing triggers for libc-bin (2.31-13) ... Errors were encountered while processing: bareos-database-common cheers, Andreas bareos-database-common_17.2.7-2.1.log.gz Description: application/gzip
Processed: Re: atftpd: Installation inconsistent and not functional
Processing control commands: > severity -1 serious Bug #988456 [atftpd] atftpd: Installation inconsistent and not functional Severity set to 'serious' from 'normal' > found -1 0.7.git20120829-3.2 Bug #988456 [atftpd] atftpd: Installation inconsistent and not functional Ignoring request to alter found versions of bug #988456 to the same values previously set -- 988456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988456 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#990708: [debian-mysql] Bug#990708: mariadb-server-10.5: upgrade problems due to galera-3 -> galera-4 switch
On 11/07/2021 08.55, Otto Kekäläinen wrote: Tested Roundcube + default-mysql-server upgrades with both apt and apt-get, and with and without --no-install-recommends in https://salsa.debian.org/mariadb-team/mariadb-10.5/-/commit/c3f53fe664517bbce7f8ae67244e018f9086534c All passed fine. the early upgrade of apt "broke" the test, using apt/buster "works fine", i.e. default-mysql-server gets removed. I'm not sure whether the updated apt resolver works differently, or if just the different set of installed packages makes the difference. And my dependency change in mariadb-server-10.5 does not change the outcome as long as the correspondig change is missing from galera-4 Andreas
Bug#990705: marked as done (nova-common: please depend on python3-q-text-as-data)
Your message dated Mon, 12 Jul 2021 11:18:32 +
with message-id
and subject line Bug#990705: fixed in nova 2:22.0.1-2
has caused the Debian Bug report #990705,
regarding nova-common: please depend on python3-q-text-as-data
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.)
--
990705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990705
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nova-common
Version: 2:22.0.1-1
Severity: serious
Tags: patch
nova-common depends on q-text-as-data which is a virtual package
provided by python-q-text-as-data up to buster and by
python3-q-text-as-data since stretch. Apt does not like to swap packages
to satisfy a dependency. To ease switching the provider from python-q-*
to python3-q-* on upgrades from buster, please add an explicit dependency
on python3-q-text-as-data (and place it in front of q-text-as-data).
This can be removed again for bookworm.
Andreas
diff -Nru nova-22.0.1/debian/changelog nova-22.0.1/debian/changelog
--- nova-22.0.1/debian/changelog2021-01-19 10:10:02.0 +0100
+++ nova-22.0.1/debian/changelog2021-07-04 23:45:12.0 +0200
@@ -1,3 +1,11 @@
+nova (2:22.0.1-2) UNRELEASED; urgency=medium
+
+ * nova-common: Explicitly depend on python3-q-text-as-data to ease switching
+from python-q-text-as-data which both provide the unversioned virtual
+package q-text-as-data. (Closes: #-1)
+
+ -- Andreas Beckmann Sun, 04 Jul 2021 23:45:12 +0200
+
nova (2:22.0.1-1) unstable; urgency=medium
* New upstream point release.
diff -Nru nova-22.0.1/debian/control nova-22.0.1/debian/control
--- nova-22.0.1/debian/control 2021-01-19 10:10:02.0 +0100
+++ nova-22.0.1/debian/control 2021-07-04 23:45:12.0 +0200
@@ -165,6 +165,7 @@
python3-iso8601,
python3-nova (= ${binary:Version}),
python3-openstackclient,
+ python3-q-text-as-data,
q-text-as-data,
sqlite3,
${misc:Depends},
--- End Message ---
--- Begin Message ---
Source: nova
Source-Version: 2:22.0.1-2
Done: Thomas Goirand
We believe that the bug you reported is fixed in the latest version of
nova, 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 990...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thomas Goirand (supplier of updated nova package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 12 Jul 2021 12:57:03 +0200
Source: nova
Architecture: source
Version: 2:22.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack
Changed-By: Thomas Goirand
Closes: 990705
Changes:
nova (2:22.0.1-2) unstable; urgency=medium
.
* Add depend on python3-q-text-as-data (Closes: #990705).
* Do not set [glance]/api_servers http://localhost:9292 as default: let
Nova figure it out from the Keystone catalogue.
Checksums-Sha1:
301fd902c6c3302b9bf09124ba5c8cb58ca8d665 5307 nova_22.0.1-2.dsc
36d3b517b4e2281a1597e87080d3d30b2270ea9f 60168 nova_22.0.1-2.debian.tar.xz
4c84c6314b4e5fd54c9921c621db0f5e5bc31c43 22732 nova_22.0.1-2_amd64.buildinfo
Checksums-Sha256:
557e99f8ad902d3bdc5251c27ebde367afce0e9a49fa74ac63cbc00022821329 5307
nova_22.0.1-2.dsc
d5a81d705411932421e16f05c6082e72e1ae65efc6753f5f99d1ce40b76d9955 60168
nova_22.0.1-2.debian.tar.xz
581823539b771a071ee6dc01cdc43390fa6c83ed59d0053c45f26eacfa1a8928 22732
nova_22.0.1-2_amd64.buildinfo
Files:
3984647ecac13244795b17f84ced2f57 5307 net optional nova_22.0.1-2.dsc
32e19bce113cb014a4781f231afd333a 60168 net optional nova_22.0.1-2.debian.tar.xz
6b6440cf17ccbd4093666f95e8201ebf 22732 net optional
nova_22.0.1-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmDsIYwACgkQ1BatFaxr
Q/6+Mg//a6plzJGgvroKlbEGR7/3ppmuqrkUZLTG8muoBM/9YgJADF9q6FXoAR9L
QyaLEeo8KVyDkONfQxaq9rrMJmog10GjzjtQ5JE9XFP6RqL1CarVAc7EHNVeipof
zs8tRfB653Qzl2gn8yNiFLC57BqMCah+Qg39cVOFoyQhU7zXBdTWw2R3eIb/HwZe
E0ljuu1r6P7cwseMh+7wRTW2Je+BIwGqsYBqWSSYuLBykDaQa3rH0sHE4i0IBSiE
b4owUCtMF8n3GT/PrTCuWJ96A1PR4wHOUCERq2paG8+3hPezETbwAi2SgiFR0mc2
IvXjW3EvnpO2wqwuVlBWT8IeNPJA4OZ7xPfmnA+8yoVFZSZF2xSjFkRX4PToXlvU
GtPboxQHC8HspG9NqGaUfpGNG52WLk1z4PLpvk74KyITkRR8XC5t+G19
Bug#990371: munin-node: Unit fails on startup - Runtime directory n/a
On Sun, Jul 11, 2021 at 10:08:03PM +0900, Kentaro Hayashi wrote: > I've sent MR to fix this issue. > https://salsa.debian.org/debian/munin/-/merge_requests/5 thank you, I'm preparing an upload now. -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ &fff & everyday for future too. signature.asc Description: PGP signature
Bug#990705: marked as pending in nova
Control: tag -1 pending Hello, Bug #990705 in nova reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/services/nova/-/commit/6b302ea188aeddc50e2079f9ce3846755985ab60 Add depend on python3-q-text-as-data (Closes: #990705). (this message was generated automatically) -- Greetings https://bugs.debian.org/990705
Processed: Bug#990705 marked as pending in nova
Processing control commands: > tag -1 pending Bug #990705 [nova-common] nova-common: please depend on python3-q-text-as-data Ignoring request to alter tags of bug #990705 to the same tags previously set -- 990705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990705 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#990622: bitlbee-plugin-facebook: The plugin does not start
On Sun, Jul 11, 2021 at 11:03:14PM -0700, Sean Whitton wrote: > Hello Adrian, Hi Sean, > Thanks for looking into this, but are you sure that [1] is this bug? > The original reporter saw the error ERROR_QUEUE_UNDERFLOW but [1] is > about ERROR_QUEUE-OVERFLOW. >... I might be wrong on that. I was searching the BTS for bugs that should be RC but weren't. While looking at upstream for this bug, I saw this upstream issue. If the package is not generally broken and works for you, feel free to lower the severity again. If my guess on what upstream issue matches the problem was wrong, please ignore it. > Sean Whitton cu Adrian
Bug#990359: marked as done (python3-websockify: rebind.so not found (when used in program wrapper mode))
Your message dated Mon, 12 Jul 2021 07:50:22 +
with message-id
and subject line Bug#990359: fixed in websockify 0.9.0+dfsg1-3
has caused the Debian Bug report #990359,
regarding python3-websockify: rebind.so not found (when used in program
wrapper mode)
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.)
--
990359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990359
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-websockify
Severity: important
Version: 0.9.0+dfsg1-2+b1
Hi,
I played with websockify and NoVNC recently and discovered that
websockify's program wrapper mode is currently broken in Debian 11:
```
[sunweaver@sunobo ~]$ websockify 127.0.0.1:9898 -- x11vnc -noipv6 -display :0
Traceback (most recent call last):
File "/usr/bin/websockify", line 33, in
sys.exit(load_entry_point('websockify==0.9.0', 'console_scripts',
'websockify')())
File "/usr/lib/python3/dist-packages/websockify/websocketproxy.py",
line 725, in websockify_init
server = WebSocketProxy(**opts.__dict__)
File "/usr/lib/python3/dist-packages/websockify/websocketproxy.py",
line 306, in __init__
raise Exception("rebind.so not found, perhaps you need to run make")
Exception: rebind.so not found, perhaps you need to run make
```
The directory /usr/lib/websockify has this content here:
```
root@sunobo:/usr/lib/websockify# LANG=C ls -al
total 44
drwxr-xr-x 2 root root 4096 Jun 27 07:01 .
drwxr-xr-x 182 root root 12288 Jun 24 15:44 ..
-rw-r--r-- 1 root root 14304 Nov 19 2020
rebind.cpython-39-x86_64-linux-gnu.so
-rw-r--r-- 1 root root 11776 Nov 19 2020 rebind.o
```
My work-around for the above error is putting a symlink into this
directory, like this:
```
root@sunobo:/usr/lib/websockify# LANG=C ls -al
total 44
drwxr-xr-x 2 root root 4096 Jun 27 07:05 .
drwxr-xr-x 182 root root 12288 Jun 24 15:44 ..
-rw-r--r-- 1 root root 14304 Nov 19 2020
rebind.cpython-39-x86_64-linux-gnu.so
-rw-r--r-- 1 root root 11776 Nov 19 2020 rebind.o
lrwxrwxrwx 1 root root37 Jun 27 07:05 rebind.so ->
rebind.cpython-39-x86_64-linux-gnu.so
```
Please, possibly fix this for Debian 11. If more help is needed,
please let me know.
Greets,
Mike
--
DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940
GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de
pgpYlC2v79EcB.pgp
Description: Digitale PGP-Signatur
--- End Message ---
--- Begin Message ---
Source: websockify
Source-Version: 0.9.0+dfsg1-3
Done: Thomas Goirand
We believe that the bug you reported is fixed in the latest version of
websockify, 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 990...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thomas Goirand (supplier of updated websockify package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 12 Jul 2021 09:18:22 +0200
Source: websockify
Architecture: source
Version: 0.9.0+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack
Changed-By: Thomas Goirand
Closes: 990359
Changes:
websockify (0.9.0+dfsg1-3) unstable; urgency=medium
.
[ Jochen Sprickerhof ]
* Fix rebind.so not found (Closes: #990359), thanks to Mike Gabriel for the
bug report, and Jochen Sprickerhof for the fix.
Checksums-Sha1:
657a7443dd99d3fabbd5c646111b2f3460a159a7 2191 websockify_0.9.0+dfsg1-3.dsc
e47cfcffa3ea1f43ad15197e9748da07a0da22ac 11596
websockify_0.9.0+dfsg1-3.debian.tar.xz
716cb2cd837b37d5e4ba5fadb73daa0834e1e2ee 8001
websockify_0.9.0+dfsg1-3_amd64.buildinfo
Checksums-Sha256:
48622ed701328f837b7beff86c4f6f9fae5b9023870d7f69ce81f8981b8ffe94 2191
websockify_0.9.0+dfsg1-3.dsc
d33a00c1f7a19b6ab7952593231ecacadc7cc7416138e0d762ec9b8d1899af18 11596
websockify_0.9.0+dfsg1-3.debian.tar.xz
aee94631a7db3fe10e367c9583c681e7e724bfc41d5c3217e413a49b2f8c8ef0 8001
websockify_0.9.0+dfsg1-3_amd64.buildinfo
Files:
651621c2134964766e9a173c66ebd09b 2
Bug#990359: python3-websockify: rebind.so not found (when used in program wrapper mode)
On 7/12/21 8:11 AM, Jochen Sprickerhof wrote: > Control: -1 patch > > Hi Thomas, > > the attached patch fixes this for me, can you take care of uploading or > should I? > > Cheers Jochen Hi Jochen, Thanks for the patch, I uploaded version -3 of websockify including it. I'm not sure how this will behave with multiarch, however, obviously we already have the issue with the rebind.o file, so I don't think its more harmful than previously. Cheers, Thomas Goirand (zigo)
Processed: Bug#990359 marked as pending in websockify
Processing control commands: > tag -1 pending Bug #990359 [websockify] python3-websockify: rebind.so not found (when used in program wrapper mode) Ignoring request to alter tags of bug #990359 to the same tags previously set -- 990359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#990359: marked as pending in websockify
Control: tag -1 pending Hello, Bug #990359 in websockify reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/python/websockify/-/commit/becbe8d449d8ea05bd68224242ec80deb96c4eca [ Jochen Sprickerhof ] * Fix rebind.so not found (Closes: #990359), thanks to Mike Gabriel for the bug report, and Jochen Sprickerhof for the fix. (this message was generated automatically) -- Greetings https://bugs.debian.org/990359
Processed: Bug#990359 marked as pending in websockify
Processing control commands: > tag -1 pending Bug #990359 [websockify] python3-websockify: rebind.so not found (when used in program wrapper mode) Added tag(s) pending. -- 990359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#990359: marked as pending in websockify
Control: tag -1 pending Hello, Bug #990359 in websockify reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/python/websockify/-/commit/becbe8d449d8ea05bd68224242ec80deb96c4eca [ Jochen Sprickerhof ] * Fix rebind.so not found (Closes: #990359), thanks to Mike Gabriel for the bug report, and Jochen Sprickerhof for the fix. (this message was generated automatically) -- Greetings https://bugs.debian.org/990359
Bug#990978: pppoeconf: Fails to work with recent ppp versions (>= 2.4.9)
Package: pppoeconf Version: 1.21+nmu1 Severity: serious Hi, pppoeconf invokes ppp's `pppoe-discovery` with something like `-U -A -I $iface`, which fails hard against ppp's v2.4.9-1+1, which doesn't provide such an option `-A` any longer: | # pppoe-discovery -U -A -I eth1 | pppoe-discovery: invalid option -- 'A' | Usage: pppoe-discovery [options] | Options: |-I if_name -- Specify interface (default eth0) |-D filename-- Log debugging information in filename. |-t timeout -- Initial timeout for discovery packets in seconds |-a attempts-- Number of discovery attempts |-V -- Print version and exit. |-Q -- Quit Mode: Do not print access concentrator names |-S name-- Set desired service name. |-C name-- Set desired access concentrator name. |-U -- Use Host-Unique to allow multiple PPPoE sessions. |-W hexvalue-- Set the Host-Unique to the supplied hex string. |-h -- Print usage information. | | pppoe-discovery from pppd 2.4.9 Looking at upstream's ppp git repos, the -A option (which was anyway accepted for compatibility only with pppoe) is gone as of v2.4.9. AFAICT the fix should be as simple as dropping the "-A" option from pppoeconf. regards -mika-
