Bug#1072935: marked as done (simple-obfs: Consider removing the package)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jun 2024 01:08:35 +
with message-id 
and subject line Bug#1073577: Removed package(s) from unstable
has caused the Debian Bug report #1072935,
regarding simple-obfs: Consider removing the package
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.)


-- 
1072935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072935
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: simple-obfs
Version: 0.0.5-6
Severity: serious
X-Debbugs-CC: r...@debian.org rogershim...@gmail.com
Tags: sid

Hi,

Following the previous communication in March, I am considering to take action
and remove related packages in the ss-libev ecosystem. The first targeted 
package
would be simple-obfs.

I plan to file RM bug to Debian FTP Masters after 7 days (on 2024-06-17). If you
have any questions, please feel free to let me know.

Thanks,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Version: 0.0.5-6+rm

Dear submitter,

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

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

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

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

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

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

Bug#1060535: marked as done (libvma: Please switch Build-Depends to systemd-dev)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jun 2024 01:06:39 +
with message-id 
and subject line Bug#1069150: Removed package(s) from unstable
has caused the Debian Bug report #1060535,
regarding libvma: Please switch Build-Depends to systemd-dev
to be marked as done.

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

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


-- 
1060535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060535
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libvma
Version: 9.2.2-1
Severity: normal
User: pkg-systemd-maintain...@lists.alioth.debian.org
Usertags: systemd-dev

Hi,

your package libvma declares a Build-Depends on systemd and/or udev.

In most cases, this build dependency is added to get the paths that
are defined in udev.pc or systemd.pc (via pkgconfig).

Since systemd_253-2 [1], these two pkgconfig files have been split
into a separate package named systemd-dev. This package is arch:all,
so even available on non-Linux architectures, which will simplify the
installation of upstream provided service files / udev rules.

To not make existing source packages FTBFS, the systemd and udev
package have a Depends: systemd-dev. This dependency will be removed
at some point though before trixie is released. Once this happens,
this issue will be bumped to RC.

Please update your build dependencies accordingly at your earliest
convenience.

If all you need is the systemd.pc or udev.pc pkgconfig file, please
replace any systemd or udev Build-Depends with systemd-dev. In most
cases that should be sufficient. If your package needs further
resources from systemd or udev to build successfully, it's fine to
keep those Build-Depends in addition to systemd-dev.

To ease stable backports, a version of systemd with those changes is
provided via bookworm-backports.

In case you have further questions, please contact the systemd team
at .

On behalf of the systemd team, Michael

[1]
https://salsa.debian.org/systemd-team/systemd/-/merge_requests/196 
--- End Message ---
--- Begin Message ---
Version: 9.2.2-1+rm

Dear submitter,

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

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

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

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

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

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

Bug#1021852: marked as done (libvma FTBFS: error: ISO C++17 does not allow ‘register’ storage class specifier)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jun 2024 01:06:39 +
with message-id 
and subject line Bug#1069150: Removed package(s) from unstable
has caused the Debian Bug report #1021852,
regarding libvma FTBFS: error: ISO C++17 does not allow ‘register’ storage 
class specifier
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=libvma=amd64=9.2.2-1%2Bb2=1665870043=0

...
In file included from ../../../../src/utils/asm.h:42,
 from ../../../../src/utils/rdtsc.h:41,
 from ../../../../src/vlogger/vlogger.h:49,
 from ../../../../src/vlogger/main.cpp:36:
../../../../src/utils/asm-x86.h: In function ‘void gettimeoftsc(long long 
unsigned int*)’:
../../../../src/utils/asm-x86.h:113:27: error: ISO C++17 does not allow 
‘register’ storage class specifier [-Werror=register]
  113 | register uint32_t upper_32, lower_32;
  |   ^~~~
../../../../src/utils/asm-x86.h:113:37: error: ISO C++17 does not allow 
‘register’ storage class specifier [-Werror=register]
  113 | register uint32_t upper_32, lower_32;
  | ^~~~
cc1plus: all warnings being treated as errors
In file included from ../../../../src/utils/asm.h:42,
 from ../../../../src/utils/rdtsc.h:41,
 from ../../../../src/vlogger/vlogger.h:49,
 from ../../../../src/vlogger/vlogger.cpp:34:
../../../../src/utils/asm-x86.h: In function ‘void gettimeoftsc(long long 
unsigned int*)’:
../../../../src/utils/asm-x86.h:113:27: error: ISO C++17 does not allow 
‘register’ storage class specifier [-Werror=register]
  113 | register uint32_t upper_32, lower_32;
  |   ^~~~
../../../../src/utils/asm-x86.h:113:37: error: ISO C++17 does not allow 
‘register’ storage class specifier [-Werror=register]
  113 | register uint32_t upper_32, lower_32;
  | ^~~~
make[5]: *** [Makefile:451: main.o] Error 1
make[5]: *** Waiting for unfinished jobs
In file included from ../../../../src/vma/proto/mem_buf_desc.h:39,
 from ../../../../src/vma/util/utils.h:47,
 from ../../../../src/vlogger/vlogger.cpp:46:
../../../../src/vma/util/vma_list.h: At global scope:
../../../../src/vma/util/vma_list.h:90:37: error: ‘template struct 
std::iterator’ is deprecated [-Werror=deprecated-declarations]
   90 | class list_iterator_t : public 
std::iterator
  | ^~~~
In file included from /usr/include/c++/12/string:45,
 from /usr/include/c++/12/bits/locale_classes.h:40,
 from /usr/include/c++/12/bits/ios_base.h:41,
 from /usr/include/c++/12/ios:42,
 from /usr/include/c++/12/ostream:38,
 from /usr/include/c++/12/iostream:39,
 from ../../../../src/vlogger/vlogger.h:41:
/usr/include/c++/12/bits/stl_iterator_base_types.h:127:34: note: declared here
  127 | struct _GLIBCXX17_DEPRECATED iterator
  |  ^~~~
cc1plus: all warnings being treated as errors
make[5]: *** [Makefile:467: vlogger.lo] Error 1
--- End Message ---
--- Begin Message ---
Version: 9.2.2-1+rm

Dear submitter,

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

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

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

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

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

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

Processed: your mail

[Debian Bug Tracking System]

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

> fixed 1072555 elpa-rust-mode/1.0.5+git20240520.d00d83d-1
Bug #1072555 {Done: Xiyue Deng } [elpa-rust-mode] 
elpa-rust-mode: This is an obsolete snapshot of the packaging
Marked as fixed in versions elpa-rust-mode/1.0.5+git20240520.d00d83d-1.
> fixed 1072555 1.0.5+git20240520.d00d83d-1
Bug #1072555 {Done: Xiyue Deng } [elpa-rust-mode] 
elpa-rust-mode: This is an obsolete snapshot of the packaging
Ignoring request to alter fixed versions of bug #1072555 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> fixed 1072555 elpa-rust-mode/1.0.5+git20240301.6d86af4-1
Bug #1072555 {Done: Xiyue Deng } [elpa-rust-mode] 
elpa-rust-mode: This is an obsolete snapshot of the packaging
Marked as fixed in versions elpa-rust-mode/1.0.5+git20240301.6d86af4-1.
> thanks
Stopping processing here.

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

Processed: Bug#1066799 marked as pending in dask.distributed

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1066799 [src:dask.distributed] dask.distributed: FTBFS: E 
  RuntimeError: gen_test only works for coroutine functions.
Added tag(s) pending.

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

Bug#1066799: marked as pending in dask.distributed

[Étienne Mollier]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/dask.distributed/-/commit/38fadb351c94867a038b4fba15fde250fe012eea


d/rules: apply d/default-local.patch only during tests.

Closes: #1066799


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1066799

Bug#1068782: Bug#1071322: News on those issues?

[Jeremy T. Bouse]

Upstream had been MIA for years; its last release was in 2010. It appears
he has finally returned, but I haven't had time to deal with the new
version that was released two weeks ago.

On Mon, Jun 17, 2024 at 4:09 PM Salvatore Bonaccorso 
wrote:

> Hi Jeremy,
>
> Any news on #1068782 and #1071322?  There are a couple of reverse
> dependencies as well scheduled for autoremoval if libesmtp is removed.
>
> Regards,
> Salvatore
>


-- 

Jeremy T. Bouse

Sr. DevOps Engineer

321.525.3280

UnderGrid.net 

Bug#1073560: Reverting "xshared: Print protocol numbers if --numeric was given" breaks firewalld autopkgtest

[Jeremy Sowden]

On 2024-06-17, at 15:57:05 +0200, Michael Biebl wrote:
> Source: iptables
> Version: 1.8.10-4
> Severity: serious
> 
> 
> The cherry-pick of the commit 34f085b1607364f4eaded1140060dcaf965a2649
> Revert "xshared: Print protocol numbers if --numeric was given" breaks
> firewalld, as seen in
> https://ci.debian.net/packages/f/firewalld/testing/amd64/47810213/
> 
> firewalld is very susceptible to changes of the output and command
> line interface of iptables.  See an older issue
> https://github.com/firewalld/firewalld/issues/1112
> 
> Filing with RC severity, so the package doesn't migrate to testing
> (the debci results should prevent that, but this is just to make
> doubly sure)
> 
> This change of iptables afaics has landed in a stable release
> (bookworm). Do we really want to revert it again and make all users of
> --numeric have to update again?

Hi.  Let me explain my understanding of the current situation.  I appre-
ciate that you probably know most of this already, but I just want to
avoid any confusion.

Upstream made a change that affected the output of protocols in listings
in the presence of the `--numeric` flag.  Previously, they were still
output by name, after the change they were output by number.  This was
released upstream in 1.8.9 and made its way into Bookworm.

This change broke stuff.  As a result of a bug-report:

https://bugzilla.netfilter.org/show_bug.cgi?id=1729

upstream reverted the change in commit 34f085b16073 ("Revert "xshared:
Print protocol numbers if --numeric was given"").  This is where things
currently stand upstream: in the next release (1.8.11), the original
behaviour will be restored.

A report was also created in the BTS:

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

In response, I applied the upstream commit and uploaded it to unstable.
I have a draft bookworm-pu bug-report that I had intended to send
requesting that this change go into Bookworm to minimize the time before
the old behaviour is restored.  Obviously, I will hold off while we
discuss this. :)

What do you propose?  The firewalld test-suite was updated to work with
the new output; however, other tools were not, and upstream reverted the
change because there were no compelling reasons for it and it had caused
breakage in those tools.  As things stand, the old behaviour will be re-
stored.  Would you rather wait for the next upstream release?  Are you
suggesting that we ask upstream to revert 34f085b16073?  Or do you have
something else in mind?

J.

> -- System Information:
> Debian Release: trixie/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 6.8.12-amd64 (SMP w/16 CPU threads; PREEMPT)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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

Processed: Bug#1073046: FTBFS with huge file limit due to testsuite timeouts

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1073046 {Done: Thorsten Alteholz } [src:cups] cups: 
FTBFS on riscv64 due to testsuite timeouts
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions cups/2.4.7-3.
> retitle -1 FTBFS with huge file number limit due to testsuite timeouts
Bug #1073046 [src:cups] cups: FTBFS on riscv64 due to testsuite timeouts
Changed Bug title to 'FTBFS with huge file number limit due to testsuite 
timeouts' from 'cups: FTBFS on riscv64 due to testsuite timeouts'.
> found -1 2.4.7-3
Bug #1073046 [src:cups] FTBFS with huge file number limit due to testsuite 
timeouts
Marked as found in versions cups/2.4.7-3.
> severity -1 important
Bug #1073046 [src:cups] FTBFS with huge file number limit due to testsuite 
timeouts
Severity set to 'important' from 'serious'

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

Bug#1073046: FTBFS with huge file limit due to testsuite timeouts

[Aurelien Jarno]

control: reopen -1
control: retitle -1 FTBFS with huge file number limit due to testsuite timeouts
control: found -1 2.4.7-3
control: severity -1 important

Hi,

On 2024-06-16 00:19, Debian FTP Masters wrote:
>  cups (2.4.7-3) unstable; urgency=medium
>  .
>[ Helge Kreutzmann ]
>* Update German man page (2220t)
>  .
>[ Thorsten Alteholz ]
>* reintroduce time_t changes that were accidentally deleted
>  with last upload
>  (thanks to Michael Hudson-Doyle for this work)
>* debian/rules: no test on riscv64 (Closes: #1073046)

Thanks for fixing this bug promptly. However it only papers over the
real issue, which is not riscv64 specific. riscv64 build daemons run a
mix of testing and sid, and are thus affected by some recent changes in
systemd.

More precisely, systemd 256~rc3-3 bumped the maximum number of open
files hard limit from 1048576 to 1073741816 [1]. This value seems to be
used for the maxevents argument of an epoll_pwait syscall, which now
fails:

| epoll_pwait(3, NULL, 1073741816, 1000, NULL, 8) = -1 EINVAL (Invalid argument)

Note that the second argument is NULL, as the call to calloc() to
allocate the events buffer for 1073741816 events failed and returned
NULL.

This leads to the corresponding error message in the log file:

| X [17/Jun/2024:18:35:01.401971 +] cupsdDoSelect() failed - Bad address!

The issue is reproducible on an up to date testing system, which has
been rebooted since the upgrade to systemd 256. Reducing that limit with
ulimit workarounds the issue.

Regards
Aurelien

[1] 
https://salsa.debian.org/systemd-team/systemd/-/commit/99066f931bb49b43e7282fc1fe8488373bfb81e5

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://aurel32.net

Bug#1068782: News on those issues?

[Salvatore Bonaccorso]

Hi Jeremy,

Any news on #1068782 and #1071322?  There are a couple of reverse
dependencies as well scheduled for autoremoval if libesmtp is removed.

Regards,
Salvatore

Bug#1066632: marked as done (djbdns: FTBFS: hier.c:10:3: error: implicit declaration of function ‘h’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Mon, 17 Jun 2024 19:49:09 +
with message-id 
and subject line Bug#1066632: fixed in djbdns 1:1.05-15.1
has caused the Debian Bug report #1066632,
regarding djbdns: FTBFS: hier.c:10:3: error: implicit declaration of function 
‘h’ [-Werror=implicit-function-declaration]
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.)


-- 
1066632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066632
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: djbdns
Version: 1:1.05-15
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

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

This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> ( cat warn-auto.sh; \
> echo 'main="$1"; shift'; \
> echo exec "`head -1 conf-ld`" \
> '-o "$main" "$main".o ${1+"$@"}' \
> ) > load
> ( cat warn-auto.sh; \
> echo exec "`head -1 conf-cc`" '-c ${1+"$@"}' \
> ) > compile
> ( cat warn-auto.sh; \
> echo CC=\'`head -1 conf-cc`\'; \
> echo LD=\'`head -1 conf-ld`\'; \
> cat find-systype.sh; \
> ) | sh > systype
> cat warn-auto.sh choose.sh \
> | sed s}HOME}"`head -1 conf-home`"}g \
> > choose
> chmod 755 load
> chmod 755 compile
> chmod 755 choose
> cat warn-auto.sh dnstracesort.sh \
> | sed s}HOME}"`head -1 conf-home`"}g \
> > dnstracesort
> ./compile utime.c
> cat warn-auto.sh rts.sh \
> | sed s}HOME}"`head -1 conf-home`"}g \
> > rts
> ./compile install.c
> ./compile hier.c
> ./compile instcheck.c
> chmod 755 dnstracesort
> ( ( ./compile tryulong32.c && ./load tryulong32 && \
> ./tryulong32 ) >/dev/null 2>&1 \
> && cat uint32.h2 || cat uint32.h1 ) > uint32.h
> ./choose clr tryulong64 uint64.h1 uint64.h2 > uint64.h
> chmod 755 rts
> ./compile generic-conf.c
> hier.c: In function ‘hier’:
> hier.c:10:3: error: implicit declaration of function ‘h’ 
> [-Werror=implicit-function-declaration]
>10 |   h(auto_home,-1,-1,02755);
>   |   ^
> hier.c:11:3: error: implicit declaration of function ‘d’ 
> [-Werror=implicit-function-declaration]
>11 |   d(auto_home,"bin",-1,-1,02755);
>   |   ^
> hier.c:13:3: error: implicit declaration of function ‘c’ 
> [-Werror=implicit-function-declaration]
>13 |   c(auto_home,"bin","dnscache-conf",-1,-1,0755);
>   |   ^
> utime.c: In function ‘main’:
> utime.c:22:7: error: implicit declaration of function ‘utime’; did you mean 
> ‘utimes’? [-Werror=implicit-function-declaration]
>22 |   if (utime(fn,ut) == -1) _exit(111);
>   |   ^
>   |   utimes
> cc1: some warnings being treated as errors
> rm -f tryulong32.o tryulong32
> ./compile auto-str.c
> make[1]: *** [Makefile:1084: utime.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/djbdns_1.05-15_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=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 mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

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

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

Debian distribution maintenance software
pp.
Chris Hofstaedtler  (supplier of updated djbdns 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 

Processed: gdcm FTBFS with VTK 9.3.0

[Debian Bug Tracking System]

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

> tags 1072822 + patch
Bug #1072822 [src:gdcm] gdcm FTBFS with VTK 9.3.0
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#1072822: Patch available

[Adrien Nader]

Hi,

I've prepared a fixed version in Ubuntu and Graham uploaded it. There is
another issue than this SPDX one.

I'm attaching the patch and won't paraphrase it.

-- 
Adrien
diff --git a/debian/changelog b/debian/changelog
index d155039..da50cb1 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,13 @@
+gdcm (3.0.24-1ubuntu1) oracular; urgency=medium
+
+  * VTK 9.3 compatibility (LP: #2069612):
+- d/p/vtk-9.3-compat.patch
+- d/p/cmake-include-gnuinstalldirs.patch: include(GNUInstallDirs) in
+  order to define CMAKE_INSTALLDIR_INCLUDE
+- install usr/include/vtkgdcmpython.h
+
+ -- Adrien Nader   Fri, 14 Jun 2024 17:04:24 +0200
+
 gdcm (3.0.24-1build1) oracular; urgency=medium
 
   * Rebuild against new libvtk9.3.
diff --git a/debian/control b/debian/control
index 648e47f..56a43dc 100644
--- a/debian/control
+++ b/debian/control
@@ -1,5 +1,6 @@
 Source: gdcm
-Maintainer: Debian Med Packaging Team 
+Maintainer: Ubuntu Developers 
+XSBC-Original-Maintainer: Debian Med Packaging Team 
 Uploaders: Steve M. Robbins ,
Sébastien Jodogne ,
Gert Wollny 
diff --git a/debian/control.in b/debian/control.in
index 5f7b1f0..77a795d 100644
--- a/debian/control.in
+++ b/debian/control.in
@@ -1,5 +1,6 @@
 Source: gdcm
-Maintainer: Debian Med Packaging Team 
+Maintainer: Ubuntu Developers 
+XSBC-Original-Maintainer: Debian Med Packaging Team 
 Uploaders: Steve M. Robbins ,
Sébastien Jodogne ,
Gert Wollny 
diff --git a/debian/patches/cmake-include-gnuinstalldirs.patch b/debian/patches/cmake-include-gnuinstalldirs.patch
new file mode 100644
index 000..2163cb0
--- /dev/null
+++ b/debian/patches/cmake-include-gnuinstalldirs.patch
@@ -0,0 +1,19 @@
+Subject: Use default "GNU" installation directories
+Author: Adrien Nader
+Forwarded: https://sourceforge.net/p/gdcm/bugs/563/
+Last-Update: 2024-06-14
+Applied-Upstream: no
+
+diff --git a/CMakeLists.txt b/CMakeLists.txt
+index 38c65d11..d0d77d7d 100644
+--- a/CMakeLists.txt
 b/CMakeLists.txt
+@@ -187,6 +187,8 @@ macro(CHECK_INCLUDE_FILE_CONCAT FILE VARIABLE)
+   endif()
+ endmacro()
+ 
++include(GNUInstallDirs)
++
+ #include(${GDCM_SOURCE_DIR}/CMake/gdcmPlatformCxxTests.cmake)
+ #
+ #GDCM_PLATFORM_CXX_TEST(GDCM_CXX_HAS_FUNCTION
diff --git a/debian/patches/series b/debian/patches/series
index 20a1fa9..66ebc2a 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -3,3 +3,5 @@ rename-pdf.patch
 03_linkvtkdoc.patch
 04_multiarch.patch
 dircos_rev.patch
+vtk-9.3-compat.patch
+cmake-include-gnuinstalldirs.patch
diff --git a/debian/patches/vtk-9.3-compat.patch b/debian/patches/vtk-9.3-compat.patch
new file mode 100644
index 000..a5cc411
--- /dev/null
+++ b/debian/patches/vtk-9.3-compat.patch
@@ -0,0 +1,96 @@
+Subject: Compatibility with VTK 9.3
+Author: Nicklas Larsson
+Forwarded: https://sourceforge.net/p/gdcm/bugs/552/#9e8f
+Applied-Upstream: no
+Last-Update: 2023-12-05
+Bug: https://sourceforge.net/p/gdcm/bugs/552/
+
+--- gdcm.orig/CMakeLists.txt.orig
 gdcm/CMakeLists.txt
+@@ -698,6 +698,7 @@
+ HEADERS_DESTINATION   "${GDCM_INSTALL_INCLUDE_DIR}/vtk${vtk_version_suffix}"
+ CMAKE_DESTINATION "${GDCM_INSTALL_PACKAGE_DIR}"
+ LICENSE_DESTINATION   "${GDCM_INSTALL_DATA_DIR}/vtkgdcm-${GDCM_SHORT_VERSION}"
++SPDX_DESTINATION  "${GDCM_INSTALL_DATA_DIR}/vtkgdcm-${GDCM_SHORT_VERSION}"
+ HIERARCHY_DESTINATION "${GDCM_INSTALL_LIB_DIR}/vtk${vtk_version_suffix}/hierarchy/vtkgdcm"
+ LIBRARY_NAME_SUFFIX   "${vtkgdcm_library_suffix}"
+ VERSION   "${GDCM_VERSION}"
+
+
+--- gdcm.orig/Utilities/VTK/vtkImageColorViewer.h.orig
 gdcm/Utilities/VTK/vtkImageColorViewer.h
+@@ -199,22 +199,6 @@
+   virtual int GetOffScreenRendering();
+   vtkBooleanMacro(OffScreenRendering,int);
+
+-  // Description:
+-  // @deprecated Replaced by vtkImageColorViewer::GetSliceMin() as of VTK 5.0.
+-  VTK_LEGACY(int GetWholeZMin());
+-
+-  // Description:
+-  // @deprecated Replaced by vtkImageColorViewer::GetSliceMax() as of VTK 5.0.
+-  VTK_LEGACY(int GetWholeZMax());
+-
+-  // Description:
+-  // @deprecated Replaced by vtkImageColorViewer::GetSlice() as of VTK 5.0.
+-  VTK_LEGACY(int GetZSlice());
+-
+-  // Description:
+-  // @deprecated Replaced by vtkImageColorViewer::SetSlice() as of VTK 5.0.
+-  VTK_LEGACY(void SetZSlice(int));
+-
+ protected:
+   vtkImageColorViewer();
+   ~vtkImageColorViewer();
+
+
+
+--- gdcm.orig/Utilities/VTK/vtkImageColorViewer.cxx.orig
 gdcm/Utilities/VTK/vtkImageColorViewer.cxx
+@@ -919,34 +919,6 @@
+ }
+
+ //
+-#ifndef VTK_LEGACY_REMOVE
+-int vtkImageColorViewer::GetWholeZMin()
+-{
+-  VTK_LEGACY_REPLACED_BODY(vtkImageColorViewer::GetWholeZMin, "VTK 5.0",
+-   vtkImageColorViewer::GetSliceMin);
+-  return this->GetSliceMin();
+-}
+-int vtkImageColorViewer::GetWholeZMax()
+-{
+-  

Bug#1073311: marked as done (pd-flext: FTBFS: m_pd.h:575:52: error: static assertion failed: field must be t_float!)

[Debian Bug Tracking System]

Your message dated Mon, 17 Jun 2024 19:08:58 +
with message-id 
and subject line Bug#1073311: fixed in pd-flext 0.6.3-2
has caused the Debian Bug report #1073311,
regarding pd-flext: FTBFS: m_pd.h:575:52: error: static assertion failed: field 
must be t_float!
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.)


-- 
1073311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073311
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-flext
Version: 0.6.3-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> /bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DPACKAGE_NAME=\"flext\" 
> -DPACKAGE_TARNAME=\"flext\" -DPACKAGE_VERSION=\"0.6.3\" 
> -DPACKAGE_STRING=\"flext\ 0.6.3\" -DPACKAGE_BUGREPORT=\"g...@g.org\" 
> -DPACKAGE_URL=\"\" -DPACKAGE=\"flext\" -DVERSION=\"0.6.3\" -DHAVE_STDIO_H=1 
> -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
> -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 
> -DSTDC_HEADERS=1 -DFLEXT_SYS=2 -DPD_FLOATSIZE=64 -DHAVE_DLFCN_H=1 
> -DLT_OBJDIR=\".libs/\" -DFLEXT_USE_CMEM=1 -I. -I../../../../source   
> -Wdate-time -D_FORTIFY_SOURCE=2  -fPIC -O3 -static -I/usr/include/pd 
> -I/usr/include/stk -I/usr/include/SndObj -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection  -c 
> -o libflext_pd64_s_la-flattr_ed.lo `test -f 'flattr_ed.cpp' || echo 
> '../../../../source/'`flattr_ed.cpp
> libtool: compile:  g++ -DPACKAGE_NAME=\"flext\" -DPACKAGE_TARNAME=\"flext\" 
> -DPACKAGE_VERSION=\"0.6.3\" "-DPACKAGE_STRING=\"flext 0.6.3\"" 
> -DPACKAGE_BUGREPORT=\"g...@g.org\" -DPACKAGE_URL=\"\" -DPACKAGE=\"flext\" 
> -DVERSION=\"0.6.3\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
> -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 
> -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 -DFLEXT_SYS=2 
> -DPD_FLOATSIZE=64 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DFLEXT_USE_CMEM=1 
> -I. -I../../../../source -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -O3 
> -I/usr/include/pd -I/usr/include/stk -I/usr/include/SndObj -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c 
> ../../../../source/fldsp.cpp -o libflext_pd64_s_la-fldsp.o
> libtool: compile:  g++ -DPACKAGE_NAME=\"flext\" -DPACKAGE_TARNAME=\"flext\" 
> -DPACKAGE_VERSION=\"0.6.3\" "-DPACKAGE_STRING=\"flext 0.6.3\"" 
> -DPACKAGE_BUGREPORT=\"g...@g.org\" -DPACKAGE_URL=\"\" -DPACKAGE=\"flext\" 
> -DVERSION=\"0.6.3\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
> -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 
> -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 -DFLEXT_SYS=2 
> -DPD_FLOATSIZE=64 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DFLEXT_USE_CMEM=1 
> -I. -I../../../../source -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -O3 
> -I/usr/include/pd -I/usr/include/stk -I/usr/include/SndObj -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c 
> ../../../../source/flbase.cpp -o libflext_pd64_s_la-flbase.o
> libtool: compile:  g++ -DPACKAGE_NAME=\"flext\" -DPACKAGE_TARNAME=\"flext\" 
> -DPACKAGE_VERSION=\"0.6.3\" "-DPACKAGE_STRING=\"flext 0.6.3\"" 
> -DPACKAGE_BUGREPORT=\"g...@g.org\" -DPACKAGE_URL=\"\" -DPACKAGE=\"flext\" 
> -DVERSION=\"0.6.3\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
> -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 
> -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 -DFLEXT_SYS=2 
> -DPD_FLOATSIZE=64 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DFLEXT_USE_CMEM=1 
> -I. -I../../../../source -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -O3 
> -I/usr/include/pd -I/usr/include/stk -I/usr/include/SndObj -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c 
> ../../../../source/fllib.cpp -o libflext_pd64_s_la-fllib.o
> libtool: compile:  g++ -DPACKAGE_NAME=\"flext\" -DPACKAGE_TARNAME=\"flext\" 
> -DPACKAGE_VERSION=\"0.6.3\" "-DPACKAGE_STRING=\"flext 0.6.3\"" 
> -DPACKAGE_BUGREPORT=\"g...@g.org\" -DPACKAGE_URL=\"\" -DPACKAGE=\"flext\" 
> -DVERSION=\"0.6.3\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
> 

Processed: Bug#1073311 marked as pending in pd-flext

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1073311 [src:pd-flext] pd-flext: FTBFS: m_pd.h:575:52: error: static 
assertion failed: field must be t_float!
Added tag(s) pending.

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

Bug#1073311: marked as pending in pd-flext

[IOhannes zmölnig]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/multimedia-team/pd/pd-flext/-/commit/8b3a7fe1397027eb074c614af978e02f4f84262f


Add patch to fix FTBFS with Pd64

Closes: #1073311


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1073311

Processed: src:r-cran-vegan: fails to migrate to testing for too long: cause autopkgtest issues

[Debian Bug Tracking System]

Processing control commands:

> close -1 2.6-6.1+dfsg-1
Bug #1073582 [src:r-cran-vegan] src:r-cran-vegan: fails to migrate to testing 
for too long: cause autopkgtest issues
Marked as fixed in versions r-cran-vegan/2.6-6.1+dfsg-1.
Bug #1073582 [src:r-cran-vegan] src:r-cran-vegan: fails to migrate to testing 
for too long: cause autopkgtest issues
Marked Bug as done

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

Bug#1073582: src:r-cran-vegan: fails to migrate to testing for too long: cause autopkgtest issues

[Paul Gevers]

Source: r-cran-vegan
Version: 2.6-4+dfsg-1
Severity: serious
Control: close -1 2.6-6.1+dfsg-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:r-cran-vegan has been trying to migrate 
for 31 days [2]. Hence, I am filing this bug. The version in unstable 
causes issues with autopkgtests from reverse (test) dependencies.


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


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


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


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=r-cran-vegan



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1073033: marked as done (neomutt removes gpg.rc and smime.rc breaking cryptographic functions for users relying on them)

[Debian Bug Tracking System]

Your message dated Mon, 17 Jun 2024 15:35:58 -0300
with message-id 

and subject line Close bug
has caused the Debian Bug report #1073033,
regarding neomutt removes gpg.rc and smime.rc breaking cryptographic functions 
for users relying on them
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.)


-- 
1073033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073033
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: neomutt
Version: 20231103+dfsg1-1+b2
Severity: normal
X-Debbugs-Cc: charlesmel...@riseup.net

Dear Maintainer,

This is a bug to prevent 20240425+dfsg-1 migrating to testing.
20240425+dfsg-2 was uploaded today containing d/NEWS and d/README.Debian
explaining the situation to neomutt users.


-- Package-specific info:
NeoMutt 20231103
Copyright (C) 1996-2022 Michael R. Elkins and others.
NeoMutt comes with ABSOLUTELY NO WARRANTY; for details type 'neomutt -vv'.
NeoMutt is free software, and you are welcome to redistribute it
under certain conditions; type 'neomutt -vv' for details.

System: Linux 6.7.12-amd64 (x86_64)
ncurses: ncurses 6.5.20240427 (compiled with 6.4.20240113)
libidn2: 2.3.7 (compiled with 2.3.7)
GPGME: 1.18.0
GnuTLS: 3.8.3
libnotmuch: 5.6.0
PCRE2: 10.42 2022-12-11
storage: tokyocabinet, lmdb
compression: lz4, zlib, zstd

Configure options: --build=x86_64-linux-gnu --prefix=/usr 
{--includedir=${prefix}/include} {--mandir=${prefix}/share/man} 
{--infodir=${prefix}/share/info} --sysconfdir=/etc --localstatedir=/var 
--disable-option-checking --disable-silent-rules 
{--libdir=${prefix}/lib/x86_64-linux-gnu} --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking --mandir=/usr/share/man 
--libexecdir=/usr/libexec --with-mailpath=/var/mail --autocrypt --full-doc 
--gnutls --gpgme --gsasl --gss --lmdb --lua --lz4 --notmuch --mixmaster --pcre2 
--sqlite --tokyocabinet --zlib --zstd

Compilation CFLAGS: -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/build/reproducible-path/neomutt-20231103+dfsg1=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -fno-delete-null-pointer-checks 
-D_ALL_SOURCE=1 -D_GNU_SOURCE=1 -D__EXTENSIONS__ -D_XOPEN_SOURCE_EXTENDED 
-I/usr/include/lua5.4 -I/usr/include -I/usr/include -I/usr/include 
-DNCURSES_WIDECHAR -I/usr/include -I/usr/include/p11-kit-1 -I/usr/include 
-isystem /usr/include/mit-krb5 -O2

Default options:
  +attach_headers_color +compose_to_sender +compress +cond_date +debug 
  +encrypt_to_self +forgotten_attachments +forwref +ifdef +imap +index_color 
  +initials +limit_current_thread +multiple_fcc +nested_if +new_mail +nntp +pop 
  +progress +quasi_delete +regcomp +reply_with_xorig +sensible_browser +sidebar 
  +skip_quoted +smtp +status_color +timeout +tls_sni +trash 

Compile options:
  +autocrypt +fcntl -flock -fmemopen +futimens +getaddrinfo +gnutls +gpgme 
  +gsasl +gss +hcache -homespool +idn +inotify -locales_hack +lua +mixmaster 
  +nls +notmuch -openssl +pcre2 +pgp -sasl +smime +sqlite +sun_attachment 
  +truecolor 

MAILPATH="/var/mail"
MIXMASTER="mixmaster"
PKGDATADIR="/usr/share/neomutt"
SENDMAIL="/usr/sbin/sendmail"
SYSCONFDIR="/etc"

To learn more about NeoMutt, visit: https://neomutt.org
If you find a bug in NeoMutt, please raise an issue at:
https://github.com/neomutt/neomutt/issues
or send an email to: 

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

Kernel: Linux 6.7.12-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.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

Versions of packages neomutt depends on:
ii  libc62.38-12
ii  libgnutls30t64   3.8.5-4
ii  libgpgme11t641.18.0-4.1+b1
ii  libgsasl18   2.2.1-1+b1
ii  libgssapi-krb5-2 1.20.1-6+b1
ii  libidn2-02.3.7-2
ii  liblmdb0 0.9.31-1+b1
ii  liblua5.4-0  5.4.6-3+b1
ii  liblz4-1 1.9.4-2
ii  libncursesw6 6.5-2
ii  libnotmuch5t64   0.38.3-1+b1
ii  libpcre2-8-0 10.42-4+b1
ii  libsqlite3-0 3.46.0-1
ii  libtinfo66.5-2
ii  libtokyocabinet9t64  1.4.48-15.1
ii  libzstd1 1.5.5+dfsg2-2
ii  sensible-utils   0.0.22
ii  zlib1g   1:1.3.dfsg+really1.3.1-1

Versions of packages neomutt recommends:
ii  locales  2.38-12
ii  mailcap  3.72

Versions of packages neomutt 

Bug#1034995: marked as done (python-is-python3: missing Breaks+Replaces for python-dev-is-python2 when upgrading from bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 17 Jun 2024 18:02:10 +
with message-id 
and subject line Bug#1034995: fixed in what-is-python 13+deb12u1
has caused the Debian Bug report #1034995,
regarding python-is-python3: missing Breaks+Replaces for python-dev-is-python2 
when upgrading from bullseye
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.)


-- 
1034995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034995
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-is-python3
Version: 3.11.1-3
Severity: serious
Justification: dpkg unpack error

Attempting to unpack python-is-python3/3.11.1-3 from Debian bookworm
on a minimal Debian bullseye with python-dev-is-python2/2.7.18-9
installed, causes an unpack error from dpkg due to
/usr/bin/pydoc being contained in both packages.

| Selecting previously unselected package python-is-python3.
| dpkg: considering deconfiguration of python-is-python2, which would be broken 
by installation of python-is-python3 ...
| dpkg: yes, will deconfigure python-is-python2 (broken by python-is-python3)
| (Reading database ... 9300 files and directories currently installed.)
| Preparing to unpack .../python-is-python3_3.11.1-3_all.deb ...
| De-configuring python-is-python2 (2.7.18-9) ...
| Unpacking python-is-python3 (3.11.1-3) ...
| dpkg: error processing archive ./python-is-python3_3.11.1-3_all.deb 
(--unpack):
|  trying to overwrite '/usr/bin/pydoc', which is also in package 
python-dev-is-python2 2.7.18-9
| Errors were encountered while processing:
|  ./python-is-python3_3.11.1-3_all.deb


Please ensure that python-is-python3 has sufficient Breaks and Replaces 
declarations.

Helmut
--- End Message ---
--- Begin Message ---
Source: what-is-python
Source-Version: 13+deb12u1
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated what-is-python package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 17 Jun 2024 15:36:12 +0200
Source: what-is-python
Architecture: source
Version: 13+deb12u1
Distribution: bookworm
Urgency: medium
Maintainer: Matthias Klose  
Changed-By: Andreas Beckmann 
Closes: 1034995
Changes:
 what-is-python (13+deb12u1) bookworm; urgency=medium
 .
   [ Andreas Beckmann ]
   * Non-maintainer upload.
   * Bump version to 3.11.2.
   * Fix version mangling for NMU, stable or backports uploads, i.e. versions
 with a suffix starting with a non-digit ([.+~]).
 .
   [ Matthias Klose ]
   * python-is-python3: Add breaks/replaces to python-dev-is-python2.
 Closes: #1034995.
Checksums-Sha1:
 732a61934fe4e5431f223a076dec49203a7573de 1609 what-is-python_13+deb12u1.dsc
 ad5e1819b25641125e2bc73f36f5f043d150f619 2744 what-is-python_13+deb12u1.tar.xz
 39aa7766edc3d3459fb2b6c86ae21c50e76d1420 5758 
what-is-python_13+deb12u1_source.buildinfo
Checksums-Sha256:
 cef7d920f248b3d524e768f6f65352aaf34dbec8f5e461339b77cd3fdcf5998b 1609 
what-is-python_13+deb12u1.dsc
 4abd2b1c0015995a9ae8f310b10a1699c80eccc4196b807eeffa405786878d66 2744 
what-is-python_13+deb12u1.tar.xz
 1a03ffa5786968f93c96e073dd260aba6c60103bcf19db231cb2a70456a96acc 5758 
what-is-python_13+deb12u1_source.buildinfo
Files:
 87076ff0cb51505146c214c8cf1aad78 1609 python optional 
what-is-python_13+deb12u1.dsc
 a8dfb23450c898a1b00ee96aa843344a 2744 python optional 
what-is-python_13+deb12u1.tar.xz
 8a6251ab2f329eac6899388aa4f95a6e 5758 python optional 
what-is-python_13+deb12u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmZwPA0QHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCPenD/9+M+Ufz5bng6jtcEnhJxl/IvEM3k94FWBE
uwE1CHgNEzHMMZ3tPxpHraDPX4lkGGYHCLtmpe80D2yIypkcWVVaaMOJY9Yc/9ya
yBtLhdCCMpoqLrUhEd1BpwDrew7paRpOv9/TDSwsnZVZ30hDnNdOXGjBULKDIgR9
xUOZdEGGESWZxDJWXGVHUBMhm4nFL6xvsjR5fU05Wpjxhhc67U041zsfg/lbZ1NI
hdf1qmdzPaLue/9RlcZQxd/okv84qc3EniIz0SDHcfUCo9T2yNeSyMMwhueabOXE
bPfl7qNRdxNTGJYPCCPjkK3ACsxtlRru7eQpaI7sFcSE/pahkP1ymJuVNtUOiwLQ

Bug#1040438: marked as done (libmail-dkim-perl: missing dependency on libgetopt-long-descriptive-perl)

[Debian Bug Tracking System]

Your message dated Mon, 17 Jun 2024 18:02:08 +
with message-id 
and subject line Bug#1040438: fixed in libmail-dkim-perl 1.20230212-2~deb12u1
has caused the Debian Bug report #1040438,
regarding libmail-dkim-perl: missing dependency on 
libgetopt-long-descriptive-perl
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.)


-- 
1040438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040438
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmail-dkim-perl
Version: 1.20230212-1
Severity: serious
Justification: Policy 3.5

  $ dkimproxy-verify
  Can't locate Getopt/Long/Descriptive.pm in @INC (you may need to install the 
Getopt::Long::Descriptive module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 
/usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 
/usr/share/perl/5.36 /usr/local/lib/site_perl) at /usr/bin/dkimproxy-verify 
line 13.
  BEGIN failed--compilation aborted at /usr/bin/dkimproxy-verify line 13.

Installing libgetopt-long-descriptive-perl fixes it, but this should
clearly be in Depends.

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

Kernel: Linux 6.1.0-8-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 libmail-dkim-perl depends on:
ii  libcrypt-openssl-rsa-perl   0.33-3+b1
ii  liberror-perl   0.17029-2
ii  libmail-authenticationresults-perl  2.20230112-1
ii  libmailtools-perl   2.21-2
ii  libnet-dns-perl 1.36-1
ii  perl [libdigest-sha-perl]   5.36.0-7

libmail-dkim-perl recommends no packages.

libmail-dkim-perl suggests no packages.

-- no debconf information

Thanks,

-- 
Colin Watson (he/him)  [cjwat...@debian.org]
--- End Message ---
--- Begin Message ---
Source: libmail-dkim-perl
Source-Version: 1.20230212-2~deb12u1
Done: Andreas Beckmann 

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

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

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated libmail-dkim-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 17 Jun 2024 15:18:32 +0200
Source: libmail-dkim-perl
Architecture: source
Version: 1.20230212-2~deb12u1
Distribution: bookworm
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Andreas Beckmann 
Closes: 1040438
Changes:
 libmail-dkim-perl (1.20230212-2~deb12u1) bookworm; urgency=medium
 .
   * Non-maintainer upload.
   * Rebuild for bookworm.
 .
 libmail-dkim-perl (1.20230212-2) unstable; urgency=medium
 .
   * Team upload.
   * Add scripts to autopkgtest's syntax.t. Cf. #1040438.
   * Add a runtime dependency on libgetopt-long-descriptive-perl.
 Thanks to Colin Watson for the bug report. (Closes: #1040438)
Checksums-Sha1:
 5d421e9aa23e8cdd0eb8b2627a2a298d2f2bcb79 2506 
libmail-dkim-perl_1.20230212-2~deb12u1.dsc
 3135af5c5b466df167c32118a6f1beb7d430443c 5748 
libmail-dkim-perl_1.20230212-2~deb12u1.debian.tar.xz
 ff332d5bde76dc2ce3ac3cdbe1988edd5eb97bc1 5813 
libmail-dkim-perl_1.20230212-2~deb12u1_source.buildinfo
Checksums-Sha256:
 f2fb1ee9e6fcb30403f2921f8d196084740cbb63ca6f5766b819489dccef7749 2506 
libmail-dkim-perl_1.20230212-2~deb12u1.dsc
 35a29a0c579896165eb8cd024c3cf9cd9ed03a79a8ecf69d465610a142e46723 5748 
libmail-dkim-perl_1.20230212-2~deb12u1.debian.tar.xz
 03e4d5eead2050c16f77e8a3f74eee9f91c80dce07fac5e0a1fba30ac477b306 5813 
libmail-dkim-perl_1.20230212-2~deb12u1_source.buildinfo
Files:
 52c8380975f471ed9bb618431eb6232e 2506 perl optional 
libmail-dkim-perl_1.20230212-2~deb12u1.dsc
 

Bug#1073362: marked as done (python-zstandard: FTBFS: ImportError: zstd C API versions mismatch; Python bindings were not compiled/linked against expected zstd version (10506 returned by the lib, 1050

[Debian Bug Tracking System]

Your message dated Mon, 17 Jun 2024 17:50:01 +
with message-id 
and subject line Bug#1073362: fixed in python-zstandard 0.22.0+git20240526-1
has caused the Debian Bug report #1073362,
regarding python-zstandard: FTBFS: ImportError: zstd C API versions mismatch; 
Python bindings were not compiled/linked against expected zstd version (10506 
returned by the lib, 10506 hardcoded in zstd headers, 10505 hardcoded in the 
cext)
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.)


-- 
1073362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073362
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-zstandard
Version: 0.22.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cd docs; LC_ALL=C.UTF-8 LANGUAGE=C.UTF-8 sphinx-build -bhtml . _build/html
> Running Sphinx v7.2.6
> making output directory... done
> building [mo]: targets for 0 po files that are out of date
> writing output... 
> building [html]: targets for 15 source files that are out of date
> updating environment: [new config] 15 added, 0 changed, 0 removed
> reading sources... [  7%] api_usage
> reading sources... [ 13%] buffer
> reading sources... [ 20%] compression_parameters
> reading sources... [ 27%] compressor
> reading sources... [ 33%] concepts
> reading sources... [ 40%] contributing
> reading sources... [ 47%] decompressor
> reading sources... [ 53%] dictionaries
> reading sources... [ 60%] index
> reading sources... [ 67%] installing
> reading sources... [ 73%] misc_apis
> reading sources... [ 80%] missing_features
> reading sources... [ 87%] multithreaded
> reading sources... [ 93%] news
> reading sources... [100%] projectinfo
> 
> WARNING: autodoc: failed to import class 'BufferSegment' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'BufferSegments' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'BufferWithSegments' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'BufferWithSegmentsCollection' from 
> module 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdCompressionParameters' from 
> module 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdCompressor' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdCompressionWriter' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdCompressionReader' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdCompressionObj' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdCompressionChunker' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdDecompressor' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdDecompressionWriter' from 
> module 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdDecompressionReader' from 
> module 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdDecompressionObj' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdCompressionDict' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import function 'train_dictionary' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import function 'get_frame_parameters' from 
> module 

Bug#1073335: gettext: FTBFS: locating-rule.c:150:7: error: implicit declaration of function ‘free’ [-Werror=implicit-function-declaration]

[Santiago Vila]

Thanks for the report.

I'm going to see if I can package version 0.22.5, which fixes this and other 
bugs.

The plan B, if it becomes too much complex, is to override with 
DEB_CFLAGS_MAINT_STRIP
and maybe also apply the proposed patch for Java 21 in Bug#1056293, but this 
would be
only to gain some time. I would really like to see 0.22.5 in trixie.

Thanks.

Bug#1073382: marked as done (mutatormath: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Mon, 17 Jun 2024 17:19:08 +
with message-id 
and subject line Bug#1073382: fixed in mutatormath 3.0.1-4
has caused the Debian Bug report #1073382,
regarding mutatormath: FTBFS: dh_auto_test: error: pybuild --test -i 
python{version} -p "3.12 3.11" returned exit code 13
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.)


-- 
1073382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073382
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mutatormath
Version: 3.0.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:311: python3.12 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293: 
> _DeprecatedConfig: Deprecated config in `setup.cfg`
> !!
> 
> 
> 
> The license_file parameter is deprecated, use license_files instead.
> 
> This deprecation is overdue, please update your project and remove 
> deprecated
> calls to avoid build errors in the future.
> 
> See 
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for 
> details.
> 
> 
> 
> !!
>   parsed = self.parsers.get(option_name, lambda x: x)(value)
> running config
> I: pybuild base:311: python3.11 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293: 
> _DeprecatedConfig: Deprecated config in `setup.cfg`
> !!
> 
> 
> 
> The license_file parameter is deprecated, use license_files instead.
> 
> This deprecation is overdue, please update your project and remove 
> deprecated
> calls to avoid build errors in the future.
> 
> See 
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for 
> details.
> 
> 
> 
> !!
>   parsed = self.parsers.get(option_name, lambda x: x)(value)
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:311: /usr/bin/python3.12 setup.py build 
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293: 
> _DeprecatedConfig: Deprecated config in `setup.cfg`
> !!
> 
> 
> 
> The license_file parameter is deprecated, use license_files instead.
> 
> This deprecation is overdue, please update your project and remove 
> deprecated
> calls to avoid build errors in the future.
> 
> See 
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for 
> details.
> 
> 
> 
> !!
>   parsed = self.parsers.get(option_name, lambda x: x)(value)
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.12/build/mutatorMath
> copying Lib/mutatorMath/__init__.py -> 
> /<>/.pybuild/cpython3_3.12/build/mutatorMath
> creating /<>/.pybuild/cpython3_3.12/build/mutatorMath/objects
> copying Lib/mutatorMath/objects/__init__.py -> 
> /<>/.pybuild/cpython3_3.12/build/mutatorMath/objects
> copying Lib/mutatorMath/objects/bender.py -> 
> /<>/.pybuild/cpython3_3.12/build/mutatorMath/objects
> copying Lib/mutatorMath/objects/error.py -> 
> /<>/.pybuild/cpython3_3.12/build/mutatorMath/objects
> copying Lib/mutatorMath/objects/location.py -> 
> /<>/.pybuild/cpython3_3.12/build/mutatorMath/objects
> copying Lib/mutatorMath/objects/mutator.py -> 
> /<>/.pybuild/cpython3_3.12/build/mutatorMath/objects
> creating /<>/.pybuild/cpython3_3.12/build/mutatorMath/ufo
> copying Lib/mutatorMath/ufo/__init__.py -> 
> /<>/.pybuild/cpython3_3.12/build/mutatorMath/ufo
> copying Lib/mutatorMath/ufo/document.py -> 
> /<>/.pybuild/cpython3_3.12/build/mutatorMath/ufo
> copying Lib/mutatorMath/ufo/instance.py -> 
> /<>/.pybuild/cpython3_3.12/build/mutatorMath/ufo
> I: pybuild base:311: /usr/bin/python3 setup.py build 
> 

Bug#1073308: marked as done (pd-pdogg: FTBFS: m_pd.h:85:26: error: static assertion failed: "field must be t_float!")

[Debian Bug Tracking System]

Your message dated Mon, 17 Jun 2024 17:04:53 +
with message-id 
and subject line Bug#1073308: fixed in pd-pdogg 0.25.1-10
has caused the Debian Bug report #1073308,
regarding pd-pdogg: FTBFS: m_pd.h:85:26: error: static assertion failed: "field 
must be t_float!"
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.)


-- 
1073308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073308
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-pdogg
Version: 0.25.1-9
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> cc -DPD -I "/usr/include/pd"  -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC  
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o 
> oggwrite~.pd_linux.o -c oggwrite~.c
> oggcast~.c: In function ‘oggcast_child_connect’:
> oggcast~.c:602:36: warning: format ‘%d’ expects argument of type ‘int’, but 
> argument 3 has type ‘t_int’ {aka ‘long int’} [-Wformat=]
>   602 | if(sprintf(resp, "%d", br_nom) == -1)/* convert 
> int to a string */
>   |   ~^   ~~
>   ||   |
>   |int t_int {aka long int}
>   |   %ld
> oggcast~.c:670:36: warning: format ‘%d’ expects argument of type ‘int’, but 
> argument 3 has type ‘t_int’ {aka ‘long int’} [-Wformat=]
>   670 | if(sprintf(resp, "%d", br_nom) == -1)/* convert 
> int to a string */
>   |   ~^   ~~
>   ||   |
>   |int t_int {aka long int}
>   |   %ld
> oggcast~.c: In function ‘oggcast_child_main’:
> oggcast~.c:845:49: warning: format ‘%d’ expects argument of type ‘int’, but 
> argument 3 has type ‘t_int’ {aka ‘long int’} [-Wformat=]
>   845 | sprintf(boo, "fifosize %d\n", x->x_fifosize);
>   |~^ ~
>   | |  |
>   | intt_int {aka 
> long int}
>   |%ld
> oggcast~.c:891:52: warning: format ‘%d’ expects argument of type ‘int’, but 
> argument 3 has type ‘t_int’ {aka ‘long int’} [-Wformat=]
>   891 | sprintf(boo, "after: head %d, tail %d, pages 
> %d\n", x->x_fifohead, x->x_fifotail, sysrtn);
>   |   ~^  
>   ~
>   ||  
>|
>   |int
>t_int {aka long int}
>   |   %ld
> oggamp~.c: In function ‘oggamp_child_dographics’:
> oggcast~.c:891:61: warning: format ‘%d’ expects argument of type ‘int’, but 
> argument 4 has type ‘t_int’ {aka ‘long int’} [-Wformat=]
>   891 | sprintf(boo, "after: head %d, tail %d, pages 
> %d\n", x->x_fifohead, x->x_fifotail, sysrtn);
>   |~^ 
>  ~
>   | | 
>   |
>   | int   
>   t_int {aka long int}
>   |%ld
> oggamp~.c:637:17: warning: ‘sys_vgui’ is deprecated 
> [-Wdeprecated-declarations]
>   637 | sys_vgui(".x%x.c create rectangle %d %d %d %d -fill 
> lightblue -tags %xPBAR\n",
>   | ^~~~
> In file included from oggamp~.c:33:
> /usr/include/pd/m_pd.h:796:27: note: declared here
>   796 | PD_DEPRECATED EXTERN void sys_vgui(const char *fmt, ...); /* avoid 
> this: use pdgui_vmess() instead */
>   |   ^~~~
> oggamp~.c: In function ‘oggamp_child_updategraphics’:
> oggamp~.c:651:17: warning: ‘sys_vgui’ is deprecated 
> [-Wdeprecated-declarations]

Bug#1073330: marked as done (pd-sigpack: FTBFS: m_pd.h:85:26: error: static assertion failed: "field must be t_float!")

[Debian Bug Tracking System]

Your message dated Mon, 17 Jun 2024 16:51:10 +
with message-id 
and subject line Bug#1073330: fixed in pd-sigpack 0.46.0-2
has caused the Debian Bug report #1073330,
regarding pd-sigpack: FTBFS: m_pd.h:85:26: error: static assertion failed: 
"field must be t_float!"
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.)


-- 
1073330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073330
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-sigpack
Version: 0.46.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> cc -DPD -I "/usr/include/pd" -DPD_FLOATSIZE=64 -DUNIX -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIC  -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -o source/chop~.linux-amd64-64.so.o 
> -c source/chop~.c
>  info: making source/harmgen~.linux-amd64-64.so.o in lib sigpack
> In file included from source/vowel~.c:6:
> source/vowel~.c: In function ‘vowel_tilde_setup’:
> /usr/include/pd/m_pd.h:85:26: error: static assertion failed: "field must be 
> t_float!"
>85 | #define PD_STATIC_ASSERT _Static_assert
>   |  ^~
> /usr/include/pd/m_pd.h:575:5: note: in expansion of macro ‘PD_STATIC_ASSERT’
>   575 | PD_STATIC_ASSERT(sizeof(((type *)NULL)->field) == 
> sizeof(t_float), "field must be t_float!"); \
>   | ^~~~
> source/vowel~.c:144:5: note: in expansion of macro ‘CLASS_MAINSIGNALIN’
>   144 | CLASS_MAINSIGNALIN(vowel_tilde_class, t_vowel_tilde, x_f);
>   | ^~
> In file included from source/split~.c:6:
> source/split~.c: In function ‘split_tilde_setup’:
> /usr/include/pd/m_pd.h:85:26: error: static assertion failed: "field must be 
> t_float!"
>85 | #define PD_STATIC_ASSERT _Static_assert
>   |  ^~
> /usr/include/pd/m_pd.h:575:5: note: in expansion of macro ‘PD_STATIC_ASSERT’
>   575 | PD_STATIC_ASSERT(sizeof(((type *)NULL)->field) == 
> sizeof(t_float), "field must be t_float!"); \
>   | ^~~~
> source/split~.c:70:5: note: in expansion of macro ‘CLASS_MAINSIGNALIN’
>70 | CLASS_MAINSIGNALIN(split_tilde_class, t_split_tilde, x_f);
>   | ^~
> make[1]: *** [/usr/share/pd-lib-builder//Makefile.pdlibbuilder:987: 
> source/vowel~.linux-amd64-64.so.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/06/15/pd-sigpack_0.46.0-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240615;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240615=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 mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: pd-sigpack
Source-Version: 0.46.0-2
Done: IOhannes m zmölnig (Debian/GNU) 

We believe that the bug you reported is fixed in the latest version of
pd-sigpack, 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 1073...@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 
pd-sigpack package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 17 Jun 2024 18:33:42 +0200
Source: pd-sigpack
Architecture: source
Version: 0.46.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: 

Bug#1072847: marked as done (lacme: Post-issuance validation fails in the default configuration)

[Debian Bug Tracking System]

Your message dated Mon, 17 Jun 2024 16:47:34 +
with message-id 
and subject line Bug#1072847: fixed in lacme 0.8.0-2+deb11u2
has caused the Debian Bug report #1072847,
regarding lacme: Post-issuance validation fails in the default configuration
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.)


-- 
1072847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072847
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lacme
Version: 0.8.2-1
Severity: grave
Justification: renders package unusable

Let's Encrypt has recently rotated its intermediate certificates [0].
The previous intermediate certificates (lets-encrypt-r[34].pem and
lets-encrypt-e[12].pem) are concatenated along side the roots
(isrgrootx1.pem and isrg-root-x2.pem) and used as trust anchors for
validation of the issued X.509 certificate before its deployment.

The new intermediates means the validation step now fails.  A quick fix
is to add R1[0-4].pem and E[5-9].pem to the certificate bundle, however
that will cease to work once Let's Encrypt rotates its intermediates
again.

A proper fix would be to use the intermediate(s) provided during the
issuance step as -untrusted (for chain building).

-- 
Guilhem.

[0] https://letsencrypt.org/2024/03/19/new-intermediate-certificates


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: lacme
Source-Version: 0.8.0-2+deb11u2
Done: Guilhem Moulin 

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

Debian distribution maintenance software
pp.
Guilhem Moulin  (supplier of updated lacme 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, 13 Jun 2024 19:19:07 +0200
Source: lacme
Architecture: source
Version: 0.8.0-2+deb11u2
Distribution: bullseye
Urgency: medium
Maintainer: Guilhem Moulin 
Changed-By: Guilhem Moulin 
Closes: 1072847
Changes:
 lacme (0.8.0-2+deb11u2) bullseye; urgency=medium
 .
   * Backport upstream patches to fix post-issuance validation logic.  We avoid
 pinning the intermediate certificates in the bundle and instead validate
 the leaf certificate with intermediates supplied during issuance as
 untrusted (used for chain building only).  Only the root certificates are
 used as trust anchor.
 Not pinning intermediate certificates is in line with Let's Encrypt's
 latest recommendations.
 Closes: #1072847
   * Adjust test suite against current Let's Encrypt staging environment.
Checksums-Sha1:
 0d271783d6a808bc85ce44f7883087b348bad183 1924 lacme_0.8.0-2+deb11u2.dsc
 850c8a5ab446ef6a0a26b1682d27d2041a4d5e49 20848 
lacme_0.8.0-2+deb11u2.debian.tar.xz
 55daa909dc6ea4698a6b5b027e95ff188ec2994e 6546 
lacme_0.8.0-2+deb11u2_amd64.buildinfo
Checksums-Sha256:
 46db26d15c7717c96e26cf10e22df41d8dda6affbf2bcb4eb3bbd2b6ec0b5b44 1924 
lacme_0.8.0-2+deb11u2.dsc
 bb2acb43e92e0cd48712644535cfceb3cbbbc86c412e30f614b9b719d42a1f2c 20848 
lacme_0.8.0-2+deb11u2.debian.tar.xz
 fd63350f932bd59c155ba0590a1ee4b9b2c9d2586ef4710d4e23f8b61eecb150 6546 
lacme_0.8.0-2+deb11u2_amd64.buildinfo
Files:
 d5df633a3c5af23efe9d8448f7cc1ac2 1924 utils optional lacme_0.8.0-2+deb11u2.dsc
 ae2a34e62e9ef21a3e42f5ec7791968d 20848 utils optional 
lacme_0.8.0-2+deb11u2.debian.tar.xz
 3805bc773a9fa600769b9fdacc6af2a7 6546 utils optional 
lacme_0.8.0-2+deb11u2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEERpy6p3b9sfzUdbME05pJnDwhpVIFAmZt608ACgkQ05pJnDwh
pVLh2RAAk7HR8pPXDKJ80pZSYAxT8LeMqmCk741C8re/xinZ5iqLpB9kDH/Wd/Pp
0TODeVlqxV98aaw2FnMs4WaTLy3wL5wKc3FXHsH+J+HFDia56M9ns12gNS66AlFj
+VWm1m91OCMd9cSG/AAkIoGMPZQXx+SY4YAji0e58wERg5WGrbZfG3EZM3mixFyb
12dWL0HfqN2GNXGIGwu5WfW1KonN6o4qdmQKVOGMWP945vhtihmvuID6p9BnKNho
0DivbHSjbzXLOMLvf1sJAgm4WDfRknZfxtYQPQNU3KpIDKmXZE28WSN5/XUmDPZ6
WF6uqjotNGqa7kTQCD+8vqTOWqX+UNLzgBziz++8IBD9dolBQzrkwwkfjB6jaTdW
HYqZH4Vxh9DCoG5xS4jytNwn+LVf1+/FI1XoRNuEh7WZRZcQ0wTx1LulTJW/oVPp
9wpPgxSJxrBpCOcyn4iif4bFzOvv9AnIOIZ0fT/dE+ihKbN/RzZtmKlbsXkVQpcS
TzT50rBmeCqlHRwDW33IduaOaLpxRas1YBwbMxTqrRfj0qjzWO475iGw23yKJUU3

Bug#1072119: marked as done (python-aiosmtpd: CVE-2024-34083)

[Debian Bug Tracking System]

Your message dated Mon, 17 Jun 2024 16:47:35 +
with message-id 
and subject line Bug#1072119: fixed in python-aiosmtpd 1.2.2-1+deb11u1
has caused the Debian Bug report #1072119,
regarding python-aiosmtpd: CVE-2024-34083
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.)


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

Hi,

The following vulnerability was published for python-aiosmtpd.

CVE-2024-34083[0]:
| aiosmptd is  a reimplementation of the Python stdlib smtpd.py based
| on asyncio. Prior to version 1.4.6, servers based on aiosmtpd accept
| extra unencrypted commands after STARTTLS, treating them as if they
| came from inside the encrypted connection. This could be exploited
| by a man-in-the-middle attack. Version 1.4.6 contains a patch for
| the issue.

https://github.com/aio-libs/aiosmtpd/security/advisories/GHSA-wgjv-9j3q-jhg8
https://github.com/aio-libs/aiosmtpd/commit/b3a4a2c6ecfd228856a20d637dc383541fcdbfda
 (v1.4.6)


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

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: python-aiosmtpd
Source-Version: 1.2.2-1+deb11u1
Done: Dale Richards 

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

Debian distribution maintenance software
pp.
Dale Richards  (supplier of updated python-aiosmtpd 
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, 14 Jun 2024 14:09:42 +0100
Source: python-aiosmtpd
Architecture: source
Version: 1.2.2-1+deb11u1
Distribution: bullseye
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Dale Richards 
Closes: 1066820 1072119
Changes:
 python-aiosmtpd (1.2.2-1+deb11u1) bullseye; urgency=medium
 .
   * Team upload.
   * CVE-2024-27305 - SMTP smuggling due to poor handling of
 non-standard line endings (Closes: #1066820)
   * CVE-2024-34083 - STARTTLS unencrypted command injection
 (Closes: #1072119)
Checksums-Sha1:
 d70a03089eb84129c4941773ca9cb76eaa887836 1584 
python-aiosmtpd_1.2.2-1+deb11u1.dsc
 aabe8dbe7e544e4873730780cf2c48b34117d11c 5376 
python-aiosmtpd_1.2.2-1+deb11u1.debian.tar.xz
 ed18d6b9d606ccfef24ed83db7a683cb08c9f443 7620 
python-aiosmtpd_1.2.2-1+deb11u1_amd64.buildinfo
Checksums-Sha256:
 accb80544ff605ea0abbbaefc054918b1a85c64237c97a48a2d3ad2a50a912ad 1584 
python-aiosmtpd_1.2.2-1+deb11u1.dsc
 7b238a09e4108462d9dd8ad9971f2a8dcabd7b752574073e4c1a21d9687ee467 5376 
python-aiosmtpd_1.2.2-1+deb11u1.debian.tar.xz
 50b87cc99c93a9d4e3731b12f9048199d266fa239251a11ccc809b6763bae1a7 7620 
python-aiosmtpd_1.2.2-1+deb11u1_amd64.buildinfo
Files:
 2ed2ffb8b9eb9378908d680aef231658 1584 python optional 
python-aiosmtpd_1.2.2-1+deb11u1.dsc
 9f2282e707f51d5b5635e983f09f77dd 5376 python optional 
python-aiosmtpd_1.2.2-1+deb11u1.debian.tar.xz
 e805cd46304aacc500b894b9d27b361c 7620 python optional 
python-aiosmtpd_1.2.2-1+deb11u1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZm4BjwAKCRAhk2s2YA/N
iZ5iAQDmHFC75ydIOn75NexeMObtdg45Fmw/RCNCkhLuZRIDBwD8C+md/V5VbVcc
yu0j4f11M/IwA2mRs5WxEJ8c7t4eSQ4=
=jilf
-END PGP SIGNATURE-



pgpIAtjmF2zft.pgp
Description: PGP signature
--- End Message ---

Bug#1050288: marked as done (nsis 3.08-3 (bookworm) generates bogus relocation information (regression))

[Debian Bug Tracking System]

Your message dated Mon, 17 Jun 2024 16:47:08 +
with message-id 
and subject line Bug#1050288: fixed in nsis 3.08-3+deb12u1
has caused the Debian Bug report #1050288,
regarding nsis 3.08-3 (bookworm) generates bogus relocation information 
(regression)
to be marked as done.

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

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


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

Package: nsis
Version: 3.08-3
Severity: important

makensis 3.08-3 on bookworm creates installers with a non-empty 
relocation section which contains garbage.


The installers work, but trigger false positive warnings from security 
scanners, likely due to exe file corruption.


Testcase:

$ dpkg --list nsis nsis-common
...
ii  nsis   3.08-3   amd64    ...
ii  nsis-common    3.08-3   all  ...

$ cat test.nsi
Section "Empty"
SectionEnd

$ makensis test.nsi
...

$ objdump -p test.exe >/dev/null
objdump: error: test.exe(.reloc) is too large (0x8e4 bytes)

$ objdump -p test.exe 2>/dev/null
...
Entry 5 00047000 08e4 Base Relocation Directory [.reloc]
...

$ objdump -p /usr/share/nsis/Stubs/zlib-x86-unicode
...
Entry 5 00047000 08e4 Base Relocation Directory [.reloc]
...
PE File Base Relocations (interpreted .reloc section contents)

Virtual Address: 1000 Chunk size 196 (0xc4) Number of fixups 94
    reloc    0 offset   2b [102b] HIGHLOW
    reloc    1 offset   40 [1040] HIGHLOW
...
Virtual Address: c000 Chunk size 216 (0xd8) Number of fixups 104
    reloc    1 offset    8 [c008] HIGHLOW
    reloc    2 offset    c [c00c] HIGHLOW
...
    reloc  102 offset  8f8 [c8f8] HIGHLOW
    reloc  103 offset  8fc [c8fc] HIGHLOW


All the stubs apparently have a non-empty relocation section with 
garbage. This is not the case for the stubs from nsis-common-3.06.1-1 
(bullseye) and nsis-common-3.09-1 (sid).


This is also not the case with the upstream 3.08 and 3.09 builds for 
windows which are available at

https://sourceforge.net/projects/nsis/files/NSIS%203/

Related: https://sourceforge.net/p/nsis/bugs/1299/

--
Regards
Christian Franke
smartmontools.org
--- End Message ---
--- Begin Message ---
Source: nsis
Source-Version: 3.08-3+deb12u1
Done: Thomas Gaugler 

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

Debian distribution maintenance software
pp.
Thomas Gaugler  (supplier of updated nsis package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 05 Feb 2024 11:18:05 +0100
Source: nsis
Architecture: source
Version: 3.08-3+deb12u1
Distribution: bookworm
Urgency: medium
Maintainer: Thomas Gaugler 
Changed-By: Thomas Gaugler 
Closes: 1040880 1050288
Changes:
 nsis (3.08-3+deb12u1) bookworm; urgency=medium
 .
   * Cherry-pick upstream commits to fix CVE-2023-37378 (Closes: #1040880)
   * Use common options for nsis-doc installation
   * Exclude Debian revison suffix from VER_REVISION
   * Backport upstream commit to disable stub relocations (Closes: #1050288)
Checksums-Sha1:
 9b8a1ee43d18f41bec9a3fea5012aed64cac3b59 1633 nsis_3.08-3+deb12u1.dsc
 8e49435ca97a7bec1b2248d778bb7e1acb24267b 32284 
nsis_3.08-3+deb12u1.debian.tar.xz
Checksums-Sha256:
 68b74caa1c1123d6771282b373b485d740ba8013f7b54bcc30238a3d54973278 1633 
nsis_3.08-3+deb12u1.dsc
 15964a928584aadee8a71e35fc456d32f2e6b9b9ed491c6f6e49906cdffb3c07 32284 
nsis_3.08-3+deb12u1.debian.tar.xz
Files:
 9a949c5ae5ab32b1c0fbb86cd2e96434 1633 devel optional nsis_3.08-3+deb12u1.dsc
 d76fb11d9706b874061dfab5200a0729 32284 devel optional 
nsis_3.08-3+deb12u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQTjpQ0b6NokWkvBQbzqgwvGpoTNfAUCZnACYAAKCRDqgwvGpoTN
fFRWAQCWsqrwUHJXlldo2M4Yc5ZgeQFOTEp06wm4M4fgQwocQgD/WvSPH/bUrwzm
08ALnEE07/XH3E/3g6NbjpHFW0mhkgw=
=ruhL
-END PGP SIGNATURE-



pgppffOVlkKiE.pgp
Description: PGP signature
--- End Message ---

Bug#1073308: marked as pending in pd-pdogg

[IOhannes zmölnig]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/multimedia-team/pd/pd-pdogg/-/commit/b8e485b149b5a5af79f5fc684c28390ea99f3359


Add patch to fix building with Pd64

Closes: #1073308


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1073308

Processed: Bug#1073308 marked as pending in pd-pdogg

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1073308 [src:pd-pdogg] pd-pdogg: FTBFS: m_pd.h:85:26: error: static 
assertion failed: "field must be t_float!"
Added tag(s) pending.

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

Bug#1073557: marked as done (python3-motor: Fails to import and crashes the entire program)

[Debian Bug Tracking System]

Your message dated Mon, 17 Jun 2024 16:36:10 +
with message-id 
and subject line Bug#1073557: fixed in python-motor 3.4.0-1
has caused the Debian Bug report #1073557,
regarding python3-motor: Fails to import and crashes the entire program
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.)


-- 
1073557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073557
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-motor
Version: 2.3.0-3
Severity: grave
Tags: upstream
Justification: renders package unusable
X-Debbugs-Cc: ltw...@debian.org

Dear Maintainer,

the package no longer works.


import motor.motor_asyncio

ModuleNotFoundError: No module named 'pymongo.mongo_replica_set_client'

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

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

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


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

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

Versions of packages python3-motor depends on:
ii  python3  3.11.8-1
ii  python3-gridfs   4.7.3-1
ii  python3-pymongo  4.7.3-1

python3-motor recommends no packages.

Versions of packages python3-motor suggests:
ii  python3-aiohttp  3.9.5-1
ii  python3-tornado  6.4.1-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: python-motor
Source-Version: 3.4.0-1
Done: Salvo 'LtWorf' Tomaselli 

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

Debian distribution maintenance software
pp.
Salvo 'LtWorf' Tomaselli  (supplier of updated python-motor 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 17 Jun 2024 15:13:41 +0200
Source: python-motor
Architecture: source
Version: 3.4.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Salvo 'LtWorf' Tomaselli 
Closes: 1073557
Changes:
 python-motor (3.4.0-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Remove myself from Uploaders.
 .
   [ Salvo 'LtWorf' Tomaselli ]
   * New upstream version (Closes: #1073557)
   * Add myself to uploaders
   * Drop version in dependencies
   * Remove upstreamed patches
Checksums-Sha1:
 017cce7d5a1a4aea23e29b1d364f3c837c20c6ba 2220 python-motor_3.4.0-1.dsc
 c8560dbb57c51c9d9ce79eddb9fe38fdfb20ab53 274386 python-motor_3.4.0.orig.tar.gz
 3b3d23c6c826e4d64d91644ffdcd3173f6038043 4032 
python-motor_3.4.0-1.debian.tar.xz
 ee6d6ffa010fa447bb06cbbb319cc550a519fe55 7035 
python-motor_3.4.0-1_amd64.buildinfo
Checksums-Sha256:
 34b363dd2719d71aedf60c46474762c9e82bb6cf2c7bea8ac76356a708684b18 2220 
python-motor_3.4.0-1.dsc
 ff01ec029bfbeb21ef6f11a8751c6dc7ad9399f4579e92f37af4e7c978373074 274386 
python-motor_3.4.0.orig.tar.gz
 0ec604c5a20cdf6c314137fe1fd09d91ece45aabda6218c3b97fd75732b02da4 4032 
python-motor_3.4.0-1.debian.tar.xz
 84c41435421f33cc7ec9246029c47a8efef7c38bcfa4007523d2237a4d55ecf1 7035 
python-motor_3.4.0-1_amd64.buildinfo
Files:
 2e6a8c8a35f88cccaba264536838ab79 2220 python optional python-motor_3.4.0-1.dsc
 b3bf690ac0eb53bc4081029313d17c19 274386 python optional 
python-motor_3.4.0.orig.tar.gz
 0687aef563829a9b5b639df1c8d98d7a 4032 python optional 
python-motor_3.4.0-1.debian.tar.xz
 77826601ec7109998d0f780e79b6ee3e 7035 python optional 
python-motor_3.4.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJdBAEBCgBHFiEEQnSLnnbYmXmeH74Us6fPDIAYhs8FAmZwYMUpHHNhbHZhdG9y
ZS50b21hc2VsbGlAZ2FsaWxlby5kbWkudW5pY3QuaXQACgkQs6fPDIAYhs9jaQ//
apd3O9L55ccJtouhMySDc/vMbUhEUS6Jo8VO87Lo4Yb0uxirG+mVcppIfatudnty

Bug#1073340: marked as done (pd-mrpeach: FTBFS: m_pd.h:85:26: error: static assertion failed: "field must be t_float!")

[Debian Bug Tracking System]

Your message dated Mon, 17 Jun 2024 16:35:59 +
with message-id 
and subject line Bug#1073340: fixed in pd-mrpeach 0.1~svn17672-6
has caused the Debian Bug report #1073340,
regarding pd-mrpeach: FTBFS: m_pd.h:85:26: error: static assertion failed: 
"field must be t_float!"
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.)


-- 
1073340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073340
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-mrpeach
Version: 0.1~svn17672-5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> cc -DPD -I "/usr/include/pd" -DPD_FLOATSIZE=64 -DUNIX -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIC  -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -o sqosc~/sqosc~.linux-amd64-64.so.o 
> -c sqosc~/sqosc~.c
>  info: making cmos/cd4001.linux-amd64-64.so.o in lib mrpeach
> In file included from sqosc~/sqosc~.c:10:
> sqosc~/sqosc~.c: In function ‘sqosc_tilde_setup’:
> /usr/include/pd/m_pd.h:85:26: error: static assertion failed: "field must be 
> t_float!"
>85 | #define PD_STATIC_ASSERT _Static_assert
>   |  ^~
> /usr/include/pd/m_pd.h:575:5: note: in expansion of macro ‘PD_STATIC_ASSERT’
>   575 | PD_STATIC_ASSERT(sizeof(((type *)NULL)->field) == 
> sizeof(t_float), "field must be t_float!"); \
>   | ^~~~
> sqosc~/sqosc~.c:343:5: note: in expansion of macro ‘CLASS_MAINSIGNALIN’
>   343 | CLASS_MAINSIGNALIN(sqosc_class, t_sqosc, x_f);/* x_f is used when 
> no signal is input */
>   | ^~
> cc -DPD -I "/usr/include/pd" -DPD_FLOATSIZE=64 -DUNIX -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIC  -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -o cmos/cd4001.linux-amd64-64.so.o -c 
> cmos/cd4001.c
>  info: making net/udpsndrcv.linux-amd64-64.so.o in lib mrpeach
> make[1]: *** [/usr/share/pd-lib-builder//Makefile.pdlibbuilder:987: 
> sqosc~/sqosc~.linux-amd64-64.so.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/06/15/pd-mrpeach_0.1~svn17672-5_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240615;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240615=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 mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: pd-mrpeach
Source-Version: 0.1~svn17672-6
Done: IOhannes m zmölnig (Debian/GNU) 

We believe that the bug you reported is fixed in the latest version of
pd-mrpeach, 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 1073...@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 
pd-mrpeach package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 17 Jun 2024 18:11:18 +0200
Source: pd-mrpeach
Architecture: source
Version: 0.1~svn17672-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Closes: 1073340
Changes:
 pd-mrpeach (0.1~svn17672-6) unstable; urgency=medium
 .
   * Fix FTBFS with Pd64 (Closes: #1073340)
   * Add 'Provides' stanza
   * Switch to 

Processed: Bug#1073330 marked as pending in pd-sigpack

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1073330 [src:pd-sigpack] pd-sigpack: FTBFS: m_pd.h:85:26: error: static 
assertion failed: "field must be t_float!"
Added tag(s) pending.

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

Bug#1073330: marked as pending in pd-sigpack

[IOhannes zmölnig]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/multimedia-team/pd/pd-sigpack/-/commit/39ff21a3afe272611fc82e40791e4e80ee391c75


Fix FTBFS with Pd64

Closes: #1073330


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1073330

Bug#1073351: marked as done (pd-motex: FTBFS: m_pd.h:85:26: error: static assertion failed: "field must be t_float!")

[Debian Bug Tracking System]

Your message dated Mon, 17 Jun 2024 16:22:43 +
with message-id 
and subject line Bug#1073351: fixed in pd-motex 1.1.4-9
has caused the Debian Bug report #1073351,
regarding pd-motex: FTBFS: m_pd.h:85:26: error: static assertion failed: "field 
must be t_float!"
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.)


-- 
1073351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073351
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-motex
Version: 1.1.4-8
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> cc -DPD -I "/usr/include/pd" -DPD_FLOATSIZE=64 -DUNIX -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIC  -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -o pansig~.linux-amd64-64.so.o -c 
> pansig~.c
>  info: making pan~.linux-amd64-64.so.o in lib motex
> getenv.c: In function ‘getenv_new’:
> getenv.c:57:20: warning: assignment discards ‘const’ qualifier from pointer 
> target type [-Wdiscarded-qualifiers]
>57 |   x->envar = argv[0].a_w.w_symbol->s_name;
>   |^
> system.c: In function ‘system_anything’:
> system.c:52:3: warning: ignoring return value of ‘system’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>52 |   system(message);
>   |   ^~~
> pansig~.c: In function ‘pansig_perform’:
> pansig~.c:67:16: warning: initialization of ‘float *’ from incompatible 
> pointer type ‘t_float *’ {aka ‘double *’} [-Wincompatible-pointer-types]
>67 |   float *in1 = (t_float *)(w[1]);
>   |^
> pansig~.c:68:16: warning: initialization of ‘float *’ from incompatible 
> pointer type ‘t_float *’ {aka ‘double *’} [-Wincompatible-pointer-types]
>68 |   float *in2 = (t_float *)(w[2]);
>   |^
> pansig~.c:69:17: warning: initialization of ‘float *’ from incompatible 
> pointer type ‘t_float *’ {aka ‘double *’} [-Wincompatible-pointer-types]
>69 |   float *out1 = (t_float *)(w[3]);
>   | ^
> pansig~.c:70:17: warning: initialization of ‘float *’ from incompatible 
> pointer type ‘t_float *’ {aka ‘double *’} [-Wincompatible-pointer-types]
>70 |   float *out2 = (t_float *)(w[4]);
>   | ^
> pansig~.c:78:29: warning: passing argument 2 of ‘pansig_getpan’ from 
> incompatible pointer type [-Wincompatible-pointer-types]
>78 |   pansig_getpan(value2, , );
>   | ^
>   | |
>   | float *
> pansig~.c:31:58: note: expected ‘t_floatarg *’ {aka ‘double *’} but argument 
> is of type ‘float *’
>31 | static void pansig_getpan(t_floatarg signal, t_floatarg *left, 
> t_floatarg *right)
>   |  ^~~~
> pansig~.c:78:36: warning: passing argument 3 of ‘pansig_getpan’ from 
> incompatible pointer type [-Wincompatible-pointer-types]
>78 |   pansig_getpan(value2, , );
>   |^~
>   ||
>   |float *
> pansig~.c:31:76: note: expected ‘t_floatarg *’ {aka ‘double *’} but argument 
> is of type ‘float *’
>31 | static void pansig_getpan(t_floatarg signal, t_floatarg *left, 
> t_floatarg *right)
>   |
> ^
> pansig~.c: In function ‘pansig_dsp’:
> pansig~.c:92:16: warning: initialization of ‘float *’ from incompatible 
> pointer type ‘t_sample *’ {aka ‘double *’} [-Wincompatible-pointer-types]
>92 |   float *in1 = sp[0]->s_vec;
>   |^~
> pansig~.c:93:16: warning: initialization of ‘float *’ from incompatible 
> pointer type ‘t_sample *’ {aka ‘double *’} [-Wincompatible-pointer-types]
>93 |   float *in2 = sp[1]->s_vec;
>   |^~
> pansig~.c:94:17: warning: initialization of ‘float *’ from incompatible 
> pointer type ‘t_sample *’ {aka ‘double *’} [-Wincompatible-pointer-types]
>94 |   float *out1 = sp[2]->s_vec;
>   | ^~
> pansig~.c:95:17: warning: initialization of ‘float *’ from incompatible 
> pointer type ‘t_sample *’ {aka ‘double *’} [-Wincompatible-pointer-types]
>95 |   

Bug#1073349: marked as done (pd-moonlib: FTBFS: m_pd.h:85:26: error: static assertion failed: "field must be t_float!")

[Debian Bug Tracking System]

Your message dated Mon, 17 Jun 2024 16:22:36 +
with message-id 
and subject line Bug#1073349: fixed in pd-moonlib 0.7-3
has caused the Debian Bug report #1073349,
regarding pd-moonlib: FTBFS: m_pd.h:85:26: error: static assertion failed: 
"field must be t_float!"
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.)


-- 
1073349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073349
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-moonlib
Version: 0.7-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> cc -DPD -I "/usr/include/pd" -DPD_FLOATSIZE=64 -DUNIX -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIC -Wno-unused -Wno-unused-parameter -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o 
> comma.linux-amd64-64.so.o -c comma.c
>  info: making sfread2~.linux-amd64-64.so.o in lib moonlib
> In file included from ssaw~.c:23:
> ssaw~.c: In function ‘ssaw_tilde_setup’:
> /usr/include/pd/m_pd.h:85:26: error: static assertion failed: "field must be 
> t_float!"
>85 | #define PD_STATIC_ASSERT _Static_assert
>   |  ^~
> /usr/include/pd/m_pd.h:575:5: note: in expansion of macro ‘PD_STATIC_ASSERT’
>   575 | PD_STATIC_ASSERT(sizeof(((type *)NULL)->field) == 
> sizeof(t_float), "field must be t_float!"); \
>   | ^~~~
> ssaw~.c:187:5: note: in expansion of macro ‘CLASS_MAINSIGNALIN’
>   187 | CLASS_MAINSIGNALIN(ssaw_class, t_ssaw, x_f);
>   | ^~
> make[1]: *** [/usr/share/pd-lib-builder//Makefile.pdlibbuilder:987: 
> ssaw~.linux-amd64-64.so.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/06/15/pd-moonlib_0.7-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240615;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240615=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 mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: pd-moonlib
Source-Version: 0.7-3
Done: IOhannes m zmölnig (Debian/GNU) 

We believe that the bug you reported is fixed in the latest version of
pd-moonlib, 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 1073...@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 
pd-moonlib package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 17 Jun 2024 17:52:53 +0200
Source: pd-moonlib
Architecture: source
Version: 0.7-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Closes: 1073349
Changes:
 pd-moonlib (0.7-3) unstable; urgency=medium
 .
   * Add patch to fix building with Pd64 (Closes: #1073349)
   * Add 'Provides' stanza
   * Switch to dh-sequence-puredata
   * Bump standards version to 4.7.0
Checksums-Sha1:
 de67565ae0df4673187d424a82943a5d0a789982 2123 pd-moonlib_0.7-3.dsc
 fbcb7887b46b9acf81cc2cb1186eef8f92a6863a 7756 pd-moonlib_0.7-3.debian.tar.xz
Checksums-Sha256:
 a04053ee55863cac1b3d05d099cf2fdd1426a01929df46e662418bd6db2464c0 2123 
pd-moonlib_0.7-3.dsc
 4f2680d202b99d8491ba85daf2b35c50211b3f3426d3810f6224d2352e1fee6d 7756 
pd-moonlib_0.7-3.debian.tar.xz
Files:
 94a28d1d8f69e1710ac8d943a533ae9e 2123 sound optional pd-moonlib_0.7-3.dsc
 

Bug#950372: closed by Debian FTP Masters (reply to Alex Myczko ) (Bug#950372: fixed in radare2 5.9.0+dfsg-1)

[Adrian Bunk]

On Thu, Apr 25, 2024 at 02:54:32PM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the src:radare2 package:
> 
> #950372: Is radare2 suitable for stable Debian releases?
>...
>  radare2 (5.9.0+dfsg-1) unstable; urgency=medium
>  .
>* New upstream version. (Closes: #1034862, #1060127, #950372)
>...
> It is understandable (and normal for most software) that upstream
> is not able or willing to provide security support for the old
> version shipped in stable distribution releases.
> 
> But below seems to be upstream actively encouraging exploiting
> the version in stable.
> 
> AFAIK Debian in general tries to avoid shipping software when upstream
> strongly objects to it, or is openly hostile towards Debian.
> 
> <--  snip  -->
> 
> https://rada.re/con/2019/
> 
> PwnDebian
> 
> Since the very begining of radare development we had people complaining of 
> bugs because they were using the 3-4 year old version shipped in their 
> distro. We tried to work with everyone who ships builds of r2 to always get 
> updates and merge back their patches upstream so everyone gets benefit out of 
> it.
> 
> But that has been not enough. In github/radare2 we can check out most of 
> known/used Linux and BSD distros and the shipped r2 version, and it's pretty 
> clear that Debian/Ubuntu stopped updating those packages long time ago 
> (3.2.1). Yes, the 0.9.6 drama is over.
> 
> The aim of this competition is to publish a working exploit for radare2 on 
> Debian stable (nowadays, unstable keeps the same version). To show that 
> debian-security and backporting patches is not solving enough when 
> distributing such state-of-the-art packages.
> 
> In order to win this competition. We will accept only 1 working exploit (the 
> first one to submit it) for radare2-3.2.1 (built for x86-64 debian/stable). 
> Additional points will be given for writing some notes or presenting at r2con 
> the way the vuln was found and how the exploit was developed.


Hi Alex,

has there been any change in the attitude radare2 upstream has towards 
distributions?

cu
Adrian

Processed: Bug#1073340 marked as pending in pd-mrpeach

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1073340 [src:pd-mrpeach] pd-mrpeach: FTBFS: m_pd.h:85:26: error: static 
assertion failed: "field must be t_float!"
Added tag(s) pending.

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

Bug#1073340: marked as pending in pd-mrpeach

[IOhannes zmölnig]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/multimedia-team/pd/pd-mrpeach/-/commit/79db5c3f5b80b92c85dc83c30e30e3ced69c58ec


Fix FTBFS with Pd64

Closes: #1073340


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1073340

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 1073259 botch
Bug #1073259 {Done: Gianfranco Costamagna } 
[libyojson-ocaml-dev] libyojson-ocaml-dev should depend on yojson-tools
Bug reassigned from package 'libyojson-ocaml-dev' to 'botch'.
No longer marked as found in versions yojson/2.2.1-1.
No longer marked as fixed in versions botch/0.24-4.
> forcemerge 1073199 1073259
Bug #1073199 {Done: Gianfranco Costamagna } [botch] 
botch: please update from libyojson-ocaml-dev to new yojson-tools package
Bug #1073259 {Done: Gianfranco Costamagna } [botch] 
libyojson-ocaml-dev should depend on yojson-tools
Removed indication that 1073259 affects src:botch
Marked as fixed in versions botch/0.24-4.
Marked as found in versions botch/0.24-3.
Added tag(s) patch.
Bug #1073199 {Done: Gianfranco Costamagna } [botch] 
botch: please update from libyojson-ocaml-dev to new yojson-tools package
Added tag(s) ftbfs.
Merged 1073199 1073259
> thanks
Stopping processing here.

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

Processed: forward #1071775 to upstream

[Debian Bug Tracking System]

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

> forwarded 1071775  https://github.com/PlotPyStack/PlotPy/issues/11
Bug #1071775 [src:plotpy] plotpy: FTBFS: 
plotpy/tests/benchmarks/test_benchmarks.py Fatal Python error: Aborted
Set Bug forwarded-to-address to 
'https://github.com/PlotPyStack/PlotPy/issues/11'.
>
End of message, stopping processing here.

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

Processed: Bug#1073351 marked as pending in pd-motex

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1073351 [src:pd-motex] pd-motex: FTBFS: m_pd.h:85:26: error: static 
assertion failed: "field must be t_float!"
Added tag(s) pending.

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

Bug#1073351: marked as pending in pd-motex

[IOhannes zmölnig]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/multimedia-team/pd/pd-motex/-/commit/ea9375635ad6ad24f7143640ccf8458a98a6c801


Fix FTBFS with Pd64

Closes: #1073351


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1073351

Bug#1073349: marked as pending in pd-moonlib

[IOhannes zmölnig]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/multimedia-team/pd/pd-moonlib/-/commit/7fb546bdd4de5a9a374c8474c27e4c6f1b3bd803


Add patch to fix building with Pd64

Closes: #1073349


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1073349

Processed: Bug#1073349 marked as pending in pd-moonlib

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1073349 [src:pd-moonlib] pd-moonlib: FTBFS: m_pd.h:85:26: error: static 
assertion failed: "field must be t_float!"
Added tag(s) pending.

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

Bug#1073342: marked as done (pd-mjlib: FTBFS: m_pd.h:85:26: error: static assertion failed: "field must be t_float!")

[Debian Bug Tracking System]

Your message dated Mon, 17 Jun 2024 15:50:23 +
with message-id 
and subject line Bug#1073342: fixed in pd-mjlib 0.2.0-2
has caused the Debian Bug report #1073342,
regarding pd-mjlib: FTBFS: m_pd.h:85:26: error: static assertion failed: "field 
must be t_float!"
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.)


-- 
1073342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073342
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-mjlib
Version: 0.2.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> cc -DPD -I "/usr/include/pd" -DPD_FLOATSIZE=64 -DUNIX -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIC  -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -o src/monorhythm.linux-amd64-64.so.o 
> -c src/monorhythm.c
> src/metroplus.c: In function ‘metroplus_time_seq’:
> src/metroplus.c:125:28: warning: assignment to ‘t_float *’ {aka ‘double *’} 
> from incompatible pointer type ‘float *’ [-Wincompatible-pointer-types]
>   125 | x->x_times = (float *) malloc( ac * sizeof( float ));
>   |^
> src/metroplus.c:135:28: warning: assignment to ‘t_float *’ {aka ‘double *’} 
> from incompatible pointer type ‘float *’ [-Wincompatible-pointer-types]
>   135 | x->x_times = (float *) malloc( sizeof( float ));
>   |^
> src/metroplus.c: In function ‘metroplus_time_float’:
> src/metroplus.c:152:20: warning: assignment to ‘t_float *’ {aka ‘double *’} 
> from incompatible pointer type ‘float *’ [-Wincompatible-pointer-types]
>   152 | x->x_times = (float *) malloc( sizeof( float ));
>   |^
> src/monorhythm.c: In function ‘monorhythm_pattern_seq’:
> src/monorhythm.c:172:30: warning: assignment to ‘t_float *’ {aka ‘double *’} 
> from incompatible pointer type ‘float *’ [-Wincompatible-pointer-types]
>   172 | x->x_pattern = (float *) malloc( ac * sizeof( float 
> ));
>   |  ^
> In file included from src/pin~.c:1:
> src/pin~.c: In function ‘pin_tilde_setup’:
> /usr/include/pd/m_pd.h:85:26: error: static assertion failed: "field must be 
> t_float!"
>85 | #define PD_STATIC_ASSERT _Static_assert
>   |  ^~
> /usr/include/pd/m_pd.h:575:5: note: in expansion of macro ‘PD_STATIC_ASSERT’
>   575 | PD_STATIC_ASSERT(sizeof(((type *)NULL)->field) == 
> sizeof(t_float), "field must be t_float!"); \
>   | ^~~~
> src/pin~.c:198:5: note: in expansion of macro ‘CLASS_MAINSIGNALIN’
>   198 | CLASS_MAINSIGNALIN( pin_tilde_class, t_pin_tilde, x_f);
>   | ^~
> make[1]: *** [/usr/share/pd-lib-builder//Makefile.pdlibbuilder:987: 
> src/pin~.linux-amd64-64.so.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/06/15/pd-mjlib_0.2.0-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240615;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240615=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 mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: pd-mjlib
Source-Version: 0.2.0-2
Done: IOhannes m zmölnig (Debian/GNU) 

We believe that the bug you reported is fixed in the latest version of
pd-mjlib, 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 1073...@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 
pd-mjlib package)

(This message 

Bug#1073333: marked as done (pd-ggee: FTBFS: experimental/fofsynth~.c:31:46: error: ‘COSTABSIZE’ undeclared (first use in this function))

[Debian Bug Tracking System]

Your message dated Mon, 17 Jun 2024 15:50:17 +
with message-id 
and subject line Bug#107: fixed in pd-ggee 0.28-6
has caused the Debian Bug report #107,
regarding pd-ggee: FTBFS: experimental/fofsynth~.c:31:46: error: ‘COSTABSIZE’ 
undeclared (first use in this function)
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.)


-- 
107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=107
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-ggee
Version: 0.28-5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> cc -DPD -I "/usr/include/pd"  -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC  
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o 
> filters/equalizer.pd_linux.o -c filters/equalizer.c
>  info: making gui/state.pd_linux.o in lib ggee
> gui/image.c: In function ‘image_drawme’:
> gui/image.c:32:11: warning: ‘sys_vgui’ is deprecated 
> [-Wdeprecated-declarations]
>32 |   sys_vgui("image create photo img%lx -file {%s}\n",x,fname);
>   |   ^~~~
> In file included from gui/image.c:2:
> /usr/include/pd/m_pd.h:796:27: note: declared here
>   796 | PD_DEPRECATED EXTERN void sys_vgui(const char *fmt, ...); /* avoid 
> this: use pdgui_vmess() instead */
>   |   ^~~~
> gui/image.c:33:11: warning: ‘sys_vgui’ is deprecated 
> [-Wdeprecated-declarations]
>33 |   sys_vgui(".x%lx.c create image %d %d -image img%lx -tags 
> %lxS\n",
>   |   ^~~~
> /usr/include/pd/m_pd.h:796:27: note: declared here
>   796 | PD_DEPRECATED EXTERN void sys_vgui(const char *fmt, ...); /* avoid 
> this: use pdgui_vmess() instead */
>   |   ^~~~
> gui/image.c:42:18: warning: ‘sys_vgui’ is deprecated 
> [-Wdeprecated-declarations]
>42 |  sys_vgui(".x%lx.c coords %lxS %d %d\n",
>   |  ^~~~
> /usr/include/pd/m_pd.h:796:27: note: declared here
>   796 | PD_DEPRECATED EXTERN void sys_vgui(const char *fmt, ...); /* avoid 
> this: use pdgui_vmess() instead */
>   |   ^~~~
> gui/image.c: In function ‘image_erase’:
> gui/image.c:53:6: warning: ‘sys_vgui’ is deprecated 
> [-Wdeprecated-declarations]
>53 |  sys_vgui(".x%lx.c delete %lxS\n",
>   |  ^~~~
> /usr/include/pd/m_pd.h:796:27: note: declared here
>   796 | PD_DEPRECATED EXTERN void sys_vgui(const char *fmt, ...); /* avoid 
> this: use pdgui_vmess() instead */
>   |   ^~~~
> gui/image.c: In function ‘image_displace’:
> gui/image.c:102:5: warning: ‘sys_vgui’ is deprecated 
> [-Wdeprecated-declarations]
>   102 | sys_vgui(".x%lx.c coords %lxSEL %d %d %d %d\n",
>   | ^~~~
> /usr/include/pd/m_pd.h:796:27: note: declared here
>   796 | PD_DEPRECATED EXTERN void sys_vgui(const char *fmt, ...); /* avoid 
> this: use pdgui_vmess() instead */
>   |   ^~~~
> gui/image.c: In function ‘image_select’:
> gui/image.c:115:11: warning: ‘sys_vgui’ is deprecated 
> [-Wdeprecated-declarations]
>   115 |   sys_vgui(".x%lx.c create rectangle \
>   |   ^~~~
> /usr/include/pd/m_pd.h:796:27: note: declared here
>   796 | PD_DEPRECATED EXTERN void sys_vgui(const char *fmt, ...); /* avoid 
> this: use pdgui_vmess() instead */
>   |   ^~~~
> gui/image.c:123:11: warning: ‘sys_vgui’ is deprecated 
> [-Wdeprecated-declarations]
>   123 |   sys_vgui(".x%lx.c delete %lxSEL\n",
>   |   ^~~~
> /usr/include/pd/m_pd.h:796:27: note: declared here
>   796 | PD_DEPRECATED EXTERN void sys_vgui(const char *fmt, ...); /* avoid 
> this: use pdgui_vmess() instead */
>   |   ^~~~
> control/qread.c: In function ‘qread_next’:
> control/qread.c:66:6: warning: ignoring return value of ‘fscanf’ declared 
> with attribute ‘warn_unused_result’ [-Wunused-result]
>66 |  fscanf(x->x_file,"%f",);
>   |  ^
> control/qread.c:72:6: warning: ignoring return value of ‘fscanf’ declared 
> with attribute ‘warn_unused_result’ [-Wunused-result]
>72 |  fscanf(x->x_file,"%s",name);
>   |  ^~~
> 

Processed: tagging 1055297, tagging 1047864, tagging 1042983, tagging 1071992, tagging 1073557 ...

[Debian Bug Tracking System]

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

> tags 1055297 + sid trixie
Bug #1055297 {Done: Aurelien Jarno } [ruby3.1] ruby3.1: 
fails to build against glibc 2.38
Added tag(s) sid and trixie.
> tags 1047864 + sid trixie
Bug #1047864 {Done: Gunnar Wolf } [impressive] impressive: 
Crashes at startup: «module 'PIL.Image' has no attribute 'ANTIALIAS'»
Added tag(s) trixie and sid.
> tags 1042983 + sid trixie
Bug #1042983 {Done: Arnaud Ferraris } [squeekboard] 
squeekboard - rust gtk stack update.
Added tag(s) trixie and sid.
> tags 1071992 + sid trixie experimental
Bug #1071992 [src:sqlmodel] sqlmodel: please make this package compatible with 
SQL Alchemy 2.x
Added tag(s) experimental, sid, and trixie.
> tags 1073557 + sid trixie
Bug #1073557 [python3-motor] python3-motor: Fails to import and crashes the 
entire program
Added tag(s) trixie and sid.
> notfound 1073299 2.4.90
Bug #1073299 [roger-router] debian package version 2.4.2 does not work in 
stable, and was not updated to 2.4.90 in testing and unstable.
There is no source info for the package 'roger-router' at version '2.4.90' with 
architecture ''
Unable to make a source version for version '2.4.90'
No longer marked as found in versions 2.4.90.
> found 1073299 2.4.2-3
Bug #1073299 [roger-router] debian package version 2.4.2 does not work in 
stable, and was not updated to 2.4.90 in testing and unstable.
Marked as found in versions roger-router/2.4.2-3.
> found 1073290 256~rc1-1~exp
Bug #1073290 [systemd] systemd: Please breaks against dracut-core << 102-2~
Marked as found in versions systemd/256~rc1-1~exp.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1042983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042983
1047864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1047864
1055297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055297
1071992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071992
1073290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073290
1073299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073299
1073557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073557
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1073322: marked as done (pd-ext13: FTBFS: m_pd.h:85:26: error: static assertion failed: "field must be t_float!")

[Debian Bug Tracking System]

Your message dated Mon, 17 Jun 2024 15:36:20 +
with message-id 
and subject line Bug#1073322: fixed in pd-ext13 0.17.1-10
has caused the Debian Bug report #1073322,
regarding pd-ext13: FTBFS: m_pd.h:85:26: error: static assertion failed: "field 
must be t_float!"
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.)


-- 
1073322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073322
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-ext13
Version: 0.17.1-9
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> cc -rdynamic -shared -fPIC -Wl,-rpath,"\$ORIGIN",--enable-new-dtags  
> -Wl,-z,relro -Wl,-z,now  -o ftos.linux-amd64-64.so ftos.linux-amd64-64.so.o  
> -lc -lm   
>  info: linking objects in catch13~.linux-amd64-64.so for lib ext13
> mandelbrot~.c: In function ‘mandelbrot_tilde_new’:
> mandelbrot~.c:18:35: warning: passing argument 2 of ‘floatinlet_new’ from 
> incompatible pointer type [-Wincompatible-pointer-types]
>18 | floatinlet_new(>x_obj, >k);
>   |   ^
>   |   |
>   |   float *
> In file included from mandelbrot~.c:1:
> /usr/include/pd/m_pd.h:460:58: note: expected ‘t_float *’ {aka ‘double *’} 
> but argument is of type ‘float *’
>   460 | EXTERN t_inlet *floatinlet_new(t_object *owner, t_float *fp);
>   | ~^~
> mandelbrot~.c: In function ‘mandelbrot_tilde_setup’:
> /usr/include/pd/m_pd.h:85:26: error: static assertion failed: "field must be 
> t_float!"
>85 | #define PD_STATIC_ASSERT _Static_assert
>   |  ^~
> /usr/include/pd/m_pd.h:575:5: note: in expansion of macro ‘PD_STATIC_ASSERT’
>   575 | PD_STATIC_ASSERT(sizeof(((type *)NULL)->field) == 
> sizeof(t_float), "field must be t_float!"); \
>   | ^~~~
> mandelbrot~.c:120:5: note: in expansion of macro ‘CLASS_MAINSIGNALIN’
>   120 | CLASS_MAINSIGNALIN(mandelbrot_tilde_class, t_mandelbrot_tilde, k);
>   | ^~
> cc -rdynamic -shared -fPIC -Wl,-rpath,"\$ORIGIN",--enable-new-dtags  
> -Wl,-z,relro -Wl,-z,now  -o catch13~.linux-amd64-64.so 
> catch13~.linux-amd64-64.so.o  -lc -lm   
>  info: linking objects in send13~.linux-amd64-64.so for lib ext13
> make[1]: *** [/usr/share/pd-lib-builder//Makefile.pdlibbuilder:987: 
> mandelbrot~.linux-amd64-64.so.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/06/15/pd-ext13_0.17.1-9_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240615;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240615=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 mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: pd-ext13
Source-Version: 0.17.1-10
Done: IOhannes m zmölnig (Debian/GNU) 

We believe that the bug you reported is fixed in the latest version of
pd-ext13, 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 1073...@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 
pd-ext13 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 17 Jun 2024 17:17:27 +0200
Source: pd-ext13
Architecture: source
Version: 0.17.1-10
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m 

Bug#1073306: marked as done (pd-bassemu: FTBFS: m_pd.h:85:26: error: static assertion failed: "field must be t_float!")

[Debian Bug Tracking System]

Your message dated Mon, 17 Jun 2024 15:36:13 +
with message-id 
and subject line Bug#1073306: fixed in pd-bassemu 0.3-12
has caused the Debian Bug report #1073306,
regarding pd-bassemu: FTBFS: m_pd.h:85:26: error: static assertion failed: 
"field must be t_float!"
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.)


-- 
1073306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073306
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-bassemu
Version: 0.3-11
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> cc -DPD -I "/usr/include/pd" -DPD_FLOATSIZE=64 -DUNIX -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIC  -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -o bassemu~.linux-amd64-64.so.o -c 
> bassemu~.c
> In file included from bassemu~.c:5:
> bassemu~.c: In function ‘bassemu_tilde_setup’:
> /usr/include/pd/m_pd.h:85:26: error: static assertion failed: "field must be 
> t_float!"
>85 | #define PD_STATIC_ASSERT _Static_assert
>   |  ^~
> /usr/include/pd/m_pd.h:575:5: note: in expansion of macro ‘PD_STATIC_ASSERT’
>   575 | PD_STATIC_ASSERT(sizeof(((type *)NULL)->field) == 
> sizeof(t_float), "field must be t_float!"); \
>   | ^~~~
> bassemu~.c:485:5: note: in expansion of macro ‘CLASS_MAINSIGNALIN’
>   485 | CLASS_MAINSIGNALIN(bassemu_class, t_bassemu, dummy);
>   | ^~
> make[1]: *** [/usr/share/pd-lib-builder//Makefile.pdlibbuilder:987: 
> bassemu~.linux-amd64-64.so.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/06/15/pd-bassemu_0.3-11_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240615;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240615=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 mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: pd-bassemu
Source-Version: 0.3-12
Done: IOhannes m zmölnig (Debian/GNU) 

We believe that the bug you reported is fixed in the latest version of
pd-bassemu, 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 1073...@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 
pd-bassemu package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 17 Jun 2024 17:05:21 +0200
Source: pd-bassemu
Architecture: source
Version: 0.3-12
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Closes: 1073306
Changes:
 pd-bassemu (0.3-12) unstable; urgency=medium
 .
   * Fix FTBFS with Pd64 (Closes: #1073306)
   * Add puredata:Provides
   * Switch to dh-sequence-puredata
   * Bump standards version to 4.7.0
Checksums-Sha1:
 38b7adc3aa00a5e293287723cbdc7252d07a7478 2112 pd-bassemu_0.3-12.dsc
 366b5b9cc36e8263c20cd76e64a3b81417ef5b17 4564 pd-bassemu_0.3-12.debian.tar.xz
Checksums-Sha256:
 886d90ef9442d18db8f820858e5c108ae2599c8656e54f5457771e18bbce8f73 2112 
pd-bassemu_0.3-12.dsc
 a7884eb2c5501b623dd1e06f8f5f3371b148e8c672475e9aa14a94c3384a87bc 4564 
pd-bassemu_0.3-12.debian.tar.xz
Files:
 a0e228dd766f8aab553f79ac360df325 2112 sound optional pd-bassemu_0.3-12.dsc
 db359b118640cfc1476921528f577aaf 4564 sound optional 
pd-bassemu_0.3-12.debian.tar.xz

Bug#1073305: marked as done (pd-iemlib: FTBFS: src/fade~.c:85:39: error: ‘COSTABSIZE’ undeclared (first use in this function))

[Debian Bug Tracking System]

Your message dated Mon, 17 Jun 2024 15:36:30 +
with message-id 
and subject line Bug#1073305: fixed in pd-iemlib 1.22.3-3
has caused the Debian Bug report #1073305,
regarding pd-iemlib: FTBFS: src/fade~.c:85:39: error: ‘COSTABSIZE’ undeclared 
(first use in this function)
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.)


-- 
1073305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073305
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-iemlib
Version: 1.22.3-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> cc -DPD -I "/usr/include/pd"  -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -Iinclude -DHAVE_G_CANVAS_H=1 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -o src/hml_shelf~.pd_linux.o -c 
> src/hml_shelf~.c
>  info: making src/iem_alisttosym.pd_linux.o in lib iemlib
> src/fade~.c: In function ‘fade_tilde_perform’:
> src/fade~.c:85:39: error: ‘COSTABSIZE’ undeclared (first use in this function)
>85 |   dphase = (double)(*in++ * (t_float)(COSTABSIZE) * 0.9) + 
> UNITBIT32;
>   |   ^~
> src/fade~.c:85:39: note: each undeclared identifier is reported only once for 
> each function it appears in
> src/fade~.c: In function ‘fade_tilde_maketable’:
> src/fade~.c:116:64: error: ‘COSTABSIZE’ undeclared (first use in this 
> function)
>   116 |   t_float *fp, phase, fff,phsinc = 0.5*3.141592653 / 
> ((t_float)COSTABSIZE*0.9);
>   |
> ^~
> make[1]: *** [/usr/share/pd-lib-builder//Makefile.pdlibbuilder:987: 
> src/fade~.pd_linux.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/06/15/pd-iemlib_1.22.3-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240615;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240615=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 mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: pd-iemlib
Source-Version: 1.22.3-3
Done: IOhannes m zmölnig (Debian/GNU) 

We believe that the bug you reported is fixed in the latest version of
pd-iemlib, 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 1073...@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 
pd-iemlib package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 17 Jun 2024 17:18:45 +0200
Source: pd-iemlib
Architecture: source
Version: 1.22.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Closes: 1073305
Changes:
 pd-iemlib (1.22.3-3) unstable; urgency=medium
 .
   * Add patch to compile against Pd>=0.55
 (Closes: #1073305)
   * Add 'Provides' stanza
   * Switch to dh-sequence-puredata
   * Update d/watch (because GitLab broke it)
   * Bump standards version to 4.7.0
Checksums-Sha1:
 4023b706ce0a3d29653fa4d40444f3b66c43c109 2170 pd-iemlib_1.22.3-3.dsc
 440429b6592d814905b860edf239198b594d4438 7420 pd-iemlib_1.22.3-3.debian.tar.xz
Checksums-Sha256:
 930ce1dc59dd8a93955d94927caa8a66f1802c5d2935d78e70f9dde4d885f7b7 2170 
pd-iemlib_1.22.3-3.dsc
 88c987e5593d1ba081317484df61d0a903abe2665f653a19321d0bcae675f1e9 7420 

Processed: Bug#1073342 marked as pending in pd-mjlib

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1073342 [src:pd-mjlib] pd-mjlib: FTBFS: m_pd.h:85:26: error: static 
assertion failed: "field must be t_float!"
Added tag(s) pending.

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

Bug#1073342: marked as pending in pd-mjlib

[IOhannes zmölnig]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/multimedia-team/pd/pd-mjlib/-/commit/8f1bbf0138429fe24367771211a37db02d35ffb6


Add patch to fix building with Pd64

Closes: #1073342


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1073342

Processed: Bug#1073333 marked as pending in pd-ggee

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #107 [src:pd-ggee] pd-ggee: FTBFS: experimental/fofsynth~.c:31:46: 
error: ‘COSTABSIZE’ undeclared (first use in this function)
Added tag(s) pending.

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

Bug#1073333: marked as pending in pd-ggee

[IOhannes zmölnig]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/multimedia-team/pd/pd-ggee/-/commit/77340b7da818c5127156a0c79a069cc12737bce8


Add patch to fix build against Pd>=0.55

Closes: #107


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/107

Bug#1073322: marked as pending in pd-ext13

[IOhannes zmölnig]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/multimedia-team/pd/pd-ext13/-/commit/62ed048c848aac968bfc2697274f834b5ca914d2


Add patch to compile against Pd>=0.55

Closes: #1073322


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1073322

Processed: Bug#1073322 marked as pending in pd-ext13

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1073322 [src:pd-ext13] pd-ext13: FTBFS: m_pd.h:85:26: error: static 
assertion failed: "field must be t_float!"
Added tag(s) pending.

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

Processed: cpython build is fixed since long

[Debian Bug Tracking System]

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

> fixed #1056832 0.8.9-1
Bug #1056832 [src:pplpy] pplpy: ftbfs with cython 3.0.x
Marked as fixed in versions pplpy/0.8.9-1.
> thanks
Stopping processing here.

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

Bug#1066202: marked as done (rubiks: FTBFS: dik/cube.c:20:9: error: implicit declaration of function ‘exit’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Mon, 17 Jun 2024 14:49:56 +
with message-id 
and subject line Bug#1066202: fixed in rubiks 20070912-7
has caused the Debian Bug report #1066202,
regarding rubiks: FTBFS: dik/cube.c:20:9: error: implicit declaration of 
function ‘exit’ [-Werror=implicit-function-declaration]
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.)


-- 
1066202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066202
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rubiks
Version: 20070912-6
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

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

This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Relevant part (hopefully):
> gcc -DPACKAGE_NAME=\"rubiks\" -DPACKAGE_TARNAME=\"rubiks\" 
> -DPACKAGE_VERSION=\"20070912\" -DPACKAGE_STRING=\"rubiks\ 20070912\" 
> -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"rubiks\" 
> -DVERSION=\"20070912\" -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -DLARGE_MEM -g 
> -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c 
> -o dik/rubiks_dikcube-phase2.o `test -f 'dik/phase2.c' || echo 
> './'`dik/phase2.c
> dik/cube.c:9:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
> 9 | main(argc, argv)
>   | ^~~~
> dik/cube.c: In function ‘main’:
> dik/cube.c:20:9: error: implicit declaration of function ‘exit’ 
> [-Werror=implicit-function-declaration]
>20 | exit(1);
>   | ^~~~
> dik/cube.c:2:1: note: include ‘’ or provide a declaration of ‘exit’
> 1 | #include "globals.h"
>   +++ |+#include 
> 2 | 
> dik/cube.c:20:9: warning: incompatible implicit declaration of built-in 
> function ‘exit’ [-Wbuiltin-declaration-mismatch]
>20 | exit(1);
>   | ^~~~
> dik/cube.c:20:9: note: include ‘’ or provide a declaration of ‘exit’
> dik/cube.c:23:13: error: implicit declaration of function ‘strcmp’ 
> [-Werror=implicit-function-declaration]
>23 | if(!strcmp(argv[1], "-t")) {
>   | ^~
> gcc -DPACKAGE_NAME=\"rubiks\" -DPACKAGE_TARNAME=\"rubiks\" 
> -DPACKAGE_VERSION=\"20070912\" -DPACKAGE_STRING=\"rubiks\ 20070912\" 
> -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"rubiks\" 
> -DVERSION=\"20070912\" -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -DLARGE_MEM -g 
> -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c 
> -o dik/rubiks_dikcube-prntsol.o `test -f 'dik/prntsol.c' || echo 
> './'`dik/prntsol.c
> dik/cube.c:2:1: note: include ‘’ or provide a declaration of 
> ‘strcmp’
> 1 | #include "globals.h"
>   +++ |+#include 
> 2 | 
> dik/cube.c:42:9: warning: incompatible implicit declaration of built-in 
> function ‘exit’ [-Wbuiltin-declaration-mismatch]
>42 | exit(1);
>   | ^~~~
> dik/cube.c:42:9: note: include ‘’ or provide a declaration of ‘exit’
> dik/cube.c:51:5: error: implicit declaration of function ‘init_phase1’ 
> [-Werror=implicit-function-declaration]
>51 | init_phase1();
>   | ^~~
> dik/permcube.c:3:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
> 3 | perm_cube()
>   | ^
> dik/cube.c:53:5: error: implicit declaration of function ‘init_phase2’ 
> [-Werror=implicit-function-declaration]
>53 | init_phase2();
>   | ^~~
> dik/cube.c:64:9: error: implicit declaration of function ‘set_cube’; did you 
> mean ‘def_cube’? [-Werror=implicit-function-declaration]
>64 | set_cube();
>   | ^~~~
>   | def_cube
> dik/cube.c:68:17: error: implicit declaration of function ‘init_phase1_cube’ 
> [-Werror=implicit-function-declaration]
>68 | do_phase1 = init_phase1_cube();
>   | ^~~~
> dik/cube.c:75:13: error: implicit declaration of function ‘phase1’ 
> [-Werror=implicit-function-declaration]
>75 | phase1(i++);
>   | ^~
> dik/cube.c:81:9: error: implicit declaration of function ‘perm_cube’; did you 
> mean ‘read_cube’? [-Werror=implicit-function-declaration]
>81 | 

Bug#1072507: marked as done (python3-google-auth-oauthlib: ships /usr/lib/python3/dist-packages/docs/conf.py)

[Debian Bug Tracking System]

Your message dated Mon, 17 Jun 2024 14:49:22 +
with message-id 
and subject line Bug#1072507: fixed in google-auth-oauthlib 1.2.0-2
has caused the Debian Bug report #1072507,
regarding python3-google-auth-oauthlib: ships 
/usr/lib/python3/dist-packages/docs/conf.py
to be marked as done.

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

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


-- 
1072507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072507
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-google-auth-oauthlib
Version: 1.2.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts fileconflict

Hi,

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

  Preparing to unpack .../python3-google-auth-oauthlib_1.2.0-1_all.deb ...
  Unpacking python3-google-auth-oauthlib (1.2.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-google-auth-oauthlib_1.2.0-1_all.deb (--unpack):
   trying to overwrite '/usr/lib/python3/dist-packages/docs/conf.py', which is 
also in package python3-specreduce 1.4.0-1
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-google-auth-oauthlib_1.2.0-1_all.deb

/usr/lib/python3/dist-packages/build/lib/docs/conf.py is an overly
generic name (and outside the package's namespace) that shouldn't be
shipped in any package.
There could be even more conflicting files.


cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: google-auth-oauthlib
Source-Version: 1.2.0-2
Done: Jochen Sprickerhof 

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated 
google-auth-oauthlib package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 17 Jun 2024 16:35:10 +0200
Source: google-auth-oauthlib
Architecture: source
Version: 1.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Jochen Sprickerhof 
Closes: 1072507
Changes:
 google-auth-oauthlib (1.2.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Drop salsa-ci.yml
   * Don't install generic docs/conf.py (Closes: #1072507)
   * Switch to autopkgtest-pkg-pybuild
Checksums-Sha1:
 132fce29a5df633adadc478d863158cbd02847da 2409 google-auth-oauthlib_1.2.0-2.dsc
 aaf246faec1f2a30c53563259bf5813aca5d28fe 2584 
google-auth-oauthlib_1.2.0-2.debian.tar.xz
Checksums-Sha256:
 3642bc8381029b50f93b3b021b5d8a9d298545fca341bc6ed0a73d00849b50bf 2409 
google-auth-oauthlib_1.2.0-2.dsc
 891eedb66c7ce5a64f31bf50ddf28242ee725a80312165852bd92b1cd2dfe653 2584 
google-auth-oauthlib_1.2.0-2.debian.tar.xz
Files:
 fe77c8da1d2067f2a764e6a4137f3808 2409 python optional 
google-auth-oauthlib_1.2.0-2.dsc
 a32e8bae0bfdc08845758fc6a5ab6384 2584 python optional 
google-auth-oauthlib_1.2.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAmZwSn0ACgkQW//cwljm
lDME7Q/+Ooebren0MZnzmahIFQsMB6NRpIOcETFw1hTcjTHmy0uVC1tEj98wLFrk
2aOSyiD8/V+got5GIkNPhwHr6SPiFGJhQu5W9Ax9FXMYV83Rc1bmwrhJPOt5aSNd
QJCtwag72Vnu672f7P5TckBwLc0Kvd+eMkCboSPb69GUB28aGsreJ4EFZgPFverU
iFowHy2YVOdMa/C6EOV96N9iWPsAkXMgxnt81C7LYyEDlmRei+EYtDOClzhhGg1w
XA6gpYKFqxdT2IuOX7yXpOFjAnhfvHSX9UkF8B49KSGfzMIZVwhb95MlId6oGFn8
6dNU7q5H/LcMkCxZkGRjwM/CvUMs3pqiu65vy9mNrOtgr7gr57ZbDfU7PDWCx5Ot
OJiGUOrrTeYGT2Ray0yKlG+kbzuChGnWYLXQd72GJf7XKI8RMztz2wgqBLZjBUPF
XBwZAPVDXb1lezWZuhgsOUWoO3jMX8zj15H2/5fXfQG3iN2dybfEGNGqq/x0knUH
eKQ0eU0jLTGpjd9x91Hx4kqqAlPjzuh/OP3poH024W99dYUk9LNS+JPj/5ipkVbL
8964mrPdAXXoEqLa3ozE/PQKAi7XoH3fEL2l4kwhy1iSQ+YOtDTPAqdwHTp/V1x3
VZgUITJ/DgWaAuEd/hmFRVH2Jd+rp/DZP+0j1gZGu7MHiJ1o0BQ=
=N0HW
-END PGP SIGNATURE-



pgpEuaN8qoPz3.pgp
Description: PGP signature
--- End Message ---

Bug#1072366: marked as done (libndp: CVE-2024-5564)

[Debian Bug Tracking System]

Your message dated Mon, 17 Jun 2024 14:47:08 +
with message-id 
and subject line Bug#1072366: fixed in libndp 1.8-1+deb12u1
has caused the Debian Bug report #1072366,
regarding libndp: CVE-2024-5564
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.)


-- 
1072366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libndp
Version: 1.8-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 1.6-1

Hi,

The following vulnerability was published for libndp.

CVE-2024-5564[0]:
| A vulnerability was found in libndp. This flaw allows a local
| malicious user to cause a buffer overflow in NetworkManager,
| triggered by sending a malformed IPv6 router advertisement packet.
| This issue occurred as libndp was not correctly validating the route
| length information.


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

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libndp
Source-Version: 1.8-1+deb12u1
Done: Florian Ernst 

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

Debian distribution maintenance software
pp.
Florian Ernst  (supplier of updated libndp 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, 11 Jun 2024 07:34:43 +0200
Source: libndp
Architecture: source
Version: 1.8-1+deb12u1
Distribution: bookworm-security
Urgency: medium
Maintainer: Florian Ernst 
Changed-By: Florian Ernst 
Closes: 1072366
Changes:
 libndp (1.8-1+deb12u1) bookworm-security; urgency=medium
 .
   * add debian/patches/CVE-2024-5564.patch from upstream fixing CVE-2024-5564
 (Closes: #1072366)
   * d/gbp.conf: update for bookworm release
Checksums-Sha1:
 446762f3367fdcf36a71d0aedc04f2df6350a364 2061 libndp_1.8-1+deb12u1.dsc
 c3a63a27574a0af9a893a395a4916314bb596292 364669 libndp_1.8.orig.tar.gz
 4b3b4dfae0e340afe117ad659d5e47e364f17cf3 5192 
libndp_1.8-1+deb12u1.debian.tar.xz
 815c0b19a5632d30477089799e5d1805c050346c 7322 
libndp_1.8-1+deb12u1_amd64.buildinfo
Checksums-Sha256:
 f1d8c3e91963b63f22aec4371f5e676b8e090f2121fec6b76b3b303cb11d0d3b 2061 
libndp_1.8-1+deb12u1.dsc
 88ffb66ee2eb527f146f5c02f5ccbc38ba97d2b0d57eb46bfba488821ab0c02b 364669 
libndp_1.8.orig.tar.gz
 53ebb65352b36045d9c1d08e3b0f6c7d66172841a2e1cdeb8c680fd4103aeeaa 5192 
libndp_1.8-1+deb12u1.debian.tar.xz
 6722ed3bb70429d15201e7ce62f99c396f4788c72ab129336afc3ddcd6649e70 7322 
libndp_1.8-1+deb12u1_amd64.buildinfo
Files:
 6fa37bd8eddbdf367cd92529191d4bb1 2061 net optional libndp_1.8-1+deb12u1.dsc
 c7e775fd5a9d676e8cba9c3732c4df93 364669 net optional libndp_1.8.orig.tar.gz
 24cf4541d88a0e3f58782492364328c5 5192 net optional 
libndp_1.8-1+deb12u1.debian.tar.xz
 725e28cf046baeafe5fecb68848c2f89 7322 net optional 
libndp_1.8-1+deb12u1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEBn03XtJwVyplJ26xBjdBuvXdHs4FAmZn6EcACgkQBjdBuvXd
Hs6t3hAAlEuBGh8fD9DJ7/CQGhGRRx23I15Prbo5MhAOh3VJd9xBJs/qFM4O7oMw
QftS064MMw3K5BDZkGZhFGS9zmxcN970aNLLPwK38HFDFaJke7hAtrYF6CpyU4d1
SCyCabq3tWMmQhj819oMz4AgUH3a+2uiE9rTPiZ2q8wVQB2Se8bBUr6vep7FrfC3
9Mi1AfB2li82yg6P8M666SgYfo8gsgsl4W5S4Jn+d0qj0SV+JeTmyWgu/ZwdccTB
zsurOI72DEDW2XU9Qvg135blsX+TuIMaCg23gfNnOFgBI9a2XxTjrMo2hkR6WFKe
N8lZAO4SDmFPY9gPgnMMZ61PixVkCN/wRbdtc+xcNDN6IiPvmFV7i7xK4wrd1FPN
2vDq7S+b1GFMWCHQH1N6CszmVqAZpseM4k7p/Ywgvdgr9mS2pwFVUBfkNkrvfJx8
5GH/gFJ4jlG33raFLd8qqTYVTbxmqSAN1ZMJZSiZs/ZllcXMpvM/LqHS4+jTgVE2
BD46yp5+IKI2TVbbLsH7UgAnd6CRpyxJYMBPEGu+MUclyesobRqSUjTTzDfw1Q8c
Bw4CHfZXo+ksqVZZ6hCs2zQ9axS3s6yfvKQAWnrVyoVgYUJyly3UnS0wNkehznEf
DKfGM7mhvDHtyqIrTesakOcU9qLL1qszkwgUNlp/gESn1TD0cMU=
=Z5He
-END PGP SIGNATURE-



pgprdNBraBTEG.pgp
Description: PGP signature

Bug#1072366: marked as done (libndp: CVE-2024-5564)

[Debian Bug Tracking System]

Your message dated Mon, 17 Jun 2024 14:47:38 +
with message-id 
and subject line Bug#1072366: fixed in libndp 1.6-1+deb11u1
has caused the Debian Bug report #1072366,
regarding libndp: CVE-2024-5564
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.)


-- 
1072366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libndp
Version: 1.8-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 1.6-1

Hi,

The following vulnerability was published for libndp.

CVE-2024-5564[0]:
| A vulnerability was found in libndp. This flaw allows a local
| malicious user to cause a buffer overflow in NetworkManager,
| triggered by sending a malformed IPv6 router advertisement packet.
| This issue occurred as libndp was not correctly validating the route
| length information.


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

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libndp
Source-Version: 1.6-1+deb11u1
Done: Florian Ernst 

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

Debian distribution maintenance software
pp.
Florian Ernst  (supplier of updated libndp 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, 11 Jun 2024 07:38:05 +0200
Source: libndp
Architecture: source
Version: 1.6-1+deb11u1
Distribution: bullseye-security
Urgency: medium
Maintainer: Andrew Ayer 
Changed-By: Florian Ernst 
Closes: 1072366
Changes:
 libndp (1.6-1+deb11u1) bullseye-security; urgency=medium
 .
   * add debian/patches/CVE-2024-5564.patch from upstream fixing CVE-2024-5564
 (Closes: #1072366)
   * d/gbp.conf: update for bullseye release
Checksums-Sha1:
 0ee6b3fc099d2dae3289b5abe34babe432b91391 2083 libndp_1.6-1+deb11u1.dsc
 300e63fcf69f6239dc6c5f82770437d5ffbc2dd4 364406 libndp_1.6.orig.tar.gz
 936afe9993b64c40a49c8bcf0c3d6403f1da926e 3956 
libndp_1.6-1+deb11u1.debian.tar.xz
 5fd90b0748e90459e7e94585362467447918ca88 7029 
libndp_1.6-1+deb11u1_amd64.buildinfo
Checksums-Sha256:
 7533ca6807defe92e09e60292236dd85affef10b63162c6be481e0202f591676 2083 
libndp_1.6-1+deb11u1.dsc
 0c7dfa84e013bd5e569ef2c6292a6f72cfaf14f4ff77a77425e52edc33ffac0e 364406 
libndp_1.6.orig.tar.gz
 424c67ad49cd27f71e1e534bf68fb3e17d0cc7f80f0dc415979c0e98e1bca1e3 3956 
libndp_1.6-1+deb11u1.debian.tar.xz
 9736c33929ba93caa98ed2bba537bdba40a505b49e801d24c2c20a3e3a3811c6 7029 
libndp_1.6-1+deb11u1_amd64.buildinfo
Files:
 bc6658ac4567b8b37c5dd617d5c441b4 2083 net optional libndp_1.6-1+deb11u1.dsc
 1e54d26bcb4a4110bc3f90c5dd04f1a7 364406 net optional libndp_1.6.orig.tar.gz
 65d454bbcb8b5990c41b4350c0eceda9 3956 net optional 
libndp_1.6-1+deb11u1.debian.tar.xz
 4f857f8c23544e3a4fb6a24b8e29bc00 7029 net optional 
libndp_1.6-1+deb11u1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEBn03XtJwVyplJ26xBjdBuvXdHs4FAmZn6D0ACgkQBjdBuvXd
Hs7OkBAArYvlWcfIAi9NdLU6mAM3JUO7v3fsETpsKv/7VP2oDZ7d/7mfERdPT2Zj
Xt+jiMW3Qxrabj/ISGNS1XFrv5cb0lua21Z1YadEpYZtb9FV7etwprT4rj4qb9E7
8R1i9klq9Wi03tMNKUt3EsXcrA1lMqqlzoTzM1qN0pxG5aVI3uUfQ4n/T5XMhm8X
L4bQdp3y8V+M3rTJpcIIGwVZfyI6kGnQ99KZYgc8ApmU+O9wrB7BzxzeqDgU3PIv
pGSTr6HHI2nBlfL+hHtuwcU7aFZUkgELb/yBZK6j/X0tUGOnLMEFdiutV/Y7QXex
cRW21urSOXGx6UQyGLtLKPrhbefyO0GEb9NnUpYgLoK7YAUc1Cn3BHWC+q9XKWHf
2JKH/z5flw48Tw3oWfP9V29D5I+SgPEGFb+yrOSLUxHC3SKi6kC4zEaB3bbUeU79
vBuJ352loMgUbgFP2J+Hy/7gcUBkB52sYFN3zY2vT02tzgB3qoK13ZuHyVTX2wGo
ZpYOVbJqbsFBCHaIrl5s3QFNrGTGtLbjB8hB3vMiQVV8qgfl2OBMowG8InxNIzRN
vNgqEUJg7rxyfevL4WZNsySvYsbN3cQ/nkwJp5dbZQJ0MgnsP8hiI6eExr7uYpIJ
TSoArcVXX1RfCrM/j96nfoF9wrZb4GVXQJa8NVX/wlyH69G8+LU=
=tNbW
-END PGP SIGNATURE-



pgpT9Bj8V9tSZ.pgp
Description: PGP signature
--- 

Bug#1072507: marked as pending in google-auth-oauthlib

[Jochen Sprickerhof]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/google-auth-oauthlib/-/commit/38a7a57b066efd6fd49c1cc0e5109fed297e47b0


Don't install generic docs/conf.py

Closes: #1072507


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1072507

Processed: Bug#1072507 marked as pending in google-auth-oauthlib

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1072507 [python3-google-auth-oauthlib] python3-google-auth-oauthlib: ships 
/usr/lib/python3/dist-packages/docs/conf.py
Added tag(s) pending.

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

Bug#1073508: libxml2: just another API+ABI break; please bump soname

[Thorsten Glaser]

On Mon, 17 Jun 2024, Aron Xu wrote:

>Control: tags -1 - pending

Oops, right.

>It looks that this libxml2 update is causing more troubles than
>expected, I would like to ask for your opinion whether it's better to
>revert to an older version for the moment?

Might be useful while you ask upstream what they’re doing there
with regards to both API and ABI, and/or someone diffs the API
and ABI surface of the old and new version and figures out whether
there are any other such surprises. Security fixes might need
backporting though.

Maybe they haven’t realised themselves and decide they need to
bump to libxml3 upstream at some point.

bye,
//mirabilos
-- 
Infrastrukturexperte • Qvest Digital AG
Am Dickobskreuz 10, D-53121 Bonn • https://www.qvest-digital.com/
Telephon +49 228 54881-393 • Fax: +49 228 54881-235
HRB AG Bonn 18196 • USt-ID (VAT): DE274355441
Vorstand: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
Vorsitzender Aufsichtsrat: Peter Nöthen

Bug#1073343: marked as done (pd-cyclone: FTBFS: m_pd.h:85:26: error: static assertion failed: "field must be t_float!")

[Debian Bug Tracking System]

Your message dated Mon, 17 Jun 2024 14:34:21 +
with message-id 
and subject line Bug#1073343: fixed in pd-cyclone 0.8.1+ds-2
has caused the Debian Bug report #1073343,
regarding pd-cyclone: FTBFS: m_pd.h:85:26: error: static assertion failed: 
"field must be t_float!"
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.)


-- 
1073343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-cyclone
Version: 0.8.1+ds-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> cc -DPD -I "/usr/include/pd" -DPD_FLOATSIZE=64 -DUNIX -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIC -Ishared -DHAVE_STRUCT_TIMESPEC -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o 
> cyclone_objects/binaries/audio/sampstoms.linux-amd64-64.so.o -c 
> cyclone_objects/binaries/audio/sampstoms.c
>  info: making cyclone_objects/binaries/control/append.linux-amd64-64.so.o 
> in lib cyclone
> In file included from cyclone_objects/binaries/audio/sampstoms.c:5:
> cyclone_objects/binaries/audio/sampstoms.c: In function 
> ‘sampstoms_tilde_setup’:
> /usr/include/pd/m_pd.h:85:26: error: static assertion failed: "field must be 
> t_float!"
>85 | #define PD_STATIC_ASSERT _Static_assert
>   |  ^~
> /usr/include/pd/m_pd.h:575:5: note: in expansion of macro ‘PD_STATIC_ASSERT’
>   575 | PD_STATIC_ASSERT(sizeof(((type *)NULL)->field) == 
> sizeof(t_float), "field must be t_float!"); \
>   | ^~~~
> cyclone_objects/binaries/audio/sampstoms.c:59:5: note: in expansion of macro 
> ‘CLASS_MAINSIGNALIN’
>59 | CLASS_MAINSIGNALIN(sampstoms_class, t_sampstoms, x_f);
>   | ^~
> make[1]: *** [/usr/share/pd-lib-builder//Makefile.pdlibbuilder:987: 
> cyclone_objects/binaries/audio/sampstoms.linux-amd64-64.so.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/06/15/pd-cyclone_0.8.1+ds-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240615;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240615=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 mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: pd-cyclone
Source-Version: 0.8.1+ds-2
Done: IOhannes m zmölnig (Debian/GNU) 

We believe that the bug you reported is fixed in the latest version of
pd-cyclone, 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 1073...@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 
pd-cyclone package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 17 Jun 2024 15:43:38 +0200
Source: pd-cyclone
Architecture: source
Version: 0.8.1+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Closes: 1073343
Changes:
 pd-cyclone (0.8.1+ds-2) unstable; urgency=medium
 .
   * Fix struct member types for Pd64 (Closes: #1073343)
   * Switch to dh-sequence-puredata
   * Add puredata:Provides
Checksums-Sha1:
 26062e338cebb0fd3f33fed7ab1c52633e218a5e 2182 pd-cyclone_0.8.1+ds-2.dsc
 dd96c5fd2873ac01a6441b9086f1a61d06b595da 9780 
pd-cyclone_0.8.1+ds-2.debian.tar.xz
Checksums-Sha256:
 

Bug#1073314: marked as done (yaz: FTBFS: xmlquery.c:56:23: error: implicit declaration of function ‘atoi’; did you mean ‘atoi_n’? [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Mon, 17 Jun 2024 14:28:49 +
with message-id 
and subject line Bug#1073314: fixed in yaz 5.34.0-2
has caused the Debian Bug report #1073314,
regarding yaz: FTBFS: xmlquery.c:56:23: error: implicit declaration of function 
‘atoi’; did you mean ‘atoi_n’? [-Werror=implicit-function-declaration]
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.)


-- 
1073314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073314
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yaz
Version: 5.34.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.  
> -I/usr/include/libxml2  -I/usr/include/p11-kit-1  -Wdate-time 
> -D_FORTIFY_SOURCE=2  -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection  -c 
> -o tokenizer.lo tokenizer.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I/usr/include/libxml2 
> -I/usr/include/p11-kit-1 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -c http.c  -fPIC -DPIC -o .libs/http.o
> xmlquery.c: In function ‘check_diagnostic’:
> xmlquery.c:56:23: error: implicit declaration of function ‘atoi’; did you 
> mean ‘atoi_n’? [-Werror=implicit-function-declaration]
>56 | *error_code = atoi(code_str);
>   |   ^~~~
>   |   atoi_n
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.  
> -I/usr/include/libxml2  -I/usr/include/p11-kit-1  -Wdate-time 
> -D_FORTIFY_SOURCE=2  -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection  -c 
> -o record_conv.lo record_conv.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I/usr/include/libxml2 
> -I/usr/include/p11-kit-1 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -c mime.c  -fPIC -DPIC -o .libs/mime.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I/usr/include/libxml2 
> -I/usr/include/p11-kit-1 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -c oid_util.c  -fPIC -DPIC -o 
> .libs/oid_util.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I/usr/include/libxml2 
> -I/usr/include/p11-kit-1 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -c tokenizer.c  -fPIC -DPIC -o 
> .libs/tokenizer.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I/usr/include/libxml2 
> -I/usr/include/p11-kit-1 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -c xmlerror.c -o xmlerror.o 
> >/dev/null 2>&1
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I/usr/include/libxml2 
> -I/usr/include/p11-kit-1 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -c mime.c -o mime.o >/dev/null 2>&1
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I/usr/include/libxml2 
> -I/usr/include/p11-kit-1 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -c record_conv.c  -fPIC -DPIC -o 
> .libs/record_conv.o
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.  
> -I/usr/include/libxml2  -I/usr/include/p11-kit-1  -Wdate-time 
> -D_FORTIFY_SOURCE=2  -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat 

Bug#1073368: marked as done (python-flickrapi: FTBFS: ModuleNotFoundError: No module named 'six')

[Debian Bug Tracking System]

Your message dated Mon, 17 Jun 2024 14:27:40 +
with message-id 
and subject line Bug#1073368: fixed in python-flickrapi 2.4-0.1
has caused the Debian Bug report #1073368,
regarding python-flickrapi: FTBFS: ModuleNotFoundError: No module named 'six'
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.)


-- 
1073368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073368
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-flickrapi
Version: 2.1.2-5.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
> (level 9 in use)
> I: pybuild base:311: python3.12 setup.py config 
> running config
> I: pybuild base:311: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
> I: pybuild base:311: /usr/bin/python3.12 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.12_flickrapi/build/flickrapi
> copying flickrapi/auth.py -> 
> /<>/.pybuild/cpython3_3.12_flickrapi/build/flickrapi
> copying flickrapi/tokencache.py -> 
> /<>/.pybuild/cpython3_3.12_flickrapi/build/flickrapi
> copying flickrapi/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_flickrapi/build/flickrapi
> copying flickrapi/sockutil.py -> 
> /<>/.pybuild/cpython3_3.12_flickrapi/build/flickrapi
> copying flickrapi/xmlnode.py -> 
> /<>/.pybuild/cpython3_3.12_flickrapi/build/flickrapi
> copying flickrapi/shorturl.py -> 
> /<>/.pybuild/cpython3_3.12_flickrapi/build/flickrapi
> copying flickrapi/exceptions.py -> 
> /<>/.pybuild/cpython3_3.12_flickrapi/build/flickrapi
> copying flickrapi/call_builder.py -> 
> /<>/.pybuild/cpython3_3.12_flickrapi/build/flickrapi
> copying flickrapi/html.py -> 
> /<>/.pybuild/cpython3_3.12_flickrapi/build/flickrapi
> copying flickrapi/core.py -> 
> /<>/.pybuild/cpython3_3.12_flickrapi/build/flickrapi
> copying flickrapi/cache.py -> 
> /<>/.pybuild/cpython3_3.12_flickrapi/build/flickrapi
> copying flickrapi/contrib.py -> 
> /<>/.pybuild/cpython3_3.12_flickrapi/build/flickrapi
> I: pybuild base:311: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_flickrapi/build/flickrapi
> copying flickrapi/auth.py -> 
> /<>/.pybuild/cpython3_3.11_flickrapi/build/flickrapi
> copying flickrapi/tokencache.py -> 
> /<>/.pybuild/cpython3_3.11_flickrapi/build/flickrapi
> copying flickrapi/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_flickrapi/build/flickrapi
> copying flickrapi/sockutil.py -> 
> /<>/.pybuild/cpython3_3.11_flickrapi/build/flickrapi
> copying flickrapi/xmlnode.py -> 
> /<>/.pybuild/cpython3_3.11_flickrapi/build/flickrapi
> copying flickrapi/shorturl.py -> 
> /<>/.pybuild/cpython3_3.11_flickrapi/build/flickrapi
> copying flickrapi/exceptions.py -> 
> /<>/.pybuild/cpython3_3.11_flickrapi/build/flickrapi
> copying flickrapi/call_builder.py -> 
> /<>/.pybuild/cpython3_3.11_flickrapi/build/flickrapi
> copying flickrapi/html.py -> 
> /<>/.pybuild/cpython3_3.11_flickrapi/build/flickrapi
> copying flickrapi/core.py -> 
> /<>/.pybuild/cpython3_3.11_flickrapi/build/flickrapi
> copying flickrapi/cache.py -> 
> /<>/.pybuild/cpython3_3.11_flickrapi/build/flickrapi
> copying flickrapi/contrib.py -> 
> /<>/.pybuild/cpython3_3.11_flickrapi/build/flickrapi
>dh_auto_test -O--buildsystem=pybuild
> dh_auto_test: warning: Compatibility levels before 10 are deprecated (level 9 
> in use)
> I: pybuild base:311: cd 
> /<>/.pybuild/cpython3_3.12_flickrapi/build; python3.12 -m nose 
> -v 
> Failure: ModuleNotFoundError (No module named 'six') ... ERROR
> /usr/lib/python3.12/unittest/case.py:580: RuntimeWarning: TestResult has no 
> addDuration method
>   warnings.warn("TestResult has no addDuration method",
> 
> ==
> ERROR: Failure: ModuleNotFoundError (No module named 'six')
> --
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/nose/failure.py", line 39, in 

Bug#1073434: marked as done (bmap-tools: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Mon, 17 Jun 2024 14:23:30 +
with message-id 
and subject line Bug#1073434: fixed in bmap-tools 3.8.0-1
has caused the Debian Bug report #1073434,
regarding bmap-tools: FTBFS: dh_auto_test: error: pybuild --test --test-pytest 
-i python{version} -p 3.11 returned exit code 13
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.)


-- 
1073434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073434
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bmap-tools
Version: 3.7-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:129: Building wheel for python3.11 with "build" 
> module
> I: pybuild base:311: python3.11 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.11  
> * Building wheel...
> Successfully built bmaptools-3.7.0-py3-none-any.whl
> I: pybuild plugin_pyproject:144: Unpacking wheel built for python3.11 with 
> "installer" module
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:311: cd /<>/.pybuild/cpython3_3.11/build; 
> python3.11 -m pytest tests
> = test session starts 
> ==
> platform linux -- Python 3.11.9, pytest-8.2.2, pluggy-1.5.0
> rootdir: /<>/.pybuild/cpython3_3.11/build
> configfile: pyproject.toml
> collected 19 items
> 
> tests/test_CLI.py ..F..  [ 
> 26%]
> tests/test_api_base.py . [ 
> 31%]
> tests/test_bmap_helpers.py ...   [ 
> 89%]
> tests/test_compat.py .   [ 
> 94%]
> tests/test_filemap.py .  
> [100%]
> 
> === FAILURES 
> ===
> _ TestCLI.test_valid_signature 
> _
> 
> self = 
> 
> def test_valid_signature(self):
> completed_process = subprocess.run(
> [
> "bmaptool",
> "copy",
> "--bmap",
> "tests/test-data/test.image.bmap.v2.0",
> "--bmap-sig",
> "tests/test-data/signatures/test.image.bmap.v2.0.valid-sig",
> "tests/test-data/test.image.gz",
> self.tmpfile,
> ],
> stdout=subprocess.PIPE,
> stderr=subprocess.STDOUT,
> check=False,
> )
> >   self.assertEqual(completed_process.returncode, 0, 
> > completed_process.stdout)
> E   AssertionError: 1 != 0 : b'bmaptool: \x1b[91mERROR\x1b[0m: An error 
> occurred, here is the traceback:\nTraceback (most recent call last):\n  File 
> "/<>/.pybuild/cpython3_3.11/build/bmaptools/CLI.py", line 214, 
> in verify_detached_bmap_signature\nsigs = context.verify(signed_data, 
> signature, None)[1].signatures\n   
> \n  File 
> "/usr/lib/python3/dist-packages/gpg/core.py", line 558, in verify\nraise 
> errors.BadSignatures(results[1], results=results)\n\nbmaptool: 
> \x1b[91mERROR\x1b[0m: discovered a BAD GPG signature: 
> tests/test-data/signatures/test.image.bmap.v2.0.valid-sig\n\n\n'
> 
> tests/test_CLI.py:43: AssertionError
> === short test summary info 
> 
> FAILED tests/test_CLI.py::TestCLI::test_valid_signature - AssertionError: 1 
> !...
> === 1 failed, 18 passed in 87.41s (0:01:27) 
> 
> E: pybuild pybuild:389: test: plugin pyproject failed with: exit code=1: cd 
> /<>/.pybuild/cpython3_3.11/build; python3.11 -m pytest tests
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 
> returned exit code 13


The full build log is available from:
http://qa-logs.debian.net/2024/06/15/bmap-tools_3.7-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240615;users=lu...@debian.org
or:

Bug#1073561: openbabel: FTBFS: failing tests test_tautomer_2[27]

[Andrius Merkys]

Source: openbabel
Version: 3.1.1+dfsg-9
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs

Hi,

openbabel FTBFS both in unstable (if a fix for #1073327 is applied) and 
testing with the following:


99% tests passed, 2 tests failed out of 229

Total Test time (real) = 317.34 sec

The following tests FAILED:
149 - test_tautomer_22 (Subprocess aborted)
154 - test_tautomer_27 (Subprocess aborted)
Errors while running CTest

It is not clear when the FTBFS first started happening as these tests do 
not seem to be covered by openbabel's autopkgtest.


Andrius

Bug#1073560: Reverting "xshared: Print protocol numbers if --numeric was given" breaks firewalld autopkgtest

[Michael Biebl]

Source: iptables
Version: 1.8.10-4
Severity: serious


The cherry-pick of the commit 34f085b1607364f4eaded1140060dcaf965a2649
Revert "xshared: Print protocol numbers if --numeric was given"
breaks firewalld, as seen in
https://ci.debian.net/packages/f/firewalld/testing/amd64/47810213/

firewalld is very susceptible to changes of the output and command line
interface of iptables.
See an older issue https://github.com/firewalld/firewalld/issues/1112

Filing with RC severity, so the package doesn't migrate to testing (the
debci results should prevent that, but this is just to make doubly sure)

This change of iptables afaics has landed in a stable release
(bookworm). Do we really want to revert it again and make all users of
--numeric have to update again?


Regards,
Michael


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

Kernel: Linux 6.8.12-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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

Processed: Bug#1073343 marked as pending in pd-cyclone

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1073343 [src:pd-cyclone] pd-cyclone: FTBFS: m_pd.h:85:26: error: static 
assertion failed: "field must be t_float!"
Added tag(s) pending.

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

Bug#1073327: [Debichem-devel] Bug#1073327: openbabel: FTBFS: xml.cpp:245:39: error: invalid conversion from ‘const xmlError*’ {aka ‘const _xmlError*’} to ‘xmlError*’ {aka ‘_xmlError*’} [-fpermissive]

[Andrius Merkys]

Hello,

On 2024-06-16 15:48, Lucas Nussbaum wrote:

/<>/src/formats/xml/xml.cpp:245:39: error:
invalid conversion from ‘const xmlError*’ {aka ‘const _xmlError*’} to
‘xmlError*’ {aka ‘_xmlError*’} [-fpermissive]
   245 |   xmlError* perr = xmlGetLastError();
   |~~~^~
   |   |
   |   const xmlError* {aka const 
_xmlError*}


This is caused by libxml2 update to version 2.12.7 in unstable. It could 
be fixed by the patch suggested above and removal of 
'xmlResetError(perr);' line slightly below in the same source file. 
However, openbabel FTBFS both in unstable and testing due to some other 
bug which is not yet reported:


99% tests passed, 2 tests failed out of 229

Total Test time (real) = 317.34 sec

The following tests FAILED:
149 - test_tautomer_22 (Subprocess aborted)
154 - test_tautomer_27 (Subprocess aborted)

I have not yet checked whether the solution I described above does not 
leave unfreed memory.


Andrius

Bug#1073343: marked as pending in pd-cyclone

[IOhannes zmölnig]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/multimedia-team/pd/pd-cyclone/-/commit/ed90613575b6de87272e1bec968bcbbde4ee4920


Fix struct member types for Pd64

Closes: #1073343


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1073343

Bug#1052788: python-asyncssh: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.11 --system=custom "--test-args={interpreter} -m unittest discover -v" returned exit code 13

[Helmut Grohne]

On Thu, Nov 16, 2023 at 07:50:26PM +, Dale Richards wrote:
> Builds fine for me on sid as of 2023-11-16. Build log and diff attached.

Fails for me. Here is the relevant part from the log:

| ==
| ERROR: test_connect_timeout_exceeded 
(tests.test_connection._TestConnection.test_connect_timeout_exceeded)
| Test connect timeout exceeded
| --
| Traceback (most recent call last):
|   File "/usr/lib/python3.11/unittest/mock.py", line 1378, in patched
| return func(*newargs, **newkeywargs)
|^
|   File "/<>/tests/util.py", line 81, in async_wrapper
| return self.loop.run_until_complete(coro(self, *args, **kwargs))
|^
|   File "/usr/lib/python3.11/asyncio/base_events.py", line 654, in 
run_until_complete
| return future.result()
|^^^
|   File "/<>/tests/test_connection.py", line 430, in 
test_connect_timeout_exceeded
| await asyncssh.connect('223.255.255.254', connect_timeout=1)
|   File "/<>/asyncssh/connection.py", line 7707, in connect
| return await asyncio.wait_for(
|^^^
|   File "/usr/lib/python3.11/asyncio/tasks.py", line 489, in wait_for
| return fut.result()
|
|   File "/<>/asyncssh/connection.py", line 430, in _connect
| _, session = await loop.create_connection(
|  ^
|   File "/usr/lib/python3.11/asyncio/base_events.py", line 1086, in 
create_connection
| raise exceptions[0]
|   File "/usr/lib/python3.11/asyncio/base_events.py", line 1070, in 
create_connection
| sock = await self._connect_sock(
|^
|   File "/usr/lib/python3.11/asyncio/base_events.py", line 974, in 
_connect_sock
| await self.sock_connect(sock, address)
|   File "/usr/lib/python3.11/asyncio/selector_events.py", line 638, in 
sock_connect
| return await fut
|^
|   File "/usr/lib/python3.11/asyncio/selector_events.py", line 678, in 
_sock_connect_cb
| raise OSError(err, f'Connect call failed {address}')
| OSError: [Errno 101] Connect call failed ('223.255.255.254', 22)
| 
| ==
| ERROR: test_connect_timeout_exceeded_string 
(tests.test_connection._TestConnection.test_connect_timeout_exceeded_string)
| Test connect timeout exceeded with string value
| --
| Traceback (most recent call last):
|   File "/usr/lib/python3.11/unittest/mock.py", line 1378, in patched
| return func(*newargs, **newkeywargs)
|^
|   File "/<>/tests/util.py", line 81, in async_wrapper
| return self.loop.run_until_complete(coro(self, *args, **kwargs))
|^
|   File "/usr/lib/python3.11/asyncio/base_events.py", line 654, in 
run_until_complete
| return future.result()
|^^^
|   File "/<>/tests/test_connection.py", line 440, in 
test_connect_timeout_exceeded_string
| await asyncssh.connect('223.255.255.254', connect_timeout='0m1s')
|   File "/<>/asyncssh/connection.py", line 7707, in connect
| return await asyncio.wait_for(
|^^^
|   File "/usr/lib/python3.11/asyncio/tasks.py", line 489, in wait_for
| return fut.result()
|
|   File "/<>/asyncssh/connection.py", line 430, in _connect
| _, session = await loop.create_connection(
|  ^
|   File "/usr/lib/python3.11/asyncio/base_events.py", line 1086, in 
create_connection
| raise exceptions[0]
|   File "/usr/lib/python3.11/asyncio/base_events.py", line 1070, in 
create_connection
| sock = await self._connect_sock(
|^
|   File "/usr/lib/python3.11/asyncio/base_events.py", line 974, in 
_connect_sock
| await self.sock_connect(sock, address)
|   File "/usr/lib/python3.11/asyncio/selector_events.py", line 638, in 
sock_connect
| return await fut
|^
|   File "/usr/lib/python3.11/asyncio/selector_events.py", line 678, in 
_sock_connect_cb
| raise OSError(err, f'Connect call failed {address}')
| OSError: [Errno 101] Connect call failed ('223.255.255.254', 22)
| 
| ==
| ERROR: test_connect_timeout_exceeded_tunnel 
(tests.test_connection._TestConnection.test_connect_timeout_exceeded_tunnel)
| Test connect timeout exceeded
| --
| Traceback (most recent call last):
|   File "/usr/lib/python3.11/unittest/mock.py", line 1378, in patched
| return func(*newargs, **newkeywargs)

Bug#1073557: python3-motor: Fails to import and crashes the entire program

[Salvo "LtWorf" Tomaselli]

Package: python3-motor
Version: 2.3.0-3
Severity: grave
Tags: upstream
Justification: renders package unusable
X-Debbugs-Cc: ltw...@debian.org

Dear Maintainer,

the package no longer works.


import motor.motor_asyncio

ModuleNotFoundError: No module named 'pymongo.mongo_replica_set_client'

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

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

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


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

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

Versions of packages python3-motor depends on:
ii  python3  3.11.8-1
ii  python3-gridfs   4.7.3-1
ii  python3-pymongo  4.7.3-1

python3-motor recommends no packages.

Versions of packages python3-motor suggests:
ii  python3-aiohttp  3.9.5-1
ii  python3-tornado  6.4.1-1

-- no debconf information

Processed: block 1070411 with 1073549

[Debian Bug Tracking System]

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

> block 1070411 with 1073549
Bug #1070411 {Done: Reinhard Tartler } [src:containerd] 
containerd fails to build as a normal user due to sysctl
1070411 was not blocked by any bugs.
1070411 was not blocking any bugs.
Added blocking bug(s) of 1070411: 1073549
> thanks
Stopping processing here.

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

Processed: (No Subject)

[Debian Bug Tracking System]

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

> reopen 1063645 =
Bug #1063645 {Done: Victor Seva } 
[src:markdown] markdown: missing required debian/rules targets build-arch 
and/or build-indep
Bug reopened
Ignoring request to alter fixed versions of bug #1063645 to the same values 
previously set
> --
Stopping processing here.

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

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

[Debian Bug Tracking System]

Your message dated Mon, 17 Jun 2024 11:50:04 +
with message-id <14e20533-5966-45f6-b791-480a1fa84...@torreviejawireless.org>
and subject line (No Subject)
has caused the Debian Bug report #1063645,
regarding markdown: missing required debian/rules targets build-arch and/or 
build-indep
to be marked as done.

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

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


-- 
1063645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063645
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: markdown
Version: 1.0.1-12
Severity: serious
Justification: Debian Policy section 4.9
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

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

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

This mass bug filing was discussed on debian-devel@ in
.
(The severity of this bug at the time of the mass bug filing was set to
'important', and bumped to 'serious' after a month, but given that quite
some time has passed, I'm just setting it directly to 'serious' now, as
I'm planning to remove the fallback workaround for these targets in the
next dpkg upload.)

Thanks,
Guillem
--- End Message ---
--- Begin Message ---
fixed 1063645 11.5.1.25-1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 13 Jun 2024 14:52:33 +0200
Source: rtpengine
Architecture: source
Version: 11.5.1.25-1
Distribution: unstable
Urgency: medium
Maintainer: Debian VoIP Team 
Changed-By: Victor Seva 
Closes: 1073102
Changes:
  rtpengine (11.5.1.25-1) unstable; urgency=medium
  .
* New upstream version 11.5.1.25
* switch from markdown to discount (Closes: #1073102)
Checksums-Sha1:
  b5552d6dbee2eabff5328525ce9d4efbca073d1d 3028 rtpengine_11.5.1.25-1.dsc
  89ea2a17b1a8dd369c288d7794270602d355d021 6491224 
rtpengine_11.5.1.25.orig.tar.gz
  dc927227958c50146803be64adff80f6e50c13c7 9500 
rtpengine_11.5.1.25-1.debian.tar.xz
  6c28be746d54d717a773766eaccdf02b2a8ff451 18071 
rtpengine_11.5.1.25-1_amd64.buildinfo
Checksums-Sha256:
  e1aac581f447ed0f5ef792859f96198357fd417298c4c2bc95c2efbbc9de0b2a 3028 
rtpengine_11.5.1.25-1.dsc
  2cb61769a3e18904f657b9778b8ac3e6fe799dee452eced842cbec1b866c4820 
6491224 rtpengine_11.5.1.25.orig.tar.gz
  cfb5204f890e0ff1d913b5e971f7d024a31a19af26903b609e7e2d851cd5c062 9500 
rtpengine_11.5.1.25-1.debian.tar.xz
  8ebc2759551961d7233cd672565f5b70b60c365c924032834d74695b31decfff 18071 
rtpengine_11.5.1.25-1_amd64.buildinfo
Files:
  daae0a6924c5d04ebd578506790b562e 3028 net optional 
rtpengine_11.5.1.25-1.dsc
  986b20636c9c38ec5730b030ef5afff6 6491224 net optional 
rtpengine_11.5.1.25.orig.tar.gz
  c5021325e477864cd01e408328941dd8 9500 net optional 
rtpengine_11.5.1.25-1.debian.tar.xz
  f009bdab95a256d674957700e44c15f5 18071 net optional 
rtpengine_11.5.1.25-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iIcEARYKAC8WIQQq6AO8RS0zF4SC1vh9e2XEKg7IsgUCZmrsxBEcdnNldmFAZGVi
aWFuLm9yZwAKCRB9e2XEKg7IsqQmAQDHf/FD+HUE3TDVh4kxGngwmMDjuWlcZB5h
L+X1QqfDyAD/WLkzITL/cGHwWxgZ0ODkMgEvtXIhXBKW2EVaVYXvwwQ=
=1Tak
-END PGP SIGNATURE-
-- 
-
|   ,''`. Victor Seva |
|  : :' :  linuxman...@torreviejawireless.org |
|  `. `'  PGP: 8F19 CADC D42A 42D4 5563  730C 51A0 9B18 CF5A 5068 |
|`-  Debian Developer |
   End Message ---

Processed: Re: Bug#1073099: markdown-mode: replace to-be-removed markdown build-dependency

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #1073099 [src:markdown-mode] markdown-mode: replace to-be-removed markdown 
build-dependency
Added tag(s) pending.

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

Bug#1073099: markdown-mode: replace to-be-removed markdown build-dependency

[Xiyue Deng]

Control: tags -1 pending

Hi Chris,

Chris Hofstaedtler  writes:

> Source: markdown-mode
> Version: 2.6-1
> Severity: serious
> Control: block 1072958 by -1
>
> Your package build-depends on markdown. Per bug #1063645, markdown is not
> maintained upstream or in Debian and should be removed.
> Drop-in alternatives, for examples the suggested `discount` or
> `python3-markdown` or `libtext-markdown-perl`.
>
> `discount` and `libtext-markdown-perl` provide a `markdown` program if your
> package needs that.
>

Thanks for your report!  Actually, this has been implemented in team
repo (see commits [1][2][3]).  Please also see Bug#1072906[4] for the
RFS of markdown-mode, and please feel free to add any comments there.

[1] 
https://salsa.debian.org/emacsen-team/markdown-mode/-/commit/a5348a075464f77701df1c138985f4976fe6a8a0
[2] 
https://salsa.debian.org/emacsen-team/markdown-mode/-/commit/10deb2fb6c00fb83a96226fb0c7645af0672d676
[3] 
https://salsa.debian.org/emacsen-team/markdown-mode/-/commit/adfe33a78fac11877c32fe2f5c87284b0c1d6463
[4] https://bugs.debian.org/1072906

-- 
Xiyue Deng

Bug#1073284: marked as done (librust-async-compression-dev: Depends: librust-zstd-safe-6-dev but it is not installable)

[Debian Bug Tracking System]

Your message dated Mon, 17 Jun 2024 08:51:17 +
with message-id 
and subject line Bug#1073284: fixed in rust-async-compression 0.4.11-2
has caused the Debian Bug report #1073284,
regarding librust-async-compression-dev: Depends: librust-zstd-safe-6-dev but 
it is not installable
to be marked as done.

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

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


-- 
1073284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073284
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librust-async-compression-dev
Version: 0.4.0-2
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

Install main build dependencies (apt-based resolver)


Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
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:
 librust-async-compression-dev : Depends: librust-zstd-0.12-dev
 Depends: librust-zstd-safe-6-dev but it is not 
installable
E: Unable to correct problems, you have held broken packages.
apt-get failed.
E: Package installation failed


Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: rust-async-compression
Source-Version: 0.4.11-2
Done: Holger Levsen 

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

Debian distribution maintenance software
pp.
Holger Levsen  (supplier of updated rust-async-compression 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 17 Jun 2024 10:23:18 +0200
Source: rust-async-compression
Architecture: source
Version: 0.4.11-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Holger Levsen 
Closes: 1073284
Changes:
 rust-async-compression (0.4.11-2) unstable; urgency=medium
 .
   [ Holger Levsen ]
   * Team upload.
 .
   [ Matthias Geiger ]
   * Package async-compression 0.4.11 from crates.io using debcargo 2.6.1
   * Patch brotli dependency (Closes: #1073284)
   * Updated my mail address in debcargo.toml
   * Patch ntest dependency so tests can run
   * Skip currently broken features
Checksums-Sha1:
 934d5608898af94b3e802489033b9ac567848b59 2845 
rust-async-compression_0.4.11-2.dsc
 2e99fd51aba71b203ecc5bc74e7bc587bc44a2f9 4392 
rust-async-compression_0.4.11-2.debian.tar.xz
 1adeace3d96766452174fd6c49cc9bdfb2548528 7817 
rust-async-compression_0.4.11-2_source.buildinfo
Checksums-Sha256:
 65e73478eefeb60b57349304484f262593e280c98bafbc45cf8022ce26506af2 2845 
rust-async-compression_0.4.11-2.dsc
 5ad3137d8d435b72507cf6948afa9239f521917f145ce6b0477d882a432acb3b 4392 
rust-async-compression_0.4.11-2.debian.tar.xz
 3c4a84698ae3f28f68a606ac9d969487aef05ca8b171b2ad2c0b537a62ce1133 7817 
rust-async-compression_0.4.11-2_source.buildinfo
Files:
 1ca07e61912855a561a715d0efbe9944 2845 rust optional 
rust-async-compression_0.4.11-2.dsc
 da7228314c9af548dacf7ed1656e2ae9 4392 rust optional 
rust-async-compression_0.4.11-2.debian.tar.xz
 88e4bf1f97aa67c68fae35967fb80a22 7817 rust optional 
rust-async-compression_0.4.11-2_source.buildinfo


-BEGIN PGP SIGNATURE-

wsG7BAEBCgBvBYJmb/KTCRAJGrhWBpqqHEcUAAAeACBzYWx0QG5vdGF0aW9u
cy5zZXF1b2lhLXBncC5vcmdGpLw2lQHsmSGQUe07dtA4GFEJ/G0JEVMH2+uLr8rJ
7xYhBLi/VBN7CdNc8Cb+nQkauFYGmqocAAD8xg/7BIfHgRdetCs7N647OhGfXAYR
my7Osz3qrf+/lkPT+TTvHDhGOhZGtQ1XmOJZl4K22e5E9DXp8BF/LfbcEMeuKWyZ
imVryMusAo76ks80jO63pjX1C5P0fum4N4lZ/1pGXT5R3pcA0avJ+EsZk4KvIdE2
B0sv5TNiWNXl10Wm+7BCGw4gmJ6EN69vQIGiADgP9iUsKg47NwB93WiO94mMhwOm
0MfEOI3FTDHlGAOLWJAePLHxPRfNCYwWYd9v+yKBBgkq3LSYzvWnfUQxJSv7JSHm
wCrr4XbVwgM+L7HYpO75Y5YT/50BJ9jdgDy1toPaaUYW9hQe5D1WIa5ToiowIgVk
kyOkMArCFPfmkwo2AfEKJrpttM0C2fNZG2G52yQ0rh/bKxMWob+ZpN0bSdTvkH6l

Processed: Re: libxml2: just another API+ABI break; please bump soname

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - pending
Bug #1073508 [libxml2] libxml2: just another API+ABI break; please bump soname
Removed tag(s) pending.

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

Bug#1073508: libxml2: just another API+ABI break; please bump soname

[Aron Xu]

Control: tags -1 - pending

Hi,

On Sun, 16 Jun 2024 19:10:57 +0200 (CEST) Thorsten Glaser
 wrote:
> On Sun, 16 Jun 2024, Thorsten Glaser wrote:
>
> >Better prevent this from landing in trixie until the package
> >gets its soname bumped.
>
> In fact, unless someone has the tuits to diff every single
> API and ABI surface of the package between trixie (ideally
> bookworm) and sid versions, it would be best if any package
> built against libxml2 >2.12 be binNMU’d in trixie, and once
> 2.12 is renamed to libxml3 or something, they are to be rebuilt
> in sid anyway.
>
> Who knows what other API and ABI breaks are hiding herein…
>
> bye,
> //mirabilos
>

It looks that this libxml2 update is causing more troubles than
expected, I would like to ask for your opinion whether it's better to
revert to an older version for the moment?

The LibreOffice break stuff isn't a real API/ABI break, it was caused
by default build options being changed so that some features were
intentionally disabled by upstream... I can try to dig further about
the surface of API/ABI changes, but I have to say that would take some
time to complete.

Thanks,
Aron

Bug#1073046: fixed in cups 2.4.7-3

[John Paul Adrian Glaubitz]

Hi Thorsten,

On Sun, 2024-06-16 at 00:19 +, Debian FTP Masters wrote:
>[ Thorsten Alteholz ]
>* reintroduce time_t changes that were accidentally deleted
>  with last upload
>  (thanks to Michael Hudson-Doyle for this work)
>* debian/rules: no test on riscv64 (Closes: #1073046)

Would be great if the testsuite could be disabled for sparc64 as well
if there is no prospective fix for the testsuite failures in sight.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Processed: severity of 1069130 is serious

[Debian Bug Tracking System]

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

> severity 1069130 serious
Bug #1069130 {Done: Bas Couwenberg } [src:python-mapnik] 
python-mapnik: FTBFS with Mapnik 4.0.0
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: tagging 1069130

[Debian Bug Tracking System]

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

> tags 1069130 + trixie sid
Bug #1069130 {Done: Bas Couwenberg } [src:python-mapnik] 
python-mapnik: FTBFS with Mapnik 4.0.0
Added tag(s) sid and trixie.
> thanks
Stopping processing here.

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