Bug#1027538: herisvm: FTBFS: dh_auto_build: error: exec (for cmd: mkcmake PREFIX=/usr MANDIR=/usr/share/man INFODIR=/usr/share/info SYSCONFDIR=/etc STRIPFLAG= LIBDIR=/usr/lib/x86_64-linux-gnu LIBEXECD

[Bo YU]

Source: herisvm
Version: 0.9.0-2
Followup-For: Bug #1027538

Hi Lucas,

I have rebuild the package on my local pc, but it works:

```
...
Build Architecture: amd64
Build Type: full
Build-Space: 584
Build-Time: 11
Distribution: unstable
Host Architecture: amd64
Install-Time: 23
Job: /home/vimer/build/rfs/nmu/37_herisvm/herisvm_0.9.0-2.dsc
Lintian: info
Machine Architecture: amd64
Package: herisvm
Package-Time: 102
Source-Version: 0.9.0-2
Space: 584
Status: successful
Version: 0.9.0-2

Finished at 2023-01-10T07:32:40Z
Build needed 00:01:42, 584k disk space

```

I am not sure how to deal with the bug in such situation. I can close it
but I think after your confirmation.

-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Processed: tagging 1027934

[Debian Bug Tracking System]

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

> # https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027934#14
> tags 1027934 + patch
Bug #1027934 [src:hugin] hugin: misses link_directories
Bug #1028198 [src:hugin] hugin: Blocks transition to python-3.11
Added tag(s) patch.
Added tag(s) patch.
> thanks
Stopping processing here.

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

Processed: severity of 1028370 is important

[Debian Bug Tracking System]

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

> severity 1028370 important
Bug #1028370 [clusterssh] Connection to server failed
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#1028370: Connection to server failed

[Stéphane Glondu]

Le 10/01/2023 à 07:56, Stéphane Glondu a écrit :

Today, cssh does not work:

$ cssh a b c d
Connection to server failed -- (version 11.0)
Authorization required, but no authorization protocol specified
  at /usr/share/perl5/App/ClusterSSH/Window/Tk.pm line 57.

I'm pretty sure it was working 3 weeks ago or so. However, with 4.16-3
I still get the issue.


More info: the error was with the default GNOME (on Wayland) session. 
With GNOME on Xorg, cssh works. I also tried, xterm itself works with 
Wayland session.



Cheers,

--
Stéphane

Bug#1027367: marked as done (golang-github-jinzhu-gorm: FTBFS in bullseye (missing build-depends on tzdata))

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2023 07:04:35 +
with message-id 
and subject line Bug#1027367: fixed in golang-github-jinzhu-gorm 1.9.6-2
has caused the Debian Bug report #1027367,
regarding golang-github-jinzhu-gorm: FTBFS in bullseye (missing build-depends 
on tzdata)
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.)


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

Package: src:golang-github-jinzhu-gorm
Version: 1.9.6-1
Severity: serious
Tags: ftbfs patch

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang
   dh_update_autotools_config -i -O--buildsystem=golang
   dh_autoreconf -i -O--buildsystem=golang
   dh_auto_configure -i -O--buildsystem=golang
   dh_auto_build -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install -trimpath -v -p 2 
github.com/jinzhu/gorm github.com/jinzhu/gorm/dialects/mssql 
github.com/jinzhu/gorm/dialects/mysql github.com/jinzhu/gorm/dialects/postgres 
github.com/jinzhu/gorm/dialects/sqlite
internal/unsafeheader
internal/cpu
runtime/internal/atomic
runtime/internal/sys
internal/bytealg
runtime/internal/math
internal/race
sync/atomic
unicode
runtime
unicode/utf8
math/bits
math
internal/testlog
encoding
unicode/utf16
crypto/internal/subtle
crypto/subtle
container/list
vendor/golang.org/x/crypto/cryptobyte/asn1
internal/nettrace
runtime/cgo
vendor/golang.org/x/crypto/internal/subtle
github.com/lib/pq/oid
sync
internal/reflectlite
math/rand
internal/singleflight
errors
sort
io
internal/oserror
syscall
bytes
hash
strconv
crypto
reflect
time
context
internal/syscall/unix
internal/poll
internal/syscall/execenv
os
encoding/binary
crypto/sha1
internal/fmtsort
fmt
encoding/base64
strings
regexp/syntax
database/sql/driver
database/sql
encoding/json
regexp
github.com/jinzhu/inflection
go/token
path/filepath
log
go/scanner
crypto/cipher
go/ast
crypto/des
crypto/md5
bufio
github.com/jinzhu/gorm
crypto/aes
math/big
crypto/rand
crypto/elliptic
crypto/internal/randutil
crypto/sha512
encoding/asn1
crypto/ed25519/internal/edwards25519
vendor/golang.org/x/crypto/cryptobyte
crypto/ed25519
crypto/hmac
crypto/rc4
crypto/ecdsa
crypto/rsa
crypto/sha256
crypto/dsa
encoding/hex
encoding/pem
crypto/x509/pkix
io/ioutil
vendor/golang.org/x/net/dns/dnsmessage
net/url
vendor/golang.org/x/crypto/chacha20
vendor/golang.org/x/crypto/poly1305
net
vendor/golang.org/x/sys/cpu
vendor/golang.org/x/crypto/chacha20poly1305
vendor/golang.org/x/crypto/curve25519
vendor/golang.org/x/crypto/hkdf
golang.org/x/crypto/md4
golang.org/x/net/context
github.com/lib/pq/scram
os/user
path
github.com/lib/pq/hstore
github.com/mattn/go-sqlite3
crypto/x509
crypto/tls
github.com/denisenkom/go-mssqldb
github.com/go-sql-driver/mysql
github.com/jinzhu/gorm/dialects/mysql
github.com/lib/pq
github.com/jinzhu/gorm/dialects/mssql
github.com/jinzhu/gorm/dialects/sqlite
github.com/jinzhu/gorm/dialects/postgres
   dh_auto_test -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go test -vet=off -v -p 2 
github.com/jinzhu/gorm github.com/jinzhu/gorm/dialects/mssql 
github.com/jinzhu/gorm/dialects/mysql github.com/jinzhu/gorm/dialects/postgres 
github.com/jinzhu/gorm/dialects/sqlite
testing sqlite3...


(/<>/obj-x86_64-linux-gnu/src/github.com/jinzhu/gorm/migration_test.go:292)
[2022-11-30 15:52:24]  no such table: animals 


(/<>/obj-x86_64-linux-gnu/src/github.com/jinzhu/gorm/migration_test.go:292)
[2022-11-30 15:52:24]  no such table: user_languages 


(/<>/obj-x86_64-linux-gnu/src/github.com/jinzhu/gorm/migration_test.go:297)
[2022-11-30 15:52:24]  no such table: shorts 


(/<>/obj-x86_64-linux-gnu/src/github.com/jinzhu/gorm/migration_test.go:297)
[2022-11-30 15:52:24]  no such table: 
really_long_thing_that_references_shorts 


(/<>/obj-x86_64-linux-gnu/src/github.com/jinzhu/gorm/migration_test.go:297)
[2022-11-30 15:52:24]  no such table: 
really_long_table_name_to_test_my_sql_name_length_limits 


(/<>/obj-x86_64-linux-gnu/src/github.com/jinzhu/gorm/migration_test.go:297)
[2022-11-30 15:52:24]  no such table: not_so_long_table_names 



(/<>/obj-x86_64-linux-gnu/src/github.com/jinzhu/gorm/migration_test.go:297)
[2022-11-30 15:52:24] 

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

[Gianfranco Costamagna]

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)

G.


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1028370: Connection to server failed

[Stéphane Glondu]

Package: clusterssh
Version: 4.16-4
Severity: grave

Dear Maintainer,

Today, cssh does not work:

$ cssh a b c d
Connection to server failed -- (version 11.0)
Authorization required, but no authorization protocol specified
 at /usr/share/perl5/App/ClusterSSH/Window/Tk.pm line 57.

I'm pretty sure it was working 3 weeks ago or so. However, with 4.16-3
I still get the issue.


Cheers,

-- 
Stéphane


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

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

Versions of packages clusterssh depends on:
ii  libexception-class-perl 1.45-1
ii  libtry-tiny-perl0.31-2
ii  libx11-protocol-other-perl  31-1
ii  libx11-protocol-perl0.56-9
ii  openssh-client  1:9.1p1-1
ii  perl5.36.0-6
ii  perl-tk 1:804.036-1+b1
ii  xterm   377-1

clusterssh recommends no packages.

clusterssh suggests no packages.

-- no debconf information

Bug#1027363: marked as done (golang-github-araddon-dateparse: FTBFS in bullseye (missing build-depends on tzdata))

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2023 06:38:27 +
with message-id 
and subject line Bug#1027363: fixed in golang-github-araddon-dateparse 
0.0~git20210429.6b43995-3
has caused the Debian Bug report #1027363,
regarding golang-github-araddon-dateparse: FTBFS in bullseye (missing 
build-depends on tzdata)
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.)


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

Package: src:golang-github-araddon-dateparse
Version: 0.0~git20210207.0eec95c-1
Severity: serious
Tags: ftbfs patch

Dear maintainer:

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


[...]
 debian/rules binary-indep
dh binary-indep --builddirectory=_build --buildsystem=golang --with=golang
   dh_update_autotools_config -i -O--builddirectory=_build 
-O--buildsystem=golang
   dh_autoreconf -i -O--builddirectory=_build -O--buildsystem=golang
   dh_auto_configure -i -O--builddirectory=_build -O--buildsystem=golang
   dh_auto_build -i -O--builddirectory=_build -O--buildsystem=golang
cd _build && go install -trimpath -v -p 2 github.com/araddon/dateparse
internal/unsafeheader
internal/cpu
runtime/internal/atomic
runtime/internal/sys
runtime/internal/math
internal/bytealg
math/bits
math
runtime
unicode/utf8
internal/race
sync/atomic
unicode
internal/testlog
internal/reflectlite
sync
errors
sort
strconv
io
internal/oserror
syscall
reflect
internal/syscall/unix
time
internal/poll
internal/fmtsort
internal/syscall/execenv
strings
os
fmt
github.com/araddon/dateparse
   dh_auto_test -i -O--builddirectory=_build -O--buildsystem=golang
cd _build && go test -vet=off -v -p 2 github.com/araddon/dateparse
=== RUN   TestOne
--- PASS: TestOne (0.00s)
=== RUN   TestParse
parseany_test.go:441: Expected to load location "America/Los_Angeles" but 
got unknown time zone America/Los_Angeles
--- FAIL: TestParse (0.00s)
=== RUN   TestPStruct
parseany_test.go:489:
Error Trace:parseany_test.go:489
Error:  Not equal:
expected: ()
actual  : 
*errors.errorString({s:"unknown time zone America/Denver"})
Test:   TestPStruct
--- FAIL: TestPStruct (0.00s)
=== RUN   TestParseErrors
--- PASS: TestParseErrors (0.00s)
=== RUN   TestParseLayout
--- PASS: TestParseLayout (0.00s)
=== RUN   TestParseStrict
--- PASS: TestParseStrict (0.00s)
=== RUN   TestInLocation
parseany_test.go:619:
Error Trace:parseany_test.go:619
Error:  Not equal:
expected: ()
actual  : 
*errors.errorString({s:"unknown time zone America/Denver"})
Test:   TestInLocation
parseany_test.go:649:
Error Trace:parseany_test.go:649
Error:  Not equal:
expected: -25200
actual  : 0
Test:   TestInLocation
Messages:   Should have found offset = -25200 0  UTC
parseany_test.go:650:
Error Trace:parseany_test.go:650
Error:  Not equal:
expected: "MST"
actual  : "UTC"

Diff:
--- Expected
+++ Actual
@@ -1 +1 @@
-MST
+UTC
Test:   TestInLocation
Messages:   Should have found zone = MST UTC
parseany_test.go:651:
Error Trace:parseany_test.go:651
Error:  Not equal:
expected: "2013-02-01 07:00:00 + UTC"
actual  : "2013-02-01 00:00:00 + UTC"

Diff:
--- Expected
+++ Actual
@@ -1 +1 @@
-2013-02-01 07:00:00 + UTC
+2013-02-01 00:00:00 + UTC
Test:   TestInLocation
parseany_test.go:656:
Error Trace:parseany_test.go:656
 

Bug#1027971: marked as done (virtualbox : Depends: python3 (< 3.11) but 3.11.1-1 is installed)

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2023 07:11:25 +0100
with message-id <26701277-5f05-8f4b-f363-c79bb49f1...@debian.org>
and subject line Re: virtualbox : Depends: python3 (< 3.11) but 3.11.1-1 is 
installed
has caused the Debian Bug report #1027971,
regarding virtualbox : Depends: python3 (< 3.11) but 3.11.1-1 is installed
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.)


-- 
1027971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027971
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: virtualbox
Version: 7.0.4-dfsg-5
Severity: grave
Justification: renders package unusable

Dear Maintainer,

trying to install virtualbox on sid, but its dependencies are wrong.
python3 (<< 3.11), python3 (>= 3.10~), python3.10

Please upgrade to 3.11.1-1.

TIA,
Michael


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

Kernel: Linux 6.0.0-6-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages virtualbox depends on:
ii  python3   3.11.1-1
ii  python3.103.10.9-1
--- End Message ---
--- Begin Message ---

On Thu, 05 Jan 2023 12:41:43 +0100 Michael Tatge  wrote:

Package: virtualbox
Version: 7.0.4-dfsg-5
Severity: grave
Justification: renders package unusable

Dear Maintainer,

trying to install virtualbox on sid, but its dependencies are wrong.
python3 (<< 3.11), python3 (>= 3.10~), python3.10

Please upgrade to 3.11.1-1.

TIA,
Michael


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

Kernel: Linux 6.0.0-6-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages virtualbox depends on:
ii  python3   3.11.1-1
ii  python3.103.10.9-1




this is handled by Release Team, not maintainer, and its already done.

G.


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---

Processed: Re: Bug#1027476 closed by Debian FTP Masters (reply to Georges Khaznadar ) (Bug#1027476: fixed in cron 3.0pl1-155)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1027476 {Done: Georges Khaznadar } [cron] cron: 
postrm script fails because expected dpkg-statoverride is not present
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions cron/3.0pl1-155.

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

Bug#1027476: closed by Debian FTP Masters (reply to Georges Khaznadar ) (Bug#1027476: fixed in cron 3.0pl1-155)

[Guillem Jover]

Control: reopen -1

Hi!

Although I've not tested nor checked the affected code, the fix done
to close this cannot possibly be correct, see below. :)

On Mon, 2023-01-09 at 21:27:06 +, Debian Bug Tracking System wrote:
> Date: Sun, 01 Jan 2023 07:12:58 -0500
> From: "Kevin P. Fleming" 
> To: Debian Bug Tracking System 
> Subject: cron: postrm script fails because expected dpkg-statoverride is
>  not present

> The postrm script in the current version of the cron package assumes the
> presence of a dpkg-statoverride for /usr/bin/crontab, but no such statoverride
> is present on my systems. As a result when I try to 'purge' the cron package
> the process fails.

I think the description might be read incorrectly. The error is not
that the dpkg-statoverride program is missing, as that's not possible
(w/o force) being part of dpkg which is an Essential package. But that
a statoverride entry setup by some package is missing.

> This results in the following output:
> 
> Reading package lists... Done
> Building dependency tree... Done
> The following packages will be REMOVED:
>   cron*
> 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
> After this operation, 0 B of additional disk space will be used.
> Do you want to continue? [Y/n] y
> perl: warning: Setting locale failed.
> perl: warning: Please check that your locale settings:
> LANGUAGE = (unset),
> LC_ALL = (unset),
> LANG = "en_US.UTF-8"
> are supported and installed on your system.
> perl: warning: Falling back to the standard locale ("C").
> E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such 
> device)
> (Reading database ... 11054 files and directories currently installed.)
> Purging configuration files for cron (3.0pl1-154) ...
> dpkg-statoverride: warning: no override present

As can be seen here, the tool is executed and it runs, but it warns that
it cannot find the statoverride entry.

> dpkg: error processing package cron (--purge):
>  installed cron package post-removal script subprocess returned error exit
> status 2
> Errors were encountered while processing:
>  cron
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> Editing /var/lib/dpkg/info/cron.postrm to remove the first section resolves 
> the
> issue.

Adding a dependency on dpkg cannot have solved anything here.

Thanks,
Guillem

Bug#1012496: marked as done (inkscape: FTBFS on arm64, ppc64el, s390x)

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2023 03:25:24 +
with message-id 
and subject line Bug#1012496: fixed in inkscape 1.2.2-2
has caused the Debian Bug report #1012496,
regarding inkscape: FTBFS on arm64, ppc64el, s390x
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.)


-- 
1012496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012496
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: inkscape
Version: 1.2-1
Severity: serious
Tags: ftbfs
Forwarded: https://gitlab.com/inkscape/inkscape/-/issues/3554

https://buildd.debian.org/status/fetch.php?pkg=inkscape=arm64=1.2-1=1653329867=0
https://buildd.debian.org/status/fetch.php?pkg=inkscape=ppc64el=1.2-1=1653326620=0
https://buildd.debian.org/status/fetch.php?pkg=inkscape=s390x=1.2-1=165123=0


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: inkscape
Source-Version: 1.2.2-2
Done: Mattia Rizzolo 

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated inkscape 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, 10 Jan 2023 02:09:18 +0100
Source: inkscape
Architecture: source
Version: 1.2.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Mattia Rizzolo 
Closes: 1012496
Changes:
 inkscape (1.2.2-2) unstable; urgency=medium
 .
   * Add several patches skipping several tests that fail across varying
 architectures.  Closes: #1012496
   * Add a patch skipping the tests regarding librevenge formats, that suddenly
 started failing as well, to be investigated.
Checksums-Sha1:
 03e2322d88de29155708fa90618b0c4ab17e6be4 3056 inkscape_1.2.2-2.dsc
 ae7ea7cf2f5548fdf21892c79b37edecab3eb106 34208 inkscape_1.2.2-2.debian.tar.xz
 74c07a931c56ad320898782f254abb0c91cf28a7 7413 inkscape_1.2.2-2_source.buildinfo
Checksums-Sha256:
 01454a32ff974d6f8202dcce649aaa2c226ec43360ee17356a584983a9fc6772 3056 
inkscape_1.2.2-2.dsc
 3c1eeb50733a3555dc947b0f36808a6afd9a9c50b8419fdcbd36c6fe19642722 34208 
inkscape_1.2.2-2.debian.tar.xz
 88980c80237c7c8699f2055f2ab08da9dc11b21e4d5f05f3aed03f4c4a156761 7413 
inkscape_1.2.2-2_source.buildinfo
Files:
 6ae7827971e2b31b141ef241f5f59809 3056 graphics optional inkscape_1.2.2-2.dsc
 13bfacf2757c9bd7d36974e1f0b56100 34208 graphics optional 
inkscape_1.2.2-2.debian.tar.xz
 b4568bdb1b2d79905d9a62c5a0433ce6 7413 graphics optional 
inkscape_1.2.2-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAmO8vZcACgkQCBa54Yx2
K63lVhAAtmLKGzRa0tPcDPHclikM8YYDMdS0cmuyurKXY8Z4D2tzit0FL21R5p+h
4crwGuJzAz+V79OjnjB4cuoq5i2K8g1iHS6A+W3HY8vXgEWpFPUrW9kvCbUp8Cts
ChKAR5noE4X0peNnuve3AZeT1JaXNmUIDUurE20Uu0Y1gfiC57mhgwKKQZvspk6n
8ktTA7PevMkayS9meXWJpI+Htxo+fnkbWG5qPIC0sA2nMJfQWwqiw3RRqI5Z5YsZ
MAviQjnYnimAyAd8br4LyThZQxpL/s6nBYMbqL90ZEsjX9h1/ox+IilZqsdLoE8K
E8Pt3VZDoftQUjJa7AIdv2QUoTAfnoSJfJIli9fTw8D+2xt7kcRGw5t/Wywkk0r4
VVAGqN2HKm9vtu321E7js6yEgLNDV/ktYNrn8vxYZq2WaCMRzihTUDqsFMkq3pao
k8cQj5CVFGailBrpaWHpv2vVK7l/JEAPyM4XzEACE/R8IpWt03XtYcnYdVSP3zl/
vHhU9joltyNt2739uwSd/Y2IqZxOzWxXYWrNvO5GOtDvCdzUm5ghHI0VEwR+ysVr
V13qO4GCzRS8uT+tWG54aTLIGvOHEuLvbtFksp7H5fgkOXVHCEApC8oCrG+VgtAe
pHKHiXvMS0ArZd46qSduoCMxvcmcWb3WwRP4au2xu9UQi/a2MCo=
=RMdE
-END PGP SIGNATURE End Message ---

Bug#922396: QA

[William Desportes]

Hi all,

I found this package during my QA analysis.

Based on the discussion and some QA elements I think a FTP RM could be useful 
for this package unless someone intends to upload a new version some day.

Does someone think we should keep this package?

The fact that there is updates upstream makes me think it could be worth 
keeping it.

--
William Desportes

Processed: tagging 1028240

[Debian Bug Tracking System]

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

> tags 1028240 + pending
Bug #1028240 [src:poetry] poetry: FTBFS (requires internet access)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1021079: disable the ppc64el binary for now?

[Adam Borowski]

Hi!
As the window for new packages to [re-]enter bookworm will close soon,
and fixing vectorscan on ppc doesn't appear to be coming, what about
disabling that arch for now?

It is described as "in development", thus it's not surprising it's
not working yet.  It'd be shame for the package to miss bookworm.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ Quis trollabit ipsos trollos?
⠈⠳⣄

Bug#1028171: marked as done (freecad FTBFS with Python 3.11 as default version)

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2023 00:08:28 +
with message-id 
and subject line Bug#1028171: fixed in freecad 0.20.2+dfsg1-1
has caused the Debian Bug report #1028171,
regarding freecad FTBFS with Python 3.11 as default version
to be marked as done.

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

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


-- 
1028171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028171
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freecad
Version: 0.20.1+dfsg1-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=freecad=amd64=0.20.1%2Bdfsg1-2%2Bb2=1673131196=0

...
/<>/src/Base/ConsoleObserver.cpp: In member function 
‘std::stringstream& Base::LogLevel::prefix(std::stringstream&, const char*, 
int)’:
/<>/src/Base/ConsoleObserver.cpp:269:41: error: invalid use of 
incomplete type ‘PyFrameObject’ {aka ‘struct _frame’}
  269 | src = PyUnicode_AsUTF8(frame->f_code->co_filename);
  | ^~
In file included from /usr/include/python3.11/Python.h:42,
 from /<>/src/Base/ConsoleObserver.cpp:31:
/usr/include/python3.11/pytypedefs.h:22:16: note: forward declaration of 
‘PyFrameObject’ {aka ‘struct _frame’}
   22 | typedef struct _frame PyFrameObject;
  |^~
make[4]: *** [src/Base/CMakeFiles/FreeCADBase.dir/build.make:388: 
src/Base/CMakeFiles/FreeCADBase.dir/ConsoleObserver.cpp.o] Error 1
--- End Message ---
--- Begin Message ---
Source: freecad
Source-Version: 0.20.2+dfsg1-1
Done: Kurt Kremitzki 

We believe that the bug you reported is fixed in the latest version of
freecad, 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.
Kurt Kremitzki  (supplier of updated freecad 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, 09 Jan 2023 17:00:02 -0600
Source: freecad
Architecture: source
Version: 0.20.2+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Kurt Kremitzki 
Closes: 993089 1028171
Changes:
 freecad (0.20.2+dfsg1-1) unstable; urgency=medium
 .
   [ Tobias Frost ]
   * [7556687] Add several supported MIME types to the .desktop file.
 (Closes: #993089)
 .
   [ Kurt Kremitzki ]
   * [69cb156] Switch from Qt WebKit to WebEngine
   * [bdc52cd] New upstream version 0.20.2+dfsg1 (Closes: #1028171)
   * [1e3598e] Refresh patches
Checksums-Sha1:
 0bc0f7180f4750c4fe19c070dce64f1f3d331174 3352 freecad_0.20.2+dfsg1-1.dsc
 4fe4fdd072dedd2cd77097b46baca97cc244c241 38576460 
freecad_0.20.2+dfsg1.orig.tar.xz
 e6d5ddbb95c4b015cac58cd84046eafb3f80f330 30696 
freecad_0.20.2+dfsg1-1.debian.tar.xz
 f941919d2ef15b0b393f1813a2bd4f603d25b480 29038 
freecad_0.20.2+dfsg1-1_source.buildinfo
Checksums-Sha256:
 3867d881bf2218d1a352290bdbeb5cacede2ba0486106d796df1ba356873d72f 3352 
freecad_0.20.2+dfsg1-1.dsc
 fde91f3ab109925743d0ef060d1f078a30ad9adcdc3b53a9a283a2f4f861a739 38576460 
freecad_0.20.2+dfsg1.orig.tar.xz
 f7a0d012a3733cb6581daa1ec5d40ecff6936d90d3d249c7a447149cc9427905 30696 
freecad_0.20.2+dfsg1-1.debian.tar.xz
 5f126623f8a1ee26bc16768aee0cd947ec93699b3f9aff239ddf46ac5411dd95 29038 
freecad_0.20.2+dfsg1-1_source.buildinfo
Files:
 bf6c9510fbf5aa31d6d01b8328b2c844 3352 science optional 
freecad_0.20.2+dfsg1-1.dsc
 4e4548289787cc46adff37278e49f1b6 38576460 science optional 
freecad_0.20.2+dfsg1.orig.tar.xz
 278a473ce67544bb690d7183a800ea9f 30696 science optional 
freecad_0.20.2+dfsg1-1.debian.tar.xz
 a7014d8d16f70b4f75993e6cf2686877 29038 science optional 
freecad_0.20.2+dfsg1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJKBAEBCgA0FiEEh8RU7HmiYTD5HEfrKUghB0bfc8AFAmO8ovMWHGtrcmVtaXR6
a2lAZGViaWFuLm9yZwAKCRApSCEHRt9zwDGiD/4vfF1dE8uO9W4RKnupcs0cUuKJ
zBpfXcyTZgWEhXI6KZpL5TUJrAyFmlHqZoWFRapMvEMkMoCeXNLwOz/qgszHQz/n
zeF+WYGp9tByqz0TpkeMoyk1G3F8m8F0Yaf2AOK/40V2GO8eu32gEkNwY4EyfNE1
Z56TB81rj7akeRLdSO24oAnCacDCONkZ2rnrjT8BVRryIyeEaOWi8vNimzfqRuqS
K1b9PDmzDw68WVcnGzZ3lrttK4fIOj1ZwNqQbumEDSgODDYo1981SbojG6MxIKqQ
bxr7t9TMB7ErDTQ91v2ezTu9CaNlm3ZL2sIqLb91Eby//uqk6zSj5Tnptymqkwx9

Bug#1027506: Status of mozillavpn in Debian

[Richard B. Kreckel]

On 1/9/23 23:26, Sylvestre Ledru wrote:

Le 08/01/2023 à 00:46, Richard B. Kreckel a écrit :


2) Based on mozillavpn_2.9.0-1.debian.tar.xz, apply some changes to 
debian/ directory:
   a) -DBUILD_TESTING=OFF to dh_auto_configure argument in 
debian/rules (without it it FTBFS trying to run some tests and that is 
also in upstream's rules file)
   d) change rm -rf debian/mozillavpn/etc/opt/chrome to rm -rf 
debian/mozillavpn/etc/opt in debian/rules so purge won't remove 
/etc/opt/ since there's nothing in there anyway
   c) Add packages python3-click and python3-jinja2 to Build-Depnds in 
debian/control (without these, it FTBFS)
   d) remove libqt6* and qt6-qpa-plugins dependencies in 
debian/control (see #1026957).



I tried with these changes but I am getting:


/<>/src/connectionbenchmark/benchmarktaskdownload.cpp:50:4: 
error: #error Check if QT added support for QDnsLookup::lookup() on Android
    50 | #  error Check if QT added support for QDnsLookup::lookup() on 
Android

   |    ^
[ 56%] Building CXX object 
src/CMakeFiles/mozillavpn.dir/connectionbenchmark/benchmarktaskping.cpp.o


rings a bell?


Sure.

Mozillavpn 2.9.0 #errors out there if QT_VERSION >= 0x060400.

The current qt6-base-dev in the archive is 6.4.2+dfsg~rc1-3 and that 
#defines QT_VERSION 060402. Hence, #error...


You must have been compiling Mozillavpn version 2.9.0, and not 2.12.0, 
as I recommended! (It was Andrea Marchesini who changed this upstream 
2022-10-06.)


All my best,
  -richard.
--
Richard B. Kreckel




OpenPGP_signature
Description: OpenPGP digital signature

Bug#1023965: marked as done (pandas FTBFS with Python 3.11 as supported version)

[Debian Bug Tracking System]

Your message dated Mon, 09 Jan 2023 23:21:54 +
with message-id 
and subject line Bug#1023965: fixed in pandas 1.5.2+dfsg-4
has caused the Debian Bug report #1023965,
regarding pandas FTBFS with Python 3.11 as supported version
to be marked as done.

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

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


-- 
1023965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023965
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pandas
Version: 1.3.5+dfsg-5
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=pandas=1.3.5%2Bdfsg-5%2Bb2

...
=== FAILURES ===
_ TestCategoricalAPI.test_set_ordered __

self = 

def test_set_ordered(self):

cat = Categorical(["a", "b", "c", "a"], ordered=True)
cat2 = cat.as_unordered()
assert not cat2.ordered
cat2 = cat.as_ordered()
assert cat2.ordered
cat2.as_unordered(inplace=True)
assert not cat2.ordered
cat2.as_ordered(inplace=True)
assert cat2.ordered

assert cat2.set_ordered(True).ordered
assert not cat2.set_ordered(False).ordered
cat2.set_ordered(True, inplace=True)
assert cat2.ordered
cat2.set_ordered(False, inplace=True)
assert not cat2.ordered

# removed in 0.19.0
msg = "can't set attribute"
with pytest.raises(AttributeError, match=msg):
>   cat.ordered = True
E   AttributeError: property 'ordered' of 'Categorical' object has no 
setter

pandas/tests/arrays/categorical/test_api.py:59: AttributeError

During handling of the above exception, another exception occurred:

self = 

def test_set_ordered(self):

cat = Categorical(["a", "b", "c", "a"], ordered=True)
cat2 = cat.as_unordered()
assert not cat2.ordered
cat2 = cat.as_ordered()
assert cat2.ordered
cat2.as_unordered(inplace=True)
assert not cat2.ordered
cat2.as_ordered(inplace=True)
assert cat2.ordered

assert cat2.set_ordered(True).ordered
assert not cat2.set_ordered(False).ordered
cat2.set_ordered(True, inplace=True)
assert cat2.ordered
cat2.set_ordered(False, inplace=True)
assert not cat2.ordered

# removed in 0.19.0
msg = "can't set attribute"
>   with pytest.raises(AttributeError, match=msg):
E   AssertionError: Regex pattern "can't set attribute" does not match 
"property 'ordered' of 'Categorical' object has no setter".

pandas/tests/arrays/categorical/test_api.py:58: AssertionError
 TestPrivateCategoricalAPI.test_codes_immutable 

self = 

def test_codes_immutable(self):

# Codes should be read only
c = Categorical(["a", "b", "c", "a", np.nan])
exp = np.array([0, 1, 2, 0, -1], dtype="int8")
tm.assert_numpy_array_equal(c.codes, exp)

# Assignments to codes should raise
with pytest.raises(AttributeError, match="can't set attribute"):
>   c.codes = np.array([0, 1, 2, 0, 1], dtype="int8")
E   AttributeError: property 'codes' of 'Categorical' object has no 
setter

pandas/tests/arrays/categorical/test_api.py:512: AttributeError

During handling of the above exception, another exception occurred:

self = 

def test_codes_immutable(self):

# Codes should be read only
c = Categorical(["a", "b", "c", "a", np.nan])
exp = np.array([0, 1, 2, 0, -1], dtype="int8")
tm.assert_numpy_array_equal(c.codes, exp)

# Assignments to codes should raise
>   with pytest.raises(AttributeError, match="can't set attribute"):
E   AssertionError: Regex pattern "can't set attribute" does not match 
"property 'codes' of 'Categorical' object has no setter".

pandas/tests/arrays/categorical/test_api.py:511: AssertionError
- generated xml file: 
/<>/.pybuild/cpython3_3.11/build/test-data.xml -
= slowest 30 durations =
0.38s teardown 
.pybuild/cpython3_3.11/build/pandas/tests/arrays/timedeltas/test_reductions.py::TestReductions::test_mean_2d
0.21s call 
.pybuild/cpython3_3.11/build/pandas/tests/arrays/interval/test_interval.py::TestAttributes::test_is_empty[both-IntervalIndex-left2-right2]
0.15s call 
.pybuild/cpython3_3.11/build/pandas/tests/arrays/test_datetimelike.py::TestDatetimeArray::test_int_properties[pytz.FixedOffset(300)-Y-day_of_week]
0.10s teardown 

Processed: tagging 1027206

[Debian Bug Tracking System]

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

> tags 1027206 + ftbfs
Bug #1027206 [src:qiskit-aer] qiskit-aer: autopkgtest fail with numpy/1.24.1
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1028356: procmail: Variable set with stdin pipe action fails leaving empty variable

[Debian Bug Tracking System]

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

> forwarded 1028356 https://github.com/BuGlessRB/procmail/issues/5
Bug #1028356 [procmail] procmail: Variable set with stdin pipe action fails 
leaving empty variable
Set Bug forwarded-to-address to 
'https://github.com/BuGlessRB/procmail/issues/5'.
> tags 1028356 + help
Bug #1028356 [procmail] procmail: Variable set with stdin pipe action fails 
leaving empty variable
Added tag(s) help.
> thanks
Stopping processing here.

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

Bug#1028356: procmail: Variable set with stdin pipe action fails leaving empty variable

[Santiago Vila]

forwarded 1028356 https://github.com/BuGlessRB/procmail/issues/5
tags 1028356 + help
thanks

Hi. I've forwarded the bug by making a github issue from it.

There is a full git history for procmail at github. If you
feel brave enough you could try a git-bisect on the code
to see where this bug was introduced (right now I have no idea
where it could come from).

Thanks.

Processed: fix email address

[Debian Bug Tracking System]

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

> submitter 1028356 !
Bug #1028356 [procmail] procmail: Variable set with stdin pipe action fails 
leaving empty variable
Changed Bug submitter to 'Bob Proulx ' from 'Bob Proulx 
'.
> thanks
Stopping processing here.

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

Bug#1028297: marked as done (python3-freezegun: ships a copy of python3-arrow: /usr/lib/python3/dist-packages/arrow/*.py)

[Debian Bug Tracking System]

Your message dated Mon, 09 Jan 2023 22:49:39 +
with message-id 
and subject line Bug#1028297: fixed in freezegun 1.2.1+actually1.2.1-1
has caused the Debian Bug report #1028297,
regarding python3-freezegun: ships a copy of python3-arrow: 
/usr/lib/python3/dist-packages/arrow/*.py
to be marked as done.

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

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


-- 
1028297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028297
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-freezegun
Version: 1.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.

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

  Preparing to unpack .../python3-freezegun_1.2.1-1_all.deb ...
  Unpacking python3-freezegun (1.2.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-freezegun_1.2.1-1_all.deb (--unpack):
   trying to overwrite '/usr/lib/python3/dist-packages/arrow/__init__.py', 
which is also in package python3-arrow 1.2.3-1
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-freezegun_1.2.1-1_all.deb
 

cheers,

Andreas


python3-arrow=1.2.3-1_python3-freezegun=1.2.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: freezegun
Source-Version: 1.2.1+actually1.2.1-1
Done: Federico Ceratto 

We believe that the bug you reported is fixed in the latest version of
freezegun, 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.
Federico Ceratto  (supplier of updated freezegun 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, 09 Jan 2023 22:25:47 +
Source: freezegun
Architecture: source
Version: 1.2.1+actually1.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Federico Ceratto 
Changed-By: Federico Ceratto 
Closes: 1018361 1028297
Changes:
 freezegun (1.2.1+actually1.2.1-1) unstable; urgency=medium
 .
   * New upstream release
   * Cleanup incorrect import (Closes: #1028297)
   * Drop nose dependency (Closes: #1018361)
Checksums-Sha1:
 163524288ecd6e9335973183d763194b6d160e7a 2153 
freezegun_1.2.1+actually1.2.1-1.dsc
 3c74a6ac120bd7d27be661bcbae5b5c848a4ef1c 26901 
freezegun_1.2.1+actually1.2.1.orig.tar.gz
 62448c4ad3416ae3b1cbaf016f0fd6e324f204e3 2728 
freezegun_1.2.1+actually1.2.1-1.debian.tar.xz
 74c336c6e13cb9ee8f90878bbd1f88cf9389bd16 7423 
freezegun_1.2.1+actually1.2.1-1_amd64.buildinfo
Checksums-Sha256:
 9eb7e868c904690f38cf8d2f4c92bbb74362f8f6f4683dd0b80efdb140a79cb6 2153 
freezegun_1.2.1+actually1.2.1-1.dsc
 d37b784685f7b3bdbb5f5ac3473102532ef4ab5c685178905ffe4fe5186fc7b0 26901 
freezegun_1.2.1+actually1.2.1.orig.tar.gz
 cc372ce3ce58d6ab1f4f9c3629f24e883fc9394e04b07adef198357ec708f143 2728 
freezegun_1.2.1+actually1.2.1-1.debian.tar.xz
 8ec22d8b48ef60c590fe74637c73bd834729d7fff206c61ca84cf4f7585fa966 7423 
freezegun_1.2.1+actually1.2.1-1_amd64.buildinfo
Files:
 21355081f08f07840d1e13c06bc5c019 2153 python optional 
freezegun_1.2.1+actually1.2.1-1.dsc
 173b6d68374dfedd8426d7cdee388fb4 26901 python optional 
freezegun_1.2.1+actually1.2.1.orig.tar.gz
 49365b70ab3a4afeb10941e88bd6053e 2728 python optional 
freezegun_1.2.1+actually1.2.1-1.debian.tar.xz
 a0d49c62379ad4a77597d9b3a947c80e 7423 python optional 
freezegun_1.2.1+actually1.2.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfKfd+zM5IUCMbyuWbzG8RPUXfaoFAmO8laAACgkQbzG8RPUX
farnYA/9Hb9omNb5uOYzjU9izgrUGcmk3FW/9dcJXPPbj9xHTHw7Nj4QvXfVnB0l
V7hJMfuZbtYu80YRS901SCeuV02evdTwHrL4itdtyiI0U9vesCkC7ph6U4UlqO1v
zL2iPzieaOEvtQMG2hg+iaTjySpb5m9gxpqoFaEZr1foqdJluCpTvcnwzSJzHXgx
+C22OcSXMjIHn9ifFXTbDcbR6LajtxJ9ulQ8A6YaRQDr+yyPKUB1Ym8j/jUrQpAb
nkoDDFMyURQtBlSlhibM8jw1+8kB6MmGp9RNiC0oK/qy14uoFVLr/84VU0j0U8fA
iQTdpZCDCRk/e2Tq6sw9vgMQjC3pzwAD8gHmqRBdRY5RPHq2SmUBC/ngdwRIZZqm
k+XBU1dJEKquvgpY4KrjmZJ0iGMGJbekKCH0kPGd2Uz04ZvF/3dh7E8rv0aQ3r80
5WT7wNfYRC1EuZnB4p0eFLmfjPor8k4jz0nXFma3kWnu8AdpVlNGppJP5g/5Sb9R
LxkxC0SkMF+se1rDXOub5ZenLlWs8kkvAsITFRE/nk249Z7guyWm3NKncvwMdkGE

Bug#1028356: procmail: Variable set with stdin pipe action fails leaving empty variable

[Santiago Vila]

El 9/1/23 a las 23:13, Bob Proulx escribió:

Unfortunately in 3.24 this functionality is broken.  I see in the
Testing migration "excuses" this "Too young, only 4 of 5 days old".
Should severity be "important" in order to keep Testing from breaking?


I've just set it to serious, which is the minimal severity to prevent
a migration to testing.

I don't want regressions of any kind for this package. If this is
not possible, we'll have to stick with old 3.22 for bookworm.

I'll forward this to upstream and see what happens.

Thanks a lot.

Processed: severity

[Debian Bug Tracking System]

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

> severity 1028356 serious
Bug #1028356 [procmail] procmail: Variable set with stdin pipe action fails 
leaving empty variable
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#1028359: pygpu: fails to import in numpy 1.24

[Rebecca N. Palmer]

Package: python3-pygpu
Version: 0.7.6-12
Severity: grave

numpy 1.24 no longer has np.bool, which makes pygpu fail to import:

pygpu/dtypes.py:74: in _fill_dtype_registry
register_dtype(np.bool, ["ga_bool", "bool"])
numpy/__init__.py:284: in __getattr__
raise AttributeError("module {!r} has no attribute "
E   AttributeError: module 'numpy' has no attribute 'bool'

Full log: https://salsa.debian.org/science-team/theano/-/jobs/3771271

Bug#1027506: Status of mozillavpn in Debian

[Sylvestre Ledru]

Le 08/01/2023 à 00:46, Richard B. Kreckel a écrit :


2) Based on mozillavpn_2.9.0-1.debian.tar.xz, apply some changes to 
debian/ directory:
   a) -DBUILD_TESTING=OFF to dh_auto_configure argument in 
debian/rules (without it it FTBFS trying to run some tests and that is 
also in upstream's rules file)
   d) change rm -rf debian/mozillavpn/etc/opt/chrome to rm -rf 
debian/mozillavpn/etc/opt in debian/rules so purge won't remove 
/etc/opt/ since there's nothing in there anyway
   c) Add packages python3-click and python3-jinja2 to Build-Depnds in 
debian/control (without these, it FTBFS)
   d) remove libqt6* and qt6-qpa-plugins dependencies in 
debian/control (see #1026957).



I tried with these changes but I am getting:


/<>/src/connectionbenchmark/benchmarktaskdownload.cpp:50:4: 
error: #error Check if QT added support for QDnsLookup::lookup() on Android
   50 | #  error Check if QT added support for QDnsLookup::lookup() on 
Android

  |    ^
[ 56%] Building CXX object 
src/CMakeFiles/mozillavpn.dir/connectionbenchmark/benchmarktaskping.cpp.o


rings a bell?

Thanks

S

Bug#1027506: Status of mozillavpn in Debian

[Sylvestre Ledru]

Le 08/01/2023 à 00:46, Richard B. Kreckel a écrit :


2) Based on mozillavpn_2.9.0-1.debian.tar.xz, apply some changes to 
debian/ directory:
   a) -DBUILD_TESTING=OFF to dh_auto_configure argument in 
debian/rules (without it it FTBFS trying to run some tests and that is 
also in upstream's rules file)
   d) change rm -rf debian/mozillavpn/etc/opt/chrome to rm -rf 
debian/mozillavpn/etc/opt in debian/rules so purge won't remove 
/etc/opt/ since there's nothing in there anyway
   c) Add packages python3-click and python3-jinja2 to Build-Depnds in 
debian/control (without these, it FTBFS)
   d) remove libqt6* and qt6-qpa-plugins dependencies in 
debian/control (see #1026957).



I tried with these changes but I am getting:


/<>/src/connectionbenchmark/benchmarktaskdownload.cpp:50:4: 
error: #error Check if QT added support for QDnsLookup::lookup() on Android
   50 | #  error Check if QT added support for QDnsLookup::lookup() on 
Android

  |    ^
[ 56%] Building CXX object 
src/CMakeFiles/mozillavpn.dir/connectionbenchmark/benchmarktaskping.cpp.o


rings a bell?

Thanks

S

Processed: Re: libmaa: FTBFS: dh_auto_build: error: exec (for cmd: mkcmake PREFIX=/usr MANDIR=/usr/share/man INFODIR=/usr/share/info SYSCONFDIR=/etc STRIPFLAG= LIBDIR=/usr/lib/x86_64-linux-gnu LIBEXEC

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #1027657 [src:libmaa] libmaa: FTBFS: dh_auto_build: error: exec (for cmd: 
mkcmake PREFIX=/usr MANDIR=/usr/share/man INFODIR=/usr/share/info 
SYSCONFDIR=/etc STRIPFLAG= LIBDIR=/usr/lib/x86_64-linux-gnu 
LIBEXECDIR=/usr/lib/x86_64-linux-gnu) failed: No such file or directory
Severity set to 'normal' from 'serious'
> notfound -1 libmaa/1.4.7-1
Bug #1027657 [src:libmaa] libmaa: FTBFS: dh_auto_build: error: exec (for cmd: 
mkcmake PREFIX=/usr MANDIR=/usr/share/man INFODIR=/usr/share/info 
SYSCONFDIR=/etc STRIPFLAG= LIBDIR=/usr/lib/x86_64-linux-gnu 
LIBEXECDIR=/usr/lib/x86_64-linux-gnu) failed: No such file or directory
No longer marked as found in versions libmaa/1.4.7-1.
> tags -1 - ftbfs
Bug #1027657 [src:libmaa] libmaa: FTBFS: dh_auto_build: error: exec (for cmd: 
mkcmake PREFIX=/usr MANDIR=/usr/share/man INFODIR=/usr/share/info 
SYSCONFDIR=/etc STRIPFLAG= LIBDIR=/usr/lib/x86_64-linux-gnu 
LIBEXECDIR=/usr/lib/x86_64-linux-gnu) failed: No such file or directory
Removed tag(s) ftbfs.

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

Bug#1027657: libmaa: FTBFS: dh_auto_build: error: exec (for cmd: mkcmake PREFIX=/usr MANDIR=/usr/share/man INFODIR=/usr/share/info SYSCONFDIR=/etc STRIPFLAG= LIBDIR=/usr/lib/x86_64-linux-gnu LIBEXECDI

[Bastian Germann]

Control: severity -1 normal
Control: notfound -1 libmaa/1.4.7-1
Control: tags -1 - ftbfs

On Mon, 9 Jan 2023 10:51:06 +0200 Peter Pentchev  wrote:

FTR, I think this was fixed by the upload of mk-configure/0.37.0-2, which
actually installed the package files (including the mkcmake program).


I comfirm. Let's decrease severity so that this will not get autoremoved.

Bug#1026088: rdma-core: diff for NMU version 44.0-1.1

[Adrian Bunk]

Control: tags 1026088 + patch
Control: tags 1026088 + pending

Dear maintainer,

I've prepared an NMU for rdma-core (versioned as 44.0-1.1) and uploaded 
it to DELAYED/2. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru rdma-core-44.0/debian/changelog rdma-core-44.0/debian/changelog
--- rdma-core-44.0/debian/changelog	2023-01-03 18:29:32.0 +0200
+++ rdma-core-44.0/debian/changelog	2023-01-09 23:24:21.0 +0200
@@ -1,3 +1,11 @@
+rdma-core (44.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add 32-bit MIPS architectures to COHERENT_DMA_ARCHS.
+(Closes: #1026088)
+
+ -- Adrian Bunk   Mon, 09 Jan 2023 23:24:21 +0200
+
 rdma-core (44.0-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru rdma-core-44.0/debian/rules rdma-core-44.0/debian/rules
--- rdma-core-44.0/debian/rules	2023-01-03 16:56:24.0 +0200
+++ rdma-core-44.0/debian/rules	2023-01-09 23:24:13.0 +0200
@@ -4,7 +4,7 @@
 
 export DEB_BUILD_MAINT_OPTIONS=hardening=+all
 
-COHERENT_DMA_ARCHS = amd64 arm64 i386 ia64 mips64 mips64el mips64r6 mips64r6el powerpc powerpcspe ppc64 ppc64el riscv64 s390x sparc64 x32
+COHERENT_DMA_ARCHS = amd64 arm64 i386 ia64 mips mipsel mipsr6 mipsr6el mips64 mips64el mips64r6 mips64r6el powerpc powerpcspe ppc64 ppc64el riscv64 s390x sparc64 x32
 
 dh_params = --with python3 --builddirectory=build-deb
 

Bug#1028269: marked as done (mender-connect FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Mon, 9 Jan 2023 23:13:31 +0100
with message-id <20230109221331.mxuymgzo54iib...@fatal.se>
and subject line Re: mender-connect FTBFS: test failures
has caused the Debian Bug report #1028269,
regarding mender-connect FTBFS: test failures
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.)


-- 
1028269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028269
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mender-connect
Version: 2.1.0+ds1-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=mender-connect=2.1.0%2Bds1-2

...
task-0: --- FAIL: TestPermit_DownloadFile (0.00s)
task-0: --- PASS: TestPermit_DownloadFile/not_a_regular_file (0.00s)
task-0: --- PASS: TestPermit_DownloadFile/not_in_a_chroot (0.00s)
task-0: --- PASS: TestPermit_DownloadFile/file_owner_mismatch (0.00s)
task-0: --- FAIL: TestPermit_DownloadFile/file_owner_match (0.00s)
task-0: --- PASS: TestPermit_DownloadFile/file_group_mismatch (0.00s)
task-0: --- PASS: TestPermit_DownloadFile/file_group_match (0.00s)
task-0: --- PASS: 
TestPermit_DownloadFile/over_the_max_file_size_limit_in_bytes (0.00s)
task-0: --- PASS: 
TestPermit_DownloadFile/below_the_max_file_size_limit_in_bytes (0.00s)
...
task-0: --- FAIL: TestPermit_UploadFile (0.00s)
task-0: --- PASS: 
TestPermit_UploadFile/over_the_max_file_size_limit_in_bytes (0.00s)
task-0: --- PASS: TestPermit_UploadFile/not_in_a_chroot (0.00s)
task-0: --- PASS: TestPermit_UploadFile/forbidden_to_follow_links (0.00s)
task-0: --- PASS: TestPermit_UploadFile/file_exists_forbidden_to_overwrite 
(0.00s)
task-0: --- PASS: TestPermit_UploadFile/file_exists_allowed_to_overwrite 
(0.00s)
task-0: --- PASS: 
TestPermit_UploadFile/file_exists_allowed_to_overwrite_owner_mismatch (0.00s)
task-0: --- FAIL: 
TestPermit_UploadFile/file_exists_allowed_to_overwrite_owner_match (0.00s)
task-0: --- PASS: 
TestPermit_UploadFile/file_exists_allowed_to_overwrite_group_mismatch (0.00s)
task-0: --- PASS: 
TestPermit_UploadFile/file_exists_allowed_to_overwrite_group_match (0.00s)
task-0: --- PASS: TestPermit_UploadFile/suid_bit_not_allowed_in_modes 
(0.00s)
task-0: --- PASS: TestPermit_UploadFile/suid_bit_allowed_in_modes (0.00s)
...
--- End Message ---
--- Begin Message ---
Version: 2.1.0+ds1-3

On Mon, Jan 09, 2023 at 03:01:55AM +0200, Adrian Bunk wrote:
> Source: mender-connect
> Version: 2.1.0+ds1-2
> Severity: serious
> Tags: ftbfs
> 
> https://buildd.debian.org/status/logs.php?pkg=mender-connect=2.1.0%2Bds1-2

Thanks, I noticed after upload. The test passed locally when my gecos
was empty. I've already uploaded -3 with a patch to fix bug in the
testsuite.

> 
> ...
> task-0: --- FAIL: TestPermit_DownloadFile (0.00s)
> task-0: --- PASS: TestPermit_DownloadFile/not_a_regular_file (0.00s)
> task-0: --- PASS: TestPermit_DownloadFile/not_in_a_chroot (0.00s)
> task-0: --- PASS: TestPermit_DownloadFile/file_owner_mismatch (0.00s)
> task-0: --- FAIL: TestPermit_DownloadFile/file_owner_match (0.00s)
> task-0: --- PASS: TestPermit_DownloadFile/file_group_mismatch (0.00s)
> task-0: --- PASS: TestPermit_DownloadFile/file_group_match (0.00s)
> task-0: --- PASS: 
> TestPermit_DownloadFile/over_the_max_file_size_limit_in_bytes (0.00s)
> task-0: --- PASS: 
> TestPermit_DownloadFile/below_the_max_file_size_limit_in_bytes (0.00s)
> ...
> task-0: --- FAIL: TestPermit_UploadFile (0.00s)
> task-0: --- PASS: 
> TestPermit_UploadFile/over_the_max_file_size_limit_in_bytes (0.00s)
> task-0: --- PASS: TestPermit_UploadFile/not_in_a_chroot (0.00s)
> task-0: --- PASS: TestPermit_UploadFile/forbidden_to_follow_links (0.00s)
> task-0: --- PASS: 
> TestPermit_UploadFile/file_exists_forbidden_to_overwrite (0.00s)
> task-0: --- PASS: TestPermit_UploadFile/file_exists_allowed_to_overwrite 
> (0.00s)
> task-0: --- PASS: 
> TestPermit_UploadFile/file_exists_allowed_to_overwrite_owner_mismatch (0.00s)
> task-0: --- FAIL: 
> TestPermit_UploadFile/file_exists_allowed_to_overwrite_owner_match (0.00s)
> task-0: --- PASS: 
> TestPermit_UploadFile/file_exists_allowed_to_overwrite_group_mismatch (0.00s)
> task-0: --- PASS: 
> TestPermit_UploadFile/file_exists_allowed_to_overwrite_group_match (0.00s)
> task-0: --- PASS: TestPermit_UploadFile/suid_bit_not_allowed_in_modes 
> (0.00s)
> task-0: --- PASS: TestPermit_UploadFile/suid_bit_allowed_in_modes (0.00s)
> ...
> --- End Message ---

Processed: rdma-core: diff for NMU version 44.0-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1026088 + patch
Bug #1026088 [src:rdma-core] rdma-core: add mips64* to COHERENT_DMA_ARCHS
Added tag(s) patch.
> tags 1026088 + pending
Bug #1026088 [src:rdma-core] rdma-core: add mips64* to COHERENT_DMA_ARCHS
Added tag(s) pending.

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

Bug#1028354: apbs fails with python3.11: "invalid mode rU"

[Steve Langasek]

Package: apbs
Version: 3.4.1-4
Severity: grave
Tags: patch
Justification: renders package unusable
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu lunar ubuntu-patch

apbs fails its autopkgtests with python3.11, revealing a bug in the
software, because it uses a mode flag to open() which has been deprecated
since python 3 and is now obsolete in python 3.11:

[...]

Testing input file apbs-mol-parallel.in

Splitting the input file into 4 separate files using the inputgen utility

Test failed: invalid mode: 'rU'
Elapsed time: 0.000597 seconds

[...]

  
(https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/a/apbs/20221229_092334_1918a@/log.gz)

This is not an autopkgtest regression in Debian because the autopkgtest
itself is also buggy, using bash-specific shell syntax in a file with no
interpreter line that as a result fails under /bin/sh.  (I'm not sure why it
gets farther on Ubuntu's autopkgtest infrastructure.) However, despite not
being detected as an autopkgtest regression, it shows a significant code
defect when run under python3.11 and should be fixed.

Please see the attached patch.

Thanks for considering,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru apbs-3.4.1/debian/patches/open-U-obsolete.patch 
apbs-3.4.1/debian/patches/open-U-obsolete.patch
--- apbs-3.4.1/debian/patches/open-U-obsolete.patch 1969-12-31 
16:00:00.0 -0800
+++ apbs-3.4.1/debian/patches/open-U-obsolete.patch 2023-01-09 
13:27:36.0 -0800
@@ -0,0 +1,21 @@
+Description: Drop obsolete "U" mode passed to open()
+ The "U" mode has been deprecated in python since python3 and has had no
+ effect.  In python 3.11, it is now disallowed.  Drop this mode flag that
+ causes runtime failures.
+Author: Steve Langasek 
+Last-Update: 2023-01-09
+Forwarded: no
+
+Index: apbs-3.4.1/tools/manip/inputgen.py
+===
+--- apbs-3.4.1.orig/tools/manip/inputgen.py
 apbs-3.4.1/tools/manip/inputgen.py
+@@ -311,7 +311,7 @@
+file (string)
+ """
+ nproc = 0
+-file = open(filename, "rU")
++file = open(filename, "r")
+ text = ""
+ while 1:
+ line = file.readline()
diff -Nru apbs-3.4.1/debian/patches/series apbs-3.4.1/debian/patches/series
--- apbs-3.4.1/debian/patches/series2022-06-04 00:58:09.0 -0700
+++ apbs-3.4.1/debian/patches/series2023-01-09 13:26:06.0 -0800
@@ -5,3 +5,4 @@
 python3.patch
 cmake.patch
 docs.patch
+open-U-obsolete.patch

Bug#1027254: dask and pandas 1.5

[Rebecca N. Palmer]

(I meant to send that to the dask/pandas bug, which is #1025393, but 
both of them are potential reasons to update dask.)


The intake issue is now https://github.com/dask/dask/issues/9813
(They're planning to fix it in intake rather than dask, but we might not 
be allowed to do that after the 12th.)

Processed: Re: ulmo fails in pandas 1.4+

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/ulmo-dev/ulmo/pull/214
Bug #1017573 [python3-ulmo] python3-ulmo: autopkgtest fail with pandas 1.4
Set Bug forwarded-to-address to 'https://github.com/ulmo-dev/ulmo/pull/214'.
> severity -1 serious
Bug #1017573 [python3-ulmo] python3-ulmo: autopkgtest fail with pandas 1.4
Severity set to 'serious' from 'important'

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

Bug#1028097: marked as done (mplcursors: remove Build-Depends: libopenblas0 (use libblas-dev instead))

[Debian Bug Tracking System]

Your message dated Mon, 09 Jan 2023 21:52:16 +
with message-id 
and subject line Bug#1028097: fixed in mplcursors 0.5.2-2
has caused the Debian Bug report #1028097,
regarding mplcursors: remove Build-Depends: libopenblas0 (use libblas-dev 
instead)
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.)


-- 
1028097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028097
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mplcursors
Version: 0.5.2-1
Severity: serious
Justification: debci

mplcursors Build-Depends:libopenblas0

This is bad for several reasons.

Firstly, OpenBLAS is not available on all architectures. In particular
it's not available on armel (and mipsel), and therefore debci testing
on armel fails, due to the missing libopenblas0.  That's why I'm
filing this bug as Severity: serious (debci).

Secondly, it's wrong to specify a specific library binary package in
Build-Depends. Build-Depends should be made using the development
package instead, i.e. Build-Depends: libblas-dev.  Note that is not
Build-Depends: libopenblas-dev, see next point.

Thirdly, in regards to BLAS support, all BLAS packages are
binary-compatible, with the preferred BLAS implementation controllable
using the debian alternatives mechanisms.  Even where OpenBLAS is
available, it may not be the best BLAS implementation for the activity
that a particular system performs.  That is, the local admin might
determine that blis or atlas (or intel-mkl) performs better. Not to
mention the various threaded builds which would generally have better
performance than libopenblas0, which is a serial build.

For this reason, debian packages using blas are usually built against
the generic (slow) libblas-dev.  Then one of the performant BLAS
implementation is installed at runtime by the system administrator.

On your own machine you'll want one of the optimised BLAS
implementations installed (libopenblas0, for instance). So to allow
for this the Build-Depends can include alternatives.  But the first
alternative should be the generic development package, libblas-dev, so
that it's used by the debian buildds to build the package.

Thus, the Build-Depends should be something like

  Build-Depends: libblas-dev | libopenblas-dev | libblis-dev | libatlas-base-dev
--- End Message ---
--- Begin Message ---
Source: mplcursors
Source-Version: 0.5.2-2
Done: Sudip Mukherjee 

We believe that the bug you reported is fixed in the latest version of
mplcursors, 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.
Sudip Mukherjee  (supplier of updated mplcursors 
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, 09 Jan 2023 20:34:59 +
Source: mplcursors
Architecture: source
Version: 0.5.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Sudip Mukherjee 
Closes: 1028097
Changes:
 mplcursors (0.5.2-2) unstable; urgency=medium
 .
   * Remove dependency on libopenblas. (Closes: #1028097)
Checksums-Sha1:
 97ff4c82921c3c5718537cc3dc6c7a6c2625fce8 2156 mplcursors_0.5.2-2.dsc
 979120caa8aab252baeab3505fdb6d8b5234c0f6 3204 mplcursors_0.5.2-2.debian.tar.xz
 0bec86183450bc1f80ac70c1fbe01af57cd677ce 10211 
mplcursors_0.5.2-2_amd64.buildinfo
Checksums-Sha256:
 03548cdcd80114ca814cd2a51b286670eb2b72e3558afec87fcadee190283317 2156 
mplcursors_0.5.2-2.dsc
 a7eb990d1fde03b6dd83e1db532d329df6adbf05523d437d67cc9fe524a0aefc 3204 
mplcursors_0.5.2-2.debian.tar.xz
 1dcd4e5cc6e9edb00b650b846fc9993e69e284f627e492e7d09e07720a78e5bd 10211 
mplcursors_0.5.2-2_amd64.buildinfo
Files:
 7ae7e40eb2acfb2eef60c0e601127d80 2156 python optional mplcursors_0.5.2-2.dsc
 cbcef199c5c86f8393d2dba77fcf0ad6 3204 python optional 
mplcursors_0.5.2-2.debian.tar.xz
 b22f3ead1c38327b0e0320d2c41db3cf 10211 python optional 
mplcursors_0.5.2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuDQJkCg9jZvBlJrHR5mjUUbRKzUFAmO8gdEACgkQR5mjUUbR
KzX8hQ//auuaEZ3FSDUqieCi1PKkYKvEb/pidiR9Xgg4Z8OgPU5Ew+vAUO+S5A1O
WxlRyVGfj0iDbt4xoolKl6OTh+SpBfybViy8rLzh26P+pDX9Mm7bI8fEtPlkdbVp

Bug#1019781: dolphin-emu: Please transition to wxwidgets3.2

[Olly Betts]

On Wed, Sep 14, 2022 at 03:42:14PM -0400, s...@techie.net wrote:
> Please transition dolphin-emu from wxwidgets3.0 to wxwidgets3.2.

I've been looking through the handful of packages which are still
using wxwidgets3.0 with an eye to seeing if any can usefully be
NMUed to help them reenter testing before the release freeze.

I see in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986739#5 :

| (upstream switched to QT5 3 years ago)

That comment is dated 2021-04-10 so it's actually more like 5 years ago
now.

That's long enough ago that the code is likely to need changes for wx3.2
so it seems most sensible to address this bug by packaging a recent
snapshot from upstream (or convincing upstream to make a release) which
would eliminate the wxwidgets dependency.

Updating to newer upstream code also seems like probably it's the best
way to address most of the other open RC bugs.

Cheers,
Olly

Bug#956949: elektra build depends on cruft package swig3.0

[Bastian Germann]

Looks like newer versions can be built with swig 4.
Please import a new version.

Bug#1028129: marked as done (securestring FTBFS: fatal error: Python.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 09 Jan 2023 21:33:11 +
with message-id 
and subject line Bug#1028129: fixed in securestring 0.2-2
has caused the Debian Bug report #1028129,
regarding securestring FTBFS: fatal error: Python.h: No such file or directory
to be marked as done.

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

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


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

https://buildd.debian.org/status/logs.php?pkg=securestring=0.2-1

...
creating build/temp.linux-x86_64-3.10
x86_64-linux-gnu-gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 
-Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv 
-O2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/include/python3.10 -c pysecstr.c -o 
build/temp.linux-x86_64-3.10/pysecstr.o
pysecstr.c:3:10: fatal error: Python.h: No such file or directory
3 | #include 
  |  ^~
compilation terminated.
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
E: pybuild pybuild:388: build: plugin distutils failed with: exit code=1: 
/usr/bin/python3.10 setup.py build
--- End Message ---
--- Begin Message ---
Source: securestring
Source-Version: 0.2-2
Done: Bo YU 

We believe that the bug you reported is fixed in the latest version of
securestring, 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.
Bo YU  (supplier of updated securestring 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, 09 Jan 2023 07:43:55 +0800
Source: securestring
Architecture: source
Version: 0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Bo YU 
Closes: 1028129
Changes:
 securestring (0.2-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Joost van Baal-Ilić ]
   * some housekeeping: filling in the blanks
   * cleaning up unused stuff
   * fix homepage to https://github.com/dnet/pysecstr
   * debian/watch, based upon watch file from
 https://salsa.debian.org/python-team/packages/aiohttp-apispec
   * arch, multi-arch
   * fix d/copyright
   * shlibs
 .
   [ Bo YU ]
   * fix ftbfs with python3-dev-all. (Closes: #1028129)
Checksums-Sha1:
 94eb49e8c934971ebe68df8b2b45ff7d3feec662 1851 securestring_0.2-2.dsc
 e1c8a929adfeb5464a1963b8f3868a92fdc3a839 1988 securestring_0.2-2.debian.tar.xz
 9b33a4caca24cff49bbcad95f2aed4aaddbcc830 6601 
securestring_0.2-2_source.buildinfo
Checksums-Sha256:
 176552390ae6b15b23c5b10db1d28a3645f89524ea6e07c6b5dd3c14ab25b3c9 1851 
securestring_0.2-2.dsc
 a5902c96a3fe57561c8b6b4dea255f577dc2606feb68b1f5889ac175d3211ab1 1988 
securestring_0.2-2.debian.tar.xz
 fbb8194909c8fd222a87377bb2750e5321d60f2f525c3164f0126e85e6920208 6601 
securestring_0.2-2_source.buildinfo
Files:
 89fd6ab43a998fa359dbdf8a95da268e 1851 python optional securestring_0.2-2.dsc
 edc7de20698b91c76a02a490be5d6f72 1988 python optional 
securestring_0.2-2.debian.tar.xz
 0b48aa8dddf383075fa9ec2cff532d1f 6601 python optional 
securestring_0.2-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmO8bTMQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFI6IDACG/Jo9N+Qw88FJNDwA84TEBqj6p/Tb1+5n
4//Gb1AIu+AqG8G5yQfGrMa05stUea2bVSfZegt5uPTyev4W1gPg56tGSLJ+YWlY
jJ+2xBU54DMTOZ6SG3/0i+m/EDFZzUVFNvmVAzTuAcHQ0+RIfXCA9+FrtK5URm20
G+ojmLDIsM9tyS+9vuMUksgr7fnGsf9vt6qef3Cftht/DI60Wbdn6npStMTyArJX
PKY+Zw3Aoym+eoXI4soURdJ1x4uxL0Rk59WYEgA/h+CX0pMBqgT9dUmfiHSYBeB/
ogIQXB+BClUGFOPBpSvOvoSfpCR/iDDeNOlHXxHqg5u8uQ9HK1Fp/IsSwln6scN6
2wyTLwfgigubXCgZJUxWiLxBt5HQLNS5oBxR1u9g+4XR8CA5wdJfKs70Kc8SYzks
WhNvdL8dk5ZMr73/wuU8Zw9ZFJnbw9PqGaboW7eX6kRkaN44R5sjiUFJzcpt8/7A
GM3wZee8QmCYTgZ41j9qhHTJm0XSO64=
=+TZ3
-END PGP SIGNATURE End Message ---

Bug#1026769: marked as done (rust-trust-dns-proto - uninstallable on architectures other than arm* and x86*)

[Debian Bug Tracking System]

Your message dated Mon, 09 Jan 2023 21:32:26 +
with message-id 
and subject line Bug#1026769: fixed in rust-trust-dns-proto 0.22.0-2
has caused the Debian Bug report #1026769,
regarding rust-trust-dns-proto - uninstallable on architectures other than arm* 
and x86*
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.)


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

Package: rust-trust-dns-proto
Version: 0.22.0-1
Severity: serious

01234567890123456789012345678901234567890123456789012345678901234567890123456789
rust-trust-dns-proto has an "optional" (in the cargo sense) dependency on
rustls, since collapse_features is used*, this results in it depending but not
build-depending on rust-rustls.

rustls itself is written in portable rust. However it depends on ring which is
written in a mixture of rust, C and asm and current releases only support x86-*
and arm-*. There is upstream work to improve portability but I wouldn't feel
comfortable packaging a pre-release version of a crypto library and it looks
like s390x is still out of luck even with current upstream main

So the current situation is that rust-trust-dns-proto is uninstable on three
release architectures and is unable to migrate to testing, the question then
becomes what to do about it, I see three options.

1. Add architecture restrictions to the packaging so the features are
   only made available on the relevant architectures.
2. Add build-dependencies so the package is not built on architectures
   where rustls/ring is available. The request removal of the uninstable
   package by ftpmaster.
3. Disable rustls support in the trust-dns stack completely.

Option 1 is the best from the point of view of offering the widest range of
features on each architecture. Unfortunately debcargo is currently unable to
do this declaratively, it can only be done by overriding debian/control which
makes maintaining the package more annoying.

I attempted to implement option 1 with the 0.21.2-4 upload, but I screwed up
slightly and as I was about to fix my screwups, my changes were reverted by
siretart and he implemented option 2 in the 0.21.2-5 upload.

However the upload of 0.22.0-1 seemed to drop the implementation of option
2, leading to the package becoming uninstallable again.

Meanwhile over in trust-dns-client, Reinhard seemed to go with the option of
disabling rustls support.

I don't really mind which option we implement, but it would be good to have
a consensus and then do it consistently.

* If collapse_features was not used, the affect would be that the main binary 
package
  was installable, but the relavent feature packages were not. This would still
  prevent the package from migrating to testing.
--- End Message ---
--- Begin Message ---
Source: rust-trust-dns-proto
Source-Version: 0.22.0-2
Done: Reinhard Tartler 

We believe that the bug you reported is fixed in the latest version of
rust-trust-dns-proto, 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.
Reinhard Tartler  (supplier of updated 
rust-trust-dns-proto 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, 09 Jan 2023 16:04:16 -0500
Source: rust-trust-dns-proto
Architecture: source
Version: 0.22.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Reinhard Tartler 
Closes: 1026769
Changes:
 rust-trust-dns-proto (0.22.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Build-Depends on rust-ring to ensure we only provide packages on 
architectures
 that provide all build depends, Closes: #1026769
   * Package trust-dns-proto 0.22.0 from crates.io using debcargo 2.6.0
Checksums-Sha1:
 6a1b5baab6a72633c46c9cd43b9a743fb43aab94 3812 rust-trust-dns-proto_0.22.0-2.dsc
 452391655e912b5b15ba0f51b38dddaebd77c89e 7876 
rust-trust-dns-proto_0.22.0-2.debian.tar.xz
 45b1c64bb5f3421c6adf0951684d07f398e32669 7892 
rust-trust-dns-proto_0.22.0-2_source.buildinfo
Checksums-Sha256:
 

Bug#1027476: marked as done (cron: postrm script fails because expected dpkg-statoverride is not present)

[Debian Bug Tracking System]

Your message dated Mon, 09 Jan 2023 21:24:40 +
with message-id 
and subject line Bug#1027476: fixed in cron 3.0pl1-155
has caused the Debian Bug report #1027476,
regarding cron: postrm script fails because expected dpkg-statoverride is not 
present
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.)


-- 
1027476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027476
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cron
Version: 3.0pl1-154
Severity: normal

Dear Maintainer,

The postrm script in the current version of the cron package assumes the
presence of a dpkg-statoverride for /usr/bin/crontab, but no such statoverride
is present on my systems. As a result when I try to 'purge' the cron package
the process fails.

Recipe to reproduce the issue:

1) cd /root
2) mkdir foo
3) debootstrap --variant=minbase --include=logrotate,systemd-cron bookworm
4) chroot /root/foo /bin/bash
5) apt remove --purge cron

This results in the following output:

Reading package lists... Done
Building dependency tree... Done
The following packages will be REMOVED:
  cron*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such device)
(Reading database ... 11054 files and directories currently installed.)
Purging configuration files for cron (3.0pl1-154) ...
dpkg-statoverride: warning: no override present
dpkg: error processing package cron (--purge):
 installed cron package post-removal script subprocess returned error exit
status 2
Errors were encountered while processing:
 cron
E: Sub-process /usr/bin/dpkg returned an error code (1)

Editing /var/lib/dpkg/info/cron.postrm to remove the first section resolves the
issue.


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

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

Versions of packages cron depends on:
ii  cron-daemon-common   3.0pl1-154
ii  init-system-helpers  1.65.2
ii  libc62.36-7
ii  libpam-runtime   1.5.2-5
ii  libpam0g 1.5.2-5
ii  libselinux1  3.4-1+b4
ii  sensible-utils   0.0.17

Versions of packages cron recommends:
ii  msmtp-mta [mail-transport-agent]  1.8.22-1

Versions of packages cron suggests:
pn  checksecurity   
ii  logrotate   3.21.0-1
ii  systemd-cron [anacron]  1.15.19-2+b1
--- End Message ---
--- Begin Message ---
Source: cron
Source-Version: 3.0pl1-155
Done: Georges Khaznadar 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 09 Jan 2023 21:32:55 +0100
Source: cron
Architecture: source
Version: 3.0pl1-155
Distribution: unstable
Urgency: medium
Maintainer: Javier Fernández-Sanguino Peña 
Changed-By: Georges Khaznadar 
Closes: 1027476
Changes:
 cron (3.0pl1-155) unstable; urgency=medium
 .
   * added a dependency on dpkg. Closes: #1027476
Checksums-Sha1:
 a3cdf84afecd9ef79629ac6a061169910e181418 2129 cron_3.0pl1-155.dsc
 873e631bb8163a8c89d234e4a8e858e3de967d83 113236 cron_3.0pl1-155.debian.tar.xz
 33580dc1483e8bb192dd21da8edb427f94c70c4f 6355 cron_3.0pl1-155_source.buildinfo
Checksums-Sha256:
 

Processed: zeroc-ice: diff for NMU version 3.7.8-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1027849 + pending
Bug #1027849 [src:zeroc-ice] zeroc-ice FTBFS with Python 3.11 as default version
Added tag(s) pending.

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

Bug#1027849: zeroc-ice: diff for NMU version 3.7.8-1.1

[Adrian Bunk]

Control: tags 1027849 + pending

Dear maintainer,

I've prepared an NMU for zeroc-ice (versioned as 3.7.8-1.1) and uploaded 
it to DELAYED/2. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru zeroc-ice-3.7.8/debian/changelog zeroc-ice-3.7.8/debian/changelog
--- zeroc-ice-3.7.8/debian/changelog	2022-08-05 10:25:42.0 +0300
+++ zeroc-ice-3.7.8/debian/changelog	2023-01-09 21:57:08.0 +0200
@@ -1,3 +1,10 @@
+zeroc-ice (3.7.8-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add upstream build fixes for Python 3.11. (Closes: #1027849)
+
+ -- Adrian Bunk   Mon, 09 Jan 2023 21:57:08 +0200
+
 zeroc-ice (3.7.8-1) unstable; urgency=medium
 
   * New upstream version 3.7.8
diff -Nru zeroc-ice-3.7.8/debian/patches/0001-Python-3.11-build-fixes-1394.patch zeroc-ice-3.7.8/debian/patches/0001-Python-3.11-build-fixes-1394.patch
--- zeroc-ice-3.7.8/debian/patches/0001-Python-3.11-build-fixes-1394.patch	1970-01-01 02:00:00.0 +0200
+++ zeroc-ice-3.7.8/debian/patches/0001-Python-3.11-build-fixes-1394.patch	2023-01-09 21:56:48.0 +0200
@@ -0,0 +1,48 @@
+From a98f34df525dce54a96f443806599978b293d7c5 Mon Sep 17 00:00:00 2001
+From: Jose 
+Date: Thu, 3 Nov 2022 16:52:58 +0100
+Subject: Python 3.11 build fixes (#1394)
+
+---
+ python/modules/IcePy/Slice.cpp | 7 ++-
+ python/modules/IcePy/Util.cpp  | 5 +
+ 2 files changed, 11 insertions(+), 1 deletion(-)
+
+diff --git a/python/modules/IcePy/Slice.cpp b/python/modules/IcePy/Slice.cpp
+index e11365d8d4..7138e76dac 100644
+--- a/python/modules/IcePy/Slice.cpp
 b/python/modules/IcePy/Slice.cpp
+@@ -14,7 +14,12 @@
+ // Python headers needed for PyEval_EvalCode.
+ //
+ #include 
+-#include 
++// Use ceval.h instead of eval.h with Pyhthon 3.11 and greater
++#if PY_VERSION_HEX >= 0x030B
++#   include 
++#else
++#   include 
++#endif
+ 
+ using namespace std;
+ using namespace IcePy;
+diff --git a/python/modules/IcePy/Util.cpp b/python/modules/IcePy/Util.cpp
+index f15c7a5c69..73955c933a 100644
+--- a/python/modules/IcePy/Util.cpp
 b/python/modules/IcePy/Util.cpp
+@@ -225,7 +225,12 @@ IcePy::getFunction()
+ //
+ // Get name of current function.
+ //
++// Use PyEval_GetFrame with Pyhthon >= 3.11
++#if PY_VERSION_HEX >= 0x030B
++PyFrameObject *f = PyEval_GetFrame();
++#else
+ PyFrameObject *f = PyThreadState_GET()->frame;
++#endif
+ PyObjectHandle code = getAttr(reinterpret_cast(f), "f_code", false);
+ assert(code.get());
+ PyObjectHandle func = getAttr(code.get(), "co_name", false);
+-- 
+2.30.2
+
diff -Nru zeroc-ice-3.7.8/debian/patches/series zeroc-ice-3.7.8/debian/patches/series
--- zeroc-ice-3.7.8/debian/patches/series	2022-08-05 10:25:42.0 +0300
+++ zeroc-ice-3.7.8/debian/patches/series	2023-01-09 21:57:08.0 +0200
@@ -1 +1,2 @@
 java-build.patch
+0001-Python-3.11-build-fixes-1394.patch

Bug#1019799: marked as done (libalien-wxwidgets-perl: Please transition to wxwidgets3.2)

[Debian Bug Tracking System]

Your message dated Mon, 9 Jan 2023 15:58:01 -0500 (EST)
with message-id 
and subject line Fixed by today's upload
has caused the Debian Bug report #1019799,
regarding libalien-wxwidgets-perl: Please transition to wxwidgets3.2
to be marked as done.

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

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


-- 
1019799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019799
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libalien-wxwidgets-perl
Severity: normal
Control: block 1019416 by -1

Hi,

Please transition libalien-wxwidgets-perl from wxwidgets3.0 to
wxwidgets3.2.

wxWidgets 3.2 (a new API/ABI stable release) has been released a few
months ago and is now packaged in unstable as wxwidgets3.2. Upstream
has stopped supporting wxWidgets 3.0, so the Debian wx team would
like to migrate all wx package users to wxwidgets3.2 for bullseye,
with the plan to remove wxwidgets3.0 before release.

For most packages, the transition should be as simple as changing
Build-Depends from libwxgtk3.0-gtk3-dev to libwxgtk3.2-dev. Some
packages may require small patches; I'm happy to help with those (and
I have some already from working on this transition in Fedora
already).

Thanks, Scott 
--- End Message ---
--- Begin Message ---

Version: libalien-wxwidgets-perl/0.69+dfsg-5--- End Message ---

Bug#1027227: marked as done (mdanalysis: autopkgtest fail with numpy/1.24.1)

[Debian Bug Tracking System]

Your message dated Mon, 09 Jan 2023 20:49:17 +
with message-id 
and subject line Bug#1027227: fixed in mdanalysis 2.4.2+dfsg1-1
has caused the Debian Bug report #1027227,
regarding mdanalysis: autopkgtest fail with numpy/1.24.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.)


-- 
1027227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mdanalysis
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: numpy1.24

Hello,
recently numpy/1.24.1 has been uploaded to experimental, and this package
autopkgtest fail when running against it.

An overview of the upstream changes in the 1.24.x series is available at:

  https://numpy.org/doc/stable/release/1.24.0-notes.html

Several of the errors are in the form of:

AttributeError: module 'numpy' has no attribute 'X'

with X in [float, int, bool, object, ...]. This is because, numpy upstream in
1.24.0, finally decided to expire

  
https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases

some deprecations introduced in 1.20.0

  
https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated

(released almost 2 years ago).

All of those are quite straightforward to fix, since often it's just necessary
to stop importing them from numpy and use the python native types.

Other changes may requires a bit more rework to be addressed.

Currently numpy/1.24.x is in experimental, but given the possible longer support
that it'll receive from upstream, we're hopeful to include this in bookworm, so
your help is necessary to address this bug ASAP.

Regards,
Sandro
--- End Message ---
--- Begin Message ---
Source: mdanalysis
Source-Version: 2.4.2+dfsg1-1
Done: Drew Parsons 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 09 Jan 2023 17:54:02 +0100
Source: mdanalysis
Architecture: source
Version: 2.4.2+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Drew Parsons 
Closes: 1027227
Changes:
 mdanalysis (2.4.2+dfsg1-1) unstable; urgency=medium
 .
   * New upstream release.
 - fixes DensityAnalysis for numpy 1.24. Closes: #1027227,
Checksums-Sha1:
 69c14af4404d480816d3cc981f6c3ec9981ee6be 2901 mdanalysis_2.4.2+dfsg1-1.dsc
 6d13bb890605d944507d8be8951e1b21293fb345 46702388 
mdanalysis_2.4.2+dfsg1.orig.tar.xz
 b760ce377b44cf357da62daa5b2e5919f51f9a82 8768 
mdanalysis_2.4.2+dfsg1-1.debian.tar.xz
Checksums-Sha256:
 d813d966ae985ec7fee6f88f4c5d6146d7dff147b2975a1da520fbfe168964fc 2901 
mdanalysis_2.4.2+dfsg1-1.dsc
 500281060fd0d99b8e4a5ebac2b69e54e3d4b2d60dae618d936039394e865b21 46702388 
mdanalysis_2.4.2+dfsg1.orig.tar.xz
 a716d3b05e0de061e93b901f4780505c8c484e347af1f631f41821b2570ad830 8768 
mdanalysis_2.4.2+dfsg1-1.debian.tar.xz
Files:
 2a3f10b6458c10ded836eab8e4e511ec 2901 python optional 
mdanalysis_2.4.2+dfsg1-1.dsc
 ce05ec2f2c4ac19a6fd45992052b9d1e 46702388 python optional 
mdanalysis_2.4.2+dfsg1.orig.tar.xz
 5eb135305e3576bc8c6ead0d6eee827a 8768 python optional 
mdanalysis_2.4.2+dfsg1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmO8c10ACgkQVz7x5L1a
AfpH8xAAmJtsJmK486INvbCPRK5Vle5+PD4BT8n752K7kla2RqIqu530Dxz76VPL
DYk6CPVwGv0fJ9LB3Iqb7+mtXcSz7vFfcgJQqly2AFXcxgkIvWizohxe90dQrgDw
MV8WFVzaU+SzymZzR9dQy9R2oVh9PplZScYJ/zin2bgxjoECSf5TYk8CTIeWh7G9
2Q15nhBgyqOtfj3BPtuomQwcvcmnIn7nIgXMJkswUUBiOUFL5pQjP7L5hVKJYPcA
VIp6SDJ21eDgBsNeLaVBNMdPE6k13XPqOR/Q865y4cAQ2bI4P9QBOMZrYTNLQ2DD
YW71AjpqsUv0T8b4EBRfdUSf0ctTaQS77xFD+mEXT1Gb6p6221ght5vC9F1Cj3/T
W5MwtMyb8Pl67u5imhQrvXjCy0qjaaRFyMHMPyDuJVAxvV9PnbnMNLR5ssXIJa/T
OzIV48WVXIPar70s4G3yqd2t5NttuW/BISrR3Qe7e7az+cxeryhQkAkWhHSDD89N
S3/BXHFDGFwBObgMnpGAdJrIp9c9zJywnqiYEO06sNaqkay8uhuvCEErKOqtsWsA

Bug#1027398: marked as done (gavodachs: autopkgtest needs update for new version of python-cryptography: fails to install)

[Debian Bug Tracking System]

Your message dated Mon, 09 Jan 2023 20:42:30 +
with message-id 
and subject line Bug#1027398: fixed in gavodachs 2.7+dfsg-2
has caused the Debian Bug report #1027398,
regarding gavodachs: autopkgtest needs update for new version of 
python-cryptography: fails to install
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.)


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

Source: gavodachs
Version: 2.7+dfsg-1
Severity: serious
X-Debbugs-CC: python-cryptogra...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:python-cryptography

Dear maintainer(s),

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


   passfail
python-cryptographyfrom testing38.0.4-1
gavodachs  from testing2.7+dfsg-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. 
gavodachs2-server fails to install.


Currently this regression is blocking the migration of 
python-cryptography to testing [1]. Of course, python-cryptography 
shouldn't just break your autopkgtest (or even worse, your package), but 
it seems to me that the change in python-cryptography was intended and 
your package needs to update to the new situation.


If this is a real problem in your package (and not only in your 
autopkgtest), the right binary package(s) from python-cryptography 
should really add a versioned Breaks on the unfixed version of (one of 
your) package(s). Note: the Breaks is nice even if the issue is only in 
the autopkgtest as it helps the migration software to figure out the 
right versions to combine in the tests.


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/g/gavodachs/29784808/log.gz

Setting up python3-docutils (0.17.1+dfsg-3) ...
Setting up python3-gavo-utils (2.7+dfsg-1) ...
Setting up python3-gavo-stc (2.7+dfsg-1) ...
Setting up python3-gavo-votable (2.7+dfsg-1) ...
Setting up python3-gavo (2.7+dfsg-1) ...
Setting up gavodachs2-server (2.7+dfsg-1) ...
Created symlink 
/etc/systemd/system/multi-user.target.wants/dachs.service → 
/lib/systemd/system/dachs.service.

Adding group `gavo' (GID 1001) ...
Done.
adduser: Warning: The home dir /nonexistent you specified can't be 
accessed: No such file or directory

Adding system user `gavo' (UID 103) ...
Adding new user `gavo' (UID 103) with group `gavo' ...
Not creating home directory `/nonexistent'.
Adding user `dachsroot' ...
Adding new user `dachsroot' (1002) with group `gavo (1001)' ...
Creating home directory `/home/dachsroot' ...
Copying files from `/etc/skel' ...
Adding new user `dachsroot' to supplemental / extra groups `users' ...
Adding user `dachsroot' to group `users' ...
*** Error: Oops.  Unhandled exception AttributeError.

Exception payload: module 'lib' has no attribute
'SSL_CTX_set_ecdh_auto'
dpkg: error processing package gavodachs2-server (--configure):
 installed gavodachs2-server package post-installation script 
subprocess returned error exit status 1

dpkg: dependency problems prevent configuration of autopkgtest-satdep:
 autopkgtest-satdep depends on gavodachs2-server; however:
  Package gavodachs2-server is not configured yet.

dpkg: error processing package autopkgtest-satdep (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 gavodachs2-server
 autopkgtest-satdep
E: Sub-process /usr/bin/dpkg returned an error code (1)


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: gavodachs
Source-Version: 2.7+dfsg-2
Done: Markus Demleitner 

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

Bug#1027213: marked as done (gavodachs: autopkgtest fail with numpy/1.24.1)

[Debian Bug Tracking System]

Your message dated Mon, 09 Jan 2023 20:42:30 +
with message-id 
and subject line Bug#1027213: fixed in gavodachs 2.7+dfsg-2
has caused the Debian Bug report #1027213,
regarding gavodachs: autopkgtest fail with numpy/1.24.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.)


-- 
1027213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027213
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gavodachs
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: numpy1.24

Hello,
recently numpy/1.24.1 has been uploaded to experimental, and this package
autopkgtest fail when running against it.

An overview of the upstream changes in the 1.24.x series is available at:

  https://numpy.org/doc/stable/release/1.24.0-notes.html

Several of the errors are in the form of:

AttributeError: module 'numpy' has no attribute 'X'

with X in [float, int, bool, object, ...]. This is because, numpy upstream in
1.24.0, finally decided to expire

  
https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases

some deprecations introduced in 1.20.0

  
https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated

(released almost 2 years ago).

All of those are quite straightforward to fix, since often it's just necessary
to stop importing them from numpy and use the python native types.

Other changes may requires a bit more rework to be addressed.

Currently numpy/1.24.x is in experimental, but given the possible longer support
that it'll receive from upstream, we're hopeful to include this in bookworm, so
your help is necessary to address this bug ASAP.

Regards,
Sandro
--- End Message ---
--- Begin Message ---
Source: gavodachs
Source-Version: 2.7+dfsg-2
Done: Markus Demleitner 

We believe that the bug you reported is fixed in the latest version of
gavodachs, 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.
Markus Demleitner  (supplier of updated gavodachs 
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, 09 Jan 2023 15:32:10 +0100
Source: gavodachs
Architecture: source
Version: 2.7+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Team 

Changed-By: Markus Demleitner 
Closes: 1027213 1027398
Changes:
 gavodachs (2.7+dfsg-2) unstable; urgency=medium
 .
   * Make tapstc REs work with python >= 3.11 (Closes: #1027398)
   * Fixing numpy to SQL and VOTable type mappings for str and bool
 (Closes: #1027213)
Checksums-Sha1:
 ece65131e39cd047c2211a826cf439f84b05b447 1823 gavodachs_2.7+dfsg-2.dsc
 cbe51c340c8fe3be59710464aebe13bd87f5a1a9 10320 
gavodachs_2.7+dfsg-2.debian.tar.xz
 c4844ec2de3207e8e0d4347ba76ff376936ce657 6263 
gavodachs_2.7+dfsg-2_source.buildinfo
Checksums-Sha256:
 0d27e75879a4fd007c7a5178d5d75ccc3f617cce13baea0fb97a27b431279d09 1823 
gavodachs_2.7+dfsg-2.dsc
 05e00b955a5a3fd4e555b03fe7e3a2602865ab1b80b870e3fc57e27d693c12e1 10320 
gavodachs_2.7+dfsg-2.debian.tar.xz
 37d7e5d5628174abd02b4e3719b27a8df8cea15020bf2b1ecf79bc920c7e33a0 6263 
gavodachs_2.7+dfsg-2_source.buildinfo
Files:
 c1747ebc93914da6e698c92593635a3c 1823 python optional gavodachs_2.7+dfsg-2.dsc
 3007a7f87f26adc4da07d6eede6af0bd 10320 python optional 
gavodachs_2.7+dfsg-2.debian.tar.xz
 d4ba7e6f920c115b595ecce255e004cb 6263 python optional 
gavodachs_2.7+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCY7xzJhQcc3RlZmFub3JA
ZGViaWFuLm9yZwAKCRBHew2wJjpU2D9MAP4/c43j54UsO3dKl9id92Nd4tcqjRGX
Yv/xf3kYPlB5GgEA0Qr/k5fBgbFKLch75xRxALLInOFhVYbqCZYug3Ir0QA=
=nAai
-END PGP SIGNATURE End Message ---

Bug#1028303: marked as done (dracut-core: missing Breaks+Replaces: dracut-live (<< 059-2))

[Debian Bug Tracking System]

Your message dated Mon, 09 Jan 2023 20:41:26 +
with message-id 
and subject line Bug#1028303: fixed in dracut 059-3
has caused the Debian Bug report #1028303,
regarding dracut-core: missing Breaks+Replaces: dracut-live (<< 059-2)
to be marked as done.

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

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


-- 
1028303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028303
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dracut-core
Version: 059-2
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 .../dracut-core_059-2_amd64.deb ...
  Unpacking dracut-core (059-2) over (059-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/dracut-core_059-2_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/dracut/modules.d/90overlayfs/module-setup.sh', 
which is also in package dracut-live 059-1
  Errors were encountered while processing:
   /var/cache/apt/archives/dracut-core_059-2_amd64.deb


cheers,

Andreas


dracut-live=059-1_dracut-core=059-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: dracut
Source-Version: 059-3
Done: Thomas Lange 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 09 Jan 2023 20:56:29 +0100
Source: dracut
Architecture: source
Version: 059-3
Distribution: unstable
Urgency: low
Maintainer: Thomas Lange 
Changed-By: Thomas Lange 
Closes: 1028303
Changes:
 dracut (059-3) unstable; urgency=low
 .
   * control: add breaks + replaces, Closes: #1028303
Checksums-Sha1:
 b368205b01b67d703eb23721055b3c6bfbaa1835 2290 dracut_059-3.dsc
 0a51375c976ae44dea9b7185ea8bd5d847135e05 16064 dracut_059-3.debian.tar.xz
 62c131afffa492651d11ca641e0edb9b9c62f9ea 8899 dracut_059-3_amd64.buildinfo
Checksums-Sha256:
 465b4237a88715218c9ea15e7c3efd6f1cf13c921760ddc54405e4c1953d64ad 2290 
dracut_059-3.dsc
 6f7ebf0b7f422ca622b7bfdb8e1cc6d04b9bdcd966378f0b59a3480654b1d1f7 16064 
dracut_059-3.debian.tar.xz
 2798adcdcc1f10d7220dcdaee2a9fdb4b3d02e25b3a8258868eecc35bfb0a820 8899 
dracut_059-3_amd64.buildinfo
Files:
 80a57532b19a242eefe832bf54d4e371 2290 utils optional dracut_059-3.dsc
 192377c0157e8e1fcf5daa8cd5b28553 16064 utils optional 
dracut_059-3.debian.tar.xz
 4b14b73feafae615f56c2c5bb2de24ed 8899 utils optional 
dracut_059-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEEsR7jJz9rLetSjJPaK/jZ/gdLzeQFAmO8cckRHGxhbmdlQGRl
Ymlhbi5vcmcACgkQK/jZ/gdLzeTLpRAAmGxD7/g9j/LR4SJQb6OBPEMuHw9JufXf
pKfbRB2IjaLjszfiqEu54Xm3YweQY3N6Ft6aMVwyT2ebKzgsdNNg+nw73/0XeXXq
9M1gKz8s8tymZVo6oV5wlfdGOMFW1AnG/VHVumNTX3jHFztwF9Jz0De0vV8enwPp
jbS49WZxwJGbiehN6oNvJyGUtqSYoyqMMpRYy5Z+/2wJPCHLeO6+3HXnvcMJB0kf
gDIePROwpRHO/2W1Jjlq6NQC4JZ28KmR59eEAt0iiUm5U+J3LwN1rpymasX3Hq+6
EZaQ03iUBQgrZFh1FEW7WX2IbzW6dxcgBtk5xDnEQwopXP0PSIUabBFIGn2ni0p0
VM0mFFdoex6H5lVEnBhVRlqoqRMX+91ONiL9o0/OMHG/h0e5y+ucWxjd6QzxQBHx
2bqy1cLg1yyNKnwpdtoxzQGujgwCrWUG7oAmE5FpUd5MUor2rP59crtscNyDeTY8
IYFXsmcN56joWU9+z19fiCOiRi7e9jDusSzHMQ4SaGR3cmrrBTukwJHy48Is9A11
Z8lE6Z1QWHa/CMzACfTImWnE7BRW5mRhQNMNy8c4EiHDkKIRcHY/SCSR4g8+waKN
ej2YX0HDqCWlJzt2ulypcJWUF5eEm6WgFR2WfWdrLm3yYjKhJrOH9tzahnU53/Jx
+ONdFBoXZvo=
=J3Oj
-END PGP SIGNATURE End Message ---

Bug#1028350: davmail: autopkgtest regression on arm64, armhf and ppc64el: Unable to store settings: /etc/davmail.properties (Permission denied)

[Paul Gevers]

Source: davmail
Version: 6.0.1.3390-5
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of davmail the autopkgtest of davmail fails in 
testing when that autopkgtest is run with the binary packages of davmail 
from unstable on arm64, armhf and ppc64el. It passes when run with only 
packages from testing. In tabular form:


   passfail
davmailfrom testing6.0.1.3390-5
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/arm64/d/davmail/30174884/log.gz

2023-01-09 22:27:31,539 ERROR [main] davmail  - Unable to store 
settings: /etc/davmail.properties (Permission denied)

java.io.FileNotFoundException: /etc/davmail.properties (Permission denied)
at java.base/java.io.FileOutputStream.open0(Native Method)
at java.base/java.io.FileOutputStream.open(FileOutputStream.java:293)
at java.base/java.io.FileOutputStream.(FileOutputStream.java:235)
at java.base/java.io.FileOutputStream.(FileOutputStream.java:123)
at davmail.Settings.save(Settings.java:358)
at davmail.Settings.load(Settings.java:144)
at davmail.DavGateway.main(DavGateway.java:72)
2023-01-09 22:27:31,546 DEBUG [main] davmail.DavGateway  - Start DavMail 
in server mode
2023-01-09 22:27:31,571 INFO  [main] davmail  - DavMail Gateway 
6.0.1-trunk listening on SMTP port 1025 POP port 1110 IMAP port 1143 
CALDAV port 1080 LDAP port 1389 Exception in thread "main" 
java.lang.UnsatisfiedLinkError: Native library 
(com/sun/jna/linux-aarch64/libjnidispatch.so) not found in resource path 
(/usr/share/davmail/davmail.jar)
	at 
com.sun.jna.Native.loadNativeDispatchLibraryFromClasspath(Native.java:1086)

at com.sun.jna.Native.loadNativeDispatchLibrary(Native.java:1042)
at com.sun.jna.Native.(Native.java:221)
at davmail.util.SystemdNotify$SystemD.(SystemdNotify.java:33)
at davmail.util.SystemdNotify.notify(SystemdNotify.java:67)
at davmail.util.SystemdNotify.ready(SystemdNotify.java:77)
at davmail.DavGateway.start(DavGateway.java:163)
at davmail.DavGateway.main(DavGateway.java:91)
Daemon does not seem to listen
/tmp/autopkgtest-lxc.gn_yo_b1/downtmp/build.uRA/src/debian/tests/binary-starts: 
12: kill: No such process


autopkgtest [22:27:41]: test binary-starts



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1027193: marked as done (brian: autopkgtest fail with numpy/1.24.1)

[Debian Bug Tracking System]

Your message dated Mon, 09 Jan 2023 19:35:19 +
with message-id 
and subject line Bug#1027193: fixed in brian 2.5.1-3
has caused the Debian Bug report #1027193,
regarding brian: autopkgtest fail with numpy/1.24.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.)


-- 
1027193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027193
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: brian
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: numpy1.24

Hello,
recently numpy/1.24.1 has been uploaded to experimental, and this package
autopkgtest fail when running against it.

An overview of the upstream changes in the 1.24.x series is available at:

  https://numpy.org/doc/stable/release/1.24.0-notes.html

Several of the errors are in the form of:

AttributeError: module 'numpy' has no attribute 'X'

with X in [float, int, bool, object, ...]. This is because, numpy upstream in
1.24.0, finally decided to expire

  
https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases

some deprecations introduced in 1.20.0

  
https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated

(released almost 2 years ago).

All of those are quite straightforward to fix, since often it's just necessary
to stop importing them from numpy and use the python native types.

Other changes may requires a bit more rework to be addressed.

Currently numpy/1.24.x is in experimental, but given the possible longer support
that it'll receive from upstream, we're hopeful to include this in bookworm, so
your help is necessary to address this bug ASAP.

Regards,
Sandro
--- End Message ---
--- Begin Message ---
Source: brian
Source-Version: 2.5.1-3
Done: Étienne Mollier 

We believe that the bug you reported is fixed in the latest version of
brian, 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.
Étienne Mollier  (supplier of updated brian 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, 09 Jan 2023 19:30:37 +0100
Source: brian
Architecture: source
Version: 2.5.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Étienne Mollier 
Closes: 1027193
Changes:
 brian (2.5.1-3) unstable; urgency=medium
 .
   * numpy1.24.patch: fix autopkgtest failure with numpy 1.24.
 Closes: #1027193
Checksums-Sha1:
 ad752bbf1d5fd0e030b288a2e6ab7d6c3fcccedb 2614 brian_2.5.1-3.dsc
 f5cdfb773790590a7dfe417c39d19a884142a886 19364 brian_2.5.1-3.debian.tar.xz
Checksums-Sha256:
 b30ff6914513f430e5250f8c629578fb5e42fe128bcd7bfe9badebbfdce797ca 2614 
brian_2.5.1-3.dsc
 df70c128b410e0be462e734aa1d7231b0287d9747fd80f11570567c4c3866272 19364 
brian_2.5.1-3.debian.tar.xz
Files:
 410db56c0d6f7c0045dce344969ba750 2614 python optional brian_2.5.1-3.dsc
 24cfb12a02b70e009081b694f8c724ac 19364 python optional 
brian_2.5.1-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmO8ZKEUHGVtb2xsaWVy
QGRlYmlhbi5vcmcACgkQeTz2fo8NEdrQlQ//ayh+INDPDSFSGO5jJySUpiH4uwg6
v+zzu+2WgFen8Vy9cBtAab/hwU2QF5uQpOvtWipbm43l45SLksegGO4jsGA6Iry5
d1ti+OP4EGSfcBs2cMwkUoTdwG1eTwbvsj2rkt7jGZyWuqW4p7zWbdBMFHpTpGEj
8hRkorw/sqAucY2V4nT6U7xYJ8x2Ev6TD1YY76BnGwBlQW/HGyg/LtnrKnmA3Sn7
RleyXF+/xwvTJCDoLTQpwbj4qbgGR7eJ87K7/lO59xoaJe+TwgnONaNr/U+86MaS
tRDTL91G0KO+OXcGMf5Cn76DuJkqCBgRIYb+inG/zX9uX4MMcYJzyy1zvr5cy+fF
ujE6Qo8bo7ffSWHujHDewaCQ0YxOT4cVnL4kPsZvM5rSKe+eIdJNEZGohNVuGI88
3bs9ahOUMK/vtdUiipvdmA+VXO/Y8BJs83x1Ht2WHty0iMT4pVuHrfyNFO09lGeW
qEeJQIrAtVh0Zh1IpaWf2tUPKltCJGmgkPSbfJ6/yt5A88MZkULdqhwD7PzAXhQd
lwJKTdzH/GIkBu0Qq+9CX1n7qGG5W6iwsIzQLwfsE50P8IE7tEPRFFzX8gP4QqYp
SlzGVSB+koL2URP5CdWzIq7Qmy+F8ckVHEEo+hgFaAhcEYikKadIhkIt4bdsl13h
6qDEtWdghEnW/Uw=
=0CSx
-END PGP SIGNATURE End Message ---

Processed: src:r-cran-callr: fails to migrate to testing for too long: autopkgtest regression

[Debian Bug Tracking System]

Processing control commands:

> close -1 3.7.3-1
Bug #1028348 [src:r-cran-callr] src:r-cran-callr: fails to migrate to testing 
for too long: autopkgtest regression
Marked as fixed in versions r-cran-callr/3.7.3-1.
Bug #1028348 [src:r-cran-callr] src:r-cran-callr: fails to migrate to testing 
for too long: autopkgtest regression
Marked Bug as done

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

Bug#1028348: src:r-cran-callr: fails to migrate to testing for too long: autopkgtest regression

[Paul Gevers]

Source: r-cran-callr
Version: 3.7.2-1
Severity: serious
Control: close -1 3.7.3-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:r-cran-callr has been trying to migrate 
for 61 days [2]. Hence, I am filing this bug. Your package fails its own 
autopkgtest everywhere.


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=r-cran-callr



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1028303: dracut-core: missing Breaks+Replaces: dracut-live (<< 059-2)

[Andreas Beckmann]

On 09/01/2023 18.16, Thomas Lange wrote:

Hi Andreas,

should I replace the old Breaks+Replaces with the new ones, or add them?
These are the current for dracut-core:
Breaks: dracut-network (<< 057+157-2)
Replaces: dracut-network (<< 057+157-2)


Add them. Janitor will tell you once the old ones are old enough 
(usually satisfied in oldstable) to be removed.


Andreas

Bug#1028023: marked as done (librepo FTBFS on MIPS)

[Holger Levsen]

On Mon, Jan 09, 2023 at 08:17:14PM +0200, Adrian Bunk wrote:
> I "improved" it by also breaking the build on all other architectures...
> :-(
> The things that happen when trying to fix a problem you cannot reproduce.

only those who do, do mistakes :)
 
> Patch with the missing import added is attached.

thank you!


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

It's not climate change nor climate crisis, it's climate disaster.


signature.asc
Description: PGP signature

Bug#994108: gcc-9: do not release with bookworm

[Bastian Germann]

On Sat, 11 Sep 2021 23:33:44 +0200 Sebastian Ramacher wrote:

With only odb left requring gcc-9 (#994104), let's remove gcc-9,
gcc-9-cross and gcc-9-cross-ports from bookworm. This bug is here to
keep gcc-9 out of bookworm once removed from there (unless removal from
unstable happens sooner, of course)


There is still the reverse dep kfreebsd-10 (not in testing).
I think the gcc9 packages can be removed now.

Bug#1028346: php-horde-imap-client: fails on login: Return value of Horde_Imap_Client_Tokenize::current() must be an instance of mixed,

[Andy Dorman]

Package: php-horde-imap-client
Version: 2.30.6-1
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

With php7.4-fpm, after updating to 2.30.6-1 users are unable to login. 

Login attempts generate the following error:

HORDE: [imp] TypeError: Return value of Horde_Imap_Client_Tokenize::current() 
must be an instance of mixed, string returned in 
/usr/share/php/Horde/Imap/Client/Tokenize.php:225
HORDE: Stack trace:
HORDE: #0 /usr/share/php/Horde/Imap/Client/Interaction/Server.php(102): 
Horde_Imap_Client_Tokenize->current()
HORDE: #1 /usr/share/php/Horde/Imap/Client/Interaction/Server.php(84): 
Horde_Imap_Client_Interaction_Server->__construct()
HORDE: #2 /usr/share/php/Horde/Imap/Client/Socket.php(4542): 
Horde_Imap_Client_Interaction_Server::create()
HORDE: #3 /usr/share/php/Horde/Imap/Client/Socket.php(621): 
Horde_Imap_Client_Socket->_getLine()
HORDE: #4 /usr/share/php/Horde/Imap/Client/Socket.php(375): 
Horde_Imap_Client_Socket->_connect()
HORDE: #5 /usr/share/php/Horde/Imap/Client/Base.php(839): 
Horde_Imap_Client_Socket->_login()
HORDE: #6 /usr/share/horde/imp/lib/Imap.php(718): 
Horde_Imap_Client_Base->login()
HORDE: #7 /usr/share/horde/imp/lib/Auth.php(86): IMP_Imap->__call()
HORDE: #8 /usr/share/horde/imp/lib/Application.php(370): 
IMP_Auth::authenticate()
HORDE: #9 /usr/share/php/Horde/Registry.php(1197): 
IMP_Application->authAuthenticate()
HORDE: #10 /usr/share/php/Horde/Core/Auth/Application.php(170): 
Horde_Registry->callAppMethod()
HORDE: #11 /usr/share/php/Horde/Auth/Base.php(161): 
Horde_Core_Auth_Application->_authenticate()
HORDE: #12 /usr/share/php/Horde/Core/Auth/Application.php(141): 
Horde_Auth_Base->authenticate()
HORDE: #13 /usr/share/php/Horde/Core/Auth/Application.php(138): 
Horde_Core_Auth_Application->authenticate()
HORDE: #14 /usr/share/horde/login.php(155): 
Horde_Core_Auth_Application->authenticate()
HORDE: #15 {main} [pid 1480064 on line 74 of 
"/usr/share/php/Horde/ErrorHandler.php"]

I reverted php-horde-imap-client back to 2.30.1-4 and the problem went away.

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

Kernel: Linux 6.0.0-6-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages php-horde-imap-client depends on:
ii  libapache2-mod-php8.1 [php-json]  8.1.12-1+b1
hi  php-common2:76
ii  php-horde-exception   2.0.8-9
ii  php-horde-mail2.6.6-4
ii  php-horde-mime2.11.2-1
ii  php-horde-secret  2.0.6-9
ii  php-horde-socket-client   2.1.4-1
ii  php-horde-stream  1.6.3-10
ii  php-horde-stream-filter   2.0.5-1
ii  php-horde-translation 2.2.2-7
ii  php-horde-util2.5.12-1
ii  php-json  2:8.1+92+nmu1
ii  php7.4-json [php-json]7.4.33-1+deb11u1
ii  php8.1-cli [php-json] 8.1.12-1+b1
ii  php8.1-fpm [php-json] 8.1.12-1+b1
ii  php8.2-cli [php-json] 8.2.1-1

Versions of packages php-horde-imap-client recommends:
ii  php-horde-cache 2.5.5-10
ii  php-horde-compress-fast 1.1.1-10
ii  php-horde-crypt-blowfish1.1.4-1
hi  php-horde-db2.4.1-1
ii  php-horde-hashtable 1.2.6-11
pn  php-horde-mongo 
ii  php-horde-pack  1.0.7-7
pn  php-horde-stringprep
ii  php-horde-support   2.2.2-1
ii  php-horde-test  2.6.4+debian0-7
pn  php-intl
ii  php-mbstring2:8.1+92+nmu1
ii  php7.4-mbstring [php-mbstring]  7.4.33-1+deb11u1
ii  php8.1-mbstring [php-mbstring]  8.1.12-1+b1

php-horde-imap-client suggests no packages.

-- no debconf information

Bug#1028345: python3-sage: sagemath uninstallable due to python3-sage issues

[Rann Bar-On]

Package: python3-sage
Version: 9.5-4+b3
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: baronr...@gmail.com

Dear Maintainer,

python3-sage depends on python3 < 3.11, which conflicts with current python 
3.11.1-1, and on libsingular4m2n1, which is unavailable. I therefore can't 
install sage at all.

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (1000, 'unstable'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-updates'), (500, 'stable-security'), (500, 
'proposed-updates'), (500, 'stable'), (100, 'testing'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages python3-sage depends on:
ii  bc1.07.1-3+b1
ii  binutils  2.39.90.20230104-1
ii  bzip2 1.0.8-5+b1
ii  ca-certificates   20211016
pn  cliquer   
pn  cmake 
ii  curl  7.87.0-1
pn  cython3   
pn  ecl   
pn  eclib-tools   
pn  fflas-ffpack  
pn  flintqs   
pn  gap-atlasrep  
pn  gap-dev   
pn  gap-online-help   
pn  gap-primgrp   
pn  gap-smallgrp  
pn  gap-table-of-marks
pn  gap-transgrp  
pn  gfan  
ii  gfortran  4:12.2.0-3
pn  glpk-utils
pn  gmp-ecm   
pn  jmol  
pn  lcalc 
pn  libatomic-ops-dev 
ii  libblas3 [libblas.so.3]   3.11.0-2
ii  libboost-dev  1.74.0.3
pn  libbraiding-dev   
pn  libbraiding0  
pn  libbrial-dev  
pn  libbrial-groebner-dev 
pn  libbrial-groebner3
pn  libbrial3 
ii  libbz2-dev1.0.8-5+b1
ii  libc6 2.36-8
pn  libcdd-dev
pn  libcdd-tools  
pn  libcliquer-dev
pn  libcliquer1   
pn  libcurl4-openssl-dev  
pn  libec-dev 
pn  libec10   
pn  libecl21.2
pn  libecm-dev
pn  libecm1   
pn  libffi-dev
pn  libflint-arb-dev  
pn  libflint-arb2 
pn  libflint-dev  
pn  libflint17
pn  libfreetype6-dev  
pn  libgap-dev
pn  libgap7   
pn  libgc-dev 
ii  libgcc-s1 12.2.0-14
pn  libgd-dev 
ii  libgd32.3.3-7
pn  libgf2x-dev   
pn  libgiac-dev   
pn  libgiac0  
pn  libgivaro-dev 
pn  libgivaro9
pn  libglpk-dev   
pn  libglpk40 
pn  libgmp-dev
ii  libgmp10  2:6.2.1+dfsg1-1.1
pn  libgmpxx4ldbl 
pn  libgsl-dev
pn  libgsl27  
pn  libhomfly-dev 

Bug#1028023: marked as done (librepo FTBFS on MIPS)

[Adrian Bunk]

On Mon, Jan 09, 2023 at 02:04:22PM +, Holger Levsen wrote:
> control: reopen -1
> thanks
> 
> librepo 1.14.5-2 still fails to build as 1.14.5-1 did, see
> https://buildd.debian.org/status/package.php?p=librepo

I "improved" it by also breaking the build on all other architectures...
:-(

The things that happen when trying to fix a problem you cannot reproduce.

Patch with the missing import added is attached.

> cheers,
>   Holger

Sorry for the mess
Adrian
>From abed2856f5a35c86e03851a94a9e4d92c95c1386 Mon Sep 17 00:00:00 2001
From: Adrian Bunk 
Date: Mon, 9 Jan 2023 20:06:46 +0200
Subject: test_yum_package_downloading.py: Don't hardcode a value for
 EOPNOTSUPP

For historical reasons, errno numbers are not the same on all
architectures (compatibility with other operating systems already
available on the same hardware was considered more important than
having the same numbers on all Linux architectures).

Use errno.EOPNOTSUPP instead of hardcoding a number.
---
 tests/python/tests/test_yum_package_downloading.py | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/tests/python/tests/test_yum_package_downloading.py b/tests/python/tests/test_yum_package_downloading.py
index 0364be0..ff74656 100644
--- a/tests/python/tests/test_yum_package_downloading.py
+++ b/tests/python/tests/test_yum_package_downloading.py
@@ -6,6 +6,7 @@ import hashlib
 import unittest
 import tempfile
 import xattr
+import errno
 
 import tests.servermock.yum_mock.config as config
 
@@ -758,7 +759,7 @@ class TestCaseYumPackagesDownloading(TestCaseWithServer):
"user.Librepo.DownloadInProgress".encode("utf-8"),
"".encode("utf-8"))
 except IOError as err:
-if err.errno == 95:
+if err.errno == errno.EOPNOTSUPP:
 self.skipTest('extended attributes are not supported')
 raise
 
-- 
2.30.2

Bug#1028297: python3-freezegun: ships a copy of python3-arrow: /usr/lib/python3/dist-packages/arrow/*.py

[Joe Nahmias]

On Mon, Jan 09, 2023 at 11:59:42AM +0100, Andreas Beckmann wrote:
> Package: python3-freezegun
> Version: 1.2.1-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> during a test with piuparts I noticed your package failed to install
> because it tries to overwrite other packages files.

Actually, it looks like the upstream source tarball for arrow v1.2.1 got
imported into the freezegun salsa repo by mistake -- instead of freezegun
v1.2.1.  The (arrow) code was then subsequently built and uploaded (as
freezegun) -- without noticing the change.

This breaks anything that needs freezegun, as that python module is not
provided by this (version of the) package (anymore).

--Joe

Bug#1028303: dracut-core: missing Breaks+Replaces: dracut-live (<< 059-2)

[Thomas Lange]

Hi Andreas,

should I replace the old Breaks+Replaces with the new ones, or add them?
These are the current for dracut-core:
Breaks: dracut-network (<< 057+157-2)
Replaces: dracut-network (<< 057+157-2)

-- 
regards Thomas

Bug#1027254: dask and pandas 1.5

[Diane Trout]

On Mon, 2023-01-09 at 08:00 +, Rebecca N. Palmer wrote:
> To get the new upstream version to work, dask_sphinx-theme, dask and 
> dask.distributed all need to be updated, in that order.  Tests here:
> https://launchpad.net/~rebecca-palmer/+archive/ubuntu/dask2022p12v2/+packages

Ok thanks for the updates. I'll try to work on it.

As an explanation the dask tests have a dependency on on
dask.distribute being installed. And the easiest way I had to deal with
that was to skip the build time tests in favor of autopkgtests.

Bug#1019799: Proposed MBF: wxwidgets3.2 transition

[gregor herrmann]

On Sun, 08 Jan 2023 16:56:14 -0500, Scott Talbert wrote:

> On Thu, 15 Sep 2022, gregor herrmann wrote:
> > On Thu, 15 Sep 2022 15:13:24 -0400, Scott Talbert wrote:
> > > Thanks for your work so far.  I'll try to take a stab at it...
> > Great, thank you!
> > (The preliminary patch is in git:
> > https://salsa.debian.org/perl-team/modules/packages/libwx-perl )
> 
> I just submitted a PR [1] with a patch to move libwx-perl to wxWidgets 3.2.
> I tested with a few of libwx-perl's rdeps (kephra, unifont-bin, eekboek-gui
> [as much as I could understand it]), and I didn't notice any obvious
> problems.
> 
> [1] 
> https://salsa.debian.org/perl-team/modules/packages/libwx-perl/-/merge_requests/1

Thank you very much!

Merged, and libalien-wxwidgets-perl and libwx-perl uploaded to
unstable.


Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#1016963: Please test u-boot for rpi_4 rpi_4_32b

[Sjoerd Simons]

Hey,


On Fri, 2023-01-06 at 16:36 +0100, Andreas Henriksson wrote:
> On Tue, Jan 03, 2023 at 11:56:51PM +0100, Andreas Henriksson wrote:
> > On Tue, Jan 03, 2023 at 11:46:31PM +0100, Andreas Henriksson wrote:
> > > On Wed, Dec 28, 2022 at 04:11:04PM -0800, Vagrant Cascadian
> > > wrote:
> > > > rpi_4
> > > > rpi_4_32b
> [...]
> 
> Hello again,
> 
> While I only have the earliest rpi 4B rev A0 (1.1) it has come to
> my attention that apparently there's a revision C0 (1.4) that
> has problems booting with u-boot.
> 
> Apparently in 1.4 revision they changed the hardware in
> an incompatible way and then cover this up by having the
> proprietary firmware modify the dtb in ram to change nodes
> as needed.


Yes that revision has a newer version of the SoC same/similar as in the
rpi 400


> The issue has been discussed on the rpi forums:
> https://forums.raspberrypi.com/viewtopic.php?t=315662
> 
> There has been seemingly two indenpendent attempts at submitting
> (very similar) patches upstream to adress this in u-boot:
> https://lists.denx.de/pipermail/u-boot/2021-November/468322.html
> https://lists.denx.de/pipermail/u-boot/2021-September/462020.html
> ... but apparently they've never been merged.

Fwiw this came up on the u-boot list again today: 
  https://lists.denx.de/pipermail/u-boot/2023-January/504038.html

Lets see if things move forward this year..


Fwiw the latest upstream attempt i saw was Antoine's patch series:
  https://lists.denx.de/pipermail/u-boot/2022-August/491455.html

Which resent my patch + added some additional tweaks. 



> 
> NixOS are carrying patches:
> https://github.com/NixOS/nixpkgs/tree/master/pkgs/misc/uboot
> which includes some revision of Sjoerds patch.
> 
> Some info on board revisions can be found at:
> https://www.raspberrypi-spy.co.uk/2012/09/checking-your-raspberry-pi-board-version/
> 
> This issue probably deserves it's own separate bug report,
> but since I don't have the hardware in question I'm leaving that
> to who ever else cares and just share the info I have.
> 
> It might be useful to consider just include NixOS/Sjoerds patch
> or documenting that RPi 4B hw rev 1.4 will not work.
> (Hardware revision is visible in /proc/cpuinfo under the Revision:
> field.)
> However it maybe best trying to find someone who has the affected
> hardware revision that can confirm the problem exists and that
> the patch actually resolves it.

I can confirm both the problem and the patch solving it :)  

-- 
Sjoerd Simons 

Bug#1028333: puppetserver: find an upgrade path from puppet-master

[Louis-Philippe Véronneau]

Package: puppetserver
Severity: grave

At the moment, this package doesn't acknowledge the existence of the 
puppet-master package at all. As such, if the two packages are installed 
on the same machines, important breakage is likely.


A proper upgrade path should be found, to make the transition from 
puppet-master to puppetserver seamless.


--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_0xE1E5457C8BAD4113.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Processed: severity of 1028324 is serious

[Debian Bug Tracking System]

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

> severity 1028324 serious
Bug #1028324 [src:cduce] RM: cduce -- RoQA, unmaintained, FTBFS, zero popcon
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#1028325: RM: myodbc -- RoQA, unmaintained, FTBFS since years

[Tobias Frost]

Source: myodbc
Severity: serious
Justification: QA
User: tobi-rm-proposals@d.o
Usertags: rm-proposal

Dear Maintainer,

- the package has currently 5 RC bugs and FTBFS on all architectures:

#835166 [G|  |  ] [libmyodbc] libmyodbc: SIGFPE, Arithmetic exception in 
sqlchar_as_sqlwchar
#868882 [G|  |  ] [libmyodbc] libmyodbc: The package is not installable in Sid 
due to missing libmysqlclient18 dependency

#849630 [G|M|  ] [libmyodbc] libmyodbc: Programs using it fails with floating 
point exeption, then connects to mariadb
#841561 [S|⛺|  ] [src:myodbc] myodbc: FTBFS: stringutil.c:71:29: error: too few 
arguments to function 'my_malloc'
#852457 [S|  |☣] [src:myodbc] myodbc: switch to build depend on the metapackage 
default-libmysqlclient-dev

- The last upload was 2013 and it has been not in testing since Jan 2017.

- It is not installable in sid (see #868882 above):
  
> The following packages have unmet dependencies:
> libmyodbc : Depends: libmysqlclient18 (>= 5.5.24+dfsg-1) but it is not 
> installable
> E: Unable to correct problems, you have held broken packages.

This makes me wonder if we should retire this package.

If you don't think so, please fix your package.

If you also think that it shoulw be removed, just reassign it to the
ftp.debian.org pseudo package.

If there is no answer, I will reassing the bug for removal in exactly 3 months.

Thanks!
--
tobi

Bug#1023972: Python 3.11 for bookworm?

[Andrius Merkys]

Hi Simon,

On 2023-01-07 13:24, Simon McVittie wrote:

On Sat, 07 Jan 2023 at 10:23:19 +0200, Andrius Merkys wrote:

If I may, I would as well be grateful if someone could give a look at:

#1023972 [src:python-ase] FTBFS with Python 3.11 due to
pathlib.Path.__enter__() deprecation

I have no idea how to fix this and the upstream is silent.

My first thought on seeing this was: why were Path objects a context
manager in the first place? What would that mean?

Looking at the code in python3.10 and python3.11 pathlib, it seems the
reason this is deprecated is indeed that it didn't make sense:

 def __enter__(self):
 # In previous versions of pathlib, __exit__() marked this path as
 # closed; subsequent attempts to perform I/O would raise an IOError.
 # This functionality was never documented, and had the effect of
 # making Path objects mutable, contrary to PEP 428.
 # In Python 3.9 __exit__() was made a no-op.
 # In Python 3.11 __enter__() began emitting DeprecationWarning.
 # In Python 3.13 __enter__() and __exit__() should be removed.
 warnings.warn("pathlib.Path.__enter__() is deprecated and scheduled "
   "for removal in Python 3.13; Path objects as a context "
   "manager is a no-op",
   DeprecationWarning, stacklevel=2)
 return self

 def __exit__(self, t, v, tb):
 pass

So the solution seems to be that if your package contains this:

 with some_path_object:
 do_stuff(some_path_object)

replace it with:

 do_stuff(some_path_object)

and if it contains:

 with Path(...) as my_path:
 do_stuff(my_path)

replace with:

 my_path = Path(...)
 do_stuff(my_path)

I hope that should be a relatively straightforward change.


Thanks a lot for the hint, this indeed worked. Failure in __enter__() 
threw me off tracks, but now I recall how it is related to 'with' 
construction.


Best wishes,
Andrius

Bug#976506: Fix for bullseye

[Santiago Vila]

El 9/1/23 a las 16:25, Nilesh Patra escribió:

I would make an upload proposal in the form of debdiff, but I'm unsure
about backporting the fix in unstable to stable in this case, because
I don't really understand it.


I will not do it, it is not worth the effort. The package is functional, it 
fails a test due to the date being set in 2021, and this fails upstream as well 
as they confirmed it.


Ok, you don't have to do it yourself, as there is also the possibility of NMU
(which I was trying to avoid).

The reason this is necessary in bullseye is that packages in stable *must* 
build in stable.
This was already a release goal for bullseye, it's not a new requirement.

Naturally, if packages start failing after we release bullseye, it follows that
the only way to keep bullseye buildable from source is to fix things as they 
happen.

But again, I will not force anybody to do uploads they don't want to do.

Thanks.

Bug#991067: reopen for bullseye

[Santiago Vila]

reopen 991067
found 991067 1.2-1
found 991067 1.2-4
fixed 991067 1.2-5
thanks

Note: There is already a release.debian.org bug with a debdiff.

Processed: reopen for bullseye

[Debian Bug Tracking System]

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

> reopen 991067
Bug #991067 {Done: Santiago Vila } [src:x4d-icons] 
x4d-icons FTBFS with imagemagick with the #987504 change
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions x4d-icons/1.2-4 and x4d-icons/1.2-5.
> found 991067 1.2-1
Bug #991067 [src:x4d-icons] x4d-icons FTBFS with imagemagick with the #987504 
change
Ignoring request to alter found versions of bug #991067 to the same values 
previously set
> found 991067 1.2-4
Bug #991067 [src:x4d-icons] x4d-icons FTBFS with imagemagick with the #987504 
change
Marked as found in versions x4d-icons/1.2-4.
> fixed 991067 1.2-5
Bug #991067 [src:x4d-icons] x4d-icons FTBFS with imagemagick with the #987504 
change
Marked as fixed in versions x4d-icons/1.2-5.
> thanks
Stopping processing here.

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

Bug#1028323: RM: vdr-plugin-remoteosd -- RoQA, unmaintained, FTBFS, dead upstream, low popcon

[Tobias Frost]

Source: vdr-plugin-remoteosd
Severity: serious
Justification: QA
User: tobi-rm-proposals@d.o
Usertags: rm-proposal

Dear Maintainer,

- the package has currently 1 RC (FTBFS) bug on all architectures:

#872495 [S|⛺|  ] [src:vdr-plugin-remoteosd] vdr-plugin-remoteosd FTBFS with vdr 
2.3.8

- It is even not installable in sid:

$apt install vdr-plugin-remoteosd
(…)
The following packages have unmet dependencies:
 vdr-plugin-remoteosd : Depends: vdr-abi-2.2.0-debian
E: Unable to correct problems, you have held broken packages.


- The last upload was 2015.

- Upstream disappeared and

- popcon is "1".

- There are no r-depends on the package.


This makes me wonder if we should retire this package.

If you don't think so, please fix your package.

If you also think that it shoulw be removed, just reassign it to the
ftp.debian.org pseudo package.

If there is no answer, I will reassing the bug for removal in exactly 3 months.

Thanks!
--
tobi

Bug#1028249: marked as done (warzone2100: Missing build dependency on libopus-dev)

[Debian Bug Tracking System]

Your message dated Mon, 09 Jan 2023 15:27:05 +
with message-id 
and subject line Bug#1028249: fixed in warzone2100 4.3.3-2
has caused the Debian Bug report #1028249,
regarding warzone2100: Missing build dependency on libopus-dev
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=warzone2100=ppc64el=4.3.3-1=1673202563=0

...
CMake Error at 
/usr/share/cmake-3.25/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
  Could NOT find Opus (missing: OPUS_LIBRARY OPUS_INCLUDE_DIR)
Call Stack (most recent call first):
  /usr/share/cmake-3.25/Modules/FindPackageHandleStandardArgs.cmake:600 
(_FPHSA_FAILURE_MESSAGE)
  cmake/FindOpus.cmake:23 (find_package_handle_standard_args)
  lib/sound/CMakeLists.txt:25 (find_package)


-- Configuring incomplete, errors occurred!
--- End Message ---
--- Begin Message ---
Source: warzone2100
Source-Version: 4.3.3-2
Done: Russell Coker 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 09 Jan 2023 21:43:32 +1100
Source: warzone2100
Architecture: source
Version: 4.3.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Russell Coker 
Closes: 1027722 1028249
Changes:
 warzone2100 (4.3.3-2) unstable; urgency=medium
 .
   * Added build-depends on libopus-dev Closes: #1028249
   * Added build-depends on libshaderc-dev and glslc to add Vulkan
 Closes: #1027722
   * Changed the datadir patch to have priority 5 to allow mods to work,
 addressed an issue mentioned in bug 1000302 but doesn't fix it
   * Removed the debian/clean entries for LEXX generated files because we
 can't regenerate them at this time, see bug 1000301
 This means you can run dpkg-buildpackage twice without a strange LEXX
 related build failure
Checksums-Sha1:
 37dc8b2ecbf499ca239ab34085ae23d9da835d50 2687 warzone2100_4.3.3-2.dsc
 b240783d0c42a1c1372ac7b15c25fc5b4c2a6d5f 25992 
warzone2100_4.3.3-2.debian.tar.xz
 33e849fc3bfd5d9de01b81e56506d6f83ec0f4c1 16405 
warzone2100_4.3.3-2_amd64.buildinfo
Checksums-Sha256:
 ade30f4a8e15201165910966cf72e8e07e42865ddbefe473324255636d9d 2687 
warzone2100_4.3.3-2.dsc
 a428b48bcce373c19430d224f91624e426cde73254573dc6288509b10c96ff47 25992 
warzone2100_4.3.3-2.debian.tar.xz
 4c926b3ab0659b1669e1886cf21e9b98b567c025c184ca7689319ba8e7b2 16405 
warzone2100_4.3.3-2_amd64.buildinfo
Files:
 0e348506a4df976d5fdef31f68cf8964 2687 games optional warzone2100_4.3.3-2.dsc
 af833776d5dc71a4434259097ca288dd 25992 games optional 
warzone2100_4.3.3-2.debian.tar.xz
 ce86d8265b53a7c53eaa001982807363 16405 games optional 
warzone2100_4.3.3-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEn31hncwG9XwCqmbH0UHNMPxLj3kFAmO8KoAACgkQ0UHNMPxL
j3m6RA/9HrHi43ZNQzmTgws7CjWAeJOH2Kg8CzWu70KWLk5rpa35uKuhc+Su6BaG
MqbsCAJ3P1SANa/jj8jkCtCMyTOwkJrMO9MPme10qvAJ6jkPzjHqya9PdKTRT+WY
32XakxoMbFHOKeP8iSjQnawbzZ5JF96Gvw0UKyOwFWVSYLCyZVKN7/wU122cs2d6
VD6E4b3tt5Gvueqh4cBJ0fpybLhtQqXQZg8H+QgkSXw7K35D6DnNUW+x/OG1mJI1
xtYY9q0vTnwk6+vHlU/BXi6IymNC7jXlyjSQz/X4y+UJCuF7Sa8fyJkkAPGQkYDL
OLGfTDs8OBrs83njJ/ORCfanmfk+Fm2hMFtNTNR0eFyNCymx5CROmCayM+z2d0TI
IOng1GlgF83EK9IbecaSWa3bkA8qVs+hYMXpcpkI10v4n1N3A9n7rUrSj6SJpUK+
mDeJBYnTiBjNRb73z2tWKqof5KgpBiIkxepdfExC3tE3kYK/PlWFiT/K/xSwYi/m
9lFHSsJayOuA7JyfWeDwLp6dcC8JIiPITULzJ9Oa1LLXPNbIHivlRMP48mhme2mj
RCWfgTLSP/gqkh0h1tMkWAUg5fsQtJIpHWKMam43IlSm0wMhjsVMPUzWWr5s05nK
/nb7feGIc/SSuBlhqkS5Pyc96q4HZZFFYzhO3llKDnKFJPt/V2A=
=25o4
-END PGP SIGNATURE End Message ---

Bug#997183: marked as done (meterec: FTBFS: display.c:474:9: error: format not a string literal and no format arguments [-Werror=format-security])

[Debian Bug Tracking System]

Your message dated Mon, 09 Jan 2023 15:24:28 +
with message-id 
and subject line Bug#997183: fixed in meterec 0.9.3-2
has caused the Debian Bug report #997183,
regarding meterec: FTBFS: display.c:474:9: error: format not a string literal 
and no format arguments [-Werror=format-security]
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.)


-- 
997183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997183
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: meterec
Version: 0.9.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/opus 
>   -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600  -Wall  -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -I/usr/include/opus   -D_DEFAULT_SOURCE 
> -D_XOPEN_SOURCE=600  -c -o display.o display.c
> display.c: In function ‘display_tiny_meter’:
> display.c:474:9: error: format not a string literal and no format arguments 
> [-Werror=format-security]
>   474 | wprintw(win, blink + 2*pos);
>   | ^~~
> display.c: In function ‘display_ports’:
> display.c:1370:46: warning: zero-length gnu_printf format string 
> [-Wformat-zero-length]
>  1370 | wprintw(win, "");
>   |  ^~
> gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/opus 
>   -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600  -Wall  -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -I/usr/include/opus   -D_DEFAULT_SOURCE 
> -D_XOPEN_SOURCE=600  -c -o queue.o queue.c
> gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/opus 
>   -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600  -Wall  -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -I/usr/include/opus   -D_DEFAULT_SOURCE 
> -D_XOPEN_SOURCE=600  -c -o keyboard.o keyboard.c
> gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/opus 
>   -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600  -Wall  -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -I/usr/include/opus   -D_DEFAULT_SOURCE 
> -D_XOPEN_SOURCE=600  -c -o session.o session.c
> gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/opus 
>   -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600  -Wall  -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -I/usr/include/opus   -D_DEFAULT_SOURCE 
> -D_XOPEN_SOURCE=600  -c -o disk.o disk.c
> session.c: In function ‘session_callback’:
> session.c:61:9: warning: ‘jack_session_reply’ is deprecated 
> [-Wdeprecated-declarations]
>61 | jack_session_reply( meterec->client, event );
>   | ^~
> In file included from session.c:33:
> /usr/include/jack/session.h:204:5: note: declared here
>   204 | int jack_session_reply (jack_client_t*client,
>   | ^~
> session.c:64:17: warning: ‘jack_session_event_free’ is deprecated 
> [-Wdeprecated-declarations]
>64 | jack_session_event_free(event);
>   | ^~~
> In file included from session.c:33:
> /usr/include/jack/session.h:217:6: note: declared here
>   217 | void jack_session_event_free (jack_session_event_t *event) 
> JACK_OPTIONAL_WEAK_DEPRECATED_EXPORT;
>   |  ^~~
> session.c:68:9: warning: ‘jack_session_event_free’ is deprecated 
> [-Wdeprecated-declarations]
>68 | jack_session_event_free (event);
>   | ^~~
> In file included from session.c:33:
> /usr/include/jack/session.h:217:6: note: declared here
>   217 | void jack_session_event_free (jack_session_event_t *event) 
> JACK_OPTIONAL_WEAK_DEPRECATED_EXPORT;
>   |  ^~~
> gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/opus 
>   -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600  -Wall  -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -I/usr/include/opus   -D_DEFAULT_SOURCE 
> -D_XOPEN_SOURCE=600  -c -o meterec.o meterec.c
> meterec.c: In function ‘main’:
> meterec.c:1302:9: warning: ‘jack_set_session_callback’ is deprecated 
> [-Wdeprecated-declarations]
>  1302 | jack_set_session_callback(meterec->client, session_callback, 
> 

Bug#1026719: marked as done (vmg: FTBFS: /usr/bin/ld.bfd: cannot find -latk-1.0: No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 09 Jan 2023 15:23:53 +
with message-id 
and subject line Bug#1026718: fixed in lazpaint 7.2.2-2
has caused the Debian Bug report #1026718,
regarding vmg: FTBFS: /usr/bin/ld.bfd: cannot find -latk-1.0: No such file or 
directory
to be marked as done.

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

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


-- 
1026718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026718
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vmg
Version: 3.7.1-7
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 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 '/<>'
> /usr/bin/i686-w64-mingw32-windres fpcmagnifier.rc fpcmagnifier.res
> /usr/bin/i686-w64-mingw32-windres magnifier.rc magnifier.res
> lazres startform.lrs startform.lfm
> startform.lfm ResourceName='TvStartWindow' Type='FORMDATA'
> fpc -S2cgi -O1 -gl -vewnhi -l \
>   -Fu/usr/lib/lazarus/default/lcl/units/x86_64-linux/ \
>   -Fu/usr/lib/lazarus/default/lcl/units/x86_64-linux/gtk2/ \
>   -Fu/usr/lib/lazarus/default/packager/units/x86_64-linux/ \
>   -Fu/usr/lib/lazarus/default/components/lazutils/lib/x86_64-linux/ \
>   -Fu. -o./vmg -dLCL -dLCLgtk2 magnifier.dpr
> Hint: Start of reading config file /etc/fpc.cfg
> Hint: End of reading config file /etc/fpc.cfg
> Free Pascal Compiler version 3.2.2+dfsg-17 [2022/11/27] for x86_64
> Copyright (c) 1993-2021 by Florian Klaempfl and others
> Target OS: Linux for x86-64
> Compiling magnifier.dpr
> Compiling glass.pas
> Compiling constants.pas
> Compiling appsettings.pas
> Compiling translationsvmg.pas
> appsettings.pas(70,28) Hint: Parameter "Sender" not used
> appsettings.pas(71,20) Hint: Parameter "Sender" not used
> appsettings.pas(248,3) Note: Local variable "APath" not used
> appsettings.pas(249,3) Note: Local variable "LocalConfigFile" not used
> appsettings.pas(250,3) Note: Local variable "attrs" not used
> glass.pas(205,3) Note: Local variable "buffer" not used
> glass.pas(206,3) Note: Local variable "memstream" not used
> glass.pas(483,3) Note: Local variable "c" not used
> glass.pas(484,3) Note: Local variable "srcRect" not used
> glass.pas(484,12) Note: Local variable "destRect" not used
> glass.pas(486,3) Note: Local variable "lCurWindow" not used
> glass.pas(486,15) Note: Local variable "lVMGWindow" not used
> glass.pas(487,3) Note: Local variable "lCurWindowText" not used
> glass.pas(488,3) Note: Local variable "i" not used
> glass.pas(490,3) Note: Local variable "bmpRetinaDisplay" not used
> glass.pas(93,33) Hint: Parameter "DestCanvas" not used
> glass.pas(658,3) Note: Local variable "dwROP" is assigned but never used
> glass.pas(770,3) Note: Local variable "i" not used
> glass.pas(770,6) Note: Local variable "MinWidth" not used
> glass.pas(770,16) Note: Local variable "MinHeight" not used
> glass.pas(775,9) Note: Local variable "stepMinor" is assigned but never used
> glass.pas(775,20) Note: Local variable "tickSize" is assigned but never used
> glass.pas(775,30) Note: Local variable "tickCount" not used
> glass.pas(916,3) Note: Local variable "I" not used
> glass.pas(986,47) Hint: Local variable "DrawInfo" does not seem to be 
> initialized
> glass.pas(112,31) Hint: Parameter "DC" not used
> Compiling app.pas
> Compiling plugins.pas
> Compiling plugininfo.pas
> app.pas(113,15) Warning: An inherited method is hidden by "ShowHelp(TObject);"
> Compiling about.pas
> about.pas(63,24) Hint: Parameter "Sender" not used
> Compiling configdlg.pas
> configdlg.pas(62,24) Hint: Parameter "Sender" not used
> configdlg.pas(63,25) Hint: Parameter "Sender" not used
> configdlg.pas(63,46) Hint: Parameter "Action" not used
> configdlg.pas(35,54) Hint: Unit "constants" not used in configdlg
> configdlg.pas(77,3) Hint: Unit "glass" not used in configdlg
> app.pas(106,26) Hint: Parameter "Sender" not used
> app.pas(94,27) Hint: Parameter "Sender" not used
> app.pas(184,3) Note: Local variable "lResult" not used
> app.pas(521,3) Note: Local variable "OSVersion" not used
> app.pas(123,38) Hint: Parameter "Sender" not used
> app.pas(124,32) Hint: Parameter "AID" not used
> app.pas(108,25) Hint: Parameter "Sender" not used
> app.pas(108,42) Hint: Parameter "Shift" not used
> app.pas(108,62) Hint: Parameter "X" not used
> app.pas(108,65) Hint: Parameter "Y" not used
> app.pas(109,30) Hint: Parameter "uID" not used
> app.pas(114,28) Hint: Parameter "Sender" not used
> app.pas(115,36) Hint: Parameter "Sender" not used
> app.pas(107,24) Hint: 

Bug#976506: Fix for bullseye

[Nilesh Patra]

On 9 January 2023 8:11:11 pm IST, Santiago Vila  wrote:
>reopen 976506
>found 976506 1.7.2-1
>found 976506 1.7.2-2
>fixed 976506 2.0.1-1
>thanks
>
>Hi. Please consider fixing this in stable as well,
>as packages in stable must build in stable.
>
>If you have never done an upload for stable, the procedure
>is documented here:
>
>https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#special-case-uploads-to-the-stable-and-oldstable-distributions
>
>I would make an upload proposal in the form of debdiff, but I'm unsure
>about backporting the fix in unstable to stable in this case, because
>I don't really understand it.

I will not do it, it is not worth the effort. The package is functional, it 
fails a test due to the date being set in 2021, and this fails upstream as well 
as they confirmed it.

Thanks.

Bug#1028321: RM: vdr-plugin-infosatepg -- RoQA, unmaintained, FTBFS, dead upstream, low popcon

[Tobias Frost]

Source: vdr-plugin-infosatepg
Severity: serious
Justification: QA
User: tobi-rm-proposals@d.o
Usertags: rm-proposal

Dear Maintainer,

- the package has currently 1 RC (FTBFS) bug on all architectures:

#872487 [S|⛺|  ] [src:vdr-plugin-infosatepg] vdr-plugin-infosatepg FTBFS with 
vdr 2.3.8

- It is even not installable in sid:

$apt install vdr-plugin-infosatepg
(…)
The following packages have unmet dependencies:
 vdr-plugin-infosatepg : Depends: vdr-abi-2.2.0-debian
E: Unable to correct problems, you have held broken packages.


- The last upload was 2015.

- Upstream disappeared and

- popcon is "1".

- There are no r-depends on the package.


This makes me wonder if we should retire this package.

If you don't think so, please fix your package.

If you also think that it shoulw be removed, just reassign it to the
ftp.debian.org pseudo package.

If there is no answer, I will reassing the bug for removal in exactly 3 months.

Thanks!
-- 
tobi

Bug#1028166: marked as done (commons-configuration: Build-depends on NBS package about to FTBFS)

[Debian Bug Tracking System]

Your message dated Mon, 09 Jan 2023 15:20:19 +
with message-id 
and subject line Bug#1028166: fixed in commons-configuration 1.10-6
has caused the Debian Bug report #1028166,
regarding commons-configuration: Build-depends on NBS package about to FTBFS
to be marked as done.

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

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


-- 
1028166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028166
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: commons-configuration
Version: 1.10-5
Severity: serious
Tags: ftbfs
Justification: fails to build from source


* source package commons-vfs version 2.1-4 no longer builds
  binary package(s): libcommons-vfs-java-doc
  on all
  - broken Build-Depends:
commons-configuration: libcommons-vfs-java-doc

Once libcommons-vfs-java-doc is decrufted, this package will not longer
build.

Scott K
--- End Message ---
--- Begin Message ---
Source: commons-configuration
Source-Version: 1.10-6
Done: tony mancill 

We believe that the bug you reported is fixed in the latest version of
commons-configuration, 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.
tony mancill  (supplier of updated commons-configuration 
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, 08 Jan 2023 08:47:11 -0800
Source: commons-configuration
Architecture: source
Version: 1.10-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: tony mancill 
Closes: 1028166
Changes:
 commons-configuration (1.10-6) unstable; urgency=medium
 .
   * Team upload.
   * Drop libcommons-configuration-java-doc package (Closes: #1028166)
   * Remove build-dep on libmaven-javadoc-plugin-java
   * Use debhelper-compat (=13)
   * Replace libservlet3.1-java with libservlet-api-java
   * Add liblog4j1.2-java to build-deps
   * Update Homepage URL
   * Freshen years in debian/copyright
   * Include Apache NOTICE.txt in binary package documentation
   * Update Vcs URLs to point to Salsa
   * Remove get-orig-source target from debian/rules
   * Bump Standards-Version to 4.6.2
   * Set Rules-Requires-Root: no in debian/control
   * Update debian/watch URL and version
Checksums-Sha1:
 66989ef6744218aa659341bd76d9177d8e1bc9a8 2641 commons-configuration_1.10-6.dsc
 02d542259fe69a625c65e199f7864a1593884425 4888 
commons-configuration_1.10-6.debian.tar.xz
 126eb8a2d59ec7d09e4ab34a75531456b375c60b 16856 
commons-configuration_1.10-6_amd64.buildinfo
Checksums-Sha256:
 114202ed90a0faa16442ed8c3305c4ee7fb5b7d0c35e0bc71d56f2cc1e906148 2641 
commons-configuration_1.10-6.dsc
 6efabff00ba679e2f3a32569bf5d0b4481d67acc470c6d54af39cd8f9ce3e7e3 4888 
commons-configuration_1.10-6.debian.tar.xz
 92f0a2591fc35c3618ddab205e2088c2258f007b89f35b65db0e996e11ef1780 16856 
commons-configuration_1.10-6_amd64.buildinfo
Files:
 d52aebe92c40bf7fe4a802e5d4bd2cbd 2641 java optional 
commons-configuration_1.10-6.dsc
 452937f2a6b85c0e9ac142f727e307d7 4888 java optional 
commons-configuration_1.10-6.debian.tar.xz
 563196830bb6848ca85bd44d203a4d14 16856 java optional 
commons-configuration_1.10-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAmO8KjsUHHRtYW5jaWxs
QGRlYmlhbi5vcmcACgkQIdIFiZdLPpZ4KQ//Yi7eJzdtyp92EcKWZtmM2NyJvJNY
ElfRPwQN7RWFHKIQNsQRkjPriTAatfVE173E+MYYzTQ8FgDhgOwt0XOTFfz0tzwj
vzCV/R4nKrGUgDrr10TtFYa3x9aMTBiela97EHjLfJv5lMVJFV1dpxj4zcBwNc3C
QJnyNKZBkcod92MX0J3BQkXFrlmVAqSnbzdUtqVJg23JzIlxidk75EhO1Z+Gi4LK
Au4TBaoZk08EEoHzL9/0o+ASWf8ARogTelF8V3uzi3pWO+BQpIs4VmmBeDkDmhcp
+89IeWTlLfkIX/5tKyEjzECCrLYYDMohnhflvJ7JVGqa6bMbhucEkST/d01V6qAx
qZm7j+XIoXyRxYSIih2cFpXD5D06sA5QAIUDYzej03NWkp51Rr8D5Adqzg5B+WMk
3ntSHl3iBNW27qz7I9YmDqIgiZJQ90oMRNlP+9yiv+zRNsKlnlclh8O3pMh73sHi
ud2Vm8veDmW0b2BzbRsxDDs+1foq11R8LDXG81SOgd2fIMkYmBCFHCMmBtuzFUy6
VrFCIOoSd9okk9x3Z980KTO0LIoUhMNcKl9T2b8zuKapUjOAUn3EtyTN79LUYbNZ
9MP3RC5BtotDBWVPuMVSwzGTq8xCA2Hh4SiXyvloujn5cK0PQmlvxwVw6tASqfmu
y5J2ra3rRS7d5hI=
=zAJX
-END PGP SIGNATURE End Message ---

Bug#1028298: marked as done (juff-dev: missing Breaks+Replaces: juffed-dev (<< 0.10-89-g3690b60-6))

[Debian Bug Tracking System]

Your message dated Mon, 9 Jan 2023 23:16:31 +0800
with message-id 
and subject line juff-dev: missing Breaks+Replaces: juffed-dev (<< 
0.10-89-g3690b60-6)
has caused the Debian Bug report #1028298,
regarding juff-dev: missing Breaks+Replaces: juffed-dev (<< 0.10-89-g3690b60-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.)


-- 
1028298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028298
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: juff-dev
Version: 0.10-89-g3690b60-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack .../juff-dev_0.10-89-g3690b60-6_amd64.deb ...
  Unpacking juff-dev (0.10-89-g3690b60-6) ...
  dpkg: error processing archive 
/var/cache/apt/archives/juff-dev_0.10-89-g3690b60-6_amd64.deb (--unpack):
   trying to overwrite '/usr/include/juffed/AppInfo.apple.h', which is also in 
package juffed-dev 0.10-89-g3690b60-5+b1
  Errors were encountered while processing:
   /var/cache/apt/archives/juff-dev_0.10-89-g3690b60-6_amd64.deb


cheers,

Andreas


juffed-dev=0.10-89-g3690b60-5+b1_juff-dev=0.10-89-g3690b60-6.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 0.10-89-g3690b60-7


-- 
ChangZhuo Chen (陳昌倬) czchen@{czchen,debian}.org
http://czchen.info/
Key fingerprint = BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


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

Processed: Bug#1023972 marked as pending in python-ase

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1023972 [src:python-ase] python-ase: FTBFS with Python 3.11 due to 
pathlib.Path.__enter__() deprecation
Added tag(s) pending.

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

Bug#1027836: marked as done (planner,planner-data: both ship /usr/share/planner/images/gnome-planner.png)

[Debian Bug Tracking System]

Your message dated Mon, 09 Jan 2023 14:59:10 +
with message-id 
and subject line Bug#1027836: fixed in planner 0.14.91-2
has caused the Debian Bug report #1027836,
regarding planner,planner-data: both ship 
/usr/share/planner/images/gnome-planner.png
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.)


-- 
1027836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027836
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: planner,planner-data
Version: 0.14.91-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your packages failed to install
because they tries to overwrite each others files.

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

  Selecting previously unselected package planner.
  Preparing to unpack .../101-planner_0.14.91-1_amd64.deb ...
  Unpacking planner (0.14.91-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-9JdNac/101-planner_0.14.91-1_amd64.deb (--unpack):
   trying to overwrite '/usr/share/planner/images/gnome-planner.png', which is 
also in package planner-data 0.14.91-1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-9JdNac/101-planner_0.14.91-1_amd64.deb


cheers,

Andreas


planner=0.14.91-1_planner-data=0.14.91-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: planner
Source-Version: 0.14.91-2
Done: Bastian Germann 

We believe that the bug you reported is fixed in the latest version of
planner, 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.
Bastian Germann  (supplier of updated planner 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, 09 Jan 2023 14:33:11 +0100
Source: planner
Architecture: source
Version: 0.14.91-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Bastian Germann 
Closes: 1027836
Changes:
 planner (0.14.91-2) unstable; urgency=medium
 .
   * QA upload
   * Move /usr/share data to -data package (Closes: #1027836)
Checksums-Sha1:
 13df9bfdaf6c86f4cb977e496d2001ea84bf2792 1841 planner_0.14.91-2.dsc
 9d7663176d56f2d9ebfd375dd872f2f84a94ce25 12504 planner_0.14.91-2.debian.tar.xz
 bce0101b732e43a334bf7d706e0480a2d8e3f92b 15168 
planner_0.14.91-2_source.buildinfo
Checksums-Sha256:
 bef887163a7299046424ffd91ed380a1b888727ad68c773b924cee2e2e2dd310 1841 
planner_0.14.91-2.dsc
 e5e47df690ed5273112199fe5f6baea318e08418cead03dc4ddccc39577f4156 12504 
planner_0.14.91-2.debian.tar.xz
 4ee84c069169b1fd51e6a91eb8c31832b6c444801f68a3b720696b86b6ec23b9 15168 
planner_0.14.91-2_source.buildinfo
Files:
 a366ed37bb1950379332751d6b536b0f 1841 gnome optional planner_0.14.91-2.dsc
 a973329a16531151f5b0d814d1dd47c1 12504 gnome optional 
planner_0.14.91-2.debian.tar.xz
 a39951c5065134fc2f23c691dab11138 15168 gnome optional 
planner_0.14.91-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmO8HMUQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFGO/C/4ocavWUnu7XkpKSJEq4b2JTZrrr/vVmht/
cis3uEAq9iLYexkpxeQfjxqseS+5NN91kHgvrgy9McVTEspzJZCcRKPJeS6YLeQp
XFHHM3Ni5EacphUnn5njGx/PRfsyRAvcYXYfXPUYT6ifDVIrKPP48eLCoJ6dNiUv
9Ms8seJOqufCv6xPZzREwbQ6lqb2V7RAfqpXKXScNn8OaiqPa8PZ1Vb+wWCoi+3y
xxJaHCzGML9ifzqq2pfKrOYYdsDA6hG1VG906a9gELQkl83VlTP/Ui8W4ORdy+ez
Jy8f4pc7Crrq1jKN8thgPyoqBVJHW4VYOzTSw6dM9fIq44Fo1AkdVt8lbrnFteBV
iNkf4Hzw+XnmyZxFjLHxrrRVdGDEjyopQ1odxeJuoIRpt6Ng6TZCtLX7sHz36VHo
AubRqyD8R3BFQ14vfoafLv8AELXmwwbjW06hEtOnUtfF035PwYay7LIWJoOHUIdi
CArWbTuIP7ZINKHgZNdQCxPE4tq4rCU=
=TnsP
-END PGP SIGNATURE End Message ---

Bug#1023972: marked as pending in python-ase

[Andrius Merkys]

Control: tag -1 pending

Hello,

Bug #1023972 in python-ase 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/debichem-team/python-ase/-/commit/1ff2e8498eda0fbb3684c3a695f31712e9c93bfa


Add a patch to fix compatibility with Python 3.11 (Closes: #1023972). Thanks 
Simon McVittie.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1023972

Bug#1028169: marked as done (maven-reporting-impl: Build-depends on NBS package, will soon FTBS)

[Debian Bug Tracking System]

Your message dated Mon, 09 Jan 2023 14:57:07 +
with message-id 
and subject line Bug#1028169: fixed in maven-reporting-impl 3.2.0-1
has caused the Debian Bug report #1028169,
regarding maven-reporting-impl: Build-depends on NBS package, will soon FTBS
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.)


-- 
1028169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028169
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: maven-reporting-impl
Version: 3.0.0-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source

* source package doxia version 1.11.1-1 no longer builds
  binary package(s): libdoxia-java-doc
  - broken Build-Depends:
maven-reporting-impl: libdoxia-java-doc

Once libdoxia-java-doc is decrufted, this package will start to FTBFS.

Scott K
--- End Message ---
--- Begin Message ---
Source: maven-reporting-impl
Source-Version: 3.2.0-1
Done: Emmanuel Bourg 

We believe that the bug you reported is fixed in the latest version of
maven-reporting-impl, 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.
Emmanuel Bourg  (supplier of updated maven-reporting-impl 
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, 09 Jan 2023 15:23:01 +0100
Source: maven-reporting-impl
Architecture: source
Version: 3.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Closes: 1028169
Changes:
 maven-reporting-impl (3.2.0-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release
 - Depend on junit4 instead of junit
 - Depend on doxia (>= 1.11)
 - Removed the unused build dependencies
   * Removed the -java-doc package (Closes: #1028169)
   * Standards-Version updated to 4.6.1
   * Switch to debhelper level 13
   * Use salsa.debian.org Vcs-* URLs
   * Track and download the new releases from GitHub
Checksums-Sha1:
 a1eac077109c3ab036af22c4a82d8dcfc7fcae68 2257 maven-reporting-impl_3.2.0-1.dsc
 a8464e3dc4f9d837ab101b4daf033a92e4226cce 16028 
maven-reporting-impl_3.2.0.orig.tar.xz
 40222129bb2aaa3940ca4482cf9dec34065b2565 3896 
maven-reporting-impl_3.2.0-1.debian.tar.xz
 4960489934b008fd323538722fef4365d59269ea 15173 
maven-reporting-impl_3.2.0-1_source.buildinfo
Checksums-Sha256:
 7bb21bb48a65d560472c82c78524bf29fb6f6b441e90786d9533087f81c84919 2257 
maven-reporting-impl_3.2.0-1.dsc
 3baf03fccfe6562405a8a2dae51a42214df087200d626878201b327edbd35191 16028 
maven-reporting-impl_3.2.0.orig.tar.xz
 8a376bd6924ead338022fc40a16e2f3825250661a62bcc69e63fa8a5a5467fbf 3896 
maven-reporting-impl_3.2.0-1.debian.tar.xz
 8a44ab69e4fae9fa54039ae64b8cc0cbb0d2b788487bf370d3a35fc6651c6c8c 15173 
maven-reporting-impl_3.2.0-1_source.buildinfo
Files:
 443d271e38a29125eb5485fa6284e039 2257 java optional 
maven-reporting-impl_3.2.0-1.dsc
 8598f1b515316ede124aa320b1998412 16028 java optional 
maven-reporting-impl_3.2.0.orig.tar.xz
 683aadf4d1a689a1a5a7282e6991fdd5 3896 java optional 
maven-reporting-impl_3.2.0-1.debian.tar.xz
 080c97be0c95dcadbca64771290fca3e 15173 java optional 
maven-reporting-impl_3.2.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAmO8JAwACgkQ9RPEGeS5
0Kzt1g/+IFe6k4X9f1nI73csjIj4CYr0meRVBWaYq1MjVIiR3BBE95YEFwzP1rcw
S2T8AcopPjP00kN+a72kgWTBCF7ajo+OOR1GoAd3lGDcP03JUmprPY9Hz5b8U+Ea
38hFGDF2WzTo/Iu7bmJQzUBFlBNahZtWv9hKrXhdCVJCp0y+ot+3iCFruspyr1Rf
7OP9WpkvBjfIs9fRHqvPFyBNAbcJboavtDCP+VO0jR7zqCcknBMxMASIzeJwqLlw
QVZJluKPSVJrguMhcDVcTLox/I0BGTmzMmN/n4rmJ1HgBBVt5H/jTz4IbTnr60S8
zcQyZwncNY4Je75hoD1naV0GSFY/3p3qzRqvFbeS6nNi8rp132GHSZMpbvU26GDJ
ybvzEUQsFTEguSN5Whcshpi2e5Oqi/f6s51NOSConKcuM8pRRt9TXv+tiqJM51Ro
007AklX7AUSRQ1kgDQkuK/j3ldDJCNNEJj1s0m4/IodZ+W5zcQeigaUaMASHTHgD
qfv16oOAmJ3Fge5BMRv6gaPpjVadZDyfezLV9cKuUlEgO/4WL2fDJV0pO2k/QoHo
vyaSGKM5scJurGePn05CJ+cYbJsT1QATgcNDI/OVTam8P6FpdA4OjHt9dmTJjKYP
g1pGADQaIec4u1RFajvpgEAlk6ytZpM8v1rjucFSupG6nP7B7FQ=
=hJkG
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#1028111: r-cran-clock: autopkgtest failure on 32bit

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream
Bug #1028111 [src:r-cran-clock] r-cran-clock: autopkgtest failure on 32bit
Added tag(s) upstream.
> forwarded -1 https://github.com/r-lib/clock/issues/312
Bug #1028111 [src:r-cran-clock] r-cran-clock: autopkgtest failure on 32bit
Set Bug forwarded-to-address to 'https://github.com/r-lib/clock/issues/312'.

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

Bug#1028111: r-cran-clock: autopkgtest failure on 32bit

[Andreas Tille]

Control: tags -1 upstream
Control: forwarded -1 https://github.com/r-lib/clock/issues/312

I've forwarded the issue to the upstream issue tracker.

Kind regards
   Andreas.

Am Sat, Jan 07, 2023 at 03:02:04AM +0200 schrieb Adrian Bunk:
> Source: r-cran-clock
> Version: 0.6.1-1
> Severity: serious
> 
> https://tracker.debian.org/pkg/r-cran-clock
> 
> Issues preventing migration:
> ∙ ∙ autopkgtest for r-cran-clock/0.6.1-1: amd64: Pass, arm64: Pass, armel: 
> Regression ♻ , armhf: Regression ♻ , i386: Regression ♻
> 
> 
> ...
> > test_check("clock")
> [ FAIL 2 | WARN 29 | SKIP 252 | PASS 1146 ]
> 
> ══ Skipped tests 
> ═══
> • On CRAN (252)
> 
> ══ Failed tests 
> 
> ── Failure ('test-posixt.R:151'): can group by 
> year/month/day/hour/minute/second ──
> date_group(z, "year") (`actual`) not identical to `expect` (`expected`).
> 
> actual  | expected 
> [1] "-1-12-31 23:56:02" - "0-01-01" [1]
> [2] "0-12-31 23:56:02"  - "1-01-01" [2]
> [3] "1-12-31 23:56:02"  - "2-01-01" [3]
> [4] "2-12-31 23:56:02"  - "3-01-01" [4]
> [5] "3-12-31 23:56:02"  - "4-01-01" [5]
> ── Failure ('test-posixt.R:152'): can group by 
> year/month/day/hour/minute/second ──
> date_group(z, "year", n = 3) (`actual`) not identical to expect[c(1, 1, 1, 4, 
> 4)] (`expected`).
> 
> actual  | expected 
> [1] "-1-12-31 23:56:02" - "0-01-01" [1]
> [2] "-1-12-31 23:56:02" - "0-01-01" [2]
> [3] "-1-12-31 23:56:02" - "0-01-01" [3]
> [4] "2-12-31 23:56:02"  - "3-01-01" [4]
> [5] "2-12-31 23:56:02"  - "3-01-01" [5]
> 
> [ FAIL 2 | WARN 29 | SKIP 252 | PASS 1146 ]
> Error: Test failures
> Execution halted
> autopkgtest [16:10:54]: test run-unit-test: ---]
> autopkgtest [16:10:55]: test run-unit-test:  - - - - - - - - - - results - - 
> - - - - - - - -
> run-unit-testFAIL non-zero exit status 1
> ...
> ___
> R-pkg-team mailing list
> r-pkg-t...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/r-pkg-team

-- 
http://fam-tille.de

Bug#1028129: #1028129: securestring FTBFS: fatal error: Python.h: No such file or directory

[Joost van Baal-Ilić]

Hi,

Bo YU: thanks a lot for your recent work on securestring!  Do you plan
to upload it, or would you prefer me to handle that?  (I have time
to take care of it this week.)

Bye,

Joost

Processed: Fix for bullseye

[Debian Bug Tracking System]

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

> reopen 976506
Bug #976506 {Done: Nilesh Patra } 
[src:conda-package-handling] conda-package-handling: FTBFS in bullseye (failing 
tests)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions conda-package-handling/2.0.1-1.
> found 976506 1.7.2-1
Bug #976506 [src:conda-package-handling] conda-package-handling: FTBFS in 
bullseye (failing tests)
Ignoring request to alter found versions of bug #976506 to the same values 
previously set
> found 976506 1.7.2-2
Bug #976506 [src:conda-package-handling] conda-package-handling: FTBFS in 
bullseye (failing tests)
Ignoring request to alter found versions of bug #976506 to the same values 
previously set
> fixed 976506 2.0.1-1
Bug #976506 [src:conda-package-handling] conda-package-handling: FTBFS in 
bullseye (failing tests)
Marked as fixed in versions conda-package-handling/2.0.1-1.
> thanks
Stopping processing here.

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

Bug#976506: Fix for bullseye

[Santiago Vila]

reopen 976506
found 976506 1.7.2-1
found 976506 1.7.2-2
fixed 976506 2.0.1-1
thanks

Hi. Please consider fixing this in stable as well,
as packages in stable must build in stable.

If you have never done an upload for stable, the procedure
is documented here:

https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#special-case-uploads-to-the-stable-and-oldstable-distributions

I would make an upload proposal in the form of debdiff, but I'm unsure
about backporting the fix in unstable to stable in this case, because
I don't really understand it.

In bullseye the code was like this:

@pytest.mark.skipif(datetime.now() <= datetime(2021, 12, 1), reason="Don't 
understand why this doesn't behave.  Punt.")

and I removed the "if" and the condition (datetime etc) in my proposal
to fix this in unstable.

But now in version 2.0.1-1 I see this:

@pytest.mark.skipif(reason="Don't understand why this doesn't behave.  Punt.")

I believe the "if" thing does not apply here, but I don't know enough python to 
be 100% sure.

Thanks.

Processed: limit source to gnustep-base, tagging 1028189

[Debian Bug Tracking System]

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

> limit source gnustep-base
Limiting to bugs with field 'source' containing at least one of 'gnustep-base'
Limit currently set to 'source':'gnustep-base'

> tags 1028189 + pending
Bug #1028189 [src:gnustep-base] gnustep-base/1.28.1-2 should not migrate to 
testing
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1028023: marked as done (librepo FTBFS on MIPS)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1028023 [src:librepo] librepo FTBFS on MIPS
Bug 1028023 is not marked as done; doing nothing.

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

Processed: voms-api-java: FTBFS in bullseye because of expired certificates

[Debian Bug Tracking System]

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

> reopen 1021551
Bug #1021551 {Done: Mattias Ellert } 
[src:voms-api-java] FTBFS: 11 test failures
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions voms-api-java/3.3.2-4.
> retitle 1021551 voms-api-java: FTBFS in bullseye because of expired 
> certificates in test suite
Bug #1021551 [src:voms-api-java] FTBFS: 11 test failures
Changed Bug title to 'voms-api-java: FTBFS in bullseye because of expired 
certificates in test suite' from 'FTBFS: 11 test failures'.
> found 1021551 3.3.2-1
Bug #1021551 [src:voms-api-java] voms-api-java: FTBFS in bullseye because of 
expired certificates in test suite
Marked as found in versions voms-api-java/3.3.2-1.
> found 1021551 3.3.2-3
Bug #1021551 [src:voms-api-java] voms-api-java: FTBFS in bullseye because of 
expired certificates in test suite
Ignoring request to alter found versions of bug #1021551 to the same values 
previously set
> fixed 1021551 3.3.2-4
Bug #1021551 [src:voms-api-java] voms-api-java: FTBFS in bullseye because of 
expired certificates in test suite
Marked as fixed in versions voms-api-java/3.3.2-4.
> tags 1021551 + ftbfs
Bug #1021551 [src:voms-api-java] voms-api-java: FTBFS in bullseye because of 
expired certificates in test suite
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1028023: marked as done (librepo FTBFS on MIPS)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1028023 {Done: Frédéric Pierret } 
[src:librepo] librepo FTBFS on MIPS
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions librepo/1.14.5-2.

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

Bug#1021551: voms-api-java: FTBFS in bullseye because of expired certificates

[Santiago Vila]

reopen 1021551
retitle 1021551 voms-api-java: FTBFS in bullseye because of expired 
certificates in test suite
found 1021551 3.3.2-1
found 1021551 3.3.2-3
fixed 1021551 3.3.2-4
tags 1021551 + ftbfs
thanks

Hi. I'm reopening because this problem also happens in bullseye,
and packages in stable must build in stable.

I attach an upload proposal to fix this in bullseye, which
is essentially all the things that have been disabled
since version 3.3.2-1 folded into a new 3.3.2-1+deb11u1 version
for stable.

Maybe the item about "Disable tests failing with bouncycastle 1.71"
is not strictly necessary for bullseye, so I'm doubt about that one.

(I tried not to include such item, but it was not completely trivial
because of the interspersed comments in debian/patches/series).

The procedure for a stable upload, if you have not done it before,
is explained here:

https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#special-case-uploads-to-the-stable-and-oldstable-distributions

Thanks.diff --git a/debian/changelog b/debian/changelog
index b928b66..80f45cd 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,13 @@
+voms-api-java (3.3.2-1+deb11u1) bullseye; urgency=medium
+
+  * Disable tests failing with bouncycastle 1.71 (Closes: #1011698)
+  * Disable failing multi-thread test
+  * Disable tests using obsolete hashes (md5/sha1)
+  * Disable tests that fail due to expired certificates (Closes: #1021551)
+  * Disable tests that fail due to more expired certificates
+
+ -- Mattias Ellert   Sat, 31 Dec 2022 19:58:00 
+0100
+
 voms-api-java (3.3.2-1) unstable; urgency=medium
 
   * Update to version 3.3.2 - matches canl-java 2.6.x
diff --git a/debian/copyright b/debian/copyright
index 947c592..5be590f 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -19,7 +19,7 @@ License: Apache-2.0
 
 Files: debian/*
 Copyright:
- 2012-2020, Mattias Ellert 
+ 2012-2022, Mattias Ellert 
 License: Apache-2.0
 
 License: Apache-2.0
diff --git a/debian/patches/series b/debian/patches/series
index 1fd6782..0675e82 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1,13 @@
-# Disable tests using non-local network interface
-voms-api-java-no-local.patch
+# Disable failing tests
+# IllegalState object explicit - implicit expected.
+# https://github.com/italiangrid/voms-api-java/issues/29
+voms-api-java-disable-some-tests.patch
+
+# Disable tests that fail due to expired certificates
+# https://github.com/italiangrid/voms-api-java/issues/30
+# 2022-09-24 (test0.cert.pem, wilco_cnaf_infn_it.cert.pem)
+voms-api-java-expired-2022-09-24.patch
+# 2022-10-08 (test_host_cnaf_infn_it.cert.pem)
+voms-api-java-expired-2022-10-08.patch
+# 2022-12-02 (test_host_2_cnaf_infn_it.cert.pem)
+voms-api-java-expired-2022-12-12.patch
diff --git a/debian/patches/voms-api-java-disable-some-tests.patch 
b/debian/patches/voms-api-java-disable-some-tests.patch
new file mode 100644
index 000..5f2cc99
--- /dev/null
+++ b/debian/patches/voms-api-java-disable-some-tests.patch
@@ -0,0 +1,62 @@
+diff --git a/src/test/java/org/italiangrid/voms/test/ac/TestACGeneration.java 
b/src/test/java/org/italiangrid/voms/test/ac/TestACGeneration.java
+index bc7557c..32ba7a5 100644
+--- a/src/test/java/org/italiangrid/voms/test/ac/TestACGeneration.java
 b/src/test/java/org/italiangrid/voms/test/ac/TestACGeneration.java
+@@ -191,7 +191,7 @@ public class TestACGeneration {
+ return ga;
+   }
+ 
+-  @Test
++  // @Test
+   public void testGeneratedACParsing() throws KeyStoreException,
+ CertificateException, FileNotFoundException, IOException,
+ OperatorCreationException {
+@@ -230,7 +230,7 @@ public class TestACGeneration {
+ 
+   }
+ 
+-  @Test
++  // @Test
+   public void testACValidation() {
+ 
+ ValidationResultChecker c = new ValidationResultChecker(true);
+@@ -247,7 +247,7 @@ public class TestACGeneration {
+ 
+   }
+ 
+-  @Test
++  // @Test
+   public void testLSCValidationFailure() {
+ 
+ ValidationResultChecker c = new ValidationResultChecker(false,
+@@ -264,7 +264,7 @@ public class TestACGeneration {
+ assertEquals(validatedAttrs.size(), 0);
+   }
+ 
+-  @Test
++  // @Test
+   public void testExpiredAACertValidationFailure()
+ throws OperatorCreationException {
+ 
+@@ -284,7 +284,7 @@ public class TestACGeneration {
+ assertEquals(validatedAttrs.size(), 0);
+   }
+ 
+-  @Test
++  // @Test
+   public void testRevokedAACertValidationFailure() {
+ 
+ ValidationResultChecker c = new ValidationResultChecker(false,
+diff --git 
a/src/test/java/org/italiangrid/voms/test/ac/TestFakeVOMSACService.java 
b/src/test/java/org/italiangrid/voms/test/ac/TestFakeVOMSACService.java
+index 6eca55f..49f0498 100644
+--- a/src/test/java/org/italiangrid/voms/test/ac/TestFakeVOMSACService.java
 b/src/test/java/org/italiangrid/voms/test/ac/TestFakeVOMSACService.java
+@@ -54,7 +54,7 @@ public class TestFakeVOMSACService extends TestACSupport {
+ initializeCredentials();
+   }
+ 
+-  @Test
++  // 

Bug#1028023: marked as done (librepo FTBFS on MIPS)

[Holger Levsen]

control: reopen -1
thanks

librepo 1.14.5-2 still fails to build as 1.14.5-1 did, see
https://buildd.debian.org/status/package.php?p=librepo


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

If we'd ban all cars from cities tomorrow, next week we will wonder why we
waited for so long.


signature.asc
Description: PGP signature

Processed: severity

[Debian Bug Tracking System]

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

> severity 1026914 normal
Bug #1026914 [arcanist] arcanist client improperly uploading files
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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

Bug#1027175: marked as done (ceph: Missing adduser dependency for ceph-common and cephadm)

[Debian Bug Tracking System]

Your message dated Mon, 09 Jan 2023 13:54:11 +
with message-id 
and subject line Bug#1027175: fixed in ceph 16.2.10+ds-5
has caused the Debian Bug report #1027175,
regarding ceph: Missing adduser dependency for ceph-common and cephadm
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.)


-- 
1027175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027175
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ceph
Version: 16.2.10+ds-4
Severity: serious
Justification: Policy 7.2. Binary Dependencies
X-Debbugs-Cc: car...@debian.org

Hi

cephadm and ceph-common use adduser in postinst script but do not
declare a Depends on adduser.

There is as well a respective piuparts report uncovering this, cf.
https://piuparts.debian.org/sid/fail/cephadm_16.2.10+ds-4.log .

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: ceph
Source-Version: 16.2.10+ds-5
Done: Thomas Goirand 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 09 Jan 2023 11:41:27 +0100
Source: ceph
Architecture: source
Version: 16.2.10+ds-5
Distribution: unstable
Urgency: medium
Maintainer: Ceph Packaging Team 
Changed-By: Thomas Goirand 
Closes: 1024700 1027151 1027175
Changes:
 ceph (16.2.10+ds-5) unstable; urgency=medium
 .
   [ Thomas Goirand ]
   * Add adduser as depends for cephadm and ceph-common, fixing piupart run
 (Closes: #1027175).
   * CVE-2022-3854: RGW Segmentation fault when requested resource includes a
 colon. Added upstream patches (Closes: #1027151):
 - CVE-2022-3854_1_rgw_Guard_against_malformed_bucket_URLs.patch
 - CVE-2022-3854_2_rgw_Fix_rgw_sal_Bucket_empty_static_method_patch
 .
   [ Charles Plessy ]
   * Replace transition package mime-support with media-types
 (Closes: #1024700).
Checksums-Sha1:
 bf16cea92c288657b1a2fe961c29af7950f99c7d 8082 ceph_16.2.10+ds-5.dsc
 e9424d0ea5903f6445e07b749b5d3cf469b67724 121356 ceph_16.2.10+ds-5.debian.tar.xz
 396f866a98cfca8ec27dbc4f8e850a2ea22d4227 42580 
ceph_16.2.10+ds-5_amd64.buildinfo
Checksums-Sha256:
 716259c664f9847e0075adbfc03c21cd75798ba614362ce13563d443b2902afd 8082 
ceph_16.2.10+ds-5.dsc
 3cd18855db7b542d61886911a1446be6b35b63d46e1445b96b37db142cc72563 121356 
ceph_16.2.10+ds-5.debian.tar.xz
 8208c86531d417f613d782b58abebca93a00f72762f70156572f26c260f5c87d 42580 
ceph_16.2.10+ds-5_amd64.buildinfo
Files:
 553d645a77437bc59b837e3450c9d6f2 8082 admin optional ceph_16.2.10+ds-5.dsc
 978aeacf463bfa896c5ac6262ab90d2a 121356 admin optional 
ceph_16.2.10+ds-5.debian.tar.xz
 34b4342294263ec3f107cf54c8a604d2 42580 admin optional 
ceph_16.2.10+ds-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmO8GQYACgkQ1BatFaxr
Q/6l0hAAlFoZBoPW9ZwrFQmbwbDLmBndrOHbdSH2DQ1C2TkHtualMb1G2LrgYXtL
CcrTHWKdUvWTjgVViFRJbfbsNJ9CdrKOcOveK9Pznbo1hdeFno9iIzBfNqkJMFY8
59xeRxA0HVrax5VmLGaiXiQ5mpnfRGpJZI3a3c128/6DQAx4kV4vdz0oZmgkmvkX
N37exCHjA93PYB4uzXHUpjslUs9dRgJy02RZ+Te38XiXk5mX8T6FqJMqzgh5KyOf
1bpobcx+zCE6NmJxDUZkVWYEHUYIPsNbbBxOhYP3By3sRimVKRz5P0afyxtbJgYp
Bzku+he7MYCXAg4zjjES5Snj2U8I010ZMuJurEXsf0R5DW39PpsQiP1gHFVZsT+B
DxQcrw1C0ptTET0g6MtpHoW0dDXNqVwnMAY5V5ICWRDcDCnK7sGyo19y2Wr+H90P
G5SwfJloWHfzMMppAP0u4rQW/GTvS8tu5cLnArBR2mNhzBROjAvuyBrILLuL9NGs
aU+VGIbRZRFixlUolObKJrck62rnW8bp/IVrm/hlxMalaVhbuuJLEJadkxqrpOvg
2ELEi5DRsBuF0m9bhV5QXHV5h4Zqv0xHrJvoQBV3O9UsLnQKCZx5N3DEith4+DgT
CfVvRtVuZ3Glojj5CaRAetjSo11FfPn/TK62VdMhSeOarjiipy8=
=aZyG
-END PGP SIGNATURE End Message ---

Processed: severity of 942501 is serious

[Debian Bug Tracking System]

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

> severity 942501 serious
Bug #942501 [src:milter-greylist] src:milter-greylist: please drop libbind-dev 
build dependency, it's not in use and libbind-dev is going away
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1011437: Should bind9-libs be shipped in bookworm?

[Ondřej Surý]

> On 9. 1. 2023, at 14:50, Bernhard Schmidt  wrote:
> 
> Hi,
> 
>>> not about src:bind9, building the bind9-libs binary package (yes, this is 
>>> totally confusing, even to Debian tooling)
>> I though that had been already removed: 
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011538 
>> 
>> But I guess something went wrong and perhaps **just** binary bind9-libs was 
>> removed instead.
> 
> Eheehe, this explains 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018016
> 
> Unless you beat me to it, I'll give it another RM stab.


Go ahead, my head is fully in the BIND 9 OpenSSL 3 refactoring review, so I 
could
use less distractions :)

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

Processed: unarchive for bullseye

[Debian Bug Tracking System]

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

> unarchive 1021551
Bug #1021551 {Done: Mattias Ellert } 
[src:voms-api-java] FTBFS: 11 test failures
Unarchived Bug 1021551
> thanks
Stopping processing here.

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

Bug#1011437: Should bind9-libs be shipped in bookworm?

[Bernhard Schmidt]

Hi,

not about src:bind9, building the bind9-libs binary package (yes, this 
is totally confusing, even to Debian tooling)


I though that had been already removed: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011538 



But I guess something went wrong and perhaps **just** binary bind9-libs 
was removed instead.


Eheehe, this explains 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018016


Unless you beat me to it, I'll give it another RM stab.

Bernhard