Bug#1017260: marked as done (ruby-builder: FTBFS: chmod: cannot access 'debian/ruby-builder/usr/share/rubygems-integration/all/gems/builder-3.2.4/doc/releases/builder-2.1.1.rdoc': No such file or dire

[Debian Bug Tracking System]

Your message dated Wed, 21 Sep 2022 13:56:34 +0900
with message-id <98354ed964d50ed8594970052e495...@duckcorp.org>
and subject line Re:  ruby-builder: FTBFS: chmod: cannot access 
'debian/ruby-builder/usr/share/rubygems-integration/all/gems/builder-3.2.4/doc/releases/builder-2.1.1.rdoc':
 No such file or directory
has caused the Debian Bug report #1017260,
regarding ruby-builder: FTBFS: chmod: cannot access 
'debian/ruby-builder/usr/share/rubygems-integration/all/gems/builder-3.2.4/doc/releases/builder-2.1.1.rdoc':
 No such file or directory
to be marked as done.

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

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


-- 
1017260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017260
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-builder
Version: 3.2.4-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_install
> chmod a-x 
> debian/ruby-builder/usr/share/rubygems-integration/all/gems/builder-3.2.4/doc/releases/builder-2.1.1.rdoc
> chmod: cannot access 
> 'debian/ruby-builder/usr/share/rubygems-integration/all/gems/builder-3.2.4/doc/releases/builder-2.1.1.rdoc':
>  No such file or directory
> make[1]: *** [debian/rules:12: override_dh_install] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/08/13/ruby-builder_3.2.4-1_unstable.log

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

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

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

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

Version: 3.2.4-2

Sorry I forgot to mention the BR in the changelog.

--
Marc Dequènes--- End Message ---

Bug#1019061: marked as done (gnuplot and gnuplot-data not available)

[Debian Bug Tracking System]

Your message dated Wed, 21 Sep 2022 06:33:23 +0200
with message-id 

and subject line Done
has caused the Debian Bug report #1019061,
regarding gnuplot and gnuplot-data not available
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.)


-- 
1019061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019061
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnuplot
Version: 5.4.4+dfsg1-1
Severity: important

Dear Maintainer,

it looks like gnuplot-data is not available anymore (at least from version
5.4.4-gfsg1-1). This makes gnuplot (any flavour) uninstallable.

I'm surprised I could not find any report on this on the debian bugtracking
system. Is there anything I'm missing about this package?

In any case, if I'm not wrong, this "bug" (maybe just a delay in packaging
the new version?) is far more than "important" because it makes the package
unusable.

Thank you for your work and your patience.

Alberto



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

Kernel: Linux 5.18.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
gnuplot-data is built. Thus closing.

Cheers

Anton
--- End Message ---

Bug#1019061: Done

[Anton Gladky]

gnuplot-data is built. Thus closing.

Cheers

Anton

Processed: your mail

[Debian Bug Tracking System]

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

> reopen 1011716
Bug #1011716 {Done: Sebastian Ramacher } [src:libbluray] 
libbluray: FTBFS: [javac] 
/<>/src/libbluray/bdj/java-j2se/java/io/BDFileSystemImpl.java:21: 
error: BDFileSystemImpl is not abstract and does not override abstract method 
isInvalid(File) in FileSystem
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions libbluray/1:1.3.1-2.
> tags 1011716 bullseye patch
Bug #1011716 [src:libbluray] libbluray: FTBFS: [javac] 
/<>/src/libbluray/bdj/java-j2se/java/io/BDFileSystemImpl.java:21: 
error: BDFileSystemImpl is not abstract and does not override abstract method 
isInvalid(File) in FileSystem
Added tag(s) bullseye and patch.
> thanks
Stopping processing here.

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

Bug#1011716: libbluray: continue to FTBFS and VLC crash in stable

[Christian Barcenas]

reopen 1011716
tags 1011716 bullseye patch
thanks

Re-opening because I still see FTBFS on Bullseye 11.5 (stable), and
this library causes a crash in VLC when certain Blu-rays are opened.

I think an upload to stable-updates is necessary. Backporting the
following patch from the packaging repository's master branch onto
the current source package in bullseye seemed to fix both issues.

https://salsa.debian.org/multimedia-team/libbluray/-/blob/8c62a5c355ab7b68eacaced9ae245a88059924db/debian/patches/0002-Fix-build-failure-after-Oracle-Java-CPU-for-April-20.patch

Thanks.

Processed: Re: Bug#998097: [DRE-maint] Bug#998097: ruby-eventmachine FTBFS on IPV6-only buildds and accesses the internet during the build

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #998097 {Done: Lucas Kanashiro } 
[src:ruby-eventmachine] ruby-eventmachine FTBFS on IPV6-only buildds and 
accesses the internet during the build
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 
ruby-eventmachine/1.3~pre20201020-b50c135-6.

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

Bug#998097: [DRE-maint] Bug#998097: ruby-eventmachine FTBFS on IPV6-only buildds and accesses the internet during the build

[Adrian Bunk]

Control: reopen -1

On Wed, Nov 03, 2021 at 09:50:32AM -0300, Antonio Terceiro wrote:
> On Sat, Oct 30, 2021 at 11:53:46AM +0300, Adrian Bunk wrote:
> > Source: ruby-eventmachine
> > Severity: serious
> > Tags: ftbfs
> > 
> > FTBFS on IPV6-only buildds:
> > 
> > https://buildd.debian.org/status/fetch.php?pkg=ruby-eventmachine=amd64=1.3~pre20201020-b50c135-3=1633500476=0
> > https://buildd.debian.org/status/fetch.php?pkg=ruby-eventmachine=i386=1.3~pre20201020-b50c135-4%2Bb1=1635578996=0
> > 
> > FTBFS due to attempted DNS:
> > 
> > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-eventmachine.html
> > 
> > ...
> > ===
> > Failure: test_nameserver(TestResolver):
> >was expected to be kind_of?
> >but was
> >   .
> > /build/1st/ruby-eventmachine-1.3~pre20201020-b50c135/tests/test_resolver.rb:19:in
> >  `test_nameserver'
> >  16:   end
> >  17: 
> >  18:   def test_nameserver
> >   => 19: assert_kind_of(String, EM::DNS::Resolver.nameserver)
> >  20:   end
> >  21: 
> >  22:   def test_nameservers
> > ===
> > ...
> 
> The ipv6-only thing is already worked around in
> 1.3~pre20201020-b50c135-4 by skipping the tests in those setups.
>...

Something still seems to fail on IPV-6 only buildds:
https://buildd.debian.org/status/fetch.php?pkg=ruby-eventmachine=amd64=1.3~pre20201020-b50c135-6%2Bb1=1663720780=0

cu
Adrian

Processed: Re: Bug#1020290 init-system-helpers depends on usrmerge | usr-is-merged

[Debian Bug Tracking System]

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

> reopen 1020290
Bug #1020290 {Done: Luca Boccassi } [init-system-helpers] 
init-system-helpers depends on usrmerge | usr-is-merged
Bug reopened
Ignoring request to alter fixed versions of bug #1020290 to the same values 
previously set
> severity 1020290 critical
Bug #1020290 [init-system-helpers] init-system-helpers depends on usrmerge | 
usr-is-merged
Ignoring request to change severity of Bug 1020290 to the same value.
> stop
Stopping processing here.

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

Bug#1020290: init-system-helpers depends on usrmerge | usr-is-merged

[Craig Sanders]

reopen 1020290
severity 1020290 critical
stop

> Given you have made usrmerge uninstallable in your system as you
> admitted (probably running one of dpkg's unsupported scripts that
> installs a local blocking package, I'd imagine) then it is entirely on
> you to fix that, it cannot be done remotely. Please stop spewing abuse
> and playing games with the BTS, it is not going to achieve anything.

I did not do that.  And I stated very clearly that I didn't.

You asked, and I replied:

> > did you block it locally somehow?
> Nope.  I had no idea this stealth-mandatory change was being forced.

stop twisting my words to avoid fixing your bug.

I said that I probably *would* (note: future tense, an indication of intent)
do something to block usrmerge on my systems somehow.

And I also said that it wasn't necessary to do so because your package was
broken.

I then gave another example of the problem occuring on a minimalist standard
sid VM.



Stop closing this bug without fixing it.

It is breaking upgrades and dist-upgrades etc.

Bug#1020395: ruby-sdbm FTBFS with more than one supported Ruby version

[Adrian Bunk]

Source: ruby-sdbm
Version: 1.0.0-4
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=ruby-sdbm=1.0.0-4%2Bb1

...
   dh_gencontrol -a -O--buildsystem=ruby
dpkg-gencontrol: warning: can't parse dependency lib lib
dpkg-gencontrol: error: parsing package 'ruby-sdbm' Depends field: ,
,
libc6 (>= 2.33), libruby3.0 (>= 3.0.0~preview1) | libruby3.1 (>= 
3.1.2), lib | lib lib
dh_gencontrol: error: dpkg-gencontrol -pruby-sdbm -ldebian/changelog 
-Tdebian/ruby-sdbm.substvars -Pdebian/.debhelper/ruby-sdbm/dbgsym-root 
-UPre-Depends -URecommends -USuggests -UEnhances -UProvides -UEssential 
-UConflicts -DPriority=optional -UHomepage -UImportant -UBuilt-Using 
-DAuto-Built-Package=debug-symbols -UProtected -DPackage=ruby-sdbm-dbgsym 
"-DDepends=ruby-sdbm (= \${binary:Version})" "-DDescription=debug symbols for 
ruby-sdbm" "-DBuild-Ids=4fef3beede0c69a9a14602656f4dfbd945ea5163 
8f82f5a95abaf8b82874576873c2885577570001" -DSection=debug -UReplaces -UBreaks 
returned exit code 25
dh_gencontrol: error: Aborting due to earlier error
make: *** [debian/rules:7: binary-arch] Error 25

Bug#1017166: marked as done (obs-studio: FTBFS: media-remux.c:91:49: error: ‘AVStream’ has no member named ‘codec’)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2022 23:46:15 +
with message-id 
and subject line Bug#1017166: fixed in obs-studio 28.0.1+dfsg1-1
has caused the Debian Bug report #1017166,
regarding obs-studio: FTBFS: media-remux.c:91:49: error: ‘AVStream’ has no 
member named ‘codec’
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.)


-- 
1017166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017166
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: obs-studio
Version: 27.2.4+dfsg1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/libobs && /usr/bin/cc 
> -DENABLE_DARRAY_TYPE_TEST -DHAVE_OBSCONFIG_H -DIS_LIBOBS=1 -DLIBOBS_EXPORTS 
> -DUSE_XDG -Dlibobs_EXPORTS -I/usr/include/glib-2.0/gio 
> -I/<>/deps/libcaption -I/<>/libobs 
> -I/<>/obj-x86_64-linux-gnu/config -Wall -Wextra -Wvla 
> -Wno-unused-function -Werror-implicit-function-declaration 
> -Wno-missing-braces -Wno-missing-field-initializers -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -DSIMDE_ENABLE_OPENMP -fopenmp-simd -O3 -Wdate-time 
> -D_FORTIFY_SOURCE=2 
> -DFFMPEG_MUX_FIXED=\"/usr/lib/x86_64-linux-gnu/obs-plugins/obs-ffmpeg/obs-ffmpeg-mux\"
>  -std=gnu99 -fno-strict-aliasing -fPIC   -pthread -I/usr/include/gio-unix-2.0 
> -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -mmmx -msse -msse2 
> -fvisibility=hidden -MD -MT 
> libobs/CMakeFiles/libobs.dir/util/array-serializer.c.o -MF 
> CMakeFiles/libobs.dir/util/array-serializer.c.o.d -o 
> CMakeFiles/libobs.dir/util/array-serializer.c.o -c 
> /<>/libobs/util/array-serializer.c
> /<>/libobs/media-io/media-remux.c: In function ‘init_output’:
> /<>/libobs/media-io/media-remux.c:91:49: error: ‘AVStream’ has 
> no member named ‘codec’
>91 | job->ofmt_ctx, in_stream->codec->codec);
>   | ^~
> /<>/libobs/media-io/media-remux.c:103:23: error: implicit 
> declaration of function ‘avcodec_copy_context’ 
> [-Werror=implicit-function-declaration]
>   103 | ret = avcodec_copy_context(out_stream->codec, 
> in_stream->codec);
>   |   ^~~~
> /<>/libobs/media-io/media-remux.c:103:54: error: ‘AVStream’ has 
> no member named ‘codec’
>   103 | ret = avcodec_copy_context(out_stream->codec, 
> in_stream->codec);
>   |  ^~
> /<>/libobs/media-io/media-remux.c:103:72: error: ‘AVStream’ has 
> no member named ‘codec’
>   103 | ret = avcodec_copy_context(out_stream->codec, 
> in_stream->codec);
>   |   
>  ^~
> /<>/libobs/media-io/media-remux.c:117:27: error: ‘AVStream’ has 
> no member named ‘codec’
>   117 | out_stream->codec->codec_tag = 0;
>   |   ^~
> /<>/libobs/media-io/media-remux.c:118:51: error: ‘AVStream’ has 
> no member named ‘codec’
>   118 | out_stream->time_base = out_stream->codec->time_base;
>   |   ^~
> /<>/libobs/media-io/media-remux.c:120:35: error: ‘AVStream’ has 
> no member named ‘codec’
>   120 | out_stream->codec->flags |= 
> CODEC_FLAG_GLOBAL_H;
>   |   ^~
> /<>/libobs/media-io/media-remux.c:30:29: error: 
> ‘AV_CODEC_FLAG_GLOBAL_HEADER’ undeclared (first use in this function); did 
> you mean ‘CODEC_FLAG_GLOBAL_H’?
>30 | #define CODEC_FLAG_GLOBAL_H AV_CODEC_FLAG_GLOBAL_HEADER
>   | ^~~
> /<>/libobs/media-io/media-remux.c:120:53: note: in expansion of 
> macro ‘CODEC_FLAG_GLOBAL_H’
>   120 | out_stream->codec->flags |= 
> CODEC_FLAG_GLOBAL_H;
>   | 
> ^~~
> /<>/libobs/media-io/media-remux.c:30:29: note: each undeclared 
> identifier is reported only once for each function it appears in
>30 | #define CODEC_FLAG_GLOBAL_H AV_CODEC_FLAG_GLOBAL_HEADER
>   | ^~~
> /<>/libobs/media-io/media-remux.c:120:53: note: in expansion of 
> macro ‘CODEC_FLAG_GLOBAL_H’
>   120 | 

Bug#1020038: marked as done (dash-el: FTBFS: dash.el:615:8: Error: docstring wider than 80 characters)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2022 23:25:37 +
with message-id 
and subject line Bug#1020038: fixed in dash-el 
2.19.1+git20220608.1.0ac1ecf+dfsg-1
has caused the Debian Bug report #1020038,
regarding dash-el: FTBFS: dash.el:615:8: Error:  docstring wider than 80 
characters
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.)


-- 
1020038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020038
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dash-el
Version: 2.19.1+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> emacs -Q -batch -L . -eval '(setq byte-compile-error-on-warn t)' -f 
> batch-byte-compile dash.el
> emacs -Q -batch -L . -eval '(setq byte-compile-error-on-warn t)' -f 
> batch-byte-compile dev/dash-defs.el
> 
> In toplevel form:
> dash.el:615:8: Error:  docstring wider than 80 characters
> make[1]: *** [Makefile:69: dash.elc] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/09/17/dash-el_2.19.1+dfsg-1_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: dash-el
Source-Version: 2.19.1+git20220608.1.0ac1ecf+dfsg-1
Done: Sean Whitton 

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

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

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

Debian distribution maintenance software
pp.
Sean Whitton  (supplier of updated dash-el 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, 20 Sep 2022 13:56:45 -0700
Source: dash-el
Architecture: source
Version: 2.19.1+git20220608.1.0ac1ecf+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen team 
Changed-By: Sean Whitton 
Closes: 1020038
Changes:
 dash-el (2.19.1+git20220608.1.0ac1ecf+dfsg-1) unstable; urgency=medium
 .
   * New upstream snapshot (Closes: #1020038).
Checksums-Sha1:
 ce83c43b521a62d21422f5e96f28a08dd247f658 2272 
dash-el_2.19.1+git20220608.1.0ac1ecf+dfsg-1.dsc
 87bb3fa4f94299f9a676f7343b986a591fc7a1c9 79080 
dash-el_2.19.1+git20220608.1.0ac1ecf+dfsg.orig.tar.xz
 170e7769bb1c7fa53a08eb786205c5c3f17d9583 2956 
dash-el_2.19.1+git20220608.1.0ac1ecf+dfsg-1.debian.tar.xz
Checksums-Sha256:
 e8107526d19ee7e5788b6f282de2eef8550a2b4f9827c40adabb67de30ed9297 2272 
dash-el_2.19.1+git20220608.1.0ac1ecf+dfsg-1.dsc
 4da15adc6dc802687632fc03bf9d4359c24e63f0985f65ca192818e23d9d42d9 79080 
dash-el_2.19.1+git20220608.1.0ac1ecf+dfsg.orig.tar.xz
 1b944274cd56c15ad505bcd31a46733ead23af6e79f53bce96172d776d95c99b 2956 
dash-el_2.19.1+git20220608.1.0ac1ecf+dfsg-1.debian.tar.xz
Files:
 782349b323afc0ac6836ad11cff42af7 2272 lisp optional 
dash-el_2.19.1+git20220608.1.0ac1ecf+dfsg-1.dsc
 a3e10fa30a2b66607930bf13f7bc20d7 79080 lisp optional 
dash-el_2.19.1+git20220608.1.0ac1ecf+dfsg.orig.tar.xz
 b4513b3fe586530a49dfcd4848cccab4 2956 lisp optional 
dash-el_2.19.1+git20220608.1.0ac1ecf+dfsg-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAmMqKZcACgkQaVt65L8G
YkBp2w//QArscR3ve8Gx50itb8PfWTLLkrfi+Av4bqlWjccKWYqZD6SDt6iL25Cc
7DPp5MV/W1lXVufF5OqqhdLfUUjzmokW6oFe8D6HcEdJl7U5Jor7U9GJqNQ3BAA4
e/JBATV16CFbS1Pa2PnwVeGdrRMIs25MEFondwumm3svY0a5AaswIg16LCOa7F3M

Bug#1010289: marked as done (audit: FTBFS: error: cast specifies array type)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2022 23:22:14 +
with message-id 
and subject line Bug#1010289: fixed in audit 1:3.0.7-1.1
has caused the Debian Bug report #1010289,
regarding audit: FTBFS: error: cast specifies array type
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.)


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

>From my build log:

...
Making all in python3
make[6]: Entering directory
'/home/tmpbuilder/cross-i386/audit/audit-3.0.7/debian/build/bindings/swig/python3'
swig -o audit_wrap.c -python -py3 -modern -I. -I../../..
-I../../../../../lib -I/usr/include/python3.10
-I/usr/include/python3.10
../../../../../bindings/swig/python3/../src/auditswig.i
Deprecated command line option: -modern. This option is now always on.
/bin/bash ../../../libtool  --tag=CC   --mode=compile gcc
-DHAVE_CONFIG_H -I. -I../../../../../bindings/swig/python3 -I../../..
-I. -I../../.. -I../../../../../lib -I/usr/include/python3.10
-I/usr/include/python3.10 -Wdate-time -D_FORT
IFY_SOURCE=2 -shared -g -O2
-ffile-prefix-map=/home/tmpbuilder/cross-i386/audit/audit-3.0.7=.
-fstack-protector-strong -Wformat -Werror=format-security -c -o
_audit_la-audit_wrap.lo `test -f 'audit_wrap.c' || echo
'../../../../../bindin
gs/swig/python3/'`audit_wrap.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I.
-I../../../../../bindings/swig/python3 -I../../.. -I. -I../../..
-I../../../../../lib -I/usr/include/python3.10
-I/usr/include/python3.10 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
-ffile-prefix-ma
p=/home/tmpbuilder/cross-i386/audit/audit-3.0.7=.
-fstack-protector-strong -Wformat -Werror=format-security -c
audit_wrap.c  -fPIC -DPIC -o .libs/_audit_la-audit_wrap.o
audit_wrap.c: In function '_wrap_audit_rule_data_buf_set':
audit_wrap.c:4701:17: error: cast specifies array type
4701 | arg1->buf = (char [])(char
*)memcpy(malloc((size)*sizeof(char)), (const char *)(arg2),
sizeof(char)*(size));
 | ^
audit_wrap.c:4701:15: error: invalid use of flexible array member
4701 | arg1->buf = (char [])(char
*)memcpy(malloc((size)*sizeof(char)), (const char *)(arg2),
sizeof(char)*(size));
 |   ^
audit_wrap.c:4703:15: error: invalid use of flexible array member
4703 | arg1->buf = 0;
 |   ^
make[6]: *** [Makefile:518: _audit_la-audit_wrap.lo] Error 1
make[6]: Leaving directory
'/home/tmpbuilder/cross-i386/audit/audit-3.0.7/debian/build/bindings/swig/python3'
make[5]: *** [Makefile:417: all-recursive] Error 1
make[5]: Leaving directory
'/home/tmpbuilder/cross-i386/audit/audit-3.0.7/debian/build/bindings/swig'
make[4]: *** [Makefile:414: all-recursive] Error 1
make[4]: Leaving directory
'/home/tmpbuilder/cross-i386/audit/audit-3.0.7/debian/build/bindings'
make[3]: *** [Makefile:471: all-recursive] Error 1
make[3]: Leaving directory
'/home/tmpbuilder/cross-i386/audit/audit-3.0.7/debian/build'
make[2]: *** [Makefile:403: all] Error 2
make[2]: Leaving directory
'/home/tmpbuilder/cross-i386/audit/audit-3.0.7/debian/build'
dh_auto_build: error: cd debian/build && make -j8 returned exit code 2
make[1]: *** [debian/rules:64: debian/build-python-stamp] Error 2
make[1]: Leaving directory '/home/tmpbuilder/cross-i386/audit/audit-3.0.7'
make: *** [debian/rules:34: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned
exit status 2

Looking at the situation a bit, it seems that a recent update to
/usr/include/linux/audit.h made a change such that struct
audit_rule_data is no longer swig friendly.
-- 
Daniel Schepler
--- End Message ---
--- Begin Message ---
Source: audit
Source-Version: 1:3.0.7-1.1
Done: Paul Gevers 

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated audit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 20 Sep 2022 21:05:52 +0200
Source: audit
Architecture: source

Processed: block 1020389

[Debian Bug Tracking System]

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

> block 1020389 by 1020312 926699 1019985 1019506
Bug #1020389 [init-system-helpers] init-system-helpers: block migration waiting 
for #926699 #1020312 #1019985 #1019506
1020389 was not blocked by any bugs.
1020389 was not blocking any bugs.
Added blocking bug(s) of 1020389: 1019985, 1020228, 926699, 1020312, and 1019506
> thanks
Stopping processing here.

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

Bug#1020389: init-system-helpers: block migration waiting for #926699 #1020312 #1019985 #1019506

[Luca Boccassi]

Package: init-system-helpers
Version: 1.65
Severity: grave
Justification: waiting for usrmerge fixes to migrate

Temporarily block migration until the following fixes have migrated to
testing:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020312
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926699
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019985
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019506

-- 
Kind regards,
Luca Boccassi


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

Bug#1019855: Fwd: libc6: immediately crashes with SIGILL on 4th gen Intel Core CPUs (seems related to AVX2 instructions), bricking the whole system

[Aurelien Jarno]

Hi,

Have you been able to progress on that? Do you need some help for a
specific step?

Regards
Aurelien

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

Bug#926699: marked as pending in glibc

[Aurelien Jarno]

Control: tag -1 pending

Hello,

Bug #926699 in glibc 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/glibc-team/glibc/-/commit/cf50a0b40745966ab86ece3afe7c6baa56b14813


libc6-: create merged-usr symlinks via preinst

There is a corner case on a merged-usr system that affects users
installing and then removing a libc6- package: the top-level
symlink gets removed, as the library is usually the last package to
install files there.

Add a preinst snippet that, if the system is merged-usr, creates the
top-level symlink used by the package. This way if it gets installed
and then removed, and then installed again, everything will work.
Note that this does not implement the full conversion, as that's the
responsibility of the usrmerge package (moving files, etc) - this
simply deals with the common case of the missing symlink.

Once all packages ship only files under /usr, hopefully in Trixie,
this can be removed.

Closes: #926699


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/926699

Processed: Bug#926699 marked as pending in glibc

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #926699 [debootstrap,usrmerge] libc6 foreign/biarch: installing, removing, 
reinstalling in a --merged-usr system results in unmerged /lib{32,x32}
Added tag(s) pending.

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

Bug#1010289: audit: FTBFS: error: cast specifies array type

[Paul Gevers]

Hi

On 20-09-2022 22:20, Graham Inggs wrote:

I think we should follow Ubuntu here.


I have uploaded the same and pushed the changes to the salsa repository 
of audit.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1010289: audit: FTBFS: error: cast specifies array type

[Graham Inggs]

Hi Paul

On Tue, 20 Sept 2022 at 21:30, Paul Gevers  wrote:
> I'm not sure how to pick either solution. (At least one member of)
> Upstream seems to think that the Fedora way is better. What do you think?

Upstream wrote "The function that is failing to build looks like it
was never used because the code is completely wrong" [1]
and later they mention the PR #253 (which Ubuntu used) alongside a
link to the mailing list [2].

I think we should follow Ubuntu here.

Regards
Graham


[1] 
https://github.com/linux-audit/audit-userspace/issues/252#issuecomment-1078595249
[2] 
https://github.com/linux-audit/audit-userspace/issues/265#issuecomment-1146603552

Bug#1010289: audit: FTBFS: error: cast specifies array type

[Paul Gevers]

Hi all,

On 20-09-2022 10:34, Graham Inggs wrote:

fwiw, Ubuntu went with a different solution, see diff at:

https://launchpad.net/ubuntu/+source/audit/1:3.0.7-1ubuntu1


I'm not sure how to pick either solution. (At least one member of) 
Upstream seems to think that the Fedora way is better. What do you think?


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1014211: marked as done (apertium-fra-cat: FTBFS: Error (line 229): Invalid construction.)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2022 19:19:47 +
with message-id 
and subject line Bug#1014211: fixed in apertium-fra-cat 1.10.0-1
has caused the Debian Bug report #1014211,
regarding apertium-fra-cat: FTBFS: Error (line 229): Invalid construction.
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.)


-- 
1014211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014211
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apertium-fra-cat
Version: 1.9.0-2
Severity: serious
Justification: FTBFS

1.9.0-2 version fails to build with the following error:

lrx-comp .deps/apertium-fra-cat.cat-fra.lrx cat-fra.autolex.bin
Error (line 229): Invalid construction.
make[2]: *** [Makefile:864: cat-fra.autolex.bin] Error 1
make[2]: *** Waiting for unfinished jobs
apostrophes@postblank 713 1082
final@inconditional 7 17
main@standard 83221 173892
regexp@standard 134 4862
rm .deps/apertium-fra-cat.fra-cat.metalrx .deps/apertium-fra-cat.cat-fra.metalrx
make[2]: Leaving directory
'/builds/science-team/apertium-fra-cat/debian/output/source_dir'
dh_auto_build: error: make -j2 returned exit code 2
make[1]: *** [debian/rules:27: override_dh_auto_build] Error 25
make[1]: Leaving directory
'/builds/science-team/apertium-fra-cat/debian/output/source_dir'
make: *** [debian/rules:14: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full log: https://salsa.debian.org/science-team/apertium-fra-cat/-/jobs/2940030

-- 
Kartik Mistry | કાર્તિક મિસ્ત્રી
kartikm.wordpress.com
--- End Message ---
--- Begin Message ---
Source: apertium-fra-cat
Source-Version: 1.10.0-1
Done: Tino Didriksen 

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

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

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

Debian distribution maintenance software
pp.
Tino Didriksen  (supplier of updated apertium-fra-cat 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 29 Aug 2022 15:25:11 +0200
Source: apertium-fra-cat
Architecture: source
Version: 1.10.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Tino Didriksen 
Closes: 1014211
Changes:
 apertium-fra-cat (1.10.0-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #1014211)
   * Bundles apertium-fra 1.11.0 and apertium-cat 2.10.3
Checksums-Sha1:
 e9ba271eccf598f4c53f3c23dc1bf7c9677f1492 2198 apertium-fra-cat_1.10.0-1.dsc
 9717b6b9fcbab4b4bd7310ce23432a6ee4720a91 2948231 
apertium-fra-cat_1.10.0.orig.tar.bz2
 8588bf7dd4bd4d76c7cb09365166c0c236011e7e 3680 
apertium-fra-cat_1.10.0-1.debian.tar.xz
 3b09175d40d1804d760388142a51194c8229f37a 6951 
apertium-fra-cat_1.10.0-1_source.buildinfo
Checksums-Sha256:
 70b5a0f63fbd977e9f57fad53143ff16185fcb5422d4a4e2dc82426e380a3a86 2198 
apertium-fra-cat_1.10.0-1.dsc
 6b64263c96672c936334cffd8da203d36c3f3240f89a5989a20e111c6e9b7f08 2948231 
apertium-fra-cat_1.10.0.orig.tar.bz2
 3adab71b3d7d0e24f469954fcd6d1032efe63701b3d5d94e9fb7cccb5a8aa59c 3680 
apertium-fra-cat_1.10.0-1.debian.tar.xz
 17ba1f8fe9efd5a2c6f8e20385eb3b07ac680b13bd6dd762e4906bbc1a90b27e 6951 
apertium-fra-cat_1.10.0-1_source.buildinfo
Files:
 59252109549778da4da233d1c1df26f0 2198 science optional 
apertium-fra-cat_1.10.0-1.dsc
 1815e678d554fdf9b60c922a1a41c494 2948231 science optional 
apertium-fra-cat_1.10.0.orig.tar.bz2
 c1c41bc3d4430889d1fb5a978bf2279b 3680 science optional 
apertium-fra-cat_1.10.0-1.debian.tar.xz
 a9ed2f2fb8ee5717e5927df0f64be774 6951 science optional 
apertium-fra-cat_1.10.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEPM9UTIHRuWAtu3CGuXR64aaovegFAmMqDgASHHRpbm9AZGlk
cmlrc2VuLmNjAAoJELl0euGmqL3oP38P/iUzgcQ0dkBBRYvrZwFHFnvGBHWePn52
Bkg1qHSD/nIQUJX0iv+Qm32MXsW+XWr+wBZr87BRksAn4yDsvIg/uaqCDCmcbNLI
xgc0i5AtFTe+h4mLqIuaMCSZKTcfavrd8AJVu6bQN5I9Sy6/JX005kSv6uRvd40k
6KTA5MWsB82EytchKVd0va+MNVx0WoHEysENpLbOYBlLqKEPASzw9RkFnLop17la
rE1dSDvl0vlHEr/ueT9zlHPAZ8PGAorg5cdyPsc3y/ha7f9eBMw0uHH8H8hizsIO
Ox0FnyD5jolp9zjveY7k55pQq5H9WNB8Q2NkxlTM5HdSitd0ksvdx0wME/jyl7h7
K4+eAd/Vn3Id/BLc894NJZrDpumeTN61xHtuANXBXdx3hHju3wnMHOZspdbXryQl

Bug#1013018: marked as done (pstoedit: ftbfs with GCC-12)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2022 19:07:38 +
with message-id 
and subject line Bug#1013018: fixed in pstoedit 3.78-2
has caused the Debian Bug report #1013018,
regarding pstoedit: ftbfs with GCC-12
to be marked as done.

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

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


-- 
1013018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013018
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pstoedit
Version: 3.78-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12

[This bug is targeted to the upcoming bookworm 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-12/g++-12, but succeeds to build with gcc-11/g++-11. The
severity of this report will be raised before the bookworm release.

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/pstoedit_3.78-1_unstable_gcc12.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
/bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I.  
-DHAVE_LIBPLOTTER  -DHAVE_MKSTEMP -DHAVE_MAGIC -fopenmp 
-DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp 
-DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp 
-DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 
-I/usr/include/x86_64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 
-I/usr/include/x86_64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 
-I/usr/include/x86_64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 
-DHAVE_LIBEMF  -DHAVE_LIBZIP -DDEFAULTGS=gs 
-DPSTOEDITDATADIR="\"/usr/share/pstoedit\"" 
-DPSTOEDITLIBDIR="\"/usr/lib/x86_64-linux-gnu/pstoedit\"" -Wall -Wextra 
-Wuninitialized -Wswitch-default -Wunused -Wshadow -Wwrite-strings -Wcast-qual 
-Wpointer-arith -Wno-long-long -Wdate-time -D_FORTIFY_SOURCE=2 -D_LITTLE_ENDIAN 
 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,--as-needed -Wl,-O1 -DINT
 ERNALBOOL -c -o drvgschem.lo drvgschem.cpp
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -DHAVE_LIBPLOTTER -DHAVE_MKSTEMP 
-DHAVE_MAGIC -fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 
-fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp 
-DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 
-I/usr/include/x86_64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 
-I/usr/include/x86_64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 
-I/usr/include/x86_64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 
-DHAVE_LIBEMF -DHAVE_LIBZIP -DDEFAULTGS=gs 
-DPSTOEDITDATADIR=\"/usr/share/pstoedit\" 
-DPSTOEDITLIBDIR=\"/usr/lib/x86_64-linux-gnu/pstoedit\" -Wall -Wextra 
-Wuninitialized -Wswitch-default -Wunused -Wshadow -Wwrite-strings -Wcast-qual 
-Wpointer-arith -Wno-long-long -Wdate-time -D_FORTIFY_SOURCE=2 -D_LITTLE_ENDIAN 
-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,--as-needed -Wl,-O1 -DINTERNALBOOL -c drvgschem.cpp 
 -fPIC -DPI
 C -o .libs/drvgschem.o
/bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I.  
-DHAVE_LIBPLOTTER  -DHAVE_MKSTEMP -DHAVE_MAGIC -fopenmp 
-DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp 
-DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp 
-DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 
-I/usr/include/x86_64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 
-I/usr/include/x86_64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 
-I/usr/include/x86_64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 
-DHAVE_LIBEMF  -DHAVE_LIBZIP -DDEFAULTGS=gs 

Processed: Re: utf8proc: build-depends on unicode-data (< 14.1) but Unstable has 15.0.0-1

[Debian Bug Tracking System]

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

> forwarded 1019923 https://github.com/JuliaStrings/utf8proc/issues/246
Bug #1019923 [src:utf8proc] utf8proc: build-depends on unicode-data (< 14.1) 
but Unstable has 15.0.0-1
Set Bug forwarded-to-address to 
'https://github.com/JuliaStrings/utf8proc/issues/246'.
>
End of message, stopping processing here.

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

Processed: update bts meta info

[Debian Bug Tracking System]

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

> reassign 1019393 src:libsis-jhdf5-java 19.04.1+dfsg-1
Bug #1019393 {Done: Pierre Gruet } [src:hdf5, 
src:libsis-jhdf5-java] hdf5 breaks libsis-jhdf5-java autopkgtest: Could not 
initialize class
Bug reassigned from package 'src:hdf5, src:libsis-jhdf5-java' to 
'src:libsis-jhdf5-java'.
No longer marked as found in versions libsis-jhdf5-java/19.04.1+dfsg-1 and 
hdf5/1.10.8+repack-1.
No longer marked as fixed in versions libsis-jhdf5-java/19.04.1+dfsg-2.
Bug #1019393 {Done: Pierre Gruet } [src:libsis-jhdf5-java] 
hdf5 breaks libsis-jhdf5-java autopkgtest: Could not initialize class
Marked as found in versions libsis-jhdf5-java/19.04.1+dfsg-1.
> affects 1019393 src:hdf5
Bug #1019393 {Done: Pierre Gruet } [src:libsis-jhdf5-java] 
hdf5 breaks libsis-jhdf5-java autopkgtest: Could not initialize class
Added indication that 1019393 affects src:hdf5
> fixed 1019393 19.04.1+dfsg-2
Bug #1019393 {Done: Pierre Gruet } [src:libsis-jhdf5-java] 
hdf5 breaks libsis-jhdf5-java autopkgtest: Could not initialize class
Marked as fixed in versions libsis-jhdf5-java/19.04.1+dfsg-2.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1020085: python-astor: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 returned exit code 13

[Debian Bug Tracking System]

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

> forwarded 1020085 https://github.com/berkerpeksag/astor/issues/212
Bug #1020085 [src:python-astor] python-astor: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p 3.10 returned exit code 13
Ignoring request to change the forwarded-to-address of bug#1020085 to the same 
value
> thanks
Stopping processing here.

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

Bug#1020085: python-astor: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 returned exit code 13

[Tianon Gravi]

forwarded 1020085 https://github.com/berkerpeksag/astor/issues/212
thanks

On Sat, 17 Sept 2022 at 23:45, Lucas Nussbaum  wrote:
> > p = <[ValueError('Exceeds the limit (4300) for integer string conversion') 
> > raised in repr()] int object at 0x556a03b67200>
> > imaginary = False
> >
> > def part(p, imaginary):
> > # Represent infinity as 1e1000 and NaN as 1e1000-1e1000.
> > s = 'j' if imaginary else ''
> > try:
> > if math.isinf(p):
> > if p < 0:
> > return '-1e1000' + s
> > return '1e1000' + s
> > if math.isnan(p):
> > return '(1e1000%s-1e1000%s)' % (s, s)
> > except OverflowError:
> > # math.isinf will raise this when given an integer
> > # that's too large to convert to a float.
> > pass
> > >   return repr(p) + s
> > E   ValueError: Exceeds the limit (4300) for integer string conversion

Looks like this is known upstream (see forwarded URL above), but there
isn't a fix yet. :(

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

Processed: src:markdown-it-py: fails to migrate to testing for too long: uploader built arch:all binaries

[Debian Bug Tracking System]

Processing control commands:

> close -1 2.1.0-3
Bug #1020379 [src:markdown-it-py] src:markdown-it-py: fails to migrate to 
testing for too long: uploader built arch:all binaries
Marked as fixed in versions markdown-it-py/2.1.0-3.
Bug #1020379 [src:markdown-it-py] src:markdown-it-py: fails to migrate to 
testing for too long: uploader built arch:all binaries
Marked Bug as done

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

Processed: src:fast-histogram: fails to migrate to testing for too long: unresolved RC bug

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.11-1
Bug #1020378 [src:fast-histogram] src:fast-histogram: fails to migrate to 
testing for too long: unresolved RC bug
Marked as fixed in versions fast-histogram/0.11-1.
Bug #1020378 [src:fast-histogram] src:fast-histogram: fails to migrate to 
testing for too long: unresolved RC bug
Marked Bug as done
> block -1 by 1015929
Bug #1020378 {Done: Paul Gevers } [src:fast-histogram] 
src:fast-histogram: fails to migrate to testing for too long: unresolved RC bug
1020378 was not blocked by any bugs.
1020378 was not blocking any bugs.
Added blocking bug(s) of 1020378: 1015929

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

Bug#1020379: src:markdown-it-py: fails to migrate to testing for too long: uploader built arch:all binaries

[Paul Gevers]

Source: markdown-it-py
Version: 2.1.0-2
Severity: serious
Control: close -1 2.1.0-3
Tags: sid bookworm pending
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 60 days as having a Release Critical bug in 
testing [1]. Your package src:markdown-it-py has been trying to migrate 
for 61 days [2]. Hence, I am filing this bug.


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 bookworm, so 
it doesn't affect (old-)stable.


Your package is only blocked because the arch:all binary package(s) 
aren't built on a buildd. Unfortunately the Debian infrastructure 
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will 
shortly do a no-changes source-only upload to DELAYED/15, closing this 
bug. Please let me know if I should delay or cancel that upload.


Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=markdown-it-py



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1020378: src:fast-histogram: fails to migrate to testing for too long: unresolved RC bug

[Paul Gevers]

Source: fast-histogram
Version: 0.9-2
Severity: serious
Control: close -1 0.11-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1015929

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:fast-histogram has been trying to migrate 
for 61 days [2]. Hence, I am filing this bug. Your package in unstable 
has an unresolved RC bug.


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 bookworm, 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/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=fast-histogram



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:bnfc: fails to migrate to testing for too long: part of unfinshed ghc transition

[Debian Bug Tracking System]

Processing control commands:

> close -1 2.9.4-1
Bug #1020377 [src:bnfc] src:bnfc: fails to migrate to testing for too long: 
part of unfinshed ghc transition
Marked as fixed in versions bnfc/2.9.4-1.
Bug #1020377 [src:bnfc] src:bnfc: fails to migrate to testing for too long: 
part of unfinshed ghc transition
Marked Bug as done

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

Bug#1020377: src:bnfc: fails to migrate to testing for too long: part of unfinshed ghc transition

[Paul Gevers]

Source: bnfc
Version: 2.8.3-1
Severity: serious
Control: close -1 2.9.4-1
Tags: sid bookworm
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 60 days as having a Release Critical bug in 
testing [1]. Your package src:bnfc has been trying to migrate for 61 
days [2]. Hence, I am filing this bug. Your package is part of the 
unfinished ghc transition.


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 bookworm, 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/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=bnfc



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1004634: openscenegraph: FTBFS with ffmpeg 5.0

[Ying-Chun Liu (PaulLiu)]

Hi all,

I've patched the audio part. But not completed. The video part needs 
more changes. But I don't have enough time now.


Just attach the partial patch I made so that when someone has time or I 
have time then we can continue it.


Yours,
Paul
Index: openscenegraph-3.6.5+dfsg1/src/osgPlugins/ffmpeg/FFmpegDecoderAudio.cpp
===
--- openscenegraph-3.6.5+dfsg1.orig/src/osgPlugins/ffmpeg/FFmpegDecoderAudio.cpp
+++ openscenegraph-3.6.5+dfsg1/src/osgPlugins/ffmpeg/FFmpegDecoderAudio.cpp
@@ -45,12 +45,19 @@ static int decode_audio(AVCodecContext *
 if (!frame)
 return AVERROR(ENOMEM);
 
-ret = avcodec_decode_audio4(avctx, frame, _frame, );
+ret = avcodec_send_packet(avctx, );
+if (ret >= 0) {
+  ret = avcodec_receive_frame(avctx, frame);
+  if (ret == 0) {
+	got_frame = 1;
+  }
+}
+  
 
 #ifdef USE_AVRESAMPLE// libav's AVFrame structure does not contain a 'channels' field
 if (ret >= 0 && got_frame) {
 #else
-if (ret >= 0 && got_frame && av_frame_get_channels(frame)>0) {
+if (ret >= 0 && got_frame && frame->ch_layout.nb_channels>0) {
 #endif
 int ch, plane_size;
 int planar = av_sample_fmt_is_planar(avctx->sample_fmt);
@@ -151,11 +158,13 @@ void FFmpegDecoderAudio::open(AVStream *
 return;
 
 m_stream = stream;
-m_context = stream->codec;
-
-m_in_sample_rate = m_context->sample_rate;
-m_in_nb_channels = m_context->channels;
-m_in_sample_format = m_context->sample_fmt;
+	AVCodecParameters* avp = stream->codecpar;
+const AVCodec * p_codec = avcodec_find_decoder(avp->codec_id);
+	m_context = avcodec_alloc_context3(p_codec);	  
+
+m_in_sample_rate = avp->sample_rate;
+m_in_nb_channels = avp->channels;
+m_in_sample_format = ((AVSampleFormat)(avp->format));
 
 AVDictionaryEntry *opt_out_sample_rate = av_dict_get( *parameters->getOptions(), "out_sample_rate", NULL, 0 );
 if ( opt_out_sample_rate )
@@ -210,11 +219,10 @@ printf("### CONVERTING from sample forma
 }
 
 // Check stream sanity
-if (m_context->codec_id == AV_CODEC_ID_NONE)
+if (avp->codec_id == AV_CODEC_ID_NONE)
 throw std::runtime_error("invalid audio codec");;
 
 // Find the decoder for the audio stream
-AVCodec * const p_codec = avcodec_find_decoder(m_context->codec_id);
 
 if (p_codec == 0)
 throw std::runtime_error("avcodec_find_decoder() failed");
Index: openscenegraph-3.6.5+dfsg1/src/osgPlugins/ffmpeg/FFmpegPacket.hpp
===
--- openscenegraph-3.6.5+dfsg1.orig/src/osgPlugins/ffmpeg/FFmpegPacket.hpp
+++ openscenegraph-3.6.5+dfsg1/src/osgPlugins/ffmpeg/FFmpegPacket.hpp
@@ -42,7 +42,7 @@ namespace osgFFmpeg
 void clear()
 {
 if (packet.data != 0)
-av_free_packet();
+av_packet_unref();
 
 release();
 }


OpenPGP_0x44173FA13D05.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1020082: scons: FTBFS: make: *** [debian/rules:10: binary] Error 25

[GCS]

On Tue, Sep 20, 2022 at 7:26 PM Bill Deegan  wrote:
> Not sure I entirely understand.
> Are you saying that SCons 4.4.0 is installing something in /usr/local/bin 
> instead of /usr/bin/ ?
 Yes, all executables go to /usr/local/bin directory.

> What command are you using to install SCons which is causing this?
 I downloaded the Git tag 4.4.0 from GitHub. Then:
$ tar zxf 4.4.0.tar.gz
$ cd scons-4.4.0/
$ touch scons.1 sconsign.1 scons-time.1
$ mkdir out/
$ python3 setup.py install --prefix=/usr
--install-data=/usr/share/man/man1/ --root=out/

Output ends with:
reating out/usr/share
creating out/usr/share/man
creating out/usr/share/man/man1
copying scons.1 -> out/usr/share/man/man1/.
copying scons-time.1 -> out/usr/share/man/man1/.
copying sconsign.1 -> out/usr/share/man/man1/.
running install_egg_info
Copying SCons.egg-info to
out/usr/local/lib/python3.10/dist-packages/SCons-4.4.0-py3.10.egg-info
running install_scripts
Installing scons script to out/usr/local/bin
Installing scons-configure-cache script to out/usr/local/bin
Installing sconsign script to out/usr/local/bin

Additional info: python3 --version
Python 3.10.7

Currently I don't know where the additional local subdirectory comes from.

Regards,
Laszlo/GCS

Bug#1013504: marked as done (ruby-tilt: FTBFS: ERROR: Test "ruby3.0" failed. Exiting.)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2022 17:33:38 +
with message-id 
and subject line Bug#1013504: fixed in ruby-tilt 2.0.10-3
has caused the Debian Bug report #1013504,
regarding ruby-tilt: FTBFS: ERROR: Test "ruby3.0" failed. Exiting.
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.)


-- 
1013504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013504
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-tilt
Version: 2.0.10-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> SyntaxError: Unexpected token 'export'
> at Object.compileFunction (node:vm:352:18)
> at wrapSafe (node:internal/modules/cjs/loader:1033:15)
> at Module._compile (node:internal/modules/cjs/loader:1069:27)
> at Object.Module._extensions..js 
> (node:internal/modules/cjs/loader:1159:10)
> at Module.load (node:internal/modules/cjs/loader:981:32)
> at Function.Module._load (node:internal/modules/cjs/loader:822:12)
> at Function.executeUserEntryPoint [as runMain] 
> (node:internal/modules/run_main:77:12)
> at node:internal/main/run_main_module:17:47
> 
> (execjs):1
> /usr/lib/ruby/vendor_ruby/execjs/external_runtime.rb:219:in `exec_runtime'
> /usr/lib/ruby/vendor_ruby/execjs/external_runtime.rb:39:in `exec'
> /usr/lib/ruby/vendor_ruby/execjs/external_runtime.rb:14:in `initialize'
> /usr/lib/ruby/vendor_ruby/execjs/runtime.rb:72:in `new'
> /usr/lib/ruby/vendor_ruby/execjs/runtime.rb:72:in `compile'
> /usr/lib/ruby/vendor_ruby/execjs/module.rb:27:in `compile'
> /usr/lib/ruby/vendor_ruby/coffee_script.rb:50:in `context'
> /usr/lib/ruby/vendor_ruby/coffee_script.rb:78:in `compile'
> 
> /<>/debian/ruby-tilt/usr/lib/ruby/vendor_ruby/tilt/coffee.rb:44:in
>  `evaluate'
> 
> /<>/debian/ruby-tilt/usr/lib/ruby/vendor_ruby/tilt/template.rb:109:in
>  `render'
> /<>/test/tilt_coffeescripttemplate_test.rb:62:in `block (3 
> levels) in included'
> 
> 237 runs, 359 assertions, 0 failures, 18 errors, 0 skips
> rake aborted!
> Command failed with status (1): [ruby -w -I"test" 
> /usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb
>  "test/tilt_asciidoctor_test.rb" "test/tilt_blueclothtemplate_test.rb" 
> "test/tilt_buildertemplate_test.rb" "test/tilt_cache_test.rb" 
> "test/tilt_coffeescripttemplate_test.rb" 
> "test/tilt_commonmarkertemplate_test.rb" "test/tilt_compilesite_test.rb" 
> "test/tilt_creoletemplate_test.rb" "test/tilt_csv_test.rb" 
> "test/tilt_erbtemplate_test.rb" "test/tilt_erubistemplate_test.rb" 
> "test/tilt_erubitemplate_test.rb" "test/tilt_etannitemplate_test.rb" 
> "test/tilt_hamltemplate_test.rb" "test/tilt_kramdown_test.rb" 
> "test/tilt_lesstemplate_test.rb" "test/tilt_liquidtemplate_test.rb" 
> "test/tilt_livescripttemplate_test.rb" "test/tilt_mapping_test.rb" 
> "test/tilt_markaby_test.rb" "test/tilt_markdown_test.rb" 
> "test/tilt_marukutemplate_test.rb" "test/tilt_metadata_test.rb" 
> "test/tilt_nokogiritemplate_test.rb" "test/tilt_pandoctemplate_test.rb" 
> "test/tilt_prawntemplate_test.rb" "test/tilt_radiustemplate_test.rb" 
> "test/tilt_rdiscounttemplate_test.rb" "test/tilt_rdoctemplate_test.rb" 
> "test/tilt_redcarpettemplate_test.rb" "test/tilt_redclothtemplate_test.rb" 
> "test/tilt_rstpandoctemplate_test.rb" "test/tilt_sasstemplate_test.rb" 
> "test/tilt_sigil_test.rb" "test/tilt_stringtemplate_test.rb" 
> "test/tilt_template_test.rb" "test/tilt_test.rb" 
> "test/tilt_typescript_test.rb" "test/tilt_wikiclothtemplate_test.rb" 
> "test/tilt_yajltemplate_test.rb" -v]
> /usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in ` (required)>'
> Tasks: TOP => default
> (See full trace by running task with --trace)
> ERROR: Test "ruby3.0" failed. Exiting.
> dh_auto_install: error: dh_ruby --install /<>/debian/ruby-tilt 
> returned exit code 1
> make: *** [debian/rules:17: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/06/24/ruby-tilt_2.0.10-2_unstable.log

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

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

If you 

Bug#1020082: scons: FTBFS: make: *** [debian/rules:10: binary] Error 25

[Bill Deegan]

Not sure I entirely understand.
Are you saying that SCons 4.4.0 is installing something in /usr/local/bin
instead of /usr/bin/ ?
What command are you using to install SCons which is causing this?

On Tue, Sep 20, 2022 at 9:41 AM László Böszörményi (GCS) 
wrote:

> On Sun, Sep 18, 2022 at 6:42 PM Bill Deegan 
> wrote:
> > SCons 4.0.1 is fairly old and doesn't seem to be compatible with Python
> 3.10.
> > The latest SCons 4.4.0 is available and works fine with Python 3.10
>  Actually it's not a compatibility issue, but a behaviour change with
> Python 3.10 as I know. It (or some module) now installs binaries into
> /usr/local/bin instead of the normal /usr/bin path.
> Packaged SCons 4.4.0 and it fails the same way due to installing
> binaries under /usr/local/bin directory. For the moment I don't know
> how to skip 'local' from the installation path, but will move back
> binaries directly after installation.
>
> Regards,
> Laszlo/GCS
>

Bug#1012665: marked as done (coreutils: wrong GFDL version)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2022 17:21:59 +
with message-id 
and subject line Bug#1012665: fixed in coreutils 9.1-1
has caused the Debian Bug report #1012665,
regarding coreutils: wrong GFDL version
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.)


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

Source: coreutils
Version: 8.32-4.1
Severity: serious
Justification: Policy violation
Tags: patch

The GFDL version of the published package version is 1.3, not 1.2 as claimed by 
coreutils.copyright.

I have attached a patch that places a machine-readable copyright file in 
debian/copyright
instead of referencing the *.copyright files of (some non-existing) binary 
packages.
The GFDL-NIV-1.3 license boilerplate is replaced by one in 
coreutils_8.32.orig.tar.xz.diff -Nru coreutils-8.32/debian/copyright coreutils-8.32/debian/copyright
--- coreutils-8.32/debian/copyright 2016-01-25 16:42:26.0 +0100
+++ coreutils-8.32/debian/copyright 2022-06-11 14:09:27.0 +0200
@@ -1,4 +1,124 @@
-Coreutils itself is generally copyrighted under the terms of the GNU General
-Public License. Specific copyrights can be found in the coreutils.copyright
-file and the *.copyright files for other packages included within the coreutils
-source package. (Generally, these are trivial transitional packages.)
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Comment: This is the Debian GNU/Linux packaged version of the GNU core
+ utilities.
+ This package is maintained by Michael Stone .
+ See the file AUTHORS for a list of each program's main authors.
+Source: ftp://ftp.gnu.org/gnu/coreutils
+
+Files: *
+Copyright: (C) 1984-2008 Free Software Foundation, Inc.
+License: GPL-3+
+
+Files: lib/fts.c
+   lib/fts_.h
+Copyright: (C) 2004-2020, 2008 Free Software Foundation, Inc.
+   (c) 1989, 1990, 1993, 1994  The Regents of the University of 
California.  All rights reserved.
+License: GPL-3+ and BSD-4-clause-UC
+
+License: GPL-3+
+   This program is free software: you can redistribute it and/or modify
+   it under the terms of the GNU General Public License as published by
+   the Free Software Foundation; either version 3 of the License, or
+   (at your option) any later version.
+ .
+   This program is distributed in the hope that it will be useful,
+   but WITHOUT ANY WARRANTY; without even the implied warranty of
+   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+   GNU General Public License for more details.
+ .
+   You should have received a copy of the GNU General Public License
+   along with this program.  If not, see .
+ .
+ On Debian systems, the complete text of the GNU General
+ Public License can be found in `/usr/share/common-licenses/GPL-3'.
+
+License: BSD-4-clause-UC
+ * Redistribution and use in source and binary forms, with or without
+ * modification, are permitted provided that the following conditions
+ * are met:
+ * 1. Redistributions of source code must retain the above copyright
+ *notice, this list of conditions and the following disclaimer.
+ * 2. Redistributions in binary form must reproduce the above copyright
+ *notice, this list of conditions and the following disclaimer in the
+ *documentation and/or other materials provided with the distribution.
+ * 4. Neither the name of the University nor the names of its contributors
+ *may be used to endorse or promote products derived from this software
+ *without specific prior written permission.
+ *
+ * THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+ * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+ * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ * ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+ * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+ * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+ * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+ * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+ * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+ * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+ * SUCH DAMAGE.
+
+Files: lib/rand-isaac.[ch]
+Copyright: (C) 1999-2006 Free Software Foundation, Inc.
+   (C) 1997, 1998, 1999 Colin Plumb.
+License: GPL-3+
+
+Files: lib/inet_ntop.c
+Copyright: 

Processed: closing 1013658

[Debian Bug Tracking System]

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

> close 1013658 1.9.0-2
Bug #1013658 [src:apertium-fra-cat] apertium-fra-cat: FTBFS: configure: error: 
Package requirements (apertium-lex-tools >= 0.2.3) were not met
The source 'apertium-fra-cat' and version '1.9.0-2' do not appear to match any 
binary packages
Marked as fixed in versions apertium-fra-cat/1.9.0-2.
Bug #1013658 [src:apertium-fra-cat] apertium-fra-cat: FTBFS: configure: error: 
Package requirements (apertium-lex-tools >= 0.2.3) were not met
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1020375: opengv: binary-all FTBFS

[Adrian Bunk]

Source: opengv
Version: 1.0+1git91f4b1-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=opengv=all=1.0%2B1git91f4b1-3=1661457294=0

...
0% tests passed, 18 tests failed out of 18

Total Test time (real) =   0.03 sec

The following tests FAILED:
  1 - test_absolute_pose (Not Run)
  2 - test_absolute_pose_sac (Not Run)
  3 - test_noncentral_absolute_pose (Not Run)
  4 - test_noncentral_absolute_pose_sac (Not Run)
  5 - test_multi_noncentral_absolute_pose_sac (Not Run)
  6 - test_relative_pose (Not Run)
  7 - test_relative_pose_rotationOnly (Not Run)
  8 - test_relative_pose_rotationOnly_sac (Not Run)
  9 - test_relative_pose_sac (Not Run)
 10 - test_noncentral_relative_pose (Not Run)
 11 - test_noncentral_relative_pose_sac (Not Run)
 12 - test_multi_noncentral_relative_pose_sac (Not Run)
 13 - test_eigensolver_sac (Not Run)
 14 - test_triangulation (Not Run)
 15 - test_eigensolver (Not Run)
 16 - test_point_cloud (Not Run)
 17 - test_point_cloud_sac (Not Run)
 18 - test_Sturm (Not Run)
Errors while running CTest
make[1]: *** [Makefile:74: test] Error 8

Processed: Re: Bug#1018882: ruby-vcr: build times out after 150 minutes

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 ruby-vcr FTBFS on IPV6-only buildds
Bug #1018882 [src:ruby-vcr] ruby-vcr: build times out after 150 minutes
Changed Bug title to 'ruby-vcr FTBFS on IPV6-only buildds' from 'ruby-vcr: 
build times out after 150 minutes'.

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

Bug#1018882: ruby-vcr: build times out after 150 minutes

[Adrian Bunk]

Control: retitle -1 ruby-vcr FTBFS on IPV6-only buildds

On Thu, Sep 01, 2022 at 02:08:36PM +0200, Paul Gevers wrote:
> Source: ruby-vcr
> Version: 6.0.0+really5.0.0-2
> Severity: serious
> Tags: ftbfs
> Justification: ftbfs
> 
> Dear maintainers,
> 
> The last upload failed to build from source.
> 
> https://buildd.debian.org/status/fetch.php?pkg=ruby-vcr=all=6.0.0%2Breally5.0.0-3=1661725468=0
> 
>   when VCR.real_http_connections_allowed? is returning false
> does not allow real HTTP requests or record them
> when ignore_hosts is configured to "127.0.0.1", "localhost"
> E: Build killed with signal TERM after 150 minutes of inactivity

This was on x86-conova-01, which is IPV6-only.
Looking at the "127.0.0.1" above, this is likely relevant.

> Paul

cu
Adrian

Bug#1020082: scons: FTBFS: make: *** [debian/rules:10: binary] Error 25

[GCS]

On Sun, Sep 18, 2022 at 6:42 PM Bill Deegan  wrote:
> SCons 4.0.1 is fairly old and doesn't seem to be compatible with Python 3.10.
> The latest SCons 4.4.0 is available and works fine with Python 3.10
 Actually it's not a compatibility issue, but a behaviour change with
Python 3.10 as I know. It (or some module) now installs binaries into
/usr/local/bin instead of the normal /usr/bin path.
Packaged SCons 4.4.0 and it fails the same way due to installing
binaries under /usr/local/bin directory. For the moment I don't know
how to skip 'local' from the installation path, but will move back
binaries directly after installation.

Regards,
Laszlo/GCS

Bug#1017015: [Debian-on-mobile-maintainers] Bug#1017015: gnome-console: bugs after switch to GTK4

[Jeremy Bicha]

On Tue, Sep 20, 2022 at 12:26 PM Arnaud Ferraris  wrote:
> That sounds good, thanks for tracking those issues! IIUC the workaround
> for the remaining issue is using middle-click-paste, is that right?

Yeah, that's probably the easiest workaround. There are a few other
ideas on the upstream bug.

Thank you,
Jeremy Bicha

Bug#1017015: [Debian-on-mobile-maintainers] Bug#1017015: gnome-console: bugs after switch to GTK4

[Arnaud Ferraris]

Hi Jeremy,

Le 20/09/2022 à 00:45, Jeremy Bicha a écrit :

Control: retitle -1 gnome-console: copying won't work if end of line is selected

I intend to lower the severity of this bug to Important once gtk4
migrates to Testing

The Ctrl+Shift bug is fixed in gtk4; the open link bug was fixed in
vte2.91. That only leaves one significant known issue which can be
worked around.


That sounds good, thanks for tracking those issues! IIUC the workaround 
for the remaining issue is using middle-click-paste, is that right?


Cheers,
Arnaud



Thank you,
Jeremy Bicha

___
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#1013504: marked as pending in ruby-tilt

[Lucas Kanashiro]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/ruby-team/ruby-tilt/-/commit/24bfe355097fa2e7dacd805922bcf0bf3bad8048


d/control: do not depend on ruby-coffee-script (Closes: #1013504)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1013504

Processed: Bug#1013504 marked as pending in ruby-tilt

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1013504 [src:ruby-tilt] ruby-tilt: FTBFS: ERROR: Test "ruby3.0" failed. 
Exiting.
Added tag(s) pending.

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

Bug#1020126: marked as done (gitlabracadabra: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.10 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2022 15:40:04 +0200
with message-id 

and subject line Re: Bug#1020126: gitlabracadabra: FTBFS: dh_auto_test: error: 
pybuild --test -i python{version} -p 3.10 returned exit code 13
has caused the Debian Bug report #1020126,
regarding gitlabracadabra: FTBFS: dh_auto_test: error: pybuild --test -i 
python{version} -p 3.10 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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.10_gitlabracadabra/build/gitlabracadabra
> copying gitlabracadabra/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_gitlabracadabra/build/gitlabracadabra
> copying gitlabracadabra/disk_cache.py -> 
> /<>/.pybuild/cpython3_3.10_gitlabracadabra/build/gitlabracadabra
> copying gitlabracadabra/parser.py -> 
> /<>/.pybuild/cpython3_3.10_gitlabracadabra/build/gitlabracadabra
> copying gitlabracadabra/cli.py -> 
> /<>/.pybuild/cpython3_3.10_gitlabracadabra/build/gitlabracadabra
> copying gitlabracadabra/dictutils.py -> 
> /<>/.pybuild/cpython3_3.10_gitlabracadabra/build/gitlabracadabra
> copying gitlabracadabra/matchers.py -> 
> /<>/.pybuild/cpython3_3.10_gitlabracadabra/build/gitlabracadabra
> copying gitlabracadabra/singleton.py -> 
> /<>/.pybuild/cpython3_3.10_gitlabracadabra/build/gitlabracadabra
> copying gitlabracadabra/auth_info.py -> 
> /<>/.pybuild/cpython3_3.10_gitlabracadabra/build/gitlabracadabra
> creating 
> /<>/.pybuild/cpython3_3.10_gitlabracadabra/build/gitlabracadabra/gitlab
> copying gitlabracadabra/gitlab/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_gitlabracadabra/build/gitlabracadabra/gitlab
> copying gitlabracadabra/gitlab/user_cache.py -> 
> /<>/.pybuild/cpython3_3.10_gitlabracadabra/build/gitlabracadabra/gitlab
> copying gitlabracadabra/gitlab/pygit2.py -> 
> /<>/.pybuild/cpython3_3.10_gitlabracadabra/build/gitlabracadabra/gitlab
> copying gitlabracadabra/gitlab/connections.py -> 
> /<>/.pybuild/cpython3_3.10_gitlabracadabra/build/gitlabracadabra/gitlab
> copying gitlabracadabra/gitlab/group_cache.py -> 
> /<>/.pybuild/cpython3_3.10_gitlabracadabra/build/gitlabracadabra/gitlab
> copying gitlabracadabra/gitlab/access_levels.py -> 
> /<>/.pybuild/cpython3_3.10_gitlabracadabra/build/gitlabracadabra/gitlab
> copying gitlabracadabra/gitlab/connection.py -> 
> /<>/.pybuild/cpython3_3.10_gitlabracadabra/build/gitlabracadabra/gitlab
> copying gitlabracadabra/gitlab/pygitlab.py -> 
> /<>/.pybuild/cpython3_3.10_gitlabracadabra/build/gitlabracadabra/gitlab
> creating 
> /<>/.pybuild/cpython3_3.10_gitlabracadabra/build/gitlabracadabra/containers
> copying gitlabracadabra/containers/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_gitlabracadabra/build/gitlabracadabra/containers
> copying gitlabracadabra/containers/registry.py -> 
> /<>/.pybuild/cpython3_3.10_gitlabracadabra/build/gitlabracadabra/containers
> copying gitlabracadabra/containers/with_blobs.py -> 
> /<>/.pybuild/cpython3_3.10_gitlabracadabra/build/gitlabracadabra/containers
> copying gitlabracadabra/containers/scope.py -> 
> /<>/.pybuild/cpython3_3.10_gitlabracadabra/build/gitlabracadabra/containers
> copying gitlabracadabra/containers/manifest.py -> 
> /<>/.pybuild/cpython3_3.10_gitlabracadabra/build/gitlabracadabra/containers
> copying gitlabracadabra/containers/manifest_base.py -> 
> /<>/.pybuild/cpython3_3.10_gitlabracadabra/build/gitlabracadabra/containers
> copying gitlabracadabra/containers/blob.py -> 
> /<>/.pybuild/cpython3_3.10_gitlabracadabra/build/gitlabracadabra/containers
> copying gitlabracadabra/containers/registry_importer.py -> 
> /<>/.pybuild/cpython3_3.10_gitlabracadabra/build/gitlabracadabra/containers
> copying gitlabracadabra/containers/registry_session.py -> 
> /<>/.pybuild/cpython3_3.10_gitlabracadabra/build/gitlabracadabra/containers
> copying 

Processed: Re: Bug#1015864: gr-radar: FTBFS with upcoming doxygen 1.9.4

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 doxygen 1.9.4-1
Bug #1015864 [gr-radar] gr-radar: FTBFS with upcoming doxygen 1.9.4
Bug reassigned from package 'gr-radar' to 'doxygen'.
No longer marked as found in versions gr-radar/0.0.0.20180308-6.
Ignoring request to alter fixed versions of bug #1015864 to the same values 
previously set
Bug #1015864 [doxygen] gr-radar: FTBFS with upcoming doxygen 1.9.4
Marked as found in versions doxygen/1.9.4-1.
> reassign 1015865 doxygen 1.9.4-1
Bug #1015865 [liblog4c3] liblog4c3: FTBFS with upcoming doxygen 1.9.4
Bug reassigned from package 'liblog4c3' to 'doxygen'.
No longer marked as found in versions log4c/1.2.4-2.
Ignoring request to alter fixed versions of bug #1015865 to the same values 
previously set
Bug #1015865 [doxygen] liblog4c3: FTBFS with upcoming doxygen 1.9.4
Marked as found in versions doxygen/1.9.4-1.
> forcemerge -1 1015865
Bug #1015864 [doxygen] gr-radar: FTBFS with upcoming doxygen 1.9.4
Bug #1015865 [doxygen] liblog4c3: FTBFS with upcoming doxygen 1.9.4
Merged 1015864 1015865
> retitle -1 doxygen creates broken Makefiles
Bug #1015864 [doxygen] gr-radar: FTBFS with upcoming doxygen 1.9.4
Bug #1015865 [doxygen] liblog4c3: FTBFS with upcoming doxygen 1.9.4
Changed Bug title to 'doxygen creates broken Makefiles' from 'gr-radar: FTBFS 
with upcoming doxygen 1.9.4'.
Changed Bug title to 'doxygen creates broken Makefiles' from 'liblog4c3: FTBFS 
with upcoming doxygen 1.9.4'.
> affects -1 src:gr-radar src:log4c
Bug #1015864 [doxygen] doxygen creates broken Makefiles
Bug #1015865 [doxygen] doxygen creates broken Makefiles
Added indication that 1015864 affects src:gr-radar and src:log4c
Added indication that 1015865 affects src:gr-radar and src:log4c
> forwarded -1 https://github.com/doxygen/doxygen/pull/9475
Bug #1015864 [doxygen] doxygen creates broken Makefiles
Bug #1015865 [doxygen] doxygen creates broken Makefiles
Set Bug forwarded-to-address to 'https://github.com/doxygen/doxygen/pull/9475'.
Set Bug forwarded-to-address to 'https://github.com/doxygen/doxygen/pull/9475'.

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

Bug#1015864: gr-radar: FTBFS with upcoming doxygen 1.9.4

[Adrian Bunk]

Control: reassign -1 doxygen 1.9.4-1
Control: reassign 1015865 doxygen 1.9.4-1
Control: forcemerge -1 1015865
Control: retitle -1 doxygen creates broken Makefiles
Control: affects -1 src:gr-radar src:log4c
Control: forwarded -1 https://github.com/doxygen/doxygen/pull/9475

On Fri, Jul 22, 2022 at 06:14:48PM +0200, Paolo Greppi wrote:
>...
> The errors were:
> 
> Output written on refman.dvi (479 pages, 4549236 bytes).
> Transcript written on refman.log.
> latex_count=%(LATEX_COUNT) ; \
> while egrep -s 'Rerun (LaTeX|to get cross-references right|to get
> bibliographical references right)' refman.log && [ $latex_count -gt 0 ] ;\
> do \
>   echo "Rerunning latex" ;\
>   latex refman.tex ; \
>   latex_count=`expr $latex_count - 1` ;\
> done
> /bin/sh: 1: Syntax error: "(" unexpected
> make[4]: *** [Makefile:30: refman.dvi] Error 2
> 
> The errors do not occur with the current version of doxygen (1.9.1). I
> attach the build logs.

This is a bug in doxygen, see the pull request above.

> Paolo

cu
Adrian

Bug#1020069: marked as done (ros-angles: FTBFS: error: invalid command 'angles')

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2022 12:02:30 +
with message-id 
and subject line Bug#1020069: fixed in ros-angles 1.16.0-1
has caused the Debian Bug report #1020069,
regarding ros-angles: FTBFS: error: invalid command 'angles'
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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --buildsystem=cmake --sourcedirectory=angles
>dh_update_autotools_config -O--buildsystem=cmake -O--sourcedirectory=angles
>dh_autoreconf -O--buildsystem=cmake -O--sourcedirectory=angles
>dh_auto_configure -O--buildsystem=cmake -O--sourcedirectory=angles
>   cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
> -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
> -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
> -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF 
> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
> -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
> -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" 
> -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
> ../angles
> -- The C compiler identification is GNU 12.2.0
> -- The CXX compiler identification is GNU 12.2.0
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working C compiler: /usr/bin/cc - skipped
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Check for working CXX compiler: /usr/bin/c++ - skipped
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Using CATKIN_DEVEL_PREFIX: /<>/obj-x86_64-linux-gnu/devel
> -- Using CMAKE_PREFIX_PATH: 
> -- Found PythonInterp: /usr/bin/python3 (found suitable version "3.10.7", 
> minimum required is "3") 
> -- Using PYTHON_EXECUTABLE: /usr/bin/python3
> -- Using Debian Python package layout
> -- Using empy: /usr/bin/empy
> -- Using CATKIN_ENABLE_TESTING: ON
> -- Call enable_testing()
> -- Using CATKIN_TEST_RESULTS_DIR: 
> /<>/obj-x86_64-linux-gnu/test_results
> -- GTest is not available. Please install libgtest-dev to enable tests 
> involving GTest.
> -- GMock is not available. Please install libgmock-dev to enable tests 
> involving GMock.
> -- nosetests not found, Python tests can not be run (try installing package 
> 'python3-nose')
> -- Performing Test CMAKE_HAVE_LIBC_PTHREAD
> -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
> -- Found Threads: TRUE  
> -- catkin 0.8.10
> -- BUILD_SHARED_LIBS is on
> CMake Warning at /usr/share/catkin/cmake/test/gtest.cmake:159 (message):
>   skipping gtest 'utest' in project 'angles' because gtest was not found
> Call Stack (most recent call first):
>   /usr/share/catkin/cmake/test/gtest.cmake:89 
> (_catkin_add_executable_with_google_test)
>   /usr/share/catkin/cmake/test/gtest.cmake:37 (_catkin_add_google_test)
>   test/CMakeLists.txt:2 (catkin_add_gtest)
> 
> 
> -- skipping nosetests(utest.py) in project 'angles'
> /usr/share/catkin/cmake/interrogate_setup_dot_py.py:43: DeprecationWarning: 
> The distutils package is deprecated and slated for removal in Python 3.12. 
> Use setuptools or check PEP 632 for potential alternatives
>   import distutils.core
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning: 
> Distutils was imported before Setuptools, but importing Setuptools also 
> replaces the `distutils` module in `sys.modules`. This may lead to 
> undesirable behaviors or errors. To avoid these issues, avoid using distutils 
> directly, ensure that setuptools is installed in the traditional way (e.g. 
> not an editable install), and/or make sure that setuptools is always imported 
> before distutils.
>   warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning: 
> Setuptools is replacing distutils.
>   warnings.warn("Setuptools is replacing distutils.")
> usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
>or: setup.py --help [cmd1 cmd2 ...]
>or: setup.py --help-commands
>or: setup.py cmd --help
> 
> error: invalid command 'angles'
> CMake Error at 

Bug#1020015: marked as done (ros-resource-retriever: FTBFS: error: invalid command 'resource_retriever')

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2022 12:02:44 +
with message-id 
and subject line Bug#1020015: fixed in ros-resource-retriever 1.12.7-3
has caused the Debian Bug report #1020015,
regarding ros-resource-retriever: FTBFS: error: invalid command 
'resource_retriever'
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.)


-- 
1020015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020015
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ros-resource-retriever
Version: 1.12.7-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --buildsystem=cmake
>dh_update_autotools_config -O--buildsystem=cmake
>dh_autoreconf -O--buildsystem=cmake
>dh_auto_configure -O--buildsystem=cmake
>   cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
> -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
> -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
> -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF 
> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
> -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
> -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" 
> -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu ..
> -- The C compiler identification is GNU 12.2.0
> -- The CXX compiler identification is GNU 12.2.0
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working C compiler: /usr/bin/cc - skipped
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Check for working CXX compiler: /usr/bin/c++ - skipped
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Using CATKIN_DEVEL_PREFIX: /<>/obj-x86_64-linux-gnu/devel
> -- Using CMAKE_PREFIX_PATH: 
> -- Found PythonInterp: /usr/bin/python3 (found suitable version "3.10.7", 
> minimum required is "3") 
> -- Using PYTHON_EXECUTABLE: /usr/bin/python3
> -- Using Debian Python package layout
> -- Using empy: /usr/bin/empy
> -- Using CATKIN_ENABLE_TESTING: ON
> -- Call enable_testing()
> -- Using CATKIN_TEST_RESULTS_DIR: 
> /<>/obj-x86_64-linux-gnu/test_results
> -- GTest is available
> -- GMock is not available. Please install libgmock-dev to enable tests 
> involving GMock.
> -- nosetests not found, Python tests can not be run (try installing package 
> 'python3-nose')
> -- Found Threads: TRUE  
> -- catkin 0.8.10
> -- BUILD_SHARED_LIBS is on
> -- Found Boost: 
> /usr/lib/x86_64-linux-gnu/cmake/Boost-1.74.0/BoostConfig.cmake (found version 
> "1.74.0")  
> -- Found CURL: /usr/lib/x86_64-linux-gnu/libcurl.so (found version "7.85.0")  
> /usr/share/catkin/cmake/interrogate_setup_dot_py.py:43: DeprecationWarning: 
> The distutils package is deprecated and slated for removal in Python 3.12. 
> Use setuptools or check PEP 632 for potential alternatives
>   import distutils.core
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning: 
> Distutils was imported before Setuptools, but importing Setuptools also 
> replaces the `distutils` module in `sys.modules`. This may lead to 
> undesirable behaviors or errors. To avoid these issues, avoid using distutils 
> directly, ensure that setuptools is installed in the traditional way (e.g. 
> not an editable install), and/or make sure that setuptools is always imported 
> before distutils.
>   warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning: 
> Setuptools is replacing distutils.
>   warnings.warn("Setuptools is replacing distutils.")
> usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
>or: setup.py --help [cmd1 cmd2 ...]
>or: setup.py --help-commands
>or: setup.py cmd --help
> 
> error: invalid command 'resource_retriever'
> CMake Error at /usr/share/catkin/cmake/safe_execute_process.cmake:11 
> (message):
>   
>   
> execute_process(/<>/obj-x86_64-linux-gnu/catkin_generated/env_cached.sh
>   "/usr/bin/python3" "/usr/share/catkin/cmake/interrogate_setup_dot_py.py"
>   "resource_retriever"
>   "/<>/setup.py"
>   
> "/<>/obj-x86_64-linux-gnu/catkin_generated/setup_py_interrogation.cmake")
>   returned error code 1
> Call Stack (most recent call first):
>   /usr/share/catkin/cmake/catkin_python_setup.cmake:46 (safe_execute_process)
>   

Bug#1020006: marked as done (ros-laser-geometry: FTBFS: error: invalid command 'laser_geometry')

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2022 12:02:37 +
with message-id 
and subject line Bug#1020006: fixed in ros-laser-geometry 1.6.7-5
has caused the Debian Bug report #1020006,
regarding ros-laser-geometry: FTBFS: error: invalid command 'laser_geometry'
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.)


-- 
1020006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020006
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ros-laser-geometry
Version: 1.6.7-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --buildsystem=cmake
>dh_update_autotools_config -O--buildsystem=cmake
>dh_autoreconf -O--buildsystem=cmake
>dh_auto_configure -O--buildsystem=cmake
>   cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
> -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
> -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
> -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF 
> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
> -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
> -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" 
> -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu ..
> -- The C compiler identification is GNU 12.2.0
> -- The CXX compiler identification is GNU 12.2.0
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working C compiler: /usr/bin/cc - skipped
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Check for working CXX compiler: /usr/bin/c++ - skipped
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Using CATKIN_DEVEL_PREFIX: /<>/obj-x86_64-linux-gnu/devel
> -- Using CMAKE_PREFIX_PATH: 
> -- Found PythonInterp: /usr/bin/python3 (found suitable version "3.10.7", 
> minimum required is "3") 
> -- Using PYTHON_EXECUTABLE: /usr/bin/python3
> -- Using Debian Python package layout
> -- Using empy: /usr/bin/empy
> -- Using CATKIN_ENABLE_TESTING: ON
> -- Call enable_testing()
> -- Using CATKIN_TEST_RESULTS_DIR: 
> /<>/obj-x86_64-linux-gnu/test_results
> -- GTest is available
> -- GMock is not available. Please install libgmock-dev to enable tests 
> involving GMock.
> -- nosetests not found, Python tests can not be run (try installing package 
> 'python3-nose')
> -- Found Threads: TRUE  
> -- catkin 0.8.10
> -- BUILD_SHARED_LIBS is on
> -- Using these message generators: gencpp;genlisp;genpy
> -- Found Boost: 
> /usr/lib/x86_64-linux-gnu/cmake/Boost-1.74.0/BoostConfig.cmake (found version 
> "1.74.0") found components: system thread 
> /usr/share/catkin/cmake/interrogate_setup_dot_py.py:43: DeprecationWarning: 
> The distutils package is deprecated and slated for removal in Python 3.12. 
> Use setuptools or check PEP 632 for potential alternatives
>   import distutils.core
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning: 
> Distutils was imported before Setuptools, but importing Setuptools also 
> replaces the `distutils` module in `sys.modules`. This may lead to 
> undesirable behaviors or errors. To avoid these issues, avoid using distutils 
> directly, ensure that setuptools is installed in the traditional way (e.g. 
> not an editable install), and/or make sure that setuptools is always imported 
> before distutils.
>   warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning: 
> Setuptools is replacing distutils.
>   warnings.warn("Setuptools is replacing distutils.")
> usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
>or: setup.py --help [cmd1 cmd2 ...]
>or: setup.py --help-commands
>or: setup.py cmd --help
> 
> error: invalid command 'laser_geometry'
> CMake Error at /usr/share/catkin/cmake/safe_execute_process.cmake:11 
> (message):
>   
>   
> execute_process(/<>/obj-x86_64-linux-gnu/catkin_generated/env_cached.sh
>   "/usr/bin/python3" "/usr/share/catkin/cmake/interrogate_setup_dot_py.py"
>   "laser_geometry"
>   "/<>/setup.py"
>   
> "/<>/obj-x86_64-linux-gnu/catkin_generated/setup_py_interrogation.cmake")
>   returned error code 1
> Call Stack (most recent call first):
>   /usr/share/catkin/cmake/catkin_python_setup.cmake:46 (safe_execute_process)
>   CMakeLists.txt:22 

Bug#1020033: marked as done (python-sabyenc: FTBFS: tmp0h4oo8h4.cc:2:2: error: #error __ILP32__ not available!)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2022 11:59:42 +
with message-id 
and subject line Bug#1020033: fixed in python-sabyenc 5.4.3-2
has caused the Debian Bug report #1020033,
regarding python-sabyenc: FTBFS: tmp0h4oo8h4.cc:2:2: error: #error __ILP32__ 
not available!
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.)


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

Hi,

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


Relevant part (hopefully):
> x86_64-linux-gnu-gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv 
> -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g 
> -fwrapv -O2 -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.10 -c /tmp/tmp0h4oo8h4.cc -o 
> tmp/tmp0h4oo8h4.o
> /tmp/tmp0h4oo8h4.cc:2:2: error: #error __ILP32__ not available!
> 2 | #error __ILP32__ not available!
>   |  ^
> error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
> E: pybuild pybuild:379: build: plugin distutils failed with: exit code=1: 
> /usr/bin/python3 setup.py build 
> dh_auto_build: error: pybuild --build -i python{version} -p 3.10 returned 
> exit code 13
> make: *** [debian/rules:11: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/09/17/python-sabyenc_5.4.3-1_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: python-sabyenc
Source-Version: 5.4.3-2
Done: Jeroen Ploemen 

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

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

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

Debian distribution maintenance software
pp.
Jeroen Ploemen  (supplier of updated python-sabyenc 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, 20 Sep 2022 07:48:23 +
Source: python-sabyenc
Architecture: source
Version: 5.4.3-2
Distribution: unstable
Urgency: medium
Maintainer: Jeroen Ploemen 
Changed-By: Jeroen Ploemen 
Closes: 1020033
Changes:
 python-sabyenc (5.4.3-2) unstable; urgency=medium
 .
   * Patches: add 01 to import setuptools before distutils.
 (Closes: #1020033)
Checksums-Sha1:
 7826b4eed34bfa8637c6cb1506247cde2de5b3fb 2178 python-sabyenc_5.4.3-2.dsc
 50a0b4a49ccf62b5e4bbf3bd453199b2218cb1e0 6268 
python-sabyenc_5.4.3-2.debian.tar.xz
 53d513ce885e633d6393d9cbe29e48fd1cb12141 8176 
python-sabyenc_5.4.3-2_source.buildinfo
Checksums-Sha256:
 d3e5adbc6213a053dde3938b1cfc3038b95334ebe390e0fbea41549ebc37f48e 2178 
python-sabyenc_5.4.3-2.dsc
 e38a4ac23d142654aa9e5cf29d584cc021550fc9a0a8ccb7a69e34e4f11675d9 6268 
python-sabyenc_5.4.3-2.debian.tar.xz
 0470bfb73a0aeac2e41d75bb59c734e93163e6bfef1acada4d9036dad7e0606f 8176 
python-sabyenc_5.4.3-2_source.buildinfo
Files:
 82fbae3ebd11335da3044db537077fc0 2178 python optional 
python-sabyenc_5.4.3-2.dsc
 9a6c0b2bb43cf7b228c5365487cdc8a1 6268 python optional 
python-sabyenc_5.4.3-2.debian.tar.xz
 4cd1e47d9e466dacf9d7fb62b3c9e548 8176 python optional 
python-sabyenc_5.4.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#1020300: marked as done (popt: non-source popt.pdf file)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2022 11:59:03 +
with message-id 
and subject line Bug#1020300: fixed in popt 1.19+dfsg-1~exp1
has caused the Debian Bug report #1020300,
regarding popt: non-source popt.pdf file
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.)


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

Source: popt
Version: 1.18-3
Severity: serious

The popt.pdf file is non-source and probably not DFSG-free licensed, so please 
remove it.
When repacking, please add a repacksuffix to the version number.
--- End Message ---
--- Begin Message ---
Source: popt
Source-Version: 1.19+dfsg-1~exp1
Done: Håvard F. Aasen 

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

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

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

Debian distribution maintenance software
pp.
Håvard F. Aasen  (supplier of updated popt 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, 20 Sep 2022 00:42:04 +0200
Source: popt
Architecture: source
Version: 1.19+dfsg-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Håvard F. Aasen 
Changed-By: Håvard F. Aasen 
Closes: 941814 995268 1020300
Changes:
 popt (1.19+dfsg-1~exp1) experimental; urgency=medium
 .
   * New upstream release.
 - Fixes memory leak. Closes: #941814
   * Drop all patches, included upstream.
   * Repack source, remove popt.pdf. Closes: #1020300
   * Adopt package. Closes: #995268
   * d/copyright:
 - Add myself under Debian paragraph.
 - Upstream changed license to MIT/expat.
   * Update Standards-Version to 4.6.1
   * Remove no longer needed package conflicts.
   * wrap-and-sort -at
Checksums-Sha1:
 cbe5fac74075ff4b7c54b77d16fa98d2370cb98a 1914 popt_1.19+dfsg-1~exp1.dsc
 e90c9837494f9523f6078e90fe9ee081c002cd6e 353032 popt_1.19+dfsg.orig.tar.xz
 100013d838847bce123ff15d6c0276ae6821c0b9 10236 
popt_1.19+dfsg-1~exp1.debian.tar.xz
 b0f0d89083680795fe79e9b16e8f2459a6f33354 5537 
popt_1.19+dfsg-1~exp1_source.buildinfo
Checksums-Sha256:
 31b1254b56b93afc6aa6dfe2d0e1fd426c8b9f854f4f356d7592c04d043e74d8 1914 
popt_1.19+dfsg-1~exp1.dsc
 4cd0cd2963d0c4078f65949599d97135c15ee6c09cf3a36a9a1b2753025bb06b 353032 
popt_1.19+dfsg.orig.tar.xz
 994e897f4f858f69017d3b47f81acdc2c38465a94183fb309391988c6a132877 10236 
popt_1.19+dfsg-1~exp1.debian.tar.xz
 e520bc5645a3edfb5ab41481770e10ccf59031a5a0c3a7d9b69c3e9c0353d2b7 5537 
popt_1.19+dfsg-1~exp1_source.buildinfo
Files:
 e835e226b4cc5659938dc513efe88a4d 1914 devel optional popt_1.19+dfsg-1~exp1.dsc
 f7c74e1d71879cd73859c44a71923138 353032 devel optional 
popt_1.19+dfsg.orig.tar.xz
 6464323e30a056b092a5c00fc96355b3 10236 devel optional 
popt_1.19+dfsg-1~exp1.debian.tar.xz
 5ef2677d9c94638dffc294cf78ff9b81 5537 devel optional 
popt_1.19+dfsg-1~exp1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmMpiu8QHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFFxwDACAgfAhPbxtIuVumY78vIs6uub8u4QQHeuw
CJYXrtBC/VpRjLCtkdCGyrybskpF4XUI9JsoMvpsoDuLz5JIGqylEQs8DIKUW0wq
yqIf1++eIxi7o54pyqFEdYWW/KPS86DauFARndNBDh3Yb9ahjd6jYcZhxUerCo12
1qLWT80skr/OzcvaOc/HoQ+IwM2ev4labESFtfIY8dheNM7OK1J/HlGnCmbkHRwH
DUuP/3FImd5hacv44oKoS8t6jjaoVZRHCwWpknlJYn+vTCPUMeByMXXEW2gCJi3Z
0vxXhZEeXgVRAbwN/dU5JRZnrCjElr7Tt6PGtdRjmcO0Uln4P+qqSioWKWHeju0C
FbDNrgWywtfsBPegk+mFZDSISTv/BCU3nEy6KywHbQ0FjZY3pbEQvQNgzHrsUCue
QwtsenX58uJ53XfDW93wGV79SLeweB1IAaXOwdicHstx0a8hVdIJjS17XApmZeo0
tYiUlnkPet/xkYcUKnTRx8fPfJkOZko=
=jE8j
-END PGP SIGNATURE End Message ---

Bug#1017499: marked as done (mesa: Updates to 22.2 RCs cause artifacts on nouveau and blank screen on VirtIO)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2022 11:57:59 +
with message-id 
and subject line Bug#1017499: fixed in mesa 22.2.0~rc3-2
has caused the Debian Bug report #1017499,
regarding mesa: Updates to 22.2 RCs cause artifacts on nouveau and blank screen 
on VirtIO
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.)


-- 
1017499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017499
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mesa
Version: 22.2.0~rc1-1
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,

After updating to mesa 22.2.0~rc1-1 on my 2008 Dell Precision laptop
with a Quadro FX 1700M GPU, I began experiencing artifacts [1] as soon
as lightdm started, and they still remained after launching Xfce [2].
I also updated my Debian virtual machine in UTM on macOS, which uses
VirtIO graphics, and LightDM is just completely black there except for
a cursor.

After updating to 22.2.0~rc2-1, the nouveau laptop's artifacts were
limited to only foreground objects, such as the login box of lightdm
[3] or the menu and panel of Xfce [4]. The virtual machine stayed the
same.

- --
Ben Westover

[1] https://i.ibb.co/mcw7phd/IMG-20220816-231123.jpg
[2] https://i.ibb.co/QpRZMwV/IMG-20220816-231401.jpg
[3] https://i.ibb.co/y5F1dsJ/IMG-20220816-233627.jpg
[4] https://i.ibb.co/7z3X5sy/IMG-20220816-233611.jpg

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

Kernel: Linux 5.18.0-4-amd64 (SMP w/2 CPU threads; PREEMPT)
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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOGnacqRhdU6eNmtFwxHF9U6JtpgFAmL8ZzkACgkQwxHF9U6J
tphg4A/9Fv5e8+V6K2BAXqeoJQPI+JPRWEqe4dW7XnEkvZAWPDw9t6SG9bJYZMwK
axwxL+Iobj90WyxGtsUbAjXjFbNJJ0gPorgA/0d83KpPzLwJEDgk1yZKs/vraO64
secD1BBQ04X07NEhZoTzNKbqrUCJUmgZk7R21OfAzTBXdYmMk7CAa4WVoVSgYNcu
VP0+GsvmQhETgidDFa4QfrzT4bKEzWo/Vcp3jXWM6u+ovrVtYKvbovE9/M3kRMyJ
0PEZfMYxkq54ggIdT4dEbh7wYN1eGvfubodQ6pDyk+lxaZ00dVZdBcmGhH3RQGLz
AClLDr7ZQ+dXz6/HZgd1KXx1PEteI7Cx58yUbJkDcGXS9ddbwfXDLdJYZ9rFYWet
CMFuBILn15FxzpjObNjQANzc8xzFAUwMGjq5g0HcAByTslvDipkZtz1Gc5lRyygs
ixH8WKWh6dJv54n8KMppjLsr9miJq5Azf82x2AlD5A2Z4xN1zAkagjeijZVZGJwn
t8gy2TwK0GsJET2M/hlLRD/1qbPpB4BrUJJIqSTMuNOPUQyRvu0MlcQv8rVYmXCi
E9I6o8nG/4k/MeSh/YFXdk49iet1w1fbwQ2GaIvA8FdS/kd7AEQD5p1rW4hcIbBQ
ogaKc+2IP2ZHjsr1i5oH7eaE3GgYLRR8Ym5oKKh8Z4fh5oiMiCM=
=DQZd
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: mesa
Source-Version: 22.2.0~rc3-2
Done: Timo Aaltonen 

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated mesa 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, 20 Sep 2022 13:25:59 +0300
Source: mesa
Built-For-Profiles: noudeb
Architecture: source
Version: 22.2.0~rc3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Timo Aaltonen 
Closes: 1017499
Changes:
 mesa (22.2.0~rc3-2) unstable; urgency=medium
 .
   * nv50-ir-fix-OP_UNION-resolving-when-used-for-vector.diff: Fix a
 regression on nouveau. (Closes: #1017499)
Checksums-Sha1:
 c28e0e8413079da287c415b05b385a78ee804008 5414 mesa_22.2.0~rc3-2.dsc
 889455f8227c23e29f13331949b80a265cc76cb5 118096 mesa_22.2.0~rc3-2.diff.gz
 de82fef6232a6849c9a29ae7507b57fe47b054bf 10092 
mesa_22.2.0~rc3-2_source.buildinfo
Checksums-Sha256:
 c961c07d0b37f04282d5bdd6bbc455b3053ff5378285d0cc067beeba39213bdf 5414 
mesa_22.2.0~rc3-2.dsc
 1f9db7212e87fe7ebaf0b7109af630c372f1a54b773116a1a46fb30939866585 118096 
mesa_22.2.0~rc3-2.diff.gz
 6c43f19271a150fa4c090675f54ad9b73e4e7f3c364198448acf2c958e9bbd2b 10092 
mesa_22.2.0~rc3-2_source.buildinfo
Files:
 3324d1654d5f29b41e6ad2f53179e43f 5414 graphics optional mesa_22.2.0~rc3-2.dsc
 ebfdbc1e1c7ced2c518912ece794e7c8 118096 graphics optional 

Bug#1013007: marked as done (oomd: ftbfs with GCC-12)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2022 11:58:54 +
with message-id 
and subject line Bug#1013007: fixed in oomd 0.5.0-1.2
has caused the Debian Bug report #1013007,
regarding oomd: ftbfs with GCC-12
to be marked as done.

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

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


-- 
1013007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013007
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:oomd
Version: 0.5.0-1.1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12

[This bug is targeted to the upcoming bookworm 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-12/g++-12, but succeeds to build with gcc-11/g++-11. The
severity of this report will be raised before the bookworm release.

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/oomd_0.5.0-1.1_unstable_gcc12.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
   dh_clean
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure
cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
--localstatedir=/var --libdir=lib/x86_64-linux-gnu
The Meson build system
Version: 0.62.2
Source dir: /<>
Build dir: /<>/obj-x86_64-linux-gnu
Build type: native build
Project name: oomd
Project version: v0.5.0
C++ compiler for the host machine: c++ (gcc 12.1.0 "c++ (Debian 12.1.0-2) 
12.1.0")
C++ linker for the host machine: c++ ld.bfd 2.38
Host machine cpu family: x86_64
Host machine cpu: x86_64
Found pkg-config: /usr/bin/pkg-config (0.29.2)
Run-time dependency jsoncpp found: YES 1.9.5
Run-time dependency threads found: YES
Run-time dependency libsystemd found: YES 251
Configuring oomd.json using configuration
Run-time dependency GTest found: YES 1.11.0
Run-time dependency GMock found: YES 1.11.0
Build targets in project: 16
NOTICE: Future-deprecated features used:
 * 0.56.0: {'meson.source_root'}

oomd v0.5.0

  User defined options
buildtype: plain
libdir   : lib/x86_64-linux-gnu
localstatedir: /var
prefix   : /usr
sysconfdir   : /etc
wrap_mode: nodownload

Found ninja-1.11.0 at /usr/bin/ninja
   dh_auto_build
cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j8 -v
[1/79] /usr/bin/meson --internal vcstagger ../src/oomd/include/Version.h.in 
Version.h v0.5.0 /<> @VCS_TAG@ '(.*)' 
/<>/vcs_tagger.sh /<> v0.5.0
[2/79] c++ -Iliboomd.a.p -I. -I.. -I../src -I/usr/include/jsoncpp 
-fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch 
-Wnon-virtual-dtor -std=c++17 -O0 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -pthread -DMESON_BUILD -MD -MQ 
liboomd.a.p/src_oomd_PluginConstructionContext.cpp.o -MF 
liboomd.a.p/src_oomd_PluginConstructionContext.cpp.o.d -o 
liboomd.a.p/src_oomd_PluginConstructionContext.cpp.o -c 
../src/oomd/PluginConstructionContext.cpp
[3/79] c++ -Iliboomd.a.p -I. -I.. -I../src -I/usr/include/jsoncpp 
-fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch 
-Wnon-virtual-dtor -std=c++17 -O0 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -pthread -DMESON_BUILD -MD -MQ 
liboomd.a.p/src_oomd_Log.cpp.o -MF liboomd.a.p/src_oomd_Log.cpp.o.d -o 
liboomd.a.p/src_oomd_Log.cpp.o -c ../src/oomd/Log.cpp
FAILED: liboomd.a.p/src_oomd_Log.cpp.o 
c++ -Iliboomd.a.p -I. -I.. -I../src -I/usr/include/jsoncpp 
-fdiagnostics-color=always 

Bug#1020290: marked as done (init-system-helpers depends on usrmerge | usr-is-merged)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2022 12:48:03 +0100
with message-id 
and subject line Re: Bug#1020290 closed by Luca Boccassi  
(Re: init-system-helpers depends on usrmerge | usr-is-merged)
has caused the Debian Bug report #1020290,
regarding init-system-helpers depends on usrmerge | usr-is-merged
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.)


-- 
1020290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020290
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: init-system-helpers
Version: 1.65.2

dist-upgrade was broken on four systems tonight due to:

Depends: usrmerge | usr-is-merged

This effectively makes these packages Essential by stealth.  Debian's usrmerge
FAQ says:

* Is it mandatory to install this package?
No.


All four systems (3 running systemd, one running sysvinit - because systemd
is incapable of booting this machine) gave the following error message and
aborted the upgrade:

Selecting previously unselected package usr-is-merged.
Preparing to unpack .../01-usr-is-merged_30+nmu1_all.deb ...



**
*
* The usr-is-merged package cannot be installed because this system does
* not have a merged /usr.
*
* Please install the usrmerge package to convert this system to merged-/usr.
*
* For more information please read https://wiki.debian.org/UsrMerge.
*

**


dpkg: error processing archive 
/tmp/user/0/apt-dpkg-install-zRN5ON/01-usr-is-merged_30+nmu1_all.deb (--unpack):
 new usr-is-merged package pre-installation script subprocess returned 
error exit status 1
.
.
.
Errors were encountered while processing:
 /tmp/user/0/apt-dpkg-install-zRN5ON/01-usr-is-merged_30+nmu1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


This could only be fixed by reverting back to 1.64 and purging usr-is-merged,
followed by 'apt-mark hold init-system-helpers' of course.


This is an essential package.  Why is it forcing this usr merge idiocy on me,
even on systems that don't run systemd? what actual benefit does it provide?

And WTF does forcing usrmerge have to do with init-system-helpers' purpose?
How does forcing usrmerge qualify as a helper tool for switching between "all"
init systems?


Description-en: helper tools for all init systems
 This package contains helper tools that are necessary for switching
 between the various init systems that Debian contains (e. g. sysvinit
 or systemd). An example is deb-systemd-helper, a script that enables
 systemd unit files without depending on a running systemd.
 .
 It also includes the "service", "invoke-rc.d", and "update-rc.d"
 scripts which provide an abstraction for enabling, disabling,
 starting, and stopping services for all supported Debian init systems
 as specified by the policy.
 .
 While this package is maintained by pkg-systemd-maintainers, it is
 NOT specific to systemd at all. Maintainers of other init systems are
 welcome to include their helpers in this package.


craig

ps: I'm annoyed enough that this tried to install usr-is-merged and failed.
I would have been furious if it had successfully installed usrmerge and
irreversibly fucked with my filesystems without warning and especially without
my CONSENT.
--- End Message ---
--- Begin Message ---
Given you have made usrmerge uninstallable in your system as you
admitted (probably running one of dpkg's unsupported scripts that
installs a local blocking package, I'd imagine) then it is entirely on
you to fix that, it cannot be done remotely. Please stop spewing abuse
and playing games with the BTS, it is not going to achieve anything.

-- 
Kind regards,
Luca Boccassi


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

Bug#1020021: marked as done (dt-schema: FTBFS: ModuleNotFoundError: No module named 'setuptools')

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2022 11:35:53 +
with message-id 
and subject line Bug#1020021: fixed in dt-schema 2022.08.2-2
has caused the Debian Bug report #1020021,
regarding dt-schema: FTBFS: ModuleNotFoundError: No module named 'setuptools'
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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py clean 
> Traceback (most recent call last):
>   File "/<>/setup.py", line 5, in 
> import setuptools
> ModuleNotFoundError: No module named 'setuptools'
> E: pybuild pybuild:379: clean: plugin distutils failed with: exit code=1: 
> python3.10 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.10 returned 
> exit code 13
> make: *** [debian/rules:5: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/09/17/dt-schema_2022.08.2-1_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: dt-schema
Source-Version: 2022.08.2-2
Done: Bastian Germann 

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

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

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated dt-schema 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, 20 Sep 2022 12:57:44 +0200
Source: dt-schema
Architecture: source
Version: 2022.08.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Bastian Germann 
Closes: 1020021
Changes:
 dt-schema (2022.08.2-2) unstable; urgency=medium
 .
   * Team upload
   * Add B-D setuptools (Closes: #1020021)
Checksums-Sha1:
 2c72fcf644400723f586f36c09eda59163cbd5f8 2034 dt-schema_2022.08.2-2.dsc
 7ccfb27e0c8adebc2d3bbbd774eaaf254704dba3 3656 
dt-schema_2022.08.2-2.debian.tar.xz
 4fb2f006451ec85f619ec6f0efaa926659064276 6261 
dt-schema_2022.08.2-2_source.buildinfo
Checksums-Sha256:
 70099cda1fd6fe50839a104ee4fe5bcc8deb8d6ca2561455e2fdad53e4fad710 2034 
dt-schema_2022.08.2-2.dsc
 57c8323cf03ce11c3de2ea5a11a19645dda54cd6d9df112bb14e105d409a0ca0 3656 
dt-schema_2022.08.2-2.debian.tar.xz
 22ce9b12d0f821a3baa39c7755a7e0214fdb50294c66f0725aab0cceba8a37c1 6261 
dt-schema_2022.08.2-2_source.buildinfo
Files:
 b73f6ea381e115e34ad56a706ec9e92b 2034 devel optional dt-schema_2022.08.2-2.dsc
 bf98d38386eece128b1695f9fa9076ac 3656 devel optional 
dt-schema_2022.08.2-2.debian.tar.xz
 91f86febc266aa619feb86bb8a93fa24 6261 devel optional 
dt-schema_2022.08.2-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmMpnVsQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFEwjDADQZVujeywuO6Iai0vV/f18Byamc01skP4/
JC+LC17G7fCJanrE1kdxRUPFoTydvyEFXoq8INPmcV1/D/ghBxrN5Iq/r7AoAd+0
/lpKplMxA01VsHnkQAVLbn1VsmO7x48O0JmesK8CRWFv1DzplTAmztoytM5Yltd6
E4QIJuahB6QcPjfXEcoHevBjQyZi3oxm1HzIzyeWnKgOGwUKR1U93D3mQ/1Q7JIV

Bug#1019976: marked as done (asn1crypto: pypy removal: please drop pypy-asn1crypto and stop Build Depending on pypy related packages)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2022 11:34:36 +
with message-id 
and subject line Bug#1019976: fixed in asn1crypto 1.5.1-2
has caused the Debian Bug report #1019976,
regarding asn1crypto: pypy removal: please drop pypy-asn1crypto and stop Build 
Depending on pypy related packages
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.)


-- 
1019976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019976
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: asn1crypto
Version: 1.5.1-1
Severity: serious
Control: block 1011926 by -1

Dear maintainer(s),

We're trying to remove the last remnants of python2 from bookworm. One
of the involved source packages is pypy. Your package has a
Build-Depends on pypy and some related packages. I assume because this
source buils pypy-asn1crypto. I suggest to drop that latter package in order to 
drop the Build-Depends related to pypy.

Paul
--- End Message ---
--- Begin Message ---
Source: asn1crypto
Source-Version: 1.5.1-2
Done: Jochen Sprickerhof 

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

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

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated asn1crypto 
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, 20 Sep 2022 13:10:03 +0200
Source: asn1crypto
Architecture: source
Version: 1.5.1-2
Distribution: unstable
Urgency: medium
Maintainer: Tristan Seligmann 
Changed-By: Jochen Sprickerhof 
Closes: 1019976
Changes:
 asn1crypto (1.5.1-2) unstable; urgency=medium
 .
   * Team upload.
   * Drop pypy package (Closes: #1019976)
Checksums-Sha1:
 a003e8f08fbbec12b47252e4b9749eec34e90307 2016 asn1crypto_1.5.1-2.dsc
 fee5ca867ed312e2053c86297b3fe0ec10fa88d0 2812 asn1crypto_1.5.1-2.debian.tar.xz
 beffd90e19352e8886e284c5f9ccdce884d6436b 6914 
asn1crypto_1.5.1-2_source.buildinfo
Checksums-Sha256:
 235635d8016e852960588b4641df69063befa10b53df25d6db7fbcb6e2ab0b3f 2016 
asn1crypto_1.5.1-2.dsc
 3ae16f8c5852e2248c00d25686b3b018f48c312a0def7f792b291b425e3eea42 2812 
asn1crypto_1.5.1-2.debian.tar.xz
 a6a5353c70bdd62d93d45e8e7f93b6a2a787ab1b2559e68a5fc85b3fd815b0ff 6914 
asn1crypto_1.5.1-2_source.buildinfo
Files:
 914b5429ae528c2838e4cabf66e78a14 2016 python optional asn1crypto_1.5.1-2.dsc
 4347aec006134c6e5a6b3c57e484da9a 2812 python optional 
asn1crypto_1.5.1-2.debian.tar.xz
 16b58fd605e60019f33f8fb5f6fc4c6c 6914 python optional 
asn1crypto_1.5.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAmMpn5cACgkQW//cwljm
lDNRSQ//WFBSPvtnwW6gpntHf+YZUp44QVUOeDTL8eq4Nk/vrmXSa523spuv0eyw
3iy+OaQ+e1Y5swR0UpIlrZ3sWk+2TQ5BmHDuKpxkm/OYb6zIBr7CxVHYbMxg6Laa
vL2W+Wnr2i2UaX1QOpS4XouQIU0MMk+Y68j+HnprolbbV1iOv93y/35I1W002tGU
rbPwTjgmfChcFl2QGfq0xIv6PGYJnrUyRugRXgdrtrYexPrSSbkT+upiGzNdEkAj
4pSNKMQ5cWrk8S4i7NTom1NsDlAc9Y4s+mvq1R/vyl/ekyozT41RkW+OpGEUD+rj
IUnoinVoT0TpF42LM/SomCbNhCpZ9ZmVw7uNv6fMQAUGITMubx7JYp6t+GA0L4UM
JEXMWmi4MsJixbXvXZ3/8Lm/GWeC7WH6TT5cj8NoorZqSONZgIeugCKl3e3YNlBa
7vpxfsanMBtkZRlyHLHlLO4kKjjsbWjtrsJHiiHfVvWRclYbfT/QyFQyyv+ZNACv
PYNlh5T+yLdNLu0aP3wj7RUUrEX2hOv54gbfGZSiiDd/lTEP1YfXD4WyHMn+ekgE
F4EgdOZehRFhGvwe0TR7u/rY/U9T2ip86WFkRg/v3nYJDvBsGxkAatQcXJDNU8hh
+oJWbn2YNodDWtNWwwhl1PjKg0wJLwkUzql7K47v2QJXbsMYqIw=
=Jo0V
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#1017979: mozjs91: FTBFS on armel with gcc 12: multiple definition of `__sync_fetch_and_add_4' etc.

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1017979 [src:mozjs91] mozjs91: FTBFS on armel with gcc 12: multiple 
definition of `__sync_fetch_and_add_4' etc.
Added tag(s) patch.

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

Bug#1017979: mozjs91: FTBFS on armel with gcc 12: multiple definition of `__sync_fetch_and_add_4' etc.

[Simon McVittie]

Control: tags -1 + patch

On Tue, 23 Aug 2022 at 21:39:50 +0100, Simon McVittie wrote:
> On Tue, 23 Aug 2022 at 13:23:30 +0100, Simon McVittie wrote:
> > The final link fails with multiple definitions of the various atomic
> > builtins:
> > 
> > > (.text+0x0): multiple definition of `__sync_fetch_and_add_4'; 
> > > /home/smcv/mozjs91-armel/debian/build/armv5te-unknown-linux-gnueabi/release/libjsrust.a(compiler_builtins-23c2fc8f8ef06d87.compiler_builtins.bdb7b41d-cgu.153.rcgu.o):/usr/src/rustc-1.59.0/vendor/compiler_builtins/src/arm_linux.rs:94:
> > >  first defined here
> 
> Reported upstream as https://bugzilla.mozilla.org/show_bug.cgi?id=1786623

Workaround: link with -Wl,--allow-multiple-definition (thanks to Adrian
Bunk).

I think we're more likely to replace mozjs91 in gjs' dependencies with
mozjs102 and remove mozjs91 than we are to fix mozjs91, but I'm mentioning
this here in case it becomes necessary to use mozjs91 for some reason.
Linking with -Wl,--allow-multiple-definition seems like a less bad
workaround than using a non-default gcc.

smcv

Processed: Re: Bug#1020290 closed by Luca Boccassi (Re: init-system-helpers depends on usrmerge | usr-is-merged)

[Debian Bug Tracking System]

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

> reopen 1020290
Bug #1020290 {Done: Luca Boccassi } [init-system-helpers] 
init-system-helpers depends on usrmerge | usr-is-merged
Bug reopened
Ignoring request to alter fixed versions of bug #1020290 to the same values 
previously set
> severity 1020290 critical
Bug #1020290 [init-system-helpers] init-system-helpers depends on usrmerge | 
usr-is-merged
Severity set to 'critical' from 'normal'
> stop
Stopping processing here.

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

Processed: Bug#1019976 marked as pending in asn1crypto

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1019976 [src:asn1crypto] asn1crypto: pypy removal: please drop 
pypy-asn1crypto and stop Build Depending on pypy related packages
Added tag(s) pending.

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

Bug#1019976: marked as pending in asn1crypto

[Jochen Sprickerhof]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/asn1crypto/-/commit/61655895550ecc7c7e7e126ed2fb0a8a44d70936


Drop pypy package

Closes: #1019976


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1019976

Processed: Re: Bug#1019965: pydevd: FTBFS in sid (failed tests)

[Debian Bug Tracking System]

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

> severity 1019965 normal
Bug #1019965 [src:pydevd] pydevd: FTBFS in sid (failed tests)
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#1019965: pydevd: FTBFS in sid (failed tests)

[Julian Gilbey]

severity 1019965 normal
thanks

On Mon, Sep 19, 2022 at 04:01:31PM +0100, Julian Gilbey wrote:
> On Sat, Sep 17, 2022 at 02:41:29PM +0200, Gianfranco Costamagna wrote:
> > Source: pydevd
> > Version: 2.8.0+git20220826.8ee4065+ds-1
> > Severity: serious
> > 
> > Hello, please have a look at the build log, some tests are now failing.
> > 
> > Can also be seed in Debian CI
> > 
> > https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/pydevd.html
> > 
> > Thanks for having a look.
> 
> Hi Gianfranco,
> 
> That's weird, as it built OK just two weeks ago.  Upstream's tests
> succeed on this test, which is a little weird, so it might be a
> version thing.  I'll report it upstream.
> 
> Best wishes,
> 
>Julian

OK, it's transient: I reran it on both my machine and on ci.debian.net
and it passed without difficulty.  So I'm going to downgrade this bug
report and just keep an eye on it.  If it recurs, I'll report it and
separate out this test (or perhaps just skip it).

Best wishes,

   Julian

Bug#1010289: audit: FTBFS: error: cast specifies array type

[Graham Inggs]

fwiw, Ubuntu went with a different solution, see diff at:

https://launchpad.net/ubuntu/+source/audit/1:3.0.7-1ubuntu1

Processed: filezilla - fails to build from source (but built successfully in the past) - Forwarded upstream

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #1020327 [src:filezilla] filezilla: FTBFS on i386
Added tag(s) confirmed.
> forwarded -1 https://trac.filezilla-project.org/ticket/12777
Bug #1020327 [src:filezilla] filezilla: FTBFS on i386
Set Bug forwarded-to-address to 
'https://trac.filezilla-project.org/ticket/12777'.

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

Bug#1020327: filezilla - fails to build from source (but built successfully in the past) - Forwarded upstream

[Philip Wyett]

Control: tags -1 + confirmed
Control: forwarded -1 https://trac.filezilla-project.org/ticket/12777

Regards

Phil

-- 
*** Playing the game for the games own sake. ***


Associations:

* Debian Maintainer (DM)
* Fedora/EPEL Maintainer.
* Contributor member of the AlmaLinux foundation.

WWW: https://kathenas.org

Buy Me a Coffee: https://www.buymeacoffee.com/kathenasorg

Twitter: @kathenasorg

Instagram: @kathenasorg

IRC: kathenas

GPG: 724AA9B52F024C8B


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

Processed: Bug#1020148 marked as pending in georegression

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1020148 {Done: Andrius Merkys } [src:georegression] 
georegression: FTBFS: make[1]: *** [debian/rules:7: override_dh_auto_build] 
Error 25
Added tag(s) pending.

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

Bug#1020148: marked as pending in georegression

[Andrius Merkys]

Control: tag -1 pending

Hello,

Bug #1020148 in georegression 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/java-team/georegression/-/commit/10c8f41bde224d1059cd94983f7ac29f48450d71


Switch to javahelper (Closes: #1020148).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1020148

Bug#1020148: marked as done (georegression: FTBFS: make[1]: *** [debian/rules:7: override_dh_auto_build] Error 25)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2022 07:34:17 +
with message-id 
and subject line Bug#1020148: fixed in georegression 0.22+ds-1
has caused the Debian Bug report #1020148,
regarding georegression: FTBFS: make[1]: *** [debian/rules:7: 
override_dh_auto_build] 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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build -- autogenerate
>   mkdir -p .gradle/init.d
>   cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/
>   gradle --info --console plain --offline --stacktrace --no-daemon 
> --refresh-dependencies --gradle-user-home .gradle -Duser.home=. 
> -Duser.name=debian -Ddebian.package=georegression -Dfile.encoding=UTF-8 
> --parallel --max-workers=8 autogenerate
> Initialized native services in: /<>/.gradle/native
> To honour the JVM settings for this build a new JVM will be forked. Please 
> consider using the daemon: 
> https://docs.gradle.org/4.4.1/userguide/gradle_daemon.html.
> Starting process 'Gradle build daemon'. Working directory: 
> /<>/.gradle/daemon/4.4.1 Command: 
> /usr/lib/jvm/java-11-openjdk-amd64/bin/java 
> -Xbootclasspath/a:/usr/share/java/gradle-helper-hook.jar:/usr/share/java/maven-repo-helper.jar
>  --add-opens java.base/java.lang=ALL-UNNAMED -Dfile.encoding=UTF-8 
> -Duser.country -Duser.language=en -Duser.variant -cp 
> /usr/share/gradle/lib/gradle-launcher-4.4.1.jar 
> org.gradle.launcher.daemon.bootstrap.GradleDaemon 4.4.1
> Successfully started process 'Gradle build daemon'
> An attempt to start the daemon took 1.0 secs.
> The client will now receive all logging from the daemon (pid: 3235137). The 
> daemon log file: /<>/.gradle/daemon/4.4.1/daemon-3235137.out.log
> Daemon will be stopped at the end of the build stopping after processing
> Closing daemon's stdin at end of input.
> The daemon will no longer process any standard input.
> Using 8 worker leases.
> Creating new cache for fileHashes, path 
> /<>/.gradle/caches/4.4.1/fileHashes/fileHashes.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@464919bf
> Creating new cache for resourceHashesCache, path 
> /<>/.gradle/caches/4.4.1/fileHashes/resourceHashesCache.bin, 
> access org.gradle.cache.internal.DefaultCacheAccess@464919bf
> Creating new cache for fileHashes, path 
> /<>/.gradle/4.4.1/fileHashes/fileHashes.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@34064827
> Starting Build
> Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
> using SubsetScriptTransformer.
> Creating new cache for metadata-1.1/results, path 
> /<>/.gradle/caches/transforms-1/metadata-1.1/results.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@2302cca9
> Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
> using BuildScriptTransformer.
> Compiling settings file '/<>/settings.gradle' using 
> SubsetScriptTransformer.
> Compiling settings file '/<>/settings.gradle' using 
> BuildScriptTransformer.
> Settings evaluated using settings file '/<>/settings.gradle'.
>   Settings file found (/<>/settings.gradle), but 
> rootProject.name isn't defined
>   Root project name not defined in settings.gradle, defaulting to 
> 'georegression' instead of the name of the root directory 
> 'georegression-0.20+ds'
> Projects loaded. Root project using build file 
> '/<>/build.gradle'.
> Included projects: [root project 'georegression', project ':autocode', 
> project ':examples', project ':experimental', project ':georegression']
>   Keep-alive timer started
>   Adding Debian repository to project 'georegression'
>   Adding Debian repository to project 'autocode'
>   Adding Debian repository to project 'examples'
>   Adding Debian repository to project 'experimental'
>   Adding Debian repository to project 'georegression'
> Parallel execution is an incubating feature.
> Evaluating root project 'georegression' using build file 
> '/<>/build.gradle'.
> Compiling build file '/<>/build.gradle' using 
> SubsetScriptTransformer.
> Compiling build file '/<>/build.gradle' using 
> BuildScriptTransformer.
> Evaluating project ':autocode' using build file 
> '/<>/autocode/build.gradle'.
> 

Processed: Bug#1020033 marked as pending in python-sabyenc

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1020033 [src:python-sabyenc] python-sabyenc: FTBFS: tmp0h4oo8h4.cc:2:2: 
error: #error __ILP32__ not available!
Added tag(s) pending.

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

Bug#1020033: marked as pending in python-sabyenc

[jcfp]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/python-sabyenc/-/commit/392b5f58288121e630f8044e6cd49d740a43c08c


Patches: add 01 to import setuptools before distutils. (Closes: #1020033)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1020033