Bug#1071090: iso-codes: installs broken symbolic links
control: retitle -1 localepurge: should remove symlinks as well control: tag -1 -unreproducible Am 16.09.24 um 06:50 schrieb Martin-Éric Racine: I checked and noticed the same issue on all of my hosts, not just that Sid chroot. Anyhow, I think that I found the cause: I use 'localepurge' to have APT automatically remove unused localizations and save disk space. As far as I can tell, the bug is that it removes any unused FILE shipped by a package, but not symbolic links. We are therefore left with 2 symbolic links pointing to nothing, and 'adequate' complains about them. 'localepurge' should probably manage those too. Hi, thanks for digging deeper and finding the cause. Now it makes sense. :-) Regards, Tobias
Bug#1071090: iso-codes: installs broken symbolic links
control: reopen -1 control: tag -1 unreproducible Am 15.09.24 um 10:11 schrieb Martin-Éric Racine: This IS in a Sid chroot. I have tried purging and re-installing. Same result. Martin-Éric Thanks for investigating again. I'm reopening the bug, but it's not reproducible by me, so tagging accordingly. Maybe I'll get another report about a similar problem with some hints where the problem might be -- right now, I don't have a clue what's going on in your sid chroot versus mine. Regards, Tobias
Bug#1071090: iso-codes: installs broken symbolic links
Am 14.09.24 um 07:48 schrieb Martin-Éric Racine: $ LC_ALL=C ls -l /usr/share/locale/fil/LC_MESSAGES/ total 0 lrwxrwxrwx 1 root root 13 2024-09-13 22:45 iso_3166.mo -> iso_3166-1.mo lrwxrwxrwx 1 root root 13 2024-09-13 22:45 iso_3166_2.mo -> iso_3166-2.mo You might wanna check whether other files failed to install. Martin-Éric This is the output on my system: $ adequate iso-codes $ $ LC_ALL=C ls -l /usr/share/locale/fil/LC_MESSAGES/ total 44K -rw-r--r-- 1 root root 11K Jan 14 2024 iso_15924.mo -rw-r--r-- 1 root root 24K Jan 14 2024 iso_3166-1.mo -rw-r--r-- 1 root root 3.0K Jan 14 2024 iso_3166-2.mo lrwxrwxrwx 1 root root 13 Jan 14 2024 iso_3166.mo -> iso_3166-1.mo lrwxrwxrwx 1 root root 13 Jan 14 2024 iso_3166_2.mo -> iso_3166-2.mo $ So I cannot reproduce this. Also, I'm not convinced that there is an actual problem in the iso-codes package, because I can see both files in the created .deb package. They are also listed in the package's contents, see e. g. https://packages.debian.org/sid/all/iso-codes/filelist. I would guess that there is some strange error in the system you are using for this test. Did you try to create a clean sid chroot and install iso-codes from scratch? Are those files still missing in that environment? Regards, Tobias
Bug#1072742: On Romanian translations in the iso-codes package
control: tag -1 pending Am 05.08.24 um 19:57 schrieb Remus-Gabriel Chelu: Last night, I tried to upload the corrected "iso-3166-2-ro.po" file into "iso-codes_Weblate", but ... I couldn't do it! Hi Remus-Gabriel, thanks again for this update, I've now committed the file to the repository, which in turn should appear on Weblate soon. Regards, Tobias
Bug#1079750: setuptools test command is removed
Hi, we encountered this issue in Ubuntu too, the attached patch should to fix it. Cheers, Tobias >From 9b7ce9d05185ec427fbb12ff0bf9a8f49c8506ed Mon Sep 17 00:00:00 2001 From: Tobias Heider Date: Tue, 10 Sep 2024 21:26:41 +0200 Subject: [PATCH] Run tests without setuptools setuptools dropped support for tests_require and fails so run tests directly instead. --- debian/tests/testsuite | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/tests/testsuite b/debian/tests/testsuite index 23403ad..aa9f280 100755 --- a/debian/tests/testsuite +++ b/debian/tests/testsuite @@ -1,2 +1,2 @@ #!/bin/bash -python3 setup.py test +python3 -m unittest prometheus_xmpp.tests.test_suite -- 2.45.2
Bug#1041004: firmware-b43-installer: Drivers in this package are not available in debian-12.0.0-amd64-netinst.iso at time of writing.
Control: tags -1 wontfix Control: close -1 Hi David, Not sure if I got your report correcty; firmware-b43-installer merley downloads the firmware files, as the firmware files cannot be distributed IIUIC due to no redistributions rights granted by Broadcom. If my understanding is correct that you'd expect the firmware files to be present without downloading them, that would be undortunatly if my IIUIC is right, not fixable. (If I misunderstood, please feel free to reopen this bug and expand a bit, thanks) -- tobi On Thu, 13 Jul 2023 16:52:06 -0400 David Peacock wrote: > Package: firmware-b43-installer > Severity: normal > X-Debbugs-Cc: david.j.peac...@gmail.com > > Dear Maintainer, > > Upon attempting to install Debian 12 using [0] on my early 2013 Retina > Macbook Pro, I discovered that the drivers needed to operate the > Broadcom wireless card included were not available. It was my > understanding that these drivers should be included in the newly > established non-free-firmware repository. > > I'm raising this bug report purely to bring this to attention in hope > that it's possible to add these drivers to the Bookworm netinst image to > avoid having to deal with this when installing on various models of > Macbook Pro. > > Thank you > David > > [0] https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-12.0.0-amd64-netinst.iso > > -- System Information: > Debian Release: 12.0 > APT prefers stable-security > APT policy: (500, 'stable-security'), (500, 'stable') > Architecture: amd64 (x86_64) > > Kernel: Linux 6.1.0-10-amd64 (SMP w/24 CPU threads; PREEMPT) > Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages firmware-b43-installer depends on: > pn b43-fwcutter > ii bzip2 1.0.8-5+b1 > ii ca-certificates 20230311 > ii pciutils 1:3.9.0-4 > ii wget 1.21.3-1+b2 > > firmware-b43-installer recommends no packages. > > firmware-b43-installer suggests no packages. > >
Bug#1079404: gnucash: warnings for incompatible bytecode version
Package: gnucash Version: 1:5.8-1 Severity: normal Dear Maintainer, since upgrading to trixie, when I launch gnucash from the command line, I get ~200 warnings like this: ;;; WARNING: loading compiled file /usr/lib/x86_64-linux-gnu/guile/3.0/site-ccache/gnucash/qif-import/qif-file.go failed: ;;; In procedure load-thunk-from-memory: incompatible bytecode version -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (420, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.10.3-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnucash depends on: ii gnucash-common 1:5.8-1 ii guile-3.0 3.0.9-1+b2 ii guile-3.0-libs 3.0.9-1+b2 ii libaqbanking44 6.5.12beta-1 ii libboost-filesystem1.83.0 1.83.0-3.1 ii libboost-locale1.83.0 1.83.0-3.1 ii libboost-program-options1.83.0 1.83.0-3.1 ii libc6 2.39-6 ii libcairo2 1.18.0-3+b1 ii libcrypt-ssleay-perl0.73.06-2+b3 ii libdate-manip-perl 6.95-1 ii libdbi1t64 0.9.0-6.1 ii libfinance-quote-perl 1.62-1 ii libgcc-s1 14.2.0-1 ii libgdk-pixbuf-2.0-0 2.42.12+dfsg-1 ii libglib2.0-0t64 2.81.1-3 ii libgtk-3-0t64 3.24.43-1 ii libgwengui-gtk3-79t64 5.11.2beta-2 ii libgwenhywfar79t64 5.11.2beta-2 ii libhtml-tableextract-perl 2.15-2 ii libhtml-tree-perl 5.07-3 ii libicu7272.1-5 ii libofx7t64 1:0.10.9-1.1+b1 ii libpango-1.0-0 1.54.0+ds-1 ii libpangocairo-1.0-0 1.54.0+ds-1 ii libpython3.12t643.12.4-3 ii libsecret-1-0 0.21.4-1+b1 ii libstdc++6 14.2.0-1 ii libwebkit2gtk-4.1-0 2.44.2-1+b2 ii libwww-perl 6.77-1 ii libxml2 2.9.14+dfsg-1.3+b3 ii perl5.38.2-5 ii zlib1g 1:1.3.dfsg+really1.3.1-1 Versions of packages gnucash recommends: ii gnucash-docs 5.6-1 ii python3-gnucash 1:5.8-1 pn yelp Versions of packages gnucash suggests: pn libdbd-mysql pn libdbd-pgsql pn libdbd-sqlite3 -- no debconf information
Bug#1075105: jxrlib: diff for NMU version 1.2~git20170615.f752187-5.3
Control: tags 1075105 + pending Dear maintainer, I've prepared an NMU for jxrlib (versioned as 1.2~git20170615.f752187-5.3) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -Nru jxrlib-1.2~git20170615.f752187/debian/changelog jxrlib-1.2~git20170615.f752187/debian/changelog --- jxrlib-1.2~git20170615.f752187/debian/changelog 2024-03-17 05:12:37.0 +0100 +++ jxrlib-1.2~git20170615.f752187/debian/changelog 2024-08-17 09:05:27.0 +0200 @@ -1,3 +1,11 @@ +jxrlib (1.2~git20170615.f752187-5.3) unstable; urgency=medium + + * Non-maintainer upload. + * Apply patch to fix building with GCC-14s, thanks to YOKOTA Hiroshi for +preparing it. (Closes: #1075105) + + -- Tobias Frost Sat, 17 Aug 2024 09:05:27 +0200 + jxrlib (1.2~git20170615.f752187-5.2) unstable; urgency=medium * Non-maintainer upload. diff -Nru jxrlib-1.2~git20170615.f752187/debian/patches/0013-jxrlib-ftbfs-with-GCC-14.patch jxrlib-1.2~git20170615.f752187/debian/patches/0013-jxrlib-ftbfs-with-GCC-14.patch --- jxrlib-1.2~git20170615.f752187/debian/patches/0013-jxrlib-ftbfs-with-GCC-14.patch 1970-01-01 01:00:00.0 +0100 +++ jxrlib-1.2~git20170615.f752187/debian/patches/0013-jxrlib-ftbfs-with-GCC-14.patch 2024-08-17 09:00:32.0 +0200 @@ -0,0 +1,33 @@ +From: YOKOTA Hiroshi +Date: Thu, 25 Jul 2024 15:03:31 +0900 +Subject: jxrlib: ftbfs with GCC-14 +MIME-Version: 1.0 +Content-Type: text/plain; charset="utf-8" +Content-Transfer-Encoding: 8bit + +Bug-Debian: https://bugs.debian.org/1075105 + +_byteswap_ulong() is defined in image/sys/strcodec.c + + +/usr/bin/cc -DDISABLE_PERF_MEASUREMENT -D__ANSI__ -Djpegxr_EXPORTS -I"/<>/common/include" -I"/<>/image/sys" -I"/<>/jxrgluelib" -I"/<>/jxrtestlib" -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -Wextra -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -w -MD -MT CMakeFiles/jpegxr.dir/image/encode/strenc.c.o -MF CMakeFiles/jpegxr.dir/image/encode/strenc.c.o.d -o CMakeFiles/jpegxr.dir/image/encode/strenc.c.o -c "/<>/image/encode/strenc.c" +/<>/image/decode/segdec.c: In function ‘_load4’: +/<>/image/decode/segdec.c:68:12: error: implicit declaration of function ‘_byteswap_ulong’ [-Wimplicit-function-declaration] + 68 | return _byteswap_ulong(v); + |^~~ +--- + image/decode/segdec.c | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/image/decode/segdec.c b/image/decode/segdec.c +index 3c890af..5d55f06 100644 +--- a/image/decode/segdec.c b/image/decode/segdec.c +@@ -63,6 +63,7 @@ static U32 _FORCEINLINE _load4(void* pv) + v |= ((U32)((U16 *) pv)[1]) << 16; + return _byteswap_ulong(v); + #else // _M_IA64 ++U32 _byteswap_ulong(U32 bits); // from image/sys/strcodec.c + U32 v; + memcpy(&v, pv, sizeof(U32)); + return _byteswap_ulong(v); diff -Nru jxrlib-1.2~git20170615.f752187/debian/patches/0014-FTBFS-fix-for-pointer-type-mismatch.patch jxrlib-1.2~git20170615.f752187/debian/patches/0014-FTBFS-fix-for-pointer-type-mismatch.patch --- jxrlib-1.2~git20170615.f752187/debian/patches/0014-FTBFS-fix-for-pointer-type-mismatch.patch 1970-01-01 01:00:00.0 +0100 +++ jxrlib-1.2~git20170615.f752187/debian/patches/0014-FTBFS-fix-for-pointer-type-mismatch.patch 2024-08-17 09:00:32.0 +0200 @@ -0,0 +1,88 @@ +From: YOKOTA Hiroshi +Date: Thu, 25 Jul 2024 16:00:12 +0900 +Subject: FTBFS fix for pointer type mismatch + +Bug-Debian: https://bugs.debian.org/1075105 +--- + jxrencoderdecoder/JxrDecApp.c | 2 +- + jxrtestlib/JXRTest.c | 10 +- + jxrtestlib/JXRTestTif.c | 4 ++-- + 3 files changed, 8 insertions(+), 8 deletions(-) + +diff --git a/jxrencoderdecoder/JxrDecApp.c b/jxrencoderdecoder/JxrDecApp.c +index 5779eb8..f07b3c4 100644 +--- a/jxrencoderdecoder/JxrDecApp.c b/jxrencoderdecoder/JxrDecApp.c +@@ -428,7 +428,7 @@ ERR WmpDecAppCreateEncoderFromExt( + Call(GetTestEncodeIID(szExt, &pIID)); + + // Create encoder +-Call(PKTestFactory_CreateCodec(pIID, ppIE)); ++Call(PKTestFactory_CreateCodec(pIID, (void **)ppIE)); + + Cleanup: + return err; +diff --git a/jxrtestlib/JXRTest.c b/jxrtestlib/JXRTest.c +index b2a9b64..790b0de 100644 +--- a/jxrtestlib/JXRTest.c b/jxrtestlib/JXRTest.c +@@ -198,7 +198,7 @@ ERR PKTestFactory_CreateDecoderFromFile(const char* szFilename, PKImageDecode** + ERR err = WMP_errSuccess; + + char *pExt = NULL; +-PKIID* pIID = NULL; ++const PKIID* pIID = NULL; + + struct WMPStream* pStream = NULL; + PKImageDecode* pDecoder = NULL; +@@ -214,7 +214,7 @@ ERR PKTestFactory_CreateDecoderFromFile(const char* szFilename, PKImageDecode** + Call(CreateWS_File(&pStream, szFilename, "rb")); + + // Create decoder +-C
Bug#1075105: jxrlib: diff for NMU version 1.2~git20170615.f752187-5.3
Control: tags 1075105 + pending Dear maintainer, I've prepared an NMU for jxrlib (versioned as 1.2~git20170615.f752187-5.3) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -Nru jxrlib-1.2~git20170615.f752187/debian/changelog jxrlib-1.2~git20170615.f752187/debian/changelog --- jxrlib-1.2~git20170615.f752187/debian/changelog 2024-03-17 05:12:37.0 +0100 +++ jxrlib-1.2~git20170615.f752187/debian/changelog 2024-08-17 09:05:27.0 +0200 @@ -1,3 +1,11 @@ +jxrlib (1.2~git20170615.f752187-5.3) unstable; urgency=medium + + * Non-maintainer upload. + * Apply patch to fix building with GCC-14s, thanks to YOKOTA Hiroshi for +preparing it. (Closes: #1075105) + + -- Tobias Frost Sat, 17 Aug 2024 09:05:27 +0200 + jxrlib (1.2~git20170615.f752187-5.2) unstable; urgency=medium * Non-maintainer upload. diff -Nru jxrlib-1.2~git20170615.f752187/debian/patches/0013-jxrlib-ftbfs-with-GCC-14.patch jxrlib-1.2~git20170615.f752187/debian/patches/0013-jxrlib-ftbfs-with-GCC-14.patch --- jxrlib-1.2~git20170615.f752187/debian/patches/0013-jxrlib-ftbfs-with-GCC-14.patch 1970-01-01 01:00:00.0 +0100 +++ jxrlib-1.2~git20170615.f752187/debian/patches/0013-jxrlib-ftbfs-with-GCC-14.patch 2024-08-17 09:00:32.0 +0200 @@ -0,0 +1,33 @@ +From: YOKOTA Hiroshi +Date: Thu, 25 Jul 2024 15:03:31 +0900 +Subject: jxrlib: ftbfs with GCC-14 +MIME-Version: 1.0 +Content-Type: text/plain; charset="utf-8" +Content-Transfer-Encoding: 8bit + +Bug-Debian: https://bugs.debian.org/1075105 + +_byteswap_ulong() is defined in image/sys/strcodec.c + + +/usr/bin/cc -DDISABLE_PERF_MEASUREMENT -D__ANSI__ -Djpegxr_EXPORTS -I"/<>/common/include" -I"/<>/image/sys" -I"/<>/jxrgluelib" -I"/<>/jxrtestlib" -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -Wextra -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -w -MD -MT CMakeFiles/jpegxr.dir/image/encode/strenc.c.o -MF CMakeFiles/jpegxr.dir/image/encode/strenc.c.o.d -o CMakeFiles/jpegxr.dir/image/encode/strenc.c.o -c "/<>/image/encode/strenc.c" +/<>/image/decode/segdec.c: In function ‘_load4’: +/<>/image/decode/segdec.c:68:12: error: implicit declaration of function ‘_byteswap_ulong’ [-Wimplicit-function-declaration] + 68 | return _byteswap_ulong(v); + |^~~ +--- + image/decode/segdec.c | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/image/decode/segdec.c b/image/decode/segdec.c +index 3c890af..5d55f06 100644 +--- a/image/decode/segdec.c b/image/decode/segdec.c +@@ -63,6 +63,7 @@ static U32 _FORCEINLINE _load4(void* pv) + v |= ((U32)((U16 *) pv)[1]) << 16; + return _byteswap_ulong(v); + #else // _M_IA64 ++U32 _byteswap_ulong(U32 bits); // from image/sys/strcodec.c + U32 v; + memcpy(&v, pv, sizeof(U32)); + return _byteswap_ulong(v); diff -Nru jxrlib-1.2~git20170615.f752187/debian/patches/0014-FTBFS-fix-for-pointer-type-mismatch.patch jxrlib-1.2~git20170615.f752187/debian/patches/0014-FTBFS-fix-for-pointer-type-mismatch.patch --- jxrlib-1.2~git20170615.f752187/debian/patches/0014-FTBFS-fix-for-pointer-type-mismatch.patch 1970-01-01 01:00:00.0 +0100 +++ jxrlib-1.2~git20170615.f752187/debian/patches/0014-FTBFS-fix-for-pointer-type-mismatch.patch 2024-08-17 09:00:32.0 +0200 @@ -0,0 +1,88 @@ +From: YOKOTA Hiroshi +Date: Thu, 25 Jul 2024 16:00:12 +0900 +Subject: FTBFS fix for pointer type mismatch + +Bug-Debian: https://bugs.debian.org/1075105 +--- + jxrencoderdecoder/JxrDecApp.c | 2 +- + jxrtestlib/JXRTest.c | 10 +- + jxrtestlib/JXRTestTif.c | 4 ++-- + 3 files changed, 8 insertions(+), 8 deletions(-) + +diff --git a/jxrencoderdecoder/JxrDecApp.c b/jxrencoderdecoder/JxrDecApp.c +index 5779eb8..f07b3c4 100644 +--- a/jxrencoderdecoder/JxrDecApp.c b/jxrencoderdecoder/JxrDecApp.c +@@ -428,7 +428,7 @@ ERR WmpDecAppCreateEncoderFromExt( + Call(GetTestEncodeIID(szExt, &pIID)); + + // Create encoder +-Call(PKTestFactory_CreateCodec(pIID, ppIE)); ++Call(PKTestFactory_CreateCodec(pIID, (void **)ppIE)); + + Cleanup: + return err; +diff --git a/jxrtestlib/JXRTest.c b/jxrtestlib/JXRTest.c +index b2a9b64..790b0de 100644 +--- a/jxrtestlib/JXRTest.c b/jxrtestlib/JXRTest.c +@@ -198,7 +198,7 @@ ERR PKTestFactory_CreateDecoderFromFile(const char* szFilename, PKImageDecode** + ERR err = WMP_errSuccess; + + char *pExt = NULL; +-PKIID* pIID = NULL; ++const PKIID* pIID = NULL; + + struct WMPStream* pStream = NULL; + PKImageDecode* pDecoder = NULL; +@@ -214,7 +214,7 @@ ERR PKTestFactory_CreateDecoderFromFile(const char* szFilename, PKImageDecode** + Call(CreateWS_File(&pStream, szFilename, "rb")); + + // Create decoder +-C
Bug#1078747: python3-cryptography: cryptography.exceptions fails to import
Package: python3-cryptography Version: 42.0.5-2+b1 Followup-For: Bug #1078747 Hi, This was caused by the recent split of legacy providers from the main OpenSSL package. Installing openssl-provider-legacy "fixes" the error. These are the aloorithms considered "legacy": Hashing: MD2, MD4, MDC2, WHIRLPOOL, RIPEMD160 Ciphers: Blowfish, CAST, DES, IDEA, RC2, RC4, RC5, SEED KDF: PBKDF1, PVKKDF (From https://manpages.debian.org/bookworm/openssl/OSSL_PROVIDER-legacy.7ssl.en.html) Some of the software I tried works with setting CRYPTOGRAPHY_OPENSSL_NO_LEGACY=1, because they obviously don't use any of the legacy algorithms... I wonder if this really needs to be a hard fail in Debian? Or do we want to patch every cryptography-using tool with a line like os.environ['CRYPTOGRAPHY_OPENSSL_NO_LEGACY'] = "1" to "promise" not to require the legacy ciphers? And every package which needs these ciphers must add a dependency on openssl-provider-legacy? I currently don't have a good solution. Making python3-cryptography depend on openssl-provider-legacy feels kinda wrong to me... Regargs, Tobias -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.10.4-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de:en_GB:en_US Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-cryptography depends on: ii libc62.39-7 ii libgcc-s114.2.0-2 ii libssl3t64 3.3.1-6 ii python3 3.12.5-1 ii python3-cffi-backend [python3-cffi-backend-api-min] 1.17.0-1 pn python3-cffi-backend-api-max python3-cryptography recommends no packages. Versions of packages python3-cryptography suggests: pn python-cryptography-doc pn python3-cryptography-vectors -- no debconf information
Bug#1078342: pandoc: Memory leak when converting markdown files
Package: pandoc Version: 3.1.3+ds-3 Severity: normal Dear Maintainer, I have a large markdown file (11M) that I cannot convert to epub because pandoc runs out of memory. As far as i can see, this has already been fixed upstream: https://github.com/jgm/pandoc/blob/main/changelog.md#pandoc-315-2023-07-07 -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (420, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.9.12-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pandoc depends on: ii libc62.39-6 ii libffi8 3.4.6-1 ii libgmp10 2:6.3.0+dfsg-2+b1 ii liblua5.4-0 5.4.6-3+b1 ii libyaml-0-2 0.2.5-1+b1 ii pandoc-data 3.1.3-2 ii zlib1g 1:1.3.dfsg+really1.3.1-1 pandoc recommends no packages. Versions of packages pandoc suggests: pn citation-style-language-styles pn context pn ghc pn groff pn libjs-katex pn libjs-mathjax pn librsvg2-bin ii nodejs 20.15.0+dfsg-1 pn pandoc-citeproc ii perl5.38.2-5 ii php8.2 [php]8.2.21-1 pn python pn r-base-core ii ruby1:3.1+nmu1 pn texlive-latex-extra ii texlive-latex-recommended 2024.20240706-1 pn texlive-luatex pn texlive-xetex pn wkhtmltopdf -- no debconf information
Bug#1072742: On Romanian translations in the iso-codes package
Hi, thanks for the updated file. I'm currently on vacation, but I'll look into the weblate issue next week when I'm back. If all else fails, I can always apply your fixes manually to iso-codes. Regards, Tobias 05.08.2024 19:58:07 Remus-Gabriel Chelu : > Hello, > > > În 24.07.2024 22:18, Remus-Gabriel Chelu a scris: > >> >> >> Hi, >> >> I just published on the mailing list of the Romanian Debian team >> <https://lists.debian.org/debian-l10n-romanian/2024/07/>, the corrected >> "iso-3166-2-ro.po" file, with a request for review [RFR]. >> >> I hope that at the beginning of next month (probably Sunday, the 4th day >> of the month), I will upload it to Weblate with the changes proposed by the >> team. > > Last night, I tried to upload the corrected "iso-3166-2-ro.po" file into > "iso-codes_Weblate", but ... I couldn't do it! > > On the project page, in fact on the page of each component of the project, > there is a warning message > > "The translation is temporarily closed for contributions due to maintenance, > please come back later. > The translation was automatically locked due to following alerts: Could not > push the repository."; > clicking on the «Could not push the repository.» link will display the > message: > > "Could not push the repository. > > Weblate could not push changes to the upstream repository. > > kex_exchange_identification: Connection closed by remote host > Connection closed by 2607:f8f0:614:1::1274:44 port 22 > fatal: Could not read from remote repository. > > Please make sure you have the correct access rights > and the repository exists. > (128) > > Weblate will retry the operation once it is needed again, > so the alert might disappear for the temporary issues. > Appeared 3 months ago, last seen 3 months ago" > > > That's why I'm attaching the corrected file here, so as not to open another > bug report on the "iso-codes" project. > > -- > Greetings, > Remus-Gabriel
Bug#1072381: Provide gtk4-client package
On Sun, 4 Aug 2024 07:57:32 +0300 Marko Lindqvist wrote: > You may want to backport https://redmine.freeciv.org/issues/750 > It's a fix to gtk4-client crash occurring on some environments > (avoided by luck in others). Last I tested, Trixie was affected. > Thanks for the info! I see that there are many patches listed on the issue... Do I need all of them?
Bug#1072381: Provide gtk4-client package
Package prepared and uploaded -- as this introduces a new binary package this needs to pass the NEW queue, so it might take some time until it will be available. -- tobi
Bug#1077782: contributors.debian.org: users listed as "voters" but have not voted.
Package: contributors.debian.org Severity: normal While doing MIA work I saw people recorded as voters "until April 2024", but the voters list [1] does not list them as having actual having voted in the (only) vote in 2024, the DPL vote. For example: bossekr camrdale cowboy ccheney [1] https://www.debian.org/vote/2024/vote_001_voters.txt -- tobi
Bug#1077781: netsend: d/control Homepage is invalid
Source: netsend Severity: minor berlinos is dead since years. -- System Information: Debian Release: trixie/sid APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.9.11-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1077589: boost1.83: diff for NMU version 1.83.0-3.1
On Wed, Jul 31, 2024 at 10:20:45PM +0200, Anton Gladky wrote: > Hi Tobias, > > thanks for the update! Please go ahead with the immediate upload. > Please also update the git. Thanks. Regards Thanks for the heads up! Rescheduled to 0-day and salsa MR merged. -- tobi > > Anton > > > Am Di., 30. Juli 2024 um 10:48 Uhr schrieb Tobias Frost : > > > Package: boost1.83 > > Version: 1.83.0-3 > > Severity: normal > > Tags: patch pending > > > > > > Dear maintainer, > > > > I've prepared an NMU for boost1.83 (versioned as 1.83.0-3.1) and > > uploaded it to DELAYED/5. Please feel free to tell me if I > > should delay it longer. > > > > Regards. > > > >
Bug#1077589: boost1.83: diff for NMU version 1.83.0-3.1
Package: boost1.83
Version: 1.83.0-3
Severity: normal
Tags: patch pending
Dear maintainer,
I've prepared an NMU for boost1.83 (versioned as 1.83.0-3.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru boost1.83-1.83.0/debian/changelog boost1.83-1.83.0/debian/changelog
--- boost1.83-1.83.0/debian/changelog 2024-05-27 06:59:36.0 +0200
+++ boost1.83-1.83.0/debian/changelog 2024-07-30 09:09:13.0 +0200
@@ -1,3 +1,13 @@
+boost1.83 (1.83.0-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix "Boost.Signals2 causes FTBFS", cherry-picking upstream patch
+ (Closes: #1056100)
+ * Fix "autopkgtest regression with CMake 3.30+", enforcing the new CMP0167
+policy. (Closes: #1076426)
+
+ -- Tobias Frost Tue, 30 Jul 2024 09:09:13 +0200
+
boost1.83 (1.83.0-3) unstable; urgency=medium
* [4b317f3] Add upstream fix for dogecoin. (Closes: #1059133)
diff -Nru boost1.83-1.83.0/debian/patches/70-boost-causing-ftbfs-signal2-part1.patch boost1.83-1.83.0/debian/patches/70-boost-causing-ftbfs-signal2-part1.patch
--- boost1.83-1.83.0/debian/patches/70-boost-causing-ftbfs-signal2-part1.patch 1970-01-01 01:00:00.0 +0100
+++ boost1.83-1.83.0/debian/patches/70-boost-causing-ftbfs-signal2-part1.patch 2024-07-28 10:57:52.0 +0200
@@ -0,0 +1,128 @@
+From 2ba258f7b465e7bde14663ca3a966019b4ec3694 Mon Sep 17 00:00:00 2001
+From: Frank Mori Hess
+Date: Sat, 30 Dec 2023 14:34:58 -0500
+Subject: [PATCH] Fix disconnect by slot when the slot is another signal.
+
+---
+ .../boost/signals2/detail/signal_template.hpp | 48 +++
+ 1 file changed, 39 insertions(+), 9 deletions(-)
+
+diff --git a/libs/signals2/include/boost/signals2/detail/signal_template.hpp b/include/boost/signals2/detail/signal_template.hpp
+index a399883c..4546906d 100644
+--- a/libs/signals2/include/boost/signals2/detail/signal_template.hpp
b/libs/signals2/include/boost/signals2/detail/signal_template.hpp
+@@ -103,9 +103,9 @@ namespace boost
+ BOOST_SIGNALS2_FORWARDED_ARGS(BOOST_SIGNALS2_NUM_ARGS));
+ }
+ template
+- bool operator==(const T &other) const
++ bool contains(const T &other) const
+ {
+- return _fun == other;
++ return _fun.contains(other);
+ }
+ private:
+ BOOST_SIGNALS2_BOUND_EXTENDED_SLOT_FUNCTION_N(BOOST_SIGNALS2_NUM_ARGS)()
+@@ -115,6 +115,8 @@ namespace boost
+ boost::shared_ptr _connection;
+ };
+
++ template
++class BOOST_SIGNALS2_WEAK_SIGNAL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS);
+ template
+ class BOOST_SIGNALS2_SIGNAL_IMPL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS);
+
+@@ -150,6 +152,8 @@ namespace boost
+ typedef GroupCompare group_compare_type;
+ typedef typename detail::slot_call_iterator_t > slot_call_iterator;
++typedef detail::BOOST_SIGNALS2_WEAK_SIGNAL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS)
++ weak_signal_type;
+
+ BOOST_SIGNALS2_SIGNAL_IMPL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS)(const combiner_type &combiner_arg,
+ const group_compare_type &group_compare):
+@@ -531,13 +535,20 @@ namespace boost
+ {
+ (*it)->nolock_disconnect(lock);
+ }else
+-{
+- // check for wrapped extended slot
++{ // check for wrapped extended slot
+ bound_extended_slot_function_type *fp;
+ fp = (*it)->slot().slot_function().template target();
+- if(fp && function_equal(*fp, slot))
++ if(fp && fp->contains(slot))
+ {
+ (*it)->nolock_disconnect(lock);
++ }else
++ { // check for wrapped signal
++weak_signal_type *fp;
++fp = (*it)->slot().slot_function().template target();
++if(fp && fp->contains(slot))
++{
++ (*it)->nolock_disconnect(lock);
++}
+ }
+ }
+ }
+@@ -588,8 +599,6 @@ namespace boost
+ const boost::shared_ptr _mutex;
+ };
+
+- template
+-class BOOST_SIGNALS2_WEAK_SIGNAL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS);
+ }
+
+ template
+@@ -603,8 +612,7 @@ namespace boost
+ typedef detail::BOOST_SIGNALS2_SIGNAL_IMPL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS)
+ impl_class;
+ public:
+- typedef detail::BOOST_SIGNALS2_WEAK_SIGNAL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS)
+- weak_signal_type;
++ typedef typename impl_class::weak_signal_type weak_signal_type;
+ friend class detail::BOOST_SIGNALS2_WEAK_SIGNAL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS)
+ ;
+
+@@ -746,12 +754,24 @@ namespace boost
+ using std::swap;
+ swap(_pimpl, other._pimpl);
+ }
++ bool operator==(const BOOST_SIGN
Bug#1056100: boost1.83: Boost.Signals2 causes FTBFS
Source: boost1.83
Followup-For: Bug #1056100
Control: tags -1 ftbfs patch
I've extraced the upsteam patches, they seem to work for swift-im.
Attached for your convenience.
--
tobi
-- System Information:
Debian Release: trixie/sid
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500,
'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.9.11-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
>From 2ba258f7b465e7bde14663ca3a966019b4ec3694 Mon Sep 17 00:00:00 2001
From: Frank Mori Hess
Date: Sat, 30 Dec 2023 14:34:58 -0500
Subject: [PATCH] Fix disconnect by slot when the slot is another signal.
---
.../boost/signals2/detail/signal_template.hpp | 48 +++
1 file changed, 39 insertions(+), 9 deletions(-)
diff --git a/libs/signals2/include/boost/signals2/detail/signal_template.hpp b/include/boost/signals2/detail/signal_template.hpp
index a399883c..4546906d 100644
--- a/libs/signals2/include/boost/signals2/detail/signal_template.hpp
+++ b/libs/signals2/include/boost/signals2/detail/signal_template.hpp
@@ -103,9 +103,9 @@ namespace boost
BOOST_SIGNALS2_FORWARDED_ARGS(BOOST_SIGNALS2_NUM_ARGS));
}
template
- bool operator==(const T &other) const
+ bool contains(const T &other) const
{
- return _fun == other;
+ return _fun.contains(other);
}
private:
BOOST_SIGNALS2_BOUND_EXTENDED_SLOT_FUNCTION_N(BOOST_SIGNALS2_NUM_ARGS)()
@@ -115,6 +115,8 @@ namespace boost
boost::shared_ptr _connection;
};
+ template
+class BOOST_SIGNALS2_WEAK_SIGNAL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS);
template
class BOOST_SIGNALS2_SIGNAL_IMPL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS);
@@ -150,6 +152,8 @@ namespace boost
typedef GroupCompare group_compare_type;
typedef typename detail::slot_call_iterator_t > slot_call_iterator;
+typedef detail::BOOST_SIGNALS2_WEAK_SIGNAL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS)
+ weak_signal_type;
BOOST_SIGNALS2_SIGNAL_IMPL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS)(const combiner_type &combiner_arg,
const group_compare_type &group_compare):
@@ -531,13 +535,20 @@ namespace boost
{
(*it)->nolock_disconnect(lock);
}else
-{
- // check for wrapped extended slot
+{ // check for wrapped extended slot
bound_extended_slot_function_type *fp;
fp = (*it)->slot().slot_function().template target();
- if(fp && function_equal(*fp, slot))
+ if(fp && fp->contains(slot))
{
(*it)->nolock_disconnect(lock);
+ }else
+ { // check for wrapped signal
+weak_signal_type *fp;
+fp = (*it)->slot().slot_function().template target();
+if(fp && fp->contains(slot))
+{
+ (*it)->nolock_disconnect(lock);
+}
}
}
}
@@ -588,8 +599,6 @@ namespace boost
const boost::shared_ptr _mutex;
};
- template
-class BOOST_SIGNALS2_WEAK_SIGNAL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS);
}
template
@@ -603,8 +612,7 @@ namespace boost
typedef detail::BOOST_SIGNALS2_SIGNAL_IMPL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS)
impl_class;
public:
- typedef detail::BOOST_SIGNALS2_WEAK_SIGNAL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS)
- weak_signal_type;
+ typedef typename impl_class::weak_signal_type weak_signal_type;
friend class detail::BOOST_SIGNALS2_WEAK_SIGNAL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS)
;
@@ -746,12 +754,24 @@ namespace boost
using std::swap;
swap(_pimpl, other._pimpl);
}
+ bool operator==(const BOOST_SIGNALS2_SIGNAL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS) & other) const
+ {
+return _pimpl.get() == other._pimpl.get();
+ }
protected:
virtual shared_ptr lock_pimpl() const
{
return _pimpl;
}
private:
+ // explicit private copy constructor to avoid compiler trying to do implicit conversions to signal
+ explicit BOOST_SIGNALS2_SIGNAL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS)(
+const BOOST_SIGNALS2_SIGNAL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS) & other) BOOST_NOEXCEPT
+ {
+ // noncopyable
+ BOOST_ASSERT(false);
+ }
+
shared_ptr
_pimpl;
};
@@ -802,6 +822,16 @@ namespace boost
shared_pimpl(_weak_pimpl.lock());
return (*shared_pimpl)(BOOST_SIGNALS2_SIGNATURE_ARG_NAMES(BOOST_SI
Bug#1072226: RFS: serious-engine/0~git20230724+dfsg-1 [ITP]
Control: tags -1 moreinfo Hi, a short review: - You're repacking the source. It's not clear to me why you are removing the files. Can you expand? - d/patches: (more a hint, as maintaining patches in Debian will cause extra work down the road for you…): Please consider upstream the patches, the write-to-userdir and the use-system-zlib might be candidates. As serious-source is using CMake, the use-system-zlib patch could be rewritten that CMake is looking for the system's zlib, and if it is found use that, otherwise add the bundled zlib to the include path. (For illustration, I did something similar recently: https://github.com/codereader/DarkRadiant/pull/43) - (Another hint) Please upstream the manpages. - What is the copyright of the logos (debian/*svg)? Where are they from? - (optional) Please add a repository for the packaging on salsa, maybe even under the games team umbrella? (I can create one for you, if you want to go that route.) The README says: Running --- This version of the engine comes with a set of resources (`\SE1_10.GRO`) that allow you to freely use the engine without any additional resources required. However if you want to open or modify levels from Serious Sam Classic: The First Encounter or The Second Encounter (including most user-made levels), you will have to copy the game's resources (.GRO files) into the engine folder. You can buy the original games on Steam, as a part of a bundle with Serious Sam Revolution ( http://store.steampowered.com/app/227780 ) - Are the resources mentioned redistributeable or even DFSG licensed? - The README also mentions level editors. Do they compile for linux? If both could be answered yes, your package could go into main. -- tobi On Thu, May 30, 2024 at 07:34:07PM +0200, Sébastien Noel wrote: > Package: sponsorship-requests > Severity: wishlist > > Dear mentors, > > I am looking for a sponsor for my package "serious-engine": > > * Package name : serious-engine >Version : 0~git20230724+dfsg-1 >Upstream contact : https://github.com/ptitSeb/Serious-Engine/issues > * URL : https://www.croteam.com/serious-sam-source-code-released/ > * License : GPL-2 > * Vcs : https://salsa.debian.org/twolife/serious-engine >Section : contrib/games > > The source builds the following binary packages: > > serious-sam-tfe - Serious Sam - The First Encounter > serious-sam-tse - Serious Sam - The Second Encounter > > To access further information about this package, please visit the > following URL: > > https://mentors.debian.net/package/serious-engine/ > > Alternatively, you can download the package with 'dget' using this > command: > > dget -x > https://mentors.debian.net/debian/pool/contrib/s/serious-engine/serious-engine_0~git20230724+dfsg-1.dsc > > Changes for the initial release: > > serious-engine (0~git20230724+dfsg-1) unstable; urgency=low > . >* Initial release. Closes: #1034630 > > > This package alone isn't of any use; it only contains the game engine, > an engine that has no Free data and therefore is in contrib. > You will need a copy of the original game for this package to be > useful. > Please use game-data-packager to build a .deb of proprietary data (gog > or steam) to unleash the full potential of this code. > > Best Regards, > Sébastien >
Bug#1077252: RFS: tty-clock/2.3-git.2021.11.21.f2f847c-1 [ITA] -- simple terminal clock
Control: tags -1 moreinfo Hi, Thanks for your work on the package! (please not that I will NOT sponsor this upload with from a psedonym; this is a personal policy of mine, others might have different policies) A short review; - d/control VCS-* Please keep the package minimum on salsa, better even in the Debian namespace. If you need access rights, that can be done, just ask (with your salsa username) - d/changelog Please mention the dropped patch as well, as well the reason why it has been dropped. Has it been applied upstream? - d/copyright should transferred to DEP-5 style, ands needs updating, as copyright statments in the code a slightly different. -- tobi On Sat, Jul 27, 2024 at 08:08:56PM +0900, EiPiFun wrote: > Package: sponsorship-requests > Severity: normal > > Dear mentors, > > I am looking for a sponsor for my package "tty-clock": > > * Package name : tty-clock > Version : 2.3-git.2021.11.21.f2f847c-1 > Upstream contact : xorg62 > * URL : https://github.com/xorg62/tty-clock > * License : BSD 3-Clause > * Vcs : https://github.com/EiPiFun/tty-clock > Section : utils > > The source builds the following binary packages: > > tty-clock - simple terminal clock > > It is a small clock using lib ncurses, which could be used as a clock > of course, and it could act as a simple screensaver for device without > desktop environment. It is easy to use and does have some functions. > But it was orphaned and I just want to maintain it. > > To access further information about this package, please visit the > following URL: > > https://mentors.debian.net/package/tty-clock/ > > Alternatively, you can download the package with 'dget' using this > command: > > dget -x > https://mentors.debian.net/debian/pool/main/t/tty-clock/tty-clock_2.3-git.2021.11.21.f2f847c-1.dsc > > Changes since the last upload: > > tty-clock (2.3-git.2021.11.21.f2f847c-1) unstable; urgency=medium > . > * Adopting package (Closes: #1031941). > * New upstream release based on latest git commit. > * Add 0003-Makefile-improve_cross_build.patch: > - Improve cross build by change hardcoded pkgconf > > Regards, >
Bug#497888: backuppc bug triaging -- closing ancient bugs
Hi, I was going through those very old bugs and decided to close them, as BackupPC V4 has evolved a lot and a lot of those bugs seems to be feature requests, unsure if the problems still exist or otherwise not actionable. Please feel free to reopen the bugs, if think that is sensible, or maybe if it as feature request check directly with upstream. -- tobi
Bug#1076253: RFS: sosreport/4.7.2-1 [ITA] -- Set of tools to gather troubleshooting data from a system
Control: reassign -1 sponsorship-requests Control: merge 1076347 -1 This seems to be an duplicate of #1076347
Bug#1074596: (no subject)
Control: -1 moreinfo Hi Zixing Liu, > cpio (2.15+dfsg-2) UNRELEASED; urgency=medium > . > * Use compat level 13 (Closes: #1073111, #851631). > - Switch to use autoconf Debian Helper template. > - Switch to use dh generated alternatives scripts. > - Remove all manual installation steps from d/rules. > Those bugs seems to be out of scope for an NMU. Please see the developers reference about NMUs in general. Have you tried contacted the maintainer? On Thu, Jul 25, 2024 at 09:31:06PM -0600, Zixing Liu wrote: > Control: retitle -1 cpio/2.15+dfsg-1.1 [NMU] -- GNU cpio -- a program to > manage archives of files > > Hi, > > I have fixed the packaging and re-uploaded the fixed version to > mentors.debian.org. > Please see my previous message for the link. > > Thanks, > Zixing >
Bug#1077091: src:sosreport: d/copyright inaccurate
Source: sosreport Severity: serious Justification: Policy 4.5 (Found during reviewing RFS #1076347) On Thu, 25 Jul 2024 13:13:28 +0100 Arif Ali wrote: > I've delayed the copyright updates until we've discussed this upstream, so > no changes there for the time being. (It seems that part of the discussions are not on the bug (at least I do not see a Chris participating here)) d/copyright needs to reflect the code "verbatim" -- see Policy Checking a random file, (sos/report/archive.py) the file is licenses GPL2 *only*, while d/copyright says GPL2 *or later*. (An inaccurate d/copyright is a RC bug and a blocker for this RFS)
Bug#1076347: RFS: sosreport/4.7.2-1 [ITA]-- Set of tools to gather troubleshooting data from a system
Control: tags -1 moreinfo On Thu, 25 Jul 2024 13:13:28 +0100 Arif Ali wrote: > I've delayed the copyright updates until we've discussed this upstream, so > no changes there for the time being. (It seems that part of the discussions are not on the bug (at least I do not see a Chris participating here)) d/copyright needs to reflect the code "verbatim" -- see Policy Checking a random file, (sos/report/archive.py) the file is licenses GPL2 *only*, while d/copyright says GPL2 *or later*. (An inaccurate d/copyright is a RC bug and a blocker for this RFS) -- tobi
Bug#1075742: RFS: adminer/4.8.1-3 [RC] -- Web-based database administration tool
Control: tags -1 moreinfo Please remove the tag moreinfo once you've done investigating. Thanks! -- tobi On Mon, 8 Jul 2024 18:17:04 +0200 Alexandre Rossi wrote: > No clue as to where those directories come from, investigating.
Bug#1055431: RFS: scala-mode-el/1:1.1.0+git20221025.5d7cf21-1 [RC] [Team] -- transitional dummy package, scala-mode-el to elpa-scala-mode
Control: tags -1 moreinfo (Tagging moreinfo as the package seems not be ready , please remove tag when it is ready for the next round of review, or if I misunderstood the conversation and it is ready already now)
Bug#1076671: RFS: uriparser/0.9.8+dfsg-2 -- documentation files for uriparser
On Fri, Jul 26, 2024 at 03:01:43AM +0100, Phil Wyett wrote: > Hi, > > The current 'Standards-Version' is 4.7.0[1]. It is the packages in Debian > that have yet to catch up. Of course, my tired eyes had got that parsing backwards. Sorry for that part. > [1] https://www.debian.org/doc/debian-policy/ > > Regards > > Phil > > On Fri, 2024-07-26 at 03:49 +0200, Tobias Frost wrote: > > Control: tags -1 -confirmed +moreinfo > > > > Hi Jörg, > > > > > Version : 0.9.8+dfsg-2 > > > Package name : uriparser > > > > the only change seem to be that of VCS-Git; usually such kind of changes > > should be compared with others, it should be avoided to upload if this > > is the only change. As lintian has some suggetions: > > > > W: uriparser source: newer-standards-version 4.7.0 (current is 4.6.2) > > I: uriparser source: patch-not-forwarded-upstream > > [debian/patches/0001-missing_pthread.patch] > > > > can you solve those and then do the upload? > > > > TIA > > -- > > tobi > > > > On Sun, Jul 21, 2024 at 08:04:51PM +0200, Jörg Frings-Fürst wrote: > > > Package: sponsorship-requests > > > Severity: normal > > > > > > Dear mentors, > > > > > > I am looking for a sponsor for my package "uriparser": > > > > > > Upstream contact : [fill in name and email of upstream] > > > URL : http://uriparser.sourceforge.net > > > License : LGPL-2.1+, BSD-3-clause > > > Vcs : https://git.jff.email/cgit/uriparser.git > > > Section : libs > > > > > > The source builds the following binary packages: > > > > > > liburiparser1 - URI parsing library compliant with RFC 3986 > > > liburiparser-dev - development files for uriparser > > > liburiparser-doc - documentation files for uriparser > > > > > > To access further information about this package, please visit the > > > following > > > URL: > > > > > > https://mentors.debian.net/package/uriparser/ > > > > > > Alternatively, you can download the package with 'dget' using this > > > command: > > > > > > dget -x > > > https://mentors.debian.net/debian/pool/main/u/uriparser/uriparser_0.9.8+dfsg-2.dsc > > > > > > or from > > > > > > git > > > https://git.jff.email/cgit/uriparser.git?h=release%2Fdebian%2F0.9.8%2Bdfsg-2 > > > > > > > > > > > > > > > Changes since the last upload: > > > > > > uriparser (0.9.8+dfsg-2) unstable; urgency=medium > > > . > > > * debian/control: > > > - Fix Vcs-Git URL. > > > > > > CU > > > Jörg > > > > > > -- > > > 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 > > > > > > > > > Jörg Frings-Fürst > > > D-54470 Lieser > > > > > > > > > git: https://git.jff.email/cgit/ > > > > > > Skype:jff-skype@jff.email > > > Jami: joergfringsfuerst > > > Telegram: @joergfringsfuerst > > > Matrix: @joergff:matrix.snct-gmbh.de > > > > > > My wish list: > > > - Please send me a picture from the nature at your home. > > > > > > > > > > > > > > > > -- > "I play the game for the game’s own sake" > > Arthur Conan Doyle - The Adventure of the Bruce-Partington Plans > > -- > > Internet Relay Chat (IRC): kathenas > > Website: https://kathenas.org > > Instagram: https://instagram.com/kathenasorg/ > > Buy Me A Coffee: https://buymeacoffee.com/kathenasorg > > -- >
Bug#1073960: RFS: libmobi/0.12+dfsg-1 [RC] -- Tools for handling Mobipocket/Kindle ebook format documents
Control: tag -1 moreinfo -confirmed On Thu, Jun 20, 2024 at 07:14:45PM +0200, Bartek Fabiszewski wrote: > Package: sponsorship-requests > Severity: important > > Dear mentors, > > I am looking for a sponsor for my package "libmobi": > > * Package name : libmobi >Version : 0.12+dfsg-1 >Upstream contact : Bartek Fabiszewski > * URL : https://github.com/bfabiszewski/libmobi > * License : ISC, BSD-4-Clause, Unlicense, public-domain, LGPL-3+ > * Vcs : https://salsa.debian.org/debian/libmobi >Section : libs (Review based on the upload 2024-07-21 18:39) - There are empty files: d/libmobi0.(install,docs,symbols) --> drop them - The patches could have dep3 information whether you have applied them upstream as well. - There are changes that are not documented in d/changelog, like (not exhaustive) - bump of SV to 4.7.0 (did you have to do any changes because of it?) and - update of d/copyright years (d/copyright should reflect the data in the source file "verbatim" - you update the copyright years in d/copyright 2024, but did not change the year in your source code. That violates the "verbatim". So either bump the year in your source code too, or record the years as they are in the source - usually d/changelog's purpose is to document the changes to the Debian *packaging*, not to document upstream changes. See Policy 4.6. (You've got your upstream changelog, that is where your upstream changes shoudl got to. In this case I'd write the changelog as: libmobi (0.12+dfsg-1) unstable; urgency=medium * New upstream release. (Closes: #1073331) * * Updated d/copyright years * New patches to fixing typo/tweak wording in the manpage * (...) -- Bartek Fabiszewski Mon, 17 Jun 2024 13:34:25 +0200 -- tobi
Bug#1076671: RFS: uriparser/0.9.8+dfsg-2 -- documentation files for uriparser
Control: tags -1 -confirmed +moreinfo Hi Jörg, > Version : 0.9.8+dfsg-2 > Package name : uriparser the only change seem to be that of VCS-Git; usually such kind of changes should be compared with others, it should be avoided to upload if this is the only change. As lintian has some suggetions: W: uriparser source: newer-standards-version 4.7.0 (current is 4.6.2) I: uriparser source: patch-not-forwarded-upstream [debian/patches/0001-missing_pthread.patch] can you solve those and then do the upload? TIA -- tobi On Sun, Jul 21, 2024 at 08:04:51PM +0200, Jörg Frings-Fürst wrote: > Package: sponsorship-requests > Severity: normal > > Dear mentors, > > I am looking for a sponsor for my package "uriparser": > > Upstream contact : [fill in name and email of upstream] > URL : http://uriparser.sourceforge.net > License : LGPL-2.1+, BSD-3-clause > Vcs : https://git.jff.email/cgit/uriparser.git > Section : libs > > The source builds the following binary packages: > > liburiparser1 - URI parsing library compliant with RFC 3986 > liburiparser-dev - development files for uriparser > liburiparser-doc - documentation files for uriparser > > To access further information about this package, please visit the following > URL: > > https://mentors.debian.net/package/uriparser/ > > Alternatively, you can download the package with 'dget' using this command: > > dget -x > https://mentors.debian.net/debian/pool/main/u/uriparser/uriparser_0.9.8+dfsg-2.dsc > > or from > > git > https://git.jff.email/cgit/uriparser.git?h=release%2Fdebian%2F0.9.8%2Bdfsg-2 > > > > > Changes since the last upload: > > uriparser (0.9.8+dfsg-2) unstable; urgency=medium > . > * debian/control: > - Fix Vcs-Git URL. > > CU > Jörg > > -- > 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 > > > Jörg Frings-Fürst > D-54470 Lieser > > > git: https://git.jff.email/cgit/ > > Skype:jff-skype@jff.email > Jami: joergfringsfuerst > Telegram: @joergfringsfuerst > Matrix: @joergff:matrix.snct-gmbh.de > > My wish list: > - Please send me a picture from the nature at your home. > > > >
Bug#1072448: rbdoom3bfg: FTBFS with ffmpeg 7.0
Control: tags -1 pending Thanks for the patch! I've imported it into the git repo, so once the transition starts the fix can be uploaded. Cheers, tobi
Bug#1038895: freecad: 'Path' workbench throw 'marshal data too short' error.
Control: close -1 Hi Petter, I'm looking through old bugs and I am not sure if this bug is actionable, therefore I'm going to close it. (it can be reopened if new information makes it actionable) -- tobi
Bug#1032834: freecad: Segmentation fault while redoing
Control: tags -1 moreinfo Control: close -1 As not additional information has been provided, closing. (The bug can be reopened with addtional informations, if needed, of course)
Bug#1077021: RM: obs-scene-tree-view [ppc64el] -- RoQA; B-D not available for arch
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: obs-scene-tree-v...@packages.debian.org Control: affects -1 + src:obs-scene-tree-view User: ftp.debian@packages.debian.org Usertags: remove Dear ftp-masters, please remove the package for ppc64el. It indirectly B-D on luajit, which is not built anymore for pp64el (set by architecture list in its d/control) Thanks! -- tobi
Bug#1033695: freecad-python3: FreeCAD segfaults instantly
Control: close -1 As no addtional information has been provided, closing this bug.
Bug#1077015: RM: obs-color-monitor [ppc64el] -- RoQA; B-D no longer available on arch
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: obs-color-moni...@packages.debian.org Control: affects -1 + src:obs-color-monitor User: ftp.debian@packages.debian.org Usertags: remove Dear ftp-masters, please remove the package for ppc64el. It indirectly B-D on luajit, which is not built anymore for pp64el (set by architecture list in its d/control) Thanks! -- tobi
Bug#1077014: RM: obs-transition-table [ppc64el] -- RoQA; B-D not available on arch
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: obs-transition-ta...@packages.debian.org Control: affects -1 + src:obs-transition-table User: ftp.debian@packages.debian.org Usertags: remove Hi, The package indirectly B-D on luajit, which is not built anymore for pp64el (set by architecture list in its d/control) -- tobi
Bug#1077013: RM: obs-source-copy [ppc64el] -- RoQA; B-D no longer available for arch
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: obs-source-c...@packages.debian.org Control: affects -1 + src:obs-source-copy User: ftp.debian@packages.debian.org Usertags: remove Hi, please remove the package, it indirectly B-D on luajit, which is not built anymore for pp64el (set by architecture list in its d/control) Thanks! -- tobi
Bug#1077000: RM: obs-advanced-scene-switcher [ppc64el] -- RoQA; B-D not available
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: obs-advanced-scene-switc...@packages.debian.org Control: affects -1 + src:obs-advanced-scene-switcher User: ftp.debian@packages.debian.org Usertags: remove Dear ftp-masters, please remove obs-advanced-scene-switcher for ppc64el. It indirectly B-D on luajit, which is not built anymore for pp64el (set by architecture list in its d/control) Thanks! -- tobi
Bug#1076962: linux: Enable CONFIG_NETKIT=m
Subject: linux: Enable CONFIG_NETKIT=m Package: linux Severity: wishlist X-Debbugs-Cc: deb+net...@aibor.de Dear Maintainer, Recently, support for a new network device type "netkit" was added. Support must be explicitley enabled in the kernel with the config key CONFIG_NETKIT=m https://www.kernelconfig.io/config_netkit Please enable this new device type in the kernel config. Thank you in advance. Best regards, Tobias Böhm -- System Information: Debian Release: 12.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: arm64 (aarch64) Kernel: Linux 6.9.7+bpo-arm64 (SMP w/2 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system)
Bug#1076783: linux-image: CONFIG_SENSORS_ADM1021=m dropped since 6.1
Package: linux-image Version: 6.1 Severity: normal Hi, it seems that the adm1021 driver module was dropped from the kernel config (CONFIG_SENSORS_ADM1021=m) starting from Debian Bookworm. There are several Siemens devices that use this chip for temperature monitoring and many of these devices rely on Debian. An absence of the driver is an issue for us that has to be fixed downstream at the moment. Is it possible to re-add the config switch? Was the omission of the ADM1021 driver part of a regular cleanup process or is there some technical reasons behind this decision? Thanks and all the best, Tobias
Bug#1076776: RM: obs-time-source [ppc64el] -- RoQA; B-D not available
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: obs-time-sou...@packages.debian.org, highvolt...@debian.org Control: affects -1 + src:obs-time-source User: ftp.debian@packages.debian.org Usertags: remove Dear ftp-masters, please remove obs-time-source for ppc64el. It indirectly B-D on luajit, which is not built anymore for pp64el (set by architecture list in its d/control) Thanks! -- tobi
Bug#1052101: gnome-shell-extension-hamster: diff for NMU version 0.10.0+git20240714-0.1
Control: tags 1052101 + patch
Control: tags 1052101 + pending
Dear maintainer,
I've prepared an NMU for gnome-shell-extension-hamster (versioned as
0.10.0+git20240714-0.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.
The debdiff is available as MRs for the affected branches:
master:
https://salsa.debian.org/projecthamster-team/gnome-shell-extension-hamster/-/merge_requests/4
upstream:
https://salsa.debian.org/projecthamster-team/gnome-shell-extension-hamster/-/merge_requests/5
pristine-tar
https://salsa.debian.org/projecthamster-team/gnome-shell-extension-hamster/-/merge_requests/6
--
Regards,
tobi
diff -Nru gnome-shell-extension-hamster-0.10.0+git20230901/data/metadata.json.in gnome-shell-extension-hamster-0.10.0+git20240714/data/metadata.json.in
--- gnome-shell-extension-hamster-0.10.0+git20230901/data/metadata.json.in 2023-08-10 18:33:38.0 +0200
+++ gnome-shell-extension-hamster-0.10.0+git20240714/data/metadata.json.in 2024-04-09 15:09:59.0 +0200
@@ -10,14 +10,8 @@
"gettext-domain": "hamster-shell-extension",
"settings-schema": "org.gnome.shell.extensions.project-hamster",
"shell-version": [
-"3.34",
-"3.36",
-"3.38",
-"40",
-"41",
-"42",
-"43",
-"44"
+ "45",
+ "46"
],
"url": "https://github.com/projecthamster/hamster-shell-extension.git";,
"uuid": @UUID@
diff -Nru gnome-shell-extension-hamster-0.10.0+git20230901/data/schemas/org.gnome.shell.extensions.project-hamster.gschema.xml gnome-shell-extension-hamster-0.10.0+git20240714/data/schemas/org.gnome.shell.extensions.project-hamster.gschema.xml
--- gnome-shell-extension-hamster-0.10.0+git20230901/data/schemas/org.gnome.shell.extensions.project-hamster.gschema.xml 2023-08-10 18:33:38.0 +0200
+++ gnome-shell-extension-hamster-0.10.0+git20240714/data/schemas/org.gnome.shell.extensions.project-hamster.gschema.xml 2024-04-09 15:09:59.0 +0200
@@ -1,10 +1,10 @@
-
+
0
Placement in the panel.
-Position to place extension at. 0 - default, 1 - replace calendar, 2 - replace activities.
+Position to place extension at. 0 - default, 1 - replace calendar, 2 - replace activities, 3 - Center, next to calendar.
diff -Nru gnome-shell-extension-hamster-0.10.0+git20230901/debian/changelog gnome-shell-extension-hamster-0.10.0+git20240714/debian/changelog
--- gnome-shell-extension-hamster-0.10.0+git20230901/debian/changelog 2023-09-01 08:43:28.0 +0200
+++ gnome-shell-extension-hamster-0.10.0+git20240714/debian/changelog 2024-07-14 09:43:35.0 +0200
@@ -1,3 +1,12 @@
+gnome-shell-extension-hamster (0.10.0+git20240714-0.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * New upstream git snaphsot with GNOME Shell 46 compat. (Closes: #1052101)
+ * Update version constraints on gnome-shell, as this version is only
+compatible with GNOME Shell 45 and up.
+
+ -- Tobias Frost Sun, 14 Jul 2024 09:43:35 +0200
+
gnome-shell-extension-hamster (0.10.0+git20230901-1) unstable; urgency=medium
* New upstream git snapshot with GNOME Shell 44 compat. (Closes: #1041574)
diff -Nru gnome-shell-extension-hamster-0.10.0+git20230901/debian/control gnome-shell-extension-hamster-0.10.0+git20240714/debian/control
--- gnome-shell-extension-hamster-0.10.0+git20230901/debian/control 2023-09-01 08:43:28.0 +0200
+++ gnome-shell-extension-hamster-0.10.0+git20240714/debian/control 2024-07-14 09:43:35.0 +0200
@@ -18,8 +18,8 @@
Architecture: all
Depends:
hamster-time-tracker,
- gnome-shell (>= 3.38),
- gnome-shell (<< 45~),
+ gnome-shell (>= 45),
+ gnome-shell (<< 47~),
${misc:Depends}
Description: GNOME Shell extension for the Hamster Time Tracker
Project Hamster helps you to keep track of how much time you spend on various
diff -Nru gnome-shell-extension-hamster-0.10.0+git20230901/extension/extension.js gnome-shell-extension-hamster-0.10.0+git20240714/extension/extension.js
--- gnome-shell-extension-hamster-0.10.0+git20230901/extension/extension.js 2023-08-10 18:33:38.0 +0200
+++ gnome-shell-extension-hamster-0.10.0+git20240714/extension/extension.js 2024-04-09 15:09:59.0 +0200
@@ -21,18 +21,14 @@
*/
-const GLib = imports.gi.GLib;
-const Shell = imports.gi.Shell;
-const Meta = imports.gi.Meta;
-const Main = imports.ui.main;
-const Gio = imports.gi.Gio;
-
-const Gettext = imports.gettext.domain('hamster-shell-extension');
-const _ = Gettext.gettext;
-
-const ExtensionUtils = imports.misc.extensionUtils;
-const Me = ExtensionUtils.getCurrentExtension();
-const PanelWidget = Me.imports.widgets.panelWidget.PanelWidget;
+import GLib fro
Bug#1065873: hamster-time-tracker: diff for NMU version 3.0.3-1.1
(Updated debdiff, also dropping python3-distutils from Depends:)
MR:
https://salsa.debian.org/projecthamster-team/hamster-time-tracker/-/merge_requests/3
Dear maintainer,
I've prepared an NMU for hamster-time-tracker (versioned as 3.0.3-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru hamster-time-tracker-3.0.3/debian/changelog hamster-time-tracker-3.0.3/debian/changelog
--- hamster-time-tracker-3.0.3/debian/changelog 2023-11-24 00:40:13.0 +0100
+++ hamster-time-tracker-3.0.3/debian/changelog 2024-07-14 08:56:19.0 +0200
@@ -1,3 +1,10 @@
+hamster-time-tracker (3.0.3-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop python3-distutils from B-D (Closes: #1065873)
+
+ -- Tobias Frost Sun, 14 Jul 2024 08:56:19 +0200
+
hamster-time-tracker (3.0.3-1) unstable; urgency=medium
[ Raphaël Hertzog ]
diff -Nru hamster-time-tracker-3.0.3/debian/control hamster-time-tracker-3.0.3/debian/control
--- hamster-time-tracker-3.0.3/debian/control 2023-11-24 00:40:13.0 +0100
+++ hamster-time-tracker-3.0.3/debian/control 2024-07-14 08:56:19.0 +0200
@@ -15,7 +15,6 @@
python3,
python3-cairo,
python3-dbus,
- python3-distutils,
python3-gi
Standards-Version: 4.6.2
Homepage: https://github.com/projecthamster/hamster
@@ -31,7 +30,6 @@
libjs-jquery-ui,
python3-cairo,
python3-dbus,
- python3-distutils,
python3-gi,
python3-gi-cairo,
${misc:Depends},
Bug#1065873: hamster-time-tracker: diff for NMU version 3.0.3-1.1
Control: tags 1065873 + patch Control: tags 1065873 + pending Dear maintainer, I've prepared an NMU for hamster-time-tracker (versioned as 3.0.3-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -Nru hamster-time-tracker-3.0.3/debian/changelog hamster-time-tracker-3.0.3/debian/changelog --- hamster-time-tracker-3.0.3/debian/changelog 2023-11-24 00:40:13.0 +0100 +++ hamster-time-tracker-3.0.3/debian/changelog 2024-07-14 08:49:38.0 +0200 @@ -1,3 +1,10 @@ +hamster-time-tracker (3.0.3-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Drop python3-distutils from B-D (Closes: #1065873) + + -- Tobias Frost Sun, 14 Jul 2024 08:49:38 +0200 + hamster-time-tracker (3.0.3-1) unstable; urgency=medium [ Raphaël Hertzog ] diff -Nru hamster-time-tracker-3.0.3/debian/control hamster-time-tracker-3.0.3/debian/control --- hamster-time-tracker-3.0.3/debian/control 2023-11-24 00:40:13.0 +0100 +++ hamster-time-tracker-3.0.3/debian/control 2024-07-14 08:49:38.0 +0200 @@ -15,7 +15,6 @@ python3, python3-cairo, python3-dbus, - python3-distutils, python3-gi Standards-Version: 4.6.2 Homepage: https://github.com/projecthamster/hamster signature.asc Description: PGP signature
Bug#743969: fl-cow: new upstream release 0.10
Hi Petter, On Thu, Jul 11, 2024 at 07:41:15AM +0200, Petter Reinholdtsen wrote: > [Tobias Frost 2014-04-08] > > Thanks for considering packaging the upstream release 0.10 > > I had a look for it, but could not find release 0.10 anywhere. Any idea > where to find it? Its homepage has a link at the bottom, (it blends/hides there quite good :)) http://www.xmailserver.org/fl-cow-0.10.tar.gz Cheers, -- tobi > -- > Happy hacking > Petter Reinholdtsen
Bug#1076031: pyside breaks reverse dependencies by renaming library file
X-Debbugs-Cc: debian-rele...@lists.debian.org Control: reassign -1 pyside2 Control: affects -1 freecad This has been introduced by the upload of pyside3, which changed the libary name without managing that reverse dependencies so that they rebuilt. Dear pyside2 maintainers, please be more thoughtful and manage your transistions more carefully. This happend already in the past, see #1013881. Thanks. -- tobi
Bug#1050030: Slow boot with 2020.11-2+deb11u1 and building OVMF from source
Hello all, As noted before, going back to 2020.11-2+deb11u1 allows booting HVM domains. However, for us it slowed down the boot from half a minute to two minutes, when using PCI passthrough. The Xen community pointed out to me that this may be due to a patch for Xen not being built in that version (https://github.com/tianocore/edk2/commit/c05de360ec614f71716a201760b91ee055a5ff28). I propose to either - ship a Xen specific version of OVMF (as suggested here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978595 and above and similar to Fedora https://packages.fedoraproject.org/pkgs/edk2/edk2-ovmf-xen/) or - build Xen with OVMF included (the Xen build should supports this). However, I myself could get neither package to compile this way from Debian sources. We mitigated the problem for us, by building OVMF ourselves from git://xenbits.xen.org/ovmf.git for "edk2-stable202305", the latest tag found there. It should actually be the same for https://github.com/tianocore/edk2.git, but I did not try. On Debian 12 to make it work we - removed "brotli" from BaseTools/Source/C/Makefile (otherwise the build will fail with warnings treated as errors) - apt-get build-dep -y ovmf # Build needs GCC 11 instead of version 12 shipped with Debian 12, because otherwise again the build will end with warnings treated as errors - apt-get install -y gcc-11 g++-11 libgcc-11-dev - update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-11 1 - update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-11 1 - cd BaseTools; make -C Source/C - cd ..; OvmfPkg/build.sh -a X64 -b RELEASE -p OvmfPkg/OvmfXen.dsc Then "Build/OvmfXen/RELEASE_GCC5/FV/OVMF.fd" must be placed at "/usr/share/ovmf/OVMF.fd", because the Debian package for Xen is compiled with "--with-system-ovmf=/usr/share/ovmf/OVMF.fd". Best regards, Tobias
Bug#1073176: gramps: Error with loss of data: TypeError: '<' not supported between instances of 'str' and 'NoneType'
control: tag -1 unreproducible control: severity -1 normal On Fri, 14 Jun 2024 19:39:23 +1200 Mark Robinson wrote: On completing the database migration I created a new person, added birth and death information including a new death location and notes, and clicked OK. This resulted in the python error referred to in the headline which left the new person with the OK button greyed out and no way to save it. The record was lost. Hi Mark, sorry about that. I've tried to reproduce this bug, using the steps you've described above. It worked without any problem on my system, so I'm not able to reproduce the faulty behaviour of gramps. I'm therefore lowering the severity, because otherwise gramps would be removed from testing. I currently don't think that this would be necessary. However, there should be an automatic backup of your database, as printed in the status messages: 11723: WARNING: upgrade.py: line 2218: If upgrade and loading the Family Tree works, you can delete the zip file at /home/mark/.gramps/ROBINSON__Mark_Gregory_2024-06-14_12-07-04.zip Could you try to extract that database version of your family tree and open it with gramps? The program should then ask you again to convert the tree to the new database format. Afterwards, could you repeat the steps above, i. e. creating a new person, adding birth and death information etc.? Then please report back if the error still occurs. Regards, Tobias OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1073827: (no subject)
Hi, I am seeing exactly the same with chromium since 126.0.6478.56-1~deb12u1 Best Regards, Toby
Bug#1073233: plasma-workspace: Regression fix for CVE-2024-36041 is missing
Hello, I notice the described bug (session restore not working) on plasma with X11 on Debian/sid, currently using 5.27.11.1-1+b1. Greetings Tobi signature.asc Description: This is a digitally signed message part.
Bug#1061743: Gramps in Debian
Am 03.06.24 um 06:55 schrieb Ross Gammon: I will try and take a look this week. But if I fail, either of you are welcome to lose patience, merge it to master, and upload it for me. :-) Hi Ross, I've decided to lose patience. :-) No, seriously, I've built Gramps locally and did some test runs with it. Everything seems to work fine, so I've pushed my latest changes to salsa, merged it into the master branch, and uploaded to unstable. Regards, Tobias OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072742: On Romanian translations in the iso-codes package
Am 07.06.24 um 13:08 schrieb Alex: Hello, I’d like to report an issue in the Romanian translations of the iso-codes package. I’m not sure whether this is the right place. The README says to open a Salsa issue but that requires authentication and my account is yet to be approved. If this isn’t the place, please instruct me on where to post as linux.debian.bugs.dist on Google Groups seems to be read-only. In any case, I want to report that the Romanian translations for the ISO 3166-2 data have unnecessary prefixes indicating the type of the subdivision (and sometimes suffixes too.) For example, “Alaska” is translated as “Statul Alaska” (i.e. “The state of Alaska”); the Romanian county of “Bacău” is translated as “Județul Bacău, România” (i.e. “The county of Bacău, România”); “Thüringen” is translated to "Landul Turingia, Germania” (i.e. “The land of Turingia, Germany") etc. It goes on and on for virtually all subdivisions. On the one hand, that’s not how Romanians refer to countries' subdivisions. For example, I was born in "Onești, Bacău", not “Onești, Bacău County”. Similarly, “Paris" is just “Paris”, not “Orașul metropolitan Paris (capitala), Franța” (i.e. “Metropolitan city of Paris (capital), France”). On the other hand, it looks like it's only the Romanian translation that does this, making it very odd in comparison. To add to the weirdness, the Zimbabwean province of "Matabeleland South” is translated as "Provincia Matabeleland South”, not even “Provincia Matabeleland Sud”, though "South Australia” is fully translated to "Statul Australia de sud”. I can and am willing to invest some time in reviewing and cleaning up at least some of the translations. Considering there’s many of them, it would take a while to cover all of them, though. There is of course the question of whether the Debian team is willing to consider accepting such changes. Regards, Alex Hi Alex, thanks so much for your bug report! I'm not speaking Romanian, so I cannot judge the quality of the Romanian translation. However, what you've written seems plausible to me, and I can at least infer from your examples that what you're writing is correct. All those translations have come from Weblate, where the iso-codes translation is hosted. The changes (adding those prefixes) have been done by a translator named Remus-Gabriel Chelu, I've added them in CC of this mail. Remus-Gabriel, would you be so kind to join this discussion on the Debian BTS and share your point of view? You can just reply to this mail, keeping all addresses in the loop. Many thanks in advance! The bug report can be seen here: https://bugs.debian.org/1072742 Regards, Tobias OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072241: src:manpages: fails to migrate to testing for too long: RC bug and B-D not in testing
Am 31.05.24 um 10:32 schrieb Dr. Tobias Quathamer: I couldn't find any explanation in the commit messages or debian/changelog. What's the reason for all those additional dependencies? Can't we get rid of them? I don't see how they are needed for building the package. I did not get a response, so I went ahead and uploaded a version without all those extra Build-Dependencies. Regards, Tobias OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072241: src:manpages: fails to migrate to testing for too long: RC bug and B-D not in testing
Am 30.05.24 um 22:30 schrieb Paul Gevers: Source: manpages Version: 6.05.01-1 Severity: serious Control: close -1 6.8-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1072158 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:manpages has been trying to migrate for 59 days [2]. Hence, I am filing this bug. The version in unstable has an unresolved RC bug (#1072158) and one of its Build-Depends isn't in testing and can't migrate. [...] Hi Marcos, I've seen that you've added quite a lot of new packages to the Build-Depends of manpages, therefore the migration to testing is currently not possible (due to missing Build-Depends in testing). The list of packages in Build-Depends changed considerably between manpages 6.05.01-1 and manpages 6.7-1 from Build-Depends: debhelper-compat (= 13), groff (>= 1.23.0), mandoc to Build-Depends: debhelper-compat (= 13), groff (>= 1.23.0), groff-base, bsdextrautils, bzip2, binutils, clang, clang-tidy, cpp, cppcheck, cpplint, diffoscope, git, iwyu, lzip, man, mandoc, moreutils, pkgconf, xz-utils I couldn't find any explanation in the commit messages or debian/changelog. What's the reason for all those additional dependencies? Can't we get rid of them? I don't see how they are needed for building the package. Regards, Tobias OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1061743: Gramps in Debian
Am 27.05.24 um 15:38 schrieb IOhannes m zmölnig (Debian GNU|Linux): On 5/26/24 23:56, Dr. Tobias Quathamer wrote: The package builds on my machine, although I had to disable a single test for now. You'll find it in the newly created patch. Maybe you have an idea what's causing the failure, so it can be fixed properly. https://gramps-project.org/bugs/view.php?id=13305 i think this is just a wrong assumption on the side of the upstream testsuite (shadowed by their workflows). upstream evades this by ensuring that "~/.gramps/" is there before running the tests (both in their GitHub action, and in their debian/ packaging). i think that for now the proper resolution for the problem is to simply do a `mkdir "$CURDIR)/build/.gramps` before running the tests. (which i've now pushed to the 'experimental' branch) Great, thanks! That's a cleaner approach. as a sidenote: the testsuite now creates a *very* verbose buildlog (~420MB). is that ok? gf,madsr IOhannes Hm, I guess that's because of the "--verbose" option when running the tests. However, the buildlog has been similarly large in v5.1.6 as well. Could that to be due to the switch from nosetest to unittest? Maybe the --verbose option should be dropped? The buildlog gets shrinked to 1.4 MB, but the tests are only displayed as dots. Regards, Tobias OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1061743: Gramps in Debian
Am 24.05.24 um 21:23 schrieb Ross Gammon: Hi Tobias, There are no blockers other than real life getting in the way. I did start working on 5.2.0 in the experimental branch on Salsa. From memory, there was a problem with fuzzy patches, and the tedious checking of copyrights still to do. But I should probably merge the changes into master, and then import 5.2.2. If you have some spare cycles you are welcome to help move things along. I use gbp + quilt. Regards, Ross Hi Ross, I took some time to update the experimental branch to v5.2.2 and fix some FTBFS with the new upstream version. I've pushed my work to Salsa, please take a look if you have some time. The package builds on my machine, although I had to disable a single test for now. You'll find it in the newly created patch. Maybe you have an idea what's causing the failure, so it can be fixed properly. I haven't looked at the copyrights for now. Regards, Tobias OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1068464: deal.ii: FTBFS: libgmp not linked, libdeal.ii.g.so.9.5.1: error: undefined reference to '__gmpn_neg'
Control: tags -1 unreproducible Control: close -1 Hi Drew, I've rebuilt deal.ii in the course of the opencascade transition, and I cannot reproduce this FTBFS; petsc 3.20 is now in unstable too, and the binNMU has been done ~4 days ago, also without the failure you've seen. Buildds works too... Therefore, I'm closing this bug as non-reproducible. (it can be reopened of course if it reappears.) -- tobi
Bug#1070377: frr: CVE-2024-34088
Control: tags -1 fixed-upstream Control: forwarded -1 https://github.com/FRRouting/frr/pull/15674 Upstream has merged a fix.
Bug#1071473: transition: opencascade
Hi Emilio, thanks for the head up! opencascade is now in unstable and has built for all archs except riscv64, where the buildds are just busy right now and as they are currently building huge packages, this could last a few days. I think a strategic Dep-Wait will help :) Level2 : - f3d and kicad could use a binNMU, with a Dep-Wait on libocct-data-exchange-dev (>= 7.8.1) - freecad, netgen has been (team) uploaded. - horizon-eda and slic3r-prusa are both in DELAYED/2. Level3 : - gmsh has been team uploaded. Level4: - deal.ii will be team-uploaded soon. Thanks! -- tobi On Wed, May 22, 2024 at 08:50:35AM +0200, Emilio Pozuelo Monfort wrote: > Control: tags -1 confirmed > > On 19/05/2024 23:08, Tobias Frost wrote: > > Package: release.debian.org > > Severity: normal > > X-Debbugs-Cc: opencasc...@packages.debian.org > > Control: affects -1 + src:opencascade > > User: release.debian@packages.debian.org > > Usertags: transition > > Control: block 1071284 by -1 > > Control: block 1071223 by -1 > > Control: block 1071470 by -1 > > Control: block 1071451 by -1 > > Control: block 1071471 by -1 > > > > Hi Release team, > > > > opencascade has a new release with breaking ABI, upstream versionied them as > > 7.8. The transition tracker [1] correctly picked it up already after the > > upload > > to experimental. > > > > [1] https://release.debian.org/transitions/html/auto-opencascade.html > > > > building the reverse depenencies most FTBFS due to library naming changes, > > but I was able to come up with patches for most, but they will require > > sourceful > > uploads. Freecad will require either backporting the upstream fixes or > > package > > a new upstream snapshot. > > > > This is the result of the compilation tests: > > > > Dependency level 2: > > > > f3d ✔ > > freecad (sid only) FTBFS, fixed in upstream git. > > horizon-eda patch available, #1071284 > > kicad ✔ > > netgen patch available, #1071223 > > slic3r-prusa (sid only) patch available, #1071470 > > > > Dependency level 3: > > gmshpatch available, #1071451 > > > > Dependency level 4: > > deal.ii patch available, #1071471 > > Will you help upload those fixes? Perhaps through delayed NMUs or team > uploads? If so, go ahead. > > Cheers, > Emilio signature.asc Description: PGP signature
Bug#1071470: slic3r-prusa: diff for NMU version 2.7.4+dfsg-1.1
Control: tags 1071470 + pending Dear maintainer, I've prepared an NMU for slic3r-prusa (versioned as 2.7.4+dfsg-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -Nru slic3r-prusa-2.7.4+dfsg/debian/changelog slic3r-prusa-2.7.4+dfsg/debian/changelog --- slic3r-prusa-2.7.4+dfsg/debian/changelog 2024-04-18 07:26:21.0 +0200 +++ slic3r-prusa-2.7.4+dfsg/debian/changelog 2024-05-24 22:12:57.0 +0200 @@ -1,3 +1,11 @@ +slic3r-prusa (2.7.4+dfsg-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix FTBFS with opencasacade 7.8.1 (Closes: #1071470) and +add a versioned B-D on it. + + -- Tobias Frost Fri, 24 May 2024 22:12:57 +0200 + slic3r-prusa (2.7.4+dfsg-1) unstable; urgency=medium * [3cddded] New upstream version 2.7.4+dfsg diff -Nru slic3r-prusa-2.7.4+dfsg/debian/control slic3r-prusa-2.7.4+dfsg/debian/control --- slic3r-prusa-2.7.4+dfsg/debian/control 2024-04-18 07:26:21.0 +0200 +++ slic3r-prusa-2.7.4+dfsg/debian/control 2024-05-24 22:12:57.0 +0200 @@ -20,11 +20,11 @@ libheatshrink-dev, libnanosvg-dev, libnlopt-cxx-dev | libnlopt-dev (<< 2.4.2+dfsg-5~), - libocct-data-exchange-dev, - libocct-draw-dev, - libocct-foundation-dev, - libocct-modeling-algorithms-dev, - libocct-visualization-dev, + libocct-data-exchange-dev (>=7.8.1+dfsg1), + libocct-draw-dev (>=7.8.1+dfsg1), + libocct-foundation-dev (>=7.8.1+dfsg1), + libocct-modeling-algorithms-dev (>=7.8.1+dfsg1), + libocct-visualization-dev (>=7.8.1+dfsg1), libopenvdb-dev (>= 5.0), libopenvdb-tools, libpng-dev, diff -Nru slic3r-prusa-2.7.4+dfsg/debian/patches/occt-7.8.patch slic3r-prusa-2.7.4+dfsg/debian/patches/occt-7.8.patch --- slic3r-prusa-2.7.4+dfsg/debian/patches/occt-7.8.patch 1970-01-01 01:00:00.0 +0100 +++ slic3r-prusa-2.7.4+dfsg/debian/patches/occt-7.8.patch 2024-05-24 22:12:57.0 +0200 @@ -0,0 +1,18 @@ +diff --git a/src/occt_wrapper/CMakeLists.txt b/src/occt_wrapper/CMakeLists.txt +index d8dd8e1..d27055f 100644 +--- a/src/occt_wrapper/CMakeLists.txt b/src/occt_wrapper/CMakeLists.txt +@@ -22,11 +22,8 @@ generate_export_header(OCCTWrapper) + find_package(OpenCASCADE REQUIRED) + + set(OCCT_LIBS +-TKXDESTEP +-TKSTEP +-TKSTEP209 +-TKSTEPAttr +-TKSTEPBase ++TKDESTEP ++TKDESTL + TKXCAF + TKXSBase + TKVCAF diff -Nru slic3r-prusa-2.7.4+dfsg/debian/patches/series slic3r-prusa-2.7.4+dfsg/debian/patches/series --- slic3r-prusa-2.7.4+dfsg/debian/patches/series 2024-04-18 07:26:21.0 +0200 +++ slic3r-prusa-2.7.4+dfsg/debian/patches/series 2024-05-24 22:12:57.0 +0200 @@ -8,3 +8,4 @@ Disable-preset-update-and-version-check-by-default.patch Patch-tests-for-Catch2-v3-compatibility.patch Explicit-wxWidgets-initializers.patch +occt-7.8.patch signature.asc Description: PGP signature
Bug#1071643: horizon-eda: diff for NMU version 2.6.0-2.1
Control: tags 1071643 + pending Dear maintainer, I've prepared an NMU for horizon-eda (versioned as 2.6.0-2.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. (note: the previous patch was by accident reversed.) Regards. diff -Nru horizon-eda-2.6.0/debian/changelog horizon-eda-2.6.0/debian/changelog --- horizon-eda-2.6.0/debian/changelog 2024-05-22 17:31:22.0 +0200 +++ horizon-eda-2.6.0/debian/changelog 2024-05-24 20:52:05.0 +0200 @@ -1,3 +1,10 @@ +horizon-eda (2.6.0-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix FTBFS, add missing B-D on cppzmq-dev. Closes: #1071643 + + -- Tobias Frost Fri, 24 May 2024 20:52:05 +0200 + horizon-eda (2.6.0-2) unstable; urgency=medium * Fix build depend diff -Nru horizon-eda-2.6.0/debian/control horizon-eda-2.6.0/debian/control --- horizon-eda-2.6.0/debian/control 2024-05-22 17:30:29.0 +0200 +++ horizon-eda-2.6.0/debian/control 2024-05-24 20:52:01.0 +0200 @@ -9,7 +9,7 @@ libglm-dev, libgit2-dev, libcurl4-gnutls-dev, libocct-data-exchange-dev, libdxflib-dev (>> 3.17.0), libarchive-dev, libzip-dev, libglib2.0-dev, libpodofo-dev, python3-cairo-dev, libosmesa6-dev, - dh-python + dh-python, cppzmq-dev Standards-Version: 4.4.0 Homepage: https://horizon-eda.org/ Rules-Requires-Root: no signature.asc Description: PGP signature
Bug#1071643: horizon-eda: Missing build dependency on cppzmq-dev
Source: horizon-eda Followup-For: Bug #1071643 Control: tags -1 patch I can confirm that the version in sid FTBFS, and all that needs is adding the B.D. (Trivial) patch attached. To speed up the opencascade transistion, I'll NMU this in DELAYED/2. -- System Information: Debian Release: trixie/sid APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.8.9-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1071643: horizon-eda: Missing build dependency on cppzmq-dev
Source: horizon-eda Followup-For: Bug #1071643 (patch attached now) -- System Information: Debian Release: trixie/sid APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.8.9-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Naur horizon-eda-2.6.0/debian/control horizon-eda-2.6.0-bak/debian/control --- horizon-eda-2.6.0/debian/control2024-05-24 20:14:57.641114565 +0200 +++ horizon-eda-2.6.0-bak/debian/control2024-05-24 20:14:28.444689829 +0200 @@ -9,7 +9,7 @@ libglm-dev, libgit2-dev, libcurl4-gnutls-dev, libocct-data-exchange-dev, libdxflib-dev (>> 3.17.0), libarchive-dev, libzip-dev, libglib2.0-dev, libpodofo-dev, python3-cairo-dev, libosmesa6-dev, - dh-python, cppzmq-dev + dh-python Standards-Version: 4.4.0 Homepage: https://horizon-eda.org/ Rules-Requires-Root: no
Bug#1071223: Opencascade transition starts now
Control: severity -1 serious The transistion (#1071473) has been confirmed and I'll upload opencascade 8.1 to unstable soon, making those bugs RC. I will either team upload (science team) or NMU the packages to have a speedy transition. -- tobi
Bug#1071473: transition: opencascade
now, there is also a patch for freecad (#1071283)
Bug#1064340: Re: Bug#1064340: RFS: kylin-nm/4.0.0.0-1 -- Gui Applet tool for display and edit network simply
On Tue, May 21, 2024 at 05:15:09PM +0800, handsome_feng wrote: > Hi, > > > > The NMU has not been incorporated. > Sorry, I didn't quite understand this point. Did someone request an NMU? I stand correctred, it was not a NMU, but the changelog entry for 3.0.3.1-1 was not in d/changelog.
Bug#1071283: src:freecad: FTBFS with opencascade 7.8.1
Package: freecad Followup-For: Bug #1071283 Control: tags -1 ftbfs patch Backported upstream patch attached. (Testing is not yet completed, but it compiles with the new opencascade) -- System Information: Debian Release: trixie/sid APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.8.9-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages freecad depends on: ii freecad-python3 0.21.2+dfsg1-1+b3 Versions of packages freecad recommends: ii calculix-ccx2.21-1 ii graphviz2.42.2-9+b1 ii python3-opencamlib 2023.01.11-5 Versions of packages freecad suggests: pn povray -- no debconf information
Bug#1064340: RFS: kylin-nm/4.0.0.0-1 -- Gui Applet tool for display and edit network simply
Control: tags -1 moreinfo Hi, - The NMU has not been incorporated. - There are undocumented changes. Some are very confusing. - Why the move from github to gitlab? - Why the uploaders change? Is this authorized? - Upstream Contact Changed from a team email to your mail? What's going on here? - There is neither a response for #1070113, nor has it been adressed. (It seems also that all documents moved aways from English to Chinese?) -- tobi On Tue, Feb 20, 2024 at 03:53:24PM +0800, xibowen wrote: > Package: sponsorship-requests > Severity: normal > > Dear mentors, > > I am looking for a sponsor for my package "kylin-nm": > > * Package name : kylin-nm >Version : 4.0.0.0-1 >Upstream contact : xibowen > * URL : https://gitee.com/openkylin/kylin-nm > * License : GPL-2+, BSD-3-clause, GPL-3+ > * Vcs : https://gitee.com/openkylin/kylin-nm >Section : utils > > The source builds the following binary packages: > > kylin-nm - Gui Applet tool for display and edit network simply > kylin-nm-plugin - Gui Applet plugin for display and edit network simply > kylin-nm-plugin-dev - Gui Applet development for display and edit network > simply > libkylin-nm-base - Gui lib for display and edit network simply > libkylin-nm-base-dev - Gui lib development for display and edit network > simply > > To access further information about this package, please visit the following > URL: > > https://mentors.debian.net/package/kylin-nm/ > > Alternatively, you can download the package with 'dget' using this command: > > dget -x > https://mentors.debian.net/debian/pool/main/k/kylin-nm/kylin-nm_4.0.0.0-1.dsc > > Changes since the last upload: > > kylin-nm (4.0.0.0-1) unstable; urgency=medium > . >* New upstream release. > > This package is depended on ukui-greeter and ukui-screensaver. > > Regards, > -- > xibowen
Bug#1067595: RFS: psocksxx/1.1.1-5 -- psocksxx is a C++ wrapper for POSIX sockets
Control: tags -1 moreinfo On Sun, Mar 24, 2024 at 10:23:53AM +0100, Jörg Frings-Fürst wrote: > psocksxx (1.1.1-5) unstable; urgency=medium > . > * debian/control: > - Fix git URL. Hi Jörg, can you provide a secure URL for VCS-Git, please? Thanks! -- tobi
Bug#1071473: transition: opencascade
Package: release.debian.org Severity: normal X-Debbugs-Cc: opencasc...@packages.debian.org Control: affects -1 + src:opencascade User: release.debian@packages.debian.org Usertags: transition Control: block 1071284 by -1 Control: block 1071223 by -1 Control: block 1071470 by -1 Control: block 1071451 by -1 Control: block 1071471 by -1 Hi Release team, opencascade has a new release with breaking ABI, upstream versionied them as 7.8. The transition tracker [1] correctly picked it up already after the upload to experimental. [1] https://release.debian.org/transitions/html/auto-opencascade.html building the reverse depenencies most FTBFS due to library naming changes, but I was able to come up with patches for most, but they will require sourceful uploads. Freecad will require either backporting the upstream fixes or package a new upstream snapshot. This is the result of the compilation tests: Dependency level 2: f3d ✔ freecad (sid only) FTBFS, fixed in upstream git. horizon-eda patch available, #1071284 kicad ✔ netgen patch available, #1071223 slic3r-prusa (sid only) patch available, #1071470 Dependency level 3: gmshpatch available, #1071451 Dependency level 4: deal.ii patch available, #1071471 -- Cheers, tobi signature.asc Description: PGP signature
Bug#1071471: src:deal.ii: FTBFS with opencascade 7.8
Source: deal.ii Severity: important Tags: patch ftbfs Dear maintainer, deal.ii FBTFS with opencascade 7.8, which renames a few libraries. Attached patch fixes the FTBFS, unfortunatly it is not backward compatible and it should only be applied after the transistion has been started. -- tobi -- System Information: Debian Release: trixie/sid APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.7.12-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- a/cmake/modules/FindDEAL_II_OPENCASCADE.cmake +++ b/cmake/modules/FindDEAL_II_OPENCASCADE.cmake @@ -69,8 +69,8 @@ # These seem to be pretty much the only required ones. set(_opencascade_libraries TKBO TKBool TKBRep TKernel TKFeat TKFillet TKG2d TKG3d TKGeomAlgo - TKGeomBase TKHLR TKIGES TKMath TKMesh TKOffset TKPrim TKShHealing TKSTEP - TKSTEPAttr TKSTEPBase TKSTEP209 TKSTL TKTopAlgo TKXSBase + TKGeomBase TKHLR TKDEIGES TKMath TKMesh TKOffset TKPrim TKShHealing TKDESTEP + TKDESTL TKTopAlgo TKXSBase ) set(_libraries "")
Bug#1071470: src:slic3r-prusa: FTBFS with opencasacade 7.8.1
Source: slic3r-prusa Severity: important Tags: patch ftbfs Dear maintainer, the new opencascade version 7.8.1 changes some library names, making slic3r-prusa fail. The attached patch fixes the compilation issue. (Source is gentoo, https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5a345e202892c9358921d7a70cd54624bf17e42c) -- tobi -- System Information: Debian Release: trixie/sid APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.7.12-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff --git a/src/occt_wrapper/CMakeLists.txt b/src/occt_wrapper/CMakeLists.txt index d8dd8e1..d27055f 100644 --- a/src/occt_wrapper/CMakeLists.txt +++ b/src/occt_wrapper/CMakeLists.txt @@ -22,11 +22,8 @@ generate_export_header(OCCTWrapper) find_package(OpenCASCADE REQUIRED) set(OCCT_LIBS -TKXDESTEP -TKSTEP -TKSTEP209 -TKSTEPAttr -TKSTEPBase +TKDESTEP +TKDESTL TKXCAF TKXSBase TKVCAF
Bug#1071451: src:gmsh: FTBFS with new opencascade 7.8.1
Source: gmsh Severity: important Tags: patch ftbfs Dear maintainer, gmsh FTBFS with the new opencascade 7.8.1 as the CMakeLists.txt missed to list one library, and therefore many symbols are not resolved at build time: Excerpt of build log: /usr/bin/ld: libgmsh.so.4.12.2: undefined reference to `STEPCAFControl_Reader::STEPCAFControl_Reader()' /usr/bin/ld: libgmsh.so.4.12.2: undefined reference to `STEPCAFControl_Reader::ChangeReader()' /usr/bin/ld: libgmsh.so.4.12.2: undefined reference to `HeaderSection_FileDescription::SetImplementationLevel(opencascade::handle const&)' /usr/bin/ld: libgmsh.so.4.12.2: undefined reference to `APIHeaderSection_MakeHeader::FdValue() const' /usr/bin/ld: libgmsh.so.4.12.2: undefined reference to `HeaderSection_FileName::SetTimeStamp(opencascade::handle const&)' /usr/bin/ld: libgmsh.so.4.12.2: undefined reference to `APIHeaderSection_MakeHeader::APIHeaderSection_MakeHeader(int)' /usr/bin/ld: libgmsh.so.4.12.2: undefined reference to `HeaderSection_FileName::SetOriginatingSystem(opencascade::handle const&)' /usr/bin/ld: libgmsh.so.4.12.2: undefined reference to `StepData_StepModel::AddHeaderEntity(opencascade::handle const&)' /usr/bin/ld: libgmsh.so.4.12.2: undefined reference to `HeaderSection_FileName::SetPreprocessorVersion(opencascade::handle const&)' /usr/bin/ld: libgmsh.so.4.12.2: undefined reference to `StepData_StepModel::Header() const' collect2: error: ld returned 1 exit status /usr/bin/ld: libgmsh.so.4.12.2: undefined reference to `STEPCAFControl_Reader::Transfer(opencascade::handle const&, Message_ProgressRange const&)' /usr/bin/ld: libgmsh.so.4.12.2: undefined reference to `HeaderSection_FileName::SetName(opencascade::handle const&)' collect2: error: ld returned 1 exit status /usr/bin/ld: libgmsh.so.4.12.2: undefined reference to `STEPControl_Writer::Write(char const*)' make[4]: *** [CMakeFiles/t13_cpp.dir/build.make:190: t13_cpp] Error 1 make[4]: Leaving directory '/build/gmsh-4.12.2+ds1/debian/build' make[3]: *** [CMakeFiles/Makefile2:1759: CMakeFiles/t13_cpp.dir/all] Error 2 make[4]: *** [CMakeFiles/t14_cpp.dir/build.make:190: t14_cpp] Error 1 make[4]: Leaving directory '/build/gmsh-4.12.2+ds1/debian/build' The attached patch makes the packages compile here locally - the patch *should* be backward compatible with the older opencascade currently in sid. -- tobi -- System Information: Debian Release: trixie/sid APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.7.12-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -1331,7 +1331,7 @@ if(FREETYPE_FOUND) if(OCC_VERSION AND OCC_VERSION VERSION_GREATER_EQUAL "7.8.0") set(OCC_CAF_LIBS_REQUIRED -TKXCAF TKLCAF TKVCAF TKCAF TKV3d TKService TKCDF) +TKXCAF TKLCAF TKVCAF TKCAF TKV3d TKService TKCDF TKDESTEP ) else() set(OCC_CAF_LIBS_REQUIRED TKXDESTEP TKXDEIGES TKXCAF TKLCAF TKVCAF TKCAF TKV3d TKService TKCDF)
Bug#1071284: src:horizon-eda: FTBFS with opencascade 7.8.1
Source: horizon-eda
Followup-For: Bug #1071284
Now with attachement :)
-- System Information:
Debian Release: trixie/sid
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500,
'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.7.12-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Description: Fix FTBFS with opencacscade 7.8
Author: Tobias Frost
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071284
Last-Update: 2024-05-19
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/Makefile
+++ b/Makefile
@@ -1036,7 +1036,7 @@
INC_OCE ?= -isystem /opt/opencascade/inc/ -isystem /mingw64/include/oce/
-isystem /usr/include/oce -isystem /usr/include/opencascade -isystem
${CASROOT}/include/opencascade -isystem ${CASROOT}/include/oce -isystem
/usr/local/include/OpenCASCADE
INC_PYTHON = $(shell $(PKG_CONFIG) --cflags python3 py3cairo)
OCE_LIBDIRS = -L/opt/opencascade/lib/ -L${CASROOT}/lib
-LDFLAGS_OCE = $(OCE_LIBDIRS) -lTKSTEP -lTKernel -lTKXCAF -lTKXSBase -lTKBRep
-lTKCDF -lTKXDESTEP -lTKLCAF -lTKMath -lTKMesh -lTKTopAlgo -lTKPrim -lTKBO
-lTKShHealing -lTKBRep -lTKG3d
+LDFLAGS_OCE = $(OCE_LIBDIRS) -lTKDESTEP -lTKernel -lTKXCAF -lTKXSBase
-lTKBRep -lTKCDF -lTKDESTEP -lTKLCAF -lTKMath -lTKMesh -lTKTopAlgo -lTKPrim
-lTKBO -lTKShHealing -lTKBRep -lTKG3d
ifeq ($(OS),Windows_NT)
LDFLAGS_OCE += -lTKV3d
endif
@@ -1117,7 +1117,7 @@
$(BUILDDIR)/horizon.so: $(OBJ_PYTHON) $(OBJ_SHARED) $(OBJ_SHARED_OCE)
$(ECHO) " $@"
- $(QUIET)$(CXX) $^ $(LDFLAGS) $(INC) $(CXXFLAGS) $(shell $(PKG_CONFIG)
--libs $(LIBS_COMMON) python3 glibmm-2.4 giomm-2.4 cairomm-1.0 py3cairo libpng
libarchive) -lpodofo $(OCE_LIBDIRS) -lTKXDESTEP -lOSMesa -shared -o $@
+ $(QUIET)$(CXX) $^ $(LDFLAGS) $(INC) $(CXXFLAGS) $(shell $(PKG_CONFIG)
--libs $(LIBS_COMMON) python3 glibmm-2.4 giomm-2.4 cairomm-1.0 py3cairo libpng
libarchive) -lpodofo $(OCE_LIBDIRS) -lTKDESTEP -lOSMesa -shared -o $@
$(OBJDIR)/%.o: %.c
$(QUIET)$(MKDIR) $(dir $@)
Bug#1071284: src:horizon-eda: FTBFS with opencascade 7.8.1
Source: horizon-eda Followup-For: Bug #1071284 Control: tags -1 +patch Patch attached that makes it compile with opencascade 7.8.1. It is unfortunatly not backward-compatible with older opencascade. -- tobi -- System Information: Debian Release: trixie/sid APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.7.12-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1071433: src:horizon: Builds with quiet rules
Source: horizon-eda Severity: normal Dear maintainer, the package has hardcoded quiet rules in its Makefile. This makes debugging compilation errors harder - like the current opencascade transistion - and is also a Policy violation (§4.9) The package build should be as verbose as reasonably possible, except where the terse tag is included in DEB_BUILD_OPTIONS (see debian/rules and DEB_BUILD_OPTIONS). This makes life easier for porters and bug squashers more generally, who can look at build logs for possible problems. To accomplish this, debian/rules should pass to the commands it invokes options that cause them to produce verbose output. The attached patch fixes this, but does not implement terse: --- a/Makefile +++ b/Makefile @@ -1003,7 +1003,7 @@ PICOBJDIR= $(BUILDDIR)/picobj GENDIR = $(BUILDDIR)/gen MKDIR= mkdir -p -QUIET= @ +QUIET= ECHO = @echo # Object files @@ -1036,7 +1036,7 @@ -- tobi -- System Information: Debian Release: trixie/sid APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.7.12-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1069942: RFS: imsprog/1.3.7-1 -- Linux chip programmer for CH341a devices
On Sat, May 18, 2024 at 09:42:56PM +0200, Fabio Fantoni wrote: > On Thu, 16 May 2024 12:47:44 +0200 Tobias Frost wrote: > > > > > > * Don't fixed: P: imsprog source: > > > package-uses-old-debhelper-compat-version 12 - I want to maintain > > > compatibility for |Jammy| and |Focal| releases. > > > > If you package for different distributions, let me recommend me to utilize > > dedicated branches for those, for example by following the DEP14 proposal; > > this will allow to optimize for the different Debian derivates. > > > > For a Debian upload, please use a acutal compat level; >12 has a lots of > > benefits. > > Hi, I think compat 12 is not too old and can be keeped for now to make > possible to do unofficial build and individual build (any people also > without experience) on multiple Debian versions and derivatives still > supported easier and faster using debian/latest. I disagree. Uploads to Debian are aimed for the next stable, not for old releases, therefore they should follow the current best practices, and this is not compat 12. DEP14 is designed to cater older (and other distributions), this would be a compromise. Also, debhelper is very often backported to older released, so many people will not even need to change back to an older compat level. Even Jammie and Focal have debhelper 13 available. IMHO There is no reason to stay at 12; while others might, I'll certainly will not sponsor level 12. > About creation of other packaging branches following DEP14 I think is good > only for official build (for example possible official backports), but > before I think is good update the package to 1.3.9-1 before consider doing > official backports and don't backports of 1.3.2-1. DEP14 is not only for backports, but also for other distributions, like Ubuntu, -- tobi
Bug#983365: linphone-desktop: chat messages
Control: severity -1 important This bugs seems to be at least partially fixed, at least it seems that the messages are now showing up, so this bug should no longer be RC. (If I'm wrong, severity can be readjusted if needed) -- tobi
Bug#1071283: src:freecad: FTBFS with opencascade 7.8.1
Package: freecad Version: 0.21.2+dfsg1-1 Followup-For: Bug #1071283 Control: tags -1 ftbfs fixed-upstream Seems so that there is an upstream fix: https://github.com/FreeCAD/FreeCAD/pull/11909/commits/8d94e48921be080de4e0b44abeb642d57d38512f (The patch does not apply cleanly to the version currently in sid, but as the PR has been merged upstream, I think this is fixed upstream.) -- tobi -- System Information: Debian Release: trixie/sid APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.7.12-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages freecad depends on: ii freecad-python3 0.21.2+dfsg1-1+b3 Versions of packages freecad recommends: ii calculix-ccx2.21-1 ii graphviz2.42.2-9+b1 ii python3-opencamlib 2023.01.11-5 Versions of packages freecad suggests: pn povray -- no debconf information
Bug#1071223: negen: Will FTBFS with next opencascade version 7.8.1
Source: netgen
Followup-For: Bug #1071223
Control: tags -1 ftbfs patch
Attached a patch that makes netgen compile.
Taken from upstream, see forwarded information.
--
tobi
-- System Information:
Debian Release: trixie/sid
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500,
'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.7.12-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Description: Fix for FTBFS with opencascade 7.8.1
Taken from upstream, with addtional bits (linkage) from the upstream bug.
and one addtional include removed.
Bug: https://github.com/NGSolve/netgen/issues/170
Origin:
https://github.com/NGSolve/netgen/commit/486c7d9bcb950dfb33c2a59b68eca3e720af4107
>From 6b89d2cf6203272d04d2738f145bc01b49d75186 Mon Sep 17 00:00:00 2001
From: "Hochsteger, Matthias"
Date: Wed, 6 Mar 2024 16:29:11 +0100
Subject: [PATCH] Compatibility with Opencascade 7.8
---
libsrc/meshing/basegeom.cpp | 13 +++--
libsrc/meshing/basegeom.hpp | 8
libsrc/occ/occ_edge.cpp | 5 -
libsrc/occ/occ_edge.hpp | 1 -
libsrc/occ/occ_face.cpp | 5 -
libsrc/occ/occ_face.hpp | 1 -
libsrc/occ/occ_solid.hpp| 2 --
libsrc/occ/occ_vertex.cpp | 5 -
libsrc/occ/occ_vertex.hpp | 1 -
libsrc/occ/occgeom.cpp | 7 ---
10 files changed, 7 insertions(+), 41 deletions(-)
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -377,25 +377,20 @@
TKGeomAlgo
TKGeomBase
TKHLR
- TKIGES
TKLCAF
TKMath
TKMesh
TKOffset
TKPrim
- TKSTEP
- TKSTEP209
- TKSTEPAttr
- TKSTEPBase
- TKSTL
+ TKDESTL
TKService
TKShHealing
TKTopAlgo
TKV3d
TKVCAF
TKXCAF
- TKXDEIGES
- TKXDESTEP
+ TKDEIGES
+ TKDESTEP
TKXSBase
TKernel
)
--- a/libsrc/meshing/basegeom.cpp
+++ b/libsrc/meshing/basegeom.cpp
@@ -568,12 +568,13 @@
auto & identifications = mesh.GetIdentifications();
-std::map vert2meshpt;
+Array vert2meshpt(vertices.Size());
+vert2meshpt = PointIndex::INVALID;
for(auto & vert : vertices)
{
auto pi = mesh.AddPoint(vert->GetPoint(), vert->properties.layer);
tree.Insert(mesh[pi], pi);
-vert2meshpt[vert->GetHash()] = pi;
+vert2meshpt[vert->nr] = pi;
mesh[pi].Singularity(vert->properties.hpref);
mesh[pi].SetType(FIXEDPOINT);
@@ -585,8 +586,8 @@
for(auto & vert : vertices)
for(auto & ident : vert->identifications)
-identifications.Add(vert2meshpt[ident.from->GetHash()],
-vert2meshpt[ident.to->GetHash()],
+identifications.Add(vert2meshpt[ident.from->nr],
+vert2meshpt[ident.to->nr],
ident.name,
ident.type);
@@ -600,8 +601,8 @@
auto edge = edges[edgenr].get();
PointIndex startp, endp;
// throws if points are not found
-startp = vert2meshpt.at(edge->GetStartVertex().GetHash());
-endp = vert2meshpt.at(edge->GetEndVertex().GetHash());
+startp = vert2meshpt[edge->GetStartVertex().nr];
+endp = vert2meshpt[edge->GetEndVertex().nr];
// ignore collapsed edges
if(startp == endp && edge->GetLength() < 1e-10 * bounding_box.Diam())
--- a/libsrc/meshing/basegeom.hpp
+++ b/libsrc/meshing/basegeom.hpp
@@ -68,7 +68,6 @@
Transformation<3> primary_to_me;
virtual ~GeometryShape() {}
-virtual size_t GetHash() const = 0;
virtual bool IsMappedShape( const GeometryShape & other, const
Transformation<3> & trafo, double tolerance ) const;
};
@@ -320,13 +319,6 @@
throw Exception("Base geometry get tangent called");
}
-virtual size_t GetEdgeIndex(const GeometryEdge& edge) const
-{
- for(auto i : Range(edges))
-if(edge.GetHash() == edges[i]->GetHash())
- return i;
- throw Exception("Couldn't find edge index");
-}
virtual void Save (const filesystem::path & filename) const;
virtual void SaveToMeshFile (ostream & /* ost */) const { ; }
};
--- a/libsrc/occ/occ_edge.cpp
+++ b/libsrc/occ/occ_edge.cpp
@@ -53,11 +53,6 @@
throw Exception(ToString("not implemented") + __FILE__ + ":" +
ToString(__LINE__));
}
-size_t OCCEdge::GetHash() const
-{
- return edge.HashCode(std::numeric_limits::max());
-}
-
void OCCEdge::ProjectPoint(Point<3>& p, EdgePointGeomInfo* gi) const
{
auto pnt = ng2occ(p);
--- a/libsrc/occ/occ_edge.hpp
+++ b/libsrc/occ/occ_edge.hpp
@@ -36,7 +36,6 @@
Poi
Bug#1071284: src:horizon-eda: FTBFS with opencascade 7.8.1
Source: horizon-eda Severity: important Tags: ftbfs horizon-eda fails to build ; it seems has hardcoded library names in its build system and as opencascade has 7.8.1 slightly changed them (eg s/TKXDESTEP/-TKDESTEP/) horizon-eda FTBFS now: build/horizon.so /usr/bin/ld.gold: error: cannot find -lTKXDESTEP collect2: error: ld returned 1 exit status make[2]: *** [Makefile:1120: build/horizon.so] Error 1 make[2]: Leaving directory '/build/horizon-eda-2.5.0' make[1]: *** [debian/rules:21: override_dh_auto_build] Error 2 make[1]: Leaving directory '/build/horizon-eda-2.5.0' make: *** [debian/rules:17: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 I: copying local configuration E: Failed autobuilding of package PS: Please make the build verbose. Currently it only shows e.g build/picobj/src/canvas3d/canvas_mesh.o build/picobj/src/canvas3d/background_renderer.o build/picobj/src/canvas3d/wall_renderer.o build/picobj/src/canvas3d/cover_renderer.o build/picobj/src/canvas3d/face_renderer.o build/picobj/src/canvas3d/point_renderer.o build/picobj/src/canvas/gl_util.o but it should output the commands for compiling, see policy 4.9 The package build should be as verbose as reasonably possible, except where the terse tag is included in DEB_BUILD_OPTIONS (see debian/rules and DEB_BUILD_OPTIONS). This makes life easier for porters and bug squashers more generally, who can look at build logs for possible problems. To accomplish this, debian/rules should pass to the commands it invokes options that cause them to produce verbose output. For example, the build target should pass --disable-silent-rules to any configure scripts. See also Binaries. -- System Information: Debian Release: trixie/sid APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.7.12-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1071283: src:freecad: FTBFS with opencascade 7.8.1
Package: freecad Version: 0.21.2+dfsg1-1 Severity: important Tags: ftbfs freecad fails to build with opencascade 7.8.1, which is now in experimental. (Once the transistion starts, this bug will become RC.) snippet attached: [ 0%] Linking CXX shared library ../../../lib/libSMDS.so cd /build/freecad-0.21.2+dfsg1/debian/build-py3/src/3rdParty/salomesmesh && /usr/bin/cmake -E cmake_link_script CMakeFiles/SMDS.dir/link.txt --verbose=1 /usr/lib/ccache/c++ -fPIC -Wall -Wextra -Wno-write-strings -g -O2 -ffile-prefix-map=/build/freecad-0.21.2+dfsg1=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -fpermissive -I/usr/include/python3.11 -flto -Wno-sign-compare -Wno-reorder -Wno-switch -Wno-unused-variable -Wno-unused-but-set-variable -Wno-comment -Wno-unused-parameter -Wno-empty-body -Wno-pedantic -Wno-unused-result -Wno-cast-function-type -Wno-maybe-uninitialized -Wno-missing-field-initializers -O2 -g -DNDEBUG -L/usr/lib/x86_64-linux-gnu/openmpi/lib -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -Wl,-flto -shared -Wl,-soname,libSMDS.so -o ../../../lib/libSMDS.so CMakeFiles/SMDS.dir/src/SMDS/SMDS_BallElement.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_Downward.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_EdgePosition.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_FaceOfEdges.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_FaceOfNodes.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_FacePosition.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_IteratorOfElements.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_LinearEdge.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_Mesh.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_Mesh0DElement.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_MeshCell.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_MeshEdge.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_MeshElement.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_MeshElementIDFactory.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_MeshFace.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_MeshGroup.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_MeshIDFactory.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_MeshNode.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_MeshNodeIDFactory.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_MeshObject.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_MeshVolume.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_PolygonalFaceOfNodes.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_PolyhedralVolumeOfNodes.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_Position.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_QuadraticEdge.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_QuadraticFaceOfNodes.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_QuadraticVolumeOfNodes.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_SpacePosition.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_UnstructuredGrid.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_VertexPosition.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_VolumeOfFaces.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_VolumeOfNodes.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_VolumeTool.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_VtkCellIterator.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_VtkEdge.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_VtkFace.cpp.o CMakeFiles/SMDS.dir/src/SMDS/SMDS_VtkVolume.cpp.o CMakeFiles/SMDS.dir/src/SMDS/Utils_SALOME_Exception.cpp.o CMakeFiles/SMDS.dir/src/SMDS/chrono.cpp.o CMakeFiles/SMDS.dir/src/SMDS/duplicate.cpp.o -L/usr/lib/x86_64-linux-gnu/hdf5/serial -L/usr/lib/x86_64-linux-gnu/openmpi/lib -Wl,-rpath,/usr/lib/x86_64-linux-gnu/hdf5/serial:/usr/lib/x86_64-linux-gnu/openmpi/lib: -lhdf5 -lmpi_cxx -lmpi -lTKIGES -lTKSTL /usr/lib/x86_64-linux-gnu/libTKXSBase.so.7.8.1 /usr/lib/x86_64-linux-gnu/libTKOffset.so.7.8.1 -lTKSTEPBase -lTKSTEPAttr -lTKSTEP209 -lTKSTEP /usr/lib/x86_64-linux-gnu/libTKFeat.so.7.8.1 /usr/lib/x86_64-linux-gnu/libTKBin.so.7.8.1 /usr/lib/x86_64-linux-gnu/libTKBinL.so.7.8.1 -lTKXDESTEP -lTKXDEIGES /usr/lib/x86_64-linux-gnu/libTKMeshVS.so.7.8.1 /usr/lib/x86_64-linux-gnu/libTKRWMesh.so.7.8.1 /usr/lib/x86_64-linux-gnu/libvtkFiltersVerdict-9.1.so.9.1.0 /usr/lib/x86_64-linux-gnu/libvtkIOMPIParallel-9.1.so.9.1.0 /usr/lib/x86_64-linux-gnu/libvtkInteractionStyle-9.1.so.9.1.0 /usr/lib/x86_64-linux-gnu/libvtkRenderingFreeType-9.1.so.9.1.0 /usr/lib/x86_64-linux-gnu/libvtkRenderingOpenGL2-9.1.so.9.1.0 /usr/lib/x86_64-linux-gnu/libTKFillet.so.7.8.1 /usr/lib/x86_64-linux-gnu/libTKBool.so.7.8.1 /usr/lib/x86_64-linux-gnu/libTKXCAF.so.7.8.1 /usr/lib/x86_64-linux-gnu/libTKVCAF.so.7.8.1 /usr/lib/x86_64-linux-gnu/libTKCAF.so.7.8.1 /usr/lib/x86_64-linux-gnu/libTKBO.so.7.8.1 /usr/lib/x86_64-linux-gnu/libTKPrim.so.7.8.1 /usr/lib/x86_64-linux-gnu/libTKLCAF.so.7.8.1 /usr/lib/x86_64-linux-gnu/libTKCDF.so.7.8.1 /usr/lib/x86_64-linux-gnu/libTKV3d.so.7.8.1 /usr/lib/x86_64-linux-gnu/libTKMesh.so.7.8.1 /usr/lib/x86_64-linux-gnu/libTKShHealing.so.7.8.1 /usr/lib/x86_64-linux-gnu/libTKHLR.so.7.8.1 /usr/lib/x86_64-linux-gnu/libTKTopAlgo.so.7.8.1 /usr/lib/x86_64-linux-gnu/libTKGeomAlgo.so.7.8.1 /usr/lib/x86_64-linux-gnu/libTKBRep.so.7.8.1 /u
Bug#1071223: negen: Will FTBFS with next opencascade version 7.8.1
Source: netgen Severity: important Tags: ftbfs Dear maintainers, I've just uploaded opencascade 7.8.1 to experimental (currently sitting in NEW waiting for ftp master approval) Unfortunatly, netgen fails with the new version, as there are ABI changes (e.g dropped header files.) [ 48%] Building CXX object CMakeFiles/nglib.dir/libsrc/occ/Partition_Loop3d.cxx.o /usr/bin/c++ -DFFMPEG -DHAVE_DLFCN_H -DHAVE_FREEIMAGE -DHAVE_FREETYPE -DHAVE_OPENGL_EXT -DHAVE_RAPIDJSON -DHAVE_TBB -DHAVE_TK -DHAVE_XLIB -DJPEGLIB -DMETIS -DNETGEN_PYTHON -DNG_MPI4PY -DNG_PYTHON -DOCCGEOMETRY -DOCC_CONVERT_SIGNALS -DPARALLEL -DPYBIND11_SIMPLE_GIL_MANAGEMENT -D__STDC_CONSTANT_MACROS -Dnglib_EXPORTS -I/build/netgen-6.2.2401+dfsg1/obj-x86_64-linux-gnu -I/build/netgen-6.2.2401+dfsg1 -I/build/netgen-6.2.2401+dfsg1/include -I/build/netgen-6.2.2401+dfsg1/libsrc -I/build/netgen-6.2.2401+dfsg1/libsrc/include -I/usr/include/python3.11 -I/usr/lib/python3/dist-packages/mpi4py/include/mpi4py -I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -isystem /usr/include/opencascade -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/build/netgen-6.2.2401+dfsg1=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -g -DNDEBUG -std=gnu++17 -fPIC -fvisibility=hidden -MD -MT CMakeFiles/nglib.dir/libsrc/occ/Partition_Loop3d.cxx.o -MF CMakeFiles/nglib.dir/libsrc/occ/Partition_Loop3d.cxx.o.d -o CMakeFiles/nglib.dir/libsrc/occ/Partition_Loop3d.cxx.o -c /build/netgen-6.2.2401+dfsg1/libsrc/occ/Partition_Loop3d.cxx In file included from /build/netgen-6.2.2401+dfsg1/libsrc/occ/Partition_Loop3d.jxx:29, from /build/netgen-6.2.2401+dfsg1/libsrc/occ/Partition_Loop3d.ixx:10, from /build/netgen-6.2.2401+dfsg1/libsrc/occ/Partition_Loop3d.cxx:14: /build/netgen-6.2.2401+dfsg1/libsrc/occ/Partition_Loop3d.hxx:32:13: fatal error: TopTools_OrientedShapeMapHasher.hxx: No such file or directory 32 |#include | ^ compilation terminated. -- tobi -- System Information: Debian Release: trixie/sid APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.7.12-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1069942: RFS: imsprog/1.3.7-1 -- Linux chip programmer for CH341a devices
Hi, thanks for working on the package! > Hello, Tobias! > I've done some work on the bugs :) > > In version v1.3.9: > > * Fixed: There is a spelling error "copyed" in in 99-CH341.rules. > * Fixed (metadata changed): W: imsprog: > appstream-metadata-missing-modalias-provide > usr/lib/udev/rules.d/99-CH341.rules > * Fixed: As you are upstream, you could wrap README.md at 80 chars per > line :) > * Fixed: src:imsprog: Does not rebuild qt language files > > * Don't fixed: P: imsprog source: > package-uses-old-debhelper-compat-version 12 - I want to maintain > compatibility for |Jammy| and |Focal| releases. If you package for different distributions, let me recommend me to utilize dedicated branches for those, for example by following the DEP14 proposal; this will allow to optimize for the different Debian derivates. For a Debian upload, please use a acutal compat level; >12 has a lots of benefits. -- tobi > Please check this package and send me Lintian's warnings. > Regards, Mikhail
Bug#1070991: RFS: libcdio-paranoia/10.2+2.0.2-1 -- audio CD reading utility which includes extra data verification features
Hi Phillippe, a short review: - package could use some modernization: - it is still using d/compat, at the very old level 11 - d/copyright is not dep5 Would be cool if you could update those parts. -- tobi On Sun, May 12, 2024 at 05:45:13PM +0200, Philippe SWARTVAGHER wrote: > Package: sponsorship-requests > Severity: normal > > Dear mentors, > > I am looking for a sponsor for my package "libcdio-paranoia": > > * Package name : libcdio-paranoia >Version : 10.2+2.0.2-1 >Upstream contact : [fill in name and email of upstream] > * URL : https://www.gnu.org/software/libcdio/ > * License : [fill in] > * Vcs : https://salsa.debian.org/debian/libcdio-paranoia >Section : libs > > The source builds the following binary packages: > > libcdio-cdda-dev - library to read and control digital audio CDs > (development files) > libcdio-cdda2t64 - library to read and control digital audio CDs > libcdio-paranoia-dev - library to read digital audio CDs with error > correction (development files) > libcdio-paranoia2t64 - library to read digital audio CDs with error > correction > cd-paranoia - audio CD reading utility which includes extra data > verification features > > To access further information about this package, please visit the > following URL: > > https://mentors.debian.net/package/libcdio-paranoia/ > > Alternatively, you can download the package with 'dget' using this command: > > dget -x > https://mentors.debian.net/debian/pool/main/libc/libcdio-paranoia/libcdio-paranoia_10.2+2.0.2-1.dsc > > Changes since the last upload: > > libcdio-paranoia (10.2+2.0.2-1) unstable; urgency=medium > . >[ Debian Janitor ] >* Remove constraints unnecessary since buster (oldstable): > + Build-Depends: Drop versioned constraint on libcdio-dev. > + libcdio-cdda-dev: Drop versioned constraint on libcdio-dev in > Depends. > + libcdio-paranoia-dev: Drop versioned constraint on libcdio-dev > in Depends. > + cd-paranoia: Drop versioned constraint on libcdio-utils in Replaces. > + cd-paranoia: Drop versioned constraint on libcdio-utils in Breaks. > . >[ Philippe SWARTVAGHER ] >* d/control: update Build-Depends packages, as suggested by Lintian >* New upstream release > - Drop all patches (applied upstream). > - Closes: #981017. >* Bump Standards-Version to 4.7.0 (no change) >* Add patches to fix typos > > Regards, > -- > Philippe >
Bug#1069906: RFS: vzlogger/0.8.5-1 -- Fixes for the migration to testing
Control: tags -1 moreinfo Hi Joachim, On Sun, May 12, 2024 at 01:59:22PM +0200, Joachim Zobel wrote: > > An updated 0.8.5-1 has been uploaded. It's nice that you've picked up my suggestions regarding the README.md… However, recycling upstream version numbers (as upstream) should be avoided, as there are now two 0.8.5 in the world. Please avoid that. The watch file is not working: tobi@gondor:~/workspace/deb/mentors/JoachimZobel/vzlogger/debcheckout/vzlogger$ uscan --force-download uscan warn: In directory ., downloading https://github.com/volkszaehler/vzlogger/releases/download/v0.8.5/vzlogger-0.8.5.tar.gz failed: 404 Not Found uscan warn: No upstream tarball downloaded. No further processing with mk_origtargz ... (Tagging moreinfo because of the watchfile.) > Sincerely, > Joachim >
Bug#1069906: RFS: vzlogger/0.8.5-1 -- Fixes for the migration to testing
On Sun, May 12, 2024 at 01:59:22PM +0200, Joachim Zobel wrote: > (forgotten cc) > > Am Freitag, dem 03.05.2024 um 18:50 +0200 schrieb Tobias Frost: > > reviewing your new package: > > > > - d/changelog > > - generally documents only changes to the packaging, not "upstream" > changes > > (the entry "Fixed logrotate conf user name" is an upstream > change.) > > There are exceptions, like if it a very noteworthy change, but > this > > is one isn't in that category. > > - When packaging a new upstream version, you say so in the > changelog. > > (Like first changelog entry: > > * New upstream version. > > ) > > - There are undocumented changes, for example the change to the > > Standard-Version. > > > > Done. > > > A nitpick on d/rules: > > I'm a fan of declarative syntax, so I'd replace the dh_clean > override > > with specifing the file to be deleted in the file d/clean. (If you > feel > > different about this, it is ok to ignore my nitpicking) > > Done, thx. > > > Remarks on Readme.md: > > - It cointains only information not relevant when the user is > > installing the binary package (like how to build, how to install > and > > where to find the packages), so it should not be installed into > > the binary package. > > Not exactly. There is the important line "Our packages are built with > MQTT support, but without OMS support.". In addition it is a moving > target. So I'd prefer to keep it as now. This information would go into the long description of the package, (README.md is not available pre-install, and this is something the user wants to knowbeforehand; using README.md for this purpose is very unusal in Debian.) > > - "Debian" is written with a captial "D". > > Done. > > > - The sentence "Unfortunately Debian armhf packages do not > > run on Raspberry Pi 1 although the architecture on the RPi is > named armhf. > > Using Raspian armhf packages fixes that." is a bit hard to parse, > a > > bit off: > > - Raspberry Pi 1 is supported by the Debian armel architecture, > so people > > running (real) Debian on the Pi 1 need to use "armel" not > "armhf". > > - Paspian has been renamed to Raspberry Pi OS, so the naming > should > > maybe be also updated. > > Done. During the discussion more changes were added. > > > Maybe this should be separated into a Debian and Raspberry Pi OS > > section? (They are different distributions anyways…) > > The handling is very similar from the users perspective. > > > > > Some parts already mentioned for the previous upload, would be great > if > > you could start tackling them: > > > > As you are involved with upstream: > > The manpage, initfile, systemd service file should probably be > included in the > > upstream part, it is not only useful for Debian alone. > > > > It is currently under discussion if other installation methods are > still needed. I'd still say README.md shouldn't end up in the binary package, as it only covers installation topics, which are irrelevant to our users. > > Linitian: (I've pre-filtered them a bit already on those that should > be > > investigaged. If harderning is working now, override the linitian I: > tag.) > > I: vzlogger source: debian-rules-parses-dpkg-parsechangelog > [debian/rules:15] > > I: vzlogger: hardening-no-bindnow [usr/bin/vzlogger] > > I: vzlogger: systemd-service-file-missing-documentation-key > [usr/lib/systemd/system/vzlogger.service] > > P: vzlogger source: trailing-whitespace [debian/changelog:10] > > P: vzlogger source: trailing-whitespace [debian/changelog:4] > > P: vzlogger source: trailing-whitespace [debian/control:17] > > P: vzlogger source: trailing-whitespace [debian/control:40] > > P: vzlogger source: trailing-whitespace [debian/rules:45] > > X: vzlogger: systemd-service-file-missing-hardening-features > [usr/lib/systemd/system/vzlogger.service] > > X: vzlogger source: upstream-metadata-file-is-missing > > All done except for upstream-metadata-file-is-missing. I don't think > this is of much use for a service. > > An updated 0.8.5-1 has been uploaded. > > Sincerely, > Joachim
Bug#1070983: supertuxkart: symbol lookup error: undefined symbol
Control: reassign -1 src:shaderc Control: affects -1 src:supertuxkart Control: fixed -1 2023.8-1 Hi Bernd, It seems that that symbol is missing in libshaderci [1] , and it seems that it is in version 2023.8-1 (which is currently only in unstable.) So, if you feel comfortable pull in that package from unstable, you will be able to play the game. Reassignin to shaderc, and CC'ing the maintainer of shaderc, maybe they have an idea what's going and can check if something has to be done (maybe to make it migrate to testing…) [1] LD_WARN=1 /lib64/ld-linux-x86-64.so.2 /lib/x86_64-linux-gnu/libshaderc.so.1 /lib/x86_64-linux-gnu/libshaderc.so.1: symbol lookup error: /lib/x86_64-linux-gnu/libshaderc.so.1: undefined symbol: _ZTVN8spvtools5utils5TimerE -- tobi On Sun, May 12, 2024 at 02:49:06PM +0200, Bernd Dau wrote: > Package: supertuxkart > Version: 1.4+dfsg-4 > Severity: grave > Justification: renders package unusable > X-Debbugs-Cc: b...@zockertown.de > > Dear Maintainer, > > Trying to start supertuxkart from console brings this as answer, after last > full-upgrade > > supertuxkart: symbol lookup error: /lib/x86_64-linux-gnu/libshaderc.so.1: > undefined symbol: _ZTVN8spvtools5utils5TimerE > This is my first bugreort, hope it is ok. > Tanks and have a nice day > Bernd, aka bed > > -- System Information: > Debian Release: trixie/sid > APT prefers stable-security > APT policy: (500, 'stable-security'), (500, 'testing'), (500, 'stable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 6.7.12-amd64 (SMP w/16 CPU threads; PREEMPT) > Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not > set > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages supertuxkart depends on: > ii libangelscript2.35.1t64 2.35.1+ds-3.1 > ii libbluetooth35.71-1 > ii libc62.38-10 > ii libcurl3t64-gnutls 8.7.1-5 > ii libfreetype6 2.13.2+dfsg-1+b4 > ii libgcc-s114-20240330-1 > ii libharfbuzz0b8.3.0-2+b1 > ii libjpeg62-turbo 1:2.1.5-3 > ii libmbedcrypto7t642.28.8-1 > ii libmcpp0 2.7.2-5.1 > ii libopenal1 1:1.23.1-4+b1 > ii libpng16-16t64 1.6.43-5 > ii libsdl2-2.0-02.30.2+dfsg-1 > ii libshaderc1 2023.2-1 > ii libsqlite3-0 3.45.3-1 > ii libsquish0 1.15-3+b1 > ii libstdc++6 14-20240330-1 > ii libvorbisfile3 1.3.7-2 > ii supertuxkart-data1.4+dfsg-4 > ii zlib1g 1:1.3.dfsg-3.1 > > supertuxkart recommends no packages. > > supertuxkart suggests no packages. > > -- no debconf information >
Bug#1070331: RFS: nq/0.5-0.1 [NMU] -- Lightweight queue system
On Sun, May 12, 2024 at 02:34:15PM +0200, Preuße, Hilmar wrote: > On 11.05.2024 09:08, Tobias Frost wrote: > > Hi, > > > Please also announce the NMU / RFS to the package maintainer, > > preferable as bug reported against it. Thanks! > > > The package is flagged as LowNMU [1], which says: > > "You don't need to contact the maintainers beforehand, and you don't need to > use a delayed upload queue. If the package maintainer or maintainer group is > active, it is polite to let them have a stab at fixing the problem first." > > Given the fact that the last upload was 3.5 years ago I'd assume that the > maintainers group is non-active. Hence I did not inform them. LowNMU just says you can upload into DELAYED/0, or directly, but not that communication is not needed beforehand. It explictly says [1]: "at any time, as long as the NMU procedure in the Debian Developer's Reference is otherwise followed" The Developers Reference [2] explictly says: "Have you clearly expressed your intention to NMU, at least in the BTS? If that didn't generate any feedback, it might also be a good idea to try to contact the maintainer by other means (email to the maintainer addresses or private email, IRC). So, no, announcing the NMU is not optional, it is the bare minimum. [1] https://wiki.debian.org/LowThresholdNmu [2] > Hilmar > > [1] https://tracker.debian.org/pkg/nq > -- > -- > sigfault > -- tobi signature.asc Description: PGP signature
Bug#1070906: ecryptfs-utils: mount fails with "No such file or directory" after user switch with sudo -i -u ...
Package: ecryptfs-utils Version: 111-6 Severity: normal Tags: patch Dear Maintainer, ecrypts-mount-private is failing when starting a user session via sudo (and probably other methods where no password is required for login, e.g. ssh with keyfile) Error message is: "mount: No such file or directory" and home directory is not mounted. Reason is that the user keyring is not linked to the session keyring. see also here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870126#15 Easy fix is to add a file into /etc/profile.d which does this linking, a one- liner in it is sufficient: keyctl link @u @s After this small change ecryptfs-mount-private is working as intended. This shouldn't raise any safety concerns as all is done with normal user permissions, the same is done by su (resp. pam) automatically. If the user keyring is already linked this additional command will do nothing and doesn't do any harm. So please include a file in the package which does this fix. -- System Information: Debian Release: 12.5 APT prefers stable APT policy: (990, 'stable'), (900, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-18-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages ecryptfs-utils depends on: ii gettext-base0.21-12 ii keyutils1.6.3-2 ii libc6 2.36-9+deb12u4 ii libecryptfs1111-6 ii libgpgme11 1.18.0-3+b1 ii libkeyutils11.6.3-2 ii libpam-runtime 1.5.2-6+deb12u1 ii libpam0g1.5.2-6+deb12u1 ii libtspi10.3.15-0.3 ecryptfs-utils recommends no packages. Versions of packages ecryptfs-utils suggests: ii cryptsetup 2:2.6.1-4~deb12u2 ii rsync 3.2.7-1 -- no debconf information
Bug#1070890: qabc: [src:qabc] VCS-* in d/control is not pointing to the packaging repository
Source: qabc Severity: minor Dear Maintainer, during review I've seen that VCS-* is pointing to the upstream repo, according to Policy §5.6.26 "The purpose of the following fields is to indicate a publicly accessible repository where the Debian source package is developed." -- IOW where the debian package is maintained. (It seems you are just missing to sepcify the branch, see Policy for details how to do that.) -- tobi
Bug#1069620: RFS: lua-mode/20231023~git-1 -- Emacs major-mode for editing Lua programs
Hi Xiyue, when packaging a git snapshot, I feel this should be indicated in the upstream version that it is based on the old one, something like + In your case I'd 20210802+git20231023 as upstream version. Long time ago I did something like that for dhewm3, you can see the watch file here: https://salsa.debian.org/games-team/dhewm3/-/blob/debian/1.5.0+git20181221+dfsg-1/debian/watch?ref_type=tags (not marking moreinfo, as other people might see that differently.) -- tobi On Sun, Apr 21, 2024 at 10:02:48AM -0700, Xiyue Deng wrote: > Package: sponsorship-requests > Severity: normal > > Dear mentors, > > I am looking for a sponsor for my package "lua-mode": > > * Package name : lua-mode >Version : 20231023~git-1 >Upstream contact : immerrr > * URL : https://github.com/immerrr/lua-mode > * License : GPL-3+ > * Vcs : https://salsa.debian.org/emacsen-team/lua-mode >Section : lisp > > The source builds the following binary packages: > > elpa-lua-mode - Emacs major-mode for editing Lua programs > > To access further information about this package, please visit the following > URL: > > https://mentors.debian.net/package/lua-mode/ > > Alternatively, you can download the package with 'dget' using this command: > > dget -x > https://mentors.debian.net/debian/pool/main/l/lua-mode/lua-mode_20231023~git-1.dsc > > Changes since the last upload: > > lua-mode (20231023~git-1) unstable; urgency=medium > . >* Sync to latest upstream snapshot (d074e41) >* Drop the patch applied upstream and reorder the remaining patch >* Update upstream license to GPL-3+ following upstream change >* Add a missing upstream copyright holder > > Regards, > -- > Xiyue Deng >
Bug#1068724: RFS: gensync/2.0.5-1 [ITP] -- a library for efficient synchronization of data over a network.
Control: reopen -1 Control: forcemerge 1069696 -1 Hi Chen, In future, please do not file new RFS bugs, instead modify the existing one until a package has been sponsored. (forcemerge: FTR, the new one is #1069696, let that one be the leading one) -- tobi On Tue, Apr 09, 2024 at 06:53:58PM +, Chen, Xingyu wrote: > Package: sponsorship-requests > Severity: wishlist > > Dear mentors, > > I am looking for a sponsor for my package "gensync": > > * Package name : gensync >Version : 2.0.5-1 >Upstream contact : project> > * URL : https://github.com/nislab/gensync > * License : > * Vcs : [fill in URL of packaging vcs] >Section : libs > > The source builds the following binary packages: > > gensync - a library for efficient synchronization of data over a network. > Gensync is a library that uses many different syncing algorithms to sync data > between two nodes in a network. These algorithms include IBLTs, CPISyncs, > HashSyncs, Cuckoo Syncs, and more. > > To access further information about this package, please visit the following > URL: > > https://mentors.debian.net/package/gensync/ > > Alternatively, you can download the package with 'dget' using this command: > > dget -x > https://mentors.debian.net/debian/pool/main/g/gensync/gensync_2.0.5-1.dsc > > Changes for the initial release: > > gensync (2.0.5-1) UNRELEASED; urgency=medium > . >* Initial release (Closes: #) > > Regards, > -- > Kevin Chen >
Bug#1069083: RFS: runit-services/0.7.2 -- UNIX init scheme with service supervision (services)
On Tue, Apr 16, 2024 at 09:39:58AM +0200, Lorenzo wrote: > Control: block -1 by 1067525 > > this fix need to go to unstable because elogind 255.4.1 is already > there, but runit-services depends on runit > 2.1.2-56 (unstable is at > 2.1.2-54) so 1067525 needs to be uploaded first or together with this > one, otherwise runit-services is not installable Ok, just saw that one. Please note that this fact must be stated in d/changelog, something like "Upload to unstable." -- tobi > On Tue, 16 Apr 2024 09:30:08 +0200 Lorenzo wrote: > > Package: sponsorship-requests > > Severity: normal > > > > Dear mentors, > > > > I am looking for a sponsor for my package "runit-services": > > > > * Package name : runit-services > >Version : 0.7.2 > >Upstream contact : [fill in name and email of upstream] > > * URL : [fill in URL of upstream's web site] > > * License : BSD-3-Clause, GPL-2.0+, GPL-3+, CC0-1.0 > > * Vcs : > >https://salsa.debian.org/Lorenzo.ru.g-guest/runit-services Section > > : admin > > > > The source builds the following binary packages: > > > > runit-services - UNIX init scheme with service supervision > > (services) > > > > To access further information about this package, please visit the > > following URL: > > > > https://mentors.debian.net/package/runit-services/ > > > > Alternatively, you can download the package with 'dget' using this > > command: > > > > dget -x > > > > https://mentors.debian.net/debian/pool/main/r/runit-services/runit-services_0.7.2.dsc > > > > Git repo: > > > > https://salsa.debian.org/Lorenzo.ru.g-guest/runit-services/-/tree/next?ref_type=heads > > > > Changes since the last upload: > > > > runit-services (0.7.2) unstable; urgency=medium > > . > >* Fix elogind service (Closes: #1069075) > > > > Regards, > > Lorenzo > > > > >
Bug#1069083: RFS: runit-services/0.7.2 -- UNIX init scheme with service supervision (services)
Control: tags -1 moreinfo Hi Lorenzo, the last uploads where to experimental, this one targets unstable but that is not mentioned in the changelog, so I guess this was accidential? -- tobi On Tue, Apr 16, 2024 at 09:30:08AM +0200, Lorenzo wrote: > Package: sponsorship-requests > Severity: normal > > Dear mentors, > > I am looking for a sponsor for my package "runit-services": > > * Package name : runit-services >Version : 0.7.2 >Upstream contact : [fill in name and email of upstream] > * URL : [fill in URL of upstream's web site] > * License : BSD-3-Clause, GPL-2.0+, GPL-3+, CC0-1.0 > * Vcs : >https://salsa.debian.org/Lorenzo.ru.g-guest/runit-services Section > : admin > > The source builds the following binary packages: > > runit-services - UNIX init scheme with service supervision (services) > > To access further information about this package, please visit the > following URL: > > https://mentors.debian.net/package/runit-services/ > > Alternatively, you can download the package with 'dget' using this > command: > > dget -x > > https://mentors.debian.net/debian/pool/main/r/runit-services/runit-services_0.7.2.dsc > > Git repo: > > https://salsa.debian.org/Lorenzo.ru.g-guest/runit-services/-/tree/next?ref_type=heads > > Changes since the last upload: > > runit-services (0.7.2) unstable; urgency=medium > . >* Fix elogind service (Closes: #1069075) > > Regards, > Lorenzo >
Bug#1069696: RFS: gensync/2.0.5-1 [ITP] -- a library for efficient synchronization of data over a network.
Control: tags -1 moreinfo Hi Chen, please take a look at [1] -- the page indicates a lots of problems with your package, especially the lintian errors, warnings and informational tags. That means your package is not yet ready to be reviewed in depth. Please fix those linitian erros, then remove the moreinfo tag. As you seems to be upstream, please read https://wiki.debian.org/UpstreamGuide Cheers, -- tobi [1] https://mentors.debian.net/package/gensync/ On Mon, Apr 22, 2024 at 09:43:03PM +, Chen, Xingyu wrote: > Package: sponsorship-requests > Severity: wishlist > > Dear mentors, > > I am looking for a sponsor for my package "gensync": > > * Package name : gensync >Version : 2.0.5-1 >Upstream contact : Kevin Chen > * URL : https://github.com/nislab/gensync-lib > * License : GPL > * Vcs : >Section : libs > > The source builds the following binary packages: > > gensync - a library for efficient synchronization of data over a network. > Gensync is a library that uses many different syncing algorithms to sync data > between two nodes in a network. These algorithms include IBLTs, CPISyncs, > HashSyncs, Cuckoo Syncs, and more. > > To access further information about this package, please visit the following > URL: > > https://mentors.debian.net/package/gensync/ > > Alternatively, you can download the package with 'dget' using this command: > > dget -x > https://mentors.debian.net/debian/pool/main/g/gensync/gensync_2.0.5-1.dsc > > Changes for the initial release: > > gensync (2.0.5-1) UNRELEASED; urgency=medium > . >* Initial release (Closes: #1069684) > > Regards, > -- > Kevin Chen > >
Bug#1069942: RFS: imsprog/1.3.7-1 -- Linux chip programmer for CH341a devices
Control: tags -1 moreinfo Hi Mikhail, Thanks for the update. There is one thing I'd like to fixed: The qm language files needs to be recreated at build time. As you are upstream, you can incoorporate that change upstream (and drop the binary files from your tarball) There is a spelling error "copyed" in in 99-CH341.rules. Linitian to be checked (verified and if not a false positive fixed otherwise overriden) W: imsprog: appstream-metadata-missing-modalias-provide usr/lib/udev/rules.d/99-CH341.rules (likekly false positive) I: imsprog: hardening-no-bindnow [usr/bin/IMSProg] I: imsprog: hardening-no-bindnow [usr/bin/IMSProg_editor] P: imsprog source: package-uses-old-debhelper-compat-version 12 P: imsprog source: trailing-whitespace [debian/changelog:12] As you are upstream, please consider signing your tarballs: X: imsprog source: debian-watch-does-not-check-openpgp-signature [debian/watch] As you are upstream, you could wrap README.md at 80 chars per line :) X: imsprog source: very-long-line-length-in-source-file 577 > 512 [README.md:103] -- tobi On Sat, Apr 27, 2024 at 02:19:07PM +0300, Михаил Медведев wrote: > Package: sponsorship-requests > Severity: normal > > Dear mentors, > > I am looking for a sponsor for my package "imsprog": > > * Package name : imsprog >Version : 1.3.7-1 >Upstream contact : Mikhail medvedeve-ink-rea...@yandex.ru > * URL :https://github.com/bigbigmdm/IMSProg > * License : GPL-2+, GPL-3+, LGPL-2.1 > * Vcs :https://github.com/bigbigmdm/IMSProg/ >Section : devel > > The source builds the following binary packages: > > imsprog - Linux chip programmer for CH341a devices > > To access further information about this package, please visit the following > URL: > > https://mentors.debian.net/package/imsprog/ > > Alternatively, you can download the package with 'dget' using this command: > > dget > -xhttps://mentors.debian.net/debian/pool/main/i/imsprog/imsprog_1.3.7-1.dsc > > Changes since the last upload: > > imsprog (1.3.7-1) unstable; urgency=medium > . >* New upstream release > > Regards, > -- > Mikhail Medvedev
Bug#1070883: src:imsprog: Does not rebuild qt language files
Source: imsprog Severity: important Dear Maintainer, When reviewing #1069942 I saw the the build process does not redbuilt the qt language files. In Debian it is important to rebuild everything from source, that includes those files. (As you are upstream, you could incoorpoate this into your build system and then drop the qm files from the tarball, which will everyone allow to benefit from this)
