Processed: tagging 1037761

[Debian Bug Tracking System]

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

> tags 1037761 + pending
Bug #1037761 [src:lnav] lnav: ftbfs with GCC-13
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: limit source to git-imerge, tagging 1035639

[Debian Bug Tracking System]

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

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

> tags 1035639 + pending
Bug #1035639 [src:git-imerge] git-imerge: FTBFS with tox 4
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1043004: mozillavpn: CVE-2023-4104

[Salvatore Bonaccorso]

Source: mozillavpn
Version: 2.9.0-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for mozillavpn.

CVE-2023-4104[0]:
| Privileged vpndaemon on Linux wrongly and incompletely implements
| Polkit authentication


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-4104
https://www.cve.org/CVERecord?id=CVE-2023-4104
[1] https://www.openwall.com/lists/oss-security/2023/08/03/1

Regards,
Salvatore

Bug#1042980: gnome-shell: FTBFS on mips64el, mipsel: perf-* tests fail

[YunQiang Su]

Simon McVittie  于2023年8月4日周五 00:33写道：
>
> Source: gnome-shell
> Version: 44.3-1
> Severity: serious
> Tags: ftbfs experimental help
> Justification: fails to build from source (but built successfully in the past)
> X-Debbugs-Cc: debian-m...@lists.debian.org
> User: debian-m...@lists.debian.org
> Usertags: mips64el mipsel
>
> gnome-shell 44 builds successfully on all release architectures except
> mips*el, but fails to build on mips*el. The three perf-* unit tests fail
> with exit status 1 and no obvious error messages:
> 
> 
>
> At the moment this is only in experimental, but we want to upload it to
> unstable soon, as part of the libmutter-12-0 transition
> .
>

I will try to debug it.

> Is gnome-shell practically useful on mips-based hardware, or does it
> have hardware requirements that the mips family do not meet in practice?
> If nobody really uses it on mips*el, it might be better to do
> architecture-specific removals rather than attempting to debug and fix it.
>
> Or, if the mips porting team can confirm that GNOME 43 works in practice
> as a desktop environment on mips*el hardware, then it would be useful

Yes. There are some MIPS desktop cases.

> to try GNOME 44 from experimental on the same hardware (after building
> gnome-shell locally with DEB_BUILD_OPTIONS=nocheck) to check whether
> this is a practical problem.
>
> Thanks,
> smcv
>


-- 
YunQiang Su

Processed: python-escript: FTBFS on i386

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1041457 [src:python-escript] python-escript: FTBFS on i386
Severity set to 'important' from 'serious'

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

Bug#1041457: python-escript: FTBFS on i386

[Sebastiaan Couwenberg]

Control: severity -1 important

python-escript was removed from i386 (#1042939).

Reducing the severity accordingly.

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#1031977: marked as done (gdb-bpf: not binNMU safe)

[Debian Bug Tracking System]

Your message dated Fri, 04 Aug 2023 04:20:07 +
with message-id 
and subject line Bug#1031977: fixed in gdb-bpf 6
has caused the Debian Bug report #1031977,
regarding gdb-bpf: not binNMU safe
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.)


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

The method to compute the version of the binary packages is not
binNMU-safe. This can be seen from the latest round of binNMUs to
rebuild for outdated Built-Using fields. See
https://buildd.debian.org/status/fetch.php?pkg=gdb-bpf=amd64=5%2Bb1=1677353719=0

As it can be seen from the log, the version of the binary packages is
computed as the version of gdb and a single +. The binNMU version -- b1
in this case -- is missing. Locally rebuilding the package with a
different binNMU version produces the same version number.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: gdb-bpf
Source-Version: 6
Done: Matthias Klose 

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated gdb-bpf package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 04 Aug 2023 05:44:33 +0200
Source: gdb-bpf
Architecture: source
Version: 6
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Matthias Klose 
Closes: 1031977
Changes:
 gdb-bpf (6) unstable; urgency=medium
 .
   * Build using GDB 13.2.
   * Honor appendix in source version. Closes: #1031977.
Checksums-Sha1:
 2c73ea5b77d646b4d768ed7e9bdec4fed41393dd 1769 gdb-bpf_6.dsc
 9eeab7af4f92d1cf304368e45aaf015f39dc192a 6724 gdb-bpf_6.tar.xz
 14980755b31cc18209b13cd8f2c707520d4a3d28 7780 gdb-bpf_6_source.buildinfo
Checksums-Sha256:
 4303e299ee3a439e0de4f7cc569a97997807987ca4d22a0590bdba8f25328fea 1769 
gdb-bpf_6.dsc
 3efd2367e33b61058c71c1c8e3ae9c518cc5c7456083f62aad517a534c86326d 6724 
gdb-bpf_6.tar.xz
 e0e306b1b0b3c46c62544a9073a0b7d4fed8decbe11cc233b2fd2c9eb91177c0 7780 
gdb-bpf_6_source.buildinfo
Files:
 70d47382a5ed0b815334bdf36a762591 1769 devel optional gdb-bpf_6.dsc
 4290f7e0a4ea82874a363cf76f1f3470 6724 devel optional gdb-bpf_6.tar.xz
 4b4016a292b3d9de3331c19d5f8ab82f 7780 devel optional gdb-bpf_6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmTMdYUQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9V9nD/9HqNYZyaS3f0ocZK6cVGNnkGtO8Sfycdl/
LyNT42fcEIJ6juTGH1gdyZc6dZ7OGv0oGvzQsqIbFFqWBCD0khrYOa1Y5m0MhtMW
zLazEq/MZJMpNnIPHh6li6KuLkZCVKvuhGEYZerbPEaj8a77qMoasPZh2WUxYMJ6
zECdzs6Zz0W6cTpbvn+AFTF+rGqt/PmIRmCWRDYowMuOmniOs9GFNakoalGFMZpM
8iWTKwdk3iVF06SIRV+1gB8G8jMfrVGN+W0fBw6JDXH2EaQ6fPh8frPEJ8KuAdEk
IKHGJEXt5E7SdYgBpfLYTrQa6PKdgk/MEnBK8yRRao/OQ97ZVRW6aLKc9pTiwG6y
8D4q44H+eM3QmByzKnPzjOPUBXImc+K7j4hzfIBxPTQkm22UkKaGbYI0DDHJG83P
oduwG+18h/JsCfLDBQ7Wb2janxMZnNuhFvAVe5f1EvtQ7N11FtFnXo0ZCDd1BGIv
bc1k9r7UIyd9T96OJDDmVmmJTY+n4/GE21aMbRQxDCK5c+jWn8JlyThSGhSFsGtk
F+8fpxB9SCbKpqUucnTY4X4A8+/uevl94kwh4KnPLlXhzeYlxsx4PpxRUB2s5AfT
267Yo4gDsQgnV2gyB1BewD+qxZn52NNWdpD0vslZXiktEPvJy+vhASFvThy0/gO7
0zO6JyFIoQ==
=bcuk
-END PGP SIGNATURE End Message ---

Bug#1042044: Additional information

[Vladimir Petko]

Dear Maintainers,

I have tried to fix gtk warnings but due to changes in the FileDialog
API there are significant changes that are best fixed upstream[1].
I have attached debdiff patch to disable those warnings for now.

Best regards,
 Vladimir.

[1] https://github.com/strongswan/strongswan/issues/1829


disable-gtk-warnings.debdiff
Description: Binary data

Bug#899908: marked as done (opennebula-context: Invalid maintainer address pkg-opennebula-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Thu, 03 Aug 2023 23:41:01 +
with message-id 
and subject line Bug#1042924: Removed package(s) from unstable
has caused the Debian Bug report #899908,
regarding opennebula-context: Invalid maintainer address 
pkg-opennebula-de...@lists.alioth.debian.org
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.)


-- 
899908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899908
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:opennebula-context
Version: 4.14.0-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of opennebula-context,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package opennebula-context since the list address
pkg-opennebula-de...@lists.alioth.debian.org used in the Maintainer:
field was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-opennebula-de...@lists.alioth.debian.org is 2.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 4.14.0-1+rm

Dear submitter,

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

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

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

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

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

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

Bug#737395: marked as done (funny-manpages: Copyright problem)

[Debian Bug Tracking System]

Your message dated Thu, 03 Aug 2023 23:41:30 +
with message-id 
and subject line Bug#1042925: Removed package(s) from unstable
has caused the Debian Bug report #737395,
regarding funny-manpages: Copyright problem
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.)


-- 
737395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737395
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: funny-manpages
Version: 1.3-5
Severity: serious

The contents of /usr/share/doc/funny-manpages/copyright does
not at all look as if the package would be DFSG-free:

<--  snip  -->

This package was debianized by Pawel Wiecek co...@pwr.wroc.pl on
Wed, 10 Dec 1997 01:10:17 +0100.

This set of manpages was collected from all over the net. No specific
location can be given.

Copyright:

To the best of my knowledge all of these manpages are free to use and
redistribute.

The authors are:

baby.1fun   - unknown, based on man page by Joe Beck 
celibacy.1fun   - unknown
condom.1fun - Ken Maupin 
flame.1fun  - unknown
flog.1fun   - unknown
gong.1fun   - unknown
grope.1fun  - unknown
party.1fun  - unknown
rescrog.1fun- unknown
rtfm.1fun   - unknown
sex.1fun- unknown
tm.1fun - unknown
xlart.1fun  - James McPherson
date.1fun   - Glen Overby 
echo.1fun   - unknown
rm.1fun - Matthew Farwell 
strfry.3fun - 
xkill.1fun  - Claudio Calvelli 
uubp.1fun   - unknown

<--  snip  -->
--- End Message ---
--- Begin Message ---
Version: 2.3-1+rm

Dear submitter,

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

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

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

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

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

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

Bug#1041364: marked as done (adapta-gtk-theme: Intent of package removal)

[Debian Bug Tracking System]

Your message dated Thu, 03 Aug 2023 23:43:32 +
with message-id 
and subject line Bug#1042991: Removed package(s) from unstable
has caused the Debian Bug report #1041364,
regarding adapta-gtk-theme: Intent of package removal
to be marked as done.

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

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


-- 
1041364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041364
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: adapta-gtk-theme
Severity: serious
Version: 3.95.0.11-2
Tags: sid trixie
X-Debbugs-CC: prof.franciscar...@gmail.com

Dear Debian adapta-gtk-theme package maintainer,

As stated in https://bugs.debian.org/1010199 , the upstream development of
this package has ended and it is now the candidate for removal from Debian.
I intend to remove this package after 3 weeks (after Aug 07, 2023) if no
disagreement appears. If you have any comments, please let me know as soon
as possible by replying this bug report.

Thanks,
Boyuan Yang


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

Dear submitter,

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

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

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

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

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

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

Bug#1038624: marked as done (netcdf-cxx-legacy: Should not be included in trixie)

[Debian Bug Tracking System]

Your message dated Thu, 03 Aug 2023 23:42:20 +
with message-id 
and subject line Bug#1042963: Removed package(s) from unstable
has caused the Debian Bug report #1038624,
regarding netcdf-cxx-legacy: Should not be included in trixie
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.)


-- 
1038624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038624
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: netcdf-cxx-legacy
Version: 4.2-13
Severity: serious
Control: block -1 by 1038449 1038468 1038596 1038602 1038618 1038619 1038614

netcdf-cxx-legacy is dead upstream, where it was superseded by netcdf-cxx.

netcdf-cxx-legacy should not be included in trixie, but cannot be removed 
before its rdeps are.
--- End Message ---
--- Begin Message ---
Version: 4.2-13+rm

Dear submitter,

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

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

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

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

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

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

Bug#1019304: marked as done (adapta-gtk-theme: Please build-depend on libgdk-pixbuf-2.0-dev instead of libgdk-pixbuf2.0-dev)

[Debian Bug Tracking System]

Your message dated Thu, 03 Aug 2023 23:43:32 +
with message-id 
and subject line Bug#1042991: Removed package(s) from unstable
has caused the Debian Bug report #1019304,
regarding adapta-gtk-theme: Please build-depend on libgdk-pixbuf-2.0-dev 
instead of libgdk-pixbuf2.0-dev
to be marked as done.

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

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


-- 
1019304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019304
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: adapta-gtk-theme
Version: 3.95.0.11-2
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: split-gdk-pixbuf

In Debian 10 and older, the libgdk-pixbuf2.0-dev package contained
development files for two libraries: gdk-pixbuf-2.0 and the deprecated
gdk-pixbuf-xlib-2.0.

In Debian 11, it was split into libgdk-pixbuf-2.0-dev and
libgdk-pixbuf-xlib-2.0-dev packages. libgdk-pixbuf2.0-dev continues to
exist, but is now a transitional package that pulls in the deprecated
libgdk-pixbuf-xlib-2.0-dev in addition to libgdk-pixbuf-2.0-dev.

If libgdk-pixbuf-2.0-dev is sufficient to build this package,
please swap the build-dependency on libgdk-pixbuf2.0-dev to refer to
libgdk-pixbuf-2.0-dev instead. That change will avoid this package having
to be removed from Debian if gdk-pixbuf-xlib gets removed.

If this package also needs the deprecated gdk-pixbuf-xlib-2.0
(unlikely), please build-depend on both libgdk-pixbuf-2.0-dev and
libgdk-pixbuf-xlib-2.0-dev explicitly, instead of via the transitional
package libgdk-pixbuf2.0-dev.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Version: 3.95.0.11-2+rm

Dear submitter,

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

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

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

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

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

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

Bug#1010199: marked as done (adapta-gtk-theme: Development has completely and officially ended)

[Debian Bug Tracking System]

Your message dated Thu, 03 Aug 2023 23:43:32 +
with message-id 
and subject line Bug#1042991: Removed package(s) from unstable
has caused the Debian Bug report #1010199,
regarding adapta-gtk-theme: Development has completely and officially ended
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.)


-- 
1010199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010199
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: adapta-gtk-theme
Version: 3.95.0.11-2
Severity: minor
Tags: upstream
X-Debbugs-Cc: lorenzolucio+b...@live.it

Dear maintainer,
development has completely ended in 2018 and the official repository has been
archived in 2020.

Due to the rapid development of CSS this package is already
flooding .xsession-errors with theme parsing errors and, because GTK's CSS is
now compiled, end users have no easy way to fix the issue.
Perhaps it is time to mark this package as obsolete and add suggested
alternatives or remove it from the repository altogether.

Best regards,
Lorenzo

adapta-gtk-theme recommends no packages.
adapta-gtk-theme suggests no packages.
--- End Message ---
--- Begin Message ---
Version: 3.95.0.11-2+rm

Dear submitter,

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

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

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

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

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

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

Bug#1042937: marked as done (libsasl2-dev should depend on libssl-dev)

[Debian Bug Tracking System]

Your message dated Thu, 03 Aug 2023 23:21:11 +
with message-id 
and subject line Bug#1042937: fixed in cyrus-sasl2 2.1.28+dfsg1-3
has caused the Debian Bug report #1042937,
regarding libsasl2-dev should depend on libssl-dev
to be marked as done.

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

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


-- 
1042937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042937
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cyrus-sasl2
Version: 2.1.28+dfsg1-2
Severity: grave

Hi there,

I noticed that the last upload for cyrus-sasl2 removed the md5.h header
file (among other stuff).  As it turns out, /usr/include/sasl/hmac-md5.h
will include  which will make builds using the header
FTBFS.  This is currently the case with OpenLDAP.

I'd like to request that libsasl2-dev depend on libssl-dev so that we
can get a working md5.h.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: cyrus-sasl2
Source-Version: 2.1.28+dfsg1-3
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated cyrus-sasl2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 04 Aug 2023 00:35:18 +0200
Source: cyrus-sasl2
Architecture: source
Version: 2.1.28+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Cyrus Team 
Changed-By: Bastian Germann 
Closes: 1042937
Changes:
 cyrus-sasl2 (2.1.28+dfsg1-3) unstable; urgency=medium
 .
   * Let libsasl2-dev depend on libssl-dev (Closes: #1042937)
Checksums-Sha1:
 b164322d374c8f24009d5c80ea8527131290881a 3330 cyrus-sasl2_2.1.28+dfsg1-3.dsc
 5eb172467dcd271264613f7aed18a80728b014b5 106568 
cyrus-sasl2_2.1.28+dfsg1-3.debian.tar.xz
 df4e4fbfd580fc111cfbba56aae9e6f57f3686c9 9476 
cyrus-sasl2_2.1.28+dfsg1-3_source.buildinfo
Checksums-Sha256:
 a43831934f49088f8a018913e3ed7fc48ffc2e5c48a8eafbba25ccabdaf80341 3330 
cyrus-sasl2_2.1.28+dfsg1-3.dsc
 7e2bc5df64d3959cd190cf24b9a0d89be48708ff167b0d7556b2f6818b1de397 106568 
cyrus-sasl2_2.1.28+dfsg1-3.debian.tar.xz
 fa14b52f99f4e9208fdfafbc845670caff46cc5b380d7e36c253f157bb0af05f 9476 
cyrus-sasl2_2.1.28+dfsg1-3_source.buildinfo
Files:
 5f432ff09349aa4ed669e07c0879563d 3330 libs optional 
cyrus-sasl2_2.1.28+dfsg1-3.dsc
 133d8e8b4d4a6192408b94bd20e63fd3 106568 libs optional 
cyrus-sasl2_2.1.28+dfsg1-3.debian.tar.xz
 c991f45c8bafcfcc88ce76204de890a9 9476 libs optional 
cyrus-sasl2_2.1.28+dfsg1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmTMLsMQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFITeDADiCmkNroYURjLdj0J2YZKRQipT4SzOxt1p
mL+L5b00HMq1b7+cJncnWfyaSMPbmMfPYNu0OZ63q4HkWLSa7/8tDeOU4KFAkNhe
X3ZzduZCFk20F1SNQMHrMME+U85hPQQMhnrCXwa4rPAz6XZnmken8pA+lulT8h69
zs7YRGW1RH+Cu7//4HBAStHlrd3gtKKWJcR9V/DSqVeend94WphX118OqHFP8n/R
D2xbUVAniMefNC2dpVzfwtTy32IBtE4ASmtzJ4ipJCrdqZ9xBdQtUEpFjg+zuLMH
AKM1w2qnyScqbhjZAv1EA6JQ5+74BcGbTNtGYXfs/WEL1YjcGgnoN365Wgx/fT0n
LulraThUxoSm4lmZNuJGOBa69fTnnX2UnX8onsDKOnVhHqvU7AImDzZdvwlIynGw
Ggo1RFYlXgYHsQZUeSrAkYdDO9fv0YMVdvc53AkiJ+YJm9J2ji34viwXakfNHRKw
5j+B5GpNjt/RWS6Fi0fRIhxjy2QxNWg=
=ySBD
-END PGP SIGNATURE End Message ---

Bug#1039710: marked as done (busybox-udeb: /var/log/syslog is empty)

[Debian Bug Tracking System]

Your message dated Thu, 03 Aug 2023 23:20:30 +
with message-id 
and subject line Bug#1039710: fixed in busybox 1:1.36.1-3.1
has caused the Debian Bug report #1039710,
regarding busybox-udeb: /var/log/syslog is empty
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.)


-- 
1039710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039710
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer
Version: daily build 2023-06-28T05:19Z
Severity: grave
Tags: d-i
Justification: renders package unusable
X-Debbugs-Cc: p...@hands.com

Hello Debian-installer maintainers,

On openQA [1] the installation tests with the latest netinst image [2] fail,
because GRUB cannot install.
I've tried to look a bit deeper into the issue, but I cannot proceed, because
/var/log/syslog is empty. So effectively there are possibly two issues in this
report:
1) Failure in grub
2) No logging to /var/log/syslog

My findings so far:
* The command line arguments of syslogd and klogd (both from Busybox) have not
changed between Bookworm and Trixie.
* At the moment of the failure, the /var/log folder contains only 3 files [3]:
syslog (a single line, stating that syslog was started from Busybox [4]),
partman and Xorg.0.log
* When running `logger`, an entry should have been created in /var/log/syslog,
but that doesn't happen. The netinst image from Bookworm works correctly.
* Possibly relevant packages that have been updated: busybox, libc, linux-
image, bsdutils

With kind regards,
Roland Clobus

[1] https://openqa.debian.net/tests/167456
[2] https://get.debian.org/images/daily-builds/daily/arch-latest/amd64/iso-
cd/debian-testing-amd64-netinst.iso
[3] https://openqa.debian.net/tests/167456/file/grub-var_log.tar
[4] https://openqa.debian.net/tests/167456/logfile?filename=DI_syslog.txt

PS: Attached system information is from my personal computer, not the installed
system


-- System Information:
Debian Release: 12.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: busybox
Source-Version: 1:1.36.1-3.1
Done: Steve McIntyre <93...@debian.org>

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

Debian distribution maintenance software
pp.
Steve McIntyre <93...@debian.org> (supplier of updated busybox 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, 03 Aug 2023 21:22:44 +0100
Source: busybox
Architecture: source
Version: 1:1.36.1-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Steve McIntyre <93...@debian.org>
Closes: 1039710
Changes:
 busybox (1:1.36.1-3.1) unstable; urgency=medium
 .
   * NMU
   * Revert recent changes that have broken syslogd in d-i.
 Closes: #1039710
Checksums-Sha1:
 2c296d809815f286fb98eede39da174716b6b999 2312 busybox_1.36.1-3.1.dsc
 f1127d7cdaad49d1c036cb47cf4cab5fa0645985 64680 busybox_1.36.1-3.1.debian.tar.xz
 f3bc7ce917ed5b80d9000948f87f38a7b2d3b4ce 6160 
busybox_1.36.1-3.1_source.buildinfo
Checksums-Sha256:
 764e284a165dbf37a008a02fbfaf8a3ab2186a309fcd3a905aa32501d81a0682 2312 
busybox_1.36.1-3.1.dsc
 acbdd882ea73b62e2320198f3e68d79a960c1da7046a90601060f406a44c051d 64680 
busybox_1.36.1-3.1.debian.tar.xz
 e1f591ede73556c8b01a004afdbe981b77986555fa518e714cfe99b9cf06e01c 6160 
busybox_1.36.1-3.1_source.buildinfo
Files:
 7af430428d576204910350271d1da8b3 2312 utils optional busybox_1.36.1-3.1.dsc
 9107eefb885a9e72ba0636ca3246374a 64680 utils optional 
busybox_1.36.1-3.1.debian.tar.xz
 5c71cc338babaa7fc3f66decbe6bb88d 6160 utils optional 
busybox_1.36.1-3.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEEzrtSMB1hfpEDkP4WWHl5VzRCaE4FAmTMMhoRHDkzc2FtQGRl

Bug#996905: pms: diff for NMU version 0.42-1.1

[gregor herrmann]

Control: tags 996905 + patch
Control: tags 996905 + pending


Dear maintainer,

Daniel Gröber has prepared an NMU for pms (versioned as 0.42-1.1) and
I've uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   
diff -Nru pms-0.42/debian/changelog pms-0.42/debian/changelog
--- pms-0.42/debian/changelog	2013-08-11 22:46:48.0 +0200
+++ pms-0.42/debian/changelog	2023-07-05 23:17:35.0 +0200
@@ -1,3 +1,14 @@
+pms (0.42-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "FTBFS: error: format not a string literal and no format arguments
+[-Werror=format-security]" by selectively demoting -Wformat-security to
+warning (Closes: #996905)
+  * Fix time() undeclared error when building with gcc-12
+  * Upgrade debhelper compat to 11 and fix related lintian warnings
+
+ -- Daniel Gröber   Wed, 05 Jul 2023 23:17:35 +0200
+
 pms (0.42-1) unstable; urgency=low
 
   * New upstream release (Closes: #612192).
diff -Nru pms-0.42/debian/compat pms-0.42/debian/compat
--- pms-0.42/debian/compat	2013-08-11 21:14:52.0 +0200
+++ pms-0.42/debian/compat	1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-9
diff -Nru pms-0.42/debian/control pms-0.42/debian/control
--- pms-0.42/debian/control	2013-08-11 22:40:45.0 +0200
+++ pms-0.42/debian/control	2023-07-05 23:17:35.0 +0200
@@ -1,9 +1,10 @@
 Source: pms
 Section: sound
-Priority: extra
+Priority: optional
 Maintainer: Alejandro Garrido Mota 
-Build-Depends: debhelper (>= 9), gettext, gettext-base, libgettextpo0, libncurses5-dev,
-   libmpd-dev, libncursesw5-dev, libglib2.0-dev, gnulib, libboost-regex-dev
+Build-Depends: debhelper-compat (= 11),
+   gettext, gettext-base, libgettextpo0, libncurses-dev,
+   libmpd-dev, libglib2.0-dev, gnulib, libboost-regex-dev
 Standards-Version: 3.9.4
 Homepage: http://pms.sourceforge.net
 
diff -Nru pms-0.42/debian/patches/Fix-autotools-errors.patch pms-0.42/debian/patches/Fix-autotools-errors.patch
--- pms-0.42/debian/patches/Fix-autotools-errors.patch	1970-01-01 01:00:00.0 +0100
+++ pms-0.42/debian/patches/Fix-autotools-errors.patch	2023-07-05 23:17:35.0 +0200
@@ -0,0 +1,24 @@
+Description: Fix autotools errors
+Author: Daniel Gröber 
+--- a/configure.ac
 b/configure.ac
+@@ -13,7 +13,7 @@ AC_ARG_ENABLE([regex],
+esac])
+ 
+ AC_PREFIX_PROGRAM(man)
+-AM_INIT_AUTOMAKE([-Wall -Werror foreign])
++AM_INIT_AUTOMAKE([-Wall -Werror subdir-objects foreign])
+ AC_PROG_CXX
+ AC_CONFIG_HEADERS([config.h])
+ AC_CONFIG_FILES([Makefile po/Makefile.in])
+--- a/Makefile.am
 b/Makefile.am
+@@ -3,7 +3,7 @@ man_MANS = pms.1
+ EXTRA_pms_SOURCES = src/action.h src/color.h src/command.h src/config.h src/conn.h src/display.h src/input.h src/list.h src/song.h src/types.h src/libmpdclient.h src/i18n.h src/topbar.h src/pms.h src/settings.h src/field.h src/mycurses.h src/mediator.h src/message.h src/filter.h
+ EXTRA_DIST = config.rpath m4/ChangeLog  pms.1 po
+ pms_SOURCES = src/action.cpp src/color.cpp src/command.cpp src/config.cpp src/conn.cpp src/display.cpp src/input.cpp src/list.cpp src/pms.cpp src/song.cpp src/libmpdclient.c src/field.cpp src/settings.cpp src/mediator.cpp src/message.cpp
+-CXXFLAGS += \
++AM_CXXFLAGS = \
+ 	@GLIB_CFLAGS@ \
+ 	-DLOCALE_DIR=\""$(datadir)/locale"\"
+ 
diff -Nru pms-0.42/debian/patches/Fix-missing-ctime-include.patch pms-0.42/debian/patches/Fix-missing-ctime-include.patch
--- pms-0.42/debian/patches/Fix-missing-ctime-include.patch	1970-01-01 01:00:00.0 +0100
+++ pms-0.42/debian/patches/Fix-missing-ctime-include.patch	2023-07-05 23:17:35.0 +0200
@@ -0,0 +1,13 @@
+Description: Fix missing  include
+ Newer gcc version must have moved stuff around
+Author: Daniel Gröber 
+--- a/src/message.cpp
 b/src/message.cpp
+@@ -23,6 +23,7 @@
+ 
+ 
+ #include 
++#include 
+ #include 
+ #include "message.h"
+ 
diff -Nru pms-0.42/debian/patches/Ignore-format-security-FP.patch pms-0.42/debian/patches/Ignore-format-security-FP.patch
--- pms-0.42/debian/patches/Ignore-format-security-FP.patch	1970-01-01 01:00:00.0 +0100
+++ pms-0.42/debian/patches/Ignore-format-security-FP.patch	2023-07-05 23:17:35.0 +0200
@@ -0,0 +1,47 @@
+Description: Ignore -Wformat-security false positive
+ I don't see a reasonable way to rewrite this code without triggering this
+ warning since the dynamic format string being used here is controlled by the
+ user in the rc file.
+Author: Daniel Gröber 
+--- a/src/display.cpp
 b/src/display.cpp
+@@ -1700,6 +1700,7 @@ void colprint(pms_window * w, int y, int
+ 			{
+ fmt += 2;
+ output = "%%";
++#pragma GCC diagnostic warning "-Wformat-security"
+ wprintw(w->h(), 

Processed: pms: diff for NMU version 0.42-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 996905 + patch
Bug #996905 [src:pms] pms FTBFS: error: format not a string literal and no 
format arguments [-Werror=format-security]
Added tag(s) patch.
> tags 996905 + pending
Bug #996905 [src:pms] pms FTBFS: error: format not a string literal and no 
format arguments [-Werror=format-security]
Added tag(s) pending.

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

Processed: RE: ruby-moneta: FTBFS: ERROR: Test "ruby3.1" failed: cannot load such file -- ox/ox

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:ruby-ox
Bug #1042218 [src:ruby-moneta] ruby-moneta: FTBFS: ERROR: Test "ruby3.1" 
failed: cannot load such file -- ox/ox
Bug reassigned from package 'src:ruby-moneta' to 'src:ruby-ox'.
No longer marked as found in versions ruby-moneta/1.5.2-1.
Ignoring request to alter fixed versions of bug #1042218 to the same values 
previously set

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

Bug#1042218: ruby-moneta: FTBFS: ERROR: Test "ruby3.1" failed: cannot load such file -- ox/ox

[Leandro Cunha]

Control: reassign -1 src:ruby-ox

The package in question causing the problem is ruby-ox (on an upgrade
to 2.14.16-1 and solved with 2.14.17-1). The 'ox/ox' does not exist in
Debian's ruby-ox (but assumes it is in stalled as a gem and hence
loads 'ox/ox'), but there is only 'ox.so' and the solution was to
remove the require for 'ox/ox'. Require relative, according to the
documentation[1], when it returns false for a directory not found, it
returns a load error with a file not found message and does not search
for the file in the entire directory tree, unlike require that found
the archive 'ox.so'.

[1] https://ruby-doc.org/3.2.2/Kernel.html#method-i-require_relative

-- 
Cheers,
Leandro Cunha
-BEGIN PGP PUBLIC KEY BLOCK-

mQINBF/gQ8gBEADHVKgoWsUWNGVvR6sMhBPUdBUEH+QALpr1QYXhetBfRwaY0HWN
pKgejHdxKO8H+kIhRMoh89CCKg3hAJ9LmOOTXkX7U5/Cya/zRMKk5zBD3rKIaugh
0XYT15Nz1jwL7TIDG25yPSloDtVgVXTep0ZzKsNYJjb4OAqa88cvUEJEhhqrldlR
gpNbkixEh5ituO8pMShEBWqLs3yt4Hr1VFWnTIm4dl/JLBHpexzubDOw/mKCTpNd
A1JGHTvce1wtJ2fMzCVzhEjd5pyjLZV/o8hVw2/ON/yXvpJuz0lV/hiW0M+cDcas
sKftErtsZpRy3wwXdkBcJt6soYuqfCHwgMfL2iC6mPviE8xWAHMOmhdC3wDskZpb
RcLfH5IMYajJAGRO/GCMcKKbq7WkEOeloivtg64xBlYuJf9aOcHKP/8R3EObiNp7
ubQAJtV3pEGD4mx1mhutFxDHB+CfnxE3dWvxZSV9y1n4UOzkDJ3kDx5Ee0MbRvJD
w6aXKc6dhYREgh7hLDcMFz+3LcBiZDLxI3g+SHe3Bl61vdsnPno+0HhCzvB+fL4S
eoy7Myfiunz9BrB2HPN+wNCT0YgV+Kv8QoDGzBwos5H1vUJSY4t59w6xoXAYUsAm
hjAM8s+rUtG40mcUWePd8kZtgE9IV1eQ+Qt8/SNpSdRnUunmIGl3JjHvEwARAQAB
tClMZWFuZHJvIEN1bmhhIDxsZWFuZHJvY3VuaGEwMTZAZ21haWwuY29tPokCTgQT
AQoAOBYhBLT5oBCvKN3HzFEPK8LZ4zKUW9A8BQJf4EPIAhsDBQsJCAcCBhUKCQgL
AgQWAgMBAh4BAheAAAoJEMLZ4zKUW9A8FjAQAKWYqiLpLUD+DLB+NSy3DI3rf9z3
k0vE7TLaEjdEM5CQWN+j4vBqMnAckdcARvSWPndTjp8K+mtFF4PyfhNbS64z/a7L
F3DdhmX73n7LKFG8Ow9NZwcrkmPwH5WcP7mXTh6R+6/+OSL/K85NB8MLlxQTJOni
julVax9JEZjwBaP2HLCu53Zq9gZcvJlXoAoTHyTxKdp8Mh8V+Qit26E78o9c6SQD
Dq9eyMRG8hYCRfreDjKceRkYHjECySlk+VoI1ssVs07Dqvxg6qSyP4RnW+1+W74C
s0yIyuC/eRJpMAf1PBQEOOrVcTfRfpN+go955t21yIAvT58vqotTM5eaqXYIQn/y
sC4lThZai/ZBZHxl5Mbv42WkkYdjisLQOCALIMBpj5nq4oh2C+kvMupcuBKfERgV
dguU51MzfQktKb6d5y777zYnDaFMQDD2IfiD/C7ln5A9LP/L54ixlA3uRmWx/yAx
/m+Zusws98j4Eq/jw5T54XW655m6lMCTE9WXLJkgxrRcEonHSllbgRSsToEmWq0Z
doxcnpagHdcGQzW+cu2VOGi1da73ZFmrn+ptJgc8cW2suO06IeArOi0TzIg7e65j
Xp2DbJCpFrfzEuBb1u71WvB8V2MkAfJZx/uZJPCA936B4HT8YGPEMzlQRIHI2Y9C
+DloyzlBLTS1EMKuuQINBF/gQ8gBEAC47o9u1Wm9jZ6RC+lfxEDEvVS7MmI5VzSy
q04rFttWwbKix13pc65aDlk47LxWrb84N3Gnf1E/OTsLTXqC7u5JZ7YJkC6CsPbo
D1sQkfCiJCFCTgf7dydEVt8ujS/Uu1kz86ufdRwaMRcvBZAORGdB58LEsLB65WN4
hLRYF7xvcxu6t7FGrIYereaxUAWLA2B/ZnCEdOY94w7s0uaPjHdf4lfHebuZ7T08
iG5ACDvKBjgaFArGfdNYWchXJgbOEg14bGj40/8LuBKQMZASiFSqLPZxoporK9FY
xBw+D080dUWWD5g868TZ3pkM3DXO9bdq22IBKqKOep8CnuKgoDpUvA8dTEY/UDCn
sdOlBUK/Y9zTGVmD/90cO/xkvkV78suqiBnwBSddPzVS0EuiWwrLGu8gaY4EyM/X
7khlbTcMgh4njzUCAE6Tq+TbXSxn86wuOybVY5Y+I99LNdsocI5SIn2nDh2IOi00
4dE/iwO2MatWIOLFBC7pw8Xv4UHZY+WIf3Y/6XjExpllhUkeB6BwZpTr1SXk+cug
q5Dj5i4aGn2LrvQJ57terqUWYyDUBFgXTc4SPOzT5og8CavBgHfrQoFwSnRZ2oyX
xtZhEDI5Pk2j1qTbOhXZ29po4rPNWHMq2HQgM0I+BqQndsoVdkPOFzS2wKkdXjCz
bNYcyanusQARAQABiQI2BBgBCgAgFiEEtPmgEK8o3cfMUQ8rwtnjMpRb0DwFAl/g
Q8gCGwwACgkQwtnjMpRb0Dzh6g//ZjXaWSzKmG5ZS6XJa/ZOokkE2hFOFusWX8Qa
hEwLAnTFEy02dLfV54rKwmu2jHPDKLhE+iYtusvytueZAzVRyQahv0RE4BH8Emqw
gQdBwyJ/L+QhUp/lMdJ6Hh/2ZSZmzU29U24vnY+U+haoB1fLnA3lXgOP59kMLGud
lERR2Vluuc7TcpzvcaRWgrQRU2vSrrBBEp6y07iVKbRM/9yhE/aHJahLbhKh2Dk9
WJvHPnhYJY5yU+Y5vTl3BiW5+EuzMBdPUawOWKhqCq9dswn0GL1g/vlt/bdU/6DO
jECQ6fssTAtDjRClXySsS3X0mh8y8qlGvMPB4anfvOy4+4nUV6IESdJftKn2SMGd
CA3MaQ+S7frWn5v7GIWSC9vumCsiu1JTOugLmbVmu5m5nFsyllavm/k9LtOtswuF
fHM/SlXLFuGBWU6XceqaM2dpP8i5jGz0vIGMhqoFNgXWGO1NhwR1rmeU1CMpnM5e
Wue4h/+mJiuEzuZcmzOcwq3HGMUXO0jZDgLEmlnenO9czhrLuGZaMXGdwnIk0G3O
+SqH36v7blnDh96RXpgaa+ifTHd0qKeoVXVwSq/9jNtHSQrI+NJcTpMhu73xtxhX
UFPr/31+IFLWepC5GDwdu/gQm5E6ntGyxE2p2v76pcjz7SGdXjPFZjqekBveEJuW
fNdY6Ns=
=rdCA
-END PGP PUBLIC KEY BLOCK-

Bug#1042992: micropython FTBFS with gcc 13

[Adrian Bunk]

Source: micropython
Version: 1.19.1+ds-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=micropython=riscv64=1.19.1%2Bds-1=1691093977=0

...
../py/stackctrl.c: In function ‘mp_stack_ctrl_init’:
../py/stackctrl.c:32:32: error: storing the address of local variable 
‘stack_dummy’ in ‘mp_state_ctx.thread.stack_top’ [-Werror=dangling-pointer=]
   32 | MP_STATE_THREAD(stack_top) = (char *)_dummy;
../py/stackctrl.c:31:18: note: ‘stack_dummy’ declared here
   31 | volatile int stack_dummy;
  |  ^~~
In file included from ../py/runtime.h:29,
 from ../py/stackctrl.c:27:
../py/mpstate.h:323:23: note: ‘mp_state_ctx’ declared here
  323 | extern mp_state_ctx_t mp_state_ctx;
  |   ^~~~
cc1: all warnings being treated as errors
make[2]: *** [../py/mkrules.mk:80: build/py/stackctrl.o] Error 1


micropython builds with the following two fixes:
https://github.com/micropython/micropython/commit/f1c6cb7725960487195daa5c5c196fd8d3563811
https://github.com/micropython/micropython/commit/32572439984e5640c6af46fbe7c27400c30112ce

Bug#1040731: marked as done (wslay: autopkgtest failure due to new CMake deprecation warning)

[Debian Bug Tracking System]

Your message dated Thu, 03 Aug 2023 22:29:29 +
with message-id 
and subject line Bug#1040731: fixed in wslay 1.1.1-4
has caused the Debian Bug report #1040731,
regarding wslay: autopkgtest failure due to new CMake deprecation warning
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.)


-- 
1040731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040731
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wslay
Version: 1.1.1-3
Severity: important
User: roehl...@debian.org
Usertags: cmake3.27

Dear maintainer,

your package wslay will soon experience autopkgtest failures because
the new CMake release 3.27 will issue a deprecation warning on stderr
if cmake_minimum_required() asks for compatibility with CMake 3.4 or
older.

You can check for the exact failure on the cmake pseudo-excuses page
from experimental:
https://qa.debian.org/excuses.php?experimental=1=cmake

For a more in-depth discussion, kindly refer to the debian-devel
thread: https://lists.debian.org/debian-devel/2023/06/msg00150.html

Cheers

Timo
--- End Message ---
--- Begin Message ---
Source: wslay
Source-Version: 1.1.1-4
Done: Anton Gladky 

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

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

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated wslay 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, 03 Aug 2023 23:13:19 +0200
Source: wslay
Architecture: source
Version: 1.1.1-4
Distribution: unstable
Urgency: medium
Maintainer: Anton Gladky 
Changed-By: Anton Gladky 
Closes: 873677 1040731
Changes:
 wslay (1.1.1-4) unstable; urgency=medium
 .
   [ Anton Gladky ]
   * [4834d49] Revert "Update debian/.gitlab-ci.yml"
   * [33e6c09] Update watch file format version to 4.
   * [99f2459] Update standards version to 4.6.2, no changes needed.
   * [e3a4a89] Remove unneeded breaks/replaces
 .
   [ Debian Janitor ]
   * [80e2ba6] Apply multi-arch hints.
 + libwslay-dev: Add Multi-Arch: same.
 + libwslay-doc: Add Multi-Arch: foreign.
 .
   [ Pino Toscano ]
   * [988937e] d/rules: do not build the examples on non-Linux (Closes: #873677)
 .
   [ Timo Röhling ]
   * [5d568e2] debian/tests/build1: Bump cmake_minimum_required() for examples
 (Closes: #1040731)
Checksums-Sha1:
 c06ef0d410ca92f9848b81f0dc467b5ab8fe60ee 2073 wslay_1.1.1-4.dsc
 83ce7f945e8b6f2633ff0ed9112b465583e7caa7 7120 wslay_1.1.1-4.debian.tar.xz
 9c5d4c0c5726e8af4f32c3dc97a6a04adc7f88d3 6846 wslay_1.1.1-4_source.buildinfo
Checksums-Sha256:
 6e0f5679af498448ef4fa2022699cb55216d578636e4788f9e68303b69883930 2073 
wslay_1.1.1-4.dsc
 b93ff4729b2f64a617f45fcdf7015fc412ec8ec7513236010c0d33f4352d9fa2 7120 
wslay_1.1.1-4.debian.tar.xz
 013aa4f5ed08ad7b3b08daa57f1c0def43c89ebf25e56aa1c922b473cfbd4d8c 6846 
wslay_1.1.1-4_source.buildinfo
Files:
 d85a8acce68a5b65c9b0ca2caf4555c3 2073 libs optional wslay_1.1.1-4.dsc
 44c0a73cf5973699bb215467c3c7cb04 7120 libs optional wslay_1.1.1-4.debian.tar.xz
 25e72434d4f3e2d5ee13de28b67a4cc7 6846 libs optional 
wslay_1.1.1-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAmTMGPUACgkQ0+Fzg8+n
/wat0Q//XOLiC6xcryfpWzc5A312/3mNFOGKit9HUzCLhJR09WNF2Gxh3D0dnXZ0
EQf0e4xdvd1BR7Y8MlueNw31zNYZX37f/eRkbJ+cUumTJ48WMbz5ySEl6r0CbCoA
QQ20o+nYd9LEO+xUiSrOrQJexC703HWZdK2Yudkn9WsPO6ywGI2A1sgjk8a+Cq3Q
XrYnUJfNvLfsOOKHQ+CEbCXS35rhdhiCkcH1gk5T8kb8ks0NeNxR9GssgOh84I/O
mXH9ZSLvTYzwi3wUo1+kVpf7P+fV5Dpa+zEhkMKd2agcl3BLcHxtzcC6IdI5KKwA
Xv4pECvBGF0EsVgzgJEYVmJ9f/4wyf9C6zR+L4nbgOT7onAl7us89V6f2KQSDsx3
xpp1/Cy3I8kTJR2jCTsTpaskmtQ+Sz1XSt3D4dLKqbHHeIi3GS7SpybjPKBJzbyR
8GAWJx7VDZWWH51D7poaV7pRwmrsg1xW+3cqH+5fRTMhPaYxqaz039MvOWb4oCsA
iG13JNtpxw5TR0fFN6MJFf7jny2VVOARAwiz5uVZnR+m4B7kIaL9J/yoFmsH0Dot
BW+WDvrFPh0g7YHPYbkkEml9qmHstljZoIVbxlI8k0Z+a6J/xnNb/NVGXPbdGukV
9uUq4wSMx10LHpPKQ/SL0XJvwqRNlEMmq/GAkT/Zk+68fk09ebE=
=/arF
-END PGP SIGNATURE End Message ---

Bug#1041076: marked as done (dolphin-emu FTBFS with imgui 1.89.6)

[Debian Bug Tracking System]

Your message dated Thu, 03 Aug 2023 22:20:35 +
with message-id 
and subject line Bug#1041076: fixed in dolphin-emu 5.0-19368+dfsg-2.1
has caused the Debian Bug report #1041076,
regarding dolphin-emu FTBFS with imgui 1.89.6
to be marked as done.

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

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


-- 
1041076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041076
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dolphin-emu
Version: 5.0-19368+dfsg-2
Severity: serious
Tags: ftbfs

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

...
In file included from 
/build/1st/dolphin-emu-5.0-19368+dfsg/Externals/implot/implot/implot_internal.h:39,
 from 
/build/1st/dolphin-emu-5.0-19368+dfsg/Externals/implot/implot/implot_items.cpp:26:
/usr/include/imgui/imgui_internal.h:101:2: error: #error Please '#define 
IMGUI_DEFINE_MATH_OPERATORS' _BEFORE_ including imgui.h!
  101 | #error Please '#define IMGUI_DEFINE_MATH_OPERATORS' _BEFORE_ including 
imgui.h!
  |  ^
In file included from 
/build/1st/dolphin-emu-5.0-19368+dfsg/Externals/implot/implot/implot_internal.h:39,
 from 
/build/1st/dolphin-emu-5.0-19368+dfsg/Externals/implot/implot/implot.cpp:126:
/usr/include/imgui/imgui_internal.h:101:2: error: #error Please '#define 
IMGUI_DEFINE_MATH_OPERATORS' _BEFORE_ including imgui.h!
  101 | #error Please '#define IMGUI_DEFINE_MATH_OPERATORS' _BEFORE_ including 
imgui.h!
  |  ^
...
--- End Message ---
--- Begin Message ---
Source: dolphin-emu
Source-Version: 5.0-19368+dfsg-2.1
Done: Sebastian Ramacher 

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated dolphin-emu 
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, 01 Aug 2023 22:59:04 +0200
Source: dolphin-emu
Architecture: source
Version: 5.0-19368+dfsg-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Sebastian Ramacher 
Closes: 1041076
Changes:
 dolphin-emu (5.0-19368+dfsg-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/patches: Apply upstream patch to fix FTBFS with imgui 1.89.6
 (Closes: #1041076)
Checksums-Sha1:
 312f871c4b34095c70dbf4f3c2199bee3e283dfb 2271 
dolphin-emu_5.0-19368+dfsg-2.1.dsc
 59436db23403433638d1b5b2cc3688289020a2ca 12980 
dolphin-emu_5.0-19368+dfsg-2.1.debian.tar.xz
Checksums-Sha256:
 67665f23925cc9259bb78e34a6df11837a8e1b19a76fd1feca8cd3b0d6abbcd2 2271 
dolphin-emu_5.0-19368+dfsg-2.1.dsc
 001e12d96ef301a85226d14831c2b6f2eb188ae00e622c2bb2c6fa622b5379fc 12980 
dolphin-emu_5.0-19368+dfsg-2.1.debian.tar.xz
Files:
 bdbc77451089717d7aad747802c0fdec 2271 games optional 
dolphin-emu_5.0-19368+dfsg-2.1.dsc
 1c3e8eb5ed72b102c812c52e1dc3c8c7 12980 games optional 
dolphin-emu_5.0-19368+dfsg-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZMl2oAAKCRAhk2s2YA/N
iap3AQDHF/CREYqIRv3yV18HQviE6CkIMJ4jTp6OoJbbDZlz1QD/d6j02pw3rs90
ru9nIQ7iN3ff2ygue5uPsOjvM0iXkQM=
=L+P4
-END PGP SIGNATURE End Message ---

Processed: Re: onetbb 2021.9.0-1 FTBFS on multiple release architectures

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 2021.9.0-2
Bug #1041230 [src:onetbb] onetbb 2021.9.0-1 FTBFS on multiple release 
architectures
Marked as fixed in versions onetbb/2021.9.0-2.

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

Bug#1041230: onetbb 2021.9.0-1 FTBFS on multiple release architectures

[M. Zhou]

Control: fixed -1 2021.9.0-2

I agree.

On Thu, 2023-08-03 at 00:32 +0200, Petter Reinholdtsen wrote:
> [M. Zhou]
> > The issue still exists with armel:
> > https://buildd.debian.org/status/package.php?p=onetbb
> 
> If so, this is a duplicate of 
> https://bugs.debian.org/1042009 >, which is about the armel
> issue,
> and should be closed.
> 

Bug#1040731: wslay: autopkgtest failure due to new CMake deprecation warning

[Anton Gladky]

Hi Timo,

thanks a lot for this upload! I have just prepared a
"normal" update, including your changes and some
others. If you want, you can cancel NMU or it will be
automatically rejected by the system.

Best regards


Anton


Am Di., 1. Aug. 2023 um 11:21 Uhr schrieb Timo Röhling :

> Hi Anton,
>
> On Fri, 21 Jul 2023 21:13:56 +0200 Anton Gladky  wrote:
> > Thanks a lot for the MR and update.
> > I will prepare an update and upload it in one week. If it's ok for you.
> > Otherwise, please NMU.
> I have just uploaded an NMU to DELAYED/5 and pushed the corresponding
> commits to the branch nmu-bug-1040731. Chris' solution is probably
> cleaner (I just hot-patched the CMakeLists.txt in autopkgtest), so
> if you have time this week, feel free to upload your own release,
> and I will cancel my upload.
>
>
> Cheers
> Timo
>
> --
> ⢀⣴⠾⠻⢶⣦⠀   ╭╮
> ⣾⠁⢠⠒⠀⣿⡁   │ Timo Röhling   │
> ⢿⡄⠘⠷⠚⠋⠀   │ 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA │
> ⠈⠳⣄   ╰╯
>

Bug#1037704: marked as done (jigdo: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Thu, 03 Aug 2023 21:09:50 +
with message-id 
and subject line Bug#1037704: fixed in jigdo 0.8.2-1
has caused the Debian Bug report #1037704,
regarding jigdo: ftbfs with GCC-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.)


-- 
1037704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037704
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:jigdo
Version: 0.8.1-1
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/jigdo_0.8.1-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
 EXTRA_CFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security" \
 EXTRA_CXXFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security" \
 EXTRA_LDFLAGS="-Wl,-z,relro"
make[1]: Entering directory '/<>'
test -h gfx -o -d gfx || ln -s "./gfx" gfx
cd src && /usr/bin/make all EXTRA_CFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2 -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security" EXTRA_CXXFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security" EXTRA_LDFLAGS="-Wl,-z,relro"
make[2]: Entering directory '/<>/src'
g++ -Wdate-time -D_FORTIFY_SOURCE=2 -I. -I"." -I"./util" -D_FILE_OFFSET_BITS=64 
-DHAVE_CONFIG_H -DPACKAGE_DATA_DIR="\"/usr/share/jigdo/\"" 
-DPACKAGE_LOCALE_DIR="\"/usr/share/locale\""-O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -W -Wpointer-arith -Wconversion 
-Woverloaded-virtual  -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c "cachefile.cc" -o "cachefile.o"
g++ -Wdate-time -D_FORTIFY_SOURCE=2 -I. -I"." -I"./util" -D_FILE_OFFSET_BITS=64 
-DHAVE_CONFIG_H -DPACKAGE_DATA_DIR="\"/usr/share/jigdo/\"" 
-DPACKAGE_LOCALE_DIR="\"/usr/share/locale\""-O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -W -Wpointer-arith -Wconversion 
-Woverloaded-virtual  -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c "compat.cc" -o "compat.o"
g++ -Wdate-time -D_FORTIFY_SOURCE=2 -I. -I"." -I"./util" -D_FILE_OFFSET_BITS=64 
-DHAVE_CONFIG_H -DPACKAGE_DATA_DIR="\"/usr/share/jigdo/\"" 
-DPACKAGE_LOCALE_DIR="\"/usr/share/locale\""-O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -W -Wpointer-arith -Wconversion 
-Woverloaded-virtual  -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c "jigdo-file-cmd.cc" -o "jigdo-file-cmd.o"
g++ -Wdate-time -D_FORTIFY_SOURCE=2 -I. -I"." -I"./util" -D_FILE_OFFSET_BITS=64 
-DHAVE_CONFIG_H -DPACKAGE_DATA_DIR="\"/usr/share/jigdo/\"" 
-DPACKAGE_LOCALE_DIR="\"/usr/share/locale\""-O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -W -Wpointer-arith -Wconversion 
-Woverloaded-virtual  -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c "jigdo-file.cc" -o "jigdo-file.o"
g++ -Wdate-time -D_FORTIFY_SOURCE=2 -I. -I"." -I"./util" -D_FILE_OFFSET_BITS=64 
-DHAVE_CONFIG_H -DPACKAGE_DATA_DIR="\"/usr/share/jigdo/\"" 

Bug#1037628: marked as done (drumgizmo: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Thu, 03 Aug 2023 21:07:21 +
with message-id 
and subject line Bug#1037628: fixed in drumgizmo 0.9.20-2
has caused the Debian Bug report #1037628,
regarding drumgizmo: ftbfs with GCC-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.)


-- 
1037628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037628
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:drumgizmo
Version: 0.9.20-1
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/drumgizmo_0.9.20-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
libtool: link: g++ -DUI_X11 -I.. -I../src -I../hugin -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -ffast-math -std=c++11 -DDISABLE_HUGIN -Wl,-z -Wl,relro 
-Wl,-z -Wl,now -o plugingui plugingui-testmain.o plugingui-hugin.o  
./.libs/libplugingui.a -lX11 -lXext ../src/.libs/libdg.a -lsndfile -lpthread 
../src/.libs/libnls.a -latomic -lrt
make[5]: Leaving directory '/<>/plugingui'
make[4]: Leaving directory '/<>/plugingui'
make[3]: Leaving directory '/<>/plugingui'
Making all in plugin
make[3]: Entering directory '/<>/plugin'
Making all in vst
make[4]: Entering directory '/<>/plugin/vst'
make[4]: Nothing to be done for 'all'.
make[4]: Leaving directory '/<>/plugin/vst'
make[4]: Entering directory '/<>/plugin'
g++ -DHAVE_CONFIG_H -I. -I..-I../plugin/plugingizmo -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -ffast-math 
-std=c++11 -DDISABLE_HUGIN -c -o ttlgen-ttlgen.o `test -f 
'../plugin/plugingizmo/ttlgen.cc' || echo './'`../plugin/plugingizmo/ttlgen.cc
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..   
-Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -ffast-math -c -o drumgizmo_la-hugin.lo `test -f 
'../hugin/hugin.c' || echo './'`../hugin/hugin.c
/bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I..   
-Wdate-time -D_FORTIFY_SOURCE=2 -DLV2 
-DLV2_PLUGIN_URI=\"http://drumgizmo.org/lv2\;  -fvisibility=hidden 
-I../zita-resampler/libs  -I/usr/include/opus -I/usr/include/x86_64-linux-gnu  
-I../plugin/plugingizmo -I../ -I../plugingui -I../src -I../hugin -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -ffast-math -std=c++11 -DDISABLE_HUGIN -c -o 
drumgizmo_la-midievent.lo `test -f '../plugin/plugingizmo/midievent.cc' || echo 
'./'`../plugin/plugingizmo/midievent.cc
/bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I..   
-Wdate-time -D_FORTIFY_SOURCE=2 -DLV2 
-DLV2_PLUGIN_URI=\"http://drumgizmo.org/lv2\;  -fvisibility=hidden 
-I../zita-resampler/libs  -I/usr/include/opus -I/usr/include/x86_64-linux-gnu  
-I../plugin/plugingizmo -I../ -I../plugingui -I../src -I../hugin -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -ffast-math -std=c++11 -DDISABLE_HUGIN -c -o 
drumgizmo_la-pluginlv2.lo `test -f '../plugin/plugingizmo/pluginlv2.cc' || echo 
'./'`../plugin/plugingizmo/pluginlv2.cc
/bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I..   
-Wdate-time -D_FORTIFY_SOURCE=2 -DLV2 
-DLV2_PLUGIN_URI=\"http://drumgizmo.org/lv2\;  -fvisibility=hidden 
-I../zita-resampler/libs  -I/usr/include/opus -I/usr/include/x86_64-linux-gnu  
-I../plugin/plugingizmo -I../ -I../plugingui 

Bug#1039710: debian-installer: Grub installation fails and /var/log/syslog is empty

[Steve McIntyre]

On Wed, Jul 12, 2023 at 11:15:57AM +0200, Cyril Brulebois wrote:
>Hi Michael,
>
>Cyril Brulebois  (2023-06-28):
>> Control: reassign -1 busybox-udeb 1:1.36.1-3
>
>[…]
>
>> With a local build, confirmed -3 is buggy, and that reverting only
>> busybox-udeb to -1 is sufficient to restore syslog support in the
>> installer.
>> 
>> Reassigning there; the GRUB thing can be filed separately once we have
>> actual information via syslog.
>
>A fix would be appreciated, we've got reports piling up about things we
>have no logs for.

After weeks with this breakage, I've just uploaded a minimal NMU to
fix it, reverting the syslog changes since -1. I've buit and tested
successfully locally.

Here's the NMU diff.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
You raise the blade, you make the change... You re-arrange me 'til I'm sane...
diff -Nru busybox-1.36.1/debian/changelog busybox-1.36.1/debian/changelog
--- busybox-1.36.1/debian/changelog 2023-06-14 22:01:54.0 +0100
+++ busybox-1.36.1/debian/changelog 2023-08-03 21:22:44.0 +0100
@@ -1,3 +1,11 @@
+busybox (1:1.36.1-3.1) unstable; urgency=medium
+
+  * NMU
+  * Revert recent changes that have broken syslogd in d-i.
+Closes: #1039710
+
+ -- Steve McIntyre <93...@debian.org>  Thu, 03 Aug 2023 21:22:44 +0100
+
 busybox (1:1.36.1-3) unstable; urgency=medium
 
   * syslogd-avoid-nulling-devlog.patch - fix overriding dev/log
diff -Nru busybox-1.36.1/debian/patches/series 
busybox-1.36.1/debian/patches/series
--- busybox-1.36.1/debian/patches/series2023-06-14 21:55:08.0 
+0100
+++ busybox-1.36.1/debian/patches/series2023-08-03 21:22:44.0 
+0100
@@ -14,6 +14,7 @@
 platform-linux.diff
 fix-non-linux-build.patch
 #
-syslogd-decrease-stack-usage-50-bytes.patch
-syslogd-daemonize-after-init-make-errs-visible.patch
-syslogd-avoid-nulling-devlog.patch
+syslogd-fork-after-init-not-before.patch
+#syslogd-decrease-stack-usage-50-bytes.patch
+#syslogd-daemonize-after-init-make-errs-visible.patch
+#syslogd-avoid-nulling-devlog.patch
diff -Nru 
busybox-1.36.1/debian/patches/syslogd-fork-after-init-not-before.patch 
busybox-1.36.1/debian/patches/syslogd-fork-after-init-not-before.patch
--- busybox-1.36.1/debian/patches/syslogd-fork-after-init-not-before.patch  
1970-01-01 01:00:00.0 +0100
+++ busybox-1.36.1/debian/patches/syslogd-fork-after-init-not-before.patch  
2023-08-03 21:22:44.0 +0100
@@ -0,0 +1,58 @@
+From: Michael Tokarev 
+Date: Tue, 6 Jun 2023 17:08:18 +0300
+Subject: [PATCH] syslogd: fork after init on a regular system, not before
+
+Current syslogd performs all init after daemonizing, meanwhile
+main process exits successfully. This means any errors during init
+will not be even shown up because at this time the process has its
+stderr redirected to /dev/null already.
+
+On a MMU system, delay daemonizing to after init.
+On non-MMU system, keep current code.
+
+Signed-off-by: Michael Tokarev 
+---
+ sysklogd/syslogd.c | 13 -
+ 1 file changed, 12 insertions(+), 1 deletion(-)
+
+diff --git a/sysklogd/syslogd.c b/sysklogd/syslogd.c
+index 6ddfd771a..2f9a727cd 100644
+--- a/sysklogd/syslogd.c
 b/sysklogd/syslogd.c
+@@ -1025,7 +1025,6 @@ static void do_syslogd(void)
+   signal(SIGALRM, do_mark);
+   alarm(G.markInterval);
+ #endif
+-  xmove_fd(create_socket(), STDIN_FILENO);
+ 
+   if (option_mask32 & OPT_circularlog)
+   ipcsyslog_init();
+@@ -1033,6 +1032,16 @@ static void do_syslogd(void)
+   if (option_mask32 & OPT_kmsg)
+   kmsg_init();
+ 
++  {
++  int fd = create_socket();
++#if BB_MMU
++  if (!(option_mask32 & OPT_nofork)) {
++  bb_daemonize(DAEMON_CHDIR_ROOT);
++  }
++#endif
++  xmove_fd(fd, STDIN_FILENO);
++  }
++
+   timestamp_and_log_internal("syslogd started: BusyBox v" BB_VER);
+   write_pidfile_std_path_and_ext("syslogd");
+ 
+@@ -1179,9 +1188,11 @@ int syslogd_main(int argc UNUSED_PARAM, char **argv)
+   G.hostname = safe_gethostname();
+   *strchrnul(G.hostname, '.') = '\0';
+ 
++#if !BB_MMU
+   if (!(opts & OPT_nofork)) {
+   bb_daemonize_or_rexec(DAEMON_CHDIR_ROOT, argv);
+   }
++#endif
+ 
+   do_syslogd();
+   /* return EXIT_SUCCESS; */

Processed: tagging 1042937

[Debian Bug Tracking System]

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

> tags 1042937 + ftbfs
Bug #1042937 [src:cyrus-sasl2] libsasl2-dev should depend on libssl-dev
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#1042978: Tests invalid package upgrades

[Paul Gevers]

Control: reassign -1 release.debian.org

Hi Ben,

On 03-08-2023 18:01, Ben Hutchings wrote:

ci.debian.net must therefore also test updating the binaries from all
these source packages together, not just those built from linux.


But ci.debian.net just does what it's been asked to do by the client, in 
this case britney. So, if anything it's britney2 that needs to be 
changed to support this. But, britney2 tries to deduce what needs to be 
tested together from the package relations. Normally, what you're seeing 
here is the result of a test where the signed packages haven't been 
build yet. britney retries tests after 24 hours and normally it retries 
with linux-signed-* in the list of pinned packages as you can see in the 
dkms history. The question that now arises is why it doesn't do that now.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: Bug#1042978: Tests invalid package upgrades

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 release.debian.org
Bug #1042978 [debci] Tests invalid package upgrades
Bug reassigned from package 'debci' to 'release.debian.org'.
Ignoring request to alter found versions of bug #1042978 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1042978 to the same values 
previously set

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

Bug#1042983: squeekboard - rust gtk stack update.

[Arnaud Ferraris]

Hi Peter,

Le 03/08/2023 à 19:27, Peter Green a écrit :

Package: squeekboard
Version: 1.22.0-3
Severity: serious

The rust gtk stack is currently being updated in Debian,
squeekboard needs a small patch

Please test that squeekboard works with this patch and
if-so apply it.


Thanks for the patch, it works as expected but tests seem to fail on 
i386. I'll check what is going wrong there and upload as soon as this 
issue is fixed.


Cheers,
Arnaud



___
Debian-on-mobile-maintainers mailing list
debian-on-mobile-maintain...@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-on-mobile-maintainers

Bug#1037567: abseil: ftbfs with GCC-13

[Aurelien Jarno]

Hi,

On 2023-08-02 14:27, Benjamin Barenblat wrote:
> I’ve been procrastinating on starting the transition because of some
> lingering MIPS issues. I think they’ve all been sorted out, and I just
> uploaded my latest work to experimental. If that passes the buildds,
> I’ll request a transition slot and do the transition as quickly as
> possible.
> 
> If waiting on the transition is going to unacceptably delay the riscv64
> bootstrap, please let me know. I think I know which patches I would have
> to backport to 20220623 to get it to build with GCC 13, so I may be able
> to fix this in unstable before the transition completes.

It was not clear when we're going to need abseil when sending the
initial mail, but it's not clear that we'll need to really soon for
building llvm-toolchain-XX through both libgrpc++-dev and
libctypes-ocaml.

Therefore it would be great if you can fix that in unstable before the
transition. From what I understand it should be this patch:
https://github.com/abseil/abseil-cpp/commit/4eef16170014f75f4291ae335a271900f89eaedf

Alternatively it could also be changing the compiler to gcc-12.

Thanks
Aurelien

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

Bug#1042050: meson: FTBFS: ./b 52a78b9866/../test cases/failing build/2 hidden symbol/bobuser.c:4:(.text.startup+0x3): undefined reference to `hidden_function'

[Shmerl]

On Tue, 1 Aug 2023 22:55:02 +0300 Jussi Pakkanen  wrote:
> On Wed, 26 Jul 2023 at 00:16, Lucas Nussbaum  wrote:
>
> This is actually a bug in gobject-introspection. It has already been
> fixed upstream. Dunno what the schedule is for getting that into a
> release and on to Debian.
>

Can this be applied for now as a patch until upstream makes a new tag
(which can be a while)?

https://gitlab.gnome.org/GNOME/gobject-introspection/-/commit/bf96a92ef263820d40e233814a46932cae00db41

Stuck Meson is blocking a bunch of packages from being updated in testing.

Regards,

Shmerl.

Bug#1042984: golang-1.19 should not be in trixie

[Adrian Bunk]

Source: golang-1.19
Severity: serious
Tags: trixie sid

With 1.20 already being the default, the obsolete golang-1.19
should be removed from trixie.

This bug will trigger the autoremoval.

Bug#1041850: marked as done (phoc: FTBFS with wlroots 0.16.)

[Debian Bug Tracking System]

Your message dated Thu, 03 Aug 2023 18:53:34 +
with message-id 
and subject line Bug#1041850: fixed in phoc 0.30.0+ds-1
has caused the Debian Bug report #1041850,
regarding phoc: FTBFS with wlroots 0.16.
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.)


-- 
1041850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041850
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: phoc
Version: 0.29.0+ds-1
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=phoc=amd64=0.29.0%2Bds-1%2Bb1=1690184504=0

Dependency wlroots found: NO found 0.16.2 but need: '== 0.15.1'
Dependency lookup for wlroots with method 'pkgconfig' failed: Invalid version, 
need 'wlroots' ['== 0.15.1'] found '0.16.2'.
CMake binary for 1 is not cached
CMake binary missing from cross or native file, or env var undefined.
Trying a default CMake fallback at cmake
Did not find CMake 'cmake'
Found CMake: NO
Dependency lookup for wlroots with method 'cmake' failed: CMake binary for 
machine 1 not found. Giving up.
Run-time dependency wlroots found: NO 

../meson.build:72:18: ERROR: Dependency lookup for wlroots with method 
'pkgconfig' failed: Invalid version, need 'wlroots' ['== 0.15.1'] found 
'0.16.2'.
dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson setup 
.. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
--localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dembed-wlroots=disabled 
-Dman=true returned exit code 1
make[1]: *** [debian/rules:9: override_dh_auto_configure] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: binary-arch] Error 2


Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: phoc
Source-Version: 0.30.0+ds-1
Done: Guido Günther 

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

Debian distribution maintenance software
pp.
Guido Günther  (supplier of updated phoc 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, 03 Aug 2023 18:00:27 +0200
Source: phoc
Architecture: source
Version: 0.30.0+ds-1
Distribution: unstable
Urgency: medium
Maintainer: DebianOnMobile Maintainers 

Changed-By: Guido Günther 
Closes: 1041155 1041850
Changes:
 phoc (0.30.0+ds-1) unstable; urgency=medium
 .
   * New upstream release
 Closes: #1041850
   * d/control: Bump wlroots dependency
   * d/gbp.conf: Drop duplicate upstream-vcs-tag
   * Update filter settings now the upstream tarball is
 generted via --include-subprojects
   * docs: Install NEWS
 Closes: #1041155
Checksums-Sha1:
 b01b2e3561fc24abf1903a2339769331ae966545 2527 phoc_0.30.0+ds-1.dsc
 0f05ebc942e8179fc15aef86353b2cd4065019ef 215388 phoc_0.30.0+ds.orig.tar.xz
 334f23e26aaeaecba0fd46f91ca2036774282bfb 13072 phoc_0.30.0+ds-1.debian.tar.xz
 e5e062fa68175be3d9f9f51adb3e328fe5ce0e31 16967 phoc_0.30.0+ds-1_amd64.buildinfo
Checksums-Sha256:
 6d7617bb50fe0c64b049f90743e4d5e4062fe57c5d4fa306e8ab1785e74699c5 2527 
phoc_0.30.0+ds-1.dsc
 81353ed9682d1122d41b8aa0039b6c10cca767ce732e4fbb53bc7bdce67df9b4 215388 
phoc_0.30.0+ds.orig.tar.xz
 9c01e1ee1d369fec0929949917efbd85f13608e4ce145ce93b84ca07a984be85 13072 
phoc_0.30.0+ds-1.debian.tar.xz
 6205ece2e44836bdd95033742c80f2e9214039f19c67fdcf96d169e8babe5562 16967 
phoc_0.30.0+ds-1_amd64.buildinfo
Files:
 a31ef4d076d9e3700de7fb6d39a94bef 2527 x11 optional phoc_0.30.0+ds-1.dsc
 a18492444c0c056e72f8edcb002f7db0 215388 x11 optional phoc_0.30.0+ds.orig.tar.xz
 8a8091d24a9415acfd995c599d00f838 13072 x11 optional 
phoc_0.30.0+ds-1.debian.tar.xz
 b04d3e7fd074824e119ae450adf9edd4 16967 x11 optional 
phoc_0.30.0+ds-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEY/bM35YinQkoayrDJb+GUkr8weMFAmTL6BwACgkQJb+GUkr8
wePBNA/8DkiVsbFBBvERFodoS8+h+plGfjl78XtW7CaIMD0yU58PYxhvS3etEy/z
CkXF/oKF1bhpRd7F0721j670vshMJPTwBCiTzuvjDLSd7YrN21i94mx0P7UsXl2o
YFD2An1ZC9jy6JyKj8iPuGCyvYgHoKUtqowev+QBqCwt3YPjOSZf3iyAZKj1Q8+d

Bug#1042957: marked as done (iraf-mscred: FTBFS with iraf 2.17.1)

[Debian Bug Tracking System]

Your message dated Thu, 03 Aug 2023 18:51:10 +
with message-id 
and subject line Bug#1042957: fixed in iraf-mscred 5.05+2018.07.09-2
has caused the Debian Bug report #1042957,
regarding iraf-mscred: FTBFS with iraf 2.17.1
to be marked as done.

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

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


-- 
1042957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042957
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: iraf-mscred
Version: 5.05+2018.07.09-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear maintainer,

iraf-fitsutil FTBFS on amd64, this seems to be related to the upload of iraf
2.17.1. From my build log:

| $call libsf.a
| warning: library `libsf.a' not found
| /usr/lib/iraf/unix/bin/xc.e -c -w -p mscred rngranges.x stfgraph.x 
stfprofile.x t_starfocus.x
| ar r /<>/bin/libsf.a rngranges.o stfgraph.o stfprofile.o 
t_starfocus.o
| ar: creating /<>/bin/libsf.a
| ranlib /<>/bin/libsf.a
| Updated 4 files in libsf.a
| check file `libsf.a' into `mscbin$'
| mkpkg[4]: Leaving directory `/<>/src/mscdisplay/src/starfocus/'
| mkpkg[3]: Leaving directory `/<>/src/mscdisplay/src/'
| mkpkg[2]: Leaving directory `/<>/src/mscdisplay/'
| mkpkg[1]: Leaving directory `/<>/src/'
| $call lfinder@src
| mkpkg[1]: Entering directory `/<>/src/'
| $call lfinder@mscfinder
| mkpkg[2]: Entering directory `/<>/src/mscfinder/'
| check out file `libfinder.a = /<>/bin/libfinder.a'
| $call libfinder.a
| warning: library `libfinder.a' not found
| mkpkg[3]: Entering directory `/<>/src/mscfinder/select/'
| /usr/lib/iraf/unix/bin/xc.e -c -w -p mscred select.x allrows.x change.x mjd.x 
tbleval.x tblterm.x
| ar r /<>/bin/libfinder.a select.o allrows.o change.o mjd.o 
tbleval.o tblterm.o
| ar: creating /<>/bin/libfinder.a
| mkpkg[3]: Leaving directory `/<>/src/mscfinder/select/'
| /usr/lib/iraf/unix/bin/xc.e -c -w -p mscred t_tpeak.x
| ar r /<>/bin/libfinder.a t_tpeak.o
| ranlib /<>/bin/libfinder.a
| Updated 7 files in libfinder.a
| check file `libfinder.a' into `mscbin$'
| mkpkg[2]: Leaving directory `/<>/src/mscfinder/'
| mkpkg[1]: Leaving directory `/<>/src/'
| $call update@src
| mkpkg[1]: Entering directory `/<>/src/'
| $call update@ccdred
| mkpkg[2]: Entering directory `/<>/src/ccdred/'
| $call update@src
| mkpkg[3]: Entering directory `/<>/src/ccdred/src/'
| $call update@combine
| mkpkg[4]: Entering directory `/<>/src/ccdred/src/combine/'
| $call relink
| check out file `x_combine.o = /<>/bin/x_combine.o'
| /usr/lib/iraf/unix/bin/xc.e -c -w -p mscred x_combine.x
| /usr/lib/iraf/unix/bin/xc.e -Nz -p mscred x_combine.o -lcombine -limc 
-lccdred -lmscred -lxtools -lcurfit -lsurfit -lgsurfit -liminterp -lnlfit 
-lslalib -lncar -lgks -o xx_combine.e
| check file `x_combine.o' into `mscbin$'
| $call install
| move `xx_combine.e' to `mscbin$x_combine.e'
| mkpkg[4]: Leaving directory `/<>/src/ccdred/src/combine/'
| mkpkg[3]: Leaving directory `/<>/src/ccdred/src/'
| $call relink
| check out file `x_ccdred.o = /<>/bin/x_ccdred.o'
| /usr/lib/iraf/unix/bin/xc.e -c -w -p mscred x_ccdred.x
| /usr/lib/iraf/unix/bin/xc.e -Nz -p mscred  x_ccdred.o -lccdred -limc -lxtools 
-lcurfit -lgsurfit -lncar -lgks -o xx_ccdred.e
| check file `x_ccdred.o' into `mscbin$'
| $call install
| move `xx_ccdred.e' to `mscbin$x_ccdred.e'
| mkpkg[2]: Leaving directory `/<>/src/ccdred/'
| $call update@mscdisplay
| mkpkg[2]: Entering directory `/<>/src/mscdisplay/'
| $call relink
| $call mscdisplay
| check out file `x_mscdisplay.o = /<>/bin/x_mscdisplay.o'
| /usr/lib/iraf/unix/bin/xc.e -c -w -p mscred x_mscdisplay.x
| src/mscdisplay/mkpkg:27: error: file `imdwcsver.x' not found
| mkpkg[2]: Leaving directory `/<>/src/mscdisplay/'
| make[1]: *** [debian/rules:15: override_dh_auto_build] Error 1
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:5: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
| 

| Build finished at 2023-08-03T09:36:22Z
| 
| Finished
| 
| 
| 
| 
+--+
| | Cleanup 
 |
| 
+--+
| 
| Purging /<>
| Not cleaning session: cloned chroot in use
| I: 71killgpgagent: No /usr/bin/gpg-agent found running; none killed.
| E: Build failure (dpkg-buildpackage died)
| 
| 

Bug#1042956: marked as done (iraf-fitsutil: FTBFS with iraf 2.17.1)

[Debian Bug Tracking System]

Your message dated Thu, 03 Aug 2023 18:50:58 +
with message-id 
and subject line Bug#1042956: fixed in iraf-fitsutil 2018.07.06-5
has caused the Debian Bug report #1042956,
regarding iraf-fitsutil: FTBFS with iraf 2.17.1
to be marked as done.

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

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


-- 
1042956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042956
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: iraf-fitsutil
Version: 2018.07.06-4
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear maintainer,

iraf-fitsutil FTBFS on amd64, this seems to be related to the upload of iraf
2.17.1. From my build log:

| dpkg-buildpackage
| -
| 
| Command: dpkg-buildpackage --sanitize-env -us -uc -mAurelien Jarno 
 -eAurelien Jarno  -rfakeroot
| dpkg-buildpackage: info: source package iraf-fitsutil
| dpkg-buildpackage: info: source version 2018.07.06-4
| dpkg-buildpackage: info: source distribution unstable
|  dpkg-source --before-build .
| dpkg-buildpackage: info: host architecture amd64
|  fakeroot debian/rules clean
| dh clean
|dh_clean
|  dpkg-source -b .
| dpkg-source: info: using source format '3.0 (quilt)'
| dpkg-source: info: building iraf-fitsutil using existing 
./iraf-fitsutil_2018.07.06.orig.tar.gz
| dpkg-source: info: using patch list from debian/patches/series
| dpkg-source: info: building iraf-fitsutil in 
iraf-fitsutil_2018.07.06-4.debian.tar.xz
| dpkg-source: info: building iraf-fitsutil in iraf-fitsutil_2018.07.06-4.dsc
|  debian/rules build
| dh build
|dh_update_autotools_config
|dh_autoreconf
|debian/rules override_dh_auto_configure
| make[1]: Entering directory '/<>'
| rm -rf bin
| mkdir bin
| make[1]: Leaving directory '/<>'
|debian/rules override_dh_auto_build
| make[1]: Entering directory '/<>'
| mkpkg -p fitsutil
| hlib$mkpkg.inc:5: warning: macro `IRAFARCH' not found
| !clear;date
| TERM environment variable not set.
| Thu Aug  3 09:30:34 UTC 2023
| $call update
| $call lib
| = LIB =
| 
| $call update@lib
| mkpkg[1]: Entering directory `/<>/lib/'
| $call install@cfitsio
| lib/mkpkg:14: error: cannot access subdirectory `cfitsio'
| mkpkg[1]: Leaving directory `/<>/lib/'
| make[1]: *** [debian/rules:19: override_dh_auto_build] Error 1
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:5: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
| 

| Build finished at 2023-08-03T09:30:34Z


Regards
Aurelien
--- End Message ---
--- Begin Message ---
Source: iraf-fitsutil
Source-Version: 2018.07.06-5
Done: Ole Streicher 

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

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated iraf-fitsutil 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, 03 Aug 2023 19:35:23 +0200
Source: iraf-fitsutil
Architecture: source
Version: 2018.07.06-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Astro Team 
Changed-By: Ole Streicher 
Closes: 1042956
Changes:
 iraf-fitsutil (2018.07.06-5) unstable; urgency=medium
 .
   * Don't try to install cfitsio (Closes: #1042956)
   * Push dh-compat to 13. No changes needed
   * Push Standards-Version to 4.6.2. No changes needed.
Checksums-Sha1:
 1cf4a71a70057a734029c507a61181205d24ee15 2005 iraf-fitsutil_2018.07.06-5.dsc
 e55534ba29387ca5241c08159def96739b8a5b9f 10224 
iraf-fitsutil_2018.07.06-5.debian.tar.xz
Checksums-Sha256:
 9cc4a1e74670b36c3b896cfa02707357024bcca6c6dcf8ff64cb5b441c3919ac 2005 
iraf-fitsutil_2018.07.06-5.dsc
 02e5610fa14ffa8c4f57cae0e9b9a394fd88dc41347583648cfc864c8f6b2c42 10224 
iraf-fitsutil_2018.07.06-5.debian.tar.xz
Files:
 451f839d8385e4bf4ce729050befcc95 2005 science optional 
iraf-fitsutil_2018.07.06-5.dsc
 3b99952de7932fdf4576a1b906fbd3b3 10224 science optional 
iraf-fitsutil_2018.07.06-5.debian.tar.xz

Processed: affects 1042937

[Debian Bug Tracking System]

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

> affects 1042937 src:openldap
Bug #1042937 [src:cyrus-sasl2] libsasl2-dev should depend on libssl-dev
Added indication that 1042937 affects src:openldap
> thanks
Stopping processing here.

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

Processed: tagging 1038711

[Debian Bug Tracking System]

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

> tags 1038711 + pending
Bug #1038711 {Done: Paul Gevers } [src:beaker] src:beaker: 
fails to migrate to testing for too long: FTBFS
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:svt-av1

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:svt-av1
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1041302 (http://bugs.debian.org/1041302)
> # Bug title: svt-av1: breaks ABI without SONAME bump
> #  * https://gitlab.com/AOMediaCodec/SVT-AV1/-/issues/2095
> #  * remote status changed: opened -> closed
> #  * closed upstream
> tags 1041302 + fixed-upstream
Bug #1041302 [src:svt-av1] svt-av1: breaks ABI without SONAME bump
Added tag(s) fixed-upstream.
> usertags 1041302 - status-opened
Usertags were: status-opened.
There are now no usertags set.
> usertags 1041302 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:python-w3lib

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:python-w3lib
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1042345 (http://bugs.debian.org/1042345)
> # Bug title: python-w3lib: FTBFS: dh_auto_test: error: pybuild --test 
> --test-pytest -i python{version} -p 3.11 returned exit code 13
> #  * https://github.com/scrapy/w3lib/issues/212
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 1042345 + fixed-upstream
Bug #1042345 [src:python-w3lib] python-w3lib: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Added tag(s) fixed-upstream.
> usertags 1042345 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#1042983: squeekboard - rust gtk stack update.

[Peter Green]

Package: squeekboard
Version: 1.22.0-3
Severity: serious

The rust gtk stack is currently being updated in Debian,
squeekboard needs a small patch

Please test that squeekboard works with this patch and
if-so apply it.diff -Nru squeekboard-1.22.0/debian/changelog 
squeekboard-1.22.0/debian/changelog
--- squeekboard-1.22.0/debian/changelog 2023-07-01 15:14:45.0 +
+++ squeekboard-1.22.0/debian/changelog 2023-08-03 16:41:53.0 +
@@ -1,3 +1,10 @@
+squeekboard (1.22.0-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update for gtk-rs 0.17.
+
+ -- Peter Michael Green   Thu, 03 Aug 2023 16:41:53 +
+
 squeekboard (1.22.0-3) unstable; urgency=medium
 
   * debian: update build dependencies.
diff -Nru squeekboard-1.22.0/debian/control squeekboard-1.22.0/debian/control
--- squeekboard-1.22.0/debian/control   2023-07-01 15:14:45.0 +
+++ squeekboard-1.22.0/debian/control   2023-08-03 16:39:01.0 +
@@ -17,11 +17,11 @@
  librust-aho-corasick-dev,
  librust-bitflags-1-dev (>= 1.0),
  librust-clap-4+std-dev (>= 4.0),
- librust-gio+v2-58-dev (>= 0.16),
- librust-glib+v2-58-dev (>= 0.16),
- librust-glib-sys-dev (>= 0.16),
- librust-gtk+v3-24-dev (>= 0.16),
- librust-gtk-sys-dev (>= 0.16),
+ librust-gio+v2-58-dev (>= 0.17),
+ librust-glib+v2-58-dev (>= 0.17),
+ librust-glib-sys-dev (>= 0.17),
+ librust-gtk+v3-24-dev (>= 0.17),
+ librust-gtk-sys-dev (>= 0.17),
  librust-maplit-1-dev (>= 1.0),
  librust-serde-derive-1-dev (>= 1.0),
  librust-serde-yaml-0.8-dev (>= 0.8),
diff -Nru squeekboard-1.22.0/debian/patches/0005-gtk-rs-0.17.patch 
squeekboard-1.22.0/debian/patches/0005-gtk-rs-0.17.patch
--- squeekboard-1.22.0/debian/patches/0005-gtk-rs-0.17.patch1970-01-01 
00:00:00.0 +
+++ squeekboard-1.22.0/debian/patches/0005-gtk-rs-0.17.patch2023-08-03 
16:41:53.0 +
@@ -0,0 +1,56 @@
+Index: squeekboard-1.22.0/Cargo.deps.newer
+===
+--- squeekboard-1.22.0.orig/Cargo.deps.newer
 squeekboard-1.22.0/Cargo.deps.newer
+@@ -10,30 +10,30 @@ zvariant_derive = "2.10.*"
+ xkbcommon = { version = "0.5.*", features = ["wayland"] }
+ 
+ [dependencies.cairo-rs]
+-version = "0.16.*"
++version = "0.17.*"
+ 
+ [dependencies.cairo-sys-rs]
+-version = "0.16.*"
++version = "0.17.*"
+ 
+ [dependencies.gdk]
+-version = "0.16.*"
++version = "0.17.*"
+ 
+ [dependencies.gio]
+-version = "0.16.*"
++version = "0.17.*"
+ features = ["v2_58"]
+ 
+ [dependencies.glib]
+-version = "0.16.*"
++version = "0.17.*"
+ features = ["v2_58"]
+ 
+ [dependencies.glib-sys]
+-version = "0.16.*"
++version = "0.17.*"
+ features = ["v2_58"]
+ 
+ [dependencies.gtk]
+-version = "0.16.*"
++version = "0.17.*"
+ features = ["v3_24"]
+ 
+ [dependencies.gtk-sys]
+-version = "0.16.*"
++version = "0.17.*"
+ features = ["v3_24"]
+Index: squeekboard-1.22.0/src/popover.rs
+===
+--- squeekboard-1.22.0.orig/src/popover.rs
 squeekboard-1.22.0/src/popover.rs
+@@ -326,7 +326,7 @@ pub fn show(
+ let layout_action = gio::SimpleAction::new_stateful(
+ "layout",
+ Some(current_layout_name.to_variant().type_()),
+-_layout_name.to_variant()
++current_layout_name.to_variant()
+ );
+ 
+ let menu_inner = menu.clone();
diff -Nru squeekboard-1.22.0/debian/patches/series 
squeekboard-1.22.0/debian/patches/series
--- squeekboard-1.22.0/debian/patches/series2023-07-01 15:14:45.0 
+
+++ squeekboard-1.22.0/debian/patches/series2023-08-03 16:40:41.0 
+
@@ -2,3 +2,4 @@
 0002-src-popover-fix-build-with-newer-gtk-rs.patch
 0003-src-style-fix-build-with-newer-gtk-rs.patch
 0004-Cargo.-use-xkbcommon-v0.5.patch
+0005-gtk-rs-0.17.patch

Bug#1042982: yaru-theme-gnome-shell: Broken with gnome-shell 43

[Jeremy Bícha]

Package: yaru-theme-gnome-shell
Version: 23.04.4-1
Severity: serious

Yaru 23.04 was designed for GNOME Shell 44 but Debian still only has
GNOME Shell 43. This makes the theme broken for users of Debian
Testing and Unstable currently.

How can we coordinate this better in the future?

It's potentially especially challenging every 2 years when Debian
freezes and the GNOME team delays switching to the new GNOME until the
Debian Stable .1 release.

Even the non-GNOME Shell parts might have been broken too but the new
gtk4 and libadwaita landed in Testing last week so it's at least not
broken any more.

Thank you,
Jeremy Bícha

Bug#1037804: marked as done (openmsx: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Thu, 03 Aug 2023 17:05:39 +
with message-id 
and subject line Bug#1037804: fixed in openmsx 19.0-1
has caused the Debian Bug report #1037804,
regarding openmsx: ftbfs with GCC-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.)


-- 
1037804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:openmsx
Version: 18.0-1
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/openmsx_18.0-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
  libvorbis:version unknown
  OpenGL:   version 4.6
  SDL2: version 2.26.5
  SDL2_ttf: version 2.20.1
  Tcl:  version 8.6.13
  zlib: version 1.2.13

Components overview:
  Emulation core:   yes
  GL renderer:  yes
  Laserdisc:yes
  ALSA MIDI:yes

Customisable options:
  Install to/usr
  (you can edit these in build/custom.mk)

All required and optional components can be built.

If the detected libraries differ from what you think is installed on this 
system, please check the log file: derived/x86_64-linux-debian/config/probe.log

touch derived/x86_64-linux-debian/config/probed_defs.mk
python3 build/components2defs.py 
derived/x86_64-linux-debian/config/components_defs.mk 
derived/x86_64-linux-debian/config/probed_defs.mk
Creating derived/x86_64-linux-debian/config/components_defs.mk...
touch derived/x86_64-linux-debian/config/components_defs.mk
Using Python: python3
Build configuration:
  Platform: x86_64-linux
  Flavour:  debian
  Compiler: g++
  Subset:   full build
python3 build/version2code.py derived/x86_64-linux-debian/config/Version.ii
Creating derived/x86_64-linux-debian/config/Version.ii...
python3 build/buildinfo2code.py 
derived/x86_64-linux-debian/config/build-info.hh \
linux x86_64 debian \
/usr/share/openmsx
Creating derived/x86_64-linux-debian/config/build-info.hh...
touch derived/x86_64-linux-debian/config/build-info.hh
python3 build/components2code.py 
derived/x86_64-linux-debian/config/components.hh 
derived/x86_64-linux-debian/config/probed_defs.mk
Creating derived/x86_64-linux-debian/config/components.hh...
touch derived/x86_64-linux-debian/config/components.hh
Compiling Autofire.cc...
mkdir -p derived/x86_64-linux-debian/obj
mkdir -p derived/x86_64-linux-debian/dep
g++ \
-MP -MMD -MF derived/x86_64-linux-debian/dep/Autofire.cc.d \
-o derived/x86_64-linux-debian/obj/Autofire.cc.o -g 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -pthread -m64 -pipe 
-std=c++2a -Wall -Wextra -Wundef -Wno-invalid-offsetof -Wunused-macros 
-Wdouble-promotion -Wmissing-declarations -Wshadow -Wold-style-cast 
-Wzero-as-null-pointer-constant -Isrc -Isrc/cassette -Isrc/commands 
-Isrc/config -Isrc/console -Isrc/cpu -Isrc/debugger -Isrc/events -Isrc/fdc 
-Isrc/file -Isrc/ide -Isrc/input -Isrc/laserdisc -Isrc/memory -Isrc/resource 
-Isrc/security -Isrc/serial -Isrc/settings -Isrc/sound -Isrc/thread 
-Isrc/unittest -Isrc/utils -Isrc/video -Isrc/video/ld -Isrc/video/scalers 
-Isrc/video/v9990 -Iderived/x86_64-linux-debian/config -I/usr/include/tcl8.6 
-I/usr/include/SDL2 -D_REENTRANT -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/libpng16 -I/usr/include/SDL2 
-D_REENTRANT -c src/Autofire.cc
In file included from src/utils/hash_map.hh:9,
 from 

Processed: unarchiving 1030814, fixed 1030814 in openldap/2.6.5+dfsg-1~exp1

[Debian Bug Tracking System]

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

> unarchive 1030814
Bug #1030814 {Done: Ryan Tandy } [src:openldap] openldap: 
autopkgtest regression
Unarchived Bug 1030814
> fixed 1030814 openldap/2.6.5+dfsg-1~exp1
Bug #1030814 {Done: Ryan Tandy } [src:openldap] openldap: 
autopkgtest regression
Marked as fixed in versions openldap/2.6.5+dfsg-1~exp1.
> thanks
Stopping processing here.

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

Processed: unarchiving 1020442, fixed 1020442 in openldap/2.6.5+dfsg-1~exp1

[Debian Bug Tracking System]

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

> unarchive 1020442
Bug #1020442 {Done: Ryan Tandy } [src:openldap] heimdal breaks 
openldap autopkgtest: test smbk5pwd
Unarchived Bug 1020442
> fixed 1020442 openldap/2.6.5+dfsg-1~exp1
Bug #1020442 {Done: Ryan Tandy } [src:openldap] heimdal breaks 
openldap autopkgtest: test smbk5pwd
Marked as fixed in versions openldap/2.6.5+dfsg-1~exp1.
> thanks
Stopping processing here.

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

Bug#1042980: gnome-shell: FTBFS on mips64el, mipsel: perf-* tests fail

[Simon McVittie]

Source: gnome-shell
Version: 44.3-1
Severity: serious
Tags: ftbfs experimental help
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: debian-m...@lists.debian.org
User: debian-m...@lists.debian.org
Usertags: mips64el mipsel

gnome-shell 44 builds successfully on all release architectures except
mips*el, but fails to build on mips*el. The three perf-* unit tests fail
with exit status 1 and no obvious error messages:



At the moment this is only in experimental, but we want to upload it to
unstable soon, as part of the libmutter-12-0 transition
.

Is gnome-shell practically useful on mips-based hardware, or does it
have hardware requirements that the mips family do not meet in practice?
If nobody really uses it on mips*el, it might be better to do
architecture-specific removals rather than attempting to debug and fix it.

Or, if the mips porting team can confirm that GNOME 43 works in practice
as a desktop environment on mips*el hardware, then it would be useful
to try GNOME 44 from experimental on the same hardware (after building
gnome-shell locally with DEB_BUILD_OPTIONS=nocheck) to check whether
this is a practical problem.

Thanks,
smcv

Processed: affects 1042978, affects 1042978

[Debian Bug Tracking System]

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

> affects 1042978 src:linux
Bug #1042978 [debci] Tests invalid package upgrades
Added indication that 1042978 affects src:linux
> affects 1042978 src:dkms
Bug #1042978 [debci] Tests invalid package upgrades
Added indication that 1042978 affects src:dkms
> thanks
Stopping processing here.

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

Bug#1042978: Acknowledgement (Tests invalid package upgrades)

[Ben Hutchings]

The test log for reference:
https://ci.debian.net/data/autopkgtest/testing/amd64/d/dkms/36392756/log.gz

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
   - Robert Coveyou



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

Bug#1042978: Tests invalid package upgrades

[Ben Hutchings]

Package: debci
Severity: serious
X-Debbugs-Cc: debian-ker...@lists.debian.org

ci.debian.net is running dkms's autopkgtest with packages from testing
except for linux's binaries updated from unstable.  The test fails
because linux-headers-amd64 is uninstallable in this scenario:

* The available version of linux-headers-amd64 will be the latest,
  6.4.4-2.  It depends on (currently) linux-headers-6.4.0-1-amd64
  at the same version.
* The available version of linux-headers-6.4.0-1-amd64 (built from
  src:linux-signed-amd64) will be 6.4.4-1.

This cross-source-package version lock is unusual but has been
implemented deliberately to ensure that linux and linux-signed-*
always migrate from unstable to testing together.

ci.debian.net must therefore also test updating the binaries from all
these source packages together, not just those built from linux.  If
it's not possible to do this in a general way then we need a specific
workaround that can be used in dkms and any other affected packages
to prevent this invalid test scenario.

Ben.

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

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

Versions of packages debci depends on:
ii  adduser 3.137
pn  amqp-tools  
ii  bsdmainutils12.1.8
ii  curl7.88.1-10
ii  dctrl-tools 2.24-3+b1
ii  debian-archive-keyring  2023.3
ii  debootstrap 1.0.128+nmu5
ii  devscripts  2.23.5
ii  distro-info 1.5
ii  fonts-font-awesome  5.0.10+really4.7.0~dfsg-4.1
ii  jq  1.6-2.1
pn  libjs-bootstrap 
ii  libjs-jquery3.6.1+dfsg+~3.5.14-1
pn  libjs-jquery-flot   
ii  moreutils   0.67-1
ii  netcat-openbsd  1.225-1
ii  netcat-traditional  1.10-47
pn  parallel
ii  patchutils  0.4.2-1
pn  retry   
ii  rsync   3.2.7-1
ii  ruby1:3.1
pn  ruby-activerecord   
pn  ruby-bunny  
pn  ruby-erubi  
pn  ruby-kaminari-activerecord  
pn  ruby-minitar
pn  ruby-omniauth-gitlab
pn  ruby-sinatra
pn  ruby-sinatra-contrib
pn  ruby-sqlite3 | ruby-pg  
pn  ruby-thor   
ii  sudo1.9.14p2-1

Versions of packages debci recommends:
ii  systemd-timesyncd [time-daemon]  254~rc3-3

Versions of packages debci suggests:
pn  apt-cacher-ng   
pn  auto-apt-proxy  

Bug#1037685: marked as pending in guitarix

[Dennis Braun]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/multimedia-team/guitarix/-/commit/997fa54a7b7a3ba67f9cbc8f767776d9c780e669


Fix FTBFS with GCC13 (Closes: #1037685)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1037685

Processed: Bug#1037685 marked as pending in guitarix

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1037685 [src:guitarix] guitarix: ftbfs with GCC-13
Added tag(s) pending.

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

Processed: no a bug

[Debian Bug Tracking System]

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

> notfound 1042557 xtensor/0.24.3-2
Bug #1042557 {Done: Drew Parsons } [src:xtensor] xtensor 
builds with -march=native
No longer marked as found in versions xtensor/0.24.3-2.
>
End of message, stopping processing here.

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

Bug#1037628: marked as pending in drumgizmo

[Dennis Braun]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/multimedia-team/drumgizmo/-/commit/7951a06d44b0f4bde7fbf5a7b0cbbfdf9bde8ddf


Fix FTBFS with GCC13 (Closes: #1037628)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1037628

Processed: Bug#1037628 marked as pending in drumgizmo

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1037628 [src:drumgizmo] drumgizmo: ftbfs with GCC-13
Added tag(s) pending.

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

Bug#1042268: marked as done (haskell-gi-glib: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:158: build-ghc-stamp] Error 25)

[Debian Bug Tracking System]

Your message dated Thu, 3 Aug 2023 10:49:28 -0400 (EDT)
with message-id 
and subject line 
has caused the Debian Bug report #1042268,
regarding haskell-gi-glib: FTBFS: make: *** 
[/usr/share/cdbs/1/class/hlibrary.mk:158: build-ghc-stamp] 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.)


-- 
1042268: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042268
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-gi-glib
Version: 2.0.27-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep 
> dh_installdirs -A 
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> Adding cdbs dependencies to debian/libghc-gi-glib-doc.substvars
> dh_installdirs -plibghc-gi-glib-doc \
>   
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'make_setup_recipe'
> Running ghc --make Setup.hs -o debian/hlibrary.setup
> [1 of 1] Compiling Main ( Setup.hs, Setup.o )
> Linking debian/hlibrary.setup ...
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'configure_recipe'
> Running find . ! -newer /tmp/RThYc68J6o -exec touch -d 1998-01-01 UTC {} ;
> Running dh_listpackages
> libghc-gi-glib-dev
> libghc-gi-glib-prof
> libghc-gi-glib-doc
> Running dh_listpackages
> libghc-gi-glib-dev
> libghc-gi-glib-prof
> libghc-gi-glib-doc
> Running dpkg-buildflags --get LDFLAGS
> -Wl,-z,relro
> Running debian/hlibrary.setup configure --ghc -v2 
> --package-db=/var/lib/ghc/package.conf.d --prefix=/usr 
> --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib 
> --builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro 
> --haddockdir=/usr/lib/ghc-doc/haddock/gi-glib-2.0.27/ --datasubdir=gi-glib 
> --htmldir=/usr/share/doc/libghc-gi-glib-doc/html/ --enable-library-profiling
> Using Parsec parser
> Configuring gi-glib-2.0.27...
> Dependency base >=4.7 && <5: using base-4.15.1.0
> Dependency bytestring >=0.10 && <1: using bytestring-0.10.12.1
> Dependency containers >=0.5 && <1: using containers-0.6.4.1
> Dependency haskell-gi >=0.26 && <0.27: using haskell-gi-0.26.1
> Dependency haskell-gi-base >=0.26 && <0.27: using haskell-gi-base-0.26.2
> Dependency text >=1.0 && <3: using text-1.2.5.0
> Dependency transformers >=0.4 && <1: using transformers-0.5.6.2
> Dependency glib-2.0: using version 2.76.4
> Source component graph: component lib
> Configured component graph:
> component gi-glib-2.0.27-KPNdhQB5q4lD3LJBp2P6eK
> include base-4.15.1.0
> include bytestring-0.10.12.1
> include containers-0.6.4.1
> include haskell-gi-0.26.1-JSRupHRF34I93KyyU4gimG
> include haskell-gi-base-0.26.2-BgiSD0snxm47Hg27HVVupt
> include text-1.2.5.0
> include transformers-0.5.6.2
> Linked component graph:
> unit gi-glib-2.0.27-KPNdhQB5q4lD3LJBp2P6eK
> include base-4.15.1.0
> include bytestring-0.10.12.1
> include containers-0.6.4.1
> include haskell-gi-0.26.1-JSRupHRF34I93KyyU4gimG
> include haskell-gi-base-0.26.2-BgiSD0snxm47Hg27HVVupt
> include text-1.2.5.0
> include transformers-0.5.6.2
> 
> 

Processed: your mail

[Debian Bug Tracking System]

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

> reassign 1042268 haskell-haskell-gi 0.26.1-1
Bug #1042268 [src:haskell-gi-glib] haskell-gi-glib: FTBFS: make: *** 
[/usr/share/cdbs/1/class/hlibrary.mk:158: build-ghc-stamp] Error 25
Bug reassigned from package 'src:haskell-gi-glib' to 'haskell-haskell-gi'.
No longer marked as found in versions haskell-gi-glib/2.0.27-1.
Ignoring request to alter fixed versions of bug #1042268 to the same values 
previously set
Bug #1042268 [haskell-haskell-gi] haskell-gi-glib: FTBFS: make: *** 
[/usr/share/cdbs/1/class/hlibrary.mk:158: build-ghc-stamp] Error 25
There is no source info for the package 'haskell-haskell-gi' at version 
'0.26.1-1' with architecture ''
Unable to make a source version for version '0.26.1-1'
Marked as found in versions 0.26.1-1.
> affects 1042268 haskell-gi-glib
Bug #1042268 [haskell-haskell-gi] haskell-gi-glib: FTBFS: make: *** 
[/usr/share/cdbs/1/class/hlibrary.mk:158: build-ghc-stamp] Error 25
Added indication that 1042268 affects haskell-gi-glib
>
End of message, stopping processing here.

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

Bug#1042918: marked as done (reprotest: FTBFS with tox 4)

[Debian Bug Tracking System]

Your message dated Thu, 03 Aug 2023 14:42:29 +
with message-id 
and subject line Bug#1042918: fixed in reprotest 0.7.26
has caused the Debian Bug report #1042918,
regarding reprotest: FTBFS with tox 4
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.)


-- 
1042918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042918
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: reprotest
Version: 0.7.25
Severity: serious
Justification: ftbfs

I thought we'd managed to avoid this, in #1035645, but we just did the
transition, and I see reprotest is FTBFS:

I: pybuild base:275: cd 
/<>/.pybuild/cpython3_3.11_reprotest/build; tox -c /<>/tox.ini --sitepackages --installpkg 
/<>/.pybuild/cpython3_3.11_reprote
st/reprotest-0.7.25-py3-none-any.whl -e py311 
py311: install_deps .pybuild/cpython3_3.11_reprotest/build> python -I -m pip 
install coverage 
diffoscope pytest
py311: install_package_deps .pybuild/cpython3_3.11_reprotest/build> python -I 
-m pip install d
istro rstr
py311: install_package .pybuild/cpython3_3.11_reprotest/build> python -I -m pip 
install --forc
e-reinstall --no-deps 
/<>/.pybuild/cpython3_3.11_reprotest/reprotest-0.7.25-py3-n
one-any.whl
py311: commands[0] .pybuild/cpython3_3.11_reprotest/build> 
.tox/py311/bin/python -m coverage r
un --omit '.tox/*' --parallel -m py.test tests/
__path__ attribute not found on 'py' while trying to find 'py.test'
py311: exit 1 (0.09 seconds) /<>> .tox/py311/bin/python -m 
coverage run --omit '.
tox/*' --parallel -m py.test tests/ pid=7370
  py311: FAIL code 1 (2.31=setup[2.22]+cmd[0.09] seconds)
  evaluation failed :( (2.36 seconds)
E: pybuild pybuild:388: test: plugin distutils failed with: exit code=1: cd 
/<>/.
pybuild/cpython3_3.11_reprotest/build; tox -c /<>/tox.ini 
--sitepackages --instal
lpkg 
/<>/.pybuild/cpython3_3.11_reprotest/reprotest-0.7.25-py3-none-any.whl
 -e py311 
dh_auto_test: error: pybuild --test --test-tox -i python{version} -p 3.11 
--test-tox returned exit code 13


I'm guessing you want to replace py.test there with pytest.

Stefano

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

Kernel: Linux 6.3.0-1-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
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
--- End Message ---
--- Begin Message ---
Source: reprotest
Source-Version: 0.7.26
Done: Holger Levsen 

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

Debian distribution maintenance software
pp.
Holger Levsen  (supplier of updated reprotest 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, 03 Aug 2023 16:24:39 +0200
Source: reprotest
Architecture: source
Version: 0.7.26
Distribution: unstable
Urgency: medium
Maintainer: Reproducible builds folks 

Changed-By: Holger Levsen 
Closes: 1042918
Changes:
 reprotest (0.7.26) unstable; urgency=medium
 .
   [ Vagrant Cascadian ]
   * tox.ini: Update to use "pytest" which is needed for tox 4. Thanks to
 Stefano Rivera. Closes: #1042918.
Checksums-Sha1:
 c682d6f0dd69e852a96358a11612603707a0468b 2270 reprotest_0.7.26.dsc
 a00c362bee1ef23f4563fed9d395b32ab89eec65 176368 reprotest_0.7.26.tar.xz
 9ec6fda8abf3c638140e25f46ade3a26e9d05276 12402 
reprotest_0.7.26_source.buildinfo
Checksums-Sha256:
 11983fd732a06049db971038ce45599a7acf84018215f670abc263fcbb2d306c 2270 
reprotest_0.7.26.dsc
 0e6c58b2e48d432219ffb611c5daf7c522c81e0bb78abfc7d32422b4269207a1 176368 
reprotest_0.7.26.tar.xz
 81b23ab76f566e028a150a79f3b53b8449616848fe0988933967329eb3608044 12402 
reprotest_0.7.26_source.buildinfo
Files:
 33e57da6b34750b9d4f0b0d8ce6cd9d0 2270 devel optional reprotest_0.7.26.dsc
 1be8f16fc97c5824bd4e3a5848ad2c29 176368 devel optional reprotest_0.7.26.tar.xz
 acf55a10d75be279a763d6c08574f935 12402 devel optional 

Bug#1042557: marked as done (xtensor builds with -march=native)

[Debian Bug Tracking System]

Your message dated Thu, 03 Aug 2023 16:43:42 +0200
with message-id <4f62dbc5c045e8266bd69ca54df51...@debian.org>
and subject line Re: Bug#1042557 xtensor builds with -march=native
has caused the Debian Bug report #1042557,
regarding xtensor builds with -march=native
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.)


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

Package: src:xtensor
Version: 0.24.3-2
Severity: serious
Tags: sid trixie

xtensor builds with -march=native.  I didn't check if there are code paths that 
work with the default baseline on amd64.  If there isn't such a code path, then 
it is another bug report.


However building -march=native is not deterministic, you never can say if the 
package works on your machine or, because it's just dependent on the buildd. 
From my point of view, no package should be built with -march=native.


At least GCC has -march=x86-64-v[1-4] for such settings, so please use that 
instead, and look for other appropriate settings on the other architectures.
--- End Message ---
--- Begin Message ---

tags 1042557 wontfix
thanks

xtensor is a header-only library.  -march=native is used when building 
tests.


The end-user would be sensible to use -march=native in their own builds, 
so it's appropriate to test it also in debian tests.--- End Message ---

Processed: Re: Bug#1042557 xtensor builds with -march=native

[Debian Bug Tracking System]

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

> tags 1042557 wontfix
Bug #1042557 [src:xtensor] xtensor builds with -march=native
Added tag(s) wontfix.
> thanks
Stopping processing here.

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

Bug#1042432: marked as done (mat2: autopkgtest regression with ffmpeg 6.0)

[Debian Bug Tracking System]

Your message dated Thu, 03 Aug 2023 14:40:43 +
with message-id 
and subject line Bug#1042432: fixed in mat2 0.13.4-1
has caused the Debian Bug report #1042432,
regarding mat2: autopkgtest regression with ffmpeg 6.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.)


-- 
1042432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042432
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mat2
Version: 0.13.3-1
Severity: serious
Tag: sid trixie
X-Debbugs-Cc: sramac...@debian.org

mat2's autopkgtests fail with ffmpeg 6.0:

https://ci.debian.net/data/autopkgtest/testing/amd64/m/mat2/36194920/log.gz

126s === FAILURES 
===
126s ___ TestCleaning.test_all_parametred 
___
126s 
126s self = 
126s 
126s def test_all_parametred(self):
126s for case in self.data:
126s with self.subTest(case=case):
126s if 'ffmpeg' in case:
126s try:
126s video._get_ffmpeg_path()
126s except RuntimeError:
126s raise unittest.SkipTest
126s 
126s print('[+] Testing %s' % case['name'])
126s target = './tests/data/clean.' + case['name']
126s shutil.copy('./tests/data/dirty.' + case['name'], target)
126s p1 = case['parser'](target)
126s 
126s for k, v in p1.get_meta().items():
126s if k not in case['meta']:
126s continue
126s if isinstance(v, dict):
126s for _k, _v in v.items():
126s if _k in case['meta'][k]:
126s self.assertEqual(_v, case['meta'][k][_k])
126s else:
126s self.assertEqual(v, case['meta'][k])
126s 
126s p1.lightweight_cleaning = True
126s self.assertTrue(p1.remove_all())
126s 
126s p2 = case['parser'](p1.output_filename)
126s meta = p2.get_meta()
126s if meta:
126s for k, v in p2.get_meta().items():
126s >   self.assertIn(k, case['expected_meta'], '"%s" is 
not in "%s" (%s)' % (k, case['expected_meta'], case['name']))
126s E   AssertionError: 'CompressorName' not found in 
{'AverageBitrate': 465641, 'BufferSize': 0, 'CompatibleBrands': ['isom', 
'iso2', 'avc1', 'mp41'], 'ColorProfiles': 'nclx', 'ColorPrimaries': 'BT.709', 
'ColorRepresentation': 'nclx 1 1 1', 'CompressorID': 'avc1', 'GraphicsMode': 
'srcCopy', 'HandlerDescription': 'SoundHandler', 'HandlerType': 'Metadata', 
'HandlerVendorID': 'Apple', 'MajorBrand': 'Base Media v1 [IS0 14496-12:2003]', 
'MatrixCoefficients': 'BT.709', 'MaxBitrate': 465641, 'MediaDataOffset': 48, 
'MediaDataSize': 379872, 'MediaHeaderVersion': 0, 'MinorVersion': '0.2.0', 
'MovieDataOffset': 48, 'MovieHeaderVersion': 0, 'NextTrackID': 3, 
'PreferredRate': 1, 'Rotation': 0, 'TimeScale': 1000, 'TrackHeaderVersion': 0, 
'TrackID': 1, 'TrackLayer': 0, 'TransferCharacteristics': 'BT.709'} : 
"CompressorName" is not in "{'AverageBitrate': 465641, 'BufferSize': 0, 
'CompatibleBrands': ['isom', 'iso2', 'avc1', 'mp41'], 'ColorProfiles': 'nclx', 
'ColorPrimaries': 'BT.709', 'ColorRepresentation': 'nclx 1 1 1', 
'CompressorID': 'avc1', 'GraphicsMode': 'srcCopy', 'HandlerDescription': 
'SoundHandler', 'HandlerType': 'Metadata', 'HandlerVendorID': 'Apple', 
'MajorBrand': 'Base Media v1 [IS0 14496-12:2003]', 'MatrixCoefficients': 
'BT.709', 'MaxBitrate': 465641, 'MediaDataOffset': 48, 'MediaDataSize': 379872, 
'MediaHeaderVersion': 0, 'MinorVersion': '0.2.0', 'MovieDataOffset': 48, 
'MovieHeaderVersion': 0, 'NextTrackID': 3, 'PreferredRate': 1, 'Rotation': 0, 
'TimeScale': 1000, 'TrackHeaderVersion': 0, 'TrackID': 1, 'TrackLayer': 0, 
'TransferCharacteristics': 'BT.709'}" (mp4)
126s 
126s tests/test_libmat2.py:557: AssertionError

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: mat2
Source-Version: 0.13.4-1
Done: Georg Faerber 

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

Bug#1042970: zoneminder: Embded cakephp

[Bastien Roucariès]

Source: zoneminder
Severity: serious
Justification: embded code copy

Dear Maintainer,

Your package include a copy of cake php. Could you use the packaged one ?

Thanks



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

Bug#1042969: vsftpd: Deletes the ftp user on remove, breaking other packages

[John Goerzen]

Package: vsftpd
Version: 3.0.3-13+b2
Severity: critical
Justification: breaks unrelated software

On removing this package, it indiscriminately removes the ftp user.
Unfortunately, that user was required for iksd in package ckermit to work, so
this broke the unrelated ckermit package.

It is likely that there are other packages and users that would also
use the ftp user.  It should not be removed on package removal.

-- Package-specific info:

-- 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.1.0-10-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, 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 vsftpd depends on:
ii  adduser3.134
ii  debconf [debconf-2.0]  1.5.82
ii  libc6  2.36-9+deb12u1
ii  libcap21:2.66-4
ii  libpam-modules 1.5.2-6
ii  libpam0g   1.5.2-6
ii  libssl33.0.9-1
ii  libwrap0   7.6.q-32
ii  lsb-base   11.6
ii  netbase6.4
ii  procps 2:4.0.2-3
ii  sysvinit-utils [lsb-base]  3.06-4

Versions of packages vsftpd recommends:
ii  logrotate  3.21.0-1
ii  ssl-cert   1.1.2

vsftpd suggests no packages.

-- debconf information:
  vsftpd/directory: /srv/ftp
  vsftpd/username: ftp
# Example config file /etc/vsftpd.conf
#
# The default compiled in settings are fairly paranoid. This sample file
# loosens things up a bit, to make the ftp daemon more usable.
# Please see vsftpd.conf.5 for all compiled in defaults.
#
# READ THIS: This example file is NOT an exhaustive list of vsftpd options.
# Please read the vsftpd.conf.5 manual page to get a full idea of vsftpd's
# capabilities.
#
#
# Run standalone?  vsftpd can run either from an inetd or as a standalone
# daemon started from an initscript.
listen=NO
#
# This directive enables listening on IPv6 sockets. By default, listening
# on the IPv6 "any" address (::) will accept connections from both IPv6
# and IPv4 clients. It is not necessary to listen on *both* IPv4 and IPv6
# sockets. If you want that (perhaps because you want to listen on specific
# addresses) then you must run two copies of vsftpd with two configuration
# files.
listen_ipv6=YES
#
# Allow anonymous FTP? (Disabled by default).
anonymous_enable=NO
#
# Uncomment this to allow local users to log in.
local_enable=YES
#
# Uncomment this to enable any form of FTP write command.
#write_enable=YES
#
# Default umask for local users is 077. You may wish to change this to 022,
# if your users expect that (022 is used by most other ftpd's)
#local_umask=022
#
# Uncomment this to allow the anonymous FTP user to upload files. This only
# has an effect if the above global write enable is activated. Also, you will
# obviously need to create a directory writable by the FTP user.
#anon_upload_enable=YES
#
# Uncomment this if you want the anonymous FTP user to be able to create
# new directories.
#anon_mkdir_write_enable=YES
#
# Activate directory messages - messages given to remote users when they
# go into a certain directory.
dirmessage_enable=YES
#
# If enabled, vsftpd will display directory listings with the time
# in  your  local  time  zone.  The default is to display GMT. The
# times returned by the MDTM FTP command are also affected by this
# option.
use_localtime=YES
#
# Activate logging of uploads/downloads.
xferlog_enable=YES
#
# Make sure PORT transfer connections originate from port 20 (ftp-data).
connect_from_port_20=YES
#
# If you want, you can arrange for uploaded anonymous files to be owned by
# a different user. Note! Using "root" for uploaded files is not
# recommended!
#chown_uploads=YES
#chown_username=whoever
#
# You may override where the log file goes if you like. The default is shown
# below.
#xferlog_file=/var/log/vsftpd.log
#
# If you want, you can have your log file in standard ftpd xferlog format.
# Note that the default log file location is /var/log/xferlog in this case.
#xferlog_std_format=YES
#
# You may change the default value for timing out an idle session.
#idle_session_timeout=600
#
# You may change the default value for timing out a data connection.
#data_connection_timeout=120
#
# It is recommended that you define on your system a unique user which the
# ftp server can use as a totally isolated and unprivileged user.
#nopriv_user=ftpsecure
#
# Enable this and the server will recognise asynchronous ABOR requests. Not
# recommended for security (the code is non-trivial). Not enabling it,
# however, may confuse older FTP clients.
#async_abor_enable=YES
#
# By default the server will 

Bug#1042916: marked as done (Unsatisfiable build-dependency on gtk4 0.16)

[Debian Bug Tracking System]

Your message dated Thu, 03 Aug 2023 13:50:13 +
with message-id 
and subject line Bug#1042916: fixed in helvum 0.4.0-4
has caused the Debian Bug report #1042916,
regarding Unsatisfiable build-dependency on gtk4 0.16
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.)


-- 
1042916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042916
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: helvum
Severity: grave
Justification: renders package installable
X-Debbugs-Cc: werdah...@riseup.net

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi Jonas.

Yesterday I uploaded the new gtk-rs release which makes helvum uninstallable
as it depends on the no longer present 0.16 versions of the gtk-rs
libraries. The fix is simple, just dropping 2001_gtk.patch should
suffice. Please look into this as it blocks testing migration for gtk-rs
otherwise. 

Thanks,

Matthias

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

Kernel: Linux 6.4.2-surface (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_CRAP
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages helvum depends on:
ii  libc62.36-9
ii  libcairo-gobject21.16.0-7
ii  libcairo21.16.0-7
ii  libgcc-s112.2.0-14
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libglib2.0-0 2.76.3-1
ii  libgraphene-1.0-01.10.8-1
ii  libgtk-4-1   4.10.3+ds-1
ii  libpango-1.0-0   1.50.12+ds-1
ii  libpipewire-0.3-00.3.65-3

helvum recommends no packages.

helvum suggests no packages.

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAzFiEEwuGmy/3s5RGopBdtGL0QaztsVHUFAmTKqk0VHHdlcmRhaGlh
c0ByaXNldXAubmV0AAoJEBi9EGs7bFR1yMsP9jRViLwDlXoyVxq5wSvWpVB1honZ
TqyTaPVWhjYsEZsWftKjeGWEv1Mf5cHy5A6d9rhXlIj7QIcGRKv9ss3SevQLplL8
7LwPBdQ/TIsPvNBhaHt8tOnTJlqWXT2uyVwHidjcE+UcIYN/QGW51UY2dpPPq4WS
0Qp3UTL8EvyYF0omjQ8/Gdaj7ufNKdcLsCPOMijRkGq2zcU9mIbY4a3lD/xiY4X4
NMD1GtqbFcZF1ND/FrzTQqD0Q8je0NBJzo9TJR2M1mF6ozkZjuM2ZgoVZEGwUWhl
o9kp5+69JxwAhOubPMi29TDpILHiKJfWKDph2S7I1APcjyvLBlCifDhpXVuEu6QA
rH10KWChI6j1nQ6PlcXjfD1fAnfqPLckACm2lkyLejDT3LzTjjQM1dmETepRN7h+
5Ibjxwj5+yIf0gsckru5Lj4VkMi9HRCh86TEvcG1BaS9oz0oir0CcNdw8Ytrnqrn
6+n8p257OBVCfwvLh4dQm0cJ7GyjIF6ojrM7ju0a54jASpA052PCxMM29wgC6riW
jj6weVhryZhdRlk9CJVE0GGMWhy7NjggUL7dQvoF18hevms5om0HHdMIU2uy49zg
dthnaYMLOESW9UlHV564KM/Tz1A7t0vDBdDEvHRjDBVsalu7j09CW/P1urYz3lO9
BU6yB9Q8g+5cMek=
=1f89
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: helvum
Source-Version: 0.4.0-4
Done: Jonas Smedegaard 

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated helvum 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, 03 Aug 2023 14:30:14 +0200
Source: helvum
Architecture: source
Version: 0.4.0-4
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Closes: 1042916
Changes:
 helvum (0.4.0-4) unstable; urgency=medium
 .
   * drop patch 2001, obsoleted by Debian package updates;
 tighten build-dependencies for crates glib gtk4;
 closes: bug#1042916, thanks to Matthias Geiger
   * update dh-cargo fork
Checksums-Sha1:
 c385e500ab0e1e4955ffd88a4354a7bd864469ab 2078 helvum_0.4.0-4.dsc
 65208bfa7e830cdeca0dd8b1163b0e6e8bc840e7 15744 helvum_0.4.0-4.debian.tar.xz
 97ef39642b740fad5a0cd9ad518e3a167d58a46a 22876 helvum_0.4.0-4_amd64.buildinfo
Checksums-Sha256:
 4e4e5b397607b5bf6dc8cff7cb4df7c43800ecf23f16a8a86a983de338a85a64 2078 
helvum_0.4.0-4.dsc
 3a4c7aed7de340488d7b7ad4720147a09451fe41a1bfeaca4da0c11692f687ba 15744 
helvum_0.4.0-4.debian.tar.xz
 06a53010faf62758cce0f73631cf42822459e98e9913b3baf51f440617626e9e 22876 
helvum_0.4.0-4_amd64.buildinfo
Files:
 

Bug#1042967: nheko crashes on first launch in arm64 (librem 5)

[Pirate Praveen]

Package: nheko
Version: 0.11.3-2+b1
severity: grave
justification: makes the app unusable

I initially noticed this on mobian bookworm (then I switched to 
chatty). Now I can reliable reproduce it on trixie as well.


Crash log attached.

To reproduce rm -rf .local/share/nheko .config/nheko .cache/nheko
and run nheko from terminal

First noticed when I reinstalled, flatpack also fails same way so looks 
like an upstream issue.


Second time, nheko starts but initial sync never completes. Both chatty 
and gomuks works with same matrix id.


[2023-08-03 17:42:55.678] [ui] [info] Restoring window size 0x0
[2023-08-03 17:42:55.759] [ui] [info] WebRTC: initialised GStreamer 1.22.4
[2023-08-03 17:42:55.883] [ui] [info] jdenticon plugin not found.
[2023-08-03 17:42:57.976] [ui] [info] starting nheko 0.11.3
[2023-08-03 17:42:57.986] [ui] [info] Unity service available: false
Error: signal 11:
nheko(_Z17stacktraceHandleri+0x40)[0xd55ee940]
linux-vdso.so.1(__kernel_rt_sigreturn+0x0)[0xa06be7ac]
nheko(+0x973940)[0xd5433940]
nheko(+0x977090)[0xd5437090]
nheko(+0x9783bc)[0xd54383bc]
/lib/aarch64-linux-gnu/libgstreamer-1.0.so.0(+0x55270)[0x9da25270]
/lib/aarch64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x148)[0x9d83a6c8]
/lib/aarch64-linux-gnu/libglib-2.0.so.0(+0x5aaa0)[0x9d83aaa0]
/lib/aarch64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x34)[0x9d83ab44]
/lib/aarch64-linux-gnu/libQt5Core.so.5(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x54)[0x9deef6d8]
/lib/aarch64-linux-gnu/libQt5Core.so.5(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x13c)[0x9de89d2c]
/lib/aarch64-linux-gnu/libQt5Core.so.5(_ZN16QCoreApplication4execEv+0x98)[0x9de933f8]
nheko(main+0xd14)[0xd526b684]
/lib/aarch64-linux-gnu/libc.so.6(+0x26dc0)[0x9d2a6dc0]
/lib/aarch64-linux-gnu/libc.so.6(__libc_start_main+0x98)[0x9d2a6e98]
nheko(_start+0x30)[0xd526c770]
Error: signal 6:
nheko(_Z17stacktraceHandleri+0x40)[0xd55ee940]
linux-vdso.so.1(__kernel_rt_sigreturn+0x0)[0xa06be7ac]
/lib/aarch64-linux-gnu/libc.so.6(+0x7fd30)[0x9d2ffd30]
/lib/aarch64-linux-gnu/libc.so.6(gsignal+0x1c)[0x9d2b9e2c]
nheko(_Z17stacktraceHandleri+0xd8)[0xd55ee9d8]
linux-vdso.so.1(__kernel_rt_sigreturn+0x0)[0xa06be7ac]
nheko(+0x973940)[0xd5433940]
nheko(+0x977090)[0xd5437090]
nheko(+0x9783bc)[0xd54383bc]
/lib/aarch64-linux-gnu/libgstreamer-1.0.so.0(+0x55270)[0x9da25270]
/lib/aarch64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x148)[0x9d83a6c8]
/lib/aarch64-linux-gnu/libglib-2.0.so.0(+0x5aaa0)[0x9d83aaa0]
/lib/aarch64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x34)[0x9d83ab44]
/lib/aarch64-linux-gnu/libQt5Core.so.5(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x54)[0x9deef6d8]
/lib/aarch64-linux-gnu/libQt5Core.so.5(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x13c)[0x9de89d2c]
/lib/aarch64-linux-gnu/libQt5Core.so.5(_ZN16QCoreApplication4execEv+0x98)[0x9de933f8]
nheko(main+0xd14)[0xd526b684]
/lib/aarch64-linux-gnu/libc.so.6(+0x26dc0)[0x9d2a6dc0]
/lib/aarch64-linux-gnu/libc.so.6(__libc_start_main+0x98)[0x9d2a6e98]
nheko(_start+0x30)[0xd526c770]

Bug#1042921: glib log feature

[Jonas Smedegaard]

Quoting Matthias Geiger (2023-08-03 12:18:32)
> Sorry, I patched out the log dependency (and subsequent features) 
> absentminded.
> 
> A fixed version is uploaded and should hit the buildds / archive soon.

Thanks!

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1042964: shim-signed: policy violation: Recommends a package that is not in debian main

[Zorka . Jordon]

Package: shim-signed
Version: 1.39+15.7-1
Severity: serious
Justification: Policy 2.2.1
X-Debbugs-Cc: zorka.jor...@allfreemail.net

Dear Maintainer,

shim-signed currently Recommends secureboot-db package, which is not in debian 
main.

This is a violation of debian policy 2.2.1 
https://www.debian.org/doc/debian-policy/ch-archive.html#the-main-archive-area

```
In addition, the packages in main:

- must not require or recommend a package outside of main for compilation or 
execution (thus, the package must not declare a Pre-Depends, Depends, 
Recommends, Build-Depends, Build-Depends-Indep, or Build-Depends-Arch 
relationship on a non-main package unless that package is only listed as a 
non-default alternative for a package in main)
```

This was previously mentioned 4 years ago in #932358 and #1041449. Neither of 
those bugreports had any maintainer reaction.

Please either remove shim-signed from debian, since it violates debian policy, 
or change the package dependencies to no longer recommend packages outside of 
debian main.

Alternatively, please provide information why this package should keep the 
recommendation on a package that is not in debian main, and address the 4 year 
old bugreport in #932358 and #1041449

Severity set as serious because this is a violation of debian policy, and 
because there has been no reaction in 4 years about this issue.



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

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

Versions of packages shim-signed depends on:
ii  grub-efi-amd64-bin 2.06-13
ii  grub2-common   2.06-13
ii  shim-helpers-amd64-signed  1+15.7+1
ii  shim-signed-common 1.39+15.7-1

Versions of packages shim-signed recommends:
pn  secureboot-db  

shim-signed suggests no packages.

-- no debconf information

Processed: src:verilator: fails to migrate to testing for too long: FTBFS on mipsel

[Debian Bug Tracking System]

Processing control commands:

> close -1 5.012-1
Bug #1042962 [src:verilator] src:verilator: fails to migrate to testing for too 
long: FTBFS on mipsel
Marked as fixed in versions verilator/5.012-1.
Bug #1042962 [src:verilator] src:verilator: fails to migrate to testing for too 
long: FTBFS on mipsel
Marked Bug as done

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

Bug#1042962: src:verilator: fails to migrate to testing for too long: FTBFS on mipsel

[Paul Gevers]

Source: verilator
Version: 5.006-3
Severity: serious
Control: close -1 5.012-1
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:verilator has been trying to migrate for 
31 days [2]. Hence, I am filing this bug. The version in unstable failed 
to build on mipsel where it built in the past.


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


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


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


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1042960: FTBFS: error: parsing file 'debian/gcc-doc/DEBIAN/control' near line 3 package 'gcc-doc'

[Aurelien Jarno]

Package: gcc-doc-base
Version: 12.2.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear maintainer,

gcc-doc-base currently fails to build from source on amd64. From my build log:

| dh_gencontrol -pgcc-doc-base -- -v12.2.0-1
| dh_gencontrol -i --remaining-packages
| dh_gencontrol: warning: No packages to build. Possible architecture mismatch: 
amd64, want: all alpha amd64 arm64 armel armhf i386 ia64 mips mipsel mipsn32 
mipsn32el mips64 mips64el mipsr6 mipsr6el mipsn32r6 mipsn32r6el mips64r6 
mips64r6el powerpc ppc64 ppc64el s390 s390x sparc sparc64 x32 any
| make[1]: Leaving directory '/<>'
|dh_md5sums
|dh_builddeb
| dpkg-deb: error: parsing file 'debian/gcc-doc/DEBIAN/control' near line 3 
package 'gcc-doc':
|  'Version' field value '5:': nothing after colon in version number
| dpkg-deb: error: parsing file 'debian/cpp-doc/DEBIAN/control' near line 3 
package 'cpp-doc':
|  'Version' field value '5:': nothing after colon in version number
| dpkg-deb: error: parsing file 'debian/gfortran-doc/DEBIAN/control' near line 
3 package 'gfortran-doc':
|  'Version' field value '5:': nothing after colon in version number
| dh_builddeb: error: dpkg-deb --build debian/gcc-doc .. returned exit code 2
| dh_builddeb: error: dpkg-deb --build debian/cpp-doc .. returned exit code 2
| dh_builddeb: error: dpkg-deb --build debian/gfortran-doc .. returned exit 
code 2
| dpkg-deb: building package 'gnat-doc' in '../gnat-doc_12.2.0-1_amd64.deb'.
| dpkg-deb: error: parsing file 'debian/gccgo-doc/DEBIAN/control' near line 3 
package 'gccgo-doc':
|  'Version' field value '5:': nothing after colon in version number
| dpkg-deb: building package 'gcc-doc-base' in 
'../gcc-doc-base_12.2.0-1_all.deb'.
| dh_builddeb: error: dpkg-deb --build debian/gccgo-doc .. returned exit code 2
| dh_builddeb: error: Aborting due to earlier error
| make: *** [debian/rules:117: binary] Error 25
| dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2
| 

| Build finished at 2023-08-03T10:53:37Z

Regards
Aurelien

Bug#1038468: marked as done (python-escript: Stop using netcdf-cxx-legacy)

[Debian Bug Tracking System]

Your message dated Thu, 03 Aug 2023 10:52:29 +
with message-id 
and subject line Bug#1038468: fixed in python-escript 5.6-5
has caused the Debian Bug report #1038468,
regarding python-escript: Stop using netcdf-cxx-legacy
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.)


-- 
1038468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038468
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-escript
Version: 5.6-4
Severity: important
Tags: patch
User: debian-...@lists.debian.org
Usertags: netcdf-cxx-legacy-rm

Dear Maintainer,

Your package uses netcdf-cxx-legacy which is dead upstream and will be removed 
during the trixie development cycle.

The attached patch only drops the build dependency, as your package doesn't 
actually link to netcdf-cxx-legacy.

Kind Regards,

Bas
diff -ruN python-escript-5.6/debian/changelog 
python-escript-5.6.new/debian/changelog
--- python-escript-5.6/debian/changelog 2022-01-01 12:40:25.0 +0100
+++ python-escript-5.6.new/debian/changelog 2023-06-18 17:53:26.631234221 
+0200
@@ -1,3 +1,10 @@
+python-escript (5.6-4.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Don't use netcdf-cxx-legacy.
+
+ -- Bas Couwenberg   Sun, 18 Jun 2023 17:53:18 +0200
+
 python-escript (5.6-4) unstable; urgency=medium
 
   * Standards-Version: 4.6.0
diff -ruN python-escript-5.6/debian/control 
python-escript-5.6.new/debian/control
--- python-escript-5.6/debian/control   2022-01-01 12:40:25.0 +0100
+++ python-escript-5.6.new/debian/control   2023-06-18 16:14:47.514101664 
+0200
@@ -20,7 +20,6 @@
   libboost-numpy-dev,
libboost-iostreams-dev,
libnetcdf-dev,
-   libnetcdf-cxx-legacy-dev,
   libnetcdf-c++4-dev,
   libsilo-dev (>= 4.10.2.real-5),
   libscotchparmetis-dev,
--- End Message ---
--- Begin Message ---
Source: python-escript
Source-Version: 5.6-5
Done: Alastair McKinstry 

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated python-escript 
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, 03 Aug 2023 11:13:07 +0100
Source: python-escript
Architecture: source
Version: 5.6-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Alastair McKinstry 
Closes: 1038468
Changes:
 python-escript (5.6-5) unstable; urgency=medium
 .
   * Standards-Version: 4.6.2
   * Drop build-dep on netcdf-legacy-cxx. Closes: #1038468
Checksums-Sha1:
 1ad54ac1b1d247b85399d305ed9e82a96e823bb2 2740 python-escript_5.6-5.dsc
 8dfe4d9d14a3de97b9e4229bd31ff6429a6fc0c3 19320 
python-escript_5.6-5.debian.tar.xz
Checksums-Sha256:
 318c9628e8e826653db91568d120cbe3707e99862240d77651dcc7fc78e2f282 2740 
python-escript_5.6-5.dsc
 12854329fff68c35fdd2ebc9c20e2951619eb5d7d1b272bff2945311c5292f62 19320 
python-escript_5.6-5.debian.tar.xz
Files:
 791fc6f1237c7f02dde828e82b772899 2740 science optional python-escript_5.6-5.dsc
 4182b8af2d5ea810168c79fd6d60ab85 19320 science optional 
python-escript_5.6-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmTLg2cACgkQy+a7Tl2a
06X31g/+KOADRjFHLywoeHoVI8XfwVrf56SfdrlkFSkF/atYC/Tkac7L/wJu3SXx
/p20H9yN3jh0QJuN5T/KjU1Dim2gnwl8ISe1yg353spOyhrMe8EBVnXs2YFrpA16
g+xMS3ONBEw2RHxE/yY2P3TJhrwzXoE36uS/iKN1aMBBZWEZBhI48aDF1rvntRvs
sDgTwFhQLzB31Ae7MqfASsPKyFUTF3oaXQrBdrsyy7U7xc/E856WrQx7XMAjhxiY
yVe1BvBZxHOgGXGYaUYdzTtLcNHgRBov9Y03LqUqn2/9x+83lYS7rsk4HuJXnX5i
OcvBUmOCNudXpgAtl8faAizb6Qh91GhMuLXU7Z/yWLZxpvguJ3AaODrrLAsrLkAE
dhPdy2oh9z2EFDhzbHpYXuct4Z+KgUGZ38gumC4aX3ctmGjlZUJ03XNnHikePtLH
uDH/+ooU8sCo3j4QVj9AVpCVLzgWZ1XsnD+myAFKy7zYukg6Hi/plP/RLuFXsEPV
1aknHvTF/gK2+6bCfuLTuAsfZYGdQjmsfEi4sbBsYVtl/EV9QTNi7VG3hNE0susI
fcX6LSqQ2K//1Dn7jne5AZrIpFZ1wZ4oCsG8yOMFRKh2TtVdCLGUyzZo/YBl25uv
zItXDn5zZVJtDeGT+R8zhrLdVBzAwy+0tMWt/tmPyY7GLvAkFx4=
=H4W2
-END PGP SIGNATURE End Message ---

Bug#1039871: proposed patch fails

[Alastair McKinstry]

Hi

Unfortunately the proposed patch doesn't fix the problem.

With later versions of xarray now using pooch to download data, and 
failing if its not setup, a better fix to the download issue is needed.


regards
Alastair


--
Alastair McKinstry,
GPG: 82383CE9165B347C787081A2CBE6BB4E5D9AD3A5
ph: +353 87 6847928 e: alast...@mckinstry.ie, im: @alastair:mckinstry.ie

Bug#1042921: marked as done (rust-glib: feature "log" has disappeared)

[Debian Bug Tracking System]

Your message dated Thu, 03 Aug 2023 10:34:06 +
with message-id 
and subject line Bug#1042921: fixed in rust-glib 0.17.10-2
has caused the Debian Bug report #1042921,
regarding rust-glib: feature "log" has disappeared
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.)


-- 
1042921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042921
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-glib
Version: 0.17.10-1
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

rust-glib was upgraded without coordination with reverse dependencies.
Don't do that.  It puts a stress on maintenance of reverse dependencies!

The upgrade patched away feature "log". Don't do that.  Yeah, I can see
that it requires a new package - then package that, don't break reverse
dependencies in Debian!

 - Jonas
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmTKvpAACgkQLHwxRsGg
ASF5whAAho9hTN1h+vVnX0r9dcYsWAdMSKGGEJU8Gm95dd5OvgAayquIs9KkM+SH
TVpFTNy83VtyJ+pxBNjdmk76bOUJdrgECjD2A1ytgsHKUreoZjXeuB4ukswVqRFn
Ay4WKLjSY5rEh4acrUX2kVbDo3hUn2qz8NrImw0H7zzgOJik4Hpp9nlAX/XPvNDE
9wci98XsmEh/eaHr17HSqF/BZDyXxTgHT6s3vP1WPLKBpBgGjIsSHXLVfiRi1Woj
mng+scm2KlKFtSI5KZ/q1Bj8604yLXFpRvN1hzlnroY9/HTeGJdXJtyETOKV+ESU
/fVMFIK25DyqHA8jfipvyrA7DiSJxc7FTWajPi2bdj+RxTajRM4pSahONrNtI3xx
K88fnDHJEVCgwp4zlRnn7JJsK7dFW1+SEQBW0tH+tXHUquVM+mSu4VIgQTdjGv8j
gNV5dh8j/NtIP2xRrUOYK40OJ+RdgPW5sf2ZtqslN5DH2ZtZTIpcUAVO4ehOF3Ky
AV2VMmKINPpyhyCh30/PB6VD2ImWMz44hrvS20g6yTrq2I/bdIteiqbVR7LjvbFZ
ugFLXiEHl0pWkm33vSEZXnjnZR2g1X/PZVFv9mcoUFE7CeNQEMv4IxsMs5wU8YdE
IGfjrmvKLTI3s3pDsIsNNBvbLvUSXxI6nNcYpfMln8KNu7RZqRM=
=C2MK
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: rust-glib
Source-Version: 0.17.10-2
Done: Matthias Geiger 

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

Debian distribution maintenance software
pp.
Matthias Geiger  (supplier of updated rust-glib 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, 03 Aug 2023 12:15:26 +0200
Source: rust-glib
Architecture: source
Version: 0.17.10-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Matthias Geiger 
Closes: 1042921
Changes:
 rust-glib (0.17.10-2) unstable; urgency=medium
 .
   * Package glib 0.17.10 from crates.io using debcargo 2.6.0
   * Re-enable log feature, this was patched out wrongfully (Closes:
 #1042921)
Checksums-Sha1:
 7cf805d00a313580adaf61d176fddbcf1a41d315 3122 rust-glib_0.17.10-2.dsc
 9ff7561f414d2ca6a463080f25dc2ef349d1e182 4292 rust-glib_0.17.10-2.debian.tar.xz
 b6d861094539feb1defb791cdee6eff09cca8a85 7254 
rust-glib_0.17.10-2_source.buildinfo
Checksums-Sha256:
 3974abcfbe58e9f7bc6bd3ba01ff0e7edddf610385fea8bd35203a7b0694e132 3122 
rust-glib_0.17.10-2.dsc
 55eb009a0c2399f5daa1f2fe261b928a7a6587b93c30c85216abc1cb58254342 4292 
rust-glib_0.17.10-2.debian.tar.xz
 b1eefc239f92d53a9765b5fc3150b3f3f845de0771b38ad749c4cbfa9396bc92 7254 
rust-glib_0.17.10-2_source.buildinfo
Files:
 f712fa402c94185f91c35dc94ee5669d 3122 rust optional rust-glib_0.17.10-2.dsc
 0835705fdd7c4678434c5fe33ade650c 4292 rust optional 
rust-glib_0.17.10-2.debian.tar.xz
 a30e41ce69c1346d70d60620fb3602a5 7254 rust optional 
rust-glib_0.17.10-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEEwuGmy/3s5RGopBdtGL0QaztsVHUFAmTLfkEVHHdlcmRhaGlh
c0ByaXNldXAubmV0AAoJEBi9EGs7bFR1KZoP/1DEK2NpmDtU5gGzBcqwS3BjEZId
f1KJ/DSnKWdUTueP+UWTRD87uyR45z44TxpkLVvnC5thmMrqAaWWuPWo2M60w86B
VzskU+jQjySruyzBB0Msmq9xcEoxvkXbDtVF02N16VtpEnvgYEfj7MofqmXPTxue
xPPgcGJwJdUzcwt7wOA+rEnAO9iv/lRsK0bAFdGGw3C2bbayTu1tJbwwN+mlCPod
/Byqp6IYGCgbGr9qEY+G48PxgT+tWdrATPazIN3MErKo+Q5Ztj0RerBQZG3M2Muu
qUt4KzKPJrbMC+8X181bjxkKC1UMl2dUqzH87qNE57WShuyROzSP7wnfwh1jLp5Y
jSx9cBVzi2/Sa94EdPuyKNoat+9GNTqk217GfZH8+0673zH4CLAL5QrSjYtFY4kE
AkrqpLCKisWfmy3911apZnyPATawo+WJvEhugSRBi8zI6WLJiBdcp7YpCF/J4WT/
F8e2VDtElx8H00Q2jKIiIzGnE0YqlOJy3Q+dHVbXArlDQwWRm42sfKcl0r1xD6kc
jFeqrzUyXgbanBXZnVWQ9CtlbR00qBSzyBJoapiUIx0vG5s8DtCC4UcXmfy9U2EI

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

[Paul Gevers]

Hi

[Just in case you didn't know: submitters of bugs in the BTS are not 
copied on replies, so I only saw your message because I went to the bug 
myself]


On Wed, 2 Aug 2023 20:58:39 +0530 Nilesh Patra  wrote:

This needs fixing in two stages. The error is:

| 38s TMB was built with Matrix version 1.5.4.1
| 38s Current Matrix version is 1.5.3

So rmatrix's new version needs to go to testing, which is currently
1.6.0. So

1. rmatrix 1.6.0 needs to go to testing
2. tmb needs to be rebuilt against rmatrix 1.6.0


What I don't like about this phrasing is that it doesn't discuss why tmb 
needs rebuilding and why that's not correctly embedded in the package 
relations to begin with. The message you quote above is only a warning, 
so it's not the full story as apparently it's normally OK to have the 
skew (as I would expect). I wonder, does rebuilding just work? I recall 
I saw that tmb had a new upstream release with only three changes where 
one was to be compatible with the new rmatrix [1]. With rebuilding, 
would the right relation of tmb towards rmatrix be embedded in the 
package relations (otherwise r-cran-tmb can migrate to testing before 
rmatrix does, I don't know if that would be a problem).


rmatrix can't migrate to testing before either tmb is fixed (by a 
rebuild but see above or otherwise) or tmb is removed from testing.


If it's clear that rebuilding is the right (Debian) solution (and not 
papering over issues that should be solved), then I can schedule the 
rebuilds. But I'm not convinced yet.


Paul

[1] https://cran.r-project.org/web/packages/TMB/NEWS


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1042921: glib log feature

[Matthias Geiger]

Hi Jonas.

Sorry, I patched out the log dependency (and subsequent features) 
absentminded.


A fixed version is uploaded and should hit the buildds / archive soon.


regards

Matthias



OpenPGP_0x18BD106B3B6C5475.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1035389: Timeline ETA

[Vincent Robbemond]

Is there any progress or an ETA when this will be picked up?

Bug#1042956: iraf-fitsutil: FTBFS with iraf 2.17.1

[Aurelien Jarno]

Source: iraf-fitsutil
Version: 2018.07.06-4
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear maintainer,

iraf-fitsutil FTBFS on amd64, this seems to be related to the upload of iraf
2.17.1. From my build log:

| dpkg-buildpackage
| -
| 
| Command: dpkg-buildpackage --sanitize-env -us -uc -mAurelien Jarno 
 -eAurelien Jarno  -rfakeroot
| dpkg-buildpackage: info: source package iraf-fitsutil
| dpkg-buildpackage: info: source version 2018.07.06-4
| dpkg-buildpackage: info: source distribution unstable
|  dpkg-source --before-build .
| dpkg-buildpackage: info: host architecture amd64
|  fakeroot debian/rules clean
| dh clean
|dh_clean
|  dpkg-source -b .
| dpkg-source: info: using source format '3.0 (quilt)'
| dpkg-source: info: building iraf-fitsutil using existing 
./iraf-fitsutil_2018.07.06.orig.tar.gz
| dpkg-source: info: using patch list from debian/patches/series
| dpkg-source: info: building iraf-fitsutil in 
iraf-fitsutil_2018.07.06-4.debian.tar.xz
| dpkg-source: info: building iraf-fitsutil in iraf-fitsutil_2018.07.06-4.dsc
|  debian/rules build
| dh build
|dh_update_autotools_config
|dh_autoreconf
|debian/rules override_dh_auto_configure
| make[1]: Entering directory '/<>'
| rm -rf bin
| mkdir bin
| make[1]: Leaving directory '/<>'
|debian/rules override_dh_auto_build
| make[1]: Entering directory '/<>'
| mkpkg -p fitsutil
| hlib$mkpkg.inc:5: warning: macro `IRAFARCH' not found
| !clear;date
| TERM environment variable not set.
| Thu Aug  3 09:30:34 UTC 2023
| $call update
| $call lib
| = LIB =
| 
| $call update@lib
| mkpkg[1]: Entering directory `/<>/lib/'
| $call install@cfitsio
| lib/mkpkg:14: error: cannot access subdirectory `cfitsio'
| mkpkg[1]: Leaving directory `/<>/lib/'
| make[1]: *** [debian/rules:19: override_dh_auto_build] Error 1
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:5: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
| 

| Build finished at 2023-08-03T09:30:34Z


Regards
Aurelien

Bug#1041537: python3 platlib points again to /usr/local

[Jussi Pakkanen]

On Wed, 2 Aug 2023 at 12:01, Enrico Zini  wrote:

> > I'm confused. Why is this not set by default when building packages?
> > FWICT this is a custom patch in Debian to make Python use deb paths.In
> > this case Meson is doing exactly what you ask it to do, which is to
> > use local paths because that environment variable is not set to `deb`.
>
> It will, though it's not there yet.

Based on that thread I'd say that this is not a bug in Meson at all.
Can I just close it or should it be reassigned to some other package
so it is not forgotten?

Bug#1042957: iraf-mscred: FTBFS with iraf 2.17.1

[Aurelien Jarno]

Source: iraf-mscred
Version: 5.05+2018.07.09-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear maintainer,

iraf-fitsutil FTBFS on amd64, this seems to be related to the upload of iraf
2.17.1. From my build log:

| $call libsf.a
| warning: library `libsf.a' not found
| /usr/lib/iraf/unix/bin/xc.e -c -w -p mscred rngranges.x stfgraph.x 
stfprofile.x t_starfocus.x
| ar r /<>/bin/libsf.a rngranges.o stfgraph.o stfprofile.o 
t_starfocus.o
| ar: creating /<>/bin/libsf.a
| ranlib /<>/bin/libsf.a
| Updated 4 files in libsf.a
| check file `libsf.a' into `mscbin$'
| mkpkg[4]: Leaving directory `/<>/src/mscdisplay/src/starfocus/'
| mkpkg[3]: Leaving directory `/<>/src/mscdisplay/src/'
| mkpkg[2]: Leaving directory `/<>/src/mscdisplay/'
| mkpkg[1]: Leaving directory `/<>/src/'
| $call lfinder@src
| mkpkg[1]: Entering directory `/<>/src/'
| $call lfinder@mscfinder
| mkpkg[2]: Entering directory `/<>/src/mscfinder/'
| check out file `libfinder.a = /<>/bin/libfinder.a'
| $call libfinder.a
| warning: library `libfinder.a' not found
| mkpkg[3]: Entering directory `/<>/src/mscfinder/select/'
| /usr/lib/iraf/unix/bin/xc.e -c -w -p mscred select.x allrows.x change.x mjd.x 
tbleval.x tblterm.x
| ar r /<>/bin/libfinder.a select.o allrows.o change.o mjd.o 
tbleval.o tblterm.o
| ar: creating /<>/bin/libfinder.a
| mkpkg[3]: Leaving directory `/<>/src/mscfinder/select/'
| /usr/lib/iraf/unix/bin/xc.e -c -w -p mscred t_tpeak.x
| ar r /<>/bin/libfinder.a t_tpeak.o
| ranlib /<>/bin/libfinder.a
| Updated 7 files in libfinder.a
| check file `libfinder.a' into `mscbin$'
| mkpkg[2]: Leaving directory `/<>/src/mscfinder/'
| mkpkg[1]: Leaving directory `/<>/src/'
| $call update@src
| mkpkg[1]: Entering directory `/<>/src/'
| $call update@ccdred
| mkpkg[2]: Entering directory `/<>/src/ccdred/'
| $call update@src
| mkpkg[3]: Entering directory `/<>/src/ccdred/src/'
| $call update@combine
| mkpkg[4]: Entering directory `/<>/src/ccdred/src/combine/'
| $call relink
| check out file `x_combine.o = /<>/bin/x_combine.o'
| /usr/lib/iraf/unix/bin/xc.e -c -w -p mscred x_combine.x
| /usr/lib/iraf/unix/bin/xc.e -Nz -p mscred x_combine.o -lcombine -limc 
-lccdred -lmscred -lxtools -lcurfit -lsurfit -lgsurfit -liminterp -lnlfit 
-lslalib -lncar -lgks -o xx_combine.e
| check file `x_combine.o' into `mscbin$'
| $call install
| move `xx_combine.e' to `mscbin$x_combine.e'
| mkpkg[4]: Leaving directory `/<>/src/ccdred/src/combine/'
| mkpkg[3]: Leaving directory `/<>/src/ccdred/src/'
| $call relink
| check out file `x_ccdred.o = /<>/bin/x_ccdred.o'
| /usr/lib/iraf/unix/bin/xc.e -c -w -p mscred x_ccdred.x
| /usr/lib/iraf/unix/bin/xc.e -Nz -p mscred  x_ccdred.o -lccdred -limc -lxtools 
-lcurfit -lgsurfit -lncar -lgks -o xx_ccdred.e
| check file `x_ccdred.o' into `mscbin$'
| $call install
| move `xx_ccdred.e' to `mscbin$x_ccdred.e'
| mkpkg[2]: Leaving directory `/<>/src/ccdred/'
| $call update@mscdisplay
| mkpkg[2]: Entering directory `/<>/src/mscdisplay/'
| $call relink
| $call mscdisplay
| check out file `x_mscdisplay.o = /<>/bin/x_mscdisplay.o'
| /usr/lib/iraf/unix/bin/xc.e -c -w -p mscred x_mscdisplay.x
| src/mscdisplay/mkpkg:27: error: file `imdwcsver.x' not found
| mkpkg[2]: Leaving directory `/<>/src/mscdisplay/'
| make[1]: *** [debian/rules:15: override_dh_auto_build] Error 1
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:5: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
| 

| Build finished at 2023-08-03T09:36:22Z
| 
| Finished
| 
| 
| 
| 
+--+
| | Cleanup 
 |
| 
+--+
| 
| Purging /<>
| Not cleaning session: cloned chroot in use
| I: 71killgpgagent: No /usr/bin/gpg-agent found running; none killed.
| E: Build failure (dpkg-buildpackage died)
| 
| 
+--+
| | Summary 
 |
| 
+--+
| 
| Build Architecture: amd64
| Build Type: full
| Build-Space: 14280
| Build-Time: 26
| Distribution: sid
| Fail-Stage: build
| Host Architecture: amd64
| Install-Time: 13
| Job: iraf-mscred
| Machine Architecture: amd64
| Package: iraf-mscred
| Package-Time: 60
| Source-Version: 5.05+2018.07.09-1
| Space: 14280
| Status: attempted
| Version: 5.05+2018.07.09-1
| 

| Finished at 2023-08-03T09:36:22Z

Regards,
Aurelien

Bug#1042953: smokeping: Recommends non-existing package 'echoping'

[Debian/GNU]

Source: smokeping
Severity: serious
Justification: Policy 2.2.1

Dear Maintainer,

The current version of smokeping in Debian (2.7.3-4.1) still depends on
'echoping' which was removed from the archives on 2020-08-07, so the
last release that shipped it was buster (currently: old-old-stable).

Please remove this dependency (as it violates Debian policy §2.2.1, see
https://www.debian.org/doc/debian-policy/ch-archive.html#the-main-archive-area)

cheers, and thanks for packaging 'smokeping'.


gdamsr
IOhannes

Bug#1037579: armnn: ftbfs with GCC-13

[Emanuele Rocca]

Note that since the upload of 20.08-13 the package now fails to build for
different reasons on i386 vs arm64/armhf.

I've opened https://bugs.debian.org/1042942 for i386.

On arm64/armhf the bug seems to be due to a missing include in
core/utils/misc/Utility.h from libarm-compute-dev.

[  2%] Building CXX object 
profiling/common/src/CMakeFiles/pipeCommon.dir/CommandHandlerRegistry.cpp.o
cd /<>/build-area/profiling/common/src && /usr/bin/c++ 
-DARMCOMPUTECL_ENABLED -DARMCOMPUTENEON_ENABLED -DARMNN_DYNAMIC_BACKEND_ENABLED 
-DARMNN_SERIALIZER 
-DARMNN_SERIALIZER_SCHEMA_PATH=\"/<>/src/armnnSerializer/ArmnnSchema.fbs\"
 -DARMNN_TF_LITE_PARSER -DBOOST_ALL_DYN_LINK -DBOOST_ALL_NO_LIB 
-DDYNAMIC_BACKEND_BUILD_DIR=\"/<>/build-area\" 
-I/<>/include -I/<>/profiling 
-I/<>/profiling/common/include -I/<>/common/include 
-I/<>/src/profiling -I/<>/src/armnnUtils -isystem 
/<>/third-party -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=c++14 -Wall -Wextra -Werror -Wold-style-cast 
-Wno-missing-braces -Wconversion -Wsign-conversion -fPIC   
'-DDYNAMIC_BACKEND_PATHS="/usr/lib/aarch64-linux-gnu/armnn22/"' -MD -MT 
profiling/common/src/CMakeFiles/pipeCommon.dir/CommandHandlerRegistry.cpp.o -MF 
CMakeFiles/pipeCommon.dir/CommandHandlerRegistry.cpp.o.d -o 
CMakeFiles/pipeCommon.dir/CommandHandlerRegistry.cpp.o -c 
/<>/profiling/common/src/CommandHandlerRegistry.cpp
In file included from 
/usr/include/aarch64-linux-gnu/arm_compute/core/TensorShape.h:29,
 from 
/usr/include/aarch64-linux-gnu/arm_compute/core/ITensorInfo.h:29,
 from 
/usr/include/aarch64-linux-gnu/arm_compute/core/ITensor.h:27,
 from 
/<>/src/backends/aclCommon/ArmComputeTensorUtils.hpp:10,
 from 
/<>/src/backends/aclCommon/ArmComputeTensorUtils.cpp:5:
/usr/include/aarch64-linux-gnu/arm_compute/core/utils/misc/Utility.h: In 
function ‘bool arm_compute::utility::check_aligned(void*, size_t)’:
/usr/include/aarch64-linux-gnu/arm_compute/core/utils/misc/Utility.h:194:35: 
error: ‘uintptr_t’ in namespace ‘std’ does not name a type
  194 | return (reinterpret_cast(ptr) % alignment) == 0;
  |   ^
/usr/include/aarch64-linux-gnu/arm_compute/core/utils/misc/Utility.h:30:1: 
note: ‘std::uintptr_t’ is defined in header ‘’; did you forget to 
‘#include ’?
   29 | #include 
  +++ |+#include 
   30 | #include 
[  2%] Building CXX object 
src/backends/backendsCommon/CMakeFiles/armnnBackendsCommon.dir/DynamicBackend.cpp.o
cd /<>/build-area/src/backends/backendsCommon && /usr/bin/c++ 
-DARMCOMPUTECL_ENABLED -DARMCOMPUTENEON_ENABLED -DARMNN_DYNAMIC_BACKEND_ENABLED 
-DARMNN_SERIALIZER 
-DARMNN_SERIALIZER_SCHEMA_PATH=\"/<>/src/armnnSerializer/ArmnnSchema.fbs\"
 -DARMNN_TF_LITE_PARSER -DBOOST_ALL_DYN_LINK -DBOOST_ALL_NO_LIB 
-DDYNAMIC_BACKEND_BUILD_DIR=\"/<>/build-area\" 
-I/<>/include -I/<>/profiling 
-I/<>/include/armnn/backends -I/<>/src/armnn 
-I/<>/src/armnnUtils -I/<>/src/backends 
-I/<>/src/profiling -I/<>/profiling/common/include 
-isystem /<>/third-party -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++14 -Wall 
-Wextra -Werror -Wold-style-cast -Wno-missing-braces -Wconversion 
-Wsign-conversion -fPIC   
'-DDYNAMIC_BACKEND_PATHS="/usr/lib/aarch64-linux-gnu/armnn22/"' -MD -MT 
src/backends/backendsCommon/CMakeFiles/armnnBackendsCommon.dir/DynamicBackend.cpp.o
 -MF CMakeFiles/armnnBackendsCommon.dir/DynamicBackend.cpp.o.d -o 
CMakeFiles/armnnBackendsCommon.dir/DynamicBackend.cpp.o -c 
/<>/src/backends/backendsCommon/DynamicBackend.cpp
make[3]: *** 
[src/backends/aclCommon/CMakeFiles/armnnAclCommon.dir/build.make:79: 
src/backends/aclCommon/CMakeFiles/armnnAclCommon.dir/ArmComputeTensorUtils.cpp.o]
 Error 1
make[3]: Leaving directory '/<>/build-area'
make[2]: *** [CMakeFiles/Makefile2:989: 
src/backends/aclCommon/CMakeFiles/armnnAclCommon.dir/all] Error 2

Processed: tagging 1042942 and 1037579

[Debian Bug Tracking System]

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

> tag 1042942 + ftbfs
Bug #1042942 [src:armnn] armnn: FTBFS on i386 due to test failures
Added tag(s) ftbfs.
> tag 1037579 - patch
Bug #1037579 [src:armnn] armnn: ftbfs with GCC-13
Removed tag(s) patch.
> retitle 1037579 armnn: ftbfs with GCC-13 on arm64 and armhf
Bug #1037579 [src:armnn] armnn: ftbfs with GCC-13
Changed Bug title to 'armnn: ftbfs with GCC-13 on arm64 and armhf' from 'armnn: 
ftbfs with GCC-13'.
>
End of message, stopping processing here.

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

Bug#1042942: armnn: FTBFS on i386 due to test failures

[Emanuele Rocca]

Package: src:armnn
Version: 20.08-13
Severity: serious

armnn 20.08-13 seems to compile correctly on i386, but then FTBFS due to
the following test failures:

Running 430 test cases...
./src/armnn/test/ModelAccuracyCheckerTest.cpp(103):  [1;31;49merror: in 
"ModelAccuracyCheckerTest/TestFloat32OutputTensorAccuracy": check totalAccuracy 
== 33.321f has failed [0;39;49m
./src/armnn/test/ModelAccuracyCheckerTest.cpp(107):  [1;31;49merror: in 
"ModelAccuracyCheckerTest/TestFloat32OutputTensorAccuracy": check totalAccuracy 
== 66.641f has failed [0;39;49m
./src/armnn/test/optimizations/ConvertConstantsBFloatTests.cpp(120):  
[1;31;49merror: in "Optimizer/ConvertConstantsBFloatToFloatTest": check data[3] 
== 3.1072295E29f has failed [0;39;49m
./src/armnn/test/optimizations/ConvertConstantsBFloatTests.cpp(121):  
[1;31;49merror: in "Optimizer/ConvertConstantsBFloatToFloatTest": check data[4] 
== 9.131327E-10f has failed [0;39;49m
./src/armnn/test/optimizations/ConvertConstantsBFloatTests.cpp(123):  
[1;31;49merror: in "Optimizer/ConvertConstantsBFloatToFloatTest": check data[6] 
== -3.1072295E29f has failed [0;39;49m
./src/armnn/test/optimizations/ConvertConstantsBFloatTests.cpp(124):  
[1;31;49merror: in "Optimizer/ConvertConstantsBFloatToFloatTest": check data[7] 
== -9.131327E-10f has failed [0;39;49m
./src/profiling/test/ProfilingTests.cpp(1366):  [1;31;49merror: in 
"ExternalProfiling/CheckCounterDirectoryRegisterCounter": check 
counter->m_Multiplier == 123.45f has failed [0;39;49m
./src/profiling/test/ProfilingTests.cpp(1408):  [1;31;49merror: in 
"ExternalProfiling/CheckCounterDirectoryRegisterCounter": check 
counterWUnits->m_Multiplier == 123.45f has failed [0;39;49m
./src/profiling/test/ProfilingTests.cpp(1436):  [1;31;49merror: in 
"ExternalProfiling/CheckCounterDirectoryRegisterCounter": check 
counterWoDevice->m_Multiplier == 123.45f has failed [0;39;49m
./src/profiling/test/ProfilingTests.cpp(1490):  [1;31;49merror: in 
"ExternalProfiling/CheckCounterDirectoryRegisterCounter": check 
counterWDevice->m_Multiplier == 123.45f has failed [0;39;49m
./src/profiling/test/ProfilingTests.cpp(1519):  [1;31;49merror: in 
"ExternalProfiling/CheckCounterDirectoryRegisterCounter": check 
counterWoCounterSet->m_Multiplier == 123.45f has failed [0;39;49m
./src/profiling/test/ProfilingTests.cpp(1561):  [1;31;49merror: in 
"ExternalProfiling/CheckCounterDirectoryRegisterCounter": check 
counterWNumberOfCores->m_Multiplier == 123.45f has failed [0;39;49m
./src/profiling/test/ProfilingTests.cpp(1600):  [1;31;49merror: in 
"ExternalProfiling/CheckCounterDirectoryRegisterCounter": check 
counterWMultiCoreDevice->m_Multiplier == 123.45f has failed [0;39;49m
./src/profiling/test/ProfilingTests.cpp(1648):  [1;31;49merror: in 
"ExternalProfiling/CheckCounterDirectoryRegisterCounter": check 
counterWMultiCoreDeviceWParentCategory->m_Multiplier == 123.45f has failed 
[0;39;49m
./src/profiling/test/ProfilingTests.cpp(1684):  [1;31;49merror: in 
"ExternalProfiling/CheckCounterDirectoryRegisterCounter": check 
counterWCounterSet->m_Multiplier == 123.45f has failed [0;39;49m
./src/profiling/test/ProfilingTests.cpp(1708):  [1;31;49merror: in 
"ExternalProfiling/CheckCounterDirectoryRegisterCounter": check 
counterWDeviceWCounterSet->m_Multiplier == 123.45f has failed [0;39;49m
./src/profiling/test/ProfilingTests.cpp(1741):  [1;31;49merror: in 
"ExternalProfiling/CheckCounterDirectoryRegisterCounter": check 
anotherCounter->m_Multiplier == .00043f has failed [0;39;49m

 [1;31;49m*** 17 failures are detected in the test module "UnitTests"
 [0;39;49mmake[1]: *** [debian/rules:67: override_dh_auto_test] Error 201
make[1]: Leaving directory '/<>'
make: *** [debian/rules:30: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


Full build logs at:
https://buildd.debian.org/status/fetch.php?pkg=armnn=i386=20.08-13=1690924863=0

Bug#1042862: Xspice crashes on start

[Timo Aaltonen]

Frank Heckenbach kirjoitti 2.8.2023 klo 0.44:

Package: xserver-xspice
Version: 0.1.6-1
Severity: grave
Justification: renders package unusable

See #1038648.

As I wrote there, 0.1.6-1 doesn't fix the problem, but this was
ignored, so I'm sending a new bug report.

The buggy patch is now upstream, but that doesn't make it correct.
I've already explained how to fix it correctly.



send your explanation upstream, thanks

--
t

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

[Debian Bug Tracking System]

Your message dated Thu, 03 Aug 2023 07:04:35 +
with message-id 
and subject line Bug#1042271: fixed in dput-ng 1.36
has caused the Debian Bug report #1042271,
regarding dput-ng: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i 
python{version} -p 3.11 returned exit code 13
to be marked as done.

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

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


-- 
1042271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042271
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dput-ng
Version: 1.35
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/docs'
> sphinx-build -b html -W -d _build/doctrees   . _build/html
> Running Sphinx v5.3.0
> making output directory... done
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 36 source files that are out of date
> updating environment: [new config] 36 added, 0 changed, 0 removed
> reading sources... [  2%] index
> reading sources... [  5%] library/changes
> reading sources... [  8%] library/config
> reading sources... [ 11%] library/configs/dputcf
> reading sources... [ 13%] library/configs/dputng
> reading sources... [ 16%] library/configs/index
> reading sources... [ 19%] library/core
> reading sources... [ 22%] library/exceptions
> reading sources... [ 25%] library/hooks
> reading sources... [ 27%] library/hooks/checksum
> reading sources... [ 30%] library/hooks/deb
> reading sources... [ 33%] library/hooks/distribution
> reading sources... [ 36%] library/hooks/gpg
> reading sources... [ 38%] library/hooks/impatient
> reading sources... [ 41%] library/hooks/index
> reading sources... [ 44%] library/hooks/lintian
> reading sources... [ 47%] library/index
> reading sources... [ 50%] library/interface
> reading sources... [ 52%] library/interfaces/clinterface
> reading sources... [ 55%] library/interfaces/index
> reading sources... [ 58%] library/overrides
> reading sources... [ 61%] library/profile
> reading sources... [ 63%] library/uploader
> reading sources... [ 66%] library/uploaders/ftp
> reading sources... [ 69%] library/uploaders/http
> reading sources... [ 72%] library/uploaders/index
> reading sources... [ 75%] library/uploaders/local
> reading sources... [ 77%] library/uploaders/scp
> reading sources... [ 80%] library/uploaders/sftp
> reading sources... [ 83%] library/util
> reading sources... [ 86%] reference/configs
> reading sources... [ 88%] reference/contributing
> reading sources... [ 91%] reference/hookinstall
> reading sources... [ 94%] reference/hooks
> reading sources... [ 97%] reference/index
> reading sources... [100%] reference/migrating
> 
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [  2%] index
> writing output... [  5%] library/changes
> writing output... [  8%] library/config
> writing output... [ 11%] library/configs/dputcf
> writing output... [ 13%] library/configs/dputng
> writing output... [ 16%] library/configs/index
> writing output... [ 19%] library/core
> writing output... [ 22%] library/exceptions
> writing output... [ 25%] library/hooks
> writing output... [ 27%] library/hooks/checksum
> writing output... [ 30%] library/hooks/deb
> writing output... [ 33%] library/hooks/distribution
> writing output... [ 36%] library/hooks/gpg
> writing output... [ 38%] library/hooks/impatient
> writing output... [ 41%] library/hooks/index
> writing output... [ 44%] library/hooks/lintian
> writing output... [ 47%] library/index
> writing output... [ 50%] library/interface
> writing output... [ 52%] library/interfaces/clinterface
> writing output... [ 55%] library/interfaces/index
> writing output... [ 58%] library/overrides
> writing output... [ 61%] library/profile
> writing output... [ 63%] library/uploader
> writing output... [ 66%] library/uploaders/ftp
> writing output... [ 69%] library/uploaders/http
> writing output... [ 72%] library/uploaders/index
> writing output... [ 75%] library/uploaders/local
> writing output... [ 77%] library/uploaders/scp
> writing output... [ 80%] library/uploaders/sftp
> writing output... [ 83%] library/util
> writing output... [ 86%] reference/configs
> writing output... [ 88%] reference/contributing
> writing output... [ 91%] reference/hookinstall
> writing output... [ 94%] reference/hooks
> writing output... [ 97%] reference/index
> 

Processed: Bug#1042271 marked as pending in dput-ng

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1042271 [src:dput-ng] dput-ng: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p 3.11 returned exit code 13
Ignoring request to alter tags of bug #1042271 to the same tags previously set

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

Bug#1042271: marked as pending in dput-ng

[Gianfranco Costamagna]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian/dput-ng/-/commit/c43cccecac5b95b4bc29fbf15d724dfd2192dd02


Move from bionic to jammy, to fix tests and build (Closes: #1042271)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1042271

Bug#1042271: marked as pending in dput-ng

[Gianfranco Costamagna]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian/dput-ng/-/commit/49faa80020e91d6d375d2607eff7f719b2fb8978


Merge branch 'fix-tests-bionic-eol' into 'master'

Move from bionic to jammy, to fix tests and build (Closes: #1042271)

See merge request debian/dput-ng!26


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1042271

Processed: Bug#1042271 marked as pending in dput-ng

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1042271 [src:dput-ng] dput-ng: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p 3.11 returned exit code 13
Added tag(s) pending.

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

Bug#1042933: octave-statistics autopkg tests fail in unstable on amd64

[Rafael Laboissière]

* Matthias Klose  [2023-08-03 04:23]:


Package: src:octave-statistics
Version: 1.6.0-1
Severity: serious
Tags: sid trixie

octave autopkg tests fail in unstable on amd64 (triggered by gcc-13).

https://ci.debian.net/data/autopkgtest/testing/amd64/o/octave-statistics/36329437/log.gz

Not sure which ones are the regressions, because all failures seem to 
be marked as "known failure".


Thanks for the bug report, Matthias.

Just for the record, this is the offending unit test:

308s [inst/ConfusionMatrixChart.m]
308s >

/tmp/autopkgtest-lxc.9x_h6bvs/downtmp/build.BGX/src/inst/ConfusionMatrixChart.m
308s * demo
308s  ## Create a simple ConfusionMatrixChart Object
308s
308s  cm = ConfusionMatrixChart (gca, [1 2; 1 2], {"A","B"},{"XLabel","LABEL 
A"})
308s  NormalizedValues = cm.NormalizedValues
308s  ClassLabels = cm.ClassLabels
308s * shared visibility_setting
308s  visibility_setting = get (0, "DefaultFigureVisible");
308s * test
308s  set (0, "DefaultFigureVisible", "off");
308s  cm = ConfusionMatrixChart (gca, [1 2; 1 2], {"A","B"},{"XLabel","LABEL 
A"});
308s  assert (isa (cm, "ConfusionMatrixChart"), true);
308s  set (0, "DefaultFigureVisible", visibility_setting);
308s warning: Non-positive limit for logarithmic axis ignored
308s ! test failed
308s set: "cameratarget" must be finite
308s shared variables visibility_setting = on
308s 1 test, 0 passed, 0 known failure, 0 skipped

We have seen this problem already elsewhere. I will try to investigate 
it.


Best,

Rafael Laboissière