Processed: fixed 1022957 in 525.147.05-7

[Debian Bug Tracking System]

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

> fixed 1022957 525.147.05-7
Bug #1022957 [nex] nex: /usr/bin/nex is already provided by the nvi package
There is no source info for the package 'nex' at version '525.147.05-7' with 
architecture ''
Unable to make a source version for version '525.147.05-7'
Marked as fixed in versions 525.147.05-7.
> thanks
Stopping processing here.

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

Bug#1057549: crowdsec: FTBFS: FAIL: TestOneShot/permission_denied

[Cyril Brulebois]

Hi,

Cyril Brulebois  (2024-01-17):
> Santiago Vila  (2023-12-05):
> > […]
> 
> Thanks for the report. The relevant part didn't appear in the excerpt
> so I'm quoting the full build log below:
> 
> > === RUN   TestOneShot/permission_denied
> > file_test.go:234: 
> > Error Trace:
> > /<>/_build/src/github.com/crowdsecurity/crowdsec/pkg/cstest/utils.go:25
> > 
> > /<>/_build/src/github.com/crowdsecurity/crowdsec/pkg/acquisition/modules/file/file_test.go:234
> > Error:  An error is expected but got nil.
> > Test:   TestOneShot/permission_denied
> > === RUN   TestOneShot/ignored_directory
> > === RUN   TestOneShot/glob_syntax_error
> > === RUN   TestOneShot/no_matching_files
> > === RUN   TestOneShot/test.log
> > === RUN   TestOneShot/test.log.gz
> > === RUN   TestOneShot/unexpected_end_of_gzip_stream
> > === RUN   TestOneShot/deleted_file
> > --- FAIL: TestOneShot (0.00s)
> > --- FAIL: TestOneShot/permission_denied (0.00s)
> > --- PASS: TestOneShot/ignored_directory (0.00s)
> > --- PASS: TestOneShot/glob_syntax_error (0.00s)
> > --- PASS: TestOneShot/no_matching_files (0.00s)
> > --- PASS: TestOneShot/test.log (0.00s)
> > --- PASS: TestOneShot/test.log.gz (0.00s)
> > --- PASS: TestOneShot/unexpected_end_of_gzip_stream (0.00s)
> > --- PASS: TestOneShot/deleted_file (0.00s)

Is that problem still current? I cannot reproduce it with a brand new
sid environment, freshly created via either `pbuilder --create` or
`sbuild-createchroot`.


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


signature.asc
Description: PGP signature

Processed: Retag some bugs

[Debian Bug Tracking System]

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

> tags 1063497 - patch + fixed-upstream bookworm
Bug #1063497 [src:zfs-linux] zfs-dkms: Data loss bug in version in bookworm
Removed tag(s) patch.
Bug #1063497 [src:zfs-linux] zfs-dkms: Data loss bug in version in bookworm
Added tag(s) fixed-upstream and bookworm.
> tags 1023127 - patch
Bug #1023127 [src:zfs-linux] zfs-linux: please make zfs-{initramfs,dracut} 
Depend on their respective -core packages
Removed tag(s) patch.
>
End of message, stopping processing here.

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

Processed: Re-assign conflicts bug to non-free participant

[Debian Bug Tracking System]

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

> reassign 1063400 src:pgplot5
Bug #1063400 [src:plplot5] giza-dev: missing Conflicts: pgplot5t64
Warning: Unknown package 'src:plplot5'
Bug reassigned from package 'src:plplot5' to 'src:pgplot5'.
Ignoring request to alter found versions of bug #1063400 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1063400 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: notfixed 1022957 in 525.147.05-7, fixed 1063362 in 525.147.05-7

[Debian Bug Tracking System]

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

> notfixed 1022957 525.147.05-7
Bug #1022957 [nex] nex: /usr/bin/nex is already provided by the nvi package
There is no source info for the package 'nex' at version '525.147.05-7' with 
architecture ''
Unable to make a source version for version '525.147.05-7'
No longer marked as fixed in versions 525.147.05-7.
> fixed 1063362 525.147.05-7
Bug #1063362 [src:nvidia-graphics-drivers-tesla] nvidia-graphics-drivers-tesla: 
autopkgtest needs update for new version of linux
Marked as fixed in versions nvidia-graphics-drivers-tesla/525.147.05-7.
> thanks
Stopping processing here.

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

Bug#1063845: marked as done (unbound: Package 1.19.1 to fix CVE-2023-50387 and CVE-2023-50868)

[Debian Bug Tracking System]

Your message dated Thu, 15 Feb 2024 10:02:40 +
with message-id 
and subject line Bug#1063845: fixed in unbound 1.13.1-1+deb11u2
has caused the Debian Bug report #1063845,
regarding unbound: Package 1.19.1 to fix CVE-2023-50387 and CVE-2023-50868
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.)


-- 
1063845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063845
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: unbound
Version: 1.18.0-2
Severity: important
Tags: security
X-Debbugs-Cc: Debian Security Team 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Today 2 remote exploitable High Severity CVE's were published and
unbound has released version 1.19.1 to fix those.

Relevant links:
https://fosstodon.org/@nlnetlabs/111924266007688683
https://nlnetlabs.nl/news/2024/Feb/13/unbound-1.19.1-released/
https://kb.isc.org/docs/cve-2023-50387
https://kb.isc.org/docs/cve-2023-50868

I think a Release Critical Severity is more appropriate, but none of
the (by reportbug) presented options were applicable. It seems reportbug
then changed it to 'normal', which I manually changed to 'important'.

Fixing this bug would also fix bug #1051817, #1051818 and #1056631.

Link: https://bugs.debian.org/1051817
Link: https://bugs.debian.org/1051818
Link: https://bugs.debian.org/1056631

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

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

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQT1sUPBYsyGmi4usy/XblvOeH7bbgUCZcuATAAKCRDXblvOeH7b
buedAP0QEqqGjjN4ZP8nu+WdKqrUWupLtsaN6FqEyNOd5OSp3QD/Wfh/sE5azFqf
99HKnBGhNVhrnxlNYIPlEjIns5pVDQs=
=thcd
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: unbound
Source-Version: 1.13.1-1+deb11u2
Done: Salvatore Bonaccorso 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 13 Feb 2024 21:15:34 +0100
Source: unbound
Architecture: source
Version: 1.13.1-1+deb11u2
Distribution: bullseye-security
Urgency: high
Maintainer: unbound packagers 
Changed-By: Salvatore Bonaccorso 
Closes: 1063845
Changes:
 unbound (1.13.1-1+deb11u2) bullseye-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * Address DNSSEC protocol vulnerabilities (Closes: #1063845)
 - Fix CVE-2023-50387, DNSSEC verification complexity can be exploited to
   exhaust CPU resources and stall DNS resolvers.
 - Fix CVE-2023-50868, NSEC3 closest encloser proof can exhaust CPU.
Checksums-Sha1: 
 c0201ed9b8890d8fe94e29ca4104fcfd68bf283e 3198 unbound_1.13.1-1+deb11u2.dsc
 561522b06943f6d1c33bd78132db1f7020fc4fd1 5976957 unbound_1.13.1.orig.tar.gz
 f20b17d911dfa8efb58ee412207829cea2d964c4 833 unbound_1.13.1.orig.tar.gz.asc
 c6ed27f27987beb1550ac25e4c292fae4d3da1f7 44472 
unbound_1.13.1-1+deb11u2.debian.tar.xz
Checksums-Sha256: 
 4594320d0d1c8997ce17530763637ae96dcf72ce5d9412a01a9fd71806ac6afe 3198 
unbound_1.13.1-1+deb11u2.dsc
 8504d97b8fc5bd897345c95d116e0ee0ddf8c8ff99590ab2b4bd13278c9f50b8 5976957 
unbound_1.13.1.orig.tar.gz
 1ca1fb3db4baa3e831bc42fcecf3eaceb316abf7a2d816dc46d0efcd199f419e 833 
unbound_1.13.1.orig.tar.gz.asc
 2c0289540d8530d2a7cf377d4fe2ba87f4998a37e452d5b8b4f8d353b89dd2e7 44472 
unbound_1.13.1-1+deb11u2.debian.tar.xz
Files: 
 2d1aa1cfbd128149d6432ae421327e31 3198 net optional unbound_1.13.1-1+deb11u2.dsc
 0cd660a40d733acc6e7cce43731cac62 5976957 net optional 
unbound_1.13.1.orig.tar.gz
 4c3726440d8271df13ba2189846141e6 833 net optional 
unbound_1.13.1.orig.tar.gz.asc
 93f94d93ed156ca1ede8b9b2aae75d53 44472 net optional 

Bug#1060961: marked as done (clapper: FTBFS: make: *** [debian/rules:6: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Thu, 15 Feb 2024 11:00:31 +0100
with message-id <170799123103.3855153.12503207033974967424@localhost>
and subject line Re: clapper: FTBFS: make: *** [debian/rules:6: binary] Error 25
has caused the Debian Bug report #1060961,
regarding clapper: FTBFS: make: *** [debian/rules:6: binary] Error 25
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.)


-- 
1060961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060961
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: clapper
Version: 0.5.2-7
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 
> meson setup .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr 
> --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu 
> -Dpython.bytecompile=-1
> The Meson build system
> Version: 1.3.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: com.github.rafostar.Clapper
> Project version: 0.5.2
> C compiler for the host machine: cc (gcc 13.2.0 "cc (Debian 13.2.0-9) 13.2.0")
> C linker for the host machine: cc ld.bfd 2.41.50.20231227
> C++ compiler for the host machine: c++ (gcc 13.2.0 "c++ (Debian 13.2.0-9) 
> 13.2.0")
> C++ linker for the host machine: c++ ld.bfd 2.41.50.20231227
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Compiler for C++ supports arguments -Wno-non-virtual-dtor: YES 
> Compiler for C supports link arguments -Wl,-Bsymbolic-functions: YES 
> Compiler for C supports arguments -fno-strict-aliasing: YES 
> Compiler for C++ supports arguments -fno-strict-aliasing: YES 
> Message: Disabling GLib cast checks
> Message: Disabling GLib asserts
> Message: Disabling GLib checks
> Has header "dlfcn.h" : YES 
> Has header "fcntl.h" : YES 
> Has header "inttypes.h" : YES 
> Has header "memory.h" : YES 
> Has header "netinet/in.h" : YES 
> Has header "netinet/ip.h" : YES 
> Has header "netinet/tcp.h" : YES 
> Has header "pthread.h" : YES 
> Has header "stdint.h" : YES 
> Has header "stdlib.h" : YES 
> Has header "strings.h" : YES 
> Has header "string.h" : YES 
> Has header "sys/param.h" : YES 
> Has header "sys/socket.h" : YES 
> Has header "sys/stat.h" : YES 
> Has header "sys/time.h" : YES 
> Has header "sys/types.h" : YES 
> Has header "sys/utsname.h" : YES 
> Has header "unistd.h" : YES 
> Checking for function "dcgettext" : YES 
> Checking for function "getpagesize" : YES 
> Checking for function "gmtime_r" : YES 
> Checking for function "memfd_create" : YES 
> Checking for function "mmap" : YES 
> Checking for function "pipe2" : YES 
> Checking for function "getrusage" : YES 
> Checking for size of "char" : 1 
> Checking for size of "int" : 4 
> Checking for size of "long" : 8 
> Checking for size of "short" : 2 
> Checking for size of "void*" : 8 
> Compiler for C supports arguments -Wmissing-prototypes: YES 
> Compiler for C supports arguments -Wdeclaration-after-statement: YES 
> Compiler for C supports arguments -Wold-style-definition: YES 
> Compiler for C++ supports arguments -Wformat-nonliteral: YES 
> Compiler for C supports arguments -Wmissing-declarations: YES 
> Compiler for C++ supports arguments -Wmissing-declarations: YES 
> Compiler for C supports arguments -Wredundant-decls: YES 
> Compiler for C++ supports arguments -Wredundant-decls: YES 
> Compiler for C supports arguments -Wwrite-strings: YES 
> Compiler for C++ supports arguments -Wwrite-strings: YES 
> Compiler for C supports arguments -Wformat: YES 
> Compiler for C++ supports arguments -Wformat: YES 
> Compiler for C supports arguments -Wformat-security: YES 
> Compiler for C++ supports arguments -Wformat-security: YES 
> Compiler for C supports arguments -Winit-self: YES 
> Compiler for C++ supports arguments -Winit-self: YES 
> Compiler for C supports arguments -Wmissing-include-dirs: YES 
> Compiler for C++ supports arguments -Wmissing-include-dirs: YES 
> Compiler for C supports arguments -Waddress: YES 
> Compiler for C++ supports arguments -Waddress: YES 
> Compiler for C supports arguments -Wno-multichar: YES 
> Compiler for C++ supports arguments -Wno-multichar: YES 
> Compiler for C supports arguments -Wvla: YES 
> Compiler for C++ supports arguments -Wvla: YES 
> Compiler for C 

Bug#1060936: marked as done (udm: FTBFS: make[1]: *** [debian/rules:68: override_dh_auto_build] Error 2)

[Debian Bug Tracking System]

Your message dated Thu, 15 Feb 2024 13:05:11 +0200
with message-id 

and subject line udm: FTBFS: make[1]: *** [debian/rules:68: 
override_dh_auto_build] Error 2
has caused the Debian Bug report #1060936,
regarding udm: FTBFS: make[1]: *** [debian/rules:68: override_dh_auto_build] 
Error 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.)


-- 
1060936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060936
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: udm
Version: 1.0.0.322-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # this looks awfull and I hope there is a better solution
> #  but at the moment at least the package builds
> mkdir /<>/tmphome
> echo "#INCLUDE /etc/fpc.cfg" > /<>/tmphome/.fpc.cfg
> echo "-dLCLGTK2" >> /<>/tmphome/.fpc.cfg
> echo "-Fu/usr/lib/lazarus/2.2.6/components/lazutils/lib/x86_64-linux" >> 
> /<>/tmphome/.fpc.cfg
> echo "-Fu/usr/lib/lazarus/2.2.6/packager/units/x86_64-linux" >> 
> /<>/tmphome/.fpc.cfg
> echo "-Fu/usr/lib/lazarus/2.2.6/lcl/units/x86_64-linux" >> 
> /<>/tmphome/.fpc.cfg
> echo "-Fu/usr/lib/lazarus/2.2.6/components/ideintf/units/x86_64-linux/gtk2/" 
> >> /<>/tmphome/.fpc.cfg
> echo 
> "-Fu/usr/lib/lazarus/2.2.6/components/lazcontrols/lib/x86_64-linux/gtk2/" >> 
> /<>/tmphome/.fpc.cfg
> echo "-Fu/usr/lib/lazarus/2.2.6/components/synedit/units/x86_64-linux/gtk2/" 
> >> /<>/tmphome/.fpc.cfg
> echo "-Fu/usr/lib/lazarus/2.2.6/components/tachart/lib/x86_64-linux/gtk2/" >> 
> /<>/tmphome/.fpc.cfg
> echo "-Fu/usr/lib/lazarus/2.2.6/components/printers/lib/x86_64-linux/gtk2/" 
> >> /<>/tmphome/.fpc.cfg
> echo 
> "-Fu/usr/lib/lazarus/2.2.6/components/cairocanvas/lib/x86_64-linux/gtk2/" >> 
> /<>/tmphome/.fpc.cfg
> echo "-Fu/usr/lib/lazarus/2.2.6/lcl/units/x86_64-linux/gtk2/" >> 
> /<>/tmphome/.fpc.cfg
> ln -s /usr/lib/lazarus/2.2.6/components/freetype/ttcalc4.inc
> ln -s /usr/lib/lazarus/2.2.6/components/freetype/ttconfig.inc
> ln -s /usr/lib/lazarus/2.2.6/components/freetype/ttraster_sweep.inc
> ln -s /usr/lib/lazarus/2.2.6/components/opengl/openglcontext.res
> ln -s /usr/lib/lazarus/2.2.6/components/buildintf/ideoptionsintf.pas
> ln -s /usr/lib/lazarus/2.2.6/components/buildintf/baseideintf.pas
> ln -s /usr/lib/lazarus/2.2.6/components/buildintf/macrointf.pas
> ln -s /usr/lib/lazarus/2.2.6/components/buildintf/macrodefintf.pas
> ln -s /usr/lib/lazarus/2.2.6/components/buildintf/compoptsintf.pas
> ln -s /usr/lib/lazarus/2.2.6/components/buildintf/projectintf.pas
> ln -s /usr/lib/lazarus/2.2.6/components/buildintf/newitemintf.pas
> ln -s /usr/lib/lazarus/2.2.6/components/buildintf/projpackintf.pas
> ln -s /usr/lib/lazarus/2.2.6/components/buildintf/buildstrconsts.pas
> ln -s /usr/lib/lazarus/2.2.6/components/buildintf/ideexterntoolintf.pas
> ln -s /usr/lib/lazarus/2.2.6/components/buildintf/lazmsgworker.pas
> ln -s /usr/lib/lazarus/2.2.6/components/opengl/openglcontext.pas
> ln -s /usr/lib/lazarus/2.2.6/components/opengl/glgtkglxcontext.pas
> ln -s /usr/lib/lazarus/2.2.6/components/opengl/lazopenglcontext.pas
> ln -s /usr/lib/lazarus/2.2.6/components/freetype/easylazfreetype.pas
> ln -s /usr/lib/lazarus/2.2.6/components/freetype/lazfreetype.pas
> ln -s /usr/lib/lazarus/2.2.6/components/freetype/tttypes.pas
> ln -s /usr/lib/lazarus/2.2.6/components/freetype/tterror.pas
> ln -s /usr/lib/lazarus/2.2.6/components/freetype/ttcalc4.pas
> ln -s /usr/lib/lazarus/2.2.6/components/freetype/ttcalc.pas
> ln -s /usr/lib/lazarus/2.2.6/components/freetype/ttmemory.pas
> ln -s /usr/lib/lazarus/2.2.6/components/freetype/tttables.pas
> ln -s /usr/lib/lazarus/2.2.6/components/freetype/ttcache.pas
> ln -s /usr/lib/lazarus/2.2.6/components/freetype/ttfile.pas
> ln -s /usr/lib/lazarus/2.2.6/components/freetype/ttcmap.pas
> ln -s /usr/lib/lazarus/2.2.6/components/freetype/ttobjs.pas
> ln -s /usr/lib/lazarus/2.2.6/components/freetype/ttload.pas
> ln -s /usr/lib/lazarus/2.2.6/components/freetype/ttinterp.pas
> ln -s /usr/lib/lazarus/2.2.6/components/freetype/ttgload.pas
> ln -s /usr/lib/lazarus/2.2.6/components/freetype/ttkern.pas
> ln -s /usr/lib/lazarus/2.2.6/components/freetype/ttraster.pas
> ln -s /usr/lib/lazarus/2.2.6/components/freetype/ttprofile.pas
> ln -s /usr/lib/lazarus/2.2.6/components/freetype/lazfreetypefontcollection.pas
> lazbuild --widgetset=gtk2 -B udm.lpi
> CopySecondaryConfigFile /etc/lazarus/environmentoptions.xml -> 
> 

Bug#1063922: libnfft3-long4 has an undeclared file conflict

[Andreas Beckmann]

Followup-For: Bug #1063922

This looks like you want 
  Breaks+Replaces: libnfft3-long2 (>= 3.5)
(Yes, really a >= relation, as the older versions are co-installable,
only the versions that didn't do the required transition are the
problem.)


Andreas

Bug#1061024: marked as done (transgui: FTBFS: InitializeFppkg failed: Unable to create file "/sbuild-nonexistent/.config/fppkg.cfg": No such file or directory)

[Debian Bug Tracking System]

Your message dated Thu, 15 Feb 2024 13:04:16 +0200
with message-id 

and subject line transgui: FTBFS: InitializeFppkg failed: Unable to create file 
"/sbuild-nonexistent/.config/fppkg.cfg": No such file or directory
has caused the Debian Bug report #1061024,
regarding transgui: FTBFS: InitializeFppkg failed: Unable to create file 
"/sbuild-nonexistent/.config/fppkg.cfg": 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.)


-- 
1061024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061024
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: transgui
Version: 5.18.0+dfsg-3.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> lazbuild -B transgui.lpi --lazarusdir=/usr/lib/lazarus/default/
> CopySecondaryConfigFile /etc/lazarus/environmentoptions.xml -> 
> /sbuild-nonexistent/.lazarus/environmentoptions.xml
> WARNING: unable to create primary config directory 
> "/sbuild-nonexistent/.lazarus"
> SetupCompilerFilename: Searching compiler ...
> SearchCompilerCandidates Value=/usr/bin/fpc File=/usr/bin/fpc
> SetupCompilerFilename: using /usr/bin/fpc
> Hint: (lazarus) storing Lazarus directory "/usr/lib/lazarus/default/" 
> Compiler path "/usr/bin/fpc" in 
> "/sbuild-nonexistent/.lazarus/environmentoptions.xml"
> Error: (lazarus) unable to edit file 
> /sbuild-nonexistent/.lazarus/environmentoptions.xml
> InitializeFppkg failed: Unable to create file 
> "/sbuild-nonexistent/.config/fppkg.cfg": No such file or directory
> Note: (lazarus) Invalid Package Link: file 
> "/usr/lib/lazarus/default/ide/packages/ideconfig/ideconfig.lpk" does not 
> exist.
> 
>   $55596A94CB7A
>   $55596A947B65
>   $55596A8A3F2E
>   $55596AEF5713
>   $55596AA57C83
>   $55596AA421DE
>   $55596AA420D8
>   $55596A8A813D
>   $55596A8A5D64
>   $55596A8A43EB
>   $55596A8A9C93
>   $55596A8AC979
>   $55596A8CE75C
> Error: (lazbuild) Package file not found
> The package "IdeConfig" is installed but no valid package file (.lpk) was 
> found.
> A broken dummy package was created.
> lazbuild is non interactive, aborting now.
> make[1]: *** [debian/rules:13: override_dh_auto_build] Error 2


The full build log is available from:
http://qa-logs.debian.net/2024/01/15/transgui_5.18.0+dfsg-3.1_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
This was actually bug #1061034 in Lazarus.--- End Message ---

Processed: Re-assign conflicts bug to non-free participant

[Debian Bug Tracking System]

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

> reassign 1063400 src:plplot5
Bug #1063400 [giza-dev] giza-dev: missing Conflicts: pgplot5t64
Bug reassigned from package 'giza-dev' to 'src:plplot5'.
Warning: Unknown package 'src:plplot5'
Warning: Unknown package 'src:plplot5'
No longer marked as found in versions giza/1.4.1-1.
Warning: Unknown package 'src:plplot5'
Warning: Unknown package 'src:plplot5'
Ignoring request to alter fixed versions of bug #1063400 to the same values 
previously set
Warning: Unknown package 'src:plplot5'
> affects 1063400 src:giza
Bug #1063400 [src:plplot5] giza-dev: missing Conflicts: pgplot5t64
Warning: Unknown package 'src:plplot5'
Added indication that 1063400 affects src:giza
Warning: Unknown package 'src:plplot5'
> thanks
Stopping processing here.

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

Processed: Re-assign conflicts bug to non-free participant

[Debian Bug Tracking System]

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

> reassign 1063400 pgplot5 5.2.2-19.6~exp1
Bug #1063400 [src:pgplot5] giza-dev: missing Conflicts: pgplot5t64
Bug reassigned from package 'src:pgplot5' to 'pgplot5'.
Ignoring request to alter found versions of bug #1063400 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1063400 to the same values 
previously set
Bug #1063400 [pgplot5] giza-dev: missing Conflicts: pgplot5t64
There is no source info for the package 'pgplot5' at version '5.2.2-19.6~exp1' 
with architecture ''
Unable to make a source version for version '5.2.2-19.6~exp1'
Marked as found in versions 5.2.2-19.6~exp1.
> thanks
Stopping processing here.

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

Bug#1063942: nginx: Violation of DFSG article 5

[Anon]

Source: nginx
Version: 1.24.0-2
Severity: serious
Tags: upstream
Justification: Policy 2.1.5

Dear Maintainer,

The company behind nginx fired half of their most senior programmers two
years ago, due to the country in which they reside (Russia).  This might
be a violation of DFSG 5 (Debian Policy 2.1.5)

No Discrimination Against Persons or Groups

That article is described in more detail as

The license must not discriminate against any person or group of
persons.

which isn't exactly what happened here, but the spirit of the DFSG
shouldn't restrict to the license but also to the maintainership of the
project.  nginx is maintained by a company that has violated the spirit
of the DFSG in their management of the project.  Also, we have
alternatives like freenginx, maintained by a former maintainer of nginx,
or Angie, also maintained by a former programmer of nginx.

See also:




Thanks.

Bug#1061341: marked as done (cyrus-common: identified for time_t transition but no ABI in shlibs)

[Debian Bug Tracking System]

Your message dated Thu, 15 Feb 2024 09:50:07 +
with message-id 
and subject line Bug#1061341: fixed in cyrus-imapd 3.10.0~beta1-2
has caused the Debian Bug report #1061341,
regarding cyrus-common: 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.)


-- 
1061341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061341
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cyrus-common
Version: 3.8.1-1
Severity: serious
User: debian-...@lists.debian.org
Usertags: time-t

Dear maintainers,

Analysis of the archive for the 64-bit time_t transition[0][1] identifies
cyrus-common 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, cyrus-commons's shlibs file declares a dependency on a library
package name that contains no ABI information:

$ cat DEBIAN/shlibs
libcyrus 0 cyrus-common (>= 3.8.1)
libcyrus_imap 0 cyrus-common (>= 3.8.1)
libcyrus_min 0 cyrus-common (>= 3.8.1)
libcyrus_sieve 0 cyrus-common (>= 3.8.1)
$

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

Looking at the archive, there are packages that depend on these libraries,
cyrus-admin and cyrus-clients.  Despite being built from the same source
package, they do not have a strict versioned dependency on cyrus-common but
instead use the shlibs.

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 (upgrading cyrus-common without also
upgrading cyrus-{admin,clients}) 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/cyrus-dev/base/log.txt


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: cyrus-imapd
Source-Version: 3.10.0~beta1-2
Done: Yadd 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 15 Feb 2024 13:16:02 +0400
Source: cyrus-imapd
Architecture: source
Version: 3.10.0~beta1-2
Distribution: experimental
Urgency: medium
Maintainer: Debian Cyrus Team 
Changed-By: Yadd 
Closes: 1061341
Changes:
 cyrus-imapd (3.10.0~beta1-2) experimental; urgency=medium
 .
   * Add ABI flags (#1061341)
   * Drop unusable .h files from cyrus-dev (Closes: #1061341)
   * Build dependencies: replace pkg-config by pkgconf
Checksums-Sha1: 
 536fbc8c71ae34971f4b2bd9e679bb128a581542 5482 cyrus-imapd_3.10.0~beta1-2.dsc
 eb9b510e01b8197443d55a1aef6b49727d237b86 86432 
cyrus-imapd_3.10.0~beta1-2.debian.tar.xz
Checksums-Sha256: 
 f40c29fa00d02232e2eca9b5bdb20b45e6248aeb87fb7cb323608983b5b7bfea 5482 
cyrus-imapd_3.10.0~beta1-2.dsc
 63d81921b2ce1ece4c0e8c2ac4b2a95885c3ab3b1a1a9f1b13c0abad173ad06f 86432 
cyrus-imapd_3.10.0~beta1-2.debian.tar.xz
Files: 
 eb9d867fc19af757ba76553c544244e9 5482 mail optional 
cyrus-imapd_3.10.0~beta1-2.dsc
 b535861908de54a3b0c774282e6cbe56 86432 mail optional 
cyrus-imapd_3.10.0~beta1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmXN2VUACgkQ9tdMp8mZ
7uk69g/+NW8JPKIwOab/jb9CdOMa+zAd7P9FMX1yGsNIX2OrU6VJqqq3LXD9+Rll
hkC5Yw7u/Cw+ANiI4732vaC1dIICPL/ayMdPEApZj692yWJ7sDX+pQ/3Nd39fA13

Bug#1063942: marked as done (nginx: Violation of DFSG article 5)

[Debian Bug Tracking System]

Your message dated Thu, 15 Feb 2024 10:31:03 +
with message-id <20240215103103.ga1343...@tack.einval.com>
and subject line Re: Bug#1063942: nginx: Violation of DFSG article 5
has caused the Debian Bug report #1063942,
regarding nginx: Violation of DFSG article 5
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.)


-- 
1063942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063942
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nginx
Version: 1.24.0-2
Severity: serious
Tags: upstream
Justification: Policy 2.1.5

Dear Maintainer,

The company behind nginx fired half of their most senior programmers two
years ago, due to the country in which they reside (Russia).  This might
be a violation of DFSG 5 (Debian Policy 2.1.5)

No Discrimination Against Persons or Groups

That article is described in more detail as

The license must not discriminate against any person or group of
persons.

which isn't exactly what happened here, but the spirit of the DFSG
shouldn't restrict to the license but also to the maintainership of the
project.  nginx is maintained by a company that has violated the spirit
of the DFSG in their management of the project.  Also, we have
alternatives like freenginx, maintained by a former maintainer of nginx,
or Angie, also maintained by a former programmer of nginx.

See also:




Thanks.
--- End Message ---
--- Begin Message ---
On Thu, Feb 15, 2024 at 10:45:55AM +0100, Anon wrote:
>Source: nginx
>Version: 1.24.0-2
>Severity: serious
>Tags: upstream
>Justification: Policy 2.1.5
>
>Dear Maintainer,
>
>The company behind nginx fired half of their most senior programmers two
>years ago, due to the country in which they reside (Russia).  This might
>be a violation of DFSG 5 (Debian Policy 2.1.5)
>
>No Discrimination Against Persons or Groups
>
>That article is described in more detail as
>
>The license must not discriminate against any person or group of
>persons.
>
>which isn't exactly what happened here, but the spirit of the DFSG
>shouldn't restrict to the license but also to the maintainership of the
>project.  nginx is maintained by a company that has violated the spirit
>of the DFSG in their management of the project.  Also, we have
>alternatives like freenginx, maintained by a former maintainer of nginx,
>or Angie, also maintained by a former programmer of nginx.
This is not a Debian bug, closing.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"C++ ate my sanity" -- Jon Rabone--- End Message ---

Bug#1056419: Spinx help needed

[Dmitry Shachnev]

Hi Andreas!

On Thu, Feb 15, 2024 at 08:37:38AM +0100, Andreas Tille wrote:
> Control: tags -1 pending
> 
> Hi,
> 
> I pushed fixes for #1056419 and #1058311 to Git and I think should be
> fixed as well.  The only remaining build problem is new and caused by
> sphinx[1]:
> 
>   dh_sphinxdoc -i -O--buildsystem=pybuild
> dh_sphinxdoc: error: 
> debian/python-lmfit-doc/usr/share/doc/python3-lmfit/html/search.html 
> top-level node does not have data-content_root attribute
> 
> Unfortunately I have no idea how to fix this.  Any ideas?

lmfit-py ships a vendored copy of sphinx13 theme [1], which was copied from
Sphinx source code with a minor modification in 2020 [2] and rebased in
January 2022 [3]. However, there were more Sphinx releases since that month,
and the theme needs to be updated for compatibility with them.

In particular, the basic_layout.html file misses the change which was made
in Sphinx commit [4], without which the search will not work. There is a
comment under that commit which illustrates how exactly it will not work:
contentRoot will be undefined, and the browser will attempt to make requests
to a URL that has "undefined" in it. dh_sphinxdoc catches such issues and
produces an error about them.

So, to fix this issue, you should copy sphinx/themes/basic/layout.html from
the latest stable version of Sphinx to lmfit-py's basic_layout.html, applying
the one-line change which is described in [2] and [3].

[1]: doc/sphinx/theme/sphinx13/*
[2]: 
https://github.com/lmfit/lmfit-py/commit/29e4712036606913149e16b246340a7fbedd8829
[3]: 
https://github.com/lmfit/lmfit-py/commit/e2418377c9870e02c820d0fe40d2232187864a81
[4]: 
https://github.com/sphinx-doc/sphinx/commit/8e730ae303ae686705ea12f44ef11da926a87cf5

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#1059040: marked as done (libxml2: ABI change? (undefined references))

[Debian Bug Tracking System]

Your message dated Thu, 15 Feb 2024 10:06:30 +
with message-id 
and subject line Bug#1059040: fixed in libxml2 2.12.5+dfsg-0exp1
has caused the Debian Bug report #1059040,
regarding libxml2: ABI change? (undefined references)
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.)


-- 
1059040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059040
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libxml2
Version: 2.12.3+dfsg-0exp1
Severity: serious

Dear Maintainer,

Hi,

LibreOffice builds (patch available), but doesn't yet build with 2.12.
But that is not the point of this issue.

While test building current 24.2 snapshot which will become 24.2 rc1
later this week I get

[build LNK] Executable/pdfverify
S=/home/rene/LibreOffice/git/libreoffice-24-2 && I=$S/instdir && W=$S/workdir 
&&  mkdir -p $W/Dep/LinkTarget/Executable/ && RESPONSEFILE=/tmp/gbuild.yEebjc 
&& SYSTEM_BOOST="TRUE" 
LD_LIBRARY_PATH=${LD_LIBRARY_PATH:+$LD_LIBRARY_PATH:}"$I/program:$I/program"   
$W/LinkTarget/Executable/concat-deps ${RESPONSEFILE} > 
$W/Dep/LinkTarget/Executable/pdfverify.d.tmp && rm -f ${RESPONSEFILE}
mv 
/home/rene/LibreOffice/git/libreoffice-24-2/workdir/Dep/LinkTarget/Executable/pdfverify.d.tmp
 
/home/rene/LibreOffice/git/libreoffice-24-2/workdir/Dep/LinkTarget/Executable/pdfverify.d
S=/home/rene/LibreOffice/git/libreoffice-24-2 && I=$S/instdir && W=$S/workdir 
&&  /usr/bin/ccache x86_64-linux-gnu-g++ -pthread  -flto=jobserver 
-fuse-linker-plugin -O2  -Wl,-z,origin '-Wl,-rpath,$ORIGIN/../Library' 
-Wl,-rpath-link,$I/program  -Wl,-z,defs -Wl,-rpath-link,/lib:/usr/lib 
-Wl,-z,combreloc  -Wl,--hash-style=gnu  -Wl,-Bsymbolic-functions 
-L$W/LinkTarget/StaticLibrary -L$I/sdk/lib  -L$I/program  -L$I/program  
-L$W/LinkTarget/Library -ffat-lto-objects -Wl,-z,relro
$W/CxxObject/xmlsecurity/workben/pdfverify.o   -Wl,--start-group
-Wl,--end-group -Wl,--no-as-needed -luno_cppu -luno_cppuhelpergcc3 -luno_sal 
-lxmlsecurity -lmergedlo  -o $W/LinkTarget/Executable/pdfverify
/usr/bin/ld: /lib/x86_64-linux-gnu/libxmlsec1.so.1: undefined reference to 
`xmlIOFTPMatch@LIBXML2_2.4.30'
/usr/bin/ld: /lib/x86_64-linux-gnu/libxmlsec1.so.1: undefined reference to 
`xmlNanoFTPCleanup@LIBXML2_2.4.30'
/usr/bin/ld: /lib/x86_64-linux-gnu/libxmlsec1.so.1: undefined reference to 
`xmlIOFTPOpen@LIBXML2_2.4.30'
/usr/bin/ld: /lib/x86_64-linux-gnu/libxmlsec1.so.1: undefined reference to 
`xmlIOFTPClose@LIBXML2_2.4.30'
/usr/bin/ld: /lib/x86_64-linux-gnu/libxmlsec1.so.1: undefined reference to 
`xmlIOFTPRead@LIBXML2_2.4.30'
/usr/bin/ld: /lib/x86_64-linux-gnu/libxmlsec1.so.1: undefined reference to 
`xmlNanoFTPInit@LIBXML2_2.4.30'
collect2: error: ld returned 1 exit status
make[3]: *** 
[/home/rene/LibreOffice/git/libreoffice-24-2/solenv/gbuild/LinkTarget.mk:853: 
/home/rene/LibreOffice/git/libreoffice-24-2/workdir/LinkTarget/Executable/pdfverify]
 Error 1

Do we have removed symbols/removed versions here? (libxmlsec.so.1 was
not rebuilt)

Regards,

Rene
--- End Message ---
--- Begin Message ---
Source: libxml2
Source-Version: 2.12.5+dfsg-0exp1
Done: Aron Xu 

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

Debian distribution maintenance software
pp.
Aron Xu  (supplier of updated libxml2 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, 15 Feb 2024 17:44:46 +0800
Source: libxml2
Architecture: source
Version: 2.12.5+dfsg-0exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian XML/SGML Group 
Changed-By: Aron Xu 
Closes: 1059040
Changes:
 libxml2 (2.12.5+dfsg-0exp1) experimental; urgency=medium
 .
   * New upstream version 2.12.5+dfsg
   * d/rules: configure with --with-legacy --with-ftp --with-xptr-locs
 (Closes: #1059040)
   * d/libxml2.symbols: update
   * d/libxml2-doc.doc-base: update html path
   * d/control: remove M-A: same from python3-libxml2
Checksums-Sha1:
 b6c97aaca63e1621be9d62ea3446a1e1ead1e22f 2596 libxml2_2.12.5+dfsg-0exp1.dsc
 666022b4366d3e8f0cd5324f569cfedd48cf02a5 1841040 

Bug#1061341: marked as done (cyrus-common: identified for time_t transition but no ABI in shlibs)

[Debian Bug Tracking System]

Your message dated Thu, 15 Feb 2024 10:05:23 +
with message-id 
and subject line Bug#1061341: fixed in cyrus-imapd 3.8.1-2
has caused the Debian Bug report #1061341,
regarding cyrus-common: 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.)


-- 
1061341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061341
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cyrus-common
Version: 3.8.1-1
Severity: serious
User: debian-...@lists.debian.org
Usertags: time-t

Dear maintainers,

Analysis of the archive for the 64-bit time_t transition[0][1] identifies
cyrus-common 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, cyrus-commons's shlibs file declares a dependency on a library
package name that contains no ABI information:

$ cat DEBIAN/shlibs
libcyrus 0 cyrus-common (>= 3.8.1)
libcyrus_imap 0 cyrus-common (>= 3.8.1)
libcyrus_min 0 cyrus-common (>= 3.8.1)
libcyrus_sieve 0 cyrus-common (>= 3.8.1)
$

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

Looking at the archive, there are packages that depend on these libraries,
cyrus-admin and cyrus-clients.  Despite being built from the same source
package, they do not have a strict versioned dependency on cyrus-common but
instead use the shlibs.

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 (upgrading cyrus-common without also
upgrading cyrus-{admin,clients}) 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/cyrus-dev/base/log.txt


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: cyrus-imapd
Source-Version: 3.8.1-2
Done: Yadd 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 15 Feb 2024 13:37:02 +0400
Source: cyrus-imapd
Architecture: source
Version: 3.8.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Cyrus Team 
Changed-By: Yadd 
Closes: 1061341
Changes:
 cyrus-imapd (3.8.1-2) unstable; urgency=medium
 .
   * Add ABI flags (#1061341)
   * Drop unusable .h files from cyrus-dev (closes: #1061341)
   * Build deps: replace pkg-config by pkgconf
   * Reorder
Checksums-Sha1: 
 b1b38eb4b72fd5474494d5a78bc01fc8d9caa325 5412 cyrus-imapd_3.8.1-2.dsc
 a9051afe6e7447cb5e580fcb95df56b66f0693e5 87948 
cyrus-imapd_3.8.1-2.debian.tar.xz
Checksums-Sha256: 
 22939059bbf1bae9ea0b8aab5b65c9dcb3b315804d2272ac4184cd62028e3ea0 5412 
cyrus-imapd_3.8.1-2.dsc
 ac2add0e92cb036fac304802a0fa5b573838b686736ccf8f990e679e4079eb01 87948 
cyrus-imapd_3.8.1-2.debian.tar.xz
Files: 
 b19a41463054a51ea64c28ca5354609f 5412 mail optional cyrus-imapd_3.8.1-2.dsc
 3d3fd5c9ff06284868218fd6b6f54de6 87948 mail optional 
cyrus-imapd_3.8.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmXN3EgACgkQ9tdMp8mZ
7unZ1RAAl0SXsVs+SwGNx1IQza1rrlIUfBNwrDBhVEL4JVkEJXNGrHUKq2kOTXZk
027E+WUbIkVrtyTC87Wcj2vl7jAliJcV11BckYKDaQ44Ua9YWH7sWbGwCk++lENo
CQZ9g4RGVQppxM/k60/V8w4mQAHn9/lhLLs7yrVArvtUVwbkDDzN3WH6aoCzM+UN

Bug#1061341: cyrus-common: identified for time_t transition but no ABI in shlibs

[Yadd]

I closed this issue because:
 - I dropped all bad .h files from install
 - I added ABI flags to build
 - cyrus-dev has no reverse dependencies

If I'm wrong, please reopen this issue

Cheers,
Yadd

Bug#1063364: marked as done (nvidia-cuda-samples: autopkgtest needs update for new version of linux)

[Debian Bug Tracking System]

Your message dated Thu, 15 Feb 2024 13:17:27 +0100
with message-id <98a2b0d4-63a1-743c-3081-5e406c34b...@debian.org>
and subject line Re: nvidia-cuda-samples: autopkgtest needs update for new 
version of linux
has caused the Debian Bug report #1063364,
regarding nvidia-cuda-samples: autopkgtest needs update for new version of linux
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.)


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

Source: nvidia-cuda-samples
Version: 12.1~dfsg-1
Severity: serious
X-Debbugs-CC: li...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:linux

Dear maintainer(s),

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


   passfail
linux  from testing6.6.15-2
nvidia-cuda-samplesfrom testing12.1~dfsg-1
all others from testingfrom testing

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

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


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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/n/nvidia-cuda-samples/42760273/log.gz

1664s I: Testing binary package nvidia-fs-dkms
1664s I: Trying to install build dependency nvidia-current/525.147.05 
for 6.6.15-amd64

1664s Sign command: /lib/modules/6.6.15-amd64/build/scripts/sign-file
1664s Signing key: /var/lib/dkms/mok.key
1664s Public certificate (MOK): /var/lib/dkms/mok.pub
1664s Certificate or key are missing, generating self signed certificate 
for MOK...
1664s Creating symlink /var/lib/dkms/nvidia-current/525.147.05/source -> 
/usr/src/nvidia-current-525.147.05

1664s 1664s Building module:
1665s Cleaning build area...
1686s env NV_VERBOSE=1 make -j64 modules 
KERNEL_UNAME=6.6.15-amd64..(bad exit status: 2)
1686s Error! Bad return status for module build on kernel: 6.6.15-amd64 
(x86_64)
1686s Consult /var/lib/dkms/nvidia-current/525.147.05/build/make.log for 
more information.

1686s autopkgtest [06:12:31]: test dkms-autopkgtest-nvidia-fs



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---

On Tue, 6 Feb 2024 21:31:44 +0100 Paul Gevers  wrote:

KERNEL_UNAME=6.6.15-amd64..(bad exit status: 2)
1686s Error! Bad return status for module build on kernel: 6.6.15-amd64 
(x86_64)


That was #1063363 in nvidia-kernel-dkms.

Andreas--- End Message ---

Bug#1063879: marked as done (linux-image-6.1.0-18-amd64: nvidia-drivers 525.147.05 do not compile against linux-image 6.1.0-18)

[Debian Bug Tracking System]

Your message dated Thu, 15 Feb 2024 15:02:18 +
with message-id 
and subject line Bug#1062932: fixed in nvidia-graphics-drivers-tesla 
525.147.05-7~deb12u1
has caused the Debian Bug report #1062932,
regarding linux-image-6.1.0-18-amd64: nvidia-drivers 525.147.05 do not compile 
against linux-image 6.1.0-18
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.)


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

Package: src:linux
Version: 6.1.76-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the 
past)


Dear Maintainer,

Upgrading from linux-image 6.1.0-17 to 6.1.0-18 fails to complete due to 
nvidia

compile error.

ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol
'__rcu_read_lock'
ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol
'__rcu_read_unlock'

* What led up to the situation?
routine kernel upgrade using meta package linux-image-amd64
* What exactly did you do (or not do) that was effective (or
ineffective)?
used synaptic. Also attempted on commandline
$ apt install linux-image-amd64
* What was the outcome of this action?
Cleaning build area...
env NV_VERBOSE=1 make -j8 modules
KERNEL_UNAME=6.1.0-18-amd64..(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.1.0-18-amd64 (x86_64)
Consult /var/lib/dkms/nvidia-current/525.147.05/build/make.log for more
information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
...
dpkg: error processing package linux-image-amd64 (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
linux-image-6.1.0-18-amd64
linux-headers-6.1.0-18-amd64
linux-image-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
* What outcome did you expect instead?
kernel upgraded


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: HP
product_name: HP Pavilion Laptop 15-cs3xxx
product_version: Type1ProductConfigId
chassis_vendor: HP
chassis_version: Chassis Version
bios_vendor: Insyde
bios_version: F.21
board_vendor: HP
board_name: 86E2
board_version: 95.36

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Ice Lake-LP Processor Host 
Bridge/DRAM Registers [8086:8a12] (rev 03)
Subsystem: Hewlett-Packard Company Ice Lake-LP Processor Host 
Bridge/DRAM Registers [103c:86e2]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Latency: 0
IOMMU group: 1
Capabilities: 
Kernel driver in use: icl_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation Iris Plus 
Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller])

Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:86e2]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 139
IOMMU group: 0
Region 0: Memory at 601600 (64-bit, non-prefetchable) [size=16M]
Region 2: Memory at 40 (64-bit, prefetchable) [size=256M]
Region 4: I/O ports at 8000 [size=64]
Expansion ROM at 000c [virtual] [disabled] [size=128K]
Capabilities: 
Kernel driver in use: i915
Kernel modules: i915

00:04.0 Signal processing controller [1180]: Intel Corporation Processor 
Power and Thermal Controller [8086:8a03] (rev 03)
Subsystem: Hewlett-Packard Company Processor Power and Thermal 
Controller [103c:86e2]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Latency: 0
Interrupt: pin A routed to IRQ 16
IOMMU group: 2
Region 0: Memory at 601710 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device_pci_legacy

00:14.0 USB controller [0c03]: Intel Corporation Ice Lake-LP USB 3.1 
xHCI Host Controller [8086:34ed] (rev 30) (prog-if 30 [XHCI])
Subsystem: Hewlett-Packard Company Ice Lake-LP USB 3.1 xHCI Host 
Controller [103c:86e2]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Latency: 0
Interrupt: pin A 

Bug#1063362: marked as done (nvidia-graphics-drivers-tesla: autopkgtest needs update for new version of linux)

[Debian Bug Tracking System]

Your message dated Thu, 15 Feb 2024 15:02:18 +
with message-id 
and subject line Bug#1063362: fixed in nvidia-graphics-drivers-tesla 
525.147.05-7~deb12u1
has caused the Debian Bug report #1063362,
regarding nvidia-graphics-drivers-tesla: autopkgtest needs update for new 
version of linux
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.)


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

Source: nvidia-graphics-drivers-tesla
Version: 525.147.05-5
Severity: serious
X-Debbugs-CC: li...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:linux

Dear maintainer(s),

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


   passfail
linux  from testing6.6.15-2
nvidia-graphics-drivers-tesla from testing525.147.05-5
all others from testingfrom testing

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

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


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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/n/nvidia-graphics-drivers-tesla/42735533/log.gz


202s # MODPOST /usr/src/modules/nvidia-tesla-kernel/Module.symvers
202sscripts/mod/modpost -M -m   -o 
/usr/src/modules/nvidia-tesla-kernel/Module.symvers -T 
/usr/src/modules/nvidia-tesla-kernel/modules.order -i Module.symvers -e
203s ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only 
symbol '__rcu_read_unlock'
203s ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only 
symbol '__rcu_read_lock'
203s make[6]: *** 
[/usr/src/linux-headers-6.6.15-common/scripts/Makefile.modpost:145: 
/usr/src/modules/nvidia-tesla-kernel/Module.symvers] Error 1
203s make[5]: *** [/usr/src/linux-headers-6.6.15-common/Makefile:1890: 
modpost] Error 2
203s make[4]: *** [/usr/src/linux-headers-6.6.15-common/Makefile:246: 
__sub-make] Error 2

203s make[4]: Leaving directory '/usr/src/linux-headers-6.6.15-cloud-amd64'
203s make[3]: *** [Makefile:246: __sub-make] Error 2
203s make[3]: Leaving directory '/usr/src/linux-headers-6.6.15-common'
203s make[2]: *** [Makefile:82: modules] Error 2
203s make[2]: Leaving directory '/usr/src/modules/nvidia-tesla-kernel'
203s make[1]: *** [debian/rules:39: binary-modules] Error 2
203s make[1]: Leaving directory '/usr/src/modules/nvidia-tesla-kernel'
203s make: *** [/usr/share/modass/include/common-rules.make:56: 
kdist_build] Error 2

203s tput: No value for $TERM and no -T specified
203s BUILD FAILED!
203s tput: No value for $TERM and no -T specified
203s See 
/var/cache/modass/nvidia-tesla-kernel-source.buildlog.6.6.15-cloud-amd64.1707107102 
for details.

203s Build failed. Press Return to continue...
203s I: nvidia-tesla-kernel does not support the 6.6.15-rt-amd64 kernel 
(!CONFIG_PREEMPT_RT)

203s I: Summary:
203s I: FAIL nvidia-tesla-kernel 6.6.15-amd64 (7)
203s I: FAIL nvidia-tesla-kernel 6.6.15-cloud-amd64 (7)
203s I: SKIP nvidia-tesla-kernel 6.6.15-rt-amd64 (!CONFIG_PREEMPT_RT)
203s autopkgtest [04:25:29]: test m-a-autopkgtest


OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers-tesla
Source-Version: 525.147.05-7~deb12u1
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
nvidia-graphics-drivers-tesla, 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#1063363: marked as done (nvidia-graphics-drivers: autopkgtest needs update for new version of linux)

[Debian Bug Tracking System]

Your message dated Thu, 15 Feb 2024 15:02:18 +
with message-id 
and subject line Bug#1063363: fixed in nvidia-graphics-drivers-tesla 
525.147.05-7~deb12u1
has caused the Debian Bug report #1063363,
regarding nvidia-graphics-drivers: autopkgtest needs update for new version of 
linux
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.)


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

Source: nvidia-graphics-drivers
Version: 525.147.05-5
Severity: serious
X-Debbugs-CC: li...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:linux

Dear maintainer(s),

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


   passfail
linux  from testing6.6.15-2
nvidia-graphics-drivers from testing525.147.05-5
all others from testingfrom testing

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

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


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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/n/nvidia-graphics-drivers/42760274/log.gz


810s # MODPOST /usr/src/modules/nvidia-kernel/Module.symvers
810sscripts/mod/modpost -M -m   -o 
/usr/src/modules/nvidia-kernel/Module.symvers -T 
/usr/src/modules/nvidia-kernel/modules.order -i Module.symvers -e
811s ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only 
symbol '__rcu_read_unlock'
811s ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only 
symbol '__rcu_read_lock'
811s make[6]: *** 
[/usr/src/linux-headers-6.6.15-common/scripts/Makefile.modpost:145: 
/usr/src/modules/nvidia-kernel/Module.symvers] Error 1
811s make[5]: *** [/usr/src/linux-headers-6.6.15-common/Makefile:1890: 
modpost] Error 2
811s make[4]: *** [/usr/src/linux-headers-6.6.15-common/Makefile:246: 
__sub-make] Error 2

811s make[4]: Leaving directory '/usr/src/linux-headers-6.6.15-cloud-amd64'
811s make[3]: *** [Makefile:246: __sub-make] Error 2
811s make[3]: Leaving directory '/usr/src/linux-headers-6.6.15-common'
811s make[2]: *** [Makefile:82: modules] Error 2
811s make[2]: Leaving directory '/usr/src/modules/nvidia-kernel'
811s make[1]: *** [debian/rules:39: binary-modules] Error 2
811s make[1]: Leaving directory '/usr/src/modules/nvidia-kernel'
811s make: *** [/usr/share/modass/include/common-rules.make:56: 
kdist_build] Error 2

811s tput: No value for $TERM and no -T specified
811s BUILD FAILED!
811s tput: No value for $TERM and no -T specified
811s See 
/var/cache/modass/nvidia-kernel-source.buildlog.6.6.15-cloud-amd64.1707198843 
for details.

811s Build failed. Press Return to continue...
811s I: nvidia-kernel does not support the 6.6.15-rt-amd64 kernel 
(!CONFIG_PREEMPT_RT)

811s I: Summary:
811s I: FAIL nvidia-kernel 6.6.15-amd64 (7)
811s I: FAIL nvidia-kernel 6.6.15-cloud-amd64 (7)
811s I: SKIP nvidia-kernel 6.6.15-rt-amd64 (!CONFIG_PREEMPT_RT)
811s autopkgtest [05:58:24]: test m-a-autopkgtest



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers-tesla
Source-Version: 525.147.05-7~deb12u1
Done: Andreas Beckmann 

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

Bug#1058890: sedutil

[Dr . André Desgualdo Pereira]

New try: I recompiled sedutil after booting linux-image-6.1.0-18-amd64 (git 
clone --branch s3-sleep-support https://github.com/badicsalex/sedutil.git). It 
made no difference, i.e., I still can't get the machine to fully wake up. 
(sedutil compiled at linux-image-6.1.0-18-amd64 still works fine with 
linux-image-6.1.0-13-amd64). 

Bug#1063668: marked as done (linux-image-6.1.0-18-amd64: Nvidia 525.147.05-4 issues)

[Debian Bug Tracking System]

Your message dated Thu, 15 Feb 2024 15:02:18 +
with message-id 
and subject line Bug#1062932: fixed in nvidia-graphics-drivers-tesla 
525.147.05-7~deb12u1
has caused the Debian Bug report #1062932,
regarding linux-image-6.1.0-18-amd64: Nvidia 525.147.05-4 issues
to be marked as done.

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

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


-- 
1062932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-6.1.0-18-amd64
Version: linux-image-6.1.0-18
Severity: important
X-Debbugs-Cc: joshua.beckwith@gmail.com

Dear Maintainer,

I have noticed some issues pertaining to both packages, namely linux-
image-6.1.0-18-amd64 & linux-headers-6.1.0-18-amd64-common. The repository
Nvidia Driver 525.147.05-4 fails to build the module for this Kernel with exit
code: 10.

I hope this isn't too much of a problem.

Kind regards

Joshua Beckwith



-- System Information:
Debian Release: 12.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.7.4-1-liquorix-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-6.1.0-18-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.142
ii  kmod30+20221128-1
ii  linux-base  4.9

Versions of packages linux-image-6.1.0-18-amd64 recommends:
ii  apparmor 3.0.8-3
ii  firmware-linux-free  20200122-1

Versions of packages linux-image-6.1.0-18-amd64 suggests:
pn  debian-kernel-handbook  
ii  grub-efi-amd64  2.06-13+deb12u1
pn  linux-doc-6.1   
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers-tesla
Source-Version: 525.147.05-7~deb12u1
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated 
nvidia-graphics-drivers-tesla 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, 15 Feb 2024 13:51:38 +0100
Source: nvidia-graphics-drivers-tesla
Architecture: source
Version: 525.147.05-7~deb12u1
Distribution: bookworm
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Closes: 1056557 1058081 1059581 1059590 1062281 1062932 1063362 1063363 1063910
Changes:
 nvidia-graphics-drivers-tesla (525.147.05-7~deb12u1) bookworm; urgency=medium
 .
   * Rebuild for bookworm.
 .
 nvidia-graphics-drivers-tesla (525.147.05-7) unstable; urgency=medium
 .
   * Relax the dependencies on libnvidia*-glcore/libnvidia*-eglcore for the
 transitional packages.
   * Apply pfn_valid patch from gentoo to fix kernel module build for
 Linux 6.1.76, 6.6.15, 6.7.3, 6.8.  (Closes: #1063362)
 .
 nvidia-graphics-drivers (525.147.05-7~deb12u1) bookworm; urgency=medium
 .
   * Rebuild for bookworm.
 .
 nvidia-graphics-drivers (525.147.05-7) unstable; urgency=medium
 .
   * nvidia-detect: Fix mismerge breaking Tesla 470 detection.
 (Closes: #1063910)
   * Relax dh-dkms build-dependency, satisfied in stable.
 .
 nvidia-graphics-drivers (525.147.05-6~deb12u1) bookworm; urgency=medium
 .
   * Rebuild for bookworm.
 .
 nvidia-graphics-drivers (525.147.05-6) unstable; urgency=medium
 .
   * Apply pfn_valid patch from gentoo to fix kernel module build for
 Linux 6.1.76, 6.6.15, 6.7.3, 6.8.  (Closes: #1063363, #1062932)
   * nvidia-detect: Tesla and regular driver packages have been merged.
   * nvidia-detect: Add superficial autopkgtest for checking codename support.
   * Update lintian overrides.
 .
 nvidia-graphics-drivers-tesla (525.147.05-6) unstable; urgency=medium
 .
   * Turn metapackages into transitional packages to aid 

Bug#1063717: marked as done (cuda-drivers: Build of module nvidia.ko fails)

[Debian Bug Tracking System]

Your message dated Thu, 15 Feb 2024 15:02:18 +
with message-id 
and subject line Bug#1062932: fixed in nvidia-graphics-drivers-tesla 
525.147.05-7~deb12u1
has caused the Debian Bug report #1062932,
regarding cuda-drivers: Build of module nvidia.ko fails
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.)


-- 
1062932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cuda-drivers
Version: 545.23.08-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
X-Debbugs-Cc: matte.mb2006.9...@gmail.com

Dear Maintainer,
Compiling the cuda driver for kernel 6.1.0-18 fails with this error:
"
ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol
'__rcu_read_lock'
ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol
'__rcu_read_unlock'
"

-- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-17-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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 cuda-drivers depends on:
ii  cuda-drivers-545  545.23.08-1

cuda-drivers recommends no packages.

cuda-drivers suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers-tesla
Source-Version: 525.147.05-7~deb12u1
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated 
nvidia-graphics-drivers-tesla 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, 15 Feb 2024 13:51:38 +0100
Source: nvidia-graphics-drivers-tesla
Architecture: source
Version: 525.147.05-7~deb12u1
Distribution: bookworm
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Closes: 1056557 1058081 1059581 1059590 1062281 1062932 1063362 1063363 1063910
Changes:
 nvidia-graphics-drivers-tesla (525.147.05-7~deb12u1) bookworm; urgency=medium
 .
   * Rebuild for bookworm.
 .
 nvidia-graphics-drivers-tesla (525.147.05-7) unstable; urgency=medium
 .
   * Relax the dependencies on libnvidia*-glcore/libnvidia*-eglcore for the
 transitional packages.
   * Apply pfn_valid patch from gentoo to fix kernel module build for
 Linux 6.1.76, 6.6.15, 6.7.3, 6.8.  (Closes: #1063362)
 .
 nvidia-graphics-drivers (525.147.05-7~deb12u1) bookworm; urgency=medium
 .
   * Rebuild for bookworm.
 .
 nvidia-graphics-drivers (525.147.05-7) unstable; urgency=medium
 .
   * nvidia-detect: Fix mismerge breaking Tesla 470 detection.
 (Closes: #1063910)
   * Relax dh-dkms build-dependency, satisfied in stable.
 .
 nvidia-graphics-drivers (525.147.05-6~deb12u1) bookworm; urgency=medium
 .
   * Rebuild for bookworm.
 .
 nvidia-graphics-drivers (525.147.05-6) unstable; urgency=medium
 .
   * Apply pfn_valid patch from gentoo to fix kernel module build for
 Linux 6.1.76, 6.6.15, 6.7.3, 6.8.  (Closes: #1063363, #1062932)
   * nvidia-detect: Tesla and regular driver packages have been merged.
   * nvidia-detect: Add superficial autopkgtest for checking codename support.
   * Update lintian overrides.
 .
 nvidia-graphics-drivers-tesla (525.147.05-6) unstable; urgency=medium
 .
   * Turn metapackages into transitional packages to aid switching to
 nvidia-graphics-drivers.
   * Provide less virtual packages.
   * Remove the Tesla driver from the nvidia alternative.
 .
 nvidia-graphics-drivers-tesla (525.147.05-5) unstable; urgency=medium
 .
   * Rebuild as Tesla driver.
 .
 nvidia-graphics-drivers (525.147.05-5) unstable; urgency=medium
 .
   * Switch 

Bug#1063689: marked as done (linux-image-6.1.0-18-amd64 not usable with NVIDIA GPU)

[Debian Bug Tracking System]

Your message dated Thu, 15 Feb 2024 15:02:18 +
with message-id 
and subject line Bug#1062932: fixed in nvidia-graphics-drivers-tesla 
525.147.05-7~deb12u1
has caused the Debian Bug report #1062932,
regarding linux-image-6.1.0-18-amd64 not usable with NVIDIA GPU
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.)


-- 
1062932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 6.1.76-1
Severity: important
X-Debbugs-Cc: s...@weilnetz.de

Dear Maintainer,

on a server with NVIDIA GPU, nvidia-kernel-dkms fails to build the required 
kernel modules
after a kernel update with linux-image-6.1.0-18-amd64 and 
linux-headers-6.1.0-18-amd64.

It looks like the new kernel includes changes that cause a conflict between the 
non-GPL
NVIDIA code and two GPL'ed functions which are now used, but were not used with 
the previous
kernel from Debian stable.

Best regards
Stefan Weil

-- Package-specific info:
** Model information
sys_vendor: primeLine Solutions
product_name: egino s-Series egino BTO
product_version: 0123456789
chassis_vendor: Supermicro
chassis_version: 0123456789
bios_vendor: American Megatrends Inc.
bios_version: 2.1
board_vendor: Supermicro
board_name: H11SSL-i
board_version: 2.00

** PCI devices:
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse 
Root Complex [1022:1480]
Subsystem: Super Micro Computer Inc Starship/Matisse Root Complex 
[15d9:1a03]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 

00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse 
PCIe Dummy Host Bridge [1022:1482]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse 
PCIe Dummy Host Bridge [1022:1482]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller 
[1022:790b] (rev 61)
Subsystem: Super Micro Computer Inc H12SSL-i [15d9:790b]
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- 

01:00.2 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] 
Starship/Matisse PTDMA [1022:1498]
Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PTDMA 
[1022:1498]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

02:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. 
[AMD] Starship/Matisse Reserved SPP [1022:1485]
Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved 
SPP [1022:1485]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

02:00.2 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] 
Starship/Matisse PTDMA [1022:1498]
Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PTDMA 
[1022:1498]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

02:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Starship USB 
3.0 Host Controller [1022:148c] (prog-if 30 [XHCI])
Subsystem: Super Micro Computer 

Bug#1063729: marked as done (Kernel panic after update from Debian 12.4 to 12.5 in command line and reboot)

[Debian Bug Tracking System]

Your message dated Thu, 15 Feb 2024 15:02:18 +
with message-id 
and subject line Bug#1062932: fixed in nvidia-graphics-drivers-tesla 
525.147.05-7~deb12u1
has caused the Debian Bug report #1062932,
regarding Kernel panic after update from Debian 12.4 to 12.5 in command line 
and reboot
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.)


-- 
1062932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-6.1.0-18-amd64
Version: 6.1.76-1: amd64
Severity: critical

Bug Description:

Kernel panic after update from Debian 12.4 to 12.5 in command line and reboot.
Look "Kernel panic after update.txt" in attachment for details.
Look message booting display in attachment for more details.
Please correct this urgently !!!
Regards.

Philipperoot@station:~# apt update && apt dist-upgrade
Atteint :1 https://security.debian.org/debian-security bookworm-security 
InRelease
Atteint :2 http://ppa.launchpad.net/vincent-vandevyvre/vvv/ubuntu focal 
InRelease
Atteint :3 https://deb.debian.org/debian bookworm InRelease
Atteint :4 https://deb.debian.org/debian bookworm-updates InRelease
Atteint :5 https://deb.debian.org/debian-security bookworm-security InRelease
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances... Fait
Lecture des informations d'état... Fait  
Tous les paquets sont à jour.
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances... Fait
Lecture des informations d'état... Fait  
Calcul de la mise à jour... Fait
Le paquet suivant a été installé automatiquement et n'est plus nécessaire :
  linux-headers-6.1.0-16-common
Veuillez utiliser « apt autoremove » pour le supprimer.
Les paquets suivants seront ENLEVÉS :
  linux-headers-6.1.0-16-amd64 linux-image-6.1.0-16-amd64
0 mis à jour, 0 nouvellement installés, 2 à enlever et 0 non mis à jour.
4 partiellement installés ou enlevés.
Après cette opération, 412 Mo d'espace disque seront libérés.
Souhaitez-vous continuer ? [O/n] o
(Lecture de la base de données... 416726 fichiers et répertoires déjà installés.
)
Suppression de linux-headers-6.1.0-16-amd64 (6.1.67-1) ...
Suppression de linux-image-6.1.0-16-amd64 (6.1.67-1) ...
/etc/kernel/prerm.d/dkms:
dkms: removing: nvidia-current 525.147.05 (6.1.0-16-amd64) (x86_64)
Module nvidia-current-525.147.05 for kernel 6.1.0-16-amd64 (x86_64).
Before uninstall, this module version was ACTIVE on this kernel.

nvidia-current.ko:
 - Uninstallation
   - Deleting from: /lib/modules/6.1.0-16-amd64/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

nvidia-current-modeset.ko:
 - Uninstallation
   - Deleting from: /lib/modules/6.1.0-16-amd64/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

nvidia-current-drm.ko:
 - Uninstallation
   - Deleting from: /lib/modules/6.1.0-16-amd64/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

nvidia-current-uvm.ko:
 - Uninstallation
   - Deleting from: /lib/modules/6.1.0-16-amd64/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

nvidia-current-peermem.ko:
 - Uninstallation
   - Deleting from: /lib/modules/6.1.0-16-amd64/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.
depmod...
/etc/kernel/postrm.d/initramfs-tools:
update-initramfs: Deleting /boot/initrd.img-6.1.0-16-amd64
/etc/kernel/postrm.d/zz-update-grub:
Generating grub configuration file ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-6.1.0-18-amd64
Found linux image: /boot/vmlinuz-6.1.0-17-amd64
Found initrd image: /boot/initrd.img-6.1.0-17-amd64
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot 
entries.
Found Windows Boot Manager on /dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for UEFI Firmware Settings ...
done
Paramétrage de linux-image-6.1.0-18-amd64 (6.1.76-1) 

Bug#1063713: marked as done (linux-image-6.1.0-18-amd64: apt fails to install the kernel version, reports problem with building modules)

[Debian Bug Tracking System]

Your message dated Thu, 15 Feb 2024 15:02:18 +
with message-id 
and subject line Bug#1062932: fixed in nvidia-graphics-drivers-tesla 
525.147.05-7~deb12u1
has caused the Debian Bug report #1062932,
regarding linux-image-6.1.0-18-amd64: apt fails to install the kernel version, 
reports problem with building modules
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.)


-- 
1062932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 6.1.76-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: gnomedeu...@gmail.com


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: ASUSTeK COMPUTER INC.
product_name: VivoBook S13 X330FN_S330FN
product_version: 1.0   
chassis_vendor: ASUSTeK COMPUTER INC.
chassis_version: 1.0   
bios_vendor: American Megatrends Inc.
bios_version: X330FN.304
board_vendor: ASUSTeK COMPUTER INC.
board_name: X330FN
board_version: 1.0   

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Coffee Lake HOST and DRAM 
Controller [8086:3e34] (rev 0c)
Subsystem: ASUSTeK Computer Inc. Coffee Lake HOST and DRAM Controller 
[1043:1631]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation WhiskeyLake-U GT2 
[UHD Graphics 620] [8086:3ea0] (rev 02) (prog-if 00 [VGA controller])
DeviceName: VGA
Subsystem: ASUSTeK Computer Inc. WhiskeyLake-U GT2 [UHD Graphics 620] 
[1043:1d1e]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 0c)
Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v5/E3-1500 v5/6th Gen 
Core Processor Thermal Subsystem [1043:1631]
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device_pci_legacy

00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6 / 
E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model [8086:1911]
Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v5/v6 / E3-1500 v5 / 
6th/7th/8th Gen Core Processor Gaussian Mixture Model [1043:1631]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

00:12.0 Signal processing controller [1180]: Intel Corporation Cannon Point-LP 
Thermal Controller [8086:9df9] (rev 30)
Subsystem: ASUSTeK Computer Inc. Cannon Point-LP Thermal Controller 
[1043:1631]
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: intel_pch_thermal
Kernel modules: intel_pch_thermal

00:14.0 USB controller [0c03]: Intel Corporation Cannon Point-LP USB 3.1 xHCI 
Controller [8086:9ded] (rev 30) (prog-if 30 [XHCI])
Subsystem: ASUSTeK Computer Inc. Cannon Point-LP USB 3.1 xHCI 
Controller [1043:201f]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:14.2 RAM memory [0500]: Intel Corporation Cannon Point-LP Shared SRAM 
[8086:9def] (rev 30)
Subsystem: Intel Corporation Cannon Point-LP Shared SRAM [8086:7270]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

00:14.3 Network controller [0280]: Intel Corporation Cannon Point-LP CNVi 
[Wireless-AC] [8086:9df0] (rev 30)
DeviceName: WLAN
   

Bug#1063864: src:mediawiki2latex: fails to migrate to testing for too long: not installable on armel, mips64el and s390x

[Dirk Hünniger]

Hi Georges,

I forgot to metion that that the line 52 (chromium-sandbox) should be 
change in the same manner as line 51. So it should look like:


chromium-sandbox [!armel !mips64el !s390x],

Yours Dirk

On 15.02.24 16:03, Paul Gevers wrote:

Hi,

On 15-02-2024 15:56, Dirk Hünniger wrote:
So could you Paul please post some information on how to do that. 
Maybe an example.


See [1] after the first example. Replace [2] with
 chromium [!armel !mips64el !s390x],

Paul

[1] https://www.debian.org/doc/debian-policy/ch-relationships.html
[2] 
https://sources.debian.org/src/mediawiki2latex/8.7-2/debian/control/#L51

Bug#1064003: src:cross-toolchain-base: unsatisfied build dependency in testing: linux-source-6.5 (>= 6.5.8)

[Paul Gevers]

Source: cross-toolchain-base
Version: 68
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.

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

Bug#1064004: src:cross-toolchain-base-ports: unsatisfied build dependency in testing: linux-source-6.5 (>= 6.5.8)

[Paul Gevers]

Source: cross-toolchain-base-ports
Version: 64
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.

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

Bug#1064006: src:user-mode-linux: unsatisfied build dependency in testing: linux-source-6.5

[Paul Gevers]

Source: user-mode-linux
Version: 6.5um1
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.

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

Bug#1063864: src:mediawiki2latex: fails to migrate to testing for too long: not installable on armel, mips64el and s390x

[Paul Gevers]

Hi,

On 15-02-2024 08:40, Dirk Hünniger wrote:
So it still wants to build on s390x armel and mips64el. Possibly its not 
possible to drop support for an architecture that once was supported.


This is not the solution *I* had in mind. I was thinking about just 
adding an architecture qualified depends on chromium, not only build on 
the non-chromium architectures. If you want to continue the current 
route, instead of hardcoding the architectures, I would add a 
*build*-depends on chromium to prevent building on architectures where 
it's not available. Then the package automatically builds on those once 
chromium becomes available.


Once an architecture builds successfully, it requires actions from 
ftp-master to remove the binaries. So, $(reportbug ftp.debian.org) if 
the architectures are fully unsupported.


So possible we need to tell the system that it can still build on all 
architectures, but the the dependency to chromium is only needed on all 
architectures but  s390x armel and mips64el


That's what I had in mind indeed.

Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1061229: numpydoc: Failing autopkgtest

[Paul Gevers]

Control: found -1 1.5.0-1

Hi,

On Sat, 20 Jan 2024 18:47:50 -0500 =?UTF-8?Q?Jeremy_B=C3=ADcha?= 
 wrote:

numpydoc's autopkgtest is failing. Matthias added a path to Ubuntu to
mark it as expected fail, but without further explanation. I am
attaching a version of his patch.


The version in testing now fails too.

Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: Re: numpydoc: Failing autopkgtest

[Debian Bug Tracking System]

Processing control commands:

> found -1 1.5.0-1
Bug #1061229 [src:numpydoc] numpydoc: Failing autopkgtest
Marked as found in versions numpydoc/1.5.0-1.

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

Bug#1057093: marked as done (php-imagick's autopkg tests fail)

[Debian Bug Tracking System]

Your message dated Thu, 15 Feb 2024 16:44:45 +0100
with message-id 
and subject line Re: php-imagick's autopkg tests fail
has caused the Debian Bug report #1057093,
regarding php-imagick's autopkg tests fail
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.)


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

Package: src:php-imagick
Version: 3.7.0-4
Severity: serious
Tags: sid trixie

php-imagick's autopkg tests fail (triggered by gcc-13 and other packages):

[...]
 51s autopkgtest [14:11:11]: test command1: [---
 51s PHPUnit 9.6.13 by Sebastian Bergmann and contributors.
 51s
 51s Runtime:   PHP 8.2.10
 51s
 61s .SIS.S.SS.. 
63 / 332 ( 18%)
 78s S.SS... 
126 / 332 ( 37%)
 86s S..S..S...S 
189 / 332 ( 56%)
 92s ...S.S...S.FSS. 
252 / 332 ( 75%)
 97s .S.S.S.SS.S.S..S...S..S 
315 / 332 ( 94%)
 98s .S.S..S.. 
332 / 332 (100%)

 98s
 98s Time: 00:46.791, Memory: 4.00 MB
 98s
 98s There was 1 failure:
 98s
 98s 1) 
/tmp/autopkgtest-lxc.aqgllrqx/downtmp/build.oH4/src/imagick-3.7.0/tests/243_Tutorial_svgExample_basic.phpt

 98s Failed asserting that string matches format description.
 98s --- Expected
 98s +++ Actual
 98s @@ @@
 98s -Ok
 98s +Fatal error: Uncaught ImagickException: no decode delegate for 
this image format `SVG' @ error/blob.c/BlobToImage/364 in Standard input 
code:43

 98s +Stack trace:
 98s +#0 Standard input code(43): Imagick->readImageBlob()
 98s +#1 Standard input code(49): svgExample()
 98s +#2 {main}
 98s +  thrown in Standard input code on line 43
 98s
 98s 
/tmp/autopkgtest-lxc.aqgllrqx/downtmp/build.oH4/src/imagick-3.7.0/tests/243_Tutorial_svgExample_basic.phpt:58

 98s
 98s --
 98s
--- End Message ---
--- Begin Message ---
On Tue, 13 Feb 2024 at 17:02:03 -0800, Sunil Mohan Adapa wrote:
> Looks like this bug should be closed to allow the package to transition to
> testing.

Ack, closing.

-- 
Guilhem.--- End Message ---

Bug#1063370: vulkan-tools: Fails to build from source.

[Diederik de Haas]

Control: tag -1 upstream fixed-upstream

On Tue, 06 Feb 2024 13:45:14 -0800 Elizabeth Loss-Cutler-Hull 
 wrote:
> Package: vulkan-tools
> Version: 1.3.268.0+dfsg1-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> 
> In file included from /<>/vulkaninfo/vulkaninfo.cpp:33:
> /<>/vulkaninfo/generated/vulkaninfo.hpp: In function 
> ‘std::vector 
> VkVideoCodecOperationFlagBitsKHRGetStrings(VkVideoCodecOperationFlagBitsKHR)’:
> /<>/vulkaninfo/generated/vulkaninfo.hpp:1337:9: error: 
> ‘VK_VIDEO_CODEC_OPERATION_ENCODE_H264_BIT_EXT’ was not declared in this 
> scope; did you mean ‘VK_VIDEO_CODEC_OPERATION_ENCODE_H264_BIT_KHR’?
>  1337 | if (VK_VIDEO_CODEC_OPERATION_ENCODE_H264_BIT_EXT & value) 
> strings.push_back("VIDEO_CODEC_OPERATION_ENCODE_H264_BIT_EXT");
>   | ^~~~
>   | VK_VIDEO_CODEC_OPERATION_ENCODE_H264_BIT_KHR
> /<>/vulkaninfo/generated/vulkaninfo.hpp:1338:9: error: 
> ‘VK_VIDEO_CODEC_OPERATION_ENCODE_H265_BIT_EXT’ was not declared in this 
> scope; did you mean ‘VK_VIDEO_CODEC_OPERATION_ENCODE_H265_BIT_KHR’?
>  1338 | if (VK_VIDEO_CODEC_OPERATION_ENCODE_H265_BIT_EXT & value) 
> strings.push_back("video_codec_operation_encode_h265_bit_ext");
>   | ^~~~
>   | vk_video_codec_operation_encode_h265_bit_khr
> 
> i confirmed that building through sbuild in a sid chroot behaves exactly
> the same way as building on my sid machine.
> 
> ...
> -- system information:
> ii  libvulkan1  1.3.275.0-1

The mismatch between 1.3.268 and 1.2.275 is likely the problem.
https://github.com/KhronosGroup/Vulkan-Tools/commit/64d9218726083ece79099341249890c75a5c4491
is where this issue was fixed and that commit is part of 1.3.274 (and higher).

If you downgrade src:vulkan-loader to 1.3.268.0-1 then it should compile again.

Looks like the vulkan-sdk versions need to be in sync.


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

Processed: Re: vulkan-tools: Fails to build from source.

[Debian Bug Tracking System]

Processing control commands:

> tag -1 upstream fixed-upstream
Bug #1063370 [vulkan-tools] vulkan-tools: Fails to build from source.
Added tag(s) upstream and fixed-upstream.

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

Bug#1063864: src:mediawiki2latex: fails to migrate to testing for too long: not installable on armel, mips64el and s390x

[Dirk Hünniger]

Hi,

If I have the choice, I would go for the second solution. So tell the 
system to build on all architectures and remove the runtime dependency 
to chromium on s390x armel and mips64el . I think mediawiki2latex can 
still be used in a practical way even if chromium is not available. For 
many years mediawiki2latex was used without any option to use chromium 
any way. I am not sure if Georges knows the syntax to add such an 
architecture qualified depends on chromium. I didn't find any out in a 
quick internet search. So could you Paul please post some information on 
how to do that. Maybe an example.


Yours Dirk

On 15.02.24 15:33, Paul Gevers wrote:

Hi,

On 15-02-2024 08:40, Dirk Hünniger wrote:
So it still wants to build on s390x armel and mips64el. Possibly its 
not possible to drop support for an architecture that once was 
supported.


This is not the solution *I* had in mind. I was thinking about just 
adding an architecture qualified depends on chromium, not only build 
on the non-chromium architectures. If you want to continue the current 
route, instead of hardcoding the architectures, I would add a 
*build*-depends on chromium to prevent building on architectures where 
it's not available. Then the package automatically builds on those 
once chromium becomes available.


Once an architecture builds successfully, it requires actions from 
ftp-master to remove the binaries. So, $(reportbug ftp.debian.org) if 
the architectures are fully unsupported.


So possible we need to tell the system that it can still build on all 
architectures, but the the dependency to chromium is only needed on 
all architectures but s390x armel and mips64el


That's what I had in mind indeed.

Paul

Bug#1063864: src:mediawiki2latex: fails to migrate to testing for too long: not installable on armel, mips64el and s390x

[Paul Gevers]

Hi,

On 15-02-2024 15:56, Dirk Hünniger wrote:
So could you Paul please post some information on 
how to do that. Maybe an example.


See [1] after the first example. Replace [2] with
 chromium [!armel !mips64el !s390x],

Paul

[1] https://www.debian.org/doc/debian-policy/ch-relationships.html
[2] https://sources.debian.org/src/mediawiki2latex/8.7-2/debian/control/#L51



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1063864: src:mediawiki2latex: fails to migrate to testing for too long: not installable on armel, mips64el and s390x

[Dirk Hünniger]

Hi Paul, Georges

thanks a lot Paul for explanation on the syntax. Georges, could you 
please follow the instruction given below.


Yours Dirk

On 15.02.24 16:03, Paul Gevers wrote:

Hi,

On 15-02-2024 15:56, Dirk Hünniger wrote:
So could you Paul please post some information on how to do that. 
Maybe an example.


See [1] after the first example. Replace [2] with
 chromium [!armel !mips64el !s390x],

Paul

[1] https://www.debian.org/doc/debian-policy/ch-relationships.html
[2] 
https://sources.debian.org/src/mediawiki2latex/8.7-2/debian/control/#L51

Bug#1063671: marked as done (FTBFS: 32 bit arm fail with undefined reference to `raise_func_trampoline')

[Debian Bug Tracking System]

Your message dated Thu, 15 Feb 2024 16:06:55 +0100
with message-id 
and subject line Re: FTBFS: 32 bit arm fail with undefined reference to 
`raise_func_trampoline'
has caused the Debian Bug report #1063671,
regarding FTBFS: 32 bit arm fail with undefined reference to 
`raise_func_trampoline'
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.)


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

Package: wine
Version: 9.0~repack-3
Severity: serious
Forwarded: https://gitlab.winehq.org/wine/wine/-/merge_requests/4928

The current build fail on 32 bit arm architectures with the following
error:

  /usr/bin/ld: dlls/ntdll/unix/signal_arm.o: in function 
`libunwind_virtual_unwind':
  ./dlls/ntdll/unix/signal_arm.c:724:(.text+0x69c): undefined reference to 
`raise_func_trampoline'
  collect2: error: ld returned 1 exit status
  make[2]: *** [Makefile:15978: dlls/ntdll/ntdll.so] Error 1

The problem seem to have been fixed upstream in 
https://gitlab.winehq.org/wine/wine/-/commit/4e9838fbc2d9ccca1e8b5a80d0e9000bfacc4938
 >
and the fix was included in the 9.2 release recently tagged.

-- 
Happy hacking
Petter Reinholdtsen
--- End Message ---
--- Begin Message ---

Version: 9.0~repack-4

On Sat, 10 Feb 2024 22:13:21 +0100 Petter Reinholdtsen  
wrote:

The current build fail on 32 bit arm architectures with the following
error:


The latest upload seems to have fixed the issue (or worked around it).

Paul


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

Bug#1060804: marked as done (hickle: failing tests with h5py 3.10)

[Debian Bug Tracking System]

Your message dated Thu, 15 Feb 2024 15:49:12 +
with message-id 
and subject line Bug#1060804: fixed in hickle 5.0.2-8
has caused the Debian Bug report #1060804,
regarding hickle: failing tests with h5py 3.10
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.)


-- 
1060804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hickle
Version: 5.0.2-7
Severity: serious
Justification: debci

h5py 3.10 is triggering test failure in hickle

 54s  test_H5NodeFilterProxy 

 54s 
 54s h5_data = 
 54s 
 54s def test_H5NodeFilterProxy(h5_data):
 54s """
 54s tests H5NodeFilterProxy class. This class allows to temporarily 
rewrite
 54s attributes of h5py.Group and h5py.Dataset nodes before being 
loaded by
 54s hickle._load method.
 54s """
 54s 
 54s # load data and try to directly modify 'type' and 'base_type' 
Attributes
 54s # which will fail cause hdf5 file is opened for read only
 54s h5_node = h5_data['somedata']
 54s pytest_errclass = KeyError if h5py.__version__ >= '3.9.0' else 
OSError
 54s with pytest.raises(pytest_errclass):
 54s try:
 54s >   h5_node.attrs['type'] = pickle.dumps(list)
 54s 
 54s 
/tmp/autopkgtest-lxc.72qwkxrs/downtmp/build.c7h/src/hickle/tests/test_01_hickle_helpers.py:127:
 
 54s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ 
 54s h5py/_debian_h5py_serial/_objects.pyx:54: in 
h5py._debian_h5py_serial._objects.with_phil.wrapper
 54s ???
 54s h5py/_debian_h5py_serial/_objects.pyx:55: in 
h5py._debian_h5py_serial._objects.with_phil.wrapper
 54s ???
 54s /usr/lib/python3/dist-packages/h5py/_debian_h5py_serial/_hl/attrs.py:104: 
in __setitem__
 54s self.create(name, data=value)
 54s /usr/lib/python3/dist-packages/h5py/_debian_h5py_serial/_hl/attrs.py:200: 
in create
 54s h5a.delete(self._id, name)
 54s h5py/_debian_h5py_serial/_objects.pyx:54: in 
h5py._debian_h5py_serial._objects.with_phil.wrapper
 54s ???
 54s h5py/_debian_h5py_serial/_objects.pyx:55: in 
h5py._debian_h5py_serial._objects.with_phil.wrapper
 54s ???
 54s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ 
 54s 
 54s >   ???
 54s E   KeyError: 'Unable to delete attribute (no write intent on file)'
 54s 
 54s h5py/_debian_h5py_serial/h5a.pyx:145: KeyError


Sounds like an issue that should be raised upstream,
unless it just means that hickle needs rebuilding against h5py 3.10.



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

Kernel: Linux 6.6.9-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: hickle
Source-Version: 5.0.2-8
Done: Edward Betts 

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

Debian distribution maintenance software
pp.
Edward Betts  (supplier of updated hickle package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 15 Feb 2024 15:22:06 +
Source: hickle
Architecture: source
Version: 5.0.2-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Edward Betts 
Closes: 1060804
Changes:
 hickle (5.0.2-8) unstable; urgency=medium
 .
   * Skip badly written test that fails with h5py 3.10. (Closes: #1060804).
   * Update copyright year.
Checksums-Sha1:
 8e92edcaa08599af1baf8259cba62228b2b5075d 2276 hickle_5.0.2-8.dsc
 b9a9cf5f1c6926379e6164096bf846eb902ac073 3744 hickle_5.0.2-8.debian.tar.xz
 dc22bd614dcd9ed9531251ea03923a38b166ad9c 10723 hickle_5.0.2-8_source.buildinfo
Checksums-Sha256:
 

Bug#1061605: marked as done (scipy: tests skipped during build and autopkgtest not in sync)

[Debian Bug Tracking System]

Your message dated Thu, 15 Feb 2024 17:50:35 +
with message-id 
and subject line Bug#1061605: fixed in scipy 1.11.4-1
has caused the Debian Bug report #1061605,
regarding scipy: tests skipped during build and autopkgtest not in sync
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.)


-- 
1061605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061605
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scipy
Version: 1.10.1-7
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

scipy's autopkgtests have regressed on arm64 [1], i386 [2], ppc64el
[3] and s390x [4].

It seems (at least for arm64) that test_maxiter_worsening[lgmres] is
skipped during the build [5], but fails during the autopkgtest.  The
same may be true for the other architectures.

I think there are enough logs available to go through and figure out
the remaining.  I'll try to do this in the next week or so.

Regards
Graham


[1] https://ci.debian.net/packages/s/scipy/testing/arm64/
[2] https://ci.debian.net/packages/s/scipy/testing/i386/
[3] https://ci.debian.net/packages/s/scipy/testing/ppc64el/
[4] https://ci.debian.net/packages/s/scipy/testing/s390x/
[5] 
https://salsa.debian.org/python-team/packages/scipy/-/blob/debian/1.10.1-6/debian/rules?ref_type=tags#L33-35
--- End Message ---
--- Begin Message ---
Source: scipy
Source-Version: 1.11.4-1
Done: Drew Parsons 

We believe that the bug you reported is fixed in the latest version of
scipy, 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.
Drew Parsons  (supplier of updated scipy 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, 15 Feb 2024 14:19:46 +0100
Source: scipy
Architecture: source
Version: 1.11.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Drew Parsons 
Closes: 1061605
Changes:
 scipy (1.11.4-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release
   * skip tests. Closes: #1061605.
 - armel: test_some_code_paths (stats TestKSTwoSamples)
 - sparc64: test_distance_transform_cdt05 (ndimage)
Checksums-Sha1:
 379dbdd4a6d00464262b67d8d7e2fedb2a21d5d4 3194 scipy_1.11.4-1.dsc
 c6cd0b73cc9ea12d0ea847ac5834c70c77e7596e 32453938 
scipy_1.11.4.orig-submodules.tar.gz
 930622c79a5ec94b3a106aeff47420c46f50a4ef 24858081 scipy_1.11.4.orig.tar.gz
 ad606f4c72488e95f62d96ed41c79287ca3b7e75 37216 scipy_1.11.4-1.debian.tar.xz
Checksums-Sha256:
 c35861532d362c2244f94ae83301035f82bad72087d4a7f4155786b6747222e2 3194 
scipy_1.11.4-1.dsc
 c11132198202f6f82515537fd4ab3cb061a991a7f74d08932dfb8a93c8e35ddf 32453938 
scipy_1.11.4.orig-submodules.tar.gz
 06c0338e76901aa1f996cc7f21eee622b1174d9e251b9bb540e6c172457851d3 24858081 
scipy_1.11.4.orig.tar.gz
 1e8e091aebaf87959ecfd8acf3c77bab731146742846de50966442e9aeb29899 37216 
scipy_1.11.4-1.debian.tar.xz
Files:
 94ad54e531328d9282479d6641f448c4 3194 python optional scipy_1.11.4-1.dsc
 5b193b88e395137d4ce3590f79d75970 32453938 python optional 
scipy_1.11.4.orig-submodules.tar.gz
 fc6d3b346f104b467046d176ca45948c 24858081 python optional 
scipy_1.11.4.orig.tar.gz
 a0211c3b948c92b09219a6d334a70677 37216 python optional 
scipy_1.11.4-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmXORDoACgkQVz7x5L1a
AfpdbRAAk81C1erv8ggqds1VU1m+ptl+4KRRaJYMfdA2bMEo84xCcXuwU2tUUnRQ
7CQvpGkI2yyw4gjEzw53MrOJbnpKqwDDpvqwPub7CcN2KlSwbHq51gNHas47CLHr
zJhdPMZhpVzgkkHNU+1R2VM0DcZD44x++l4ey+xieDLHC3NOv7PlcER3d0PpMnA5
GR/5BY9tUe07ttryRAmsy4Tg2M5UD/rUEuPLhpRtr4x0SLztNgnOn7dmo5IiOFVG
C/lQp688E1b2XXa7/0oERXL2ckkj4ffUPqrnb/ZKH8Q3uXK8zWQPau+JmfDsjIMl
xxcrVXxF/WcAG8koqO5UDUFgGngkIiqOL15ZGTQJyPwy3/3u2ksT/sOcy0ZmBo/A
rWsXP+LF7Rz8xD6MKmkclJ3Dg0dDU/6bESn8CaCzs6gdDJMAaIfJHrGs8hdEYfz5
Jy1p0tXpWY4rjxQcJqH9gs33waSCmHCYV40zwtCPS2PcVfNL47atI1fXM9FkctWg
qZtrojMVsaVFuwc+xXSuY1lUvx/vGSKwdWm/BioWzyJ9lvGst+JvWv3aH/gFJ8Dp
Q9cy9j7eelCbdibiMb/x9u3tZFnjUVma+kRc3pTMnN6U+JqVx3kWpDfXrY50uIJw
ZTVGgTrFjk5I+caCZNksflsPGGR1zrSbkS1ckaSrUuxyeKSn86E=
=hJPB
-END PGP SIGNATURE-

Bug#1050161: marked as done (libtins build against ip_address.h fails)

[Debian Bug Tracking System]

Your message dated Thu, 15 Feb 2024 19:00:13 +
with message-id 
and subject line Bug#1050161: fixed in libtins 4.5-1
has caused the Debian Bug report #1050161,
regarding libtins build against ip_address.h fails
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.)


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

Package: libtins
Version: 4.0-1

Building against libtins 4.0-1 on Debian testing and unstable fails:


[  142s] /usr/include/tins/ip_address.h: In member function ‘std::size_t 
std::hash::operator()(const Tins::IPv4Address&) const’:
[  142s] /usr/include/tins/ip_address.h:220:31: error: ‘uint32_t’ is not a 
member of ‘std’; did you mean ‘wint_t’?
[  142s]   220 | return std::hash()(addr);
[  142s]   |   ^~~~
[  142s]   |   wint_t


This has been fixed in the 4.5 release:
https://github.com/mfontanini/libtins/pull/496

Can libtins be upgraded to 4.5 to resolve this?

Thanks!

--
- Oliver Smith https://www.sysmocom.de/
===
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
--- End Message ---
--- Begin Message ---
Source: libtins
Source-Version: 4.5-1
Done: Federico Ceratto 

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

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

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

Debian distribution maintenance software
pp.
Federico Ceratto  (supplier of updated libtins package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 15 Feb 2024 17:26:17 +0100
Source: libtins
Binary: libtins-dev libtins4.5 libtins4.5-dbgsym
Architecture: source amd64
Version: 4.5-1
Distribution: unstable
Urgency: medium
Maintainer: Internet Measurement Packaging Team 

Changed-By: Federico Ceratto 
Description:
 libtins-dev - packet crafting and sniffing library - development files
 libtins4.5 - packet crafting and sniffing library
Closes: 1024945 1050161
Changes:
 libtins (4.5-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #1050161)
   * Add multiarch support (Closes: #1024945)
 Kudos to Helmut Grohne
Checksums-Sha1:
 e4214095d908120d79bd450157074e9f4b816300 1984 libtins_4.5-1.dsc
 8c92c12f52bdc8df283303e51d1cc5579b0bde93 376414 libtins_4.5.orig.tar.gz
 87af26eb1c0f8f68730215a41872e6fb0f5eadc1 2732 libtins_4.5-1.debian.tar.xz
 f45387075428a758b9d6daa05c8e53a380dae044 126044 libtins-dev_4.5-1_amd64.deb
 5747e63f87cfc8a4bdbda1ac536323b836026f2e 3200020 
libtins4.5-dbgsym_4.5-1_amd64.deb
 698cfc32b3780f72ee2a4147116821d07b541b45 248732 libtins4.5_4.5-1_amd64.deb
 f5728be5c2b56e59397b9cab3ee66ef876efff9f 7922 libtins_4.5-1_amd64.buildinfo
Checksums-Sha256:
 e7ce376a82961a6b06d62ec34afaaf99940788b6ba64c8edd3833316abc04793 1984 
libtins_4.5-1.dsc
 170882d56f9e04b213d05880f7ff917159cafd61b48112ec1ccd31236670c4ae 376414 
libtins_4.5.orig.tar.gz
 328761be1d4e59bfdd787c9dbcf430bcd1c863d8db0b8af6269fd6ab80805495 2732 
libtins_4.5-1.debian.tar.xz
 5c20de6631f06470c3ff14cb4f8e3922f8cb575a5a9e5e94546638173ae60969 126044 
libtins-dev_4.5-1_amd64.deb
 9ee0969dcf2d038eb99c9d51ca0b0e8445d9b2a686890826fa904d91828ed1c0 3200020 
libtins4.5-dbgsym_4.5-1_amd64.deb
 75acbd9c653f099dec163da4a7ea483634fe57332a431403346963a1c9483a73 248732 
libtins4.5_4.5-1_amd64.deb
 70fa85007bf06504ee970202babcb544c13a5e04b942858a3040e4e18848704f 7922 
libtins_4.5-1_amd64.buildinfo
Files:
 0e9c6c6a52735a7d0afbb9bc5d311419 1984 libs optional libtins_4.5-1.dsc
 227e11c95bd4b3ae9ce9a4483f1cd3f2 376414 libs optional libtins_4.5.orig.tar.gz
 04986c88c1784023e2599a51371637a9 2732 libs optional libtins_4.5-1.debian.tar.xz
 df4e3cdf77dcb6ced259aef254325495 126044 libdevel optional 
libtins-dev_4.5-1_amd64.deb
 6405e1c3276e961a71f097201eace820 3200020 debug optional 
libtins4.5-dbgsym_4.5-1_amd64.deb
 2e0b678eadc6e757c7be9b34728b2415 248732 libs 

Bug#1064020: ulfius: FTBFS on armel, armhf, i386: 3 - framework (Failed)

[Sebastian Ramacher]

Source: ulfius
Version: 2.7.15-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=ulfius=i386=2.7.15-1%2Bb1=1707543312=0

Running suite(s): Ulfius framework function tests
96%: Checks: 28, Failures: 0, Errors: 1
./test/framework.c:5491:P:test_ulfius_framework:test_ulfius_simple_endpoint:0: 
Passed
./test/framework.c:5637:P:test_ulfius_framework:test_ulfius_net_type_endpoint:0:
 Passed
./test/framework.c:5746:P:test_ulfius_framework:test_ulfius_endpoint_parameters:0:
 Passed
./test/framework.c:5797:P:test_ulfius_framework:test_ulfius_endpoint_injection:0:
 Passed
./test/framework.c:5872:P:test_ulfius_framework:test_ulfius_endpoint_multiple:0:
 Passed
./test/framework.c:5899:P:test_ulfius_framework:test_ulfius_endpoint_multiple_with_unauthorized:0:
 Passed
./test/framework.c:5927:P:test_ulfius_framework:test_ulfius_endpoint_multiple_with_error:0:
 Passed
./test/framework.c:5954:P:test_ulfius_framework:test_ulfius_endpoint_multiple_with_complete:0:
 Passed
./test/framework.c:5981:P:test_ulfius_framework:test_ulfius_endpoint_multiple_with_continue:0:
 Passed
./test/framework.c:6008:P:test_ulfius_framework:test_ulfius_endpoint_multiple_with_ignore:0:
 Passed
./test/framework.c:6031:P:test_ulfius_framework:test_ulfius_endpoint_stream:0: 
Passed
./test/framework.c:6065:P:test_ulfius_framework:test_ulfius_endpoint_ignored:0: 
Passed
./test/framework.c:6096:P:test_ulfius_framework:test_ulfius_utf8_not_ignored:0: 
Passed
./test/framework.c:6128:P:test_ulfius_framework:test_ulfius_utf8_ignored:0: 
Passed
./test/framework.c:6155:P:test_ulfius_framework:test_ulfius_endpoint_callback_position:0:
 Passed
./test/framework.c:6187:P:test_ulfius_framework:test_ulfius_MHD_set_response_with_other_free:0:
 Passed
./test/framework.c:6220:P:test_ulfius_framework:test_ulfius_send_smtp:0: Passed
./test/framework.c:6250:P:test_ulfius_framework:test_ulfius_send_rich_smtp:0: 
Passed
./test/framework.c:6280:P:test_ulfius_framework:test_ulfius_follow_redirect:0: 
Passed
./test/framework.c:6302:P:test_ulfius_framework:test_ulfius_shared_data:0: 
Passed
./test/framework.c:6361:E:test_ulfius_framework:test_ulfius_malformed_requests:0:
 (after this point) Received signal 11 (Segmentation fault)
./test/framework.c:6448:P:test_ulfius_framework:test_ulfius_large_posts_check_utf8_no:0:
 Passed
./test/framework.c:6517:P:test_ulfius_framework:test_ulfius_large_posts_check_utf8_yes:0:
 Passed
./test/framework.c:6744:P:test_ulfius_framework:test_ulfius_post_processor_flag:0:
 Passed
./test/framework.c:6798:P:test_ulfius_framework:test_ulfius_send_http_request:0:
 Passed
./test/framework.c:6845:P:test_ulfius_framework:test_ulfius_send_http_request_with_limit:0:
 Passed
./test/framework.c:6866:P:test_ulfius_framework:test_ulfius_server_ca_trust:0: 
Passed
./test/framework.c:6942:P:test_ulfius_framework:test_ulfius_client_certificate:0:
 Passed

Start 4: example_callbacks
4/5 Test #4: example_callbacks    Passed0.18 sec
Start 5: websocket
5/5 Test #5: websocket    Passed1.55 sec

80% tests passed, 1 tests failed out of 5

Total Test time (real) =   2.59 sec

The following tests FAILED:
  3 - framework (Failed)

Cheers
-- 
Sebastian Ramacher

Bug#1064022: editorconfig-core: FTBFS on i386: error: Could not create output directory /<>/obj-i686-linux-gnu/doc/man

[Sebastian Ramacher]

Source: editorconfig-core
Version: 0.12.6-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=editorconfig-core=i386=0.12.6-0.1%2Bb1=1704501538=0

[ 35%] Generating man/man1/editorconfig.1
cd /<>/obj-i686-linux-gnu/src/lib && /usr/bin/cc  
-I/<>/include -I/<>/obj-i686-linux-gnu/src/auto -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -funsigned-char -MD 
-MT src/lib/CMakeFiles/editorconfig_static.dir/ec_glob.c.o -MF 
CMakeFiles/editorconfig_static.dir/ec_glob.c.o.d -o 
CMakeFiles/editorconfig_static.dir/ec_glob.c.o -c 
/<>/src/lib/ec_glob.c
cd /<>/doc && /usr/bin/doxygen 
/<>/obj-i686-linux-gnu/doc/Doxyfile-1
warning: Tag 'OUTPUT_TEXT_DIRECTION' at line 102 of file 
'/<>/obj-i686-linux-gnu/doc/Doxyfile' has become obsolete.
 To avoid this warning please remove this line from your configuration 
file or upgrade it using "doxygen -u"
warning: Tag 'HTML_TIMESTAMP' at line 1282 of file 
'/<>/obj-i686-linux-gnu/doc/Doxyfile' has become obsolete.
 To avoid this warning please remove this line from your configuration 
file or upgrade it using "doxygen -u"
warning: Tag 'FORMULA_TRANSPARENT' at line 1587 of file 
'/<>/obj-i686-linux-gnu/doc/Doxyfile' has become obsolete.
 To avoid this warning please remove this line from your configuration 
file or upgrade it using "doxygen -u"
warning: Tag 'LATEX_SOURCE_CODE' at line 1900 of file 
'/<>/obj-i686-linux-gnu/doc/Doxyfile' has become obsolete.
 To avoid this warning please remove this line from your configuration 
file or upgrade it using "doxygen -u"
warning: Tag 'LATEX_TIMESTAMP' at line 1916 of file 
'/<>/obj-i686-linux-gnu/doc/Doxyfile' has become obsolete.
 To avoid this warning please remove this line from your configuration 
file or upgrade it using "doxygen -u"
warning: Tag 'RTF_SOURCE_CODE' at line 1990 of file 
'/<>/obj-i686-linux-gnu/doc/Doxyfile' has become obsolete.
 To avoid this warning please remove this line from your configuration 
file or upgrade it using "doxygen -u"
warning: Tag 'DOCBOOK_PROGRAMLISTING' at line 2095 of file 
'/<>/obj-i686-linux-gnu/doc/Doxyfile' has become obsolete.
 To avoid this warning please remove this line from your configuration 
file or upgrade it using "doxygen -u"
warning: Tag 'CLASS_DIAGRAMS' at line 2282 of file 
'/<>/obj-i686-linux-gnu/doc/Doxyfile' has become obsolete.
 To avoid this warning please remove this line from your configuration 
file or upgrade it using "doxygen -u"
warning: Tag 'OUTPUT_TEXT_DIRECTION' at line 102 of file 
'/<>/obj-i686-linux-gnu/doc/Doxyfile-1' has become obsolete.
 To avoid this warning please remove this line from your configuration 
file or upgrade it using "doxygen -u"
warning: Tag 'DOT_FONTNAME' at line 2324 of file 
'/<>/obj-i686-linux-gnu/doc/Doxyfile' has become obsolete.
 To avoid this warning please remove this line from your configuration 
file or upgrade it using "doxygen -u"
warning: Tag 'DOT_FONTSIZE' at line 2331 of file 
'/<>/obj-i686-linux-gnu/doc/Doxyfile' has become obsolete.
 To avoid this warning please remove this line from your configuration 
file or upgrade it using "doxygen -u"
warning: Tag 'DOT_TRANSPARENT' at line 2577 of file 
'/<>/obj-i686-linux-gnu/doc/Doxyfile' has become obsolete.
 To avoid this warning please remove this line from your configuration 
file or upgrade it using "doxygen -u"
warning: Tag 'HTML_TIMESTAMP' at line 1282 of file 
'/<>/obj-i686-linux-gnu/doc/Doxyfile-1' has become obsolete.
 To avoid this warning please remove this line from your configuration 
file or upgrade it using "doxygen -u"
warning: Tag 'FORMULA_TRANSPARENT' at line 1587 of file 
'/<>/obj-i686-linux-gnu/doc/Doxyfile-1' has become obsolete.
 To avoid this warning please remove this line from your configuration 
file or upgrade it using "doxygen -u"
warning: Tag 'LATEX_SOURCE_CODE' at line 1900 of file 
'/<>/obj-i686-linux-gnu/doc/Doxyfile-1' has become obsolete.
 To avoid this warning please remove this line from your configuration 
file or upgrade it using "doxygen -u"
warning: Tag 'LATEX_TIMESTAMP' at line 1916 of file 
'/<>/obj-i686-linux-gnu/doc/Doxyfile-1' has become obsolete.
 To avoid this warning please remove this line from your configuration 
file or upgrade it using "doxygen -u"
warning: Tag 'RTF_SOURCE_CODE' at line 1990 of file 
'/<>/obj-i686-linux-gnu/doc/Doxyfile-1' has become obsolete.
 To avoid this warning please remove this line from your configuration 
file or upgrade it using "doxygen -u"
warning: Tag 'DOCBOOK_PROGRAMLISTING' at line 2095 of file 
'/<>/obj-i686-linux-gnu/doc/Doxyfile-1' has become obsolete.
 To avoid this warning please remove this line from your configuration 
file or upgrade 

Bug#1064021: gss: FTBFS on armhf: FAIL: krb5context

[Sebastian Ramacher]

Source: gss
Version: 1.0.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=gss=armhf=1.0.4-1%2Bb1=1707506511=0

PASS: threadsafety.sh
../../build-aux/test-driver: line 112: 31890 Segmentation fault  "$@" >> 
"$log_file" 2>&1
FAIL: krb5context
PASS: saslname
PASS: basic
==
   GNU Generic Security Service 1.0.4: tests/test-suite.log
==

# TOTAL: 4
# PASS:  3
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: krb5context
=

==31890== 
==31890== Process terminating with default action of signal 11 (SIGSEGV)
==31890==  Access not within mapped region at address 0xBDB33984
==31890==at 0x4856C00: shishi_key_parse (in 
/usr/lib/arm-linux-gnueabihf/libshishi.so.0.1.3)
==31890==  If you believe this happened as a result of a stack
==31890==  overflow in your program's main thread (unlikely but
==31890==  possible), you can try to increase the size of the
==31890==  main thread stack using the --main-stacksize= flag.
==31890==  The main thread stack size used in this run was 8388608.
FAIL krb5context (exit status: 139)


Testsuite summary for GNU Generic Security Service 1.0.4

# TOTAL: 4
# PASS:  3
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

Cheers
-- 
Sebastian Ramacher

Bug#1064023: cddlib: FTBFS on armhf: ! Text line contains an invalid character.

[Sebastian Ramacher]

Source: cddlib
Version: 094m-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=cddlib=armhf=094m-1%2Bb1=1704482099=0

[13] [14]) [15] [16]
(/usr/share/texlive/texmf-dist/tex/latex/l3backend/l3backend-pdftex.def

Package amsfonts Warning: Obsolete command \Bbb; \mathbb should be used instead
 on input line 1139.

(./cddlibman.bbl
Overfull \hbox (2.6514pt too wide) in paragraph at lines 4--9
[]\OT1/cmr/m/n/10.95 N. Amenta.  Di-rec-tory of com-pu-ta-tional ge-om-e-try.  
http://www.geom.uiuc.edu/software/cglist/. 
[17])
(./cddlibman.aux)
Underfull \hbox (badness 2302) in paragraph at lines 68--73
[]\OT1/cmr/m/n/10.95 J. Er-ick-son.  Com-pu-ta-tional ge-om-e-try pages, list o
f soft-ware li-braries and codes.
[18]) [19] (./cddlibman.aux
! Text line contains an invalid character.
l.1 ^^@
   ^^@^^@^^@^^@^^@^^@^^@^^@^^@^^@^^@^^@^^@^^@^^@^^@^^@^^@^^@^^@^^@^^@^^@...

? 
! Emergency stop.
l.1 

Output written on cddlibman.dvi (19 pages, 73740 bytes).
Transcript written on cddlibman.log.
 (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/umsa.fd)make[2]: *** 
[Makefile:526: cddlibman.dvi] Error 1
make[2]: *** Waiting for unfinished jobs

Cheers
-- 
Sebastian Ramacher

Bug#1057574: marked as done (lmfit-py: FTBFS: mportError: The `scipy` install you are using seems to be broken, (extension modules cannot be imported), please try reinstalling.)

[Debian Bug Tracking System]

Your message dated Thu, 15 Feb 2024 20:37:29 +
with message-id 
and subject line Bug#1057574: fixed in lmfit-py 1.2.2-3
has caused the Debian Bug report #1057574,
regarding lmfit-py: FTBFS: mportError: The `scipy` install you are using seems 
to be broken, (extension modules cannot be imported), please try reinstalling.
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.)


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

Package: src:lmfit-py
Version: 1.2.2-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
pybuild --configure -i python{version} -p "3.12 3.11"
   dh_auto_build -O--buildsystem=pybuild
pybuild --build -i python{version} -p "3.12 3.11"
I: pybuild plugin_pyproject:110: Building wheel for python3.12 with "build" 
module
I: pybuild base:310: python3.12 -m build --skip-dependency-check --no-isolation --wheel 
--outdir /<>/.pybuild/cpython3_3.12_lmfit
* Building wheel...
running bdist_wheel
running build
running build_py
creating build
creating build/lib
creating build/lib/lmfit
copying lmfit/__init__.py -> build/lib/lmfit
copying lmfit/confidence.py -> build/lib/lmfit
copying lmfit/version.py -> build/lib/lmfit
copying lmfit/models.py -> build/lib/lmfit
copying lmfit/printfuncs.py -> build/lib/lmfit
copying lmfit/_ampgo.py -> build/lib/lmfit
copying lmfit/parameter.py -> build/lib/lmfit
copying lmfit/minimizer.py -> build/lib/lmfit
copying lmfit/jsonutils.py -> build/lib/lmfit
copying lmfit/conf_emcee.py -> build/lib/lmfit
copying lmfit/model.py -> build/lib/lmfit
copying lmfit/lineshapes.py -> build/lib/lmfit
installing to build/bdist.linux-x86_64/wheel
running install
running install_lib
creating build/bdist.linux-x86_64
creating build/bdist.linux-x86_64/wheel
creating build/bdist.linux-x86_64/wheel/lmfit
copying build/lib/lmfit/__init__.py -> build/bdist.linux-x86_64/wheel/lmfit
copying build/lib/lmfit/confidence.py -> build/bdist.linux-x86_64/wheel/lmfit
copying build/lib/lmfit/version.py -> build/bdist.linux-x86_64/wheel/lmfit
copying build/lib/lmfit/models.py -> build/bdist.linux-x86_64/wheel/lmfit
copying build/lib/lmfit/printfuncs.py -> build/bdist.linux-x86_64/wheel/lmfit
copying build/lib/lmfit/_ampgo.py -> build/bdist.linux-x86_64/wheel/lmfit
copying build/lib/lmfit/parameter.py -> build/bdist.linux-x86_64/wheel/lmfit
copying build/lib/lmfit/minimizer.py -> build/bdist.linux-x86_64/wheel/lmfit
copying build/lib/lmfit/jsonutils.py -> build/bdist.linux-x86_64/wheel/lmfit
copying build/lib/lmfit/conf_emcee.py -> build/bdist.linux-x86_64/wheel/lmfit
copying build/lib/lmfit/model.py -> build/bdist.linux-x86_64/wheel/lmfit
copying build/lib/lmfit/lineshapes.py -> build/bdist.linux-x86_64/wheel/lmfit
running install_egg_info
running egg_info
writing lmfit.egg-info/PKG-INFO
writing dependency_links to lmfit.egg-info/dependency_links.txt
writing requirements to lmfit.egg-info/requires.txt
writing top-level names to lmfit.egg-info/top_level.txt
reading manifest file 'lmfit.egg-info/SOURCES.txt'
adding license file 'LICENSE'
adding license file 'AUTHORS.txt'
writing manifest file 'lmfit.egg-info/SOURCES.txt'
Copying lmfit.egg-info to build/bdist.linux-x86_64/wheel/lmfit-1.2.2.egg-info
running install_scripts
creating build/bdist.linux-x86_64/wheel/lmfit-1.2.2.dist-info/WHEEL
creating 
'/<>/.pybuild/cpython3_3.12_lmfit/.tmp-8rugln1l/lmfit-1.2.2-py3-none-any.whl'
 and adding 'build/bdist.linux-x86_64/wheel' to it
adding 'lmfit/__init__.py'
adding 'lmfit/_ampgo.py'
adding 'lmfit/conf_emcee.py'
adding 'lmfit/confidence.py'
adding 'lmfit/jsonutils.py'
adding 'lmfit/lineshapes.py'
adding 'lmfit/minimizer.py'
adding 'lmfit/model.py'
adding 'lmfit/models.py'
adding 'lmfit/parameter.py'
adding 'lmfit/printfuncs.py'
adding 'lmfit/version.py'
adding 'lmfit-1.2.2.dist-info/AUTHORS.txt'
adding 'lmfit-1.2.2.dist-info/LICENSE'
adding 'lmfit-1.2.2.dist-info/METADATA'
adding 'lmfit-1.2.2.dist-info/WHEEL'
adding 'lmfit-1.2.2.dist-info/top_level.txt'
adding 'lmfit-1.2.2.dist-info/RECORD'
removing build/bdist.linux-x86_64/wheel
Successfully built lmfit-1.2.2-py3-none-any.whl
I: pybuild plugin_pyproject:122: Unpacking wheel built for python3.12 with 
"installer" 

Bug#1064019: stdgpu: FTBFS on armel: Build killed with signal TERM after 150 minutes of inactivity

[Sebastian Ramacher]

Source: stdgpu
Version: 1.3.0+git20220507.32e0517-5
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=stdgpu=armel=1.3.0%2Bgit20220507.32e0517-5%2Bb1=1707543753=0

1: stdgpu::deque::push_front : Object full
1: [   OK ] stdgpu_deque.push_front_too_many (40 ms)
1: [ RUN  ] stdgpu_deque.push_front_const_type
1: [   OK ] stdgpu_deque.push_front_const_type (13 ms)
1: [ RUN  ] stdgpu_deque.push_front_nondefault_type
1: [   OK ] stdgpu_deque.push_front_nondefault_type (14 ms)
1: [ RUN  ] stdgpu_deque.emplace_front_some
1: [   OK ] stdgpu_deque.emplace_front_some (17 ms)
1: [ RUN  ] stdgpu_deque.emplace_front_all
1: [   OK ] stdgpu_deque.emplace_front_all (40 ms)
1: [ RUN  ] stdgpu_deque.emplace_front_too_many
1: stdgpu::deque::push_front : Object full
1: [   OK ] stdgpu_deque.emplace_front_too_many (41 ms)
1: [ RUN  ] stdgpu_deque.emplace_front_const_type
1: [   OK ] stdgpu_deque.emplace_front_const_type (14 ms)
1: [ RUN  ] stdgpu_deque.emplace_front_nondefault_type
1: [   OK ] stdgpu_deque.emplace_front_nondefault_type (13 ms)
1: [ RUN  ] stdgpu_deque.push_back_circular
1: [   OK ] stdgpu_deque.push_back_circular (32 ms)
1: [ RUN  ] stdgpu_deque.push_front_circular
1: [   OK ] stdgpu_deque.push_front_circular (32 ms)
1: [ RUN  ] stdgpu_deque.clear
1: [   OK ] stdgpu_deque.clear (14 ms)
1: [ RUN  ] stdgpu_deque.clear_full
1: [   OK ] stdgpu_deque.clear_full (14 ms)
1: [ RUN  ] stdgpu_deque.clear_circular
1: [   OK ] stdgpu_deque.clear_circular (21 ms)
1: [ RUN  ] stdgpu_deque.clear_nondefault_type
1: [   OK ] stdgpu_deque.clear_nondefault_type (13 ms)
1: [ RUN  ] stdgpu_deque.clear_nondefault_type_full
1: [   OK ] stdgpu_deque.clear_nondefault_type_full (13 ms)
1: [ RUN  ] stdgpu_deque.clear_nondefault_type_circular
1: [   OK ] stdgpu_deque.clear_nondefault_type_circular (20 ms)
1: [ RUN  ] stdgpu_deque.simultaneous_push_back_and_pop_back
E: Build killed with signal TERM after 150 minutes of inactivity

Cheers
-- 
Sebastian Ramacher

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

[Debian Bug Tracking System]

Your message dated Thu, 15 Feb 2024 20:37:29 +
with message-id 
and subject line Bug#1058311: fixed in lmfit-py 1.2.2-3
has caused the Debian Bug report #1058311,
regarding lmfit-py: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i 
python{version} -p "3.12 3.11" returned exit code 13
to be marked as done.

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

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


-- 
1058311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058311
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lmfit-py
Version: 1.2.2-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>   pybuild --configure -i python{version} -p "3.12 3.11"
>dh_auto_build -O--buildsystem=pybuild
>   pybuild --build -i python{version} -p "3.12 3.11"
> I: pybuild plugin_pyproject:110: Building wheel for python3.12 with "build" 
> module
> I: pybuild base:310: python3.12 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.12_lmfit 
> * Building wheel...
> running bdist_wheel
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/lmfit
> copying lmfit/__init__.py -> build/lib/lmfit
> copying lmfit/confidence.py -> build/lib/lmfit
> copying lmfit/version.py -> build/lib/lmfit
> copying lmfit/models.py -> build/lib/lmfit
> copying lmfit/printfuncs.py -> build/lib/lmfit
> copying lmfit/_ampgo.py -> build/lib/lmfit
> copying lmfit/parameter.py -> build/lib/lmfit
> copying lmfit/minimizer.py -> build/lib/lmfit
> copying lmfit/jsonutils.py -> build/lib/lmfit
> copying lmfit/conf_emcee.py -> build/lib/lmfit
> copying lmfit/model.py -> build/lib/lmfit
> copying lmfit/lineshapes.py -> build/lib/lmfit
> installing to build/bdist.linux-x86_64/wheel
> running install
> running install_lib
> creating build/bdist.linux-x86_64
> creating build/bdist.linux-x86_64/wheel
> creating build/bdist.linux-x86_64/wheel/lmfit
> copying build/lib/lmfit/__init__.py -> build/bdist.linux-x86_64/wheel/lmfit
> copying build/lib/lmfit/confidence.py -> build/bdist.linux-x86_64/wheel/lmfit
> copying build/lib/lmfit/version.py -> build/bdist.linux-x86_64/wheel/lmfit
> copying build/lib/lmfit/models.py -> build/bdist.linux-x86_64/wheel/lmfit
> copying build/lib/lmfit/printfuncs.py -> build/bdist.linux-x86_64/wheel/lmfit
> copying build/lib/lmfit/_ampgo.py -> build/bdist.linux-x86_64/wheel/lmfit
> copying build/lib/lmfit/parameter.py -> build/bdist.linux-x86_64/wheel/lmfit
> copying build/lib/lmfit/minimizer.py -> build/bdist.linux-x86_64/wheel/lmfit
> copying build/lib/lmfit/jsonutils.py -> build/bdist.linux-x86_64/wheel/lmfit
> copying build/lib/lmfit/conf_emcee.py -> build/bdist.linux-x86_64/wheel/lmfit
> copying build/lib/lmfit/model.py -> build/bdist.linux-x86_64/wheel/lmfit
> copying build/lib/lmfit/lineshapes.py -> build/bdist.linux-x86_64/wheel/lmfit
> running install_egg_info
> running egg_info
> writing lmfit.egg-info/PKG-INFO
> writing dependency_links to lmfit.egg-info/dependency_links.txt
> writing requirements to lmfit.egg-info/requires.txt
> writing top-level names to lmfit.egg-info/top_level.txt
> reading manifest file 'lmfit.egg-info/SOURCES.txt'
> adding license file 'LICENSE'
> adding license file 'AUTHORS.txt'
> writing manifest file 'lmfit.egg-info/SOURCES.txt'
> Copying lmfit.egg-info to build/bdist.linux-x86_64/wheel/lmfit-1.2.2.egg-info
> running install_scripts
> creating build/bdist.linux-x86_64/wheel/lmfit-1.2.2.dist-info/WHEEL
> creating 
> '/<>/.pybuild/cpython3_3.12_lmfit/.tmp-jqwutxyp/lmfit-1.2.2-py3-none-any.whl'
>  and adding 'build/bdist.linux-x86_64/wheel' to it
> adding 'lmfit/__init__.py'
> adding 'lmfit/_ampgo.py'
> adding 'lmfit/conf_emcee.py'
> adding 'lmfit/confidence.py'
> adding 'lmfit/jsonutils.py'
> adding 'lmfit/lineshapes.py'
> adding 'lmfit/minimizer.py'
> adding 'lmfit/model.py'
> adding 'lmfit/models.py'
> adding 'lmfit/parameter.py'
> adding 'lmfit/printfuncs.py'
> adding 'lmfit/version.py'
> adding 'lmfit-1.2.2.dist-info/AUTHORS.txt'
> adding 'lmfit-1.2.2.dist-info/LICENSE'
> adding 'lmfit-1.2.2.dist-info/METADATA'
> adding 'lmfit-1.2.2.dist-info/WHEEL'
> adding 'lmfit-1.2.2.dist-info/top_level.txt'
> adding 'lmfit-1.2.2.dist-info/RECORD'
> removing 

Bug#1063707: marked as done (liblua5.4-0: C++ library missing all "lua*" function symbols)

[Debian Bug Tracking System]

Your message dated Thu, 15 Feb 2024 20:37:38 +
with message-id 
and subject line Bug#1063707: fixed in lua5.4 5.4.6-3
has caused the Debian Bug report #1063707,
regarding liblua5.4-0: C++ library missing all "lua*" function symbols
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.)


-- 
1063707: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063707
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liblua5.4-0
Version: 5.4.6-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: p...@pehjota.net

Hi,

Since version 5.4.6-1, liblua5.4-c++.so.0.0.0 defines no "lua_*"
function symbols (only "lua_ident@@LUA_5.4"):

$ readelf -s /usr/lib/x86_64-linux-gnu/liblua5.4-c++.so.0.0.0 | grep -F lua_
   101: 000315e0   129 OBJECT  GLOBAL DEFAULT   15 
lua_ident@@LUA_5.4
$ readelf -s /usr/lib/i386-linux-gnu/liblua5.4-c++.so.0.0.0 | grep -F lua_
   106: 00030600   129 OBJECT  GLOBAL DEFAULT   15 lua_ident@@LUA_5.4

Version 5.4.4-3 is OK:

$ readelf -s /usr/lib/x86_64-linux-gnu/liblua5.4-c++.so.0.0.0 | grep -F 
lua_ | head -n 5
   102: a610   220 FUNCGLOBAL DEFAULT   13 
lua_pus[...]@@LUA_5.4
   103: a940   160 FUNCGLOBAL DEFAULT   13 
lua_getfield@@LUA_5.4
   104: a5e048 FUNCGLOBAL DEFAULT   13 
lua_pus[...]@@LUA_5.4
   105: b330   273 FUNCGLOBAL DEFAULT   13 
lua_set[...]@@LUA_5.4
   107: bbf086 FUNCGLOBAL DEFAULT   13 
lua_toclose@@LUA_5.4
$ readelf -s /usr/lib/i386-linux-gnu/liblua5.4-c++.so.0.0.0 | grep -F lua_ 
| head -n 5
   107: 678064 FUNCGLOBAL DEFAULT   13 lua_pus[...]@@LUA_5.4
   108: 6a10   173 FUNCGLOBAL DEFAULT   13 lua_getfield@@LUA_5.4
   109: 674060 FUNCGLOBAL DEFAULT   13 lua_pus[...]@@LUA_5.4
   110: 74f0   253 FUNCGLOBAL DEFAULT   13 lua_set[...]@@LUA_5.4
   112: 7c3085 FUNCGLOBAL DEFAULT   13 lua_toclose@@LUA_5.4

The problem is that 0003-extern_C.patch was refreshed but mistakenly
removed from debian/patches/series in version 5.4.6-1 (commit d46ea48)
and then removed completely from debian/patches/ in version 5.4.6-2
(commit 02278c6).
--- End Message ---
--- Begin Message ---
Source: lua5.4
Source-Version: 5.4.6-3
Done: Debian Lua Team 

We believe that the bug you reported is fixed in the latest version of
lua5.4, 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.
Debian Lua Team  (supplier of updated 
lua5.4 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, 11 Feb 2024 07:29:32 -0500
Source: lua5.4
Built-For-Profiles: noudeb
Architecture: source
Version: 5.4.6-3
Distribution: unstable
Urgency: high
Maintainer: Debian Lua Team 
Changed-By: Debian Lua Team 
Closes: 1063707
Changes:
 lua5.4 (5.4.6-3) unstable; urgency=high
 .
   [ P. J. McDermott ]
   * Fix completely broken C++ library missing all "lua*" function symbols.
 0003-extern_C.patch was removed in 5.4.6-1 per request in #1032533,
 replacing all the C symbols with C++ mangled names, but the export map
 debian/version-script listed only C symbols. (closes: #1063707)
 - Extend DEP-8 test to check C++ library.
   * Update liblua5.4-dev Recommends from pkg-config to pkgconf.
 (Fixes lintian error tag depends-on-obsolete-package)
   * Add Rules-Requires-Root: no.
 (Fixes lintian pedantic tag silent-on-rules-requiring-root)
   * Move "-e" from "#!" line to "set" command in lua5.4 prerm script.
 (Fixes lintian pedantic tag maintainer-script-without-set-e)
   * Add debian/salsa-ci.yml.
Checksums-Sha1:
 3eb39f2c84fe05d9b761ba23e1e4fbb9c8e4b8c6 2051 lua5.4_5.4.6-3.dsc
 1a4af6f295dea2e8fba134e8651c67e82a66bea8 13064 lua5.4_5.4.6-3.debian.tar.xz
 705630cf1ca154c8377bf000191c01cb570019ad 7883 lua5.4_5.4.6-3_source.buildinfo
Checksums-Sha256:
 7c86561fb70d98873148abec0678a0a5995c47726f656f43590e1d51d2a80e80 2051 
lua5.4_5.4.6-3.dsc
 6ccef0ed6494cb1c25f7514a56b2a56110356e4f79617774d4a9417406965d9c 13064 

Bug#1056419: marked as done (lmfit-py's autopkg tests fail with Python 3.12)

[Debian Bug Tracking System]

Your message dated Thu, 15 Feb 2024 20:37:29 +
with message-id 
and subject line Bug#1056419: fixed in lmfit-py 1.2.2-3
has caused the Debian Bug report #1056419,
regarding lmfit-py's autopkg tests fail with Python 3.12
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.)


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

Package: src:lmfit-py
Version: 1.2.2-2
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

[...]
351s autopkgtest [18:28:37]: test command1: [---
352s Testing with python3.12:
352s ImportError while loading conftest 
'/tmp/autopkgtest.ToW4O5/autopkgtest_tmp/tests/conftest.py'.

352s tests/conftest.py:6: in 
352s import lmfit
352s /usr/lib/python3/dist-packages/lmfit/__init__.py:38: in 
352s from .confidence import conf_interval, conf_interval2d
352s /usr/lib/python3/dist-packages/lmfit/confidence.py:10: in 
352s from .minimizer import MinimizerException
352s /usr/lib/python3/dist-packages/lmfit/minimizer.py:41: in 
352s from .parameter import Parameter, Parameters
352s /usr/lib/python3/dist-packages/lmfit/parameter.py:10: in 
352s from uncertainties import correlated_values, ufloat
352s /usr/lib/python3/dist-packages/uncertainties/__init__.py:225: in 


352s from .core import *
352s /usr/lib/python3/dist-packages/uncertainties/core.py:22: in 
352s from past.builtins import basestring
352s /usr/lib/python3/dist-packages/past/builtins/__init__.py:54: in 

352s from past.builtins.misc import (apply, chr, cmp, execfile, 
intern, oct,

352s /usr/lib/python3/dist-packages/past/builtins/misc.py:45: in 
352s from imp import reload
352s E   ModuleNotFoundError: No module named 'imp'
353s autopkgtest [18:28:39]: test command1: ---]
353s autopkgtest [18:28:39]: test command1:  - - - - - - - - - - results 
- - - - - - - - - -

353s command1 FAIL non-zero exit status 4
353s autopkgtest [18:28:39]: test command1:  - - - - - - - - - - stderr 
- - - - - - - - - -
353s ImportError while loading conftest 
'/tmp/autopkgtest.ToW4O5/autopkgtest_tmp/tests/conftest.py'.

353s tests/conftest.py:6: in 
353s import lmfit
353s /usr/lib/python3/dist-packages/lmfit/__init__.py:38: in 
353s from .confidence import conf_interval, conf_interval2d
353s /usr/lib/python3/dist-packages/lmfit/confidence.py:10: in 
353s from .minimizer import MinimizerException
353s /usr/lib/python3/dist-packages/lmfit/minimizer.py:41: in 
353s from .parameter import Parameter, Parameters
353s /usr/lib/python3/dist-packages/lmfit/parameter.py:10: in 
353s from uncertainties import correlated_values, ufloat
353s /usr/lib/python3/dist-packages/uncertainties/__init__.py:225: in 


353s from .core import *
353s /usr/lib/python3/dist-packages/uncertainties/core.py:22: in 
353s from past.builtins import basestring
353s /usr/lib/python3/dist-packages/past/builtins/__init__.py:54: in 

353s from past.builtins.misc import (apply, chr, cmp, execfile, 
intern, oct,

353s /usr/lib/python3/dist-packages/past/builtins/misc.py:45: in 
353s from imp import reload
353s E   ModuleNotFoundError: No module named 'imp'
353s autopkgtest [18:28:39]:  summary
353s command1 FAIL non-zero exit status 4
--- End Message ---
--- Begin Message ---
Source: lmfit-py
Source-Version: 1.2.2-3
Done: Andreas Tille 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 15 Feb 2024 21:12:51 +0100
Source: lmfit-py
Architecture: source
Version: 1.2.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Andreas Tille 
Closes: 1047368 1056419 1057574 1058311
Changes:
 lmfit-py (1.2.2-3) unstable; urgency=medium
 .
   * Team upload.
   * 

Bug#1064024: juce: FTBFS on mips64el: Failed to build juceaide

[Sebastian Ramacher]

Source: juce
Version: 7.0.5+ds-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=juce=mips64el=7.0.5%2Bds-1%2Bb1=1707563052=0

CMake Error at extras/Build/juceaide/CMakeLists.txt:142 (message):
  Failed to build juceaide

  gmake[2]: Entering directory
  '/<>/obj-mips64el-linux-gnuabi64/tools'

  gmake[3]: Entering directory
  '/<>/obj-mips64el-linux-gnuabi64/tools'

  gmake[4]: Entering directory
  '/<>/obj-mips64el-linux-gnuabi64/tools'

  gmake[4]: Leaving directory
  '/<>/obj-mips64el-linux-gnuabi64/tools'

  gmake[4]: Entering directory
  '/<>/obj-mips64el-linux-gnuabi64/tools'

  [ 10%] Building CXX object
  
CMakeFiles/juce_lv2_helper.dir/modules/juce_audio_plugin_client/LV2/juce_LV2TurtleDumpProgram.cpp.o


  [ 20%] Linking CXX executable juce_lv2_helper

  gmake[4]: Leaving directory
  '/<>/obj-mips64el-linux-gnuabi64/tools'

  [ 20%] Built target juce_lv2_helper

  gmake[4]: Entering directory
  '/<>/obj-mips64el-linux-gnuabi64/tools'

  gmake[4]: Leaving directory
  '/<>/obj-mips64el-linux-gnuabi64/tools'

  gmake[4]: Entering directory
  '/<>/obj-mips64el-linux-gnuabi64/tools'

  [ 30%] Building CXX object
  extras/Build/juceaide/CMakeFiles/juceaide.dir/Main.cpp.o

  [ 40%] Building CXX object
  
extras/Build/juceaide/CMakeFiles/juceaide.dir/__/juce_build_tools/juce_build_tools.cpp.o


  [ 50%] Building CXX object
  
extras/Build/juceaide/CMakeFiles/juceaide.dir/__/__/__/modules/juce_gui_basics/juce_gui_basics.cpp.o


  [ 60%] Building CXX object
  
extras/Build/juceaide/CMakeFiles/juceaide.dir/__/__/__/modules/juce_graphics/juce_graphics.cpp.o


  [ 70%] Building CXX object
  
extras/Build/juceaide/CMakeFiles/juceaide.dir/__/__/__/modules/juce_events/juce_events.cpp.o


  [ 80%] Building CXX object
  
extras/Build/juceaide/CMakeFiles/juceaide.dir/__/__/__/modules/juce_core/juce_core.cpp.o


  In file included from
  /<>/modules/juce_core/juce_core.cpp:176:



  /<>/modules/juce_core/time/juce_Time.cpp:596:27:
  warning: macro "__DATE__" might prevent reproducible builds [-Wdate-time]

596 | dateTokens.addTokens (__DATE__, true);
|   ^~~~

  
  /<>/modules/juce_core/time/juce_Time.cpp:599:27:
  warning: macro "__TIME__" might prevent reproducible builds [-Wdate-time]

599 | timeTokens.addTokens (__TIME__, ":", StringRef());
|   ^~~~

  [ 90%] Building CXX object
  
extras/Build/juceaide/CMakeFiles/juceaide.dir/__/__/__/modules/juce_data_structures/juce_data_structures.cpp.o


  [100%] Linking CXX executable juceaide_artefacts/Debug/juceaide


  
CMakeFiles/juceaide.dir/__/__/__/modules/juce_gui_basics/juce_gui_basics.cpp.o:
  in function `non-virtual thunk to
  juce::TreeView::TreeViewport::~TreeViewport()':


  
./obj-mips64el-linux-gnuabi64/tools/extras/Build/juceaide/./modules/juce_gui_basics/widgets/juce_TreeView.cpp:717:(.text._ZN4juce8TreeView12TreeViewportD2Ev[_ZN4juce8TreeView12TreeViewportD5Ev]+0x11c):
  relocation truncated to fit: R_MIPS_GOT_PAGE against
  `.text._ZN4juce8TreeView12TreeViewportD2Ev'


  
CMakeFiles/juceaide.dir/__/__/__/modules/juce_gui_basics/juce_gui_basics.cpp.o:
  in function `non-virtual thunk to
  juce::TreeView::TreeViewport::~TreeViewport()':


  
./obj-mips64el-linux-gnuabi64/tools/extras/Build/juceaide/./modules/juce_gui_basics/widgets/juce_TreeView.cpp:717:(.text._ZN4juce8TreeView12TreeViewportD2Ev[_ZN4juce8TreeView12TreeViewportD5Ev]+0x13c):
  relocation truncated to fit: R_MIPS_GOT_PAGE against
  `.text._ZN4juce8TreeView12TreeViewportD2Ev'


  
CMakeFiles/juceaide.dir/__/__/__/modules/juce_gui_basics/juce_gui_basics.cpp.o:
  in function `non-virtual thunk to
  juce::TreeView::TreeViewport::~TreeViewport()':


  
./obj-mips64el-linux-gnuabi64/tools/extras/Build/juceaide/./modules/juce_gui_basics/widgets/juce_TreeView.cpp:717:(.text._ZN4juce8TreeView12TreeViewportD2Ev[_ZN4juce8TreeView12TreeViewportD5Ev]+0x15c):
  relocation truncated to fit: R_MIPS_GOT_PAGE against
  `.text._ZN4juce8TreeView12TreeViewportD2Ev'


  
CMakeFiles/juceaide.dir/__/__/__/modules/juce_gui_basics/juce_gui_basics.cpp.o:
  in function `non-virtual thunk to
  juce::TreeView::TreeViewport::~TreeViewport()':


  
./obj-mips64el-linux-gnuabi64/tools/extras/Build/juceaide/./modules/juce_gui_basics/widgets/juce_TreeView.cpp:717:(.text._ZN4juce8TreeView12TreeViewportD0Ev[_ZN4juce8TreeView12TreeViewportD5Ev]+0x8c):
  relocation truncated to fit: R_MIPS_GOT_PAGE against
  `.text._ZN4juce8TreeView12TreeViewportD0Ev'


  
CMakeFiles/juceaide.dir/__/__/__/modules/juce_gui_basics/juce_gui_basics.cpp.o:
  in function `non-virtual thunk to
  juce::TreeView::TreeViewport::~TreeViewport()':


  

Bug#1062259: libcomps: NMU diff for 64-bit time_t transition

[Holger Levsen]

On Wed, Feb 14, 2024 at 10:31:21AM -0800, Steve Langasek wrote:
> Well, these packages will be garbage collected from experimental upon the
> next upload of a package to unstable or experimental with a higher version;

which might happen next month or next year or in 2027...

> so this is a low priority vs the work to actually get the transition done
> successfully.

I'd appreciate if transitions would be less messy for random bystanders.
it takes you one email to ask for the removal of all errously uploaded
packages.

i'm not impressed.


-- 
cheers,
Holger

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

The planet we think we're living on no longer exists.


signature.asc
Description: PGP signature

Bug#1044079: augur: FTBFS with pandas 2.0

[Andreas Tille]

Control: tags -1 pending

Hi,

thanks a lot for this hint.

Am Wed, Feb 14, 2024 at 10:36:05AM +0100 schrieb s3v:
> I don't know if renaming is a drop-in replacement

Me neither but I simply trust that its passing its test
suite.

Kind regards
   Andreas.

-- 
http://fam-tille.de

Processed: Re: Bug#1044079: augur: FTBFS with pandas 2.0

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #1044079 [src:augur] augur: FTBFS with pandas 2.0
Added tag(s) pending.

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

Bug#1044079: marked as done (augur: FTBFS with pandas 2.0)

[Debian Bug Tracking System]

Your message dated Thu, 15 Feb 2024 18:34:11 +
with message-id 
and subject line Bug#1044079: fixed in augur 24.1.0-1
has caused the Debian Bug report #1044079,
regarding augur: FTBFS with pandas 2.0
to be marked as done.

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

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


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

Package: src:augur
Version: 22.1.0-1
Control: block 1043240 by -1

augur fails to build with pandas 2.0, currently in experimental.

Build log:
https://launchpadlibrarian.net/680698719/buildlog_ubuntu-mantic-amd64.augur_22.1.0-1_BUILDING.txt.gz

Autopkgtest log:
https://ci.debian.net/data/autopkgtest/unstable/amd64/a/augur/36575793/log.gz

A common source of failures is that pandas.util.testing has been renamed 
to pandas.testing.  Both names were available in all 1.x versions (and 
hence in Debian stable and oldstable), so Debian packages that were 
using this can immediately switch unconditionally.
--- End Message ---
--- Begin Message ---
Source: augur
Source-Version: 24.1.0-1
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated augur package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 15 Feb 2024 19:07:50 +0100
Source: augur
Architecture: source
Version: 24.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 1044079
Changes:
 augur (24.1.0-1) unstable; urgency=medium
 .
   * New upstream version
   * s/parse_time_string()/parse_datetime_string_with_reso()/ to gain
 pandas 2.0 compatitibility (Thanks for the hint to
 s3v )
 Closes: #1044079
Checksums-Sha1:
 28cbcb694430dfd009b0143010834f609a9b156f 2638 augur_24.1.0-1.dsc
 6bbba945bf34b2690073920eef7d276e452aeb5e 6713705 augur_24.1.0.orig.tar.gz
 5fb39e4fbc28ee6487f7f114e203d2c53271bb79 16232 augur_24.1.0-1.debian.tar.xz
 9489787902540e5da1243144eddff1c29e0ea781 10993 augur_24.1.0-1_amd64.buildinfo
Checksums-Sha256:
 162629a1ebf10f37af99b0cf79b974c724161c32e0d63e34496f8fe053248eaf 2638 
augur_24.1.0-1.dsc
 ffc32541ac4eb39e12d06e74796738eec96141cdccca4d5ccf700d090cbcc428 6713705 
augur_24.1.0.orig.tar.gz
 5e46985dc7f5e1754e30337ffb596e990af10b4f63e70645d0039afc23233e08 16232 
augur_24.1.0-1.debian.tar.xz
 1e20fbf464f6bf0846bb6c1567bf9e98ef2beff9188563066d05a82962e2cb5c 10993 
augur_24.1.0-1_amd64.buildinfo
Files:
 0ceb1bc712717a6b1dfd4b3ae6304fde 2638 science optional augur_24.1.0-1.dsc
 536ae317bb7f13ae4e424ee21026dbb5 6713705 science optional 
augur_24.1.0.orig.tar.gz
 7c9ef2528c0556869057549b7344f1a0 16232 science optional 
augur_24.1.0-1.debian.tar.xz
 64f9ea71262cbe71f9651c500a9ef75c 10993 science optional 
augur_24.1.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmXOVOARHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFYLRAAjXjm+1yyzDn59yoLgEBSj37XZY4gFihX
eLaH0ZHbM8Z3mJ1J7Bv8ue+h6xJMPaxgiiy0C3djNYphkg5THxPCRRLu12gEs5Zq
qNk3qw+lj2Q3nUdAd2sgza+HOyTU6QKisnu4pWG11oOhM/AxszBXEKB2mHyexAuJ
3gXtsLL+CExQKDXDqFt+bK71xkkC4neowiKI/Dx68/hq9dhbPa1KB7LUNsNvOsz3
Qu+8LhjB1Ww2J/ueuCRCb59qY19mzwl+ns36UKQQeR+IpUuSIgHa5DtccY/xeOu1
cEE3rqH5UeyC/Lmeoa3nADX+AypPxhXK6wBrJDirqY7yod0K5sFdsNcDkGt4LdfF
WbBz+yX9AgCQgzOkGXHMBs39MFy8UWV8hxL0zeSePN8qEc4N0icDz9BpdjSzGnpe
P4gqhXLU8QuINbkUogl/tgPyOjveXpT0HLA1/uTQVgy8omgPhoG+GiTd8l6l36Vw
I+9usjqHItA+BI/TCToPU/GP/arAgIxtzrSKorodUHTX9RZKJwh07NrfdXsnrEUs
Ot50pJ/7iSheCiq3LHMxdV80aCO2yb1rtAt0uDgsLUXXw+l9+uPjVUzc3dcK+OaA
jMiCO4QDXBQHKmsfjOU3S2LFzWXMi+CDrBBrO4IuSNrIKv8N9njbt17LJbQhipgp
KobSV2kXPc4=
=owjE
-END PGP SIGNATURE-



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

Processed: severity

[Debian Bug Tracking System]

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

> severity 1062010 important
Bug #1062010 {Done: John Goerzen } [src:dar] dar: NMU 
diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
>
End of message, stopping processing here.

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

Processed: tagging 1063530, tagging 1063654, tagging 1064021, tagging 1064022, tagging 1064023, tagging 1064024 ...

[Debian Bug Tracking System]

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

> tags 1063530 + sid trixie
Bug #1063530 [src:node-undici] node-undici: FTBFS with nodejs 
18.19.0+dfsg-6~deb12u1
Added tag(s) sid and trixie.
> tags 1063654 + sid trixie
Bug #1063654 {Done: Debian FTP Masters } 
[ruby-graphql-errors] ruby-graphql-errors - upstream dead and incompatible with 
ruby-graphql 2.x
Added tag(s) trixie and sid.
> tags 1064021 + sid trixie
Bug #1064021 [src:gss] gss: FTBFS on armhf: FAIL: krb5context
Added tag(s) trixie and sid.
> tags 1064022 + sid trixie
Bug #1064022 [src:editorconfig-core] editorconfig-core: FTBFS on i386: error: 
Could not create output directory /<>/obj-i686-linux-gnu/doc/man
Added tag(s) sid and trixie.
> tags 1064023 + sid trixie
Bug #1064023 [src:cddlib] cddlib: FTBFS on armhf: ! Text line contains an 
invalid character.
Added tag(s) trixie and sid.
> tags 1064024 + sid trixie
Bug #1064024 [src:juce] juce: FTBFS on mips64el: Failed to build juceaide
Added tag(s) trixie and sid.
> tags 1060766 + sid trixie
Bug #1060766 [src:dumpasn1] dumpasn1: FTBFS with stack-clash-protection on 
armhf due to valgrind segfault
Added tag(s) sid and trixie.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1060766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060766
1063530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063530
1063654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063654
1064021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064021
1064022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064022
1064023: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064023
1064024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064024
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 1063744 to wnpp, reassign 1061966 to src:audit, fixed 1061966 in 1:3.1.2-2.1~exp3 ...

[Debian Bug Tracking System]

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

> reassign 1063744 wnpp
Bug #1063744 {Done: Colin Watson } [alexvsbus] RFP: 
alexvsbus -- a platform runner game
Warning: Unknown package 'alexvsbus'
Bug reassigned from package 'alexvsbus' to 'wnpp'.
Ignoring request to alter found versions of bug #1063744 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1063744 to the same values 
previously set
> reassign 1061966 src:audit 1:3.1.2-2.1~exp1
Bug #1061966 {Done: Steve Langasek } 
[libaudit1t64,libauparse0t64] file loss due to combining time64 + /usr-move
Warning: Unknown package 'libaudit1t64'
Bug reassigned from package 'libaudit1t64,libauparse0t64' to 'src:audit'.
No longer marked as found in versions 1:3.1.2-2.1~exp1.
No longer marked as fixed in versions audit/1:3.1.2-2.1~exp3.
Bug #1061966 {Done: Steve Langasek } [src:audit] file loss 
due to combining time64 + /usr-move
Marked as found in versions audit/1:3.1.2-2.1~exp1.
> fixed 1061966 1:3.1.2-2.1~exp3
Bug #1061966 {Done: Steve Langasek } [src:audit] file loss 
due to combining time64 + /usr-move
Marked as fixed in versions audit/1:3.1.2-2.1~exp3.
> reassign 1063890 src:zydis
Bug #1063890 [libzydiscore-dev] libzydiscore-dev: Static library is missing
Warning: Unknown package 'libzydiscore-dev'
Bug reassigned from package 'libzydiscore-dev' to 'src:zydis'.
Ignoring request to alter found versions of bug #1063890 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1063890 to the same values 
previously set
> reassign 1063754 src:linux
Bug #1063754 [fat-modules] fat-modules: SD corruption upon opening file on 
Linux desktop
Warning: Unknown package 'fat-modules'
Bug reassigned from package 'fat-modules' to 'src:linux'.
No longer marked as found in versions fat-modules-5.10.0-28-686-di.
Ignoring request to alter fixed versions of bug #1063754 to the same values 
previously set
> tags 1064024 + experimental
Bug #1064024 [src:juce] juce: FTBFS on mips64el: Failed to build juceaide
Added tag(s) experimental.
> tags 1064023 + experimental
Bug #1064023 [src:cddlib] cddlib: FTBFS on armhf: ! Text line contains an 
invalid character.
Added tag(s) experimental.
> tags 1052660 - sid trixie
Bug #1052660 [src:gst-plugins-bad1.0] gst-plugins-bad1.0: Fails to build: 
netsim build test failing
Removed tag(s) trixie and sid.
> tags 1038631 + experimental
Bug #1038631 [cinnamon-control-center] cinnamon-control-center: depends on 
obsolete policykit-1-gnome
Added tag(s) experimental.
> tags 1063796 + experimental
Bug #1063796 {Done: Paul Gevers } [src:plplot] src:plplot: 
fails to migrate to testing for too long: patchelf not available on mips64el
Added tag(s) experimental.
> found 1063497 2.1.11-1
Bug #1063497 [src:zfs-linux] zfs-dkms: Data loss bug in version in bookworm
Marked as found in versions zfs-linux/2.1.11-1.
> fixed 1063497 2.1.14-1
Bug #1063497 [src:zfs-linux] zfs-dkms: Data loss bug in version in bookworm
Marked as fixed in versions zfs-linux/2.1.14-1.
> tags 1063497 - bookworm
Bug #1063497 [src:zfs-linux] zfs-dkms: Data loss bug in version in bookworm
Removed tag(s) bookworm.
> found 979332 1.3.1+dfsg-5
Bug #979332 [libphp-simplepie] New upstream version
Marked as found in versions simplepie/1.3.1+dfsg-5.
> tags 979332 + bookworm sid trixie
Bug #979332 [libphp-simplepie] New upstream version
Added tag(s) sid, trixie, and bookworm.
> tags 1056888 - sid trixie
Bug #1056888 {Done: Graham Inggs } [src:scipy] scipy: ftbfs 
with cython 3.0.x
Removed tag(s) trixie and sid.
> tags 1049614 + experimental
Bug #1049614 {Done: Gianfranco Costamagna } 
[src:lirc] lirc: Fails to build binary packages again after successful build
Added tag(s) experimental.
> tags 1045980 + experimental
Bug #1045980 {Done: Thomas Weber } [src:lcms2] lcms2: Fails 
to build source after successful build
Added tag(s) experimental.
> tags 1004264 =
Bug #1004264 {Done: Boyuan Yang } [src:music] music: Please 
package new upstream version (1.1.17)
Removed tag(s) bookworm, sid, and trixie.
> tags 1004029 =
Bug #1004029 {Done: Boyuan Yang } [src:music] music: Please 
update package homepage information
Removed tag(s) bookworm, sid, and trixie.
> tags 1024506 + experimental
Bug #1024506 {Done: Felix Geyer } [src:docker.io] docker.io: 
FTBFS: FAIL: builder/remotecontext/git TestCheckoutGit
Bug #1040141 {Done: Felix Geyer } [src:docker.io] FTBFS: 
FAIL: TestCheckoutGit
Added tag(s) experimental.
Added tag(s) experimental.
> tags 1047442 + experimental
Bug #1047442 {Done: Samuel Thibault } [src:lwip] lwip: 
Fails to build source after successful build
Added tag(s) experimental.
> tags 1030683 + experimental
Bug #1030683 {Done: Daniel Baumann } 
[src:gnome-shell-extensions-extra] bundling extensions into one src/bin: 
unmaintainable?
Added tag(s) experimental.
> tags 1033061 + experimental
Bug #1033061 {Done: Ben Hutchings } [src:linux] linux: Enable 
Intel In-Field Scan (IFS)
Added tag(s) experimental.
> tags 1032437 + experimental

Processed: Re: Bug#1063329: libselinux1t64: breaks system in upgrade from unstable

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 seli...@vger.kernel.org
Bug #1063329 [libselinux1t64] libselinux1t64: breaks system in upgrade from 
unstable
Set Bug forwarded-to-address to 'seli...@vger.kernel.org'.

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

Bug#1063329: libselinux1t64: breaks system in upgrade from unstable

[Steve Langasek]

Control: forwarded -1 seli...@vger.kernel.org

Patch now forwarded upstream for review.

https://lore.kernel.org/selinux/zc6tzkpsyzric...@homer.dodds.net/T/#t



On Wed, Feb 14, 2024 at 11:25:26PM -0800, Steve Langasek wrote:
> On Wed, Feb 07, 2024 at 09:06:58AM +0100, Helmut Grohne wrote:
> > On Wed, Feb 07, 2024 at 04:32:45AM +0100, Guillem Jover wrote:
> > > Yes, I'm not sure I understand either. This is what symbol versioning
> > > makes possible, even providing different variants for the same symbol,
> > > see for example glibc or libbsd.
> 
> > I think symbol versioning is subtly different and glibc does not use
> > symbol versioning for e.g. gettimeofday selection. With symbol
> > versioning, you select a default version at release time and stick to
> > it. In other words, building against the updated libselinux does not
> > allow you to use the older 32bit variant of the symbol even if you opt
> > out of lfs and time64 and you always get the 64bit symbol. What glibc
> > does is a little more fancy than my simplistic #define in that it uses
> > asm("name") instead. Still this approach allows for selecting which
> > symbol is being used via macros (e.g. _FILE_OFFSET_BITS). Please correct
> > me if I am misrepresenting this as my experience with symbol versioning
> > is fairly limited.
> 
> Agreed.  libselinux as it happens does use a symbol version map so there is
> symbol versioning involved in some sense? but not the sense you really mean.
> 
> (We could make the symbol map expose the two different function variants
> under the same name but different symbols; that's fine but I'll leave that
> for upstream to decide.)
> 
> > > In any case, if going the bi-ABI path, I think upstream should get
> > > involved, and the shape of this decided with them. In addition
> > > the library should also be built with LFS by the upstream build
> > > system, which it does not currently, to control its ABI.
> 
> > I agree that involving upstream is a good idea and my understanding is
> > that someone from Canonical is doing that already, which is why the
> > schedule was delayed.
> 
> Well, "already" is not exactly correct, but the need to resolve this
> critical showstopper bug in libselinux before making changes to the
> toolchain behavior in unstable and breaking the world has affected the
> timeline, yes.
> 
> I now have a tested patch that I've raised as an MP in salsa:
> 
>   https://salsa.debian.org/selinux-team/libselinux/-/merge_requests/9
> 
> I welcome review from the Debian libselinux maintainers prior to opening a
> discussion with upstream.  (Which I will plan to do sometime Thursday
> US/Pacific)
> 
> -- 
> 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

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


signature.asc
Description: PGP signature

Bug#1063833: marked as done (mpich: ftbfs in sid due to newer slurm-wlm)

[Debian Bug Tracking System]

Your message dated Thu, 15 Feb 2024 21:28:02 +
with message-id 
and subject line Bug#1063833: fixed in mpich 4.1.2-3
has caused the Debian Bug report #1063833,
regarding mpich: ftbfs in sid due to newer slurm-wlm
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.)


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

Source: mpich
Version: 4.1.2-2
Severity: serious
tags: patch

Hello, the package now FTBFS due to newer slurm-wlm

see e.g. 
https://buildd.debian.org/status/fetch.php?pkg=mpich=i386=4.1.2-2%2Bb3=1707819996=0

  | ^~~~
./modules/mpl/include/mpl_atomic_c11.h:102:1: note: in expansion of macro 
‘MPLI_ATOMIC_DECL_FUNC_VAL’
  102 | MPLI_ATOMIC_DECL_FUNC_VAL(int64_t, int64, atomic_int_fast64_t, 
int_fast64_t)
  | ^
lib/tools/bootstrap/external/slurm_query_node_list.c: In function 
‘list_to_nodes’:
lib/tools/bootstrap/external/slurm_query_node_list.c:29:16: error: storage size 
of ‘hostlist’ isn’t known
   29 | hostlist_t hostlist;
  |^~~~
make[5]: *** [Makefile:1350: 
lib/tools/bootstrap/external/slurm_query_node_list.lo] Error 1

cherry-picking upstream fix 
https://github.com/pmodels/mpich/commit/7a28682a805acfe84a4ea7b41cea079696407398
is enough to make the build succeed.

G.


OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: mpich
Source-Version: 4.1.2-3
Done: Gianfranco Costamagna 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 13 Feb 2024 10:41:59 +0100
Source: mpich
Built-For-Profiles: noudeb
Architecture: source
Version: 4.1.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Gianfranco Costamagna 
Closes: 1063833
Changes:
 mpich (4.1.2-3) unstable; urgency=medium
 .
   * Team upload
   * debian/patches/7a28682a805acfe84a4ea7b41cea079696407398.patch:
 - upstream build fix (Closes: #1063833)
Checksums-Sha1:
 d05c668815ed47c9b3f572de2c7b2e86fe4041bc 2708 mpich_4.1.2-3.dsc
 e4b52496de2d02148f5da8948ec704cfa1b1da6e 339548 mpich_4.1.2-3.debian.tar.xz
 8a06292a4a8d704378bea46c9b2e897958456505 10970 mpich_4.1.2-3_source.buildinfo
Checksums-Sha256:
 a8f14af9471d3dc1d2eb6279187b066cc3a1a5b9526ca26a917350e69b71a1af 2708 
mpich_4.1.2-3.dsc
 1b4bf41af65e6429ea69c74dde628465c7a52f6b5be45053074676e1cee1fe76 339548 
mpich_4.1.2-3.debian.tar.xz
 275559e486c7f162d58dd728532f7d922ae5182be4991279e46f7ba3e55dbfdd 10970 
mpich_4.1.2-3_source.buildinfo
Files:
 e657d0ac90b31b54ac8e0ff1e6b9c98f 2708 devel optional mpich_4.1.2-3.dsc
 d949c92160e198d75c89bb638938d543 339548 devel optional 
mpich_4.1.2-3.debian.tar.xz
 f2929bb443a7b634e8fdd808539257cc 10970 devel optional 
mpich_4.1.2-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAmXOdxwACgkQ808JdE6f
XdkfKg//dZr+wefi5wCekQg2JEHfUEwvNZvddwlLYDKz0ZnltYLUiqKQFrs80ZFT
JkAYwYlWg1qDsNnaYnPXWKQ+58xjR6re1cpEXWNMmqOxtZYh8jQ340OnL3juqTXl
ZZWFg2XGc6dmQUkdVSkROvEaP7mULd2dlG2fywvsJEqvOZIqtmdL0TGPZlcFOUtN
K4Clbt6ikuLZo4/Bv63KUqKqjVZoemnqRTrdETT3ZTVxirtaAR92SKj9hc8YRQEi
KPayAv6sBEAOV0hSCN+JKToAqlBVab1X5zVTddV8sQw+El2XBGz9IooLPTgtQA3k
8g/xMruRuFzPoBqWHD9zphy2eUpfmDyuU82/flEv09KrLLSG4INbzRuF7cAk8ChS
zIbooG8Jgw68jwP4cJncmoO6xJ8QIzqO4EOzsdYqF++Hn5YUhOUUcRZTV9riUfvV
daPM70qwTCSQVMi7Nw2YxM+BdFVoPQLvukltMXtWwZxzixxwRXJzV5c/q45WAUjd
QG9kAXm2RBPizQmhY+ZKx7mo4wZhIJ4zNXvf8AMzi1NxFEV0A4hbGamIy5ZfYr9Z
HTV7sMbeBk+Sc7gnbpZvjOOWg2USvQM942cDfzbSVvLLKZ2wUOKrpUse3kClt4QD
GsHcprbDB990d/D01A6Baj26e4DOKSPeWgJ7SqEDywGp7YNwV4g=
=Tnzk
-END PGP SIGNATURE-



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

Processed: Re: Bug#1063527: einsteinpy: test_plotting fails to converge with scipy 1.11

[Debian Bug Tracking System]

Processing control commands:

> severity 1063527 serious
Bug #1063527 [src:einsteinpy] einsteinpy: test_plotting fails to converge with 
scipy 1.11
Severity set to 'serious' from 'important'

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

Processed: Re: scikit-learn: tests fail with scipy 1.10

[Debian Bug Tracking System]

Processing control commands:

> severity 1029701 serious
Bug #1029701 [scikit-learn] scikit-learn: tests fail with scipy 1.10
Severity set to 'serious' from 'normal'

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

Processed: Re: cloud-initramfs-growroot: missing dependencies in initramfs

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1037914 [cloud-initramfs-growroot] cloud-initramfs-growroot: missing 
dependencies in initramfs
Added tag(s) patch.

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

Bug#1037914: cloud-initramfs-growroot: missing dependencies in initramfs

[Tiago Ilieve]

Control: tags -1 patch

Hi,

I've managed to reproduce the original report after adding 'debug' to the
kernel command line and checking "/run/initramfs/initramfs.debug"[1].

A patch was sent to the "cloud-team/cloud-initramfs-tools" Salsa repository[2].

Regards,
Tiago.

[1]: https://wiki.debian.org/InitramfsDebug#Saving_debug_information
[2]: 
https://salsa.debian.org/cloud-team/cloud-initramfs-tools/-/merge_requests/8

--
Tiago "Myhro" Ilieve
Blog: https://blog.myhro.info/
GitHub: https://github.com/myhro
LinkedIn: https://www.linkedin.com/in/myhro/
Montes Claros, Brazil

Bug#1063491: python3-jedi: unvendoring python3-typeshed breaks other packages

[Daniel Vacek]

Package: python3-jedi
Followup-For: Bug #1063491
X-Debbugs-Cc: neel...@gmail.com

The 0.19.1+ds1-1 still depends on python3-typeshed. Is that correct?

--nX


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

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

Versions of packages python3-jedi depends on:
ii  python33.11.6-1
ii  python3-parso  0.8.3-1

python3-jedi recommends no packages.

python3-jedi suggests no packages.

-- no debconf information

Bug#1064034: FTBFS: Expired test certificate

[Ángel]

Package: ruby3.1
Version: 3.1.2-8
Severity: serious
Tags: ftbfs

A build of ruby3.1 fails on the test stage, since multiple
test/net/http/test_https.rb tests return 

> "ERROR OpenSSL::SSL::SSLError: SSL_accept returned=1 errno=0
peeraddr=(null) state=error: sslv3 alert certificate expired\n"

where no error was expected.


Failing tests:
TestNetHTTPS#test_get, TestNetHTTPS#test_skip_hostname_verification,
TestNetHTTPS#test_skip_hostname_verification, TestNetHTTPS#test_post,
TestNetHTTPS#test_min_version, TestNetHTTPS#test_get_SNI,
TestNetHTTPS#test_get, TestNetHTTPS#test_post,
TestNetHTTPS#test_min_version, TestNetHTTPS#test_get_SNI


The actual reason is that the certificate it uses (file
test/net/fixtures/server.crt) *IS* expired:

$ openssl x509 -in test/net/fixtures/server.crt -text
Certificate:
Data:
Version: 3 (0x2)
Serial Number: 2 (0x2)
Signature Algorithm: sha256WithRSAEncryption
Issuer: C = JP, ST = Shimane, L = Matz-e city, O = Ruby Core Team, CN = 
Ruby Test CA, emailAddress = secur...@ruby-lang.org
Validity
Not Before: Jan  2 03:27:13 2019 GMT
Not After : Jan  1 03:27:13 2024 GMT
Subject: C = JP, ST = Shimane, O = Ruby Core Team, OU = Ruby Test, CN = 
localhost


This was fixed upstream on 
https://github.com/ruby/ruby/commit/d3933fc753187a055a4904af82f5f3794c88c416