Bug#1001714: update 2

[detlev schmidtke]

After numerous installation attempts with a lot of trial and error, I
got it bootable, but unfortunately cannot say, what in particular let
the error message disappear 

Bug#984232: status

[Anton Gladky]

This bug is fixed. I followed the advice from Adrian and now the package
builds fine.

Regards

Anton

Am Sa., 18. Dez. 2021 um 01:39 Uhr schrieb Ryan Pavlik :
>
> The updated package just needs the copyright file updated and reviewed. If 
> you'd like a fix uploaded before I get a chance to do that (which is somewhat 
> intimidating, they swapped some bundled dependencies since the last packaged 
> version), please feel free to nmu. Alternately I'd happily accept an mr to 
> make the copyright file complete again.
>
> Ryan
>
> On Wed, Dec 15, 2021, 5:24 AM Adrian Bunk  wrote:
>>
>> On Mon, Nov 15, 2021 at 02:53:40PM -0600, Ryan Pavlik wrote:
>> > Upstream has fixed this, and I have a package with the latest upstream
>> > sources in progress, happy to accept help to put it over the edge.
>>
>> Any progress on this?
>>
>> If necessary, I could NMU with the minimal fix of adding
>>   export DEB_CXXFLAGS_MAINT_APPEND += -std=gnu++14
>> to debian/rules.
>>
>> > Ryan
>>
>> cu
>> Adrian
>>
> --
> debian-science-maintainers mailing list
> debian-science-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Processed: bug 998527 is forwarded to https://github.com/log2timeline/dfvfs/commit/068cfd815c85a1077005f692bd94892b9a325a17

[Debian Bug Tracking System]

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

> forwarded 998527 
> https://github.com/log2timeline/dfvfs/commit/068cfd815c85a1077005f692bd94892b9a325a17
Bug #998527 [src:dfvfs] dfvfs: FTBFS: TypeError: 
_GetNumberOfSecondsFromElements() takes 7 positional arguments but 8 were given
Set Bug forwarded-to-address to 
'https://github.com/log2timeline/dfvfs/commit/068cfd815c85a1077005f692bd94892b9a325a17'.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1000233: php-remctl lost its phpapi-20190902 dependency

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 dh-php
Bug #1000233 [php-remctl] php-remctl lost its phpapi-20190902 dependency
Bug reassigned from package 'php-remctl' to 'dh-php'.
No longer marked as found in versions remctl/3.17-1.
Ignoring request to alter fixed versions of bug #1000233 to the same values 
previously set
> severity -1 important
Bug #1000233 [dh-php] php-remctl lost its phpapi-20190902 dependency
Severity set to 'important' from 'serious'
> affects -1 + php-remctl
Bug #1000233 [dh-php] php-remctl lost its phpapi-20190902 dependency
Added indication that 1000233 affects php-remctl
> affects -1 + kopanocore
Bug #1000233 [dh-php] php-remctl lost its phpapi-20190902 dependency
Added indication that 1000233 affects kopanocore
> affects -1 + libguestfs
Bug #1000233 [dh-php] php-remctl lost its phpapi-20190902 dependency
Added indication that 1000233 affects libguestfs
> affects -1 + libvirt-php
Bug #1000233 [dh-php] php-remctl lost its phpapi-20190902 dependency
Added indication that 1000233 affects libvirt-php
> affects -1 + mapserver
Bug #1000233 [dh-php] php-remctl lost its phpapi-20190902 dependency
Added indication that 1000233 affects mapserver
> affects -1 + php-excimer
Bug #1000233 [dh-php] php-remctl lost its phpapi-20190902 dependency
Added indication that 1000233 affects php-excimer
> affects -1 + php-facedetect
Bug #1000233 [dh-php] php-remctl lost its phpapi-20190902 dependency
Added indication that 1000233 affects php-facedetect
> affects -1 + php-horde-lz4
Bug #1000233 [dh-php] php-remctl lost its phpapi-20190902 dependency
Added indication that 1000233 affects php-horde-lz4
> affects -1 + php-luasandbox
Bug #1000233 [dh-php] php-remctl lost its phpapi-20190902 dependency
Added indication that 1000233 affects php-luasandbox
> affects -1 + php-wmerrors
Bug #1000233 [dh-php] php-remctl lost its phpapi-20190902 dependency
Added indication that 1000233 affects php-wmerrors
> affects -1 + php-sass
Bug #1000233 [dh-php] php-remctl lost its phpapi-20190902 dependency
Added indication that 1000233 affects php-sass
> affects -1 + php-tideways
Bug #1000233 [dh-php] php-remctl lost its phpapi-20190902 dependency
Added indication that 1000233 affects php-tideways
> affects -1 + php-wikidiff2
Bug #1000233 [dh-php] php-remctl lost its phpapi-20190902 dependency
Added indication that 1000233 affects php-wikidiff2
> affects -1 + php-zeroc-ice
Bug #1000233 [dh-php] php-remctl lost its phpapi-20190902 dependency
Added indication that 1000233 affects php-zeroc-ice

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

Bug#1000233: php-remctl lost its phpapi-20190902 dependency

[Russ Allbery]

Control: reassign -1 dh-php
Control: severity -1 important
Control: affects -1 + php-remctl
Control: affects -1 + kopanocore
Control: affects -1 + libguestfs
Control: affects -1 + libvirt-php
Control: affects -1 + mapserver
Control: affects -1 + php-excimer
Control: affects -1 + php-facedetect
Control: affects -1 + php-horde-lz4
Control: affects -1 + php-luasandbox
Control: affects -1 + php-wmerrors
Control: affects -1 + php-sass
Control: affects -1 + php-tideways
Control: affects -1 + php-wikidiff2
Control: affects -1 + php-zeroc-ice

Replaying the control commands from the below message because it looks
like they didn't take for some reason (maybe because there was a Control:
line with no command at the start of the message).

Ondřej Surý  writes:

> Hi Russ,

> I am reassigning this bug to dh-php as I need to figure out what to
> do with non-PECL extensions in the long run. The dh-php might
> need some compatibility layer to support packages that bundle PHP
> with something else.

> I rewrote dh-php >= 4 to generate phpX.Y- out of the template
> and there are couple more loose ends that needs either fix in the
> package or in the dh-php.

> The whole perl + shell + makefile has also lot of duct tape included.
> I’ll either fix this directly in dh-php or provide the affected packages
> with a patch.

> 1. I don’t think missing dependency on PHP is a serious bug, it doesn’t
> prevent usage of the extension, it just doesn’t pull the interpreter in.

-- 
Russ Allbery (r...@debian.org)  

Bug#984232: status

[Ryan Pavlik]

The updated package just needs the copyright file updated and reviewed. If
you'd like a fix uploaded before I get a chance to do that (which is
somewhat intimidating, they swapped some bundled dependencies since the
last packaged version), please feel free to nmu. Alternately I'd happily
accept an mr to make the copyright file complete again.

Ryan

On Wed, Dec 15, 2021, 5:24 AM Adrian Bunk  wrote:

> On Mon, Nov 15, 2021 at 02:53:40PM -0600, Ryan Pavlik wrote:
> > Upstream has fixed this, and I have a package with the latest upstream
> > sources in progress, happy to accept help to put it over the edge.
>
> Any progress on this?
>
> If necessary, I could NMU with the minimal fix of adding
>   export DEB_CXXFLAGS_MAINT_APPEND += -std=gnu++14
> to debian/rules.
>
> > Ryan
>
> cu
> Adrian
>
>

Processed: libimage-metadata-jpeg-perl: diff for NMU version 0.153-1.2

[Debian Bug Tracking System]

Processing control commands:

> tags 999061 + patch
Bug #999061 [src:libimage-metadata-jpeg-perl] libimage-metadata-jpeg-perl: 
missing required debian/rules targets build-arch and/or build-indep
Added tag(s) patch.
> tags 999061 + pending
Bug #999061 [src:libimage-metadata-jpeg-perl] libimage-metadata-jpeg-perl: 
missing required debian/rules targets build-arch and/or build-indep
Added tag(s) pending.

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

Bug#999061: libimage-metadata-jpeg-perl: diff for NMU version 0.153-1.2

[gregor herrmann]

Control: tags 999061 + patch
Control: tags 999061 + pending


Dear maintainer,

I've prepared an NMU for libimage-metadata-jpeg-perl (versioned as 0.153-1.2) 
and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Flying Pickets: Wonderful World
diff -u libimage-metadata-jpeg-perl-0.153/debian/changelog libimage-metadata-jpeg-perl-0.153/debian/changelog
--- libimage-metadata-jpeg-perl-0.153/debian/changelog
+++ libimage-metadata-jpeg-perl-0.153/debian/changelog
@@ -1,3 +1,12 @@
+libimage-metadata-jpeg-perl (0.153-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "missing required debian/rules targets build-arch and/or build-
+indep": add missing targets to debian/rules.
+(Closes: #999061)
+
+ -- gregor herrmann   Sat, 18 Dec 2021 01:27:53 +0100
+
 libimage-metadata-jpeg-perl (0.153-1.1) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.
diff -u libimage-metadata-jpeg-perl-0.153/debian/rules libimage-metadata-jpeg-perl-0.153/debian/rules
--- libimage-metadata-jpeg-perl-0.153/debian/rules
+++ libimage-metadata-jpeg-perl-0.153/debian/rules
@@ -28,7 +28,7 @@
 	touch configure-stamp
 
 
-build: build-stamp
+build-indep: build-stamp
 
 build-stamp: configure-stamp 
 	dh_testdir
@@ -46,6 +46,11 @@
 
 	touch $@
 
+# Nothing to do
+build-arch:
+
+build: build-indep
+
 clean:
 	dh_testdir
 	dh_testroot
@@ -109,4 +114,4 @@
 # We have nothing to do by default.
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install configure
+.PHONY: build-indep build-arch build clean binary-indep binary-arch binary install configure


signature.asc
Description: Digital Signature

Bug#984154: marked as done (gnome-chemistry-utils: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Sat, 18 Dec 2021 00:18:59 +
with message-id 
and subject line Bug#984154: fixed in gnome-chemistry-utils 0.14.17-6.1
has caused the Debian Bug report #984154,
regarding gnome-chemistry-utils: ftbfs with GCC-11
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.)


-- 
984154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984154
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gnome-chemistry-utils
Version: 0.14.17-5
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

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

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/gnome-chemistry-utils_0.14.17-5_unstable_gcc11.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

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

[...]
  181 | bool SetTarget (char const *id, Object **target, Object 
*parent, Object *owner = NULL, Action action = ActionException) throw 
(std::runtime_error);
  | 
^
document.h:187:32: error: ISO C++17 does not allow dynamic exception 
specifications
  187 | virtual bool Loaded () throw (LoaderError);
  |^
make[4]: *** [Makefile:687: chain.lo] Error 1
make[4]: *** Waiting for unfinished jobs
make[4]: *** [Makefile:687: atom.lo] Error 1
make[4]: *** [Makefile:687: bond.lo] Error 1
application.cc: In member function ‘void gcu::Application::AddRule(gcu::TypeId, 
gcu::RuleId, gcu::TypeId)’:
application.cc:432:64: warning: this statement may fall through 
[-Wimplicit-fallthrough=]
  432 | typedesc1.RequiredChildren.insert (typedesc2.Id);
  |^
application.cc:433:9: note: here
  433 | case RuleMayContain:
  | ^~~~
application.cc:438:63: warning: this statement may fall through 
[-Wimplicit-fallthrough=]
  438 | typedesc1.RequiredParents.insert (typedesc2.Id);
  |   ^
application.cc:439:9: note: here
  439 | case RuleMayBeIn:
  | ^~~~
application.cc: In member function ‘char* gcu::Application::ConvertToCML(const 
string&, const char*, const char*)’:
application.cc:597:23: warning: ignoring return value of ‘ssize_t write(int, 
const void*, size_t)’ declared with attribute ‘warn_unused_result’ 
[-Wunused-result]
  597 | write (sock, buf.c_str (), buf.length ());
  | ~~^~~
application.cc:644:23: warning: ignoring return value of ‘ssize_t write(int, 
const void*, size_t)’ declared with attribute ‘warn_unused_result’ 
[-Wunused-result]
  644 | write (sock, buf.c_str (), buf.length ());
  | ~~^~~
application.cc:645:23: warning: ignoring return value of ‘ssize_t write(int, 
const void*, size_t)’ declared with attribute ‘warn_unused_result’ 
[-Wunused-result]
  645 | write (sock, szbuf, size);
  | ~~^~~
application.cc: In member function ‘char* 
gcu::Application::ConvertToCML(GsfInput*, const char*, const char*)’:

Bug#1001785: texlive-extra affected by log4j CVEs

[Hilmar Preuße]

Am 16.12.2021 um 09:38 teilte Sven Mueller mit:

Hi,


texlive-extra-utils contains arara (https://github.com/islandoftex/arara)
which was updated two days ago via TeX Live (https://www.tug.org/texlive/)
which was updated slightly after that. Please update to the newest TeX Live
ASAP, as arara in unstable and testing (also stable?) currently bundles a
vulnerable apache-log4j2 version.

For unstable / testing I'll simply push a new CTAN snapshot to the 
archive. Should not be that hard.


I did not check stable yet, but I'm pretty sure it is affected too. I'd 
put the jar file in question on the blacklist and hence remove it from 
the package. Would this be OK?


Did you check oldstable yet?

Hilmar
--
sigfault



OpenPGP_signature
Description: OpenPGP digital signature

Processed: tagging 1001485

[Debian Bug Tracking System]

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

> tags 1001485 + pending
Bug #1001485 [src:shellingham] shellingham: autopkgtest tests all supported 
python3 versions but doesn't ensure they are installed
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1001824: xml2rfc: Incompatible with current weaseyprint

[Scott Kitterman]

On Thu, 16 Dec 2021 23:28:26 -0500 Scott Kitterman  
wrote:
> Package: xml2rfc
> Version: 3.12.0-1
> Severity: serious
> Tags: ftbfs upstream patch
> Justification: fails to build from source
> 
> Note: Using ftbfs because that's the closest thing we have to an
> autopkgtest failure.
> 
> The new version of weasyprint no longer uses the same PDF generation
> libraries and as a result, xml2rfc's detection mechanism for if it is
> capable of making a PDF is not working (see attached patch).
> 
> Once the detection mechanism is patched, PDF generation works fine,
> which leads me to believe the test failure is bogus:
> 
> ==
> FAIL: test_text_content (__main__.PdfWriterTests)
> --
> Traceback (most recent call last):
>   File "/home/xml2rfc-3.12.0/test.py", line 510, in test_text_content
> self.assertIn(t, text)
> AssertionError: 'RFC' not found in 'l- WN –&,ÛžÆ TNDQ&·sX l-%Zñ¢<³ WN P½RÔ
> n®>Ø %˜oh l† .µ ¬( .µ=N'
> 
> --
> 
> If things were really that garbled, I don't see how it could make a PDF.
> 
> Reported upstream:
> 
> https://trac.ietf.org/trac/xml2rfc/ticket/696
> 
> In the interim, I think it might make sense to apply the attached patch
> and get rid of the failing test.  If we go down this path, then this
> will also need fixing (get rid of HAVE_CAIRO and HAVE_PANGO):
> 
> xml2rfc-3.12.0/test.py", line 513, in test_included_fonts
> 
> if xml2rfc.HAVE_WEASYPRINT and xml2rfc.HAVE_PYCAIRO and
> xml2rfc.HAVE_CAIRO and xml2rfc.HAVE_PANGO:

dkg,

Unless you want to object, I think we should go ahead and make this change.  I 
don't get the impression that since the IETF LLC booted Henrik there's much 
upstream going on, so I don't see much point in waiting for them.

Scott K

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

Bug#1001855: marked as done (eslint breaks node-domino autopkgtest: Cannot find module 'js-yaml')

[Debian Bug Tracking System]

Your message dated Fri, 17 Dec 2021 21:15:25 +
with message-id 
and subject line Bug#1001855: fixed in node-domino 2.1.6~ds-3
has caused the Debian Bug report #1001855,
regarding eslint breaks node-domino autopkgtest: Cannot find module 'js-yaml'
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.)


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

Source: eslint, node-domino
Control: found -1 eslint/5.16.0~dfsg+~4.16.8-9
Control: found -1 node-domino/2.1.6~ds-1
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
eslint from testing5.16.0~dfsg+~4.16.8-9
node-dominofrom testing2.1.6~ds-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. Is this 
pointing at a missing (test) dependency somewhere?


Currently this regression is blocking the migration of eslint 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

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

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-domino/17644607/log.gz

There was a problem loading formatter: ./formatters/tap
Error: Cannot find module 'js-yaml'
Require stack:
- /usr/share/nodejs/eslint/lib/formatters/tap.js
- /usr/share/nodejs/eslint/lib/cli-engine.js
- /usr/share/nodejs/eslint/lib/cli.js
- /usr/share/nodejs/eslint/bin/eslint.js
autopkgtest [12:10:53]: test command2



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: node-domino
Source-Version: 2.1.6~ds-3
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-domino package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 17 Dec 2021 21:41:52 +0100
Source: node-domino
Architecture: source
Version: 2.1.6~ds-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1001855
Changes:
 node-domino (2.1.6~ds-3) unstable; urgency=medium
 .
   * Team upload
   * Add test dependency to node-js-yaml (Closes: #1001855)
Checksums-Sha1: 
 c39ca2ce4f1e38e9b0d0f3aae4c319ca96bc2aba 2189 node-domino_2.1.6~ds-3.dsc
 3457326cbaf8775eeb7e28a74fdd7c1e76f62975 10632 
node-domino_2.1.6~ds-3.debian.tar.xz
Checksums-Sha256: 
 fa76fc8da9052124d8dfc2bc1f4c24e632eb9f3ee3de117c1f19ff5bf1bf69e2 2189 
node-domino_2.1.6~ds-3.dsc
 597115f7db240bd915007e5f2ed853cf6cf7a7cd0f47a058f171b8a9c960547f 10632 
node-domino_2.1.6~ds-3.debian.tar.xz
Files: 
 1cd00f24ebfa97600161de63f9f393c1 2189 javascript optional 
node-domino_2.1.6~ds-3.dsc
 5bd4f2bee0e5d030e73ea1222b1c6445 10632 javascript optional 
node-domino_2.1.6~ds-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmG89nMACgkQ9tdMp8mZ
7ukzew/7BNWutlBItiGVYxuB5/YOuNZWUH+0OnwXoZ2/x3L9r6OHGCX67VKJuJqB
elImf9xBswTwc+MkGEyde8nDnSOv/gizGv4FyeME/q7/BbBmZhssfrGGeI92f73s
bYnhNDB3I8NCkG3M32MOgsLYcIoNhR1rM9Kzj3utAsygnH0FDgb9drWRIw3kI2ES
beFGzDDhJEuNWZ+8/MHhVHG/1jfDOe+dxIk0+vC8lf86PzCXv7e22C9mb8O9mYxA
NKONijAzyyZ6tqM1/UZElc06bijlaaELMvIukRrKazEYQeafSORyoUjEpmq9Rax6
sv8NQOQU6XiSxHKOdM18AurU1AXXnPB0lwcSemL4fgpHr3jNKN21vkYpko+fkmpU
LRWVdSJspkZiR5NKnhOzijtcheDwP49XqzlyjfAK8sIJie6J+fJXadSCtNefJC1H

Bug#1001243: marked as done (cloud-sptheme: autopkgtest needs update for new version of python3-defaults: python3.10: not found)

[Debian Bug Tracking System]

Your message dated Fri, 17 Dec 2021 21:05:13 +
with message-id 
and subject line Bug#1001243: fixed in cloud-sptheme 1.10.1.post20200504175005-4
has caused the Debian Bug report #1001243,
regarding cloud-sptheme: autopkgtest needs update for new version of 
python3-defaults: python3.10: not found
to be marked as done.

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

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


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

Source: cloud-sptheme
Version: 1.10.1.post20200504175005-3
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:python3-defaults

Dear maintainer(s),

With a recent upload of python3-defaults the autopkgtest of 
cloud-sptheme fails in testing when that autopkgtest is run with the 
binary packages of python3-defaults from unstable. It passes when run 
with only packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.9.8-1
cloud-sptheme  from testing1.10.1.post20200504175005-3
all others from testingfrom testing

I copied some of the output at the bottom of this report. Seems you test 
for all supported Python3 versions but you don't ensure they are 
actually all installed during autopkgtesting.


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


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


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

Paul

[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/c/cloud-sptheme/17290350/log.gz

=== python3.10 ===
/tmp/autopkgtest-lxc.gop2f388/downtmp/build.veH/src/debian/tests/unittests: 
8: python3.10: not found

autopkgtest [19:10:44]: test unittests



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: cloud-sptheme
Source-Version: 1.10.1.post20200504175005-4
Done: Stefano Rivera 

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

Debian distribution maintenance software
pp.
Stefano Rivera  (supplier of updated cloud-sptheme package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 17 Dec 2021 16:29:41 -0400
Source: cloud-sptheme
Architecture: source
Version: 1.10.1.post20200504175005-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Stefano Rivera 
Closes: 1001243
Changes:
 cloud-sptheme (1.10.1.post20200504175005-4) unstable; urgency=medium
 .
   * autopkgtest: Depend on python3-all. (Closes: #1001243)
Checksums-Sha1:
 c5aec3e50915a3246a63140d760913a4fbaffc20 1795 
cloud-sptheme_1.10.1.post20200504175005-4.dsc
 c40655b8f411c8a8c53f9ff0abf671b0b68767c3 7932 
cloud-sptheme_1.10.1.post20200504175005-4.debian.tar.xz
 a0671d3f440d08fe127f85f9ca6e8d39635fa702 6859 
cloud-sptheme_1.10.1.post20200504175005-4_source.buildinfo
Checksums-Sha256:
 095c3b6e0f220dca2f36ac36f1ab2b5565e53057a49c500f3f4c2187d01532db 1795 
cloud-sptheme_1.10.1.post20200504175005-4.dsc
 50179a23f91ab054d4f0878f604fb0554e919ad3168ef66101fe8a25af07f403 7932 
cloud-sptheme_1.10.1.post20200504175005-4.debian.tar.xz
 be47db0f28a30b502a52ab6445685696ee6a2c3cbc4ca1510ac9abdae3ff2c6e 6859 

Processed: update bts with meta info

[Debian Bug Tracking System]

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

> reassign 1001855 src:node-domino 2.1.6~ds-1
Bug #1001855 [src:eslint, src:node-domino] eslint breaks node-domino 
autopkgtest: Cannot find module 'js-yaml'
Bug reassigned from package 'src:eslint, src:node-domino' to 'src:node-domino'.
No longer marked as found in versions node-domino/2.1.6~ds-1 and 
eslint/5.16.0~dfsg+~4.16.8-9.
Ignoring request to alter fixed versions of bug #1001855 to the same values 
previously set
Bug #1001855 [src:node-domino] eslint breaks node-domino autopkgtest: Cannot 
find module 'js-yaml'
Marked as found in versions node-domino/2.1.6~ds-1.
> affects 1001855 src:eslint
Bug #1001855 [src:node-domino] eslint breaks node-domino autopkgtest: Cannot 
find module 'js-yaml'
Added indication that 1001855 affects src:eslint
> thanks
Stopping processing here.

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

Processed: Bug#1001855 marked as pending in node-domino

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1001855 [src:eslint, src:node-domino] eslint breaks node-domino 
autopkgtest: Cannot find module 'js-yaml'
Added tag(s) pending.

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

Bug#1001855: marked as pending in node-domino

[Yadd]

Control: tag -1 pending

Hello,

Bug #1001855 in node-domino 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-domino/-/commit/07cb1c77570969bf3258c6776e84730cd6752e2d


Add test dependency to node-js-yaml

Closes: #1001855


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1001855

Processed: Bug#1001243 marked as pending in cloud-sptheme

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1001243 [src:cloud-sptheme] cloud-sptheme: autopkgtest needs update for 
new version of python3-defaults: python3.10: not found
Added tag(s) pending.

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

Bug#1001243: marked as pending in cloud-sptheme

[Stefano Rivera]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/cloud-sptheme/-/commit/7194dedfa8402ec820f8c6e0d2570b29f7f38582


autopkgtest: Depend on python3-all. (Closes: #1001243)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1001243

Bug#1001855: eslint breaks node-domino autopkgtest: Cannot find module 'js-yaml'

[Paul Gevers]

Source: eslint, node-domino
Control: found -1 eslint/5.16.0~dfsg+~4.16.8-9
Control: found -1 node-domino/2.1.6~ds-1
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
eslint from testing5.16.0~dfsg+~4.16.8-9
node-dominofrom testing2.1.6~ds-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. Is this 
pointing at a missing (test) dependency somewhere?


Currently this regression is blocking the migration of eslint 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

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

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-domino/17644607/log.gz

There was a problem loading formatter: ./formatters/tap
Error: Cannot find module 'js-yaml'
Require stack:
- /usr/share/nodejs/eslint/lib/formatters/tap.js
- /usr/share/nodejs/eslint/lib/cli-engine.js
- /usr/share/nodejs/eslint/lib/cli.js
- /usr/share/nodejs/eslint/bin/eslint.js
autopkgtest [12:10:53]: test command2



OpenPGP_signature
Description: OpenPGP digital signature

Processed: eslint breaks node-domino autopkgtest: Cannot find module 'js-yaml'

[Debian Bug Tracking System]

Processing control commands:

> found -1 eslint/5.16.0~dfsg+~4.16.8-9
Bug #1001855 [src:eslint, src:node-domino] eslint breaks node-domino 
autopkgtest: Cannot find module 'js-yaml'
Marked as found in versions eslint/5.16.0~dfsg+~4.16.8-9.
> found -1 node-domino/2.1.6~ds-1
Bug #1001855 [src:eslint, src:node-domino] eslint breaks node-domino 
autopkgtest: Cannot find module 'js-yaml'
Marked as found in versions node-domino/2.1.6~ds-1.

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

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

[Debian Bug Tracking System]

Your message dated Fri, 17 Dec 2021 19:03:30 +
with message-id 
and subject line Bug#999242: fixed in authbind 2.1.3
has caused the Debian Bug report #999242,
regarding authbind: 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.)


-- 
999242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999242
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: authbind
Version: 2.1.2
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 ---
Source: authbind
Source-Version: 2.1.3
Done: Ian Jackson 

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

Debian distribution maintenance software
pp.
Ian Jackson  (supplier of updated authbind 
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: Fri, 17 Dec 2021 18:34:02 +
Source: authbind
Architecture: source
Version: 2.1.3
Distribution: unstable
Urgency: medium
Maintainer: Ian Jackson 
Changed-By: Ian Jackson 
Closes: 999242
Changes:
 authbind (2.1.3) unstable; urgency=medium
 .
   * debian/rules: add newly required targets, and reorder/tidy.
 Closes: #999242.
Checksums-Sha1:
 fce1ced8770efc186e26d6a73f4eef368a9baaaf 1131 authbind_2.1.3.dsc
 6198a9ae97a59d508f1e0d535ca9e0694d2e1c9b 15215 authbind_2.1.3.tar.gz
Checksums-Sha256:
 f7365e4a4378c7fd0c615791dc69711b81d6773885eb2060adf9a085e66e526f 1131 
authbind_2.1.3.dsc
 0f5c70aa5e3b09497fa2f93992aef33872f5a4d50d68040534f7a9751cc579b7 15215 
authbind_2.1.3.tar.gz
Files:
 f10668a88358bb1169b2095a1b8b4e20 1131 utils optional authbind_2.1.3.dsc
 25522828332ee39a78f3cee91a38ed2b 15215 utils optional authbind_2.1.3.tar.gz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEVZrkbC1rbTJl58uh4+M5I0i1DTkFAmG82FkACgkQ4+M5I0i1
DTlYJQgAgjI30TdTaf8dr4L/zYuTbfSedJGy4Q2SYOfoEnWqVMadi5SanXbfiEFG
rUy9DD4DGrzXHXo9eAo5XyEbIsipKjbBH+0C+Vw+BCD0/c/59OG2IjfDB9L3VY39
Q1LmjvYK617D6uMx+X2o3OL76gfyI+tb6j0vbxpcQ45UOgJeAhEvlgt51XK7Zq1F
ZvUKQ3bxg3kH3f5IhPha2C39XtxmepjUDg6AWazX0zm4NEmHvECrNag02IK4gAXz
x7bvo09/KqylkKvemVi5J+wA8fJuz5LfwSArhGxHH3gGHVeSqL1EjTHzEr4hreMi
iFqcm1d09At2MCtD/0MlnMPSl5CyVA==
=a8hT
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

Your message dated Fri, 17 Dec 2021 18:49:59 +
with message-id 
and subject line Bug#999188: fixed in vtwm 5.4.7-6
has caused the Debian Bug report #999188,
regarding vtwm: 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.)


-- 
999188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999188
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vtwm
Version: 5.4.7-5
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 ---
Source: vtwm
Source-Version: 5.4.7-6
Done: Ian Jackson 

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

Debian distribution maintenance software
pp.
Ian Jackson  (supplier of updated vtwm 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: Fri, 17 Dec 2021 18:20:38 +
Source: vtwm
Architecture: source
Version: 5.4.7-6
Distribution: unstable
Urgency: medium
Maintainer: Ian Jackson 
Changed-By: Ian Jackson 
Closes: 999188
Changes:
 vtwm (5.4.7-6) unstable; urgency=medium
 .
   * switch to dh(1); now provides newly required rules targets.
 Closes: #999188.
Checksums-Sha1:
 202797c8448a217f81474a003fc1f5956e0401d3 1565 vtwm_5.4.7-6.dsc
 e1c825db1c41379bc9037ee85c227a9888cf50e9 18316 vtwm_5.4.7-6.diff.gz
Checksums-Sha256:
 d7e1d8b0488ddc6cd141a28b93571fb0fc3fbc3627e485ffd32a61ef3c6bbb50 1565 
vtwm_5.4.7-6.dsc
 cf0ac56b29312dd846f689992b4d96b8decee1e777ce7e4f611bb2a265548019 18316 
vtwm_5.4.7-6.diff.gz
Files:
 4759eed3efcdfb2adf818996541fd490 1565 x11 optional vtwm_5.4.7-6.dsc
 f3cd3fe2542b37338f8fe6b7778b9090 18316 x11 optional vtwm_5.4.7-6.diff.gz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEVZrkbC1rbTJl58uh4+M5I0i1DTkFAmG81UMACgkQ4+M5I0i1
DTnUKwf/UTjxxCLim1L3gaMeGNPAz9b4CLKJlDhwJFmf5OvfiFqj+TIIAQjDwoZq
Ei9CMV4rZ/+qKXihfJruma6TSxLMWKlcSNNQ5cG8o7xVTKZNvbR9M8QYp2PKhMW9
/F4HPMr+q5So8UN6Pr8SDJYpdUI6zQyGo9IAknJtJ8E47MPX86K6i+n8nXUNIJI2
Ojl+m282M1QSatUNMgmhRcgwXLbMJK56LUW/nKybqT4Xa90cy9LwibfE0HsW26fm
dxxu49KAo91q7Sn506ujF2USlMuwB5RbA4Ms8CJpEKLNfZqSqV1OYQlSnADV/eWn
IPKCKbe6hlw8Wt6gVKauniBN5UbU0w==
=YAYZ
-END PGP SIGNATURE End Message ---

Bug#1001242: marked as done (weex FTBFS: dh_testroot: error: You must run this as root (or use fakeroot).)

[Debian Bug Tracking System]

Your message dated Fri, 17 Dec 2021 18:34:11 +
with message-id 
and subject line Bug#1001242: fixed in weex 2.8.4.1
has caused the Debian Bug report #1001242,
regarding weex FTBFS: dh_testroot: error: You must run this as root (or use 
fakeroot).
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.)


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

https://buildd.debian.org/status/logs.php?pkg=weex=2.8.4

...
# Add here commands to compile the package.
#/usr/bin/make prefix=`pwd`/debian/weex/usr
touch build-stamp
dh_testdir
dh_testroot
dh_testroot: error: You must run this as root (or use fakeroot).
make: *** [debian/rules:37: install] Error 25
--- End Message ---
--- Begin Message ---
Source: weex
Source-Version: 2.8.4.1
Done: Ludovic Drolez 

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

Debian distribution maintenance software
pp.
Ludovic Drolez  (supplier of updated weex 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: Fri, 17 Dec 2021 17:22:40 +0100
Source: weex
Architecture: source
Version: 2.8.4.1
Distribution: unstable
Urgency: medium
Maintainer: Ludovic Drolez 
Changed-By: Ludovic Drolez 
Closes: 1001242
Changes:
 weex (2.8.4.1) unstable; urgency=medium
 .
   * Fixed a stupid build typo. Closes: #1001242
Checksums-Sha1:
 e92c13d8f89277c12aea49c9f20e93d4f50ee370 1095 weex_2.8.4.1.dsc
 fc899c1d080a90d4a410bf602de314d890e8f583 337389 weex_2.8.4.1.tar.gz
 48eb460667bf3632f221bfc8d44d883ade1c0f50 6235 weex_2.8.4.1_amd64.buildinfo
Checksums-Sha256:
 d0703cc0866dfc18ae003f0cd3d4a7a97e789b1949ac02916fa2816a5b11857d 1095 
weex_2.8.4.1.dsc
 f7546c28b9fe1ba75ef5fa68e7a80fd49714ffee2dbcc3df3d675acf09fc6354 337389 
weex_2.8.4.1.tar.gz
 9ae030c982ac6b4b925618c7174fe9808f82000fec40ac5b2c91ce8e49af1cae 6235 
weex_2.8.4.1_amd64.buildinfo
Files:
 aff599351c4aa90fe362956bd6eaae79 1095 net optional weex_2.8.4.1.dsc
 849ffbae034a51b5c30c132a39d97f7b 337389 net optional weex_2.8.4.1.tar.gz
 b1bc41638a67d4b19bba9da1f6278535 6235 net optional weex_2.8.4.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQFHBAEBCAAxFiEEKrWNbKjxjlSqtxlZi3UoEkf5wXwFAmG80gATHGxkcm9sZXpA
ZGViaWFuLm9yZwAKCRCLdSgSR/nBfM2RB/48Q2SFk1vm6KifZJq1sAhFRiy2923r
FGbwLd0bFzsSD65+taDZ+PBpX08mgw9BJzZIV8Kel2dqA+0lj6SnAnsM7wWacAuF
IlwqUVPomvbOP40vxfpoEX79cZwp8uisi4W3cSMeSdqtOuKBgQvWG1HjSt+0wwhs
s7JRjCopfrp1c5qF+LNyBvJ5TqpsDgiWYXf/9uL/IN0ZVMEoq8KfCx5h3/T3N30b
Wqt7ZqRckVOJlxVJchGyz3iSK7CDF21YjEq0Lff0qwxo1BICUpkEuTCfqGSMDPzD
ZaRf/hXUoQuagEuM5sBSoQJj+eZ1FewDjeXkU79ECL4ZVMIbTqAbttfq
=qIXQ
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

Your message dated Fri, 17 Dec 2021 17:51:56 +
with message-id 
and subject line Bug#999279: fixed in swish-e 2.4.7-6.1
has caused the Debian Bug report #999279,
regarding swish-e: 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.)


-- 
999279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999279
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: swish-e
Version: 2.4.7-6
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 ---
Source: swish-e
Source-Version: 2.4.7-6.1
Done: Damyan Ivanov 

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

Debian distribution maintenance software
pp.
Damyan Ivanov  (supplier of updated swish-e package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 16 Dec 2021 07:52:44 +
Source: swish-e
Architecture: source
Version: 2.4.7-6.1
Distribution: unstable
Urgency: medium
Maintainer: Ludovic Drolez 
Changed-By: Damyan Ivanov 
Closes: 999279
Changes:
 swish-e (2.4.7-6.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * add build-arch and build-inde targets to debian/rules (Closes: #999279)
Checksums-Sha1: 
 c3099ec605aee833ce013aec4d3a4947664591ae 1784 swish-e_2.4.7-6.1.dsc
 e4d545726fd01e831e3cbfa55d1216f6b7f8ba5a 31639 swish-e_2.4.7-6.1.diff.gz
Checksums-Sha256: 
 92d9c5a8b923778fb8fa60b09eb07b6e337a7a4e78272cbd888f65336e317355 1784 
swish-e_2.4.7-6.1.dsc
 26669d86c6dd6ce66c18e46ce9614ec6845de154a24cc33bb2733ca52b91dc23 31639 
swish-e_2.4.7-6.1.diff.gz
Files: 
 20ac42af5597c52a258bded44d976edd 1784 web optional swish-e_2.4.7-6.1.dsc
 740af4712da0801a7704f893c3da0d4e 31639 web optional swish-e_2.4.7-6.1.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErqDETssFbpNjDZ0z276dTZnSoAQFAmG68MYACgkQ276dTZnS
oATq/w//SPDWrF7ndu8PC0+8yqQf3w6S2IAkpaDd33hT/Sk/nVrWIYfNkMqEI6hU
mAWCrBIRLutpSrFojAriKe/ojDyQcDLQTqJTSD0rms5s8pzsB86k9pbCBZZaXE6f
XCb6wQ18FMCBpVoVYu8rc/WPMJrbGkh1wdXtZtQslG691B8BZ0BktUbO3F1NZo8K
Kj+R1UAXt8WDSsBjA+KEWDO2BMKiM/mN9M6bl9KfI6q/XH0opOwKRYguCLbVarjp
9LY0JbdJeoxTBxloIXbB9/lbUj9/pw/E8x8f6MMeW+nrrdTFohiMYwkvPt9mRSmE
g8k+x46uieDtT3sZRhfbRcgXQcHFdpfyAM9ZEBpvQ0fTkDBythwt6bEI3mFPM+mU
fPr+QJhLfRDy/RrxOWZ4F6Enqm0paaeFvxwc5jUBoQRB6+B3cn9z7mI3DUb8Efwm
Op+LzxPouUeif2n/iOvB1NwP/F4Lka6hUn+6KkGvDAHFsZX1Ck63+BL2Z/oQBUkC
ZU0QdHfV0Os6uI4qnP0g2iDCZT8r25UA3mYvH/r94o10qHas3IwQNWW4TlsdOZno
W5wIq7l6MXe+CQeQgWDNZ8Ujo5yqja79yKW6XQte3wkbHyz5X+FVLt5F9/f0C/ym
0XwpSLW5XiaZuQI/HANnFrekVHskVHTwYrd/uf/tyls/UVCP/0E=
=erTr
-END PGP SIGNATURE End Message ---

Bug#999279: swish-e: diff for NMU version 2.4.7-6.1

[Damyan Ivanov]

-=| Ludovic Drolez, 17.12.2021 16:20:53 +0100 |=-
> On Thu, Dec 16, 2021 at 07:56:50AM +, Damyan Ivanov wrote:
> > I've prepared an NMU for swish-e (versioned as 2.4.7-6.1) and
> > uploaded it to DELAYED/7. Please feel free to tell me if I
> > should delay it longer.
> > 
> 
> That's perfect, thanks for your help!

Glad to be of service. Upload rescheduled to DELAYED/0 and should 
enter the archive within a day.

Cheers!
dam

Bug#1001823: Re-send patch, bugtracker messed up spaces

[Jens Rottmann]

Turns out bugtracker messes up whitespace in text/patch attachments. :(
Re-attaching same patch, but gziped, hoping it's left intact now.


python3fix.patch.gz
Description: application/gzip

Processed: Re: booth: intermittent autopkgtest failures

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #994794 {Done: Valentin Vidic } [src:booth] booth: 
intermittent autopkgtest failures
Added tag(s) patch.

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

Bug#994794: booth: intermittent autopkgtest failures

[Simon Chopin]

Package: booth
Followup-For: Bug #994794
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
X-Debbugs-Cc: simon.cho...@canonical.com
Control: tags -1 patch

In Ubuntu, the attached patch was applied on top of the fix, as the
online node doesn't necessarily contain the 'node1' string in the name.
I'm guessing it depends on the configuration of the autopkgtest runners.

For instance, here is the output of the crm status command in my
LXC-based local runner.

```
Cluster Summary:
  * Stack: corosync
  * Current DC: autopkgtest-lxc-fisgca (version 2.0.5-ba59be7122) - partition 
with quorum
  * Last updated: Fri Dec 17 16:56:18 2021
  * Last change:  Fri Dec 17 16:55:54 2021 by hacluster via crmd on 
autopkgtest-lxc-fisgca
  * 1 node configured
  * 0 resource instances configured

Node List:
  * Online: [ autopkgtest-lxc-fisgca ]

Full List of Resources:
  * No resources
```

Cheers,
Simon Chopin
diff -Nru booth-1.0-237-gdd88847/debian/tests/pacemaker 
booth-1.0-237-gdd88847/debian/tests/pacemaker
--- booth-1.0-237-gdd88847/debian/tests/pacemaker   2021-09-22 
22:33:36.0 +0200
+++ booth-1.0-237-gdd88847/debian/tests/pacemaker   2021-12-17 
17:49:22.0 +0100
@@ -28,7 +28,7 @@
 start_service corosync
 start_service pacemaker
 n=0
-while ! crm status | grep 'Online:.*node1'; do
+while ! crm status | grep "\\* Online: "; do
   test "$n" -lt 120
   sleep 1
   n=$((n+1))

Bug#1001770: marked as done (libgmsh4.8: needs Breaks+Replaces: libgmsh4 (>= 4.8))

[Debian Bug Tracking System]

Your message dated Fri, 17 Dec 2021 16:49:05 +
with message-id 
and subject line Bug#1001770: fixed in gmsh 4.8.4+ds2-2
has caused the Debian Bug report #1001770,
regarding libgmsh4.8: needs Breaks+Replaces: libgmsh4 (>= 4.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.)


-- 
1001770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001770
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgmsh4
Version: 4.8.4+ds2-1
Severity: serious

Unpacking libgmsh4.8:amd64 (4.8.4+ds2-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-g8oaD4/13-libgmsh4.8_4.8.4+ds2-1_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libgmsh.so.4.8.4', which is 
also in package libgmsh4:amd64 4.8.4+ds1-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
--- End Message ---
--- Begin Message ---
Source: gmsh
Source-Version: 4.8.4+ds2-2
Done: Anton Gladky 

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated gmsh package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 16 Dec 2021 21:45:43 +0100
Source: gmsh
Architecture: source
Version: 4.8.4+ds2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Closes: 1001770
Changes:
 gmsh (4.8.4+ds2-2) unstable; urgency=medium
 .
   * [a3b3547] Add Breaks+Replaces: libgmsh4. (Closes: #1001770)
   * [9a78c7e] Avoid explicitly specifying -Wl,--as-needed linker flag.
Checksums-Sha1:
 c3f9cfed173b13682efc4fdbeebfd6757be3e348 2835 gmsh_4.8.4+ds2-2.dsc
 4337f4a09da92ea1ae422c39ea9bed08df2e0680 24348 gmsh_4.8.4+ds2-2.debian.tar.xz
 5ec1604f168aaecb4ac8707e89049c8a2d6e967c 9933 gmsh_4.8.4+ds2-2_source.buildinfo
Checksums-Sha256:
 d7882ff3573577250168e5e55b88e66b136d69af72137702875e4cc5e210fce8 2835 
gmsh_4.8.4+ds2-2.dsc
 3b62969c0016145917a3a5cafcde8fff41fa88947f445d7829393fe93da46e24 24348 
gmsh_4.8.4+ds2-2.debian.tar.xz
 2927dc9e79fbb6552d7984646bc5598d88ee3a988beacac1ff01c6ccca63acf9 9933 
gmsh_4.8.4+ds2-2_source.buildinfo
Files:
 b1f5b8c0a28197f2ab8880bb290a22bc 2835 math optional gmsh_4.8.4+ds2-2.dsc
 f43c5103d93ce68fb98836a3e99fd7a4 24348 math optional 
gmsh_4.8.4+ds2-2.debian.tar.xz
 d162ddea99a42fc5011e852deb36c5b4 9933 math optional 
gmsh_4.8.4+ds2-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAmG7pbIACgkQ0+Fzg8+n
/wbc7g/9GSOvrfnkeXu2cRZ3ix8gW0YvJ+kNUw8CrdPZUA4uAI8P5qAYwkgqoMim
Id1Fb9KhcrSqdTujaC0a4cTtwT24dI+oPYCxjVcaEQ/ryp1jf9yjI3fY2y4oRRTn
M4KkI1NO5Q4z+JJ15Pyfr+FiGIadd8PJ9w7AO/AAtQfo+0pxRJ0l076KSR81isD8
fadx3ODHN3apqegfAootse15UElYVg64o1IsVeS9C8HJUYLsrsA6x7jXmdxLq+6e
JHZTAMf/vnniG/2a0vPCFKV923AdewSTP27JdzXkbpjXHHz7HQ7luGCuSf4LqBGu
VF0gB4GCwG0Wuf7OWoFOiLHe2pj9EwjDc7gk7Yx9PWVbdJAdRpiGBffyRe7HykYA
1jFLSQX/piGhKwVjiVVdVoklJKaYHHzMNXgD5j6DGMfrlFstsEZfdD7ChJJXg53n
gzlKyFE0wEtx5u+eWkC9Q3quqmklr+NQzTLxYPD+mRhbFAYseiE4+5U/uhZqYxFK
LneIQE1BovxlqdxH5RPSjUyCL/aoIYK40vaGPOJB13jeISZK/s2pNOIs+nC7uW2E
g4tuy1c/cu4aTr3gQJuQot6A5eijetddoXRxLS7PCzzkE59gsLqWaQoPGHzSxoE7
tvi9sOuHWqD7lV3TcfBgj2yfXtDxenpu2PEQMYuoa5gJ9ceMA1I=
=o8qt
-END PGP SIGNATURE End Message ---

Bug#1001823: Improved patch

[Jens Rottmann]

My fix removes the only occurrence of cmp() in magic.py, so we should drop the 
line importing past.builtins.cmp. Updated patch accordingly, also improved 
commit message.

Attached patch v2, hoping bugtracker can handle attachments.
Python 3 port introduced at least five severe bugs.

* Customizing action keys via Options, Control prints 2 deprecation warnings
  and no longer works, changed keys aren't saved. Not being able to remap
  keys makes it hard for users of non-English keyboards. (controls.py)
* Playing as Nyx and casting Ice ([D][S]) or Implosion ([D][W]) instantly
  crashes the game due to 3 exceptions. (magic.py)
* Playing as Pyralis and using Spin-slash ([C][S]) hangs gameplay, you have
  to abort the current level to be able to move again. (play_level.py)

Bug-Debian: https://bugs.debian.org/1001823
Signed-off-by: Jens Rottmann

--- ardentryst/controls.py
+++ python3fix/controls.py
@@ -35,7 +35,7 @@
 class SET2:
 def __init__(self, keycodes, x, y, set):
 self.set = set
-self.keys = [Key(keycodes[c], x + ((8-c)%3) * 32, y + (c/3)*30, "B-" + str(((11-c)/3)*3 - (11-c)%3), set) for c in range(9)]
+self.keys = [Key(keycodes[c], x + ((8-c)%3) * 32, y + (c//3)*30, "B-" + str(((11-c)//3)*3 - (11-c)%3), set) for c in range(9)]

 class Key:
 def __init__(self, keycode, x, y, binding, set):
--- ardentryst/magic.py
+++ python3fix/magic.py
@@ -21,7 +21,6 @@

 import pygame, math, random
 from pygame.locals import *
-from past.builtins import cmp

 def ground_at(LEVEL, x, f=False):
 "Finds the y co-ordinate of the ground at position x."
@@ -236,7 +235,7 @@ class Ice_1(Spell):
 def s_init(self):
 global DATA
 self.affected = []
-self.cant = self.caster.mp < 4
+self.cant = self.caster.mp[0] < 4
 def s_blit(self, surf, ALT_X, ALT_Y):
 global DATA
 if not self.affected:
@@ -441,7 +440,7 @@ class Implosion_1(Spell):
 def s_init(self):
 global DATA
 self.affected = []
-self.cant = self.caster.mp < 15
+self.cant = self.caster.mp[0] < 15
 def s_blit(self, surf, ALT_X, ALT_Y):
 global DATA
 pic = DATA.mag_images["bubble.png"][0]
@@ -472,7 +471,7 @@ class Implosion_1(Spell):
 if self.caster.mp[0] >= 15:
 self.affected.append(monster)

-self.affected.sort(lambda x, y: cmp(y.maxhp, x.maxhp))
+self.affected.sort(key=lambda x: -x.maxhp)

 if len(self.affected):
 self.affected = self.affected[:1]
--- ardentryst/play_level.py
+++ python3fix/play_level.py
@@ -4727,7 +4727,7 @@ class Character:
 self.mycombotime -= 1
 if self.chainmove[1] and self.chainmove[1] > 0:
 self.chainmove[1] -= 1
-if self.chainmove[1] and self.chainmove[1] == 0:
+if self.chainmove[1] == 0:
 cm = self.chainmove[:]
 self.chainmove = [None, None]
 getattr(self, cm[0])()
--

Processed: Re: libgmsh4.8: needs Breaks+Replaces: libgmsh4 (>= 4.8)

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libgmsh4.8 4.8.4+ds1-1
Bug #1001770 [libgmsh4] libgmsh4 needs Breaks+Replaces: libgmsh4 (>= 
4.8.4+ds1-1~)
Bug reassigned from package 'libgmsh4' to 'libgmsh4.8'.
No longer marked as found in versions 4.8.4+ds2-1.
Ignoring request to alter fixed versions of bug #1001770 to the same values 
previously set
Bug #1001770 [libgmsh4.8] libgmsh4 needs Breaks+Replaces: libgmsh4 (>= 
4.8.4+ds1-1~)
There is no source info for the package 'libgmsh4.8' at version '4.8.4+ds1-1' 
with architecture ''
Unable to make a source version for version '4.8.4+ds1-1'
Marked as found in versions 4.8.4+ds1-1.
> retitle -1 libgmsh4.8: needs Breaks+Replaces: libgmsh4 (>= 4.8)
Bug #1001770 [libgmsh4.8] libgmsh4 needs Breaks+Replaces: libgmsh4 (>= 
4.8.4+ds1-1~)
Changed Bug title to 'libgmsh4.8: needs Breaks+Replaces: libgmsh4 (>= 4.8)' 
from 'libgmsh4 needs Breaks+Replaces: libgmsh4 (>= 4.8.4+ds1-1~)'.

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

Bug#1001770: libgmsh4.8: needs Breaks+Replaces: libgmsh4 (>= 4.8)

[Andreas Beckmann]

Followup-For: Bug #1001770
Control: reassign -1 libgmsh4.8 4.8.4+ds1-1
Control: retitle -1 libgmsh4.8: needs Breaks+Replaces: libgmsh4 (>= 4.8)

libgmsh4.8 is the new package and co-installable with libgmsh4 4.7.* in
stable, thus the a bit unusual (>= 4.8) relation to only break the bad
version in sid.

Andreas

Bug#1001844: sdformat9-doc: ships /usr/share/doc/sdformat-doc/html/jquery.js

[Andreas Beckmann]

Package: sdformat9-doc
Version: 9.6.1+ds1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

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

  Preparing to unpack .../sdformat9-doc_9.6.1+ds1-1_all.deb ...
  Unpacking sdformat9-doc (9.6.1+ds1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/sdformat9-doc_9.6.1+ds1-1_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/sdformat-doc/html/jquery.js', which is 
also in package sdformat-doc 12.0.0+ds-1
  Errors were encountered while processing:
   /var/cache/apt/archives/sdformat9-doc_9.6.1+ds1-1_all.deb

/usr/share/doc/sdformat-doc/html/jquery.js should rather be in 
.../sdformat*9*-doc/...


cheers,

Andreas


sdformat-doc=12.0.0+ds-1_sdformat9-doc=9.6.1+ds1-1.log.gz
Description: application/gzip

Bug#999279: swish-e: diff for NMU version 2.4.7-6.1

[Ludovic Drolez]

On Thu, Dec 16, 2021 at 07:56:50AM +, Damyan Ivanov wrote:
> Control: tags 999279 + patch
> Control: tags 999279 + pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for swish-e (versioned as 2.4.7-6.1) and
> uploaded it to DELAYED/7. Please feel free to tell me if I
> should delay it longer.
> 

Hi!

That's perfect, thanks for your help!

-- 
Ludovic

https://isabelleantoine.be   - Coaching Gestion du Stress

Bug#993379: libyami-utils FTBFS: error: ‘void av_init_packet(AVPacket*)’ is deprecated [-Werror=deprecated-declarations]

[Simon Chopin]

Package: libyami-utils
Version: 1.3.0-3
Followup-For: Bug #993379
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
X-Debbugs-Cc: simon.cho...@canonical.com
Control: tags -1 patch

Hi,

In Ubuntu, the attached patch was applied to fix the aforementioned
FTBFS:

Thanks for considering the patch.

Cheers,
Simon
diff -Nru 
libyami-utils-1.3.0/debian/patches/0004-tests-decodeinputavformat-use-heap-allocated-m_packe.patch
 
libyami-utils-1.3.0/debian/patches/0004-tests-decodeinputavformat-use-heap-allocated-m_packe.patch
--- 
libyami-utils-1.3.0/debian/patches/0004-tests-decodeinputavformat-use-heap-allocated-m_packe.patch
  1970-01-01 01:00:00.0 +0100
+++ 
libyami-utils-1.3.0/debian/patches/0004-tests-decodeinputavformat-use-heap-allocated-m_packe.patch
  2021-12-17 15:50:51.0 +0100
@@ -0,0 +1,85 @@
+From dbd0c5508d0084a9b069cafd583e6004a12f562a Mon Sep 17 00:00:00 2001
+From: Simon Chopin 
+Date: Fri, 17 Dec 2021 16:03:10 +0100
+Subject: [PATCH] tests/decodeinputavformat: use heap-allocated m_packet
+Forwarded: https://github.com/intel/libyami-utils/pull/138
+
+This allows us to migrate away from av_init_packet() which has been
+deprecated in recent FFMpeg, making the build fail.
+
+This implementation is somewhat rough, there's probably a way to avoid
+reallocating the packet each iteration, but it does the job.
+---
+ tests/decodeinputavformat.cpp | 23 +--
+ tests/decodeinputavformat.h   |  2 +-
+ 2 files changed, 10 insertions(+), 15 deletions(-)
+
+--- a/tests/decodeinputavformat.cpp
 b/tests/decodeinputavformat.cpp
+@@ -22,18 +22,12 @@
+ #include "common/log.h"
+ #include 
+ 
+-#if LIBAVCODEC_VERSION_INT < AV_VERSION_INT(55, 39, 100)
+-#define av_packet_unref av_free_packet
+-#endif
+-
+ DecodeInputAvFormat::DecodeInputAvFormat()
+-:m_format(NULL),m_videoId(-1), m_codecId(AV_CODEC_ID_NONE), m_isEos(true)
++:m_format(NULL),m_videoId(-1), m_codecId(AV_CODEC_ID_NONE), 
m_packet(av_packet_alloc()), m_isEos(true)
+ {
+ #if LIBAVFORMAT_VERSION_INT < AV_VERSION_INT(58, 9, 100)
+ av_register_all();
+ #endif
+-
+-av_init_packet(_packet);
+ }
+ 
+ bool DecodeInputAvFormat::initInput(const char* fileName)
+@@ -132,18 +126,19 @@
+ int ret;
+ while (1) {
+ //free old packet
+-av_packet_unref(_packet);
++av_packet_free(_packet);
++m_packet = av_packet_alloc();
+ 
+-ret = av_read_frame(m_format, _packet);
++ret = av_read_frame(m_format, m_packet);
+ if (ret) {
+ m_isEos = true;
+ return false;
+ }
+-if (m_packet.stream_index == m_videoId) {
++if (m_packet->stream_index == m_videoId) {
+ memset(, 0, sizeof(inputBuffer));
+-inputBuffer.data = m_packet.data;
+-inputBuffer.size = m_packet.size;
+-inputBuffer.timeStamp = m_packet.dts;
++inputBuffer.data = m_packet->data;
++inputBuffer.size = m_packet->size;
++inputBuffer.timeStamp = m_packet->dts;
+ return true;
+ }
+ }
+@@ -158,8 +153,8 @@
+ DecodeInputAvFormat::~DecodeInputAvFormat()
+ {
+ if (m_format) {
+-av_packet_unref(_packet);
+ avformat_close_input(_format);
+ }
++av_packet_free(_packet);
+ 
+ }
+--- a/tests/decodeinputavformat.h
 b/tests/decodeinputavformat.h
+@@ -47,7 +47,7 @@
+ AVFormatContext* m_format;
+ int m_videoId;
+ AVCodecID m_codecId;
+-AVPacket m_packet;
++AVPacket* m_packet;
+ bool m_isEos;
+ string m_codecData;
+ };
diff -Nru libyami-utils-1.3.0/debian/patches/av_packet_init-deprecated.patch 
libyami-utils-1.3.0/debian/patches/av_packet_init-deprecated.patch
--- libyami-utils-1.3.0/debian/patches/av_packet_init-deprecated.patch  
1970-01-01 01:00:00.0 +0100
+++ libyami-utils-1.3.0/debian/patches/av_packet_init-deprecated.patch  
2021-12-17 15:48:08.0 +0100
@@ -0,0 +1,61 @@
+Description: Migrate away from the deprecated av_packet_init API
+Author: Simon Chopin 
+
+--- a/tests/decodeinputavformat.cpp
 b/tests/decodeinputavformat.cpp
+@@ -33,7 +33,7 @@
+ av_register_all();
+ #endif
+ 
+-av_init_packet(_packet);
++m_packet = av_packet_alloc();
+ }
+ 
+ bool DecodeInputAvFormat::initInput(const char* fileName)
+@@ -132,18 +132,19 @@
+ int ret;
+ while (1) {
+ //free old packet
+-av_packet_unref(_packet);
++av_packet_free(_packet);
++m_packet = av_packet_alloc();
+ 
+-ret = av_read_frame(m_format, _packet);
++ret = av_read_frame(m_format, m_packet);
+ if (ret) {
+ m_isEos = true;
+ return false;
+ }
+-if (m_packet.stream_index == m_videoId) {
++if (m_packet->stream_index == m_videoId) {
+ memset(, 0, sizeof(inputBuffer));
+-inputBuffer.data = m_packet.data;
+-inputBuffer.size = m_packet.size;
+-inputBuffer.timeStamp 

Processed: Re: libyami-utils FTBFS: error: ‘void av_init_packet(AVPacket*)’ is deprecated [-Werror=deprecated-declarations]

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #993379 [src:libyami-utils] libyami-utils FTBFS: error: ‘void 
av_init_packet(AVPacket*)’ is deprecated [-Werror=deprecated-declarations]
Added tag(s) patch.

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

Bug#1001719: marked as done (jenkins-job-builder: autopkgtest needs update for new version of setuptools: deprecation warning on stderr)

[Debian Bug Tracking System]

Your message dated Fri, 17 Dec 2021 15:03:43 +
with message-id 
and subject line Bug#1001719: fixed in jenkins-job-builder 3.11.0-2
has caused the Debian Bug report #1001719,
regarding jenkins-job-builder: autopkgtest needs update for new version of 
setuptools: deprecation warning on stderr
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.)


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

Source: jenkins-job-builder
Version: 3.11.0-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, setupto...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:setuptools

Dear maintainer(s),

With a recent upload of setuptools the autopkgtest of 
jenkins-job-builder fails in testing when that autopkgtest is run with 
the binary packages of setuptools from unstable. It passes when run with 
only packages from testing. In tabular form:


   passfail
setuptools from testing59.4.0-1
jenkins-job-builderfrom testing3.11.0-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. The test fails 
because there is a deprecation warning on stderr and the allow-stderr 
restriction is not set on the autopkgtest.


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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/j/jenkins-job-builder/17554110/log.gz

Testing with python3.9:
{3} 
tests.cachestorage.test_cachestorage.TestCaseJobCache.test_save_on_exit 
[0.004601s] ... ok
{3} 
tests.jenkins_manager.test_manager.TestCaseTestJenkinsManager.test_get_plugins_info_handles_connectionrefused_errors 
[0.004442s] ... ok
{6} 
tests.parallel.test_parallel.TestCaseParallel.test_parallel_single_thread [0.001632s] 
... ok
{6} 
tests.xml_config.test_xml_config.TestXmlJobGeneratorExceptions.test_incorrect_template_params 
[0.026831s] ... ok
{4} 
tests.cmd.subcommands.test_update.UpdateTests.test_update_timeout_set 
... SKIPPED: TODO: Develop actual update timeout test approach.
/usr/lib/python3/dist-packages/pkg_resources/__init__.py:116: 
PkgResourcesDeprecationWarning: 1.0a.preview is an invalid version and 
will not be supported in a future release

  warnings.warn(


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: jenkins-job-builder
Source-Version: 3.11.0-2
Done: Christoph Berg 

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated jenkins-job-builder 
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: Fri, 17 Dec 2021 14:04:59 +0100
Source: jenkins-job-builder
Architecture: source
Version: 3.11.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Christoph Berg 
Closes: 1001719
Changes:
 jenkins-job-builder (3.11.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Fix FTBFS with sphinx 4.3: Changed get_doc() signature.
   * Remove requirements.txt entry that makes dh_python choke.
   * debian/tests/control: Don't barf on deprecation notices emitted by tests.
 (Closes: #1001719)
Checksums-Sha1:
 171ac599f01c73ce5ea123d8e010699631a015d6 2964 jenkins-job-builder_3.11.0-2.dsc
 9bdfad42271905cfe4bbcb9fb62c036e9f7d9fb7 11960 
jenkins-job-builder_3.11.0-2.debian.tar.xz
Checksums-Sha256:
 89f4957fa592d4b6cbf854323467b596e1802ce55170705a9acac78e33e0cec3 2964 

Processed: Re: Bug#1001527: FTBFS with fmtlib 8

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1001527 [src:vast] FTBFS with fmtlib 8
Severity set to 'serious' from 'important'

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

Bug#1001791: marked as done (fonts-cantarell: Renders system hardly usable)

[Debian Bug Tracking System]

Your message dated Fri, 17 Dec 2021 12:22:29 +0100
with message-id 
and subject line Re: Bug#1001791: fonts-cantarell: Renders system hardly usable
has caused the Debian Bug report #1001791,
regarding fonts-cantarell: Renders system hardly usable
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.)


-- 
1001791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001791
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fonts-cantarell
Version: 0.303-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: g...@safe-mail.net

Dear Maintainer,

this version displays only letters a-z correctly thus making the system hardly
usable, unless you change to a different font. The problem is best shown with
the attached screen-shot.

An earlier bug report seems not to have reached Debian's bug tracking system.
If it has, please delete one or merge.

Yours
G. Heine


-- Package-specific info:
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version   Architecture Description
+++-==-=--=
ii  fontconfig 2.13.1-4.2amd64generic font configuration 
library - support binaries
ii  libfreetype6:amd64 2.11.0+dfsg-1 amd64FreeType 2 font engine, 
shared library files
ii  libxft2:amd64  2.3.2-2   amd64FreeType-based font drawing 
library for X

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

Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages fonts-cantarell depends on:
ii  fontconfig  2.13.1-4.2

fonts-cantarell recommends no packages.

fonts-cantarell suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Am Donnerstag, dem 16.12.2021 um 10:58 -0500 schrieb g...@safe-mail.net:
> Hi,
> 
> short answer: no.
> 
> I have to admit that I was so shocked at what I saw that I didn't
> even think of restarting the system. After more than a decade with
> Linux I'm no longer used to restart after upgrading my system. I did
> just now, reset the system fonts to Cantarell and the problem is no
> longer there.
> 
> Regards
> G. Heine

Closing, thanks!
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEIsF2SKlSa4TfGRyWy+qOlwzNWd8FAmG8cvUACgkQy+qOlwzN
Wd/Epg/+PHBwL9F9yBpfIQF0aeGa9bxupYCT4k1T0NB/FZXWDQ7aD/3lvTqeWqwC
+wLPggfR0fwWamru2M41pw0a9uoJyC7H0aiuJeFP+ivIspQibUh9BBgT5j3BgYQq
+0M0kKxOCjrjpIaHn9CytZ7xmJGm7+wTvCXz0xdWkdQBT6kzogVFo4m1xyUD/y+t
nEJcZO29k/AFP++2WGF+K2FleE08YlA4+wcjBLeiaVB1Uvz1QF3pbUBBznolkArE
P6G9rj357OQFCNoR5+W1QRDkRyyDWWEEKnw98aRYkieYUQdpnT5aKU/jxJAn9Zse
FfyWog489/lwgIH99CybAGc8WWY/BtDxE/xswx/PM3qitvkEot1TYi+ocu/LwQcj
XkNiz6MBLZYCCdbUYUty6aQEPad4ZPgg2H8YOBugXOVfg767gRzOxvCM6x1T7UFR
bh4F6VwOQG3Oyyi9r25mkqCjuanEGrP6OAUzJhYIj8qVdpP7EUXDv/ejZ7xz8hqe
inLwfGbkJZLeABIQL3cH71WZtb2iSeQIy+kUZxRPjIJxKipo+zOWRgzCxj5HAh0P
W4FRs6S8hJe7ymgslYazGDGQhjsTSzBbEgQ6BZR2rpOfa6WvdM16ttWXM8rY5/Ae
L8znqshwY/kKO3nFIpbGKi4ZAZr3BkYbCoojfLN7a1xx6cH5yL8=
=vfzG
-END PGP SIGNATURE End Message ---

Bug#1001789: marked as done (r-cran-gplots: package 'gplots' was installed before R 4.0.0: please re-install it)

[Debian Bug Tracking System]

Your message dated Fri, 17 Dec 2021 11:19:03 +0100
with message-id 
and subject line Closing since caused by remainings in 
/usr/local/lib/R/site-library
has caused the Debian Bug report #1001789,
regarding r-cran-gplots: package 'gplots' was installed before R 4.0.0: please 
re-install it
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.)


-- 
1001789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001789
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: r-cran-gplots
Version: 3.1.1-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: debia...@lists.debian.org

Hi,

seems r-cran-gplots has sliped trough in the Transition r-base for 4.0.0
(bug #955211).  This is strange since current r-cran-gplots was uploaded
at 2020-11-29 while the transition bug was closed 2020-10-31 - but anyway
gplots claims to be installed "installed before R 4.0.0" when running on
stable=bullseye (not on testing / unstable):

$ R -e 'library(gplots)'

R version 4.0.4 (2021-02-15) -- "Lost Library Book"
Copyright (C) 2021 The R Foundation for Statistical Computing
Platform: x86_64-pc-linux-gnu (64-bit)

R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.

  Natural language support but running in an English locale

R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.

Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.

> library(gplots)
Error: package or namespace load failed for 'gplots':
 package 'gplots' was installed before R 4.0.0: please re-install it
Execution halted


Kind regards

 Andreas.


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

Kernel: Linux 5.10.0-9-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages r-cran-gplots depends on:
ii  r-base-core [r-api-4.0]  4.0.4-1
ii  r-cran-catools   1.18.1-1
ii  r-cran-gdata 2.18.0-3
ii  r-cran-gtools3.8.2-1+b1
ii  r-cran-kernsmooth2.23-18-1

r-cran-gplots recommends no packages.

r-cran-gplots suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,

I'm closing this bug report since it was caused by an old copy
of the R package in

   /usr/local/lib/R/site-library

Kind regards

 Andreas.

-- 
http://fam-tille.de--- End Message ---

Processed: forcibly merging 947425 973927

[Debian Bug Tracking System]

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

> forcemerge 947425 973927
Bug #947425 [incron] incron crashes in IncronTabEntry::GetSafePath due to 
use-after-free bug
Bug #973927 [incron] incron SEGV when monitoring directories
Set Bug forwarded-to-address to 'https://github.com/ar-/incron/issues/36'.
Marked as found in versions incron/0.5.12-1.
Added tag(s) upstream, security, and patch.
Bug #947425 [incron] incron crashes in IncronTabEntry::GetSafePath due to 
use-after-free bug
Marked as found in versions incron/0.5.12-1+deb10u1.
Merged 947425 973927
> thanks
Stopping processing here.

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

Bug#972211: FTBFS with OCaml 4.11.1 (-unsafe-string is not available)

[Joseph Nuthalapati]

Adding a link to the upstream issue.

-unsafe-string usage
https://github.com/ygrek/mldonkey/issues/46

--
Joseph Nuthalapati

Bug#997627: marked as done (pixmap: FTBFS: ar: libdeps specified more than once)

[Debian Bug Tracking System]

Your message dated Fri, 17 Dec 2021 09:34:06 +
with message-id 
and subject line Bug#997627: fixed in pixmap 2.6.6-1
has caused the Debian Bug report #997627,
regarding pixmap: FTBFS: ar: libdeps specified more than once
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.)


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

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/SelFile'
> rm -f SelFile.o
> gcc -c -g -O2 -fno-strict-aliasing  -I. -I.. -I/usr/include/X11 
> -I/usr/include/-Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L  
> -D_POSIX_SOURCE -D_XOPEN_SOURCE 
> -D_BSD_SOURCE -D_SVID_SOURCE 
> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
>-DFUNCPROTO=15 -DNARROWPROTO -DUSE_ATHENA 
> -DAPPDEFDIR=\"/etc/X11/app-defaults\"   
> -DRGBF=\"/etc/X11/rgb.txt\"   SelFile.c
> In file included from 
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
>  from /usr/include/stdio.h:27,
>  from SelFile.c:46:
> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> SelFile.c: In function ‘SFexposeList’:
> SelFile.c:153:9: warning: implicit declaration of function ‘SFdrawList’ 
> [-Wimplicit-function-declaration]
>   153 | SFdrawList(n, SF_DO_NOT_SCROLL);
>   | ^~
> SelFile.c: In function ‘SFcreateWidgets’:
> SelFile.c:275:9: warning: implicit declaration of function ‘SFinitFont’ 
> [-Wimplicit-function-declaration]
>   275 | SFinitFont();
>   | ^~
> SelFile.c:481:9: warning: implicit declaration of function ‘SFcreateGC’; did 
> you mean ‘XCreateGC’? [-Wimplicit-function-declaration]
>   481 | SFcreateGC();
>   | ^~
>   | XCreateGC
> SelFile.c: In function ‘SFopenFile’:
> SelFile.c:568:5: warning: implicit declaration of function ‘SFchdir’; did you 
> mean ‘fchdir’? [-Wimplicit-function-declaration]
>   568 | SFchdir(SFstartDir);
>   | ^~~
>   | fchdir
> SelFile.c: At top level:
> SelFile.c:594:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
>   594 | SFtextChanged()
>   | ^
> SelFile.c: In function ‘SFtextChanged’:
> SelFile.c:613:9: warning: implicit declaration of function ‘SFupdatePath’ 
> [-Wimplicit-function-declaration]
>   613 | SFupdatePath();
>   | ^~~~
> SelFile.c: At top level:
> SelFile.c:624:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
>   624 | SFprepareToReturn()
>   | ^
> SelFile.c: In function ‘XsraSelFile’:
> SelFile.c:710:33: warning: implicit declaration of function ‘SFsetText’; did 
> you mean ‘SFgetText’? [-Wimplicit-function-declaration]
>   710 | SFsetText(SFcurrentPath);
>   | ^
>   | SFgetText
> rm -f Path.o
> gcc -c -g -O2 -fno-strict-aliasing  -I. -I.. -I/usr/include/X11 
> -I/usr/include/-Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L  
> -D_POSIX_SOURCE -D_XOPEN_SOURCE 
> -D_BSD_SOURCE -D_SVID_SOURCE 
> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
>-DFUNCPROTO=15 -DNARROWPROTO -DUSE_ATHENA 
> -DAPPDEFDIR=\"/etc/X11/app-defaults\"   
> -DRGBF=\"/etc/X11/rgb.txt\"   Path.c
> In file included from 
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
>  from /usr/include/stdio.h:27,
>  from Path.c:27:
> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> Path.c:86:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
>86 | SFfree(i)
> 

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

[Debian Bug Tracking System]

Your message dated Fri, 17 Dec 2021 09:34:07 +
with message-id 
and subject line Bug#999119: fixed in pixmap 2.6.6-1
has caused the Debian Bug report #999119,
regarding pixmap: 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.)


-- 
999119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999119
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pixmap
Version: 2.6pl4-20
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 ---
Source: pixmap
Source-Version: 2.6.6-1
Done: Paul Slootman 

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

Debian distribution maintenance software
pp.
Paul Slootman  (supplier of updated pixmap package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 23 Nov 2021 16:16:09 +0100
Source: pixmap
Architecture: source
Version: 2.6.6-1
Distribution: unstable
Urgency: medium
Maintainer: Paul Slootman 
Changed-By: Paul Slootman 
Closes: 997627 999119
Changes:
 pixmap (2.6.6-1) unstable; urgency=medium
 .
   * New upstream version.
   * Packaging now based on dh as far as that's possible with an
 Imake-based package.
 closes:#999119
   * Work around the binutils mess that means xutils-dev needs to fix Imake
 (see #981072, #997628 and #994276).
 closes:#997627
   * Replaced menu file with FreeDesktop entry.
Checksums-Sha1:
 79b67f29c4c5a32e244a65ca1b85d5d3f15a975a 1682 pixmap_2.6.6-1.dsc
 b3df495a90c2a3a5c1724f7477b59f242d0bc5f7 133625 pixmap_2.6.6.orig.tar.gz
 999a95b63effa546eebd3d26be3d41ac20e58c78 9444 pixmap_2.6.6-1.debian.tar.xz
 7508c2b0dc889a91d620c57d349a9778736e8edb 6617 pixmap_2.6.6-1_source.buildinfo
Checksums-Sha256:
 2ffb57cd985b494846a48a1ff08d806a3df77a4c32aa21eaa7b1ff7ee7bb761f 1682 
pixmap_2.6.6-1.dsc
 5fcfc0ff38d6998959e81b3b63cffe0d720227b26756422dc25fb9575d8c4f73 133625 
pixmap_2.6.6.orig.tar.gz
 d02043db0cca24184b8b59f9c2c27051bc48026ed64a5f99c07ebbcaf872ab7f 9444 
pixmap_2.6.6-1.debian.tar.xz
 c2fd5149019365d0e2be76e9dd2db26c82009da2cb42048e4c5d6d8561c6b505 6617 
pixmap_2.6.6-1_source.buildinfo
Files:
 c1673296eca29afe9bbf586eaf5f0474 1682 graphics optional pixmap_2.6.6-1.dsc
 e48d0a67ab6f61571db0cad1014863b8 133625 graphics optional 
pixmap_2.6.6.orig.tar.gz
 5bcb8519a1080f39847bf894f5706453 9444 graphics optional 
pixmap_2.6.6-1.debian.tar.xz
 54981426fe767f5754e9439e03387e67 6617 graphics optional 
pixmap_2.6.6-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEyfNP08AZcbxb9VhpMveNzq0RO4sFAmG8ViIACgkQMveNzq0R
O4sq9w//cZpmyFd1VnZfeEqQS8MsIATIlJEfSa70hkWsaicN1ZcFBF7ttgIehyZU
h8uusGeLmavtRXypVqQo0/F7LIzBFX1bpFT15kjMdBThTHDFeXdKJ/Zq0XmenG7v
s+8koF1j0eXGrDlpQYnRhaQe/Mhk4laCFwQR5s4jRYsf/qR/R4gzlpFVyG0YyU7C
Vxmw3sdVcz4UhVm+iEYyFkoJawoCXPSH2yl/KBhzMs17r4FGwk0Kt5yVJLmZglSh
kkhLMhLFzy3eqb+EiE2wILtV+k6OKHHJK6JJK4liteBTv/NlQV5prdKNdCQw2/sW
PNRSO8Wl6bCervh8YLzk3WisxM4FYus1DQ8OAkEJrVNIvolgJkNT/uhklrfLSyY+
6Agv3Udm9+E0LwB6n03Zo5020mfc4fNArVZLhSi1SnE1lPVMX+peoisY0+8uEamp
WURPP/359tmdiMpsvFvcULnoRzeIpcJLDLm+RHRc+GJwRSRLxwzsZPCgCr1mqG2q
rIy7uXQ0nVRPvHKnZkFux6V50DmeTqbDU6ifgKOIXoOWgG98dwhhFKpe5G5bWsD8
hLmQQC3AnMv8pHQVVxxBgZJOkUcfNpVgoJ6U+nLJf8p4D/Lx2m+Xn0PzVBF1WxSg
De78Kk7LQQWZ7y/qBqhdJCjjCeTD9KiKItWMgdtReDIjciMM8IU=
=C8rD
-END PGP 

Processed: tagging 992575

[Debian Bug Tracking System]

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

> tags 992575 + fixed-upstream
Bug #992575 [libtorrent-rasterbar10] libtorrent-rasterbar10: import fails on 
Raspberry Pi 3b
Bug #999422 [libtorrent-rasterbar10] Deluge fails with ModuleNotFoundError
Ignoring request to alter tags of bug #992575 to the same tags previously set
Ignoring request to alter tags of bug #999422 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#1001821: marked as done (phoc FTBFS with libwlroots-dev 0.14.1)

[Debian Bug Tracking System]

Your message dated Fri, 17 Dec 2021 09:04:34 +
with message-id 
and subject line Bug#1001821: fixed in phoc 0.11.0-1
has caused the Debian Bug report #1001821,
regarding phoc FTBFS with libwlroots-dev 0.14.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.)


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

https://buildd.debian.org/status/logs.php?pkg=phoc=0.9.0-1%2Bb1

...
FAILED: src/libphoc.a.p/desktop.c.o 
cc -Isrc/libphoc.a.p -Isrc -I../src -Iprotocols -I/usr/include/libdrm 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gnome-desktop-3.0 
-I/usr/include/libxml2 -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 
-I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gio-unix-2.0 
-I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz 
-I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/x86_64-linux-gnu 
-I/usr/include/gsettings-desktop-schemas 
-I/<>/obj-x86_64-linux-gnu -fdiagnostics-color=always 
-D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu11 -DWLR_USE_UNSTABLE 
-Wcast-align -Wdate-time -Werror=format-security -Werror=format=2 
-Wendif-labels -Werror=incompatible-pointer-types -Werror=missing-declarations 
-Werror=overflow -Werror=return-type -Werror=shift-count-overflow 
-Werror=shift-overflow=2 -Werror=implicit-fallthrough=3 -Wformat-nonliteral 
-Wformat-security -Winit-self -Wmaybe-uninitialized 
-Wmissing-field-initializers -Wmissing-include-dirs -Wmissing-noreturn 
-Wnested-externs -Wno-missing-field-initializers -Wno-sign-compare 
-Wno-strict-aliasing -Wno-unused-parameter -Wold-style-definition 
-Wpointer-arith -Wredundant-decls -Wshadow -Wstrict-prototypes -Wtype-limits 
-Wundef -Wunused-function -Wswitch-default -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ 
src/libphoc.a.p/desktop.c.o -MF src/libphoc.a.p/desktop.c.o.d -o 
src/libphoc.a.p/desktop.c.o -c ../src/desktop.c
../src/desktop.c:16:10: fatal error: wlr/types/wlr_gtk_primary_selection.h: No 
such file or directory
   16 | #include 
  |  ^~~
compilation terminated.
--- End Message ---
--- Begin Message ---
Source: phoc
Source-Version: 0.11.0-1
Done: Guido Günther 

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

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

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

Debian distribution maintenance software
pp.
Guido Günther  (supplier of updated phoc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 16 Dec 2021 19:22:05 +0100
Source: phoc
Architecture: source
Version: 0.11.0-1
Distribution: unstable
Urgency: medium
Maintainer: DebianOnMobile Maintainers 

Changed-By: Guido Günther 
Closes: 1001821
Changes:
 phoc (0.11.0-1) unstable; urgency=medium
 .
   * New upstream version 0.11.0
 (Closes: #1001821)
   * d/watch: Fix watch expression to match tag names
   * d/gbp.conf: Use upsteam tarball
Checksums-Sha1:
 d5c82cff3e4a8c9e2df96bb9d64892f006fa4195 2363 phoc_0.11.0-1.dsc
 1cf9cde7194087208f2091c2d81c9b7522d8f11d 161198 phoc_0.11.0.orig.tar.gz
 c801d4b07a1d51c253c329cd64c5a451d255f3c0 5592 phoc_0.11.0-1.debian.tar.xz
 8865bfc6a830dd38715525af62c9f774ee525969 16478 phoc_0.11.0-1_amd64.buildinfo
Checksums-Sha256:
 9e1bd915b33f3facbf0f671d95d9a5a552efa0ab2f45de13f8c5ce1b81de0f18 2363 
phoc_0.11.0-1.dsc
 237ce471bdf01a14259f33725632deceaf429353766205beeb9d96a3fb921de1 161198 
phoc_0.11.0.orig.tar.gz
 894b0efe6fc926bdd432547bf4eb7199d034717de840c27e8d2dfdf221d2902a 5592 
phoc_0.11.0-1.debian.tar.xz
 43015680205ed9523d952a25a80e1c19fcfbfba891ad31e01f063449d2a9814d 16478 
phoc_0.11.0-1_amd64.buildinfo
Files:
 

Bug#993247: Fixed version is in NEW

[Adrian Bunk]

A fixed version is in NEW.

cu
Adrian

Processed: tagging 999422

[Debian Bug Tracking System]

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

> tags 999422 + fixed-upstream
Bug #999422 [libtorrent-rasterbar10] Deluge fails with ModuleNotFoundError
Bug #992575 [libtorrent-rasterbar10] libtorrent-rasterbar10: import fails on 
Raspberry Pi 3b
Ignoring request to alter tags of bug #999422 to the same tags previously set
Ignoring request to alter tags of bug #992575 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: fixed 999422 in 2.0.4-1

[Debian Bug Tracking System]

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

> fixed 999422 2.0.4-1
Bug #999422 [libtorrent-rasterbar10] Deluge fails with ModuleNotFoundError
Bug #992575 [libtorrent-rasterbar10] libtorrent-rasterbar10: import fails on 
Raspberry Pi 3b
There is no source info for the package 'libtorrent-rasterbar10' at version 
'2.0.4-1' with architecture ''
Unable to make a source version for version '2.0.4-1'
Ignoring request to alter fixed versions of bug #999422 to the same values 
previously set
Ignoring request to alter fixed versions of bug #992575 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: tagging 992575

[Debian Bug Tracking System]

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

> tags 992575 + fixed-upstream
Bug #992575 [libtorrent-rasterbar10] libtorrent-rasterbar10: import fails on 
Raspberry Pi 3b
Bug #999422 [libtorrent-rasterbar10] Deluge fails with ModuleNotFoundError
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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