Bug#996362: ruby-raindrops: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.
Antonio Terceiro wrote: > Source: ruby-raindrops > Version: 0.19.0-2 > > === > > Error: test_unix(TestLinux): TypeError: no implicit conversion of Hash into > > Integer > > /<>/debian/ruby-raindrops/usr/lib/ruby/vendor_ruby/raindrops/linux.rb:60:in > > `read' > > /<>/debian/ruby-raindrops/usr/lib/ruby/vendor_ruby/raindrops/linux.rb:60:in > > `unix_listener_stats' > > /<>/test/test_linux.rb:26:in `test_unix' This is fixed in raindrops v0.19.1 (2020-01-08): https://yhbt.net/raindrops-public/20200108093633.GA30847@dcvr/ And v0.19.2 (2021-05-25) fixes compatibility with GC.compact: https://yhbt.net/raindrops-public/20210525233405.GA6904@dcvr/
Processed: tagging 991146
Processing commands for cont...@bugs.debian.org: > # > https://salsa.debian.org/python-team/tools/dh-python/-/commit/cde02a32cd1b51cf7d07828edca0be61458e0eee > tags 991146 + pending Bug #991146 [dh-python] python3-libxml2: ambiguous package name 'python3-libxml2' with more than one installed instance Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 991146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991146 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984349: marked as done (spring: ftbfs with GCC-11)
Your message dated Fri, 15 Oct 2021 23:04:53 + with message-id and subject line Bug#984349: fixed in spring 105.0.1+dfsg-3 has caused the Debian Bug report #984349, regarding spring: ftbfs with GCC-11 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.) -- 984349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984349 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:spring Version: 105.0.1+dfsg-1 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/spring_105.0.1+dfsg-1_unstable_gcc11.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. [...] | ^ /<>/rts/Sim/Weapons/WeaponLoader.cpp:34:97: error: ‘::max’ has not been declared; did you mean ‘std::max’? 34 | static_assert(MAX_WEAPONS_PER_UNIT < std::numeric_limits::max(), ""); | ^~~ | std::max In file included from /usr/include/c++/11/algorithm:62, from /<>/rts/System/ContainerUtil.h:6, from /<>/rts/System/MemPoolTypes.h:16, from /<>/rts/Sim/Weapons/WeaponMemPool.h:7, from /<>/rts/Sim/Weapons/WeaponLoader.cpp:4: /usr/include/c++/11/bits/stl_algo.h:3467:5: note: ‘std::max’ declared here 3467 | max(initializer_list<_Tp> __l, _Compare __comp) | ^~~ make[4]: *** [rts/Sim/CMakeFiles/engineSim.dir/build.make:1840: rts/Sim/CMakeFiles/engineSim.dir/Weapons/WeaponLoader.cpp.o] Error 1 make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu' make[3]: *** [CMakeFiles/Makefile2:3544: rts/Sim/CMakeFiles/engineSim.dir/all] Error 2 make[3]: *** Waiting for unfinished jobs [ 58%] Building CXX object AI/Skirmish/CircuitAI/CMakeFiles/CircuitAI.dir/src/circuit/unit/action/SupportAction.cpp.o cd /<>/obj-x86_64-linux-gnu/AI/Skirmish/CircuitAI && /usr/bin/c++ -DASIO_STANDALONE -DBUILDING_AI -DBUILDING_SKIRMISH_AI -DCircuitAI_EXPORTS -DSPRING_DATADIR=\"/usr/share/games/spring:/usr/lib/spring\" -DSYNCCHECK -DTHREADPOOL -D_GLIBCXX_USE_NANOSLEEP -D_GNU_SOURCE=1 -D_RANDOM_TCC -D_REENTRANT -I/<>/AI/Skirmish/CircuitAI/src/circuit -I/<>/AI/Skirmish/CircuitAI/src/lib -I/usr/include/SDL2 -I/<>/obj-x86_64-linux-gnu/AI/Wrappers/Cpp/src-generated -I/<>/AI/Wrappers/Cpp/src -I/<>/rts -I/<>/obj-x86_64-linux-gnu/src-generated/engine -I/<>/rts/ExternalAI/Interface -I/<>/AI/Wrappers -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++17 -fdiagnostics-color=auto -march=native -msse -mfpmath=sse -mno-sse2 -mno-sse3 -mno-ssse3 -mno-sse4.1 -mno-sse4.2 -mno-sse4 -mno-sse4a -mno-avx -mno-fma -m no-fma4 -mno-xop -mno-lwp -mno-avx2 -fsingle-precision-constant -frounding-math -mieee-fp -pipe -fno-strict-aliasing -fvisibility=hidden -fvisibility-inlines-hidden -pthread -O2 -Wformat -Wformat-security -DNDEBUG -g -fPIC -fpic -Wall -o
Processed: tagging 994521
Processing commands for cont...@bugs.debian.org: > tags 994521 + sid Bug #994521 [ledmon] ledmon: libsgutils2-2 1.46 update breaks ledmon Added tag(s) sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 994521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994521 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#984349 marked as pending in spring
Processing control commands: > tag -1 pending Bug #984349 [src:spring] spring: ftbfs with GCC-11 Added tag(s) pending. -- 984349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984349 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984349: marked as pending in spring
Control: tag -1 pending Hello, Bug #984349 in spring 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/games-team/spring/-/commit/26c9b47f03e7cc474ee400a4b2cf303e5e2038e0 Fix FTBFS with GCC 11. Closes: #984349 (this message was generated automatically) -- Greetings https://bugs.debian.org/984349
Bug#996589: cloudcompare FTBFS on !amd64
Source: cloudcompare Version: 2.11.3-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=cloudcompare=2.11.3-2 There are at least two separate errors: ... /<>/plugins/core/Standard/qRANSAC_SD/RANSAC_SD_orig/MiscLib/AlignedAllocator.h: In member function ‘T* MiscLib::AlignedAllocator::allocate(MiscLib::AlignedAllocator::size_type, std::allocator::const_pointer)’: /<>/plugins/core/Standard/qRANSAC_SD/RANSAC_SD_orig/MiscLib/AlignedAllocator.h:30:29: error: there are no arguments to ‘aligned_alloc’ that depend on a template parameter, so a declaration of ‘aligned_alloc’ must be available [-fpermissive] 30 | #define a_malloc(sz, align) aligned_alloc((align), (sz)) | ^ ... ... make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libavutil.so', needed by 'plugins/core/Standard/qAnimation/libQANIMATION_PLUGIN.so'. Stop. make[3]: *** Waiting for unfinished jobs ...
Bug#996586: heimdal: CVE-2021-3671
Source: heimdal Version: 7.7.0+dfsg-2 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 7.5.0+dfsg-3 Hi, The following vulnerability was published for heimdal. CVE-2021-3671[0]: | A null pointer de-reference was found in the way samba kerberos server | handled missing sname in TGS-REQ (Ticket Granting Server - Request). | An authenticated user could use this flaw to crash the samba server. 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-2021-3671 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3671 [1] https://github.com/heimdal/heimdal/commit/04171147948d0a3636bc6374181926f0fb2ec83a [2] https://github.com/heimdal/heimdal/commit/773802aecfb4b6a73817fa522faeb55b2a7cdb2a Regards, Salvatore
Processed: heimdal: CVE-2021-3671
Processing control commands: > found -1 7.5.0+dfsg-3 Bug #996586 [src:heimdal] heimdal: CVE-2021-3671 Marked as found in versions heimdal/7.5.0+dfsg-3. -- 996586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996586 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996583: xir FTBFS
Source: xir
Version: 1.3.2-1
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/xir.html
https://buildd.debian.org/status/logs.php?pkg=xir=1.3.2-1
...
/<>/src/xir/graph/elf2xir.cpp: In instantiation of ‘std::ostream&
{anonymous}::operator<<(std::ostream&, const std::vector&) [with T =
std::__cxx11::basic_string; std::ostream = std::basic_ostream]’:
/<>/src/xir/graph/elf2xir.cpp:1010:33: required from here
/<>/src/xir/graph/elf2xir.cpp:403:19: error: loop variable ‘x’
creates a copy from type ‘const std::__cxx11::basic_string’
[-Werror=range-loop-construct]
403 | for (const auto x : v) {
| ^
/<>/src/xir/graph/elf2xir.cpp:403:19: note: use reference type to
prevent copying
403 | for (const auto x : v) {
| ^
| &
...
Bug#993324: libgsl25: ABI breakage: removed symbol gsl_linalg_QR_TR_decomp
On 15 October 2021 at 20:35, Sebastian Ramacher wrote: | On 2021-10-15 10:38:48 -0500, Dirk Eddelbuettel wrote: | > | > Turns out this was fully my fault. The 2.7 release sets the SO number to 26, | > and I didn't use that. | | No, it doesn't. gsl 2.7 has current=26 and age=1, meaning the the SOVERSION | is 25. gsl 2.6 had current=25, age=0. Increasing current was correct, | increasing age wasn't. I will admit not fully understanding the three components used as eg in upstream's configuire.ac: dnl Library versioning (C:R:A == current:revision:age) dnl See the libtool manual for an explanation of the numbers dnl dnl gsl-1.0libgsl 0:0:0 libgslcblas 0:0:0 [...] dnl gsl-2.6libgsl 25:0:0 libgslcblas 0:0:0 dnl gsl-2.7libgsl 26:0:1 libgslcblas 0:0:0 and GSL_CURRENT=26 GSL_REVISION=0 GSL_AGE=1 If I understand you correctly we needed / need dnl gsl-2.7libgsl 26:0:0 libgslcblas 0:0:0 GSL_CURRENT=26 GSL_REVISION=0 GSL_AGE=0 Is that correct (as far as the Debian package goes) ? What do you (ie Sebastian) suggest we do going forward? Be more careful about increasing CURRENT (only) when the ABI changes? (And I CC'ed Patrick from GSL upstream now.) Dirk -- https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#993324: libgsl25: ABI breakage: removed symbol gsl_linalg_QR_TR_decomp
On 2021-10-15 10:38:48 -0500, Dirk Eddelbuettel wrote: > > Turns out this was fully my fault. The 2.7 release sets the SO number to 26, > and I didn't use that. No, it doesn't. gsl 2.7 has current=26 and age=1, meaning the the SOVERSION is 25. gsl 2.6 had current=25, age=0. Increasing current was correct, increasing age wasn't. Cheers > > So a new package will be forthcoming, and likely need a transition. That > means I should upload to experimental first, right, to then request the > transition? (I'll read up on it later today as a refresher but I guess > Graham is fully immersed in this practice?) > > Dirk > > -- > https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#984077: marked as done (kasumi: ftbfs with GCC-11)
Your message dated Fri, 15 Oct 2021 18:03:47 +
with message-id
and subject line Bug#984077: fixed in kasumi 2.5-10
has caused the Debian Bug report #984077,
regarding kasumi: ftbfs with GCC-11
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.)
--
984077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:kasumi
Version: 2.5-9
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11
[This bug is not targeted to the upcoming bullseye 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.
The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/kasumi_2.5-9_unstable_gcc11.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.
[...]
| ^
KasumiWord.cxx:205:5: error: ISO C++17 does not allow dynamic exception
specifications
205 | throw(KasumiException){
| ^
KasumiDic.cxx:50:3: error: ISO C++17 does not allow dynamic exception
specifications
50 | throw(KasumiException){
| ^
KasumiDic.cxx:72:5: error: ISO C++17 does not allow dynamic exception
specifications
72 | throw(KasumiException){
| ^
KasumiDic.cxx:189:5: error: ISO C++17 does not allow dynamic exception
specifications
189 | throw(KasumiException)
| ^
make[3]: *** [Makefile:602: KasumiWord.o] Error 1
make[3]: *** [Makefile:602: KasumiDic.o] Error 1
In file included from KasumiWord.hxx:36,
from KasumiDic.hxx:36,
from main.cxx:37:
KasumiConfiguration.hxx:41:32: error: ISO C++17 does not allow dynamic
exception specifications
41 | void loadDefaultProperties() throw(KasumiException);
|^
KasumiConfiguration.hxx:42:32: error: ISO C++17 does not allow dynamic
exception specifications
42 | void loadConfigurationFile() throw (KasumiException);
|^
KasumiConfiguration.hxx:44:5: error: ISO C++17 does not allow dynamic exception
specifications
44 | throw(KasumiException);
| ^
KasumiConfiguration.hxx:45:28: error: ISO C++17 does not allow dynamic
exception specifications
45 | void saveConfiguration() throw (KasumiException);
|^
KasumiConfiguration.hxx:48:24: error: ISO C++17 does not allow dynamic
exception specifications
48 | void checkValidity() throw(KasumiException);
|^
KasumiConfiguration.hxx:50:47: error: ISO C++17 does not allow dynamic
exception specifications
50 | KasumiConfiguration(int argc, char *argv[]) throw (KasumiException);
| ^
In file included from KasumiDic.hxx:36,
from main.cxx:37:
KasumiWord.hxx:73:7: error: ISO C++17 does not allow dynamic exception
specifications
73 | throw(KasumiException);
| ^
KasumiWord.hxx:75:7: error: ISO C++17 does not allow dynamic exception
specifications
75 | throw(KasumiException);
| ^
In file included from main.cxx:37:
KasumiDic.hxx:52:40: error: ISO C++17 does not allow dynamic exception
specifications
52 | void load(KasumiConfiguration *conf) throw (KasumiException);
|^
KasumiDic.hxx:55:9:
Bug#996561: qepcad fails autopkgtests on !amd64, !i386
Control: tags -1 confirmed On Fri 15 Oct 2021 10:29:40 AM EDT, Nilesh Patra wrote: qepcad fails its autopkgtests on every non-x86 arch as seen here. Can you fix this? I confirmed that QEPCAD isn't functioning for me locally on an armhf system (Raspberry Pi). I'll see if I can track down the issue. Doug signature.asc Description: PGP signature
Processed: Re: Bug#996561: qepcad fails autopkgtests on !amd64, !i386
Processing control commands: > tags -1 confirmed Bug #996561 [qepcad] qepcad fails autopkgtests on !amd64, !i386 Added tag(s) confirmed. -- 996561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996561 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996461: nvidia-kernel-dkms: DKMS tree already contains: nvidia-current-470.74
On 2021-10-15 19:23, Andreas Beckmann wrote: On 14/10/2021 12.15, Drew Parsons wrote: Package: nvidia-kernel-dkms Version: 470.74-1 Severity: serious Justification: fails to configure Upgrade to the new nvidia-driver 470.74-1 (nvidia-kernel-dkms) fails at the configuration step with this error message: $ sudo aptitude Performing actions... Setting up nvidia-kernel-dkms (470.74-1) ... Removing old nvidia-current-470.74 DKMS files... Loading new nvidia-current-470.74 DKMS files... Error! DKMS tree already contains: nvidia-current-470.74 You cannot add the same module/version combo more than once. What happened earlier? Did you somehow try to manually install the 470.74 driver from the .run file? No, I didn't try any manual installations. Only upgrading nvidia-driver and nvidia-kernel-dkms etc to the version in experimental at times. What happened at the first configuration attempt of the package? You should find the full transcript of upgrading to 470 somewhere in /var/log/apt/term.log* /var/log/apt/term.log tells me it was upgrading from 470.63.01-1 Nothing unusual in the unpacking step (I guess we can ignore the message "Deleting from: /lib/modules/5.14.0-1-amd64/ rmdir: failed to remove '': No such file or directory"), ... Unpacking nvidia-vdpau-driver:i386 (470.74-1) over (470.63.01-1) ... Preparing to unpack .../056-nvidia-kernel-dkms_470.74-1_amd64.deb ... Module nvidia-current-470.63.01 for kernel 5.14.0-1-amd64 (x86_64). Before uninstall, this module version was ACTIVE on this kernel. nvidia-current.ko: - Uninstallation - Deleting from: /lib/modules/5.14.0-1-amd64/ rmdir: failed to remove '': No such file or directory - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. nvidia-current-modeset.ko: - Uninstallation - Deleting from: /lib/modules/5.14.0-1-amd64/ rmdir: failed to remove '': No such file or directory - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. ... Deleting module nvidia-current-470.63.01 completely from the DKMS tree. Unpacking nvidia-kernel-dkms (470.74-1) over (470.63.01-1) ... Preparing to unpack .../057-nvidia-kernel-support_470.74-1_amd64.deb ... Unpacking nvidia-kernel-support (470.74-1) over (470.63.01-1) ... ... Then setup step shows no errors, until ... Setting up nvidia-vdpau-driver:amd64 (470.74-1) ... Setting up nvidia-vdpau-driver:i386 (470.74-1) ... Setting up libgl1-nvidia-glvnd-glx:amd64 (470.74-1) ... Setting up nvidia-kernel-dkms (470.74-1) ... Loading new nvidia-current-470.74 DKMS files... Building for 5.14.0-2-amd64 Building initial module for 5.14.0-2-amd64 + [ clean = modules ] At main.c:160: - SSL error:02001002:system library:fopen:No such file or directory: ../crypto/bio/bss_file.c:69 - SSL error:2006D080:BIO routines:BIO_new_file:no such file: ../crypto/bio/bss_file.c:76 sign-file: /root/dkms.key: No such file or directory Error! Bad exit status 1 for sign tool. Consult /var/lib/dkms/nvidia-current/470.74/5.14.0-2-amd64/x86_64/log/make.log for more information. dpkg: error processing package nvidia-kernel-dkms (--configure): installed nvidia-kernel-dkms package post-installation script subprocess returned error exit status 11 Setting up libgles-nvidia1:amd64 (470.74-1) ... Setting up libegl-nvidia0:amd64 (470.74-1) ... Setting up nvidia-smi (470.74-1) ... dpkg: dependency problems prevent configuration of nvidia-driver: nvidia-driver depends on nvidia-kernel-dkms (= 470.74-1) | nvidia-kernel-470.74; however: Package nvidia-kernel-dkms is not configured yet. Package nvidia-kernel-470.74 is not installed. Package nvidia-kernel-dkms which provides nvidia-kernel-470.74 is not configured yet. dpkg: error processing package nvidia-driver (--configure): dependency problems - leaving unconfigured Setting up nvidia-driver-bin (470.74-1) ... I guess that reference to bss_file.c must be a clue, if not the reference to the missing /root/dkms.key The 470.74/5.14.0-2 make.log in the error message shows no errors itself, but the last line is "Signing /var/lib/dkms/nvidia-current/470.74/build/nvidia.ko" Drew
Processed: Bug#984077 marked as pending in kasumi
Processing control commands: > tag -1 pending Bug #984077 [src:kasumi] kasumi: ftbfs with GCC-11 Added tag(s) pending. -- 984077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984077 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984077: marked as pending in kasumi
Control: tag -1 pending Hello, Bug #984077 in kasumi 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/kasumi/-/commit/b14d07848974a091f6d1467a12a78b90b5ea9864 debian/rules: Force std=c++14 to fix ftbfs with gcc 11 (Closes: #984077) (this message was generated automatically) -- Greetings https://bugs.debian.org/984077
Bug#996461: nvidia-kernel-dkms: DKMS tree already contains: nvidia-current-470.74
On 14/10/2021 12.15, Drew Parsons wrote: Package: nvidia-kernel-dkms Version: 470.74-1 Severity: serious Justification: fails to configure Upgrade to the new nvidia-driver 470.74-1 (nvidia-kernel-dkms) fails at the configuration step with this error message: $ sudo aptitude Performing actions... Setting up nvidia-kernel-dkms (470.74-1) ... Removing old nvidia-current-470.74 DKMS files... Loading new nvidia-current-470.74 DKMS files... Error! DKMS tree already contains: nvidia-current-470.74 You cannot add the same module/version combo more than once. What happened earlier? Did you somehow try to manually install the 470.74 driver from the .run file? What happened at the first configuration attempt of the package? You should find the full transcript of upgrading to 470 somewhere in /var/log/apt/term.log* Andreas
Bug#984164: marked as done (gyoto: ftbfs with GCC-11)
Your message dated Fri, 15 Oct 2021 17:03:42 + with message-id and subject line Bug#984164: fixed in gyoto 1.4.4-6 has caused the Debian Bug report #984164, regarding gyoto: ftbfs with GCC-11 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.) -- 984164: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984164 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gyoto Version: 1.4.4-3 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/gyoto_1.4.4-3_unstable_gcc11.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. [...] 667 | data->binspectrum=curvect; | ^~~~ In file included from /usr/include/c++/11/vector:69, from ../include/GyotoDefs.h:29, from gyoto.C:21: /usr/include/c++/11/bits/range_access.h:318:5: note: candidates are: ‘template constexpr const _Tp* std::data(std::initializer_list<_Tp>)’ 318 | data(initializer_list<_Tp> __il) noexcept | ^~~~ /usr/include/c++/11/bits/range_access.h:309:5: note: ‘template constexpr _Tp* std::data(_Tp (&)[_Nm])’ 309 | data(_Tp (&__array)[_Nm]) noexcept | ^~~~ /usr/include/c++/11/bits/range_access.h:299:5: note: ‘template constexpr decltype (__cont.data()) std::data(const _Container&)’ 299 | data(const _Container& __cont) noexcept(noexcept(__cont.data())) | ^~~~ /usr/include/c++/11/bits/range_access.h:289:5: note: ‘template constexpr decltype (__cont.data()) std::data(_Container&)’ 289 | data(_Container& __cont) noexcept(noexcept(__cont.data())) | ^~~~ gyoto.C:64:42: note: ‘Gyoto::SmartPointer data’ 64 | static SmartPointer data = NULL; | ^~~~ gyoto.C:670:7: error: reference to ‘data’ is ambiguous 670 | data->offset=int(offset); | ^~~~ In file included from /usr/include/c++/11/vector:69, from ../include/GyotoDefs.h:29, from gyoto.C:21: /usr/include/c++/11/bits/range_access.h:318:5: note: candidates are: ‘template constexpr const _Tp* std::data(std::initializer_list<_Tp>)’ 318 | data(initializer_list<_Tp> __il) noexcept | ^~~~ /usr/include/c++/11/bits/range_access.h:309:5: note: ‘template constexpr _Tp* std::data(_Tp (&)[_Nm])’ 309 | data(_Tp (&__array)[_Nm]) noexcept | ^~~~ /usr/include/c++/11/bits/range_access.h:299:5: note: ‘template constexpr decltype (__cont.data()) std::data(const _Container&)’ 299 | data(const _Container& __cont) noexcept(noexcept(__cont.data())) | ^~~~ /usr/include/c++/11/bits/range_access.h:289:5: note: ‘template constexpr decltype (__cont.data()) std::data(_Container&)’ 289 | data(_Container& __cont) noexcept(noexcept(__cont.data())) | ^~~~ gyoto.C:64:42: note: ‘Gyoto::SmartPointer data’ 64 | static SmartPointer data = NULL; | ^~~~ gyoto.C:691:31: error: reference to ‘data’ is ambiguous 691 | scenery -> rayTrace(grid, data,
Bug#984340: marked as done (solarpowerlog: ftbfs with GCC-11)
Your message dated Fri, 15 Oct 2021 16:34:44 + with message-id and subject line Bug#984340: fixed in solarpowerlog 0.24-9 has caused the Debian Bug report #984340, regarding solarpowerlog: ftbfs with GCC-11 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.) -- 984340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984340 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:solarpowerlog Version: 0.24-8 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/solarpowerlog_0.24-8_unstable_gcc11.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. [...] configure: Shared Communication: .. yes configure: FILTERS AND LOGGERS: configure: CSV logger support: yes configure: Dumb Dumper support: ... yes configure: HTML Writer support: ... yes dh_auto_build make -j4 make[1]: Entering directory '/<>' Making all in src make[2]: Entering directory '/<>/src' make all-am make[3]: Entering directory '/<>/src' g++ -DHAVE_CONFIG_H -I. -DLINUX -D_REENTRANT -D_GNU_SOURCE -I/usr/include/apr-1.0 -I ../extlibs -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -pthread -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o solarpowerlog-CCapability.o `test -f 'interfaces/CCapability.cpp' || echo './'`interfaces/CCapability.cpp g++ -DHAVE_CONFIG_H -I. -DLINUX -D_REENTRANT -D_GNU_SOURCE -I/usr/include/apr-1.0 -I ../extlibs -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -pthread -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o solarpowerlog-CMutexHelper.o `test -f 'interfaces/CMutexHelper.cpp' || echo './'`interfaces/CMutexHelper.cpp g++ -DHAVE_CONFIG_H -I. -DLINUX -D_REENTRANT -D_GNU_SOURCE -I/usr/include/apr-1.0 -I ../extlibs -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -pthread -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o solarpowerlog-InverterFactoryFactory.o `test -f 'Inverters/factories/InverterFactoryFactory.cpp' || echo './'`Inverters/factories/InverterFactoryFactory.cpp g++ -DHAVE_CONFIG_H -I. -DLINUX -D_REENTRANT -D_GNU_SOURCE -I/usr/include/apr-1.0 -I ../extlibs -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -pthread -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o solarpowerlog-IInverterFactory.o `test -f 'Inverters/factories/IInverterFactory.cpp' || echo './'`Inverters/factories/IInverterFactory.cpp g++ -DHAVE_CONFIG_H -I. -DLINUX -D_REENTRANT -D_GNU_SOURCE -I/usr/include/apr-1.0 -I ../extlibs -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -pthread -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o solarpowerlog-CWorkScheduler.o `test -f 'interfaces/CWorkScheduler.cpp' || echo './'`interfaces/CWorkScheduler.cpp g++ -DHAVE_CONFIG_H -I. -DLINUX -D_REENTRANT -D_GNU_SOURCE -I/usr/include/apr-1.0 -I ../extlibs -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -pthread -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
Bug#816393: Works now?
Hello, for what is worth: helge@samd:/tmp$ debget nghttp2 Get:1 http://172.16.18.51:/ftp.de.debian.org/debian bullseye/main amd64 nghttp2 all 1.43.0-1 [14.4 kB] Fetched 14.4 kB in 0s (117 kB/s) Best greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc Description: PGP signature
Processed: bug 983977 is forwarded to https://sourceforge.net/p/avarice/bugs/34/
Processing commands for cont...@bugs.debian.org: > forwarded 983977 https://sourceforge.net/p/avarice/bugs/34/ Bug #983977 [src:avarice] avarice: ftbfs with GCC-11 Set Bug forwarded-to-address to 'https://sourceforge.net/p/avarice/bugs/34/'. > thanks Stopping processing here. Please contact me if you need assistance. -- 983977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983977 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#983977: (no subject)
Control: tags -1 fixed-upstream This seems to be fixed upstream with svn commit r391. I'll take a look in updating the package soon(tm)... -- tobi
Bug#995756: marked as done (gnome-shell-extension-autohidetopbar: missing file /usr/share/gnome-shell/extensions/hidetop...@mathieu.bidon.ca/Settings-40.ui)
Your message dated Fri, 15 Oct 2021 16:19:27 + with message-id and subject line Bug#995756: fixed in gnome-shell-extension-autohidetopbar 20211001-1 has caused the Debian Bug report #995756, regarding gnome-shell-extension-autohidetopbar: missing file /usr/share/gnome-shell/extensions/hidetop...@mathieu.bidon.ca/Settings-40.ui 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.) -- 995756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995756 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-shell-extension-autohidetopbar Version: 20210525-2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: tomas.ju...@gmail.com missing file /usr/share/gnome-shell/extensions/hidetop...@mathieu.bidon.ca/Settings-40.ui consequently the extension cannot be activated using extension-manager -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.0-1-amd64 (SMP w/6 CPU threads) Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.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 gnome-shell-extension-autohidetopbar depends on: ii gnome-shell 40.5-1+b1 Versions of packages gnome-shell-extension-autohidetopbar recommends: ii gnome-shell-extension-prefs 40.5-1+b1 gnome-shell-extension-autohidetopbar suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: gnome-shell-extension-autohidetopbar Source-Version: 20211001-1 Done: Tobias Frost We believe that the bug you reported is fixed in the latest version of gnome-shell-extension-autohidetopbar, 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 995...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tobias Frost (supplier of updated gnome-shell-extension-autohidetopbar package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 15 Oct 2021 17:57:27 +0200 Source: gnome-shell-extension-autohidetopbar Architecture: source Version: 20211001-1 Distribution: unstable Urgency: medium Maintainer: Tobias Frost Changed-By: Tobias Frost Closes: 995756 996046 Changes: gnome-shell-extension-autohidetopbar (20211001-1) unstable; urgency=medium . * New upstream git snapshot. - This version declares compatibility with GNOME 41. (Closes: #996046) * Install the file Settings-40.ui for GNOME 40 compatibility. Thanks to Tomas for the triaging and bug report (Closes: #995756). Checksums-Sha1: ec07fae20287b02d4655c858f9e856d0cc1fccb6 2187 gnome-shell-extension-autohidetopbar_20211001-1.dsc 2702a5ec8d5759e67920d7ccf8b041dfe77e06ca 28216 gnome-shell-extension-autohidetopbar_20211001.orig.tar.xz 44cffe5c841d5338c38a3cb4763fee6d724a1bf9 4940 gnome-shell-extension-autohidetopbar_20211001-1.debian.tar.xz 1ee16e178a6e00c1f5e8ef07a5a590a8e9bfc0fd 6933 gnome-shell-extension-autohidetopbar_20211001-1_amd64.buildinfo Checksums-Sha256: 0fb635fb25448cda26d3d3536d3b7e03e22614a42a5fb37cdb11d85f42fd194e 2187 gnome-shell-extension-autohidetopbar_20211001-1.dsc 7cc1d16c982d3e9f7ba025892c8ec402d8228cd621f0085709654ed529d7df2c 28216 gnome-shell-extension-autohidetopbar_20211001.orig.tar.xz 1bee2c1ed9440691a2ef5863c3f5b717a090f7af1f67dbc8be2bda1e1fa53cf7 4940 gnome-shell-extension-autohidetopbar_20211001-1.debian.tar.xz a610a3429469bcb5d60aaf98e92f4cc102837107de1e5f5abe8b44fbb4de444d 6933 gnome-shell-extension-autohidetopbar_20211001-1_amd64.buildinfo Files: d3ec16b15d2889dfdfbc6d4d81dd06f3 2187 gnome optional gnome-shell-extension-autohidetopbar_20211001-1.dsc 64a9cc05445148911ca77ad2719e8b9c 28216 gnome optional gnome-shell-extension-autohidetopbar_20211001.orig.tar.xz ebe7255c250b60f2f4c8c5c5b65c00f1 4940 gnome optional gnome-shell-extension-autohidetopbar_20211001-1.debian.tar.xz dbfbcec0a1485201f533ed76be06bc34 6933 gnome optional gnome-shell-extension-autohidetopbar_20211001-1_amd64.buildinfo -BEGIN PGP SIGNATURE-
Bug#983958: marked as done (aces3: ftbfs with GCC-11)
Your message dated Fri, 15 Oct 2021 16:03:50 + with message-id and subject line Bug#983958: fixed in aces3 3.0.8-8 has caused the Debian Bug report #983958, regarding aces3: ftbfs with GCC-11 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.) -- 983958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983958 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:aces3 Version: 3.0.8-7 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/aces3_3.0.8-7_unstable_gcc11.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. [...] 1220 | Call igetrec(0, 'JOBARC', 'HAVEGEOM', i_length, i_havegeom) | 2 .. 2591 | call igetrec(20,'JOBARC','EASYM_A ',nIrrps,iArr) |1 Error: Rank mismatch between actual argument at (1) and actual argument at (2) (scalar and rank-1) aces3_gtflgs.F:2594:52: 1220 | Call igetrec(0, 'JOBARC', 'HAVEGEOM', i_length, i_havegeom) | 2 .. 2594 | call igetrec(20,'JOBARC','EASYM_B ',nIrrps,iArr) |1 Error: Rank mismatch between actual argument at (1) and actual argument at (2) (scalar and rank-1) aces3_gtflgs.F:2615:55: 1220 | Call igetrec(0, 'JOBARC', 'HAVEGEOM', i_length, i_havegeom) | 2 .. 2615 | call igetrec(20,'JOBARC','FDIRREP ',iTmpReg21,iArr) | 1 Error: Rank mismatch between actual argument at (1) and actual argument at (2) (scalar and rank-1) aces3_gtflgs.F:2622:55: 1220 | Call igetrec(0, 'JOBARC', 'HAVEGEOM', i_length, i_havegeom) | 2 .. 2622 | call igetrec(20,'JOBARC','EESYMINF',iTmpReg28,iArr) | 1 Error: Rank mismatch between actual argument at (1) and actual argument at (2) (scalar and rank-1) aces3_gtflgs.F:2629:55: 1220 | Call igetrec(0, 'JOBARC', 'HAVEGEOM', i_length, i_havegeom) | 2 .. 2629 | call igetrec(20,'JOBARC','QRHFIRR ',iTmpReg22,iArr) | 1 Error: Rank mismatch between actual argument at (1) and actual argument at (2) (scalar and rank-1) aces3_gtflgs.F:2642:55: 1220 | Call igetrec(0, 'JOBARC', 'HAVEGEOM', i_length, i_havegeom) | 2 .. 2642 | call igetrec(20,'JOBARC','QRHFLOC ',iTmpReg25,iArr) | 1 Error: Rank mismatch between actual argument at (1) and actual argument at (2) (scalar and rank-1) aces3_gtflgs.F:2667:56: 361 | call iputrec(-1,'JOBARC','EA_IRREP',1,nIrr) |2 .. 2667 | call iputrec(20,'JOBARC','IFLAGS ',dim_iflags,ioppar)
Bug#993324: libgsl25: ABI breakage: removed symbol gsl_linalg_QR_TR_decomp
Turns out this was fully my fault. The 2.7 release sets the SO number to 26, and I didn't use that. So a new package will be forthcoming, and likely need a transition. That means I should upload to experimental first, right, to then request the transition? (I'll read up on it later today as a refresher but I guess Graham is fully immersed in this practice?) Dirk -- https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Processed: tagging 995756
Processing commands for cont...@bugs.debian.org: > tags 995756 + pending Bug #995756 [gnome-shell-extension-autohidetopbar] gnome-shell-extension-autohidetopbar: missing file /usr/share/gnome-shell/extensions/hidetop...@mathieu.bidon.ca/Settings-40.ui Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 995756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995756 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996561: qepcad fails autopkgtests on !amd64 and !i386
On Fri, 15 Oct 2021 19:59:40 +0530 Nilesh Patra wrote: > Package: qepcad > Version: 1.74+ds-2 > Severity: serious > X-Debbugs-Cc: dtorra...@piedmont.edu > > Hi Doug, > > qepcad fails its autopkgtests on every non-x86 arch as seen here. > Can you fix this? > > https://qa.debian.org/excuses.php?package=qepcad Precisely, the error is: qepcad < debian/tests/anai && qepcad < debian/tests/edge-square-product && qepcad < debian/tests/quartic && qepcad < debian/tests/hong-liska-steinberg && cad2d < debian/tests/cad2d autopkgtest [07:03:40]: test command1: [--- terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc bash: line 1: 2418 Aborted qepcad < debian/tests/positive-semidefinite autopkgtest [07:06:04]: test command1: ---] autopkgtest [07:06:04]: test command1: - - - - - - - - - - results - - - - - - - - - - command1 FAIL non-zero exit status 134 -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Processed: Re: libloki: ftbfs with GCC-11
Processing control commands: > tags -1 patch Bug #984186 [src:libloki] libloki: ftbfs with GCC-11 Added tag(s) patch. -- 984186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984186 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984186: libloki: ftbfs with GCC-11
Package: libloki
Version: 0.1.7-3
Followup-For: Bug #984186
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu ubuntu-patch
X-Debbugs-Cc: sl...@ubuntu.com
Control: tags -1 patch
Dear Maintainer,
GCC 11 defaults to C++17 which does not allow dynamic exception specifications
anymore: https://gcc.gnu.org/gcc-11/porting_to.html
In Ubuntu, the attached patch was applied to replace the throw(...)
specifications in the recommended way:
* Fix FTBFS with GCC-11 by avoiding dynamic exception specifications
Thanks for considering the patch.
Cheers,
Lukas
-- System Information:
Debian Release: 11.0
APT prefers impish
APT policy: (500, 'impish')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.13.0-16-generic (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE:en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
only in patch2:
unchanged:
--- libloki-0.1.7.orig/include/loki/SmallObj.h
+++ libloki-0.1.7/include/loki/SmallObj.h
@@ -459,7 +459,7 @@
/// @note MSVC complains about non-empty exception specification lists.
static void * operator new ( std::size_t size )
#else
-static void * operator new ( std::size_t size ) throw ( std::bad_alloc
)
+static void * operator new ( std::size_t size ) noexcept(false)
#endif
{
typename MyThreadingModel::Lock lock;
@@ -468,7 +468,7 @@
}
/// Non-throwing single-object new returns NULL if allocation fails.
-static void * operator new ( std::size_t size, const std::nothrow_t &
) throw ()
+static void * operator new ( std::size_t size, const std::nothrow_t &
) noexcept
{
typename MyThreadingModel::Lock lock;
(void)lock; // get rid of warning
@@ -482,7 +482,7 @@
}
/// Single-object delete.
-static void operator delete ( void * p, std::size_t size ) throw ()
+static void operator delete ( void * p, std::size_t size ) noexcept
{
typename MyThreadingModel::Lock lock;
(void)lock; // get rid of warning
@@ -512,8 +512,7 @@
/// @note MSVC complains about non-empty exception specification lists.
static void * operator new [] ( std::size_t size )
#else
-static void * operator new [] ( std::size_t size )
-throw ( std::bad_alloc )
+static void * operator new [] ( std::size_t size ) noexcept(false)
#endif
{
typename MyThreadingModel::Lock lock;
@@ -523,7 +522,7 @@
/// Non-throwing array-object new returns NULL if allocation fails.
static void * operator new [] ( std::size_t size,
-const std::nothrow_t & ) throw ()
+const std::nothrow_t & ) noexcept
{
typename MyThreadingModel::Lock lock;
(void)lock; // get rid of warning
@@ -537,7 +536,7 @@
}
/// Array-object delete.
-static void operator delete [] ( void * p, std::size_t size ) throw ()
+static void operator delete [] ( void * p, std::size_t size ) noexcept
{
typename MyThreadingModel::Lock lock;
(void)lock; // get rid of warning
Bug#996561: qepcad fails autopkgtests on !amd64, !i386
Package: qepcad Version: 1.74+ds-2 Severity: serious X-Debbugs-Cc: dtorra...@piedmont.edu Hi Doug, qepcad fails its autopkgtests on every non-x86 arch as seen here. Can you fix this? https://qa.debian.org/excuses.php?package=qepcad Nilesh -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-1-amd64 (SMP w/8 CPU threads) 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
Bug#993324: libgsl25: ABI breakage: removed symbol gsl_linalg_QR_TR_decomp
Graham, On 15 October 2021 at 13:34, Graham Inggs wrote: | > Yes. And I follow upstream. They didn't change :-/ | | Right, so please speak to your upstream. Dropping (or renaming) a Done. Looks like a 2.8 release is coming, so maybe the soname gets cleaned up there and we get to do (yet another full) transition (which is really the best way to handle this under changes). | symbol is changing the ABI in a backward-incompatible way, and they | need to bump the SONAME (or revert the change). | | This is not something Debian-specific, this is how shared objects in | Unix work [1][2]. Thanks for the pointers. As you may imagine, I actually already have come across this practice in my 26 years with Debian . Best, Dirk -- https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#930332: marked as done (FTBFS on arm64: FAIL: peer_test.go:79: PeerSuite.Test_NameForPresentation_returnsTheNameIfItExistsButJidOtherwise)
Your message dated Fri, 15 Oct 2021 13:39:42 +
with message-id
and subject line Bug#994195: Removed package(s) from unstable
has caused the Debian Bug report #930332,
regarding FTBFS on arm64: FAIL: peer_test.go:79:
PeerSuite.Test_NameForPresentation_returnsTheNameIfItExistsButJidOtherwise
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.)
--
930332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930332
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: coyim
Version: 0.3.8+ds-6
Severity: grave
When binNMU coyim in sid, it FTBFS on arm64,
https://buildd.debian.org/status/fetch.php?pkg=coyim=arm64=0.3.8%2Bds-6%2Bb10=1552303594=0
Log is
FAIL: peer_test.go:79:
PeerSuite.Test_NameForPresentation_returnsTheNameIfItExistsButJidOtherwise
peer_test.go:80:
c.Assert(({Name: "foo", Jid: "f...@bar.com"}).NameForPresentation(),
g.Equals, "foo")
... obtained string = "f...@bar.com"
... expected string = "foo"
OOPS: 36 passed, 1 FAILED
--- FAIL: Test (0.03s)
This looks strange to me... I can reproduce it on porterbox(amdahl.d.o).
I checked the code, it should be correct...
--
Shengjing Zhu
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 0.3.8+ds-6+rm
Dear submitter,
as the package coyim has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/994195
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---
Bug#996558: knot: FTBFS with new automake (putting "none required" into build flags)
Package: knot Version: 3.0.5-1 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu ubuntu-patch X-Debbugs-Cc: sl...@ubuntu.com Dear Maintainer, knot fails to build from source with newer autotools: libtool: link: gcc -g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -Wall -DNDEBUG -Wall -Wshadow -Werror=format-security -Werror=implicit -Werror=attributes -Wstrict-prototypes -Wl,-Bsymbolic-functions -flto=auto -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -o .libs/kxdpgun utils/kxdpgun/kxdpgun-load_queries.o utils/kxdpgun/kxdpgun-main.o utils/kxdpgun/kxdpgun-popenve.o none required ./.libs/libcontrib.a ./.libs/libknot.so -lcap-ng /usr/bin/ld: cannot find none: No such file or directory /usr/bin/ld: cannot find required: No such file or directory collect2: error: ld returned 1 exit status make[4]: *** [Makefile:3354: kxdpgun] Error 1 The problem was fixed upstream: https://gitlab.nic.cz/knot/knot-dns/-/commit/70dc4a5c85b65678662854c18a3475371ef4a8eb In Ubuntu, the attached patch was applied to achieve the following: * Fix FTBFS with new automake, using upstream commit + debian/patches/70dc4a5c85b65678662854c18a3475371ef4a8eb.patch Thanks for considering the patch. Cheers, Lukas -- System Information: Debian Release: 11.0 APT prefers impish APT policy: (500, 'impish') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.13.0-16-generic (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE:en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru knot-3.0.5/debian/patches/70dc4a5c85b65678662854c18a3475371ef4a8eb.patch knot-3.0.5/debian/patches/70dc4a5c85b65678662854c18a3475371ef4a8eb.patch --- knot-3.0.5/debian/patches/70dc4a5c85b65678662854c18a3475371ef4a8eb.patch 1970-01-01 01:00:00.0 +0100 +++ knot-3.0.5/debian/patches/70dc4a5c85b65678662854c18a3475371ef4a8eb.patch 2021-10-15 15:14:17.0 +0200 @@ -0,0 +1,60 @@ +From 70dc4a5c85b65678662854c18a3475371ef4a8eb Mon Sep 17 00:00:00 2001 +From: Daniel Salzman +Date: Wed, 14 Jul 2021 14:29:13 +0200 +Subject: [PATCH] configure: fix AC_SEARCH_LIBS usage if the result is cached + with value 'none required' + +--- + configure.ac | 14 +- + 1 file changed, 9 insertions(+), 5 deletions(-) + +diff --git a/configure.ac b/configure.ac +index 0d3552045..c8f1f4548 100644 +--- a/configure.ac b/configure.ac +@@ -613,9 +613,10 @@ AS_IF([test "$enable_cap_ng" != "no"],[ + AC_CHECK_HEADER([cap-ng.h], [ + save_LIBS="$LIBS" + AC_SEARCH_LIBS([capng_apply], [cap-ng], [ +-enable_cap_ng=yes +-cap_ng_LIBS="$ac_cv_search_capng_apply" ++AS_IF([test "$ac_cv_search_capng_apply" != "none required"], ++ [cap_ng_LIBS="$ac_cv_search_capng_apply"], [cap_ng_LIBS=]) + AC_SUBST([cap_ng_LIBS]) ++enable_cap_ng=yes + ]) + LIBS="$save_LIBS" + ]) +@@ -631,7 +632,8 @@ AS_IF([test "$enable_cap_ng" = yes], + + save_LIBS="$LIBS" + AC_SEARCH_LIBS([pthread_create], [pthread], [ +- pthread_LIBS="$ac_cv_search_pthread_create" ++ AS_IF([test "$ac_cv_search_pthread_create" != "none required"], ++[pthread_LIBS="$ac_cv_search_pthread_create"], [pthread_LIBS=]) + AC_SUBST([pthread_LIBS]) + ],[ + AC_MSG_ERROR([pthreads not found]) +@@ -640,7 +642,8 @@ LIBS="$save_LIBS" + + save_LIBS="$LIBS" + AC_SEARCH_LIBS([dlopen], [dl], [ +- dlopen_LIBS="$ac_cv_search_dlopen" ++ AS_IF([test "$ac_cv_search_dlopen" != "none required"], ++[dlopen_LIBS="$ac_cv_search_dlopen"], [dlopen_LIBS=]) + AC_SUBST([dlopen_LIBS]) + ],[ + AC_MSG_ERROR([dlopen not found]) +@@ -649,7 +652,8 @@ LIBS="$save_LIBS" + + save_LIBS="$LIBS" + AC_SEARCH_LIBS([pow], [m], [ +- math_LIBS="$ac_cv_search_pow" ++ AS_IF([test "$ac_cv_search_pow" != "none required"], ++[math_LIBS="$ac_cv_search_pow"], [math_LIBS=]) + AC_SUBST([math_LIBS]) + ],[ + AC_MSG_ERROR([math not found]) +-- +GitLab + diff -Nru knot-3.0.5/debian/patches/series knot-3.0.5/debian/patches/series --- knot-3.0.5/debian/patches/series1970-01-01 01:00:00.0 +0100 +++ knot-3.0.5/debian/patches/series2021-10-15 15:14:17.0 +0200 @@ -0,0 +1 @@ +70dc4a5c85b65678662854c18a3475371ef4a8eb.patch
Bug#996559: minimap2 FTBFS on !x86
Source: minimap2 Version: 2.22+dfsg-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=minimap2=2.22%2Bdfsg-1 ... cc -c -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fopenmp-simd -O3 -DSIMDE_ENABLE_OPENMP -DUSE_SIMDE -DSIMDE_ENABLE_NATIVE_ALIASES -g -Wall -O2 -Wc++-compat -msse2 -Wdate-time -D_FORTIFY_SOURCE=2 -DHAVE_KALLOC ksw2_ll_sse.c -o ksw2_ll_sse.o cc: error: unrecognized command-line option ‘-msse2’ make[2]: *** [Makefile:64: ksw2_ll_sse.o] Error 1
Bug#996426: marked as done (irpas: FTBFS due to RPC removal from glibc)
Your message dated Fri, 15 Oct 2021 13:03:24 + with message-id and subject line Bug#996426: fixed in irpas 0.10-9 has caused the Debian Bug report #996426, regarding irpas: FTBFS due to RPC removal from glibc 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.) -- 996426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996426 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: irpas Version: 0.10-8 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) Hi, irpas no longer builds in sid since glibc has dropped the rpc headers. They are now provided by libtirpc-dev (and you may need -I/usr/include/tirpc to find them). >From the attached log: make[1]: Entering directory '/build/irpas-0.10' gcc -g -O2 -ffile-prefix-map=/build/irpas-0.10=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -g -Wunused -Wmissing-prototypes -I. -Wdate-time -D_FORTIFY_SOURCE=2 -c cdp.c cdp.c:14:10: fatal error: rpc/types.h: No such file or directory 14 | #include | ^ compilation terminated. make[1]: *** [Makefile:56: cdp.o] Error 1 Andreas irpas_0.10-8.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: irpas Source-Version: 0.10-9 Done: Sophie Brun We believe that the bug you reported is fixed in the latest version of irpas, 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 996...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sophie Brun (supplier of updated irpas package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 15 Oct 2021 14:47:04 +0200 Source: irpas Architecture: source Version: 0.10-9 Distribution: unstable Urgency: medium Maintainer: Debian Security Tools Changed-By: Sophie Brun Closes: 996426 Changes: irpas (0.10-9) unstable; urgency=medium . * Refresh patches * Fix build for new glibc (Closes: #996426) * Bump Standards-Version to 4.6.0 * Update my email address Checksums-Sha1: 3e7561970f600b7576925ad1d15264aa1d8006b4 1970 irpas_0.10-9.dsc 86c833d9b0f191c39f525e3b1808813c9a51682f 13496 irpas_0.10-9.debian.tar.xz cd7a8312cd812ceba0b033fa5cad6a18a0acec5a 6202 irpas_0.10-9_source.buildinfo Checksums-Sha256: a43c09f416d86e7ddff9744ff1448ae4102c1254f59962ac889a42ec51fbe4e5 1970 irpas_0.10-9.dsc c9a9f9118e31ed54897723cdc7926bfde405c9889a97166177a0ec8e209273f6 13496 irpas_0.10-9.debian.tar.xz 9bedce74caa0f1cd64881c4c05947b74182cd137238504bac8c569d304a0cd94 6202 irpas_0.10-9_source.buildinfo Files: 846de572587da6e0a0636d2031050cf4 1970 non-free/net optional irpas_0.10-9.dsc fd30373dbcac21e1e3929af8bb192dd4 13496 non-free/net optional irpas_0.10-9.debian.tar.xz 4c5ab16816f6f5fa706d99dbc75daff7 6202 non-free/net optional irpas_0.10-9_source.buildinfo -BEGIN PGP SIGNATURE- Comment: Signed by Sophie Brun iQIzBAEBCgAdFiEEOyG45orlwW+H9TItV5J4OyBv7jAFAmFpeIQACgkQV5J4OyBv 7jCPUQ//fA6JMeFSEPXH1CrRGHirjprWoMge37ybn1tPuby0z/B0wI1T/bEfWebg AFoSHvhUoXgRA/sLve8zrn6Ud8fMmR1pW+R8H05+ZMv0EfBuiU62A9m5n85p5O7H FRoNVjvj/SqJRLkIyM1SdVTNqiXQUAGDMbaRYKZKqmdbr8T+HHQfmoWnT/o5aGBk LDd0humEYduq4ZPLcT3JW+yTfssraA29Buz+Zh3J9vhC5nz5rSk6dcroGPErZy5g mV4rT97BzFEEqkcIJbNVyxn7VUoyD/p+WF+yjevg4zOF2n+qKv1WenaN92Nth0KI 4fKtrk9gdQwy7gY2R8LfMDbkdObXDZ7iZCgFbFZCOga/ATG7mRnCiH5VspdYeMqk yEY2S1Kt40KzxT1lDASCsEvPFjvzqU8abX/clo0Bz2oXFrpuzRbCrX94AnJ8MrT4 qZSX2FFj+7R5jguit6JatZh91K11jmgpNDU7673XzW4IdOPACidng/N8v2TLagsF XV9IfZ8F8vXZCZJzhyPV81JKX/9lSxQkmtrj+lSBOyafpZUfJnKPQFvcnoSJmjmz 9JHF38B7RLUiXoR0ysb3n1orYodmQ+aT8xRJbgrz6aLgxl+s783IZFq0Aewmhr/K BlR4/6uyNUIUB0lqrvGCXHI5z94gDh87N3dheozr1hdrNSldFs4= =TFfz -END PGP SIGNATURE End Message ---
Bug#996557: linux-image-5.14.0-3-686-pae-unsigned: just about every sse2 program crashes with a SIGFPE
Package: src:linux Version: 5.14.12-1 Severity: serious X-Debbugs-Cc: Jiri Palecek Dear Maintainer, when I booted my system with the latest kernel from unstable, many of the applications didn't work. That includes plasmashell (so I couldn't log in into plasma) and chromium. I ran xterm (which worked) and some of these failing programs under gdb and found they all tripped on some sse2 instructions with a SIGFPE. However, all the programs work under the kernel from linux-image-5.14.0-2-. Regards Jiri Palecek -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information ** PCI devices: 00:00.0 RAM memory [0500]: NVIDIA Corporation MCP61 Host Bridge [10de:03e2] (rev a1) Subsystem: ASUSTeK Computer Inc. M4N68T series motherboard [1043:83a4] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:01.0 ISA bridge [0601]: NVIDIA Corporation MCP61 LPC Bridge [10de:03e1] (rev a2) Subsystem: ASUSTeK Computer Inc. M4N68T series motherboard [1043:83a4] Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Kernel driver in use: nForce2_smbus Kernel modules: i2c_nforce2 00:01.2 RAM memory [0500]: NVIDIA Corporation MCP61 Memory Controller [10de:03f5] (rev a2) Subsystem: ASUSTeK Computer Inc. M4N68T series motherboard [1043:83a4] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Kernel driver in use: ohci-pci Kernel modules: ohci_pci 00:02.1 USB controller [0c03]: NVIDIA Corporation MCP61 USB 2.0 Controller [10de:03f2] (rev a3) (prog-if 20 [EHCI]) Subsystem: ASUSTeK Computer Inc. M4N68T series motherboard [1043:83a4] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: ehci-pci Kernel modules: ehci_pci 00:04.0 PCI bridge [0604]: NVIDIA Corporation MCP61 PCI bridge [10de:03f3] (rev a1) (prog-if 01 [Subtractive decode]) Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr+ DiscTmrStat- DiscTmrSERREn- Capabilities: 00:05.0 Audio device [0403]: NVIDIA Corporation MCP61 High Definition Audio [10de:03f0] (rev a2) Subsystem: ASUSTeK Computer Inc. MCP61 High Definition Audio [1043:840c] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:06.0 IDE interface [0101]: NVIDIA Corporation MCP61 IDE [10de:03ec] (rev a2) (prog-if 8a [ISA Compatibility mode controller, supports both channels switched to PCI native mode, supports bus mastering]) Subsystem: ASUSTeK Computer Inc. M4N68T series motherboard [1043:83a4] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: pata_amd Kernel modules: pata_amd, ata_generic 00:07.0 Bridge [0680]: NVIDIA Corporation MCP61 Ethernet [10de:03ef] (rev a2) Subsystem: ASUSTeK Computer Inc. M4N68T series motherboard [1043:83a4] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: forcedeth Kernel modules: forcedeth 00:08.0 IDE interface [0101]: NVIDIA Corporation MCP61 SATA Controller [10de:03f6] (rev a2) (prog-if 85 [PCI native mode-only controller, supports bus mastering]) Subsystem: ASUSTeK Computer Inc. M4N68T series motherboard [1043:83a4] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: sata_nv Kernel modules: sata_nv, ata_generic 00:08.1 IDE interface [0101]: NVIDIA Corporation MCP61 SATA Controller [10de:03f6] (rev a2) (prog-if 85 [PCI native mode-only controller, supports bus mastering]) Subsystem: ASUSTeK Computer Inc. M4N68T series motherboard [1043:83a4] Control: I/O+ Mem+
Bug#996426: marked as pending in irpas
Control: tag -1 pending Hello, Bug #996426 in irpas 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/pkg-security-team/irpas/-/commit/ecf8ee1507fccde282fadaa029b260f1b675844c Fix build because glibc dropped the rpc headers (Closes: #996426) Add build-dep libtirpc-dev Add CFLAGS -I/usr/include/tirpc (this message was generated automatically) -- Greetings https://bugs.debian.org/996426
Processed: Bug#996426 marked as pending in irpas
Processing control commands: > tag -1 pending Bug #996426 [src:irpas] irpas: FTBFS due to RPC removal from glibc Added tag(s) pending. -- 996426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996426 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984104: marked as done (libfastahack: ftbfs with GCC-11)
Your message dated Fri, 15 Oct 2021 12:48:46 + with message-id and subject line Bug#984104: fixed in libfastahack 1.0.0+dfsg-9 has caused the Debian Bug report #984104, regarding libfastahack: ftbfs with GCC-11 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.) -- 984104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984104 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libfastahack Version: 1.0.0+dfsg-7 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/libfastahack_1.0.0+dfsg-7_unstable_gcc11.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. [...] mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libfastahack.so.0 debian/libfastahack0/usr/lib/x86_64-linux-gnu mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libfastahack.so.0.0.0 debian/libfastahack0/usr/lib/x86_64-linux-gnu PKGDEV=libfastahack-dev PKGSHL=libfastahack0 install -d -m 755 debian/libfastahack-dev/usr/include mv debian/tmp/usr/include/fastahack debian/libfastahack-dev/usr/include install -d -m 755 debian/libfastahack-dev/usr/lib/x86_64-linux-gnu/pkgconfig mv debian/tmp/usr/lib/*/pkgconfig/*.pc debian/libfastahack-dev/usr/lib/x86_64-linux-gnu/pkgconfig find debian -name libfastahack.la -delete make[1]: Leaving directory '/<>' dh_installdocs dh_installchangelogs debian/rules override_dh_installman make[1]: Entering directory '/<>' help2man --no-discard-stderr --no-info --version-string=1.0.0+dfsg-7 \ --name="fastahack - indexing and extracting sequences and subsequences from FASTA files" \ ./fastahack > debian/fastahack.1 dh_installman make[1]: Leaving directory '/<>' dh_perl dh_link dh_strip_nondeterminism dh_compress dh_fixperms dh_missing dh_dwz -a dh_strip -a debian/rules override_dh_makeshlibs make[1]: Entering directory '/<>' echo "On architecture amd64 symbols file is provided" On architecture amd64 symbols file is provided dh_makeshlibs dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libfastahack0/DEBIAN/symbols doesn't match completely debian/libfastahack0.symbols --- debian/libfastahack0.symbols (libfastahack0_1.0.0+dfsg-7_amd64) +++ dpkg-gensymbolsKCtwDB 2021-03-01 21:09:58.987468905 + @@ -32,9 +32,9 @@ _ZN15FastaIndexEntryD1Ev@Base 0.0+git20160702.bbc645f _ZN15FastaIndexEntryD2Ev@Base 0.0+git20160702.bbc645f _ZNKSt5ctypeIcE8do_widenEc@Base 0.0+git20160702.bbc645f - (optional)_ZNSt12_Destroy_auxILb0EE9__destroyIPNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEvT_S9_@Base 1.0.0+dfsg - (optional)_ZNSt4pairINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE15FastaIndexEntryED1Ev@Base 1.0.0+dfsg - (optional)_ZNSt4pairINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE15FastaIndexEntryED2Ev@Base 1.0.0+dfsg +#MISSING: 1.0.0+dfsg-7# (optional)_ZNSt12_Destroy_auxILb0EE9__destroyIPNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEvT_S9_@Base 1.0.0+dfsg +#MISSING: 1.0.0+dfsg-7# (optional)_ZNSt4pairINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE15FastaIndexEntryED1Ev@Base 1.0.0+dfsg +#MISSING: 1.0.0+dfsg-7#
Processed: Re: lasi: ftbfs with GCC-11
Processing control commands: > tags -1 patch Bug #984083 [src:lasi] lasi: ftbfs with GCC-11 Added tag(s) patch. -- 984083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984083 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984083: lasi: ftbfs with GCC-11
Package: lasi
Version: 1.1.0-2
Followup-For: Bug #984083
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu ubuntu-patch
X-Debbugs-Cc: sl...@ubuntu.com
Control: tags -1 patch
Dear Maintainer,
lasi fails to build from source with GCC-11.
Fix FTFBFS with C++17/GCC-11, by avoiding dynamic exception specification.
GCC 11 defaults to C++17 which does not allow dynamic exception specifications
anymore. Replace "throw(std::runtime_error)" with "noexcept(false)" as described
in https://gcc.gnu.org/gcc-11/porting_to.html
In Ubuntu, the attached patch was applied to achieve the following:
* Fix FTBFS with C++17/GCC-11 (Closes: #984083)
+ debian/patches/fix-gcc11-throw-ftbfs.patch
Thanks for considering the patch.
Cheers,
Lukas
-- System Information:
Debian Release: 11.0
APT prefers impish
APT policy: (500, 'impish')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.13.0-16-generic (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE:en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru lasi-1.1.0/debian/patches/fix-gcc11-throw-ftbfs.patch
lasi-1.1.0/debian/patches/fix-gcc11-throw-ftbfs.patch
--- lasi-1.1.0/debian/patches/fix-gcc11-throw-ftbfs.patch 1970-01-01
01:00:00.0 +0100
+++ lasi-1.1.0/debian/patches/fix-gcc11-throw-ftbfs.patch 2021-10-15
14:20:05.0 +0200
@@ -0,0 +1,22 @@
+Description: Avoid dynamic exception spec, to fix build with C++17 (GCC-11)
+ GCC 11 defaults to C++17 which does not allow dynamic exception
+ specifications anymore. Replace "throw(std::runtime_error)" with
+ "noexcept(false)" as described in https://gcc.gnu.org/gcc-11/porting_to.html
+Author: Lukas Märdian
+Origin: vendor, Ubuntu
+Bug-Debian: https://bugs.debian.org/984083
+Forwarded: no
+Last-Update: 2021-10-15
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- lasi-1.1.0.orig/src/util.h
lasi-1.1.0/src/util.h
+@@ -27,7 +27,7 @@ std::ostream& operator<<(std::ostream&,
+
+ /** Converts a freetype return code into an exception.
+ */
+-inline void evalReturnCode(const int errCode, const char* funcName) throw
(std::runtime_error) {
++inline void evalReturnCode(const int errCode, const char* funcName)
noexcept(false) {
+ if (errCode)
+ throw std::runtime_error(std::string("Error returned from ") + funcName);
+ }
diff -Nru lasi-1.1.0/debian/patches/series lasi-1.1.0/debian/patches/series
--- lasi-1.1.0/debian/patches/series2014-06-19 13:47:21.0 +0200
+++ lasi-1.1.0/debian/patches/series2021-10-15 14:12:42.0 +0200
@@ -1 +1,2 @@
fix-freetype-ftbfs
+fix-gcc11-throw-ftbfs.patch
Processed: Bug#984104 marked as pending in libfastahack
Processing control commands: > tag -1 pending Bug #984104 [src:libfastahack] libfastahack: ftbfs with GCC-11 Added tag(s) pending. -- 984104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984104 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984104: marked as pending in libfastahack
Control: tag -1 pending Hello, Bug #984104 in libfastahack 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/med-team/libfastahack/-/commit/751d23647b23c5c566c361f6d9f3ee3597cf7a56 Mark another symbol as optional for GCC 11. Closes: #984104 (this message was generated automatically) -- Greetings https://bugs.debian.org/984104
Bug#996219: marked as done (ruby-enumerable-statistics: FTBFS with ruby3.0: statistics.c:67:32: error: ‘RComplex’ undeclared (first use in this function))
Your message dated Fri, 15 Oct 2021 12:04:50 + with message-id and subject line Bug#996219: fixed in ruby-enumerable-statistics 2.0.7+dfsg-1 has caused the Debian Bug report #996219, regarding ruby-enumerable-statistics: FTBFS with ruby3.0: statistics.c:67:32: error: ‘RComplex’ undeclared (first use in this function) 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.) -- 996219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996219 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-enumerable-statistics Version: 2.0.1+dfsg-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-enumerable-statistics was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > gcc -fdebug-prefix-map=/<>=. -I. > -I/usr/include/x86_64-linux-gnu/ruby-3.0.0 > -I/usr/include/ruby-3.0.0/ruby/backward -I/usr/include/ruby-3.0.0 -I. > -DHAVE_RB_RATIONAL_NEW -DHAVE_RB_RATIONAL_NUM -DHAVE_RB_RATIONAL_DEN > -DHAVE_RB_COMPLEX_RAW -DHAVE_RB_COMPLEX_REAL -DHAVE_RB_COMPLEX_IMAG > -DHAVE_RB_COMPLEX_PLUS -DHAVE_RB_COMPLEX_DIV -DHAVE_RB_DBL_COMPLEX_NEW > -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -g -O2 > -ffile-prefix-map=/build/ruby3.0-2KsnwC/ruby3.0-3.0.2=. > -fstack-protector-strong -Wformat -Werror=format-security -fPIC -o > statistics.o -c statistics.c > statistics.c: In function ‘complex_add’: > statistics.c:67:25: warning: implicit declaration of function ‘R_CAST’ > [-Wimplicit-function-declaration] >67 | # define RCOMPLEX(obj) (R_CAST(RComplex)(obj)) > | ^~ > statistics.c:152:18: note: in expansion of macro ‘RCOMPLEX’ > 152 | real = f_add(RCOMPLEX(self)->real, RCOMPLEX(other)->real); > | ^~~~ > statistics.c:67:32: error: ‘RComplex’ undeclared (first use in this function) >67 | # define RCOMPLEX(obj) (R_CAST(RComplex)(obj)) > |^~~~ > statistics.c:152:18: note: in expansion of macro ‘RCOMPLEX’ > 152 | real = f_add(RCOMPLEX(self)->real, RCOMPLEX(other)->real); > | ^~~~ > statistics.c:67:32: note: each undeclared identifier is reported only once > for each function it appears in >67 | # define RCOMPLEX(obj) (R_CAST(RComplex)(obj)) > |^~~~ > statistics.c:152:18: note: in expansion of macro ‘RCOMPLEX’ > 152 | real = f_add(RCOMPLEX(self)->real, RCOMPLEX(other)->real); > | ^~~~ > statistics.c: In function ‘f_zero_p’: > statistics.c:47:33: error: ‘RRational’ undeclared (first use in this function) >47 | # define RRATIONAL(obj) (R_CAST(RRational)(obj)) > | ^ > statistics.c:400:17: note: in expansion of macro ‘RRATIONAL’ > 400 | VALUE num = RRATIONAL(x)->num; > | ^ > statistics.c: In function ‘rb_rational_plus’: > statistics.c:47:33: error: ‘RRational’ undeclared (first use in this function) >47 | # define RRATIONAL(obj) (R_CAST(RRational)(obj)) > | ^ > statistics.c:613:17: note: in expansion of macro ‘RRATIONAL’ > 613 | VALUE num = RRATIONAL(self)->num; > | ^ > statistics.c: In function ‘calculate_and_set_mean’: > statistics.c:67:32: error: ‘RComplex’ undeclared (first use in this function) >67 | # define RCOMPLEX(obj) (R_CAST(RComplex)(obj)) > |^~~~ > statistics.c:751:24: note: in expansion of macro ‘RCOMPLEX’ > 751 | VALUE const real = RCOMPLEX(sum)->real; > |^~~~ > make[1]: *** [Makefile:245: statistics.o] Error 1 The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-enumerable-statistics/ruby-enumerable-statistics_2.0.1+dfsg-3+rebuild1633378917_amd64.build.txt signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: ruby-enumerable-statistics Source-Version: 2.0.7+dfsg-1 Done: Antonio Terceiro We believe that the bug you reported is fixed in the latest version of ruby-enumerable-statistics, 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
Bug#984348: marked as done (spoa: ftbfs with GCC-11)
Your message dated Fri, 15 Oct 2021 12:05:26 + with message-id and subject line Bug#984348: fixed in spoa 4.0.7+ds-2 has caused the Debian Bug report #984348, regarding spoa: ftbfs with GCC-11 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.) -- 984348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984348 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:spoa Version: 4.0.7+ds-1 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/spoa_4.0.7+ds-1_unstable_gcc11.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. [...] dh_makeshlibs -a -O--no-parallel dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libspoa7.0.0/DEBIAN/symbols doesn't match completely debian/libspoa7.0.0.symbols.amd64 --- debian/libspoa7.0.0.symbols.amd64 (libspoa7.0.0_4.0.7+ds-1_amd64) +++ dpkg-gensymbolsasbohv 2021-03-01 21:04:41.854431493 + @@ -1,5 +1,33 @@ libspoa.so.7.0.0 libspoa7.0.0 #MINVER# * Build-Depends-Package: libspoa-dev + CpuFeatures_CloseFile@Base 4.0.7+ds-1 + CpuFeatures_OpenFile@Base 4.0.7+ds-1 + CpuFeatures_ReadFile@Base 4.0.7+ds-1 + CpuFeatures_StringView_Back@Base 4.0.7+ds-1 + CpuFeatures_StringView_CopyString@Base 4.0.7+ds-1 + CpuFeatures_StringView_Front@Base 4.0.7+ds-1 + CpuFeatures_StringView_GetAttributeKeyValue@Base 4.0.7+ds-1 + CpuFeatures_StringView_HasWord@Base 4.0.7+ds-1 + CpuFeatures_StringView_IndexOf@Base 4.0.7+ds-1 + CpuFeatures_StringView_IndexOfChar@Base 4.0.7+ds-1 + CpuFeatures_StringView_IsEquals@Base 4.0.7+ds-1 + CpuFeatures_StringView_KeepFront@Base 4.0.7+ds-1 + CpuFeatures_StringView_ParsePositiveNumber@Base 4.0.7+ds-1 + CpuFeatures_StringView_PopBack@Base 4.0.7+ds-1 + CpuFeatures_StringView_PopFront@Base 4.0.7+ds-1 + CpuFeatures_StringView_StartsWith@Base 4.0.7+ds-1 + CpuFeatures_StringView_TrimWhitespace@Base 4.0.7+ds-1 + FillX86BrandString@Base 4.0.7+ds-1 + GetCpuidLeaf@Base 4.0.7+ds-1 + GetX86CacheInfo@Base 4.0.7+ds-1 + GetX86FeaturesEnumName@Base 4.0.7+ds-1 + GetX86FeaturesEnumValue@Base 4.0.7+ds-1 + GetX86Info@Base 4.0.7+ds-1 + GetX86Microarchitecture@Base 4.0.7+ds-1 + GetX86MicroarchitectureName@Base 4.0.7+ds-1 + GetXCR0Eax@Base 4.0.7+ds-1 + StackLineReader_Initialize@Base 4.0.7+ds-1 + StackLineReader_NextLine@Base 4.0.7+ds-1 _ZGVN6cereal6detail12StaticObjectINS0_18PolymorphicCastersEE8instanceE@Base 4.0.5+ds _ZGVZN6cereal6detail12StaticObjectINS0_18PolymorphicCastersEE6createEvE1t@Base 4.0.5+ds _ZN4spoa15AlignmentEngine5AlignERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERKNS_5GraphEPi@Base 4.0.5+ds @@ -104,7 +132,7 @@ _ZNK4spoa5Graph8SubgraphEjjPSt6vectorIPKNS0_4NodeESaIS4_EE@Base 4.0.5+ds _ZNKSt5ctypeIcE8do_widenEc@Base 1.1.5
Bug#993324: libgsl25: ABI breakage: removed symbol gsl_linalg_QR_TR_decomp
Hi Dirk > Yes. And I follow upstream. They didn't change :-/ Right, so please speak to your upstream. Dropping (or renaming) a symbol is changing the ABI in a backward-incompatible way, and they need to bump the SONAME (or revert the change). This is not something Debian-specific, this is how shared objects in Unix work [1][2]. Regards Graham [1] https://en.wikipedia.org/wiki/Soname [2] https://www.gnu.org/software/libtool/manual/html_node/Updating-version-info.html
Processed: tagging 996541
Processing commands for cont...@bugs.debian.org: > tags 996541 + ftbfs Bug #996541 [racon] racon: FTBFS when rebuilt against libedlib1 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 996541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996541 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 996480
Processing commands for cont...@bugs.debian.org: > tags 996480 + ftbfs Bug #996480 [src:dvbstreamer] dvbstreamer: FTBFS with autoconf 2.71 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 996480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996480 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996553: ptl: autopkgtest failure on armhf
Source: ptl Version: 2.0.0-1 Severity: serious https://ci.debian.net/data/autopkgtest/testing/armhf/p/ptl/15952694/log.gz ... In file included from /usr/include/c++/10/map:61, from /usr/include/PTL/Utility.hh:30, from /usr/include/PTL/Globals.hh:36, from /usr/include/PTL/Threading.hh:28, from /usr/include/PTL/AutoLock.hh:246, from /usr/include/PTL/PTL.hh:22, from /tmp/autopkgtest-lxc.75pc7umd/downtmp/autopkgtest_tmp/minimal/minimal.cc:22: /usr/include/c++/10/bits/stl_map.h: In member function ‘std::map<_Key, _Tp, _Compare, _Alloc>::mapped_type& std::map<_Key, _Tp, _Compare, _Alloc>::operator[](const key_type&) [with _Key = std::thread::id; _Tp = long long unsigned int; _Compare = std::less; _Alloc = std::allocator >]’: /usr/include/c++/10/bits/stl_map.h:501:37: note: parameter passing for argument of type ‘std::_Rb_tree, std::_Select1st >, std::less, std::allocator > >::const_iterator’ changed in GCC 7.1 ... autopkgtest [09:22:50]: summary examples.sh FAIL stderr: In file included from /usr/include/c++/10/map:61,
Bug#995649: marked as done (therion: autopkgtest regression on at least arm64 and i386)
Your message dated Fri, 15 Oct 2021 11:06:28 +0100
with message-id <20211015100628.gw29...@mail.wookware.org>
and subject line Re: Bug#995649: therion: autopkgtest regression on at least
arm64 and i386
has caused the Debian Bug report #995649,
regarding therion: autopkgtest regression on at least arm64 and i386
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.)
--
995649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995649
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: therion
Version: 6.0.2ds1-4
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Control: affects -1 src:texlive-base src:texlive-lang
Dear maintainer(s),
With a recent upload of therion the autopkgtest of therion fails in
testing on at least arm64 and i386 when that autopkgtest is run with the
binary packages of therion from unstable. It passes when run with only
packages from testing. In tabular form:
passfail
therionfrom testing6.0.2ds1-4
versioned deps [0] from testingfrom unstable
all others from testingfrom testing
I copied some of the output at the bottom of this report.
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
[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
therion/6.0.2ds1-4. I.e. due to versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=therion
https://ci.debian.net/data/autopkgtest/testing/arm64/t/therion/15744313/log.gz
writing samples/survex/cave1.pdf ...
This is MetaPost, version 2.01 (TeX Live 2022/dev/Debian) (kpathsea
version 6.3.4/dev)
(/usr/share/texlive/texmf-dist/metapost/base/mpost.mp
(/usr/share/texlive/texmf-dist/metapost/base/plain.mp
Preloading the plain mem file, version 1.005) ) (./data.mp [1] [2] [3] [4]
[5] [6] [7] [8] [9] [10] [11] [12] [13] [14]
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17]
(./mptextmp.mp) [18] (./mptextmp.mp) (./mptextmp.mp) (./mptextmp.mp)
(./mptextmp.mp) (./mptextmp.mp) (./mptextmp.mp) [19] )
33 output files written: data-patt.1 .. data.19
Transcript written on data.log.
converting scraps ... done
making map ... done
This is pdfTeX, Version 3.141592653-2.6-1.40.22 (TeX Live
2022/dev/Debian) (preloaded format=pdftex)
restricted \write18 enabled.
entering extended mode
(./data.tex (./th_enc.tex) (./th_texts.tex) (./th_resources.tex
(/usr/share/texlive/texmf-dist/tex/generic/pdftex/glyphtounicode.tex))
(./th_fontdef.tex{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}<><><><>)
(./th_formdef.tex) (./th_pagedef.tex) (./th_pages.tex) [1]
)
Output written on data.pdf (1 page, 34360 bytes).
Transcript written on data.log.
done
checking CRC32 of all output files ...
samples/survex/cave1.pdf ... CRC32 error: was e974864e, expected a344ba1f
done.
therion: error -- CRC32 checks not passed.
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
On 2021-10-03 18:54 +0200, Paul Gevers wrote:
> With a recent upload of therion the autopkgtest of therion fails in
> testing on at least arm64 and i386 when that autopkgtest is run with the
> binary packages of therion from unstable.
> Currently this regression is blocking the migration to testing [1]. Can
> you please investigate the situation and fix it?
This is fixed in 6.0.3. Well, it's not actually fixed so much as worked around
for now.
The issue is that we are now doing crc checks on the output from a
wider range of tests and it turns out that some outputs vary between
architectures.
The underlying problem of generating .lox files that varied between
architectures was fixed in 6.0.2ds1-4 (which helps make therion build
reproducibly); but that let it get to a different test to discover that
the generated PDF files vary. That is probably down to external
tools. Whilst we are investigating 6.0.3 has been uploaded with the
crc check aspect turned off so that texlive can migrate.
We'll turn it back on once we either have per-arch crcs or have made
all the tools behave the same.
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
signature.asc
Bug#984206: marked as done (libquazip: ftbfs with GCC-11)
Your message dated Fri, 15 Oct 2021 09:03:45 + with message-id and subject line Bug#984206: fixed in libquazip 0.9.1-2 has caused the Debian Bug report #984206, regarding libquazip: ftbfs with GCC-11 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.) -- 984206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984206 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libquazip Version: 0.9.1-1 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/libquazip_0.9.1-1_unstable_gcc11.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. [...] gzip -9nf usr/share/doc/libquazip5-1/changelog usr/share/doc/libquazip5-1/changelog.Debian usr/share/man/man1/libquazip5-1.1 chmod a-x usr/share/doc/libquazip-doc/changelog usr/share/doc/libquazip-doc/changelog.Debian gzip -9nf usr/share/doc/libquazip5-dev/changelog usr/share/doc/libquazip5-dev/changelog.Debian gzip -9nf usr/share/doc/libquazip-doc/changelog usr/share/doc/libquazip-doc/changelog.Debian cd '/<>' cd '/<>' cd '/<>' rm -f debian/libquazip5-1/usr/share/doc/libquazip5-1/NEWS debian/libquazip5-1/usr/share/doc/libquazip5-1/NEWS.gz ln -s changelog.gz debian/libquazip5-1/usr/share/doc/libquazip5-1/NEWS.gz rm -f debian/libquazip5-dev/usr/share/doc/libquazip5-dev/NEWS debian/libquazip5-dev/usr/share/doc/libquazip5-dev/NEWS.gz ln -s changelog.gz debian/libquazip5-dev/usr/share/doc/libquazip5-dev/NEWS.gz rm -f debian/libquazip-doc/usr/share/doc/libquazip-doc/NEWS debian/libquazip-doc/usr/share/doc/libquazip-doc/NEWS.gz ln -s changelog.gz debian/libquazip-doc/usr/share/doc/libquazip-doc/NEWS.gz dh_fixperms -O-buildsystemqmake find debian/libquazip5-1 ! -type l -a -true -a -true -print0 2>/dev/null | xargs -0r chmod go=rX,u+rw,a-s find debian/libquazip5-dev ! -type l -a -true -a -true -print0 2>/dev/null | xargs -0r chmod go=rX,u+rw,a-s find debian/libquazip-doc ! -type l -a -true -a -true -print0 2>/dev/null | xargs -0r chmod go=rX,u+rw,a-s find debian/libquazip5-1/usr/share/doc -type f -a -true -a ! -regex 'debian/libquazip5-1/usr/share/doc/[^/]*/examples/.*' -print0 2>/dev/null | xargs -0r chmod 0644 find debian/libquazip-doc/usr/share/doc -type f -a -true -a ! -regex 'debian/libquazip-doc/usr/share/doc/[^/]*/examples/.*' -print0 2>/dev/null | xargs -0r chmod 0644 find debian/libquazip5-dev/usr/share/doc -type f -a -true -a ! -regex 'debian/libquazip5-dev/usr/share/doc/[^/]*/examples/.*' -print0 2>/dev/null | xargs -0r chmod 0644 find debian/libquazip5-1/usr/share/doc -type d -a -true -a -true -print0 2>/dev/null | xargs -0r chmod 0755 find debian/libquazip5-dev/usr/share/doc -type d -a -true -a -true -print0 2>/dev/null | xargs -0r chmod 0755 find debian/libquazip-doc/usr/share/doc -type d -a -true -a -true -print0 2>/dev/null | xargs -0r chmod 0755 find debian/libquazip5-1/usr/share/man -type f -a -true -a -true -print0 2>/dev/null | xargs -0r chmod 0644 find debian/libquazip5-dev/usr/include -type f -a -true -a -true -print0
Processed: Re: node-mermaid: ships a copy of /usr/share/nodejs/crypto-random-string/*, already in node-crypto-random-string
Processing control commands: > severity -1 important Bug #996427 [node-mermaid] node-mermaid: ships a copy of /usr/share/nodejs/crypto-random-string/*, already in node-crypto-random-string Severity set to 'important' from 'serious' -- 996427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996427 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996427: node-mermaid: ships a copy of /usr/share/nodejs/crypto-random-string/*, already in node-crypto-random-string
Control: severity -1 important On Wed, 13 Oct 2021 23:36:03 +0200 Andreas Beckmann wrote: > during a test with piuparts I noticed your package fails to upgrade from > 'stable'. > It installed fine in 'stable', then the upgrade to 'sid' fails > because it tries to overwrite other packages files without declaring a > Breaks+Replaces relation. > > See policy 7.6 at > https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces I’ve added Conflicts, so the severity can be lowered. -- Cheers, Andrej
Bug#996427: [Pkg-javascript-devel] Bug#996427: node-mermaid: ships a copy of /usr/share/nodejs/crypto-random-string/*, already in node-crypto-random-string
On 10/14/21 3:06 AM, Andreas Beckmann wrote: Package: node-mermaid [...] Hi, I think it'd be sensible to unvendor crypto-random-string here. However, after trying to un-vendor -- patch attached with email, The checksum reduces as expected to 26.13.21 -- which is less than the one in the archive $ dpkg --compare-versions 8.13.2+ds+~cs26.13.21 lt 8.13.2+ds+~cs30.13.21 && echo true true So, what should be done then? @Yadd, team, ideas? Nilesh diff --git a/debian/control b/debian/control index 54e6dd3..a8116d7 100644 --- a/debian/control +++ b/debian/control @@ -19,6 +19,7 @@ Build-Depends: , rollup , uglifyjs.terser , webpack (>= 4.43.0~) + , node-crypto-random-string Standards-Version: 4.6.0 Vcs-Browser: https://salsa.debian.org/js-team/node-mermaid Vcs-Git: https://salsa.debian.org/js-team/node-mermaid.git diff --git a/debian/gbp.conf b/debian/gbp.conf index 4e777c0..e686aad 100644 --- a/debian/gbp.conf +++ b/debian/gbp.conf @@ -1,4 +1,4 @@ [DEFAULT] pristine-tar=True filter=[ '.gitignore', '.travis.yml', '.git*' ] -component=['sanitize-url', 'webpack-node-externals', 'scope-css', 'crypto-random-string', 'slugify', 'escaper', 'strip-css-comments', 'is-regexp', 'khroma', 'stylis', 'entity-decode'] +component=['sanitize-url', 'webpack-node-externals', 'scope-css', 'slugify', 'escaper', 'strip-css-comments', 'is-regexp', 'khroma', 'stylis', 'entity-decode'] diff --git a/debian/watch b/debian/watch index ed13b14..50f26a3 100644 --- a/debian/watch +++ b/debian/watch @@ -23,12 +23,6 @@ opts="searchmode=plain,component=webpack-node-externals,pgpmode=none" \ opts="searchmode=plain,component=scope-css,pgpmode=none" \ https://registry.npmjs.org/scope-css https://registry.npmjs.org/scope-css/-/scope-css-([\d\.]+)@ARCHIVE_EXT@ checksum -opts=\ -component=crypto-random-string,\ -dversionmangle=auto,\ -filenamemangle=s/.*\/v?([\d\.-]+)\.tar\.gz/node-crypto-random-string-$1.tar.gz/ \ - https://github.com/sindresorhus/crypto-random-string/tags .*/archive/.*/v?([\d\.]+).tar.gz checksum - opts=\ component=slugify,\ dversionmangle=auto,\ OpenPGP_signature Description: OpenPGP digital signature
Processed: pytest breaks pytest-doctestplus autopkgtest: pytest.PytestAssertRewriteWarning: Module already imported so cannot be rewritten: pytest_doctestplus
Processing control commands:
> notfound -1 pytest/6.2.5-1
Bug #995737 {Done: Stefano Rivera } [src:pytest,
src:pytest-doctestplus] pytest breaks pytest-doctestplus autopkgtest:
pytest.PytestAssertRewriteWarning: Module already imported so cannot be
rewritten: pytest_doctestplus
No longer marked as found in versions pytest/6.2.5-1.
--
995737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995737
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#995737: pytest breaks pytest-doctestplus autopkgtest: pytest.PytestAssertRewriteWarning: Module already imported so cannot be rewritten: pytest_doctestplus
Control: notfound -1 pytest/6.2.5-1
Bug#996478: marked as done (checkinstall: FTBFS with glibc 2.33+)
Your message dated Fri, 15 Oct 2021 07:33:27 + with message-id and subject line Bug#996478: fixed in checkinstall 1.6.2+git20170426.d24a630-3 has caused the Debian Bug report #996478, regarding checkinstall: FTBFS with glibc 2.33+ 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.) -- 996478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996478 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: checkinstall Version: 1.6.2+git20170426.d24a630-2 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu ubuntu-patch X-Debbugs-Cc: sl...@ubuntu.com Dear Maintainer, checkinstall fails to build from source with the following error if compiled with glibc 2.33+: gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>/checkinstall-1.6.2+git20170426.d24a630=. -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -Wl,-Bsymbolic-functions -flto=auto -Wl,-z,relro -Wall -c -g -D_GNU_SOURCE -DPIC -fPIC -D_REENTRANT -DVERSION=\"0.7.0beta7\" installwatch.c installwatch.c: In function ‘true_stat’: installwatch.c:162:27: error: ‘_STAT_VER’ undeclared (first use in this function) 162 | return true_xstat(_STAT_VER,pathname,info); | ^ installwatch.c:162:27: note: each undeclared identifier is reported only once for each function it appears in installwatch.c: In function ‘true_mknod’: installwatch.c:166:28: error: ‘_MKNOD_VER’ undeclared (first use in this function) 166 | return true_xmknod(_MKNOD_VER,pathname,mode,); |^~ installwatch.c: In function ‘true_lstat’: installwatch.c:170:28: error: ‘_STAT_VER’ undeclared (first use in this function) 170 | return true_lxstat(_STAT_VER,pathname,info); |^ installwatch.c: In function ‘true_fstatat’: installwatch.c:174:30: error: ‘_STAT_VER’ undeclared (first use in this function) 174 | return true_fxstatat(_STAT_VER, dirfd, pathname, info, flags); | ^ installwatch.c: In function ‘true_fstatat64’: installwatch.c:178:32: error: ‘_STAT_VER’ undeclared (first use in this function) 178 | return true_fxstatat64(_STAT_VER, dirfd, pathname, info, flags); |^ installwatch.c: In function ‘true_mknodat’: installwatch.c:182:30: error: ‘_MKNOD_VER’ undeclared (first use in this function) 182 | return true_xmknodat(_MKNOD_VER, dirfd, pathname, mode, ); | ^~ installwatch.c: In function ‘instw_init’: installwatch.c:1211:17: warning: ignoring return value of ‘realpath’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 1211 | realpath(proot,wrkpath); | ^~~ installwatch.c:1330:17: warning: ignoring return value of ‘realpath’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 1330 | realpath(__instw.root,wrkpath); | ^~ installwatch.c:1348:25: warning: ignoring return value of ‘realpath’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 1348 | realpath(pexclude,wrkpath); | ^~ installwatch.c: In function ‘true_stat’: installwatch.c:163:1: warning: control reaches end of non-void function [-Wreturn-type] 163 | } | ^ installwatch.c: In function ‘copy_path’: installwatch.c:757:33: warning: ignoring return value of ‘write’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 757 | write(translfd,buffer,bytes); | ^~~~ installwatch.c: In function ‘true_lstat’: installwatch.c:171:1: warning: control reaches end of non-void function [-Wreturn-type] 171 | } | ^ installwatch.c: In function ‘true_mknod’: installwatch.c:167:1: warning: control reaches end of non-void function [-Wreturn-type] 167 | } | ^ make[3]: *** [Makefile:22: installwatch.o] Error 1 make[3]: Leaving directory '/<>/checkinstall-1.6.2+git20170426.d24a630/installwatch' make[2]: *** [Makefile:12: all] Error 2 make[2]: Leaving directory '/<>/checkinstall-1.6.2+git20170426.d24a630' dh_auto_build: error: make -j4 "INSTALL=install --strip-program=true" returned exit code 2
Bug#996500: wlroots FTBFS: error: ‘av_init_packet’ is deprecated [-Werror=deprecated-declarations]
Hi, This is fixed in experimental which should go to unstable soon. Otherwise I'll backport upstream commit 6230f7be4f92b83df7ea8e6487410b3b81dd4b1d Cheers, -- Guido On Thu, Oct 14, 2021 at 07:54:13PM +0200, Helmut Grohne wrote: > Source: wlroots > Version: 0.12.0-2 > Severity: serious > Tags: ftbfs > > wlroots fails to build from source in unstable on amd64. A non-parallel > build now ends as follows: > > | FAILED: examples/dmabuf-capture.p/dmabuf-capture.c.o > | cc -Iexamples/dmabuf-capture.p -Iexamples -I../examples -Iprotocol > -I/usr/include/x86_64-linux-gnu -I/usr/include/libdrm > -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra > -Werror -std=c11 -DWLR_USE_UNSTABLE -Wundef -Wlogical-op > -Wmissing-include-dirs -Wold-style-definition -Wpointer-arith -Winit-self > -Wstrict-prototypes -Wimplicit-fallthrough=2 -Wendif-labels > -Wstrict-aliasing=2 -Woverflow -Wmissing-prototypes -Wno-missing-braces > -Wno-missing-field-initializers -Wno-unused-parameter -fmacro-prefix-map=../= > -DLIBINPUT_MAJOR=1 -DLIBINPUT_MINOR=19 -DLIBINPUT_PATCH=1 > '-DICONDIR="/usr/share/icons"' -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -pthread -MD -MQ > examples/dmabuf-capture.p/dmabuf-capture.c.o -MF > examples/dmabuf-capture.p/dmabuf-capture.c.o.d -o > examples/dmabuf-capture.p/dmabuf-capture.c.o -c ../examples/dmabuf-capture.c > | ../examples/dmabuf-capture.c: In function ‘vid_encode_thread’: > | ../examples/dmabuf-capture.c:494:25: error: ‘av_init_packet’ is deprecated > [-Werror=deprecated-declarations] > | 494 | av_init_packet(); > | | ^~ > | In file included from /usr/include/x86_64-linux-gnu/libavcodec/bsf.h:30, > | from /usr/include/x86_64-linux-gnu/libavcodec/avcodec.h:44, > | from > /usr/include/x86_64-linux-gnu/libavformat/avformat.h:312, > | from ../examples/dmabuf-capture.c:2: > | /usr/include/x86_64-linux-gnu/libavcodec/packet.h:488:6: note: declared here > | 488 | void av_init_packet(AVPacket *pkt); > | | ^~ > | cc1: all warnings being treated as errors > | ninja: build stopped: subcommand failed. > | dh_auto_build: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j1 > -v returned exit code 1 > | make: *** [debian/rules:7: binary] Error 25 > | dpkg-buildpackage: error: debian/rules binary subprocess returned exit > status 2 > > Helmut >
Bug#972888: marked as done (libclutter-perl: Deprecated upstream)
Your message dated Fri, 15 Oct 2021 07:15:01 + with message-id and subject line Bug#996441: Removed package(s) from unstable has caused the Debian Bug report #972888, regarding libclutter-perl: Deprecated upstream 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.) -- 972888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972888 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libclutter-perl Severity: serious User: debian-p...@lists.debian.org Usertags: rm-candidate Hi, upstream announced¹ that the Clutter Perl module would be deprecated in December 2020. It is actually already archived on their GitLab, so: - The module will no longer be updated with security patches, bug fixes, or when changes are made in the Perl ABI. - It will no longer be possible to submit new issues or pull requests for these modules, or push new changes to their Git repos. Therefore, I don't think we should ship this package in Bullseye. Any objection to removing the package from testing & sid? This is a leaf package and popcon is 0/9 (vote/inst). [1] https://mail.gnome.org/archives/gtk-perl-list/2020-October/msg2.html --- End Message --- --- Begin Message --- Version: 1.110-6+rm Dear submitter, as the package libclutter-perl has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/996441 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---
Bug#984236: marked as done (minbif: ftbfs with GCC-11)
Your message dated Fri, 15 Oct 2021 07:13:17 +
with message-id
and subject line Bug#996096: Removed package(s) from unstable
has caused the Debian Bug report #984236,
regarding minbif: ftbfs with GCC-11
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.)
--
984236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984236
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:minbif
Version: 1:1.0.5+git20150505-3
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11
[This bug is not targeted to the upcoming bullseye 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.
The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/minbif_1.0.5+git20150505-3_unstable_gcc11.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.
[...]
CMAKE_LD_FLAGS
-- Build files have been written to: /<>/builddir
dh_testdir
/usr/bin/make -C builddir
make[1]: Entering directory '/<>/builddir'
/usr/bin/cmake -S/<> -B/<>/builddir
--check-build-system CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start /<>/builddir/CMakeFiles
/<>/builddir//CMakeFiles/progress.marks
/usr/bin/make -f CMakeFiles/Makefile2 all
make[2]: Entering directory '/<>/builddir'
/usr/bin/make -f src/CMakeFiles/minbif.dir/build.make
src/CMakeFiles/minbif.dir/depend
make[3]: Entering directory '/<>/builddir'
cd /<>/builddir && /usr/bin/cmake -E cmake_depends "Unix
Makefiles" /<> /<>/src /<>/builddir
/<>/builddir/src
/<>/builddir/src/CMakeFiles/minbif.dir/DependInfo.cmake --color=
Scanning dependencies of target minbif
make[3]: Leaving directory '/<>/builddir'
/usr/bin/make -f src/CMakeFiles/minbif.dir/build.make
src/CMakeFiles/minbif.dir/build
make[3]: Entering directory '/<>/builddir'
[ 1%] Building CXX object src/CMakeFiles/minbif.dir/core/minbif.cpp.o
cd /<>/builddir/src && /usr/bin/c++ -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libpurple
-I/usr/include/libxml2 -I/usr/include/p11-kit-1 -I/<>/src -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DHAVE_IMLIB
-DHAVE_CACA -DHAVE_PAM -DHAVE_TLS -D_REENTRANT -D_FILE_OFFSET_BITS=64 -Wall
-Wextra -Wno-unused-parameter -O3 -DNDEBUG -o
CMakeFiles/minbif.dir/core/minbif.cpp.o -c /<>/src/core/minbif.cpp
/<>/src/core/minbif.cpp:39:16: warning: macro "__DATE__" might
prevent reproducible builds [-Wdate-time]
39 | strdup(MINBIF_BUILD.c_str()), /* don't care if we don't free it
as it can be used until exit. */
|^~~~
In file included from /<>/src/core/minbif.cpp:31:
/<>/src/core/version.h:60:44: warning: macro "__TIME__" might
prevent reproducible builds [-Wdate-time]
60 | #define MINBIF_BUILD ("(Build at " __DATE__ " " __TIME__ " with
libpurple-" \
|^~~~
/<>/src/core/minbif.cpp:39:16: note: in expansion of macro
‘MINBIF_BUILD’
39 | strdup(MINBIF_BUILD.c_str()), /* don't care if we don't free it
as it can be used until exit. */
|^~~~
/<>/src/core/minbif.cpp:246:27: warning: Deprecated pre-processor
symbol, replace with
246 | loop = g_main_new(FALSE);
| ^~~
Bug#911166: marked as done (gtksourceview2: Do not release with Bullseye)
Your message dated Fri, 15 Oct 2021 07:01:26 + with message-id and subject line Bug#994162: Removed package(s) from unstable has caused the Debian Bug report #911166, regarding gtksourceview2: Do not release with Bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 911166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911166 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gtksourceview2 Version: 2.10.5-3 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs gtksourceview2 Tags: sid buster Control: block -1 by 885675 885676 885678 885681 890456 911164 gtksourceview2 has not had an upstream release since 2010. The Debian GNOME Team would like to remove it from Debian. Please port your package to gtk3 and gtksourceview4. Because of the late filing of this RC bug in the Buster release cycle, please contact us if you object to its removal from Buster. Thanks, Jeremy Bicha --- End Message --- --- Begin Message --- Version: 2.10.5-3+rm Dear submitter, as the package gtksourceview2 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/994162 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---
Bug#978825: marked as done (gnome-shell-extension-redshift: ftbfs with autoconf 2.70)
Your message dated Fri, 15 Oct 2021 06:55:10 + with message-id and subject line Bug#993657: Removed package(s) from unstable has caused the Debian Bug report #978825, regarding gnome-shell-extension-redshift: ftbfs with autoconf 2.70 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.) -- 978825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978825 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gnome-shell-extension-redshift Version: 3.20.1-2 Severity: normal Tags: sid bookworm User: d...@debian.org Usertags: ftbfs-ac270 [This bug report is not targeted to the upcoming bullseye release] The package fails to build in a test rebuild on at least amd64 with autoconf 2.70, but succeeds to build with autoconf 2.69. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://qa-logs.debian.net/2020/09/26.ac270/gnome-shell-extension-redshift_3.20.1-2_unstable_ac270.log The last lines of the build log are at the end of this report. To build with autoconf 2.70, please install the autoconf package from experimental: apt-get -t=experimental install autoconf [...] User Environment APT_CONFIG=/var/lib/sbuild/apt.conf HOME=/sbuild-nonexistent LANG=C.UTF-8 LC_ALL=C.UTF-8 LOGNAME=user42 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games SCHROOT_ALIAS_NAME=unstable SCHROOT_CHROOT_NAME=sid-amd64-sbuild SCHROOT_COMMAND=env SCHROOT_GID=1001 SCHROOT_GROUP=user42 SCHROOT_SESSION_ID=sid-amd64-sbuild-ee1ad6ed-3742-40bf-b3d7-f8519a188583 SCHROOT_UID=1001 SCHROOT_USER=user42 SHELL=/bin/sh USER=user42 dpkg-buildpackage - Command: dpkg-buildpackage -us -uc -sa -rfakeroot dpkg-buildpackage: info: source package gnome-shell-extension-redshift dpkg-buildpackage: info: source version 3.20.1-2 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Eric Dorland dpkg-source --before-build . dpkg-buildpackage: info: host architecture amd64 fakeroot debian/rules clean dh clean --with autoreconf dh: warning: Compatibility levels before 10 are deprecated (level 9 in use) dh_clean dh_clean: warning: Compatibility levels before 10 are deprecated (level 9 in use) dpkg-source -b . dpkg-source: info: using source format '3.0 (quilt)' dpkg-source: info: building gnome-shell-extension-redshift using existing ./gnome-shell-extension-redshift_3.20.1.orig.tar.gz dpkg-source: info: building gnome-shell-extension-redshift in gnome-shell-extension-redshift_3.20.1-2.debian.tar.xz dpkg-source: info: building gnome-shell-extension-redshift in gnome-shell-extension-redshift_3.20.1-2.dsc debian/rules build dh build --with autoreconf dh: warning: Compatibility levels before 10 are deprecated (level 9 in use) dh_update_autotools_config debian/rules override_dh_autoreconf make[1]: Entering directory '/<>' dh_autoreconf ./autogen.sh dh_autoreconf: warning: Compatibility levels before 10 are deprecated (level 9 in use) /usr/bin/gnome-autogen.sh ***Warning*** PKG_NAME is deprecated, you may remove it from autogen.sh checking for automake >= 1.11.2... testing automake... found 1.16.2 checking for autoreconf >= 2.53... testing autoreconf... found 2.69c Processing ./configure.ac Running autoreconf... autoreconf: export WARNINGS=no-portability autoreconf: Entering directory '.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal --force autoreconf: configure.ac: tracing autoreconf: configure.ac: not using Libtool autoreconf: running: intltoolize --copy --force ERROR: 'IT_PROG_INTLTOOL' must appear in configure.ac for intltool to work. autoreconf: error: intltoolize failed with exit status: 1 dh_autoreconf: error: ./autogen.sh returned exit code 1 make[1]: *** [debian/rules:9: override_dh_autoreconf] Error 25 make[1]: Leaving directory '/<>' make: *** [debian/rules:6: build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 --- End Message --- --- Begin Message --- Version: 3.20.1-2.1+rm Dear submitter, as the package gnome-shell-extension-redshift has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/993657 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been
Bug#988940: marked as done (gnome-shell-extension-redshift: Is this package obsolete?)
Your message dated Fri, 15 Oct 2021 06:55:10 + with message-id and subject line Bug#993657: Removed package(s) from unstable has caused the Debian Bug report #988940, regarding gnome-shell-extension-redshift: Is this package obsolete? 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.) -- 988940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988940 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-shell-extension-redshift Version: 3.20.1-2.1 Severity: serious https://extensions.gnome.org/extension/685/redshift/ Deprecation notice: As of GNOME 3.24, there is native support for night light mode in your display settings. This extension is not required or reccomended anymore. --- End Message --- --- Begin Message --- Version: 3.20.1-2.1+rm Dear submitter, as the package gnome-shell-extension-redshift has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/993657 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---
Bug#993336: marked as done (libclass-trait-perl: arch:all but depends on perlapi-5.32.0)
Your message dated Fri, 15 Oct 2021 06:35:12 + with message-id and subject line Bug#993410: Removed package(s) from unstable has caused the Debian Bug report #993336, regarding libclass-trait-perl: arch:all but depends on perlapi-5.32.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 993336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993336 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libclass-trait-perl Version: 0.31-4.1 Severity: serious Tags: sid bookworm User: debian-p...@lists.debian.org Usertags: perl-5.34-transition X-Debbugs-Cc: Holger Levsen It looks like the no-change 0.31-4.1 upload introduced a regression: despite being arch:all it ships /usr/lib/x86_64-linux-gnu/perl5/5.32/auto/Class/Trait/.packlist which has made debhelper add a dependency on perlapi-5.32.0. This is broken: the package will become uninstallable when Perl 5.34 (currently in experimental) enters unstable, but it can't be automatically rebuilt as we don't do arch:all binNMUs. The reason is a hardcoded reference to the old /usr/lib/perl5 directory in debian/rules: the packlist file no longer got removed in the rebuild because it gets installed elsewhere nowadays. AFAICS when this is fixed, upgrades (even partial) from the current version should work fine, so we can live with having this in the stable release. Copying Holger who did the NMU, but mainly just FYI. I'm sure the pkg-perl folks can fix this before the Perl 5.34 transition if the maintainer doesn't. -- Niko Tyni nt...@debian.org --- End Message --- --- Begin Message --- Version: 0.31-4.1+rm Dear submitter, as the package libclass-trait-perl has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/993410 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---
Bug#938789: marked as done (vizigrep: Python2 removal in sid/bullseye)
Your message dated Fri, 15 Oct 2021 06:33:10 + with message-id and subject line Bug#993369: Removed package(s) from unstable has caused the Debian Bug report #938789, regarding vizigrep: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 938789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938789 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:vizigrep Version: 1.4-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:vizigrep If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 1.4-1+rm Dear submitter, as the package vizigrep has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/993369 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---
Bug#812619: marked as done (libtm-perl: FTBFS - Failed test 'assertions applying to identical topics are found')
Your message dated Fri, 15 Oct 2021 06:34:21 +
with message-id
and subject line Bug#993411: Removed package(s) from unstable
has caused the Debian Bug report #812619,
regarding libtm-perl: FTBFS - Failed test 'assertions applying to identical
topics are found'
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.)
--
812619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812619
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libtm-perl
Version: 1.56-7
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
# Failed test 'assertions applying to identical topics are found'
# at t/043diff.t line 408.
# Comparing hash keys of $data->{"modified"}
# Extra: 'tm:/told'
# Looks like you failed 1 test of 52.
t/043diff.t
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/52 subtests
[...]
Test Summary Report
---
t/043diff.t (Wstat: 256 Tests: 52 Failed: 1)
Failed test: 52
Non-zero exit status: 1
t/102mapsphere.t (Wstat: 0 Tests: 41 Failed: 0)
TODO passed: 25
Files=41, Tests=11410, 54 wallclock secs ( 2.24 usr 0.17 sys + 52.04 cusr
1.21 csys = 55.66 CPU)
Result: FAIL
Failed 1/41 test programs. 1/11410 subtests failed.
Makefile:1259: recipe for target 'test_dynamic' failed
The full build log is attached; please do let me know if the problem is
unreproducible, in which case I shall try to investigate further.
Best,
Michael
libtm-perl-build-log.txt.gz
Description: application/gunzip
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 1.56-10+rm
Dear submitter,
as the package libtm-perl has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/993411
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---
Bug#980331: marked as done (tokyotyrant: should ship with bullseye?)
Your message dated Fri, 15 Oct 2021 06:14:58 + with message-id and subject line Bug#992644: Removed package(s) from unstable has caused the Debian Bug report #980331, regarding tokyotyrant: should ship with bullseye? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 980331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980331 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tokyotyrant tokyotyrant is a network server. It's upstream has vanished, and the last upstream release was in 2012 or earlier; that version is not packaged in Debian. The package is currently orphaned in Debian. Should bullseye really ship with such a package? Also, it exposes tokyocabinet to the network, which itself is a rather old codebase, last updated in 2013. A successor, Tkrzw is actively maintained. Security team, maybe you also want to chime in here. I'll consider raising this bugs priority over time. Thanks for everyone's considerations, Chris --- End Message --- --- Begin Message --- Version: 1.1.40-4.3+rm Dear submitter, as the package tokyotyrant has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/992644 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---
Bug#906474: marked as done (ircp-tray: FTBFS in buster/sid (linux/irda.h: No such file or directory))
Your message dated Fri, 15 Oct 2021 06:13:04 + with message-id and subject line Bug#992643: Removed package(s) from unstable has caused the Debian Bug report #906474, regarding ircp-tray: FTBFS in buster/sid (linux/irda.h: No such file or directory) 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.) -- 906474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906474 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ircp-tray Version: 0.7.6-1.2 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-arch dh build-arch dh: Compatibility levels before 9 are deprecated (level 7 in use) dh_update_autotools_config -a debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' /<>/configure --prefix=/usr checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no [... snipped ...] utf8 = (char*) unicode_to_utf8(hv.bs, hlen); ^ ircp_server.c:508:28: warning: implicit declaration of function 'filename_from_utf8' [-Wimplicit-function-declaration] srv->filename = (char*) filename_from_utf8(utf8); ^~ ircp_server.c:508:20: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] srv->filename = (char*) filename_from_utf8(utf8); ^ ircp_server.c:523:18: warning: implicit declaration of function 'filename_to_utf8' [-Wimplicit-function-declaration] utf8 = (char*) filename_to_utf8(srv->filename); ^~~~ ircp_server.c:523:10: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] utf8 = (char*) filename_to_utf8(srv->filename); ^ ircp_server.c:524:3: warning: implicit declaration of function 'recvfile_launch_dialog' [-Wimplicit-function-declaration] recvfile_launch_dialog(utf8, >localfilename, ^~ mv -f .deps/ircp_server.Tpo .deps/ircp_server.Po gcc -DHAVE_CONFIG_H -I. -I.. -I.. -DLOCALE_DIR=\""/usr/share/locale"\" -DDATADIR=\""/usr/share"\" -DG_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libusb-1.0 -pthread -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 -MT progresswin.o -MD -MP -MF .deps/progresswin.Tpo -c -o progresswin.o progresswin.c mv -f .deps/progresswin.Tpo .deps/progresswin.Po gcc -DHAVE_CONFIG_H -I. -I.. -I.. -DLOCALE_DIR=\""/usr/share/locale"\" -DDATADIR=\""/usr/share"\" -DG_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libusb-1.0 -pthread -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 -MT savefiledlg.o -MD -MP -MF .deps/savefiledlg.Tpo -c -o savefiledlg.o savefiledlg.c savefiledlg.c: In function 'savefile_dialog_new': savefiledlg.c:68:16: warning: implicit declaration of function 'config_get_lastsavedir' [-Wimplicit-function-declaration] path = (char*)config_get_lastsavedir(); ^~ savefiledlg.c:68:9: warning: cast to pointer from
Bug#989074: marked as done (Ship upstream-dead aewm with bullseye?)
Your message dated Fri, 15 Oct 2021 06:01:50 +
with message-id
and subject line Bug#989005: Removed package(s) from unstable
has caused the Debian Bug report #989074,
regarding Ship upstream-dead aewm with bullseye?
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
989074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989074
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
Hi,
aewm has not seen a new upstream release since 2007, and upstream
seems to have stopped working on it long long time ago.
Furthermore:
- the upstream website is not available anymore
- I cannot find anywhere a potential repository that continues the
development
- it has been "maintained" in Debian with NMUs/QA uploads since 2011
- uses old tech/libs (GTK+ 2)
- it has a very low popcon count (38 at the time I'm writing this)
- plenty of alternatives ("minimalist/lightweights" WMs) exist
Hence, it looks to me it would be a better idea to simply remove aewm
from Debian.
Thanks,
--
Pino
--- End Message ---
--- Begin Message ---
Version: 1.3.12-7+rm
Dear submitter,
as the package aewm has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/989005
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---
