Bug#1016294: marked as done (pocl: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

[Debian Bug Tracking System]

Your message dated Wed, 03 Aug 2022 05:49:13 +
with message-id 
and subject line Bug#1016294: fixed in pocl 3.0-5
has caused the Debian Bug report #1016294,
regarding pocl: FTBFS: dpkg-gensymbols: error: some symbols or patterns 
disappeared in the symbols file: see diff output below
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.)


-- 
1016294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016294
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pocl
Version: 3.0-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220728 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_makeshlibs
> dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
> diff output below
> dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
> file: see diff output below
> dpkg-gensymbols: warning: debian/libpocl2/DEBIAN/symbols doesn't match 
> completely debian/libpocl2.symbols
> --- debian/libpocl2.symbols (libpocl2_3.0-4_amd64)
> +++ dpkg-gensymbolsf_Q3Gx 2022-07-29 09:30:18.279814704 +
> @@ -23,28 +23,28 @@
>   
> _ZGVZNKSt8__detail11_AnyMatcherINSt7__cxx1112regex_traitsIcEELb0ELb1ELb0EEclEcE5__nul@Base
>  3.0
>   
> _ZGVZNKSt8__detail11_AnyMatcherINSt7__cxx1112regex_traitsIcEELb0ELb1ELb1EEclEcE5__nul@Base
>  3.0
>   _ZN4pocl23eraseFunctionAndCallersEPN4llvm8FunctionE@Base 1.8-3~visibility
> -#MISSING: 1.8# 
> (optional=templinst)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE12emplace_backIJS5_EEEvDpOT_@Base
>  0.11
> -#MISSING: 1.8# 
> (optional=templinst)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE17_M_realloc_insertIJRKS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base
>  0.13-9~llvm3.8+gcc7
> -#MISSING: 1.8# 
> (optional=templinst)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE17_M_realloc_insertIJS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base
>  0.13-9~llvm3.8+gcc7
> -#MISSING: 1.8# 
> (optional=templinst)_ZNSt6vectorIPKcSaIS1_EE17_M_realloc_insertIJS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
>  0.13-9~llvm3.8+gcc7
> -#MISSING: 1.8# 
> (optional=templinst|subst)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE10_M_replaceE{size_t}{size_t}PKc{size_t}@Base
>  1.6-2~hardening
> +#MISSING: 3.0-4# 
> (optional=templinst)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE12emplace_backIJS5_EEEvDpOT_@Base
>  0.11
> +#MISSING: 3.0-4# 
> (optional=templinst)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE17_M_realloc_insertIJRKS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base
>  0.13-9~llvm3.8+gcc7
> +#MISSING: 3.0-4# 
> (optional=templinst)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE17_M_realloc_insertIJS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base
>  0.13-9~llvm3.8+gcc7
> +#MISSING: 3.0-4# 
> (optional=templinst)_ZNSt6vectorIPKcSaIS1_EE17_M_realloc_insertIJS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
>  0.13-9~llvm3.8+gcc7
> +#MISSING: 3.0-4# 
> (optional=templinst|subst)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE10_M_replaceE{size_t}{size_t}PKc{size_t}@Base
>  1.6-2~hardening
>  #MISSING: 1.8# 
> (optional=templinst|arch=mipsel)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPKcEEvT_S8_St20forward_iterator_tag@Base
>  1.1-6~llvm6.0+gcc8
> -#MISSING: 1.8# 
> (optional=templinst)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE4swapERS4_@Base
>  1.6-2~hardening
> -#MISSING: 1.8# 
> (optional=templinst|subst)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE9_M_appendEPKc{size_t}@Base
>  1.6-2~hardening
> -#MISSING: 1.8# 
> (optional=templinst)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE9_M_assignERKS4_@Base
>  1.6-2~hardening
> -#MISSING: 1.8# 
> (optional=templinst|subst)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE9_M_mutateE{size_t}{size_t}PKc{size_t}@Base
>  1.6-2~hardening
> -#MISSING: 1.8# 
> (optional=templinst)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_St9_IdentityIS5_ESt4lessIS5_ESaIS5_EE24_M_get_insert_unique_posERKS5_@Base
>  1.0
> -#MISSING: 1.8# 
> (optional=templinst)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_St9_IdentityIS5_ESt4lessIS5_ESaIS5_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS5_ERKS5_@Base
>  1.0
> 

Bug#1016129: (no subject)

[Octavio Alvarez]

On 31/07/22 14:57, Thorsten Glaser wrote:

debdiff (±version) attached. Would you prefer for me to NMU, do a
maintainer-agreed regular upload (as -2), or handle this yourself,
Octavio?


I can handle it. By the way, did the fix work for you?


• the bullseye package, as-is, is broken, so this is an RC fix there
• buster “as-is” works but if libpcap0.8 is upgraded, either via
   buster-backports or by mixing buster and bullseye packages, it’ll
   break (and we cannot retrofit a matching Breaks to libpcap0.8 in
   bullseye any more now it’s released) so buster’s will either need
   the patch applied or a versioned depends on libpcap0.8 (<< 1.10)


The proposed fix should work with both libpcap versions, so that should 
be the way to go. I'll take a look at that too.



Will you communicate with the SRM or do you wish for me to handle that?


I may need help with that. I'll get back to you.

Thanks,
Octavio.

Bug#1016569: elpa-taxy-magit-section: fails to install with emacs installed

[Andreas Beckmann]

Package: elpa-taxy-magit-section
Version: 0.9.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

...
  Setting up elpa-magit-section (3.3.0-1) ...
  tsort: -: input contains a loop:
  tsort: elpa-dash
  tsort: emacsen-common
  Install elpa-dash for emacs
  install/dash-2.19.1: Handling install of emacsen flavor emacs
  install/dash-2.19.1: byte-compiling for emacs
  Install emacsen-common for emacs
  emacsen-common: Handling install of emacsen flavor emacs
  Install elpa-magit-section for emacs
  install/magit-section-3.3.0: Handling install of emacsen flavor emacs
  install/magit-section-3.3.0: byte-compiling for emacs
  Setting up elpa-taxy-magit-section (0.9.1-1) ...
  Install elpa-dash for emacs
  install/dash-2.19.1: Handling install of emacsen flavor emacs
  install/dash-2.19.1: byte-compiling for emacs
  Install emacsen-common for emacs
  emacsen-common: Handling install of emacsen flavor emacs
  Install elpa-magit-section for emacs
  install/magit-section-3.3.0: Handling install of emacsen flavor emacs
  install/magit-section-3.3.0: byte-compiling for emacs
  Install elpa-taxy-magit-section for emacs
  install/taxy-magit-section-0.9.1: Handling install of emacsen flavor emacs
  install/taxy-magit-section-0.9.1: byte-compiling for emacs
  
  In toplevel form:
  taxy-magit-section.el:38:1:Error: Cannot open load file: No such file or 
directory, taxy
  ERROR: install script from elpa-taxy-magit-section package failed
  dpkg: error processing package elpa-taxy-magit-section (--configure):
   installed elpa-taxy-magit-section package post-installation script 
subprocess returned error exit status 1
  Processing triggers for install-info (6.8-6) ...
  Errors were encountered while processing:
   elpa-taxy-magit-section


cheers,

Andreas


elpa-taxy-magit-section=0.9.1-1_emacs.log.gz
Description: application/gzip

Bug#1016566: libdap FTBFS on 32bit

[Adrian Bunk]

Source: libdap
Version: 3.20.10-1
Severity: serious
Tags: ftbfs patch fixed-upstream
Forwarded: https://github.com/OPENDAP/libdap4/pull/192

https://buildd.debian.org/status/logs.php?pkg=libdap=3.20.10-1

...
HTTPCache.cc: In member function ‘void libdap::HTTPCache::read_metadata(const 
std::string&, std::vector >&)’:
HTTPCache.cc:1034:17: error: no matching function for call to ‘min(const long 
unsigned int&, size_t)’
 1034 | line[min(line_buf_len, strnlen(line, line_buf_len))-1] = '\0'; 
// erase newline
  |  ~~~^~~
...

Bug#1016565: liblibrecast0.5: Missing Breaks+Replaces headers against liblibrecast0.4: trying to overwrite '/usr/share/man/man3/lc_ctx_new.3.gz', which is also in package liblibrecast0.4:amd64 0.4.5-1

[Axel Beckert]

Package: liblibrecast0.5
Severity: serious
Version: 0.5.1-1
Control: affects -1 lcsync

lcsync fails to upgrade due to this issue:

Unpacking liblibrecast0.5:amd64 (0.5.1-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/liblibrecast0.5_0.5.1-1_amd64.deb (--unpack):
 trying to overwrite '/usr/share/man/man3/lc_ctx_new.3.gz', which is also in 
package liblibrecast0.4:amd64 0.4.5-1
Errors were encountered while processing:
 /var/cache/apt/archives/liblibrecast0.5_0.5.1-1_amd64.deb

There seem to be Breaks and Replaces headers missing for moving this and
potentially further files from liblibrecast0.4 to liblibrecast0.5.

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), 
(500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 
'buildd-experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.18.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Processed: liblibrecast0.5: Missing Breaks+Replaces headers against liblibrecast0.4: trying to overwrite '/usr/share/man/man3/lc_ctx_new.3.gz', which is also in package liblibrecast0.4:amd64 0.4.5-1

[Debian Bug Tracking System]

Processing control commands:

> affects -1 lcsync
Bug #1016565 [liblibrecast0.5] liblibrecast0.5: Missing Breaks+Replaces headers 
against liblibrecast0.4: trying to overwrite 
'/usr/share/man/man3/lc_ctx_new.3.gz', which is also in package 
liblibrecast0.4:amd64 0.4.5-1
Added indication that 1016565 affects lcsync

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

Bug#1013045: marked as done (supertux: ftbfs with GCC-12)

[Debian Bug Tracking System]

Your message dated Wed, 03 Aug 2022 00:10:54 +
with message-id 
and subject line Bug#1013045: fixed in supertux 0.6.3-2
has caused the Debian Bug report #1013045,
regarding supertux: ftbfs with GCC-12
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.)


-- 
1013045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013045
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:supertux
Version: 0.6.3-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12

[This bug is targeted to the upcoming bookworm release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The
severity of this report will be raised before the bookworm release.

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/supertux_0.6.3-1_unstable_gcc12.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
/usr/bin/ranlib libtinygettext.a
make[6]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/tinygettext-prefix/src/tinygettext-build'
[100%] Built target tinygettext
make[5]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/tinygettext-prefix/src/tinygettext-build'
/usr/bin/cmake -E cmake_progress_start 
/<>/obj-x86_64-linux-gnu/tinygettext-prefix/src/tinygettext-build/CMakeFiles
 0
make[4]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/tinygettext-prefix/src/tinygettext-build'
cd 
/<>/obj-x86_64-linux-gnu/tinygettext-prefix/src/tinygettext-build 
&& /usr/bin/cmake -E touch 
/<>/obj-x86_64-linux-gnu/tinygettext-prefix/src/tinygettext-stamp/tinygettext-build
[  8%] Performing install step for 'tinygettext'
cd 
/<>/obj-x86_64-linux-gnu/tinygettext-prefix/src/tinygettext-build 
&& make install
make[4]: Entering directory 
'/<>/obj-x86_64-linux-gnu/tinygettext-prefix/src/tinygettext-build'
/usr/bin/cmake -S/<>/external/tinygettext 
-B/<>/obj-x86_64-linux-gnu/tinygettext-prefix/src/tinygettext-build
 --check-build-system CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start 
/<>/obj-x86_64-linux-gnu/tinygettext-prefix/src/tinygettext-build/CMakeFiles
 
/<>/obj-x86_64-linux-gnu/tinygettext-prefix/src/tinygettext-build//CMakeFiles/progress.marks
make  -f CMakeFiles/Makefile2 all
make[5]: Entering directory 
'/<>/obj-x86_64-linux-gnu/tinygettext-prefix/src/tinygettext-build'
make  -f CMakeFiles/tinygettext.dir/build.make CMakeFiles/tinygettext.dir/depend
make[6]: Entering directory 
'/<>/obj-x86_64-linux-gnu/tinygettext-prefix/src/tinygettext-build'
cd 
/<>/obj-x86_64-linux-gnu/tinygettext-prefix/src/tinygettext-build 
&& /usr/bin/cmake -E cmake_depends "Unix Makefiles" 
/<>/external/tinygettext /<>/external/tinygettext 
/<>/obj-x86_64-linux-gnu/tinygettext-prefix/src/tinygettext-build 
/<>/obj-x86_64-linux-gnu/tinygettext-prefix/src/tinygettext-build 
/<>/obj-x86_64-linux-gnu/tinygettext-prefix/src/tinygettext-build/CMakeFiles/tinygettext.dir/DependInfo.cmake
 --color=
Dependencies file "CMakeFiles/tinygettext.dir/src/dictionary.o.d" is newer than 
depends file 
"/<>/obj-x86_64-linux-gnu/tinygettext-prefix/src/tinygettext-build/CMakeFiles/tinygettext.dir/compiler_depend.internal".
Dependencies file "CMakeFiles/tinygettext.dir/src/dictionary_manager.o.d" is 
newer than depends file 
"/<>/obj-x86_64-linux-gnu/tinygettext-prefix/src/tinygettext-build/CMakeFiles/tinygettext.dir/compiler_depend.internal".
Dependencies file "CMakeFiles/tinygettext.dir/src/iconv.o.d" is newer than 
depends file 
"/<>/obj-x86_64-linux-gnu/tinygettext-prefix/src/tinygettext-build/CMakeFiles/tinygettext.dir/compiler_depend.internal".
Dependencies 

Bug#864423: Software RAID is not activated at boot time

[Chris Hofstaedtler]

Hi,

* Holger Wansing  [220802 23:37]:
> Cyril Brulebois  wrote (Sun, 31 Jul 2022 14:31:20 +0200):
> > > I was digging around in the d-i code, and it appears for dmraid to
> > > be invoked, one has to boot with disk-detect/dmraid/enable. 
> > > 
> > > I have opened merge requests to remove the dmraid/sataraid code from
> > > d-i. The changes look like low risk to me, but obviously I have no
> > > idea. For the lack of a build environment I also didn't test them.
> > > 
> > > Given d-i does nothing with dmraid unless the boot flag is present,
> > > I want to ask if dmraid could also stop shipping its udeb, if thats
> > > ok with debian-boot?
> > 
> > Given how specific it is, opt-in, on a specific arch, and dead upstream,
> > looks like a wholesale removal would be the best way forward, yes.
> 
> I have merged the merge requests filed by Chris (partman-base, partman-auto,
> hw-detect, grub-installer).
> 
> The packages build fine with those changings.
> And a locally built mini.iso with those changings in local udebs also 
> installs fine (default install) in QEMU VM.

Great, thanks for testing!

Maybe these changes can make it into unstable soon?

I'm attaching a draft patch to drop udebs from src:dmraid. Maybe you
want to use this as a starting point, László?

I would also suggest keeping dmraid for one more release, and
putting something into the release notes. To keep dmraid, I think
the severity of this bug also might need adjusting, or something.

Thanks everyone for your helping hands.

Best,
Chris

diff -Nru dmraid-1.0.0.rc16/debian/changelog dmraid-1.0.0.rc16/debian/changelog
--- dmraid-1.0.0.rc16/debian/changelog  2022-02-16 16:44:50.0 +
+++ dmraid-1.0.0.rc16/debian/changelog  2022-08-02 23:30:56.0 +
@@ -1,3 +1,10 @@
+dmraid (1.0.0.rc16-11.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop udebs. 
+
+ -- Chris Hofstaedtler   Tue, 02 Aug 2022 23:30:56 +
+
 dmraid (1.0.0.rc16-11) unstable; urgency=medium
 
   [ Helmut Grohne  ]
diff -Nru dmraid-1.0.0.rc16/debian/control dmraid-1.0.0.rc16/debian/control
--- dmraid-1.0.0.rc16/debian/control2022-02-16 16:44:50.0 +
+++ dmraid-1.0.0.rc16/debian/control2022-08-02 23:30:56.0 +
@@ -28,28 +28,6 @@
  Please read the documentation in /usr/share/doc/dmraid BEFORE attempting
  any use of this software. Improper use can cause data loss!
 
-Package: dmraid-udeb
-Architecture: linux-any
-Section: debian-installer
-Package-Type: udeb
-Depends: ${shlibs:Depends}, dmsetup-udeb
-Description: Device-Mapper Software RAID support tool (udeb)
- dmraid discovers, activates, deactivates and displays properties
- of software RAID sets (eg, ATARAID) and contained DOS partitions.
- .
- This is the minimal package (udeb) used by debian-installer
-
-Package: libdmraid1.0.0.rc16-udeb
-Architecture: linux-any
-Section: debian-installer
-Package-Type: udeb
-Depends: ${shlibs:Depends}
-Description: Device-Mapper Software RAID support tool - shared library (udeb)
- dmraid discovers, activates, deactivates and displays properties
- of software RAID sets (eg, ATARAID) and contained DOS partitions.
- .
- This is the minimal package (udeb shared library) used by debian-installer
-
 Package: libdmraid1.0.0.rc16
 Architecture: linux-any
 Multi-Arch: same
diff -Nru dmraid-1.0.0.rc16/debian/dmraid.install 
dmraid-1.0.0.rc16/debian/dmraid.install
--- dmraid-1.0.0.rc16/debian/dmraid.install 2017-08-30 21:28:37.0 
+
+++ dmraid-1.0.0.rc16/debian/dmraid.install 2022-08-02 23:30:56.0 
+
@@ -1,5 +1,5 @@
 debian/initramfs/dmraid.initramfs-hook/dmraid usr/share/initramfs-tools/hooks
 debian/initramfs/dmraid.initramfs-local-top/dmraid 
usr/share/initramfs-tools/scripts/local-top
-debian/standard/sbin/dmraid sbin
-debian/standard/usr/share/man usr/share
+debian/tmp/sbin/dmraid sbin
+debian/tmp/usr/share/man usr/share
 debian/dmraid-activate sbin
diff -Nru dmraid-1.0.0.rc16/debian/dmraid-udeb.install 
dmraid-1.0.0.rc16/debian/dmraid-udeb.install
--- dmraid-1.0.0.rc16/debian/dmraid-udeb.install2017-08-30 
21:28:37.0 +
+++ dmraid-1.0.0.rc16/debian/dmraid-udeb.install1970-01-01 
00:00:00.0 +
@@ -1,2 +0,0 @@
-debian/udeb/sbin/dmraid sbin
-debian/dmraid-activate sbin
diff -Nru dmraid-1.0.0.rc16/debian/libdmraid1.0.0.rc16.install 
dmraid-1.0.0.rc16/debian/libdmraid1.0.0.rc16.install
--- dmraid-1.0.0.rc16/debian/libdmraid1.0.0.rc16.install2022-02-03 
16:28:13.0 +
+++ dmraid-1.0.0.rc16/debian/libdmraid1.0.0.rc16.install2022-08-02 
23:30:56.0 +
@@ -1,2 +1,2 @@
 #!/usr/bin/dh-exec
-debian/standard/lib/${DEB_HOST_MULTIARCH}/*.so.* lib/${DEB_HOST_MULTIARCH}
+debian/tmp/lib/${DEB_HOST_MULTIARCH}/*.so.* lib/${DEB_HOST_MULTIARCH}
diff -Nru dmraid-1.0.0.rc16/debian/libdmraid1.0.0.rc16-udeb.install 
dmraid-1.0.0.rc16/debian/libdmraid1.0.0.rc16-udeb.install
--- dmraid-1.0.0.rc16/debian/libdmraid1.0.0.rc16-udeb.install   2022-02-03 

Processed: severity of 1016546 is normal

[Debian Bug Tracking System]

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

> # Failing to build reproducibly isn't a serious issue
> severity 1016546 normal
Bug #1016546 [rust-vergen] rust-vergen inserts build timestamps
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#1016564: haskell-cracknum FTBFS: Package contains no library to register: crackNum-3.2

[Adrian Bunk]

Source: haskell-cracknum
Version: 3.2-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=haskell-cracknum=3.2-1

...
Running debian/hlibrary.setup copy --builddir=dist-ghc 
--destdir=debian/tmp-inst-ghc
Installing executable crackNum in debian/tmp-inst-ghc/usr/bin
ln --symbolic --force "debian/tmp-inst-ghc" debian/tmp
dh_haskell_install_ghc_registration --package=libghc-cracknum-dev
Running debian/hlibrary.setup register --builddir=dist-ghc --gen-pkg-config 
--verbose=verbose+nowrap
Package contains no library to register: crackNum-3.2...
Cannot generate package registration. at 
/usr/bin/dh_haskell_install_ghc_registration line 70.
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:194: 
install/libghc-cracknum-dev] Error 25

Processed: octave-video: Use this patch instead

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1004770 [src:octave-video] octave-video: FTBFS with ffmpeg 5.0
Ignoring request to alter tags of bug #1004770 to the same tags previously set

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

Bug#1004770: octave-video: Use this patch instead

[William 'jawn-smith' Wilson]

Package: octave-video
Followup-For: Bug #1004770
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic ubuntu-patch
Control: tags -1 patch

Dear Maintainer,

The first patch I submitted was a bit messy and failed to build
with older versions of ffmpeg. A version with this patch has
built successfully for me in Ubuntu kinetic and Debian sid.

In Ubuntu, the attached patch was applied to achieve the following:


  * d/patches/ffmpeg5.patch: Update to FFMPEG 5 API.


Thanks for considering the patch.


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

Kernel: Linux 5.15.0-27-generic (SMP w/32 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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
diff -Nru octave-video-2.0.2/debian/control octave-video-2.0.2/debian/control
--- octave-video-2.0.2/debian/control   2022-07-19 08:01:01.0 -0500
+++ octave-video-2.0.2/debian/control   2022-08-02 15:58:29.0 -0500
@@ -1,8 +1,7 @@
 Source: octave-video
 Section: math
 Priority: optional
-Maintainer: Ubuntu Developers 
-XSBC-Original-Maintainer: Debian Octave Group 

+Maintainer: Debian Octave Group 
 Uploaders: Rafael Laboissière 
 Build-Depends: debhelper-compat (= 13),
dh-octave (>= 0.7.1),
diff -Nru octave-video-2.0.2/debian/patches/ffmpeg5.patch 
octave-video-2.0.2/debian/patches/ffmpeg5.patch
--- octave-video-2.0.2/debian/patches/ffmpeg5.patch 1969-12-31 
18:00:00.0 -0600
+++ octave-video-2.0.2/debian/patches/ffmpeg5.patch 2022-08-02 
15:58:29.0 -0500
@@ -0,0 +1,568 @@
+Description: Fix FTBFS with ffmpeg 5
+Author: William 'jawn-smith' Wilson 
+Origin: Ubuntu
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004770
+Last-Update: 2022-08-02
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+Index: octave-video-2.0.2/src/cap_ffmpeg_impl_ov.hpp
+===
+--- octave-video-2.0.2.orig/src/cap_ffmpeg_impl_ov.hpp
 octave-video-2.0.2/src/cap_ffmpeg_impl_ov.hpp
+@@ -525,7 +525,9 @@
+ 
+ const char* get_video_codec_name () const
+   {
+-#if LIBAVFORMAT_BUILD > 4628
++#if LIBAVFORMAT_BUILD > 6027
++return _opencv_avcodec_get_name(video_st->codecpar->codec_id);
++#elif LIBAVFORMAT_BUILD > 4628
+ return _opencv_avcodec_get_name(video_st->codec->codec_id);
+ #else
+ return _opencv_avcodec_get_name(video_st->codec.codec_id);
+@@ -604,7 +606,9 @@
+ 
+ void CvCapture_FFMPEG::init()
+ {
++#if LIBAVFORMAT_BUILD < CALC_FFMPEG_VERSION(59, 0, 0)
+ av_register_all();
++#endif
+ ic = 0;
+ video_stream = -1;
+ video_st = 0;
+@@ -651,7 +655,10 @@
+ 
+ if( video_st )
+ {
+-#if LIBAVFORMAT_BUILD > 4628
++#if LIBAVFORMAT_BUILD > 6027
++AVCodecContext *context;
++avcodec_parameters_to_context(context, video_st->codecpar);
++#elif LIBAVFORMAT_BUILD > 4628
+ avcodec_close( video_st->codec );
+ 
+ #else
+@@ -842,6 +849,7 @@
+ 
+ static ImplMutex _mutex;
+ 
++#if LIBAVFORMAT_BUILD < CALC_FFMPEG_VERSION(59, 0, 0)
+ static int LockCallBack(void **mutex, AVLockOp op)
+ {
+ ImplMutex* localMutex = reinterpret_cast(*mutex);
+@@ -872,6 +880,7 @@
+ }
+ return 0;
+ }
++#endif
+ 
+ 
+ static void ffmpeg_log_callback(void *ptr, int level, const char *fmt, 
va_list vargs)
+@@ -900,11 +909,13 @@
+ avformat_network_init();
+ #endif
+ 
++#if LIBAVFORMAT_BUILD < CALC_FFMPEG_VERSION(59, 0, 0)
+ /* register all codecs, demux and protocols */
+ av_register_all();
+ 
+ /* register a callback function for synchronization */
+ av_lockmgr_register();
++#endif
+ 
+ #ifndef NO_GETENV
+ char* debug_option = getenv("OPENCV_FFMPEG_DEBUG");
+@@ -919,10 +930,12 @@
+ av_log_set_level(AV_LOG_ERROR);
+ }
+ }
++#if LIBAVFORMAT_BUILD < CALC_FFMPEG_VERSION(59, 0, 0)
+ ~InternalFFMpegRegister()
+ {
+ av_lockmgr_register(NULL);
+ }
++#endif
+ };
+ 
+ bool CvCapture_FFMPEG::open( const char* _filename )
+@@ -962,6 +975,9 @@
+ #else
+ av_dict_set(, "rtsp_transport", "tcp", 0);
+ #endif
++#if LIBAVFORMAT_BUILD > CALC_FFMPEG_VERSION(59, 0, 0)
++const
++#endif
+ AVInputFormat* input_format = NULL;
+ AVDictionaryEntry* entry = av_dict_get(dict, "input_format", NULL, 0);
+ if (entry != 0)
+@@ -993,7 +1009,10 @@
+ }
+ for(i = 0; i < ic->nb_streams; i++)
+ {
+-#if LIBAVFORMAT_BUILD > 4628
++#if LIBAVFORMAT_BUILD >= CALC_FFMPEG_VERSION(59, 0, 0)
++AVCodecContext *enc;
++avcodec_parameters_to_context(enc, ic->streams[i]->codecpar);
++#elif LIBAVFORMAT_BUILD > 4628
+ AVCodecContext *enc = 

Bug#1016563: debhelper: Should dh_dwz be dropped?

[Adrian Bunk]

Package: debhelper
Version: 13.8
Severity: serious
X-Debbugs-Cc: debian-de...@lists.debian.org

[ debian-devel is in Cc for getting further input. ]

dh_dwz is part of the standard sequence in dh since debhelper compat 12.

dwz offers small optimizations of debug info, the typical benefit
seems to be ~ 3% size reduction.

These optimizations are only in the -dbgsym packages that nearly
noone installs and nearly noone uses.

Debug info is super useful when needed, but it is not installed by
default and dwz optimizations have little practical relevance in the
cases when it is used.

OTOH, the cases where dh_dwz has created additional work for maintainers
are many.[1]

dwz is processing debug info from several producers on many architectures,
and this sometimes breaks in various ways.

On arm64, gcc in stable sometime produces debug info that dwz in
stable cannot handle.[2]

C++ code can result in huge debuginfo, resulting in dwz exhausting
the address space on 32bit architectures, requiring workarounds from
maintainers.[3]

clang 14 which is now default in instable defaults to DWARF 5,
and dwz in unstable has some problems with that.[4,5]

Scroll through [1] for more workarounds for problems in dwz.

The track record of such bugs in dwz getting fixed swiftly is not good.
This is a real problem if dwz is a core toolchain tool most packages
are using by default, and usually maintainers are forced to use
override_dh_dwz whenever dwz chokes on what it is supposed to process.

IMHO the small benefits of dh_dwz are not worth the constant extra work
it causes, and it should be dropped from the standard sequence in dh.

Dropping dh_dwz from the standard sequence in dh could also be done
in the compat levels 12 and 13 since such a change should not cause
user-visible changes (except for a slight size increase of -dbgsym)

Ignoring errors from dh_dwz by default might work if we can trust
that dwz does not touch the file in case of errors, but it feels
wrong to ignore errors.


[1] https://codesearch.debian.net/search?q=override_dh_dwz=1
[2] 
https://sources.debian.org/src/qt6-base/6.2.4%2Bdfsg-10~bpo11%2B1/debian/rules/#L97
[3] https://sources.debian.org/src/qtcreator/8.0.0-2/debian/rules/#L66
[4] https://bugs.debian.org/1016329
[5] https://bugs.debian.org/1016330

Bug#1015031: marked as done (irssi-plugin-xmpp: FTBFS: xep/ping.c:169:37: error: request for member ‘tv_sec’ in something not a structure or union)

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2022 22:20:41 +
with message-id 
and subject line Bug#1015031: fixed in irssi-plugin-xmpp 
0.54+git20191101+c13fa5-1.1
has caused the Debian Bug report #1015031,
regarding irssi-plugin-xmpp: FTBFS: xep/ping.c:169:37: error: request for 
member ‘tv_sec’ in something not a structure or union
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.)


-- 
1015031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015031
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: irssi-plugin-xmpp
Version: 0.54+git20191101+c13fa5-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220716 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -fPIC -DUOFF_T_LONG -fPIC -DUOFF_T_LONG  
> -I../../src/core -I/usr/include/irssi -I/usr/include/irssi/src 
> -I/usr/include/irssi/src/core -I/usr/include/irssi/src/fe-common/core 
> -I/usr/include/irssi/src/fe-text `pkg-config --cflags glib-2.0` `pkg-config 
> --cflags loudmouth-1.0` -o xep/vcard.o -c xep/vcard.c
> xep/ping.c:41:9: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead 
> [-Wdeprecated-declarations]
>41 | GTimeVal  time;
>   | ^~~~
> In file included from /usr/include/glib-2.0/glib/galloca.h:32,
>  from /usr/include/glib-2.0/glib.h:30,
>  from /usr/include/irssi/src/common.h:39,
>  from ../../src/core/module.h:4,
>  from xep/ping.c:26:
> /usr/include/glib-2.0/glib/gtypes.h:553:8: note: declared here
>   553 | struct _GTimeVal
>   |^
> xep/ping.c: In function ‘request_ping’:
> xep/ping.c:66:17: warning: ‘g_get_current_time’ is deprecated: Use 
> 'g_get_real_time' instead [-Wdeprecated-declarations]
>66 | g_get_current_time(>lag_sent);
>   | ^~
> In file included from /usr/include/glib-2.0/glib/giochannel.h:33,
>  from /usr/include/glib-2.0/glib.h:54,
>  from /usr/include/irssi/src/common.h:39,
>  from ../../src/core/module.h:4,
>  from xep/ping.c:26:
> /usr/include/glib-2.0/glib/gmain.h:712:8: note: declared here
>   712 | void   g_get_current_time (GTimeVal   *result);
>   |^~
> xep/ping.c:66:36: warning: passing argument 1 of ‘g_get_current_time’ from 
> incompatible pointer type [-Wincompatible-pointer-types]
>66 | g_get_current_time(>lag_sent);
>   |^
>   ||
>   |gint64 * {aka long int *}
> In file included from /usr/include/glib-2.0/glib/giochannel.h:33,
>  from /usr/include/glib-2.0/glib.h:54,
>  from /usr/include/irssi/src/common.h:39,
>  from ../../src/core/module.h:4,
>  from xep/ping.c:26:
> /usr/include/glib-2.0/glib/gmain.h:712:60: note: expected ‘GTimeVal *’ {aka 
> ‘struct _GTimeVal *’} but argument is of type ‘gint64 *’ {aka ‘long int *’}
>   712 | void   g_get_current_time (GTimeVal   *result);
>   |^~
> xep/ping.c:72:17: warning: ‘g_get_current_time’ is deprecated: Use 
> 'g_get_real_time' instead [-Wdeprecated-declarations]
>72 | g_get_current_time(>time);
>   | ^~
> In file included from /usr/include/glib-2.0/glib/giochannel.h:33,
>  from /usr/include/glib-2.0/glib.h:54,
>  from /usr/include/irssi/src/common.h:39,
>  from ../../src/core/module.h:4,
>  from xep/ping.c:26:
> /usr/include/glib-2.0/glib/gmain.h:712:8: note: declared here
>   712 | void   g_get_current_time (GTimeVal   *result);
>   |^~
> xep/ping.c: In function ‘sig_recv_iq’:
> xep/ping.c:101:9: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead 
> [-Wdeprecated-declarations]
>   101 | GTimeVal now;
>   | ^~~~
> In file included from /usr/include/glib-2.0/glib/galloca.h:32,
>  from /usr/include/glib-2.0/glib.h:30,
>  from /usr/include/irssi/src/common.h:39,
>   

Bug#1010122: marked as done (scamper FTBFS on !amd64)

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2022 22:05:43 +
with message-id 
and subject line Bug#1010122: fixed in scamper 20211212-1.1
has caused the Debian Bug report #1010122,
regarding scamper FTBFS on !amd64
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.)


-- 
1010122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010122
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scamper
Version: 20211212-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=scamper=sid

...
rm debian/tmp/usr/bin/sc_wartsfix
rm debian/tmp/usr/bin/sc_warts2csv
rm debian/tmp/usr/share/man/man1/sc_wartsfix.1
rm debian/tmp/usr/share/man/man1/sc_warts2csv.1
rm debian/tmp/usr/lib/x86_64-linux-gnu/libscamperfile.la
rm: cannot remove 'debian/tmp/usr/lib/x86_64-linux-gnu/libscamperfile.la': No 
such file or directory
make[1]: *** [debian/rules:27: override_dh_auto_install] Error 1
--- End Message ---
--- Begin Message ---
Source: scamper
Source-Version: 20211212-1.1
Done: Boyuan Yang 

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated scamper 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: Sat, 30 Jul 2022 17:26:40 -0400
Source: scamper
Architecture: source
Version: 20211212-1.1
Distribution: unstable
Urgency: medium
Maintainer: Internet Measurement Packaging Team 

Changed-By: Boyuan Yang 
Closes: 1010122
Changes:
 scamper (20211212-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/rules: Avoid hardcoding arch triplet to prevent
 FTBFS. (Closes: #1010122)
Checksums-Sha1:
 f1c3211e01196b3d718306d8bd12e11ddca3abb0 2192 scamper_20211212-1.1.dsc
 82d572d03b6de409b9aa617e37972a889ed7c94f 2099070 scamper_20211212.orig.tar.gz
 6bb037725836fb52b725d09d22830804eacb7b1e 5416 
scamper_20211212-1.1.debian.tar.xz
 c31d0deb494d8f383627c7f7829eab9733b4ace7 7027 
scamper_20211212-1.1_amd64.buildinfo
Checksums-Sha256:
 b54a53255af01c31ffc2f57365e5cbef3750466f30565ad06689052ec84ddc9b 2192 
scamper_20211212-1.1.dsc
 ae4f84aef28373701568a9e57ec44a31ec20871c33c044a5272de726acbd2d13 2099070 
scamper_20211212.orig.tar.gz
 8a9d4f3f631a5897f457e18853944d8b9cf300ec4bffa6a5d0b942befb9bc8db 5416 
scamper_20211212-1.1.debian.tar.xz
 fea3cae03599117bc44164879d053c57112027259f6587534ce98ec8753200e3 7027 
scamper_20211212-1.1_amd64.buildinfo
Files:
 f6d952fc9bdae363fb8049d164bb1f3c 2192 admin optional scamper_20211212-1.1.dsc
 83f9899736a1820bc8c0442dfe1de79d 2099070 admin optional 
scamper_20211212.orig.tar.gz
 d7b9b616e3ebbac5ccdc9bc210e875b1 5416 admin optional 
scamper_20211212-1.1.debian.tar.xz
 e37431a500b30b9cc690ddb9b3b653ff 7027 admin optional 
scamper_20211212-1.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmLlosEACgkQwpPntGGC
Ws5HQxAAn6n98y1ESotIoPtWhBNyscCCAz11LVAjkldy2FQGoAa9AS+6Z1a9xPSi
IE5JBIyglQS+Ob4Z0ZanM+evwvP7NsdAR2o1t2cE3p9+BwUdt8m+Skio2OEoBezW
JnZ9E7t5lFGanHgQWv6iVHtBOFYWOrgffL6yn+7WdL8umbLXKoG+LQ8sX4WgFiOe
PiT2AW/iZcPU4aX1cefMGZq7K2cYRVsyzbpkrmENyR11+IUYEgZmT0DNV3JtU/Ln
OMhyHpD0W/zSrzPoDxSWkEDA3KcmzF/1WEw1uQfTPiUg6a8tsotY/2grB2D0hv+I
XiDXQFJXS9dIEZRGMx1yogB7HZbJCrdnEhOnUvDPvt1Y6vjrrWG8Zhbw4i98fmp0
rhy3UexsBXSjsryEplLONwQ3hK+2QyWW0Z4IrFeCWitVsqZcTf6FPX7sfV1NJM3l
3WUrSet3fncsTUnRSHSUoUv6krm9s110+nKI2ofvaE9O/CuYRV8e6FFPmZYfNQpg
PG9xfEras+ZznC5nUws8vRL6Z9BNOFHJ7yDG2jDiUeu2+quPyFx9lUQpLC3Cs2qJ
xHwTro60AaXMA3JzYNlK+2XQIN4XustlzO73ZSRMLAtQD7OoIW+FwzAvYDcU6+uE
rLtzHF8PhiXWCPDm6inV5g22F3IV0ZidMxObrEnqfECqtc5tsUE=
=YOiq
-END PGP SIGNATURE End Message ---

Bug#1016557: xfonts-cronyx: Non-DFSG file

[Joao Eriberto Mota Filho]

Source: xfonts-cronyx
Version: 2.3.8
Severity: serious
Tags: upstream
Justification: Policy 2.2.1
X-Debbugs-Cc: eribe...@debian.org

The license for tryfont/ISO8859-5 says:

---
Copyright (c) 1991-1995 Unicode, Inc.  All Rights reserved.

This file is provided as-is by Unicode, Inc. (The Unicode Consortium).
No claims are made as to fitness for any particular purpose.  No
warranties of any kind are expressed or implied.  The recipient
agrees to determine applicability of information provided.  If this
file has been provided on magnetic media by Unicode, Inc., the sole
remedy for any claim will be exchange of defective media within 90
days of receipt.

Recipient is granted the right to make copies in any form for
internal distribution and to freely use the information supplied
in the creation of products supporting Unicode.  Unicode, Inc.
specifically excludes the right to re-distribute this file directly
to third parties or other organizations whether for profit or not.
---

Eriberto

Bug#1016510: marked as done (python3-omegaconf: ships /usr/lib/python3/dist-packages/pydevd_plugins/__init__.py, now in python3-pydevd, too)

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2022 21:09:40 +
with message-id 
and subject line Bug#1016510: fixed in python-omegaconf 2.2.2-1
has caused the Debian Bug report #1016510,
regarding python3-omegaconf: ships 
/usr/lib/python3/dist-packages/pydevd_plugins/__init__.py, now in 
python3-pydevd, too
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.)


-- 
1016510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016510
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-omegaconf
Version: 2.1.0~rc1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

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

  Selecting previously unselected package python3-pydevd.
  Preparing to unpack 
.../python3-pydevd_2.8.0+git20220714.32dee0b+dfsg-2_amd64.deb ...
  Unpacking python3-pydevd (2.8.0+git20220714.32dee0b+dfsg-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-pydevd_2.8.0+git20220714.32dee0b+dfsg-2_amd64.deb
 (--unpack):
   trying to overwrite 
'/usr/lib/python3/dist-packages/pydevd_plugins/__init__.py', which is also in 
package python3-omegaconf 2.1.0~rc1-3
  Errors were encountered while processing:
   
/var/cache/apt/archives/python3-pydevd_2.8.0+git20220714.32dee0b+dfsg-2_amd64.deb

python3-pydevd was recently introduced into the archive, please stop
shipping the conflicting files:

usr/lib/python3/dist-packages/pydevd_plugins/__init__.py
usr/lib/python3/dist-packages/pydevd_plugins/extensions/__init__.py


cheers,

Andreas


python3-omegaconf=2.1.0~rc1-3_python3-pydevd=2.8.0+git20220714.32dee0b+dfsg-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-omegaconf
Source-Version: 2.2.2-1
Done: Thomas Goirand 

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-omegaconf 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: Tue, 02 Aug 2022 17:45:50 +0200
Source: python-omegaconf
Architecture: source
Version: 2.2.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 1016510
Changes:
 python-omegaconf (2.2.2-1) unstable; urgency=medium
 .
   * New upstream release.
   * Run unit tests at build time.
   * Add autopkgtest.
   * Do not package /usr/lib/python3/dist-packages/pydevd_plugins/__init__.py
 already in pydevd (Closes: #1016510).
Checksums-Sha1:
 6eb811209b3a72a4aa5cab0c29d2a2d1357b16a4 2269 python-omegaconf_2.2.2-1.dsc
 316d72b1382dd77b336371f8f59b14728dbbfddb 3111276 
python-omegaconf_2.2.2.orig.tar.xz
 bc62091c24bfc6d29a9a3b3ad8b3316bba045830 2844 
python-omegaconf_2.2.2-1.debian.tar.xz
 e89481b1c8f2c120c8c522e452f739aeb14c0053 9513 
python-omegaconf_2.2.2-1_amd64.buildinfo
Checksums-Sha256:
 e14fe263f3ccfc4c118ee3de4a82ccef65ff6460cf6e254be240ecf2618e08cc 2269 
python-omegaconf_2.2.2-1.dsc
 f7a26b3ccb2fe3986e6f6cd2bd38bcff6c309657f5ebe4636772e84ec39325d8 3111276 
python-omegaconf_2.2.2.orig.tar.xz
 06b9c405a690b65d2bf81cbc2f08aa95cda7176409c5cf3f7cd7a1801746204a 2844 
python-omegaconf_2.2.2-1.debian.tar.xz
 4c0ad33648c3bb6c762f6e0558b41ba47374d7d22a5607c75d342ecb348704a8 9513 
python-omegaconf_2.2.2-1_amd64.buildinfo
Files:
 ccd145668a5dde5a71774d29db821205 2269 python optional 
python-omegaconf_2.2.2-1.dsc
 ed2a8e5367d13328321c32a7efc284ce 3111276 python optional 
python-omegaconf_2.2.2.orig.tar.xz
 8ee8ad685327f842b27053f4c638c256 2844 python optional 
python-omegaconf_2.2.2-1.debian.tar.xz
 2ceb87c058ab9757d156d634ecad7f2a 9513 python optional 
python-omegaconf_2.2.2-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmLphoIACgkQ1BatFaxr
Q/6FGw/9Hk93n92ApUzriyyYZN3bU0rtkDedH//SV+pJc0lOroGTqTNfnFDYVL0r
Hm3cP+Q46BhDw0Fik1e7rekEs9e4T0ow7/NeEabSEq8Xo1AHMAD1YHjjgIY1XtXt

Bug#1016228: marked as done (python-taskflow: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2022 21:09:50 +
with message-id 
and subject line Bug#1016228: fixed in python-taskflow 4.6.4-3
has caused the Debian Bug report #1016228,
regarding python-taskflow: FTBFS: E: Build killed with signal TERM after 150 
minutes of inactivity
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.)


-- 
1016228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016228
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-taskflow
Version: 4.6.4-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220728 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>   File "/usr/lib/python3/dist-packages/kombu/messaging.py", line 592, in 
> receive
> [callback(body, message) for callback in callbacks]
>   File "/usr/lib/python3/dist-packages/kombu/messaging.py", line 592, in 
> 
> [callback(body, message) for callback in callbacks]
>   File "/<>/taskflow/engines/worker_based/dispatcher.py", line 
> 167, in on_message
> self._process_message(data, message, message_type)
>   File "/<>/taskflow/engines/worker_based/dispatcher.py", line 
> 134, in _process_message
> handler.validator(data)
>   File "/<>/taskflow/engines/worker_based/protocol.py", line 
> 220, in validate
> su.schema_validate(data, schema)
>   File "/<>/taskflow/utils/schema_utils.py", line 34, in 
> schema_validate
> jsonschema.validate(data, schema, types=_SCHEMA_TYPES)
>   File "/usr/lib/python3/dist-packages/jsonschema/validators.py", line 1055, 
> in validate
> validator = cls(schema, *args, **kwargs)
> TypeError: create..Validator.__init__() got an unexpected keyword 
> argument 'types'
> E: Build killed with signal TERM after 150 minutes of inactivity


The full build log is available from:
http://qa-logs.debian.net/2022/07/28/python-taskflow_4.6.4-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220728;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220728=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: python-taskflow
Source-Version: 4.6.4-3
Done: Thomas Goirand 

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-taskflow 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: Sun, 31 Jul 2022 12:57:31 +0200
Source: python-taskflow
Architecture: source
Version: 4.6.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 1016228
Changes:
 python-taskflow (4.6.4-3) unstable; urgency=medium
 .
   * Refreshed patches.
   * Add Adapt-to-new-jsonschema-versions.patch (Closes: #1016228).
   * Add autopkgtest.
Checksums-Sha1:
 9286ce649dd3311bd6b2b2a6f18332f2fc1127a0 2887 python-taskflow_4.6.4-3.dsc
 2a02f91719edad49514b7984c72075849845a1d9 6832 
python-taskflow_4.6.4-3.debian.tar.xz
 803b913fa469bfbe844156c03703101a6544d0e6 13613 
python-taskflow_4.6.4-3_amd64.buildinfo
Checksums-Sha256:
 f93c6535f7cc91440598b8049368130d51eec4b9c98c326e9c4aedea5be93eca 2887 
python-taskflow_4.6.4-3.dsc
 2ca4ef81bc95bc8977aba69dcd4c0e155bdf91290970404db5fbc09b2c9cb28e 6832 
python-taskflow_4.6.4-3.debian.tar.xz
 dd5867affb23fe6d8b12574cda82c23676e9713c338eab842bb15ddff5a082dc 13613 
python-taskflow_4.6.4-3_amd64.buildinfo
Files:
 

Bug#1016513: marked as done (node-fetch: node-data-uri-to-buffer is now packaged separately)

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2022 21:07:24 +
with message-id 
and subject line Bug#1016513: fixed in node-fetch 3.2.10+repack1+~cs14.4.14-1
has caused the Debian Bug report #1016513,
regarding node-fetch: node-data-uri-to-buffer is now packaged separately
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.)


-- 
1016513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016513
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-fetch
Version: 3.2.9+~cs18.4.14-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files.

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

  Preparing to unpack .../node-fetch_3.2.9+~cs18.4.14-1_all.deb ...
  Unpacking node-fetch (3.2.9+~cs18.4.14-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/node-fetch_3.2.9+~cs18.4.14-1_all.deb (--unpack):
   trying to overwrite '/usr/share/nodejs/data-uri-to-buffer/dist/index.d.ts', 
which is also in package node-data-uri-to-buffer 4.0.0-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/node-fetch_3.2.9+~cs18.4.14-1_all.deb


cheers,

Andreas


node-data-uri-to-buffer=4.0.0-2_node-fetch=3.2.9+~cs18.4.14-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: node-fetch
Source-Version: 3.2.10+repack1+~cs14.4.14-1
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-fetch 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: Tue, 02 Aug 2022 21:59:36 +0200
Source: node-fetch
Architecture: source
Version: 3.2.10+repack1+~cs14.4.14-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1016513
Changes:
 node-fetch (3.2.10+repack1+~cs14.4.14-1) experimental; urgency=medium
 .
   * Team upload
   * Build missing typescript files
   * Replace component data-uri-to-buffer by dependency to
 node-data-uri-to-buffer (Closes: #1016513)
   * New upstream version 3.2.10+repack1+~cs14.4.14
Checksums-Sha1: 
 a76cd2a447aeb1a33d3d67a84f2d914886c44f2c 4416 
node-fetch_3.2.10+repack1+~cs14.4.14-1.dsc
 40cc36e734583ada92e29b85ffc4ca98942952e4 15731 
node-fetch_3.2.10+repack1+~cs14.4.14.orig-fetch-blob.tar.gz
 2b1ed24d4f2219e35e656929450f94230bb256a3 22463 
node-fetch_3.2.10+repack1+~cs14.4.14.orig-formdata-polyfill.tar.gz
 6888db46a1f71c0b76b3f7555016b63fe64766e5 3614 
node-fetch_3.2.10+repack1+~cs14.4.14.orig-node-domexception.tar.gz
 9d969c9a748e841554a40ee435d26e53fa3ee899 1075 
node-fetch_3.2.10+repack1+~cs14.4.14.orig-types-node-fetch.tar.gz
 d94ea0620c675087940738d0bed4fe7afc2534ff 105310 
node-fetch_3.2.10+repack1+~cs14.4.14.orig-web-streams-polyfill.tar.gz
 8e9da8ebda65323adbbf6d4effe6e2d3d41c3a8f 101017 
node-fetch_3.2.10+repack1+~cs14.4.14.orig.tar.gz
 f80609d032c7be62bc46f0cb5ca027a7df48a16c 54216 
node-fetch_3.2.10+repack1+~cs14.4.14-1.debian.tar.xz
Checksums-Sha256: 
 cbbdea22d267f418ae6b161c118336b59e158b66ddfb6f2cdd598a818ae2316b 4416 
node-fetch_3.2.10+repack1+~cs14.4.14-1.dsc
 0c5d1f08b67de62b961c852155e87d186fe1e9e2d46394b5fd198650839a3cbb 15731 
node-fetch_3.2.10+repack1+~cs14.4.14.orig-fetch-blob.tar.gz
 31796e5e11856ef4617b872245b997c364995a9c23b25b8b99c743fabe93424a 22463 
node-fetch_3.2.10+repack1+~cs14.4.14.orig-formdata-polyfill.tar.gz
 eba234134890897807b85c2bc67cd32d0242eb9be1d1c62513797fdaab60c971 3614 
node-fetch_3.2.10+repack1+~cs14.4.14.orig-node-domexception.tar.gz
 e766500d7cf5a3e769b009d8ef920d42dc4c266ae9db690753130bf87e0ee979 1075 
node-fetch_3.2.10+repack1+~cs14.4.14.orig-types-node-fetch.tar.gz
 011ecfc6197f97867fffb16be0d01e380295292c738f24184bf3695f16b9736d 105310 

Processed: src:squeekboard: fails to migrate to testing for too long: FTBFS on ppc64el

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.19.0-1
Bug #1016555 [src:squeekboard] src:squeekboard: fails to migrate to testing for 
too long: FTBFS on ppc64el
Marked as fixed in versions squeekboard/1.19.0-1.
Bug #1016555 [src:squeekboard] src:squeekboard: fails to migrate to testing for 
too long: FTBFS on ppc64el
Marked Bug as done
> block -1 by 1016396
Bug #1016555 {Done: Paul Gevers } [src:squeekboard] 
src:squeekboard: fails to migrate to testing for too long: FTBFS on ppc64el
1016555 was not blocked by any bugs.
1016555 was not blocking any bugs.
Added blocking bug(s) of 1016555: 1016396

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

Bug#1016555: src:squeekboard: fails to migrate to testing for too long: FTBFS on ppc64el

[Paul Gevers]

Source: squeekboard
Version: 1.17.1-1
Severity: serious
Control: close -1 1.19.0-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1016396

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:squeekboard has been trying to migrate for 
61 days [2]. Hence, I am filing this bug. Your package fails to build 
from source on ppc64el, which was reported in bug #1016396.


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=squeekboard



OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: octave-video: FTBFS with ffmpeg 5.0

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1004770 [src:octave-video] octave-video: FTBFS with ffmpeg 5.0
Added tag(s) patch.

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

Bug#1004770: octave-video: FTBFS with ffmpeg 5.0

[William 'jawn-smith' Wilson]

Package: octave-video
Followup-For: Bug #1004770
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic ubuntu-patch
Control: tags -1 patch

Dear Maintainer,

As noted in this bug, octave-video FTBFS with ffmpeg 5. This patch
resolves that failure.

In Ubuntu, the attached patch was applied to achieve the following:

  * d/patches/ffmpeg5.patch: Update to FFMPEG 5 API.

Thanks for considering the patch.


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

Kernel: Linux 5.15.0-27-generic (SMP w/32 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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
diff -Nru octave-video-2.0.2/debian/control octave-video-2.0.2/debian/control
--- octave-video-2.0.2/debian/control   2022-07-19 08:01:01.0 -0500
+++ octave-video-2.0.2/debian/control   2022-08-01 14:26:51.0 -0500
@@ -1,8 +1,7 @@
 Source: octave-video
 Section: math
 Priority: optional
-Maintainer: Ubuntu Developers 
-XSBC-Original-Maintainer: Debian Octave Group 

+Maintainer: Debian Octave Group 
 Uploaders: Rafael Laboissière 
 Build-Depends: debhelper-compat (= 13),
dh-octave (>= 0.7.1),
diff -Nru octave-video-2.0.2/debian/patches/ffmpeg5.patch 
octave-video-2.0.2/debian/patches/ffmpeg5.patch
--- octave-video-2.0.2/debian/patches/ffmpeg5.patch 1969-12-31 
18:00:00.0 -0600
+++ octave-video-2.0.2/debian/patches/ffmpeg5.patch 2022-08-01 
14:26:51.0 -0500
@@ -0,0 +1,545 @@
+Index: octave-video-2.0.2/src/cap_ffmpeg_impl_ov.hpp
+===
+--- octave-video-2.0.2.orig/src/cap_ffmpeg_impl_ov.hpp
 octave-video-2.0.2/src/cap_ffmpeg_impl_ov.hpp
+@@ -110,6 +110,8 @@
+ #define CV_WARN(message) fprintf(stderr, "warning: %s (%s:%d)\n", message, 
__FILE__, __LINE__)
+ #endif
+ 
++#define FF_API_LOCKMGR 1
++
+ static int global_err;
+ 
+ std::string get_last_err_msg ()
+@@ -526,9 +528,9 @@
+ const char* get_video_codec_name () const
+   {
+ #if LIBAVFORMAT_BUILD > 4628
+-return _opencv_avcodec_get_name(video_st->codec->codec_id);
++return _opencv_avcodec_get_name(video_st->codecpar->codec_id);
+ #else
+-return _opencv_avcodec_get_name(video_st->codec.codec_id);
++return _opencv_avcodec_get_name(video_st->codecpar.codec_id);
+ #endif
+   }
+ 
+@@ -604,7 +606,6 @@
+ 
+ void CvCapture_FFMPEG::init()
+ {
+-av_register_all();
+ ic = 0;
+ video_stream = -1;
+ video_st = 0;
+@@ -651,11 +652,13 @@
+ 
+ if( video_st )
+ {
++AVCodecContext *codec;
++  avcodec_parameters_to_context(codec, video_st->codecpar);
+ #if LIBAVFORMAT_BUILD > 4628
+-avcodec_close( video_st->codec );
++avcodec_close( codec );
+ 
+ #else
+-avcodec_close( &(video_st->codec) );
++avcodec_close(  );
+ 
+ #endif
+ video_st = NULL;
+@@ -842,38 +845,6 @@
+ 
+ static ImplMutex _mutex;
+ 
+-static int LockCallBack(void **mutex, AVLockOp op)
+-{
+-ImplMutex* localMutex = reinterpret_cast(*mutex);
+-switch (op)
+-{
+-case AV_LOCK_CREATE:
+-localMutex = new ImplMutex();
+-if (!localMutex)
+-return 1;
+-*mutex = localMutex;
+-if (!*mutex)
+-return 1;
+-break;
+-
+-case AV_LOCK_OBTAIN:
+-localMutex->lock();
+-break;
+-
+-case AV_LOCK_RELEASE:
+-localMutex->unlock();
+-break;
+-
+-case AV_LOCK_DESTROY:
+-delete localMutex;
+-localMutex = NULL;
+-*mutex = NULL;
+-break;
+-}
+-return 0;
+-}
+-
+-
+ static void ffmpeg_log_callback(void *ptr, int level, const char *fmt, 
va_list vargs)
+ {
+ static bool skip_header = false;
+@@ -900,12 +871,6 @@
+ avformat_network_init();
+ #endif
+ 
+-/* register all codecs, demux and protocols */
+-av_register_all();
+-
+-/* register a callback function for synchronization */
+-av_lockmgr_register();
+-
+ #ifndef NO_GETENV
+ char* debug_option = getenv("OPENCV_FFMPEG_DEBUG");
+ if (debug_option != NULL)
+@@ -919,10 +884,6 @@
+ av_log_set_level(AV_LOG_ERROR);
+ }
+ }
+-~InternalFFMpegRegister()
+-{
+-av_lockmgr_register(NULL);
+-}
+ };
+ 
+ bool CvCapture_FFMPEG::open( const char* _filename )
+@@ -962,7 +923,7 @@
+ #else
+ av_dict_set(, "rtsp_transport", "tcp", 0);
+ #endif
+-AVInputFormat* input_format = NULL;
++const AVInputFormat* input_format = NULL;
+ AVDictionaryEntry* entry = av_dict_get(dict, "input_format", NULL, 0);
+ if (entry != 0)
+ {
+@@ -994,7 +955,8 @@

Bug#1016228: marked as pending in python-taskflow

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1016228 in python-taskflow reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/openstack-team/libs/python-taskflow/-/commit/b2aac72727e983746b42ee3f1a6fe50b4d7d04a1


Add Adapt-to-new-jsonschema-versions.patch (Closes: #1016228).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1016228

Processed: Bug#1016228 marked as pending in python-taskflow

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1016228 [src:python-taskflow] python-taskflow: FTBFS: E: Build killed with 
signal TERM after 150 minutes of inactivity
Added tag(s) pending.

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

Bug#1016546: rust-vergen inserts build timestamps

[Maxime Devos]

On 02-08-2022 20:41, Geert Stappers wrote:


Date: Tue, 2 Aug 2022 19:18:46 +0200, From: Maxime Devos

In Guix, I've noticed that rust-vergen embeds build timestamps. There is also
a work-around available: .
  


Thanks for reporting the FTBR.

Please update the workaround, so it looks more
like https://en.wikipedia.org/wiki/Diff#Unified_format
and can be absured by https://en.wikipedia.org/wiki/Patch_(Unix)


Just telling the filename that needs modification would be a great help.


Oops, I did not send the full work-around, here it is:


     (substitute* (find-files "." "\\.rs$")
       (("^extern crate chrono;") "extern crate chrono; use 
chrono::Utc; use chrono::TimeZone;")
       (("^use chrono::Utc;") "use chrono::Utc; use 
chrono::TimeZone;")

       (("\\bUtc::now\\(\\)") "Utc.timestamp(0, 0)"))

(Should hopefully be clearer now!)

The important thing here is replacing all instances of Utc::now() 
(across all Rust source files of rust-vergen) by Utc.timestamp(0, 0), 
the rest is just adding the required imports -- I have not made a list 
of all file names.  If you want a list, try "grep -rF Utc::now" or such.


I do not intend to update the workaround, it works fine in Guix and 
frankly porting it to whatever format Debian likes is Debian's concern, 
not Guix', I'm just sharing our workaround as a courtesy to another distro.


Greetings,
Maxime.



OpenPGP_0x49E3EE22191725EE.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1015983: marked as done (undertow: CVE-2021-3859)

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2022 21:43:32 +0200
with message-id <6bc24eedb504cf54e8c2efb81d80006d0b5c9a05.ca...@debian.org>
and subject line Re: undertow: CVE-2021-3859
has caused the Debian Bug report #1015983,
regarding undertow: CVE-2021-3859
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.)


-- 
1015983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015983
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: undertow
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for undertow.

CVE-2021-3859[0]:
https://bugzilla.redhat.com/show_bug.cgi?id=2010378

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2021-3859
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3859

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Version: 2.2.16-1

fixed upstream in 2.2.15. First Debian version was 2.2.16-1

https://github.com/undertow-io/undertow/commit/e43f0ada3f4da6e8579e0020cec3cb1a81e487c2


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

Bug#1016551: cawbird: Switch to librest 1.0 and libsoup3

[Jeremy Bicha]

Source: cawbird
Version: 1.5-1
Severity: serious
Forwarded: https://github.com/IBBoard/cawbird/issues/464

cawbird won't work with the new version of librest that is linked
against libsoup3. See more details in the forwarded bug.

We will upload the new librest to experimental soon after
https://bugs.debian.org/1015285 is handled.


Thank you,
Jeremy Bicha

Bug#1016550: gfbgraph: unmaintained, depends on old libsoup

[Jeremy Bicha]

Source: gfbgraph
Version: 0.2.5-2
Severity: serious

gfbgraph needs to be ported to the new librest 1.0 API and libsoup3.
Because I don't intend to have more than one version of librest in
Debian, gfbgraph will need to be removed.

There really isn't anything else using gfbgraph currently since core
GNOME has stopped using it because of this issue.

Thank you,
Jeremy Bicha

Bug#1016546: rust-vergen inserts build timestamps

[Geert Stappers]

Date: Tue, 2 Aug 2022 19:18:46 +0200, From: Maxime Devos
> 
> In Guix, I've noticed that rust-vergen embeds build timestamps. There is also
> a work-around available: .
 

Thanks for reporting the FTBR.

Please update the workaround, so it looks more
like https://en.wikipedia.org/wiki/Diff#Unified_format
and can be absured by https://en.wikipedia.org/wiki/Patch_(Unix)


Just telling the filename that needs modification would be a great help.



Groeten
Geert Stappers
Has set Reply-To to wanted destination (the BTS).
-- 
Silence is hard to parse

Bug#1016519: marked as done (ffmpeg: FTBFS)

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2022 18:49:33 +
with message-id 
and subject line Bug#1016519: fixed in ffmpeg 7:5.1-2
has caused the Debian Bug report #1016519,
regarding ffmpeg: 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.)


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

Source: ffmpeg
Version: 7:5.1-1
Severity: serious

Hello, version 5.1-1 is currently FTBFS on s390x (and all Big Endian 
architectures?).
Can you please have a look?

thanks

G.

TESTfilter-overlay_yuv420p10
/<>/tests/fate-run.sh fate-filter-overlay_yuv420p10 "" "" 
"/<>/debian/standard" 'framecrc -auto_conversion_filters -c:v pgmyuv -i 
/<>/debian/standard/tests/vsynth1/%02d.pgm -filter_complex_script 
/<>/debian/standard/tests/data/filtergraphs/overlay_yuv420p10 -pix_fmt yuv420p10le -frames:v 3' '' '' '' '1' '' '' '' '' '' '' '' '' 
'' ''
 /<>/debian/standard/ffmpeg -nostdin -nostats -noauto_conversion_filters -cpuflags all 
-auto_conversion_filters -c:v pgmyuv -hwaccel none -threads 1 -thread_type frame+slice -i 
/<>/debian/standard/tests/vsynth1/%02d.pgm -filter_complex_script 
/<>/debian/standard/tests/data/filtergraphs/overlay_yuv420p10 -pix_fmt yuv420p10le 
-frames:v 3 -bitexact -f framecrc -
TESTfilter-overlay_nv12
/<>/tests/fate-run.sh fate-filter-overlay_nv12 "" "" "/<>/debian/standard" 'framecrc 
-auto_conversion_filters -c:v pgmyuv -i /<>/debian/standard/tests/vsynth1/%02d.pgm -filter_complex_script 
/<>/debian/standard/tests/data/filtergraphs/overlay_nv12' '' '/<>/tests/ref/fate/filter-overlay_yuv420' '' '1' '' '' '' 
'' '' '' '' '' '' ''
 /<>/debian/standard/ffmpeg -nostdin -nostats -noauto_conversion_filters -cpuflags all 
-auto_conversion_filters -c:v pgmyuv -hwaccel none -threads 1 -thread_type frame+slice -i 
/<>/debian/standard/tests/vsynth1/%02d.pgm -filter_complex_script 
/<>/debian/standard/tests/data/filtergraphs/overlay_nv12 -bitexact -f framecrc -
--- /<>/tests/ref/fate/filter-overlay_yuv420p102022-07-22 
17:58:40.0 +
+++ tests/data/fate/filter-overlay_yuv420p102022-07-31 19:51:46.046562449 
+
@@ -3,6 +3,6 @@
 #codec_id 0: rawvideo
 #dimensions 0: 352x288
 #sar 0: 0/1
-0,  0,  0,1,   304128, 0x524bcfc6
-0,  1,  1,1,   304128, 0xab3a13af
-0,  2,  2,1,   304128, 0xac08d718
+0,  0,  0,1,   304128, 0xd041d116
+0,  1,  1,1,   304128, 0x293f14ff
+0,  2,  2,1,   304128, 0x2a0dd868
Test filter-overlay_yuv420p10 failed. Look at 
tests/data/fate/filter-overlay_yuv420p10.err for details.
ffmpeg version 5.1-1 Copyright (c) 2000-2022 the FFmpeg developers
  built with gcc 12 (Debian 12.1.0-7)
  configuration: --prefix=/usr --extra-version=1 --toolchain=hardened 
--libdir=/usr/lib/s390x-linux-gnu --incdir=/usr/include/s390x-linux-gnu 
--arch=s390x --enable-gpl --disable-stripping --enable-gnutls --enable-ladspa 
--enable-libaom --enable-libass --enable-libbluray --enable-libbs2b 
--enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libdav1d 
--enable-libflite --enable-libfontconfig --enable-libfreetype 
--enable-libfribidi --enable-libglslang --enable-libgme --enable-libgsm 
--enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg 
--enable-libopenmpt --enable-libopus --enable-libpulse --enable-librabbitmq 
--enable-librist --enable-librubberband --enable-libshine --enable-libsnappy 
--enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh 
--enable-libsvtav1 --enable-libtheora --enable-libtwolame --enable-libvidstab 
--enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx265 
--enable-libxml2 --enable-libxvid --enable-libzimg --enable-libzmq 
--enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl 
--enable-opengl --enable-sdl2 --disable-sndio --enable-librsvg 
--enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint 
--enable-frei0r --enable-libplacebo --enable-libx264 
--ignore-tests='hapenc-hap-none,hapenc-hapa-none,hapenc-hapq-none' 
--enable-shared
  libavutil  57. 28.100 / 57. 28.100
  libavcodec 59. 37.100 / 59. 37.100
  libavformat59. 27.100 / 59. 27.100
  libavdevice59.  7.100 / 59.  7.100
  libavfilter 8. 44.100 /  8. 44.100
  libswscale  6.  7.100 /  6.  7.100
  libswresample   4.  7.100 /  4.  7.100
  libpostproc56.  6.100 / 56.  6.100
Input #0, image2, from 
'/<>/debian/standard/tests/vsynth1/%02d.pgm':
  Duration: 

Bug#1014633: marked as done (linux-headers-5.19.0-rc4-common: file check-local-export does not exist)

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2022 18:00:11 +
with message-id 
and subject line Bug#1014633: fixed in linux 5.19-1~exp1
has caused the Debian Bug report #1014633,
regarding linux-headers-5.19.0-rc4-common: file check-local-export does not 
exist
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.)


-- 
1014633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014633
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-headers-5.19.0-rc4-common
Version: 5.19~rc4-1~exp1
Severity: serious

Hello.
I can't build kernel module

DKMS make.log for rtl88x2bu-git for kernel 5.19.0-rc4-amd64 (x86_64)
Пн 04 июл 2022 22:11:57 MSK
make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/5.19.0-rc4-amd64/build 
M=/var/lib/dkms/rtl88x2bu/git/build modules
make[1]: вход в каталог «/usr/src/linux-headers-5.19.0-rc4-amd64»
CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_cmd.o
CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_security.o
/bin/sh: 1: 
/usr/src/linux-headers-5.19.0-rc4-common/scripts/check-local-export: not found
make[2]: *** 
[/usr/src/linux-headers-5.19.0-rc4-common/scripts/Makefile.build:254: 
/var/lib/dkms/rtl88x2bu/git/build/core/rtw_security.o] Ошибка 127
make[2]: *** Удаляется файл 
«/var/lib/dkms/rtl88x2bu/git/build/core/rtw_security.o»
make[2]: *** Ожидание завершения заданий…
/bin/sh: 1: 
/usr/src/linux-headers-5.19.0-rc4-common/scripts/check-local-export: not found
make[2]: *** 
[/usr/src/linux-headers-5.19.0-rc4-common/scripts/Makefile.build:254: 
/var/lib/dkms/rtl88x2bu/git/build/core/rtw_cmd.o] Ошибка 127
make[2]: *** Удаляется файл «/var/lib/dkms/rtl88x2bu/git/build/core/rtw_cmd.o»
make[1]: *** [/usr/src/linux-headers-5.19.0-rc4-common/Makefile:1867: 
/var/lib/dkms/rtl88x2bu/git/build] Ошибка 2
make[1]: выход из каталога «/usr/src/linux-headers-5.19.0-rc4-amd64»
make: *** [Makefile:2454: modules] Ошибка 2


Debian don't have file check-local-export at all
https://packages.debian.org/search?suite=default=all=any=contents=check-local-export
https://packages.debian.org/search?suite=sid=any=contents=check-local-export
But on previous kernels build was successful.
And there is no problem on original 5.19.0-rc4 kernel.
See also https://github.com/RinCat/RTL88x2BU-Linux-Driver/issues/143
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.19-1~exp1
Done: Salvatore Bonaccorso 

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated linux 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: Tue, 02 Aug 2022 16:04:51 +0200
Source: linux
Architecture: source
Version: 5.19-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 958904 999551 1013870 1014633
Changes:
 linux (5.19-1~exp1) experimental; urgency=medium
 .
   * New upstream release: https://kernelnewbies.org/Linux_5.19
 - [i386] x86/asm/32: Fix ANNOTATE_UNRET_SAFE use on 32-bit (fixes FTBFS)
 .
   [ Ben Hutchings ]
   * [riscv64] Disable COMPAT (fixes FTBFS)
   * linux-kbuild: Add check-local-export script (Closes: #1014633)
   * [x86,arm64,armhf] Add rtla package for Real-Time Linux Analysis tools
 .
   [ Uwe Kleine-König ]
   * Enable IOSM modem driver as a module.
 .
   [ Diederik de Haas ]
   * [arm64] drivers/crypto: Enable CRYPTO_DEV_ROCKCHIP as module
 .
   [ Salvatore Bonaccorso ]
   * [rt] Update to 5.19-rc8-rt9
 .
   [ Vincent Blut ]
   * [amd64] crypto: Enable CRYPTO_NHPOLY1305_SSE2 and CRYPTO_NHPOLY1305_AVX2
 as modules (Closes: #1013870)
 .
 linux (5.19~rc6-1~exp1) experimental; urgency=medium
 .
   * New upstream release candidate
 .
   [ Ben Hutchings ]
   * [mips64el/mips64r2el] Fix package description
   * [x86] Add mitigations for RETbleed on AMD/Hygon (CVE-2022-29900) and
 Intel (CVE-2022-29901) processors:
 - x86/kvm/vmx: Make noinstr clean
 - x86/cpufeatures: Move RETPOLINE flags to word 11
 - x86/retpoline: Cleanup some #ifdefery
 - 

Bug#1016546: rust-vergen inserts build timestamps

[Geert Stappers]

Package: rust-vergen
Version: 3.0.4-2
Severity: serious
Justify: fails to build reproducible
Tags: +patch

- Forwarded message from Maxime Devos  -

Date: Tue, 2 Aug 2022 19:18:46 +0200
From: Maxime Devos 
To: debian-r...@lists.debian.org
Subject: rust-vergen is irreproducible and causes irreproducibility
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 
Thunderbird/91.11.0

Hi,

In Guix, I've noticed that rust-vergen embeds build timestamps. There is also
a work-around available: .

Greetings,
Maxime.


pub EdDSA 256/191725EE 2020-10-14 Maxime Devos 
sub  ECDH 256/52A5D546 2020-10-14

- End forwarded message -

Groeten
Geert Stappers
-- 
Silence is hard to parse

Bug#1016448: marked as done (undertow: CVE-2022-1319 CVE-2021-3629)

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2022 19:46:35 +0200
with message-id <422cc868717105b4f7c2dfbdab16c724d0e64731.ca...@debian.org>
and subject line Re: undertow: CVE-2022-1319 CVE-2021-3629
has caused the Debian Bug report #1016448,
regarding undertow: CVE-2022-1319 CVE-2021-3629
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.)


-- 
1016448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016448
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: undertow
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for undertow.

CVE-2022-1319[0]:
https://bugzilla.redhat.com/show_bug.cgi?id=2073890


CVE-2021-3629[1]:
| A flaw was found in Undertow. A potential security issue in flow
| control handling by the browser over http/2 may potentially cause
| overhead or a denial of service in the server. The highest threat from
| this vulnerability is availability. This flaw affects Undertow
| versions prior to 2.0.40.Final and prior to 2.2.11.Final.

https://bugzilla.redhat.com/show_bug.cgi?id=1977362

Make sure to also address followup tracked as CVE-2022-1259:
https://bugzilla.redhat.com/show_bug.cgi?id=2072339


If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-1319
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1319
[1] https://security-tracker.debian.org/tracker/CVE-2021-3629
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3629

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
according to Red Hat CVE-2021-3629 was fixed in version 2.2.11. The first
fixing version in Debian was 2.2.12. No further details are available

See https://bugzilla.redhat.com/show_bug.cgi?id=1977362


CVE-2022-1319 was fixed in 2.2.17

See https://access.redhat.com/errata/RHSA-2022:4918

and the original Red Hat bug report

https://bugzilla.redhat.com/show_bug.cgi?id=2073890

No further details are available



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

Bug#1010355: marked as done (unzip: CVE-2022-0529 CVE-2022-0530)

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2022 17:22:16 +
with message-id 
and subject line Bug#1010355: fixed in unzip 6.0-27
has caused the Debian Bug report #1010355,
regarding unzip: CVE-2022-0529 CVE-2022-0530
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.)


-- 
1010355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010355
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: unzip
Version: 6.0-21+deb9u2
Severity: serious
Tags: security upstream patch
X-Debbugs-Cc: Debian Security Team 

Fixed: 6.0-26

Hello,

details are at https://security-tracker.debian.org/tracker/CVE-2022-0530

stretch and buster segfault:

  $ unzip testcase-0530 
  Archive:  testcase-0530
  warning [testcase-0530]:  16 extra bytes at beginning or within zipfile
(attempting to process anyway)
  error [testcase-0530]:  reported length of central directory is
-16 bytes too long (Atari STZip zipfile?  J.H.Holm ZIPSPLIT 1.1
zipfile?).  Compensating...
  error:  zipfile probably corrupt (segmentation violation)

bullseye errors out without valgrind issues reported:

  $ unzip testcase-0530
  Archive:  testcase-0530
  warning [testcase-0530]:  16 extra bytes at beginning or within zipfile
(attempting to process anyway)
  error [testcase-0530]:  reported length of central directory is
-16 bytes too long (Atari STZip zipfile?  J.H.Holm ZIPSPLIT 1.1
zipfile?).  Compensating...
  
mp/zip-unzip-0/7/source/workdir/��6a9f01ad36a4ac3b68815bf6f83b3ff_inpu㉴�瑥:
  mismatching "local" filename 
(mp/zip-unzip-0/7/source/workdir/��6a9f01ad36a4ac3b6881PK^G^HQ�V�^Q),
   continuing with "central" filename version
 skipping: 
mp/zip-unzip-0/7/source/workdir/��6a9f01ad36a4ac3b68815bf6f83b3ff_inpu㉴�瑥
  unable to get password

The main issue here seems to be at utf8_to_local_string, defined in
process.c:2606, which doesn't check the result of utf8_to_wide_string
for a NULL value.

I'm attaching a proposed patch that adds the missing error handling.


Enrico


-- System Information:
Debian Release: 11.3
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages unzip depends on:
ii  libbz2-1.0  1.0.8-4
ii  libc6   2.31-13+deb11u3

unzip recommends no packages.

Versions of packages unzip suggests:
ii  zip  3.0-12

-- no debconf information
diff --git a/fileio.c b/fileio.c
index 6290824..77e4b5f 100644
--- a/fileio.c
+++ b/fileio.c
@@ -2361,6 +2361,9 @@ int do_string(__G__ length, option)   /* return PK-type 
error code */
   /* convert UTF-8 to local character set */
   fn = utf8_to_local_string(G.unipath_filename,
 G.unicode_escape_all);
+  if (fn == NULL)
+return PK_ERR;
+
   /* make sure filename is short enough */
   if (strlen(fn) >= FILNAMSIZ) {
 fn[FILNAMSIZ - 1] = '\0';
diff --git a/process.c b/process.c
index d2a846e..715bc0f 100644
--- a/process.c
+++ b/process.c
@@ -2605,6 +2605,8 @@ char *utf8_to_local_string(utf8_string, escape_all)
   int escape_all;
 {
   zwchar *wide = utf8_to_wide_string(utf8_string);
+  if (wide == NULL)
+return NULL;
   char *loc = wide_to_local_string(wide, escape_all);
   free(wide);
   return loc;
--- End Message ---
--- Begin Message ---
Source: unzip
Source-Version: 6.0-27
Done: Santiago Vila 

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

Debian distribution maintenance software
pp.
Santiago Vila  (supplier of updated unzip 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: Tue, 02 Aug 2022 19:05:00 +0200
Source: unzip
Architecture: source
Version: 6.0-27
Distribution: unstable

Bug#1016090: marked as done (python-django breaks lots of autopkgtests)

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2022 17:07:53 +
with message-id 
and subject line Bug#1016090: fixed in python-django 3:3.2.14-1
has caused the Debian Bug report #1016090,
regarding python-django breaks lots of autopkgtests
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.)


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

Source: python-django
Control: found -1 python-django/2:4.0.6-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks
Control: affects -1 django-mailman3 django-invitations
Control: affects -1 django-oauth-toolkit django-tables
Control: affects -1 djangorestframework-filters factory-boy
Control: affects -1 python-django-braces python-django-celery-results
Control: affects -1 python-django-dbconn-retry python-django-extensions
Control: affects -1 python-django-extra-views
Control: affects -1 python-django-rest-framework-guardian

Dear maintainer(s),

With a recent upload of python-django the autopkgtest of 
django-mailman3, django-invitations, django-oauth-toolkit, 
django-tables, djangorestframework-filters, factory-boy, 
python-django-braces, python-django-celery-results, 
python-django-dbconn-retry, python-django-extensions, 
python-django-extra-views and python-django-rest-framework-guardian fail 
in testing when that autopkgtest is run with the binary packages of 
python-django from unstable. It passes when run with only packages from 
testing.


I note that the changelog has this:
"This security release mitigates the issue, but we have identified 
improvements to the Database API methods related to date extract and 
truncate that would be beneficial to add to Django 4.1 before it's final 
release. This will impact 3rd party database backends using Django 4.1 
release candidate 1 or newer, until they are able to update to the API 
changes. We apologize for the inconvenience."


I guess that means that these breakages might be intentional, but even 
if all this is to be expected, it would be good to add a *versioned* 
Breaks to python-django3 for all the packages that it really breaks (not 
just the autopkgtest).


Currently this regression is blocking the migration of python-django to 
testing [1].


Paul


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-django
Source-Version: 3:3.2.14-1
Done: Chris Lamb 

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated python-django 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: Tue, 02 Aug 2022 09:02:41 -0700
Source: python-django
Built-For-Profiles: nocheck
Architecture: source
Version: 3:3.2.14-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Chris Lamb 
Closes: 1016090
Changes:
 python-django (3:3.2.14-1) unstable; urgency=medium
 .
   * Revert Debian unstable to 3.2.x LTS release stream, bumping epoch.
 (Closes: #1016090)
   * Refresh patches.
   * Bump Standards-Version to 4.6.1.
Checksums-Sha1:
 d5589df7841a3480c3bc3bda8b0ffe2669cd3842 2807 python-django_3.2.14-1.dsc
 11b667ad90d5e9542a51791e5a895543567a1428 9814965 
python-django_3.2.14.orig.tar.gz
 c7c879f0d76174124b13860d3b8e1d77ad05ba5b 36316 
python-django_3.2.14-1.debian.tar.xz
 3d04288b29e1183307cba68a37e0ad0c59d7dc96 8107 
python-django_3.2.14-1_amd64.buildinfo
Checksums-Sha256:
 024f0e07e655bf285854efa3f43b6a058e291a443e3febbfecbed026c3dce218 2807 
python-django_3.2.14-1.dsc
 677182ba8b5b285a4e072f3ac17ceee6aff1b5ce77fd173cc5b6a2d3dc022fcf 9814965 
python-django_3.2.14.orig.tar.gz
 d1f5292ffc0fa7d33c790c9a7cc7c147eeb3fc4db5c489526c82d70a3b0c6ba9 36316 
python-django_3.2.14-1.debian.tar.xz
 2fc6847c72916a89ad19e5f885671514a7d984fa7a2913fc1ea4967f68ff2fb6 8107 
python-django_3.2.14-1_amd64.buildinfo
Files:
 58b3d62f16eadeee200e29d46d87a269 2807 python optional 
python-django_3.2.14-1.dsc
 

Bug#1016466: ImportError: /usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so.3.10.3: undefined symbol

[Jan van Gils]

Good day,

I am new to the Debian bug system so maybe I am wrong regarding my next remark.

This bug that I filed causes 'GNURadio unable to start' and is now depending on 
a libspdlog1 bug 1015742
Looking at that bug it seems it isn't possible to reproduce after a distro 
reinstall.

I guess now this GNURadio bug will also not be addressed, please change the 
status back to grave and have another look.

Bug#1013929: src:goffice: FTBFS on mips64el

[Ludovic Rousseau]

Le 02/08/2022 à 11:27, Dmitry Smirnov a écrit :

Hi Ludovic,

On Sunday, 31 July 2022 12:36:04 AM AEST Ludovic Rousseau wrote:

I am the Debian maintainer of the package grisbi that depends on
libgoffice-0.10-10

I see no update on this bug since 3 weeks.

It looks like the fix is proposed upstream at
https://gitlab.gnome.org/GNOME/goffice/-/issues/59#note_1495045


Sorry, I'm being very slow lately...

I've applied the upstream patch but unfortunately it did not fix the
problem...


I think we now have a *different* issue.
The initial build failure 
https://buildd.debian.org/status/fetch.php?pkg=goffice=mips64el=0.10.52-2=1656999642=0
 was during execution of dh_auto_build command:

/usr/bin/ld: .libs/goffice-0.10-scan.o: in function `get_object_types':
./docs/reference/goffice-0.10-scan.c:207: undefined reference to 
`go_complexl_get_type'
/usr/bin/ld: ./docs/reference/goffice-0.10-scan.c:207: undefined reference to 
`go_complexl_get_type'
collect2: error: ld returned 1 exit status
2022-07-05 05:40:30,271:scangobj.py:execute_command:1289:WARNING:Linking scanner failed: 1, 
command: /bin/bash ../../libtool --tag=CC --mode=link mips64el-linux-gnuabi64-gcc 
-lgobject-2.0 -lglib-2.0 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -g -Wall -Werror=init-self 
-Werror=missing-include-dirs -Wsign-compare -Werror=pointer-arith -Wchar-subscripts 
-Wwrite-strings -Wdeclaration-after-statement -Wnested-externs -Wmissing-noreturn 
-Werror=missing-prototypes -Werror=implicit-function-declaration -Wmissing-declarations 
-Wno-pointer-sign -Werror=format-security -Wstrict-prototypes -Wno-error=format-nonliteral 
-Wl,-z,relro -Wl,-z,now -Wl,-z,defs -Wl,-O1 -Wl,--as-needed -L/usr/X11R6/lib 
goffice-0.10-scan.lo ../../goffice/libgoffice-0.10.la -Wl,--export-dynamic -lgmodule-2.0 
-pthread -lgsf-1 -lrsvg-2 -lm -lxslt -lxml2 -lgtk-3 -lgdk-3 -lpangocairo-1.0 -lpango-1.0 
-lharfbuzz -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 
-lglib-2.0 -Wl,-z,relro -Wl,-z,now -Wl,-z,defs -Wl,-O1 -Wl,--as-needed -L/usr/X11R6/lib -o 
goffice-0.10-scan
make[3]: *** [Makefile:695: scan-build.stamp] Error 1
make[3]: Leaving directory '/<>/docs/reference'
make[2]: *** [Makefile:438: all-recursive] Error 1
make[2]: Leaving directory '/<>/docs'
make[1]: *** [Makefile:552: all-recursive] Error 1
make[1]: Leaving directory '/<>'
dh_auto_build: error: make -j4 returned exit code 2
make: *** [debian/rules:70: binary-arch] Error 25
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2


With the new upstream patch the build failure is during ecxecution of 
dpkg-gensymbols command:

dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libgoffice-0.10-10/DEBIAN/symbols doesn't 
match completely debian/libgoffice-0.10-10.symbols
--- debian/libgoffice-0.10-10.symbols (libgoffice-0.10-10_0.10.52-3_mips64el)
+++ dpkg-gensymbolsz0mJDF   2022-08-02 08:51:19.169391884 +
@@ -60,22 +60,22 @@
  go__VOID__INT_BOOLEAN_BOOLEAN_BOOLEAN@Base 0.9.0
  go_accumulator_add@Base 0.9.0
  go_accumulator_add_quad@Base 0.9.1
- go_accumulator_add_quadl@Base 0.9.1
- go_accumulator_addl@Base 0.9.0
+#MISSING: 0.10.52-3# go_accumulator_add_quadl@Base 0.9.1
+#MISSING: 0.10.52-3# go_accumulator_addl@Base 0.9.0
  go_accumulator_clear@Base 0.9.0
- go_accumulator_clearl@Base 0.9.0
+#MISSING: 0.10.52-3# go_accumulator_clearl@Base 0.9.0
[...]

Some symbols, ending with "l", were previously defined but are no more present.

From the header file 
https://gitlab.gnome.org/GNOME/goffice/-/blob/master/goffice/math/go-accumulator.h#L29
 we see that the symbol go_accumulator_addl() is defined only if 
GOFFICE_WITH_LONG_DOUBLE is defined.

But in debian/rules we still have "--without-long-double" option for mips64el. 
I think that is the source of the new problem.

Have you tried to *revert* 
https://salsa.debian.org/debian/goffice/-/commit/3cd973d85f5b6d337100270e068f09fd30d8cea5
 and keep only the new upstream patch?


Hope this helps.

--
Dr. Ludovic Rousseau

Bug#1016090: python-django breaks lots of autopkgtests

[Chris Lamb]

Raphael Hertzog wrote:

> As such, as much as I hate it, I think than only (a) is realistic.

Yeah. :/   Okay, I'll upload 3.3.14 shortly.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-

Bug#1013890: closed by Jerome BENOIT (reply to calcu...@rezozer.net) (sagemath: ABI breakage without SONAME bump)

[Paul Gevers]

Hi,

On 02-08-2022 14:30, Debian Bug Tracking System wrote:

the gmp-ecm migration troubles appear to have been fixed.
So I am closing the report.


Hmmm, and how about derivatives, or people that build local packages 
linked to gmp-ecm? There's a reason why SONAME is tracked and why in 
Debian we want the library package to match the SONAME.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

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

[Debian Bug Tracking System]

Your message dated Tue, 2 Aug 2022 16:52:30 +0300
with message-id <4e812d86-8555-4d65-80de-8851ba0e2...@gmail.com>
and subject line Re: Bug#1016314: asn1c: FTBFS: dh_auto_test: error: make -j8 
check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
has caused the Debian Bug report #1016314,
regarding asn1c: 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.)


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

Hi,

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


Relevant part (hopefully):
> PASS: check-GeneralizedTime
> check-OCTET_STRING: OCTET_STRING.c:1009: OCTET_STRING__convert_entrefs: 
> Assertion `val > 0' failed.
> /bin/bash: line 6: 200614 Aborted ${dir}$tst
> FAIL: check-OCTET_STRING
> []: size=0, expect=0, got=0
> []: size=1, expect=1, got=1
> [a]: size=1, expect=1, got=1
> [ab]: size=2, expect=2, got=2
> [abc]: size=3, expect=3, got=3
> [aßcd]: size=5, expect=4, got=4
> [a?c]: size=7, expect=3, got=3
> [лев]: size=6, expect=3, got=3
> [a?]: size=2, expect=-1, got=-1
> [?]: size=1, expect=-2, got=-2
> [?]: size=1, expect=-2, got=-2
> [?]: size=5, expect=-2, got=-2
> [?c]: size=2, expect=-3, got=-3
> [ac]: size=6, expect=-3, got=-3
> [a?c]: size=7, expect=-4, got=-4
> [???]: size=7, expect=-4, got=-4
> []: size=0, expect=-5, got=-5
> Now wait a bit...
> 100 cycles in 0.214ms
> PASS: check-UTF8String
> [...]
> 
> 1 of 12 tests failed
> Please report to v...@lionet.info
> 
> make[4]: *** [Makefile:586: check-TESTS] Error 1
> make[4]: Leaving directory '/<>/skeletons/tests'
> make[3]: *** [Makefile:712: check-am] Error 2
> make[3]: Leaving directory '/<>/skeletons/tests'
> make[2]: *** [Makefile:1084: check-recursive] Error 1
> make[2]: Leaving directory '/<>/skeletons'
> make[1]: *** [Makefile:472: check-recursive] Error 1
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 
> returned exit code 2


The full build log is available from:
http://qa-logs.debian.net/2022/07/28/asn1c_0.9.28+dfsg-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220728;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220728=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Hello,

Thank you for the report.
This bug has been fixed in 0.9.28+dfsg-4 and 0.9.28+dfsg-5 which are already 
uploaded to unstable.
See also the bug 1012896.

---
Best regards,
Evgeny Seliverstov

> On Jul 29, 2022, at 21:18, Lucas Nussbaum  wrote:
> 
> Source: asn1c
> Version: 0.9.28+dfsg-3
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20220728 ftbfs-bookworm
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> 
> Relevant part (hopefully):
>> PASS: check-GeneralizedTime
>> check-OCTET_STRING: OCTET_STRING.c:1009: OCTET_STRING__convert_entrefs: 
>> Assertion `val > 0' failed.
>> /bin/bash: line 6: 200614 Aborted ${dir}$tst
>> FAIL: check-OCTET_STRING
>> []: size=0, expect=0, got=0
>> []: size=1, expect=1, got=1
>> [a]: size=1, expect=1, got=1
>> [ab]: size=2, expect=2, got=2
>> [abc]: size=3, expect=3, got=3
>> [aßcd]: size=5, expect=4, got=4
>> [a?c]: size=7, expect=3, got=3
>> [лев]: size=6, expect=3, got=3
>> [a?]: size=2, expect=-1, got=-1
>> [?]: size=1, expect=-2, got=-2
>> [?]: size=1, expect=-2, got=-2
>> [?]: size=5, expect=-2, got=-2
>> [?c]: size=2, expect=-3, got=-3
>> [ac]: size=6, expect=-3, got=-3
>> [a?c]: size=7, expect=-4, got=-4
>> [???]: 

Processed: Re: Bug#1013578: golang-github-prometheus-exporter-toolkit: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.com/prometheus/exporter-toolkit/web github.com/prometheu

[Debian Bug Tracking System]

Processing control commands:

> tag -1 unreproducible moreinfo
Bug #1013578 [src:golang-github-prometheus-exporter-toolkit] 
golang-github-prometheus-exporter-toolkit: FTBFS: dh_auto_test: error: cd 
_build && go test -vet=off -v -p 8 github.com/prometheus/exporter-toolkit/web 
github.com/prometheus/exporter-toolkit/web/kingpinflag returned exit code 1
Added tag(s) unreproducible and moreinfo.

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

Bug#1013578: golang-github-prometheus-exporter-toolkit: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.com/prometheus/exporter-toolkit/web github.com/prometheus/exporter-tool

[Santiago Vila]

Hi.

I have not tested in sid, but these are my statistics:

In bookworm, it FTBFS for me:

100% of the time on systems with 1 CPU.
 80% of the time on systems with 2 CPUs.

In bullseye, it FTBFS for me:

100% of the time on systems with 1 CPU
  0% of the time on systems with 2 CPUs.

I'm currently using Hetzner machines with 8 GB of RAM and either 1 or 2 
CPUs. To emulate a single CPU on a machine with 2 CPUs I do this in 
/etc/default/grub:


GRUB_CMDLINE_LINUX="nr_cpus=1"

I can give you access to a machine where this happens, please contact me 
privately for details.


Thanks.

Bug#1016222: marked as done (sahara: FTBFS: TypeError: create..Validator.__init__() got an unexpected keyword argument 'types')

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2022 13:04:46 +
with message-id 
and subject line Bug#1016222: fixed in sahara 1:16.0.0-2
has caused the Debian Bug report #1016222,
regarding sahara: FTBFS: TypeError: create..Validator.__init__() got an 
unexpected keyword argument 'types'
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.)


-- 
1016222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016222
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sahara
Version: 1:16.0.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220728 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> =
> Failures during discovery
> =
> --- import errors ---
> Failed to import test module: sahara.tests.unit.db.templates.test_delete
> Traceback (most recent call last):
>   File "/usr/lib/python3.10/unittest/loader.py", line 436, in _find_test_path
> module = self._get_module_from_name(name)
>   File "/usr/lib/python3.10/unittest/loader.py", line 377, in 
> _get_module_from_name
> __import__(name)
>   File "/<>/sahara/tests/unit/db/templates/test_delete.py", line 
> 18, in 
> from sahara.db.templates import api as template_api
>   File "/<>/sahara/db/templates/api.py", line 47, in 
> ng_validator = api_validator.ApiValidator(ngt.NODE_GROUP_TEMPLATE_SCHEMA)
>   File "/<>/sahara/utils/api_validator.py", line 176, in __init__
> super(ApiValidator, self).__init__(
> TypeError: create..Validator.__init__() got an unexpected keyword 
> argument 'types'
> 
> Failed to import test module: sahara.tests.unit.db.templates.test_update
> Traceback (most recent call last):
>   File "/usr/lib/python3.10/unittest/loader.py", line 436, in _find_test_path
> module = self._get_module_from_name(name)
>   File "/usr/lib/python3.10/unittest/loader.py", line 377, in 
> _get_module_from_name
> __import__(name)
>   File "/<>/sahara/tests/unit/db/templates/test_update.py", line 
> 24, in 
> from sahara.db.templates import api as template_api
>   File "/<>/sahara/db/templates/api.py", line 47, in 
> ng_validator = api_validator.ApiValidator(ngt.NODE_GROUP_TEMPLATE_SCHEMA)
>   File "/<>/sahara/utils/api_validator.py", line 176, in __init__
> super(ApiValidator, self).__init__(
> TypeError: create..Validator.__init__() got an unexpected keyword 
> argument 'types'
> 
> 
> The above traceback was encountered during test discovery which imports all 
> the found test modules in the specified test_path.
> 
> --
> Ran 0 tests in 4.217s
> 
> OK
> + stestr slowest
> make[1]: *** [debian/rules:41: override_dh_install] Error 3


The full build log is available from:
http://qa-logs.debian.net/2022/07/28/sahara_16.0.0-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220728;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220728=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: sahara
Source-Version: 1:16.0.0-2
Done: Thomas Goirand 

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated sahara 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

Bug#1016222: marked as pending in sahara

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1016222 in sahara reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/openstack-team/services/sahara/-/commit/c8632de4edfa30becac3a1d5d6d5d0d9b760c77e


* Get Ubuntu patches fixing compat with jsonschema 4.x (Closes: #1016222):
- d/p/adapt-to-new-jsonschema-versions.patch: This fixes the majority of
  the new jsonschema unit test failures.
- d/p/skip-test.patch: Skip the last jsonschema failure until it is fixed
  upstream.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1016222

Processed: Bug#1016222 marked as pending in sahara

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1016222 [src:sahara] sahara: FTBFS: TypeError: 
create..Validator.__init__() got an unexpected keyword argument 'types'
Added tag(s) pending.

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

Bug#1013890: marked as done (ABI breakage without SONAME bump)

[Debian Bug Tracking System]

Your message dated Tue, 2 Aug 2022 14:11:31 +0200
with message-id 
and subject line sagemath: ABI breakage without SONAME bump
has caused the Debian Bug report #1013890,
regarding ABI breakage without SONAME bump
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.)


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

Source: gmp-ecm, sagemath
Control: found -1 gmp-ecm/7.0.5+ds-1
Control: found -1 sagemath/9.5-4
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of gmp-ecm the autopkgtest of sagemath fails in 
testing when that autopkgtest is run with the binary packages of gmp-ecm 
from unstable. It passes when run with only packages from testing. In 
tabular form:


   passfail
gmp-ecmfrom testing7.0.5+ds-1
sagemath   from testing9.5-4
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of gmp-ecm to 
testing [1]. Due to the nature of this issue, I filed this bug report 
against both packages. Can you please investigate the situation and 
reassign the bug to the right package?


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=gmp-ecm

https://ci.debian.net/data/autopkgtest/testing/amd64/s/sagemath/23080949/log.gz

sage -t --random-seed=254306892368924504610037307929798433555 
sage/src/sage/calculus/calculus.py

**
File "sage/src/sage/calculus/calculus.py", line 1642, in 
sage.calculus.calculus.laplace

Failed example:
a, cond
Expected:
(-oo, True)
Got:
(0, True)
**
1 item had failures:
   1 of  46 in sage.calculus.calculus.laplace
[451 tests, 1 failure, 11.81 s]

sage -t --random-seed=254306892368924504610037307929798433555 
sage/src/sage/combinat/cluster_algebra_quiver/interact.py

**
File "sage/src/sage/combinat/cluster_algebra_quiver/interact.py", line 
29, in sage.combinat.cluster_algebra_quiver.interact.cluster_interact

Failed example:
S.interact()   # indirect doctest
Expected:
VBox(children=...
Got:
doctest:warning
  File "/usr/bin/sage-runtests", line 155, in 
err = DC.run()
  File "/usr/lib/python3/dist-packages/sage/doctest/control.py", 
line 1261, in run

self.run_doctests()
  File "/usr/lib/python3/dist-packages/sage/doctest/control.py", 
line 962, in run_doctests

self.dispatcher.dispatch()
  File "/usr/lib/python3/dist-packages/sage/doctest/forker.py", 
line 2004, in dispatch

self.parallel_dispatch()
  File "/usr/lib/python3/dist-packages/sage/doctest/forker.py", 
line 1899, in parallel_dispatch

w.start()  # This might take some time
  File "/usr/lib/python3/dist-packages/sage/doctest/forker.py", 
line 2173, in start

super(DocTestWorker, self).start()
  File "/usr/lib/python3.10/multiprocessing/process.py", line 121, 
in start

self._popen = self._Popen(self)
  File "/usr/lib/python3.10/multiprocessing/context.py", line 224, 
in _Popen

return _default_context.get_context().Process._Popen(process_obj)
  File "/usr/lib/python3.10/multiprocessing/context.py", line 277, 
in _Popen

return Popen(process_obj)
  File "/usr/lib/python3.10/multiprocessing/popen_fork.py", line 
19, in __init__

self._launch(process_obj)
  File "/usr/lib/python3.10/multiprocessing/popen_fork.py", line 
71, in _launch

code = process_obj._bootstrap(parent_sentinel=child_r)
  File "/usr/lib/python3.10/multiprocessing/process.py", line 315, 
in _bootstrap

self.run()
  File "/usr/lib/python3/dist-packages/sage/doctest/forker.py", 
line 2145, in run

task(self.options, self.outtmpfile, msgpipe, self.result_queue)
  File "/usr/lib/python3/dist-packages/sage/doctest/forker.py", 
line 2475, in __call__

doctests, extras = self._run(runner, options, results)
  File "/usr/lib/python3/dist-packages/sage/doctest/forker.py", 
line 2527, in _run

result = runner.run(test)
  File 

Bug#999310: marked as done (libxml-dumper-perl: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2022 12:05:11 +
with message-id 
and subject line Bug#999310: fixed in libxml-dumper-perl 0.81-1.4
has caused the Debian Bug report #999310,
regarding libxml-dumper-perl: missing required debian/rules targets build-arch 
and/or build-indep
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.)


-- 
999310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libxml-dumper-perl
Version: 0.81-1.3
Severity: important
Justification: Debian Policy section 4.9
Tags: bookworm sid
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules

Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00052.html .
The severity of this bug will be changed to 'serious' after a month.

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: libxml-dumper-perl
Source-Version: 0.81-1.4
Done: Håvard F. Aasen 

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

Debian distribution maintenance software
pp.
Håvard F. Aasen  (supplier of updated 
libxml-dumper-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 28 Jul 2022 13:23:26 CEST
Source: libxml-dumper-perl
Binary: 
Architecture: source
Version: 0.81-1.4
Distribution: unstable
Urgency: medium
Maintainer: Florian Hinzmann 
Changed-By: Håvard F. Aasen 
Description: 
Closes: 999310
Changes:
 libxml-dumper-perl (0.81-1.4) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Include missing build target. (Closes: #999310)
  - Using dh sequencer.
  - Add libxml-parser-perl as build dependency, for testsuite.
  - Add runtime dependency on ${misc:Depends}.
   * d/watch
 - Bump to version 4.
 - Update URI.
   * Remove superfluous dot '.' in package description
   * d/copyright: Change to UTF-8 encoding.
Checksums-Sha256: 
 78a31ea7efea1a57ad10ba8445c3ca901ff48e5149322fd8cdd9d19843afdf4c 1912 
libxml-dumper-perl_0.81-1.4.dsc
 98636625a93139df63b18a6b0d97197677bb302a98c9c7fee8d1aafe9419017d 2845 
libxml-dumper-perl_0.81-1.4.diff.gz
 a183bd1f93b1b0d1f85e329815d603cc473dcebbd014b1be1194b4a976680993 6868 
libxml-dumper-perl_0.81-1.4_sourceonly.buildinfo
Checksums-Sha1: 
 f8122463ba34fedfe78df5706589b6bcdd22c0d3 1912 libxml-dumper-perl_0.81-1.4.dsc
 3d530a01b1bc930a63e9727ff7d7ec61f9c5e43a 2845 
libxml-dumper-perl_0.81-1.4.diff.gz
 c68bb6d330c4eb7e47839841e440aa1a38a36ca8 6868 
libxml-dumper-perl_0.81-1.4_sourceonly.buildinfo
Files: 
 d3312336ff4abc9516917b567be46206 1912 perl optional 
libxml-dumper-perl_0.81-1.4.dsc
 2eac1d3e3add64850206ebcc2b385a35 2845 perl optional 
libxml-dumper-perl_0.81-1.4.diff.gz
 40151038fc360cbd520cb5bc2c87f327 6868 - - 
libxml-dumper-perl_0.81-1.4_sourceonly.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmLicbJfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgYDuw//eozLXtBtaVPjq8rlS2C8HOJKo9MyY+FeNA2I+kcGo1xUUzNPKuVCobv4
a8PJd0rEpcUQrU7ah9eZII/od9lwj87n+yzvFooLflTwqMJT7lZ30EcW4jCsRcJB
g4ijxQmwLWzeAxVPa5WL8vZnqvQay/MnOS+kheL4fmT6We++U14lh72DC70APtpy
3fldX1qDZHe+g48Ov5pDNS1ripwZZf9BAFk2L8t7tz/6ZijITr2D9FG10EC3rrA6
5HclGNME5tUb3SGUbOtn+7EwDWhsGYcYeJDLayjD6/Y41MUC+gX46tS6OSph2JYP
pdDp+NT3bUZ4MSfLwXlo+jIOXeDgH9hwETaOaCPt8GVWfWQM59YKjuiCZm32KcYo
uEAUl2a3tyA+04nqFurvCQC1B43zoyHlE6/K52unq22va75lBCBGGuUqVtECtJ2R
V3lQ2iyGa8n2cKLZjnpPX3f5bYUrxLaA2XVCRMhMuhXB8Bmcby0ThUqvPhgpBTpH

Bug#981009: charybdis abandoned upstream, do not ship in bullseye

[Chris Hofstaedtler]

* Antoine Beaupre :
> After a somewhat long period of uncertainty, Charybdis has been
> finally abandoned upstream. The official git repository here:
> 
> https://github.com/charybdis-ircd/charybdis
> 
> .. is marked as "archived by the owner [and] read-only".

Is it time to file an RM bug, given that its probably going to be
solanum?

Chris

Processed: python-h5netcdf: CI tests fail with h5py 3.7.0

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/h5netcdf/h5netcdf/issues/179
Bug #1016525 [src:python-h5netcdf] python-h5netcdf: CI tests fail with h5py 
3.7.0
Set Bug forwarded-to-address to 
'https://github.com/h5netcdf/h5netcdf/issues/179'.

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

Bug#1016525: python-h5netcdf: CI tests fail with h5py 3.7.0

[Drew Parsons]

Source: python-h5netcdf
Version: 1.0.1-1
Severity: serious
Tags: patch
Justification: debci
Control: forwarded -1 https://github.com/h5netcdf/h5netcdf/issues/179

h5netcdf tests fail with h5py 3.7.0, which was recently uploaded to
unstable.

The problem is fixed upstream, the fix is available in the new release
h5netcdf 1.0.2



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

Kernel: Linux 5.18.0-3-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1016090: python-django breaks lots of autopkgtests

[Raphael Hertzog]

Hi,

On Mon, 01 Aug 2022, Chris Lamb wrote:
> Regardless of that though, I think we have two options:
> 
> a) Revert back to the 3.2.14 LTS version in Debian unstable.
> 
> b) Wait for the 4.x stream to become designated LTS. I believe this
>should happen with version 4.2, due for release in about 6 or 7
>months:

The Django and Debian releases are not well aligned. The 4.2 release
is planned in April 2023 so a bit late given the freeze. If the number of
reverse dependencies was lower, it could argued to try to have some sort
of exceptions and offering extra work to help fix/migrate the reverse
dependencies.

But unfortunately I assume that most of the important reverse dependencies
track mainly the LTS releases and the upstream fixes for 4.x compatibility
will only materialize once Django 4.2 is released and we would have to
commit to too much work to be able to push Django 4.x (including 4.2~rc1
or similar) in bookworn.

As such, as much as I hate it, I think than only (a) is realistic.

Cheers,
-- 
  ⢀⣴⠾⠻⢶⣦⠀   Raphaël Hertzog 
  ⣾⠁⢠⠒⠀⣿⡁
  ⢿⡄⠘⠷⠚⠋The Debian Handbook: https://debian-handbook.info/get/
  ⠈⠳⣄   Debian Long Term Support: https://deb.li/LTS

Bug#1013929: src:goffice: FTBFS on mips64el

[Dmitry Smirnov]

Hi Ludovic,

On Sunday, 31 July 2022 12:36:04 AM AEST Ludovic Rousseau wrote:
> I am the Debian maintainer of the package grisbi that depends on
> libgoffice-0.10-10
> 
> I see no update on this bug since 3 weeks.
> 
> It looks like the fix is proposed upstream at
> https://gitlab.gnome.org/GNOME/goffice/-/issues/59#note_1495045

Sorry, I'm being very slow lately...

I've applied the upstream patch but unfortunately it did not fix the
problem...


> Dmitry, do you need help?

Yes please. I'm clueless what to do next. Thank you.

-- 
Best wishes,
 Dmitry Smirnov
 GPG key : 4096R/52B6BBD953968D1B

---

The entire notion of "a government of the people, by the people, and for
the people," while it makes nice feel-good political rhetoric, is a
logical impossibility. A ruling class cannot serve or represent those it
rules any more than a slave owner can serve or represent his slaves.
 -- Larken Rose, The Most Dangerous Superstition

---

The Face Mask Folly in Retrospect
https://swprs.org/the-face-mask-folly-in-retrospect/


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

Processed: reopening 1013929

[Debian Bug Tracking System]

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

> reopen 1013929
Bug #1013929 {Done: Dmitry Smirnov } [src:goffice] 
src:goffice: fails to migrate to testing for too long: FTBFS on mips64el
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions goffice/0.10.52-3.
> thanks
Stopping processing here.

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

Processed: Re: Bug#982459: mdadm examine corrupts host ext4

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:linux
Bug #982459 [mdadm] mdadm --examine in chroot without /proc,/dev,/sys mounted 
corrupts host's filesystem
Bug reassigned from package 'mdadm' to 'src:linux'.
No longer marked as found in versions mdadm/4.1-1.
Ignoring request to alter fixed versions of bug #982459 to the same values 
previously set

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

Bug#982459: mdadm examine corrupts host ext4

[Chris Hofstaedtler]

Control: reassign -1 src:linux

Dear Håkan,

thanks for reporting back and testing!

* Håkan T Johansson  [220801 19:31]:
> On Sun, 31 Jul 2022, Chris Hofstaedtler wrote:
> 
> > I can't see a difference that should matter from userspace.
> > 
> > I have stared a bit at the kernel code... there have been quite some
> > changes and fixes in this area. Which kernel version were you
> > running when testing this?
> > 
> > Could you retry on something >= 5.9? I.e. some version with patch
> >08fc1ab6d748ab1a690fd483f41e2938984ce353.
> 
> I believe that I was running 5.10 (bullseye).
> 
> It looks like 5.18 (from backports) does not show the issue!  (i.e. works)

Okay, I think we are now clearly in "this is not an mdadm bug per
se" territory (-> reassigning to src:linux).

[..]
>   This time I did get some dmesg BUG output as well (attached).
>   It does not seem to be the same backtrace on two occurances.
> 
>   I also noticed that the BUG: report in dmesg does not happen directly
>   when doing 'mdadm --examine --scan --config=partitions'.  It rather
>   occurs when some activity happens on the host filesystem, e.g.
>   a 'touch /root/a' command.
> 
> host:
>   linux-image-5.18.0-0.bpo.1-amd64  5.18.2-1~bpo11+1
> 
>   (did not re-install anything else, except upgraded zfs, also from
>   backports (since pure bullseye would not compile with 5.18))
> 
>   Does not exhibit the problem.
> 
> I have tried with both kernels several times, and it was repeatable that
> 5.10 got stuck while 5.18 does not show issues.

Its good that this now works in 5.18. However I'm not sure how we
should find the commit fixing this - in 5.14 lots of block layer
code was shuffled around/refactored.

If you have the time, maybe trying the various kernel versions
between 5.10 and 5.18 would be a good start. If they are not in
backports anymore, they should still be at
  http://snapshot.debian.org/package/linux/

> Reminder: to get the issue, /dev/ should not be mounted in the chroot.
> With /dev/ mounted, 5.10 also works.

I'll see if I can repro this on 5.10, but need to find a box first.

Best,
Chris

> [mån aug  1 15:53:08 2022] BUG: kernel NULL pointer dereference, address: 
> 0010
> [mån aug  1 15:53:08 2022] #PF: supervisor read access in kernel mode
> [mån aug  1 15:53:08 2022] #PF: error_code(0x) - not-present page
> [mån aug  1 15:53:08 2022] PGD 0 P4D 0 
> [mån aug  1 15:53:08 2022] Oops:  [#1] SMP PTI
> [mån aug  1 15:53:08 2022] CPU: 2 PID: 284256 Comm: cron Tainted: P   
> OE 5.10.0-16-amd64 #1 Debian 5.10.127-2
> [mån aug  1 15:53:08 2022] Hardware name: Dell Computer Corporation PowerEdge 
> 2850/0T7971, BIOS A04 09/22/2005
> [mån aug  1 15:53:08 2022] RIP: 
> 0010:__ext4_journal_get_write_access+0x29/0x120 [ext4]
> [mån aug  1 15:53:08 2022] Code: 00 0f 1f 44 00 00 41 57 41 56 41 89 f6 41 55 
> 41 54 49 89 d4 55 48 89 cd 53 48 83 ec 10 48 89 3c 24 e8 ab d7 bb e1 48 8b 45 
> 30 <4c> 8b 78 10 4d 85 ff 74 2f 49 8b 87 e0 00 00 00 49 8b 9f 88 03 00
> [mån aug  1 15:53:08 2022] RSP: 0018:ae27c059fd60 EFLAGS: 00010246
> [mån aug  1 15:53:08 2022] RAX:  RBX: 9d1b94505480 RCX: 
> 9d1bc52e5e38
> [mån aug  1 15:53:08 2022] RDX: 9d1bc13782d8 RSI: 0c14 RDI: 
> c096feb0
> [mån aug  1 15:53:08 2022] RBP: 9d1bc52e5e38 R08: 9d1be04d5230 R09: 
> 0001
> [mån aug  1 15:53:08 2022] R10: 9d1bc985f000 R11: 001d R12: 
> 9d1bc13782d8
> [mån aug  1 15:53:08 2022] R13: 9d1be04d5000 R14: 0c14 R15: 
> 9d1bc13782d8
> [mån aug  1 15:53:08 2022] FS:  7fed5ecb1840() 
> GS:9d1cd7c8() knlGS:
> [mån aug  1 15:53:08 2022] CS:  0010 DS:  ES:  CR0: 80050033
> [mån aug  1 15:53:08 2022] CR2: 0010 CR3: 0001a46d8000 CR4: 
> 06e0
> [mån aug  1 15:53:08 2022] Call Trace:
> [mån aug  1 15:53:08 2022]  ext4_orphan_del+0x23f/0x290 [ext4]
> [mån aug  1 15:53:08 2022]  ext4_evict_inode+0x31f/0x630 [ext4]
> [mån aug  1 15:53:08 2022]  evict+0xd1/0x1a0
> [mån aug  1 15:53:08 2022]  __dentry_kill+0xe4/0x180
> [mån aug  1 15:53:08 2022]  dput+0x149/0x2f0
> [mån aug  1 15:53:08 2022]  __fput+0xe4/0x240
> [mån aug  1 15:53:08 2022]  task_work_run+0x65/0xa0
> [mån aug  1 15:53:08 2022]  exit_to_user_mode_prepare+0x111/0x120
> [mån aug  1 15:53:08 2022]  syscall_exit_to_user_mode+0x28/0x140
> [mån aug  1 15:53:08 2022]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
> [mån aug  1 15:53:08 2022] RIP: 0033:0x7fed5eea2d77
> [mån aug  1 15:53:08 2022] Code: 44 00 00 48 8b 15 19 a1 0c 00 f7 d8 64 89 02 
> b8 ff ff ff ff eb bc 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 b8 03 00 00 00 0f 
> 05 <48> 3d 00 f0 ff ff 77 01 c3 48 8b 15 e9 a0 0c 00 f7 d8 64 89 02 b8
> [mån aug  1 15:53:08 2022] RSP: 002b:7ffd50452818 EFLAGS: 0202 
> ORIG_RAX: 0003
> [mån aug  1 15:53:08 2022] RAX:  RBX: 55dab4578910 RCX: 
> 7fed5eea2d77
> [mån 

Bug#1016512: multipath-tools: ships /usr/share/bug/multipath-tools-boot/script

[Chris Hofstaedtler]

* Andreas Beckmann :
> Are you installing that file manually instead of using dh_bugfiles -A ?

Obviously we did, because dh_bugfiles did not exist until October
2008. :-)

Switched to dh_bugfiles now, thanks.

Chris

Bug#1016512: marked as done (multipath-tools: ships /usr/share/bug/multipath-tools-boot/script)

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2022 08:49:31 +
with message-id 
and subject line Bug#1016512: fixed in multipath-tools 0.9.0-3
has caused the Debian Bug report #1016512,
regarding multipath-tools: ships /usr/share/bug/multipath-tools-boot/script
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.)


-- 
1016512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016512
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: multipath-tools
Version: 0.9.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

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

  Preparing to unpack .../multipath-tools-boot_0.9.0-2_all.deb ...
  Unpacking multipath-tools-boot (0.9.0-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/multipath-tools-boot_0.9.0-2_all.deb (--unpack):
   trying to overwrite '/usr/share/bug/multipath-tools-boot/script', which is 
also in package multipath-tools 0.9.0-2
  Errors were encountered while processing:
   /var/cache/apt/archives/multipath-tools-boot_0.9.0-2_all.deb

Are you installing that file manually instead of using dh_bugfiles -A ?


cheers,

Andreas


multipath-tools=0.9.0-2_multipath-tools-boot=0.9.0-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: multipath-tools
Source-Version: 0.9.0-3
Done: Chris Hofstaedtler 

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

Debian distribution maintenance software
pp.
Chris Hofstaedtler  (supplier of updated multipath-tools 
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: Tue, 02 Aug 2022 08:21:25 +
Source: multipath-tools
Architecture: source
Version: 0.9.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian DM Multipath Team 
Changed-By: Chris Hofstaedtler 
Closes: 1016512
Changes:
 multipath-tools (0.9.0-3) unstable; urgency=medium
 .
   * [baa940a] Install reportbug helper using dh_bugfiles (Closes: #1016512)
Checksums-Sha1:
 d81326d04d1aa60f14dbb11393fa8b2c82091f85 2576 multipath-tools_0.9.0-3.dsc
 d10c95e6bea6adf8e4650dce3945558364187d8d 28132 
multipath-tools_0.9.0-3.debian.tar.xz
 67a336f19024b7d7dc12d1e4760bcc3683b383f7 7522 
multipath-tools_0.9.0-3_source.buildinfo
Checksums-Sha256:
 5707b15f3ba590d8c6acc68a5ae1960547a425aecb87e40db8437c97da330a06 2576 
multipath-tools_0.9.0-3.dsc
 ebe39049701716d6dae4a69908782ec8e08756ade6e5c29282ccdeb7275d222e 28132 
multipath-tools_0.9.0-3.debian.tar.xz
 8432c0b5fc2699c7b023f175517fe120896387b99c2d4b7b44c599c7e09f59fd 7522 
multipath-tools_0.9.0-3_source.buildinfo
Files:
 ca4c9ffc7b7362aa269da2a7004d885b 2576 admin optional 
multipath-tools_0.9.0-3.dsc
 fdf23f41da3376a71b3f08d940bfeaa6 28132 admin optional 
multipath-tools_0.9.0-3.debian.tar.xz
 99d4cd55625ce21f44261bd5cf757f10 7522 admin optional 
multipath-tools_0.9.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmLo4WsACgkQXBPW25MF
LgOoDQ/+KPgqh3kS7/CynixqpDslxhQE75X9jy14pR9KFVrUBeg4rqlcSRhXRXRi
CXkMpBH/f1Mn0Q1zch2/5oQJGjxztDdY2K5hc0OLbvVnX2UVgFVRCROCoRLJ1+Pd
crbObZV2wD+7QwZfyc3KK1gMOWHShqHOocKXZ/V3Mv16lvtHuq8ojFvzuIn+TMfV
YKaRrHlop8hThNtkBTt4bokzQS45nipEU2/PsBgvdEoS9Yka16Kiyt2E4mi5q7VH
ZnQxkhgfEoPxYuQc/vAWt9o7wqeOyEvakJbJ4up2AjBoRPo0unxamOpjq5l4oof8
/B6K+0BFz1kwck8lLMhIgb72V0blxu3CZBkcYaigePNF8ztKD8RPUs1YN2mIcIRv
lkeycVvEgIynBTRwonb1Q0Lg40E9KXU2WYBJbnB/uAAgtl5zWN3m59YV9AHfDxNB
hWQBizNVpc9AIFxCT8iItlIiQAfYfVh+/5MyWkg2u7c60fcQGp2CEPrEQyD8Xj3T
NsqlTrxU7dP2JSD2YqAccLuSizyFBUlRBW75oxL5ml8DH5GEUQdd/Y4FGCkjzo9C
wbnR0nltDGn8soAg0dRYM2RJQZgdk5ub6XHiFwWoYsL4YarB+aIeuhIKedA4O33v
W0JeWQ4X+4GjmCDlhALtbe7f92D50z9BLaqMRPCd5byd59sTUlk=
=9klC
-END PGP SIGNATURE End Message ---

Processed: Re: Please update jupyter-notebook to 6.4.12

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #1015783 [jupyter-notebook] Please update jupyter-notebook to 6.4.12
Severity set to 'grave' from 'normal'
> tags -1 security upstream
Bug #1015783 [jupyter-notebook] Please update jupyter-notebook to 6.4.12
Added tag(s) upstream and security.

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

Processed: bug 1016519 is forwarded to https://trac.ffmpeg.org/ticket/9855, tagging 1016519

[Debian Bug Tracking System]

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

> forwarded 1016519 https://trac.ffmpeg.org/ticket/9855
Bug #1016519 [src:ffmpeg] ffmpeg: FTBFS
Set Bug forwarded-to-address to 'https://trac.ffmpeg.org/ticket/9855'.
> tags 1016519 + upstream
Bug #1016519 [src:ffmpeg] ffmpeg: FTBFS
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#1013929: marked as done (src:goffice: fails to migrate to testing for too long: FTBFS on mips64el)

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2022 08:23:06 +
with message-id 
and subject line Bug#1013929: fixed in goffice 0.10.52-3
has caused the Debian Bug report #1013929,
regarding src:goffice: fails to migrate to testing for too long: FTBFS on 
mips64el
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.)


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

Source: goffice
Version: 0.10.51-1
Severity: serious
Tags: sid bookworm
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:goffice has been trying to migrate for 61 
days [2]. Hence, I am filing this bug. Your package fails to build from 
source on mips64el where it successfully built 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 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=goffice



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: goffice
Source-Version: 0.10.52-3
Done: Dmitry Smirnov 

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

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated goffice 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: Tue, 02 Aug 2022 17:39:55 +1000
Source: goffice
Architecture: source
Version: 0.10.52-3
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Dmitry Smirnov 
Closes: 1013929
Changes:
 goffice (0.10.52-3) unstable; urgency=medium
 .
   * New upstream patch to fix FTBFS on [mips64el] (Closes: #1013929).
Checksums-Sha1:
 b4551fed9f012d6c90090eb019b794a277f688c0 2503 goffice_0.10.52-3.dsc
 5853261e5ced11844e6dac2fd31a0225b88be313 23648 goffice_0.10.52-3.debian.tar.xz
 1b06df8633a2722da66ae03ed13513bb5a2e2b9a 16889 
goffice_0.10.52-3_amd64.buildinfo
Checksums-Sha256:
 9dd29c0427ed109ba0b30a5a7e01feac87a0aa811f722ea981313cd9f821b258 2503 
goffice_0.10.52-3.dsc
 4c605e32efbfbfa88cfa427c39421668ff71cbfed0577f7ba58376dd467062c3 23648 
goffice_0.10.52-3.debian.tar.xz
 c36ebba33386f29892bcf116b3f0d0eba3cd198b9bcb94561ae036f88695f534 16889 
goffice_0.10.52-3_amd64.buildinfo
Files:
 605958454db28a9d47980c72325fe6cf 2503 libs optional goffice_0.10.52-3.dsc
 3cf28664e68c7515572985de3885f383 23648 libs optional 
goffice_0.10.52-3.debian.tar.xz
 1aa38a77b71423c3f23d9cf355be98eb 16889 libs optional 
goffice_0.10.52-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEULx8+TnSDCcqawZWUra72VOWjRsFAmLo1vYACgkQUra72VOW
jRvE4w//Znwae0rnOa43VFpexJmvx7M93rqgLFwC9nDdNrVid+NkVLKF71edme+l
k67LWXb/L3OZLn+3OFLuD+STyiJ7gbV0+FPUNZK3fyMBzOGLtPEkSnMGd+9Snh9u
43fXDwcdAPRdpiFSyPyF5q0vWP3S8SG0H02wYUc/+Fc4rAWi+kthNYHT3KMVupVN
NKYSSNnwGuieP048miFgdlkaRr5naVHGXc4DXAo1HtGHvvJk4cv3/h9be0hWKkY8
jy8iEmv2LkUmRrdHLqqRsDVCeJZ1KWGqszsc+/grpgnZvwjUVTcvvjYV5mJosrxM
282n1mFJaY87ZD5kjhWegnuEjda+MMl12/jUSLspQH0Sv53YWaOZjWrpyTYgAXpd

Bug#1016520: KeyError: 'dislike_count'

[michel]

Package: python3-pafy
Version: 0.5.2-2.1
Severity: grave
Tags: patch
Justification: renders package unusable
X-Debbugs-Cc: okgomdjgbm...@gmail.com

Dear Maintainer,



pafy broke, after youtube droped dislike counts. There's a proper fix upstream 
in the dev repo but not released yet.


A simple fix for the current package: In backend_youtube_dl.py

replace the line: self._dislikes = self._ydl_info['dislike_count']
with: self._dislikes = "0"

Bug#1016519: ffmpeg: FTBFS

[Gianfranco Costamagna]

Source: ffmpeg
Version: 7:5.1-1
Severity: serious

Hello, version 5.1-1 is currently FTBFS on s390x (and all Big Endian 
architectures?).
Can you please have a look?

thanks

G.

TESTfilter-overlay_yuv420p10
/<>/tests/fate-run.sh fate-filter-overlay_yuv420p10 "" "" 
"/<>/debian/standard" 'framecrc -auto_conversion_filters -c:v pgmyuv -i 
/<>/debian/standard/tests/vsynth1/%02d.pgm -filter_complex_script 
/<>/debian/standard/tests/data/filtergraphs/overlay_yuv420p10 -pix_fmt yuv420p10le -frames:v 3' '' '' '' '1' '' '' '' '' '' '' '' '' 
'' ''
 /<>/debian/standard/ffmpeg -nostdin -nostats -noauto_conversion_filters -cpuflags all 
-auto_conversion_filters -c:v pgmyuv -hwaccel none -threads 1 -thread_type frame+slice -i 
/<>/debian/standard/tests/vsynth1/%02d.pgm -filter_complex_script 
/<>/debian/standard/tests/data/filtergraphs/overlay_yuv420p10 -pix_fmt yuv420p10le 
-frames:v 3 -bitexact -f framecrc -
TESTfilter-overlay_nv12
/<>/tests/fate-run.sh fate-filter-overlay_nv12 "" "" "/<>/debian/standard" 'framecrc 
-auto_conversion_filters -c:v pgmyuv -i /<>/debian/standard/tests/vsynth1/%02d.pgm -filter_complex_script 
/<>/debian/standard/tests/data/filtergraphs/overlay_nv12' '' '/<>/tests/ref/fate/filter-overlay_yuv420' '' '1' '' '' '' 
'' '' '' '' '' '' ''
 /<>/debian/standard/ffmpeg -nostdin -nostats -noauto_conversion_filters -cpuflags all 
-auto_conversion_filters -c:v pgmyuv -hwaccel none -threads 1 -thread_type frame+slice -i 
/<>/debian/standard/tests/vsynth1/%02d.pgm -filter_complex_script 
/<>/debian/standard/tests/data/filtergraphs/overlay_nv12 -bitexact -f framecrc -
--- /<>/tests/ref/fate/filter-overlay_yuv420p102022-07-22 
17:58:40.0 +
+++ tests/data/fate/filter-overlay_yuv420p102022-07-31 19:51:46.046562449 
+
@@ -3,6 +3,6 @@
 #codec_id 0: rawvideo
 #dimensions 0: 352x288
 #sar 0: 0/1
-0,  0,  0,1,   304128, 0x524bcfc6
-0,  1,  1,1,   304128, 0xab3a13af
-0,  2,  2,1,   304128, 0xac08d718
+0,  0,  0,1,   304128, 0xd041d116
+0,  1,  1,1,   304128, 0x293f14ff
+0,  2,  2,1,   304128, 0x2a0dd868
Test filter-overlay_yuv420p10 failed. Look at 
tests/data/fate/filter-overlay_yuv420p10.err for details.
ffmpeg version 5.1-1 Copyright (c) 2000-2022 the FFmpeg developers
  built with gcc 12 (Debian 12.1.0-7)
  configuration: --prefix=/usr --extra-version=1 --toolchain=hardened 
--libdir=/usr/lib/s390x-linux-gnu --incdir=/usr/include/s390x-linux-gnu 
--arch=s390x --enable-gpl --disable-stripping --enable-gnutls --enable-ladspa 
--enable-libaom --enable-libass --enable-libbluray --enable-libbs2b 
--enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libdav1d 
--enable-libflite --enable-libfontconfig --enable-libfreetype 
--enable-libfribidi --enable-libglslang --enable-libgme --enable-libgsm 
--enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg 
--enable-libopenmpt --enable-libopus --enable-libpulse --enable-librabbitmq 
--enable-librist --enable-librubberband --enable-libshine --enable-libsnappy 
--enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh 
--enable-libsvtav1 --enable-libtheora --enable-libtwolame --enable-libvidstab 
--enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx265 
--enable-libxml2 --enable-libxvid --enable-libzimg --enable-libzmq 
--enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl 
--enable-opengl --enable-sdl2 --disable-sndio --enable-librsvg 
--enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint 
--enable-frei0r --enable-libplacebo --enable-libx264 
--ignore-tests='hapenc-hap-none,hapenc-hapa-none,hapenc-hapq-none' 
--enable-shared
  libavutil  57. 28.100 / 57. 28.100
  libavcodec 59. 37.100 / 59. 37.100
  libavformat59. 27.100 / 59. 27.100
  libavdevice59.  7.100 / 59.  7.100
  libavfilter 8. 44.100 /  8. 44.100
  libswscale  6.  7.100 /  6.  7.100
  libswresample   4.  7.100 /  4.  7.100
  libpostproc56.  6.100 / 56.  6.100
Input #0, image2, from 
'/<>/debian/standard/tests/vsynth1/%02d.pgm':
  Duration: 00:00:02.00, start: 0.00, bitrate: N/A
  Stream #0:0: Video: pgmyuv, yuv420p, 352x288, 25 fps, 25 tbr, 25 tbn
Stream mapping:
  Stream #0:0 (pgmyuv) -> split:default
  overlay:default -> Stream #0:0 (rawvideo)
Output #0, framecrc, to 'pipe:':
  Stream #0:0: Video: rawvideo (Y3[11][10] / 0xA0B3359), yuv420p10le(tv, 
progressive), 352x288, q=2-31, 38016 kb/s, 25 fps, 25 tbn
Metadata:
  encoder : Lavc rawvideo
frame=3 fps=0.0 q=-0.0 Lsize=   0kB time=00:00:00.12 bitrate=  
17.6kbits/s speed=14.2x
video:891kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing 
overhead: unknown
make[2]: *** [/<>/tests/Makefile:305: 
fate-filter-overlay_yuv420p10] Error 1
TESTfilter-overlay_nv21
/<>/tests/fate-run.sh fate-filter-overlay_nv21 "" "" 

Bug#1013929: marked as pending in goffice

[Dmitry Smirnov]

Control: tag -1 pending

Hello,

Bug #1013929 in goffice reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/debian/goffice/-/commit/8ee5145f01311f19d77106404f715f3b97128409


New upstream patch to fix FTBFS on [mips64el] (Closes: #1013929).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1013929

Processed: Bug#1013929 marked as pending in goffice

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1013929 [src:goffice] src:goffice: fails to migrate to testing for too 
long: FTBFS on mips64el
Added tag(s) pending.

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

Bug#1016385: marked as done (asn1c-doc: trying to overwrite '/usr/share/doc/asn1c/BUGS', which is also in package asn1c 0.9.28+dfsg-3)

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2022 07:03:58 +
with message-id 
and subject line Bug#1016385: fixed in asn1c 0.9.28+dfsg-5
has caused the Debian Bug report #1016385,
regarding asn1c-doc: trying to overwrite '/usr/share/doc/asn1c/BUGS', which is 
also in package asn1c 0.9.28+dfsg-3
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.)


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

Package: asn1c-doc
Version: 0.9.28+dfsg-4
Severity: serious

Upgrading the package failed:

  Unpacking asn1c-doc (0.9.28+dfsg-4) over (0.9.28+dfsg-3) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-wSkNUL/03-asn1c-doc_0.9.28+dfsg-4_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/asn1c/BUGS', which is also in package 
asn1c 0.9.28+dfsg-3

--
Jakub Wilk
--- End Message ---
--- Begin Message ---
Source: asn1c
Source-Version: 0.9.28+dfsg-5
Done: Eugene Seliverstov 

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

Debian distribution maintenance software
pp.
Eugene Seliverstov  (supplier of updated asn1c 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, 01 Aug 2022 09:49:37 +
Source: asn1c
Built-For-Profiles: noudeb
Architecture: source
Version: 0.9.28+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Eugene Seliverstov 
Changed-By: Eugene Seliverstov 
Closes: 1016385
Changes:
 asn1c (0.9.28+dfsg-5) unstable; urgency=medium
 .
   * Update package transitions (closes: #1016385)
Checksums-Sha1:
 10c5ecba2c875d178594654fb82246daef7c9e8e 2009 asn1c_0.9.28+dfsg-5.dsc
 66c77df62f9b84b83c2800ac23aac5c319168077 7956 asn1c_0.9.28+dfsg-5.debian.tar.xz
 82c2951b77bb7dbd4f311c39d03b791c669b3e79 7334 
asn1c_0.9.28+dfsg-5_source.buildinfo
Checksums-Sha256:
 7041bd5dbba9115c7da09d7dcdfea933281c945610073512d6079302da330cc2 2009 
asn1c_0.9.28+dfsg-5.dsc
 3972ff98aafb2d365c7cbb87eadffc6b38428343c5d2e4eebb99cd19e9240b5a 7956 
asn1c_0.9.28+dfsg-5.debian.tar.xz
 5ca579c708fb8533a2d5661c96fe62ec5c63fefc35b6ca3338f1f4fc888e971f 7334 
asn1c_0.9.28+dfsg-5_source.buildinfo
Files:
 de833c38ba17c16ae3fd122cc50c307f 2009 devel optional asn1c_0.9.28+dfsg-5.dsc
 0700d38874b7fa682ec33f6786a0ef3a 7956 devel optional 
asn1c_0.9.28+dfsg-5.debian.tar.xz
 28a93cdbf01929feb266511b8767ae23 7334 devel optional 
asn1c_0.9.28+dfsg-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAmLoyAUACgkQ808JdE6f
XdksrxAAvyVeKvElGk/ibMDQwS0ERHT/MV5Bo3YQRlzd6BYSFtXm5w1f5AksobpD
783dWlfv30JEfczlAKVLGo0VBElL8ObKQ+Z1AE1nso8mQ6/sfZ+cfEg0G83QXFMH
JywzAxRJpNWQ17SWRvp5U046y6qyB5QSaHk6aT/pYax948zAxiVvZapLcPASKp2m
eP0vydy/yJ5waoVHr3pIco1WJ+6cUDRL9ilXjedCqGCbqIOTpzvzSeadS/eOZEGQ
/T0lXXJiw/mzn5G1QJB/5v85tS1869CEX5WZbOYNMDXd9kKSpsAuV9C8C70hV96C
YwZFXD8DWhDd6Mk4S/6wgMkGAIJDYA/I9cIHSGE5H3jyDcU1rP6MIcnYPvoRrW+M
GQzDTjfFaO3xust+0cxspRLMDD+hzD76jlsWcQI3ueKJWh3dN5R8ytny8k1He13a
Y1W4jA8n2Kr8hWC48X5Q5ryfj0O6Kh291c4nADhDJef+o99oIiTnVQgX5i1I/ZzR
sIrp0+05IxYW/dxG08jaupfhpw1lNidcJYUzFJ4+gk3aKHmDHYvXrgE0UIqiaLp+
E8rsF6LE2AiS26kDMmUF4LPuJIF0hBHsjYjTNx8ZMPaHODPx7WzdLWdhf6GtpNzJ
n3TRE0gSTmeozHZO3MKz4W7CmPLzm2hN2Q7A8+Vz0xUoQKAJCjQ=
=gvl0
-END PGP SIGNATURE End Message ---

Bug#1016501: marked as done (node-rollup-plugin-typescript2: ships /usr/share/nodejs/graphlib/*, already in node-graphlibrary)

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2022 06:49:52 +
with message-id 
and subject line Bug#1016501: fixed in node-rollup-plugin-typescript2 
0.32.1+repack1+~cs5.2.1-1
has caused the Debian Bug report #1016501,
regarding node-rollup-plugin-typescript2: ships /usr/share/nodejs/graphlib/*, 
already in node-graphlibrary
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.)


-- 
1016501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016501
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-rollup-plugin-typescript2
Version: 0.32.1+ds+~cs9.4.17-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

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

  Selecting previously unselected package node-rollup-plugin-typescript2.
  Preparing to unpack 
.../36-node-rollup-plugin-typescript2_0.32.1+ds+~cs9.4.17-1_all.deb ...
  Unpacking node-rollup-plugin-typescript2 (0.32.1+ds+~cs9.4.17-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-bJes1H/36-node-rollup-plugin-typescript2_0.32.1+ds+~cs9.4.17-1_all.deb
 (--unpack):
   trying to overwrite '/usr/share/nodejs/graphlib/index.js', which is also in 
package node-graphlibrary 2.2.0+really2.1.8+dfsg-4
  Errors were encountered while processing:
   
/tmp/apt-dpkg-install-bJes1H/36-node-rollup-plugin-typescript2_0.32.1+ds+~cs9.4.17-1_all.deb

The following files are in conflict:

usr/share/nodejs/graphlib/index.js
usr/share/nodejs/graphlib/lib/alg/components.js
usr/share/nodejs/graphlib/lib/alg/dfs.js
usr/share/nodejs/graphlib/lib/alg/dijkstra-all.js
usr/share/nodejs/graphlib/lib/alg/dijkstra.js
usr/share/nodejs/graphlib/lib/alg/find-cycles.js
usr/share/nodejs/graphlib/lib/alg/floyd-warshall.js
usr/share/nodejs/graphlib/lib/alg/index.js
usr/share/nodejs/graphlib/lib/alg/is-acyclic.js
usr/share/nodejs/graphlib/lib/alg/postorder.js
usr/share/nodejs/graphlib/lib/alg/preorder.js
usr/share/nodejs/graphlib/lib/alg/prim.js
usr/share/nodejs/graphlib/lib/alg/tarjan.js
usr/share/nodejs/graphlib/lib/alg/topsort.js
usr/share/nodejs/graphlib/lib/data/priority-queue.js
usr/share/nodejs/graphlib/lib/graph.js
usr/share/nodejs/graphlib/lib/index.js
usr/share/nodejs/graphlib/lib/json.js
usr/share/nodejs/graphlib/lib/lodash.js
usr/share/nodejs/graphlib/lib/version.js
usr/share/nodejs/graphlib/package.json


cheers,

Andreas


node-graphlibrary=2.2.0+really2.1.8+dfsg-4_node-rollup-plugin-typescript2=0.32.1+ds+~cs9.4.17-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: node-rollup-plugin-typescript2
Source-Version: 0.32.1+repack1+~cs5.2.1-1
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-rollup-plugin-typescript2 
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: Tue, 02 Aug 2022 08:31:40 +0200
Source: node-rollup-plugin-typescript2
Architecture: source
Version: 0.32.1+repack1+~cs5.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1016501
Changes:
 node-rollup-plugin-typescript2 (0.32.1+repack1+~cs5.2.1-1) unstable; 
urgency=medium
 .
   * Drop component graphlib and repack (Closes: #1016501)
Checksums-Sha1: 
 3c4582754ab400369ab40f8575d122e24425ef59 3670 
node-rollup-plugin-typescript2_0.32.1+repack1+~cs5.2.1-1.dsc
 48393d158b30b4b2e74757b03da466ab8223e863 13704 
node-rollup-plugin-typescript2_0.32.1+repack1+~cs5.2.1.orig-object-hash.tar.xz
 a13d6229d1f9a93a3c802d8bafa38aa65be271db 2168 
node-rollup-plugin-typescript2_0.32.1+repack1+~cs5.2.1.orig-types-object-hash.tar.xz
 3ba1cbea3c4581f1956c3329c8bc2318dc4087c6 53360 
node-rollup-plugin-typescript2_0.32.1+repack1+~cs5.2.1.orig.tar.xz
 8293683ba13ef4100f904ed34d3412372b3a7326 5160 
node-rollup-plugin-typescript2_0.32.1+repack1+~cs5.2.1-1.debian.tar.xz
Checksums-Sha256: 
 

Bug#1016237: marked as done (efl: FTBFS: jquery is used Error 1)

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2022 06:35:47 +
with message-id 
and subject line Bug#1016237: fixed in efl 1.26.2-2
has caused the Debian Bug report #1016237,
regarding efl: FTBFS: jquery is used Error 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.)


-- 
1016237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016237
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: efl
Version: 1.26.2-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220728 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_install 
> # remove unused file, fail otherwise
> rm -f obj-x86_64-linux-gnu/html/jquery.js
> if grep -qr jquery.js obj-x86_64-linux-gnu/html/ ; \
>   then echo jquery is used ; false ; fi
> jquery is used
> make[1]: *** [debian/rules:86: override_dh_install] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/07/28/efl_1.26.2-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220728;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220728=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: efl
Source-Version: 1.26.2-2
Done: Ross Vandegrift 

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

Debian distribution maintenance software
pp.
Ross Vandegrift  (supplier of updated efl 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, 01 Aug 2022 22:50:48 -0700
Source: efl
Architecture: source
Version: 1.26.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Pkg-e Team 
Changed-By: Ross Vandegrift 
Closes: 1008040 1016237
Changes:
 efl (1.26.2-2) unstable; urgency=medium
 .
   * d/control: weaken libelementary1 recommends on -bin to get better
 dependencies after binnmu (Closes: #1008040)
   * d/copyright: update upstream git url
   * d/rules: drop fake_home.sh, compat 13 provides writable $HOME and $XDG_*
   * 30_disable_chm_docs.diff: disable chm docs (Closes: #1016237)
   * Update some lintian overrides for new format
Checksums-Sha1:
 99d71e66ec440719e6dfa93f29f9fe7ac7d8ecde 6451 efl_1.26.2-2.dsc
 b6da51ceb0f663a90534a13836e912cb8d5862af 97600 efl_1.26.2-2.debian.tar.xz
Checksums-Sha256:
 64b1ad880bb4a544700ce7301a8a959f7349dedb0a018787a2bd5cae16aa3281 6451 
efl_1.26.2-2.dsc
 88435d69b0faf177fe8854d081156ba6457436cfa07a39e0117c6813d5e21a62 97600 
efl_1.26.2-2.debian.tar.xz
Files:
 c08f0c9c6d2bf30ec3b5cdc47b887d4a 6451 libs optional efl_1.26.2-2.dsc
 05b5f4a9f9a225ed15231b851c24c462 97600 libs optional efl_1.26.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEsAjXULa3g2HtU1bw2rOJMppM+hYFAmLowS0ACgkQ2rOJMppM
+hb1PQ/8DIple/e+DMCb8Q3VZhvNG7Mc4V1vmfku/q5ci9Ud2YCXQ6pMWLX6I6Gz
1JrSwpZxi23bnLLUC74cYSVCZl94KLlyLLRZ6yfOJcaYY2AYK/daP0MocsQwS4w6
WO3I6IwcPNpSmRzcSxvsYdJuC9w0wYQD488u/0cyLH054rpqBW0cvrqXPKV9UPl9
xSTxt802s7ROc6gaRp/kkU1TrH+T4lMS/ODpzrWhnLbtMFEonepURpCpu+Yc42RS
WwZWbea9vLFC7LZzoJ2PKDrgz25RQDZZ4fRmv2UrB7fyqS8UVEaIbIc+8pifj8ZG
0qDKIFukBA2/vXAOBBNkADdynm8vCBpew4bYknuDDffSG8suYxRh+UJMZsgvA6cf
zowdn+Uv3BVuivVTm87Bv+ngcUdQVPh541PYPo/IRrgU/oLzcaNbJex1Wm56A6P2
sS2gnJ4xRYl7i/jkBuqgJ3iW8zlGbThEkisVxYe/WI+oXl5+n5gIWwLVq3pa1sWE
Ep6fx0qEJxjHydKCMc2diWYlpLlFJ2e5lNkqMV7tQkfL0FIpfMow2HzxgkiwBThB
br0XMWfDokJbC70AOxiKvxsrohISdDVrk4VxoxWTZq5Ovy21jWXtMwHhijhK/ZQG

Bug#1013940: marked as done (nfft breaks pynfft autopkgtest on i386: Segmentation fault)

[Debian Bug Tracking System]

Your message dated Tue, 2 Aug 2022 08:29:57 +0200
with message-id 
and subject line Closing bug since autopkgtest of pynfft is working now
has caused the Debian Bug report #1013940,
regarding nfft breaks pynfft autopkgtest on i386: Segmentation fault
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.)


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

Source: nfft, pynfft
Control: found -1 nfft/3.3.2-2.1
Control: found -1 pynfft/1.3.2-5
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of nfft the autopkgtest of pynfft fails in testing 
when that autopkgtest is run with the binary packages of nfft from 
unstable. It passes when run with only packages from testing. In tabular 
form:


   passfail
nfft   from testing3.3.2-2.1
pynfft from testing1.3.2-5
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of nfft to testing 
[1]. Due to the nature of this issue, I filed this bug report against 
both packages. Can you please investigate the situation and reassign the 
bug to the right package?


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=nfft

https://ci.debian.net/data/autopkgtest/testing/i386/p/pynfft/23100486/log.gz

=== python3.9 ===
Segmentation fault
autopkgtest [15:22:19]: test python3



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Closing bug since autopkgtest of pynfft is working now.--- End Message ---

Bug#1016514: libfm-qt-common: missing Breaks+Replaces: libfm-qt8

[Andreas Beckmann]

Package: libfm-qt-common
Version: 1.1.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
This error may also be triggered by having a predecessor package from
'sid 'installed while installing the package from 'experimental'.

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 .../libfm-qt-common_1.1.0-2_all.deb ...
  Unpacking libfm-qt-common (1.1.0-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libfm-qt-common_1.1.0-2_all.deb (--unpack):
   trying to overwrite '/usr/share/libfm-qt/archivers.list', which is also in 
package libfm-qt8:amd64 0.16.0-3.2
  Errors were encountered while processing:
   /var/cache/apt/archives/libfm-qt-common_1.1.0-2_all.deb


cheers,

Andreas


libfm-qt8=0.16.0-3.2_libfm-qt-common=1.1.0-2.log.gz
Description: application/gzip

Bug#1016513: node-fetch: node-data-uri-to-buffer is now packaged separately

[Andreas Beckmann]

Package: node-fetch
Version: 3.2.9+~cs18.4.14-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files.

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

  Preparing to unpack .../node-fetch_3.2.9+~cs18.4.14-1_all.deb ...
  Unpacking node-fetch (3.2.9+~cs18.4.14-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/node-fetch_3.2.9+~cs18.4.14-1_all.deb (--unpack):
   trying to overwrite '/usr/share/nodejs/data-uri-to-buffer/dist/index.d.ts', 
which is also in package node-data-uri-to-buffer 4.0.0-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/node-fetch_3.2.9+~cs18.4.14-1_all.deb


cheers,

Andreas


node-data-uri-to-buffer=4.0.0-2_node-fetch=3.2.9+~cs18.4.14-1.log.gz
Description: application/gzip

Bug#1016512: multipath-tools: ships /usr/share/bug/multipath-tools-boot/script

[Andreas Beckmann]

Package: multipath-tools
Version: 0.9.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

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

  Preparing to unpack .../multipath-tools-boot_0.9.0-2_all.deb ...
  Unpacking multipath-tools-boot (0.9.0-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/multipath-tools-boot_0.9.0-2_all.deb (--unpack):
   trying to overwrite '/usr/share/bug/multipath-tools-boot/script', which is 
also in package multipath-tools 0.9.0-2
  Errors were encountered while processing:
   /var/cache/apt/archives/multipath-tools-boot_0.9.0-2_all.deb

Are you installing that file manually instead of using dh_bugfiles -A ?


cheers,

Andreas


multipath-tools=0.9.0-2_multipath-tools-boot=0.9.0-2.log.gz
Description: application/gzip