Bug#1031258: python-instagram: Missing active upstream should not be in Bookworm

[Petter Reinholdtsen]

Package: python-instagram
Version: 1.3.2+git20160108~dfeebe9-4.1
Severity: critical

This project is archived upstream, and thus seem to be dead.  There are
9 installations reported to popularity-contest, and one user last week.
Unless a new active upstream is found I believe this project should be
removed from Debian, and I definitely do not want to try to maintain it
in the next stable release in its current state, hence this RC issue to
keep it out of testing.

Anyone willing to rescue this package for Bookworm got less then a month
to do so.  If no-one step up, I'll file a request for removal from
unstable later.

-- 
Happy hacking
Petter Reinholdtsen

Processed: Re: Bug#1014831: android-platform-frameworks-base: aapt2 command does not work at all

[Debian Bug Tracking System]

Processing control commands:

> found -1 1:13.0.0+r30-1~exp1
Bug #1014831 [android-platform-frameworks-base] 
android-platform-frameworks-base: aapt2 command does not work at all
There is no source info for the package 'android-platform-frameworks-base' at 
version '1:13.0.0+r30-1~exp1' with architecture ''
Unable to make a source version for version '1:13.0.0+r30-1~exp1'
Marked as found in versions 1:13.0.0+r30-1~exp1.

-- 
1014831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014831
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1014831: android-platform-frameworks-base: aapt2 command does not work at all

[Roger Shimizu]

control: found -1 1:13.0.0+r30-1~exp1

still occurs in latest experimental version.

Bug#1031252: hipsparse: FTBFS (c++: error: -E or -x required when input is from standard input)

[Cordell Bloor]

On 2023-02-13 17:22, Santiago Vila wrote:

[  8%] Linking CXX shared library libhipsparse.so
cd /<>/obj-x86_64-linux-gnu/library && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/hipsparse.dir/link.txt --verbose=1
/usr/bin/c++ -fPIC -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -Wl,-z,relro -shared 
-Wl,-soname,libhipsparse.so.0 -o libhipsparse.so.0.1 
CMakeFiles/hipsparse.dir/src/hcc_detail/hipsparse.cpp.o 
/usr/lib/x86_64-linux-gnu/librocsparse.so.0.1 
/usr/lib/x86_64-linux-gnu/libamdhip64.so.5.2.21153- 
-lCLANGRT_BUILTINS-NOTFOUND

c++: error: -E or -x required when input is from standard input
make[3]: *** [library/CMakeFiles/hipsparse.dir/build.make:102: 
library/libhipsparse.so.0.1] Error 1


This is a bug in libamdhip64-5:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021643

It was fixed in rocm-hipamd 5.2.3-2, but no versions since rocm-hipamd 
5.2.3-1 have migrated to bookworm. This problem will affect all 
libraries and executables that link against libamdhip64-5 using the GCC 
toolchain.



If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.


I'm still learning how to use these the Debian bug reporting tools. 
Perhaps another maintainer could help set these properties.


Apologies for the incomplete handling, but I hope that this information 
is helpful.


Sincerely,
Cory Bloor

Bug#1030846: Bug#1030939: e2fsprogs: generates filesystems that grub-install doesn't recognize

[Theodore Ts'o]

On Tue, Feb 14, 2023 at 01:01:38AM +0100, Daniel Leidert wrote:
> Hi Steve,
> 
> I believe that your fix to grub2 in Sid is not enough to handle
> #1030939/#1030846.
> 
> This problem breaks e.g. vmdb2. I can no longer create a Bullseye
> system image with vmdb2 on Sid, because the grub-install step in the
> Bullseye chroot now fails, because the created filesystem (created with
> e2fsprogs on Sid) cannot be recognized by grub.

I'm confused, why does using vmdb2 on *sid* involve running
grub-install on a *bulleye* chroot?  That seems to be extremely
ill-advised.  If you are trying to install a bullseye system, why
can't you using vmdb2 on bullseye?

And if you are trying to install a sid or bookworm system using vmdb2,
why can't you (or vmdb2) use a sid or bookworm chroot for doing the
grub-install?

> I have to downgrade e2fsprogs to the version in Testing to get the
> build going again. It also means that a Bookworm system can never be
> used to format and debootstrap a Bullseye or Buster system that
> requires a grub installation.
> 
> I guess that the fix applied to grub2 in Sid would have to be applied
> to grub2 in Bullseye as well (and basically to any grub2 package in any
> Debian or Ubuntu or Raspbian release supported by debootstrap).

I can understand why we need to keep things synchronized so that a
debian installer for Bookworm be able to generate a bootable system
using the version of grub and e2fsprogs in Bookworm.

But a generalized requirement that we be able to use debootstrap and
vmdb2 to be able to bootstrap an arbitrarily old distribution doesn't
seem to be reasonable.  It would mean that we couldn't update to newer
versions of the C library, or of new file system featuers, because we
are somehow obliged to be able to boostrap ancient versions of the
system.  After all, we don't require that a binary built using
Bookworm be able to run on Bullseye.  How is this any different?

I generate test appliances for file system regression testing which
run on Debian Bullseye on my Debian Bookworm system --- and this gets
done using build chroot[1].  I even have super-convenient scripts to
create the build chroot[2].  This is not hard why can't vmdb2 do
the same thing?

[1] 
https://github.com/tytso/xfstests-bld/blob/master/Documentation/building-xfstests.md
[2] https://github.com/tytso/xfstests-bld/blob/master/setup-buildchroot

- Ted

Bug#1030669: Only include in Bookworm with commitment to stable updates

[Marco d'Itri]

On Feb 02, Moritz Muehlenhoff  wrote:

> Varnish should only be included in Bookworm with a reliable commitment
> by the maintainers to backport/test security fixes across the typical
> three year life cycle (two years of stable-security and one year of
> oldstable-security).
I do not think that this will be helpful for Varnish users.

> Especially since testing currently has 7.1, which reaches it's end of
> life on March 15 2023 and does not contain the LTS release.
stable contains 6.5.1, oldstable 6.1.1, neither of which was a LTS, and 
the sky did not fall.

> (It's not unlikely that most people who operate a CDN based on Varnish
> only use custom/patched/recent packages backported from stable
> anyway, which is perfectly fine, but then let's make that explicit
> by keeping it out of testing).
Varnish is used by much more than CDNs! Web site operators use Varnish 
all the time to cache CMSes like Wordpress and Magento, and they do not 
have the resources to build custom packages (and matching extensions).

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#1031253: jthread: FTBFS (dh_install: error: missing files, aborting)

[Santiago Vila]

Package: src:jthread
Version: 1.3.1-3.1
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules build-arch
dh build-arch
dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
   dh_update_autotools_config -a
   dh_auto_configure -a
dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
(level 9 in use)
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DFETCHCONTENT_FULLY_DISCONNECTED=ON "-GUnix 
Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu ..
CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required):
  Compatibility with CMake < 2.8.12 will be removed from a future version of
  CMake.

  Update the VERSION argument  value or use a ... suffix to tell
  CMake that the project does not need compatibility with older versions.


-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
-- Found Threads: TRUE
CMake Warning (dev) at src/CMakeLists.txt:48 (get_target_property):
  Policy CMP0026 is not set: Disallow use of the LOCATION target property.
  Run "cmake --help-policy CMP0026" for policy details.  Use the cmake_policy
  command to set the policy and suppress this warning.

  The LOCATION property should not be read from target "jthread-shared".  Use
  the target name directly with add_custom_command, or use the generator
  expression $, as appropriate.

This warning is for project developers.  Use -Wno-dev to suppress it.

-- Configuring done
-- Generating done
CMake Warning:
  Manually-specified variables were not used by the project:

CMAKE_EXPORT_NO_PACKAGE_REGISTRY
CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY
CMAKE_INSTALL_LIBDIR
CMAKE_INSTALL_LOCALSTATEDIR
CMAKE_INSTALL_SYSCONFDIR
FETCHCONTENT_FULLY_DISCONNECTED


-- Build files have been written to: /<>/obj-x86_64-linux-gnu
   dh_auto_build -a
dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 9 
in use)
cd obj-x86_64-linux-gnu && make -j1 VERBOSE=1
make[1]: Entering directory '/<>/obj-x86_64-linux-gnu'
/usr/bin/cmake -S/<> -B/<>/obj-x86_64-linux-gnu 
--check-build-system CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start /<>/obj-x86_64-linux-gnu/CMakeFiles 
/<>/obj-x86_64-linux-gnu//CMakeFiles/progress.marks
make  -f CMakeFiles/Makefile2 all
make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
make  -f src/CMakeFiles/jthread-static.dir/build.make 
src/CMakeFiles/jthread-static.dir/depend
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> 
/<>/src /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/src 
/<>/obj-x86_64-linux-gnu/src/CMakeFiles/jthread-static.dir/DependInfo.cmake --color=
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make  -f src/CMakeFiles/jthread-static.dir/build.make 
src/CMakeFiles/jthread-static.dir/build
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
[ 16%] Building CXX object 
src/CMakeFiles/jthread-static.dir/pthread/jmutex.cpp.o
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ -DJTHREAD_COMPILING -I/<>/src 
-I/<>/obj-x86_64-linux-gnu/src -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MT src/CMakeFiles/jthread-static.dir/pthread/jmutex.cpp.o -MF 
CMakeFiles/jthread-static.dir/pthread/jmutex.cpp.o.d -o CMakeFiles/jthread-static.dir/pthread/jmutex.cpp.o -c 
/<>/src/pthread/jmutex.cpp
[ 33%] Building CXX object 
src/CMakeFiles/jthread-static.dir/pthread/jthread.cpp.o
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ -DJTHREAD_COMPILING -I/<>/src 
-I/<>/obj-x86_64-linux-gnu/src -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MT src/CMakeFiles/jthread-static.dir/pthread/jthread.cpp.o -MF 
CMakeFiles/jthread-static.dir/pthread/jthread.cpp.o.d -o CMakeFiles/jthread-static.dir/pthread/jthread.cpp.o -c 
/<>/src/pthread/jthread.cpp
[ 50%] Linking CXX static library libjthread.a
cd 

Bug#1031252: hipsparse: FTBFS (c++: error: -E or -x required when input is from standard input)

[Santiago Vila]

Package: src:hipsparse
Version: 5.3.3+dfsg-1
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-arch
dh binary-arch -Scmake
   dh_update_autotools_config -a -O-Scmake
   dh_autoreconf -a -O-Scmake
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- -DCMAKE_BUILD_TYPE=Release -DROCM_SYMLINK_LIBS=OFF 
-DBUILD_FILE_REORG_BACKWARD_COMPATIBILITY=OFF
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DFETCHCONTENT_FULLY_DISCONNECTED=ON 
-DCMAKE_INSTALL_RUNSTATEDIR=/run -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix 
Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
-DCMAKE_BUILD_TYPE=Release -DROCM_SYMLINK_LIBS=OFF -DBUILD_FILE_REORG_BACKWARD_COMPATIBILITY=OFF 
..
Re-run cmake no build system arguments
-- The CXX compiler identification is GNU 12.2.0
-- The Fortran compiler identification is GNU 12.2.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Detecting Fortran compiler ABI info
-- Detecting Fortran compiler ABI info - done
-- Check for working Fortran compiler: /usr/bin/gfortran - skipped
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
-- Found Threads: TRUE
-- hip::amdhip64 is SHARED_LIBRARY
-- hip::amdhip64 is SHARED_LIBRARY
-- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY
-- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY - Success
-- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY
-- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY - Success
-- Performing Test COMPILER_HAS_DEPRECATED_ATTR
-- Performing Test COMPILER_HAS_DEPRECATED_ATTR - Success
-- OS: debian
-- Configuring done
-- Generating done
CMake Warning:
  Manually-specified variables were not used by the project:

CMAKE_EXPORT_NO_PACKAGE_REGISTRY
CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY
FETCHCONTENT_FULLY_DISCONNECTED


-- Build files have been written to: /<>/obj-x86_64-linux-gnu
make[1]: Leaving directory '/<>'
   dh_auto_build -a -O-Scmake
cd obj-x86_64-linux-gnu && make -j1 "INSTALL=install 
--strip-program=true" VERBOSE=1
make[1]: Entering directory '/<>/obj-x86_64-linux-gnu'
/usr/bin/cmake -S/<> -B/<>/obj-x86_64-linux-gnu 
--check-build-system CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start /<>/obj-x86_64-linux-gnu/CMakeFiles 
/<>/obj-x86_64-linux-gnu//CMakeFiles/progress.marks
make  -f CMakeFiles/Makefile2 all
make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
make  -f library/CMakeFiles/hipsparse_fortran.dir/build.make 
library/CMakeFiles/hipsparse_fortran.dir/depend
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> 
/<>/library /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/library 
/<>/obj-x86_64-linux-gnu/library/CMakeFiles/hipsparse_fortran.dir/DependInfo.cmake --color=
Dependee 
"/<>/obj-x86_64-linux-gnu/library/CMakeFiles/hipsparse_fortran.dir/DependInfo.cmake" is 
newer than depender 
"/<>/obj-x86_64-linux-gnu/library/CMakeFiles/hipsparse_fortran.dir/depend.internal".
Dependee "/<>/obj-x86_64-linux-gnu/library/CMakeFiles/CMakeDirectoryInformation.cmake" 
is newer than depender 
"/<>/obj-x86_64-linux-gnu/library/CMakeFiles/hipsparse_fortran.dir/depend.internal".
Scanning dependencies of target hipsparse_fortran
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make  -f library/CMakeFiles/hipsparse_fortran.dir/build.make 
library/CMakeFiles/hipsparse_fortran.dir/build
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
[  2%] Building Fortran object 
library/CMakeFiles/hipsparse_fortran.dir/src/hipsparse_enums.f90.o
cd /<>/obj-x86_64-linux-gnu/library && /usr/bin/gfortran   -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -O3 -DNDEBUG -O3 -J../include/hipsparse 
-std=f2003 -ffree-form -cpp -c /<>/library/src/hipsparse_enums.f90 -o 
CMakeFiles/hipsparse_fortran.dir/src/hipsparse_enums.f90.o
/usr/bin/cmake -E cmake_copy_f90_mod include/hipsparse/hipsparse_enums.mod 
library/CMakeFiles/hipsparse_fortran.dir/hipsparse_enums.mod.stamp GNU
[  4%] Building Fortran object 
library/CMakeFiles/hipsparse_fortran.dir/src/hipsparse.f90.o
cd /<>/obj-x86_64-linux-gnu/library && /usr/bin/gfortran   -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -O3 -DNDEBUG -O3 -J../include/hipsparse 
-std=f2003 -ffree-form -cpp -c /<>/library/src/hipsparse.f90 -o 

Bug#1031129: marked as done (libglib2.0-0: breaks pipewire/wireplumber)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2023 00:20:05 +
with message-id 
and subject line Bug#1031129: fixed in glib2.0 2.75.3-1
has caused the Debian Bug report #1031129,
regarding libglib2.0-0: breaks pipewire/wireplumber
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.)


-- 
1031129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031129
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libglib2.0-0
Version: 2.75.2-1
Severity: critical
Justification: breaks unrelated software

I've tried to install this version on two different machines and each time it 
did break wireplumber/pulseoaudio.

extract of journalctl:
févr. 12 11:13:06 tri-yann4 wireplumber[2267]: Failed to set scheduler 
settings: Opération non permise
févr. 12 11:13:06 tri-yann4 kernel: traps: wireplumber[2299] trap int3 
ip:7fe5d515b4e7 sp:7fe5d2e22b40 error:0 in 
libglib-2.0.so.0.7502.0[7fe5d511c000+8e000]
févr. 12 11:13:06 tri-yann4 systemd-coredump[2304]: Process 2267 (wireplumber) 
of user 1000 dumped core.
 #0  0x7fe5d52c4633 
wp_object_interest_validate (libwireplumber-0.4.so.0 + 0x2c633)
 


-- System Information:
Debian Release: bookworm/sid
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), 
(500, 'stable'), (1, 'experimental')
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 5.15.93 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libglib2.0-0 depends on:
ii  libc6 2.36-8
ii  libffi8   3.4.4-1
ii  libmount1 2.38.1-4
ii  libpcre2-8-0  10.42-1
ii  libselinux1   3.4-1+b5
ii  zlib1g1:1.2.13.dfsg-1

Versions of packages libglib2.0-0 recommends:
ii  libglib2.0-data   2.75.2-1
ii  shared-mime-info  2.2-1
ii  xdg-user-dirs 0.18-1

Versions of packages libglib2.0-0 suggests:
pn  low-memory-monitor  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: glib2.0
Source-Version: 2.75.3-1
Done: Simon McVittie 

We believe that the bug you reported is fixed in the latest version of
glib2.0, 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 1031...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated glib2.0 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 13 Feb 2023 20:49:33 +
Source: glib2.0
Architecture: source
Version: 2.75.3-1
Distribution: experimental
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 1031129
Changes:
 glib2.0 (2.75.3-1) experimental; urgency=medium
 .
   * New upstream release
 - Resolves a crash when creating threads in a process with elevated
   priority, such as wireplumber (Closes: #1031129)
   * d/copyright: Update
   * Drop patches that were applied upstream
   * d/libglib2.0-0.symbols: Update.
 Two private symbols that were not intended to appear in the ABI were
 removed. Other Debian packages don't seem to use either.
   * d/patches: Update all patches that skip tests to ensure all tests
 produce valid TAP syntax
Checksums-Sha1:
 32843231c98986dfde8ede33100ebb70270d77e0 3773 glib2.0_2.75.3-1.dsc
 99d58feb1c68e16f1bf922afcf3b122ad32705b6 266184 
glib2.0_2.75.3.orig-unicode-data.tar.xz
 ae4d77a6fcb9ac8206261203d079ae07d09aa67e 5261616 glib2.0_2.75.3.orig.tar.xz
 93259ed68923d981bca41e4c5bebfb40b71a0335 115760 glib2.0_2.75.3-1.debian.tar.xz
 72b8033bf4fb278f5c2383f06ec3b0dbe3b94330 7027 glib2.0_2.75.3-1_source.buildinfo
Checksums-Sha256:
 e5089f6b45be1b3f4105149e9355472cb54b6d427bf7540f11f899c2a09f03e2 3773 
glib2.0_2.75.3-1.dsc
 7c3e36ec1356ac025a92169b74c4c3e6858345f59ed4ea4cf0db300dec4fa21a 266184 
glib2.0_2.75.3.orig-unicode-data.tar.xz
 7c517d0aff456c35a039bce8a8df7a08ce95a8285b09d1849f8865f633f7f871 5261616 
glib2.0_2.75.3.orig.tar.xz
 

Processed: affects 1030939

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 1030939 + vmdb2
Bug #1030939 [e2fsprogs] e2fsprogs: generates filesystems that grub-install 
doesn't recognize
Added indication that 1030939 affects vmdb2
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1030939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030939
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1030846: e2fsprogs: generates filesystems that grub-install doesn't recognize

[Daniel Leidert]

Hi Steve,

I believe that your fix to grub2 in Sid is not enough to handle
#1030939/#1030846.

This problem breaks e.g. vmdb2. I can no longer create a Bullseye
system image with vmdb2 on Sid, because the grub-install step in the
Bullseye chroot now fails, because the created filesystem (created with
e2fsprogs on Sid) cannot be recognized by grub. I have to downgrade
e2fsprogs to the version in Testing to get the build going again. It
also means that a Bookworm system can never be used to format and
debootstrap a Bullseye or Buster system that requires a grub
installation.

I guess that the fix applied to grub2 in Sid would have to be applied
to grub2 in Bullseye as well (and basically to any grub2 package in any
Debian or Ubuntu or Raspbian release supported by debootstrap).

This situation is really messy. It breaks basically all my image builds
with vmdb2.

Regards, Daniel


signature.asc
Description: This is a digitally signed message part

Bug#1028857: marked as done (libpsl: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Mon, 13 Feb 2023 23:56:05 +
with message-id 
and subject line Bug#1028857: fixed in libpsl 0.21.2-1
has caused the Debian Bug report #1028857,
regarding libpsl: FTBFS: dh_auto_test: error: make -j8 check 
"TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1028857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028857
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpsl
Version: 0.21.0-1.2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230113 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[5]: Entering directory '/<>/tests'
> PASS: test-is-public-builtin
> PASS: test-registrable-domain
> PASS: test-is-public
> PASS: test-is-cookie-domain-acceptable
> FAIL: test-is-public-all
> =
>libpsl 0.21.0: tests/test-suite.log
> =
> 
> # TOTAL: 5
> # PASS:  4
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> .. contents:: :depth: 2
> 
> FAIL: test-is-public-all
> 
> 
> loaded 9458 suffixes and 8 exceptions
> builtin PSL has 9458 suffixes and 8 exceptions
> psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-1.amazonaws.com, 
> PSL_TYPE_PRIVATE)=0 (expected 1)
> psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-1.amazonaws.com, 
> PSL_TYPE_PRIVATE|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
> psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-1.amazonaws.com, 
> PSL_TYPE_ANY)=0 (expected 1)
> psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-1.amazonaws.com, 
> PSL_TYPE_ANY|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
> psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-2.amazonaws.com, 
> PSL_TYPE_PRIVATE)=0 (expected 1)
> psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-2.amazonaws.com, 
> PSL_TYPE_PRIVATE|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
> psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-2.amazonaws.com, 
> PSL_TYPE_ANY)=0 (expected 1)
> psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-2.amazonaws.com, 
> PSL_TYPE_ANY|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
> psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-3.amazonaws.com, 
> PSL_TYPE_PRIVATE)=0 (expected 1)
> psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-3.amazonaws.com, 
> PSL_TYPE_PRIVATE|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
> psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-3.amazonaws.com, 
> PSL_TYPE_ANY)=0 (expected 1)
> psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-3.amazonaws.com, 
> PSL_TYPE_ANY|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
> psl_is_public_suffix2(webview-assets.cloud9.ap-southeast-1.amazonaws.com, 
> PSL_TYPE_PRIVATE)=0 (expected 1)
> psl_is_public_suffix2(webview-assets.cloud9.ap-southeast-1.amazonaws.com, 
> PSL_TYPE_PRIVATE|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
> psl_is_public_suffix2(webview-assets.cloud9.ap-southeast-1.amazonaws.com, 
> PSL_TYPE_ANY)=0 (expected 1)
> psl_is_public_suffix2(webview-assets.cloud9.ap-southeast-1.amazonaws.com, 
> PSL_TYPE_ANY|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
> psl_is_public_suffix2(webview-assets.cloud9.ap-southeast-2.amazonaws.com, 
> PSL_TYPE_PRIVATE)=0 (expected 1)
> psl_is_public_suffix2(webview-assets.cloud9.ap-southeast-2.amazonaws.com, 
> PSL_TYPE_PRIVATE|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
> psl_is_public_suffix2(webview-assets.cloud9.ap-southeast-2.amazonaws.com, 
> PSL_TYPE_ANY)=0 (expected 1)
> psl_is_public_suffix2(webview-assets.cloud9.ap-southeast-2.amazonaws.com, 
> PSL_TYPE_ANY|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
> psl_is_public_suffix2(webview-assets.cloud9.ca-central-1.amazonaws.com, 
> PSL_TYPE_PRIVATE)=0 (expected 1)
> psl_is_public_suffix2(webview-assets.cloud9.ca-central-1.amazonaws.com, 
> PSL_TYPE_PRIVATE|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
> psl_is_public_suffix2(webview-assets.cloud9.ca-central-1.amazonaws.com, 
> PSL_TYPE_ANY)=0 (expected 1)
> psl_is_public_suffix2(webview-assets.cloud9.ca-central-1.amazonaws.com, 
> PSL_TYPE_ANY|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
> psl_is_public_suffix2(webview-assets.cloud9.eu-central-1.amazonaws.com, 
> PSL_TYPE_PRIVATE)=0 (expected 1)
> psl_is_public_suffix2(webview-assets.cloud9.eu-central-1.amazonaws.com, 
> PSL_TYPE_PRIVATE|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
> psl_is_public_suffix2(webview-assets.cloud9.eu-central-1.amazonaws.com, 
> PSL_TYPE_ANY)=0 (expected 

Bug#1030680: marked as done (librust-criterion-0.3-dev: missing Breaks+Replaces: librust-criterion-dev (<< 0.4))

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2023 00:27:25 +0100
with message-id <167633084536.3113738.14306817291835594...@auryn.jones.dk>
and subject line Re: Bug#1030680: librust-criterion-0.3-dev: missing 
Breaks+Replaces: librust-criterion-dev (<< 0.4)
has caused the Debian Bug report #1030680,
regarding librust-criterion-0.3-dev: missing Breaks+Replaces: 
librust-criterion-dev (<< 0.4)
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.)


-- 
1030680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030680
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librust-criterion-0.3-dev
Version: 0.3.6-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../librust-criterion-0.3-dev_0.3.6-6_all.deb ...
  Unpacking librust-criterion-0.3-dev (0.3.6-6) ...
  dpkg: error processing archive 
/var/cache/apt/archives/librust-criterion-0.3-dev_0.3.6-6_all.deb (--unpack):
   trying to overwrite 
'/usr/share/cargo/registry/criterion-0.3.6/.cargo-checksum.json', which is also 
in package librust-criterion-dev 0.3.6-4
  Errors were encountered while processing:
   /var/cache/apt/archives/librust-criterion-0.3-dev_0.3.6-6_all.deb


cheers,

Andreas


librust-criterion-dev=0.3.6-4_librust-criterion-0.3-dev=0.3.6-6.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 0.3.6-7

Quoting Andreas Beckmann (2023-02-06 14:01:01)
> during a test with piuparts I noticed your package fails to upgrade from
> 'testing'.
> It installed fine in 'testing', then the upgrade to 'sid' fails
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.

This was fixed since version 0.3.6-7.

Thanks for reporting!

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature
--- End Message ---

Processed: tagging 1026713

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1026713 + fixed-upstream
Bug #1026713 [src:apache-directory-server] apache-directory-server: FTBFS due 
to compatibility issue with mina 2.2
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1026713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026713
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1030525: marked as done (src:stockfish: fails to migrate to testing for too long: FTBFS on armel and mipsel)

[Debian Bug Tracking System]

Your message dated Mon, 13 Feb 2023 21:16:05 +
with message-id 
and subject line Bug#1030525: fixed in stockfish 15.1-2
has caused the Debian Bug report #1030525,
regarding src:stockfish: fails to migrate to testing for too long: FTBFS on 
armel and mipsel
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.)


-- 
1030525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030525
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: stockfish
Version: 14.1-1
Severity: serious
Control: close -1 15.1-1
Tags: sid bookworm ftbfs
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 60 days as having a Release Critical bug in 
testing [1]. Your package src:stockfish has been trying to migrate for 
61 days [2]. Hence, I am filing this bug. Your package failed to build 
from source on armel and mipsel, while it built there successfully in 
the past.


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 bookworm, 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/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=stockfish



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: stockfish
Source-Version: 15.1-2
Done: Milan Zamazal 

We believe that the bug you reported is fixed in the latest version of
stockfish, 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 1030...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Milan Zamazal  (supplier of updated stockfish 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: Mon, 14 Feb 2023 19:12:38 +0100
Source: stockfish
Architecture: source
Version: 15.1-2
Distribution: unstable
Urgency: medium
Maintainer: Milan Zamazal 
Changed-By: Milan Zamazal 
Closes: 1030525
Changes:
 stockfish (15.1-2) unstable; urgency=medium
 .
   * Standards 4.6.2 (no real change).
   * Make sure -latomic is used on armel and mipsel; closes: #1030525.
Checksums-Sha1:
 928053392bd1906a055cce74f5bd99229a713206 1729 stockfish_15.1-2.dsc
 c3709c5de208660bd74425f4ee45fda7b0748725 16624 stockfish_15.1-2.debian.tar.xz
 b769963406af90d5234683793f32ef590958f75f 5955 stockfish_15.1-2_amd64.buildinfo
Checksums-Sha256:
 d231b00affcc21c1602a09692f90a13563018e772fbb994b693c47d3ce8c5bb8 1729 
stockfish_15.1-2.dsc
 32c386c36045e4e56659a32d99bae5950a23038190b155cc6a8d3af9f7fc9c43 16624 
stockfish_15.1-2.debian.tar.xz
 a46a987d41c56b76ef4bfd02c3e959ee58663f95d31661423a665eca5c47f6ec 5955 
stockfish_15.1-2_amd64.buildinfo
Files:
 92ace99b848a5ae32b5cc8e7e53af315 1729 games optional stockfish_15.1-2.dsc
 a0f81964217a4b100471c5b931da8b8e 16624 games optional 
stockfish_15.1-2.debian.tar.xz
 5e5897ae2807458c92707b2ca4f52094 5955 games optional 
stockfish_15.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEEPv4PPfDJjii4qBxHFNAaCK/Ym+MFAmPqnOUPHHBkbUBkZWJp
YW4ub3JnAAoJEBTQGgiv2Jvj9qsQAIa+Yl2FKC1tWh/QABNQg5RA3/EJq8GrE2cQ
kqce9qRxLxwaEOLeC58vb0AjAOLOQ8vmhe+TCts6kFwEijJgWdYL5UBqRfxNP+x3
Mo6/2j2fKF6vg5qVfOSIbGSTSYuQj6efDvYiv12fiSfJC56HUa9Pq69Mi2FP0m1a

Bug#1031104: marked as done (minexpert2: FTBFS (error: ‘QMouseEvent::QMouseEvent(QEvent::Type, const QPointF&, Qt::MouseButton, Qt::MouseButtons, Qt::KeyboardModifiers, const QPointingDevice*)’ is dep

[Debian Bug Tracking System]

Your message dated Mon, 13 Feb 2023 21:11:06 +
with message-id 
and subject line Bug#1031104: fixed in minexpert2 8.6.3-1
has caused the Debian Bug report #1031104,
regarding minexpert2: FTBFS (error: ‘QMouseEvent::QMouseEvent(QEvent::Type, 
const QPointF&, Qt::MouseButton, Qt::MouseButtons, Qt::KeyboardModifiers, const 
QPointingDevice*)’ is deprecated)
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.)


-- 
1031104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031104
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:minexpert2
Version: 8.6.2-2
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
PATH: 
/<>/doc/user-manual/scripts:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
dh binary-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
PATH: 
/<>/doc/user-manual/scripts:/<>/doc/user-manual/scripts:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
mkdir -p debian/build
mkdir -p debian/tmp
cd debian/build && cmake -DCMAKE_BUILD_TYPE=Release -DBUILD_USER_MANUAL=1 
-DCMAKE_INSTALL_PREFIX=/usr ../..
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done

[...]

[ 71%] Building CXX object 
src/CMakeFiles/minexpert2.dir/gui/BasePlotCompositeWidget.cpp.o
cd /<>/debian/build/src && /usr/bin/c++ -DQT_CORE5COMPAT_LIB -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_NO_DEBUG_OUTPUT -DQT_PRINTSUPPORT_LIB 
-DQT_SVG_LIB -DQT_WIDGETS_LIB -DQT_XML_LIB -I/<>/debian/build/src -I/<>/src 
-I/<>/debian/build/src/minexpert2_autogen/include -I/<>/debian/build -I/<> -isystem 
/usr/include/x86_64-linux-gnu/qt6/QtWidgets -isystem /usr/include/x86_64-linux-gnu/qt6 -isystem /usr/include/x86_64-linux-gnu/qt6/QtCore -isystem 
/usr/lib/x86_64-linux-gnu/qt6/mkspecs/linux-g++ -isystem /usr/include/x86_64-linux-gnu/qt6/QtGui -isystem /usr/include/x86_64-linux-gnu/qt6/QtXml -isystem 
/usr/include/x86_64-linux-gnu/qt6/QtSvg -isystem /usr/include/x86_64-linux-gnu/qt6/QtPrintSupport -isystem /usr/include/IsoSpec++ -isystem /usr/include/pappsomspp -isystem 
/usr/include/QuaZip-Qt6-1.4 -isystem /usr/include/QuaZip-Qt6-1.4/quazip -isystem /usr/include/x86_64-linux-gnu/qt6/QtCore5Compat -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fopenmp -O3 -DNDEBUG   -Wno-unknown-pragmas -Wall -pedantic -Wextra -Werror 
-fPIC -std=gnu++17 -MD -MT src/CMakeFiles/minexpert2.dir/gui/BasePlotCompositeWidget.cpp.o -MF CMakeFiles/minexpert2.dir/gui/BasePlotCompositeWidget.cpp.o.d -o 
CMakeFiles/minexpert2.dir/gui/BasePlotCompositeWidget.cpp.o -c /<>/src/gui/BasePlotCompositeWidget.cpp
[ 72%] Building CXX object 
src/CMakeFiles/minexpert2.dir/gui/BaseTracePlotCompositeWidget.cpp.o
cd /<>/debian/build/src && /usr/bin/c++ -DQT_CORE5COMPAT_LIB -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_NO_DEBUG_OUTPUT -DQT_PRINTSUPPORT_LIB 
-DQT_SVG_LIB -DQT_WIDGETS_LIB -DQT_XML_LIB -I/<>/debian/build/src -I/<>/src 
-I/<>/debian/build/src/minexpert2_autogen/include -I/<>/debian/build -I/<> -isystem 
/usr/include/x86_64-linux-gnu/qt6/QtWidgets -isystem /usr/include/x86_64-linux-gnu/qt6 -isystem /usr/include/x86_64-linux-gnu/qt6/QtCore -isystem 
/usr/lib/x86_64-linux-gnu/qt6/mkspecs/linux-g++ -isystem /usr/include/x86_64-linux-gnu/qt6/QtGui -isystem /usr/include/x86_64-linux-gnu/qt6/QtXml -isystem 
/usr/include/x86_64-linux-gnu/qt6/QtSvg -isystem /usr/include/x86_64-linux-gnu/qt6/QtPrintSupport -isystem /usr/include/IsoSpec++ -isystem /usr/include/pappsomspp -isystem 
/usr/include/QuaZip-Qt6-1.4 -isystem /usr/include/QuaZip-Qt6-1.4/quazip -isystem /usr/include/x86_64-linux-gnu/qt6/QtCore5Compat -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fopenmp -O3 -DNDEBUG   -Wno-unknown-pragmas -Wall -pedantic -Wextra -Werror 
-fPIC -std=gnu++17 -MD -MT src/CMakeFiles/minexpert2.dir/gui/BaseTracePlotCompositeWidget.cpp.o -MF CMakeFiles/minexpert2.dir/gui/BaseTracePlotCompositeWidget.cpp.o.d -o 
CMakeFiles/minexpert2.dir/gui/BaseTracePlotCompositeWidget.cpp.o -c /<>/src/gui/BaseTracePlotCompositeWidget.cpp
/<>/src/gui/BaseTracePlotCompositeWidget.cpp: In member function 
‘virtual void 

Bug#1024047: python-line-profiler

[Julian Gilbey]

Just an FYI: though ubelt is a requirement for running the tests, a
much more serious problem is that python-line-profiler requires an
alpha version of Cython 3.0.0 to compile, and that is not (yet?)
packaged for Debian.  Hopefully at some point over the next two years,
Cython 3.0 will mature enough to actually be released, and then it
will be possible to upgrade python-line-profiler.

Best wishes,

   Julian

Bug#1031241: marked as done (aspic: no upstream URL in copyright file)

[Debian Bug Tracking System]

Your message dated Mon, 13 Feb 2023 20:49:25 +
with message-id 
and subject line Bug#1031241: fixed in aspic 2.00+dfsg-2
has caused the Debian Bug report #1031241,
regarding aspic: no upstream URL in copyright file
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.)


-- 
1031241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031241
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: aspic
Version: 2.00+dfsg-1
Severity: serious
Justification: Policy 12.5

The copyright file doesn't say where the upstream sources were obtained.

--
Jakub Wilk
--- End Message ---
--- Begin Message ---
Source: aspic
Source-Version: 2.00+dfsg-2
Done: Bastian Germann 

We believe that the bug you reported is fixed in the latest version of
aspic, 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 1031...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated aspic 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: Mon, 13 Feb 2023 21:18:22 +0100
Source: aspic
Architecture: source
Version: 2.00+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Bastian Germann 
Closes: 1031241
Changes:
 aspic (2.00+dfsg-2) unstable; urgency=medium
 .
   * QA upload.
   * d/copyright: Add Source (Closes: #1031241).
Checksums-Sha1:
 9b7dfb8bb474a4ccce3871d3ff99d0161fb57bfc 1550 aspic_2.00+dfsg-2.dsc
 b4e93f4b1ce5e4bfccc0c249c7a25e29e7a277f9 2504 aspic_2.00+dfsg-2.debian.tar.xz
 d24b000fb931ea4798921dc33f133a7371996879 6917 
aspic_2.00+dfsg-2_source.buildinfo
Checksums-Sha256:
 a5f05183f0eba60990c693bbc1105f8d3f65520f585111c377edbc8da615b9a1 1550 
aspic_2.00+dfsg-2.dsc
 83ab955e150f12e46e963f39ad36fa9b5dc7b82a1d268af8fa225f7709f61444 2504 
aspic_2.00+dfsg-2.debian.tar.xz
 44bed182db56f8a347e5f69a6fe9460f7628119ce60de0c8ccaab106c1de5910 6917 
aspic_2.00+dfsg-2_source.buildinfo
Files:
 83998a6f663d501c729413ccb02f4c68 1550 tex optional aspic_2.00+dfsg-2.dsc
 6a19e39c09c51dafe39d3ceae3544290 2504 tex optional 
aspic_2.00+dfsg-2.debian.tar.xz
 51a6c43d134e00c59977f3b645b51dd5 6917 tex optional 
aspic_2.00+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmPqm7YQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFEtbC/kB7vTw9t5AlrgK+ZexZ70Y1hk0xPKulQGy
pWXIkh2TYowjOyG18gLSMhyejByhWwEGe0Zh4m5eT4Ccpw+c+c/cHTrqma+jni2j
tPZHcdHa0ANZAlqfLLAUlvUl7WCCguy6lpcmEdjnetRB9qRhaWZ3R9E1g7RTwBOC
CacaEoScC+YLqiEhyvf0/gmheKaQCwjr6KX4iLebIZdHsst94BUEcOlPn3k5PAU5
4qHi5+ejSzTaRkuQWmsozoAfrjI2D3glRLY1+fShnVOcteQIT80YQQe4RMgDY88V
oo5nXWPFb1HvuavhjRi5GbWdwfiB/V2RWhjfSI+hmuLCZEja6f1w7bw9zUDcAYcV
Z3vMMlXRJ5KRByDy4Nu3yvRZRguKoKj+jnzeFg2WHI9am6yxo+mu4IhaAyzEzEiH
SDvYd48GFkvYJ6hR0a9i8MITZ7JxBoZvWubzwwA3kXx5z1N9GFPNiLhHNIN5jA0+
BYYlf+TywyW1Yg2N7lTMdTzRVbi89FE=
=fhSE
-END PGP SIGNATURE End Message ---

Bug#1031233: hplip: hp-plugin unable to download plugin

[Brian Potkin]

tags 1031233 upstream
merge 1031233 1029459
severity 103123 important
thanks



On Mon 13 Feb 2023 at 09:20:49 -0800, Curtis Dean Smith wrote:

> Package: hplip
> Version: 3.22.10+dfsg0-1
> Severity: grave
> Justification: renders package unusable
> X-Debbugs-Cc: smit...@hush.com
> 
> Dear Maintainer,
> 
>* What led up to the situation?
> 
> The cups hplip suddenly stopped working and initiated the plugin
>download, which failed.
>  
> 
> -- Package-specific info:
> Saving output in log file: /home/cds/hp-check.log
> 
> HP Linux Imaging and Printing System (ver. 3.22.10)
> Dependency/Version Check Utility ver. 15.1
> 
> Copyright (c) 2001-18 HP Development Company, LP
> This software comes with ABSOLUTELY NO WARRANTY.
> This is free software, and you are welcome to distribute it
> under certain conditions. See COPYING file for more details.
> 
> Note: hp-check can be run in three modes:
> 1. Compile-time check mode (-c or --compile): Use this mode before compiling 
> the
> HPLIP supplied tarball (.tar.gz or .run) to determine if the proper 
> dependencies
> are installed to successfully compile HPLIP.  
>   
> 2. Run-time check mode (-r or --run): Use this mode to determine if a distro  
>   
> supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball 
>   
> has the proper dependencies installed to successfully run.
>   
> 3. Both compile- and run-time check mode (-b or --both) (Default): This mode  
>   
> will check both of the above cases (both compile- and run-time dependencies). 
>   
> 
> Check types:  
>   
> a. EXTERNALDEP - External Dependencies
>   
> b. GENERALDEP - General Dependencies (required both at compile and run time)  
>   
> c. COMPILEDEP - Compile time Dependencies 
>   
> d. [All are run-time checks]  
>   
> PYEXT SCANCONF QUEUES PERMISSION  
>   
> 
> Status Types:
> OK
> MISSING   - Missing Dependency or Permission or Plug-in
> INCOMPAT  - Incompatible dependency-version or Plugin-version
> 
> Traceback (most recent call last):
>   File "/usr/bin/hp-check", line 860, in 
> dep =  DependenciesCheck(MODE_CHECK,INTERACTIVE_MODE,ui_toolkit)
>^
>   File "/usr/bin/hp-check", line 175, in __init__
> self.core = CoreInstall(mode, ui_mode, ui_toolkit)
> ^^
>   File "/usr/share/hplip/installer/core_install.py", line 240, in __init__
> self.passwordObj = password.Password(ui_mode)
>^^
>   File "/usr/share/hplip/base/password.py", line 94, in __init__
> self.__readAuthType()  # self.__authType
> ^
>   File "/usr/share/hplip/base/password.py", line 119, in __readAuthType
> distro_name = get_distro_std_name(os_name)
>   ^^^
> NameError: name 'get_distro_std_name' is not defined. Did you mean: 
> 'get_distro_name'?

Thank you for your report, Curtis. This looks like #1029459:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029459

A nice confirmation that something is amiss.

Regards,

Brian.

Bug#1031228: nvidia-driver: Broken dependencies

[Fernando Santagata]

Hello,
I'm having the same problem. Apparently the cause is the lack of
firmware-nvidia-gsp, which is now a virtual package:

# apt install nvidia-driver
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 nvidia-kernel-dkms : Depends: firmware-nvidia-gsp (= 525.85.12) but it is
not installable or
   firmware-nvidia-gsp-525.85.12 but it is not
installable
# apt install firmware-nvidia-gsp
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package firmware-nvidia-gsp is not available, but is referred to by another
package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'firmware-nvidia-gsp' has no installation candidate

Is it really obsolete, and in this case it should not be in the dependency
tree of nvidia-driver, or is it just to be released?

-- 
Fernando Santagata

Processed (with 2 errors): Re: Bug#1031233: hplip: hp-plugin unable to download plugin

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1031233 upstream
Bug #1031233 [hplip] hplip: hp-plugin unable to download plugin
Added tag(s) upstream.
> merge 1031233 1029459
Bug #1031233 [hplip] hplip: hp-plugin unable to download plugin
Unable to merge bugs because:
forwarded of #1029459 is 'https://bugs.launchpad.net/hplip/+bug/2003739' not ''
severity of #1029459 is 'important' not 'grave'
Failed to merge 1031233: Did not alter merged bugs.

> severity 103123 important
Failed to set severity of Bug 103123 to important: Not altering archived bugs; 
see unarchive.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1029459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029459
1031233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031233
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1031241: aspic: no upstream URL in copyright file

[Jakub Wilk]

Package: aspic
Version: 2.00+dfsg-1
Severity: serious
Justification: Policy 12.5

The copyright file doesn't say where the upstream sources were obtained.

--
Jakub Wilk

Bug#1030767:

[Salvatore Bonaccorso]

Hi,

On Tue, Feb 07, 2023 at 11:20:32AM +, Waylon Liu (Cybit) wrote:
> official patch: 
> https://github.com/ImageMagick/ImageMagick6/commit/3c5188b41902a909e163492fb0c19e49efefcefe

This is likely not enough. There were several iterations on the
commits, and believe the last one valid change would be
https://github.com/ImageMagick/ImageMagick6/commit/d77c01e560e973177feed4915ffd7dd1a45fd763
.

Regards,
Salvatore

Bug#1031238: debci: fails for source packages in non-free-firmware

[Andreas Beckmann]

Package: debci
Version: 3.5.2+nmu1
Severity: serious
X-Debbugs-Cc: Cyril Brulebois 

src:nvidia-graphics-drivers recently moved from non-free to
non-free-firmware since the firmware-nvidia-gsp binary package was moved
to that section, too.

Tracker reports
 autopkgtest for nvidia-graphics-drivers/n/a: amd64: Regression ♻ (reference 
♻), ...
not sure whether the version "n/a" comes from tracker or debci.

Autopkgtest regresses with
https://ci.debian.net/data/autopkgtest/testing/amd64/n/nvidia-graphics-drivers/31312665/log.gz
...
autopkgtest [14:12:05]: testbed dpkg architecture: amd64
autopkgtest [14:12:05]: testbed running kernel: Linux 5.10.0-21-cloud-amd64 #1 
SMP Debian 5.10.162-1 (2023-01-21)
autopkgtest [14:12:06]:  apt-source nvidia-graphics-drivers
blame: nvidia-graphics-drivers
badpkg: rules extract failed with exit code 1
autopkgtest [14:12:06]: ERROR: erroneous package: rules extract failed with 
exit code 1

My guess is that it fails since it cannot find the source package
anywhere.


Andreas

Processed: severity of 1030767 is grave, fixed 1030767 in 8:6.9.11.60+dfsg-1.3+deb11u1 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1030767 grave
Bug #1030767 [imagemagick] imagemagick: CVE-2022-44267 CVE-2022-44268
Severity set to 'grave' from 'important'
> fixed 1030767 8:6.9.11.60+dfsg-1.3+deb11u1
Bug #1030767 [imagemagick] imagemagick: CVE-2022-44267 CVE-2022-44268
Marked as fixed in versions imagemagick/8:6.9.11.60+dfsg-1.3+deb11u1.
> found 1030767 8:6.9.11.60+dfsg-1.5
Bug #1030767 [imagemagick] imagemagick: CVE-2022-44267 CVE-2022-44268
Marked as found in versions imagemagick/8:6.9.11.60+dfsg-1.5.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1030767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030767
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1031140, reassign 1027335 to src:pairtools, fixed 1027335 in 1.0.2-1 ..., tagging 1031184 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1031140 + help
Bug #1031140 [sendmail-bin] sendmail: please integrate natively with systemd
Added tag(s) help.
> reassign 1027335 src:pairtools 0.3.0-3.2
Bug #1027335 {Done: Nilesh Patra } [src:python-pysam] 
pairtools -- current repo in salsa FTBFS
Bug reassigned from package 'src:python-pysam' to 'src:pairtools'.
No longer marked as found in versions python-pysam/0.20.0+ds-2.
No longer marked as fixed in versions pairtools/1.0.2-1.
Bug #1027335 {Done: Nilesh Patra } [src:pairtools] pairtools 
-- current repo in salsa FTBFS
Marked as found in versions pairtools/0.3.0-3.2.
> fixed 1027335 1.0.2-1
Bug #1027335 {Done: Nilesh Patra } [src:pairtools] pairtools 
-- current repo in salsa FTBFS
Marked as fixed in versions pairtools/1.0.2-1.
> notfound 1025453 0.3.61-1
Bug #1025453 {Done: Dylan Aïssi } [pipewire] pipewire: 
Upgrade to pipewire 0.3.60-1 breaks sound
No longer marked as found in versions pipewire/0.3.61-1.
> notfixed 1025453 0.3.60-2
Bug #1025453 {Done: Dylan Aïssi } [pipewire] pipewire: 
Upgrade to pipewire 0.3.60-1 breaks sound
No longer marked as fixed in versions pipewire/0.3.60-2.
> found 1025453 0.3.61-1
Bug #1025453 {Done: Dylan Aïssi } [pipewire] pipewire: 
Upgrade to pipewire 0.3.60-1 breaks sound
Marked as found in versions pipewire/0.3.61-1 and reopened.
> reassign 1031189 libogre-1.12-dev
Bug #1031189 [libogre-dev] libogre-dev: Does not automatically derive plugin 
path
Warning: Unknown package 'libogre-dev'
Bug reassigned from package 'libogre-dev' to 'libogre-1.12-dev'.
No longer marked as found in versions libogre-1.12-dev.
Ignoring request to alter fixed versions of bug #1031189 to the same values 
previously set
> tags 1031184 + sid bookworm
Bug #1031184 [adapta-kde] adapta-kde: Development has completely and officially 
ended
Added tag(s) bookworm and sid.
> tags 1010199 + sid bookworm
Bug #1010199 [adapta-gtk-theme] adapta-gtk-theme: Development has completely 
and officially ended
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1010199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010199
1025453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025453
1027335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027335
1031140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031140
1031184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031184
1031189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031189
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1030982: gscan2pdf: Not a JPEG file: starts with 0x00 0x00 (was: Segmentation fault)

[Jeff]

On 11/02/2023 15:50, Janusz S. Bień wrote:

The failure log was
[log1 (application/octet-stream, attachment)]


That file ends with:

DEBUG - signal 'started-process' emitted with message: Scanning page 1 of 1
INFO - gscan2pdf: scanning image of size 1275x1784 pixels at 24 bits/pixel
INFO - gscan2pdf: acquiring RGB frame

So you are saying that in the terminal, you then additionally received 
the message:


Not a JPEG file: starts with 0x00 0x00

and then it segfaulted?

And that now you can't reproduce the problem?

What happens if you try the following from the command line:

scanimage --device="xerox_mfp:tcp  192.168.0.155" --batch

?


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1031228: marked as done (nvidia-driver: Broken depencies)

[Debian Bug Tracking System]

Your message dated Mon, 13 Feb 2023 18:29:00 +0100
with message-id 
and subject line Re: Bug#1031228: nvidia-driver: Broken depencies
has caused the Debian Bug report #1031228,
regarding nvidia-driver: Broken depencies
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.)


-- 
1031228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031228
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nvidia-driver
Version: 525.85.12
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I'm trying to install the package nvidia-driver on sid.
It fails with the following message:

The following packages have unmet dependencies:
 nvidia-driver : Depends: nvidia-kernel-dkms (= 525.85.12-1) but it is not 
installable or
  nvidia-kernel-525.85.12 or
  nvidia-open-kernel-525.85.12 but it is not 
installable or
  nvidia-open-kernel-525.85.12 but it is not installable
E: Unable to correct problems, you have held broken packages.


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (990, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-4-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=de_DE.utf8 (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 nvidia-driver depends on:
pn  nvidia-alternative   
pn  nvidia-driver-bin
pn  nvidia-driver-libs   
ii  nvidia-installer-cleanup 20220217+2
pn  nvidia-kernel-dkms | nvidia-kernel-525.85.12 | nvidia-open-kern  
el-525.85.12 | nvidia-open-kernel-525.85.12
pn  nvidia-legacy-check  
pn  nvidia-support   
pn  nvidia-vdpau-driver  
pn  xserver-xorg-video-nvidia

Versions of packages nvidia-driver recommends:
pn  libnvidia-cfg1   
pn  nvidia-persistenced  
pn  nvidia-settings  

Versions of packages nvidia-driver suggests:
pn  nvidia-kernel-dkms | nvidia-kernel-source | nvidia-open-kernel-sour  
ce | nvidia-open-kernel-source


TIA,
Michael
--- End Message ---
--- Begin Message ---

On 13/02/2023 16.27, Michael Tatge wrote:

I'm trying to install the package nvidia-driver on sid.
It fails with the following message:


Please enable the new non-free-firmware archive section in addition to 
non-free in your apt sources configuration.


https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.en.html#non-free-split


Andreas--- End Message ---

Bug#1031233: hplip: hp-plugin unable to download plugin

[Curtis Dean Smith]

Package: hplip
Version: 3.22.10+dfsg0-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: smit...@hush.com

Dear Maintainer,

   * What led up to the situation?

The cups hplip suddenly stopped working and initiated the plugin
   download, which failed.
 

-- Package-specific info:
Saving output in log file: /home/cds/hp-check.log

HP Linux Imaging and Printing System (ver. 3.22.10)
Dependency/Version Check Utility ver. 15.1

Copyright (c) 2001-18 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

Note: hp-check can be run in three modes:
1. Compile-time check mode (-c or --compile): Use this mode before compiling the
HPLIP supplied tarball (.tar.gz or .run) to determine if the proper dependencies
are installed to successfully compile HPLIP.
2. Run-time check mode (-r or --run): Use this mode to determine if a distro
supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball   
has the proper dependencies installed to successfully run.  
3. Both compile- and run-time check mode (-b or --both) (Default): This mode
will check both of the above cases (both compile- and run-time dependencies).   

Check types:
a. EXTERNALDEP - External Dependencies  
b. GENERALDEP - General Dependencies (required both at compile and run time)
c. COMPILEDEP - Compile time Dependencies   
d. [All are run-time checks]
PYEXT SCANCONF QUEUES PERMISSION

Status Types:
OK
MISSING   - Missing Dependency or Permission or Plug-in
INCOMPAT  - Incompatible dependency-version or Plugin-version

Traceback (most recent call last):
  File "/usr/bin/hp-check", line 860, in 
dep =  DependenciesCheck(MODE_CHECK,INTERACTIVE_MODE,ui_toolkit)
   ^
  File "/usr/bin/hp-check", line 175, in __init__
self.core = CoreInstall(mode, ui_mode, ui_toolkit)
^^
  File "/usr/share/hplip/installer/core_install.py", line 240, in __init__
self.passwordObj = password.Password(ui_mode)
   ^^
  File "/usr/share/hplip/base/password.py", line 94, in __init__
self.__readAuthType()  # self.__authType
^
  File "/usr/share/hplip/base/password.py", line 119, in __readAuthType
distro_name = get_distro_std_name(os_name)
  ^^^
NameError: name 'get_distro_std_name' is not defined. Did you mean: 
'get_distro_name'?

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-3-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages hplip depends on:
ii  adduser3.131
ii  cups   2.4.2-1+b2
ii  hplip-data 3.22.10+dfsg0-1
ii  libc6  2.36-8
ii  libcups2   2.4.2-1+b2
ii  libdbus-1-31.14.6-1
ii  libhpmud0  3.22.10+dfsg0-1
ii  libpython3.11  3.11.1-2
ii  libsane-hpaio  3.22.10+dfsg0-1
ii  libsane1   1.1.1-6+b2
ii  lsb-base   11.6
ii  printer-driver-hpcups  3.22.10+dfsg0-1
ii  python33.11.1-3
ii  python3-dbus   1.3.2-4+b1
ii  python3-gi 3.42.2-3+b1
ii  python3-pexpect4.8.0-4
ii  python3-pil9.4.0-1.1+b1
ii  python3-reportlab  3.6.12-1
ii  sysvinit-utils [lsb-base]  3.06-2
ii  wget   1.21.3-1+b2
ii  xz-utils   5.4.1-0.1

Versions of packages hplip recommends:
ii  avahi-daemon  0.8-8
ii  policykit-1   122-3
ii  printer-driver-postscript-hp  3.22.10+dfsg0-1
ii  sane-utils1.1.1-6+b2

Versions of packages hplip suggests:
ii  hplip-doc  3.22.10+dfsg0-1
ii  hplip-gui  3.22.10+dfsg0-1
ii  python3-notify20.3-5
pn  system-config-printer  

-- no debconf information

Bug#1027632: marked as done (libwww-curl-perl: FTBFS: curlopt-constants.c:19:51: error: ‘CURL_DEPRECATED’ undeclared (first use in this function))

[Debian Bug Tracking System]

Your message dated Mon, 13 Feb 2023 16:36:22 +
with message-id 
and subject line Bug#1027632: fixed in libwww-curl-perl 4.17-9
has caused the Debian Bug report #1027632,
regarding libwww-curl-perl: FTBFS: curlopt-constants.c:19:51: error: 
‘CURL_DEPRECATED’ undeclared (first use in this function)
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.)


-- 
1027632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027632
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libwww-curl-perl
Version: 4.17-8
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230101 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> x86_64-linux-gnu-gcc -c  -I/usr/include/x86_64-linux-gnu -D_REENTRANT 
> -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe 
> -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -DVERSION=\"4.17\" 
> -DXS_VERSION=\"4.17\" -fPIC "-I/usr/lib/x86_64-linux-gnu/perl/5.36/CORE"   
> Curl.c
> Curl.xs: In function ‘callback_index’:
> Curl.xs:109:9: warning: ‘CURLOPT_PROGRESSFUNCTION’ is deprecated: since 
> 7.32.0. Use CURLOPT_XFERINFOFUNCTION [-Wdeprecated-declarations]
>   109 | case CURLOPT_PROGRESSFUNCTION:
>   | ^~~~
> In file included from Curl.xs:17:
> /usr/include/x86_64-linux-gnu/curl/curl.h:1295:3: note: declared here
>  1295 |   CURLOPTDEPRECATED(CURLOPT_PROGRESSFUNCTION, 
> CURLOPTTYPE_FUNCTIONPOINT, 56,
>   |   ^
> Curl.xs: In function ‘perl_curl_form_delete’:
> Curl.xs:231:9: warning: ‘curl_formfree’ is deprecated: since 7.56.0. Use 
> curl_mime_free() [-Wdeprecated-declarations]
>   231 | curl_formfree(self->post);
>   | ^
> /usr/include/x86_64-linux-gnu/curl/curl.h:2606:1: note: declared here
>  2606 | curl_formfree(struct curl_httppost *form);
>   | ^
> In file included from Curl.xs:578:
> curlopt-constants.c: In function ‘constant’:
> curlopt-constants.c:19:51: error: ‘CURL_DEPRECATED’ undeclared (first use in 
> this function)
>19 | if (strEQ(name, "DEPRECATED")) return CURL_DEPRECATED;
>   |   ^~~
> curlopt-constants.c:19:51: note: each undeclared identifier is reported only 
> once for each function it appears in
> curlopt-constants.c:28:13: warning: ‘CURL_FORMADD_DISABLED’ is deprecated: 
> since 7.56.0.  [-Wdeprecated-declarations]
>28 | if (strEQ(name, "FORMADD_DISABLED")) return 
> CURL_FORMADD_DISABLED;
>   | ^~
> /usr/include/x86_64-linux-gnu/curl/curl.h:2555:3: note: declared here
>  2555 |   CURL_FORMADD_DISABLED   CURL_DEPRECATED(7.56.0, ""),
>   |   ^
> curlopt-constants.c:29:13: warning: ‘CURL_FORMADD_ILLEGAL_ARRAY’ is 
> deprecated: since 7.56.0.  [-Wdeprecated-declarations]
>29 | if (strEQ(name, "FORMADD_ILLEGAL_ARRAY")) return 
> CURL_FORMADD_ILLEGAL_ARRAY;
>   | ^~
> /usr/include/x86_64-linux-gnu/curl/curl.h:2553:3: note: declared here
>  2553 |   CURL_FORMADD_ILLEGAL_ARRAY  CURL_DEPRECATED(7.56.0, ""),
>   |   ^~
> curlopt-constants.c:30:13: warning: ‘CURL_FORMADD_INCOMPLETE’ is deprecated: 
> since 7.56.0.  [-Wdeprecated-declarations]
>30 | if (strEQ(name, "FORMADD_INCOMPLETE")) return 
> CURL_FORMADD_INCOMPLETE;
>   | ^~
> /usr/include/x86_64-linux-gnu/curl/curl.h:2552:3: note: declared here
>  2552 |   CURL_FORMADD_INCOMPLETE CURL_DEPRECATED(7.56.0, ""),
>   |   ^~~
> curlopt-constants.c:31:13: warning: ‘CURL_FORMADD_MEMORY’ is deprecated: 
> since 7.56.0.  [-Wdeprecated-declarations]
>31 | if (strEQ(name, "FORMADD_MEMORY")) return 
> CURL_FORMADD_MEMORY;
>   | ^~
> /usr/include/x86_64-linux-gnu/curl/curl.h:2548:3: note: declared here
>  2548 |   CURL_FORMADD_MEMORY CURL_DEPRECATED(7.56.0, ""),
>   |   ^~~
> curlopt-constants.c:32:13: warning: ‘CURL_FORMADD_NULL’ is deprecated: since 
> 7.56.0.  [-Wdeprecated-declarations]
>32 | if (strEQ(name, "FORMADD_NULL")) return CURL_FORMADD_NULL;
>   | ^~
> /usr/include/x86_64-linux-gnu/curl/curl.h:2550:3: note: declared here
>  2550 |   CURL_FORMADD_NULL   CURL_DEPRECATED(7.56.0, ""),
>  

Processed: reassign 1030434 to src:opensc, tagging 1030434, affects 1030434

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1030434 src:opensc 0.23.0-0.1
Bug #1030434 [src:opensc] rauc: FTBFS: tests failed writing: Error opening file 
?/tmp/tmp.I4dlWcaK4g/notexisting/out.raucb?: No such file or directory
Ignoring request to reassign bug #1030434 to the same package
Bug #1030434 [src:opensc] rauc: FTBFS: tests failed writing: Error opening file 
?/tmp/tmp.I4dlWcaK4g/notexisting/out.raucb?: No such file or directory
Ignoring request to alter found versions of bug #1030434 to the same values 
previously set
> tags 1030434 + fixed-upstream
Bug #1030434 [src:opensc] rauc: FTBFS: tests failed writing: Error opening file 
?/tmp/tmp.I4dlWcaK4g/notexisting/out.raucb?: No such file or directory
Ignoring request to alter tags of bug #1030434 to the same tags previously set
> affects 1030434 + rauc
Bug #1030434 [src:opensc] rauc: FTBFS: tests failed writing: Error opening file 
?/tmp/tmp.I4dlWcaK4g/notexisting/out.raucb?: No such file or directory
Ignoring request to set affects of bug 1030434 to the same value previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1030434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030434
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1030434: rauc: FTBFS: tests failed writing: Error opening file ?/tmp/tmp.I4dlWcaK4g/notexisting/out.raucb?: No such file or directory

[Bastian Germann]

I am uploading a NMU to DELAYED/10 with the attached debdiff.diff -Nru opensc-0.23.0/debian/changelog opensc-0.23.0/debian/changelog
--- opensc-0.23.0/debian/changelog  2023-01-10 18:00:21.0 +0100
+++ opensc-0.23.0/debian/changelog  2023-02-13 17:13:20.0 +0100
@@ -1,3 +1,10 @@
+opensc (0.23.0-0.2) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Fix rauc build (Closes: #1030434)
+
+ -- Bastian Germann   Mon, 13 Feb 2023 17:13:20 +0100
+
 opensc (0.23.0-0.1) unstable; urgency=medium
 
   * Non-maintainer upload
diff -Nru opensc-0.23.0/debian/patches/0002-Fix-private-key-import.patch 
opensc-0.23.0/debian/patches/0002-Fix-private-key-import.patch
--- opensc-0.23.0/debian/patches/0002-Fix-private-key-import.patch  
1970-01-01 01:00:00.0 +0100
+++ opensc-0.23.0/debian/patches/0002-Fix-private-key-import.patch  
2023-02-13 16:52:41.0 +0100
@@ -0,0 +1,29 @@
+Origin: upstream, 9294183e07ff4944e3f5e590f343f5727636767e
+From: Jakub Jelen 
+Date: Thu, 1 Dec 2022 20:08:53 +0100
+Subject: pkcs11-tool: Fix private key import
+
+---
+ src/tools/pkcs11-tool.c | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/src/tools/pkcs11-tool.c b/src/tools/pkcs11-tool.c
+index aae205fe2c..cfee8526d5 100644
+--- a/src/tools/pkcs11-tool.c
 b/src/tools/pkcs11-tool.c
+@@ -3669,13 +3669,13 @@ parse_rsa_pkey(EVP_PKEY *pkey, int private, struct 
rsakey_info *rsa)
+   RSA_get0_factors(r, _p, _q);
+   RSA_get0_crt_params(r, _dmp1, _dmq1, _iqmp);
+ #else
+-  if (EVP_PKEY_get_bn_param(pkey, OSSL_PKEY_PARAM_RSA_FACTOR1, 
_d) != 1 ||
++  if (EVP_PKEY_get_bn_param(pkey, OSSL_PKEY_PARAM_RSA_D, _d) != 
1 ||
+   EVP_PKEY_get_bn_param(pkey, 
OSSL_PKEY_PARAM_RSA_FACTOR1, _p) != 1 ||
+   EVP_PKEY_get_bn_param(pkey, 
OSSL_PKEY_PARAM_RSA_FACTOR2, _q) != 1 ||
+   EVP_PKEY_get_bn_param(pkey, 
OSSL_PKEY_PARAM_RSA_EXPONENT1, _dmp1) != 1 ||
+   EVP_PKEY_get_bn_param(pkey, 
OSSL_PKEY_PARAM_RSA_EXPONENT2, _dmq1) != 1 ||
+-  EVP_PKEY_get_bn_param(pkey, 
OSSL_PKEY_PARAM_RSA_EXPONENT3, _iqmp) != 1) {
+   util_fatal("OpenSSL error during RSA private key 
parsing");
++  EVP_PKEY_get_bn_param(pkey, 
OSSL_PKEY_PARAM_RSA_COEFFICIENT1, _iqmp) != 1) {
+   }
+ #endif
+   RSA_GET_BN(rsa, private_exponent, r_d);
diff -Nru opensc-0.23.0/debian/patches/0003-Log-OpenSSL-errors.patch 
opensc-0.23.0/debian/patches/0003-Log-OpenSSL-errors.patch
--- opensc-0.23.0/debian/patches/0003-Log-OpenSSL-errors.patch  1970-01-01 
01:00:00.0 +0100
+++ opensc-0.23.0/debian/patches/0003-Log-OpenSSL-errors.patch  2023-02-13 
16:51:41.0 +0100
@@ -0,0 +1,50 @@
+Origin: upstream, cff91cf6167743bdd59285150c4ef19802ed2644
+From: Jakub Jelen 
+Date: Thu, 1 Dec 2022 20:11:41 +0100
+Subject: pkcs11-tool: Log more information on OpenSSL errors
+
+---
+ src/tools/pkcs11-tool.c | 15 ++-
+ 1 file changed, 6 insertions(+), 9 deletions(-)
+
+diff --git a/src/tools/pkcs11-tool.c b/src/tools/pkcs11-tool.c
+index cfee8526d5..f2e6b1dd91 100644
+--- a/src/tools/pkcs11-tool.c
 b/src/tools/pkcs11-tool.c
+@@ -3641,10 +3641,8 @@ parse_rsa_pkey(EVP_PKEY *pkey, int private, struct 
rsakey_info *rsa)
+   const BIGNUM *r_dmp1, *r_dmq1, *r_iqmp;
+   r = EVP_PKEY_get1_RSA(pkey);
+   if (!r) {
+-  if (private)
+-  util_fatal("OpenSSL error during RSA private key 
parsing");
+-  else
+-  util_fatal("OpenSSL error during RSA public key 
parsing");
++  util_fatal("OpenSSL error during RSA %s key parsing: %s", 
private ? "private" : "public",
++  ERR_error_string(ERR_peek_last_error(), NULL));
+   }
+ 
+   RSA_get0_key(r, _n, _e, NULL);
+@@ -3654,10 +3652,8 @@ parse_rsa_pkey(EVP_PKEY *pkey, int private, struct 
rsakey_info *rsa)
+   BIGNUM *r_dmp1 = NULL, *r_dmq1 = NULL, *r_iqmp = NULL;
+   if (EVP_PKEY_get_bn_param(pkey, OSSL_PKEY_PARAM_RSA_N, _n) != 1 ||
+   EVP_PKEY_get_bn_param(pkey, OSSL_PKEY_PARAM_RSA_E, _e) != 1) {
+-  if (private)
+-  util_fatal("OpenSSL error during RSA private key 
parsing");
+-  else
+-  util_fatal("OpenSSL error during RSA public key 
parsing");
++  util_fatal("OpenSSL error during RSA %s key parsing: %s", 
private ? "private" : "public",
++  ERR_error_string(ERR_peek_last_error(), NULL));
+}
+ #endif
+   RSA_GET_BN(rsa, modulus, r_n);
+@@ -3674,8 +3670,9 @@ parse_rsa_pkey(EVP_PKEY *pkey, int private, struct 
rsakey_info *rsa)
+   EVP_PKEY_get_bn_param(pkey, 
OSSL_PKEY_PARAM_RSA_FACTOR2, _q) != 1 ||
+   EVP_PKEY_get_bn_param(pkey, 
OSSL_PKEY_PARAM_RSA_EXPONENT1, _dmp1) != 1 ||
+  

Bug#1031231: tries to overwrite /etc/cron.yearly/.placeholder from systemd-cron

[Felix Zielcke]

Package: cron-daemon-common
Version: 3.0pl1-159
Severity: serious

Hi,

cron-daemon-common can't be upgraded if systemd-cron is also installed:

Preparing to unpack .../cron-daemon-common_3.0pl1-159_all.deb ...
Unpacking cron-daemon-common (3.0pl1-159) over (3.0pl1-156) ...
dpkg: error processing archive 
/var/cache/apt/archives/cron-daemon-common_3.0pl1-159_all.deb (--unpack):
 trying to overwrite '/etc/cron.yearly/.placeholder', which is also in package 
systemd-cron 1.15.19-4
Errors were encountered while processing:
 /var/cache/apt/archives/cron-daemon-common_3.0pl1-159_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


AFAICS this hasn't been fixed in the already uploaded but not yet avaible 
3.0pl1-160

Bug#1030447: libgeo-distance-xs-perl: FTBFS: make[1]: *** [Makefile:1020: test_dynamic] Error 255

[gregor herrmann]

On Sat, 04 Feb 2023 13:26:55 +0100, gregor herrmann wrote:

> We can skip this test; or think about removing the package …
> 
> (The only reverse dependency is a Recommends in libgeo-distance-perl
> which I'm about to remove now.)

Gone from the CPAN, archived on GitHub …

Any objections to a removal bug?


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Bug#1011567: needs com.sun.javadoc migration

[Hans-Christoph Steiner]

Looks like doclava would need to be ported to use the API that replaces 
com.sun.javadoc:


https://docs.oracle.com/en/java/javase/11/docs/api/jdk.javadoc/jdk/javadoc/doclet/package-summary.html#migration

If someone does the migration, I can take care of the packaging updates.

Bug#1031230: spirv-tools: autopkgtest regression for glslang: undefined reference to spvtools::CreateAggressiveDCEPass etc.

[Simon McVittie]

Package: spirv-tools
Version: 2023.1-1
Severity: serious
Justification: https://release.debian.org/testing/rc_policy.txt 6a
User: debian...@lists.debian.org
Usertags: regression
X-Debbugs-Cc: debian...@lists.debian.org
Control: affects -1 + src:glslang

The test-case debian/tests/glslang-dev that I contributed
in glslang_11.1.0-4 has started failing with the upload of
spirv-tools_2023.1-1, or possibly 2022.4+1.3.236.0-1:

> + pkg-config --cflags --libs glslang
> + g++ -std=c++11 -o trivial trivial.cpp -lglslang -lMachineIndependent 
> -lOSDependent -lHLSL -lOGLCompiler -lGenericCodeGen -lSPVRemapper -lpthread
> + test -x trivial
> + ./trivial
> + pkg-config --cflags --libs spirv
> + g++ -std=c++11 -o spirv spirv.cpp -lSPIRV -lSPIRV-Tools-opt -lSPIRV-Tools 
> -lSPIRV-Tools-link -lglslang -lMachineIndependent -lOSDependent -lHLSL 
> -lOGLCompiler -lGenericCodeGen -lSPVRemapper -lpthread
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libSPIRV.a(SpvTools.cpp.o):
>  in function `glslang::SpirvToolsTransform(glslang::TIntermediate const&, 
> std::vector >&, 
> spv::SpvBuildLogger*, glslang::SpvOptions const*)':
> (.text+0x689): undefined reference to 
> `spvtools::CreateAggressiveDCEPass(bool, bool)'
> /usr/bin/ld: (.text+0x6de): undefined reference to 
> `spvtools::CreateAggressiveDCEPass(bool, bool)'
> /usr/bin/ld: (.text+0x784): undefined reference to 
> `spvtools::CreateAggressiveDCEPass(bool, bool)'
> /usr/bin/ld: (.text+0x7ff): undefined reference to 
> `spvtools::CreateAggressiveDCEPass(bool, bool)'
> /usr/bin/ld: (.text+0x8ef): undefined reference to 
> `spvtools::CreateEliminateDeadInputComponentsSafePass()'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libSPIRV.a(SpvTools.cpp.o):
>  in function `glslang::SpirvToolsAnalyzeDeadOutputStores(spv_target_env, 
> std::vector >&, 
> std::unordered_set, 
> std::equal_to, std::allocator >*, 
> std::unordered_set, 
> std::equal_to, std::allocator >*, 
> spv::SpvBuildLogger*)':
> (.text+0x9b1): undefined reference to 
> `spvtools::CreateAnalyzeLiveInputPass(std::unordered_set std::hash, std::equal_to, std::allocator int> >*, std::unordered_set, 
> std::equal_to, std::allocator >*)'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libSPIRV.a(SpvTools.cpp.o):
>  in function `glslang::SpirvToolsEliminateDeadOutputStores(spv_target_env, 
> std::vector >&, 
> std::unordered_set, 
> std::equal_to, std::allocator >*, 
> std::unordered_set, 
> std::equal_to, std::allocator >*, 
> spv::SpvBuildLogger*)':
> (.text+0xae1): undefined reference to 
> `spvtools::CreateEliminateDeadOutputStoresPass(std::unordered_set int, std::hash, std::equal_to, 
> std::allocator >*, std::unordered_set std::hash, std::equal_to, std::allocator int> >*)'
> /usr/bin/ld: (.text+0xb03): undefined reference to 
> `spvtools::CreateAggressiveDCEPass(bool, bool)'
> /usr/bin/ld: (.text+0xb1e): undefined reference to 
> `spvtools::CreateEliminateDeadOutputComponentsPass()'
> /usr/bin/ld: (.text+0xb40): undefined reference to 
> `spvtools::CreateAggressiveDCEPass(bool, bool)'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libSPIRV.a(SpvTools.cpp.o):
>  in function `glslang::SpirvToolsEliminateDeadInputComponents(spv_target_env, 
> std::vector >&, 
> spv::SpvBuildLogger*)':
> (.text+0xc80): undefined reference to 
> `spvtools::CreateAggressiveDCEPass(bool, bool)'

I think probably this means that SPIRV-Tools.pc is missing some libraries,
similar to #951988 but for spirv-tools rather than glslang?

Adding an autopkgtest to spirv-tools and running it before upload might
be a helpful way to catch similar issues.

smcv

Processed: spirv-tools: autopkgtest regression for glslang: undefined reference to spvtools::CreateAggressiveDCEPass etc.

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:glslang
Bug #1031230 [spirv-tools] spirv-tools: autopkgtest regression for glslang: 
undefined reference to spvtools::CreateAggressiveDCEPass etc.
Added indication that 1031230 affects src:glslang

-- 
1031230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031230
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1030577: marked as done (simde: autopkgtest regressions on i386 and ppc64el)

[Debian Bug Tracking System]

Your message dated Mon, 13 Feb 2023 15:34:08 +
with message-id 
and subject line Bug#1030577: fixed in simde 0.7.4~rc2-1
has caused the Debian Bug report #1030577,
regarding simde: autopkgtest regressions on i386 and ppc64el
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.)


-- 
1030577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030577
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: simde
Version: 0.7.4~rc1-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/i386/s/simde/31050074/log.gz

...
Summary of Failures:

 107/1534 x86/avx512/dbsad/emul/c ERROR   0.01s   exit 
status 1
 108/1534 x86/avx512/dbsad/native/c   ERROR   0.01s   exit 
status 1
 109/1534 x86/avx512/dbsad/emul/cpp   ERROR   0.01s   exit 
status 1
 110/1534 x86/avx512/dbsad/native/cpp ERROR   0.01s   exit 
status 1

Ok: 1524
Expected Fail:  0   
Fail:   4   
Unexpected Pass:0   
Skipped:6   
Timeout:0   

Full log written to 
/tmp/autopkgtest-lxc.tgbnxsqh/downtmp/autopkgtest_tmp/build-gcc/meson-logs/testlog.txt
FAILED: meson-internal__test 
/usr/bin/meson test --no-rebuild --print-errorlogs
ninja: build stopped: subcommand failed.
autopkgtest [20:10:51]: test run-unit-test: ---]
autopkgtest [20:10:51]: test run-unit-test:  - - - - - - - - - - results - - - 
- - - - - - -
run-unit-testFAIL non-zero exit status 1



https://ci.debian.net/data/autopkgtest/testing/ppc64el/s/simde/31050076/log.gz

...
Summary of Failures:

 268/1534 x86/avx512/range/native/cpp ERROR   0.06s   exit 
status 1
 269/1534 x86/avx512/range/native/c   ERROR   0.11s   exit 
status 1
 271/1534 x86/avx512/range_round/native/c ERROR   0.04s   exit 
status 1
 274/1534 x86/avx512/range_round/native/cpp   ERROR   0.05s   exit 
status 1
 436/1534 x86/sse/native/cERROR   0.09s   exit 
status 1
 438/1534 x86/sse/native/cpp  ERROR   0.11s   exit 
status 1
 440/1534 x86/sse2/native/c   ERROR   0.12s   exit 
status 1
 442/1534 x86/sse2/native/cpp ERROR   0.10s   exit 
status 1
1364/1534 wasm_simd128/mul/native/c   ERROR   0.06s   exit 
status 1
1366/1534 wasm_simd128/mul/native/cpp ERROR   0.08s   exit 
status 1
1424/1534 wasm_simd128/shr/native/c   ERROR   0.05s   exit 
status 1
1426/1534 wasm_simd128/shr/native/cpp ERROR   0.07s   exit 
status 1

Ok: 622 
Expected Fail:  0   
Fail:   12  
Unexpected Pass:0   
Skipped:900 
Timeout:0   

Full log written to 
/tmp/autopkgtest-lxc.h12h1wf1/downtmp/autopkgtest_tmp/build-gcc/meson-logs/testlog.txt
FAILED: meson-internal__test 
/usr/bin/meson test --no-rebuild --print-errorlogs
ninja: build stopped: subcommand failed.
autopkgtest [19:58:03]: test run-unit-test: ---]
autopkgtest [19:58:03]: test run-unit-test:  - - - - - - - - - - results - - - 
- - - - - - -
run-unit-testFAIL non-zero exit status 1
--- End Message ---
--- Begin Message ---
Source: simde
Source-Version: 0.7.4~rc2-1
Done: Michael R. Crusoe 

We believe that the bug you reported is fixed in the latest version of
simde, 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 1030...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated simde 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: Sun, 12 Feb 2023 19:29:01 +0100
Source: simde
Architecture: source
Version: 0.7.4~rc2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Michael R. Crusoe 
Closes: 102124 1002223 1023687 1030577
Changes:
 simde (0.7.4~rc2-1) unstable; urgency=medium
 .
   * Build & test with default gcc version.  Closes: #1023687, #1002223
   * New upstream version. Closes: #1030577

Bug#1023687: marked as done (simde build depends on gcc-10 that should not be in bookworm)

[Debian Bug Tracking System]

Your message dated Mon, 13 Feb 2023 15:34:08 +
with message-id 
and subject line Bug#1023687: fixed in simde 0.7.4~rc2-1
has caused the Debian Bug report #1023687,
regarding simde build depends on gcc-10 that should not be in bookworm
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.)


-- 
1023687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023687
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: simde
Version: 0.7.2-6
Severity: serious
Control: block 1023666 by -1
Control: close -1 0.7.3~0git20210929204341.90523a2-1

This is already fixed in experimental.
--- End Message ---
--- Begin Message ---
Source: simde
Source-Version: 0.7.4~rc2-1
Done: Michael R. Crusoe 

We believe that the bug you reported is fixed in the latest version of
simde, 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 1023...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated simde 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: Sun, 12 Feb 2023 19:29:01 +0100
Source: simde
Architecture: source
Version: 0.7.4~rc2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Michael R. Crusoe 
Closes: 102124 1002223 1023687 1030577
Changes:
 simde (0.7.4~rc2-1) unstable; urgency=medium
 .
   * Build & test with default gcc version.  Closes: #1023687, #1002223
   * New upstream version. Closes: #1030577
   * Skip dbsad tests on i686, known failure. Closes: #102124
Checksums-Sha1:
 a71cb4aa17b5bc408d479dbfd45adac5416b1c4a 2050 simde_0.7.4~rc2-1.dsc
 32b121dd106e5be56d00e79bfa36f9712b3afc0e 4018612 simde_0.7.4~rc2.orig.tar.xz
 7ec41ce0bb2dee3f1d5a67eebb3223c6e5dc8dc6 22416 simde_0.7.4~rc2-1.debian.tar.xz
 b0c473a325f543eb9a283d398a9a624fd237bd53 7876 
simde_0.7.4~rc2-1_source.buildinfo
Checksums-Sha256:
 ced06b27c5a55cd898c5fb50d66a4c13b0dda2cb04934eeff964642bfe5c2f7a 2050 
simde_0.7.4~rc2-1.dsc
 2f6c9eceb360ba587c2456a985a8cefdc7c6a7a538431cd7d99a443b7074369e 4018612 
simde_0.7.4~rc2.orig.tar.xz
 7c84945a2579e5bd36152d35c3b2a1bc652dc699e29f4e19be45556bf6a4372a 22416 
simde_0.7.4~rc2-1.debian.tar.xz
 338cd3d0adef418c930193cec9aef125b1b7ab1db5ec618397c9f9411b2be283 7876 
simde_0.7.4~rc2-1_source.buildinfo
Files:
 b573b0dd9f9a203a43188bb3478ae3ee 2050 libdevel optional simde_0.7.4~rc2-1.dsc
 82e079147cb9f8887684d569094a9762 4018612 libdevel optional 
simde_0.7.4~rc2.orig.tar.xz
 54f53ea5f518a9152e8d6ea79465f899 22416 libdevel optional 
simde_0.7.4~rc2-1.debian.tar.xz
 87bdfd3d1b6d5a78792543557fbe45e4 7876 libdevel optional 
simde_0.7.4~rc2-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAmPqSu4ACgkQPCZ2P2xn
5uIDYg/9HMRm/G0betYk+SSEbxVyzcS8Aq6i61pF27FduRov3oCy7cZ5Ot36qCrQ
vmtKTTSNkJNWtE5Eicj9jOtMQ109nLVhQs68iq1gbTdv382nvqizW6YuCWYl4UrS
RwhEyc6g0rakZnza7KtSOxo7qQbiUxJkc3nkyvG5FrrgTP8oUMdCJJ0UGmMASg3h
0OR3mS5RyeLtyrbdrhGNwZ56dPHxbHz4E1eeIXd657rumGMwAnnY2uk2g6kwrDV1
J+v1hbd2PgnWIiIFlE5VyRTwHRDoPkQ/UdRbHjy/NNZv56fzxPzlCegR7TnrQeAx
COmPBHU1bZNN4GWBzlvJnr7s+gFzpLLf6TTCY/k8atxfzLgWVyp3uXE+egWM8sUQ
VEPtUEd1XStkMVcbLA0VjY4puj9CwuZak+Bb/tVNTFP12SZRruMkwuvC5f5iXiDj
Xz88kFBorVwM3l0TQ6D0dsL4RuWNQmASZervXLO9uJaLXUMwFADjeNCAZ77TdX9V
nD1/wb779LvzPPNr24t+OhdwkTZTHSE1nejUcTMEsjt5MDE4egEyPe7Jsw/FTBKH
VC0873L7nWHaeaKGLYcU7S8FTpZMU9mRVcTHP2xOeve4jOJjtESfOfU6XgCBqgXC
62xIAk6+Gvo5h5C6CbLSiiuer3sI4Z0PL5GEnZ+F1OFvgy9j3Hg=
=rArn
-END PGP SIGNATURE End Message ---

Bug#1031228: nvidia-driver: Broken depencies

[Michael Tatge]

Package: nvidia-driver
Version: 525.85.12
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I'm trying to install the package nvidia-driver on sid.
It fails with the following message:

The following packages have unmet dependencies:
 nvidia-driver : Depends: nvidia-kernel-dkms (= 525.85.12-1) but it is not 
installable or
  nvidia-kernel-525.85.12 or
  nvidia-open-kernel-525.85.12 but it is not 
installable or
  nvidia-open-kernel-525.85.12 but it is not installable
E: Unable to correct problems, you have held broken packages.


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (990, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-4-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=de_DE.utf8 (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 nvidia-driver depends on:
pn  nvidia-alternative   
pn  nvidia-driver-bin
pn  nvidia-driver-libs   
ii  nvidia-installer-cleanup 20220217+2
pn  nvidia-kernel-dkms | nvidia-kernel-525.85.12 | nvidia-open-kern  
el-525.85.12 | nvidia-open-kernel-525.85.12
pn  nvidia-legacy-check  
pn  nvidia-support   
pn  nvidia-vdpau-driver  
pn  xserver-xorg-video-nvidia

Versions of packages nvidia-driver recommends:
pn  libnvidia-cfg1   
pn  nvidia-persistenced  
pn  nvidia-settings  

Versions of packages nvidia-driver suggests:
pn  nvidia-kernel-dkms | nvidia-kernel-source | nvidia-open-kernel-sour  
ce | nvidia-open-kernel-source


TIA,
Michael

Processed: Re: Bug#1030434: rauc: FTBFS: tests failed writing: Error opening file ?/tmp/tmp.I4dlWcaK4g/notexisting/out.raucb?: No such file or directory

[Debian Bug Tracking System]

Processing control commands:

> reassign 1030434 src:opensc 0.23.0-0.1
Bug #1030434 [src:rauc] rauc: FTBFS: tests failed writing: Error opening file 
?/tmp/tmp.I4dlWcaK4g/notexisting/out.raucb?: No such file or directory
Bug reassigned from package 'src:rauc' to 'src:opensc'.
No longer marked as found in versions rauc/1.8-2.
Ignoring request to alter fixed versions of bug #1030434 to the same values 
previously set
Bug #1030434 [src:opensc] rauc: FTBFS: tests failed writing: Error opening file 
?/tmp/tmp.I4dlWcaK4g/notexisting/out.raucb?: No such file or directory
Marked as found in versions opensc/0.23.0-0.1.
> tag 1030434 + fixed-upstream
Bug #1030434 [src:opensc] rauc: FTBFS: tests failed writing: Error opening file 
?/tmp/tmp.I4dlWcaK4g/notexisting/out.raucb?: No such file or directory
Added tag(s) fixed-upstream.
> affects 1030434 + rauc
Bug #1030434 [src:opensc] rauc: FTBFS: tests failed writing: Error opening file 
?/tmp/tmp.I4dlWcaK4g/notexisting/out.raucb?: No such file or directory
Added indication that 1030434 affects rauc

-- 
1030434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030434
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1030434: rauc: FTBFS: tests failed writing: Error opening file ?/tmp/tmp.I4dlWcaK4g/notexisting/out.raucb?: No such file or directory

[Uwe Kleine-König]

Control: reassign 1030434 src:opensc 0.23.0-0.1
Control: tag 1030434 + fixed-upstream
Control: affects 1030434 + rauc

Hello,

On Sat, Feb 04, 2023 at 08:39:04AM +0100, Lucas Nussbaum wrote:
> Source: rauc
> Version: 1.8-2
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20230203 ftbfs-bookworm
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> The full build log is available from:
> http://qa-logs.debian.net/2023/02/03/rauc_1.8-2_unstable.log
> 
> All bugs filed during this archive rebuild are listed at:
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230203;users=lu...@debian.org
> or:
> https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230203=lu...@debian.org=1=1=1=1#results

This is a regression in opensc with openssl3 support. This is
fixed upstream by the following commits:

9294183e07ff pkcs11-tool: Fix private key import
cff91cf61677 pkcs11-tool: Log more information on OpenSSL errors

With these two fixes applied, rauc should build fine again as is.

Best regards
Uwe

-- 
Pengutronix e.K.   | Uwe Kleine-König|
Industrial Linux Solutions | https://www.pengutronix.de/ |


signature.asc
Description: PGP signature

Bug#1031179: marked as done (libzvbi-dev: libzvbi.h unusable - missing version.h include)

[Debian Bug Tracking System]

Your message dated Mon, 13 Feb 2023 14:43:16 +
with message-id 
and subject line Bug#1031179: fixed in zvbi 0.2.41-1
has caused the Debian Bug report #1031179,
regarding libzvbi-dev: libzvbi.h unusable - missing version.h include
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.)


-- 
1031179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031179
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libzvbi-dev
Version: 0.2.40-1
Severity: grave
Tags: upstream
Justification: renders package unusable

Trying to build GStreamer (gst-plugins-bad) against the latest version results 
in

In file included from 
../subprojects/gst-plugins-bad/ext/teletextdec/gstteletextdec.h:26,
 from 
../subprojects/gst-plugins-bad/ext/teletextdec/gstteletextdec.c:45:
/usr/include/libzvbi.h:28:10: fatal error: version.h: No such file or directory
   28 | #include "version.h"
  |  ^~~

This header is not shipped by the libzvbi-dev package.

On further investigation it appears to be an upstream bug actually, it also 
doesn't install the version.h file.

Which is probably for the best because installing a version.h file into the 
general /usr/include directory is probably a bit questionable.


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-4-amd64 (SMP w/16 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 libzvbi-dev depends on:
ii  libpng-dev  1.6.39-2
ii  libzvbi00.2.40-1

libzvbi-dev recommends no packages.

libzvbi-dev suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: zvbi
Source-Version: 0.2.41-1
Done: Ileana Dumitrescu 

We believe that the bug you reported is fixed in the latest version of
zvbi, 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 1031...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ileana Dumitrescu  (supplier of updated zvbi 
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: Mon, 13 Feb 2023 15:32:40 +0200
Source: zvbi
Architecture: source
Version: 0.2.41-1
Distribution: unstable
Urgency: medium
Maintainer: Ileana Dumitrescu 
Changed-By: Ileana Dumitrescu 
Closes: 1031179
Changes:
 zvbi (0.2.41-1) unstable; urgency=medium
 .
   * New upstream release.
   * Fixes include issue (Closes: #1031179).
Checksums-Sha1:
 b740c10660e7cf8733e521a4f06c04b9c08c6749 2129 zvbi_0.2.41-1.dsc
 1b344c1ca6de1bf8e60cc47dad6bb5f9cd4d8833 1295453 zvbi_0.2.41.orig.tar.gz
 12de2f23db80fafa091f16ac6e7e460a4a3d86a8 17440 zvbi_0.2.41-1.debian.tar.xz
 926dfbb8ca20ae5f26b69c49a46f20df787506c1 7821 zvbi_0.2.41-1_amd64.buildinfo
Checksums-Sha256:
 6e239f8a0e00408a6a6f1dcaacb2f92596f37ac9389fb5b78e5fc03e37dfcdab 2129 
zvbi_0.2.41-1.dsc
 2f22f9846bceead26349dd0b026cd41b638171eca2af98e69fe6762b98cbcd87 1295453 
zvbi_0.2.41.orig.tar.gz
 4a8767a1fb6fcfdcf9da21945a33de9c9cfac3ebfa4222929a043fabc1110492 17440 
zvbi_0.2.41-1.debian.tar.xz
 dab0ef69422f9685ef0565da23ca826af29832e99120aea8779f63a31ff63a18 7821 
zvbi_0.2.41-1_amd64.buildinfo
Files:
 dc4224dd3e74e3df6a22ed1992bdb039 2129 devel optional zvbi_0.2.41-1.dsc
 e92a835ec821658bfb74473742119f7a 1295453 devel optional zvbi_0.2.41.orig.tar.gz
 b8ac935e2a134daa2ab854b836833e08 17440 devel optional 
zvbi_0.2.41-1.debian.tar.xz
 ac676e8e085a359c36b915bf5f71e5f3 7821 devel optional 
zvbi_0.2.41-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE+ibKeEvhiJJ/IrmfZXDqARRvc1QFAmPqQRYACgkQZXDqARRv
c1RAaw/9HSkfsvlcYxdIHLti67Fw6h2WFivs8YxPjd9pCsbTbChOL3gzukS0ruY4
VF3t6BLS4XtCZYO6VogDQxdXMZ9a6bBwRkdbZeqcBE366hrFGW3Ivw4pXSmhA1Hq
ecGnTo+DsuabDJ7NaRT3Fd9taN2OWQ0MEccgLZDzd3nFYlGjB9AC3J2aRI8y4ZOA
2OJLjQFmVyBa75DN05Zn86Jitqgl1pDGTtSDLcNFIbJKRvE6ID7n+gWOMJfAcWDv
bxJGSnqdyiyYvj/1+t5kXuWRb0SYJIuntsDgYcd/KiDErDADWkGZM58F6AdPcRBQ

Bug#1025279: marked as done (nvidia-graphics-drivers: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CV

[Debian Bug Tracking System]

Your message dated Mon, 13 Feb 2023 14:40:36 +
with message-id 
and subject line Bug#1025279: fixed in nvidia-open-gpu-kernel-modules 
525.85.12-1
has caused the Debian Bug report #1025279,
regarding nvidia-graphics-drivers: CVE-2022-34670, CVE-2022-34674, 
CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, 
CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, 
CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, 
CVE-2022-42263, CVE-2022-42264
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.)


-- 
1025279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025279
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Severity: serious
Tags: security upstream
Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34680, CVE-2022-42257, 
CVE-2022-42258, CVE-2022-42259
Control: tag -2 + wontfix
Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4
Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34680, CVE-2022-42257, 
CVE-2022-42258, CVE-2022-42259
Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1
Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, 
CVE-2022-34682, CVE-2022-42254, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, 
CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, 
CVE-2022-42264
Control: tag -4 + wontfix
Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1
Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, 
CVE-2022-34682, CVE-2022-42254, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, 
CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, 
CVE-2022-42264
Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1
Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, 
CVE-2022-34682, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, 
CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, 
CVE-2022-42263, CVE-2022-42264
Control: tag -6 + wontfix
Control: close -6 460.106.00-3
Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1
Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, 
CVE-2022-34682, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, 
CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, 
CVE-2022-42263, CVE-2022-42264
Control: reassign -8 src:nvidia-graphics-drivers-tesla-510 510.47.03-1
Control: retitle -8 nvidia-graphics-drivers-tesla-510: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, 
CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, 
CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, 
CVE-2022-42262, CVE-2022-42263, CVE-2022-42264
Control: reassign -9 src:nvidia-graphics-drivers-tesla 510.85.02-1
Control: retitle -9 nvidia-graphics-drivers-tesla: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, 
CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, 
CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, 
CVE-2022-42262, CVE-2022-42263, CVE-2022-42264
Control: found -1 340.24-1
Control: found -1 343.22-1
Control: found -1 396.18-1
Control: found -1 430.14-1
Control: found -1 455.23.04-1
Control: found -1 465.24.02-1
Control: found -1 495.44-1
Control: found -1 515.48.07-1

https://nvidia.custhelp.com/app/answers/detail/a_id/5415

CVE-2022-34670  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer handler, where an unprivileged
regular user can cause truncation errors when casting a primitive to a
primitive of smaller size causes data to be lost in the conversion,
which may lead to denial of service or information disclosure.

CVE-2022-42263  

Bug#1031197: marked as done (firmware-ath9k-htc: Conflict with firmware-atheros < 20230210-1)

[Debian Bug Tracking System]

Your message dated Mon, 13 Feb 2023 13:54:00 +
with message-id 
and subject line Bug#1031197: fixed in open-ath9k-htc-firmware 
1.4.0-108-gd856466+dfsg1-1.2
has caused the Debian Bug report #1031197,
regarding firmware-ath9k-htc: Conflict with firmware-atheros < 20230210-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.)


-- 
1031197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firmware-ath9k-htc
Version: 1.4.0-108-gd856466+dfsg1-1
Severity: normal
X-Debbugs-Cc: billchenchina2...@gmail.com

Hi,

My firmware-ath9k-htc fails to unpack when firmware-atheros is 20221214-3:

Preparing to unpack .../02-firmware-linux_20230210-1_all.deb ...
Unpacking firmware-linux (20230210-1) over (20221214-3) ...
Preparing to unpack .../03-firmware-amd-graphics_20230210-1_all.deb ...
Unpacking firmware-amd-graphics (20230210-1) over (20221214-3) ...
Preparing to unpack .../04-firmware-linux-nonfree_20230210-1_all.deb
...
Unpacking firmware-linux-nonfree (20230210-1) over (20221214-3) ...
Preparing to unpack .../05-firmware-misc-nonfree_20230210-1_all.deb ...
Unpacking firmware-misc-nonfree (20230210-1) over (20221214-3) ...
Preparing to unpack .../06-firmware-
ath9k-htc_1.4.0-108-gd856466+dfsg1-1.1_all.deb ...
Unpacking firmware-ath9k-htc (1.4.0-108-gd856466+dfsg1-1.1) over
(1.4.0-108-gd856466+dfsg1-1) ...
dpkg: error processing archive /tmp/apt-dpkg-install-
mZXa67/06-firmware-ath9k-htc_1.4.0-108-gd856466+dfsg1-1.1_all.deb (--unpack):
 trying to overwrite '/lib/firmware/ath9k_htc/htc_7010-1.4.0.fw', which
is also in package firmware-atheros 20221214-3
Preparing to unpack .../07-firmware-atheros_20230210-1_all.deb ...
Unpacking firmware-atheros (20230210-1) over (20221214-3) ...

Best regards,
Tianyu Chen


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-4-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages firmware-ath9k-htc is related to:
ii  network-manager  1.42.0-1
ii  wpasupplicant2:2.10-11

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: open-ath9k-htc-firmware
Source-Version: 1.4.0-108-gd856466+dfsg1-1.2
Done: Bastian Germann 

We believe that the bug you reported is fixed in the latest version of
open-ath9k-htc-firmware, 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 1031...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated open-ath9k-htc-firmware 
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: Mon, 13 Feb 2023 14:27:16 +0100
Source: open-ath9k-htc-firmware
Architecture: source
Version: 1.4.0-108-gd856466+dfsg1-1.2
Distribution: unstable
Urgency: high
Maintainer: John Scott 
Changed-By: Bastian Germann 
Closes: 1031197
Changes:
 open-ath9k-htc-firmware (1.4.0-108-gd856466+dfsg1-1.2) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Breaks/Replaces on firmware-atheros. (Closes: #1031197)
   * metadata: Remove Homepage field.
Checksums-Sha1:
 15a2a45c3d001d042948c06617dad14d82a8c29a 2067 
open-ath9k-htc-firmware_1.4.0-108-gd856466+dfsg1-1.2.dsc
 684eeda4e875b73e390ec648f76159df9be63e0e 14752 
open-ath9k-htc-firmware_1.4.0-108-gd856466+dfsg1-1.2.debian.tar.xz
 fb429a3fa54b1510fd5d9ee28b28b3f97b654bdd 6678 
open-ath9k-htc-firmware_1.4.0-108-gd856466+dfsg1-1.2_source.buildinfo
Checksums-Sha256:
 d3d94c418e7a04e90f857ef04ea87b43bdea122db6ae8af7e0916f81afd912b8 2067 
open-ath9k-htc-firmware_1.4.0-108-gd856466+dfsg1-1.2.dsc
 08b11f4e32313e18e7d9db68f9ebbe57f8a717edf35799f0b582783ebe2a 14752 
open-ath9k-htc-firmware_1.4.0-108-gd856466+dfsg1-1.2.debian.tar.xz
 eb4d3b798da485a42a5e6c3bcd3ed0db1828346ac0f65dda758a0eb094192344 6678 

Bug#1031224: marked as done (vdr-dev: helper dh_vdrplugin_depends makes vdr-plugin-mp3 to FTBFS)

[Debian Bug Tracking System]

Your message dated Mon, 13 Feb 2023 14:47:48 +0100
with message-id <66821713-c993-cf39-1536-904dddf43...@debian.org>
and subject line closing duplicate
has caused the Debian Bug report #1031224,
regarding vdr-dev: helper dh_vdrplugin_depends makes vdr-plugin-mp3 to FTBFS
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.)


-- 
1031224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031224
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: vdr-dev
Version: 2.6.0-1
Severity: serious
Control: affects -1 src:vdr-plugin-mp3
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in bookworm, the vdr-plugin-mp3 package failed 
to build:


[...]
 debian/rules build-arch
dh build-arch --with vdrplugin
   dh_update_autotools_config -a
   dh_autoreconf -a
   dh_auto_configure -a
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build -- all VDRDIR=/usr/include/vdr LIBDIR=. LOCALEDIR=locale
make -j1 "INSTALL=install --strip-program=true" all 
VDRDIR=/usr/include/vdr LIBDIR=. LOCALEDIR=locale
make[2]: Entering directory '/<>'
g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -g -O2 -ffile-prefix-map=/build/vdr-5Csy3v/vdr-2.6.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-Wl,-z,relro -c -D_GNU_SOURCE -DAPIVERSNUM=20600 -DHAVE_SNDFILE -DHAVE_VORBISFILE 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -I/usr/include/vdr/include 
mp3.c
g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -g -O2 -ffile-prefix-map=/build/vdr-5Csy3v/vdr-2.6.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-Wl,-z,relro -c -D_GNU_SOURCE -DAPIVERSNUM=20600 -DHAVE_SNDFILE -DHAVE_VORBISFILE 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -I/usr/include/vdr/include 
data.c
g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -g -O2 -ffile-prefix-map=/build/vdr-5Csy3v/vdr-2.6.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-Wl,-z,relro -c -D_GNU_SOURCE -DAPIVERSNUM=20600 -DHAVE_SNDFILE -DHAVE_VORBISFILE 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -I/usr/include/vdr/include 
menu.c
g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -g -O2 -ffile-prefix-map=/build/vdr-5Csy3v/vdr-2.6.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-Wl,-z,relro -c -D_GNU_SOURCE -DAPIVERSNUM=20600 -DHAVE_SNDFILE -DHAVE_VORBISFILE 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -I/usr/include/vdr/include 
version.c
g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -g -O2 -ffile-prefix-map=/build/vdr-5Csy3v/vdr-2.6.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-Wl,-z,relro -c -D_GNU_SOURCE -DAPIVERSNUM=20600 -DHAVE_SNDFILE -DHAVE_VORBISFILE 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -I/usr/include/vdr/include 
data-mp3.c
g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -g -O2 -ffile-prefix-map=/build/vdr-5Csy3v/vdr-2.6.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-Wl,-z,relro -c -D_GNU_SOURCE -DAPIVERSNUM=20600 -DHAVE_SNDFILE -DHAVE_VORBISFILE 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -I/usr/include/vdr/include 
setup-mp3.c
g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -g -O2 -ffile-prefix-map=/build/vdr-5Csy3v/vdr-2.6.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-Wl,-z,relro 

Processed: affects

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 1026310 + src:vdr-plugin-mp3
Bug #1026310 [vdr-dev] vdr-dev: dh_vdrplugin_depends fail with "error: Bug in 
helper:"
Bug #1026475 [vdr-dev] vdr-plugin-remote: FTBFS: make: *** [debian/rules:7: 
binary] Error 25
Bug #1026533 [vdr-dev] vdr-plugin-femon: FTBFS: make: *** [debian/rules:7: 
binary] Error 25
Bug #1027498 [vdr-dev] vdr-plugin-streamdev: FTBFS: make: *** [debian/rules:9: 
binary] Error 25
Bug #1027499 [vdr-dev] vdr-plugin-svdrposd: FTBFS: make: *** [debian/rules:7: 
binary] Error 25
Bug #1027532 [vdr-dev] vdr-plugin-dvd: FTBFS: make: *** [debian/rules:7: 
binary] Error 25
Bug #1027543 [vdr-dev] vdr-plugin-osdserver: FTBFS: make: *** [debian/rules:10: 
binary] Error 25
Bug #1027568 [vdr-dev] vdr-plugin-fritzbox: FTBFS: make: *** [debian/rules:9: 
binary] Error 25
Bug #1027575 [vdr-dev] vdr-plugin-epgsearch: FTBFS: make: *** [debian/rules:7: 
binary] Error 25
Bug #1027609 [vdr-dev] vdr-plugin-xineliboutput: FTBFS: make: *** 
[debian/rules:13: binary] Error 25
Bug #1027627 [vdr-dev] vdr-plugin-osdteletext: FTBFS: make: *** 
[debian/rules:7: binary] Error 25
Bug #1027630 [vdr-dev] vdr-plugin-satip: FTBFS: make: *** [debian/rules:11: 
binary] Error 25
Bug #1027631 [vdr-dev] vdr-plugin-epgsync: FTBFS: make: *** [debian/rules:7: 
binary] Error 25
Bug #1027645 [vdr-dev] vdr-plugin-dvbsddevice: FTBFS: make: *** 
[debian/rules:7: binary] Error 25
Bug #1027646 [vdr-dev] vdr-plugin-vnsiserver: FTBFS: make: *** 
[debian/rules:16: binary] Error 25
Bug #1027659 [vdr-dev] vdr-plugin-dvbhddevice: FTBFS: make: *** 
[debian/rules:7: binary] Error 25
Bug #1027660 [vdr-dev] vdr-plugin-svdrpservice: FTBFS: make: *** 
[debian/rules:9: binary] Error 25
Bug #1027663 [vdr-dev] vdr-plugin-skinenigmang: FTBFS: make: *** 
[debian/rules:11: binary] Error 25
Added indication that 1026310 affects src:vdr-plugin-mp3
Added indication that 1026475 affects src:vdr-plugin-mp3
Added indication that 1026533 affects src:vdr-plugin-mp3
Added indication that 1027498 affects src:vdr-plugin-mp3
Added indication that 1027499 affects src:vdr-plugin-mp3
Added indication that 1027532 affects src:vdr-plugin-mp3
Added indication that 1027543 affects src:vdr-plugin-mp3
Added indication that 1027568 affects src:vdr-plugin-mp3
Added indication that 1027575 affects src:vdr-plugin-mp3
Added indication that 1027609 affects src:vdr-plugin-mp3
Added indication that 1027627 affects src:vdr-plugin-mp3
Added indication that 1027630 affects src:vdr-plugin-mp3
Added indication that 1027631 affects src:vdr-plugin-mp3
Added indication that 1027645 affects src:vdr-plugin-mp3
Added indication that 1027646 affects src:vdr-plugin-mp3
Added indication that 1027659 affects src:vdr-plugin-mp3
Added indication that 1027660 affects src:vdr-plugin-mp3
Added indication that 1027663 affects src:vdr-plugin-mp3
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1026310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026310
1026475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026475
1026533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026533
1027498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027498
1027499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027499
1027532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027532
1027543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027543
1027568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027568
1027575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027575
1027609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027609
1027627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027627
1027630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027630
1027631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027631
1027645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027645
1027646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027646
1027659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027659
1027660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027660
1027663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027663
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1026639: rhino FTBFS

[Markus Koschany]

I believe I have corrected all regressions except of one in closure-compiler
which I will fix later today (renamed class). It turned out that I had to
update the Manifest file and include another META-INF file,
javax.script.ScriptEngineFactory, to solve some FTBFS in reverse-dependencies.
This is the downside of just using javahelper. You have to be extra careful to
include everything that ant or gradle will do "automagically" for you. I'm
going to upload rhino 1.7.14 now.


signature.asc
Description: This is a digitally signed message part

Bug#1030413: marked as done (trac: FTBFS: ImportError: cannot import name 'soft_unicode' from 'jinja2.utils' (/usr/lib/python3/dist-packages/jinja2/utils.py))

[Debian Bug Tracking System]

Your message dated Mon, 13 Feb 2023 13:35:12 +
with message-id 
and subject line Bug#1030413: fixed in trac 1.5.4-1
has caused the Debian Bug report #1030413,
regarding trac: FTBFS: ImportError: cannot import name 'soft_unicode' from 
'jinja2.utils' (/usr/lib/python3/dist-packages/jinja2/utils.py)
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.)


-- 
1030413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030413
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: trac
Version: 1.5.3+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230203 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> running build
> running compile_catalog_tracini
> compiling catalog trac/locale/sv/LC_MESSAGES/tracini.po to 
> trac/locale/sv/LC_MESSAGES/tracini.mo
> compiling catalog trac/locale/he/LC_MESSAGES/tracini.po to 
> trac/locale/he/LC_MESSAGES/tracini.mo
> compiling catalog trac/locale/zh_TW/LC_MESSAGES/tracini.po to 
> trac/locale/zh_TW/LC_MESSAGES/tracini.mo
> compiling catalog trac/locale/cs/LC_MESSAGES/tracini.po to 
> trac/locale/cs/LC_MESSAGES/tracini.mo
> compiling catalog trac/locale/tr/LC_MESSAGES/tracini.po to 
> trac/locale/tr/LC_MESSAGES/tracini.mo
> compiling catalog trac/locale/ca/LC_MESSAGES/tracini.po to 
> trac/locale/ca/LC_MESSAGES/tracini.mo
> compiling catalog trac/locale/it/LC_MESSAGES/tracini.po to 
> trac/locale/it/LC_MESSAGES/tracini.mo
> compiling catalog trac/locale/nl/LC_MESSAGES/tracini.po to 
> trac/locale/nl/LC_MESSAGES/tracini.mo
> compiling catalog trac/locale/fi/LC_MESSAGES/tracini.po to 
> trac/locale/fi/LC_MESSAGES/tracini.mo
> compiling catalog trac/locale/eo/LC_MESSAGES/tracini.po to 
> trac/locale/eo/LC_MESSAGES/tracini.mo
> compiling catalog trac/locale/ru/LC_MESSAGES/tracini.po to 
> trac/locale/ru/LC_MESSAGES/tracini.mo
> compiling catalog trac/locale/pt_BR/LC_MESSAGES/tracini.po to 
> trac/locale/pt_BR/LC_MESSAGES/tracini.mo
> compiling catalog trac/locale/pl/LC_MESSAGES/tracini.po to 
> trac/locale/pl/LC_MESSAGES/tracini.mo
> compiling catalog trac/locale/en_GB/LC_MESSAGES/tracini.po to 
> trac/locale/en_GB/LC_MESSAGES/tracini.mo
> compiling catalog trac/locale/fa/LC_MESSAGES/tracini.po to 
> trac/locale/fa/LC_MESSAGES/tracini.mo
> compiling catalog trac/locale/hu/LC_MESSAGES/tracini.po to 
> trac/locale/hu/LC_MESSAGES/tracini.mo
> compiling catalog trac/locale/ro/LC_MESSAGES/tracini.po to 
> trac/locale/ro/LC_MESSAGES/tracini.mo
> compiling catalog trac/locale/es/LC_MESSAGES/tracini.po to 
> trac/locale/es/LC_MESSAGES/tracini.mo
> compiling catalog trac/locale/en_US/LC_MESSAGES/tracini.po to 
> trac/locale/en_US/LC_MESSAGES/tracini.mo
> compiling catalog trac/locale/nb/LC_MESSAGES/tracini.po to 
> trac/locale/nb/LC_MESSAGES/tracini.mo
> compiling catalog trac/locale/el/LC_MESSAGES/tracini.po to 
> trac/locale/el/LC_MESSAGES/tracini.mo
> compiling catalog trac/locale/fr/LC_MESSAGES/tracini.po to 
> trac/locale/fr/LC_MESSAGES/tracini.mo
> compiling catalog trac/locale/gl/LC_MESSAGES/tracini.po to 
> trac/locale/gl/LC_MESSAGES/tracini.mo
> compiling catalog trac/locale/ko/LC_MESSAGES/tracini.po to 
> trac/locale/ko/LC_MESSAGES/tracini.mo
> compiling catalog trac/locale/zh_CN/LC_MESSAGES/tracini.po to 
> trac/locale/zh_CN/LC_MESSAGES/tracini.mo
> compiling catalog trac/locale/es_AR/LC_MESSAGES/tracini.po to 
> trac/locale/es_AR/LC_MESSAGES/tracini.mo
> compiling catalog trac/locale/ja/LC_MESSAGES/tracini.po to 
> trac/locale/ja/LC_MESSAGES/tracini.mo
> compiling catalog trac/locale/vi/LC_MESSAGES/tracini.po to 
> trac/locale/vi/LC_MESSAGES/tracini.mo
> compiling catalog trac/locale/de/LC_MESSAGES/tracini.po to 
> trac/locale/de/LC_MESSAGES/tracini.mo
> compiling catalog trac/locale/hy/LC_MESSAGES/tracini.po to 
> trac/locale/hy/LC_MESSAGES/tracini.mo
> compiling catalog trac/locale/pt/LC_MESSAGES/tracini.po to 
> trac/locale/pt/LC_MESSAGES/tracini.mo
> compiling catalog trac/locale/sl/LC_MESSAGES/tracini.po to 
> trac/locale/sl/LC_MESSAGES/tracini.mo
> running compile_catalog_js
> compiling catalog trac/locale/sv/LC_MESSAGES/messages-js.po 

Processed: affects

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 1031224 src:vdr-plugin-mp3
Bug #1031224 [vdr-dev] vdr-dev: helper dh_vdrplugin_depends makes 
vdr-plugin-mp3 to FTBFS
Ignoring request to set affects of bug 1031224 to the same value previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1031224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031224
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1031197: firmware-ath9k-htc: Conflict with firmware-atheros < 20230210-1

[Bastian Germann]

As I have messed this up, I am NMUing again. debdiff attached.diff -Nru open-ath9k-htc-firmware-1.4.0-108-gd856466+dfsg1/debian/changelog 
open-ath9k-htc-firmware-1.4.0-108-gd856466+dfsg1/debian/changelog
--- open-ath9k-htc-firmware-1.4.0-108-gd856466+dfsg1/debian/changelog   
2023-02-12 22:34:38.0 +0100
+++ open-ath9k-htc-firmware-1.4.0-108-gd856466+dfsg1/debian/changelog   
2023-02-13 14:27:16.0 +0100
@@ -1,3 +1,11 @@
+open-ath9k-htc-firmware (1.4.0-108-gd856466+dfsg1-1.2) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Breaks/Replaces on firmware-atheros. (Closes: #1031197)
+  * metadata: Remove Homepage field.
+
+ -- Bastian Germann   Mon, 13 Feb 2023 14:27:16 +0100
+
 open-ath9k-htc-firmware (1.4.0-108-gd856466+dfsg1-1.1) unstable; urgency=high
 
   * Non-maintainer upload.
diff -Nru open-ath9k-htc-firmware-1.4.0-108-gd856466+dfsg1/debian/control 
open-ath9k-htc-firmware-1.4.0-108-gd856466+dfsg1/debian/control
--- open-ath9k-htc-firmware-1.4.0-108-gd856466+dfsg1/debian/control 
2023-02-12 22:32:48.0 +0100
+++ open-ath9k-htc-firmware-1.4.0-108-gd856466+dfsg1/debian/control 
2023-02-13 14:24:18.0 +0100
@@ -22,8 +22,8 @@
 Multi-Arch: foreign
 Depends:
  ${misc:Depends}
-Breaks: atheros-firmware (<= 20230210-1)
-Replaces: atheros-firmware (<= 20230210-1)
+Breaks: firmware-atheros (<= 20230210-1)
+Replaces: firmware-atheros (<= 20230210-1)
 Description: firmware for AR7010 and AR9271 USB wireless adapters
  The Qualcomm Atheros AR7010 and AR9271 chipsets are used in USB
  wireless adapters which are 802.11n-capable. This package contains
diff -Nru 
open-ath9k-htc-firmware-1.4.0-108-gd856466+dfsg1/debian/upstream/metadata 
open-ath9k-htc-firmware-1.4.0-108-gd856466+dfsg1/debian/upstream/metadata
--- open-ath9k-htc-firmware-1.4.0-108-gd856466+dfsg1/debian/upstream/metadata   
2023-02-12 22:34:38.0 +0100
+++ open-ath9k-htc-firmware-1.4.0-108-gd856466+dfsg1/debian/upstream/metadata   
2023-02-13 14:26:28.0 +0100
@@ -1,6 +1,5 @@
 Name: open-ath9k-htc-firmware
 Bug-Submit: https://github.com/qca/open-ath9k-htc-firmware/issues/new
-Homepage: https://github.com/qca/open-ath9k-htc-firmware
 Bug-Database: https://github.com/qca/open-ath9k-htc-firmware/issues
 Repository: https://github.com/qca/open-ath9k-htc-firmware.git
 Repository-Browse: https://github.com/qca/open-ath9k-htc-firmware

Bug#1031224: vdr-dev: helper dh_vdrplugin_depends makes vdr-plugin-mp3 to FTBFS

[Santiago Vila]

Package: vdr-dev
Version: 2.6.0-1
Severity: serious
Control: affects -1 src:vdr-plugin-mp3
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in bookworm, the vdr-plugin-mp3 package failed 
to build:


[...]
 debian/rules build-arch
dh build-arch --with vdrplugin
   dh_update_autotools_config -a
   dh_autoreconf -a
   dh_auto_configure -a
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build -- all VDRDIR=/usr/include/vdr LIBDIR=. LOCALEDIR=locale
make -j1 "INSTALL=install --strip-program=true" all 
VDRDIR=/usr/include/vdr LIBDIR=. LOCALEDIR=locale
make[2]: Entering directory '/<>'
g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -g -O2 -ffile-prefix-map=/build/vdr-5Csy3v/vdr-2.6.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-Wl,-z,relro -c -D_GNU_SOURCE -DAPIVERSNUM=20600 -DHAVE_SNDFILE -DHAVE_VORBISFILE 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -I/usr/include/vdr/include 
mp3.c
g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -g -O2 -ffile-prefix-map=/build/vdr-5Csy3v/vdr-2.6.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-Wl,-z,relro -c -D_GNU_SOURCE -DAPIVERSNUM=20600 -DHAVE_SNDFILE -DHAVE_VORBISFILE 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -I/usr/include/vdr/include 
data.c
g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -g -O2 -ffile-prefix-map=/build/vdr-5Csy3v/vdr-2.6.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-Wl,-z,relro -c -D_GNU_SOURCE -DAPIVERSNUM=20600 -DHAVE_SNDFILE -DHAVE_VORBISFILE 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -I/usr/include/vdr/include 
menu.c
g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -g -O2 -ffile-prefix-map=/build/vdr-5Csy3v/vdr-2.6.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-Wl,-z,relro -c -D_GNU_SOURCE -DAPIVERSNUM=20600 -DHAVE_SNDFILE -DHAVE_VORBISFILE 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -I/usr/include/vdr/include 
version.c
g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -g -O2 -ffile-prefix-map=/build/vdr-5Csy3v/vdr-2.6.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-Wl,-z,relro -c -D_GNU_SOURCE -DAPIVERSNUM=20600 -DHAVE_SNDFILE -DHAVE_VORBISFILE 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -I/usr/include/vdr/include 
data-mp3.c
g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -g -O2 -ffile-prefix-map=/build/vdr-5Csy3v/vdr-2.6.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-Wl,-z,relro -c -D_GNU_SOURCE -DAPIVERSNUM=20600 -DHAVE_SNDFILE -DHAVE_VORBISFILE 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -I/usr/include/vdr/include 
setup-mp3.c
g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -g -O2 -ffile-prefix-map=/build/vdr-5Csy3v/vdr-2.6.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-Wl,-z,relro -c -D_GNU_SOURCE -DAPIVERSNUM=20600 -DHAVE_SNDFILE -DHAVE_VORBISFILE 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -I/usr/include/vdr/include 
player-mp3.c
player-mp3.c: In member function ‘void cPlayManager::Throttle(bool)’:
player-mp3.c:912:17: warning: format ‘%llu’ expects argument of type ‘long long 
unsigned int’, but argument 2 has type ‘uint64_t’ {aka ‘long unsigned int’} 
[-Wformat=]
  912 |   db(printf("mgr: bgr-scan -> run (%llu)\n",cTimeMs::Now()))
  | ^~~ ~~
  | |
  | uint64_t 
{aka long unsigned int}
player-mp3.c:59:18: note: in definition of macro ‘db’
   59 | #define db(x) { (x); }
  |  ^

Processed: vdr-dev: helper dh_vdrplugin_depends makes vdr-plugin-mp3 to FTBFS

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:vdr-plugin-mp3
Bug #1031224 [vdr-dev] vdr-dev: helper dh_vdrplugin_depends makes 
vdr-plugin-mp3 to FTBFS
Added indication that 1031224 affects src:vdr-plugin-mp3

-- 
1031224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031224
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1031197: firmware-ath9k-htc: Conflict with firmware-atheros < 20230210-1

[Cyril Brulebois]

Control: notfound -1 1.4.0-108-gd856466+dfsg1-1
Control: found -1 1.4.0-108-gd856466+dfsg1-1.1

Cyril Brulebois  (2023-02-13):
> Tianyu Chen  (2023-02-13):
> > Package: firmware-ath9k-htc
> > Version: 1.4.0-108-gd856466+dfsg1-1
> > Severity: normal
> > X-Debbugs-Cc: billchenchina2...@gmail.com
> 
> Thanks for reporting, I was about to do that for you after seeing your
> report on IRC. :)

I missed the version skew in the original bug report, fixing.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Processed: Re: Bug#1031197: firmware-ath9k-htc: Conflict with firmware-atheros < 20230210-1

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 1.4.0-108-gd856466+dfsg1-1
Bug #1031197 [firmware-ath9k-htc] firmware-ath9k-htc: Conflict with 
firmware-atheros < 20230210-1
No longer marked as found in versions 
open-ath9k-htc-firmware/1.4.0-108-gd856466+dfsg1-1.
> found -1 1.4.0-108-gd856466+dfsg1-1.1
Bug #1031197 [firmware-ath9k-htc] firmware-ath9k-htc: Conflict with 
firmware-atheros < 20230210-1
Marked as found in versions 
open-ath9k-htc-firmware/1.4.0-108-gd856466+dfsg1-1.1.

-- 
1031197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1031223: python-streamz: FTBFS (failing tests)

[Santiago Vila]

Package: src:python-streamz
Version: 0.6.3-3
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --with python3 --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:240: python3.11 setup.py config
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:240: /usr/bin/python3 setup.py build
running build
running build_py
creating /<>/.pybuild/cpython3_3.11_streamz/build/streamz
copying streamz/utils_test.py -> 
/<>/.pybuild/cpython3_3.11_streamz/build/streamz
copying streamz/orderedweakset.py -> 
/<>/.pybuild/cpython3_3.11_streamz/build/streamz
copying streamz/collection.py -> 
/<>/.pybuild/cpython3_3.11_streamz/build/streamz
copying streamz/core.py -> 
/<>/.pybuild/cpython3_3.11_streamz/build/streamz
copying streamz/batch.py -> 
/<>/.pybuild/cpython3_3.11_streamz/build/streamz
copying streamz/sinks.py -> 
/<>/.pybuild/cpython3_3.11_streamz/build/streamz
copying streamz/utils.py -> 
/<>/.pybuild/cpython3_3.11_streamz/build/streamz
copying streamz/__init__.py -> 
/<>/.pybuild/cpython3_3.11_streamz/build/streamz
copying streamz/graph.py -> 
/<>/.pybuild/cpython3_3.11_streamz/build/streamz
copying streamz/plugins.py -> 
/<>/.pybuild/cpython3_3.11_streamz/build/streamz
copying streamz/sources.py -> 
/<>/.pybuild/cpython3_3.11_streamz/build/streamz
copying streamz/dask.py -> 
/<>/.pybuild/cpython3_3.11_streamz/build/streamz
creating /<>/.pybuild/cpython3_3.11_streamz/build/streamz/dataframe
copying streamz/dataframe/core.py -> 
/<>/.pybuild/cpython3_3.11_streamz/build/streamz/dataframe
copying streamz/dataframe/utils.py -> 
/<>/.pybuild/cpython3_3.11_streamz/build/streamz/dataframe
copying streamz/dataframe/__init__.py -> 
/<>/.pybuild/cpython3_3.11_streamz/build/streamz/dataframe
copying streamz/dataframe/aggregations.py -> 
/<>/.pybuild/cpython3_3.11_streamz/build/streamz/dataframe
creating /<>/.pybuild/cpython3_3.11_streamz/build/streamz/tests
copying streamz/tests/test_batch.py -> 
/<>/.pybuild/cpython3_3.11_streamz/build/streamz/tests
copying streamz/tests/test_core.py -> 
/<>/.pybuild/cpython3_3.11_streamz/build/streamz/tests
copying streamz/tests/py3_test_core.py -> 
/<>/.pybuild/cpython3_3.11_streamz/build/streamz/tests
copying streamz/tests/test_graph.py -> 
/<>/.pybuild/cpython3_3.11_streamz/build/streamz/tests
copying streamz/tests/test_kafka.py -> 
/<>/.pybuild/cpython3_3.11_streamz/build/streamz/tests
copying streamz/tests/__init__.py -> 
/<>/.pybuild/cpython3_3.11_streamz/build/streamz/tests
copying streamz/tests/test_dask.py -> 
/<>/.pybuild/cpython3_3.11_streamz/build/streamz/tests
copying streamz/tests/test_sinks.py -> 
/<>/.pybuild/cpython3_3.11_streamz/build/streamz/tests
copying streamz/tests/test_plugins.py -> 
/<>/.pybuild/cpython3_3.11_streamz/build/streamz/tests
copying streamz/tests/test_sources.py -> 
/<>/.pybuild/cpython3_3.11_streamz/build/streamz/tests
creating 
/<>/.pybuild/cpython3_3.11_streamz/build/streamz/dataframe/tests
copying streamz/dataframe/tests/test_dataframes.py -> 
/<>/.pybuild/cpython3_3.11_streamz/build/streamz/dataframe/tests
copying streamz/dataframe/tests/test_dataframe_utils.py -> 
/<>/.pybuild/cpython3_3.11_streamz/build/streamz/dataframe/tests
   dh_auto_test -i -O--buildsystem=pybuild
I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11_streamz/build; 
python3.11 -m pytest
= test session starts ==
platform linux -- Python 3.11.1, pytest-7.2.1, pluggy-1.0.0+repack
rootdir: /<>, configfile: setup.cfg
plugins: flaky-3.7.0
collected 1569 items / 2 skipped

streamz/dataframe/tests/test_dataframe_utils.py .s.s [  0%]
streamz/dataframe/tests/test_dataframes.py . [  2%]
 [  6%]
 [ 11%]
...ss... [ 15%]
.sss [ 20%]
 [ 25%]
 [ 29%]
 [ 34%]
 [ 38%]
 [ 43%]
s.xxx... [ 47%]
...X.X.X.X.X.X.X.X.. [ 52%]
...X.X.X.X.X.X.X.X.X.X.X.X.. [ 57%]

Bug#1030965: marked as done (libsmali-java: autopkgtest regression)

[Debian Bug Tracking System]

Your message dated Mon, 13 Feb 2023 11:51:25 +
with message-id 
and subject line Bug#1030965: fixed in libsmali-java 2.5.2.git2771eae-2
has caused the Debian Bug report #1030965,
regarding libsmali-java: autopkgtest regression
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1030965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030965
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libsmali-java
Version: 2.5.2.git2771eae-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/libs/libsmali-java/31172804/log.gz

...
autopkgtest [21:48:48]: test roundtrip: [---
readlink: missing operand
Try 'readlink --help' for more information.
autopkgtest [21:48:48]: test roundtrip: ---]
autopkgtest [21:48:48]: test roundtrip:  - - - - - - - - - - results - - - - - 
- - - - -
roundtripFAIL non-zero exit status 1
--- End Message ---
--- Begin Message ---
Source: libsmali-java
Source-Version: 2.5.2.git2771eae-2
Done: Hans-Christoph Steiner 

We believe that the bug you reported is fixed in the latest version of
libsmali-java, 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 1030...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Hans-Christoph Steiner  (supplier of updated libsmali-java 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 13 Feb 2023 12:42:17 +0100
Source: libsmali-java
Architecture: source
Version: 2.5.2.git2771eae-2
Distribution: unstable
Urgency: medium
Maintainer: Android Tools Maintainers 

Changed-By: Hans-Christoph Steiner 
Closes: 1030965
Changes:
 libsmali-java (2.5.2.git2771eae-2) unstable; urgency=medium
 .
   * apkpgtest Depends: default-jre-headless (Closes: #1030965)
Checksums-Sha1:
 e5aa699a8086625a4f87d406f81a7dce7e368332 2125 
libsmali-java_2.5.2.git2771eae-2.dsc
 6098467fcf98d6f1fbd1d97e5739f0c60be9e3f4 19524 
libsmali-java_2.5.2.git2771eae-2.debian.tar.xz
 b4fe4167a9f833e0ddf1e1b3fb4b4619f5fdb415 16266 
libsmali-java_2.5.2.git2771eae-2_source.buildinfo
Checksums-Sha256:
 4164ebb33176010d0b672d1cc5ae585298580cdc0a908f5b648a15397ae63918 2125 
libsmali-java_2.5.2.git2771eae-2.dsc
 3a087895b64c09d630ad6d85bfde20900aabf09e603aee51caf374eca7967647 19524 
libsmali-java_2.5.2.git2771eae-2.debian.tar.xz
 1f7eaaa561f50fb6f01a0d6be23d429c056ee1e0236464c59a43e79f24dcf974 16266 
libsmali-java_2.5.2.git2771eae-2_source.buildinfo
Files:
 bec6a23a1c5f9133a037dd0f486bbbd2 2125 java optional 
libsmali-java_2.5.2.git2771eae-2.dsc
 ecd3db76baf74f3c6098f1998341e1fa 19524 java optional 
libsmali-java_2.5.2.git2771eae-2.debian.tar.xz
 fc9265a7d2b10e0d9a539406b5160be0 16266 java optional 
libsmali-java_2.5.2.git2771eae-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEElyI52+aGmfUmwGoFPhd4F7obm/oFAmPqIlMACgkQPhd4F7ob
m/q6aggAgE649YQBRd1VwlLDxqNZ3gtP7WuC46plWEI2gUqrns6l7FzJFCS4v/EY
UjXzTLDEBBiS1BKrtXJ3oxsXtXG2vCRgyjvovgYgAu0sywbfsRvWtJXuVZXl2fHh
1s4quQLyrJGeTJdqfQnfrsmv0/jbdKGQL7ILkKmuWanJS+GAnF/6RMYR3/pfJzRn
Y/OLw4ZoWYcvC5gjpPIqNsqZ/Kypm+c6YK6TdlC5jWUxCfuTEhyh40FTOGPc6RFn
UQxSyHqUpMVMPg6ox0Gcm//3C9y6pi0zBPEfkglfj3Uetg3nRW8IT+Mf0JUsC1BE
cK5f5poMnD3wigTWtF90aVIAK1Gs6w==
=/X88
-END PGP SIGNATURE End Message ---

Bug#1026728: Update to 2.4.0 should fix FTBFS

[Adrien Nader]

Hi,

I was looking at this FTBFS in Ubuntu and noticed that upstream has
migrated to github, away from bitbucket. You can see a link from the
current upstream page to pypi and then land on github. It is not the
same person though but both of them are listed on the pypi page.

I'm going to email the original author and ask for some clarifications.

Anyway, upstream doesn't seem to have the same FTBFS. Please note that I
didn't try to update the package and I can't tell how much work this
needs but updating looks like the better path for maintenance.

-- 
Adrien

Processed: Re: Bug#1031197: firmware-ath9k-htc: Conflict with firmware-atheros < 20230210-1

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1031197 [firmware-ath9k-htc] firmware-ath9k-htc: Conflict with 
firmware-atheros < 20230210-1
Severity set to 'serious' from 'normal'

-- 
1031197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1026639: rhino FTBFS

[Markus Koschany]

Am Montag, dem 13.02.2023 um 11:04 +0100 schrieb Markus Koschany:
> preserve-backward-compatibility.patch

To answer my own question. Yes, this is still needed otherwise closure-compiler
starts to FTBFS



signature.asc
Description: This is a digitally signed message part

Bug#1026639: rhino FTBFS

[Markus Koschany]

Am Montag, dem 13.02.2023 um 12:14 +0200 schrieb Adrian Bunk:
> On Mon, Feb 13, 2023 at 11:04:38AM +0100, Markus Koschany wrote:
> > ...
> > I don't really like to use gradle for a key package.
> > ...
> 
> FTR, gradle is already a key package:
> libxi -> asciidoc -> fop -> mockito -> gradle

I know. That's what I want to change in the future.


signature.asc
Description: This is a digitally signed message part

Bug#1026639: rhino FTBFS

[Adrian Bunk]

On Mon, Feb 13, 2023 at 11:04:38AM +0100, Markus Koschany wrote:
>...
> I don't really like to use gradle for a key package.
>...

FTR, gradle is already a key package:
libxi -> asciidoc -> fop -> mockito -> gradle

> Markus

cu
Adrian

Bug#1026639: rhino FTBFS

[Markus Koschany]

Am Montag, dem 13.02.2023 um 09:33 +0100 schrieb Emmanuel Bourg:
> I don't think this should be assigned to rhino. ckeditor should
> open the internal packages it touches.

I'm currently working on rhino. I have packaged 1.7.14 now. I haven't looked
into ckeditor yet but it seems we have to upgrade rhino anyway. At least
openrefine fails with a silent error when rendering javascript in its webapp
and there may be other errors with OpenJDK 17. Fortunately rhino has no build
dependencies on other packages. However I had to change the way how we build
the package because upstream removed support for ant and I don't really like to
use gradle for a key package. Hence I am using just javahelper now which seems
to work fine. I'm a bit confused about all the old rhino patches. script-
engine.patch is included in the sources now, but I'm not not sure if we still
need the others like preserve-backward-compatibility. Right now I am rebuilding
everything with ratt. There is a build failure with libapache-poi-java. I'm
going to upload my current work to Git.

Markus


signature.asc
Description: This is a digitally signed message part

Bug#1026639: rhino FTBFS

[Emmanuel Bourg]

I don't think this should be assigned to rhino. ckeditor should
open the internal packages it touches.

Bug#1031108: marked as done (kotlin: FTBFS (Build failed with an exception))

[Debian Bug Tracking System]

Your message dated Mon, 13 Feb 2023 09:21:01 +
with message-id 
and subject line Bug#1031108: fixed in kotlin 1.3.31+~1.0.1+~0.11.12-6
has caused the Debian Bug report #1031108,
regarding kotlin: FTBFS (Build failed with an exception)
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.)


-- 
1031108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031108
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:kotlin
Version: 1.3.31+~1.0.1+~0.11.12-5
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=gradle --with-maven-repo-helper
   dh_update_autotools_config -i -O--buildsystem=gradle 
-O--with-maven-repo-helper
   dh_autoreconf -i -O--buildsystem=gradle -O--with-maven-repo-helper
   dh_auto_configure -i -O--buildsystem=gradle -O--with-maven-repo-helper
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
sed -e "s|__VERSION__|1.3.31|g" < debian/kotlin.poms.in > debian/kotlin.poms
# Build atomicfu component
dh_auto_build -- --project-dir=atomicfu  
-Dkotlin.compiler.execution.strategy=in-proces -Pkotlin_version=1.3.31 
-Pversion=0.11.12 install
mkdir -p .gradle/init.d
cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/
gradle --info --console plain --offline --stacktrace --no-daemon 
--refresh-dependencies --gradle-user-home .gradle -Duser.home=. 
-Duser.name=debian -Ddebian.package=kotlin -Dfile.encoding=UTF-8 
--project-dir=atomicfu -Dkotlin.compiler.execution.strategy=in-proces 
-Pkotlin_version=1.3.31 -Pversion=0.11.12 install
openjdk version "17.0.6" 2023-01-17

[... snipped ...]

Skipping task ':compiler:backend.jvm:processResources' as it has no source 
files and no previous output files.
:compiler:backend.jvm:processResources NO-SOURCE
:compiler:backend.jvm:processResources (Thread[Daemon worker,5,main]) 
completed. Took 0.0 secs.
:compiler:backend.jvm:classes (Thread[Daemon worker,5,main]) started.
:compiler:backend.jvm:classes
Skipping task ':compiler:backend.jvm:classes' as it has no actions.
:compiler:backend.jvm:classes (Thread[Daemon worker,5,main]) completed. Took 
0.0 secs.
:compiler:backend.jvm:debianMavenPom (Thread[Daemon worker,5,main]) started.
:compiler:backend.jvm:debianMavenPom
Putting task artifact state for task ':compiler:backend.jvm:debianMavenPom' 
into context took 0.0 secs.
Up-to-date check for task ':compiler:backend.jvm:debianMavenPom' took 0.0 secs. 
It is not up-to-date because:
  No history is available.
Generating pom file 
/<>/compiler/ir/backend.jvm/build/debian/backend.jvm.pom
:compiler:backend.jvm:debianMavenPom (Thread[Daemon worker,5,main]) completed. 
Took 0.021 secs.
:compiler:backend.jvm:inspectClassesForKotlinIC (Thread[Daemon worker,5,main]) 
started.
:compiler:backend.jvm:inspectClassesForKotlinIC
Putting task artifact state for task 
':compiler:backend.jvm:inspectClassesForKotlinIC' into context took 0.0 secs.
Up-to-date check for task ':compiler:backend.jvm:inspectClassesForKotlinIC' 
took 0.004 secs. It is not up-to-date because:
  No history is available.
:compiler:backend.jvm:inspectClassesForKotlinIC (Thread[Daemon worker,5,main]) 
completed. Took 0.009 secs.
:compiler:backend.jvm:jar (Thread[Daemon worker,5,main]) started.
:compiler:backend.jvm:jar
Putting task artifact state for task ':compiler:backend.jvm:jar' into context 
took 0.0 secs.
Up-to-date check for task ':compiler:backend.jvm:jar' took 0.004 secs. It is 
not up-to-date because:
  No history is available.
:compiler:backend.jvm:jar (Thread[Daemon worker,5,main]) completed. Took 0.049 
secs.
:core:descriptors.runtime:compileKotlin (Thread[Daemon worker,5,main]) started.
:core:descriptors.runtime:compileKotlin
Putting task artifact state for task ':core:descriptors.runtime:compileKotlin' 
into context took 0.0 secs.
file or directory '/<>/core/descriptors.runtime/src/main/kotlin', 
not found
file or directory '/<>/core/descriptors.runtime/src/main/java', 
not found
file or directory '/<>/core/descriptors.runtime/src/main/kotlin', 
not found
file or directory '/<>/core/descriptors.runtime/src/main/java', 
not found
Up-to-date check for task ':core:descriptors.runtime:compileKotlin' took 0.008 
secs. It is not up-to-date because:
  No history is available.
All input files are considered out-of-date for incremental task 
':core:descriptors.runtime:compileKotlin'.
file or directory 

Bug#1012890: android-platform-frameworks-base: ftbfs with GCC-12

[Roger Shimizu]

Dear Hans-Christoph,

Now the main blocker for migrating android-platform-tools from
experimental to sid is:
- 
https://qa.debian.org/excuses.php?experimental=1=android-platform-tools

And blocker for migrating android-platform-frameworks-base is Bug#1014831
- https://bugs.debian.org/1014831
I still don't have good way to resolve it.

One idea is to enable all the embedded *_test.cpp code, and to see
whether the tests pass or not.

Cheers,
Roger

On Mon, Feb 13, 2023 at 12:17 AM Hans-Christoph Steiner  wrote:
>
>
> Roger, it is great to see your progress on android-platform-tools.  Are you
> thinking of trying to get it into bookworm?  If so, let me know how I can 
> help.
> It would be really valuable to have there, but I don't know how much work 
> it'll be.

Bug#1012890: android-platform-frameworks-base: ftbfs with GCC-12

[Hans-Christoph Steiner]

Roger, it is great to see your progress on android-platform-tools.  Are you 
thinking of trying to get it into bookworm?  If so, let me know how I can help. 
It would be really valuable to have there, but I don't know how much work it'll be.

Bug#1012890: android-platform-frameworks-base: ftbfs with GCC-12

[Jochen Sprickerhof]

Hi Hans,

* Hans-Christoph Steiner  [2023-02-13 09:17]:
Roger, it is great to see your progress on android-platform-tools.  
Are you thinking of trying to get it into bookworm?  If so, let me 
know how I can help. It would be really valuable to have there, but I 
don't know how much work it'll be.


ähm, soft freeze started yesterday so no new upstream versions, please:

https://release.debian.org/testing/freeze_policy.html#soft

Cheers Jochen


signature.asc
Description: PGP signature