Bug#1052376: lxpanel: probably related to #1052050
Package: lxpanel Version: 0.10.1-4 Followup-For: Bug #1052376 Hey, similar issue here.. i think this is related to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052050 cheers, -- System Information: Debian Release: trixie/sid APT prefers experimental APT policy: (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 6.5.4-x64v3-xanmod1 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=el_GR.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) LSM: AppArmor: enabled Versions of packages lxpanel depends on: ii libasound2 1.2.10-1 ii libc62.37-10 ii libcairo21.17.8-3 ii libcurl3-gnutls 8.3.0-1 ii libfm-gtk3-4 1.3.2-4 ii libfm-modules1.3.2-4 ii libfm4 1.3.2-4 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1 ii libglib2.0-0 2.78.0-2 ii libgtk-3-0 3.24.38-5 ii libiw30 30~pre9-14 ii libkeybinder-3.0-0 0.3.2-1.1 ii libmenu-cache3 1.1.0-1.1 ii libpango-1.0-0 1.51.0+ds-2 ii libwnck-3-0 43.0-3 ii libx11-6 2:1.8.6-1 ii libxml2 2.9.14+dfsg-1.3 ii lxmenu-data 0.1.5-2.1 ii lxpanel-data 0.10.1-4 Versions of packages lxpanel recommends: ii dunst [notification-daemon] 1.9.2-1 ii libnotify-bin0.8.2-1 ii lxterminal [x-terminal-emulator] 0.4.0-2 ii mate-terminal [x-terminal-emulator] 1.26.1-1 ii notification-daemon 3.20.0-4+b1 ii pavucontrol 5.0-2 ii xkb-data 2.38-2 Versions of packages lxpanel suggests: ii chromium [www-browser]117.0.5938.62-1 ii firefox [www-browser] 117.0.1-1 ii librewolf [www-browser] 117.0-1 ii lynx [www-browser]2.9.0dev.12-1 ii vivaldi-stable [www-browser] 6.2.3105.48-1 -- no debconf information
Bug#999962: RFS to solve bug#999962 (silversearcher-ag: depends on obsolete pcre3 library)
Nicholas D Steeves writes: > I've moved this discussion from debian-emacsen to the relevant bug. > Please remove debian-emacsen from CC and add me to CC for all > follow-ups. > Dropped debian-emacsen@. > Manphiz writes: > >> Manphiz writes: >> >>> >>> Thanks Nicholas! I used licensecheck and checked manually and updated >>> d/copyright accordingly in my merge request[1]. PTAL, thanks! >>> >>> [1] https://salsa.debian.org/debian/silversearcher-ag/-/merge_requests/1 >> >> Friendly ping. > > haha @enable_pcre2_support.patch:L478 > > Thanks for adding some copyright info; this will cover a "patches > applied" view, but doesn't cover the "patches unapplied" source package > (orig.tar, debian.tar, dsc). If you manually evaluate the rules in > d/copyright you'll see that this patch becomes misattributed to the > debian/* holder, which gets even more confusing since you set yourself > as the patch author ;) Yes, I understand you synthesised commits, and > I'm fine with that, but please finish fixing up d/copyright. > Makes sense. Updated accordingly. > changelog: Please enclose "Closes: #62" in parentheses in order to > follow the style that is already in use by this package's maintainer; > it's technically still Majime Mizuno's package, after all. > Done. > Then finalise the changelog and build the package. > Done as well. > Finally, learn about what an "nmudiff" is, and file one at the relevant > bug. > To be careful I'd like to have you take another look before doing so[1] :) BTW, I'm not a DD or DMD yet so I'm probably not able to submit to delayed queue yet, right? > Thanks, > Nicholas > [1] https://salsa.debian.org/debian/silversearcher-ag/-/merge_requests/1/diffs -- Manphiz signature.asc Description: PGP signature
Bug#1052234: marked as done (FTBFS with OCaml 4.14.1)
Your message dated Fri, 22 Sep 2023 04:52:10 + with message-id and subject line Bug#1052234: fixed in ocaml-merlin 4.10-414-1 has caused the Debian Bug report #1052234, regarding FTBFS with OCaml 4.14.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1052234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052234 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ocaml-merlin Version: 4.7-413-4 Severity: important Tags: ftbfs User: debian-ocaml-ma...@lists.debian.org Usertags: ocaml-4.14.1-transition Dear Maintainer, Your package FTBFS with OCaml 4.14.1 with the following error: [...] dune build @all File "src/config/my_config.ml", line 7, characters 70-83: 7 | | `OCaml_4_10_0 | `OCaml_4_11_0 | `OCaml_4_12_0 | `OCaml_4_13_0 ] = `OCaml_4_14_0 ^ Error: This expression has type [> `OCaml_4_14_0 ] but an expression was expected of type [ `OCaml_4_02_0 | `OCaml_4_02_1 | `OCaml_4_02_2 | `OCaml_4_02_3 | `OCaml_4_03_0 | `OCaml_4_04_0 | `OCaml_4_05_0 | `OCaml_4_06_0 | `OCaml_4_07_0 | `OCaml_4_07_1 | `OCaml_4_08_0 | `OCaml_4_09_0 | `OCaml_4_10_0 | `OCaml_4_11_0 | `OCaml_4_12_0 | `OCaml_4_13_0 ] The second variant type does not allow tag(s) `OCaml_4_14_0 File "src/ocaml/preprocess/parser_raw.mly", line 846, characters 29-36: Warning: the token COMMENT is unused. File "src/ocaml/preprocess/parser_raw.mly", line 847, characters 30-39: Warning: the token DOCSTRING is unused. File "src/ocaml/preprocess/parser_raw.mly", line 849, characters 7-10: Warning: the token EOL is unused. File "src/ocaml/preprocess/parser_raw.mly", line 759, characters 7-22: Warning: the token GREATERRBRACKET is unused. ocamlmerlin.c: In function 'connect_socket.constprop': ocamlmerlin.c:262:40: warning: '%s' directive output may be truncated writing up to 4096 bytes into a region of size 102 [-Wformat-truncation=] 262 | snprintf(address.sun_path, 104, "./%s", socketname); |^~ ocamlmerlin.c:262:5: note: 'snprintf' output between 3 and 4099 bytes into a destination of size 104 262 | snprintf(address.sun_path, 104, "./%s", socketname); | ^~~ ocamlmerlin.c: In function 'start_server.constprop': ocamlmerlin.c:353:40: warning: '%s' directive output may be truncated writing up to 4096 bytes into a region of size 102 [-Wformat-truncation=] 353 | snprintf(address.sun_path, 104, "./%s", socketname); |^~ ocamlmerlin.c:353:5: note: 'snprintf' output between 3 and 4099 bytes into a destination of size 104 353 | snprintf(address.sun_path, 104, "./%s", socketname); | ^~~ ocamlmerlin.c:377:41: warning: 'snprintf' output may be truncated before the last format character [-Wformat-truncation=] 377 | snprintf(socket_path, PATHSZ, "%s/%s", path_socketdir(), socketname); | ^ ocamlmerlin.c:377:5: note: 'snprintf' output 2 or more bytes (assuming 4098) into a destination of size 4097 377 | snprintf(socket_path, PATHSZ, "%s/%s", path_socketdir(), socketname); | ^~~~ make[1]: *** [debian/rules:9: override_dh_auto_build] Error 1 make[1]: Leaving directory '/tmp/build/ocaml-merlin-4.7-413' make: *** [debian/rules:6: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Packages rebuilt with OCaml 4.14.1 are available at: http://ocaml.debian.net/transitions/ocaml-4.14.1/ Cheers, -- Stéphane --- End Message --- --- Begin Message --- Source: ocaml-merlin Source-Version: 4.10-414-1 Done: Julien Puydt We believe that the bug you reported is fixed in the latest version of ocaml-merlin, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1052...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Puydt (supplier of updated ocaml-merlin package) (This message was generated automatically at their request; if y
Processed: Bug#1042049 marked as pending in lintian
Processing control commands: > tag -1 pending Bug #1042049 [src:lintian] lintian: FTBFS: 3 tests failed Added tag(s) pending. -- 1042049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042049 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042049: marked as pending in lintian
Control: tag -1 pending Hello, Bug #1042049 in lintian 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/lintian/lintian/-/commit/0803577fdbecc26dcda6719789a55637cacedc34 Adapt groff 1.23 warning message (Closes: #1042049) (this message was generated automatically) -- Greetings https://bugs.debian.org/1042049
Bug#1036256: golang-github-pin-tftp: FTBFS in testing
On Mon, 18 Sep 2023 09:23:19 -0300 Thiago Andrade wrote: > I'm waiting for this upgrade. After I'll try to upgrade gobuster to > 3.6.0 version. Hello Thiago, the new package was uploaded and is now in unstable. However, after manually triggering the autopkgtests two times, I noticed that a test failed (2 times, on a different architecture each time, cf ppc64el and riscv64 logs at [1]). So it still looks like a test is flaky, or maybe there's a bug in the code. I pinged upstream to see if they can help [2]. Cheers, Arnaud -- [1] https://ci.debian.net/packages/g/golang-github-pin-tftp/ [2] https://github.com/pin/tftp/issues/87
Bug#1037607: marked as done (colobot: ftbfs with GCC-13)
Your message dated Fri, 22 Sep 2023 00:34:53 +
with message-id
and subject line Bug#1037607: fixed in colobot 0.2.0-2.1
has caused the Debian Bug report #1037607,
regarding colobot: ftbfs with GCC-13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1037607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037607
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:colobot
Version: 0.2.0-2
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/colobot_0.2.0-2_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html
[...]
| ^~~
/<>/src/common/resources/resourcemanager.cpp: In static member
function ‘static bool CResourceManager::RemoveLocation(const std::string&)’:
/<>/src/common/resources/resourcemanager.cpp:79:37: warning: ‘int
PHYSFS_removeFromSearchPath(const char*)’ is deprecated
[-Wdeprecated-declarations]
79 | if (!PHYSFS_removeFromSearchPath(location.c_str()))
| ~~~^~
/usr/include/physfs.h:878:17: note: declared here
878 | PHYSFS_DECL int PHYSFS_removeFromSearchPath(const char *oldDir)
| ^~~
/<>/src/common/resources/resourcemanager.cpp:81:104: warning:
‘const char* PHYSFS_getLastError()’ is deprecated [-Wdeprecated-declarations]
81 | GetLogger()->Error("Error while unmounting \"%s\": %s\n",
location.c_str(), PHYSFS_getLastError());
|
~~~^~
/usr/include/physfs.h:654:25: note: declared here
654 | PHYSFS_DECL const char *PHYSFS_getLastError(void) PHYSFS_DEPRECATED;
| ^~~
/<>/src/common/resources/resourcemanager.cpp: In static member
function ‘static bool CResourceManager::SetSaveLocation(const std::string&)’:
/<>/src/common/resources/resourcemanager.cpp:109:118: warning:
‘const char* PHYSFS_getLastError()’ is deprecated [-Wdeprecated-declarations]
109 | GetLogger()->Error("Error while setting save location to
\"%s\": %s\n", location.c_str(), PHYSFS_getLastError());
|
~~~^~
/usr/include/physfs.h:654:25: note: declared here
654 | PHYSFS_DECL const char *PHYSFS_getLastError(void) PHYSFS_DEPRECATED;
| ^~~
/<>/src/common/resources/resourcemanager.cpp: In static member
function ‘static bool CResourceManager::DirectoryExists(const std::string&)’:
/<>/src/common/resources/resourcemanager.cpp:154:81: warning: ‘int
PHYSFS_isDirectory(const char*)’ is deprecated [-Wdeprecated-declarations]
154 | return PHYSFS_exists(CleanPath(directory).c_str()) &&
PHYSFS_isDirectory(CleanPath(directory).c_str());
|
~~^~
/usr/include/physfs.h:1159:17: note: declared here
1159 | PHYSFS_DECL int PHYSFS_isDirectory(const char *fname) PHYSFS_DEPRECATED;
| ^~
/<>/src/common/resources/resourcemanager.cpp: In static member
function ‘static std::vector >
CResourceManager::ListFiles(const std::string&, bool)’:
/<>/src/common/resources/resourcemanager.cpp:196:39: warning: ‘int
PHYSFS_isDirectory(const char*)’ is deprecated [-Wdeprecated-declarations]
19
Bug#1041081: marked as done (apitrace FTBFS with waffle 1.7.2-1)
Your message dated Thu, 21 Sep 2023 23:19:18 + with message-id and subject line Bug#1041081: fixed in apitrace 11.1+repack-1.2 has caused the Debian Bug report #1041081, regarding apitrace FTBFS with waffle 1.7.2-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1041081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041081 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apitrace Version: 11.1+repack-1.1 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apitrace.html ... CMake Error at CMakeLists.txt:216 (find_package): By not providing "FindWaffle.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "Waffle", but CMake did not find one. Could not find a package configuration file provided by "Waffle" with any of the following names: WaffleConfig.cmake waffle-config.cmake Add the installation prefix of "Waffle" to CMAKE_PREFIX_PATH or set "Waffle_DIR" to a directory containing one of the above files. If "Waffle" provides a separate development package or SDK, be sure it has been installed. -- Configuring incomplete, errors occurred! --- End Message --- --- Begin Message --- Source: apitrace Source-Version: 11.1+repack-1.2 Done: Dimitri John Ledkov We believe that the bug you reported is fixed in the latest version of apitrace, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1041...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dimitri John Ledkov (supplier of updated apitrace package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 21 Sep 2023 23:42:42 +0100 Source: apitrace Built-For-Profiles: noudeb Architecture: source Version: 11.1+repack-1.2 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Dimitri John Ledkov Closes: 1041081 Changes: apitrace (11.1+repack-1.2) unstable; urgency=medium . * Non-maintainer upload. * Switch CMake check from native to pkgconfig for waffle-1. Closes: #1041081 Checksums-Sha1: b313624d44e2a5b85ec21a958ba4a7473fba7373 2309 apitrace_11.1+repack-1.2.dsc 6bed72d50354881f20366f881b39d83a0ed2b6e8 8432 apitrace_11.1+repack-1.2.debian.tar.xz 1fcb5b93923cb4068a976a09b1fe12afd93c07db 7554 apitrace_11.1+repack-1.2_source.buildinfo Checksums-Sha256: 69cb7da5d5e7fdab345c18252fbf727b52fe3eefc144a2a554a9c571a242f10d 2309 apitrace_11.1+repack-1.2.dsc 9713f794466992779d7c84158926fcb18f62472134a94326b6e6735a276f15fe 8432 apitrace_11.1+repack-1.2.debian.tar.xz 5b408f225371384e03f6c1da3e2c13893b83c56fa6bac298628096e9f5d93609 7554 apitrace_11.1+repack-1.2_source.buildinfo Files: ac755cec1653bb6f05843ee442c4c773 2309 graphics optional apitrace_11.1+repack-1.2.dsc fba5e8b9913976c1b2799e6de0e40dd4 8432 graphics optional apitrace_11.1+repack-1.2.debian.tar.xz af150304a1d667c6f861ee040c5699a4 7554 graphics optional apitrace_11.1+repack-1.2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE7iQKBSojGtiSWEHXm47ISdXvcO0FAmUMylYACgkQm47ISdXv cO1IBQ/6AozinCVfgK5gnpae5P1UZQYTiRpefOwT4iDEd8oDP0SdUGfWk1Oue3u5 U+03IZ2OpLILG9WsVsO1kvQoAkvaerlQ4+8/wFNqbE4ZrZCQvxbOENDltOKTdgxJ Y81WKFhmyRK0AL3gpLLvFcOscd2nxlzbZcFqr8+Hd5shMVAT+iPqOMCjcS/VO6CI TojRj1qQrVCiN84xS9pGjpmhOw3IOuqc49fZtQctNkG+VXi3u1TbcGtd+f9l7sZH pxSzch5EflurDeEj41S9xcB/W0qoGF44s6FkqLtTS+yv818NConilDrEH/j+ZwMF NuRGwWTyGT/qOykYuR40eD7loeubgkMPCDXvznAo5xCmosVz2AnseliL6jP4BVF6 AL1P3Z3yJ6jxX434WZduGQlYDUaAHu5cYkjUKhDcGVuxDIzLGJH+OVJsdVbI0IE+ tgOPyOCJTnKkLr8yXOdYxQUo9cbyKoLiH2pCI2nXBLrTK4cQ/DSh5p10uZwcEuiJ kLru6hgobxCwkrrgLj741XrFFgjHBCaFJ9tPL7HZ/TBFETchxPHfjCCrJeWklAMj nEsbN4qkeQeZAICd53F+JQwU4OcQpEvJt/c9DiRnhU4M2Z0Al/rkipxjfMATAiQp WIoVV2F+G1Se9/T7QxwJbbwYUndKE/GjUzQOn06NmZWWt2b/8Ts= =PnCo -END PGP SIGNATURE End Message ---
Bug#1041242: libheif1: 1.16.2-1+b1 breaks displaying any pictures
Hey. Any chance to cherry pick the fixing commit from upstream and upload a new version with that to unstable? Thanks, Chris.
Bug#1051454: marked as done (librist: FTBFS on 32-bit architectures: "Simple profile unicast packet loss" test segfaults)
Your message dated Thu, 21 Sep 2023 20:38:33 +
with message-id
and subject line Bug#1051454: fixed in librist 0.2.8+dfsg+really0.2.7+dfsg-1
has caused the Debian Bug report #1051454,
regarding librist: FTBFS on 32-bit architectures: "Simple profile unicast
packet loss" test segfaults
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1051454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051454
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: librist
Version: 0.2.8+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
The new version of librist in unstable is failing its build-time tests on
all 32-bit architectures (armel, armhf, i386 and several ports
architectures):
> Summary of Failures:
>
> 3/21 libRIST:simple+unicast / Simple profile unicast packet loss 10%
> FAIL
> 0.05s killed by signal 11 SIGSEGV
> 4/21 libRIST:simple+unicast / Simple profile unicast packet loss 25%
> FAIL
> 0.03s killed by signal 11 SIGSEGV
It's likely to be easy to reproduce this on an amd64 machine by building
the i386 package (debuild -ai386), either cross-compiling or in an
i386 chroot, container or VM. This is a regression since 0.2.7+dfsg-1,
so I would suggest starting by reviewing the differences between those
versions.
This could be related to one of these compiler warnings, which indicate
assumptions in the source code that are not true on ILP32 architectures:
> ../tools/srp_shared.c: In function ‘user_verifier_lookup’:
> ../tools/srp_shared.c:176:43: warning: left shift count >= width of type
> [-Wshift-count-overflow]
> 176 | *generation = (buf.st_mtim.tv_sec << 32) |
> buf.st_mtim.tv_nsec;
> | ^~
> ../tools/ristreceiver.c: In function ‘cb_stats’:
> ../tools/ristreceiver.c:446:86: warning: cast from pointer to integer of
> different size [-Wpointer-to-int-cast]
> 446 | rist_prometheus_parse_stats(prom_stats_ctx,
> stats_container, (uint64_t)arg);
> |
>^
> ../tools/ristsender.c: In function ‘setup_rist_peer’:
> ../tools/ristsender.c:447:74: warning: cast to pointer from integer of
> different size [-Wint-to-pointer-cast]
> 447 | if (rist_stats_callback_set(ctx, setup->statsinterval,
> cb_stats, (void*)w->id) == -1) {
> |
>^
Or it could be something more subtle that gcc is unable to diagnose, like
type-size assumptions in a varargs function.
(It also failed to build on arm64, but that seems to be unrelated:
a different test failed there with an assertion failure, that test has
failed similarly in the past, and it doesn't fit the pattern of 64-bit
architectures succeeding but 32-bit failing. That's out of scope for this
particular bug report.)
librist4:i386 is pulled in by this dependency chain for users of Wine:
wine32 -> libwine -R-> gstreamer1.0-libav -> libavformat60 -> librist4
(where -R-> indicates a Recommends)
so having both amd64 and i386 versions installed is going to be a relatively
normal thing to do. Please could you take a look?
Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: librist
Source-Version: 0.2.8+dfsg+really0.2.7+dfsg-1
Done: Florian Ernst
We believe that the bug you reported is fixed in the latest version of
librist, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1051...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Florian Ernst (supplier of updated librist package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 21 Sep 2023 21:06:00 +0200
Source: librist
Architecture: source
Version: 0.2.8+dfsg+really0.2.7+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Florian Ernst
Changed-By: Florian Ernst
Closes: 1051454
Cha
Bug#1052430: pastedeploy: FTBFS against dh-python 6.20230825
Package: pastedeploy Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu mantic ubuntu-patch X-Debbugs-Cc: scho...@ubuntu.com Hi, The package now fails to build due to dh-python new clean behavior removing the FakeApp egg info that is needed for the test suite to run. We've applied the attached workaround in Ubuntu, although I think it'd be nicer to have an API for specifying exclusion, see #1051837. * Fix FTBFS due to dh-python being overly enthusiastic in its cleaning duties (LP: #2035337) Thanks for considering the patch. Simon Chopin -- System Information: Debian Release: trixie/sid APT prefers mantic APT policy: (500, 'mantic'), (100, 'mantic-proposed') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-5-generic (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru pastedeploy-3.0.1/debian/rules pastedeploy-3.0.1/debian/rules --- pastedeploy-3.0.1/debian/rules 2022-12-08 00:29:11.0 +0100 +++ pastedeploy-3.0.1/debian/rules 2023-09-21 22:20:30.0 +0200 @@ -22,3 +22,8 @@ override_dh_installchangelogs: dh_installchangelogs $(CURDIR)/docs/news.rst + +override_dh_auto_clean: + mv tests/fake_packages/FakeApp.egg/FakeApp.egg-info FakeApp.backup + dh_auto_clean + mv FakeApp.backup tests/fake_packages/FakeApp.egg/FakeApp.egg-info
Bug#1050019: marked as done (cctz: FTBFS due to time_zone_lookup_test failure)
Your message dated Thu, 21 Sep 2023 19:19:40 + with message-id and subject line Bug#1050019: fixed in cctz 2.3+dfsg1-4 has caused the Debian Bug report #1050019, regarding cctz: FTBFS due to time_zone_lookup_test failure to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1050019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050019 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cctz Version: 2.3+dfsg1-3 Severity: serious Tags: sid trixie ftbfs Hi, cctz fails to build with the following error message: 75% tests passed, 1 tests failed out of 4 Total Test time (real) = 30.25 sec The following tests FAILED: 2 - time_zone_lookup_test (Failed) Errors while running CTest make[1]: *** [Makefile:74: test] Error 8 make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu' dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j16 test ARGS\+=--verbose ARGS\+=-j16 returned exit code 2 make: *** [debian/rules:7: build] Error 25 --- End Message --- --- Begin Message --- Source: cctz Source-Version: 2.3+dfsg1-4 Done: Anton Gladky We believe that the bug you reported is fixed in the latest version of cctz, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1050...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anton Gladky (supplier of updated cctz package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 21 Sep 2023 20:30:20 +0200 Source: cctz Architecture: source Version: 2.3+dfsg1-4 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Anton Gladky Closes: 1050019 Changes: cctz (2.3+dfsg1-4) unstable; urgency=medium . [ Anton Gladky ] * [434ca88] Add .gitlab-ci.yml . [ Janitor ] * [f2d6695] Apply multi-arch hints . [ Anton Gladky ] * [fa70f53] Refresh patches * [c995bca] Use tzdata-legacy instead of tzdata. (Closes: #1050019) * [8c7e732] Set compat-level to 13 Standards-Version to 4.6.2. * [6770455] Install cmake files and some more changes due to dh 13. Checksums-Sha1: a4043de06a289ce548e4b10557a3d2157b46bf29 2124 cctz_2.3+dfsg1-4.dsc 227c989e0a8176531b335a2d649c007ded2307d7 4460 cctz_2.3+dfsg1-4.debian.tar.xz a18202e6c723309dd20ca62c251f1644b6c99c7c 6970 cctz_2.3+dfsg1-4_source.buildinfo Checksums-Sha256: 879f442192775cbe003824f917251b86cab7ac3b2838724264241e2e7300842a 2124 cctz_2.3+dfsg1-4.dsc 4118fb5232710515819dbd3cf6631a1863d6b085cb135ef785a9c1f5052b2156 4460 cctz_2.3+dfsg1-4.debian.tar.xz f63ca6ec0b5cb51871aa805204cba93ac36b070f3b6216bb41ed23292778db1e 6970 cctz_2.3+dfsg1-4_source.buildinfo Files: 36058af4b2990cc6d5b930952ab22f08 2124 libs optional cctz_2.3+dfsg1-4.dsc da3bf6810a615b2cc810d98aa2d42f55 4460 libs optional cctz_2.3+dfsg1-4.debian.tar.xz 587705df11b959a6e27de507550733e6 6970 libs optional cctz_2.3+dfsg1-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAmUMlmUACgkQ0+Fzg8+n /wYjCg/8CKwxANYpg0I9MBZ/LY1jclucHKFg18JPXlFwvxzqmXxVurOMNjXed70J Fq40bwkCOxDKe0j3A9T3BrvJmLQAeveEipRtfNtWRZTCI4E74RtXx3wrS+Hssh8d MWtplp4ArIJ3FFvYa9AYwsfwRXdcKxEmBRB7a6j4bR35XlpGjBCDQQ/T/9rllWBC d/DDTB5Oy3ivlUOQy5etzZKVdxB5uQDHDzx6SZavgrFQ6E5NhJrmoYum03NExDhJ TQSiQisiaK8HN63LA2XT8w4QQIuRpaEjYCXpce8iJmxjkvJ3slplcStuigBNTdt+ 61QkQicj0qLZTiqM6h9Soh5sfp3fe0SELMW0cdKYyEXe507+oUfgA4TKtNNoafH4 wqfPF2syrHHxCzyJrGfUFWC8KI5C+Fo2zNKmgQEampGMixAfu/yjFlD3Ncr3iX64 cIkVn+ZXdMlCoBGEYt+Hbiz9gx3PjbsHClCITfIKladWFV4gF9QTdhcSzazBE3Mq hclVI8cqACW4qmT52P1f5xLwEHeIHqSNKW4N4D7mv8sX/LFfMbohZbK75mhpCliq SrbOawb9Up2kkHDEXrQsbfZropLc891XhafCWgPme17tMgambgRKmJZnW1sWqpf6 xS2J7WK+rurDLQrVVn+ZwPGoMcJRsEOytsH+OlDFdFViEs3JNf8= =SB9a -END PGP SIGNATURE End Message ---
Bug#1052417: marked as done (bind9: CVE-2023-4236)
Your message dated Thu, 21 Sep 2023 18:19:33 + with message-id and subject line Bug#1052417: fixed in bind9 1:9.19.17-1 has caused the Debian Bug report #1052417, regarding bind9: CVE-2023-4236 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1052417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052417 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bind9 Version: 1:9.18.16-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 1:9.18.16-1~deb12u1 Hi, The following vulnerability was published for bind9. CVE-2023-4236[0]: | A flaw in the networking code handling DNS-over-TLS queries may | cause `named` to terminate unexpectedly due to an assertion failure. | This happens when internal data structures are incorrectly reused | under significant DNS-over-TLS query load. This issue affects BIND 9 | versions 9.18.0 through 9.18.18 and 9.18.11-S1 through 9.18.18-S1. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-4236 https://www.cve.org/CVERecord?id=CVE-2023-4236 [1] https://kb.isc.org/docs/cve-2023-4236 Regards, Salvtore --- End Message --- --- Begin Message --- Source: bind9 Source-Version: 1:9.19.17-1 Done: Ondřej Surý We believe that the bug you reported is fixed in the latest version of bind9, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1052...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ondřej Surý (supplier of updated bind9 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 20 Sep 2023 18:13:07 +0200 Source: bind9 Architecture: source Version: 1:9.19.17-1 Distribution: unstable Urgency: medium Maintainer: Debian DNS Team Changed-By: Ondřej Surý Closes: 1052416 1052417 Changes: bind9 (1:9.19.17-1) unstable; urgency=medium . * New upstream version 9.19.17 - CVE-2023-3341: A stack exhaustion flaw in control channel code may cause named to terminate unexpectedly (Closes: #1052416) - CVE-2023-4236: named may terminate unexpectedly under high DNS-over-TLS query load (Closes: #1052417) Checksums-Sha1: 9420e1389ac7a41fb993681aabdffe081c7493ec 3294 bind9_9.19.17-1.dsc c867148749eef06b0501462203d91bf0b64175ff 5644580 bind9_9.19.17.orig.tar.xz d2a7c9dbe011f401daf192cc379e4afa3c22683d 833 bind9_9.19.17.orig.tar.xz.asc 1fe69f2ad652ad3510b551f0f67c58b6a173bad3 58768 bind9_9.19.17-1.debian.tar.xz 22799d90575d3e91dd7bf1a7f61b90020d03b02f 15417 bind9_9.19.17-1_amd64.buildinfo Checksums-Sha256: 3eebd753ba99f960386bb89b713f5fade678262ee97d934acebb0cbbd7b3d68f 3294 bind9_9.19.17-1.dsc d86460943ababf8fb91cb20c2807efb30c2014ba6d8b5c690ad889e328655363 5644580 bind9_9.19.17.orig.tar.xz a4a5db0fd558f4dfe9fdedd5bef851010fa5e446def5e0d14976869683982d0f 833 bind9_9.19.17.orig.tar.xz.asc 3ea74154c695d78992f941ff0069d56a0530ba9b429b5b1afcfa00fc53e76e2c 58768 bind9_9.19.17-1.debian.tar.xz e492e18ca459ade8d85fbf1ed0e3a611db35e02545f22a2d27720598f5509b65 15417 bind9_9.19.17-1_amd64.buildinfo Files: c7a3671b65a2eaccab327a5dc96cb795 3294 net optional bind9_9.19.17-1.dsc 534c24d4bc2de30adc62ef7612cd3dde 5644580 net optional bind9_9.19.17.orig.tar.xz b739c3c0258ba15f226915481c0e36dd 833 net optional bind9_9.19.17.orig.tar.xz.asc 548011800fa7daf557cc91d3963d79a8 58768 net optional bind9_9.19.17-1.debian.tar.xz 98329a37818157b9a8c661987818b59d 15417 net optional bind9_9.19.17-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAmUMhmVfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u WcJPHA/+OVeA8xdC9t/jKRa0bvkGDcweEK+3nuLbYAij/lIUaZfrzrHdLZXzzaot l9GuIFW33ANPvlxL0QG93X9ymgs80r/ukO/BZNnPGRah6AhhtCo7MR7OEphtW2qd fa9pROcf96gMax48s6TgmDiymE+6s5WGuLciB5dWmmar+2QAfonA0Wf5tYJF+DO9 Juaqq/FJoOrC3v0AmVI6Un8oCvwz1q5jwZj57CqIgfZu+r0knTu6O4yquBNhE6aG vDsHdmm8TOFl/pz4ywBr62t2bf32M3Wgipb3OWMB
Bug#1052416: marked as done (bind9: CVE-2023-3341)
Your message dated Thu, 21 Sep 2023 18:19:33 + with message-id and subject line Bug#1052416: fixed in bind9 1:9.19.17-1 has caused the Debian Bug report #1052416, regarding bind9: CVE-2023-3341 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1052416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052416 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bind9 Version: 1:9.18.16-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 1:9.18.16-1~deb12u1 Control: found -1 1:9.16.42-1~deb11u1 Control: found -1 1:9.16.37-1~deb11u1 Hi, The following vulnerability was published for bind9. CVE-2023-3341[0]: | The code that processes control channel messages sent to `named` | calls certain functions recursively during packet parsing. Recursion | depth is only limited by the maximum accepted packet size; depending | on the environment, this may cause the packet-parsing code to run | out of available stack memory, causing `named` to terminate | unexpectedly. Since each incoming control channel message is fully | parsed before its contents are authenticated, exploiting this flaw | does not require the attacker to hold a valid RNDC key; only network | access to the control channel's configured TCP port is necessary. | This issue affects BIND 9 versions 9.2.0 through 9.16.43, 9.18.0 | through 9.18.18, 9.19.0 through 9.19.16, 9.9.3-S1 through | 9.16.43-S1, and 9.18.0-S1 through 9.18.18-S1. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-3341 https://www.cve.org/CVERecord?id=CVE-2023-3341 [1] https://kb.isc.org/docs/cve-2023-3341 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: bind9 Source-Version: 1:9.19.17-1 Done: Ondřej Surý We believe that the bug you reported is fixed in the latest version of bind9, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1052...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ondřej Surý (supplier of updated bind9 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 20 Sep 2023 18:13:07 +0200 Source: bind9 Architecture: source Version: 1:9.19.17-1 Distribution: unstable Urgency: medium Maintainer: Debian DNS Team Changed-By: Ondřej Surý Closes: 1052416 1052417 Changes: bind9 (1:9.19.17-1) unstable; urgency=medium . * New upstream version 9.19.17 - CVE-2023-3341: A stack exhaustion flaw in control channel code may cause named to terminate unexpectedly (Closes: #1052416) - CVE-2023-4236: named may terminate unexpectedly under high DNS-over-TLS query load (Closes: #1052417) Checksums-Sha1: 9420e1389ac7a41fb993681aabdffe081c7493ec 3294 bind9_9.19.17-1.dsc c867148749eef06b0501462203d91bf0b64175ff 5644580 bind9_9.19.17.orig.tar.xz d2a7c9dbe011f401daf192cc379e4afa3c22683d 833 bind9_9.19.17.orig.tar.xz.asc 1fe69f2ad652ad3510b551f0f67c58b6a173bad3 58768 bind9_9.19.17-1.debian.tar.xz 22799d90575d3e91dd7bf1a7f61b90020d03b02f 15417 bind9_9.19.17-1_amd64.buildinfo Checksums-Sha256: 3eebd753ba99f960386bb89b713f5fade678262ee97d934acebb0cbbd7b3d68f 3294 bind9_9.19.17-1.dsc d86460943ababf8fb91cb20c2807efb30c2014ba6d8b5c690ad889e328655363 5644580 bind9_9.19.17.orig.tar.xz a4a5db0fd558f4dfe9fdedd5bef851010fa5e446def5e0d14976869683982d0f 833 bind9_9.19.17.orig.tar.xz.asc 3ea74154c695d78992f941ff0069d56a0530ba9b429b5b1afcfa00fc53e76e2c 58768 bind9_9.19.17-1.debian.tar.xz e492e18ca459ade8d85fbf1ed0e3a611db35e02545f22a2d27720598f5509b65 15417 bind9_9.19.17-1_amd64.buildinfo Files: c7a3671b65a2eaccab327a5dc96cb795 3294 net optional bind9_9.19.17-1.dsc 534c24d4bc2de30adc62ef7612cd3dde 5644580 net optional bind9_9.19.17.orig.tar.xz b739c3c0258ba15f226915481c0e36dd 833 net optional bind9_9.19.17.orig.tar.xz.asc 548011800fa7daf557cc91d3963d79a8 58768 net optional bind9_9.19.17-1.debian.tar.xz 98329a37818157b9a8c661987818b5
Bug#1052334: marked as done (rust-leptonica-sys - Debian and Cargo dependencies inconsistent.)
Your message dated Thu, 21 Sep 2023 17:54:35 + with message-id and subject line Bug#1052334: fixed in rust-leptonica-sys 0.4.6-4 has caused the Debian Bug report #1052334, regarding rust-leptonica-sys - Debian and Cargo dependencies inconsistent. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1052334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052334 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rust-leptonica-sys Version: 0.4.6-3 Severity: serious The Debian dependencies for rust-leptonica-sys allow versions of rust-bindgen from 0.60.x to 0.66.x, however the Cargo dependencies only allow versions from 0.64.x to 0.66.x. This is causing autopkgtest failures and blocking rust-leptonica-sys and hence rust-bindgen from migrating to testing. Please make the dependencies consistent, either by changing the Debian depndencies to match the Cargo ones or by changing the Cargo dependency to match the Debian ones. --- End Message --- --- Begin Message --- Source: rust-leptonica-sys Source-Version: 0.4.6-4 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of rust-leptonica-sys, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1052...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated rust-leptonica-sys package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 21 Sep 2023 19:27:51 +0200 Source: rust-leptonica-sys Architecture: source Version: 0.4.6-4 Distribution: unstable Urgency: medium Maintainer: Jonas Smedegaard Changed-By: Jonas Smedegaard Closes: 1052334 Changes: rust-leptonica-sys (0.4.6-4) unstable; urgency=medium . * tighten (build-)dependency on packages for crate bindgen; closes: bug#1052334, thanks to Peter Green * update dh-cargo fork * update copyright info: update coverage Checksums-Sha1: 4da7f79271e0bc427ca73936c515933778d3e05e 2326 rust-leptonica-sys_0.4.6-4.dsc f9a7754fb1cc76bd4c478b5273ecc7c03c3d526f 15156 rust-leptonica-sys_0.4.6-4.debian.tar.xz e63fa33d0f110ab9651a06233fc424e5d30652b6 14506 rust-leptonica-sys_0.4.6-4_amd64.buildinfo Checksums-Sha256: 5c1012d9da0369b63d142b08f51c74bcef2f88f86e774dce11047c7360a8b093 2326 rust-leptonica-sys_0.4.6-4.dsc 878c16fa5194c36d68add3f8e083b58fec5d5b09894189c332fb020ba507e681 15156 rust-leptonica-sys_0.4.6-4.debian.tar.xz 383da8695ee12be4e1008a060cbc9f323142641d095e425c143c68724ac9140e 14506 rust-leptonica-sys_0.4.6-4_amd64.buildinfo Files: 26aeb2447d0289cf3b4a877caa78ded2 2326 rust optional rust-leptonica-sys_0.4.6-4.dsc c1204bdbb6b0a0d1f6dcddca2dc21170 15156 rust optional rust-leptonica-sys_0.4.6-4.debian.tar.xz 2b04b92eb83257c4b8688a7db203e045 14506 rust optional rust-leptonica-sys_0.4.6-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmUMfaEACgkQLHwxRsGg ASHnqQ/+KzfYWfdCzvSYcx2kdkWPPHBUWs9M9euxXWDrim3TBQYF+8S8Yjgc29ne +2nxvWprkS4cO0Fkj++rFIxrCMz+uK6VAr+MvzgSV2ObyEFp8sA6pK4u0bevEJEz 1g1DtTiaG3ehCe9jll7NkgY/3mWCc5VpHm4wbDuEexw0ixzorGEwoGtAtau2MnYb y/ZKWR+KNX9L8tQg6qxUi2Wh/d75tHB/kAxZFI842xnrJNQNnTGbf/Co40SCJpOy w1WEOmPyFAxmUvlf4xtr4Y7nIUFIzmeK6fkJ8a6TUEHqCiqsbhHdGeZehuN+bOO/ THbyaJymnDoxA5GK7ID+1tZktS1x471l77u+iPApYVVQcvW4U/psL28VSVdZOlax gqT5tQnn6ewzadVk2EPhM6MypRJT6mDhjcuipKuDaorh0QZkDA1DU3mVpkaFt4n1 oUWf7AnOBn+EMyQ+aeYFTc0yHX5vcMESv2ambIYe6XpONLXxYZ1E0S4KUnZ3tzzv 4SSDyN+fhQTpdpZY2LsboA9I8ZhZg3MHQd5yWR3UCJXtt3gKpI0vwAQNJ9btPg6I WL9toT5KHXyP9RqaEouI3dbp+j4PFr4OAM1eqsyW6kLkBPOwsyWDhAZ32ZrlKNxz VpFMD120qtXEXczwu7Zm/b0YUMZYQP29HEmyZE2z1Gx8IjWcmLM= =RqjR -END PGP SIGNATURE End Message ---
Bug#1052417: bind9: CVE-2023-4236
Thanks for the nudge. I must be tired or something as I totally forgot about updating the versions in upstream Debian. I'm working on it right now. Ondrej -- Ondřej Surý (He/Him) ond...@sury.org > On 21. 9. 2023, at 19:23, Salvatore Bonaccorso wrote: > > Source: bind9 > Version: 1:9.18.16-1 > Severity: grave > Tags: security upstream > X-Debbugs-Cc: car...@debian.org, Debian Security Team > > Control: found -1 1:9.18.16-1~deb12u1 > > Hi, > > The following vulnerability was published for bind9. > > CVE-2023-4236[0]: > | A flaw in the networking code handling DNS-over-TLS queries may > | cause `named` to terminate unexpectedly due to an assertion failure. > | This happens when internal data structures are incorrectly reused > | under significant DNS-over-TLS query load. This issue affects BIND 9 > | versions 9.18.0 through 9.18.18 and 9.18.11-S1 through 9.18.18-S1. > > > If you fix the vulnerability please also make sure to include the > CVE (Common Vulnerabilities & Exposures) id in your changelog entry. > > For further information see: > > [0] https://security-tracker.debian.org/tracker/CVE-2023-4236 >https://www.cve.org/CVERecord?id=CVE-2023-4236 > [1] https://kb.isc.org/docs/cve-2023-4236 > > Regards, > Salvtore >
Processed: [bts-link] source package src:gpac
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:gpac > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1051955 (http://bugs.debian.org/1051955) > # Bug title: gpac: CVE-2023-41000 > # * https://github.com/gpac/gpac/issues/2550 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1051955 + fixed-upstream Bug #1051955 [src:gpac] gpac: CVE-2023-41000 Added tag(s) fixed-upstream. > usertags 1051955 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1051955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:ocsigenserver
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:ocsigenserver > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1042501 (http://bugs.debian.org/1042501) > # Bug title: ocsigenserver depends on obsolete pcre > # * https://github.com/ocsigen/ocsigenserver/pull/229 > # * remote status changed: open -> closed > # * closed upstream > tags 1042501 + fixed-upstream Bug #1042501 [src:ocsigenserver] ocsigenserver depends on obsolete pcre Added tag(s) fixed-upstream. > usertags 1042501 - status-open Usertags were: status-open. There are now no usertags set. > usertags 1042501 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1042501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042501 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052417: bind9: CVE-2023-4236
Source: bind9 Version: 1:9.18.16-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 1:9.18.16-1~deb12u1 Hi, The following vulnerability was published for bind9. CVE-2023-4236[0]: | A flaw in the networking code handling DNS-over-TLS queries may | cause `named` to terminate unexpectedly due to an assertion failure. | This happens when internal data structures are incorrectly reused | under significant DNS-over-TLS query load. This issue affects BIND 9 | versions 9.18.0 through 9.18.18 and 9.18.11-S1 through 9.18.18-S1. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-4236 https://www.cve.org/CVERecord?id=CVE-2023-4236 [1] https://kb.isc.org/docs/cve-2023-4236 Regards, Salvtore
Processed: bind9: CVE-2023-4236
Processing control commands: > found -1 1:9.18.16-1~deb12u1 Bug #1052417 [src:bind9] bind9: CVE-2023-4236 Marked as found in versions bind9/1:9.18.16-1~deb12u1. -- 1052417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052417 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bind9: CVE-2023-3341
Processing control commands: > found -1 1:9.18.16-1~deb12u1 Bug #1052416 [src:bind9] bind9: CVE-2023-3341 Marked as found in versions bind9/1:9.18.16-1~deb12u1. > found -1 1:9.16.42-1~deb11u1 Bug #1052416 [src:bind9] bind9: CVE-2023-3341 Marked as found in versions bind9/1:9.16.42-1~deb11u1. > found -1 1:9.16.37-1~deb11u1 Bug #1052416 [src:bind9] bind9: CVE-2023-3341 Marked as found in versions bind9/1:9.16.37-1~deb11u1. -- 1052416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052416 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052416: bind9: CVE-2023-3341
Source: bind9 Version: 1:9.18.16-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 1:9.18.16-1~deb12u1 Control: found -1 1:9.16.42-1~deb11u1 Control: found -1 1:9.16.37-1~deb11u1 Hi, The following vulnerability was published for bind9. CVE-2023-3341[0]: | The code that processes control channel messages sent to `named` | calls certain functions recursively during packet parsing. Recursion | depth is only limited by the maximum accepted packet size; depending | on the environment, this may cause the packet-parsing code to run | out of available stack memory, causing `named` to terminate | unexpectedly. Since each incoming control channel message is fully | parsed before its contents are authenticated, exploiting this flaw | does not require the attacker to hold a valid RNDC key; only network | access to the control channel's configured TCP port is necessary. | This issue affects BIND 9 versions 9.2.0 through 9.16.43, 9.18.0 | through 9.18.18, 9.19.0 through 9.19.16, 9.9.3-S1 through | 9.16.43-S1, and 9.18.0-S1 through 9.18.18-S1. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-3341 https://www.cve.org/CVERecord?id=CVE-2023-3341 [1] https://kb.isc.org/docs/cve-2023-3341 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#1051408: Acknowledgement (flameshot: uploads potentially sensitive screenshots to the internet)
X-Debbugs-CC: Peter Control: tags -1 +confirmed Control: notfound -1 12.1.0-2 Control: fixed -1 12.1.0-2 Hi, On Thu, 7 Sep 2023 19:43:10 +0200 Peter wrote: > Thank you for the quick response to my message. > > My message is wrong in one place: I tested the old version from Debian > Bullseye. > > In Bookworm it behaves as follows: There is an "Imgur Application Client > Id" configured in the installation. So it is possible to use the upload > without any further configuration. But before uploading there is a > security prompt. In German: "Möchest du diese Aufnahme hochladen?"/"Do > you want to upload this image?". You may set "Upload without confirmation". > > For privacy reasons I would prefer the image upload function to be > disabled by default and no Imgur Application Id configured. Debian's flameshot package maintainer here. My understanding is that this bug only affects flameshot in Debian 11. Since flameshot in Debian 12 or later provides a confirmation window before uploading, no security concern should be assumed. As a package maintainer, I do not want to deviate from upstream's decision on providing a default imgur token in newer flameshot. Your concern of flameshot in Debian 11 looks valid. You proposed the patch to completely strip imgur token is kind of brute-force and I don't really like it, but I don't have enough time to backport a proper fix on popping up a confirmation window before imgur upload. As a result, I will take it as-is and provide an oldstable-proposed-updates for flameshot in Debian 11. NOTE: such change will later need to be reviewed by Debian Release Team, and the acceptance of this patch is solely at the discretion of Release Team, which I cannot guarantee to be accepted. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#1051408: Acknowledgement (flameshot: uploads potentially sensitive screenshots to the internet)
Processing control commands: > tags -1 +confirmed Bug #1051408 [flameshot] flameshot: uploads potentially sensitive screenshots to the internet Added tag(s) confirmed. > notfound -1 12.1.0-2 Bug #1051408 [flameshot] flameshot: uploads potentially sensitive screenshots to the internet No longer marked as found in versions flameshot/12.1.0-2. > fixed -1 12.1.0-2 Bug #1051408 [flameshot] flameshot: uploads potentially sensitive screenshots to the internet Marked as fixed in versions flameshot/12.1.0-2. -- 1051408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1051739: Package is uninstallable, bug unacknowledged, therefore release critical
Processing control commands: > tags -1 wontfix Bug #1051739 [caja-dropbox] 1.26.0-3 uninstallable due to nonexistent package Added tag(s) wontfix. -- 1051739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051739 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1051739: Package is uninstallable, bug unacknowledged, therefore release critical
Control: tags -1 wontfix Hi, On So 17 Sep 2023 03:39:55 CEST, Joseph Carter wrote: Control: severity -1 grave I didn't do this when filing the bug since ages ago it was considered impolite for end-users to set severity and particularly to set a severity above important. But it's been a week without acknowledgment or fix, and it is release critical even if it's a contrib package that isn't for the Holy Gnoman Empire DE. Joseph Problem here is that we are removing GTK-2+ from Debian testing/unstable, so the libs that get built against GTK-2+ (such as libayatana-appindicator-1). Problem here is that the downloaded dropbox executable probably is still GTK-2+. I need to test this and see how easily portable to GTK-3 is. Mike -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de pgpN_uo04Qdue.pgp Description: Digitale PGP-Signatur
Bug#1051063: vim-scripts: no license assumption must be non-free
On Fri, Sep 01, 2023 at 11:04:44PM +0200, Bastian Germann wrote: > In vim-script's copyright file, the following assumption is written: > > "Summary of license information of each script is reported below. For scripts > which license is "no license" it is assumed in good faith that having being > posted on vim.org their licence is at least as free as the licence of Vim > itself." > > This assumption is wrong. International copyright agreements unfortunately > make > those files non-DFSG-free. > > Please move them affected files to a new source package with Section: > non-free/editors. Honestly, this package probably should just be removed. Most of the scripts aren't maintained upstream anymore and are of questionable utility. I had been intending to split the package up anyway, but I'll probably just package a couple of the more useful/maintained ones and then just RM vim-scripts. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1052374: gdm3: Shows only an error screen when gnome.session is missing
On 2023-09-21 13:39 +03:00, Simon McVittie wrote: > On Thu, 21 Sep 2023 at 11:17:51 +0100, Simon McVittie wrote: >> On Thu, 21 Sep 2023 at 09:41:25 +0300, Alper Nebi Yasak wrote: >>> I've been using gdm3 without GNOME, and after recently upgrading gdm3 to >>> 45~beta-1 I started getting the gray "Oh no!" error message instead of >>> the login screen. >> >> Please look in the system log (systemd Journal) for the error messages >> that occur at this time, and send it to the bug address. Knowing only >> "it crashed" does not give us much information, and in particular, if we >> can reproduce a crash with gdm but not GNOME, it does not give us enough >> information to know that we have really reproduced the same crash you see. > > I can reproduce something similar in a test VM after > `apt install --no-install-recommends xorg openbox gdm3`, does the attached > match what you see? I had tried `journalctl -u gdm3` and `dmesg` but those were not very informative... Didn't think of `journalctl -b`, sorry. It's similar to your logs, attached for the record. More specifically, I do have "gsettings[1650]: unable to open named profile (Debian-gdm): using the null configuration." which seems to match what you fixed (per the changelog). Anyway, I built 45.0.1-1 locally and can confirm it fixes this error screen, thanks! journalctl-xb.log.gz Description: application/gzip
Bug#1052374: marked as done (gdm3: Shows only an error screen when gnome.session is missing)
Your message dated Thu, 21 Sep 2023 13:04:12 + with message-id and subject line Bug#1052374: fixed in gdm3 45.0.1-1 has caused the Debian Bug report #1052374, regarding gdm3: Shows only an error screen when gnome.session is missing to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1052374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052374 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gdm3 Version: 45~beta-1 Severity: serious Justification: missing dependency to function properly Control: -1 notfound 44.1-2 Dear Maintainer, I've been using gdm3 without GNOME, and after recently upgrading gdm3 to 45~beta-1 I started getting the gray "Oh no!" error message instead of the login screen. Tried a few things and found installing the gnome-session package fixes it. Copying /usr/share/gnome-session/sessions/gnome-login.session to .../gnome.session also fixes it. Looks like #850291, but that is archived and I don't know the Control invocations I need to continue on top of that. Setting severity same as that, though. Thanks for all the work on GNOME. My system is a bit of a mess, so don't hesitate to ask specifics if you can't reproduce the error. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: arm64, armhf, armel, i386 Kernel: Linux 6.5.0-1-amd64 (SMP w/24 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gdm3 depends on: ii accountsservice 23.13.9-4 ii adduser 3.137 ii dbus [default-dbus-system-bus]1.14.10-1 ii dbus-bin 1.14.10-1 ii dbus-daemon 1.14.10-1 ii dconf-cli 0.40.0-4 ii dconf-gsettings-backend 0.40.0-4 ii debconf [debconf-2.0] 1.5.82 ii gir1.2-gdm-1.045~beta-1 ii gnome-session [x-session-manager] 45.0-1 ii gnome-session-bin 45.0-1 ii gnome-session-common 45.0-1 ii gnome-settings-daemon 45.0-1 ii gnome-shell 44.5-1 ii gnome-terminal [x-terminal-emulator] 3.50.0-1 ii gsettings-desktop-schemas 45.0-1 ii kwin-x11 [x-window-manager] 4:5.27.8-1 ii libaccountsservice0 23.13.9-4 ii libaudit1 1:3.1.1-1 ii libc6 2.37-10 ii libcanberra-gtk3-00.30-10 ii libcanberra0 0.30-10 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1 ii libgdm1 45~beta-1 ii libglib2.0-0 2.78.0-2 ii libglib2.0-bin2.78.0-2 ii libgtk-3-03.24.38-5 ii libgudev-1.0-0238-2 ii libkeyutils1 1.6.3-2 ii libpam-modules1.5.2-7 ii libpam-runtime1.5.2-7 ii libpam-systemd [logind] 254.3-1 ii libpam0g 1.5.2-7 ii librsvg2-common 2.54.7+dfsg-2 ii libselinux1 3.5-1 ii libsystemd0 254.3-1 ii libx11-6 2:1.8.6-1 ii libxau6 1:1.0.9-1 ii libxcb1 1.15-1 ii libxdmcp6 1:1.1.2-3 ii lxterminal [x-terminal-emulator] 0.4.0-2 ii metacity [x-window-manager] 1:3.49.1-1 ii polkitd 123-1 ii procps2:4.0.3-1 ii qterminal [x-terminal-emulator] 1.3.0-1 ii rxvt-unicode [x-terminal-emulator]9.31-1 ii systemd-sysv 254.3-1 ii ucf 3.0043+nmu1 ii x11-common1:7.7+23 ii x11-xserver-utils 7.7+9+b1 ii xfce4-session [x-session-manager] 4.18.3-1 ii xfce4-terminal [x-terminal-emulator] 1.1.0-1 ii xfwm4 [x-window-manager] 4.18.0-1 ii xterm [x-terminal-emulator] 384-1 Versions of packages gdm3 recommends: ii at-spi2-core 2.50.0-1 ii desktop-base 12.0.6+nmu1 ii gnome-session [x
Processed: Bug#1052374 marked as pending in gdm3
Processing control commands: > tag -1 pending Bug #1052374 [gdm3] gdm3: Shows only an error screen when gnome.session is missing Added tag(s) pending. -- 1052374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052374 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052374: marked as pending in gdm3
Control: tag -1 pending Hello, Bug #1052374 in gdm3 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/gnome-team/gdm/-/commit/46f501348e7d96f31a73c94754a30399fe125c50 d/gdm3.links: Create a dconf profile named for the Debian-gdm user In upstream and Ubuntu gdm, the system username used for the greeter is "gdm", but in Debian, for historical reasons it is "Debian-gdm". Before version 45, the dconf profile name "gdm" was hard-coded, but since version 45 it uses a profile name that matches the system username (to allow gnome-initial-setup to have its own profile). This resulted in the gdm greeter trying to use the ordinary gnome.session instead of gnome-login.session, which caused login to fail when the gnome-session package was not installed, and caused settings in /etc/gdm3/greeter.dconf-defaults to be ineffective. Other differences between gnome.session and gnome-login.session, potentially including security hardening for the greeter, would also not have been effective. Closes: #1052374, #1051671, #1051993 (this message was generated automatically) -- Greetings https://bugs.debian.org/1052374
Bug#1051374: breaks existing setups using /etc/default/mini-httpd
Hello, > Looks good to me! I just uploaded. If this upload introduces any > other > problems, feel free to contact me to upload a fix. > > Thanks! > Thanks for your contribution and thanks for offering to help with a possible future upload :) By the way, the other fixed bug rendered virtual hosting in mini-httpd pretty annoying; if you were ever thinking about using that feature, it should work as intended now (seeing you have a non-trivial setup, maybe that could be of interest sometimes) > cheers, josch Have a great day, Alexandru signature.asc Description: This is a digitally signed message part
Bug#1051374: marked as done (breaks existing setups using /etc/default/mini-httpd)
Your message dated Thu, 21 Sep 2023 12:09:08 + with message-id and subject line Bug#1051374: fixed in mini-httpd 1.30-5 has caused the Debian Bug report #1051374, regarding breaks existing setups using /etc/default/mini-httpd to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1051374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051374 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mini-httpd Version: 1.30-4 Severity: serious Hi, after an upgrade to mini-httpd 1.30-4 my setup stopped working. It seems that this new version changed the init script for a systemd unit where the latter ignores the contents of /etc/default/mini-httpd. If that is intentional and not an oversight, there should at least be a NEWS entry so that users upgrading to 1.30-4 learn about this breaking change and are also told how to convert their existing configuration to the new style. If possible it would of course be nice if the systemd service would not break user's setups and would continue to consume /etc/default/mini-httpd. Thanks! cheers, josch --- End Message --- --- Begin Message --- Source: mini-httpd Source-Version: 1.30-5 Done: Alexandru Mihail We believe that the bug you reported is fixed in the latest version of mini-httpd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1051...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandru Mihail (supplier of updated mini-httpd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 21 Sep 2023 01:39:39 +0300 Source: mini-httpd Architecture: source Version: 1.30-5 Distribution: unstable Urgency: medium Maintainer: Alexandru Mihail Changed-By: Alexandru Mihail Closes: 491078 1051374 Changes: mini-httpd (1.30-5) unstable; urgency=medium . * Added patch stripping port numbers in vhost setup. (Closes: #491078). * Corrected systemd service not consuming /etc/default/mini-httpd configurations. Thanks a lot, Johannes Schauer Marin Rodrigues (Closes: #1051374). Checksums-Sha1: cc28ae7275c37669d2ac22f9ecfa3243b50f4ee6 1869 mini-httpd_1.30-5.dsc c9b88d1a46e16a1e78a6f781b1df4255ad4fff61 15540 mini-httpd_1.30-5.debian.tar.xz 943da2c11260441ab8fc3058451ffbc7024d4b15 5937 mini-httpd_1.30-5_arm64.buildinfo Checksums-Sha256: 9ab8df08a946254e8404d11adafc1b1afd19b5eb3b32ce0ee010ace58e3fe1ff 1869 mini-httpd_1.30-5.dsc c20c86239bc0d4d6316990ca575d8f4bb177518a167c50e1db6ffe15d9d2835e 15540 mini-httpd_1.30-5.debian.tar.xz 083fcbed4f5cebbec3422b6a78bc5406ed148faccda8ae8b0218acdc6d801f29 5937 mini-httpd_1.30-5_arm64.buildinfo Files: 151d544ea12838d3455ea76d688a8364 1869 web optional mini-httpd_1.30-5.dsc 1452b3b112177433bbe08fcd726604ed 15540 web optional mini-httpd_1.30-5.debian.tar.xz 1574a4a8388306f482fb9107248f4d78 5937 web optional mini-httpd_1.30-5_arm64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEElFhU6KL81LF4wVq58sulx4+9g+EFAmUMLV0ACgkQ8sulx4+9 g+FojQ//aAzOlAkt0txFYq0kfBByPaigQmBsUEP1WP9pkNrwndL9ePXhOQ604aFG M8BqPEhz36/Vd3t+7RQ7atrixA1b27pjYwAa9robjoix6hdhbOeJzdA29SY3vgqw eKZh3p69BF7ow7ZgV+ZwEYvDoex1/TknHbNas8jijizf6naH705xlMPtYcoXLyeD iKlntJONpi8FRcvvjLBkt9rP6xgwOTPpiRIJDz9l4BoiN9JPlxWGxOKpjtsk3KuA JwSwdkLQ8+DUZ7d/aurRhx9AECaBm0Mw6+fDoIvvsqk0y9ufbzNV+5uP5gkaZ/4m lTeZBeVAa94AzL60zqtrsM0cq/MXX6clWTHlH/Du19IPWsfF06RYH+xfqLqw/40w KMBe+IS7QR7FcEW5x7W3RdZxcBJliUKc8wweojteuqkWptv9CE9/omtrYm76+OTX ehSVxKTi0rPVz2AcLugXPx9BIeP+/euPT1pAQI9Ceg+k4WgwsFab7oILks+D9hJf q9+zTA9qZ3Q7GipiAveOBEGO+W+1GCVFes5gZyHzyoEGcd76NIUQndpwQztedft/ +rwEV0yoHEldAj/dEtrfPDr/cV+DVhE9rrDiO+f9sij6nqWKFizt6AfWO+g0nTiX 4FRGbHO7nnVw1NaAQGobTU8h6FVEEAFu3DsU4XdqZFiVLD+K948= =FJt/ -END PGP SIGNATURE End Message ---
Bug#1041162: marked as done (autopkgtest should ignore ESO entries for pinning)
Your message dated Thu, 21 Sep 2023 13:50:21 +0200 with message-id <4996da1b-a453-4e75-ad7a-f4f61972c...@debian.org> and subject line Re: Accepted autopkgtest 5.30 (source) into unstable has caused the Debian Bug report #1041162, regarding autopkgtest should ignore ESO entries for pinning to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1041162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041162 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:dkms Version: 3.0.11-3 Severity: serious Tags: sid trixie seen with https://ci.debian.net/data/autopkgtest/testing/amd64/d/dkms/35776414/log.gz triggered by gcc-11, gcc-12, gcc-9 dkms's dependencies are a bit bogus, make | build-essential can be reduced to just make, because build-essential depends on it. gcc | c-compiler probably leads to the excessive testing, please consider dropping the alternative, or if you want to really test with a specific compiler, use the package that triggered the test. But having these tests fail on a regular basis is just a burden. [...] 343s autoinstall for dkms modules has been disabled. 343s I: Checking for missing dkms dependency by trying to deinstall dkms 343s dpkg: dependency problems prevent removal of dkms: 343s dkms-test-dkms depends on dkms (>= 2.1.0.0). 343s 343s dpkg: error processing package dkms (--remove): 343s dependency problems - not removing 343s Errors were encountered while processing: 343s dkms 344s I: No Linux header packages are installed. 344s I: Installing all available ones from src:linux 6.3.7-1: 344s I: install linux-headers-6.3.0-1-amd64 344s I: install linux-headers-6.3.0-1-cloud-amd64 344s I: install linux-headers-6.3.0-1-rt-amd64 344s I: skiplinux-headers-amd64 344s I: skiplinux-headers-cloud-amd64 345s I: skiplinux-headers-rt-amd64 345s I: skiplinux-headers-6.3.0-2-amd64 345s I: skiplinux-headers-6.3.0-2-cloud-amd64 345s I: skiplinux-headers-6.3.0-2-rt-amd64 345s Reading package lists... 345s Building dependency tree... 345s Reading state information... 345s Some packages could not be installed. This may mean that you have 345s requested an impossible situation or if you are using the unstable 345s distribution that some required packages have not yet been created 345s or been moved out of Incoming. 345s The following information may help to resolve the situation: 345s 345s The following packages have unmet dependencies: 345s libatomic1 : Depends: gcc-13-base (= 13.1.0-8) but 13.1.0-6 is to be installed 345s libcc1-0 : Depends: gcc-13-base (= 13.1.0-8) but 13.1.0-6 is to be installed 345s libgomp1 : Depends: gcc-13-base (= 13.1.0-8) but 13.1.0-6 is to be installed 345s libitm1 : Depends: gcc-13-base (= 13.1.0-8) but 13.1.0-6 is to be installed 345s liblsan0 : Depends: gcc-13-base (= 13.1.0-8) but 13.1.0-6 is to be installed 345s libquadmath0 : Depends: gcc-13-base (= 13.1.0-8) but 13.1.0-6 is to be installed 345s libubsan1 : Depends: gcc-13-base (= 13.1.0-8) but 13.1.0-6 is to be installed 345s E: Unable to correct problems, you have held broken packages. 345s E: Linux headers failed to install. --- End Message --- --- Begin Message --- Version: 5.30 This landed in unstable and testing some time ago. Paul OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#1041161: marked as done (autopkgtest should ignore ESO entries for pinning)
Your message dated Thu, 21 Sep 2023 13:50:21 +0200 with message-id <4996da1b-a453-4e75-ad7a-f4f61972c...@debian.org> and subject line Re: Accepted autopkgtest 5.30 (source) into unstable has caused the Debian Bug report #1041162, regarding autopkgtest should ignore ESO entries for pinning to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1041162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041162 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:dkms Version: 3.0.11-3 Severity: serious Tags: sid trixie see https://ci.debian.net/data/autopkgtest/testing/arm64/d/dkms/35791560/log.gz triggered by gcc-11 [...] 179s Building dependency tree... 179s Reading state information... 179s Some packages could not be installed. This may mean that you have 179s requested an impossible situation or if you are using the unstable 179s distribution that some required packages have not yet been created 179s or been moved out of Incoming. 179s The following information may help to resolve the situation: 179s 179s The following packages have unmet dependencies: 179s libhwasan0 : Depends: gcc-13-base (= 13.1.0-8) but 13.1.0-6 is to be installed 179s E: Unable to correct problems, you have held broken packages. 179s E: Linux headers failed to install. there seems to be something wrong with the setup of the test. why isn't the same version taken for the two packages? --- End Message --- --- Begin Message --- Version: 5.30 This landed in unstable and testing some time ago. Paul OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#1051374: breaks existing setups using /etc/default/mini-httpd
Quoting Alexandru Mihail (2023-09-21 12:30:52) > I have no problem with that, can you minimally review the tag and determine > if it's fit for release or if anything is missing (ignore the added patch, > that fixes a separate bug) ? > > This is still one of my first releases, I'm still getting the hang of > certain operations in salsa :) > > If everything is OK, let's proceed with the upload ! Looks good to me! I just uploaded. If this upload introduces any other problems, feel free to contact me to upload a fix. Thanks! cheers, josch signature.asc Description: signature
Bug#1052316: marked as done (udev postinst uses update-rc.d -f remove which breaks /etc.init.d/udev transition and non-systemd boot)
Your message dated Thu, 21 Sep 2023 13:40:36 +0200 with message-id <42c8f6c9-360a-4ef4-a32f-22a9dd7aa...@debian.org> and subject line Re: udev postinst uses update-rc.d -f remove which breaks /etc.init.d/udev transition and non-systemd boot has caused the Debian Bug report #1052316, regarding udev postinst uses update-rc.d -f remove which breaks /etc.init.d/udev transition and non-systemd boot to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1052316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052316 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: udev Version: 254.3-1 Severity: serious Justification: Breaks unrelated software, causes boot failure on some systems Dear systemd Maintainers, As reported in the follow-up to #1052116[1], udev's postinst uses update-rc.d's -f option which breaks the transition of /etc/init.d/udev to bin:initscripts and causes non-systemd systems to fail to boot. Michael, as discussed yesterday on #debian-systemd, I am very grateful for your quick commit of a fix[2]. This bug is to prevent unintended migration of the broken udev to trixie. With thanks and best wishes Mark [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052116#17 [2] https://salsa.debian.org/systemd-team/systemd/-/commit/12e2c67612f958148f0a4ca165cfb9ca1ed9d3c3 -- System Information: Debian Release: 12.0 merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) --- End Message --- --- Begin Message --- Version: 254.4-1 OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#1052374: gdm3: Shows only an error screen when gnome.session is missing
On Thu, 21 Sep 2023 at 11:17:51 +0100, Simon McVittie wrote: > On Thu, 21 Sep 2023 at 09:41:25 +0300, Alper Nebi Yasak wrote: > > I've been using gdm3 without GNOME, and after recently upgrading gdm3 to > > 45~beta-1 I started getting the gray "Oh no!" error message instead of > > the login screen. > > Please look in the system log (systemd Journal) for the error messages > that occur at this time, and send it to the bug address. Knowing only > "it crashed" does not give us much information, and in particular, if we > can reproduce a crash with gdm but not GNOME, it does not give us enough > information to know that we have really reproduced the same crash you see. I can reproduce something similar in a test VM after `apt install --no-install-recommends xorg openbox gdm3`, does the attached match what you see? smcv gdm-only.log.gz Description: application/gzip
Bug#1042172: marked as done (ruby-jekyll-commonmark: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: expect(commonmark.convert(content).gsub(%r!\s+!, "")).to match(output.gsub(%r!\s+!, "")))
Your message dated Thu, 21 Sep 2023 10:18:22 + with message-id and subject line Bug#1042172: fixed in ruby-jekyll-commonmark 1.4.0-2 has caused the Debian Bug report #1042172, regarding ruby-jekyll-commonmark: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: expect(commonmark.convert(content).gsub(%r!\s+!, "")).to match(output.gsub(%r!\s+!, "")) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042172 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-jekyll-commonmark Version: 1.4.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > Failure/Error: expect(commonmark.convert(content).gsub(%r!\s+!, "")).to > match(output.gsub(%r!\s+!, "")) >expected > "atm_pin:1234" > to match > "#Sampleconfigurationtitle:CommonMarkTestverbose:trueatm_pin:1234" > # ./spec/jekyll_commonmark_spec.rb:78:in `block (3 levels) in (required)>' > > Finished in 0.36213 seconds (files took 0.48642 seconds to load) > 12 examples, 1 failure > > Failed examples: > > rspec ./spec/jekyll_commonmark_spec.rb:50 # > Jekyll::Converters::Markdown::CommonMark with default configuration > highlights fenced code-block > > Randomized with seed 62109 > > /usr/bin/ruby3.1 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec > ./spec/jekyll_commonmark_spec.rb --format documentation failed > ERROR: Test "ruby3.1" failed: The full build log is available from: http://qa-logs.debian.net/2023/07/26/ruby-jekyll-commonmark_1.4.0-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230726&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: ruby-jekyll-commonmark Source-Version: 1.4.0-2 Done: Cédric Boutillier We believe that the bug you reported is fixed in the latest version of ruby-jekyll-commonmark, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cédric Boutillier (supplier of updated ruby-jekyll-commonmark package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 21 Sep 2023 11:11:06 +0200 Source: ruby-jekyll-commonmark Architecture: source Version: 1.4.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Cédric Boutillier Closes: 1042172 Changes: ruby-jekyll-commonmark (1.4.0-2) unstable; urgency=medium . * Team upload * patch to fix class for boolean in test. Closes: #1042172 Checksums-Sha1: 007ba99605ed13b2646d6c098ae2250fb50e7e9a 1588 ruby-jekyll-commonmark_1.4.0-2.dsc 6cd33a09f45284e193f48619c57ff41d6161e003 3976 ruby-jekyll-commonmark_1.4.0-2.debian.tar.xz 8a6f4b8e401d10f90f9d95afc83bd40e0ba496f0 10381 ruby-jekyll-commonmark_1.4.0-2_amd64.buildinfo Checksums-Sha256: 5ada8382ce9dc2da01aca767becd803a5f1543535a48a65b82853f0d5fd81f10 1588 ruby-jekyll-commonmark_1.4.0-2.dsc f498540f986b65023a006211ba49e6ac2430c89d2366598f6451ef337101906c 3976 ruby-jekyll-commonmark_1.4.0-2.debian.tar.xz 88495d175f1a169d6f4e5c9bf09b39fc51526c9dc309c9625d66
Bug#1052374: gdm3: Shows only an error screen when gnome.session is missing
On Thu, 21 Sep 2023 at 09:41:25 +0300, Alper Nebi Yasak wrote: > I've been using gdm3 without GNOME, and after recently upgrading gdm3 to > 45~beta-1 I started getting the gray "Oh no!" error message instead of > the login screen. Please look in the system log (systemd Journal) for the error messages that occur at this time, and send it to the bug address. Knowing only "it crashed" does not give us much information, and in particular, if we can reproduce a crash with gdm but not GNOME, it does not give us enough information to know that we have really reproduced the same crash you see. Thanks, smcv
Bug#1042172: marked as pending in ruby-jekyll-commonmark
Control: tag -1 pending Hello, Bug #1042172 in ruby-jekyll-commonmark 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/ruby-team/ruby-jekyll-commonmark/-/commit/8c4233bf4565bcb180fa30e51a8804f68d89 patch to fix class for boolean in test. Closes: #1042172 (this message was generated automatically) -- Greetings https://bugs.debian.org/1042172
Processed: Bug#1042172 marked as pending in ruby-jekyll-commonmark
Processing control commands: > tag -1 pending Bug #1042172 [src:ruby-jekyll-commonmark] ruby-jekyll-commonmark: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: expect(commonmark.convert(content).gsub(%r!\s+!, "")).to match(output.gsub(%r!\s+!, "")) Added tag(s) pending. -- 1042172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042172 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052388: python-sparse: autopkgtest needs update for new version of numba
Source: python-sparse
Version: 0.13.0-1
Severity: serious
X-Debbugs-CC: nu...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:numba
Dear maintainer(s),
With a recent upload of numba the autopkgtest of python-sparse fails in
testing when that autopkgtest is run with the binary packages of numba
from unstable. It passes when run with only packages from testing. In
tabular form:
passfail
numba from testing0.57.1+dfsg-1
python-sparse from testing0.13.0-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of numba to testing
[1]. Of course, numba shouldn't just break your autopkgtest (or even
worse, your package), but it seems to me that numba isn't going to fix
the situation.
If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from numba should really add a
versioned Breaks on the unfixed version of (one of your) package(s).
Note: the Breaks is nice even if the issue is only in the autopkgtest as
it helps the migration software to figure out the right versions to
combine in the tests.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=numba
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-sparse/38059394/log.gz
115s === FAILURES
===
115s ___ test_tensordot[coo-gcxs-a_shape1-b_shape1-axes1]
___
115s
115s a_shape = (3, 4), b_shape = (4, 3), axes = (0, 1), a_format = 'coo'
115s b_format = 'gcxs'
115s
115s @pytest.mark.parametrize(
115s "a_shape,b_shape,axes",
115s [
115s [(3, 4), (4, 3), (1, 0)],
115s [(3, 4), (4, 3), (0, 1)],
115s [(3, 4, 5), (4, 3), (1, 0)],
115s [(3, 4), (5, 4, 3), (1, 1)],
115s [(3, 4), (5, 4, 3), ((0, 1), (2, 1))],
115s [(3, 4), (5, 4, 3), ((1, 0), (1, 2))],
115s [(3, 4, 5), (4,), (1, 0)],
115s [(4,), (3, 4, 5), (0, 1)],
115s [(4,), (4,), (0, 0)],
115s [(4,), (4,), 0],
115s ],
115s )
115s @pytest.mark.parametrize(
115s "a_format, b_format",
115s [("coo", "coo"), ("coo", "gcxs"), ("gcxs", "coo"), ("gcxs",
"gcxs")],
115s )
115s def test_tensordot(a_shape, b_shape, axes, a_format, b_format):
115s sa = sparse.random(a_shape, density=0.5, format=a_format)
115s sb = sparse.random(b_shape, density=0.5, format=b_format)
115s
115s a = sa.todense()
115s b = sb.todense()
115s
115s a_b = np.tensordot(a, b, axes)
115s
115s # tests for return_type=None
115s sa_sb = sparse.tensordot(sa, sb, axes)
115s sa_b = sparse.tensordot(sa, b, axes)
115s a_sb = sparse.tensordot(a, sb, axes)
115s
115s assert_eq(a_b, sa_sb)
115s assert_eq(a_b, sa_b)
115s assert_eq(a_b, a_sb)
115s if all(isinstance(arr, COO) for arr in [sa, sb]):
115s assert isinstance(sa_sb, COO)
115s else:
115s assert isinstance(sa_sb, GCXS)
115s assert isinstance(sa_b, np.ndarray)
115s assert isinstance(a_sb, np.ndarray)
115s
115s # tests for return_type=COO
115s sa_b = sparse.tensordot(sa, b, axes, return_type=COO)
115s > a_sb = sparse.tensordot(a, sb, axes, return_type=COO)
115s
115s tests/test_dot.py:58:
115s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _
115s /usr/lib/python3/dist-packages/sparse/_common.py:198: in tensordot
115s res = _dot(at, bt, return_type)
115s /usr/lib/python3/dist-packages/sparse/_common.py:425: in _dot
115s out = GCXS(
115s
/usr/lib/python3/dist-packages/sparse/_compressed/compressed.py:195: in
__init__
115s self._prune()
115s
/usr/lib/python3/dist-packages/sparse/_compressed/compressed.py:817: in
_prune
115s np.cumsum(np.bincount(coords[0], minlength=row_size),
out=indptr[1:])
115s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _
115s
115s args = (array([7304680739967889201, 3701732606794297453,
1,
115s 1, 2, 2,
115s 3, 3]),)
115s kwargs = {'minlength': 4}
115s relevant_args = (array([7304680739967889201, 3701732606794297453,
1,
115s 1, 2, 2,
115s 3, 3]), None)
115s
115s > ???
115s E ValueError: array is too big; `arr.size * arr.dtype.itemsize`
is larger than the maximum possib
Processed: python-sparse: autopkgtest needs update for new version of numba
Processing control commands: > affects -1 src:numba Bug #1052388 [src:python-sparse] python-sparse: autopkgtest needs update for new version of numba Added indication that 1052388 affects src:numba -- 1052388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052388 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:android-platform-tools: fails to migrate to testing for too long: ABI breakage?
Processing control commands: > close -1 34.0.4-1 Bug #1052383 [src:android-platform-tools] src:android-platform-tools: fails to migrate to testing for too long: ABI breakage? Marked as fixed in versions android-platform-tools/34.0.4-1. Bug #1052383 [src:android-platform-tools] src:android-platform-tools: fails to migrate to testing for too long: ABI breakage? Marked Bug as done -- 1052383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052383 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052383: src:android-platform-tools: fails to migrate to testing for too long: ABI breakage?
Source: android-platform-tools Version: 33.0.3-2 Severity: serious Control: close -1 34.0.4-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:android-platform-tools has been trying to migrate for 31 days [2]. Hence, I am filing this bug. The version in unstable causes autopkgtest failures in android-platform-art. The error message suggest an ABI breakage without a SONAME bump and associated library package rename. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=android-platform-tools https://ci.debian.net/data/autopkgtest/testing/amd64/a/android-platform-art/38059356/log.gz 86s /usr/bin/dexdump: symbol lookup error: /usr/lib/x86_64-linux-gnu/android/libart.so.0: undefined symbol: _ZN12BacktraceMap6CreateEib OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: wrong tags
Processing commands for cont...@bugs.debian.org: > tags 1031414 = Bug #1031414 [src:libgpuarray] libgpuarray: i386 test fail with new pocl Removed tag(s) fixed-upstream, sid, and bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 1031414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1031414: not fixed Re: libgpuarray: i386 test fail with new pocl
Control: reassign -1 src:libgpuarray Control: found -1 0.7.6-13 On Mon, 21 Aug 2023 07:51:27 +0100 "Rebecca N. Palmer" wrote: Control: severity -1 serious That wasn't a fix - log with pocl 4: https://ci.debian.net/data/autopkgtest/testing/i386/libg/libgpuarray/37023715/log.gz Given that this bug is already linked (blocked) by the root cause of this issue, which doesn't seem to get resolved, I consider this bug to not be a pocl issue anymore, but only a libgpuarray issue: its autopkgtest fails. Of course ideally the issue in llvm gets fixed, but while that is waiting for somebody to pick up the work, I suggest to skip the failing test on i386. If you believe that the autopkgtest shows that libgpuarray (or pocl) isn't usable for most usage on i386, than please have it removed from i386 (and prevent a successful build until the issue is resolved). Paul PS: CC the i386 porter to let him know in case he's not aware yet. OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: not fixed Re: libgpuarray: i386 test fail with new pocl
Processing control commands: > reassign -1 src:libgpuarray Bug #1031414 [src:pocl,src:libgpuarray] libgpuarray: i386 test fail with new pocl Bug reassigned from package 'src:pocl,src:libgpuarray' to 'src:libgpuarray'. No longer marked as found in versions libgpuarray/0.7.6-13, pocl/4.0-2, pocl/3.1-3, and libgpuarray/0.7.6-14. Ignoring request to alter fixed versions of bug #1031414 to the same values previously set > found -1 0.7.6-13 Bug #1031414 [src:libgpuarray] libgpuarray: i386 test fail with new pocl Marked as found in versions libgpuarray/0.7.6-13. -- 1031414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052376: lxpanel: no longer obeys its geometry settings
On Thu, 21 Sep 2023 08:49:04 +0200 Francesco Poli (wintermute) wrote: > Downgrading/reinstalling the following packages: > > libwnck-common (2.30.7-6) > libwnck22 (2.30.7-6+b1) > libkeybinder0 (0.3.1-2.1) > libfm4 (1.3.2-1) > libfm-gtk4 (1.3.2-1) > lxpanel-data (0.10.1-2) ... > lxpanel (0.10.1-2) > > is enough to restore the normal (sane) behavior. I also had to downgrade the following package: libfm-modules (1.3.2-1) and to purge the following packages: libfm-gtk3-4 libkeybinder-3.0-0 libwnck-3-0 libwnck-3-common -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpEyZ59mSSga.pgp Description: PGP signature
Processed: Re: lintian: FTBFS: 3 tests failed
Processing control commands: > tags -1 + patch Bug #1042049 [src:lintian] lintian: FTBFS: 3 tests failed Added tag(s) patch. -- 1042049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042049 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042049: lintian: FTBFS: 3 tests failed
Control: tags -1 + patch Hi, Please see the following patch https://salsa.debian.org/lintian/lintian/-/merge_requests/480
