Bug#995281: lomiri-download-manager: FTBFS due to symbols changes
Source: lomiri-download-manager Version: 0.1.0-8 Severity: serious Hi Mike, The lomiri-download-manager package fails to build in unstable, because of some symbols file mismatches: [...] dpkg-gensymbols: warning: debian/liblomiri-download-manager-common0/DEBIAN/symbols doesn't match completely debian/liblomiri-download-manager-common0.symbols --- debian/liblomiri-download-manager-common0.symbols (liblomiri-download-manager-common0_0.1.0-8_amd64) +++ dpkg-gensymbolsKFBfk1 2021-09-29 04:28:53.866805288 + @@ -34,8 +34,8 @@ _ZN6Lomiri15DownloadManager19GroupDownloadStructC2ERK7QStringS4_S4_@Base 0.1.0 _ZN6Lomiri15DownloadManager19GroupDownloadStructC2ERKS1_@Base 0.1.0 _ZN6Lomiri15DownloadManager19GroupDownloadStructC2Ev@Base 0.1.0 - (arch=armel armhf)_ZN6Lomiri15DownloadManager19GroupDownloadStructD1Ev@Base 0.1.0 - (arch=armel armhf)_ZN6Lomiri15DownloadManager19GroupDownloadStructD2Ev@Base 0.1.0 + _ZN6Lomiri15DownloadManager19GroupDownloadStructD1Ev@Base 0.1.0 + _ZN6Lomiri15DownloadManager19GroupDownloadStructD2Ev@Base 0.1.0 _ZN6Lomiri15DownloadManager19GroupDownloadStructaSERKS1_@Base 0.1.0 _ZN6Lomiri15DownloadManagerlsER13QDBusArgumentRKNS0_14DownloadStructE@Base 0.1.0 _ZN6Lomiri15DownloadManagerlsER13QDBusArgumentRKNS0_19DownloadStateStructE@Base 0.1.0 dpkg-gensymbols: warning: debian/liblomiri-download-manager-client0/DEBIAN/symbols doesn't match completely debian/liblomiri-download-manager-client0.symbols --- debian/liblomiri-download-manager-client0.symbols (liblomiri-download-manager-client0_0.1.0-8_amd64) +++ dpkg-gensymbolsUJ6Ro5 2021-09-29 04:28:53.982805242 + @@ -131,14 +131,14 @@ _ZNK6Lomiri15DownloadManager9DBusError10metaObjectEv@Base 0.1.0 _ZNK6Lomiri15DownloadManager9HashError10metaObjectEv@Base 0.1.0 _ZNK6Lomiri15DownloadManager9HttpError10metaObjectEv@Base 0.1.0 -#MISSING: 0.1.0# (optional=templinst|arch=amd64)_ZNSt8functionIFvPN6Lomiri15DownloadManager13DownloadsListEEEC1ERKS5_@Base 0.1.0 -#MISSING: 0.1.0# (optional=templinst|arch=amd64)_ZNSt8functionIFvPN6Lomiri15DownloadManager13DownloadsListEEEC2ERKS5_@Base 0.1.0 -#MISSING: 0.1.0# (optional=templinst|arch=amd64)_ZNSt8functionIFvPN6Lomiri15DownloadManager13GroupDownloadEEEC1ERKS5_@Base 0.1.0 -#MISSING: 0.1.0# (optional=templinst|arch=amd64)_ZNSt8functionIFvPN6Lomiri15DownloadManager13GroupDownloadEEEC2ERKS5_@Base 0.1.0 -#MISSING: 0.1.0# (optional=templinst|arch=amd64)_ZNSt8functionIFvPN6Lomiri15DownloadManager8DownloadEEEC1ERKS5_@Base 0.1.0 -#MISSING: 0.1.0# (optional=templinst|arch=amd64)_ZNSt8functionIFvPN6Lomiri15DownloadManager8DownloadEEEC2ERKS5_@Base 0.1.0 -#MISSING: 0.1.0# (optional=templinst|arch=amd64)_ZNSt8functionIFvRK7QStringS2_PN6Lomiri15DownloadManager13DownloadsListEEEC1ERKS8_@Base 0.1.0 -#MISSING: 0.1.0# (optional=templinst|arch=amd64)_ZNSt8functionIFvRK7QStringS2_PN6Lomiri15DownloadManager13DownloadsListEEEC2ERKS8_@Base 0.1.0 +#MISSING: 0.1.0-8# (optional=templinst|arch=amd64)_ZNSt8functionIFvPN6Lomiri15DownloadManager13DownloadsListEEEC1ERKS5_@Base 0.1.0 +#MISSING: 0.1.0-8# (optional=templinst|arch=amd64)_ZNSt8functionIFvPN6Lomiri15DownloadManager13DownloadsListEEEC2ERKS5_@Base 0.1.0 +#MISSING: 0.1.0-8# (optional=templinst|arch=amd64)_ZNSt8functionIFvPN6Lomiri15DownloadManager13GroupDownloadEEEC1ERKS5_@Base 0.1.0 +#MISSING: 0.1.0-8# (optional=templinst|arch=amd64)_ZNSt8functionIFvPN6Lomiri15DownloadManager13GroupDownloadEEEC2ERKS5_@Base 0.1.0 +#MISSING: 0.1.0-8# (optional=templinst|arch=amd64)_ZNSt8functionIFvPN6Lomiri15DownloadManager8DownloadEEEC1ERKS5_@Base 0.1.0 +#MISSING: 0.1.0-8# (optional=templinst|arch=amd64)_ZNSt8functionIFvPN6Lomiri15DownloadManager8DownloadEEEC2ERKS5_@Base 0.1.0 +#MISSING: 0.1.0-8# (optional=templinst|arch=amd64)_ZNSt8functionIFvRK7QStringS2_PN6Lomiri15DownloadManager13DownloadsListEEEC1ERKS8_@Base 0.1.0 +#MISSING: 0.1.0-8# (optional=templinst|arch=amd64)_ZNSt8functionIFvRK7QStringS2_PN6Lomiri15DownloadManager13DownloadsListEEEC2ERKS8_@Base 0.1.0 _ZTIN6Lomiri15DownloadManager12NetworkErrorE@Base 0.1.0 _ZTIN6Lomiri15DownloadManager12ProcessErrorE@Base 0.1.0 _ZTIN6Lomiri15DownloadManager13DownloadsListE@Base 0.1.0 dh_makeshlibs: error: failing due to earlier errors make: *** [debian/rules:54: binary] Error 25 [...] I discovered this error because the package also fails to build in Ubuntu, albeit with a different set of symbol errors: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file : see diff output below dpkg-gensymbols: warning: debian/libldm-common0/DEBIAN/symbols doesn't match com pletely debian/libldm-common0.symbols --- debian/libldm-common0.symbols (libldm-common0_0.1.0-8_amd64) +++ dpkg-gensymbolsRpfeei 2021-09-29 02:38:00.468167849 + @@ -75,9 +75,9 @@ _ZN6Lomiri9Transfers6System14DBusConnectionC1EP7QObject@Base 0.1.0 _ZN6Lomiri9Transfers6System14DBusConnectionC2E15QDBusConnectionP7QObject@Base 0.1.0
Bug#995282: amule crashes on start
Package: amule
Version: 1:2.3.3-1
Severity: grave
(gdb) run
Starting program: /usr/bin/amule
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Detaching after vfork from child process 7263]
2021-09-29 07:08:05: Initialising aMule 2.3.3 compiled with wxGTK2 v3.0.5 and
Boost 1.74
2021-09-29 07:08:05: Checking if there is an instance already running...
2021-09-29 07:08:05: No other instances are running.
Program received signal SIGSEGV, Segmentation fault.
0x77ca062c in CryptoPP::SecureWipeBuffer
(n=2305843009213693951, buf=0x2) at misc.h:1442
1442misc.h: Datei oder Verzeichnis nicht gefunden.
(gdb) bt
#0 0x77ca062c in CryptoPP::SecureWipeBuffer
(n=2305843009213693951, buf=0x2) at misc.h:1442
#1 CryptoPP::SecureWipeArray (n=2305843009213693951, buf=0x2)
at misc.h:1493
#2 CryptoPP::AllocatorWithCleanup::deallocate
(size=2305843009213693951, ptr=0x2, this=) at secblock.h:235
#3 CryptoPP::StandardReallocate > (oldPtr=0x2,
oldSize=2305843009213693951, newSize=8, preserve=, alloc=...) at
secblock.h:172
#4 0x77ca350a in CryptoPP::AllocatorWithCleanup::reallocate (preserve=false, newSize=8, oldSize=,
oldPtr=, this=) at secblock.h:259
#5 CryptoPP::SecBlock >::New (newSize=8, this=) at secblock.h:1128
#6 CryptoPP::SecBlock >::CleanNew (newSize=8, this=) at secblock.h:1145
#7 CryptoPP::Integer::Decode (this=0x56c4ee20, bt=..., inputLen=, s=) at integer.cpp:3397
#8 0x77caae4e in CryptoPP::Integer::BERDecode
(this=this@entry=0x56c4ee20, bt=...) at asn.h:405
#9 0x77dfea1b in CryptoPP::InvertibleRSAFunction::BERDecodePrivateKey
(this=0x56c4ed48, bt=...) at rsa.cpp:211
#10 0x77cb6e98 in CryptoPP::PKCS8PrivateKey::BERDecode
(this=this@entry=0x56c4edc8, bt=...) at asn.cpp:679
#11 0x5575e7fb in CryptoPP::InvertibleRSAFunction::BERDecode (bt=...,
this=0x56c4ed48) at /usr/include/cryptopp/rsa.h:100
#12
CryptoPP::PK_FinalTemplate, CryptoPP::RSA,
CryptoPP::PKCS1v15_SignatureMessageEncodingMethod, CryptoPP::SHA1> >
>::PK_FinalTemplate (
bt=..., this=0x56c4ed30) at /usr/include/cryptopp/pubkey.h:2196
#13 CClientCreditsList::InitalizeCrypting (this=0x56ddd230) at
../../src/ClientCreditsList.cpp:311
#14 0x5575fa24 in CClientCreditsList::CClientCreditsList
(this=0x56ddd230) at ../../src/ClientCreditsList.cpp:54
#15 0x55745ffe in CamuleApp::OnInit (this=this@entry=0x55c3bc20) at
../../src/amule.cpp:513
#16 0x558079f7 in CamuleGuiApp::OnInit (this=0x55c3bc20) at
../../src/amule-gui.cpp:288
#17 0x770093aa in wxEntry (argc=, argv=)
at ../src/common/init.cpp:490
#18 0x5571b562 in main (argc=, argv=) at
../../src/amule-gui.cpp:95
(gdb) bt full
#0 0x77ca062c in CryptoPP::SecureWipeBuffer
(n=2305843009213693951, buf=0x2) at misc.h:1442
p = 0x2
#1 CryptoPP::SecureWipeArray (n=2305843009213693951, buf=0x2)
at misc.h:1493
No locals.
#2 CryptoPP::AllocatorWithCleanup::deallocate
(size=2305843009213693951, ptr=0x2, this=) at secblock.h:235
No locals.
#3 CryptoPP::StandardReallocate > (oldPtr=0x2,
oldSize=2305843009213693951, newSize=8, preserve=, alloc=...) at
secblock.h:172
No locals.
#4 0x77ca350a in CryptoPP::AllocatorWithCleanup::reallocate (preserve=false, newSize=8, oldSize=,
oldPtr=, this=) at secblock.h:259
No locals.
#5 CryptoPP::SecBlock >::New (newSize=8, this=) at secblock.h:1128
No locals.
#6 CryptoPP::SecBlock >::CleanNew (newSize=8, this=) at secblock.h:1145
No locals.
#7 CryptoPP::Integer::Decode (this=0x56c4ee20, bt=..., inputLen=, s=) at integer.cpp:3397
b = 30 '\036'
#8 0x77caae4e in CryptoPP::Integer::BERDecode
(this=this@entry=0x56c4ee20, bt=...) at asn.h:405
dec = { =
{
>> = {> =
{ = { =
{ = {_vptr.Clonable = 0x77f1fed8 }, }, =
{_vptr.Waitable = 0x77f20070 },
m_buf = "\001\000\000\000\000\000\000"}, },
m_autoSignalPropagation = -1}, m_messageEnd = false}, m_inQueue =
@0x7fffd640, m_length = 48, m_finished = false, m_definiteLength = true}
#9 0x77dfea1b in CryptoPP::InvertibleRSAFunction::BERDecodePrivateKey
(this=0x56c4ed48, bt=...) at rsa.cpp:211
privateKey = { = { =
{
>> = {> =
{ = { =
{ = {_vptr.Clonable = 0x77f1e840 }, }, =
{_vptr.Waitable = 0x77f1e9d8 },
m_buf = "`\327\377\377\377\177\000"}, },
m_autoSignalPropagation = -1}, m_messageEnd = false}, m_inQueue =
@0x7fffd760, m_length = 182, m_finished = false, m_definiteLength = true},
}
version = 0
#10 0x77cb6e98 in CryptoPP::PKCS8PrivateKey::BERDecode
(this=this@entry=0x56c4edc8, bt=...) at asn.cpp:679
privateKeyInfo = { = { =
{
>> = {> =
{ = { =
{ = {_vptr.Clonable = 0x77f1e840 }, }, =
{_vptr.Waitable = 0x77f1e9d8 },
m_buf = "\000\000\000\000\000\000\000"}, },
m_autoSignalPropagation = -1}, m_messageEnd = false}, m_inQueue =
@0x7fffd950,
Processed: ayatana-indicator-datetime: Fails to build from source
Processing commands for cont...@bugs.debian.org: > block 993945 by 995279 Bug #993945 [release.debian.org] transition: evolution-data-server 993945 was blocked by: 992870 993934 993945 was blocking: 993850 Added blocking bug(s) of 993945: 995279 > tags 995279 +ftbfs Bug #995279 [src:ayatana-indicator-datetime] ayatana-indicator-datetime: Fails to build from source Added tag(s) ftbfs. > End of message, stopping processing here. Please contact me if you need assistance. -- 993945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993945 995279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995279 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995279: ayatana-indicator-datetime: Fails to build from source
Source: ayatana-indicator-datetime Version: 0.8.2-1 Severity: serious Tags: patch sid bookworm Control: blocks 993945 by -1 Please apply this commit to Debian to fix this package's failure to build from source. https://github.com/AyatanaIndicators/ayatana-indicator-datetime/commit/19923632 This is needed to complete the evolution-data-server 3.42 transition. Thanks, Jeremy Bicha
Bug#995187: qtwebengine-opensource-src FTBFS on mips*: unistd_nr_{n32,n64,o32}.h no linger exported by the kernel
YunQiang Su 于2021年9月28日周二 下午12:20写道： > > Adrian Bunk 于2021年9月28日周二 上午12:06写道： > > > > Source: qtwebengine-opensource-src > > Version: 5.15.5+dfsg-2 > > Severity: serious > > Tags: ftbfs > > > > https://buildd.debian.org/status/fetch.php?pkg=qtwebengine-opensource-src=mips64el=5.15.6%2Bdfsg-1=1632387575=0 > > > > ... > > FAILED: obj/sandbox/linux/seccomp_bpf/syscall_set.o > > /usr/bin/g++ -MMD -MF obj/sandbox/linux/seccomp_bpf/syscall_set.o.d > > -DSANDBOX_IMPLEMENTATION -DUSE_UDEV -DUSE_AURA=1 -DUSE_NSS_CERTS=1 > > -DUSE_OZONE=1 -DOFFICIAL_BUILD -DTOOLKIT_QT -D_FILE_OFFSET_BITS=64 > > -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DNO_UNWIND_TABLES > > -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -DNDEBUG -DNVALGRIND > > -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DOPENSSL_NO_ASM -Igen > > -I../../3rdparty/chromium > > -I../../3rdparty/chromium/third_party/perfetto/include > > -Igen/third_party/perfetto/build_config -Igen/third_party/perfetto -Igen > > -Igen -Igen -Igen -I../../3rdparty/chromium/third_party/abseil-cpp > > -I../../3rdparty/chromium/third_party/boringssl/src/include > > -I../../3rdparty/chromium/third_party/protobuf/src -Igen/protoc_out > > -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector > > -fno-unwind-tables -fno-asynchronous-unwind-tables -fPIC -pipe -pthread > > -D__SANE_USERSPACE_TYPES__ -mips64r2 -Wa,-mips64r2 -Wall -U_FORTIFY_SOURCE > > -D_FORTIFY_SOURCE=2 -Wno-unused-local-typedefs -Wno-maybe-uninitialized > > -Wno-deprecated-declarations -fno-delete-null-pointer-checks -Wno-comments > > -Wno-packed-not-aligned -Wno-dangling-else -Wno-missing-field-initializers > > -Wno-unused-parameter -O2 -fno-ident -fdata-sections -ffunction-sections > > -fno-omit-frame-pointer -g0 -fvisibility=hidden -std=gnu++14 -Wno-narrowing > > -Wno-class-memaccess -Wno-attributes -Wno-class-memaccess > > -Wno-subobject-linkage -Wno-invalid-offsetof -Wno-return-type > > -Wno-deprecated-copy -fno-exceptions -fno-rtti -fvisibility-inlines-hidden > > -c ../../3rdparty/chromium/sandbox/linux/bpf_dsl/syscall_set.cc -o > > obj/sandbox/linux/seccomp_bpf/syscall_set.o > > In file included from > > ../../3rdparty/chromium/sandbox/linux/bpf_dsl/syscall_set.cc:12: > > ../../3rdparty/chromium/sandbox/linux/bpf_dsl/linux_syscall_ranges.h:47:10: > > fatal error: asm/unistd_nr_n64.h: No such file or directory > >47 | #include // for __NR_64_Linux and > > __NR_64_Linux_syscalls > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ccb21774863add648e709337919d2cfeefe4be49 > This commit change the struct of unistd*.h files. > And I guess that we can just drop mipsel-linux-5.patch now. > I am testing it. > Ohh, the new mips linux kernel removes some macros: so now we can use the same code as x86: Index: qtwebengine-opensource-src-5.15.6+dfsg/src/3rdparty/chromium/sandbox/linux/bpf_dsl/linux_syscall_ranges.h === --- qtwebengine-opensource-src-5.15.6+dfsg.orig/src/3rdparty/chromium/sandbox/linux/bpf_dsl/linux_syscall_ranges.h +++ qtwebengine-opensource-src-5.15.6+dfsg/src/3rdparty/chromium/sandbox/linux/bpf_dsl/linux_syscall_ranges.h @@ -35,18 +35,11 @@ #define MIN_GHOST_SYSCALL (MIN_PRIVATE_SYSCALL + 0xfff0u) #define MAX_SYSCALL (MIN_GHOST_SYSCALL + 4u) -#elif defined(ARCH_CPU_MIPS_FAMILY) && defined(ARCH_CPU_32_BITS) +#elif defined(ARCH_CPU_MIPS_FAMILY) -#include // for __NR_O32_Linux and __NR_Linux_syscalls -#define MIN_SYSCALL __NR_O32_Linux -#define MAX_PUBLIC_SYSCALL (MIN_SYSCALL + __NR_Linux_syscalls) -#define MAX_SYSCALL MAX_PUBLIC_SYSCALL - -#elif defined(ARCH_CPU_MIPS_FAMILY) && defined(ARCH_CPU_64_BITS) - -#include // for __NR_64_Linux and __NR_64_Linux_syscalls -#define MIN_SYSCALL __NR_64_Linux -#define MAX_PUBLIC_SYSCALL (MIN_SYSCALL + __NR_64_Linux_syscalls) +#include +#define MIN_SYSCALL __NR_Linux +#define MAX_PUBLIC_SYSCALL (MIN_SYSCALL + 999u) #define MAX_SYSCALL MAX_PUBLIC_SYSCALL #elif defined(__aarch64__) > > > | ^ > > compilation terminated. > > ... > > > > > > Context: > > https://sources.debian.org/src/qtwebengine-opensource-src/5.15.6+dfsg-1/debian/patches/mipsel-linux-5.patch/ > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ccb21774863a > > > > > -- > YunQiang Su -- YunQiang Su
Processed: user release.debian....@packages.debian.org, usertagging 994451, tagging 994451
Processing commands for cont...@bugs.debian.org: > user release.debian@packages.debian.org Setting user to release.debian@packages.debian.org (was siret...@tauware.de). > usertags 994451 pu There were no usertags set. Usertags are now: pu. > tags 994451 + bullseye Bug #994451 [golang-github-containers-common] golang-github-containers-common: secomp.json does not include newer syscall used by stable kernel/glibc on arm Added tag(s) bullseye. > thanks Stopping processing here. Please contact me if you need assistance. -- 994451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994451 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995223: libffi: SIGILL on powerpc and ppc64 systems since libffi8
Hello! On 9/29/21 00:38, John Paul Adrian Glaubitz wrote: > There is actually a baseline violation on i386 as "-march=amdfam10" is > passed to the compiler, see the build log in [1], for example. Comparing the build logs, it seems that this an issue with the newer version of autoconf that was used to build version 3.4.2-2. Looking at the log for 3.4.2-2, a lot of autoconf warnings can be seen which are not present in the log for 3.4.1-1. > https://buildd.debian.org/status/fetch.php?pkg=libffi=powerpc=3.4.2-1=1626443428=0 > https://buildd.debian.org/status/fetch.php?pkg=libffi=powerpc=3.4.2-2=1632868252=0 So, upstream needs to fix compatibility issues with the newer autoconf version. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#995223: libffi: SIGILL on powerpc and ppc64 systems since libffi8
Hi! On 9/28/21 22:40, John Paul Adrian Glaubitz wrote: > We should therefore pass "--enable-portable-binary" in debian/rules. There is actually a baseline violation on i386 as "-march=amdfam10" is passed to the compiler, see the build log in [1], for example. Adrian > [1] > https://buildd.debian.org/status/fetch.php?pkg=libffi=i386=3.4.2-2=1632469242=0 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#957954: wmwave: diff for NMU version 0.4-11.1
Control: tags 957954 + patch Control: tags 957954 + pending Dear maintainer, I've prepared an NMU for wmwave (versioned as 0.4-11.1) and uploaded it to DELAYED/7. Please feel free to tell me if I should delay it longer or cancel the NMU. Regards. diff -Nru wmwave-0.4/debian/changelog wmwave-0.4/debian/changelog --- wmwave-0.4/debian/changelog 2019-10-25 21:59:08.0 + +++ wmwave-0.4/debian/changelog 2021-02-12 22:18:49.0 + @@ -1,3 +1,11 @@ +wmwave (0.4-11.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add debian/patches/Fix-compilation-with-gcc-10.patch. +Thanks to Logan Rosen . (Closes: #957954) + + -- Francisco Vilmar Cardoso Ruviaro Fri, 12 Feb 2021 22:18:49 + + wmwave (0.4-11) unstable; urgency=medium [ Guido Günther ] diff -Nru wmwave-0.4/debian/patches/Fix-compilation-with-gcc-10.patch wmwave-0.4/debian/patches/Fix-compilation-with-gcc-10.patch --- wmwave-0.4/debian/patches/Fix-compilation-with-gcc-10.patch 1970-01-01 00:00:00.0 + +++ wmwave-0.4/debian/patches/Fix-compilation-with-gcc-10.patch 2021-02-12 22:18:49.0 + @@ -0,0 +1,29 @@ +Description: Fix compilation with GCC 10. +Author: Logan Rosen +Bug-Debian: https://bugs.debian.org/957954 +Forwarded: no +Reviewed-By: Francisco Vilmar Cardoso Ruviaro +Last-Update: 2021-02-12 + +--- a/wmgeneral.h b/wmgeneral.h +@@ -36,7 +36,7 @@ + /* Global variable */ + /***/ + +-Display *display; ++extern Display*display; + + /***/ + /* Function Prototypes */ +--- a/wmwave.c b/wmwave.c +@@ -79,6 +79,8 @@ + + int mode = 0;// default: no card detected + ++Display *display; ++ + void usage(void); + void printversion(void); + void BlitString(char *name, int x, int y); diff -Nru wmwave-0.4/debian/patches/series wmwave-0.4/debian/patches/series --- wmwave-0.4/debian/patches/series2019-10-25 21:28:57.0 + +++ wmwave-0.4/debian/patches/series2021-02-12 22:18:49.0 + @@ -1,2 +1,3 @@ Debian-delta.patch Move-libraries-to-the-end.patch +Fix-compilation-with-gcc-10.patch -- Francisco Vilmar Cardoso Ruviaro 4096R: 1B8C F656 EF3B 8447 2F48 F0E7 82FB F706 0B2F 7D00 diff -Nru wmwave-0.4/debian/changelog wmwave-0.4/debian/changelog --- wmwave-0.4/debian/changelog 2019-10-25 21:59:08.0 + +++ wmwave-0.4/debian/changelog 2021-02-12 22:18:49.0 + @@ -1,3 +1,11 @@ +wmwave (0.4-11.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add debian/patches/Fix-compilation-with-gcc-10.patch. +Thanks to Logan Rosen . (Closes: #957954) + + -- Francisco Vilmar Cardoso Ruviaro Fri, 12 Feb 2021 22:18:49 + + wmwave (0.4-11) unstable; urgency=medium [ Guido Günther ] diff -Nru wmwave-0.4/debian/patches/Fix-compilation-with-gcc-10.patch wmwave-0.4/debian/patches/Fix-compilation-with-gcc-10.patch --- wmwave-0.4/debian/patches/Fix-compilation-with-gcc-10.patch 1970-01-01 00:00:00.0 + +++ wmwave-0.4/debian/patches/Fix-compilation-with-gcc-10.patch 2021-02-12 22:18:49.0 + @@ -0,0 +1,29 @@ +Description: Fix compilation with GCC 10. +Author: Logan Rosen +Bug-Debian: https://bugs.debian.org/957954 +Forwarded: no +Reviewed-By: Francisco Vilmar Cardoso Ruviaro +Last-Update: 2021-02-12 + +--- a/wmgeneral.h b/wmgeneral.h +@@ -36,7 +36,7 @@ + /* Global variable */ + /***/ + +-Display *display; ++extern Display*display; + + /***/ + /* Function Prototypes */ +--- a/wmwave.c b/wmwave.c +@@ -79,6 +79,8 @@ + + int mode = 0;// default: no card detected + ++Display *display; ++ + void usage(void); + void printversion(void); + void BlitString(char *name, int x, int y); diff -Nru wmwave-0.4/debian/patches/series wmwave-0.4/debian/patches/series --- wmwave-0.4/debian/patches/series2019-10-25 21:28:57.0 + +++ wmwave-0.4/debian/patches/series2021-02-12 22:18:49.0 + @@ -1,2 +1,3 @@ Debian-delta.patch Move-libraries-to-the-end.patch +Fix-compilation-with-gcc-10.patch OpenPGP_signature Description: OpenPGP digital signature
Processed: wmwave: diff for NMU version 0.4-11.1
Processing control commands: > tags 957954 + patch Bug #957954 [src:wmwave] wmwave: ftbfs with GCC-10 Ignoring request to alter tags of bug #957954 to the same tags previously set > tags 957954 + pending Bug #957954 [src:wmwave] wmwave: ftbfs with GCC-10 Added tag(s) pending. -- 957954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957954 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: webalizer: diff for NMU version 2.23.08-3.2
Processing control commands: > tags 957923 + patch Bug #957923 [src:webalizer] webalizer: ftbfs with GCC-10 Ignoring request to alter tags of bug #957923 to the same tags previously set > tags 957923 + pending Bug #957923 [src:webalizer] webalizer: ftbfs with GCC-10 Added tag(s) pending. -- 957923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957923 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957923: webalizer: diff for NMU version 2.23.08-3.2
Control: tags 957923 + patch Control: tags 957923 + pending Dear maintainer, I've prepared an NMU for webalizer (versioned as 2.23.08-3.2) and uploaded it to DELAYED/7. Please feel free to tell me if I should delay it longer or cancel the NMU. Regards. diff -Nru webalizer-2.23.08/debian/changelog webalizer-2.23.08/debian/changelog --- webalizer-2.23.08/debian/changelog 2018-10-15 15:03:02.0 + +++ webalizer-2.23.08/debian/changelog 2021-02-12 21:04:51.0 + @@ -1,3 +1,11 @@ +webalizer (2.23.08-3.2) unstable; urgency=medium + + * Non-maintainer upload. + * Add debian/patches/27_fix_compilation_with_gcc-10.diff. +Thanks to Logan Rosen . (Closes: #957923) + + -- Francisco Vilmar Cardoso Ruviaro Fri, 12 Feb 2021 21:04:51 + + webalizer (2.23.08-3.1) unstable; urgency=medium * Non-maintainer upload with maintainer consent. diff -Nru webalizer-2.23.08/debian/patches/27_fix_compilation_with_gcc-10.diff webalizer-2.23.08/debian/patches/27_fix_compilation_with_gcc-10.diff --- webalizer-2.23.08/debian/patches/27_fix_compilation_with_gcc-10.diff 1970-01-01 00:00:00.0 + +++ webalizer-2.23.08/debian/patches/27_fix_compilation_with_gcc-10.diff 2021-02-12 20:58:29.0 + @@ -0,0 +1,25 @@ +Description: Fix compilation with GCC 10. +Author: Logan Rosen +Bug-Debian: https://bugs.debian.org/957923 +Forwarded: no +Reviewed-By: Francisco Vilmar Cardoso Ruviaro +Last-Update: 2021-02-12 + +--- a/dns_resolv.c b/dns_resolv.c +@@ -78,11 +78,11 @@ + + struct dns_child child[MAXCHILD];/* DNS child pipe data */ + +-DNODEPTR host_table[MAXHASH]; /* hostname/ip hash table */ ++extern DNODEPTR host_table[MAXHASH]; /* hostname/ip hash table */ + +-char buffer[BUFSIZE]; /* log file record buffer */ +-char tmp_buf[BUFSIZE]; /* used to temp save above */ +-struct utsname system_info; /* system info structure*/ ++extern char buffer[BUFSIZE]; /* log file record buffer */ ++extern char tmp_buf[BUFSIZE]; /* used to temp save above */ ++extern struct utsname system_info; /* system info structure*/ + + int raiseSigChild = 1; + diff -Nru webalizer-2.23.08/debian/patches/series webalizer-2.23.08/debian/patches/series --- webalizer-2.23.08/debian/patches/series 2018-10-15 15:03:02.0 + +++ webalizer-2.23.08/debian/patches/series 2021-02-12 21:01:24.0 + @@ -15,3 +15,4 @@ 24_gettext_generated.diff 25_add_convertlang2po.diff 26_gettext_po_files.diff +27_fix_compilation_with_gcc-10.diff -- Francisco Vilmar Cardoso Ruviaro 4096R: 1B8C F656 EF3B 8447 2F48 F0E7 82FB F706 0B2F 7D00 diff -Nru webalizer-2.23.08/debian/changelog webalizer-2.23.08/debian/changelog --- webalizer-2.23.08/debian/changelog 2018-10-15 15:03:02.0 + +++ webalizer-2.23.08/debian/changelog 2021-02-12 21:04:51.0 + @@ -1,3 +1,11 @@ +webalizer (2.23.08-3.2) unstable; urgency=medium + + * Non-maintainer upload. + * Add debian/patches/27_fix_compilation_with_gcc-10.diff. +Thanks to Logan Rosen . (Closes: #957923) + + -- Francisco Vilmar Cardoso Ruviaro Fri, 12 Feb 2021 21:04:51 + + webalizer (2.23.08-3.1) unstable; urgency=medium * Non-maintainer upload with maintainer consent. diff -Nru webalizer-2.23.08/debian/patches/27_fix_compilation_with_gcc-10.diff webalizer-2.23.08/debian/patches/27_fix_compilation_with_gcc-10.diff --- webalizer-2.23.08/debian/patches/27_fix_compilation_with_gcc-10.diff 1970-01-01 00:00:00.0 + +++ webalizer-2.23.08/debian/patches/27_fix_compilation_with_gcc-10.diff 2021-02-12 20:58:29.0 + @@ -0,0 +1,25 @@ +Description: Fix compilation with GCC 10. +Author: Logan Rosen +Bug-Debian: https://bugs.debian.org/957923 +Forwarded: no +Reviewed-By: Francisco Vilmar Cardoso Ruviaro +Last-Update: 2021-02-12 + +--- a/dns_resolv.c b/dns_resolv.c +@@ -78,11 +78,11 @@ + + struct dns_child child[MAXCHILD];/* DNS child pipe data */ + +-DNODEPTR host_table[MAXHASH]; /* hostname/ip hash table */ ++extern DNODEPTR host_table[MAXHASH]; /* hostname/ip hash table */ + +-char buffer[BUFSIZE]; /* log file record buffer */ +-char tmp_buf[BUFSIZE]; /* used to temp save above */ +-struct utsname system_info; /* system info structure*/ ++extern char buffer[BUFSIZE]; /* log file record buffer */ ++extern char tmp_buf[BUFSIZE]; /* used to temp save above */ ++extern struct utsname system_info; /* system info structure*/ + + int raiseSigChild = 1; + diff -Nru webalizer-2.23.08/debian/patches/series webalizer-2.23.08/debian/patches/series --- webalizer-2.23.08/debian/patches/series 2018-10-15
Bug#983206: [libupnp13] Please update for CVE-2020-12695 & fixes
With bullseye now released, can we please now progress with the necessary transition to upgrade and thus address the security issue?
Bug#995272: libsql-abstract-pg-perl: trying to overwrite '/usr/share/man/man3/SQL::Abstract::Pg.3pm.gz', which is also in package libmojo-pg-perl 4.24-1
Package: libsql-abstract-pg-perl,libmojo-pg-perl Severity: serious Version: libsql-abstract-pg-perl/1.0-1 Version: libmojo-pg-perl/4.24-1 Trying to install libsql-abstract-pg-perl when libmojo-pg-perl is already installed results in a file conflict as follows: Preparing to unpack .../libsql-abstract-pg-perl_1.0-1_all.deb ... Unpacking libsql-abstract-pg-perl (1.0-1) ... dpkg: error processing archive /var/cache/apt/archives/libsql-abstract-pg-perl_1.0-1_all.deb (--unpack): trying to overwrite '/usr/share/man/man3/SQL::Abstract::Pg.3pm.gz', which is also in package libmojo-pg-perl 4.24-1 Errors were encountered while processing: /var/cache/apt/archives/libsql-abstract-pg-perl_1.0-1_all.deb I'm not sure if it is intentional that both packages ship the same file(s) and how they relate to each other (as libsql-abstract-pg-perl mentions libmojo-pg-perl in its package description), so I'm not sure what's the right way to solve this. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.13.0-trunk-amd64 (SMP w/4 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled
Bug#994971: OpenCL not working with latest Nvidia driver
On 2021-09-26 18:58:48 +0200, Andreas Beckmann wrote: > Control: severity -1 serious > > On 26/09/2021 18.07, Klaus Ethgen wrote: > > > available somewhere in /var/log/apt/term.log*, it might give some hints > > > what > > > happened. > > > > Here it is. > > Thanks. You had modifications in nvidia-modprobe.conf, didn't try that > before. And dpkg messed it up. I could reproduce the disappearance of the > file. Will try to reproduce with a conffile outside nvidia stuff... This smells like #994919 in debhelper, i.e, nvidia-driver needs to be rebuilt with a fixed debhelper version. Cheers > > > By the way, make it sense to include all involved persons in reply? > > Doesn't the bugtracker send notification too? > > Only the maintainer gets notifications by default, everyone else has to > subscribe manually. So let's keep the Cc:s. > > Andreas > -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#994567: marked as done (black: autopkgtest regression: ModuleNotFoundError: No module named 'aiohttp_cors')
Your message dated Tue, 28 Sep 2021 21:20:47 + with message-id and subject line Bug#994567: fixed in black 21.4b2-2 has caused the Debian Bug report #994567, regarding black: autopkgtest regression: ModuleNotFoundError: No module named 'aiohttp_cors' 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.) -- 994567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994567 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: black Version: 21.4b2-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of black the autopkgtest of black fails in testing on amd64 when that autopkgtest is run with the binary packages of black from unstable. It passes when run with only packages from testing. In tabular form: passfail black from testing21.4b2-1 all others from testingfrom testing I copied some of the output at the bottom of this report, are you missing (test) dependencies? On top of fixing amd64, can you please stop "PASSING" on the other architectures? If you can't test there, please use the (relatively new) Architecture [0] field in the autopkgtest control file to skip testing on those architectures, or add the skippable restriction and exit with code 77. 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] https://salsa.debian.org/ci-team/autopkgtest/-/raw/master/doc/README.package-tests.rst [1] https://qa.debian.org/excuses.php?package=black https://ci.debian.net/data/autopkgtest/testing/amd64/b/black/15301566/log.gz ERRORS ERROR collecting tests/test_blackd.py _ /usr/lib/python3/dist-packages/blackd/__init__.py:12: in import aiohttp_cors E ModuleNotFoundError: No module named 'aiohttp_cors' During handling of the above exception, another exception occurred: tests/test_blackd.py:10: in import blackd /usr/lib/python3/dist-packages/blackd/__init__.py:20: in sys.exit(-1) E SystemExit: -1 --- Captured stderr aiohttp dependency is not installed: No module named 'aiohttp_cors'. Please re-install black with the '[d]' extra install to obtain aiohttp_cors: `pip install black[d]` ERROR collecting tests/test_format.py _ ImportError while importing test module '/tmp/autopkgtest-lxc.nc2rafez/downtmp/autopkgtest_tmp/tests/test_format.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: /usr/lib/python3.9/importlib/__init__.py:127: in import_module return _bootstrap._gcd_import(name[level:], package, level) tests/test_format.py:4: in from parameterized import parameterized E ModuleNotFoundError: No module named 'parameterized' === short test summary info ERROR tests/test_blackd.py - SystemExit: -1 ERROR tests/test_format.py !!! Interrupted: 2 errors during collection === 1 deselected, 2 errors in 0.44s autopkgtest [03:10:26]: test testsuite: ---] OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: black Source-Version: 21.4b2-2 Done: Antonio Terceiro We believe that the bug you reported is fixed in the latest version of black, 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 994...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antonio Terceiro (supplier of updated black 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: Tue, 28 Sep 2021 18:02:01 -0300 Source: black Architecture: source Version: 21.4b2-2 Distribution: unstable
Bug#981699: fixed in thinkfan 1.2.1-3.1
Debian FTP Masters dixit: > * Don't ship an example config in /etc/thinkfan.yaml (Closes: #983727) > * Ship example config in /usr/share/doc/thinkfan/examples/ I don’t think these resolve my issue with the newer thinkfan releases. I’ve looked at the example configuration, and it refers to multiple hwmon and other files, which caused problems with my laptop. With the older thinkfan release, my configuration literally consisted of only the temperatures, nothing else, and it worked (Thinkpad X61), and the new configuration file doesn’t have a “user’s PoV” documentation for how to achieve an at-all working configuration. bye, //mirabilos -- /⁀\ The UTF-8 Ribbon ╲ ╱ Campaign against ╳ HTML eMail! Also, ╱ ╲ header encryption!
Processed: Re: Bug#995223: libffi: SIGILL on powerpc and ppc64 systems since libffi8
Processing control commands: > severity -1 serious Bug #995223 [src:libffi] libffi: SIGILL on powerpc and ppc64 systems since libffi8 Severity set to 'serious' from 'important' -- 995223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995223 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 995051 is important
Processing commands for cont...@bugs.debian.org: > # only times out on some buildds > severity 995051 important Bug #995051 [src:python3.9] python3.9: FTBFS on i386: test timeout Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 995051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995051 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 995175
Processing commands for cont...@bugs.debian.org: > tags 995175 + upstream fixed-upstream Bug #995175 [src:request-tracker4] request-tracker4: CVE-2021-38562 Added tag(s) upstream and fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 995175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995175 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#981699: marked as done (thinkfan: fails on upgrade)
Your message dated Tue, 28 Sep 2021 17:19:44 + with message-id and subject line Bug#981699: fixed in thinkfan 1.2.1-3.1 has caused the Debian Bug report #981699, regarding thinkfan: fails on upgrade 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.) -- 981699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981699 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: thinkfan Version: 1.2.1-2 Severity: normal X-Debbugs-Cc: t...@mirbsd.de $ sudo apt-get --purge dist-upgrade […] Preparing to unpack .../thinkfan_1.2.1-2_amd64.deb ... Unpacking thinkfan (1.2.1-2) over (1.2.1-1) ... dpkg: warning: unable to delete old directory '/etc/systemd/system/thinkfan.service.d': Directory not empty […] Setting up thinkfan (1.2.1-2) ... Removing obsolete conffile /etc/systemd/system/thinkfan.service.d/override.conf ... Restarting fan control tool: thinkfan ERROR: Error scanning /sys/devices/pci:00/:00:03.1/:27:00.0/hwmon: No such file or directory failed! […] -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'oldstable-updates'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-4-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) Versions of packages thinkfan depends on: ii init-system-helpers 1.60 ii libatasmart4 0.19-5 ii libc62.31-9 ii libgcc-s110.2.1-6 ii libstdc++6 10.2.1-6 ii libyaml-cpp0.6 0.6.3-9 thinkfan recommends no packages. thinkfan suggests no packages. -- Configuration Files: /etc/default/thinkfan changed: START=yes DAEMON_ARGS="-q" /etc/thinkfan.conf changed: (0, 0, 58) (1, 47, 60) (2, 55, 66) (5, 60, 77) (7, 70, 32767) -- no debconf information --- End Message --- --- Begin Message --- Source: thinkfan Source-Version: 1.2.1-3.1 Done: Lee Garrett We believe that the bug you reported is fixed in the latest version of thinkfan, 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 981...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lee Garrett (supplier of updated thinkfan 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: Tue, 28 Sep 2021 19:06:21 CEST Source: thinkfan Binary: Architecture: source Version: 1.2.1-3.1 Distribution: unstable Urgency: medium Maintainer: Evgeni Golov Changed-By: Lee Garrett Description: Closes: 981699 983727 Changes: thinkfan (1.2.1-3.1) unstable; urgency=medium . * Non-maintainer upload. * Don't ship an example config in /etc/thinkfan.yaml (Closes: #983727) * Don't fail startup by installing broken config (Closes: #981699) * Ship example config in /usr/share/doc/thinkfan/examples/ Checksums-Sha256: 569f4c987773cd207065835d6fd19160283e6e30943c000e9aad0c8f7ed0dc10 2018 thinkfan_1.2.1-3.1.dsc f5b8fed06323b330cb6e0bf288241656f2943ef87e17996ca300cbd97a6fecda 7936 thinkfan_1.2.1-3.1.debian.tar.xz a9ca636a57c4dff92c25982af7cf51dbaae8ea09b5d835316fe1736bd14ac56e 7529 thinkfan_1.2.1-3.1_sourceonly.buildinfo Checksums-Sha1: 3570a807568ae501821ee7db7481b4fe8cac20aa 2018 thinkfan_1.2.1-3.1.dsc 2ec71dd379485bdf774b572b4dbb629afe70b961 7936 thinkfan_1.2.1-3.1.debian.tar.xz a57457f0b408f58745088d1343f5e8d6b42f74b8 7529 thinkfan_1.2.1-3.1_sourceonly.buildinfo Files: ba1e3ee9e9101a96f41dafa186615858 2018 misc optional thinkfan_1.2.1-3.1.dsc ccdbcff021ba152811b8a37b57eec099 7936 misc optional thinkfan_1.2.1-3.1.debian.tar.xz dad692f9188e7b54c41e52deb48ec9e8 7529 - - thinkfan_1.2.1-3.1_sourceonly.buildinfo -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmFTS45fFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgauyRAAxSjJWUUdkkC5Sf2MUw05FA6yw52WxenJnFJe3eQomYPN8SW9o7gvcWnu
Bug#983727: marked as done (thinkfan should not ship an example in /etc/thinkfan.yaml)
Your message dated Tue, 28 Sep 2021 17:19:44 + with message-id and subject line Bug#983727: fixed in thinkfan 1.2.1-3.1 has caused the Debian Bug report #983727, regarding thinkfan should not ship an example in /etc/thinkfan.yaml 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.) -- 983727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983727 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: thinkfan Version: 1.2.1-3 Severity: serious The “thinkfan Example Config File” currently shipped as /etc/thinkfan.yaml “is NOT a working config file that can just be copied” (quotes from the file itself). Pretending that “The new default configuration might not work for your system” in NEWS.Debian implies that it could work in some cases, but that does not seem to be the case at all. By installing /etc/thinkfan.yaml on systems with a working configuration in /etc/thinkfan.conf, the daemon simply fails to start (while simply removing the new /etc/thinkfan.yaml allow one to start it again). Please, ship the “thinkfan Example Config File” in /usr/share/doc/thinkfan/examples in order to not break existing configuration, especially since it can’t work as is anyway. Regards David signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: thinkfan Source-Version: 1.2.1-3.1 Done: Lee Garrett We believe that the bug you reported is fixed in the latest version of thinkfan, 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 983...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lee Garrett (supplier of updated thinkfan 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: Tue, 28 Sep 2021 19:06:21 CEST Source: thinkfan Binary: Architecture: source Version: 1.2.1-3.1 Distribution: unstable Urgency: medium Maintainer: Evgeni Golov Changed-By: Lee Garrett Description: Closes: 981699 983727 Changes: thinkfan (1.2.1-3.1) unstable; urgency=medium . * Non-maintainer upload. * Don't ship an example config in /etc/thinkfan.yaml (Closes: #983727) * Don't fail startup by installing broken config (Closes: #981699) * Ship example config in /usr/share/doc/thinkfan/examples/ Checksums-Sha256: 569f4c987773cd207065835d6fd19160283e6e30943c000e9aad0c8f7ed0dc10 2018 thinkfan_1.2.1-3.1.dsc f5b8fed06323b330cb6e0bf288241656f2943ef87e17996ca300cbd97a6fecda 7936 thinkfan_1.2.1-3.1.debian.tar.xz a9ca636a57c4dff92c25982af7cf51dbaae8ea09b5d835316fe1736bd14ac56e 7529 thinkfan_1.2.1-3.1_sourceonly.buildinfo Checksums-Sha1: 3570a807568ae501821ee7db7481b4fe8cac20aa 2018 thinkfan_1.2.1-3.1.dsc 2ec71dd379485bdf774b572b4dbb629afe70b961 7936 thinkfan_1.2.1-3.1.debian.tar.xz a57457f0b408f58745088d1343f5e8d6b42f74b8 7529 thinkfan_1.2.1-3.1_sourceonly.buildinfo Files: ba1e3ee9e9101a96f41dafa186615858 2018 misc optional thinkfan_1.2.1-3.1.dsc ccdbcff021ba152811b8a37b57eec099 7936 misc optional thinkfan_1.2.1-3.1.debian.tar.xz dad692f9188e7b54c41e52deb48ec9e8 7529 - - thinkfan_1.2.1-3.1_sourceonly.buildinfo -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmFTS45fFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgauyRAAxSjJWUUdkkC5Sf2MUw05FA6yw52WxenJnFJe3eQomYPN8SW9o7gvcWnu mYj8b0H+tL22kwDNlAwqGdeuf0Hmg7p8z8+6oVBqDkxxIuNSQ+P7RcRlrhyrbzfP oWdSSaI7vzB42sTkzop+2acldKeEzQs6EgXmGs5CUBwHee5zpbfRmF4Dl8WVPaDk 9jQo35KX/DgC6dPl4ZkUE6Qsooe0SSO4RegI0g1QqXIfbYy3ZoW4cBq5BgZSG1vf 10DZw7ipQxopTECeAE6Qio9gku19yyoxsWTtj3uHlRdRpLQFzsaXMmJ089bdHbRR QqWUT10lz1Ahg3gmSzk+l7nazBlfr+9tr4D7mveYxc6U+R9HiIuLkyJ0Fmzw/xc1 7rydTNH3FokXPmXPY/jzQ6sE/kgpE9j2UiEeg0NyOgsLQTgeZaYIL878+7N4cu4Y KCvfQgm5MrvybPfyw+ZbFN1/8vbFsC+XDemk9/yU4akfB+MzgdLbckDRrkugDNpS fu4B2xU+tCPGIaB7dNMDSP3aB4W/VnJcT7Jq3Z86kO2u2iK3+W63KCZIEyNM69dK 5u5z3kSNINs9k++Hha1Uem8m9zQz6+Vnxx7/ILQHvA6C7VscgHb2bA3RC8Fzs6Qb W+lYzpVax/eKahlFfLYDYe2+STj1CTd0HXnfFrY1B0h9ONbMypo= =aAhi -END PGP SIGNATURE End Message ---
Bug#995266: openmpi: binary-all FTBFS
Source: openmpi Version: 4.1.2~rc1-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=openmpi=all=4.1.2~rc1-3=1632846883=0 ... dh_missing -i dh_missing: warning: usr/share/doc/openmpi/javadoc-openmpi/allclasses-index.html exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/share/doc/openmpi/javadoc-openmpi/allclasses.html exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/share/doc/openmpi/javadoc-openmpi/allpackages-index.html exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/share/doc/openmpi/javadoc-openmpi/constant-values.html exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/share/doc/openmpi/javadoc-openmpi/deprecated-list.html exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/share/doc/openmpi/javadoc-openmpi/element-list exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/share/doc/openmpi/javadoc-openmpi/help-doc.html exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/share/doc/openmpi/javadoc-openmpi/index-all.html exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/share/doc/openmpi/javadoc-openmpi/index.html exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/share/doc/openmpi/javadoc-openmpi/jquery/external/jquery/jquery.js exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/share/doc/openmpi/javadoc-openmpi/jquery/images/ui-bg_glass_55_fbf9ee_1x400.png exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/share/doc/openmpi/javadoc-openmpi/jquery/images/ui-bg_glass_65_dadada_1x400.png exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/share/doc/openmpi/javadoc-openmpi/jquery/images/ui-bg_glass_75_dadada_1x400.png exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/share/doc/openmpi/javadoc-openmpi/jquery/images/ui-bg_glass_75_e6e6e6_1x400.png exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/share/doc/openmpi/javadoc-openmpi/jquery/images/ui-bg_glass_95_fef1ec_1x400.png exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/share/doc/openmpi/javadoc-openmpi/jquery/images/ui-bg_highlight-soft_75_cc_1x100.png exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/share/doc/openmpi/javadoc-openmpi/jquery/images/ui-icons_22_256x240.png exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/share/doc/openmpi/javadoc-openmpi/jquery/images/ui-icons_2e83ff_256x240.png exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/share/doc/openmpi/javadoc-openmpi/jquery/images/ui-icons_454545_256x240.png exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/share/doc/openmpi/javadoc-openmpi/jquery/images/ui-icons_88_256x240.png exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/share/doc/openmpi/javadoc-openmpi/jquery/images/ui-icons_cd0a0a_256x240.png exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/share/doc/openmpi/javadoc-openmpi/jquery/jquery-3.5.1.js exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/share/doc/openmpi/javadoc-openmpi/jquery/jquery-ui.css exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/share/doc/openmpi/javadoc-openmpi/jquery/jquery-ui.js exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/share/doc/openmpi/javadoc-openmpi/jquery/jquery-ui.min.css exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/share/doc/openmpi/javadoc-openmpi/jquery/jquery-ui.min.js exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/share/doc/openmpi/javadoc-openmpi/jquery/jquery-ui.structure.css exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/share/doc/openmpi/javadoc-openmpi/jquery/jquery-ui.structure.min.css exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/share/doc/openmpi/javadoc-openmpi/jquery/jszip-utils/dist/jszip-utils-ie.js exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/share/doc/openmpi/javadoc-openmpi/jquery/jszip-utils/dist/jszip-utils-ie.min.js exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/share/doc/openmpi/javadoc-openmpi/jquery/jszip-utils/dist/jszip-utils.js exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/share/doc/openmpi/javadoc-openmpi/jquery/jszip-utils/dist/jszip-utils.min.js exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/share/doc/openmpi/javadoc-openmpi/jquery/jszip/dist/jszip.js
Bug#995260: closed by Vincent Blut (Re: Bug#995260: chrony: Mismatched filename for UNIX socket between client and daemon)
so why did it not use the Unix socket but fell back to 127.0.0.1 approach? i wonder what happens if i do ‘cmddeny all’?
Bug#995260: marked as done (chrony: Mismatched filename for UNIX socket between client and daemon)
Your message dated Tue, 28 Sep 2021 18:59:37 +0200
with message-id
and subject line Re: Bug#995260: chrony: Mismatched filename for UNIX socket
between client and daemon
has caused the Debian Bug report #995260,
regarding chrony: Mismatched filename for UNIX socket between client and daemon
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.)
--
995260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995260
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chrony
Version: 4.0-8
Severity: grave
Tags: upstream
Justification: renders package unusable
X-Debbugs-Cc: s.egb...@sbcglobal.net
Dear Maintainer,
The filename construct for a UNIX socket to be shared
between the Chrony (chronyd) daemon and its Chrony CLI (chronyc) client
admin tool are not in sync, as client's UNIX filename uses a PID value
whereas server's UNIX filename does not use PID value.
This appears to be a Debian-only issue.
Fired up its daemon and doubled checked that a UNIX socket was made:
$ ls -1 /run/chrony
chrony.sock
chrony.pid
Execute the client and no successful UNIX socket opened.
Using List Open File (lsof) tool, I show the daemon's opened files:
COMMAND PID USER FD TYPE NODE NAME
chronyd 3597 _chrony3u unix 0x \
type=DGRAM
chronyd 3597 _chrony5u IPv4 UDP 127.0.0.1:323
chronyd 3597 _chrony6u IPv6 UDP [::1]:323
chronyd 3597 _chrony7u unix 0x \
/run/chrony/chronyd.sock type=DGRAM
chronyd 3597 _chrony8u unix 0x type=SEQPACKET
chronyc 3809johnd3u IPv4 UDP \
127.0.0.1:33911->127.0.0.1:323
No socket in the dispatcher part of the daemon, now to check the other
forked part of the daemon used to carry on the connection with
its chronyc client, same 'lsof' output.
COMMAND PID USER FD TYPE NODE NAME
chronyd 3597 _chrony5u IPv4 UDP 127.0.0.1:323
chronyd 3597 _chrony6u IPv6 UDP [::1]:323
chronyd 3598 _chrony9u unix 0x type=SEQPACKET
chronyc 3809johnd3u IPv4 UDP \
127.0.0.1:33911->127.0.0.1:323
Appears that client failed socket open and fell back to a
different approach which is using an IP loopback address.
Investigated why socket open failed... by using 'strace -f chrony[c|d]'.
For the chronyd v4.0 having opened a Debian-tweaked '/run/chrony/chrony.sock',
I show the corresponding chronyc v4.0 version:
$ chronyc -v
chronyc (chrony) version 4.0 (+READLINE +SECHASH +IPV6 -DEBUG)
And ran strace against this v4.0 client and grep'd for 'sock' word pattern:
$ strace -f /usr/bin/chronyc
socket(AF_UNIX, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
unlink("/run/chrony/chronyc.3875.sock") = -1 EACCES (Permission denied)
bind(3, {sa_family=AF_UNIX, sun_path="/run/chrony/chronyc.3875.sock"}, 110)
= -1 EACCES (Permission denied)
getsockname(3, {sa_family=AF_UNIX}, [112->2]) = 0
close(3)= 0
socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 3
connect(3, {sa_family=AF_INET, sin_port=htons(323),
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
Noticed the 'PID' number being inserted into the
'/run/chrony/chronyc.3875.sock'?
This is the chronyc client doing "PID-sock" filenaming convention, whereas
its daemon is doing a different "just-sock" filenaming convention.
The v4.1 client does exactly the same.
chronyc (chrony) version DEVELOPMENT (-READLINE -SECHASH +IPV6 +DEBUG)
socket(AF_UNIX, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
unlink("/var/run/chrony/chronyc.3885.sock") = -1 EACCES (Permission denied)
bind(3, {sa_family=AF_UNIX, sun_path="/var/run/chrony/chronyc.3885.sock"},
110) = -1 EACCES (Permission denied)
getsockname(3, {sa_family=AF_UNIX}, [112->2]) = 0
close(3)= 0
socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 3
connect(3, {sa_family=AF_INET, sin_port=htons(323),
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
fstat(0, {st_mode=S_IFCHR|0620, st_rdev=makedev(0x88, 0), ...}) = 0
read(0, ^Cstrace: Process 3885 detached
It would be nice to use consistent filenaming convention for the UNIX socket
for both client and daemon.
-- System Information:
Debian Release: 11.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500,
Bug#995260: chrony: Mismatched filename for UNIX socket between client and daemon
Hi,
Le 2021-09-28 11:55, Steve Egbert a écrit :
> Package: chrony
> Version: 4.0-8
> Severity: grave
> Tags: upstream
> Justification: renders package unusable
> X-Debbugs-Cc: s.egb...@sbcglobal.net
>
> Dear Maintainer,
>
>
> The filename construct for a UNIX socket to be shared
> between the Chrony (chronyd) daemon and its Chrony CLI (chronyc) client
> admin tool are not in sync, as client's UNIX filename uses a PID value
> whereas server's UNIX filename does not use PID value.
>
> This appears to be a Debian-only issue.
What makes you think that this issue, if at all, is specific to Debian?
> Fired up its daemon and doubled checked that a UNIX socket was made:
>
> $ ls -1 /run/chrony
> chrony.sock
> chrony.pid
chrony in Debian will create by default the chronyd.{pid,sock} files. The
above shows that you are tweaked chronyd's configuration. What changes did you
make?
> Execute the client and no successful UNIX socket opened.
>
> Using List Open File (lsof) tool, I show the daemon's opened files:
>
> COMMAND PID USER FD TYPE NODE NAME
>
> chronyd 3597 _chrony3u unix 0x \
> type=DGRAM
> chronyd 3597 _chrony5u IPv4 UDP 127.0.0.1:323
> chronyd 3597 _chrony6u IPv6 UDP [::1]:323
> chronyd 3597 _chrony7u unix 0x \
> /run/chrony/chronyd.sock type=DGRAM
> chronyd 3597 _chrony8u unix 0x type=SEQPACKET
> chronyc 3809johnd3u IPv4 UDP \
> 127.0.0.1:33911->127.0.0.1:323
>
> No socket in the dispatcher part of the daemon, now to check the other
> forked part of the daemon used to carry on the connection with
> its chronyc client, same 'lsof' output.
>
> COMMAND PID USER FD TYPE NODE NAME
>
> chronyd 3597 _chrony5u IPv4 UDP 127.0.0.1:323
> chronyd 3597 _chrony6u IPv6 UDP [::1]:323
> chronyd 3598 _chrony9u unix 0x type=SEQPACKET
> chronyc 3809johnd3u IPv4 UDP \
> 127.0.0.1:33911->127.0.0.1:323
>
> Appears that client failed socket open and fell back to a
> different approach which is using an IP loopback address.
>
> Investigated why socket open failed... by using 'strace -f chrony[c|d]'.
>
> For the chronyd v4.0 having opened a Debian-tweaked '/run/chrony/chrony.sock',
> I show the corresponding chronyc v4.0 version:
>
> $ chronyc -v
> chronyc (chrony) version 4.0 (+READLINE +SECHASH +IPV6 -DEBUG)
>
> And ran strace against this v4.0 client and grep'd for 'sock' word pattern:
>
> $ strace -f /usr/bin/chronyc
> socket(AF_UNIX, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
> unlink("/run/chrony/chronyc.3875.sock") = -1 EACCES (Permission denied)
>
> bind(3, {sa_family=AF_UNIX, sun_path="/run/chrony/chronyc.3875.sock"},
> 110) = -1 EACCES (Permission denied)
> getsockname(3, {sa_family=AF_UNIX}, [112->2]) = 0
> close(3)= 0
>
> socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 3
> connect(3, {sa_family=AF_INET, sin_port=htons(323),
> sin_addr=inet_addr("127.0.0.1")}, 16) = 0
>
> Noticed the 'PID' number being inserted into the
> '/run/chrony/chronyc.3875.sock'?
> This is the chronyc client doing "PID-sock" filenaming convention, whereas
> its daemon is doing a different "just-sock" filenaming convention.
The PID is included to have the ability to run multiple chronyc instances at
the same time. Nothing wrong with that.
> The v4.1 client does exactly the same.
>
> chronyc (chrony) version DEVELOPMENT (-READLINE -SECHASH +IPV6 +DEBUG)
>
> socket(AF_UNIX, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
> unlink("/var/run/chrony/chronyc.3885.sock") = -1 EACCES (Permission
> denied)
>
> bind(3, {sa_family=AF_UNIX,
> sun_path="/var/run/chrony/chronyc.3885.sock"}, 110) = -1 EACCES (Permission
> denied)
> getsockname(3, {sa_family=AF_UNIX}, [112->2]) = 0
> close(3)= 0
>
> socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 3
> connect(3, {sa_family=AF_INET, sin_port=htons(323),
> sin_addr=inet_addr("127.0.0.1")}, 16) = 0
> fstat(0, {st_mode=S_IFCHR|0620, st_rdev=makedev(0x88, 0), ...}) = 0
> read(0, ^Cstrace: Process 3885 detached
>
>
> It would be nice to use consistent filenaming convention for the UNIX socket
> for both client and daemon.
Cheers,
Vincent
signature.asc
Description: PGP signature
Bug#995263: user-mode-linux: build-depends on removed package.
Source: user-mode-linux Version: 5.10um3 Severity: serious Justification: rc policy - "Packages must be buildable within the same release." Tags: bookworm, sid user-mode-linux build-depends on linux-source-5.10 which is no longer built by the linux source package. It is still present in unstable as a cruft package but is completely gone from testing.
Bug#995150: marked as done (openmpi: segfault in mca_io_romio_dist_MPI_File_iwrite_all)
Your message dated Tue, 28 Sep 2021 16:08:06 + with message-id and subject line Bug#995150: fixed in openmpi 4.1.2~rc1-3 has caused the Debian Bug report #995150, regarding openmpi: segfault in mca_io_romio_dist_MPI_File_iwrite_all 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.) -- 995150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995150 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openmpi Version: 4.1.2~rc1-2 Severity: serious Justification: FTBFS The new version of openmpi seems to be segfaulting in mca_io_romio321.so The segfault is found in nearly all arches in mpi4py tests, https://buildd.debian.org/status/package.php?p=mpi4py (it causes mpi4py to FTBFS) The crash is bad enough that most arches are not able to provide a backtrace, although some arches reference libpthread.so.0 (which could suggest instability from the libc6 2.32 transition) ppc64el and ia64 however provide a full backtrace, both pointing at mca_io_romio321.so (MPIOI_File_iwrite_all) >From ppc64el https://buildd.debian.org/status/fetch.php?pkg=mpi4py=ppc64el=3.1.1-8=1632692000=0 testIReadIWrite (test_io.TestIOSelf) ... ok testIReadIWriteAll (test_io.TestIOSelf) ... [ppc64el-osuosl-01:1381766] *** Process received signal *** [ppc64el-osuosl-01:1381766] Signal: Segmentation fault (11) [ppc64el-osuosl-01:1381766] Signal code: Address not mapped (1) [ppc64el-osuosl-01:1381766] Failing at address: (nil) [ppc64el-osuosl-01:1381766] [ 0] linux-vdso64.so.1(__kernel_sigtramp_rt64+0x0)[0x7fff92ec0514] [ppc64el-osuosl-01:1381766] [ 1] [0x0] [ppc64el-osuosl-01:1381766] [ 2] /usr/lib/powerpc64le-linux-gnu/openmpi/lib/openmpi3/mca_io_romio321.so(mca_io_romio_dist_MPI_File_iwrite_all+0x38)[0x7fff831135e8] [ppc64el-osuosl-01:1381766] [ 3] /usr/lib/powerpc64le-linux-gnu/openmpi/lib/openmpi3/mca_io_romio321.so(mca_io_romio321_file_iwrite_all+0xa8)[0x7fff831100f8] [ppc64el-osuosl-01:1381766] [ 4] /usr/lib/powerpc64le-linux-gnu/libmpi.so.40(PMPI_File_iwrite_all+0x100)[0x7fff9221e890] [ppc64el-osuosl-01:1381766] [ 5] /<>/.pybuild/cpython3_3.9/build/mpi4py/MPI.cpython-39-powerpc64le-linux-gnu.so(+0x12b654)[0x7fff9245b654] [ppc64el-osuosl-01:1381766] [ 6] /usr/bin/python3.9[0x100f9e84] [ppc64el-osuosl-01:1381766] [ 7] /usr/bin/python3.9(_PyEval_EvalFrameDefault+0xa9c)[0x100d2a6c] [ppc64el-osuosl-01:1381766] [ 8] /usr/bin/python3.9(_PyFunction_Vectorcall+0x20c)[0x100f631c] --- End Message --- --- Begin Message --- Source: openmpi Source-Version: 4.1.2~rc1-3 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of openmpi, 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. Alastair McKinstry (supplier of updated openmpi 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: Tue, 28 Sep 2021 08:11:18 +0100 Source: openmpi Architecture: source Version: 4.1.2~rc1-3 Distribution: unstable Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Closes: 995150 Changes: openmpi (4.1.2~rc1-3) unstable; urgency=medium . * Update versions: - libmca_common_ompio.so 41.29.1 -> 41.29.2 - libmca_common_ofi.so 10.0.1 -> 10.0.2 Closes: #995150 * Add autopkg test for unlinked shared libs * Add alpha, ppc64, sparc64 to the 'nojava' arch list * Only install javadocs via d/rules inside conditional Checksums-Sha1: 4a9d09b14cb6889c1d92717a496519833c2a9950 2771 openmpi_4.1.2~rc1-3.dsc 0b32e211bd171989baad1ef3c1e9ab05067da0f3 68460 openmpi_4.1.2~rc1-3.debian.tar.xz Checksums-Sha256: c62370de7ce3d71d329723a214a5b03fc9f2b9ddfa64eceb3b02ab73f14f437d 2771 openmpi_4.1.2~rc1-3.dsc d3e4b00052213e0b95a44add1fc7daa4a9503ad48ba2850ec6e2e421661867cc 68460 openmpi_4.1.2~rc1-3.debian.tar.xz Files: e81fb378b880761388b8737614e0d8ad 2771 net optional openmpi_4.1.2~rc1-3.dsc cdcbfde15c50a31b3bdabb74bc77adcc 68460 net optional openmpi_4.1.2~rc1-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmFTOb4ACgkQy+a7Tl2a
Processed: fixed 995215 in 0.31.1-2
Processing commands for cont...@bugs.debian.org: > fixed 995215 0.31.1-2 Bug #995215 [postgresql-semver] postgresql-semver: Wait for acceptance of backport There is no source info for the package 'postgresql-semver' at version '0.31.1-2' with architecture '' Unable to make a source version for version '0.31.1-2' Marked as fixed in versions 0.31.1-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 995215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995260: chrony: Mismatched filename for UNIX socket between client and daemon
Package: chrony
Version: 4.0-8
Severity: grave
Tags: upstream
Justification: renders package unusable
X-Debbugs-Cc: s.egb...@sbcglobal.net
Dear Maintainer,
The filename construct for a UNIX socket to be shared
between the Chrony (chronyd) daemon and its Chrony CLI (chronyc) client
admin tool are not in sync, as client's UNIX filename uses a PID value
whereas server's UNIX filename does not use PID value.
This appears to be a Debian-only issue.
Fired up its daemon and doubled checked that a UNIX socket was made:
$ ls -1 /run/chrony
chrony.sock
chrony.pid
Execute the client and no successful UNIX socket opened.
Using List Open File (lsof) tool, I show the daemon's opened files:
COMMAND PID USER FD TYPE NODE NAME
chronyd 3597 _chrony3u unix 0x \
type=DGRAM
chronyd 3597 _chrony5u IPv4 UDP 127.0.0.1:323
chronyd 3597 _chrony6u IPv6 UDP [::1]:323
chronyd 3597 _chrony7u unix 0x \
/run/chrony/chronyd.sock type=DGRAM
chronyd 3597 _chrony8u unix 0x type=SEQPACKET
chronyc 3809johnd3u IPv4 UDP \
127.0.0.1:33911->127.0.0.1:323
No socket in the dispatcher part of the daemon, now to check the other
forked part of the daemon used to carry on the connection with
its chronyc client, same 'lsof' output.
COMMAND PID USER FD TYPE NODE NAME
chronyd 3597 _chrony5u IPv4 UDP 127.0.0.1:323
chronyd 3597 _chrony6u IPv6 UDP [::1]:323
chronyd 3598 _chrony9u unix 0x type=SEQPACKET
chronyc 3809johnd3u IPv4 UDP \
127.0.0.1:33911->127.0.0.1:323
Appears that client failed socket open and fell back to a
different approach which is using an IP loopback address.
Investigated why socket open failed... by using 'strace -f chrony[c|d]'.
For the chronyd v4.0 having opened a Debian-tweaked '/run/chrony/chrony.sock',
I show the corresponding chronyc v4.0 version:
$ chronyc -v
chronyc (chrony) version 4.0 (+READLINE +SECHASH +IPV6 -DEBUG)
And ran strace against this v4.0 client and grep'd for 'sock' word pattern:
$ strace -f /usr/bin/chronyc
socket(AF_UNIX, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
unlink("/run/chrony/chronyc.3875.sock") = -1 EACCES (Permission denied)
bind(3, {sa_family=AF_UNIX, sun_path="/run/chrony/chronyc.3875.sock"}, 110)
= -1 EACCES (Permission denied)
getsockname(3, {sa_family=AF_UNIX}, [112->2]) = 0
close(3)= 0
socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 3
connect(3, {sa_family=AF_INET, sin_port=htons(323),
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
Noticed the 'PID' number being inserted into the
'/run/chrony/chronyc.3875.sock'?
This is the chronyc client doing "PID-sock" filenaming convention, whereas
its daemon is doing a different "just-sock" filenaming convention.
The v4.1 client does exactly the same.
chronyc (chrony) version DEVELOPMENT (-READLINE -SECHASH +IPV6 +DEBUG)
socket(AF_UNIX, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
unlink("/var/run/chrony/chronyc.3885.sock") = -1 EACCES (Permission denied)
bind(3, {sa_family=AF_UNIX, sun_path="/var/run/chrony/chronyc.3885.sock"},
110) = -1 EACCES (Permission denied)
getsockname(3, {sa_family=AF_UNIX}, [112->2]) = 0
close(3)= 0
socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 3
connect(3, {sa_family=AF_INET, sin_port=htons(323),
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
fstat(0, {st_mode=S_IFCHR|0620, st_rdev=makedev(0x88, 0), ...}) = 0
read(0, ^Cstrace: Process 3885 detached
It would be nice to use consistent filenaming convention for the UNIX socket
for both client and daemon.
-- System Information:
Debian Release: 11.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.46 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages chrony depends on:
ii adduser 3.118
ii init-system-helpers 1.60
ii iproute2 5.10.0-4
ii libc62.31-13
ii libcap2 1:2.44-1
ii libedit2 3.1-20191231-2+b1
ii libgnutls30 3.7.1-5
ii libnettle8 3.7.3-1
ii libseccomp2 2.5.1-1
ii tzdata 2021a-1
ii ucf 3.0043
chrony recommends no packages.
Versions of packages chrony suggests:
ii bind9-dnsutils [dnsutils] 1:9.16.15-1
pn networkd-dispatcher
--
Bug#995199: marked as done (r-bioc-ioniser: autopkgtest regression)
Your message dated Tue, 28 Sep 2021 15:49:43 + with message-id and subject line Bug#995199: fixed in r-bioc-ioniser 2.16.0+dfsg-2 has caused the Debian Bug report #995199, regarding r-bioc-ioniser: autopkgtest regression 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.) -- 995199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995199 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: r-bioc-ioniser Version: 2.16.0+dfsg-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org | ══ Failed tests | ── Error (test_Fast5Summary.R:5:1): (code run outside of `test_that()`) | Error: there is no package called ‘minionSummaryData’ | Backtrace: | █ | 1. └─utils::data(s.typhi.rep2, package = "minionSummaryData") test_Fast5Summary.R:5:0 | 2. └─base::find.package(package, lib.loc, verbose = verbose) | ── Error (test_plotting.R:5:1): (code run outside of `test_that()`) | Error: there is no package called ‘minionSummaryData’ | Backtrace: | █ | 1. └─utils::data(s.typhi.rep2, package = "minionSummaryData") test_plotting.R:5:0 | 2. └─base::find.package(package, lib.loc, verbose = verbose) | | [ FAIL 2 | WARN 2 | SKIP 0 | PASS 1 ] | Error: Test failures See https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-bioc-ioniser/15560558/log.gz Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: r-bioc-ioniser Source-Version: 2.16.0+dfsg-2 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of r-bioc-ioniser, 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. Nilesh Patra (supplier of updated r-bioc-ioniser 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: Tue, 28 Sep 2021 20:50:30 +0530 Source: r-bioc-ioniser Architecture: source Version: 2.16.0+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian R Packages Maintainers Changed-By: Nilesh Patra Closes: 995199 Changes: r-bioc-ioniser (2.16.0+dfsg-2) unstable; urgency=medium . * Team Upload. * d/t/autopkgtest-pkg-r.hook: hook to remove tests depending on miniondatasummary since this is not packaged (Closes: #995199) Checksums-Sha1: c1804250c50e4539997ca5fbc7298c5650cdea42 2415 r-bioc-ioniser_2.16.0+dfsg-2.dsc 1ce58813ff922723f03aadf7b838a98ca77f6faf 3408 r-bioc-ioniser_2.16.0+dfsg-2.debian.tar.xz 419d1905b377dcb03102bd663d7b1238b003b04f 15383 r-bioc-ioniser_2.16.0+dfsg-2_amd64.buildinfo Checksums-Sha256: 7ddfc0cbe47e64d2c4346e9facceb3a3b6c0d453a581d02442a81d7c62557851 2415 r-bioc-ioniser_2.16.0+dfsg-2.dsc fd1e1adfb549a2891f295c2bcc3223acde15fa0bdce6536add4d543d539cf0bd 3408 r-bioc-ioniser_2.16.0+dfsg-2.debian.tar.xz 4c0c8f43dc4be69bd011655769fb0e2cb0e066eae14a6fb8d34cdd42a63fd743 15383 r-bioc-ioniser_2.16.0+dfsg-2_amd64.buildinfo Files: 85db703a3707365f3eff308fc31f6348 2415 gnu-r optional r-bioc-ioniser_2.16.0+dfsg-2.dsc 5101b06052d8cdb60d6ad7a2a99ee67c 3408 gnu-r optional r-bioc-ioniser_2.16.0+dfsg-2.debian.tar.xz 68f032881f1a2a77884c5e1e5b67820d 15383 gnu-r optional r-bioc-ioniser_2.16.0+dfsg-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmFTNVwUHG5wYXRyYTk3 NEBnbWFpbC5jb20ACgkQALrnSzQzafGPeRAAlX1GTLlg2fwXuHkrx2eDUTLsO49l 40DaXkq1Ph/UVAXtT0AGrzaDmfZj95B5efUX/WEdKjFSXjocUsOqUBFvybqpDkCX Z8FTajHVgP38L2Uz2kXsdFWguYcFOVKc1bTTNJtGAt/7i80JhsOnRrvHBcSfc/ao Or9VoWCMFf3T2GJbTSG0gtY1HhDJf4tJbSq2lpuTtwpG604M3PJ261mRBCbnCwWx xe1B6a27ryDVsS6Zy/J7lRpVaT2RvZO241FzmIMsM8/aJuy3IJC2xL4LJYiy8/hk 4ZBlVprSpTm8HwKEl9QNFB4q/VyeCpB3HSD43csHFyJjDkx+79wXgkKcs3dtNlj/ +ZcngCcpnH3OF1knWMoZZpPcwlTVGA0ubXxo0W7JFaSMpAIsx2maYqkIl4oJr2ek B6+XKQorQoa1/uCGq1Lk6irlemPPwhCCxZXu7Z0o4zJmNPyDDKe3ojSqllkBAJsS Cx2o3czEKlhUenj1ly7apbWoeIHE7kimPqa503WCd1/dMBSOsNGKYKuzkjQiToT1 sj3CZZrH1FeMDHviazhbl31bFRd5nz21mjsNc/wSaRRnD0CWAMC37oGH8K8jtMcU i6vg+yQqEZ4azySiBtrlhd+qM/BFUZRSrmQo8P4vhg/5GRFU/ZDW70TtLllRIAFz gFplY26/QpbMM9o= =sl4n -END PGP
Bug#995114: marked as done (python3-pyroute2.{core,ndb}: missing Breaks+Replaces: python3-pyroute2 (<< 0.6))
Your message dated Tue, 28 Sep 2021 15:38:36 +
with message-id
and subject line Bug#995114: fixed in pyroute2 0.6.4-2
has caused the Debian Bug report #995114,
regarding python3-pyroute2.{core,ndb}: missing Breaks+Replaces:
python3-pyroute2 (<< 0.6)
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.)
--
995114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995114
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pyroute2.core,python3-pyroute2.ndb
Version: 0.6.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
This error may also be triggered by having a predecessor package from
'sid 'installed while installing the package from 'experimental'.
See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
>From the attached log (scroll to the bottom...):
Selecting previously unselected package python3-pyroute2.core.
Preparing to unpack .../python3-pyroute2.core_0.6.4-1_all.deb ...
Unpacking python3-pyroute2.core (0.6.4-1) ...
dpkg: error processing archive
/var/cache/apt/archives/python3-pyroute2.core_0.6.4-1_all.deb (--unpack):
trying to overwrite '/usr/bin/ss2', which is also in package
python3-pyroute2 0.5.14-2
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Selecting previously unselected package python3-pyroute2.nslink.
Preparing to unpack .../python3-pyroute2.nslink_0.6.4-1_all.deb ...
Unpacking python3-pyroute2.nslink (0.6.4-1) ...
Selecting previously unselected package python3-pyroute2.ndb.
Preparing to unpack .../python3-pyroute2.ndb_0.6.4-1_all.deb ...
Unpacking python3-pyroute2.ndb (0.6.4-1) ...
dpkg: error processing archive
/var/cache/apt/archives/python3-pyroute2.ndb_0.6.4-1_all.deb (--unpack):
trying to overwrite '/usr/bin/pyroute2-cli', which is also in package
python3-pyroute2 0.5.14-2
Errors were encountered while processing:
/var/cache/apt/archives/python3-pyroute2.core_0.6.4-1_all.deb
/var/cache/apt/archives/python3-pyroute2.ndb_0.6.4-1_all.deb
W: --force-yes is deprecated, use one of the options starting with --allow
instead.
E: Sub-process /usr/bin/dpkg returned an error code (1)
+ apt-get -yf --force-yes install python3-pyroute2=0.5.14-2
python3-pyroute2.ndb=0.6.4-1
Reading package lists...
Building dependency tree...
Reading state information...
python3-pyroute2 is already the newest version (0.5.14-2).
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
python3-pyroute2.ndb : Depends: python3-pyroute2.core but it is not going to
be installed
python3-pyroute2.nslink : Depends: python3-pyroute2.core but it is not going
to be installed
cheers,
Andreas
python3-pyroute2=0.5.14-2_python3-pyroute2.ndb=0.6.4-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: pyroute2
Source-Version: 0.6.4-2
Done: Thomas Goirand
We believe that the bug you reported is fixed in the latest version of
pyroute2, 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.
Thomas Goirand (supplier of updated pyroute2 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: Tue, 28 Sep 2021 17:04:23 +0200
Source: pyroute2
Architecture: source
Version: 0.6.4-2
Distribution: experimental
Urgency: medium
Maintainer: Debian OpenStack
Changed-By: Thomas Goirand
Closes: 995114
Changes:
pyroute2 (0.6.4-2) experimental; urgency=medium
.
* python3-pyroute2.{core,ndb}: add missing Breaks+Replaces: python3-pyroute2
(<< 0.6) (Closes: #995114).
* Add fix-conf.py-for-sphinx-4.patch.
Checksums-Sha1:
8339ad99f2c0369b7b816eee20232ae19f3481b9 3030 pyroute2_0.6.4-2.dsc
Bug#994896: marked as done (pyhst2: FTBFS due to missing B-D: python3-six)
Your message dated Tue, 28 Sep 2021 15:19:05 +
with message-id
and subject line Bug#994896: fixed in pyhst2 2020c-2
has caused the Debian Bug report #994896,
regarding pyhst2: FTBFS due to missing B-D: python3-six
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.)
--
994896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994896
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyhst2
Version: 2020c-1
Severity: serious
Tags: sid bookworm
Hi,
pyhst2 FTBFS in current sid when running the tests:
dh_auto_test -O--buildsystem=pybuild
I: pybuild base:232: cd /build/pyhst2-2020c/.pybuild/cpython3_3.9_pyhst2/build;
python3.9 -m unittest discover -v
PyHST2_2020c.test (unittest.loader._FailedTest) ... ERROR
==
ERROR: PyHST2_2020c.test (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: PyHST2_2020c.test
Traceback (most recent call last):
File
"/build/pyhst2-2020c/.pybuild/cpython3_3.9_pyhst2/build/PyHST2_2020c/third_party/six.py",
line 46, in
from ._local.six import * # noqa
ModuleNotFoundError: No module named 'PyHST2_2020c.third_party._local'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3.9/unittest/loader.py", line 470, in _find_test_path
package = self._get_module_from_name(name)
File "/usr/lib/python3.9/unittest/loader.py", line 377, in
_get_module_from_name
__import__(name)
File
"/build/pyhst2-2020c/.pybuild/cpython3_3.9_pyhst2/build/PyHST2_2020c/test/__init__.py",
line 44, in
from . import utilstest
File
"/build/pyhst2-2020c/.pybuild/cpython3_3.9_pyhst2/build/PyHST2_2020c/test/utilstest.py",
line 50, in
from ..third_party import six
File
"/build/pyhst2-2020c/.pybuild/cpython3_3.9_pyhst2/build/PyHST2_2020c/third_party/six.py",
line 49, in
from six import * # noqa
ModuleNotFoundError: No module named 'six'
--
Ran 1 test in 0.001s
FAILED (errors=1)
E: pybuild pybuild:353: test: plugin distutils failed with: exit code=1: cd
/build/pyhst2-2020c/.pybuild/cpython3_3.9_pyhst2/build; python3.9 -m unittest
discover -v
dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit
code 13
make: *** [debian/rules:11: build] Error 25
This looks like the package is missing an explicit
Build-Depends: python3-six
as that package is no longer pulled in transitively.
Andreas
--- End Message ---
--- Begin Message ---
Source: pyhst2
Source-Version: 2020c-2
Done: Neil Williams
We believe that the bug you reported is fixed in the latest version of
pyhst2, 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 994...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Neil Williams (supplier of updated pyhst2 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: Tue, 28 Sep 2021 15:28:16 +0100
Source: pyhst2
Architecture: source
Version: 2020c-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Neil Williams
Closes: 994896
Changes:
pyhst2 (2020c-2) unstable; urgency=medium
.
* Team upload.
* Add missing B-D: python3-six (Closes: #994896)
* Improve clean rule for generated file
* Bump Standards Version
Checksums-Sha1:
58fa0b432962b3c688aef3984c81779f998226a4 2203 pyhst2_2020c-2.dsc
5500e88658695343471f8f4ceef11df9d42f245e 9168 pyhst2_2020c-2.debian.tar.xz
4be23c27c156ab1a28eb3b7dd857840747fa10df 11650 pyhst2_2020c-2_amd64.buildinfo
Checksums-Sha256:
545b1bb6b4c9e3ce80fa4793fc329b768d0e4360a3a7296fd9b28cd53f1d5ead 2203
pyhst2_2020c-2.dsc
9d4458d7a804eb7f5aac96922dc177d77681e37d54b9e93c7325cdd1727d77c3 9168
pyhst2_2020c-2.debian.tar.xz
006585fb87be09b5300f2c1c310225659df73a81392271139873e401f41138da 11650
pyhst2_2020c-2_amd64.buildinfo
Files:
832e46ae671d01ad566fb31d730e076b 2203 contrib/python optional
pyhst2_2020c-2.dsc
dfe708144d1d0514c868f50b5fc9b62f 9168
Bug#995241: marked as done (rdkit FTBFS with sphinx 4.2)
Your message dated Tue, 28 Sep 2021 14:48:30 + with message-id and subject line Bug#995241: fixed in rdkit 202009.5-2 has caused the Debian Bug report #995241, regarding rdkit FTBFS with sphinx 4.2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 995241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995241 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rdkit Version: 202009.5-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=rdkit=202009.5-1%2Bb2 ... ! LaTeX Error: File `tgtermes.sty' not found. ... Latexmk: Errors, so I did not complete making targets make[3]: *** [Makefile:29: RDKit.pdf] Error 12 A build dependency on tex-gyre is now required for LaTeX output with Sphinx. --- End Message --- --- Begin Message --- Source: rdkit Source-Version: 202009.5-2 Done: Andrius Merkys We believe that the bug you reported is fixed in the latest version of rdkit, 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. Andrius Merkys (supplier of updated rdkit 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: Tue, 28 Sep 2021 08:56:39 -0400 Source: rdkit Architecture: source Version: 202009.5-2 Distribution: unstable Urgency: medium Maintainer: Debichem Team Changed-By: Andrius Merkys Closes: 995241 Changes: rdkit (202009.5-2) unstable; urgency=medium . * Team upload. * Adding missing build dependency on tex-gyre (Closes: #995241) Checksums-Sha1: 7411a0cdb7b8ce6dcef0aacd0bfc7249304150e4 2856 rdkit_202009.5-2.dsc d68a28a6b0af646a9b29c55234620bf167402a86 100032 rdkit_202009.5-2.debian.tar.xz dcaab716fde7c3b9ad8e8ff8ae08b6e1036ea456 14630 rdkit_202009.5-2_source.buildinfo Checksums-Sha256: 956cdc718688b01ff0af78e5d75176cbc2ccfe64f00b781bb8360854e9fa0c0b 2856 rdkit_202009.5-2.dsc 24f21eae4c4ac5dff08ced50efc3cc3bddb763bc6fa0f496f6f330817f900e1f 100032 rdkit_202009.5-2.debian.tar.xz 8f10bc2ebd2d0cb2911a2164346f3664da0119f53dcf2bef859403948e1af6e3 14630 rdkit_202009.5-2_source.buildinfo Files: 3530d84aff2e262438a5b4479b6e8768 2856 science optional rdkit_202009.5-2.dsc 63dae4fdd81aaa9c0db1832d68716420 100032 science optional rdkit_202009.5-2.debian.tar.xz ee69d2c24c8c503d201a83745e1abe4a 14630 science optional rdkit_202009.5-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEdyKS9veshfrgQdQe5fQ/nCc08ocFAmFTIlsSHG1lcmt5c0Bk ZWJpYW4ub3JnAAoJEOX0P5wnNPKHJpUP/3/c23ZlAdGEF060hwUBhnUm9luEW1Ct yTunaHhiQ0nX4jpfvqbg2LCxn6CI6P/5gklegbJEiP9gv9TZjDFcvFy92fgN/DRh xcuBEFcO///g3TAV2mkUVsl/43SmBfiCMhbcCdOCzsnrjXG9fBbHYzcfsGvqXDBw 65c3PLqPVZnhMD0Q8Fxr+R2TAQ1ZDdLVN5ZeMqnVMvX/REgJposYI6GVLhsk+/zQ 65DCGVmRJjXLJGMbB6vwcim7A791oZKheqsA4E7UUQ62ULcoD8Dsm1fB8HqatIE3 otk/wChNdBjMSOFENZciLUYQqwg8cl9ytISRJ7ZHaSeoM5ARwlpu5EV8c38uL58w lEXyE3nOvbSyGVUKMoqkzIQ2BSkpMh7Cq+AtPAWWtayDOAusawzd2zXNDjPfK1TM xnczIcAWmdTld0mM7abXjiHuyN6Enw1Icp/sDaDmbAd//+lYYw4LXPqhv1lkFYnz ebBA9yhXFmKpFitNWyAxEd7W6E4Knc2jAWi7kkomluY0vdL55NpCQVTcyk5EO8xf A0XPQ3b3unpP7HCE5Z0nBkBuWkNCsoqXtT5qIRX6kOkK6TCxBObtgOWRH6TyqaWU NQZRYU3QOcKfCeQfSMPDoKIXh0zg//ELgB6Jdi9ieb175VuLCu7TzV4fRCztOU+z +wgyAoNfuWMU =G5yO -END PGP SIGNATURE End Message ---
Processed: limit source to pyhst2, tagging 994896
Processing commands for cont...@bugs.debian.org: > limit source pyhst2 Limiting to bugs with field 'source' containing at least one of 'pyhst2' Limit currently set to 'source':'pyhst2' > tags 994896 + pending Bug #994896 [src:pyhst2] pyhst2: FTBFS due to missing B-D: python3-six Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 994896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994896 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995242: isc-dhcp-server: omshell returns inconsistent results or segfaults
Package: isc-dhcp-server Version: 4.4.1-2.3 Severity: grave Justification: renders package unusable -- System Information: Debian Release: 11.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/2 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages isc-dhcp-server depends on: ii debconf [debconf-2.0] 1.5.77 ii debianutils4.11.2 ii libc6 2.31-13 ii libdns-export1110 1:9.11.19+dfsg-2.1 ii libirs-export161 1:9.11.19+dfsg-2.1 ii libisc-export1105 1:9.11.19+dfsg-2.1 ii lsb-base 11.1.0 Versions of packages isc-dhcp-server recommends: ii isc-dhcp-common 4.4.1-2.3 ii policycoreutils 3.1-3 Versions of packages isc-dhcp-server suggests: pn isc-dhcp-server-ldap pn policykit-1 -- Configuration Files: /etc/dhcp/dhcpd.conf changed [not included] -- debconf information excluded -- To Reproduce -- Two DHCP servers need to be configured as failover peers. Issue the following commands using omshell # omshell > server localhost > port 7911 > key omapi_key > connect Segmentation fault (core dumped) Note, the connect works occasionally after a cold server restart, but once the failure starts there is no recovery. The connect does not always result is a segfault. Frequently the connect just hangs. example from 'dmesg' output: [Tue Sep 28 11:05:22 2021] omshell[4604]: segfault at 0 ip 55623cdd06dc sp 7ffd5a2c7c78 error 4 in omshell[55623cd97000+45000]
Bug#995241: rdkit FTBFS with sphinx 4.2
Source: rdkit Version: 202009.5-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=rdkit=202009.5-1%2Bb2 ... ! LaTeX Error: File `tgtermes.sty' not found. ... Latexmk: Errors, so I did not complete making targets make[3]: *** [Makefile:29: RDKit.pdf] Error 12 A build dependency on tex-gyre is now required for LaTeX output with Sphinx.
Bug#993198: gnome-shell-extension-system-monitor: does not declare compatibility with GNOME Shell 40
On Tue, Sep 28, 2021 at 12:27 AM Samuel Henrique wrote: > I gave you permission to that repo (best I can do on my side), and I > set an expiration date of the end of this year, until then you will > end up in the salsa group and inherit permissions so it should be > good. Perfect, thanks! > Awesome, I can do that. Alternatively, I can also push your changes > myself, if you push them to your own repo and give me a go ahead. Just pushed to the main repo. Please take a look and let me know if it works! Cheers
Bug#994699: marked as done (libtest-xml-simple-perl: Test failure in t/03valid.t)
Your message dated Tue, 28 Sep 2021 10:23:08 + with message-id and subject line Bug#994699: fixed in libtest-xml-simple-perl 1.05-3 has caused the Debian Bug report #994699, regarding libtest-xml-simple-perl: Test failure in t/03valid.t 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.) -- 994699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994699 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libtest-xml-simple-perl Version: 1.05-2 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 As first seen on ci.debian.net, this package has a test failure which also happens at build time: # Failed test 'bad XML' # at t/03valid.t line 48. # STDOUT is: # > not ok 1 - :2: parser error : Premature end of data in tag nomatch line 1 # # # # ^ # not: # > not ok 1 - :2: parser error : EndTag: ' ii libxml-libxml-perl 2.0134+dfsg-2+b1 ii perl 5.32.1-5 libtest-xml-simple-perl recommends no packages. libtest-xml-simple-perl suggests no packages. -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmFHWn9fFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgZaFg/9G/ymXDLGeZTkL7Sx7f0YX7OrfYW/+psUJE/fXNbWP7pq8nFIVRtRpiER OWtBwSQLppMq55MyyIaDWvSPIGHZo0eISB6/ujIWsEbHKPithpMzK3QnTZjq41eD +a+i3FwwzqRgz0bu5U26M+AmIop0KRw9iZOkHCglssmRs+q7EeIWmqdpq2XBfGzy 3dcu4VplSmRX2eNAm8iJvC8BpbGeAoHZwOI1dS0TAKKklRYIyFbfDWRxPFVGfWVI cDpyx3E6LPs+7FrvlVjpnNe9gci8V9BVwGxQSZGjREhs2iKPhQNxDFnzoG9eQJGL XoVxf58YJYG2vUK9is+sBLT2wo9llGACWMvcBG3j+Jl6yAHMKA1J/HKM2oR9ulOm qv2Ip7GeU3oDdLBk0ByDI6ghwuYbll9FgUyE6u3hgp+3TKXbTUyoQ2wPWToUv8kF ynxlNzSFH+/r3CMBE6IYKOmTbze8t2lSxmkhU81lZ3nwbJgrHpt6KuTC4QUcvqLj qhDF8mT40LE4v24zJNb8HIsFleRWiOH7R6w2waJH2vF7iCX+xhlW3ouCCIZJxISa 3NEHuUyaStXh/9zHyfIpfQulWzthvcH7WHJ/a48mvq1Nc0pT4KrdjXceMp5NpIKs UFjBO33YZGc+UIlaY4he3HHWhMtWLsgrKXHAkneykf8ZX6vJK4Q= =m9vE -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: libtest-xml-simple-perl Source-Version: 1.05-3 Done: gregor herrmann We believe that the bug you reported is fixed in the latest version of libtest-xml-simple-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 994...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated libtest-xml-simple-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 28 Sep 2021 11:54:08 +0200 Source: libtest-xml-simple-perl Architecture: source Version: 1.05-3 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: gregor herrmann Closes: 994699 Changes: libtest-xml-simple-perl (1.05-3) unstable; urgency=medium . * Update patch for t/03valid.t to adjust for changed libxml2 output. (Closes: #994699) * Update years of packaging copyright. * Declare compliance with Debian Policy 4.6.0. * Set Rules-Requires-Root: no. * Bump debhelper-compat to 13. * Annotate test-only build dependencies with . * Refresh lintian overrides. Checksums-Sha1: 724e65fd461ee9d80b8f844c9c460994e430f81b 2619 libtest-xml-simple-perl_1.05-3.dsc 04731b1b7dedc5c1cc19d045fbb4f590408f739c 3888 libtest-xml-simple-perl_1.05-3.debian.tar.xz Checksums-Sha256: 8a38a3213ff8ad04d3da60f8615469568a2cf5170ef474cec7e31b55518e6b00 2619 libtest-xml-simple-perl_1.05-3.dsc c1cc6b6615427814669fab3af0652caf93bd9037c706be6ad9cce03703b367ff 3888 libtest-xml-simple-perl_1.05-3.debian.tar.xz Files: bd2fadab8392c22d95d0238fa40ad1d0 2619 perl optional libtest-xml-simple-perl_1.05-3.dsc 545f398c15f011272239cf8af314c98d 3888 perl optional libtest-xml-simple-perl_1.05-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmFS5wJfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgbYwA/+LHD54YoTUPCEfQT6WFOogc3V/oHE+z4H3QSmfbCIXS/0OQ80hh/nplkW
Processed: Bug#994699 marked as pending in libtest-xml-simple-perl
Processing control commands: > tag -1 pending Bug #994699 [libtest-xml-simple-perl] libtest-xml-simple-perl: Test failure in t/03valid.t Added tag(s) pending. -- 994699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994699 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#994699: marked as pending in libtest-xml-simple-perl
Control: tag -1 pending Hello, Bug #994699 in libtest-xml-simple-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libtest-xml-simple-perl/-/commit/aac138732eb600258fbe38024535a849981496fb Update patch for t/03valid.t to adjust for changed libxml2 output. Closes: #994699 (this message was generated automatically) -- Greetings https://bugs.debian.org/994699
Processed: upstream
Processing commands for cont...@bugs.debian.org: > forwarded 995150 https://github.com/open-mpi/ompi/issues/9432 Bug #995150 [src:openmpi] openmpi: segfault in mca_io_romio_dist_MPI_File_iwrite_all Set Bug forwarded-to-address to 'https://github.com/open-mpi/ompi/issues/9432'. > thanks Stopping processing here. Please contact me if you need assistance. -- 995150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995150 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#995216: simple-scan: B Text scans saved as gibberish
Processing commands for cont...@bugs.debian.org: > severity 995216 normal Bug #995216 [simple-scan] simple-scan: B Text scans saved as gibberish Severity set to 'normal' from 'grave' > tags 995216 + moreinfo Bug #995216 [simple-scan] simple-scan: B Text scans saved as gibberish Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 995216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995216 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995216: simple-scan: B Text scans saved as gibberish
severity 995216 normal tags 995216 + moreinfo thanks Hello Felix, thank you for spending your time helping to make Debian better with this bug report. First of all, I set the severity to normal, because there is no data loss in the sense of grave, but only an erroneous output. For a better understanding please answer the following questions: - What was the occupancy of the mouted partitions? - How big was the logfile (~/.cache/simple-scan/simple-scan.log)? - What was recorded in the logfile at the time of the error? - Does the error still occur after a reboot? And so that I have all system information can you please start once: bugreport -N 995216 CU Jörg Am Montag, dem 27.09.2021 um 17:37 -0700 schrieb Felix Lechner: > Package: simple-scan > Found: 3.38.1-1 > Severity: grave > > Hi, > > Starting earlier today (between scans) simple-scan on bullseye became > unable to save B text scans properly. Now they are saved as > gibberish. > > It is possible the files are being saved in a format not understood > by > my PDF reader, but I could not find a common reader that worked: I > tried evince, muPDF, gscan2pdf, an old trial version of Master PDF > Editor, and GIMP and Inkscape. Only LibreOffice Draw got it right. > > In accordance with the recommendations here [1] I marked the bug > 'grave' because I lost data because of it (or so it seemed when I > wrote). The bug is also somewhat treacherous: The image on the screen > looks fine. One has to open the saved file to see the issue. > > Thanks for simple-scan! It's a great and best-in-class program! > > Kind regards > Felix Lechner > > [1] https://www.debian.org/Bugs/Developer#severities -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old pgp Key: BE581B6E (revoked since 2014-12-31). Jörg Frings-Fürst D-54470 Lieser git: https://jff.email/cgit/ Threema: SYR8SJXB Wire: @joergfringsfuerst Skype: joergpenguin Ring: jff Telegram: @joergfringsfuerst My wish list: - Please send me a picture from the nature at your home. signature.asc Description: This is a digitally signed message part
Processed: affects 995150
Processing commands for cont...@bugs.debian.org: > affects 995150 src:mpi4py Bug #995150 [src:openmpi] openmpi: segfault in mca_io_romio_dist_MPI_File_iwrite_all Added indication that 995150 affects src:mpi4py > thanks Stopping processing here. Please contact me if you need assistance. -- 995150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995150 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 995150
Processing commands for cont...@bugs.debian.org: > tags 995150 + ftbfs Bug #995150 [src:openmpi] openmpi: segfault in mca_io_romio_dist_MPI_File_iwrite_all Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 995150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995150 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995228: Old bug is back, needs a rebuild.
I've just rebuilt qtcreator locally, and the bug is gone. Dear maintainer, please rebuild the package. Roman. On Tue, Sep 28, 2021 at 11:24 AM Roman Lebedev wrote: > > Package: qtcreator > Version: 5.0.1-1 > Severity: serious > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Looks like qtcreator (and iwyu/etc) need to be rebuilt again. > After some recent updates, qtcreator again shows errors > about certain C++ types not being known. > > Roman > > > - -- System Information: > Debian Release: bookworm/sid > APT prefers unstable > APT policy: (990, 'unstable'), (500, 'unstable-debug'), (1, > 'experimental-debug'), (1, 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 5.14.0-1-amd64 (SMP w/32 CPU threads) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages qtcreator depends on: > ii clang-11 1:11.1.0-2 > ii libc6 2.32-4 > ii libclang1-11 1:11.1.0-2 > ii libdw1 0.185-2 > ii libelf10.185-2 > ii libgcc-s1 11.2.0-8 > ii libkf5syntaxhighlighting5 5.86.0-1 > ii libqt5concurrent5 5.15.2+dfsg-12 > ii libqt5core5a [qtbase-abi-5-15-2] 5.15.2+dfsg-12 > ii libqt5designer55.15.2-5 > ii libqt5designercomponents5 5.15.2-5 > ii libqt5gui5 5.15.2+dfsg-12 > ii libqt5help55.15.2-5 > ii libqt5network5 5.15.2+dfsg-12 > ii libqt5printsupport55.15.2+dfsg-12 > ii libqt5qml5 [qtdeclarative-abi-5-15-2] 5.15.2+dfsg-8 > ii libqt5quick5 5.15.2+dfsg-8 > ii libqt5quickwidgets55.15.2+dfsg-8 > ii libqt5serialport5 5.15.2-2 > ii libqt5sql5 5.15.2+dfsg-12 > ii libqt5sql5-sqlite 5.15.2+dfsg-12 > ii libqt5svg5 5.15.2-3 > ii libqt5test55.15.2+dfsg-12 > ii libqt5widgets5 5.15.2+dfsg-12 > ii libqt5xml5 5.15.2+dfsg-12 > ii libstdc++6 11.2.0-8 > ii libyaml-cpp0.6 0.6.3-10 > ii libzstd1 1.4.8+dfsg-2.1 > ii qml-module-qtqml-models2 5.15.2+dfsg-8 > ii qml-module-qtquick-controls5.15.2-2 > ii qml-module-qtquick25.15.2+dfsg-8 > ii qtchooser 66-2 > ii qtcreator-data 5.0.1-1 > > Versions of packages qtcreator recommends: > pn clang-tidy > ii gdb10.1-2 > ii konsole [x-terminal-emulator] 4:21.08.1-1 > ii make 4.3-4.1 > ii qmlscene 5.15.2+dfsg-8 > pn qt5-doc > ii qt5-qmltooling-plugins 5.15.2+dfsg-8 > ii qtbase5-dev-tools 5.15.2+dfsg-12 > pn qtcreator-doc > ii qtdeclarative5-dev-tools 5.15.2+dfsg-8 > ii qttools5-dev-tools 5.15.2-5 > ii qttranslations5-l10n 5.15.2-2 > ii qtxmlpatterns5-dev-tools 5.15.2-3 > ii xterm [x-terminal-emulator]369-1 > > Versions of packages qtcreator suggests: > pn clazy > ii cmake 3.21.3-2 > ii g++ 4:10.2.1-1 > ii git 1:2.33.0-1 > ii meson 0.59.1-2 > ii subversion 1.14.1-3 > ii valgrind1:3.17.0-1 > > - -- no debconf information > > -BEGIN PGP SIGNATURE- > > iQIzBAEBCgAdFiEEjkF6151RK40WXe2HCDw+u0oWieAFAmFS0FMACgkQCDw+u0oW > ieAaCA/+NRCFsGN6uZl9E2E15Jz3gWYL6IKgu83f8RLr4czP7LpCijmK42Joa/Cm > l3GdPi4YgzzqPakZ7IxQ4YTeKm3Sp1JspKa8LmkbBMWOQJIKUkjKNMk509T9FcAd > dxtuWOlPVjN1qKfxPxGgdHwrk54xtgzoSCDP7EQvU/elYVta2FqAUl6tcJNsbA1N > 5qS/kbbP74XIxSsXb8sXhi+UaPjBizr+LaXm4GVMj+xKAdP90H1kbQZUKI4qCMbp > PNwGzsdWqyq+xqpGwf9e4J53U8E8qhlpU3Yk7TlIAOZxb0CDWqjnmr1GO9MyTeAO > dcvT7kUWNaCdr7OnuMZGDZT46CZRVcZfvQGwILmF9GrHATJv+fuFBiE6WSSnVcVg > Gh/KQKKjVqddYLnzAWfyd0zFSltO9jLFuFLhaWb+CVeUbGFTTq1qUKHjI1gVFIQc > OzbH5r6MZ2CmKkPjg/dYY/Peial9obuJ2UUw5MhvzLinNkdAwUIN535yfjHxMCKP > dW6EWGHzQH1MJiWgIR7HjxKB5icJa3o30G92DYG8OU0PeMgU32xPTaP7eE8iHPLh > 2PyDomWMSIyosQ9iPIrlap1GqzUetc/6NHKHTDFGO4mIoykj1soc0gHgpVDjPaxn > U0m1yeRDLy53Hm2L207CYBUhaH/drvnEJ2/X5D7x2tF08fBsyUQ= > =s0V5 > -END PGP SIGNATURE-
Bug#995228: Old bug is back, needs a rebuild.
Package: qtcreator Version: 5.0.1-1 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Looks like qtcreator (and iwyu/etc) need to be rebuilt again. After some recent updates, qtcreator again shows errors about certain C++ types not being known. Roman - -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-1-amd64 (SMP w/32 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages qtcreator depends on: ii clang-11 1:11.1.0-2 ii libc6 2.32-4 ii libclang1-11 1:11.1.0-2 ii libdw1 0.185-2 ii libelf10.185-2 ii libgcc-s1 11.2.0-8 ii libkf5syntaxhighlighting5 5.86.0-1 ii libqt5concurrent5 5.15.2+dfsg-12 ii libqt5core5a [qtbase-abi-5-15-2] 5.15.2+dfsg-12 ii libqt5designer55.15.2-5 ii libqt5designercomponents5 5.15.2-5 ii libqt5gui5 5.15.2+dfsg-12 ii libqt5help55.15.2-5 ii libqt5network5 5.15.2+dfsg-12 ii libqt5printsupport55.15.2+dfsg-12 ii libqt5qml5 [qtdeclarative-abi-5-15-2] 5.15.2+dfsg-8 ii libqt5quick5 5.15.2+dfsg-8 ii libqt5quickwidgets55.15.2+dfsg-8 ii libqt5serialport5 5.15.2-2 ii libqt5sql5 5.15.2+dfsg-12 ii libqt5sql5-sqlite 5.15.2+dfsg-12 ii libqt5svg5 5.15.2-3 ii libqt5test55.15.2+dfsg-12 ii libqt5widgets5 5.15.2+dfsg-12 ii libqt5xml5 5.15.2+dfsg-12 ii libstdc++6 11.2.0-8 ii libyaml-cpp0.6 0.6.3-10 ii libzstd1 1.4.8+dfsg-2.1 ii qml-module-qtqml-models2 5.15.2+dfsg-8 ii qml-module-qtquick-controls5.15.2-2 ii qml-module-qtquick25.15.2+dfsg-8 ii qtchooser 66-2 ii qtcreator-data 5.0.1-1 Versions of packages qtcreator recommends: pn clang-tidy ii gdb10.1-2 ii konsole [x-terminal-emulator] 4:21.08.1-1 ii make 4.3-4.1 ii qmlscene 5.15.2+dfsg-8 pn qt5-doc ii qt5-qmltooling-plugins 5.15.2+dfsg-8 ii qtbase5-dev-tools 5.15.2+dfsg-12 pn qtcreator-doc ii qtdeclarative5-dev-tools 5.15.2+dfsg-8 ii qttools5-dev-tools 5.15.2-5 ii qttranslations5-l10n 5.15.2-2 ii qtxmlpatterns5-dev-tools 5.15.2-3 ii xterm [x-terminal-emulator]369-1 Versions of packages qtcreator suggests: pn clazy ii cmake 3.21.3-2 ii g++ 4:10.2.1-1 ii git 1:2.33.0-1 ii meson 0.59.1-2 ii subversion 1.14.1-3 ii valgrind1:3.17.0-1 - -- no debconf information -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEjkF6151RK40WXe2HCDw+u0oWieAFAmFS0FMACgkQCDw+u0oW ieAaCA/+NRCFsGN6uZl9E2E15Jz3gWYL6IKgu83f8RLr4czP7LpCijmK42Joa/Cm l3GdPi4YgzzqPakZ7IxQ4YTeKm3Sp1JspKa8LmkbBMWOQJIKUkjKNMk509T9FcAd dxtuWOlPVjN1qKfxPxGgdHwrk54xtgzoSCDP7EQvU/elYVta2FqAUl6tcJNsbA1N 5qS/kbbP74XIxSsXb8sXhi+UaPjBizr+LaXm4GVMj+xKAdP90H1kbQZUKI4qCMbp PNwGzsdWqyq+xqpGwf9e4J53U8E8qhlpU3Yk7TlIAOZxb0CDWqjnmr1GO9MyTeAO dcvT7kUWNaCdr7OnuMZGDZT46CZRVcZfvQGwILmF9GrHATJv+fuFBiE6WSSnVcVg Gh/KQKKjVqddYLnzAWfyd0zFSltO9jLFuFLhaWb+CVeUbGFTTq1qUKHjI1gVFIQc OzbH5r6MZ2CmKkPjg/dYY/Peial9obuJ2UUw5MhvzLinNkdAwUIN535yfjHxMCKP dW6EWGHzQH1MJiWgIR7HjxKB5icJa3o30G92DYG8OU0PeMgU32xPTaP7eE8iHPLh 2PyDomWMSIyosQ9iPIrlap1GqzUetc/6NHKHTDFGO4mIoykj1soc0gHgpVDjPaxn U0m1yeRDLy53Hm2L207CYBUhaH/drvnEJ2/X5D7x2tF08fBsyUQ= =s0V5 -END PGP SIGNATURE-
Bug#995224: relion-cuda: FTBFS with cub 1.14
Source: relion-cuda Version: 3.1.0-2 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source Hi, relion-cuda FTBFS with cub 1.14 which was just uploaded to unstable: make[4]: Entering directory '/build/relion-cuda-3.1.0/build' [ 1%] Building NVCC (Device) object src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/relion_gpu_util_generated_cuda_projector_plan.cu.o cd /build/relion-cuda-3.1.0/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda && /usr/bin/cmake -E make_directory /build/relion-cuda-3.1.0/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/. cd /build/relion-cuda-3.1.0/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda && /usr/bin/cmake -D verbose:BOOL=1 -D build_configuration:STRING=Release -D generated_file:STRING=/build/relion-cuda-3.1.0/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/./relion_gpu_util_generated_cuda_projector_plan.cu.o -D generated_cubin_file:STRING=/build/relion-cuda-3.1.0/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/./relion_gpu_util_generated_cuda_projector_plan.cu.o.cubin.txt -P /build/relion-cuda-3.1.0/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/relion_gpu_util_generated_cuda_projector_plan.cu.o.Release.cmake -- Removing /build/relion-cuda-3.1.0/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/./relion_gpu_util_generated_cuda_projector_plan.cu.o /usr/bin/cmake -E rm -f /build/relion-cuda-3.1.0/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/./relion_gpu_util_generated_cuda_projector_plan.cu.o -- Generating dependency file: /build/relion-cuda-3.1.0/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/relion_gpu_util_generated_cuda_projector_plan.cu.o.NVCC-depend /usr/bin/nvcc -M -D__CUDACC__ /build/relion-cuda-3.1.0/src/acc/cuda/cuda_projector_plan.cu -o /build/relion-cuda-3.1.0/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/relion_gpu_util_generated_cuda_projector_plan.cu.o.NVCC-depend -ccbin /usr/bin/cc -m64 -DINSTALL_LIBRARY_DIR=/usr/lib/ -DSOURCE_DIR=/build/relion-cuda-3.1.0/src/ -DACC_CUDA=2 -DACC_CPU=1 -DCUDA -DALLOW_CTF_IN_SGD -DHAVE_SINCOS -DHAVE_TIFF -Xcompiler ,\"-g\",\"-O2\",\"-ffile-prefix-map=/build/relion-cuda-3.1.0=.\",\"-fstack-protector-strong\",\"-Wformat\",\"-Werror=format-security\",\"-O3\",\"-DNDEBUG\" -arch=sm_35 -D__INTEL_COMPILER --default-stream per-thread --disable-warnings -DNVCC -I/usr/include -I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -I/build/relion-cuda-3.1.0 -I/usr/lib/fltk -I/usr/include/x86_64-linux-gnu nvcc warning : The 'compute_35', 'compute_37', 'compute_50', 'sm_35', 'sm_37' and 'sm_50' architectures are deprecated, and may be removed in a future release (Use -Wno-deprecated-gpu-targets to suppress warning). In file included from /usr/include/thrust/system/cuda/config.h:33, from /usr/include/thrust/system/cuda/detail/execution_policy.h:35, from /usr/include/thrust/iterator/detail/device_system_tag.h:23, from /usr/include/thrust/iterator/detail/iterator_facade_category.h:22, from /usr/include/thrust/iterator/iterator_facade.h:37, from /build/relion-cuda-3.1.0/src/acc/cuda/cub/device/../iterator/arg_index_input_iterator.cuh:48, from /build/relion-cuda-3.1.0/src/acc/cuda/cub/device/device_reduce.cuh:41, from /build/relion-cuda-3.1.0/src/acc/cuda/cuda_utils_cub.cuh:16, from /build/relion-cuda-3.1.0/src/acc/cuda/cuda_projector_plan.cu:10: /usr/include/cub/util_namespace.cuh:46:2: error: #error CUB requires a definition of CUB_NS_QUALIFIER when CUB_NS_PREFIX/POSTFIX are defined. 46 | #error CUB requires a definition of CUB_NS_QUALIFIER when CUB_NS_PREFIX/POSTFIX are defined. | ^ CMake Error at relion_gpu_util_generated_cuda_projector_plan.cu.o.Release.cmake:220 (message): Error generating /build/relion-cuda-3.1.0/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/./relion_gpu_util_generated_cuda_projector_plan.cu.o make[4]: *** [src/apps/CMakeFiles/relion_gpu_util.dir/build.make:1439: src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/relion_gpu_util_generated_cuda_projector_plan.cu.o] Error 1 make[4]: Leaving directory '/build/relion-cuda-3.1.0/build' This seems to be the Breaking Change described in https://github.com/NVIDIA/cub/releases/tag/1.14.0: #350: When the CUB_NS_[PRE|POST]FIX macros are set, CUB_NS_QUALIFIER must also be defined to the fully qualified CUB namespace (e.g. #define CUB_NS_QUALIFIER ::foo::cub). Note that this is handled automatically when using the new [THRUST_]CUB_WRAPPED_NAMESPACE mechanism. Andreas
Bug#994673: marked as done (slcfitsio FTBFS: error: too many decimal points in number)
Your message dated Tue, 28 Sep 2021 07:19:07 + with message-id and subject line Bug#994673: fixed in slcfitsio 0.3.8+nosvn-6 has caused the Debian Bug report #994673, regarding slcfitsio FTBFS: error: too many decimal points in number 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.) -- 994673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994673 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: slcfitsio Version: 0.3.8+nosvn-5 Severity: serious Tags: ftbfs slcfitsio fails to build from source in unstable on amd64. A build ends as follows: | cc -shared -fPIC cfitsio-module.c -o cfitsio-module.so -L/usr/lib/x86_64-linux-gnu -lslang -L/usr/lib/x86_64-linux-gnu -lcfitsio-lm | In file included from cfitsio-module.c:10: | cfitsio-module.c: In function ‘check_version’: | cfitsio-module.c:2421:23: error: too many decimal points in number | 2421 |compiled_version = CFITSIO_VERSION; | | ^~~ | make[2]: *** [Makefile:65: cfitsio-module.so] Error 1 | make[2]: Leaving directory '/<>/src' | make[1]: *** [Makefile:7: all] Error 2 | make[1]: Leaving directory '/<>' | make: *** [/usr/share/cdbs/1/class/makefile.mk:77: debian/stamp-makefile-build] Error 2 | dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 Helmut --- End Message --- --- Begin Message --- Source: slcfitsio Source-Version: 0.3.8+nosvn-6 Done: Rafael Laboissière We believe that the bug you reported is fixed in the latest version of slcfitsio, 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 994...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rafael Laboissière (supplier of updated slcfitsio 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: Tue, 28 Sep 2021 03:29:59 -0300 Source: slcfitsio Architecture: source Version: 0.3.8+nosvn-6 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Rafael Laboissière Closes: 994673 Changes: slcfitsio (0.3.8+nosvn-6) unstable; urgency=medium . * QA upload. . * Create Git repository at Salsa.debian.org. The Git repository was created with "gbp import-dscs --debsnap", instead of doing archeological work in the Alioth archives. The layout of the repository follows the recommendation in DEP-14. * d/s/format: Use source format 3.0 (quilt) * Bump debhelper compatibility level to 13 + d/control: Set dependency on debhelper-compat = 13 + d/compat: Drop file * Switch from CDBS to debhelper + d/control: Drop the build-dependencies on cdbs and dpkg-dev + d/rules: Use the dh sequencer * Activate dh_autoreconf + d/rules: Move the generated autoconf/configure to the top directory + d/control: Drop useless build-dependency on autotools-dev + d/autoreconf: New file + d/p/update-configure.patch: New patch + d/source/options: Ignore the configure file * d/control: + Bump Standards-Version to 4.6.0 (no changes needed) + Use secure URI in Homepage field + Add Rules-Requires-Root: no * d/watch: + Bump version to 4 (no changes) + Use secure URI * d/t/control: Add autopkgtest support * d/p/cfitsio-version.patch: New patch (Closes: #994673) * d/p/fix-spelling.patch: New patch * d/p/uint64-unit-test.patch: New patch Checksums-Sha1: 50301234799d6ae7fb125d5cde6243858cb3e37f 2177 slcfitsio_0.3.8+nosvn-6.dsc a43b8f98cbe42570aa6153dd2fd906be73c1b56c 6976 slcfitsio_0.3.8+nosvn-6.debian.tar.xz Checksums-Sha256: 50989aff96b146421f27523fe9f7493bc03c6f725a3292590003b3a67d990fee 2177 slcfitsio_0.3.8+nosvn-6.dsc f46386f812e08cc3d0d51393208afc4d241a80e9d61d05d3ab01bccfe5d3433f 6976 slcfitsio_0.3.8+nosvn-6.debian.tar.xz Files: 7c05ce8f532457b6c25fe53a7ed9bf6b 2177 interpreters optional slcfitsio_0.3.8+nosvn-6.dsc 9baadf0a1787751bb5fbd2b84d82e7e0 6976 interpreters optional slcfitsio_0.3.8+nosvn-6.debian.tar.xz -BEGIN PGP SIGNATURE- iQJGBAEBCAAwFiEEP0ZDkUmP6HS9tdmPISSqGYN4XJAFAmFSvt8SHHJhZmFlbEBk ZWJpYW4ub3JnAAoJECEkqhmDeFyQYBoP/21WEsSTZHS8e90pqBCgtx0PdvRJd/uI
Bug#995187: qtwebengine-opensource-src FTBFS on mips*: unistd_nr_{n32,n64,o32}.h no linger exported by the kernel
Adrian Bunk 于2021年9月28日周二 上午12:06写道： > > Source: qtwebengine-opensource-src > Version: 5.15.5+dfsg-2 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/fetch.php?pkg=qtwebengine-opensource-src=mips64el=5.15.6%2Bdfsg-1=1632387575=0 > > ... > FAILED: obj/sandbox/linux/seccomp_bpf/syscall_set.o > /usr/bin/g++ -MMD -MF obj/sandbox/linux/seccomp_bpf/syscall_set.o.d > -DSANDBOX_IMPLEMENTATION -DUSE_UDEV -DUSE_AURA=1 -DUSE_NSS_CERTS=1 > -DUSE_OZONE=1 -DOFFICIAL_BUILD -DTOOLKIT_QT -D_FILE_OFFSET_BITS=64 > -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DNO_UNWIND_TABLES > -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -DNDEBUG -DNVALGRIND > -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DOPENSSL_NO_ASM -Igen > -I../../3rdparty/chromium > -I../../3rdparty/chromium/third_party/perfetto/include > -Igen/third_party/perfetto/build_config -Igen/third_party/perfetto -Igen > -Igen -Igen -Igen -I../../3rdparty/chromium/third_party/abseil-cpp > -I../../3rdparty/chromium/third_party/boringssl/src/include > -I../../3rdparty/chromium/third_party/protobuf/src -Igen/protoc_out > -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector > -fno-unwind-tables -fno-asynchronous-unwind-tables -fPIC -pipe -pthread > -D__SANE_USERSPACE_TYPES__ -mips64r2 -Wa,-mips64r2 -Wall -U_FORTIFY_SOURCE > -D_FORTIFY_SOURCE=2 -Wno-unused-local-typedefs -Wno-maybe-uninitialized > -Wno-deprecated-declarations -fno-delete-null-pointer-checks -Wno-comments > -Wno-packed-not-aligned -Wno-dangling-else -Wno-missing-field-initializers > -Wno-unused-parameter -O2 -fno-ident -fdata-sections -ffunction-sections > -fno-omit-frame-pointer -g0 -fvisibility=hidden -std=gnu++14 -Wno-narrowing > -Wno-class-memaccess -Wno-attributes -Wno-class-memaccess > -Wno-subobject-linkage -Wno-invalid-offsetof -Wno-return-type > -Wno-deprecated-copy -fno-exceptions -fno-rtti -fvisibility-inlines-hidden -c > ../../3rdparty/chromium/sandbox/linux/bpf_dsl/syscall_set.cc -o > obj/sandbox/linux/seccomp_bpf/syscall_set.o > In file included from > ../../3rdparty/chromium/sandbox/linux/bpf_dsl/syscall_set.cc:12: > ../../3rdparty/chromium/sandbox/linux/bpf_dsl/linux_syscall_ranges.h:47:10: > fatal error: asm/unistd_nr_n64.h: No such file or directory >47 | #include // for __NR_64_Linux and > __NR_64_Linux_syscalls https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ccb21774863add648e709337919d2cfeefe4be49 This commit change the struct of unistd*.h files. And I guess that we can just drop mipsel-linux-5.patch now. I am testing it. > | ^ > compilation terminated. > ... > > > Context: > https://sources.debian.org/src/qtwebengine-opensource-src/5.15.6+dfsg-1/debian/patches/mipsel-linux-5.patch/ > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ccb21774863a > -- YunQiang Su
Bug#995216: simple-scan: B Text scans saved as gibberish
Package: simple-scan Found: 3.38.1-1 Severity: grave Hi, Starting earlier today (between scans) simple-scan on bullseye became unable to save B text scans properly. Now they are saved as gibberish. It is possible the files are being saved in a format not understood by my PDF reader, but I could not find a common reader that worked: I tried evince, muPDF, gscan2pdf, an old trial version of Master PDF Editor, and GIMP and Inkscape. Only LibreOffice Draw got it right. In accordance with the recommendations here [1] I marked the bug 'grave' because I lost data because of it (or so it seemed when I wrote). The bug is also somewhat treacherous: The image on the screen looks fine. One has to open the saved file to see the issue. Thanks for simple-scan! It's a great and best-in-class program! Kind regards Felix Lechner [1] https://www.debian.org/Bugs/Developer#severities
Bug#995206: marked as done (r-bioc-altcdfenvs: autopkgtest regression)
Your message dated Tue, 28 Sep 2021 06:04:20 + with message-id and subject line Bug#995206: fixed in r-bioc-altcdfenvs 1:2.54.0-2 has caused the Debian Bug report #995206, regarding r-bioc-altcdfenvs: autopkgtest regression 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.) -- 995206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995206 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: r-bioc-altcdfenvs Version: 1:2.54.0-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org | E: Unable to locate package r-cran-r-unit | pkg-r-autopkgtestFAIL badpkg | blame: r-bioc-altcdfenvs Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: r-bioc-altcdfenvs Source-Version: 1:2.54.0-2 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of r-bioc-altcdfenvs, 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. Nilesh Patra (supplier of updated r-bioc-altcdfenvs 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: Tue, 28 Sep 2021 11:22:57 +0530 Source: r-bioc-altcdfenvs Architecture: source Version: 1:2.54.0-2 Distribution: unstable Urgency: medium Maintainer: Debian R Packages Maintainers Changed-By: Nilesh Patra Closes: 995206 Changes: r-bioc-altcdfenvs (1:2.54.0-2) unstable; urgency=medium . * Team Upload. * d/t/autopkgtest-pkg-r.conf: Fix the name of test-depends, r-cran-r-unit => r-bioc-runit (Closes: #995206) Checksums-Sha1: b8071f60f1ff0b0f8c823d4eb46e2f0014430b65 2227 r-bioc-altcdfenvs_2.54.0-2.dsc c1dc16497ebee9ee81c5fe68fabaab60086a591d 4520 r-bioc-altcdfenvs_2.54.0-2.debian.tar.xz 18e5828d6da4ad37a9c079b110146da99c7b44d4 10722 r-bioc-altcdfenvs_2.54.0-2_amd64.buildinfo Checksums-Sha256: f7d6c18324f95fbc59df2b11662ef54abf5a0f6638e464d5d22c2e0bf7c96db9 2227 r-bioc-altcdfenvs_2.54.0-2.dsc d8ec9c29e97bd37fefe22f1a98b19affa46c57b0a5fff5c4e2fc6e916f7926f5 4520 r-bioc-altcdfenvs_2.54.0-2.debian.tar.xz a9631cc8891a5491be5f97eb160b536d6a40085b86507663a2d187c62e7040b4 10722 r-bioc-altcdfenvs_2.54.0-2_amd64.buildinfo Files: 25cd502b87386a3c4c3bd77c0276f105 2227 gnu-r optional r-bioc-altcdfenvs_2.54.0-2.dsc ff9afca40a70a15adee1f22d61c9ac70 4520 gnu-r optional r-bioc-altcdfenvs_2.54.0-2.debian.tar.xz 66e0cb9b7a25fd160797dd05b4b2ceda 10722 gnu-r optional r-bioc-altcdfenvs_2.54.0-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmFSrx0UHG5wYXRyYTk3 NEBnbWFpbC5jb20ACgkQALrnSzQzafHVQQ//Y2uw57pCWUXLyp15E9eunnoQO9vv uwxnYbqluTTnpnrNn7ka9HAMFx4W/u/DbPdn4LVnwJ+u3q8NTC7fyizh+gWLWood DuKFBGifu9520Upc5Ohf0b/O0Zy7GxOAiFT0zbj8eFB/b/tWrBpxbCKbatrbAsmV LGgXk+ANA49jtIeGT13QwbgTl3C9S0RFjjqt5ok60RVvozatgRgGFDrkmjpSuk6H h2+WO+p9cnQhvnCJkqWzK+mYAG04yH2I63+thtX/qhQQFGZ8o+2E2157VJeCYnXq R6J2rVTMqsw5mcIesXJfOF4PspGCORhOQdThTlf56IG/BeFW73btZtjUXA7Rfhr2 QP2JheWpQ/4Em4tJbtmSVBJLXxAVGZVMZ0CQXSAfuwoytQjs/Oh0J9c/saltvdMc D3dXBnTyUqKgzmo3qsyAQjC5a50hIWr+hh0ZzZRqS96TXh1SMCjCQr4HwTwuXo31 j47++y1S4Mwp/tQrqwydiSFSSg8pMuikI5GPlZp8a/h6DFY7wxWMzoNUKy2gafEf 4BtAGpmkVihBMV/1gGkXbrWBDB+1aZdLOmiUlUoRdvaLbPHe6iih3JDF0LI2OuXK bczTIGS3K73ULm8d3gjGhVbB9XQpOi6EkBQmUVr1sc/muyS1fWy5Pdl0muJKgeff 6iCOKC0LWuJlS1Y= =IrQO -END PGP SIGNATURE End Message ---
Bug#995215: postgresql-semver: Wait for acceptance of backport
Package: postgresql-semver Severity: serious The sole purpose of this bug is to keep version 0.31.1-3 out of testing until version 0.31.1-2~bpo11+1 is in backports.
