Processed: tagging 1017467, tagging 998361, tagging 1012688
Processing commands for cont...@bugs.debian.org: > tags 1017467 + pending Bug #1017467 [pam] libpam-systemd: upgrade broke unix_chkpwd fallback for root user Added tag(s) pending. > tags 998361 + pending Bug #998361 [src:pam] pam FTBFS Added tag(s) pending. > tags 1012688 + pending Bug #1012688 [src:pam] libpam0-dev: Provide pkgconfig files (new upstream available) Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1012688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012688 1017467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017467 998361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998361 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017375: marked as done (liblexical-accessor-perl: test failure with Sub::HandlesVia 0.034)
Your message dated Thu, 18 Aug 2022 05:35:16 +
with message-id
and subject line Bug#1017375: fixed in liblexical-accessor-perl 0.014-2
has caused the Debian Bug report #1017375,
regarding liblexical-accessor-perl: test failure with Sub::HandlesVia 0.034
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.)
--
1017375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017375
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liblexical-accessor-perl
Version: 0.014-1
Severity: serious
Tags: upstream ftbfs
Justification: fails to build from source (but built successfully in the past)
t/30shv.t fails with:
Usage: Sub::HandlesVia::CodeGenerator::method_installer(self) at
.../lib/Sub/HandlesVia/Toolkit/SubAccessorSmall.pm line 58.
In version 0.034, Sub::HandlesVia::CodeGenerator's method_installer field
is read-only and the above line tries to modify it:
$gen->method_installer( sub {
my ( $method_name, $coderef ) = @_;
my $real_destination = $handles_map->{$method_name};
$realattr->install_coderef( $real_destination, $coderef );
} );
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable'),
(500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.18.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: liblexical-accessor-perl
Source-Version: 0.014-2
Done: Damyan Ivanov
We believe that the bug you reported is fixed in the latest version of
liblexical-accessor-perl, 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 1017...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Damyan Ivanov (supplier of updated liblexical-accessor-perl
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, 18 Aug 2022 05:25:44 +
Source: liblexical-accessor-perl
Built-For-Profiles: nocheck
Architecture: source
Version: 0.014-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group
Changed-By: Damyan Ivanov
Closes: 1017375
Changes:
liblexical-accessor-perl (0.014-2) unstable; urgency=medium
.
* Team upload
.
* bump (build-) dependency on libsub-handlesvia-perl to 0.035 fixing FTBFS
(Closes: #1017375)
Checksums-Sha1:
e98589ed13223554bd9e1c67a0a3acc2a337a384 2473
liblexical-accessor-perl_0.014-2.dsc
89f1fce4ac79a3b325d2b677e3a3f01edc10c4a9 4404
liblexical-accessor-perl_0.014-2.debian.tar.xz
Checksums-Sha256:
2162679ab7a9adae27b514ed00ff9d5103c204953fbe168ac08c74501d14ed15 2473
liblexical-accessor-perl_0.014-2.dsc
04892571311b6aee8e75998013f0d4e215e0990b2d38bc686c24cef069a76a90 4404
liblexical-accessor-perl_0.014-2.debian.tar.xz
Files:
304f9a88486a17889f851d93182d2d50 2473 perl optional
liblexical-accessor-perl_0.014-2.dsc
6266a4d7728c5363e0c9509707dff6c5 4404 perl optional
liblexical-accessor-perl_0.014-2.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEErqDETssFbpNjDZ0z276dTZnSoAQFAmL9zecACgkQ276dTZnS
oATxbRAAnplYnLXQiGxsr7MAYZWMxIRd/sRsb7fPr9FoxxGWUSWC5IE1ImV1zfYN
SUfy5i0oVCeqrBkU7j0zhlix/lF6YJEhcPrHb82MxTXJsOHJXm0j9yq5FaZAN5Mu
iEiSIlRz9TEtxmrsUiMiLIXrh1mY6uPVgZg+2I8XKS81ZdUfK6/yaANRrotURanp
ZD1w3ySCk2EmbsTgRWpWIjUeLlo/ZcoaATU/V7wiwuXvB+R1hBY0coqbO0YpC+/A
SJCfCVnKZrHy3YTGh6DQPYg41fRfemCBN2zYZrAy7JH+ixBfVetx+wXT+18/nD5I
+nGuHXvO3TUpZyQqeLkWxYW1HZkmKXBkoL4HHjjL5mLWLYH5zW6H2v2i/yXWSOOz
vcTB0hw19P6L4DQ38TCw8EDAd1kxZ3Ik0rfSbFD3F2Kar0+Jb/pzFC0Q9MENVTyY
fs21WYuYGspSGNIHryed8nI3lM1pcqbIwostuwEkxiYYcT1a7GuAQcTyShmEjQyP
33KdlDsZLCoGf+2FZzWHehB0YOA/FqQgBDKCSTf7w5HbOVZaCRINCJJv4fds/XN2
wL2e6qAce2Olo8Tcz0Zz8acDHSuCLVutQIYRdJiu+xyr7Ivgbphf8Kgj6sEVJkvc
b3aPaoK0zPMcfIaYnnuN22OrIdJ94ZZYEFrjkOakcx28zzD/uBs=
=ASSO
-END PGP SIGNATURE End Message ---
Bug#1017375: marked as pending in liblexical-accessor-perl
Control: tag -1 pending Hello, Bug #1017375 in liblexical-accessor-perl 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/perl-team/modules/packages/liblexical-accessor-perl/-/commit/5a60e0b880a38a2bade2d052b3941178bd56d254 bump (build-) dependency on libsub-handlesvia-perl to 0.035 fixing FTBFS Closes: #1017375 (this message was generated automatically) -- Greetings https://bugs.debian.org/1017375
Bug#1017375: liblexical-accessor-perl: test failure with Sub::HandlesVia 0.034
-=| gregor herrmann, 17.08.2022 17:59:41 +0200 |=- > This should be fixed with libsub-handlesvia-perl 0.035, judging from > the following upstream commit: > … > Also Changes say: > - Sub::HandlesVia::CodeGenerator method_installer is now a rw attribute as >Sub::Accessor::Small was relying on that. > > > I'm going to upload libsub-handlesvia-perl now, then we can depend on > the fixed version to close this bug, I guess? build-time and run-time dependency version bumped, all tests pass, so uploaded. Thank you for the investigation. -- Damyan
Processed: Bug#1017375 marked as pending in liblexical-accessor-perl
Processing control commands: > tag -1 pending Bug #1017375 [liblexical-accessor-perl] liblexical-accessor-perl: test failure with Sub::HandlesVia 0.034 Added tag(s) pending. -- 1017375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017375 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017591: libkf5service5: missing symbols in library
Package: libkf5service5 Version: 5.97.0-1 Severity: grave Justification: renders package unusable /usr/bin/startplasma-x11: symbol lookup error: /usr/lib/x86_64-linux-gnu/libKF5Service.so.5: undefined symbol: _ZN8KSandbox9isFlatpakEv -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C, LC_CTYPE=en_US.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 libkf5service5 depends on: ii libc6 2.34-4 ii libkf5configcore5 5.97.0-1 ii libkf5coreaddons5 5.97.0-1 ii libkf5dbusaddons5 5.97.0-1 ii libkf5i18n5 5.97.0-1 ii libkf5service-data 5.97.0-1 ii libqt5core5a5.15.4+dfsg-5 ii libqt5dbus5 5.15.4+dfsg-5 ii libqt5xml5 5.15.4+dfsg-5 ii libstdc++6 12.1.0-8 Versions of packages libkf5service5 recommends: ii libkf5service-bin 5.97.0-1 libkf5service5 suggests no packages. -- no debconf information
Processed: retitle 1017579 to freeciv: CVE-2022-6083: Modpack Installer buffer overflow
Processing commands for cont...@bugs.debian.org: > retitle 1017579 freeciv: CVE-2022-6083: Modpack Installer buffer overflow Bug #1017579 [src:freeciv] Freeciv < 2.6.7, freeciv-3.0 < 3.0.3, Modpack Installer buffer overflow Changed Bug title to 'freeciv: CVE-2022-6083: Modpack Installer buffer overflow' from 'Freeciv < 2.6.7, freeciv-3.0 < 3.0.3, Modpack Installer buffer overflow'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1017579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017579 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965820: marked as done (slack: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Thu, 18 Aug 2022 04:04:51 + with message-id and subject line Bug#965820: fixed in slack 1:0.15.2-10 has caused the Debian Bug report #965820, regarding slack: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965820 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: slack Version: 1:0.15.2-9 Severity: normal Usertags: compat-5-6-removal Hi, The package slack uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: slack Source-Version: 1:0.15.2-10 Done: Andrew Pollock We believe that the bug you reported is fixed in the latest version of slack, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrew Pollock (supplier of updated slack 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, 18 Aug 2022 12:57:55 +1000 Source: slack Binary: slack Architecture: source all Version: 1:0.15.2-10 Distribution: unstable Urgency: medium Maintainer: Andrew Pollock Changed-By: Andrew Pollock Description: slack - configuration management program for lazy admins Closes: 965820 Changes: slack (1:0.15.2-10) unstable; urgency=medium . * debian/compat: bump to 13 (closes: #965820) * debian/control: bump build-dep on debhelper accordingly * debian/control: bump standards-version * debian/rules: avoid parallel building due odd behaviours invoking the tests Checksums-Sha1: 25df3193c0d36d566f43c06ac143d6bcc1888269 1658 slack_0.15.2-10.dsc f5812d7b8f2be93ccfcadb7f0680e3c0055148ed 4348 slack_0.15.2-10.debian.tar.xz 7a39c574a6e8a9284d56cf92275774405dff 35668 slack_0.15.2-10_all.deb 69bc755d257f2a49a1e60396231a1371e9ed6ca2 6566 slack_0.15.2-10_amd64.buildinfo Checksums-Sha256: acc008fe62ed11b1ce5c8e353d6621debb5508d685586bb3a6114fe174d25070 1658 slack_0.15.2-10.dsc 0960e1b3f9dd0976e099c93accffe1e9c08ffe2f7d2baa8425b68f213bbb01f2 4348 slack_0.15.2-10.debian.tar.xz 7a1cb573de189542c8181e20e8fde95f63b11300f449b2ef896c8ba956ba77f9 35668 slack_0.15.2-10_all.deb 51116b8ee62e443a0a927ee1a6d73fca6dda1dae796f2a10582a5523882cec09 6566 slack_0.15.2-10_amd64.buildinfo Files: 0d128fa0cccaeefab1b90eb56cad75e3 1658 admin optional slack_0.15.2-10.dsc 9a42b25efd1e0a57c2772a682c4e5126 4348 admin optional slack_0.15.2-10.debian.tar.xz cbff7847bdd709169b8dc74a883aa4c5 35668 admin optional slack_0.15.2-10_all.deb fa61d974d60bea4fe9880f2d50b02776 6566 admin optional slack_0.15.2-10_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEW3Akls+mpQcjnC15Ud/ZOz77ee8FAmL9sMwACgkQUd/ZOz77 ee/axA/+L+FaIbEoMaS6b1H9Y7bBCIngWIaWJT3xN0NuMG3p64kUu2G+ABTtY4qy 5P+ba+Rny8DFIJf5U8hZqiEKeZZNl08xa1fgbUPQwuj5sILdloWAizVCSpLWM5aa +yiQewEAZiiY4/IAH4qGq/AfLkqag6GNhU439zvGaVnjwUQa15lW84sws7wEiWU8 w5zZ7F0kQDfDpMDPRd6eD4q+XwlVwLoBM/D70MASOhiSuDvrwDeTecWlrzFKaufO DK4dXd8H7ffqEIi0EfLNd2uJDiBILI7YH3aYyRb8SH0Rh0p9fBihkaONxgSuNylb
Bug#1017585: lime FTBFS: Missing build dependency on javahelper
Source: lime Version: 5.0.37+dfsg-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=lime=5.0.37%2Bdfsg-1 ... debian/rules clean dh clean --with javahelper dh: error: unable to load addon javahelper: Can't locate Debian/Debhelper/Sequence/javahelper.pm in @INC (you may need to install the Debian::Debhelper::Sequence::javahelper module) (@INC contains: /etc/perl /usr/local/lib/arm-linux-gnueabi/perl/5.34.0 /usr/local/share/perl/5.34.0 /usr/lib/arm-linux-gnueabi/perl5/5.34 /usr/share/perl5 /usr/lib/arm-linux-gnueabi/perl-base /usr/lib/arm-linux-gnueabi/perl/5.34 /usr/share/perl/5.34 /usr/local/lib/site_perl) at (eval 12) line 1. BEGIN failed--compilation aborted at (eval 12) line 1. make: *** [debian/rules:24: clean] Error 25
Bug#1017538: dietlibc: FTBFS on armhf: selected processor does not support vldm in ARM mode
On Thu, Aug 18, 2022 at 12:13 AM Thorsten Glaser wrote: > > Arnd Bergmann dixit: > > >The way the FPU type gets selected in gcc changed with recent versions, > >this was intentional and won't be reverted but it did break packages that > >used the old method. > > Hmph. > > >In most cases, it's sufficient to pass > >-march=armv7-a+fp instead of -march=armv7-a to pick the right > >instruction set. > > There’s no “instead of”, though. > > So basically, I now need to add -march=… to CFLAGS in the package > when compiling for either of armel and armhf. What I see with gcc-12-arm-linux-gnueabihf 12.1.0-8cross1 is that it defaults to the correct architecture level (armv7-a+fp) and passes that to the assembler, so it /should/ not be necessary do this explictily. The problem with other packages was that they did pass "-march=armv7-a" for armhf, but that is interpreted as not having an FPU now, where on older compilers the -mhard-float flag would override the -march= flag and enable support for an FPU regardless. > Which value do I use for armel, which for armhf (the one you gave > is for armhf, I think)? That should be -march=armv5te Arnd
Bug#1015084: marked as done (ruby-rubame: FTBFS: ERROR: Test "ruby3.0" failed: Failure/Error: pairs = client.recvfrom(20000))
Your message dated Wed, 17 Aug 2022 22:53:34 +
with message-id
and subject line Bug#1015084: fixed in ruby-rubame 0.0.3~git20131224.f3c78ba-3
has caused the Debian Bug report #1015084,
regarding ruby-rubame: FTBFS: ERROR: Test "ruby3.0" failed: Failure/Error:
pairs = client.recvfrom(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.)
--
1015084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015084
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-rubame
Version: 0.0.3~git20131224.f3c78ba-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220716 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> Failure/Error: pairs = client.recvfrom(2)
>
> IOError:
>recv for buffered IO
> # ./spec/rubame_spec.rb:97:in `recvfrom'
> # ./spec/rubame_spec.rb:97:in `block (3 levels) in '
> # ./spec/rubame_spec.rb:96:in `each'
> # ./spec/rubame_spec.rb:96:in `block (2 levels) in '
>
> Deprecation Warnings:
>
> Using `should` from rspec-expectations' old `:should` syntax without
> explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or
> explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax =
> :should }` instead. Called from /<>/spec/rubame_spec.rb:6:in
> `block (2 levels) in '.
>
>
> If you need more of the backtrace for any of these deprecations to
> identify where to make the necessary changes, you can configure
> `config.raise_errors_for_deprecations!`, and it will turn the
> deprecation warnings into errors, giving you the full backtrace.
>
> 1 deprecation warning total
>
> Finished in 0.69634 seconds (files took 0.16716 seconds to load)
> 4 examples, 1 failure
>
> Failed examples:
>
> rspec ./spec/rubame_spec.rb:62 # Rubame::Server should be able to send a
> message to a client
>
> /usr/bin/ruby3.0
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.0" failed:
The full build log is available from:
http://qa-logs.debian.net/2022/07/16/ruby-rubame_0.0.3~git20131224.f3c78ba-2_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220716=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: ruby-rubame
Source-Version: 0.0.3~git20131224.f3c78ba-3
Done: Valentin Vidic
We believe that the bug you reported is fixed in the latest version of
ruby-rubame, 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 1015...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Valentin Vidic (supplier of updated ruby-rubame 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: Wed, 17 Aug 2022 23:48:09 +0200
Source: ruby-rubame
Architecture: source
Version: 0.0.3~git20131224.f3c78ba-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
Changed-By: Valentin Vidic
Closes: 1015084
Changes:
ruby-rubame (0.0.3~git20131224.f3c78ba-3) unstable; urgency=medium
.
[ Debian Janitor ]
* Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
Repository-Browse.
* Remove constraints unnecessary since buster:
+ Build-Depends: Drop versioned constraint on ruby-websocket.
Bug#1017579: Freeciv < 2.6.7, freeciv-3.0 < 3.0.3, Modpack Installer buffer overflow
Source: freeciv Version: 2.6.6-1 Severity: grave Tags: security X-Debbugs-Cc: Debian Security Team Quoting from the announcement posted to oss-security (no CVE is available): -- Just released freeciv-2.6.7 & freeciv-3.0.3 fix buffer overflow in Modpack Installer utility's handling of the modpack URL. Specially crafted URLs, without any '/' -characters would result in an underflowing length (unsigned)(-1) string copy, i.e., all of the NULL-terminated string given as "URL" would get written beyond the buffer reserved for it. Freeciv source tarballs are available from https://www.freeciv.org/download.html for current 3.0, and from https://www.freeciv.org/wiki/Old_downloads for 2.6. In case you can't make full version update at the moment, bug tracker ticket has also a patch for this single issue attached: https://osdn.net/projects/freeciv/ticket/45299 --
Bug#1017538: dietlibc: FTBFS on armhf: selected processor does not support vldm in ARM mode
Arnd Bergmann dixit: >The way the FPU type gets selected in gcc changed with recent versions, >this was intentional and won't be reverted but it did break packages that >used the old method. Hmph. >In most cases, it's sufficient to pass >-march=armv7-a+fp instead of -march=armv7-a to pick the right >instruction set. There’s no “instead of”, though. So basically, I now need to add -march=… to CFLAGS in the package when compiling for either of armel and armhf. Which value do I use for armel, which for armhf (the one you gave is for armhf, I think)? bye, //mirabilos -- 22:20⎜ The crazy that persists in his craziness becomes a master 22:21⎜ And the distance between the craziness and geniality is only measured by the success 18:35⎜ "Psychotics are consistently inconsistent. The essence of sanity is to be inconsistently inconsistent
Processed: severity of 1017546 is important
Processing commands for cont...@bugs.debian.org: > severity 1017546 important Bug #1017546 [src:golang-github-vbatts-tar-split] golang-github-vbatts-tar-split: FTBFS on mips64el Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1017546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017546 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1012901: marked as done (belle-sip: ftbfs with GCC-12)
Your message dated Wed, 17 Aug 2022 21:49:10 +
with message-id
and subject line Bug#1012901: fixed in belle-sip 5.0.37+dfsg-2
has caused the Debian Bug report #1012901,
regarding belle-sip: ftbfs with GCC-12
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.)
--
1012901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012901
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:belle-sip
Version: 4.4.21+dfsg-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12
[This bug is targeted to the upcoming bookworm release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The
severity of this report will be raised before the bookworm release.
The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/belle-sip_4.4.21+dfsg-1_unstable_gcc12.log
The last lines of the build log are at the end of this report.
To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html
GCC 11 defaults to the GNU++17 standard. If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.
[...]
41 |
obj->timer_K=belle_sip_timeout_source_new((belle_sip_source_func_t)nict_on_timer_K,obj,cfg->T4);
| ^
/<>/src/nict.c: In function ‘nict_send_request’:
/<>/src/nict.c:144:51: warning: cast between incompatible function
types from ‘int (*)(belle_sip_nict_t *)’ {aka ‘int (*)(struct belle_sip_nict
*)’} to ‘int (*)(void *, unsigned int)’ [-Wcast-function-type]
144 |
obj->timer_F=belle_sip_timeout_source_new((belle_sip_source_func_t)nict_on_timer_F,obj,cfg->T1*64);
| ^
/<>/src/nict.c:149:59: warning: cast between incompatible function
types from ‘int (*)(belle_sip_nict_t *)’ {aka ‘int (*)(struct belle_sip_nict
*)’} to ‘int (*)(void *, unsigned int)’ [-Wcast-function-type]
149 |
obj->timer_E=belle_sip_timeout_source_new((belle_sip_source_func_t)nict_on_timer_E,obj,cfg->T1);
| ^
[ 29%] Building C object src/CMakeFiles/bellesip.dir/nist.c.o
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cc
-DBCTBX_LOG_DOMAIN=\"belle-sip\" -DBCTBX_STATIC -DBELLESIP_EXPORTS
-DBELLESIP_STATIC -DHAVE_CONFIG_H -Dbellesip_EXPORTS -I/<>/include
-I/<>/src -I/<>/obj-x86_64-linux-gnu
-I/<>/obj-x86_64-linux-gnu/src -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -std=gnu99 -Wall
-Wuninitialized -Wno-error=deprecated-declarations -Wno-error=pragmas -Werror
-Wextra -Wno-unused-parameter -Wno-error=unknown-pragmas -fno-strict-aliasing
-Werror=vla -Wno-error=cast-function-type -Wno-missing-field-initializers
-Wno-error=unused-result -Wno-error=sign-compare -MD -MT
src/CMakeFiles/bellesip.dir/nist.c.o -MF CMakeFiles/bellesip.dir/nist.c.o.d -o
CMakeFiles/bellesip.dir/nist.c.o -c /<>/src/nist.c
/<>/src/nist.c: In function ‘nist_set_completed’:
/<>/src/nist.c:54:51: warning: cast between incompatible function
types from ‘int (*)(belle_sip_nist_t *)’ {aka ‘int (*)(struct belle_sip_nist
*)’} to ‘int (*)(void *, unsigned int)’ [-Wcast-function-type]
54 |
obj->timer_J=belle_sip_timeout_source_new((belle_sip_source_func_t)nist_on_timer_J,obj,tval);
| ^
[ 30%] Building C object src/CMakeFiles/bellesip.dir/port.c.o
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cc
-DBCTBX_LOG_DOMAIN=\"belle-sip\" -DBCTBX_STATIC -DBELLESIP_EXPORTS
-DBELLESIP_STATIC -DHAVE_CONFIG_H -Dbellesip_EXPORTS -I/<>/include
-I/<>/src -I/<>/obj-x86_64-linux-gnu
Bug#1017537: Bug#1017538: dietlibc: FTBFS on armhf: selected processor does not support vldm in ARM mode
Arnd Bergmann dixit: >I tried cross-building it myself now and found the same issue with >an older arm-linux-gnueabihf-gcc-11, which invokes the assembler as > >/usr/lib/gcc-cross/arm-linux-gnueabihf/11/../../../../arm-linux-gnueabihf/bin/as >-v -march=armv7-a -mfloat-abi=hard -meabi=5 -o bin-arm/__longjmp.o >longjmp.s > >where the old one would pass an extra -mfpu=vfpv3-d16. Is my expectation that, for any given platform (armel, armhf, arm64), that a default invocation of the system compiler adds the correct flags not good? >However, with arm-linux-gnueabihf-gcc-12, it appears to work fine again. Sounds like a bug in gcc-11 instead then? (Why has this then not hit more packages?) >I also see that the Makefile attempts to detect the host architecture, but >fails to recognize armv8 hardware as arm. What hardware and toolchain >environment was the failing build on? debian/rules inspects DEB_HOST_ARCH and passes MYARCH to the upstream Makefile so this ought to DTRT…ish — arm64 is passed as aarch64, and all other *arm* are passed as arm (though we don’t carry armeb or the pre-EABI arm any more so that’s probably also fine). Note that #1017537 (on armel) and #1017538 (on armhf) probably are, if not the same thing, at least related. bye, //mirabilos -- > Hi, does anyone sell openbsd stickers by themselves and not packaged > with other products? No, the only way I've seen them sold is for $40 with a free OpenBSD CD. -- Haroon Khalid and Steve Shockley in gmane.os.openbsd.misc
Bug#1017538: dietlibc: FTBFS on armhf: selected processor does not support vldm in ARM mode
On Wed, Aug 17, 2022 at 8:00 PM Thorsten Glaser wrote: > > Arnd Bergmann dixit: > > >-march=armv7-a+fp instead of -march=armv7-a to pick the right > > “instead of” > > We pass nothing there, and we need a solution (or two distinct > ones) for armel and armhf. I tried cross-building it myself now and found the same issue with an older arm-linux-gnueabihf-gcc-11, which invokes the assembler as /usr/lib/gcc-cross/arm-linux-gnueabihf/11/../../../../arm-linux-gnueabihf/bin/as -v -march=armv7-a -mfloat-abi=hard -meabi=5 -o bin-arm/__longjmp.o longjmp.s where the old one would pass an extra -mfpu=vfpv3-d16. However, with arm-linux-gnueabihf-gcc-12, it appears to work fine again. I also see that the Makefile attempts to detect the host architecture, but fails to recognize armv8 hardware as arm. What hardware and toolchain environment was the failing build on? Arnd
Bug#1017571: haskell-persistent: FTBFS on 32 bit archs
Source: haskell-persistent
Version: 2.13.3.5-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=haskell-persistent=i386=2.13.3.5-1=1659381639=0
Failures:
test/Database/Persist/THSpec.hs:240:26:
1) Database.Persist.THSpec.HasIdDef should have correct underlying sql type
expected: SqlInt64
but got: SqlInt32
To rerun use: --match "/Database/Persist/THSpec/HasIdDef/should have correct
underlying sql type/"
Randomized with seed 158227830
Finished in 0.1950 seconds
231 examples, 1 failure, 3 pending
Test suite test: FAIL
Test suite logged to: dist-ghc/test/persistent-2.13.3.5-test.log
0 of 1 test suites (0 of 1 test cases) passed.
-e: error: debian/hlibrary.setup test --builddir=dist-ghc --show-details=direct
returned exit code 1
at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 852.
Debian::Debhelper::Dh_Lib::error("debian/hlibrary.setup test
--builddir=dist-ghc --show-details"...) called at
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 596
Debian::Debhelper::Dh_Lib::error_exitcode("debian/hlibrary.setup test
--builddir=dist-ghc --show-details"...) called at
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 470
Debian::Debhelper::Dh_Lib::doit("debian/hlibrary.setup", "test",
"--builddir=dist-ghc", "--show-details=direct") called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 678
Debian::Debhelper::Buildsystem::Haskell::Recipes::check_recipe() called
at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:165: check-ghc-stamp] Error 25
Cheers
--
Sebastian Ramacher
Bug#1017568: marked as done (reportbug: gnome dependency issues (43 alpha3))
Your message dated Wed, 17 Aug 2022 16:54:54 -0400 with message-id and subject line Re: Bug#1017568: reportbug: gnome dependency issues (43 alpha3) has caused the Debian Bug report #1017568, regarding reportbug: gnome dependency issues (43 alpha3) 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.) -- 1017568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017568 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome Severity: grave Justification: renders package unusable X-Debbugs-Cc: 51vd21...@mozmail.com Dear Maintainer, after running apt full-upgrade and rebooting today, i found myself at tty1 i found that the gnome metapackage had been uninstalled, so i tried to install it using apt install gnome i encountered a dependency issue: libgnome-desktop-3-19 depends gnome-desktop3-data < 43~ but 43~alpha-3 is to be installed -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-4-amd64 (SMP w/24 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome depends on: ii avahi-daemon 0.8-6 ii cheese 43~alpha-1+b1 ii cups-pk-helper 0.2.6-1+b1 ii desktop-base 11.0.3 ii evolution3.44.4-1+b1 ii evolution-plugins3.44.4-1+b1 ii file-roller 3.42.0-1 ii gnome-calendar 42.2-1 ii gnome-clocks 43~beta-1+b1 ii gnome-color-manager 3.36.0-1+b1 pn gnome-core ii gnome-maps 42.3-2 pn gnome-music ii gnome-sound-recorder 43~beta-1 ii gnome-todo 3.28.1-6+b1 pn gnome-tweaks ii gnome-weather43~beta-1 ii gstreamer1.0-libav 1.20.3-1+b1 ii gstreamer1.0-plugins-ugly1.20.3-1 ii libgsf-bin 1.14.50-1 ii libproxy1-plugin-networkmanager 0.4.18-1 ii libreoffice-calc 1:7.4.0~rc3-1 ii libreoffice-gnome1:7.4.0~rc3-1 ii libreoffice-impress 1:7.4.0~rc3-1 ii libreoffice-writer 1:7.4.0~rc3-1 ii network-manager-gnome1.28.0-1 ii orca 42.3-1 ii rhythmbox3.4.6-2 ii rhythmbox-plugin-cdrecorder 3.4.6-2 ii rhythmbox-plugins3.4.6-2 ii rygel-playbin0.40.4-1 ii rygel-tracker0.40.4-1 ii seahorse 42.0-2 ii shotwell 0.30.16-1 ii simple-scan 42.0-1 ii totem-plugins42.0-2+b1 ii xdg-user-dirs-gtk0.10-3 Versions of packages gnome recommends: ii gnome-games 1:42+4 ii gnome-remote-desktop42.4-1 ii nautilus-extension-brasero 3.12.3-1 ii transmission-gtk3.00-2.1 Versions of packages gnome suggests: pn alacarte pn empathy pn firefox-esr-l10n-all | firefox-l10n-all pn goobox | sound-juicer pn polari pn vinagre pn webext-ublock-origin --- End Message --- --- Begin Message --- On Wed, Aug 17, 2022 at 4:39 PM Brian Smith <51vd21...@mozmail.com> wrote: > after running apt full-upgrade and rebooting today, i found myself at tty1 > > i found that the gnome metapackage had been uninstalled, so i tried to > install it using apt install gnome > > i encountered a dependency issue: > > libgnome-desktop-3-19 depends gnome-desktop3-data < 43~ but 43~alpha-3 is to > be installed Please pay attention when running apt full upgrades, especially on Unstable. There is a gnome-desktop transition happening now and there will be temporary installability until all the packages are rebuilt. https://release.debian.org/transitions/html/auto-gnome-desktop.html I'm closing this bug since this is expected behavior and it will be resolved soon. Thank you, Jeremy Bicha--- End Message ---
Processed: Re: Bug#1006788: bagel: autopkgtest failure with new mpich.
Processing control commands: > severity -1 serious Bug #1006788 [bagel] bagel: autopkgtest failure with new mpich. Severity set to 'serious' from 'important' > retitle -1 autopkgtest fails on hosts with lots of RAM/cores Bug #1006788 [bagel] bagel: autopkgtest failure with new mpich. Changed Bug title to 'autopkgtest fails on hosts with lots of RAM/cores' from 'bagel: autopkgtest failure with new mpich.'. -- 1006788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006788 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: nautilus-python: Doesn't work with nautilus 43
Processing commands for cont...@bugs.debian.org:
> notfound 1016960 1.2.3-3.1
Bug #1016960 {Done: Jeremy Bicha } [src:nautilus-python]
nautilus-python: Doesn't work with nautilus 43
No longer marked as found in versions nautilus-python/1.2.3-3.1.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1016960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016960
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1017565: crysal: FTBFS everywhere
Source: crystal
Version: 1.3.2+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=crystal=amd64=1.3.2%2Bdfsg-1=1660695991=0
Failures:
1) Crystal::Loader .parse parses file paths
Failure/Error: expect_raises(Crystal::Loader::LoadError,
/#{Dir.current}\/foobar\.o.+(No such file or directory|image not found)/) do
Expected Crystal::Loader::LoadError with message matching
/\/build\/crystal-oKAM1A\/crystal-1.3.2+dfsg\/foobar\.o.+(No such file or
directory|image not found)/, got #>/foobar.o: cannot open shared object file: No such file or
directory> with backtrace:
# src/compiler/crystal/loader/unix.cr:59:25 in 'parse:search_paths'
# src/spec/expectations.cr:422:12 in '->'
# src/primitives.cr:266:3 in 'internal_run'
# src/spec/example.cr:33:16 in 'run'
# src/spec/context.cr:18:23 in 'internal_run'
# src/spec/context.cr:337:14 in 'run'
# src/spec/context.cr:18:23 in 'internal_run'
# src/spec/context.cr:337:14 in 'run'
# src/spec/context.cr:18:23 in '->'
# src/array.cr:1273:5 in 'main'
# /lib/x86_64-linux-gnu/libc.so.6 in '??'
# /lib/x86_64-linux-gnu/libc.so.6 in '__libc_start_main'
# .build/compiler_spec in '_start'
# ???
# spec/compiler/loader/unix_spec.cr:31
Finished in 14:37 minutes
10296 examples, 1 failures, 0 errors, 15 pending
Failed examples:
crystal spec spec/compiler/loader/unix_spec.cr:30 # Crystal::Loader .parse
parses file paths
make[2]: *** [Makefile:108: compiler_spec] Error 1
Cheers
--
Sebastian Ramacher
Bug#1017564: consul: FTBFS on armel
Source: consul Version: 1.8.7+dfsg1-5 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=consul=armel=1.8.7%2Bdfsg1-5%2Bb2=1660745521=0 === RUN TestGenerateCert generate_test.go:101: DM-skipped --- SKIP: TestGenerateCert (0.00s) === CONT TestGeneratePrivateKey === CONT TestGenerateCA --- PASS: TestGeneratePrivateKey (0.01s) --- PASS: TestGenerateCA (0.02s) PASS ok github.com/hashicorp/consul/tlsutil 1.715s ? github.com/hashicorp/consul/types [no test files] ? github.com/hashicorp/consul/version [no test files] FAIL dh_auto_test: error: cd _build && go test -vet=off -v -p 2 -short -failfast -timeout 8m github.com/hashicorp/consul github.com/hashicorp/consul/acl github.com/hashicorp/consul/command github.com/hashicorp/consul/command/acl github.com/hashicorp/consul/command/acl/authmethod github.com/hashicorp/consul/command/acl/authmethod/create github.com/hashicorp/consul/command/acl/authmethod/delete github.com/hashicorp/consul/command/acl/authmethod/list github.com/hashicorp/consul/command/acl/authmethod/read github.com/hashicorp/consul/command/acl/authmethod/update github.com/hashicorp/consul/command/acl/bindingrule github.com/hashicorp/consul/command/acl/bindingrule/create github.com/hashicorp/consul/command/acl/bindingrule/delete github.com/hashicorp/consul/command/acl/bindingrule/list github.com/hashicorp/consul/command/acl/bindingrule/read github.com/hashicorp/consul/command/acl/bindingrule/update github.com/hashicorp/consul/command/acl/bootstrap github.com/hashicorp/consul/command/acl/policy github.com/hashicorp/consul/command/acl/policy/create github.com/hashicorp/consul/command/acl/policy/delete github.com/hashicorp/consul/command/acl/policy/list github.com/hashicorp/consul/command/acl/policy/read github.com/hashicorp/consul/command/acl/policy/update github.com/hashicorp/consul/command/acl/role github.com/hashicorp/consul/command/acl/role/create github.com/hashicorp/consul/command/acl/role/delete github.com/hashicorp/consul/command/acl/role/list github.com/hashicorp/consul/command/acl/role/read github.com/hashicorp/consul/command/acl/role/update github.com/hashicorp/consul/command/acl/rules github.com/hashicorp/consul/command/acl/token github.com/hashicorp/consul/command/acl/token/clone github.com/hashicorp/consul/command/acl/token/create github.com/hashicorp/consul/command/acl/token/delete github.com/hashicorp/consul/command/acl/token/list github.com/hashicorp/consul/command/acl/token/read github.com/hashicorp/consul/command/acl/token/update github.com/hashicorp/consul/command/catalog github.com/hashicorp/consul/command/catalog/list/dc github.com/hashicorp/consul/command/catalog/list/nodes github.com/hashicorp/consul/command/catalog/list/services github.com/hashicorp/consul/command/config github.com/hashicorp/consul/command/config/delete github.com/hashicorp/consul/command/config/list github.com/hashicorp/consul/command/config/read github.com/hashicorp/consul/command/config/write github.com/hashicorp/consul/command/connect github.com/hashicorp/consul/command/connect/ca github.com/hashicorp/consul/command/connect/ca/get github.com/hashicorp/consul/command/connect/ca/set github.com/hashicorp/consul/command/connect/expose github.com/hashicorp/consul/command/connect/proxy github.com/hashicorp/consul/command/event github.com/hashicorp/consul/command/forceleave github.com/hashicorp/consul/command/helpers github.com/hashicorp/consul/command/info github.com/hashicorp/consul/command/intention github.com/hashicorp/consul/command/intention/check github.com/hashicorp/consul/command/intention/create github.com/hashicorp/consul/command/intention/delete github.com/hashicorp/consul/command/intention/finder github.com/hashicorp/consul/command/intention/get github.com/hashicorp/consul/command/intention/match github.com/hashicorp/consul/command/join github.com/hashicorp/consul/command/keygen github.com/hashicorp/consul/command/keyring github.com/hashicorp/consul/command/kv github.com/hashicorp/consul/command/kv/del github.com/hashicorp/consul/command/kv/exp github.com/hashicorp/consul/command/kv/get github.com/hashicorp/consul/command/kv/imp github.com/hashicorp/consul/command/kv/impexp github.com/hashicorp/consul/command/kv/put github.com/hashicorp/consul/command/leave github.com/hashicorp/consul/command/lock github.com/hashicorp/consul/command/login github.com/hashicorp/consul/command/logout github.com/hashicorp/consul/command/maint github.com/hashicorp/consul/command/members github.com/hashicorp/consul/command/operator github.com/hashicorp/consul/command/operator/autopilot github.com/hashicorp/consul/command/operator/autopilot/get github.com/hashicorp/consul/command/operator/autopilot/set github.com/hashicorp/consul/command/operator/raft
Processed: Re: [Pkg-clamav-devel] Bug#1016270: havp: FTBFS: logfile.cpp:111:22: error: ‘time’ was not declared in this scope
Processing commands for cont...@bugs.debian.org: > # fixed pushed to salsa. > tags 1016270 + patch Bug #1016270 [src:havp] havp: FTBFS: logfile.cpp:111:22: error: ‘time’ was not declared in this scope Added tag(s) patch. > End of message, stopping processing here. Please contact me if you need assistance. -- 1016270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016270 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014264: marked as done (gst-plugins-bad1.0: FTBFS on arm64: test failure)
Your message dated Wed, 17 Aug 2022 19:49:58 + with message-id and subject line Bug#1014264: fixed in gst-plugins-bad1.0 1.20.3-2 has caused the Debian Bug report #1014264, regarding gst-plugins-bad1.0: FTBFS on arm64: test failure to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1014264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014264 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gst-plugins-bad1.0 Version: 1.20.3-1 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) https://buildd.debian.org/status/fetch.php?pkg=gst-plugins-bad1.0=arm64=1.20.3-1%2Bb2=1656796869=0 (elements_dash_mpd:1333015): GStreamer-WARNING **: 21:19:39.329: External plugin loader failed. This most likely means that the plugin loader helper binary was not found or could not be run. You might need to set the GST_PLUGIN_SCANNER environment variable if your setup is unusual. This should normally not be required though. noname.xml:1: namespace error : Namespace prefix customns on bar is not defined Set> ^ noname.xml:1: parser error : Opening and ending tag mismatch: MPD line 1 and NPD sh:schema:mpd:2011" profiles="urn:mpeg:dash:profile:isoff-main:2011"> ^ -- Summary of Failures: 22/77 elements_camerabin FAIL 143.59s exit status 1 Ok: 76 Expected Fail: 0 Fail: 1 Unexpected Pass:0 Skipped:0 Timeout:0 dh_auto_test: error: cd obj-aarch64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 meson test returned exit code 1 Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: gst-plugins-bad1.0 Source-Version: 1.20.3-2 Done: Jeremy Bicha We believe that the bug you reported is fixed in the latest version of gst-plugins-bad1.0, 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 1014...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Bicha (supplier of updated gst-plugins-bad1.0 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: Wed, 17 Aug 2022 15:23:16 -0400 Source: gst-plugins-bad1.0 Built-For-Profiles: noudeb Architecture: source Version: 1.20.3-2 Distribution: unstable Urgency: medium Maintainer: Maintainers of GStreamer packages Changed-By: Jeremy Bicha Closes: 1014264 Changes: gst-plugins-bad1.0 (1.20.3-2) unstable; urgency=medium . * Update patch to skip flaky camerabin test too (Closes: #1014264) Checksums-Sha1: 4f9123c01134dd3d584568075174036ab10929ab 5775 gst-plugins-bad1.0_1.20.3-2.dsc 563d6186d1da33e85789fff416a39730207c242d 31804 gst-plugins-bad1.0_1.20.3-2.debian.tar.xz dd22f2a6c434a3e14f339cc3d06091f16dcc0133 17399 gst-plugins-bad1.0_1.20.3-2_source.buildinfo Checksums-Sha256: 7bfd65937c2d99761f448a0762a1567991cf53d5ea4e47cb3ce4340fece30e47 5775 gst-plugins-bad1.0_1.20.3-2.dsc d6be0fd5f2dbc52aec2d15a37669f76a2cd12550b47ae938bf94d6b9b39e9106 31804 gst-plugins-bad1.0_1.20.3-2.debian.tar.xz 78ff0fa1632138f0fdcd067a9aee2f35a04a90fa429f8f3a7fb53bd50301b6e8 17399 gst-plugins-bad1.0_1.20.3-2_source.buildinfo Files: 4fb160320b99acbb5f4580448803bea0 5775 libs optional gst-plugins-bad1.0_1.20.3-2.dsc ccbccbf57d7f3302cb4be733660a577e 31804 libs optional gst-plugins-bad1.0_1.20.3-2.debian.tar.xz 4120e8b2e3c2c3fb9fd273775257c31f 17399 libs optional gst-plugins-bad1.0_1.20.3-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmL9QW0ACgkQ5mx3Wuv+ bH1dYRAAkqls2t/xQm0x23FSWlA5pKyMWBZ3O40WCG09n+9Tlp6guu0u9UYutVax byS8QX0o4u5kJM6ugJHqnBSCQGGCaBgDJi9YoIarqLxoXY5kM9hmb2ipVefmQNOh ernB25U9dDDnfCuLVjMgVcQYph8z+G4HAJfrR2NRMCHrFqVVDfQRhg0HSufw9LiF pCacKfdPshafvDwMA5GSgMCaJ/FEJPa7POpZvqWP6m585wKl3P0KSxOehw0Oh05c VRahxhskUr2ZQNXZdEFR6MieofSqhkQFUmYeq+eL1PIXSqDi0HWBaVVfCDpsR90E KYkLXWGY293wC+2vvI7U+z8w8PEP0UZ8N/5ntqla7FQVa2NjFIjHY4TTGKSn5x2x
Processed: retitle 1017559 to aqsis FTBFS with openexr 3.1.5
Processing commands for cont...@bugs.debian.org: > retitle 1017559 aqsis FTBFS with openexr 3.1.5 Bug #1017559 [src:aqsis] aqsis TBFS with openexr 3.1.5 Changed Bug title to 'aqsis FTBFS with openexr 3.1.5' from 'aqsis TBFS with openexr 3.1.5'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1017559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017559 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017537: dietlibc: FTBFS on armel: illegal instruction
Sebastian Ramacher dixit: >This is already an issue with 0.34~cvs20160606-12. It’s an incompatible toolchain change that broke this package. I’m trying to find out why, but the ARM porters are not helpful. bye, //mirabilos -- Support mksh as /bin/sh and RoQA dash NOW! ‣ src:bash (406 (433) bugs: 0 RC, 275 (295) I, 131 (138) M, 0 F) + 208 ‣ src:dash (91 (106) bugs: 0 RC, 51 (55) I, 40 (51) M, 0 F) + 63 ubu ‣ src:mksh (1 bug: 0 RC, 0 I, 1 M, 0 F) dash has two RC bugs they just closed because they don’t care about quality…
Bug#1017559: aqsis TBFS with openexr 3.1.5
Source: aqsis Version: 1.8.2+git20210815-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=aqsis=1.8.2%2Bgit20210815-1%2Bb2 ... CMake Error at libs/shadervm/CMakeLists.txt:5 (message): Aqsis shadervm requires boost regex and OpenEXR to build -- Configuring incomplete, errors occurred! ... //Location of the Half OpenEXR library AQSIS_HALF_LIBRARY:FILEPATH=AQSIS_HALF_LIBRARY-NOTFOUND //Location of the Iex OpenEXR library AQSIS_IEX_LIBRARY:FILEPATH=/usr/lib/x86_64-linux-gnu/libIex.so //Location of the IlmImf OpenEXR library AQSIS_ILMIMF_LIBRARY:FILEPATH=AQSIS_ILMIMF_LIBRARY-NOTFOUND //Location of the IlmThread OpenEXR library AQSIS_ILMTHREAD_LIBRARY:FILEPATH=/usr/lib/x86_64-linux-gnu/libIlmThread.so //Location of the Imath OpenEXR library AQSIS_IMATH_LIBRARY:FILEPATH=/usr/lib/x86_64-linux-gnu/libImath.so //Name of the main aqsis configuration file AQSIS_MAIN_CONFIG_NAME:STRING=aqsisrc //Location of the NSIS executable AQSIS_NSIS_EXECUTABLE:FILEPATH=AQSIS_NSIS_EXECUTABLE-NOTFOUND //Location of the OpenEXR headers AQSIS_OPENEXR_INCLUDE_DIR:PATH=/usr/include //Semi-colon separated list of paths to search for openexr libraries AQSIS_OPENEXR_LIBRARIES_DIR:PATH= ...
Bug#1017547: openexr-viewers FTBFS with openexr 3.1.5
Hi Pino ! Since openexr-viewers does not build anymore against openexr 3.x and it is dead upstream, do you want me to fill in a RM for you ? Thanks
Processed: src:redis: fails to migrate to testing for too long: autopkgtest regressions
Processing control commands: > close -1 5:7.0.4-1 Bug #1017556 [src:redis] src:redis: fails to migrate to testing for too long: autopkgtest regressions Marked as fixed in versions redis/5:7.0.4-1. Bug #1017556 [src:redis] src:redis: fails to migrate to testing for too long: autopkgtest regressions Marked Bug as done -- 1017556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017556 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017556: src:redis: fails to migrate to testing for too long: autopkgtest regressions
Source: redis Version: 5:6.0.16-4 Severity: serious Control: close -1 5:7.0.4-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:redis has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your package is a key package and so is python-fakeredis. Hence, the autopkgtest regression won't be fixed by autoremoval. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=redis OpenPGP_signature Description: OpenPGP digital signature
Processed: Re: Bug#1017537: dietlibc: FTBFS on armel: illegal instruction
Processing control commands: > found -1 0.34~cvs20160606-12 Bug #1017537 [src:dietlibc] dietlibc: FTBFS on armel: illegal instruction Marked as found in versions dietlibc/0.34~cvs20160606-12. > tags -1 sid bookworm Bug #1017537 [src:dietlibc] dietlibc: FTBFS on armel: illegal instruction Added tag(s) sid and bookworm. -- 1017537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017537 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017537: dietlibc: FTBFS on armel: illegal instruction
Control: found -1 0.34~cvs20160606-12 Control: tags -1 sid bookworm On 2022-08-17 18:54:38 +0200, Sebastian Ramacher wrote: > Source: dietlibc > Version: 0.34~cvs20160606-14 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > X-Debbugs-Cc: sramac...@debian.org > > https://buildd.debian.org/status/fetch.php?pkg=dietlibc=armel=0.34%7Ecvs20160606-14=1658293281=0 > > > RUN ERROR for debian/unittests/tc523086.c in variant pthreads (rc = 132), > test output is: > > Illegal instruction > This is already an issue with 0.34~cvs20160606-12. Cheers > > > RUN ERROR for debian/unittests/t-ascii1.c in variant pthreads (rc = 132), > test output is: > > Illegal instruction > > > > RUN ERROR for debian/unittests/signal.c in variant pthreads (rc = 132), test > output is: > > Illegal instruction > > > > RUN ERROR for debian/unittests/gettimeofday.c in variant pthreads (rc = 132), > test output is: > > Illegal instruction > > > > RUN ERROR for debian/unittests/socketfns.c in variant pthreads (rc = 132), > test output is: > > Illegal instruction > > > > RUN ERROR for test/bsearch.c in variant pthreads (rc = 132), test output is: > > Illegal instruction > > > > RUN ERROR for test/fadvise.c in variant pthreads (rc = 132), test output is: > > Illegal instruction > > > > RUN ERROR for test/mmap_test.c in variant pthreads (rc = 132), test output is: > > Illegal instruction > > > > RUN ERROR for test/stdarg.c in variant pthreads (rc = 132), test output is: > > Illegal instruction > > > > RUN ERROR for test/ungetc.c in variant pthreads (rc = 132), test output is: > > Illegal instruction > > > > RUN ERROR for test/utime.c in variant pthreads (rc = 132), test output is: > > Illegal instruction > > > > RUN ERROR for test/waitpid.c in variant pthreads (rc = 132), test output is: > > Illegal instruction > > > > RUN ERROR for test/dirent/opendir-tst1.c in variant pthreads (rc = 132), test > output is: > > Illegal instruction > > > > RUN ERROR for test/stdlib/tst-calloc.c in variant pthreads (rc = 132), test > output is: > > Illegal instruction > > > make[1]: *** [debian/rules:105: override_dh_auto_test-arch] Error 1 > make[1]: Leaving directory '/<>' > > > Cheers > -- > Sebastian Ramacher -- Sebastian Ramacher
Processed: juce-7.0.1~ds0/debian/extra/juce_audio_processors/format_types/juce_VSTInterface.h needs updating for 7.0.1
Processing control commands: > affects -1 src:iem-plugin-suite Bug #1017554 [juce-modules-source-data] juce-7.0.1~ds0/debian/extra/juce_audio_processors/format_types/juce_VSTInterface.h needs updating for 7.0.1 Added indication that 1017554 affects src:iem-plugin-suite -- 1017554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017554 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017554: juce-7.0.1~ds0/debian/extra/juce_audio_processors/format_types/juce_VSTInterface.h needs updating for 7.0.1
Package: juce-modules-source-data Version: 7.0.1~ds0-1 Severity: serious Tags: ftbfs Control: affects -1 src:iem-plugin-suite https://buildd.debian.org/status/fetch.php?pkg=iem-plugin-suite=amd64=1.13.0-2%2Bb2=1660758021=0 ... /usr/share/juce/modules/juce_audio_plugin_client/VST/juce_VST_Wrapper.cpp: In member function ‘void JuceVSTWrapper::updateCallbackContextInfo()’: /usr/share/juce/modules/juce_audio_plugin_client/VST/juce_VST_Wrapper.cpp:670:100: error: ‘const struct Vst2::VstTimeInfo’ has no member named ‘nanoSeconds’ 670 | info.setHostTimeNs ((ti->flags & Vst2::kVstNanosValid) != 0 ? makeOptional ((uint64_t) ti->nanoSeconds) : nullopt); | ^~~ ...
Bug#1017513: marked as done (isa-support: mktemp on /usr/lib and base64 encoded binary in preinst are evil)
Your message dated Wed, 17 Aug 2022 19:01:09 + with message-id and subject line Bug#1017513: fixed in isa-support 8 has caused the Debian Bug report #1017513, regarding isa-support: mktemp on /usr/lib and base64 encoded binary in preinst are evil 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.) -- 1017513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017513 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: isa-support Version: 7 Severity: grave Tags: patch Justification: causes non-serious data loss Dear Maintainer, mktemp could fail and base64 is preinst is not nice -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-2-rt-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: isa-support Source-Version: 8 Done: Bastien Roucariès We believe that the bug you reported is fixed in the latest version of isa-support, 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 1017...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastien Roucariès (supplier of updated isa-support 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: Wed, 17 Aug 2022 10:26:10 + Source: isa-support Binary: isa-support isa-support-dbgsym sse3-support sse4.2-support Architecture: source amd64 Version: 8 Distribution: experimental Urgency: medium Maintainer: Bastien Roucariès Changed-By: Bastien Roucariès Description: isa-support - prevent installation on processors without required features sse3-support - prevent installation on processors without required sse3 instruct sse4.2-support - prevent installation on processors without required sse4.2 instru Closes: 1014892 1017513 Changes: isa-support (8) experimental; urgency=medium . [ Gioele Barabucci ] * d/preinst: Use base64 instead of uuencode+perl to encode test binaries * d/control: Adopt package (Closes: #1014892) * d/control: Bump Standards-Version to 4.6.1 (no changes needed) * d/control: Update to debhelper compat 13 * d/control: Fix Vcs-Browser URL * d/preinst: Use `||` and `&&` instead of non well defined `-o` and `-a` * d/preinst: Use command substitutions instead of backticks * build: Split into multiple scripts * build: Delegate compilation to Makefile * Materialize package files * d/control: Add instruction set name to Description * calculate-shlibdeps: Run only on archs supported by host machine * d/po: Refresh po files (no changes in messages) * d/control: Avoid repeated Priority field in binary package stanzas * d/s/lintian-overrides: Drop package-depends-on-hardcoded-libc * d/gitlab-ci: Add standard CI instructions . [ Bastien Roucariès ] * Add myself as uploader * run salsa-ci tests * Run make only on test for DEB_HOST_ARCH * Split package and do not use embdeded base64 ELF binaries in preinst (Closes: 1017513) Checksums-Sha1: 015f967c798601cdeb9949da102c6022d098cc72 1996 isa-support_8.dsc bacf0e63d3d2ec1e1c233b5d3174c66c7ae8bc8f 10436 isa-support_8.tar.xz c81ec9e890335790f1578d36fb79b6f319452e16 2800 isa-support-dbgsym_8_amd64.deb 270d2bb5cb3c9c8e22ff2b122e18ecad7a05a37d 6701 isa-support_8_amd64.buildinfo 2cb0b71c0b941c4aafa10f682736b37d3dcc82c6 7956 isa-support_8_amd64.deb e428d8b278ad3948ef1086d02fbfef33516c3b32 3036 sse3-support_8_amd64.deb 67c93da57463b0c2d46627f26b4743ad552f18b5 3048 sse4.2-support_8_amd64.deb Checksums-Sha256: 31594b12b5e1e18a3554753264e30d3625b57ca53656a441d376ed9a1b0593b4 1996 isa-support_8.dsc 189e9e41456d502fe9a3c61781b165e4fbc45a69eac991e3bd1c9ef9dbc3e6da 10436 isa-support_8.tar.xz 08e49cc62dc963c033246a6ade0a51005189d9e35ab3376994eb86b126a6d0b1 2800 isa-support-dbgsym_8_amd64.deb 8ed49618a1a05f45cbd5ef4df1433f26586448a9785bd22a2d6c35ab16d4a8c6 6701 isa-support_8_amd64.buildinfo
Processed (with 2 errors): Re: Bug#1017154: fuse: FTBFS: ulockmgr_server.c:127:12: error: conflicting types for ‘closefrom’; have ‘int(int)’
Processing control commands: > tags -1 + confirmed patch upstream Bug #1017154 [src:fuse] fuse: FTBFS: ulockmgr_server.c:127:12: error: conflicting types for ‘closefrom’; have ‘int(int)’ Added tag(s) patch, upstream, and confirmed. > forwarded -1 > https://patchwork.ozlabs.org/project/buildroot/patch/20210912194057.2556882-1-fontaine.fabr...@gmail.com/#2753385 Bug #1017154 [src:fuse] fuse: FTBFS: ulockmgr_server.c:127:12: error: conflicting types for ‘closefrom’; have ‘int(int)’ Set Bug forwarded-to-address to 'https://patchwork.ozlabs.org/project/buildroot/patch/20210912194057.2556882-1-fontaine.fabr...@gmail.com/#2753385'. > user helm...@debian.org Unknown command or malformed arguments to command. > usertags -1 + rebootstrap Unknown command or malformed arguments to command. -- 1017154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017154 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017154: fuse: FTBFS: ulockmgr_server.c:127:12: error: conflicting types for ‘closefrom’; have ‘int(int)’
Control: tags -1 + confirmed patch upstream Control: forwarded -1 https://patchwork.ozlabs.org/project/buildroot/patch/20210912194057.2556882-1-fontaine.fabr...@gmail.com/#2753385 Control: user helm...@debian.org Control: usertags -1 + rebootstrap On Sun, Aug 14, 2022 at 09:12:12AM +0200, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. The patch to fix this is in the link above. Helmut
Bug#1017552: alertmanager-irc-relay: FTBFS on armel
Source: alertmanager-irc-relay Version: 0.4.2-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=alertmanager-irc-relay=armel=0.4.2-1%2Bb3=1660740127=0 2022/08/17 12:41:55.543763 reconciler.go:77: INFO Setting JOIN state on channel #foo 2022/08/17 12:41:55.543873 reconciler.go:116: INFO Channel #foo monitor: join succeeded 2022/08/17 12:41:55.543971 reconciler.go:129: INFO Channel #foo monitor: context canceled while monitoring 2022/08/17 12:41:55.544069 irc_server_for_test.go:168: INFO =Server= Stopped accepting new connections --- PASS: TestKickRejoin (0.00s) FAIL FAILgithub.com/google/alertmanager-irc-relay0.128s ? github.com/google/alertmanager-irc-relay/logging[no test files] FAIL dh_auto_test: error: cd obj-arm-linux-gnueabi && go test -vet=off -v -p 4 github.com/google/alertmanager-irc-relay github.com/google/alertmanager-irc-relay/logging returned exit code 1 make: *** [debian/rules:7: build-arch] Error 25 dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2 Cheers -- Sebastian Ramacher
Processed: severity of 1017545 is important
Processing commands for cont...@bugs.debian.org: > severity 1017545 important Bug #1017545 [src:golang-github-golang-jwt-jwt] golang-github-golang-jwt-jwt: FTBFS on mipsel Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1017545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017545 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017538: dietlibc: FTBFS on armhf: selected processor does not support vldm in ARM mode
On 2022-08-17 17:28:08 +, Thorsten Glaser wrote:
> tags 1017538 + help
> forwarded 1017538 https://lists.debian.org/debian-arm/2022/07/msg00041.html
> thanks
>
> Hi Sebastian,
>
> instead of filing a bug with the information we already have…
>
> >arm/__longjmp.S: Assembler messages:
> >arm/__longjmp.S:9: Error: selected processor does not support `vldm
> >ip!,{d0-d15}' in ARM mode
>
> … you could maybe have considered answering the question I posed
> on the Debian ARM mailing list about *why* it fails because nothing
> related to ARM was changed in the package or code.
Don't shoot the messanger.
Cheers
>
> So something in the toolchain(?) must have changed since the last
> successful build (what?) which we need to locally revert.
>
> Thanks in advance for any help,
> //mirabilos
> --
> Solange man keine schmutzigen Tricks macht, und ich meine *wirklich*
> schmutzige Tricks, wie bei einer doppelt verketteten Liste beide
> Pointer XORen und in nur einem Word speichern, funktioniert Boehm ganz
> hervorragend. -- Andreas Bogk über boehm-gc in d.a.s.r
--
Sebastian Ramacher
Bug#1017284: fenics-dolfinx: FTBFS: CheckSymbolExists.c:8:19: error: ‘PETSC_USE_COMPLEX’ undeclared (first use in this function); did you mean ‘PETSC_HAVE_COMPLEX’?
Source: fenics-dolfinx Followup-For: Bug #1017284 The cmake error logs can be too effusive, they tend to obscure the error. In this case the real problem seems to be that it never found scotch, even though it found it. A mystery indeed. Schrödinger's SCOTCH.
Bug#1017548: minetest: CVE-2022-35978
Source: minetest Version: 5.5.0+dfsg+~1.9.0mt4+dfsg-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for minetest, filling it as grave, but downgrade if you strongly disagree. CVE-2022-35978[0]: | Minetest is a free open-source voxel game engine with easy modding and | game creation. In **single player**, a mod can set a global setting | that controls the Lua script loaded to display the main menu. The | script is then loaded as soon as the game session is exited. The Lua | environment the menu runs in is not sandboxed and can directly | interfere with the user's system. There are currently no known | workarounds. 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-2022-35978 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-35978 [1] https://github.com/minetest/minetest/security/advisories/GHSA-663q-pcjw-27cc [2] https://github.com/minetest/minetest/commit/da71e86633d0b27cd02d7aac9fdac625d141ca13 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#1017538: dietlibc: FTBFS on armhf: selected processor does not support vldm in ARM mode
Arnd Bergmann dixit: >-march=armv7-a+fp instead of -march=armv7-a to pick the right “instead of” We pass nothing there, and we need a solution (or two distinct ones) for armel and armhf. bye, //mirabilos -- [...] if maybe ext3fs wasn't a better pick, or jfs, or maybe reiserfs, oh but what about xfs, and if only i had waited until reiser4 was ready... in the be- ginning, there was ffs, and in the middle, there was ffs, and at the end, there was still ffs, and the sys admins knew it was good. :) -- Ted Unangst über *fs
Bug#1017547: openexr-viewers FTBFS with openexr 3.1.5
Source: openexr-viewers Version: 2.3.0-1 Severity: serious Tags: ftbfs bookworm sid https://buildd.debian.org/status/fetch.php?pkg=openexr-viewers=amd64=2.3.0-1%2Bb2=1660741866=0 ... main.cpp:66:10: fatal error: ImathLimits.h: No such file or directory 66 | #include | ^~~ compilation terminated. make[2]: *** [Makefile:494: main.o] Error 1
Bug#1017538: dietlibc: FTBFS on armhf: selected processor does not support vldm in ARM mode
On Wed, Aug 17, 2022 at 7:28 PM Thorsten Glaser wrote:
>
> tags 1017538 + help
> forwarded 1017538 https://lists.debian.org/debian-arm/2022/07/msg00041.html
> thanks
>
> Hi Sebastian,
>
> instead of filing a bug with the information we already have…
>
> >arm/__longjmp.S: Assembler messages:
> >arm/__longjmp.S:9: Error: selected processor does not support `vldm
> >ip!,{d0-d15}' in ARM mode
>
> … you could maybe have considered answering the question I posed
> on the Debian ARM mailing list about *why* it fails because nothing
> related to ARM was changed in the package or code.
>
> So something in the toolchain(?) must have changed since the last
> successful build (what?) which we need to locally revert.
The way the FPU type gets selected in gcc changed with recent versions,
this was intentional and won't be reverted but it did break packages that
used the old method. In most cases, it's sufficient to pass
-march=armv7-a+fp instead of -march=armv7-a to pick the right
instruction set.
Arnd
Bug#1017546: golang-github-vbatts-tar-split: FTBFS on mips64el
Source: golang-github-vbatts-tar-split
Version: 0.11.1-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=golang-github-vbatts-tar-split=mips64el=0.11.1-2%2Bb7=1660746830=0
=== RUN TestLargeJunkPadding
[TestLargeJunkPadding] junk chunk #0/#320
[TestLargeJunkPadding] junk chunk #32/#320
[TestLargeJunkPadding] junk chunk #64/#320
[TestLargeJunkPadding] junk chunk #96/#320
[TestLargeJunkPadding] junk chunk #128/#320
[TestLargeJunkPadding] junk chunk #160/#320
panic: test timed out after 10m0s
goroutine 28 [running]:
testing.(*M).startAlarm.func1()
/usr/lib/go-1.19/src/testing/testing.go:2036 +0x108
created by time.goFunc
/usr/lib/go-1.19/src/time/sleep.go:176 +0x5c
goroutine 1 [chan receive, 9 minutes]:
testing.(*T).Run(0xc82b60, {0x1201c59a6, 0x14}, 0x1201ceb00)
/usr/lib/go-1.19/src/testing/testing.go:1494 +0x4b8
testing.runTests.func1(0xc82b60)
/usr/lib/go-1.19/src/testing/testing.go:1846 +0xa0
testing.tRunner(0xc82b60, 0xcb1cf8)
/usr/lib/go-1.19/src/testing/testing.go:1446 +0x140
testing.runTests(0xcb6030, {0x1202c5300, 0x3, 0x3}, {0xc0b75cf0c3e8d1b6,
0x8bb2fe5587, 0x1202e4760})
/usr/lib/go-1.19/src/testing/testing.go:1844 +0x524
testing.(*M).Run(0xcc4140)
/usr/lib/go-1.19/src/testing/testing.go:1726 +0x734
main.main()
_testmain.go:53 +0x250
goroutine 41 [select]:
io.(*pipe).read(0xc0002958c0, {0xc000218000, 0x2000, 0x2000})
/usr/lib/go-1.19/src/io/pipe.go:57 +0xc0
io.(*PipeReader).Read(0xc0002a4048, {0xc000218000, 0x2000, 0x2000})
/usr/lib/go-1.19/src/io/pipe.go:136 +0x5c
io.discard.ReadFrom({}, {0x1201fb5b8, 0xc0002a4048})
/usr/lib/go-1.19/src/io/io.go:611 +0xb4
io.copyBuffer({0x1201fb7f8, 0x120311d40}, {0x1201fb5b8, 0xc0002a4048}, {0x0,
0x0, 0x0})
/usr/lib/go-1.19/src/io/io.go:413 +0x18c
io.Copy(...)
/usr/lib/go-1.19/src/io/io.go:386
github.com/vbatts/tar-split/tar/asm.TestLargeJunkPadding(0xc036c0)
/<>/obj-mips64el-linux-gnuabi64/src/github.com/vbatts/tar-split/tar/asm/disassemble_test.go:65
+0x468
testing.tRunner(0xc036c0, 0x1201ceb00)
/usr/lib/go-1.19/src/testing/testing.go:1446 +0x140
created by testing.(*T).Run
/usr/lib/go-1.19/src/testing/testing.go:1493 +0x498
goroutine 42 [select]:
io.(*pipe).write(0xc000295860, {0xc000394000, 0x8000, 0x8000})
/usr/lib/go-1.19/src/io/pipe.go:86 +0x1f0
io.(*PipeWriter).Write(0xc0002a4040, {0xc000394000, 0x8000, 0x8000})
/usr/lib/go-1.19/src/io/pipe.go:165 +0x5c
io.copyBuffer({0x1201fb5d8, 0xc0002a4040}, {0x1201fb598, 0xcb6048}, {0x0,
0x0, 0x0})
/usr/lib/go-1.19/src/io/io.go:429 +0x2a8
io.Copy(...)
/usr/lib/go-1.19/src/io/io.go:386
io.CopyN({0x1201fb5d8, 0xc0002a4040}, {0x1201fb658, 0xca2050}, 0x400)
/usr/lib/go-1.19/src/io/io.go:362 +0xc8
github.com/vbatts/tar-split/tar/asm.TestLargeJunkPadding.func1()
/<>/obj-mips64el-linux-gnuabi64/src/github.com/vbatts/tar-split/tar/asm/disassemble_test.go:46
+0x39c
created by github.com/vbatts/tar-split/tar/asm.TestLargeJunkPadding
/<>/obj-mips64el-linux-gnuabi64/src/github.com/vbatts/tar-split/tar/asm/disassemble_test.go:21
+0x248
goroutine 43 [runnable]:
bytes.(*Buffer).Write(0xc0002ba000, {0xc0002f0db8, 0x400, 0x400})
/usr/lib/go-1.19/src/bytes/buffer.go:166 +0x1c
encoding/base64.(*encoder).Write(0xc0002f0d80, {0xc00088, 0x8000, 0x10})
/usr/lib/go-1.19/src/encoding/base64/base64.go:224 +0x1dc
encoding/json.encodeByteSlice(0xc0002ba000, {0x1201981a0, 0xc001223dd8, 0x97},
{0x0, 0x1})
/usr/lib/go-1.19/src/encoding/json/encode.go:857 +0x414
encoding/json.structEncoder.encode({{{0xc00013c000, 0x6, 0x8}, 0xc9e840}},
0xc0002ba000, {0x1201b5780, 0xc001223da0, 0x99}, {0x0, 0x1})
/usr/lib/go-1.19/src/encoding/json/encode.go:760 +0x1f8
encoding/json.(*encodeState).reflectValue(0xc0002ba000, {0x1201b5780,
0xc001223da0, 0x99}, {0x0, 0x1})
/usr/lib/go-1.19/src/encoding/json/encode.go:359 +0x90
encoding/json.(*encodeState).marshal(0xc0002ba000, {0x1201b5780, 0xc001223da0},
{0x0, 0x1})
/usr/lib/go-1.19/src/encoding/json/encode.go:331 +0x188
encoding/json.(*Encoder).Encode(0xca6320, {0x1201b5780, 0xc001223da0})
/usr/lib/go-1.19/src/encoding/json/stream.go:206 +0x80
github.com/vbatts/tar-split/tar/storage.(*jsonPacker).AddEntry(0xc0005283c0,
{0x2, {0x0, 0x0}, {0x0, 0x0, 0x0}, 0x0, {0xc00088, 0x8000, ...}, ...})
/<>/obj-mips64el-linux-gnuabi64/src/github.com/vbatts/tar-split/tar/storage/packer.go:97
+0x214
github.com/vbatts/tar-split/tar/asm.NewInputTarStream.func1()
/<>/obj-mips64el-linux-gnuabi64/src/github.com/vbatts/tar-split/tar/asm/disassemble.go:138
+0x780
created by github.com/vbatts/tar-split/tar/asm.NewInputTarStream
Bug#1017545: golang-github-golang-jwt-jwt: FTBFS on mipsel
Source: golang-github-golang-jwt-jwt Version: 4.2.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=golang-github-golang-jwt-jwt=mipsel=4.2.0-1%2Bb2=1660751536=0 === RUN Example_getTokenViaHTTP 2022/08/17 15:52:04 Authenticate: user[test] pass[known] --- PASS: Example_getTokenViaHTTP (0.65s) === RUN Example_useTokenViaHTTP --- PASS: Example_useTokenViaHTTP (0.64s) FAIL FAILgithub.com/golang-jwt/jwt 32.502s ? github.com/golang-jwt/jwt/cmd/jwt [no test files] === RUN TestExtractor --- PASS: TestExtractor (0.00s) === RUN TestParseRequest --- PASS: TestParseRequest (2.62s) === RUN ExampleHeaderExtractor --- PASS: ExampleHeaderExtractor (0.00s) === RUN ExampleArgumentExtractor --- PASS: ExampleArgumentExtractor (0.00s) PASS ok github.com/golang-jwt/jwt/request 2.656s ? github.com/golang-jwt/jwt/test [no test files] FAIL dh_auto_test: error: cd _build && go test -vet=off -v -p 4 github.com/golang-jwt/jwt github.com/golang-jwt/jwt/cmd/jwt github.com/golang-jwt/jwt/request github.com/golang-jwt/jwt/test returned exit code 1 make: *** [debian/rules:6: binary-arch] Error 25 Cheers -- Sebastian Ramacher
Bug#1013573: marked as done (djangorestframework-filters: FTBFS: missing python3-tz Depends in python3-djangorestframework)
Your message dated Wed, 17 Aug 2022 19:28:14 +0200
with message-id <20220817172814.hx2azffyy3rc2...@libra.beauplat.fr>
and subject line Re: Bug#1013573: djangorestframework-filters: FTBFS:
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9
3.10" returned exit code 13
has caused the Debian Bug report #1013573,
regarding djangorestframework-filters: FTBFS: missing python3-tz Depends in
python3-djangorestframework
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.)
--
1013573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013573
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: djangorestframework-filters
Version: 1.0.0.dev2-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> pybuild --configure -i python{version} -p "3.9 3.10"
> I: pybuild base:239: python3.9 setup.py config
> running config
> I: pybuild base:239: python3.10 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> pybuild --build -i python{version} -p "3.9 3.10"
> I: pybuild base:239: /usr/bin/python3.9 setup.py build
> running build
> running build_py
> creating
> /<>/.pybuild/cpython3_3.9_djangorestframework-filters/build/rest_framework_filters
> copying rest_framework_filters/__init__.py ->
> /<>/.pybuild/cpython3_3.9_djangorestframework-filters/build/rest_framework_filters
> copying rest_framework_filters/complex_ops.py ->
> /<>/.pybuild/cpython3_3.9_djangorestframework-filters/build/rest_framework_filters
> copying rest_framework_filters/filters.py ->
> /<>/.pybuild/cpython3_3.9_djangorestframework-filters/build/rest_framework_filters
> copying rest_framework_filters/backends.py ->
> /<>/.pybuild/cpython3_3.9_djangorestframework-filters/build/rest_framework_filters
> copying rest_framework_filters/filterset.py ->
> /<>/.pybuild/cpython3_3.9_djangorestframework-filters/build/rest_framework_filters
> copying rest_framework_filters/utils.py ->
> /<>/.pybuild/cpython3_3.9_djangorestframework-filters/build/rest_framework_filters
> creating
> /<>/.pybuild/cpython3_3.9_djangorestframework-filters/build/rest_framework_filters/templatetags
> copying rest_framework_filters/templatetags/__init__.py ->
> /<>/.pybuild/cpython3_3.9_djangorestframework-filters/build/rest_framework_filters/templatetags
> copying rest_framework_filters/templatetags/rest_framework_filters.py ->
> /<>/.pybuild/cpython3_3.9_djangorestframework-filters/build/rest_framework_filters/templatetags
> running egg_info
> creating djangorestframework_filters.egg-info
> writing djangorestframework_filters.egg-info/PKG-INFO
> writing dependency_links to
> djangorestframework_filters.egg-info/dependency_links.txt
> writing requirements to djangorestframework_filters.egg-info/requires.txt
> writing top-level names to djangorestframework_filters.egg-info/top_level.txt
> writing manifest file 'djangorestframework_filters.egg-info/SOURCES.txt'
> reading manifest file 'djangorestframework_filters.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no previously-included files matching '__pycache__' found anywhere
> in distribution
> warning: no previously-included files matching '*.py[co]' found anywhere in
> distribution
> adding license file 'LICENSE'
> writing manifest file 'djangorestframework_filters.egg-info/SOURCES.txt'
> creating
> /<>/.pybuild/cpython3_3.9_djangorestframework-filters/build/rest_framework_filters/templates
> creating
> /<>/.pybuild/cpython3_3.9_djangorestframework-filters/build/rest_framework_filters/templates/rest_framework_filters
> copying
> rest_framework_filters/templates/rest_framework_filters/crispy_form.html ->
> /<>/.pybuild/cpython3_3.9_djangorestframework-filters/build/rest_framework_filters/templates/rest_framework_filters
> copying rest_framework_filters/templates/rest_framework_filters/form.html ->
> /<>/.pybuild/cpython3_3.9_djangorestframework-filters/build/rest_framework_filters/templates/rest_framework_filters
> I: pybuild base:239: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating
> /<>/.pybuild/cpython3_3.10_djangorestframework-filters/build/rest_framework_filters
> copying
Bug#1017544: golang-github-anacrolix-missinggo: FTBFS: test failures
Source: golang-github-anacrolix-missinggo
Version: 2.1.0-6
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=golang-github-anacrolix-missinggo=arm64=2.1.0-6%2Bb8=1660737580=0
--- PASS: TestGetSubtestName (0.00s)
--- PASS: TestGetSubtestName/hello (0.00s)
--- PASS: TestGetSubtestName/world (0.00s)
=== RUN TestTimerDrain
timer_test.go:22:
Error Trace:timer_test.go:22
Error: received too soon
Test: TestTimerDrain
panic: test timed out after 10m0s
goroutine 50 [running]:
testing.(*M).startAlarm.func1()
/usr/lib/go-1.19/src/testing/testing.go:2036 +0x88
created by time.goFunc
/usr/lib/go-1.19/src/time/sleep.go:176 +0x38
goroutine 1 [chan receive]:
testing.(*T).Run(0x485380, {0x2066e7?, 0x45de77c1c641?}, 0x22ebe8)
/usr/lib/go-1.19/src/testing/testing.go:1494 +0x33c
testing.runTests.func1(0x0?)
/usr/lib/go-1.19/src/testing/testing.go:1846 +0x70
testing.tRunner(0x485380, 0x4000109cb8)
/usr/lib/go-1.19/src/testing/testing.go:1446 +0x10c
testing.runTests(0x4bd220?, {0x3a6420, 0x18, 0x18}, {0xdd00?,
0xdd574404eb4f9589?, 0x3ac500?})
/usr/lib/go-1.19/src/testing/testing.go:1844 +0x3e8
testing.(*M).Run(0x4bd220)
/usr/lib/go-1.19/src/testing/testing.go:1726 +0x500
main.main()
_testmain.go:99 +0x1e8
goroutine 49 [chan receive]:
github.com/anacrolix/missinggo.TestTimerDrain(0x400012e340?)
/<>/obj-aarch64-linux-gnu/src/github.com/anacrolix/missinggo/timer_test.go:26
+0xd8
testing.tRunner(0x400012eb60, 0x22ebe8)
/usr/lib/go-1.19/src/testing/testing.go:1446 +0x10c
created by testing.(*T).Run
/usr/lib/go-1.19/src/testing/testing.go:1493 +0x328
FAILgithub.com/anacrolix/missinggo 600.139s
Cheers
--
Sebastian Ramacher
Bug#1017538: dietlibc: FTBFS on armhf: selected processor does not support vldm in ARM mode
tags 1017538 + help
forwarded 1017538 https://lists.debian.org/debian-arm/2022/07/msg00041.html
thanks
Hi Sebastian,
instead of filing a bug with the information we already have…
>arm/__longjmp.S: Assembler messages:
>arm/__longjmp.S:9: Error: selected processor does not support `vldm
>ip!,{d0-d15}' in ARM mode
… you could maybe have considered answering the question I posed
on the Debian ARM mailing list about *why* it fails because nothing
related to ARM was changed in the package or code.
So something in the toolchain(?) must have changed since the last
successful build (what?) which we need to locally revert.
Thanks in advance for any help,
//mirabilos
--
Solange man keine schmutzigen Tricks macht, und ich meine *wirklich*
schmutzige Tricks, wie bei einer doppelt verketteten Liste beide
Pointer XORen und in nur einem Word speichern, funktioniert Boehm ganz
hervorragend. -- Andreas Bogk über boehm-gc in d.a.s.r
Processed: Re: Bug#1017538: dietlibc: FTBFS on armhf: selected processor does not support vldm in ARM mode
Processing commands for cont...@bugs.debian.org: > tags 1017538 + help Bug #1017538 [src:dietlibc] dietlibc: FTBFS on armhf: selected processor does not support vldm in ARM mode Added tag(s) help. > forwarded 1017538 https://lists.debian.org/debian-arm/2022/07/msg00041.html Bug #1017538 [src:dietlibc] dietlibc: FTBFS on armhf: selected processor does not support vldm in ARM mode Set Bug forwarded-to-address to 'https://lists.debian.org/debian-arm/2022/07/msg00041.html'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1017538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017538 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org:
> unarchive 1012954
Bug #1012954 {Done: IOhannes m zmölnig (Debian/GNU) }
[src:juce] juce: ftbfs with GCC-12
Unarchived Bug 1012954
> reassign 1012947 src:juce
Bug #1012947 [src:iem-plugin-suite] iem-plugin-suite: ftbfs with GCC-12
Bug reassigned from package 'src:iem-plugin-suite' to 'src:juce'.
No longer marked as found in versions iem-plugin-suite/1.13.0-2.
Ignoring request to alter fixed versions of bug #1012947 to the same values
previously set
> forcemerge 1012954 1012947
Bug #1012954 {Done: IOhannes m zmölnig (Debian/GNU) }
[src:juce] juce: ftbfs with GCC-12
Bug #1012947 [src:juce] iem-plugin-suite: ftbfs with GCC-12
Severity set to 'normal' from 'serious'
Marked Bug as done
Marked as fixed in versions juce/7.0.0~ds0-1.
Marked as found in versions juce/6.1.6~ds0-1.
Merged 1012947 1012954
> affects 1012954 src:iem-plugin-suite
Bug #1012954 {Done: IOhannes m zmölnig (Debian/GNU) }
[src:juce] juce: ftbfs with GCC-12
Bug #1012947 {Done: IOhannes m zmölnig (Debian/GNU) }
[src:juce] iem-plugin-suite: ftbfs with GCC-12
Added indication that 1012954 affects src:iem-plugin-suite
Added indication that 1012947 affects src:iem-plugin-suite
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1012947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012947
1012954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012954
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: reassign 1013573 to python3-djangorestframework ..., affects 1013573, fixed 1013573 in 3.13.1-1
Processing commands for cont...@bugs.debian.org:
> reassign 1013573 python3-djangorestframework
Bug #1013573 [src:djangorestframework-filters] djangorestframework-filters:
FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p
"3.9 3.10" returned exit code 13
Bug reassigned from package 'src:djangorestframework-filters' to
'python3-djangorestframework'.
No longer marked as found in versions djangorestframework-filters/1.0.0.dev2-1.
Ignoring request to alter fixed versions of bug #1013573 to the same values
previously set
> retitle 1013573 djangorestframework-filters: FTBFS: missing python3-tz
> Depends in python3-djangorestframework
Bug #1013573 [python3-djangorestframework] djangorestframework-filters: FTBFS:
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9
3.10" returned exit code 13
Changed Bug title to 'djangorestframework-filters: FTBFS: missing python3-tz
Depends in python3-djangorestframework' from 'djangorestframework-filters:
FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p
"3.9 3.10" returned exit code 13'.
> affects 1013573 + djangorestframework-filters
Bug #1013573 [python3-djangorestframework] djangorestframework-filters: FTBFS:
missing python3-tz Depends in python3-djangorestframework
Added indication that 1013573 affects djangorestframework-filters
> fixed 1013573 3.13.1-1
Bug #1013573 [python3-djangorestframework] djangorestframework-filters: FTBFS:
missing python3-tz Depends in python3-djangorestframework
Marked as fixed in versions djangorestframework/3.13.1-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1013573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013573
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: severity update
Processing commands for cont...@bugs.debian.org: > severity 1017536 important Bug #1017536 [src:eiciel] eiciel: Incompatible with Nautilus 43 Severity set to 'important' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 1017536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017536 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017539: haskell-foundation: FTBFS on armel
Source: haskell-foundation
Version: 0.0.28-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=haskell-foundation=armel=0.0.28-1=1660672213=0
BlockN
Multiple n
[32;1m ✓ [0mn = CountOf 0 (4 tests)
[32;1m ✓ [0mn = CountOf 1 (4 tests)
[32;1m ✓ [0mn = CountOf 2 (4 tests)
[32;1m ✓ [0mn = CountOf 3 (4 tests)
[32;1m ✓ [0mn = CountOf 4 (4 tests)
[32;1m ✓ [0mn = CountOf 5 (4 tests)
[32;1m ✓ [0mn = CountOf 6 (4 tests)
[32;1m ✓ [0mn = CountOf 7 (4 tests)
[32;1m ✓ [0mn = CountOf 8 (4 tests)
[32;1m ✓ [0mn = CountOf 33 (4 tests)
[32;1m ✓ [0mn = CountOf 42 (4 tests)
Format
CSV
[32;1m ✓ [0mfield unit tests (9 tests)
[32;1m ✓ [0mrow unit tests (6 tests)
[32;1m ✓ [0mrow unit tests (6 tests)
[32;1m ✓ [0mrecord . toRow == id (400 tests)
[31;1mFailed 9 out of 6121[0m
Test suite check-foundation: FAIL
Test suite logged to: dist-ghc/test/foundation-0.0.28-check-foundation.log
0 of 1 test suites (0 of 1 test cases) passed.
-e: error: debian/hlibrary.setup test --builddir=dist-ghc --show-details=direct
returned exit code 1
at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 852.
Debian::Debhelper::Dh_Lib::error("debian/hlibrary.setup test
--builddir=dist-ghc --show-details"...) called at
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 596
Debian::Debhelper::Dh_Lib::error_exitcode("debian/hlibrary.setup test
--builddir=dist-ghc --show-details"...) called at
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 470
Debian::Debhelper::Dh_Lib::doit("debian/hlibrary.setup", "test",
"--builddir=dist-ghc", "--show-details=direct") called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 686
Debian::Debhelper::Buildsystem::Haskell::Recipes::check_recipe() called
at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:165: check-ghc-stamp] Error 25
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit
status 2
Cheers
--
Sebastian Ramacher
Bug#1017537: dietlibc: FTBFS on armel: illegal instruction
Source: dietlibc Version: 0.34~cvs20160606-14 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=dietlibc=armel=0.34%7Ecvs20160606-14=1658293281=0 RUN ERROR for debian/unittests/tc523086.c in variant pthreads (rc = 132), test output is: Illegal instruction RUN ERROR for debian/unittests/t-ascii1.c in variant pthreads (rc = 132), test output is: Illegal instruction RUN ERROR for debian/unittests/signal.c in variant pthreads (rc = 132), test output is: Illegal instruction RUN ERROR for debian/unittests/gettimeofday.c in variant pthreads (rc = 132), test output is: Illegal instruction RUN ERROR for debian/unittests/socketfns.c in variant pthreads (rc = 132), test output is: Illegal instruction RUN ERROR for test/bsearch.c in variant pthreads (rc = 132), test output is: Illegal instruction RUN ERROR for test/fadvise.c in variant pthreads (rc = 132), test output is: Illegal instruction RUN ERROR for test/mmap_test.c in variant pthreads (rc = 132), test output is: Illegal instruction RUN ERROR for test/stdarg.c in variant pthreads (rc = 132), test output is: Illegal instruction RUN ERROR for test/ungetc.c in variant pthreads (rc = 132), test output is: Illegal instruction RUN ERROR for test/utime.c in variant pthreads (rc = 132), test output is: Illegal instruction RUN ERROR for test/waitpid.c in variant pthreads (rc = 132), test output is: Illegal instruction RUN ERROR for test/dirent/opendir-tst1.c in variant pthreads (rc = 132), test output is: Illegal instruction RUN ERROR for test/stdlib/tst-calloc.c in variant pthreads (rc = 132), test output is: Illegal instruction make[1]: *** [debian/rules:105: override_dh_auto_test-arch] Error 1 make[1]: Leaving directory '/<>' Cheers -- Sebastian Ramacher
Bug#1017538: dietlibc: FTBFS on armhf: selected processor does not support vldm in ARM mode
Source: dietlibc
Version: 0.34~cvs20160606-14
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=dietlibc=armhf=0.34%7Ecvs20160606-14=1658252860=0
arm/__longjmp.S: Assembler messages:
arm/__longjmp.S:9: Error: selected processor does not support `vldm
ip!,{d0-d15}' in ARM mode
make[2]: *** [Makefile:206: bin-arm/__longjmp.o] Error 1
make[2]: *** Waiting for unfinished jobs
: -x -R .comment -R .note bin-arm/realpath.o
: -x -R .comment -R .note bin-arm/fnmatch.o
: -x -R .comment -R .note bin-arm/glob.o
: -x -R .comment -R .note bin-arm/sha256crypt.o
: -x -R .comment -R .note bin-arm/rx.o
: -x -R .comment -R .note bin-arm/sha512crypt.o
make[2]: Leaving directory '/<>'
dh_auto_build: error: make -j8 "INSTALL=install --strip-program=true"
prefix=/usr/lib/arm-linux-gnueabihf/diet MYARCH=arm
VERSION=0.34\~cvs20160606-14 DEBUG=1 "CFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2 -g
-O2 -ffile-prefix-map=/<>=.
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat
-Werror=format-security -Wall -fno-pie -specs=/usr/share/dpkg/no-pie-link.specs
-Wl,-z,relro -Wl,-z,now -no-pie -pipe -nostdinc -D_REENTRANT -Os
-fomit-frame-pointer -fstrict-aliasing -W -Wall -Wextra -Wchar-subscripts
-Wmissing-prototypes -Wmissing-declarations -Wno-switch -Wno-unused
-Wredundant-decls -Wshadow" returned exit code 2
make[1]: *** [debian/rules:94: override_dh_auto_build-arch] Error 25
Cheers
--
Sebastian Ramacher
Bug#1017528: marked as done (aborts at startup: Using libsoup2 and libsoup3 in the same process is not supported)
Your message dated Wed, 17 Aug 2022 16:40:31 + with message-id and subject line Bug#1017528: fixed in libgda5 5.2.10-3 has caused the Debian Bug report #1017528, regarding aborts at startup: Using libsoup2 and libsoup3 in the same process is not supported 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.) -- 1017528: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017528 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gtranslator Version: 42.0-1 Severity: grave On an up to date unstable, gtranslator aborts at startup: (gtranslator:58389): libsoup-ERROR **: 13:25:11.006: libsoup3 symbols detected. Using libsoup2 and libsoup3 in the same process is not supported. zsh: trace trap (core dumped) gtranslator bg.po Surprisingly, ldd doesn't show libsoup2 in the linked libraries: $ ldd /usr/bin/gtranslator|grep soup libsoup-3.0.so.0 => /usr/lib/x86_64-linux-gnu/libsoup-3.0.so.0 (0x7fb803048000) -- Damyan -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-4-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gtranslator depends on: ii dconf-gsettings-backend [gsettings-backend] 0.40.0-3 ii gsettings-desktop-schemas42.0-1 ii iso-codes4.11.0-1 ii libatk1.0-0 2.38.0-1 ii libc62.34-4 ii libcairo21.16.0-6 ii libgda-5.0-4 5.2.10-2 ii libgettextpo00.21-8 ii libglib2.0-0 2.72.3-1+b1 ii libgspell-1-21.11.1-1 ii libgtk-3-0 3.24.34-1 ii libgtksourceview-4-0 4.8.3-1 ii libhandy-1-0 1.7.90-1 ii libjson-glib-1.0-0 1.6.6-1 ii libpango-1.0-0 1.50.9+ds-1 ii libsoup-3.0-03.1.3-1 ii libxml2 2.9.14+dfsg-1+b1 gtranslator recommends no packages. Versions of packages gtranslator suggests: pn libpeas-1.0-python2loader -- debconf-show failed --- End Message --- --- Begin Message --- Source: libgda5 Source-Version: 5.2.10-3 Done: Jeremy Bicha We believe that the bug you reported is fixed in the latest version of libgda5, 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 1017...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Bicha (supplier of updated libgda5 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: Wed, 17 Aug 2022 12:02:38 -0400 Source: libgda5 Built-For-Profiles: noudeb Architecture: source Version: 5.2.10-3 Distribution: unstable Urgency: high Maintainer: Debian GNOME Maintainers Changed-By: Jeremy Bicha Closes: 1017528 Changes: libgda5 (5.2.10-3) unstable; urgency=high . * Stop building with libsoup2.4. This drops the web provider (Closes: #1017528) Checksums-Sha1: 4b59ef21a8e2584905a13692831eba4382642019 2987 libgda5_5.2.10-3.dsc 96eb1eed1bb1f5ac7007b7b415c321d1c0c07dba 25864 libgda5_5.2.10-3.debian.tar.xz 42d347241f6f3041b0c8b297a49bbd3c4f5dc7a2 11296 libgda5_5.2.10-3_source.buildinfo Checksums-Sha256: e514498675f541c19f4dd703fb573456ea5379a53003f79c09e2d7564f29d9b6 2987 libgda5_5.2.10-3.dsc 12f408d4c0c4315f6580c7ea660f38467f28910ca348bfbc63906cd14c5a93d2 25864 libgda5_5.2.10-3.debian.tar.xz 1f373d41e1ed7af9be7ac15abf6fa55e0f86e63ee298d7468e6d3df5186f6281 11296 libgda5_5.2.10-3_source.buildinfo Files: e6aecb0a7b9428963a6209c1f2b6f111 2987 libs optional libgda5_5.2.10-3.dsc 019c5eb023b91cfd98a031929ac76d20 25864 libs optional
Bug#1017536: eiciel: Incompatible with Nautilus 43
Source: eiciel Severity: serious Version: 0.9.13.1-1 Tags: sid bookworm eiciel is incompatible with Nautilus 43. It would need to be converted to GTK4 to continue to work. Thank you, Jesus Soto
Processed: Re: Bug#1017528: aborts at startup: Using libsoup2 and libsoup3 in the same process is not supported
Processing commands for cont...@bugs.debian.org: > affects 1017528 src:gtranslator Bug #1017528 [src:libgda5] aborts at startup: Using libsoup2 and libsoup3 in the same process is not supported Added indication that 1017528 affects src:gtranslator > End of message, stopping processing here. Please contact me if you need assistance. -- 1017528: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017528 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1017528: aborts at startup: Using libsoup2 and libsoup3 in the same process is not supported
Processing commands for cont...@bugs.debian.org: > reassign 1017528 src:libgda5 5.2.10-2 Bug #1017528 [gtranslator] aborts at startup: Using libsoup2 and libsoup3 in the same process is not supported Bug reassigned from package 'gtranslator' to 'src:libgda5'. No longer marked as found in versions gtranslator/42.0-1. Ignoring request to alter fixed versions of bug #1017528 to the same values previously set Bug #1017528 [src:libgda5] aborts at startup: Using libsoup2 and libsoup3 in the same process is not supported Marked as found in versions libgda5/5.2.10-2. > End of message, stopping processing here. Please contact me if you need assistance. -- 1017528: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017528 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017375: liblexical-accessor-perl: test failure with Sub::HandlesVia 0.034
On Mon, 15 Aug 2022 05:26:39 +, Damyan Ivanov wrote:
> t/30shv.t fails with:
>
> Usage: Sub::HandlesVia::CodeGenerator::method_installer(self) at
> .../lib/Sub/HandlesVia/Toolkit/SubAccessorSmall.pm line 58.
>
> In version 0.034, Sub::HandlesVia::CodeGenerator's method_installer field
> is read-only and the above line tries to modify it:
>
> $gen->method_installer( sub {
> my ( $method_name, $coderef ) = @_;
> my $real_destination = $handles_map->{$method_name};
> $realattr->install_coderef( $real_destination, $coderef );
> } );
This should be fixed with libsub-handlesvia-perl 0.035, judging from
the following upstream commit:
commit 8c5799169c61a4c7aec65df51997a42bbecb8bd5
Author: Toby Inkster
Date: Fri Aug 12 15:40:49 2022 +0100
Make the CodeGenerator's method_installer an rw attribute
diff --git a/lib/Sub/HandlesVia/CodeGenerator.pm
b/lib/Sub/HandlesVia/CodeGenerator.pm
index c9d353b..586ca9b 100644
--- a/lib/Sub/HandlesVia/CodeGenerator.pm
+++ b/lib/Sub/HandlesVia/CodeGenerator.pm
@@ -156,7 +156,7 @@ has generator_for_type_assertion => (
);
has method_installer => (
- is => ro,
+ is => rw,
isa => 'CodeRef',
);
Also Changes say:
- Sub::HandlesVia::CodeGenerator method_installer is now a rw attribute as
Sub::Accessor::Small was relying on that.
I'm going to upload libsub-handlesvia-perl now, then we can depend on
the fixed version to close this bug, I guess?
Cheers,
gregor
--
.''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org
: :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06
`. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
`-
signature.asc
Description: Digital Signature
Processed: rsync: The --remove-source-files destroys data when source & destination are the same (data loss!)
Processing commands for cont...@bugs.debian.org: > forwarded 1016102 https://github.com/WayneD/rsync/issues/359 Bug #1016102 [rsync] rsync: The --remove-source-files destroys data when source & destination are the same (data loss!) Set Bug forwarded-to-address to 'https://github.com/WayneD/rsync/issues/359'. > -- Stopping processing here. Please contact me if you need assistance. -- 1016102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016102 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000796: marked as pending in base-passwd
Hi, On 17-08-2022 13:16, Colin Watson wrote: On Sun, Aug 14, 2022 at 11:27:47PM +0200, Paul Gevers wrote: On Thu, 03 Mar 2022 00:42:14 + Colin Watson wrote: Bug #1000796 in base-passwd reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/base-passwd/-/commit/06ed6f49253ff244dc9cbcadc840fdf611f11462 Can we have this uploaded to unstable please? Pending RC bugs for 5 months are a bit awkward. Uploaded now - sorry for the delay. Thank you. Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: affects 1012021, merging 1012021 1017471
Processing commands for cont...@bugs.debian.org: > affects 1012021 Bug #1012021 [src:greenbone-security-assistant] yarnpkg: segfault while building greenbone-security-assistant on !amd64 Removed indication that 1012021 affects src:greenbone-security-assistant > merge 1012021 1017471 Bug #1012021 [src:greenbone-security-assistant] yarnpkg: segfault while building greenbone-security-assistant on !amd64 Bug #1012021 [src:greenbone-security-assistant] yarnpkg: segfault while building greenbone-security-assistant on !amd64 Marked as found in versions greenbone-security-assistant/21.4.4-1. Bug #1017471 [src:greenbone-security-assistant] greenbone-security-assistant connects to the internet during build Merged 1012021 1017471 > thanks Stopping processing here. Please contact me if you need assistance. -- 1012021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012021 1017471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017471 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): reassign 1012021 to src:greenbone-security-assistant, tagging 1012021, merging 1012021 1017471
Processing commands for cont...@bugs.debian.org: > reassign 1012021 src:greenbone-security-assistant Bug #1012021 [webpack] yarnpkg: segfault while building greenbone-security-assistant on !amd64 Bug reassigned from package 'webpack' to 'src:greenbone-security-assistant'. Ignoring request to alter found versions of bug #1012021 to the same values previously set Ignoring request to alter fixed versions of bug #1012021 to the same values previously set > tags 1012021 - moreinfo Bug #1012021 [src:greenbone-security-assistant] yarnpkg: segfault while building greenbone-security-assistant on !amd64 Removed tag(s) moreinfo. > merge 1012021 1017471 Bug #1012021 [src:greenbone-security-assistant] yarnpkg: segfault while building greenbone-security-assistant on !amd64 Unable to merge bugs because: affects of #1017471 is '' not 'src:greenbone-security-assistant' Failed to merge 1012021: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1012021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012021 1017471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017471 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995640: boxbackup: FTBFS with OpenSSL 3.0
On Wed, Aug 17, 2022 at 05:54:53PM +0300, Ileana Dumitrescu wrote: > > I made the attached patch, which causes the package to build and run on > both openssl 3.x and pre-3.x systems. > > Thank you for the patch! I will add it to the next debian upload. > > > Note, however, that on openssl 3.x systems, a number of the tests run at > > build time still fail with: > > > FAILED: Exception caught: TLSServerWeakCertificate: Failed to load > > certificates from testfiles/clientCerts.pem: hash too weak for current > > security level > > > but that is for a different reason: the pre-built certificates bundled > > with the source package for running the tests use the > > now-deemed-insecure SHA1 hash. > > > Nonetheless, the package builds, and works fine at runtime, assuming > > you've upgraded your certs to sha256 as recommended here: > > I am also still seeing this error during the tests, which fails the build > overall. If the package still works fine at runtime, I will look into > patching the failed tests so that this can make it into the stable > repository. Well, the preferred thing would be to just generate new sha256 certs to bundle with the test suite, so that the tests pass. I didn't see a script to auto-generate all the needed certs, but there is a file ./test/basicserver/testfiles/key-creation.txt that has instructions for at least some of them. But the ubuntu version of the package does successfully build the deb files, even if some of the tests fail. The changelog says: boxbackup (0.13~~git20200326.g8e8b63c-1ubuntu1) groovy; urgency=medium * Merge from Debian unstable. Remaining changes: - Ignore test suite results, always fails, not run on most arches anyway. -- Gianfranco Costamagna Mon, 11 May 2020 16:11:17 +0200
Bug#1013039: marked as done (skypat: ftbfs with GCC-12)
Your message dated Wed, 17 Aug 2022 15:17:40 + with message-id and subject line Bug#1013039: fixed in skypat 3.1.1-6 has caused the Debian Bug report #1013039, regarding skypat: ftbfs with GCC-12 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.) -- 1013039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013039 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:skypat Version: 3.1.1-5 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-12 [This bug is targeted to the upcoming bookworm release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The severity of this report will be raised before the bookworm release. The full build log can be found at: http://qa-logs.debian.net/2022/06/09/gcc12/skypat_3.1.1-5_unstable_gcc12.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] echo -e 'INCDIR=../../../../include\nLIBDIR=../../../../lib\nrun: skypat_c\n LD_LIBRARY_PATH=$(LIBDIR) ./$<\nskypat_c: main.cpp my_case.cpp\n$(CXX) -I$(INCDIR) -L$(LIBDIR) $^ -fno-rtti -lskypat -o $@\nclean:\nrm -f skypat_c\n' > SampleMakefile /bin/mkdir -p '/<>/debian/tmp/usr/share/skypat/examples/skypat_c' /usr/bin/install -c -m 644 main.cpp my_case.h my_case.cpp SampleMakefile '/<>/debian/tmp/usr/share/skypat/examples/skypat_c' make install-data-hook make[5]: Entering directory '/<>/examples/skypat_c' cd /<>/debian/tmp/usr/share/skypat/examples/skypat_c && mv SampleMakefile Makefile make[5]: Leaving directory '/<>/examples/skypat_c' make[4]: Leaving directory '/<>/examples/skypat_c' make[3]: Leaving directory '/<>/examples/skypat_c' Making install in thread make[3]: Entering directory '/<>/examples/thread' echo -e 'INCDIR=../../../../include\nLIBDIR=../../../../lib\nrun: thread\n LD_LIBRARY_PATH=$(LIBDIR) ./$<\nthread: main.cpp\n $(CXX) -I$(INCDIR) -L$(LIBDIR) $^ -fno-rtti -lskypat -o $@\nclean:\nrm -f thread\n' > SampleMakefile make[4]: Entering directory '/<>/examples/thread' make[4]: Nothing to be done for 'install-exec-am'. echo -e 'INCDIR=../../../../include\nLIBDIR=../../../../lib\nrun: thread\n LD_LIBRARY_PATH=$(LIBDIR) ./$<\nthread: main.cpp\n $(CXX) -I$(INCDIR) -L$(LIBDIR) $^ -fno-rtti -lskypat -o $@\nclean:\nrm -f thread\n' > SampleMakefile /bin/mkdir -p '/<>/debian/tmp/usr/share/skypat/examples/thread' /usr/bin/install -c -m 644 main.cpp ThreadTest.h SampleMakefile '/<>/debian/tmp/usr/share/skypat/examples/thread' make install-data-hook make[5]: Entering directory '/<>/examples/thread' cd /<>/debian/tmp/usr/share/skypat/examples/thread && mv SampleMakefile Makefile make[5]: Leaving directory '/<>/examples/thread' make[4]: Leaving directory '/<>/examples/thread' make[3]: Leaving directory '/<>/examples/thread' make[3]: Entering directory '/<>/examples' make[4]: Entering directory '/<>/examples' make[4]: Nothing to be done for 'install-exec-am'. make[4]: Nothing to be done for 'install-data-am'. make[4]: Leaving directory '/<>/examples' make[3]: Leaving directory '/<>/examples' make[2]: Leaving directory '/<>/examples' make[2]: Entering directory '/<>' make[3]: Entering directory '/<>' make[3]: Nothing to be done for 'install-exec-am'. /bin/mkdir -p '/<>/debian/tmp/usr/share/skypat' /usr/bin/install -c -m 644 ./LICENSE ./README.md '/<>/debian/tmp/usr/share/skypat' make[3]: Leaving directory '/<>' make[2]: Leaving directory '/<>' make[1]: Leaving directory '/<>' dh_install dh_installdocs dh_installchangelogs dh_installexamples
Bug#1016220: marked as done (sssd: FTBFS: dh_install: error: missing files, aborting)
Your message dated Wed, 17 Aug 2022 15:18:01 +
with message-id
and subject line Bug#1016220: fixed in sssd 2.7.3-2
has caused the Debian Bug report #1016220,
regarding sssd: FTBFS: dh_install: error: missing files, aborting
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.)
--
1016220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sssd
Version: 2.7.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220728 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> install -D -m755 /<>/debian/generate-config \
> /<>/debian/tmp/usr/share/sssd/generate-config
> mkdir -p /<>/debian/libpam-sss/usr/share/pam-configs
> install -m644 debian/libpam-sss.pam-auth-update \
> /<>/debian/libpam-sss/usr/share/pam-configs/sss
> install -m644 -D /<>/debian/apparmor-profile \
> /<>/debian/sssd-common/etc/apparmor.d/usr.sbin.sssd
> cat /<>/debian/sssd-common.sssd.init.in >
> /<>/debian/sssd-common.sssd.init
> # remove files we don't want to install
> find /<>/debian/tmp/ -name '*.la' -exec rm '{}' ';'
> find /<>/debian/tmp/ -name '*.pyc' -exec rm '{}' ';'
> find /<>/debian/tmp/ -name '*.egg-info' -exec rm '{}' ';'
> rm -f /<>/debian/tmp/etc/rc.d/init.d/sssd
> # match nn/nn/, replace with the date from changelog
> sed -i 's/[0-1][0-9]\/[0-3][0-9]\/[0-9][0-9][0-9][0-9]/07\/06\/2022/g'
> /<>/debian/tmp/usr/share/man/man*/*
> # change the shebang
> sed -i -e 's:/usr/bin/python:/usr/bin/python3:'
> /<>/debian/tmp/usr/sbin/sss_obfuscate
> mkdir -p debian/tmp/etc/krb5.conf.d
> # Enable krb5 idp plugins by default (when sssd-idp package is installed)
> cp debian/tmp/usr/share/sssd/krb5-snippets/sssd_enable_idp \
> debian/tmp/etc/krb5.conf.d/sssd_enable_idp
> # Kerberos KCM credential cache by default
> cp debian/tmp/usr/share/sssd-kcm/kcm_default_ccache \
> debian/tmp/etc/krb5.conf.d/kcm_default_ccache
> # krb5 configuration snippet
> cp debian/tmp/usr/share/sssd/krb5-snippets/enable_sssd_conf_dir \
> debian/tmp/etc/krb5.conf.d/enable_sssd_conf_dir
> dh_install
> dh_install: warning: Cannot find (any matches for)
> "usr/lib/*/krb5/plugins/authdata/sssd_pac_plugin.so" (tried in ., debian/tmp)
>
> dh_install: warning: sssd-common missing files:
> usr/lib/*/krb5/plugins/authdata/sssd_pac_plugin.so
> dh_install: warning: Cannot find (any matches for)
> "lib/systemd/system/sssd-pac.service" (tried in ., debian/tmp)
>
> dh_install: warning: sssd-ad-common missing files:
> lib/systemd/system/sssd-pac.service
> dh_install: warning: Cannot find (any matches for)
> "lib/systemd/system/sssd-pac.socket" (tried in ., debian/tmp)
>
> dh_install: warning: sssd-ad-common missing files:
> lib/systemd/system/sssd-pac.socket
> dh_install: warning: Cannot find (any matches for)
> "usr/libexec/sssd/sssd_pac" (tried in ., debian/tmp)
>
> dh_install: warning: sssd-ad-common missing files: usr/libexec/sssd/sssd_pac
> dh_install: error: missing files, aborting
> make[1]: *** [debian/rules:87: override_dh_install] Error 25
The full build log is available from:
http://qa-logs.debian.net/2022/07/28/sssd_2.7.3-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220728;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220728=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: sssd
Source-Version: 2.7.3-2
Done: Timo Aaltonen
We believe that the bug you reported is fixed in the latest version of
sssd, 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 1016...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance
Bug#1013023: marked as done (qt6-webengine: ftbfs with GCC-12)
Your message dated Wed, 17 Aug 2022 15:14:38 +
with message-id
and subject line Bug#1013023: fixed in qt6-webengine 6.3.1+dfsg2-11
has caused the Debian Bug report #1013023,
regarding qt6-webengine: ftbfs with GCC-12
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.)
--
1013023: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013023
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:qt6-webengine
Version: 6.2.4+dfsg-8
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12
[This bug is targeted to the upcoming bookworm release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The
severity of this report will be raised before the bookworm release.
The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/qt6-webengine_6.2.4+dfsg-8_unstable_gcc12.log
The last lines of the build log are at the end of this report.
To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html
GCC 11 defaults to the GNU++17 standard. If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.
[...]
+#MISSING: 6.2.4+dfsg-8#
_ZTVSt23_Sp_counted_ptr_inplaceINSt8__detail4_NFAINSt7__cxx1112regex_traitsIcSaIS5_ELN9__gnu_cxx12_Lock_policyE2EE@Base
6.2.2
+
_ZTVSt23_Sp_counted_ptr_inplaceINSt8__detail4_NFAINSt7__cxx1112regex_traitsIcSaIvELN9__gnu_cxx12_Lock_policyE2EE@Base
6.2.4+dfsg-8
+#MISSING: 6.2.4+dfsg-8#
_ZTVSt23_Sp_counted_ptr_inplaceISt6atomicIbESaIS1_ELN9__gnu_cxx12_Lock_policyE2EE@Base
6.2.2
+
_ZTVSt23_Sp_counted_ptr_inplaceISt6atomicIbESaIvELN9__gnu_cxx12_Lock_policyE2EE@Base
6.2.4+dfsg-8
+#MISSING: 6.2.4+dfsg-8#
_ZTVSt23_Sp_counted_ptr_inplaceISt6vectorIhSaIhEESaIS2_ELN9__gnu_cxx12_Lock_policyE2EE@Base
6.2.2
+
_ZTVSt23_Sp_counted_ptr_inplaceISt6vectorIhSaIhEESaIvELN9__gnu_cxx12_Lock_policyE2EE@Base
6.2.4+dfsg-8
+#MISSING: 6.2.4+dfsg-8#
_ZTVSt23_Sp_counted_ptr_inplaceIbSaIbELN9__gnu_cxx12_Lock_policyE2EE@Base 6.2.2
+ _ZTVSt23_Sp_counted_ptr_inplaceIbSaIvELN9__gnu_cxx12_Lock_policyE2EE@Base
6.2.4+dfsg-8
(optional=templinst)_ZZN9QMetaType21registerConverterImplI5QListI4QUrlE9QIterableI13QMetaSequenceEEEbSt8functionIFbPKvPvEES_S_E10unregister@Base
6.2.2
(optional=templinst)_ZZN9QMetaType23registerMutableViewImplI5QListI4QUrlE9QIterableI13QMetaSequenceEEEbSt8functionIFbPvS8_EES_S_E10unregister@Base
6.2.2
(optional=templinst)_ZZN9QtPrivate16QMetaTypeForTypeI10QByteArrayE10getCopyCtrEvENUlPKNS_18QMetaTypeInterfaceEPvPKvE_4_FUNES5_S6_S8_@Base
6.2.2
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see
diff output below
dpkg-gensymbols: warning: debian/libqt6pdf6/DEBIAN/symbols doesn't match
completely debian/libqt6pdf6.symbols
--- debian/libqt6pdf6.symbols (libqt6pdf6_6.2.4+dfsg-8_amd64)
+++ dpkg-gensymbols6BY4x_ 2022-06-10 11:42:31.936105370 +
@@ -213,7 +213,7 @@
(optional=templinst)_ZNSt6vectorI18UnsupportedFeatureSaIS0_EE17_M_realloc_insertIJS0_EEEvN9__gnu_cxx17__normal_iteratorIPS0_S2_EEDpOT_@Base
6.2.2
(optional=templinst)_ZNSt6vectorIN10CPDF_Annot7SubtypeESaIS1_EE17_M_realloc_insertIJS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
6.2.2
(optional=templinst)_ZNSt6vectorISt4pairIiiESaIS1_EE17_M_realloc_insertIJS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
6.2.2
-
(optional=templinst)_ZNSt6vectorISt4pairIjxESaIS1_EE17_M_realloc_insertIJjxEEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
6.2.4
+#MISSING: 6.2.4+dfsg-8#
(optional=templinst)_ZNSt6vectorISt4pairIjxESaIS1_EE17_M_realloc_insertIJjxEEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
6.2.4
(optional=templinst|subst)_ZNSt6vectorIbSaIbEE14_M_fill_insertESt13_Bit_iterator{size_t}b@Base
6.2.2
Bug#995640: boxbackup: FTBFS with OpenSSL 3.0
> I made the attached patch, which causes the package to build and run on both openssl 3.x and pre-3.x systems. Thank you for the patch! I will add it to the next debian upload. > Note, however, that on openssl 3.x systems, a number of the tests run at > build time still fail with: > FAILED: Exception caught: TLSServerWeakCertificate: Failed to load > certificates from testfiles/clientCerts.pem: hash too weak for current > security level > but that is for a different reason: the pre-built certificates bundled > with the source package for running the tests use the > now-deemed-insecure SHA1 hash. > Nonetheless, the package builds, and works fine at runtime, assuming > you've upgraded your certs to sha256 as recommended here: I am also still seeing this error during the tests, which fails the build overall. If the package still works fine at runtime, I will look into patching the failed tests so that this can make it into the stable repository. Ileana Dumitrescu GPG Public Key: FA26 CA78 4BE1 8892 7F22 B99F 6570 EA01 146F 7354
Bug#1016133: marked as done (fpga-icestorm: autopkgtest regression: new test can't be run on s390x due to missing yosys)
Your message dated Wed, 17 Aug 2022 14:49:05 + with message-id and subject line Bug#1016133: fixed in fpga-icestorm 0~20220603git2bc5417-2 has caused the Debian Bug report #1016133, regarding fpga-icestorm: autopkgtest regression: new test can't be run on s390x due to missing yosys 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.) -- 1016133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016133 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fpga-icestorm Version: 0~20220603git2bc5417-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of fpga-icestorm the autopkgtest of fpga-icestorm fails in testing when that autopkgtest is run with the binary packages of fpga-icestorm from unstable. It passes when run with only packages from testing. In tabular form: passfail fpga-icestorm from testing0~20220603git2bc5417-1 all others from testingfrom testing I copied some of the output at the bottom of this report. It seems to need to mark your new test to be not executed on s390x. You can do so by adding an "Architecture: !s390x" line to the new test definition in d/t/control. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=fpga-icestorm https://ci.debian.net/data/autopkgtest/testing/s390x/f/fpga-icestorm/24083107/log.gz Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) autopkgtest-satdep:s390x < 0 @iU K Nb Ib > Broken autopkgtest-satdep:s390x Depends on yosys:s390x < none @un H > Removing autopkgtest-satdep:s390x because I can't find yosys:s390x Done OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: fpga-icestorm Source-Version: 0~20220603git2bc5417-2 Done: Daniel Gröber We believe that the bug you reported is fixed in the latest version of fpga-icestorm, 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 1016...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Gröber (supplier of updated fpga-icestorm 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, 30 Jul 2022 17:11:11 +0200 Source: fpga-icestorm Architecture: source Version: 0~20220603git2bc5417-2 Distribution: unstable Urgency: medium Maintainer: Debian Electronics Team Changed-By: Daniel Gröber Closes: 1016133 Changes: fpga-icestorm (0~20220603git2bc5417-2) unstable; urgency=medium . * Disable autopkgtest on s390x due to missing yosys (Closes: #1016133) * Override lintian false-positive Checksums-Sha1: 0ae948af446844796fdd3958106d99f9adfc5c1a 2324 fpga-icestorm_0~20220603git2bc5417-2.dsc 08b5bb4d81ea064ab15deb75f0e357598c687653 9904 fpga-icestorm_0~20220603git2bc5417-2.debian.tar.xz 2653739ebb0252737e39afec57cbd0e43cffcdae 7311 fpga-icestorm_0~20220603git2bc5417-2_source.buildinfo Checksums-Sha256: 1afcfd4f903aa21b69f5179a54ac67a473ac3c8407ba398b2b54b8885b95e66a 2324 fpga-icestorm_0~20220603git2bc5417-2.dsc f80d01800f6eaa5484a24506feda5dfcc1fd3544b2b441b2be9b2888f8a56079 9904 fpga-icestorm_0~20220603git2bc5417-2.debian.tar.xz f8e9a1526137a307833302d8d64edf9257194d7ad139381adcc645cfd5a5d0af 7311 fpga-icestorm_0~20220603git2bc5417-2_source.buildinfo Files: 127517fd0f572ac8154c039889b41fa2 2324 electronics optional fpga-icestorm_0~20220603git2bc5417-2.dsc d929c36a8284451ec749b5919c2281ba 9904 electronics optional fpga-icestorm_0~20220603git2bc5417-2.debian.tar.xz 92ac200f12a49a6563244f15dd9ca56f 7311 electronics optional fpga-icestorm_0~20220603git2bc5417-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE3z4uQkp+J5wuSwI6ucKa7rL0UKcFAmL88xUACgkQucKa7rL0 UKcwSBAAhbEAicdolbIaf6ybUPtXoZ7StVb61mImHjTYigTU5wTCo0DxkmTtl4// hAw0egX5go8WqNYV/6ayZN9qxDy0jZ+yI42a2/37VhB4mm0Yk2BW5nb9JAFQ62Wy
Bug#1017379: marked as done (nm-openvpn: capng_change_id() failed applying capabilities: Operation not permitted (errno=1))
Your message dated Wed, 17 Aug 2022 13:53:57 + with message-id and subject line Bug#1017379: fixed in openvpn 2.6.0~git20220811-2 has caused the Debian Bug report #1017379, regarding nm-openvpn: capng_change_id() failed applying capabilities: Operation not permitted (errno=1) 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.) -- 1017379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017379 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: network-manager-openvpn Version: 1.8.18-3 Severity: important I upgraded some packages today and since then, I cannot connect to VPNs anymore. * network-manager: 1.38.2-1 --> 1.38.4-1 * systemd: 251.3-1 --> 251.4-1 The connection seems to be successful at first, but then an error occurs (IP addresses replaced by 1.2.3.4): Aug 15 09:24:45 myhostname nm-openvpn[11804]: OpenVPN 2.6_git x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] Aug 15 09:24:45 myhostname nm-openvpn[11804]: library versions: OpenSSL 3.0.5 5 Jul 2022, LZO 2.10 Aug 15 09:24:45 myhostname nm-openvpn[11804]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Aug 15 09:24:45 myhostname nm-openvpn[11804]: TCP/UDP: Preserving recently used remote address: [AF_INET]1.2.3.4:1200 Aug 15 09:24:45 myhostname nm-openvpn[11804]: UDPv4 link local: (not bound) Aug 15 09:24:45 myhostname nm-openvpn[11804]: UDPv4 link remote: [AF_INET]1.2.3.4:1200 Aug 15 09:24:45 myhostname nm-openvpn[11804]: NOTE: chroot will be delayed because of --client, --pull, or --up-delay Aug 15 09:24:45 myhostname nm-openvpn[11804]: NOTE: UID/GID downgrade will be delayed because of --client, --pull, or --up-delay Aug 15 09:24:46 myhostname nm-openvpn[11804]: [fws-kef] Peer Connection Initiated with [AF_INET]1.2.3.4:1200 Aug 15 09:24:46 myhostname nm-openvpn[11804]: sitnl_send: rtnl: generic error (-17): File exists Aug 15 09:24:46 myhostname nm-openvpn[11804]: DCO device tun1 opened Aug 15 09:24:46 myhostname nm-openvpn[11804]: /usr/lib/NetworkManager/nm-openvpn-service-openvpn-helper --debug 0 11799 --bus-name org.freedesktop.NetworkManager.openvpn.Connection_6 --tun -- tun1 1500 0 1.2.3.4 1.2.3.4 init Aug 15 09:24:46 myhostname NetworkManager[1051]: [1660548286.3476] manager: (tun1): new Generic device (/org/freedesktop/NetworkManager/Devices/12) Aug 15 09:24:46 myhostname kded5[3196]: org.kde.plasma.nm.kded: Unhandled VPN connection state change: 4 Aug 15 09:24:46 myhostname NetworkManager[1051]: [1660548286.3784] device (tun1): carrier: link connected Aug 15 09:24:46 myhostname nm-openvpn[11804]: chroot to '/var/lib/openvpn/chroot' and cd to '/' succeeded Aug 15 09:24:46 myhostname nm-openvpn[11804]: capng_change_id() failed applying capabilities: Operation not permitted (errno=1) Aug 15 09:24:46 myhostname nm-openvpn[11804]: NOTE: previous error likely due to missing capability CAP_SETPCAP. Aug 15 09:24:46 myhostname nm-openvpn[11804]: Exiting due to fatal error Aug 15 09:24:46 myhostname nm-openvpn[11804]: net_addr_v4_del: 1.2.3.4 dev tun1 Aug 15 09:24:46 myhostname nm-openvpn[11804]: sitnl_send: rtnl: generic error (-99): Cannot assign requested address Aug 15 09:24:46 myhostname nm-openvpn[11804]: Linux can't del IP from iface tun1 Aug 15 09:24:46 myhostname kernel: tun1: tun1: deleting peer with id 28, reason 0 -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-4-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages network-manager-openvpn depends on: ii adduser 3.123 ii libc62.34-3 ii libglib2.0-0 2.72.3-1+b1 ii libnm0 1.38.4-1 ii network-manager 1.38.4-1 ii openvpn 2.6.0~git20220811-1 network-manager-openvpn recommends no packages. network-manager-openvpn suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: openvpn Source-Version: 2.6.0~git20220811-2 Done: Bernhard Schmidt We believe that the bug you reported is fixed in the latest version of openvpn, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous
Bug#1017517: marked as done (mia FTBFS with openexr 3.1.5)
Your message dated Wed, 17 Aug 2022 13:52:23 +
with message-id
and subject line Bug#1017517: fixed in mia 2.4.7-11
has caused the Debian Bug report #1017517,
regarding mia FTBFS with openexr 3.1.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.)
--
1017517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017517
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mia
Version: 2.4.7-10
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=mia=ppc64el=2.4.7-10%2Bb1=1660730413=0
...
/<>/addons/openexr/2dimgexr.cc: In member function ‘virtual
mia::TIOPlugin::PData
IMAGEIO_2D_EXR::CEXR2DImageIOPlugin::do_load(const std::string&) const’:
/<>/addons/openexr/2dimgexr.cc:67:15: error: ‘Box2i’ was not
declared in this scope
67 | Box2i dw = file.header().dataWindow();
| ^
/<>/addons/openexr/2dimgexr.cc:68:30: error: ‘dw’ was not declared
in this scope
68 | C2DBounds size(dw.max.x - dw.min.x + 1, dw.max.y -
dw.min.y + 1);
| ^~
/<>/addons/openexr/2dimgexr.cc:72:56: error: invalid use of
incomplete type ‘const class Imf_3_1::Header’
72 | const ChannelList& channels = file.header().channels();
| ~~~^~
In file included from /usr/include/OpenEXR/ImfOutputFile.h:16,
from /<>/addons/openexr/2dimgexr.cc:23:
/usr/include/OpenEXR/ImfForward.h:31:23: note: forward declaration of ‘class
Imf_3_1::Header’
31 | class IMF_EXPORT_TYPE Header;
| ^~
/<>/addons/openexr/2dimgexr.cc:73:27: error: aggregate
‘Imf_3_1::FrameBuffer frameBuffer’ has incomplete type and cannot be defined
73 | FrameBuffer frameBuffer;
| ^~~
/<>/addons/openexr/2dimgexr.cc:83:54: error: ‘Slice’ was not
declared in this scope
83 | frameBuffer.insert ("Y", Slice(UINT, (char
*)(&(*img)(0, 0) - (dx + size.x * dy)),
| ^
/<>/addons/openexr/2dimgexr.cc:91:54: error: ‘Slice’ was not
declared in this scope
91 | frameBuffer.insert ("Y", Slice(FLOAT, (char
*)(&(*img)(0, 0) - (dx + size.x * dy)),
| ^
/<>/addons/openexr/2dimgexr.cc: In static member function ‘static
bool IMAGEIO_2D_EXR::image_writer_exr::apply(const mia::T2DImage&,
const std::string&)’:
/<>/addons/openexr/2dimgexr.cc:174:29: error: ‘header’ has
incomplete type
174 | Header header (image.get_size().x,
image.get_size().y);
| ^~
/usr/include/OpenEXR/ImfForward.h:31:23: note: forward declaration of ‘class
Imf_3_1::Header’
31 | class IMF_EXPORT_TYPE Header;
| ^~
/<>/addons/openexr/2dimgexr.cc:177:34: error: ‘frameBuffer’ has
incomplete type
177 | FrameBuffer frameBuffer;
| ^~~
/usr/include/OpenEXR/ImfForward.h:75:24: note: forward declaration of ‘class
Imf_3_1::FrameBuffer’
75 | class IMF_EXPORT_TYPE FrameBuffer;
|^~~
make[4]: Leaving directory '/<>/obj-powerpc64le-linux-gnu'
...
--- End Message ---
--- Begin Message ---
Source: mia
Source-Version: 2.4.7-11
Done: Mathieu Malaterre
We believe that the bug you reported is fixed in the latest version of
mia, 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 1017...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mathieu Malaterre (supplier of updated mia 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: Wed, 17 Aug 2022 15:27:13 +0200
Source: mia
Architecture: source
Version: 2.4.7-11
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
Changed-By: Mathieu Malaterre
Closes: 1017517
Changes:
mia (2.4.7-11) unstable; urgency=medium
.
* Team upload
* d/patches: Refresh patch to handle openexr 3.x. Closes: #1017517
Bug#1017528: aborts at startup: Using libsoup2 and libsoup3 in the same process is not supported
Package: gtranslator Version: 42.0-1 Severity: grave On an up to date unstable, gtranslator aborts at startup: (gtranslator:58389): libsoup-ERROR **: 13:25:11.006: libsoup3 symbols detected. Using libsoup2 and libsoup3 in the same process is not supported. zsh: trace trap (core dumped) gtranslator bg.po Surprisingly, ldd doesn't show libsoup2 in the linked libraries: $ ldd /usr/bin/gtranslator|grep soup libsoup-3.0.so.0 => /usr/lib/x86_64-linux-gnu/libsoup-3.0.so.0 (0x7fb803048000) -- Damyan -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-4-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gtranslator depends on: ii dconf-gsettings-backend [gsettings-backend] 0.40.0-3 ii gsettings-desktop-schemas42.0-1 ii iso-codes4.11.0-1 ii libatk1.0-0 2.38.0-1 ii libc62.34-4 ii libcairo21.16.0-6 ii libgda-5.0-4 5.2.10-2 ii libgettextpo00.21-8 ii libglib2.0-0 2.72.3-1+b1 ii libgspell-1-21.11.1-1 ii libgtk-3-0 3.24.34-1 ii libgtksourceview-4-0 4.8.3-1 ii libhandy-1-0 1.7.90-1 ii libjson-glib-1.0-0 1.6.6-1 ii libpango-1.0-0 1.50.9+ds-1 ii libsoup-3.0-03.1.3-1 ii libxml2 2.9.14+dfsg-1+b1 gtranslator recommends no packages. Versions of packages gtranslator suggests: pn libpeas-1.0-python2loader -- debconf-show failed
Bug#1017229: marked as done (xmonad-wallpaper: FTBFS: unsatisfiable build-dependency: libghc-xmonad-dev (< 0.16) but 0.17.0-2 is to be installed)
Your message dated Wed, 17 Aug 2022 13:15:34 + with message-id and subject line Bug#1017229: fixed in xmonad-wallpaper 0.0.1.5-2 has caused the Debian Bug report #1017229, regarding xmonad-wallpaper: FTBFS: unsatisfiable build-dependency: libghc-xmonad-dev (< 0.16) but 0.17.0-2 is to be installed 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.) -- 1017229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017229 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xmonad-wallpaper Version: 0.0.1.5-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220813 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 10), haskell-devscripts-minimal | > haskell-devscripts (>= 0.9), cdbs, ghc (>= 8.4.3), ghc-prof, libghc-magic-dev > (>= 1.1), libghc-magic-dev (<< 1.2), libghc-magic-prof, libghc-random-dev, > libghc-random-prof, libghc-xmonad-dev (>= 0.13), libghc-xmonad-dev (<< 0.16), > libghc-xmonad-prof, build-essential, fakeroot, ghc-doc, libghc-magic-doc, > libghc-random-doc, libghc-xmonad-doc > Filtered Build-Depends: debhelper (>= 10), haskell-devscripts-minimal, cdbs, > ghc (>= 8.4.3), ghc-prof, libghc-magic-dev (>= 1.1), libghc-magic-dev (<< > 1.2), libghc-magic-prof, libghc-random-dev, libghc-random-prof, > libghc-xmonad-dev (>= 0.13), libghc-xmonad-dev (<< 0.16), libghc-xmonad-prof, > build-essential, fakeroot, ghc-doc, libghc-magic-doc, libghc-random-doc, > libghc-xmonad-doc > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [490 B] > Get:5 copy:/<>/apt_archive ./ Packages [558 B] > Fetched 2005 B in 0s (165 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: libghc-xmonad-dev (< 0.16) but > 0.17.0-2 is to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2022/08/13/xmonad-wallpaper_0.0.1.5-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220813;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220813=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: xmonad-wallpaper Source-Version: 0.0.1.5-2 Done: Clint Adams We believe that the bug you reported is fixed in the latest version of xmonad-wallpaper, 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 1017...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Clint Adams (supplier of updated xmonad-wallpaper package) (This message was
Processed: freeimage FTBFS with openexr 3.1.5
Processing control commands: > tags -1 patch Bug #1017512 [src:freeimage] freeimage FTBFS with openexr 3.1.5 Added tag(s) patch. -- 1017512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017512 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017512: freeimage FTBFS with openexr 3.1.5
Control: tags -1 patch See attached. Thanks From f40352706436a15d09767011ec9c9c0df33a57a1 Mon Sep 17 00:00:00 2001 From: Mathieu Malaterre Date: Wed, 17 Aug 2022 15:04:22 +0200 Subject: [PATCH] d/patches: Refresh patch to handle openexr 3.x split --- debian/patches/Disable-vendored-dependencies.patch | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/debian/patches/Disable-vendored-dependencies.patch b/debian/patches/Disable-vendored-dependencies.patch index c948008..7844a7e 100644 --- a/debian/patches/Disable-vendored-dependencies.patch +++ b/debian/patches/Disable-vendored-dependencies.patch @@ -84,7 +84,7 @@ Index: freeimage-3.18.0+ds2/Source/FreeImage/PluginEXR.cpp === --- freeimage-3.18.0+ds2.orig/Source/FreeImage/PluginEXR.cpp +++ freeimage-3.18.0+ds2/Source/FreeImage/PluginEXR.cpp -@@ -28,16 +28,16 @@ +@@ -28,16 +28,17 @@ #pragma warning (disable : 4800) // ImfVersion.h - 'const int' : forcing value to bool 'true' or 'false' (performance warning) #endif @@ -107,7 +107,8 @@ Index: freeimage-3.18.0+ds2/Source/FreeImage/PluginEXR.cpp +#include +#include +#include -+#include ++#include ++#include // == @@ -404,7 +405,7 @@ Index: freeimage-3.18.0+ds2/Source/FreeImage/PluginTIFF.cpp +#include #include "../Metadata/FreeImageTag.h" -#include "../OpenEXR/Half/half.h" -+#include "OpenEXR/half.h" ++#include "Imath/half.h" #include "FreeImageIO.h" #include "PSDParser.h" -- 2.30.2
Bug#1017526: luminance-hdr FTBFS with openexr 3.1.5
Source: luminance-hdr Version: 2.6.0+dfsg-2 Severity: serious Tags: ftbfs bookworm sid experimental Forwarded: https://github.com/LuminanceHDR/LuminanceHDR/issues/244 https://buildd.debian.org/status/fetch.php?pkg=luminance-hdr=ppc64el=2.6.0%2Bdfsg-2%2Bb12=1660734956=0 ... CMake Error: The following variables are used in this project, but they are set to NOTFOUND. Please set them or make sure they are set and tested correctly in the CMake files: OPENEXR_HALF_LIBRARY (ADVANCED) linked by target "luminance-hdr-cli" in directory /<> linked by target "luminance-hdr" in directory /<> OPENEXR_ILMIMF_LIBRARY (ADVANCED) linked by target "luminance-hdr-cli" in directory /<> linked by target "luminance-hdr" in directory /<> ...
Bug#1017524: jekyll: Could not find 'mercenary' (~> 0.3.3)
*for migrating ruby-rouge 3.30 from experimental to unstable Sorry for the mistake :) -- Vivek K J Debian Contributor https://vivekkj.codes/
Processed: tagging 1017072
Processing commands for cont...@bugs.debian.org: > tags 1017072 + ftbfs Bug #1017072 [src:rust-grcov] rust-grcov: Please update package to 0.8.x Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1017072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017072 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 995928
Processing commands for cont...@bugs.debian.org: > close 995928 Bug #995928 [src:acorn] acorn: doc directory shipped by both binaries Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 995928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995928 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000796: marked as done (update-passwd only remove item one time)
Your message dated Wed, 17 Aug 2022 11:34:20 + with message-id and subject line Bug#1000796: fixed in base-passwd 3.6.0 has caused the Debian Bug report #1000796, regarding update-passwd only remove item one time 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.) -- 1000796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000796 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: base-passwd Version: 3.5.51 Severity: critical update-passwd only removes once and exits even more than one items need to be removed. Root cause is walk is set to walk->next after remove_node(), in which the walk has been cleaned, so the while(walk) is terminated. $update-passwd --verbose Adding group "postgres" (120) Adding group "nova" (162) Adding group "barbican" (978) Adding group "keystone" (42424) Adding group "neutron" (164) Adding group "ceilometer" (166) Adding group "sysinv" (168) Adding group "snmpd" (169) Adding group "fm" (195) Adding group "libvirt" (991) Adding group "ironic" (1874) Adding group "www" (1877) Removing group "daemon" (1) Adding user "postgres" (120) Adding user "neutron" (164) Adding user "sysinv" (168) Adding user "snmpd" (169) Adding user "fm" (195) Adding user "barbican" (982) Adding user "ceilometer" (991) Adding user "keystone" (42424) Adding user "nova" (994) Adding user "ironic" (1874) Adding user "www" (1877) Removing user "daemon" (1) 25 changes have been made, rewriting files Writing passwd-file to /etc/passwd Writing shadow-file to /etc/shadow Writing group-file to /etc/group Adding user works well, but removing user just run one time. I attached a fix, with which, it works as $sudo update-passwd --verbose Adding group "postgres" (120) Adding group "nova" (162) Adding group "barbican" (978) Adding group "keystone" (42424) Adding group "neutron" (164) Adding group "ceilometer" (166) Adding group "sysinv" (168) Adding group "snmpd" (169) Adding group "fm" (195) Adding group "libvirt" (991) Adding group "ironic" (1874) Adding group "www" (1877) Removing group "daemon" (1) Removing group "bin" (2) Removing group "lp" (7) Removing group "man" (12) Removing group "audio" (29) Removing group "video" (44) Removing group "games" (60) Adding user "postgres" (120) Adding user "neutron" (164) Adding user "sysinv" (168) Adding user "snmpd" (169) Adding user "fm" (195) Adding user "barbican" (982) Adding user "ceilometer" (991) Adding user "keystone" (42424) Adding user "nova" (994) Adding user "ironic" (1874) Adding user "www" (1877) Removing user "daemon" (1) Removing user "bin" (2) Removing user "games" (5) Removing user "lp" (7) Removing user "mail" (8) 35 changes have been made, rewriting files Writing passwd-file to /etc/passwd Writing shadow-file to /etc/shadow Writing group-file to /etc/group Thanks, ytao >From a2a96fa28fe132e34185ab1646b1f1ea4baf4942 Mon Sep 17 00:00:00 2001 From: Yue Tao Date: Thu, 25 Nov 2021 10:14:45 +0800 Subject: [PATCH] update-passwd.c: set walk to walk->next before removing update-passwd only removes once and exits even more than one items need to be removed. Root cause is walk is set to walk->next after remove_node(), in which the walk has been cleaned, so the while(walk) is terminated. Without the fix, the output of update-passwd $update-passwd --verbose Adding group "postgres" (120) Adding group "nova" (162) Adding group "barbican" (978) Adding group "keystone" (42424) Adding group "neutron" (164) Adding group "ceilometer" (166) Adding group "sysinv" (168) Adding group "snmpd" (169) Adding group "fm" (195) Adding group "libvirt" (991) Adding group "ironic" (1874) Adding group "www" (1877) Removing group "daemon" (1) Adding user "postgres" (120) Adding user "neutron" (164) Adding user "sysinv" (168) Adding user "snmpd" (169) Adding user "fm" (195) Adding user "barbican" (982) Adding user "ceilometer" (991) Adding user "keystone" (42424) Adding user "nova" (994) Adding user "ironic" (1874) Adding user "www" (1877) Removing user "daemon" (1) 25 changes have been made, rewriting files Writing passwd-file to /etc/passwd Writing shadow-file to /etc/shadow Writing group-file to /etc/group With the fix: $sudo update-passwd --verbose Adding group "postgres" (120) Adding group "nova" (162) Adding group "barbican" (978) Adding group "keystone" (42424) Adding group "neutron" (164) Adding group "ceilometer" (166) Adding group "sysinv" (168) Adding group "snmpd" (169) Adding group "fm" (195) Adding group "libvirt" (991) Adding group "ironic" (1874) Adding group "www" (1877) Removing group "daemon" (1) Removing group "bin" (2) Removing group
Bug#1017510: marked as done (exactimage FTBFS with openexr 3.1.5)
Your message dated Wed, 17 Aug 2022 11:21:33 + with message-id and subject line Bug#1017510: fixed in exactimage 1.0.2-9 has caused the Debian Bug report #1017510, regarding exactimage FTBFS with openexr 3.1.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.) -- 1017510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017510 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: exactimage Version: 1.0.2-8 Severity: serious Tags: ftbfs bookworm sid https://buildd.debian.org/status/fetch.php?pkg=exactimage=ppc64el=1.0.2-8%2Bb7=1660728909=0 ... codecs/openexr.cc:65:11: error: ‘Int64’ does not name a type; did you mean ‘int64_t’? 65 | virtual Int64 tellg () | ^ | int64_t codecs/openexr.cc:70:23: error: ‘Int64’ has not been declared 70 | virtual void seekg (Int64 pos) | ^ codecs/openexr.cc:106:11: error: ‘Int64’ does not name a type; did you mean ‘int64_t’? 106 | virtual Int64 tellp () | ^ | int64_t codecs/openexr.cc:111:23: error: ‘Int64’ has not been declared 111 | virtual void seekp (Int64 pos) | ^ codecs/openexr.cc: In member function ‘virtual int OpenEXRCodec::readImage(std::istream*, Image&, const std::string&)’: codecs/openexr.cc:128:14: error: cannot declare variable ‘istream’ to be of abstract type ‘STDIStream’ 128 | STDIStream istream (stream, ""); | ^~~ codecs/openexr.cc:43:7: note: because the following virtual functions are pure within ‘STDIStream’: 43 | class STDIStream : public IStream | ^~ In file included from codecs/openexr.cc:22: /usr/include/OpenEXR/ImfIO.h:82:25: note: ‘virtual uint64_t Imf_3_1::IStream::tellg()’ 82 | virtual uint64_ttellg () = 0; | ^ /usr/include/OpenEXR/ImfIO.h:90:25: note: ‘virtual void Imf_3_1::IStream::seekg(uint64_t)’ 90 | virtual voidseekg (uint64_t pos) = 0; | ^ codecs/openexr.cc: In member function ‘virtual bool OpenEXRCodec::writeImage(std::ostream*, Image&, int, const std::string&)’: codecs/openexr.cc:201:14: error: cannot declare variable ‘ostream’ to be of abstract type ‘STDOStream’ 201 | STDOStream ostream (stream, ""); | ^~~ codecs/openexr.cc:85:7: note: because the following virtual functions are pure within ‘STDOStream’: 85 | class STDOStream : public OStream | ^~ /usr/include/OpenEXR/ImfIO.h:154:25: note: ‘virtual uint64_t Imf_3_1::OStream::tellp()’ 154 | virtual uint64_ttellp () = 0; | ^ /usr/include/OpenEXR/ImfIO.h:162:25: note: ‘virtual void Imf_3_1::OStream::seekp(uint64_t)’ 162 | virtual voidseekp (uint64_t pos) = 0; | ^ make[4]: *** [build/bottom.make:54: objdir/codecs/openexr.o] Error 1 make[4]: *** Waiting for unfinished jobs codecs/dcraw.h: In function ‘void dcraw::tiff_head(tiff_hdr*, int)’: codecs/dcraw.h:9963:28: warning: ‘%02d’ directive writing between 2 and 11 bytes into a region of size between 8 and 15 [-Wformat-overflow=] 9963 | sprintf (th->date, "%04d:%02d:%02d %02d:%02d:%02d", |^~~~ codecs/dcraw.h:9963:22: note: directive argument in the range [-2147483647, 2147483647] 9963 | sprintf (th->date, "%04d:%02d:%02d %02d:%02d:%02d", | ^~~ In file included from /usr/include/stdio.h:888, from /usr/include/c++/12/cstdio:42, from /usr/include/c++/12/ext/string_conversions.h:43, from /usr/include/c++/12/bits/basic_string.h:3960, from /usr/include/c++/12/string:53, from /usr/include/c++/12/bits/locale_classes.h:40, from /usr/include/c++/12/bits/ios_base.h:41, from /usr/include/c++/12/ios:42, from /usr/include/c++/12/istream:38, from codecs/dcraw.cc:18: In function ‘int sprintf(char*, const char*, ...)’, inlined from ‘void dcraw::tiff_head(tiff_hdr*, int)’ at codecs/dcraw.h:9963:11: /usr/include/powerpc64le-linux-gnu/bits/stdio2.h:38:34: note: ‘__builtin___sprintf_chk’ output between 20 and 72 bytes into a destination of size 20 38 | return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1, | ^~ 39 |
Processed: tagging 1017164
Processing commands for cont...@bugs.debian.org: > tags 1017164 + fixed-upstream upstream confirmed Bug #1017164 [src:mpd] mpd: FTBFS: ./obj-x86_64-linux-gnu/../src/decoder/plugins/FfmpegIo.cxx:102: undefined reference to `av_malloc(unsigned long)' Added tag(s) upstream, confirmed, and fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1017164: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017164 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000796: marked as pending in base-passwd
On Sun, Aug 14, 2022 at 11:27:47PM +0200, Paul Gevers wrote: > On Thu, 03 Mar 2022 00:42:14 + Colin Watson wrote: > > Bug #1000796 in base-passwd reported by you has been fixed in the > > Git repository and is awaiting an upload. You can see the commit > > message below and you can check the diff of the fix at: > > > > https://salsa.debian.org/debian/base-passwd/-/commit/06ed6f49253ff244dc9cbcadc840fdf611f11462 > > Can we have this uploaded to unstable please? Pending RC bugs for 5 months > are a bit awkward. Uploaded now - sorry for the delay. -- Colin Watson (he/him) [cjwat...@debian.org]
Bug#1017516: marked as done (libopenexr-dev: Missing dependency on zlib1g-dev)
Your message dated Wed, 17 Aug 2022 11:07:43 + with message-id and subject line Bug#1017516: fixed in openexr 3.1.5-4 has caused the Debian Bug report #1017516, regarding libopenexr-dev: Missing dependency on zlib1g-dev 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.) -- 1017516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017516 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libopenexr-dev Version: 3.1.5-3 Severity: serious Tags: ftbfs Control: affects -1 src:kimageformats https://buildd.debian.org/status/fetch.php?pkg=kimageformats=ppc64el=5.97.0-1%2Bb1=1660729065=0 ... CMake Error at /usr/share/cmake-3.24/Modules/FindPackageHandleStandardArgs.cmake:230 (message): Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR) Call Stack (most recent call first): /usr/share/cmake-3.24/Modules/FindPackageHandleStandardArgs.cmake:594 (_FPHSA_FAILURE_MESSAGE) /usr/share/cmake-3.24/Modules/FindZLIB.cmake:150 (FIND_PACKAGE_HANDLE_STANDARD_ARGS) /usr/share/cmake-3.24/Modules/CMakeFindDependencyMacro.cmake:47 (find_package) /usr/lib/powerpc64le-linux-gnu/cmake/OpenEXR/OpenEXRConfig.cmake:46 (find_dependency) CMakeLists.txt:45 (find_package) -- Configuring incomplete, errors occurred! --- End Message --- --- Begin Message --- Source: openexr Source-Version: 3.1.5-4 Done: Mathieu Malaterre We believe that the bug you reported is fixed in the latest version of openexr, 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 1017...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mathieu Malaterre (supplier of updated openexr 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: Wed, 17 Aug 2022 12:44:50 +0200 Source: openexr Architecture: source Version: 3.1.5-4 Distribution: unstable Urgency: medium Maintainer: Debian PhotoTools Maintainers Changed-By: Mathieu Malaterre Closes: 1017516 Changes: openexr (3.1.5-4) unstable; urgency=medium . * d/control: Add missing zlib1g-dev dependency. Closes: #1017516 * d/control: Run wrap-and-sort * d/control: Bump Std-Vers to 4.6.1 no changes needed Checksums-Sha1: 7f1c00a82cb7fc19bae9e5b793db9a24cce4a05a 2506 openexr_3.1.5-4.dsc 0376e5eb1d8ad0339506bfeb3e4615eeb1300834 18152 openexr_3.1.5-4.debian.tar.xz fac933270c6ecb673066a70f76f1d34f071eaf92 6933 openexr_3.1.5-4_source.buildinfo Checksums-Sha256: d9a02deed821f31f01dadf8ca284c058437cc76b2d6b374686f73b514c1dd0b7 2506 openexr_3.1.5-4.dsc d13236dee40357dbcca99312935d112a8f62aa1e9e4b025af354b8df3dbd58c8 18152 openexr_3.1.5-4.debian.tar.xz 38c42075a91fd220ce5955cfcda4377a9b932c0484eb9ab36d37d57f0c7f1e09 6933 openexr_3.1.5-4_source.buildinfo Files: 5b7523da44a7e13cdf3e15bfb66241c1 2506 graphics optional openexr_3.1.5-4.dsc ba90a47ea4222cf62c8d11f7b4d71d28 18152 graphics optional openexr_3.1.5-4.debian.tar.xz 967d1d88de5d2f18cdb67ce1c7d1e22a 6933 graphics optional openexr_3.1.5-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEaTNn/67NjqrNHwY7AXHhgorgk0UFAmL8xtcRHG1hbGF0QGRl Ymlhbi5vcmcACgkQAXHhgorgk0VODA//X+jXgWHX65CA8wGki7AiZG6gSSz7nEVt 70h4Qtt4AKQzbzUUjMi/BpWpFwxU447POr/0UBUVzrO3oQwgC09hN12Kvwmpqfpr o8rA4MXF+3cfw8P1hRPvdQPRjLuPP9aptD1w3mFM4cKJkEuP/NJt2MZkvneww5bW dSEmQfpKWhJmIFrEXf4BnknM1ewFZWAdKjNgvd/me7AEjH7HUEPJqicjfIFv77Vi mQuaqARGKlSzUDhd1/Lss0Iqqk+QZFvG4PQcEvDW3GCfNJ4AKWQR26Fg0MVyRjV8 lvGlLHggbKLeqcHYimQc9jHSy0e4QRNBt5PNqNdd6HFLm3x2sc53oM5vEgo1Cxza LCEipaaEmzlaO82qIO4EaFGBWtuXhu9QgFGibpvUxHEuvKbVS443c2AQCNwiMCRx LPodFNB3QbPj6niFC6feajmkP5e4fJGJMIba3yoZ6ti8GHDY9W4vpH2saoSq1JsC nulrw0nfs8I661Gr8eAFU49iKhZeARbOzWQEF2DeQFj3wn3QycmpIgKRMsAfnyJ0 EQzVDaf3XpOcm2jAxzqWm343YHmxgugo7SJ0Yf87CuyhuCdsuGF2E3Ypn3cjzIfE 3/SDcLNV+LYClMbzJdoleZndPVgwpCcZWU4vb+4TkkC1CdefVac+MvTC9bjKJwHP zcjGxIHa6Bw= =l50U -END PGP SIGNATURE End Message ---
Bug#1017517: mia FTBFS with openexr 3.1.5
Source: mia
Version: 2.4.7-10
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=mia=ppc64el=2.4.7-10%2Bb1=1660730413=0
...
/<>/addons/openexr/2dimgexr.cc: In member function ‘virtual
mia::TIOPlugin::PData
IMAGEIO_2D_EXR::CEXR2DImageIOPlugin::do_load(const std::string&) const’:
/<>/addons/openexr/2dimgexr.cc:67:15: error: ‘Box2i’ was not
declared in this scope
67 | Box2i dw = file.header().dataWindow();
| ^
/<>/addons/openexr/2dimgexr.cc:68:30: error: ‘dw’ was not declared
in this scope
68 | C2DBounds size(dw.max.x - dw.min.x + 1, dw.max.y -
dw.min.y + 1);
| ^~
/<>/addons/openexr/2dimgexr.cc:72:56: error: invalid use of
incomplete type ‘const class Imf_3_1::Header’
72 | const ChannelList& channels = file.header().channels();
| ~~~^~
In file included from /usr/include/OpenEXR/ImfOutputFile.h:16,
from /<>/addons/openexr/2dimgexr.cc:23:
/usr/include/OpenEXR/ImfForward.h:31:23: note: forward declaration of ‘class
Imf_3_1::Header’
31 | class IMF_EXPORT_TYPE Header;
| ^~
/<>/addons/openexr/2dimgexr.cc:73:27: error: aggregate
‘Imf_3_1::FrameBuffer frameBuffer’ has incomplete type and cannot be defined
73 | FrameBuffer frameBuffer;
| ^~~
/<>/addons/openexr/2dimgexr.cc:83:54: error: ‘Slice’ was not
declared in this scope
83 | frameBuffer.insert ("Y", Slice(UINT, (char
*)(&(*img)(0, 0) - (dx + size.x * dy)),
| ^
/<>/addons/openexr/2dimgexr.cc:91:54: error: ‘Slice’ was not
declared in this scope
91 | frameBuffer.insert ("Y", Slice(FLOAT, (char
*)(&(*img)(0, 0) - (dx + size.x * dy)),
| ^
/<>/addons/openexr/2dimgexr.cc: In static member function ‘static
bool IMAGEIO_2D_EXR::image_writer_exr::apply(const mia::T2DImage&,
const std::string&)’:
/<>/addons/openexr/2dimgexr.cc:174:29: error: ‘header’ has
incomplete type
174 | Header header (image.get_size().x,
image.get_size().y);
| ^~
/usr/include/OpenEXR/ImfForward.h:31:23: note: forward declaration of ‘class
Imf_3_1::Header’
31 | class IMF_EXPORT_TYPE Header;
| ^~
/<>/addons/openexr/2dimgexr.cc:177:34: error: ‘frameBuffer’ has
incomplete type
177 | FrameBuffer frameBuffer;
| ^~~
/usr/include/OpenEXR/ImfForward.h:75:24: note: forward declaration of ‘class
Imf_3_1::FrameBuffer’
75 | class IMF_EXPORT_TYPE FrameBuffer;
|^~~
make[4]: Leaving directory '/<>/obj-powerpc64le-linux-gnu'
...
Bug#1017516: libopenexr-dev: Missing dependency on zlib1g-dev
Package: libopenexr-dev Version: 3.1.5-3 Severity: serious Tags: ftbfs Control: affects -1 src:kimageformats https://buildd.debian.org/status/fetch.php?pkg=kimageformats=ppc64el=5.97.0-1%2Bb1=1660729065=0 ... CMake Error at /usr/share/cmake-3.24/Modules/FindPackageHandleStandardArgs.cmake:230 (message): Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR) Call Stack (most recent call first): /usr/share/cmake-3.24/Modules/FindPackageHandleStandardArgs.cmake:594 (_FPHSA_FAILURE_MESSAGE) /usr/share/cmake-3.24/Modules/FindZLIB.cmake:150 (FIND_PACKAGE_HANDLE_STANDARD_ARGS) /usr/share/cmake-3.24/Modules/CMakeFindDependencyMacro.cmake:47 (find_package) /usr/lib/powerpc64le-linux-gnu/cmake/OpenEXR/OpenEXRConfig.cmake:46 (find_dependency) CMakeLists.txt:45 (find_package) -- Configuring incomplete, errors occurred!
Processed: libopenexr-dev: Missing dependency on zlib1g-dev
Processing control commands: > affects -1 src:kimageformats Bug #1017516 [libopenexr-dev] libopenexr-dev: Missing dependency on zlib1g-dev Added indication that 1017516 affects src:kimageformats -- 1017516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017516 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017515: q2-feature-table: needs update for python-biom-format/2.1.12-1
Source: q2-feature-table Version: 2022.2.0+dfsg-2 Severity: serious User: debian...@lists.debian.org Usertags: needs-update Hi Maintainer Since the upload of python-biom-format/2.1.12-1, the autopkgtests of q2-feature-table have been failing [1]. I've copied the short test summary below. Regards Graham [1] https://ci.debian.net/packages/q/q2-feature-table/testing/amd64/ === short test summary info FAILED q2_feature_table/tests/filter/test_filter_features.py::FilterFeaturesTests::test_feature_metadata FAILED q2_feature_table/tests/filter/test_filter_features.py::FilterFeaturesTests::test_filter_empty_samples FAILED q2_feature_table/tests/filter/test_filter_features.py::FilterFeaturesTests::test_min_frequency FAILED q2_feature_table/tests/filter/test_filter_features.py::FilterFeaturesTests::test_where FAILED q2_feature_table/tests/filter/test_filter_samples.py::FilterSamplesTests::test_combine_exclude_ids_and_features_filters FAILED q2_feature_table/tests/filter/test_filter_samples.py::FilterSamplesTests::test_combine_exclude_ids_and_frequency_filters FAILED q2_feature_table/tests/filter/test_filter_samples.py::FilterSamplesTests::test_filter_empty_features FAILED q2_feature_table/tests/filter/test_filter_samples.py::FilterSamplesTests::test_max_features FAILED q2_feature_table/tests/filter/test_filter_samples.py::FilterSamplesTests::test_max_frequency FAILED q2_feature_table/tests/filter/test_filter_samples.py::FilterSamplesTests::test_min_features FAILED q2_feature_table/tests/filter/test_filter_samples.py::FilterSamplesTests::test_min_frequency FAILED q2_feature_table/tests/filter/test_filter_samples.py::FilterSamplesTests::test_sample_metadata FAILED q2_feature_table/tests/filter/test_filter_samples.py::FilterSamplesTests::test_where = 13 failed, 122 passed, 16 warnings in 24.97s =
Bug#1017514: q2-types: needs update for python-biom-format/2.1.12-1
Source: q2-types Version: 2022.2.0-1 Severity: serious User: debian...@lists.debian.org Usertags: needs-update Hi Maintainer Since the upload of python-biom-format/2.1.12-1, the autopkgtests of q2-types have been failing [1]. I've copied the short test summary below. Regards Graham [1] https://ci.debian.net/packages/q/q2-types/testing/amd64/ === short test summary info FAILED q2_types/feature_table/tests/test_transformer.py::TestTransformers::test_biom_table_to_biom_v210_format FAILED q2_types/feature_table/tests/test_transformer.py::TestTransformers::test_biom_v100_format_to_biom_table FAILED q2_types/feature_table/tests/test_transformer.py::TestTransformers::test_biom_v100_format_to_biom_v210_format FAILED q2_types/feature_table/tests/test_transformer.py::TestTransformers::test_biom_v210_format_to_biom_table == 4 failed, 350 passed, 12 warnings in 3.80s ==
Bug#1017513: isa-support: mktemp on /usr/lib and base64 encoded binary in preinst are evil
Source: isa-support Version: 7 Severity: grave Tags: patch Justification: causes non-serious data loss Dear Maintainer, mktemp could fail and base64 is preinst is not nice -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-2-rt-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1017512: freeimage FTBFS with openexr 3.1.5
Source: freeimage Version: 3.18.0+ds2-7 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=freeimage=ppc64el=3.18.0%2Bds2-7%2Bb1=1660728995=0 ... Source/FreeImage/PluginEXR.cpp:40:10: fatal error: OpenEXR/half.h: No such file or directory 40 | #include | ^~~~ compilation terminated. make[3]: *** [Makefile.gnu:66: Source/FreeImage/PluginEXR.o] Error 1
Bug#1017425: 5.10.0-17-686-pae: repeatedly crashes during initrd loading [PIII]
I can confirm that this bug also occurs on Athlon XP systems (Generic VIA KT333 motherboard, CPU AMD Athlon(tm) XP 2600+) : kernel panic early on boot. I suspect someone thought it would be a good idea to compile the kernel for P4 only, as both PIII and Athlon XP processors lack the SSE2 instruction set. -- Etienne Vogt (etienne.v...@obspm.fr)
Bug#1013549: xfsdump: FTBFS: gcc: fatal error: no input files
* Michael Prokop [Thu Aug 11, 2022 at 01:17:50PM +0200]: > * Lucas Nussbaum [Fri Jun 24, 2022 at 12:04:39PM +0200]: > > Source: xfsdump > > Version: 3.1.9+0+nmu2 > > Severity: serious > > Justification: FTBFS [...] > > During a rebuild of all packages in sid, your package failed to build > > on amd64. > AFAICS the new upstream release v3.1.10 of xfsdump (see > https://git.kernel.org/pub/scm/fs/xfs/xfsdump-dev.git/) doesn't seem > to fix this issue. Also updating xfsprogs to latest upstream git > (see https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git/), to > provide more recent xfslibs-dev + xfsprogs, doesn't seem to help > either. > > So it might be worth reaching out to upstream, though > https://marc.info/?l=linux-xfs is unavailable right now and I'm not > sure what other ways exist to check/report this towards upstream? > > FTR, xfsdump got removed from Debian testing/bookworm due to this RC > bug a few days ago. Having marc.info available again, I just checked its current situation and it looks like an according patch is available (see thread `Subject: [PATCH] xfs_restore: remove DMAPI support` on xfs list): https://marc.info/?t=16439103773=1=2 -> https://marc.info/?l=linux-xfs=164391022215783=2 https://marc.info/?l=linux-xfs=164453317302855=2 https://marc.info/?l=linux-xfs=165645703231744=2 https://marc.info/?l=linux-xfs=165961295025516=2 regards -mika- signature.asc Description: PGP signature
Bug#1017510: exactimage FTBFS with openexr 3.1.5
Source: exactimage Version: 1.0.2-8 Severity: serious Tags: ftbfs bookworm sid https://buildd.debian.org/status/fetch.php?pkg=exactimage=ppc64el=1.0.2-8%2Bb7=1660728909=0 ... codecs/openexr.cc:65:11: error: ‘Int64’ does not name a type; did you mean ‘int64_t’? 65 | virtual Int64 tellg () | ^ | int64_t codecs/openexr.cc:70:23: error: ‘Int64’ has not been declared 70 | virtual void seekg (Int64 pos) | ^ codecs/openexr.cc:106:11: error: ‘Int64’ does not name a type; did you mean ‘int64_t’? 106 | virtual Int64 tellp () | ^ | int64_t codecs/openexr.cc:111:23: error: ‘Int64’ has not been declared 111 | virtual void seekp (Int64 pos) | ^ codecs/openexr.cc: In member function ‘virtual int OpenEXRCodec::readImage(std::istream*, Image&, const std::string&)’: codecs/openexr.cc:128:14: error: cannot declare variable ‘istream’ to be of abstract type ‘STDIStream’ 128 | STDIStream istream (stream, ""); | ^~~ codecs/openexr.cc:43:7: note: because the following virtual functions are pure within ‘STDIStream’: 43 | class STDIStream : public IStream | ^~ In file included from codecs/openexr.cc:22: /usr/include/OpenEXR/ImfIO.h:82:25: note: ‘virtual uint64_t Imf_3_1::IStream::tellg()’ 82 | virtual uint64_ttellg () = 0; | ^ /usr/include/OpenEXR/ImfIO.h:90:25: note: ‘virtual void Imf_3_1::IStream::seekg(uint64_t)’ 90 | virtual voidseekg (uint64_t pos) = 0; | ^ codecs/openexr.cc: In member function ‘virtual bool OpenEXRCodec::writeImage(std::ostream*, Image&, int, const std::string&)’: codecs/openexr.cc:201:14: error: cannot declare variable ‘ostream’ to be of abstract type ‘STDOStream’ 201 | STDOStream ostream (stream, ""); | ^~~ codecs/openexr.cc:85:7: note: because the following virtual functions are pure within ‘STDOStream’: 85 | class STDOStream : public OStream | ^~ /usr/include/OpenEXR/ImfIO.h:154:25: note: ‘virtual uint64_t Imf_3_1::OStream::tellp()’ 154 | virtual uint64_ttellp () = 0; | ^ /usr/include/OpenEXR/ImfIO.h:162:25: note: ‘virtual void Imf_3_1::OStream::seekp(uint64_t)’ 162 | virtual voidseekp (uint64_t pos) = 0; | ^ make[4]: *** [build/bottom.make:54: objdir/codecs/openexr.o] Error 1 make[4]: *** Waiting for unfinished jobs codecs/dcraw.h: In function ‘void dcraw::tiff_head(tiff_hdr*, int)’: codecs/dcraw.h:9963:28: warning: ‘%02d’ directive writing between 2 and 11 bytes into a region of size between 8 and 15 [-Wformat-overflow=] 9963 | sprintf (th->date, "%04d:%02d:%02d %02d:%02d:%02d", |^~~~ codecs/dcraw.h:9963:22: note: directive argument in the range [-2147483647, 2147483647] 9963 | sprintf (th->date, "%04d:%02d:%02d %02d:%02d:%02d", | ^~~ In file included from /usr/include/stdio.h:888, from /usr/include/c++/12/cstdio:42, from /usr/include/c++/12/ext/string_conversions.h:43, from /usr/include/c++/12/bits/basic_string.h:3960, from /usr/include/c++/12/string:53, from /usr/include/c++/12/bits/locale_classes.h:40, from /usr/include/c++/12/bits/ios_base.h:41, from /usr/include/c++/12/ios:42, from /usr/include/c++/12/istream:38, from codecs/dcraw.cc:18: In function ‘int sprintf(char*, const char*, ...)’, inlined from ‘void dcraw::tiff_head(tiff_hdr*, int)’ at codecs/dcraw.h:9963:11: /usr/include/powerpc64le-linux-gnu/bits/stdio2.h:38:34: note: ‘__builtin___sprintf_chk’ output between 20 and 72 bytes into a destination of size 20 38 | return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1, | ^~ 39 | __glibc_objsize (__s), __fmt, | ~ 40 | __va_arg_pack ()); | ~ codecs/dcraw.h: In function ‘void dcraw::identify()’: codecs/dcraw.h:9195:33: warning: ‘%-10s’ directive writing between 10 and 56 bytes into a region of size 38 [-Wformat-overflow=] 9195 | sprintf (model+20, "DYNAX %-10s", model+6+(model[0]=='M')); | ^ In function ‘int sprintf(char*, const char*, ...)’, inlined from ‘void dcraw::identify()’ at codecs/dcraw.h:9195:15: /usr/include/powerpc64le-linux-gnu/bits/stdio2.h:38:34: note: ‘__builtin___sprintf_chk’ output between 17 and 63 bytes into a destination of size
Bug#999721: marked as done (ruby-omniauth-openid-connect: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in
Your message dated Wed, 17 Aug 2022 09:05:27 + with message-id and subject line Bug#999721: fixed in ruby-omniauth-openid-connect 0.10.0-1 has caused the Debian Bug report #999721, regarding ruby-omniauth-openid-connect: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies': Could not find 'omniauth' (~> 1.9) among 106 total gem(s) (Gem::MissingSpecError) 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.) -- 999721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999721 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-omniauth-openid-connect Version: 0.4.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-openid-connect was found to fail to build in that situation. To reproduce this locally, you need to install ruby-omniauth from experimental on an unstable system or build chroot. I would expect a new upstream version to work against the latest ruby-omniauth just fine. Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block > in activate_dependencies': Could not find 'omniauth' (~> 1.9) among 106 total > gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-openid-connect/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > at: > /<>/debian/ruby-omniauth-openid-connect/usr/share/rubygems-integration/all/specifications/gitlab-omniauth-openid-connect-0.4.0.gemspec, > execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not > find 'omniauth' (~> 1.9) - did find: [omniauth-2.0.4] > (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-openid-connect/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > activemodel (6.0.3.7) > activesupport (6.0.3.7) > addressable (2.8.0) > aes_key_wrap (1.0.1) > atomic (1.1.16) > attr_required (1.0.0) > benchmark (default: 0.1.0) > bigdecimal (default: 2.0.0) > bindata (2.4.8) > bundler (default: 2.1.4) > cgi (default: 0.1.0) > concurrent-ruby (1.1.6) > concurrent-ruby-edge (0.6.0) > coveralls (0.8.23) > csv (default: 3.1.2) > date (default: 3.0.0) > dbm (default: 1.1.0) > delegate (default: 0.1.0) > did_you_mean (default: 1.4.0) > docile (1.1.5) > domain_name (0.5.20190701) > etc (default: 1.1.0) > faker (1.9.1) >
Bug#999718: marked as done (ruby-omniauth-ldap: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_d
Your message dated Wed, 17 Aug 2022 08:40:15 + with message-id and subject line Bug#999718: fixed in ruby-omniauth-ldap 2.2.0-1 has caused the Debian Bug report #999718, regarding ruby-omniauth-ldap: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies': Could not find 'omniauth' (~> 1.3) among 71 total gem(s) (Gem::MissingSpecError) 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.) -- 999718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999718 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-omniauth-ldap Version: 2.1.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-ldap was found to fail to build in that situation. To reproduce this locally, you need to install ruby-omniauth from experimental on an unstable system or build chroot. Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block > in activate_dependencies': Could not find 'omniauth' (~> 1.3) among 71 total > gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-ldap/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > at: > /<>/debian/ruby-omniauth-ldap/usr/share/rubygems-integration/all/specifications/gitlab_omniauth-ldap-2.1.1.gemspec, > execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not > find 'omniauth' (~> 1.3) - did find: [omniauth-2.0.4] > (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-ldap/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > benchmark (default: 0.1.0) > bigdecimal (default: 2.0.0) > bundler (default: 2.1.4) > cgi (default: 0.1.0) > csv (default: 3.1.2) > date (default: 3.0.0) > dbm (default: 1.1.0) > delegate (default: 0.1.0) > did_you_mean (default: 1.4.0) > diff-lcs (1.4.4) > etc (default: 1.1.0) > fcntl (default: 1.0.0) > fiddle (default: 1.0.0) > fileutils (default: 1.4.1) > forwardable (default: 1.3.1) > gdbm (default: 2.1.0) > getoptlong (default: 0.1.0) > hashie (3.5.5) > io-console (default: 0.5.6) > ipaddr (default: 1.2.2) > irb (default: 1.2.6) > json (default: 2.3.0) > logger (default: 1.4.2) > matrix (default: 0.2.0) > minitest (5.13.0) > mutex_m (default: 0.1.0) > net-ldap (0.16.3) > net-pop (default: 0.1.0) > net-smtp (default: 0.1.0) > net-telnet (0.1.1) > observer (default: 0.1.0) > omniauth (2.0.4) > open3 (default: 0.1.0) > openssl (default: 2.1.2) > ostruct (default:
