Bug#1055540: obs-time-source: FTBFS on several archs: linker input file not found
Some tests were made over Debian, Alpine and Fedora and the issue causing the FTBFS is present only on Debian. The Meson finds the libobs, but fails to build using it. Maybe it can be something related to #998853. The upstream doesn't have a solution because he uses Alpine and the build is perfect there (this bug is unreproducible outside of Debian). My solution (or temporary solution): commonly, plugins for OBS are build with CMake, so I made a patch[1] to use it instead of Meson. This solution works fine and it is based in CMakeLists.txt files provided by Exeldro in several plugins, like obs-move-transition[2]. [1] https://salsa.debian.org/debian/obs-time-source/-/blob/debian/master/debian/patches/010_use-cmake.patch [2] https://salsa.debian.org/debian/obs-move-transition/-/blob/debian/master/CMakeLists.txt Eriberto
Bug#1055588: bookworm-pu: package jdupes/1.21.3-1+deb12u1
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: jdu...@packages.debian.org
Control: affects -1 + src:jdupes
[ Reason ]
jdupes is a fork from fdupes. A bug was introduced by the initial fork some
years ago. The current fdupes on Debian is already fixed. A warning about this
bug was sent by the jdupes upstream (Jody Bruchon) for me via email message.
The help option for jdupes says:
-d --delete: prompt user for files to preserve and delete all
others; [...]
Using the command 'jdupes -d .', a prompt will appear:
Set 1 of 1: keep which files? (1 - 5, [a]ll, [n]one, [l]ink all, [s]ymlink
all):
It is a mistake to set 2-4 because the jdupes considers one file only. Setting
'2-4', the file 2 will be kept and the files 3 and 4 will be deleted. The
sentence 'keep which files? (1 - 5' induces the users to use a range and it is
not valid. Currently, jdupes is not denying this behaviour and it is generating
a data loss.
[ Impact ]
If the update isn't approved, the users can be induced to select a range of
files and it will cause a possible data loss.
[ Tests ]
Some manual tests have been done over jdupes with a patch created by the
upstream. I also tested fdupes to verify if it would be necessary to open a bug
against this package. The current fdupes has no issues.
[ Risks ]
There are no risks, because the patch to fix the issue is trivial, making a
check for data inputs and generating better messages for the users.
[ Checklist ]
[x] *all* changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in stable
[x] the issue is verified as fixed in unstable
[ Changes ]
A patch, created by the upstream, will improve the messages to be shown to
users and will add checks for inputs.
[ Other info ]
No more info.
diff -Nru jdupes-1.21.3/debian/changelog jdupes-1.21.3/debian/changelog
--- jdupes-1.21.3/debian/changelog 2023-02-20 06:51:57.0 -0300
+++ jdupes-1.21.3/debian/changelog 2023-11-08 11:24:57.0 -0300
@@ -1,3 +1,12 @@
+jdupes (1.21.3-1+deb12u1) bookworm; urgency=medium
+
+ * debian/patches/010_fix-data-loss.patch: created to avoid a potential data
+loss caused by a wrong message that induces the users to use a range of
+values with -d option. Currently, the -d option doesn't understand ranges.
+(Closes: #1054237)
+
+ -- Joao Eriberto Mota Filho Wed, 08 Nov 2023 11:24:57
-0300
+
jdupes (1.21.3-1) unstable; urgency=medium
* New upstream version 1.21.3.
diff -Nru jdupes-1.21.3/debian/patches/010_fix-data-loss.patch
jdupes-1.21.3/debian/patches/010_fix-data-loss.patch
--- jdupes-1.21.3/debian/patches/010_fix-data-loss.patch1969-12-31
21:00:00.0 -0300
+++ jdupes-1.21.3/debian/patches/010_fix-data-loss.patch2023-11-08
11:24:57.0 -0300
@@ -0,0 +1,78 @@
+Description: fix potential data loss
+ The help option for jdupes says:
+ -d --delete: prompt user for files to preserve and delete all
+others; [...]
+ .
+ Using the command 'jdupes -d .', a prompt will appear:
+ Set 1 of 1: keep which files? (1 - 5, [a]ll, [n]one, [l]ink
all, [s]ymlink all):
+ It is a mistake to set 2-4 because the jdupes considers one file
+ only. Setting '2-4', the file 2 will be kept and the files 3 and 4
+ will be deleted. The sentence 'keep which files? (1 - 5' induces
+ the users to use a range and it is not valid. Currently, jdupes is
+ not denying this behaviour and it is generating a data loss.
+ .
+ This patch fixes this issue.
+Author: Jody Bruchon
+Origin: https://codeberg.org/jbruchon/jdupes/commit/4888e85
+Bug-Debian: https://bugs.debian.org/1054237
+Last-Update: 2023-10-19
+Index: jdupes/act_deletefiles.c
+===
+--- jdupes.orig/act_deletefiles.c
jdupes/act_deletefiles.c
+@@ -101,8 +101,8 @@ void deletefiles(file_t *files, int prom
+ for (x = 2; x <= counter; x++) preserve[x] = 0;
+ } else do {
+ /* Prompt for files to preserve */
+-printf("Set %u of %u: keep which files? (1 - %u, [a]ll, [n]one",
+- curgroup, groups, counter);
++printf("Specify multiple files with commas like this: 1,2,4,6\n");
++printf("Set %u of %u: keep which files? (1 - %u, [a]ll, [n]one",
curgroup, groups, counter);
+ #ifndef NO_HARDLINKS
+printf(", [l]ink all");
+ #endif
+@@ -139,6 +139,33 @@ void deletefiles(file_t *files, int prom
+
+ for (x = 1; x <= counter; x++) preserve[x] = 0;
+
++ /* Catch attempts to use invalid characters and block them */
++for (char *pscheck = preservestr; *pscheck != '\0'; pscheck++) {
++
Bug#1055540: obs-time-source: FTBFS on several archs: linker input file not found
Package: obs-time-source Version: 0.1-1 Severity: serious Tags: upstream ftbfs Justification: Fails to Build from Source X-Debbugs-Cc: ~krystianch/public-in...@lists.sr.ht The package fails to build from source on several architectures. An example for arm64: cd obj-aarch64-linux-gnu && LC_ALL=C.UTF-8 ninja -j4 -v [1/2] cc -Itime-source.so.p -I. -I.. -I/usr/include/obs -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/aarch64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Wpedantic -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -DHAVE_OBSCONFIG_H -DSIMDE_ENABLE_OPENMP '$<$,$>:-fopenmp-simd>' '$<$,$>:-fopenmp-simd>' -MD -MQ time-source.so.p/time-source.c.o -MF time-source.so.p/time-source.c.o.d -o time-source.so.p/time-source.c.o -c ../time-source.c FAILED: time-source.so.p/time-source.c.o cc -Itime-source.so.p -I. -I.. -I/usr/include/obs -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/aarch64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Wpedantic -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -DHAVE_OBSCONFIG_H -DSIMDE_ENABLE_OPENMP '$<$,$>:-fopenmp-simd>' '$<$,$>:-fopenmp-simd>' -MD -MQ time-source.so.p/time-source.c.o -MF time-source.so.p/time-source.c.o.d -o time-source.so.p/time-source.c.o -c ../time-source.c ../time-source.c: In function ‘time_source_update’: ../time-source.c:95:9: warning: ‘__builtin_strncpy’ specified bound 64 equals destination size [-Wstringop-truncation] 95 | strncpy(context->format, obs_data_get_string(settings, "format"), | ^ cc: warning: $<$,$>:-fopenmp-simd>: linker input file unused because linking not done cc: error: $<$,$>:-fopenmp-simd>: linker input file not found: No such file or directory cc: warning: $<$,$>:-fopenmp-simd>: linker input file unused because linking not done cc: error: $<$,$>:-fopenmp-simd>: linker input file not found: No such file or directory ninja: build stopped: subcommand failed. dh_auto_build: error: cd obj-aarch64-linux-gnu && LC_ALL=C.UTF-8 ninja -j4 -v returned exit code 1 make: *** [debian/rules:13: binary-arch] Error 25 Eriberto -- System Information: Debian Release: 12.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-13-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:pt:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages obs-time-source depends on: ii libc62.36-9+deb12u3 ii libcairo21.16.0-7 ii libglib2.0-0 2.74.6-2 ii libobs0 29.0.2+dfsg-1+b1 ii libpango-1.0-0 1.50.12+ds-1 ii libpangocairo-1.0-0 1.50.12+ds-1 ii obs-studio 29.0.2+dfsg-1+b1 obs-time-source recommends no packages. obs-time-source suggests no packages. -- no debconf information
Bug#1054237: jdupes: data loss behaviour from fdupes
Package: jdupes Version: 1.12-1 Severity: grave Tags: upstream patch Justification: causes non-serious data loss >From the upstream in a private message: jdupes inherited interactive deletion from fdupes and there were zero input safeguards. A user tried to use ranges "2-4" and files 3 and 4 were deleted, not preserved. This is a major data loss concern because the behavior is destructive and contrary to user expectations. In the latest commit I've placed heavy safeguards in the interactive deletion code that should prevent all of the invalid input scenarios I can conceive. The commit 4888e85[1] can and should be immediately applied to ALL versions of jdupes that are being distributed. It should cleanly apply and work without modification to every remotely recent version spanning several years back. [1] https://codeberg.org/jbruchon/jdupes/commit/4888e85
Bug#1053762: winregfs: New upstream place
Package: winregfs Version: 0.7-4 Severity: normal X-Debbugs-Cc: Jody Bruchon Dear maintainer, The winregfs is now at https://codeberg.org/jbruchon/winregfs Regards, Eriberto
Bug#1053141: bookworm-pu: package mrtg/2.17.10-5+deb12u2
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: m...@packages.debian.org Control: affects -1 + src:mrtg [ Reason ] The last SPU was broken by #1041332. This new SPU fixes the issue using a new approach. Now a debconf message is used to warn the user about a change of the configuration place. [ Impact ] The impact is the final user will not know the new place of the configuration file. Consequently, the mrtg will not use the configuration parameters created by the user before the last upgrade (from Bullseye to Bookworm). [ Tests ] Several tests were made to make sure that a warning will be shown when needed. [ Risks ] No risks because this is only a debconf warning for the user. [ Checklist ] [x] *all* changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in (old)stable [x] the issue is verified as fixed in unstable [ Changes ] In 2.17.10-5+deb12u1 the confile was moved from /etc/ to /etc/mrtg/ via a debconf process. This process was cancelled and, now, the user will receive a warning telling that is needed to move this file manually. Consequently, the Debian Policy 10.7.3 is being honored. [ Other info ] No more info. Regards, Eriberto diff -Nru mrtg-2.17.10/debian/changelog mrtg-2.17.10/debian/changelog --- mrtg-2.17.10/debian/changelog 2023-07-10 14:04:14.0 -0300 +++ mrtg-2.17.10/debian/changelog 2023-09-27 22:59:14.0 -0300 @@ -1,3 +1,24 @@ +mrtg (2.17.10-5+deb12u2) bookworm; urgency=medium + + * Changed a debconf template to honor Debian Policy (10.7.3), not +changing the place a conffile, discarding any user changes. +Thanks to Andreas Beckmann . Consequently: + - debian/mrtg.config: changed a comment. + - debian/mrtg.postinst: dropped the first conditional block, +related to moving the /etc/mrtg.cfg to /etc/mrtg/. + - debian/mrtg.templates: updated to show a specific message to +users. + - debian/po/: ran debconf-updatepo to update all templates. + - Closes: #1039103, #1041332 + * debian/po/: + - mrtg.templates: reviewed all messages. Thanks to Justin B Rye + for all help in debian-l10n-english +list and to Jonathan Wiltshire for the suggestion +to ask for help in that list. + - Updated all translations. Thanks to all translators. + + -- Joao Eriberto Mota Filho Wed, 27 Sep 2023 22:59:14 -0300 + mrtg (2.17.10-5+deb12u1) bookworm; urgency=medium * Added a debconf dialog to allow the user to decide if /etc/mrtg.cfg must diff -Nru mrtg-2.17.10/debian/mrtg.config mrtg-2.17.10/debian/mrtg.config --- mrtg-2.17.10/debian/mrtg.config 2023-07-10 14:04:14.0 -0300 +++ mrtg-2.17.10/debian/mrtg.config 2023-09-24 11:26:07.0 -0300 @@ -7,7 +7,7 @@ # Source debconf library. . /usr/share/debconf/confmodule -# Move /etc/mrtg.cfg to /etc/mrtg/mrtg.cfg? +# /etc/mrtg.cfg should be moved to /etc/mrtg/mrtg.cfg if [ -e /etc/mrtg.cfg ] then db_input high mrtg/move_config_file || true diff -Nru mrtg-2.17.10/debian/mrtg.postinst mrtg-2.17.10/debian/mrtg.postinst --- mrtg-2.17.10/debian/mrtg.postinst 2023-07-10 14:04:14.0 -0300 +++ mrtg-2.17.10/debian/mrtg.postinst 2023-09-24 11:26:07.0 -0300 @@ -28,17 +28,6 @@ if [ "$1" = "configure" ] then -# Move /etc/mrtg.cfg to /etc/mrtg/mrtg.cfg? -db_get mrtg/move_config_file || RET="false" -if [ "$RET" = "true" ] -then - if [ -e /etc/mrtg/mrtg.cfg ] - then - mv /etc/mrtg/mrtg.cfg /etc/mrtg/mrtg.cfg.NEW - fi - mv -f /etc/mrtg.cfg /etc/mrtg/ -fi - # Fix owner, group and permissions for /var/www/html/mrtg/? db_get mrtg/fix_permissions || RET="false" if [ "$RET" = "true" ] diff -Nru mrtg-2.17.10/debian/mrtg.templates mrtg-2.17.10/debian/mrtg.templates --- mrtg-2.17.10/debian/mrtg.templates 2023-07-10 14:04:14.0 -0300 +++ mrtg-2.17.10/debian/mrtg.templates 2023-09-24 11:26:07.0 -0300 @@ -1,44 +1,41 @@ Template: mrtg/move_config_file -Type: boolean -Default: true -_Description: Move /etc/mrtg.cfg to /etc/mrtg/mrtg.cfg? - Older versions of the MRTG on Debian had the /etc/mrtg.cfg configuration - file. Currently, this file is located in /etc/mrtg/ directory, but there - is a /etc/mrtg.cfg. +Type: note +_Description: /etc/mrtg.cfg should be moved to /etc/mrtg/mrtg.cfg + Older versions of MRTG on Debian had the configuration file /etc/mrtg.cfg. + The new version reads from /etc/mrtg/mrtg.cfg instead, so MRTG will not + work correctly until you move your configuration across manually. Template: mrtg/fix_permissions Type: boolean Default: true _Description: Fix owner, group and permissions for /var/www/html/mrtg? - By default MRTG writes all graphics in /var/www/html/mrtg/ dire
Bug#1052262: ITP: obs-time-source -- Plugin for OBS Studio that displays current date and time
Package: wnpp Severity: wishlist Owner: Joao Eriberto Mota Filho X-Debbugs-Cc: debian-de...@lists.debian.org, Krystian Chachuła * Package name: obs-time-source Version : 0.1 Upstream Contact: Krystian Chachuła <~krystianch/public-in...@lists.sr.ht> * URL : https://obsproject.com/forum/resources/time-and-date-source.1781/ * License : GPL-3 Programming Lang: C Description : Plugin for OBS Studio that displays current date and time This plugin provides a source that displays current date and time. It is possible to configure the time format, text font, background and text colors and outline in source properties.
Bug#1052196: mrtg: [INTL:fr] French debconf templates translation
Thanks Jean-Pierre! Already sent to Salsa. Regards, Eriberto Em seg., 18 de set. de 2023 às 19:18, Jean-Pierre Giraud escreveu: > > Package: mrtg > Severity: wishlist > Tags: patch l10n > > Hi! > > Please find attached the french debconf templates translation, proofread > by the debian-l10n-french mailing list contributors. > > This file should be put as debian/po/fr.po in your package build tree. > > Sorry to be late! > > Kind Regards > > jipege >
Bug#1052061: mrtg: [INTL:nl] Dutch translation of debconf templates
Thanks Frans! Already sent to Salsa. Regards, Eriberto Em sáb., 16 de set. de 2023 às 16:03, Frans Spiesschaert escreveu: > > > > Package: mrtg > Severity: wishlist > Tags: l10n patch > > > > Dear Maintainer, > > > Please find attached the updated Dutch translation of mrtg debconf > messages. A draft has been posted to the debian-l10n-dutch mailing list > allowing for review. > Please add it to your next package revision. > It should be put as debian/po/nl.po in your package build tree. > > > -- > Kind regards, > Frans Spiesschaert >
Bug#1052155: [l10n:cs] Updated Czech translation of PO debconf template for mrtg
Thanks Michal! Already sent to Salsa. Regards, Eriberto Em seg., 18 de set. de 2023 às 06:33, Michal Šimůnek escreveu: > > Package: mrtg > Version: 2.17.10-10 > Severity: wishlist > Tags: l10n, patch > > In attachment there is updated Czech translation of PO debconf > template (cs.po) for package mrtg, please include it.
Bug#1051483: mrtg: [INTL:de] updated German debconf translation
Thanks Helge! Already sent to Salsa. Regards, Eriberto Em sex., 8 de set. de 2023 às 11:36, Helge Kreutzmann escreveu: > > Package: mrtg > Version: 2.17.10-10 > Severity: wishlist > Tags: patch l10n > > Please find the updated German debconf translation for mrtg > attached. > > Please place this file in debian/po/ as de.po for your next upload. > > If you update your template, please use > 'msgfmt --statistics ' > to check the po-files for fuzzy or untranslated strings. > > If there are such strings, please contact me so I can update the > German translation. > > Greetings > Helge
Bug#1051486: mrtg: [INTL:pt] Portuguese translation - debconf messages
Thanks Américo! Already sent to Salsa. Regards, Eriberto Em sex., 8 de set. de 2023 às 12:30, Américo Monteiro escreveu: > > Package: mrtg > Version: 2.17.10-10 > Tags: l10n, patch > Severity: wishlist > > Updated Portuguese translation for mrtg's debconf messages > Translator: Américo Monteiro > Feel free to use it. > > For translation updates please contact 'Last Translator' > > -- > Melhores cumprimentos/Best regards, > > Américo Monteiro > > -
Bug#1050942: FTBFS: Failed 1/1 test programs. 5/246 subtests failed.
Em qua., 13 de set. de 2023 às 03:12, Simon Ruderich escreveu: > > Hi Eriberto, > > should be fixed in fb2c46d [2]. > > Best, > Simon > > [2]: > https://ruderich.org/simon/gitweb/?p=blhc/blhc.git;a=commitdiff;h=fb2c46d23c6052c714729d70d33d54011374689b Thanks Simon! Have a nice day.
Bug#1043522: blhc: Please allow -std=gnu++20 inside bin/blhc:L1114 regex exception
Hi Simon, > |but the additional "||-std=gnu++20" is found, which causes the > exception regex not to be triggered: could you please change the > mentioned line in bin/blhc to allow for optional arguments between > "/usr/lib/ccache/c++" and "-dM"?| The same case for -std=gnu++11: CPPFLAGS missing (-D_FORTIFY_SOURCE=2): /usr/lib/ccache/c++ -std=gnu++11 -dM -E -c /usr/share/cmake-3.27/Modules/CMakeCXXCompilerABI.cpp -DHAVE_OBSCONFIG_H -DQT_CORE_LIB -DQT_GUI_LIB [...] Regards, Eriberto
Bug#1050942: FTBFS: Failed 1/1 test programs. 5/246 subtests failed.
Package: blhc Version: 0.13-5 Severity: serious Tags: ftbfs upstream Justification: fails to build from source X-Debbugs-Cc: eribe...@debian.org, Simon Ruderich Dear Simon Ruderich, Currently blhc fails to build from source in Debian Sid. This issue was detected in Salsa[1]. [1] https://salsa.debian.org/debian/blhc/-/jobs/4635438 I also tested it in a fresh jail: dh_auto_test /usr/bin/perl Build test --verbose 1 # Failed test './t/logs/arch-avr32 --color (output)' # at t/tests.t line 45. # got: 'Use of uninitialized value $os in pattern match (m//) at ./bin/blhc line 1194. # Use of uninitialized value $cpu in pattern match (m//) at ./bin/blhc line 1198. # Use of uninitialized value $cpu in pattern match (m//) at ./bin/blhc line 1202. # LDFLAGS missing (-Wl,-z,relro): gcc -o test test.o # CFLAGS missing (-fstack-protector-strong): gcc -D_FORTIFY_SOURCE=2 -g -O2 -Wformat -Wformat-security -Werror=format-security -Wall -c test.c # LDFLAGS missing (-Wl,-z,relro): gcc -o test test.o # ' # expected: 'CFLAGS missing (-fstack-protector-strong): gcc -D_FORTIFY_SOURCE=2 -g -O2 -Wformat -Wformat-security -Werror=format-security -Wall -c test.c # ' # Failed test './t/logs/arch-avr32 (output)' # at t/tests.t line 45. # got: 'Use of uninitialized value $os in pattern match (m//) at ./bin/blhc line 1194. # Use of uninitialized value $cpu in pattern match (m//) at ./bin/blhc line 1198. # Use of uninitialized value $cpu in pattern match (m//) at ./bin/blhc line 1202. [...] # checking './t/logs/debian-hardening-wrapper'... # HARDENING WRAPPER: no checks possible, aborting # ' # Failed test './t/logs/arch-i386 ./t/logs/arch-amd64 ./t/logs/arch-avr32 ./t/logs/ignore-flag --ignore-arch-flag i386:-fstack-protector-strong --ignore-arch-flag mipsel:-Werror=format-security (output)' # at t/tests.t line 45. # got: 'Use of uninitialized value $os in pattern match (m//) at ./bin/blhc line 1194. # Use of uninitialized value $cpu in pattern match (m//) at ./bin/blhc line 1198. # Use of uninitialized value $cpu in pattern match (m//) at ./bin/blhc line 1202. [...] # CFLAGS missing (-O2): gcc -g -fstack-protector-strong -Wformat -Wformat-security -Werror=format-security -D_FORTIFY_SOURCE=2 -c test-c.c # ' # Failed test './t/logs/arch-i386 ./t/logs/arch-amd64 ./t/logs/arch-avr32 ./t/logs/ignore-line --ignore-arch-line "i386:gcc .+ -fPIE .+" --ignore-arch-line "mipsel:gcc .+ -Wl,-z,relro -Wl,-z,now .+" (output)' # at t/tests.t line 45. # got: 'Use of uninitialized value $os in pattern match (m//) at ./bin/blhc line 1194. # Use of uninitialized value $cpu in pattern match (m//) at ./bin/blhc line 1198. # Use of uninitialized value $cpu in pattern match (m//) at ./bin/blhc line 1202. [...] # Looks like you failed 5 tests of 246. t/tests.t .. 1..246 [...] not ok 14 - ./t/logs/arch-avr32 --color (output) [...] not ok 164 - ./t/logs/arch-avr32 (output) [...] not ok 242 - ./t/logs/bad-ldflags ./t/logs/empty ./t/logs/arch-avr32 ./t/logs/debian-hardening-wrapper (output) [...] not ok 244 - ./t/logs/arch-i386 ./t/logs/arch-amd64 ./t/logs/arch-avr32 ./t/logs/ignore-flag --ignore-arch-flag i386:-fstack-protector-strong --ignore-arch-flag mipsel:-Werror=format-security (output) [...] not ok 246 - ./t/logs/arch-i386 ./t/logs/arch-amd64 ./t/logs/arch-avr32 ./t/logs/ignore-line --ignore-arch-line "i386:gcc .+ -fPIE .+" --ignore-arch-line "mipsel:gcc .+ -Wl,-z,relro -Wl,-z,now .+" (output) Dubious, test returned 5 (wstat 1280, 0x500) Failed 5/246 subtests Test Summary Report --- t/tests.t (Wstat: 1280 (exited 5) Tests: 246 Failed: 5) Failed tests: 14, 164, 242, 244, 246 Non-zero exit status: 5 Files=1, Tests=246, 3 wallclock secs ( 0.02 usr 0.00 sys + 2.46 cusr 0.37 csys = 2.85 CPU) Result: FAIL Failed 1/1 test programs. 5/246 subtests failed. Regards, Eriberto -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-11-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8), LANGUAGE=C.UTF-8 Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect Versions of packages blhc depends on: ii libdpkg-perl 1.22.0 blhc recommends no packages. blhc suggests no packages. -- debconf-show failed
Bug#1039103: mrtg.cfg not moved to new location in /etc/mrtg/ when upgrading from bullseye to bookworm
Dear Konrad, Due #1041332, I reopened this bug some days ago. The Debian Policy[1], in its clause 10.7.3, doesn't allow the install system to modify (moving) configuration files. IMO, the best way for MRTG is to show a message to users asking for a manual action. I will do an upload to provide it soon (tomorrow?). This upload will close this bug. Sorry for this solution and feel free to reopen if needed (but if this bug be reopened, I will set a tag wontfix for it). Thanks a lot for your attention. [1] https://www.debian.org/doc/debian-policy/ch-files.html#behavior Regards, Eriberto
Bug#1043809: br.ispell: Fails to build source after successful build
Em ter., 15 de ago. de 2023 às 09:09, Agustin Martin escreveu: > > El dom, 13 ago 2023 a las 16:12, Eriberto Mota () > escribió: > > > > Control: tags 1043809 patch > > > > On Sun, 13 Aug 2023 15:17:55 +0200 > > Lucas Nussbaum wrote: > > > > > > This package fails to build a source package after a successful build > > > (dpkg-buildpackage ; dpkg-buildpackage -S). > > > > Dear maintainer, > > > > The attached patch fixes this issue. > > Thanks for the patch, Eriberto. > > There is another issue I would like to handle with this upload, so I > will wait some days before actually uploading. > > Old upstream location for this package > (https://www.ime.usp.br/~ueda/br.ispell/) seems gone, as well as > download location (http://www.ime.usp.br/~ueda/br.ispell/beta.html). > https://www.ime.usp.br seems to have changed their www page and old > personal stuff from Ricardo Ueda is no longer accesible. If I cannot > find a new project location I will change watch file by your "No-Site" > watch snippet. Good! Thanks for using "No-Site". Regards, Eriberto
Bug#1041332: mrtg: modifies conffiles (policy 10.7.3): /etc/mrtg/mrtg.cfg
> during a test with piuparts I noticed your package modifies conffiles. > This is forbidden by the policy, see > https://www.debian.org/doc/debian-policy/ch-files.html#configuration-files Hi Andreas, Thanks for your time and help. I decided to change the current action from the debconf by a warning for the final user. I will make it soon. Regards, Eriberto
Bug#1043142: git-buildpackage: import-dscs importing upstream branches out-of-order
Package: git-buildpackage Version: 0.9.22 Severity: important Tags: sid trixie bookworm bullseye X-Debbugs-Cc: eribe...@debian.org Dear Maintainer, When using: gbp import-dscs --debsnap acr or debsnap acr; gbp import-dscs source-acr/*.dsc the result is the upstream branches out-of-order. See the following command after an import (important lines only): $ git log commit 17d263cee50d3f4b8ba881ca7216194672e7fdfb (HEAD -> debian/master, tag: debian/1.9.4-2) Author: Thiago Marques Siqueira Date: Sun Jul 9 17:11:06 2023 +0100 [...] commit 8b622b80fb70e9cbdbd071f1d7f714f3f9629e57 (tag: debian/1.9.4-1) Merge: 4adf342 ce6c977 Author: Ruben Pollan Date: Wed Nov 11 13:04:48 2020 +0100 [...] commit 4adf342f0ecaf0853e2a67ce4ecd3e1acc4b (tag: debian/1.9.2-1) Merge: 5c67e33 e093e17 Author: Ruben Pollan Date: Mon May 11 17:50:30 2020 +0200 [...] commit ce6c977714bed2df56c2b5196c63be93163b9c76 (tag: upstream/1.9.4, upstream) Author: Joao Eriberto Mota Filho Date: Sun Aug 6 12:49:57 2023 -0300 [...] commit 5c67e33227e93c952beb794f187f0ea939bf6da3 (tag: debian/1.7.2-1) Merge: bf4799a 8fb8e10 Author: Ruben Pollan Date: Thu Feb 21 13:36:37 2019 +0100 [...] commit e093e17ad41e54455a91294fe7f91ea02a9d3b32 (tag: upstream/1.9.2) Author: Joao Eriberto Mota Filho Date: Sun Aug 6 12:49:57 2023 -0300 [...] commit bf4799a838a39ebfc55ab0a5927d8199918ed5ee (tag: debian/1.7.0-1) Merge: f75f0d0 4ed59ec Author: Ruben Pollan Date: Tue Oct 2 12:40:27 2018 -0500 [...] commit 8fb8e104db07fac42c81a796c50cf47febdb130b (tag: upstream/1.7.2) Author: Joao Eriberto Mota Filho Date: Sun Aug 6 12:49:56 2023 -0300 [...] commit f75f0d08a3b8e81914fbe69450e1215be93231e1 (tag: debian/1.6.2-1) Merge: 8765fb7 b83b9fb Author: Ruben Pollan Date: Fri May 18 20:20:29 2018 +0200 [...] commit 4ed59ece03f46f22e525615aa3283ce8e4344043 (tag: upstream/1.7.0) Author: Joao Eriberto Mota Filho Date: Sun Aug 6 12:49:56 2023 -0300 [...] commit 8765fb751b746fb7e2aa320821972735869ca8d7 (tag: debian/1.6.1-1) Merge: 281c76f 3916c6a Author: Ruben Pollan Date: Mon Apr 16 09:54:12 2018 +0200 [...] I consider this issue 'important' because several people use gbp import-dscs to create a repository for a package, keeping all previous history. Importing each package by hand using import-dsc (not dscs) will work fine. Regards, Eriberto -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-10-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8), LANGUAGE=C.UTF-8 Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect Versions of packages git-buildpackage depends on: ii devscripts 2.23.5 ii git1:2.40.1-1 ii man-db 2.11.2-3 ii python33.11.4-5+b1 ii python3-dateutil 2.8.2-2 ii python3-pkg-resources 68.0.0-1 ii python3-yaml 6.0.1-1 ii sensible-utils 0.0.20 Versions of packages git-buildpackage recommends: ii cowbuilder0.89 ii pbuilder 0.231 ii pristine-tar 1.50 ii python3-requests 2.31.0+dfsg-1 Versions of packages git-buildpackage suggests: pn python3-notify2 ii sudo 1.9.14p2-1 ii unzip6.0-28 -- Configuration Files: /etc/git-buildpackage/gbp.conf changed: [DEFAULT] debian-branch = debian/master pristine-tar = True [buildpackage] [import-orig] [import-dsc] [dch] [pq] [clone] [pull] [create-remote-repo] [remote-config pkg-libvirt] remote-url-pattern = ssh://git.debian.org/git/pkg-libvirt/%(pkg)s template-dir = /srv/alioth.debian.org/chroot/home/groups/pkg-libvirt/git-template
Bug#1042409: python3-distorm3,libdistorm3-3: undeclared file conflict /usr/lib/x86_64-linux-gnu/libdistorm3.so.3
Hi Helmut,
> Package: python3-distorm3,libdistorm3-3
> Version: 3.5.2b-1
> Severity: serious
>
> Hi,
>
> both libdistorm3-3 and python3-distorm3 contain
> /usr/lib/x86_64-linux-gnu/libdistorm3.so.3. When coinstalling these
> packages, an unpack error results. I suspect that the python one
> shouldn't contain the shared library. Do you concur?
You are right, but I am not able to reproduce this issue in my machine
using debuild / dpkg-buildpackage -A / dpkg-buildpackage -B.
I think this issue was caused by a dh_link in debian/rules. I will try
a new upload with the following change:
-override_dh_link:
+override_dh_link-arch:
dh_link usr/lib/${DEB_TARGET_MULTIARCH}/libdistorm3.so.$(LIB_R_VERSION)
\
usr/lib/${DEB_TARGET_MULTIARCH}/libdistorm3.so.3
If this change fixes the issue, I will close this bug manually.
Cheers,
Eriberto
Bug#1039103: mrtg.cfg not moved to new location in /etc/mrtg/ when upgrading from bullseye to bookworm
Control: reopen 1039103 Reopening this bug due issues from #1040860. Regards, Eriberto
Bug#1041332: mrtg: modifies conffiles (policy 10.7.3): /etc/mrtg/mrtg.cfg
Hi Andreas, On Mon, 17 Jul 2023 17:22:21 +0200 Andreas Beckmann wrote: > Package: mrtg > Version: 2.17.10-5+deb12u1 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > Control: block 1040860 with -1 > > Hi, > > during a test with piuparts I noticed your package modifies conffiles. > This is forbidden by the policy, see > https://www.debian.org/doc/debian-policy/ch-files.html#configuration-files [...] > I'd suggest to withdraw the 2.17.10-5+deb12u1 bookworm-pu update and > revisit that for the next point release (there is no time left to fix > this properly before saturday). I have some idea how this could be > solved better, but I need to try that first. Thanks a lot for spotting this issue. My current (emergency) plans: 1. Reopening the bug #1039103 and make it as wontfix, quoting #1040860. 2. Reverting the changes in Sid. 3. Asking to Release Team how to proceed (is possible to drop the PU or need I to send a new PU as a revision to revert the changes?). 4. Making a new PU if needed. What you think about this? Regards, Eriberto
Bug#1040860: bookworm-pu: package mrtg/2.17.10-5+deb12u1
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: m...@packages.debian.org Control: affects -1 + src:mrtg [ Reason ] Older versions of the MRTG on Debian had the /etc/mrtg.cfg configuration file. Currently, this file is located in /etc/mrtg/ directory. This PU introduces changes from Sid (revision 2.17.10-6) to ask to user if the configuration file must be moved to /etc/mrtg/, if it exists in /etc/. Some updated and new translations for the debconf template are being sent with this PU (from revisions 2.17.10-7 and 2.17.10-8). This PU closes #1039103. [ Impact ] If the update isn't approved, a user migrating MRTG from an older version will need to handle manually the configuration file, moving it to the right current place. [ Tests ] Some manual tests over unstable and stable environments were done to check if the purposed action is occurring. [ Risks ] No risks because this is a trivial change. [ Checklist ] [x] *all* changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in stable [x] the issue is verified as fixed in unstable [ Changes ] A new action, via debconf, was implemented. If the /etc/mrtg.cfg file exists when the system is being updated, the user will be asked about moving the file to /etc/mrtg/ directory. If yes, the system will rename a possible new conf file in /etc/mrtg/ and move /etc/mrtg.cfg to /etc/mrtg/. [ Other info ] No more info. diff -Nru mrtg-2.17.10/debian/changelog mrtg-2.17.10/debian/changelog --- mrtg-2.17.10/debian/changelog 2023-04-19 00:10:02.0 -0300 +++ mrtg-2.17.10/debian/changelog 2023-07-10 14:04:14.0 -0300 @@ -1,3 +1,17 @@ +mrtg (2.17.10-5+deb12u1) bookworm; urgency=medium + + * Added a debconf dialog to allow the user to decide if /etc/mrtg.cfg must +be moved to /etc/mrtg/mrtg.cfg. Consequently: + - Added a new debconf template (files debian/mrtg.config and +debian/mrtg.templates). + - Updated debian/mrtg.postinst. + - Updated translations in debian/po/ (es.po, fr.po, nl.po, pt.po, +pt_BR.po, ro.po and sv.po). + - Added new translations to debian/po/ (gl.po and vi_VN.po). + - Closes: #1039103 + + -- Joao Eriberto Mota Filho Mon, 10 Jul 2023 14:04:14 -0300 + mrtg (2.17.10-5) unstable; urgency=medium * debian/control: bumped Standards-Version to 4.6.2. diff -Nru mrtg-2.17.10/debian/mrtg.config mrtg-2.17.10/debian/mrtg.config --- mrtg-2.17.10/debian/mrtg.config 2023-04-19 00:09:56.0 -0300 +++ mrtg-2.17.10/debian/mrtg.config 2023-07-10 14:04:14.0 -0300 @@ -1,12 +1,21 @@ #!/bin/sh -# 2021 - Eriberto +# 2021-2023 - Eriberto set -e # Source debconf library. . /usr/share/debconf/confmodule +# Move /etc/mrtg.cfg to /etc/mrtg/mrtg.cfg? +if [ -e /etc/mrtg.cfg ] +then +db_input high mrtg/move_config_file || true +db_go || true +else +db_set mrtg/move_config_file false +fi + # Fix permissions for /var/www/html/mrtg/? if [ -d /var/www/html/mrtg ] then diff -Nru mrtg-2.17.10/debian/mrtg.postinst mrtg-2.17.10/debian/mrtg.postinst --- mrtg-2.17.10/debian/mrtg.postinst 2023-04-19 00:09:56.0 -0300 +++ mrtg-2.17.10/debian/mrtg.postinst 2023-07-10 14:04:14.0 -0300 @@ -28,6 +28,17 @@ if [ "$1" = "configure" ] then +# Move /etc/mrtg.cfg to /etc/mrtg/mrtg.cfg? +db_get mrtg/move_config_file || RET="false" +if [ "$RET" = "true" ] +then + if [ -e /etc/mrtg/mrtg.cfg ] + then + mv /etc/mrtg/mrtg.cfg /etc/mrtg/mrtg.cfg.NEW + fi + mv -f /etc/mrtg.cfg /etc/mrtg/ +fi + # Fix owner, group and permissions for /var/www/html/mrtg/? db_get mrtg/fix_permissions || RET="false" if [ "$RET" = "true" ] diff -Nru mrtg-2.17.10/debian/mrtg.templates mrtg-2.17.10/debian/mrtg.templates --- mrtg-2.17.10/debian/mrtg.templates 2023-04-19 00:09:56.0 -0300 +++ mrtg-2.17.10/debian/mrtg.templates 2023-07-10 14:04:14.0 -0300 @@ -1,3 +1,11 @@ +Template: mrtg/move_config_file +Type: boolean +Default: true +_Description: Move /etc/mrtg.cfg to /etc/mrtg/mrtg.cfg? + Older versions of the MRTG on Debian had the /etc/mrtg.cfg configuration + file. Currently, this file is located in /etc/mrtg/ directory, but there + is a /etc/mrtg.cfg. + Template: mrtg/fix_permissions Type: boolean Default: true diff -Nru mrtg-2.17.10/debian/po/cs.po mrtg-2.17.10/debian/po/cs.po --- mrtg-2.17.10/debian/po/cs.po2023-04-19 00:09:56.0 -0300 +++ mrtg-2.17.10/debian/po/cs.po2023-07-10 14:04:14.0 -0300 @@ -7,7 +7,7 @@ msgstr "" "Project-Id-Version: mrtg 2.17.8+git20211022.f52e91e-1\n" "Report-Msgid-Bugs-To: m...@packages.debian.org\n" -"POT-Creation-Date: 2022-01-08 15:02-0300\n" +"
Bug#1040550: RM: obs-3d-effect/experimental -- NVIU; Package not removed after upload to unstable
Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove Dear FTP Masters, The revision 0.0.2-2 was uploaded to unstable in 2023-06-11 and it migrated to testing in 2023-06-21. However, the revision 0.0.2-1 remains in experimental. Regards, Eriberto
Bug#1040501: mrtg: [INTL:nl] Dutch translation of debconf templates
Em qui., 6 de jul. de 2023 às 17:24, Frans Spiesschaert escreveu: > > > > Package: mrtg > Severity: wishlist > Tags: l10n patch > > > > Dear Maintainer, > > > Please find attached the updated Dutch translation of mrtg debconf > messages. A draft has been posted to the debian-l10n-dutch mailing list > allowing for review. > Please add it to your next package revision. > It should be put as debian/po/nl.po in your package build tree. > > > -- > Kind regards, > Frans Spiesschaert Thanks Frans. I just sent it to Salsa. Regards, Eriberto
Bug#1040510: mrtg: [INTL:fr] French templates translation
Em qui., 6 de jul. de 2023 às 19:57, Jean-Pierre Giraud escreveu: > > Package: mrtg > Severity: wishlist > Tags: patch l10n > > Hi! > > Please find attached the french templates translation updated, > proofread by the debian-l10n-french mailing list contributors. > > This file should be put as debian/po/fr.po in your package build tree. > > Kind Regards > > Jean-Pierre Giraud Thanks Jean-Pierre. I just sent this translation to Salsa. Regards, Eriberto
Bug#1040493: ITP: obs-ashmanix-blur-filter -- plugin for OBS Studio to set a blur filter on a source
Package: wnpp Severity: wishlist Owner: Joao Eriberto Mota Filho X-Debbugs-Cc: debian-de...@lists.debian.org, Ashmanix * Package name: obs-ashmanix-blur-filter Version : 0.0.2 Upstream Contact: Ashmanix * URL : https://obsproject.com/forum/resources/ashmanix-blur-filter.1742/ * License : GPL-2+ Programming Lang: C++ Description : plugin for OBS Studio to set a blur filter on a source This plugin lets to set a simple blur filter on any OBS source, such images, videos, texts, scenes, webcam, etc. To use it, just right click on an image or video source and select Filters.
Bug#1040367: mrtg: [INTL:pt] Portuguese translation - debconf messages
Em ter., 4 de jul. de 2023 às 19:15, Américo Monteiro escreveu: > > Updated Portuguese translation for mrtg's debconf messages > Translator: Américo Monteiro > Feel free to use it. I just sent this translation to Salsa. Obrigado!!! Eriberto
Bug#1038752: libjodycode2: A shared library package cannot be a transitional package on a different soversion
Em quinta-feira, 22 de junho de 2023, Adrian Bunk escreveu: > On Tue, Jun 20, 2023 at 11:12:58PM -0300, Eriberto wrote: > > Hi Adrian, > > Hi Eriberto, > > > Em ter., 20 de jun. de 2023 às 18:18, Adrian Bunk > escreveu: > >... > > > A shared library package libjodycode2 provides the shared library > > > libjodycode.so.2, and not providing it breaks reverse dependencies. > > > > > > libjodycode2 must either provide libjodycode.so.2 by shipping it > > > or depending on a package that does ship it, or libjodycode2 must > > > be dropped. Anything other than dropping it would be highly unusual. > > > > > > In at the moment, only jdupes depends of the libjodycode"X" on Debian, > > so I think that libjodycode2 (transitional) must be dropped, right? > > (jdupes 1.24 was replaced by jdupes 1.25, that depends of the > > libjodycode3). > > A transitional libjodycode2 shouldn't ever have existed since it causes > breakage of reverse dependencies (in this case only jdupes). > > Never having libjodycode2 would also automatically make it an > auto- transition at [1] showing what packages need rebuilding. Thanks for the clarification. Your words are very useful for my to learn a bit more about libs. > > > A transitional package libjodycode2-dev would be possible, > > > but there is no real benefit for a just created package. > > > > > > The -dev package should be named libjodycode-dev, > > > which is a stable name. > > > > What is the right way to make this? Renaming to libjodycode-dev, > > dropping libjodycode3-dev and sending again to NEW? Should I use > > Breaks and Replaces to make a reference to libjodycode3-dev? > > Sounds like a good plan to me. Thanks! Package already in NEW. Eriberto > > Thanks for your attention. > > > > Cheers, > > > > Eriberto > > cu > Adrian > > [1] https://release.debian.org/transitions/ >
Bug#1038752: libjodycode2: A shared library package cannot be a transitional package on a different soversion
Em qua., 21 de jun. de 2023 às 23:58, Jody Bruchon escreveu: > > Thanks for all that information! While I'm here, I should also point out > that another Debian package will eventually have to adopt libjodycode as > well: winregfs [1]. Fortunately it doesn't use any of the APIs that > changed between libjodycode 2 and 3 so changing what it needs to link to > is as simple as recompiling and pointing it to the correct libjodycode.h > header. > > [1] https://packages.debian.org/sid/utils/winregfs Thanks again Jody. The winregfs is maintained by my close friend Giovani. I am ending the revision libjodycode_3.0.1-3. > On 2023-06-21 10:14 PM, Eriberto wrote: > > Hi Jody! > > > > Em qua., 21 de jun. de 2023 às 21:09, Tritech - Jody > > escreveu: > >> Hi! I'm upstream. Would it be helpful if I provided a way to build a > >> compatibility shim libjodycode.so.2 with the old API 2 interfaces that > >> translates and links to the API 3 version? I'd be happy to provide that if > >> desired. > > I think this is not needed because all these new packages don't > > arrived to Debian Testing yet. The jdupes 1.25.0 already killed the > > 1.24.0, so libjodycode2 is no longer useful for Debian. I will follow > > the changes purposed by Adrian. I will start changing the packaging of > > the lib. Furthermore, I was wrong when making a -dev package with > > soname number attached. It was a mistake. The changes will make the > > lib arrives to NEW queue again. > > > > Thanks a lot Adrian and Jody. > > > > Cheers, > > > > Eriberto >
Bug#1038752: libjodycode2: A shared library package cannot be a transitional package on a different soversion
Hi Jody! Em qua., 21 de jun. de 2023 às 21:09, Tritech - Jody escreveu: > > Hi! I'm upstream. Would it be helpful if I provided a way to build a > compatibility shim libjodycode.so.2 with the old API 2 interfaces that > translates and links to the API 3 version? I'd be happy to provide that if > desired. I think this is not needed because all these new packages don't arrived to Debian Testing yet. The jdupes 1.25.0 already killed the 1.24.0, so libjodycode2 is no longer useful for Debian. I will follow the changes purposed by Adrian. I will start changing the packaging of the lib. Furthermore, I was wrong when making a -dev package with soname number attached. It was a mistake. The changes will make the lib arrives to NEW queue again. Thanks a lot Adrian and Jody. Cheers, Eriberto
Bug#1038752: libjodycode2: A shared library package cannot be a transitional package on a different soversion
Hi Adrian, Initially, thanks for your help. Em ter., 20 de jun. de 2023 às 18:18, Adrian Bunk escreveu: > > Package: libjodycode2 > Version: 3.0.1-1 > Severity: serious > Tags: ftbfs > Control: affects -1 src:phcpack jdupes > > https://buildd.debian.org/status/fetch.php?pkg=phcpack=amd64=2.4.86%2Bdfsg-5=1687282110=0 > > ... > jdupes -l src/Python/PHCpy3/doc/build/html/_images/math > jdupes: error while loading shared libraries: libjodycode.so.2: cannot open > shared object file: No such file or directory > make[1]: *** [debian/rules:44: override_dh_auto_build-arch] Error 127 I packaged this lib after the freeze and I sent it to NEW queue in June, 13. The package was approved in June, 15. However, the upstream dropped the libjodycode2 in June, 16, releasing libjodycode3. The jdupes in stable don't depend on a lib. jdupes 1.24 depends on the libjodycode2 and the new jdupes 1.25 depends on the libjodycode3. I uploaded libjodycode3 to unstable this morning, but jdupes was 1.24, depending on the libjdupes2. Some hours after this, I uploaded jdupes 1.25. > A shared library package libjodycode2 provides the shared library > libjodycode.so.2, and not providing it breaks reverse dependencies. > > libjodycode2 must either provide libjodycode.so.2 by shipping it > or depending on a package that does ship it, or libjodycode2 must > be dropped. Anything other than dropping it would be highly unusual. In at the moment, only jdupes depends of the libjodycode"X" on Debian, so I think that libjodycode2 (transitional) must be dropped, right? (jdupes 1.24 was replaced by jdupes 1.25, that depends of the libjodycode3). > A transitional package libjodycode2-dev would be possible, > but there is no real benefit for a just created package. > > The -dev package should be named libjodycode-dev, > which is a stable name. What is the right way to make this? Renaming to libjodycode-dev, dropping libjodycode3-dev and sending again to NEW? Should I use Breaks and Replaces to make a reference to libjodycode3-dev? Thanks for your attention. Cheers, Eriberto
Bug#1038417: jdupes: Broken hard linking
Package: jdupes Version: 1.24.0-1 Severity: important Tags: upstream patch X-Debbugs-Cc: Jody Bruchon The upstream, Jody Bruchon, notified me about hard linking is not working in 1.24.0 version. The solution for this issue is to use the following commits from the official repository[1]: https://github.com/jbruchon/jdupes/commit/9f66732 https://github.com/jbruchon/jdupes/commit/70dc66d https://github.com/jbruchon/jdupes/commit/62f365d [1] https://github.com/jbruchon/jdupes Thanks Jody! Eriberto
Bug#1037451: ITP: libjodycode -- shared lib for programs written by Jody Bruchon
Package: wnpp Severity: wishlist Owner: Joao Eriberto Mota Filho X-Debbugs-Cc: debian-de...@lists.debian.org, Jody Bruchon * Package name: libjodycode Version : 2.0.1 Upstream Contact: Jody Bruchon * URL : https://github.com/jbruchon/libjodycode * License : Expat Programming Lang: C Description : shared lib for programs written by Jody Bruchon libjodycode2 is a software code library containing code shared among several of the programs written by Jody Bruchon such as imagepile, jdupes, winregfs, and zeromerge. These shared pieces of code were copied between each program as they were updated. As the number of programs increased and keeping these pieces of code synced became more annoying, the decision was made to combine all of them into a single reusable shared library.
Bug#1037003: unblock: forensics-extra/2.45
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: forensics-ex...@packages.debian.org Control: affects -1 + src:forensics-extra Please unblock package forensics-extra [ Reason ] forensics-extra (like forensics-all) is a metapackage to install several tools to aid in forensics activities. Due an issue in reaver (see #1036809), forensics-extra is marked for autoremoval. The solution was move reaver from Depends field to Recommends field in forensics-extra. Consequently, the files list-of-packages-extra, debian/control and debian/forensics-extra.README.Debian were updated. This metapackage is native and uses some scripts to generate a final debian/control and a debian/forensics-extra.README.Debian. The list-of-packages-extra file describes which packages will be put in debian/control and where they will be put (Depends, Recommends, Suggests). The debian/forensics-extra.README.Debian is a list of all packages on forensics-extra and their short descriptions. [ Impact ] The impact for the user if the unblock isn't granted is that package forensics-extra will not available in next stable release (Bookworm). [ Tests ] Considering that this is a metapackage, no great tests are needed. The package has a CI test and the Salsa CI is activated too. The package pass in CI, piuparts, etc. There is a script in forensics-extra called find-deps.sh (available in a branch in Salsa, not merged yet, but functional). This script ensures that no other package is affected by reaver in forensics-extra. [ Risks ] No risks. This is a trivial change in a metapackage. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in testing [ Other info ] No more info needed. unblock forensics-extra/2.45 diff -Nru forensics-extra-2.44/debian/changelog forensics-extra-2.45/debian/changelog --- forensics-extra-2.44/debian/changelog 2023-04-17 20:59:36.0 -0300 +++ forensics-extra-2.45/debian/changelog 2023-05-31 17:01:50.0 -0300 @@ -1,3 +1,12 @@ +forensics-extra (2.45) unstable; urgency=medium + + * list-of-packages-extra: moved reaver from FED to FER. See #1036809 and +#1036591. + * debian/control: updated. + * debian/forensics-extra.README.Debian: updated. + + -- Joao Eriberto Mota Filho Wed, 31 May 2023 17:01:50 -0300 + forensics-extra (2.44) unstable; urgency=medium * list-of-packages-extra: changed bzip3 from FED to FER. See #1034177. diff -Nru forensics-extra-2.44/debian/control forensics-extra-2.45/debian/control --- forensics-extra-2.44/debian/control 2023-04-17 20:59:36.0 -0300 +++ forensics-extra-2.45/debian/control 2023-05-31 17:01:50.0 -0300 @@ -31,6 +31,7 @@ exfatprogs, guestfs-tools, pngcheck, +reaver, ree, tcpreplay Depends: ancient, @@ -125,7 +126,6 @@ psrip, rarcrack, readstat, - reaver, rzip, scrot, secure-delete, @@ -225,7 +225,7 @@ ncompress, netcat-openbsd, netdiscover, ngrep, nomarch, nstreams, ntfs-3g, nwipe, openpace, p7zip-full, packit, parted, pcapfix, pcaputils, pdfcrack, pecomato, pev, plzip, png-definitive-guide, - poppler-utils, psrip, rarcrack, readstat, reaver, rzip, scrot, + poppler-utils, psrip, rarcrack, readstat, rzip, scrot, secure-delete, sipcrack, sipgrep, sipvicious, sngrep, squashfs-tools-ng, ssh-audit, sslscan, stepic, sxiv, tcpdump, tcpflow, tcptrace, tcpxtract, testdisk, tshark, ugrep, unrar-free, diff -Nru forensics-extra-2.44/debian/forensics-extra.README.Debian forensics-extra-2.45/debian/forensics-extra.README.Debian --- forensics-extra-2.44/debian/forensics-extra.README.Debian 2023-04-17 20:59:36.0 -0300 +++ forensics-extra-2.45/debian/forensics-extra.README.Debian 2023-05-31 17:01:50.0 -0300 @@ -99,7 +99,6 @@ psrip - Extract images from PostScript files rarcrack - Password cracker for rar archives readstat - read/write data sets from SAS, Stata, and SPSS -reaver - brute force attack tool against Wifi Protected Setup PIN number rzip - compression program for large files scrot - command line screen capture utility secure-delete - tools to wipe files, free disk space, swap and memory @@ -173,8 +172,9 @@ exfatprogs - exFAT file system utilities guestfs-tools - guest disk image management system - tools pngcheck - print info and check PNG, JNG and MNG files +reaver - brute force attack tool against Wifi Protected Setup PIN number ree - extract ROM extensions tcpreplay - Tool to replay saved tcpdump files at arbitrary speeds - -- Joao Eriberto Mota Filho Mon, 17 Apr 2023 21:03:07 -0300 + -- Joao Eriberto Mota Filho Wed, 31 May 2023 17:06:35 -0300 diff -Nru forensics-extra-2.44/list-of-packages-extra forensics-extra-2.45/list-of-packages-extra
Bug#1037002: unblock: forensics-all/3.45
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: forensics-...@packages.debian.org
Control: affects -1 + src:forensics-all
Please unblock package forensics-all.
[ Reason ]
forensics-all (like forensics-extra) is a metapackage to install several
tools to aid in forensics activities. Due an issue in reaver (see #1036809),
forensics-all is marked for autoremoval. The solution was move wifite, that
depends of the reaver, from Depends field to Recommends field in forensics-all.
Consequently, the files list-of-packages, debian/control and
debian/forensics-all.README.Debian were updated.
This metapackage is native and uses some scripts to generate a final
debian/control and a debian/forensics-all.README.Debian. The list-of-packages
file describes which packages will be put in debian/control and where they
will be put (Depends, Recommends, Suggests). The
debian/forensics-all.README.Debian is a list of all packages on forensics-all
and their short descriptions.
[ Impact ]
The impact for the user if the unblock isn't granted is that package
forensics-all will not available in next stable release (Bookworm).
[ Tests ]
Considering that this is a metapackage, no great tests are needed. The package
has a CI test and the Salsa CI is activated too. The package pass in CI,
piuparts, etc.
There is a script in forensics-all called find-deps.sh. This script ensures
that only wifite depends of the reaver in forensics-all.
[ Risks ]
No risks. This is a trivial change in a metapackage.
[ Checklist ]
[x] all changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in testing
[ Other info ]
No more info needed.
unblock forensics-all/3.45
diff -Nru forensics-all-3.44/debian/changelog
forensics-all-3.45/debian/changelog
--- forensics-all-3.44/debian/changelog 2023-03-16 08:04:52.0 -0300
+++ forensics-all-3.45/debian/changelog 2023-05-31 16:38:48.0 -0300
@@ -1,3 +1,11 @@
+forensics-all (3.45) unstable; urgency=medium
+
+ * list-of-packages: moved wifite from FD to FR. See #1036809 and #1036591.
+ * debian/control: updated.
+ * debian/forensics-all.README.Debian: updated.
+
+ -- Joao Eriberto Mota Filho Wed, 31 May 2023 16:38:48
-0300
+
forensics-all (3.44) unstable; urgency=medium
* list-of-packages:
diff -Nru forensics-all-3.44/debian/control forensics-all-3.45/debian/control
--- forensics-all-3.44/debian/control 2023-03-16 08:04:52.0 -0300
+++ forensics-all-3.45/debian/control 2023-05-31 16:38:48.0 -0300
@@ -38,6 +38,7 @@
plaso,
radare2,
wapiti,
+wifite,
xmount,
yara
Depends: acct,
@@ -145,7 +146,6 @@
unhide.rb,
vinetto,
wfuzz,
- wifite,
winregfs,
wipe,
${misc:Depends}
@@ -176,7 +176,7 @@
scrounge-ntfs, shed, sleuthkit, smbmap, snowdrop, ssdeep, ssldump,
statsprocessor, stegcracker, steghide, stegsnow, sucrack,
tableau-parm, tcpick, testssl.sh, time-decode, undbx, unhide,
- unhide.rb, vinetto, wfuzz, wifite, winregfs, wipe
+ unhide.rb, vinetto, wfuzz, winregfs, wipe
.
This metapackage is useful for pentesters, ethical hackers and forensics
experts.
diff -Nru forensics-all-3.44/debian/forensics-all.README.Debian
forensics-all-3.45/debian/forensics-all.README.Debian
--- forensics-all-3.44/debian/forensics-all.README.Debian 2023-03-16
08:04:52.0 -0300
+++ forensics-all-3.45/debian/forensics-all.README.Debian 2023-05-31
16:38:48.0 -0300
@@ -110,7 +110,6 @@
unhide.rb - Forensics tool to find processes hidden by rootkits
vinetto - forensics tool to examine Thumbs.db files
wfuzz - Web application bruteforcer
-wifite - Python script to automate wireless auditing using aircrack-ng tools
winregfs - Windows registry FUSE filesystem
wipe - secure file deletion
@@ -128,8 +127,9 @@
plaso - super timeline all the things -- metapackage
radare2 - free and advanced command line hexadecimal editor
wapiti - web application vulnerability scanner
+wifite - Python script to automate wireless auditing using aircrack-ng tools
xmount - tool for crossmounting between disk image formats
yara - Pattern matching swiss knife for malware researchers
- -- Joao Eriberto Mota Filho Thu, 16 Mar 2023 08:33:39
-0300
+ -- Joao Eriberto Mota Filho Wed, 31 May 2023 16:43:31
-0300
diff -Nru forensics-all-3.44/list-of-packages
forensics-all-3.45/list-of-packages
--- forensics-all-3.44/list-of-packages 2023-03-16 08:04:52.0 -0300
+++ forensics-all-3.45/list-of-packages 2023-05-31 16:38:48.0 -0300
@@ -234,7 +234,7 @@
websploit SS
weevely SS
wfuzz FD
-wifite FD
+wifite FR # FIXME. Was F-D. See #1036809 and #1036591.
wig SS
winregfs FD
wipe FD
Bug#1034530: mtrg: mrtg.postinst uses useradd/groupadd (passwd) while mrtg.postrm uses deluser/delgroup (adduser)
Hi Patrice, Thanks for your bug report. I will an optional sequence, like apt-cacher-ng, to solve this issue. I tested it using the piuparts command. deluser --system mrtg 2>/dev/null || userdel -fr mrtg 2>/dev/null delgroup --system mrtg 2>/dev/null || groupdel -f mrtg 2>/dev/null Regards, Eriberto
Bug#1034534: dcfldd: memory leaks causing out of memory
Package: dcfldd Version: 1.9-1 Severity: important Tags: upstream X-Debbugs-Cc: David Polverari This bug was taken from dcfldd project[1]. [1] https://github.com/resurrecting-open-source-projects/dcfldd/issues/16 Out of memory: Killed process 9737 (dcfldd-v1.9) total-vm:847432kB, anon-rss:844620kB, file-rss:0kB, shmem-rss:0kB, UID:0 pgtables:1696kB oom_score_adj:0 Prepare: swapoff -a # Just for a faster OOM fallocate -l 10G test.dd #create bigger file than your RAM The bug: dcfldd diffwr=on if=/dev/zero of=test.dd # OOM kill Default option (without diffwr) isn't affected. The problem: When destination blocks are same (not written), memory blocks remain allocated. Eriberto
Bug#1034531: ITP: obs-scene-as-transition -- plugin for OBS Studio to use a Scene as a Transition
Package: wnpp Severity: wishlist Owner: Joao Eriberto Mota Filho X-Debbugs-Cc: debian-de...@lists.debian.org, Andi Stone * Package name: obs-scene-as-transition Version : 1.1.0 Upstream Contact: Andi Stone * URL : https://obsproject.com/forum/resources/scene-as-transition.1704 * License : GPL-2 Programming Lang: C Description : plugin for OBS Studio to use a Scene as a Transition This plugin can be used to create all kinds of transitions. It is recommended to get the most out of this plugin that you use other powerful plugins such as obs-move-transition to create advanced movements. Is possible to make the transitions dynamic by passing information from other ways. An example would be putting a text source on the transition scene and having it updated with the name of the scene or game you are transitioning to. Some features: - Choose a scene to use as a transition. - Set the total transition duration. - Set a what point the scene changes (Time or Percentage). - Choose a filter to trigger on the transition scene when the transition starts.
Bug#1033608: Exception: ModuleNotFoundError: No module named 'core.pe.photo'
Control: severity 1033608 important After several checks and tests, I got the following conclusions: - The symlinks are present in the packages provided via Debian repositories. - The package, when installed via APT on Sid and Bookworm, is working correctly. - Building the package in a fresh jail generates the symlinks. A single test: eriberto@canopus:/tmp$ apt download dupeguru Get:1 http://deb.debian.org/debian bookworm/main amd64 dupeguru amd64 4.3.1-3+b1 [439 kB] Fetched 439 kB in 0s (39.9 MB/s) eriberto@canopus:/tmp$ dpkg -c dupeguru_4.3.1-3+b1_amd64.deb | egrep '\->' lrwxrwxrwx root/root 0 2023-01-04 10:05 ./usr/bin/dupeguru -> ../share/dupeguru/run.py lrwxrwxrwx root/root 0 2023-01-04 10:05 ./usr/share/dupeguru/core/pe -> ../../../lib/dupeguru/core/pe lrwxrwxrwx root/root 0 2023-01-04 10:05 ./usr/share/dupeguru/qt/pe -> ../../../lib/dupeguru/qt/pe lrwxrwxrwx root/root 0 2023-01-04 10:05 ./usr/share/pixmaps/dupeguru.png -> ../dupeguru/dgse_logo_128.png I can't see any issue with this package. Considering that an RC bug over this package affects forensics-extra, I am decreasing the severity from grave to important. Ionut, are you installing this package via APT? Best regards, Eriberto
Bug#1023876: linux-image-5.19.0-0.deb11.2-amd64: infinite loop whit RAID1 when shutting down
Hi Salvatore,
Sorry for my delay.
Em dom., 26 de mar. de 2023 às 15:44, Salvatore Bonaccorso
escreveu:
>
> Hi,
>
> On Thu, Mar 23, 2023 at 10:36:21PM +0100, Salvatore Bonaccorso wrote:
> > Hi Eriberto,
> >
> > On Sat, Nov 19, 2022 at 11:53:59AM -0300, Eriberto wrote:
> > > Em sáb., 19 de nov. de 2022 às 11:36, Salvatore Bonaccorso
> > > escreveu:
> > > >
> > > > Hi
> > > >
> > > > On Fri, Nov 11, 2022 at 06:33:23PM -0300, Joao Eriberto Mota Filho
> > > > wrote:
> > > > > Package: src:linux
> > > > > Version: 5.19.11-1~bpo11+1
> > > > > Severity: important
> > > > >
> > > > > Dear maintainer,
> > > > >
> > > > > I have a desktop with 3 polls over RAID1 (2 SSD, 2 HDD, plus 2 SSD).
> > > > > The
> > > > > current kernel on BPO creates an infinite loop when shutting down the
> > > > > system. I
> > > > > can see several messages like:
> > > > >
> > > > > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > > > > systemd-shutdown[1]: Stopping MD devices.
> > > > > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > > > > md: md2 stopped.
> > > > > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > > > > systemd-shutdown[1]: Stopping MD devices.
> > > > > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > > > > md: md2 stopped.
> > > > > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > > > > systemd-shutdown[1]: Stopping MD devices.
> > > > > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > > > > md: md2 stopped.
> > > > > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > > > > systemd-shutdown[1]: Stopping MD devices.
> > > > > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > > > > [...]
> > > > > block device autoloading is deprecated and will be removed
> > > > > block device autoloading is deprecated and will be removed
> > > > > block device autoloading is deprecated and will be removed
> > > > > block device autoloading is deprecated and will be removed
> > > > > block device autoloading is deprecated and will be removed
> > > > > block device autoloading is deprecated and will be removed
> > > > > block device autoloading is deprecated and will be removed
> > > > > block device autoloading is deprecated and will be removed
> > > > > [...]
> > > > > md: md2 stopped.
> > > > > md: md2 stopped.
> > > > > md: md2 stopped.
> > > > > md: md2 stopped.
> > > > > md: md2 stopped.
> > > > > md: md2 stopped.
> > > > > md: md2 stopped.
> > > > > [...]
> > > > > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > > > > systemd-shutdown[1]: Stopping MD devices.
> > > > > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > > > > md: md2 stopped.
> > > > > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > > > > systemd-shutdown[1]: Stopping MD devices.
> > > > > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > > > > md: md2 stopped.
> > > > > [...]
> > > > >
> > > > > There is a solution from Arch Linux[1]:
> > > > >
> > > > > "Arch disabled BLOCK_LEGACY_AUTOLOAD for 5.18 which broke mdraid".
> > > > >
> > > > > [1] https://bbs.archlinux.org/viewtopic.php?id=279383
> > > > >
> > > > > Please, consider disabling the deprecated BLOCK_LEGACY_AUTOLOAD,
> > > > > enabled by
> > > > > default in current kernel on Debian:
> > > > >
> > > > > $ cat /boot/config-5.19.0-0.deb11.2-amd64 | grep BLOCK_LEGACY_AUTOLOAD
> > > > > CONFIG_BLOCK_LEGACY_AUTOLOAD=y
> > > > >
> > > > > Thanks in advance.
> > > >
> > > > I'm not sure, can we can do that (yet)? Some context about this is in
> > > > https://lore.kernel.org/all/yhe%2fc0k0fn9j8...@bombadil.infradead.org/
> > > > . In fact back for 5.18-rc1 upstream has weakened the removal schedule
> > > > for block device autoloading and with 451f0b6f4c44 ("block: default
> > > > BLOCK_LEGACY_AUTOLOAD to y")[1].
> > > >
> > > > Initially it was planned to make it for 5.19, see fbdee71bb5d8
> > > > ("block: deprecate autoloading based on dev_t")[2].
> > > >
> > > > [1]:
> > > > https://git.kernel.org/linus/451f0b6f4c44d7b649ae609157b114b71f6d7875
> > > > [2]:
> > > > https://git.kernel.org/linus/fbdee71bb5d8d054e1bdb5af4c540f2cb86fe296
> > > >
> > > > Regards,
> > > > Salvatore
> > >
> > > Thanks for the clarification Salvatore. Currently, this is a nightmare
> > > for me because I am being compelled to power off my computer via the
> > > energy switch.
> >
> > I noticed in mainline landed 6c0f5898836c ("md: select
> > BLOCK_LEGACY_AUTOLOAD") in 6.3-rc3, which was as well backported to
> > 6.1.21.
> >
> > https://git.kernel.org/linus/6c0f5898836c05c6d850a750ed7940ba29e4e6c5
> >
> > So I guess we can/need to close this bug or mark it wontfix at least
> > for the time beeing.
> >
> > Thoughts?
>
> Well scratch that about closing the bug. The bug still exists, it's
> just that we won't disable BLOCK_LEGACY_AUTOLOAD.
>
> I assume you are still able to reproduce the problem with the most
> current kernel available?
I am using the testing release since Feb 12. I no longer noticed the issue.
Regards,
Eriberto
Bug#1033190: libvisual-plugins: [INTL:de] Updated German Translation
> please find attached the newest German translation. Hi Chris, Your translation, sent in 2023-03-19 is for 0.4.0+dfsg1-17 revision. I uploaded a new upstream version (0.4.1) to experimental in 2023-03-12 and the version 0.4.2, also to experimental, today (some minutes ago). Could you check the last version? You may use tracker[1] or Salsa[2]. [1] https://tracker.debian.org/pkg/libvisual [2] https://salsa.debian.org/debian/libvisual Thanks in advance. Regards, Eriberto
Bug#1033161: ITP: obs-vintage-filter -- plugin for OBS Studio to make sources black and white or sepia
Package: wnpp Severity: wishlist Owner: Joao Eriberto Mota Filho X-Debbugs-Cc: debian-de...@lists.debian.org, cg2121 * Package name: obs-vintage-filter Version : 1.0.0 Upstream Contact: cg2121 * URL : https://obsproject.com/forum/resources/vintage-filter.818/ * License : GPL-2 Programming Lang: C Description : plugin for OBS Studio to make sources black and white or sepia This plugin provides a filter that adds the ability for sources to be black and white or sepia. This is useful to create vintage effects over photos, movies, webcam images, etc.
Bug#1033152: ITP: obs-3d-effect -- plugin for OBS Studio to add a static 3D effect to sources
Package: wnpp Severity: wishlist Owner: Joao Eriberto Mota Filho X-Debbugs-Cc: debian-de...@lists.debian.org, Exeldro * Package name: obs-3d-effect Version : 0.0.2 Upstream Contact: Exeldro * URL : https://obsproject.com/forum/resources/3d-effect.1692/ * License : GPL-2 Programming Lang: C Description : plugin for OBS Studio to add a static 3D effect to sources This plugin provides a filter that creates a static 3D effect over a source. In other words is possible to rotate a source around three axis. Also is possible to move the source over three axis and scale it over two axis.
Bug#1033120: ITP: obs-color-monitor -- plugin for OBS Studio to monitor color balances
Package: wnpp Severity: wishlist Owner: Joao Eriberto Mota Filho X-Debbugs-Cc: debian-de...@lists.debian.org, Norihiro Kamae * Package name: obs-color-monitor Version : 0.4.4+git20230317.dda570c Upstream Contact: Norihiro Kamae * URL : https://obsproject.com/forum/resources/color-monitor.1277/ * License : GPL-2+ Programming Lang: C, C++ Description : plugin for OBS Studio to monitor color balances This plugin provides some sources to monitor color balances, like vectorscope, waveform, histogram, zebra and false color. These tools are useful especially for streaming with multiple cameras. Color conditions can be checked in real time and it is possible to adjust the color correction settings from these monitors. In addition, a dock widget to show sources is available.
Bug#1022161: RFP: obs-backgroundremoval -- OBS Studio Plugin: Background Removal
I noticed this plugin has 90+ bugs opened. Several of these bugs tell about FTBFS and continuous crashes. Eriberto
Bug#1032649: linux-headers-6.1.0-5-amd64: Impossible to build modules via dpkg-reconfigure command
Package: linux-headers-6.1.0-5-amd64 Version: 6.1.12-1 Severity: normal Dear maintainers, When trying to build modules using the commands: # dpkg-reconfigure nvidia-tesla-470-kernel-dkms # dpkg-reconfigure lime-forensics-dkms I got: Module build for kernel 6.1.0-5-amd64 was skipped since the kernel headers for this kernel do not seem to be installed. I have the headers installed on my machine: root@canopus:~# dpkg -l | grep linux-headers ii linux-headers-6.1.0-3-amd64 6.1.8-1 amd64 Header files for Linux 6.1.0-3-amd64 ii linux-headers-6.1.0-3-common 6.1.8-1 allCommon header files for Linux 6.1.0-3 ii linux-headers-6.1.0-5-amd64 6.1.12-1 amd64 Header files for Linux 6.1.0-5-amd64 ii linux-headers-6.1.0-5-common 6.1.12-1 allCommon header files for Linux 6.1.0-5 ii linux-headers-amd64 6.1.12-1 amd64 Header files for Linux amd64 configuration (meta-package) Note this issue is specifically for linux-headers-6.1.0-5-amd64. The linux-headers-6.1.0-3-amd64 is working fine. Regards, Eriberto -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-3-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:pt:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-headers-6.1.0-5-amd64 depends on: ii linux-compiler-gcc-12-x86 6.1.12-1 ii linux-headers-6.1.0-5-common 6.1.12-1 ii linux-kbuild-6.1 6.1.12-1 linux-headers-6.1.0-5-amd64 recommends no packages. linux-headers-6.1.0-5-amd64 suggests no packages. -- no debconf information
Bug#1032157: obs-command-source: Sending Signal seems not working
Package: obs-command-source Version: 0.3.2-1 Severity: normal Tags: upstream X-Debbugs-Cc: Norihiro Kamae Control: forwarded -1 https://github.com/norihiro/obs-command-source/issues/22 I added "xcalc" to "Activated" and I set "Send signal to the command at activated when deactivating". I am using "SIGTERM". The xcalc is shown after the transition from "Preview" to "Program". However, the process keeps alive when the transition is made again and the scene returns to Preview. A workaround is add a "killall xcalc" to "Deactivated" field. Eriberto
Bug#1024589: dislocker: FTBFS with ruby3.1: mv: cannot stat '/<>/debian/tmp/usr/lib/libdislocker*': No such file or directory
Em seg., 27 de fev. de 2023 às 06:42, Santiago Vila escreveu: > > El 26/2/23 a las 0:04, Adrian Bunk escribió: > > The Ubuntu diff has a fix for this issue caused by merged /usr > > (untested). > > Note: Such diff was actually already in #1017937. I've just merged > both bugs. Also, I've tested the diff and confirm that it works. > > Thanks. Today I talked to Giovani, and he's a little busy because of a Masters Course. It asked me to upload the fix. I'll do it. Thanks guys. Regards, Eriberto
Bug#1031774: anacron: manpage error: MAILTO is not catched from crontab
Package: anacron Version: 2.3-36 Severity: important Tags: patch Dear maintainer, This is an important bug because there is a grave issue when sending email messages from anacron. The current anacron manpage on Debian says: If a job generates any output on its standard output or standard error, the output is mailed to the user running Anacron (usually root), or to the address contained by the MAILTO environment variable in the crontab, if such exists. The affirmation about "MAILTO environment variable in the crontab" is not true. anacron never reads this variable. After some tests and inspections, the right is to say "MAILTO environment variable in the /etc/anacrontab file". Also, there is a manpage here[1], from cronie (crond daemon) project, that confirms this new affirmation. [1] https://man7.org/linux/man-pages/man8/anacron.8.html The attached patch will fix the manpage. Regards, Eriberto --- debian/patches/debian-changes.orig 2023-02-22 10:52:05.567668316 -0300 +++ debian/patches/debian-changes 2023-02-22 10:53:22.910146050 -0300 @@ -90,8 +90,8 @@ If a job generates any output on its standard output or standard error, -the output is mailed to the user running Anacron (usually root). +the output is mailed to the user running Anacron (usually root), or to -+the address contained by the MAILTO environment variable in the crontab, if such -+exists. ++the address contained by the MAILTO environment variable in the /etc/anacrontab ++file, if such exists. .PP Informative messages about what Anacron is doing are sent to \fBsyslogd(8)\fR under facility \fBcron\fR, priority \fBnotice\fR. Error messages are sent at
Bug#1031723: ITP: obs-command-source -- plugin for OBS Studio providing a dummy source to execute commands
Package: wnpp Severity: wishlist Owner: Joao Eriberto Mota Filho X-Debbugs-Cc: debian-de...@lists.debian.org, Norihiro Kamae * Package name: obs-command-source Version : 0.3.2 Upstream Contact: Norihiro Kamae * URL : https://obsproject.com/forum/resources/dummy-source-to-execute-command.952/ * License : GPL-2 Programming Lang: C, Python Description : plugin for OBS Studio providing a dummy source to execute commands This plugin provides a dummy source to execute arbitrary commands when a scene is switched. . Current features: . Start a command at the following events: * Show (the source is shown in either preview or program). * Hide (the source is hidden so that no longer shown in neither preview nor program). * Activate (the source goes to the program). * Deactivate (the source goes from the program). * Show in preview (the source goes to the preview). * Hide from preview (the source goes from the preview). . Optionally, kill the created process at these conditions (this feature is not available for Windows as of now): * When hiding, kill the process created at shown. * When deactivating, kill the process created at activated. * When hiding from the preview, kill the process created at preview. . Possible usage: * Implementing custom tally lights. * Controlling PTZ cameras by switching the scene. Ii is possible to combine with CURL to send some commands. * Start and stop a daemon program required for the scene. * Trigger other operations through websocket at the event. A helper script is available for this (request-websocket.py). * Start or stop a streaming and recording. * Open a full screen video. * Open a calculator to teach about finances when switching a scene. * Other actions.
Bug#1031689: ITP: obs-scene-tree-view -- plugin for OBS Studio that adds a scene tree folder dock
Package: wnpp Severity: wishlist Owner: Joao Eriberto Mota Filho X-Debbugs-Cc: debian-de...@lists.debian.org, DigitOtter * Package name: obs-scene-tree-view Version : 0.1.5 Upstream Contact: DigitOtter * URL : https://obsproject.com/forum/resources/scene-tree-folder-plugin-for-obs-studio.1500 * License : GPL-2 Programming Lang: C++ Description : plugin for OBS Studio that adds a scene tree folder dock This plugin allows OBS to group and organize scenes into a folder structure. It is possible to switch the standard scene dock provided by OBS to this special plugin. It is possible to create several folders to group scenes on them.
Bug#992805: bplay - ship with bookworm?
Em dom., 12 de fev. de 2023 às 15:24, Santiago Vila escreveu: > > El 12/2/23 a las 16:33, Eriberto escribió: > > My NMU was a technical work only, an effort to reduce the RC bugs > > number. I don't use bplay. Feel free to make the best for Debian. > > Ok, I also do QA uploads for purely technical reasons. > > My concern is that this procedure to remove a package is suboptimal, > as we seem to be declaring the maintainer MIA and the package orphaned, > all at the same time. > > I suggest that to remove a package from a maintainer which seems to be MIA, > the package should be orphaned first, giving the opportunity for someone else > to take over the package. I agree.
Bug#992805: bplay - ship with bookworm?
Hy guys, Em dom., 12 de fev. de 2023 às 10:31, Santiago Vila escreveu: > > severity 992805 normal > thanks > > El 23/8/21 a las 18:43, Chris Hofstaedtler escribió: > > Source: bplay > > > > Hi, > > > > it appears bplay is an audio player for RIFF and VOC files. To play > > these files, it uses /dev/dsp, an OSS relic. Using it nowadays would > > require wrapping it in aoss (alsa-oss). > > Such wrapping boils down to > > modprobe snd-pcm-oss > > which is quite trivial to do. > > > I'm wondering if it makes sense to ship bplay in bookworm? > > The program still works, and it could be used to test that the snd-pcm-oss > kernel module (which we still provide) works, so it's not completely useless. > > > Upstream appears to have vanished sometime in or before 2007 (>13 > > years ago) and no Debian uploads happened either. > > There was a NMU by Joao Eriberto Mota Filho (in the CC) > to make the package fit for bookworm. > > Since the package has no other RC bugs and it works, I think we > can reconsider about this removal after that, if only as > a way to respect the work of those who bothered to NMU the > package to fit bookworm standards. > > > If no one speaks up, I'll ask for removal sooner or later. > > Well, the problem with this is that nobody really notices > such "if no one speaks up" until it's too late. > > If the maintainer is MIA, then the package should be declared orphaned, > so that somebody else can maintain it if there is some interest. My NMU was a technical work only, an effort to reduce the RC bugs number. I don't use bplay. Feel free to make the best for Debian. Cheers, Eriberto
Bug#1030933: jdupes: internal error: travdone_free() was passed NULL
Hi Berto, Em qui., 9 de fev. de 2023 às 13:03, Alberto Garcia escreveu: > > On Thu, Feb 09, 2023 at 02:37:07PM +0100, Alberto Garcia wrote: > > Thanks for handling this so quickly, I saw the upstream bug report! Thanks for your report. > > The exit status also changes: 1 in the affected version, 0 in the > > earlier ones. This could break some scripts. > > I actually just realized that this breaks the webkit2gtk build if the > documentation is not built (i.e the binary-arch builds) because jdupes > is run with a non-existent directory, which now produces an error. Sorry for this. I saw that webkit2gtk already arrived to testing and it is saved. > I can fix this in webkit but I wouldn't be surprised if other packages > are also affected. jdupes will arrive to testing in 2 days, so I will apply a patch and upload again. Maybe applying the jdupes inside an override_dh_install-indep solves your problem. Cheers, Eriberto
Bug#1030619: spell: Ispell died (if no dictionary)
Em ter., 7 de fev. de 2023 às 14:27, Marcos Talau escreveu: > > Control: tags 1030619 + patch > > Hi there! > > The attached patch fixes this issue. Thank you very much Talau for your contributions to the spell. Regards, Eriberto
Bug#1030694: Rename init variable to fix conflict with entry point
Hi David, Em seg., 6 de fev. de 2023 às 12:27, David Prévot escreveu: > > Package: inotify-tools > Version: 3.22.6.0-3 > Severity: important > Tags: upstream patch > > Hi! > > We’ve noticed that fsnotifywait didn’t work as expected: even if the > kernel is notified, fsnotifywait was not. The following upstream commit > actually fixes the issue, I’ve tested it also on a bullseye server (with > the package rebuilt as a backport). > > https://github.com/inotify-tools/inotify-tools/commit/be8426ce01fbe91cab62bc1131649cc80c60 > > Unfortunately, it also required the following change in the symbols > file. > > - init@Base 3.21.9.5 > + initialized@Base 3.22.6.0 > > Can you please consider applying this small targeted fix in time for the > Bookworm release? Sure! Thanks a lot for your help. Regards, Eriberto
Bug#1030619: spell: Ispell died (if no dictionary)
Package: spell Version: 1.1-1 Severity: normal X-Debbugs-Cc: ta...@debian.org If -D option is called against a non existent ispell dictionary, the spell command exits showing: spell: Ispell died To reproduce (is not needed to have xyz and text.txt): $ spell -D xyz text.txt Regards, Eriberto
Bug#1030611: ITP: obs-ashmanix-countdown -- plugin for OBS Studio to create a countdown timer
Package: wnpp Severity: wishlist Owner: Joao Eriberto Mota Filho X-Debbugs-Cc: debian-de...@lists.debian.org, theashma...@gmail.com, em...@ashmanix.com * Package name: obs-ashmanix-countdown Version : 1.1.0 Upstream Author : Ashmanix * URL : https://obsproject.com/forum/resources/ashmanix-countdown-timer.1610/ * License : GPL-2+ Programming Lang: C++ Description : plugin for OBS Studio to create a countdown timer This plugin lets to use a text source in OBS to show a countdown timer that updates in real time. This is useful to show to viewers the time left before a transmission. The plugin appears as a dockable widget and comes with options to display a final message or to switch to a scene when the counter reaches zero. These two features can be disabled via checkbox, so the countdown will show the zero time when waiting for someone to switch the scene. When configuring, is possible to set a period of time or a real time to count down from it. Also is possible to choose not show some part of the time (hours, minutes, seconds).
Bug#1030362: ITP: obs-source-copy -- plugin for OBS Studio to copy or save scenes, sources and filters
Package: wnpp Severity: wishlist Owner: Joao Eriberto Mota Filho X-Debbugs-Cc: debian-de...@lists.debian.org, Exeldro * Package name: obs-source-copy Version : 0.2.2 Upstream Author : Exeldro * URL : https://obsproject.com/forum/resources/source-copy.1261/ * License : GPL-2 Programming Lang: C Description : plugin for OBS Studio to copy or save scenes, sources and filters This plugin lets to copy to clipboard and paste or save to files and load scenes, sources and filters. The information is saved in JSON format. This plugin is very useful to make backups of the scenes, sources and filters or to transport some elements between "profiles".
Bug#1030193: lintian: Overriding for prefer-uscan-symlink is not possible
Package: lintian Version: 2.116.2 Severity: normal Dear maintainer, In my package obs-move-transition I needed to make an override using filenamemangle[1][2] option. [1] https://salsa.debian.org/debian/obs-move-transition/-/blob/debian/master/debian/watch [2] https://salsa.debian.org/debian/obs-move-transition/-/commit/2482783eb472483f4cec0f0a330712aa6891e692 After this change[2], lintian said me: X: obs-downstream-keyer source: prefer-uscan-symlink filenamemangle s/.*muted..([\d\.]+)..span./@PACKAGE@-$1\.tar\.gz/ [debian/watch:19] After I make an override, litian said me: W: obs-downstream-keyer source: mismatched-override prefer-uscan-symlink filenamemangle s/.*muted..([\d\.]+)..span./@PACKAGE@-$1\.tar\.gz/ [debian/watch:19] [debian/source/lintian-overrides:4] X: obs-downstream-keyer source: prefer-uscan-symlink filenamemangle s/.*muted..([\d\.]+)..span./@PACKAGE@-$1\.tar\.gz/ [debian/watch:19] Consequently, is not possible to make an override for prefer-uscan-symlink filenamemangle. I think that lintian is interpreting my REGEX. Regards, Eriberto
Bug#1029973: ITP: obs-gradient-source -- plugin for OBS Studio that creates a gradient background
Package: wnpp Severity: wishlist Owner: Joao Eriberto Mota Filho X-Debbugs-Cc: debian-de...@lists.debian.org, Exeldro * Package name: obs-gradient-source Version : 0.3.1 Upstream Author : Exeldro * URL : https://obsproject.com/forum/resources/gradient-source.1172 * License : GPL-2 Programming Lang: C Description : plugin for OBS Studio that creates a gradient background This plugin allows OBS to create sources to make available gradients to be used as background. Is possible to choose a size, two colors (from and to), a rotation for the gradient, a midpoint and an opacity level.
Bug#1029560: ITP: obs-source-clone -- plugin for OBS Studio to clone sources from a scene
Package: wnpp Severity: wishlist Owner: Joao Eriberto Mota Filho X-Debbugs-Cc: debian-de...@lists.debian.org, exel...@hotmail.com * Package name: obs-source-clone Version : 0.1.1 Upstream Author : Exeldro * URL : https://obsproject.com/forum/resources/source-clone.1632/ * License : GPL-2 Programming Lang: C Description : plugin for OBS Studio to clone sources from a scene This plugin lets to clone sources to allow different filters than the original. The main idea is generate a new source type that gets sources from a scene and clone them in current scene. WARNING: Source Clone is not an async source. In OBS there are async sources that can have more types of filters.
Bug#969113: spell: Please upload new upstream version 1.1
Em seg., 9 de jan. de 2023 às 10:18, Marcos Talau escreveu: > > Control: tags 969113 + patch > > Hi there! > > The main difference between the upstream and Debian versions is the > "-ispell-dictionary, -D" option. The attached patch implements this > option in the upstream release (1.1). Thanks a lot for your help Marcos. I will upload a new upstream release today. Cheers, Eriberto
Bug#980064: scalpel FTCBFS: combines CFLAGS into CC
Hi guys, Due an NMU sent to Debian without considering previous commits on Salsa, I 'injected' this NMU in Salsa and I did cherry-picks to put all unreleased commits in a position after this NMU. Consequently, the fix for #980064 is now at: https://salsa.debian.org/pkg-security-team/scalpel/-/commit/a760f0bd202e2c2164be2d4025964c98dd8aa1a5 Regards, Eriberto
Bug#1019521: blhc: False positive for Qt6 moc
Em qua., 21 de dez. de 2022 às 11:23, Simon Ruderich escreveu: > Hi Ross, > > thanks for the patch. Looks good. Pushed to [1]. > > Best, > Simon > > [1] > https://ruderich.org/simon/gitweb/?p=blhc/blhc.git;a=commitdiff;h=018466d7ddd9c78f1e1efbafbb7be2f969e1bbd1 Thanks Simon.
Bug#1019521: blhc: False positive for Qt6 moc
Hi Simon, Could you check the patch below? Regards, Eriberto Em qua., 21 de dez. de 2022 às 03:51, Ross Vandegrift escreveu: > > Package: blhc > Version: 0.13-2 > Followup-For: Bug #1019521 > X-Debbugs-Cc: rvandegr...@debian.org > > Hello, > > I also ran into this- moc is now at /usr/lib/qt6/libexec/moc. I think the > attached patch should address this. > > Thanks, > Ross > > -- System Information: > Debian Release: bookworm/sid > APT prefers testing > APT policy: (500, 'testing'), (40, 'unstable'), (1, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 6.0.0-4-amd64 (SMP w/16 CPU threads; PREEMPT) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not > set > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages blhc depends on: > ii libdpkg-perl 1.21.9 > > blhc recommends no packages. > > blhc suggests no packages. > > -- no debconf information
Bug#771656: iwatch: email notification not working
Hi Raffaele, Em seg., 1 de dez. de 2014 às 07:30, raffaele morelli escreveu: > > Package: iwatch > Version: 0.2.2-3 > Severity: important > > Dear Maintainer, > > I've installed iwatch from Debian repos and edited the confing file in > order to receive notification about changing in a particular directory. > > My MTA is properly configured and mail to local users are delivered by > my organization smtp server. > Perl::sendmail module works correctly and I've added my smtp server to the > list in > /usr/share/perl5/Mail/Sendmail.pm > > That give, no mail notification are sent when an event occurs and exim4 > mainlog doesn't reports errors or whatever. > > > Regards > > > -- System Information: > Debian Release: 7.7 > APT prefers testing > APT policy: (500, 'testing'), (500, 'stable') > Architecture: amd64 (x86_64) > > Kernel: Linux 3.2.0-2-amd64 (SMP w/16 CPU cores) > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > > Versions of packages iwatch depends on: > ii exim4-daemon-light [mail-transport-agent] 4.84-3 > ii libevent-perl 1.23-1+b1 > ii liblinux-inotify2-perl 1:1.22-1+b1 > ii libmail-sendmail-perl 0.79.16-1 > ii libxml-simpleobject-libxml-perl0.53-2 > ii perl-modules 5.20.1-3 > > iwatch recommends no packages. > > Versions of packages iwatch suggests: > pn sendxmpp > pn yowsup-cli > > -- Configuration Files: > /etc/default/iwatch changed: > START_DAEMON=true > CONFIG_FILE=/etc/iwatch/iwatch.xml > > /etc/iwatch/iwatch.xml changed: > > > > > > Operating System > > /home/rmorelli/tmp > > > > > -- no debconf information Note as explained in #994857[1], when using iwatch as a daemon via systemd, the email message will be sent by the root user. Is your system configured to send messages from root? Regards, Eriberto [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994857#10
Bug#1023876: linux-image-5.19.0-0.deb11.2-amd64: infinite loop whit RAID1 when shutting down
Em sáb., 19 de nov. de 2022 às 11:36, Salvatore Bonaccorso
escreveu:
>
> Hi
>
> On Fri, Nov 11, 2022 at 06:33:23PM -0300, Joao Eriberto Mota Filho wrote:
> > Package: src:linux
> > Version: 5.19.11-1~bpo11+1
> > Severity: important
> >
> > Dear maintainer,
> >
> > I have a desktop with 3 polls over RAID1 (2 SSD, 2 HDD, plus 2 SSD). The
> > current kernel on BPO creates an infinite loop when shutting down the
> > system. I
> > can see several messages like:
> >
> > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > systemd-shutdown[1]: Stopping MD devices.
> > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > md: md2 stopped.
> > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > systemd-shutdown[1]: Stopping MD devices.
> > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > md: md2 stopped.
> > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > systemd-shutdown[1]: Stopping MD devices.
> > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > md: md2 stopped.
> > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > systemd-shutdown[1]: Stopping MD devices.
> > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > [...]
> > block device autoloading is deprecated and will be removed
> > block device autoloading is deprecated and will be removed
> > block device autoloading is deprecated and will be removed
> > block device autoloading is deprecated and will be removed
> > block device autoloading is deprecated and will be removed
> > block device autoloading is deprecated and will be removed
> > block device autoloading is deprecated and will be removed
> > block device autoloading is deprecated and will be removed
> > [...]
> > md: md2 stopped.
> > md: md2 stopped.
> > md: md2 stopped.
> > md: md2 stopped.
> > md: md2 stopped.
> > md: md2 stopped.
> > md: md2 stopped.
> > [...]
> > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > systemd-shutdown[1]: Stopping MD devices.
> > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > md: md2 stopped.
> > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > systemd-shutdown[1]: Stopping MD devices.
> > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > md: md2 stopped.
> > [...]
> >
> > There is a solution from Arch Linux[1]:
> >
> > "Arch disabled BLOCK_LEGACY_AUTOLOAD for 5.18 which broke mdraid".
> >
> > [1] https://bbs.archlinux.org/viewtopic.php?id=279383
> >
> > Please, consider disabling the deprecated BLOCK_LEGACY_AUTOLOAD, enabled by
> > default in current kernel on Debian:
> >
> > $ cat /boot/config-5.19.0-0.deb11.2-amd64 | grep BLOCK_LEGACY_AUTOLOAD
> > CONFIG_BLOCK_LEGACY_AUTOLOAD=y
> >
> > Thanks in advance.
>
> I'm not sure, can we can do that (yet)? Some context about this is in
> https://lore.kernel.org/all/yhe%2fc0k0fn9j8...@bombadil.infradead.org/
> . In fact back for 5.18-rc1 upstream has weakened the removal schedule
> for block device autoloading and with 451f0b6f4c44 ("block: default
> BLOCK_LEGACY_AUTOLOAD to y")[1].
>
> Initially it was planned to make it for 5.19, see fbdee71bb5d8
> ("block: deprecate autoloading based on dev_t")[2].
>
> [1]: https://git.kernel.org/linus/451f0b6f4c44d7b649ae609157b114b71f6d7875
> [2]: https://git.kernel.org/linus/fbdee71bb5d8d054e1bdb5af4c540f2cb86fe296
>
> Regards,
> Salvatore
Thanks for the clarification Salvatore. Currently, this is a nightmare
for me because I am being compelled to power off my computer via the
energy switch.
Regards,
Eriberto
Bug#1023876: linux-image-5.19.0-0.deb11.2-amd64: infinite loop whit RAID1 when shutting down
Package: src:linux
Version: 5.19.11-1~bpo11+1
Severity: important
Dear maintainer,
I have a desktop with 3 polls over RAID1 (2 SSD, 2 HDD, plus 2 SSD). The
current kernel on BPO creates an infinite loop when shutting down the system. I
can see several messages like:
systemd-shutdown[1]: Not all MD devices stopped. 1 left.
systemd-shutdown[1]: Stopping MD devices.
systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
md: md2 stopped.
systemd-shutdown[1]: Not all MD devices stopped. 1 left.
systemd-shutdown[1]: Stopping MD devices.
systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
md: md2 stopped.
systemd-shutdown[1]: Not all MD devices stopped. 1 left.
systemd-shutdown[1]: Stopping MD devices.
systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
md: md2 stopped.
systemd-shutdown[1]: Not all MD devices stopped. 1 left.
systemd-shutdown[1]: Stopping MD devices.
systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
[...]
block device autoloading is deprecated and will be removed
block device autoloading is deprecated and will be removed
block device autoloading is deprecated and will be removed
block device autoloading is deprecated and will be removed
block device autoloading is deprecated and will be removed
block device autoloading is deprecated and will be removed
block device autoloading is deprecated and will be removed
block device autoloading is deprecated and will be removed
[...]
md: md2 stopped.
md: md2 stopped.
md: md2 stopped.
md: md2 stopped.
md: md2 stopped.
md: md2 stopped.
md: md2 stopped.
[...]
systemd-shutdown[1]: Not all MD devices stopped. 1 left.
systemd-shutdown[1]: Stopping MD devices.
systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
md: md2 stopped.
systemd-shutdown[1]: Not all MD devices stopped. 1 left.
systemd-shutdown[1]: Stopping MD devices.
systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
md: md2 stopped.
[...]
There is a solution from Arch Linux[1]:
"Arch disabled BLOCK_LEGACY_AUTOLOAD for 5.18 which broke mdraid".
[1] https://bbs.archlinux.org/viewtopic.php?id=279383
Please, consider disabling the deprecated BLOCK_LEGACY_AUTOLOAD, enabled by
default in current kernel on Debian:
$ cat /boot/config-5.19.0-0.deb11.2-amd64 | grep BLOCK_LEGACY_AUTOLOAD
CONFIG_BLOCK_LEGACY_AUTOLOAD=y
Thanks in advance.
Regards,
Eriberto
-- Package-specific info:
** Version:
Linux version 5.19.0-0.deb11.2-amd64 (debian-ker...@lists.debian.org) (gcc-10
(Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1
SMP PREEMPT_DYNAMIC Debian 5.19.11-1~bpo11+1 (2022-10-03)
** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.19.0-0.deb11.2-amd64
root=UUID=daa37e3e-4081-445f-ba72-16c898462277 ro
** Tainted: POE (12289)
* proprietary module was loaded
* externally-built ("out-of-tree") module was loaded
* unsigned module was loaded
** Kernel log:
Unable to read kernel log; any relevant messages should be attached
** Model information
sys_vendor: ASUS
product_name: System Product Name
product_version: System Version
chassis_vendor: Default string
chassis_version: Default string
bios_vendor: American Megatrends Inc.
bios_version: 1017
board_vendor: ASUSTeK COMPUTER INC.
board_name: PRIME B560-PLUS
board_version: Rev 1.xx
** Loaded modules:
tls
nfnetlink
bridge
stp
llc
binfmt_misc
intel_rapl_msr
intel_rapl_common
mei_hdcp
nls_ascii
nls_cp437
vfat
fat
x86_pkg_temp_thermal
intel_powerclamp
coretemp
kvm_intel
snd_hda_codec_realtek
snd_hda_codec_generic
kvm
ledtrig_audio
snd_hda_codec_hdmi
snd_usb_audio
snd_hda_intel
irqbypass
snd_intel_dspcfg
snd_intel_sdw_acpi
nvidia_drm(POE)
drm_kms_helper
nvidia_modeset(POE)
rapl
intel_cstate
eeepc_wmi
asus_wmi
platform_profile
battery
efi_pstore
sparse_keymap
rfkill
snd_hda_codec
uvcvideo
snd_usbmidi_lib
snd_hda_core
snd_rawmidi
videobuf2_vmalloc
snd_seq_device
snd_hwdep
videobuf2_memops
videobuf2_v4l2
snd_pcm
joydev
evdev
videobuf2_common
intel_uncore
snd_timer
pcspkr
wmi_bmof
iTCO_wdt
snd
intel_pmc_bxt
mei_me
iTCO_vendor_support
soundcore
mei
watchdog
ee1004
sg
intel_pmc_core
acpi_pad
acpi_tad
button
nvidia(POE)
v4l2loopback(OE)
videodev
mc
dummy
parport_pc
ppdev
lp
parport
loop
dm_crypt
dm_mod
drm
fuse
configfs
efivarfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
hid_logitech_hidpp
hid_logitech_dj
btrfs
zstd_compress
raid10
raid456
async_raid6_recov
async_memcpy
async_pq
async_xor
async_tx
xor
raid6_pq
libcrc32c
raid0
multipath
linear
hid_generic
usbhid
hid
raid1
md_mod
sd_mod
t10_pi
crc64_rocksoft_generic
crc64_rocksoft
crc_t10dif
crct10dif_generic
crc64
crct10dif_pclmul
crct10dif_common
crc32_pclmul
crc32c_intel
ahci
ghash_clmulni_intel
libahci
xhci_pci
libata
xhci_hcd
e1000e
aesni_intel
usbcore
crypto_simd
scsi_mod
cryptd
ptp
intel_lpss_pci
i2c_i801
pps_core
intel_lpss
i2c_smbus
scsi_common
idma64
usb_common
wmi
fan
video
** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Device [8086:9b43] (rev 05)
DeviceName: Onboard - Other
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
Bug#1023180: pdfcrack doesn't respect the -n or -m flags
Em seg., 31 de out. de 2022 às 11:42, Henning Norén escreveu: > > This issue is now resolved in pdfcrack 0.20 (just released). Thanks a lot Henning. I will package this new version now. > The problem with parsing the integer of -n or -m arguments can be > worked around by either: > > pdfcrack -f document.pdf -n 9 > > or: This is for versions =< 0.19, right? Cheers, Eriberto
Bug#1021963: bullseye-pu: package dcfldd/1.7-3+deb11u1
Package: release.debian.org Severity: normal Tags: bullseye User: release.debian@packages.debian.org Usertags: pu [ Reason ] This is not a regression, but a discovered bug. dcfldd is an enhanced dd command that is able to calculate the following hashes when copying data: MD5, SHA1 and SHA2. The SHA1 was being wrongly calculated on big endian architectures. dcfldd SHA1 implementation relies on the WORDS_BIGENDIAN define on big-endian platforms to operate correctly, but it was not defined anywhere, causing wrong results. [ Impact ] If not approved, the SHA1 will be wrong on big endian archs. [ Tests ] Some tests were made on s390x and the current CI test on unstable was improved. [ Risks ] This is a trivial change, no risks. [ Checklist ] [x] *all* changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in (old)stable [x] the issue is verified as fixed in unstable [ Changes ] All changes were made in configure.ac file, via patch, to enable big endian. Please, see the debdiff. [ Other info ] No more information. diff -Nru dcfldd-1.7/debian/changelog dcfldd-1.7/debian/changelog --- dcfldd-1.7/debian/changelog 2020-12-07 01:28:07.0 -0300 +++ dcfldd-1.7/debian/changelog 2022-10-17 20:32:39.0 -0300 @@ -1,3 +1,21 @@ +dcfldd (1.7-3+deb11u1) bullseye; urgency=medium + + * debian/patches/010_fix-sha1-big-endian.patch: created to fix SHA1 output +on big-endian architectures. dcfldd SHA1 implementation relies on the +WORDS_BIGENDIAN defined on big-endian platforms to operate correctly, +but it was not defined anywhere, causing wrong results. +. +Autoconf's AC_C_BIGENDIAN macro defines WORDS_BIGENDIAN when building on +those platforms, fixing the issue. +. +dcfldd SHA1 implementation can perform endianness runtime checks if +RUNTIME_ENDIAN is defined. This patch also makes runtime checking the +default when configuring the build. +. +Closes: #1021784 + + -- Joao Eriberto Mota Filho Mon, 17 Oct 2022 20:32:39 -0300 + dcfldd (1.7-3) unstable; urgency=medium * debian/control: diff -Nru dcfldd-1.7/debian/patches/010_fix-sha1-big-endian.patch dcfldd-1.7/debian/patches/010_fix-sha1-big-endian.patch --- dcfldd-1.7/debian/patches/010_fix-sha1-big-endian.patch 1969-12-31 21:00:00.0 -0300 +++ dcfldd-1.7/debian/patches/010_fix-sha1-big-endian.patch 2022-10-17 20:32:39.0 -0300 @@ -0,0 +1,42 @@ +Description: Fix SHA1 output on big-endian architectures + dcfldd SHA1 implementation relies on the WORDS_BIGENDIAN define on + big-endian platforms to operate correctly, but it was not defined + anywhere, causing wrong results. + . + Autoconf's AC_C_BIGENDIAN macro defines WORDS_BIGENDIAN when building on + those platforms, fixing the issue. + . + dcfldd SHA1 implementation can perform endianness runtime checks if + RUNTIME_ENDIAN is defined. This patch also makes runtime checking the + default when configuring the build. +Author: David Polverari +Origin: https://github.com/resurrecting-open-source-projects/dcfldd/commit/cb54a40d831999fff4158e3ac1c2c561c3dea59f.patch + https://github.com/resurrecting-open-source-projects/dcfldd/commit/72fcf757553965ab7f9fca108768b7c4b843baff.patch + https://github.com/resurrecting-open-source-projects/dcfldd/commit/0a03a00875bc59a8983b022da8bfee77ef8b0cd9.patch +Bug: https://github.com/resurrecting-open-source-projects/dcfldd/issues/11 +Bug-Debian: https://bugs.debian.org/1021784 +Last-Update: 2022-10-17 +Index: dcfldd-1.7/configure.ac +=== +--- dcfldd-1.7.orig/configure.ac dcfldd-1.7/configure.ac +@@ -38,9 +38,19 @@ AC_PROG_RANLIB + AC_HEADER_STDC + + AC_C_CONST ++AC_C_BIGENDIAN + AC_TYPE_OFF_T + AC_TYPE_SIZE_T + ++AC_ARG_ENABLE([runtime-endian-check], ++AC_HELP_STRING([--disable-runtime-endian-check], [disable runtime checks for endianness]) ++) ++ ++AS_IF([test "x$enable_runtime_endian_check" != "xno"], [ ++dnl Do the stuff needed for enabling the feature ++AC_DEFINE([RUNTIME_ENDIAN], 1, [Define whether to check for endianness during runtime]) ++]) ++ + AC_CHECK_DECLS([strtol, strtoul, strtoumax, strndup]) + + AC_OUTPUT(Makefile src/Makefile man/Makefile) diff -Nru dcfldd-1.7/debian/patches/series dcfldd-1.7/debian/patches/series --- dcfldd-1.7/debian/patches/series1969-12-31 21:00:00.0 -0300 +++ dcfldd-1.7/debian/patches/series2022-10-17 20:32:39.0 -0300 @@ -0,0 +1 @@ +010_fix-sha1-big-endian.patch
Bug#1021784: dcfldd: SHA1 hash is wrong over s390x architecture
Package: dcfldd Version: 1.7-3 Severity: important Tags: upstream Control: forwarded -1 https://github.com/resurrecting-open-source-projects/dcfldd/issues/11 The following command fails on s390x: dcfldd if=test.txt hash=md5,sha1,sha256,sha384,sha512 2>&1 | grep -C 20 bc0e4b74695142e0a0bdae87aea310d7078866cb I attached the file test.txt to this bug. The grep shown above will test the SHA1 result. The other hashes are right. See below the result of the test over amd64 WITHOUT the grep: Total (md5): 92994b0ce292a217e3e3bc31b639e565 Total (sha1): bc0e4b74695142e0a0bdae87aea310d7078866cb Total (sha256): 02fd428a4671925e4ca61541b9fac648f4ccdccad65602bfd3256ba14e59489c Total (sha384): 53b8374607a8258de4173265bfbfa6120093fd42090a92fd589cf2c6c16b4e421b513514976713f7949715720a83 Total (sha512): 969a39bf47b5f12d81121084f19cb5ae250e0c0ea5b7c6d82cf08131acde8e1955d137612c2f6b255e25b0e28f96f93586f90f06965cb8f719ed7fbdd95cc8d4 Now, over s390x: Total (md5): 92994b0ce292a217e3e3bc31b639e565 Total (sha1): 68afccc873eb954866097c08d4ad9d9643735f2c Total (sha256): 02fd428a4671925e4ca61541b9fac648f4ccdccad65602bfd3256ba14e59489c Total (sha384): 53b8374607a8258de4173265bfbfa6120093fd42090a92fd589cf2c6c16b4e421b513514976713f7949715720a83 Total (sha512): 969a39bf47b5f12d81121084f19cb5ae250e0c0ea5b7c6d82cf08131acde8e1955d137612c2f6b255e25b0e28f96f93586f90f06965cb8f719ed7fbdd95cc8d4 Only SHA1 differ between both architectures. Executing the sha1sum command over the file on s390x will produce the right hash: (sid_s390x-dchroot)eriberto@zelenka:~$ sha1sum dcfldd-1.7.1/debian/tests/test.txt bc0e4b74695142e0a0bdae87aea310d7078866cb dcfldd-1.7.1/debian/tests/test.txt Eriberto test.txt.gz Description: application/gzip
Bug#1021617: RM: obs-text-slideshow -- ROM; FTBFS, dead upstream
Opsss... Incompatible with obs-studio 28.0.1, not 28.1.2.
Bug#1021616: obs-text-slideshow: FTBFS with OBS 28
Opsss... obs-studio 28.0.1, not 28.1.2.
Bug#1021617: RM: obs-text-slideshow -- ROM; FTBFS, dead upstream
Package: ftp.debian.org Severity: normal The current source code of obs-text-slideshow FTBFS with obs-studio 28.1.2. See #1021616. The upstream declares the development as abandoned[1]. [1] https://github.com/jbwong05/obs-text-slideshow/issues/38 Regards, Eriberto
Bug#1021616: obs-text-slideshow: FTBFS with OBS 28
Package: obs-text-slideshow Version: 1.5.2-3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) The current source code on Debian FTBFS with obs-studio 28.1.2. dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu .. returned exit code 1 make: *** [debian/rules:11: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 debuild: fatal error at line 1182: dpkg-buildpackage -us -uc -ui failed Eriberto
Bug#1021448: apt-venv: autopkgtest regression: output on stderr
Package: apt-venv Version: 1.0.0-4 Severity: serious Dear maintainer, A recent upload of apt-venv introduced CI tests that fail over some architectures. See below an example for arm64. [...] Ign:37 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse arm64 Packages Err:19 http://archive.ubuntu.com/ubuntu jammy/main arm64 Packages 404 Not Found [IP: 185.125.190.36 80] Ign:21 http://archive.ubuntu.com/ubuntu jammy/universe arm64 Packages Ign:23 http://archive.ubuntu.com/ubuntu jammy/restricted arm64 Packages Ign:25 http://archive.ubuntu.com/ubuntu jammy/multiverse arm64 Packages Err:31 http://archive.ubuntu.com/ubuntu jammy-updates/main arm64 Packages 404 Not Found [IP: 185.125.190.36 80] Ign:33 http://archive.ubuntu.com/ubuntu jammy-updates/universe arm64 Packages Ign:35 http://archive.ubuntu.com/ubuntu jammy-updates/restricted arm64 Packages Ign:37 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse arm64 Packages Fetched 27.4 MB in 10s (2692 kB/s) Reading package lists... E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/jammy-security/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.39 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy-updates/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Some index files failed to download. They have been ignored, or old ones used instead. Welcome to apt virtual environment for jammy release. All the configuration is available in /home/debci/.config/apt-venv/jammy You may want run first "apt-get update" autopkgtest [11:14:36]: test apt-cache-update.sh: ---] autopkgtest [11:14:36]: test apt-cache-update.sh: - - - - - - - - - - results - - - - - - - - - - apt-cache-update.sh FAIL stderr: E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] autopkgtest [11:14:36]: test apt-cache-update.sh: - - - - - - - - - - stderr - - - - - - - - - - E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.39 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.39 80] E: Some index files failed to download. They have been ignored, or old ones used instead. E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/bionic-security/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.38 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.38 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-updates/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.38 80] E: Some index files failed to download. They have been ignored, or old ones used instead. E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/focal-security/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/focal/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.39 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/focal-updates/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.39 80] E: Some index files failed to download. They have been ignored, or old ones used instead. E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/jammy-security/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.39 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy-updates/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Some index files failed to download. They have been ignored, or old ones used instead.
Bug#1021445: apt-venv: autopkgtest regression: output on stderr
Package: apt-venv Version: 1.0.0-4 Severity: serious X-Debbugs-Cc: Braulio Henrique Marques Souto Dear maintainer, A recent upload of apt-venv introduced CI tests that fail over some architectures. See below an example for arm64. [...] Ign:37 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse arm64 Packages Err:19 http://archive.ubuntu.com/ubuntu jammy/main arm64 Packages 404 Not Found [IP: 185.125.190.36 80] Ign:21 http://archive.ubuntu.com/ubuntu jammy/universe arm64 Packages Ign:23 http://archive.ubuntu.com/ubuntu jammy/restricted arm64 Packages Ign:25 http://archive.ubuntu.com/ubuntu jammy/multiverse arm64 Packages Err:31 http://archive.ubuntu.com/ubuntu jammy-updates/main arm64 Packages 404 Not Found [IP: 185.125.190.36 80] Ign:33 http://archive.ubuntu.com/ubuntu jammy-updates/universe arm64 Packages Ign:35 http://archive.ubuntu.com/ubuntu jammy-updates/restricted arm64 Packages Ign:37 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse arm64 Packages Fetched 27.4 MB in 10s (2692 kB/s) Reading package lists... E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/jammy-security/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.39 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy-updates/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Some index files failed to download. They have been ignored, or old ones used instead. Welcome to apt virtual environment for jammy release. All the configuration is available in /home/debci/.config/apt-venv/jammy You may want run first "apt-get update" autopkgtest [11:14:36]: test apt-cache-update.sh: ---] autopkgtest [11:14:36]: test apt-cache-update.sh: - - - - - - - - - - results - - - - - - - - - - apt-cache-update.sh FAIL stderr: E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] autopkgtest [11:14:36]: test apt-cache-update.sh: - - - - - - - - - - stderr - - - - - - - - - - E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.39 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.39 80] E: Some index files failed to download. They have been ignored, or old ones used instead. E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/bionic-security/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.38 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.38 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-updates/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.38 80] E: Some index files failed to download. They have been ignored, or old ones used instead. E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/focal-security/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/focal/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.39 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/focal-updates/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.39 80] E: Some index files failed to download. They have been ignored, or old ones used instead. E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/jammy-security/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.39 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy-updates/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Some index files failed to download. They have been ignored, or old ones used instead.
Bug#1021441: apt-venv: autopkgtest regression: output on stderr
Package: apt-venv Version: 1.0.0-4 Severity: serious X-Debbugs-Cc: Braulio Henrique Marques Souto Dear maintainer, A recent upload of apt-venv introduced CI tests that fail over some architectures. See below an example for arm64. [...] Ign:37 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse arm64 Packages Err:19 http://archive.ubuntu.com/ubuntu jammy/main arm64 Packages 404 Not Found [IP: 185.125.190.36 80] Ign:21 http://archive.ubuntu.com/ubuntu jammy/universe arm64 Packages Ign:23 http://archive.ubuntu.com/ubuntu jammy/restricted arm64 Packages Ign:25 http://archive.ubuntu.com/ubuntu jammy/multiverse arm64 Packages Err:31 http://archive.ubuntu.com/ubuntu jammy-updates/main arm64 Packages 404 Not Found [IP: 185.125.190.36 80] Ign:33 http://archive.ubuntu.com/ubuntu jammy-updates/universe arm64 Packages Ign:35 http://archive.ubuntu.com/ubuntu jammy-updates/restricted arm64 Packages Ign:37 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse arm64 Packages Fetched 27.4 MB in 10s (2692 kB/s) Reading package lists... E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/jammy-security/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.39 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy-updates/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Some index files failed to download. They have been ignored, or old ones used instead. Welcome to apt virtual environment for jammy release. All the configuration is available in /home/debci/.config/apt-venv/jammy You may want run first "apt-get update" autopkgtest [11:14:36]: test apt-cache-update.sh: ---] autopkgtest [11:14:36]: test apt-cache-update.sh: - - - - - - - - - - results - - - - - - - - - - apt-cache-update.sh FAIL stderr: E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] autopkgtest [11:14:36]: test apt-cache-update.sh: - - - - - - - - - - stderr - - - - - - - - - - E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.39 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.39 80] E: Some index files failed to download. They have been ignored, or old ones used instead. E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/bionic-security/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.38 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.38 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-updates/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.38 80] E: Some index files failed to download. They have been ignored, or old ones used instead. E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/focal-security/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/focal/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.39 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/focal-updates/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.39 80] E: Some index files failed to download. They have been ignored, or old ones used instead. E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/jammy-security/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.39 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy-updates/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Some index files failed to download. They have been ignored, or old ones used instead.
Bug#1014815: kiwipy initial packaging
Em qui., 6 de out. de 2022 às 18:45, Bastian Germann escreveu: > > Am 06.10.22 um 20:19 schrieb Eriberto Mota: > > Am 05.10.22 um 14:59 schrieb Guilherme Xavier: > >>> Hi, > >>> > >>> Agree, downgrading would be an option. > >>> I don't know how this can be done, but I'm open to doing it. > >> > >> You import the older version as 8.1.1+really6.8.1-1 > > > > > > Nope. Downgrading is a workaround for new upstream versions full broken, > > but already sent to Debian. Is dangerous and undesirable to reintroduce > > an old version of a software to make it "a good dependency". This action > > may generate critical bugs or introduce security holes. The right way is > > ask to the upstream to update the software to use the current version of > > a dependency. In other words, "+really" must be used in very extreme > > cases only, not for adjustments. > > In general, I agree with you. But as far as I can see, Guilherme introduced > python-aio-pika for the sake of packaging kiwipy and probably has not checked > compatiblity before packaging that. It is not in use by any other package. > So for me this would be okay. It is in the archive for two months now and > popcon is at 1. I do not think that upstream will have the issue fixed soon > and it would be a pity if Guilherme's packaging work (there are some more deps > introduced for kiwipy) would not be fruitful for him in the sense of having it > available in bookworm. Ok, this is commendable. However, keeping Debian (as OS) secure is more important than any effort to package anything.
Bug#1014815: kiwipy initial packaging
Am 05.10.22 um 14:59 schrieb Guilherme Xavier: >> Hi, >> >> Agree, downgrading would be an option. >> I don't know how this can be done, but I'm open to doing it. > > You import the older version as 8.1.1+really6.8.1-1 Nope. Downgrading is a workaround for new upstream versions full broken, but already sent to Debian. Is dangerous and undesirable to reintroduce an old version of a software to make it "a good dependency". This action may generate critical bugs or introduce security holes. The right way is ask to the upstream to update the software to use the current version of a dependency. In other words, "+really" must be used in very extreme cases only, not for adjustments. Eriberto
Bug#1021358: libpam-modules-bin: fails when upgrading from 1.5.2-2 revision
To avoid a new breaking when upgrading my jail, I made a "local" NMU to remove the duplicate manpage from a package. I am not familiar with pam packaging, so I choosen libpam-modules-bin.manpages. When installing my "local NMU", I got: dpkg: error processing archive /PKGS/libpam-modules-bin/libpam-modules-bin_1.5.2-3.1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man8/pam_namespace_helper.8.gz', which is also in package libpam-module s:amd64 1.5.2-2 Errors were encountered while processing: /PKGS/libpam-modules-bin/libpam-modules-bin_1.5.2-3.1_amd64.deb After fixing this new issue, the package was installed fine. Regards, Eriberto
Bug#1021358: libpam-modules-bin: fails when upgrading from 1.5.2-2 revision
Package: libpam-modules-bin Version: 1.5.2-3 Severity: grave Justification: renders package unusable Dear maintainer, When upgrading my jail Sid, I got: Preparing to unpack .../libpam-modules-bin_1.5.2-3_amd64.deb ... Unpacking libpam-modules-bin (1.5.2-3) over (1.5.2-2) ... dpkg: error processing archive /var/cache/apt/archives/libpam-modules-bin_1.5.2-3_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man5/namespace.conf.5.gz', which is also in package libpam-modules:amd64 1.5.2-2 Errors were encountered while processing: /var/cache/apt/archives/libpam-modules-bin_1.5.2-3_amd64.deb Thanks! Eriberto
Bug#1019651: "Control: fixed ..." not working
Package: bugs.debian.org Severity: normal Dear maintainers, I noticed in several opportunities that any "Control: fixed" inside email messages won't work. See an example here[1]. I needed to send an extra command via bts ($ bts fixed 336959 spell/1.0-16) to work. [1] https://bugs.debian.org/336959#8 Regards, Eriberto
Bug#1019497: O: watchman -- file watching service
Hello again, After taking a look over the current source code in GitHub, I noticed that it is a nightmare (for me). 1. The most complicated for me: there are 5 embedded libraries (in watchman/thirdparty/). This is a very bad thing because these libraries are old and vulnerable. 2. The program has source code based in 5 different languages (C++, Python, Rust, Java and Thrift). 3. There are several relevant issues opened (including a question about FTBFS in Ubuntu 22.04). I lost interest in adopting this package. Thanks for your previous work. Cheers, Eriberto
Bug#1019497: O: watchman -- file watching service
Em sáb., 10 de set. de 2022 às 13:57, Anuradha Weeraman escreveu: > > On Sat, Sep 10, 2022 at 01:14:51PM -0300, Eriberto Mota wrote: > > Hi Anuradha, > > > > > The current version is dated and there a few issues with the python > > > module that would need to be fixed if it's to make Bookworm. It also > > > depends on an obsolete pcre3 library and the best course of action is to > > > upgrade to the latest version upstream. > > > > Do you know if the python issues were fixed in the latest version upstream? > > Yes, it is. I've just uploaded a version (4.9.0-7) with the fix. I will check this package soon. I am interested in adopting it, but I need to take a look over the source before. Thanks for your work. Cheers, Eriberto
Bug#1019497: O: watchman -- file watching service
Hi Anuradha, > The current version is dated and there a few issues with the python > module that would need to be fixed if it's to make Bookworm. It also > depends on an obsolete pcre3 library and the best course of action is to > upgrade to the latest version upstream. Do you know if the python issues were fixed in the latest version upstream? Cheers, Eriberto
Bug#1019105: RFP: lossless-cut -- Swiss army knife of lossless video/audio editing
Package: wnpp Severity: wishlist X-Debbugs-Cc: Mikael Finstad * Package name: lossless-cut Upstream Author : Mikael Finstad * URL : https://github.com/mifi/lossless-cut * License : GPL-2 Programming Lang: JavaScript Description : Swiss army knife of lossless video/audio editing LosslessCut aims to be the ultimate cross platform FFmpeg GUI for extremely fast and lossless operations on video, audio, subtitle and other related media files. The main feature is lossless trimming and cutting of video and audio files, which is great for saving space by rough-cutting your large video files taken from a video camera, GoPro, drone, etc. It lets you quickly extract the good parts from your videos and discard many gigabytes of data without doing a slow re-encode and thereby losing quality. Or you can add a music or subtitle track to your video without needing to encode. Everything is extremely fast because it does an almost direct data copy, fueled by the awesome FFmpeg which does all the grunt work. Features * Lossless cutting of most video and audio formats. * Smart cut (experimental). * Losslessly cut out parts of video/audio (for cutting away commercials etc.) * Losslessly rearrange the order of video/audio segments. * Lossless merge/concatenation of arbitrary files (with identical codecs parameters, e.g. from the same camera). * Lossless stream editing: - Combine arbitrary tracks from multiple files (ex. add music or subtitle track to a video file). - Remove unneeded tracks. - Replace or re-encode only some tracks. - Extract all tracks from a file (extract video, audio, subtitle, attachments and other tracks from one file into separate files). * Batch view for fast multi-file workflow. * Keyboard shortcut workflow. * Losslessly remux video/audio into a different container (file) format. * Take full-resolution snapshots from videos in JPEG/PNG format, or export ranges of video frames to images. * Manual input of cutpoint times. * Apply a per-file timecode offset (and auto load timecode from file). * Edit file metadata, per-track metadata and per-track disposition. * Change rotation/orientation metadata in videos. * View technical data about all tracks. * Timeline zoom and frame/keyframe jumping for cutting around keyframes. * Video thumbnails and audio waveform. * Saves per project cut segments to project file. * View FFmpeg last command log so you can modify and re-run recent commands on the command line. * Undo/redo. * Give labels to cut segments. * Annotate segments with tags. * Import/export segments: MP4/MKV chapter marks, Text file, YouTube, CSV, CUE, XML (DaVinci, Final Cut Pro) and more. * MKV/MP4 embedded chapters marks editor. * View subtitles. * Customizable keyboard hotkeys. * Black scene detection. * Divide timeline into segments with length L or into N segments or even randomized segments! Example lossless use cases * Cut out commercials from a recorded TV show (and re-format from TS to MP4). * Remove audio tracks from a file. * Extract music track from a video and cut it to your needs. * Add music to a video (or replace existing audio track). * Combine audio and video tracks from separate recordings. * Include an external subtitle into a video. * Quickly change a H264/H265 MKV video to MOV or MP4 for playback on iPhone. * Import a list of cut times from other tool as a EDL (edit decision list, CSV) and run these cuts with LosslessCut. * Export a list of cut times as a CSV EDL and process these in another tool. * Quickly cut a file by its MP4/MKV chapters. * Quickly cut a YouTube video by its chapters (or music times from a comment). * Change the language of a file's audio/subtitle tracks. * Attach cover art to videos. * Change author, title, GPS position, recording time of a video. * Fix rotation of a video that has the wrong orientation flag set - Great for rotating phone videos that come out the wrong way without actually re-encoding the video. * Loop a video / audio clip X times quickly without re-encoding. * Convert a video or parts of it into X image files (not lossless). WARNING: Problem to package it for Debian: lossless-cut build depends of electron. See #842420.
Bug#1018041: blhc: false positive NONVERBOSE BUILD while building with cmake
Em qua., 24 de ago. de 2022 às 15:27, Samuel Thibault escreveu: > > Eriberto, le mer. 24 août 2022 15:25:02 -0300, a ecrit: > > I have several packages using cmake and none of these have issues > > with blhc. The "blhc ignore" was added to blhc to solve small bad > > behaviours. > > Ok, let's live with that then :) Thanks for your interaction. For more details about false positives, please, check blhc(1). Cheers, Eriberto
Bug#1018041: blhc: false positive NONVERBOSE BUILD while building with cmake
Em qua., 24 de ago. de 2022 às 15:19, Samuel Thibault escreveu: > > Hello, > > Eriberto Mota, le mer. 24 août 2022 14:20:26 -0300, a ecrit: > > Em qua., 24 de ago. de 2022 às 12:33, Samuel Thibault > > escreveu: > > > > > > We can see > > > > > > 469:NONVERBOSE BUILD: [ 35%] Building C object > > > src/modules/mpi/CMakeFiles/eztrace-mpi.dir/mpi_funcs/mpi_allgather.c.o > > > 479:NONVERBOSE BUILD: [ 37%] Building C object > > > src/modules/mpi/CMakeFiles/eztrace-mpi.dir/mpi_funcs/mpi_allgatherv.c.o > > > 487:NONVERBOSE BUILD: [ 39%] Building C object > > > src/modules/mpi/CMakeFiles/eztrace-mpi.dir/mpi_funcs/mpi_allreduce.c.o > > > etc. > > > > > > But there are the corresponding verbose lines just after them: > > > > > > https://salsa.debian.org/debian/eztrace/-/jobs/3143966/raw > > > > > > [ 35%] Building C object > > > src/modules/mpi/CMakeFiles/eztrace-mpi.dir/mpi_funcs/mpi_allgather.c.o > > > cd > > > /builds/debian/eztrace/debian/output/source_dir/build-mpich/src/modules/mpi > > > && /usr/bin/mpicc.mpich -Deztrace_mpi_EXPORTS > > > -I/builds/debian/eztrace/debian/output/source_dir/src/modules/mpi > > > -I/builds/debian/eztrace/debian/output/source_dir/src/core/include/eztrace-core > > > -I/builds/debian/eztrace/debian/output/source_dir/src/core/include > > > -I/builds/debian/eztrace/debian/output/source_dir/build-mpich/src/core/include > > > > > > -I/builds/debian/eztrace/debian/output/source_dir/src/eztrace-lib/include > > > -g -O2 > > > -ffile-prefix-map=/builds/debian/eztrace/debian/output/source_dir=. > > > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > > > -D_FORTIFY_SOURCE=2 -I/usr/include -D_GNU_SOURCE -fPIC -Wall -Wextra > > > -Wpedantic -DUSE_MPI3 -DLD_PRELOAD_NAME=\"LD_PRELOAD\" > > > -DMPI_MODULE_NAME=mpich -Wno-error=incompatible-pointer-types > > > -Wno-error=pointer-arith -Wno-error=int-conversion > > > -Wno-gnu-zero-variadic-macro-arguments -D_GNU_SOURCE -MD -MT > > > src/modules/mpi/CMakeFiles/eztrace-mpi.dir/mpi_funcs/mpi_allgather.c.o > > > -MF CMakeFiles/eztrace-mpi.dir/mpi_funcs/mpi_allgather.c.o.d -o > > > CMakeFiles/eztrace-mpi.dir/mpi_funcs/mpi_allgather.c.o -c > > > /builds/debian/eztrace/debian/output/source_dir/src/modules/mpi/mpi_funcs/mpi_allgather.c > > > > > > This issue was caused by a specific behavior of the cmake on this > > source code. Please, check the attached patch to fix the problem, > > forcing blhc to ignore the inadequate lines. > > That does work indeed, thanks! But can't this specific behavior of > cmake be caught by blhc? There are infinite possibilities around possible false positives (or not). A perfect blhc would need AI. So, for blhc, this is not a bug. I have several packages using cmake and none of these have issues with blhc. The "blhc ignore" was added to blhc to solve small bad behaviours. Cheers, Eriberto
Bug#1018041: blhc: false positive NONVERBOSE BUILD while building with cmake
Control: tags 1018041 patch Hi Samuel, Em qua., 24 de ago. de 2022 às 12:33, Samuel Thibault escreveu: > > We can see > > 469:NONVERBOSE BUILD: [ 35%] Building C object > src/modules/mpi/CMakeFiles/eztrace-mpi.dir/mpi_funcs/mpi_allgather.c.o > 479:NONVERBOSE BUILD: [ 37%] Building C object > src/modules/mpi/CMakeFiles/eztrace-mpi.dir/mpi_funcs/mpi_allgatherv.c.o > 487:NONVERBOSE BUILD: [ 39%] Building C object > src/modules/mpi/CMakeFiles/eztrace-mpi.dir/mpi_funcs/mpi_allreduce.c.o > etc. > > But there are the corresponding verbose lines just after them: > > https://salsa.debian.org/debian/eztrace/-/jobs/3143966/raw > > [ 35%] Building C object > src/modules/mpi/CMakeFiles/eztrace-mpi.dir/mpi_funcs/mpi_allgather.c.o > cd > /builds/debian/eztrace/debian/output/source_dir/build-mpich/src/modules/mpi > && /usr/bin/mpicc.mpich -Deztrace_mpi_EXPORTS > -I/builds/debian/eztrace/debian/output/source_dir/src/modules/mpi > -I/builds/debian/eztrace/debian/output/source_dir/src/core/include/eztrace-core > -I/builds/debian/eztrace/debian/output/source_dir/src/core/include > -I/builds/debian/eztrace/debian/output/source_dir/build-mpich/src/core/include > -I/builds/debian/eztrace/debian/output/source_dir/src/eztrace-lib/include -g > -O2 -ffile-prefix-map=/builds/debian/eztrace/debian/output/source_dir=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -I/usr/include -D_GNU_SOURCE -fPIC -Wall -Wextra > -Wpedantic -DUSE_MPI3 -DLD_PRELOAD_NAME=\"LD_PRELOAD\" > -DMPI_MODULE_NAME=mpich -Wno-error=incompatible-pointer-types > -Wno-error=pointer-arith -Wno-error=int-conversion > -Wno-gnu-zero-variadic-macro-arguments -D_GNU_SOURCE -MD -MT > src/modules/mpi/CMakeFiles/eztrace-mpi.dir/mpi_funcs/mpi_allgather.c.o -MF > CMakeFiles/eztrace-mpi.dir/mpi_funcs/mpi_allgather.c.o.d -o > CMakeFiles/eztrace-mpi.dir/mpi_funcs/mpi_allgather.c.o -c > /builds/debian/eztrace/debian/output/source_dir/src/modules/mpi/mpi_funcs/mpi_allgather.c This issue was caused by a specific behavior of the cmake on this source code. Please, check the attached patch to fix the problem, forcing blhc to ignore the inadequate lines. Cheers, Eriberto --- debian/rules.ORIG 2022-08-24 14:07:41.889022406 -0300 +++ debian/rules 2022-08-24 14:08:36.415637889 -0300 @@ -32,6 +32,7 @@ endif override_dh_auto_build: + @echo 'blhc: ignore-line-regexp: \[\ +[0-9]+%\]\ Building\ C\ object\ (src|test)/.+\.c\.o' dh_auto_build -Bbuild-mpich ifeq ($(OPENMPI),yes) dh_auto_build -Bbuild-openmpi
Bug#1016828: poc-streamer: flaky autopkgtest: regularly times out on i386
> I looked at the results of the autopkgtest of you package because it was > showing up on our "slow" page [1]. I noticed that there were several > runs that took 8:21 (our timeout time per test times 3), while > successful runs more in the order of a minute. > > Because the unstable-to-testing migration software now blocks on > regressions in testing, flaky tests, i.e. tests that flip between > passing and failing without changes to the list of installed packages, > are causing people unrelated to your package to spend time on these > tests. [...] > > [1] https://ci.debian.net/status/slow/ Hi Paul, I noticed that superficial tests around pob-2250, pob-3119 and pob-fec are failing. I set a timeout (3 minutes) for these tests and I set them as flaky. I hope these procedures fix all issues. Cheers, Eriberto
Bug#1016851: forensics-extra: Dependency on telnet but not telnet-client
Em seg., 8 de ago. de 2022 às 08:45, Guillem Jover escreveu: > > Source: forensics-extra > Source-Version: 2.39 > Severity: normal > Usertags: inetutils-default-telnet-switch > > Hi! > > This package has a dependency on telnet (which denotes either a specific > implementation or in the future the default one), but not on the > generic telnet-client, which denotes any implementation. > > Please change it to: telnet | telnet-client. Hi Guillem, Thanks for your help. forensics-extra is a metapackage built via scripts. Is a bit hard to use alternatives "|". Considering that telnet is not a essential package for forensics activities, I will drop it. Regards, Eriberto
Bug#1016557: xfonts-cronyx: Non-DFSG file
Source: xfonts-cronyx Version: 2.3.8 Severity: serious Tags: upstream Justification: Policy 2.2.1 X-Debbugs-Cc: eribe...@debian.org The license for tryfont/ISO8859-5 says: --- Copyright (c) 1991-1995 Unicode, Inc. All Rights reserved. This file is provided as-is by Unicode, Inc. (The Unicode Consortium). No claims are made as to fitness for any particular purpose. No warranties of any kind are expressed or implied. The recipient agrees to determine applicability of information provided. If this file has been provided on magnetic media by Unicode, Inc., the sole remedy for any claim will be exchange of defective media within 90 days of receipt. Recipient is granted the right to make copies in any form for internal distribution and to freely use the information supplied in the creation of products supporting Unicode. Unicode, Inc. specifically excludes the right to re-distribute this file directly to third parties or other organizations whether for profit or not. --- Eriberto
Bug#1016457: clif: non-DFSG source code in clif
Package: clif Version: 0.90.2-1 Severity: serious Tags: upstream Justification: Policy 2.2.1 X-Debbugs-Cc: eribe...@debian.org The file ch-lex.c doesn't have a license on its header. However, starting at line 927, I noticed the following text: -- /* Copyright (c) 1989 AT */ /*All Rights Reserved */ /* THIS IS UNPUBLISHED PROPRIETARY SOURCE CODE OF AT */ /* The copyright notice above does not evidence any*/ /* actual or intended publication of such source code. */ #pragma ident "@(#)ncform 6.8 95/02/11 SMI" -- It's clear to me that part of the file includes a non-free source code. Eriberto
Bug#437301: ldap2dns: not handling nostrip build option (policy 10.1)
Em sex., 15 de jul. de 2022 às 13:10, Eriberto Mota escreveu: > > The bug #940607 provides a solution for this issue. However, I noticed that migrating debian/rules to dh sequence (debian/rules in reduced format) also will fix this bug. Eriberto
Bug#437301: ldap2dns: not handling nostrip build option (policy 10.1)
Control: tags 437301 patch The bug #940607 provides a solution for this issue. Regards, Eriberto
Bug#1014885: Conflict: unknown-field Go-Import-Path x missing-xs-go-import-path-for-golang-package
Package: lintian Version: 2.115.2 Severity: important X-Debbugs-Cc: eribe...@debian.org Dear Maintainer, When doing a QA revision over the package "gox", I received the warning: W: gox source: unknown-field Go-Import-Path However, the right field name is XS-Go-Import-Path, not Go-Import-Path. The field is present in debian/control on gox: XS-Go-Import-Path: github.com/mitchellh/gox If the XS-Go-Import-Path filed is removed, the following message is shown: I: gox source: missing-xs-go-import-path-for-golang-package The Debian bug #984719 explains how much the XS-Go-Import-Path field is needed. Regards, Eriberto
Bug#965921: zemberek-server: diff for NMU version 0.7.1-12.4
Control: tags 965921 + patch Control: tags 965921 + pending Dear maintainer, I've prepared an NMU for zemberek-server (versioned as 0.7.1-12.4) and uploaded it to DELAYED/2. Please feel free to tell me if Ishould delay it longer. Regards, Eriberto diff -u zemberek-server-0.7.1/debian/changelog zemberek-server-0.7.1/debian/changelog --- zemberek-server-0.7.1/debian/changelog +++ zemberek-server-0.7.1/debian/changelog @@ -1,3 +1,10 @@ +zemberek-server (0.7.1-12.4) unstable; urgency=medium + + * Non-maintainer upload. + * debian/compat: bumped compat level to 7. (Closes: #965921) + + -- Joao Eriberto Mota Filho Mon, 11 Jul 2022 00:08:28 -0300 + zemberek-server (0.7.1-12.3) unstable; urgency=medium * Non maintainer upload by the Reproducible Builds team. diff -u zemberek-server-0.7.1/debian/compat zemberek-server-0.7.1/debian/compat --- zemberek-server-0.7.1/debian/compat +++ zemberek-server-0.7.1/debian/compat @@ -1 +1 @@ -5 +7
