Bug#996546: jupyter notebook error "duplicate signature"

Package: python3-jupyter-client Version: 6.1.11-2 When running a jupyter notebook that spawns processes, in my case using multiprocessing.Pool.starmap(), then occasionally the notebook kernel is hit by an exception complaining about "Duplicate Signature" in zmqstreams. The bug is known upstream a

Bug#993577: Reverse dependencies

Control: tags -1 + moreinfo A few dependencies still exist: Checking reverse dependencies... # Broken Depends: bfh-metapackages: bfh-gnome-desktop progress-linux-metapackages: progress-linux-gnome-desktop

Bug#993368: Reverse dependencies

Control: tags -1 + moreinfo A dependency still exists: Checking reverse dependencies... # Broken Depends: openscap-daemon: openscap-daemon

Bug#996535: upgrading from 1.68.4-1 to 1.68.4-1+b1 breaks gnome(oh no! something has gone wrong)

Package: gjs Version: 1.68.4-1+b1 Severity: normal -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-2-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MO

Bug#996545: python3-discogs-client: Fails to get oauth access token

Package: python3-discogs-client Version: 2.3.5-2 Severity: normal Hi, Using beets' discogs plugin from sid, OAuth fails: To authenticate with Discogs, visit: https://www.discogs.com/oauth/authorize?oauth_token=REDACTED Enter the code: REDACTED discogs: connection error: Only unicode

Bug#996544: ITP: libime-jyutping -- libime to implement jyutping (粵拼) input method.

Package: wnpp Severity: wishlist Owner: Lu YaNing * Package name: libime-jyutping Version : 1.0.3 Upstream Author : Xuetian Weng * URL : https://github.com/fcitx/libime-jyutping * License : LGPL-2.1+ Programming Lang: C++

Bug#992819: Reverse dependencies

Control: tags -1 + moreinfo A few dependencies still exist: Checking reverse dependencies... # Broken Depends: kmerresistance: kmerresistance [armel armhf i386 mipsel] resfinder: resfinder virulencefinder: virulencefinder # Broken Build-Depends: resfinder-db: kma

Bug#990789: LERC compression in TIFF

Dear Laszlo, would you accept a patch for this? kind regards antonio On Wed, 7 Jul 2021 16:02:44 +0200 Antonio Valentino wrote: Package: tiff Version: 4.3.0-1 Starting form libtiff v4.3 support for the LERC compression codec has been officially integrated into libtiff. LERC is a very inter

Bug#996543: ITP: sphinx-press-theme -- responsive theme for Sphinx documentation generator

Package: wnpp Owner: Andrius Merkys Severity: wishlist Control: block 995905 by -1 X-Debbugs-CC: m...@debian.org * Package name: sphinx-press-theme Version : 0.8.0 Upstream Author : Eduardo Naufel Schettino and other contributors * URL : https://github.com/schettino72/

Bug#996541: racon: FTBFS when rebuilt against libedlib1

Package: racon Version: 1.4.21-1 Severity: serious X-Debbugs-Cc: ni...@thykier.net Hi, A new version of libedlib (with a new ABI) has been uploaded to unstable and that causes racon to fail to build from source. Relevant parts of the amd64 log: ``` > /usr/bin/cmake -E cmake_link_script CMakeFil

Bug#996542: Post install fails when run as non-root user and does not respect PKG_ROOT

Package: udev Version: 247.3-5 Probably the easiest solution would be to exit early from the post install if the current user is not root. There's probably a more subtle fix that preserves more functionality (eg. maybe updating the hwdb in PKG_ROOT?), what ever gets the post install to not fail in

Bug#996540: Post install fails when run as non-root user and does not respect PKG_ROOT

Package: install-info Version: 6.7.0.dfsg.2-6 The post install is failing when dpkg is configured with a root and run as an unprivileged user. This is an issue partly with packaging and partly with the upstream package (I think). The upstream issue can be remedied with a patch in the packaging.

Bug#996539: ITP: sqlitecpp -- a smart and easy to use C++ SQLite3 wrapper

Package: wnpp Severity: wishlist X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: sqlitecpp Version : 3.1.1-1 Upstream Author : Sébastien Rombauts * URL : https://github.com/SRombauts/SQLiteCpp * License : MIT

Bug#996534: netkit-telnet: Specifying a port in telnetrc is not working

Package: netkit-telnet Followup-For: Bug #996534 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu ubuntu-patch Dear Maintainer, *** /tmp/tmpn1vxgjaz/bug_body In Ubuntu, the attached patch was applied to achieve the following: * Description: Fix Bug-Specifying a port in telnetrc

Bug#948701: Acknowledgement (ITP: libsqlitecpp -- smart and easy to use C++ SQLite3 wrapper)

HI Eduard， I am very interested in this package and want to take over the packaging project. I will create a new ITP due to the upstream version update. Best regards, Lu

Bug#996538: gnome-software: Shows wrong type of license

Package: gnome-software Version: 41.0-1 Severity: normal Dear Maintainer, hi! I was looking, through Gnome-software, at some programs that are installed on my Debian and to my surprise I came across something a little unusual. In gnome-software when I accessed the "add-ons" option, then "codecs"

Bug#996534: netkit-telnet: Specifying a port in telnetrc is not working

Source: netkit-telnet Version: 0.17 Severity: normal Dear Maintainer, # What expected to happen - 1. Specify a port in telnetrc ( $HOME/.telnetrc) as follows * DEFAUT:8023 mode character - 2. telnet a host with specific port * telnet 192.168.1.1 8023 - The expected is that "mode c

Bug#996533: groff-message (line 1) can't set the locale; make sure $LC_* and $LANG are correct

Package: lintian Version: 2.108.0 Severity: normal X-Debbugs-Cc: atzli...@sina.com Hi, lintian tags groff-message has error report in salsa CI/CD. Please see: https://salsa.debian.org/atzlinux-guest/stardict/-/jobs/2071953 W: stardict-gtk: groff-message usr/share/man/man1/stardict.1.gz

Bug#996532: installation-reports: The brightness-control keys won't work on HP Pavilion Gaming Laptop 15-cx0076tx.

Package: installation-reports Severity: minor (Please provide enough information to help the Debian maintainers evaluate the report efficiently - e.g., by filling in the sections below.) Boot method: USB Image version: https://cdimage.debian.org/debian-cd/current/amd64/bt-dvd/ Date: Machine: HP

Bug#996531: tp-smapi-dkms: Loading thinkpad_ec and/or tp_smapi causes kernel oops

Package: tp-smapi-dkms Version: 0.43-1 Severity: important X-Debbugs-Cc: evily...@gmail.com Dear Maintainer, While working fine on kernel 5.10, starting with 5.14, when the thinkpad_ec or tp_smapi modules are loaded, a kernel oop occurs. Here's a relevant extract from kernel messages: [ 92.365

Bug#996472: nspark: Description doesn't say what it does

> On 14/10/2021 18:45 Justin B Rye wrote: > > Oh, is this another one for my collection of packages where the prefix > "n-" stands for "new thirty years ago"? Yes, I'm afraid so. > My suggestion: > > # de-archiver for !Spark archives > # > # nspark ("new spark") supports extracting files from S

Bug#996530: yard: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot load such file -- webrick

Source: yard Version: 0.9.24-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, yard was found to fail to build in that situation. To reprod

Bug#996529: vagrant: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError:

Source: vagrant Version: 2.2.14+dfsg-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, vagrant was found to fail to build in that situation.

Bug#996528: test-kitchen: FTBFS: ERROR: Test "ruby2.7" failed: Could not find 'thor' (~> 0.19) among 87 total gem(s) (Gem::MissingSpecError)

Source: test-kitchen Version: 1.23.2-5 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, test-kitchen was found to fail to build in that situa

Bug#996527: sup-mail: FTBFS: ERROR: Test "ruby2.7" failed: NameError: uninitialized constant ActiveSupport

Source: sup-mail Version: 1.0-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, sup-mail was found to fail to build in that situation. This

Bug#996526: rubygems: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.

Source: rubygems Version: 3.2.27-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, rubygems was found to fail to build in that situation. T

Bug#996525: ruby-xmlrpc: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.

Source: ruby-xmlrpc Version: 0.3.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-xmlrpc was found to fail to build in that situatio

Bug#996524: ruby-whitequark-parser: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.

Source: ruby-whitequark-parser Version: 2.7.1.4-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-whitequark-parser was found to fail t

Bug#996523: ruby-websocket: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot load such file -- webrick

Source: ruby-websocket Version: 1.2.8-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-websocket was found to fail to build in that si

Bug#996522: ruby-vips: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:

Source: ruby-vips Version: 2.0.17-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-vips was found to fail to build in that situation.

Bug#996521: ruby-vcr: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot load such file -- webrick

Source: ruby-vcr Version: 6.0.0+really5.0.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-vcr was found to fail to build in that si

Bug#996520: ruby-varia-model: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: expect(subject.to_json).to eql(JSON.dump(first_name: "brooke", nick: "leblanc"))

Source: ruby-varia-model Version: 0.6.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-varia-model was found to fail to build in tha

Bug#996519: ruby-vagrant-cloud: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:

Source: ruby-vagrant-cloud Version: 3.0.2-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-vagrant-cloud was found to fail to build in

Bug#996518: ruby-typhoeus: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: require 'rack/handler/webrick'

Source: ruby-typhoeus Version: 1.4.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-typhoeus was found to fail to build in that situ

Bug#996517: ruby-tty-command: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:

Source: ruby-tty-command Version: 0.9.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-tty-command was found to fail to build in tha

Bug#996516: ruby-toml-rb: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Segmentation fault

Source: ruby-toml-rb Version: 2.0.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-toml-rb was found to fail to build in that situat

Bug#996515: ruby-tilt: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: TypeError: no implicit conversion of Hash into String

Source: ruby-tilt Version: 2.0.10-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-tilt was found to fail to build in that situation.

Bug#996514: ruby-terrapin: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: undef_method :exitstatus

Source: ruby-terrapin Version: 0.6.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-terrapin was found to fail to build in that situ

Bug#996513: ruby-stackprof: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.

Source: ruby-stackprof Version: 0.2.15-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-stackprof was found to fail to build in that s

Bug#996512: ruby-spy: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: tried to create Proc object without a block

Source: ruby-spy Version: 0.4.3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-spy was found to fail to build in that situation. To

Bug#996511: ruby-sprockets: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 2, expected 1)

Source: ruby-sprockets Version: 3.7.2-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-sprockets was found to fail to build in that si

Bug#996510: ruby-spring: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Errno::ENOENT: No such file or directory @ rb_check_realpath_internal - /tmp/d20211005-1582813-mce9ae

Source: ruby-spring Version: 2.1.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-spring was found to fail to build in that situatio

Bug#996509: ruby-slop: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 2, expected 1)

Source: ruby-slop Version: 4.6.2-1.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-slop was found to fail to build in that situation.

Bug#996265: autopkgtest: The dependency of each test is added to the dependencies of the following tests

Hello Paul, Thanks for taking the time to look at this. > Can you please specify which backend you're using? This is *not* what > I'm seeing in the runs on ci.d.n which uses lxc. As an example, one of > my packages has Depends mariadb-server in the first test, it doesn't get > installed in the se

Bug#996508: reportbug: davmail server doesn't start

Package: davmail Version: 6.0.0.3375-2 Severity: normal Dear Maintainer, After upgrading davmail, it did not start. /usr/bin/davmail is now a jar file; it doesn't run without java. /etc/init.d/davmail start dows not give any information. (and does not start the server). I had to do: java -j

Bug#996163: tzdata: [INTL:fr] French templates translation

hi Le 13/10/2021 à 22:58, Aurelien Jarno a écrit : Hi, On 2021-10-11 18:32, Jean-Pierre Giraud wrote: Package: tzdata Severity: wishlist Tags: patch l10n Hi! Please find attached the updated french templates translation, proofread by the debian-l10n-french mailing list contributors. This fi

Bug#996507: trilinos-all-dev: No rule to make target '/usr/lib/x86_64-linux-gnu/libdl.so'

Package: trilinos-all-dev Version: 12.18.1-2 Severity: normal X-Debbugs-Cc: nico.schloe...@gmail.com Dear Maintainer, First of all, I need to say because I'm partly responsible for making this a "monster" package of packages. It really should have been a libtrilinos-dev with no subpackaging, this

Bug#996328: Additional information

bugs.debian.org: I moved the Debian 10 instance disk from the Dell Latitude E6520 laptop with Optimus graphics to a Intel DQ67SW motherboard desktop with Intel integrated graphics. The Xfce desktop issues remain. I installed a Debian 9 instance disk into the DQ67SW and ran it for several h

Bug#994833: OpenCL programs abort when intel-opencl-icd is installed

Control: tag -1 pending On 22/09/2021 15.59, Giuseppe Bilotta wrote: The virtual ABI package sounds like the best choice. I've tried to implement this in src:intel-graphics-compiler and src:intel-compute-runtime. Couldn't test the first one due to the gcc 11 ftbfs, but the second one does wh

Bug#996489: awscli: Cryptic error if awscli and boto versions mismatch

Package: awscli Version: 1.20.53-1 Severity: normal Dear Maintainer, On a system running bullseye (11.1), I wanted to install a newer version of awscli. So I added sources.list entries for testing, set APT::Default-Release "bullseye"; and then # apt-get install -t testing install awscli This

Bug#996505: cryptsetup: set CRYPTTAB_OPTION_tries for keyscripts when not explicitly set

Package: cryptsetup Version: 2:2.4.0-1 Severity: wishlist Hey. I've noted that when there is no explicit tries=n in crypttab, that CRYPTTAB_OPTION_tries isn't set either for the keyscripts. I think it might sense to actually have that set then (to it's default of 3) so that keyscripts still see

Bug#993324: libgsl25: ABI breakage: removed symbol gsl_linalg_QR_TR_decomp

On 14 October 2021 at 23:20, Sebastian Ramacher wrote: | On 2021-10-14 15:52:03 -0500, Dirk Eddelbuettel wrote: | > | > Hi Sebastian, | > | > On 14 October 2021 at 22:46, Sebastian Ramacher wrote: | > | Hi Dirk | > | | > | On 2021-08-30 16:27:49 -0500, Dirk Eddelbuettel wrote: | > | > | > | >

Bug#993324: libgsl25: ABI breakage: removed symbol gsl_linalg_QR_TR_decomp

On 2021-10-14 15:52:03 -0500, Dirk Eddelbuettel wrote: > > Hi Sebastian, > > On 14 October 2021 at 22:46, Sebastian Ramacher wrote: > | Hi Dirk > | > | On 2021-08-30 16:27:49 -0500, Dirk Eddelbuettel wrote: > | > > | > On 30 August 2021 at 23:42, Niko Tyni wrote: > | > | Package: libgsl25 > | >

Bug#980559: angelscript: FTBFS on arm64: test error

On Thu, Oct 14, 2021 at 05:46:30PM +0200, Reiner Herrmann wrote: > I was able to fix it by including arm64 in the "buggy archs" list > in debian/rules (see below). FTR I tested my change based on 2.35.1+ds-1 (not -2). signature.asc Description: PGP signature

Bug#993324: libgsl25: ABI breakage: removed symbol gsl_linalg_QR_TR_decomp

Hi Sebastian, On 14 October 2021 at 22:46, Sebastian Ramacher wrote: | Hi Dirk | | On 2021-08-30 16:27:49 -0500, Dirk Eddelbuettel wrote: | > | > On 30 August 2021 at 23:42, Niko Tyni wrote: | > | Package: libgsl25 | > | Version: 2.7+dfsg-2 | > | Control: affects -1 libmath-gsl-perl | > | Seve

Bug#993324: libgsl25: ABI breakage: removed symbol gsl_linalg_QR_TR_decomp

Hi Dirk On 2021-08-30 16:27:49 -0500, Dirk Eddelbuettel wrote: > > On 30 August 2021 at 23:42, Niko Tyni wrote: > | Package: libgsl25 > | Version: 2.7+dfsg-2 > | Control: affects -1 libmath-gsl-perl > | Severity: serious > | > | gsl 2.7 broke libmath-gsl-perl on runtime, as seen in the autopkgte

Bug#996504: ITP: oxigraph -- SPARQL server based on Oxigraph graph database

Package: wnpp Severity: wishlist Owner: Jonas Smedegaard X-Debbugs-Cc: debian-de...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: oxigraph Version : 0.2.5 Upstream Author : Tpt * URL : https://github.com/oxigraph/oxigraph * License

Bug#996503: sddm fails to start

Package: sddm Version: 0.19.0-3 Severity: important X-Debbugs-Cc: debian...@brinin.org Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** Noticed since upgrade of nvidia-driver v.470.74-1. SDDM crashes, cannot login as usual. Messages in /var/log/mess

Bug#996490: audacious-plugins: cannot install last binNMU 4.0.5-1+b1

Control: severity -1 serious On 2021-10-14 20:46:53, Patrice Duroux wrote: > Package: audacious-plugins > Version: 4.0.5-1 > Severity: normal > > Dear Maintainer, > > Its dependency 'audacious-plugins-data' does not have an identical version > tag. > I am not sure if this is related to: > https

Bug#996502: RM: networking-arista -- ROM; unmaintained upstream

Package: ftp.debian.org Severity: normal Hi, This Neutron plugin is unmaintained upstream (and in Debian). Please remove this package from Debian. Cheers, Thomas Goirand (zigo)

Bug#982998: chkrootkit chkproc uses incorrect value for max_pid

Package: chkrootkit Version: 0.55-1+b1 Followup-For: Bug #982998 X-Debbugs-Cc: report...@duvert.net Hello, I also have the same problem. Looking at the extracted source package, I noticed that the MAX_PROCESSES 9 define actually comes from the Debian patch debian/patches/27_fix-race-condition

Bug#994911: error modifying deb822 object while iterating

On Sun, Oct 10, 2021 at 08:41:55AM +0200, Niels Thykier wrote: > On Thu, 23 Sep 2021 00:43:50 + Jelmer Vernooij > wrote: > > Package: python3-debian > > Version: 0.1.41 > > Severity: normal > > > > Modifying a deb822 file while iterating over it results in a RuntimeError: > > > > ... > > F

Bug#996501: systemd FTCBFS: unsatisfiable Build-Depends: python3-jinja2

Source: systemd Version: 249.5-1 Severity: important Justification: breaks architecture bootstrap Tags: patch User: helm...@debian.org Usertags: rebootstrap User: debian-cr...@lists.debian.org Usertags: cross-satisfiability systemd can no longer be cross built from source, because it gained a buil

Bug#996500: wlroots FTBFS: error: ‘av_init_packet’ is deprecated [-Werror=deprecated-declarations]

Source: wlroots Version: 0.12.0-2 Severity: serious Tags: ftbfs wlroots fails to build from source in unstable on amd64. A non-parallel build now ends as follows: | FAILED: examples/dmabuf-capture.p/dmabuf-capture.c.o | cc -Iexamples/dmabuf-capture.p -Iexamples -I../examples -Iprotocol -I/usr/in

Bug#996498: ocp FTCBFS: multiple reasons

Source: ocp Version: 1:0.2.90-3.1 Tags: patch upstream User: debian-cr...@lists.debian.org Usertags: ftcbfs ocp fails to cross build from source, because configure.ac hard codes the build architecture pkg-config in a lot of occasions. A good solution is using the PKG_CHECK_MODULES macro. I'm attac

Bug#996499: jdim FTCBFS: exports DEB_BUILD_OPTIONS

Source: jdim Version: 0.6.0-1 Tags: patch User: debian-cr...@lists.debian.org Usertags: ftcbfs jdim fails to cross build from source, because it fails running tests despite being passed DEB_BUILD_OPTIONS=nocheck. That variable is ignored, because debian/rules sets it. Please drop that. Helmut dif

Bug#996497: u-boot FTCBFS: missing build dependency on libssl-dev

Source: u-boot Version: 2021.10+dfsg-1 Tags: patch User: debian-cr...@lists.debian.org Usertags: ftcbfs u-boot fails to cross build from source, because it misses a build dependency on libssl-dev. Please add it. Helmut diff --minimal -Nru u-boot-2021.10+dfsg/debian/changelog u-boot-2021.10+dfsg/

Bug#996496: src:golang-gopkg-square-go-jose.v1: fails to migrate to testing for too long: uploader built arch:all binary

Source: golang-gopkg-square-go-jose.v1 Version: 1.1.2-2 Severity: serious Control: close -1 1.1.2-3 X-Debbugs-CC: jel...@debian.org Tags: sid bookworm pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of

Bug#996495: bash-completion: [regression from buster] tab no longer completes filenames in some cases

Package: bash-completion Version: 1:2.11-2 Severity: normal X-Debbugs-Cc: timo.lindf...@iki.fi I'm not quite sure what is the right package for this report, please feel free to reassign/retitle when needed. Steps to reproduce: 1) Install vanilla Debian 11 from netinst CD 2) Login and start gnome

Bug#996040: Acknowledgement (qml-module-qtpositioning: Bogus Altitude, Direction and Speed values with geoclue2 backend)

Control: tags -1 patch A simple fix, once it's seen. As a bonus, fix the invalid altitude detection. >From f83eb0b27b0e9458a371b725a8e360ef4230cc8a Mon Sep 17 00:00:00 2001 From: Teemu Ikonen Date: Thu, 14 Oct 2021 21:22:23 +0300 Subject: [PATCH 1/2] Fix assignment vs. comparison precedence e

Bug#996494: unbound in bullseye fails to start under systemd - issue already fixed in unbound upstream

Package: unbound Version: 1.13.1-1 After upgrading to bullseye from buster (unbound v1.9.0-2+deb10u2), unbound fails to start via systemd, but starts and runs fine when daemon is started directly. There is an upstream fix (to unbound, not systemd) for this issue: https://github.com/NLnetLabs

Bug#996177: cryptsetup: please report fatal errors without having to use -v

On Thu, 14 Oct 2021 at 20:48:51 +0200, Marc Lehmann wrote: > I reported this from another system, but both were recently upgraded to > bullseye. > > I know because I use kvm to see if the machine will actually boot (Cthus > the different memory setup) and the kvm in bullseye has a bug that makes >

Bug#996493: src:golang-github-getlantern-hidden: fails to migrate to testing for too long: uploader built arch:all binary

Source: golang-github-getlantern-hidden Version: 0.0~git20190325.f02dbb0-2 Severity: serious Control: close -1 0.0~git20190325.f02dbb0-3 X-Debbugs-CC: jel...@debian.org Tags: sid bookworm pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Te

Bug#996492: O: mpack -- tools for encoding/decoding MIME messages

Package: wnpp Severity: normal X-Debbugs-Cc: ftob...@debian.org Control: affects -1 src:mpack I intend to orphan the mpack package. The package description is: Mpack and munpack are utilities for encoding and decoding (respectively) binary files in MIME (Multipurpose Internet Mail Extensions)

Bug#996491: src:gnome-authenticator: fails to migrate to testing for too long: uploader built arch:all

Source: gnome-authenticator Version: 3.32.2+dfsg1-2 Severity: serious Control: close -1 3.32.2+dfsg1-3 X-Debbugs-CC: jel...@debian.org Tags: sid bookworm pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out

Bug#996265: autopkgtest: The dependency of each test is added to the dependencies of the following tests

Control: tags -1 moreinfo Hi Fab, On 12-10-2021 20:04, Fab Stz wrote: > I noticed that the dependency of each test is added to the dependencies of the > following tests > > For example: debian/tests/control contains: > > Test-Command: /usr/lib/android-sdk/build-tools/19.1.0/aapt v > Depends: go

Bug#996177: cryptsetup: please report fatal errors without having to use -v

On Tue, Oct 12, 2021 at 02:25:31AM +0200, Guilhem Moulin wrote: > > Also did you run luksFormat on that same machine (and didn't remove > > memory sticks afterwards)? > > I was actually able to reproduce this with buster's 2.1.0, but doing the > same thing after upgrading to bullseye or sid yiel

Bug#996490: audacious-plugins: cannot install last binNMU 4.0.5-1+b1

Package: audacious-plugins Version: 4.0.5-1 Severity: normal Dear Maintainer, Its dependency 'audacious-plugins-data' does not have an identical version tag. I am not sure if this is related to: https://salsa.debian.org/multimedia-team/audacious- plugins/-/commit/7243b8f6e361af34a09cb169726b7178a

Bug#996443: src:units-filter: fails to migrate to testing for too long: FTBFS

Hi Georges, On 14-10-2021 17:43, Georges Khaznadar wrote: > If I upload another package, without the new features (and the new > binary artifact), is there a chance that it will be taken in > consideration by the build system ? I fear that it would compete with > the other package in the NEW queue

Bug#996177: cryptsetup: please report fatal errors without having to use -v

On Thu, 14 Oct 2021 at 19:53:14 +0200, Marc Lehmann wrote: > On Tue, Oct 12, 2021 at 12:33:32AM +0200, Guilhem Moulin > wrote: >> Could you please share the memory cost of the PBKDF, > > I wouldn't know how to do that. `cryptsetup luksDump` >> of `free` just before running cryptsetup? That w

Bug#996488: ITP: transforms3d -- Python code to convert between various geometric transformations

Package: wnpp Severity: wishlist Owner: Jose Luis Rivero X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: transforms3d Version : 0.3.1 Upstream Author : Matthew Brett and Christoph Gohlke * URL : https://github.com/matthew-brett/transforms3d.git * License

Bug#995202: horst FTBFS: error: format not a string literal and no format arguments

Control: tags -1 + patch Am 27.09.2021 um 22:25 schrieb Helmut Grohne: > Source: horst > Version: 5.1-2 > Severity: serious > Tags: ftbfs > > horst fails to build from source in unstable on amd64 due to ncurses > having become stricter about format strings. A build now ends as > follows: > > | cc

Bug#996177: cryptsetup: please report fatal errors without having to use -v

On Tue, Oct 12, 2021 at 12:33:32AM +0200, Guilhem Moulin wrote: > Could you please share the memory cost of the PBKDF, I wouldn't know how to do that. > of `free` just before running cryptsetup? That would help us trying to > reproduce this and forward the issue upstream. I tried to reproduce

Bug#994423: pytorch-vision: FTBFS on armhf: Illegal instruction

Control: reassign -1 src:pytorch 1.7.1-7 Control: retitle -1 pytorch: Baseline violation on armhf Control: affects -1 python3-torch src:pytorch-vision On Wed, Sep 15, 2021 at 10:00:09PM +0200, Sebastian Ramacher wrote: > Source: pytorch-vision > Version: 0.8.2-1 > Severity: serious > Tags: ftbfs s

Bug#996487: nbd-client: connects to localhost instead of the requested server

Package: nbd-client Version: 1:3.22-1 Severity: important Hi! Since a few days ago (ie, since 1:3.22-1 upload), nbd-client stopped working for me. stracing it shows: [pid 4166] socket(AF_INET6, SOCK_DGRAM|SOCK_CLOEXEC, IPPROTO_IP) = 3 [pid 4166] connect(3, {sa_family=AF_INET6, sin6_port=htons(

Bug#995624: pktstat FTBFS: error: format not a string literal and no format arguments [-Werror=format-security]

Control: tags -1 + patch Am 03.10.2021 um 12:00 schrieb Helmut Grohne: > Source: pktstat > Version: 1.8.5-7 > Severity: serious > Tags: ftbfs > > pktstat fails to build from source in unstable on amd64. A non-parallel > build ends as follows: > > | gcc -DHAVE_CONFIG_H -I. -DPATH_PKTSTATRC=\"/etc

Bug#993201: fixed in upstream pull request

I fixed it and created a pull request upstream: https://gitlab.com/bertoldia/gnome-shell-trash-extension/-/merge_requests/23

Bug#992116: release-notes: Add breakage from merged-/usr-via-aliased-dirs

Paul Gevers wrote: > On 23-09-2021 21:25, Paul Gevers wrote: >> "The Debian project is still deciding how to do this and how to migrate >> existing systems as the proper solution isn't known yet." Yes, highly >> frustrating, but it is reality. >> >> For reference: >> https://salsa.debian.org/debia

Bug#996472: nspark: Description doesn't say what it does

Simon McVittie wrote: > Package: nspark > Version: 1.7.8B2+git20210317.cb30779-1 > Severity: normal > X-Debbugs-Cc: debian-l10n-engl...@lists.debian.org Well, it reached me, but the BTS etc. don't seem to be sure whether the package exists... # A rewritten version of RISC OS !Spark for UNIX # # n

Bug#996028: [debian-mysql] Bug#996028: #996028 InnoDB: corrupted TRX_NO after upgrading to 10.3.31

e46f76c9749d7758765ba274a212cfc2dcf3eeb8 is the first bad commit commit e46f76c9749d7758765ba274a212cfc2dcf3eeb8 Author: Marko Mäkelä Date: Mon Jun 21 12:34:07 2021 +0300 MDEV-15912: Remove traces of insert_undo Let us simply refuse an upgrade from earlier versions if the upgrade p

Bug#996486: bitcoind: fails to start with undefined symbol: _ZTIN7leveldb6LoggerE

Control: reassign -1 libleveldb1d Control: affects -1 bitcoind Quoting Vincas Dargis (2021-10-14 19:16:00) > Package: bitcoind > Version: 22.0-1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > Since 2021-10-12 bitcoind fails to start on my machine: > > ``` >

Bug#995423: libyaml-cpp-dev: Incorrect include PATH in CMake configuration script.

Hello Tomasz On Fri, 01 Oct 2021 00:04:51 +0200 Tomasz Wolak wrote: > Package: libyaml-cpp-dev > Version: 0.6.3-9 > Severity: normal > X-Debbugs-Cc: tomas.wo...@gmail.com > > One of the package config files for CMake: > > /usr/lib/x86_64-linux-gnu/cmake/yaml-cpp/yaml-cpp-config.cmake > > conta

Bug#996486: bitcoind: fails to start with undefined symbol: _ZTIN7leveldb6LoggerE

Package: bitcoind Version: 22.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, Since 2021-10-12 bitcoind fails to start on my machine: ``` # fgrep leveldb /var/log/syslog Oct 12 20:00:34 vinco bitcoind[1103]: /usr/bin/bitcoind: symbol lookup error: /usr/bin/bitcoind:

Bug#954215: pybuild: Should do better than a traceback if cmake is not found

On Wed, 18 Mar 2020 13:26:56 -0400 Scott Kitterman wrote: Pybuild should catch the error and if needed print something useful. I don't know that this needs anything though. If a package uses cmake and it's not there, it'll eventually blow up the build anyway. I don't thnk pybuild needs to cal

Bug#996485: pytools: please package 2021.2.7 or later, needed by pyopencl

Source: pytools Version: 2021.1-2 Severity: important Tags: sid bookworm Control: affects -1 + src:pyopencl Hi, whily trying to upgrade pyopencl to its latest release I noticed that it has bumped the dependency on pytools to >= 2021.2.7. (And it actually uses some of the new features.) Please pa

Bug#996484: Doesn not starts

Package: pushover Version: 0.0.5+git20180909-4+b2 Severity: important X-Debbugs-Cc: pi...@debian.org Hello, while trying to play with pushover, I got this message $ pushover Using portable datadir: ./data File not found: ./data/pushover/images/dominoes.png File not found: ./data/pushover/images/

Bug#995066: [debian-mysql] Bug#995066: mariadb-server: Incorrect warning about corrupt tables on mysql start

Otto Kekäläinen писал 2021-09-25 22:04: Thanks for the report and patch! Would you want to submit it as a MR at https://salsa.debian.org/mariadb-team/mariadb-10.5 ? The problem can be fixed by adding default-character-set = utf8mb4 to the [client] section of /etc/mysql/debian.cnf. Consider

Bug#961129: xscreensaver should not search for screensaver executables in PATH

You could solve this problem with a one-line change: simply make "xscreensaver" depend upon "xscreensaver-data", "xscreensaver-data-extra", "xscreensaver-gl", "xscreensaver-gl-extra", "xscreensaver-screensaver-bsod" and "xscreensaver-screensaver-webcollage". I can see the argument for allowing

Bug#996389: [debian-mysql] Bug#996389: mariadb-server: FATAL ERROR: Upgrade failed

Otto Kekäläinen писал 2021-10-14 04:55: Hello! This is not a duplicate of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995066, right? Does the same fix (https://salsa.debian.org/mariadb-team/mariadb-10.5/-/merge_requests/11) however apply to this too? This is not a duplicate of https://b

Bug#996470: motion terminates directly after startup when run as service from systemd

Package: motion Version: 4.3.2-1 Severity: important Dear Maintainer, after migration of motion settings to a fresh setup of Raspbian 11, the motion process terminates directly after startup without any error message. Without any changes to config files, running the command motion -b -p /var/r

  1   2   >