Processed: affects 1021735

[Debian Bug Tracking System]

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

> affects 1021735 src:python-cffi src:python3.11 src:python3.10
Bug #1021735 [src:libffi] libffi breaks python3.10 autopkgtest on arm64 (and 5 
other packages)
Added indication that 1021735 affects src:python-cffi, src:python3.11, and 
src:python3.10
> thanks
Stopping processing here.

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

Bug#1021906: kanboard FTBFS: Failed asserting that 3.3000000000000003 matches expected 3.3

[Adrian Bunk]

Source: kanboard
Version: 1.2.23+ds-1.1
Severity: serious
Tags: ftbfs patch fixed-upstream
Forwarded: https://github.com/kanboard/kanboard/pull/5078

https://buildd.debian.org/status/fetch.php?pkg=kanboard=all=1.2.23%2Bds-1.1=1665834979=0

...
There was 1 failure:

1) SubtaskTimeTrackingModelTest::testCalculateSubtaskTime
Total spent
Failed asserting that 3.3003 matches expected 3.3.

/<>/tests/units/Model/SubtaskTimeTrackingModelTest.php:186

FAILURES!
Tests: 1094, Assertions: 146248, Failures: 1, Warnings: 8.
make[1]: *** [debian/rules:40: override_dh_auto_test] Error 1

Bug#1021616: marked as done (obs-text-slideshow: FTBFS with OBS 28)

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2022 04:10:47 +
with message-id 
and subject line Bug#1021617: Removed package(s) from unstable
has caused the Debian Bug report #1021616,
regarding obs-text-slideshow: FTBFS with OBS 28
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.)


-- 
1021616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: obs-text-slideshow
Version: 1.5.2-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

The current source code on Debian FTBFS with obs-studio 28.1.2.

dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake
-DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON
-DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run
-DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles"
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu ..
returned exit code 1
make: *** [debian/rules:11: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
debuild: fatal error at line 1182:
dpkg-buildpackage -us -uc -ui failed

Eriberto
--- End Message ---
--- Begin Message ---
Version: 1.5.2-3+rm

Dear submitter,

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

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

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

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

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

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

Bug#1021274: marked as done (python-opcua: CVE-2022-25304)

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2022 04:13:12 +
with message-id 
and subject line Bug#1021760: Removed package(s) from unstable
has caused the Debian Bug report #1021274,
regarding python-opcua: CVE-2022-25304
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.)


-- 
1021274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021274
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-opcua
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for python-opcua.

CVE-2022-25304[0]:
| All versions of package opcua; all versions of package asyncua are
| vulnerable to Denial of Service (DoS) due to a missing limitation on
| the number of received chunks - per single session or in total for all
| concurrent sessions. An attacker can exploit this vulnerability by
| sending an unlimited number of huge chunks (e.g. 2GB each) without
| sending the Final closing chunk.

https://github.com/FreeOpcUa/python-opcua/issues/1466
https://security.snyk.io/vuln/SNYK-PYTHON-OPCUA-2988730

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-25304
https://www.cve.org/CVERecord?id=CVE-2022-25304

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Version: 0.98.11-2+rm

Dear submitter,

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

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

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

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

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

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

Bug#902132: marked as done (falcon: FTBFS since python-networkx version 2.1-1; fails in test suite)

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2022 04:07:55 +
with message-id 
and subject line Bug#1015978: Removed package(s) from unstable
has caused the Debian Bug report #902132,
regarding falcon: FTBFS since python-networkx version 2.1-1; fails in test suite
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.)


-- 
902132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902132
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: falcon
Version: 1.8.8-1
Severity: serious
Tags: ftbfs
Justification: FTBFS
User: debian...@lists.debian.org
Usertags: needs-update

Dear Afif,

Follow-up from the thread starting here:
https://alioth-lists.debian.net/pipermail/debian-med-packaging/2018-June/063209.html

falcon FTBFS since python-networkx version 2.1-1 entered the archive
because the test suite is broken.

Paul

On 22-06-18 15:44, Afif Elghraoui wrote:
> On June 22, 2018 8:54:03 AM EDT, Paul Gevers  wrote:
>> falcon needs updating anyways as your test is run during build and your
>> package now FTBFS¹. Do you consider this a bug against falcon or
>> against
>> python-networkx? (In general it will be considered a falcon bug once
>> python-networkx migrates).
>>
> 
> It's a falcon bug, but there's a newer upstream that probably doesn't
> have this problem. I tried to update the package a while ago, but it
> requires more time than I had at the moment because the build system
> changed significantly and part of the code base is now written in
> nim.
>> ¹
>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/falcon.html



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

Dear submitter,

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

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

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

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

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

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

Bug#1015978: marked as done (RM: falcon -- RoM; Depends on Python 2)

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2022 04:07:51 +
with message-id 
and subject line Bug#1015978: Removed package(s) from unstable
has caused the Debian Bug report #1015978,
regarding RM: falcon -- RoM; Depends on Python 2
to be marked as done.

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

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


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

Your package came up as a candidate for removal from Debian:
- Still depends on Python 2
- Dropped from testing in 2018
- Last upload in 2017

If you disagree and want to continue to maintain this package,
please just close this bug (and fix the open issues).

If you agree with the removal, please reassign to ftp.debian.org
by sending the following commands to cont...@bugs.debian.org:

--
severity $BUGNUM normal
reassign $BUGNUM ftp.debian.org
retitle $BUGNUM RM:  -- RoM; 
thx
--

Otherwise I'll move forward and request it's removal in a month.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

falcon |1.8.8-1 | source, amd64, arm64, mips64el, ppc64el, s390x

--- Reason ---
RoM; Depends on Python 2
--

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

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

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

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

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

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

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

Bug#936503: marked as done (falcon: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2022 04:07:55 +
with message-id 
and subject line Bug#1015978: Removed package(s) from unstable
has caused the Debian Bug report #936503,
regarding falcon: Python2 removal in sid/bullseye
to be marked as done.

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

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


-- 
936503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936503
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:falcon
Version: 1.8.8-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:falcon

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

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

Dear submitter,

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

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

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

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

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

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

Bug#1021888: librust-deflate-dev: impossible to install

[Peter Green]

posting to -quiet as I already sent pretty much the same mail to two other 
rust-team bugs.

It appears that rust-deflate was uploaded a bit prematurely, it depends on a new
version of rust-gzip--header which can't be packaged with the cargo/debcargo
currently in Debian.

Processed: closing 1017129

[Debian Bug Tracking System]

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

> close 1017129 5+c3
Bug #1017129 [src:gcc-11-cross-mipsen] gcc-11-cross-mipsen: FTBFS: 
conftest.c:80: undefined reference to `fprintf_unlocked'
Marked as fixed in versions gcc-11-cross-mipsen/5+c3.
Bug #1017129 [src:gcc-11-cross-mipsen] gcc-11-cross-mipsen: FTBFS: 
conftest.c:80: undefined reference to `fprintf_unlocked'
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 1017177

[Debian Bug Tracking System]

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

> close 1017177 2+c1
Bug #1017177 [src:gcc-12-cross-mipsen] gcc-12-cross-mipsen: FTBFS: 
gcc/build/gcc/include-fixed/pthread.h:42:11: fatal error: 
bits/pthread_stack_min-dynamic.h: No such file or directory
Marked as fixed in versions gcc-12-cross-mipsen/2+c1.
Bug #1017177 [src:gcc-12-cross-mipsen] gcc-12-cross-mipsen: FTBFS: 
gcc/build/gcc/include-fixed/pthread.h:42:11: fatal error: 
bits/pthread_stack_min-dynamic.h: No such file or directory
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1004638: Bug#1013009: Bug#1004638: openjfx: FTBFS with ffmpeg 5.0

[Emmanuel Bourg]

Le 16/10/2022 à 17:10, Philipp Kern a écrit :


While arm64/armhf remains unfixed (and could have its own t-p-u upload
based on the +0 version plus Ubuntu's patch), there's also a question if
a newer version would actually fix the issue.

I talked to Sebastian on IRC and we agreed that I'd upload the Ubuntu
patch for now. It doesn't make anything worse and will allow building
on amd64 again.


Hi Philipp,

Thank you for taking the time to look into the openjfx package. Do you 
know how difficult porting to ffmpeg 5.0 would be? The video support is 
a major feature of OpenJFX, removing it isn't ideal.


Emmanuel Bourg

Bug#1021880: rust-image - multiple issues.

[Peter Green]

Hi.

It appears that rust-deflate was uploaded a bit prematurely, it depends on a new
version of rust-gzip--header which can't be packaged with the cargo/debcargo
currently in Debian.

Once cargo/debcargo are updated we can move on to updating/fixing the image
stack.

Bug#1021603: libpmix2

[Ron Lovell]

Should have said Arch Linux Issue 75727.

On Sun, Oct 16, 2022 at 5:20 PM Ron Lovell  wrote:

> Same issue as Arch issue 279267?
>
> --
> James Ronald Lovell 
> Huntsville, AL, USA
>
>

-- 
James Ronald Lovell 
Huntsville, AL, USA

Bug#1021603: libpmix2

[Ron Lovell]

Same issue as Arch issue 279267?

-- 
James Ronald Lovell 
Huntsville, AL, USA

Bug#1021846: grub-install is broken since 2.06-3: error: unknown filesystem

[Steve McIntyre]

On Sun, Oct 16, 2022 at 09:57:35PM +0100, Steve McIntyre wrote:
>On Sun, Oct 16, 2022 at 07:37:53AM +0300, программист некто wrote:
>>Output already captured. See 
>>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021846  the first message 
>>- it have an attached files with grub-install output.
>
>Ah, sorry; I missed them. Looking now.

So I can see from the logs is that from 2.06-3 is just failing to
detect a f2fs filesyste. There *was* a significant set of changes
before we shipped that version: upstream security updates that fixed a
big set of bugs, including in the f2fs code. I'm thinking that one of
those changes might have caused this issue.

Are you happy to try rebuilding grub from source yourself? If so, I'd
suggest to rebuild without those f2fs changes included. If you're not
sure, let me know and I'll do a rebuild for you.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
< Aardvark> I dislike C++ to start with. C++11 just seems to be
handing rope-creating factories for users to hang multiple
instances of themselves.

Bug#1013549: marked as done (xfsdump: FTBFS: gcc: fatal error: no input files)

[Debian Bug Tracking System]

Your message dated Sun, 16 Oct 2022 21:10:50 +
with message-id 
and subject line Bug#1013549: fixed in xfsdump 3.1.11-0.1
has caused the Debian Bug report #1013549,
regarding xfsdump: FTBFS: gcc: fatal error: no input files
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.)


-- 
1013549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013549
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xfsdump
Version: 3.1.9+0+nmu2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> [CC] rmtmsg.lo
> [LD] librmt.la
> Building common
> Building inventory
> [LTDEP]
> gcc: fatal error: no input files
> compilation terminated.
> Building invutil
> [LN] global.h
> [LN] mlog.h
> [LN] timeutil.h
> [LN] types.h
> [LN] timeutil.c
> [LN] inventory.h
> [LN] inv_priv.h
> [LN] inv_files.c
> [DEP]
> [CC] timeutil.o
> [CC] inv_files.o
> [CC] invutil.o
> [CC] cmenu.o
> [CC] fstab.o
> fstab.c: In function ‘fstab_highlight’:
> fstab.c:167:41: warning: ‘%s’ directive output may be truncated writing up to 
> 255 bytes into a region of size 248 [-Wformat-truncation=]
>   167 | snprintf(txt, sizeof(txt), "device: %s", fstabentry->ft_devpath);
>   | ^~
> fstab.c:167:5: note: ‘snprintf’ output between 9 and 264 bytes into a 
> destination of size 256
>   167 | snprintf(txt, sizeof(txt), "device: %s", fstabentry->ft_devpath);
>   | ^~~~
> [CC] invidx.o
> invidx.c: In function ‘invidx_highlight’:
> invidx.c:705:40: warning: ‘%s’ directive output may be truncated writing up 
> to 255 bytes into a region of size 249 [-Wformat-truncation=]
>   705 | snprintf(txt, sizeof(txt), "path:  %s", invtentry->ie_filename);
>   |^~
> invidx.c:705:5: note: ‘snprintf’ output between 8 and 263 bytes into a 
> destination of size 256
>   705 | snprintf(txt, sizeof(txt), "path:  %s", invtentry->ie_filename);
>   | ^~~
> invidx.c: In function ‘invidx_commit’:
> invidx.c:253:51: warning: ‘%s’ directive output may be truncated writing up 
> to 4095 bytes into a region of size 1020 [-Wformat-truncation=]
>   253 | snprintf(cmd, sizeof(cmd), "cp %s %s", stobjfile, 
> dst_stobjfile);
>   |   ^~  
> ~
> invidx.c:253:17: note: ‘snprintf’ output 5 or more bytes (assuming 4100) into 
> a destination of size 1024
>   253 | snprintf(cmd, sizeof(cmd), "cp %s %s", stobjfile, 
> dst_stobjfile);
>   | 
> ^~~~
> invidx.c:323:47: warning: ‘%s’ directive output may be truncated writing up 
> to 4095 bytes into a region of size 1020 [-Wformat-truncation=]
>   323 | snprintf(cmd, sizeof(cmd), "cp %s %s", stobjfile, 
> dst_stobjfile);
>   |   ^~  
> ~
> invidx.c:323:13: note: ‘snprintf’ output 5 or more bytes (assuming 4100) into 
> a destination of size 1024
>   323 | snprintf(cmd, sizeof(cmd), "cp %s %s", stobjfile, 
> dst_stobjfile);
>   | 
> ^~~~
> [CC] list.o
> [CC] menu.o
> [CC] screen.o
> [CC] stobj.o
> stobj.c: In function ‘stobjstrm_highlight’:
> stobj.c:227:58: warning: ‘%s’ directive output may be truncated writing up to 
> 255 bytes into a region of size between 230 and 231 [-Wformat-truncation=]
>   227 | snprintf(txt, sizeof(txt), "interrupted: %s, cmdarg: %s",
>   |  ^~
> stobj.c:227:5: note: ‘snprintf’ output between 26 and 282 bytes into a 
> destination of size 256
>   227 | snprintf(txt, sizeof(txt), "interrupted: %s, cmdarg: %s",
>   | ^
>   228 | (stobjstrm->st_interrupted == BOOL_TRUE) ? "yes" : "no",
>   | 
>   229 | stobjstrm->st_cmdarg);
>   | 

Bug#1019347: Fixed NMU

[Sven Bartscher]

Hi,

I just wanted to give a heads up, that earlier today I uploaded an NMU 
to DELAYED+5 containing upstream version 1.7.4 which should fix this bug.


I pushed the changes to the packaging repository on salsa, so I assume a 
debdiff of the NMU is not required here.


Regards
Sven


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1021846: grub-install is broken since 2.06-3: error: unknown filesystem

[Steve McIntyre]

On Sun, Oct 16, 2022 at 07:37:53AM +0300, программист некто wrote:
>Output already captured. See 
>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021846  the first message - 
>it have an attached files with grub-install output.

Ah, sorry; I missed them. Looking now.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
  Mature Sporty Personal
  More Innovation More Adult
  A Man in Dandism
  Powered Midship Specialty

Processed: affects 1021735

[Debian Bug Tracking System]

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

> affects 1021735 python-cffi python3.11 python3.10
Bug #1021735 [src:libffi] libffi breaks python3.10 autopkgtest on arm64 (and 5 
other packages)
Added indication that 1021735 affects python-cffi, python3.11, and python3.10
> thanks
Stopping processing here.

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

Processed: Re: kopano-presence: please migrate from sleekxmpp to slixmpp

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1017035 [kopano-presence] kopano-presence: please migrate from sleekxmpp 
to slixmpp
Severity set to 'serious' from 'important'

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

Bug#1021889: marked as done (pylint breaks pylint-django autopkgtest: ScopeConsumer.__new__() missing 1 required positional argument: 'scope_type')

[Debian Bug Tracking System]

Your message dated Sun, 16 Oct 2022 19:10:58 +
with message-id 
and subject line Bug#1021889: fixed in pylint-django 2.0.13-3
has caused the Debian Bug report #1021889,
regarding pylint breaks pylint-django autopkgtest: ScopeConsumer.__new__() 
missing 1 required positional argument: 'scope_type'
to be marked as done.

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

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


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

Source: pylint, pylint-django
Control: found -1 pylint/2.15.3-1
Control: found -1 pylint-django/2.0.13-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
pylint from testing2.15.3-1
pylint-django  from testing2.0.13-2
all others from testingfrom testing

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

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pylint-django/27163271/log.gz

Running “django-admin startproject testproject”
Running “django-admin startapp testapp”
Running “pylint --version”
pylint 2.15.3
astroid 2.12.10
Python 3.10.7 (main, Sep  8 2022, 14:34:29) [GCC 12.2.0]
Running “pylint -E --load-plugins=pylint_django testapp/”
Exception on node  in file 
'/tmp/autopkgtest-lxc.6ld_wzc5/downtmp/autopkgtest_tmp/testproject/testapp/__init__.py'

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/pylint/utils/ast_walker.py", 
line 95, in walk

callback(astroid)
  File 
"/usr/lib/python3/dist-packages/pylint_django/augmentations/__init__.py", 
line 739, in wrap_func

return with_method(orig_method, *args, **kwargs)
  File 
"/usr/lib/python3/dist-packages/pylint_django/augmentations/__init__.py", 
line 317, in ignore_import_warnings_for_related_fields
consumer._atomic = ScopeConsumer(new_things, consumer.consumed, 
consumer.scope_type)  # pylint: disable=W0212
TypeError: ScopeConsumer.__new__() missing 1 required positional 
argument: 'scope_type'
Can't write the issue template for the crash in 
/home/debci/.cache/pylint/pylint-crash-2022-10-16-06-16-20.txt because 
of: '[Errno 2] No such file or directory: 
'/home/debci/.cache/pylint/pylint-crash-2022-10-16-06-16-20.txt''

Here's the content anyway:
First, please verify that the bug is not already filled:
https://github.com/PyCQA/pylint/issues/

Then create a new crash issue:
https://github.com/PyCQA/pylint/issues/new?assignees==crash%2Cneeds+triage=BUG-REPORT.yml


Issue title:
Crash  (if possible, be more specific about what made pylint crash)
Content:
When parsing the following file:



```python

```

pylint crashed with a ``AstroidError`` and with the following stacktrace:
```
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/pylint/lint/pylinter.py", line 
782, in _lint_file

check_astroid_module(module)
  File "/usr/lib/python3/dist-packages/pylint/lint/pylinter.py", line 
1049, in check_astroid_module

retval = self._check_astroid_module(
  File "/usr/lib/python3/dist-packages/pylint/lint/pylinter.py", line 
1099, in _check_astroid_module

walker.walk(node)
  File "/usr/lib/python3/dist-packages/pylint/utils/ast_walker.py", 
line 95, in walk

callback(astroid)
  File 
"/usr/lib/python3/dist-packages/pylint_django/augmentations/__init__.py", 
line 739, in wrap_func

return with_method(orig_method, *args, **kwargs)
  File 
"/usr/lib/python3/dist-packages/pylint_django/augmentations/__init__.py", 
line 317, in ignore_import_warnings_for_related_fields
consumer._atomic = ScopeConsumer(new_things, consumer.consumed, 
consumer.scope_type)  # pylint: disable=W0212
TypeError: ScopeConsumer.__new__() missing 1 required positional 
argument: 'scope_type'


The above exception was the direct cause of the following exception:

Traceback 

Bug#1021898: sfepy: FTBFS: distutils.errors.DistutilsSetupError: each element of 'ext_modules' option must be an Extension instance or 2-tuple

[Sebastian Ramacher]

Source: sfepy
Version: 2021.4-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=sfepy=amd64=2021.4-1%2Bb1=1665944538=0

Traceback (most recent call last):
  File "/<>/setup.py", line 252, in 
setup_package()
  File "/<>/setup.py", line 230, in setup_package
setup(name='sfepy',
  File "/usr/lib/python3/dist-packages/numpy/distutils/core.py", line 169, in 
setup
return old_setup(**new_attr)
  File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 87, in 
setup
return distutils.core.setup(**attrs)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
185, in setup
return run_commands(dist)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
201, in run_commands
dist.run_commands()
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
973, in run_commands
self.run_command(cmd)
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1217, in 
run_command
super().run_command(command)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
992, in run_command
cmd_obj.run()
  File "/usr/lib/python3/dist-packages/numpy/distutils/command/build.py", line 
61, in run
old_build.run(self)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/command/build.py", 
line 132, in run
self.run_command(cmd_name)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 319, 
in run_command
self.distribution.run_command(command)
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1217, in 
run_command
super().run_command(command)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
992, in run_command
cmd_obj.run()
  File "/usr/lib/python3/dist-packages/numpy/distutils/command/build_src.py", 
line 144, in run
self.build_sources()
  File "/usr/lib/python3/dist-packages/numpy/distutils/command/build_src.py", 
line 158, in build_sources
self.check_extensions_list(self.extensions)
  File "/usr/lib/python3.10/distutils/command/build_ext.py", line 362, in 
check_extensions_list
raise DistutilsSetupError(
distutils.errors.DistutilsSetupError: each element of 'ext_modules' option must 
be an Extension instance or 2-tuple
E: pybuild pybuild:379: build: plugin distutils failed with: exit code=1: 
/usr/bin/python3 setup.py build 
dh_auto_build: error: pybuild --build -i python{version} -p 3.10 returned exit 
code 13


Cheers
-- 
Sebastian Ramacher

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

[Debian Bug Tracking System]

Your message dated Sun, 16 Oct 2022 19:09:13 +
with message-id 
and subject line Bug#999259: fixed in leave 1.12-2.2
has caused the Debian Bug report #999259,
regarding leave: 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.)


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

Dear maintainer,

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

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

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

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: leave
Source-Version: 1.12-2.2
Done: Chris Lamb 

We believe that the bug you reported is fixed in the latest version of
leave, 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.
Chris Lamb  (supplier of updated leave 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, 06 Oct 2022 10:59:51 -0700
Source: leave
Binary: leave
Architecture: source amd64
Version: 1.12-2.2
Distribution: unstable
Urgency: medium
Maintainer: Josip Rodin 
Changed-By: Chris Lamb 
Description:
 leave  - Reminds you when you have to leave
Closes: 777403 967002 999259
Changes:
 leave (1.12-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Pass -n to gzip(1) to make the manual page and changelog reproducible, as
 well as pass CFLAGS to the C compiler to ensure that, for instance,
 -ffile-prefix-map is used. (Closes: #777403)
   * Apply a patch by Helmut Grohne to correctly cross-build the leave binary.
 (Closes: #967002)
   * Add the missing required debian/rules targets, build-arch and build-indep.
 (Closes: #999259)
   * Remove a "debian/changelog~" editor backup file.
Checksums-Sha1:
 57dc7148e136060daf194149321e341b40cc8901 1576 leave_1.12-2.2.dsc
 499943d84f0425c4c774563b0d1ae911f565ad1e 3470 leave_1.12.orig.tar.gz
 8ac18ca6b280b2733dcacd57a5c3909e14e65e80 3268 leave_1.12-2.2.diff.gz
 528eaccb6a087f7a7e333c4d2ec5807662985616 4742 leave_1.12-2.2_amd64.buildinfo
 a18970d7a0f971e612cf4881c46e2f6dbced9cfb 7604 leave_1.12-2.2_amd64.deb
Checksums-Sha256:
 e6cd6ea8bd7b08b364acc64a8afcf911438344438e1a941648cd7c858d9aebf7 1576 
leave_1.12-2.2.dsc
 de30529de8abf49004da4120ca352d5c588a657f8845e44d5e83a4860e6bbe1f 3470 
leave_1.12.orig.tar.gz
 5efa9008131b3f19b7a1cb44cce2f65d16d94dfce2cd660f2d2cb472a62520e8 3268 
leave_1.12-2.2.diff.gz
 f8734a147459b18f034309c4b37a70776e261e0b479edd6342822606caf57731 4742 
leave_1.12-2.2_amd64.buildinfo
 348578ac307e6d4bb0da1e77a75977e0e212a05d5845a0735c0cb3fb73c811b7 7604 
leave_1.12-2.2_amd64.deb
Files:
 67c347f78f8d92e84174c36b42444b42 1576 utils optional leave_1.12-2.2.dsc
 1d02b3420b22c59d5983780763076090 3470 utils optional leave_1.12.orig.tar.gz
 0fb3b265f666a7ea873c07f97f32fedb 3268 utils optional leave_1.12-2.2.diff.gz
 387176ffd2e52cfc47fa0b4c2e9b602c 4742 utils optional 
leave_1.12-2.2_amd64.buildinfo
 1a290a6d52d340fe6e9e87aca142cc5c 7604 utils optional leave_1.12-2.2_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAmM/GKsACgkQHpU+J9Qx
HliyPhAAmTxOJHNZAfqGguHGevGKZyIC/aN+cjWM6J/w5sIeXgBjHDWripOCHiaY
wp4BB/VzxpzcsHLIm844UCGSEbi1WYyynStsRbI07TEVvg82tL5OBeeUkDW09VjY
YBWbykeFnqdeTIt35YfAdYk5Po5tpWZnUxCkopi5Y9f7RWcFhcfwhMxRxk8z3SmX
/d+dzJu6Mb88y6cQEMkz7X8JEqAE9sRjCjJ/yWhSpHYpEb/COg1lIev5VRgIYo6j

Bug#1021895: pylint: fails to honor "--" argument

[Nilesh Patra]

Package: pylint
Version: 2.15.3-1
Severity: serious
Tags: patch
X-Debbugs-Cc: mo...@debian.org

Hi,

It seems that the new version of pylint does not honor the
"--" arg.
In particular, if you notice the autopkgtest for ionit[1] it fails with:

/usr/bin/python3 -m pylint 
--rcfile=/tmp/autopkgtest-lxc.2tqox33y/downtmp/build.geB/src/tests/pylint.conf 
-- /usr/bin/ionit tests /usr/lib/python3/dist-packages/ionit_plugin.py setup.py
[...]
AssertionError: pylint found issues:
* Module --
--:1:0: F0001: No module named -- (fatal)

This seems to have been fixed upstream already in this commit[2]. Please - 
either
apply this or upgrade to latest upstream (which is just one patch release 
later).

[1]: 
https://ci.debian.net/data/autopkgtest/testing/amd64/i/ionit/27128934/log.gz
[2]: 
https://github.com/PyCQA/pylint/commit/43ecd7dbf34d9a4ed0e3085a9c6e047a8326e131

Thanks,
Nilesh

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

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

Versions of packages pylint depends on:
ii  python3 3.10.6-1
pn  python3-astroid 
pn  python3-isort   
pn  python3-logilab-common  
pn  python3-mccabe  
ii  python3-platformdirs2.5.2-1
ii  python3-setuptools  59.6.0-1.2
ii  python3-toml0.10.2-1

Versions of packages pylint recommends:
ii  python3-tk  3.10.7-1

Versions of packages pylint suggests:
pn  pylint-doc  

Processed: reassign

[Debian Bug Tracking System]

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

> reassign 1021889 pylint-django 2.0.13-2
Bug #1021889 [src:pylint, src:pylint-django] pylint breaks pylint-django 
autopkgtest: ScopeConsumer.__new__() missing 1 required positional argument: 
'scope_type'
Bug reassigned from package 'src:pylint, src:pylint-django' to 'pylint-django'.
No longer marked as found in versions pylint-django/2.0.13-2 and 
pylint/2.15.3-1.
Ignoring request to alter fixed versions of bug #1021889 to the same values 
previously set
Bug #1021889 [pylint-django] pylint breaks pylint-django autopkgtest: 
ScopeConsumer.__new__() missing 1 required positional argument: 'scope_type'
There is no source info for the package 'pylint-django' at version '2.0.13-2' 
with architecture ''
Unable to make a source version for version '2.0.13-2'
Marked as found in versions 2.0.13-2.
> stop
Stopping processing here.

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

Bug#1021894: openjfx: FTBFS on arm64 and armhf

[Sebastian Ramacher]

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

openjfx FTBFS on arm64 and armhf for some time now. Let's record that in
the BTS.

https://buildd.debian.org/status/fetch.php?pkg=openjfx=arm64=11.0.11%2B1-1=1651592229=0

:web:compileNativeLinux FAILED
:web:compileNativeLinux (Thread[Task worker for ':' Thread 3,5,main]) 
completed. Took 10 mins 30.851 secs.

FAILURE: Build failed with an exception.

* Where:
Build file '/<>/build.gradle' line: 3922

* What went wrong:
Execution failed for task ':web:compileNativeLinux'.
> Process 'command 'perl'' finished with non-zero exit value 2

* Try:
Run with --debug option to get more log output. Run with --scan to get full 
insights.

* Exception is:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task 
':web:compileNativeLinux'.
at 
org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:100)
at 
org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:70)
at 
org.gradle.api.internal.tasks.execution.OutputDirectoryCreatingTaskExecuter.execute(OutputDirectoryCreatingTaskExecuter.java:51)
at 
org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:62)
at 
org.gradle.api.internal.tasks.execution.ResolveTaskOutputCachingStateExecuter.execute(ResolveTaskOutputCachingStateExecuter.java:54)
at 
org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:60)
at 
org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:97)
at 
org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:87)
at 
org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:52)
at 
org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:52)
at 
org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:54)
at 
org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)
at 
org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:34)
at 
org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker$1.run(DefaultTaskGraphExecuter.java:248)
at 
org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336)
at 
org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328)
at 
org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:199)
at 
org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:110)
at 
org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:241)
at 
org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:230)
at 
org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.processTask(DefaultTaskPlanExecutor.java:123)
at 
org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.access$200(DefaultTaskPlanExecutor.java:79)
at 
org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:104)
at 
org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:98)
at 
org.gradle.execution.taskgraph.DefaultTaskExecutionPlan.execute(DefaultTaskExecutionPlan.java:626)
at 
org.gradle.execution.taskgraph.DefaultTaskExecutionPlan.executeWithTask(DefaultTaskExecutionPlan.java:581)
at 
org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.run(DefaultTaskPlanExecutor.java:98)
at 
org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
at 
org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
at 
org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
Caused by: org.gradle.process.internal.ExecException: Process 'command 'perl'' 
finished with non-zero exit value 2
at 
org.gradle.process.internal.DefaultExecHandle$ExecResultImpl.assertNormalExitValue(DefaultExecHandle.java:382)
at 

Processed: Bug#1021889 marked as pending in pylint-django

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1021889 [src:pylint, src:pylint-django] pylint breaks pylint-django 
autopkgtest: ScopeConsumer.__new__() missing 1 required positional argument: 
'scope_type'
Added tag(s) pending.

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

Bug#1021889: marked as pending in pylint-django

[Nilesh Patra]

Control: tag -1 pending

Hello,

Bug #1021889 in pylint-django 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/pylint-django/-/commit/f2ac9bb889f4192791c2c0ad6a9324c505d299cc


Add patch to fix FTBFS with new pylint (Closes: #1021889)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1021889

Bug#1021882: marked as done (ros2-rosidl: FTBFS on mipsel: test failures)

[Debian Bug Tracking System]

Your message dated Sun, 16 Oct 2022 18:15:59 +
with message-id 
and subject line Bug#1021882: fixed in ros2-rosidl 3.3.0-3
has caused the Debian Bug report #1021882,
regarding ros2-rosidl: FTBFS on mipsel: test failures
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=ros2-rosidl=mipsel=3.3.0-2=1665762594=0


94% tests passed, 1 tests failed out of 16

Label Time Summary:
cppcheck  =   3.13 sec*proc (2 tests)
cpplint   = 174.44 sec*proc (2 tests)
gtest =   4.96 sec*proc (7 tests)
linter= 198.87 sec*proc (6 tests)
uncrustify=  21.30 sec*proc (2 tests)

Total Test time (real) = 120.04 sec

The following tests FAILED:
  2 - cpplint_rosidl_generated_cpp (Timeout)
Errors while running CTest
make[1]: *** [Makefile:74: test] Error 8

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: ros2-rosidl
Source-Version: 3.3.0-3
Done: Timo Röhling 

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

Debian distribution maintenance software
pp.
Timo Röhling  (supplier of updated ros2-rosidl 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: Sun, 16 Oct 2022 19:53:45 +0200
Source: ros2-rosidl
Architecture: source
Version: 3.3.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Robotics Team 
Changed-By: Timo Röhling 
Closes: 1021882
Changes:
 ros2-rosidl (3.3.0-3) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository-Browse.
 .
   [ Timo Röhling ]
   * Rebuild against ros2-ament-lint with increased timeouts (Closes: #1021882)
Checksums-Sha1:
 2ffe40ca52cc6fc446b4cee920f8d93b78894702 3244 ros2-rosidl_3.3.0-3.dsc
 a76dd85869ad7239269148d26ea98d219fbb690a 5472 ros2-rosidl_3.3.0-3.debian.tar.xz
Checksums-Sha256:
 e18fe2b568af6b4dd9ed550a44ea6c6acaac63e44f43db7053ffaf7219d4f2b0 3244 
ros2-rosidl_3.3.0-3.dsc
 a745172b7a6a39df91576ddb770e1c199ec71f47741365f12c634b5765120bd8 5472 
ros2-rosidl_3.3.0-3.debian.tar.xz
Files:
 80fe8342c824eec7000100d39c40cacb 3244 devel optional ros2-rosidl_3.3.0-3.dsc
 1baa2aa9f5f0298bc6055db5ce72c5ae 5472 devel optional 
ros2-rosidl_3.3.0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQHIBAEBCgAyFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmNMRiwUHHJvZWhsaW5n
QGRlYmlhbi5vcmcACgkQ+C8H+466LVlU6wwAsoT8f3vxxGKvReK0X6d7PZOZLxdK
yMi8zmqjWGOo6UbqjC2iEUHGopHL3OSgjtq9J1GaoKU2rejnNmvqDdua6uVd6CPl
u1C5BMbHVnRmBzVgXmTVN+/sxc8EsVCrXZJ1tQgLa1kVTLU6KdpU1a8yin30Ki2R
cgdCLSzjjlL1StMkHNuWV1Fr8L3pCUc7m9XpNJbJ6bnzCDonbHeZjESJmqJVw6nk
zRlcHFhlhRYqa57Kj0ABbr8M5z41nxPtNq8U31tYqx63mKNAhAZvjLIQ7hMXXE9V
9JxyTygrafgUCkKbdpVdoMDr0F1PLm/JZn22rqvn+UDCIeYD0/CO3yiqdqIX3X1n
3KQs4aeJgEc0CgJBWyiKBZFc3GYigbf+5XWzKQs7UnnzGa3jpRpI6eJ9CiqmLpp7
zjsnwdlQWAe9gtWqXKFHLpnnQ2IznmV+XVAanAtjBXhlXYecMfBB1ZhMthIns/Ke
wXeq+6T0jcFhm3hqXkz59awhcMuGpqbkLTmi
=UGo+
-END PGP SIGNATURE End Message ---

Bug#1021892: pmw: autopkgtest regression: [stavelines ] is deprecated; use [stave m/] instead

[Paul Gevers]

Source: pmw
Version: 1:5.20-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
pmwfrom testing1:5.20-1
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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=pmw

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pmw/27178828/log.gz

doc/examples/ex44
PMW version 5.20
** Warning: [stavelines ] is deprecated; use [stave m/] instead
   Detected near line 6 of doc/examples/ex44
[stave 1 hclef 0 stavelines 1]
->


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1021891: rsass: autopkgtest regression: no matching package named `arc-swap` found

[Paul Gevers]

Source: rsass
Version: 0.26.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
rsass  from testing0.26.0-1
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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=rsass

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rsass/27178838/log.gz

debian cargo wrapper: options, profiles, parallel: ['parallel=64'] [] 
['-j64']
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
x86_64-linux-gnu
debian cargo wrapper: linking /usr/share/cargo/registry/* into 
/tmp/tmp.3vENjMmwHj/registry/
debian cargo wrapper: options, profiles, parallel: ['parallel=64'] [] 
['-j64']
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
x86_64-linux-gnu
debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', 
'/usr/bin/cargo', '-Zavoid-dev-deps', 'test', '--verbose', '--verbose', 
'-j64', '--target', 'x86_64-unknown-linux-gnu', '--all-targets'],) {}

error: no matching package named `arc-swap` found
location searched: registry `crates-io`
required by package `rsass v0.26.0 (/usr/share/cargo/registry/rsass-0.26.0)`
autopkgtest [08:19:18]: test librust-rsass-dev:default



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1006022: closed by Pirate Praveen (already fixed in 5.6.4-1)

[Paul Gevers]

Control: reopen -1

Hi Pirate,

On 16-10-2022 18:03, Debian Bug Tracking System wrote:

Subject:
already fixed in 5.6.4-1
From:
Pirate Praveen 
Date:
16-10-2022 18:00

To:
1006022-d...@bugs.debian.org


closing


I'm not convinced. To give some examples:

https://ci.debian.net/data/autopkgtest/testing/amd64/p/puma/26957707/log.gz

autopkgtest [12:18:03]:  apt-source puma
Get:1 http://deb.debian.org/debian testing/main puma 5.6.4-1 (dsc) [2,087 B]
Get:2 http://deb.debian.org/debian testing/main puma 5.6.4-1 (tar) [311 kB]
Get:3 http://deb.debian.org/debian testing/main puma 5.6.4-1 (diff) 
[9,004 B]


[...]

  1) Error:
TestIntegrationSingle#test_hot_restart_does_not_drop_connections:
Errno::EBADF: Bad file descriptor

/tmp/autopkgtest-lxc.8ydn8oqp/downtmp/build.4F8/src/test/helpers/integration.rb:50:in 
`close'


/tmp/autopkgtest-lxc.8ydn8oqp/downtmp/build.4F8/src/test/helpers/integration.rb:50:in 
`teardown'


/tmp/autopkgtest-lxc.8ydn8oqp/downtmp/build.4F8/src/test/helper.rb:90:in 
`block (5 levels) in run'


/tmp/autopkgtest-lxc.8ydn8oqp/downtmp/build.4F8/src/test/helper.rb:90:in 
`each'


/tmp/autopkgtest-lxc.8ydn8oqp/downtmp/build.4F8/src/test/helper.rb:90:in 
`block (4 levels) in run'

/usr/lib/ruby/3.0.0/timeout.rb:97:in `block in timeout'
/usr/lib/ruby/3.0.0/timeout.rb:107:in `timeout'

/tmp/autopkgtest-lxc.8ydn8oqp/downtmp/build.4F8/src/test/helper.rb:89:in 
`block (3 levels) in run'


418 runs, 1135 assertions, 0 failures, 1 errors, 6 skips


https://ci.debian.net/data/autopkgtest/testing/arm64/p/puma/24007200/log.gz

autopkgtest [21:22:10]:  apt-source puma
Get:1 http://deb.debian.org/debian testing/main puma 5.6.4-1 (dsc) [2,087 B]
Get:2 http://deb.debian.org/debian testing/main puma 5.6.4-1 (tar) [311 kB]
Get:3 http://deb.debian.org/debian testing/main puma 5.6.4-1 (diff) 
[9,004 B]


[...]

  1) Failure:
TestBusyWorker#test_multiple_requests_waiting_on_less_busy_worker 
[/tmp/autopkgtest-lxc.vmusro6g/downtmp/build.DoB/src/test/test_busy_worker.rb:80]:

maximum number of concurrent requests needs to be 1.
Expected: 1
  Actual: 2

418 runs, 1125 assertions, 1 failures, 0 errors, 6 skips


https://ci.debian.net/data/autopkgtest/testing/armel/p/puma/26313576/log.gz

autopkgtest [19:18:01]:  apt-source puma
Get:1 http://deb.debian.org/debian testing/main puma 5.6.4-1 (dsc) [2,087 B]
Get:2 http://deb.debian.org/debian testing/main puma 5.6.4-1 (tar) [311 kB]
Get:3 http://deb.debian.org/debian testing/main puma 5.6.4-1 (diff) 
[9,004 B]


[...]

  1) Failure:
TestPumaServer#test_not_drain_on_shutdown 
[/tmp/autopkgtest-lxc.4nhbkp68/downtmp/build.fbR/src/test/test_puma_server.rb:1341]:

Expected 0 to not be equal to 0.

418 runs, 1141 assertions, 1 failures, 0 errors, 6 skips



OpenPGP_signature
Description: OpenPGP digital signature

Bug#994348: python-apt: diff for NMU version 2.3.0+nmu1

[Micha Lenk]

Hi all,

I just realized an alternative implementation was already contributed by 
Michael Vogt on salsa.d.o


https://salsa.debian.org/apt-team/python-apt/-/merge_requests/67

Good to see he ended up with almost the same implementation as I did.

Regards,
Micha

Processed: Bug#1021882 marked as pending in ros2-rosidl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1021882 [src:ros2-rosidl] ros2-rosidl: FTBFS on mipsel: test failures
Ignoring request to alter tags of bug #1021882 to the same tags previously set

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

Bug#1021882: marked as pending in ros2-rosidl

[Timo Röhling]

Control: tag -1 pending

Hello,

Bug #1021882 in ros2-rosidl 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/robotics-team/ros2-rosidl/-/commit/299cae457fc52a928d8c793715c4971b30e82f45


Rebuild against ros2-ament-lint with increased timeouts

Closes: #1021882


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1021882

Processed: Re: Bug#1006022 closed by Pirate Praveen (already fixed in 5.6.4-1)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1006022 {Done: Pirate Praveen } [src:puma] puma: 
flaky tests
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions puma/5.6.4-1.

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

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

[Debian Bug Tracking System]

Your message dated Sun, 16 Oct 2022 17:47:28 +
with message-id 
and subject line Bug#999219: fixed in xcolmix 1.07-10.1
has caused the Debian Bug report #999219,
regarding xcolmix: 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.)


-- 
999219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999219
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xcolmix
Version: 1.07-10
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: xcolmix
Source-Version: 1.07-10.1
Done: Chris Lamb 

We believe that the bug you reported is fixed in the latest version of
xcolmix, 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.
Chris Lamb  (supplier of updated xcolmix 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, 06 Oct 2022 09:41:37 -0700
Source: xcolmix
Binary: xcolmix xcolmix-dbgsym
Architecture: source amd64
Version: 1.07-10.1
Distribution: unstable
Urgency: medium
Maintainer: Peter S Galbraith 
Changed-By: Chris Lamb 
Description:
 xcolmix- an RGB colour mixer
Closes: 988018 999219 1020748
Changes:
 xcolmix (1.07-10.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add missing required debian/rules targets build-arch and/or build-indep.
 (Closes: #999219)
   * Apply a patch by Helmut Grohne to correctly pass cross-building tools to
 Make. (Closes: #988018)
   * Make the build reproducible by adapting debian/rules to use CFLAGS from
 dpkg-buildflags(1), appending -ffile-prefix-map. (Closes: #1020748)
Checksums-Sha1:
 eec8271609504f02ce9714d5b40f1ebad77e0ca6 1670 xcolmix_1.07-10.1.dsc
 476f69c3bec8d3b37ab4fa945c7f12368b3f62ac 16460 xcolmix_1.07.orig.tar.gz
 aa619ccf44ec52af24e11cc92d9e884549ded633 4368 xcolmix_1.07-10.1.debian.tar.xz
 9066d1309678a67425f1b216ae4d1cd8320a5d92 21628 
xcolmix-dbgsym_1.07-10.1_amd64.deb
 ae76b30965b017e672e582d8e1deb7efaea1cf74 6469 xcolmix_1.07-10.1_amd64.buildinfo
 87d8c01d3537a96e362b80c6b80541d61b28a4a1 11772 xcolmix_1.07-10.1_amd64.deb
Checksums-Sha256:
 c4a2290a54bdca64115c503f79b1b7e351c646bb9bbd4a7d77179ec824025ec0 1670 
xcolmix_1.07-10.1.dsc
 1955698b1d9e62d9af8eef8f544e4509025785c49bef914296fa90987780ef17 16460 
xcolmix_1.07.orig.tar.gz
 0beb159d6e84b2c6111d362e8cfd1684d2d7fad6fc8501e37c6564292b0e7b41 4368 
xcolmix_1.07-10.1.debian.tar.xz
 9d40c34d306aa44c30a1d2a6e9dc381201445a1d9d66af020f5a7626f9a90bff 21628 
xcolmix-dbgsym_1.07-10.1_amd64.deb
 dcd014125f7481e7deeddb6c130a48faa6fe03290e94269afcef726bb71e795f 6469 
xcolmix_1.07-10.1_amd64.buildinfo
 1d143934a5359972def659e281e2c0dd99db71f24daf231130f6db1d35a7db92 11772 
xcolmix_1.07-10.1_amd64.deb
Files:
 ee4cdaab056d09129df4b598a992 1670 utils optional xcolmix_1.07-10.1.dsc
 8b1b3d5a012415cb402c0c7da8dd3423 16460 utils optional xcolmix_1.07.orig.tar.gz
 f2789239239768389194eafc2bebcc92 4368 utils optional 
xcolmix_1.07-10.1.debian.tar.xz
 c712cb1a57798b1f2a02b93c1bdb04ed 21628 debug optional 
xcolmix-dbgsym_1.07-10.1_amd64.deb
 b8b9d543f0c086dcecfe13babf476060 6469 utils optional 
xcolmix_1.07-10.1_amd64.buildinfo
 a6106110eae9d1056ccf0980fb228dd4 11772 utils optional 
xcolmix_1.07-10.1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAmM/B08ACgkQHpU+J9Qx

Bug#1021889: pylint breaks pylint-django autopkgtest: ScopeConsumer.__new__() missing 1 required positional argument: 'scope_type'

[Paul Gevers]

Source: pylint, pylint-django
Control: found -1 pylint/2.15.3-1
Control: found -1 pylint-django/2.0.13-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
pylint from testing2.15.3-1
pylint-django  from testing2.0.13-2
all others from testingfrom testing

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

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pylint-django/27163271/log.gz

Running “django-admin startproject testproject”
Running “django-admin startapp testapp”
Running “pylint --version”
pylint 2.15.3
astroid 2.12.10
Python 3.10.7 (main, Sep  8 2022, 14:34:29) [GCC 12.2.0]
Running “pylint -E --load-plugins=pylint_django testapp/”
Exception on node  in file 
'/tmp/autopkgtest-lxc.6ld_wzc5/downtmp/autopkgtest_tmp/testproject/testapp/__init__.py'

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/pylint/utils/ast_walker.py", 
line 95, in walk

callback(astroid)
  File 
"/usr/lib/python3/dist-packages/pylint_django/augmentations/__init__.py", 
line 739, in wrap_func

return with_method(orig_method, *args, **kwargs)
  File 
"/usr/lib/python3/dist-packages/pylint_django/augmentations/__init__.py", 
line 317, in ignore_import_warnings_for_related_fields
consumer._atomic = ScopeConsumer(new_things, consumer.consumed, 
consumer.scope_type)  # pylint: disable=W0212
TypeError: ScopeConsumer.__new__() missing 1 required positional 
argument: 'scope_type'
Can't write the issue template for the crash in 
/home/debci/.cache/pylint/pylint-crash-2022-10-16-06-16-20.txt because 
of: '[Errno 2] No such file or directory: 
'/home/debci/.cache/pylint/pylint-crash-2022-10-16-06-16-20.txt''

Here's the content anyway:
First, please verify that the bug is not already filled:
https://github.com/PyCQA/pylint/issues/

Then create a new crash issue:
https://github.com/PyCQA/pylint/issues/new?assignees==crash%2Cneeds+triage=BUG-REPORT.yml


Issue title:
Crash  (if possible, be more specific about what made pylint crash)
Content:
When parsing the following file:



```python

```

pylint crashed with a ``AstroidError`` and with the following stacktrace:
```
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/pylint/lint/pylinter.py", line 
782, in _lint_file

check_astroid_module(module)
  File "/usr/lib/python3/dist-packages/pylint/lint/pylinter.py", line 
1049, in check_astroid_module

retval = self._check_astroid_module(
  File "/usr/lib/python3/dist-packages/pylint/lint/pylinter.py", line 
1099, in _check_astroid_module

walker.walk(node)
  File "/usr/lib/python3/dist-packages/pylint/utils/ast_walker.py", 
line 95, in walk

callback(astroid)
  File 
"/usr/lib/python3/dist-packages/pylint_django/augmentations/__init__.py", 
line 739, in wrap_func

return with_method(orig_method, *args, **kwargs)
  File 
"/usr/lib/python3/dist-packages/pylint_django/augmentations/__init__.py", 
line 317, in ignore_import_warnings_for_related_fields
consumer._atomic = ScopeConsumer(new_things, consumer.consumed, 
consumer.scope_type)  # pylint: disable=W0212
TypeError: ScopeConsumer.__new__() missing 1 required positional 
argument: 'scope_type'


The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/pylint/lint/pylinter.py", line 
747, in _lint_files

self._lint_file(fileitem, module, check_astroid_module)
  File "/usr/lib/python3/dist-packages/pylint/lint/pylinter.py", line 
784, in _lint_file

raise astroid.AstroidError from e
astroid.exceptions.AstroidError
```
.
* Module testapp
testapp/__init__.py:1:0: F0002: testapp/__init__.py: Fatal error while 
checking 'testapp/__init__.py'. Please open an issue in our bug tracker 
so we address this. There is a pre-filled template that you can use in 
'/home/debci/.cache/pylint/pylint-crash-2022-10-16-06-16-20.txt'. 
(astroid-error)
Can't write the issue template for the crash in 
/home/debci/.cache/pylint/pylint-crash-2022-10-16-06-16-20.txt because 
of: '[Errno 2] No such file or directory: 

Processed: pylint breaks pylint-django autopkgtest: ScopeConsumer.__new__() missing 1 required positional argument: 'scope_type'

[Debian Bug Tracking System]

Processing control commands:

> found -1 pylint/2.15.3-1
Bug #1021889 [src:pylint, src:pylint-django] pylint breaks pylint-django 
autopkgtest: ScopeConsumer.__new__() missing 1 required positional argument: 
'scope_type'
Marked as found in versions pylint/2.15.3-1.
> found -1 pylint-django/2.0.13-2
Bug #1021889 [src:pylint, src:pylint-django] pylint breaks pylint-django 
autopkgtest: ScopeConsumer.__new__() missing 1 required positional argument: 
'scope_type'
Marked as found in versions pylint-django/2.0.13-2.

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

Processed: block 976052 with 1021888

[Debian Bug Tracking System]

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

> block 976052 with 1021888
Bug #976052 [wnpp] ITP: zola -- static site generator
976052 was blocked by: 984864 1013117 1013118 1021887 1009888 1013116 1013115 
1013121 1013120 1013119 1021880
976052 was not blocking any bugs.
Added blocking bug(s) of 976052: 1021888
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

Your message dated Sun, 16 Oct 2022 17:39:26 +
with message-id 
and subject line Bug#998978: fixed in mailto 1.3.2-3.1
has caused the Debian Bug report #998978,
regarding mailto: 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.)


-- 
998978: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998978
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mailto
Version: 1.3.2-3
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: mailto
Source-Version: 1.3.2-3.1
Done: Chris Lamb 

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated mailto 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, 06 Oct 2022 09:26:08 -0700
Source: mailto
Binary: mailto
Architecture: source amd64
Version: 1.3.2-3.1
Distribution: unstable
Urgency: medium
Maintainer: Martin Schulze 
Changed-By: Chris Lamb 
Description:
 mailto - WWW Forms to Mail Gateway
Closes: 777413 998978
Changes:
 mailto (1.3.2-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Implement the required build-arch and build-indep targets in debian/rules.
 (Closes: #998978)
   * Make the build reproducible by adding "-n" to the gzip(1) invocation.
 (Closes: #777413)
Checksums-Sha1:
 8a1b00708be52e0f7eeca5411e9fc943d1054e50 1591 mailto_1.3.2-3.1.dsc
 89632a615167593ffa49fc7a0e91cd4d853aa0c0 15751 mailto_1.3.2.orig.tar.gz
 d51b08ecd5cc915a0346aa20c53ce345b5de9a1c 14703 mailto_1.3.2-3.1.diff.gz
 92c8fa373709fecd1572a0eb734d681b647a0c9e 4760 mailto_1.3.2-3.1_amd64.buildinfo
 cb3d8f2b78585f07dd2f4469987e88f9f755ac6a 15972 mailto_1.3.2-3.1_amd64.deb
Checksums-Sha256:
 80af41dff0929ec60c39bbf382cfee0a6442bb2bada4fd95bb7952c35334d35d 1591 
mailto_1.3.2-3.1.dsc
 74050d4dae4b3f32ba9f5069251394887b6f044f8c68ef49a0e350876d0d1c99 15751 
mailto_1.3.2.orig.tar.gz
 36269f58a48446638ffdc5ad1ec84456505e77c087935cf79c35a84085b4da8f 14703 
mailto_1.3.2-3.1.diff.gz
 2796c845193d94454a8a9efd2ce04a8ce3b56f6201fa366808b44bfc401d1e9a 4760 
mailto_1.3.2-3.1_amd64.buildinfo
 8931b6ef80f4204bea3e8f0965f60da1730693a7cf3df40bd82240818df4cc1f 15972 
mailto_1.3.2-3.1_amd64.deb
Files:
 f0fce0e0cb6e009b94abcdeade50cf24 1591 web optional mailto_1.3.2-3.1.dsc
 87f2ac30b5133bcfca1ffd69ce8ab5e7 15751 web optional mailto_1.3.2.orig.tar.gz
 8d68eaa489aa6b0c68f188ed88f84bcc 14703 web optional mailto_1.3.2-3.1.diff.gz
 eb14d689239431785535c7e88f9c 4760 web optional 
mailto_1.3.2-3.1_amd64.buildinfo
 189467ce219bdd78db2bc1d8d4153003 15972 web optional mailto_1.3.2-3.1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAmM/AtcACgkQHpU+J9Qx
HliMjBAAsHyfFyhxCHqJjrstcFFtp0p2FlqRojONy8VGPw0MgO5lMF8jxODCzgKF
j9b19WgS51hopdBlpFTcJN2lY4489S2TdTWLs7dCqREEzhVOFUUAgKMf5rdG2l60
xt5zc6fcG27dhpaC5DDVpUzQAySe8Ut34+9hE6DzcUu0jxqKWPen1I58krvDu4KO
vjZQBCrFCxwC/iNlUm5dZRsp/nBGrotqPHI5052JOOV+SlxndjJfhdfKrTTnMQiW
Opgmg7Wjgi1X0cyBSCobiJyzJVmCxUUj+P89JFG02wiDkPChx9WP/buenn9Sti25
z7GBVNeFyHyEnmC+uIobywLZw01cc94jvpdhEVxuwFJPyyz6+AP4zu5qiVerOPgH
Lr4P7whGSbObJGUBY54JawdF8/ghF5L2PCs4HR4yeZAt6rua5MXKlfi2L6GYVQE3
qTmRPwqKfqtNycncn81vagwlH1L0ygddw/PVuXpc1QIN4DI1T9IP7yaM+ZoT0hqL

Processed: Bug#1021882 marked as pending in ros2-rosidl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1021882 [src:ros2-rosidl] ros2-rosidl: FTBFS on mipsel: test failures
Added tag(s) pending.

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

Bug#1021882: marked as pending in ros2-rosidl

[Timo Röhling]

Control: tag -1 pending

Hello,

Bug #1021882 in ros2-rosidl 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/robotics-team/ros2-rosidl/-/commit/f8133a1922fb67aa1b35e8b00985efec97efe1cc


Skip useless linter tests

Closes: #1021882


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1021882

Bug#1019999: marked as done (graph-tool: FTBFS: ax_python_devel serial 32 fails)

[Debian Bug Tracking System]

Your message dated Sun, 16 Oct 2022 17:38:42 +
with message-id 
and subject line Bug#101: fixed in graph-tool 2.45+ds-8
has caused the Debian Bug report #101,
regarding graph-tool: FTBFS: ax_python_devel serial 32 fails
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> checking for python3 script directory (pythondir)... 
> ${PYTHON_PREFIX}/lib/python3.10/site-packages
> checking for python3 extension module directory (pyexecdir)... 
> ${PYTHON_EXEC_PREFIX}/lib/python3.10/site-packages
> checking for python3.10... (cached) /usr/bin/python3
> checking for a version of Python >= '2.1.0'... yes
> checking for a version of Python == '3.10.7'... no
> configure: error: this package requires Python == '3.10.7'.
> If you have it installed, but it isn't the default Python
> interpreter in your system path, please pass the PYTHON_VERSION
> variable to configure. See ``configure --help'' for reference.
> 
>   cd _BUILD && tail -v -n \+0 config.log


The full build log is available from:
http://qa-logs.debian.net/2022/09/17/graph-tool_2.45+ds-7_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: graph-tool
Source-Version: 2.45+ds-8
Done: Jerome Benoit 

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

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

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

Debian distribution maintenance software
pp.
Jerome Benoit  (supplier of updated graph-tool 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: Sun, 16 Oct 2022 16:59:25 +
Source: graph-tool
Architecture: source
Version: 2.45+ds-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Jerome Benoit 
Closes: 101
Changes:
 graph-tool (2.45+ds-8) unstable; urgency=medium
 .
   * FTBFS fix release, provide a fixed version of ax_python_devel.m4
 (see #1020747; closes: #101).
Checksums-Sha1:
 4bc1cc5bca30a38dea797276ce27890c5adca61a 3761 graph-tool_2.45+ds-8.dsc
 9d1f4642c3a8aa70abe1fddef157966ae75d0925 365696 
graph-tool_2.45+ds-8.debian.tar.xz
 4d979fa1c83a58a63f06546a3486e64c7f7ade6e 15614 
graph-tool_2.45+ds-8_source.buildinfo
Checksums-Sha256:
 fd6ddc7a8ad158e31bdd68eca7f39b8141a86340c363dcce203f5b530bd6ab22 3761 
graph-tool_2.45+ds-8.dsc
 8193cfd62806a210aec58fe1bac512f5332bf417db8b0b0784ac092a10487ccc 365696 
graph-tool_2.45+ds-8.debian.tar.xz
 9fd1660e611ba65de126b566cdc405ba90fcc0a0880effaa653cbd4778647e42 15614 
graph-tool_2.45+ds-8_source.buildinfo
Files:
 555be2918ad6cd06778d8e7cd7820a41 3761 python optional graph-tool_2.45+ds-8.dsc
 9e73117340e434127ac76cb6d6bd839a 365696 python optional 
graph-tool_2.45+ds-8.debian.tar.xz
 04722addf4a21bcac3f3106c611406ed 15614 python optional 
graph-tool_2.45+ds-8_source.buildinfo

-BEGIN PGP SIGNATURE-

iQRJBAEBCgAzFiEEriiuFXEN/x2H5adiP5IZpn82xosFAmNMOx0VHGNhbGN1bHVz
QHJlem96ZXIubmV0AAoJED+SGaZ/NsaLoGsf+gOMcgkHUWwuP8nD9PFihDgOTGdr
ks2Gbqcr8inw8YLxA4yrJb8A6UbDBl4/krEqZae95Lta0dXXBXjzr56Pspyowg3P

Processed: Re: ncurses-hexedit: FTBFS: init.c:390:10: error: format not a string literal and no format arguments [-Werror=format-security]

[Debian Bug Tracking System]

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

> user debian-rele...@lists.debian.org
Setting user to debian-rele...@lists.debian.org (was rei...@reiner-h.de).
> usertags 997184 + bsp-2022-10-de-karlsruhe
There were no usertags set.
Usertags are now: bsp-2022-10-de-karlsruhe.
> tags 997184 + patch
Bug #997184 [src:ncurses-hexedit] ncurses-hexedit: FTBFS: init.c:390:10: error: 
format not a string literal and no format arguments [-Werror=format-security]
Added tag(s) patch.
> thank you
Stopping processing here.

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

Bug#997184: ncurses-hexedit: FTBFS: init.c:390:10: error: format not a string literal and no format arguments [-Werror=format-security]

[Reiner Herrmann]

user debian-rele...@lists.debian.org
usertags 997184 + bsp-2022-10-de-karlsruhe
tags 997184 + patch
thank you

Hi,

the attached patch fixes the build errors caused by the new
GCC version.

Kind regards,
  Reiner
From 8525b3f41ef3acf2130167cc0072c38452253cc0 Mon Sep 17 00:00:00 2001
From: Reiner Herrmann 
Date: Sun, 16 Oct 2022 19:32:38 +0200
Subject: [PATCH] Fix FTBFS with GCC 12

Closes: #997184
---
 debian/patches/gcc12.patch | 246 +
 debian/patches/series  |   1 +
 2 files changed, 247 insertions(+)
 create mode 100644 debian/patches/gcc12.patch

diff --git a/debian/patches/gcc12.patch b/debian/patches/gcc12.patch
new file mode 100644
index 000..540c788
--- /dev/null
+++ b/debian/patches/gcc12.patch
@@ -0,0 +1,246 @@
+Author: Reiner Herrmann 
+Bug-Debian: https://bugs.debian.org/997184
+Description: Fix FTBFS with GCC 12
+ - make sure global variables are declared in only one place
+   to fix "multiple definition" linking errors
+ - use fixed format string to prevent format string vulnerabilities
+
+--- a/src/hexedit.h
 b/src/hexedit.h
+@@ -343,7 +343,7 @@
+ 
+ 
+/* Global structure, keep most global variables here. */
+-struct
++struct Global
+ {
+WINDOW *wmain, *wstatus, *whelp; /* three windows used throughout. */
+unsigned long filesize;  /* size of the file buffer. */
+@@ -365,7 +365,7 @@
+ /* buf end. */
+int beeping; /* Allow beeping or not. */
+int help_msg_count;  /* Number of messages in help menu. */
+-} Globals;
++};
+ 
+ 
+ struct foundit
+@@ -400,7 +400,7 @@
+int s;
+struct Change *base;
+struct Change *top;
+-} UndoStack;
++};
+ 
+ 
+ struct FileNames
+--- a/src/init.c
 b/src/init.c
+@@ -35,6 +35,9 @@
+ 
+ extern char **environ;
+ 
++struct Global Globals;
++extern struct ChangeLog UndoStack;
++
+ 
+/* This is called once at the start of the program.  Handles HEXEDIT
+ * Environment variable, command line arguments, sets up signal
+@@ -385,7 +388,7 @@
+  box (wpopup, 0, 0);
+  wmove (wpopup, 1, (FILE_ERR_WIDTH / 2)
+  - (strlen (msg) / 2));
+- wprintw (wpopup, (char *) msg);
++ wprintw (wpopup, "%s", (char *) msg);
+  wmove (wpopup, FILE_ERR_HEIGHT - 3, (FILE_ERR_WIDTH / 2) -
+ (strlen (strerror (errno)) + strlen ("Reason: ")) / 2);
+  wprintw (wpopup, "Reason: %s", 
+--- a/src/misc.c
 b/src/misc.c
+@@ -26,6 +26,8 @@
+ #endif
+ #endif
+ 
++extern struct Global Globals;
++extern struct ChangeLog UndoStack;
+ 
+ int
+ mappos (int pos)
+--- a/src/undo.c
 b/src/undo.c
+@@ -15,6 +15,8 @@
+ #include "hexedit.h"
+ #include 
+ 
++struct ChangeLog UndoStack;
++extern struct Global Globals;
+ 
+ void
+ pushUndo (int type, unsigned long offset,
+--- a/src/widgets.c
 b/src/widgets.c
+@@ -14,6 +14,8 @@
+ 
+ #include "hexedit.h"
+ 
++extern struct Global Globals;
++
+ #define S_BOX_COLOR  (COLOR_PAIR(4) | A_BOLD)
+ 
+ 
+@@ -366,7 +368,7 @@
+if (!rstr.str)
+{
+   wmove (win, 4, boxleft);
+-  wprintw (win, (char *) NOT_ENOUGH_MEMORY);
++  wprintw (win, "%s", (char *) NOT_ENOUGH_MEMORY);
+   getch ();
+   return NULL;
+}
+--- a/src/windows.c
 b/src/windows.c
+@@ -14,6 +14,7 @@
+ 
+ #include "hexedit.h"
+ 
++extern struct Global Globals;
+ 
+/* Brings up Jump to offset window, to relocate to a different part
+ * of the file.  Uses one string box and takes input in octal, decimal, 
+--- a/src/calc.c
 b/src/calc.c
+@@ -14,6 +14,8 @@
+ 
+ #include "hexedit.h"
+ 
++extern struct Global Globals;
++
+/* Used only for redraw function after Control-C */
+ struct calcEntryBox *bbox;
+ struct calcEntryBox *obox;
+--- a/src/print.c
 b/src/print.c
+@@ -14,6 +14,8 @@
+ 
+ #include "hexedit.h"
+ 
++extern struct Global Globals;
++
+ static long findNewline   (unsigned long);
+ static void drawAscii (unsigned long off);
+ static void drawAsciiDump (unsigned long, unsigned long *);
+--- a/src/calckeys.c
 b/src/calckeys.c
+@@ -14,6 +14,7 @@
+ 
+ #include "hexedit.h"
+ 
++extern struct Global Globals;
+ 
+ void
+ calcNumberKey (struct calcEntryBox *binbox, struct calcEntryBox *octbox,
+--- a/src/edit.c
 b/src/edit.c
+@@ -15,6 +15,8 @@
+ #include "hexedit.h"
+ #include 
+ 
++extern struct Global Globals;
++
+ /* The routines in this file are very messy and ugly and not much thought
+  * went into thinking how to minimize the amount of code, I only did it
+  * real fast, making every case I could think of a separate code block,
+--- a/src/file.c
 b/src/file.c
+@@ -30,6 +30,8 @@
+ 
+ #include "hexedit.h"
+ 
++extern struct Global Globals;
++
+ struct FileNames *fp = NULL; /* used to traverse the list of files */
+ struct FileNames **pages = NULL; /* node that starts a new page */
+ int current_page = 0;
+--- a/src/filebuf.c
 b/src/filebuf.c
+@@ -15,6 +15,7 @@
+ #include "hexedit.h"
+ 

Bug#1019365: marked as done (qml-module-lomiri-settings-fingerprint : Depends: qml-module-biometryd but it is not installable)

[Debian Bug Tracking System]

Your message dated Sun, 16 Oct 2022 17:00:10 +
with message-id 
and subject line Bug#1019365: fixed in biometryd 0.0.3~git20221003.39b529a-1
has caused the Debian Bug report #1019365,
regarding qml-module-lomiri-settings-fingerprint : Depends: 
qml-module-biometryd but it is not installable
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.)


-- 
1019365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019365
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qml-module-lomiri-settings-fingerprint
Version: 1.0.0-3
Severity: grave
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic

The qml-module-lomiri-settings-fingerprint package is uninstallable because
it depends on qml-module-biometryd which does not exist in unstable, nor has
it been uploaded to the NEW queue.

Please upload qml-module-biometryd, or drop the dependency, or drop the
binary package.

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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: biometryd
Source-Version: 0.0.3~git20221003.39b529a-1
Done: Mike Gabriel 

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

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

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated biometryd 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, 04 Oct 2022 01:05:53 +0200
Source: biometryd
Binary: biometryd-bin biometryd-bin-dbgsym libbiometry-dev libbiometry1 
libbiometry1-dbgsym qml-module-biometryd qml-module-biometryd-dbgsym
Architecture: source amd64
Version: 0.0.3~git20221003.39b529a-1
Distribution: unstable
Urgency: medium
Maintainer: Debian UBports Team 
Changed-By: Mike Gabriel 
Description:
 biometryd-bin - biometryd mediates/multiplexes to biometric devices - 
daemon/help
 libbiometry-dev - biometryd mediates/multiplexes to biometric devices - 
development
 libbiometry1 - biometryd mediates/multiplexes to biometric devices - runtime 
lib
 qml-module-biometryd - biometryd mediates/multiplexes to biometric devices - 
QML binding
Closes: 1019365 1021212
Changes:
 biometryd (0.0.3~git20221003.39b529a-1) unstable; urgency=medium
 .
   * Initial upload to Debian. (Closes: #1021212, #1019365).
 .
   * debian/patches/:
 + Add 1001_CMake-Werror-option.patch.
 + Add 2001_no-lxc-android-config-service-in-Debian.patch. Don't want
   lxc-android-config.service. We don't/won't have that in Debian, for now.
   * debian/:
 + Rename libbiometryd* pkgs to libbiometry* and make lib:pkg and dev:pkg
   match the library's SONAME.
   * debian/{control,compat}:
 + Switch to debhelper-compat notation, bump to DH compat level version 13.
   * debian/control:
 + Drop top comment. Not true for biometryd in Debian: the control
   file does not get auto-generated (any more).
 + Bump Standards-Version: to 4.6.1. No changes needed.
 + Drop from B-D: qt5-default.
 + Adjust Vcs-*: fields for Debian.
 + Update Maintainer: field for official Debian upload. Add Uploaders: 
field.
 + Add Rules-Requires-Root: field and set it to 'no'.
 + Line-wrap too-long extended descriptions.
 + Make biometryd-bin multi-arch: foreign.
 + Disentangle circular dependency between biometryd-bin <-> libbiometryd1.
 + Add B-D: pkg-kde-tools.
   * debian/{control,copyright}:
 + Update homepage URL.
   * debian/rules:
 + Adapt to building with DH compat level 13.
 + Add get-orig-source target.
 + Build with -DENABLE_WERROR=OFF.
 + Amend broken install target for include/biometryd/.
 + Enable all hardening flags.
 + Build with pkgkde_symbolshelper.
 + Don't run tests in parallel.
   * debian/{rules,biometryd-bin.install}:
 + Don't install upstart configuration.
   * 

Bug#1021888: librust-deflate-dev: impossible to install

[Jonas Smedegaard]

Package: librust-deflate-dev
Version: 1.0.0-1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package is impossible to install: Depends on missing package 
librust-gzip-header-1+default-dev

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmNMOEQACgkQLHwxRsGg
ASHSFw/+LViZjDgukHKs4L/lU28HGvX9w/oM5ipGKgsrEM0J4kcT6Om6yzg2CCCl
Ss7IZg9zx5kVr2O45Bxo2jl+NDh51WocsiT/tjlOmF8EoPylXlJfxpfIuIvvNArW
GNpt9FhSTzYOIohEf/QWYiC2cdwWA+lek0qyhUPIjaa+1B/j4aSxlbwAwYnr33YN
8t329wAKyhbRDJVRDKeWsspqYAIC7AiVxMOF1EJ/TPjRtA64FBUZkn0NXoCZek9c
LocZSqaSvgiRibhEb/ifDndmkncY2TCt7cvbhjcB9UvGbxiiIRFRnR+W8SrEHEqf
w9ED6rE//jhT3/GYlZ6UaK9b64CbrT7VX5Hkl35NexO2tUucCSgORCetCEdcNsly
j6UV1/3v5KYbX3gRGCvQJO/3zNcEmZlQ88Nt6CbHiQBwbGfpztja7R+v7p2MK63P
fr/GIFE5V08f6pQe0PtDcbjRtFvxx6jA7vO1yg1lz3Bh0UYnGCrwpnLMn67LrF8C
rqfQx0vZyl4dhvQDFrL/56WNETgcJcXyPEdr8UCHHGm+tABzAhogtUwZYtcIS5m7
hXKSY7o1uOY8/hU1WDi9rVV79TFBXYoZTPjZrmUo5tKKBOcUCu6LOzF/hlXJnEEO
YMSe5FpL7WtgmUZ70qrZOnHIPid7Aw48RJccBrZ7stP8g/xhjDU=
=RAGB
-END PGP SIGNATURE-

Processed: Re: AM_PATH_PYTHON

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 autoconf-archive
Bug #1020747 [automake] autoconf-archive: ax_python_devel serial 32 fails with 
current Sid python3
Bug reassigned from package 'automake' to 'autoconf-archive'.
Ignoring request to alter found versions of bug #1020747 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1020747 to the same values 
previously set
> tags -1 patch
Bug #1020747 [autoconf-archive] autoconf-archive: ax_python_devel serial 32 
fails with current Sid python3
Added tag(s) patch.

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

Bug#1020747: AM_PATH_PYTHON

[Jerome BENOIT]

control: reassign -1 autoconf-archive
control: tags -1 patch

I have just doublechecked: the bug does lie in autoconf-archive .

The faulty code was introduce in commit df89f6cdaade38f3c1c9987be0c5a57c96fc1730
https://github.com/autoconf-archive/autoconf-archive/commit/df89f6cdaade38f3c1c9987be0c5a57c96fc1730

The current code tuple(sys.version_info) gives the 5-tuple (3, 10, 7, 'final', 
0) while
the former code sys.version.split()[0] would give the 3-tuple (3, 10, 7).
So, at first glance, the current code tuple(sys.version_info) should be 
replaced by
tuple(sys.version_info)[:3].

A patch that applied to the current ax_python_devel serial 32 is attached.

Best wishes,
Jerome


On Fri, 30 Sep 2022 14:31:47 + Bastien =?ISO-8859-1?Q?Roucari=E8s?= 
 wrote:

control: reassign -1 automake
control: affects -1 autoconf-archive


Hi,


The macro AM_PATH_PYTHON dos not support 3 level python version...


The bug lie in automake not autoconf-archive 



Could be workarround by a little sed script in order remove micro version on graph tool 
side



Bastien


--
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B
--- ax_python_devel.m4-s32.original	2022-10-01 17:42:46.0 +0200
+++ ax_python_devel.m4	2022-10-16 18:40:38.873380357 +0200
@@ -125,7 +125,7 @@
 return tuple(map(int, s.strip().replace("rc", ".").split(".")))
 def __init__(self):
 import sys
-self.vpy = tuple(sys.version_info)
+self.vpy = tuple(sys.version_info)[[:3]]
 def __eq__(self, s):
 return self.vpy == self.vtup(s)
 def __ne__(self, s):


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1017304: libmateweather: diff for NMU version 1.26.0-1.1

[Mike Gabriel]

Hi Reiner,

On  Sa 15 Okt 2022 18:16:49 CEST, Reiner Herrmann wrote:


Control: tags 1017304 + patch
Control: tags 1017304 + pending

Dear maintainer,

I've prepared an NMU for libmateweather (versioned as 1.26.0-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards,
  Reiner


thanks for doing the NMU. I have updated the packaging Git with your .debdiff.

Greets,
Mike
--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpq0ufHocgKW.pgp
Description: Digitale PGP-Signatur

Bug#1006022: marked as done (puma: flaky tests)

[Debian Bug Tracking System]

Your message dated Sun, 16 Oct 2022 21:30:34 +0530
with message-id 
and subject line already fixed in 5.6.4-1
has caused the Debian Bug report #1006022,
regarding puma: flaky tests
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.)


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

Source: puma
Version: 5.5.2-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of you package because it was 
showing up as a regression for the upload of glibc. I noticed that the 
test regularly fails on all architectures, particularly since version 
5.5.2-2


Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

https://ci.debian.net/data/autopkgtest/testing/armhf/p/puma/19335931/log.gz

  1) Failure:
TestIntegrationSingle#test_hot_restart_does_not_drop_connections_threads 
[/tmp/autopkgtest-lxc.4tg64laj/downtmp/build.gqr/src/test/helpers/integration.rb:313]:

  0 unexpected_response
  1 refused
  0 read timeout
  0 reset
999 success
893 success after restart
  2 restart count
Expected no refused connections.
Expected: 0
  Actual: 1

412 runs, 1423 assertions, 1 failures, 0 errors, 6 skips


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

closing--- End Message ---

Bug#1014977: marked as done (libde265: CVE-2022-1253 CVE-2021-36411 CVE-2021-36410 CVE-2021-36408 CVE-2021-35452)

[Debian Bug Tracking System]

Your message dated Sun, 16 Oct 2022 15:35:49 +
with message-id 
and subject line Bug#1014977: fixed in libde265 1.0.8-1.1
has caused the Debian Bug report #1014977,
regarding libde265: CVE-2022-1253 CVE-2021-36411 CVE-2021-36410 CVE-2021-36408 
CVE-2021-35452
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.)


-- 
1014977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014977
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libde265
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for libde265.

CVE-2022-1253[0]:
| Heap-based Buffer Overflow in GitHub repository strukturag/libde265
| prior to and including 1.0.8. The fix is established in commit
| 8e89fe0e175d2870c39486fdd09250b230ec10b8 but does not yet belong to an
| official release.

https://huntr.dev/bounties/1-other-strukturag/libde265/
https://github.com/strukturag/libde265/commit/8e89fe0e175d2870c39486fdd09250b230ec10b8

CVE-2021-36411[1]:
| An issue has been found in libde265 v1.0.8 due to incorrect access
| control. A SEGV caused by a READ memory access in function
| derive_boundaryStrength of deblock.cc has occurred. The vulnerability
| causes a segmentation fault and application crash, which leads to
| remote denial of service.

https://github.com/strukturag/libde265/issues/302
https://github.com/strukturag/libde265/commit/45904e5667c5bf59c67fcdc586dfba110832894c

CVE-2021-36410[2]:
| A stack-buffer-overflow exists in libde265 v1.0.8 via fallback-
| motion.cc in function put_epel_hv_fallback when running program
| dec265.

https://github.com/strukturag/libde265/issues/301
https://github.com/strukturag/libde265/commit/697aa4f7c774abd6374596e6707a6f4f54265355


CVE-2021-36409:
https://github.com/strukturag/libde265/issues/300
https://github.com/strukturag/libde265/commit/64d591a6c70737604ca3f5791736fc462cbe8a3c


CVE-2021-36408[3]:
| An issue was discovered in libde265 v1.0.8.There is a Heap-use-after-
| free in intrapred.h when decoding file using dec265.

https://github.com/strukturag/libde265/issues/299
https://github.com/strukturag/libde265/commit/f538254e4658ef5ea4e233c2185dcbfd165e8911

CVE-2021-35452[4]:
| An Incorrect Access Control vulnerability exists in libde265 v1.0.8
| due to a SEGV in slice.cc.

https://github.com/strukturag/libde265/issues/298
https://github.com/strukturag/libde265/commit/e83f3798dd904aa579425c53020c67e03735138d


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-1253
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1253
[1] https://security-tracker.debian.org/tracker/CVE-2021-36411
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-36411
[2] https://security-tracker.debian.org/tracker/CVE-2021-36410
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-36410
[3] https://security-tracker.debian.org/tracker/CVE-2021-36408
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-36408
[4] https://security-tracker.debian.org/tracker/CVE-2021-35452
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-35452

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: libde265
Source-Version: 1.0.8-1.1
Done: Philipp Kern 

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

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

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

Debian distribution maintenance software
pp.
Philipp Kern  (supplier of updated libde265 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: Sun, 16 Oct 2022 15:26:20 +0200
Source: libde265
Architecture: source
Version: 1.0.8-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Philipp Kern 
Closes: 1014977
Changes:
 libde265 (1.0.8-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Import upstream fixes for CVE-tracked 

Bug#1013009: marked as done (openjfx: ftbfs with GCC-12)

[Debian Bug Tracking System]

Your message dated Sun, 16 Oct 2022 15:37:45 +
with message-id 
and subject line Bug#1013009: fixed in openjfx 11.0.11+1-1.1
has caused the Debian Bug report #1013009,
regarding openjfx: ftbfs with GCC-12
to be marked as done.

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

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


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

[This bug is targeted to the upcoming bookworm release]

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

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

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

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

  apt-get -t=experimental install g++ 

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

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

[...]
org.gradle.api.tasks.TaskExecutionException: Execution failed for task 
':web:compileNativeLinux'.
at 
org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:100)
at 
org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:70)
at 
org.gradle.api.internal.tasks.execution.OutputDirectoryCreatingTaskExecuter.execute(OutputDirectoryCreatingTaskExecuter.java:51)
at 
org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:62)
at 
org.gradle.api.internal.tasks.execution.ResolveTaskOutputCachingStateExecuter.execute(ResolveTaskOutputCachingStateExecuter.java:54)
at 
org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:60)
at 
org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:97)
at 
org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:87)
at 
org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:52)
at 
org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:52)
at 
org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:54)
at 
org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)
at 
org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:34)
at 
org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker$1.run(DefaultTaskGraphExecuter.java:248)
at 
org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336)
at 
org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328)
at 
org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:199)
at 
org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:110)
at 
org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:241)
at 

Bug#1004638: marked as done (openjfx: FTBFS with ffmpeg 5.0)

[Debian Bug Tracking System]

Your message dated Sun, 16 Oct 2022 15:37:45 +
with message-id 
and subject line Bug#1004638: fixed in openjfx 11.0.11+1-1.1
has caused the Debian Bug report #1004638,
regarding openjfx: FTBFS with ffmpeg 5.0
to be marked as done.

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

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


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

openjfx FTBFS with ffmpeg 5.0 (available in experimental):
| gcc -fPIC -Wformat -Wextra -Wformat-security -fstack-protector 
-Werror=implicit-function-declaration -Werror=trampolines -fbuiltin 
-DHAVE_STDINT_H -DLINUX -DGST_DISABLE_LOADSAVE -DGSTREAMER_LITE 
-ffunction-sections -fdata-sections -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>/modules/javafx.media/src/main/native/gstreamer/projects/linux/avplugin=.
 -fstack-protector-strong -Wformat -Werror=format-security -Wall -msse2 
-I../../../plugins -I../../../plugins/av -I../../../gstreamer-lite/gstreamer 
-I../../../gstreamer-lite/gstreamer/libs -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/x86_64-linux-gnu -c 
../../../plugins/av/videodecoder.c -o 
/<>/modules/javafx.media/build/native/linux/Release/obj/plugins/avplugin/av/videodecoder.o
| In file included from /usr/include/glib-2.0/glib/gthread.h:32,
|  from /usr/include/glib-2.0/glib/gasyncqueue.h:32,
|  from /usr/include/glib-2.0/glib.h:32,
|  from ../../../gstreamer-lite/gstreamer/gst/gst.h:27,
|  from ../../../plugins/av/decoder.h:29,
|  from ../../../plugins/av/decoder.c:26:
| ../../../plugins/av/decoder.c: In function ‘basedecoder_get_type’:
| /usr/include/glib-2.0/glib/gatomic.h:113:5: warning: argument 2 of 
‘__atomic_load’ discards ‘volatile’ qualifier [-Wincompatible-pointer-types]
|   113 | __atomic_load (gapg_temp_atomic, _temp_newval, 
__ATOMIC_SEQ_CST); \
|   | ^
| /usr/include/glib-2.0/glib/gthread.h:260:7: note: in expansion of macro 
‘g_atomic_pointer_get’
|   260 | (!g_atomic_pointer_get (location) && \
|   |   ^~~~
| ../../../plugins/av/decoder.c:58:9: note: in expansion of macro 
‘g_once_init_enter’
|58 | if (g_once_init_enter (_data))
|   | ^
| ../../../plugins/av/decoder.c:64:16: warning: cast between incompatible 
function types from ‘void (*)(void *)’ to ‘void (*)(void *, void *)’ 
[-Wcast-function-type]
|64 |(GClassInitFunc) basedecoder_class_intern_init,
|   |^
| ../../../plugins/av/decoder.c:66:16: warning: cast between incompatible 
function types from ‘void (*)(BaseDecoder *)’ {aka ‘void (*)(struct 
_BaseDecoder *)’} to ‘void (*)(GTypeInstance *, void *)’ {aka ‘void (*)(struct 
_GTypeInstance *, void *)’} [-Wcast-function-type]
|66 |(GInstanceInitFunc) basedecoder_init,
|   |^
| ../../../plugins/av/decoder.c: In function ‘basedecoder_init’:
| ../../../plugins/av/decoder.c:73:43: warning: unused parameter ‘self’ 
[-Wunused-parameter]
|73 | static void basedecoder_init(BaseDecoder *self)
|   |  ~^~~~
| ../../../plugins/av/decoder.c: In function ‘basedecoder_class_init’:
| ../../../plugins/av/decoder.c:79:5: error: implicit declaration of function 
‘avcodec_register_all’ [-Werror=implicit-function-declaration]
|79 | avcodec_register_all();
|   | ^~~~
| ../../../plugins/av/decoder.c: In function ‘basedecoder_open_decoder’:
| ../../../plugins/av/decoder.c:112:20: warning: assignment discards ‘const’ 
qualifier from pointer target type [-Wdiscarded-qualifiers]
|   112 | decoder->codec = avcodec_find_decoder(id);
|   |^
| ../../../plugins/av/decoder.c: In function ‘basedecoder_set_codec_data’:
| ../../../plugins/av/decoder.c:169:17: warning: ‘g_memdup’ is deprecated: Use 
'g_memdup2' instead [-Wdeprecated-declarations]
|   169 | decoder->codec_data = g_memdup(info.data, info.size);
|   | ^~~
| In file included from /usr/include/glib-2.0/glib.h:82,
|  from ../../../gstreamer-lite/gstreamer/gst/gst.h:27,
|  from ../../../plugins/av/decoder.h:29,
|  from ../../../plugins/av/decoder.c:26:
| /usr/include/glib-2.0/glib/gstrfuncs.h:257:23: 

Processed: Re: Bug#1004638: openjfx: FTBFS with ffmpeg 5.0

[Debian Bug Tracking System]

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

> tag 1013009 + pending
Bug #1013009 [src:openjfx] openjfx: ftbfs with GCC-12
Added tag(s) pending.
> tag 1004638 + pending
Bug #1004638 [src:openjfx] openjfx: FTBFS with ffmpeg 5.0
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1004638: openjfx: FTBFS with ffmpeg 5.0

[Philipp Kern]

tag 1013009 + pending
tag 1004638 + pending
thanks

On Sun, Oct 16, 2022 at 03:53:13PM +0200, Philipp Kern wrote:
> I think it's still worthwhile to upload this build.

While arm64/armhf remains unfixed (and could have its own t-p-u upload
based on the +0 version plus Ubuntu's patch), there's also a question if
a newer version would actually fix the issue.

I talked to Sebastian on IRC and we agreed that I'd upload the Ubuntu
patch for now. It doesn't make anything worse and will allow building
on amd64 again.

nmudiff attached.

Kind regards
Philipp Kern
diff -Nru openjfx-11.0.11+1/debian/changelog openjfx-11.0.11+1/debian/changelog
--- openjfx-11.0.11+1/debian/changelog  2022-05-03 16:48:31.0 +0200
+++ openjfx-11.0.11+1/debian/changelog  2022-10-16 12:19:38.0 +0200
@@ -1,3 +1,14 @@
+openjfx (11.0.11+1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop build-dependency on ffmpeg, openjfx isn't source-compatible with
+ffmpeg 5.0. Closes: #1004638.
+  * Build-depend on g++-11, source not compatible with g++ 12.
+Closes: #1013009.
+(Both patches taken from Ubuntu, thanks to Steve Langasek)
+
+ -- Philipp Kern   Sun, 16 Oct 2022 12:19:38 +0200
+
 openjfx (11.0.11+1-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru openjfx-11.0.11+1/debian/control openjfx-11.0.11+1/debian/control
--- openjfx-11.0.11+1/debian/control2022-05-03 15:33:58.0 +0200
+++ openjfx-11.0.11+1/debian/control2022-10-16 12:19:38.0 +0200
@@ -10,13 +10,12 @@
default-jdk,
default-jdk-doc,
flex,
+   g++-11,
gperf,
gradle (>= 4.4),
gradle-debian-helper (>= 2.0),
junit4,
libasound2-dev,
-   libavcodec-dev,
-   libavformat-dev,
libgl1-mesa-dev,
libgstreamer-plugins-base1.0-dev,
libgstreamer1.0-dev,
diff -Nru openjfx-11.0.11+1/debian/patches/disable-ffmpeg.patch 
openjfx-11.0.11+1/debian/patches/disable-ffmpeg.patch
--- openjfx-11.0.11+1/debian/patches/disable-ffmpeg.patch   1970-01-01 
01:00:00.0 +0100
+++ openjfx-11.0.11+1/debian/patches/disable-ffmpeg.patch   2022-10-16 
12:19:38.0 +0200
@@ -0,0 +1,24 @@
+Description: Don't build ffmpeg plugin when ffmpeg is disabled
+Author: Steve Langasek 
+Last-Update: 2022-09-21
+Bug-Debian: https://bugs.debian.org/1004638
+
+Index: openjfx-11.0.11+1/build.gradle
+===
+--- openjfx-11.0.11+1.orig/build.gradle
 openjfx-11.0.11+1/build.gradle
+@@ -3715,14 +3715,6 @@ project(":media") {
+ }
+ }
+ }
+-} else {
+-// Building fxavcodec plugin (libav plugin)
+-exec {
+-commandLine ("make", "${makeJobsFlag}", "-C", 
"${nativeSrcDir}/gstreamer/projects/linux/avplugin")
+-args("CC=${mediaProperties.compiler}", 
"LINKER=${mediaProperties.linker}",
+- "OUTPUT_DIR=${nativeOutputDir}", 
"BUILD_TYPE=${buildType}",
+- "BASE_NAME=avplugin", IS_64 ? "ARCH=x64" 
: "ARCH=x32")
+-}
+ }
+ }
+ }
diff -Nru openjfx-11.0.11+1/debian/patches/series 
openjfx-11.0.11+1/debian/patches/series
--- openjfx-11.0.11+1/debian/patches/series 2022-05-03 15:27:46.0 
+0200
+++ openjfx-11.0.11+1/debian/patches/series 2022-10-16 12:19:38.0 
+0200
@@ -18,3 +18,4 @@
 no-error_deprecated-declarations.patch
 32-gradle-compatibility.patch
 36-disable-swt-on-32bit-arch.patch
+disable-ffmpeg.patch
diff -Nru openjfx-11.0.11+1/debian/rules openjfx-11.0.11+1/debian/rules
--- openjfx-11.0.11+1/debian/rules  2022-05-03 15:27:46.0 +0200
+++ openjfx-11.0.11+1/debian/rules  2022-10-16 12:19:38.0 +0200
@@ -3,6 +3,8 @@
 DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
 DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
 
+export CXX=g++-11
+
 # FIXME: looks like s390x is recognized as a 32bit arch ...
 # more heap on s390x needed
 ifneq (,$(filter $(DEB_HOST_ARCH), s390x))

Bug#1015073: marked as done (daps: FTBFS: make[3]: *** [/<>/make/validate.mk:38: /<>/doc/build/.profiled/x86_amd64_em64t_osuse_noquick_/.validate] Error 3)

[Debian Bug Tracking System]

Your message dated Sun, 16 Oct 2022 15:04:22 +
with message-id 
and subject line Bug#1015073: fixed in daps 3.3.1+cleaned1-1
has caused the Debian Bug report #1015073,
regarding daps: FTBFS: make[3]: *** [/<>/make/validate.mk:38: 
/<>/doc/build/.profiled/x86_amd64_em64t_osuse_noquick_/.validate] 
Error 3
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.)


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

Hi,

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


Relevant part (hopefully):
> make[3]: Entering directory '/<>'
> /<>/doc/build/.profiled/x86_amd64_em64t_osuse_noquick_/MAIN.DAPS.xml:19:
>  element include: XInclude error : detected a local recursion with no 
> xpointer in 
> /<>/doc/build/.profiled/x86_amd64_em64t_osuse_noquick_/MAIN.DAPS.xml
> /<>/doc/build/.profiled/x86_amd64_em64t_osuse_noquick_/MAIN.DAPS.xml:21:
>  element include: XInclude error : detected a local recursion with no 
> xpointer in 
> /<>/doc/build/.profiled/x86_amd64_em64t_osuse_noquick_/MAIN.DAPS.xml
> /<>/doc/build/.profiled/x86_amd64_em64t_osuse_noquick_/MAIN.DAPS.xml:5:
>  element set: validity error : Element set content does not follow the DTD, 
> expecting ((title , subtitle? , titleabbrev?)? , setinfo? , toc? , (set | 
> book)+ , setindex?), got (title setinfo xi:include xi:include )
> /<>/doc/build/.profiled/x86_amd64_em64t_osuse_noquick_/MAIN.DAPS.xml:19:
>  element include: validity error : No declaration for element include
> /<>/doc/build/.profiled/x86_amd64_em64t_osuse_noquick_/MAIN.DAPS.xml:19:
>  element include: validity error : No declaration for attribute xmlns:xi of 
> element include
> /<>/doc/build/.profiled/x86_amd64_em64t_osuse_noquick_/MAIN.DAPS.xml:21:
>  element include: validity error : No declaration for element include
> /<>/doc/build/.profiled/x86_amd64_em64t_osuse_noquick_/MAIN.DAPS.xml:21:
>  element include: validity error : No declaration for attribute xmlns:xi of 
> element include
> Document 
> /<>/doc/build/.profiled/x86_amd64_em64t_osuse_noquick_/MAIN.DAPS.xml
>  does not validate
> make[3]: *** [/<>/make/validate.mk:38: 
> /<>/doc/build/.profiled/x86_amd64_em64t_osuse_noquick_/.validate]
>  Error 3


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

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: daps
Source-Version: 3.3.1+cleaned1-1
Done: Filippo Rusconi 

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

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

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

Debian distribution maintenance software
pp.
Filippo Rusconi  (supplier of updated daps package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 15 Oct 2022 11:40:33 +0200
Source: daps
Architecture: source
Version: 3.3.1+cleaned1-1
Distribution: unstable
Urgency: low
Maintainer: Filippo Rusconi 
Changed-By: Filippo Rusconi 
Closes: 1015073
Changes:
 daps (3.3.1+cleaned1-1) unstable; urgency=low
 .
   * New upstream version.
 .
   * Make patch to fix daps build failures (Closes: #1015073). Thanks to crew
 mentioned at https://github.com/openSUSE/daps/issues/676.
 .
   * Make patch to fix the call 

Bug#1021882: ros2-rosidl: FTBFS on mipsel: test failures

[Sebastian Ramacher]

Source: ros2-rosidl
Version: 3.3.0-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=ros2-rosidl=mipsel=3.3.0-2=1665762594=0


94% tests passed, 1 tests failed out of 16

Label Time Summary:
cppcheck  =   3.13 sec*proc (2 tests)
cpplint   = 174.44 sec*proc (2 tests)
gtest =   4.96 sec*proc (7 tests)
linter= 198.87 sec*proc (6 tests)
uncrustify=  21.30 sec*proc (2 tests)

Total Test time (real) = 120.04 sec

The following tests FAILED:
  2 - cpplint_rosidl_generated_cpp (Timeout)
Errors while running CTest
make[1]: *** [Makefile:74: test] Error 8

Cheers
-- 
Sebastian Ramacher

Processed: block 976052 with 1021880

[Debian Bug Tracking System]

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

> block 976052 with 1021880
Bug #976052 [wnpp] ITP: zola -- static site generator
976052 was blocked by: 1013115 1013118 984864 1013121 1009888 1013116 1013119 
1013117 1013120
976052 was not blocking any bugs.
Added blocking bug(s) of 976052: 1021880
> thanks
Stopping processing here.

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

Bug#998206: calendar: cronjob processes all users’ calendars as root, allowing information disclosure

[Philipp Kern]

Hi,

On Wed, Dec 08, 2021 at 12:11:28PM +, Thorsten Glaser wrote:
> Michael Meskes dixit:
> 
> >I did some more testing and it seems this simple patch fixes the issue:
> 
> I think you should still include a setgroups(0, NULL) call there.
> 
> Personally I’d prefer setres[ug]id() because that makes the intent
> more explicit even when the effect is the same, but… I’ll let you
> and the security team decide.

Gentle bump for this issue. Also shouldn't patching out setusercontext
and having no substitute get a CVE? >:)

calendar.c forks, so there is no need to regain privileges post
setuid(). I'm kinda with tg in that setres[ug]id() makes the intent
clearer instead of relying on uid==0 behavior.

Kind regards
Philipp Kern

Bug#885563: Bug#887649: Bug#885563: vte: Do not release with Buster

[Cyril Brulebois]

Philipp Kern  (2022-10-16):
> Unfortunately it doesn't look like there was progress on #887649 this
> cycle either. So I fear that we'll end up needing to tag both #887649
> and #885563 bookworm-ignore. :(

I'm keeping an open mind but given the remaining time, and the otherwise
important workload on firmware and other things, it looks to me working
on this is likely to trigger more immediate questions/problems than
we'll have time to figure out before it's time to release.


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


signature.asc
Description: PGP signature

Bug#997174: netdiag: FTBFS: statnet.c:471:32: error: format not a string literal and no format arguments [-Werror=format-security]

[Michael Meskes]

Hi Reiner,

> I've prepared an NMU for netdiag (versioned as 1.2-1.2) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.

Please go ahead, I wouldn't mind it being uploaded without delay.

Thanks,
Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De
Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org

Bug#1021880: librust-image+default-dev: impossible to install

[Jonas Smedegaard]

Package: librust-image+default-dev
Version: 0.23.14-2
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package librust-image+default-dev cannot be satisfied.

As a build-dependency on my pbuilder setup, it fails like this:

The following packages have unmet dependencies:
 pbuilder-satisfydepends-dummy : Depends: librust-image-0.23+default-dev which 
is a virtual package, provided by:
  - librust-image+default-dev 
(0.23.14-2), but it is not installable

At the command-line a bit more is revealed:

# LANG=C apt install librust-image+default-dev
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 librust-png+deflate-dev : Depends: librust-deflate-0.8+default-dev (>= 
0.8.2-~~) but it is not installable
E: Unable to correct problems, you have held broken packages.


-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmNMEK4ACgkQLHwxRsGg
ASHvGg/7Boy3eIa2+uAX2RJRJHUomMjrrLss4j/yAcfYXSbaCrou6kulnGfQMkuy
CsFRkSG+SxQ9sdgQ6sLZfXXLr3OwQ5d36wR4uZSxSf31KK1ttalSc0H2y2oGSg7g
WrEDpglP+oVZ10RoaI1I52zSFnDpDRo3xLPWicAT5MyWRfjNyDBiAcbD7dKOYL6k
TWFToUqw+egBtCVL/FEdnHTqvJ5w5O4Ekuq1ynmCrxdo0hoJZn2Hy32jiGgFNl+P
FJlLq+lhm/TSc5riR/pBaaHuZeWwhW8d+A7l1f2Ih0pYkTq6JmTwRIK6CRRDWN/e
BfuU+Y+paD5khfSO8TtBvSPr9b0ysVSVOYwtdck70pkSdQOodbmJKxWGI1c/xLQx
Ujy03DqEupPBfrOQsC7wLf24B1m13IrEYKUwfnDesml/wwDLjAYexJWQkrEnyBDW
MJqNDGL6XCklQ7b+G+hlkQgsQB82CaQJY/q4HhFi6AwecM7dBTSM6mq6qtsfQiah
MSHyT5m1IhJI8OU5wP6b5KdDEVvALKO3MF57CThO4u/MjdCkPQRdHeUbPnC9fpAX
SNp0SnCZYpKR+4hjjOB+mTX/c/VNHSa1fLLG7QwSe6JwKg+f7ELTUnhwvziQafkQ
a9DETi+6GU9WM7OYnUjMGi9M7jnsHNdTS4F3CBfL82/7Tm6bKWM=
=r2Xm
-END PGP SIGNATURE-

Processed: tagging 1014977

[Debian Bug Tracking System]

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

> tags 1014977 + pending
Bug #1014977 [src:libde265] libde265: CVE-2022-1253 CVE-2021-36411 
CVE-2021-36410 CVE-2021-36408 CVE-2021-35452
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: closing 902562

[Debian Bug Tracking System]

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

> close 902562 4.21-1
Bug #902562 [src:strace] strace: FTBFS in stretch
Ignoring request to alter fixed versions of bug #902562 to the same values 
previously set
Bug #902562 [src:strace] strace: FTBFS in stretch
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#902562: closing 902562

[Sebastian Ramacher]

close 902562 4.21-1
thanks

Bug#1004638: openjfx: FTBFS with ffmpeg 5.0

[Philipp Kern]

Hey,

On 16.10.22 14:02, Sebastian Ramacher wrote:

I was looking into applying Ubuntu's patch to Debian. It still has the
issue that the builds on arm64 and armhf fail. Reverting to 11.0.11+0
seems to fix that.


So we definitely need the g++-11 dependency as well. I guess I was 
misled by the most recent logs now failing due to ffmpeg, but the 
earlier log failed differently - that's true.


I think it's still worthwhile to upload this build. It looks like the 
getJumpIsland* code is guarded by an JUMP_ISLANDS ifdef (and newly 
introduced in +1). But it's also hard-enabled for ARM64 specifically:


| #if CPU(ARM64) && CPU(ADDRESS64)
| #define USE_JUMP_ISLANDS 1
| #endif

Did I expect to run into an embedded copy of WebKit? Not really. We are 
also already turning off the JIT for armel through a patch.


Kind regards
Philipp Kern

Bug#1004963: Bug#1014977: libde265: CVE-2022-1253 CVE-2021-36411 CVE-2021-36410 CVE-2021-36408 CVE-2021-35452

[Philipp Kern]

tags -1 + pending
thanks

Hey Moritz,

On Fri, Jul 15, 2022 at 05:48:41PM +0200, Moritz Mühlenhoff wrote:
> The following vulnerabilities were published for libde265.
[...]

Thanks for clearly linking to the upstream commits, that was very
helpful! Compared to the older bug these were quite straightforward to
apply. The CVEs referenced by #1004963 are still open in upstream's
bugtracker.

Attached is the diff of the NMU I just uploaded to DELAYED/2-days.

Kind regards and thanks
Philipp Kern
diff -Nru libde265-1.0.8/debian/changelog libde265-1.0.8/debian/changelog
--- libde265-1.0.8/debian/changelog 2020-12-16 16:32:29.0 +0100
+++ libde265-1.0.8/debian/changelog 2022-10-16 15:26:20.0 +0200
@@ -1,3 +1,17 @@
+libde265 (1.0.8-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Import upstream fixes for CVE-tracked vulnerabilities
+(Closes: #1014977)
+- CVE-2022-1253
+- CVE-2021-36411
+- CVE-2021-36410
+- CVE-2021-36409
+- CVE-2021-36408
+- CVE-2021-35452
+
+ -- Philipp Kern   Sun, 16 Oct 2022 15:26:20 +0200
+
 libde265 (1.0.8-1) unstable; urgency=medium
 
   * Update to debhelper compat level 13 and add debian/not-installed
diff -Nru libde265-1.0.8/debian/patches/0001-CVE-2022-1253.patch 
libde265-1.0.8/debian/patches/0001-CVE-2022-1253.patch
--- libde265-1.0.8/debian/patches/0001-CVE-2022-1253.patch  1970-01-01 
01:00:00.0 +0100
+++ libde265-1.0.8/debian/patches/0001-CVE-2022-1253.patch  2022-10-16 
15:19:58.0 +0200
@@ -0,0 +1,50 @@
+From 8e89fe0e175d2870c39486fdd09250b230ec10b8 Mon Sep 17 00:00:00 2001
+From: Dirk Farin 
+Date: Tue, 5 Apr 2022 09:52:57 +0200
+Subject: [PATCH] error on out-of-range cpb_cnt_minus1 (oss-fuzz issue 27590)
+
+---
+ libde265/sps.cc | 5 -
+ libde265/vui.cc | 6 ++
+ 2 files changed, 10 insertions(+), 1 deletion(-)
+
+Index: libde265-1.0.8/libde265/sps.cc
+===
+--- libde265-1.0.8.orig/libde265/sps.cc
 libde265-1.0.8/libde265/sps.cc
+@@ -425,7 +425,10 @@ de265_error seq_parameter_set::read(erro
+ 
+   vui_parameters_present_flag = get_bits(br,1);
+   if (vui_parameters_present_flag) {
+-vui.read(errqueue, br, this);
++de265_error err = vui.read(errqueue, br, this);
++if (err) {
++  return err;
++}
+   }
+ 
+ 
+Index: libde265-1.0.8/libde265/vui.cc
+===
+--- libde265-1.0.8.orig/libde265/vui.cc
 libde265-1.0.8/libde265/vui.cc
+@@ -201,6 +201,9 @@ de265_error video_usability_information:
+ if (!low_delay_hrd_flag[i])
+ {
+   READ_VLC_OFFSET(cpb_cnt_minus1[i], uvlc, 0);
++  if (cpb_cnt_minus1[i] > 31) {
++  return DE265_ERROR_CODED_PARAMETER_OUT_OF_RANGE;
++  }
+ }
+ 
+ for (nalOrVcl = 0; nalOrVcl < 2; nalOrVcl++)
+@@ -361,6 +364,9 @@ de265_error video_usability_information:
+ if (vui_hrd_parameters_present_flag) {
+   de265_error err;
+   err = hrd_parameters(errqueue, br, sps);
++  if (err) {
++  return err;
++  }
+ }
+   }
+ 
diff -Nru libde265-1.0.8/debian/patches/0001-fill-32x32-scaling-matrices.patch 
libde265-1.0.8/debian/patches/0001-fill-32x32-scaling-matrices.patch
--- libde265-1.0.8/debian/patches/0001-fill-32x32-scaling-matrices.patch
1970-01-01 01:00:00.0 +0100
+++ libde265-1.0.8/debian/patches/0001-fill-32x32-scaling-matrices.patch
2022-10-16 15:25:49.0 +0200
@@ -0,0 +1,85 @@
+From 7d5aeb5f11531de33f5b7ae0e768ffc50da4facb Mon Sep 17 00:00:00 2001
+From: Dirk Farin 
+Date: Tue, 23 Feb 2021 16:29:01 +0100
+Subject: [PATCH] fill 32x32 scaling matrices
+
+---
+ libde265/sps.cc   | 25 +++--
+ libde265/sps.h|  2 +-
+ libde265/transform.cc |  4 +---
+ 3 files changed, 25 insertions(+), 6 deletions(-)
+
+Index: libde265-1.0.8/libde265/sps.cc
+===
+--- libde265-1.0.8.orig/libde265/sps.cc
 libde265-1.0.8/libde265/sps.cc
+@@ -873,10 +873,10 @@ de265_error read_scaling_list(bitreader*
+   int dc_coeff[4][6];
+ 
+   for (int sizeId=0;sizeId<4;sizeId++) {
+-int n = ((sizeId==3) ? 2 : 6);
++//int n = ((sizeId==3) ? 2 : 6);
+ uint8_t scaling_list[6][32*32];
+ 
+-for (int matrixId=0;matrixIdScalingFactor_Size1[matrixId][y][x];
++
++  for (int dy=0;dy<4;dy++)
++for (int dx=0;dx<4;dx++) {
++  sclist->ScalingFactor_Size3[matrixId][4*y+dy][4*x+dx] = v;
++}
++  }
++
++  sclist->ScalingFactor_Size3[matrixId][0][0] = 
sclist->ScalingFactor_Size1[matrixId][0][0];
++}
++  
+   return DE265_OK;
+ }
+ 
+Index: libde265-1.0.8/libde265/sps.h
+===
+--- libde265-1.0.8.orig/libde265/sps.h
 libde265-1.0.8/libde265/sps.h
+@@ -54,7 +54,7 @@ typedef struct scaling_list_data {
+   uint8_t ScalingFactor_Size0[6][4][4];
+   uint8_t 

Bug#1021836: marked as done (mypaint: FTBFS: AssertionError: False is not true : The maximum abs difference with premultiplied alpha is too great: 97.0 > 8.0 [255=white].)

[Debian Bug Tracking System]

Your message dated Sun, 16 Oct 2022 09:49:34 -0400
with message-id 
and subject line Re: Bug#1021836: mypaint: FTBFS: AssertionError: False is not 
true : The maximum abs difference with premultiplied alpha is too great: 97.0 > 
8.0 [255=white].
has caused the Debian Bug report #1021836,
regarding mypaint: FTBFS: AssertionError: False is not true : The maximum abs 
difference with premultiplied alpha is too great: 97.0 > 8.0 [255=white].
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.)


-- 
1021836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021836
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mypaint
Version: 2.0.1-5
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=mypaint=amd64=2.0.1-5=1661980780=0

==
FAIL: test_docpaint (tests.mypaintlib.DocPaint)
Saved and reloaded documents look identical
--
Traceback (most recent call last):
  File "/<>/tests/mypaintlib.py", line 353, in test_docpaint
self.assert_pngs_equal(
  File "/<>/tests/mypaintlib.py", line 187, in assert_pngs_equal
self.assertTrue(equal_enough, msg=msg)
AssertionError: False is not true : The maximum abs difference with 
premultiplied alpha is too great: 97.0 > 8.0 [255=white].

--
Ran 43 tests in 21.153s

FAILED (failures=1, skipped=30)
Test failed: 
error: Test failed: 
E: pybuild pybuild:379: test: plugin distutils failed with: exit code=1: 
python3.10 setup.py test 
rm -fr -- /tmp/dh-xdg-rundir-w0Ft5vcq
dh_auto_test: error: pybuild --test -i python{version} -p 3.10 returned exit 
code 13

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Version: 2.0.1-7

This is now fixed in the new upload.

Thanks,
Boyuan Yang

在 2022-10-15星期六的 19:02 +0200，Sebastian Ramacher写道：
> Source: mypaint
> Version: 2.0.1-5
> Severity: serious
> Tags: ftbfs sid bookworm
> Justification: fails to build from source (but built successfully in the
> past)
> X-Debbugs-Cc: sramac...@debian.org
> 
> https://buildd.debian.org/status/fetch.php?pkg=mypaint=amd64=2.0.1-5=1661980780=0
> 
> ==
> FAIL: test_docpaint (tests.mypaintlib.DocPaint)
> Saved and reloaded documents look identical
> --
> Traceback (most recent call last):
>   File "/<>/tests/mypaintlib.py", line 353, in test_docpaint
>     self.assert_pngs_equal(
>   File "/<>/tests/mypaintlib.py", line 187, in
> assert_pngs_equal
>     self.assertTrue(equal_enough, msg=msg)
> AssertionError: False is not true : The maximum abs difference with
> premultiplied alpha is too great: 97.0 > 8.0 [255=white].
> 
> --
> Ran 43 tests in 21.153s
> 
> FAILED (failures=1, skipped=30)
> Test failed: 
> error: Test failed:  failures=1>
> E: pybuild pybuild:379: test: plugin distutils failed with: exit code=1:
> python3.10 setup.py test 
> rm -fr -- /tmp/dh-xdg-rundir-w0Ft5vcq
> dh_auto_test: error: pybuild --test -i python{version} -p 3.10 returned exit
> code 13
> 
> Cheers



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

Bug#1021832: marked as done (fastqtl: Missing build dependency on libbz2-dev)

[Debian Bug Tracking System]

Your message dated Sun, 16 Oct 2022 13:49:17 +
with message-id 
and subject line Bug#1021832: fixed in fastqtl 2.184+v7+dfsg-2
has caused the Debian Bug report #1021832,
regarding fastqtl: Missing build dependency on libbz2-dev
to be marked as done.

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

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


-- 
1021832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021832
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fastqtl
Version: 2.184+v7+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=fastqtl=amd64=2.184%2Bv7%2Bdfsg-1=1665041296=0

g++ -std=c++11 -O3 -Wl,-z,relro -Wl,-z,now obj/analysisMapping.o 
obj/analysisNominal.o obj/analysisNominalBest.o obj/analysisPermutation.o 
obj/analysisPermutationInteraction.o obj/analysisPermutationPerGroup.o 
obj/analysisPermutationSequence.o obj/commands.o obj/df.o obj/fastQTL.o 
obj/management.o obj/mle.o obj/readCovariates.o obj/readGenotypes.o 
obj/readGroups.o obj/readInclusionsExclusions.o obj/readInteractions.o 
obj/readPhenotypes.o obj/readThresholds.o obj/residualizer.o obj/tabix.o 
obj/utils.o -lRmath -lhts -lm -lz -lbz2 -lboost_iostreams 
-lboost_program_options -lgslcblas -lgsl -lblas -o bin/fastQTL
/usr/bin/ld: cannot find -lbz2: No such file or directory
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:94: bin/fastQTL] Error 1
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: fastqtl
Source-Version: 2.184+v7+dfsg-2
Done: Andreas Tille 

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 16 Oct 2022 14:59:19 +0200
Source: fastqtl
Architecture: source
Version: 2.184+v7+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 1021832
Changes:
 fastqtl (2.184+v7+dfsg-2) unstable; urgency=medium
 .
   * Team upload.
   * Build-Depends: libbz2-dev
 Closes: #1021832
Checksums-Sha1:
 f43e56c44fdacb2d590d4d5d0417aac35c103f8b 2237 fastqtl_2.184+v7+dfsg-2.dsc
 af6aa911cc50bdd936a48dfabc234dd389ea0656 20732 
fastqtl_2.184+v7+dfsg-2.debian.tar.xz
 58a5d35747a6142c3e0bace179cca5dc7509359f 17876 
fastqtl_2.184+v7+dfsg-2_source.buildinfo
Checksums-Sha256:
 10d310201ad95f0e5600c597a6d203c81a22741ca44e779209de72d522755911 2237 
fastqtl_2.184+v7+dfsg-2.dsc
 e1eef9e21b3087bea19bcfdbee54030b2dbcec00157b1850289abe16e7c3151a 20732 
fastqtl_2.184+v7+dfsg-2.debian.tar.xz
 d9cfe949fc1d1b2e0e5fdc8dda8c107c060e9f7d3a97a571ef3ba3e0eef633a4 17876 
fastqtl_2.184+v7+dfsg-2_source.buildinfo
Files:
 e92df90eb45e9f8d6fc0ec79c775c679 2237 science optional 
fastqtl_2.184+v7+dfsg-2.dsc
 a2760c27263aeceb2961a55c33468fd5 20732 science optional 
fastqtl_2.184+v7+dfsg-2.debian.tar.xz
 f6705ca26500bde4e1c95447d77f482a 17876 science optional 
fastqtl_2.184+v7+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCAAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmNMBmUOHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtGTBRAAmin8F8suas6MNJDxrs1RVrkdYdzrXFj94Dmi
PVAnJXBqGn4EehjGesBiN170TnVQPEf52/q9M7uuolkDeXFUB488vx8A4XCEFSjK
2EpMLBrtXFFASXGKMQg9iy5vzXU0V31u1pVKizKQbqSx5RgI7FWr+VGcLkuAQXfv
ht/FNo7r+P6GLqUXO4V8e5Ksj07uHkw5KDdiN3BBtOU8IBzm7cb98aQUvm/s0Ga7
YuT4G55o0+WlwLGm86yzN/1nAREHV8HhheDvuHZ47+DCFf6fIG2O4HrY8DxZAlKE
VxShJhK5mRal9DDsP+JpvdWSV1/bUzpU/xbz+7LWddtda/NBF8a1e4xgwOxAuLiN
zbGRis6YSGmEcXhO52GxVcJf00CRp6ecfafI9akwZzsu9p1uwS/+XLw9WhCUnJta
QwB6T+ByyzoIx7K5yUhO0bUFQAXKspnZeBal9YIpJEx0mRKZ+MR/ARyajOJBr1c6
A2qOLxE3C5p43Rf82X9WPDhBBY8+VD9ud77AJYbJQug/J6idCmI1enapbsGOAHsB
YxNT2E74SvEmi8mWZH7pTVdzBuPuGSglomHiUTfhJ5FHfGE+ZV3LZlyDpUAq5c8b
CFDl1yfwxfak4HE3Rk9A5H4WspJVPv8JHHAo2TYtd/X02lSC7cWSHWZMklli0476
4mQXxqg=
=hJbg
-END PGP SIGNATURE End Message ---

Bug#1017154: marked as done (fuse: FTBFS: ulockmgr_server.c:127:12: error: conflicting types for ‘closefrom’; have ‘int(int)’)

[Debian Bug Tracking System]

Your message dated Sun, 16 Oct 2022 13:49:26 +
with message-id 
and subject line Bug#1017154: fixed in fuse 2.9.9-6
has caused the Debian Bug report #1017154,
regarding fuse: FTBFS: ulockmgr_server.c:127:12: error: conflicting types for 
‘closefrom’; have ‘int(int)’
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.)


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

Hi,

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


Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I../include  -D_FILE_OFFSET_BITS=64  -Wdate-time 
> -D_FORTIFY_SOURCE=2  -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c -o mount.fuse.o 
> mount.fuse.c
> mount_util.c: In function ‘mtab_needs_update’:
> mount_util.c:62:25: warning: ignoring return value of ‘setreuid’ declared 
> with attribute ‘warn_unused_result’ [-Wunused-result]
>62 | setreuid(0, -1);
>   | ^~~
> mount_util.c:67:25: warning: ignoring return value of ‘setreuid’ declared 
> with attribute ‘warn_unused_result’ [-Wunused-result]
>67 | setreuid(ruid, -1);
>   | ^~
> mount_util.c: In function ‘add_mount’:
> mount_util.c:102:17: warning: ignoring return value of ‘setuid’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>   102 | setuid(geteuid());
>   | ^
> mount_util.c: In function ‘exec_umount’:
> mount_util.c:155:17: warning: ignoring return value of ‘setuid’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>   155 | setuid(geteuid());
>   | ^
> mount_util.c: In function ‘remove_mount’:
> mount_util.c:221:17: warning: ignoring return value of ‘setuid’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>   221 | setuid(geteuid());
>   | ^
> ulockmgr_server.c:127:12: error: conflicting types for ‘closefrom’; have 
> ‘int(int)’
>   127 | static int closefrom(int minfd)
>   |^
> In file included from ulockmgr_server.c:14:
> /usr/include/unistd.h:363:13: note: previous declaration of ‘closefrom’ with 
> type ‘void(int)’
>   363 | extern void closefrom (int __lowfd) __THROW;
>   | ^
> ulockmgr_server.c: In function ‘main’:
> ulockmgr_server.c:371:16: warning: ignoring return value of ‘chdir’ declared 
> with attribute ‘warn_unused_result’ [-Wunused-result]
>   371 | (void) chdir("/");
>   |^~
> make[3]: *** [Makefile:515: ulockmgr_server-ulockmgr_server.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/08/13/fuse_2.9.9-5_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: fuse
Source-Version: 2.9.9-6
Done: Laszlo Boszormenyi (GCS) 

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

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

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated fuse 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 

Bug#997174: netdiag: FTBFS: statnet.c:471:32: error: format not a string literal and no format arguments [-Werror=format-security]

[Reiner Herrmann]

Control: tags -1 + pending
Control: tags -1 + patch

Dear maintainer,

I've prepared an NMU for netdiag (versioned as 1.2-1.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards,
  Reiner
diff -u netdiag-1.2/debian/changelog netdiag-1.2/debian/changelog
--- netdiag-1.2/debian/changelog
+++ netdiag-1.2/debian/changelog
@@ -1,3 +1,10 @@
+netdiag (1.2-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use fixed format strings in mvprintw calls. (Closes: #997174)
+
+ -- Reiner Herrmann   Sun, 16 Oct 2022 15:28:17 +0200
+
 netdiag (1.2-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u netdiag-1.2/debian/patches/series netdiag-1.2/debian/patches/series
--- netdiag-1.2/debian/patches/series
+++ netdiag-1.2/debian/patches/series
@@ -8,3 +8,4 @@
 clang-ftbfs.diff
 gcc-10.diff
 pcap_init.diff
+gcc12.patch
only in patch2:
unchanged:
--- netdiag-1.2.orig/debian/patches/gcc12.patch
+++ netdiag-1.2/debian/patches/gcc12.patch
@@ -0,0 +1,51 @@
+Author: Reiner Herrmann 
+Bug-Debian: https://bugs.debian.org/997174
+Description: Use fixed format string in mvprintw to prevent format string vulnerabilities
+
+--- a/statnet-3.8/statnet.c
 b/statnet-3.8/statnet.c
+@@ -467,7 +467,7 @@
+ #define min(a,b) (((a) > (b)) ? (b) : (a))
+   if( COLS < 25 + min( 25, strlen( StatMem->servername ) ) )
+   {
+-mvprintw (0, (COLS - min( 25, strlen( StatMem->servername ) )) / 2,
++mvprintw (0, (COLS - min( 25, strlen( StatMem->servername ) )) / 2, "%s",
+ 			StatMem->servername);
+   }
+   else
+@@ -475,13 +475,13 @@
+ if( ((COLS/2) + 14) > COLS - min( 25, strlen( StatMem->servername )+1 ) )
+ {
+   mvprintw (0, 0, "STATISTICS OF NETWORKS");
+-  mvprintw (0, (COLS - min( 25, strlen( StatMem->servername )+1 )),
++  mvprintw (0, (COLS - min( 25, strlen( StatMem->servername )+1 )), "%s",
+ 	  		StatMem->servername);
+ }
+ 	else
+ {
+   mvprintw (0, (COLS - 22) / 2, "STATISTICS OF NETWORKS");
+-  mvprintw (0, (COLS - min( 25, strlen( StatMem->servername )+1 )),
++  mvprintw (0, (COLS - min( 25, strlen( StatMem->servername )+1 )), "%s",
+ 	  		StatMem->servername);
+ }
+   }
+--- a/netwatch-1.3.1-2/dispdata.c
 b/netwatch-1.3.1-2/dispdata.c
+@@ -1488,7 +1488,7 @@
+ 	  fprintf (fpspeclog, "%s\n", ttt);
+ 	else
+ 	  //!!mvprintw (yact, xleft, "%s",ttt);
+-	  mvprintw (yact, xleft, ttt);
++	  mvprintw (yact, xleft, "%s", ttt);
+ 	attron (col4);
+ 	if (current->update)
+ 	{
+@@ -1736,7 +1736,7 @@
+ 	  fprintf (fpspeclog, "%s\n", ttt);
+ 	else
+ 	  //!!mvprintw (yact, xright,"%s", ttt);
+-	  mvprintw (yact, xright, ttt);
++	  mvprintw (yact, xright, "%s", ttt);
+ 	attron (col4);
+ 	if (current->update)
+ 	{

Processed: Re: netdiag: FTBFS: statnet.c:471:32: error: format not a string literal and no format arguments [-Werror=format-security]

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #997174 [src:netdiag] netdiag: FTBFS: statnet.c:471:32: error: format not a 
string literal and no format arguments [-Werror=format-security]
Added tag(s) pending.
> tags -1 + patch
Bug #997174 [src:netdiag] netdiag: FTBFS: statnet.c:471:32: error: format not a 
string literal and no format arguments [-Werror=format-security]
Added tag(s) patch.

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

Processed: Re: libsass symbols table looks updated

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - pending
Bug #1012989 [src:libsass] libsass: ftbfs with GCC-12
Removed tag(s) pending.

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

Bug#1012989: libsass symbols table looks updated

[Étienne Mollier]

Control: tags -1 - pending

Étienne Mollier, on 2022-10-16:
> This issue looks fixed in the experimental updload, if I trust
> the current buildd status report[1], and the bug still open
> might simply be an oversight.  I suppose the bug can be closed
> now already or when migrating the package to unstable.
> 
> [1]: 
> https://buildd.debian.org/status/package.php?p=libsass=experimental=compact

Hmn, typical me: my mail fires away and some 1.5 seconds later I
see a lintian error stating that the tracking file must get new
symbols.  That being said, strictly speaking, changes in version
-2 do not break the build with gcc-12.  I'm sorry for the noise,
I was hopeful to provide a patch updating the table, preferably
for all supported architectures, but my time at the BSP is
running out.

Any ways, have a nice day,  :)
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from my alarm clock.


signature.asc
Description: PGP signature

Bug#1015043: marked as done (pcb: FTBFS: configure: error: cannot find gdlib-config. gdlib)

[Debian Bug Tracking System]

Your message dated Sun, 16 Oct 2022 15:22:11 +0200
with message-id 
and subject line Re: pcb: FTBFS: configure: error: cannot find gdlib-config. 
gdlib
has caused the Debian Bug report #1015043,
regarding pcb: FTBFS: configure: error: cannot find gdlib-config.  gdlib
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.)


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

Hi,

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


Relevant part (hopefully):
> checking if GIF output from the png HID is desired... yes
> checking if JPEG output from the png HID is desired... yes
> checking if PNG output from the png HID is desired... yes
> checking for GDLIB... no
> checking for gdlib-config... notfound
> configure: error: cannot find gdlib-config.  gdlib
> is required for gcode, nelma, png HIDs
> You may want to review the following errors
> from /usr/bin/pkg-config:
> Package 'libwebp', required by 'gdlib', not found
>   cd build_gtk && tail -v -n \+0 config.log


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

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
The build failure no longer occurs.
The problem was fixed in libgd-dev, where a dependency
on libwebp-dev was missing [0].

[0] 
https://tracker.debian.org/news/1346307/accepted-libgd2-233-6-source-into-unstable/--- End Message ---

Bug#979021: lirc: diff for NMU version 0.10.1-7.1

[Micha Lenk]

tags 979021 + pending
forwarded 979021 https://sourceforge.net/p/lirc/tickets/374/
user debian-rele...@lists.debian.org
usertags -1 + bsp-2022-10-de-karlsruhe
thank you


Dear maintainer,

I've prepared an NMU for lirc (versioned as 0.10.1-7.1) and
uploaded it to DELAYED/3. Please feel free to tell me if I
should delay it longer.

Additionally I dared to forward the patch affecting the upstream
code to their bug tracker. Hopefully this will make future
maintenance of this package easier.

Regards,
Micha
diff -Nru lirc-0.10.1/debian/changelog lirc-0.10.1/debian/changelog
--- lirc-0.10.1/debian/changelog	2022-05-12 21:29:00.0 +0200
+++ lirc-0.10.1/debian/changelog	2022-10-16 13:31:28.0 +0200
@@ -1,3 +1,14 @@
+lirc (0.10.1-7.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches: Add patch to support passing MODINFO to configure.
+  * debian/rules: Pass MODINFO and SH_PATH to configure. The paths to "modinfo"
+and "sh" may vary as either located in /bin and /sbin or in /usr/bin and
+/usr/sbin if the system is configured as a usrmerge system. Use the
+non-usrmerge paths for the most compatible location (closes: #979021).
+
+ -- Micha Lenk   Sun, 16 Oct 2022 13:31:28 +0200
+
 lirc (0.10.1-7) unstable; urgency=medium
 
   * Add patch from Fedora for failing tests. Closes: #1009389
diff -Nru lirc-0.10.1/debian/patches/0010-Patch-configure.ac-to-support-passing-MODINFO.patch lirc-0.10.1/debian/patches/0010-Patch-configure.ac-to-support-passing-MODINFO.patch
--- lirc-0.10.1/debian/patches/0010-Patch-configure.ac-to-support-passing-MODINFO.patch	1970-01-01 01:00:00.0 +0100
+++ lirc-0.10.1/debian/patches/0010-Patch-configure.ac-to-support-passing-MODINFO.patch	2022-10-16 13:31:28.0 +0200
@@ -0,0 +1,28 @@
+From: Vagrant Cascadian 
+Date: Sat, 2 Jan 2021 01:03:10 +
+Subject: Patch configure.ac to support passing MODINFO.
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979021
+Bug: https://sourceforge.net/p/lirc/tickets/374/
+Reviewed-by: Simon McVittie 
+Last-Update: 2022-10-16
+
+---
+ configure.ac | 2 --
+ 1 file changed, 2 deletions(-)
+
+diff --git a/configure.ac b/configure.ac
+index 58347d8..1d910b0 100644
+--- a/configure.ac
 b/configure.ac
+@@ -25,8 +25,6 @@ AC_CHECK_PROGS([MODINFO], [modinfo], [no], [$PATH:/sbin:/usr/sbin])
+ if test x$MODINFO = xno; then
+   AC_MSG_WARN(["No modinfo command found - skipping kernel drivers."])
+   MODINFO="false"
+-else
+-  MODINFO=$( PATH=$PATH:/sbin:/usr/sbin which modinfo )
+ fi
+ AC_SUBST(MODINFO)
+ AC_CHECK_PROG([PKGCONFIG],[pkg-config],[yes],[no])
+-- 
+2.20.1
+
diff -Nru lirc-0.10.1/debian/patches/series lirc-0.10.1/debian/patches/series
--- lirc-0.10.1/debian/patches/series	2022-05-12 21:26:56.0 +0200
+++ lirc-0.10.1/debian/patches/series	2022-10-16 13:31:28.0 +0200
@@ -7,3 +7,4 @@
 0007-lirc-gpio-ir-0.10.patch
 0008-python3.8.diff
 0009-Replace-the-obsolete-get_event_loop-with-get_running.patch
+0010-Patch-configure.ac-to-support-passing-MODINFO.patch
diff -Nru lirc-0.10.1/debian/rules lirc-0.10.1/debian/rules
--- lirc-0.10.1/debian/rules	2021-03-18 22:21:31.0 +0100
+++ lirc-0.10.1/debian/rules	2022-10-16 13:31:28.0 +0200
@@ -22,10 +22,14 @@
 override_dh_auto_configure:
 ifeq ($(DEB_BUILD_ARCH_OS), linux)
 	dh_auto_configure -- \
+	SH_PATH=/bin/sh \
+	MODINFO=/sbin/modinfo \
 	--enable-uinput --enable-devinput \
 	--enable-silent-rules
 else
 	dh_auto_configure -- \
+	SH_PATH=/bin/sh \
+	MODINFO=/sbin/modinfo \
 	--disable-uinput --disable-devinput \
 	--enable-silent-rules
 endif

Bug#1021510: marked as done (lxqt-qtplugin: hardcoded dependencies on libfm-qt8)

[Debian Bug Tracking System]

Your message dated Sun, 16 Oct 2022 13:19:49 +
with message-id 
and subject line Bug#1021510: fixed in lxqt-qtplugin 0.16.0-1.1
has caused the Debian Bug report #1021510,
regarding lxqt-qtplugin: hardcoded dependencies on libfm-qt8
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.)


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

The libfm-qt started its transition from libfm-qt8 to libfm-qt11. Since
lxqt-qtplugin hardcodes a dependency on libfm-qt8, this dependency needs
to be fixed with a sourceful upload.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: lxqt-qtplugin
Source-Version: 0.16.0-1.1
Done: Sebastian Ramacher 

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated lxqt-qtplugin 
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: Sun, 16 Oct 2022 15:00:28 +0200
Source: lxqt-qtplugin
Architecture: source
Version: 0.16.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: LXQt Packaging Team 
Changed-By: Sebastian Ramacher 
Closes: 1021510
Changes:
 lxqt-qtplugin (0.16.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/control: Update hard-coded dependency on libfm-qt8 to libfm-qt11
 (Closes: #1021510)
Checksums-Sha1:
 1cee9a1853e1ceeb81c8d079745437a110ed78f1 2572 lxqt-qtplugin_0.16.0-1.1.dsc
 50006683bb988a9cb4b4a6ed39d5e72027f44538 6212 
lxqt-qtplugin_0.16.0-1.1.debian.tar.xz
Checksums-Sha256:
 7a1831df1fd706df6befa79794ec6f52b6e84babb70aeee218492d3721f9947e 2572 
lxqt-qtplugin_0.16.0-1.1.dsc
 293a9fc319356e4b4654ae6d7fa67ebb3ef0a423835560376ed48b4ca7c366d7 6212 
lxqt-qtplugin_0.16.0-1.1.debian.tar.xz
Files:
 788c1a9ef2609df2bd5ab5bfb137bda6 2572 x11 optional lxqt-qtplugin_0.16.0-1.1.dsc
 996d34452cb0cfd036cf7d860f12249e 6212 x11 optional 
lxqt-qtplugin_0.16.0-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAmNMAM8ACgkQafL8UW6n
GZMuWQ/+ISQD5Fy4vOq3z7NDPt3oEC3WwZ6XBawOcmYAmYHLjhzikn6R7svvDne8
6mbFJEht2MJao5tUTFkbQ2I+d+nYgRJbCu2D8S3JxV+NFr4NOt3J6KqQf7VakO4D
DEGGbNYDMUvZz8IYUzcEVMqTbhjGjzsIjJQIThf9kY0JLV3P4l54munI7uluBoCa
F/hF1kFYlSajwr00Aw7ePbv7LRXFqJWCJgN+xAeKfYGdfGUSWb3FK3Yydfl7JTqU
V3bclji8W2/Z5zuP6VGF+sdb5gEha8Xh5s0Y4LBcEiIQW/EbPG//VPzfC2ov965g
8lo6gN9C5WQUoWNKUS+0UlVnhTJZlwBgk0p5YZaYgrzlC5uqFezODZN8LE5sT7FR
o7KEezVDkIfkout7UWDoU7XkX6p0xDU1NkSfvlHYk010V8AUaLcWXpKDrE9S2gIz
iDN/POLd3AiBBSCSybMQC68RKu2r9fKRa879Bawi6HVM7+z0KTW5D5fpLqLAeRKw
0ahqa+gs/xjDMlyMU2P8FEPxO6q9XMfEP13jKnUgYz0WjULpG3ryavcNQbosiqMO
NaxbswRDCjbQlxvIq8qiHtVqexDX1KjXLzy2zrD2KiHlKUQClhJqAvGlYVRFhV/m
/0hBFlePb0nyCAUylfux7uRHY+F+g+9AAUF5SLgmNz81opcp2XA=
=ikDX
-END PGP SIGNATURE End Message ---

Processed: pcmanfm-qt: diff for NMU version 0.16.0-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1021529 + patch
Bug #1021529 [src:pcmanfm-qt] pcmanfm-qt: hardcoded dependency on libfm-qt8
Added tag(s) patch.
> tags 1021529 + pending
Bug #1021529 [src:pcmanfm-qt] pcmanfm-qt: hardcoded dependency on libfm-qt8
Added tag(s) pending.

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

Bug#1021529: pcmanfm-qt: diff for NMU version 0.16.0-1.1

[Sebastian Ramacher]

Control: tags 1021529 + patch
Control: tags 1021529 + pending

Dear maintainer,

I've prepared an NMU for pcmanfm-qt (versioned as 0.16.0-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Cheers
-- 
Sebastian Ramacher
diff -Nru pcmanfm-qt-0.16.0/debian/changelog pcmanfm-qt-0.16.0/debian/changelog
--- pcmanfm-qt-0.16.0/debian/changelog	2021-01-07 10:33:42.0 +0100
+++ pcmanfm-qt-0.16.0/debian/changelog	2022-10-16 15:02:26.0 +0200
@@ -1,3 +1,11 @@
+pcmanfm-qt (0.16.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/control: Remove hard-coded dependency on libfm-qt8 (Closes:
+#1021529)
+
+ -- Sebastian Ramacher   Sun, 16 Oct 2022 15:02:26 +0200
+
 pcmanfm-qt (0.16.0-1) unstable; urgency=medium
 
   [ Alf Gaida ]
diff -Nru pcmanfm-qt-0.16.0/debian/control pcmanfm-qt-0.16.0/debian/control
--- pcmanfm-qt-0.16.0/debian/control	2021-01-07 10:30:30.0 +0100
+++ pcmanfm-qt-0.16.0/debian/control	2022-10-15 19:48:09.0 +0200
@@ -27,7 +27,6 @@
  ${shlibs:Depends},
  default-dbus-session-bus | dbus-session-bus | dbus-x11,
  desktop-file-utils,
- libfm-qt8 (>= 0.16.0~),
  lxqt-sudo
 Recommends: eject,
 ffmpegthumbnailer,

Bug#1021510: lxqt-qtplugin: diff for NMU version 0.16.0-1.1

[Sebastian Ramacher]

Control: tags 1021510 + patch
Control: tags 1021510 + pending

Dear maintainer,

I've prepared an NMU for lxqt-qtplugin (versioned as 0.16.0-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Cheers
-- 
Sebastian Ramacher
diff -Nru lxqt-qtplugin-0.16.0/debian/changelog lxqt-qtplugin-0.16.0/debian/changelog
--- lxqt-qtplugin-0.16.0/debian/changelog	2021-01-07 10:53:47.0 +0100
+++ lxqt-qtplugin-0.16.0/debian/changelog	2022-10-16 15:00:28.0 +0200
@@ -1,3 +1,11 @@
+lxqt-qtplugin (0.16.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/control: Update hard-coded dependency on libfm-qt8 to libfm-qt11
+(Closes: #1021510)
+
+ -- Sebastian Ramacher   Sun, 16 Oct 2022 15:00:28 +0200
+
 lxqt-qtplugin (0.16.0-1) unstable; urgency=medium
 
   [ Alf Gaida ]
diff -Nru lxqt-qtplugin-0.16.0/debian/control lxqt-qtplugin-0.16.0/debian/control
--- lxqt-qtplugin-0.16.0/debian/control	2021-01-07 10:53:35.0 +0100
+++ lxqt-qtplugin-0.16.0/debian/control	2022-10-16 15:00:25.0 +0200
@@ -26,7 +26,7 @@
 Multi-Arch: same
 Depends: ${misc:Depends},
  ${shlibs:Depends},
- libfm-qt8
+ libfm-qt11
 Recommends: lxqt-session,
 lxqt-config
 Suggests: lxqt | lxqt-core

Processed: lxqt-qtplugin: diff for NMU version 0.16.0-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1021510 + patch
Bug #1021510 [src:lxqt-qtplugin] lxqt-qtplugin: hardcoded dependencies on 
libfm-qt8
Added tag(s) patch.
> tags 1021510 + pending
Bug #1021510 [src:lxqt-qtplugin] lxqt-qtplugin: hardcoded dependencies on 
libfm-qt8
Added tag(s) pending.

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

Bug#1021810: Should firefox-esr be dropped on 32bit architectures in bookworm?

[Arnd Bergmann]

On Sat, Oct 15, 2022, at 8:27 AM, Adrian Bunk wrote:
> Package: firefox-esr
> Version: 102.3.0esr-1
> Severity: serious
> Tags: bookworm sid
> X-Debbugs-Cc: Carsten Schoenert , 
> debian-rele...@lists.debian.org, t...@security.debian.org, 
> debian-...@lists.debian.org
>
> [ various potentially interested parties are Cc'ed ]
>
> 4 GB address space for one process is an absolute limit on 32bit
> architectures, including for native building as is done in Debian.[1]
>
> mipsel has 2 GB address space (all Debian buildds have 64bit kernels),
> the 2020 Firefox ESR (78) was the last Firefox ESR to build there.
>
> On i386 and 32bit arm:
> 4 GB address space are available with a 64bit kernel.
> 3 GB address space are typically available with a 32bit kernel.
>
> All i386 buildds are using a 64bit kernel,
> but armhf buildds are currently mixed.
>
> This uncovered that the 2022 ESR of Firefox (102) already needs
> more than 3 GB address space on armhf.[2]

I see there is already a patch in there that changes from fulllto
link mode to thinlto, which uses less memory. It might be worth
investigating if it is still possible to build firefox-esr with
LTO disabled altogether, as that should use drastically less
address space at build time, at the expense of runtime performance.

 Arnd

Bug#1004638: openjfx: FTBFS with ffmpeg 5.0

[Sebastian Ramacher]

On 2022-10-16 14:02:12 +0200, Sebastian Ramacher wrote:
> On 2022-10-16 11:42:40 +, Philipp Kern wrote:
> > On Sun, Jan 30, 2022 at 11:23:39PM +0100, Sebastian Ramacher wrote:
> > > openjfx FTBFS with ffmpeg 5.0 (available in experimental):
> > [...]
> > 
> > It looks like even upstream openjfx (moved to [1]) is still not
> > source-compatible with ffmpeg 5.0. I could not find a bug in Oracle's
> > Java bug tracker about this either.
> > 
> > Ubuntu has disabled ffmpeg support[2], but hasn't released with that yet
> > (it's only in Kinetic due to be released soonish). This drops
> > libavplugin.so completely from libopenjfx-jni.
> > 
> > Source packages with a reverse (build-)dependency:
> > 
> > | afterburner.fx
> > | controlsfx
> > | davmail
> > | easybind
> > | fontawesomefx
> > | igv
> > | javafxsvg
> > | josm
> > | libhibernate-validator-java
> > | libjloda-java
> > | libmiglayout-java
> > | mediathekview
> > | megan-ce
> > | openchemlib
> > | pdfsam
> > | starjava-topcat
> > | triplea
> > | zeroc-ice
> > 
> > controlsfx uses javafx.scene.media.Media. pdfsam uses
> > javafx.scene.media.AudioClip. The others don't use javafx.scene.media at
> > all. mediathekview does not use controlsfx's MediaImageCell - which is
> > the one importing javafx.scene.media.Media. So I'd assume that within
> > Debian this breaks at most completion sound functionality in pdfsam-gui
> > if we were to drop the ffmpeg build-dependency.
> > 
> > I'm going to go ahead and do that.
> 
> I was looking into applying Ubuntu's patch to Debian. It still has the
> issue that the builds on arm64 and armhf fail. Reverting to 11.0.11+0
> seems to fix that.

… and I can confirm that 11.0.11+0 with the changes from Ubuntu builds
successfully on arm64.

Cheers
-- 
Sebastian Ramacher

Bug#1004638: openjfx: FTBFS with ffmpeg 5.0

[Sebastian Ramacher]

On 2022-10-16 11:42:40 +, Philipp Kern wrote:
> On Sun, Jan 30, 2022 at 11:23:39PM +0100, Sebastian Ramacher wrote:
> > openjfx FTBFS with ffmpeg 5.0 (available in experimental):
> [...]
> 
> It looks like even upstream openjfx (moved to [1]) is still not
> source-compatible with ffmpeg 5.0. I could not find a bug in Oracle's
> Java bug tracker about this either.
> 
> Ubuntu has disabled ffmpeg support[2], but hasn't released with that yet
> (it's only in Kinetic due to be released soonish). This drops
> libavplugin.so completely from libopenjfx-jni.
> 
> Source packages with a reverse (build-)dependency:
> 
> | afterburner.fx
> | controlsfx
> | davmail
> | easybind
> | fontawesomefx
> | igv
> | javafxsvg
> | josm
> | libhibernate-validator-java
> | libjloda-java
> | libmiglayout-java
> | mediathekview
> | megan-ce
> | openchemlib
> | pdfsam
> | starjava-topcat
> | triplea
> | zeroc-ice
> 
> controlsfx uses javafx.scene.media.Media. pdfsam uses
> javafx.scene.media.AudioClip. The others don't use javafx.scene.media at
> all. mediathekview does not use controlsfx's MediaImageCell - which is
> the one importing javafx.scene.media.Media. So I'd assume that within
> Debian this breaks at most completion sound functionality in pdfsam-gui
> if we were to drop the ffmpeg build-dependency.
> 
> I'm going to go ahead and do that.

I was looking into applying Ubuntu's patch to Debian. It still has the
issue that the builds on arm64 and armhf fail. Reverting to 11.0.11+0
seems to fix that.

Cheers

> 
> Kind regards
> Philipp Kern
> 
> [1] https://github.com/openjdk/jfx
> [2] https://patches.ubuntu.com/o/openjfx/openjfx_11.0.11+1-1ubuntu1.patch

-- 
Sebastian Ramacher

Bug#984057: infinipath-psm: diff for NMU version 3.3+20.604758e7-6.2 (was: Bug#984057: infinipath-psm: ftbfs with GCC-11)

[Christoph Biedl]

Control: tags 984057 + patch pending

Christoph Biedl wrote...

> After staring at this for a while I think upstream did some creepy
> things gcc is understandably
 un
>  happy, but overall this code in sysdep.h
> 
> | static __inline__ uint32_t ips_cmpxchg(volatile uint32_t *ptr,
> |uint32_t old, uint32_t new)
> | {
> | uint32_t prev;
> | struct xchg_dummy { uint32_t a[100]; };
> | 
> | asm volatile(LOCK_PREFIX "cmpxchgl %1,%2"
> |  : "=a"(prev)
> |  : "q"(new), "m"(*(struct xchg_dummy *)ptr), "0"(old)
> |  : "memory");
> | 
> | return prev;
> | }
> 
> is okay-ish. And so, unless someone finds a saner way (I guess it's
> replacing the 100 with a better value, possibly architecture-dependent),
> I'd just disable the warning, patch attached, makes the build pass.

After some more discussion on this here at the Karlsruhe BSP, also
playing with godbolt, we figured this is indeed rather an overcautious
gcc warning, and muting it should not do harm.


So here we go:

to fix the issues with this package, I've prepared an NMU for
infinipath-psm (versioned as 3.3+20.604758e7-6.2), debdiff below. An
upload to DELAYED/5 will follow shortly. Please feel free to tell me if
I should delay it longer.

Regards,

Christoph
diff -Nru infinipath-psm-3.3+20.604758e7/debian/changelog 
infinipath-psm-3.3+20.604758e7/debian/changelog
--- infinipath-psm-3.3+20.604758e7/debian/changelog 2021-01-03 
08:42:58.0 +0100
+++ infinipath-psm-3.3+20.604758e7/debian/changelog 2022-10-16 
13:18:17.0 +0200
@@ -1,3 +1,10 @@
+infinipath-psm (3.3+20.604758e7-6.2) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Work around FTBFS with gcc-12. Closes: #984057
+
+ -- Christoph Biedl   Sun, 16 Oct 2022 
13:18:17 +0200
+
 infinipath-psm (3.3+20.604758e7-6.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru 
infinipath-psm-3.3+20.604758e7/debian/patches/0004-gcc-11-warning.patch 
infinipath-psm-3.3+20.604758e7/debian/patches/0004-gcc-11-warning.patch
--- infinipath-psm-3.3+20.604758e7/debian/patches/0004-gcc-11-warning.patch 
1970-01-01 01:00:00.0 +0100
+++ infinipath-psm-3.3+20.604758e7/debian/patches/0004-gcc-11-warning.patch 
2022-10-16 13:18:17.0 +0200
@@ -0,0 +1,22 @@
+Description: Disable warning in the cmpxchgl wrapper
+Author: Christoph Biedl  
+Origin: no # upstream is dead
+Bug-Debian: https://bugs.debian.org/984057
+Last-Update: 2022-10-16
+
+--- a/include/linux-i386/sysdep.h
 b/include/linux-i386/sysdep.h
+@@ -106,10 +106,13 @@
+ uint32_t prev;
+ struct xchg_dummy { uint32_t a[100]; };
+ 
++#pragma GCC diagnostic push
++#pragma GCC diagnostic ignored "-Warray-bounds"
+ asm volatile(LOCK_PREFIX "cmpxchgl %1,%2"
+: "=a"(prev)
+: "q"(new), "m"(*(struct xchg_dummy *)ptr), "0"(old)
+: "memory");
++#pragma GCC diagnostic pop
+ 
+ return prev;
+ }
diff -Nru infinipath-psm-3.3+20.604758e7/debian/patches/series 
infinipath-psm-3.3+20.604758e7/debian/patches/series
--- infinipath-psm-3.3+20.604758e7/debian/patches/series2021-01-03 
08:42:58.0 +0100
+++ infinipath-psm-3.3+20.604758e7/debian/patches/series2022-10-16 
13:18:17.0 +0200
@@ -1,3 +1,4 @@
 0001-Fix-truncation-warnings-with-gcc7.patch
 0002-Include-sys-sysmacros.h-to-avoid-warning-about-minor.patch
 0003-gcc8.patch
+0004-gcc-11-warning.patch


signature.asc
Description: PGP signature

Processed: infinipath-psm: diff for NMU version 3.3+20.604758e7-6.2 (was: Bug#984057: infinipath-psm: ftbfs with GCC-11)

[Debian Bug Tracking System]

Processing control commands:

> tags 984057 + patch pending
Bug #984057 [src:infinipath-psm] infinipath-psm: ftbfs with GCC-11
Added tag(s) pending and patch.

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

Bug#1004638: openjfx: FTBFS with ffmpeg 5.0

[Philipp Kern]

On Sun, Jan 30, 2022 at 11:23:39PM +0100, Sebastian Ramacher wrote:
> openjfx FTBFS with ffmpeg 5.0 (available in experimental):
[...]

It looks like even upstream openjfx (moved to [1]) is still not
source-compatible with ffmpeg 5.0. I could not find a bug in Oracle's
Java bug tracker about this either.

Ubuntu has disabled ffmpeg support[2], but hasn't released with that yet
(it's only in Kinetic due to be released soonish). This drops
libavplugin.so completely from libopenjfx-jni.

Source packages with a reverse (build-)dependency:

| afterburner.fx
| controlsfx
| davmail
| easybind
| fontawesomefx
| igv
| javafxsvg
| josm
| libhibernate-validator-java
| libjloda-java
| libmiglayout-java
| mediathekview
| megan-ce
| openchemlib
| pdfsam
| starjava-topcat
| triplea
| zeroc-ice

controlsfx uses javafx.scene.media.Media. pdfsam uses
javafx.scene.media.AudioClip. The others don't use javafx.scene.media at
all. mediathekview does not use controlsfx's MediaImageCell - which is
the one importing javafx.scene.media.Media. So I'd assume that within
Debian this breaks at most completion sound functionality in pdfsam-gui
if we were to drop the ffmpeg build-dependency.

I'm going to go ahead and do that.

Kind regards
Philipp Kern

[1] https://github.com/openjdk/jfx
[2] https://patches.ubuntu.com/o/openjfx/openjfx_11.0.11+1-1ubuntu1.patch

Processed: libsass symbols table looks updated

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 3.6.5+20211226-2
Bug #1012989 [src:libsass] libsass: ftbfs with GCC-12
Marked as fixed in versions libsass/3.6.5+20211226-2.
> tags -1 pending
Bug #1012989 [src:libsass] libsass: ftbfs with GCC-12
Added tag(s) pending.

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

Bug#1012989: libsass symbols table looks updated

[Étienne Mollier]

Control: fixed -1 3.6.5+20211226-2
Control: tags -1 pending

Greetings,

This issue looks fixed in the experimental updload, if I trust
the current buildd status report[1], and the bug still open
might simply be an oversight.  I suppose the bug can be closed
now already or when migrating the package to unstable.

[1]: 
https://buildd.debian.org/status/package.php?p=libsass=experimental=compact

Have a nice day,  :)
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from my alarm clock.


signature.asc
Description: PGP signature

Processed: Re: schleuder: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: expect(error).to be_empty

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1019682 [src:schleuder] schleuder: FTBFS with ruby3.1: ERROR: Test 
"ruby3.1" failed:   Failure/Error: expect(error).to be_empty
Severity set to 'serious' from 'important'

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

Bug#997619: marked as done (python-mailer: FTBFS: error in mailer setup command: use_2to3 is invalid.)

[Debian Bug Tracking System]

Your message dated Sun, 16 Oct 2022 13:12:11 +0200
with message-id 
and subject line Re: python-mailer: FTBFS: error in mailer setup command: 
use_2to3 is invalid.
has caused the Debian Bug report #997619,
regarding python-mailer: FTBFS: error in mailer setup command: use_2to3 is 
invalid.
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.)


-- 
997619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997619
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-mailer
Version: 0.8.1-4
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):
>  fakeroot debian/rules clean
> dh  clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean 
> error in mailer setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit 
> code 13
> make: *** [debian/rules:6: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-mailer_0.8.1-4_unstable.log

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

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

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

Closing this manually, as it has already been fixed in 0.8.1-5,
but there is a typo in the changelog (which lintian also warns about),
so it has not been detected.--- End Message ---

Bug#1021083: marked as done (securefs: autopkgtest regression: output on stderr)

[Debian Bug Tracking System]

Your message dated Sun, 16 Oct 2022 10:55:57 +
with message-id 
and subject line Bug#1021083: fixed in securefs 0.13.0+ds-2
has caused the Debian Bug report #1021083,
regarding securefs: autopkgtest regression: output 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.)


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

Source: securefs
Version: 0.13.0+ds-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
securefs   from testing0.13.0+ds-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. Your test 
passes, but it produces output on stderr. By default autopkgtest fails 
with output on stderr, except with the allow-stderr restriction set. 
Please fix the output or use the restriction.


Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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=securefs

https://ci.debian.net/data/autopkgtest/testing/amd64/s/securefs/26558003/log.gz

[Info] [0x7fe804337b80] [2022-09-30 23:33:11.845448233 UTC] 
[get_random_number_engine()::Initializer::Initializer():27]Random 
seed: 
4442d8b9ef6c4bc430fada81e389a29ad79c47afb559160982b60423af6b298f1d6ee0a97c1306ab182097d3ab9ef2ad87bbc21c68bb0264a7fc783d03d493e7df41cbff77ddc3c8bc1a447461aba5fab11832b6826f61d3546ca685124469afbe924e829203b17d68f8d9e5426a529cf55c0a8c85487c95282ea8e535ee1adb377961bc68a42c9e544a63c8de4fa04dff5aea9e5ccfeaafb6ad6558af250298a30a0d27c229022979c5fba4112e2dba7fd40bf5f8ea7679662727a11b363f378d259dc5dea3953bbc1d8b9de9c1edc2013d9aa58fdf1992efcb90566744ec48cd3579c29c3e19b376d70a4cc878af4a317b42838cd97b41b55305198565733d
[Info] [0x7fe804337b80] [2022-09-30 23:33:12.251601986 UTC] 
[C_A_T_C_HT_E_S_T1()::unsigned int)>:296]Actual padding size: 0
[Info] [0x7fe804337b80] [2022-09-30 23:33:12.255596070 UTC] 
[C_A_T_C_HT_E_S_T1()::unsigned int)>:308]Actual padding size: 0
[Info] [0x7fe804337b80] [2022-09-30 23:33:12.259687939 UTC] 
[C_A_T_C_HT_E_S_T1()::unsigned int)>:296]Actual padding size: 0
[Info] [0x7fe804337b80] [2022-09-30 23:33:12.268763279 UTC] 
[C_A_T_C_HT_E_S_T1()::unsigned int)>:308]Actual padding size: 0
[Info] [0x7fe804337b80] [2022-09-30 23:33:12.277214124 UTC] 
[C_A_T_C_HT_E_S_T1()::unsigned int)>:296]Actual padding size: 7
[Info] [0x7fe804337b80] [2022-09-30 23:33:12.285512300 UTC] 
[C_A_T_C_HT_E_S_T1()::unsigned int)>:308]Actual padding size: 7
[Info] [0x7fe804337b80] [2022-09-30 23:33:12.293644781 UTC] 
[C_A_T_C_HT_E_S_T1()::unsigned int)>:296]Actual padding size: 1
[Info] [0x7fe804337b80] [2022-09-30 23:33:12.297981264 UTC] 
[C_A_T_C_HT_E_S_T1()::unsigned int)>:308]Actual padding size: 1
[Info] [0x7fe804337b80] [2022-09-30 23:33:12.302177492 UTC] 
[C_A_T_C_HT_E_S_T1()::unsigned int)>:296]Actual padding size: 30
[Info] [0x7fe804337b80] [2022-09-30 23:33:12.306428162 UTC] 
[C_A_T_C_HT_E_S_T1()::unsigned int)>:308]Actual padding size: 30

===
All tests passed (901865 assertions in 19 test cases)

autopkgtest [23:33:12]: test command2



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: securefs
Source-Version: 0.13.0+ds-2
Done: Yanhao 

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

Debian distribution maintenance software
pp.
Yanhao  (supplier of updated securefs package)

(This message was generated automatically at their request; if you

Bug#1017829: marked as done (elpa-ess: emacs-gtk 28.1 install fails with installed elpa-ess)

[Debian Bug Tracking System]

Your message dated Sun, 16 Oct 2022 10:49:22 +
with message-id 
and subject line Bug#1017829: fixed in ess 18.10.2+git20220915.f45542e-1
has caused the Debian Bug report #1017829,
regarding elpa-ess: emacs-gtk 28.1 install fails with installed elpa-ess
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.)


-- 
1017829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017829
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: elpa-ess
Version: 18.10.2
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

Upgrading to emacs 28.1-2 leads emacs-gtk to a failure at emacs-ess
byte-compiling.

Paramétrage de emacs-gtk (1:28.1+1-2) ...
Deep recursion on subroutine 
"main::generate_relevant_tsort_dependencies_internals" at 
/usr/lib/emacsen-common/lib.pl line 127.
Install emacs-calfw for emacs
Install emacs-window-layout for emacs
Install emacsen-common for emacs
emacsen-common: Handling install of emacsen flavor emacs
Install emacspeak for emacs
/usr/lib/emacsen-common/packages/install/emacspeak running in /
Latest installed version: 53.0+dfsg-1
Latest compiled version:  53.0+dfsg-1

... I skip a lot of successful
Install   
... until ess failure lines

Install elpa-ess for emacs
install/ess-18.10.2: Handling install of emacsen flavor emacs
install/ess-18.10.2: byte-compiling for emacs
Package cl is deprecated
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)
Error loading autoloads: (wrong-number-of-arguments (3 . 4) 2)
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
debian-autoloads.el:9:1: Error: Wrong number of arguments: (3 . 4), 2

In toplevel form:
ess-custom.el:363:1: Warning: custom-declare-variable
`ess-tab-complete-in-script' docstring wider than 80 characters
ess-custom.el:409:1: Warning: custom-declare-variable
`ess-eldoc-abbreviation-style' docstring wider than 80 characters
ess-custom.el:1484:1: Warning: custom-declare-variable `ess-roxy-fill-param-p'
docstring wider than 80 characters
ess-custom.el:1547:1: Warning: custom-declare-variable
`ess-gen-proc-buffer-name-function' docstring wider than 80 characters
ess-custom.el:1657:1: Warning: custom-declare-variable `ess-R-readline'
docstring wider than 80 characters
ess-custom.el:1694:1: Warning: custom-declare-variable `ess-program-files'
docstring wider than 80 characters
ess-custom.el:1704:1: Warning: custom-declare-variable `ess-program-files-64'
docstring wider than 80 characters
ess-custom.el:1926:1: Warning: custom-declare-variable
`inferior-Sqpe+-start-args' docstring wider than 80 characters
ess-custom.el:2329:1: Warning: custom-declare-variable
`inferior-ess-safe-names-command' docstring wider than 80 characters

In ess-font-lock-db:
ess-font-lock.el:136:8: Warning: docstring wider than 80 characters
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
ess-gretl.el:40:1: Error: Wrong number of arguments: (3 . 4), 2

In inferior-ess:
ess-inf.el:284:20: Warning: ‘syntax-begin-function’ is an obsolete variable
(as of 25.1).

In ess-gen-proc-buffer-name:abbr-long-directory:
ess-inf.el:373:8: Warning: docstring wider than 80 characters

In ess-process-put:
ess-inf.el:723:8: Warning: docstring wider than 80 characters

In ess-switch-to-inferior-or-script-buffer:
ess-inf.el:924:8: Warning: docstring wider than 80 characters

In ess-execute-search:
ess-inf.el:2301:8: Warning: docstring wider than 80 characters

In ess-resynch:
ess-inf.el:2757:8: Warning: docstring wider than 80 characters
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
ess-julia.el:46:1: Error: Wrong number of arguments: (3 . 4), 2

In ess-noweb-font-lock-mode:
ess-noweb-font-lock-mode.el:163:8: Warning: docstring wider than 80 characters

In ess-noweb-font-lock-fontify-chunk-by-number:
ess-noweb-font-lock-mode.el:244:11: Warning: ‘syntax-begin-function’ is an
obsolete variable (as of 25.1).

Processed: binutils-arm-none-eabi: diff for NMU version 17+nmu1 (was: Bug#1021193: binutils-arm-none-eabi ftbfs)

[Debian Bug Tracking System]

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

> tags 1021193 + patch pending
Bug #1021193 [src:binutils-arm-none-eabi] binutils-arm-none-eabi ftbfs
Added tag(s) patch and pending.
> user debian-rele...@lists.debian.org
Setting user to debian-rele...@lists.debian.org (was 
debian.a...@manchmal.in-ulm.de).
> usertags 1021193 + bsp-2022-10-de-karlsruhe
There were no usertags set.
Usertags are now: bsp-2022-10-de-karlsruhe.
> thank you
Stopping processing here.

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

Bug#885563: vte: Do not release with Buster

[Philipp Kern]

On Sun, Sep 30, 2018 at 09:03:47AM -0400, Jeremy Bicha wrote:
> On Sun, Sep 30, 2018 at 2:57 AM Niels Thykier  wrote:
> > AFAICT, the cdebconf-gtk-terminal bug (#887649) has not been updated in
> > the past 8 months.  Is it still realistic to remove vte before the
> > transition freeze (2019-01-12)?
> I agree that I don't see anyone working on that bug now. I think
> porting to gtk3 and getting rid of the unmaintained vte version is an
> important goal for Debian. I'd like to leave this bug as RC for Buster
> until the Transition Freeze.

Unfortunately it doesn't look like there was progress on #887649 this
cycle either. So I fear that we'll end up needing to tag both #887649
and #885563 bookworm-ignore. :(

Kind regards
Philipp Kern

Bug#1021193: binutils-arm-none-eabi: diff for NMU version 17+nmu1 (was: Bug#1021193: binutils-arm-none-eabi ftbfs)

[Christoph Biedl]

tags 1021193 + patch pending
user debian-rele...@lists.debian.org
usertags 1021193 + bsp-2022-10-de-karlsruhe
thank you

Matthias Klose wrote...

> setting deb_upstream_version in debian/rules fails:

Well, that was a low-hanging fruit. The updated code copied the
behaviour as found in /usr/share/dpkg/pkg-info.mk, and the packaging
could benefit from that one in other ways as well.

Aside, all this will break if binutils-source ever has an epoch in the
version number.

So here we go: 

To fix the issues with this package, I've prepared an NMU for
binutils-arm-none-eabi (versioned as 17+nmu1), debdiff below. An upload
to DELAYED/10 will follow shortly. Please feel free to tell me if I
should delay it longer.

Regards,

Christoph
diff -Nru binutils-arm-none-eabi-17/debian/changelog 
binutils-arm-none-eabi-17+nmu1/debian/changelog
--- binutils-arm-none-eabi-17/debian/changelog  2022-08-10 17:50:39.0 
+0200
+++ binutils-arm-none-eabi-17+nmu1/debian/changelog 2022-10-16 
11:02:35.0 +0200
@@ -1,3 +1,11 @@
+binutils-arm-none-eabi (17+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Fix extraction of the binutils-source upstream version number.
+Closes: #1021193
+
+ -- Christoph Biedl   Sun, 16 Oct 2022 
11:02:35 +0200
+
 binutils-arm-none-eabi (17) unstable; urgency=medium
 
   * Make --no-warn-rwx-segments the default.
diff -Nru binutils-arm-none-eabi-17/debian/rules 
binutils-arm-none-eabi-17+nmu1/debian/rules
--- binutils-arm-none-eabi-17/debian/rules  2022-08-10 17:50:39.0 
+0200
+++ binutils-arm-none-eabi-17+nmu1/debian/rules 2022-10-16 11:01:51.0 
+0200
@@ -13,7 +13,7 @@
 
 source_version := $(shell dpkg-query -W -f="\$${Version}\n" binutils-source)
 deb_version := $(source_version)+$(shell dpkg-parsechangelog | sed -ne 
"s/^Version: \(.*\)/\1/p")
-deb_upstream_version := $(shell echo $(deb_version) | cut -d. -f1-3)
+deb_upstream_version := $(shell echo $(deb_version) | sed -e 's/-[^-]*$$//')
 
 upstream_dir=binutils-$(deb_upstream_version)
 


signature.asc
Description: PGP signature

Processed: found 1014803 in 1.4.1-1

[Debian Bug Tracking System]

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

> found 1014803 1.4.1-1
Bug #1014803 {Done: Adrian Bunk } [src:ruby-yajl] ruby-yajl: 
CVE-2022-24795
Marked as found in versions ruby-yajl/1.4.1-1.
> thanks
Stopping processing here.

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

Processed: found 1021787 in 1.9-2

[Debian Bug Tracking System]

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

> found 1021787 1.9-2
Bug #1021787 {Done: tony mancill } [src:commons-text] 
commons-text: CVE-2022-42889
Marked as found in versions commons-text/1.9-2.
> thanks
Stopping processing here.

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