date:20220716

Bug#1015098: nng: FTBFS: Errors while running CTest

2022-07-16 Thread GCS

Control: tags -1 +moreinfo +unreproducible
Control: severity -1 important

Hi Lucas,

On Sat, Jul 16, 2022 at 4:03 PM Lucas Nussbaum  wrote:
> Source: nng
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
 Unfortunately I can't reproduce it. Tried in several ways. Do you
have time to repeat your build process and see if it builds this time?

Thanks,
Laszlo/GCS

Processed: Re: Bug#1015098: nng: FTBFS: Errors while running CTest

2022-07-16 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 +moreinfo +unreproducible
Bug #1015098 [src:nng] nng: FTBFS: Errors while running CTest
Added tag(s) moreinfo.
Bug #1015098 [src:nng] nng: FTBFS: Errors while running CTest
Added tag(s) unreproducible.
> severity -1 important
Bug #1015098 [src:nng] nng: FTBFS: Errors while running CTest
Severity set to 'important' from 'serious'

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

Bug#1015174: lvm2-udeb: uninstallable, depends on non-udeb libsystemd0

2022-07-16 Thread Cyril Brulebois

Package: lvm2-udeb
Version: 2.03.15-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: debian-b...@lists.debian.org

[ Please keep debian-boot@ cc'd. ]

Hi,

lvm2-udeb is no longer installable, which causes some d-i images to fail
to build:

The following packages have unmet dependencies:
 lvm2-udeb : Depends: libsystemd0 (>= 251.2) but it is not installable

This also causes some issues at runtime (even though it seems a little
strange to get that far, despite the dependency issue):
  https://lists.debian.org/debian-boot/2022/07/msg00015.html

A naive check (grepping in debian/*-udeb after an lvm2 build in unstable)
suggests that only /sbin/lvm in lvm2-udeb pulls such a NEEDED dependency
on libsystemd.so.0, for those symbols:

U sd_id128_get_machine_app_specific@LIBSYSTEMD_233
U sd_journal_printv_with_location@LIBSYSTEMD_209
U sd_journal_send_with_location@LIBSYSTEMD_209

I suppose the journal bits could be patched out for the udeb build (right
now, configure ends up defining SYSTEMD_JOURNAL_SUPPORT to 1 there), but
I'm not sure what consequences disabling APP_MACHINEID_SUPPORT in the udeb
could have for arrays built at installation time (the function call itself
is already guarded within an #ifdef/#endif block, so it seems somewhat
optional already).

Feel free to let us know, and whether you'd like us to try and come up
with a tentative patch.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant

Bug#1015109: marked as done (rust-sequoia-sq: FTBFS: build-dependency not installable: librust-sequoia-net-0.24-dev)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sun, 17 Jul 2022 03:06:15 +
with message-id 
and subject line Bug#1015109: fixed in rust-sequoia-sq 0.26.0-3
has caused the Debian Bug report #1015109,
regarding rust-sequoia-sq: FTBFS: build-dependency not installable: 
librust-sequoia-net-0.24-dev
to be marked as done.

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

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


-- 
1015109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015109
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-sequoia-sq
Version: 0.26.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220716 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, 
> libstd-rust-dev, librust-anyhow-1+default-dev (>= 1.0.18-~~), 
> librust-buffered-reader-1+compression-bzip2-dev, 
> librust-buffered-reader-1+compression-deflate-dev, 
> librust-chrono-0.4+default-dev (>= 0.4.10-~~), librust-clap-2+default-dev (>= 
> 2.33-~~), librust-clap-2+wrap-help-dev (>= 2.33-~~), 
> librust-itertools-0.10+default-dev, librust-rpassword-5+default-dev, 
> librust-sequoia-autocrypt-0.24-dev, librust-sequoia-net-0.24-dev, 
> librust-sequoia-openpgp-1+compression-bzip2-dev (>= 1.1-~~), 
> librust-sequoia-openpgp-1+compression-deflate-dev (>= 1.1-~~), 
> librust-sequoia-openpgp-1+crypto-nettle-dev (>= 1.1-~~), 
> librust-sequoia-openpgp-1-dev, librust-tempfile-3+default-dev (>= 3.1-~~), 
> librust-term-size-0.3+default-dev, librust-tokio-1+default-dev (>= 
> 1.13.1-~~), bash-completion, build-essential, fakeroot
> Filtered Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, 
> libstd-rust-dev, librust-anyhow-1+default-dev (>= 1.0.18-~~), 
> librust-buffered-reader-1+compression-bzip2-dev, 
> librust-buffered-reader-1+compression-deflate-dev, 
> librust-chrono-0.4+default-dev (>= 0.4.10-~~), librust-clap-2+default-dev (>= 
> 2.33-~~), librust-clap-2+wrap-help-dev (>= 2.33-~~), 
> librust-itertools-0.10+default-dev, librust-rpassword-5+default-dev, 
> librust-sequoia-autocrypt-0.24-dev, librust-sequoia-net-0.24-dev, 
> librust-sequoia-openpgp-1+compression-bzip2-dev (>= 1.1-~~), 
> librust-sequoia-openpgp-1+compression-deflate-dev (>= 1.1-~~), 
> librust-sequoia-openpgp-1+crypto-nettle-dev (>= 1.1-~~), 
> librust-sequoia-openpgp-1-dev, librust-tempfile-3+default-dev (>= 3.1-~~), 
> librust-term-size-0.3+default-dev, librust-tokio-1+default-dev (>= 
> 1.13.1-~~), bash-completion, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [611 B]
> Get:5 copy:/<>/apt_archive ./ Packages [695 B]
> Fetched 2269 B in 0s (118 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: librust-sequoia-net-0.24-dev but 
> it is not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2022/07/16/rust-sequoia-sq_0.26.0-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://b

Processed: libzhuyin13: Unaligned access makes fcitx5-zhuyin FTBFS when building armhf on 64 bit hardware

2022-07-16 Thread Debian Bug Tracking System

Processing control commands:

> affects -1 src:fcitx5-zhuyin
Bug #1015171 [libzhuyin13] libzhuyin13: Unaligned access makes fcitx5-zhuyin 
FTBFS when building armhf on 64 bit hardware
Added indication that 1015171 affects src:fcitx5-zhuyin

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

Bug#1015171: libzhuyin13: Unaligned access makes fcitx5-zhuyin FTBFS when building armhf on 64 bit hardware

2022-07-16 Thread Adrian Bunk

Package: libzhuyin13
Version: 2.6.2-1
Severity: serious
Tags: ftbfs patch
Forwarded: https://github.com/libpinyin/libpinyin/pull/152
Control: affects -1 src:fcitx5-zhuyin

https://buildd.debian.org/status/fetch.php?pkg=fcitx5-zhuyin=armhf=5.0.8-1=1657997016=0

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

Total Test time (real) =   0.02 sec

The following tests FAILED:
  1 - testzhuyinbuffer (Bus error)
Errors while running CTest
make[1]: *** [Makefile:74: test] Error 8


The fix is in the linked pull request above.

Bug#1002109: marked as done (ruby-slim: FTBFS: ERROR: Test "ruby3.0" failed: /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/testtask.rb:130:in `block (3 levels) in define': Command failed with sta

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 23:19:09 +
with message-id 
and subject line Bug#1002109: fixed in ruby-slim 4.1.0-1
has caused the Debian Bug report #1002109,
regarding ruby-slim: FTBFS: ERROR: Test "ruby3.0" failed: 
/usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/testtask.rb:130:in `block (3 
levels) in define': Command failed with status (1) (RuntimeError)
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.)


-- 
1002109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002109
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-slim
Version: 4.0.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/testtask.rb:130:in `block 
> (3 levels) in define': Command failed with status (1) (RuntimeError)
>   from 
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/file_utils.rb:57:in `sh'
>   from 
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/file_utils.rb:104:in `ruby'
>   from 
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/testtask.rb:117:in `block 
> (2 levels) in define'
>   from 
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/file_utils_ext.rb:58:in 
> `verbose'
>   from 
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/testtask.rb:111:in `block 
> in define'
>   from /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:281:in 
> `block in execute'
>   from /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:281:in 
> `each'
>   from /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:281:in 
> `execute'
>   from /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:219:in 
> `block in invoke_with_call_chain'
>   from /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:199:in 
> `synchronize'
>   from /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:199:in 
> `invoke_with_call_chain'
>   from /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:243:in 
> `block in invoke_prerequisites'
>   from /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:241:in 
> `each'
>   from /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:241:in 
> `invoke_prerequisites'
>   from /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:218:in 
> `block in invoke_with_call_chain'
>   from /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:199:in 
> `synchronize'
>   from /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:199:in 
> `invoke_with_call_chain'
>   from /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:243:in 
> `block in invoke_prerequisites'
>   from /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:241:in 
> `each'
>   from /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:241:in 
> `invoke_prerequisites'
>   from /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:218:in 
> `block in invoke_with_call_chain'
>   from /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:199:in 
> `synchronize'
>   from /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:199:in 
> `invoke_with_call_chain'
>   from /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:188:in 
> `invoke'
>   from debian/ruby-tests.rb:5:in `'
> ERROR: Test "ruby3.0" failed: 


The full build log is available from:
http://qa-logs.debian.net/2021/12/20/ruby-slim_4.0.1-3_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: ruby-slim
Source-Version: 4.1.0-1
Done: Cédric Boutillier 

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

Bug#1015107: marked as done (gap-hap: FTBFS: make: *** [debian/rules:42: clean] Error 1)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 22:34:13 +
with message-id 
and subject line Bug#1015107: fixed in gap-hap 1.44-2
has caused the Debian Bug report #1015107,
regarding gap-hap: FTBFS: make: *** [debian/rules:42: clean] Error 1
to be marked as done.

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

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


-- 
1015107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015107
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gap-hap
Version: 1.44-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220716 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 '/<>/doc'
> rm -f {.,../tutorial}/*.{html,txt,css,js}
> rm -f {.,../tutorial}/make_manuals.out {.,../tutorial}/mathjax
> rm -f 
> {.,../tutorial}/*Hap*.{aux,bbl,blg,brf,idx,ilg,ind,log,out,pnr,tex,toc,toc.gz}
> rm -f {.,../tutorial}/manual{,-bw}.{lab,six,six.gz,pdf}
> rm -f manualbib.xml.bib
> make[1]: Leaving directory '/<>/doc'
> find . -name '*.swp' -delete
> rm -rf debian/gaproot
> rm -rf /tmp/gap-hap*
> rm: cannot remove '/tmp/gap-hap20220716-4986-1cr3x4': Operation not permitted
> rm: cannot remove '/tmp/gap-hap_1.44-1_unstable.log': Operation not permitted
> make: *** [debian/rules:42: clean] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/07/16/gap-hap_1.44-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220716=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: gap-hap
Source-Version: 1.44-2
Done: Joachim Zobel 

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

Debian distribution maintenance software
pp.
Joachim Zobel  (supplier of updated gap-hap 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: Sat, 16 Jul 2022 18:57:19 +0200
Source: gap-hap
Architecture: source
Version: 1.44-2
Distribution: unstable
Urgency: medium
Maintainer: Joachim Zobel 
Changed-By: Joachim Zobel 
Closes: 1015107
Changes:
 gap-hap (1.44-2) unstable; urgency=medium
 .
   * Renamed polymake directory in /tmp (Closes: #1015107).
Checksums-Sha1:
 6e7875f9a9adfc3d626c470ed83f23328a17815a 1916 gap-hap_1.44-2.dsc
 d1f65ea677836bab19a9dade6d41581197a8b181 6052 gap-hap_1.44-2.debian.tar.xz
 2f58ab38ce7c16dc9ef1562a83dc62a1edf8989d 11066 gap-hap_1.44-2_source.buildinfo
Checksums-Sha256:
 18debdb3ce306dbaab19822cbee5204c6c2f50c53f92b3647fe072b35e740c71 1916 
gap-hap_1.44-2.dsc
 94968f8daaec265fa9fe78c706fde2d64dbca3fdcdcd662efadd8399b6ca44e9 6052 
gap-hap_1.44-2.debian.tar.xz
 34c6121ec534ad548b39d7ae67c42419d7b65ecc36287188a9dcd9c65d52372f 11066 
gap-hap_1.44-2_source.buildinfo
Files:
 7814b45a26f6711a9aee1dcbf1bf796f 1916 math optional gap-hap_1.44-2.dsc
 15e1ffc72fa7ea23f399ff9be57c8bb4 6052 math optional 
gap-hap_1.44-2.debian.tar.xz
 731a619203d0290d583d12759b5f9ed2 11066 math optional 
gap-hap_1.44-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEQgKOpASi6dgKxFMUjw58K0Ui44cFAmLTOXQACgkQjw58K0Ui
44cVig/+JW3TNilfXymVodxK2yjFJSnXKzWhWf3kkpMgUgmhZPuQ0fqbnsf3XckH
5FLY5Tik2TXTBMzykbxLxEGMpJqtZQENShd+d+3im4+uUICYO6EG7XWyVK9ZuZdZ
jpBuzuqiOV7VLoTQzYM+yXPDniTND9rzZGNgifohrhmPYv6tFTs6mQswRT4dYxD5
NAB9bHYOqt48WBmUxxz0YQaow0TwhBoZL0BS1la2jsIS5OYJB8j2ufhhTQd9p9fL
S7pqIymJgzkeEC8oaQGBBI+K

Bug#1009384: marked as done (ruby-html-proofer: FTBFS: ERROR: Test "ruby3.0" failed: [31mFailure/Error: [0m[32mexpect[0m(output).to match([31m[1;31m'[0m[31msuccessfully[1;31m'[0m[31m[0m)[

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 22:04:28 +
with message-id 
and subject line Bug#1009384: fixed in ruby-html-proofer 3.19.2-5
has caused the Debian Bug report #1009384,
regarding ruby-html-proofer: FTBFS: ERROR: Test "ruby3.0" failed: 
[31mFailure/Error: [0m[32mexpect[0m(output).to 
match([31m[1;31m'[0m[31msuccessfully[1;31m'[0m[31m[0m)[0m
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.)


-- 
1009384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009384
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-html-proofer
Version: 3.19.2-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220412 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  [31mFailure/Error: [0m[32mexpect[0m(output).to 
> match([31m[1;31m'[0m[31msuccessfully[1;31m'[0m[31m[0m)[0m
>  [31m[0m
>  [31m  expected "Running [\"ScriptCheck\", \"LinkCheck\", 
> \"ImageCheck\"] on 
> spec/html-proofer/fixtures/links/broken_...elp.github.com/articles/searching-issues#no
>  failed: 403 No error\n\nHTML-Proofer found 1 failure!\n" to match 
> "successfully"[0m
>  [31m  Diff:[0m[0m
>  [31m  [0m[34m@@ -1,12 +1,23 @@[0m
>  [31m  [0m[31m-successfully[0m
>  [31m  [0m[32m+Running ["ScriptCheck", "LinkCheck", "ImageCheck"] on 
> spec/html-proofer/fixtures/links/broken_hash_on_the_web.html on *.html... [0m
>  [31m  [0m[32m+[0m
>  [31m  [0m[32m+[0m
>  [31m  [0m[32m+Checking 1 external link...[0m
>  [31m  [0m[32m+Ran on 1 file![0m
>  [31m  [0m[32m+[0m
>  [31m  [0m[32m+[0m
>  [31m  [0m[32m+[0m
>  [31m  [0m[32m+- 
> spec/html-proofer/fixtures/links/broken_hash_on_the_web.html[0m
>  [31m  [0m[32m+  *  External link 
> https://help.github.com/articles/searching-issues#no failed: 403 No error[0m
>  [31m  [0m[32m+[0m
>  [31m  [0m[32m+HTML-Proofer found 1 failure![0m
>  [31m  [0m[0m
>  [36m# ./spec/html-proofer/command_spec.rb:82:in `block (2 levels) in 
> '[0m
> 
> Finished in 23.13 seconds (files took 0.99833 seconds to load)
> [31m289 examples, 1 failure, 3 pending[0m
> 
> Failed examples:
> 
> [31mrspec ./spec/html-proofer/command_spec.rb:79[0m [36m# Command test 
> works with only-4xx[0m
> 
> Randomized with seed 41695
> 
> /usr/bin/ruby3.0 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.0" failed: 


The full build log is available from:
http://qa-logs.debian.net/2022/04/12/ruby-html-proofer_3.19.2-4_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220412;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220412=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: ruby-html-proofer
Source-Version: 3.19.2-5
Done: Cédric Boutillier 

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

Debian distribution maintenance software
pp.
Cédric Boutillier  (supplier of updated ruby-html-proofer 
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: Sat, 16 Jul 2022 23:27:35 +0200
Source: ruby-html-proofer

Bug#1015059: marked as done (node-dagre-d3-renderer: FTBFS: make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 21:35:21 +
with message-id 
and subject line Bug#1015059: fixed in node-dagre-d3-renderer 0.6.4+dfsg-5
has caused the Debian Bug report #1015059,
regarding node-dagre-d3-renderer: FTBFS: make[1]: *** [debian/rules:11: 
override_dh_auto_build] Error 1
to be marked as done.

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

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


-- 
1015059: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015059
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-dagre-d3-renderer
Version: 0.6.4+dfsg-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220716 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 '/<>'
> rollup -c debian/rollup.config.js index.js -n dagreD3 -f umd -o 
> dist/dagre-d3.js
> [36m
> [1mindex.js[22m → [1mdist/dagre-d3.js[22m...[39m
> [1m[31m[!] [1m(plugin commonjs--resolver) CompileError: Transforming 
> for-of statements is not fully supported. Use `transforms: { forOf: false }` 
> to skip transformation and disable this error, or `transforms: { 
> dangerousForOf: true }` if you know what you're doing. 
> (4:4)[22m[1m[39m[22m
> ../../../usr/share/nodejs/d3-array/src/count.js (4:4)
> [2m1 : export default function count(values, valueof) {
> 2 :   let count = 0;
> 3 :   if (valueof === undefined) {
> 4 : for (let value of values) {
> 
> ^^[22m
> [2mError
> at Function.missingTransform 
> (/usr/share/nodejs/buble/dist/buble.cjs.js:367:9)
> at Node.initialise (/usr/share/nodejs/buble/dist/buble.cjs.js:2522:17)
> at /usr/share/nodejs/buble/dist/buble.cjs.js:795:34
> at Array.forEach ()
> at Node.initialise (/usr/share/nodejs/buble/dist/buble.cjs.js:795:13)
> at Node.initialise (/usr/share/nodejs/buble/dist/buble.cjs.js:105:11)
> at Node.initialise (/usr/share/nodejs/buble/dist/buble.cjs.js:2826:9)
> at /usr/share/nodejs/buble/dist/buble.cjs.js:795:34
> at Array.forEach ()[22m
> 
> make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/07/16/node-dagre-d3-renderer_0.6.4+dfsg-4_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220716=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: node-dagre-d3-renderer
Source-Version: 0.6.4+dfsg-5
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-dagre-d3-renderer 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: Sat, 16 Jul 2022 22:57:55 +0200
Source: node-dagre-d3-renderer
Architecture: source
Version: 0.6.4+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1015059
Changes:
 node-dagre-d3-renderer (0.6.4+dfsg-5) unstable; urgency=medium
 .
   * Team upload
   * Declare compliance with policy 4.6.1
   * Fix filenamemangle
   * Drop dependency to nodejs
   * Replace deprecated rollup-plugin-buble by @rollup/plugin-babel
 (

Bug#1007237: marked as done (cryptsetup-nuke-password: autopkgtest failure)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 21:34:19 +
with message-id 
and subject line Bug#1007237: fixed in cryptsetup-nuke-password 4
has caused the Debian Bug report #1007237,
regarding cryptsetup-nuke-password: autopkgtest failure
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.)


-- 
1007237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007237
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cryptsetup-nuke-password
Version: 3
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/c/cryptsetup-nuke-password/19957107/log.gz

...
autopkgtest [15:09:59]: test askpass.sh: [---
>> Setup the 'cryptedfs' file that will contain the luks container
1+0 records in
1+0 records out
20971520 bytes (21 MB, 20 MiB) copied, 0.0281347 s, 745 MB/s
>> Format with cryptsetup
Key slot 0 created.
Command successful.
>> Add nuke passphrase
>> Open the luks container
Attaching loopback device failed (loop device with autoclear flag is required).
No usable token is available.
Command failed with code -1 (wrong or missing parameters).
autopkgtest [15:10:06]: test askpass.sh: ---]
autopkgtest [15:10:06]: test askpass.sh:  - - - - - - - - - - results - - - - - 
- - - - -
askpass.sh   FAIL non-zero exit status 1
--- End Message ---
--- Begin Message ---
Source: cryptsetup-nuke-password
Source-Version: 4
Done: Jonas Meurer 

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

Debian distribution maintenance software
pp.
Jonas Meurer  (supplier of updated 
cryptsetup-nuke-password 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: Sat, 16 Jul 2022 22:00:36 +0100
Source: cryptsetup-nuke-password
Architecture: source
Version: 4
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Jonas Meurer 
Closes: 1007237 1007933 1008527 1010035
Changes:
 cryptsetup-nuke-password (4) unstable; urgency=medium
 .
   * d/tests/control: Change restriction for askpass autopkgtest from
 `isolation-container` to `isolation-machine`. The test needs to load
 kernel modules (dm_crypt). (Closes: #1007237)
   * d/control: Bump standards-version to 4.6.1, no changes required.
   * d/po/de.po: Add german translation, thanks to Hermann-Josef Beckers.
 (Closes: #1007933)
   * d/po/es.po: Add spanish translation, thanks to Camaleón.
 (Closes: #1008527)
   * d/po/nl.po: Add dutch translation, thanks Frans Spiesschaert.
 (Closes: #1010035)
Checksums-Sha1:
 d515a0e2ce55a5ddfaafdd83874e0f8e923e 1930 cryptsetup-nuke-password_4.dsc
 f3b47ddc5407c669c7a2b4e3dac6357181767774 13368 
cryptsetup-nuke-password_4.tar.xz
 4a9151677344a1acff188251a3567d90c712f0f4 6502 
cryptsetup-nuke-password_4_amd64.buildinfo
Checksums-Sha256:
 e12bef9ee86a7364c412e3003dbff150f635d818ec242e9a35511695cfe8fa9b 1930 
cryptsetup-nuke-password_4.dsc
 1408a66c0f5735be9883a60c00dac21629be573df1bf4c5a0fd544ae5cf2e984 13368 
cryptsetup-nuke-password_4.tar.xz
 dbeeccd7fccfa017309f7d10fdaa352cab1473d21ff649dfc7e25a88d34befbf 6502 
cryptsetup-nuke-password_4_amd64.buildinfo
Files:
 fc956411c2cdd0002a7580cc30086371 1930 admin optional 
cryptsetup-nuke-password_4.dsc
 f943cccf5e78ea5cbd2b819b646d0634 13368 admin optional 
cryptsetup-nuke-password_4.tar.xz
 f5610cadb8cb33d73d6aa613deb3799c 6502 admin optional 
cryptsetup-nuke-password_4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEELIzSg9Pv30M4kOeDUmLn/0kQSf4FAmLTJ60ACgkQUmLn/0kQ
Sf72+xAAkW4nKe3YWSLwrcvE5mw5m/ktG+fUicOVsHfuqsHf7V9MucK0OSvqH6Df
RobTqaR8azLy2O1HvoVcez236A0htfmHLUIwavavLp579pdOxg8vrgr25CbZ5ncZ
LsyT7l5NJ5Vf9rIu3O+gQ2vk/+itW17+GCEUaMfELTE4Kzmu7tLt3XdzkNwW3JXW
d05/VQiJtcRcDtAWlwkgDrWZFCnmX8+43Vw8+1FeZvPy/H1ysaBotBZXLjEyuYQI
hD2jB3VVt0C+fUhy71RNm9+zFGufWzo/43CIehnSjAyqbrnDaN5Z5iHoKNv3ob00
piFGHP/VkFBxUYt6itrXK+ttEsD89yq/d05yuMgn06fCUAfxlEddoOyDLW1d6Hbk
RHkMrkWpq5Y7fGhUH0Thq/9lYqDB/fiv4n2c+QvUmzB6lqrEcskma51V6ourWIMy
sP3n9Gomhz7SsdtS4ZSA4Wm6abDmkTDXTadUy8c7DC+yFzx+dXqF3XW6IsFIKqyg

Bug#1015099: marked as done (wayvnc: FTBFS: ../src/main.c:504:9: error: too few arguments to function ‘nvnc_set_userdata’)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 21:12:15 +
with message-id 
and subject line Bug#1015099: fixed in wayvnc 0.5.0-1
has caused the Debian Bug report #1015099,
regarding wayvnc: FTBFS: ../src/main.c:504:9: error: too few arguments to 
function ‘nvnc_set_userdata’
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.)


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

Hi,

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


Relevant part (hopefully):
> cc -Iwayvnc.p -I. -I.. -I../include -I/usr/include/pixman-1 
> -I/usr/include/libdrm -I/usr/include/p11-kit-1 -fdiagnostics-color=always 
> -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu11 -O0 
> '-DPROJECT_VERSION="0.4.1"' -D_GNU_SOURCE -DNDEBUG -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MQ 
> wayvnc.p/src_main.c.o -MF wayvnc.p/src_main.c.o.d -o wayvnc.p/src_main.c.o -c 
> ../src/main.c
> ../src/main.c: In function ‘init_nvnc’:
> ../src/main.c:504:9: error: too few arguments to function ‘nvnc_set_userdata’
>   504 | nvnc_set_userdata(self->nvnc, self);
>   | ^
> In file included from ../src/main.c:27:
> /usr/include/neatvnc.h:125:6: note: declared here
>   125 | void nvnc_set_userdata(void* self, void* userdata, nvnc_cleanup_fn);
>   |  ^
> ../src/main.c:508:9: warning: implicit declaration of function 
> ‘nvnc_display_set_render_fn’; did you mean ‘nvnc_display_get_server’? 
> [-Wimplicit-function-declaration]
>   508 | nvnc_display_set_render_fn(self->nvnc_display, on_render);
>   | ^~
>   | nvnc_display_get_server
> ../src/main.c: In function ‘wayvnc_damage_region’:
> ../src/main.c:578:9: warning: implicit declaration of function 
> ‘nvnc_display_damage_region’ [-Wimplicit-function-declaration]
>   578 | nvnc_display_damage_region(self->nvnc_display, damage);
>   | ^~
> ../src/main.c: In function ‘wayvnc_process_frame’:
> ../src/main.c:638:32: error: too few arguments to function ‘nvnc_fb_new’
>   638 | self->buffer = nvnc_fb_new(width, height, format);
>   |^~~
> In file included from ../src/main.c:27:
> /usr/include/neatvnc.h:144:17: note: declared here
>   144 | struct nvnc_fb* nvnc_fb_new(uint16_t width, uint16_t height,
>   | ^~~
> ../src/main.c:639:17: warning: implicit declaration of function 
> ‘nvnc_display_set_buffer’; did you mean ‘nvnc_display_feed_buffer’? 
> [-Wimplicit-function-declaration]
>   639 | nvnc_display_set_buffer(self->nvnc_display, 
> self->buffer);
>   | ^~~
>   | nvnc_display_feed_buffer
> [36/50] cc -Iwayvnc.p -I. -I.. -I../include -I/usr/include/pixman-1 
> -I/usr/include/libdrm -I/usr/include/p11-kit-1 -fdiagnostics-color=always 
> -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu11 -O0 
> '-DPROJECT_VERSION="0.4.1"' -D_GNU_SOURCE -DNDEBUG -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MQ 
> wayvnc.p/src_seat.c.o -MF wayvnc.p/src_seat.c.o.d -o wayvnc.p/src_seat.c.o -c 
> ../src/seat.c
> [37/50] cc -Iwayvnc.p -I. -I.. -I../include -I/usr/include/pixman-1 
> -I/usr/include/libdrm -I/usr/include/p11-kit-1 -fdiagnostics-color=always 
> -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu11 -O0 
> '-DPROJECT_VERSION="0.4.1"' -D_GNU_SOURCE -DNDEBUG -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MQ 
> wayvnc.p/src_output.c.o -MF wayvnc.p/src_output.c.o.d -o 
> wayvnc.p/src_output.c.o -c ../src/output.c
> [38/50] cc -Iwayvnc.p -I. -I.. -I../include -I/usr/include/pixman-1 
> -I/usr/include/libdrm -I/usr/include/p11-kit-1 -fdiagnostics-color=always 
> -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu11 -O0 
> '-DPROJECT_VE

Processed: closing 1015041

2022-07-16 Thread Debian Bug Tracking System

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

> close 1015041
Bug #1015041 [gyp] node-opencv: FTBFS: ModuleNotFoundError: No module named 
'six'
Bug #1015051 [gyp] node-re2: FTBFS: ModuleNotFoundError: No module named 'six'
Bug #1015058 [gyp] node-expat: FTBFS: ModuleNotFoundError: No module named 'six'
Bug #1015061 [gyp] node-websocket: FTBFS: ModuleNotFoundError: No module named 
'six'
Bug #1015062 [gyp] node-shiny-server: FTBFS: ModuleNotFoundError: No module 
named 'six'
Bug #1015101 [gyp] node-sqlite3: FTBFS: ModuleNotFoundError: No module named 
'six'
Bug #1015113 [gyp] node-modern-syslog: FTBFS: ModuleNotFoundError: No module 
named 'six'
Bug #1015114 [gyp] node-iconv: FTBFS: ModuleNotFoundError: No module named 'six'
Bug #1015119 [gyp] node-nan: FTBFS: ModuleNotFoundError: No module named 'six'
Bug #1015121 [gyp] node-leveldown: FTBFS: ModuleNotFoundError: No module named 
'six'
Bug #1015130 [gyp] node-node-sass: FTBFS: ModuleNotFoundError: No module named 
'six'
Marked Bug as done
Marked Bug as done
Marked Bug as done
Marked Bug as done
Marked Bug as done
Marked Bug as done
Marked Bug as done
Marked Bug as done
Marked Bug as done
Marked Bug as done
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1015041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015041
1015051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015051
1015058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015058
1015061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015061
1015062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015062
1015101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015101
1015113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015113
1015114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015114
1015119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015119
1015121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015121
1015130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1014901: Home directories should not be setgid by default

2022-07-16 Thread Josh Triplett

On Thu, Jul 14, 2022 at 04:20:18PM -0400, Matt Barry wrote:
> On Thu, 2022-07-14 at 13:05 -0700, Josh Triplett wrote:
> > The use case below, and any other tools that create files and know to
> > set their permissions appropriately but don't expect unusual
> > ownership
> > by default:
> > > > In particular, it is common to build various kinds of filesystem,
> > > > container, or disk images, and to do so within your home
> > > > directory.
> > > > Users writing tools and scripts to build such images need to make
> > > > sure
> > > > to create files with an appropriate mode, but such scripts often
> > > > assume
> > > > (reasonably) that if they're running as root:root and they create
> > > > a
> > > > file, that file will be owned by root:root. Attempting to build
> > > > filesystems, containers, disk images, or similar in an
> > > > unexpectedly
> > > > setgid directory will produce unexpected results (leaving aside
> > > > that the
> > > > directory mode itself will be surprising).
> 
> Could you be just slightly more specific about a use case that fails? 
> Given how many times this has come up over the years, I'm trying to get
> a sense of what the *actual* issues are (as opposed to what they used
> to be).
> 
> Enough instruction that I can reproduce a specific problem(s) would be
> great.

Sure. Here's a sample of the kind of script I regularly encounter,
producing incorrect results in a setgid directory. The script expects to
produce files owned by root:root, but the files and directories get the
wrong group, and the setgid bit gets propagated to the constructed
filesystem image.

/tmp/testdir$ ls -ld
drwxr-sr-x 2 josh josh 4096 Jul 16 13:40 .
/tmp/testdir$ ls -l
total 4
-rwxr-xr-x 1 josh josh 354 Jul 16 13:40 make-filesystem.sh
/tmp/testdir$ cat make-filesystem.sh
#!/bin/bash
if [ "$(id -u)" -ne 0 ]; then
echo Run as root >&2
exit 1
fi

umask 022

mkdir fsroot fsroot/bin fsroot/etc fsroot/srv
mkdir -m 0700 fsroot/srv/workdir
echo 'nameserver 169.254.169.253' > fsroot/etc/resolv.conf
printf '#!/bin/sh\necho example binary\n' > fsroot/bin/example
chmod a+x fsroot/bin/example

mke2fs -d fsroot root.img 16M
/tmp/testdir$ sudo ./make-filesystem.sh
mke2fs 1.46.5 (30-Dec-2021)
Creating regular file root.img
Creating filesystem with 16384 1k blocks and 4096 inodes
Filesystem UUID: ec2c8666-96d9-4bce-b964-4c32ed098638
Superblock backups stored on blocks:
8193

Allocating group tables: done
Writing inode tables: done
Copying files into the device: done
Writing superblocks and filesystem accounting information: done

/tmp/testdir$ ls -l
total 1196
drwxr-sr-x 5 root josh 4096 Jul 16 13:41 fsroot
-rwxr-xr-x 1 josh josh  354 Jul 16 13:40 make-filesystem.sh
-rw-r--r-- 1 root josh 16777216 Jul 16 13:41 root.img
/tmp/testdir$ mkdir /tmp/testmount
/tmp/testdir$ sudo mount -o loop root.img /tmp/testmount
/tmp/testdir$ sudo ls -lR /tmp/testmount/
/tmp/testmount/:
total 15
drwxr-sr-x 2 root josh  1024 Jul 16 13:41 bin
drwxr-sr-x 2 root josh  1024 Jul 16 13:41 etc
drwx-- 2 root root 12288 Jul 16 13:41 lost+found
drwxr-sr-x 3 root josh  1024 Jul 16 13:41 srv

/tmp/testmount/bin:
total 1
-rwxr-xr-x 1 root josh 30 Jul 16 13:41 example

/tmp/testmount/etc:
total 1
-rw-r--r-- 1 root josh 27 Jul 16 13:41 resolv.conf

/tmp/testmount/lost+found:
total 0

/tmp/testmount/srv:
total 1
drwx--S--- 2 root josh 1024 Jul 16 13:41 workdir

/tmp/testmount/srv/workdir:
total 0

Processed: forcibly merging 1015041 1015058, forcibly merging 1015062 1015058

2022-07-16 Thread Debian Bug Tracking System

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

> forcemerge 1015041 1015058
Bug #1015041 [gyp] node-opencv: FTBFS: ModuleNotFoundError: No module named 
'six'
Bug #1015041 [gyp] node-opencv: FTBFS: ModuleNotFoundError: No module named 
'six'
Marked as found in versions gyp/0.1+20220404git9ecf45e-1.
Bug #1015119 {Done: Jérémy Lal } [gyp] node-nan: FTBFS: 
ModuleNotFoundError: No module named 'six'
'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 gyp/0.1+20220404git9ecf45e-2.
No longer marked as fixed in versions gyp/0.1+20220404git9ecf45e-2.
No longer marked as fixed in versions gyp/0.1+20220404git9ecf45e-2.
No longer marked as fixed in versions gyp/0.1+20220404git9ecf45e-2.
No longer marked as fixed in versions gyp/0.1+20220404git9ecf45e-2.
No longer marked as fixed in versions gyp/0.1+20220404git9ecf45e-2.
No longer marked as fixed in versions gyp/0.1+20220404git9ecf45e-2.
No longer marked as fixed in versions gyp/0.1+20220404git9ecf45e-2.
No longer marked as fixed in versions gyp/0.1+20220404git9ecf45e-2.
Bug #1015113 [gyp] node-modern-syslog: FTBFS: ModuleNotFoundError: No module 
named 'six'
Marked as fixed in versions gyp/0.1+20220404git9ecf45e-2.
Marked as fixed in versions gyp/0.1+20220404git9ecf45e-2.
Marked as fixed in versions gyp/0.1+20220404git9ecf45e-2.
Marked as fixed in versions gyp/0.1+20220404git9ecf45e-2.
Marked as fixed in versions gyp/0.1+20220404git9ecf45e-2.
Marked as fixed in versions gyp/0.1+20220404git9ecf45e-2.
Marked as fixed in versions gyp/0.1+20220404git9ecf45e-2.
Marked as fixed in versions gyp/0.1+20220404git9ecf45e-2.
Marked as fixed in versions gyp/0.1+20220404git9ecf45e-2.
Bug #1015051 [gyp] node-re2: FTBFS: ModuleNotFoundError: No module named 'six'
Bug #1015058 [gyp] node-expat: FTBFS: ModuleNotFoundError: No module named 'six'
Bug #1015061 [gyp] node-websocket: FTBFS: ModuleNotFoundError: No module named 
'six'
Bug #1015101 [gyp] node-sqlite3: FTBFS: ModuleNotFoundError: No module named 
'six'
Bug #1015114 [gyp] node-iconv: FTBFS: ModuleNotFoundError: No module named 'six'
Bug #1015121 [gyp] node-leveldown: FTBFS: ModuleNotFoundError: No module named 
'six'
Bug #1015130 [gyp] node-node-sass: FTBFS: ModuleNotFoundError: No module named 
'six'
Merged 1015041 1015051 1015058 1015061 1015101 1015113 1015114 1015119 1015121 
1015130
> forcemerge 1015062 1015058
Bug #1015062 [gyp] node-shiny-server: FTBFS: ModuleNotFoundError: No module 
named 'six'
Bug #1015062 [gyp] node-shiny-server: FTBFS: ModuleNotFoundError: No module 
named 'six'
Marked as found in versions gyp/0.1+20220404git9ecf45e-1.
Bug #1015041 [gyp] node-opencv: FTBFS: ModuleNotFoundError: No module named 
'six'
Bug #1015051 [gyp] node-re2: FTBFS: ModuleNotFoundError: No module named 'six'
Bug #1015058 [gyp] node-expat: FTBFS: ModuleNotFoundError: No module named 'six'
Bug #1015061 [gyp] node-websocket: FTBFS: ModuleNotFoundError: No module named 
'six'
Bug #1015101 [gyp] node-sqlite3: FTBFS: ModuleNotFoundError: No module named 
'six'
Bug #1015113 [gyp] node-modern-syslog: FTBFS: ModuleNotFoundError: No module 
named 'six'
Bug #1015114 [gyp] node-iconv: FTBFS: ModuleNotFoundError: No module named 'six'
Bug #1015119 [gyp] node-nan: FTBFS: ModuleNotFoundError: No module named 'six'
Bug #1015121 [gyp] node-leveldown: FTBFS: ModuleNotFoundError: No module named 
'six'
Bug #1015130 [gyp] node-node-sass: FTBFS: ModuleNotFoundError: No module named 
'six'
Merged 1015041 1015051 1015058 1015061 1015062 1015101 1015113 1015114 1015119 
1015121 1015130
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1015041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015041
1015051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015051
1015058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015058
1015061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015061
1015062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015062
1015101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015101
1015113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015113
1015114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015114
1015119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015119
1015121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015121
1015130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Bug#1015059 marked as pending in node-dagre-d3-renderer

2022-07-16 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 pending
Bug #1015059 [src:node-dagre-d3-renderer] node-dagre-d3-renderer: FTBFS: 
make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1
Added tag(s) pending.

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

Bug#1015059: marked as pending in node-dagre-d3-renderer

2022-07-16 Thread Yadd

Control: tag -1 pending

Hello,

Bug #1015059 in node-dagre-d3-renderer 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/js-team/node-dagre-d3-renderer/-/commit/87c29daad537e4160b5426228f1c13c6a50d2984


Replace deprecated rollup-plugin-buble by @rollup/plugin-babel

Closes: #1015059


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1015059

Bug#1015155: neatvnc: copyright Joseph Werle for murmurhash missing

2022-07-16 Thread Johannes Schauer Marin Rodrigues

Source: neatvnc
Version: 0.5.1+dfsg-1
Severity: serious
Justification: Policy 2.3
X-Debbugs-Cc: jo...@debian.org

Hi,

your recent upload of neatvnc introduced murmurhash which is copyright
"2014 Joseph Werle" but you did not add that to d/copyright:

https://sources.debian.org/src/neatvnc/0.5.1%2Bdfsg-1/src/murmurhash.c/

Thanks!

cheers, josch

Processed (with 2 errors): reassign 1015041 to gyp, reassign 1015062 to gyp, fixed 1015041 in 0.1+20220404git9ecf45e-2 ...

2022-07-16 Thread Debian Bug Tracking System

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

> reassign 1015041 gyp
Bug #1015041 [src:node-opencv] node-opencv: FTBFS: ModuleNotFoundError: No 
module named 'six'
Bug reassigned from package 'src:node-opencv' to 'gyp'.
No longer marked as found in versions node-opencv/7.0.0+git20200316.f0a03a4b-1.
Ignoring request to alter fixed versions of bug #1015041 to the same values 
previously set
> reassign 1015062 gyp
Bug #1015062 [src:node-shiny-server] node-shiny-server: FTBFS: 
ModuleNotFoundError: No module named 'six'
Bug reassigned from package 'src:node-shiny-server' to 'gyp'.
No longer marked as found in versions node-shiny-server/1.5.17.973-3.
Ignoring request to alter fixed versions of bug #1015062 to the same values 
previously set
> fixed 1015041 0.1+20220404git9ecf45e-2
Bug #1015041 [gyp] node-opencv: FTBFS: ModuleNotFoundError: No module named 
'six'
Marked as fixed in versions gyp/0.1+20220404git9ecf45e-2.
> fixed 1015062 0.1+20220404git9ecf45e-2
Bug #1015062 [gyp] node-shiny-server: FTBFS: ModuleNotFoundError: No module 
named 'six'
Marked as fixed in versions gyp/0.1+20220404git9ecf45e-2.
> merge 1015041 1015058
Bug #1015041 [gyp] node-opencv: FTBFS: ModuleNotFoundError: No module named 
'six'
Unable to merge bugs because:
done of #1015051 is 'Jérémy Lal ' not ''
done of #1015061 is 'Jérémy Lal ' not ''
done of #1015114 is 'Jérémy Lal ' not ''
done of #1015121 is 'Jérémy Lal ' not ''
done of #1015119 is 'Jérémy Lal ' not ''
done of #1015130 is 'Jérémy Lal ' not ''
done of #1015113 is 'Jérémy Lal ' not ''
done of #1015058 is 'Jérémy Lal ' not ''
done of #1015101 is 'Jérémy Lal ' not ''
Failed to merge 1015041: Did not alter merged bugs.

> merge 1015062 1015058
Bug #1015062 [gyp] node-shiny-server: FTBFS: ModuleNotFoundError: No module 
named 'six'
Failed to merge 1015062: failed to get lock on 
/srv/bugs.debian.org/spool/lock/1015058 -- Unable to lock 
/srv/bugs.debian.org/spool/lock/1015058 Resource temporarily unavailable.
Unable to lock /srv/bugs.debian.org/spool/lock/1015058 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1015058 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1015058 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1015058 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1015058 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1015058 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1015058 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1015058 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1015058 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
$locks = {
   'lockorder' => [],
   'locks' => {}
 };
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 650.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1015041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015041
1015051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015051
1015058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015058
1015061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015061
1015062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015062
1015101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015101
1015113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015113
1015114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015114
1015119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015119
1015121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015121
1015130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1015124: marked as done (python-pluggy: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 20:40:23 +
with message-id 
and subject line Bug#1015124: fixed in python-pluggy 1.0.0+repack-1
has caused the Debian Bug report #1015124,
regarding python-pluggy: FTBFS: dpkg-buildpackage: error: dpkg-source -b . 
subprocess returned exit status 2
to be marked as done.

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

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


-- 
1015124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015124
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pluggy
Version: 1.0.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220716 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 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:239: python3.9 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.9_pluggy/build' (and 
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.9' does not exist -- can't clean it
> I: pybuild base:239: python3.10 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.10_pluggy/build' (and 
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.10' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building python-pluggy using existing 
> ./python-pluggy_1.0.0.orig.tar.gz
> dpkg-source: info: local changes detected, the modified files are:
>  python-pluggy-1.0.0/src/pluggy/_version.py
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/python-pluggy_1.0.0-1.diff.gCHe4T
> dpkg-source: info: Hint: make sure the version in debian/changelog matches 
> the unpacked source tree
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> Build finished at 2022-07-16T06:06:03Z


The full build log is available from:
http://qa-logs.debian.net/2022/07/16/python-pluggy_1.0.0-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220716=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-pluggy
Source-Version: 1.0.0+repack-1
Done: Jochen Sprickerhof 

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated python-pluggy 
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: Sat, 16 Jul 2022 22:26:24 +0200
Source: python-pluggy
Architecture: source
Version: 1.0.0+repack-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Jochen Sprickerhof 
Closes: 1015124
Changes:
 python-pluggy (1.0.0+repack-1) unstable; urgency=medium
 .
   * Team upload.
   * Switch d/watch to Github to avoid _version.py
   * New upstream version 1.0.0+repack
   * Add d/clean for generated files (Closes: #1015124)
   * Bump policy version (no chang

Bug#1015068: marked as done (python-dbusmock: FTBFS: AssertionError: Regex didn't match: b'[0-9.]+ Notify "fooApp" 0 "warning_icon" "title" "my text" \\[\\] {"urgency": 1} 27\n' not found in b'1657951

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 20:40:08 +
with message-id 
and subject line Bug#1015068: fixed in python-dbusmock 0.28.2-1
has caused the Debian Bug report #1015068,
regarding python-dbusmock: FTBFS: AssertionError: Regex didn't match: b'[0-9.]+ 
Notify "fooApp" 0 "warning_icon" "title" "my text" \\[\\] {"urgency": 1} 27\n' 
not found in b'1657951521.419 GetServerInformation\n1657951521.420 
GetServerInformation\n1657951521.420 Notify "fooApp" 0 "warning_icon" "title" 
"my text" [] {"urgency": 1, "sender-pid": 169159} 27\n'
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.)


-- 
1015068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015068
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-dbusmock
Version: 0.28.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220716 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:239: python3.9 setup.py config 
> running config
> I: pybuild base:239: python3.10 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:239: /usr/bin/python3.9 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9/build/dbusmock
> copying dbusmock/__init__.py -> 
> /<>/.pybuild/cpython3_3.9/build/dbusmock
> copying dbusmock/__main__.py -> 
> /<>/.pybuild/cpython3_3.9/build/dbusmock
> copying dbusmock/mockobject.py -> 
> /<>/.pybuild/cpython3_3.9/build/dbusmock
> copying dbusmock/testcase.py -> 
> /<>/.pybuild/cpython3_3.9/build/dbusmock
> creating /<>/.pybuild/cpython3_3.9/build/dbusmock/templates
> copying dbusmock/templates/__init__.py -> 
> /<>/.pybuild/cpython3_3.9/build/dbusmock/templates
> copying dbusmock/templates/iio-sensors-proxy.py -> 
> /<>/.pybuild/cpython3_3.9/build/dbusmock/templates
> copying dbusmock/templates/ofono.py -> 
> /<>/.pybuild/cpython3_3.9/build/dbusmock/templates
> copying dbusmock/templates/logind.py -> 
> /<>/.pybuild/cpython3_3.9/build/dbusmock/templates
> copying dbusmock/templates/systemd.py -> 
> /<>/.pybuild/cpython3_3.9/build/dbusmock/templates
> copying dbusmock/templates/bluez5-obex.py -> 
> /<>/.pybuild/cpython3_3.9/build/dbusmock/templates
> copying dbusmock/templates/upower.py -> 
> /<>/.pybuild/cpython3_3.9/build/dbusmock/templates
> copying dbusmock/templates/urfkill.py -> 
> /<>/.pybuild/cpython3_3.9/build/dbusmock/templates
> copying dbusmock/templates/polkitd.py -> 
> /<>/.pybuild/cpython3_3.9/build/dbusmock/templates
> copying dbusmock/templates/timedated.py -> 
> /<>/.pybuild/cpython3_3.9/build/dbusmock/templates
> copying dbusmock/templates/low_memory_monitor.py -> 
> /<>/.pybuild/cpython3_3.9/build/dbusmock/templates
> copying dbusmock/templates/networkmanager.py -> 
> /<>/.pybuild/cpython3_3.9/build/dbusmock/templates
> copying dbusmock/templates/bluez5.py -> 
> /<>/.pybuild/cpython3_3.9/build/dbusmock/templates
> copying dbusmock/templates/notification_daemon.py -> 
> /<>/.pybuild/cpython3_3.9/build/dbusmock/templates
> copying dbusmock/templates/gnome_screensaver.py -> 
> /<>/.pybuild/cpython3_3.9/build/dbusmock/templates
> copying dbusmock/templates/power_profiles_daemon.py -> 
> /<>/.pybuild/cpython3_3.9/build/dbusmock/templates
> I: pybuild base:239: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10/build/dbusmock
> copying dbusmock/__init__.py -> 
> /<>/.pybuild/cpython3_3.10/build/dbusmock
> copying dbusmock/__main__.py -> 
> /<>/.pybuild/cpython3_3.10/build/dbusmock
> copying dbusmock/mockobject.py -> 
> /<>/.pybuild/cpython3_3.10/build/dbusmock
> copying dbusmock/testcase.py -> 
> /<>/.pybuild/cpython3_3.10/build/dbusmock
> creating /<>/

Bug#1004769: Video not handled anymore for now

2022-07-16 Thread Vincent Danjean




Le 16/07/2022 à 18:50, Steven Robbins a écrit :

Thank you for the suggestion.  I was completely unaware of "apt-listbugs".

I have just re-titled and changed the severity of this bug.


Great, it can help other users to avoid the upgrade if they want to.


Due to the large dependencies, it is probably very difficult to
downgrade digikam to a version with video support once 4:7.7.0-1
is installed. I did not try for now.


I haven't tried either, so I don't know.  Maybe one can just pull the packages
from the last stable release?  Build the 7.6 source package ?

I would say that there may well be others in your situation so if you do find a
method please report back to this bug.


Reading bug reports (in particular [1] and [2]), the root cause comes from
the ffmpeg transition in Debian. Trying to reverse this would be very
difficult leading to lots of downgrade of other packages (going back to
stable versions).

I'm also afraid that the older digikam would run with a upgraded
database. I'm not sure this won't corrupt some internal tables...

If I've time, I would probably try to build local ffmpeg4 packages
(or to install previous one if they are coinstallable) and rebuild
digikam with ffmpeg4. Of cause, this would be a local workaround,
not something sutable for Debian.

  Thanks for your work on digikam packaging

  Vincent

[1] https://bugs.kde.org/show_bug.cgi?id=453840
[2] https://bugs.kde.org/show_bug.cgi?id=448681

Processed: Downgrade severity

2022-07-16 Thread Debian Bug Tracking System

Processing control commands:

> severity -1 important
Bug #09 [src:ckeditor] ckeditor: CVE-2021-41164 CVE-2021-41165
Severity set to 'important' from 'grave'

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

Bug#999909: Downgrade severity

2022-07-16 Thread Yadd


Control: severity -1 important

Hi,

those 2 CVEs are tagged as no-dsa (minor issue), then severity can't be 
"grave". Fix pushed to unstable (4.19.0+dfsg-1)


Cheers,
Yadd

Bug#1006094: marked as done (fonts-roboto-slab: FTBFS: pkg_resources.DistributionNotFound: The 'unicodedata2>=14.0.0' distribution was not found and is required by fonttools)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 21:54:38 +0200
with message-id <6dcef693-8a59-8558-0604-04d097712...@debian.org>
and subject line FTBFS resolved
has caused the Debian Bug report #1006094,
regarding fonts-roboto-slab: FTBFS: pkg_resources.DistributionNotFound: The 
'unicodedata2>=14.0.0' distribution was not found and is required by fonttools
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.)


-- 
1006094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006094
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fonts-roboto-slab
Version: 1.100263+20170512-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> fontmake -o otf -m sources/RobotoSlab.designspace
> Traceback (most recent call last):
>   File "/usr/bin/fontmake", line 33, in 
> sys.exit(load_entry_point('fontmake==2.4.1', 'console_scripts', 
> 'fontmake')())
>   File "/usr/bin/fontmake", line 25, in importlib_load_entry_point
> return next(matches).load()
>   File "/usr/lib/python3.9/importlib/metadata.py", line 77, in load
> module = import_module(match.group('module'))
>   File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
>   File "", line 1030, in _gcd_import
>   File "", line 1007, in _find_and_load
>   File "", line 986, in _find_and_load_unlocked
>   File "", line 680, in _load_unlocked
>   File "", line 850, in exec_module
>   File "", line 228, in _call_with_frames_removed
>   File "/usr/lib/python3/dist-packages/fontmake/__main__.py", line 20, in 
> 
> from ufo2ft import CFFOptimization
>   File "/usr/lib/python3/dist-packages/ufo2ft/__init__.py", line 8, in 
> 
> from ufo2ft.featureCompiler import (
>   File "/usr/lib/python3/dist-packages/ufo2ft/featureCompiler.py", line 14, 
> in 
> from ufo2ft.featureWriters import (
>   File "/usr/lib/python3/dist-packages/ufo2ft/featureWriters/__init__.py", 
> line 11, in 
> from .markFeatureWriter import MarkFeatureWriter
>   File 
> "/usr/lib/python3/dist-packages/ufo2ft/featureWriters/markFeatureWriter.py", 
> line 9, in 
> from ufo2ft.fontInfoData import getAttrWithFallback
>   File "/usr/lib/python3/dist-packages/ufo2ft/fontInfoData.py", line 23, in 
> 
> from fontTools import ufoLib
>   File "/usr/lib/python3/dist-packages/fontTools/ufoLib/__init__.py", line 8, 
> in 
> import fs
>   File "/usr/lib/python3/dist-packages/fs/__init__.py", line 4, in 
> __import__("pkg_resources").declare_namespace(__name__)  # type: ignore
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3267, 
> in 
> def _initialize_master_working_set():
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3241, 
> in _call_aside
> f(*args, **kwargs)
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3279, 
> in _initialize_master_working_set
> working_set = WorkingSet._build_master()
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 573, 
> in _build_master
> ws.require(__requires__)
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 891, 
> in require
> needed = self.resolve(parse_requirements(requirements))
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 777, 
> in resolve
> raise DistributionNotFound(req, requirers)
> pkg_resources.DistributionNotFound: The 'unicodedata2>=14.0.0' distribution 
> was not found and is required by fonttools
> make[1]: *** [debian/rules:7: override_dh_auto_build] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/02/18/fonts-roboto-slab_1.100263+20170512-2_unstable.log

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

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

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

Version: 1.100263+20170512-2

This bug has been fixed since 2022-02-26 with the upload of fonttools 
4.29.1-2.


Regards,
Tobias


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

Processed: concerning issue, but not serious (yet)

2022-07-16 Thread Debian Bug Tracking System

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

> severity 1001999 important
Bug #1001999 [src:snapd] snapd: packaging not up to Debian standards
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Processed: Re: Bug#1015068: python-dbusmock: FTBFS: AssertionError: Regex didn't match: b'[0-9.]+ Notify "fooApp" 0 "warning_icon" "title" "my text" \\[\\] {"urgency": 1} 27\n' not found in b'16579515

2022-07-16 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 upstream pending
Bug #1015068 [src:python-dbusmock] python-dbusmock: FTBFS: AssertionError: 
Regex didn't match: b'[0-9.]+ Notify "fooApp" 0 "warning_icon" "title" "my 
text" \\[\\] {"urgency": 1} 27\n' not found in b'1657951521.419 
GetServerInformation\n1657951521.420 GetServerInformation\n1657951521.420 
Notify "fooApp" 0 "warning_icon" "title" "my text" [] {"urgency": 1, 
"sender-pid": 169159} 27\n'
Added tag(s) pending and upstream.
> forwarded -1 https://github.com/martinpitt/python-dbusmock/pull/139
Bug #1015068 [src:python-dbusmock] python-dbusmock: FTBFS: AssertionError: 
Regex didn't match: b'[0-9.]+ Notify "fooApp" 0 "warning_icon" "title" "my 
text" \\[\\] {"urgency": 1} 27\n' not found in b'1657951521.419 
GetServerInformation\n1657951521.420 GetServerInformation\n1657951521.420 
Notify "fooApp" 0 "warning_icon" "title" "my text" [] {"urgency": 1, 
"sender-pid": 169159} 27\n'
Set Bug forwarded-to-address to 
'https://github.com/martinpitt/python-dbusmock/pull/139'.

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

Bug#1015068: python-dbusmock: FTBFS: AssertionError: Regex didn't match: b'[0-9.]+ Notify "fooApp" 0 "warning_icon" "title" "my text" \\[\\] {"urgency": 1} 27\n' not found in b'1657951521.419 GetServe

2022-07-16 Thread Martin Pitt

Control: tag -1 upstream pending
Control: forwarded -1 https://github.com/martinpitt/python-dbusmock/pull/139

Ça va Lucas,

Lucas Nussbaum [2022-07-16 15:32 +0200]:
> > ==
> > FAIL: test_options (tests.test_notification_daemon.TestNotificationDaemon)
> > notify-send with some options
> > --
> > Traceback (most recent call last):
> >   File 
> > "/<>/.pybuild/cpython3_3.9/build/tests/test_notification_daemon.py",
> >  line 68, in test_options
> > self.assertRegex(log, b'[0-9.]+ Notify "fooApp" 0 "warning_icon" 
> > "title" "my text" \\[\\] {"urgency": 1} 27\n')
> > AssertionError: Regex didn't match: b'[0-9.]+ Notify "fooApp" 0 
> > "warning_icon" "title" "my text" \\[\\] {"urgency": 1} 27\n' not found in 
> > b'1657951503.818 GetServerInformation\n1657951503.819 
> > GetServerInformation\n1657951503.820 Notify "fooApp" 0 "warning_icon" 
> > "title" "my text" [] {"urgency": 1, "sender-pid": 168975} 27\n'

Thanks for the report! The tests need to be adjusted to the new libnotify 0.8.
I fixed this upstream, and will do a new release ASAP.

Bonne soirée,

Martin

Bug#1013539: marked as done (newsboat: FTBFS: unsatisfiable build-dependencies: librust-gettext-rs-0.4-dev, librust-gettext-sys-0.19-dev, librust-proptest-0.9+bit-set-dev, librust-proptest-0.9+rusty-f

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 19:49:24 +
with message-id 
and subject line Bug#1013539: fixed in newsboat 2.21-1.3
has caused the Debian Bug report #1013539,
regarding newsboat: FTBFS: unsatisfiable build-dependencies: 
librust-gettext-rs-0.4-dev, librust-gettext-sys-0.19-dev, 
librust-proptest-0.9+bit-set-dev, librust-proptest-0.9+rusty-fork-dev, 
librust-proptest-0.9+timeout-dev
to be marked as done.

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

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


-- 
1013539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013539
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: newsboat
Version: 2.21-1.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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 12), libncursesw5-dev, libxml2-dev, 
> libstfl-dev, libsqlite3-dev, perl, pkg-config, libcurl4-gnutls-dev, 
> libjson-c-dev, asciidoctor, cargo, librust-chrono-0.4-dev, 
> librust-time-0.1-dev, librust-rand-0.8-dev, 
> librust-once-cell-1+parking-lot-dev, librust-regex-1-dev, librust-url-2-dev, 
> librust-xdg-2-dev, librust-backtrace-0.3-dev, librust-backtrace-sys-0.1-dev, 
> librust-unicode-width-0.1-dev, librust-nom-7-dev, 
> librust-curl-sys-0.4+ssl-dev, librust-libc-0.2-dev, 
> librust-gettext-rs-0.4-dev, librust-natord-1-dev, librust-clap-2-dev, 
> librust-gettext-sys-0.19-dev, librust-tempfile-3-dev, 
> librust-proptest-0.9+bit-set-dev, librust-proptest-0.9+rusty-fork-dev, 
> librust-proptest-0.9+timeout-dev, librust-percent-encoding-2-dev, 
> librust-section-testing-0.0.4-dev, build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 12), libncursesw5-dev, 
> libxml2-dev, libstfl-dev, libsqlite3-dev, perl, pkg-config, 
> libcurl4-gnutls-dev, libjson-c-dev, asciidoctor, cargo, 
> librust-chrono-0.4-dev, librust-time-0.1-dev, librust-rand-0.8-dev, 
> librust-once-cell-1+parking-lot-dev, librust-regex-1-dev, librust-url-2-dev, 
> librust-xdg-2-dev, librust-backtrace-0.3-dev, librust-backtrace-sys-0.1-dev, 
> librust-unicode-width-0.1-dev, librust-nom-7-dev, 
> librust-curl-sys-0.4+ssl-dev, librust-libc-0.2-dev, 
> librust-gettext-rs-0.4-dev, librust-natord-1-dev, librust-clap-2-dev, 
> librust-gettext-sys-0.19-dev, librust-tempfile-3-dev, 
> librust-proptest-0.9+bit-set-dev, librust-proptest-0.9+rusty-fork-dev, 
> librust-proptest-0.9+timeout-dev, librust-percent-encoding-2-dev, 
> librust-section-testing-0.0.4-dev, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [637 B]
> Get:5 copy:/<>/apt_archive ./ Packages [721 B]
> Fetched 2321 B in 0s (185 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: librust-gettext-rs-0.4-dev but it 
> is not installable
>Depends: librust-gettext-sys-0.19-dev but 
> it is not installable
>Depends: librust-proptest-0.9+bit-set-dev 
> but it is not installable
>Depends: 
> librust-proptest-0.9+rusty-fork-dev but it is not installable
>Depends: librust-proptest-0.9+timeout-dev 
> but it is not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:

Bug#1015118: marked as done (node-configurable-http-proxy: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 19:49:30 +
with message-id 
and subject line Bug#1015118: fixed in node-configurable-http-proxy 
4.5.0+~cs15.1.4-6
has caused the Debian Bug report #1015118,
regarding node-configurable-http-proxy: FTBFS: dh_auto_test: error: /bin/sh -ex 
debian/tests/pkg-js/test returned exit code 1
to be marked as done.

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

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


-- 
1015118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015118
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-configurable-http-proxy
Version: 4.5.0+~cs15.1.4-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220716 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 --buildsystem=nodejs
> Found debian/nodejs/prom-client/build
>   cd ./prom-client && sh -ex ../debian/nodejs/prom-client/build
> + tsc -p .
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
> help2man -n 'configurable-on-the-fly HTTP Proxy in Node.js' -N 
> ./bin/configurable-http-proxy > configurable-http-proxy.1
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
>   ln -s ../debian/tests/test_modules/better-assert 
> node_modules/better-assert
>   ln -s ../debian/tests/test_modules/callsite node_modules/callsite
>   ln -s ../debian/tests/test_modules/request node_modules/request
>   ln -s ../debian/tests/test_modules/request-promise-core 
> node_modules/request-promise-core
>   ln -s ../debian/tests/test_modules/request-promise-native 
> node_modules/request-promise-native
>   ln -s ../. node_modules/configurable-http-proxy
>   cd ./bintrees && sh -ex ../debian/nodejs/bintrees/test
> + nodeunit ./test/test_api.js ./test/test_correctness.js
> 
> [1mtest_api.js[22m
> ✔ api - rbtree_clear
> ✔ api - rbtree_dup
> ✔ api - rbtree_nonexist
> ✔ api - rbtree_minmax
> ✔ api - rbtree_forward_it
> ✔ api - rbtree_forward_it_break
> ✔ api - rbtree_reverse_it
> ✔ api - rbtree_reverse_it_break
> ✔ api - rbtree_switch_it
> ✔ api - rbtree_empty_it
> ✔ api - rbtree_lower_bound
> ✔ api - rbtree_upper_bound
> ✔ api - rbtree_find
> ✔ api - rbtree_find_iter
> ✔ api - bintree_clear
> ✔ api - bintree_dup
> ✔ api - bintree_nonexist
> ✔ api - bintree_minmax
> ✔ api - bintree_forward_it
> ✔ api - bintree_forward_it_break
> ✔ api - bintree_reverse_it
> ✔ api - bintree_reverse_it_break
> ✔ api - bintree_switch_it
> ✔ api - bintree_empty_it
> ✔ api - bintree_lower_bound
> ✔ api - bintree_upper_bound
> ✔ api - bintree_find
> ✔ api - bintree_find_iter
> 
> [1mtest_correctness.js[22m
> ✔ correctness - rbtree_10k
> ✔ correctness - bintree_10k
> 
> [1m[32mOK: [39m[22m56 assertions (5248ms)
>   cd ./prom-client && sh -ex ../debian/nodejs/prom-client/test
> + jest --ci
> PASS test/clusterTest.js
> PASS test/pushgatewayWithPathTest.js
> PASS test/counterTest.js
> PASS test/gaugeTest.js
> PASS test/histogramTest.js
> PASS test/summaryTest.js
> PASS test/registerTest.js
> PASS test/metrics/eventLoopLagTest.js
> PASS test/metrics/heapSpacesSizeAndUsedTest.js
> PASS test/aggregatorsTest.js
> PASS test/timeWindowQuantilesTest.js
> PASS test/defaultMetricsTest.js
> PASS test/bucketGeneratorsTest.js
> PASS test/metrics/maxFileDescriptorsTest.js
> /<>/prom-client/test/metrics/eventLoopLagTest.js:19
>   expect(metrics).toHaveLength(8);
>   ^
> 
> JestAssertionError: expect(received).toHaveLength(expected)
> 
> Expected length: 8
> Received length: 0
> Received array:  []
> at Timeout._onTimeout 
> (/<>/prom-client/test/metrics/eventLoopLagTest.js:19:23) {
>   matcherResult: {
> message: 'expect(received).toHaveLength(expected)\n' +
>   '\n' +
>   'Expected length: 8\n' +
>   'Received length: 0\n' +
>   'Received array:  []',
> pass: false
>   }
> }
> PASS test/metrics/heapSizeAndUsedTest.js
> PASS test/metrics/versionTest.js
> PASS test/metrics/processRequestsTest.js
> PASS test/metrics/gcTest.js
> PASS test/metrics/processHandlesTest.js
>

Bug#1011620: marked as done (newsboat - needs update for new gettext crates.)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 19:49:24 +
with message-id 
and subject line Bug#1011620: fixed in newsboat 2.21-1.3
has caused the Debian Bug report #1011620,
regarding newsboat - needs update for new gettext crates.
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.)


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

Package: newsboat
Version: 2.21-1.2
Severity: serious

rust-gettext-sys and rust-gettext-rs have been updated to new upstream versions
breaking the build-dependencies of newsboat.
--- End Message ---
--- Begin Message ---
Source: newsboat
Source-Version: 2.21-1.3
Done: Peter Michael Green 

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

Debian distribution maintenance software
pp.
Peter Michael Green  (supplier of updated newsboat package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 16 Jul 2022 19:13:03 +
Source: newsboat
Architecture: source
Version: 2.21-1.3
Distribution: unstable
Urgency: medium
Maintainer: Nikos Tsipinakis 
Changed-By: Peter Michael Green 
Closes: 1011620 1013539
Changes:
 newsboat (2.21-1.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Bump dependencies on gettext-sys, gettext-rs and proptest crates.
 (Closes: #1011620, #1013539)
Checksums-Sha1:
 0c0fd50a9b5f1f89896e80a9a8f9af16485c40e5 2836 newsboat_2.21-1.3.dsc
 02bd529c66adcee6bce3f31bbd3ecff102c0a2da 9396 newsboat_2.21-1.3.debian.tar.xz
 4c048deb5b4a836711d2d3c47e42c3e347ed81df 13369 
newsboat_2.21-1.3_source.buildinfo
Checksums-Sha256:
 9c5f3a6a053cf041957582ee1c1d588523b91789407d5cb8cc5141db5b6bcf9b 2836 
newsboat_2.21-1.3.dsc
 507a0ac6045c2383ab7b2e99eb8b011477a91af451f5f2404fe5b520655a7300 9396 
newsboat_2.21-1.3.debian.tar.xz
 eecf3f06288dbf3cae3e410b0065befe32d0913add5a3d694586772c3fcc774b 13369 
newsboat_2.21-1.3_source.buildinfo
Files:
 39a1a8807a97e8e6e922c531132b999d 2836 net optional newsboat_2.21-1.3.dsc
 bc8e8fd24226b38d096de90838c66ba8 9396 net optional 
newsboat_2.21-1.3.debian.tar.xz
 751cc4deaa1d9da77ee6d684d32e5d0a 13369 net optional 
newsboat_2.21-1.3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmLTEf4UHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/Xu1hRAAho9bcqHi1IUfdGzOokVxJqlEPkM6
YSEzZrspK4rwGDPaQVICUe+nJ4RQVXF/KuEFQbXjd3nVLEQwWyfz+CVGdm9PJAUv
TOzvioVclQ0So4rNqnXC3jU7a7rGnvcksbpNDbcgxNL1+hizLbLYmLzNRCI8SnGh
mI+Qoxmisz66pnjDokgV2d68+1F2cvWiww78RaSQzo/LlmNe8CGUBLxEHu7vM80s
flrZXWKFu5XkDVcw5o6Dtsg9pAaOtNytCee5nGWGci6MyayV4sCGgCewG6I0W7cc
XJGn/Pv2N+Fp93MBEkm9jv3Q+VVdqKS6M6gBYNiSOBqmagPIzIIjujGn4eC0FVx3
QHuQsdEHcAaktvJtZ4OGROSOjcIimeLXrhpfbOWCqLVOCfQgrnOFurUqaGZX5NS0
CW1YFp4wQyc51NvOzWt7o4TCYAsGTSbXzFTd8mrQPNgM63onu66Qohmp9Jr4URCW
EnP8JLq2jjEkNRCvoi3v/bQLFC/xW7dAZ6NB9M+GVU/U6D6MEop6kT9s4eQjTkiW
VI6swspPY6es2Qy3kWM/w5eU440E57WaXq169HmYLKHaKsk31k0o+M10aLHFvvKR
1ZYSRdhu3dvC/rX/zIICu1uaKlGfhbh0FhLJrZknmI+U80lZ1zJcTuYgUGCCNsRn
Tc1pK3b9Jh9UixM=
=zMnO
-END PGP SIGNATURE End Message ---

Bug#965850: marked as done (ttf-bitstream-vera: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 21:30:53 +0200
with message-id 
and subject line Already fixed
has caused the Debian Bug report #965850,
regarding ttf-bitstream-vera: Removal of obsolete debhelper compat 5 and 6 in 
bookworm
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.)


-- 
965850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965850
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ttf-bitstream-vera
Version: 1.10-8
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package ttf-bitstream-vera uses debhelper with a compat level of 5 or 6,
which is deprecated and scheduled for removal[1].

Please bump the debhelper compat at your earliest convenience
/outside the freeze/!

  * Compat 13 is recommended (supported in stable-backports)

  * Compat 7 is the bare minimum


PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads
with compat bumps during the freeze.

If there is any risk that the fix for this bug might not migrate to
testing before 2021-01-01[3] then please postpone the fix until after
the freeze.


At the time of filing this bug, compat 5 and 6 are expected to be
removed "some time during the development cycle of bookworm".


Thanks,
~Niels


[1] https://lists.debian.org/debian-devel/2020/07/msg00065.html

[2] https://release.debian.org/bullseye/FAQ.html

[3] The choice of 2021-01-01 as a "deadline" is set before the actual
freeze deadline to provide a safe cut off point for most people.

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---

Version: 1.10-8.2

This bug has been fixed since 2022-02-25, but the bug number has not 
been mentioned in d/changelog.


Regards,
Tobias


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

Bug#1015150: haskell-product-isomorphic FTBFS: The constructor ‘PlainTV’ should have 2 arguments, but has been given 1

2022-07-16 Thread Adrian Bunk

Source: haskell-product-isomorphic
Version: 0.0.3.3-2
Severity: serious
Tags: ftbfs bookworm sid

https://buildd.debian.org/status/package.php?p=haskell-product-isomorphic=sid

...
src/Data/Functor/ProductIsomorphic/TH/Internal.hs:47:10: error:
• The constructor ‘PlainTV’ should have 2 arguments, but has been given 1
• In the pattern: PlainTV n
  In an equation for ‘getTV’: getTV (PlainTV n) = n
  In an equation for ‘recordInfo'’:
  recordInfo'
= d
where
d (TyConI tcon)
  = do (tcn, bs, r) <- ... <|> ...
   
d _ = Nothing
getTV (PlainTV n) = n
getTV (KindedTV n _) = n
buildT tcn vns = foldl' appT (conT tcn) [varT vn | vn <- vns]
   |
47 |   getTV (PlainTV n)=  n
   |  ^
 at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 107.

Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
 "haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock", 
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 131

Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup", 
"haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock", 
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 709
Debian::Debhelper::Buildsystem::Haskell::Recipes::haddock_recipe() 
called at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25

Bug#1011620: newsboat - needs update for new gettext crates.

2022-07-16 Thread Peter Michael Green

While I did not originally plan to NMU this, the bug has gone well over 
a month with no maintainer response, and Fabian Grünbichler said on irc 
that he had tested the patched newsboat and it worked for him, so I have 
decided to NMU it.


Final debdiff attatched.
diff -Nru newsboat-2.21/debian/changelog newsboat-2.21/debian/changelog
--- newsboat-2.21/debian/changelog  2022-03-06 00:26:54.0 +
+++ newsboat-2.21/debian/changelog  2022-07-16 19:13:03.0 +
@@ -1,3 +1,11 @@
+newsboat (2.21-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Bump dependencies on gettext-sys, gettext-rs and proptest crates.
+(Closes: #1011620, #1013539)
+
+ -- Peter Michael Green   Sat, 16 Jul 2022 19:13:03 +
+
 newsboat (2.21-1.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru newsboat-2.21/debian/control newsboat-2.21/debian/control
--- newsboat-2.21/debian/control2022-03-05 21:46:48.0 +
+++ newsboat-2.21/debian/control2022-06-23 16:47:20.0 +
@@ -26,14 +26,14 @@
librust-nom-7-dev,
librust-curl-sys-0.4+ssl-dev,
librust-libc-0.2-dev,
-   librust-gettext-rs-0.4-dev,
+   librust-gettext-rs-0.7-dev,
librust-natord-1-dev,
librust-clap-2-dev,
-   librust-gettext-sys-0.19-dev,
+   librust-gettext-sys-0.21-dev,
librust-tempfile-3-dev,
-   librust-proptest-0.9+bit-set-dev,
-   librust-proptest-0.9+rusty-fork-dev,
-   librust-proptest-0.9+timeout-dev,
+   librust-proptest-1+bit-set-dev,
+   librust-proptest-1+rusty-fork-dev,
+   librust-proptest-1+timeout-dev,
librust-percent-encoding-2-dev,
librust-section-testing-0.0.4-dev
 Standards-Version: 4.5.0
diff -Nru newsboat-2.21/debian/patches/relax-deps.diff 
newsboat-2.21/debian/patches/relax-deps.diff
--- newsboat-2.21/debian/patches/relax-deps.diff2022-03-05 
21:43:42.0 +
+++ newsboat-2.21/debian/patches/relax-deps.diff2022-06-23 
16:45:28.0 +
@@ -20,7 +20,7 @@
  curl-sys = "0.4.5"
  libc = "0.2"
 -gettext-rs = "0.5.0"
-+gettext-rs = "0.4"
++gettext-rs = "0.7.0"
  natord = "1.0.9"
  lazy_static = "1.4.0"
  
@@ -29,7 +29,7 @@
  
  [dependencies.gettext-sys]
 -version = "0.19.9"
-+version = "0.19.8"
++version = "0.21.0"
  # Don't let the crate build its own copy of gettext; force it to use the one
  # built into glibc.
  features = [ "gettext-system" ]
@@ -38,7 +38,7 @@
  tempfile = "3"
 -# 0.9.6 fixes build failures on Nightly >=2020-04-08: 
https://github.com/newsboat/newsboat/issues/870
 -proptest = ">=0.9.6"
-+proptest = "0.9"
++proptest = "1.0"
  section_testing = "0.0.4"
 Index: newsboat-2.21/rust/regex-rs/Cargo.toml
 ===
@@ -49,4 +49,4 @@
  bitflags = "1.2"
  libc = ">=0.2.69"
 -gettext-rs = "0.5.0"
-+gettext-rs = "0.4.0"
++gettext-rs = "0.7.0"

Bug#1015128: FTBFS probably already resolved

2022-07-16 Thread Dr. Tobias Quathamer


Dear APT Development Team,

just as a quick info: this FTBFS bug is most likely already resolved 
with the new upload of po4a.


See https://bugs.debian.org/1015087 for a little longer explanation.

I'm not closing this bug, however, because I didn't try to build apt and 
therefore cannot be sure that the bug is resolved.


Regards,
Tobias


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1015087: marked as done (isoquery: FTBFS: po4a::chooser: Module loading error: Can't locate Syntax/Keyword/Try.pm in @INC)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 21:07:51 +0200
with message-id 
and subject line Re: Bug#1015087: isoquery: FTBFS: po4a::chooser: Module 
loading error: Can't locate Syntax/Keyword/Try.pm in @INC
has caused the Debian Bug report #1015087,
regarding isoquery: FTBFS: po4a::chooser: Module loading error: Can't locate 
Syntax/Keyword/Try.pm in @INC
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.)


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

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> /usr/bin/rst2man ./man/isoquery.rst isoquery.1
> /bin/mkdir -p man_de
> /bin/mkdir -p man_fr
> /bin/mkdir -p man_it
> po4a-translate --format text --option markdown \
> --master ./man/isoquery.rst \
> --po ./man/de.po \
> --addendum ./man/de.add \
> --localized man_de/isoquery.rst
> po4a-translate --format text --option markdown \
> --master ./man/isoquery.rst \
> --po ./man/fr.po \
> --addendum ./man/fr.add \
> --localized man_fr/isoquery.rst
> po4a-translate --format text --option markdown \
> --master ./man/isoquery.rst \
> --po ./man/it.po \
> --addendum ./man/it.add \
> --localized man_it/isoquery.rst
> /bin/mkdir -p man_pt
> po4a-translate --format text --option markdown \
> --master ./man/isoquery.rst \
> --po ./man/pt.po \
> --addendum ./man/pt.add \
> --localized man_pt/isoquery.rst
> Unknown format type: text.
> po4a::chooser: Module loading error: Can't locate Syntax/Keyword/Try.pm in 
> @INC
> BEGIN failed--compilation aborted at /usr/share/perl5/Locale/Po4a/Text.pm 
> line 61.
> Compilation failed in require at (eval 34) line 1.
> BEGIN failed--compilation aborted at (eval 34) line 1.
> 
> List of valid formats:
>   - asciidoc: AsciiDoc format.
>   - dia: uncompressed Dia diagrams.
>   - docbook: DocBook XML.
>   - guide: Gentoo Linux's XML documentation format.
>   - ini: INI format.
>   - kernelhelp: Help messages of each kernel compilation option.
>   - latex: LaTeX format.
>   - man: Good old manual page format.
>   - pod: Perl Online Documentation format.
>   - rubydoc: Ruby Documentation (RD) format.
>   - sgml: either DebianDoc or DocBook DTD.
>   - texinfo: The info page format.
>   - tex: generic TeX documents (see also latex).
>   - text: simple text document.
>   - wml: WML documents.
>   - xhtml: XHTML documents.
>   - xml: generic XML documents (see also docbook).
>   - yaml: YAML documents.
> make[2]: *** [Makefile:1032: man_fr/isoquery.1] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/07/16/isoquery_3.3.0-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220716=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 ---

Am 16.07.22 um 15:51 schrieb Lucas Nussbaum:

Source: isoquery
Version: 3.3.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220716 ftbfs-bookworm

Hi,

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


Hi Lucas,

thanks for your continuous effort of rebuilding the archive. However, in 
this case I cannot reproduce the FTBFS. I've just built the package 
successfully in sid.


I suspect that your build happened between 2022-07-14 and 2022-07-16. On 
the first date, po4a has been uploaded with a new upstream version, 
resulting in the FTBFS in isoquery during the (translated) manpage 
generation.


On 2022-07-16, po4a has been uploaded with a new runtime dependency 
(libsyntax-keyword-try-perl), so I assum

Bug#1015099: wayvnc: FTBFS: ../src/main.c:504:9: error: too few arguments to function ‘nvnc_set_userdata’

2022-07-16 Thread Johannes Schauer Marin Rodrigues

Hi Boyuan,

recently you uploaded neatvnc 0.5.1+dfsg-1 without making sure that its reverse
dependencies don't break. This resulted in the following FTBFS for wayvnc. I'm
fixing that now, but in the future, please do a rebuild of your reverse
dependencies before uploading or upload to experimental and notify maintainers
of your reverse dependencies so that they can fix them before a mass bug filing
finds the problem.

Thanks!

cheers, josch

Quoting Lucas Nussbaum (2022-07-16 15:23:55)
> Source: wayvnc
> Version: 0.4.1-1
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20220716 ftbfs-bookworm
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> 
> Relevant part (hopefully):
> > cc -Iwayvnc.p -I. -I.. -I../include -I/usr/include/pixman-1 
> > -I/usr/include/libdrm -I/usr/include/p11-kit-1 -fdiagnostics-color=always 
> > -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu11 -O0 
> > '-DPROJECT_VERSION="0.4.1"' -D_GNU_SOURCE -DNDEBUG -g -O2 
> > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MQ 
> > wayvnc.p/src_main.c.o -MF wayvnc.p/src_main.c.o.d -o wayvnc.p/src_main.c.o 
> > -c ../src/main.c
> > ../src/main.c: In function ‘init_nvnc’:
> > ../src/main.c:504:9: error: too few arguments to function 
> > ‘nvnc_set_userdata’
> >   504 | nvnc_set_userdata(self->nvnc, self);
> >   | ^
> > In file included from ../src/main.c:27:
> > /usr/include/neatvnc.h:125:6: note: declared here
> >   125 | void nvnc_set_userdata(void* self, void* userdata, nvnc_cleanup_fn);
> >   |  ^
> > ../src/main.c:508:9: warning: implicit declaration of function 
> > ‘nvnc_display_set_render_fn’; did you mean ‘nvnc_display_get_server’? 
> > [-Wimplicit-function-declaration]
> >   508 | nvnc_display_set_render_fn(self->nvnc_display, on_render);
> >   | ^~
> >   | nvnc_display_get_server
> > ../src/main.c: In function ‘wayvnc_damage_region’:
> > ../src/main.c:578:9: warning: implicit declaration of function 
> > ‘nvnc_display_damage_region’ [-Wimplicit-function-declaration]
> >   578 | nvnc_display_damage_region(self->nvnc_display, damage);
> >   | ^~
> > ../src/main.c: In function ‘wayvnc_process_frame’:
> > ../src/main.c:638:32: error: too few arguments to function ‘nvnc_fb_new’
> >   638 | self->buffer = nvnc_fb_new(width, height, format);
> >   |^~~
> > In file included from ../src/main.c:27:
> > /usr/include/neatvnc.h:144:17: note: declared here
> >   144 | struct nvnc_fb* nvnc_fb_new(uint16_t width, uint16_t height,
> >   | ^~~
> > ../src/main.c:639:17: warning: implicit declaration of function 
> > ‘nvnc_display_set_buffer’; did you mean ‘nvnc_display_feed_buffer’? 
> > [-Wimplicit-function-declaration]
> >   639 | nvnc_display_set_buffer(self->nvnc_display, 
> > self->buffer);
> >   | ^~~
> >   | nvnc_display_feed_buffer
> > [36/50] cc -Iwayvnc.p -I. -I.. -I../include -I/usr/include/pixman-1 
> > -I/usr/include/libdrm -I/usr/include/p11-kit-1 -fdiagnostics-color=always 
> > -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu11 -O0 
> > '-DPROJECT_VERSION="0.4.1"' -D_GNU_SOURCE -DNDEBUG -g -O2 
> > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MQ 
> > wayvnc.p/src_seat.c.o -MF wayvnc.p/src_seat.c.o.d -o wayvnc.p/src_seat.c.o 
> > -c ../src/seat.c
> > [37/50] cc -Iwayvnc.p -I. -I.. -I../include -I/usr/include/pixman-1 
> > -I/usr/include/libdrm -I/usr/include/p11-kit-1 -fdiagnostics-color=always 
> > -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu11 -O0 
> > '-DPROJECT_VERSION="0.4.1"' -D_GNU_SOURCE -DNDEBUG -g -O2 
> > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MQ 
> > wayvnc.p/src_output.c.o -MF wayvnc.p/src_output.c.o.d -o 
> > wayvnc.p/src_output.c.o -c ../src/output.c
> > [38/50] cc -Iwayvnc.p -I. -I.. -I../include -I/usr/include/pixman-1 
> > -I/usr/include/libdrm -I/usr/include/p11-kit-1 -fdiagnostics-color=always 
> > -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu11 -O0 
> > '-

Bug#1015132: meson: FTBFS: ./b 52a78b9866/../test cases/failing build/2 hidden symbol/bobuser.c:4: undefined reference to `hidden_function'

2022-07-16 Thread Lucas Nussbaum

On 16/07/22 at 22:17 +0300, Jussi Pakkanen wrote:
> On Sat, 16 Jul 2022 at 17:04, Lucas Nussbaum  wrote:
> 
> > Relevant part (hopefully):
> > > /usr/bin/ld: bobuser.p/bobuser.c.o: in function `main':
> > > ./b 52a78b9866/../test cases/failing build/2 hidden symbol/bobuser.c:4: 
> > > undefined reference to `hidden_function'
> > > collect2: error: ld returned 1 exit status
> 
> This is the second time (at least) that this issue has been
> incorrectly reported. This is not a test failure. As you can tell the
> test name has "failing build" in it, which means that failing to
> compile is the correct behaviour. If this report has been done by
> hand, please in the future report the thing that actually failed (if
> any). If this is an automated test then please fix it to not report
> spurious failures like this.

Hi,

The script I use to extract the failure from the log might have guessed
badly indeed, however the build still fails, as shown by the full log
linked in the bug:
http://qa-logs.debian.net/2022/07/16/meson_0.63.0-1_unstable.log
SO I wouldn't call that a "spurious failure".

However looking at the log I don't really understand why the
override_dh_auto_test target fails. Can you explain? Maybe I can improve
my script.

Lucas

Processed: Re: gir1.2-notify-0.7: Upgrade to version 0.8.0-1 breaks at least two packages that use Python

2022-07-16 Thread Debian Bug Tracking System

Processing control commands:

> affects -1 + cinnamon
Bug #1015006 [gir1.2-notify-0.7] gir1.2-notify-0.7: Upgrade to version 0.8.0-1 
breaks at least two packages that use Python
Added indication that 1015006 affects cinnamon

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

Bug#1015006: gir1.2-notify-0.7: Upgrade to version 0.8.0-1 breaks at least two packages that use Python

2022-07-16 Thread Fabio Fantoni


Control: affects -1 + cinnamon

This make unable to start also cinnamon-settings



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1015146: rust-cbindgen_0.23.0-1~deb10u1_s390x-buildd.changes REJECTED

2022-07-16 Thread Aurelien Jarno

Source: rust-cbindgen
Version: 0.23.0-1~deb10u1
Severity: serious
X-Debbugs-Cc: po...@debian.org

On 2022-07-16 15:34, Debian FTP Masters wrote:
> 
> 
> cbindgen_0.23.0-1~deb10u1_s390x.deb: has 1 file(s) with a timestamp too far 
> in the past:
>   usr/share/doc/cbindgen/changelog.gz (Thu Nov 29 21:33:09 1973)
> 
> 
> 
> ===
> 
> Please feel free to respond to this email if you don't understand why
> your files were rejected, or if you upload new files which address our
> concerns.
> 
> 
> 


signature.asc
Description: PGP signature

Bug#1013420: corsix-th FTBFS with ffmpeg 5.0.1

2022-07-16 Thread Alexandre Detiste

lua-lpeg is orphaned ... someone has to take care of it first;
I might even adopt it.

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

I created a Merge Request:

https://salsa.debian.org/lua-team/lua-lpeg/-/merge_requests/1

Le sam. 16 juil. 2022 à 20:09, Alexandre Detiste
 a écrit :
>
> Hi,
>
> I imported and packaged corsix-th 0.66.
>
> This fix this one build time bug but not the run-time one.
>
> >Welcome to CorsixTH v0.66!
> >
> >An error has occurred in CorsixTH:
> >/usr/share/games/corsix-th/Lua/strict.lua:66: module 'lpeg' not found:
> >no field package.preload['lpeg']
> >no file './lpeg.lua'
> >no file './lpeg/init.lua'
> >[C]: in ?
> >/usr/share/games/corsix-th/Lua/audio.lua:662: attempt to index a nil >value 
> >(field 'ui')
>
> Greetings
>
> Alexandre Detiste

Bug#860336: marked as done (parse error in Request.php)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 18:31:11 +
with message-id 
and subject line Bug#1015140: Removed package(s) from unstable
has caused the Debian Bug report #860336,
regarding parse error in Request.php
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.)


-- 
860336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860336
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-http-request
Version: 1.4.4-5

When I try to open a web page implemented using PHP, I get error

[Fri Apr 14 20:04:15.147463 2017] [:error] [pid 977] [client ::1:48700] PHP 
Parse error:  syntax error, unexpected 'new' (T_NEW) in 
/usr/share/php/HTTP/Request.php on line 412

The offending line is here:

function setURL($url)
{
$this->_url =  Net_URL($url, $this->_useBrackets);

This page used to work on Jessie, but now fails on Stretch.

-- Juha
--- End Message ---
--- Begin Message ---
Version: 1.4.4-5+rm

Dear submitter,

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

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

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

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

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#882901: marked as done (php-numbers-words FTBFS with phpunit 6.4.4-2)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 18:32:16 +
with message-id 
and subject line Bug#1015141: Removed package(s) from unstable
has caused the Debian Bug report #882901,
regarding php-numbers-words FTBFS with phpunit 6.4.4-2
to be marked as done.

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

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


-- 
882901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882901
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-numbers-words
Version: 0.18.1-2
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/php-numbers-words.html

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/php-numbers-words-0.18.1'
phpunit --configuration Numbers_Words-*/tests/phpunit.xml Numbers_Words-*/tests
PHP Fatal error:  Class 'PHPUnit_Framework_TestCase' not found in 
/build/1st/php-numbers-words-0.18.1/Numbers_Words-0.18.1/tests/BulgarianTest.php
 on line 25
debian/rules:7: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 255
--- End Message ---
--- Begin Message ---
Version: 0.18.1-2+rm

Dear submitter,

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

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

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

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

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#941264: marked as done (phpunit breaks php-cache-lite autopkgtest: tries to write to /usr/bin/.phpunit.result.cache)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 18:27:02 +
with message-id 
and subject line Bug#1014698: Removed package(s) from unstable
has caused the Debian Bug report #941264,
regarding phpunit breaks php-cache-lite autopkgtest: tries to write to 
/usr/bin/.phpunit.result.cache
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.)


-- 
941264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941264
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: phpunit, php-cache-lite
Control: found -1 phpunit/8.3.5-1
Control: found -1 php-cache-lite/1.8.2-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of phpunit the autopkgtest of php-cache-lite fails
in testing when that autopkgtest is run with the binary packages of
phpunit from unstable. It passes when run with only packages from
testing. In tabular form:
   passfail
phpunitfrom testing8.3.5-1
php-cache-lite from testing1.8.2-1
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

I copied some of the output at the bottom of this report. It seems the
test now tries to write in /usr/bin, which is obviously not good.

Currently this regression is blocking the migration of phpunit to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?

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

Paul

[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
phpunit/8.3.5-1. I.e. due to versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=phpunit

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-cache-lite/3027486/log.gz

autopkgtest [02:12:32]: test command1: [---
PHPUnit 8.3.5 by Sebastian Bergmann and contributors.

  24 /
24 (100%)PHP Warning:
file_put_contents(/usr/bin/.phpunit.result.cache): failed to open
stream: Permission denied in
/usr/share/php/PHPUnit/Runner/DefaultTestResultCache.php on line 108


Time: 15.44 seconds, Memory: 4.00 MB

OK (24 tests, 30 assertions)
autopkgtest [02:12:48]: test command1: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 1.8.2-1+rm

Dear submitter,

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

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

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

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

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#940275: marked as done (FTBFS with recent PHPUnit (8))

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 18:27:02 +
with message-id 
and subject line Bug#1014698: Removed package(s) from unstable
has caused the Debian Bug report #940275,
regarding FTBFS with recent PHPUnit (8)
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.)


-- 
940275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940275
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-cache-lite
Version: 1.8.2-1
Severity: serious

Hi,

This package FTBFS with recent PHPUnit (8). Even if the fix may be
trivial, I open this bug report to see php-cache-lite removed from
testing unless there is a good reason to keep it in Debian.

“This package is not maintained” [Upstream], is only a php-xml-rpc2
dependency in Debian (and php-xml-rpc2 is a leaf package), and has a low
popcon.

Upstream: https://pear.php.net/package/Cache_Lite/

Regards

David


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

Dear submitter,

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

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

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

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

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#882910: marked as done (php-http-request2 FTBFS with phpunit 6.4.4-2)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 18:27:41 +
with message-id 
and subject line Bug#1014700: Removed package(s) from unstable
has caused the Debian Bug report #882910,
regarding php-http-request2 FTBFS with phpunit 6.4.4-2
to be marked as done.

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

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


-- 
882910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882910
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-http-request2
Version: 2.3.0-1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/php-http-request2.html

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/php-http-request2-2.3.0'
cd HTTP_Request2-* && \
phpunit tests
PHP Fatal error:  Class 'PHPUnit_Framework_TestCase' not found in 
/build/1st/php-http-request2-2.3.0/HTTP_Request2-2.3.0/tests/ObserverTest.php 
on line 48
debian/rules:7: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 255
--- End Message ---
--- Begin Message ---
Version: 2.3.0-1+rm

Dear submitter,

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

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

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

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

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#988440: marked as done (golang-github-seccomp-containers-golang: Keep out of bookworm)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 18:24:54 +
with message-id 
and subject line Bug#1014673: Removed package(s) from unstable
has caused the Debian Bug report #988440,
regarding golang-github-seccomp-containers-golang: Keep out of bookworm
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.)


-- 
988440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988440
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-seccomp-containers-golang
Version: 0.3.2-1
Severity: serious
Tags: bookworm sid

Hello,

golang-github-seccomp-containers-golang is now deprecated upstream and
has been replaced by containers-common

This package should be removed of the archive when the rdeps updated to
not depends against this package.

Better to keep this outside of bookworm in any cases

Kind regards,

Laurent Bigonville

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

Kernel: Linux 5.10.0-6-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
--- End Message ---
--- Begin Message ---
Version: 0.3.2-2+rm

Dear submitter,

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

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

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

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

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#976794: marked as done (Useless in Debian)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 18:25:17 +
with message-id 
and subject line Bug#1014688: Removed package(s) from unstable
has caused the Debian Bug report #976794,
regarding Useless in Debian
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.)


-- 
976794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976794
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-doctrine-reflection
Version: 1.2.2-1
Severity: serious
X-Debbugs-Cc: pkg-php-p...@lists.alioth.debian.org

[ Filled as an RC-bug by the maintainer to see the package auto-removed
  from testing. ]

I packaged php-doctrine-reflection as used by php-doctrine-persistence,
but php-doctrine-persistence does not use is anymore (well, the version
in experimental does not use it, but it should soon be uploaded to
unstable, before this package gets removed anyway). There is a priori
little point to ship php-doctrine-reflection in the next stable Debian
release.

I intend to follow up with an RM request in a few months if nobody
objects (but feel free to beat me to it).

Regards

David


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 1.2.2-2+rm

Dear submitter,

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

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

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

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

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#949016: marked as done (Useless in Debian)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 18:24:21 +
with message-id 
and subject line Bug#1014671: Removed package(s) from unstable
has caused the Debian Bug report #949016,
regarding Useless in Debian
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.)


-- 
949016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949016
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-doctrine-cache-bundle
Version: 1.3.5+git-1
Severity: serious

[ Filled as an RC-bug by the maintainer to see the package auto-removed
  from testing. ]

I packaged php-doctrine-cache-bundle as used by symfony, but symfony
does not use is anymore (it uses php-doctrine-bundle instead, as a
build-dependency). There is a priori little point to ship
php-doctrine-cache-bundle in the next stable Debian release.

I intend to follow up with an RM request in a few months if nobody
objects (but feel free to beat me to it).

Regards

David


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

Dear submitter,

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

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

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

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

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

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

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 18:20:47 +
with message-id 
and subject line Bug#1014632: Removed package(s) from unstable
has caused the Debian Bug report #999133,
regarding sapphire: missing required debian/rules targets build-arch and/or 
build-indep
to be marked as done.

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

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


-- 
999133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999133
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sapphire
Version: 0.15.8-9.1
Severity: important
Justification: Debian Policy section 4.9
Tags: bookworm sid
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

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

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

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00052.html .
The severity of this bug will be changed to 'serious' after a month.

Best,

Lucas
--- End Message ---
--- Begin Message ---
Version: 0.15.8-9.1+rm

Dear submitter,

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

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

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

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

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#1005383: marked as done (Useless in Debian)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 18:23:49 +
with message-id 
and subject line Bug#1014670: Removed package(s) from unstable
has caused the Debian Bug report #1005383,
regarding Useless in Debian
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.)


-- 
1005383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005383
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-xml-htmlsax3
Version: 3.0.0+really3.0.0-4
Severity: serious
Tags: bookworm sid

[ Filled as an RC-bug by the maintainer to see the package auto-removed
  from testing. ]

php-xml-htmlsax3 was packaged as a spip dependency, but the embedded
copy in SPIP is actually updated to work with recent versions of PHP,
while php-xml-htmlsax3 seems dead upstream. Since php-xml-htmlsax3 does
not have any other reverse-dependencies, the spip package now uses its
embedded up-to-date copy, and the php-xml-htmlsax3 package is now
useless.

I intend to follow up with an RM request in a few months if nobody
objects (but feel free to beat me to it).

Regards

David


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 3.0.0+really3.0.0-4+rm

Dear submitter,

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

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

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

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

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#936459: marked as done (dvcs-autosync: Python2 removal in sid/bullseye)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 18:21:52 +
with message-id 
and subject line Bug#1014656: Removed package(s) from unstable
has caused the Debian Bug report #936459,
regarding dvcs-autosync: Python2 removal in sid/bullseye
to be marked as done.

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

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


-- 
936459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dvcs-autosync
Version: 0.5+nmu1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:dvcs-autosync

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Version: 0.5+nmu1+rm

Dear submitter,

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

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

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

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

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#935639: marked as done (Abandoned upstream)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 18:23:25 +
with message-id 
and subject line Bug#1014669: Removed package(s) from unstable
has caused the Debian Bug report #935639,
regarding Abandoned upstream
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.)


-- 
935639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935639
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: phpunit-dbunit
Version: 4.0.0-2
Severity: serious

[ Filled as an RC-bug by the maintainer to see the package auto-removed
  from testing. ]

Since this PHPUnit extension is abandoned upstream and nothing depends
on it in Debian, there is a priori little point to keep this package in
the next stable Debian release.

I intend to follow up with an RM request in a few months if nobody
objects (but feel free to beat me to it).

Regards

David

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

Kernel: Linux 5.2.0-2-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_CRAP, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages phpunit-dbunit depends on:
ii  php-common2:69
ii  php-symfony-yaml  4.3.3+dfsg-3
ii  php-xml   2:7.3+69
ii  php7.3-xml [php-xml]  7.3.8-1
ii  phpunit   8.2.4-1

phpunit-dbunit recommends no packages.

phpunit-dbunit suggests no packages.


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 4.0.0-2+rm

Dear submitter,

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

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

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

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

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#935384: marked as done (Abandoned upstream)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 18:22:53 +
with message-id 
and subject line Bug#1014668: Removed package(s) from unstable
has caused the Debian Bug report #935384,
regarding Abandoned upstream
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.)


-- 
935384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935384
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: phpunit-git
Version: 2.1.4-1
Severity: serious

[ Filled as an RC-bug by the maintainer to see the package auto-removed
  from testing. ]

Since this Git wrapper is abandoned upstream and nothing depends on it
in Debian, there is a priori little point to keep this package in the
next stable Debian release.

I intend to follow up with an RM request in a few months if nobody
objects (but feel free to beat me to it).

Regards

David


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

Dear submitter,

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

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

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

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

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#910813: marked as done (doc-linux-fr: FTBFS, latex error "Package inputenc Error: Invalid UTF-8 byte sequence")

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 18:22:21 +
with message-id 
and subject line Bug#1014667: Removed package(s) from unstable
has caused the Debian Bug report #910813,
regarding doc-linux-fr: FTBFS, latex error "Package inputenc Error: Invalid 
UTF-8 byte sequence"
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.)


-- 
910813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910813
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: doc-linux-fr
Version: 2013.01-3
Severity: serious

Hi David,

After fixing #880786, doc-linux-fr would still FTBFS due to LaTeX error.
Example source repo can be found at
https://salsa.debian.org/debian/doc-linux-fr .

 debian/rules build
dh build
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
cd fcol-faq && make
make[2]: Entering directory '/<>/fcol-faq'
sed -e 's/%ISOent;/%TeXent;/' < faq-fcol.xml > faq-fcol-LaTeX.xml
xsltproc --catalogs --nonet --novalid to_tex.xsl faq-fcol-LaTeX.xml >
faq-fcol.tex
Variable $SGML_CATALOG_FILES not set
latex faq-fcol.tex ;
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live
2019/dev/Debian) (preloaded format=latex)
 restricted \write18 enabled.
entering extended mode
(./faq-fcol.tex
LaTeX2e <2018-04-01> patch level 5
(/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size11.clo))
(/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
(/usr/share/texlive/texmf-dist/tex/generic/babel/switch.def)
(/usr/share/texlive/texmf-dist/tex/generic/babel-french/frenchb.ldf

Package babel-french Warning: Option `frenchb' for Babel is *deprecated*,
(babel-french)it might be removed sooner or later. Please
(babel-french)use `french' instead; reported on input line 35.

(/usr/share/texlive/texmf-dist/tex/generic/babel-french/french.ldf
(/usr/share/texlive/texmf-dist/tex/generic/babel/babel.def
(/usr/share/texlive/texmf-dist/tex/generic/babel/txtbabel.def)
(/usr/share/texlive/texmf-dist/tex/latex/carlisle/scalefnt.sty)
(/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
(/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty
(/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.def))
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/times.sty)
(/usr/share/texlive/texmf-dist/tex/latex/geometry/geometry.sty
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifpdf.sty)
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifvtex.sty)
(/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty))
(/usr/share/texlive/texmf-dist/tex/latex/relsize/relsize.sty)
(/usr/share/texlive/texmf-dist/tex/latex/url/url.sty)
(/usr/share/texlive/texmf-dist/tex/latex/moreverb/moreverb.sty
(/usr/share/texlive/texmf-dist/tex/latex/tools/verbatim.sty))
(/usr/share/texlive/texmf-dist/tex/latex/fancyhdr/fancyhdr.sty)
No file faq-fcol.aux.
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1ptm.fd)
*geometry* driver: auto-detecting
*geometry* detected driver: dvips

! Package inputenc Error: Invalid UTF-8 byte sequence.

See the inputenc package documentation for explanation.
Type  H   for immediate help.
 ...

l.27   \maketitle

?
! Emergency stop.
 ...

l.27   \maketitle

No pages of output.
Transcript written on faq-fcol.log.
make[2]: *** [Makefile:30: faq-fcol.dvi] Error 1
make[2]: Leaving directory '/<>/fcol-faq'
make[1]: *** [debian/rules:120: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:161: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


==

Besides, I'm wondering if doc-linux-fr is still relavent for future
Debian releases.
Is it okay that we eventually remove it from Debian archive?

--
Thanks,
Boyuan Yang
--- End Message ---
--- Begin Message ---
Version: 2013.01-3+rm

Dear submitter,

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

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

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

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

This message was generated automatically; if you believe that there is

Bug#880786: marked as done (doc-linux-fr build depends on removed transitional package lynx-cur)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 18:22:21 +
with message-id 
and subject line Bug#1014667: Removed package(s) from unstable
has caused the Debian Bug report #880786,
regarding doc-linux-fr build depends on removed transitional package lynx-cur
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.)


-- 
880786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880786
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: doc-linux-fr
Version: 2013.01-3
Severity: serious
Tags: buster sid

The following packages have unmet dependencies:
 builddeps:doc-linux-fr : Depends: lynx-cur but it is not installable


Please update the build dependency to lynx.
--- End Message ---
--- Begin Message ---
Version: 2013.01-3+rm

Dear submitter,

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

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

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

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

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#906953: marked as done (doc-linux-fr: French translations of horribly outdated documentation)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 18:22:21 +
with message-id 
and subject line Bug#1014667: Removed package(s) from unstable
has caused the Debian Bug report #906953,
regarding doc-linux-fr: French translations of horribly outdated documentation
to be marked as done.

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

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


-- 
906953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906953
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: doc-linux-fr
Version: 2013.01-3
Severity: serious
Tags: buster sid

The doc-linux-* packages were very useful 20 years ago.

In the meantime Linux has changed a lot,
but the documentation has not been updated.
Updates in the past 15 years were minor updates,
everywhere the contents is outdated and sometimes
even the topic is completely irrelevant now.

A translation of outdated documentation stays outdated.

IMHO our users will be better served without this package in
buster, there are better sources of information available.
--- End Message ---
--- Begin Message ---
Version: 2013.01-3+rm

Dear submitter,

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

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

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

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

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#997138: marked as done (ffdiaporama: FTBFS: engine/_EncodeVideo.cpp:134:46: error: ‘AVStream’ {aka ‘struct AVStream’} has no member named ‘probe_data’; did you mean ‘priv_data’?)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 18:17:10 +
with message-id 
and subject line Bug#1014378: Removed package(s) from unstable
has caused the Debian Bug report #997138,
regarding ffdiaporama: FTBFS: engine/_EncodeVideo.cpp:134:46: error: ‘AVStream’ 
{aka ‘struct AVStream’} has no member named ‘probe_data’; did you mean 
‘priv_data’?
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.)


-- 
997138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997138
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ffdiaporama
Version: 2.1+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> In file included from 
> /usr/include/x86_64-linux-gnu/libavformat/avformat.h:312,
>  from /usr/include/x86_64-linux-gnu/libavdevice/avdevice.h:51,
>  from engine/cDeviceModelDef.h:47,
>  from engine/cApplicationConfig.h:42,
>  from engine/_Transition.h:80,
>  from engine/_Diaporama.h:26,
>  from engine/_EncodeVideo.h:28,
>  from engine/_EncodeVideo.cpp:21:
> /usr/include/x86_64-linux-gnu/libavcodec/avcodec.h:1764:35: note: declared 
> here
>  1764 | attribute_deprecated AVFrame *coded_frame;
>   |   ^~~
> make[2]: *** [Makefile:4376: _EncodeVideo.o] Error 1


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

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

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

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

Dear submitter,

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

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

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

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

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#1014462: marked as done (libzapojit: unmaintained, only used by gnome-documents)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 18:19:42 +
with message-id 
and subject line Bug#1014464: Removed package(s) from unstable
has caused the Debian Bug report #1014462,
regarding libzapojit: unmaintained, only used by gnome-documents
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.)


-- 
1014462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014462
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libzapojit
Version: 3.34.0-4
Severity: serious

libzapojit has been archived. That means that bug reports, bug fixes,
translations, etc. are no longer being accepted for it.

https://gitlab.gnome.org/GNOME/libzapojit

https://discourse.gnome.org/t/gnome-online-miners-is-archived/10374

It was only really used by gnome-documents which is being removed from
Debian. Therefore, we'll remove libzapojit too.

Thank you,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 0.0.3-5+rm

Dear submitter,

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

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

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

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

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#1014281: marked as done (ffdiaporama: Crashes on start with "malloc(): corrupted top size")

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 18:17:10 +
with message-id 
and subject line Bug#1014378: Removed package(s) from unstable
has caused the Debian Bug report #1014281,
regarding ffdiaporama: Crashes on start with "malloc(): corrupted top size"
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.)


-- 
1014281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014281
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ffdiaporama
Version: 2.1+dfsg-1+b3
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: skqu...@rushpost.com

Dear Maintainer,

   * What led up to the situation?

Trying to run ffdiaporama for the first time.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Run the executable "ffDiaporama" from a terminal.

   * What was the outcome of this action?

The program appears to start normally, but I get this output:

$ ffDiaporama
[07:09:12.213:INFO] QT Version:5.15.2
[07:09:12.213:INFO] StartupDir /home/skquinn
[07:09:12.213:INFO] Application not found in directory
/home/skquinn/BUILDVERSION.txt
[07:09:12.213:INFO] Application not found in directory
/../../ffDiaporama/BUILDVERSION.txt
[07:09:12.213:INFO] Application not found in directory
/../ffDiaporama/BUILDVERSION.txt
[07:09:12.213:INFO] Application not found in directory
/opt/share/ffDiaporama/BUILDVERSION.txt
[07:09:12.213:INFO] Application found in directory
/usr/share/ffDiaporama/BUILDVERSION.txt
[07:09:12.213:INFO] Set working path to /usr/share/ffDiaporama
[07:09:12.213:INFO] Start ffDiaporama 2.1 (20140209) ...
[07:09:12.286:INFO] Parse command line ...
[07:09:12.286:INFO] Set LogLevel to INFORMATION
[07:09:12.286:INFO] Start GUI ...
[07:09:12.287:INFO] Start ...
libpng warning: iCCP: known incorrect sRGB profile
[07:09:12.309:INFO] Init home user database...
[07:09:12.311:INFO] Init translations...
[07:09:12.312:INFO] Read configuration file
/usr/share/ffDiaporama/ffDiaporama.xml
[07:09:12.315:INFO] Read configuration file
/usr/share/ffDiaporama/Devices.xml
[07:09:12.321:INFO] Read configuration file
/home/skquinn/.ffDiaporama/ffDiaporama.xml
[07:09:12.321:INFO] Read configuration file
/home/skquinn/.ffDiaporama/Devices.xml
[07:09:12.322:ERROR]Restore from a previous crash...
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
[07:09:13.075:INFO] Loading system icons...
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
[07:09:13.104:INFO] Starting libav...
[07:09:13.105:INFO] Loading background library...
[07:09:13.114:INFO] Loading text frame library...
[07:09:13.139:INFO] Loading no-luma transitions...
[07:09:13.142:INFO] Loading luma transitions...
[07:09:13.310:INFO] Scan drives in computer...
[07:09:13.310:INFO] Register models...
[07:09:13.646:INFO] Reading directory content (~/)
[07:09:13.796:WARNING]  LIBAV: Warning: data is not aligned! This can lead to a
speed loss
[07:09:13.801:INFO] LIBAV: Statistics: 32768 bytes read, 0 seeks
[07:09:13.807:INFO] LIBAV: Reinit context to 960x528, pix_fmt: yuv420p
[07:09:13.814:INFO] LIBAV: Reinit context to 960x528, pix_fmt: yuv420p
[07:09:13.823:INFO] LIBAV: Statistics: 137773 bytes read, 2 seeks
[07:09:13.841:INFO] LIBAV: Reinit context to 1152x720, pix_fmt: yuv420p
[07:09:13.846:INFO] LIBAV: Reinit context to 1152x720, pix_fmt: yuv420p
[07:09:13.857:INFO] LIBAV: Statistics: 163840 bytes read, 0 seeks
[07:09:13.869:INFO] LIBAV: Statistics: 32768 bytes read, 0 seeks
[07:09:13.879:INFO] LIBAV: Reinit context to 1920x1088, pix_fmt: yuv420p
[07:09:13.888:INFO] LIBAV: Reinit context to 1920x1088, pix_fmt: yuv420p
[07:09:13.910:INFO] LIBAV: Statistics: 130938 bytes read, 2 seeks
[07:09:13.926:INFO] LIBAV: Statistics: 65536 bytes read, 0 seeks
malloc(): corrupted top size
Aborted


   * What outcome did you

Bug#1004613: marked as done (nordlicht: FTBFS with ffmpeg 5.0)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 18:17:47 +
with message-id 
and subject line Bug#1014381: Removed package(s) from unstable
has caused the Debian Bug report #1004613,
regarding nordlicht: FTBFS with ffmpeg 5.0
to be marked as done.

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

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


-- 
1004613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004613
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nordlicht
Version: 0.4.5-2
Severity: important
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs
Usertags: ffmpeg5.0

nordlicht FTBFS with ffmpeg 5.0 (available in experimental):
| /usr/lib/ccache/cc -DNORDLICHT_BUILD_SHARED -Dlibnordlicht_EXPORTS 
-I/<>/obj-x86_64-linux-gnu -I/<> -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-fvisibility=hidden -MD -MT CMakeFiles/libnordlicht.dir/src/source.c.o -MF 
CMakeFiles/libnordlicht.dir/src/source.c.o.d -o 
CMakeFiles/libnordlicht.dir/src/source.c.o -c /<>/src/source.c
| /<>/src/source.c: In function ‘grab_next_frame’:
| /<>/src/source.c:94:25: warning: implicit declaration of 
function ‘avcodec_decode_video2’; did you mean ‘avcodec_decode_subtitle2’? 
[-Wimplicit-function-declaration]
|94 | avcodec_decode_video2(st->codec, st->frame, 
_frame, >packet);
|   | ^
|   | avcodec_decode_subtitle2
| /<>/src/source.c:97:25: warning: implicit declaration of 
function ‘avcodec_decode_audio4’; did you mean ‘avcodec_decode_subtitle2’? 
[-Wimplicit-function-declaration]
|97 | avcodec_decode_audio4(st->codec, st->frame, 
_frame, >packet);
|   | ^
|   | avcodec_decode_subtitle2
| /<>/src/source.c: In function ‘stream_init’:
| /<>/src/source.c:225:47: error: ‘AVStream’ has no member named 
‘codec’
|   225 | st->codec = s->format->streams[st->stream]->codec;
|   |   ^~
| /<>/src/source.c:227:11: warning: assignment discards ‘const’ 
qualifier from pointer target type [-Wdiscarded-qualifiers]
|   227 | codec = avcodec_find_decoder(st->codec->codec_id);
|   |   ^
| /<>/src/source.c: In function ‘source_init’:
| /<>/src/source.c:270:5: warning: implicit declaration of 
function ‘av_register_all’ [-Wimplicit-function-declaration]
|   270 | av_register_all();
|   | ^~~
| make[3]: *** [CMakeFiles/libnordlicht.dir/build.make:121: 
CMakeFiles/libnordlicht.dir/src/source.c.o] Error 1
| make[3]: *** Waiting for unfinished jobs
| /<>/src/image.c: In function ‘image_write_png’:
| /<>/src/image.c:263:24: warning: initialization discards ‘const’ 
qualifier from pointer target type [-Wdiscarded-qualifiers]
|   263 | AVCodec *encoder = avcodec_find_encoder_by_name("png");
|   |^~~~
| /<>/src/image.c:277:5: warning: ‘av_init_packet’ is deprecated 
[-Wdeprecated-declarations]
|   277 | av_init_packet();
|   | ^~
| In file included from /usr/include/x86_64-linux-gnu/libavcodec/avcodec.h:45,
|  from /<>/src/image.h:4,
|  from /<>/src/image.c:1:
| /usr/include/x86_64-linux-gnu/libavcodec/packet.h:506:6: note: declared here
|   506 | void av_init_packet(AVPacket *pkt);
|   |  ^~
| /<>/src/image.c:287:5: warning: implicit declaration of function 
‘avcodec_encode_video2’; did you mean ‘avcodec_encode_subtitle’? 
[-Wimplicit-function-declaration]
|   287 | avcodec_encode_video2(encoder_context, , i->frame, 
_packet);
|   | ^
|   | avcodec_encode_subtitle
| make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 0.4.5-2+rm

Dear submitter,

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

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

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

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

This message was generated automatically; if you believe that

Bug#1013422: marked as done (libgroove FTBFS with ffmpeg 5.0.1)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 18:18:46 +
with message-id 
and subject line Bug#1014384: Removed package(s) from unstable
has caused the Debian Bug report #1013422,
regarding libgroove FTBFS with ffmpeg 5.0.1
to be marked as done.

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

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


-- 
1013422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013422
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgroove
Version: 4.3.0-5
Severity: serious
Tags: ftbfs bookworm sid

https://buildd.debian.org/status/logs.php?pkg=libgroove=4.3.0-5%2Bb1

...
/<>/groove/encoder.c:84:50: error: ‘AVStream’ has no member named 
‘codec’
   84 | int errcode = avcodec_encode_audio2(e->stream->codec, >pkt, 
frame, _packet);
  |  ^~
/<>/groove/encoder.c:84:19: warning: implicit declaration of 
function ‘avcodec_encode_audio2’; did you mean ‘avcodec_encode_subtitle’? 
[-Wimplicit-function-declaration]
   84 | int errcode = avcodec_encode_audio2(e->stream->codec, >pkt, 
frame, _packet);
  |   ^
  |   avcodec_encode_subtitle
/<>/groove/encoder.c:84:50: error: ‘AVStream’ has no member named 
‘codec’
   84 | int errcode = avcodec_encode_audio2(e->stream->codec, >pkt, 
frame, _packet);
  |  ^~
/<>/groove/encoder.c:94:5: warning: implicit declaration of 
function ‘av_free_packet’; did you mean ‘av_get_packet’? 
[-Wimplicit-function-declaration]
   94 | av_free_packet(>pkt);
  | ^~
  | av_get_packet
/<>/groove/encoder.c: In function ‘cleanup_avcontext’:
/<>/groove/encoder.c:101:32: error: ‘AVStream’ has no member named 
‘codec’
  101 | avcodec_close(e->stream->codec);
  |^~
/<>/groove/encoder.c:94:5: warning: implicit declaration of 
function ‘av_free_packet’; did you mean ‘av_get_packet’? 
[-Wimplicit-function-declaration]
   94 | av_free_packet(>pkt);
  | ^~
  | av_get_packet
/<>/groove/encoder.c: In function ‘init_avcontext’:
/<>/groove/encoder.c:134:42: error: ‘AVStream’ has no member named 
‘codec’
  134 | AVCodecContext *codec_ctx = e->stream->codec;
  |  ^~
/<>/groove/encoder.c:148:14: error: ‘AVStream’ has no member named 
‘codec’
  148 | e->stream->codec = codec_ctx;
  |  ^~
/<>/groove/encoder.c: In function ‘cleanup_avcontext’:
/<>/groove/encoder.c:101:32: error: ‘AVStream’ has no member named 
‘codec’
  101 | avcodec_close(e->stream->codec);
  |^~
/<>/groove/encoder.c: In function ‘init_avcontext’:
/<>/groove/encoder.c:134:42: error: ‘AVStream’ has no member named 
‘codec’
  134 | AVCodecContext *codec_ctx = e->stream->codec;
  |  ^~
/<>/groove/encoder.c:148:14: error: ‘AVStream’ has no member named 
‘codec’
  148 | e->stream->codec = codec_ctx;
  |  ^~
/<>/groove/encoder.c: In function ‘groove_encoder_attach’:
/<>/groove/encoder.c:565:16: warning: assignment discards ‘const’ 
qualifier from pointer target type [-Wdiscarded-qualifiers]
  565 | e->oformat = av_guess_format(encoder->format_short_name,
  |^
/<>/groove/encoder.c:579:15: warning: assignment discards ‘const’ 
qualifier from pointer target type [-Wdiscarded-qualifiers]
  579 | codec = avcodec_find_encoder_by_name(encoder->codec_short_name);
  |   ^
/<>/groove/encoder.c:584:23: warning: assignment discards ‘const’ 
qualifier from pointer target type [-Wdiscarded-qualifiers]
  584 | codec = avcodec_find_encoder(desc->id);
  |   ^
/<>/groove/encoder.c:592:15: warning: assignment discards ‘const’ 
qualifier from pointer target type [-Wdiscarded-qualifiers]
  592 | codec = avcodec_find_encoder(codec_id);
  |   ^
/<>/groove/encoder.c: In function ‘groove_encoder_attach’:
/<>/groove/encoder.c:565:16: warning: assignment discards ‘const’ 
qualifier from pointer target type [-Wdiscarded-qualifiers]
  565 | e->oformat = av_guess_format(encoder->format_short_name,
  |^
/<>/groove/encoder.c:620:22: error: ‘AVStream’ has no member named 
‘codec’
  620 | 0 : e->stream->codec->frame_size;
  |  ^~
/<>/groove/encoder.c:579:15: warning: assignment discards ‘const’ 
qualifier from pointer target type [-Wdiscarded-qualifiers]
  579 | codec =

Bug#980023: marked as done (petri-foo: FTBFS with GCC 10)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 18:14:51 +
with message-id 
and subject line Bug#1014144: Removed package(s) from unstable
has caused the Debian Bug report #980023,
regarding petri-foo: FTBFS with GCC 10
to be marked as done.

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

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


-- 
980023: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980023
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: petri-foo
Version: 0.1.87-4
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
X-Debbugs-Cc: lo...@ubuntu.com

Hi,

petri-foo currently FTBFS on rebuild in unstable with GCC 10 as default
because of a variable being defined multiple times.

In Ubuntu, the attached patch was applied to achieve the following:

  * d/p/gcc-10.patch: Fix FTBFS with GCC 10.

Thanks for considering the patch.

Logan
diff -Nru petri-foo-0.1.87/debian/control petri-foo-0.1.87/debian/control
--- petri-foo-0.1.87/debian/control 2018-02-05 11:51:44.0 -0500
+++ petri-foo-0.1.87/debian/control 2021-01-12 22:37:28.0 -0500
@@ -1,8 +1,7 @@
 Source: petri-foo
 Section: sound
 Priority: optional
-Maintainer: Ubuntu Developers 
-XSBC-Original-Maintainer: Debian Multimedia Maintainers 

+Maintainer: Debian Multimedia Maintainers 

 Uploaders:
  Alessio Treglia ,
  Jaromír Mikeš 
diff -Nru petri-foo-0.1.87/debian/patches/gcc-10.patch 
petri-foo-0.1.87/debian/patches/gcc-10.patch
--- petri-foo-0.1.87/debian/patches/gcc-10.patch1969-12-31 
19:00:00.0 -0500
+++ petri-foo-0.1.87/debian/patches/gcc-10.patch2021-01-12 
22:37:27.0 -0500
@@ -0,0 +1,21 @@
+--- a/gui/gui.c
 b/gui/gui.c
+@@ -93,6 +93,8 @@
+ /* current patch, makes passing patch id to sample editor easier */
+ static int cur_patch = -1;
+ 
++GtkRecentManager *recent_manager;
++
+ 
+ GtkWidget* gui_title_new(const char* msg)
+ {
+--- a/gui/gui.h
 b/gui/gui.h
+@@ -107,6 +107,6 @@
+ 
+ void gui_set_session_mode(void);
+ 
+-GtkRecentManager *recent_manager;
++extern GtkRecentManager *recent_manager;
+  
+ #endif /* __GUI_H__ */
diff -Nru petri-foo-0.1.87/debian/patches/series 
petri-foo-0.1.87/debian/patches/series
--- petri-foo-0.1.87/debian/patches/series  2016-12-23 10:09:46.0 
-0500
+++ petri-foo-0.1.87/debian/patches/series  2021-01-12 22:36:12.0 
-0500
@@ -1,2 +1,3 @@
 0003-desktop_file_fix.patch
 0005-spelling.patch
+gcc-10.patch
--- End Message ---
--- Begin Message ---
Version: 0.1.87-4+rm

Dear submitter,

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

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

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

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

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#965563: marked as done (gnome-phone-manager: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 18:14:22 +
with message-id 
and subject line Bug#1014063: Removed package(s) from unstable
has caused the Debian Bug report #965563,
regarding gnome-phone-manager: Removal of obsolete debhelper compat 5 and 6 in 
bookworm
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.)


-- 
965563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965563
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-phone-manager
Version: 0.69-2.1
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package gnome-phone-manager uses debhelper with a compat level of 5 or 6,
which is deprecated and scheduled for removal[1].

Please bump the debhelper compat at your earliest convenience
/outside the freeze/!

  * Compat 13 is recommended (supported in stable-backports)

  * Compat 7 is the bare minimum


PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads
with compat bumps during the freeze.

If there is any risk that the fix for this bug might not migrate to
testing before 2021-01-01[3] then please postpone the fix until after
the freeze.


At the time of filing this bug, compat 5 and 6 are expected to be
removed "some time during the development cycle of bookworm".


Thanks,
~Niels


[1] https://lists.debian.org/debian-devel/2020/07/msg00065.html

[2] https://release.debian.org/bullseye/FAQ.html

[3] The choice of 2021-01-01 as a "deadline" is set before the actual
freeze deadline to provide a safe cut off point for most people.

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Version: 0.69-2.1+rm

Dear submitter,

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

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

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

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

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#1013813: marked as done (RM: uwsgi-plugin-luajit [ppc64el] -- RoQA; luajit2 segfaults)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 18:12:24 +
with message-id 
and subject line Bug#1013813: Removed package(s) from unstable
has caused the Debian Bug report #1013813,
regarding RM: uwsgi-plugin-luajit [ppc64el] -- RoQA; luajit2 segfaults
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.)


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

Package: nginx
Version: 1.20.2-2
Severity: serious
X-Debbugs-CC: 1004...@bugs.debian.org, lu...@debian.org
Control: reopen 1004511
Control: block 1004511 by -1
Control: block 1012362 by 1004511
Control: clone -1 -2 -3 -4 -5 -6 -7 -8
Control: reassign -2 src:aegisub 3.2.2+dfsg-6
Control: reassign -3 src:ettercap 1:0.8.3.1-9
Control: reassign -4 src:knot-resolver 5.5.1-1
Control: reassign -5 src:snort 2.9.15.1-6
Control: reassign -6 src:trafficserver  9.1.2+ds-10
Control: reassign -7 src:uwsgi-plugin-luajit 0.0.7
Control: reassign -8 src:luakit 1:2.3-1

Dear maintainers,

We have been working for a while to get a working libluajit on ppc64el 
(for reference, see history in bug #1012362). In the end we concluded 
that it's not going to work as commitment upstream is lacking to support 
ppc64el.


Your source package build depends on libluajit-5.1-dev when building on 
ppc64el and at least one of its binaries depends on libluajit-5.1-2 on 
that architecture. Please use liblua on ppc64el if that works for your 
package, otherwise please request removal of the binaries on ppc64el 
(e.g. by reassigning the bug to ftp.debian.org, lowering severity and 
re-titling appropriately).


Sorry we couldn't solve the problem in a better way.

Paul



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

uwsgi-plugin-luajit | 2.0.20+4+0.0.7+b1 | ppc64el

--- Reason ---
RoQA; luajit2 segfaults
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

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

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1013...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1013813

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#1013811: marked as done (RM: snort [ppc64el] -- RoQA; luajit2 segfaults)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 18:12:08 +
with message-id 
and subject line Bug#1013811: Removed package(s) from unstable
has caused the Debian Bug report #1013811,
regarding RM: snort [ppc64el] -- RoQA; luajit2 segfaults
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.)


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

Package: nginx
Version: 1.20.2-2
Severity: serious
X-Debbugs-CC: 1004...@bugs.debian.org, lu...@debian.org
Control: reopen 1004511
Control: block 1004511 by -1
Control: block 1012362 by 1004511
Control: clone -1 -2 -3 -4 -5 -6 -7 -8
Control: reassign -2 src:aegisub 3.2.2+dfsg-6
Control: reassign -3 src:ettercap 1:0.8.3.1-9
Control: reassign -4 src:knot-resolver 5.5.1-1
Control: reassign -5 src:snort 2.9.15.1-6
Control: reassign -6 src:trafficserver  9.1.2+ds-10
Control: reassign -7 src:uwsgi-plugin-luajit 0.0.7
Control: reassign -8 src:luakit 1:2.3-1

Dear maintainers,

We have been working for a while to get a working libluajit on ppc64el 
(for reference, see history in bug #1012362). In the end we concluded 
that it's not going to work as commitment upstream is lacking to support 
ppc64el.


Your source package build depends on libluajit-5.1-dev when building on 
ppc64el and at least one of its binaries depends on libluajit-5.1-2 on 
that architecture. Please use liblua on ppc64el if that works for your 
package, otherwise please request removal of the binaries on ppc64el 
(e.g. by reassigning the bug to ftp.debian.org, lowering severity and 
re-titling appropriately).


Sorry we couldn't solve the problem in a better way.

Paul



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

 snort | 2.9.15.1-6+b2 | ppc64el
snort-common-libraries | 2.9.15.1-6+b2 | ppc64el

--- Reason ---
RoQA; luajit2 segfaults
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

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

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1013...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1013811

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#1013808: marked as done (RM: aegisub [ppc64el] -- RoQA; luajit2 segfaults)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 18:11:45 +
with message-id 
and subject line Bug#1013808: Removed package(s) from unstable
has caused the Debian Bug report #1013808,
regarding RM: aegisub [ppc64el] -- RoQA; luajit2 segfaults
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.)


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

Package: nginx
Version: 1.20.2-2
Severity: serious
X-Debbugs-CC: 1004...@bugs.debian.org, lu...@debian.org
Control: reopen 1004511
Control: block 1004511 by -1
Control: block 1012362 by 1004511
Control: clone -1 -2 -3 -4 -5 -6 -7 -8
Control: reassign -2 src:aegisub 3.2.2+dfsg-6
Control: reassign -3 src:ettercap 1:0.8.3.1-9
Control: reassign -4 src:knot-resolver 5.5.1-1
Control: reassign -5 src:snort 2.9.15.1-6
Control: reassign -6 src:trafficserver  9.1.2+ds-10
Control: reassign -7 src:uwsgi-plugin-luajit 0.0.7
Control: reassign -8 src:luakit 1:2.3-1

Dear maintainers,

We have been working for a while to get a working libluajit on ppc64el 
(for reference, see history in bug #1012362). In the end we concluded 
that it's not going to work as commitment upstream is lacking to support 
ppc64el.


Your source package build depends on libluajit-5.1-dev when building on 
ppc64el and at least one of its binaries depends on libluajit-5.1-2 on 
that architecture. Please use liblua on ppc64el if that works for your 
package, otherwise please request removal of the binaries on ppc64el 
(e.g. by reassigning the bug to ftp.debian.org, lowering severity and 
re-titling appropriately).


Sorry we couldn't solve the problem in a better way.

Paul



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

   aegisub | 3.2.2+dfsg-6+b1 | ppc64el

--- Reason ---
RoQA; luajit2 segfaults
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

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

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1013...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1013808

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#1004809: marked as done (deepin-voice-recorder: FTBFS with ffmpeg 5.0)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 18:08:59 +
with message-id 
and subject line Bug#1013450: Removed package(s) from unstable
has caused the Debian Bug report #1004809,
regarding deepin-voice-recorder: FTBFS with ffmpeg 5.0
to be marked as done.

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

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


-- 
1004809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004809
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: deepin-voice-recorder
Version: 5.0.0-3
Severity: important
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs
Usertags: ffmpeg5.0

deeping-voice-recorder FTBFS with ffmpeg 5.0 in experimental:

g++ -c -pipe -g -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=gnu++11 -Wall -Wextra -D_REENTRANT -fPIC 
-DVERSION=5.0.0 
-DDSR_LANG_PATH=\"/usr/share/deepin-voice-recorder/translations\" -DQT_NO_DEBUG 
-DQT_WIDGETS_LIB -DQT_MULTIMEDIA_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB 
-DQT_CORE_LIB -I. -I. -I/usr/include/libdtk-5.5.17/DWidget 
-I/usr/include/libdtk-5.5.17/DGui -I/usr/include/libdtk-5.5.17/DCore 
-I/usr/include/x86_64-linux-gnu -I/usr/include/x86_64-linux-gnu/qt5 
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
-I/usr/include/x86_64-linux-gnu/qt5/QtMultimedia 
-I/usr/include/x86_64-linux-gnu/qt5/QtGui 
-I/usr/include/x86_64-linux-gnu/qt5/QtNetwork 
-I/usr/include/x86_64-linux-gnu/qt5/QtCore -I. 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o 
moc_expand_animation_button.o moc_expand_animation_button.cpp
In file included from src/file_item.cpp:41:
src/file_item.h:76:19: warning: ‘DImageButton’ is deprecated: Use DIconButton 
[-Wdeprecated-declarations]
   76 | DImageButton *pausePlayButton;
  |   ^~~
In file included from src/file_item.h:33,
 from src/file_item.cpp:41:
/usr/include/libdtk-5.5.17/DWidget/dimagebutton.h:31:72: note: declared here
   31 | class LIBDTKWIDGETSHARED_EXPORT D_DECL_DEPRECATED_X("Use DIconButton") 
DImageButton : public QLabel, public DTK_CORE_NAMESPACE::DObject
  |
^~~~
In file included from src/file_item.cpp:41:
src/file_item.h:77:19: warning: ‘DImageButton’ is deprecated: Use DIconButton 
[-Wdeprecated-declarations]
   77 | DImageButton *pauseStopButton;
  |   ^~~
In file included from src/file_item.h:33,
 from src/file_item.cpp:41:
/usr/include/libdtk-5.5.17/DWidget/dimagebutton.h:31:72: note: declared here
   31 | class LIBDTKWIDGETSHARED_EXPORT D_DECL_DEPRECATED_X("Use DIconButton") 
DImageButton : public QLabel, public DTK_CORE_NAMESPACE::DObject
  |
^~~~
In file included from src/file_item.cpp:41:
src/file_item.h:78:19: warning: ‘DImageButton’ is deprecated: Use DIconButton 
[-Wdeprecated-declarations]
   78 | DImageButton *playPauseButton;
  |   ^~~
In file included from src/file_item.h:33,
 from src/file_item.cpp:41:
/usr/include/libdtk-5.5.17/DWidget/dimagebutton.h:31:72: note: declared here
   31 | class LIBDTKWIDGETSHARED_EXPORT D_DECL_DEPRECATED_X("Use DIconButton") 
DImageButton : public QLabel, public DTK_CORE_NAMESPACE::DObject
  |
^~~~
In file included from src/file_item.cpp:41:
src/file_item.h:79:19: warning: ‘DImageButton’ is deprecated: Use DIconButton 
[-Wdeprecated-declarations]
   79 | DImageButton *playStartButton;
  |   ^~~
In file included from src/file_item.h:33,
 from src/file_item.cpp:41:
/usr/include/libdtk-5.5.17/DWidget/dimagebutton.h:31:72: note: declared here
   31 | class LIBDTKWIDGETSHARED_EXPORT D_DECL_DEPRECATED_X("Use DIconButton") 
DImageButton : public QLabel, public DTK_CORE_NAMESPACE::DObject
  |
^~~~
In file included from src/file_item.cpp:41:
src/file_item.h:80:19: warning: ‘DImageButton’ is deprecated: Use DIconButton 
[-Wdeprecated-declarations]
   80 | DImageButton *playStopButton;
  |   ^~
In file included from src/file_item.h:33,
 from src/file_item.cpp:41:
/usr/include/libdtk-5.5.17/DWidget/dimagebutton.h:31:72: note: declared here
   31 | class LIBDTKWIDGETSHARED_EXPORT D_DECL_DEPRECATED_X("Use DIconButton") 
DImageButton : public QLabel, public

Bug#1015038: marked as done (node-browserslist: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 18:06:40 +
with message-id 
and subject line Bug#1015038: fixed in node-browserslist 4.21.2+~cs6.1.11-1
has caused the Debian Bug report #1015038,
regarding node-browserslist: FTBFS: dh_auto_test: error: /bin/sh -ex 
debian/tests/pkg-js/test returned exit code 1
to be marked as done.

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

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


-- 
1015038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015038
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-browserslist
Version: 4.21.1+~cs6.1.10-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220716 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 --buildsystem=nodejs
> No build command found, searching known files
> No build command found, searching known files
> help2man -N -n 'The config to share target browsers and Node.js versions' 
> ./cli.js >browserslist.1
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
>   ln -s ../debian/tests/test_modules/browserslist-config-test 
> node_modules/browserslist-config-test
>   ln -s ../debian/tests/test_modules/nanospy node_modules/nanospy
>   ln -s ../. node_modules/browserslist
>   /bin/sh -ex debian/tests/pkg-js/test
> + NODE_ENV=test uvu test .test.js
> [1m[4m[37mand.test.js[22m[24m[39m
> [90m• [39m[90m• [39m[90m• [39m[32m  (3 / 3)
> [39m
> [1m[4m[37mbrowser.test.js[22m[24m[39m
> [90m• [39m[90m• [39m[90m• [39m[90m• [39m[90m• [39m[32m  (5 / 5)
> [39m
> [1m[4m[37mcache.test.js[22m[24m[39m
> [90m• [39m[90m• [39m[32m  (2 / 2)
> [39m
> [1m[4m[37mcli.test.js[22m[24m[39m
> [90m• [39m[90m• [39m[90m• [39m[90m• [39m[90m• [39m[90m• 
> [39m[90m• [39m[90m• [39m[90m• [39m[90m• [39m[90m• [39m[90m• 
> [39m[90m• [39m[90m• [39m[90m• [39m[90m• [39m[90m• [39m[90m• 
> [39m[90m• [39m[32m  (19 / 19)
> [39m
> [1m[4m[37mconfig-query.test.js[22m[24m[39m
> [90m• [39m[32m  (1 / 1)
> [39m
> [1m[4m[37mconfig.test.js[22m[24m[39m
> [90m• [39m[90m• [39m[90m• [39m[90m• [39m[90m• [39m[90m• 
> [39m[90m• [39m[90m• [39m[90m• [39m[90m• [39m[90m• [39m[90m• 
> [39m[90m• [39m[90m• [39m[90m• [39m[90m• [39m[90m• [39m[32m  (17 / 
> 17)
> [39m
> [1m[4m[37mcountry.test.js[22m[24m[39m
> [90m• [39m[90m• [39m[90m• [39m[90m• [39m[90m• [39m[90m• 
> [39m[90m• [39m[90m• [39m[90m• [39m[90m• [39m[90m• [39m[32m  (11 / 
> 11)
> [39m
> [1m[4m[37mcover.test.js[22m[24m[39m
> [90m• [39m[90m• [39m[90m• [39m[90m• [39m[90m• [39m[90m• 
> [39m[90m• [39m[90m• [39m[90m• [39m[90m• [39m[32m  (10 / 10)
> [39m
> [1m[4m[37mcoverage.test.js[22m[24m[39m
> [90m• [39m[90m• [39m[90m• [39m[90m• [39m[90m• [39m[90m• 
> [39m[90m• [39m[90m• [39m[90m• [39m[90m• [39m[90m• [39m[90m• 
> [39m[90m• [39m[32m  (13 / 13)
> [39m
> [1m[4m[37mcustom.test.js[22m[24m[39m
> [90m• [39m[90m• [39m[90m• [39m[90m• [39m[90m• [39m[90m• 
> [39m[90m• [39m[90m• [39m[90m• [39m[90m• [39m[90m• [39m[90m• 
> [39m[32m  (12 / 12)
> [39m
> [1m[4m[37mdead.test.js[22m[24m[39m
> [90m• [39m[90m• [39m[32m  (2 / 2)
> [39m
> [1m[4m[37mdefaults.test.js[22m[24m[39m
> [90m• [39m[90m• [39m[90m• [39m[32m  (3 / 3)
> [39m
> [1m[4m[37mdirect.test.js[22m[24m[39m
> [90m• [39m[90m• [39m[90m• [39m[90m• [39m[90m• [39m[90m• 
> [39m[90m• [39m[90m• [39m[90m• [39m[90m• [39m[90m• [39m[90m• 
> [39m[90m• [39m[32m  (13 / 13)
> [39m
> [1m[4m[37melectron.test.js[22m[24m[39m
> [90m• [39m[90m• [39m[90m• [39m[90m• [39m[90m• [39m[90m• 
> [39m[90m• [39m[90m• [39m[90m• [39m[90m• [39m[90m• [39m[90m• 
> [39m[90m• [39m[90m• [39m[32m  (14 / 14)
> [39m
> [1m[4m[37merror.test.js[22m[24m[39m
> [90m• [39m[90m• [39m[32m  (2 / 2)
> [39m
> [1m[4m[37mesr.test.js[22m[24m[39m
> [90m• [39m[90m• [39m[32m  (2 / 2)
> [39m
> [1m[4m[37mextends.test.js[22m[24m[39m
> [90m• [39m[31m✘ [39m[90m• [39m[90m• [39m[90m• [39m[90m• 
> [39m[90m• [39m[90m• [39m[90m• [

Bug#1015118: marked as done (node-configurable-http-proxy: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 18:06:46 +
with message-id 
and subject line Bug#1015118: fixed in node-configurable-http-proxy 
4.5.0+~cs15.1.4-5
has caused the Debian Bug report #1015118,
regarding node-configurable-http-proxy: FTBFS: dh_auto_test: error: /bin/sh -ex 
debian/tests/pkg-js/test returned exit code 1
to be marked as done.

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

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


-- 
1015118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015118
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-configurable-http-proxy
Version: 4.5.0+~cs15.1.4-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220716 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 --buildsystem=nodejs
> Found debian/nodejs/prom-client/build
>   cd ./prom-client && sh -ex ../debian/nodejs/prom-client/build
> + tsc -p .
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
> help2man -n 'configurable-on-the-fly HTTP Proxy in Node.js' -N 
> ./bin/configurable-http-proxy > configurable-http-proxy.1
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
>   ln -s ../debian/tests/test_modules/better-assert 
> node_modules/better-assert
>   ln -s ../debian/tests/test_modules/callsite node_modules/callsite
>   ln -s ../debian/tests/test_modules/request node_modules/request
>   ln -s ../debian/tests/test_modules/request-promise-core 
> node_modules/request-promise-core
>   ln -s ../debian/tests/test_modules/request-promise-native 
> node_modules/request-promise-native
>   ln -s ../. node_modules/configurable-http-proxy
>   cd ./bintrees && sh -ex ../debian/nodejs/bintrees/test
> + nodeunit ./test/test_api.js ./test/test_correctness.js
> 
> [1mtest_api.js[22m
> ✔ api - rbtree_clear
> ✔ api - rbtree_dup
> ✔ api - rbtree_nonexist
> ✔ api - rbtree_minmax
> ✔ api - rbtree_forward_it
> ✔ api - rbtree_forward_it_break
> ✔ api - rbtree_reverse_it
> ✔ api - rbtree_reverse_it_break
> ✔ api - rbtree_switch_it
> ✔ api - rbtree_empty_it
> ✔ api - rbtree_lower_bound
> ✔ api - rbtree_upper_bound
> ✔ api - rbtree_find
> ✔ api - rbtree_find_iter
> ✔ api - bintree_clear
> ✔ api - bintree_dup
> ✔ api - bintree_nonexist
> ✔ api - bintree_minmax
> ✔ api - bintree_forward_it
> ✔ api - bintree_forward_it_break
> ✔ api - bintree_reverse_it
> ✔ api - bintree_reverse_it_break
> ✔ api - bintree_switch_it
> ✔ api - bintree_empty_it
> ✔ api - bintree_lower_bound
> ✔ api - bintree_upper_bound
> ✔ api - bintree_find
> ✔ api - bintree_find_iter
> 
> [1mtest_correctness.js[22m
> ✔ correctness - rbtree_10k
> ✔ correctness - bintree_10k
> 
> [1m[32mOK: [39m[22m56 assertions (5248ms)
>   cd ./prom-client && sh -ex ../debian/nodejs/prom-client/test
> + jest --ci
> PASS test/clusterTest.js
> PASS test/pushgatewayWithPathTest.js
> PASS test/counterTest.js
> PASS test/gaugeTest.js
> PASS test/histogramTest.js
> PASS test/summaryTest.js
> PASS test/registerTest.js
> PASS test/metrics/eventLoopLagTest.js
> PASS test/metrics/heapSpacesSizeAndUsedTest.js
> PASS test/aggregatorsTest.js
> PASS test/timeWindowQuantilesTest.js
> PASS test/defaultMetricsTest.js
> PASS test/bucketGeneratorsTest.js
> PASS test/metrics/maxFileDescriptorsTest.js
> /<>/prom-client/test/metrics/eventLoopLagTest.js:19
>   expect(metrics).toHaveLength(8);
>   ^
> 
> JestAssertionError: expect(received).toHaveLength(expected)
> 
> Expected length: 8
> Received length: 0
> Received array:  []
> at Timeout._onTimeout 
> (/<>/prom-client/test/metrics/eventLoopLagTest.js:19:23) {
>   matcherResult: {
> message: 'expect(received).toHaveLength(expected)\n' +
>   '\n' +
>   'Expected length: 8\n' +
>   'Received length: 0\n' +
>   'Received array:  []',
> pass: false
>   }
> }
> PASS test/metrics/heapSizeAndUsedTest.js
> PASS test/metrics/versionTest.js
> PASS test/metrics/processRequestsTest.js
> PASS test/metrics/gcTest.js
> PASS test/metrics/processHandlesTest.js
>

Bug#1008526: marked as done (gnome-documents: deprecated and unmaintained upstream)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 18:07:25 +
with message-id 
and subject line Bug#1010319: Removed package(s) from unstable
has caused the Debian Bug report #1008526,
regarding gnome-documents: deprecated and unmaintained upstream
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.)


-- 
1008526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-documents
Severity: serious
Tags: wontfix
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs

gnome-documents is no longer maintained upstream. It has been archived
which means GNOME is no longer accepting any code fixes, translations,
or even bug reports for it any more.

https://gitlab.gnome.org/Archive/gnome-documents

Its most recent release was in October of 2019.

I propose that we remove gnome-documents from Debian soon.

It is recommended by task-gnome-flashback-desktop so we'll need to
drop that recommendation.

Until this week, it was installed by default by meta-gnome3 so its
popcorn is still very high.

Thank you,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 3.34.0-4+rm

Dear submitter,

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

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

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

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

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#1005549: marked as done (gnome-documents: FTBFS: ../data/meson.build:58:2: ERROR: Function does not take positional arguments.)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 18:07:25 +
with message-id 
and subject line Bug#1010319: Removed package(s) from unstable
has caused the Debian Bug report #1005549,
regarding gnome-documents: FTBFS: ../data/meson.build:58:2: ERROR: Function 
does not take positional arguments.
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.)


-- 
1005549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005549
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-documents
Version: 3.34.0-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 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_configure -- \
>   -Dgetting_started=true
>   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 -Dgetting_started=true
> The Meson build system
> Version: 0.61.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: gnome-documents
> Project version: 3.34.0
> C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16) 
> 11.2.0")
> C linker for the host machine: cc 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 gjs-1.0 found: YES 1.70.1
> Run-time dependency evince-document-3.0 found: YES 41.3
> Run-time dependency evince-view-3.0 found: YES 41.3
> Run-time dependency glib-2.0 found: YES 2.70.3
> Run-time dependency gnome-desktop-3.0 found: YES 41.3
> Run-time dependency gobject-introspection-1.0 found: YES 1.70.0
> Run-time dependency gtk+-3.0 found: YES 3.24.31
> Run-time dependency libsoup-2.4 found: YES 2.74.2
> Run-time dependency tracker-sparql-3.0 found: YES 3.1.2
> Run-time dependency webkit2gtk-4.0 found: YES 2.34.5
> Library m found: YES
> Run-time dependency libgdata found: YES 0.18.1
> Run-time dependency goa-1.0 found: YES 3.40.1
> Run-time dependency zapojit-0.0 found: YES 0.0.3
> Checking for function "cairo_surface_set_device_scale" with dependencies 
> gjs-1.0, evince-document-3.0, evince-view-3.0, glib-2.0, gnome-desktop-3.0, 
> gobject-introspection-1.0, gtk+-3.0, libsoup-2.4, tracker-sparql-3.0, 
> webkit2gtk-4.0, -lm: YES 
> 
> Executing subproject libgd 
> 
> libgd| Project name: libgd
> libgd| Project version: undefined
> libgd| C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16) 
> 11.2.0")
> libgd| C linker for the host machine: cc ld.bfd 2.38
> libgd| Dependency gtk+-3.0 found: YES 3.24.31 (cached)
> libgd| Library m found: YES
> libgd| Dependency gobject-introspection-1.0 found: YES 1.70.0 (cached)
> libgd| Dependency gobject-introspection-1.0 found: YES 1.70.0 (cached)
> libgd| Program g-ir-scanner found: YES (/usr/bin/g-ir-scanner)
> libgd| Dependency gobject-introspection-1.0 found: YES 1.70.0 (cached)
> libgd| Program g-ir-compiler found: YES (/usr/bin/g-ir-compiler)
> libgd| Build targets in project: 5
> libgd| Subproject libgd finished.
> 
> Configuring config.h using configuration
> Program itstool found: YES (/usr/bin/itstool)
> Program msgmerge found: YES (/usr/bin/msgmerge)
> Program msgfmt found: YES (/usr/bin/msgfmt)
> Configuring org.gnome.Documents.service using configuration
> Configuring org.gnome.Documents using configuration
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Program glib-compile-resources found: YES (/usr/bin/glib-compile-resources)
> Program glib-mkenums found: YES (/usr/bin/glib-mkenums)
> Program desktop-file-validate found: YES (/usr/bin/desktop-file-validate)
> Program appstream-util found: NO
> Program glib-compile-resources found: YES (/usr/bin/glib-compile-resources)
> 
> ../data/meson.build:58:2: ERROR: Function does not take positional arguments.
> 
> A full log can be found at 
> /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt
>   cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt
> ==> meson-logs/meson-log.txt <==
> Build started at 2022-02-12T22:44:33.874023
> Main binary: /usr/bin/python3
> Build Options: -Dgetting_started=true -Dprefix=/usr 
> -Dlibdir=lib/x86_64-linux-gnu -Dlocalstatedir=/var -Dsysconfdir=/etc 
> -Dbuildtype=plain -Dwrap_mode=nodownload
> Python system: Linux
> The Meson build system
> Version: 0.61.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name:

Bug#1013420: corsix-th FTBFS with ffmpeg 5.0.1

2022-07-16 Thread Alexandre Detiste

Hi,

I imported and packaged corsix-th 0.66.

This fix this one build time bug but not the run-time one.

>Welcome to CorsixTH v0.66!
>
>An error has occurred in CorsixTH:
>/usr/share/games/corsix-th/Lua/strict.lua:66: module 'lpeg' not found:
>no field package.preload['lpeg']
>no file './lpeg.lua'
>no file './lpeg/init.lua'
>[C]: in ?
>/usr/share/games/corsix-th/Lua/audio.lua:662: attempt to index a nil >value 
>(field 'ui')

Greetings

Alexandre Detiste

Processed: Bug#1015118 marked as pending in node-configurable-http-proxy

2022-07-16 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 pending
Bug #1015118 [src:node-configurable-http-proxy] node-configurable-http-proxy: 
FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit 
code 1
Added tag(s) pending.

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

Bug#1015118: marked as pending in node-configurable-http-proxy

2022-07-16 Thread Yadd

Control: tag -1 pending

Hello,

Bug #1015118 in node-configurable-http-proxy 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/js-team/node-configurable-http-proxy/-/commit/9cbdadd3e4c3b2a2b6f6d18e3d1c30f9b31eba07


Add test dependency to node-stealthy-require

Closes: #1015118


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1015118

Bug#1014952: marked as done (libgnunetgtk3: missing Breaks+Replaces: gnunet-gtk (<< 0.16.0-4))

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 17:49:08 +
with message-id 
and subject line Bug#1014952: fixed in gnunet-gtk 0.16.0-6
has caused the Debian Bug report #1014952,
regarding libgnunetgtk3: missing Breaks+Replaces: gnunet-gtk (<< 0.16.0-4)
to be marked as done.

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

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


-- 
1014952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014952
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgnunetgtk3
Version: 0.16.0-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../libgnunetgtk3_0.16.0-4_amd64.deb ...
  Unpacking libgnunetgtk3 (0.16.0-4) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libgnunetgtk3_0.16.0-4_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libgnunetgtk.so.3.0.0', which 
is also in package gnunet-gtk 0.16.0-2
  Errors were encountered while processing:
   /var/cache/apt/archives/libgnunetgtk3_0.16.0-4_amd64.deb


cheers,

Andreas


gnunet-gtk=0.16.0-2_libgnunetgtk3=0.16.0-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gnunet-gtk
Source-Version: 0.16.0-6
Done: Daniel Baumann 

We believe that the bug you reported is fixed in the latest version of
gnunet-gtk, 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.
Daniel Baumann  (supplier of updated 
gnunet-gtk 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: Sat, 16 Jul 2022 18:01:32 +0200
Source: gnunet-gtk
Architecture: source
Version: 0.16.0-6
Distribution: sid
Urgency: medium
Maintainer: Daniel Baumann 
Changed-By: Daniel Baumann 
Closes: 1014952
Changes:
 gnunet-gtk (0.16.0-6) sid; urgency=medium
 .
   * Uploading to sid.
   * Updating http links to https in copyright.
   * Correcting breaks/replaces for gnunet-gtk/gnunet-gtk-dev (Closes:
 #1014952).
Checksums-Sha1:
 08b3ac68cd413a33c7085cf8e3a2df7ecca22e31 2250 gnunet-gtk_0.16.0-6.dsc
 c37ff7b665efa01ec86f0d138df350249482d519 38280 
gnunet-gtk_0.16.0-6.debian.tar.xz
 1c982a38d1b6e7adf7824efb59ae11722605d52b 18601 
gnunet-gtk_0.16.0-6_amd64.buildinfo
Checksums-Sha256:
 2a402829fb2ce93cd9985ea0ac7a8fd8282bd330b359ba88e190fbbb99aa265d 2250 
gnunet-gtk_0.16.0-6.dsc
 78ec34a593f00d4ed047cd8cee3b20cb4436aa6064b51470c5249dd1e3819e3c 38280 
gnunet-gtk_0.16.0-6.debian.tar.xz
 5045c4fef290b0223d06e038b535d69d7176cc10b1954ce2bc3d0a41f566a9a3 18601 
gnunet-gtk_0.16.0-6_amd64.buildinfo
Files:
 66d11dab1d36674e1d236a9a9d32b9f9 2250 net optional gnunet-gtk_0.16.0-6.dsc
 8d58cce77dfc3f1a968e8597641a80be 38280 net optional 
gnunet-gtk_0.16.0-6.debian.tar.xz
 06b3a578d34010979c82cd87ed054b8f 18601 net optional 
gnunet-gtk_0.16.0-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAmLS98UACgkQVc8b+Yar
uceJag//Wa9WTp7+PEpgifMEyrfVI1AHJLUDL38mH64QyHqZODtmNRQuuZ8Yc/AO
gel0Atw1rvXrH8mtlKNl6oPcJ91D8uR0OFdm3f+x1wgI//CMBdvLP/QtqPJjy5wW
MDzA9R6fahF+oIxCF1Cr+ETmFCF1skq9Q8x4qikCwBQzlB3CzK6RAgVM1X31oGjx
DKpRqhjPb5EgRuU3YQsu9AnXFZuhgkmWHXjXm+FvnF0PGF5UzHxYaNUkTOE031NY
fBJsTWCy6ppji9qybLbAeT5AKvlY2uGtbSGUOGK78wG9hXqWt0+jlHly1dqKR9iJ
k9VL0Mf8ryPjJHYQWYviHkC0QcAjaOTxOQdISQpVxt30DZ2Do7C6rc82jYfRbKzt
cUFiKo8Y0LIn9RNbJ7eYZw8STaaIPsGt3Utyu8a/Wh/CXVKYwzuDfyvrJSpctLwM
DuNnhL8bSucESKca3r1jJFBjumyZa4GXJFd82ggj1gHPN85KYw5wqO+xU/MvcG22
r1BzF6tiLjvukIVsvH9Y5UJSdOZUIofWp5fb+jFHkzpoxa9CRHM7jFepe4rvtItL
wxHhzJM9M/giaWETovANn9u7Qp+93QFL9A68GUnndeWQJm17aAKL7dljFipiMKg4
XLN5MYtbTBX6s45Cu8lX/5goaYe8cZ7BK+A0K6GwoDpWucQfZSg=
=pJi7
-END PGP SIGNATURE End Message ---

Bug#1015064: marked as done (cataclysm-dda: FTBFS: src/sdl_font.cpp:25:44: error: invalid conversion from ‘const char’ to ‘char’ [-fpermissive])

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 17:34:10 +
with message-id 
and subject line Bug#1015064: fixed in cataclysm-dda 0.F-3-5
has caused the Debian Bug report #1015064,
regarding cataclysm-dda: FTBFS: src/sdl_font.cpp:25:44: error: invalid 
conversion from ‘const char*’ to ‘char*’ [-fpermissive]
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.)


-- 
1015064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015064
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cataclysm-dda
Version: 0.F-3-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220716 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> g++ -Wdate-time -D_FORTIFY_SOURCE=2 -DRELEASE -DTILES -DBACKTRACE -DLOCALIZE 
> -DPREFIX="/usr" -DDATA_DIR_PREFIX -DUSE_XDG_DIR -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -ffast-math -Os -flto=jobserver 
> -flto-odr-type-merging -Wodr -Werror -Wall -Wextra -Wformat-signedness 
> -Wlogical-op -Wmissing-declarations -Wmissing-noreturn -Wnon-virtual-dtor 
> -Wold-style-cast -Woverloaded-virtual -Wpedantic -Wsuggest-override 
> -Wunused-macros -Wzero-as-null-pointer-constant -Wno-unknown-warning-option 
> -Wredundant-decls -g -fsigned-char -std=c++14 -MMD -MP -D_REENTRANT -pthread 
> -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -D_REENTRANT -I/usr/include/SDL2 
> -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
> -I/usr/include/libinstpatch-2 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/opus 
> -I/usr/include/SDL2 -DSDL_SOUND -D_REENTRANT -I/usr/include/SDL2 
> -I/usr/include/x86_64-linux-gnu -I/usr/include/SDL2 -I/usr/include/harfbuzz 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/SDL2  -c 
> src/sdl_utils.cpp -o obj/tiles/sdl_utils.o
> src/sdl_font.cpp: In function ‘int test_face_size(const string&, int, int)’:
> src/sdl_font.cpp:25:44: error: invalid conversion from ‘const char*’ to 
> ‘char*’ [-fpermissive]
>25 | char *style = TTF_FontFaceStyleName( fnt.get() );
>   |   ~^
>   ||
>   |const char*
> src/sdl_font.cpp:32:64: error: invalid conversion from ‘const char*’ to 
> ‘char*’ [-fpermissive]
>32 | if( nullptr != ( ts = TTF_FontFaceStyleName( 
> tf.get() ) ) ) {
>   |   
> ~^~~~
>   ||
>   |const 
> char*
> g++ -Wdate-time -D_FORTIFY_SOURCE=2 -DRELEASE -DTILES -DBACKTRACE -DLOCALIZE 
> -DPREFIX="/usr" -DDATA_DIR_PREFIX -DUSE_XDG_DIR -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -ffast-math -Os -flto=jobserver 
> -flto-odr-type-merging -Wodr -Werror -Wall -Wextra -Wformat-signedness 
> -Wlogical-op -Wmissing-declarations -Wmissing-noreturn -Wnon-virtual-dtor 
> -Wold-style-cast -Woverloaded-virtual -Wpedantic -Wsuggest-override 
> -Wunused-macros -Wzero-as-null-pointer-constant -Wno-unknown-warning-option 
> -Wredundant-decls -g -fsigned-char -std=c++14 -MMD -MP -D_REENTRANT -pthread 
> -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -D_REENTRANT -I/usr/include/SDL2 
> -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
> -I/usr/include/libinstpatch-2 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/opus 
> -I/usr/include/SDL2 -DSDL_SOUND -D_REENTRANT -I/usr/include/SDL2 
> -I/usr/include/x86_64-linux-gnu -I/usr/include/SDL2 -I/usr/include/harfbuzz 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/SDL2  -c 
> src/sdl_wrappers.cpp -o obj/tiles/sdl_wrappers.o
> g++ -Wdate-time -D_FORTIFY_SOURCE=2 -DRELEASE -DTILES -DBACKTRACE -DLOCALIZE 
> -DPREFIX="/usr" -DDATA_DIR_PREFIX -DUSE_XDG_DIR -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werro

Bug#1013985: marked as done (FTBFS: attempt to build with Go module)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 17:34:17 +
with message-id 
and subject line Bug#1013985: fixed in golang-github-evanw-esbuild 0.14.43-2
has caused the Debian Bug report #1013985,
regarding FTBFS: attempt to build with Go module
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.)


-- 
1013985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013985
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-evanw-esbuild
Version: 0.14.43-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Happened when doing a nodejs 18.4.0 migration check.
However it doesn't look like it is related to node at all.
See attached log.


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

Kernel: Linux 5.18.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
[0KRunning with gitlab-runner 15.1.0 (76984217)[0;m
[0K  on store3 UR8HsV5T[0;m
[0K  feature flags: FF_USE_FASTZIP:true[0;m
section_start:1656417905:prepare_executor
[0K[0K[36;1mPreparing the "custom" executor[0;m[0;m
[0KUsing Custom executor...[0;m
2022-06-28 14:05:05,451 INFO Starting machine using image unstable
2022-06-28 14:05:05,451 INFO Running systemd-run --setenv=SYSTEMD_SECCOMP=0 
--property=KillMode=mixed --property=Type=notify 
--property=RestartForceExitStatus=133 --property=SuccessExitStatus=133 
--property=Slice=machine.slice --property=Delegate=yes 
--property=TasksMax=16384 --property=WatchdogSec=3min 
--property=CPUAccounting=yes --property=CPUWeight=50 
--property=MemoryAccounting=yes --property=MemoryHigh=30% 
--property=MemoryMax=40% systemd-nspawn --quiet 
--directory=/var/lib/nspawn-runner/unstable --machine=run-2926317 --boot 
--notify-ready=yes --suppress-sync=yes 
--overlay=/var/lib/nspawn-runner/unstable:/var/lib/nspawn-runner/.overlays/run-2926317:/
Running as unit: run-red0251b2a8a44cf0a36169f0f4c8c9bf.service
section_end:1656417905:prepare_executor
[0Ksection_start:1656417905:prepare_script
[0K[0K[36;1mPreparing environment[0;m[0;m
Running on store3...
section_end:1656417905:prepare_script
[0Ksection_start:1656417905:get_sources
[0K[0K[36;1mGetting source from Git repository[0;m[0;m
[32;1mFetching changes with git depth set to 1...[0;m
Initialized empty Git repository in 
/var/lib/nspawn-runner/.build/kapouer/nodejs/.git/
[32;1mCreated fresh repository.[0;m
[32;1mChecking out 80d5a07a as transition-18...[0;m

[32;1mSkipping Git submodules setup[0;m
section_end:1656417918:get_sources
[0Ksection_start:1656417918:restore_cache
[0K[0K[36;1mRestoring cache[0;m[0;m
[32;1mChecking cache for 
golang-github-evanw-esbuild-build-non_protected...[0;m
time="2022-06-28T14:05:18+02:00" level=error msg="Docker executor: prebuilt 
image will be loaded from /var/lib/gitlab-runner."
Runtime platform  [0;m  arch[0;m=amd64 
os[0;m=linux pid[0;m=166 revision[0;m=13.3.1 version[0;m=13.3.1
No URL provided, cache will not be downloaded from shared cache server. Instead 
a local version of cache will be extracted.[0;m 
[32;1mSuccessfully extracted cache[0;m
section_end:1656417918:restore_cache
[0Ksection_start:1656417918:download_artifacts
[0K[0K[36;1mDownloading artifacts[0;m[0;m
[32;1mDownloading artifacts for build (2926231)...[0;m
time="2022-06-28T14:05:18+02:00" level=error msg="Docker executor: prebuilt 
image will be loaded from /var/lib/gitlab-runner."
Runtime platform  [0;m  arch[0;m=amd64 
os[0;m=linux pid[0;m=195 revision[0;m=13.3.1 version[0;m=13.3.1
Downloading artifacts from coordinator... ok  [0;m  id[0;m=2926231 
responseStatus[0;m=200 OK token[0;m=1CF5vHbn
section_end:1656417922:download_artifacts
[0Ksection_start:1656417922:step_script
[0K[0K[36;1mExecuting "step_script" stage of the job script[0;m[0;m
[0;33mWARNING: Starting with version 14.0 the 'build_script' stage will be 
replaced with 'step_script': 
https://gitlab.com/gitlab-org/gitlab-runner/-/issues/26426[0;m
[32;1m$ add_extra_repository.sh -v -e "${SALSA_CI_EXTRA_REPOSITORY}" -k 
"${SALSA_CI_EXTRA_REPOSITORY_KEY}"[0;m
+ [[ -n '' ]]
[32;1m$ export CCACHE_DIR=${CCACHE_TMP_DIR} # collapsed multi-line command[0;m
Hit:1 http://deb.debian.org/debian unstable InRelease
Reading package lists...

Processed: Bug#1013985 marked as pending in golang-github-evanw-esbuild

2022-07-16 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 pending
Bug #1013985 [src:golang-github-evanw-esbuild] FTBFS: attempt to build with Go 
module
Added tag(s) pending.

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

Bug#1013985: marked as pending in golang-github-evanw-esbuild

2022-07-16 Thread Shengjing Zhu

Control: tag -1 pending

Hello,

Bug #1013985 in golang-github-evanw-esbuild 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/go-team/packages/golang-github-evanw-esbuild/-/commit/a764c2c65fdfc9eaecdfb53ebf48bd3101aa5e1f


Build wasm in GOPATH mode (Closes: #1013985)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1013985

Bug#1015039: gtk4 memorytexture test-case regresses with Mesa 22.1

2022-07-16 Thread Simon McVittie

Control: retitle -1 gtk4 memorytexture test-case regresses with Mesa 22.1
Control: reassign -1 src:gtk4,src:mesa
Control: found -1 gtk4/4.6.6+ds-1
Control: found -1 mesa/22.1.3-1

On Sat, 16 Jul 2022 at 15:49:25 +0200, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> > ▶  11/681 
> > ERROR:../../../testsuite/gdk/memorytexture.c:389:compare_textures: 
> > assertion failed (expected_data[y * width + x] == test_data[y * width + 
> > x]): (0x55441155 == 0x) ERROR 
> >  11/681 gtk:gdk / memorytexture 
> > ERROR   0.98s   killed by signal 6 SIGABRT

Context for Mesa maintainers: gtk4 fails one of its build-time tests
when built in a current sid environment. In this test, it fills a local
memory buffer with a random colour, uploads it to a GL texture, downloads
it using glReadPixels and compares each pixel with a matching in-memory
texture. The good result is that the colour is the same; the failing
result observed is that the texture is transparent black, rgba(0,0,0,0).

I can reproduce this test failure with sid's mesa 22.1.3-1, but not with
bookworm's mesa, so it seems like this is probably a mesa regression (or
possibly a mesa behaviour change that means what gtk4 is doing no longer
works).

I can also reproduce this test failure without needing to rebuild gtk4,
by using the installed-tests provided in the gtk-4-tests package. Steps
to reproduce:

# apt build-dep gtk4
# apt install gtk-4-tests xvfb xauth dbus
# adduser --disabled-password user
# runuser -u user -- xvfb-run dbus-run-session -- \
  /usr/libexec/installed-tests/gtk-4.0/gdk/memorytexture \
  || echo "failed with status $?"

In a debian:bookworm-slim podman container, this test succeeds.

With all packages except for src:mesa upgraded from bookworm to sid, this
test still succeeds (see attached working-packages.gz).

With all packages *including* those from src:mesa upgraded from bookworm
to sid, the test starts to fail (see attached not-working-packages.gz).

The test has a lot of versions of the scenario that I described, for
different texture sizes, pixel encodings and upload/download pairs: you
can run it as

/usr/libexec/installed-tests/gtk-4.0/gdk/memorytexture -l

to list them, and then run with arguments like

/usr/libexec/installed-tests/gtk-4.0/gdk/memorytexture -p 
/memorytexture/download_4x4/b8g8r8/gl

to run just one version.

>From a bit of experimenting, it seems like the pattern is:

* 1x1/*/gl: fails
* 4x4/*/gl: fails
* 192x192/*/gl: succeeds
* 1x1/*/gl-released: fails
* 4x4/*/gl-released: fails
* 192x192/*/gl-released: fails

The 1x1 or whatever refers to the pixel size of the test texture.
/gl is the sub-test that uploads the texture to GL and then downloads it
again. /gl-released is the same, but it also calls gdk_gl_texture_release(),
documented as:

Releases the GL resources held by a GdkGLTexture.

The texture contents are still available via the
gdk_texture_download() function, after this function has been called.

which seems to be implemented by downloading the GL texture into an
in-memory buffer which will be used as a source for subsequent downloads,
then discarding the actual GL resources. (I don't know why this makes a
difference to whether the 192x192 case succeeds.)

smcv

Processed: Re: Bug#1015039: gtk4 memorytexture test-case regresses with Mesa 22.1

2022-07-16 Thread Debian Bug Tracking System

Processing control commands:

> retitle -1 gtk4 memorytexture test-case regresses with Mesa 22.1
Bug #1015039 [src:gtk4] gtk4: FTBFS, build-time test failure: 
testsuite/gdk/memorytexture.c:389: 0x55441155 != 0x
Changed Bug title to 'gtk4 memorytexture test-case regresses with Mesa 22.1' 
from 'gtk4: FTBFS, build-time test failure: testsuite/gdk/memorytexture.c:389: 
0x55441155 != 0x'.
> reassign -1 src:gtk4,src:mesa
Bug #1015039 [src:gtk4] gtk4 memorytexture test-case regresses with Mesa 22.1
Bug reassigned from package 'src:gtk4' to 'src:gtk4,src:mesa'.
No longer marked as found in versions gtk4/4.6.6+ds-1.
Ignoring request to alter fixed versions of bug #1015039 to the same values 
previously set
> found -1 gtk4/4.6.6+ds-1
Bug #1015039 [src:gtk4,src:mesa] gtk4 memorytexture test-case regresses with 
Mesa 22.1
Marked as found in versions gtk4/4.6.6+ds-1.
> found -1 mesa/22.1.3-1
Bug #1015039 [src:gtk4,src:mesa] gtk4 memorytexture test-case regresses with 
Mesa 22.1
Marked as found in versions mesa/22.1.3-1.

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

Bug#1004769: Video not handled anymore for now

2022-07-16 Thread Steven Robbins

On Friday, July 15, 2022 6:27:51 P.M. CDT you wrote:
>Hi,
> 
>This bug is rather anoying as I'm using digikam to manage my video.

I agree it is annoying.  I feel the same pain.

Given the hard-transition of ffmpeg [1], it is not possible to build with video 
in unstable today.  Digikam was temporarily removed from Debian and the only 
way to re-introduce it is to not use ffmpeg at all which has the serious side 
effect to drop video.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004831

> The low severity (and the title of the bug) does not allow one to stop
> the upgrade with apt-listbugs. In my opinion, this bug is at lease
> important (to be seen by apt-listbugs) and its title should reflect
> that video is not handle by digikam for now (or a new bug can be
> created and blocked by this one)

Thank you for the suggestion.  I was completely unaware of "apt-listbugs".  

I have just re-titled and changed the severity of this bug.  

The manpage for apt-listbugs says it displays serious and above by default.  
Therefore, I have made it 'serious' according to the criteria "in the package 
maintainer's or release manager's opinion, makes the package unsuitable for 
release".

>Due to the large dependencies, it is probably very difficult to
> downgrade digikam to a version with video support once 4:7.7.0-1
> is installed. I did not try for now.

I haven't tried either, so I don't know.  Maybe one can just pull the packages 
from the last stable release?  Build the 7.6 source package ?

I would say that there may well be others in your situation so if you do find a 
method please report back to this bug.  

> I hope video will be soon back.

Upstream is certainly aware of the issue and work is underway to migrate to 
the newer ffmpeg.  I am monitoring the upstream mailing list and sources.  
Based on what I see at present, I'm not optimistic for the short term, so if 
you're using testing or unstable you may want to  look into the downgrade 
option.

I am more hopeful that things will be resolved in time for the next Debian 
release. 

Best,
-Steve

Processed: severity of 1004769 is serious

2022-07-16 Thread Debian Bug Tracking System

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

> severity 1004769 serious
Bug #1004769 [src:digikam] Video support missing (FTBFS with ffmpeg 5.0)
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#1015132: meson: FTBFS: ./b 52a78b9866/../test cases/failing build/2 hidden symbol/bobuser.c:4: undefined reference to `hidden_function'

2022-07-16 Thread Jussi Pakkanen

On Sat, 16 Jul 2022 at 17:04, Lucas Nussbaum  wrote:

> Relevant part (hopefully):
> > /usr/bin/ld: bobuser.p/bobuser.c.o: in function `main':
> > ./b 52a78b9866/../test cases/failing build/2 hidden symbol/bobuser.c:4: 
> > undefined reference to `hidden_function'
> > collect2: error: ld returned 1 exit status

This is the second time (at least) that this issue has been
incorrectly reported. This is not a test failure. As you can tell the
test name has "failing build" in it, which means that failing to
compile is the correct behaviour. If this report has been done by
hand, please in the future report the thing that actually failed (if
any). If this is an automated test then please fix it to not report
spurious failures like this.

Thanks,

Processed: Re: Bug#1013985: golang-github-evanw-esbuild: ftbfs in experimental

2022-07-16 Thread Debian Bug Tracking System

Processing control commands:

> retitle -1 FTBFS: attempt to build with Go module
Bug #1013985 [src:golang-github-evanw-esbuild] golang-github-evanw-esbuild: 
ftbfs in experimental
Changed Bug title to 'FTBFS: attempt to build with Go module' from 
'golang-github-evanw-esbuild: ftbfs in experimental'.

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

Bug#1013985: golang-github-evanw-esbuild: ftbfs in experimental

2022-07-16 Thread Shengjing Zhu

Control: retitle -1 FTBFS: attempt to build with Go module

On Tue, Jun 28, 2022 at 9:30 PM Jérémy Lal  wrote:
>
> Source: golang-github-evanw-esbuild
> Version: 0.14.43-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
>
> Happened when doing a nodejs 18.4.0 migration check.
> However it doesn't look like it is related to node at all.
> See attached log.
>

The log from reproducible-builds is much clearer. It tries to build
with the go module, which is not possible in the Debian build system.

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-evanw-esbuild.html

-- 
Shengjing Zhu

Bug#999527: marked as done (joblib: FTBFS with numpy 1.21 (in experimental): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 15:49:10 +
with message-id 
and subject line Bug#999527: fixed in joblib 1.1.0-2
has caused the Debian Bug report #999527,
regarding joblib: FTBFS with numpy 1.21 (in experimental): dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p 3.9 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.)


-- 
999527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999527
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: joblib
Version: 0.17.0-4
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-numpy121

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64, using numpy 1.21 currently in experimental. This version
will soon be uploaded to unstable.

If you have questions about this, please contact Sandro Tosi
.

Relevant part (hopefully):
>  debian/rules binary
> dh binary --buildsystem=pybuild --with=python3
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of 
> dash-separated 'doc-files' will not be supported in future versions. Please 
> use the underscore name 'doc_files' instead
>   warnings.warn(
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:232: /usr/bin/python3 setup.py build 
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of 
> dash-separated 'doc-files' will not be supported in future versions. Please 
> use the underscore name 'doc_files' instead
>   warnings.warn(
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9/build/joblib
> copying joblib/backports.py -> 
> /<>/.pybuild/cpython3_3.9/build/joblib
> copying joblib/_store_backends.py -> 
> /<>/.pybuild/cpython3_3.9/build/joblib
> copying joblib/numpy_pickle.py -> 
> /<>/.pybuild/cpython3_3.9/build/joblib
> copying joblib/__init__.py -> 
> /<>/.pybuild/cpython3_3.9/build/joblib
> copying joblib/func_inspect.py -> 
> /<>/.pybuild/cpython3_3.9/build/joblib
> copying joblib/_memmapping_reducer.py -> 
> /<>/.pybuild/cpython3_3.9/build/joblib
> copying joblib/_deprecated_my_exceptions.py -> 
> /<>/.pybuild/cpython3_3.9/build/joblib
> copying joblib/memory.py -> 
> /<>/.pybuild/cpython3_3.9/build/joblib
> copying joblib/_parallel_backends.py -> 
> /<>/.pybuild/cpython3_3.9/build/joblib
> copying joblib/logger.py -> 
> /<>/.pybuild/cpython3_3.9/build/joblib
> copying joblib/format_stack.py -> 
> /<>/.pybuild/cpython3_3.9/build/joblib
> copying joblib/compressor.py -> 
> /<>/.pybuild/cpython3_3.9/build/joblib
> copying joblib/hashing.py -> 
> /<>/.pybuild/cpython3_3.9/build/joblib
> copying joblib/my_exceptions.py -> 
> /<>/.pybuild/cpython3_3.9/build/joblib
> copying joblib/_dask.py -> /<>/.pybuild/cpython3_3.9/build/joblib
> copying joblib/_deprecated_format_stack.py -> 
> /<>/.pybuild/cpython3_3.9/build/joblib
> copying joblib/_multiprocessing_helpers.py -> 
> /<>/.pybuild/cpython3_3.9/build/joblib
> copying joblib/numpy_pickle_utils.py -> 
> /<>/.pybuild/cpython3_3.9/build/joblib
> copying joblib/executor.py -> 
> /<>/.pybuild/cpython3_3.9/build/joblib
> copying joblib/pool.py -> /<>/.pybuild/cpython3_3.9/build/joblib
> copying joblib/numpy_pickle_compat.py -> 
> /<>/.pybuild/cpython3_3.9/build/joblib
> copying joblib/parallel.py -> 
> /<>/.pybuild/cpython3_3.9/build/joblib
> copying joblib/testing.py -> 
> /<>/.pybuild/cpython3_3.9/build/joblib
> copying joblib/disk.py -> /<>/.pybuild/cpython3_3.9/build/joblib
> creating /<>/.pybuild/cpython3_3.9/build/joblib/test
> copying joblib/test/test_my_exceptions.py -> 
> /<>/.pybuild/cpython3_3.9/build/joblib/test
> copying joblib/test/test_parallel.py -> 
> /<>/.pybuild/cpython3_3.9/build/joblib/test
> copying joblib/test/test_numpy_pickle_utils.py -> 
> /<>/.pybuild/cpython3_3.9/build/joblib/test
> copying joblib/test/test_memory.py -> 
> /<>/.pybuild/cpython3_3.9/build/joblib/test
> copying joblib/test/test_hashing.py -> 
> /<>/.pybuild/cpython3_3.9/build/joblib/test
> copying joblib/test/__init__.py -> 
> /<>/.pybuild/cpython3_3.9/build/joblib/test
> copying joblib/test/test_store_backends.py -> 
> /<>/.pybuild/cpython3_3.9/build/joblib/test
> copying joblib/test/test_backports.py -> 
> /<>/.pybuild/cpython3_3.9/build/joblib/test
> copying joblib/test/test_disk.py -> 
> /<>/.pybuild/cpython3_3.9/build/joblib/test
> copying

Bug#1015067: marked as done (python-shapely: FTBFS: AttributeError: can't set attribute '_is_empty')

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 15:34:06 +
with message-id 
and subject line Bug#1015067: fixed in python-shapely 1.8.2-1
has caused the Debian Bug report #1015067,
regarding python-shapely: FTBFS: AttributeError: can't set attribute '_is_empty'
to be marked as done.

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

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


-- 
1015067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015067
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-shapely
Version: 1.8.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220716 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_test
> I: pybuild base:239: cd /<>/.pybuild/cpython3_3.9_shapely/build; 
> python3.9 -m pytest tests
> = test session starts 
> ==
> platform linux -- Python 3.9.13, pytest-7.1.2, pluggy-1.0.0
> numpy: 1.21.5
> rootdir: /<>, configfile: setup.cfg
> collected 481 items
> 
> tests/test_affinity.py ..[  
> 2%]
> tests/test_binascii_hex.txt .[  
> 3%]
> tests/test_box.py ...[  
> 3%]
> tests/test_buffer.py [  
> 5%]
> tests/test_cga.py    [  
> 6%]
> tests/test_clip_by_rect.py ...xx [  
> 8%]
> tests/test_collection.py [ 
> 11%]
> tests/test_coords.py ... [ 
> 12%]
> tests/test_create_inconsistent_dimensionality.py ... [ 
> 14%]
> tests/test_default_impl.py ..[ 
> 14%]
> tests/test_delaunay.py ...   [ 
> 15%]
> tests/test_delegated.py ..   [ 
> 15%]
> tests/test_dlls.py ..[ 
> 16%]
> tests/test_doctests.py . [ 
> 16%]
> tests/test_emptiness.py ...  [ 
> 19%]
> tests/test_empty_polygons.py [ 
> 20%]
> tests/test_equality.py ...   [ 
> 20%]
> tests/test_geointerface.py .Exception ignored in:  BaseGeometry.__del__ at 0x7fe96270>
> Traceback (most recent call last):
>   File 
> "/<>/.pybuild/cpython3_3.9_shapely/build/shapely/geometry/base.py",
>  line 209, in __del__
> self._empty(val=None)
>   File 
> "/<>/.pybuild/cpython3_3.9_shapely/build/shapely/geometry/base.py",
>  line 199, in _empty
> self._is_empty = True
>   File 
> "/<>/.pybuild/cpython3_3.9_shapely/build/shapely/geometry/proxy.py",
>  line 44, in __setattr__
> object.__setattr__(self, name, value)
> AttributeError: can't set attribute
> ...  [ 21%]
> tests/test_geometry_base.py  [ 
> 24%]
> tests/test_geomseq.py .  [ 
> 24%]
> tests/test_geos_err_handler.py ..[ 
> 25%]
> tests/test_getitem.py ...[ 
> 28%]
> tests/test_hash.py   [ 
> 28%]
> tests/test_invalid_geometries.py .   [ 
> 29%]
> tests/test_iterops.py    [ 
> 29%]
> tests/test_linear_referencing.py .   [ 
> 31%]
> tests/test_linemerge.py .[ 
> 32%]
> tests/test_linestring.py ..  [ 
> 38%]
> tests/test_locale.py s   [ 
> 38%]
> tests/test_make_valid.py ..  [ 
> 38%]
> tests/test_mapping.py ..

Bug#1015091: marked as done (php-guzzlehttp-psr7: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)

2022-07-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Jul 2022 15:33:58 +
with message-id 
and subject line Bug#1015091: fixed in php-http-interop-http-factory-tests 
0.9.0-3
has caused the Debian Bug report #1015091,
regarding php-guzzlehttp-psr7: FTBFS: E: Build killed with signal TERM after 
150 minutes of inactivity
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.)


-- 
1015091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015091
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-guzzlehttp-psr7
Version: 2.4.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220716 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> Error in bootstrap script: Error:
> Failed opening required 'Psr/HttpFactory/autoload.php' 
> (include_path='.:/usr/share/php')
> #0 /<>/vendor/autoload.php(5): require_once()
> #1 /usr/share/php/PHPUnit/Util/FileLoader.php(65): include_once('...')
> #2 /usr/share/php/PHPUnit/Util/FileLoader.php(49): 
> PHPUnit\Util\FileLoader::load()
> #3 /usr/share/php/PHPUnit/TextUI/Command.php(562): 
> PHPUnit\Util\FileLoader::checkAndLoad()
> #4 /usr/share/php/PHPUnit/TextUI/Command.php(344): 
> PHPUnit\TextUI\Command->handleBootstrap()
> #5 /usr/share/php/PHPUnit/TextUI/Command.php(111): 
> PHPUnit\TextUI\Command->handleArguments()
> #6 /usr/share/php/PHPUnit/TextUI/Command.php(96): 
> PHPUnit\TextUI\Command->run()
> #7 /usr/bin/phpunit(73): PHPUnit\TextUI\Command::main()
> #8 {main}
> make[1]: *** [debian/rules:24: override_dh_auto_test] Error 1
> make[1]: Leaving directory '/<>'
> make: *** [debian/rules:3: binary] Error 2
> dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
> 2
> E: Build killed with signal TERM after 150 minutes of inactivity


The full build log is available from:
http://qa-logs.debian.net/2022/07/16/php-guzzlehttp-psr7_2.4.0-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220716=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: php-http-interop-http-factory-tests
Source-Version: 0.9.0-3
Done: David Prévot 

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

Debian distribution maintenance software
pp.
David Prévot  (supplier of updated 
php-http-interop-http-factory-tests package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 16 Jul 2022 16:32:27 +0200
Source: php-http-interop-http-factory-tests
Architecture: source
Version: 0.9.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: David Prévot 
Closes: 1015091
Changes:
 php-http-interop-http-factory-tests (0.9.0-3) unstable; urgency=medium
 .
   * Add build-dependency needed for phpabtpl(1) (Closes: #1015091)
Checksums-Sha1:
 5d986a9a08027760ee81616c97b7dc370a340ba5 1998 
php-http-interop-http-factory-tests_0.9.0-3.dsc
 e85aa7a010cf3c6bf9a3edbbacd6d99658c75602 2364 
php-http-interop-http-factory-tests_0.9.0-3.debian.tar.xz
 425348079b7181fefed5aa9965f800eb3c12cd13 7904 
php-http-interop-http-factory-tests_0.9.0-3_amd64.buildinfo
Checksums-Sha256:
 f7219ec4d4a687c8d22bf20f3c7d7d4a75f1e51320080095783277283f4901a9 1998 
php-http-interop-http-factory-tests_0.9.0-3.dsc
 e9

Processed: limit source to php-http-interop-http-factory-tests, tagging 1015091

2022-07-16 Thread Debian Bug Tracking System

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

> limit source php-http-interop-http-factory-tests
Limiting to bugs with field 'source' containing at least one of 
'php-http-interop-http-factory-tests'
Limit currently set to 'source':'php-http-interop-http-factory-tests'

> tags 1015091 + pending
Bug #1015091 [php-http-interop-http-factory-tests] php-guzzlehttp-psr7: FTBFS: 
E: Build killed with signal TERM after 150 minutes of inactivity
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1015067: python-shapely: FTBFS: AttributeError: can't set attribute '_is_empty'

2022-07-16 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 upstream pending
Bug #1015067 [src:python-shapely] python-shapely: FTBFS: AttributeError: can't 
set attribute '_is_empty'
Added tag(s) upstream and pending.

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

Bug#1015067: python-shapely: FTBFS: AttributeError: can't set attribute '_is_empty'

2022-07-16 Thread Sebastiaan Couwenberg


Control: tags -1 upstream pending

On 7/16/22 15:32, Lucas Nussbaum wrote:

=== FAILURES ===
__ OperationsTestCase.test_parallel_offset_linestring __

self = 

 def test_parallel_offset_linestring(self):
 line1 = LineString([(0, 0), (10, 0)])
 left = line1.parallel_offset(5, 'left')
 self.assertEqual(left, LineString([(0, 5), (10, 5)]))
 right = line1.parallel_offset(5, 'right')

   self.assertEqual(right, LineString([(10, -5), (0, -5)]))

E   AssertionError:  != 
This is the actual reason for the FTBFS, not the AttributeError that 
occurs during the tests.


It's caused by changes in GEOS 3.11.0, and fixed upstream already.

The patch has been added to the package and a new upload will follow 
shortly.


Kind Regards,

Bas

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

Bug#1015123: latex-cjk-chinese-arphic: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

2022-07-16 Thread 韓達耐

Thanks Lucas, I'll look at it tonight.

On Sat, 16 Jul 2022, 22:04 Lucas Nussbaum,  wrote:

> Source: latex-cjk-chinese-arphic
> Version: 1.24
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20220716 ftbfs-bookworm
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
>
> Relevant part (hopefully):
> > Reading subfont definition file
> `/usr/share/texlive/texmf-dist/fonts/sfd/ttf2pk/Unicode.sfd'...
> > Writing extended font definition file `c70bsmi.fdx'...
> >
> > # Remove the *.enc files; they're not used.
> > ( cd build/bsmi00lp && rm -f *.enc )
> >
> > # Create a Type1 font map.
> >
> > # Create entries for the font definition file
> > # `c00bsmi.fd' (which uses UBig5 encoding).
> >
> > # Create entries for the font definition file
> > # `c70bsmi.fd' (which uses Unicode encoding).
> >
> > touch build-stamp.bsmi
> > E: Build killed with signal TERM after 150 minutes of inactivity
>
>
> The full build log is available from:
>
> http://qa-logs.debian.net/2022/07/16/latex-cjk-chinese-arphic_1.24_unstable.log
>
> All bugs filed during this archive rebuild are listed at:
>
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org
> or:
>
> https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220716=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.
>
>

Processed: retitle 1015039 to gtk4: FTBFS, build-time test failure: testsuite/gdk/memorytexture.c:389: 0x55441155 != 0x00000000

2022-07-16 Thread Debian Bug Tracking System

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

> retitle 1015039 gtk4: FTBFS, build-time test failure: 
> testsuite/gdk/memorytexture.c:389: 0x55441155 != 0x
Bug #1015039 [src:gtk4] gtk4: FTBFS: make[1]: *** [debian/rules:264: 
override_dh_auto_test] Error 1
Changed Bug title to 'gtk4: FTBFS, build-time test failure: 
testsuite/gdk/memorytexture.c:389: 0x55441155 != 0x' from 'gtk4: FTBFS: 
make[1]: *** [debian/rules:264: override_dh_auto_test] Error 1'.
> thanks
Stopping processing here.

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

Processed: reassign 1015091 to php-http-interop-http-factory-tests

2022-07-16 Thread Debian Bug Tracking System

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

> reassign 1015091 php-http-interop-http-factory-tests
Bug #1015091 [src:php-guzzlehttp-psr7] php-guzzlehttp-psr7: FTBFS: E: Build 
killed with signal TERM after 150 minutes of inactivity
Bug reassigned from package 'src:php-guzzlehttp-psr7' to 
'php-http-interop-http-factory-tests'.
No longer marked as found in versions php-guzzlehttp-psr7/2.4.0-2.
Ignoring request to alter fixed versions of bug #1015091 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: tagging 1015088, bug 1015088 is forwarded to https://github.com/golang/go/issues/53916

2022-07-16 Thread Debian Bug Tracking System

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

> tags 1015088 + upstream
Bug #1015088 [src:golang-1.18] icingadb: FTBFS: ../pkg/com/bulker.go:30:16: 
internal compiler error: assertion failed
Added tag(s) upstream.
> forwarded 1015088 https://github.com/golang/go/issues/53916
Bug #1015088 [src:golang-1.18] icingadb: FTBFS: ../pkg/com/bulker.go:30:16: 
internal compiler error: assertion failed
Set Bug forwarded-to-address to 'https://github.com/golang/go/issues/53916'.
> thanks
Stopping processing here.

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

Processed: Re: [Pkg-nagios-devel] Bug#1015088: icingadb: FTBFS: ../pkg/com/bulker.go:30:16: internal compiler error: assertion failed

2022-07-16 Thread Debian Bug Tracking System

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

> reassign 1015088 src:golang-1.18
Bug #1015088 [src:icingadb] icingadb: FTBFS: ../pkg/com/bulker.go:30:16: 
internal compiler error: assertion failed
Bug reassigned from package 'src:icingadb' to 'src:golang-1.18'.
No longer marked as found in versions icingadb/1.0.0-1.
Ignoring request to alter fixed versions of bug #1015088 to the same values 
previously set
> found 1015088 golang-1.18/1.18.4-1
Bug #1015088 [src:golang-1.18] icingadb: FTBFS: ../pkg/com/bulker.go:30:16: 
internal compiler error: assertion failed
Marked as found in versions golang-1.18/1.18.4-1.
> affects 1015088 src:icingadb
Bug #1015088 [src:golang-1.18] icingadb: FTBFS: ../pkg/com/bulker.go:30:16: 
internal compiler error: assertion failed
Added indication that 1015088 affects src:icingadb
> thanks
Stopping processing here.

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

Bug#1015088: [Pkg-nagios-devel] Bug#1015088: icingadb: FTBFS: ../pkg/com/bulker.go:30:16: internal compiler error: assertion failed

2022-07-16 Thread Sebastiaan Couwenberg


reassign 1015088 src:golang-1.18
found 1015088 golang-1.18/1.18.4-1
affects 1015088 src:icingadb
thanks

On 7/16/22 15:21, Lucas Nussbaum wrote:

dh_auto_build
cd _build && go version
go version go1.18.4 linux/amd64
cd _build && go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN=""
GOCACHE="/<>/_build/go-build"
GOENV="/sbuild-nonexistent/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/<>/_build/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/<>/_build"
GOPRIVATE=""
GOPROXY="off"
GOROOT="/usr/lib/go-1.18"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go-1.18/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.18.4"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/<>/go.mod"
GOWORK=""
CGO_CFLAGS="-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security"
CGO_CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2"
CGO_CXXFLAGS="-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security"
CGO_FFLAGS="-g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong"
CGO_LDFLAGS="-Wl,-z,relro"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 
-fdebug-prefix-map=/tmp/go-build898317925=/tmp/go-build -gno-record-gcc-switches"
cd _build && go install -trimpath -v -p 8 
github.com/icinga/icingadb/cmd/icingadb
[...]
github.com/icinga/icingadb/pkg/com
os/user
# github.com/icinga/icingadb/pkg/com
../pkg/com/bulker.go:30:16: internal compiler error: assertion failed

Please file a bug report including a short program that triggers the error.
https://go.dev/issue/new


This issue is introduced in golang-1.18 (1.18.4-1), icingadb built 
successfully with 1.18.3-1.


Kind Regards,

Bas

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

1 2 3 >

1 - 100 of 225 matches

Mail list logo