Bug#1024677: marked as done (protobuf: autopkgtest failure (error: file not found: com/example/tutorial/AddressBookProtos.java))

[Debian Bug Tracking System]

Your message dated Fri, 25 Nov 2022 06:50:42 +
with message-id 
and subject line Bug#1024677: fixed in protobuf 3.21.9-5
has caused the Debian Bug report #1024677,
regarding protobuf: autopkgtest failure (error: file not found: 
com/example/tutorial/AddressBookProtos.java)
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.)


-- 
1024677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024677
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: protobuf
Version: 3.21.9-3
Severity: serious
Tags: upstream patch
Control: block 1023535 by -1

Dear Maintainer,

The autopkgtest for your package is failing:

 autopkgtest [02:27:53]: test simple: [---
 *** Building example programs
 protoc $PROTO_PATH --cpp_out=. --java_out=. --python_out=. addressbook.proto
 pkg-config --cflags protobuf  # fails if protobuf is not installed
 
 c++ -std=c++11 add_person.cc addressbook.pb.cc -o add_person_cpp `pkg-config 
--cflags --libs protobuf`
 pkg-config --cflags protobuf  # fails if protobuf is not installed
 
 c++ -std=c++11 list_people.cc addressbook.pb.cc -o list_people_cpp `pkg-config 
--cflags --libs protobuf`
 javac -cp $CLASSPATH AddPerson.java ListPeople.java 
com/example/tutorial/AddressBookProtos.java
 error: file not found: com/example/tutorial/AddressBookProtos.java
 Usage: javac  
 use --help for a list of possible options
 make: *** [Makefile:66: javac_middleman] Error 2

https://ci.debian.net/data/autopkgtest/unstable/amd64/p/protobuf/28586956/log.gz

The attached patch fixes the issue by correcting the paths in the Makefile.

Kind Regards,

Bas
--- a/examples/Makefile 2022-10-26 19:50:48.0 +0200
+++ b/examples/Makefile 2022-11-23 07:07:29.963242439 +0100
@@ -13,8 +13,8 @@
 
 clean:
rm -f add_person_cpp list_people_cpp add_person_java list_people_java 
add_person_python list_people_python
-   rm -f javac_middleman AddPerson*.class ListPeople*.class 
com/example/tutorial/*.class
-   rm -f protoc_middleman addressbook.pb.cc addressbook.pb.h 
addressbook_pb2.py com/example/tutorial/AddressBookProtos.java
+   rm -f javac_middleman AddPerson*.class ListPeople*.class 
com/example/tutorial/protos/*.class
+   rm -f protoc_middleman addressbook.pb.cc addressbook.pb.h 
addressbook_pb2.py com/example/tutorial/protos/*.java
rm -f *.pyc
rm -f go/tutorialpb/*.pb.go add_person_go list_people_go
rm -f protoc_middleman_dart dart_tutorial/*.pb*.dart
@@ -63,7 +63,7 @@
cd go && go test ./cmd/list_people
 
 javac_middleman: AddPerson.java ListPeople.java protoc_middleman
-   javac -cp $$CLASSPATH AddPerson.java ListPeople.java 
com/example/tutorial/AddressBookProtos.java
+   javac -cp $$CLASSPATH AddPerson.java ListPeople.java 
com/example/tutorial/protos/*.java
@touch javac_middleman
 
 add_person_java: javac_middleman
--- End Message ---
--- Begin Message ---
Source: protobuf
Source-Version: 3.21.9-5
Done: Laszlo Boszormenyi (GCS) 

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

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

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated protobuf 
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: Fri, 25 Nov 2022 07:04:22 +0100
Source: protobuf
Architecture: source
Version: 3.21.9-5
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 1024677
Changes:
 protobuf (3.21.9-5) unstable; urgency=medium
 .
   * Backport upstream fix of Makefile rule for java target in examples
 (closes: #1024677).
Checksums-Sha1:
 2ff059528d2dc464f1912682965dff08e42dd3f4 3067 protobuf_3.21.9-5.dsc
 eef938cb2e097cb76b420f284cf9fa75bc60a783 30824 protobuf_3.21.9-5.debian.tar.xz
Checksums-Sha256:
 b9814d62e96fbc870f4dd32243274a797fc6d22c21ea0a1d26729f86d0d13ce0 3067 
protobuf_3.21.9-5.dsc
 667b078b7b68fbba68bc782bfcf992d74e2619924b70a1fce3f53709a51f9f25 30824 
protobuf_3.21.9-5.debian.tar.xz
Files:
 fac62d14675e46565e0ada160aa77487 3067 devel 

Bug#1023616: marked as done (opensbi: Emulation of fence.tso hangs in endless loop)

[Debian Bug Tracking System]

Your message dated Fri, 25 Nov 2022 06:50:22 +
with message-id 
and subject line Bug#1023616: fixed in opensbi 1.1-2
has caused the Debian Bug report #1023616,
regarding opensbi: Emulation of fence.tso hangs in endless loop
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.)


-- 
1023616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: opensbi
Version: 1.1-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu lunar ubuntu-patch

Dear Maintainer,

  * Fix emulation of fence.tso hanging in endless loop on Allwinner D1
d/p/lib-sbi_illegal_insn-Fix-FENCE.TSO-emulation-infinit.patch
(LP: #1995860)

Thanks for considering the patch.

Best regards

Heinrich

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

Kernel: Linux 5.19.0-21-generic (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru 
opensbi-1.1/debian/patches/lib-sbi_illegal_insn-Fix-FENCE.TSO-emulation-infinit.patch
 
opensbi-1.1/debian/patches/lib-sbi_illegal_insn-Fix-FENCE.TSO-emulation-infinit.patch
--- 
opensbi-1.1/debian/patches/lib-sbi_illegal_insn-Fix-FENCE.TSO-emulation-infinit.patch
   1970-01-01 01:00:00.0 +0100
+++ 
opensbi-1.1/debian/patches/lib-sbi_illegal_insn-Fix-FENCE.TSO-emulation-infinit.patch
   2022-11-07 14:25:01.0 +0100
@@ -0,0 +1,36 @@
+From 111afc12306e4368fa112f97d31ea802c4561294 Mon Sep 17 00:00:00 2001
+From: Rahul Pathak 
+Date: Fri, 12 Aug 2022 19:24:42 +0530
+Subject: [PATCH] lib: sbi_illegal_insn: Fix FENCE.TSO emulation infinite trap
+ loop
+
+In case of missing "FENCE.TSO" instruction implementation,
+opensbi can emulate the "FENCE.TSO" with "FENCE RW,RW", but
+mepc was not incremented to continue from the next instruction
+causing infinite trap.
+
+Fixes: cb8271c8 ("lib: sbi_illegal_insn: Add emulation for fence.tso")
+Signed-off-by: Rahul Pathak 
+Reviewed-by: Andrew Jones 
+Reviewed-by: Xiang W 
+Reviewed-by: Samuel Holland 
+Origin: 
https://github.com/riscv-software-src/opensbi/commit/111afc12306e4368fa112f97d31ea802c4561294
+---
+ lib/sbi/sbi_illegal_insn.c | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/lib/sbi/sbi_illegal_insn.c b/lib/sbi/sbi_illegal_insn.c
+index ecd3508..9691bce 100644
+--- a/lib/sbi/sbi_illegal_insn.c
 b/lib/sbi/sbi_illegal_insn.c
+@@ -40,6 +40,7 @@ static int misc_mem_opcode_insn(ulong insn, struct 
sbi_trap_regs *regs)
+   /* Errata workaround: emulate `fence.tso` as `fence rw, rw`. */
+   if ((insn & INSN_MASK_FENCE_TSO) == INSN_MATCH_FENCE_TSO) {
+   smp_mb();
++  regs->mepc += 4;
+   return 0;
+   }
+ 
+-- 
+2.37.2
+
diff -Nru opensbi-1.1/debian/patches/series opensbi-1.1/debian/patches/series
--- opensbi-1.1/debian/patches/series   1970-01-01 01:00:00.0 +0100
+++ opensbi-1.1/debian/patches/series   2022-11-07 13:18:42.0 +0100
@@ -0,0 +1 @@
+lib-sbi_illegal_insn-Fix-FENCE.TSO-emulation-infinit.patch
--- End Message ---
--- Begin Message ---
Source: opensbi
Source-Version: 1.1-2
Done: Vagrant Cascadian 

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

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

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

Debian distribution maintenance software
pp.
Vagrant Cascadian  (supplier of updated opensbi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 24 Nov 2022 21:45:21 -0800
Source: opensbi
Architecture: source
Version: 1.1-2
Distribution: unstable
Urgency: medium
Maintainer: Vagrant Cascadian 
Changed-By: Vagrant Cascadian 
Closes: 1023616
Changes:
 opensbi (1.1-2) unstable; urgency=medium
 .
   [ Lintian Brush ]
   * Set upstream metadata fields: Bug-Database, 

Bug#1022185: marked as done (nfs-utils: blkmapd crash)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 23:22:09 +
with message-id 
and subject line Bug#1022185: fixed in nfs-utils 1:2.6.2-2
has caused the Debian Bug report #1022185,
regarding nfs-utils: blkmapd crash
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.)


-- 
1022185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022185
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-utils
Version: 1:2.6.2-1+b1
Severity: normal

Dear Maintainer,

Under certain conditions, blkmapd can crash due to calling free() on a
pointer that wasn't malloc()ed. The reproducer I list below using a
debian sid VM went as far as isolating it to having LVM Logical
Volumes on SCSI disks, but this does not exclude other scenarios.

The struct bl_serial *serial structure is allocated via
bl_create_scsi_string() which does a malloc for it, but the code later
on was doing a free() on the data element of this structure and only
then on the structure itself. That first free() is incorrect, as the
data element was never malloc()ed separatedly.

This was first brought up by lixiaokeng via
https://www.spinics.net/lists/linux-nfs/msg87598.html, but not
acknowledged back then.

Here is a reproducer using a VM. It assumes you can add a SCSI disk to
it, which in my steps below is /dev/sdb.

# apt install nfs-kernel-server lvm2
# systemctl stop nfs-blkmapd.service
# pvcreate /dev/sdb
# vgcreate vg0 /dev/sdb
# lvcreate -ntest -L100M vg0
# blkmapd -f
blkmapd: open pipe file /run/rpc_pipefs/nfs/blocklayout failed: No
such file or directory
double free or corruption (out)
Aborted

Note the message about blocklayout is not relevant for this bug.

In gdb:
(gdb) bt
#0  __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at
./nptl/pthread_kill.c:44
#1  0x77c895df in __pthread_kill_internal (signo=6,
threadid=) at ./nptl/pthread_kill.c:78
#2  0x77c3da02 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#3  0x77c28469 in __GI_abort () at ./stdlib/abort.c:79
#4  0x77c7d888 in __libc_message
(action=action@entry=do_abort, fmt=fmt@entry=0x77db66fb "%s\n") at
../sysdeps/posix/libc_fatal.c:155
#5  0x77c9322a in malloc_printerr
(str=str@entry=0x77db9340 "double free or corruption (out)") at
./malloc/malloc.c:5659
#6  0x77c95198 in _int_free (av=0x77df4c60 ,
p=0x55567ad0, have_lock=, have_lock@entry=0) at
./malloc/malloc.c:4583
#7  0x77c978df in __GI___libc_free (mem=) at
./malloc/malloc.c:3386
#8  0x745e in bl_add_disk (filepath=0x7fffd2b0
"/dev/dm-0") at ./utils/blkmapd/device-discovery.c:245
#9  bl_discover_devices () at ./utils/blkmapd/device-discovery.c:276
#10 0x67cd in main (argc=, argv=) at ./utils/blkmapd/device-discovery.c:558

The crash is caused by this erroneous free on a pointer that is not
malloc()ed:  
https://salsa.debian.org/kernel-team/nfs-utils/-/blob/master/utils/blkmapd/device-discovery.c#L245

I sent a ping to upstream again[1], and in Ubuntu for now I'll just
remove the faulty free(serial->data) in the 3 places in that function.


1. 
https://lore.kernel.org/linux-nfs/CANYNYEG=utJ2pe+FtMWh8O+dz63R2wbzOC7ZVrvoqD=u04w...@mail.gmail.com/T/#u
--- End Message ---
--- Begin Message ---
Source: nfs-utils
Source-Version: 1:2.6.2-2
Done: Salvatore Bonaccorso 

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

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

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated nfs-utils package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 24 Nov 2022 23:42:20 +0100
Source: nfs-utils
Architecture: source
Version: 1:2.6.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian kernel team 
Changed-By: Salvatore Bonaccorso 
Closes: 1022185
Changes:
 nfs-utils (1:2.6.2-2) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Update lintian override info to new format on line 2.
 .
   [ Salvatore Bonaccorso ]
   * blkmapd: fix coredump in bl_add_disk (Closes: #1022185)

Processed: closing 714736

[Debian Bug Tracking System]

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

> close 714736
Bug #714736 [nfs-common] thunar: GUI freeze while moving to trash a file from a 
NFS4+Kerberos mount
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 743626

[Debian Bug Tracking System]

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

> close 743626
Bug #743626 [nfs-kernel-server] nfs-kernel-server doesn't startup reliable. 
Needs 'reload' or 'restart' in order to work
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 758544

[Debian Bug Tracking System]

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

> close 758544
Bug #758544 [nfs-kernel-server] nfsdrpc.nfsd: writing fd to kernel failed: 
errno 13 (Permission denied)
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 821267

[Debian Bug Tracking System]

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

> close 821267
Bug #821267 [nfs-kernel-server] nfs-kernel-server: NFSD stops X from getting 
started
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 832513

[Debian Bug Tracking System]

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

> close 832513
Bug #832513 [nfs-common] [nfs-common] nfs-idmapd.service fails unless package 
is installed nfs-kernel-server
Bug #832514 [nfs-common] [nfs-common] nfs-idmapd.service fails unless package 
is installed nfs-kernel-server
Bug #858274 [nfs-common] nfs-common: Unable to enable /usr/sbin/rpc.idmapd and 
NFS client on Debian 9
Marked Bug as done
Marked Bug as done
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#864398: marked as done (nfs-common: can't mount nfs3 after updating to nfs-common 1:1.3.4-2.1)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 23:46:23 +0100
with message-id 
and subject line Re: Bug#864398: nfs-common: can't mount nfs3 after updating to 
nfs-common 1:1.3.4-2.1
has caused the Debian Bug report #864398,
regarding nfs-common: can't mount nfs3 after updating to nfs-common 1:1.3.4-2.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.)


-- 
864398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864398
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-common
Version: 1:1.3.4-2.1
Severity: important

Dear Maintainer,

It looks like something somewhat recent in testing broke the nfs3 client.

   * What led up to the situation?

 After updating from stable to testing, I could not mount nfs3
 shares.  Typical results were pretty opaque:

   $ mount /mnt/shared
   mount.nfs: mount system call failed

 There is no firewall; iptables -L shows no rules at all.  It
 appears that rpcbind and rpc.statd are both running.  The nfs
 server works for other clients, and worked for this client before
 updating.

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

 While looking for relevant bugs, I found mentions of
 systemd-related problems, including nfs-common.service being
 masked (which it was).

 First I asked apt to downgrade nfs-common and rpcbind to the stable
 version, but it complained it would need to remove systemd.  So I
 found some intermediate-version systemd packages cached on another
 host and downgraded to match what it has.

 To get nfs3 working again, I downgraded several packages:
   downgrading systemd from 232-25 to 229-4
   downgrading libsystemd0:amd64 from 232-25 to 229-4
   downgrading udev from 232-25 to 229-4
   downgrading libudev1:amd64 from 232-25 to 229-4
   downgrading libpam-systemd:amd64 from 232-25 to 229-4
   downgrading rpcbind from 0.2.3-0.6 to 0.2.1-6.1
   downgrading nfs-common from 1:1.3.4-2.1 to 1:1.2.8-9

 Since these had to be downgraded as a set, I'm not sure exactly
 which package(s) are responsible.  It also doesn't narrow down the
 nature of the error, but it does at least reduce things to a
 specific range of versions.  I don't see packages available for
 intermediate versions though, so I haven't found a more specific
 revision to check.

   * What was the outcome of this action?

 Upgrading from stable (jessie) to testing broke nfs3; I couldn't
 mount remote filesystems from /etc/fstab or from a command line.

 Downgrading a few packages back to stable (or an earlier version
 from testing, in some cases) got nfs3 working again.

   * What outcome did you expect instead?

 In general, nfs is something which usually "just works", using the
 following steps:

 - Do a minimal install.
 - (optional) add debian/testing to sources.list and
  apt upgrade/dist-upgrade to it
 - apt install nfs-common
 - mkdir /mnt/path ; mount server:/path /mnt/path

 Something in testing is breaking this use case.
 I'm sorry I don't have more specifics...


The information below is from after I got it working.


-- Package-specific info:
-- rpcinfo --
   program vers proto   port  service
104   tcp111  portmapper
103   tcp111  portmapper
102   tcp111  portmapper
104   udp111  portmapper
103   udp111  portmapper
102   udp111  portmapper
1000241   udp  33146  status
1000241   tcp  50201  status
-- /etc/default/nfs-common --
NEED_STATD=yes
STATDOPTS=
NEED_IDMAPD=
NEED_GSSD=
-- /etc/idmapd.conf --
[General]
Verbosity = 0
Pipefs-Directory = /run/rpc_pipefs
[Mapping]
Nobody-User = nobody
Nobody-Group = nogroup
-- /etc/fstab --
nas:/volume1/shared /mnt/shared nfs 
user,nolock,intr,rsize=8192,wsize=8192,exec 0 0
-- /proc/mounts --
nas:/volume1/shared /mnt/shared nfs 
rw,nosuid,nodev,relatime,vers=3,rsize=8192,wsize=8192,namlen=255,hard,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.5.5.4,mountvers=3,mountport=892,mountproto=udp,local_lock=all,addr=10.5.5.4
 0 0

-- System Information:
Debian Release: 9.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C 
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via 

Bug#977904: marked as done (nfs-common: start-statd calls 'systemctl start rpc-statd' which can hang dbus-daemon/systemd at boot)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 23:38:43 +0100
with message-id 
and subject line Re: Bug#977904: nfs-common: start-statd calls 'systemctl start 
rpc-statd' which can hang dbus-daemon/systemd at boot
has caused the Debian Bug report #977904,
regarding nfs-common: start-statd calls 'systemctl start rpc-statd' which can 
hang dbus-daemon/systemd at boot
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.)


-- 
977904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977904
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-common
Version: 1:1.3.4-2.1+deb9u1
Severity: important

Dear Maintainer,

FYI: /usr/share/bug/nfs-common/script warns of error.
  in my case:  'cat /etc/fstab|grep nfs >&3' returns 1 due to 'grep'
  fail (my nfs is all in autofs).  should probably '|| true' that.
  to avoid user confusion in bugreport.  same for other grep statements.

Note:
  This is a doozy -- a whole tower of fail (some my fault for
  implementing an earlier workaround for nfs deadlocks and forgetting
  it was there). So i'm not sure what package to report it against, but
  the core trigger is in /usr/sbin/start-statd so starting there. Yes,
  my system is likely configured in a pretty non-standard way, having
  an /etc/nfsmount.conf forcing nfsv3 to avoid a deadlock in earlier
  systems coming back to bite me as a deadlock in the future :-(

  other subsystems involved:
- systemd
- dbus-daemon
- autofs

  ultimately, my goal here is to help establish a robust systemd-capable
  coordination in the various parts here to avoid another similar issue
  due to these inter-dependencies.  I don't know if 'start-statd' being
  re-written to take systemd state into account is the correct solution,
  but IMHO, systemd/dbus-daemon are utterly fragile in this situation
  and extremely difficult to debug (need systemctl to do stuff, but it
  won't work, and you can't restart dbus-daemon w/o systemctl, and kill
  -TERM on pid 1 doesn't work ...

Summary:
  - system configured for NFSv3 mounts via /etc/nfsmount.conf
note: this was to workaround a bug in NFSv4.[012] that
caused deadlocks against NFSv3 servers running Jessie.
i do not recall the bug #
something changed in a recent Stretch patchlevel as this
was working fine up until i patched and rebooted.
  - systemd unit rpc-statd.service is disabled
  - automount/autofs -> nfs is called triggering start-statd
that makes a 'systemctl start rpc-statd' that takes down
dbus-daemon and never completes.
  - regardless of where the blame lies, it is possible that is wrong to
call 'systemctl' from inside 'start-statd' *if* it's being called
from a systemd unit itself.

  If system is configured for NFS v3 mounts via /etc/nfsmount.conf
  and systemctl unit 'rpc-statd' is disabled, then the automounter
  creates a chain in boot (at least in our system case) that forcibly
  tries to run 'systemctl start rpc-statd' via /usr/sbin/start-statd.

  This results in systemctl call not completing (i don't know if
  it's because systemctl calls can't be nested or called outside normal
  startup flow or what), and eventually dbus-daemon stops responding
  (so it could be a bug that needs to be transferred there).  this locks
  up the entire boot process.   systemctl calls all timeout.
  dbus-daemon is sitting in EAGAIN (resource temporarily unavailable)

  Additionally, i wasn't able to ssh in (even though systemd had started
  sshd) because of 'pam_motd' in /etc/pam.d/sshd calling update-motd,
  which also blocked hard and never completed and was uninterruptable.
  once i commented 'pam_motd' out, i could ssh in, and C something
  hanging on nfs to get a shell. (again, tower of fail)

  once in, if i killed the 'systemctl start rpc-statd', the system would
  return to responsiveness. (systemctl could again contact dbus-daemon)

  systemd-cgls showed:

  +-autofs.service
| +-1453 /usr/sbin/automount --pid-file /var/run/autofs.pid
  | +-1465 /bin/mount -t nfs -s -o intr,nodev,nosuid
  ral-local-linux:/exports/linux-amd64 /var/autofs/mnt/linux-amd64
| +-1466 /sbin/mount.nfs
ral-local-linux:/exports/linux-amd64 /var/autofs/mnt/linux-amd64
-s -o rw,nodev,nosuid,intr
  | +-1467 /bin/sh /usr/sbin/start-statd
| -1470 systemctl start rpc-statd.service
 this hangs dbus-daemon and brings down the
whole systemd kingdom.

  before it hung, ...
puffin:/etc/default/grub.d# systemctl list-jobs
TYPE  STATE  
607 apt-daily.service 

Processed: closing 679274

[Debian Bug Tracking System]

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

> close 679274
Bug #679274 [nfs-kernel-server] init script does not start nfsd when 
/etc/exports is empty
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 884871

[Debian Bug Tracking System]

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

> close 884871
Bug #884871 [nfs-kernel-server] nfs-kernel-server: svcgssd starts anyways when 
"disabled" in /etc/default/nfs-kernel-server
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 675176

[Debian Bug Tracking System]

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

> close 675176 1:1.2.3-1
Bug #675176 [nfs-kernel-server] svcgssd not working with '-n' option after 
lenny to squeeze upgrade
Marked as fixed in versions nfs-utils/1:1.2.3-1.
Bug #675176 [nfs-kernel-server] svcgssd not working with '-n' option after 
lenny to squeeze upgrade
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 806829

[Debian Bug Tracking System]

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

> close 806829
Bug #806829 [nfs-common] nfs-common says 'No such file or directory'
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1024625: marked as done (cmake-data: FindPython.cmake points to newest Python version, not the default)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 21:20:52 +
with message-id 
and subject line Bug#1024625: fixed in cmake 3.25.0-3
has caused the Debian Bug report #1024625,
regarding cmake-data: FindPython.cmake points to newest Python version, not the 
default
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.)


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

Package: cmake-data
Version: 3.25.0-1
Severity: important
Control: affects -1 src:openstructure
Control: affects -1 src:promod3

Dear Maintainer,

Due to the added support for Python 3.11, CMake's FindPython.cmake no 
longer returns the default Python version (3.10 currently), but returns 
the latest one (3.11 currently). Due to this, some packages FTBFS (for 
example, openstructure and promod3) and some only provide the built 
object for Python 3.11 which is not the default.


There was a similar bug #945825 during previous Python transition. That 
was resolved by patching FindPython.cmake to use 'py3versions -d'. I 
suppose additional logic has to be implemented to allow for default 
Python version being not the latest available Python version.


Andrius
--- End Message ---
--- Begin Message ---
Source: cmake
Source-Version: 3.25.0-3
Done: Timo Röhling 

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

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

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

Debian distribution maintenance software
pp.
Timo Röhling  (supplier of updated cmake package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 24 Nov 2022 21:45:01 +0100
Source: cmake
Architecture: source
Version: 3.25.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian CMake Team 
Changed-By: Timo Röhling 
Closes: 1024625
Changes:
 cmake (3.25.0-3) unstable; urgency=medium
 .
   * Prefer default Python version regardless of CMP0094 (Closes: #1024625)
Checksums-Sha1:
 c5b3f59da4920639bc27500b92933b6f39aeb6f5 3887 cmake_3.25.0-3.dsc
 facd1e4f59c8166e56d3642152e0a4e7651cc581 32496 cmake_3.25.0-3.debian.tar.xz
Checksums-Sha256:
 bbdb25f586b7d056714c4985bf2b528641e87ee472bd680c99cf345512014295 3887 
cmake_3.25.0-3.dsc
 bc4dc0ee72b5406361c3dd7023456f14c6cdbee4f986fdd13416ec3295dc1835 32496 
cmake_3.25.0-3.debian.tar.xz
Files:
 753fea5d04b20a50ada23ea930e7576c 3887 devel optional cmake_3.25.0-3.dsc
 8e5ca8609b8c4c6d19c0911fda95e5ff 32496 devel optional 
cmake_3.25.0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQHIBAEBCgAyFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmN/3BAUHHJvZWhsaW5n
QGRlYmlhbi5vcmcACgkQ+C8H+466LVm4kgwAiUll5p543tam6u5T1ke85m+uGja/
LlFEhJGZB6XzUwM8ZKezDIEYsrF8mgMS2zXXSY6ruOnPxLzAZnmSOwZgqjfMFHot
I8qCg1cpvWudXvO/DvEJ7x94ZUz4W4kExpvMue+jMPIJPgWz4si9LSKUIyq1jOlJ
Woh2rQsHbZdS9AU8MYKnw8+C5dcGa8YmUNtrldnq670DgPvwvMdQJA6EtSuwyywl
keo6ZJnrK3reQRKclfn9kMqjxpiRjKo1RTqo5BCr9NqkxHun5vyHYeidE/6e+4rg
ILJ8u26p/WmP7bABSlCGE6RYXLEvo5alPAv/zKxZBUzX/Zjqd++3xj+KeNvQ1ydt
NQ3CpEtyOQ94zp01/su48U8Kl51XlMsb0ovcZdPhqSBAJ4AnhNeNDQZnyTrgQXMx
wJ3zHOYNZ1SrI92qIanvmQEIPNbBBnDsrB7BdTineH+7/ceKe96TfOlnVDVDKlIe
5v8hqAdoSiEGOE82DsxidKllW94M33fPJPvt
=4zIX
-END PGP SIGNATURE End Message ---

Bug#1019929: marked as done (podman: Subordinate UID/GID ranges not fetched from libsubid)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 21:05:07 +
with message-id 
and subject line Bug#1019929: fixed in libpod 4.3.1+ds1-4
has caused the Debian Bug report #1019929,
regarding podman: Subordinate UID/GID ranges not fetched from libsubid
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.)


-- 
1019929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019929
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: podman
Version: 4.2.0+ds1-3
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

I've not got anything in /etc/subuid or /etc/subgid because subordinate
id range info is stored in LDAP.

  $ grep ^subid: /etc/nsswitch.conf
  subid: sss

This is transparent to clients using libsubid:

  $ getsubids sam
  0: sam 2147483648 65536

... but it looks like podman doesn't use this library yet:

$ podman system info
ERRO[] cannot find UID/GID for user sam: no subuid ranges found for 
user "sam" in /etc/subuid - check rootless mode in man pages.
WARN[] Using rootless single mapping into the namespace. This might 
break some images. Check /etc/subuid and /etc/subgid for adding sub*ids if not 
using a network user
[...]
  idMappings:
gidmap:
- container_id: 0
  host_id: 1000
  size: 1
uidmap:
- container_id: 0
  host_id: 1000
  size: 1
[...]

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

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

Versions of packages podman depends on:
ii  conmon   2.1.3+ds1-1
ii  crun 1.5+dfsg-1+b1
ii  golang-github-containers-common  0.48.0+ds1-1
ii  libc62.34-7
ii  libdevmapper1.02.1   2:1.02.185-1
ii  libgpgme11   1.17.1-4.1
ii  libseccomp2  2.5.4-1+b1
ii  systemd [systemd-tmpfiles]   251.4-3

Versions of packages podman recommends:
ii  buildah1.26.1+ds1-1
ii  catatonit  0.1.7-1
ii  dbus-user-session  1.14.0-2
ii  fuse-overlayfs 1.9-1
ii  slirp4netns1.2.0-1
ii  uidmap 1:4.11.1+dfsg1-2

Versions of packages podman suggests:
ii  containers-storage  1.37.2+ds1-1+b2
pn  docker-compose  
ii  iptables1.8.8-1

- -- no debconf information

-BEGIN PGP SIGNATURE-

iIgEARYIADAWIQTWOGqGn6HETecdzqZOEaKLhlAYigUCYyRZrhIcc2FtQHJvYm90
cy5vcmcudWsACgkQThGii4ZQGIra+wEA9cSULDer04xzpg1djBcsaxdK78eH6avT
szoQ8hl2ERMA/08sN17EOvYQOLB8WwleW1kPCQZdDztMiapcY5Ep7CYI
=DI3R
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: libpod
Source-Version: 4.3.1+ds1-4
Done: Reinhard Tartler 

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

Debian distribution maintenance software
pp.
Reinhard Tartler  (supplier of updated libpod package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 24 Nov 2022 15:35:49 -0500
Source: libpod
Architecture: source
Version: 4.3.1+ds1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Reinhard Tartler 
Closes: 1000521 1001780 1003486 1006426 1007022 1009374 1009376 1009747 1012053 
1014309 1019591 1019929
Changes:
 libpod (4.3.1+ds1-4) unstable; urgency=medium
 .
   * upload to unstable
 .
 libpod (4.3.1+ds1-3) experimental; urgency=medium
 .
   * debian/rules: make the previous change to build machine/qemu only
 on supported architecture actually work
 .
 libpod (4.3.1+ds1-2) experimental; urgency=medium
 .
   * Build machine/qemu only on amd64, arm64, fixes FTBFS
 .
 libpod (4.3.1+ds1-1) experimental; urgency=medium
 .
   * New upstream release
 - Add container GID to additional groups,
   fixes CVE-2022-2989, 

Bug#1019591: marked as done (libpod: CVE-2022-2989)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 21:05:07 +
with message-id 
and subject line Bug#1019591: fixed in libpod 4.3.1+ds1-4
has caused the Debian Bug report #1019591,
regarding libpod: CVE-2022-2989
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.)


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

Hi,

The following vulnerability was published for libpod.

CVE-2022-2989[0]:
https://www.benthamsgaze.org/2022/08/22/vulnerability-in-linux-containers-investigation-and-mitigation/
https://bugzilla.redhat.com/show_bug.cgi?id=2121445

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

For further information see:

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

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: libpod
Source-Version: 4.3.1+ds1-4
Done: Reinhard Tartler 

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

Debian distribution maintenance software
pp.
Reinhard Tartler  (supplier of updated libpod package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 24 Nov 2022 15:35:49 -0500
Source: libpod
Architecture: source
Version: 4.3.1+ds1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Reinhard Tartler 
Closes: 1000521 1001780 1003486 1006426 1007022 1009374 1009376 1009747 1012053 
1014309 1019591 1019929
Changes:
 libpod (4.3.1+ds1-4) unstable; urgency=medium
 .
   * upload to unstable
 .
 libpod (4.3.1+ds1-3) experimental; urgency=medium
 .
   * debian/rules: make the previous change to build machine/qemu only
 on supported architecture actually work
 .
 libpod (4.3.1+ds1-2) experimental; urgency=medium
 .
   * Build machine/qemu only on amd64, arm64, fixes FTBFS
 .
 libpod (4.3.1+ds1-1) experimental; urgency=medium
 .
   * New upstream release
 - Add container GID to additional groups,
   fixes CVE-2022-2989, closes: #1019591
   * Bugfix: Subordinate UID/GID ranges not fetched from libsubid,
 Thanks to Sam Morris  for the patch, closes: #1019929
 .
 libpod (4.2.0+ds1-3) experimental; urgency=medium
 .
   * Force using golang-go to avoid compilation failures with gcc-go
   * Confirmed updated components allow podman to work, thanks to
 Bastian Blank (Closes: #1012053), and is compiled against a
 containers/common that is more mindful regarding foreign-arch
 images (Closes: #1009376)
   * Confirmed fix: "starting rootless container fails with: can't get final
 child's PID from pipe: EOF", code change likely already in 4.1
 thanks to Gabriel Filion (Closes: #1007022).
   * Make podman recommend 'dbus-user-session', Closes: #1009747
 .
 libpod (4.2.0+ds1-2) experimental; urgency=medium
 .
   * tighten dependency on golang-github-opencontainers-runc-dev
 .
 libpod (4.2.0+ds1-1) experimental; urgency=medium
 .
   * New upstream release
   * drop patches merged upstream
   * add distro patch to use system 'goimports' utility
   * tighten dependencies
   * hooks/docs no longer provides section 5 manpages
 .
 libpod (4.1.1+ds1-3) experimental; urgency=medium
 .
   * reorganize dependencies for networking stack
 .
 libpod (4.1.1+ds1-2) experimental; urgency=medium
 .
   * organize GOLANG_EXCLUDES and GOLANG_TEST_EXCLUDES
   * add patches fix-test-TestEnvVarValue-NN.patch, fixes
 Test failures for !amd64, !arm64 Closes: #1014309
 .
 libpod (4.1.1+ds1-1) experimental; urgency=medium
 .
   * New upstream release
 .
 libpod (4.1.0+ds2-2) experimental; urgency=medium
 .
   * Avoid building podman/pkg/machine/e2e on all architectures
 .
 libpod (4.1.0+ds2-1) experimental; urgency=medium
 .
   * New upstream release
 .
 libpod (4.0.3+ds1-1) experimental; urgency=medium
 

Bug#1014309: marked as done (libpod - FTBFS: FAIL: TestMonitorTwoDirGood (1.08s))

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 21:05:07 +
with message-id 
and subject line Bug#1014309: fixed in libpod 4.3.1+ds1-4
has caused the Debian Bug report #1014309,
regarding libpod - FTBFS: FAIL: TestMonitorTwoDirGood (1.08s)
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.)


-- 
1014309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014309
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpod
Version: 3.4.7+ds1-3
Severity: serious
Tags: ftbfs

libpod fails to build from source on several architectures:
| 
| time="2022-05-19T21:23:53Z" level=error msg="Failed loading hooks for 
/tmp/hooks-test-fallback-3506184749/a.json: parsing hook 
\"/tmp/hooks-test-primary-2094757904/0a.json\": unrecognized hook version: 
\"-1\""
| time="2022-05-19T21:23:53Z" level=error msg="Failed loading hooks for 
/tmp/hooks-test-primary-2094757904/0a.json: parsing hook 
\"/tmp/hooks-test-primary-2094757904/0a.json\": unrecognized hook version: 
\"-1\""
| time="2022-05-19T21:23:53Z" level=error msg="Failed loading hooks for 
/tmp/hooks-test-primary-2094757904/0a.json: parsing hook 
\"/tmp/hooks-test-primary-2094757904/0a.json\": unrecognized hook version: 
\"-1\""
| expected:  
| actual:  &{[{/bin/sh [] [] 0xc00012c118}] [] [] [] [] []}
| === RUN   TestMonitorTwoDirGood/bad-primary-same-addition
| time="2022-05-19T21:23:53Z" level=error msg="Failed loading hooks for 
/tmp/hooks-test-primary-2094757904/a.json: parsing hook 
\"/tmp/hooks-test-primary-2094757904/a.json\": unrecognized hook version: 
\"-1\": parsing hook \"/tmp/hooks-test-primary-2094757904/0a.json\": 
unrecognized hook version: \"-1\""
| === RUN   TestMonitorTwoDirGood/good-primary-removal
| time="2022-05-19T21:23:53Z" level=error msg="Failed loading hooks for 
/tmp/hooks-test-primary-2094757904/a.json: parsing hook 
\"/tmp/hooks-test-primary-2094757904/0a.json\": unrecognized hook version: 
\"-1\""
| === RUN   TestMonitorTwoDirGood/good-non-json-addition
| time="2022-05-19T21:23:53Z" level=error msg="Failed loading hooks for 
/tmp/hooks-test-fallback-3506184749/README: parsing hook 
\"/tmp/hooks-test-primary-2094757904/0a.json\": unrecognized hook version: 
\"-1\""
| time="2022-05-19T21:23:53Z" level=error msg="Failed loading hooks for 
/tmp/hooks-test-fallback-3506184749/README: parsing hook 
\"/tmp/hooks-test-primary-2094757904/0a.json\": unrecognized hook version: 
\"-1\""
| === RUN   TestMonitorTwoDirGood/good-fallback-removal#01
| time="2022-05-19T21:23:53Z" level=error msg="Failed loading hooks for 
/tmp/hooks-test-fallback-3506184749/a.json: parsing hook 
\"/tmp/hooks-test-primary-2094757904/0a.json\": unrecognized hook version: 
\"-1\""
| --- FAIL: TestMonitorTwoDirGood (1.08s)
| --- PASS: TestMonitorTwoDirGood/good-fallback-addition (0.10s)
| --- FAIL: TestMonitorTwoDirGood/good-primary-override (0.11s)
| --- FAIL: TestMonitorTwoDirGood/good-fallback-removal (0.10s)
| --- PASS: TestMonitorTwoDirGood/good-fallback-restore (0.17s)
| --- PASS: TestMonitorTwoDirGood/bad-primary-new-addition (0.10s)
| --- PASS: TestMonitorTwoDirGood/bad-primary-same-addition (0.10s)
| --- PASS: TestMonitorTwoDirGood/good-primary-removal (0.10s)
| --- PASS: TestMonitorTwoDirGood/good-non-json-addition (0.10s)
| --- PASS: TestMonitorTwoDirGood/good-fallback-removal#01 (0.19s)

Bastian

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

Kernel: Linux 5.18.0-2-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: libpod
Source-Version: 4.3.1+ds1-4
Done: Reinhard Tartler 

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

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

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

Debian distribution maintenance software
pp.
Reinhard Tartler  (supplier of updated libpod 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)

Bug#1009882: marked as done (golang-github-containers-buildah: CVE-2022-27651)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 21:04:27 +
with message-id 
and subject line Bug#1009882: fixed in golang-github-containers-buildah 
1.28.0+ds1-2
has caused the Debian Bug report #1009882,
regarding golang-github-containers-buildah: CVE-2022-27651
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.)


-- 
1009882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009882
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-containers-buildah
Version: 1.23.1+ds1-2
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for golang-github-containers-buildah.

CVE-2022-27651[0]:
| A flaw was found in buildah where containers were incorrectly started
| with non-empty default permissions. A bug was found in Moby (Docker
| Engine) where containers were incorrectly started with non-empty
| inheritable Linux process capabilities, enabling an attacker with
| access to programs with inheritable file capabilities to elevate those
| capabilities to the permitted set when execve(2) runs. This has the
| potential to impact confidentiality and integrity.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-27651
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-27651
[1] 
https://github.com/containers/buildah/commit/e7e55c988c05dd74005184ceb64f097a0cfe645b

Please adjust the affected versions in the BTS as needed.

Regards,
Salvaotre
--- End Message ---
--- Begin Message ---
Source: golang-github-containers-buildah
Source-Version: 1.28.0+ds1-2
Done: Reinhard Tartler 

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

Debian distribution maintenance software
pp.
Reinhard Tartler  (supplier of updated 
golang-github-containers-buildah package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 24 Nov 2022 15:27:47 -0500
Source: golang-github-containers-buildah
Architecture: source
Version: 1.28.0+ds1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Reinhard Tartler 
Closes: 1009882
Changes:
 golang-github-containers-buildah (1.28.0+ds1-2) unstable; urgency=medium
 .
   * upload to unstable
 .
 golang-github-containers-buildah (1.28.0+ds1-1) experimental; urgency=medium
 .
   * New upstream release
 new upstream version fixes CVE-2022-27651, Closes: #1009882
 .
 golang-github-containers-buildah (1.27.0+ds1-6) experimental; urgency=medium
 .
   * Force building with golang-go, gccgo miscompiles at least on mips
 .
 golang-github-containers-buildah (1.27.0+ds1-5) experimental; urgency=medium
 .
   * also exclude running "copier" test from package build, breaks/timeouts
 on arm64, armel, armhf and powerpc64
 .
 golang-github-containers-buildah (1.27.0+ds1-4) experimental; urgency=medium
 .
   * also exclude running pkg/cli test from package build
 .
 golang-github-containers-buildah (1.27.0+ds1-3) experimental; urgency=medium
 .
   * don't run test pkg/completion at package build times
 .
 golang-github-containers-buildah (1.27.0+ds1-2) experimental; urgency=medium
 .
   * New upstream release
   * Run tests at build time
 .
 golang-github-containers-buildah (1.26.1+ds1-1) experimental; urgency=medium
 .
   * New upstream release
 .
 golang-github-containers-buildah (1.24.1+ds1-1) experimental; urgency=medium
 .
   * New upstream release
Checksums-Sha1:
 8e2b40b9687c7873ff1c4d9e582cb41ec97c1561 4007 
golang-github-containers-buildah_1.28.0+ds1-2.dsc
 3670d28dce316fe453c6c3ec937d52bfde4b5932 6844 
golang-github-containers-buildah_1.28.0+ds1-2.debian.tar.xz
Checksums-Sha256:
 ebc280303d5659a76c54be59a663dc164e28b0cd272c8e007fcfc74b7883ce3e 4007 
golang-github-containers-buildah_1.28.0+ds1-2.dsc
 703396ca99411f54aaec26493841aa974574252b95a4304577116717c974ba57 6844 

Bug#1009376: marked as done (running foreign architecture containers hits the network every time and confuses future `podman run` invocations)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 21:05:07 +
with message-id 
and subject line Bug#1009376: fixed in libpod 4.3.1+ds1-4
has caused the Debian Bug report #1009376,
regarding running foreign architecture containers hits the network every time 
and confuses future `podman run` invocations
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.)


-- 
1009376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009376
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: podman
Version: 3.4.4+ds1-1
Severity: normal

When running containers for a foreign architecture, podman run will hit
the networking looking for images on every invocation:

8<8<8<-
terceiro@host:~$ podman run --arch=arm64 debian arch
Resolved "debian" as an alias 
(/etc/containers/registries.conf.d/shortnames.conf)
Trying to pull docker.io/library/debian:latest...
Getting image source signatures
Copying blob fa223d8c149d done
Copying config 05e8051d05 done
Writing manifest to image destination
Storing signatures
aarch64
terceiro@host:~$ podman run --arch=arm64 debian arch
Resolved "debian" as an alias 
(/etc/containers/registries.conf.d/shortnames.conf)
Trying to pull docker.io/library/debian:latest...
Getting image source signatures
Copying blob fa223d8c149d [-] 0.0b / 0.0b
Copying config 05e8051d05 done
Writing manifest to image destination
Storing signatures
aarch64
8<8<8<-

This means that if I try run a foreign container while I'm offline, I
can't:

8<8<8<-
terceiro@host:~$ podman run --arch=arm64 debian arch
Resolved "debian" as an alias 
(/etc/containers/registries.conf.d/shortnames.conf)
Trying to pull docker.io/library/debian:latest...
Error: initializing source docker://debian:latest: pinging container registry 
registry-1.docker.io: Get "https://registry-1.docker.io/v2/": dial tcp: lookup 
registry-1.docker.io on 10.0.2.3:53: dial udp 10.0.2.3:53: connect: network is 
unreachable
8<8<8<-

Weirder than that, is that from this point on, a plain `podman run` will
run the foreign container, instead of a native one (but will not hit the
network, as I'm able to do that while still offline):

8<8<8<-
terceiro@host:~$ podman run debian arch
aarch64
8<8<8<-

To "fix" this, I have to explicitly pull the same image without any
architecture request after coming online again:

8<8<8<-
terceiro@host:~$ podman pull debian
Trying to pull docker.io/library/debian:latest...
Getting image source signatures
Copying blob dbba69284b27 done
Copying config d69c6cd3a2 done
Writing manifest to image destination
Storing signatures
d69c6cd3a20d21ec91b677c3bcd10d9975f4fe67eff81afb5a09bdef5134afeb
terceiro@host:~$ podman run debian arch
x86_64
8<8<8<-

I have checked the version in experimental, and this bug still applies
to it.

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

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

Versions of packages podman depends on:
ii  conmon   2.0.25+ds1-1.1
ii  containernetworking-plugins  1.1.0+ds1-1
ii  crun 0.17+dfsg-1.1
ii  golang-github-containers-common  0.47.2+ds1-1
ii  init-system-helpers  1.62
ii  libc62.33-7
ii  libdevmapper1.02.1   2:1.02.175-2.1
ii  libgpgme11   1.16.0-1.2
ii  libseccomp2  2.5.3-2
ii  runc 1.1.1+ds1-1

Versions of packages podman recommends:
ii  buildah   1.24.1+ds1-1
ii  catatonit 0.1.7-1
ii  fuse-overlayfs1.8.2-1
ii  golang-github-containernetworking-plugin-dnsname  

Bug#1007022: marked as done (podman: starting rootless container fails with: can't get final child's PID from pipe: EOF)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 21:05:07 +
with message-id 
and subject line Bug#1007022: fixed in libpod 4.3.1+ds1-4
has caused the Debian Bug report #1007022,
regarding podman: starting rootless container fails with: can't get final 
child's PID from pipe: EOF
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.)


-- 
1007022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007022
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: podman
Version: 3.4.4+ds1-1
Severity: normal

Hello,

I used to be able to run rootless container on debian sid maybe 3 months ago
(I'm sorry, I don't have much more precise information about versions when
things used to work), but now that I try and start containers again I am
consistently hitting errors of this form:

$ podman run -d --name="draw" -p 8080:8080 -p 8443:8443 fjudith/draw.io
Error: OCI runtime error: unable to start container 
"0f2eb8afb9ce6eebbede769dc288e228ea6cbae0e76936672e6673228ac6862c": runc create 
failed: unable to start container process: can't get final child's PID from 
pipe: EOF

so no container will start at all in rootless mode

for information, the images required for running the containers were correctly
downloaded and are available locally.

I've tried to search for information about this online but the cause for this
particular error message can seemingly be very varied. The usual answers about
the user.max_user_namespaces kernel option, or memory allocation settings for
images/containers seem not to hold in this case.

if I run the container as root with:

# sudo podman run -d --name="draw" -p 8080:8080 -p 8443:8443 fjudith/draw.io

then it's getting started as expected.

I'm not sure what additional information could be helpful, but I'm willing to
send more output from logs/commands to help out identify what's happening.

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

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

Versions of packages podman depends on:
ii  conmon   2.0.25+ds1-1.1
ii  containernetworking-plugins  1.1.0+ds1-1
ii  golang-github-containers-common  0.44.4+ds1-1
ii  init-system-helpers  1.62
ii  libc62.33-7
ii  libdevmapper1.02.1   2:1.02.175-2.1
ii  libgpgme11   1.16.0-1.2
ii  libseccomp2  2.5.3-2
ii  runc 1.1.0+ds1-1

Versions of packages podman recommends:
ii  buildah   1.23.1+ds1-2
ii  fuse-overlayfs1.7.1-1
ii  golang-github-containernetworking-plugin-dnsname  1.3.1+ds1-2
ii  slirp4netns   1.0.1-2
ii  tini  0.19.0-1
ii  uidmap1:4.11.1+dfsg1-2

Versions of packages podman suggests:
pn  containers-storage  
ii  docker-compose  1.29.2-1
ii  iptables1.8.7-1

-- Configuration Files:
/etc/cni/net.d/87-podman-bridge.conflist [Errno 13] Permission denied: 
'/etc/cni/net.d/87-podman-bridge.conflist'

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libpod
Source-Version: 4.3.1+ds1-4
Done: Reinhard Tartler 

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

Debian distribution maintenance software
pp.
Reinhard Tartler  (supplier of updated libpod package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 24 Nov 2022 15:35:49 -0500
Source: libpod
Architecture: source
Version: 4.3.1+ds1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Reinhard Tartler 
Closes: 

Bug#1000521: marked as done (libpod: please provide podman-remote binary)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 21:05:07 +
with message-id 
and subject line Bug#1000521: fixed in libpod 4.3.1+ds1-4
has caused the Debian Bug report #1000521,
regarding libpod: please provide podman-remote binary
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.)


-- 
1000521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000521
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpod
Version: 3.4.1+ds1-2
Severity: wishlist

Dear Maintainer,

Recent podman upstream releases provide a new podman-remote binary, but
the Debian package does not even build it.

I'm used to packages providing binaries without a manpage, but this is
the first time I have seen the opposite! :-)

$ dpkg -S podman-remote
podman: /usr/share/zsh/vendor-completions/_podman-remote
podman: /usr/share/man/man1/podman-remote.1.gz


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

Kernel: Linux 5.14.0-4-amd64 (SMP w/4 CPU threads)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: libpod
Source-Version: 4.3.1+ds1-4
Done: Reinhard Tartler 

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

Debian distribution maintenance software
pp.
Reinhard Tartler  (supplier of updated libpod package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 24 Nov 2022 15:35:49 -0500
Source: libpod
Architecture: source
Version: 4.3.1+ds1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Reinhard Tartler 
Closes: 1000521 1001780 1003486 1006426 1007022 1009374 1009376 1009747 1012053 
1014309 1019591 1019929
Changes:
 libpod (4.3.1+ds1-4) unstable; urgency=medium
 .
   * upload to unstable
 .
 libpod (4.3.1+ds1-3) experimental; urgency=medium
 .
   * debian/rules: make the previous change to build machine/qemu only
 on supported architecture actually work
 .
 libpod (4.3.1+ds1-2) experimental; urgency=medium
 .
   * Build machine/qemu only on amd64, arm64, fixes FTBFS
 .
 libpod (4.3.1+ds1-1) experimental; urgency=medium
 .
   * New upstream release
 - Add container GID to additional groups,
   fixes CVE-2022-2989, closes: #1019591
   * Bugfix: Subordinate UID/GID ranges not fetched from libsubid,
 Thanks to Sam Morris  for the patch, closes: #1019929
 .
 libpod (4.2.0+ds1-3) experimental; urgency=medium
 .
   * Force using golang-go to avoid compilation failures with gcc-go
   * Confirmed updated components allow podman to work, thanks to
 Bastian Blank (Closes: #1012053), and is compiled against a
 containers/common that is more mindful regarding foreign-arch
 images (Closes: #1009376)
   * Confirmed fix: "starting rootless container fails with: can't get final
 child's PID from pipe: EOF", code change likely already in 4.1
 thanks to Gabriel Filion (Closes: #1007022).
   * Make podman recommend 'dbus-user-session', Closes: #1009747
 .
 libpod (4.2.0+ds1-2) experimental; urgency=medium
 .
   * tighten dependency on golang-github-opencontainers-runc-dev
 .
 libpod (4.2.0+ds1-1) experimental; urgency=medium
 .
   * New upstream release
   * drop patches merged upstream
   * add distro patch to use system 'goimports' utility
   * tighten dependencies
   * hooks/docs no longer provides section 5 manpages
 .
 libpod (4.1.1+ds1-3) experimental; urgency=medium
 .
   * reorganize dependencies for networking stack
 .
 libpod (4.1.1+ds1-2) experimental; urgency=medium
 .
   * organize GOLANG_EXCLUDES and GOLANG_TEST_EXCLUDES
   * add patches fix-test-TestEnvVarValue-NN.patch, fixes
 Test failures for !amd64, !arm64 Closes: #1014309
 .
 libpod (4.1.1+ds1-1) 

Bug#1024733: marked as done (timeshift: GUI crashes on backup/restore. Fixed upstream, package needs update)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 16:01:21 -0500
with message-id 
and subject line Re: Bug#1024733: timeshift: GUI crashes on backup/restore. 
Fixed upstream, package needs update
has caused the Debian Bug report #1024733,
regarding timeshift: GUI crashes on backup/restore. Fixed upstream, package 
needs update
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.)


-- 
1024733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024733
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: timeshift
Version: 22.06.5-1
Severity: important
X-Debbugs-Cc: mcar...@yahoo.co.uk

Dear Maintainer,

The GUI crashes on backup or restore with Timeshift v22.06.5. See 
https://github.com/linuxmint/timeshift/issues/91.

Bug is fixed in latest version of Timeshift. Please upgrade this package to a 
newer version.


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

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

Versions of packages timeshift depends on:
ii  cron [cron-daemon]   3.0pl1-137ubuntu3
ii  libc62.36-0ubuntu4
ii  libcairo21.16.0-5ubuntu2
ii  libgdk-pixbuf-2.0-0  2.42.9+dfsg-1
ii  libgee-0.8-2 0.20.6-1
ii  libglib2.0-0 2.74.0-3
ii  libgtk-3-0   3.24.34-3ubuntu2
ii  libjson-glib-1.0-0   1.6.6-1build1
ii  libvte-2.91-00.70.0-1
ii  libxapp1 2.2.15-1
ii  psmisc   23.5-3
ii  rsync3.2.5-1

timeshift recommends no packages.

timeshift suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 22.11.1-1

New version has been uploaded.

Thanks,
Boyuan Yang

在 2022-11-24星期四的 15:06 +1300，Michael Rans写道：
> Package: timeshift
> Version: 22.06.5-1
> Severity: important
> X-Debbugs-Cc: mcar...@yahoo.co.uk
> 
> Dear Maintainer,
> 
> The GUI crashes on backup or restore with Timeshift v22.06.5. See
> https://github.com/linuxmint/timeshift/issues/91.
> 
> Bug is fixed in latest version of Timeshift. Please upgrade this package
> to a newer version.
> 
> 
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers kinetic-updates
>   APT policy: (500, 'kinetic-updates'), (500, 'kinetic-security'), (500,
> 'kinetic'), (100, 'kinetic-backports')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 5.19.0-23-generic (SMP w/8 CPU threads; PREEMPT)
> Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_NZ:en
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages timeshift depends on:
> ii  cron [cron-daemon]   3.0pl1-137ubuntu3
> ii  libc6    2.36-0ubuntu4
> ii  libcairo2    1.16.0-5ubuntu2
> ii  libgdk-pixbuf-2.0-0  2.42.9+dfsg-1
> ii  libgee-0.8-2 0.20.6-1
> ii  libglib2.0-0 2.74.0-3
> ii  libgtk-3-0   3.24.34-3ubuntu2
> ii  libjson-glib-1.0-0   1.6.6-1build1
> ii  libvte-2.91-0    0.70.0-1
> ii  libxapp1 2.2.15-1
> ii  psmisc   23.5-3
> ii  rsync    3.2.5-1
> 
> timeshift recommends no packages.
> 
> timeshift suggests no packages.
> 
> -- no debconf information
> 



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

Bug#1007541: marked as done (dvdtape: please consider upgrading to 3.0 source format)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 20:35:12 +
with message-id 
and subject line Bug#1007541: fixed in dvdtape 1.6-2.1
has caused the Debian Bug report #1007541,
regarding dvdtape: please consider upgrading to 3.0 source format
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.)


-- 
1007541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007541
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dvdtape
Version: 1.6-2
Severity: wishlist
Tags: bookworm sid
Usertags: format1.0 format1.0-nkp-nv

Dear maintainer,

This package is among the few (1.9%) that still use source format 1.0 in
bookworm.  Please upgrade it to source format 3.0, as (1) this format has many
advantages, as documented in https://wiki.debian.org/Projects/DebSrc3.0 ; (2)
this contributes to standardization of packaging practices.

Please note that this is also a sign that the packaging of this software
could maybe benefit from a refresh. It might be a good opportunity to
look at other aspects as well.

It was noticed in https://lists.debian.org/debian-devel/2022/03/msg00096.html
that the conversion for this package is likely trivial, and builds bit-by-bit
identical binary packages.


This mass bug filing was discussed on debian-devel@:
https://lists.debian.org/debian-devel/2022/03/msg00074.html

Thanks

Lucas
--- End Message ---
--- Begin Message ---
Source: dvdtape
Source-Version: 1.6-2.1
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated dvdtape package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 24 Nov 2022 21:05:16 +0100
Source: dvdtape
Architecture: source
Version: 1.6-2.1
Distribution: unstable
Urgency: medium
Maintainer: Steve McIntyre <93...@debian.org>
Changed-By: Bastian Germann 
Closes: 1007541
Changes:
 dvdtape (1.6-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Convert to 3.0 source format. Closes: #1007541
Checksums-Sha1:
 4f2f16a5c8b3557406d5b75798d2928f51a0f727 1493 dvdtape_1.6-2.1.dsc
 5825d5d61c0b60bbc32e97a496439c5c0f6dc8d1 3204 dvdtape_1.6-2.1.debian.tar.xz
 59fdc7205ea5c8ecedd05227252f0983dcdb7223 5570 dvdtape_1.6-2.1_source.buildinfo
Checksums-Sha256:
 6a77104ad7738f3e1a942652e6d6ff389a85348130c7065a19935c3ee41a3ae5 1493 
dvdtape_1.6-2.1.dsc
 fd30bfc03a73b9d13ae227d181536a3594cd2198e1d5f60b506b948f88e2e783 3204 
dvdtape_1.6-2.1.debian.tar.xz
 212b3c7daaf4ba2992f44b0442915a5a35507dfddf3638eb8b0fd281bdf1aca0 5570 
dvdtape_1.6-2.1_source.buildinfo
Files:
 e8a8fdddaf8c40c3e144111459120c38 1493 utils extra dvdtape_1.6-2.1.dsc
 80fa9a7b9146000676cc926ff1810adb 3204 utils extra dvdtape_1.6-2.1.debian.tar.xz
 df3b7ec1b6b477dbeb5439333f25366b 5570 utils extra 
dvdtape_1.6-2.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmN/z1MQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFCe4C/98dLD4KNvAvMewMWFxiBC+aSvQD1M3myPH
FBMndrE5XvoqHA7HDQCh0kaHrg01y++CTvajbm0WTsKVYTHVI6/lvSMFvxLI2gA7
djHlATjQ63/O0Eg4sIQq2+h6/GJxUJXmXN7eEKgPZuT4cR9Xgr50DL4ENvGVjez6
p66eJO0V7NZheHCkyX8mrbHKapF7H7V5w/AHcFZy6QruZc73tMo/gDSOQKvLMQd6
3Q401UKqLbg0ILUb82x4z2RRMajKwG66XPP4XWoNHwC3uPWg2obyxFCsi3dL5PPa
UnS1t/J8+zar2xsKWcnQOG/fTMy7Bw9OctBgbZjf2+4WXlL4uW/xCWBcQvJbx5uM
D5UzGR3xDJLms5SQHoORNHayyBs3WdCpsrUJJBNIIImx76lzEmoBGYq/SWNlbA07
M+25tTKIlrS+aK9eJRa6RdSpFpI+WtHo3MVgimWB7yHlPNWdHtwd2vm1IFA5PVPz
1XACXeQ944FMXrAmFpdRh6jsXNdhM/E=
=eNRH
-END PGP SIGNATURE End Message ---

Bug#1007075: marked as done (dpkg-cross: please consider upgrading to 3.0 source format)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 20:35:04 +
with message-id 
and subject line Bug#1007075: fixed in dpkg-cross 2.6.19
has caused the Debian Bug report #1007075,
regarding dpkg-cross: please consider upgrading to 3.0 source format
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.)


-- 
1007075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dpkg-cross
Version: 2.6.18+nmu2
Severity: wishlist
Tags: bookworm sid
Usertags: format1.0 format1.0-kp-nv

Dear maintainer,

This package is among the few (1.9%) that still use source format 1.0 in
bookworm.  Please upgrade it to source format 3.0, as (1) this format has many
advantages, as documented in https://wiki.debian.org/Projects/DebSrc3.0 ; (2)
this contributes to standardization of packaging practices.

Please note that this is also a sign that the packaging of this software
could maybe benefit from a refresh. It might be a good opportunity to
look at other aspects as well.

This mass bug filing was discussed on debian-devel@:
https://lists.debian.org/debian-devel/2022/03/msg00074.html

Thanks

Lucas
--- End Message ---
--- Begin Message ---
Source: dpkg-cross
Source-Version: 2.6.19
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated dpkg-cross package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 24 Nov 2022 20:47:05 +0100
Source: dpkg-cross
Architecture: source
Version: 2.6.19
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Bastian Germann 
Closes: 1007075
Changes:
 dpkg-cross (2.6.19) unstable; urgency=medium
 .
   * QA upload.
   * Convert to 3.0 source format (Closes: #1007075).
   * d/copyright: Convert to machine-readable format.
Checksums-Sha1:
 813b864a1b77721a06380ba9668daa0c3ba0d0bd 1408 dpkg-cross_2.6.19.dsc
 2cab762ab5619ef6dd912162d6e2d7a8c2a3e976 63120 dpkg-cross_2.6.19.tar.xz
 8866829d4624f9fdbcb583466df9246ecee5c85d 5597 
dpkg-cross_2.6.19_source.buildinfo
Checksums-Sha256:
 bd41c9959fcfc85aee9deaeade16c01966a8e4958b02ff1476f3e2213ce4be03 1408 
dpkg-cross_2.6.19.dsc
 a309c9c9159bcbad38c19a72cb5c13e7d2875dc938113410fa876830cdefdf85 63120 
dpkg-cross_2.6.19.tar.xz
 8d39274213de2b82ed34873ec58427a9712afa0ea1a2d1149eeff5c84c176a05 5597 
dpkg-cross_2.6.19_source.buildinfo
Files:
 fbfc73b426a63b7e93fce64a194c12e1 1408 utils optional dpkg-cross_2.6.19.dsc
 ff0c8a62a9b7d796a463066f7413d046 63120 utils optional dpkg-cross_2.6.19.tar.xz
 7c7c4f7963ce72da733986bf53f34bd8 5597 utils optional 
dpkg-cross_2.6.19_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmN/y9gQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFHRJC/0RDgIb7lsbhWIZMhmmJp22yHpoXfLkLk8j
Nx4fEk4HlO2EbD5dAZpxKsNx2/cS+JCGoHvdJ1xzgtRbesEHS56X2gYazASgEH09
NB5ubq8u8QuPEn6YEsAVhwrzzgnezfj9VOnXWTztg/nimZnBvUE41TWu5a7qWNrB
2i2nRt39yzAyUEZaVR8zOGa1i0i1L7Q7OBFtOdfHR0WzWMrrIcpu2ODgD/76s+JE
KkSwG7u4NmMWE/EVqSlXlgaLl7g8bEI24QJWRKR9LgkfRkgtlGDpiaC9S+nQfjit
VJsnSjuGcc6Di+jFyRvzeHBUKaPTNKAB4CdZAnt5PLcHUH20t5PceulMEhrNt31L
13xTrVEAII0vf+RRpzpMEbcz1pXWt+X1JpMDQr9TS7U8gMrEfPbPGii0d1QuzWX5
XdKqcPHvjRT50gcbxxXTSqHnShxqVUD1nWlfaDIzlCZMZgC9ePcv9R15PGy7GhR2
m5zh9UqKXYLxaVkduWvK0mXPmpaEnGs=
=C0w/
-END PGP SIGNATURE End Message ---

Bug#1017496: marked as done (libgeocoding.so: needs to link with -lphonenumber)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 19:34:37 +
with message-id 
and subject line Bug#1017496: fixed in libphonenumber 8.12.57+ds-3
has caused the Debian Bug report #1017496,
regarding libgeocoding.so: needs to link with -lphonenumber
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.)


-- 
1017496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017496
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgeocoding8
Version: 8.12.51+ds-1
Severity: minor
File: /usr/lib/x86_64-linux-gnu/libgeocoding.so.8.12
User: debian...@lists.debian.org
Usertags: undefined-symbol adequate

libgeocoding.so needs to link with -lphonenumber, see the output of
adequate, symtree and objdump below. I detected this on amd64 but the
Debian build log scanner also detected dpkg-buildpackage complaining
about it on most architectures, see the w3m/getbuildlog output below.

I filed this bug at severity minor since I'm not sure if there are any
programs using the libgeocoding.so lib and if they already use the
libphonenumber.so symbols and link with the -lphonenumber flag or not. 

This bug report brought to you by adequate:

https://bonedaddy.net/pabs3/log/2013/02/23/inadequate-software/

$ lib=/usr/lib/x86_64-linux-gnu/libgeocoding.so.8.12
$ link=/usr/lib/x86_64-linux-gnu/libphonenumber.so.8.12
$ pkg="$(dpkg-query --search "$lib" | sed s/:.*//)"
$ src="$(grep-aptavail --no-field-names --show-field Source:Package --field 
Package --exact-match --pattern "$pkg" | sed 's/ .*//')"
$ first="$(printf '%s' "$src" | head --bytes 1)"

$ adequate "$pkg" | c++filt
libgeocoding8:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libgeocoding.so.8.12 => 
i18n::phonenumbers::PhoneNumberUtil::kRegionCodeForNonGeoEntity
libgeocoding8:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libgeocoding.so.8.12 => 
i18n::phonenumbers::PhoneNumberUtil::GetRegionCodeForNumber(i18n::phonenumbers::PhoneNumber
 const&, std::__cxx11::basic_string, 
std::allocator >*) const
libgeocoding8:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libgeocoding.so.8.12 => 
i18n::phonenumbers::PhoneNumberUtil::GetInstance()
libgeocoding8:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libgeocoding.so.8.12 => 
i18n::phonenumbers::PhoneNumberUtil::GetNationalSignificantNumber(i18n::phonenumbers::PhoneNumber
 const&, std::__cxx11::basic_string, 
std::allocator >*) const
libgeocoding8:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libgeocoding.so.8.12 => 
i18n::phonenumbers::SimpleItoa[abi:cxx11](int)
libgeocoding8:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libgeocoding.so.8.12 => 
i18n::phonenumbers::PhoneNumberUtil::IsNumberGeographical(i18n::phonenumbers::PhoneNumberUtil::PhoneNumberType,
 int) const
libgeocoding8:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libgeocoding.so.8.12 => 
i18n::phonenumbers::PhoneNumberUtil::GetNumberType(i18n::phonenumbers::PhoneNumber
 const&) const
libgeocoding8:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libgeocoding.so.8.12 => 
i18n::phonenumbers::safe_strto64(std::__cxx11::basic_string, std::allocator > const&, long*)
libgeocoding8:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libgeocoding.so.8.12 => 
i18n::phonenumbers::SimpleItoa[abi:cxx11](long)

$ man adequate | grep -A4 undefined-symbol
   undefined-symbol
   The symbol has not been found in the libraries linked with the 
binary.  Either the binary either needs to be linked with an additional shared 
library, or the dependency
   on the shared library package that provides this symbol is too weak.

   References: Debian Policy §3.5, §8.6, §10.2.

$ lddtree "$lib"
libgeocoding.so.8.12 => /usr/lib/x86_64-linux-gnu/libgeocoding.so.8.12 
(interpreter => none)
    libicuuc.so.71 => /usr/lib/x86_64-linux-gnu/libicuuc.so.71
    libicudata.so.71 => /usr/lib/x86_64-linux-gnu/libicudata.so.71
    libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
    libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2
    libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6
    ld-linux-x86-64.so.2 => /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
    libabsl_synchronization.so.20210324 => 
/usr/lib/x86_64-linux-gnu/libabsl_synchronization.so.20210324
    libabsl_graphcycles_internal.so.20210324 => 
/usr/lib/x86_64-linux-gnu/libabsl_graphcycles_internal.so.20210324
    libabsl_stacktrace.so.20210324 => 
/usr/lib/x86_64-linux-gnu/libabsl_stacktrace.so.20210324
    libabsl_debugging_internal.so.20210324 => 
/usr/lib/x86_64-linux-gnu/libabsl_debugging_internal.so.20210324
    

Bug#1024768: marked as done (libphonenumber: FTBFS after switch to debhelper)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 19:34:37 +
with message-id 
and subject line Bug#1024768: fixed in libphonenumber 8.12.57+ds-3
has caused the Debian Bug report #1024768,
regarding libphonenumber: FTBFS after switch to debhelper
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.)


-- 
1024768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024768
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libphonenumber
Version: 8.12.57+ds-2
Severity: serious

Creating this for tracking and coordination purposes.  After this [1]
upload, libphonenumber is FTBFS.  Please refer to the buildd logs [2].

[1] 
https://tracker.debian.org/news/1389357/accepted-libphonenumber-81257ds-2-source-into-unstable/
[2] https://buildd.debian.org/status/package.php?p=libphonenumber
--- End Message ---
--- Begin Message ---
Source: libphonenumber
Source-Version: 8.12.57+ds-3
Done: Jochen Sprickerhof 

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 24 Nov 2022 20:17:13 +0100
Source: libphonenumber
Architecture: source
Version: 8.12.57+ds-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Jochen Sprickerhof 
Closes: 1017496 1024768
Changes:
 libphonenumber (8.12.57+ds-3) unstable; urgency=medium
 .
   * Team upload.
   * Add patch to link geocoding-shared with phonenumber-shared
 (Closes: #1017496)
   * Build java lib in arch any builds (Closes: #1024768)
Checksums-Sha1:
 065489aca6dce6b8b69fc97a177a07d0530168d8 2899 libphonenumber_8.12.57+ds-3.dsc
 1855daa06b545e888fe50b9580cb1f327b44095a 12300 
libphonenumber_8.12.57+ds-3.debian.tar.xz
 ea9df596790089aa556b8146236d6afcfc8be5e5 19103 
libphonenumber_8.12.57+ds-3_source.buildinfo
Checksums-Sha256:
 8d7bc92ef866c125aa39c52ce8c2ae20b5f2243c7754012a2ec73cee98d9a0e2 2899 
libphonenumber_8.12.57+ds-3.dsc
 77cb18483834a5a0c22e55bb1a094eac6a698d47a382685f649503468fa09814 12300 
libphonenumber_8.12.57+ds-3.debian.tar.xz
 c2487f189b6d29a21c42bd4c89fd007f5eeed23ed84052c89ad5e344acb7e6ec 19103 
libphonenumber_8.12.57+ds-3_source.buildinfo
Files:
 9e21728dc2664939e0761101551a3acc 2899 libs optional 
libphonenumber_8.12.57+ds-3.dsc
 48c9e64a3d6b167cf60e039cff53e663 12300 libs optional 
libphonenumber_8.12.57+ds-3.debian.tar.xz
 c53b6759e7675e49f22b80247c10ee80 19103 libs optional 
libphonenumber_8.12.57+ds-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAmN/w14ACgkQW//cwljm
lDPTqxAAnTk0z99iIIhQLJ+WKLb1o3RkSRCq/tWS8j7aJVjYpdY6jyQIxf3SZ2d4
nv6I7qHuERW/o+FcHjs0Ie0VCvIGl2bWU3v+dYAREE/jY+lPzPD3UObo4prLLG86
fT9R+RPqGnVfsgPPQc0YUhYUKPLtUgeoJBOd6BNKcElJ7jRWlk4Q5jXat6Gp6bz3
tOdhOoaO4swIEkLCYiBQ6argx8A363npV3xWwJ4eVZ5cM36QKhHwf1vunvbnTeMu
+0AFALioSObWORCz8bzHAQVKNCjV51ViCV/E4nAKrT8zdbysQgUVJMFrxPa9Wty6
nvB2Dnev1D0byngKfJV5zACYSPMWcmJ63Wyuan2GBfQCuq5QjEBLQn+C6P2yI8a9
kmqUsNNCp7r62diWXhLrhWRyksxuquot8dXSwoGebmzTPZifboCTLTVw23ztS9e+
EqzKVaEUAWrb8kCOCmGfYStthoq7whRij35lTDTc5Ekq2OpeLOCC83+kdnxMKP/9
lfICPVoUWOi5SGXEmVGJ0J2zkESrhX7qahJlD0V15Bqw+yTn4KYvYQm0UOqsDAYz
AAUlhioCKqZHVM+qzTUrW8R+OgVjY68Tj/jNa33KYhcOa8PZuhUoeD7yaMjqTat5
5jCPTztn0j/BeayDXCwjg2QJD43dNwhenpRzXlbG8aRW4/kJweI=
=kMsB
-END PGP SIGNATURE End Message ---

Bug#1023379: marked as done (git-buildpackage: FTBFS with Git 2.38.1)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 19:19:16 +
with message-id 
and subject line Bug#1023379: fixed in git-buildpackage 0.9.30
has caused the Debian Bug report #1023379,
regarding git-buildpackage: FTBFS with Git 2.38.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.)


-- 
1023379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023379
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: git-buildpackage
Version: 0.9.29
Severity: normal
User: de...@kali.org
Usertags: origin-kali

Dear Maintainer,

I tried to rebuild git-buildpackage locally and the submodule tests
fail:


==
ERROR: Add a submodule
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 
"/build/git-buildpackage-JtfSq8/git-buildpackage-0.9.29/tests/04_test_submodules.py",
 line 99, in test_add_submodule
REPO.add_submodule(SUBMODULES[0].dir)
  File 
"/build/git-buildpackage-JtfSq8/git-buildpackage-0.9.29/gbp/git/repository.py", 
line 1938, in add_submodule
self._git_command("submodule", ["add", repo_path])
  File 
"/build/git-buildpackage-JtfSq8/git-buildpackage-0.9.29/gbp/git/repository.py", 
line 245, in _git_command
raise GitRepositoryError("Error running git %s: %s" % (command, 
detail.decode().strip()))
gbp.git.repository.GitRepositoryError: Error running git submodule: Cloning 
into '/tmp/tmp7tjw_zrzgbp_tests.04_test_submodules_/test_repo/test_submodule'...
fatal: transport 'file' not allowed
fatal: clone of '/tmp/tmp7tjw_zrzgbp_tests.04_test_submodules_/test_submodule' 
into submodule path 
'/tmp/tmp7tjw_zrzgbp_tests.04_test_submodules_/test_repo/test_submodule' failed
 >> begin captured logging << 
gbp: debug: ['git', 'submodule', 'add', 
'/tmp/tmp7tjw_zrzgbp_tests.04_test_submodules_/test_submodule']
- >> end captured logging << -


This is due to a recent change in Git, and it's documented at:
* 
https://vielmetti.typepad.com/logbook/2022/10/git-security-fixes-lead-to-fatal-transport-file-not-allowed-error-in-ci-systems-cve-2022-39253.html
* https://bugs.launchpad.net/ubuntu/+source/git/+bug/1993586

Please find a tentative fix at:
https://salsa.debian.org/arnaudr/git-buildpackage/-/commit/5a73cf0e

I tried using REPO.set_config() but it didn't work, so I used the
environment instead.

Best,

Arnaud



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

Kernel: Linux 6.0.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: 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 git-buildpackage depends on:
ii  devscripts 2.22.2
ii  git1:2.37.2-1
ii  man-db 2.11.0-1+b1
ii  python33.10.6-1
ii  python3-dateutil   2.8.2-1
ii  python3-pkg-resources  65.5.0-1
ii  python3-yaml   5.4.1-1+b2
ii  sensible-utils 0.0.17

Versions of packages git-buildpackage recommends:
ii  pristine-tar  1.49
ii  python3-requests  2.27.1+dfsg-1
ii  sbuild0.83.2

Versions of packages git-buildpackage suggests:
pn  python3-notify2  
ii  sudo 1.9.11p3-2
ii  unzip6.0-27

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: git-buildpackage
Source-Version: 0.9.30
Done: Guido Günther 

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

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

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

Debian distribution maintenance software
pp.
Guido Günther  (supplier of updated git-buildpackage package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 24 

Bug#1008014: marked as done (python3-blinker: DeprecationWarning with Python 3.10: invalid escape sequence '\*')

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 19:04:03 +
with message-id 
and subject line Bug#1008014: fixed in blinker 1.5-1
has caused the Debian Bug report #1008014,
regarding python3-blinker: DeprecationWarning with Python 3.10: invalid escape 
sequence '\*'
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.)


-- 
1008014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008014
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-blinker
Version: 1.4+dfsg1-0.4
Severity: normal
Tags: upstream

I am getting the following warning:

../../../../../../../../../../usr/lib/python3/dist-packages/blinker/base.py:93
  /usr/lib/python3/dist-packages/blinker/base.py:93: DeprecationWarning: 
invalid escape sequence '\*'
"""Connect *receiver* to signal events sent by *sender*.

and two other similar ones.

Upstream have fixed this (https://github.com/jek/blinker, commit
https://github.com/jek/blinker/commit/194e17a20008bd778714182ac191ad654074f81c
on 28 Oct 2020) but have not officially released a new version of the
package.

Perhaps you could either cherry-pick this fix, or upload the current
GitHub version of the package?

Best wishes,

   Julian
--- End Message ---
--- Begin Message ---
Source: blinker
Source-Version: 1.5-1
Done: Carsten Schoenert 

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

Debian distribution maintenance software
pp.
Carsten Schoenert  (supplier of updated blinker 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 24 Nov 2022 19:20:48 +0100
Source: blinker
Architecture: source
Version: 1.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Carsten Schoenert 
Closes: 1008014 1018323
Changes:
 blinker (1.5-1) unstable; urgency=medium
 .
   * Team upload.
   * d/watch: Switch to git mode on the GitHub repository
   * d/gbp.conf: Add some basic default configuration
   * New upstream version 1.5
 (Closes: #1008014 )
   * d/copyright: Update upstream data and content
   * d/README.source: Adding base information about source
   * d/control: Run wrap-and-sort -ast
   * d/control: Sort binary packages alphabetical
   * d/u/metadata: Update and add content
   * d/control: Updating the package descriptions
   * d/control: Update Homepage field to new URL
   * d/control: Bump Standards-Version to 4.6.1
 No further changes needed.
   * d/control: Update build dependencies
   * d/rules: Use PYBUILD variable to build the package
 (Closes: #1018323)
   * python-blinker-doc: Use dh_sphinxdoc for package build
   * autopkgtest: Run upstream tests for basic testing
Checksums-Sha1:
 52d65c65b5a6527e0200c39c46ce60e9eb842fe0 2229 blinker_1.5-1.dsc
 2afe9c9e4616420cf773e318ce2d5744fe907796 25094 blinker_1.5.orig.tar.gz
 4992c01039cd92046fc63098b7bdab4406174d8e 5624 blinker_1.5-1.debian.tar.xz
 49912fab83b8baec33bb514f5e5ae73d7a798482 8252 blinker_1.5-1_amd64.buildinfo
Checksums-Sha256:
 f75be1bce97602b699f829d5a7400a819523fb61d6fc9f37b400184160176143 2229 
blinker_1.5-1.dsc
 96e236b53f83c48d2433710e38e39c897491581b638c3d8260eb60650adb3afe 25094 
blinker_1.5.orig.tar.gz
 c35bca33ec4c7cba8b1c4d5249e422ab857b625b0bad004796f694afb578eeaf 5624 
blinker_1.5-1.debian.tar.xz
 f175607803469259f7e8904078643788a6398fbdda1597aac77b4d73fdbb242a 8252 
blinker_1.5-1_amd64.buildinfo
Files:
 f162424da9cd0b551c543a66dcee2f49 2229 python optional blinker_1.5-1.dsc
 5043776b4eba26025f34d1f8c4b802c7 25094 python optional blinker_1.5.orig.tar.gz
 3f54dd6649d5719410b034ecb1898cd7 5624 python optional 
blinker_1.5-1.debian.tar.xz
 93a5ed62132e564d188a17f53e416f6d 8252 python optional 
blinker_1.5-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJMBAEBCgA2FiEEtw38bxNP7PwBHmKqgwFgFCUdHbAFAmN/uiEYHGMuc2Nob2Vu
ZXJ0QHQtb25saW5lLmRlAAoJEIMBYBQlHR2wEmgP/iPLzJRjlV3FRblZ58dfPbag
YkhSz5UmJqJ+it8iIx57hOU0YRScvMEzmGV1/jhYCsdtLfwN2MhgGdL0BdaJtlli
l/6/VkckZsaa2Jr/jm4v+zt2YFtnNxfXYY04TEqIwdl6S9U8JgwTac9t9MUC5kNt
cmmBY7ispD3SvibERJVHOzeQ5wP8hz2VDX45JUx3rGxt8acGXw+z/t3/hD0Gs4BZ

Bug#1018323: marked as done (blinker: build-depends on python3-nose or uses it for autopkgtest)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 19:04:03 +
with message-id 
and subject line Bug#1018323: fixed in blinker 1.5-1
has caused the Debian Bug report #1018323,
regarding blinker: build-depends on python3-nose or uses it for autopkgtest
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.)


-- 
1018323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018323
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: blinker
Version: 1.4+dfsg1-0.5
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm

Dear Maintainer,

Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].

If you received this bug report, it means that your package either has a
build-dependency on python3-nose or uses that package in debian/tests/control.
If that is not the case, please reply and CC me explicitly.

Please port your package to one of the alternatives: nose2 [4], pytest [5]
or unittest from Python standard library [6].

There is a script called nose2pytest [7] which can assist with migrating from
nose to pytest.

This mass bug filing was discussed on debian-devel in [8].

[1]: https://tracker.debian.org/pkg/nose
[2]: https://github.com/nose-devs/nose/commit/0f40fa995384afad
[3]: https://pypi.org/project/nose/#history
[4]: https://docs.nose2.io/en/latest/
[5]: https://docs.pytest.org/en/latest/
[6]: https://docs.python.org/3/library/unittest.html
[7]: https://github.com/pytest-dev/nose2pytest
[8]: https://lists.debian.org/debian-devel/2022/08/msg00184.html

--
Dmitry Shachnev
--- End Message ---
--- Begin Message ---
Source: blinker
Source-Version: 1.5-1
Done: Carsten Schoenert 

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

Debian distribution maintenance software
pp.
Carsten Schoenert  (supplier of updated blinker 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 24 Nov 2022 19:20:48 +0100
Source: blinker
Architecture: source
Version: 1.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Carsten Schoenert 
Closes: 1008014 1018323
Changes:
 blinker (1.5-1) unstable; urgency=medium
 .
   * Team upload.
   * d/watch: Switch to git mode on the GitHub repository
   * d/gbp.conf: Add some basic default configuration
   * New upstream version 1.5
 (Closes: #1008014 )
   * d/copyright: Update upstream data and content
   * d/README.source: Adding base information about source
   * d/control: Run wrap-and-sort -ast
   * d/control: Sort binary packages alphabetical
   * d/u/metadata: Update and add content
   * d/control: Updating the package descriptions
   * d/control: Update Homepage field to new URL
   * d/control: Bump Standards-Version to 4.6.1
 No further changes needed.
   * d/control: Update build dependencies
   * d/rules: Use PYBUILD variable to build the package
 (Closes: #1018323)
   * python-blinker-doc: Use dh_sphinxdoc for package build
   * autopkgtest: Run upstream tests for basic testing
Checksums-Sha1:
 52d65c65b5a6527e0200c39c46ce60e9eb842fe0 2229 blinker_1.5-1.dsc
 2afe9c9e4616420cf773e318ce2d5744fe907796 25094 blinker_1.5.orig.tar.gz
 4992c01039cd92046fc63098b7bdab4406174d8e 5624 blinker_1.5-1.debian.tar.xz
 49912fab83b8baec33bb514f5e5ae73d7a798482 8252 blinker_1.5-1_amd64.buildinfo
Checksums-Sha256:
 f75be1bce97602b699f829d5a7400a819523fb61d6fc9f37b400184160176143 2229 
blinker_1.5-1.dsc
 96e236b53f83c48d2433710e38e39c897491581b638c3d8260eb60650adb3afe 25094 
blinker_1.5.orig.tar.gz
 c35bca33ec4c7cba8b1c4d5249e422ab857b625b0bad004796f694afb578eeaf 5624 
blinker_1.5-1.debian.tar.xz
 f175607803469259f7e8904078643788a6398fbdda1597aac77b4d73fdbb242a 8252 
blinker_1.5-1_amd64.buildinfo
Files:
 f162424da9cd0b551c543a66dcee2f49 2229 python optional blinker_1.5-1.dsc
 5043776b4eba26025f34d1f8c4b802c7 25094 python optional blinker_1.5.orig.tar.gz
 3f54dd6649d5719410b034ecb1898cd7 5624 python optional 
blinker_1.5-1.debian.tar.xz
 93a5ed62132e564d188a17f53e416f6d 8252 python optional 

Processed: your mail

[Debian Bug Tracking System]

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

> close 1024776
Bug #1024776 [wnpp] ITP: golang-github-slackhq-nebula -- scalable overlay 
networking (Go library)
Marked Bug as done
>
End of message, stopping processing here.

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

Bug#1014060: marked as done (golang-github-masterminds-sprig FTBFS due to build-time test failure)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 18:49:37 +
with message-id 
and subject line Bug#1014060: fixed in golang-github-masterminds-sprig 3.2.2-1
has caused the Debian Bug report #1014060,
regarding golang-github-masterminds-sprig FTBFS due to build-time test failure
to be marked as done.

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

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


-- 
1014060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014060
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: golang-github-masterminds-sprig
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic ubuntu-patch

Dear Maintainer,

There is a build-time test using network access, which will not work
in Debian/Ubuntu package build environments.

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

 * Resolve FTBFS by skipping test that requires network access

Thanks for considering the patch.


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

Kernel: Linux 5.15.0-27-generic (SMP w/32 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru 
golang-github-masterminds-sprig-3.2.1/debian/patches/0001-skip-network-test.patch
 
golang-github-masterminds-sprig-3.2.1/debian/patches/0001-skip-network-test.patch
--- 
golang-github-masterminds-sprig-3.2.1/debian/patches/0001-skip-network-test.patch
   1969-12-31 18:00:00.0 -0600
+++ 
golang-github-masterminds-sprig-3.2.1/debian/patches/0001-skip-network-test.patch
   2022-06-29 10:04:49.0 -0500
@@ -0,0 +1,22 @@
+Description: Skip test that requires network access
+ There is a build-time test in this package that is failing
+ due to a lack of network access. Skip it to enable building
+ of the package
+Author: William 'jawn-smith' Wilson 
+Last-Update: 2022-06-29
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+Index: golang-github-masterminds-sprig-3.2.1/network_test.go
+===
+--- golang-github-masterminds-sprig-3.2.1.orig/network_test.go
 golang-github-masterminds-sprig-3.2.1/network_test.go
+@@ -8,6 +8,9 @@
+ )
+ 
+ func TestGetHostByName(t *testing.T) {
++  // This test requires network access, which does not
++  // work in package build environments
++  t.Skip()
+   tpl := `{{"www.google.com" | getHostByName}}`
+ 
+   resolvedIP, _ := runRaw(tpl, nil)
diff -Nru golang-github-masterminds-sprig-3.2.1/debian/patches/series 
golang-github-masterminds-sprig-3.2.1/debian/patches/series
--- golang-github-masterminds-sprig-3.2.1/debian/patches/series 1969-12-31 
18:00:00.0 -0600
+++ golang-github-masterminds-sprig-3.2.1/debian/patches/series 2022-06-29 
10:04:49.0 -0500
@@ -0,0 +1 @@
+0001-skip-network-test.patch
--- End Message ---
--- Begin Message ---
Source: golang-github-masterminds-sprig
Source-Version: 3.2.2-1
Done: Peymaneh 

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

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

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

Debian distribution maintenance software
pp.
Peymaneh  (supplier of updated 
golang-github-masterminds-sprig package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 24 Nov 2022 19:29:43 +0100
Source: golang-github-masterminds-sprig
Binary: golang-github-masterminds-sprig-dev
Architecture: source all
Version: 3.2.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Peymaneh 
Description:
 golang-github-masterminds-sprig-dev - Useful template functions for Go 
templates (library)
Closes: 1014060
Changes:
 golang-github-masterminds-sprig (3.2.2-1) unstable; urgency=medium
 .
   * New upstream version 3.2.2
   * d/patches: Skip tests that require network access (Closes: 

Bug#1024737: marked as done (tiff: CVE-2022-3970: TIFFReadRGBATileExt(): fix (unsigned) integer overflow on strips/tiles > 2 GB)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 18:21:19 +
with message-id 
and subject line Bug#1024737: fixed in tiff 4.4.0-6
has caused the Debian Bug report #1024737,
regarding tiff: CVE-2022-3970: TIFFReadRGBATileExt(): fix (unsigned) integer 
overflow on strips/tiles > 2 GB
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.)


-- 
1024737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024737
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tiff
Version: 4.4.0-5
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for tiff.

CVE-2022-3970[0]:
| A vulnerability was found in LibTIFF. It has been classified as
| critical. This affects the function TIFFReadRGBATileExt of the file
| libtiff/tif_getimage.c. The manipulation leads to integer overflow. It
| is possible to initiate the attack remotely. The exploit has been
| disclosed to the public and may be used. The name of the patch is
| 227500897dfb07fb7d27f7aa570050e62617e3be. It is recommended to apply a
| patch to fix this issue. The identifier VDB-213549 was assigned to
| this vulnerability.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-3970
https://www.cve.org/CVERecord?id=CVE-2022-3970
[1] https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=53137
[2] 
https://gitlab.com/libtiff/libtiff/-/commit/227500897dfb07fb7d27f7aa570050e62617e3be

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: tiff
Source-Version: 4.4.0-6
Done: Laszlo Boszormenyi (GCS) 

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

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

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated tiff package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 24 Nov 2022 17:54:18 +0100
Source: tiff
Architecture: source
Version: 4.4.0-6
Distribution: unstable
Urgency: high
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 1024670 1024737
Changes:
 tiff (4.4.0-6) unstable; urgency=high
 .
   * Backport security fix for CVE-2022-2519, double free or corruption in
 rotateImage() (closes: #1024670).
   * Backport security fix for CVE-2022-2520, sysmalloc assertion fail in
 rotateImage().
   * Backport security fix for CVE-2022-2521, invalid pointer free operation
 in TIFFClose().
   * Backport security fix for CVE-2022-2953, out-of-bounds read in
 extractImageSection().
   * Backport security fix for CVE-2022-3970, fix (unsigned) integer overflow
 on strips/tiles > 2 GB in TIFFReadRGBATileExt() (closes: #1024737).
Checksums-Sha1:
 54526a597709e13559b9e3fb7c7599426f43e44e 2238 tiff_4.4.0-6.dsc
 ae9dab47d4495cf502b42addbd085885e4319283 33680 tiff_4.4.0-6.debian.tar.xz
Checksums-Sha256:
 39f656d60cb0a75ae02fad9c16eb0c275c8a4bcb7efb02898c8c9bcfcf83b5f5 2238 
tiff_4.4.0-6.dsc
 37c1e4a7151c3790404e94a137825856f4d1f8fe8a8d3253a455ddff648f329b 33680 
tiff_4.4.0-6.debian.tar.xz
Files:
 07f8a7896c660806d4161644e07734c3 2238 libs optional tiff_4.4.0-6.dsc
 0fadacf944b89734f191bdd67508c42b 33680 libs optional tiff_4.4.0-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAmN/sCMACgkQ3OMQ54ZM
yL//Tg//alHP1u6T/H4pimYiAQKjFqcnVdPzY2tkwOkQiNJjKPQlD2ICzB35MzjE
gbeijGgmh+6m51i0kV2LvpaTsbY7C3i6/soN7nhDo0MxU3k47n0LTZXcFQ3V6OGp
THNYGQsfZ9CRFmVMNxF/ZzOs7LOOPsbKnUe92lQAiUWptJubAaZr9Uc/LnBHuv+f
iuykwMfs4GWc6mYjjYKYho5sDT76R7O57L2r8PO4NR5rKes6Qg2RKu9upp9kKZjI
r2pbrgiSBOg3b5yywU4sT5NVJLvoUJW6Zm4a/QBjzd2tacc5VRb4+igYlhzSsn+J
Ov1cOXEcphwn34mOvM5fyS3M32vAX/Hto4NwHZDaN+RjZnlTLMrATb1OJGYzSTww
V3xJ/YuJl7m9niMUfZSGR/AUgx+rTKHRqv5umE1GrHlITnn5g7XK0VjMz7Q+Jjya
V3aEv93tus/MB+g+REmhgpmXkQAxa67YyHDToeolLeuPPTtDZ+2JxtUsnUOfotWu

Bug#1024670: marked as done (tiff: CVE-2022-2519 CVE-2022-2520 CVE-2022-2521 CVE-2022-2953)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 18:21:19 +
with message-id 
and subject line Bug#1024670: fixed in tiff 4.4.0-6
has caused the Debian Bug report #1024670,
regarding tiff: CVE-2022-2519 CVE-2022-2520 CVE-2022-2521 CVE-2022-2953
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.)


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

Source: tiff
Version: 4.4.0-5
Severity: important
Tags: security

Hello,

The following vulnerabilities had been published for tiff:

CVE-2022-2519[0]:
| There is a double free or corruption in rotateImage() at
| tiffcrop.c:8839 found in libtiff 4.4.0rc1

https://gitlab.com/libtiff/libtiff/-/issues/423
https://gitlab.com/libtiff/libtiff/-/merge_requests/378
https://gitlab.com/libtiff/libtiff/-/commit/8fe3735942ea1d90d8cef843b55b3efe8ab6feaf
https://gitlab.com/libtiff/libtiff/-/commit/bad48e90b410df32172006c7876da449ba62cdba

CVE-2022-2520[1]:
| A flaw was found in libtiff 4.4.0rc1. There is a sysmalloc assertion
| fail in rotateImage() at tiffcrop.c:8621 that can cause program crash
| when reading a crafted input.

https://gitlab.com/libtiff/libtiff/-/issues/424
https://gitlab.com/libtiff/libtiff/-/merge_requests/378
https://gitlab.com/libtiff/libtiff/-/commit/8fe3735942ea1d90d8cef843b55b3efe8ab6feaf
https://gitlab.com/libtiff/libtiff/-/commit/bad48e90b410df32172006c7876da449ba62cdba

CVE-2022-2521[2]:
| It was found in libtiff 4.4.0rc1 that there is an invalid pointer free
| operation in TIFFClose() at tif_close.c:131 called by tiffcrop.c:2522
| that can cause a program crash and denial of service while processing
| crafted input.

https://gitlab.com/libtiff/libtiff/-/issues/422
https://gitlab.com/libtiff/libtiff/-/merge_requests/378
https://gitlab.com/libtiff/libtiff/-/commit/8fe3735942ea1d90d8cef843b55b3efe8ab6feaf
https://gitlab.com/libtiff/libtiff/-/commit/bad48e90b410df32172006c7876da449ba62cdba

CVE-2022-2953[3]:
| LibTIFF 4.4.0 has an out-of-bounds read in extractImageSection in
| tools/tiffcrop.c:6905, allowing attackers to cause a denial-of-service
| via a crafted tiff file. For users that compile libtiff from sources,
| the fix is available with commit 48d6ece8.

https://gitlab.com/libtiff/libtiff/-/issues/414
https://gitlab.com/libtiff/libtiff/-/commit/8fe3735942ea1d90d8cef843b55b3efe8ab6feaf
https://gitlab.com/libtiff/libtiff/-/commit/bad48e90b410df32172006c7876da449ba62cdba

I saw they are marked as "unimportant" in Debian's security tracker,
but I thought I would file this bug report anyway.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-2519
https://www.cve.org/CVERecord?id=CVE-2022-2519
[1] https://security-tracker.debian.org/tracker/CVE-2022-2520
https://www.cve.org/CVERecord?id=CVE-2022-2520
[2] https://security-tracker.debian.org/tracker/CVE-2022-2521
https://www.cve.org/CVERecord?id=CVE-2022-2521
[3] https://security-tracker.debian.org/tracker/CVE-2022-2953
https://www.cve.org/CVERecord?id=CVE-2022-2953

Please adjust the affected versions in the BTS as needed.

Best,
amin
--- End Message ---
--- Begin Message ---
Source: tiff
Source-Version: 4.4.0-6
Done: Laszlo Boszormenyi (GCS) 

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

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

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated tiff package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 24 Nov 2022 17:54:18 +0100
Source: tiff
Architecture: source
Version: 4.4.0-6
Distribution: unstable
Urgency: high
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 1024670 1024737
Changes:
 tiff (4.4.0-6) unstable; urgency=high
 .
   * Backport security fix for CVE-2022-2519, double free or corruption in
 rotateImage() (closes: #1024670).
   * Backport security fix for CVE-2022-2520, 

Bug#1022748: marked as done (libqt5gui5: hide() + show() + hide() on a dialog frame hides it forever under X)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 18:09:11 +
with message-id 
and subject line Bug#1022748: fixed in qtbase-opensource-src 5.15.6+dfsg-4
has caused the Debian Bug report #1022748,
regarding libqt5gui5: hide() + show() + hide() on a dialog frame hides it 
forever under X
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.)


-- 
1022748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022748
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libqt5gui5
Version: 5.15.6+dfsg-2
Severity: important
X-Debbugs-Cc: sh200...@mail.ru

Control: notfound -1 5.15.4+dfsg-5
Control: found -1 5.15.6+dfsg-2

Attaching the example project. There are two buttons that preform some actions
with the second window: Show does show(), and Hide does hide() + show() +
hide().

If you compile the project and first press Hide, then press Show, then the
second window won't be shown again.

The expected result is that the second window will reappear after pressing
Show.

This is a regression in 5.15.6+dfsg-2 since 5.15.4+dfsg-5 works just fine in
this case.

The bug is only reproducible under X, and Wayland is not affected.

Currently, this bug breaks code completion in ktexteditor and its dependencies
(Kate, KDevelop etc.)


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

Kernel: Linux 5.19.0-2-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE=ru
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libqt5gui5 depends on:
ii  fontconfig2.13.1-4.5
ii  libc6 2.35-3
ii  libdrm2   2.4.113-2
ii  libegl1   1.5.0-1
ii  libfontconfig12.13.1-4.5
ii  libfreetype6  2.12.1+dfsg-3
ii  libgbm1   22.2.0-1
ii  libgcc-s1 12.2.0-3
ii  libgl11.5.0-1
ii  libglib2.0-0  2.74.0-3
ii  libharfbuzz0b 5.2.0-2
ii  libice6   2:1.0.10-1
ii  libinput101.21.0-1
ii  libjpeg62-turbo   1:2.1.2-1+b1
ii  libmd4c0  0.4.8-1
ii  libmtdev1 1.1.6-1
ii  libpng16-16   1.6.38-2
ii  libqt5core5a [qtbase-abi-5-15-6]  5.15.6+dfsg-2
ii  libqt5dbus5   5.15.6+dfsg-2
ii  libqt5network55.15.6+dfsg-2
ii  libsm62:1.2.3-1
ii  libstdc++612.2.0-3
ii  libudev1  251.6-1
ii  libx11-6  2:1.8.1-2
ii  libx11-xcb1   2:1.8.1-2
ii  libxcb-glx0   1.15-1
ii  libxcb-icccm4 0.4.1-1.1
ii  libxcb-image0 0.4.0-2
ii  libxcb-keysyms1   0.4.0-1+b2
ii  libxcb-randr0 1.15-1
ii  libxcb-render-util0   0.3.9-1+b1
ii  libxcb-render01.15-1
ii  libxcb-shape0 1.15-1
ii  libxcb-shm0   1.15-1
ii  libxcb-sync1  1.15-1
ii  libxcb-xfixes01.15-1
ii  libxcb-xinerama0  1.15-1
ii  libxcb-xinput01.15-1
ii  libxcb-xkb1   1.15-1
ii  libxcb1   1.15-1
ii  libxkbcommon-x11-01.4.1-1
ii  libxkbcommon0 1.4.1-1
ii  libxrender1   1:0.9.10-1.1
ii  zlib1g1:1.2.11.dfsg-4.1

Versions of packages libqt5gui5 recommends:
ii  libqt5svg5 5.15.6-2
pn  qt5-gtk-platformtheme  

Versions of packages libqt5gui5 suggests:
ii  qt5-image-formats-plugins  5.15.6-2
ii  qtwayland5 5.15.6-2

-- no debconf information


bug.tar.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: qtbase-opensource-src
Source-Version: 5.15.6+dfsg-4
Done: Dmitry Shachnev 

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

Bug#1024679: marked as done (dxf2gcode: Clean more generated files before and after build)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 16:34:56 +
with message-id 
and subject line Bug#1024679: fixed in dxf2gcode 20170925-5
has caused the Debian Bug report #1024679,
regarding dxf2gcode: Clean more generated files before and after build
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.)


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

Package: dxf2gcode
Version: 20170925-4
Tags: patch

To make it easier to rebuild the source package, I suggest to do some
more cleaning after build:

diff --git a/debian/rules b/debian/rules
index c86b1a6..6d787c1 100755
--- a/debian/rules
+++ b/debian/rules
@@ -8,6 +8,8 @@ override_dh_auto_clean:
rm -rf dxf2gcode_images5_rc.py \
   dxf2gcode_ui5.py \
   dxf2gcode.egg-info/ \
+  dxf2gcode/globals/__pycache__/ \
+  dxf2gcode/__pycache__/ \
   globals/__pycache__/ \
   i18n/*.qm
 
-- 
Happy hacking
Petter Reinholdtsen
--- End Message ---
--- Begin Message ---
Source: dxf2gcode
Source-Version: 20170925-5
Done: Petter Reinholdtsen 

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

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

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

Debian distribution maintenance software
pp.
Petter Reinholdtsen  (supplier of updated dxf2gcode package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 24 Nov 2022 17:11:19 +0100
Source: dxf2gcode
Architecture: source
Version: 20170925-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Petter Reinholdtsen 
Closes: 1001879 1022387 1024679
Changes:
 dxf2gcode (20170925-5) unstable; urgency=medium
 .
   * Team upload.
   * Clean more generated files before and after build. (Closes: #1024679)
   * Updated Standards-Version, copyright and added d/watch. (Closes: #1001879)
   * Adjusted debian/rules for recent setuptool changes. (Closes: #1022387)
   * Updated d/gbp.conf to enforce use of pristine-tar.
Checksums-Sha1:
 8a8f55c82ed9d534436bfad8e6c218fcf4e5461f 2064 dxf2gcode_20170925-5.dsc
 92b1d21a68acde9e34fac2653aba2a35e89dafa3 14104 
dxf2gcode_20170925-5.debian.tar.xz
 e303e32361e98b2d3808ca44541afce058b1a3d9 5 
dxf2gcode_20170925-5_source.buildinfo
Checksums-Sha256:
 c2a1c88872c1614b9d989bf4c88b5b561a5dff9d9c4211d51dfb7c59fb681885 2064 
dxf2gcode_20170925-5.dsc
 a8deb28f26cc7dd57048d429f8e6e486ef2c7fd3bbeb32d48188c43f39b5839e 14104 
dxf2gcode_20170925-5.debian.tar.xz
 655c1b12e3d26069c9ff16a045daa98d15286a11a75b964f2c7ba4f7fa855426 5 
dxf2gcode_20170925-5_source.buildinfo
Files:
 580bc834decf5a9d9dd98336b7bbe9c0 2064 science optional dxf2gcode_20170925-5.dsc
 1b49099b522c122165e173d0985a29fe 14104 science optional 
dxf2gcode_20170925-5.debian.tar.xz
 6244657bbdb5ef36e625c9c4f0c19342 5 science optional 
dxf2gcode_20170925-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAmN/mL4ACgkQgSgKoIe6
+w57yA/5AQTJmj8LpNDTfxZXXlbtGJ/R3dECcBfz9atO7XJq1iANhMlL6pL711L+
qIgdDiuAoWxrO1qcOREhjJE9NzB2VAarsTYNb1juFy8k4iNozz8vh0m+sETlxma4
gYjz6jxaH2EtH3sOwUFX7M3739nUEbwoR39o6nJfxWxncO7cmE5TZc51TLlpZoOC
ig4M3X+DWj1ly1kHIz9/FcTF2vWAYAWvnmVgqborM8a3lnnaWeNCQy2IY5/zb3PB
0+IYrV9ZUOBAZaVD7F/Ym0oC/CaEjweV+jZ0pkpEDqBGnZ18J4ritnNHHiWW8NFZ
GobnLX0semT0csAzq8qxAB55QVfZGKk4dtenTkTyIEhKVd8itaEHMMF3/j+54m5M
xw4dYmqO8oumkbDI1v8jofBmfcMrfNpdCBa0rSme2oZsO8z79XB0iA53djI2tIHf
3AlmGl/hBSGzr5UH7jYnFbiOChLOtS9TvavaK+sMyPM5Bs3JHQSkp/F08f4pJyQB
ZG83/LEnoP+SF8ZSZ94mOF0riX/wJ/FUmvrLcJ+/+GYbkyz7foTFQpD6ZXvk2Bdr
/NQvAdpCdLbX1jsyuYMkmAs0mfAKboB4nn0CrYlOnG4ccvHfkaCHlzHXw9gSHclG
rruQPSFUMKp+LRolmNqkPRQ+Ymydm5IabrCP3hqRX/QQAjIry0Q=
=bWxT
-END PGP SIGNATURE End Message ---

Bug#1024169: marked as done (csound breaks csound-plugins autopkgtest: *** stack smashing detected ***: terminated)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 16:34:47 +
with message-id 
and subject line Bug#1024169: fixed in csound 1:6.18.1+dfsg-1
has caused the Debian Bug report #1024169,
regarding csound breaks csound-plugins autopkgtest: *** stack smashing detected 
***: terminated
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.)


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

Source: csound, csound-plugins
Control: found -1 csound/1:6.18.0+dfsg-2
Control: found -1 csound-plugins/1.0.2~dfsg1-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
csound from testing1:6.18.0+dfsg-2
csound-plugins from testing1.0.2~dfsg1-2
all others from testingfrom testing

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

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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/arm64/c/csound-plugins/28320936/log.gz

*** stack smashing detected ***: terminated

csound command: Aborted

csound command: Segmentation fault
autopkgtest [17:15:52]: test command1



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: csound
Source-Version: 1:6.18.1+dfsg-1
Done: IOhannes m zmölnig (Debian/GNU) 

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

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

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

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated 
csound package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 24 Nov 2022 17:00:05 +0100
Source: csound
Architecture: source
Version: 1:6.18.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Closes: 1024169
Changes:
 csound (1:6.18.1+dfsg-1) unstable; urgency=medium
 .
   * New upstream version 6.18.1+dfsg
 + Fixes BigEndian issues
 + Fixes ABI compatibility (Closes: #1024169)
 + Drop patches applied (or obsoleted) upstream
   * Drop "Recommends:stk" (this belongs to csound-plugins)
   * Drop obsolete Cmake configvars
   * Modernize 'licensecheck' target
 + Regenerate d/copyright_hints
Checksums-Sha1:
 234ca9cc7ec4c3837b953def5899de34cc6d649b 3384 csound_6.18.1+dfsg-1.dsc
 e6e6134ca73d3e11bdc716871b4f295742837ece 25231484 
csound_6.18.1+dfsg.orig.tar.xz
 ff8051bd150d4903971265f922ffc8b920ac3d80 52564 
csound_6.18.1+dfsg-1.debian.tar.xz
Checksums-Sha256:
 931cc8ec04ad66b5b68b34cbe6fe790dd8851dbad92772bf0e6dfbedd6adb319 3384 
csound_6.18.1+dfsg-1.dsc
 cca9e8cd5655b5b5b99f967cff7f9fa222307becf00f70f1508126377ef94d4e 25231484 
csound_6.18.1+dfsg.orig.tar.xz
 a29c8c79b9f8a85130564861df8587d8a78238fb09049d67b647ffbdba7d247b 52564 
csound_6.18.1+dfsg-1.debian.tar.xz
Files:
 b7eaabaf53c48fd4e9797655b6d8c275 3384 sound optional csound_6.18.1+dfsg-1.dsc
 bebeed8b5aec52b0a96de82879034679 25231484 sound optional 
csound_6.18.1+dfsg.orig.tar.xz
 4771a2be723c20b33a06be8401409e8c 52564 sound optional 
csound_6.18.1+dfsg-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEdAXnRVdICXNIABVttlAZxH96NvgFAmN/l9EACgkQtlAZxH96
NvglzA/7Bmyi4RYuHsitTGGw7s3TRHsDoCu/ALqLdCWvfl7HwOdEkc2TYPx7qU7e
2DjfB4zITKgrCNWcsQcCz0Yr13yVqDhXcRbRrkvWEJyIbB1CnTOVxg/G/QOHp1yb

Bug#1022387: marked as done (dxf2gcode: FTBFS: dh_usrlocal: error: debian/dxf2gcode/usr/local/bin/dxf2gcode is not a directory)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 16:34:56 +
with message-id 
and subject line Bug#1022387: fixed in dxf2gcode 20170925-5
has caused the Debian Bug report #1022387,
regarding dxf2gcode: FTBFS: dh_usrlocal: error: 
debian/dxf2gcode/usr/local/bin/dxf2gcode is not a 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.)


-- 
1022387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022387
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dxf2gcode
Version: 20170925-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 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 '/<>'
> python3 ./st-setup.py install --prefix=usr --install-lib 
> usr/lib/python3/dist-packages --root=debian/dxf2gcode
> running install
> /usr/lib/python3/dist-packages/setuptools/command/install.py:34: 
> SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and 
> pip and other standards-based tools.
>   warnings.warn(
> running build
> running build_py
> running egg_info
> writing dxf2gcode.egg-info/PKG-INFO
> writing dependency_links to dxf2gcode.egg-info/dependency_links.txt
> writing requirements to dxf2gcode.egg-info/requires.txt
> writing top-level names to dxf2gcode.egg-info/top_level.txt
> reading manifest file 'dxf2gcode.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'COPYING'
> writing manifest file 'dxf2gcode.egg-info/SOURCES.txt'
> running build_scripts
> running install_lib
> creating debian/dxf2gcode
> creating debian/dxf2gcode/usr
> creating debian/dxf2gcode/usr/lib
> creating debian/dxf2gcode/usr/lib/python3
> creating debian/dxf2gcode/usr/lib/python3/dist-packages
> copying build/lib/dxf2gcode_ui5.py -> 
> debian/dxf2gcode/usr/lib/python3/dist-packages
> copying build/lib/dxf2gcode_images5_rc.py -> 
> debian/dxf2gcode/usr/lib/python3/dist-packages
> creating debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode
> copying build/lib/dxf2gcode/__init__.py -> 
> debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode
> creating debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/gui
> copying build/lib/dxf2gcode/gui/__init__.py -> 
> debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/gui
> copying build/lib/dxf2gcode/gui/canvas.py -> 
> debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/gui
> copying build/lib/dxf2gcode/gui/canvas2d.py -> 
> debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/gui
> copying build/lib/dxf2gcode/gui/configwindow.py -> 
> debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/gui
> copying build/lib/dxf2gcode/gui/routetext.py -> 
> debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/gui
> copying build/lib/dxf2gcode/gui/treeview.py -> 
> debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/gui
> copying build/lib/dxf2gcode/gui/wpzero.py -> 
> debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/gui
> copying build/lib/dxf2gcode/gui/aboutdialog.py -> 
> debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/gui
> copying build/lib/dxf2gcode/gui/messagebox.py -> 
> debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/gui
> copying build/lib/dxf2gcode/gui/popupdialog.py -> 
> debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/gui
> copying build/lib/dxf2gcode/gui/arrow.py -> 
> debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/gui
> copying build/lib/dxf2gcode/gui/canvas3d.py -> 
> debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/gui
> copying build/lib/dxf2gcode/gui/treehandling.py -> 
> debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/gui
> creating debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/postpro
> copying build/lib/dxf2gcode/postpro/__init__.py -> 
> debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/postpro
> copying build/lib/dxf2gcode/postpro/tspoptimisation.py -> 
> debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/postpro
> copying build/lib/dxf2gcode/postpro/postprocessor.py -> 
> debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/postpro
> copying build/lib/dxf2gcode/postpro/breaks.py -> 
> debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/postpro
> copying build/lib/dxf2gcode/postpro/postprocessorconfig.py -> 
> debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/postpro
> creating debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/dxfimport
> copying build/lib/dxf2gcode/dxfimport/__init__.py -> 
> 

Bug#1001879: marked as done (dxf2gcode: Add d/watch file and fix some lintian issues)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 16:34:56 +
with message-id 
and subject line Bug#1001879: fixed in dxf2gcode 20170925-5
has caused the Debian Bug report #1001879,
regarding dxf2gcode: Add d/watch file and fix some lintian issues
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.)


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

Package: dxf2gcode
Version: 20170925-4
Tags: patch

Included are some git commits to get rid of some Lintian warnings and to
add a d/watch file to automatically track new upstream versions.
Please include in the next upload.

I tried commiting the fixes directly to salsa, but alas lacked write
access to the git repository.
--
Happy hacking
Petter Reinholdtsen
>From f82c734ea16e5c8f671b515b2761ca5bf5f63b2a Mon Sep 17 00:00:00 2001
From: Petter Reinholdtsen 
Date: Sat, 18 Dec 2021 09:02:39 +0100
Subject: [PATCH 1/3] Updated Standards-Version from 4.1.3 to 4.6.0.

---
 debian/control | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/control b/debian/control
index 6ec2202..a3eb0a8 100644
--- a/debian/control
+++ b/debian/control
@@ -5,7 +5,7 @@ Maintainer: Debian Science Maintainers 
 Build-Depends: debhelper (>= 11), dh-python, python3, python3-setuptools,
  python3-pyqt5, pyqt5-dev-tools, qttools5-dev-tools
-Standards-Version: 4.1.3
+Standards-Version: 4.6.0
 Homepage: https://sourceforge.net/p/dxf2gcode/wiki/Home/
 Vcs-Git: https://salsa.debian.org/science-team/dxf2gcode.git
 Vcs-Browser: https://salsa.debian.org/science-team/dxf2gcode
-- 
2.30.2

>From 852884736019ea8c786e95864a882b3eb6985d7d Mon Sep 17 00:00:00 2001
From: Petter Reinholdtsen 
Date: Sat, 18 Dec 2021 09:13:41 +0100
Subject: [PATCH 2/3] Added a d/watch file to track new upstream versions.

---
 debian/watch | 5 +
 1 file changed, 5 insertions(+)
 create mode 100644 debian/watch

diff --git a/debian/watch b/debian/watch
new file mode 100644
index 000..a36f436
--- /dev/null
+++ b/debian/watch
@@ -0,0 +1,5 @@
+version=4
+# qa.debian.org runs a redirector which allows a simpler form of URL
+# for SourceForge based projects. The format below will automatically
+# be rewritten to use the redirector.
+http://sf.net/dxf2gcode/dxf2gcode-(\d\S+)\.(?:zip|tgz|tbz|txz|(?:tar\.(?:gz|bz2|xz)))
-- 
2.30.2

>From 644a8fb70f6589ab67a3f2a53588b4cc0a6f878f Mon Sep 17 00:00:00 2001
From: Petter Reinholdtsen 
Date: Sat, 18 Dec 2021 09:23:41 +0100
Subject: [PATCH 3/3] Added correct copyright for dxf2gcode.appdata.xml.

Thanks Lintian for discovering the inaccurate license information.
---
 debian/copyright | 14 ++
 1 file changed, 14 insertions(+)

diff --git a/debian/copyright b/debian/copyright
index 7eba20c..e2fdeb4 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -13,6 +13,20 @@ Copyright: 2008-2016 Christian Kohlöffel
2017 Damian Wrobel
 License: GPL-3+
 
+Files: dxf2gcode.appdata.xml
+Copyright: 2017 Damian Wrobel
+License: CC0-1.0
+ To the extent possible under law, the author(s) have dedicated all copyright
+ and related and neighboring rights to this software to the public domain
+ worldwide. This software is distributed without any warranty.
+ .
+ You should have received a copy of the CC0 Public Domain Dedication along
+ with this software. If not, see
+ .
+ .
+ On Debian systems, the complete text of the CC0 Public Domain Dedication
+ can be found in "/usr/share/common-licenses/CC0-1.0".
+
 Files: globals/six.py
 Copyright: 2010-2015 Benjamin Peterson
 License: Expat
-- 
2.30.2

--- End Message ---
--- Begin Message ---
Source: dxf2gcode
Source-Version: 20170925-5
Done: Petter Reinholdtsen 

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

Debian distribution maintenance software
pp.
Petter Reinholdtsen  (supplier of updated dxf2gcode package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 24 Nov 2022 17:11:19 +0100
Source: dxf2gcode

Bug#1024180: marked as done (pngcheck: autopkgtest needs update for new version of zlib: warning on stderr)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 15:35:20 +
with message-id 
and subject line Bug#1024180: fixed in pngcheck 3.0.2-3
has caused the Debian Bug report #1024180,
regarding pngcheck: autopkgtest needs update for new version of zlib: warning 
on stderr
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.)


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

Source: pngcheck
Version: 3.0.2-2
Severity: serious
X-Debbugs-CC: z...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:zlib

Dear maintainer(s),

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


   passfail
zlib   from testing1:1.2.13.dfsg-1
pngcheck   from testing3.0.2-2
all others from testingfrom testing

I copied some of the output at the bottom of this report. Your test 
*only* fails because of a warning. The default behavior of autopkgtest 
is to fail when there is output on stderr, unless the allow-stderr 
restriction is added. In this case, I'd try to avoid the warning 
altogether, because this is something that can happen easily in Debian.


Currently this regression is blocking the migration of zlib to testing 
[1]. Of course, zlib shouldn't just break your autopkgtest (or even 
worse, your package), but it seems to me that the change in zlib 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 zlib 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=zlib

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pngcheck/28323432/log.gz

zlib warning:  different version (expected 1.2.11, using 1.2.13)

OK: debian/tests/openlogo-nd-100.png (101x124, 8-bit palette, 
non-interlaced, 88.5%).

autopkgtest [11:15:19]: test command2



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: pngcheck
Source-Version: 3.0.2-3
Done: David da Silva Polverari 

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

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

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

Debian distribution maintenance software
pp.
David da Silva Polverari  (supplier of updated 
pngcheck package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 24 Nov 2022 15:14:37 +
Source: pngcheck
Architecture: source
Version: 3.0.2-3
Distribution: unstable
Urgency: medium
Maintainer: David da Silva Polverari 
Changed-By: David da Silva Polverari 
Closes: 1024180
Changes:
 pngcheck (3.0.2-3) unstable; urgency=medium
 .
   * debian/control: bumped Standards-Version to 4.6.1.
   * debian/copyright: updated packaging copyright years.
   * debian/tests/control: changed test to avoid failing only because of 
warning.
 Thanks to Paul Gevers . (Closes: #1024180)
Checksums-Sha1:
 0e0b6180910281c4352932da3a841fa20edc4fcd 1893 pngcheck_3.0.2-3.dsc
 82f87e9e1d892def459da1cfae9fc61fe6b2a09e 14956 pngcheck_3.0.2-3.debian.tar.xz
 f7d4ac6024c73e641e7fc1496d7922a314ce98ff 5543 pngcheck_3.0.2-3_source.buildinfo
Checksums-Sha256:
 db5a47440797284baadae36494f5a6fed192db1fbbf0546397085a5b62a27ed1 1893 
pngcheck_3.0.2-3.dsc
 d3b4368e6943729ba5cb73a81759620688d9d8f4dc4afb6b4041bb5693d3c18d 14956 
pngcheck_3.0.2-3.debian.tar.xz
 880f081fd0e15d7798e0aea0309fedb211069a48b62d06cf48a1ce8798482dec 5543 

Bug#1003642: marked as done ([INTL:es] Spanish translation of the debconf template)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 15:20:49 +
with message-id 
and subject line Bug#1003642: fixed in ocsinventory-agent 2:2.10.0-1
has caused the Debian Bug report #1003642,
regarding [INTL:es] Spanish translation of the debconf template
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.)


-- 
1003642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003642
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ocsinventory-agent
Severity: wishlist
Tags: patch l10n

Hello,
You can find enclosed the Spanish translation template to be uploaded with the 
latest package build.
Cheers,

-- 
Camaleón# ocsinventory-agent po-debconf translation to Spanish
# Copyright (C) 2010 Software in the Public Interest
# This file is distributed under the same license as the ocsinventory-server 
package.
#
# Changes:
# - Initial translation
# Maria Germana Oliveira Blazetic , 2018
#
# - Updates
# Camaleón , 2020, 2022
#
# Traductores, si no conocen el formato PO, merece la pena leer la
# documentación de gettext, especialmente las secciones dedicadas a este
# formato, por ejemplo ejecutando:
# info -n '(gettext)PO Files'
# info -n '(gettext)Header Entry'
#
# Equipo de traducción al español, por favor lean antes de traducir
# los siguientes documentos:
#
# - El proyecto de traducción de Debian al español
# http://www.debian.org/intl/spanish/
# especialmente las notas y normas de traducción en
# http://www.debian.org/intl/spanish/notas
#
# - La guía de traducción de po's de debconf:
# /usr/share/doc/po-debconf/README-trans
# o http://www.debian.org/intl/l10n/po-debconf/README-trans
#
msgid ""
msgstr ""
"Project-Id-Version: ocsinventory-agent\n"
"Report-Msgid-Bugs-To: ocsinventory-ag...@packages.debian.org\n"
"POT-Creation-Date: 2018-04-12 19:34+0200\n"
"PO-Revision-Date: 2022-01-13 08:35+0100\n"
"Last-Translator: Camaleón \n"
"Language-Team: Debian Spanish \n"
"Language: es\n"
"Plural-Forms: nplurals=2; plural=n!=1;\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: select
#. Choices
#: ../ocsinventory-agent.templates:2001
msgid "local"
msgstr "local"

#. Type: select
#. Choices
#: ../ocsinventory-agent.templates:2001
msgid "http"
msgstr "http"

#. Type: select
#. Description
#: ../ocsinventory-agent.templates:2002
msgid "Method used to generate the inventory:"
msgstr "Método usado para generar el inventario:"

#. Type: select
#. Description
#: ../ocsinventory-agent.templates:2002
msgid "Choose the 'local' method if you do not have a network connection."
msgstr "Seleccione el método «local» si no posee una conexión de red."

#. Type: select
#. Description
#: ../ocsinventory-agent.templates:2002
msgid "Choose the 'http' method if an OCS Inventory server is set up."
msgstr "Seleccione el método «http» si posee un servidor de inventario OCS."

#. Type: string
#. Description
#: ../ocsinventory-agent.templates:3001
msgid "OCS Inventory server URL:"
msgstr "Dirección URL del servidor de inventario OCS:"

#. Type: string
#. Description
#: ../ocsinventory-agent.templates:3001
msgid "Please enter the URL of the OCS inventory server."
msgstr "Introduzca la dirección URL del servidor de inventario OCS."

#. Type: string
#. Description
#: ../ocsinventory-agent.templates:4001
msgid "Tag for the generated inventory:"
msgstr "Etiqueta del inventario generado:"

#. Type: string
#. Description
#: ../ocsinventory-agent.templates:4001
msgid ""
"Each inventory can have an associated tag. Please enter the tag you would "
"like for the new inventory."
msgstr ""
"Cada inventario puede tener una etiqueta asociada. Introduzca la etiqueta a "
"utilizar con el nuevo inventario."

#. Type: string
#. Description
#: ../ocsinventory-agent.templates:4001
msgid ""
"This field can be left blank to continue without setting a new tag for the "
"inventory."
msgstr ""
"Puede dejar este campo en blanco para continuar sin asignar una nueva "
"etiqueta al inventario."
--- End Message ---
--- Begin Message ---
Source: ocsinventory-agent
Source-Version: 2:2.10.0-1
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated 

Bug#1021483: marked as done (Pipewire keeps waking up CPU even when not playing sound)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 14:36:50 +
with message-id 
and subject line Bug#1022120: fixed in pipewire 0.3.61-1
has caused the Debian Bug report #1022120,
regarding Pipewire keeps waking up CPU even when not playing sound
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.)


-- 
1022120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022120
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pipewire
Version: 0.3.59-1
Severity: important
X-Debbugs-Cc: j...@joshtriplett.org

Reporting this as "important" because as far as I can tell my battery
life has gone down noticeably since switching from Pulseaudio to Pipewire.

Even when not playing any sound whatsoever, pipewire is waking up more
than a hundred times per second, and using ~10ms of CPU out of every 1s.

This keeps the CPU in lower sleep states, and uses more battery.

- Josh Triplett

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

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

Versions of packages pipewire depends on:
ii  init-system-helpers  1.65.2
ii  libpipewire-0.3-modules  0.3.59-1
ii  pipewire-bin 0.3.59-1

pipewire recommends no packages.

pipewire suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pipewire
Source-Version: 0.3.61-1
Done: Dylan Aïssi 

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

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

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

Debian distribution maintenance software
pp.
Dylan Aïssi  (supplier of updated pipewire package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 24 Nov 2022 14:30:51 +0100
Source: pipewire
Architecture: source
Version: 0.3.61-1
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Dylan Aïssi 
Closes: 1021483 1022120
Changes:
 pipewire (0.3.61-1) unstable; urgency=medium
 .
   * New upstream release
   - pulse-server: add a pulse.idle.timeout option. Clients that are
 not sending any data will be paused so that the sinks can suspend
 to save battery power (Closes: #1021483, #1022120)
   * Drop patches included in upstream release:
   - b720da77: pulse-server: also advance read pointer in underrun
   - bf3516ba: To avoid crashes when switching profiles
   - b46d8a8c: Make PipeWire in qemu work again
   * pipewire-audio-client-libraries: depend on ${misc:Depends}
   * pipewire-jack: drop lintian-overrides, not relevant anymore
   * pipewire-libcamera: set minimum libcamera to 0.0.1
   * Drop debian/libspa-0.2-vulkan.install, not used
Checksums-Sha1:
 d74a4e589fe27c6e8dc3ba4360a373dac9a0ff67 4151 pipewire_0.3.61-1.dsc
 821ae8ba9f5b2248e0423d2d48d5cd3617814056 1480364 pipewire_0.3.61.orig.tar.bz2
 c111b8a4f7c8db98806a7b36cf2b8002ee894ad4 22892 pipewire_0.3.61-1.debian.tar.xz
 e45342b76b28409ce59a9f299a5afaa3bcdf1134 24490 
pipewire_0.3.61-1_amd64.buildinfo
Checksums-Sha256:
 e22e0b8f29cce925fb978c1d1610ba2a183c1a52a790bfb2ce94554f1f77fa9f 4151 
pipewire_0.3.61-1.dsc
 c9e6584286787e332ed463d89c90c7a0edcbc836fb597de104a6a50d2ffe745c 1480364 
pipewire_0.3.61.orig.tar.bz2
 5d6d8b5c1c68a96a0b95e9e17b7d7f6237476ada92ba6a29c6f67dc28c91908d 22892 
pipewire_0.3.61-1.debian.tar.xz
 0db25b76889f103ff82cac4d710f1fc9ea3bdbea84062ec6ab738214dd6b4acc 24490 
pipewire_0.3.61-1_amd64.buildinfo
Files:
 cd54fb6cda2e2ccfb057c525e94847e6 4151 libs optional pipewire_0.3.61-1.dsc
 03453b2fac9eab38a1083e1b8314bd0a 1480364 libs optional 
pipewire_0.3.61.orig.tar.bz2
 9b76a0544d441df5e65fd108007c1dd5 22892 libs optional 
pipewire_0.3.61-1.debian.tar.xz
 b0d42cca24c0bbe37577be01ae9fa671 24490 libs optional 
pipewire_0.3.61-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#1022120: marked as done (speech-dispatcher-dummy causes pipewire to spin and use battery)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 14:36:50 +
with message-id 
and subject line Bug#1022120: fixed in pipewire 0.3.61-1
has caused the Debian Bug report #1022120,
regarding speech-dispatcher-dummy causes pipewire to spin and use battery
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.)


-- 
1022120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022120
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: speech-dispatcher
Version: 0.11.3-1+b1
Severity: important
X-Debbugs-Cc: j...@joshtriplett.org

Previously, I reported
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021483 against
pipewire. I discovered pw-top, and it showed that
speech-dispatcher-dummy was the only thing interacting with pipewire.
Killing speech-dispatcher caused pipewire to *stop* waking up and using
battery.

To the best of my knowledge, nothing on my system should be *using*
speech-dispatcher. (Happy to check that if there's a tool to do so.) So
it shouldn't be sending anything to pipewire and causing pipewire to
wake up.

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

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

Versions of packages speech-dispatcher depends on:
ii  adduser  3.129
ii  init-system-helpers  1.65.2
ii  libc62.35-3
ii  libdotconf0  1.3-0.3
ii  libglib2.0-0 2.74.0-3
ii  libltdl7 2.4.7-4
ii  libsndfile1  1.1.0-3
ii  libspeechd2  0.11.3-1+b1
ii  speech-dispatcher-audio-plugins  0.11.3-1+b1
ii  sysvinit-utils [lsb-base]3.05-6

Versions of packages speech-dispatcher recommends:
pn  sound-icons  
pn  speech-dispatcher-espeak-ng  

Versions of packages speech-dispatcher suggests:
pn  espeak  
pn  libttspico-utils
pn  mbrola  
pn  speech-dispatcher-cicero
pn  speech-dispatcher-doc-cs
pn  speech-dispatcher-espeak
pn  speech-dispatcher-festival  
pn  speech-dispatcher-flite 

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pipewire
Source-Version: 0.3.61-1
Done: Dylan Aïssi 

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

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

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

Debian distribution maintenance software
pp.
Dylan Aïssi  (supplier of updated pipewire package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 24 Nov 2022 14:30:51 +0100
Source: pipewire
Architecture: source
Version: 0.3.61-1
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Dylan Aïssi 
Closes: 1021483 1022120
Changes:
 pipewire (0.3.61-1) unstable; urgency=medium
 .
   * New upstream release
   - pulse-server: add a pulse.idle.timeout option. Clients that are
 not sending any data will be paused so that the sinks can suspend
 to save battery power (Closes: #1021483, #1022120)
   * Drop patches included in upstream release:
   - b720da77: pulse-server: also advance read pointer in underrun
   - bf3516ba: To avoid crashes when switching profiles
   - b46d8a8c: Make PipeWire in qemu work again
   * pipewire-audio-client-libraries: depend on ${misc:Depends}
   * pipewire-jack: drop lintian-overrides, not relevant anymore
   * pipewire-libcamera: set minimum libcamera to 0.0.1
   * Drop debian/libspa-0.2-vulkan.install, not used
Checksums-Sha1:
 d74a4e589fe27c6e8dc3ba4360a373dac9a0ff67 4151 pipewire_0.3.61-1.dsc
 821ae8ba9f5b2248e0423d2d48d5cd3617814056 1480364 pipewire_0.3.61.orig.tar.bz2
 c111b8a4f7c8db98806a7b36cf2b8002ee894ad4 22892 pipewire_0.3.61-1.debian.tar.xz
 

Bug#1021483: marked as done (Pipewire keeps waking up CPU even when not playing sound)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 14:36:50 +
with message-id 
and subject line Bug#1021483: fixed in pipewire 0.3.61-1
has caused the Debian Bug report #1021483,
regarding Pipewire keeps waking up CPU even when not playing sound
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.)


-- 
1021483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021483
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pipewire
Version: 0.3.59-1
Severity: important
X-Debbugs-Cc: j...@joshtriplett.org

Reporting this as "important" because as far as I can tell my battery
life has gone down noticeably since switching from Pulseaudio to Pipewire.

Even when not playing any sound whatsoever, pipewire is waking up more
than a hundred times per second, and using ~10ms of CPU out of every 1s.

This keeps the CPU in lower sleep states, and uses more battery.

- Josh Triplett

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

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

Versions of packages pipewire depends on:
ii  init-system-helpers  1.65.2
ii  libpipewire-0.3-modules  0.3.59-1
ii  pipewire-bin 0.3.59-1

pipewire recommends no packages.

pipewire suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pipewire
Source-Version: 0.3.61-1
Done: Dylan Aïssi 

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

Debian distribution maintenance software
pp.
Dylan Aïssi  (supplier of updated pipewire package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 24 Nov 2022 14:30:51 +0100
Source: pipewire
Architecture: source
Version: 0.3.61-1
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Dylan Aïssi 
Closes: 1021483 1022120
Changes:
 pipewire (0.3.61-1) unstable; urgency=medium
 .
   * New upstream release
   - pulse-server: add a pulse.idle.timeout option. Clients that are
 not sending any data will be paused so that the sinks can suspend
 to save battery power (Closes: #1021483, #1022120)
   * Drop patches included in upstream release:
   - b720da77: pulse-server: also advance read pointer in underrun
   - bf3516ba: To avoid crashes when switching profiles
   - b46d8a8c: Make PipeWire in qemu work again
   * pipewire-audio-client-libraries: depend on ${misc:Depends}
   * pipewire-jack: drop lintian-overrides, not relevant anymore
   * pipewire-libcamera: set minimum libcamera to 0.0.1
   * Drop debian/libspa-0.2-vulkan.install, not used
Checksums-Sha1:
 d74a4e589fe27c6e8dc3ba4360a373dac9a0ff67 4151 pipewire_0.3.61-1.dsc
 821ae8ba9f5b2248e0423d2d48d5cd3617814056 1480364 pipewire_0.3.61.orig.tar.bz2
 c111b8a4f7c8db98806a7b36cf2b8002ee894ad4 22892 pipewire_0.3.61-1.debian.tar.xz
 e45342b76b28409ce59a9f299a5afaa3bcdf1134 24490 
pipewire_0.3.61-1_amd64.buildinfo
Checksums-Sha256:
 e22e0b8f29cce925fb978c1d1610ba2a183c1a52a790bfb2ce94554f1f77fa9f 4151 
pipewire_0.3.61-1.dsc
 c9e6584286787e332ed463d89c90c7a0edcbc836fb597de104a6a50d2ffe745c 1480364 
pipewire_0.3.61.orig.tar.bz2
 5d6d8b5c1c68a96a0b95e9e17b7d7f6237476ada92ba6a29c6f67dc28c91908d 22892 
pipewire_0.3.61-1.debian.tar.xz
 0db25b76889f103ff82cac4d710f1fc9ea3bdbea84062ec6ab738214dd6b4acc 24490 
pipewire_0.3.61-1_amd64.buildinfo
Files:
 cd54fb6cda2e2ccfb057c525e94847e6 4151 libs optional pipewire_0.3.61-1.dsc
 03453b2fac9eab38a1083e1b8314bd0a 1480364 libs optional 
pipewire_0.3.61.orig.tar.bz2
 9b76a0544d441df5e65fd108007c1dd5 22892 libs optional 
pipewire_0.3.61-1.debian.tar.xz
 b0d42cca24c0bbe37577be01ae9fa671 24490 libs optional 
pipewire_0.3.61-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#1022120: marked as done (speech-dispatcher-dummy causes pipewire to spin and use battery)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 14:36:50 +
with message-id 
and subject line Bug#1021483: fixed in pipewire 0.3.61-1
has caused the Debian Bug report #1021483,
regarding speech-dispatcher-dummy causes pipewire to spin and use battery
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.)


-- 
1021483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021483
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: speech-dispatcher
Version: 0.11.3-1+b1
Severity: important
X-Debbugs-Cc: j...@joshtriplett.org

Previously, I reported
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021483 against
pipewire. I discovered pw-top, and it showed that
speech-dispatcher-dummy was the only thing interacting with pipewire.
Killing speech-dispatcher caused pipewire to *stop* waking up and using
battery.

To the best of my knowledge, nothing on my system should be *using*
speech-dispatcher. (Happy to check that if there's a tool to do so.) So
it shouldn't be sending anything to pipewire and causing pipewire to
wake up.

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

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

Versions of packages speech-dispatcher depends on:
ii  adduser  3.129
ii  init-system-helpers  1.65.2
ii  libc62.35-3
ii  libdotconf0  1.3-0.3
ii  libglib2.0-0 2.74.0-3
ii  libltdl7 2.4.7-4
ii  libsndfile1  1.1.0-3
ii  libspeechd2  0.11.3-1+b1
ii  speech-dispatcher-audio-plugins  0.11.3-1+b1
ii  sysvinit-utils [lsb-base]3.05-6

Versions of packages speech-dispatcher recommends:
pn  sound-icons  
pn  speech-dispatcher-espeak-ng  

Versions of packages speech-dispatcher suggests:
pn  espeak  
pn  libttspico-utils
pn  mbrola  
pn  speech-dispatcher-cicero
pn  speech-dispatcher-doc-cs
pn  speech-dispatcher-espeak
pn  speech-dispatcher-festival  
pn  speech-dispatcher-flite 

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pipewire
Source-Version: 0.3.61-1
Done: Dylan Aïssi 

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

Debian distribution maintenance software
pp.
Dylan Aïssi  (supplier of updated pipewire package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 24 Nov 2022 14:30:51 +0100
Source: pipewire
Architecture: source
Version: 0.3.61-1
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Dylan Aïssi 
Closes: 1021483 1022120
Changes:
 pipewire (0.3.61-1) unstable; urgency=medium
 .
   * New upstream release
   - pulse-server: add a pulse.idle.timeout option. Clients that are
 not sending any data will be paused so that the sinks can suspend
 to save battery power (Closes: #1021483, #1022120)
   * Drop patches included in upstream release:
   - b720da77: pulse-server: also advance read pointer in underrun
   - bf3516ba: To avoid crashes when switching profiles
   - b46d8a8c: Make PipeWire in qemu work again
   * pipewire-audio-client-libraries: depend on ${misc:Depends}
   * pipewire-jack: drop lintian-overrides, not relevant anymore
   * pipewire-libcamera: set minimum libcamera to 0.0.1
   * Drop debian/libspa-0.2-vulkan.install, not used
Checksums-Sha1:
 d74a4e589fe27c6e8dc3ba4360a373dac9a0ff67 4151 pipewire_0.3.61-1.dsc
 821ae8ba9f5b2248e0423d2d48d5cd3617814056 1480364 pipewire_0.3.61.orig.tar.bz2
 c111b8a4f7c8db98806a7b36cf2b8002ee894ad4 22892 pipewire_0.3.61-1.debian.tar.xz
 

Processed: closing 1024175, closing 1024174

[Debian Bug Tracking System]

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

> close 1024175 4.1.0-1
Bug #1024175 [src:ruby-omniauth-gitlab] ruby-omniauth-gitlab: autopkgtest needs 
update for new version of ruby-omniauth-oauth2: Could not find 
'omniauth-oauth2' (~> 1.7.1
Marked as fixed in versions ruby-omniauth-gitlab/4.1.0-1.
Bug #1024175 [src:ruby-omniauth-gitlab] ruby-omniauth-gitlab: autopkgtest needs 
update for new version of ruby-omniauth-oauth2: Could not find 
'omniauth-oauth2' (~> 1.7.1
Marked Bug as done
> close 1024174 1.0.1-1
Bug #1024174 [src:ruby-omniauth-dingtalk-oauth2] ruby-omniauth-dingtalk-oauth2: 
autopkgtest needs update for new version of ruby-omniauth-oauth2: Could not 
find 'omniauth-oauth2' (~> 1.7.1)
Marked as fixed in versions ruby-omniauth-dingtalk-oauth2/1.0.1-1.
Bug #1024174 [src:ruby-omniauth-dingtalk-oauth2] ruby-omniauth-dingtalk-oauth2: 
autopkgtest needs update for new version of ruby-omniauth-oauth2: Could not 
find 'omniauth-oauth2' (~> 1.7.1)
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1024750: marked as done (rust-serde: please update to v1.0.147)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 13:05:58 +
with message-id 
and subject line Bug#1024750: fixed in rust-serde 1.0.147-1
has caused the Debian Bug report #1024750,
regarding rust-serde: please update to v1.0.147
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.)


-- 
1024750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024750
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-serde
Version: 1.0.145-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please update to newer upstream release v1.0.147.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmN/MqUACgkQLHwxRsGg
ASGyFA/8D4t7bAa7NYGLIQ/ZPbFx9Hzqj9u9fY+ByrsbAEXyt9V2wv6/VEJD439P
WLQaRqCdFNohYFMKWZy08FTFK8GaIqRYZuK2u5SMTQzTqPvP/f//jAVe7M7KgFNV
25FppY+nBSyD2sCZ4QmQpT6lC86qlCETQX6oHTe+xYjlQpVHusU05uxo+KSsvK0U
DMEwWaHoU4mQWNIOnKsPg+/ZPbLykMOEsxJurfRLiTUiVtsMhEuzopAx4JJeaLAd
nYYh+OKWZamCSHrVD40YVi3OQeCrNl2MibKbkIcsh751PukeWK3roulLBVFXwcK5
juigshIGlKRx2AqNWcNeSn7wdFSp1NHYdk100lVmP0oRckY4Np6LlBR/JaA43MT/
e9V0pvSTgt+0TQx+xYEdOBDh+9yHtOwRLMZIAwLlnz32SSAQQywn8n32GU8t0QPM
LJbue2M58DOMR7k4d64BTaBojE9EaUHQ2PNLaOyg8fzYzGEyyUWoguSB+4QjOCH/
yQY4pPyu2YwoesZPw0hZDtuzg7xABXJi8Ytw/De5ejIdAmHCpx8G+BsPwsby9yv0
kq3TjZc7B5y8vXgzX9Gisl5LbAQPthuDiho4XQWRakfHwG22+PX9KFxlRjtXv5qc
07j0DunNMkG/9+DZEt4ETMLBlfqJVbI2QtuO3GJamhK7zPEYl/Q=
=Qwzi
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: rust-serde
Source-Version: 1.0.147-1
Done: Blair Noctis 

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

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

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

Debian distribution maintenance software
pp.
Blair Noctis  (supplier of updated rust-serde package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 24 Nov 2022 12:06:01 +
Source: rust-serde
Architecture: source
Version: 1.0.147-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Blair Noctis 
Closes: 1024750
Changes:
 rust-serde (1.0.147-1) unstable; urgency=medium
 .
   * Team upload.
   * Package serde 1.0.147 from crates.io using debcargo 2.6.0 (Closes: 
#1024750)
Checksums-Sha1:
 b0c49258382ebb2c3b83af50578cec99a239 2322 rust-serde_1.0.147-1.dsc
 f5a47927d915430ce7fcf4f3b4305462d7120166 76697 rust-serde_1.0.147.orig.tar.gz
 94f155ec3677a258a36a427de117bf28cadb86c6 3636 
rust-serde_1.0.147-1.debian.tar.xz
 c757df9fc4d9675905f8d17d0ade087d18126306 7325 
rust-serde_1.0.147-1_source.buildinfo
Checksums-Sha256:
 2dc0bd91847a273200877c50b631f8d242b57ab05ba0e3e5b1b2a56f72053743 2322 
rust-serde_1.0.147-1.dsc
 d193d69bae983fc11a79df82342761dfbf28a99fc8d203dca4c3c1b590948965 76697 
rust-serde_1.0.147.orig.tar.gz
 84e06f700af7a90e1e2afcad1c54e818e60c985d12d91f23c5f97fa6ac83e2ac 3636 
rust-serde_1.0.147-1.debian.tar.xz
 e41adf46bf0c878eea9f08047a09afd1afb76de3887d0bdf19fbc7487a133bd0 7325 
rust-serde_1.0.147-1_source.buildinfo
Files:
 2092979530122f222d7a5ef902342e4d 2322 rust optional rust-serde_1.0.147-1.dsc
 fbb26834819534a6cf6ec8df4bccff02 76697 rust optional 
rust-serde_1.0.147.orig.tar.gz
 5c015c0c7d2506d35166b2ad5e96d178 3636 rust optional 
rust-serde_1.0.147-1.debian.tar.xz
 e58b58bfa6c65a8bc2e6dd5d87193b39 7325 rust optional 
rust-serde_1.0.147-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmN/Y3IUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XuHvQ//W6c++tDlaGbabGus+YvJrv3KokVB
yGGWs8we3dvAaCBR2gZ/4TC0MT7PivZGx3DG2ekj1V9p5QAqe3lICvr4B71L32bh
D0Ckg/n2UxLqSqWhDduTqtfgmz7nI5m12HLJYGPwPUgW8iyZw0+UmXZwtVMWjF68
E4F1vRX4n91oozQ6W3icgOdvTj4/pY17fowTFxok72rNwt+sA1k0DnoPgfT4as/A
SnBriqTD2xiBK2f0+/dlHaaKVqJQw02GG3CrXUz2vJHSSLtNdSID5mQyH/HCXvHs
rGqysb0pRb7YL7L7fp5pjrjMNLvDjokp1Na2zyLWQV1WNugmBmwc4MZptCEImLF1
rXgQ0IHcIA9yqnNa3kqFzr38KYy7o2/fKvl40Pd1v7kdODjZui816i+Se2Hwm/pg
s1dUp/GmcAmw2A6aFez+fx3E6FF4aXqOVrofpLyR4M+GLsUvV77pUVWm2+48a6Jy
3ozPE/HNed2nTLxCNa+Cm/Fx2GfxGez4VHWrmUtjwbxwJWnKFMewLyjZRJLaAZed
eIDu4jL4qOU6ykxsAYEamqdYEWqDx+IIHcqp3jeNdx/QWigMyJT53nzGAoF5ljsN

Bug#964010: marked as done (ddogleg: package v0.19)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 13:04:06 +
with message-id 
and subject line Bug#964010: fixed in ddogleg 0.22+ds-1
has caused the Debian Bug report #964010,
regarding ddogleg: package v0.19
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.)


-- 
964010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964010
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ddogleg
Severity: wishlist
Control: block -1 by 959930

Packaging ddogleg v0.18 requires libejml-java v0.39 at least.

Best,
Andrius
--- End Message ---
--- Begin Message ---
Source: ddogleg
Source-Version: 0.22+ds-1
Done: Andrius Merkys 

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

Debian distribution maintenance software
pp.
Andrius Merkys  (supplier of updated ddogleg package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 24 Nov 2022 07:25:47 -0500
Source: ddogleg
Architecture: source
Version: 0.22+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Andrius Merkys 
Closes: 964010
Changes:
 ddogleg (0.22+ds-1) unstable; urgency=medium
 .
   * Run tests.
   * New upstream version 0.22+ds (Closes: #964010)
   * Adjust source version for javac.
   * Set upstream metadata fields: Repository-Browse.
   * Update standards version to 4.6.1, no changes needed.
   * Refresh copyright years.
Checksums-Sha1:
 62053710ddb6ecbfcc7480283daa6835eb9e75a0 2021 ddogleg_0.22+ds-1.dsc
 136e9c380411cc07d3c72b607290615d5cdb0233 234304 ddogleg_0.22+ds.orig.tar.xz
 2016b11f23414152fa98d1ef8d07b9d6655d5403 2296 ddogleg_0.22+ds-1.debian.tar.xz
 ab90efb81650e1fc2a53856937daa02aa8551dfe 14535 
ddogleg_0.22+ds-1_source.buildinfo
Checksums-Sha256:
 f1cba9f72e83410364e6593964868570b62f3529be025a9b7ec2fd31153c2a07 2021 
ddogleg_0.22+ds-1.dsc
 13d0104af3c34214aa1b20fded6f11104e9c6f753bed656e2c1cf783db1996c5 234304 
ddogleg_0.22+ds.orig.tar.xz
 842597099955c2300a3c416a4f13307998094bb160aba6827c75301e0644722d 2296 
ddogleg_0.22+ds-1.debian.tar.xz
 e9a9f4493cd9c25a967885ff2e31e6c35a2373d27a7ac8d53e6eba23a5ed864c 14535 
ddogleg_0.22+ds-1_source.buildinfo
Files:
 9378d6c078312a5c7a90d9150008adcf 2021 java optional ddogleg_0.22+ds-1.dsc
 bc62b8459170ed6e51c99fe4b5c9db45 234304 java optional 
ddogleg_0.22+ds.orig.tar.xz
 e6355d60bc5321a34352fad9f437d71b 2296 java optional 
ddogleg_0.22+ds-1.debian.tar.xz
 c1c68b4eda37db78b91ed258dcc4ffa5 14535 java optional 
ddogleg_0.22+ds-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEdyKS9veshfrgQdQe5fQ/nCc08ocFAmN/ZGYSHG1lcmt5c0Bk
ZWJpYW4ub3JnAAoJEOX0P5wnNPKHf3AP/jmfDzV35EI6/VjKJkZwksFr4r3DC9Pj
csRsSdA7ZKhKqNvf7oj5H0wpwXj6JF2bzfTLUSRtIJUcJp33INFbIlNttJidxXTL
MApG7ZsNMTtlFu4vjVxLmR4LpCFPqU1Kin0JMpIz1j74NiDDQ1Se8TXQxPlx4E2c
iFf+CeuvbT1wjPwe2M+s7tH/+qJq3+8O/w68Gnwr9icuOj3QSVD92z6p91J2Z4nM
kKREpdyjZTUx0Xj5zcdiAyZgev4B7KuQKS3efqaBO24Fd/L971TbNt9/pdlf805M
ZtAaUS0yZfx/oY3fFXReh26e4Z4RG6RUB/WdttcwBGsMOP79+ApmQ9OL3aEQHYAh
kcc1tlpLe1qZYT22qjlNYlADdjhoAo5vNyGCo8k5M7SwB2q/i7YtxtdHX4++GFaq
U0ACfj42dA0WAH+m6YBXWUJiCyqEgIn0ECqbkrXieRH3Z/hukpwqAVvbGmLCHf7X
Ebug/sEFSTm4awJ+C99gFTuJQ8NWucZPvBeXKRbpJrHRY5h6SbO9xjgSPXX/eslC
1GOf8f+eIuDMagccynbG97pdINEm3gNK2NsCzD/uU8sgZhLJzD3L621/Wsrl3p84
AZjyaD2080g3UvjzmC86/yQFov8Cy6MYAw1jibqQ4HDOSP6PEcloFvcXGW4fHn3W
CCQ/ykDvkEty
=2xWx
-END PGP SIGNATURE End Message ---

Bug#1024726: marked as done (nmu: evolution-data-server_3.46.1-1+b1)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 14:03:32 +0100
with message-id 
and subject line Re: Bug#1024726: nmu: evolution-data-server_3.46.1-1+b1
has caused the Debian Bug report #1024726,
regarding nmu: evolution-data-server_3.46.1-1+b1
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.)


-- 
1024726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024726
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: binnmu
Severity: high

Please schedule this rebuild to fix evolution-data-server
compatibility with libphonenumber which was rebuilt for the ongoing
protobuf transition. This rebuild wasn't on the auto tracker which
suggests that there is a bigger dependency issue somewhere. I don't
know if other packages are also affected. See
https://bugs.debian.org/1024674

Here's my guess at the syntax:

nmu evolution-data-server_3.46.1-1+b1 . ANY . unstable . -m
"libphonenumber8 (>= 8.12.57+ds-1+b2)"

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
On 2022-11-24 12:27:18 +0100, Jochen Sprickerhof wrote:
> * Jeremy Bicha  [2022-11-23 16:33]:
> > Please schedule this rebuild to fix evolution-data-server
> > compatibility with libphonenumber which was rebuilt for the ongoing
> > protobuf transition. This rebuild wasn't on the auto tracker which
> > suggests that there is a bigger dependency issue somewhere. I don't
> > know if other packages are also affected. See
> > https://bugs.debian.org/1024674
> 
> The problem is/was that libphonenumber8 exposes the protobuf ABI. I've just
> uploaded a -2 to declare this dependency through a
> libphonenumber8-protobuf32 virtual package, similar how it is done in
> ignition-msgs.

Thanks. Note though that libphonenumber FTBFS almost everywhere.

> I've just did a test build and evolution-data-server picks up the new
> dependency now. so I think the request should be:
> 
> dw evolution-data-server_3.46.1-1+b1 . ANY . unstable . -m "libphonenumber8 
> (>= 8.12.57+ds-2)"

Scheduled with the dw.

Cheers
-- 
Sebastian Ramacher--- End Message ---

Bug#1024181: marked as done (RFS: php-zumba-json-serializer/3.0.1-1 [ITP] -- Json Serializer is a PHP library to serialize PHP variables in JSON format)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 17:56:11 +0530
with message-id 

and subject line Re: Bug#1024181: RFS: php-zumba-json-serializer -- Json 
Serializer is a PHP library to serialize PHP variables in JSON format
has caused the Debian Bug report #1024181,
regarding RFS: php-zumba-json-serializer/3.0.1-1 [ITP] -- Json Serializer is a 
PHP library to serialize PHP variables in JSON format
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.)


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

Package: sponsorship-requests
Severity: normal
X-Debbugs-CC:pkg-php-p...@lists.alioth.debian.org
X-Debbugs-CC:utka...@debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear mentors,

I am looking for a sponsor for my package "php-zumba-json-serializer":

 * Package name : php-zumba-json-serializer
   Version  : 3.0.1-1
   Upstream contact : Juan Basso
 * URL  :https://github.com/zumba/json-serializer
 * License  : MIT
 * Vcs  
:https://salsa.debian.org/php-team/pear/php-zumba-json-serializer
   Section  : php

The source builds the following binary packages:

  php-zumba-json-serializer -- Json Serializer is a PHP library to serialize 
PHP variables in JSON format

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/php-zumba-json-serializer/

Alternatively, you can download the package with 'dget' using this command:

  dget 
-xhttps://mentors.debian.net/debian/pool/main/p/php-zumba-json-serializer/php-zumba-json-serializer_3.0.1-1.dsc

Changes since the last upload:

 php-zumba-json-serializer (3.0.1-1) unstable; urgency=medium
 .
   * Initial release (Closes: #1015858)

Regards,
- -- 
William Desportes


-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEExNkf3872tKPGU/14kKDvG4JRqIkFAmNz/O8ACgkQkKDvG4JR
qImtoRAAhL8QkuSmJzDsIdTOQDbhhgAJmSEGewO+KudWLM1N4l3ATOsoLX5ep3YP
52marGCGVMpk52Wud2t+Adb0eJ2NImrT/hYXdGRwXPWRW7MmL1d6oj7aX3lhlvTw
F6RuO1NK1W4REh+lvfCOfgQ4JUhsQS2aTzNVw9RlKXjyntcWDXH8DdFARzRxdo72
37pnQrg66i/sjLrJzoAI/Gn3EHwuxtTKxFfBETFNOPl8osDl0JQopt9Bu3f7fSRg
xfkigTVQ5HBV6wOLI7uvyyO6InGXwB06KScuFcHj/cSi98nEsm3MsAmeFq03Pksc
8BNBGfGiqjE1/1rWsxzi1lYaaIDMIRyburg+1M0cuE/d/qy6372AlW+VGI7OwM7z
jE5vrXwyISIkloPsh+09PJZsV/pGOf6nHDJLt2GytVLvLOhtOVVL6gU923CCkgeV
3NM5gTuNBtYXetNstUS3VJtC2tJNsuAYqttekFlbWi452QpMC2fcGKhfXjOX9eqc
CyBAOnaKrchOVVMsAixb7LeTtsY0dcakY1wjDqnEqRAxRDOUhPmfZ4V+NSNYcRSb
4O96eu9AbSlQSIO2a5ibS2yNd3zcKQ56oc4lhFuVbi9juInayLW3X5dgWsCy6Cti
ylGF94bf8nws1pmRWAgtQOcfEzh/ZdGDdN7q9k7IoAVPj00sjSc=
=8dsa
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Hi William,

On Wed, Nov 16, 2022 at 2:39 AM William Desportes  wrote:
> I am looking for a sponsor for my package "php-zumba-json-serializer":

Sponsored the upload! \o/


- u--- End Message ---

Bug#1024749: marked as done (rust-pretty-assertions: please update to v1.3.0)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 12:07:22 +
with message-id 
and subject line Bug#1024749: fixed in rust-pretty-assertions 1.3.0-1
has caused the Debian Bug report #1024749,
regarding rust-pretty-assertions: please update to v1.3.0
to be marked as done.

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

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


-- 
1024749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024749
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-pretty-assertions
Version: 1.2.1-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please update to newer upstream release v1.3.0.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmN/MggACgkQLHwxRsGg
ASF/nRAAjwj+X9I9AILU1ndSDzRpQN/hIwE/IMDPWxqJZJEsvmeVo4aoXkChTa0n
tSNCoe3hVFk/meOdPBWdrPZdoGVY3QouroPJKwHPCCGXoDiQG8xxnzu+gbcvZ7lc
eekPzhvjtX0Yl1FJAP+KsKhXd0n10w5wzbLFPCSI4IUHMhmiyU0jZrhNPArceDnQ
wT9JEMilaV1KbML7WfWg9Jq+Sz9iXPHNwtSQJAM2M56Yw881i0tnYtC6LThC3KWi
nYCJeVo5jIXdr5599KxCxBxdIyCDXyJxXkTt7Obv3kEOEU5aZ2plXM3LbRGtgQeE
tiq9vkeko0Jv3oPxptpgkKZXS+9b78fUu7zXfQBfV8JpcJ0T/g02mHgppa14/ojK
8SF1EEdQZcDg9ifxRK8RB6zI5epaCtTUAE9tH7+mOiCmYTfWS0sWZCpYqkcLavH4
bNJVOXpgV0Dbzl06Ii6jLDFd9RlScCPxI3XQS0KQ9KgtGyTPwVpLi4bC8JmhwwH1
qrHFECwyrbXvc/3b9Mlqrx0w2DH8ACD/zdmFM8Ksryv8hrmA5Th+MZYHHpJkBzHI
IjAf8TkfrR/UbdJsWsv2X6AkOvflS5nhZsUNOjZ2uruMh94WY8dLTbi8YxxwsXsu
X7vaIQNMJ5ylhak84ojDmbw3QlV+sm/x6mo0PcJFngjV0WXPhOc=
=B8xj
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: rust-pretty-assertions
Source-Version: 1.3.0-1
Done: Peter Michael Green 

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

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

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

Debian distribution maintenance software
pp.
Peter Michael Green  (supplier of updated 
rust-pretty-assertions package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 24 Nov 2022 11:38:04 +
Source: rust-pretty-assertions
Architecture: source
Version: 1.3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Peter Michael Green 
Closes: 1024749
Changes:
 rust-pretty-assertions (1.3.0-1) unstable; urgency=medium
 .
   * Team upload.
   * Package pretty_assertions 1.3.0 from crates.io using debcargo 2.6.0 
(Closes: #1024749)
   * Update copyright file.
Checksums-Sha1:
 f6ae2ebba73c2be2c8ea985967f4093f826e145b 2505 
rust-pretty-assertions_1.3.0-1.dsc
 6770cd52cee3c07a2ee0b2b984508f70605e616a 79441 
rust-pretty-assertions_1.3.0.orig.tar.gz
 2ba5f2bf560d85a9b651f973a4958b55fdf536bf 3320 
rust-pretty-assertions_1.3.0-1.debian.tar.xz
 2052db4358efb7b08b45f6d214595c374df650a5 7809 
rust-pretty-assertions_1.3.0-1_source.buildinfo
Checksums-Sha256:
 f66712b1843f6fd1158bfca2bf1120cfb60d33cc2d826faee7343c889332e174 2505 
rust-pretty-assertions_1.3.0-1.dsc
 a25e9bcb20aa780fd0bb16b72403a9064d6b3f22f026946029acb941a50af755 79441 
rust-pretty-assertions_1.3.0.orig.tar.gz
 ba7259d74c72eaeca45b1b6b96b3cbcea7d98c63fbe66f7aebb2737e02f296c1 3320 
rust-pretty-assertions_1.3.0-1.debian.tar.xz
 7c77d552c887c413e463636ef7cf99b3a65df2e0d785f09e339434df69e6cf1b 7809 
rust-pretty-assertions_1.3.0-1_source.buildinfo
Files:
 c40cbae74602694660758a9ca5b4452e 2505 rust optional 
rust-pretty-assertions_1.3.0-1.dsc
 0bb99c9eaad50376888050a2f0e80abb 79441 rust optional 
rust-pretty-assertions_1.3.0.orig.tar.gz
 a73d97d2ee0d2181d84538f476bae40a 3320 rust optional 
rust-pretty-assertions_1.3.0-1.debian.tar.xz
 564e16b7c09e71e1c5307b78573ffa1f 7809 rust optional 
rust-pretty-assertions_1.3.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmN/WRMUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/Xt3GxAAjJNjpvBeAzuyL0H8ciT3+knTtijB
uHA6jZmA2k++GduhqHGw2XvoETO0ioVMJ6fQc5f6peHNjpuvbUQoLoBTvqOxMuBW
I6oruq5jcE1n9V6HNFe0BrCRPM2QgwFJitJ/RmTG5Ez2Av2SFQ92aAmU10BY97or
nRW+eN38l8ZrcQqLy9lV4eDKcpaa7CP4dvkUi8Bh8CcdyoJFEZkTvlVp/yAVY2+I
r8wg/LKaHeEwovRrxzQWiKosjkWtH6fn+Rd3aSih9zFwcyAbtBMLATm49VDjSnKj
J7Gg5DzJhV38bqsu2DZuW04j24o0X11Ogg3WiNeLuk+p03JZwcS6Q07FJbBdUikr

Bug#1024747: marked as done (rust-env-logger: please update to v0.9.3)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 11:50:03 +
with message-id 
and subject line Bug#1024747: fixed in rust-env-logger 0.9.3-1
has caused the Debian Bug report #1024747,
regarding rust-env-logger: please update to v0.9.3
to be marked as done.

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

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


-- 
1024747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-env-logger
Version: 0.9.0-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please update to newer upstream release v0.9.3.


-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmN/L0MACgkQLHwxRsGg
ASF4+xAAi3aZLmE1MC+sTciedsgTffiQ+88OWtVh8fyp/LOf0qxU6sCOcah8+vEG
HVVb/6BA/sR9Sf1lBl4IMQ4Bb3Ky7biByFhFriW0gUFnnNuyVEQtGKNYjUANgF5V
x62ejQ+u9qeUfxs+jQuiWjDhwY78raC8y+S/AZ5yq99G70qQm3dDXpvdqGtXBhRi
Qd6ZYeZM/RJACJbuSwfjHBRZfURfSfjCD6x0x6c1jCd8ns87cczJAMlvozyqD18C
uzdgZF5BEZG+oz0Cf8OOmcJyfllg+UxOJH0ww26hjjeiRlqD8gc8qIFYSDt2q0vY
gJxowA5SEaJwOUnZOU729iK7gZ6ierTpaRWjD1Zzti0h62Dz+UTeDfzkBc2+Tl3v
4xTacNFf/iTwXfHamhEiTXMKW2ltPiLTvGghYaajXHQXRdb7ex9ymP6guOJN1PSm
+dKxUn1KLrI2Nkt2sP3vjlT1YDtLzfKYK1irF9tKO1ETAnjQ96nLgdbZfmk6rt38
MpBDNjsbsAA9EdBJFlBPrEpKGAWs3g7E6130GW5W3hrHkT2T1E/rhsLL1PqQONYS
dxe0FA9QDbWoOQAJ88ObgLa98TVIx1ZQXAemleekfz88i69H/jj07obcFgEsE4R4
N9szY86LwBR5FOEegWY85XhPzVZuR0MTbqWfJ01kNl9SaASk5B8=
=bucR
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: rust-env-logger
Source-Version: 0.9.3-1
Done: Peter Michael Green 

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

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

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

Debian distribution maintenance software
pp.
Peter Michael Green  (supplier of updated rust-env-logger 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 24 Nov 2022 11:13:01 +
Source: rust-env-logger
Architecture: source
Version: 0.9.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Peter Michael Green 
Closes: 1024747
Changes:
 rust-env-logger (0.9.3-1) unstable; urgency=medium
 .
   * Team upload.
   * Package env_logger 0.9.3 from crates.io using debcargo 2.6.0 (Closes: 
#1024747)
Checksums-Sha1:
 f6ab17383a55e70bbe3d40570636c14d64a7048d 2990 rust-env-logger_0.9.3-1.dsc
 d4e036865058ee95e4bf32b0b58b5ff11fddda0c 33291 
rust-env-logger_0.9.3.orig.tar.gz
 564bdff04e1ec2def28094ad274481bc5aed2099 3392 
rust-env-logger_0.9.3-1.debian.tar.xz
 b8f77ae20f4c1d60b263038d3896e2696ea16e3a 8648 
rust-env-logger_0.9.3-1_source.buildinfo
Checksums-Sha256:
 81fe7ee569e94aaa39c90077700957657c6608fe02f428762c71cf331e240564 2990 
rust-env-logger_0.9.3-1.dsc
 a12e6657c4c97ebab115a42dcee77225f7f482cdd841cf7088c657a42e9e00e7 33291 
rust-env-logger_0.9.3.orig.tar.gz
 341fb5fe48d4ea7081c6d3bfec0c77010febbff8fa2ade82b2ff672b8b5dfce8 3392 
rust-env-logger_0.9.3-1.debian.tar.xz
 b9dd13e371583d92f2502eb547d7dcba7c3f5e8085b18bfbab9e6924de3c9734 8648 
rust-env-logger_0.9.3-1_source.buildinfo
Files:
 be733a52218d7570765e37e70789d8a9 2990 rust optional rust-env-logger_0.9.3-1.dsc
 c25e1a69f2d40b3f6f8dae4b4459413d 33291 rust optional 
rust-env-logger_0.9.3.orig.tar.gz
 b25e7de1053b6419f5b0677575131c9e 3392 rust optional 
rust-env-logger_0.9.3-1.debian.tar.xz
 190f4d5eb3f7431c28f46fcce3c47a00 8648 rust optional 
rust-env-logger_0.9.3-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmN/U5YUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XvcXA/+I87PTK1viN8qJWFAwVUOYOCMUDMm
btvek2nq/M1I+GILqakfacr9396Xpog0A7Y0RXF2zS7BYsIkr+akfJoBZpdoriX1
LnaTP7kkAfibEubTTXjNTTRDlhM7i2ggMC6BX3HTbGgau7XjKUHoKmGsK3qI4XtA
mUx5yxeLu5PZ2s21UhlV/iBDwleoFWSe+Dg65IoG69fVPDoTfZfndro5uj95kKbi
r0gqa1wn4GZz4fs9tchApeZ6ZN7GqOL/rdsTEB8w26NuLefLa3PX/QvCSKJ1FtXC
9tx/ocWp4SdHA7oFR+j0/cT1IqZDxRJogxxKG33NsA8EeQBRFt3D0sE6R4n/mgka
3W3ZCfnqWnBVrdr43qxzR6jKqCBeDv0kLJE5LzptFvAi5iNaV79qiU0wegECjFl6
VrLSldbCstrJXpJIzf0W+ZwSPftmlkIo/8upldFpWbLHJCyBIvBzlyQCkemC95Y8
nFgO9f9aRJhETP91XU4brCodaVeW+C7aKa4A4JySWVxSEdUKjvu8TSDnOofe5quH

Bug#1024522: marked as done (python-leidenalg FTBFS with igraph 0.10.2)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 11:23:24 +
with message-id 
and subject line Bug#1024522: fixed in python-leidenalg 0.9.0-1
has caused the Debian Bug report #1024522,
regarding python-leidenalg FTBFS with igraph 0.10.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.)


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

https://buildd.debian.org/status/fetch.php?pkg=python-leidenalg=amd64=0.8.10-1%2Bb3=1668985384=0

...
src/leidenalg/GraphHelper.cpp: In member function ‘void 
Graph::cache_neighbour_edges(size_t, igraph_neimode_t)’:
src/leidenalg/GraphHelper.cpp:465:33: error: cannot convert ‘igraph_vector_t*’ 
to ‘igraph_vector_int_t*’
  465 |   igraph_incident(this->_graph, incident_edges, v, mode);
  | ^~
  | |
  | igraph_vector_t*
In file included from /usr/include/igraph/igraph.h:57,
 from include/GraphHelper.h:4,
 from src/leidenalg/GraphHelper.cpp:1:
/usr/include/igraph/igraph_interface.h:74:90: note:   initializing argument 2 
of ‘igraph_error_t igraph_incident(const igraph_t*, igraph_vector_int_t*, 
igraph_integer_t, igraph_neimode_t)’
   74 | IGRAPH_EXPORT igraph_error_t igraph_incident(const igraph_t *graph, 
igraph_vector_int_t *eids, igraph_integer_t vid,
  | 
~^~~~
...
--- End Message ---
--- Begin Message ---
Source: python-leidenalg
Source-Version: 0.9.0-1
Done: Andreas Tille 

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated python-leidenalg package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 24 Nov 2022 11:18:04 +0100
Source: python-leidenalg
Architecture: source
Version: 0.9.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 1024522
Changes:
 python-leidenalg (0.9.0-1) unstable; urgency=medium
 .
   [ Étienne Mollier ]
   * New upstream version
 .
   [ Andreas Tille ]
   * Versioned Build-Depends: python-igraph (>= 0.10)
 Closes: #1024522
Checksums-Sha1:
 1360cba15889ca4760d2be40a537765deb833513 2385 python-leidenalg_0.9.0-1.dsc
 e88ed385600129266e6d444db2be71b41480f78b 483479 
python-leidenalg_0.9.0.orig.tar.gz
 ee3ffb3e164c8952ca5c0a53890fe221d0028bf2 3964 
python-leidenalg_0.9.0-1.debian.tar.xz
 1737eea43ad919e43fb0474371f2250e0a0c61a3 8536 
python-leidenalg_0.9.0-1_amd64.buildinfo
Checksums-Sha256:
 d958756a57b2eae91f5cd768037bcd34a9f24a99b0fd94fb37df046ab1db5f76 2385 
python-leidenalg_0.9.0-1.dsc
 b31e446ca2fadbcb280b6ddb1008ac543a2d6b601e936040a3ec62c2a8ba8108 483479 
python-leidenalg_0.9.0.orig.tar.gz
 e197cf54941445575022ea511b89eddc8327a57dcf3d1d67b5dec8ae4e8f1b08 3964 
python-leidenalg_0.9.0-1.debian.tar.xz
 a2a334396c4188b2202e02b25fef478e042aeededa7a9ba9c2b887a11db12caf 8536 
python-leidenalg_0.9.0-1_amd64.buildinfo
Files:
 ff2e1a37988520e7de02dfde11fba026 2385 science optional 
python-leidenalg_0.9.0-1.dsc
 bd4231fb56c82936d80fee465a8e8d39 483479 science optional 
python-leidenalg_0.9.0.orig.tar.gz
 88e7f2063a4c647efee2662ad9c17d28 3964 science optional 
python-leidenalg_0.9.0-1.debian.tar.xz
 1293ea0e1d759b43b84d9f2b0162e26c 8536 science optional 
python-leidenalg_0.9.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmN/SnQRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHaQxAAjiUGxPnDg8luGZOjOVQURN6xPjhFEK5F
kAhkE+VdUautcAZ69/7G5jf3+TV73ij++CVTpeHk7cNsTNBtltVg4EW8Drc2AqX/
J5JqeBUtfUFV/f0R/rJNftiKnnEekuE37iAklvwZJjPzPBaZQXdqQq17Gdt7OcI0
lRUARkATbUf5yNrEXU9mJ/Z6yiRGiYdGw+JF5HxKRWMNYTlw7EFGiBdOeyxLPUZX
YkKKxhPaKxs9iNO6b15ZOBSd+bzB+Vm8TzG04tZBjeUMkllyqEqDPv5yh5X+jkwa

Bug#1024458: marked as done (seqan-needle: binary-all FTBFS)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 11:23:38 +
with message-id 
and subject line Bug#1024458: fixed in seqan-needle 1.0.1.0.0.git.3011926+ds-4
has caused the Debian Bug report #1024458,
regarding seqan-needle: binary-all FTBFS
to be marked as done.

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

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


-- 
1024458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024458
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: seqan-needle
Version: 1.0.1.0.0.git.3011926+ds-2
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=seqan-needle=all=1.0.1.0.0.git.3011926%2Bds-2=1668618292=0

...
   debian/rules override_dh_auto_build-indep
make[1]: Entering directory '/<>'
cd obj-* && /usr/bin/make doc
/bin/sh: 1: cd: can't cd to obj-*
make[1]: *** [debian/rules:26: override_dh_auto_build-indep] Error 2
--- End Message ---
--- Begin Message ---
Source: seqan-needle
Source-Version: 1.0.1.0.0.git.3011926+ds-4
Done: Andreas Tille 

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated seqan-needle package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 24 Nov 2022 11:38:47 +0100
Source: seqan-needle
Architecture: source
Version: 1.0.1.0.0.git.3011926+ds-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 1024458
Changes:
 seqan-needle (1.0.1.0.0.git.3011926+ds-4) unstable; urgency=medium
 .
   * Team upload.
   * Create doc without previous binary build
 Closes: #1024458
Checksums-Sha1:
 16fda09863bee9848bddfb3fee149e290e81420b 2281 
seqan-needle_1.0.1.0.0.git.3011926+ds-4.dsc
 e484a3867f677c7a91ac21744337637bcdcfd25b 6052 
seqan-needle_1.0.1.0.0.git.3011926+ds-4.debian.tar.xz
 d10b115fd8035b6c1f68ebe6dcfd7dc0e6bd2d79 8208 
seqan-needle_1.0.1.0.0.git.3011926+ds-4_amd64.buildinfo
Checksums-Sha256:
 3560b1624aff0499dd8f47954890d2840508b78152f706bfcad796863d5a523a 2281 
seqan-needle_1.0.1.0.0.git.3011926+ds-4.dsc
 0f39029448ddca892db717c02cfd153eccd4b315ee6a2fb42db73d7eaed454ef 6052 
seqan-needle_1.0.1.0.0.git.3011926+ds-4.debian.tar.xz
 c402ff0b4d539286eadd002c7ca69d4842c208a5243e575eef9480c3893af3f6 8208 
seqan-needle_1.0.1.0.0.git.3011926+ds-4_amd64.buildinfo
Files:
 e827bbaf0fd55b0480ee77ec65db47eb 2281 science optional 
seqan-needle_1.0.1.0.0.git.3011926+ds-4.dsc
 16c8be5f321c4109a6b2980b8139efa0 6052 science optional 
seqan-needle_1.0.1.0.0.git.3011926+ds-4.debian.tar.xz
 980d698655306687d63927b72d8cda89 8208 science optional 
seqan-needle_1.0.1.0.0.git.3011926+ds-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmN/StERHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHxfg//Zva/FxVpJevX1eJvovcrJcriPtBCMZk1
AjmcleKj2EEq9EtU92lsfNvEeUft4JE2fw4cPeONL2ZQ95hH9az9n0Q6h72K3Z0H
yIYsqU8JRYMm3QxFiqDMClSAJSqt6v+AEuWeEoQzXOfOwo38IOLuQS9B+jL5M7w7
5rkZplXprJTqyWD3Slmm41D8No3gLDwqIgjwhopzL2c9ead32gYFP2Hs+VsIJ3Pn
QEhm5pnYNFt/avRVJ2rrf9SO3HQew9LRatfQgUltgdvRRG3ZBa+to3rvL/IQKUrY
fvWO712Bi9UQ23hX/N+xR8Sq/8m+mn4p/5AunbQOpDrosPq21yhl7MXRwMWpoJWr
lFvD9qv7dNzx7+nQ4qlRFwtzjiYHKr3MYGTky0lyPxRRB+Mj1ovjigK65UsNcW7U
oQ16Y9Kd5mj6h9udHyd2j1YdS+qgQQZ6d9vxEqa6N/ygah0IqsIgL03tGhvbXGRD
PBnPBgUPp44qvP8x7H/h/k6f3swCXcrUo2tcxLGFceQP3a4oLNZOZNSzOMtHgg4r
bfZiEOc2M8hJOxtEI5xwCvq9S2/jOUvdU+sfT3FIFZnIgtuZ9pO45QnDnOMhEzCW
9KBVBCGgShk6IXhdJhls26B11t2fzrp3zAB675H0p51strTMbvGv175/crG0zg4+
Qu1t4MxaYWY=
=atv/
-END PGP SIGNATURE End Message ---

Bug#1024018: marked as done (python-cleo: CVE-2022-42966)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 11:22:55 +
with message-id 
and subject line Bug#1024018: fixed in python-cleo 1.0.0a5-1
has caused the Debian Bug report #1024018,
regarding python-cleo: CVE-2022-42966
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.)


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

Hi,

The following vulnerability was published for python-cleo.

CVE-2022-42966[0]:
| An exponential ReDoS (Regular Expression Denial of Service) can be
| triggered in the cleo PyPI package, when an attacker is able to supply
| arbitrary input to the Table.set_rows method

https://research.jfrog.com/vulnerabilities/cleo-redos-xray-257186/

This doesn't seem to have been reported upstream yet, can you please
take care of that?`

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

For further information see:

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

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: python-cleo
Source-Version: 1.0.0a5-1
Done: Emmanuel Arias 

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

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

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

Debian distribution maintenance software
pp.
Emmanuel Arias  (supplier of updated python-cleo 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, 22 Nov 2022 12:39:05 -0300
Source: python-cleo
Architecture: source
Version: 1.0.0a5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Emmanuel Arias 
Closes: 1024018
Changes:
 python-cleo (1.0.0a5-1) unstable; urgency=medium
 .
   * d/watch: Update link to upstream, now is under python-poetry umbrella.
 - Remove debian uupdate from watch file.
   * New upstream version.
   * d/patches: Add patch from upstream to avoid ReDoS security issue
 (CVE-2022-42966). Closes: #1024018.
   * d/control: Bump Standards-Version to 4.6.1.1 (from 4.6.0.1; no further
 changes).
   * d/control: Remove python3-clickit from B-Depends, it's not longer needed.
   * d/copyright: Update Source key in the file.
   * d/control: Update Homepage to the new upstream repository.
   * d/patches: Remove
 0001-add_stylesheet-deprecated-use-add_css_file-instead.patch file is
 already applied for upstream.
   * d/control: Add python3-pylev as Build Depends.
   * d/tests: Update cleo-tests.py according to the new upstream release API.
   * d/control: Remove trivial autopkgtest-pkg-python.
Checksums-Sha1:
 9a6c4079d3e96f49267d26ffa3a27334b6a6a9c4 2369 python-cleo_1.0.0a5-1.dsc
 d0a3cafe1640e9570bd4ba2a1a5a3cac3068123d 144117 python-cleo_1.0.0a5.orig.tar.gz
 e2f7142f52566c6088080864578a61b9812b5698 4120 
python-cleo_1.0.0a5-1.debian.tar.xz
 f87be30def7bb38b2649f9d9e0ac409df8035e18 8881 
python-cleo_1.0.0a5-1_amd64.buildinfo
Checksums-Sha256:
 29d0c7590412e8ecc4c86d4c9e2dcfc5fe9080214c8fd50bfc773e2e085d000f 2369 
python-cleo_1.0.0a5-1.dsc
 b75424b2c3f71dec06342290b255d725a4c02f83f3baa98b0a805162f09515da 144117 
python-cleo_1.0.0a5.orig.tar.gz
 c19f2bf4a8f70df43019ebc68544a3a542a4054c44571ab7e210f5e5e44ed8b1 4120 
python-cleo_1.0.0a5-1.debian.tar.xz
 ae80b05dabafa5d46b3098458d4dffe300bd6feae476fe4bc3561c2ae346d4d1 8881 
python-cleo_1.0.0a5-1_amd64.buildinfo
Files:
 25f28c37f32be010e07c366bb90c03bd 2369 python optional python-cleo_1.0.0a5-1.dsc
 8146328973f05ae6d7d2f42f50766d4d 144117 python optional 
python-cleo_1.0.0a5.orig.tar.gz
 125178f5758da77a25f1520647308710 4120 python optional 
python-cleo_1.0.0a5-1.debian.tar.xz
 7233f2dfc027f0af686818c2727e33c2 8881 python optional 
python-cleo_1.0.0a5-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEE3lnVbvHK7ir4q61+p3sXeEcY/EFAmN/ST8THGVhbWFudUB5

Bug#1024701: marked as done (libphonenumber8 update breaks evolution)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 11:20:22 +
with message-id 
and subject line Bug#1024701: fixed in libphonenumber 8.12.57+ds-2
has caused the Debian Bug report #1024701,
regarding libphonenumber8 update breaks evolution
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.)


-- 
1024701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024701
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libphonenumber8
Version: 8.12.57+ds-1+b2
Severity: serious

After updating libphonenumber8 from version 8.12.57+ds-1+b1 to version
8.12.57+ds-1+b2 in Debian Sid, Gnome Evolution fails to launch.

Downgrading to the previous version (still in Bookworm) fixes the
issue.

Regards


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: libphonenumber
Source-Version: 8.12.57+ds-2
Done: Jochen Sprickerhof 

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 24 Nov 2022 12:03:20 +0100
Source: libphonenumber
Architecture: source
Version: 8.12.57+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Jochen Sprickerhof 
Closes: 1024701
Changes:
 libphonenumber (8.12.57+ds-2) unstable; urgency=medium
 .
   * Team upload.
   * Convert to debhelper
   * Expose protobuf ABI (Closes: #1024701)
   * Bump policy version (no changes)
   * Move package description to source package
   * Drop old Conflicts/Replaces
Checksums-Sha1:
 544dd8220be2f51d3aa132a5c41d87694d432ab0 2899 libphonenumber_8.12.57+ds-2.dsc
 29be7beb720f1aaac9dc6869014f5a11e4fea13d 11944 
libphonenumber_8.12.57+ds-2.debian.tar.xz
 723410b32318da06636fa2ec85de89ec795092d5 19351 
libphonenumber_8.12.57+ds-2_source.buildinfo
Checksums-Sha256:
 39a6db5078070a4b42f1e915c76fb926836cff63ec0ec2913e60c9b667aa75d9 2899 
libphonenumber_8.12.57+ds-2.dsc
 c9ee290c9a9950b28fb832f602e550dbf041db5855001ead159ab7fc93e85168 11944 
libphonenumber_8.12.57+ds-2.debian.tar.xz
 5320a4bc2244a8100f1d156198738e6dc2ef12d3b7d0e3dc6cf94788386d8f9c 19351 
libphonenumber_8.12.57+ds-2_source.buildinfo
Files:
 397e3913ccf75f4d8fff85c9b64e18d0 2899 libs optional 
libphonenumber_8.12.57+ds-2.dsc
 d26f40bf89a0079fb4878cdafe9d1c8c 11944 libs optional 
libphonenumber_8.12.57+ds-2.debian.tar.xz
 50725b4e815885ded890102fb01b9675 19351 libs optional 
libphonenumber_8.12.57+ds-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAmN/T7AACgkQW//cwljm
lDM0tw/7B6XKWKjDVFcFYot3DkqqqYHIr8122z2eL/onFvQX87ql5nuKCZ3xhM8q
1f4JdNRJRmgSRl9ArJSP6UgKklVe9heteegbg3oMqT0MebEHl6w9T2QAl+Ol5wFp
+N8KPs0bFBX2S+0y0xdF+st8PiNRC3R7UlyMie5X7oRK/G6TyeYURPyS8pM86TqW
PabvpONGCqyYPSAaV7LdXWCoiOJPIyvgwaTjeiowvBhMhL6oKLTmGaFn1mcov/Gn
F1ZQmkd/JSRduFVRF27j4CUjRi3gxZMK/NUhfTQ8/Dxo/sK1p/LGmmM7aF6VaFUc
Bj+T4s4CUi8TO28/tL6Ujuv4OV2qyjve2HJbIgMK9HQmUUwrBUkBy9PIw7p7pQn/
4Ztb3snWg5oeNpflX5lKpZX8BZ0cl4xTAyFq2rSHYBA4l2XSjcYZ8jzzqq4qFr6S
LT37dFoAeglrZLXTpJFip/yIsaI9g1XZBmfvlUzOV723bw0d5jn2R86t0vpHhaJI
OyrgDjtuMo24v1JnQu9B1uh5qw0pAsPJjPaZsxXAN4BXp2iouFumZ/zwN5I/xnyq
n/JhsekKWHYnHuVdw/90yfxv5dpEYruuX0yEVfTzh8WpnDy/Y9leiECUA2LHp6a+
qQdzczGy/JU75VxiC6XTdKlOYhQqqjHcr+X8upYqLZdC/3uExlY=
=19mP
-END PGP SIGNATURE End Message ---

Bug#1008434: marked as done (golang-github-hashicorp-go-plugin: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/hashicorp/go-plugin github.com/hashicorp/go-p

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 11:58:43 +0100
with message-id 
and subject line Re: Bug#1008434: golang-github-hashicorp-go-plugin: FTBFS: 
dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 
github.com/hashicorp/go-plugin github.com/hashicorp/go-plugin/internal/plugin 
returned exit code 1
has caused the Debian Bug report #1008434,
regarding golang-github-hashicorp-go-plugin: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/hashicorp/go-plugin 
github.com/hashicorp/go-plugin/internal/plugin returned exit code 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.)


-- 
1008434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008434
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-hashicorp-go-plugin
Version: 1.0.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220326 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> DH_GOLANG_EXCLUDES="examples test/grpc" \
> dh_auto_test
>   cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 
> github.com/hashicorp/go-plugin github.com/hashicorp/go-plugin/internal/plugin
> === RUN   TestClient_testInterfaceReattach
> 2022-03-26T19:39:12.362Z [DEBUG] plugin: starting plugin: 
> path=/tmp/go-build1311877249/b001/go-plugin.test 
> args=[/tmp/go-build1311877249/b001/go-plugin.test, 
> -test.run=TestHelperProcess, --, test-interface-daemon]
> 2022-03-26T19:39:12.362Z [DEBUG] plugin: plugin started: 
> path=/tmp/go-build1311877249/b001/go-plugin.test pid=1239565
> 2022-03-26T19:39:12.362Z [DEBUG] plugin: waiting for RPC address: 
> path=/tmp/go-build1311877249/b001/go-plugin.test
> 2022-03-26T19:39:12.367Z [DEBUG] plugin.go-plugin.test: plugin address: 
> address=/tmp/plugin1699243854 network=unix timestamp=2022-03-26T19:39:12.367Z
> 2022-03-26T19:39:12.367Z [DEBUG] plugin: using plugin: version=1
> 2022-03-26T19:39:13.369Z [DEBUG] plugin.go-plugin.test: 2022/03/26 19:39:13 
> [ERR] plugin: plugin server: accept unix /tmp/plugin1699243854: use of closed 
> network connection
> 2022-03-26T19:39:13.370Z [DEBUG] plugin: plugin process exited: 
> path=/tmp/go-build1311877249/b001/go-plugin.test pid=1239565
> 2022-03-26T19:39:14.367Z [DEBUG] plugin: reattached plugin process exited
> 2022-03-26T19:39:14.367Z [DEBUG] plugin: plugin exited
> --- PASS: TestClient_testInterfaceReattach (2.01s)
> === RUN   TestClient
> 2022-03-26T19:39:14.367Z [DEBUG] plugin: starting plugin: 
> path=/tmp/go-build1311877249/b001/go-plugin.test 
> args=[/tmp/go-build1311877249/b001/go-plugin.test, 
> -test.run=TestHelperProcess, --, mock]
> 2022-03-26T19:39:14.368Z [DEBUG] plugin: plugin started: 
> path=/tmp/go-build1311877249/b001/go-plugin.test pid=1239573
> 2022-03-26T19:39:14.368Z [DEBUG] plugin: waiting for RPC address: 
> path=/tmp/go-build1311877249/b001/go-plugin.test
> 2022-03-26T19:39:14.373Z [DEBUG] plugin: using plugin: version=1
> 2022-03-26T19:39:14.373Z [ERROR] plugin: client: error="dial tcp :1234: 
> connect: connection refused"
> 2022-03-26T19:39:14.373Z [WARN]  plugin: plugin failed to exit gracefully
> 2022-03-26T19:39:14.373Z [DEBUG] plugin: plugin process exited: 
> path=/tmp/go-build1311877249/b001/go-plugin.test pid=1239573 error="signal: 
> killed"
> --- PASS: TestClient (0.01s)
> === RUN   TestClient_killStart
> 2022-03-26T19:39:14.374Z [DEBUG] plugin: starting plugin: 
> path=/tmp/go-build1311877249/b001/go-plugin.test 
> args=[/tmp/go-build1311877249/b001/go-plugin.test, 
> -test.run=TestHelperProcess, --, bad-version, /tmp/plugin2389898487/booted]
> 2022-03-26T19:39:14.374Z [DEBUG] plugin: plugin started: 
> path=/tmp/go-build1311877249/b001/go-plugin.test pid=1239579
> 2022-03-26T19:39:14.374Z [DEBUG] plugin: waiting for RPC address: 
> path=/tmp/go-build1311877249/b001/go-plugin.test
> 2022-03-26T19:39:14.379Z [WARN]  plugin: plugin failed to exit gracefully
> 2022-03-26T19:39:14.379Z [DEBUG] plugin: plugin process exited: 
> path=/tmp/go-build1311877249/b001/go-plugin.test pid=1239579 error="signal: 
> killed"
> --- PASS: TestClient_killStart (0.01s)
> === RUN   TestClient_testCleanup
> 2022-03-26T19:39:14.380Z [DEBUG] plugin: starting plugin: 
> path=/tmp/go-build1311877249/b001/go-plugin.test 
> args=[/tmp/go-build1311877249/b001/go-plugin.test, 
> -test.run=TestHelperProcess, --, cleanup, /tmp/plugin3397144587/output]
> 2022-03-26T19:39:14.380Z [DEBUG] plugin: plugin started: 
> 

Bug#980275: marked as done (Please depend on media-types instead of mime-support)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 10:04:29 +
with message-id 
and subject line Bug#980275: fixed in apache2 2.4.54-4
has caused the Debian Bug report #980275,
regarding Please depend on media-types instead of mime-support
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.)


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

Dear apache2 maintainers,

I have recently split the `mime-support` package into two: `mailcap` for
the mailcap system, and `media-types` for providing `/etc/mime.types`.
The goal is to allow minimal systems without `mailcap`.

`mime-support` is now a transitional package, and it would be great if
users could be able to remove it after the _Bookworm_ release.

Please Depend on `media-types` instead of `mime-support` if you only
need the `/etc/mime.types` file.

Have a nice week-end,

Charles

-- 
Charles Plessy Nagahama, Yomitan, Okinawa, Japan
Tooting from work,   https://mastodon.technology/@charles_plessy
Tooting from home, https://framapiaf.org/@charles_plessy
--- End Message ---
--- Begin Message ---
Source: apache2
Source-Version: 2.4.54-4
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated apache2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 24 Nov 2022 10:45:00 +0100
Source: apache2
Built-For-Profiles: nocheck
Architecture: source
Version: 2.4.54-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Apache Maintainers 
Changed-By: Yadd 
Closes: 980275
Changes:
 apache2 (2.4.54-4) unstable; urgency=medium
 .
   [ Charles Plessy ]
   * Replace mime-support transition package with media-types (Closes: #980275)
 .
   [ Hendrik Jäger ]
   * fix mislead safety precautions: don't hide errors when enabling a module.
 MR !20
   * fix trailing spaces and indentation inconsistencies. MR !19 !21 !22
   * Fix confusing and impractical naming: rename default-ssl.conf into
 000-default-ssl.conf. MR !23
   * Fix confusing keyword: replace _default_ by *. MR !24
Checksums-Sha1: 
 1cc112119c9e7b70b4405310b7ff241be9352bfe 3488 apache2_2.4.54-4.dsc
 ef078164fa31bbab23d077b60ed80872ffe93f1e 899572 apache2_2.4.54-4.debian.tar.xz
Checksums-Sha256: 
 2ef2ed0c4996b0e70c85c379755a62a62f40840f9e8dd0a1c4c6d2c2b0ec535c 3488 
apache2_2.4.54-4.dsc
 496535ffef8af4776b2dba0c09d1c5472efbbb45f0f8d5a93bce655293b5e865 899572 
apache2_2.4.54-4.debian.tar.xz
Files: 
 f371660a0e5542a176d3e3c2bf7cd4fd 3488 httpd optional apache2_2.4.54-4.dsc
 9b769ac142ee552b09fe83cc48cbcfdc 899572 httpd optional 
apache2_2.4.54-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmN/PhYACgkQ9tdMp8mZ
7umqFRAAjAvYVcR996xz1Oj4v3UK5Ml55eoE17dXIYr9ZhqR1kCUcHtXymUV6mKO
jeLZMssHQBhsdzkigoKtTA5NuYtJEt1cmLU0c/xwx5nybWpiCHaTJuHdgROS9Q9u
Di7iEP4r9iyF5h6nVOVDktblfxcQP4TlTOW2HkhbArEXRCNKMtVq7jRpUVkWRGcL
Y3tac9y9sKjyI6YqlcMxznnhBWPoGgNyC7n0jYMkgtW426vED2RF3oeGVkK/hC/I
6U3nZyTi034BEsAsfjrbA+sealGXOKStxOiMupw5LZPyT5ukg7jFa2cK8Hmkxv2T
RKSc+4unHtOX4NDfJzFf3QXrfj7iNpq5G9sUxcSdU2KwPznWxtTlx0EFnZuVw0e9
7My6z8bDxoCqSyvNVX10MrQYfaGrm1r1yHVfdKKZ7E9hko5SxoE23z8B3dPNFdAq
9szEvzsOOaH60Y56yy/prcJWphjSzTcA9IswuupdW4/nv4GTRgqyRWkpSmXd/DyL
f9pDpuOa2NTIC5xePxhcgOhmszuYqhxCImFt7nzuIbCl1iybA6grXyvCiJWmkeFr
0gaI3vvVoxLrx90BGmeCIDXkJqrA0TQihy4quq9qA/XNialzKgBW29FYvmopNOq6
hu/esYTJCd77QGVnzhvftSH317s3RgsS3oKEzOsTIkhCsD9stIA=
=Q1jv
-END PGP SIGNATURE End Message ---

Processed: RFS: qt-android-6.2/6.2.4+ds-1 [ITP] -- Qt for Android

[Debian Bug Tracking System]

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

> close 1001759
Bug #1001759 [sponsorship-requests] RFS: qt-android-6.2/6.2.4+ds-1 [ITP] -- Qt 
for Android
Marked Bug as done
> stop
Stopping processing here.

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

Bug#1020018: marked as done (libxmlada: FTBFS: unsatisfiable build-dependency: unicode-data (< 15~) but 15.0.0-1 is to be installed)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 09:34:13 +
with message-id 
and subject line Bug#1020018: fixed in libxmlada 23.0.0-1
has caused the Debian Bug report #1020018,
regarding libxmlada: FTBFS: unsatisfiable build-dependency: unicode-data (< 
15~) but 15.0.0-1 is to be 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.)


-- 
1020018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020018
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libxmlada
Version: 22.0.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), build-essential, fakeroot, 
> gnat, gnat-11, unicode-data (>= 14~), unicode-data (<< 15~), 
> dh-sequence-sphinxdoc, python3-sphinx (>= 1.6.3-2), latexmk, tex-gyre, 
> texlive-fonts-recommended, texlive-plain-generic, texlive-latex-extra
> Filtered Build-Depends: debhelper-compat (= 13), build-essential, fakeroot, 
> gnat, gnat-11, unicode-data (>= 14~), unicode-data (<< 15~), 
> dh-sequence-sphinxdoc, python3-sphinx (>= 1.6.3-2), latexmk, tex-gyre, 
> texlive-fonts-recommended, texlive-plain-generic, texlive-latex-extra
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [492 B]
> Get:5 copy:/<>/apt_archive ./ Packages [564 B]
> Fetched 2013 B in 0s (118 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: unicode-data (< 15~) but 15.0.0-1 
> is to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2022/09/17/libxmlada_22.0.0-3_unstable.log

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

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

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

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

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

Debian distribution maintenance software
pp.
Nicolas Boulenguez  (supplier of updated libxmlada package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 24 Nov 2022 08:52:59 +
Source: libxmlada
Architecture: 

Bug#1024739: marked as done (nmu: libmcfp_1.2.2-1)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 10:01:46 +0100
with message-id 
and subject line Re: Bug#1024739: nmu: libmcfp_1.2.2-1
has caused the Debian Bug report #1024739,
regarding nmu: libmcfp_1.2.2-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.)


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

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Hello,

I want to request binNMU on amd64 for recently accepted new package.

  nmu libmcfp_1.2.2-1 . amd64 . unstable . -m "Rebuild on buildd"

Thanks,
Andrius
--- End Message ---
--- Begin Message ---

Hi,

On 24-11-2022 07:52, Andrius Merkys wrote:

I want to request binNMU on amd64 for recently accepted new package.

   nmu libmcfp_1.2.2-1 . amd64 . unstable . -m "Rebuild on buildd"


A newer version was uploaded. Closing.

Paul


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

Bug#1024736: marked as done (node-xmldom: CVE-2022-39353)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 08:36:02 +
with message-id 
and subject line Bug#1024736: fixed in node-xmldom 0.8.6-1
has caused the Debian Bug report #1024736,
regarding node-xmldom: CVE-2022-39353
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.)


-- 
1024736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024736
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-xmldom
Version: 0.8.3-1
Severity: important
Tags: security upstream
Forwarded: https://github.com/jindw/xmldom/issues/150
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for node-xmldom.

CVE-2022-39353[0]:
| xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core)
| `DOMParser` and `XMLSerializer` module. xmldom parses XML that is not
| well-formed because it contains multiple top level elements, and adds
| all root nodes to the `childNodes` collection of the `Document`,
| without reporting any error or throwing. This breaks the assumption
| that there is only a single root node in the tree, which led to
| issuance of CVE-2022-39299 as it is a potential issue for dependents.
| Update to @xmldom/xmldom@~0.7.7, @xmldom/xmldom@~0.8.4 (dist-tag
| latest) or @xmldom/xmldom@=0.9.0-beta.4 (dist-tag next). As a
| workaround, please one of the following approaches depending on your
| use case: instead of searching for elements in the whole DOM, only
| search in the `documentElement`or reject a document with a document
| that has more then 1 `childNode`.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-39353
https://www.cve.org/CVERecord?id=CVE-2022-39353
[1] https://github.com/jindw/xmldom/issues/150
[2] https://github.com/xmldom/xmldom/security/advisories/GHSA-crh6-fp67-6883

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: node-xmldom
Source-Version: 0.8.6-1
Done: Yadd 

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

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

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-xmldom package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 24 Nov 2022 09:03:06 +0100
Source: node-xmldom
Architecture: source
Version: 0.8.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1024736
Changes:
 node-xmldom (0.8.6-1) unstable; urgency=medium
 .
   * Team upload
   * Set upstream metadata fields: Security-Contact.
   * New upstream release (Closes: #1024736, CVE-2022-39353)
Checksums-Sha1: 
 c7215ce3fb5d271a1a2d70e75e27cb0b6ac198cb 2022 node-xmldom_0.8.6-1.dsc
 0c208388138933518748680a3e686175e02ce532 318742 node-xmldom_0.8.6.orig.tar.gz
 a9841bcedfa7eb2b574dba180d94e63cfc258a5b 3512 node-xmldom_0.8.6-1.debian.tar.xz
Checksums-Sha256: 
 7e461daba7c7b1a237364648a295939af1c7f73fa8599bc7c3e0be9b6920e196 2022 
node-xmldom_0.8.6-1.dsc
 ff8313ae508287c23fda321655c94247ca5e4e841487b7103b5259fbb903dd97 318742 
node-xmldom_0.8.6.orig.tar.gz
 0cb251321ad51efaa5f2d0a6340e666a601c58b80907e0de766e4f49fad6dc8f 3512 
node-xmldom_0.8.6-1.debian.tar.xz
Files: 
 a3d9d519964cedb2da52d9a9f0d4c2f6 2022 javascript optional 
node-xmldom_0.8.6-1.dsc
 226ddb5b83975654597c1828c46bca8c 318742 javascript optional 
node-xmldom_0.8.6.orig.tar.gz
 baa7d17dee01da19f60e2a05104a0461 3512 javascript optional 
node-xmldom_0.8.6-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmN/JbkACgkQ9tdMp8mZ
7uncFRAAjgvzISBlQZSQqIlCtHRqDKSzADsuJquZrcU1oCEXw+CneFBvDQ+ot87t
zyq7FuabhMk4LO2ftQ3P42Wiwo+Njh0L6PDLWEYDZlA6UNs46wQTK6vRNgLmef6Y
SCbqWqBKDq7HKToXvCj/mYq+3WN9s/l1T3kXU4jBSq25ORQwl4EwbkrKjiqOv9zC
GmpunZ7bPM/9VlqVt3f0/T7/k5yny5zPDgzW9fPZv3vhv/aCy5csBxnF+xhwdAxx
Z1o20gToLhJK/VCzmPY+SA2U9qHCN/5lwP/5q3jVZ/A+ZrkikxUgj3V1GKxKmynD

Bug#1023149: marked as done (pandoc FTBFS on i386)

[Debian Bug Tracking System]

Your message dated Thu, 24 Nov 2022 08:37:07 +
with message-id 
and subject line Bug#1023149: fixed in pandoc 2.17.1.1-1.1
has caused the Debian Bug report #1023149,
regarding pandoc FTBFS on i386
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.)


-- 
1023149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023149
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pandoc
Version: 2.17.1.1-1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Debian Haskell Group 


https://buildd.debian.org/status/logs.php?pkg=pandoc=2.17.1.1-1%2Bb3

...
[193 of 214] Compiling Text.Pandoc.Readers.EPUB

src/Text/Pandoc/Readers/EPUB.hs:79:40: error:
• Local identifier ‘FilePath’ used as a type
• In the type signature:
parseSpineElem :: PandocMonad m =>
  FilePath -> (FilePath, MimeType) -> m Pandoc
  In an equation for ‘archiveToEPUB’:
  archiveToEPUB os archive
= do (root, content) <- getManifest archive
 (coverId, meta) <- parseMeta content
 (cover, items) <- parseManifest content coverId
 
where
os'
  = os
  {readerExtensions = enableExtension
Ext_raw_html (readerExtensions os)}
parseSpineElem ::
  PandocMonad m => FilePath -> (FilePath, MimeType) -> m Pandoc
parseSpineElem (normalise -> r) (normalise -> path, mime)
  = do doc <- mimeToReader mime r path
   
mimeToReader ::
  PandocMonad m => MimeType -> FilePath -> FilePath -> m Pandoc

   |
79 | parseSpineElem :: PandocMonad m => FilePath -> (FilePath, MimeType) -> 
m Pandoc
   |

src/Text/Pandoc/Readers/EPUB.hs:84:50: error:
• Local identifier ‘FilePath’ used as a type
• In the type signature:
mimeToReader :: PandocMonad m =>
MimeType -> FilePath -> FilePath -> m Pandoc
  In an equation for ‘archiveToEPUB’:
  archiveToEPUB os archive
= do (root, content) <- getManifest archive
 (coverId, meta) <- parseMeta content
 (cover, items) <- parseManifest content coverId
 
where
os'
  = os
  {readerExtensions = enableExtension
Ext_raw_html (readerExtensions os)}
parseSpineElem ::
  PandocMonad m => FilePath -> (FilePath, MimeType) -> m Pandoc
parseSpineElem (normalise -> r) (normalise -> path, mime)
  = do doc <- mimeToReader mime r path
   
mimeToReader ::
  PandocMonad m => MimeType -> FilePath -> FilePath -> m Pandoc

   |
84 | mimeToReader :: PandocMonad m => MimeType -> FilePath -> FilePath -> m 
Pandoc
   |  
-e: error: debian/hlibrary.setup build --builddir=dist-ghc returned exit code 1
...


The patch below workarounds the issue, which indicates that it might
be a bug in the compiler and not a problem in pandoc?

Short-term it might even be good enough to unblock migration of several
packages to testing.

--- debian/rules.old2022-10-30 17:52:59.643347191 +
+++ debian/rules2022-10-30 17:54:14.347251214 +
@@ -192,6 +192,10 @@
 DEB_SETUP_GHC_CONFIGURE_ARGS += --ghc-options="-optc--param 
-optcggc-min-expand=10 -O0"
 endif
 
+ifneq (,$(filter $(DEB_HOST_ARCH_CPU), i386))
+DEB_SETUP_GHC_CONFIGURE_ARGS += --ghc-options="-O0"
+endif
+
 DEB_SETUP_GHC_CONFIGURE_ARGS += $(if $(filter 
nocheck,$(DEB_BUILD_OPTIONS)),,-ftests)
 
 DEB_INSTALL_DOCS_ALL += README.md
--- End Message ---
--- Begin Message ---
Source: pandoc
Source-Version: 2.17.1.1-1.1
Done: Adrian Bunk 

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

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

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated pandoc package)

(This message was generated automatically at their