Processed: Re: Bug#1030510: Info received (Bug#1030510: Info received (Bug#1030510: Info received (mariadb: FTBFS on s390x: timeout)))

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1030510 [src:mariadb] mariadb: FTBFS on s390x: crash on munmap(),
Severity set to 'serious' from 'normal'

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

Bug#1030838: rust-quinn-proto: autopkgtest failure on i386

[Adrian Bunk]

Source: rust-quinn-proto
Version: 0.9.2-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/i386/r/rust-quinn-proto/31157225/log.gz

...
failures:

 connection::pacing::tests::computes_pause_correctly stdout 
thread 'connection::pacing::tests::computes_pause_correctly' panicked at 
'assertion failed: `(left == right)`
  left: `3`,
 right: `4`', src/connection/pacing.rs:272:9
stack backtrace:
   0: rust_begin_unwind
 at /usr/src/rustc-1.63.0/library/std/src/panicking.rs:584:5
   1: core::panicking::panic_fmt
 at /usr/src/rustc-1.63.0/library/core/src/panicking.rs:142:14
   2: core::panicking::assert_failed_inner
   3: core::panicking::assert_failed
 at /usr/src/rustc-1.63.0/library/core/src/panicking.rs:181:5
   4: quinn_proto::connection::pacing::tests::computes_pause_correctly
 at ./src/connection/pacing.rs:272:9
   5: 
quinn_proto::connection::pacing::tests::computes_pause_correctly::{{closure}}
 at ./src/connection/pacing.rs:232:5
   6: core::ops::function::FnOnce::call_once
 at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
   7: core::ops::function::FnOnce::call_once
 at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose 
backtrace.


failures:
connection::pacing::tests::computes_pause_correctly

test result: FAILED. 103 passed; 1 failed; 0 ignored; 0 measured; 0 filtered 
out; finished in 0.87s

error: test failed, to rerun pass `--lib`
autopkgtest [22:07:02]: test librust-quinn-proto-dev:arbitrary: 
---]
autopkgtest [22:07:02]: test librust-quinn-proto-dev:arbitrary:  - - - - - - - 
- - - results - - - - - - - - - -
librust-quinn-proto-dev:arbitrary FAIL non-zero exit status 101
...
autopkgtest [22:18:39]:  summary
rust-quinn-proto:@   FLAKY non-zero exit status 101
librust-quinn-proto-dev:arbitrary FAIL non-zero exit status 101
librust-quinn-proto-dev:default FLAKY non-zero exit status 101
librust-quinn-proto-dev:native-certs FAIL non-zero exit status 101
librust-quinn-proto-dev:ring FAIL non-zero exit status 101
librust-quinn-proto-dev:rustls FLAKY non-zero exit status 101
librust-quinn-proto-dev:rustls-native-certs FAIL non-zero exit status 101
librust-quinn-proto-dev:tls-rustls FLAKY non-zero exit status 101
librust-quinn-proto-dev:webpki FAIL non-zero exit status 101
librust-quinn-proto-dev: FAIL non-zero exit status 101

Bug#1028841: marked as pending in gopacket

[Shengjing Zhu]

Control: tag -1 pending

Hello,

Bug #1028841 in gopacket 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/go-team/packages/gopacket/-/commit/69d0160931702639bbda0620316d815ea9fa7ca5


Add patch to skip comparing libpcap output in TestBPFInstruction

Closes: #1028841


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1028841

Processed: Bug#1028841 marked as pending in gopacket

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1028841 [src:gopacket] gopacket: FTBFS with libpcap >= 1.10.2
Added tag(s) pending.

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

Bug#1028371: bernhard: needs rebuilds on top of new protobuf

[Adrian Bunk]

On Tue, Jan 10, 2023 at 07:57:45AM +0100, Gianfranco Costamagna wrote:
> Source: bernhard
> Version: 0.2.6-3
> Severity: serious
> 
> Hello, your package is tied to a specific protobuf version, but doesn't 
> declare any explicit dependency on it
> 
> Now, the package fails to load due to pb.py not being rebuilt.
> 
> python3 -c "import bernhard"
> Traceback (most recent call last):
>   File "", line 1, in 
>   File "/usr/lib/python3/dist-packages/bernhard/__init__.py", line 20, in 
> 
> from . import pb
>   File "/usr/lib/python3/dist-packages/bernhard/pb.py", line 36, in 
> _descriptor.FieldDescriptor(
>   File "/usr/lib/python3/dist-packages/google/protobuf/descriptor.py", line 
> 560, in __new__
> _message.Message._CheckCalledFromGeneratedFile()
> TypeError: Descriptors should not be created directly, but only retrieved 
> from their parent.
> 
> 
> Please have a look.
> (not change rebuilding works as workaround, but I think we should make sure 
> the package is not used with a wrong
> protobuf version)

The package seems to require the same protobuf version as it was 
compiled with, but the dependency is only indirectly through 
python3-protobuf.

> G.

cu
Adrian

Processed: tagging 1024868

[Debian Bug Tracking System]

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

> tags 1024868 + pending
Bug #1024868 {Done: Paul Gevers } [src:rust-kvm-bindings] 
src:rust-kvm-bindings: fails to migrate to testing for too long: FTBFS on i386
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1030096: Any ideas Re: #1030096 dask.distributed intermittent autopkgtest fail ?

[Diane Trout]

On Tue, 2023-02-07 at 07:31 +, Rebecca N. Palmer wrote:
> On 07/02/2023 03:20, Diane Trout wrote:
> > What's your test environment like?
> 
> Salsa CI.
> 
> > I don't think head is hugely different from what was released in -
> > 1.
> > 
> > The diff looks like Andreas adjusted the dask dependency version,
> > configured a salsa CI run, and added some upstream metadata files
> 
> That sounds like you're not looking at my branch at all.  As
> previously 
> stated, that's
> https://salsa.debian.org/rnpalmer-guest/dask.distributed/-/tree/fix1030096
> (It's in a fork because I can't push to debian-python.)
> 
> See earlier in this bug for which test failures still remain.

I merged in most of Rebecca's changes via git cherry pick, though I
slightly edited the changelog. (making most entries a bullet point
instead of subheadings of the one line I left out).

I think I got the code to detect if IPv6 is available to work correctly
so I could set the DISABLE_IPV6 environment variable that
dask.distrubted supports.

I went with skipping the 32bit tests instead of xfailed because I don't
think they can work as written since I really think they're making
really large memory requests that can't ever succeed on 32bit.

You did a lot of work on trying to get the flaky tests to work more
reliably, and all that's included. Well except for the apply a patch
and then revert it.

All the merges are pushed to salsa debian/master. They also passed on
my local build host running i386.

Diane

Bug#1030432: marked as done (sleef: FTBFS: testerutil.h:93:6: error: conflicting types for 'mpfr_sinpi')

[Debian Bug Tracking System]

Your message dated Wed, 08 Feb 2023 06:36:48 +
with message-id 
and subject line Bug#1030432: fixed in sleef 3.5.1-3
has caused the Debian Bug report #1030432,
regarding sleef: FTBFS: testerutil.h:93:6: error: conflicting types for 
'mpfr_sinpi'
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.)


-- 
1030432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030432
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sleef
Version: 3.5.1-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):
> make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> [ 41%] Building C object src/libm-tester/CMakeFiles/iut.dir/iut.c.o
> cd /<>/obj-x86_64-linux-gnu/src/libm-tester && /usr/bin/clang 
> -DENABLE_ALIAS=1 -DENABLE_SYS_getrandom=1 -I/<>/src/common 
> -I/<>/src/arch -I/<>/obj-x86_64-linux-gnu/include 
> -I/<>/src/libm 
> -I/<>/obj-x86_64-linux-gnu/src/libm/include -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wno-unused 
> -Wno-attributes -Wno-unused-result -ffp-contract=off -fno-math-errno 
> -fno-trapping-math -O2 -g -DNDEBUG -std=gnu99 -MD -MT 
> src/libm-tester/CMakeFiles/iut.dir/iut.c.o -MF CMakeFiles/iut.dir/iut.c.o.d 
> -o CMakeFiles/iut.dir/iut.c.o -c /<>/src/libm-tester/iut.c
> [ 42%] Building C object 
> src/libm-tester/CMakeFiles/tester2avx512fsp.dir/tester2simdsp.c.o
> cd /<>/obj-x86_64-linux-gnu/src/libm-tester && /usr/bin/clang 
> -DENABLE_ALIAS=1 -DENABLE_AVX512F=1 -DENABLE_SYS_getrandom=1 -DUSEMPFR=1 
> -I/<>/src/common -I/<>/src/arch 
> -I/<>/obj-x86_64-linux-gnu/include -I/<>/src/libm 
> -I/<>/obj-x86_64-linux-gnu/src/libm/include -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wno-unused 
> -Wno-attributes -Wno-unused-result -ffp-contract=off -fno-math-errno 
> -fno-trapping-math -O2 -g -DNDEBUG -mavx512f -std=gnu99 -MD -MT 
> src/libm-tester/CMakeFiles/tester2avx512fsp.dir/tester2simdsp.c.o -MF 
> CMakeFiles/tester2avx512fsp.dir/tester2simdsp.c.o.d -o 
> CMakeFiles/tester2avx512fsp.dir/tester2simdsp.c.o -c 
> /<>/src/libm-tester/tester2simdsp.c
> In file included from /<>/src/libm-tester/tester2simdsp.c:24:
> /<>/src/libm-tester/testerutil.h:93:6: error: conflicting types 
> for 'mpfr_sinpi'
> void mpfr_sinpi(mpfr_t ret, mpfr_t arg, mpfr_rnd_t rnd);
>  ^
> /usr/include/mpfr.h:752:21: note: previous declaration is here
> __MPFR_DECLSPEC int mpfr_sinpi (mpfr_ptr, mpfr_srcptr, mpfr_rnd_t);
> ^
> In file included from /<>/src/libm-tester/tester2simdsp.c:24:
> /<>/src/libm-tester/testerutil.h:94:6: error: conflicting types 
> for 'mpfr_cospi'
> void mpfr_cospi(mpfr_t ret, mpfr_t arg, mpfr_rnd_t rnd);
>  ^
> /usr/include/mpfr.h:753:21: note: previous declaration is here
> __MPFR_DECLSPEC int mpfr_cospi (mpfr_ptr, mpfr_srcptr, mpfr_rnd_t);
> ^
> 2 errors generated.
> make[3]: *** [src/libm-tester/CMakeFiles/tester2yavx512fsp.dir/build.make:79: 
> src/libm-tester/CMakeFiles/tester2yavx512fsp.dir/tester2simdsp.c.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/02/03/sleef_3.5.1-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230203;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230203&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: sleef
Source-Version: 3.5.1-3
Done: Aron Xu 

We believe that the bug you reported is fixed in the latest version of
sleef, 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
ha

Bug#999200: marked as done (fdflush: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

Your message dated Wed, 08 Feb 2023 04:21:00 +
with message-id 
and subject line Bug#1030754: Removed package(s) from unstable
has caused the Debian Bug report #999200,
regarding fdflush: missing required debian/rules targets build-arch and/or 
build-indep
to be marked as done.

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

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


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

Dear maintainer,

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

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

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

Best,

Lucas
--- End Message ---
--- Begin Message ---
Version: 1.0.1.3+rm

Dear submitter,

as the package fdflush has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1030754

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#965520: marked as done (fdflush: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Wed, 08 Feb 2023 04:21:00 +
with message-id 
and subject line Bug#1030754: Removed package(s) from unstable
has caused the Debian Bug report #965520,
regarding fdflush: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.

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

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


-- 
965520: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965520
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fdflush
Version: 1.0.1.3
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package fdflush uses debhelper with a compat level of 5 or 6,
which is deprecated and scheduled for removal[1].

Please bump the debhelper compat at your earliest convenience
/outside the freeze/!

  * Compat 13 is recommended (supported in stable-backports)

  * Compat 7 is the bare minimum


PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads
with compat bumps during the freeze.

If there is any risk that the fix for this bug might not migrate to
testing before 2021-01-01[3] then please postpone the fix until after
the freeze.


At the time of filing this bug, compat 5 and 6 are expected to be
removed "some time during the development cycle of bookworm".


Thanks,
~Niels


[1] https://lists.debian.org/debian-devel/2020/07/msg00065.html

[2] https://release.debian.org/bullseye/FAQ.html

[3] The choice of 2021-01-01 as a "deadline" is set before the actual
freeze deadline to provide a safe cut off point for most people.

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Version: 1.0.1.3+rm

Dear submitter,

as the package fdflush has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1030754

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1018801: marked as done (stdx-allocator ftbfs: assertThrown failed: No Exception was thrown.)

[Debian Bug Tracking System]

Your message dated Wed, 08 Feb 2023 04:19:46 +
with message-id 
and subject line Bug#1030718: Removed package(s) from unstable
has caused the Debian Bug report #1018801,
regarding stdx-allocator ftbfs: assertThrown failed: No Exception was thrown.
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.)


-- 
1018801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018801
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: stdx-allocator
Version: 3.1.0~beta.2-3
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic

Hi Matthias,

After fixing up stdx-allocator build-deps so that they're installable,
stdx-allocator fails to build from source due to a test failure:

[...]
 1/1 =
test: stdx-allocator-test
start time:   00:11:36
duration: 0.03s
result:   exit status 1
command:  MALLOC_PERTURB_=202 
'/<>/obj-x86_64-linux-gnu/stdx-allocator-test'
--- stderr ---
core.exception.AssertError@../source/stdx/allocator/package.d(1399): 
assertThrown failed: No Exception was thrown.

/usr/lib/ldc/x86_64-linux-gnu/include/d/std/exception.d:299 [0x55d86e05b4d5]
../source/stdx/allocator/package.d:1399 [0x55d86e065d87]
??:? [0x7fbe61462c85]
??:? [0x7fbe61480d7a]
??:? int rt.sections_elf_shared.DSO.opApply(scope int delegate(ref 
rt.sections_elf_shared.DSO)) [0x7fbe61481e08]
??:? int rt.minfo.moduleinfos_apply(scope int 
delegate(immutable(object.ModuleInfo*))) [0x7fbe61480d0b]
??:? int object.ModuleInfo.opApply(scope int delegate(object.ModuleInfo*)) 
[0x7fbe6146e9be]
??:? runModuleUnitTests [0x7fbe61462b34]
??:? void rt.dmain2._d_run_main2(char[][], ulong, extern (C) int 
function(char[][])*).runAll() [0x7fbe6147738a]
??:? _d_run_main2 [0x7fbe614771d5]
??:? _d_run_main [0x7fbe6147702d]
??:? [0x7fbe6119654f]
??:? __libc_start_main [0x7fbe61196608]
??:? [0x55d86dffd9b4]
1/22 modules FAILED unittests
==
[...]

You can see this in the Ubuntu build logs at
.

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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 3.1.0~beta.2-3+rm

Dear submitter,

as the package stdx-allocator has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1030718

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1004356: marked as done (ruby-gitlab-license-finder: missing Breaks+Replaces: ruby-license-finder (<< 6))

[Debian Bug Tracking System]

Your message dated Wed, 08 Feb 2023 04:18:45 +
with message-id 
and subject line Bug#1030707: Removed package(s) from unstable
has caused the Debian Bug report #1004356,
regarding ruby-gitlab-license-finder: missing Breaks+Replaces: 
ruby-license-finder (<< 6)
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.)


-- 
1004356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004356
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-gitlab-license-finder
Version: 6.14.2.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

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

  Selecting previously unselected package ruby-gitlab-license-finder.
  Preparing to unpack .../ruby-gitlab-license-finder_6.14.2.1-1_all.deb ...
  Unpacking ruby-gitlab-license-finder (6.14.2.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/ruby-gitlab-license-finder_6.14.2.1-1_all.deb 
(--unpack):
   trying to overwrite '/usr/bin/license_finder', which is also in package 
ruby-license-finder 2.1.2-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/ruby-gitlab-license-finder_6.14.2.1-1_all.deb

ruby-license-finder (2.1.2-2) is an RC buggy stale package in sid and
should probably be removed. It may be a predecessor of the newly packaged
ruby-gitlab-license-finder ...

The (<< 6) is based on the fact that uscan reports a new upstream
6.15.0 for src:ruby-license-finder.


cheers,

Andreas


ruby-license-finder=2.1.2-2_ruby-gitlab-license-finder=6.14.2.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 6.14.2.1-2+rm

Dear submitter,

as the package ruby-gitlab-license-finder has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1030707

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1029919: marked as done (ruby-gitlab-license-finder,ruby-license-finder: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Wed, 08 Feb 2023 04:18:45 +
with message-id 
and subject line Bug#1030707: Removed package(s) from unstable
has caused the Debian Bug report #1004356,
regarding ruby-gitlab-license-finder,ruby-license-finder: error when trying to 
install together
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.)


-- 
1004356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004356
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-gitlab-license-finder,ruby-license-finder
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 6.14.2.1-2
Control: found -1 7.0.1-1

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package ruby-license-finder.
  Preparing to unpack .../ruby-license-finder_7.0.1-1_all.deb ...
  Unpacking ruby-license-finder (7.0.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/ruby-license-finder_7.0.1-1_all.deb (--unpack):
   trying to overwrite '/usr/bin/license_finder', which is also in package 
ruby-gitlab-license-finder 6.14.2.1-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/ruby-license-finder_7.0.1-1_all.deb

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/bin/license_finder

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


ruby-gitlab-license-finder=6.14.2.1-2_ruby-license-finder=7.0.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 6.14.2.1-2+rm

Dear submitter,

as the package ruby-gitlab-license-finder has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1030707

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1030813: mumble: autopkgtest regression

[Chris Knadle]

This should be fixed in Mumble 1.3.4-3.
debian/tests/control had this:

   Test-Command: smoke

when it should have been:

   Tests: smoke

If the autopkgtest passes tomorrow as shown in the Debian tracker I'll close 
this bug.


   -- Chris

--
Chris Knadle
chris.kna...@coredump.us

Adrian Bunk:

Source: mumble
Version: 1.3.4-2
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/m/mumble/31139421/log.gz

...
autopkgtest [09:23:28]: test command1: smoke
autopkgtest [09:23:28]: test command1: [---
bash: line 1: smoke: command not found
autopkgtest [09:23:29]: test command1: ---]
autopkgtest [09:23:29]: test command1:  - - - - - - - - - - results - - - - - - 
- - - -
command1 FAIL non-zero exit status 127

Processed: closing 1030460

[Debian Bug Tracking System]

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

> close 1030460
Bug #1030460 [src:qtmir] qtmir: FTBFS: make[1]: *** [debian/rules:29: 
override_dh_auto_configure] Error 2
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1030460: closing 1030460

[Marius Gripsgard]

close 1030460 
thanks

Bug#1030814: marked as done (openldap: autopkgtest regression)

[Debian Bug Tracking System]

Your message dated Wed, 08 Feb 2023 03:19:43 +
with message-id 
and subject line Bug#1030814: fixed in openldap 2.5.13+dfsg-5
has caused the Debian Bug report #1030814,
regarding openldap: 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.)


-- 
1030814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030814
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openldap
Version: 2.5.13+dfsg-4
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/o/openldap/31139461/log.gz

...
autopkgtest [09:28:43]: test sha2-contrib: [---
/tmp/autopkgtest-lxc.jrj8ozx8/downtmp/build.7fx/src/debian/tests/sha2-contrib: 
line 6: slappasswd: command not found
autopkgtest [09:28:44]: test sha2-contrib: ---]
autopkgtest [09:28:44]: test sha2-contrib:  - - - - - - - - - - results - - - - 
- - - - - -
sha2-contrib FAIL non-zero exit status 127
autopkgtest [09:28:44]: test sha2-contrib:  - - - - - - - - - - stderr - - - - 
- - - - - -
/tmp/autopkgtest-lxc.jrj8ozx8/downtmp/build.7fx/src/debian/tests/sha2-contrib: 
line 6: slappasswd: command not found
autopkgtest [09:28:44]:  summary
slapdPASS (superficial)
smbk5pwd PASS (superficial)
sha2-contrib FAIL non-zero exit status 127
--- End Message ---
--- Begin Message ---
Source: openldap
Source-Version: 2.5.13+dfsg-5
Done: Ryan Tandy 

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

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

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

Debian distribution maintenance software
pp.
Ryan Tandy  (supplier of updated openldap package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 07 Feb 2023 17:56:12 -0800
Source: openldap
Architecture: source
Version: 2.5.13+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenLDAP Maintainers 

Changed-By: Ryan Tandy 
Closes: 1030814
Changes:
 openldap (2.5.13+dfsg-5) unstable; urgency=medium
 .
   * Fix sha2-contrib autopkgtest failure. Call slappasswd using its full path.
 (Closes: #1030814)
   * Disable flaky test test069-delta-multiprovider-starttls.
Checksums-Sha1:
 05da628ca7088ac84b7dbb2b0a38cc3048c0b237 3233 openldap_2.5.13+dfsg-5.dsc
 85f3a0603c1ea0a6e955ad342121bde20a407071 164516 
openldap_2.5.13+dfsg-5.debian.tar.xz
Checksums-Sha256:
 3192f78a46825039c6c9de6808ae98ab3d1c8846f43d2109ed654fd9c33fe472 3233 
openldap_2.5.13+dfsg-5.dsc
 161e22c1c79e2f7c6013cfc2bbf0265d6bbb78d91a0fcfa9ca866837f2c31d88 164516 
openldap_2.5.13+dfsg-5.debian.tar.xz
Files:
 ad5c15cfeb94742b07dc6531c2ccab04 3233 net optional openldap_2.5.13+dfsg-5.dsc
 e52f28b630246ee037c7e87aaa9ce0e1 164516 net optional 
openldap_2.5.13+dfsg-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEEPSfh0nqdQTd5kOFlIp/PEvXWa7YFAmPjDgoPHHJ5YW5AbmFy
ZGlzLmNhAAoJECKfzxL11mu2F9UP/2FqyYM7Wm0hKsocXOR79H0ciel5Fr7jqW6Q
dHbVRsUHingbcGhwx78gg2RLqJtfrNOyVW0UAhgXIDzBb29kylTeDNjp9REdFu+E
Fmo2isGICN0OjZwQPfkmKTcJPukhlkCWXak5Bj0bgz7685RIIxJ0vUxHf/lLV6nU
neQtdP6G7KQQpiBfJGBxDwCRVgsRlzMBoAqK36RKzajOjXNIwPNOCWgtpsLVbAc2
Xu2FNHcvct0H+dKGlb0WHQ4UNjvo4ujgIIKJsjEVEwyH2s25YLR7aORzAgpdLyHu
c10R7G86aYRYi/60MeWe+CnSaT8OHXO9mZTFMy3RuYUsdX/dQ1Q4TpvjJZzca+Vo
sXBRj9E5xbzGOMHdCYvJzAlbdjbA8pqcHH/MmkxA0YTQtkzPA/gbWiqztEJQIL9E
j4zswJlx+QxHyWkKtwLmtrc/WwE+Dzh8lPUE2XANlrTjEgD2DyQpbTvp7RzJMJ2u
L/zePWnwdjMJsY4P6yZ/vBOMwCK7pG2opwyqxeUvYjGbS+hg0IJH2huyFoN66NDF
h/30q2Fu9z/gORlN3EAoPs7Nj4peKnN7tVfV54jl7aNOBWQxmkVLIyjQQSocBK0L
IC9PNrpto9crKJFfdUDM/VLqCmt2zIKBCcKbMH4gUNgtfA54IwvFVBDbELuOsqxA
vRrWhzVm
=27yx
-END PGP SIGNATURE End Message ---

Bug#1030460: (no subject)

[Marius Gripsgard]

This got fixed upstream and the fix is included my last upload. closing this


Thank you

Processed: fixed 1030460 in 0.8.0~git20230207.ec35994-1

[Debian Bug Tracking System]

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

> fixed 1030460 0.8.0~git20230207.ec35994-1
Bug #1030460 [src:qtmir] qtmir: FTBFS: make[1]: *** [debian/rules:29: 
override_dh_auto_configure] Error 2
Marked as fixed in versions qtmir/0.8.0~git20230207.ec35994-1.
> thanks
Stopping processing here.

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

Bug#1026485: marked as done (debian-installer: FTBFS: Failed to stat - stat (2: No such file or directory))

[Debian Bug Tracking System]

ocate package usb-modules-5.19.0-1-amd64-di
> E: Couldn't find any package by glob 'usb-modules-5.19.0-1-amd64-di'
> E: Couldn't find any package by regex 'usb-modules-5.19.0-1-amd64-di'
> E: Unable to locate package usb-storage-modules-5.19.0-1-amd64-di
> E: Couldn't find any package by glob 'usb-storage-modules-5.19.0-1-amd64-di'
> E: Couldn't find any package by regex 'usb-storage-modules-5.19.0-1-amd64-di'
> make[9]: *** [Makefile:626: stamps/get_udebs-cdrom_gtk-stamp] Error 100


The full build log is available from:
http://qa-logs.debian.net/2022/12/20/debian-installer_20220917_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20221220&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 ---
Version: 20230207--- End Message ---

Processed: block 1023267 with 1029559

[Debian Bug Tracking System]

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

> block 1023267 with 1029559
Bug #1023267 [sc-im] sc-im: scopen fails with gvim not found (if it is not 
installed)
1023267 was not blocked by any bugs.
1023267 was not blocking any bugs.
Added blocking bug(s) of 1023267: 1029559
> thanks
Stopping processing here.

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

Bug#1002885: marked as done (tangerine-icon-theme: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Wed, 08 Feb 2023 00:08:46 +
with message-id 
and subject line Bug#1002885: fixed in tangerine-icon-theme 0.26.debian-6
has caused the Debian Bug report #1002885,
regarding tangerine-icon-theme: Removal of obsolete debhelper compat 5 and 6 in 
bookworm
to be marked as done.

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

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


-- 
1002885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002885
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tangerine-icon-theme
Version: 0.26.debian-5
Severity: serious
Tags: sid bookworm
User: nthyk...@master.debian.org
Usertags: compat-5-6-removal

Hi,

The package tangerine-icon-theme uses debhelper with a compat level of 5 or 6,
which is no longer supported [1].

Please bump the debhelper compat at your earliest convenience

  * Compat 13 is recommended (supported in stable-backports)

  * Compat 7 is the bare minimum


Thanks,
Andreas

[1] https://lists.debian.org/debian-devel/2020/07/msg00065.html
--- End Message ---
--- Begin Message ---
Source: tangerine-icon-theme
Source-Version: 0.26.debian-6
Done: Boyuan Yang 

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated tangerine-icon-theme 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 07 Feb 2023 18:47:23 -0500
Source: tangerine-icon-theme
Binary: tangerine-icon-theme
Architecture: source all
Version: 0.26.debian-6
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Boyuan Yang 
Description:
 tangerine-icon-theme - Tangerine Icon theme
Closes: 1002885
Changes:
 tangerine-icon-theme (0.26.debian-6) unstable; urgency=medium
 .
   * QA upload.
   * debian/compat: Bump compat to v7 to satisfy minimum requirement.
 (Closes: #1002885)
Checksums-Sha1:
 00511cb0be7d82903345e83ec5d9eae1a3231975 2121 
tangerine-icon-theme_0.26.debian-6.dsc
 6f942e682f27cea4d42a37cdafa326d44816987e 1148832 
tangerine-icon-theme_0.26.debian.orig.tar.gz
 596f15bc9b3c1c88515845cf1d8431e2b75e6631 27284 
tangerine-icon-theme_0.26.debian-6.debian.tar.xz
 6c7b816f134f0a76f0a56a5f6b6300ece3eafd24 375928 
tangerine-icon-theme_0.26.debian-6_all.deb
 18c9b44b630c76acd25991e4c5049ba3360975db 12426 
tangerine-icon-theme_0.26.debian-6_amd64.buildinfo
Checksums-Sha256:
 d1655b37caf9537f2edf0febd819e10b1fd3aa2112145335c1ef9d9b95ed9bb8 2121 
tangerine-icon-theme_0.26.debian-6.dsc
 b0d76fa82ba603b4d5e41a242b6f5b0e4f335aad471acb12fd497b225aa779a9 1148832 
tangerine-icon-theme_0.26.debian.orig.tar.gz
 9413f362f3a9d7db9ce3f7ec150344fbcf9e2b4a306b58c24356c2acf4066e78 27284 
tangerine-icon-theme_0.26.debian-6.debian.tar.xz
 a088f00ee4fdca3f7d4dd51fae9aba240899ef95cd070c93600040783534ea65 375928 
tangerine-icon-theme_0.26.debian-6_all.deb
 8715ff1fc9f31889b1bf6aea5f3b0cc6cbd636150994390e495b5dccf5c1d894 12426 
tangerine-icon-theme_0.26.debian-6_amd64.buildinfo
Files:
 4972bafc435f7f548360bb21a72246e4 2121 non-free/x11 optional 
tangerine-icon-theme_0.26.debian-6.dsc
 28c4c71aec139c09f12c9d5c8bf2d0b9 1148832 non-free/x11 optional 
tangerine-icon-theme_0.26.debian.orig.tar.gz
 9b654eb8110b315c8939d5be6fd1f517 27284 non-free/x11 optional 
tangerine-icon-theme_0.26.debian-6.debian.tar.xz
 f0c0ffad693b44b6b5e11921ebb310bc 375928 non-free/x11 optional 
tangerine-icon-theme_0.26.debian-6_all.deb
 ea2681fb84d35d4ee8298cc14fa2ddcb 12426 non-free/x11 optional 
tangerine-icon-theme_0.26.debian-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmPi5DsACgkQwpPntGGC
Ws5bBRAAuoM4y9srYKcbCfcjB9YVrn0E4S8hGPAj5fivjlD/khjsHO9RIi3h06xX
B1YmtWe+AxM+SeLCiNODSn7/ZyRbA8wYLq+VjXEhHmgdjtYolyj0Tg6aHDGip8aC
2w2n0dJJXRdROEtLLQutTofIuw0dDdfFBFrEwcFj27mWy3YO41buXOcv2+sC0W6x
dcFO9+KLzatukjwxO+2YkssiaGiT41kpsXL8Qlg0F2M7bCnku9B8wokhivRsJJpQ
6QqSD8t7f8u0aAX3AKOST8wW0JoOTVWc3L8vf47cXa+1daAxCGv1dE64nmBi0+Xv
RdrPj7i+e5sCKvwWNFx282WlNykjuMK/4bXO6NSxRwdf0/EG28N2JlhPNFknULSr
151Hp0iyRYxJPLNRZG0/qJ/wvtJ74CAsez/NhKzIu+NFXVWI9ewnGJurAk8tU4AR

Bug#1022222: marked as done (valgrind-if-available shouldn't stop providing valgrind on mipsel)

[Debian Bug Tracking System]

Your message dated Wed, 08 Feb 2023 00:07:06 +
with message-id 
and subject line Bug#102: fixed in qtmir 0.8.0~git20230207.ec35994-1
has caused the Debian Bug report #102,
regarding valgrind-if-available shouldn't stop providing valgrind on mipsel
to be marked as done.

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

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


-- 
102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=102
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: valgrind-if-available
Version: 3.18.1-1-1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Alessandro Ghedini , Debian UBports Team 

Control: affects -1 src:qtmir

valgrind-if-available (3.18.1-1-1) unstable; urgency=medium
...
  * Drop mipsel as valgrind disagrees about blah blah baseline Loongson.


This is wrong, and it makes at least qtmir FTBFS.

If there is any problem with valgrind on mipsel
it should be discussed and resolved in valgrind first,
if valgrind is available then valgrind-if-available
has to provide it.

It is also unclear what the baseline problem is this changelog
entry is referring to, there is no open bug in the valgrind package
mentioned and the closest I could find was a bug that was fixed (sic)
5 years ago.

It is also suprising if this is really a mipsel-only issue as the
changelog claims, I would have expected any issues to also show
up on mips64el.

Therefore please report any issues with valgrind on mipsel as bugs
against src:valgrind, but in any case please make valgrind-if-available
always provide valgrind on all architectures where it is available.
--- End Message ---
--- Begin Message ---
Source: qtmir
Source-Version: 0.8.0~git20230207.ec35994-1
Done: Marius Gripsgard 

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

Debian distribution maintenance software
pp.
Marius Gripsgard  (supplier of updated qtmir package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 08 Feb 2023 00:44:49 +0100
Source: qtmir
Architecture: source
Version: 0.8.0~git20230207.ec35994-1
Distribution: unstable
Urgency: medium
Maintainer: Debian UBports Team 
Changed-By: Marius Gripsgard 
Closes: 102
Changes:
 qtmir (0.8.0~git20230207.ec35994-1) unstable; urgency=medium
 .
   [ Mike Gabriel ]
   * debian/rules:
 + Don't hard-code architectures with valgrind support. Simply disable
   valgrind if not found in $PATH. (Closes: #102).
   * debian/control:
 + Bump to versioned B-D on liblomiri-api-dev (>= 0.2.0).
 .
   [ Marius Gripsgard ]
   * New git snapshot
Checksums-Sha1:
 a1f406a39fcb992aa200e56ccb86b21f6b5c7197 3349 
qtmir_0.8.0~git20230207.ec35994-1.dsc
 8f6b2a953f25ff2ea3bba58fbdb81a1c72506301 252228 
qtmir_0.8.0~git20230207.ec35994.orig.tar.xz
 5ae570ab6ab5ad1c51a9995aecf4f2bec01826de 46560 
qtmir_0.8.0~git20230207.ec35994-1.debian.tar.xz
 00e6fb717f15ae98fa917aedb264b1243e7e0d61 16486 
qtmir_0.8.0~git20230207.ec35994-1_source.buildinfo
Checksums-Sha256:
 456eb1adf037828b33c01d296b08ebb08b4edc495aa1d22bc1f27b99adbb6588 3349 
qtmir_0.8.0~git20230207.ec35994-1.dsc
 d7dcff2e60feffd5d3669468ce92ab5606eb3c7d548f2a8ed2da1ef7b7a235af 252228 
qtmir_0.8.0~git20230207.ec35994.orig.tar.xz
 81736bebd9593770f0597b44ec1cf4f7b7afb443491f30d8d5f9c5598fba0085 46560 
qtmir_0.8.0~git20230207.ec35994-1.debian.tar.xz
 eaf825917756280cc43a593bacdefc2846b4e13b3a8eea69b8e0e10e3adfa138 16486 
qtmir_0.8.0~git20230207.ec35994-1_source.buildinfo
Files:
 219d27ee4f3bf0c913792fa019d2273c 3349 libs optional 
qtmir_0.8.0~git20230207.ec35994-1.dsc
 4b23632ab6fe4cdbd6244932b2f69548 252228 libs optional 
qtmir_0.8.0~git20230207.ec35994.orig.tar.xz
 a8e7aa65d5394bbeb2c53fd88cd0b275 46560 libs optional 
qtmir_0.8.0~git20230207.ec35994-1.debian.tar.xz
 8191540437dd6e75812339a1cd5988a4 16486 libs optional 
qtmir_0.8.0~git20230207.ec35994-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEm65oPpnDJVLXb56DuvnOw/aSJ4kFAmPi4q4THG1hcml1c0B1
YnBvcnRzLmNvbQAKCRC6+c7D9pInib7zD/9DUXcltP6VkZ0Wbyxfl/5dMhzPZAVZ
Y+A7Engl2x0YIUCMUa3H7EgCMXFipujoNa3teav/KFZIcJoja6bi/eTtRCrGwFNg
/3ny2UYSff3wfa0m5NReh

Processed: 1030190 is fixed in unstable

[Debian Bug Tracking System]

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

> close 1030190 2:1.5+svn38408-1
Bug #1030190 [src:mplayer] mplayer uninstallable
Marked as fixed in versions mplayer/2:1.5+svn38408-1.
Bug #1030190 [src:mplayer] mplayer uninstallable
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1030579: marked as done (rust-psa-crypto: autopkgtest failure)

[Debian Bug Tracking System]

Your message dated Tue, 07 Feb 2023 23:08:18 +
with message-id 
and subject line Bug#1030579: fixed in rust-psa-crypto 0.9.2-2
has caused the Debian Bug report #1030579,
regarding rust-psa-crypto: autopkgtest failure
to be marked as done.

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

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


-- 
1030579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030579
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-psa-crypto
Version: 0.9.2-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-psa-crypto/30999064/log.gz

...
error: test failed, to rerun pass `--test mod`

Caused by:
  process didn't exit successfully: 
`/tmp/tmp.zgGN2JwJ3v/target/x86_64-unknown-linux-gnu/debug/deps/mod-5ff8f2a3ba46e536`
 (signal: 11, SIGSEGV: invalid memory reference)
autopkgtest [16:02:17]: test rust-psa-crypto:@: ---]
autopkgtest [16:02:17]: test rust-psa-crypto:@:  - - - - - - - - - - results - 
- - - - - - - - -
rust-psa-crypto:@FAIL non-zero exit status 101
...
autopkgtest [16:03:55]:  summary
rust-psa-crypto:@FAIL non-zero exit status 101
librust-psa-crypto-dev:default FAIL non-zero exit status 101
librust-psa-crypto-dev:interface FAIL non-zero exit status 101
librust-psa-crypto-dev:no-std FAIL non-zero exit status 101
librust-psa-crypto-dev:operations FAIL non-zero exit status 101
librust-psa-crypto-dev: FAIL non-zero exit status 101
--- End Message ---
--- Begin Message ---
Source: rust-psa-crypto
Source-Version: 0.9.2-2
Done: Emanuele Rocca 

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

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

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

Debian distribution maintenance software
pp.
Emanuele Rocca  (supplier of updated rust-psa-crypto package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 07 Feb 2023 23:36:01 +0100
Source: rust-psa-crypto
Architecture: source
Version: 0.9.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Emanuele Rocca 
Closes: 1030579
Changes:
 rust-psa-crypto (0.9.2-2) unstable; urgency=medium
 .
   * Run autopkgtests with --test-threads=1. The upstream test suite is not
 thread safe. (Closes: #1030579)
   * Ignore unstable tests: export_key_pair_test, generate_integration_test, and
 import_integration_test.
   * Package psa-crypto 0.9.2 from crates.io using debcargo 2.6.0
Checksums-Sha1:
 b7c30d69c3b291a2ce274b0ca8e94974bdcd5c93 2694 rust-psa-crypto_0.9.2-2.dsc
 a5b452202831a3746139cd80456754254ff1d5ce 3096 
rust-psa-crypto_0.9.2-2.debian.tar.xz
 f5f68a1248d1a454c145abd1755aebf0cd84f8ff 14861 
rust-psa-crypto_0.9.2-2_source.buildinfo
Checksums-Sha256:
 cf159505cdd88982f9ef11fc35999084422404110a9d161e9917732d041f5325 2694 
rust-psa-crypto_0.9.2-2.dsc
 44f0b26087ab391840ab83aea4f3aab56790d316e11b9384dd4f0134919fec61 3096 
rust-psa-crypto_0.9.2-2.debian.tar.xz
 b9939242d5a295d49ca34ae8f7f1609d7f0d80ce103c7543c2e542df1988 14861 
rust-psa-crypto_0.9.2-2_source.buildinfo
Files:
 a9fda787f88e6878e1865f3b0f0ddc94 2694 rust optional rust-psa-crypto_0.9.2-2.dsc
 010bc91cd15939d8b855ffd41b2ecffa 3096 rust optional 
rust-psa-crypto_0.9.2-2.debian.tar.xz
 7cc00f30c7d2e8fd32023ad49b753a0f 14861 rust optional 
rust-psa-crypto_0.9.2-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEElUWWlhkoHBf/rFiR1QhaB1D9t6MFAmPi0lcPHGVtYUBkZWJp
YW4ub3JnAAoJENUIWgdQ/bejmocP/0knMBG4Yjdab6Fc6LrU6/3pZ4aolkJqdzgy
XHPxB9QZdcKaRVCNbjFk2espl74Z5CULpEmWbcR9OLAuC3caGVJsRr9Lqeu/uE6u
uQRQ+frzbd8C/xpP9A57Fsmk+iBUlacZfPCrP1kcNQ7YfbYa9rkDKUWQ18GD39/Q
5Qm/Oks24ZIaRE15NE56P06Ss02cyONCCZjFdgJt2XQ0rsnWLPCZpXBbgulTS86i
8wB/16eC6rQ2vj8UpVolMkzwBZXohMF581/DC/P8ykGsRsBKkIuRDFIG/sieVXtZ
rc5JDxAm9mtr4ZZJE6ofp/qvkpqY/xvQmwvumcEA8aVPp5C0I5h0yOCq67F2mOqO
SY9fWTArSarvrc3DU0Gtaz1Ra76szA8fwE3NsmMnn1LBj0tsKh/QMH/twzzJXPlu
tvMykI5m6TP1Uu9N8EfL459+FlLz25QwEcEbrJmY2dDQa5uJ3pzIHAWS001YjOPB
idzs+0GvSCR3brF6+mShsAYwYuCe8JsxYHXiHeD0WCTPYmLXVqdqr/Jszsmqhfib
TsEMt6/7ttq3Lf67OYovoBqGROE240jltQ1YRICb/xoJiUlKe5d7EYRVQTAoriJe
t1B2R4bzDandQMqba11tQPAu8P5hCwI9t2OpYwfLtbn1JuAdGGJnKbj/7vBoC

Bug#1030830: marked as done (elpa-kotlin-mode: byte-compiling for emacs fails during installation)

[Debian Bug Tracking System]

Your message dated Tue, 07 Feb 2023 22:36:04 +
with message-id 
and subject line Bug#1030830: fixed in kotlin-mode 0.0~git20230123.fddd747-2
has caused the Debian Bug report #1030830,
regarding elpa-kotlin-mode: byte-compiling for emacs fails during installation
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.)


-- 
1030830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030830
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: elpa-kotlin-mode
Version: 0.0~git20230123.fddd747-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/k/kotlin-mode/31139417/log.gz

...
Setting up emacs-nox (1:28.2+1-10) ...
update-alternatives: using /usr/bin/emacs-nox to provide /usr/bin/emacs (emacs) 
in auto mode
update-alternatives: using /usr/bin/emacs to provide /usr/bin/editor (editor) 
in auto mode
Install emacsen-common for emacs
emacsen-common: Handling install of emacsen flavor emacs
Install elpa-kotlin-mode for emacs
install/kotlin-mode-20230123: Handling install of emacsen flavor emacs
install/kotlin-mode-20230123: byte-compiling for emacs

In toplevel form:
kotlin-mode.el:37:1: Error: Cannot open load file: No such file or directory, 
kotlin-mode-indent
ERROR: install script from elpa-kotlin-mode package failed
...
--- End Message ---
--- Begin Message ---
Source: kotlin-mode
Source-Version: 0.0~git20230123.fddd747-2
Done: Nicholas D Steeves 

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

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

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

Debian distribution maintenance software
pp.
Nicholas D Steeves  (supplier of updated kotlin-mode package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 07 Feb 2023 17:02:53 -0500
Source: kotlin-mode
Architecture: source
Version: 0.0~git20230123.fddd747-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen team 
Changed-By: Nicholas D Steeves 
Closes: 1030830
Changes:
 kotlin-mode (0.0~git20230123.fddd747-2) unstable; urgency=medium
 .
   * Team upload.
   * Install all elisp files.  Kotlin-mode-indent.el was missing from
 elpa-kotlin-mode in the last upload (Closes: #1030830).
Checksums-Sha1:
 c1e4f53ff09628d06dcb5a84b586bf761ff6efd7 2146 
kotlin-mode_0.0~git20230123.fddd747-2.dsc
 68ab2d92f081a86c797fdfd7b1ca60d5b43d6db4 2844 
kotlin-mode_0.0~git20230123.fddd747-2.debian.tar.xz
 2587884c0dda17c9326b7cec86c4174e44d04903 8135 
kotlin-mode_0.0~git20230123.fddd747-2_amd64.buildinfo
Checksums-Sha256:
 ed0dc95d893c5182c3a9a02fa337b046f5386077eb6cb3002a33f7399ee5f203 2146 
kotlin-mode_0.0~git20230123.fddd747-2.dsc
 c7074ee6873cefb044e72430a53d8f4e1a38d8249c25ff0953acaa769d90660f 2844 
kotlin-mode_0.0~git20230123.fddd747-2.debian.tar.xz
 1f2bc214693008c38db394174a08bc0a9b82c7a69e5ff05f0efdec07f0753e8c 8135 
kotlin-mode_0.0~git20230123.fddd747-2_amd64.buildinfo
Files:
 2fe17f198f02c817f24b83cae7a28b5e 2146 editors optional 
kotlin-mode_0.0~git20230123.fddd747-2.dsc
 b5ec62381450a13d8cd31f60e1828b6e 2844 editors optional 
kotlin-mode_0.0~git20230123.fddd747-2.debian.tar.xz
 5dd5d0489607f8e321bcdff2a87d0141 8135 editors optional 
kotlin-mode_0.0~git20230123.fddd747-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE4qYmHjkArtfNxmcIWogwR199EGEFAmPizEcACgkQWogwR199
EGEWGw/9GpZ2bKcjRaeu2A7yW5g6KCIYtNDO8ry0SjcoIVlcb2ekdZSKwQP8b6kc
8zPVvlEyIZAVbRWIk7dlR4Bm3UldZP0ozfX1xHSyXT1ER2Z8TazPXsmvRKTT7BaM
ghuhSr4ak6JtgK0rfgfvo8Lx2mW45bbs2ZPVSe4PVm9CEHVQkARVg2RYoRM7R9Im
Clvi1K4keTcDFYYtQ6J1zUrdQtyzzPMqXi7jIORXItVZg7z64d2YVS/kyeRJRoqJ
y4e7j3nXemzwUf5cWHrxcpqcgDSCfrCbQiwH/yXTBvacWSFSaTEMorUbfXdlE2Xt
9xvBNi5MYfW3npM4PLffgtbDcqL5vX9HjSH4CbJaYjB+lkT5/P/sqGegKYQ6s0k0
xgG4uFochmUFY8t/ZAeNH2Po5/J7v2DS8/LUSmr55c0plM79YdyXg/ptyuNyGMSh
ez39wLMeBUgzQen7eRNKurfv3fujuatcqHd2GqQPFxfkZne32C02rfzXOXD2wapT
limqXv8Dwt+mMLH7EVzHEBgDVZ9nSm4R/qzbYKFsjd0ip6oKB3iyhN9idLPMHhms
h6rV5AicDxFiSDvrlJKMYNCHYMhKpgf7JIhRM9BZJmuJAtQKgqdywqU14KLokXtk
kGvlh5KzDwNg1j/QCd0+uLCed0DPreoAVOAh8AWbJnnwNJoLayo=
=jGgW
-END PGP SIGNATURE End Message ---

Bug#1030806: pypy3: autopkgtest failure

[Stefano Rivera]

Hi Adrian (2023.02.07_16:10:23_+)

Ah, I forgot to bump the test dependency version requirement for pip.
It'll pass with the new pip in unstable (which will migrate soon).

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#1029292: marked as done (lomiri-greeter: Depends: lomiri-system-compositor but it is not installable)

[Debian Bug Tracking System]

Your message dated Tue, 07 Feb 2023 22:07:30 +
with message-id 
and subject line Bug#1029292: fixed in lomiri 0.1-2
has caused the Debian Bug report #1029292,
regarding lomiri-greeter: Depends: lomiri-system-compositor but it is not 
installable
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.)


-- 
1029292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029292
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lomiri-greeter
Version: 0.1~git20230111.ba0fc6a-4
Severity: serious

The following packages have unmet dependencies:
 lomiri-greeter : Depends: lomiri-system-compositor but it is not installable
--- End Message ---
--- Begin Message ---
Source: lomiri
Source-Version: 0.1-2
Done: Mike Gabriel 

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated lomiri package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 07 Feb 2023 22:33:43 +0100
Source: lomiri
Architecture: source
Version: 0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian UBports Team 
Changed-By: Mike Gabriel 
Closes: 1029292
Changes:
 lomiri (0.1-2) unstable; urgency=medium
 .
   [ Mike Gabriel ]
   * debian/control: Move lsc to recommends and comment it out for now (Closes:
 #1029292). This issue saw a regression, because upload 0.1-1 was based on
 0.1~git20230111.ba0fc6a-4 instead of 0.1~git20230111.ba0fc6a-5.
   * debian/changelog:
 + Weave-in stanza for lost 0.1~git20230111.ba0fc6a-5.
 + Amend white-space and typos of changelog item in
   0.1~git20230111.ba0fc6a-5.
Checksums-Sha1:
 a50be2ba5a153559d86f7eca3af9e6ebf706f8e5 4019 lomiri_0.1-2.dsc
 4f0e2f7068daeec56af9a943222e55fb54a732db 21780 lomiri_0.1-2.debian.tar.xz
 fdbe6865a78f02de7fcae1870fe7c45289451ddc 19778 lomiri_0.1-2_source.buildinfo
Checksums-Sha256:
 697066d536960a4cb70bcfcf3c8034e95f3152291166fc1e592c434f606881de 4019 
lomiri_0.1-2.dsc
 fd877c0b2572ecaf7ce58f91bba0269ebebaae3b879dad460635d1df4910ad17 21780 
lomiri_0.1-2.debian.tar.xz
 1ce4fcb013689857158f980862f584e955327db066190c04dc3f8f798a4c7e70 19778 
lomiri_0.1-2_source.buildinfo
Files:
 8f0b218c370a642d6747f0a8887ad10f 4019 x11 optional lomiri_0.1-2.dsc
 7a5c5727171f826478e33903415125da 21780 x11 optional lomiri_0.1-2.debian.tar.xz
 94d44602060cd62d220be8b1f2ef5cff 19778 x11 optional 
lomiri_0.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAmPixEwVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxvRMQAKN5RjF3lcIa01vJE0NzJELswhFM
JdpC3/fhsQRN0WAGyz+FjJ7tY30Rd5ulbRQqkdiP+QrTFjNq2DS0AWF7xUCebTpU
K7X0F+cUd2e8lWHiUEg7mtRvxaj8jkJn6cVtFTeQHOxul+lxMqaj/c5px3cRk1ON
xq9A4Xgbl8J1UiDohjbPcqgsoiuQ8U+2f3pja7W1/xjHNbydn29GqiQUuA7p+AEf
0mWMn1d4TYspPgN1savyzLBDVN52n/499UwgSXpTc35oTxu7S2aPpK0SCLlQCgfW
20STpD191RA9y+V7CSxtExH352zvL/SUsNEWI8+ta07iZ54yR+NeSI3OXRcyfUhJ
jzcDsWW3rJv4QXCc5hOiLiwMfaeT6Eh0R9MCYGBvOyWyuGNkvxMZY55sZcULIjkJ
W2IL6UkQFuHAl425YNCTuDf83gg6P5iXG3+vx/xBNPg/wAiQnuxp4vEwwf5HYq59
JGPPLNmGIxjYk+w/rSHegYRs41ukm+rP1DE2zbbA8gPlnrWZvTJcY4sC1PMDnF5U
ycr26e11r8b1vAlWYkHcoiHPawDf7pyu8Or3HfZWROZw2AAWE7NRBGJgqewu1UQe
yKYcdS4mGwxf+ohc8QLTY5rEmetq0X43kw2JQmp/LMxlxEd8292Zukl3Tr9mW825
sgeOOP7q4tvzNUNB
=/lxG
-END PGP SIGNATURE End Message ---

Bug#1030830: elpa-kotlin-mode: byte-compiling for emacs fails during installation

[Adrian Bunk]

Package: elpa-kotlin-mode
Version: 0.0~git20230123.fddd747-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/k/kotlin-mode/31139417/log.gz

...
Setting up emacs-nox (1:28.2+1-10) ...
update-alternatives: using /usr/bin/emacs-nox to provide /usr/bin/emacs (emacs) 
in auto mode
update-alternatives: using /usr/bin/emacs to provide /usr/bin/editor (editor) 
in auto mode
Install emacsen-common for emacs
emacsen-common: Handling install of emacsen flavor emacs
Install elpa-kotlin-mode for emacs
install/kotlin-mode-20230123: Handling install of emacsen flavor emacs
install/kotlin-mode-20230123: byte-compiling for emacs

In toplevel form:
kotlin-mode.el:37:1: Error: Cannot open load file: No such file or directory, 
kotlin-mode-indent
ERROR: install script from elpa-kotlin-mode package failed
...

Bug#1029292: lomiri-greeter: Depends: lomiri-system-compositor but it is not installable

[Mike Gabriel]

Hi Adrian,

On  Di 07 Feb 2023 18:17:42 CET, Adrian Bunk wrote:


On Fri, Jan 20, 2023 at 08:48:19PM +0200, Adrian Bunk wrote:

Package: lomiri-greeter
Version: 0.1~git20230111.ba0fc6a-4
Severity: serious

The following packages have unmet dependencies:
 lomiri-greeter : Depends: lomiri-system-compositor but it is not  
installable


As the version tracking of the BTS already correctly shows, 0.1-1 now in
unstable is based on 0.1~git20230111.ba0fc6a-4 and lacks this fix that
was in 0.1~git20230111.ba0fc6a-5.

cu
Adrian


thanks for pinging me on this. I now re-fixed #1029292 (nice bug  
number, in fact) by a follow-up upload.


@marius: please remember to git-push everything you upload  
immediately(!) to Salsa. The lomiri.git on Salsa wasn't the only repo  
that was not up-to-date. In fact, please check with  
https://tracker.debian.org/ all the packages you uploaded  
recently (or use the UBports Team DDPO page) and check where you might  
have local commits danling that might need pushing. Thanks.


I will file an unblock for this upload (0.1-2) in case it gets hit by  
the softfreeze testing-migration block.


@Adrian, thanks again for spotting these kinds of issues and reporting  
them immediately. Thanks for the QA work you do!!!

Mike
--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgp1sM9nNVJNJ.pgp
Description: Digitale PGP-Signatur

Bug#1030829: mmc-utils: FTBFS on ppc64el with error: ‘cnt’ may be used uninitialized

[Nick Rosbrook]

Package: mmc-utils
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu lunar ubuntu-patch

Dear Maintainer,

In Ubuntu, mcc-utils FTBFS[1] on ppc64el with the following:

 In file included from /usr/include/endian.h:35,
  from /usr/include/powerpc64le-linux-gnu/sys/types.h:176,
  from /usr/include/stdlib.h:395,
  from mmc_cmds.c:21:
 In function ‘__bswap_32’,
 inlined from ‘do_rpmb_write_block’ at mmc_cmds.c:2462:27:
 /usr/include/powerpc64le-linux-gnu/bits/byteswap.h:52:10: error: ‘cnt’ may be 
used uninitialized [-Werror=maybe-uninitialized]
52 |   return __builtin_bswap32 (__bsx);
   |  ^
 mmc_cmds.c: In function ‘do_rpmb_write_block’:
 mmc_cmds.c:2439:22: note: ‘cnt’ was declared here
  2439 | unsigned int cnt;
   |  ^~~
 cc1: all warnings being treated as errors
 make[1]: *** [Makefile:36: mmc_cmds.o] Error 1
 make[1]: Leaving directory '/<>'
 dh_auto_build: error: make -j4 "INSTALL=install --strip-program=true" returned 
exit code 2
 make: *** [debian/rules:8: binary-arch] Error 25
 dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2
 


This was already fixed upstream[2]. We applied the patch in Ubuntu to fix
the build on ppc64el.

Thanks,
Nick

[1] 
https://launchpadlibrarian.net/648312622/buildlog_ubuntu-lunar-ppc64el.mmc-utils_0+git20220624.d7b343fd-1_BUILDING.txt.gz
[2] 
https://git.kernel.org/pub/scm/utils/mmc/mmc-utils.git/commit/?id=5086e7c0de4d0094f8674368a88d931b27589d53
diff -Nru 
mmc-utils-0+git20220624.d7b343fd/debian/patches/0003-fix-warning-on-uninitialized-cnt.patch
 
mmc-utils-0+git20220624.d7b343fd/debian/patches/0003-fix-warning-on-uninitialized-cnt.patch
--- 
mmc-utils-0+git20220624.d7b343fd/debian/patches/0003-fix-warning-on-uninitialized-cnt.patch
 1969-12-31 19:00:00.0 -0500
+++ 
mmc-utils-0+git20220624.d7b343fd/debian/patches/0003-fix-warning-on-uninitialized-cnt.patch
 2023-02-07 15:14:11.0 -0500
@@ -0,0 +1,54 @@
+Description: mmc-utils: fix warning on uninitialized 'cnt'
+Origin: 
https://git.kernel.org/pub/scm/utils/mmc/mmc-utils.git/commit/?id=5086e7c0de4d0094f8674368a88d931b27589d53
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/mmc-utils/+bug/2006505
+Last-Update: 2023-02-07
+---
+From 5086e7c0de4d0094f8674368a88d931b27589d53 Mon Sep 17 00:00:00 2001
+From: Giulio Benetti 
+Date: Sun, 18 Sep 2022 18:17:51 +0200
+Subject: mmc-utils: fix warning on uninitialized 'cnt'
+
+When building following warning shows up:
+```
+In function '__bswap_32',
+inlined from 'do_rpmb_write_block' at mmc_cmds.c:2293:27:
+/home/autobuild/autobuild/instance-15/output-1/host/aarch64-buildroot-linux-gnu/sysroot/usr/include/bits/byteswap.h:52:10:
 error: 'cnt' may be used uninitialized [-Werror=maybe-uninitialized]
+   52 |   return __builtin_bswap32 (__bsx);
+  |  ^
+mmc_cmds.c: In function 'do_rpmb_write_block':
+mmc_cmds.c:2270:22: note: 'cnt' was declared here
+2270 | unsigned int cnt;
+  |  ^~~
+cc1: all warnings being treated as errors
+```
+This is due to function rpmb_read_counter() that doesn't set its
+argument 'unsigned int *cnt' in all return points. So let's set
+*cnt to 0 in the return point that misses to initialize it.
+
+Signed-off-by: Giulio Benetti 
+Reviewed-by: Avri Altman 
+Link: 
https://lore.kernel.org/r/20220918161751.1132590-1-giulio.bene...@benettiengineering.com
+Signed-off-by: Ulf Hansson 
+---
+ mmc_cmds.c | 4 +++-
+ 1 file changed, 3 insertions(+), 1 deletion(-)
+
+diff --git a/mmc_cmds.c b/mmc_cmds.c
+index ef1d8c6..29abd1d 100644
+--- a/mmc_cmds.c
 b/mmc_cmds.c
+@@ -2238,8 +2238,10 @@ int rpmb_read_counter(int dev_fd, unsigned int *cnt)
+   }
+ 
+   /* Check RPMB response */
+-  if (frame_out.result != 0)
++  if (frame_out.result != 0) {
++  *cnt = 0;
+   return be16toh(frame_out.result);
++  }
+ 
+   *cnt = be32toh(frame_out.write_counter);
+ 
+-- 
+cgit 
+
diff -Nru mmc-utils-0+git20220624.d7b343fd/debian/patches/series 
mmc-utils-0+git20220624.d7b343fd/debian/patches/series
--- mmc-utils-0+git20220624.d7b343fd/debian/patches/series  2022-08-04 
02:07:11.0 -0400
+++ mmc-utils-0+git20220624.d7b343fd/debian/patches/series  2023-02-07 
15:09:50.0 -0500
@@ -1,2 +1,3 @@
 0001-Fix-typo.patch
 0002-man-mmc.1-Fix-warning-macro-not-defined.patch
+0003-fix-warning-on-uninitialized-cnt.patch

Processed: found 1014998 in 20210112.2.b757bac~ds1-1

[Debian Bug Tracking System]

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

> found 1014998 20210112.2.b757bac~ds1-1
Bug #1014998 {Done: Amin Bandali } [src:ring] ring: 
CVE-2021-32686 CVE-2021-37706 CVE-2022-21723 CVE-2022-23608 CVE-2021-43299 
CVE-2021-43300 CVE-2021-43301 CVE-2021-43302 CVE-2021-43303 CVE-2021-43804 
CVE-2021-43845 CVE-2022-21722 CVE-2022-24754 CVE-2022-24763 CVE-2022-24764 
CVE-2022-24793
Marked as found in versions ring/20210112.2.b757bac~ds1-1.
> thanks
Stopping processing here.

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

Processed: src:wf-config: fails to migrate to testing for too long: FTBFS on s390x

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.7.1-3
Bug #1030828 [src:wf-config] src:wf-config: fails to migrate to testing for too 
long: FTBFS on s390x
Marked as fixed in versions wf-config/0.7.1-3.
Bug #1030828 [src:wf-config] src:wf-config: fails to migrate to testing for too 
long: FTBFS on s390x
Marked Bug as done

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

Bug#1030828: src:wf-config: fails to migrate to testing for too long: FTBFS on s390x

[Paul Gevers]

Source: wf-config
Version: 0.7.1-2
Severity: serious
Control: close -1 0.7.1-3
Tags: sid bookworm ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:wf-config has been trying to migrate for 
61 days [2]. Hence, I am filing this bug. Your package failed to build 
from source on s390x while it built there successfully in the past.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and bookworm, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=wf-config



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1028163: marked as done (sshfs-fuse: FTBFS (tries to use the ssh service from the host machine))

[Debian Bug Tracking System]

Your message dated Tue, 07 Feb 2023 21:17:42 +
with message-id 
and subject line Bug#1028163: fixed in sshfs-fuse 3.7.3-1.1
has caused the Debian Bug report #1028163,
regarding sshfs-fuse: FTBFS (tries to use the ssh service from the host machine)
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.)


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

Package: src:sshfs-fuse
Version: 3.7.1+repack-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary-arch
dh binary-arch --buildsystem=meson
   dh_update_autotools_config -a -O--buildsystem=meson
   dh_autoreconf -a -O--buildsystem=meson
   dh_auto_configure -a -O--buildsystem=meson
cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
--localstatedir=/var --libdir=lib/x86_64-linux-gnu
The Meson build system
Version: 0.56.2
Source dir: /<>
Build dir: /<>/obj-x86_64-linux-gnu
Build type: native build
Project name: sshfs
Project version: 3.7.1
Using 'CFLAGS' from environment with value: '-g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security'
Using 'LDFLAGS' from environment with value: '-Wl,-z,relro -Wl,-z,now'
Using 'CPPFLAGS' from environment with value: '-Wdate-time -D_FORTIFY_SOURCE=2'
C compiler for the host machine: cc (gcc 10.2.1 "cc (Debian 10.2.1-6) 10.2.1 
20210110")
C linker for the host machine: cc ld.bfd 2.35.2
Using 'CFLAGS' from environment with value: '-g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security'
Using 'LDFLAGS' from environment with value: '-Wl,-z,relro -Wl,-z,now'
Using 'CPPFLAGS' from environment with value: '-Wdate-time -D_FORTIFY_SOURCE=2'
Host machine cpu family: x86_64
Host machine cpu: x86_64
../meson.build:8: WARNING: Consider using the built-in warning_level option instead of 
using "-Wall".
../meson.build:8: WARNING: Consider using the built-in warning_level option instead of 
using "-Wextra".
Message: Compiler warns about unused result even when casting to void
Program rst2man found: YES (/usr/bin/rst2man)
Configuring config.h using configuration
Found pkg-config: /usr/bin/pkg-config (0.29.2)
Run-time dependency fuse3 found: YES 3.10.3
Run-time dependency glib-2.0 found: YES 2.66.8
Run-time dependency gthread-2.0 found: YES 2.66.8
Program utils/install_helper.sh found: YES 
(/<>/utils/install_helper.sh)
Build targets in project: 4

Option buildtype is: plain [default: debugoptimized]
Found ninja-1.10.1 at /usr/bin/ninja
   dh_auto_build -a -O--buildsystem=meson
cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j1 -v
[1/7] cc -Isshfs.p -I. -I.. -I/usr/include/fuse3 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -fdiagnostics-color=always -pipe 
-D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -D_REENTRANT -DHAVE_CONFIG_H -Wall -Wextra 
-Wno-sign-compare -Wmissing-declarations -Wwrite-strings -Wno-unused-result -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -DFUSE_USE_VERSION=31 -MD 
-MQ sshfs.p/sshfs.c.o -MF sshfs.p/sshfs.c.o.d -o sshfs.p/sshfs.c.o -c ../sshfs.c
[2/7] cc -Isshfs.p -I. -I.. -I/usr/include/fuse3 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -fdiagnostics-color=always -pipe 
-D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -D_REENTRANT -DHAVE_CONFIG_H -Wall -Wextra 
-Wno-sign-compare -Wmissing-declarations -Wwrite-strings -Wno-unused-result -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -DFUSE_USE_VERSION=31 -MD 
-MQ sshfs.p/cache.c.o -MF sshfs.p/cache.c.o.d -o sshfs.p/cache.c.o -c ../cache.c
[3/7] cc  -o sshfs sshfs.p/sshfs.c.o sshfs.p/cache.c.o -Wl,--as-needed -Wl,--no-undefined 
-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-z,relro -Wl,-z,now -Wl,--start-group 
/usr/lib/x86_64-linux-gnu/libfuse3.so -lpthread /usr/lib/x86_64-linux-gnu/libglib-2.0.so 
/usr/lib/x86_64-linux-gnu/libgthread-2.0.so -Wl,--end-group -pthread
[4/7] /usr/bin/rst2man ../sshfs.rst sshfs.1
[5/7] cp -fPp ../test/conftest.py ../test/pytest.ini ../test/test_sshfs.py ../test/util.py 
/<>/obj-x86_64-linux-gnu/test
[6/7] cc -Itest/wrong_command.p -Itest -I../test -fdiagnostics-

Processed: notfixed 1025125 in 3.0.5, fixed 1025125 in 3.0.5-1

[Debian Bug Tracking System]

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

> notfixed 1025125 3.0.5
Bug #1025125 [src:ruby-sinatra] ruby-sinatra: CVE-2022-45442: Reflected File 
Download attack
The source 'ruby-sinatra' and version '3.0.5' do not appear to match any binary 
packages
No longer marked as fixed in versions ruby-sinatra/3.0.5.
> fixed 1025125 3.0.5-1
Bug #1025125 [src:ruby-sinatra] ruby-sinatra: CVE-2022-45442: Reflected File 
Download attack
Marked as fixed in versions ruby-sinatra/3.0.5-1.
> thanks
Stopping processing here.

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

Bug#1030458: marked as done (jruby-utils-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact org.eclipse.jetty:jetty-jmx:jar:debian has not been download

[Debian Bug Tracking System]

Your message dated Tue, 07 Feb 2023 21:10:33 +
with message-id 
and subject line Bug#1030458: fixed in jruby-utils-clojure 4.0.3-3
has caused the Debian Bug report #1030458,
regarding jruby-utils-clojure: FTBFS: Cannot access clojars 
(https://repo.clojars.org/) in offline mode and the artifact 
org.eclipse.jetty:jetty-jmx:jar:debian has not been downloaded from it before.
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.)


-- 
1030458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030458
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jruby-utils-clojure
Version: 4.0.3-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):
> make[1]: Entering directory '/<>'
> lein pom debian/pom.xml
> Wrote /<>/debian/pom.xml
> lein jar
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact puppetlabs:trapperkeeper-webserver-jetty9:jar:debian has not 
> been downloaded from it before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact puppetlabs:trapperkeeper-webserver-jetty9:jar:debian has not been 
> downloaded from it before.
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact puppetlabs:trapperkeeper-webserver-jetty9:jar:test:debian has 
> not been downloaded from it before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact puppetlabs:trapperkeeper-webserver-jetty9:jar:test:debian has not 
> been downloaded from it before.
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact org.eclipse.jetty:jetty-server:jar:debian has not been 
> downloaded from it before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact org.eclipse.jetty:jetty-server:jar:debian has not been downloaded 
> from it before.
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact org.eclipse.jetty:jetty-servlet:jar:debian has not been 
> downloaded from it before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact org.eclipse.jetty:jetty-servlet:jar:debian has not been downloaded 
> from it before.
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact org.eclipse.jetty:jetty-servlets:jar:debian has not been 
> downloaded from it before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact org.eclipse.jetty:jetty-servlets:jar:debian has not been downloaded 
> from it before.
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact org.eclipse.jetty:jetty-webapp:jar:debian has not been 
> downloaded from it before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact org.eclipse.jetty:jetty-webapp:jar:debian has not been downloaded 
> from it before.
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact org.eclipse.jetty:jetty-proxy:jar:debian has not been downloaded 
> from it before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact org.eclipse.jetty:jetty-proxy:jar:debian has not been downloaded 
> from it before.
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact org.eclipse.jetty:jetty-jmx:jar:debian has not been downloaded 
> from it before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact org.eclipse.jetty:jetty-jmx:jar:debian has not been downloaded from 
> it before.
> This could be due to a typo in :dependencies, file system permissions, or 
> network issues.
> If you are behind a proxy, try setting the 'http_proxy' environment variable.
> make[1]: *** [debian/rules:18: override_dh_auto_build] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/02/03/jruby-utils-clojure_4.0.3-2_unstable.log

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

A list of current common problems and possible solutions is avai

Bug#1030676: pysdl2: autopkgtest failure on s390x

[Simon McVittie]

On Mon, 06 Feb 2023 at 13:00:22 +0100, Gianfranco Costamagna wrote:
> Hello, as shown in e.g. 
> https://ci.debian.net/data/autopkgtest/unstable/s390x/p/pysdl2/30731752/log.gz
> autopkgtests are failing probably due to a Big Endian issue

I don't think this is a real regression: the tests haven't passed on
s390x since 2021, at which point they were much shorter (30 seconds
rather than 2 minutes) and presumably had less coverage.

Given that pysdl2 is a game-related library and s390x machines are
~ $15K mainframes not known for their suitability for gaming, I'm not
convinced this should be RC.

On Tue, 07 Feb 2023 at 11:06:56 +, James Addison wrote:
> It looks like this has been fixed upstream in version 0.9.12 of the library.

I have intentionally not uploaded those versions to unstable when doing
team-uploads to stop it from regressing and blocking libsdl2, because
I have no good way to test them: nothing in Debian depends on pysdl2,
and I'm not actively using it for any non-Debian software.

Unfortunately backporting test fixes from newer versions tends to be a
pain because upstream have re-indented all the tests, but I'll see what
I can do.

smcv

Bug#1030693: marked as done (librust-ahash-0.7-dev: missing Breaks+Replaces: librust-ahash-dev (<< 0.8))

[Debian Bug Tracking System]

Your message dated Tue, 07 Feb 2023 20:48:48 +
with message-id 
and subject line Bug#1030693: fixed in rust-ahash-0.7 0.7.6-11
has caused the Debian Bug report #1030693,
regarding librust-ahash-0.7-dev: missing Breaks+Replaces: librust-ahash-dev (<< 
0.8)
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.)


-- 
1030693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030693
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librust-ahash-0.7-dev
Version: 0.7.6-10
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack .../librust-ahash-0.7-dev_0.7.6-10_all.deb ...
  Unpacking librust-ahash-0.7-dev (0.7.6-10) ...
  dpkg: error processing archive 
/var/cache/apt/archives/librust-ahash-0.7-dev_0.7.6-10_all.deb (--unpack):
   trying to overwrite 
'/usr/share/cargo/registry/ahash-0.7.6/.cargo-checksum.json', which is also in 
package librust-ahash-dev 0.7.6-7
  Errors were encountered while processing:
   /var/cache/apt/archives/librust-ahash-0.7-dev_0.7.6-10_all.deb


cheers,

Andreas


librust-ahash-dev=0.7.6-7_librust-ahash-0.7-dev=0.7.6-10.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: rust-ahash-0.7
Source-Version: 0.7.6-11
Done: Jonas Smedegaard 

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

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

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated rust-ahash-0.7 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 07 Feb 2023 21:17:58 +0100
Source: rust-ahash-0.7
Architecture: source
Version: 0.7.6-11
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Closes: 1030693
Changes:
 rust-ahash-0.7 (0.7.6-11) unstable; urgency=medium
 .
   * break+replace older releases of librust-ahash-dev;
 closes: bug#1030693, thanks to Andreas Beckmann
Checksums-Sha1:
 5a9f3933b7b74b6901fe659b53e22be9ac5fb064 2866 rust-ahash-0.7_0.7.6-11.dsc
 0773d56c9268c39f35ee075ec04524b17cf19561 14496 
rust-ahash-0.7_0.7.6-11.debian.tar.xz
 09eab86194666f4f60033eb653dc1209238f50a7 18497 
rust-ahash-0.7_0.7.6-11_amd64.buildinfo
Checksums-Sha256:
 7adcd151cd84654c68627d1677c280e000440d8033b75abb406b7628652db5fe 2866 
rust-ahash-0.7_0.7.6-11.dsc
 485d0a151d1cbc273600ddb1a60c2716d667d8a54292d69c45c4be8a3771 14496 
rust-ahash-0.7_0.7.6-11.debian.tar.xz
 2e105f92f51499ffb7d9a9b9801355ee15ea2a0817cfb8a68dcb472391f269d1 18497 
rust-ahash-0.7_0.7.6-11_amd64.buildinfo
Files:
 471665e358f2d1f706d78dfca3fa5f58 2866 rust optional rust-ahash-0.7_0.7.6-11.dsc
 cb7696be1db4e3d00d72f8127488d6ab 14496 rust optional 
rust-ahash-0.7_0.7.6-11.debian.tar.xz
 0df18219d0714af06a30064b818bd2a5 18497 rust optional 
rust-ahash-0.7_0.7.6-11_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmPispEACgkQLHwxRsGg
ASG8jg/+K1PwW1/386f7e8v+vaexyykacz02j6tSYNpmZ1vAQAlvVgO9eeSkh5Fj
W1mhw1NKYipzv7gaA5/mKIHI7wzsN+CPwyCgzG6q/h90b4u0rxHDPGwaxa3Llwpc
Uy7oV73xxnSLwndS2GnUZdvc/g4fTqqWRFAExsioFpPu4kV4uVBAKTpwmfedJWKC
Kl6I1SaJwFNSW7O9NUqGnJ3KLtN+Y1rGM5jPo6rzFE5t+8qhiayRFJ7Y4YCb4NXk
r/gfXXjNnqIOcK5jFvbBcy139nVcVsB1xS/oL9F+iyr8qxdw1F3f4gtncB+F9Ymr
x6CduhG28uwapEJQGIc51P7w/6m1AoTGIcfSDX/8UidLyQLlumxa9oJe8aLVtWlq
FpDUY3ufQ6PCKIeAUIJzNWGWCxY8MJ+6XHV3TA9JDXF924JklwaYDCF0XxCIO81i
6PjNPNBueN+BjygfVX0FWmfrLDgysUx/lttkrG761C8ybdwLNZXkWlRPoe2AGfwH
95mObS9XTcdAZ5SBKFCxokuAgxSAcIS+d2zrKsmJu1ElsvfXlu1wV7XXAzyHTFSX
6SHM+Ypqy7S9JSdXCaCWmlDvT8LDPkBCGc1p2Z1MQH6zgjvPere+uJrsOmMoxVpr
z7OBgVVvlbJsJAFMMH95X3OrQva8nQNlhbQDUUCFLzCQYQbuL4M=
=49mS
-END PGP SIGNAT

Bug#1030824: marked as done (libhashkit-dev needs Breaks + Replaces: libhashkit2 (<< 1.1.3-1~))

[Debian Bug Tracking System]

Your message dated Tue, 07 Feb 2023 20:40:13 +
with message-id 
and subject line Bug#1030824: fixed in libmemcached 1.1.3-2
has caused the Debian Bug report #1030824,
regarding libhashkit-dev needs Breaks + Replaces: libhashkit2 (<< 1.1.3-1~)
to be marked as done.

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

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


-- 
1030824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030824
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libhashkit-dev
Version: 1.1.3-1
Severity: serious

Unpacking libhashkit-dev:amd64 (1.1.3-1) over (1.0.18+-1+b1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-hcHxlW/19-libhashkit-dev_1.1.3-1_amd64.deb (--unpack):
 trying to overwrite '/usr/share/man/man3/hashkit_clone.3.gz', which is also in 
package libhashkit2:amd64 1.0.18+-1+b1
--- End Message ---
--- Begin Message ---
Source: libmemcached
Source-Version: 1.1.3-2
Done: Ondřej Surý 

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

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

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

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated libmemcached package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 07 Feb 2023 20:58:11 +0100
Source: libmemcached
Architecture: source
Version: 1.1.3-2
Distribution: unstable
Urgency: medium
Maintainer: Ondřej Surý 
Changed-By: Ondřej Surý 
Closes: 1030824
Changes:
 libmemcached (1.1.3-2) unstable; urgency=medium
 .
   * Add Breaks + Replaces: libhashkit2 (<< 1.1.3-1~) to libhashkit-dev
 (Closes: #1030824)
Checksums-Sha1:
 ec173e513f102398d53d3c2155918ead03897cb9 2475 libmemcached_1.1.3-2.dsc
 321ad0e8ad525c839b811937b8ad9022898168f8 11032 
libmemcached_1.1.3-2.debian.tar.xz
 a07821e141d5d516957db3e96f62ec0502bbe0ea 11722 
libmemcached_1.1.3-2_amd64.buildinfo
Checksums-Sha256:
 b966e1c5f19bf6d271ae2e52d289edb0f58429405837383d6a834ab42d5a2d74 2475 
libmemcached_1.1.3-2.dsc
 3e4a2e505f69f8689f16d11e2923db10d3d757615401ff67514678de5e1b7865 11032 
libmemcached_1.1.3-2.debian.tar.xz
 12fb40c3fd5c65222ae204188c63a21a61cd775b2e80dd9d4514289980f8e550 11722 
libmemcached_1.1.3-2_amd64.buildinfo
Files:
 9be5d2facd0b199f6d75619451a2073f 2475 libs optional libmemcached_1.1.3-2.dsc
 3a541a83204524e0fbc7c4031aef88c6 11032 libs optional 
libmemcached_1.1.3-2.debian.tar.xz
 6ea60ab625dbf5d3ac75aa58f7db5524 11722 libs optional 
libmemcached_1.1.3-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAmPirk1fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz
NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u
WcLQpQ/+JyolX2HcJlz1Se6Oe+1bxtga07av7J7lXa/iBYWH3GNurEEjanDeeaD3
0QCa2/FUV0z6GWZUVtEO9256qMqgrHVDHYfnFdGjSvBE5WLsWQWYvF0DpPgF66S6
jNrTb9yb2cJ7DpN6YWJRdaXf0O7gXKhgD4f9ta/CJhxiUuqOXqB9FDDY8rnxNKmG
C787IUqgZbQWRCGZ6gyDE0Com1NReotxMoY8A/yWiPJ8V9oIo+oN54dDRVcMvAO4
p08p6VKzVzStZDtUMTH+t/lEitj9+CjeVjtV1h/MlNzmc+r2/cF4QdzacpfsGP9+
l0xUYrVB+YISxcR1SWtbet6u0jJf1zjTMRfNEnwbCvMqL6bvzul9ShtAC5rtezzd
/o9FHTUMR/6qpFqYlwrpS37jlL+ZLWRSFWbsIvnhyXKPsuDTW3jIoPDJVOyVmKrk
jXytJN+ulkVeTXUPpkcy49POqxGwAcEJNfeR5Ctwmq4QhaRpIb4DfIYwdHm7/7km
mkxoiGcDQozM1+n2zYtUGyAXHjbmKu8m/QE0bIaFj2eIJxnv8djIEblzr4p6ce6y
i9z1TPaNsUuJr0WbNf1SjUPXUEmOHnnDOkcXRmQ7f5rTCTax3453o19JafFVZWc1
mpvwS6M+VT8/LY5TkcjEY/Vfcx8jWsukkl1VXRyF4DHz/hGwvl0=
=PDaG
-END PGP SIGNATURE End Message ---

Bug#1030670: marked as done (Does not depend on libspng0)

[Debian Bug Tracking System]

Your message dated Tue, 07 Feb 2023 20:40:26 +
with message-id 
and subject line Bug#1030670: fixed in libspng 0.7.3-3
has caused the Debian Bug report #1030670,
regarding Does not depend on libspng0
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.)


-- 
1030670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030670
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libspng-dev
Version: 0.7.3-1
Severity: serious
Tags: patch

Hi Andrea!

While trying to build against the new libspng-dev, I found that even my
build was issuing -lspng, it would fail because it could not find it.

It turns out you're missing a dependency against libspng0 itself.

Patch attached for that.

Additionally, I've seen the following too:

- spng.pc declares:

Requires.private: zlib

If I understand correctly, this is not a public dependency, which means
libspng-dev does not need to depend on zlib-dev. In fact, that's one of
the features SPNG advertises.

- I would downgrade the Recommends on libspng-doc to a Suggests, to
  avoid pulling in fonts and other unneeded packages on the 95% of
  cases.

Thank you,
Jordi

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

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

Versions of packages libspng-dev depends on:
ii  zlib1g-dev  1:1.2.13.dfsg-1

Versions of packages libspng-dev recommends:
pn  libspng-doc  

libspng-dev suggests no packages.

-- no debconf information
--- debian/control.orig 2023-02-02 20:38:28.0 +0100
+++ debian/control  2023-02-06 12:08:42.216466366 +0100
@@ -40,6 +40,7 @@
 Architecture: any
 Multi-Arch: same
 Depends: zlib1g-dev,
+ libspng0 (= ${binary:Version}),
  ${misc:Depends}
 Recommends: libspng-doc
 Description: simple, modern libpng alternative - development
--- End Message ---
--- Begin Message ---
Source: libspng
Source-Version: 0.7.3-3
Done: Andrea Pappacoda 

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

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

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

Debian distribution maintenance software
pp.
Andrea Pappacoda  (supplier of updated libspng package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 07 Feb 2023 21:18:58 +0100
Source: libspng
Architecture: source
Version: 0.7.3-3
Distribution: unstable
Urgency: medium
Maintainer: Andrea Pappacoda 
Changed-By: Andrea Pappacoda 
Closes: 1030670
Changes:
 libspng (0.7.3-3) unstable; urgency=medium
 .
   * d/control: add Depends libspng0 to libspng-dev.
 Thanks to Jordi for the report (Closes: #1030670)
Checksums-Sha1:
 56e50b2b78fb5a4ae836b26e31292234b6d0bf66 1549 libspng_0.7.3-3.dsc
 6eaec94e6a83a53d682ad22abfba041c26dc5de2 4544 libspng_0.7.3-3.debian.tar.xz
 50c6f980654c5def6e22fdfe30fa1837e797 7833 libspng_0.7.3-3_amd64.buildinfo
Checksums-Sha256:
 05f324accbf40d02f4d284047b9fb792e03481ede86c1425af01e4656c475028 1549 
libspng_0.7.3-3.dsc
 d24b992ef0839350dda99083a0c62a0bb1e403800ba9e9dfcf57754ba297d187 4544 
libspng_0.7.3-3.debian.tar.xz
 900e45b75ccbcbda81307ce1b0e95a3c857a38e7458e9917369fe0c9afeac9de 7833 
libspng_0.7.3-3_amd64.buildinfo
Files:
 205c4e600431e436f16921fbfd4a75ba 1549 libs optional libspng_0.7.3-3.dsc
 2ec42282a7671e883933e83348d3f258 4544 libs optional 
libspng_0.7.3-3.debian.tar.xz
 bdbbe7672621af3c29557453c82e5e80 7833 libs optional 
libspng_0.7.3-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQS6VuNIvZRFHt7JcAdKkgiiRVB3pwUCY+KzEQAKCRBKkgiiRVB3
p0/QAQCPYfj3ZKPBPHg4Jdur/PZVY1jlKvjeYTb0lciTW1USaAD9FF1cqw0RHtMJ
CkFPc1buJZz7nAHuGdOJkaXk7Rz/sw4=
=nQrg
-END PGP SIGNATURE End Message ---

Bug#1026962: marked as done (openjfx: tries to build with -j64 on a host with 2 processors)

[Debian Bug Tracking System]

Your message dated Tue, 07 Feb 2023 20:42:54 +
with message-id 
and subject line Bug#1026962: fixed in openjfx 11.0.11+1-3
has caused the Debian Bug report #1026962,
regarding openjfx: tries to build with -j64 on a host with 2 processors
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.)


-- 
1026962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026962
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openjfx
Version: 11.0.11+0-1.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

openjfx tries to build with -j64 on zani.debian.org, which only has 2
processors and 8GB of RAM:

buildd   3853047  0.0  0.0  67668 4 ?S11:07   0:00 cmake 
--build 
/build/openjfx-fzmlCD/openjfx-11.0.11+1/modules/javafx.web/build/linux/Release 
--config Release -- -j64
buildd   3853048  0.0  0.0   3200   272 ?S11:07   0:00 
/usr/bin/gmake -f Makefile -j64

This hogs the buildd resources and we had to kill the build.
--- End Message ---
--- Begin Message ---
Source: openjfx
Source-Version: 11.0.11+1-3
Done: tony mancill 

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

Debian distribution maintenance software
pp.
tony mancill  (supplier of updated openjfx package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 07 Feb 2023 06:59:22 -0800
Source: openjfx
Architecture: source
Version: 11.0.11+1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: tony mancill 
Closes: 1026962
Changes:
 openjfx (11.0.11+1-3) unstable; urgency=medium
 .
   * Team upload.
   * Set NUMBER_OF_PROCESSORS via nproc to address FTBFS on s390x due to
 excessive build parallelism (Closes: #1026962)
   * Add lintian overrides for long HTML lines
   * Replace build-dep on obsolete libgl1-mesa-dev with libgl-dev
   * Freshen years in debian/copyright
   * Bump Standards-Version to 4.6.2
Checksums-Sha1:
 505dab03ad74c8be79da79531f990e9c1766bf0c 2776 openjfx_11.0.11+1-3.dsc
 57ab1fc2535f08a383f9a18935dadc1ab652185e 24296 
openjfx_11.0.11+1-3.debian.tar.xz
 2c963c63858444c53e0ef271cd243ea16f830273 23625 
openjfx_11.0.11+1-3_amd64.buildinfo
Checksums-Sha256:
 4e87d9d0af4e63779b6c8f94097ae40c2ca290bd8436cdaba9664cf17e767e17 2776 
openjfx_11.0.11+1-3.dsc
 db416405a9089c2e71de916a5e37e28de0c869b56b1d16dbf0fcb59577597ad2 24296 
openjfx_11.0.11+1-3.debian.tar.xz
 11b29e1a1053fe0d076251cd0d779d1c955f65328ba97c9c0e710fe9b488a0c4 23625 
openjfx_11.0.11+1-3_amd64.buildinfo
Files:
 c789af9219b7681acafe5bc94863daf4 2776 java optional openjfx_11.0.11+1-3.dsc
 b486abf9d1becf7f773aed073be39542 24296 java optional 
openjfx_11.0.11+1-3.debian.tar.xz
 f28de4e284736676e1b8e104321ddf10 23625 java optional 
openjfx_11.0.11+1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAmPiqTwUHHRtYW5jaWxs
QGRlYmlhbi5vcmcACgkQIdIFiZdLPpb0zw/6A40sT/HO9BYzi4rEoDzpIpTX0Uaf
HMaGm2TQve42sTAC74J9LBkNxvK5DFOcMRgRgSr+ID9STAnXL2L9z5D1SbNNgu0p
/JUWMN0W58kRE/YOnQS44TfqBfEsF3bSFDwuqTDzCOrl4kmeUBaPcr9TyDJzUQmg
UtTxG9QOz+s6qfjg6rhEPIBw5o48gEuKLsJr0aqM/jZLfg/hfbt2+QL0n7L7cO2k
gZU2WIxYw/+Nj+tUA+PAv4JHhM+oEcRMjsKNlXdRPDDrdL0cbsjdUoP0AUmI283b
AVKAaXaKvB5/KhwBj0J8J31GqwqDn3Dv/xgNsiO3qa9irH1QsePE5DOTrQ3ypEhU
HGGDgP386GqCxXcMkeJIBwSR1f81Y/1cANw9lYbP3sqwsG50C1S85ZDdn1KAKRKD
nRs613OqGHfhin1AYFWiFVY0TNaDcjbV33HScbsiVWoGB8FeMyjdfweAjtyoTHUh
VX8gHVewDFcDjcQ5YTBSJzsdVm+at4YzKZc39mCfAwHtkQ/BAdlzSpt8/SbgUzQ4
g7EIzgsjR6W1c2Soka79SE6fQk06mvJpUjlY8nxbsseEgaRxfRmN2sWs/UD6I55I
A0LmQopwnHaLnd/kYSoHafRLNw6KglWg64RaFZcXMVhMNX7hTJ0aW2fDwXcdBIUX
l1ApH2RJa1vnnEI=
=B0lC
-END PGP SIGNATURE End Message ---

Bug#1030670: Does not depend on libspng0

[Andrea Pappacoda]

Hi Jordi, thanks for the fast report!

On Mon Feb 6, 2023 at 12:09 PM CET, Jordi Mallach wrote:
> While trying to build against the new libspng-dev, I found that even my
> build was issuing -lspng, it would fail because it could not find it.
>
> It turns out you're missing a dependency against libspng0 itself.

Whoops, I wonder how I missed that. I thought lintian had a check for
this too, but aparently it doesn't.

> Additionally, I've seen the following too:
>
> - spng.pc declares:
>
> Requires.private: zlib
>
> If I understand correctly, this is not a public dependency, which means
> libspng-dev does not need to depend on zlib-dev. In fact, that's one of
> the features SPNG advertises.

Yeah, it's not part of the public interface (i.e. not exposed in the
header file), but it's still required to statically link to the library.
Not only that, but even if shared linking is required, pkg-config
requires all the Requires.private dependencies if the --cflags flag is
specified. If you try to remove zlib.pc and ask pkgconf to find spng,
here's what happens:

$ pkg-config --cflags --libs spng   
Package zlib was not found in the pkg-config search path.
Perhaps you should add the directory containing `zlib.pc'
to the PKG_CONFIG_PATH environment variable
Package 'zlib', required by 'spng', not found

In short, zlib-dev is a required dependency. As for what spng
advertises, yeah, you _can_ avoid zlib, but by using minz instead.

> - I would downgrade the Recommends on libspng-doc to a Suggests, to
>   avoid pulling in fonts and other unneeded packages on the 95% of
>   cases.

I'd prefer to keep it a recommendation instead. I find offline
documentation extremely important, as you don't always have internet
access; not only that, you can only grep it for what you're looking for,
etc, etc. Some make documentation part of the -dev package itself, but
with a Recommends it won't pulled in by a buildd, where it really is
unneeded.

That being said, I find pulling in an extra font package annoying too,
so I'll look into dropping that.

Thanks again for the report and suggestions! I've pushed the fix to
Salsa, and I'll do an upload ASAP.

Bug#1030825: less: CVE-2022-46663: -R filtering bypass

[Salvatore Bonaccorso]

Source: less
Version: 590-1.1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for less. The severity is
set on purpose to RC level, as I think the issue might ideally be
fixed for the bookworm release in advance.

CVE-2022-46663[0]:
| less -R filtering bypass

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-46663
https://www.cve.org/CVERecord?id=CVE-2022-46663
[1] https://github.com/gwsw/less/commit/a78e1351113cef564d790a730d657a321624d79c
[2] https://www.openwall.com/lists/oss-security/2023/02/07/7

Regards,
Salvatore

Bug#1030824: libhashkit-dev needs Breaks + Replaces: libhashkit2 (<< 1.1.3-1~)

[Ondřej Surý]

Thanks, on it, I didn't noticed that while converting the debian/*.manpages to 
debian/*.install.

Ondrej
--
Ondřej Surý (He/Him)
ond...@sury.org



> On 7. 2. 2023, at 20:38, Adrian Bunk  wrote:
> 
> Package: libhashkit-dev
> Version: 1.1.3-1
> Severity: serious
> 
> Unpacking libhashkit-dev:amd64 (1.1.3-1) over (1.0.18+-1+b1) ...
> dpkg: error processing archive 
> /tmp/apt-dpkg-install-hcHxlW/19-libhashkit-dev_1.1.3-1_amd64.deb (--unpack):
> trying to overwrite '/usr/share/man/man3/hashkit_clone.3.gz', which is also 
> in package libhashkit2:amd64 1.0.18+-1+b1

Processed: tagging 902502

[Debian Bug Tracking System]

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

> tags 902502 + bookworm sid
Bug #902502 [src:moblin-gtk-engine] moblin-gtk-engine: Should this package be 
removed?
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.

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

Bug#1030514: marked as done (python3-mofapy needs a source upload to fix the missing python3-h5py dependency)

[Debian Bug Tracking System]

Your message dated Tue, 07 Feb 2023 19:51:05 +
with message-id 
and subject line Bug#1030514: fixed in r-bioc-mofa 1.6.1+dfsg-10
has caused the Debian Bug report #1030514,
regarding python3-mofapy needs a source upload to fix the missing python3-h5py 
dependency
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.)


-- 
1030514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030514
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-mofapy
Version: 1.6.1+dfsg-9
Severity: serious

python3-mofapy lacks a dependency on python3-h5py due to #1030274.

A no-change rebuild is sufficient, but since binNMUs are not possible
for binary-all this needs a source upload.
--- End Message ---
--- Begin Message ---
Source: r-bioc-mofa
Source-Version: 1.6.1+dfsg-10
Done: Andreas Tille 

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated r-bioc-mofa package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 07 Feb 2023 19:54:32 +0100
Source: r-bioc-mofa
Architecture: source
Version: 1.6.1+dfsg-10
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Andreas Tille 
Closes: 1030514
Changes:
 r-bioc-mofa (1.6.1+dfsg-10) unstable; urgency=medium
 .
   * Team upload
   * Rebuild to fix the missing python3-h5py dependency
 Closes: #1030514
Checksums-Sha1:
 33f03087ae9f3411e74b57205d7ac79b0065e70f 2544 r-bioc-mofa_1.6.1+dfsg-10.dsc
 afcadf5c9ae4768befbe91ed3c7d5652b8103e41 4080 
r-bioc-mofa_1.6.1+dfsg-10.debian.tar.xz
 482ccb03d8eac7f25a3d0ea04a75a3c735c9b49e 17068 
r-bioc-mofa_1.6.1+dfsg-10_amd64.buildinfo
Checksums-Sha256:
 7d29f600fcb3f2d2efb4b3bc9fbc56ef17f1a6d9d1e21be343574a406b6beb9e 2544 
r-bioc-mofa_1.6.1+dfsg-10.dsc
 858340fe30424b8fb7e7b92e8a8d52d848269ce52773e8e92714ed77f614cd56 4080 
r-bioc-mofa_1.6.1+dfsg-10.debian.tar.xz
 3e7828873a31f8313a86a367d536b1568452035253e95824b742b37ed22795c2 17068 
r-bioc-mofa_1.6.1+dfsg-10_amd64.buildinfo
Files:
 c0b1698f5fdeb524a9ed0bcb3942db4e 2544 gnu-r optional 
r-bioc-mofa_1.6.1+dfsg-10.dsc
 338bde335bce87dddcdfc9a06d53fb2c 4080 gnu-r optional 
r-bioc-mofa_1.6.1+dfsg-10.debian.tar.xz
 920816a8119dc001e67427b7cbe5008c 17068 gnu-r optional 
r-bioc-mofa_1.6.1+dfsg-10_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmPipoARHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtEUcQ/+KLuzh7ZlxBQ4IrgWQJfCkCBtcFxn3/vv
9OwvjtJmIR7S57vqY0GeiS7iPh6IdC/Ehmi4HCU3LOtv5vOUjNV06kxqAILyBVi3
bS3Y+2EE0nnkjryPucjpUGoSQuKppCygoTtTX80WW9PIO5UWEeWyb89vTNlk8ATU
kKe2PQ0sDUN3imEKqCGJCRqjA6baA+C41zSz0O19GcVTGaC9hOLXzl5w2amZ9pbE
D6W1rAppQRsXtAORkXpay9z3P0zbjapD10nzijZG9H7zDv3pwy7+S7La/pSa788Y
EFCgxQBz1nh/sVKcz1WsHgcXe3iFqdudgZbuY9gvh1fUJFT1v0AnN4lfC7++/0vI
ygn4CDSJJWQ7oyv4KPk4HCAnV83rHONOryFO9cy/GMGXpxBjy26lWsotksm7Z/n9
SXoskPMJ+shCPqDLcN3QjR7Bs3isIhokxAersYrR0RRUUslkAQDtYu52nLODXPBB
VvRcttQzTc6cy9xZkSTd3YrAoURHwI0uSJ+UdwEHMhjsoUkMdMeJX2J471TDvBx+
F5Ok+ItzGe2ylXqY1bMEPCjshj5gljXi5E3NC+DAa+NYLIETsxBxa6KZk+5kPPlo
18N36jRcgR+wN7XfXb+2Xmx7k8a/UuaeSTuDKgW2yfi0IpKXOl6itAVL6QHSs4pT
mW8z/rBOjjg=
=Has3
-END PGP SIGNATURE End Message ---

Bug#1030815: marked as done (keyman: Missing autopkgtest dependency on pkg-config)

[Debian Bug Tracking System]

Your message dated Tue, 07 Feb 2023 19:49:39 +
with message-id 
and subject line Bug#1030815: fixed in keyman 16.0.138-2
has caused the Debian Bug report #1030815,
regarding keyman: Missing autopkgtest dependency on pkg-config
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.)


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

https://ci.debian.net/data/autopkgtest/testing/amd64/k/keyman/31022569/log.gz

...
autopkgtest [03:17:05]: test test-build: [---
/tmp/autopkgtest-lxc.1u3zjijx/downtmp/build.9GP/src/debian/tests/test-build: 
line 18: pkg-config: command not found
In file included from /usr/include/keyman/keyboardprocessor.h:103,
 from keymantest.c:1:
/usr/include/keyman/keyboardprocessor_bits.h:69:10: fatal error: km_types.h: No 
such file or directory
   69 | #include 
  |  ^~~~
compilation terminated.
autopkgtest [03:17:05]: test test-build: ---]
autopkgtest [03:17:05]: test test-build:  - - - - - - - - - - results - - - - - 
- - - - -
...
--- End Message ---
--- Begin Message ---
Source: keyman
Source-Version: 16.0.138-2
Done: Gunnar Hjalmarsson 

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

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

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

Debian distribution maintenance software
pp.
Gunnar Hjalmarsson  (supplier of updated keyman package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 07 Feb 2023 20:34:35 +0100
Source: keyman
Built-For-Profiles: noudeb
Architecture: source
Version: 16.0.138-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team 
Changed-By: Gunnar Hjalmarsson 
Closes: 1030815
Changes:
 keyman (16.0.138-2) unstable; urgency=medium
 .
   * Team upload
   * debian/tests/control: Added missing autopkgtest dependency on
 pkg-config (closes: #1030815).
Checksums-Sha1:
 838de9d4275694564ef75c3c16c385ff020c68bf 2649 keyman_16.0.138-2.dsc
 e4311fa71eae603d00724ecc3f22278d5292837c 12288 keyman_16.0.138-2.debian.tar.xz
 06c03d4051c7b321103bf449e2347b00b4e3250d 21114 
keyman_16.0.138-2_source.buildinfo
Checksums-Sha256:
 47e9025ebe74c7791ae0cd28bf9fa2d02674f92c043b82d0821fd90f2aa14b5c 2649 
keyman_16.0.138-2.dsc
 8f2cce03a324c4d074220caf02fd0cc17278a4ee3869cf8e9ce327d6b39db494 12288 
keyman_16.0.138-2.debian.tar.xz
 1c75ed34872e06d974a2d73cbd889902f603eefd8b764d8739e4bec069b01265 21114 
keyman_16.0.138-2_source.buildinfo
Files:
 6df493b955a9121b68184be3bbaa9c21 2649 text optional keyman_16.0.138-2.dsc
 f359442647d5a06022af9c3617a103bd 12288 text optional 
keyman_16.0.138-2.debian.tar.xz
 517d09d005aa10ed9c3ce28b38b78e13 21114 text optional 
keyman_16.0.138-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEDP6Ze3JFgKf6cvjP8LEQ51ppLzIFAmPiqEIACgkQ8LEQ51pp
LzJLogf/YO6P9jyFXilbl+i6K9dHZ7HGTaGQiESLdPADf6jJg/1EAlh0zY5oHW4t
E7jGN9a1Hp/WzDjMHl3x2sJV3rAoJVAvwr5uUCF8JlOERfCemCnhJpo6f4KzM0dz
jbogOOpUWvv6t+yhILR1hcDzA58r7W//Su0gCnDNA6yW0TX7XPgOgYENt/XRTY2f
DA7WVAFQa6jejFlMl8ImyCpmVOibfRPTNI4cANvg9ULLiUrdD7jp2VaGJbEE7EYT
3PleMDhPOIjRrwlRgCLZ+h+qa9NQkPYWSLBQquCNiVVwYzTpxx9XRwpbvCGycGBN
Xm22bxpuKpvDGdY89c1kFn3o84yXkQ==
=7MIr
-END PGP SIGNATURE End Message ---

Bug#1030170: marked as done (dh-virtualenv: Broken on Python 3.11, AttributeError: module 'inspect' has no attribute 'getargspec')

[Debian Bug Tracking System]

Your message dated Tue, 07 Feb 2023 19:49:06 +
with message-id 
and subject line Bug#1030170: fixed in dh-virtualenv 1.2.2-1.3
has caused the Debian Bug report #1030170,
regarding dh-virtualenv: Broken on Python 3.11, AttributeError: module 
'inspect' has no attribute 'getargspec'
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.)


-- 
1030170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030170
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dh-virtualenv
Version: 1.2.2-1.2
Severity: grave
Tags: patch
Justification: renders package unusable
X-Debbugs-Cc: lego...@debian.org

Hi,

Using dh-virtualenv with bookworm's Python 3.11 breaks:

Traceback (most recent call last):
  File "/usr/bin/dh_virtualenv", line 111, in 
sys.exit(main() or 0)
 ^^
  File "/usr/bin/dh_virtualenv", line 60, in main
arguments = inspect.getargspec(DebHelper.__init__).args
^^
AttributeError: module 'inspect' has no attribute 'getargspec'. Did you mean: 
'getargs'?

This was fixed upstream last month: 
.

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

Kernel: Linux 5.15.81-1.fc32.qubes.x86_64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dh-virtualenv depends on:
ii  libjs-sphinxdoc   3.4.3-2
ii  perl  5.32.1-4+deb11u2
ii  python3   3.9.2-3
pn  sphinx-rtd-theme-common   
pn  virtualenv | python3-virtualenv | python3.9-venv  

dh-virtualenv recommends no packages.

dh-virtualenv suggests no packages.
--- End Message ---
--- Begin Message ---
Source: dh-virtualenv
Source-Version: 1.2.2-1.3
Done: Kunal Mehta 

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

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

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

Debian distribution maintenance software
pp.
Kunal Mehta  (supplier of updated dh-virtualenv 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: Thu, 02 Feb 2023 14:10:21 -0500
Source: dh-virtualenv
Architecture: source
Version: 1.2.2-1.3
Distribution: unstable
Urgency: medium
Maintainer: Jyrki Pulliainen 
Changed-By: Kunal Mehta 
Closes: 1030170
Changes:
 dh-virtualenv (1.2.2-1.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Cherry-pick upstream patch for Python 3.11 support (Closes: #1030170)
Checksums-Sha1:
 84679bf0d4c54ff1259d7e179882daaf4fe13b65 1943 dh-virtualenv_1.2.2-1.3.dsc
 79904b7ba958ac01beb027cbe397f7bf92de6f72 3104 
dh-virtualenv_1.2.2-1.3.debian.tar.xz
 f3c68ff433111965b385b3bcdda7875a2728c30f 7675 
dh-virtualenv_1.2.2-1.3_amd64.buildinfo
Checksums-Sha256:
 075666faed2d27fded6d6f2e3036e715c945416f3abc126e7ca09572c124 1943 
dh-virtualenv_1.2.2-1.3.dsc
 bb229de9dbcef92daefe681375b395276c6d9576da0a604e9476eb6d1b16a61c 3104 
dh-virtualenv_1.2.2-1.3.debian.tar.xz
 eaa3be9b7dad924c5cbc0fc841345395db78a51b83cc05551533bda630bbf2fd 7675 
dh-virtualenv_1.2.2-1.3_amd64.buildinfo
Files:
 1f416cd431265e512fe8629a0bb5d22e 1943 python optional 
dh-virtualenv_1.2.2-1.3.dsc
 c00a135225aee5f6d1b4f21e6e4d1e0e 3104 python optional 
dh-virtualenv_1.2.2-1.3.debian.tar.xz
 6a62ce71ba2b188eb64baeedf681a9c2 7675 python optional 
dh-virtualenv_1.2.2-1.3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEE2MtZ8F27ngU4xIGd8QX4EBsFJpsFAmPcCy0THGxlZ29rdG1A
cmlzZXVwLm5ldAAKCRDxBfgQGwUmmwtoD/9cPre9rG7O5/+Vl6q6eqyf8xLELAvf
JHu//c+yDYiV7T3luF+CziA9TRvgdzMFJ5zFceu8ASnm4p1iBvTkNKdn4gU1Sgxb
jS3I1KEZ8i/QKV5AwjjIbZyBWuopAfaruavvPVo7BohnHkdE71KFaIaFZyRNz8Id
viVN5YsXlB8ecYvX5PX2EiNT1RvIOuUW+/UN3eb6RDu0E7REJO7aRaXWhL3a1+r6
V0ADHisyiI757a65LdcRWoUGhc54Rdqm5++IHytxbjUNkcRXAfAaa+O8BBQrrYpG
Y+3ccxS

Processed: Re: Bug#902502: moblin-gtk-engine: Should this package be removed?

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #902502 [src:moblin-gtk-engine] moblin-gtk-engine: Should this package be 
removed?
Severity set to 'serious' from 'normal'

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

Bug#1030824: libhashkit-dev needs Breaks + Replaces: libhashkit2 (<< 1.1.3-1~)

[Adrian Bunk]

Package: libhashkit-dev
Version: 1.1.3-1
Severity: serious

Unpacking libhashkit-dev:amd64 (1.1.3-1) over (1.0.18+-1+b1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-hcHxlW/19-libhashkit-dev_1.1.3-1_amd64.deb (--unpack):
 trying to overwrite '/usr/share/man/man3/hashkit_clone.3.gz', which is also in 
package libhashkit2:amd64 1.0.18+-1+b1

Bug#1030427: marked as done (trapperkeeper-metrics-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact org.clojure:tools.namespace:jar:debian has not bee

[Debian Bug Tracking System]

Your message dated Tue, 07 Feb 2023 19:01:35 +
with message-id 
and subject line Bug#1030427: fixed in trapperkeeper-metrics-clojure 1.5.0-4
has caused the Debian Bug report #1030427,
regarding trapperkeeper-metrics-clojure: FTBFS: Cannot access clojars 
(https://repo.clojars.org/) in offline mode and the artifact 
org.clojure:tools.namespace:jar:debian has not been downloaded from it before.
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.)


-- 
1030427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030427
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: trapperkeeper-metrics-clojure
Version: 1.5.0-3
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):
> make[1]: Entering directory '/<>'
> lein pom debian/pom.xml
> Wrote /<>/debian/pom.xml
> lein jar
> Warning: specified :main without including it in :aot. 
> Implicit AOT of :main will be removed in Leiningen 3.0.0. 
> If you only need AOT for your uberjar, consider adding :aot :all into your
> :uberjar profile instead.
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact org.clojure:tools.namespace:jar:debian has not been downloaded 
> from it before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact org.clojure:tools.namespace:jar:debian has not been downloaded from 
> it before.
> This could be due to a typo in :dependencies, file system permissions, or 
> network issues.
> If you are behind a proxy, try setting the 'http_proxy' environment variable.
> make[1]: *** [debian/rules:18: override_dh_auto_build] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/02/03/trapperkeeper-metrics-clojure_1.5.0-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230203;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230203&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: trapperkeeper-metrics-clojure
Source-Version: 1.5.0-4
Done: Jérôme Charaoui 

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

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

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

Debian distribution maintenance software
pp.
Jérôme Charaoui  (supplier of updated 
trapperkeeper-metrics-clojure package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 07 Feb 2023 12:35:33 -0500
Source: trapperkeeper-metrics-clojure
Architecture: source
Version: 1.5.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Clojure Maintainers 
Changed-By: Jérôme Charaoui 
Closes: 1030427
Changes:
 trapperkeeper-metrics-clojure (1.5.0-4) unstable; urgency=medium
 .
   * drop jackson and snakeyaml version overrides (Closes: #1030427)
   * d/control: add myself to Uploaders
   * d/patches: require clojure 1.x in lein local
   * d/rules: fix FTBFS when package is used as Build-Dep
   * d/tests: streamline classpaths
Checksums-Sha1:
 8d33e0353616b6a9c0a7b87b406055137fa8110c 2504 
trapperkeeper-metrics-clojure_1.5.0-4.dsc
 20b06c9b45f0b5c3d407725b57246daaba5bb1a4 6392 
trapperkeeper-metrics-clojure_1.5.0-4.debian.tar.xz
 0c35ae6e5d01a8af0e5f0cde573f90946957edbb 13366 
trapperkeeper-metrics-clojure_1.5.0-4_amd64.buildinfo
Checksums-Sha256:
 4eac9023a3fad34474c053f40ea9f

Bug#1030781: marked as done (quilt: makes libxau FTBFS)

[Debian Bug Tracking System]

Your message dated Tue, 07 Feb 2023 18:58:28 +
with message-id 
and subject line Bug#1030781: fixed in quilt 0.67+really0.66-1
has caused the Debian Bug report #1030781,
regarding quilt: makes libxau 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.)


-- 
1030781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030781
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: quilt
Version: 0.67-1
Severity: serious
Control: affects -1 + src:libxau
Tags: ftbfs

The quilt upload makes libxau FTBFS. I think it is the wrong time to
upload a breaking change like this. Thus filing against quilt. Full
build log:

| Command: dpkg-buildpackage --sanitize-env -us -uc -b -rfakeroot
| dpkg-buildpackage: info: source package libxau
| dpkg-buildpackage: info: source version 1:1.0.9-1
| dpkg-buildpackage: info: source distribution unstable
| dpkg-buildpackage: info: source changed by Timo Aaltonen 
|  dpkg-source --before-build .
| dpkg-buildpackage: info: host architecture amd64
|  fakeroot debian/rules clean
| dh clean --with quilt --builddirectory=build/
|dh_auto_clean -O--builddirectory=build/
|dh_autoreconf_clean -O--builddirectory=build/
|dh_quilt_unpatch -O--builddirectory=build/
| No series file found
| dh_quilt_unpatch: error: quilt --quiltrc /dev/null pop -a || test $? = 2 
returned exit code 1
| make: *** [debian/rules:14: clean] Error 25
| dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned 
exit status 2

Helmut
--- End Message ---
--- Begin Message ---
Source: quilt
Source-Version: 0.67+really0.66-1
Done: Dr. Tobias Quathamer 

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

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

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

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated quilt package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 07 Feb 2023 15:19:07 +0100
Source: quilt
Architecture: source
Version: 0.67+really0.66-1
Distribution: unstable
Urgency: medium
Maintainer: Martin Quinson 
Changed-By: Dr. Tobias Quathamer 
Closes: 1030781
Changes:
 quilt (0.67+really0.66-1) unstable; urgency=medium
 .
   * Revert upstream version back to 0.66 (Closes: #1030781)
 The new upstream version has changed the error return code
 if there are no patches in the series file. Previously,
 quilt returned 2, now it returns 1.
 The program dh_quilt_unpatch relies on the previous
 error code, resulting in FTBFS errors in packages which
 use "dh --with quilt". One example is libxau, see the
 bug above.
 - Revert updates patches to version 0.66
 - Remove gawk from Build-Depends
Checksums-Sha1:
 f08140859354cfaccb4a0941b49716caa3b4c632 2063 quilt_0.67+really0.66-1.dsc
 e848f46d1e2b0dd07eee1a04f04fb2a4c37bf1d0 413069 
quilt_0.67+really0.66.orig.tar.gz
 6bce9c9f5201ffc8fc350373335b1dd672c6832a 39296 
quilt_0.67+really0.66-1.debian.tar.xz
 f40a41cc1cda34722f4b08373968986653354807 9057 
quilt_0.67+really0.66-1_amd64.buildinfo
Checksums-Sha256:
 89885bdac402e999dcf2b2efad2b70f568967910bcb89172cd3221848c9e1d3f 2063 
quilt_0.67+really0.66-1.dsc
 314b319a6feb13bf9d0f9ffa7ce6683b06919e734a41275087ea457cc9dc6e07 413069 
quilt_0.67+really0.66.orig.tar.gz
 18d9f16df86278b18b5042022f0149dd5db364ccc1139e8fc8c303317d5eca62 39296 
quilt_0.67+really0.66-1.debian.tar.xz
 03fba206a7142076990860009ead0faf1430be79ab71abbf21beb5a02a7875fd 9057 
quilt_0.67+really0.66-1_amd64.buildinfo
Files:
 5dee7ee44647b6de67bc92b63b47eb12 2063 vcs optional quilt_0.67+really0.66-1.dsc
 6800c2404a2c0598ab2eff92a636ba70 413069 vcs optional 
quilt_0.67+really0.66.orig.tar.gz
 c2398f62c5528f3001571b2ab3c0f0c7 39296 vcs optional 
quilt_0.67+really0.66-1.debian.tar.xz
 949f3dc0a9d400c875996565701c395a 9057 vcs optional 
quilt_0.67+really0.66-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAmPiYi0ACgkQEwLx8Dbr
6xmHIA/7BVNyA31PIRxv7XjceJzpL0CxTzliRa5PxfuyplJF6W5sZyTHGM6MmWXE
cSJ1AXBCBqqPw/f4RGAqpS+orhWaw+DLYLKA0yV855RoAj9/NS5fNlLN1rkB6/2y
2YR5bD951VhMe4pKhtqCndS6V8kp/hYJ

Bug#1013876: marked as done (webext-keepassxc-browser: Version 1.8.0+repack1-2 fail to load in chromium)

[Debian Bug Tracking System]

Your message dated Tue, 07 Feb 2023 18:50:42 +
with message-id 
and subject line Bug#1013876: fixed in keepassxc-browser 1.8.4+repack1-3
has caused the Debian Bug report #1013876,
regarding webext-keepassxc-browser: Version 1.8.0+repack1-2 fail to load in 
chromium
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.)


-- 
1013876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013876
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: webext-keepassxc-browser
Version: 1.8.0+repack1-2
Severity: serious

Hi!

This version seems to fail load on chromium 103.0.5060.53-1, with the
following warnings and errors shown on the extensions settings page:

  (W) Unrecognized manifest key 'applications'.
  (W) Manifest version 2 is deprecated, and support will be removed in 2023.
  See https://developer.chrome.com/blog/mv2-transition/ for more details.
  (E) Uncaught TypeError: Bootstrap's JavaScript requires jQuery. jQuery must 
be included before Bootstrap's JavaScript.
  Context: popups/popup.html
  Stack Trace: bootstrap/bootstrap.js:221 (anonymous function)
  (E) Uncaught (in promise) ReferenceError: browser is not defined
  Context: popups/popup.html
  Stack Trace: popups/popup_functions.js:74 (anonymous function)
  (E) Uncaught ReferenceError: browser is not defined
  Context: popups/popup.html
  Stack Trace: common/translate.js:11 (anonymous function)
  (E) Uncaught (in promise) ReferenceError: browser is not defined
  Context: popups/popup.html
  Stack Trace: popups/popup_functions.js:40 (anonymous function)
  (E) Uncaught ReferenceError: browser is not defined
  Context: _generated_background_page.html
  Stack Trace: common/global.js:161 (anonymous function)
  (E) Uncaught ReferenceError: browser is not defined
  Context: _generated_background_page.html
  Stack Trace: background/keepass.js:39 (anonymous function)
  (E) Uncaught ReferenceError: browser is not defined
  Context: _generated_background_page.html
  Stack Trace: background/init.js:23 (anonymous function)

Thanks,
Guillem
--- End Message ---
--- Begin Message ---
Source: keepassxc-browser
Source-Version: 1.8.4+repack1-3
Done: Bruno Kleinert 

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

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

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

Debian distribution maintenance software
pp.
Bruno Kleinert  (supplier of updated keepassxc-browser 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 07 Feb 2023 19:28:47 +0100
Source: keepassxc-browser
Architecture: source
Version: 1.8.4+repack1-3
Distribution: unstable
Urgency: medium
Maintainer: Bruno Kleinert 
Changed-By: Bruno Kleinert 
Closes: 1013876
Changes:
 keepassxc-browser (1.8.4+repack1-3) unstable; urgency=medium
 .
   * Fixed loading in Chromium. Many thanks to Guillem Jover for pointing me to
 the root cause. (Closes: #1013876)
 + Replaced faulty browser-poliyfill.js from wrong build-dependency
   node-cross-fetch by code copy
   debian/missing-sources/browser-polyfill.js and updated debian/copyright
   accordingly.
Checksums-Sha1:
 5e105e8ecdd617529456c9f3907b7624489a1625 2075 
keepassxc-browser_1.8.4+repack1-3.dsc
 dd3ba094981d79867ba7a96152fd92baab96bbfb 15952 
keepassxc-browser_1.8.4+repack1-3.debian.tar.xz
 e20a069a794a63e86c13075e1e0498ee962afff4 6161 
keepassxc-browser_1.8.4+repack1-3_source.buildinfo
Checksums-Sha256:
 71b77990a7bfe22b762c1c6ef914c7e53c463ff72c85343dc251dc5bc040b9d6 2075 
keepassxc-browser_1.8.4+repack1-3.dsc
 2fe8a0f6a1cdd9ccd88e95a69697b15e47810ea9c40dfe6c996a6816aaede515 15952 
keepassxc-browser_1.8.4+repack1-3.debian.tar.xz
 77ac530ee563e8117af56ab529495098159e1896567efaff9a24bde46c1bb0d6 6161 
keepassxc-browser_1.8.4+repack1-3_source.buildinfo
Files:
 95f57ae6d7a1d3615237cc119209942e 2075 web optional 
keepassxc-browser_1.8.4+repack1-3.dsc
 e349dda8e1a7c872859ec46df11f5b53 15952 web optional 
keepassxc-browser_1.8.4+repack1-3.debian.tar.xz
 560760ab1c16cc1a79c8e04d1162255a 6161 web optional 
keepassxc-browser_1.8.4+repac

Bug#1030468: marked as done (trapperkeeper-authorization-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact org.eclipse.jetty:jetty-jmx:jar:debian has n

[Debian Bug Tracking System]

Your message dated Tue, 07 Feb 2023 18:32:02 +
with message-id 
and subject line Bug#1030468: fixed in trapperkeeper-authorization-clojure 
1.0.0-3
has caused the Debian Bug report #1030468,
regarding trapperkeeper-authorization-clojure: FTBFS: Cannot access clojars 
(https://repo.clojars.org/) in offline mode and the artifact 
org.eclipse.jetty:jetty-jmx:jar:debian has not been downloaded from it before.
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.)


-- 
1030468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030468
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: trapperkeeper-authorization-clojure
Version: 1.0.0-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):
> make[1]: Entering directory '/<>'
> lein pom debian/pom.xml
> Wrote /<>/debian/pom.xml
> lein i18n make
> Running 'make i18n'
> lein jar
> Warning: specified :main without including it in :aot. 
> Implicit AOT of :main will be removed in Leiningen 3.0.0. 
> If you only need AOT for your uberjar, consider adding :aot :all into your
> :uberjar profile instead.
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact compojure:compojure:jar:debian has not been downloaded from it 
> before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact compojure:compojure:jar:debian has not been downloaded from it 
> before.
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact org.eclipse.jetty:jetty-server:jar:debian has not been 
> downloaded from it before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact org.eclipse.jetty:jetty-server:jar:debian has not been downloaded 
> from it before.
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact org.eclipse.jetty:jetty-servlet:jar:debian has not been 
> downloaded from it before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact org.eclipse.jetty:jetty-servlet:jar:debian has not been downloaded 
> from it before.
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact org.eclipse.jetty:jetty-servlets:jar:debian has not been 
> downloaded from it before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact org.eclipse.jetty:jetty-servlets:jar:debian has not been downloaded 
> from it before.
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact org.eclipse.jetty:jetty-webapp:jar:debian has not been 
> downloaded from it before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact org.eclipse.jetty:jetty-webapp:jar:debian has not been downloaded 
> from it before.
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact org.eclipse.jetty:jetty-proxy:jar:debian has not been downloaded 
> from it before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact org.eclipse.jetty:jetty-proxy:jar:debian has not been downloaded 
> from it before.
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact org.eclipse.jetty:jetty-jmx:jar:debian has not been downloaded 
> from it before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact org.eclipse.jetty:jetty-jmx:jar:debian has not been downloaded from 
> it before.
> This could be due to a typo in :dependencies, file system permissions, or 
> network issues.
> If you are behind a proxy, try setting the 'http_proxy' environment variable.
> make[1]: *** [debian/rules:19: override_dh_auto_build] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/02/03/trapperkeeper-authorization-clojure_1.0.0-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230203;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230203&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

Bug#1029594: marked as done (Fails to authenticate mit o365)

[Debian Bug Tracking System]

Your message dated Tue, 07 Feb 2023 18:31:47 +
with message-id 
and subject line Bug#1029606: fixed in thunderbird 1:102.7.1+1-1
has caused the Debian Bug report #1029606,
regarding Fails to authenticate mit o365
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.)


-- 
1029606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029606
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: thunderbird
Version: 1:102.7.1-1
Severity: important

After upgrading from 1:102.6.0-1 this morning, thunderbird fails to
login into microsoft o365, making it impossible to access mails from
that account.

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

Kernel: Linux 5.16.17 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages thunderbird depends on:
ii  debianutils  5.7-0.4
ii  fontconfig   2.14.1-3
ii  libasound2   1.2.8-1+b1
ii  libatk1.0-0  2.46.0-4
ii  libc62.36-8
ii  libcairo-gobject21.16.0-7
ii  libcairo21.16.0-7
ii  libdbus-1-3  1.14.4-1devuan1
ii  libdbus-glib-1-2 0.112-3
ii  libevent-2.1-7   2.1.12-stable-5+b1
ii  libffi8  3.4.4-1
ii  libfontconfig1   2.14.1-3
ii  libfreetype6 2.12.1+dfsg-4
ii  libgcc-s112.2.0-14
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libglib2.0-0 2.74.5-1
ii  libgtk-3-0   3.24.36-2
ii  libicu72 72.1-3
ii  libnspr4 2:4.35-1
ii  libnss3  2:3.87-1
ii  libpango-1.0-0   1.50.12+ds-1
ii  librnp0  0.16.2-1
ii  libstdc++6   12.2.0-14
ii  libvpx7  1.12.0-1
ii  libx11-6 2:1.8.3-3
ii  libx11-xcb1  2:1.8.3-3
ii  libxcb-shm0  1.15-1
ii  libxcb1  1.15-1
ii  libxext6 2:1.3.4-1+b1
ii  libxrandr2   2:1.5.2-2+b1
ii  psmisc   23.6-1
ii  x11-utils7.7+5
ii  zenity   3.43.0-1
ii  zlib1g   1:1.2.13.dfsg-1

Versions of packages thunderbird recommends:
ii  hunspell-de-ch [hunspell-dictionary]  20161207-11
ii  hunspell-de-de [hunspell-dictionary]  20161207-11

Versions of packages thunderbird suggests:
pn  apparmor  
pn  fonts-lyx 
ii  libgssapi-krb5-2  1.20.1-1

-- Configuration Files:
/etc/thunderbird/pref/thunderbird.js changed:
// This is the Debian specific preferences file for Mozilla Thunderbird
// You can make any change in here, it is the purpose of this file.
// You can, with this file and all files present in the directory
//
//  /etc/thunderbird/pref directory
//
// override any preference that is present in the directory
//
//  /usr/lib/thunderbird/defaults/pref
//
// While your changes will be kept on upgrade if you modify files in
// /etc/thunderbird/pref, please note that they won't be kept if you
// do them in /usr/lib/thunderbird/defaults/pref.
pref("extensions.update.enabled", false, sticky);
// Use LANG environment variable to choose locale from system
// The old environment setting 'pref("intl.locale.matchOS", true);' is
// currently not working anymore. The new introduced setting
// 'intl.locale.requested' is now used for this. Setting an empty string is
// pulling the system locale into Thunderbird.
pref("intl.locale.requested", "");
// Disable default mail checking (gnome).
pref("mail.shell.checkDefaultMail", false, locked);
// Disable default mail client check
pref("mail.shell.checkDefaultClient", false, locked);
// if you are not using gnome
pref("network.protocol-handler.app.http", "x-www-browser");
pref("network.protocol-handler.app.https", "x-www-browser");
// This setting is a workaround for some crashes inside the JS engine.
// By this Thunderbird will use more memory and acting slower as the sharing
// memory between interacting JS files is disabled.
pref("javascript.options.baselinejit", false);
// Uncomment the follwing setting if you want to have a extra mail header field
// for X-Debbugs-Cc, only needed in case you have to work with the Debian
// Bug Tracking System more deeply
//pref("mail.compose.other.header", "X-Debbugs-Cc");
pref("datareporting.healthreport.uploadEnabled", false, locked);
pref("mail.mdn.report.enabled", false);
pref("mail.openpgp.allow_external_gnupg", true);
pref("mail.phishing.detection.e

Bug#1029606: marked as done (thunderbird: After updating the package I cannot access the Exchange account)

[Debian Bug Tracking System]

Your message dated Tue, 07 Feb 2023 18:31:47 +
with message-id 
and subject line Bug#1029606: fixed in thunderbird 1:102.7.1+1-1
has caused the Debian Bug report #1029606,
regarding thunderbird: After updating the package I cannot access the Exchange 
account
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.)


-- 
1029606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029606
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: thunderbird
Version: 1:102.6.0-1~deb11u1
Severity: normal
X-Debbugs-Cc: antde...@gmail.com

Dear Maintainer,
After updating the Thunderbird, from version 1:102.6.0-1-> 1:102.7.1-1, I
cannot access the Exchange account:
- outlook.office365.com
- port 993
- SSL/TLS
- OAuth2

It makes me insert the access credentials, but then a mistake returns that
cannot authenticate the server.

Reinstalling the previous version solves the problem.

Thanks,
Antonio


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

Kernel: Linux 6.1-8.1-liquorix-amd64 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to it_IT.UTF-8), LANGUAGE=it
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages thunderbird depends on:
ii  debianutils  5.7-0.4
ii  fontconfig   2.14.1-3
ii  kdialog  4:22.12.1-1
ii  libasound2   1.2.8-1+b1
ii  libatk1.0-0  2.46.0-4
ii  libc62.36-8
ii  libcairo-gobject21.16.0-7
ii  libcairo21.16.0-7
ii  libdbus-1-3  1.14.4-1
ii  libdbus-glib-1-2 0.112-3
ii  libevent-2.1-7   2.1.12-stable-5+b1
ii  libffi7  3.3-6
ii  libfontconfig1   2.14.1-3
ii  libfreetype6 2.12.1+dfsg-4
ii  libgcc-s112.2.0-14
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libglib2.0-0 2.74.5-1
ii  libgtk-3-0   3.24.36-2
ii  libpango-1.0-0   1.50.12+ds-1
ii  libstdc++6   12.2.0-14
ii  libvpx6  1.9.0-1
ii  libx11-6 2:1.8.3-3
ii  libx11-xcb1  2:1.8.3-3
ii  libxcb-shm0  1.15-1
ii  libxcb1  1.15-1
ii  libxext6 2:1.3.4-1+b1
ii  libxrandr2   2:1.5.2-2+b1
ii  psmisc   23.6-1
ii  x11-utils7.7+5
ii  zenity   3.43.0-1
ii  zlib1g   1:1.2.13.dfsg-1

Versions of packages thunderbird recommends:
ii  hunspell-it [hunspell-dictionary]  1:7.4.2-1

Versions of packages thunderbird suggests:
ii  apparmor  3.0.8-2
ii  fonts-lyx 2.3.7-1
ii  libgssapi-krb5-2  1.20.1-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: thunderbird
Source-Version: 1:102.7.1+1-1
Done: Carsten Schoenert 

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

Debian distribution maintenance software
pp.
Carsten Schoenert  (supplier of updated thunderbird 
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, 05 Feb 2023 17:27:40 +0100
Source: thunderbird
Architecture: source
Version: 1:102.7.1+1-1
Distribution: unstable
Urgency: medium
Maintainer: Carsten Schoenert 
Changed-By: Carsten Schoenert 
Closes: 1029594 1029606 1030532
Changes:
 thunderbird (1:102.7.1+1-1) unstable; urgency=medium
 .
   * [5ce0e7d] New upstream version 102.7.1+1
 Fixed CVE issues in upstream version 102.7.1 (MFSA 2023-04):
 CVE-2023-0430: Revocation status of S/Mime signature certificates was
not checked
 Note: The previous version 1:102.7.1-1 was build on top of a release
 candidate which does not fixed CVE-2023-0430 fully.
 (Closes: #1029594, #1029606)
   * [c7c81a5] apparmor: Expand profile folder about .mozilla-thunderbird
 (Closes: #1030532)
Checksums-Sha1:
 1aaabd075c78df5bbb7780cb3f

Bug#1029606: marked as done (thunderbird: After updating the package I cannot access the Exchange account)

[Debian Bug Tracking System]

Your message dated Tue, 07 Feb 2023 18:31:47 +
with message-id 
and subject line Bug#1029594: fixed in thunderbird 1:102.7.1+1-1
has caused the Debian Bug report #1029594,
regarding thunderbird: After updating the package I cannot access the Exchange 
account
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.)


-- 
1029594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029594
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: thunderbird
Version: 1:102.6.0-1~deb11u1
Severity: normal
X-Debbugs-Cc: antde...@gmail.com

Dear Maintainer,
After updating the Thunderbird, from version 1:102.6.0-1-> 1:102.7.1-1, I
cannot access the Exchange account:
- outlook.office365.com
- port 993
- SSL/TLS
- OAuth2

It makes me insert the access credentials, but then a mistake returns that
cannot authenticate the server.

Reinstalling the previous version solves the problem.

Thanks,
Antonio


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

Kernel: Linux 6.1-8.1-liquorix-amd64 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to it_IT.UTF-8), LANGUAGE=it
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages thunderbird depends on:
ii  debianutils  5.7-0.4
ii  fontconfig   2.14.1-3
ii  kdialog  4:22.12.1-1
ii  libasound2   1.2.8-1+b1
ii  libatk1.0-0  2.46.0-4
ii  libc62.36-8
ii  libcairo-gobject21.16.0-7
ii  libcairo21.16.0-7
ii  libdbus-1-3  1.14.4-1
ii  libdbus-glib-1-2 0.112-3
ii  libevent-2.1-7   2.1.12-stable-5+b1
ii  libffi7  3.3-6
ii  libfontconfig1   2.14.1-3
ii  libfreetype6 2.12.1+dfsg-4
ii  libgcc-s112.2.0-14
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libglib2.0-0 2.74.5-1
ii  libgtk-3-0   3.24.36-2
ii  libpango-1.0-0   1.50.12+ds-1
ii  libstdc++6   12.2.0-14
ii  libvpx6  1.9.0-1
ii  libx11-6 2:1.8.3-3
ii  libx11-xcb1  2:1.8.3-3
ii  libxcb-shm0  1.15-1
ii  libxcb1  1.15-1
ii  libxext6 2:1.3.4-1+b1
ii  libxrandr2   2:1.5.2-2+b1
ii  psmisc   23.6-1
ii  x11-utils7.7+5
ii  zenity   3.43.0-1
ii  zlib1g   1:1.2.13.dfsg-1

Versions of packages thunderbird recommends:
ii  hunspell-it [hunspell-dictionary]  1:7.4.2-1

Versions of packages thunderbird suggests:
ii  apparmor  3.0.8-2
ii  fonts-lyx 2.3.7-1
ii  libgssapi-krb5-2  1.20.1-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: thunderbird
Source-Version: 1:102.7.1+1-1
Done: Carsten Schoenert 

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

Debian distribution maintenance software
pp.
Carsten Schoenert  (supplier of updated thunderbird 
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, 05 Feb 2023 17:27:40 +0100
Source: thunderbird
Architecture: source
Version: 1:102.7.1+1-1
Distribution: unstable
Urgency: medium
Maintainer: Carsten Schoenert 
Changed-By: Carsten Schoenert 
Closes: 1029594 1029606 1030532
Changes:
 thunderbird (1:102.7.1+1-1) unstable; urgency=medium
 .
   * [5ce0e7d] New upstream version 102.7.1+1
 Fixed CVE issues in upstream version 102.7.1 (MFSA 2023-04):
 CVE-2023-0430: Revocation status of S/Mime signature certificates was
not checked
 Note: The previous version 1:102.7.1-1 was build on top of a release
 candidate which does not fixed CVE-2023-0430 fully.
 (Closes: #1029594, #1029606)
   * [c7c81a5] apparmor: Expand profile folder about .mozilla-thunderbird
 (Closes: #1030532)
Checksums-Sha1:
 1aaabd075c78df5bbb7780cb3f

Bug#1029594: marked as done (Fails to authenticate mit o365)

[Debian Bug Tracking System]

Your message dated Tue, 07 Feb 2023 18:31:47 +
with message-id 
and subject line Bug#1029594: fixed in thunderbird 1:102.7.1+1-1
has caused the Debian Bug report #1029594,
regarding Fails to authenticate mit o365
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.)


-- 
1029594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029594
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: thunderbird
Version: 1:102.7.1-1
Severity: important

After upgrading from 1:102.6.0-1 this morning, thunderbird fails to
login into microsoft o365, making it impossible to access mails from
that account.

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

Kernel: Linux 5.16.17 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages thunderbird depends on:
ii  debianutils  5.7-0.4
ii  fontconfig   2.14.1-3
ii  libasound2   1.2.8-1+b1
ii  libatk1.0-0  2.46.0-4
ii  libc62.36-8
ii  libcairo-gobject21.16.0-7
ii  libcairo21.16.0-7
ii  libdbus-1-3  1.14.4-1devuan1
ii  libdbus-glib-1-2 0.112-3
ii  libevent-2.1-7   2.1.12-stable-5+b1
ii  libffi8  3.4.4-1
ii  libfontconfig1   2.14.1-3
ii  libfreetype6 2.12.1+dfsg-4
ii  libgcc-s112.2.0-14
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libglib2.0-0 2.74.5-1
ii  libgtk-3-0   3.24.36-2
ii  libicu72 72.1-3
ii  libnspr4 2:4.35-1
ii  libnss3  2:3.87-1
ii  libpango-1.0-0   1.50.12+ds-1
ii  librnp0  0.16.2-1
ii  libstdc++6   12.2.0-14
ii  libvpx7  1.12.0-1
ii  libx11-6 2:1.8.3-3
ii  libx11-xcb1  2:1.8.3-3
ii  libxcb-shm0  1.15-1
ii  libxcb1  1.15-1
ii  libxext6 2:1.3.4-1+b1
ii  libxrandr2   2:1.5.2-2+b1
ii  psmisc   23.6-1
ii  x11-utils7.7+5
ii  zenity   3.43.0-1
ii  zlib1g   1:1.2.13.dfsg-1

Versions of packages thunderbird recommends:
ii  hunspell-de-ch [hunspell-dictionary]  20161207-11
ii  hunspell-de-de [hunspell-dictionary]  20161207-11

Versions of packages thunderbird suggests:
pn  apparmor  
pn  fonts-lyx 
ii  libgssapi-krb5-2  1.20.1-1

-- Configuration Files:
/etc/thunderbird/pref/thunderbird.js changed:
// This is the Debian specific preferences file for Mozilla Thunderbird
// You can make any change in here, it is the purpose of this file.
// You can, with this file and all files present in the directory
//
//  /etc/thunderbird/pref directory
//
// override any preference that is present in the directory
//
//  /usr/lib/thunderbird/defaults/pref
//
// While your changes will be kept on upgrade if you modify files in
// /etc/thunderbird/pref, please note that they won't be kept if you
// do them in /usr/lib/thunderbird/defaults/pref.
pref("extensions.update.enabled", false, sticky);
// Use LANG environment variable to choose locale from system
// The old environment setting 'pref("intl.locale.matchOS", true);' is
// currently not working anymore. The new introduced setting
// 'intl.locale.requested' is now used for this. Setting an empty string is
// pulling the system locale into Thunderbird.
pref("intl.locale.requested", "");
// Disable default mail checking (gnome).
pref("mail.shell.checkDefaultMail", false, locked);
// Disable default mail client check
pref("mail.shell.checkDefaultClient", false, locked);
// if you are not using gnome
pref("network.protocol-handler.app.http", "x-www-browser");
pref("network.protocol-handler.app.https", "x-www-browser");
// This setting is a workaround for some crashes inside the JS engine.
// By this Thunderbird will use more memory and acting slower as the sharing
// memory between interacting JS files is disabled.
pref("javascript.options.baselinejit", false);
// Uncomment the follwing setting if you want to have a extra mail header field
// for X-Debbugs-Cc, only needed in case you have to work with the Debian
// Bug Tracking System more deeply
//pref("mail.compose.other.header", "X-Debbugs-Cc");
pref("datareporting.healthreport.uploadEnabled", false, locked);
pref("mail.mdn.report.enabled", false);
pref("mail.openpgp.allow_external_gnupg", true);
pref("mail.phishing.detection.e

Bug#1013876: Please close this bug report for keepassxc-browser to migrate to testing

[Bruno Kleinert]

Am Montag, dem 06.02.2023 um 23:40 +0100 schrieb Guillem Jover:
> Hi!
> 
> On Mon, 2023-02-06 at 19:57:02 +0100, Bruno Kleinert wrote:
> > neither revision gets properly loaded by Chromium as of today.
> > 
> > As the freeze approaches, I will remove the Chromium package relation
> > and the symbolic link to the Web Extension
> > /usr/share/chromium/extensions/keepassxc-browser in order "solve" this
> > RC bug.
> 
> That means that users that had this package installed will stop having
> the extension at all, so I'm not sure that's much of a practical
> difference compared to having the extension but it failing to load. :/
> 
> > Unless someone understands what is wrong for Chromium to load the
> > extension and provides a patch.
> 
> Ok, I looked into this, and the problem seems to be the browser
> variable polyfill, which is not required on Firefox, as that uses
> browser, but crhomium-based ones use chrome for the namespace.
> 
> Copying the keepassxc-browser/common/browser-polyfill.min.js from
> the upstream's release/1.8.x branch into
> /usr/share/webext/keepassxc-browser/common/browser-polyfill.js, makes
> the extension work again.
> 
> It appears as if the Build-Depends used is unrelated to that code,
> where a comment at the bottom of the minimized version points at
> version 0.8.0 from https://github.com/mozilla/webextension-polyfill,
> but the package is trying to use node-cross-fetch, which seems
> unrelated?
> 
> Thanks,
> Guillem

Hi Guillem,

many, many thanks for that pointer!

I built a fixed package locally and Chromium loads the extension. I
will upload to sid in a few minutes.

Kind regards,
Bruno


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

Bug#1027080: marked as done (ruby-localhost: FTBFS: tests fail randomly)

[Debian Bug Tracking System]

Your message dated Tue, 07 Feb 2023 17:59:50 +
with message-id 
and subject line Bug#1027080: fixed in ruby-localhost 1.1.9-2
has caused the Debian Bug report #1027080,
regarding ruby-localhost: FTBFS: tests fail randomly
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.)


-- 
1027080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027080
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-localhost
Version: 1.1.9-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-rspec-3.12

Hi,

I'm about to upload ruby-rspec 3.12. During a test rebuild with that version,
ruby-localhost failed to build. I retried it with ruby-rspec 3.10 from
the archive, and I got one successfull build, and one failure exactly
like the one below. So this means the test suite fails randomly, and
that is a problem.

Relevant part of the build log (hopefully):
>  2.2) Failure/Error: expect(status).to be_success
> expected `#.success?` to be 
> truthy, got false
>   # ./spec/localhost/protocol_spec.rb:42:in `block (2 levels) in  (required)>'
>   # 
> /usr/share/rubygems-integration/all/gems/async-rspec-1.16.1/lib/async/rspec/reactor.rb:93:in
>  `block (4 levels) in '
>   # 
> /usr/share/rubygems-integration/all/gems/async-rspec-1.16.1/lib/async/rspec/reactor.rb:57:in
>  `block in run_in_reactor'
>   # 
> /usr/share/rubygems-integration/all/gems/async-1.30.3/lib/async/task.rb:261:in
>  `block in make_fiber'
> 
> Finished in 2.71 seconds (files took 0.22921 seconds to load)
> 10 examples, 2 failures
> 
> Failed examples:
> 
> rspec './spec/localhost/protocol_spec.rb[1:1:2]' # Localhost::Authority 
> behaves like valid protocol can connect using HTTP over TLSv1.2
> rspec './spec/localhost/protocol_spec.rb[1:2:2]' # Localhost::Authority 
> behaves like valid protocol can connect using HTTP over default
> 
> /usr/bin/ruby3.1 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.1" failed: 

The full build log is attached.

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


ruby-localhost.log.gz
Description: application/gzip


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-localhost
Source-Version: 1.1.9-2
Done: Antonio Terceiro 

We believe that the bug you reported is fixed in the latest version of
ruby-localhost, 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.
Antonio Terceiro  (supplier of updated ruby-localhost 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 07 Feb 2023 18:31:57 +0100
Source: ruby-localhost
Architecture: source
Version: 1.1.9-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Antonio Terceiro 
Closes: 1027080
Changes:
 ruby-localhost (1.1.9-2) unstable; urgency=medium
 .
   * Skip curl tests (Closes: #1027080)
   * Add test to not reuse serial numbers
Checksums-Sha1:
 521acc8de4d00a993f69aeb348509d17247a8db1 2175 ruby-localhost_1.1.9-2.dsc
 cfd2e779ed7c03d247a39f1e6c1d6c36049488b0 3996 
ruby-localhost_1.1.9-2.debian.tar.xz
 a46ca5a8a13dd0de402be1d5017203084dfc3271 10223 
ruby-localhost_1.1.9-2_amd64.buildinfo
Checksums-Sha256:
 9f83554fb62283be039337b35538aa4f5ee9d3e9638a035084b0662e09881e1b 2175 
ruby-localhost_1.1.9-2.dsc
 8d1fa78c326514be848b0a3b543d2b5add3d808579272efe4d8dde36c04f3caf 3996 
ruby-localhost_1.1.9-2.debian.tar.xz
 ae03b95ec8d6e3a4fad6861c7dafd94a94fa153083d1cfb70541dbcf05cc958f 10223 
ruby-localhost_1.1.9-2_amd64.buildinfo
Files:
 bdcdced0306e5e7950bd4b5c81d05d90 2175 ruby optional ruby-localhost_1.1.9-2.dsc
 075f59a31fba84b4192d36312e417326 3996 ruby optional 
ruby-localhost_1.1.9-2.debian.tar.xz
 36

Bug#1030427: marked as pending in trapperkeeper-metrics-clojure

[Jérôme Charaoui]

Control: tag -1 pending

Hello,

Bug #1030427 in trapperkeeper-metrics-clojure 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/clojure-team/trapperkeeper-metrics-clojure/-/commit/0a6c16e047b5bc56d7ab7114156a13ad9fbceedd


drop jackson and snakeyaml version overrides

Avoid leaking bogus dependency versions in maven-repo. Requires updated
build-deps where the issue is fixed and makes the project.clj overrides
obsolete.

Closes: #1030427


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1030427

Processed: Bug#1030427 marked as pending in trapperkeeper-metrics-clojure

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1030427 [src:trapperkeeper-metrics-clojure] trapperkeeper-metrics-clojure: 
FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and 
the artifact org.clojure:tools.namespace:jar:debian has not been downloaded 
from it before.
Added tag(s) pending.

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

Bug#1030814: openldap: autopkgtest regression

[Ryan Tandy]

Hi, thanks for reporting.

On Tue, Feb 07, 2023 at 07:25:31PM +0200, Adrian Bunk wrote:

/tmp/autopkgtest-lxc.jrj8ozx8/downtmp/build.7fx/src/debian/tests/sha2-contrib: 
line 6: slappasswd: command not found


The dependency is definitely installed so it must be a PATH issue. Maybe 
because this test doesn't require root... Worked for me locally (qemu 
backend) so I'm a little surprised debci is different.  Will fix ASAP.

Bug#1030815: keyman: Missing autopkgtest dependency on pkg-config

[Adrian Bunk]

Source: keyman
Version: 16.0.138-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/k/keyman/31022569/log.gz

...
autopkgtest [03:17:05]: test test-build: [---
/tmp/autopkgtest-lxc.1u3zjijx/downtmp/build.9GP/src/debian/tests/test-build: 
line 18: pkg-config: command not found
In file included from /usr/include/keyman/keyboardprocessor.h:103,
 from keymantest.c:1:
/usr/include/keyman/keyboardprocessor_bits.h:69:10: fatal error: km_types.h: No 
such file or directory
   69 | #include 
  |  ^~~~
compilation terminated.
autopkgtest [03:17:05]: test test-build: ---]
autopkgtest [03:17:05]: test test-build:  - - - - - - - - - - results - - - - - 
- - - - -
...

Bug#1030814: openldap: autopkgtest regression

[Adrian Bunk]

Source: openldap
Version: 2.5.13+dfsg-4
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/o/openldap/31139461/log.gz

...
autopkgtest [09:28:43]: test sha2-contrib: [---
/tmp/autopkgtest-lxc.jrj8ozx8/downtmp/build.7fx/src/debian/tests/sha2-contrib: 
line 6: slappasswd: command not found
autopkgtest [09:28:44]: test sha2-contrib: ---]
autopkgtest [09:28:44]: test sha2-contrib:  - - - - - - - - - - results - - - - 
- - - - - -
sha2-contrib FAIL non-zero exit status 127
autopkgtest [09:28:44]: test sha2-contrib:  - - - - - - - - - - stderr - - - - 
- - - - - -
/tmp/autopkgtest-lxc.jrj8ozx8/downtmp/build.7fx/src/debian/tests/sha2-contrib: 
line 6: slappasswd: command not found
autopkgtest [09:28:44]:  summary
slapdPASS (superficial)
smbk5pwd PASS (superficial)
sha2-contrib FAIL non-zero exit status 127

Bug#1030530: Python 3.10 in bookworm

[karthek]

Sorry for spamming…
Resending the same message, I just remembered debian.org ignores mails
from mail@* addresses.

On Tue, Feb 07, 2023 at 02:24:08PM +, Stefano Rivera wrote:
> > See "ITP pyenv" @ http://bugs.debian.org/978149 .
> 
> I think the Python development community would be very happy to see
> this. Debian's selected Python releases don't meet all the needs of
> Python developers, who typically want access to all supported Python 3
> versions (and possibly the next alpha), at all times.
> 

Indeed.

> I'd be happy to review and sponsor uploads.
> 

Thanks Stefano, I packaged it almost 2 years ago while working on
Android Open-source project (AOSP). While I got response from upstream,
I Haven't got any response from debian community back then apart from
interest in it from Julian a year ago.

Since then I also didn't find any DD nearyby my city to sign my key.

I'm happy to work on the packaging…

Bug#1030813: mumble: autopkgtest regression

[Adrian Bunk]

Source: mumble
Version: 1.3.4-2
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/m/mumble/31139421/log.gz

...
autopkgtest [09:23:28]: test command1: smoke
autopkgtest [09:23:28]: test command1: [---
bash: line 1: smoke: command not found
autopkgtest [09:23:29]: test command1: ---]
autopkgtest [09:23:29]: test command1:  - - - - - - - - - - results - - - - - - 
- - - -
command1 FAIL non-zero exit status 127

Bug#1002886: marked as done (human-icon-theme: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Tue, 07 Feb 2023 17:19:43 +
with message-id 
and subject line Bug#1002886: fixed in human-icon-theme 0.28.debian-7
has caused the Debian Bug report #1002886,
regarding human-icon-theme: Removal of obsolete debhelper compat 5 and 6 in 
bookworm
to be marked as done.

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

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


-- 
1002886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002886
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: human-icon-theme
Version: 0.28.debian-6.1
Severity: serious
Tags: sid bookworm
User: nthyk...@master.debian.org
Usertags: compat-5-6-removal

Hi,

The package human-icon-theme uses debhelper with a compat level of 5 or 6,
which is no longer supported [1].

Please bump the debhelper compat at your earliest convenience

  * Compat 13 is recommended (supported in stable-backports)

  * Compat 7 is the bare minimum


Thanks,
Andreas

[1] https://lists.debian.org/debian-devel/2020/07/msg00065.html
--- End Message ---
--- Begin Message ---
Source: human-icon-theme
Source-Version: 0.28.debian-7
Done: Boyuan Yang 

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated human-icon-theme package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 07 Feb 2023 11:41:05 -0500
Source: human-icon-theme
Binary: human-icon-theme
Architecture: source all
Version: 0.28.debian-7
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Boyuan Yang 
Description:
 human-icon-theme - Human Icon theme
Closes: 1002886
Changes:
 human-icon-theme (0.28.debian-7) unstable; urgency=medium
 .
   * QA upload.
   * debian/compat: Bump to v7 for now to avoid debhelper compat v5/v6
 removal. (Closes: #1002886)
Checksums-Sha1:
 af6df3d648b3678091789807d23bc610c2cb1bfa 2073 
human-icon-theme_0.28.debian-7.dsc
 c2f2ff3f3db90fbc8b7e20e70dc7be082788a6d6 756080 
human-icon-theme_0.28.debian.orig.tar.gz
 a4bd2f4c2339beb68d2d6b26e1326d52782dc7d8 28220 
human-icon-theme_0.28.debian-7.debian.tar.xz
 d41d338c19010d7cf6af9bd39b238cafaa3e0914 605444 
human-icon-theme_0.28.debian-7_all.deb
 501bb87b3544e4c82442d1b49e02e9e4e3de94ae 12386 
human-icon-theme_0.28.debian-7_amd64.buildinfo
Checksums-Sha256:
 b2ba0d223faa3a7f771110026e58e28d7b5593afeea0be1680910ab0a0757c59 2073 
human-icon-theme_0.28.debian-7.dsc
 f8130af08b1da793a80e73afe90a60d7fe4b053469d31f2c05b3eb41147aa4e3 756080 
human-icon-theme_0.28.debian.orig.tar.gz
 44e7f252acfa8b515b81234bbc4df73f016cec39344598381cfeaa880dff75e8 28220 
human-icon-theme_0.28.debian-7.debian.tar.xz
 c388f75173790c185eb7d26cde0097ccf8cdf600a9723cf39b514e891f7f33fc 605444 
human-icon-theme_0.28.debian-7_all.deb
 26dfe94f9b760a6b52fc05a3b5be1b03b560e07b950571902e0ccb121f3515cb 12386 
human-icon-theme_0.28.debian-7_amd64.buildinfo
Files:
 d06c87be20ed8cff628174ba0220cf1a 2073 non-free/x11 optional 
human-icon-theme_0.28.debian-7.dsc
 c0bf4ed7b0a204b84d39c1310fedb54b 756080 non-free/x11 optional 
human-icon-theme_0.28.debian.orig.tar.gz
 3b0bbb6f27367848c955a0b322e7b255 28220 non-free/x11 optional 
human-icon-theme_0.28.debian-7.debian.tar.xz
 8f208f25c3355299332220bb19b22a95 605444 non-free/x11 optional 
human-icon-theme_0.28.debian-7_all.deb
 5706ab1b82aa6875c73f442ea24067dc 12386 non-free/x11 optional 
human-icon-theme_0.28.debian-7_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIyBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmPigV8ACgkQwpPntGGC
Ws4cog/45xJG43a9VnxgtRPYYKYnDJDC23dbWVMQ7/darZlaIHov0rEspbAV+p2W
rCkuzJDsyaQG3epuWWliGiGs62y/YHI17nBoqUaL8LPf8NCSP3cLNq3JaOHJXBoV
ldls1PFPOheLHMyT4DV/+ngnBt3waz4mF8DG836eyztO0iGDFAaJpjB9PNNXKqdV
8c70h12UT7NUP8wSCUJvMGkIkjBUW1jqb441Hp9QPRIwlPPm98TLkanNcTm3Ki/U
QwStrtH3AEBCe77ac5RlrdeaCVyoD6fa6pIrfUsOA8kJJN1pXjQZTkBX7n/m0fPm
R8R+Tb0A/L6BKXLxsnrhX+8vqWdfd26mEdKSsgM1UjumUMw30mGgI+ci3N5mH5GY
nIcO2Gs5E2Xw6KHJPc4lQ0LItM6HhW449UMbH63VB2fpxqKpstETvRfhX79wyELO
gxjn1pKvEC+/RwZcGDgOETsRIc+kibHtOhtZ+YZ8W6oFqHESuhBUwGC2p2EEJCw8
5D/ZC0/Eq1P6nqSF4G02VWjxXTufvvNdN1

Bug#1029292: lomiri-greeter: Depends: lomiri-system-compositor but it is not installable

[Adrian Bunk]

On Fri, Jan 20, 2023 at 08:48:19PM +0200, Adrian Bunk wrote:
> Package: lomiri-greeter
> Version: 0.1~git20230111.ba0fc6a-4
> Severity: serious
> 
> The following packages have unmet dependencies:
>  lomiri-greeter : Depends: lomiri-system-compositor but it is not installable

As the version tracking of the BTS already correctly shows, 0.1-1 now in 
unstable is based on 0.1~git20230111.ba0fc6a-4 and lacks this fix that
was in 0.1~git20230111.ba0fc6a-5.

cu
Adrian

Bug#1030812: autopkgtest failure : it should not work with ruby-omniauth >= 2

[Lucas Kanashiro]

Source: ruby-omniauth-bitbucket
Version: 0.0.2-1.1
Severity: Serious

In ruby-omniauth-bitbucket gemspec we can see:

$ cat omniauth-bitbucket.gemspec | grep omniauth | grep dependency
  s.add_dependency 'omniauth', '~> 1.1'
  s.add_dependency 'omniauth-oauth', '~> 1.0'

This should not work since we already have ruby-omniauth >= 2 in testing 
and unstable:


$ rmadison -u debian ruby-omniauth
ruby-omniauth | 1.2.1-1+deb8u1  | oldoldoldstable   | source, all
ruby-omniauth | 1.3.1-1+deb9u1  | oldoldstable  | source, all
ruby-omniauth | 1.8.1-1~bpo9+1  | stretch-backports | source, all
ruby-omniauth | 1.8.1-1 | oldstable | source, all
ruby-omniauth | 1.9.1-1~bpo10+1 | buster-backports  | source, all
ruby-omniauth | 1.9.1-1 | stable    | source, all
ruby-omniauth | 2.1.1-1 | testing   | source, all
ruby-omniauth | 2.1.1-1 | unstable  | source, all

This is not causing a FTBFS because we are not explicitly checking 
dependencies during tests (this is forced in autopkgtest), if the 
following change is added we can reproduce the same autopkgtest failure 
during the build:


commit 88dbbe95f4b83859ba2e009d3c97610f66b1fcff (HEAD -> master)
Author: Lucas Kanashiro 
Date:   Tue Feb 7 13:58:36 2023 -0300

    d/rules: check dependencies when running tests

    This demonstrates the FTBFS happening because we have ruby-omniauth 
>= 2

    in the archive. The same failure is reproducible with autopkgtest.

diff --git a/debian/rules b/debian/rules
index 00f8a91..2fab9b6 100755
--- a/debian/rules
+++ b/debian/rules
@@ -12,7 +12,7 @@
 #export DH_RUBY_GEMSPEC=gem.gemspec
 #
 # Uncomment to check dependencies during build:
-# export GEM2DEB_TEST_RUNNER = --check-dependencies
+export GEM2DEB_TEST_RUNNER = --check-dependencies

 %:
    dh $@ --buildsystem=ruby --with ruby


All these mean that we likely have a broken ruby-omniauth-bitbucket in 
testing, we should not ship this package in a stable release. Upstream 
is inactive since 2017, so I do not expect any fix from them.


--
Lucas Kanashiro

Bug#1030811: python-qrcode FTBFS: ModuleNotFoundError: No module named 'typing_extensions'

[Adrian Bunk]

Source: python-qrcode
Version: 7.4.2-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=python-qrcode&arch=all&ver=7.4.2-1&stamp=1675788862&raw=0

...
 ERRORS 
__ ERROR collecting .pybuild/cpython3_3.11/build/qrcode/tests/test_example.py __
ImportError while importing test module 
'/<>/.pybuild/cpython3_3.11/build/qrcode/tests/test_example.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.11/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
qrcode/__init__.py:1: in 
from qrcode.main import QRCode
qrcode/main.py:15: in 
from typing_extensions import Literal
E   ModuleNotFoundError: No module named 'typing_extensions'
__ ERROR collecting .pybuild/cpython3_3.11/build/qrcode/tests/test_qrcode.py ___
ImportError while importing test module 
'/<>/.pybuild/cpython3_3.11/build/qrcode/tests/test_qrcode.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.11/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
qrcode/__init__.py:1: in 
from qrcode.main import QRCode
qrcode/main.py:15: in 
from typing_extensions import Literal
E   ModuleNotFoundError: No module named 'typing_extensions'
_ ERROR collecting .pybuild/cpython3_3.11/build/qrcode/tests/test_qrcode_svg.py 
_
ImportError while importing test module 
'/<>/.pybuild/cpython3_3.11/build/qrcode/tests/test_qrcode_svg.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.11/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
qrcode/__init__.py:1: in 
from qrcode.main import QRCode
qrcode/main.py:15: in 
from typing_extensions import Literal
E   ModuleNotFoundError: No module named 'typing_extensions'
__ ERROR collecting .pybuild/cpython3_3.11/build/qrcode/tests/test_release.py __
ImportError while importing test module 
'/<>/.pybuild/cpython3_3.11/build/qrcode/tests/test_release.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.11/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
qrcode/__init__.py:1: in 
from qrcode.main import QRCode
qrcode/main.py:15: in 
from typing_extensions import Literal
E   ModuleNotFoundError: No module named 'typing_extensions'
__ ERROR collecting .pybuild/cpython3_3.11/build/qrcode/tests/test_script.py ___
ImportError while importing test module 
'/<>/.pybuild/cpython3_3.11/build/qrcode/tests/test_script.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.11/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
qrcode/__init__.py:1: in 
from qrcode.main import QRCode
qrcode/main.py:15: in 
from typing_extensions import Literal
E   ModuleNotFoundError: No module named 'typing_extensions'
___ ERROR collecting .pybuild/cpython3_3.11/build/qrcode/tests/test_util.py 
ImportError while importing test module 
'/<>/.pybuild/cpython3_3.11/build/qrcode/tests/test_util.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.11/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
qrcode/__init__.py:1: in 
from qrcode.main import QRCode
qrcode/main.py:15: in 
from typing_extensions import Literal
E   ModuleNotFoundError: No module named 'typing_extensions'
=== short test summary info 
ERROR qrcode/tests/test_example.py
ERROR qrcode/tests/test_qrcode.py
ERROR qrcode/tests/test_qrcode_svg.py
ERROR qrcode/tests/test_release.py
ERROR qrcode/tests/test_script.py
ERROR qrcode/tests/test_util.py
!!! Interrupted: 6 errors during collection 
== 6 errors in 0.22s ===
E: pybuild pybuild:388: test: plugin distutils failed with: exit code=2: cd 
/<>/.pybuild/cpython3_3.11/build; python3.11 -m pytest -k 'not 
test_script'
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 
returned exit code 13
make: *** [debian/rules:6: binary-indep] Error 25

Bug#1029198: marked as done (bugs.debian.org: linux-image-6.1.0-1-amd64/testing ERROR:M=/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.1/b)

[Curtis Dean Smith]

Hello!
I am still experiencing this bug.  Here is the log from my latest
attempt to update:
=DKMS
make.log for xtrx-0.0.1+git20190320.5ae3a3e-3.1 for kernel
6.1.0-3-amd64 (x86_64)
Tue Feb  7 08:47:34 AM PST 2023
make: Entering directory '/usr/src/linux-headers-6.1.0-3-amd64'
  CC [M] 
/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.1/build/xtrx.o
/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.1/build/xtrx.c:518:27:
error: initialization of ‘void (*)(struct uart_port *, struct
ktermios *, const struct ktermios *)’ from incompatible pointer type
‘void (*)(struct uart_port *, struct ktermios *, struct ktermios
*)’ [-Werror=incompatible-pointer-types]
  518 | .set_termios= xtrx_uart_set_termios,
  |   ^
/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.1/build/xtrx.c:518:27:
note: (near initialization for ‘xtrx_uart_ops.set_termios’)
cc1: some warnings being treated as errors
make[1]: ***
[/usr/src/linux-headers-6.1.0-3-common/scripts/Makefile.build:255:
/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.1/build/xtrx.o] Error 1
make: *** [/usr/src/linux-headers-6.1.0-3-common/Makefile:2017:
/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.1/build] Error 2
make: Leaving directory '/usr/src/linux-headers-6.1.0-3-amd64'
=

On 2/1/2023 at 10:21 PM, "Debian Bug Tracking System"  wrote:Your
message dated Thu, 02 Feb 2023 06:10:28 +
with message-id 
and subject line Bug#1029135: fixed in xtrx-dkms
0.0.1+git20190320.5ae3a3e-3.2
has caused the Debian Bug report #1029135,
regarding bugs.debian.org: linux-image-6.1.0-1-amd64/testing
ERROR:M=/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.1/b
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.)
-- 
1029135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029135
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1005899: marked as done (mplayer needs someone's commitment to be part of testing)

[Debian Bug Tracking System]

Your message dated Tue, 07 Feb 2023 16:54:09 +
with message-id 
and subject line Bug#1005899: fixed in mplayer 2:1.5+svn38408-1
has caused the Debian Bug report #1005899,
regarding mplayer needs someone's commitment to be part of testing
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.)


-- 
1005899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005899
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mplayer
Version: 2:1.4+ds1-3
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm

Let's stop pretending that mplayer is maintained. The upstream mailing
list infrastructure is gone and development has been minimal over the
last couple of months and years. So I think we should not include
mplayer in bookworm. mpv is a worthy replacement for mplayer.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: mplayer
Source-Version: 2:1.5+svn38408-1
Done: Lorenzo Puliti 

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

Debian distribution maintenance software
pp.
Lorenzo Puliti  (supplier of updated mplayer package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 26 Jan 2023 20:14:25 +0100
Source: mplayer
Architecture: source
Version: 2:1.5+svn38408-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Lorenzo Puliti 
Closes: 920485 983788 1004579 1005899 1009714
Changes:
 mplayer (2:1.5+svn38408-1) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Remove constraints unnecessary since buster
 .
   [ Lorenzo Puliti ]
   * New upstream svn snapshot 1.5+svn38408 (Closes: #1009714)
   - fixes FTBFS with recent ffmpeg (Closes: #1004579 #1030190)
   - fixes CVE-2022-38600, CVE-2022-38864, CVE-2022-38861,
 see #1021013
   - fixes broken theora (ogv) playback (Closes: #920485)
   * debian/patches:
   - temporary drop Debian version patch
   - drop 0007-ad_spdif patch, merged upstream
   - refresh other patches
   * New maintainer (Closes: #1005899)
   * Relax mplayer-skin dependency to recommends: mplayer-gui
  now has a minimalistic build-in skin. This is to avoid a circular
  dependency between mplayer-gui and mplayer-skin-blue.
 Thanks to Ingo Brückl (Closes: #983788)
   * bump Standards-Version to 4.6.2
   * Fix mismatched lintian overrides
   * enable the salsa.ci pipeline
   * update B-D replacing transitional packages with real ones
Checksums-Sha1:
 d24a4d490a132a59c051bcfc55da1f769c9894af 3228 mplayer_1.5+svn38408-1.dsc
 5d0285799a53f40f4d0961b0ae20d6d52abea408 15680651 
mplayer_1.5+svn38408.orig.tar.gz
 63803b15f00bf3d5db3d2318c3995748b66f1820 33084 
mplayer_1.5+svn38408-1.debian.tar.xz
 1e563a8c3901eb87f7d666ad93ba70a5deaee268 17503 
mplayer_1.5+svn38408-1_source.buildinfo
Checksums-Sha256:
 b554dac4b6fb842f22e2bfe97f939325556f09fd7609256e7fc52b6c1d32e191 3228 
mplayer_1.5+svn38408-1.dsc
 ff57bc5b13a85ad541930af5385d9c3dfb405632903844d9873a219f83bc5e82 15680651 
mplayer_1.5+svn38408.orig.tar.gz
 6cbc7b6927b6292b4e6800bf44a6575734d4039f887f94e935939260ecc1fb8f 33084 
mplayer_1.5+svn38408-1.debian.tar.xz
 5622b510e4a9f6ca0f0406547e436cae9a986b39b0d8b98af1089419f48e7f89 17503 
mplayer_1.5+svn38408-1_source.buildinfo
Files:
 4eb4036ed0628e32f06ab83e63092b2a 3228 video optional mplayer_1.5+svn38408-1.dsc
 17a5491846a87abe504370754ed15d7f 15680651 video optional 
mplayer_1.5+svn38408.orig.tar.gz
 2d5b996afff9a810b707741991d7d427 33084 video optional 
mplayer_1.5+svn38408-1.debian.tar.xz
 d9b43b755f2169a15576342bb5c49aa1 17503 video optional 
mplayer_1.5+svn38408-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAmPifDcACgkQweDZLphv
fH6yCg//TnbqNloMxTi2SZ5XIylDtO00ZR3MjeoY9EpXP7V5hsY0j1U86Ch/zHtj
xxm23A7nxvjobJB6++IPpcwM0ogKLVWyua4zGMb9bRbQO2Hl54jF1gQ5fDlawM4G
TlcVWJlUuBqfovqPxVxp6JSMqU69lifQtZeL767K8NmopKriItCkblyB5nLyH3rJ
RwjZXo2cz15o/dx0ZDNuCig9JiC2uVkojWGzQuXyjZate4kX4CFAcV7evAzPxIdQ
v+DmJ

Bug#1004579: marked as done (mplayer: FTBFS with ffmpeg 5.0)

[Debian Bug Tracking System]

Your message dated Tue, 07 Feb 2023 16:54:09 +
with message-id 
and subject line Bug#1004579: fixed in mplayer 2:1.5+svn38408-1
has caused the Debian Bug report #1004579,
regarding mplayer: FTBFS with ffmpeg 5.0
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.)


-- 
1004579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004579
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mplayer
Version: 2:1.4+ds1-3
Severity: important
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs
Usertags: ffmpeg5.0

mplayer FTBFS with ffmpeg 5.0 (available in experimental):
| cc -MMD -MP -Wundef -W -Wall -Wall -Wno-switch -Wno-parentheses 
-Wpointer-arith -Wredundant-decls -Werror=format-security -Wstrict-prototypes 
-Wmissing-prototypes -Wdisabled-optimization -Wno-pointer-sign 
-Wdeclaration-after-statement -std=gnu99 -Werror-implicit-function-declaration 
-D_POSIX_C_SOURCE=200112 -D_XOPEN_SOURCE=600 -D_ISOC99_SOURCE -I. -Iffmpeg -O2 
-march=x86-64 -mtune=generic -pipe -g  -fno-tree-vectorize 
-fno-asynchronous-unwind-tables -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE64_SOURCE -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -fpie -DPIC -D_REENTRANT 
-I/usr/include/p11-kit-1 -I/usr/include/samba-4.0 -I/usr/include/   
-D_REENTRANT  -I/usr/include/freetype2 -I/usr/include/libpng16 -DZLIB_CONST 
-I/usr/include/bs2b -I/usr/include/x86_64-linux-gnu 
-I/usr/include/x86_64-linux-gnu -pthread -I/usr/include/gtk-2.0 
-I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
-I/usr/include/x86_64-linux-gnu -I/usr/include/pango-1.0 
-I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/libmount 
-I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo 
-I/usr/include/pixman-1 -I/usr/include/harfbuzz -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/uuid 
-I/usr/include/freetype2 -I/usr/include/libpng16  -c -o libvo/vo_gl.o 
libvo/vo_gl.c
| libvo/vo_fbdev2.c:103:15: warning: missing initializer for field 'transp' of 
'struct fb_cmap' [-Wmissing-field-initializers]
|   103 | static struct fb_cmap fb_oldcmap = { 0, 256, fb_ored, fb_ogreen, 
fb_oblue };
|   |   ^~~
| In file included from libvo/vo_fbdev2.c:31:
| /usr/include/linux/fb.h:286:16: note: 'transp' declared here
|   286 | __u16 *transp;  /* transparency, can be NULL 
*/
|   |^~
| libvo/vo_fbdev2.c: In function 'config':
| libvo/vo_fbdev2.c:224:27: warning: comparison of integer expressions of 
different signedness: '__u32' {aka 'unsigned int'} and 'int' [-Wsign-compare]
|   224 | if (fb_vinfo.xres < in_width || fb_vinfo.yres < in_height) {
|   |   ^
| libvo/vo_fbdev2.c:224:55: warning: comparison of integer expressions of 
different signedness: '__u32' {aka 'unsigned int'} and 'int' [-Wsign-compare]
|   224 | if (fb_vinfo.xres < in_width || fb_vinfo.yres < in_height) {
|   |   ^
| libvo/vo_fbdev2.c:211:58: warning: unused parameter 'title' 
[-Wunused-parameter]
|   211 | uint32_t d_height, uint32_t flags, char *title,
|   |~~^
| libvo/vo_fbdev2.c: In function 'set_bpp':
| libvo/vo_fbdev2.c:61:42: warning: this statement may fall through 
[-Wimplicit-fallthrough=]
|61 | p->transp.length = 8;
|   | ~^~~
| libvo/vo_fbdev2.c:63:17: note: here
|63 | case 24:
|   | ^~~~
| In file included from ./mp_core.h:27,
|  from libvo/vo_png.c:35:
| ./libmpdemux/demuxer.h: In function 'new_demux_packet':
| ./libmpdemux/demuxer.h:98:29: warning: left shift of negative value 
[-Wshift-negative-value]
|98 | #define MP_NOPTS_VALUE (-1LL<<63) //both int64_t and double should be 
able to represent this exactly
|   | ^~
| ./libmpdemux/demuxer.h:289:11: note: in expansion of macro 'MP_NOPTS_VALUE'
|   289 |   dp->pts=MP_NOPTS_VALUE;
|   |   ^~
| ./libmpdemux/demuxer.h:98:29: warning: left shift of negative value 
[-Wshift-negative-value]
|98 | #define MP_NOPTS_VALUE (-1LL<<63) //both int64_t and double should be 
able to represent this exactly
|   |   

Bug#1030810: django-sass-processor FTBFS: django.core.exceptions.ImproperlyConfigured

[Adrian Bunk]

Source: django-sass-processor
Version: 1.2.2-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=django-sass-processor&arch=all&ver=1.2.2-1&stamp=1675788416&raw=0

...
 ERRORS 
__ ERROR at setup of SassProcessorTest.test_management_command_django __

cls = 

@classmethod
def setUpClass(cls):
>   super().setUpClass()

/usr/lib/python3/dist-packages/django/test/testcases.py:1182: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3/dist-packages/django/test/testcases.py:183: in setUpClass
cls._add_databases_failures()
/usr/lib/python3/dist-packages/django/test/testcases.py:204: in 
_add_databases_failures
cls.databases = cls._validate_databases()
/usr/lib/python3/dist-packages/django/test/testcases.py:190: in 
_validate_databases
if alias not in connections:
/usr/lib/python3/dist-packages/django/utils/connection.py:73: in __iter__
return iter(self.settings)
/usr/lib/python3/dist-packages/django/utils/functional.py:48: in __get__
res = instance.__dict__[self.name] = self.func(instance)
/usr/lib/python3/dist-packages/django/utils/connection.py:45: in settings
self._settings = self.configure_settings(self._settings)
/usr/lib/python3/dist-packages/django/db/utils.py:144: in configure_settings
databases = super().configure_settings(databases)
/usr/lib/python3/dist-packages/django/utils/connection.py:50: in 
configure_settings
settings = getattr(django_settings, self.settings_name)
/usr/lib/python3/dist-packages/django/conf/__init__.py:82: in __getattr__
self._setup(name)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = , name = 'DATABASES'

def _setup(self, name=None):
"""
Load the settings module pointed to by the environment variable. This
is used the first time settings are needed, if the user hasn't
configured settings manually.
"""
settings_module = os.environ.get(ENVIRONMENT_VARIABLE)
if not settings_module:
desc = ("setting %s" % name) if name else "settings"
>   raise ImproperlyConfigured(
"Requested %s, but settings are not configured. "
"You must either define the environment variable %s "
"or call settings.configure() before accessing settings."
% (desc, ENVIRONMENT_VARIABLE))
E   django.core.exceptions.ImproperlyConfigured: Requested setting 
DATABASES, but settings are not configured. You must either define the 
environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before 
accessing settings.

/usr/lib/python3/dist-packages/django/conf/__init__.py:63: ImproperlyConfigured
...
=== short test summary info 
ERROR 
tests/test_sass_processor.py::SassProcessorTest::test_management_command_django
ERROR 
tests/test_sass_processor.py::SassProcessorTest::test_management_command_jinja2
ERROR 
tests/test_sass_processor.py::SassProcessorTest::test_management_command_multiple
ERROR tests/test_sass_processor.py::SassProcessorTest::test_sass_processor - ...
ERROR tests/test_sass_processor.py::SassProcessorTest::test_sass_src_django
ERROR tests/test_sass_processor.py::SassProcessorTest::test_sass_src_jinja2
ERROR 
tests/test_sass_processor.py::SassProcessorTest::test_sass_src_jinja2_variable
ERROR tests/test_sass_processor.py::SassProcessorTest::test_use_storage_django
ERROR tests/test_sass_processor.py::SassProcessorTest::test_use_storage_jinja2
ERROR tests/test_sass_processor.py::SassProcessorTest::test_use_storage_multiple
 2 warnings, 10 errors in 1.39s 
E: pybuild pybuild:388: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.11_django-sass-processor/build; python3.11 
-m pytest tests
dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit 
code 13
make: *** [debian/rules:8: build-indep] Error 25

Bug#1017724: marked as done (libaperture-0: flaky autopkgtest on multiple architectures: timeout_reached: code should not be reached)

[Debian Bug Tracking System]

Your message dated Tue, 07 Feb 2023 16:51:53 +
with message-id 
and subject line Bug#1017724: fixed in libaperture-0 0.1.0+git20200908-3.1
has caused the Debian Bug report #1017724,
regarding libaperture-0: flaky autopkgtest on multiple architectures: 
timeout_reached: code should not be reached
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.)


-- 
1017724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017724
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libaperture-0
Version: 0.1.0+git20200908-3
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky

The autopkgtest for libaperture-0 seems to be intermittently failing
with a timeout, particularly on armel and armhf. Some examples:

- 
https://ci.debian.net/data/autopkgtest/testing/armel/liba/libaperture-0/24979047/log.gz
- 
https://ci.debian.net/data/autopkgtest/testing/armhf/liba/libaperture-0/23940701/log.gz
- 
https://ci.debian.net/data/autopkgtest/testing/amd64/liba/libaperture-0/23958726/log.gz

all of which look like this:

> ok 8 /viewfinder/no_camera
> # Aperture-DEBUG: New camera detected: Dummy Camera
> Bail out! ERROR:utils.c:48:timeout_reached: code should not be reached
> **
> ERROR:utils.c:48:timeout_reached: code should not be reached
> Aborted

When testing a proposed update to a package it depends on (such as
gdk-pixbuf or glibc), the test failure is assumed to be a regression in
the updated package, which can delay or prevent testing migration.

Please look into whether this test can be made reliable, or if it cannot,
mark the test with "Restrictions: flaky" so that it doesn't disrupt other
packages.

Upstream commit
https://gitlab.gnome.org/jwestman/libaperture/-/commit/b5bd52a63994becadd5be88814824c0679f85046
looks potentially relevant.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: libaperture-0
Source-Version: 0.1.0+git20200908-3.1
Done: Adrian Bunk 

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

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

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated libaperture-0 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 07 Feb 2023 18:35:57 +0200
Source: libaperture-0
Architecture: source
Version: 0.1.0+git20200908-3.1
Distribution: unstable
Urgency: medium
Maintainer: DebianOnMobile Maintainers 

Changed-By: Adrian Bunk 
Closes: 1017724
Changes:
 libaperture-0 (0.1.0+git20200908-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Mark the autopkgtest as flaky. (Closes: #1017724)
Checksums-Sha1:
 bb3141777a3e02bdea82a12e7f439a3062eab9fb 2801 
libaperture-0_0.1.0+git20200908-3.1.dsc
 ead6c6a0b2f9858d5cecaddf7013f117396f6551 4712 
libaperture-0_0.1.0+git20200908-3.1.debian.tar.xz
Checksums-Sha256:
 4218a5ea2035a59097e040862726ebf2492192778ce871174e01ebe20890fbdf 2801 
libaperture-0_0.1.0+git20200908-3.1.dsc
 e94d503836dc28d9992fcfe80841c2694a885c1588aed74f5c1d6af8fe9c3340 4712 
libaperture-0_0.1.0+git20200908-3.1.debian.tar.xz
Files:
 35ba2b22e6aa4286c6182d81e9f3d284 2801 libs optional 
libaperture-0_0.1.0+git20200908-3.1.dsc
 9bd6920f2899e016d6c023a001760c00 4712 libs optional 
libaperture-0_0.1.0+git20200908-3.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmPifjgACgkQiNJCh6LY
mLG32g/8CMOiTsL267eWWO4gMtfOPxULg64Yv78SVTCF0zVKFy/WDxZo0dpyXh9h
XI56pLpdoZ8KcotrZW5mkWmPP3qK06X1rcT3oE1lTJR49Tnr+ZPPJCVJ7LTNQqcQ
9fYxZjrdfgQwqs/PIJz5/N7O7+lNknr9g1WJLkct1SuKgHz0GkOwnrk7l3hoCu1T
+ymdNIgcW9TIzQJp47aqRKNG2rNp2EbSPw2cGTKtRTaCOeXOlTSf21uQHkRIyos/
AjpQLgBOpzgXN+gX8gV1cU6dz4KX2gTfHy6gE79dL4DUF+swfbVX5Zn6OHPVgdIP
pSCy/nHe+L9k6fBE94yw0oHYqhFguEgaSR0SmmPBAzH2+6SFYaKnwYbui7zdgTAA
uiR9OSe96JrAmFNV4uu3aNS6gaXz4+QCU8evKIM7HoNEue/GLRaoCxDrA9NDwXgt
XF3bYBtWjFfJUfG39Ceu1Q89xuM7Fbp+WOefaBnGVW17LQ1LFRFiycwYmkbKLoBk
VgGGL/D39ZYVTHnx8zW0RCJKk/Nu3Zo839F1r3wtlMoHdXcsEcApjsIqFl423d2P
GvMqV9IbdTwXlFzfpAwT51QgVVb+K3s82oxgWDbHoubOmRBjLqJRP2vek6wGJR+i
eC87LfDm455w9TsfLVLxwxTHto0mR39RvdCAW3In3hYrEa

Bug#1030510: Info received (Bug#1030510: Info received (Bug#1030510: Info received (mariadb: FTBFS on s390x: timeout)))

[Otto Kekäläinen]

Control: severity -1 normal
Control: tags -1 help

The s390x build is still failing after 5 retries at
https://buildd.debian.org/status/package.php?p=mariadb. The issue
seems to be with Debian buildd, as the Launchpad s390x build passed
just fine without the need to retry anything:
https://launchpad.net/~mysql-ubuntu/+archive/ubuntu/mariadb-10.11/+builds?build_text=&build_state=all

It seems to crash on different tests every time. I could disable the
entire test suite, but that feels like a bad idea.

I need help - if the s390x build does not pass, the 10.11 cannot enter
Debian testing (Bookworm).


(this email is for https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030510)

Processed: Re: Bug#1030510: Info received (Bug#1030510: Info received (Bug#1030510: Info received (mariadb: FTBFS on s390x: timeout)))

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #1030510 [src:mariadb] mariadb: FTBFS on s390x: crash on munmap(),
Severity set to 'normal' from 'serious'
> tags -1 help
Bug #1030510 [src:mariadb] mariadb: FTBFS on s390x: crash on munmap(),
Added tag(s) help.

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

Processed: libaperture-0: diff for NMU version 0.1.0+git20200908-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1017724 + patch
Bug #1017724 [src:libaperture-0] libaperture-0: flaky autopkgtest on multiple 
architectures: timeout_reached: code should not be reached
Added tag(s) patch.

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

Bug#1017724: libaperture-0: diff for NMU version 0.1.0+git20200908-3.1

[Adrian Bunk]

Control: tags 1017724 + patch

Dear maintainer,

I've uploaded an NMU for libaperture-0 (versioned as 0.1.0+git20200908-3.1).
The diff is attached to this message.

cu
Adrian
diff -Nru libaperture-0-0.1.0+git20200908/debian/changelog libaperture-0-0.1.0+git20200908/debian/changelog
--- libaperture-0-0.1.0+git20200908/debian/changelog	2022-01-03 13:08:36.0 +0200
+++ libaperture-0-0.1.0+git20200908/debian/changelog	2023-02-07 18:35:57.0 +0200
@@ -1,3 +1,10 @@
+libaperture-0 (0.1.0+git20200908-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Mark the autopkgtest as flaky. (Closes: #1017724)
+
+ -- Adrian Bunk   Tue, 07 Feb 2023 18:35:57 +0200
+
 libaperture-0 (0.1.0+git20200908-3) unstable; urgency=medium
 
   * lintian override: aperture-0-examples does not ship 
diff -Nru libaperture-0-0.1.0+git20200908/debian/tests/control libaperture-0-0.1.0+git20200908/debian/tests/control
--- libaperture-0-0.1.0+git20200908/debian/tests/control	2021-07-15 19:29:59.0 +0300
+++ libaperture-0-0.1.0+git20200908/debian/tests/control	2023-02-07 18:35:50.0 +0200
@@ -8,4 +8,4 @@
  pkg-config,
  xauth,
  xvfb
-Restrictions: allow-stderr
+Restrictions: allow-stderr, flaky

Processed: add fixed version info

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 5.2.0+dfsg-2
Bug #1005628 {Done: Paul Gevers } 
[src:ruby-turbolinks-source] ruby-turbolinks-source: FTBFS: installing symlink 
lib/assets/javascripts/turbolinks.js pointing to parent path 
/usr/share/javascript/turbolinks/turbolinks.js ... is not allowed
Marked as fixed in versions ruby-turbolinks-source/5.2.0+dfsg-2.

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

Bug#1005628: add fixed version info

[Pirate Praveen]

Control: fixed -1 5.2.0+dfsg-2

Bug#1028152: marked as done (golang-github-likexian-gokit FTBFS: chown tmp: operation not permitted)

[Debian Bug Tracking System]

Your message dated Tue, 07 Feb 2023 16:13:12 +
with message-id 
and subject line Bug#1028152: fixed in golang-github-likexian-gokit 0.25.9-2
has caused the Debian Bug report #1028152,
regarding golang-github-likexian-gokit FTBFS: chown tmp: operation not permitted
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.)


-- 
1028152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028152
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-likexian-gokit
Version: 0.25.6-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=golang-github-likexian-gokit&arch=all

...
FAILgithub.com/likexian/gokit/xdaemon   0.012s
...
assert.go:197: 
/<>/obj-x86_64-linux-gnu/src/github.com/likexian/gokit/xfile/xfile_test.go:155
assert.go:170: ! unexpected error: "chown tmp: operation not permitted"
...
--- End Message ---
--- Begin Message ---
Source: golang-github-likexian-gokit
Source-Version: 0.25.9-2
Done: Thorsten Alteholz 

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

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated 
golang-github-likexian-gokit 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, 06 Feb 2023 18:02:15 +0100
Source: golang-github-likexian-gokit
Architecture: source
Version: 0.25.9-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Thorsten Alteholz 
Closes: 1028152
Changes:
 golang-github-likexian-gokit (0.25.9-2) unstable; urgency=medium
 .
   * debian/control: bump standard to 4.6.2 (no changes)
   * update patch to avoid tests that need higher privileges
 (Closes: #1028152)
Checksums-Sha1:
 99d5a47644ef3ce2c825de2a971c82736a60e725 2430 
golang-github-likexian-gokit_0.25.9-2.dsc
 641b32e182e61b6693eba1ee7e04218212451a2c 113395 
golang-github-likexian-gokit_0.25.9.orig.tar.gz
 92541e820b9b33dc9577f8ee88c7c1fcaf35aaee 3832 
golang-github-likexian-gokit_0.25.9-2.debian.tar.xz
 4f6fc9913029a826efad022e46526d8cf55db995 6612 
golang-github-likexian-gokit_0.25.9-2_amd64.buildinfo
Checksums-Sha256:
 d1cc57beb2f4757efc0613d8af8fbfa780454a02a8b303991db3045a4a2d9774 2430 
golang-github-likexian-gokit_0.25.9-2.dsc
 58345eb85abca1523bdff431f2460328bd6dffd58475007e6acf771f6354833d 113395 
golang-github-likexian-gokit_0.25.9.orig.tar.gz
 d9e3f0620151a9347101f486535a490b62cad1ca88fc1f225289947902a8555e 3832 
golang-github-likexian-gokit_0.25.9-2.debian.tar.xz
 b91397db6b34055787abae59cbfa6260800c39a9296b7fd1d83ec96fc8477842 6612 
golang-github-likexian-gokit_0.25.9-2_amd64.buildinfo
Files:
 bb5c880567bb24cac244f69626a4490c 2430 devel optional 
golang-github-likexian-gokit_0.25.9-2.dsc
 eb18475d916b8852ecb8431857c7a88e 113395 devel optional 
golang-github-likexian-gokit_0.25.9.orig.tar.gz
 8a9ff538b8caaeff497c7a1ab46d4c8d 3832 devel optional 
golang-github-likexian-gokit_0.25.9-2.debian.tar.xz
 d08d7a7049895dae95014f88d8c3cc8b 6612 devel optional 
golang-github-likexian-gokit_0.25.9-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKnBAEBCgCRFiEEYgH7/9u94Hgi6ruWlvysDTh7WEcFAmPhdg5fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYy
MDFGQkZGREJCREUwNzgyMkVBQkI5Njk2RkNBQzBEMzg3QjU4NDcTHGRlYmlhbkBh
bHRlaG9sei5kZQAKCRCW/KwNOHtYR6C0EAC6IVhGleW8cIuCZcvhQW9PfuNnJO4L
neZC4pFvL7lVnMJsBd6Ogoga3Uep96GMZR6ucJcPzH50dznDu4WYMrI/be0SFoT0
B0hOfr81Bhm1XBsIOl3YpJ6FomBLQU+SD1W9fNTDgmrCzdRNwAMbAWr/ZlqhWuQv
c1jqSHNdbCGqsfLGiljoZ26O8404KfUEuaCcTvo3ffHmq2EwJMbCIx+4BxD1/xs4
VyJ9/4jwpAjhvrJkc/GGky3HdRRuA4i1EvQf1rE3hxx9vPJrYGy+WDlYFrbi/pYw
38NX9R7hxsLo5bnPxbKg60nOal6qacXD63K7HSd1YKLHKsMZw/ZXIDfJXi9YrtL/
sJ8DOaRJz/ns0EUYOfqviUdisFZAic8rPvKe/MQs47ytL0f5Z3uNVn4h73SDbpBU
ldlbJZM+jU8WVAtnchbmTqixsj7fPINEe4v3FRyI/IywOEaR1Oo7UKNJxbPcz2oW
reWKxVFfIWKuAxGvRTT5ZnQo+S+NHfrSQ4ZeZIu2X/XpyjFM2p7/7M1uALkFwLYJ
yZa+24yeREKtRFiuZZ5xuYzHYgYnTotN9eeeta8LVndkuub3tBaUmLlFazUKIWww
6XfZaiQ8mgEqFwtFb3IphqxAN26dDdWwgXdBD8tFnEJYVDpC4CnZOKnrf+O8aca2
4UwTJwf8/8FwMg==
=/AZW
-END PGP SIG

Bug#1030806: pypy3: autopkgtest failure

[Adrian Bunk]

Source: pypy3
Version: 7.3.11+dfsg-2
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pypy3/31129646/log.gz

...
Installed /tmp/autopkgtest-lxc.t2xhtlgq/downtmp/autopkgtest_tmp/packages/fibpy
Processing dependencies for fibpy==42.0.0
Finished processing dependencies for fibpy==42.0.0
/usr/lib/python3/dist-packages/setuptools/command/easy_install.py:146: 
EasyInstallDeprecationWarning: easy_install command is deprecated. Use build 
and pip and other standards-based tools.
  warnings.warn(
/usr/lib/python3/dist-packages/setuptools/command/install.py:34: 
SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip 
and other standards-based tools.
  warnings.warn(
testFibPyPip

Usage:   
  /usr/bin/pypy3 -m pip install [options]  
[package-index-options] ...
  /usr/bin/pypy3 -m pip install [options] -r  
[package-index-options] ...
  /usr/bin/pypy3 -m pip install [options] [-e]  ...
  /usr/bin/pypy3 -m pip install [options] [-e]  ...
  /usr/bin/pypy3 -m pip install [options]  ...

no such option: --break-system-packages
ASSERT:Install fibpy via pip in /usr/local
ASSERT:fibpy was installed to /usr/local
/usr/bin/pypy3: No module named fibpy
ASSERT:Execute fibpy from /usr/local
ASSERT:Correct result expected:<8> but was:<>
testFibPyPipEditable

Usage:   
  /usr/bin/pypy3 -m pip install [options]  
[package-index-options] ...
  /usr/bin/pypy3 -m pip install [options] -r  
[package-index-options] ...
  /usr/bin/pypy3 -m pip install [options] [-e]  ...
  /usr/bin/pypy3 -m pip install [options] [-e]  ...
  /usr/bin/pypy3 -m pip install [options]  ...

no such option: --break-system-packages
ASSERT:Install editable fibpy via pip in /usr/local
ASSERT:fibpy was linked to /usr/local
/usr/bin/pypy3: No module named fibpy
ASSERT:Execute fibpy from /usr/local
ASSERT:Correct result expected:<8> but was:<>
testFibPyDistutilsLocal
running install
running bdist_egg
running egg_info
writing fibpy.egg-info/PKG-INFO
writing dependency_links to fibpy.egg-info/dependency_links.txt
writing top-level names to fibpy.egg-info/top_level.txt
reading manifest file 'fibpy.egg-info/SOURCES.txt'
writing manifest file 'fibpy.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-x86_64/egg
running install_lib
running build_py
creating build/bdist.linux-x86_64/egg
copying build/lib/fibpy.py -> build/bdist.linux-x86_64/egg
byte-compiling build/bdist.linux-x86_64/egg/fibpy.py to fibpy.pypy39.pyc
creating build/bdist.linux-x86_64/egg/EGG-INFO
copying fibpy.egg-info/PKG-INFO -> build/bdist.linux-x86_64/egg/EGG-INFO
copying fibpy.egg-info/SOURCES.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying fibpy.egg-info/dependency_links.txt -> 
build/bdist.linux-x86_64/egg/EGG-INFO
copying fibpy.egg-info/top_level.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying fibpy.egg-info/zip-safe -> build/bdist.linux-x86_64/egg/EGG-INFO
creating 'dist/fibpy-42.0.0-py3.9.egg' and adding 
'build/bdist.linux-x86_64/egg' to it
removing 'build/bdist.linux-x86_64/egg' (and everything under it)
Processing fibpy-42.0.0-py3.9.egg
Copying fibpy-42.0.0-py3.9.egg to /usr/local/lib/pypy3.9/dist-packages
Adding fibpy 42.0.0 to easy-install.pth file

Installed /usr/local/lib/pypy3.9/dist-packages/fibpy-42.0.0-py3.9.egg
Processing dependencies for fibpy==42.0.0
Finished processing dependencies for fibpy==42.0.0
/usr/lib/python3/dist-packages/setuptools/command/install.py:34: 
SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip 
and other standards-based tools.
  warnings.warn(
/usr/lib/python3/dist-packages/setuptools/command/easy_install.py:146: 
EasyInstallDeprecationWarning: easy_install command is deprecated. Use build 
and pip and other standards-based tools.
  warnings.warn(

Ran 7 tests.

FAILED (failures=8)
autopkgtest [21:46:12]: test module-install-local: ---]
autopkgtest [21:46:12]: test module-install-local:  - - - - - - - - - - results 
- - - - - - - - - -
module-install-local FAIL non-zero exit status 1
...
autopkgtest [21:48:14]:  summary
byte-compilation PASS
command-line PASS (superficial)
import-paths PASS
pypy3-tk PASS (superficial)
module-install-local FAIL non-zero exit status 1
module-install-user  FAIL non-zero exit status 1
module-install-venv  PASS
module-install-virtualenv PASS

Processed: severity of 1018922 is important

[Debian Bug Tracking System]

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

> severity 1018922 important
Bug #1018922 [kbibtex] kbibtex crashes on startup
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Processed: Fixed in version 3.0.5

[Debian Bug Tracking System]

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

> fixed 1025125 3.0.5
Bug #1025125 [src:ruby-sinatra] ruby-sinatra: CVE-2022-45442: Reflected File 
Download attack
The source 'ruby-sinatra' and version '3.0.5' do not appear to match any binary 
packages
Marked as fixed in versions ruby-sinatra/3.0.5.
> stop
Stopping processing here.

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

Processed: notfound 1025125 in 3.0.5-2

[Debian Bug Tracking System]

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

> notfound 1025125 3.0.5-2
Bug #1025125 [src:ruby-sinatra] ruby-sinatra: CVE-2022-45442: Reflected File 
Download attack
Ignoring request to alter found versions of bug #1025125 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#1030530: Python 3.10 in bookworm

[Julian Gilbey]

On Tue, Feb 07, 2023 at 12:31:23PM +0100, Joost van Baal-Ilić wrote:
> Op Tue, Feb 07, 2023 at 05:52:21AM + schreef Danial Behzadi دانیال بهزادی:
> > Does it worth trying to package pyenv for Debian? Ain't it against any 
> > rules?
> 
> See "ITP pyenv" @ http://bugs.debian.org/978149 .

Oh, how embarrassing - I already knew about this software a year ago!

Best wishes,

   Julian

Bug#1030784: marked as done (open-infrastructure-storage-tools: missing Breaks+Replaces: open-infrastructure-ceph-tools (<< 20190301-lts1-4))

[Debian Bug Tracking System]

Your message dated Tue, 07 Feb 2023 15:07:09 +
with message-id 
and subject line Bug#1030784: fixed in open-infrastructure-storage-tools 
20190301-lts1-5
has caused the Debian Bug report #1030784,
regarding open-infrastructure-storage-tools: missing Breaks+Replaces: 
open-infrastructure-ceph-tools (<< 20190301-lts1-4)
to be marked as done.

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

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


-- 
1030784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030784
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: open-infrastructure-storage-tools
Version: 20190301-lts1-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to cleanly
upgrade from 'testing'.
Due to insufficiently versioned Breaks+Replaces it is possible to
install a mix of packages from before and after the package rename,
which can cause crippled packages after removal of some packages.

Currently there are

Replaces: open-infrastructure-ceph-tools
Breaks: open-infrastructure-ceph-tools (<< 20190301-lts1-3~)

but the Breaks does not catch all versions before the rename
and the unversioned Replaces is too wide, catching the transitional
package, too, which may have unwanted side effects ...
Please use the same version for both: (<< 20190301-lts1-4)


cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: open-infrastructure-storage-tools
Source-Version: 20190301-lts1-5
Done: Daniel Baumann 

We believe that the bug you reported is fixed in the latest version of
open-infrastructure-storage-tools, which is due to be installed in the Debian 
FTP archive.

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

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

Debian distribution maintenance software
pp.
Daniel Baumann  (supplier of updated 
open-infrastructure-storage-tools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 07 Feb 2023 15:31:53 +0100
Source: open-infrastructure-storage-tools
Architecture: source
Version: 20190301-lts1-5
Distribution: sid
Urgency: high
Maintainer: Daniel Baumann 
Changed-By: Daniel Baumann 
Closes: 1030784
Changes:
 open-infrastructure-storage-tools (20190301-lts1-5) sid; urgency=high
 .
   * Uploading to sid, with bumped urgency due to upcoming freeze deadline.
   * Correcting breaks/replaces for clean upgrade from bullseye, thanks to
 Andreas Beckmann  (Closes: #1030784).
Checksums-Sha1:
 cbe9cf2cd36fad36657b38b23ff6eb19dbe6ed0d 2424 
open-infrastructure-storage-tools_20190301-lts1-5.dsc
 a0b85005a111af1b6bbd7b868e88431a6c0f989b 15720 
open-infrastructure-storage-tools_20190301-lts1-5.debian.tar.xz
 d5a17553c444e00ea640ccecae3771f6e2730643 8128 
open-infrastructure-storage-tools_20190301-lts1-5_amd64.buildinfo
Checksums-Sha256:
 56f4e4932d8cbc2ceaeeebf7f785736032ad8a309a3fd053cd400d65787e2872 2424 
open-infrastructure-storage-tools_20190301-lts1-5.dsc
 dae81b238aaad28fe2ed7a3189651962af184dc0e9c2c37db1afefe9ac05d0c7 15720 
open-infrastructure-storage-tools_20190301-lts1-5.debian.tar.xz
 fc89474b3f2c4d4b06cbe9c5ee1fa1389fe2951badff5adde5a1d079371a6951 8128 
open-infrastructure-storage-tools_20190301-lts1-5_amd64.buildinfo
Files:
 e4a48a36cf6d2a4213f8f2b356e0b491 2424 admin optional 
open-infrastructure-storage-tools_20190301-lts1-5.dsc
 a8ad718e2700ab8a243fb6f8591b35c2 15720 admin optional 
open-infrastructure-storage-tools_20190301-lts1-5.debian.tar.xz
 743aaf91247a31e6e6e9581b960544fc 8128 admin optional 
open-infrastructure-storage-tools_20190301-lts1-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAmPiYvIACgkQVc8b+Yar
uce/Pw/+KACDh/6Mf1GxmOyTC2DuZl7JeghrKPy/YbIpyyjLtMIoLHf4eghGGDdB
4kEiDJW7IJ/NbnkqbWOOzZhg9D5IZr1wG1SZAI6b6M/ffjqnP+DN/9uK0s8+coXt
EyRjR3GSepVAM3e38sBZ9WlDOzZkJam5C6S40PY9ii2gFPXJnpdUxgrJ+zrCQFR9
bBzihntuuKsAGBbhFv2M2R/kPXiU/KRWDdEoGjD99EqFUJ30sYR79/HpGmipMKRA
AZe9t2SX/6fTc8yrPpwEW4XiFa3oBMf7GvlARNIb/iMdNDkLYQHAL/J0bs1ck59m
BBENSZktcA/+FuS2iD/gtNFXNBv6n44KEP1ydY/AtF3OyrlgAHuUmX5j19LwBpGI
MgPviUvRgoZYS43ys+e8nK5CrQMVssLyufCFhEMKc7QfEUoETN6UUK6jO5H6CbAv
nx9SvkKPl4Z0VpSeSne4278LPXhW4PfgDTFvEOwR/pHbYb0/3q5W57CkThK3SpSb
He/1GQPas11uPxAVwuWFRSFWOFkQKNdcK2ywHaSJjkNIkOCr

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

[Santiago Vila]

Hi. Beware also with the current debian/libdislocker0.7.links file,
it creates symlinks in usr/lib. I think (but I'm not sure), that
this file may be removed and dh will be smart enough to create
those symlinks automatically.

Thanks.

Bug#1026992: Preparing fix for CVE-2022-4728, CVE-2022-4729 & CVE-2022-4730

[Christoph Martin]

Hi all,

I am preparing a fix for this bug based on the upstream pull request 
https://github.com/graphite-project/graphite-web/pull/2785 which is also 
in oldstable security with version 1.1.4-3+deb10u2.


Regards
Christoph


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1030781: quilt: makes libxau FTBFS

[Dr. Tobias Quathamer]

Am 07.02.23 um 14:30 schrieb Helmut Grohne:

The quilt upload makes libxau FTBFS. I think it is the wrong time to
upload a breaking change like this. Thus filing against quilt.


Hi Helmut,

thanks for filing this bug. I didn't discover this side effect during my 
testing.


The cause of this FTBFS seems to be a changed error return code from 
quilt. If there are no patches in the series file, it now returns 1 
instead of 2. The program dh_quilt_unpatch relies on the previous error 
code, though, and fails.


Although it's probably a rather trivial code change in dh_quilt_unpatch, 
I agree with you that the timing is too close to the freeze.


I'll upload a new version of quilt which reverts upstream back to 0.66.

Regards,
Tobias



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1030530: Python 3.10 in bookworm

[Stefano Rivera]

Hi Joost (2023.02.07_11:31:23_+)
> Op Tue, Feb 07, 2023 at 05:52:21AM + schreef Danial Behzadi دانیال بهزادی:
> > Does it worth trying to package pyenv for Debian? Ain't it against any 
> > rules?
> 
> See "ITP pyenv" @ http://bugs.debian.org/978149 .

I think the Python development community would be very happy to see
this. Debian's selected Python releases don't meet all the needs of
Python developers, who typically want access to all supported Python 3
versions (and possibly the next alpha), at all times.

I'd be happy to review and sponsor uploads.

Stefano

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

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

[Santiago Vila]

Hi.

I said:


Instead of using "mv" after dh_install, I would probably
try to refactor this using debian/foo.install files,
which allow wilcards.

Those debian/*.install files would tell dh_install where
to put things, without having to move them ourselves in debian/rules.


I attach a proof of concept. Beware because it's completely untested,
but I believe you will get the idea. You will need to use debdiff
with the old packages to ensure that each package contains what
they should contain.

Thanks.diff --git a/debian/dislocker.install b/debian/dislocker.install
new file mode 100644
index 000..f7177e8
--- /dev/null
+++ b/debian/dislocker.install
@@ -0,0 +1,2 @@
+usr/bin
+usr/share
diff --git a/debian/libdislocker0.7.install b/debian/libdislocker0.7.install
new file mode 100644
index 000..32ef747
--- /dev/null
+++ b/debian/libdislocker0.7.install
@@ -0,0 +1 @@
+usr/lib*
diff --git a/debian/rules b/debian/rules
index fca4f28..5293977 100755
--- a/debian/rules
+++ b/debian/rules
@@ -13,10 +13,6 @@ export PVER=$(shell dpkg-parsechangelog --show-field version 
| cut -d"-" -f1)
 
 override_dh_install-arch:
dh_install
-   mv $(TEMPDEB)/usr/lib/libdislocker* \
-  $(DESTDIRLIB)/usr/lib/
-   mv $(TEMPDEB)/usr/bin $(DESTDIRBIN)/usr/
-   mv $(TEMPDEB)/usr/share $(DESTDIRBIN)/usr/
 
 override_dh_makeshlibs:
dh_makeshlibs -- -v$(PVER)

Bug#1030784: open-infrastructure-storage-tools: missing Breaks+Replaces: open-infrastructure-ceph-tools (<< 20190301-lts1-4)

[Andreas Beckmann]

Package: open-infrastructure-storage-tools
Version: 20190301-lts1-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to cleanly
upgrade from 'testing'.
Due to insufficiently versioned Breaks+Replaces it is possible to
install a mix of packages from before and after the package rename,
which can cause crippled packages after removal of some packages.

Currently there are

Replaces: open-infrastructure-ceph-tools
Breaks: open-infrastructure-ceph-tools (<< 20190301-lts1-3~)

but the Breaks does not catch all versions before the rename
and the unversioned Replaces is too wide, catching the transitional
package, too, which may have unwanted side effects ...
Please use the same version for both: (<< 20190301-lts1-4)


cheers,

Andreas

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

[Debian Bug Tracking System]

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

> severity 1024589 serious
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 'important'
> thanks
Stopping processing here.

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

Bug#1030777: marked as done (xorg-server: CVE-2023-0494)

[Debian Bug Tracking System]

Your message dated Tue, 07 Feb 2023 13:35:27 +
with message-id 
and subject line Bug#1030777: fixed in xorg-server 2:21.1.7-1
has caused the Debian Bug report #1030777,
regarding xorg-server: CVE-2023-0494
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.)


-- 
1030777: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030777
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xorg-server
Version: 2:21.1.6-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 2:1.20.11-1+deb11u4
Control: fixed -1 2:1.20.11-1+deb11u5

Hi,

The following vulnerability was published for xorg-server.

CVE-2023-0494[0]:
| Xi: fix potential use-after-free in DeepCopyPointerClasses

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-0494
https://www.cve.org/CVERecord?id=CVE-2023-0494
[1] 
https://gitlab.freedesktop.org/xorg/xserver/commit/0ba6d8c37071131a49790243cdac55392ecf71ec

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: xorg-server
Source-Version: 2:21.1.7-1
Done: Julien Cristau 

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

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

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

Debian distribution maintenance software
pp.
Julien Cristau  (supplier of updated xorg-server package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 07 Feb 2023 14:15:45 +0100
Source: xorg-server
Architecture: source
Version: 2:21.1.7-1
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Julien Cristau 
Closes: 1030777
Changes:
 xorg-server (2:21.1.7-1) unstable; urgency=medium
 .
   * New upstream release
 + Xi: fix potential use-after-free in DeepCopyPointerClasses
   (CVE-2023-0494, closes: #1030777)
Checksums-Sha1:
 d6c7fecdcca21d6554a6fb937ee5685b60396c92 4236 xorg-server_21.1.7-1.dsc
 64a134919cf467cc404ce45871376cd6abb6cc8c 8922821 xorg-server_21.1.7.orig.tar.gz
 2c653f19796de73f9cbaf466658803d47070ced8 195 xorg-server_21.1.7.orig.tar.gz.asc
 21a0948b390d603abe75888396a8d48fc16cf389 168149 xorg-server_21.1.7-1.diff.gz
Checksums-Sha256:
 df6c9c0f253fe2203454e8eae6b02464256fe99785527f1e80981660230edb6d 4236 
xorg-server_21.1.7-1.dsc
 1a9005f47c7ea83645a977581324439628a32c4426303e5a4b9c2d6615becfbf 8922821 
xorg-server_21.1.7.orig.tar.gz
 2f2113fe0866694084e952c7699a689d1fa0feefd1cc8492d79db432604246c4 195 
xorg-server_21.1.7.orig.tar.gz.asc
 ed25018f392feb25e2e1224b4939f86fb22e14c27e3970ec4cdb23fb1fa9e380 168149 
xorg-server_21.1.7-1.diff.gz
Files:
 35248e4cf6fe4860d754a2b31679932d 4236 x11 optional xorg-server_21.1.7-1.dsc
 9c9b0375cb17ad8b4a79f9dd9efc58d0 8922821 x11 optional 
xorg-server_21.1.7.orig.tar.gz
 3d6b4c2abedbcbd6cd7f071d74c56e5d 195 x11 optional 
xorg-server_21.1.7.orig.tar.gz.asc
 852848b3e48f01436b09611f5cfe8866 168149 x11 optional 
xorg-server_21.1.7-1.diff.gz

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEVXgdqzTmGgnvuIvhnbAjVVb4z60FAmPiTzIUHGpjcmlzdGF1
QGRlYmlhbi5vcmcACgkQnbAjVVb4z60lyRAAlLifsxvnfmavQhguxskkeDbCjOsc
AeONIrs47B4UOWjo4+u8g7bwWH6+F5sppmcHUdb2H7q1jRuErKqPV29rkBWsYmo7
GuSwnKs/73OZ/ghn6NSNGbZkun+hvtiKrNHmWwWw4C9P/W/6BA4OyGTzTl7E4Spm
Q5sRvvtBPUYwsZ7FP/KRYu1Dv7fVljrijNXNhmVz3X7mR1W7m0kZ1jd6gtM/Qw/P
+n79YAj2FbqQWLuI8vabwSV5d0qKHOITkh67K2yYiu9bFGMN6JiYE7Tca5p29yVB
EJTBpiRT3mRHIutB/u6QqadUQ+bVdcg81F2BxVKSwTQcVa21fxySgoVxjzTQ4AeR
9LzetrXK36RmleV9ZK/S1pW5hZp9t1siQlxNUVv8NDESj9FxenE97mv1B6B7TLHj
+BMNhUj8y0Z0PE7Bi1U16DHFvGx/7Q7IoQJCdQFLQj2V0U5ARbuI6zTB5sTtjgV2
3LOWvTHnoWV5NpA/E7URPTKL70oUHZn58WNM9ahBjOK86PFFlVqWC4aXt2YcXe53
nBf5O93tF7aNNuNqMpZf9IqGu+TFSXnx5rIfxvUSZgjucKx00H+Og8oFT+RNObkR
llPYHs1Pn8EUHC/JIO9+ySA6U5DAN3YXjggGdj39mR2cHC6dB0zC9NgenZ1Zb1r3
kr43wLeLiKkd7GU=
=2uvx
-END PGP SIGNATURE End Message ---

Bug#1030781: quilt: makes libxau FTBFS

[Helmut Grohne]

Package: quilt
Version: 0.67-1
Severity: serious
Control: affects -1 + src:libxau
Tags: ftbfs

The quilt upload makes libxau FTBFS. I think it is the wrong time to
upload a breaking change like this. Thus filing against quilt. Full
build log:

| Command: dpkg-buildpackage --sanitize-env -us -uc -b -rfakeroot
| dpkg-buildpackage: info: source package libxau
| dpkg-buildpackage: info: source version 1:1.0.9-1
| dpkg-buildpackage: info: source distribution unstable
| dpkg-buildpackage: info: source changed by Timo Aaltonen 
|  dpkg-source --before-build .
| dpkg-buildpackage: info: host architecture amd64
|  fakeroot debian/rules clean
| dh clean --with quilt --builddirectory=build/
|dh_auto_clean -O--builddirectory=build/
|dh_autoreconf_clean -O--builddirectory=build/
|dh_quilt_unpatch -O--builddirectory=build/
| No series file found
| dh_quilt_unpatch: error: quilt --quiltrc /dev/null pop -a || test $? = 2 
returned exit code 1
| make: *** [debian/rules:14: clean] Error 25
| dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned 
exit status 2

Helmut

Processed: quilt: makes libxau FTBFS

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:libxau
Bug #1030781 [quilt] quilt: makes libxau FTBFS
Added indication that 1030781 affects src:libxau

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