Bug#1070677: fail2ban fails: "Failed during configuration: Have not found any log file for sshd jail"

[Sylvestre Ledru]

Le 07/05/2024 à 03:57, Vincent Lefevre a écrit :

On 2024-05-07 03:28:28 +0200, Vincent Lefevre wrote:

May 07 03:01:28 qaa fail2ban-server[557228]: 2024-05-07 03:01:28,226 fail2ban   
 [557228]: ERROR   Failed during configuration: Have not found any 
log file for sshd jail

I suppose that this is because sshd no longer uses the systemd
backend. This is wrong. If I understand correctly, the point of

https://github.com/fail2ban/fail2ban/issues/3292#issuecomment-2078361360

is to no longer use the systemd backend for all jails, but for
sshd only. So "backend = systemd" has been removed from DEFAULT,
but the above comment also points to

https://github.com/fail2ban/fail2ban/commit/85a4881a9a818b6a746109f74980919296eedad0

which adds for DEFAULT in paths-debian.conf:


banaction = nftables
banaction_allports = nftables[type=allports]

sshd_backend = systemd


But paths-debian.conf has not changed in the fail2ban 1.1.0-1 package.


ok, thanks.

Any idea what the fix should be? I am a bit lost in this conversation :/

Thanks

S

Bug#1068755: docker.io: FTBFS: failing tests

[Tianon Gravi]

On Mon, 6 May 2024 at 17:00, Cyril Brulebois  wrote:
> I'm adding Tianon to the loop explicitly since I'm definitely no Docker
> (or Go) expert, in case some time can be spared to look into this
> problem. Otherwise I'll try and come up with something.

I think the backport by Reinhard[1][2] is probably correct/simplest,
although definitely a case of "how did this test ever work??" 😄

[1]: https://bugs.debian.org/1068755#13
[2]: https://bugs.debian.org/1068755#20

(it might be worth annotating that upstream patch with slightly more
DEP3 so it's clear we can just drop it in v23+, though 👀  it got
backported from v24 in [3])

[3]: https://github.com/moby/moby/pull/45062

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#1061358: marked as done (gnumeric: identified for time_t transition but no ABI in shlibs)

[Debian Bug Tracking System]

Your message dated Tue, 07 May 2024 02:46:42 +
with message-id 
and subject line Bug#1061358: fixed in gnumeric 1.12.57-1
has caused the Debian Bug report #1061358,
regarding gnumeric: identified for time_t transition but no ABI in shlibs
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.)


-- 
1061358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061358
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnumeric
Version: 1.12.56-2
Severity: serious
User: debian-...@lists.debian.org
Usertags: time-t

Hi Dmitry,

Analysis of the archive for the 64-bit time_t transition[0][1] identifies
gnumeric as an affected package, on the basis that the headers could not be
compiled and analyzed out of the box using abi-compliance-checker[2], so we
have to assume it's affected.

However, gnumeric's shlibs file declares a dependency on a library package
name that contains no ABI information:

$ cat DEBIAN/shlibs
libspreadsheet 1.12.56 gnumeric (>= 1.12.56)
$

It is therefore not obvious that we should rename the package to
'gnumeric-t64' as part of this transition.

Looking at the archive, there are packages built from separate source
packages which depend on this library: both libgcu0v5 from
gnome-chemistry-utils, and also gir1.2-gnumeric from gnumeric source whose
only dependency on gnumeric is via the shlibs, rather than being a strict
versioned dependency.

Since there is no self-evident thing to do with the library package name
here, we will not be handling this package as part of the mass NMUs.
Instead I am filing a serious bug because partial upgrades from bookworm to
trixie on 32-bit architectures will result in ABI skew and may result in
broken behavior.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org

[0] https://wiki.debian.org/ReleaseGoals/64bit-time
[1] https://lists.debian.org/debian-devel/2024/01/msg00041.html
[2] 
https://adrien.dcln.fr/misc/armhf-time_t/2024-01-17/logs/gnumeric/base/log.txt


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: gnumeric
Source-Version: 1.12.57-1
Done: Dmitry Smirnov 

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

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated gnumeric package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 02 May 2024 20:27:06 +1000
Source: gnumeric
Architecture: source
Version: 1.12.57-1
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Dmitry Smirnov 
Closes: 1061358
Changes:
 gnumeric (1.12.57-1) unstable; urgency=medium
 .
   * New upstream release.
   * Standards-Version: 4.7.0
   * Closing 64-bit time_t transition bug/report (Closes: #1061358).
   * Build-Depends:
 = libgoffice-0.10-dev (>= 0.10.57~)
Checksums-Sha1:
 db65a9b4cd64cb90eb6f7956749875c546fb31de 2516 gnumeric_1.12.57-1.dsc
 d1eab1c96214d363873715d2b9b65ee26e92bd83 18149400 gnumeric_1.12.57.orig.tar.xz
 3365af400ae5c235726ca48d1e9d617b904ee49f 44100 gnumeric_1.12.57-1.debian.tar.xz
 bff0423b8bcc6788d71748ad673b76e0b0a2b2cf 19347 
gnumeric_1.12.57-1_amd64.buildinfo
Checksums-Sha256:
 6d9c2ad482fa32e4d171354d823888973aad11d648768485d28860fb011abf6b 2516 
gnumeric_1.12.57-1.dsc
 aff50b1b62340c24fccf453d5fad3e7fb73f4bc4b34f7e34b6c3d2d9af6a1e4f 18149400 
gnumeric_1.12.57.orig.tar.xz
 72e973fe196718c482138490d04c97d76784dbefed343b34166eed2a1173e3f7 44100 
gnumeric_1.12.57-1.debian.tar.xz
 3761b6a23534770f5936c4ce60ca06e893aafc06307ea9ee9f06a15431dd8d03 19347 
gnumeric_1.12.57-1_amd64.buildinfo
Files:
 22cf105e70036acd38875bbf1cb6f2b2 2516 math optional gnumeric_1.12.57-1.dsc
 237ce4f6c43661892e802bf81dbff1b2 18149400 math optional 
gnumeric_1.12.57.orig.tar.xz
 40e8bad61591ff0b7d396844e9134c84 44100 math optional 
gnumer

Bug#1070677: fail2ban fails: "Failed during configuration: Have not found any log file for sshd jail"

[Vincent Lefevre]

On 2024-05-07 03:57:44 +0200, Vincent Lefevre wrote:
> sshd_backend = systemd

BTW, that would fix the issue only for sshd. But what about the other
jails the user could have enabled in /etc/fail2ban/jail.local? The
user configuration may rely on systemd being the default backend, at
least the configured backend for these jails.

For instance, concerning postfix, both paths-arch.conf and
paths-opensuse.conf have "postfix_backend = systemd", but not
paths-debian.conf. Other jails may be concerned.

paths-arch.conf has

# These services will log to the journal via syslog, so use the journal by
# default.
syslog_backend = systemd
sshd_backend = systemd
dropbear_backend = systemd
proftpd_backend = systemd
pureftpd_backend = systemd
wuftpd_backend = systemd
postfix_backend = systemd
dovecot_backend = systemd

and paths-opensuse.conf has

# These services will log to the journal via syslog, so use the journal by
# default.
syslog_backend = systemd
sshd_backend = systemd
dropbear_backend = systemd
proftpd_backend = systemd
pureftpd_backend = systemd
wuftpd_backend = systemd
postfix_backend = systemd
dovecot_backend = systemd
mysql_backend = systemd

But the user may also have his own services with associated jails...

Either there should be a better fix or the change should be announced
in NEWS.Debian, with a clear explanation on what to do.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1070677: fail2ban fails: "Failed during configuration: Have not found any log file for sshd jail"

[Vincent Lefevre]

On 2024-05-07 03:28:28 +0200, Vincent Lefevre wrote:
> May 07 03:01:28 qaa fail2ban-server[557228]: 2024-05-07 03:01:28,226 fail2ban 
>[557228]: ERROR   Failed during configuration: Have not found 
> any log file for sshd jail

I suppose that this is because sshd no longer uses the systemd
backend. This is wrong. If I understand correctly, the point of

https://github.com/fail2ban/fail2ban/issues/3292#issuecomment-2078361360

is to no longer use the systemd backend for all jails, but for
sshd only. So "backend = systemd" has been removed from DEFAULT,
but the above comment also points to

https://github.com/fail2ban/fail2ban/commit/85a4881a9a818b6a746109f74980919296eedad0

which adds for DEFAULT in paths-debian.conf:


banaction = nftables
banaction_allports = nftables[type=allports]

sshd_backend = systemd


But paths-debian.conf has not changed in the fail2ban 1.1.0-1 package.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1070677: fail2ban fails: "Failed during configuration: Have not found any log file for sshd jail"

[Vincent Lefevre]

Package: fail2ban
Version: 1.1.0-1
Severity: grave
Justification: renders package unusable

After the upgrade to 1.1.0-1, "systemctl status" gives

× fail2ban.service - Fail2Ban Service
 Loaded: loaded (/usr/lib/systemd/system/fail2ban.service; enabled; preset: 
enabled)
 Active: failed (Result: exit-code) since Tue 2024-05-07 03:01:28 CEST; 
25min ago
   Duration: 58ms
   Docs: man:fail2ban(1)
   Main PID: 557228 (code=exited, status=255/EXCEPTION)
CPU: 55ms

May 07 03:01:28 qaa systemd[1]: Started fail2ban.service - Fail2Ban Service.
May 07 03:01:28 qaa fail2ban-server[557228]: 2024-05-07 03:01:28,226 fail2ban   
 [557228]: ERROR   Failed during configuration: Have not found any 
log file for sshd jail
May 07 03:01:28 qaa fail2ban-server[557228]: 2024-05-07 03:01:28,230 fail2ban   
 [557228]: ERROR   Async configuration of server failed
May 07 03:01:28 qaa systemd[1]: fail2ban.service: Main process exited, 
code=exited, status=255/EXCEPTION
May 07 03:01:28 qaa systemd[1]: fail2ban.service: Failed with result 
'exit-code'.

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

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

Versions of packages fail2ban depends on:
ii  python3  3.11.8-1
ii  python3-systemd  235-1+b3

Versions of packages fail2ban recommends:
ii  iptables   1.8.10-3
ii  nftables   1.0.9-1+b2
ii  python3-pyinotify  0.9.6-2
ii  whois  5.5.22

Versions of packages fail2ban suggests:
ii  mailutils [mailx]  1:3.17-1.1+b2
pn  monit  
ii  sqlite33.45.3-1
pn  system-log-daemon  

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Processed: found 1070652 in 17

[Debian Bug Tracking System]

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

> found 1070652 17
Bug #1070652 [how-can-i-help] how-can-i-help: explicitly require 'ostruct'
Marked as found in versions how-can-i-help/17.
> thanks
Stopping processing here.

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

Bug#1040375: /usr/lib/x86_64-linux-gnu/simplescreenrecorder/libssr-glinject.so: Segmentation fault when used with anything

[Bernhard Übelacker]

On Sat, 10 Feb 2024 11:01:54 +0100 Petter Reinholdtsen  wrote:

[Petter Reinholdtsen]
> I do not use ssr much myself, and have not had time to test.

I applied the upstream commit in git branch fix-1040375-glinject and
tested it on Bookworm, but alas, the .so file still segfaults with a
useless backtrace.  I might have applied the commit incorrectly, as it
did not apply without changes, but hope not.  Perhaps someone
who understand what is happening can have a look?

--
Happy hacking
Petter Reinholdtsen




Hello,
looking through some bugs about crashes I came to this one
and found found it interesting.

If a proper backtrace is still helping one can get one by using
systemd-coredump.

Another nice way to debug early startup is using rr debugger.
(Plus the ability to debug back and forth.)


As far as I see the crash happens because it wants to print this message:

57  GLINJECT_PRINT("Error: Can't open libdl.so!");

But unfortunately libstdc++ seems not yet prepared to output the error.


(rr) bt
#0  0x7fbf7ff2fd9a in std::basic_ostream 
>::sentry::sentry(std::basic_ostream >&) () from 
/lib/x86_64-linux-gnu/libstdc++.so.6
#1  0x7fbf7ff3074c in std::basic_ostream >& std::__ostream_insert >(std::basic_ostream >&, char const*, long) () 
from /lib/x86_64-linux-gnu/libstdc++.so.6
#2  0x7fbf7ff30bdb in std::basic_ostream >& std::operator<< 
 >(std::basic_ostream >&, char const*) () from 
/lib/x86_64-linux-gnu/libstdc++.so.6
#3  0x7fbf805cef6f in InitGLInject () at ./glinject/Hook.cpp:57
#4  0x7fbf805cf13f in dlsym (handle=0x7fbf8060d2e0, symbol=0x7fbf80185f7a 
"pthread_create") at ./glinject/Hook.cpp:231
#5  0x7fbf80136dd7 in glvndSetupPthreads () at 
../src/util/glvnd_pthread.c:452
#6  0x7fbf801351a9 in __glDispatchOnLoadInit () at 
../src/GLdispatch/GLdispatch.c:174
#7  0x7fbf805de9ce in call_init (env=0x7ffeea4b1538, argv=0x7ffeea4b1528, argc=1, 
l=) at ./elf/dl-init.c:74
#8  call_init (l=, argc=1, argv=0x7ffeea4b1528, 
env=0x7ffeea4b1538) at ./elf/dl-init.c:26
#9  0x7fbf805deab4 in _dl_init (main_map=0x7fbf8060d2e0, argc=1, 
argv=0x7ffeea4b1528, env=0x7ffeea4b1538) at ./elf/dl-init.c:121
#10 0x7fbf805f4a70 in _dl_start_user () from /lib64/ld-linux-x86-64.so.2
#11 0x0001 in ?? ()
#12 0x7ffeea4b25ea in ?? ()
#13 0x in ?? ()
(rr)

(For some reason with libstdc++6-dbgsym the backtrace gets less good.)



I guess upstream discussed this issue here:

  https://github.com/MaartenBaert/ssr/issues/947


And a package built from `fix-1040375-glinject` did no
longer show this crash to me.


Attached file shows my actions inside a minimal bookworm VM.

Kind regards,
Bernhard
# 2024-05-07 Bookworm/stable amd64 qemu VM

apt update
apt dist-upgrade
apt install systemd-coredump mc gdb rr mesa-utils git simplescreenrecorder-lib 
simplescreenrecorder-lib-dbgsym libglvnd0-dbgsym libstdc++6-dbgsym appstream
apt build-dep simplescreenrecorder-lib






mkdir /home/benutzer/source/simplescreenrecorder/orig -p
cd/home/benutzer/source/simplescreenrecorder/orig
apt source simplescreenrecorder







benutzer@debian:~$ 
LD_PRELOAD=/usr/lib/x86_64-linux-gnu/simplescreenrecorder/libssr-glinject.so 
/usr/bin/true
Speicherzugriffsfehler (Speicherabzug geschrieben)
benutzer@debian:~$ 


benutzer@debian:~$ coredumpctl list
Hint: You are currently not seeing messages from other users and the system.
  Users in groups 'adm', 'systemd-journal' can see all messages.
  Pass -q to turn off this notice.
TIME PID  UID  GID SIG COREFILE EXESIZE
Tue 2024-05-07 00:10:28 CEST 994 1000 1000 SIGSEGV present  /usr/bin/true 89.0K
benutzer@debian:~$ 



benutzer@debian:~$ coredumpctl gdb --debugger-argument=-q 994
Hint: You are currently not seeing messages from other users and the system.
  Users in groups 'adm', 'systemd-journal' can see all messages.
  Pass -q to turn off this notice.
   PID: 994 (true)
   UID: 1000 (benutzer)
   GID: 1000 (benutzer)
Signal: 11 (SEGV)
 Timestamp: Tue 2024-05-07 00:10:28 CEST (1min 26s ago)
  Command Line: /usr/bin/true
Executable: /usr/bin/true
 Control Group: /user.slice/user-1000.slice/session-3.scope
  Unit: session-3.scope
 Slice: user-1000.slice
   Session: 3
 Owner UID: 1000 (benutzer)
   Boot ID: 4df23299079540e38e42560b3966b576
Machine ID: 55a5ad9df1d547f38d7696343d9fde7d
  Hostname: debian
   Storage: 
/var/lib/systemd/coredump/core.true.1000.4df23299079540e38e42560b3966b576.994.171503342800.zst
 (present)
  Size on Disk: 89.0K
   Message: Process 994 (true) of user 1000 dumped core.

Stack trace of thread 994:
#0  0x7f988d92fd9a _ZNSo6sentryC1ERSo (libstdc++.so.6 + 
0x12fd9a)
#1  0x7f988d93074c 
_ZSt16__ostream_insertIcSt11char_traitsIcEERSt13basic_ostreamIT_T0_ES6_PKS3_l 
(libstdc++.so.6 + 0x13074c)
 

Bug#1068755: docker.io: FTBFS: failing tests

[Cyril Brulebois]

Hi Santiago,

And thanks for the report.

Santiago Vila  (2024-04-10):
> Package: src:docker.io
> Version: 20.10.25+dfsg1-2
> Severity: serious
> Tags: ftbfs
> 
> Dear maintainer:
> 
> During a rebuild of all packages in unstable, your package failed to build:
> 
> === FAIL: distribution/xfer 
> TestMaxDownloadAttempts/max-attempts=5,_fail_at_6th_attempt (0.88s)
> time="2024-04-10T10:28:41Z" level=info msg="Download failed, retrying (2/5): 
> simulating download attempt 2/2"
> time="2024-04-10T10:28:41Z" level=info msg="Download failed, retrying (1/5): 
> simulating download attempt 1/6"
> download_test.go:425: assertion failed: expected error "simulating 
> download attempt 5/6", got "simulating download attempt 6/6"
> time="2024-04-10T10:28:42Z" level=info msg="Download failed, retrying (5/5): 
> simulating download attempt 5/5"
> 
> === FAIL: distribution/xfer TestMaxDownloadAttempts (0.00s)

That FTBFS is easily reproducible via cowbuilder (sid, amd64), and also
within an unclean, up-to-date devel schroot (still sid, amd64).

I'm adding Tianon to the loop explicitly since I'm definitely no Docker
(or Go) expert, in case some time can be spared to look into this
problem. Otherwise I'll try and come up with something.

Thanks for considering!


Cheers,
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/


signature.asc
Description: PGP signature

Processed: retitle 1070652 to how-can-i-help: explicitly require 'ostruct'

[Debian Bug Tracking System]

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

> retitle 1070652 how-can-i-help: explicitly require 'ostruct'
Bug #1070652 [how-can-i-help] ruby-json: breaks how-can-i-help
Changed Bug title to 'how-can-i-help: explicitly require 'ostruct'' from 
'ruby-json: breaks how-can-i-help'.
> thanks
Stopping processing here.

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

Processed: reassign 1070652 to how-can-i-help

[Debian Bug Tracking System]

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

> reassign 1070652 how-can-i-help
Bug #1070652 [ruby-json] ruby-json: breaks how-can-i-help
Bug reassigned from package 'ruby-json' to 'how-can-i-help'.
No longer marked as found in versions ruby-json/2.7.2+dfsg-1.
Ignoring request to alter fixed versions of bug #1070652 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#1070498: marked as done (libvirt attempts to write to $HOME during the build)

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2024 23:40:21 +
with message-id 
and subject line Bug#1070498: fixed in libvirt 10.3.0-2
has caused the Debian Bug report #1070498,
regarding libvirt attempts to write to $HOME during the build
to be marked as done.

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

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


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

https://buildd.debian.org/status/fetch.php?pkg=libvirt&arch=amd64&ver=10.3.0-1&stamp=1714824148&raw=0

...
53) completion-command... 
In '/<>/tests/virshtestdata/completion-command.out':
Offset 6
Expect []
Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission 
denied
]
  ... FAILED
54) completion-command-complete   ... 
In '/<>/tests/virshtestdata/completion-command-complete.out':
Offset 6
Expect []
Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission 
denied
]
  ... FAILED
55) completion-args   ... 
In '/<>/tests/virshtestdata/completion-args.out':
Offset 47
Expect []
Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission 
denied
]
  ... FAILED
56) completion-arg-partial... 
In '/<>/tests/virshtestdata/completion-arg-partial.out':
Offset 26
Expect []
Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission 
denied
]
  ... FAILED
57) completion-arg-full-bool  ... 
In '/<>/tests/virshtestdata/completion-arg-full-bool.out':
Offset 7
Expect []
Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission 
denied
]
  ... FAILED
58) completion-arg-full-bool-next ... 
In '/<>/tests/virshtestdata/completion-arg-full-bool-next.out':
Offset 47
Expect []
Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission 
denied
]
  ... FAILED
59) completion-arg-full-string... 
In '/<>/tests/virshtestdata/completion-arg-full-string.out':
Offset 10
Expect []
Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission 
denied
]
  ... FAILED
60) completion-arg-full-string-next   ... 
In '/<>/tests/virshtestdata/completion-arg-full-string-next.out':
Offset 47
Expect []
Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission 
denied
]
  ... FAILED
61) completion-arg-full-argv  ... 
In '/<>/tests/virshtestdata/completion-arg-full-argv.out':
Offset 10
Expect []
Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission 
denied
]
  ... FAILED
62) completion-arg-full-argv-next ... 
In '/<>/tests/virshtestdata/completion-arg-full-argv-next.out':
Offset 6
Expect []
Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission 
denied
]
  ... FAILED
63) completion-argv-multiple  ... 
In '/<>/tests/virshtestdata/completion-argv-multiple.out':
Offset 5
Expect []
Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission 
denied
]
  ... FAILED
64) completion-argv-multiple-next ... 
In '/<>/tests/virshtestdata/completion-argv-multiple-next.out':
Offset 268
Expect []
Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission 
denied
]
  ... FAILED
65) completion-argv-multiple-positional   ... 
In 
'/<>/tests/virshtestd

Bug#1069265: tzdata: Upgrade from 2023c-2 to 2024 corrupts zoneinfo files

[Plasma (David Paul)]

On Thu, 18 Apr 2024 23:39:14 + IvanAbs  wrote:
> On 2024-04-17 several of my servers running Debian 10 received an
> update for the tzdata package via Debian unattended-upgrade. However,
> this update resulted in corruption of files within the
> /usr/share/zoneinfo directory.

I, too, encountered a variation of this issue today while trying to
update the tzdata package on my system. I was eventually able to resolve
the issue with a little manual intervention. Details follow.

> I was using tzdata 2023c-2 package, and originally installed from an
> official Debian source

In my case, the installed version of the package was tzdata 2023c-5.

> I installed tzdata 2023c-2 with dpkg -i, because our severs needs the
> last-year updated data, but there were not a release for Debian 10,
> until yesterday.

Similarly, I had installed tzdata 2023c-5 on what is effectively Debian
Bullseye install (though what is actually an unabashed FrankenDevuan
install that is mostly composed of packages from Devuan's Chimaera
release). My motivation for doing so was similar: I wanted the
then-current timezone database and the package in chimaera/bullseye had
yet to be updated. I fully acknowledge this course of action is
actively frowned upon[1].

[1] https://wiki.debian.org/DontBreakDebian#Don.27t_make_a_FrankenDebian

> To resolve this issue, I had to completely remove the tzdata 2023
> version and perform a clean installation of the new tzdata 2024
> version.

Here's how I was able to resolve the issue. Using snapshot.debian.org,
I downloaded tzdata_2023d-1_all.deb which installed without issue over
2023c-5. Afterward, I was able to install tzdata 2024a-0+deb11u1
without issue.

As this issue only manifests on systems in explicitly unsupported
configurations, the severity of the bug should probably be reduced from
grave, but I will leave that decision to others.

I hope this was helpful,

-- 
Plasma

Bug#1068665: marked as done (cfengine3: FTBFS on arm{el,hf}: 1 of 60 tests failed)

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2024 23:20:57 +
with message-id 
and subject line Bug#1068665: fixed in cfengine3 3.21.4-1.1
has caused the Debian Bug report #1068665,
regarding cfengine3: FTBFS on arm{el,hf}: 1 of 60 tests failed
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.)


-- 
1068665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068665
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cfengine3
Version: 3.21.4-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=cfengine3&arch=armel&ver=3.21.4-1&stamp=1712477798&raw=0

==
Starting test: files_interfaces_test.c
==
test_cfreadline_valid: Starting test
test_cfreadline_valid: Test completed successfully.
test_cfreadline_corrupted: Starting test
test_cfreadline_corrupted: Test completed successfully.
All 2 tests passed
PASS: files_interfaces_test
1 != 3
ERROR: connection_management_test.c:39 Failure!
1 != 2
ERROR: connection_management_test.c:69 Failure!
1 != 2
ERROR: connection_management_test.c:99 Failure!
1 != 2
ERROR: connection_management_test.c:129 Failure!
4 out of 4 tests failed!
test_purge_old_connections_nochange
test_purge_old_connections_purge_first
test_purge_old_connections_purge_middle
test_purge_old_connections_purge_last
==
Starting test: connection_management_test.c
==
test_purge_old_connections_nochange: Starting test
test_purge_old_connections_nochange: Test failed.
test_purge_old_connections_purge_first: Starting test
test_purge_old_connections_purge_first: Test failed.
test_purge_old_connections_purge_middle: Starting test
test_purge_old_connections_purge_middle: Test failed.
test_purge_old_connections_purge_last: Starting test
test_purge_old_connections_purge_last: Test failed.
FAIL: connection_management_test

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: cfengine3
Source-Version: 3.21.4-1.1
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated cfengine3 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: Sun, 05 May 2024 00:09:03 +0200
Source: cfengine3
Architecture: source
Version: 3.21.4-1.1
Distribution: unstable
Urgency: medium
Maintainer: CFEngine Team 
Changed-By: Andreas Beckmann 
Closes: 1068665
Changes:
 cfengine3 (3.21.4-1.1) unstable; urgency=medium
 .
   [ Emanuele Rocca ]
   * Non-maintainer upload.
   * d/patches/time-t-long-long.patch: coerce time_t to long long
 (closes: #1068665)
Checksums-Sha1:
 a5536870664caf328f6b63cf5083b94f45356f98 2439 cfengine3_3.21.4-1.1.dsc
 a6e8f4b6177d693709d1ef57c4f78e289879be3c 21744 
cfengine3_3.21.4-1.1.debian.tar.xz
 40bb4651a824806571be773d5621cb6ba882eadc 7504 
cfengine3_3.21.4-1.1_source.buildinfo
Checksums-Sha256:
 9b2543553a093d6e484c0ec832dd13993080076b5c67c5a184582a3d7a76be10 2439 
cfengine3_3.21.4-1.1.dsc
 8bef1421f99c662d47bf4b6bd2a090280c77ada156a57c5f86fef25ca8d0bf8c 21744 
cfengine3_3.21.4-1.1.debian.tar.xz
 5516f25b74c0268b27e865f02418544e00a2d3e484a517421be1c763d6408f7a 7504 
cfengine3_3.21.4-1.1_source.buildinfo
Files:
 9c8ae11de5c534fadea5465e560645f8 2439 admin optional cfengine3_3.21.4-1.1.dsc
 d47ba4d71911f39e9715a4224c7a9202 21744 admin optional 
cfengine3_3.21.4-1.1.debian.tar.xz
 69e343ad6853abb941b4bebdb2edb6b3 7504 admin optional 
cfengine3_3.21.4-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmY2tUQQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCAsqEACNbd+jyMI02quVfSa4lfUAPuqu+baQXZvP
wCKAfHbpShiPRFMOkD9kZnxWgZLRac93Jm7uhbD7n/aid0vjgwFWqGpKfFXq6rRQ
gZHAqguUPGkazrXn43NJ2oxPf7psO8ofIouiBFqaja3C2OHCMVWlbUrkSCPCqXp1
I7ualCjDpbs

Bug#1070652: [DRE-maint] Bug#1070652: ruby-json: breaks how-can-i-help

[Cédric Boutillier]

Hi!

I am reassigning this bug to the `how-can-i-help` package. Indeed, the
script `/usr/bin/how-can-i-help` uses implicitly the OpenStruct class,
without requiring explicitly 'ostruct'. The class was loaded
transitively from the json gem it seems.

Adding below line 35 the following line:

require 'ostruct'

fixes the bug.


Cheers,

Cédric

Quoting Vincent Lefevre (2024-05-06 17:41:49)
> Package: ruby-json
> Version: 2.7.2+dfsg-1
> Severity: grave
> Justification: renders package unusable

> This new ruby-json version breaks how-can-i-help:

> [...]
> Unpacking ruby-json:amd64 (2.7.2+dfsg-1) over (2.6.3+dfsg-1+b2) ...
> Setting up ruby-json:amd64 (2.7.2+dfsg-1) ...
> /usr/bin/how-can-i-help:155:in `': uninitialized constant OpenStruct 
> (NameError)

> proxy_uri = $proxy_url.nil? ? OpenStruct.new : URI.parse($proxy_url)
>   ^^

> -- System Information:
> Debian Release: trixie/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
> 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), 
> (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386

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

> Versions of packages ruby-json depends on:
> ii  libc6  2.38-7
> ii  libruby1:3.1+nmu1
> ii  libruby3.1t64  3.1.2-8.3

> ruby-json recommends no packages.

> ruby-json suggests no packages.

> -- no debconf information--- /tmp/how-can-i-help	2024-05-07 01:08:00.390399139 +0200
+++ /usr/bin/how-can-i-help	2024-05-07 00:59:24.082457226 +0200
@@ -33,6 +33,7 @@
 require 'fileutils'
 require 'time'
 require 'etc'
+require 'ostruct'
 
 include Debian
 

Bug#997441: marked as done (squirrel3: FTBFS: '! LaTeX Error: File `tgtermes.sty' not found.')

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2024 23:06:14 +
with message-id 
and subject line Bug#997441: fixed in squirrel3 3.1-8.1
has caused the Debian Bug report #997441,
regarding squirrel3: FTBFS:   '! LaTeX Error: File `tgtermes.sty' not found.'
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.)


-- 
997441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997441
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: squirrel3
Version: 3.1-8
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/debian/tmp/doc'
> latexmk -pdf -dvi- -ps-  'reference.tex'
> Rc files read:
>   /etc/LatexMk
>   latexmkrc
> Latexmk: This is Latexmk, John Collins, 21 September 2021, version: 4.75.
> Rule 'pdflatex': File changes, etc:
>Changed files, or newly in use since previous run(s):
>   'reference.tex'
> 
> Run number 1 of rule 'pdflatex'
> 
> 
> Running 'pdflatex   -recorder  "reference.tex"'
> 
> Latexmk: applying rule 'pdflatex'...
> This is pdfTeX, Version 3.141592653-2.6-1.40.22 (TeX Live 2022/dev/Debian) 
> (preloaded format=pdflatex)
>  restricted \write18 enabled.
> entering extended mode
> (./reference.tex
> LaTeX2e <2021-06-01> patch level 1
> L3 programming layer <2021-08-27> (./sphinxmanual.cls
> Document Class: sphinxmanual 2019/12/01 v2.3.0 Document class (Sphinx manual)
> (/usr/share/texlive/texmf-dist/tex/latex/base/report.cls
> Document Class: report 2021/02/12 v1.4n Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo)))
> (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/cmap/cmap.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty<>)
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsmath.sty
> For additional information on amsmath, use the `?' option.
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsbsy.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsopn.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amssymb.sty
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amsfonts.sty))
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.def
> (/usr/share/texlive/texmf-dist/tex/generic/babel/txtbabel.def))
> (/usr/share/texlive/texmf-dist/tex/generic/babel-english/english.ldf))
> 
> ! LaTeX Error: File `tgtermes.sty' not found.
> 
> Type X to quit or  to proceed,
> or enter new name. (Default extension: sty)
> 
> Enter file name: 
> ! Emergency stop.
>  
>  
> l.37 \usepackage
> {tgheros}^^M
> !  ==> Fatal error occurred, no output PDF file produced!
> Transcript written on reference.log.
> Latexmk: Missing input file 'tgtermes.sty' (or dependence on it) from 
> following:
>   '! LaTeX Error: File `tgtermes.sty' not found.'
> Collected error summary (may duplicate other messages):
>   pdflatex: Command for 'pdflatex' gave return code 1
>   Refer to 'reference.log' for details
> Latexmk: Use the -f option to force complete processing,
>  unless error was exceeding maximum runs, or warnings treated as errors.
> Latexmk: Examining 'reference.log'
> === TeX engine is 'pdfTeX'
> Latexmk: Errors, so I did not complete making targets
> make[2]: *** [Makefile:29: reference.pdf] Error 12


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/squirrel3_3.1-8_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: squirrel3
Source-Version: 3.1-8.1
Done: Matthias Geiger 

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

Bug#1069793: marked as done (wrong package name mnt-reform-setup-wizard -- should be reform-setup-wizard)

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2024 23:05:45 +
with message-id 
and subject line Bug#1069793: fixed in reform-setup-wizard 1.0-1
has caused the Debian Bug report #1069793,
regarding wrong package name mnt-reform-setup-wizard -- should be 
reform-setup-wizard
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.)


-- 
1069793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069793
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: reform-setup-wizard
Version: 0.1.0-1
Severity: serious

As it says in subject.
--- End Message ---
--- Begin Message ---
Source: reform-setup-wizard
Source-Version: 1.0-1
Done: Johannes Schauer Marin Rodrigues 

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

Debian distribution maintenance software
pp.
Johannes Schauer Marin Rodrigues  (supplier of updated 
reform-setup-wizard package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 May 2024 22:59:58 +0200
Source: reform-setup-wizard
Architecture: source
Version: 1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Lukas F. Hartmann 
Changed-By: Johannes Schauer Marin Rodrigues 
Closes: 1069793
Changes:
 reform-setup-wizard (1.0-1) unstable; urgency=medium
 .
   * New upstream version 1.0
   * debian/watch: use searchmode=plain
   * reform-setup-wizard: add breaks+replaces on mnt-reform-setup-wizard
 (closes: #1069793)
   * debian/install: install cleanup.sh and reform-setup-sway-config
 .
 reform-setup-wizard (0.1.0-3) experimental; urgency=medium
 .
   * fix binary package name mnt-reform-setup-wizard -> reform-setup-wizard
 .
 reform-setup-wizard (0.1.0-2) experimental; urgency=medium
 .
   [ Johannes Schauer Marin Rodrigues ]
   * debian/rules: use tuigreet d/rules
   * debian/salsa-ci.yml: disable blhc and crossbuilding
 .
   [ Jeremy Bícha ]
   * Build with Rust GNOME 46 crates
Checksums-Sha1:
 a102ec92e9266cfb309b8dcbc61d284a5d26821b 2376 reform-setup-wizard_1.0-1.dsc
 4ed508a8abe2d228895beb2c368f671282d96fe3 243056 
reform-setup-wizard_1.0.orig.tar.gz
 deec5ffe054befb0e5bedf02b41c76e256c67518 2848 
reform-setup-wizard_1.0-1.debian.tar.xz
Checksums-Sha256:
 af36c151b22c25f2c1b35e9b048e5e0bc4937a5910d2e6297bbe0e0d0d858592 2376 
reform-setup-wizard_1.0-1.dsc
 92b555dbef77d78c76047c256f1b13ed6e84ded5ef221d3bc9bd653c73983deb 243056 
reform-setup-wizard_1.0.orig.tar.gz
 87b49f0bc19b98aba2718e2a97af023e6e7c79675a5411b1a5d71d3ed9a3b3c0 2848 
reform-setup-wizard_1.0-1.debian.tar.xz
Files:
 04e56df6da356a246990c191d47b621a 2376 utils optional 
reform-setup-wizard_1.0-1.dsc
 3fdd6979656ce221ec12a1727baa 243056 utils optional 
reform-setup-wizard_1.0.orig.tar.gz
 2f65359671cc42a999017d383a589643 2848 utils optional 
reform-setup-wizard_1.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEElFhU6KL81LF4wVq58sulx4+9g+EFAmY5RScACgkQ8sulx4+9
g+ELmBAAuVkoIlhyMtpNqchV/zwsTKHio6bmerBcwtBhryNDNSJgmRvcUEDWUeb1
KOy/Lv+q+dEqhH2DU1rQEGvpDQBHoTnfUKYqhDHpOkDJCknylQOE/Smj+SCbHMnT
xnXp5ZxmrQQyeyWvIYZEQaSrqAPFAINmyBNjCr0Ty0gm8ihHYYNiDQN+ggw6lXs2
exe+JplkVK/aHct89n25SymdEfKuYhG/bJtmvgHjm8+oFICDGagZnPRHNScMGHQr
Z5JHPLl51DH3tZHyBfydmNXQWtXGCx9UxCYTNKWodO9w07LP3P7puwD47Y4bDPXU
jDma4mY2FyHi9pb6QMLHMfmurSA01CQdFSKpd4WEEM2Ah1SE54b7ryJYdKST8VH8
6fsVWZ8x3jQJJ1ij+joXh8uOIkA9NJomU0rwjdbtqKWpdpo4LTN57AWhQIWNjkZY
skMKksmJEGJEknSjOEd1d6k0PStEIeZSsQwoYY7qYRmqfQ19a7ct2CiIDQpMRmNV
noUKnQTJJWdt9hpH0eknuekMZLjvLSeQqXI5UY1EZUQ1lZbEpXKvrIlIfZJEoLIA
cC4sUnPMwCZBBcFqBSWIHONAjJHl9CAMO6Yq2T8C63ADr/5FalDwnayDgKNEsXNy
dxv5kMEYqXDEJHaijZJmsV7J++zLq/ssnMnbhZTppwbwt9gz4fw=
=J0Qs
-END PGP SIGNATURE-



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

Processed: Bug#1070498 marked as pending in libvirt

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1070498 [src:libvirt] libvirt attempts to write to $HOME during the build
Added tag(s) pending.

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

Bug#1070498: marked as pending in libvirt

[Andrea Bolognani]

Control: tag -1 pending

Hello,

Bug #1070498 in libvirt 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/libvirt-team/libvirt/-/commit/13f1f61aacf4277b0496049fd2df78352b4c5c30


patches: Add backport/vsh-Don-t-init-history-in-cmdComplete.patch

Fixes FTBFS.

Closes: #1070498


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1070498

Bug#1070069: fossil: CVE-2024-24795 unreleated breakage

[Barak A. Pearlmutter]

Well, it would certainly be simple enough: the source code should
compile fine, and the debian/* scripts would need only the very most
minor tweaks.

Bug#1063409: marked as done (mpi4py accesses the net for the build)

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2024 22:49:46 +
with message-id 
and subject line Bug#1063409: fixed in mpi4py 3.1.5-6
has caused the Debian Bug report #1063409,
regarding mpi4py accesses the net for the build
to be marked as done.

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

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


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

Package: src:mpi4py
Version: 3.1.5-4
Severity: serious
Tags: sid trixie

at least the first repository should be available in the python3-doc 
package.


[...]
make -C docs/source/usrman/ html man info latexpdf SPHINXOPTS="-D 
today=\"January 14, 2024\""

make[2]: Entering directory '/<>/docs/source/usrman'
Running Sphinx v7.2.6
making output directory... done
[autosummary] generating autosummary for: appendix.rst, citing.rst, 
index.rst, install.rst, intro.rst, mpi4py.MPI.rst, mpi4py.futures.rst, 
mpi4py.rst, mpi4py.run.rst, mpi4py.util.dtlib.rst, mpi4py.util.pkl5.rst, 
mpi4py.util.rst, overview.rst, reference.rst, tutorial.rst
[autosummary] generating autosummary for: 
/<>/docs/source/usrman/reference/mpi4py.MPI.rst


loading intersphinx inventory from https://docs.python.org/3/objects.inv...
loading intersphinx inventory from 
https://numpy.org/doc/stable/objects.inv...


WARNING: failed to reach any of the inventories with the following issues:
intersphinx inventory 'https://numpy.org/doc/stable/objects.inv' not 
fetchable due to : 
HTTPSConnectionPool(host='numpy.org', port=443): Max retries exceeded 
with url: /doc/stable/objects.inv (Caused by ProxyError('Cannot connect 
to proxy.', NewConnectionError('object at 0x7fec6bad3e90>: Failed to establish a new connection: [Errno 
111] Connection refused')))

WARNING: failed to reach any of the inventories with the following issues:
intersphinx inventory 'https://docs.python.org/3/objects.inv' not 
fetchable due to : 
HTTPSConnectionPool(host='docs.python.org', port=443): Max retries 
exceeded with url: /3/objects.inv (Caused by ProxyError('Cannot connect 
to proxy.', NewConnectionError('object at 0x7fec6baa4550>: Failed to establish a new connection: [Errno 
111] Connection refused')))

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
--- End Message ---
--- Begin Message ---
Source: mpi4py
Source-Version: 3.1.5-6
Done: Drew Parsons 

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated mpi4py 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, 06 May 2024 19:33:49 +0200
Source: mpi4py
Architecture: source
Version: 3.1.5-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Drew Parsons 
Closes: 1063409 1066837
Changes:
 mpi4py (3.1.5-6) unstable; urgency=medium
 .
   * debian patch intersphinx_use_local_inventory.patch uses python3
 docs when building docs. Thanks Zixing Liu from Canonical.
 Closes: #1066837, #1063409
   * add Drew Parsons as uploader
Checksums-Sha1:
 8d5341fa1910f1868786e787ac428f33f01a1125 2486 mpi4py_3.1.5-6.dsc
 a093e9e2342dc0d7a9f968354c6f816324cc34bb 13356 mpi4py_3.1.5-6.debian.tar.xz
Checksums-Sha256:
 d197fe479912e378e34c70a1d4e78752d9c0680ffb9e6e74867ea87904073a70 2486 
mpi4py_3.1.5-6.dsc
 f95bf7f585c3dad8b3726aebe5a320b3c16d5befa3ec9e539cf1e706952b5ec2 13356 
mpi4py_3.1.5-6.debian.tar.xz
Files:
 2a6a696f353995ff5067f8fd8e08b721 2486 python optional mpi4py_3.1.5-6.dsc
 718e80483b840b03c36353e7c7d95a68 13356 python optional 
mpi4py_3.1.5-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmY5TH8ACgkQVz7x5L1a
AfrSLw/6A1WV5y9hypMIvizgFhiSUxUZthUqwkSSRDccG57hNEGjQUdCS7B8TPbs
bkTp05wrk5bh2tszylv8EBfWiOLlowQGkhTqcz5mUikCyi66HjguUAOIKjpTFNHI
yFU+OL6fMdIJ1lpDNjfaKBo0kjaNRSemLZBJE3m31PptQrZrf/DoYbdGKW8WAYbN
ubBX/SAFFZuwrM3EH4L5Gi/vQO1U6XKZxCuwczsKgPfM9snDNztOwqfppAFXy10J
U0aUO90wmkuLHbd6QVcXsHKw/phagW2XHXlJ1A4mb

Bug#1066837: marked as done (mpi4py: FTBFS: Unable to generate documentation)

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2024 22:49:46 +
with message-id 
and subject line Bug#1066837: fixed in mpi4py 3.1.5-6
has caused the Debian Bug report #1066837,
regarding mpi4py: FTBFS: Unable to generate documentation
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.)


-- 
1066837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066837
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mpi4py
Severity: serious
Tags: patch
User: zixing@canonical.com
Usertags: origin-ubuntu noble ubuntu-patch

Dear Maintainer,

mpi4py failed to build from source after Python 3.12 and Sphinx upgrade.
Please find the patch attached that fixes the Sphinx documentation generation
issue and also a partial fix to the InterSphinx online requirements.

Due to a packaging issue in numpy, the InterSphinx of numpy isn't included
in the package, so linking the documentation from numpy is not possible
at the moment.

  * Un-break Sphinx documentation generation by removing PYTHONPATH overrides.
  * Add a patch to make Intersphinx read the cross-documentation index
from local filesystem. (LP: #2057848)


Thanks for considering the patch.


-- System Information:
Debian Release: bookworm/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-25-generic (SMP w/10 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru mpi4py-3.1.5/debian/control mpi4py-3.1.5/debian/control
--- mpi4py-3.1.5/debian/control 2024-03-13 12:30:07.0 -0600
+++ mpi4py-3.1.5/debian/control 2024-03-13 15:33:29.0 -0600
@@ -17,7 +16,8 @@
python3-setuptools
 Build-Depends-Indep: texinfo, texlive,
  latexmk, tex-gyre,
- texlive-latex-extra
+ texlive-latex-extra,
+ python3-doc
 Standards-Version: 4.6.2
 Vcs-Browser: https://salsa.debian.org/science-team/mpi4py
 Vcs-Git: https://salsa.debian.org/science-team/mpi4py.git
diff -Nru mpi4py-3.1.5/debian/patches/intersphinx_use_local_inventory.patch 
mpi4py-3.1.5/debian/patches/intersphinx_use_local_inventory.patch
--- mpi4py-3.1.5/debian/patches/intersphinx_use_local_inventory.patch   
1969-12-31 17:00:00.0 -0700
+++ mpi4py-3.1.5/debian/patches/intersphinx_use_local_inventory.patch   
2024-03-13 15:33:29.0 -0600
@@ -0,0 +1,18 @@
+Description: Use local InterSphinx inventory data
+Author: Zixing Liu 
+Forwarded: not-needed
+Last-Update: 2024-03-13
+
+Index: mpi4py/docs/source/usrman/conf.py
+===
+--- mpi4py.orig/docs/source/usrman/conf.py
 mpi4py/docs/source/usrman/conf.py
+@@ -90,7 +90,7 @@ autosummary_context = {
+ }
+ 
+ intersphinx_mapping = {
+-'python': ('https://docs.python.org/3/', None),
++'python': ('https://docs.python.org/3/', 
('/usr/share/doc/python3/html/objects.inv', None)),
+ 'numpy': ('https://numpy.org/doc/stable/', None),
+ }
+ 
diff -Nru mpi4py-3.1.5/debian/patches/series mpi4py-3.1.5/debian/patches/series
--- mpi4py-3.1.5/debian/patches/series  2024-02-20 03:49:49.0 -0700
+++ mpi4py-3.1.5/debian/patches/series  2024-03-13 15:29:22.0 -0600
@@ -7,3 +7,4 @@
 docs_privacy.patch
 io_long_double_i386_2d868d7.patch
 skip_testPackUnpackExternal_sparc64.patch
+intersphinx_use_local_inventory.patch
diff -Nru mpi4py-3.1.5/debian/rules mpi4py-3.1.5/debian/rules
--- mpi4py-3.1.5/debian/rules   2024-02-20 03:49:49.0 -0700
+++ mpi4py-3.1.5/debian/rules   2024-03-13 15:28:23.0 -0600
@@ -64,8 +64,7 @@
--build-args "--mpicc=/usr/bin/mpicc$(MPI) 
--mpicxx=/usr/bin/mpicxx$(MPI)"
 
 override_dh_auto_build-indep: override_dh_auto_build-arch
-   PYTHONPATH=`pybuild --print "{build_dir}"` \
-make -C docs/source/usrman/ html man info latexpdf SPHINXOPTS="-D 
today=\"$(BUILD_DATE)\""
+   make -C docs/source/usrman/ html man info latexpdf SPHINXOPTS="-D 
today=\"$(BUILD_DATE)\""
 
 override_dh_auto_install:
dh_auto_install
--- End Message ---
--- Begin Message ---
Source: mpi4py
Source-Version: 3.1.5-6
Done: Drew Parsons 

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

Bug#1014539: squirrel3: CVE-2022-30292

[Matthias Geiger]

On Thu, 18 Apr 2024 14:40:58 +0200 Matthias Geiger 
 wrote:


>
> //I have prepared a fix; however this needs the FTBFS in #997441
> adressed first.
>
> Will attach a debdiff once that has happened.
>

See attachement.

best,

--
Matthias Geiger 
Debian Maintainer
diff -Nru squirrel3-3.1/debian/changelog squirrel3-3.1/debian/changelog
--- squirrel3-3.1/debian/changelog  2024-02-16 17:46:43.0 +0100
+++ squirrel3-3.1/debian/changelog  2024-05-06 23:54:53.0 +0200
@@ -1,3 +1,11 @@
+squirrel3 (3.1-8.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Cherry-pick upstream commit as 03-fix-buffer-overflow.diff (Closes: 
#1014539)
+(CVE-2022-30292) 
+
+ -- Matthias Geiger   Mon, 06 May 2024 23:54:53 +0200
+
 squirrel3 (3.1-8.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru squirrel3-3.1/debian/patches/03-fix-buffer-overflow.diff 
squirrel3-3.1/debian/patches/03-fix-buffer-overflow.diff
--- squirrel3-3.1/debian/patches/03-fix-buffer-overflow.diff1970-01-01 
01:00:00.0 +0100
+++ squirrel3-3.1/debian/patches/03-fix-buffer-overflow.diff2024-05-06 
23:52:27.0 +0200
@@ -0,0 +1,22 @@
+From a6413aa690e0bdfef648c68693349a7b878fe60d Mon Sep 17 00:00:00 2001
+From: Alberto Demichelis 
+Date: Mon, 2 May 2022 12:04:58 +0200
+Subject: [PATCH] fix in thread.call
+
+---
+ squirrel/sqbaselib.cpp | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/squirrel/sqbaselib.cpp b/squirrel/sqbaselib.cpp
+index 662aeac..e283900 100644
+--- a/squirrel/sqbaselib.cpp
 b/squirrel/sqbaselib.cpp
+@@ -1012,6 +1012,7 @@ static SQInteger thread_call(HSQUIRRELVM v)
+ SQObjectPtr o = stack_get(v,1);
+ if(type(o) == OT_THREAD) {
+ SQInteger nparams = sq_gettop(v);
++sq_reservestack(_thread(o), nparams + 3);
+ _thread(o)->Push(_thread(o)->_roottable);
+ for(SQInteger i = 2; i<(nparams+1); i++)
+ sq_move(_thread(o),v,i);
+
diff -Nru squirrel3-3.1/debian/patches/series 
squirrel3-3.1/debian/patches/series
--- squirrel3-3.1/debian/patches/series 2024-02-16 17:46:43.0 +0100
+++ squirrel3-3.1/debian/patches/series 2024-05-06 23:52:45.0 +0200
@@ -1,2 +1,3 @@
 01-fix-spelling-errors.patch
 02-sphinx-ext.patch
+03-fix-buffer-overflow.diff

Bug#1066211:

[Arvin Sedererdj]

Control: tags -1 + patch
Description: explicitly declare returntype of main bootstrap sourcefile
 dpkg version 1.22.6 makes -Werror=implicit-function-declaration
 mandatory which breaks ATS2 build. this adds ats_int_type as return 
 type of functions that breaks the build. (keep in mind ats_int_type
 is just int, as defined in src/CBOOT/ccomp/runtime/ats_types.h)
 .
 ats2-lang (0.4.2-1.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * source only upload to enable migration (Closes: #1066211)
Author: Arvin Torshizi 
Bug-Debian: https://bugs.debian.org/1066211

---
The information above should follow the Patch Tagging Guidelines, please
checkout https://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:

Bug-Debian: https://bugs.debian.org/1066211
Forwarded: (not-needed)
Reviewed-By: 
Last-Update: 2024-05-06

--- ats2-lang-0.4.2.orig/src/CBOOT/prelude/ats_main_prelude_dats.c
+++ ats2-lang-0.4.2/src/CBOOT/prelude/ats_main_prelude_dats.c
@@ -69,30 +69,30 @@ mainats_prelude () {
 // ATSlocal_void (tmp0) ;
 
 __ats_lab_mainats_prelude:
-ATS_2d0_2e2_2e12_2prelude_2DATS_2basics_2edats__dynload () ;
-ATS_2d0_2e2_2e12_2prelude_2DATS_2bool_2edats__dynload () ;
-ATS_2d0_2e2_2e12_2prelude_2DATS_2char_2edats__dynload () ;
-ATS_2d0_2e2_2e12_2prelude_2DATS_2float_2edats__dynload () ;
-ATS_2d0_2e2_2e12_2prelude_2DATS_2integer_2edats__dynload () ;
-ATS_2d0_2e2_2e12_2prelude_2DATS_2sizetype_2edats__dynload () ;
-ATS_2d0_2e2_2e12_2prelude_2DATS_2pointer_2edats__dynload () ;
-ATS_2d0_2e2_2e12_2prelude_2DATS_2reference_2edats__dynload () ;
-ATS_2d0_2e2_2e12_2prelude_2DATS_2string_2edats__dynload () ;
-ATS_2d0_2e2_2e12_2prelude_2DATS_2lazy_2edats__dynload () ;
-ATS_2d0_2e2_2e12_2prelude_2DATS_2lazy_vt_2edats__dynload () ;
-ATS_2d0_2e2_2e12_2prelude_2DATS_2printf_2edats__dynload () ;
-ATS_2d0_2e2_2e12_2prelude_2DATS_2filebas_2edats__dynload () ;
-ATS_2d0_2e2_2e12_2prelude_2DATS_2list_2edats__dynload () ;
-ATS_2d0_2e2_2e12_2prelude_2DATS_2list_vt_2edats__dynload () ;
-ATS_2d0_2e2_2e12_2prelude_2DATS_2list0_2edats__dynload () ;
-ATS_2d0_2e2_2e12_2prelude_2DATS_2option_2edats__dynload () ;
-ATS_2d0_2e2_2e12_2prelude_2DATS_2option_vt_2edats__dynload () ;
-ATS_2d0_2e2_2e12_2prelude_2DATS_2option0_2edats__dynload () ;
-ATS_2d0_2e2_2e12_2prelude_2DATS_2array_2edats__dynload () ;
-ATS_2d0_2e2_2e12_2prelude_2DATS_2array0_2edats__dynload () ;
-ATS_2d0_2e2_2e12_2prelude_2DATS_2matrix_2edats__dynload () ;
-ATS_2d0_2e2_2e12_2prelude_2DATS_2matrix0_2edats__dynload () ;
-ATS_2d0_2e2_2e12_2prelude_2DATS_2ptrarr_2edats__dynload () ;
+ats_int_type ATS_2d0_2e2_2e12_2prelude_2DATS_2basics_2edats__dynload () ;
+ats_int_type ATS_2d0_2e2_2e12_2prelude_2DATS_2bool_2edats__dynload () ;
+ats_int_type ATS_2d0_2e2_2e12_2prelude_2DATS_2char_2edats__dynload () ;
+ats_int_type ATS_2d0_2e2_2e12_2prelude_2DATS_2float_2edats__dynload () ;
+ats_int_type ATS_2d0_2e2_2e12_2prelude_2DATS_2integer_2edats__dynload () ;
+ats_int_type ATS_2d0_2e2_2e12_2prelude_2DATS_2sizetype_2edats__dynload () ;
+ats_int_type ATS_2d0_2e2_2e12_2prelude_2DATS_2pointer_2edats__dynload () ;
+ats_int_type ATS_2d0_2e2_2e12_2prelude_2DATS_2reference_2edats__dynload () ;
+ats_int_type ATS_2d0_2e2_2e12_2prelude_2DATS_2string_2edats__dynload () ;
+ats_int_type ATS_2d0_2e2_2e12_2prelude_2DATS_2lazy_2edats__dynload () ;
+ats_int_type ATS_2d0_2e2_2e12_2prelude_2DATS_2lazy_vt_2edats__dynload () ;
+ats_int_type ATS_2d0_2e2_2e12_2prelude_2DATS_2printf_2edats__dynload () ;
+ats_int_type ATS_2d0_2e2_2e12_2prelude_2DATS_2filebas_2edats__dynload () ;
+ats_int_type ATS_2d0_2e2_2e12_2prelude_2DATS_2list_2edats__dynload () ;
+ats_int_type ATS_2d0_2e2_2e12_2prelude_2DATS_2list_vt_2edats__dynload () ;
+ats_int_type ATS_2d0_2e2_2e12_2prelude_2DATS_2list0_2edats__dynload () ;
+ats_int_type ATS_2d0_2e2_2e12_2prelude_2DATS_2option_2edats__dynload () ;
+ats_int_type ATS_2d0_2e2_2e12_2prelude_2DATS_2option_vt_2edats__dynload () ;
+ats_int_type ATS_2d0_2e2_2e12_2prelude_2DATS_2option0_2edats__dynload () ;
+ats_int_type ATS_2d0_2e2_2e12_2prelude_2DATS_2array_2edats__dynload () ;
+ats_int_type ATS_2d0_2e2_2e12_2prelude_2DATS_2array0_2edats__dynload () ;
+ats_int_type ATS_2d0_2e2_2e12_2prelude_2DATS_2matrix_2edats__dynload () ;
+ats_int_type ATS_2d0_2e2_2e12_2prelude_2DATS_2matrix0_2edats__dynload () ;
+ats_int_type ATS_2d0_2e2_2e12_2prelude_2DATS_2ptrarr_2edats__dynload () ;
 return /* (tmp0) */ ;
 } /* end of [mainats_prelude] */
 

Processed:

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1066211 [src:ats2-lang] ats2-lang: FTBFS: 
prelude/ats_main_prelude_dats.c:72:1: error: implicit declaration of function 
‘ATS_2d0_2e2_2e12_2prelude_2DATS_2basics_2edats__dynload’ 
[-Werror=implicit-function-declaration]
Added tag(s) patch.

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

Bug#1063409: marked as pending in mpi4py

[Drew Parsons]

Control: tag -1 pending

Hello,

Bug #1063409 in mpi4py 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/science-team/mpi4py/-/commit/db1d69cffc738b23899e8dafbf4c0cd4b2f8d373


add debian patch intersphinx_use_local_inventory.patch

uses python3 docs when building docs.
Thanks Zixing Liu from Canonical.

Closes: #1066837, #1063409


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1063409

Processed: Bug#1066837 marked as pending in mpi4py

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1066837 [mpi4py] mpi4py: FTBFS: Unable to generate documentation
Added tag(s) pending.

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

Bug#1066837: marked as pending in mpi4py

[Drew Parsons]

Control: tag -1 pending

Hello,

Bug #1066837 in mpi4py 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/science-team/mpi4py/-/commit/db1d69cffc738b23899e8dafbf4c0cd4b2f8d373


add debian patch intersphinx_use_local_inventory.patch

uses python3 docs when building docs.
Thanks Zixing Liu from Canonical.

Closes: #1066837, #1063409


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1066837

Processed: Bug#1063409 marked as pending in mpi4py

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1063409 [src:mpi4py] mpi4py accesses the net for the build
Added tag(s) pending.

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

Processed: FTBFS due to /usr/include/aarch64-linux-gnu/bits/math-vector.h

[Debian Bug Tracking System]

Processing control commands:

> severity 1070441 important
Bug #1070441 [src:cbmc] cmbc: arm64 FTBFS with glibc 2.38
Severity set to 'important' from 'serious'
> block 1070668 by 1070441
Bug #1070668 [src:glibc] glibc: packages FTBFS caused by vector math library 
header on arm64
1070668 was not blocked by any bugs.
1070668 was not blocking any bugs.
Added blocking bug(s) of 1070668: 1070441
> severity 1070443 important
Bug #1070443 [src:aspectc++] aspectc++: arm64 FTBFS with glibc 2.38
Severity set to 'important' from 'serious'
> block 1070668 by 1070443
Bug #1070668 [src:glibc] glibc: packages FTBFS caused by vector math library 
header on arm64
1070668 was blocked by: 1070441
1070668 was not blocking any bugs.
Added blocking bug(s) of 1070668: 1070443
> severity 1070444 important
Bug #1070444 {Done: Camm Maguire } [src:cxref] cxref: arm64 
FTBFS with glibc 2.38
Severity set to 'important' from 'serious'
> block 1070668 by 1070444
Bug #1070668 [src:glibc] glibc: packages FTBFS caused by vector math library 
header on arm64
1070668 was blocked by: 1070441 1070443
1070668 was not blocking any bugs.
Added blocking bug(s) of 1070668: 1070444
> severity 1070446 important
Bug #1070446 [src:rocm-hipamd] rocm-hipamd: arm64 FTBFS with glibc 2.38
Severity set to 'important' from 'serious'
> block 1070668 by 1070446
Bug #1070668 [src:glibc] glibc: packages FTBFS caused by vector math library 
header on arm64
1070668 was blocked by: 1070441 1070444 1070443
1070668 was not blocking any bugs.
Added blocking bug(s) of 1070668: 1070446

-- 
1070441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070441
1070443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070443
1070444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070444
1070446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070446
1070668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070668
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1070441: FTBFS due to /usr/include/aarch64-linux-gnu/bits/math-vector.h

[Aurelien Jarno]

control: severity 1070441 important
control: block 1070668 by 1070441
control: severity 1070443 important
control: block 1070668 by 1070443
control: severity 1070444 important
control: block 1070668 by 1070444
control: severity 1070446 important
control: block 1070668 by 1070446


Dear maintainers,

glibc 2.38 introduced changes to the bits/math-vector.h file on arm64 in
order to support math vector functions. This unfortunately caused the
FTBFS of your packages.

The change has been temporarily reverted in version 2.38-8 until a fix
is found, and I have opened #1070668 on the glibc side to track the
issue, with a Cc: to the arm64 porters.

I am therefore downgrading the bugs to severity important. However this
should not prevent working on a solution to the problem with the arm64
porters, and depending on the case either at the package level, or at
the upstream glibc/gcc/llvm level.

Regards
Aurelien

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

Bug#1052376: lxpanel: no longer obeys its geometry settings

[Francesco Poli]

On Tue, 23 Apr 2024 17:12:54 +0300 jim_p  wrote:
[...]
> 
> Since there is no interest from the maintainers in fixing a 6+ month old grave
> bug, I want to ask. Has anyone moved away from lxpanel or even lxde?
[...]

Hello!

I am the original submitter of this bug report.

I have recently moved away from lxpanel: I have switched to xfce4-panel.

I had to adjust my setup a little, but, overall, I am quite happy with
what I could achieve.

My current setup (within a desktop based on Fluxbox) is described in my
documentation [page].

[page]: 


I hope this helps.
Bye!



-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpgXMxKwBTVT.pgp
Description: PGP signature

Bug#1070069: fossil: CVE-2024-24795 unreleated breakage

[Bastien Roucariès]

Le lundi 29 avril 2024, 18:40:39 UTC Barak A. Pearlmutter a écrit :
> Bastien,
> 
> Okay, got it. Thanks for letting me know.
> 
> I can cherry-pick that fossil commit, but you know the right magic for
> a versioned apache2 breakage and how to deal with proposed-updates.
> So I think it would make sense for you to do all of this in a
> coordinated fashion?
> If that's okay with you, please feel free to just do a regular upload
> if you want, or an NMU, as you please.
> I will push your changes into the debian fossil branch, unless you'd
> like write access to my fossil packaging repo
>  https://people.debian.org/~bap/fossil.fsl
> which I'd be happy to set up.
> 
> Cheers,
> 
> --Barak.
> 
Thanks for you work, do you think a full backport of fossil is worthwhile for 
stable ?

Bastien


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

Bug#1070420: marked as done (src:vagrant: unsatisfied build dependency in testing: ruby-net-ftp (>= 0.2) | ruby-net-ftp (>= 0.2))

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2024 20:15:54 +
with message-id 
and subject line Bug#1070420: fixed in vagrant 2.3.7+git20230731.5fc64cde+dfsg-1
has caused the Debian Bug report #1070420,
regarding src:vagrant: unsatisfied build dependency in testing: ruby-net-ftp 
(>= 0.2) | ruby-net-ftp (>= 0.2)
to be marked as done.

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

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


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

Source: vagrant
Version: 2.3.6+dfsg-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable

Dear maintainer(s),

Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
removed from testing, but unfortunately there are multiple scenarios
where that can happen nevertheless. To uphold our social contract,
Debian requires that packages can be rebuild from source in the suite
we are shipping them, so currently this is a serious issue with your
package in testing. ruby3.2 which provides these versions of 
ruby-net-ftp is currently blocked by three RC bugs. I also note that the 
runtime dependency of bin:vagrant is non-versioned.


Can you please investigate the situation and figure out how to resolve
it? Regularly, if the build dependency is available in unstable,
helping the maintainer of your Build-Depends to enable migration to
testing is a great way to solve the issue. If your build dependency is
gone from unstable and testing, you'll have to fix the build process
in some other way.

Paul

Note: this bug report was sent after some quick manual checks using a
template. Please reach out to me if you believe I made a mistake in my
process.

[1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: vagrant
Source-Version: 2.3.7+git20230731.5fc64cde+dfsg-1
Done: Lucas Nussbaum 

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

Debian distribution maintenance software
pp.
Lucas Nussbaum  (supplier of updated vagrant package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 May 2024 21:08:41 +0200
Source: vagrant
Architecture: source
Version: 2.3.7+git20230731.5fc64cde+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Lucas Nussbaum 
Closes: 1070420
Changes:
 vagrant (2.3.7+git20230731.5fc64cde+dfsg-1) unstable; urgency=medium
 .
   [ Antonio Terceiro ]
   * Drop myself from Uploaders
 .
   [ Lucas Nussbaum ]
   * New upstream version 2.3.7+git20230731.5fc64cde+dfsg
 + This is the last commit before the license change to BUSL.
   * Add patch: 0009-Raise-error-if-openssl-headers-not-found.patch
   * Add build-dep on libssl-dev and switch to Architecture: any to build the
 vagrant_ssl extension
   * Fix rubygems-integration path due to the above arch:any change
   * Drop Build-dep on ruby-net-ftp, which is provided by libruby3.X anyway.
 Closes: #1070420
   * Remove watch file: we don't expect upstream updates
   * Add patch 0010-Remove-shebang-from-bash-completion-file.patch to fix
 lintian warning.
Checksums-Sha1:
 eee205a181034b05eb8b9ad83ffb89abaebee5dc 2850 
vagrant_2.3.7+git20230731.5fc64cde+dfsg-1.dsc
 ef0f0bc1a4197501b9a450a29f0c130d4e0a621d 1894748 
vagrant_2.3.7+git20230731.5fc64cde+dfsg.orig.tar.xz
 7eddd398161025cd378398e63e818bcd853a885f 16952 
vagrant_2.3.7+git20230731.5fc64cde+dfsg-1.debian.tar.xz
 f60e9d518236336deae93f016aa0303789f9093f 11025 
vagrant_2.3.7+git20230731.5fc64cde+dfsg-1_source.buildinfo
Checksums-Sha256:
 6efdd239246811af8ca5c35e9278c06539b3707fcf9af8f9f537699d302ad576 2850 
vagrant_2.3.7+git20230731.5fc64cde+dfsg-1.dsc
 ccddc8f97704a7d393d932ec0bd3d46b85ad71a7ca5c6c74ee5d7163b96925d2 1894748 
vagrant_2.3.7+git20230731.5fc64cde+dfsg.orig.tar.xz
 fa67d6c4791d69d3a42e665f404498028f5fb64ca7c3a657ad2822c9f6863305 16952 
vagrant

Bug#1066213: marked as done (slrn: FTBFS: misc.c:376:4: error: implicit declaration of function ‘VA_COPY’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2024 20:15:34 +
with message-id 
and subject line Bug#1066213: fixed in slrn 1.0.3+dfsg-7
has caused the Debian Bug report #1066213,
regarding slrn: FTBFS: misc.c:376:4: error: implicit declaration of function 
‘VA_COPY’ [-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.)


-- 
1066213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066213
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: slrn
Version: 1.0.3+dfsg-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):
> cd /<>/src/objs && gcc -c -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -Wall -Wformat=2 -Wunused -Wundef 
> -Wextra -Wswitch-enum -Wpointer-arith -Wnested-externs -Wbad-function-cast 
> -Wcast-qual -Wcast-align -Wshadow -Dunix -Wdate-time -D_FORTIFY_SOURCE=2 
> -I/usr/lib/x86_64-linux-gnu/include  
> -DSLRN_SLANG_DIR=\"/usr/share/slrn/slang\" -DSLRN_LIB_DIR=\"/usr/share/slrn\" 
> -DSLRN_CONF_DIR=\"/etc/news\" -DNLS_LOCALEDIR=\"/usr/share/locale\"  
> /<>/src/misc.c
> /<>/src/misc.c: In function ‘top_status_line_cb’:
> /<>/src/misc.c:243:54: warning: ‘%x’ yields only last 2 digits 
> of year in some locales [-Wformat-y2k]
>   243 | if (0 != (*len = strftime (buf, sizeof(buf), "%x", 
> localtime(&now
>   |  ^~~~
> /<>/src/misc.c: In function ‘slrn_verror’:
> /<>/src/misc.c:376:4: error: implicit declaration of function 
> ‘VA_COPY’ [-Werror=implicit-function-declaration]
>   376 |VA_COPY(ap1, ap);
>   |^~~
> /<>/src/misc.c:376:4: warning: nested extern declaration of 
> ‘VA_COPY’ [-Wnested-externs]
> /<>/src/misc.c: In function ‘slrn_mail_file’:
> /<>/src/misc.c:1097:82: warning: unused parameter ‘subject’ 
> [-Wunused-parameter]
>  1097 | int slrn_mail_file (char *file, int edit, unsigned int editline, char 
> *to, char *subject) /*{{{*/
>   |   
>  ~~^~~
> /<>/src/misc.c: In function ‘create_edit_command’:
> /<>/src/misc.c:1431:9: warning: format not a string literal, 
> argument types not checked [-Wformat-nonliteral]
>  1431 | return slrn_strdup_printf (edit, file);
>   | ^~
> /<>/src/misc.c:1436:9: warning: format not a string literal, 
> argument types not checked [-Wformat-nonliteral]
>  1436 | cmd1 = slrn_strdup_printf (edit, (int) line);
>   | ^~~~
> /<>/src/misc.c:1444:11: warning: format not a string literal, 
> argument types not checked [-Wformat-nonliteral]
>  1444 |   return slrn_strdup_printf (edit, line, file);
>   |   ^~
> /<>/src/misc.c:1445:9: warning: format not a string literal, 
> argument types not checked [-Wformat-nonliteral]
>  1445 | else return slrn_strdup_printf (edit, file, line);
>   | ^~~~
> /<>/src/misc.c: In function ‘generic_mini_complete’:
> /<>/src/misc.c:1944:26: warning: cast between incompatible 
> function types from ‘void (*)(void *, size_t,  size_t,  int (*)(const void *, 
> const void *))’ {aka ‘void (*)(void *, long unsigned int,  long unsigned int, 
>  int (*)(const void *, const void *))’} to ‘void (*)(char **, unsigned int,  
> unsigned int,  int (*)(char **, char **))’ [-Wcast-function-type]
>  1944 |  qsort_fun = (void (*)(char **, unsigned int,
>   |  ^
> /<>/src/misc.c:1962:25: warning: cast between incompatible 
> function types from ‘int (*)(char *)’ to ‘int (*)(void)’ 
> [-Wcast-function-type]
>  1962 | if ((n < 2) && ((FVOID_STAR) Complete_Open == (FVOID_STAR) 
> dir_findfirst) &&
>   | ^
> /<>/src/misc.c:1962:55: warning: cast between incompatible 
> function types from ‘int (*)(char *)’ to ‘int (*)(void)’ 
> [-Wcast-function-type]
>  1962 | if ((n < 2) && ((FVOID_STAR) Complete_Open == (FVOID_STAR) 
> dir_findfirst) &&
>   |   ^
> /<>/src/misc.c: 

Bug#1069009: marked as done (dub: hard-coded dependeny on pre-t64 libraries)

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2024 19:28:41 +
with message-id 
and subject line Bug#1069009: fixed in dub 1.36.0-2
has caused the Debian Bug report #1069009,
regarding dub: hard-coded dependeny on pre-t64 libraries
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.)


-- 
1069009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069009
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dub
Version: 1.36.0-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

dub has a hard-coded dependency on libcurl3-gnutls | libcurl4. Both
packages were renamed as part of the time_t transition and the
dependency needs to be updated.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: dub
Source-Version: 1.36.0-2
Done: Matthias Klumpp 

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

Debian distribution maintenance software
pp.
Matthias Klumpp  (supplier of updated dub 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, 06 May 2024 20:52:58 +0200
Source: dub
Architecture: source
Version: 1.36.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian D Language Group 
Changed-By: Matthias Klumpp 
Closes: 1067825 1069009
Changes:
 dub (1.36.0-2) unstable; urgency=medium
 .
   * Update library dependencies for t64 transition (Closes: #1069009)
   * Build with the Debian default D compiler
 - This resolves some issues with the GDC builds by not using
   GDC on architectures where LDC works.
   It may also help resolving some FTBFS issues and likely closes: #1067825
Checksums-Sha1:
 fc37b8931715753f1ff189e9d3fb25c590c7cf51 1948 dub_1.36.0-2.dsc
 4090e0cb73bf9f05f11646f78e3a2c03edaf1336 1502081 dub_1.36.0.orig.tar.gz
 d64bcd431ede3e9713447e4eb03959576a5fff87 4892 dub_1.36.0-2.debian.tar.xz
 5c3f195ab48d2060f8b03f1f4a683f9bd9e4113f 8603 dub_1.36.0-2_source.buildinfo
Checksums-Sha256:
 310946e92ce832385ace4197be69a12004a18998e29a2a60b28c6a85682fe452 1948 
dub_1.36.0-2.dsc
 16ac09875889af03abeeca9b60777ee51611c86b3efe5869db3331d2fd97fd2b 1502081 
dub_1.36.0.orig.tar.gz
 06cd9cf0ffb26222921303eb19fb271e01a18648d1a3656a38b96c6f4c5627b9 4892 
dub_1.36.0-2.debian.tar.xz
 b48564e495ee7529bb06dcd30e22df1bdf4cca1f822973ad0a61e8857f063c02 8603 
dub_1.36.0-2_source.buildinfo
Files:
 560f07d610c9d09e748e3d0d7fb03e82 1948 devel optional dub_1.36.0-2.dsc
 9bff7e4bd3a36bfa94ac4c379ddb6d97 1502081 devel optional dub_1.36.0.orig.tar.gz
 9db1e644bbdf6d0a3e61842abe78a4c5 4892 devel optional dub_1.36.0-2.debian.tar.xz
 4893dd9bcd93f440e0baa5031a82e218 8603 devel optional 
dub_1.36.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCAAtFiEE0zo/DKFrCsxRpgc4SUyKX79N7OsFAmY5KD4PHG1ha0BkZWJp
YW4ub3JnAAoJEElMil+/TezrDBgP/0uaEr3OemMylXUA34/Skz7Bl/afk5u90k3y
QBUuqEAwcm10nuVp8a8JuQ4aS35+s3OzFJr3vpk/vXHMad/AzovkWpbElr+Oi8ew
tizJi8XGWpQhpF02V7KW60vNM9rPtrkDhAvXpTh8QtOvY6pEqvq0B5K4nPEPAN0P
ilbY5p/x7ZkC7x6K6yM8Utgdx9aVypgpOOMo/Fz+XW4VagWpQMzuIDD9nyK5QWdD
aKz+L8DOUjczc9qGoKKuwphJprrJN3g60Q3gNNHpSK/ZGhTBk8m452rl7v20O7lr
oAtzIUKzSEUtk/yHV5t7CiqUqCRYJkvpPxYobL7u+0f5DRtQwbShqhPoFNFTzpTo
110GQNMk8SK3J3M9qhCqa1Bawpf4UfZIGlIhCcFxTF8/2Sr+C5jbBcCEZR4xS0lN
xPgiuS/5jGifPOUcxabwn+WV9r1rqY9U6tG0s3AXoh4xej7YTqr3SLqK8Ia1rz7o
xbtltHCthhBzVF2UnDc2TrybKx1VR8Fjv6aV+V1vx96Jo6NUWbOfqcwKTgOVf0j1
UCYgK20SdpHSf/iVezuYn3x4RTj1emcgbBtBzhpvr6rwAsuqVB2piRvWpXa9kARX
H3Y8trXIHS1SZ5mX5v9JtuisdQyYeFMVeS++zO84Ebnh/RkB+jde9KvQ/4sos1WR
aRlyaxr9
=7Y19
-END PGP SIGNATURE-



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

Bug#1067825: marked as done (dub: FTBFS on armhf, mips64el, ppc64el)

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2024 19:28:41 +
with message-id 
and subject line Bug#1067825: fixed in dub 1.36.0-2
has caused the Debian Bug report #1067825,
regarding dub: FTBFS on armhf, mips64el, ppc64el
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.)


-- 
1067825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067825
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dub
Version: 1.36.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=dub&arch=armhf&ver=1.36.0-1&stamp=1708295658&raw=0

/usr/lib/gcc/arm-linux-gnueabihf/13/include/d/std/format/spec.d:258:33: note: 
scope variable ‘this’ assigned to non-scope parameter ‘e’ calling ‘put’
  258 | put(writer, trailing[0 .. i]);
  | ^
source/dub/internal/configy/Exceptions.d:335:31: warning: ‘@safe’ function 
‘formatMessage’ calling ‘formattedWrite’ [-Wdeprecated]
  335 | formattedWrite(sink, fmt, this.fieldNames.length, 
this.fieldNames);
  |   ^
/usr/lib/gcc/arm-linux-gnueabihf/13/include/d/std/format/write.d:537:34: note: 
which calls ‘std.format.spec.FormatSpec!char.FormatSpec.writeUpToNextSpec!(void 
delegate(in char[]) @safe).writeUpToNextSpec’
  537 | while (spec.writeUpToNextSpec(w))
  |  ^
/usr/lib/gcc/arm-linux-gnueabihf/13/include/d/std/format/spec.d:258:33: note: 
which would be ‘@system’ because of:
  258 | put(writer, trailing[0 .. i]);
  | ^
/usr/lib/gcc/arm-linux-gnueabihf/13/include/d/std/format/spec.d:258:33: note: 
scope variable ‘this’ assigned to non-scope parameter ‘e’ calling ‘put’
  258 | put(writer, trailing[0 .. i]);
  | ^
virtual memory exhausted: Cannot allocate memory

make[1]: *** [debian/rules:16: override_dh_auto_build] Error 1


https://buildd.debian.org/status/fetch.php?pkg=dub&arch=mips64el&ver=1.36.0-1&stamp=1708295519&raw=0

gdmd -run /<>/build.d \
-g -O -wi -release
Wrote version_.d` file with version: 1.36.0-1
No compiler has been found in the PATH. Attempted values: ["dmd", "ldmd2", 
"gdmd"]
Make sure one of those is in the PATH, or set the `DMD` variable
make[1]: *** [debian/rules:16: override_dh_auto_build] Error 1


https://buildd.debian.org/status/fetch.php?pkg=dub&arch=ppc64el&ver=1.36.0-1&stamp=1708295464&raw=0

gdmd -run /<>/build.d \
-g -O -wi -release
/<>/build.d:23:8: error: unable to read module ‘algorithm’
   23 | import std.algorithm;
  |^
/<>/build.d:23:8: note: Expected 'std/algorithm.d' or 
'std/algorithm/package.d' in one of the following import paths:
   23 | import std.algorithm;
  |^
import path[0] = /usr/lib/gcc/powerpc64le-linux-gnu/13/include/d
make[1]: *** [debian/rules:16: override_dh_auto_build] Error 1


Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: dub
Source-Version: 1.36.0-2
Done: Matthias Klumpp 

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

Debian distribution maintenance software
pp.
Matthias Klumpp  (supplier of updated dub 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, 06 May 2024 20:52:58 +0200
Source: dub
Architecture: source
Version: 1.36.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian D Language Group 
Changed-By: Matthias Klumpp 
Closes: 1067825 1069009
Changes:
 dub (1.36.0-2) unstable; urgency=medium
 .
   * Update library dependencies for t64 transition (Closes: #1069009)
   * Build with the Debian default D compiler
 - This resolves some issues with the GDC builds by not using
   GDC on architectures where LDC works.
   It may also help resolving some FTBFS issues and likely closes: #1067825
Checksums-Sha1:
 fc37b8931715753f1ff189e9d3fb25c590c7cf51 1948 dub_1.36.0-2.dsc
 4090e0cb73bf9f05f1164

Bug#1070420: marked as pending in vagrant

[Lucas Nussbaum]

Control: tag -1 pending

Hello,

Bug #1070420 in vagrant 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/ruby-team/vagrant/-/commit/4590433e6c69b23dc11ae4eb24851ecbed825326


Drop Build-dep on ruby-net-ftp, which is provided by libruby3.X anyway. Closes: 
#1070420


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1070420

Processed: Bug#1070420 marked as pending in vagrant

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1070420 [src:vagrant] src:vagrant: unsatisfied build dependency in 
testing: ruby-net-ftp (>= 0.2) | ruby-net-ftp (>= 0.2)
Added tag(s) pending.

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

Bug#1070663: Unable to lock an existing session

[martin f krafft]

Package: xautolock
Version: 1:2.2-8
Severity: critical

This may be related to #1022781 or not.

I have xautolock running:

% ps -fC xautolock
UID  PIDPPID  C STIME TTY  TIME CMD
madduck 27332421  0 May05 ?00:00:53 xautolock -time 3 -locker 
xsecurelock && autorandr -- …

and yet:

% xautolock -locknow
% echo $?
0

It exits 0, but nothing happens. If I use strace on the main 
process, there is also zero activity reported.

Moreover, despite being set to lock after 3 minutes, the main 
xautolock process does not lock the display.

This has happened multiple times, and each time, only a restart of 
the main xautolock process makes things work again. So if I don't 
restart the process regularly (daily? hourly?), then occasionally, 
the system will not lock as expected, and that is a huge security 
problem, hence the critical severity.

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

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

Versions of packages xautolock depends on:
ii  libc6 2.37-17
ii  libx11-6  2:1.8.7-1
ii  libxext6  2:1.3.4-1+b1
ii  libxss1   1:1.2.3-1

Versions of packages xautolock recommends:
ii  suckless-tools  47-1

xautolock suggests no packages.

-- debconf-show failed


-- 
 .''`.   martin f. krafft 
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems

Bug#1070459: psortb: FTBFS: binding.c:52:13: error: implicit declaration of function ‘free’

[Andreas Tille]

Hi,

I've fixed the original error in Git but Salsa CI shows another one[1]
which is more tricky since it involves a header file for a perl module
and I have no idea how to fix this.  Any help from the team is welcome.

Kind regards
   Andreas.

[1] https://salsa.debian.org/med-team/psortb/-/jobs/5693162

-- 
https://fam-tille.de

Processed: Re: Bug#1070644: gnome-remote-desktop: System .service file enabled but not the user one?

[Debian Bug Tracking System]

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

> forwarded 1070644 
> https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/260
Bug #1070644 [gnome-remote-desktop] gnome-remote-desktop: System .service file 
enabled but not the user one?
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/260'.
>
End of message, stopping processing here.

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

Processed: [bts-link] source package src:newsboat

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:newsboat
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1054680 (http://bugs.debian.org/1054680)
> # Bug title: newsboat: FTBFS: test/cliargsparser.cpp:1:10: fatal error: 
> 3rd-party/catch.hpp: No such file or directory
> #  * https://github.com/newsboat/newsboat/issues/2716
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 1054680 + fixed-upstream
Bug #1054680 [src:newsboat] newsboat: FTBFS: test/cliargsparser.cpp:1:10: fatal 
error: 3rd-party/catch.hpp: No such file or directory
Added tag(s) fixed-upstream.
> usertags 1054680 - status-open
Usertags were: status-open.
There are now no usertags set.
> usertags 1054680 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:golang-github-lucas-clemente-quic-go

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package 
> src:golang-github-lucas-clemente-quic-go
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1066780 (http://bugs.debian.org/1066780)
> # Bug title: golang-github-lucas-clemente-quic-go: FTBFS: dh_auto_test: 
> error: cd _build && go test -vet=off -v -p 8 github.com/quic-go/quic-go 
> github.com/quic-go/quic-go/example github.com/quic-go/quic-go/example/client 
> github.com/quic-go/quic-go/example/echo 
> github.com/quic-go/quic-go/fuzzing/frames 
> github.com/quic-go/quic-go/fuzzing/frames/cmd 
> github.com/quic-go/quic-go/fuzzing/handshake 
> github.com/quic-go/quic-go/fuzzing/handshake/cmd 
> github.com/quic-go/quic-go/fuzzing/header 
> github.com/quic-go/quic-go/fuzzing/header/cmd 
> github.com/quic-go/quic-go/fuzzing/internal/helper 
> github.com/quic-go/quic-go/fuzzing/tokens 
> github.com/quic-go/quic-go/fuzzing/transportparameters 
> github.com/quic-go/quic-go/fuzzing/transportparameters/cmd 
> github.com/quic-go/quic-go/http3 
> github.com/quic-go/quic-go/integrationtests/gomodvendor 
> github.com/quic-go/quic-go/integrationtests/self 
> github.com/quic-go/quic-go/integrationtests/tools 
> github.com/quic-go/quic-go/integrationtests/tools/israce 
> github.com/quic-go/quic-go/integrationtests/tools/proxy 
> github.com/quic-go/quic-go/integrationtests/versionnegotiation 
> github.com/quic-go/quic-go/internal/ackhandler 
> github.com/quic-go/quic-go/internal/congestion 
> github.com/quic-go/quic-go/internal/flowcontrol 
> github.com/quic-go/quic-go/internal/handshake 
> github.com/quic-go/quic-go/internal/logutils 
> github.com/quic-go/quic-go/internal/mocks 
> github.com/quic-go/quic-go/internal/mocks/ackhandler 
> github.com/quic-go/quic-go/internal/mocks/logging 
> github.com/quic-go/quic-go/internal/mocks/quic 
> github.com/quic-go/quic-go/internal/mocks/tls 
> github.com/quic-go/quic-go/internal/protocol 
> github.com/quic-go/quic-go/internal/qerr 
> github.com/quic-go/quic-go/internal/qtls 
> github.com/quic-go/quic-go/internal/testutils 
> github.com/quic-go/quic-go/internal/utils 
> github.com/quic-go/quic-go/internal/utils/linkedlist 
> github.com/quic-go/quic-go/internal/utils/ringbuffer 
> github.com/quic-go/quic-go/internal/wire 
> github.com/quic-go/quic-go/interop/client 
> github.com/quic-go/quic-go/interop/http09 
> github.com/quic-go/quic-go/interop/server 
> github.com/quic-go/quic-go/interop/utils github.com/quic-go/quic-go/logging 
> github.com/quic-go/quic-go/qlog github.com/quic-go/quic-go/quicvarint 
> returned exit code 1
> #  * https://github.com/quic-go/quic-go/issues/4338
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 1066780 + fixed-upstream
Bug #1066780 [src:golang-github-lucas-clemente-quic-go] 
golang-github-lucas-clemente-quic-go: FTBFS: dh_auto_test: error: cd _build && 
go test -vet=off -v -p 8 github.com/quic-go/quic-go 
github.com/quic-go/quic-go/example github.com/quic-go/quic-go/example/client 
github.com/quic-go/quic-go/example/echo 
github.com/quic-go/quic-go/fuzzing/frames 
github.com/quic-go/quic-go/fuzzing/frames/cmd 
github.com/quic-go/quic-go/fuzzing/handshake 
github.com/quic-go/quic-go/fuzzing/handshake/cmd 
github.com/quic-go/quic-go/fuzzing/header 
github.com/quic-go/quic-go/fuzzing/header/cmd 
github.com/quic-go/quic-go/fuzzing/internal/helper 
github.com/quic-go/quic-go/fuzzing/tokens 
github.com/quic-go/quic-go/fuzzing/transportparameters 
github.com/quic-go/quic-go/fuzzing/transportparameters/cmd 
github.com/quic-go/quic-go/http3 
github.com/quic-go/quic-go/integrationtests/gomodvendor 
github.com/quic-go/quic-go/integrationtests/self 
github.com/quic-go/quic-go/integrationtests/tools 
github.com/quic-go/quic-go/integrationtests/tools/israce 
github.com/quic-go/quic-go/integrationtests/tools/proxy 
github.com/quic-go/quic-go/integrationtests/versionnegotiation 
github.com/quic-go/quic-go/internal/ackhandler 
github.com/quic-go/quic-go/internal/congestion 
github.com/quic-go/quic-go/internal/flowcontrol 
github.com/quic-go/quic-go/internal/handshake 
github.com/quic-go/quic-go/internal/logutils 
github.com/quic-go/quic-go/internal/mocks 
github.com/quic-go/quic-go/internal/mocks/ackhandler 
github.com/quic-go/quic-go/internal/mocks/logging 
github.com/quic-go/quic-go/internal/mocks/quic 
github.com/quic-go/quic-go/internal/mocks/tls 
github.com/quic-go/quic-go/internal/protocol 
github.com/quic-go/quic-go/internal/qerr 
github.com/quic-go/quic-go/internal/qtls 
github.com/quic-go/quic-go/internal/testutils 
github.com/quic-go/quic-go/internal/utils 
github.com/quic-go/quic-go/internal/utils/linkedlist 
github.com/quic-go/quic-go/internal/utils/ringbuffer 
github.com/quic-go

Processed: [bts-link] source package src:openttd

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:openttd
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1070208 (http://bugs.debian.org/1070208)
> # Bug title: openttd: cmake licensing concern for openttd 14.0 source package
> #  * https://github.com/OpenTTD/OpenTTD/pull/12603
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 1070208 + fixed-upstream
Bug #1070208 [src:openttd] openttd: cmake licensing concern for openttd 14.0 
source package
Added tag(s) fixed-upstream.
> usertags 1070208 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#1070644: gnome-remote-desktop: System .service file enabled but not the user one?

[Jeremy Bícha]

Control: forwarded -1
https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/260

It looks like upstream is proposing to split gnome-remote-desktop's
new systemd systemd service into two system services to fix this
issue. It's unclear whether they will land this in 46.x

Thank you,
Jeremy Bícha

Bug#1070444: marked as done (cxref: arm64 FTBFS with glibc 2.38)

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2024 17:19:10 +
with message-id 
and subject line Bug#1070444: fixed in cxref 1.6e-6
has caused the Debian Bug report #1070444,
regarding cxref: arm64 FTBFS with glibc 2.38
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.)


-- 
1070444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070444
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cxref
Version: 1.6e-5
Severity: serious
Tags: ftbfs trixie sid

Hi Maintainer

As can be seen in reproducible builds [1], cxref FTBFS on arm64 with
glibc 2.38.  I've copied what I hope is the relevant part of the log
below.

A bug was filed against glibc [2], but it seems glibc upstream do not
consider it a bug in glibc.

Regards
Graham


[1] https://tests.reproducible-builds.org/debian/rb-pkg/cxref.html
[2] https://sourceware.org/bugzilla/show_bug.cgi?id=30909


../src/cxref  -D_Float128='long double' -O. -NREADME-TMP -xref README.c
/usr/include/aarch64-linux-gnu/bits/math-vector.h:30: cxref: syntax error

The previous 10, current and next 10 symbols are:
-10 | 258 :   IDENTIFIER : __overflow
 -9 |  40 :  '(' : (
 -8 | 259 :TYPE_NAME : FILE
 -7 |  42 :  '*' : *
 -6 |  44 :  ',' : ,
 -5 | 296 :  INT : int
 -4 |  41 :  ')' : )
 -3 |  59 :  ';' : ;
 -2 | 285 :  TYPEDEF : typedef
 -1 | 258 :   IDENTIFIER : __Float32x4_t
  0 | 258 :   IDENTIFIER : __f32x4_t
  1 |  59 :  ';' : ;
  2 | 285 :  TYPEDEF : typedef
  3 | 258 :   IDENTIFIER : __Float64x2_t
  4 | 258 :   IDENTIFIER : __f64x2_t
  5 |  59 :  ';' : ;
  6 | 285 :  TYPEDEF : typedef
  7 | 258 :   IDENTIFIER : __SVFloat32_t
  8 | 258 :   IDENTIFIER : __sv_f32_t
  9 |  59 :  ';' : ;
 10 | 285 :  TYPEDEF : typedef
--- End Message ---
--- Begin Message ---
Source: cxref
Source-Version: 1.6e-6
Done: Camm Maguire 

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

Debian distribution maintenance software
pp.
Camm Maguire  (supplier of updated cxref 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, 06 May 2024 12:49:07 -0400
Source: cxref
Architecture: source
Version: 1.6e-6
Distribution: unstable
Urgency: medium
Maintainer: Camm Maguire 
Changed-By: Camm Maguire 
Closes: 979632 1070444
Changes:
 cxref (1.6e-6) unstable; urgency=medium
 .
   * Bug fix: "arm64 FTBFS with glibc 2.38", thanks to Graham Inggs
 (Closes: #1070444).
   * Bug fix: "no output -- tmpfile is depreced", thanks to Martin Kovarik
 (Closes: #979632).
Checksums-Sha1:
 001bbefeac7a40120a3b69e7e8bbea5efec2a8e3 1943 cxref_1.6e-6.dsc
 653532e570edbb39fcd3eccbbc6295773b045da2 33520 cxref_1.6e-6.debian.tar.xz
 8d6ccec12ed56d316c0e60857b9abf5bb2e6ca7f 7183 cxref_1.6e-6_source.buildinfo
Checksums-Sha256:
 51c78333ac54ab7804a387f6c9864672a54503ab64ff6ae056bd9bbe322ebe39 1943 
cxref_1.6e-6.dsc
 6a8f5f5bcd7340be4770e9f8cbb46d3f596253e4cd6b6b310cfbde61b1bc3025 33520 
cxref_1.6e-6.debian.tar.xz
 a95f3073bf46a1f975d62b7da3c7006c6fbbf6f945079f35bce30acb6ea6df64 7183 
cxref_1.6e-6_source.buildinfo
Files:
 d805ecd7f12dfc52c6ab608af24b0768 1943 devel optional cxref_1.6e-6.dsc
 b8331d7da12de8191c95b3748842102f 33520 devel optional 
cxref_1.6e-6.debian.tar.xz
 3eb005b1e8f783c2f5fd77ce9d189895 7183 devel optional 
cxref_1.6e-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/iFPNjaXdzJC6BbsuEXOUQ+bcU0FAmY5CmMACgkQuEXOUQ+b
cU1rPA//T//ICuCpV/rjMraRiQeyfGVvlFW1IKV1puE20K7V9Qmw91q+ikn4UTTq
k03QlVeHSY0W1u/EKaKXCKRrZ+Cxinls4qMDe1J1fM3loWv5LkciyRZurxyo6/et
4yybM/kAL5DFZUMmpMiwzXkPwq+FjzspggCf7x7EPyJpEmYAge3LoYtkCnUKt2fA
kDGCV8Qp8dfJT6zr+EVOPz5ZbCE9Xg2XbZL1uBQTmUavj9/0OZz+BLck6zU1mL+9
X6atByCQ/sIj0GZtvQCcUjbJUUDD83yPg2kUxvZagiVFWohT0Mbwu7utTxra6PSv
7tZV0IuB0Fise+ULCJvMf3rEizehcxMIZmJLEuEd5KEI+Bd5ZoMjauedWVVXjlUi
hpKB9bOJj+gJf+qZjIwhcmfyjRiX9NYaE6KAfax2ffwcPWfxVaE+dgjB8nQ6uQDB
cBhRrxZ3vrGO85ER7y8H3n0dfwqVY261hyfff3Q8PgyKGTjTupVk2Eq8zqQUg2fj
i0XoBrl4xloSQR

Bug#1064486: rnp: FTBFS: Errors while running CTest

[Andreas Metzler]

Control: tags -1 fixed-upstream

On 2024-05-05 Andreas Metzler  wrote:
> On 2024-05-04 Santiago Vila  wrote:
> > found 1064486 0.16.3-1
> > tags 1064486 + ftbfs bookworm trixie sid
> > thanks

> > El 20/4/24 a las 14:12, Andreas Metzler escribió:
> > > FWIW I also get testsuite errors on current sid on amd64
> > > The following tests FAILED:
> > >   83 - rnp_tests.test_ffi_decrypt_wrong_mpi_bits (Failed)
> > >   90 - rnp_tests.test_ffi_security_profile (Failed)
> > >  174 - rnp_tests.test_key_add_userid (Failed)
> > >  254 - cli_tests-EncryptElgamal (Failed)

> > Hello. This is also happening in bookworm, I assume that for the same 
> > underlying reason,
> > so I'm adding the bookworm version.
> [...]

> Hmm. Perhaps a timebomb, i.e. one of the keys used in the testsuite
> expired.


Hello,

Indeed it is a timebomb. Since 0.17.1 works I had a look at
git log src/tests/key-add-userid.cpp
and found

commit 07745e2e5fa6078b95fb5c24575929eb2a19ca03
Author: Nickolay Olshevsky 
Date:   Fri Jan 19 16:05:32 2024 +0200

Update tests to match SHA1 cutoff date for key signatures.
[...]
 selfsig0.primary = false;
+auto curtime = global_ctx.time();
+global_ctx.set_time(curtime > SHA1_KEY_FROM ? SHA1_KEY_FROM - 100 : 0);


SHA1_KEY_FROM is #defined in src/tests/support.h to 1705629600, which
was Fri Jan 19 03:00:00 CET 2024.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Processed: Re: Bug#1064486: rnp: FTBFS: Errors while running CTest

[Debian Bug Tracking System]

Processing control commands:

> tags -1 fixed-upstream
Bug #1064486 [src:rnp] rnp: FTBFS: Errors while running CTest
Added tag(s) fixed-upstream.

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

Bug#1070658: FTBFS: error: expected ‘)’ before ‘maxLength’

[Stefano Rivera]

Source: clickhouse
Version: 18.16.1+ds-7.4
Severity: serious
Tags: ftbfs
Justification: ftbfs

clickhouse FTBFS in unstable:

[ 87%] Building CXX object 
dbms/CMakeFiles/dbms.dir/src/Storages/MergeTree/LevelMergeSelector.cpp.o
cd /<>/obj-x86_64-linux-gnu/dbms && /usr/bin/c++ 
-DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_PROGRAM_OPTIONS_NO_LIB 
-DBOOST_SYSTEM_DYN_LINK -DBOOST_SYSTEM_NO_LIB -Ddbms_EXPORTS 
-I/<>/contrib/cityhash102/include 
-I/<>/libs/libpocoext/include 
-I/<>/libs/libmysqlxx/include 
-I/<>/contrib/libbtrie/include -isystem 
/<>/contrib/libdivide -isystem /<>/dbms/src -isystem 
/<>/obj-x86_64-linux-gnu/dbms/src -isystem 
/<>/contrib/libpcg-random/include -isystem 
/<>/libs/libcommon/include -isystem 
/<>/obj-x86_64-linux-gnu/libs/libcommon/include -isystem 
/usr/include/metrohash -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2  -pipe  
-fno-omit-frame-pointer  -Wall  -Wnon-virtual-dtor -Wextra -O2 -g -DNDEBUG -O3  
-std=c++17 -flto=auto -fno-fat-lto-objects -fPIC   
-fno-tree-loop-distribute-patterns -MD -MT 
dbms/CMakeFiles/dbms.dir/src/Storages/MergeTree/LevelMergeSelector.cpp.o -MF 
CMakeFiles/dbms.dir/src/Storages/MergeTree/LevelMergeSelector.cpp.o.d -o 
CMakeFiles/dbms.dir/src/Storages/MergeTree/LevelMergeSelector.cpp.o -c 
/<>/dbms/src/Storages/MergeTree/LevelMergeSelector.cpp
In file included from 
/<>/dbms/src/Interpreters/InterserverIOHandler.h:8,
 from 
/<>/dbms/src/Storages/MergeTree/DataPartsExchange.h:3,
 from 
/<>/dbms/src/Storages/MergeTree/DataPartsExchange.cpp:1:
/usr/include/Poco/BinaryWriter.h:137:14: error: expected ‘)’ before ‘maxLength’
  137 | void writeCString(const char* cString, std::streamsize 
maxLength = DEFAULT_MAX_CSTR_LENGTH);
  |  ^~~~
/usr/include/Poco/BinaryWriter.h:137:14: note: to match this ‘(’
  137 | void writeCString(const char* cString, std::streamsize 
maxLength = DEFAULT_MAX_CSTR_LENGTH);
  |  ^~~~

Full build log:
https://debusine.debian.net/artifact/66597/clickhouse_18.16.1+ds-7.4_amd64-2024-05-06T16:48:46Z.build

Stefano

Processed: Re: mpi4py: FTBFS: Segmentation fault in tests

[Debian Bug Tracking System]

Processing control commands:

> tags -1 ftbfs
Bug #1066449 [src:mpi4py] mpi4py: FTBFS: Segmentation fault in tests
Ignoring request to alter tags of bug #1066449 to the same tags previously set

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

Bug#1066449: mpi4py: FTBFS: Segmentation fault in tests

[Drew Parsons]

Source: mpi4py
Followup-For: Bug #1066449
Control: tags -1 ftbfs

The bug report stopped scanning at the first "error", which is not an
error (it's a check).  The last error is the relevant one

testIReadIWrite (test_io.TestIOSelf.testIReadIWrite) ... ok
testIReadIWriteAll (test_io.TestIOSelf.testIReadIWriteAll) ... 
[ip-10-84-234-105:152676] *** Process received signal ***
[ip-10-84-234-105:152676] Signal: Segmentation fault (11)
[ip-10-84-234-105:152676] Signal code: Address not mapped (1)
[ip-10-84-234-105:152676] Failing at address: (nil)
[ip-10-84-234-105:152676] [ 0] 
/lib/x86_64-linux-gnu/libc.so.6(+0x3c510)[0x7f7a3a86f510]
[ip-10-84-234-105:152676] *** End of error message ***
Segmentation fault


Possibly a transitory inconsistency caught in the middle of an openmpi update.

Processed: tagging 1069799

[Debian Bug Tracking System]

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

> tags 1069799 + ftbfs
Bug #1069799 [rust-multihash-derive-impl] rust-multihash-derive-impl - 
(build-)depends unsatisfiable.
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1070644: gnome-remote-desktop: System .service file enabled but not the user one?

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1070644 [gnome-remote-desktop] gnome-remote-desktop: System .service file 
enabled but not the user one?
Severity set to 'serious' from 'normal'

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

Bug#1070652: ruby-json: breaks how-can-i-help

[Vincent Lefevre]

Package: ruby-json
Version: 2.7.2+dfsg-1
Severity: grave
Justification: renders package unusable

This new ruby-json version breaks how-can-i-help:

[...]
Unpacking ruby-json:amd64 (2.7.2+dfsg-1) over (2.6.3+dfsg-1+b2) ...
Setting up ruby-json:amd64 (2.7.2+dfsg-1) ...
/usr/bin/how-can-i-help:155:in `': uninitialized constant OpenStruct 
(NameError)

proxy_uri = $proxy_url.nil? ? OpenStruct.new : URI.parse($proxy_url)
  ^^

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

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

Versions of packages ruby-json depends on:
ii  libc6  2.38-7
ii  libruby1:3.1+nmu1
ii  libruby3.1t64  3.1.2-8.3

ruby-json recommends no packages.

ruby-json suggests no packages.

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1068610: marked as done (dico: binary-all FTBFS)

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2024 14:37:58 +
with message-id 
and subject line Bug#1068610: fixed in dico 2.11-4.2
has caused the Debian Bug report #1068610,
regarding dico: binary-all FTBFS
to be marked as done.

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

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


-- 
1068610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068610
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dico
Version: 2.11-4
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Helmut Grohne 

https://buildd.debian.org/status/logs.php?pkg=dico&arch=all

...
   debian/rules execute_after_dh_installsystemd
make[1]: Entering directory '/<>'
ln -s dicod.service debian/dicod/`test -e 
debian/dicod/lib/systemd/system/dicod.service || echo 
usr/`lib/systemd/system/dictd.service
ln: failed to create symbolic link 
'debian/dicod/usr/lib/systemd/system/dictd.service': No such file or directory
make[1]: *** [debian/rules:52: execute_after_dh_installsystemd] Error 1
--- End Message ---
--- Begin Message ---
Source: dico
Source-Version: 2.11-4.2
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated dico 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: Sat, 04 May 2024 15:56:18 +0200
Source: dico
Architecture: source
Version: 2.11-4.2
Distribution: unstable
Urgency: medium
Maintainer: Ritesh Raj Sarraf 
Changed-By: Andreas Beckmann 
Closes: 1068610
Changes:
 dico (2.11-4.2) unstable; urgency=medium
 .
   [ Andreas Beckmann ]
   * Non-maintainer upload.
   * Fix building twice in a row.
 .
   [ Helmut Grohne ]
   * Fix indep-only FTBFS arising from #1054187. (Closes: #1068610)
Checksums-Sha1:
 6ef71b8450e1a9936a36cbc49902a1a22586b362 2730 dico_2.11-4.2.dsc
 ea7da2eba484dcf7f87f2b9834e40a1b25045d6a 27212 dico_2.11-4.2.debian.tar.xz
 bfedff981a55058d19d1a38c525176b5ea6e333e 8388 dico_2.11-4.2_source.buildinfo
Checksums-Sha256:
 a3adeab9504525952c3ab800654caa74035904ee021638e56c01dc3761e504b0 2730 
dico_2.11-4.2.dsc
 b719feb4688f5a1875a79197b427e2308de92bce02855651e0f26a7885325c89 27212 
dico_2.11-4.2.debian.tar.xz
 2d10ab349c13446f3b33e036a226b016ec7c214af2e742048f6883a539f0c480 8388 
dico_2.11-4.2_source.buildinfo
Files:
 8d42f9791c8106193417ddb792f2fb9d 2730 text optional dico_2.11-4.2.dsc
 39c9fb45333faac2956b5eee1260ebcf 27212 text optional 
dico_2.11-4.2.debian.tar.xz
 dfd36fbe21fe1f8d45235480be6577fd 8388 text optional 
dico_2.11-4.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmY2PzoQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCK+uD/0bfA3U6ZpkM5bOojXIxesgig6OR/us7h7F
MXNww4sMjndz/x4cLSPoCDvsIFuWOZ2QEgU1FAHQg5CrdHN9MZlE2NVnOElq/JDp
mtPHkgUYEmKtPw433HnIDP1wcjLZGndvy7Rr0towTqtRBIa6Mpro6Hf6bROuTTVJ
LKxj/NEGD2IbURDYlpJ79P6qVWI8HaFMQOdpaULe4MK3ueqFAcaeGLYj/X3YqJr4
2P+wgHQBZARnJTRKATBiwDvc0tizmdaOtKL/6Rfrgj1o1AAd/BhNbnJe8kXkMlaW
M2GGcp8KznzfIRSIyIv88Wp4RwOaPptXd2U5lrPiPdNZsuumnkLKB8Q01J5tYIIT
gKSN36CtqIFfMZnqq76nOuVqRvnbDfXYkuhCAB+RPCOJdPtXpcBFfzmO4SeMXbvg
Rrxv+SvjipsVghrxQ1ArPTR0aPfTNU7Z6ickgGlAeC4EtZ2VOBNOeMGbRL8R2Kmq
LfVlahDYdKtX0CT/r3Y67coNwMy7WFhbtvmWFabGg+wXRQ1EZwhgwQkdLV3TFM1L
vLAnvqNilv4GpTKNEdnERIR0ttePePBGurbTMoFfg9ZCliblS+enA6S1Embb8leW
p5imu4DUBgDgtUMK+AEvtjhooK5T2steXtMIbqCRqQevkgISbYW0ardAeseStTU/
Ng9Qu8DwSw==
=YNKE
-END PGP SIGNATURE-



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

Bug#1070638: kde-spectacle: Build-depends on NBS libkcolorpicker-dev

[Scott Kitterman]

On Mon, 06 May 2024 10:33:54 -0400 Scott Kitterman  
wrote:
> Source: kde-spectacle
> Version: 22.12.3-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the 
past)
> 
> Once kcolorpicker is decrufted, this package will FTBFS.  Please update
> your build-depends.

Also libkimageannotator-dev needs updating.

Scott K

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

Bug#1070638: kde-spectacle: Build-depends on NBS libkcolorpicker-dev

[Scott Kitterman]

Source: kde-spectacle
Version: 22.12.3-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Once kcolorpicker is decrufted, this package will FTBFS.  Please update
your build-depends.

Scott K

Bug#1069387: marked as done (distro-info: FTBFS on arm64: Can't write the issue template for the crash in /<>/debian/.debhelper/generated/_source/home/.cache/pylint/pylint-crash-2024-04-2

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2024 16:12:31 +0200
with message-id 
and subject line Re: Bug#1069387: distro-info: FTBFS on arm64: Can't write the 
issue template for the crash in 
/<>/debian/.debhelper/generated/_source/home/.cache/pylint/pylint-crash-2024-04-20-04-31-27.txt
 because of: '[Errno 2] No such file or directory: 
'/<>/debian/.debhelper/generated/_source/home/.cache/pylint/pylint-crash-2024-04-20-04-31-27.txt''
has caused the Debian Bug report #1069387,
regarding distro-info: FTBFS on arm64: Can't write the issue template for the 
crash in 
/<>/debian/.debhelper/generated/_source/home/.cache/pylint/pylint-crash-2024-04-20-04-31-27.txt
 because of: '[Errno 2] No such file or directory: 
'/<>/debian/.debhelper/generated/_source/home/.cache/pylint/pylint-crash-2024-04-20-04-31-27.txt''
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.)


-- 
1069387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069387
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: distro-info
Version: 1.7
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> ./test-debian-distro-info
> cd perl && ./test.pl
> testAlias
> testAll
> testDevel
> py3versions: no X-Python3-Version in control file, using supported versions
> cd python && python3.12 setup.py test
> 1..35
> testOldstable
> ok 1 - unique: Matching lists
> ok 2 - symmetric_difference: Matching lists
> ok 3 - unique: 1 Unique Item
> ok 4 - unique: 1 Unique Item in the haystack
> ok 5 - symmetric_difference: 1 Unique Item
> ok 6 - Debian all
> ok 7 - Debian devel
> ok 8 - Debian oldstable
> ok 9 - Debian stable
> ok 10 - Debian testing
> ok 11 - Debian valid
> ok 12 - Debian valid
> ok 13 - Debian invalid
> ok 14 - Debian supported
> ok 15 - Debian LTS
> ok 16 - Debian ELTS
> ok 17 - Debian unsupported
> ok 18 - Debian codename, invalid
> ok 19 - Debian codename
> ok 20 - Debian version, invalid
> ok 21 - Debian version
> ok 22 - Ubuntu all
> ok 23 - Ubuntu version
> ok 24 - Ubuntu LTS version
> ok 25 - Ubuntu devel
> ok 26 - Ubuntu LTS
> ok 27 - Ubuntu stable
> ok 28 - Ubuntu valid
> ok 29 - Ubuntu invalid
> ok 30 - Ubuntu is_lts
> ok 31 - Ubuntu !is_lts
> ok 32 - Ubuntu !is_lts
> ok 33 - Ubuntu supported
> ok 34 - Ubuntu ESM
> ok 35 - Ubuntu unsupported
> testStable
> testSupported
> testLTS
> testELTS
> testUnsupported
> testTesting
> testFullname
> running test
> WARNING: Testing via this command is deprecated and will be removed in a 
> future version. Users looking for a generic test entry point independent of 
> test runner are encouraged to use tox.
> /usr/lib/python3/dist-packages/setuptools/command/test.py:193: 
> _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are 
> deprecated.
> !!
> 
> 
> 
> Requirements should be satisfied by a PEP 517 installer.
> If you are using pip, you can try `pip install --use-pep517`.
> 
> 
> 
> !!
>   ir_d = dist.fetch_build_eggs(dist.install_requires)
> WARNING: The wheel package is not available.
> testRelease
> /usr/lib/python3/dist-packages/setuptools/command/test.py:194: 
> _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are 
> deprecated.
> !!
> 
> 
> 
> Requirements should be satisfied by a PEP 517 installer.
> If you are using pip, you can try `pip install --use-pep517`.
> 
> 
> 
> !!
>   tr_d = dist.fetch_build_eggs(dist.tests_require or [])
> WARNING: The wheel package is not available.
> /usr/lib/python3/dist-packages/setuptools/command/test.py:195: 
> _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are 
> deprecated.
> !!
> 
> 
> 
> Requirements should be satisfied by a PEP 517 installer.
> If you are using pip, you can try `pip install --use-pep517`.
> 
> 
> 
> !!
>   er_d = dist.fetch_build_eggs(
> WARNING: The wheel package is not available.
> runni

Bug#1070515: dipy: FTBFS with nocheck profile

[Graham Inggs]

Source: dipy
Version: 1.8.0-2
Severity: serious
Tags: ftbfs patch

Hi Maintainer

dipy FTBFS when built with the 'nocheck' profile.  I've copied what I
hope is the relevant part of the log below.

The following patch worked for me:

--- a/debian/rules
+++ b/debian/rules
@@ -111,11 +111,11 @@
  ; done
 endif
  # Cleanup files landing unnecessarily in the python3 modules directory.
- rm -v debian/$(PACKAGE3_NAME)/usr/lib/python3*/dist-packages/*.nii.gz
- rm -v debian/$(PACKAGE3_NAME)/usr/lib/python3*/dist-packages/*.trk
- rm -v debian/$(PACKAGE3_NAME)/usr/lib/python3*/dist-packages/affine.txt
+ rm -fv debian/$(PACKAGE3_NAME)/usr/lib/python3*/dist-packages/*.nii.gz
+ rm -fv debian/$(PACKAGE3_NAME)/usr/lib/python3*/dist-packages/*.trk
+ rm -fv debian/$(PACKAGE3_NAME)/usr/lib/python3*/dist-packages/affine.txt
  # Cleanup files landing in non-standard path
- rm -rv debian/$(PACKAGE3_NAME)/usr/doc
+ rm -rfv debian/$(PACKAGE3_NAME)/usr/doc

 ## "Instantiate" both rules so dh sees them
 override_dh_python3:
@@ -136,9 +136,9 @@
  -X.par -X.bin -Xobjects.inv

 execute_before_dh_link-indep:
- rm -v 
debian/python-dipy-doc/usr/share/doc/python-dipy-doc/html/_static/doctools.js
- rm -v 
debian/python-dipy-doc/usr/share/doc/python-dipy-doc/html/_static/language_data.js
- rm -v 
debian/python-dipy-doc/usr/share/doc/python-dipy-doc/html/_static/searchtools.js
+ rm -fv 
debian/python-dipy-doc/usr/share/doc/python-dipy-doc/html/_static/doctools.js
+ rm -fv 
debian/python-dipy-doc/usr/share/doc/python-dipy-doc/html/_static/language_data.js
+ rm -fv 
debian/python-dipy-doc/usr/share/doc/python-dipy-doc/html/_static/searchtools.js

 execute_after_dh_fixperms-arch:
  # Fix a couple of executables neither elf nor scripts.

Regards
Graham


find debian/ -name LICENSE -delete
# Only now lets build docs
# Run tests later on
# cd build to prevent use of local/not-built source tree
# Cleanup files landing unnecessarily in the python3 modules directory.
rm -v debian/python3-dipy/usr/lib/python3*/dist-packages/*.nii.gz
rm: cannot remove
'debian/python3-dipy/usr/lib/python3*/dist-packages/*.nii.gz': No such
file or directory
make[1]: *** [debian/rules:81: execute_after_dh_auto_install] Error 1

Processed (with 3 errors): Merge duplicates

[Debian Bug Tracking System]

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

> reassign 1069460 src:openmpi
Bug #1069460 [src:bitshuffle] bitshuffle: FTBFS on armhf: tests fail
Bug reassigned from package 'src:bitshuffle' to 'src:openmpi'.
No longer marked as found in versions bitshuffle/0.5.1-1.2.
Ignoring request to alter fixed versions of bug #1069460 to the same values 
previously set
> forcemerge 1070300 1069460
Bug #1070300 {Done: Samuel Thibault } [src:openmpi] 
pmix_psquash_base_select failed during MPI_INIT on 32bit architectures
Bug #1069460 [src:openmpi] bitshuffle: FTBFS on armhf: tests fail
Marked Bug as done
Added indication that 1069460 affects src:dune-grid
Marked as fixed in versions openmpi/4.1.6-13.1.
Marked as found in versions openmpi/4.1.6-13.
Bug #1070300 {Done: Samuel Thibault } [src:openmpi] 
pmix_psquash_base_select failed during MPI_INIT on 32bit architectures
Added tag(s) trixie, sid, and ftbfs.
Merged 1069460 1070300
> affects 1070300 src:bitshuffle
Bug #1070300 {Done: Samuel Thibault } [src:openmpi] 
pmix_psquash_base_select failed during MPI_INIT on 32bit architectures
Bug #1069460 {Done: Samuel Thibault } [src:openmpi] 
bitshuffle: FTBFS on armhf: tests fail
Added indication that 1070300 affects src:bitshuffle
Added indication that 1069460 affects src:bitshuffle
> done
Unknown command or malformed arguments to command.
> cu
Unknown command or malformed arguments to command.
> Adrian
Unknown command or malformed arguments to command.
>
End of message, stopping processing here.

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

Bug#1069404: marked as done (lua-luaossl: FTBFS on arm64: ld: cannot find -lz: No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2024 13:49:50 +
with message-id 
and subject line Bug#1069404: fixed in lua-luaossl 20220711-2
has caused the Debian Bug report #1069404,
regarding lua-luaossl: FTBFS on arm64: ld: cannot find -lz: No such file or 
directory
to be marked as done.

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

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


-- 
1069404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069404
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lua-luaossl
Version: 20220711-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64

Hi,

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


Relevant part (hopefully):
> /<>/debian/.dh_lua-libtool/libtool --tag=CC --mode=link 
> aarch64-linux-gnu-gcc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security 
> -mbranch-protection=standard -Wall -pedantic -Wdate-time -D_FORTIFY_SOURCE=2 
> -I/usr/include/lua5.1   -I . -I src/ -std=c99 -D_REENTRANT -D_THREAD_SAFE 
> -D_GNU_SOURCE -DLUA_COMPAT_APIINTCASTS -DHAVE_CONFIG_H -Wall -Wextra 
> -Wl,--no-add-needed \
>   -static -o /<>/5.1-luaossl/app-static -I . -I 
> /<>/5.1-luaossl/ \
>   /usr/share/dh-lua/test/5.1/app.c 
> /<>/5.1-luaossl/liblua5.1-luaossl.la \
>   -Wl,-z,relro -Wl,--as-needed -lssl -lz -lzstd -ldl -pthread -lcrypto 
> -lz -lzstd -ldl -pthread  -lpthread -llua5.1 -lm -ldl 
> libtool: link: aarch64-linux-gnu-gcc -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -mbranch-protection=standard -Wall -pedantic 
> -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/lua5.1 -I . -I src/ -std=c99 
> -D_REENTRANT -D_THREAD_SAFE -D_GNU_SOURCE -DLUA_COMPAT_APIINTCASTS 
> -DHAVE_CONFIG_H -Wall -Wextra -Wl,--no-add-needed -o 
> /<>/5.1-luaossl/app-static -I . -I /<>/5.1-luaossl/ 
> /usr/share/dh-lua/test/5.1/app.c -Wl,-z -Wl,relro -Wl,--as-needed  
> /<>/5.1-luaossl/.libs/liblua5.1-luaossl.a -lssl -lcrypto -lz 
> -lzstd -lpthread -llua5.1 -lm -ldl -pthread
> /usr/bin/ld: cannot find -lz: No such file or directory
> /usr/bin/ld: cannot find -lzstd: No such file or directory
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/lua-luaossl_20220711-1_unstable-arm64.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: lua-luaossl
Source-Version: 20220711-2
Done: Jakub Ružička 

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

Debian distribution maintenance software
pp.
Jakub Ružička  (supplier of updated lua-luaossl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 May 2024 14:44:07 +0200
Source: lua-luaossl
Architecture: source
Version: 20220711-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Lua Team 
Changed-By: Jakub Ružička 
Closes: 1069404
Changes:
 lua-luaossl (20220711-2) unstable; urgency=medium
 .
   * d/control: update Homepage and Vcs-Git
   * d/control: add libz-dev and libzstd-dev to Build-Depends (Closes: #1069404)
   * d/c

Processed: Bug is still in experimental

[Debian Bug Tracking System]

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

> unarchive 1066704
Bug #1066704 {Done: Michael R. Crusoe } [src:libcgns] 
libcgns: FTBFS: tkogl.c:602:8: error: implicit declaration of function 
‘TkWmAddToColormapWindows’ [-Werror=implicit-function-declaration]
Unarchived Bug 1066704
> found 1066704 3.4.0-1
Bug #1066704 {Done: Michael R. Crusoe } [src:libcgns] 
libcgns: FTBFS: tkogl.c:602:8: error: implicit declaration of function 
‘TkWmAddToColormapWindows’ [-Werror=implicit-function-declaration]
Marked as found in versions libcgns/3.4.0-1.
> thanks
Stopping processing here.

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

Bug#1069356: marked as done (lua-cqueues: FTBFS on arm64: ld: cannot find -lz: No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2024 13:18:58 +
with message-id 
and subject line Bug#1069356: fixed in lua-cqueues 20200726-2
has caused the Debian Bug report #1069356,
regarding lua-cqueues: FTBFS on arm64: ld: cannot find -lz: No such file or 
directory
to be marked as done.

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

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


-- 
1069356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069356
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lua-cqueues
Version: 20200726-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64

Hi,

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


Relevant part (hopefully):
> /<>/debian/.dh_lua-libtool/libtool --tag=CC --mode=link 
> aarch64-linux-gnu-gcc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security 
> -mbranch-protection=standard -Wall -pedantic -Wdate-time -D_FORTIFY_SOURCE=2 
> -I/usr/include/lua5.1   -I src/ -std=c99 -D_REENTRANT -D_THREAD_SAFE 
> -D_GNU_SOURCE -DLUA_COMPAT_APIINTCASTS -DHAVE_CONFIG_H -Wall -Wextra 
> -Wl,--no-add-needed \
>   -static -o /<>/5.1-cqueues/app-static -I . -I 
> /<>/5.1-cqueues/ \
>   /usr/share/dh-lua/test/5.1/app.c 
> /<>/5.1-cqueues/liblua5.1-cqueues.la \
>   -Wl,-z,relro -Wl,--as-needed -lssl -lz -lzstd -ldl -pthread -lcrypto 
> -lz -lzstd -ldl -pthread  -lpthread -llua5.1 -lm -ldl 
> libtool: link: aarch64-linux-gnu-gcc -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -mbranch-protection=standard -Wall -pedantic 
> -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/lua5.1 -I src/ -std=c99 
> -D_REENTRANT -D_THREAD_SAFE -D_GNU_SOURCE -DLUA_COMPAT_APIINTCASTS 
> -DHAVE_CONFIG_H -Wall -Wextra -Wl,--no-add-needed -o 
> /<>/5.1-cqueues/app-static -I . -I /<>/5.1-cqueues/ 
> /usr/share/dh-lua/test/5.1/app.c -Wl,-z -Wl,relro -Wl,--as-needed  
> /<>/5.1-cqueues/.libs/liblua5.1-cqueues.a -lssl -lcrypto -lz 
> -lzstd -lpthread -llua5.1 -lm -ldl -pthread
> In file included from /<>/5.1-cqueues/app.c.conf:4,
>  from /usr/share/dh-lua/test/5.1/app.c:14:
> src/cqueues.h:195:13: warning: 'cqs_openlibs' defined but not used 
> [-Wunused-function]
>   195 | static void cqs_openlibs(lua_State *L) {
>   | ^~~~
> /usr/bin/ld: cannot find -lz: No such file or directory
> /usr/bin/ld: cannot find -lzstd: No such file or directory
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/lua-cqueues_20200726-1_unstable-arm64.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: lua-cqueues
Source-Version: 20200726-2
Done: Jakub Ružička 

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

Debian distribution maintenance software
pp.
Jakub Ružička  (supplier of updated lua-cqueues package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 May 2024 14:15:58 +0200
Source: lua-cqueues
Architecture: source
Version: 20200726-2
Distribution: unstable
U

Bug#1061519: marked as done (shim: CVE-2023-40546 CVE-2023-40547 CVE-2023-40548 CVE-2023-40549 CVE-2023-40550 CVE-2023-40551)

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2024 13:04:59 +
with message-id 
and subject line Bug#1061519: fixed in shim 15.8-1
has caused the Debian Bug report #1061519,
regarding shim: CVE-2023-40546 CVE-2023-40547 CVE-2023-40548 CVE-2023-40549 
CVE-2023-40550 CVE-2023-40551
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.)


-- 
1061519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061519
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: shim
Version: 15.7-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 15.7-1~deb11u1

Hi,

The following vulnerabilities were published for shim.

According to [6]:

* Various CVE fixes:
  CVE-2023-40546 mok: fix LogError() invocation
  CVE-2023-40547 - avoid incorrectly trusting HTTP headers
  CVE-2023-40548 Fix integer overflow on SBAT section size on 32-bit system
  CVE-2023-40549 Authenticode: verify that the signature header is in bounds.
  CVE-2023-40550 pe: Fix an out-of-bound read in verify_buffer_sbat()
  CVE-2023-40551: pe-relocate: Fix bounds check for MZ binaries

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-40546
https://www.cve.org/CVERecord?id=CVE-2023-40546
[1] https://security-tracker.debian.org/tracker/CVE-2023-40547
https://www.cve.org/CVERecord?id=CVE-2023-40547
[2] https://security-tracker.debian.org/tracker/CVE-2023-40548
https://www.cve.org/CVERecord?id=CVE-2023-40548
[3] https://security-tracker.debian.org/tracker/CVE-2023-40549
https://www.cve.org/CVERecord?id=CVE-2023-40549
[4] https://security-tracker.debian.org/tracker/CVE-2023-40550
https://www.cve.org/CVERecord?id=CVE-2023-40550
[5] https://security-tracker.debian.org/tracker/CVE-2023-40551
https://www.cve.org/CVERecord?id=CVE-2023-40551
[6] https://github.com/rhboot/shim/releases/tag/15.8

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: shim
Source-Version: 15.8-1
Done: Steve McIntyre <93...@debian.org>

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

Debian distribution maintenance software
pp.
Steve McIntyre <93...@debian.org> (supplier of updated shim 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: Sat, 04 May 2024 23:29:52 +0100
Source: shim
Architecture: source
Version: 15.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian EFI team 
Changed-By: Steve McIntyre <93...@debian.org>
Closes: 936009 1043485 1046268 1054210 1057606 1061519 1064220 1069054
Changes:
 shim (15.8-1) unstable; urgency=medium
 .
   [ Steve McIntyre ]
   * Cope with changes in pesign packaging. Closes: #1057606
   * New upstream release fixing more bugs. Closes: #1061519, #1064220
 + CVE-2023-40546 mok: fix LogError() invocation (Closes: #1054210)
 + CVE-2023-40547 - avoid incorrectly trusting HTTP headers
 + CVE-2023-40548 Fix integer overflow on SBAT section size on
   32-bit system
 + CVE-2023-40549 Authenticode: verify that the signature header is
   in bounds.
 + CVE-2023-40550 pe: Fix an out-of-bound read in
   verify_buffer_sbat()
 + CVE-2023-40551: pe-relocate: Fix bounds check for MZ binaries
   * Remove all our previous patches, no longer needed:
 + Make-sbat_var.S-parse-right-with-buggy-gcc-binutils.patch (now
   upstream)
 + Enable-NX.patch (we don't want NX just yet until the whole boot
   stack is NX-capable)
 + block-grub-sbat3-debian.patch (not needed now upstream grub SBAT
   is 4)
   * Cherry-pick 2 new patches from upstream for grub revocations:
 + 0001-sbat-Add-grub.peimage-2-to-latest-CVE-2024-2312.patch
 + 0002-sbat-Also-bump-latest-for-grub-4-and-to-todays-date.patch
   * NOTE: Stop building for i386
 + Debian kernels are no longer signed for i386, it's time to stop
   supporting i386 SB.
   * Log if the build is nx-compatible o

Bug#1057606: marked as done (shim: FTBFS: ./debian/generate_dbx_list: 23: efisiglist: not found)

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2024 13:04:59 +
with message-id 
and subject line Bug#1057606: fixed in shim 15.8-1
has caused the Debian Bug report #1057606,
regarding shim: FTBFS: ./debian/generate_dbx_list: 23: efisiglist: not found
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.)


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

Package: src:shim
Version: 15.7-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build
dh build
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
./debian/generate_dbx_list x64 debian/debian-dbx.hashes dbx.esl
  Adding 000f1547bb113601d65df9cb74ac62dd6d2ca85a0c2bb375c2f0ecedb59c84a4 to 
dbx list
./debian/generate_dbx_list: 23: efisiglist: not found
make[1]: *** [debian/rules:52: dbx.esl] Error 127
make[1]: Leaving directory '/<>'
make: *** [debian/rules:64: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

https://people.debian.org/~sanvila/build-logs/202312/

About the archive rebuild: The build was made using virtual machines
from AWS, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages.

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: shim
Source-Version: 15.8-1
Done: Steve McIntyre <93...@debian.org>

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

Debian distribution maintenance software
pp.
Steve McIntyre <93...@debian.org> (supplier of updated shim 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: Sat, 04 May 2024 23:29:52 +0100
Source: shim
Architecture: source
Version: 15.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian EFI team 
Changed-By: Steve McIntyre <93...@debian.org>
Closes: 936009 1043485 1046268 1054210 1057606 1061519 1064220 1069054
Changes:
 shim (15.8-1) unstable; urgency=medium
 .
   [ Steve McIntyre ]
   * Cope with changes in pesign packaging. Closes: #1057606
   * New upstream release fixing more bugs. Closes: #1061519, #1064220
 + CVE-2023-40546 mok: fix LogError() invocation (Closes: #1054210)
 + CVE-2023-40547 - avoid incorrectly trusting HTTP headers
 + CVE-2023-40548 Fix integer overflow on SBAT section size on
   32-bit system
 + CVE-2023-40549 Authenticode: verify that the signature header is
   in bounds.
 + CVE-2023-40550 pe: Fix an out-of-bound read in
   verify_buffer_sbat()
 + CVE-2023-40551: pe-relocate: Fix bounds check for MZ binaries
   * Remove all our previous patches, no longer needed:
 + Make-sbat_var.S-parse-right-with-buggy-gcc-binutils.patch (now
   upstream)
 + Enable-NX.patch (we don't want NX just yet until the whole boot
   stack is NX-capable)
 + block-grub-sbat3-debian.patch (not needed now upstream grub SBAT
   is 4)
   * Cherry-pick 2 new patches from upstream for grub revocations:
 + 0001-sbat-Add-grub.peimage-2-to-latest-CVE-2024-2312.patch
 + 0002-sbat-Also-bump-latest-for-grub-4-and-to-todays-date.patch
   * NOTE: Stop building for i386
 + Debian kernels are no longer signed for i386, it's time to stop
   supporting i386 SB.
   * Log if the build is nx-compati

Processed: tagging 1059228

[Debian Bug Tracking System]

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

> tags 1059228 + ftbfs
Bug #1059228 [src:s2geometry] build system hard-codes -std=c++11
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#1054661: blastem: Segfault when trying to open rom or access system settings

[Bernhard Übelacker]

On Sat, 28 Oct 2023 12:52:30 +0200 Tobias Frost  wrote:

Control: tags -1 confirmed

Here's a backtrace when clicking on Settings -> System. 
Thread 1 "blastem" received signal SIGSEGV, Segmentation fault.

tern_foreach_int (head=, fun=0x555c12a0 , 
data=0x7fffd7f0, keybuf=0x7fffd8c0 "\020", pos=0)
at /build/blastem-kipVNx/blastem-0.6.3.4/tern.c:268
268 if (!head->el) {
(gdb) bt
#0  tern_foreach_int (head=, fun=0x555c12a0 , 
data=0x7fffd7f0, keybuf=0x7fffd8c0 "\020", pos=0) at 
/build/blastem-kipVNx/blastem-0.6.3.4/tern.c:268
#1  0x555c7e15 in tern_foreach (data=0x7fffd7f0, fun=0x555c12a0 
, head=) at 
/build/blastem-kipVNx/blastem-0.6.3.4/tern.c:291
#2  get_models (num_out=0x557a8ba0 ) at 
nuklear_ui/blastem_nuklear.c:1873
#3  view_system_settings (context=0x55611ab8 ) at 
nuklear_ui/blastem_nuklear.c:1907
#4  0x555c8354 in blastem_nuklear_render () at 
nuklear_ui/blastem_nuklear.c:2049
#5  0x55589e1b in render_update_display () at 
/build/blastem-kipVNx/blastem-0.6.3.4/render_sdl.c:1783
#6  0x555caeeb in ui_idle_loop () at nuklear_ui/blastem_nuklear.c:2075
#7  0xdefa in blastem_nuklear_init (file_loaded=0 '\000') at 
nuklear_ui/blastem_nuklear.c:2332
#8  main (argc=, argv=) at 
/build/blastem-kipVNx/blastem-0.6.3.4/blastem.c:714
(gdb) 


Did not investigate further.



Hello,
tried to take a little deeper look.
And it seems it is just a missing packaged config file:


(rr)
0x55c0356f0361  1012return NULL;
1: x/i $pc
=> 0x55c0356f0361 :  xor%r13d,%r13d
10: /x $r13 = 0x0
(rr) bt
#0  0x55c0356f0361 in read_bundled_file (name=name@entry=0x55c03574ae4a 
"systems.cfg", sizeret=sizeret@entry=0x7ffc07889c88) at 
/build/blastem-kipVNx/blastem-0.6.3.4/util.c:1012
#1  0x55c0356f0a2d in parse_bundled_config (config_name=0x55c03574ae4a 
"systems.cfg") at /build/blastem-kipVNx/blastem-0.6.3.4/config.c:217
#2  0x55c03571ff56 in get_systems_config () at 
/build/blastem-kipVNx/blastem-0.6.3.4/config.c:331
#3  get_models (num_out=0x55c035900ba0 ) at 
nuklear_ui/blastem_nuklear.c:1866
#4  view_system_settings (context=0x55c035769ab8 ) at 
nuklear_ui/blastem_nuklear.c:1907
#5  0x55c035720354 in blastem_nuklear_render () at 
nuklear_ui/blastem_nuklear.c:2049
#6  0x55c0356e1e1b in render_update_display () at 
/build/blastem-kipVNx/blastem-0.6.3.4/render_sdl.c:1783
#7  0x55c035722eeb in ui_idle_loop () at nuklear_ui/blastem_nuklear.c:2075
#8  0x55c0356b5efa in blastem_nuklear_init (file_loaded=0 '\000') at 
nuklear_ui/blastem_nuklear.c:2332
#9  main (argc=, argv=) at 
/build/blastem-kipVNx/blastem-0.6.3.4/blastem.c:714


Function `read_bundled_file` does not find "systems.cfg",
therefore returns NULL,
therefore `parse_bundled_config` returns also NULL,
which is then also returned by `get_systems_config`.

This NULL is given unconditionally into tern_foreach in blasem_nuklear.c line 
1873,
and gets dereferenced.


Following change would add systems.cfg to the Debian package,
and did avoid the crash in a short test.

Kind regards,
Bernhard


diff -Nurp orig/blastem-0.6.3.4/debian/blastem.install 
try2/blastem-0.6.3.4/debian/blastem.install
--- orig/blastem-0.6.3.4/debian/blastem.install 2021-09-24 22:14:33.0 
+0200
+++ try2/blastem-0.6.3.4/debian/blastem.install 2024-05-06 14:31:55.277695226 
+0200
@@ -6,3 +6,4 @@ gamecontrollerdb.txtusr/share/games/bl
 images usr/share/games/blastem
 rom.db usr/share/games/blastem
 shadersusr/share/games/blastem
+systems.cfgusr/share/games/blastem

Bug#1070498: libvirt attempts to write to $HOME during the build

[Adrian Bunk]

Source: libvirt
Version: 10.3.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=libvirt&arch=amd64&ver=10.3.0-1&stamp=1714824148&raw=0

...
53) completion-command... 
In '/<>/tests/virshtestdata/completion-command.out':
Offset 6
Expect []
Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission 
denied
]
  ... FAILED
54) completion-command-complete   ... 
In '/<>/tests/virshtestdata/completion-command-complete.out':
Offset 6
Expect []
Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission 
denied
]
  ... FAILED
55) completion-args   ... 
In '/<>/tests/virshtestdata/completion-args.out':
Offset 47
Expect []
Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission 
denied
]
  ... FAILED
56) completion-arg-partial... 
In '/<>/tests/virshtestdata/completion-arg-partial.out':
Offset 26
Expect []
Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission 
denied
]
  ... FAILED
57) completion-arg-full-bool  ... 
In '/<>/tests/virshtestdata/completion-arg-full-bool.out':
Offset 7
Expect []
Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission 
denied
]
  ... FAILED
58) completion-arg-full-bool-next ... 
In '/<>/tests/virshtestdata/completion-arg-full-bool-next.out':
Offset 47
Expect []
Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission 
denied
]
  ... FAILED
59) completion-arg-full-string... 
In '/<>/tests/virshtestdata/completion-arg-full-string.out':
Offset 10
Expect []
Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission 
denied
]
  ... FAILED
60) completion-arg-full-string-next   ... 
In '/<>/tests/virshtestdata/completion-arg-full-string-next.out':
Offset 47
Expect []
Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission 
denied
]
  ... FAILED
61) completion-arg-full-argv  ... 
In '/<>/tests/virshtestdata/completion-arg-full-argv.out':
Offset 10
Expect []
Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission 
denied
]
  ... FAILED
62) completion-arg-full-argv-next ... 
In '/<>/tests/virshtestdata/completion-arg-full-argv-next.out':
Offset 6
Expect []
Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission 
denied
]
  ... FAILED
63) completion-argv-multiple  ... 
In '/<>/tests/virshtestdata/completion-argv-multiple.out':
Offset 5
Expect []
Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission 
denied
]
  ... FAILED
64) completion-argv-multiple-next ... 
In '/<>/tests/virshtestdata/completion-argv-multiple-next.out':
Offset 268
Expect []
Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission 
denied
]
  ... FAILED
65) completion-argv-multiple-positional   ... 
In 
'/<>/tests/virshtestdata/completion-argv-multiple-positional.out':
Offset 5
Expect []
Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission 
denied
]
  ... FAILED
66) completion-argv-multiple-positional-next  ... 
In 
'/<>/tests/virshtestdata/completion-argv-multiple-positional-next.out':
Offset 268
Expect []
Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission 
denied
]
  ... FAILED
67) completion-arg-positional-empty   ... 
In '/<>/tests/virshtestdata/completion-arg-positional-empty.out':
Offset 19
Expect []
Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission 

Bug#1056677: marked as done (build-depends on atlas, which is obsolete and scheduled for removal)

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2024 12:09:19 +
with message-id 
and subject line Bug#1056677: fixed in hpcc 1.5.0-4
has caused the Debian Bug report #1056677,
regarding build-depends on atlas, which is obsolete and scheduled for removal
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.)


-- 
1056677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056677
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hpcc
Version: 1.5.0-3
Severity: normal
Tags: sid trixie
User: debian-scie...@lists.debian.org
Usertags: atlas-rm

Dear Maintainer,

hpcc build-depends on libatlas-base-dev, which is produced by the source
package atlas.

atlas is obsolete and scheduled to be removed from Debian, ideally by the
trixie release. See the following thread on the Debian Science list for more
details:

 
https://lists.debian.org/msgid-search/4311acc16afb473599c79bd5b17a8b734c2f8d2b.ca...@debian.org

As a consequence, please drop any (build-)dependency on atlas.

This should normally be straightforward to achieve, by simply replacing atlas
with another BLAS (and possibly also LAPACK) implementation.

Ideally, packages should Build-Depend on the Netlib reference implementation
(libblas-dev, and liblapack-dev where required), and not enforce anything in
the Depends field of binary packages (dpkg-shlibdeps will automatically add the
appropriate "libblas3 | libblas.so.3" entry to ${shlibs:Depends}).

Alternative implementations may be given in Build-Depends for the ease 
of users making local builds with an optimized implementation installed, 
but the generic reference implementation should be placed first to be 
used by buildds. The simplest example is

  Build-Depends: libblas-dev | libblas.so,
 liblapack-dev | liblapack.so

where specific optimized implementations may provide the
libblas.so/liblapack.so pseudo-package.

Similarly, if one wants to encourage users to install an optimized
implementation at runtime, then one can add

  Recommends: libopenblas0 | libblis4

in binary packages.

Also note that if your package needs libcblas (which is currently only provided
by libatlas-base-dev), then the solution is to modify the build system so that
it rather uses libblas (because, under Debian, the latter already incorporates
the symbols provided by libcblas).

Thanks for your work,

--
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
⠈⠳⣄  https://www.debian.org
--- End Message ---
--- Begin Message ---
Source: hpcc
Source-Version: 1.5.0-4
Done: Lucas Nussbaum 

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

Debian distribution maintenance software
pp.
Lucas Nussbaum  (supplier of updated hpcc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 May 2024 13:41:23 +0200
Source: hpcc
Architecture: source
Version: 1.5.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Lucas Nussbaum 
Closes: 1056677 1070050
Changes:
 hpcc (1.5.0-4) unstable; urgency=medium
 .
   * Fix build-depends and recommends to avoid depending on atlas.
 Closes: #1056677
   * Fix FTCBFS: Use pkgconf instead of mpicc. Closes: #1070050
 Thanks Helmut Grohne for the patch!
Checksums-Sha1:
 5d08aef1d7756a7245c0e0645d339e3ce5fd7a56 1970 hpcc_1.5.0-4.dsc
 4887abd173bb49d58084e6db896b930a3530be8a 6384 hpcc_1.5.0-4.debian.tar.xz
 b82551f7433422e2efd97c1fdf9bef3599138e7d 8150 hpcc_1.5.0-4_source.buildinfo
Checksums-Sha256:
 9e4fa3d7f345b443ff964b869cab913854374b8bf7a5fe098b6ab9f15219796b 1970 
hpcc_1.5.0-4.dsc
 d2ae0d0f376925459ca0ddfb45569c95bf5980c8195fea6c1b5f1f10d450ba4a 6384 
hpcc_1.5.0-4.debian.tar.xz
 fad4193d9010c29225ac10ee2f15b8a978ca1c67d49dbeb0539ca47f6418c9bb 8150 
hpcc_1.5.0-4_source.buildinfo
Files:
 92f4ffe8e8afd0ae5634c46cdc845876 1970 science optional hpcc_1.5.0-4.dsc
 2cd4ce2524005941d3e7b1156c88de1c 6384 science optional 
hpcc_1.5.0-4.debian.tar.xz
 764df0b2b9de9c032820da2b03419130 8150 science optional 
hpcc_1.5.0-4_source.buildin

Bug#1070497: webrtc-audio-processing/experimental FTBFS with gcc 13

[Adrian Bunk]

Source: webrtc-audio-processing
Version: 1.0-0.2
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/experimental/amd64/webrtc-audio-processing.html
https://buildd.debian.org/status/fetch.php?pkg=webrtc-audio-processing&arch=riscv64&ver=1.0-0.2&stamp=1706028598&raw=0

...
FAILED: 
webrtc/modules/audio_processing/libwebrtc-audio-processing-1.so.0.p/transient_file_utils.cc.o
 
c++ -Iwebrtc/modules/audio_processing/libwebrtc-audio-processing-1.so.0.p 
-Iwebrtc/modules/audio_processing -I../webrtc/modules/audio_processing -Iwebrtc 
-I../webrtc -I/usr/include -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 
-Wall -Winvalid-pch -std=c++14 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -pthread -DWEBRTC_LIBRARY_IMPL 
-DWEBRTC_ENABLE_SYMBOL_EXPORT -DNDEBUG -DWEBRTC_POSIX -DWEBRTC_LINUX 
-DWEBRTC_THREAD_RR -DWEBRTC_APM_DEBUG_DUMP=0 -MD -MQ 
webrtc/modules/audio_processing/libwebrtc-audio-processing-1.so.0.p/transient_file_utils.cc.o
 -MF 
webrtc/modules/audio_processing/libwebrtc-audio-processing-1.so.0.p/transient_file_utils.cc.o.d
 -o 
webrtc/modules/audio_processing/libwebrtc-audio-processing-1.so.0.p/transient_file_utils.cc.o
 -c ../webrtc/modules/audio_processing/transient/file_utils.cc
In file included from 
../webrtc/modules/audio_processing/transient/file_utils.cc:11:
../webrtc/modules/audio_processing/transient/file_utils.h:36:35: error: 
‘uint8_t’ does not name a type
   36 | int ConvertByteArrayToFloat(const uint8_t bytes[4], float* out);
  |   ^~~
../webrtc/modules/audio_processing/transient/file_utils.h:17:1: note: ‘uint8_t’ 
is defined in header ‘’; did you forget to ‘#include ’?
   16 | #include "rtc_base/system/file_wrapper.h"
  +++ |+#include 
   17 | 
../webrtc/modules/audio_processing/transient/file_utils.h:41:36: error: 
‘uint8_t’ does not name a type
   41 | int ConvertByteArrayToDouble(const uint8_t bytes[8], double* out);
  |^~~
../webrtc/modules/audio_processing/transient/file_utils.h:41:36: note: 
‘uint8_t’ is defined in header ‘’; did you forget to ‘#include 
’?
../webrtc/modules/audio_processing/transient/file_utils.h:46:42: error: 
‘uint8_t’ has not been declared
   46 | int ConvertFloatToByteArray(float value, uint8_t out_bytes[4]);
  |  ^~~
../webrtc/modules/audio_processing/transient/file_utils.h:51:44: error: 
‘uint8_t’ has not been declared
   51 | int ConvertDoubleToByteArray(double value, uint8_t out_bytes[8]);
  |^~~
...

Processed: notforwarded 1070335

[Debian Bug Tracking System]

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

> notforwarded 1070335
Bug #1070335 [samba-dev] samba-dev: missing Breaks+Replaces: libwbclient-dev 
(<< 2:4.20)
Unset Bug forwarded-to-address
>
End of message, stopping processing here.

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

Processed: forwarded 1070335 https://bugs.launchpad.net/designate/+bug/2064916

[Debian Bug Tracking System]

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

> forwarded 1070335 https://bugs.launchpad.net/designate/+bug/2064916
Bug #1070335 [samba-dev] samba-dev: missing Breaks+Replaces: libwbclient-dev 
(<< 2:4.20)
Set Bug forwarded-to-address to 
'https://bugs.launchpad.net/designate/+bug/2064916'.
>
End of message, stopping processing here.

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

Processed: notfound 1070236 in 2:4.19.6+dfsg-3

[Debian Bug Tracking System]

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

> notfound 1070236 2:4.19.6+dfsg-3
Bug #1070236 {Done: Michael Biebl } [python3-samba] 
python3-samba: SyntaxError during configuration phase of package on upgrade
No longer marked as found in versions samba/2:4.19.6+dfsg-3.
> thanks
Stopping processing here.

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

Bug#1070188: marked as done (python3-spyder: uninstallable in unstable due to pylint)

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2024 11:22:09 +
with message-id 
and subject line Bug#1070188: fixed in spyder 5.5.1+ds-2
has caused the Debian Bug report #1070188,
regarding python3-spyder: uninstallable in unstable due to pylint
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.)


-- 
1070188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070188
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-spyder
Version: 5.5.1+ds-1
Severity: important

Dear Maintainer,

python3-spyder is no longer installable in sid; it depends (and
build-depends) on pylint (< 3.1~) but pylint is currently 3.1.0-1 in
unstable.

Loosening the versioned dependency is enough to allow spyder to build,
but I don't know whether that introduces runtime changes or not.

Roland.
--- End Message ---
--- Begin Message ---
Source: spyder
Source-Version: 5.5.1+ds-2
Done: Julian Gilbey 

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

Debian distribution maintenance software
pp.
Julian Gilbey  (supplier of updated spyder 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, 06 May 2024 10:41:11 +0100
Source: spyder
Architecture: source
Version: 5.5.1+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Julian Gilbey 
Closes: 1070188
Changes:
 spyder (5.5.1+ds-2) unstable; urgency=medium
 .
   * Bump pylint dependency version (closes: #1070188)
   * Skip test depending on pytest-lazy-fixture, as it is incompatible with
 pytest 8.x (see #1070485)
Checksums-Sha1:
 b8599bb60ae54f9993fce13f56538a0d82021748 3738 spyder_5.5.1+ds-2.dsc
 c4a470c8a6de9d37d51a5467b3823b5896e0c2f3 34320 spyder_5.5.1+ds-2.debian.tar.xz
 4b1b054673fa49a4b8e1d856372eea49c286dd18 20204 
spyder_5.5.1+ds-2_amd64.buildinfo
Checksums-Sha256:
 7d5cc684db6ff2445ff0636bf1d4d308d944c8882cd1880cb8e340f60705eff6 3738 
spyder_5.5.1+ds-2.dsc
 4fec6feeaa2c934631cbed66337417a9bc99ec71458da823428ca3569afc0280 34320 
spyder_5.5.1+ds-2.debian.tar.xz
 4673b99be0bdf2a1332d08c6408a40323b2083b98cc3cd791c60c2682f016b88 20204 
spyder_5.5.1+ds-2_amd64.buildinfo
Files:
 6e5a196a6921f4c3d7cfe110d67aa496 3738 science optional spyder_5.5.1+ds-2.dsc
 b0c9c766f448224a2f445f741c8d8df9 34320 science optional 
spyder_5.5.1+ds-2.debian.tar.xz
 ac08a0e66f0709c13ce6991bf0940062 20204 science optional 
spyder_5.5.1+ds-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCAAtFiEEfhrD+iemSShMMj72aVxCkxbAe/4FAmY4uiwPHGpkZ0BkZWJp
YW4ub3JnAAoJEGlcQpMWwHv+WI8P/0og9oHWcx5l0FrrO0+kZEO7i2sY6S6MLEMA
Lb3l0Ud7WUMSAn4fejlFnownbYidT7Co2GqvkSgMdGi101npbYoK/hY6yMlpBKd3
OparaXb0y1H70cSui8F4XijrEtvJZwr7uZPnyhcOvoJifjCL4fgfGZN9dS6k9rWp
hjct2kSLhmWnfTvXL345FWI26pLfgi6bH0CbOn63Z8HmA0xq26z2iEy6L9Xgg2dN
fjLrQSQCp14OV8TbszcCVzn5DJRfZFzC5PAXl0LrvzcJ89S9BpCxu71a7pkP68a+
rrWsyh/hGwb/aRmAC8WJ3gqhFzbSkgNEadHr06fTXcdQnzWHmzubblqNMddm5C1c
w60FOB0i/YjznTREUJRJLjGINzuBk0KNzMD2Jt16f5iq+YXBLb4EgyJoZUZyo6z8
3VSLIfA0oft/JszPzgNiDSshsp2XaB3zbiggHwesyrhi/lU40fRcC8ct4QS58+od
YoeBh+ECJSpNXjcHVbcrRnhmpkas5r4vt5hj1jNxHyp7FQgNgKgh5j1LJpztQjEj
oNmTHraisUCyQkb8RZCcnKibf9F6i+efZR60jl3sx3grXfiDxuIEJp9y6OAeeU5J
8ZRLqfLLqHPykqfEl7JnRYuljs8LmNqqUWIVPvjn8+AvsE/+1kLbKyPv5rH664hM
9ykVtBWT
=ES+R
-END PGP SIGNATURE-



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

Bug#1070017: marked as done (google-android-installers: depends on pre-64 libraries)

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2024 13:23:37 +0200
with message-id <22975850.EfDdHjke4D@debian>
and subject line 
has caused the Debian Bug report #1070017,
regarding google-android-installers: depends on pre-64 libraries
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.)


-- 
1070017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070017
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: google-android-installers
Version: =1710437545-4
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

google-android-installers builds binary packages that depend on shared
libraries (at least libasound2) that were renamed as part of the t64
transition. Please update the dependencies accordingly.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
See previous mail. I don't think there is anything more to do.--- End Message ---

Bug#1070492: mixxx: Tries to use the network during build

[Santiago Vila]

Package: src:mixxx
Version: 2.4.0+dfsg-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
  --- LOG END ---
  error: downloading 
'https://github.com/xsco/libdjinterop/archive/refs/tags/0.20.1.tar.gz' failed
  status_code: 6
  status_string: "Couldn't resolve host name"
  log:
  --- LOG BEGIN ---
  Could not resolve host: github.com

  Closing connection



  --- LOG END ---
  error: downloading 
'https://launchpad.net/~xsco/+archive/ubuntu/djinterop/+sourcefiles/libdjinterop/0.20.1-0ubuntu1/libdjinterop_0.20.1.orig.tar.gz'
 failed
  status_code: 6
  status_string: "Couldn't resolve host name"
  log:
  --- LOG BEGIN ---
  Could not resolve host: launchpad.net

  Closing connection



  --- LOG END ---
  




make[4]: *** [CMakeFiles/libdjinterop.dir/build.make:102: 
libdjinterop-prefix/src/libdjinterop-stamp/libdjinterop-download] Error 1
make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[3]: *** [CMakeFiles/Makefile2:317: CMakeFiles/libdjinterop.dir/all] Error 2
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[2]: *** [Makefile:169: all] Error 2
make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
dh_auto_build: error: cd obj-x86_64-linux-gnu && make -j2 "INSTALL=install 
--strip-program=true" VERBOSE=1 returned exit code 2
make[1]: *** [debian/rules:21: override_dh_auto_build] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:15: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


The build was made using the unshare backend of sbuild, which
does not allow network access.

If you need a full build log, it also fails here for the same reason:

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

(X-Debian-Cc: Jochen, as we are tracking all packages which ftbfs with unshare)

Thanks.

Bug#1070491: rust-pipewire FTBFS on 32bit with 64bit time_t

[Adrian Bunk]

Source: rust-pipewire
Version: 0.8.0-4
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=rust-pipewire&ver=0.8.0-4

...
error[E0308]: mismatched types
   --> src/thread_loop.rs:142:43
|
142 | nix::sys::time::TimeSpec::new(abstime.tv_sec, abstime.tv_nsec)
| - ^^ expected `i64`, 
found `i32`
| |
| arguments to this function are incorrect
|
note: associated function defined here
   --> /usr/share/cargo/registry/nix-0.27.1/src/sys/time.rs:339:18
|
339 | pub const fn new(seconds: time_t, nanoseconds: timespec_tv_nsec_t) -> 
Self {
|  ^^^
help: you can convert an `i32` to an `i64`
|
142 | nix::sys::time::TimeSpec::new(abstime.tv_sec.into(), 
abstime.tv_nsec)
| +++

error[E0308]: mismatched types
   --> src/thread_loop.rs:152:25
|
152 | tv_sec: abstime.tv_sec(),
|  expected `i32`, found `i64`

For more information about this error, try `rustc --explain E0308`.
error: could not compile `pipewire` (lib) due to 2 previous errors
...

Bug#1070489: rust-hypothesis FTBFS: test failures

[Adrian Bunk]

Source: rust-hypothesis
Version: 0.11.1-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=rust-hypothesis&ver=0.11.1-1
https://buildd.debian.org/status/logs.php?pkg=rust-hypothesis&ver=0.11.1-2

...
 Running 
`/<>/target/x86_64-unknown-linux-gnu/release/deps/cli-60d293523176a82c
 --test-threads=1 --skip it_works --skip make --skip sync --skip tag_filter`

running 5 tests
test add_and_delete_annotation ... FAILED
test create_and_leave_group ... FAILED
test search_annotations ... FAILED
test update_annotation ... FAILED
test update_group ... FAILED

failures:

 add_and_delete_annotation stdout 
Error: path not found

Caused by:
path not found

Location:
tests/cli.rs:33:5

 create_and_leave_group stdout 
Error: path not found

Caused by:
path not found

Location:
tests/cli.rs:177:5

 search_annotations stdout 
Error: path not found

Caused by:
path not found

Location:
tests/cli.rs:114:5

 update_annotation stdout 
Error: path not found

Caused by:
path not found

Location:
tests/cli.rs:69:5

 update_group stdout 
thread 'update_group' panicked at 'assertion failed: group_id.is_ok()', 
tests/cli.rs:218:5
stack backtrace:
   0: rust_begin_unwind
 at /usr/src/rustc-1.70.0/library/std/src/panicking.rs:578:5
   1: core::panicking::panic_fmt
 at /usr/src/rustc-1.70.0/library/core/src/panicking.rs:67:14
   2: core::panicking::panic
 at /usr/src/rustc-1.70.0/library/core/src/panicking.rs:117:5
   3: cli::update_group
 at ./tests/cli.rs:218:5
   4: cli::update_group::{{closure}}
 at ./tests/cli.rs:212:22
   5: core::ops::function::FnOnce::call_once
 at /usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
   6: core::ops::function::FnOnce::call_once
 at /usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose 
backtrace.


failures:
add_and_delete_annotation
create_and_leave_group
search_annotations
update_annotation
update_group

test result: FAILED. 0 passed; 5 failed; 0 ignored; 0 measured; 0 filtered out; 
finished in 0.04s

error: test failed, to rerun pass `--test cli`
   Doc-tests hypothesis
 Running `rustdoc --edition=2021 --crate-type lib --crate-name hypothesis 
--test /<>/src/lib.rs --target x86_64-unknown-linux-gnu -L 
dependency=/<>/target/x86_64-unknown-linux-gnu/release/deps -L 
dependency=/<>/target/release/deps -L 
native=/<>/target/x86_64-unknown-linux-gnu/release/build/ring-21217903804af83c/out
 --test-args --test-threads=1 --test-args --skip --test-args it_works 
--test-args --skip --test-args make --test-args --skip --test-args sync 
--test-args --skip --test-args tag_filter --extern 
assert_cmd=/<>/target/x86_64-unknown-linux-gnu/release/deps/libassert_cmd-134b03450b103fd5.rlib
 --extern 
chrono=/<>/target/x86_64-unknown-linux-gnu/release/deps/libchrono-366b82fe4c132a7f.rlib
 --extern 
clap=/<>/target/x86_64-unknown-linux-gnu/release/deps/libclap-0253bc5809b2cb30.rlib
 --extern 
clap_complete=/<>/target/x86_64-unknown-linux-gnu/release/deps/libclap_complete-e7897de87192b73b.rlib
 --extern 
color_eyre=/<>/target/x86_64-unknown-linux-gnu/release/deps/libcolor_eyre-9811652bc2e783d9.rlib
 --extern 
derive_builder=/<>/target/x86_64-unknown-linux-gnu/release/deps/libderive_builder-b3eb91696292575e.rlib
 --extern 
dotenv=/<>/target/x86_64-unknown-linux-gnu/release/deps/libdotenv-9f37bf59e8da3298.rlib
 --extern 
eyre=/<>/target/x86_64-unknown-linux-gnu/release/deps/libeyre-913f1aee7266adfa.rlib
 --extern 
futures=/<>/target/x86_64-unknown-linux-gnu/release/deps/libfutures-badab9fb8631b2a1.rlib
 --extern 
hypothesis=/<>/target/x86_64-unknown-linux-gnu/release/deps/libhypothesis-12767b8516e42793.rlib
 --extern 
predicates=/<>/target/x86_64-unknown-linux-gnu/release/deps/libpredicates-53aab59c9f2a01ff.rlib
 --extern 
reqwest=/<>/target/x86_64-unknown-linux-gnu/release/deps/libreqwest-1c860df583615e4b.rlib
 --extern 
serde=/<>/target/x86_64-unknown-linux-gnu/release/deps/libserde-c2f81dc8b529eb86.rlib
 --extern 
serde_json=/<>/target/x86_64-unknown-linux-gnu/release/deps/libserde_json-86e653e5692938d9.rlib
 --extern 
thiserror=/<>/target/x86_64-unknown-linux-gnu/release/deps/libthiserror-a30286b97953be04.rlib
 --extern 
tokio=/<>/target/x86_64-unknown-linux-gnu/release/deps/libtokio-f2e0886742c2d315.rlib
 --extern 
url=/<>/target/x86_64-unknown-linux-gnu/release/deps/liburl-a6463baef11a8609.rlib
 -C embed-bitcode=no --cfg 'feature="clap"' --cfg 'feature="clap_complete"' 
--cfg 'feature="cli"' --cfg 'feature="color-eyre"' --cfg 'feature="default"' 
--cfg 'feature="eyre"' --error-format human`

running 18 tests
test src/annotations.rs - annotations::InputAnnotation (line 27) ... ok
test src/lib.rs - (line 44) - compile ... ok
test src/lib.rs - Hypothesis::create_annotation (line 213) ... FAILED
test src/lib.rs - H

Bug#1070460: marked as done (translate-toolkit: FTBFS: failing tests)

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2024 10:51:14 +
with message-id 
and subject line Bug#1070460: fixed in translate-toolkit 3.13.0-1
has caused the Debian Bug report #1070460,
regarding translate-toolkit: FTBFS: failing tests
to be marked as done.

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

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


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

Package: src:translate-toolkit
Version: 3.12.2-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary --with python3,sphinxdoc --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.12 with "build" 
module
I: pybuild base:311: python3.12 -m build --skip-dependency-check --no-isolation --wheel 
--outdir /<>/.pybuild/cpython3_3.12_translate
* Building wheel...
running bdist_wheel
running build
running build_py
creating build
creating build/lib

[... snipped ...]

unit.makeobsolete()

  assert str(unit) == ""

E   assert '#~ msgid "te...~ msgstr ""\n' == ''
E
E + #~ msgid "test"
E + #~ msgstr ""

tests/translate/storage/test_po.py:449: AssertionError
- Captured stdout call -
b'#. The automatic one\n#: test.c\nmsgid "test"\nmsgstr ""\n'
 TestXWikiFullPage.test_remove _

self = 

@mark.xfail(reason="removal not working in full page")
def test_remove(self):

  super().test_remove()


tests/translate/storage/test_properties.py:1614:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = 

def test_remove(self):
"""Tests removing a unit with a source string."""
store = self.StoreClass()
unit = store.addsourceunit("Test String")
# Some storages (MO, OmegaT) serialize only translated units
unit.target = "Test target"
assert headerless_len(store.units) == 1
withunit = bytes(store)
print(withunit)
store.removeunit(unit)
assert headerless_len(store.units) == 0
withoutunit = bytes(store)
print(withoutunit)

  assert withoutunit != withunit

E   assert b'\n\n

Processed: bug 1069310 is forwarded to https://github.com/hanwen/go-fuse/issues/514

[Debian Bug Tracking System]

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

> forwarded 1069310 https://github.com/hanwen/go-fuse/issues/514
Bug #1069310 [golang-github-hanwen-go-fuse-dev] FTBFS: tests failed
Set Bug forwarded-to-address to 'https://github.com/hanwen/go-fuse/issues/514'.
> thanks
Stopping processing here.

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

Bug#1069310: FTBFS: tests failed

[Reinhard Tartler]

I spent about half an hour looking at this, and wanted to share my thoughts:

- the build / tests succeed on all architectures but mips64el
- the panic in question appears to come from here:
https://sources.debian.org/src/golang-github-hanwen-go-fuse/2.4.2-2/fuse/print_linux.go/#L13
--
a map[int64]string is being set with the key "syscall.O_DIRECT" to the
value "DIRECT".
- that map is pre-initialized here:
https://sources.debian.org/src/golang-github-hanwen-go-fuse/2.4.2-2/fuse/print.go/#L64-L80
- on most architectures, such as amd64, the constant `syscall.O_DIRECT` is
set to the value 0x4000, cf.
https://cs.opensource.google/go/go/+/master:src/syscall/zerrors_linux_amd64.go;l=627;bpv=0;bpt=1
- on mipsel64, the value is set to 0x8000, cf.
https://cs.opensource.google/go/go/+/master:src/syscall/zerrors_linux_mips64.go;l=774?q=O_DIRECT&ss=go%2Fgo&start=11
- this value conflicts with
https://sources.debian.org/src/golang-github-hanwen-go-fuse/2.4.2-2/fuse/print.go/#L77
so
we now get conflicting values for the same key. This explains the message
"panic: DIRECT (8000) overlaps with LARGEFILE (8000).

-- 
regards,
Reinhard

Bug#1068755: FTBFS: tests failed

[Reinhard Tartler]

please ignore the above, it was meant to be sent to #1069310 instead

On Mon, May 6, 2024 at 6:34 AM Reinhard Tartler  wrote:

> I spent about half an hour looking at this, and wanted to share my
> thoughts:
>
> - the build / tests succeed on all architectures but mips64el
> - the panic in question appears to come from here:
> https://sources.debian.org/src/golang-github-hanwen-go-fuse/2.4.2-2/fuse/print_linux.go/#L13
> -- a map[int64]string is being set with the key "syscall.O_DIRECT" to the
> value "DIRECT".
> - that map is pre-initialized here:
> https://sources.debian.org/src/golang-github-hanwen-go-fuse/2.4.2-2/fuse/print.go/#L64-L80
> - on most architectures, such as amd64, the constant `syscall.O_DIRECT` is
> set to the value 0x4000, cf.
> https://cs.opensource.google/go/go/+/master:src/syscall/zerrors_linux_amd64.go;l=627;bpv=0;bpt=1
> - on mipsel64, the value is set to 0x8000, cf.
> https://cs.opensource.google/go/go/+/master:src/syscall/zerrors_linux_mips64.go;l=774?q=O_DIRECT&ss=go%2Fgo&start=11
> - this value conflicts with
> https://sources.debian.org/src/golang-github-hanwen-go-fuse/2.4.2-2/fuse/print.go/#L77
> so we now get conflicting values for the same key. This explains the
> message "panic: DIRECT (8000) overlaps with LARGEFILE (8000).
>
>
> --
> regards,
> Reinhard
>


-- 
regards,
Reinhard

Bug#1068755: FTBFS: tests failed

[Reinhard Tartler]

I spent about half an hour looking at this, and wanted to share my thoughts:

- the build / tests succeed on all architectures but mips64el
- the panic in question appears to come from here:
https://sources.debian.org/src/golang-github-hanwen-go-fuse/2.4.2-2/fuse/print_linux.go/#L13
-- a map[int64]string is being set with the key "syscall.O_DIRECT" to the
value "DIRECT".
- that map is pre-initialized here:
https://sources.debian.org/src/golang-github-hanwen-go-fuse/2.4.2-2/fuse/print.go/#L64-L80
- on most architectures, such as amd64, the constant `syscall.O_DIRECT` is
set to the value 0x4000, cf.
https://cs.opensource.google/go/go/+/master:src/syscall/zerrors_linux_amd64.go;l=627;bpv=0;bpt=1
- on mipsel64, the value is set to 0x8000, cf.
https://cs.opensource.google/go/go/+/master:src/syscall/zerrors_linux_mips64.go;l=774?q=O_DIRECT&ss=go%2Fgo&start=11
- this value conflicts with
https://sources.debian.org/src/golang-github-hanwen-go-fuse/2.4.2-2/fuse/print.go/#L77
so we now get conflicting values for the same key. This explains the
message "panic: DIRECT (8000) overlaps with LARGEFILE (8000).


-- 
regards,
Reinhard

Processed: Re: Bug#1070463: gnome-remote-desktop: 46 has failing build tests

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1070463 [src:gnome-remote-desktop] gnome-remote-desktop: 46 has failing 
build tests
Severity set to 'important' from 'serious'
> unblock 1050237 by -1
Bug #1050237 [release.debian.org] transition: mutter/gnome-shell 45
1050237 was blocked by: 1070463 1052414 1050241 1040005 1052145
1050237 was not blocking any bugs.
Removed blocking bug(s) of 1050237: 1070463

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

Bug#1070463: gnome-remote-desktop: 46 has failing build tests

[Jeremy Bícha]

Control: severity -1 important
Control: unblock 1050237 by -1

On Sun, May 5, 2024 at 1:15 PM Jeremy Bícha  wrote:
> The build tests were passing with version 45. It is not clear to me
> why the tests are failing in Debian Experimental but passing in Ubuntu
> 24.04 LTS.

I have ignored gnome-remote-desktop's test failures for now in Debian
since it is a higher priority to land GNOME Shell 46 in Testing.

Maybe there is a missing dependency and getting more things in
Unstable would help.

Thank you,
Jeremy Bícha

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 1061216 
> https://github.com/AcademySoftwareFoundation/openvdb/issues/1804
Bug #1061216 [src:openvdb] openvdb: Please upgrade to llvm-toolchain-18
Set Bug forwarded-to-address to 
'https://github.com/AcademySoftwareFoundation/openvdb/issues/1804'.
> thanks
Stopping processing here.

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

Bug#1066662: hping3: FTBFS: script.c:1351:29: error: implicit declaration of function ‘asprintf’; did you mean ‘vsprintf’? [-Werror=implicit-function-declaration]

[Michael Prokop]

* Lucas Nussbaum [Wed Mar 13, 2024 at 12:51:29PM +0100]:

[...]
> 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 -c -g -O2 -Werror=implicit-function-declaration 
> > -ffile-prefix-map=/<>=. -fstack-protector-strong 
> > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> > -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -Wall -I/usr/include/pcap 
> > -I/usr/include/tcl8.6 -DUSE_TCL -g  ars.c
> > script.c: In function ‘HpingTcl_AppInit’:
> > script.c:1351:29: error: implicit declaration of function ‘asprintf’; did 
> > you mean ‘vsprintf’? [-Werror=implicit-function-declaration]
> >  1351 | if (asprintf(&rcfile, "%s/.hpingrc", home) 
> > < 0)
> >   | ^~~~
> >   | vsprintf
[...]

Pending patch / MR available at
https://salsa.debian.org/debian/hping3/-/merge_requests/4

regards
-mika-


signature.asc
Description: PGP signature

Processed: tagging 1066662

[Debian Bug Tracking System]

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

> tags 102 + patch
Bug #102 [src:hping3] hping3: FTBFS: script.c:1351:29: error: implicit 
declaration of function ‘asprintf’; did you mean ‘vsprintf’? 
[-Werror=implicit-function-declaration]
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#1061216: Please upgrade to llvm-toolchain-17

[Sylvestre Ledru]

Le 06/05/2024 à 10:27, Gregor Riepl a écrit :

Which LLVM versions are you planning to remove?

15, 16 soon. 17 later.
Would it be possible to keep at least LLVM 15 until upstream has 
upgraded their code base?



Sounds very unlikely for the next Debian release.


If a fix for this can't be released on time, I'm requesting an 
exception for llvm-15. Removing OpenVDB from Debian will affect 
Blender, which is is relatively high-profile and should not just be 
axed for the sake if a pruning operation.


You still have time, we aren't going to release the trixie anytime soon 
:) but we won't probably block the removal in testing for openvdb (the 
popcon isn't high IMHO).





Is there any other reason why llvm-15 couldn't be kept, aside from the 
reason mentioned in 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050070 ("too many 
llvm version") ?


llvm-toolchain-X.Y is a very complex and heavy package. There are a lot 
of changes in each release (every 6 months).


Between the new release, the port to archs, debian changes, new bugs, 
etc, it is a lot of work to keep up.


So, we, Debian, have to make efforts to limit the number of versions and 
push our upstream developers to also keep up with upstream versions 
(they probably have too anyway).



Is there an upstream bug to follow the progress on their upgrade of 
LLVM?


There is now: 
https://github.com/AcademySoftwareFoundation/openvdb/issues/1804



Thanks. I subscribed!

Sylvestre

Bug#1068058: marked as done (libgtkada: FTBFS on armhf ( compilation of gtkada-canvas_view.adb failed))

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2024 08:39:59 +
with message-id 
and subject line Bug#1068058: fixed in libgtkada 24.0.0-3
has caused the Debian Bug report #1068058,
regarding libgtkada: FTBFS on armhf (  compilation of gtkada-canvas_view.adb 
failed)
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.)


-- 
1068058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068058
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgtkada
Severity: serious
Tags: ftbfs
Control: found -1 24.0.0-2
X-Debbugs-Cc: ken...@xdump.org

Dear Maintainer,

libgtkada fails to build on armhf.

FYI:

https://buildd.debian.org/status/fetch.php?pkg=libgtkada&arch=armhf&ver=24.0.0-2&stamp=1710988310&raw=0

Regards,
--- End Message ---
--- Begin Message ---
Source: libgtkada
Source-Version: 24.0.0-3
Done: Nicolas Boulenguez 

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

Debian distribution maintenance software
pp.
Nicolas Boulenguez  (supplier of updated libgtkada 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, 06 May 2024 05:35:15 +
Source: libgtkada
Architecture: source
Version: 24.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Ludovic Brenta 
Changed-By: Nicolas Boulenguez 
Closes: 1068058
Changes:
 libgtkada (24.0.0-3) unstable; urgency=medium
 .
   * Reduce optimization to -O1 on armhf.  Closes: #1068058.
Checksums-Sha1:
 9a66af7e2d9777de8fd56a948375db4fe737a52b 2581 libgtkada_24.0.0-3.dsc
 cbb89402a2b9442a8d57ecdb37679af3b44aaa13 22488 libgtkada_24.0.0-3.debian.tar.xz
Checksums-Sha256:
 6de1cfeb7e2f3c7513aedfb0408e525b472a09b1c51630dfefe35f1e0a6a2890 2581 
libgtkada_24.0.0-3.dsc
 98bb86da7e2732ed0dc73527093e0b9fa12f80eb4b30cd070dbe2a6afcee336f 22488 
libgtkada_24.0.0-3.debian.tar.xz
Files:
 3f75b3af22742c9a619d72701d69d18e 2581 libdevel optional libgtkada_24.0.0-3.dsc
 09596f0e69b71742bb48195903c11fd8 22488 libdevel optional 
libgtkada_24.0.0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEawm/6zYhqkfTAKHtFHKayZgPCdIFAmY4k6sTHG5pY29sYXNA
ZGViaWFuLm9yZwAKCRAUcprJmA8J0lhxD/4/cKr4CixhVJ8kh/Nf2bwzbLNfJ12Q
N5wS7T7/Wx22kqcOwjGmuSLeRWMdu+xghey9VeVE+hCrYGCeukf+d3JMz7rlfOlH
XQnxM2iv/AhutP+0Tw9Txfz8oCGRddsPoEWw7nnJWN0QQF6Chf1tJpJqF9AWfAj6
xNoWuNdMZVbPbzJwvyokRQ1H1o4IBwQuf9lQYwdciwYGZ0VbKj69X//EizS3TN6a
PFqVsb3r7OkhHqD76PqFM2Zauk9nwrryj7cpFJeuKqHqeji9wbSFJRYZolnxE9Eh
hnZU3+X1/geuSjSpqGY17NXxfoyBBznnCqm8fFr/V3Kedt+fDUZjM2EPQJhM3fL/
UK5pzExaj2EpB7xpJVe07MYyKOUVtiGUcrUEAjbUWc0ImbDLYY/5agwiQvGMVScY
QPSGE18Swqlny0KuqtF4swN95pWOc3/rB1jNJEpeEAoBIr+PVqGw4VvJIRSuIpTF
FAY8i8eIy32j45AS/ej2coJr+yhmnfK4qAh64DD63we0dd48oBe9ZKuhlHYqrunQ
UGs8Z9mRU2OD0IqlxFZAaMkeoH0BPAzO7B+HxFiGcZ1ZEhsEi9waDlT6Ub2HIRnh
cyMmr5TfdLfdrD4r9HENBk/+tsN3rpcpBODbZ5W8JoN/6fzr3J16Ndc8H4T7TYrA
thX4eA+y+N/OQQ==
=wCpY
-END PGP SIGNATURE-



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

Bug#1061216: Please upgrade to llvm-toolchain-17

[Gregor Riepl]

Which LLVM versions are you planning to remove?

15, 16 soon. 17 later.
Would it be possible to keep at least LLVM 15 until upstream has 
upgraded their code base?



Sounds very unlikely for the next Debian release.


If a fix for this can't be released on time, I'm requesting an exception 
for llvm-15. Removing OpenVDB from Debian will affect Blender, which is 
is relatively high-profile and should not just be axed for the sake if a 
pruning operation.


Is there any other reason why llvm-15 couldn't be kept, aside from the 
reason mentioned in 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050070 ("too many 
llvm version") ?



Is there an upstream bug to follow the progress on their upgrade of LLVM?


There is now: 
https://github.com/AcademySoftwareFoundation/openvdb/issues/1804

Processed: reassign 1059874 to src:uhd, tagging 1063948, tagging 1061744, tagging 1070419, tagging 1062881 ...

[Debian Bug Tracking System]

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

> reassign 1059874 src:uhd 4.6.0.0+ds1-5
Bug #1059874 [libuhd4.6.0] libuhd4.6.0: Segfault in gqrx related to libuhd 4.6.0
Warning: Unknown package 'libuhd4.6.0'
Bug reassigned from package 'libuhd4.6.0' to 'src:uhd'.
No longer marked as found in versions uhd/4.6.0.0+ds1-5.
Ignoring request to alter fixed versions of bug #1059874 to the same values 
previously set
Bug #1059874 [src:uhd] libuhd4.6.0: Segfault in gqrx related to libuhd 4.6.0
Marked as found in versions uhd/4.6.0.0+ds1-5.
> tags 1063948 + experimental
Bug #1063948 {Done: Emmanuel Arias } [ipyparallel] 
ipyparallel: autopkgtest regression with pytest 8
Added tag(s) experimental.
> tags 1061744 + experimental
Bug #1061744 {Done: Emmanuel Arias } [src:ipyparallel] 
ipyparallel ftbfs with Python 3.12 as default
Added tag(s) experimental.
> tags 1070419 - sid trixie
Bug #1070419 [src:gnome-snapshot] src:gnome-snapshot: unsatisfied build 
dependency in testing: librust-gst-plugin-gtk4-0.11-dev
Removed tag(s) sid and trixie.
> tags 1062881 - sid trixie
Bug #1062881 [src:mia] mia: NMU diff for 64-bit time_t transition
Removed tag(s) sid and trixie.
> notfixed 1067220 1.06.2-14+b1
Bug #1067220 {Done: Nicolas Boulenguez } [src:libxmlezout] 
libxmlezout ftbfs on time_t64 architectures
The source 'libxmlezout' and version '1.06.2-14+b1' do not appear to match any 
binary packages
No longer marked as fixed in versions 1.06.2-14+b1.
> tags 1064311 - sid trixie
Bug #1064311 [src:rdkit] rdkit: NMU diff for 64-bit time_t transition
Removed tag(s) trixie and sid.
> tags 1063055 - sid trixie
Bug #1063055 [src:vowpal-wabbit] vowpal-wabbit: NMU diff for 64-bit time_t 
transition
Removed tag(s) sid and trixie.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1059874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059874
1061744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061744
1062881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062881
1063055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063055
1063948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063948
1064311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064311
1067220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067220
1070419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070419
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems