date:20230227

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

> reassign 1021165 src:glibc 2.36-5
Bug #1021165 {Done: Matthias Klose } [libc6.1-dev] armhf: 
floatn-common.h:214:9: error: multiple types in one declaration
Warning: Unknown package 'libc6.1-dev'
Bug reassigned from package 'libc6.1-dev' to 'src:glibc'.
No longer marked as found in versions 2.36-5.
Ignoring request to alter fixed versions of bug #1021165 to the same values 
previously set
Bug #1021165 {Done: Matthias Klose } [src:glibc] armhf: 
floatn-common.h:214:9: error: multiple types in one declaration
Marked as found in versions glibc/2.36-5.
>
End of message, stopping processing here.

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

Processed: your mail

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

> affects 1021165 src:gcc-snapshot
Bug #1021165 {Done: Matthias Klose } [libc6.1-dev] armhf: 
floatn-common.h:214:9: error: multiple types in one declaration
Warning: Unknown package 'libc6.1-dev'
Added indication that 1021165 affects src:gcc-snapshot
Warning: Unknown package 'libc6.1-dev'
> user debian-sp...@lists.debian.org
Setting user to debian-sp...@lists.debian.org (was ma...@debian.org).
> usertags 1031866 sparc64
There were no usertags set.
Usertags are now: sparc64.
> user debian-i...@lists.debian.org
Setting user to debian-i...@lists.debian.org (was 
debian-sp...@lists.debian.org).
> usertags 1031866 ia64
There were no usertags set.
Usertags are now: ia64.
>
End of message, stopping processing here.

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

Processed: floatn-common.h:214:9: error: multiple types in one declaration

Processing control commands:

> reassign -1 libc6.1-dev 2.36-5
Bug #1021165 {Done: Matthias Klose } [src:gcc-snapshot] armhf: 
floatn-common.h:214:9: error: multiple types in one declaration
Bug reassigned from package 'src:gcc-snapshot' to 'libc6.1-dev'.
Warning: Unknown package 'libc6.1-dev'
Warning: Unknown package 'libc6.1-dev'
No longer marked as found in versions gcc-snapshot/1:20220920-1.
Warning: Unknown package 'libc6.1-dev'
Warning: Unknown package 'libc6.1-dev'
Ignoring request to alter fixed versions of bug #1021165 to the same values 
previously set
Warning: Unknown package 'libc6.1-dev'
Bug #1021165 {Done: Matthias Klose } [libc6.1-dev] armhf: 
floatn-common.h:214:9: error: multiple types in one declaration
Warning: Unknown package 'libc6.1-dev'
There is no source info for the package 'libc6.1-dev' at version '2.36-5' with 
architecture ''
Unable to make a source version for version '2.36-5'
Marked as found in versions 2.36-5.
Warning: Unknown package 'libc6.1-dev'

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

Bug#1021165: floatn-common.h:214:9: error: multiple types in one declaration

2023-02-27 Thread Mathieu Malaterre

Control: reassign -1 libc6.1-dev 2.36-5

Looks like the issue is not fixed on ia64 / sparc64.

Steps:

% cat p.cxx
#include 

int main() { return 0; }

Lead to:

malat@yttrium ~ % /usr/lib/gcc-snapshot/bin/g++ -v p.cxx
Using built-in specs.
COLLECT_GCC=/usr/lib/gcc-snapshot/bin/g++
COLLECT_LTO_WRAPPER=/usr/lib/gcc-snapshot/libexec/gcc/ia64-linux-gnu/13/lto-wrapper
Target: ia64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian
20221021-1' --with-bugurl=file:///usr/share/doc/gcc-snapshot/README.Bugs
--enable-languages=c,c++,go,fortran,objc,obj-c++,m2
--prefix=/usr/lib/gcc-snapshot --with-gcc-major-version-only
--program-prefix= --enable-shared --enable-linker-build-id
--disable-nls --enable-clocale=gnu --enable-libstdcxx-debug
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new
--enable-gnu-unique-object --disable-libssp --disable-libitm
--disable-libsanitizer --enable-plugin --with-system-zlib
--enable-objc-gc=auto --enable-multiarch --disable-werror
--with-system-libunwind --enable-checking=yes --build=ia64-linux-gnu
--host=ia64-linux-gnu --target=ia64-linux-gnu
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.0.0 20221021 (experimental) [master
r13-3434-ga9de836c2b2] (Debian 20221021-1)
COLLECT_GCC_OPTIONS='-v' '-shared-libgcc' '-dumpdir' 'a-'
 /usr/lib/gcc-snapshot/libexec/gcc/ia64-linux-gnu/13/cc1plus -quiet -v
-imultilib . -imultiarch ia64-linux-gnu -D_GNU_SOURCE p.cxx -quiet
-dumpdir a- -dumpbase p.cxx -dumpbase-ext .cxx -version -o
/tmp/ccMCj3Mu.s
GNU C++17 (Debian 20221021-1) version 13.0.0 20221021 (experimental)
[master r13-3434-ga9de836c2b2] (ia64-linux-gnu)
compiled by GNU C version 13.0.0 20221021 (experimental)
[master r13-3434-ga9de836c2b2], GMP version 6.2.1, MPFR version 4.1.0,
MPC version 1.2.1, isl version isl-0.25-GMP

warning: MPFR header version 4.1.0 differs from library version 4.2.0.
warning: MPC header version 1.2.1 differs from library version 1.3.1.
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
ignoring nonexistent directory "/usr/local/include/ia64-linux-gnu"
ignoring nonexistent directory
"/usr/lib/gcc-snapshot/lib/gcc/ia64-linux-gnu/13/include-fixed/ia64-linux-gnu"
ignoring nonexistent directory
"/usr/lib/gcc-snapshot/lib/gcc/ia64-linux-gnu/13/include-fixed"
ignoring nonexistent directory
"/usr/lib/gcc-snapshot/lib/gcc/ia64-linux-gnu/13/../../../../ia64-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
 /usr/lib/gcc-snapshot/lib/gcc/ia64-linux-gnu/13/../../../../include/c++/13
 
/usr/lib/gcc-snapshot/lib/gcc/ia64-linux-gnu/13/../../../../include/c++/13/ia64-linux-gnu/.
 
/usr/lib/gcc-snapshot/lib/gcc/ia64-linux-gnu/13/../../../../include/c++/13/backward
 /usr/lib/gcc-snapshot/lib/gcc/ia64-linux-gnu/13/include
 /usr/local/include
 /usr/lib/gcc-snapshot/include
 /usr/include/ia64-linux-gnu
 /usr/include
End of search list.
GNU C++17 (Debian 20221021-1) version 13.0.0 20221021 (experimental)
[master r13-3434-ga9de836c2b2] (ia64-linux-gnu)
compiled by GNU C version 13.0.0 20221021 (experimental)
[master r13-3434-ga9de836c2b2], GMP version 6.2.1, MPFR version 4.1.0,
MPC version 1.2.1, isl version isl-0.25-GMP

warning: MPFR header version 4.1.0 differs from library version 4.2.0.
warning: MPC header version 1.2.1 differs from library version 1.3.1.
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
Compiler executable checksum: 46cce3a938a51610ba7278d8fb426d84
In file included from /usr/include/stdio.h:430,
 from p.cxx:1:
/usr/include/ia64-linux-gnu/bits/floatn.h:84:9: error: multiple types
in one declaration
   84 | typedef __float128 _Float128;
  | ^~
/usr/include/ia64-linux-gnu/bits/floatn.h:84:20: error: declaration
does not declare anything [-fpermissive]
   84 | typedef __float128 _Float128;
  |^
In file included from /usr/include/ia64-linux-gnu/bits/floatn.h:117:
/usr/include/ia64-linux-gnu/bits/floatn-common.h:214:9: error:
multiple types in one declaration
  214 | typedef float _Float32;
  | ^
/usr/include/ia64-linux-gnu/bits/floatn-common.h:214:15: error:
declaration does not declare anything [-fpermissive]
  214 | typedef float _Float32;
  |   ^~~~
/usr/include/ia64-linux-gnu/bits/floatn-common.h:251:9: error:
multiple types in one declaration
  251 | typedef double _Float64;
  | ^~
/usr/include/ia64-linux-gnu/bits/floatn-common.h:251:16: error:
declaration does not declare anything [-fpermissive]
  251 | typedef double _Float64;
  |^~~~
/usr/include/ia64-linux-gnu/bits/floatn-common.h:268:9: error:
multiple types in one declaration
  268 | typedef double _Float32x;
  | ^~
/usr/include/ia64-linux-gnu/bits/floatn-common.h:268:16: error:
declaration does not declare anything [-fpermissive]
  268 | typedef double _Float32x;
  |^

Bug#1032104: linux: ppc64el iouring corrupted read

2023-02-27 Thread Daniel Black

On Tue, Feb 28, 2023 at 5:24 PM Diederik de Haas  wrote:
>
> On Tuesday, 28 February 2023 04:13:18 CET Daniel Black wrote:
> > Source: linux
> > Version: 5.10.0-21-powerpc64le
> > Severity: grave
> > Justification: causes non-serious data loss
> > X-Debbugs-Cc: dan...@mariadb.org
> >
> > >From https://jira.mariadb.org/browse/MDEV-30728
> >
> > MariaDB's mtr tests on a number of specific tests depend on the correct
> > kernel operation.
> >
> > As observed in these tests, there is a ~1/5 chance the
> > encryption.innodb_encryption test will read zeros on the later part of
> > the 16k pages that InnoDB uses by default.
> >
> > This affects MariaDB-10.6+ packages where there is a liburing in the
> > distribution.
> >
> > I tested on tmpfs. This is a different fault from bug #1020831 as:
> > * there is no iouring error, just a bunch of zeros where data was
> >   expected.
> > * this is ppc64le only.
>
> What was the last kernel where this problem did NOT occur?

2022-12-19 03:55:34 install linux-image-5.10.0-20-powerpc64le:ppc64el
 5.10.158-2

no similar errors between ^ and ..

2023-01-24 03:19:59 install linux-image-5.10.0-21-powerpc64le:ppc64el
 5.10.162-1
(no other linux image installs in between these two)

first failure found ~ Feb 4 2023. Unsure when kernel rebooted to this
kernel bug it does appear to be the last revision.
https://buildbot.mariadb.org/#/builders/318/builds/10008

log example https://ci.mariadb.org/32263/logs/ppc64le-debian-11/mysqld.1.err.7
(search for CURRENT_TEST: encryption.innodb_encryption) - contains hex
dump of page

> It's probably needed to pinpoint the (upstream) commit that caused this error/
> issue and the best start is normally finding the closest range with Debian
> kernel releases where it did not and did occur.
>
> > -- System Information:
> > Debian Release: bullseye
> >   APT prefers jammy-updates
> >   APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500,
> > 'jammy'), (100, 'jammy-backports') Architecture: ppc64el (ppc64le)
> >
> > Kernel: Linux 5.10.0-21-powerpc64le (SMP w/128 CPU threads)
> > Init: unable to detect
>
> Why is there no 'bullseye' in APT policy's output?
> Mixing distrubutions (aka FrankenDebian) isn't recommended, but seeing no
> bullseye in there is odd, especially since the kernel version very much does
> look like Debian.

Apologies for the FrankenDebian look. This was a jammy container and
jammy report bug with bullseye edited (badly) in the system info.

Processed: your mail

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

> unarchive 1021165
Bug #1021165 {Done: Matthias Klose } [src:gcc-snapshot] armhf: 
floatn-common.h:214:9: error: multiple types in one declaration
Unarchived Bug 1021165
>
End of message, stopping processing here.

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

Bug#927124: marked as done (minitube: Minitube version in Debian Stable it's too old and doesn't work anymore.)

Your message dated Tue, 28 Feb 2023 08:34:49 +0100
with message-id <20230228083449.47ca1ee7@beer>
and subject line Re: Is API-key soliciting dialog being removed?
has caused the Debian Bug report #927124,
regarding minitube: Minitube version in Debian Stable it's too old and doesn't 
work anymore.
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.)


-- 
927124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927124
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: minitube
Version: 2.5.2-2 amd64
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   I think the package need an upgrade
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   I search a video, and instead I get a string about the google api.
   * What outcome did you expect instead?
   To get the list of the videos which are related to my search query 

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 9.8
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-8-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en_US (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages minitube depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.10.26-0+deb9u1
ii  dbus-x11 [dbus-session-bus]   1.10.26-0+deb9u1
ii  libc6 2.24-11+deb9u4
ii  libgcc1   1:6.3.0-18+deb9u1
ii  libgl1-mesa-glx [libgl1]  13.0.6-1+b2
ii  libphonon4qt5-4   4:4.9.0-4
ii  libqt5core5a  5.7.1+dfsg-3+deb9u1
ii  libqt5dbus5   5.7.1+dfsg-3+deb9u1
ii  libqt5gui55.7.1+dfsg-3+deb9u1
ii  libqt5network55.7.1+dfsg-3+deb9u1
ii  libqt5script5 5.7.1~20161021+dfsg-2
ii  libqt5sql55.7.1+dfsg-3+deb9u1
ii  libqt5sql5-sqlite 5.7.1+dfsg-3+deb9u1
ii  libqt5widgets55.7.1+dfsg-3+deb9u1
ii  libstdc++66.3.0-18+deb9u1
ii  phonon4qt54:4.9.0-4

minitube recommends no packages.

minitube suggests no packages.
--- End Message ---
--- Begin Message ---
Just a quick note to close this old bug report:

Current minitube no longer talks to YouTube directly and thus doesn't
need an API key anymore.

Cheers,
sur5r

-- 
ceterum censeo microsoftem esse delendam.


pgpjbr6vofXJi.pgp
Description: OpenPGP digital signature
--- End Message ---

Bug#1032114: Don't release with bookworm

Source: golang-github-jesseduffield-termbox-go
Version: 0.0~git20180919.1e272ff-2
Severity: serious
X-Debbugs-Cc: z...@debian.org

Fork of golang-github-nsf-termbox-go.
No new development in https://github.com/jesseduffield/termbox-go since 2020.
One reverse-depends golang-github-jesseduffield-gocui (#1032109).

Bug#1032104: linux: ppc64el iouring corrupted read

2023-02-27 Thread Diederik de Haas

On Tuesday, 28 February 2023 04:13:18 CET Daniel Black wrote:
> Source: linux
> Version: 5.10.0-21-powerpc64le
> Severity: grave
> Justification: causes non-serious data loss
> X-Debbugs-Cc: dan...@mariadb.org
> 
> >From https://jira.mariadb.org/browse/MDEV-30728
> 
> MariaDB's mtr tests on a number of specific tests depend on the correct
> kernel operation.
> 
> As observed in these tests, there is a ~1/5 chance the
> encryption.innodb_encryption test will read zeros on the later part of
> the 16k pages that InnoDB uses by default.
> 
> This affects MariaDB-10.6+ packages where there is a liburing in the
> distribution.
> 
> I tested on tmpfs. This is a different fault from bug #1020831 as:
> * there is no iouring error, just a bunch of zeros where data was
>   expected.
> * this is ppc64le only.

What was the last kernel where this problem did NOT occur?
It's probably needed to pinpoint the (upstream) commit that caused this error/
issue and the best start is normally finding the closest range with Debian 
kernel releases where it did not and did occur.

> -- System Information:
> Debian Release: bullseye
>   APT prefers jammy-updates
>   APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500,
> 'jammy'), (100, 'jammy-backports') Architecture: ppc64el (ppc64le)
> 
> Kernel: Linux 5.10.0-21-powerpc64le (SMP w/128 CPU threads)
> Init: unable to detect

Why is there no 'bullseye' in APT policy's output?
Mixing distrubutions (aka FrankenDebian) isn't recommended, but seeing no 
bullseye in there is odd, especially since the kernel version very much does 
look like Debian.

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

Bug#1032043: marked as done (pylint: autopkgtest regression)

Your message dated Tue, 28 Feb 2023 06:19:24 +
with message-id 
and subject line Bug#1032043: fixed in pylint 2.16.2-2
has caused the Debian Bug report #1032043,
regarding pylint: autopkgtest regression
to be marked as done.

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

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


-- 
1032043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032043
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pylint
Version: 2.16.2-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pylint/31703963/log.gz

...
=== FAILURES ===
___ test_functional[alternative_union_syntax_regession_8119] ___

self = 

def runTest(self) -> None:
>   self._runTest()
E   AssertionError: Wrong results for file 
"alternative_union_syntax_regession_8119":
E 
E Unexpected in testdata:
E   20: non-parent-init-called
E   23: access-member-before-definition
E   24: attribute-defined-outside-init
E 
E Actual pylint output for this file:
E OutputLine(symbol='non-parent-init-called', lineno=20, column=8, 
end_lineno=20, end_column=28, object='Child.__init__', msg="__init__ method 
from a non direct base class 'Coordinator' is called", confidence='UNDEFINED')
E OutputLine(symbol='access-member-before-definition', lineno=23, 
column=15, end_lineno=23, end_column=35, object='Child._async_update_data', 
msg="Access to member 'update_interval' before its definition line 24", 
confidence='UNDEFINED')
E OutputLine(symbol='attribute-defined-outside-init', lineno=24, 
column=8, end_lineno=24, end_column=28, object='Child._async_update_data', 
msg="Attribute 'update_interval' defined outside __init__", 
confidence='UNDEFINED')
E   assert Counter() == Counter({(20, 'non-parent-init-called'): 1, (23, 
'access-member-before-definition'): 1, (24, 'attribute-defined-outside-init'): 
1})
E Right contains 3 more items:
E {(20, 'non-parent-init-called'): 1,
E  (23, 'access-member-before-definition'): 1,
E  (24, 'attribute-defined-outside-init'): 1}
E Full diff:
E + Counter(,
E - Counter({(20, 'non-parent-init-called'): 1,
E -  (23, 'access-member-before-definition'): 1,
E -  (24, 'attribute-defined-outside-init'): 1},
E   )

/usr/lib/python3/dist-packages/pylint/testutils/lint_module_test.py:145: 
AssertionError
__ test_functional[wrong_exception_operation] __

self = 

def runTest(self) -> None:
>   self._runTest()
E   AssertionError: Wrong results for file "wrong_exception_operation":
E 
E Expected in testdata:
E6: catching-non-exception
E 
E Actual pylint output for this file:
E OutputLine(symbol='wrong-exception-operation', lineno=6, column=8, 
end_lineno=6, end_column=30, object='', msg="Invalid exception operation. Did 
you mean '(ValueError, TypeError)' instead?", confidence='UNDEFINED')
E OutputLine(symbol='wrong-exception-operation', lineno=11, column=8, 
end_lineno=11, end_column=30, object='', msg="Invalid exception operation. Did 
you mean '(ValueError, TypeError)' instead?", confidence='UNDEFINED')
E OutputLine(symbol='wrong-exception-operation', lineno=17, column=8, 
end_lineno=17, end_column=30, object='', msg="Invalid exception operation. Did 
you mean '(ValueError, TypeError)' instead?", confidence='UNDEFINED')
E   assert Counter({(6, 'catching-non-exception'): 1, (6, 
'wrong-exception-operation'): 1, (11, 'wrong-exception-operation'): 1, (17, 
'wrong-exception-operation'): 1}) == Counter({(6, 'wrong-exception-operation'): 
1, (11, 'wrong-exception-operation'): 1, (17, 'wrong-exception-operation'): 1})
E Common items:
E {(6, 'wrong-exception-operation'): 1,
E  (11, 'wrong-exception-operation'): 1,
E  (17, 'wrong-exception-operation'): 1}
E Left contains 1 more item:
E {(6, 'catching-non-exception'): 1}
E Full diff:
E + Counter({(6, 'catching-non-exception'): 1,
E - Counter({(6, 'wrong-exception-operation'): 1,
E ? ^
E +  (6, 'wrong-exception-operation'): 1,
E ? ^
E(11, 'wrong-exception-operation'): 1,
E(17, 'wrong-exception-operation'): 1},
E   )

/usr/lib/python3/dist-packages/pylint/testutils/lint_module_test.py:145: 
AssertionError
...
=== short test summa

Bug#1032113: Don't release with bookworm

Source: golang-github-jesseduffield-roll
Version: 0.0~git20190629.695be2e-3
Severity: serious
X-Debbugs-Cc: z...@debian.org

Fork of golang-github-stvp-roll-
One reverse-depends golang-github-jesseduffield-rollrus (#1032112).

Bug#1032112: Don't release with bookworm

Source: golang-github-jesseduffield-rollrus
Version: 0.0~git20190701.dd028cb-4
Severity: serious
X-Debbugs-Cc: z...@debian.org

Fork of golang-github-heroku-rollrus.
No new development in https://github.com/jesseduffield/rollrus since 2019.
No reverse-depends.

Processed: Bug#1032043 marked as pending in pylint

Processing control commands:

> tag -1 pending
Bug #1032043 [src:pylint] pylint: autopkgtest regression
Added tag(s) pending.

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

Bug#1032043: marked as pending in pylint

2023-02-27 Thread Sandro Tosi

Control: tag -1 pending

Hello,

Bug #1032043 in pylint 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/python-team/packages/pylint/-/commit/c32859f7491f0b051fe8e8b56bb131a3d564cc2f


bump b-d on astroid to >= 2.14.2; Closes: #1032043


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1032043

Bug#1032111: Don't release with bookworm

Source: golang-github-jesseduffield-pty
Version: 1.1.3+git20191112.07ed706-2
Severity: serious
X-Debbugs-Cc: z...@debian.org

Fork of golang-github-creack-pty.
No new development in https://github.com/jesseduffield/pty since 2019
No reverse-depends.

Bug#1032109: Don't release with bookworm

Source: golang-github-jesseduffield-gocui
Version: 0.3.0+git20190803.ad0cd60-1
Severity: serious
X-Debbugs-Cc: z...@debian.org

Fork of golang-github-jroimartin-gocui.
No reverse-depends.

Bug#1032108: Don't release with bookworm

Source: golang-github-jesseduffield-asciigraph
Version: 0.4.1+git20190605.6d88e39-3
Severity: serious
X-Debbugs-Cc: z...@debian.org

Fork of golang-github-guptarohit-asciigraph
No new development in https://github.com/jesseduffield/asciigraph since 2019
No reverse-depends.

Bug#1032107: Don't release with bookworm

Source: golang-github-jesseduffield-go-getter
Version: 0.0~git20180822.906e156-5
Severity: serious
X-Debbugs-Cc: z...@debian.org


Fork of golang-github-hashicorp-go-getter.
No new development in https://github.com/jesseduffield/go-getter since 2018
No reverse-depends.

Bug#1032106: Don't release with bookworm

Source: golang-github-hashicorp-terraform-plugin-test
Version: 1.3.0+git20200503.328f99a-3
Severity: serious
X-Debbugs-Cc: z...@debian.org


Upstream repo https://github.com/hashicorp/terraform-plugin-test is archived.
No reverse-depends.

Processed: bug 1032101 is forwarded to https://github.com/strukturag/libheif/pull/759

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

> forwarded 1032101 https://github.com/strukturag/libheif/pull/759
Bug #1032101 [src:libheif] libheif: CVE-2023-0996
Set Bug forwarded-to-address to 
'https://github.com/strukturag/libheif/pull/759'.
> thanks
Stopping processing here.

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

Processed: tagging 1032100, tagging 1032099, tagging 1032101

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

> tags 1032100 + upstream
Bug #1032100 [src:golang-github-hashicorp-go-getter] 
golang-github-hashicorp-go-getter: CVE-2023-0475
Added tag(s) upstream.
> tags 1032099 + upstream
Bug #1032099 [src:libpod] libpod: CVE-2023-0778
Added tag(s) upstream.
> tags 1032101 + upstream
Bug #1032101 [src:libheif] libheif: CVE-2023-0996
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#1029829: amanda: CVE-2022-37704 CVE-2022-37705

2023-02-27 Thread Amanda Trusted

One more pull request added, thanks to Pavel!

From: Amanda Trusted 
Date: Friday, February 24, 2023 at 6:00 PM
To: Jose M Calhariz , 1029...@bugs.debian.org 
<1029...@bugs.debian.org>
Subject: Re: Bug#1029829: amanda: CVE-2022-37704 CVE-2022-37705
Thank you Jose!

We added another fix for CVE-2022-37705.

So, here is the updated list.

[0] CVE - 
https://security-tracker.debian.org/tracker/CVE-2022-37704

https://www.cve.org/CVERecord?id=CVE-2022-37704
Fixes  - 
https://github.com/zmanda/amanda/pull/197,
https://github.com/zmanda/amanda/pull/202,
https://github.com/zmanda/amanda/pull/203,
https://github.com/zmanda/amanda/pull/205/

[1] CVE - 
https://security-tracker.debian.org/tracker/CVE-2022-37705

https://www.cve.org/CVERecord?id=CVE-2022-37705
Fixes - 
https://github.com/zmanda/amanda/pull/196
https://github.com/zmanda/amanda/pull/204/

[2] CVE - 
https://security-tracker.debian.org/tracker/CVE-2022-37703

https://www.cve.org/CVERecord?id=CVE-2022-37703
Fix - 
https://github.com/zmanda/amanda/pull/198

Thank you,
AmandaTrusted.

From: Jose M Calhariz 
Date: Friday, February 24, 20

Bug#1028725: flycheck: FTBFS: make: *** [debian/rules:4: binary] Error 25

2023-02-27 Thread Sergio Durigan Junior

On Monday, February 27 2023, David Bremner wrote:

> Sergio Durigan Junior  writes:
>>
>> I was testing with an upstream build.  For Debian's Emacs, we should
>> use:
>>
>>   buttercup --eval "(setq comp-enable-subr-trampolines nil)" -L .
>>
>
> Did you get that working with the upstream version currently in master
> or with a new upstream snapshot? I tried cherry picking 8379be91 but it
> seemed not to be enough (there was a bunch of conflicts, so maybe I
> missed something).

I backported 8379be91, and it needed manual adjustments to apply
cleanly.  After that, it was enough to solve the other two failures.

Here's the full diff.  If you're OK with it I can upload the package.

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/

diff --git a/debian/changelog b/debian/changelog
index cd3ad07b..30f802ea 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,14 @@
+flycheck (32-2) unstable; urgency=medium
+
+  * Team upload.
+  * d/p/fix-buttercup-tests-on-emacs-28.patch: Adjust tests for Emacs 28.
+  * d/rules: Invoke buttercup disabling subr-trampolines.
+Workaround issue described at
+https://github.com/jorgenschaefer/emacs-buttercup/issues/230.
+(Closes: #1028725)
+
+ -- Sergio Durigan Junior   Mon, 27 Feb 2023 22:17:21 
-0500
+
 flycheck (32-1) unstable; urgency=medium
 
   * new upstream release
diff --git a/debian/patches/fix-buttercup-tests-on-emacs-28.patch 
b/debian/patches/fix-buttercup-tests-on-emacs-28.patch
new file mode 100644
index ..c41e7bff
--- /dev/null
+++ b/debian/patches/fix-buttercup-tests-on-emacs-28.patch
@@ -0,0 +1,58 @@
+From: Philipp Stephani 
+Date: Mon, 6 Dec 2021 16:55:24 +0100
+Subject: Fix Buttercup tests on Emacs 28.
+MIME-Version: 1.0
+Content-Type: text/plain; charset="utf-8"
+Content-Transfer-Encoding: 8bit
+
+- On Emacs 28, Checkdoc has a new customization option
+  ‘checkdoc-column-zero-backslash-before-paren’.
+
+- The header line format is slightly different.
+
+Origin: backport, 
https://github.com/flycheck/flycheck/commit/8fefc5079107cd8f047f2f6cf6e22ff6772a90fe
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028725
+---
+ flycheck.el   | 6 --
+ test/specs/test-error-list.el | 4 +++-
+ 2 files changed, 7 insertions(+), 3 deletions(-)
+
+diff --git a/flycheck.el b/flycheck.el
+index a1298fe..19847dc 100644
+--- a/flycheck.el
 b/flycheck.el
+@@ -8519,7 +8519,7 @@ See Info Node `(elisp)Byte Compilation'."
+ (kill-buffer)))
+ 
+ (defconst flycheck-emacs-lisp-checkdoc-variables
+-  '(checkdoc-symbol-words
++  `(checkdoc-symbol-words
+ checkdoc-arguments-in-order-flag
+ checkdoc-force-history-flag
+ checkdoc-permit-comma-termination-flag
+@@ -8528,7 +8528,9 @@ See Info Node `(elisp)Byte Compilation'."
+ checkdoc-spellcheck-documentation-flag
+ checkdoc-verb-check-experimental-flag
+ checkdoc-max-keyref-before-warn
+-sentence-end-double-space)
++sentence-end-double-space
++,@(and (>= emacs-major-version 28)
++   '(checkdoc-column-zero-backslash-before-paren)))
+   "Variables inherited by the checkdoc subprocess.")
+ 
+ (defun flycheck-emacs-lisp-checkdoc-variables-form ()
+diff --git a/test/specs/test-error-list.el b/test/specs/test-error-list.el
+index 70f132a..226e235 100644
+--- a/test/specs/test-error-list.el
 b/test/specs/test-error-list.el
+@@ -67,7 +67,9 @@
+ (it "has a local header line"
+   (flycheck/with-error-list-buffer
+ (expect header-line-format
+-:to-equal " File  Line Col Level ID Message (Checker) ")
++:to-equal (if (< emacs-major-version 28)
++  " File  Line Col Level ID Message (Checker) "
++" File Line ▼ Col Level ID Message (Checker) "))
+ (expect 'header-line-format :to-be-local
+ 
+   (describe "Columns"
diff --git a/debian/patches/series b/debian/patches/series
index 6603290d..6d1290ed 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -6,3 +6,4 @@ skip-rpmlint-test.patch
 skip-flaky-tests.patch
 python3-in-test.patch
 skip-truncated-stdin-tests.patch
+fix-buttercup-tests-on-emacs-28.patch
diff --git a/debian/rules b/debian/rules
index f298da1f..7e12c97f 100755
--- a/debian/rules
+++ b/debian/rules
@@ -10,6 +10,11 @@ override_dh_installchangelogs:
 override_dh_auto_build:
( cd doc && make OFFLINE=yes html )
 
+# Temporary workaround for
+# https://github.com/jorgenschaefer/emacs-buttercup/issues/230
+override_dh_elpa_test:
+   buttercup --eval '(setq comp-enable-subr-trampolines nil)' -L .
+
 # The file flycheck.html in the _downloads subdir is generated from
 # the old texinfo manual, which is deprecated by upstream.  Don't
 # install it as parts could be out-of-date


signature.asc
Description: PGP signature

Bug#1032104: linux: ppc64el iouring corrupted read

2023-02-27 Thread Daniel Black

Source: linux
Version: 5.10.0-21-powerpc64le
Severity: grave
Justification: causes non-serious data loss
X-Debbugs-Cc: dan...@mariadb.org

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

>From https://jira.mariadb.org/browse/MDEV-30728

MariaDB's mtr tests on a number of specific tests depend on the correct
kernel operation.

As observed in these tests, there is a ~1/5 chance the
encryption.innodb_encryption test will read zeros on the later part of
the 16k pages that InnoDB uses by default.

This affects MariaDB-10.6+ packages where there is a liburing in the
distribution.

This has been observed in the CI of Debian
(https://ci.debian.net/packages/m/mariadb/testing/ppc64el/)
and upstreams https://buildbot.mariadb.org/#/builders/318.
The one ppc64le worker that has the Debian 5.10.0-21 kernel,
the same as the Debian CI, has the prefix ppc64le-db-bbw1-*.

Test faults occur on all MariaDB 10.6+ builds in containers on this kernel.
There a no faults on non-ppc64le or RHEL7/8 based ppc64le kernels.

To reproduce:

apt-get install mariadb-test
cd /usr/share/mysql/mysql-test
./mtr --mysqld=--innodb-flush-method=fsync --mysqld=--innodb-use-native-aio=1 
--vardir=/var/lib/mysql  --force encryption.innodb_encryption,innodb,undo0 
--repeat=12 

A test will frequenty fail.

2023-02-28  1:41:01 0 [ERROR] InnoDB: Database page corruption on disk or a 
failed read of file './ibdata1' page [page id: space=0, page number=282]. You 
may have to recover from a backup.

(the page number isn't predictable)

The complete mtr error log of mariadb server is $PWD/var/log/mysqld.1.err

I tested on tmpfs. This is a different fault from bug #1020831 as:
* there is no iouring error, just a bunch of zeros where data was
  expected.
* this is ppc64le only.

Note, more serious faults exist on overlayfs (MDEV-28751) and remote
filesystems so sticking to local xfs, ext4, btrfs is recommended.

-- System Information:
Debian Release: bullseye
  APT prefers jammy-updates
  APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 'jammy'), 
(100, 'jammy-backports')
Architecture: ppc64el (ppc64le)

Kernel: Linux 5.10.0-21-powerpc64le (SMP w/128 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Processed: Re: qemu: qemu-img and qemu-system-s390x hang on s390x

Processing control commands:

> block -1 by 1031753
Bug #1030545 [src:qemu] qemu: qemu-img and qemu-system-s390x hang on s390x
1030545 was not blocked by any bugs.
1030545 was not blocking any bugs.
Added blocking bug(s) of 1030545: 1031753

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

Bug#1030545: qemu: qemu-img and qemu-system-s390x hang on s390x

Source: qemu
Followup-For: Bug #1030545
Control: block -1 by 1031753

Bug#1032013: Handling of -e violates policy for x-terminal-emulator

2023-02-27 Thread John Crawley


Hello Louis-Philippe,
thank you for fixing the bug.
As far as I can tell, the -e option is now handled correctly by terminator when 
invoked as x-terminal-emulator.

Just for the record, I may be misunderstanding the Debian Policy [1], but:
1) neither -c nor --execute are mentioned, only -e.
2) command lines like
x-terminal-emulator -e 'if this; then that; fi'
*should not* work, any more than 'if this; then that; fi' would work in an 
actual terminal.
The outer quotes would make the whole line into a single argument, but an 
executable is required as the first word. Such commands do work on some 
terminals, but I don't think Debian Policy expects that:

" may be *multiple* arguments, which form the argument list to the executed 
program"

So this should work (and now does):
x-terminal-emulator -e sh -c 'if this; then that; fi'

Thanks again!

[1] 
https://www.debian.org/doc/debian-policy/ch-customized-programs.html#packages-providing-a-terminal-emulator
--
John

Bug#1028743: python-bottle: FTBFS: AssertionError: b'OK' != "URLError(ConnectionRefusedError(111, 'Connection refused'))"

Source: python-bottle
Followup-For: Bug #1028743
Control: forwarded -1 https://github.com/bottlepy/bottle/issues/1410

Processed: Re: python-bottle: FTBFS: AssertionError: b'OK' != "URLError(ConnectionRefusedError(111, 'Connection refused'))"

Processing control commands:

> forwarded -1 https://github.com/bottlepy/bottle/issues/1410
Bug #1028743 [src:python-bottle] python-bottle: FTBFS: AssertionError: b'OK' != 
"URLError(ConnectionRefusedError(111, 'Connection refused'))"
Set Bug forwarded-to-address to 
'https://github.com/bottlepy/bottle/issues/1410'.

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

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

Package: nodejs
Followup-For: Bug #1030284
X-Debbugs-Cc: t...@debian.org

> My plan is to rebuild / retest reverse deps before hard freeze.

That's a good plan.

Do you know whether any of those tests include cases that spin up large (as in:
may consume more than 50% of a system's memory) numbers of processes/threads?

Context: I've begun worrying about the additional overhead from stack
preallocation -- where increasing the stack size might significantly reduce the
number of processes that fit in memory while running simultaneously.

> Thanks, I'll welcome any patch to start with.

FWIW: I am still somewhere between 'do nothing' and 'ok, maybe, after seeing
more data that it is a safe increase'.

I don't trust myself enough to write any logic/syscall-related changes in a
patch but may provide one that updates the constant limits in the relevant
header file(s).

Thorsten: if you'd like an rlimit-based approach then I think that may be upon
you to write, or to request from upstream (where I accidentally impersonated
you on the GitHub issue, by the way - sorry about that!).

Bug#1028725: flycheck: FTBFS: make: *** [debian/rules:4: binary] Error 25

2023-02-27 Thread David Bremner

Sergio Durigan Junior  writes:
>
> I was testing with an upstream build.  For Debian's Emacs, we should
> use:
>
>   buttercup --eval "(setq comp-enable-subr-trampolines nil)" -L .
>

Did you get that working with the upstream version currently in master
or with a new upstream snapshot? I tried cherry picking 8379be91 but it
seemed not to be enough (there was a bunch of conflicts, so maybe I
missed something).

d

Bug#1030284: [Pkg-javascript-devel] Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

2023-02-27 Thread Jérémy Lal

Le mar. 28 févr. 2023 à 00:33, James Addison  a écrit :

> Package: nodejs
> Followup-For: Bug #1030284
> X-Debbugs-Cc: t...@debian.org,
> reply+aagshfqluldiwi3obwdg6lgb7if7fevbnhheauz...@reply.github.com
>
> mirabilos gesagt:
>
> > We know the default ulimits for users in Debian, and they are higher
> > than the 1 MiB assumed by v8, by quite some factor, so this won’t break
> > things which are not currently broken (by that exception). This will do
> > for the release I think.
>
> Relaying my understanding of this, so far:
>
> An increase in the V8 stack size should not cause earlier-process-exits
> for any
> processes that previously ran on Debian systems where the
> architecture-default-or-greater stack size is configured[1].
>
> In other words: the same-number-or-greater of JavaScript processes should
> continue to run on any given Debian system where the configured stack size
> is
> greater-than-or-equal to the architecture's default, after the V8 stack
> size
> limit is increased.
>
> And we expect that it should repair a failing reproducible build test for
> at
> least one Debian package on arm64.


Thanks, I'll welcome any patch to start with.
My plan is to rebuild / retest reverse deps before hard freeze.

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

Package: nodejs
Followup-For: Bug #1030284
X-Debbugs-Cc: t...@debian.org, 
reply+aagshfqluldiwi3obwdg6lgb7if7fevbnhheauz...@reply.github.com

mirabilos gesagt:

> We know the default ulimits for users in Debian, and they are higher
> than the 1 MiB assumed by v8, by quite some factor, so this won’t break
> things which are not currently broken (by that exception). This will do
> for the release I think.

Relaying my understanding of this, so far:

An increase in the V8 stack size should not cause earlier-process-exits for any
processes that previously ran on Debian systems where the
architecture-default-or-greater stack size is configured[1].

In other words: the same-number-or-greater of JavaScript processes should
continue to run on any given Debian system where the configured stack size is
greater-than-or-equal to the architecture's default, after the V8 stack size
limit is increased.

And we expect that it should repair a failing reproducible build test for at
least one Debian package on arm64.

[1] - see limits.conf

Processed: Apparent s390x kernel bug

Processing control commands:

> tags -1 + pending
Bug #1030511 [src:libguestfs] libguestfs: FTBFS on s390x: timeout
Added tag(s) pending.
> block -1 by 1031753
Bug #1030511 [src:libguestfs] libguestfs: FTBFS on s390x: timeout
1030511 was not blocked by any bugs.
1030511 was not blocking any bugs.
Added blocking bug(s) of 1030511: 1031753

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

Bug#1030511: Apparent s390x kernel bug

2023-02-27 Thread Hilko Bengen

Control: tags -1 + pending
Control: block -1 by 1031753

The hangs manifest in qemu-img, but according to #1030545, the root
cause seems to be an s390x-specific kernel bug which has been described
in #1031753.

Bug#1031923: d-i.debian.org: testing (bookworm): Unable to boot due to unsupported FEATURE_C12 in e2fsck

2023-02-27 Thread Cyril Brulebois

Hi,

Cesar Enrique Garcia Dabo  (2023-02-27):
> Thank you for the answer. Good to know that it is a known issue and is being
> taken care of.
> 
> Regarding why I took that image. I just followed the official Debian
> webpages:
> 
> https://www.debian.org/CD/http-ftp/index.en.html

Many thanks for the follow-up…

> From there I clicked on "Official CD/DVD images of the "testing"
> distribution (/regenerated weekly/)
> "
> 
> https://cdimage.debian.org/cdimage/weekly-builds/ -> amd64 -> iso-cd -> 
> https://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-netinst.iso
> 
> So from my perspective I wasn't using a "random" image, but rather an
> official one, as the web pages indicate.

… now I understand what you went through.

Unfortunately, I wasn't aware of those instructions, and that looks utterly
buggy. How can we claim to publish “official images” that are snapshots, built
using debian-installer daily builds, that can be broken by random packages in
unstable, and left unfixed for weeks?!

We already have specific instructions on the d-i page[1] regarding
*actual* official releases (as soon as testing gets an Alpha 1), plus
snapshots. My first instinct would be to entirely scrap testing-related
things from the page you started from[2], and just redirect to [1]
instead.

 1. https://www.debian.org/devel/debian-installer/
 2. https://www.debian.org/CD/http-ftp/


That link should be updated too… http://debian-cd.debian.net/


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


signature.asc
Description: PGP signature

Bug#1031923: d-i.debian.org: testing (bookworm): Unable to boot due to unsupported FEATURE_C12 in e2fsck

2023-02-27 Thread Cesar Enrique Garcia Dabo

Thank you for the answer. Good to know that it is a known issue and is
being taken care of.

Regarding why I took that image. I just followed the official Debian
webpages:

https://www.debian.org/CD/http-ftp/index.en.html

From there I clicked on "Official CD/DVD images of the "testing"
distribution (/regenerated weekly/)
"

https://cdimage.debian.org/cdimage/weekly-builds/ -> amd64 -> iso-cd ->
https://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-netinst.iso

So from my perspective I wasn't using a "random" image, but rather an
official one, as the web pages indicate.

Best regards,

Hi,

Andrew, please use reply-all, to reply to the bug and to the bug
submitter. A list-only reply doesn't quite help…

Andrew M.A. Cater (2023-02-25):

I have installed Debian testing (bookworm) from one of the latest ISO images
(https://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-
amd64-netinst.iso from 2023-02-21) and after an apparently succesfull
installation the system cannot be booted.

Enrique, thanks for the report.

We've published an official release one week ago. I'm not sure why
you're not using that instead of a random weekly build.

This is a known issue - try using the Alpha 2 installer in which this
issue is not present.

The e2fsprogs mismatch with grub is likely to be fixed by reverting
problematic versions.

No, the problem here is that e2fsck is from testing, while the
filesystem has been created by mke2fs from unstable, and the former
doesn't know about a new feature turned on by the latter.

Cheers,

Bug#1032101: libheif: CVE-2023-0996

2023-02-27 Thread Moritz Mühlenhoff

Source: libheif
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for libheif.

CVE-2023-0996[0]:
| There is a vulnerability in the strided image data parsing code in the
| emscripten wrapper for libheif. An attacker could exploit this through
| a crafted image file to cause a buffer overflow in linear memory
| during a memcpy call.

https://github.com/strukturag/libheif/pull/759
https://govtech-csg.github.io/security-advisories/2023/02/24/CVE-2023-0996.html


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-0996
https://www.cve.org/CVERecord?id=CVE-2023-0996

Please adjust the affected versions in the BTS as needed.

Bug#1030906: marked as done (taurus-pyqtgraph: FTBFS (failing tests))

Your message dated Mon, 27 Feb 2023 22:05:40 +
with message-id 
and subject line Bug#1030906: fixed in taurus-pyqtgraph 0.5.9-2
has caused the Debian Bug report #1030906,
regarding taurus-pyqtgraph: FTBFS (failing tests)
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.)


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

Package: src:taurus-pyqtgraph
Version: 0.5.9-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary-indep
dh binary-indep --with python3 --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:240: python3.11 setup.py config
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:240: /usr/bin/python3 setup.py build
running build
running build_py
creating 
/<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph
copying taurus_pyqtgraph/datainspectortool.py -> 
/<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph
copying taurus_pyqtgraph/autopantool.py -> 
/<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph
copying taurus_pyqtgraph/buffersizetool.py -> 
/<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph
copying taurus_pyqtgraph/dateaxisitem.py -> 
/<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph
copying taurus_pyqtgraph/taurustrendset.py -> 
/<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph
copying taurus_pyqtgraph/plot.py -> 
/<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph
copying taurus_pyqtgraph/forcedreadtool.py -> 
/<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph
copying taurus_pyqtgraph/y2axis.py -> 
/<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph
copying taurus_pyqtgraph/curvesmodel.py -> 
/<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph
copying taurus_pyqtgraph/curveproperties.py -> 
/<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph
copying taurus_pyqtgraph/taurusimageitem.py -> 
/<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph
copying taurus_pyqtgraph/__init__.py -> 
/<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph
copying taurus_pyqtgraph/trend.py -> 
/<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph
copying taurus_pyqtgraph/curvespropertiestool.py -> 
/<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph
copying taurus_pyqtgraph/taurusmodelchoosertool.py -> 
/<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph
copying taurus_pyqtgraph/util.py -> 
/<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph
copying taurus_pyqtgraph/taurusplotdataitem.py -> 
/<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph
copying taurus_pyqtgraph/cli.py -> 
/<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph
copying taurus_pyqtgraph/legendtool.py -> 
/<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph
creating 
/<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph/examples
copying taurus_pyqtgraph/examples/legendExample.py -> 
/<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph/examples
copying taurus_pyqtgraph/examples/taurustrendset.py -> 
/<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph/examples
copying taurus_pyqtgraph/examples/axislabels.py -> 
/<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph/examples
copying taurus_pyqtgraph/examples/y2axis.py -> 
/<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph/examples
copying taurus_pyqtgraph/examples/__init__.py -> 
/<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph/examples
copying taurus_pyqtgraph/examples/taurusplotdataitem.py -> 
/<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph/examples
running egg_info
creating taurus_pyqtgraph.egg-info
writing taurus_pyqtgraph.egg-info/PKG-INFO
writing dependency_links to taurus_pyqtgraph.egg-info/dependency_links.txt
writing entry points to taurus_pyqtgraph.egg-info/entry_points.txt
writing requirements to taurus_pyqtgraph.egg-info/requires.txt
writing top-level names to taurus_pyqtgraph.egg-info/top_level.txt
writing manifest file 'taurus_pyqtgraph.egg-info/SOURCES.txt'
reading m

Bug#1031371: closing 1031371

2023-02-27 Thread Salvatore Bonaccorso

close 1031371 7.74.0-1.3+deb11u7
thanks

Processed: closing 1031371

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

> close 1031371 7.74.0-1.3+deb11u7
Bug #1031371 {Done: Samuel Henrique } [src:curl] curl: 
CVE-2023-23914 CVE-2023-23915 CVE-2023-23916
The source 'curl' and version '7.74.0-1.3+deb11u7' do not appear to match any 
binary packages
Marked as fixed in versions curl/7.74.0-1.3+deb11u7.
Bug #1031371 {Done: Samuel Henrique } [src:curl] curl: 
CVE-2023-23914 CVE-2023-23915 CVE-2023-23916
Bug 1031371 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

Bug#1011689: marked as done (libspring-java: FTBFS: XmlBeansMarshaller.java:33: error: cannot find symbol)

Your message dated Mon, 27 Feb 2023 21:20:12 +
with message-id 
and subject line Bug#1011689: fixed in libspring-java 4.3.30-2
has caused the Debian Bug report #1011689,
regarding libspring-java: FTBFS: XmlBeansMarshaller.java:33: error: cannot find 
symbol
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.)


-- 
1011689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011689
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libspring-java
Version: 4.3.30-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 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_auto_build -- jar -x test -x check \
>  -x :spring-orm-hibernate4:compileJava \
>  -x :spring-orm-hibernate5:compileJava \
>  -x :spring-instrument-tomcat:compileJava \
>  -x :spring-webmvc-tiles2:compileJava \
>  -x :spring-websocket:compileJava
>   mkdir -p .gradle/init.d
>   cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/
>   gradle --info --console plain --offline --stacktrace --no-daemon 
> --refresh-dependencies --gradle-user-home .gradle -Duser.home=. 
> -Duser.name=debian -Ddebian.package=libspring-java -Dfile.encoding=UTF-8 
> --parallel --max-workers=8 jar -x test -x check -x 
> :spring-orm-hibernate4:compileJava -x :spring-orm-hibernate5:compileJava -x 
> :spring-instrument-tomcat:compileJava -x :spring-webmvc-tiles2:compileJava -x 
> :spring-websocket:compileJava
> Initialized native services in: /<>/.gradle/native
> To honour the JVM settings for this build a new JVM will be forked. Please 
> consider using the daemon: 
> https://docs.gradle.org/4.4.1/userguide/gradle_daemon.html.
> Starting process 'Gradle build daemon'. Working directory: 
> /<>/.gradle/daemon/4.4.1 Command: 
> /usr/lib/jvm/java-11-openjdk-amd64/bin/java 
> -Xbootclasspath/a:/usr/share/java/gradle-helper-hook.jar:/usr/share/java/maven-repo-helper.jar
>  --add-opens java.base/java.lang=ALL-UNNAMED -Dfile.encoding=UTF-8 
> -Duser.country -Duser.language=en -Duser.variant -cp 
> /usr/share/gradle/lib/gradle-launcher-4.4.1.jar 
> org.gradle.launcher.daemon.bootstrap.GradleDaemon 4.4.1
> Successfully started process 'Gradle build daemon'
> An attempt to start the daemon took 0.771 secs.
> The client will now receive all logging from the daemon (pid: 701662). The 
> daemon log file: /<>/.gradle/daemon/4.4.1/daemon-701662.out.log
> Daemon will be stopped at the end of the build stopping after processing
> Closing daemon's stdin at end of input.
> The daemon will no longer process any standard input.
> Using 8 worker leases.
> Creating new cache for fileHashes, path 
> /<>/.gradle/caches/4.4.1/fileHashes/fileHashes.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@42378b33
> Creating new cache for resourceHashesCache, path 
> /<>/.gradle/caches/4.4.1/fileHashes/resourceHashesCache.bin, 
> access org.gradle.cache.internal.DefaultCacheAccess@42378b33
> Creating new cache for fileHashes, path 
> /<>/.gradle/4.4.1/fileHashes/fileHashes.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@764d9ae6
> Starting Build
> Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
> using SubsetScriptTransformer.
> Creating new cache for metadata-1.1/results, path 
> /<>/.gradle/caches/transforms-1/metadata-1.1/results.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@5e81fdfa
> Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
> using BuildScriptTransformer.
> Generating JAR file: 
> /<>/.gradle/caches/4.4.1/generated-gradle-jars/gradle-api-4.4.1.jar
> Generating JAR file 'gradle-api-4.4.1.jar'
>   Keep-alive timer started
>   Adding Debian repository to project 'buildSrc'
> Parallel execution is an incubating feature.
> Evaluating project ':buildSrc' using build file 
> '/<>/buildSrc/build.gradle'.
>   Adding Maven pom generation to project 'buildSrc'
>   Linking the generated javadoc to the system JDK API documentation
> Selected primary task 'clean' from project :
> Selected primary task 'build' from project :
> Creating new cache for annotation-processors, path 
> /<>/buildSrc/.gradle/4.4.1/fileContent/annotation-processors.bin,
>  access org.gradle.cache.internal.DefaultCacheAccess@1d70ea5
> Creating new cache for resourceHashesCache, path 
> /<>/.gradle/4.4.1/fileHashes/resourceHashesCache.bin, access 
> org.grad

Bug#1030906: taurus-pyqtgraph: FTBFS (failing tests)

2023-02-27 Thread Étienne Mollier

Hi s3v,

Thank you for the hints on taurus-pyqtgraph affected by #1030906
in Debian.  I could devise on patches to bring it back into
working conditions for bookworm; an upload will follow shortly.

Have a nice day,  :)
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/5, please excuse my verbosity.


signature.asc
Description: PGP signature

Processed: tagging 1032092

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

> tags 1032092 + upstream
Bug #1032092 [src:asterisk] asterisk: CVE-2022-23537 CVE-2022-23547 
CVE-2022-39269
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Processed: tagging 1032091

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

> tags 1032091 + upstream
Bug #1032091 [src:py7zr] py7zr: CVE-2022-44900
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#994758: Bug#1031927: Handling the libsgutils2-2 #994758 bookworm-ignore

2023-02-27 Thread Paul Gevers


Control: tags 994758 - bookworm-ignore

Hi Adrian,

Thanks for caring.

On 25-02-2023 14:30, Adrian Bunk wrote:
With the bookworm-ignore for #994758, 


I'll admit that I misjudged that bug; with this message I'll clear the 
bookworm-ignore tag.



bullseye and bookworm
will ship libsgutils2-2 packages with different so-name.


Although the transition freeze has started long time ago, it seems that 
doing a proper transition is the best way to fix this issue. If somebody 
is up to the task to prepare the upload, we can ask ftp-master to 
process the upload swiftly. (Please upload to experimental to avoid the 
ftp-master from rejecting the package immediately and to enable 
reviewing if that's not done before the upload.)


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: Bug#1031927: Handling the libsgutils2-2 #994758 bookworm-ignore

Processing control commands:

> tags 994758 - bookworm-ignore
Bug #994758 [libsgutils2-2] Soname change without package name change
Ignoring request to alter tags of bug #994758 to the same tags previously set

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

Processed: Re: Bug#1031927: Handling the libsgutils2-2 #994758 bookworm-ignore

Processing control commands:

> tags 994758 - bookworm-ignore
Bug #994758 [libsgutils2-2] Soname change without package name change
Removed tag(s) bookworm-ignore.

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

Processed: severity of 1009035 is grave

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

> severity 1009035 grave
Bug #1009035 [src:ruby-asciidoctor-include-ext] ruby-asciidoctor-include-ext: 
CVE-2022-24803 - Command Injection vulnerability
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Processed: retitle 1032091 to py7zr: CVE-2022-44900

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

> retitle 1032091 py7zr: CVE-2022-44900
Bug #1032091 [src:py7zr] py7zr: CVE-2022-40152
Changed Bug title to 'py7zr: CVE-2022-44900' from 'py7zr: CVE-2022-40152'.
> thanks
Stopping processing here.

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

Bug#1032092: asterisk: CVE-2022-23537 CVE-2022-23547 CVE-2022-39269

2023-02-27 Thread Moritz Mühlenhoff

Source: asterisk
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for asterisk.

CVE-2022-23537[0]:
| PJSIP is a free and open source multimedia communication library
| written in C language implementing standard based protocols such as
| SIP, SDP, RTP, STUN, TURN, and ICE. Buffer overread is possible when
| parsing a specially crafted STUN message with unknown attribute. The
| vulnerability affects applications that uses STUN including PJNATH and
| PJSUA-LIB. The patch is available as a commit in the master branch
| (2.13.1).

https://github.com/pjsip/pjproject/security/advisories/GHSA-9pfh-r8x4-w26w
https://github.com/pjsip/pjproject/commit/d8440f4d711a654b511f50f79c0445b26f9dd1e1

CVE-2022-23547[1]:
| PJSIP is a free and open source multimedia communication library
| written in C language implementing standard based protocols such as
| SIP, SDP, RTP, STUN, TURN, and ICE. This issue is similar to
| GHSA-9pfh-r8x4-w26w. Possible buffer overread when parsing a certain
| STUN message. The vulnerability affects applications that uses STUN
| including PJNATH and PJSUA-LIB. The patch is available as commit in
| the master branch.

https://github.com/pjsip/pjproject/security/advisories/GHSA-9pfh-r8x4-w26w
https://github.com/pjsip/pjproject/commit/d8440f4d711a654b511f50f79c0445b26f9dd1e1
https://github.com/pjsip/pjproject/security/advisories/GHSA-cxwq-5g9x-x7fr
https://github.com/pjsip/pjproject/commit/bc4812d31a67d5e2f973fbfaf950d6118226cf36

CVE-2022-39269[2]:
| PJSIP is a free and open source multimedia communication library
| written in C. When processing certain packets, PJSIP may incorrectly
| switch from using SRTP media transport to using basic RTP upon SRTP
| restart, causing the media to be sent insecurely. The vulnerability
| impacts all PJSIP users that use SRTP. The patch is available as
| commit d2acb9a in the master branch of the project and will be
| included in version 2.13. Users are advised to manually patch or to
| upgrade. There are no known workarounds for this vulnerability.

https://github.com/pjsip/pjproject/security/advisories/GHSA-wx5m-cj97-4wwg
https://github.com/pjsip/pjproject/commit/d2acb9af4e27b5ba75d658690406cec9c274c5cc


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-23537
https://www.cve.org/CVERecord?id=CVE-2022-23537
[1] https://security-tracker.debian.org/tracker/CVE-2022-23547
https://www.cve.org/CVERecord?id=CVE-2022-23547
[2] https://security-tracker.debian.org/tracker/CVE-2022-39269
https://www.cve.org/CVERecord?id=CVE-2022-39269

Please adjust the affected versions in the BTS as needed.

Bug#1032091: py7zr: CVE-2022-40152

2023-02-27 Thread Moritz Mühlenhoff

Source: py7zr
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for py7zr.

CVE-2022-40152[0]:
| Those using Woodstox to parse XML data may be vulnerable to Denial of
| Service attacks (DOS) if DTD support is enabled. If the parser is
| running on user supplied input, an attacker may supply content that
| causes the parser to crash by stackoverflow. This effect may support a
| denial of service attack.

https://github.com/miurahr/py7zr/commit/1bb43f17515c7f69673a1c88ab9cc72a7bbef406
 (v0.20.1)
https://lessonsec.com/cve/cve-2022-44900/


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-2022-40152
https://www.cve.org/CVERecord?id=CVE-2022-40152

Please adjust the affected versions in the BTS as needed.

Bug#1032086: Don't include in Bookworm

2023-02-27 Thread Moritz Muehlenhoff

Source: golang-github-labstack-echo.v3
Version: 3.3.10-2
Severity: serious

This is an older version of src:golang-github-labstack-echo. None of the
reverse deps are currently in bookworm, so golang-github-labstack-echo.v3
should be dropped as well (and post freeze the reverse deps fixed and
the package removed)

Bug#1032085: Don't include in Bookworm

2023-02-27 Thread Moritz Muehlenhoff

Source: golang-github-labstack-echo.v2
Version: 2.2.0-3
Severity: serious

This is an older version of src:golang-github-labstack-echo. None of the
reverse deps are currently in bookworm, so golang-github-labstack-echo.v2
should be dropped as well (and post freeze the reverse deps fixed and
the package removed)

Bug#1031672: marked as done (collectd-core: lost its .service / init script)

Your message dated Mon, 27 Feb 2023 20:18:38 +0100
with message-id <20230227191838.e52x6kc3fhnbb...@percival.namespace.at>
and subject line Bug#1031672: Fixed in collected 5.12.0-14
has caused the Debian Bug report #1031672,
regarding collectd-core: lost its .service / init 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.)


-- 
1031672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031672
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: collectd-core
Version: 5.12.0-13
Severity: serious
Tags: patch

Hi BZ and friends,

Looks like a change in dh_installinit / dh_installsystemd made the package
loose its systemd service / init.d script.

The attached patch fixes the situation. If you have no time to build and
upload, just shoot me a mail and I'll push the fix to unstable (and to the
git since it's in the debian namespace).

Cheers,

Thomas Goirand (zigo)
diff -Nru collectd-5.12.0/debian/changelog collectd-5.12.0/debian/changelog
--- collectd-5.12.0/debian/changelog2023-01-27 09:08:10.0 +0100
+++ collectd-5.12.0/debian/changelog2023-02-20 10:05:23.0 +0100
@@ -1,3 +1,9 @@
+collectd (5.12.0-13.1) unstable; urgency=medium
+
+  * Fix installing systemd service and init script.
+
+ -- Thomas Goirand   Mon, 20 Feb 2023 10:05:23 +0100
+
 collectd (5.12.0-13) unstable; urgency=medium
 
   * [694f2c9] Revert "Disable nut plugin again."
diff -Nru collectd-5.12.0/debian/rules collectd-5.12.0/debian/rules
--- collectd-5.12.0/debian/rules2023-01-27 09:08:10.0 +0100
+++ collectd-5.12.0/debian/rules2023-02-20 10:05:19.0 +0100
@@ -340,3 +340,8 @@
| sed -e 's/shlibs:Suggests/shlibs:Recommends/' \
>> debian/collectd.substvars
 
+override_dh_installsystemd:
+   dh_installsystemd -pcollectd-core --name=collectd
+
+override_dh_installinit:
+   dh_installinit -pcollectd-core --name=collectd
--- End Message ---
--- Begin Message ---
Source: collectd
Source-Version: 5.12.0-14
Done: Bernd Zeimetz 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 20 Feb 2023 13:55:26 +0100
Source: collectd
Architecture: source
Version: 5.12.0-14
Distribution: unstable
Urgency: medium
Maintainer: Collectd Packaging Team 
Changed-By: Bernd Zeimetz 
Changes:
 collectd (5.12.0-14) unstable; urgency=medium
 .
   * [aa8f170] Fix installing systemd service and init script.
 Closes: ##1031672
 Thanks to Thomas Goirand
Checksums-Sha1:
 2468e0ec8b39c6a80393ad2532827b05bb5f266a 4188 collectd_5.12.0-14.dsc
 b78277bee7e55d5a58da9d75a8d1eab9de3ef733 80820 collectd_5.12.0-14.debian.tar.xz
 1cb4ce405744af9b1ccf51fb551af2270cea913e 28574 
collectd_5.12.0-14_source.buildinfo
Checksums-Sha256:
 5a0d5cd61b6b69fa6b7a6f41123611f5020eb82cdd0bb583127379edfb00629f 4188 
collectd_5.12.0-14.dsc
 242f3914a733d34f0ba14af9e2d7f6c884671374e413a836896d1e761587a563 80820 
collectd_5.12.0-14.debian.tar.xz
 3162205c23cda04bce8bf4d6323f769f7fc3ff2aa92bff7391193dbf54eb95ee 28574 
collectd_5.12.0-14_source.buildinfo
Files:
 71a8aad07048da887a0bb8a430054d6c 4188 utils optional collectd_5.12.0-14.dsc
 aa4d876844a2f1b10dbc9033cfdd0990 80820 utils optional 
collectd_5.12.0-14.debian.tar.xz
 0d801c1b77739157e1100d312fb9f660 28574 utils optional 
collectd_5.12.0-14_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE7KHj8o4RJDLUhd2V6zYXGm/5Q18FAmPzcNYACgkQ6zYXGm/5
Q1/uEw//XyfihE1yJs8+PKZGGH9aEHYlxlh7ATBgTrHjNIGZ9Tm/PLaXIIPCsoyd
d+dBUrU9OEfwPct4M33nI8rAt/ltOX19FmClhkXhTPPGpDtCG/7puUn14rbZegmK
fYND/LAybianfGYvJSQpArNR0mzFEOqyE0ioPfmKJHQejM6XWNlsZq3EgHoOHrXv
u6hCRPIGrspGbFEjm3J0eVe8wfTkdAKYppIHZ4HvRh+js/E+ucJTaW29fpi5nSVZ
h7LNW871sfoxdLJ7evjKilXuyhTd2D0wk6Kv11oFfXbeKpTSwp+ouVsXteRf9gAV
rc262Oy0qM8RDGO1D353K5VxjbnEcXXwVU0GLp/8OYpfYaJm2ePlvveK/1Sp06ju
r7TAfidcwUgupiIVdVGKb/lz2NNXjDaTgEEkLcglL9oAFmuDwkG33hNPbbB7K/7z
mOD7/wHbBr3oRlcF7kYIaJRPM/2cPPkY2H5Oo+waMXgoucv2Q/WMg2ezPbuyIVqk
pDhtJkjcXCKCCfpdiEz2918G2/WtWACh9NkiYsolA+S+X+U8Mfe2jCC9oOSjhoTV
Wzukh1QMHqwl9WkDAkoWSRwJ8xq0Q/Ws23Cl42X3vaFLWvm7Ygs8gBENiIMAm+SE
ZYqJC1t8/wFAuHWHt6Wfo+/CBDfj1cILIyh630vKw0fI8Bo3zi8=
=neN0
-END PGP SIGNATURE End Message ---

Bug#1017937: marked as done (dislocker misbuilds in a build environment that's usrmerge'd)

Your message dated Mon, 27 Feb 2023 19:19:03 +
with message-id 
and subject line Bug#1017937: fixed in dislocker 0.7.3-3
has caused the Debian Bug report #1017937,
regarding dislocker misbuilds in a build environment that's usrmerge'd
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.)


-- 
1017937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017937
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dislocker
Version: 0.7.3-2.1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic ubuntu-patch

Hi Giovani,

dislocker is failing to build in Ubuntu because the Ubuntu autobuilder
environments are all "usrmerge" environments, where the /lib* directories
have all been moved to /usr and /lib* are just symlinks.

The consequence of this is that on architectures where the dynamic linker
has a path of /lib64/*, these files are now in /usr/lib64, and the existence
of this directory causes dislocker's upstream build system to misbuild,
trying to install the libraries to this target simply because this directory
exists.

This is wrong for multiple reasons, but the most immediately relevant is
that it simply causes the package to fail to build.

Please find attached a patch which corrects this issue.

Thanks for considering,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru dislocker-0.7.3/debian/patches/series 
dislocker-0.7.3/debian/patches/series
--- dislocker-0.7.3/debian/patches/series   2022-02-26 07:29:05.0 
-0800
+++ dislocker-0.7.3/debian/patches/series   2022-08-22 09:02:45.0 
-0700
@@ -1,2 +1,3 @@
 fix-spelling.patch
 fix-ruby3.0.patch
+wrong-libdir.patch
diff -Nru dislocker-0.7.3/debian/patches/wrong-libdir.patch 
dislocker-0.7.3/debian/patches/wrong-libdir.patch
--- dislocker-0.7.3/debian/patches/wrong-libdir.patch   1969-12-31 
16:00:00.0 -0800
+++ dislocker-0.7.3/debian/patches/wrong-libdir.patch   2022-08-22 
09:06:12.0 -0700
@@ -0,0 +1,27 @@
+Description: don't install to /usr/lib64 just because it exists in build env
+ This package fails to build in Ubuntu but not in Debian because Ubuntu is
+ using usrmerge in its build environment, which causes /usr/lib64 to exist
+ and the upstream build system to wrongly install files to it instead of to
+ /usr/lib.  Patch the build system to never use /usr/lib64 as this is always
+ wrong for a Debian package.
+Author: Steve Langasek 
+Last-Update: 2022-08-22
+Forwarded: no
+
+Index: dislocker-0.7.3/src/CMakeLists.txt
+===
+--- dislocker-0.7.3.orig/src/CMakeLists.txt
 dislocker-0.7.3/src/CMakeLists.txt
+@@ -154,11 +154,7 @@
+ 
+ if(NOT DEFINED LIB_INSTALL_DIR)
+   if(NOT DEFINED libdir)
+-  if(IS_DIRECTORY "${CMAKE_INSTALL_PREFIX}/lib64")
+-  set(libdir "${CMAKE_INSTALL_PREFIX}/lib64")
+-  else()
+-  set(libdir "${CMAKE_INSTALL_PREFIX}/lib")
+-  endif()
++  set(libdir "${CMAKE_INSTALL_PREFIX}/lib")
+   endif()
+ else()
+   set(libdir ${LIB_INSTALL_DIR})
--- End Message ---
--- Begin Message ---
Source: dislocker
Source-Version: 0.7.3-3
Done: Joao Eriberto Mota Filho 

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

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated dislocker 
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, 27 Feb 2023 14:51:20 -0300
Source: dislocker
Architecture: source
Version: 0.7.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Joao Eriberto Mota Filho 
Closes: 1017937
Changes:
 dislocker (0.7.3-3) unstable; urgency=medium
 .
   * Team uplo

Bug#1024589: marked as done (dislocker: FTBFS with ruby3.1: mv: cannot stat '/<>/debian/tmp/usr/lib/libdislocker*': No such file or directory)

Your message dated Mon, 27 Feb 2023 19:19:03 +
with message-id 
and subject line Bug#1017937: fixed in dislocker 0.7.3-3
has caused the Debian Bug report #1017937,
regarding dislocker: FTBFS with ruby3.1: mv: cannot stat 
'/<>/debian/tmp/usr/lib/libdislocker*': No such file or directory
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.)


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

Source: dislocker
Version: 0.7.3-2.1
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User:debian-r...@lists.debian.org
Usertags: ruby3.1

Hi,

We are about to start the ruby3.1 transition in unstable. While trying to
rebuild dislocker with ruby3.1 enabled, the build failed.

Relevant part of the build log (hopefully):

   debian/rules override_dh_install-arch
make[1]: Entering directory '/<>'
dh_install
mv /<>/debian/tmp/usr/lib/libdislocker* \
   /<>/debian/libdislocker0.7/usr/lib/
mv: cannot stat '/<>/debian/tmp/usr/lib/libdislocker*': No such 
file or directory
make[1]: *** [debian/rules:16: override_dh_install-arch] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:12: binary] Error 2

The full build log is available from:

https://people.debian.org/~kanashiro/ruby3.1/20/dislocker/dislocker_0.7.3-2.1+rebuild1667925374_amd64-2022-11-08T16:36:15Z.build

To reproduce this, you need ruby-all-dev >= 1:3.1~0.  Depending on when you
read this, this might mean installing ruby-all-dev from experimental, or if the
transition has already started in unstable, a normal build on unstable should
do it.  If you fail to reproduce, please provide a build log and diff it with
mine so that we can identify if something relevant changed in the meantime.

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. Seehttps://www.debian.org/Bugs/server-control#affects

--
Lucas Kanashiro
--- End Message ---
--- Begin Message ---
Source: dislocker
Source-Version: 0.7.3-3
Done: Joao Eriberto Mota Filho 

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

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated dislocker 
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, 27 Feb 2023 14:51:20 -0300
Source: dislocker
Architecture: source
Version: 0.7.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Joao Eriberto Mota Filho 
Closes: 1017937
Changes:
 dislocker (0.7.3-3) unstable; urgency=medium
 .
   * Team upload.
   * debian/patches/wrong-libdir.patch: created to fix a FTBFS on a
 build environment that's usrmerge'd. Thanks to Steve Langasek
 . (Closes: #1017937)
Checksums-Sha1:
 65ed35ef236782a09044f52e15b711c20b5881dd 2161 dislocker_0.7.3-3.dsc
 dcc6794b0d4da3a31563304509ea1fef3854c392 10788 dislocker_0.7.3-3.debian.tar.xz
 e31ec57051f912f11e6fa031f813bbe718a7064a 7517 
dislocker_0.7.3-3_source.buildinfo
Checksums-Sha256:
 72c264019f342976c56ddd1f5379c57f009ddb64be0d3f0d0fa35851f709f932 2161 
dislocker_0.7.3-3.dsc
 08cfb8a97db1bf8fea7753d00a8fbb0724f46bed29cae115067d914b3057ca8f 10788 
dislocker_0.7.3-3.debian.tar.xz
 aad7d2773f185bd3ebec2d238e592955c53b587f71ac23d3cd5ce1194afbac0f 7517 
dislocker_0.7.3-3_source.buildinfo
Files:
 be7b8e4a4f881b21ad5d61cea643c762 2161 utils optional dislocker_0.7.3-3.dsc
 bf375628196484fb07f8e4be424f8673 10788 utils optional 
dislocker_0.7.3-3.debian.tar.xz
 bce728be76248f189055d0fafe47ed92 7517 utils optional 
dislocker_0.7.3-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAmP8+kIACgkQ3mO5xwTr
6e9XmRAAneegVdLppLYTbui4TD6Z4CAgU6qsQQVnz7bidHl4iSK3MAJobwv1E+9h
9ggYR5UfG+g9djbPhSHiqhFup7S+HczMGoGK9rmPq+3kkbPg4/HFukZn8VTce/7w
CD4v+/1vbqs/ZeU6rjx+qGRugnYLCeSQBYpSi8iHuCjW+TopL4PoJvnTLZqefhJS
Y2yiqIbIDpzGgkPV

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

2023-02-27 Thread Thorsten Glaser

James Addison dixit:

>Maybe it's rare to propose 'do nothing' as a technical suggestion but I think
>it is worth considering here, since we are not the arbiters of Node.

It’s still a release-critical bug in Debian which impacts arm64 builders
including reproducible-builds. I would see this fixed in bookworm, at
least by a band-aid (raising these limits by default); the proper fix
can be revisited after the release, and in coordination with upstream.

We know the default ulimits for users in Debian, and they are higher
than the 1 MiB assumed by v8, by quite some factor, so this won’t break
things which are not currently broken (by that exception). This will do
for the release I think.

If a proper, upstream-supported, fix arrives within $time it’s even
possible that a bookworm-security update includes that. Still thinking
along the line of getrlimit + subtract known arch-specific value for
the fix here, whatever makes sense with the v8 setting anyway…

bye,
//mirabilos
-- 
Gestern Nacht ist mein IRC-Netzwerk explodiert. Ich hatte nicht damit
gerechnet, darum bin ich blutverschmiert… wer konnte ahnen, daß SIE so
reagier’n… gestern Nacht ist mein IRC-Netzwerk explodiert~~~
(as of 2021-06-15 The MirOS Project temporarily reconvenes on OFTC)

Bug#1024589: dislocker: FTBFS with ruby3.1: mv: cannot stat '/<>/debian/tmp/usr/lib/libdislocker*': No such file or directory

2023-02-27 Thread Eriberto Mota

Em seg., 27 de fev. de 2023 às 06:42, Santiago Vila
 escreveu:
>
> El 26/2/23 a las 0:04, Adrian Bunk escribió:
> > The Ubuntu diff has a fix for this issue caused by merged /usr
> > (untested).
>
> Note: Such diff was actually already in #1017937. I've just merged
> both bugs. Also, I've tested the diff and confirm that it works.
>
> Thanks.

Today I talked to Giovani, and he's a little busy because of a Masters
Course. It asked me to upload the fix. I'll do it. Thanks guys.

Regards,

Eriberto

Processed: Bug#1032044 marked as pending in python-fastjsonschema

Processing control commands:

> tag -1 pending
Bug #1032044 {Done: Carsten Schoenert } 
[src:python-fastjsonschema] python-fastjsonschema: autopkgtest regression
Added tag(s) pending.

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

Bug#1032044: marked as pending in python-fastjsonschema

2023-02-27 Thread Carsten Schoenert

Control: tag -1 pending

Hello,

Bug #1032044 in python-fastjsonschema 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/python-team/packages/python-fastjsonschema/-/commit/efd6ecf7ffee4a07ad02988f6a8076586bb19d75


autopkgtest: Add additional needed package

Adding the package python3-pytest-benchmark to the list of depending
packages for running the test.

Closes: #1032044


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1032044

Bug#1032044: marked as done (python-fastjsonschema: autopkgtest regression)

Your message dated Mon, 27 Feb 2023 18:06:03 +
with message-id 
and subject line Bug#1032044: fixed in python-fastjsonschema 2.16.3-2
has caused the Debian Bug report #1032044,
regarding python-fastjsonschema: autopkgtest regression
to be marked as done.

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

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


-- 
1032044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032044
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-fastjsonschema
Version: 2.16.3-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-fastjsonschema/31711896/log.gz

...
 ERRORS 
__ ERROR at setup of test_benchmark_ok_values[value0] __
file 
/tmp/autopkgtest-lxc.xpfahx0d/downtmp/autopkgtest_tmp/tests/benchmarks/test_benchmark.py,
 line 50
  @pytest.mark.benchmark(min_rounds=20)
  @pytest.mark.parametrize('value', (
  [9, 'hello', [1, 'a', True], {'a': 'a', 'b': 'b', 'd': 'd'}, 42, 3],
  [9, 'world', [1, 'a', True], {'a': 'a', 'b': 'b', 'd': 'd'}, 42, 3],
  [9, 'world', [1, 'a', True], {'a': 'a', 'b': 'b', 'c': 'xy'}, 42, 3],
  [9, 'world', [1, 'a', True], {'a': 'a', 'b': 'b', 'c': 'xy'}, 'str', 5],
  ))
  def test_benchmark_ok_values(benchmark, value):
E   fixture 'benchmark' not found
>   available fixtures: asserter, cache, capfd, capfdbinary, caplog, 
> capsys, capsysbinary, doctest_namespace, monkeypatch, pytestconfig, 
> record_property, record_testsuite_property, record_xml_attribute, recwarn, 
> tmp_path, tmp_path_factory, tmpdir, tmpdir_factory
>   use 'pytest --fixtures [testpath]' for help on them.

/tmp/autopkgtest-lxc.xpfahx0d/downtmp/autopkgtest_tmp/tests/benchmarks/test_benchmark.py:50
...
=== short test summary info 
ERROR tests/benchmarks/test_benchmark.py::test_benchmark_ok_values[value0]
ERROR tests/benchmarks/test_benchmark.py::test_benchmark_ok_values[value1]
ERROR tests/benchmarks/test_benchmark.py::test_benchmark_ok_values[value2]
ERROR tests/benchmarks/test_benchmark.py::test_benchmark_ok_values[value3]
ERROR tests/benchmarks/test_benchmark.py::test_benchmark_bad_values[value0]
ERROR tests/benchmarks/test_benchmark.py::test_benchmark_bad_values[value1]
ERROR tests/benchmarks/test_benchmark.py::test_benchmark_bad_values[value2]
ERROR tests/benchmarks/test_benchmark.py::test_benchmark_bad_values[value3]
ERROR tests/benchmarks/test_benchmark.py::test_benchmark_bad_values[value4]
ERROR tests/benchmarks/test_benchmark.py::test_benchmark_bad_values[value5]
ERROR tests/benchmarks/test_benchmark.py::test_benchmark_bad_values[value6]
ERROR tests/benchmarks/test_benchmark.py::test_benchmark_bad_values[value7]
= 1830 passed, 8 xfailed, 20 xpassed, 2 warnings, 12 errors in 17.96s ==
autopkgtest [15:22:21]: test smoke: ---]
autopkgtest [15:22:21]: test smoke:  - - - - - - - - - - results - - - - - - - 
- - -
smokeFAIL non-zero exit status 1
...
autopkgtest [15:22:48]:  summary
smokeFAIL non-zero exit status 1
autodep8-python3 PASS (superficial)
--- End Message ---
--- Begin Message ---
Source: python-fastjsonschema
Source-Version: 2.16.3-2
Done: Carsten Schoenert 

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

Debian distribution maintenance software
pp.
Carsten Schoenert  (supplier of updated 
python-fastjsonschema 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, 27 Feb 2023 18:38:43 +0100
Source: python-fastjsonschema
Architecture: source
Version: 2.16.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Carsten Schoenert 
Closes: 1032044
Changes:
 python-fastjsonschema (2.16.3-2) unstable; urgency=medium
 .
   * Team upload.
   * autopkgtest: Add additional needed package
 (Closes: #1032044)
Checksums-Sha1:
 9b8b113833a4fef6f191718bf83a163cb6aab3b2 2559 
python-fastjsonschema_2.16.3-2.dsc
 4

Bug#1031446: marked as done (lomiri-ui-toolkit: FTBFS: QWARN : components::UnknownTestFunc() file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtTest/SignalSpy.qml:258: Error: Invalid write to global property

Your message dated Mon, 27 Feb 2023 18:05:55 +
with message-id 
and subject line Bug#1031446: fixed in lomiri-ui-toolkit 1.3.5010+dfsg-1
has caused the Debian Bug report #1031446,
regarding lomiri-ui-toolkit: FTBFS: QWARN  : components::UnknownTestFunc() 
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtTest/SignalSpy.qml:258: Error: 
Invalid write to global property "qtest_count"
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.)


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

Hi,

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


Relevant part (hopefully):
> Creating QML component for Lomiri.Metrics
> Failed to load Lomiri.Metrics
> import QtQuick 2.0
> import Lomiri.Metrics 0.1 as ALomiri_Metrics_0_1
> QtObject { }
> 
> file:///<>/qml/Lomiri/Metrics/qmldir:2:1: plugin cannot be 
> loaded for module "Lomiri.Metrics": Cannot protect module Lomiri.Metrics 0 as 
> it was never registered
> make[3]: *** [Makefile:745: check] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/lomiri-ui-toolkit_1.3.5000+dfsg-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230216&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: lomiri-ui-toolkit
Source-Version: 1.3.5010+dfsg-1
Done: Mike Gabriel 

We believe that the bug you reported is fixed in the latest version of
lomiri-ui-toolkit, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1031...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated lomiri-ui-toolkit 
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, 27 Feb 2023 18:43:10 +0100
Source: lomiri-ui-toolkit
Architecture: source
Version: 1.3.5010+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian UBports Team 
Changed-By: Mike Gabriel 
Closes: 1031446
Changes:
 lomiri-ui-toolkit (1.3.5010+dfsg-1) unstable; urgency=medium
 .
   * New upstream release.
 - Translation updates.
 - FTBFS discovered in sid-rebuilds not reproducible. (Closes: #1031446).
   * debian/control:
 + Resolve dev:pkg dependencies. Resolves crossbuilds of Lomiri.
 + Switch from fonts-ubuntu to fonts-noto*.
   * debian/patches:
 + Add 2003_stop-using-Ubuntu-fonts.patch. Stop using Ubuntu fonts, use
   Noto fonts alternatively.
Checksums-Sha1:
 3aa253b87e4b41ae90e5bc2038f06b63ae1be610 5000 
lomiri-ui-toolkit_1.3.5010+dfsg-1.dsc
 0883a6930d11e4cf7a44cc3d12930f0fe93974f4 3624256 
lomiri-ui-toolkit_1.3.5010+dfsg.orig.tar.xz
 1ab9567e9b7c06baab36a623147b2bbee8461394 51844 
lomiri-ui-toolkit_1.3.5010+dfsg-1.debian.tar.xz
 fb411d18758d4fbc95600955ffb393a244187f32 0 
lomiri-ui-toolkit_1.3.5010+dfsg-1_source.buildinfo
Checksums-Sha256:
 ec8964e2c32f20ee88f4cf2ac13fe813a372c7fdf54048971e188e50c08bd700 5000 
lomiri-ui-toolkit_1.3.5010+dfsg-1.dsc
 a35ef345d981827a25de9f45ea00a94a7164875586bed4d8f260313436a0b452 3624256 
lomiri-ui-toolkit_1.3.5010+dfsg.orig.tar.xz
 04beb4e1ba566c20410a762703d98aefd5a9b70c593fe50e2ad2d3b99536fd82 51844 
lomiri-ui-toolkit_1.3.5010+dfsg-1.debian.tar.xz
 a0b16880e38cf232f1d543bc65b04c2e005b1679fec0921b3201bba

Bug#1024047: marked as done (python-line-profiler FTBFS with Python 3.11 as supported version)

Your message dated Mon, 27 Feb 2023 17:34:38 +
with message-id 
and subject line Bug#1024047: fixed in python-line-profiler 4.0.2-1
has caused the Debian Bug report #1024047,
regarding python-line-profiler FTBFS with Python 3.11 as supported version
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.)


-- 
1024047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024047
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-line-profiler
Version: 2.1-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=python-line-profiler&ver=2.1-3%2Bb4

...
_line_profiler.c: In function ‘__pyx_f_14_line_profiler_python_trace_callback’:
_line_profiler.c:5627:46: error: invalid use of incomplete typedef 
‘PyFrameObject’ {aka ‘struct _frame’}
 5627 | __pyx_t_1 = ((PyObject *)__pyx_v_py_frame->f_code);
  |  ^~
_line_profiler.c:5835:58: error: invalid use of incomplete typedef 
‘PyFrameObject’ {aka ‘struct _frame’}
 5835 | __pyx_t_1 = __Pyx_PyInt_From_int(__pyx_v_py_frame->f_lineno); 
if (unlikely(!__pyx_t_1)) __PYX_ERR(0, 218, __pyx_L1_error)
  |  ^~
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
E: pybuild pybuild:379: build: plugin distutils failed with: exit code=1: 
/usr/bin/python3.11 setup.py build
--- End Message ---
--- Begin Message ---
Source: python-line-profiler
Source-Version: 4.0.2-1
Done: Bo YU 

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

Debian distribution maintenance software
pp.
Bo YU  (supplier of updated python-line-profiler 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, 25 Feb 2023 07:33:03 +0800
Source: python-line-profiler
Architecture: source
Version: 4.0.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Bo YU 
Closes: 1024047
Changes:
 python-line-profiler (4.0.2-1) unstable; urgency=medium
 .
   * Team upload
   [ Debian Janitor ]
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository-Browse.
   * Update standards version to 4.6.0, no changes needed.
 .
   [ Bo YU ]
   * New upstream version 4.0.2. (Closes: #1024047)
   * Transfer it from Debian science team to Debian python team
   * Drop all patches that upstream has merged
   * Add ubelt for test
   * Add more depends for autopkgtest
   * Add pybuild-plugin-pyproject on B-D
   * Set std-ver to 4.6.2
   * Update d/copyright
Checksums-Sha1:
 b920a12764582ed15f3ab00365a8890f62afe804 2199 python-line-profiler_4.0.2-1.dsc
 66bdc9250fb9b99c7d5d66c6d07f3bb7e18bd9f3 63855 
python-line-profiler_4.0.2.orig.tar.gz
 47102025fd36564a83396dbd49645ee336cdca37 6116 
python-line-profiler_4.0.2-1.debian.tar.xz
 24938e4c9e90f58467230de2870b9fa711e66ed1 7573 
python-line-profiler_4.0.2-1_source.buildinfo
Checksums-Sha256:
 a4f9a9d7b3e7ef979e60b964d9e621417d41875058a0918bfb5dd590a4f349b2 2199 
python-line-profiler_4.0.2-1.dsc
 4b10543d250ad900c2ab38d90d5e51aa7e645cd1e94842cda76706e486ba02b7 63855 
python-line-profiler_4.0.2.orig.tar.gz
 8c29b1ed8d2467ddff988a7e0d3ff3f6bae42bebcb92d8be299d5fbdfae1f010 6116 
python-line-profiler_4.0.2-1.debian.tar.xz
 90c8a1d7459fc0a8c7f9fa594495c80311cde514f23f584e506b6c3cd3505a81 7573 
python-line-profiler_4.0.2-1_source.buildinfo
Files:
 be11ba3ca103323f18f783279c0535a2 2199 python optional 
python-line-profiler_4.0.2-1.dsc
 f0e1351c4242d790fc71f64c17b0e311 63855 python optional 
python-line-profiler_4.0.2.orig.tar.gz
 e9102905d418fd3f728b91dfff54c346 6116 python optional 
python-line-profiler_4.0.2-1.debian.tar.xz
 7ec5073d30492c4c4417f9ea532a505c 7573 python optional 
python-line-profiler_4.0.2-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmP85hYQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFDMQDADFn2zy0KFF/ZYS9tQzuRF/0C8Hm9uHIpR6
MbvRFWw3VBNqeXVMiyGMate09gDrntso+isPB5SoJv15nWxH3EAokOKaShw5S0/j
2iYNkOd02aCGQivuVau1K5vhtSoMNGmvPAiTW5OllINN

Bug#987008: please review this grub patch to fix LVM rename support

2023-02-27 Thread Antoine Beaupré

Hi Peter,

I'm writing to you as the author of this patch in grub:

https://git.savannah.gnu.org/cgit/grub.git/commit/?id=879c4a8342eacc0ba4b9dd11dc69d3ec3dbe73af

We've had a report of a release-critical bug (in CC) against grub in
Debian that claims boot failures after renaming a logical volume:

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

The suggested patch (author in CC) is quite short:

---
Index: grub2-2.02+dfsg1/grub-core/disk/lvm.c
===
--- grub2-2.02+dfsg1.orig/grub-core/disk/lvm.c
+++ grub2-2.02+dfsg1/grub-core/disk/lvm.c
@@ -253,7 +253,7 @@ error_parsing_metadata:

   p = q = (char *)ptr;

-  if (grub_add ((grub_size_t)metadatabuf, (grub_size_t)mda_size, &ptr))
+  if (grub_add (ptr, (grub_size_t)grub_le_to_cpu64 (rlocn->size), &ptr))
 goto error_parsing_metadata;

   mda_end = (char *)ptr;


I have tried to review the patch but quickly got lost in this long
function, so I'm not sure it's the right fix.

Could you expand on the rationale on why the rlocn->offset is checked
first but mda_size instead of rlocn->size in the second case?

Thank you for any input,

a.


signature.asc
Description: PGP signature

Bug#1032031: marked as done (python3-zstandard also needs Depends: libzstd1 (<< 1.5.5))

Your message dated Mon, 27 Feb 2023 17:07:06 +
with message-id 
and subject line Bug#1032031: fixed in python-zstandard 0.20.0-3
has caused the Debian Bug report #1032031,
regarding python3-zstandard also needs Depends: libzstd1 (<< 1.5.5)
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.)


-- 
1032031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032031
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-zstandard
Version: 0.20.0-2
Severity: serious

This is not just an autopkgtest issue, it would break the package
for users if the dependencies of python3-zstandard in bookworm
would permit installing python3-zstandard/bookworm together
with a more recent version of libzstd1 from trixie (expecially
when upgrading from bookworm to trixie) or bookworm-backports.
--- End Message ---
--- Begin Message ---
Source: python-zstandard
Source-Version: 0.20.0-3
Done: Boyuan Yang 

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated python-zstandard 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, 27 Feb 2023 11:43:22 -0500
Source: python-zstandard
Architecture: source
Version: 0.20.0-3
Distribution: unstable
Urgency: high
Maintainer: Debian Python Team 
Changed-By: Boyuan Yang 
Closes: 1032031
Changes:
 python-zstandard (0.20.0-3) unstable; urgency=high
 .
   * debian/control: Also add dependency on libzstd1 (<< 1.5.5~).
 (Closes: #1032031)
Checksums-Sha1:
 7f78b69cb5bfc8ad4efed29421229e4e1c63ae9d 2306 python-zstandard_0.20.0-3.dsc
 e3cfd9da196ac89afa3b2f95f5d25cf42c75b77a 712241 
python-zstandard_0.20.0.orig.tar.gz
 e76ee6ac16cca45870e1d2b8e579f5e11e3d94f7 4900 
python-zstandard_0.20.0-3.debian.tar.xz
 7b0d4c926d7a743aaaf61a728c61d10a340ac475 8738 
python-zstandard_0.20.0-3_amd64.buildinfo
Checksums-Sha256:
 708a99a82de51164f33c590e66a82df5da0f84eefc1cef80a0a723186d3f80c5 2306 
python-zstandard_0.20.0-3.dsc
 4f44f00c8abb5faf051c900576816bec6612bb975fcbccf383b72087e78f30d0 712241 
python-zstandard_0.20.0.orig.tar.gz
 28b47abe3d5d7f06f6aa08e5142644990de4b719b1daf994f03397abf7aea1b6 4900 
python-zstandard_0.20.0-3.debian.tar.xz
 cd3570730c9d3487e5672a254560f5451ae2b94ff8283ca648d2d86a152c2e72 8738 
python-zstandard_0.20.0-3_amd64.buildinfo
Files:
 2b78351c1b2c3898006f21b310d1c4bb 2306 python optional 
python-zstandard_0.20.0-3.dsc
 f217399f9bf01dc6f12bf4a27aec7aa1 712241 python optional 
python-zstandard_0.20.0.orig.tar.gz
 096d2909f8404f9fc25bf4222a4f4451 4900 python optional 
python-zstandard_0.20.0-3.debian.tar.xz
 3452e4539cf6123ad7581f7fa800a2b7 8738 python optional 
python-zstandard_0.20.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmP83oUACgkQwpPntGGC
Ws6hbw/9GZXLozTsnSPruv6VsDIfSEa0E5JsW2pGRB+sntMwrSiJEh932GosB1Ez
mD+Xvw77SRoC9xTZCxqH74W3wdMoAsqRIm0s1bX7T9bhTfkfAp7PaO4Zqpl7JoQz
LWfmH+K+xoG+3kvlMZ2Xtdr7U6hx4Cp+u643RXwem5BbPsEghQaBNuAK7hot/QKB
CUay1bCTYQjYbl8G7vhz7N8sE0T+eavZ3l16Na6+oV1KFK4rDpIfX0eOzz+z2+2g
XgIn66q4/7gGIdjiMVOu5dzDT+ABCyrF8gtjFHS8JH3Crd2tL8fcKC77rz86PA4f
QQCANrYCYrQkq1Wsp6jU/TGMhKlP//yBU9kdlKpCyRLhsefE220UMpv7Ou/dzO2L
f45c+YsAKyPZ//Kn2/6MkDpvReISXBOV3XGg8sZPIXL7jKXdqamyxGVTgJ/8X87r
FkwUKY+7y0HxqAyseTOoxn+i4dFGXjiv5+j8LJVbjFgTE8Wi/pZnfCHFEJ5Au7bf
gp5WC871QPyzZGr6hrJ1PBFLqy+uREavhAbcB+1XyLZPl1YYi/hMqkUwixD6Y+0e
oZ8PF0XzSoCBTRAYkONDWPRphkbs+MkBGN72rQkSAd9y8SUWFg1f5+yydISfQdU2
EEzd4dfIssQ2KcEgSePXYL3WszJ0SfinZKbHLURHXFPjbgj6Fdg=
=+24g
-END PGP SIGNATURE End Message ---

Bug#987008: grub LVM bug #987008: experimental package available, please test

2023-02-27 Thread Hoyer, David

I was not able to use the grub2 build as-is because we are running bullseye and 
the built image required newer versions of glibc.
However, I grabbed the original source code from Debian and the Debian code 
patch from https://people.debian.org/~anarcat/debian/sid/ and rebuilt it myself 
with minor tweaks so that it would build in bullseye (changed gcc-12 to gcc-10) 
and loaded it onto a system.
When running the test case Rogier which failed previously (fails within 120 
iterations), it is now passing with >1000 iterations.

Bug#1031893: marked as done (qtcreator: binary-all FTBFS)

Your message dated Mon, 27 Feb 2023 16:36:44 +
with message-id 
and subject line Bug#1031893: fixed in qtcreator 9.0.2-2
has caused the Debian Bug report #1031893,
regarding qtcreator: binary-all 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.)


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

https://buildd.debian.org/status/fetch.php?pkg=qtcreator&arch=all&ver=9.0.2-1&stamp=1677250700&raw=0

...
   dh_install -i -O--builddirectory=builddir
dh_install: warning: Cannot find (any matches for) "usr/share/qtcreator/doc/" 
(tried in ., debian/tmp)

dh_install: warning: qtcreator-doc missing files: usr/share/qtcreator/doc/
dh_install: error: missing files, aborting
make: *** [debian/rules:33: binary-indep] Error 25
--- End Message ---
--- Begin Message ---
Source: qtcreator
Source-Version: 9.0.2-2
Done: Lisandro Damián Nicanor Pérez Meyer 

We believe that the bug you reported is fixed in the latest version of
qtcreator, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1031...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Lisandro Damián Nicanor Pérez Meyer  (supplier of updated 
qtcreator 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, 27 Feb 2023 13:12:24 -0300
Source: qtcreator
Architecture: source
Version: 9.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Lisandro Damián Nicanor Pérez Meyer 
Closes: 1031893
Changes:
 qtcreator (9.0.2-2) unstable; urgency=medium
 .
   * Fix search path for qdoc (Closes: #1031893).
 Thanks Pino Toscano for the help!
Checksums-Sha1:
 00dc71e69b67b777d28ad47b3e5a9994c48be3b5 2766 qtcreator_9.0.2-2.dsc
 e96a8115f3060c6352e364374e8b2c137e03d3e4 29616 qtcreator_9.0.2-2.debian.tar.xz
 ceeff7694c3b6dda20262a7816988648a2efa120 16701 
qtcreator_9.0.2-2_source.buildinfo
Checksums-Sha256:
 12154854ed957102eb6b62b58fbbc05d04be0cc01ad9d4e5999be4b05ed82f3b 2766 
qtcreator_9.0.2-2.dsc
 8ff4c73a32a1599312e266e07bb936f51ba318e70dc4959a506048db80b5ebb5 29616 
qtcreator_9.0.2-2.debian.tar.xz
 ae6d84ebc7bbb527393db61d82d9f8e4d58d7b1ae97e1d1e0e676549abf2f34f 16701 
qtcreator_9.0.2-2_source.buildinfo
Files:
 4cf94c4096a1e1d1f25559985c5e162c 2766 devel optional qtcreator_9.0.2-2.dsc
 2c5b34460e2ab96b459230e3b87d4128 29616 devel optional 
qtcreator_9.0.2-2.debian.tar.xz
 fab4e858b37b564fd0dd2c5acbad75b9 16701 devel optional 
qtcreator_9.0.2-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEEt36hKwjsrvwSzE8q2RfQGKGp9AFAmP81pkUHGxpc2FuZHJv
QGRlYmlhbi5vcmcACgkQq2RfQGKGp9ABsQ/+PYzh+HooFiwuVRo9qxwKd86FCOD2
Ayr31XeyPs1yH4Qs4BSObjzg1/V339gXpQZ1gTILFFxbpRgHUenl9jUhF53Ek9l5
17ooLbaCNvT/eICmsjNW0Wjz9d6cBrxRjt/3BPAEK550HB04GP2Kt5vIeAMIjCV8
LjXRJV0dNH3YzBCnpYmXe67k9n2VDv1rSLSdeOzJx6cb3Qoj9vPgMQTP6R2WUttM
NtWXvu9YooSDc/BHxMxcsVkyCnF0lNioB2bPPEEBNb2b9rR+7BRBpEYqmiHzJ3Nq
iXj4ur9jr7jv7APVvfN83Bdf4JNlN5KwI9krC2dPdac78dFxsB+PgyoUOev3ijfz
nJyztoSTxYXy8qhOktUuvZ3ZXdqQJUM5aexL2MMuvT4x1Pj4ugxE7kCZh5Y7ZoEh
pl92l3PpHs4M9/ozF2AiscHyJzhzWOeCLqCYnh5jMRRBpo83aLSN95lvWozpmfLe
jqzdqdB17ZXNKTBOEaV+vjpob4hYn80q72PyxcrhkpgcTpQyOyGNNsJXdBaA2qC+
B74H2M0nk8m8N4Bx67AeampThlumdfGtXqrmP1OupY44rMuiExG/tTrtmiUtLCCH
dgnO8+5Anb9yLgeD+vGGI0P6J1D/r4wQ24jITvy3C7IBqrMBtjH5veKL3NJUmURG
nZXyBepSd/vjPb8=
=CyBo
-END PGP SIGNATURE End Message ---

Bug#1024047: python-line-profiler

2023-02-27 Thread Julian Gilbey

On Mon, Feb 27, 2023 at 04:16:53PM +0100, Bastian Germann wrote:
> On Mon, 13 Feb 2023 21:14:24 + Julian Gilbey wrote:
> > Just an FYI: though ubelt is a requirement for running the tests, a
> > much more serious problem is that python-line-profiler requires an
> > alpha version of Cython 3.0.0 to compile, and that is not (yet?)
> > packaged for Debian.  Hopefully at some point over the next two years,
> > Cython 3.0 will mature enough to actually be released, and then it
> > will be possible to upgrade python-line-profiler.
> 
> The version seems to build with the stable cython3:
> https://salsa.debian.org/python-team/packages/python-line-profiler/-/jobs/3998594

Thanks - that's good to know!  So it should make it into trixie
regardless of what happens to Cython.

Best wishes,

   Julian

Processed: untag

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

> tags 1019273 - pending
Bug #1019273 [src:apt] apt: Missing licenses and copyright statements in 
debian/copyright
Removed tag(s) pending.
>
End of message, stopping processing here.

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

Bug#1016288: pulseaudio-dlna: crashes on start

2023-02-27 Thread Michael Prokop

* Frank Loeffler [Mon Sep 05, 2022 at 04:01:55PM +0200]:
> Package: pulseaudio-dlna
> Version: 0.5.3+git20200329-0.1
> Followup-For: Bug #1016288
> 
> Dear Maintainer,
> 
> A similar situation occurs on stable:
[...]

> Versions > 0.5.2 are available from here: 
> https://github.com/Cygn/pulseaudio-dlna .
> 
> I am reporting this here even though the previous report was for
> unstable because quite likely versions of dependencies are the problem
> in both cases and similar fixes/updates could be made in both cases.
> 
> Without any change, this package is quite unuseable also on Debian
> stable, so 'grave' seems to be the correct severity.

Due to this bug pulseaudio-dlna didn't migrate to Debian/testing and
therefore won't be shipped with the upcoming Debian/stable release
AKA bookworm.

In the meanwhile version 0.6.6-1 got released by upstream, see
https://github.com/Cygn/pulseaudio-dlna/releases/tag/pulseaudio-dlna-0.6.6-1

It looks like this issue might be related to
https://github.com/home-assistant-libs/pychromecast/pull/556
so if this issue should still be present then the version of
python3-pychromecast might not fit.

Briefly looking at
https://github.com/Cygn/pulseaudio-dlna/commits/master it looks like
it nowadays depends on pychromecast v10 which is available as
python3-pychromecast in Debian/experimental.

Might make sense to clarify the situation and ensure that it's at
least working Debian/unstable again (and could possibly be
backported in the future to bookworm then)?

Muammar, are you still maintaining this package?

regards
-mika-


signature.asc
Description: PGP signature

Bug#1024047: python-line-profiler

2023-02-27 Thread Bastian Germann


On Mon, 13 Feb 2023 21:14:24 + Julian Gilbey wrote:

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


The version seems to build with the stable cython3:
https://salsa.debian.org/python-team/packages/python-line-profiler/-/jobs/3998594

Bug#1030496: marked as done (fop: FTBFS: [javadoc] /<>/fop-core/src/main/java/org/apache/fop/servlet/FopServlet.java:29: error: package javax.servlet does not exist)

Your message dated Mon, 27 Feb 2023 15:10:46 +0100
with message-id 
and subject line Re: Bug#1030496: fop: FTBFS:   [javadoc] 
/<>/fop-core/src/main/java/org/apache/fop/servlet/FopServlet.java:29:
 error: package javax.servlet does not exist
has caused the Debian Bug report #1030496,
regarding fop: FTBFS:   [javadoc] 
/<>/fop-core/src/main/java/org/apache/fop/servlet/FopServlet.java:29:
 error: package javax.servlet 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.)


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

Hi,

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


Relevant part (hopefully):
> [INFO] ---
> [INFO]  T E S T S
> [INFO] ---
> [INFO] Running org.apache.fop.configuration.DefaultConfigurationTestCase
> [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.131 
> s - in org.apache.fop.configuration.DefaultConfigurationTestCase
> [INFO] Running org.apache.fop.HyphenationTestCase
> [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.162 
> s - in org.apache.fop.HyphenationTestCase
> [INFO] Running 
> org.apache.fop.layoutmgr.RetrieveTableMarkerLayoutManagerTestCase
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.073 
> s - in org.apache.fop.layoutmgr.RetrieveTableMarkerLayoutManagerTestCase
> [INFO] Running org.apache.fop.layoutmgr.BreakElementTestCase
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - 
> in org.apache.fop.layoutmgr.BreakElementTestCase
> [INFO] Running 
> org.apache.fop.layoutmgr.table.TableContentLayoutManagerTestCase
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.055 
> s - in org.apache.fop.layoutmgr.table.TableContentLayoutManagerTestCase
> [INFO] Running org.apache.fop.layoutmgr.table.TableCellLayoutManagerTestCase
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.373 
> s - in org.apache.fop.layoutmgr.table.TableCellLayoutManagerTestCase
> [INFO] Running org.apache.fop.layoutmgr.table.TableLayoutManagerTestCase
> [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.139 
> s - in org.apache.fop.layoutmgr.table.TableLayoutManagerTestCase
> [INFO] Running org.apache.fop.layoutmgr.PageSequenceLayoutManagerTestCase
> [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.322 
> s - in org.apache.fop.layoutmgr.PageSequenceLayoutManagerTestCase
> [INFO] Running 
> org.apache.fop.layoutmgr.RetrieveTableMarkerLayoutManagerMakerTestCase
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 
> s - in org.apache.fop.layoutmgr.RetrieveTableMarkerLayoutManagerMakerTestCase
> [INFO] Running org.apache.fop.intermediate.IFMimickingTestCase
> [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.304 
> s - in org.apache.fop.intermediate.IFMimickingTestCase
> [INFO] Running org.apache.fop.intermediate.AreaTreeParserTestCase
> [INFO] Tests run: 695, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 18.284 s - in org.apache.fop.intermediate.AreaTreeParserTestCase
> [INFO] Running org.apache.fop.intermediate.IFTestCase
> [ERROR] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
> 0.351 s <<< FAILURE! - in org.apache.fop.intermediate.IFTestCase
> [ERROR] runTest[3](org.apache.fop.intermediate.IFTestCase)  Time elapsed: 
> 0.015 s  <<< FAILURE!
> java.lang.AssertionError: Expected XPath expression to evaluate to 'true', 
> but got '' (XPath: /descendant::if:text[1]/@hyphenated)
>   at org.apache.fop.intermediate.IFTestCase.runTest(IFTestCase.java:103)
> 
> [INFO] Running org.apache.fop.intermediate.IFParserTestCase
> [INFO] Tests run: 695, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 7.409 s - in org.apache.fop.intermediate.IFParserTestCase
> [INFO] Running org.apache.fop.pdf.PDFAttachmentTestCase
> [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 
> s - in org.apache.fop.pdf.PDFAttachmentTestCase
> [INFO] Running org.apache.fop.pdf.PDFReferenceTestCase
> [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - 
> in org.apache.fop.pdf.PDFReferenceTestCase
> [INFO] Running org.apache.fop.pdf.PDFNumberTestCase

Bug#1029668: Cannot read HEIC anymore

Package: libheif1
Version: 1.14.2-1
Followup-For: Bug #1029668
X-Debbugs-Cc: debian-multime...@lists.debian.org

The inability to read HEIC content using applications that depend on libheif1
could be a symptom of a more general codec-loading problem in that package:

Version 1.14.0 of upstream libheif1 introduced a plugin-based system[1] (shared
modules) for codecs, and I'm not sure that we have opted-in to that and bundled
either-statically-or-dynamically-loaded codecs into the binary packages yet.

(also note: upstream decided to choose CMake as their single supported build
system from 1.14.0; that matches the build system that Debian already uses for
the most recent versions of the source package)


Although these codec modules are likely only intended for use by libheif1
currently, the Debian Policy Guide section about Static Libraries[2] is helpful
to refer to.

[1] - https://github.com/strukturag/libheif/tree/v1.14.2#codec-plugins

[2] - 
https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#static-libraries

Bug#1030496: fop: FTBFS: [javadoc] /<>/fop-core/src/main/java/org/apache/fop/servlet/FopServlet.java:29: error: package javax.servlet does not exist

2023-02-27 Thread Jochen Sprickerhof


Hi Lucas,

I was not able to reproduce this and RB seems to be fine as well:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/fop.html

Note that the error in your log seems to have been:


E: Build killed with signal TERM after 150 minutes of inactivity


Can you try this again?

Thanks!

Jochen


* Lucas Nussbaum  [2023-02-04 08:56]:

Source: fop
Version: 1:2.8-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230203 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):

[INFO] ---
[INFO]  T E S T S
[INFO] ---
[INFO] Running org.apache.fop.configuration.DefaultConfigurationTestCase
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.131 s 
- in org.apache.fop.configuration.DefaultConfigurationTestCase
[INFO] Running org.apache.fop.HyphenationTestCase
[INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.162 s 
- in org.apache.fop.HyphenationTestCase
[INFO] Running org.apache.fop.layoutmgr.RetrieveTableMarkerLayoutManagerTestCase
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.073 s 
- in org.apache.fop.layoutmgr.RetrieveTableMarkerLayoutManagerTestCase
[INFO] Running org.apache.fop.layoutmgr.BreakElementTestCase
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in 
org.apache.fop.layoutmgr.BreakElementTestCase
[INFO] Running org.apache.fop.layoutmgr.table.TableContentLayoutManagerTestCase
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.055 s 
- in org.apache.fop.layoutmgr.table.TableContentLayoutManagerTestCase
[INFO] Running org.apache.fop.layoutmgr.table.TableCellLayoutManagerTestCase
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.373 s 
- in org.apache.fop.layoutmgr.table.TableCellLayoutManagerTestCase
[INFO] Running org.apache.fop.layoutmgr.table.TableLayoutManagerTestCase
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.139 s 
- in org.apache.fop.layoutmgr.table.TableLayoutManagerTestCase
[INFO] Running org.apache.fop.layoutmgr.PageSequenceLayoutManagerTestCase
[INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.322 s 
- in org.apache.fop.layoutmgr.PageSequenceLayoutManagerTestCase
[INFO] Running 
org.apache.fop.layoutmgr.RetrieveTableMarkerLayoutManagerMakerTestCase
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 s 
- in org.apache.fop.layoutmgr.RetrieveTableMarkerLayoutManagerMakerTestCase
[INFO] Running org.apache.fop.intermediate.IFMimickingTestCase
[INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.304 s 
- in org.apache.fop.intermediate.IFMimickingTestCase
[INFO] Running org.apache.fop.intermediate.AreaTreeParserTestCase
[INFO] Tests run: 695, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 18.284 
s - in org.apache.fop.intermediate.AreaTreeParserTestCase
[INFO] Running org.apache.fop.intermediate.IFTestCase
[ERROR] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.351 s 
<<< FAILURE! - in org.apache.fop.intermediate.IFTestCase
[ERROR] runTest[3](org.apache.fop.intermediate.IFTestCase)  Time elapsed: 0.015 s  
<<< FAILURE!
java.lang.AssertionError: Expected XPath expression to evaluate to 'true', but 
got '' (XPath: /descendant::if:text[1]/@hyphenated)
at org.apache.fop.intermediate.IFTestCase.runTest(IFTestCase.java:103)

[INFO] Running org.apache.fop.intermediate.IFParserTestCase
[INFO] Tests run: 695, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.409 
s - in org.apache.fop.intermediate.IFParserTestCase
[INFO] Running org.apache.fop.pdf.PDFAttachmentTestCase
[INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 s 
- in org.apache.fop.pdf.PDFAttachmentTestCase
[INFO] Running org.apache.fop.pdf.PDFReferenceTestCase
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in 
org.apache.fop.pdf.PDFReferenceTestCase
[INFO] Running org.apache.fop.pdf.PDFNumberTestCase
[INFO] Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 s 
- in org.apache.fop.pdf.PDFNumberTestCase
[INFO] Running org.apache.fop.pdf.PDFPageLabelsTestCase
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.041 s 
- in org.apache.fop.pdf.PDFPageLabelsTestCase
[INFO] Running org.apache.fop.pdf.PDFImageXObjectTestCase
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.118 s 
- in org.apache.fop.pdf.PDFImageXObjectTestCase
[INFO] Running org.apache.fop.pdf.PDFPagePieceTestCase
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.018 s 
- in org.apache.fop.pdf.PDFPagePieceTestCase
[INFO] Running org.apache.fop.pdf.ObjectStreamTestCase
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0,

Processed: bug 1031964 is forwarded to https://salsa.debian.org/science-team/trilinos/-/merge_requests/1

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

> forwarded 1031964 
> https://salsa.debian.org/science-team/trilinos/-/merge_requests/1
Bug #1031964 [src:trilinos] libtrilinos-{globi,opti}pack-{13.2,dev} are empty
Set Bug forwarded-to-address to 
'https://salsa.debian.org/science-team/trilinos/-/merge_requests/1'.
> thanks
Stopping processing here.

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

Processed: tagging 1031977

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

> tags 1031977 + ftbfs
Bug #1031977 [src:gdb-bpf] gdb-bpf: not binNMU safe
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1031765: ganeti-testsuite: autopkgtest failure with procps 2:4.0.3-1

Processing control commands:

> reassign -1 procps 2:4.0.3-1
Bug #1031765 [ganeti-testsuite] ganeti-testsuite: autopkgtest failure with 
procps 2:4.0.3-1
Bug reassigned from package 'ganeti-testsuite' to 'procps'.
No longer marked as found in versions ganeti/3.0.2-2.
Ignoring request to alter fixed versions of bug #1031765 to the same values 
previously set
Bug #1031765 [procps] ganeti-testsuite: autopkgtest failure with procps 
2:4.0.3-1
Marked as found in versions procps/2:4.0.3-1.
> retitle -1 pgrep: signal handler matching breaks argument parsing
Bug #1031765 [procps] ganeti-testsuite: autopkgtest failure with procps 
2:4.0.3-1
Changed Bug title to 'pgrep: signal handler matching breaks argument parsing' 
from 'ganeti-testsuite: autopkgtest failure with procps 2:4.0.3-1'.

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

Bug#1031765: ganeti-testsuite: autopkgtest failure with procps 2:4.0.3-1

2023-02-27 Thread Apollon Oikonomopoulos

control: reassign -1 procps 2:4.0.3-1
control: retitle -1 pgrep: signal handler matching breaks argument parsing
thanks

Hi Adrian,

Thanks for the report!

On 11:07 Wed 22 Feb , Adrian Bunk wrote:
> 
> # Check with a single, known unused user-id
> #
> # We use "-1" here, which is not a valid user-id, so it's
> # guaranteed that it's unused.
> uid = uidpool.RequestUnusedUid(set([-1]))
> self.assertEqualValues(uid.GetUid(), -1)
> 
> 
> "pgrep -u -1" is now rejected by procps.

This is a (presumably) unintentional side effect of procps commit 
866abacf ("pgrep: Support matching on the presence of a userspace signal 
handler")[1], which added the same "-" argument of pkill to pgrep.
With this change, pgrep parses the numerical options in the same way as pkill:
it uses getopt_long() for most options, but it performs a manual argv 
scan[2] specifically to find signal-like options (e.g. -1, -88, -kill, 
etc.).

The result is that anything that looks like a signal option, but is 
passed as an argument to any of the other options, is removed early on 
from the argument list, causing a subsequent call to getopt_long() to 
fail if the original option takes a mandatory argument:

  $ pgrep -u -93
  pgrep: option requires an argument -- 'u'
  ...

  $ pgrep -d -2
  pgrep: option requires an argument -- 'd'
  ...

  $ pgrep -u -hup 
  pgrep: option requires an argument -- 'u'
  ...

We could probably question the usefulness of negative UID/PID/SIDs 
here, on the other hand this had been working for at least 15 years 
before breaking in a minor release. I'm reassigning this bug to procps 
for further discussion.

Cheers,
Apollon

[1] 
https://gitlab.com/procps-ng/procps/-/commit/866abacf8805a74fb7c59cae1f64963e0a540b14
[2] 
https://gitlab.com/procps-ng/procps/-/blob/806eb270f217ff7e1e745c7bda2b002b5be74be4/src/pgrep.c#L798

Bug#1027649: marked as done (aspectj: FTBFS: The type org.osgi.service.prefs.Preferences cannot be resolved. It is indirectly referenced from required .class files)

Your message dated Mon, 27 Feb 2023 11:35:07 +
with message-id 
and subject line Bug#1027649: fixed in aspectj 1.9.5-2
has caused the Debian Bug report #1027649,
regarding aspectj: FTBFS: The type org.osgi.service.prefs.Preferences cannot be 
resolved. It is indirectly referenced from required .class files
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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # Build the manpages
> docbook-to-man debian/aj.sgml> debian/aj.1
> docbook-to-man debian/ajbrowser.sgml > debian/ajbrowser.1
> sh debian/manpage_from.sh docs/devGuideDB/ajc.xml   > debian/ajc.1
> /usr/bin/onsgmls:/tmp/tmp.EnKfBMiYbA:550:25:X: reference to non-existent ID 
> "VERSIONCOMPATIBILITY"
> /usr/bin/onsgmls:/tmp/tmp.EnKfBMiYbA:27:39:X: reference to non-existent ID 
> "LTW"
> sh debian/manpage_from.sh docs/devGuideDB/ajdoc.xml > debian/ajdoc.1
> /usr/bin/onsgmls:/tmp/tmp.iyjxh7CaE5:93:25:X: reference to non-existent ID 
> "AJC_OPTIONS"
> /usr/bin/onsgmls:/tmp/tmp.iyjxh7CaE5:87:29:X: reference to non-existent ID 
> "AJC"
> # Build AspectJ
> ant -f debian/bootstrap.xml
> Buildfile: /<>/debian/bootstrap.xml
> 
> all:
> [mkdir] Created dir: /<>/org.eclipse.jdt.core/classes
>  [iajc] warning bad version number found in 
> /usr/share/java/aspectjrt-1.9.5.jar expected 1.9.5 found null
>  [iajc] error at public static class EclipsePreferencesListener 
> implements IEclipsePreferences.IPreferenceChangeListener {
>  [iajc]   
> ^^^
>  [iajc] 
> /<>/org.eclipse.jdt.core/src/main/java/org/aspectj/org/eclipse/jdt/internal/core/JavaModelManager.java:1658:0::0
>  The type org.osgi.service.prefs.Preferences cannot be resolved. It is 
> indirectly referenced from required .class files
>  [iajc] MessageHolder:  (3 info)  (1 warning)  (1 error) 
>  [iajc] [error   0]: error at public static class 
> EclipsePreferencesListener implements 
> IEclipsePreferences.IPreferenceChangeListener {
>  [iajc]   
> ^^^
>  [iajc] 
> /<>/org.eclipse.jdt.core/src/main/java/org/aspectj/org/eclipse/jdt/internal/core/JavaModelManager.java:1658:0::0
>  The type org.osgi.service.prefs.Preferences cannot be resolved. It is 
> indirectly referenced from required .class files
> 
> BUILD FAILED
> /<>/debian/bootstrap.xml:22: 1 errors
> 
> Total time: 4 seconds
> make[1]: *** [debian/rules:33: override_dh_auto_build] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/01/01/aspectj_1.9.5-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230101&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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

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

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

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated aspectj package)

(This message was generated automatically at their request; if you
believe that there is a

Bug#1027649: marked as pending in aspectj

2023-02-27 Thread Jochen Sprickerhof

Control: tag -1 pending

Hello,

Bug #1027649 in aspectj 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/java-team/aspectj/-/commit/a3a0dd2b76911a59f5df3418203ae50877ae277f


Add missing bootstrap dependency

Closes: #1027649


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1027649

Processed: Bug#1027649 marked as pending in aspectj

Processing control commands:

> tag -1 pending
Bug #1027649 [src:aspectj] aspectj: FTBFS: The type 
org.osgi.service.prefs.Preferences cannot be resolved. It is indirectly 
referenced from required .class files
Added tag(s) pending.

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

Bug#1031896: marked as done (libclamav11: LibClamAV Error: Can't verify database integrity, breaks amavis)

Your message dated Mon, 27 Feb 2023 11:19:50 +
with message-id 
and subject line Bug#1031896: fixed in clamav 1.0.1+dfsg-2
has caused the Debian Bug report #1031896,
regarding libclamav11: LibClamAV Error: Can't verify database integrity, breaks 
amavis
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.)


-- 
1031896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031896
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libclamav11
Version: 1.0.1+dfsg-1
Severity: critical
Justification: breaks unrelated software

Dear Maintainer,

   * What led up to the situation?

sudo service clamav-daemon stop
sudo service clamav-daemon start

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Tried mirroring working cvds from another machine

$ md5sum *
09c62fbb8d2de9cfeca516b3927347ba  bytecode.cvd
7294b378c7bd3bf86314365d96aea3e4  daily.cvd
a7bd2fc1eafcb260e76769a5821cb204  freshclam.dat
3a42e5027c90fba0e54d2abdaa9e86b4  main.cvd

   * What was the outcome of this action?

LibClamAV Error: Can't load /var/lib/clamav/daily.cvd: Can't verify database 
integrity
LibClamAV Error: cli_loaddbdir: error loading database /var/lib/clamav/daily.cvd

Amavis errors on every inbound email

   * What outcome did you expect instead?

Working clamav, working amavis

See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027130

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

Kernel: Linux 5.8.3-x86_64-linode137 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libclamav11 depends on:
ii  libbz2-1.01.0.8-5+b1
ii  libc6 2.36-5
ii  libcurl4  7.88.1-1
ii  libgcc-s1 12.2.0-9
ii  libjson-c50.16-1
ii  libmspack00.10.1-2
ii  libpcre2-8-0  10.40-1
ii  libssl3   3.0.8-1
ii  libtfm1   0.13-4.1
ii  libxml2   2.9.14+dfsg-1.1+b2
ii  zlib1g1:1.2.11.dfsg-4.1

libclamav11 recommends no packages.

Versions of packages libclamav11 suggests:
pn  libclamunrar
pn  libclamunrar11  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: clamav
Source-Version: 1.0.1+dfsg-2
Done: Sebastian Andrzej Siewior 

We believe that the bug you reported is fixed in the latest version of
clamav, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1031...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastian Andrzej Siewior  (supplier of updated clamav 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 26 Feb 2023 17:39:06 +0100
Source: clamav
Architecture: source
Version: 1.0.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: ClamAV Team 
Changed-By: Sebastian Andrzej Siewior 
Closes: 1027010 1031896
Changes:
 clamav (1.0.1+dfsg-2) unstable; urgency=medium
 .
   * Depend on latest libtfm1 (Closes: #1031896, #1027010).
Checksums-Sha1:
 80664ea4f13ae354f0566cf40b48fdbdbe2052cf 2829 clamav_1.0.1+dfsg-2.dsc
 bdf36c34e43477ec83ba35c0ec34ae0f25c0154e 222880 
clamav_1.0.1+dfsg-2.debian.tar.xz
Checksums-Sha256:
 d081171284ce95a0ff5455d9765e9d2a411aa7152f7cc94cfa62b6bb6879782d 2829 
clamav_1.0.1+dfsg-2.dsc
 3bf394b83955959efd3cbc8552f94b29d7564963f07ab8d87dbc4ce367971ea1 222880 
clamav_1.0.1+dfsg-2.debian.tar.xz
Files:
 5614da9c74d7d7becb8384f693516644 2829 utils optional clamav_1.0.1+dfsg-2.dsc
 b9c8cca05e3f753ce2b42638b32f9444 222880 utils optional 
clamav_1.0.1+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEV4kucFIzBRM39v3RBWQfF1cS+lsFAmP8jIAACgkQBWQfF1cS
+lvwnAv9FdALXaiYiUBbACeMxQdtx/4NvdRe+GcYQMO0ZIYklNGfta+6wGoIDhox
qjU099jEinOsCUZ6TcTyQKPLiSsm+MMPDJnUod7x4IdHEUcOPcafRqdMClKgjgk9
O0jji5FWu0p1amdgXqSdQ7b3zB2B4Vx6uYlEiVrKFkgofrVBjYeLMuScwdiNg/CV
v7+cBMvO7tywFOVKdJ7IW8j4bgIsGOyirq/Ti9Wxji8whWMVMXplnNBv+PDOCrD9
6lKHcw2Dz2/U74aPXASObyb94YEMR/aMQwCq14t7ltjjfGEEcGicsHU03ZWM+HuM
CcC+LQL8Is2E7ckbvfrjncYjhFO8wjmpBHUS0fLJYHAZoS7fDcFM3lGnHscpLqc

Processed: tagging 1031622

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

> tags 1031622 + d-i
Bug #1031622 [src:e2fsprogs] mke2fs: should not enable orphan_file by default 
until trixie
Added tag(s) d-i.
> thanks
Stopping processing here.

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

Processed: reopening 1031622, found 1031622 in 1.47.0-1

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

> reopen 1031622
Bug #1031622 {Done: Cyril Brulebois } [src:e2fsprogs] mke2fs: 
should not enable orphan_file by default until trixie
Bug reopened
Ignoring request to alter fixed versions of bug #1031622 to the same values 
previously set
> found 1031622 1.47.0-1
Bug #1031622 [src:e2fsprogs] mke2fs: should not enable orphan_file by default 
until trixie
Ignoring request to alter found versions of bug #1031622 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#1024589: dislocker: FTBFS with ruby3.1: mv: cannot stat '/<>/debian/tmp/usr/lib/libdislocker*': No such file or directory

2023-02-27 Thread Santiago Vila


El 26/2/23 a las 0:04, Adrian Bunk escribió:

The Ubuntu diff has a fix for this issue caused by merged /usr
(untested).


Note: Such diff was actually already in #1017937. I've just merged
both bugs. Also, I've tested the diff and confirm that it works.

Thanks.

Processed: severity

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

> severity 1017937 serious
Bug #1017937 [src:dislocker] dislocker misbuilds in a build environment that's 
usrmerge'd
Bug #1024589 [src:dislocker] dislocker: FTBFS with ruby3.1: mv: cannot stat 
'/<>/debian/tmp/usr/lib/libdislocker*': No such file or directory
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: merge

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

> reassign 1017937 src:dislocker
Bug #1017937 [dislocker] dislocker misbuilds in a build environment that's 
usrmerge'd
Bug reassigned from package 'dislocker' to 'src:dislocker'.
No longer marked as found in versions dislocker/0.7.3-2.1.
Ignoring request to alter fixed versions of bug #1017937 to the same values 
previously set
> forcemerge 1017937 1024589
Bug #1017937 [src:dislocker] dislocker misbuilds in a build environment that's 
usrmerge'd
Bug #1024589 [src:dislocker] dislocker: FTBFS with ruby3.1: mv: cannot stat 
'/<>/debian/tmp/usr/lib/libdislocker*': No such file or directory
Severity set to 'normal' from 'serious'
Added tag(s) patch.
Bug #1017937 [src:dislocker] dislocker misbuilds in a build environment that's 
usrmerge'd
Marked as found in versions dislocker/0.7.3-2.1.
Added tag(s) sid, bookworm, and ftbfs.
Merged 1017937 1024589
> thanks
Stopping processing here.

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

Processed (with 1 error): merge