Bug#1069909: dcraw: diff for NMU version 9.28-5.1
> Dear Eriberto, > > thank you for preparing of the upload. I think it > is completelly ready to be published thanks to you. > > Best regards, > FH > -- > PS. Sorry I am late, the end semester is hectic. Hi Filip, Thanks for your reply. I just uploaded the NMU revision. I wish you a good end of the semester. Regards, Eriberto
Bug#1071975: dh-make: Don't include 'Multi-Arch: foreign' in debian/control
Source: dh-make Version: 2.202302 Severity: serious Justification: Multiarch false promises X-Debbugs-Cc: debian-cr...@lists.debian.org, hel...@subdivi.de, chris.obb...@collabora.com Dear dh-make maintainers, This bug is related to #1040542 and to commit d411b19 on Salsa[1]. [1] https://salsa.debian.org/debian/dh-make/-/commit/d411b19 Currently, the dh_make command adds 'Multi-Arch: foreign' automatically to several packages. This implies that Multiarch will honor all items present here[2] in all new packages sent to Debian and made by people that don't know Multiarch (including some sponsors). [2] https://wiki.debian.org/DependencyHell#Multi-Arch:_foreign The natural consequence will be once such a package enters the archive, the Multiarch:hinter will suggest more 'Multi-Arch: foreign' based on this promise and before too long we have an archive polluted with false promises, rendering Multiarch useless. Regards, Eriberto
Bug#1069909: dcraw: diff for NMU version 9.28-5.1
Control: tags 1069909 + pending
Dear maintainer,
I've prepared an NMU for dcraw (versioned as 9.28-5.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should cancel or delay it longer.
Regards,
Eriberto
diff -Nru dcraw-9.28/debian/changelog dcraw-9.28/debian/changelog
--- dcraw-9.28/debian/changelog 2024-03-26 06:42:04.0 -0300
+++ dcraw-9.28/debian/changelog 2024-05-25 12:18:40.0 -0300
@@ -1,3 +1,12 @@
+dcraw (9.28-5.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/patches/remove-duplicate-memmem.patch: created to avoid a FTBFS
+caused by a redundant duplicate implementation of memmem(). Thanks to
+Steve Langasek . (Closes: #1069909)
+
+ -- Joao Eriberto Mota Filho Sat, 25 May 2024 12:18:40
-0300
+
dcraw (9.28-5) unstable; urgency=low
* Added missing headers for Fuji cameras; Closes: #1066465
diff -Nru dcraw-9.28/debian/patches/remove-duplicate-memmem.patch
dcraw-9.28/debian/patches/remove-duplicate-memmem.patch
--- dcraw-9.28/debian/patches/remove-duplicate-memmem.patch 1969-12-31
21:00:00.0 -0300
+++ dcraw-9.28/debian/patches/remove-duplicate-memmem.patch 2024-05-25
12:18:40.0 -0300
@@ -0,0 +1,28 @@
+Description: don't reimplement memmem()
+ memmem() is implemented in glibc, don't have a redundant duplicate
+ implementation with a different prototype.
+Author: Steve Langasek
+Last-Update: 2024-04-09
+Forwarded: no
+
+Index: dcraw-9.28/parse.c
+===
+--- dcraw-9.28.orig/parse.c
dcraw-9.28/parse.c
+@@ -1213,16 +1213,6 @@
+ }
+ }
+
+-char *memmem (char *haystack, size_t haystacklen,
+- char *needle, size_t needlelen)
+-{
+- char *c;
+- for (c = haystack; c <= haystack + haystacklen - needlelen; c++)
+-if (!memcmp (c, needle, needlelen))
+- return c;
+- return NULL;
+-}
+-
+ /*
+Identify which camera created this file, and set global variables
+accordingly.Return nonzero if the file cannot be decoded.
diff -Nru dcraw-9.28/debian/patches/series dcraw-9.28/debian/patches/series
--- dcraw-9.28/debian/patches/series2024-03-26 06:42:04.0 -0300
+++ dcraw-9.28/debian/patches/series2024-05-25 12:18:40.0 -0300
@@ -8,3 +8,4 @@
iowrap.diff
0009-missing_headers.patch
0010-Fuji-headers.patch
+remove-duplicate-memmem.patch
Bug#1071541: FTBFS: obs-source-clone/audio-wrapper.c:134:25: error: ‘circlebuf_push_back’ is deprecated [-Werror=deprecated-declarations]
KGS/obs-source-clone2/obs-source-clone-0.1.4/source-clone.c:88:17: error: ‘circlebuf_free’ is deprecated [-Werror=deprecated-declarations] 88 | circlebuf_free(>audio_data[i]); | ^~ /usr/include/obs/util/circlebuf.h:46:35: note: declared here 46 | OBS_DEPRECATED static inline void circlebuf_free(struct circlebuf *cb) | ^~ /PKGS/obs-source-clone2/obs-source-clone-0.1.4/source-clone.c:90:9: error: ‘circlebuf_free’ is deprecated [-Werror=deprecated-declarations] 90 | circlebuf_free(>audio_frames); | ^~ /usr/include/obs/util/circlebuf.h:46:35: note: declared here 46 | OBS_DEPRECATED static inline void circlebuf_free(struct circlebuf *cb) | ^~ /PKGS/obs-source-clone2/obs-source-clone-0.1.4/source-clone.c:91:9: error: ‘circlebuf_free’ is deprecated [-Werror=deprecated-declarations] 91 | circlebuf_free(>audio_timestamps); | ^~ /usr/include/obs/util/circlebuf.h:46:35: note: declared here 46 | OBS_DEPRECATED static inline void circlebuf_free(struct circlebuf *cb) | ^~ /PKGS/obs-source-clone2/obs-source-clone-0.1.4/source-clone.c: In function ‘source_clone_video_tick’: /PKGS/obs-source-clone2/obs-source-clone-0.1.4/source-clone.c:588:17: error: ‘circlebuf_pop_front’ is deprecated [-Werror=deprecated-declarations] 588 | circlebuf_pop_front(>audio_frames, , | ^~~ /usr/include/obs/util/circlebuf.h:291:35: note: declared here 291 | OBS_DEPRECATED static inline void circlebuf_pop_front(struct circlebuf *cb, | ^~~ /PKGS/obs-source-clone2/obs-source-clone-0.1.4/source-clone.c:590:17: error: ‘circlebuf_pop_front’ is deprecated [-Werror=deprecated-declarations] 590 | circlebuf_pop_front(>audio_timestamps, | ^~~ /usr/include/obs/util/circlebuf.h:291:35: note: declared here 291 | OBS_DEPRECATED static inline void circlebuf_pop_front(struct circlebuf *cb, | ^~~ /PKGS/obs-source-clone2/obs-source-clone-0.1.4/source-clone.c:598:25: error: ‘circlebuf_pop_front’ is deprecated [-Werror=deprecated-declarations] 598 | circlebuf_pop_front(>audio_data[i], NULL, | ^~~ /usr/include/obs/util/circlebuf.h:291:35: note: declared here 291 | OBS_DEPRECATED static inline void circlebuf_pop_front(struct circlebuf *cb, | ^~~ cc1: all warnings being treated as errors make[3]: *** [CMakeFiles/source-clone.dir/build.make:93: CMakeFiles/source-clone.dir/audio-wrapper.c.o] Error 1 make[3]: *** Waiting for unfinished jobs cc1: all warnings being treated as errors make[3]: *** [CMakeFiles/source-clone.dir/build.make:79: CMakeFiles/source-clone.dir/source-clone.c.o] Error 1 make[3]: Leaving directory '/PKGS/obs-source-clone2/obs-source-clone-0.1.4/obj-i686-linux-gnu' make[2]: *** [CMakeFiles/Makefile2:86: CMakeFiles/source-clone.dir/all] Error 2 make[2]: Leaving directory '/PKGS/obs-source-clone2/obs-source-clone-0.1.4/obj-i686-linux-gnu' make[1]: *** [Makefile:159: all] Error 2 make[1]: Leaving directory '/PKGS/obs-source-clone2/obs-source-clone-0.1.4/obj-i686-linux-gnu' dh_auto_build: error: cd obj-i686-linux-gnu && make -j16 "INSTALL=install --strip-program=true" VERBOSE=1 returned exit code 2 make: *** [debian/rules:17: binary] Error 25 Eriberto
Bug#1071017: FTBFS: source-copy.cpp:615:31: error: ‘void obs_sceneitem_get_info(const obs_sceneitem_t*, obs_transform_info*)’ is deprecated [-Werror=deprecated-declarations]
The current new upstream release (0.2.3) also will FTBFS. Eriberto
Bug#1071007: sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py
Em sáb., 18 de mai. de 2024 às 21:08, Samuel Henrique escreveu: > > Control: reopen -1 = > > I see on git that the bug was closed with a Conflicts+Replaces stanza, but > that's not the correct solution for this issue. > > As discussed on this bugreport, the fix is to not ship the file. > > Reopening to block the problematic package to migrate to testing. > > Cheers, > > -- > Samuel Henrique > In addition, 'Conflicts' is a very extreme solution for many use cases. Eriberto
Bug#1071273: skales: Architecture should be 'all'
Source: skales Version: 0.20170929-2 Severity: serious Justification: Policy 5.6.8 The package only provides executables made in Python, but it is using 'Architecture: any'. Eriberto
Bug#1071017: FTBFS: source-copy.cpp:615:31: error: ‘void obs_sceneitem_get_info(const obs_sceneitem_t*, obs_transform_info*)’ is deprecated [-Werror=deprecated-declarations]
Package: obs-source-copy Version: 0.2.2-5 Severity: serious Tags: upstream Justification: FTBFS When rebuilding the source code, we got: /usr/bin/c++ -DHAVE_OBSCONFIG_H -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_WIDGETS_LIB -Dsource_copy_EXPORTS -I/PKGS/obs-source-copy/1/obs-source-copy-0.2.2/obj-x86_64-linux-gnu/source-copy_autogen/include -isystem /usr/include/obs -isystem /usr/include/x86_64-linux-gnu/qt6/QtWidgets -isystem /usr/include/x86_64-linux-gnu/qt6 -isystem /usr/include/x86_64-linux-gnu/qt6/QtCore -isystem /usr/lib/x86_64-linux-gnu/qt6/mkspecs/linux-g++ -isystem /usr/include/x86_64-linux-gnu/qt6/QtGui -g -O2 -ffile-prefix-map=/PKGS/obs-source-copy/1/obs-source-copy-0.2.2=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Werror -Wextra -Wvla -Wformat -Wformat-security -Wswitch -Wunused-parameter -Wno-unused-function -Wno-missing-field-initializers -fno-strict-aliasing -Wconversion-null -fPIC -mmmx -msse -msse2 -MD -MT CMakeFiles/source-copy.dir/source-copy.cpp.o -MF CMakeFiles/source-copy.dir/source-copy.cpp.o.d -o CMakeFiles/source-copy.dir/source-copy.cpp.o -c /PKGS/obs-source-copy/1/obs-source-copy-0.2.2/source-copy.cpp /PKGS/obs-source-copy/1/obs-source-copy-0.2.2/source-copy.cpp: In function ‘obs_data_t* GetTransformData(obs_sceneitem_t*)’: /PKGS/obs-source-copy/1/obs-source-copy-0.2.2/source-copy.cpp:595:31: error: ‘void obs_sceneitem_get_info(const obs_sceneitem_t*, obs_transform_info*)’ is deprecated [-Werror=deprecated-declarations] 595 | obs_sceneitem_get_info(item, ); | ~~^ In file included from /PKGS/obs-source-copy/1/obs-source-copy-0.2.2/source-copy.hpp:3, from /PKGS/obs-source-copy/1/obs-source-copy-0.2.2/source-copy.cpp:1: /usr/include/obs/obs.h:1889:1: note: declared here 1889 | obs_sceneitem_get_info(const obs_sceneitem_t *item, | ^~ /PKGS/obs-source-copy/1/obs-source-copy-0.2.2/source-copy.cpp: In function ‘void LoadTransform(obs_sceneitem_t*, obs_data_t*)’: /PKGS/obs-source-copy/1/obs-source-copy-0.2.2/source-copy.cpp:615:31: error: ‘void obs_sceneitem_get_info(const obs_sceneitem_t*, obs_transform_info*)’ is deprecated [-Werror=deprecated-declarations] 615 | obs_sceneitem_get_info(item, ); | ~~^ /usr/include/obs/obs.h:1889:1: note: declared here 1889 | obs_sceneitem_get_info(const obs_sceneitem_t *item, | ^~ /PKGS/obs-source-copy/1/obs-source-copy-0.2.2/source-copy.cpp:624:31: error: ‘void obs_sceneitem_set_info(obs_sceneitem_t*, const obs_transform_info*)’ is deprecated [-Werror=deprecated-declarations] 624 | obs_sceneitem_set_info(item, ); | ~~^ /usr/include/obs/obs.h:1892:1: note: declared here 1892 | obs_sceneitem_set_info(obs_sceneitem_t *item, | ^~ cc1plus: all warnings being treated as errors make[3]: *** [CMakeFiles/source-copy.dir/build.make:100: CMakeFiles/source-copy.dir/source-copy.cpp.o] Error 1 make[3]: Leaving directory '/PKGS/obs-source-copy/1/obs-source-copy-0.2.2/obj-x86_64-linux-gnu' make[2]: *** [CMakeFiles/Makefile2:89: CMakeFiles/source-copy.dir/all] Error 2 make[2]: Leaving directory '/PKGS/obs-source-copy/1/obs-source-copy-0.2.2/obj-x86_64-linux-gnu' make[1]: *** [Makefile:159: all] Error 2 make[1]: Leaving directory '/PKGS/obs-source-copy/1/obs-source-copy-0.2.2/obj-x86_64-linux-gnu' dh_auto_build: error: cd obj-x86_64-linux-gnu && make -j16 "INSTALL=install --strip-program=true" VERBOSE=1 returned exit code 2 make: *** [debian/rules:14: binary] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 debuild: fatal error at line 1184: dpkg-buildpackage -us -uc -ui failed Eriberto
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#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#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#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#1042315: marked as pending in wfuzz
Control: tag -1 pending Hello, Bug #1042315 in wfuzz reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/pkg-security-team/wfuzz/-/commit/b1d8aef1a52b7ce9cb08bfde029ba0b16786f752 Merge branch 'debian/master' into 'debian/master' Add patch from upstream PR 347 to fix pyparsing dependency (Closes: #1042315) See merge request pkg-security-team/wfuzz!1 (this message was generated automatically) -- Greetings https://bugs.debian.org/1042315
Bug#1042315: marked as pending in wfuzz
Control: tag -1 pending Hello, Bug #1042315 in wfuzz reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/pkg-security-team/wfuzz/-/commit/bffefb79ef27d31cd586ae0aac88d350ff2ad483 Add patch from upstream PR 347 to fix pyparsing dependency (Closes: #1042315) (this message was generated automatically) -- Greetings https://bugs.debian.org/1042315
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#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#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#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#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#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#1021616: obs-text-slideshow: FTBFS with OBS 28
Opsss... obs-studio 28.0.1, not 28.1.2.
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#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#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#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#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
Bug#1010493: ltrace: diff for NMU version 0.7.3-6.3
Control: tags 1010493 + patch Control: tags 1010493 + pending Dear maintainer, I've prepared an NMU for ltrace (versioned as 0.7.3-6.3) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards, Eriberto diff -Nru ltrace-0.7.3/debian/changelog ltrace-0.7.3/debian/changelog --- ltrace-0.7.3/debian/changelog 2022-03-30 20:48:13.0 -0300 +++ ltrace-0.7.3/debian/changelog 2022-05-02 20:51:56.0 -0300 @@ -1,3 +1,12 @@ +ltrace (0.7.3-6.3) unstable; urgency=medium + + * Non-maintainer upload. + * debian/rules: disabled use of -Werror to avoid a FTBFS in mipsel, alpha and +ia64 when using DH level 13. Thanks to Paul Gevers . +(Closes: #1010493) + + -- Joao Eriberto Mota Filho Mon, 02 May 2022 20:51:56 -0300 + ltrace (0.7.3-6.2) unstable; urgency=medium * Non-maintainer upload. diff -Nru ltrace-0.7.3/debian/rules ltrace-0.7.3/debian/rules --- ltrace-0.7.3/debian/rules 2022-03-30 20:48:13.0 -0300 +++ ltrace-0.7.3/debian/rules 2022-05-02 20:51:07.0 -0300 @@ -4,7 +4,7 @@ dh $@ override_dh_auto_configure: - dh_auto_configure -- --with-libunwind=no + dh_auto_configure -- --with-libunwind=no --disable-werror override_dh_install: dh_install
Bug#1010493: ltrace: FTBFS on mipsel: directive argument is null
Em seg., 2 de mai. de 2022 às 16:21, Paul Gevers escreveu: > > Source: ltrace > Version: 0.7.3-6.1 > Severity: serious > Tags: ftbfs > Justification: FTBFS > X-Debbugs-Cc: Guilherme de Paula Xavier Segundo , > Joao Eriberto Mota Filho > > Dear all, > > Thanks for fixing RC bugs in your package. However, the last upload of ltrace > failed to build from source on mipsel, while it built there successfully in > the past. Can you please have a look? > > Paul > > https://buildd.debian.org/status/fetch.php?pkg=ltrace=mipsel=0.7.3-6.2=1649617481=0 > > Making all in mips [...] > cc1: all warnings being treated as errors Thanks a lot for pointing this out Paul. The right fix will need changes in source code and I am not able to make it. Thus, as a workaround, I will disable werror and this action will fix the build in some architectures. Regards, Eriberto
Bug#965910: xtron: diff for NMU version 1.1a-14.2
Control: tags 965910 + patch Control: tags 965910 + pending Dear maintainer, I've prepared an NMU for xtron (versioned as 1.1a-14.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards, Eriberto diff -u xtron-1.1a/debian/changelog xtron-1.1a/debian/changelog --- xtron-1.1a/debian/changelog +++ xtron-1.1a/debian/changelog @@ -1,3 +1,10 @@ +xtron (1.1a-14.2) unstable; urgency=medium + + * Non-maintainer upload. + * debian/compat: bumped compat level to 7. (Closes: #965910) + + -- Joao Eriberto Mota Filho Fri, 22 Apr 2022 20:18:27 -0300 + xtron (1.1a-14.1) unstable; urgency=medium * Non-maintainer upload. diff -u xtron-1.1a/debian/compat xtron-1.1a/debian/compat --- xtron-1.1a/debian/compat +++ xtron-1.1a/debian/compat @@ -1 +1 @@ -5 +7
Bug#965911: yasat: diff for NMU version 848-1.2
Control: tags 965911 + patch Control: tags 965911 + pending Dear maintainer, I've prepared an NMU for yasat (versioned as 848-1.2) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards, Eriberto diff -Nru yasat-848/debian/changelog yasat-848/debian/changelog --- yasat-848/debian/changelog 2021-01-03 15:56:33.0 -0300 +++ yasat-848/debian/changelog 2022-04-22 19:36:32.0 -0300 @@ -1,3 +1,16 @@ +yasat (848-1.2) unstable; urgency=medium + + * Non-maintainer upload. + * Using new DH level format. Consequently: + - debian/compat: removed. + - debian/control: changed from 'debhelper' to 'debhelper-compat' in +Build-Depends field and bumped level to 13. + - Closes: #965911 + * debian/clean: created to remove some files created from the build process +and forgotten after this. This action will allow package to build twice. + + -- Joao Eriberto Mota Filho Fri, 22 Apr 2022 19:36:32 -0300 + yasat (848-1.1) unstable; urgency=medium * Non maintainer upload by the Reproducible Builds team. diff -Nru yasat-848/debian/clean yasat-848/debian/clean --- yasat-848/debian/clean 1969-12-31 21:00:00.0 -0300 +++ yasat-848/debian/clean 2022-04-22 19:36:32.0 -0300 @@ -0,0 +1,4 @@ +tests/test_rsa.pem +tests/test_rsa_password.pem +tests/yasat_global.advice +yasat.advices diff -Nru yasat-848/debian/compat yasat-848/debian/compat --- yasat-848/debian/compat 2014-01-24 11:29:46.0 -0200 +++ yasat-848/debian/compat 1969-12-31 21:00:00.0 -0300 @@ -1 +0,0 @@ -5 diff -Nru yasat-848/debian/control yasat-848/debian/control --- yasat-848/debian/control2016-08-30 06:04:43.0 -0300 +++ yasat-848/debian/control2022-04-22 19:36:32.0 -0300 @@ -2,7 +2,7 @@ Section: utils Priority: optional Maintainer: Corentin LABBE -Build-Depends: debhelper (>= 7.0.50) +Build-Depends: debhelper-compat (= 13) Standards-Version: 3.9.8 Homepage: http://yasat.sourceforge.net/
Bug#965922: zpspell: diff for NMU version 0.4.3-4.2
Control: tags 965922 + patch Control: tags 965922 + pending Dear maintainer, I've prepared an NMU for zpspell (versioned as 0.4.3-4.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards, Eriberto diff -u zpspell-0.4.3/debian/compat zpspell-0.4.3/debian/compat --- zpspell-0.4.3/debian/compat +++ zpspell-0.4.3/debian/compat @@ -1 +1 @@ -5 +7 diff -u zpspell-0.4.3/debian/changelog zpspell-0.4.3/debian/changelog --- zpspell-0.4.3/debian/changelog +++ zpspell-0.4.3/debian/changelog @@ -1,3 +1,10 @@ +zpspell (0.4.3-4.2) unstable; urgency=medium + + * Non-maintainer upload. + * debian/compat: bumped level to 7. (Closes: #965922) + + -- Joao Eriberto Mota Filho Fri, 22 Apr 2022 19:23:46 -0300 + zpspell (0.4.3-4.1) unstable; urgency=low * Non-maintainer upload.
Bug#965463: cntlm: diff for NMU version 0.92.3-1.1
Control: tags 965463 + patch Control: tags 965463 + pending Dear maintainer, I've prepared an NMU for cntlm (versioned as 0.92.3-1.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards, Eriberto diff -u cntlm-0.92.3/debian/changelog cntlm-0.92.3/debian/changelog --- cntlm-0.92.3/debian/changelog +++ cntlm-0.92.3/debian/changelog @@ -1,3 +1,16 @@ +cntlm (0.92.3-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Using new DH level format. Consequently: + - debian/compat: removed. + - debian/control: changed from 'debhelper' to 'debhelper-compat' in +Build-Depends field and bumped level to 13. + - debian/rules: using 'dh_prep' instead of 'dh_clean -k' because the +'-k' option is not supported since compat 12. + - Closes: #965463 + + -- Joao Eriberto Mota Filho Sun, 17 Apr 2022 15:10:54 -0300 + cntlm (0.92.3-1) unstable; urgency=low * New upstream release. Closes: #652725, #588920. diff -u cntlm-0.92.3/debian/control cntlm-0.92.3/debian/control --- cntlm-0.92.3/debian/control +++ cntlm-0.92.3/debian/control @@ -2,7 +2,7 @@ Section: net Priority: optional Maintainer: David Watson -Build-Depends: debhelper (>= 5) +Build-Depends: debhelper-compat (= 13) Standards-Version: 3.9.3 Vcs-Git: git://planetwatson.co.uk/cntlm Vcs-Browser: http://projects.planetwatson.co.uk/repositories/show/cntlm reverted: --- cntlm-0.92.3/debian/compat +++ cntlm-0.92.3.orig/debian/compat @@ -1 +0,0 @@ -5 diff -u cntlm-0.92.3/debian/rules cntlm-0.92.3/debian/rules --- cntlm-0.92.3/debian/rules +++ cntlm-0.92.3/debian/rules @@ -47,7 +47,7 @@ install: build dh_testdir dh_testroot - dh_clean -k + dh_prep dh_installdirs # Add here commands to install the package into debian/cntlm.
Bug#965455: chrootuid: diff for NMU version 1.3-6.1
Em dom., 17 de abr. de 2022 às 05:48, Javier Fernandez-Sanguino escreveu: > > Dear João, > > Thanks for preparing, the patch looks ok to me. > > Saludos, > > Javier Thanks Javier! I will kill the delay. Have a nice day. Regards, Eriberto
Bug#965462: clif: diff for NMU version 0.93-9.2
Control: tags 965462 + patch Control: tags 965462 + pending Control: tags 999095 + patch Control: tags 999095 + pending Dear maintainer, I've prepared an NMU for clif (versioned as 0.93-9.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards, Eriberto diff -Nru clif-0.93/debian/changelog clif-0.93/debian/changelog --- clif-0.93/debian/changelog 2015-11-02 08:21:14.0 -0200 +++ clif-0.93/debian/changelog 2022-04-16 21:29:06.0 -0300 @@ -1,3 +1,18 @@ +clif (0.93-9.2) unstable; urgency=medium + + * Non-maintainer upload. + * Using new DH level format. Consequently: + - debian/compat: removed. + - debian/control: changed from 'debhelper' to 'debhelper-compat' in +Build-Depends field and bumped level to 13. + - debian/rules: using 'dh_prep' instead of 'dh_clean -k' because the +'-k' option is not supported since compat 12. + - Closes: #965462 + * debian/rules: added missing targets build-arch and build-indep. +(Closes: #999095) + + -- Joao Eriberto Mota Filho Sat, 16 Apr 2022 21:29:06 -0300 + clif (0.93-9.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru clif-0.93/debian/compat clif-0.93/debian/compat --- clif-0.93/debian/compat 2010-01-03 13:27:41.0 -0200 +++ clif-0.93/debian/compat 1969-12-31 21:00:00.0 -0300 @@ -1 +0,0 @@ -5 diff -Nru clif-0.93/debian/control clif-0.93/debian/control --- clif-0.93/debian/control2015-11-02 08:19:46.0 -0200 +++ clif-0.93/debian/control2022-04-16 21:29:06.0 -0300 @@ -2,7 +2,7 @@ Section: interpreters Priority: optional Maintainer: Sam Hocevar -Build-Depends: debhelper (>= 5.0), libx11-dev, libxt-dev, texlive, libelf-dev +Build-Depends: debhelper-compat (= 13), libx11-dev, libxt-dev, texlive, libelf-dev Standards-Version: 3.8.3 Package: clif diff -Nru clif-0.93/debian/rules clif-0.93/debian/rules --- clif-0.93/debian/rules 2010-01-03 14:11:32.0 -0200 +++ clif-0.93/debian/rules 2022-04-16 21:29:06.0 -0300 @@ -46,7 +46,7 @@ install: build dh_testdir dh_testroot - dh_clean -k + dh_prep $(MAKE) install DESTDIR=`pwd`/debian/clif dh_installdirs usr/bin usr/lib/clif dh_install clif usr/bin @@ -83,5 +83,6 @@ dh_builddeb binary: binary-indep binary-arch -.PHONY: build clean binary-indep binary-arch binary install configure - +build-arch: build +build-indep: build +.PHONY: build clean build-arch build-indep binary-indep binary-arch binary install configure
Bug#965468: clamassassin: diff for NMU version 1.2.4-1.2
Control: tags 965468 + patch Control: tags 965468 + pending Control: tags 999015 + patch Control: tags 999015 + pending Dear maintainer, I've prepared an NMU for clamassassin (versioned as 1.2.4-1.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards, Eriberto diff -u clamassassin-1.2.4/debian/changelog clamassassin-1.2.4/debian/changelog --- clamassassin-1.2.4/debian/changelog +++ clamassassin-1.2.4/debian/changelog @@ -1,3 +1,16 @@ +clamassassin (1.2.4-1.2) unstable; urgency=medium + + * Non-maintainer upload. + * Using new DH level format. Consequently: + - debian/compat: removed. + - debian/control: changed from 'debhelper' to 'debhelper-compat' in +Build-Depends field and bumped level to 13. + - Closes: #965468 + * debian/rules: added missing targets build-arch and build-indep. +(Closes: #999015) + + -- Joao Eriberto Mota Filho Sat, 16 Apr 2022 19:47:25 -0300 + clamassassin (1.2.4-1.1) unstable; urgency=medium * Non maintainer upload by the Reproducible Builds team. reverted: --- clamassassin-1.2.4/debian/compat +++ clamassassin-1.2.4.orig/debian/compat @@ -1 +0,0 @@ -5 diff -u clamassassin-1.2.4/debian/control clamassassin-1.2.4/debian/control --- clamassassin-1.2.4/debian/control +++ clamassassin-1.2.4/debian/control @@ -2,7 +2,7 @@ Section: mail Priority: optional Maintainer: Robert S. Edmonds -Build-Depends: debhelper (>= 5) +Build-Depends: debhelper-compat (= 13) Standards-Version: 3.7.2 Package: clamassassin diff -u clamassassin-1.2.4/debian/rules clamassassin-1.2.4/debian/rules --- clamassassin-1.2.4/debian/rules +++ clamassassin-1.2.4/debian/rules @@ -36,5 +36,7 @@ dh_builddeb binary: binary-indep +build-arch: build +build-indep: build -.PHONY: build clean install binary-arch binary-indep binary +.PHONY: build build-arch build-indep clean install binary-arch binary-indep binary
Bug#965455: chrootuid: diff for NMU version 1.3-6.1
Control: tags 965455 + patch Control: tags 965455 + pending Control: tags 998939 + patch Control: tags 998939 + pending Dear maintainer, I've prepared an NMU for chrootuid (versioned as 1.3-6.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards, Eriberto diff -u chrootuid-1.3/debian/rules chrootuid-1.3/debian/rules --- chrootuid-1.3/debian/rules +++ chrootuid-1.3/debian/rules @@ -53,4 +53,6 @@ dh_builddeb binary: binary-indep binary-arch -.PHONY: build clean binary-indep binary-arch binary install configure +build-arch: build +build-indep: build +.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install configure diff -u chrootuid-1.3/debian/control chrootuid-1.3/debian/control --- chrootuid-1.3/debian/control +++ chrootuid-1.3/debian/control @@ -2,7 +2,7 @@ Section: admin Priority: optional Maintainer: Javier Fernandez-Sanguino Pen~a -Build-Depends: debhelper (>> 3.0.0) +Build-Depends: debhelper-compat (= 13) Standards-Version: 3.9.1.0 Homepage: http://ftp.porcupine.org/pub/security/index.html diff -u chrootuid-1.3/debian/changelog chrootuid-1.3/debian/changelog --- chrootuid-1.3/debian/changelog +++ chrootuid-1.3/debian/changelog @@ -1,3 +1,16 @@ +chrootuid (1.3-6.1) unstable; urgency=medium + + * Non-maintainer upload. + * Using new DH level format. Consequently: + - debian/compat: removed. + - debian/control: changed from 'debhelper' to 'debhelper-compat' in +Build-Depends field and bumped level to 13. + - Closes: #965455 + * debian/rules: added missing targets build-arch and build-indep. +(Closes: #998939) + + -- Joao Eriberto Mota Filho Sat, 16 Apr 2022 17:10:27 -0300 + chrootuid (1.3-6) unstable; urgency=low * Change maintainer's e-mail address reverted: --- chrootuid-1.3/debian/compat +++ chrootuid-1.3.orig/debian/compat @@ -1 +0,0 @@ -5
Bug#965457: choosewm: diff for NMU version 0.1.6-3.1
Control: tags 965457 + patch Control: tags 965457 + pending Dear maintainer, I've prepared an NMU for choosewm (versioned as 0.1.6-3.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards, Eriberto diff -Nru choosewm-0.1.6/debian/changelog choosewm-0.1.6/debian/changelog --- choosewm-0.1.6/debian/changelog 2011-08-24 05:52:20.0 -0300 +++ choosewm-0.1.6/debian/changelog 2022-04-16 16:58:21.0 -0300 @@ -1,3 +1,14 @@ +choosewm (0.1.6-3.1) unstable; urgency=medium + + * Non-maintainer upload. + * Using new DH level format. Consequently: + - debian/compat: removed. + - debian/control: changed from 'debhelper' to 'debhelper-compat' in +Build-Depends field and bumped level to 13. + - Closes: #965457 + + -- Joao Eriberto Mota Filho Sat, 16 Apr 2022 16:58:21 -0300 + choosewm (0.1.6-3) unstable; urgency=low * quick fix to make it build again until I have time for diff -Nru choosewm-0.1.6/debian/compat choosewm-0.1.6/debian/compat --- choosewm-0.1.6/debian/compat2011-05-23 05:16:54.0 -0300 +++ choosewm-0.1.6/debian/compat1969-12-31 21:00:00.0 -0300 @@ -1 +0,0 @@ -5 diff -Nru choosewm-0.1.6/debian/control choosewm-0.1.6/debian/control --- choosewm-0.1.6/debian/control 2011-05-23 06:23:19.0 -0300 +++ choosewm-0.1.6/debian/control 2022-04-16 16:58:21.0 -0300 @@ -2,7 +2,7 @@ Section: x11 Priority: extra Maintainer: Bernhard R. Link -Build-Depends: debhelper (>= 5), libglib2.0-dev, libpango1.0-dev, libatk1.0-dev, libgtk2.0-dev, libcairo2-dev +Build-Depends: debhelper-compat (= 13), libglib2.0-dev, libpango1.0-dev, libatk1.0-dev, libgtk2.0-dev, libcairo2-dev Standards-Version: 3.9.2 Package: choosewm
Bug#965440: bplay: diff for NMU version 0.991-10.1
Control: tags 965440 + patch Control: tags 965440 + pending Control: tags 999139 + patch Control: tags 999139 + pending Dear maintainer, I've prepared an NMU for bplay (versioned as 0.991-10.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards, Eriberto diff -u bplay-0.991/debian/changelog bplay-0.991/debian/changelog --- bplay-0.991/debian/changelog +++ bplay-0.991/debian/changelog @@ -1,3 +1,16 @@ +bplay (0.991-10.1) unstable; urgency=medium + + * Non-maintainer upload. + * Using new DH level format. Consequently: + - debian/compat: removed. + - debian/control: changed from 'debhelper' to 'debhelper-compat' in +Build-Depends field and bumped level to 13. + - Closes: #965440 + * debian/rules: added missing targets build-arch and build-indep. +(Closes: #999139) + + -- Joao Eriberto Mota Filho Sat, 16 Apr 2022 16:32:45 -0300 + bplay (0.991-10) unstable; urgency=low * Install the manpages. (Closes: #327759) diff -u bplay-0.991/debian/control bplay-0.991/debian/control --- bplay-0.991/debian/control +++ bplay-0.991/debian/control @@ -2,7 +2,7 @@ Section: sound Priority: optional Maintainer: Carlos Laviola -Build-Depends: debhelper (>> 5.0.0) +Build-Depends: debhelper-compat (= 13) Standards-Version: 3.7.2.2 Package: bplay reverted: --- bplay-0.991/debian/compat +++ bplay-0.991.orig/debian/compat @@ -1 +0,0 @@ -5 diff -u bplay-0.991/debian/rules bplay-0.991/debian/rules --- bplay-0.991/debian/rules +++ bplay-0.991/debian/rules @@ -58,5 +58,7 @@ # Below here is fairly generic really binary:binary-arch +build-arch: build +build-indep: build -.PHONY: build binary binary-arch binary-indep clean checkroot +.PHONY: build build-arch build-indep binary binary-arch binary-indep clean checkroot
Bug#668477: cadaver: diff for NMU version 0.23.3-2.2 (new upload)
I sent a new upload now, with 10 days/delay, with the last changes plus removing no longer needed debian/README.source. Regards, Eriberto
Bug#1005981: redet: diff for NMU version 8.26-1.5
Control: tags 1005981 + patch
Dear maintainer,
I've prepared an NMU for redet (versioned as 8.26-1.5) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.
Regards,
Eriberto
diff -Nru redet-8.26/debian/changelog redet-8.26/debian/changelog
--- redet-8.26/debian/changelog 2022-04-16 02:32:24.0 -0300
+++ redet-8.26/debian/changelog 2022-04-16 02:26:50.0 -0300
@@ -1,3 +1,12 @@
+redet (8.26-1.5) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Migrated to DebSrc 3.0. Consequently:
+ - Migrated the current patch from dpatch to quilt.
+ - Closes: #1005981
+
+ -- Joao Eriberto Mota Filho Sat, 16 Apr 2022 02:26:50
-0300
+
redet (8.26-1.4) unstable; urgency=medium
* Non maintainer upload by the Reproducible Builds team.
diff -Nru redet-8.26/debian/control redet-8.26/debian/control
--- redet-8.26/debian/control 2022-04-16 02:32:24.0 -0300
+++ redet-8.26/debian/control 2022-04-16 02:23:26.0 -0300
@@ -2,7 +2,7 @@
Section: x11
Priority: optional
Maintainer: Bartosz Fenski
-Build-Depends: debhelper (>= 10), dpatch
+Build-Depends: debhelper (>= 10), quilt (>= 0.40)
Standards-Version: 3.9.8
Homepage: http://www.billposer.org/Software/redet.html
diff -Nru redet-8.26/debian/patches/00list redet-8.26/debian/patches/00list
--- redet-8.26/debian/patches/00list2022-04-16 02:32:24.0 -0300
+++ redet-8.26/debian/patches/00list1969-12-31 21:00:00.0 -0300
@@ -1 +0,0 @@
-01_path
diff -Nru redet-8.26/debian/patches/01_path.dpatch
redet-8.26/debian/patches/01_path.dpatch
--- redet-8.26/debian/patches/01_path.dpatch2022-04-16 02:32:24.0
-0300
+++ redet-8.26/debian/patches/01_path.dpatch1969-12-31 21:00:00.0
-0300
@@ -1,33 +0,0 @@
-#! /bin/sh -e
-## redet.dpatch
-## Bartosz Fenski
-
-patch_opts="${patch_opts:--f --no-backup-if-mismatch ${2:+-d $2}}"
-
-if [ $# -ne 1 ]; then
-echo >&2 "`basename $0`: script expects -patch|-unpatch as argument"
-exit 1
-fi
-case "$1" in
- -patch) patch $patch_opts -p1 < $0;;
- -unpatch) patch $patch_opts -R -p1 < $0;;
- *)
- echo >&2 "`basename $0`: script expects -patch|-unpatch as
argument"
- exit 1;;
-esac
-
-exit 0
-
-@DPATCH@
-diff -ru redet-6.13.orig/redet.tcl redet-6.13/redet.tcl
redet-6.13.orig/redet.tcl 2005-07-28 10:53:55.0 +0200
-+++ redet-6.13/redet.tcl 2005-07-28 11:46:40.0 +0200
-@@ -51,7 +51,7 @@
- set HistoryFile ".redethist";
- set JournalFile ".redetlog";
- set ColorFile".redetcolors";
--set NonBinPath [file join /usr local share Redet];
-+set NonBinPath [file join /usr share doc redet-doc];
-
- #Portability
- #Figure out what system we are running on
diff -Nru redet-8.26/debian/patches/01_path.patch
redet-8.26/debian/patches/01_path.patch
--- redet-8.26/debian/patches/01_path.patch 1969-12-31 21:00:00.0
-0300
+++ redet-8.26/debian/patches/01_path.patch 2022-04-16 02:26:15.0
-0300
@@ -0,0 +1,15 @@
+Author: Bartosz Fenski
+Description: fix the path and name of docs.
+Index: redet-8.26/redet.tcl
+===
+--- redet-8.26.orig/redet.tcl
redet-8.26/redet.tcl
+@@ -155,7 +155,7 @@ set InitFile ".redetrc";
+ set HistoryFile ".redethist";
+ set JournalFile ".redetlog";
+ set ColorFile".redetcolors";
+-set NonBinPath [file join /usr local share Redet];
++set NonBinPath [file join /usr share doc redet-doc];
+
+ #Flags showing whether windows are editable
+ set INDEditableP 0;
diff -Nru redet-8.26/debian/patches/series redet-8.26/debian/patches/series
--- redet-8.26/debian/patches/series1969-12-31 21:00:00.0 -0300
+++ redet-8.26/debian/patches/series2022-04-16 02:23:25.0 -0300
@@ -0,0 +1 @@
+01_path.patch
diff -Nru redet-8.26/debian/rules redet-8.26/debian/rules
--- redet-8.26/debian/rules 2022-04-16 02:32:24.0 -0300
+++ redet-8.26/debian/rules 2022-04-16 02:23:26.0 -0300
@@ -8,7 +8,7 @@
# This has to be exported to make some magic below work.
export DH_OPTIONS
-include /usr/share/dpatch/dpatch.make
+include /usr/share/quilt/quilt.make
CFLAGS = -Wall -g
@@ -27,7 +27,7 @@
build-arch:
build-indep: build-indep-stamp
-build-indep-stamp: patch-stamp configure-stamp
+build-indep-stamp: $(QUILT_STAMPFN) configure-stamp
touch build-indep-stamp
diff -Nru redet-8.26/debian/source/format redet-8.26/debian/source/format
--- redet-8.26/debian/source/format 1969-12-31 21:00:00.0 -0300
+++ redet-8.26/debian/source/format 2022-04-16 02:26:50.0 -0300
@@ -0,0 +1 @@
+3.0 (quilt)
Bug#998919: iisemulator: diff for NMU version 0.95-3.4
Control: tags 998919 + patch Control: tags 998919 + pending Dear maintainer, I've prepared an NMU for iisemulator (versioned as 0.95-3.4) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards, Eriberto diff -u iisemulator-0.95/debian/changelog iisemulator-0.95/debian/changelog --- iisemulator-0.95/debian/changelog +++ iisemulator-0.95/debian/changelog @@ -1,3 +1,11 @@ +iisemulator (0.95-3.4) unstable; urgency=medium + + * Non-maintainer upload. + * debian/rules: added missing targets build-arch and build-indep. +(Closes: #998919) + + -- Joao Eriberto Mota Filho Sat, 16 Apr 2022 02:11:23 -0300 + iisemulator (0.95-3.3) unstable; urgency=medium * Non maintainer upload by the Reproducible Builds team. diff -u iisemulator-0.95/debian/rules iisemulator-0.95/debian/rules --- iisemulator-0.95/debian/rules +++ iisemulator-0.95/debian/rules @@ -72,4 +72,6 @@ dh_builddeb binary: binary-indep binary-arch -.PHONY: build clean binary-indep binary-arch binary install configure +build-arch: build +build-indep: build +.PHONY: build clean build-arch build-indep binary-indep binary-arch binary install configure
Bug#999268: vncsnapshot: diff for NMU version 1.2a-5.2
Control: tags 999268 + patch Control: tags 999268 + pending Dear maintainer, I've prepared an NMU for vncsnapshot (versioned as 1.2a-5.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards, Eriberto diff -Nru vncsnapshot-1.2a/debian/changelog vncsnapshot-1.2a/debian/changelog --- vncsnapshot-1.2a/debian/changelog 2012-06-06 13:56:25.0 -0300 +++ vncsnapshot-1.2a/debian/changelog 2022-04-16 02:00:41.0 -0300 @@ -1,3 +1,11 @@ +vncsnapshot (1.2a-5.2) unstable; urgency=medium + + * Non-maintainer upload. + * debian/rules: added missing targets build-arch and build-indep. +(Closes: #999268) + + -- Joao Eriberto Mota Filho Sat, 16 Apr 2022 02:00:41 -0300 + vncsnapshot (1.2a-5.1) unstable; urgency=low * Non-maintainer upload. diff -Nru vncsnapshot-1.2a/debian/rules vncsnapshot-1.2a/debian/rules --- vncsnapshot-1.2a/debian/rules 2012-06-06 13:55:44.0 -0300 +++ vncsnapshot-1.2a/debian/rules 2022-04-16 02:00:41.0 -0300 @@ -66,4 +66,6 @@ dh_builddeb binary: binary-indep binary-arch -.PHONY: build clean binary-indep binary-arch binary install configure +build-arch: build +build-indep: build +.PHONY: build clean build-arch build-indep binary-indep binary-arch binary install configure
Bug#668477: cadaver: diff for NMU version 0.23.3-2.2
Control: tags 668477 + pending Control: tags 965443 + patch Control: tags 965443 + pending Dear maintainer, I've prepared an NMU for cadaver (versioned as 0.23.3-2.2) and uploaded it to DELAYED/10. Please feel free to tell me if I should delay it longer. Regards, Eriberto diff -Nru cadaver-0.23.3/debian/changelog cadaver-0.23.3/debian/changelog --- cadaver-0.23.3/debian/changelog 2022-04-16 01:41:44.0 -0300 +++ cadaver-0.23.3/debian/changelog 2022-04-15 21:27:34.0 -0300 @@ -1,3 +1,21 @@ +cadaver (0.23.3-2.2) unstable; urgency=medium + + * Non-maintainer upload. + * Migrated to DebSrc 3.0. Consequently: + - debian/source/options: created to ignore changes in config.guess and +config.sub. + - Migrated the current patch from dpatch to quilt. + - Closes: #668477 + * Using new DH level format. Consequently: + - debian/compat: removed. + - debian/control: changed from 'debhelper' to 'debhelper-compat' in +Build-Depends field and bumped level to 13. + - debian/rules: using 'dh_prep' instead of 'dh_clean -k' because the +'-k' option is not supported since compat 12. + - Closes: #965443 + + -- Joao Eriberto Mota Filho Fri, 15 Apr 2022 21:27:34 -0300 + cadaver (0.23.3-2.1) unstable; urgency=low * Non-maintainer upload. diff -Nru cadaver-0.23.3/debian/compat cadaver-0.23.3/debian/compat --- cadaver-0.23.3/debian/compat2022-04-16 01:41:44.0 -0300 +++ cadaver-0.23.3/debian/compat1969-12-31 21:00:00.0 -0300 @@ -1 +0,0 @@ -5 diff -Nru cadaver-0.23.3/debian/control cadaver-0.23.3/debian/control --- cadaver-0.23.3/debian/control 2022-04-16 01:41:44.0 -0300 +++ cadaver-0.23.3/debian/control 2022-04-15 21:27:34.0 -0300 @@ -2,7 +2,7 @@ Section: web Priority: optional Maintainer: Sebastian Harl -Build-Depends: debhelper (>= 5), dpkg-dev (>= 1.14.6), dpatch, +Build-Depends: debhelper-compat (= 13), dpkg-dev (>= 1.14.6), quilt (>= 0.40), autotools-dev, libgcrypt20-dev, libncurses5-dev, diff -Nru cadaver-0.23.3/debian/patches/00list cadaver-0.23.3/debian/patches/00list --- cadaver-0.23.3/debian/patches/00list2022-04-16 01:41:44.0 -0300 +++ cadaver-0.23.3/debian/patches/00list1969-12-31 21:00:00.0 -0300 @@ -1,2 +0,0 @@ -manpage_hyphen.dpatch - diff -Nru cadaver-0.23.3/debian/patches/manpage_hyphen.dpatch cadaver-0.23.3/debian/patches/manpage_hyphen.dpatch --- cadaver-0.23.3/debian/patches/manpage_hyphen.dpatch 2022-04-16 01:41:44.0 -0300 +++ cadaver-0.23.3/debian/patches/manpage_hyphen.dpatch 1969-12-31 21:00:00.0 -0300 @@ -1,27 +0,0 @@ -#! /bin/sh /usr/share/dpatch/dpatch-run -## manpage_hyphen.dpatch by Sebastian Harl -## -## DP: Do not use hyphens as minus signs. - -@DPATCH@ - a/doc/cadaver.1 -+++ b/doc/cadaver.1 -@@ -2,7 +2,7 @@ - .SH NAME - cadaver \- A command\-line WebDAV client for Unix. - .SH SYNOPSIS --cadaver [-trp[-r file][-p host[:port]]][-V][-h] http://hostname[:port]/path -+cadaver [\-trp[\-r file][\-p host[:port]]][\-V][\-h] http://hostname[:port]/path - .SH DESCRIPTION - .B cadaver - supports file upload, download, on-screen display, namespace operations -@@ -162,7 +162,7 @@ - .IP - .SH FILES - .IP "~/.cadaverrc" --Individual user settings that can override cadaver defaults and to script cadaver. Can be changed by the "--rcfile" option. -+Individual user settings that can override cadaver defaults and to script cadaver. Can be changed by the "\-\-rcfile" option. - .IP "~/.netrc" - Login and initialization information used by the auto-login process. See - section "THE .netrc FILE" for details. diff -Nru cadaver-0.23.3/debian/patches/manpage_hyphen.patch cadaver-0.23.3/debian/patches/manpage_hyphen.patch --- cadaver-0.23.3/debian/patches/manpage_hyphen.patch 1969-12-31 21:00:00.0 -0300 +++ cadaver-0.23.3/debian/patches/manpage_hyphen.patch 2022-04-15 21:27:34.0 -0300 @@ -0,0 +1,22 @@ +Author: Sebastian Harl +Description: Do not use hyphens as minus signs. +--- cadaver-0.23.3.orig/doc/cadaver.1 cadaver-0.23.3/doc/cadaver.1 +@@ -2,7 +2,7 @@ + .SH NAME + cadaver \- A command\-line WebDAV client for Unix. + .SH SYNOPSIS +-cadaver [-trp[-r file][-p host[:port]]][-V][-h] http://hostname[:port]/path ++cadaver [\-trp[\-r file][\-p host[:port]]][\-V][\-h] http://hostname[:port]/path + .SH DESCRIPTION + .B cadaver + supports file upload, download, on-screen display, namespace operations +@@ -162,7 +162,7 @@ Connects to a server called secure.examp + .IP + .SH FILES + .IP "~/.cadaverrc" +-Individual user settings that can override cadaver defaults and to script cadaver. Can be changed by the "--rcfile" option. ++Individual user settings that can override cadaver defaults and to script cadaver. Can be changed by the "\-\-rcfile" option. + .IP "~/.netrc"
Bug#965418: asql: diff for NMU version 1.6-1.2
Package: asql Version: 1.6-1.1 Severity: normal Tags: patch pending Dear maintainer, I've prepared an NMU for asql (versioned as 1.6-1.2) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards, Eriberto diff -Nru asql-1.6/debian/changelog asql-1.6/debian/changelog --- asql-1.6/debian/changelog 2021-01-05 14:29:40.0 -0300 +++ asql-1.6/debian/changelog 2022-04-14 13:40:34.0 -0300 @@ -1,3 +1,18 @@ +asql (1.6-1.2) unstable; urgency=medium + + * Non-maintainer upload. + * Using new DH level format. Consequently: + - debian/compat: removed. + - debian/control: changed from 'debhelper' to 'debhelper-compat' in +Build-Depends field and bumped level to 13. + - debian/rules: using 'dh_prep' instead of 'dh_clean -k' because the +'-k' option is not supported since compat 12. + - Closes: #965418 + * debian/rules: added missing targets build-arch and build-indep. +(Closes: #999113) + + -- Joao Eriberto Mota Filho Thu, 14 Apr 2022 13:40:34 -0300 + asql (1.6-1.1) unstable; urgency=medium * Non maintainer upload by the Reproducible Builds team. diff -Nru asql-1.6/debian/compat asql-1.6/debian/compat --- asql-1.6/debian/compat 2010-10-04 17:19:07.0 -0300 +++ asql-1.6/debian/compat 1969-12-31 21:00:00.0 -0300 @@ -1 +0,0 @@ -5 diff -Nru asql-1.6/debian/control asql-1.6/debian/control --- asql-1.6/debian/control 2010-10-04 17:19:07.0 -0300 +++ asql-1.6/debian/control 2022-04-14 13:40:34.0 -0300 @@ -2,7 +2,7 @@ Section: admin Priority: optional Maintainer: Steve Kemp -Build-Depends: debhelper (>> 5.0.0) +Build-Depends: debhelper-compat (= 13) Standards-Version: 3.8.4 Homepage: http://www.steve.org.uk/Software/asql/ diff -Nru asql-1.6/debian/rules asql-1.6/debian/rules --- asql-1.6/debian/rules 2010-10-04 17:19:07.0 -0300 +++ asql-1.6/debian/rules 2022-04-14 13:40:34.0 -0300 @@ -25,7 +25,7 @@ install: build dh_testdir dh_testroot - dh_clean -k + dh_prep dh_installdirs make install PREFIX=`pwd`/debian/asql mkdir -p `pwd`/debian/asql/usr/share/man/man8/ @@ -51,4 +51,6 @@ # We have nothing to do here binary: binary-indep binary-arch -.PHONY: build clean binary-indep binary-arch binary install +build-arch: build +build-indep: build +.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install
Bug#999182: perforate: diff for NMU version 1.2-5.2
Em qua., 6 de abr. de 2022 às 16:09, Reuben Thomas escreveu: > > On Wed, 6 Apr 2022 at 18:15, Joao Eriberto Mota Filho > wrote: >> >> Control: tags 999182 + patch >> Control: tags 999182 + pending >> >> Dear maintainer, >> >> I've prepared an NMU for perforate (versioned as 1.2-5.2) and uploaded it >> to DELAYED/1 (a decreased time because the package is set as LowNMU, but >> 1 day because I prefer to put a delay time). > > > Thanks for this, Eriberto! > > Actually, I could do with some help with perforate. I am trying to update it > *and* change the package name to "finddup", as a) there isn't a binary called > perforate, which is confusing; and b) the zum utility (which does the > "perforation") isn't actually that useful on modern systems. I believe most > users are interested in finddup. I've also added "findcore" to find core > files. > > The current version of the package upstream is at > https://github.com/rrthomas/finddup/ > > I've made attempts to upload it as a new package in 2018 and 2021 and failed > each time (for perfectly good reasons). > > If there's anything you could do to help get the new upstream version into > Debian, that would be fantastic. > > -- > https://rrt.sc3d.org Hi Reuben, Sorry, but I don't wish to have a major link with this package. My intention is to do a simple NMU. Good luck. Regards, Eriberto
Bug#999182: perforate: diff for NMU version 1.2-5.2
Control: tags 999182 + patch Control: tags 999182 + pending Dear maintainer, I've prepared an NMU for perforate (versioned as 1.2-5.2) and uploaded it to DELAYED/1 (a decreased time because the package is set as LowNMU, but 1 day because I prefer to put a delay time). Regards, Eriberto diff -u perforate-1.2/debian/changelog perforate-1.2/debian/changelog --- perforate-1.2/debian/changelog +++ perforate-1.2/debian/changelog @@ -1,3 +1,11 @@ +perforate (1.2-5.2) unstable; urgency=medium + + * Non-maintainer upload. + * debian/rules: added missing targets build-arch and build-indep. +(Closes: #999182) + + -- Joao Eriberto Mota Filho Wed, 06 Apr 2022 13:52:52 -0300 + perforate (1.2-5.1) unstable; urgency=medium * Non-maintainer upload. diff -u perforate-1.2/debian/rules perforate-1.2/debian/rules --- perforate-1.2/debian/rules +++ perforate-1.2/debian/rules @@ -45,4 +45,6 @@ binary-indep: build -.PHONY: clean build binary binary-arch binary-indep +build-arch: build +build-indep: build +.PHONY: clean build build-arch build-indep binary binary-arch binary-indep
Bug#999204: whereami: diff for NMU version 0.3.34-0.5
Control: tags 999204 + patch Control: tags 999204 + pending Dear maintainer, I've prepared an NMU for whereami (versioned as 0.3.34-0.5) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards, Eriberto diff -u whereami-0.3.34/debian/changelog whereami-0.3.34/debian/changelog --- whereami-0.3.34/debian/changelog +++ whereami-0.3.34/debian/changelog @@ -1,3 +1,11 @@ +whereami (0.3.34-0.5) unstable; urgency=medium + + * Non-maintainer upload. + * debian/rules: added missing targets build-arch and build-indep. +(Closes: #999204) + + -- Joao Eriberto Mota Filho Tue, 05 Apr 2022 17:58:14 -0300 + whereami (0.3.34-0.4) unstable; urgency=medium * Non-maintainer upload. diff -u whereami-0.3.34/debian/rules whereami-0.3.34/debian/rules --- whereami-0.3.34/debian/rules +++ whereami-0.3.34/debian/rules @@ -105,4 +105,6 @@ source diff: @echo >&2 'source and diff are obsolete - use dpkg-source -b'; false -.PHONY: binary-arch binary-indep clean +build-arch: build +build-indep: build +.PHONY: build-arch build-indep binary-arch binary-indep clean
Bug#999009: scanssh: diff for NMU version 2.0-4.2
Control: tags 999009 + patch Control: tags 999009 + pending Dear maintainer, I've prepared an NMU for scanssh (versioned as 2.0-4.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards, Eriberto diff -u scanssh-2.0/debian/changelog scanssh-2.0/debian/changelog --- scanssh-2.0/debian/changelog +++ scanssh-2.0/debian/changelog @@ -1,3 +1,11 @@ +scanssh (2.0-4.2) unstable; urgency=medium + + * Non-maintainer upload. + * debian/rules: added missing targets build-arch and build-indep. +(Closes: #999009) + + -- Joao Eriberto Mota Filho Tue, 05 Apr 2022 17:50:08 -0300 + scanssh (2.0-4.1) unstable; urgency=medium * Non-maintainer upload. diff -u scanssh-2.0/debian/rules scanssh-2.0/debian/rules --- scanssh-2.0/debian/rules +++ scanssh-2.0/debian/rules @@ -91,4 +91,6 @@ dh_builddeb binary: binary-indep binary-arch -.PHONY: build clean binary-indep binary-arch binary install configure +build-arch: build +build-indep: build +.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install configure
Bug#999064: parchive: diff for NMU version 1.1-4.2
Control: tags 999064 + patch Control: tags 999064 + pending Dear maintainer, I've prepared an NMU for parchive (versioned as 1.1-4.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards, Eriberto diff -u parchive-1.1/debian/changelog parchive-1.1/debian/changelog --- parchive-1.1/debian/changelog +++ parchive-1.1/debian/changelog @@ -1,3 +1,11 @@ +parchive (1.1-4.2) unstable; urgency=medium + + * Non-maintainer upload. + * debian/rules: added missing targets build-arch and build-indep. +(Closes: #999064) + + -- Joao Eriberto Mota Filho Tue, 05 Apr 2022 17:41:54 -0300 + parchive (1.1-4.1) unstable; urgency=medium * Non-maintainer upload. diff -u parchive-1.1/debian/rules parchive-1.1/debian/rules --- parchive-1.1/debian/rules +++ parchive-1.1/debian/rules @@ -82,4 +82,6 @@ dh_builddeb binary: binary-indep binary-arch -.PHONY: build clean binary-indep binary-arch binary install configure +build-arch: build +build-indep: build +.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install configure
Bug#999020: devio: diff for NMU version 1.2-1.3
Control: tags 999020 + patch Control: tags 999020 + pending Dear maintainer, I've prepared an NMU for devio (versioned as 1.2-1.3) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards, Eriberto diff -u devio-1.2/debian/changelog devio-1.2/debian/changelog --- devio-1.2/debian/changelog +++ devio-1.2/debian/changelog @@ -1,3 +1,11 @@ +devio (1.2-1.3) unstable; urgency=medium + + * Non-maintainer upload. + * debian/rules: added missing targets build-arch and build-indep. +(Closes: #999020) + + -- Joao Eriberto Mota Filho Tue, 05 Apr 2022 17:25:12 -0300 + devio (1.2-1.2) unstable; urgency=medium * Non-maintainer upload. diff -u devio-1.2/debian/rules devio-1.2/debian/rules --- devio-1.2/debian/rules +++ devio-1.2/debian/rules @@ -83,4 +83,6 @@ dh_builddeb binary: binary-indep binary-arch -.PHONY: build clean binary-indep binary-arch binary install +build-arch: build +build-indep: build +.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install
Bug#965555: glurp: diff for NMU version 0.12.3-1.1
Control: tags 96 + patch Control: tags 96 + pending Dear maintainer, I've prepared an NMU for glurp (versioned as 0.12.3-1.1) and uploaded it to DELAYED/10. Please feel free to tell me if I should delay it longer or cancel the upload. Regards, Eriberto diff -u glurp-0.12.3/debian/changelog glurp-0.12.3/debian/changelog --- glurp-0.12.3/debian/changelog +++ glurp-0.12.3/debian/changelog @@ -1,3 +1,19 @@ +glurp (0.12.3-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Using new DH level format. Consequently: + - debian/compat: removed. + - debian/control: changed from 'debhelper' to 'debhelper-compat' in + Build-Depends field and bumped level to 13. + - Closes: #96 + * Dropped CDBS in favor of the debhelper to allow the build system to use + DH level greater than 11. Consequently: + - debian/control: removed no longer needed cdbs from Build-Depends + field. + - debian/rules: changed from CDBS to DH. + + -- Joao Eriberto Mota Filho Tue, 01 Feb 2022 23:55:04 -0300 + glurp (0.12.3-1) unstable; urgency=medium * New upstream release (Closes: #333640, #379667, #385088, #359096, #581933). reverted: --- glurp-0.12.3/debian/compat +++ glurp-0.12.3.orig/debian/compat @@ -1 +0,0 @@ -5 diff -u glurp-0.12.3/debian/rules glurp-0.12.3/debian/rules --- glurp-0.12.3/debian/rules +++ glurp-0.12.3/debian/rules @@ -3,4 +3,4 @@ -include /usr/share/cdbs/1/rules/debhelper.mk -include /usr/share/cdbs/1/class/autotools.mk +%: + dh $@ diff -u glurp-0.12.3/debian/control glurp-0.12.3/debian/control --- glurp-0.12.3/debian/control +++ glurp-0.12.3/debian/control @@ -2,7 +2,7 @@ Section: x11 Priority: optional Maintainer: Stanislav Maslovski -Build-Depends: debhelper (>= 5), libgtk2.0-dev (>= 2.4), libglib2.0-dev (>= 2.4), libmpd-dev, cdbs +Build-Depends: debhelper-compat (= 13), libgtk2.0-dev (>= 2.4), libglib2.0-dev (>= 2.4), libmpd-dev Standards-Version: 3.8.4 Homepage: http://sourceforge.net/projects/glurp/
Bug#965431: bfbtester: diff for NMU version 2.0.1-7.2
Control: tags 965431 + patch Control: tags 965431 + pending Dear maintainer, I've prepared an NMU for bfbtester (versioned as 2.0.1-7.2) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer or cancel it. Regards, Eriberto diff -u bfbtester-2.0.1/debian/rules bfbtester-2.0.1/debian/rules --- bfbtester-2.0.1/debian/rules +++ bfbtester-2.0.1/debian/rules @@ -1,13 +1,4 @@ #!/usr/bin/make -f - -DEB_INSTALL_MANPAGES_bfbtester := debian/bfbtester.1 - -common-configure-impl:: - cd $(DEB_BUILDDIR); touch aclocal.m4 && touch Makefile.in && \ - touch src/Makefile.in && touch src/config.h.in && \ - touch src/bfbt/Makefile && touch configure - -include /usr/share/cdbs/1/class/autotools.mk -include /usr/share/cdbs/1/rules/debhelper.mk -include /usr/share/cdbs/1/rules/simple-patchsys.mk +%: + dh $@ diff -u bfbtester-2.0.1/debian/changelog bfbtester-2.0.1/debian/changelog --- bfbtester-2.0.1/debian/changelog +++ bfbtester-2.0.1/debian/changelog @@ -1,3 +1,20 @@ +bfbtester (2.0.1-7.2) unstable; urgency=medium + + * Non-maintainer upload. + * Using new DH level format. Consequently: + - debian/compat: removed. + - debian/control: changed from 'debhelper' to 'debhelper-compat' in +Build-Depends field and bumped level to 13. + - Closes: #965431 + * Dropped CDBS in favor of the debhelper to allow the build system to use +DH level greater than 11. Consequently: + - debian/control: removed no longer needed cdbs and autotools-dev from +Build-Depends field. + - debian/manpages: created to install the manpage. + - debian/rules: changed from CDBS to DH. + + -- Joao Eriberto Mota Filho Fri, 28 Jan 2022 22:14:01 -0300 + bfbtester (2.0.1-7.1) unstable; urgency=high * Non-maintainer upload. diff -u bfbtester-2.0.1/debian/control bfbtester-2.0.1/debian/control --- bfbtester-2.0.1/debian/control +++ bfbtester-2.0.1/debian/control @@ -2,7 +2,7 @@ Section: utils Priority: optional Maintainer: Uwe Hermann -Build-Depends: cdbs, debhelper (>= 5), autotools-dev +Build-Depends: debhelper-compat (= 13) Standards-Version: 3.7.2 Package: bfbtester reverted: --- bfbtester-2.0.1/debian/compat +++ bfbtester-2.0.1.orig/debian/compat @@ -1 +0,0 @@ -5 only in patch2: unchanged: --- bfbtester-2.0.1.orig/debian/manpages +++ bfbtester-2.0.1/debian/manpages @@ -0,0 +1 @@ +debian/bfbtester.1
Bug#1002213: dmitry: diff for NMU version 1.3a-1.2
Control: tags 1002213 + patch Control: tags 1002213 + pending Dear maintainer, I've prepared an NMU for dmitry (versioned as 1.3a-1.2) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer or cancel the upload. Regards, Eriberto diff -u dmitry-1.3a/debian/changelog dmitry-1.3a/debian/changelog --- dmitry-1.3a/debian/changelog +++ dmitry-1.3a/debian/changelog @@ -1,3 +1,19 @@ +dmitry (1.3a-1.2) unstable; urgency=medium + + * Non-maintainer upload. + * Using new DH level format. Consequently: + - debian/compat: removed. + - debian/control: changed from 'debhelper' to 'debhelper-compat' in +Build-Depends field and bumped level to 13. + - Closes: #1002213 + * Dropped CDBS in favor of the debhelper to allow the build system to use +DH level greater than 11. Consequently: + - debian/control: removed no longer needed cdbs and autotools-dev from +Build-Depends field. + - debian/rules: changed from CDBS to DH. + + -- Joao Eriberto Mota Filho Fri, 28 Jan 2022 21:25:23 -0300 + dmitry (1.3a-1.1) unstable; urgency=medium * Non-maintainer upload. reverted: --- dmitry-1.3a/debian/compat +++ dmitry-1.3a.orig/debian/compat @@ -1 +0,0 @@ -5 diff -u dmitry-1.3a/debian/control dmitry-1.3a/debian/control --- dmitry-1.3a/debian/control +++ dmitry-1.3a/debian/control @@ -2,7 +2,7 @@ Section: net Priority: extra Maintainer: Runa Sandvik -Build-Depends: cdbs, debhelper (>= 7), autotools-dev +Build-Depends: debhelper-compat (= 13) Standards-Version: 3.8.0 Homepage: http://www.mor-pah.net/index.php?file=projects/dmitry diff -u dmitry-1.3a/debian/rules dmitry-1.3a/debian/rules --- dmitry-1.3a/debian/rules +++ dmitry-1.3a/debian/rules @@ -5,5 +5,5 @@ # Workaround for #957142 export DEB_CFLAGS_MAINT_APPEND = -fcommon -include /usr/share/cdbs/1/rules/debhelper.mk -include /usr/share/cdbs/1/class/autotools.mk +%: + dh $@
Bug#1004019: Should forensics-extra drop the dependendency on smb-nat?
Em qua., 19 de jan. de 2022 às 09:48, Adrian Bunk escreveu: > > Package: forensics-extra > Version: 2.34 > Severity: serious > Control: block 1004018 by -1 > > Does the 25 year old smb-nat provide any functionality that is > not also provided by Samba tools (that were originally written > by the same author)? > Hi Adrian, Thanks for your tip. I will remove this package from forensics-extra. Cheers, Eriberto
Bug#998358: Subject: grepmail: autopkgtest doesn't do anything
Em qua., 10 de nov. de 2021 às 18:55, Paul Gevers escreveu: > > Hi Eriberto, > > On Tue, 2 Nov 2021 19:57:37 -0300 Eriberto wrote: > > ow, Marcos will package the new upstream > > release and he will fix this mistake. In a final action, he will send > > a SPU to fix a specific issue. > > Please be aware that grepmail will be removed from testing in 7 days if > the issue isn't fixed. Obviously, the package can come back later too, > but just so you know. Thanks Paul. Marcos is a bit busy these days, so I will fix this issue now. Regards, Eriberto
Bug#998358: Subject: grepmail: autopkgtest doesn't do anything
Thanks a lot Paul. Really, in our machines the package is built and Makefile exists. I need to check some packages of mine. I think there are some tests around grepmail in upstream source. However, don't worry because this upload was a first work. Now, Marcos will package the new upstream release and he will fix this mistake. In a final action, he will send a SPU to fix a specific issue. Regards, Eriberto
Bug#978883: pnscan: ftbfs with autoconf 2.70
Control: tags 978883 unreproducible moreinfo Control: severity 978883 important Hi Matthias, I can't reproduce it in a fresh jail with autoconf 2.70/2.71 and GCC-10/11. I tested this package and 32 other packages with the same bug. I wasn't able to reproduce this issue in 18 packages. Maybe it is a failure in a robot. This issue is causing AUTORM in forensics-all and forensics-extra. Can you recheck? As an additional information, the package builds twice. Regards, Eriberto
Bug#978906: tcpxtract: ftbfs with autoconf 2.70
Control: tags 978906 unreproducible moreinfo Control: severity 978906 important Hi Matthias, I can't reproduce it in a fresh jail with autoconf 2.70/2.71 and GCC-10/11. I tested this package and 32 other packages with the same bug. I wasn't able to reproduce this issue in 18 packages. Maybe it is a failure in a robot. This issue is causing AUTORM in forensics-all and forensics-extra. Can you recheck? Regards, Eriberto
Bug#978905: tcpreplay: ftbfs with autoconf 2.70
Em qua., 25 de ago. de 2021 às 06:30, Christoph Biedl escreveu: > > Control: tags 978905 unreproducible moreinfo > > Matthias Klose wrote... > > > The package fails to build in a test rebuild on at least amd64 with > > autoconf 2.70, but succeeds to build with autoconf 2.69. The > > severity of this report will be raised before the bookworm release, > > so nothing has to be done for the bullseye release. > > Now looking into this, I cannot reproduce the issue in a pure Debian > build chroot, both usrmerged and non-usrmerged (in case that ever > matters). Indeed. The same case for pnscan and tcpxtract, both causing AUTORM for forensics-all and forensics-extra. Yesterday I tested 33 packages. I wasn't able to reproduce the issue in 18 packages. Regards, Eriberto
Bug#988254: FTBFS: Missing build dependency on txt2man
Control: severity 988254 normal Control: tags 988254 moreinfo unreproducible Em sáb., 8 de mai. de 2021 às 18:21, Wyatt Ward escreveu: > > Package: axel > Version: 2.17.10-2 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > > Dear Maintainer, > > When building axel from sources (with dpkg-buildpackage), the build fails > partway through unless txt2man is installed. txt2man is not currently listed > under the 'Build-Depends' field in debian/control. > > After manually installing txt2man, the build completes normally. > > I was building it on my powerbook (powerpc), but have also noticed this on one > of my amd64 machines (which I am sending this message from, hence the 'built > successfully in the past' message). > > This is likely my first Debian bug report, so I apologise in advance if I did > this wrong. I am letting 'reportbug' determine the severity but I don't > personally see it as a huge deal. If it's actually a policy violation, then I > guess that's why. > > Errors: > > /bin/bash: line 2: txt2man: command not found > make[3]: *** [Makefile:1146: doc/axel.1] Error 1 > make[3]: Leaving directory '/home/wyatt/development/axel/axel-git-debian' > make[2]: *** [Makefile:676: all-recursive] Error 1 > make[2]: Leaving directory '/home/wyatt/development/axel/axel-git-debian' > make[1]: *** [Makefile:452: all] Error 2 > make[1]: Leaving directory '/home/wyatt/development/axel/axel-git-debian' > dh_auto_build: error: make -j1 returned exit code 2 > make: *** [debian/rules:7: binary] Error 2 > dpkg-buildpackage: error: debian/rules binary subprocess returned exit > status 2 Hi Wyatt , Thanks for your message. axel 2.17.10-2 arrived in unstable on 2021-04-01 and it was successfully built by all supported architectures in Debian[1]. I did a new check now in my jail and all right in the axel. Considering it, I am sure the problem is on your side. Please, describe step to step all your procedures to build, starting with the source acquisition, and I will be able to point the cause of the failure. [1] https://buildd.debian.org/status/package.php?p=axel Best regards, Eriberto
Bug#986246: axel: flaky autopkgtest (on ci.d.n arm64) due to output on stderr: Connection gone.
Hi Paul, Em qui., 1 de abr. de 2021 às 10:24, Paul Gevers escreveu: > > Your package has an autopkgtest, great. However, I looked into > the history of your autopkgtest [1] and I noticed it fails regularly on > arm64. I have copied some of the output below. Can > you please look into it and fix it? Either suppress this particular case > of output to stderr if you still want to catch the rest, or add an > allow-stderr restriction to your test cases. Thanks a lot for your help. I decided to add allow-stderr in some tests. Regards, Eriberto
Bug#984647: forensics-extra's autopkg tests always fail on 32bit archs
Hi Matthias, Thanks a lot for your report. This issue was identificated in 2.28 version by me. I wrote in file list-of-packages-extra: -stegosuite FED +stegosuite FGR # FIXME, dependencies not available for i386 in autopkgtest In other words, I moved stegosuite from Depends (in forensics-extra) to Recommends (in forensics-extra-gui). However, because of a mistake of mine, a new debian/control file wasn't generated by gen-control.sh command. I will release the revision 2.29 to fix it. Thanks again. Eriberto
Bug#979978: lime-forensics-dkms: unable to make or make install due to error set_fs
Thanks a lot Gregory and Paul. I will use a PR from upstream site[1]. I tested this patch and it works fine. The patch used in Ubuntu seems a bit wrong[2]. [1] https://github.com/504ensicsLabs/LiME/pull/85 [2] https://github.com/504ensicsLabs/LiME/pull/83 Cheers, Eriberto Em ter., 12 de jan. de 2021 às 11:26, Paul Wise escreveu: > > Control: severity -1 serious > Control: tags -1 - ftbfs > Control: tags -1 + patch > > On Tue, 12 Jan 2021 09:00:57 -0500 Gregory Lamarche wrote: > > >* What was the outcome of this action? instead of building the modules > > it just errors out and gives error > > It looks like Ubuntu have a patch for this: > > https://patches.ubuntu.com/l/lime-forensics/lime-forensics_1.9.1-1ubuntu1.patch > > -- > bye, > pabs > > https://wiki.debian.org/PaulWise
Bug#969841: mac-robber: autopkgtest should be marked superficial
Thank you Samuel. In my personal opinion, this bug is not serious. So, I will set it as "normal" soon. I will wait for forensics-samples (in NEW) to fix this bug. Regards, Eriberto
Bug#970473: libgs9-common: Fails to install
Package: libgs9-common Version: 9.53.1~dfsg-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: eribe...@debian.org Dear Maintainer, When trying to install libgs9-common in Sid, I got the following message: The following packages have unmet dependencies: libgs9-common : Depends: fonts-urw-base35 (< 20170801.1.0~) but 20200910-1 is to be installed Recommends: fonts-droid-fallback but it is not going to be installed E: Unable to correct problems, you have held broken packages. The cause is today fonts-urw-base35 20200910-1 arrived to Sid[1]. [1] https://tracker.debian.org/news/1176330/accepted-fonts-urw-base35-20200910-1-source-into-unstable/ I think a re-upload of ghostscript will fix the problem. Best regards, Eriberto
Bug#969835: iwatch: autopkgtest should be marked superficial
Please, can you explain why this bug is marked as serious? Regards, Eriberto
Bug#957657: packeth: diff for NMU version 1.6.5-2.1
Control: tags 957657 + patch Control: tags 957657 + pending Dear maintainer, I've prepared an NMU for packeth (versioned as 1.6.5-2.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel or delay it longer. Regards. diff -Nru packeth-1.6.5/debian/changelog packeth-1.6.5/debian/changelog --- packeth-1.6.5/debian/changelog 2011-09-13 10:10:02.0 -0300 +++ packeth-1.6.5/debian/changelog 2020-08-20 15:05:18.0 -0300 @@ -1,3 +1,11 @@ +packeth (1.6.5-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * debian/rules: added -fcommon to CFLAGS as a workaround +to fix a FTBFS with GCC-10. (Closes: #957657) + + -- Joao Eriberto Mota Filho Thu, 20 Aug 2020 15:05:18 -0300 + packeth (1.6.5-2) unstable; urgency=low * Fix FTBFS because of wrong link order, thanks to Colin Watson diff -Nru packeth-1.6.5/debian/rules packeth-1.6.5/debian/rules --- packeth-1.6.5/debian/rules 2011-09-13 10:10:02.0 -0300 +++ packeth-1.6.5/debian/rules 2020-08-20 15:05:18.0 -0300 @@ -4,7 +4,7 @@ # Uncomment this to turn on verbose mode. #export DH_VERBOSE=1 -export CFLAGS = -Wall -g -Wall -Wunused -Wmissing-prototypes -Wmissing-declarations +export CFLAGS = -Wall -g -Wall -Wunused -Wmissing-prototypes -Wmissing-declarations -fcommon export LDFLAGS = -Wl,-z,defs -Wl,--as-needed override_dh_auto_install:
Bug#957219: foremost: diff for NMU version 1.5.7-9.1
Glad to help! Em qui., 20 de ago. de 2020 às 12:24, Raúl Benencia escreveu: > > Hi Joao, > > This is perfect. Thanks for taking care of it. > > On Wed, Aug 19, 2020 at 03:52:30PM -0300, Joao Eriberto Mota Filho wrote: > > Control: tags 957219 + patch > > Control: tags 957219 + pending > > > > Dear maintainer, > > > > I've prepared an NMU for foremost (versioned as 1.5.7-9.1) and > > uploaded it to DELAYED/2. Please feel free to tell me if I > > should cancel or delay it longer. > > > > Regards. > > > > diff -Nru foremost-1.5.7/debian/changelog foremost-1.5.7/debian/changelog > > --- foremost-1.5.7/debian/changelog 2019-06-12 12:08:06.0 -0300 > > +++ foremost-1.5.7/debian/changelog 2020-08-19 15:38:47.0 -0300 > > @@ -1,3 +1,11 @@ > > +foremost (1.5.7-9.1) unstable; urgency=medium > > + > > + * Non-maintainer upload. > > + * debian/rules: added DEB_CFLAGS_MAINT_APPEND variable as a workaround > > to fix > > +a FTBFS with GCC-10. (Closes: #957219) > > + > > + -- Joao Eriberto Mota Filho Wed, 19 Aug 2020 > > 15:38:47 -0300 > > + > > foremost (1.5.7-9) unstable; urgency=medium > > > >* Fix extra byte at the tail of recovered zip files if -t all is > > diff -Nru foremost-1.5.7/debian/rules foremost-1.5.7/debian/rules > > --- foremost-1.5.7/debian/rules 2018-06-11 02:27:20.0 -0300 > > +++ foremost-1.5.7/debian/rules 2020-08-19 15:38:47.0 -0300 > > @@ -5,6 +5,9 @@ > > #export DH_VERBOSE=1 > > export DEB_BUILD_MAINT_OPTIONS=hardening=+all > > > > +# Workaround for #957219 > > +export DEB_CFLAGS_MAINT_APPEND = -fcommon > > + > > %: > > dh $@ > >
Bug#957219: foremost: diff for NMU version 1.5.7-9.1
Control: tags 957219 + patch Control: tags 957219 + pending Dear maintainer, I've prepared an NMU for foremost (versioned as 1.5.7-9.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel or delay it longer. Regards. diff -Nru foremost-1.5.7/debian/changelog foremost-1.5.7/debian/changelog --- foremost-1.5.7/debian/changelog 2019-06-12 12:08:06.0 -0300 +++ foremost-1.5.7/debian/changelog 2020-08-19 15:38:47.0 -0300 @@ -1,3 +1,11 @@ +foremost (1.5.7-9.1) unstable; urgency=medium + + * Non-maintainer upload. + * debian/rules: added DEB_CFLAGS_MAINT_APPEND variable as a workaround to fix +a FTBFS with GCC-10. (Closes: #957219) + + -- Joao Eriberto Mota Filho Wed, 19 Aug 2020 15:38:47 -0300 + foremost (1.5.7-9) unstable; urgency=medium * Fix extra byte at the tail of recovered zip files if -t all is diff -Nru foremost-1.5.7/debian/rules foremost-1.5.7/debian/rules --- foremost-1.5.7/debian/rules 2018-06-11 02:27:20.0 -0300 +++ foremost-1.5.7/debian/rules 2020-08-19 15:38:47.0 -0300 @@ -5,6 +5,9 @@ #export DH_VERBOSE=1 export DEB_BUILD_MAINT_OPTIONS=hardening=+all +# Workaround for #957219 +export DEB_CFLAGS_MAINT_APPEND = -fcommon + %: dh $@
Bug#963154: nmapsi4: Must not be arch:any
Em sáb., 20 de jun. de 2020 às 10:00, Adrian Bunk escreveu: > > There are plenty of packages in the archive whose build dependencies > cannot be fulfilled on all release architectures. > > This is not a problem. Ok, thanks Adrian. I fixed forensics-all, affected by this change. Regards, Eriberto
Bug#963154: nmapsi4: Must not be arch:any
Package: nmapsi4
Version: 0.5~alpha2-1
Severity: serious
Tags: ftbfs patch
Justification: fails to build from source (but built successfully in the past)
Dear Maintainer,
nmapsi4 fails to build from source in several architectures since 0.5~alpha2-1
revision.
nmapsi4 build depends of qtwebengine5-dev. Since 5.9.1+dfsg-5 revision, released
in 30 Sep 2017, qtwebengine5-dev is only available for amd64, arm64, armhf, i386
and mipsel. Consequently, now nmapsi4 FTBFS in armel, mips64el, ppc64el, s390x,
alpha, hppa, hurd-i386, ia64, m68k, powerpc, ppc64, riscv64, sh4, sparc64 and
x32.
The following patch fixes the FTBFS in nmapsi4:
diff -Nru nmapsi4-0.5~alpha2/debian/control nmapsi4-0.5~alpha2/debian/control
--- nmapsi4-0.5~alpha2/debian/control 2020-05-22 12:50:04.0 -0300
+++ nmapsi4-0.5~alpha2/debian/control 2020-06-19 14:33:47.0 -0300
@@ -11,7 +11,7 @@
Rules-Requires-Root: no
Package: nmapsi4
-Architecture: any
+Architecture: amd64 arm64 armhf i386 mipsel
Depends: ${shlibs:Depends}, ${misc:Depends}, nmap, bind9-dnsutils
Description: graphical interface to nmap, the network scanner
NmapSI4 is a complete Qt-based Gui with the design goal to provide a complete
Regards,
Eriberto
Bug#960899: [Python-modules-team] Bug#960899: paramiko: diff for NMU version 2.7.1-1.1
Em sáb., 13 de jun. de 2020 às 01:21, Sandro Tosi escreveu: > > On Wed, Jun 10, 2020 at 11:45 AM César Túlio wrote: > > > > Control: tags 960899 + patch > > Control: tags 960899 + pending > > > > Dear maintainer, > > > > I've prepared an NMU for paramiko (versioned as 2.7.1-1.1) and > > uploaded it to DELAYED/5. Please feel free to tell me if I > > should delay it longer or cancel the NMU. > > hold off with this please; i'd much rather for you to submit an MR at > https://salsa.debian.org/python-team/modules/paramiko Hi Sandro, It is part of a local sprint. I am cancelling the upload now. Regards, Eriberto
Bug#962673: cunit: autopkgtest failure: stdio.h: No such file or directory
Source: cunit Version: 2.1-3-dfsg-2.2 Severity: serious Autopkgtest fails since last NMU with the following messages: autopkgtest [17:33:49]: test test.sh: [--- debian/tests/test.c:1:10: fatal error: stdio.h: No such file or directory 1 | #include | ^ compilation terminated. /tmp/autopkgtest-lxc.m92mckta/downtmp/build.vSN/src/debian/tests/test.sh: 8: /tmp/autopkgtest-lxc.m92mckta/downtmp/autopkgtest_tmp/test: not found debian/tests/test.c:1:10: fatal error: stdio.h: No such file or directory 1 | #include | ^ compilation terminated. /tmp/autopkgtest-lxc.m92mckta/downtmp/build.vSN/src/debian/tests/test.sh: 8: /tmp/autopkgtest-lxc.m92mckta/downtmp/autopkgtest_tmp/test: not found autopkgtest [17:33:49]: test test.sh: ---] autopkgtest [17:33:49]: test test.sh: - - - - - - - - - - results - - - - - - - - - - test.sh FAIL non-zero exit status 127 autopkgtest [17:33:50]: test test.sh: - - - - - - - - - - stderr - - - - - - - - - - debian/tests/test.c:1:10: fatal error: stdio.h: No such file or directory 1 | #include | ^ compilation terminated. /tmp/autopkgtest-lxc.m92mckta/downtmp/build.vSN/src/debian/tests/test.sh: 8: /tmp/autopkgtest-lxc.m92mckta/downtmp/autopkgtest_tmp/test: not found debian/tests/test.c:1:10: fatal error: stdio.h: No such file or directory 1 | #include | ^ compilation terminated. /tmp/autopkgtest-lxc.m92mckta/downtmp/build.vSN/src/debian/tests/test.sh: 8: /tmp/autopkgtest-lxc.m92mckta/downtmp/autopkgtest_tmp/test: not found autopkgtest [17:33:50]: summary test.sh FAIL non-zero exit status 127 The release team has announced [1] that failing autopkgtest are now considered RC in testing. The full log from autopkgtest is availble here[2]. [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html [2] https://ci.debian.net/data/autopkgtest/unstable/amd64/c/cunit/5861880/log.gz Regards, Eriberto
Bug#962643: cunit: broken NMU does FTBFS
All right with build now! \o/ However, I can see the CI tests failing again and we will need a new NMU. We will work over it now (using Salsa to approve the local changes in tests). I will open a bug. Em qui., 11 de jun. de 2020 às 13:22, Adrian Bunk escreveu: > > Something unrelated missing on your list: > debdiff between previous and current binary packages. > Both file differences and dependency differences are worth checking. Added, thanks! > > > We are in a local sprint. We are monitoring all builds to prevent > > issues. We are 17 people working around several issues. > >... > > Ah, I already wondered about all the Brazilian names in > https://ftp-master.debian.org/deferred.html Yes. We are 14 collaborators and 3 sponsors. > I hope I did not come across as unfriendly, more than 100k unwanted LOC > in the debdiff was just a shock while still drinking my wake-up black tea. I understand you first impressions and I know your nice work around Debian. You're welcome. Cheers, Eriberto
Bug#962643: cunit: broken NMU does FTBFS
Hi Adrian, how are you? Em qui., 11 de jun. de 2020 às 03:15, Adrian Bunk escreveu: > > On Thu, Jun 11, 2020 at 08:46:23AM +0300, Adrian Bunk wrote: > >... > > The diffstat of this NMU is > > 510 files changed, 139791 insertions(+), 3 deletions(-) > > > > It is the responsibility of the sponsor (Cc'ed) to verify that > > sponsored uploads are not broken: > > https://wiki.debian.org/DebianMentorsFaq#What_is_the_process_for_sponsoring_a_package.3F > > I have to take that back, it is actually likely that this went wrong on > the sponsor side due to verifying the package: > > The debdiff in #960715 looks OK. > > Building a source package for upload after having done a testbuild > can cause this kind of problems, when the source tree is not clean > many unwanted changes might end up in the new source package. Thanks a lot for your comments. The problem is caused by several files in directories created by package inside debian/ (build, build-ncurses e tmp-ncurses) and not cleaned by dh_clean. Initially, Regis did a fix for this but I asked him to remove it because an NMU should not modify some things in third-party packages (cleanup wasn't a RC target). So, I did a double check using my sponsor checklist[1], I ran debuild and cowbuilder. After this I did a debuild -S and the trash inside debian/ was sent. Sorry for this. [1] http://bit.ly/pkgcheck We are in a local sprint. We are monitoring all builds to prevent issues. We are 17 people working around several issues. Don't worry because this issue will be fixed today with a NMU without delay and with an override_dh_autoclean. Thanks a lot for your help. Cheers, Eriberto
Bug#831104: xevil: diff for NMU version 2.02r2-10.1
Control: tags 831104 + pending
Dear maintainer,
I've prepared an NMU for xevil (versioned as 2.02r2-10.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer or cancel the NMU.
Regards,
Eriberto
--- xevil-2.02r2/debian/changelog
+++ xevil-2.02r2/debian/changelog
@@ -1,3 +1,11 @@
+xevil (2.02r2-10.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fixed FTBFS with GCC 6 and higher. Thanks to Javier Serrano
+Polo . (Closes: #831104)
+
+ -- Joao Eriberto Mota Filho Sun, 07 Jun 2020 02:11:06
-0300
+
xevil (2.02r2-10) unstable; urgency=low
* Fixed bug that sometimes prevented X resources from being read properly.
diff -u xevil-2.02r2/cmn/utils.h xevil-2.02r2/cmn/utils.h
--- xevil-2.02r2/cmn/utils.h
+++ xevil-2.02r2/cmn/utils.h
@@ -98,11 +98,11 @@
#define MSEC_PER_CLOCK (1.0e3 / CLOCKS_PER_SEC)
#endif
-#ifndef max
-#define max(a,b) (ab ? b : a)
+#ifndef MIN
+#define MIN(a,b) (a>b ? b : a)
#endif
#if X11
diff -u xevil-2.02r2/cmn/game.cpp xevil-2.02r2/cmn/game.cpp
--- xevil-2.02r2/cmn/game.cpp
+++ xevil-2.02r2/cmn/game.cpp
@@ -577,7 +577,7 @@
assert(maximums[weapons[n]->classId] == 0);
// Don't allow objectWorldPercent values that are too small.
- float objWPercent = (float)max(weapons[n]->objectWorldPercent,
+ float objWPercent = (float)MAX(weapons[n]->objectWorldPercent,
OBJECT_WORLD_PERCENT_MIN);
maximums[weapons[n]->classId] = (int)ceil(areaFactor * objWPercent);
@@ -590,7 +590,7 @@
for (n = 0; n < oItemsNum; n++) {
// Check not already set.
assert(maximums[oItems[n]->classId] == 0);
- float objWPercent = (float)max(oItems[n]->objectWorldPercent,
+ float objWPercent = (float)MAX(oItems[n]->objectWorldPercent,
OBJECT_WORLD_PERCENT_MIN);
maximums[oItems[n]->classId] = (int)ceil(areaFactor * objWPercent);
diff -u xevil-2.02r2/debian/changelog xevil-2.02r2/debian/changelog
Bug#962065: rdist: Non-free license
Package: rdist Version: 6.1.5 Severity: serious Tags: upstream Justification: Policy 2.1 The current version of rdist in Debian says in Copyright file and in every headers: /* * Copyright (c) 1992-1998 Michael A. Cooper. * This software may be freely used and distributed provided it is not * sold for profit or used in part or in whole for commercial gain * without prior written agreement, and the author is credited * appropriately. */ /* * Copyright (c) 1983 Regents of the University of California. * All rights reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * 1. Redistributions of source code must retain the above copyright *notice, this list of conditions and the following disclaimer. * 2. Redistributions in binary form must reproduce the above copyright *notice, this list of conditions and the following disclaimer in the *documentation and/or other materials provided with the distribution. * 3. All advertising materials mentioning features or use of this software *must display the following acknowledgement: * This product includes software developed by the University of * California, Berkeley and its contributors. * 4. Neither the name of the University nor the names of its contributors *may be used to endorse or promote products derived from this software *without specific prior written permission. * * THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE * ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. */ It sounds like a multi-licensed source code, as "Special and BSD-4-Clause". The Special slice (Copyright (c) 1992-1998 Michael A. Cooper) is non-DFSG compliant. Regards, Eriberto -- System Information: Debian Release: 10.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-9-amd64 (SMP w/4 CPU cores) 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 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages rdist depends on: ii libc6 2.28-10 rdist recommends no packages. rdist suggests no packages.
Bug#955777: forensics-all: depends on neopi which was removed from unstable
Em sáb., 4 de abr. de 2020 às 17:59, Sebastian Ramacher escreveu: > > neopi was removed from unstable (see #955518). Please drop it from > forensics-all's Depends. Thanks Sebastian! I will fix it today. Regards, Eriberto
Bug#951120: hydra: Non-free licence exception
Em qua., 12 de fev. de 2020 às 10:17, Raphael Hertzog escreveu: > > I'd rather convince upstream to fix this. I opened a ticket here: > https://github.com/vanhauser-thc/thc-hydra/issues/497 Is a good idea change the help too. I also saw the following message: $ hydra -h Hydra v8.8 (c) 2019 by van Hauser/THC - Please do not use in military or secret service organizations, or for illegal purposes. Syntax: hydra [[[-l LOGIN|-L FILE] [-p PASS|-P FILE]] | [-C FILE]] [-e nsr] [-o FILE] [-t TASKS] [-M FILE [-T TASKS]] [-w TIME] [-W TIME] [-f] [-s PORT] [-x MIN:MAX:CHARSET] [-c TIME] [-ISOuvVd46] [service://server[:PORT][/OPT]] Cheers, Eriberto
Bug#946906: autoremoval looking at Recommends field
Package: release.debian.org Severity: serious >From https://udd.debian.org/cgi-bin/autoremovals.cgi: forensics-all: buggy deps aircrack-ng, flagged for removal in 18 days >From https://tracker.debian.org/pkg/forensics-all: Version 3.12 of forensics-all is marked for autoremoval from testing on Sat 04 Jan 2020. It depends (transitively) on aircrack-ng, affected by #936113. You should try to prevent the removal by fixing these RC bugs. However, since version 3.11 aircrack-ng is a recommended package, not a dependency. From Sid: $ apt-cache depends forensics-all | grep aircrack Recommends: aircrack-ng Thanks in advance. Regards, Eriberto -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) 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 (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect
Bug#945234: cupp: Renaming cupp3 to cupp breaks Debian Sid/Bullseye repository
Hi Marcio, Em qui., 21 de nov. de 2019 às 14:10, Marcio Souza escreveu: > > Em 21/11/2019 13:50, Joao Eriberto Mota Filho escreveu: > > Source: cupp > > Version: 0.0+20160624.git07f9b8-1 > > Severity: normal > > > > Dear maintainer, > Hi Eriberto > > > After renaming cupp3 to cupp suddenly and without coordinate with other > > maintainers, forensics-extra packages (and maybe others) was affected. > > If it is a forced needed transition, please coordinate the action before > > make it. > Sorry for this, I should have coordinated it. > > > If you only need rename the package from now on because a light reason > > as Python 2 removing, please follow these instructions[1]. IMO, this is > > the solution for cupp. Note that you package will arrives to NEW queue. > The cupp source package generated two binaries: cupp and cupp3, respectively > the version for python2 and python3. The new upstream version of cupp > [1] removed > the python2 implementation, so the cupp3 lost its purpose, as we started > having only the python3 version. > > So in debian release [2], I removed the cupp3 of cupp source package, I > don't rename the package. Sorry, I didn't make myself understood. In other words, is not recommendable remove a package from Debian without coordinate it. Considering that you removed cupp3 suddenly, the best way to fix it without disrupt other packages/users is adopt the same procedure as renaming a package (this procedure is also used to rename but it not just to rename). > Could you modify the dependencies of forensics-extra to use cupp package > instead of cupp3? [3]. Sure, I will do it soon. Regards, Eriberto
Bug#866419: cfv: diff for NMU version 1.18.3-2.1
Control: tags 866419 + patch
Control: tags 866419 + pending
Dear maintainer,
I've prepared an NMU for cfv (versioned as 1.18.3-2.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru cfv-1.18.3/debian/changelog cfv-1.18.3/debian/changelog
--- cfv-1.18.3/debian/changelog 2012-05-10 15:43:38.0 -0300
+++ cfv-1.18.3/debian/changelog 2019-07-24 12:55:20.0 -0300
@@ -1,3 +1,14 @@
+cfv (1.18.3-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix a FTBFS: (Closes: #866419)
+ - debian/control: changed from python-imaging to python-pil in
+Suggests field. Thanks to David Gnedt .
+ - debian/patches/10_fix-python.patch: created to fix PIL namespace.
+Thanks to David Gnedt .
+
+ -- Joao Eriberto Mota Filho Wed, 24 Jul 2019
12:55:20 -0300
+
cfv (1.18.3-2) unstable; urgency=low
* Package cleanup below by Jari Aalto - thanks!
diff -Nru cfv-1.18.3/debian/control cfv-1.18.3/debian/control
--- cfv-1.18.3/debian/control 2012-05-10 15:36:48.0 -0300
+++ cfv-1.18.3/debian/control 2019-07-24 12:55:20.0 -0300
@@ -9,7 +9,7 @@
Package: cfv
Architecture: all
Depends: ${python:Depends}, ${misc:Depends}
-Suggests: python-imaging, bittorrent | bittornado
+Suggests: python-pil, bittorrent | bittornado
Description: versatile file checksum creator and verifier
cfv is a utility to test and create a wide range of checksum
verification files. It currently supports testing and creating
diff -Nru cfv-1.18.3/debian/patches/10_fix-python.patch
cfv-1.18.3/debian/patches/10_fix-python.patch
--- cfv-1.18.3/debian/patches/10_fix-python.patch 1969-12-31
21:00:00.0 -0300
+++ cfv-1.18.3/debian/patches/10_fix-python.patch 2019-07-24
12:55:20.0 -0300
@@ -0,0 +1,26 @@
+Description: fix PIL namespace
+Author: David Gnedt
+Bug-Debian: https://bugs.debian.org/866419
+Last-Update: 2019-03-13
+Index: cfv-1.18.3/cfv
+===
+--- cfv-1.18.3.orig/cfv
cfv-1.18.3/cfv
+@@ -1837,7 +1837,7 @@ def getimagedimensions(filename):
+ if filename == '':
+ return '0','0'
+ try:
+- import Image
++ from PIL import Image
+ im1=Image.open(filename)
+ return map(str, im1.size)
+ except (ImportError, IOError):
+@@ -1910,7 +1910,7 @@ class JPEGSheriff_CRC(ChksumType, CRC_Mi
+ file.write('Generated at: %s\n'%time.strftime('%a, %d
%b %Y %H:%M:%S',time.gmtime(time.time(
+ file.write('Find it at: http://cfv.sourceforge.net/\n\n')
+ try:
+- import Image
++ from PIL import Image
+ self.use_dimensions=1 should this be made
optional somehow?
+ except ImportError:
+ self.use_dimensions=0
diff -Nru cfv-1.18.3/debian/patches/series cfv-1.18.3/debian/patches/series
--- cfv-1.18.3/debian/patches/series2012-05-10 15:36:48.0 -0300
+++ cfv-1.18.3/debian/patches/series2019-07-24 12:55:20.0 -0300
@@ -1 +1,2 @@
# 01-color.patch
+10_fix-python.patch
Bug#932796: Non-DFSG license in dyndns.pl file
Package: dyndns Version: 2016.1021-3 Severity: serious Tags: upstream When searching for a license inside dyndns.pl, I found the information shown below: #!/usr/bin/perl # # Copyright # # Copyright (C) 1999-2016 Jari Aalto # # License # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version. [...] [...] The last block says about a PROPRIETARY source code. This notice was shown two times in dyndns main file. Regards, Eriberto -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64)
Bug#928728: testssl.sh: missing dependencies
Em sex, 17 de mai de 2019 às 20:43, Eriberto Mota escreveu: > > So, package needs bsdmailutils and procps. > s/bsdmailutils/bsdmainutils/
Bug#928728: testssl.sh: missing dependencies
Hi Lee, Thanks for your report. I can confirm it: Fatal error: Neither "dig", "host", "drill" or "nslookup" is present So, package needs dnsutils | ldnsutils (dnsutils also provide host). /usr/bin/testssl: line 8865: hexdump: command not found /usr/bin/testssl: line 1236: ps: command not found So, package needs bsdmailutils and procps. I will fix it. Regards, Eriberto
Bug#926335: closed by Joao Eriberto Mota Filho (Bug#926335: fixed in forensics-extra 2.8)
Em qui, 4 de abr de 2019 às 05:35, Andreas Beckmann escreveu: > > Thanks. > > Unblock request filed: #926374 Thanks a lot Andreas! Eriberto
Bug#919850: python3-link-grammar: broken symlink: /usr/lib/python3.7/site-packages/linkgrammar/_clinkgrammar.so -> _clinkgrammar.so.5.5.1
Hi, After dh_install: python3-link-grammar └── usr └── lib └── python3.7 └── site-packages ├── linkgrammar │ ├── clinkgrammar.py │ ├── _clinkgrammar.so -> _clinkgrammar.so.5.5.1 │ ├── _clinkgrammar.so.5 -> _clinkgrammar.so.5.5.1 │ ├── _clinkgrammar.so.5.5.1 │ ├── __init__.py │ ├── linkgrammar.py │ └── __pycache__ │ ├── clinkgrammar.cpython-37.opt-1.pyc │ ├── clinkgrammar.cpython-37.pyc │ ├── __init__.cpython-37.opt-1.pyc │ ├── __init__.cpython-37.pyc │ ├── linkgrammar.cpython-37.opt-1.pyc │ └── linkgrammar.cpython-37.pyc └── linkgrammar.pth After dh_python3: python3-link-grammar └── usr ├── lib │ ├── python3 │ │ └── dist-packages │ │ ├── linkgrammar │ │ │ ├── clinkgrammar.py │ │ │ ├── _clinkgrammar.so.5.5.1 │ │ │ ├── __init__.py │ │ │ └── linkgrammar.py │ │ └── linkgrammar.pth │ └── python3.7 │ └── site-packages │ └── linkgrammar │ └── _clinkgrammar.so -> _clinkgrammar.so.5.5.1 So, the link was not moved or recreated by dh_python3. Eriberto
Bug#917898: libvisual-0.4-dev: Broken include path in pkg-config file
Hi Tim, Em seg, 31 de dez de 2018 às 11:54, Tim Müller escreveu: > > $ pkg-config --cflags libvisual-0.4 > -I/usr/include/libvisual-0.4 > > $ ls /usr/include/libvisual-0.4 > ls: cannot access '/usr/include/libvisual-0.4': No such file or directory > > Only /usr/include/libvisual exists. It's not clear to me why it was renamed, > having the major/API version in the subdirectory name is good practice, so > that in case a new version with a different API/ABI is made it can be > installed in parallel. I adopted libvisual some years ago. Originally, it was installing include files in '/usr/include/libvisual-0.4'. In november 2018, I created a test for autopkgtest (debian/tests/). The test called all .h files and failed because these headers called '/usr/include/libvisual'. So, I "fixed" the path for include files in 0.4.0-13 revision. I will revert this action and add a symlink to fix the problem without more noising. > In any case, this will cause everyone who uses this package via pkg-config > (e.g. gst-plugins-base) to FTBFS. > > Cheers > Tim Thanks! Cheers, Eriberto Hi Tim, I adopted
Bug#915431: dc3dd FTBFS with glibc 2.28
Em seg, 3 de dez de 2018 às 18:42, Adrian Bunk escreveu: > > Source: dc3dd > Version: 7.2.646-2 > Severity: serious > Tags: ftbfs > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dc3dd.html > > ... > freadahead.c: In function 'freadahead': > freadahead.c:69:3: error: #error "Please port gnulib freadahead.c to your > platform! Look at the definition of fflush, fread, ungetc on your system, > then report this to bug-gnulib." > #error "Please port gnulib freadahead.c to your platform! Look at the > definition of fflush, fread, ungetc on your system, then report this to > bug-gnulib." >^ > gcc -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -ffile-prefix-map=/build/1st/dc3dd-7.2.646=. -fstack-protector-strong > -Wformat -Werror=format-security -c -o full-read.o full-read.c > make[4]: *** [Makefile:1470: freadahead.o] Error 1 > > > See #915151 for background. > Hi all, I will apply the patch available here[1]. [1] https://aur.archlinux.org/packages/dc3dd/ Regards, Eriberto
Bug#915043: nikto: missing build on all
Em qui, 29 de nov de 2018 às 16:56, Vincent Bernat escreveu: > > ❦ 29 novembre 2018 16:51 -0200, Eriberto Mota : > > > I've prepared an NMU for nikto (versioned as 1:2.1.5-3.1) and > > uploaded it to DELAYED/10. Please feel free to tell me if I > > should delay it longer. > > Thanks. You can upload it right now if you want. Thanks! I will do it. Cheers, Eriberto
Bug#915043: nikto: missing build on all
Control: tags 915043 + patch Control: tags 915043 + pending Dear maintainer, I've prepared an NMU for nikto (versioned as 1:2.1.5-3.1) and uploaded it to DELAYED/10. Please feel free to tell me if I should delay it longer. Regards, Eriberto
