Bug#996586: heimdal: CVE-2021-3671

[Salvatore Bonaccorso]

Hi Brian,

Only commenting on the first part for now:

On Thu, Oct 21, 2021 at 11:19:50AM +1100, Brian May wrote:
> Salvatore Bonaccorso  writes:
> 
> > Source: heimdal
> > Version: 7.7.0+dfsg-2
> > Severity: grave
> > Tags: security upstream
> > Justification: user security hole
> > X-Debbugs-Cc: car...@debian.org, Debian Security Team 
> > 
> > Control: found -1 7.5.0+dfsg-3
> 
> Does this need to be grave? Considering it was considered a minor issue
> everywhere else, maybe not?

Right, when filling a bug the severity is often "orthogonal" to a
no-dsa security tracking decision. With the grave severity as RC I
would like to basically make the statement here, the security issue
should be considered RC and the next release (far away) should contain
this fix.

A RC severity fileld bug does not make necdssarily the implication
that a DSA is needed (instead of e.g. fixing it via point release,
which seems sensible here for me). OTOH, many non-RC severity
warranted a DSA.

Hope this explains a bit. If you feel strong about the severity beeing
to hight, feel free to downgrade, please.

Regards,
Salvatore

Bug#987257: marked as pending in unixcw

[Federico Grau]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian-hamradio-team/unixcw/-/commit/6503634e26a44a807366cfb758384577124bec91


Update d/control Breaks, match Replaces Closes: #987257


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/987257

Processed: Bug#987257 marked as pending in unixcw

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #987257 [libcw-dev,libcw7] libcw{7,-dev}: removal of libcw{7,-dev} makes 
files disappear from libcw6{,-dev}
Added tag(s) pending.

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

Bug#617856: marked as done (apt-show-versions: does not see gzipped Packages files when uncompressed are not available)

[Debian Bug Tracking System]

Your message dated Thu, 21 Oct 2021 00:33:37 +
with message-id 
and subject line Bug#617856: fixed in apt-show-versions 0.22.12+nmu1
has caused the Debian Bug report #617856,
regarding apt-show-versions: does not see gzipped Packages files when 
uncompressed are not available
to be marked as done.

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

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


-- 
617856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617856
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apt-show-versions
Version: 0.17
Severity: important

Hi.

On my system, apt-show-versions started complaining with the message:

Error: No information about packages! (Maybe no deb entries?)

Of course, I do have deb entries in my system. Reading the source code, I
saw that there was this snippet of code:

,
| @files = map { $list_dir . $_} grep /Packages$/, readdir(DIR);
`

right there in the initialization of the cache. Since my system only has
gzipped files as shown by "ls /var/lib/apt/lists/*Packages*",
apt-show-versions goes on to say that it found no informations about the
packages, but the files are there, only gzipped (that is, ending with
Packages.gz extension, instead of only Packages).

If you need any further information, please let me know.


Regards,
Rogério Brito.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (300, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.38-rc7+ (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.utf-8, LC_CTYPE=pt_BR.utf-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages apt-show-versions depends on:
ii  apt   0.8.12 Advanced front-end for dpkg
ii  libapt-pkg-perl   0.1.24+b1  Perl interface to libapt-pkg
ii  perl [libstorable-perl]   5.10.1-17  Larry Wall's Practical Extraction 

apt-show-versions recommends no packages.

apt-show-versions suggests no packages.

-- no debconf information

-- 
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://rb.doesntexist.org : Packages for LaTeX : algorithms.berlios.de
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br


--- End Message ---
--- Begin Message ---
Source: apt-show-versions
Source-Version: 0.22.12+nmu1
Done: Antonio Terceiro 

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

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated apt-show-versions 
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, 05 Oct 2021 20:39:04 -0300
Source: apt-show-versions
Architecture: source
Version: 0.22.12+nmu1
Distribution: unstable
Urgency: medium
Maintainer: Christoph Martin 
Changed-By: Antonio Terceiro 
Closes: 617856
Changes:
 apt-show-versions (0.22.12+nmu1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Fix indexing with compressed APT Packages files (Closes: #617856)
Checksums-Sha1:
 c054c5739b2a87066fe47282e99fe3d426123dfd 1716 
apt-show-versions_0.22.12+nmu1.dsc
 cb7cfecfe90fb7164dec84ed5c618e1d64cdcc7e 31700 
apt-show-versions_0.22.12+nmu1.tar.xz
 a41a5714c4c0707105f0c59b070c6fe0997fa360 6061 
apt-show-versions_0.22.12+nmu1_source.buildinfo
Checksums-Sha256:
 5e7cbd990c7be2f7d75becb71ab5af90a31e714f77fda1c02d509426acbcb128 1716 
apt-show-versions_0.22.12+nmu1.dsc
 b0ec125ecc74fcb998a5735f49d9f22a30897cab4ee9a15976361eb5e41ae7b7 31700 
apt-show-versions_0.22.12+nmu1.tar.xz
 0b2e417d5ba4fa364cd850f8f2d8ff399ebb0ce5fb287b9f1ac3b05e8996aa4d 6061 
apt-show-versions_0.22.12+nmu1_source.buildinfo
Files:
 52ce57556ab30ec465edfa77468057ed 1716 admin optional 
apt-show-versions_0.22.12+nmu1.dsc
 a977545454662169a3c2505153e39c14 31700 admin optional 
apt-show-versions_0.22.12+nmu1.tar.xz
 6550b22f215eb262383782e8dd236fa0 6061 admin optional 
apt-show-versions_0.22.12+nmu1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAmFc43gACgkQ/A2xu81G
C94VoBAA2ucNqzJNpQP9RGid9q+HUwj0A+aRFZSdFztVlZ9jd3tssW2EI

Bug#996586: heimdal: CVE-2021-3671

[Brian May]

Salvatore Bonaccorso  writes:

> Source: heimdal
> Version: 7.7.0+dfsg-2
> Severity: grave
> Tags: security upstream
> Justification: user security hole
> X-Debbugs-Cc: car...@debian.org, Debian Security Team 
> 
> Control: found -1 7.5.0+dfsg-3

Does this need to be grave? Considering it was considered a minor issue
everywhere else, maybe not?

I attempted to fix this for unstable - and committed changed to Debian
git repo, but:


* Patch breaks compilation on latest Heimdal release:

krb5tgs.c: In function ‘tgs_build_reply’:
krb5tgs.c:1665:2: warning: implicit declaration of function ‘_kdc_set_e_text’ 
[-Wimplicit-function-declaration]
 1665 |  _kdc_set_e_text(priv, "No server in request");
  |  ^~~
krb5tgs.c:1665:2: warning: nested extern declaration of ‘_kdc_set_e_text’ 
[-Wnested-externs]
krb5tgs.c:1665:18: error: ‘priv’ undeclared (first use in this function)
 1665 |  _kdc_set_e_text(priv, "No server in request");
  |  ^~~~
krb5tgs.c:1665:18: note: each undeclared identifier is reported only once for 
each function it appears in
  CC   config.o
make[2]: *** [Makefile:1037: krb5tgs.lo] Error 1


* Heimdal doesn't appear build on sid anymore. Syntax error in
  configure, which I can't work out (the file looks fine to me).

checking for dn_expand... yes
checking for _res... yes
./configure: line 20867: syntax error near unexpected token `)'
./configure: line 20867: `)'
make[1]: *** [debian/rules:38: override_dh_auto_configure] Error 2


Anyway, just my status for now. Help appreciated :-)
-- 
Brian May 

Bug#996722: src:python-volatile: fails to migrate to testing for too long: uploader built arch:all binaries

[Nicholas D Steeves]

Hi Paul!

Paul Gevers  writes:

> Source: python-volatile
> Version: 2.1.0-2
> Severity: serious
> Control: close -1 2.1.0-3
> X-Debbugs-CC: jel...@debian.org   
> Tags: sid bookworm pending
> User: release.debian@packages.debian.org
> Usertags: out-of-sync
>
[snip]
> I have immediately closed this bug with the version in unstable, so if
> that version or a later version migrates, this bug will no longer affect
> testing. I have also tagged this bug to only affect sid and bookworm, so
> it doesn't affect (old-)stable.
>
> Your package is only blocked because the arch:all binary package(s)
> aren't built on a buildd. Unfortunately the Debian infrastructure
> doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will
> shortly do a no-changes source-only upload to DELAYED/15, closing this
> bug. Please let me know if I should delay or cancel that upload.
>

Solving this bug justifies an upload, and I'd also like to update my
email address in src:python-volatile.  Normally I don't think changing
an email address would justify an upload, so this is a great opportunity
;-)

I will of course credit you for identifying this issue and taking the
initiative to fix it, and will upload without delay once I receive your
ACK (please CC me).

For future reference, if there was an NMUdiff, I would incorporate it
into the -4 release along with my change, but then, what is the best
practise?  Ask for the NMU submitter to cancel the delayed upload,
upload -4 which will presumably cause -3.1 to be rejected when the
delayed timer fires, or cancel the delayed upload myself?

Thanks!
Nicholas


signature.asc
Description: PGP signature

Processed: Re: Bug#994258: python-django breaks lava autopkgtest: PASSWORD_RESET_TIMEOUT_DAYS/PASSWORD_RESET_TIMEOUT are mutually exclusive.

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #994258 [src:python-django, src:lava] python-django breaks lava 
autopkgtest: PASSWORD_RESET_TIMEOUT_DAYS/PASSWORD_RESET_TIMEOUT are mutually 
exclusive.
Bug 994258 cloned as bug 996931
> reassign -1 lava-server 2020.12-5
Bug #994258 [src:python-django, src:lava] python-django breaks lava 
autopkgtest: PASSWORD_RESET_TIMEOUT_DAYS/PASSWORD_RESET_TIMEOUT are mutually 
exclusive.
Bug reassigned from package 'src:python-django, src:lava' to 'lava-server'.
No longer marked as found in versions python-django/2:3.2.7-4 and 
lava/2020.12-5.
Ignoring request to alter fixed versions of bug #994258 to the same values 
previously set
Bug #994258 [lava-server] python-django breaks lava autopkgtest: 
PASSWORD_RESET_TIMEOUT_DAYS/PASSWORD_RESET_TIMEOUT are mutually exclusive.
Marked as found in versions lava/2020.12-5.
> retitle -1 lava-server fails to install with python3-django 3.2
Bug #994258 [lava-server] python-django breaks lava autopkgtest: 
PASSWORD_RESET_TIMEOUT_DAYS/PASSWORD_RESET_TIMEOUT are mutually exclusive.
Changed Bug title to 'lava-server fails to install with python3-django 3.2' 
from 'python-django breaks lava autopkgtest: 
PASSWORD_RESET_TIMEOUT_DAYS/PASSWORD_RESET_TIMEOUT are mutually exclusive.'.
> reassign -2 python3-django 2:3.2.8-1
Bug #996931 [src:python-django, src:lava] python-django breaks lava 
autopkgtest: PASSWORD_RESET_TIMEOUT_DAYS/PASSWORD_RESET_TIMEOUT are mutually 
exclusive.
Bug reassigned from package 'src:python-django, src:lava' to 'python3-django'.
No longer marked as found in versions python-django/2:3.2.7-4 and 
lava/2020.12-5.
Ignoring request to alter fixed versions of bug #996931 to the same values 
previously set
Bug #996931 [python3-django] python-django breaks lava autopkgtest: 
PASSWORD_RESET_TIMEOUT_DAYS/PASSWORD_RESET_TIMEOUT are mutually exclusive.
Marked as found in versions python-django/2:3.2.8-1.
> retitle -2 python3-django needs Breaks for the bullseye lava-server
Bug #996931 [python3-django] python-django breaks lava autopkgtest: 
PASSWORD_RESET_TIMEOUT_DAYS/PASSWORD_RESET_TIMEOUT are mutually exclusive.
Changed Bug title to 'python3-django needs Breaks for the bullseye lava-server' 
from 'python-django breaks lava autopkgtest: 
PASSWORD_RESET_TIMEOUT_DAYS/PASSWORD_RESET_TIMEOUT are mutually exclusive.'.
> block -2 by -1
Bug #996931 [python3-django] python3-django needs Breaks for the bullseye 
lava-server
996931 was not blocked by any bugs.
996931 was not blocking any bugs.
Added blocking bug(s) of 996931: 994258

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

Bug#994258: python-django breaks lava autopkgtest: PASSWORD_RESET_TIMEOUT_DAYS/PASSWORD_RESET_TIMEOUT are mutually exclusive.

[Adrian Bunk]

Control: clone -1 -2
Control: reassign -1 lava-server 2020.12-5
Control: retitle -1 lava-server fails to install with python3-django 3.2
Control: reassign -2 python3-django 2:3.2.8-1
Control: retitle -2 python3-django needs Breaks for the bullseye lava-server
Control: block -2 by -1

On Tue, Sep 14, 2021 at 09:27:21PM +0200, Paul Gevers wrote:
>...
> lava-server manage migrate --noinput --fake-initial
> Traceback (most recent call last):
>   File "/usr/bin/lava-server", line 68, in 
> main()
>   File "/usr/bin/lava-server", line 64, in main
> execute_from_command_line([sys.argv[0]] + options.command)
>   File
> "/usr/lib/python3/dist-packages/django/core/management/__init__.py",
> line 419, in execute_from_command_line
> utility.execute()
>   File
> "/usr/lib/python3/dist-packages/django/core/management/__init__.py",
> line 413, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "/usr/lib/python3/dist-packages/django/core/management/base.py",
> line 354, in run_from_argv
> self.execute(*args, **cmd_options)
>   File "/usr/lib/python3/dist-packages/django/core/management/base.py",
> line 398, in execute
> output = self.handle(*args, **options)
>   File "/usr/lib/python3/dist-packages/django/core/management/base.py",
> line 86, in wrapped
> saved_locale = translation.get_language()
>   File
> "/usr/lib/python3/dist-packages/django/utils/translation/__init__.py",
> line 254, in get_language
> return _trans.get_language()
>   File
> "/usr/lib/python3/dist-packages/django/utils/translation/__init__.py",
> line 57, in __getattr__
> if settings.USE_I18N:
>   File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line
> 82, in __getattr__
> self._setup(name)
>   File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line
> 69, in _setup
> self._wrapped = Settings(settings_module)
>   File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line
> 190, in __init__
> raise ImproperlyConfigured(
> django.core.exceptions.ImproperlyConfigured:
> PASSWORD_RESET_TIMEOUT_DAYS/PASSWORD_RESET_TIMEOUT are mutually exclusive.

Note that what fails is installing lava-server, this can be reproduced 
easily just by trying to install the package.

I'm splitting this into two bugs:
1. lava-server needs fixing for Django 3.2 (Antonio told me that work is 
ongoing)
2. after that, python3-django needs Breaks against older versions
   this is important both for upgrades from bullseye, and for 
   python3-django/bullseye-backports that will likely exist

cu
Adrian

Bug#996631: marked as done (llvm-toolchain-13: autopkgtest failure)

[Debian Bug Tracking System]

Your message dated Wed, 20 Oct 2021 22:34:02 +
with message-id 
and subject line Bug#996551: fixed in llvm-toolchain-13 1:13.0.0-7
has caused the Debian Bug report #996551,
regarding llvm-toolchain-13: autopkgtest failure
to be marked as done.

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

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


-- 
996551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996551
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: llvm-toolchain-13
Version: 1:13.0.0-4
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

The changes in 1:13.0.0-4 introduced new autopkgtest failures:

| autopkgtest [11:21:06]: test cmake-test: [---
| -- The C compiler identification is GNU 10.3.0
| -- The CXX compiler identification is GNU 10.3.0
| -- Detecting C compiler ABI info
| -- Detecting C compiler ABI info - done
| -- Check for working C compiler: /usr/bin/cc - skipped
| -- Detecting C compile features
| -- Detecting C compile features - done
| -- Detecting CXX compiler ABI info
| -- Detecting CXX compiler ABI info - done
| -- Check for working CXX compiler: /usr/bin/c++ - skipped
| -- Detecting CXX compile features
| -- Detecting CXX compile features - done
| -- Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR) 
| -- Found LibXml2: /usr/lib/aarch64-linux-gnu/libxml2.so (found version 
"2.9.12") 
| CMake Error at /usr/lib/llvm-13/lib/cmake/llvm/LLVMExports.cmake:1501 
(message):
|   The imported target "llvm-omp-device-info" references the file
|
|  "/usr/lib/llvm-13/bin/llvm-omp-device-info"
|
|   but this file does not exist.  Possible reasons include:
|
|   * The file was deleted, renamed, or moved to another location.
|
|   * An install or uninstall procedure did not complete successfully.
|
|   * The installation package was faulty and contained
|
|  "/usr/lib/llvm-13/lib/cmake/llvm/LLVMExports.cmake"
|
|   but not all the files it references.
|
| Call Stack (most recent call first):
|   /usr/lib/llvm-13/cmake/LLVMConfig.cmake:299 (include)
|   CMakeLists.txt:3 (find_package)
|
|
| -- Configuring incomplete, errors occurred!
| See also 
"/tmp/autopkgtest-lxc.w3ziie21/downtmp/autopkgtest_tmp/build/CMakeFiles/CMakeOutput.log".
| autopkgtest [11:21:08]: test cmake-test: ---]
| autopkgtest [11:21:09]: test cmake-test:  - - - - - - - - - - results - - - - 
- - - - - -
| cmake-test   FAIL non-zero exit status 1

See
https://ci.debian.net/data/autopkgtest/testing/amd64/l/llvm-toolchain-13/15959122/log.gz

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-13
Source-Version: 1:13.0.0-7
Done: Sylvestre Ledru 

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated llvm-toolchain-13 
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: Wed, 20 Oct 2021 07:36:28 +0200
Source: llvm-toolchain-13
Architecture: source
Version: 1:13.0.0-7
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Closes: 995827 996551
Changes:
 llvm-toolchain-13 (1:13.0.0-7) unstable; urgency=medium
 .
   * Remove omp-device-info from LLVMExports.cmake (Closes: #996551)
 For real this time
   * Fix the link issue (hopefully on all archs) (Closes: #995827)
 customs LDFLAGS were not passed to the stage2
   * Trim trailing whitespace.
   * Update watch file format version to 4.
   * Update to compat 11.
 oldstable has 12
 bionic has 11
Checksums-Sha1:
 5cf7bce707ce681f48ac7cebaca33c2c36975f6f 6704 llvm-toolchain-13_13.0.0-7.dsc
 dc62d18e82398fef95ffa0719572aee0d829dc9d 141632 
llvm-toolchain-13_13.0.0-7.debian.tar.xz
 0ad88a98af3087a2b0383b8e259620a057948a8e 29018 
llvm-toolchain-13_13.0.0-7_amd64.buildinfo
Checksums-Sha256:
 bce98bbfb8119e4b21390bd2eed52edeac859d3b0ba5255fccb0b6a9e4e8c830 6704 
llvm-toolchain-13_13.0.0-7.dsc
 65c17383b4f70f44124d2384b9b8a31f85f30930d343a30e1eaba86b69c36c99 1416

Bug#996551: marked as done (llvm-13-dev: Missing dependency to libomp-13-dev)

[Debian Bug Tracking System]

Your message dated Wed, 20 Oct 2021 22:34:02 +
with message-id 
and subject line Bug#996551: fixed in llvm-toolchain-13 1:13.0.0-7
has caused the Debian Bug report #996551,
regarding llvm-13-dev: Missing dependency to libomp-13-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.)


-- 
996551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996551
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: llvm-13-dev
Version: 1:13.0.0-5
Severity: important
X-Debbugs-Cc: joubert...@gmail.com

Dear Maintainer,

With the recent move of llvm-omp-device-info from llvm-X to libomp8-dev, done
in llvm-toolchain-13 (1:13.0.0-4),
this package should now depend on libomp-X-dev

The current situation is that llvm-X-dev references llvm-omp-device-info as
part of an installed targets in its cmake
configuration, but since it no longer provides that file any attempt to use the
LLVM cmake package results in an error:

CMake Error at /usr/lib/llvm-13/lib/cmake/llvm/LLVMExports.cmake:1501
(message):
  The imported target "llvm-omp-device-info" references the file
 "/usr/lib/llvm-13/bin/llvm-omp-device-info"
  but this file does not exist.  Possible reasons include:
  * The file was deleted, renamed, or moved to another location.
  * An install or uninstall procedure did not complete successfully.
  * The installation package was faulty and contained
 "/usr/lib/llvm-13/lib/cmake/llvm/LLVMExports.cmake"
  but not all the files it references.

Manually installing libomp-X-dev fixes the problem.


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (800, 'stable-updates'), (800, 'stable'), (700,
'unstable'), (90, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages llvm-13-dev depends on:
ii  libc6  2.32-4
ii  libclang-cpp13 1:13.0.0-5
ii  libffi-dev 3.4.2-2
ii  libgcc-s1  11.2.0-9
ii  libllvm13  1:13.0.0-5
ii  libncurses-dev [libtinfo-dev]  6.2+20201114-4
ii  libstdc++6 11.2.0-9
ii  libtinfo-dev   6.2+20201114-4
ii  libxml2-dev2.9.12+dfsg-5
ii  libz3-dev  4.8.12-1+b1
ii  llvm-131:13.0.0-5
ii  llvm-13-tools  1:13.0.0-5

llvm-13-dev recommends no packages.

llvm-13-dev suggests no packages.
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-13
Source-Version: 1:13.0.0-7
Done: Sylvestre Ledru 

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated llvm-toolchain-13 
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: Wed, 20 Oct 2021 07:36:28 +0200
Source: llvm-toolchain-13
Architecture: source
Version: 1:13.0.0-7
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Closes: 995827 996551
Changes:
 llvm-toolchain-13 (1:13.0.0-7) unstable; urgency=medium
 .
   * Remove omp-device-info from LLVMExports.cmake (Closes: #996551)
 For real this time
   * Fix the link issue (hopefully on all archs) (Closes: #995827)
 customs LDFLAGS were not passed to the stage2
   * Trim trailing whitespace.
   * Update watch file format version to 4.
   * Update to compat 11.
 oldstable has 12
 bionic has 11
Checksums-Sha1:
 5cf7bce707ce681f48ac7cebaca33c2c36975f6f 6704 llvm-toolchain-13_13.0.0-7.dsc
 dc62d18e82398fef95ffa0719572aee0d829dc9d 141632 
llvm-toolchain-13_13.0.0-7.debian.tar.xz
 0ad88a98af3087a2b0383b8e259620a057948a8e 29018 
llvm-toolchain-13_13.0.0-7_amd64.buildinfo
Checksums-Sha256:
 bce98bbfb8119e4b21390bd2eed52edeac859d3b0ba5255fccb0b6a9e4e8c830 6704 
llvm-toolchain-1

Bug#996558: marked as done (knot: FTBFS with new automake (putting "none required" into build flags))

[Debian Bug Tracking System]

Your message dated Thu, 21 Oct 2021 00:14:24 +0200
with message-id 
and subject line Re: Bug#996558: knot: FTBFS with new automake (putting "none 
required" into build flags)
has caused the Debian Bug report #996558,
regarding knot: FTBFS with new automake (putting "none required" into build 
flags)
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.)


-- 
996558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996558
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: knot
Version: 3.0.5-1
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu  ubuntu-patch
X-Debbugs-Cc: sl...@ubuntu.com

Dear Maintainer,

knot fails to build from source with newer autotools:


libtool: link: gcc -g -O2 -ffile-prefix-map=/<>=. -flto=auto 
-ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security 
-Wall -DNDEBUG -Wall -Wshadow -Werror=format-security -Werror=implicit 
-Werror=attributes -Wstrict-prototypes -Wl,-Bsymbolic-functions -flto=auto 
-Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -o .libs/kxdpgun 
utils/kxdpgun/kxdpgun-load_queries.o utils/kxdpgun/kxdpgun-main.o 
utils/kxdpgun/kxdpgun-popenve.o none required  ./.libs/libcontrib.a 
./.libs/libknot.so -lcap-ng
/usr/bin/ld: cannot find none: No such file or directory
/usr/bin/ld: cannot find required: No such file or directory
collect2: error: ld returned 1 exit status
make[4]: *** [Makefile:3354: kxdpgun] Error 1


The problem was fixed upstream:
https://gitlab.nic.cz/knot/knot-dns/-/commit/70dc4a5c85b65678662854c18a3475371ef4a8eb

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

  * Fix FTBFS with new automake, using upstream commit
+ debian/patches/70dc4a5c85b65678662854c18a3475371ef4a8eb.patch


Thanks for considering the patch.

Cheers,
  Lukas

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

Kernel: Linux 5.13.0-16-generic (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE:en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru 
knot-3.0.5/debian/patches/70dc4a5c85b65678662854c18a3475371ef4a8eb.patch 
knot-3.0.5/debian/patches/70dc4a5c85b65678662854c18a3475371ef4a8eb.patch
--- knot-3.0.5/debian/patches/70dc4a5c85b65678662854c18a3475371ef4a8eb.patch
1970-01-01 01:00:00.0 +0100
+++ knot-3.0.5/debian/patches/70dc4a5c85b65678662854c18a3475371ef4a8eb.patch
2021-10-15 15:14:17.0 +0200
@@ -0,0 +1,60 @@
+From 70dc4a5c85b65678662854c18a3475371ef4a8eb Mon Sep 17 00:00:00 2001
+From: Daniel Salzman 
+Date: Wed, 14 Jul 2021 14:29:13 +0200
+Subject: [PATCH] configure: fix AC_SEARCH_LIBS usage if the result is cached
+ with value 'none required'
+
+---
+ configure.ac | 14 +-
+ 1 file changed, 9 insertions(+), 5 deletions(-)
+
+diff --git a/configure.ac b/configure.ac
+index 0d3552045..c8f1f4548 100644
+--- a/configure.ac
 b/configure.ac
+@@ -613,9 +613,10 @@ AS_IF([test "$enable_cap_ng" != "no"],[
+ AC_CHECK_HEADER([cap-ng.h], [
+   save_LIBS="$LIBS"
+   AC_SEARCH_LIBS([capng_apply], [cap-ng], [
+-enable_cap_ng=yes
+-cap_ng_LIBS="$ac_cv_search_capng_apply"
++AS_IF([test "$ac_cv_search_capng_apply" != "none required"],
++  [cap_ng_LIBS="$ac_cv_search_capng_apply"], [cap_ng_LIBS=])
+ AC_SUBST([cap_ng_LIBS])
++enable_cap_ng=yes
+   ])
+   LIBS="$save_LIBS"
+ ])
+@@ -631,7 +632,8 @@ AS_IF([test "$enable_cap_ng" = yes],
+ 
+ save_LIBS="$LIBS"
+ AC_SEARCH_LIBS([pthread_create], [pthread], [
+-  pthread_LIBS="$ac_cv_search_pthread_create"
++  AS_IF([test "$ac_cv_search_pthread_create" != "none required"],
++[pthread_LIBS="$ac_cv_search_pthread_create"], [pthread_LIBS=])
+   AC_SUBST([pthread_LIBS])
+ ],[
+   AC_MSG_ERROR([pthreads not found])
+@@ -640,7 +642,8 @@ LIBS="$save_LIBS"
+ 
+ save_LIBS="$LIBS"
+ AC_SEARCH_LIBS([dlopen], [dl], [
+-  dlopen_LIBS="$ac_cv_search_dlopen"
++  AS_IF([test "$ac_cv_search_dlopen" != "none required"],
++[dlopen_LIBS="$ac_cv_search_dlopen"], [dlopen_LIBS=])
+   AC_SUBST([dlopen_LIBS])
+ ],[
+   AC_MSG_ERROR([dlopen not found])
+@@ -649,7 +652,8 @@ LIBS="$save_LIBS"
+ 
+ save_LIBS="$LIBS"
+ AC_SEARCH_LIBS([pow], [m], [
+-  math_LIBS="$ac_cv_search_pow"
++  AS_IF([t

Processed: tagging 996558

[Debian Bug Tracking System]

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

> tags 996558 + sid bookworm
Bug #996558 [knot] knot: FTBFS with new automake (putting "none required" into 
build flags)
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.

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

Processed: tagging 996905, tagging 996906, tagging 996169

[Debian Bug Tracking System]

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

> tags 996905 + sid bookworm
Bug #996905 [src:pms] pms FTBFS: error: format not a string literal and no 
format arguments [-Werror=format-security]
Added tag(s) sid and bookworm.
> tags 996906 + sid bookworm
Bug #996906 [src:klibc] klibc FTBFS on armhf: cc1: error: '-mfloat-abi=hard': 
selected architecture lacks an FPU
Added tag(s) sid and bookworm.
> tags 996169 + sid bookworm
Bug #996169 {Done: Shengjing Zhu } [packer] 
step_run_spot_instance.go:69:59: cannot convert mapping.Ebs
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.

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

Bug#996716: marked as done (pyopencl: FTBFS on 32-bit arches; autopkgtest regression: test-depends on removed package)

[Debian Bug Tracking System]

Your message dated Wed, 20 Oct 2021 21:49:05 +
with message-id 
and subject line Bug#996716: fixed in pyopencl 2021.2.9-1
has caused the Debian Bug report #996716,
regarding pyopencl: FTBFS on 32-bit arches; autopkgtest regression: 
test-depends on removed package
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.)


-- 
996716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996716
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyopencl
Version: 2021.2.2-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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

   passfail
pyopencl   from testing2021.2.2-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. The package
python3-pyopencl-dbg was dropped in the latest upload but the test still
depends on it. On top of that, the package also FTBFS on armel, armhf
and i386 (all 32-bits archs).

Currently these 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=pyopencl

https://ci.debian.net/data/autopkgtest/testing/arm64/p/pyopencl/15992067/log.gz

autopkgtest [23:21:15]: testbed dpkg architecture: arm64
Reading package lists...
Building dependency tree...
Reading state information...
Correcting dependencies...Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) autopkgtest-satdep:arm64 < 0 @iU K Nb Ib >
Broken autopkgtest-satdep:arm64 Depends on python3-pyopencl-dbg:arm64 <
none @un H >
  Considering python3-pyopencl-dbg:arm64 1 as a solution to
autopkgtest-satdep:arm64 -2
  Removing autopkgtest-satdep:arm64 rather than change
python3-pyopencl-dbg:arm64
Done
 Done
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
The following additional packages will be installed:
  libmpdec3 libpython3.9-stdlib media-types python3.9
Suggested packages:
  python3.9-venv python3.9-doc
The following packages will be REMOVED:
  autopkgtest-satdep
The following NEW packages will be installed:
  libmpdec3 libpython3.9-stdlib media-types python3.9
0 upgraded, 4 newly installed, 1 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 2,258 kB of archives.
After this operation, 8,833 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian testing/main arm64 media-types all
4.0.0 [30.3 kB]
Get:2 http://deb.debian.org/debian testing/main arm64 libmpdec3 arm64
2.5.1-2 [84.4 kB]
Get:3 http://deb.debian.org/debian testing/main arm64
libpython3.9-stdlib arm64 3.9.7-4 [1,663 kB]
Get:4 http://deb.debian.org/debian testing/main arm64 python3.9 arm64
3.9.7-4 [480 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 2,258 kB in 0s (30.1 MB/s)
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 13210 files and directories currently installed.)
Removing autopkgtest-satdep (0) ...
Selecting previously unselected package media-types.
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%

Bug#993431: marked as done (virtuoso-opensource: checking WBXML2 library usability... bad. Check config.log for details)

[Debian Bug Tracking System]

Your message dated Wed, 20 Oct 2021 21:49:59 +
with message-id 
and subject line Bug#993431: fixed in virtuoso-opensource 7.2.5.1+dfsg1-0.2
has caused the Debian Bug report #993431,
regarding virtuoso-opensource: checking WBXML2 library usability... bad. Check 
config.log for details
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.)


-- 
993431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993431
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: virtuoso-opensource
Version: 7.2.5.1+dfsg1-0.1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

virtuoso-opensource silently drops support for WBXML2 when building
against libwbxml2-dev 0.11.7:

| checking WBXML2 library usability... bad. Check config.log for details

and later:

| make[5]: Entering directory '/<>/binsrc/samples/wbxml2'
| **
| ** WARNING: wbxml2 plugin can not be build
| **
| make[5]: Leaving directory '/<>/binsrc/samples/wbxml2'

https://buildd.debian.org/status/fetch.php?pkg=virtuoso-opensource&arch=amd64&ver=7.2.5.1%2Bdfsg1-0.1%2Bb1&stamp=1630425431&raw=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: virtuoso-opensource
Source-Version: 7.2.5.1+dfsg1-0.2
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated virtuoso-opensource 
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: Wed, 20 Oct 2021 23:11:44 +0200
Source: virtuoso-opensource
Architecture: source
Version: 7.2.5.1+dfsg1-0.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Andreas Beckmann 
Closes: 993390 993431
Changes:
 virtuoso-opensource (7.2.5.1+dfsg1-0.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix WBXML2 0.11 detection.  (Closes: #993431)
   * Use libtirpc-dev.  (Closes: #993390)
   * The bullseye toolchain defaults to linking with --as-needed.
   * Set Rules-Requires-Root: no.
   * Update Lintian overrides.
   * Drop NEWS from 2010.
Checksums-Sha1:
 270620dea7ba2585d42641d2f0a3f69384b198e5 4050 
virtuoso-opensource_7.2.5.1+dfsg1-0.2.dsc
 fdac53eac142649f42dd8c525fde115387f835ae 72384 
virtuoso-opensource_7.2.5.1+dfsg1-0.2.debian.tar.xz
 18e945e252c108f6e65c622b7e3733f9138ee2d7 22268 
virtuoso-opensource_7.2.5.1+dfsg1-0.2_source.buildinfo
Checksums-Sha256:
 3f9e03e995a9a909a6719dc91ce3b276ca43030e835b462ced4c6b8c4da08cf3 4050 
virtuoso-opensource_7.2.5.1+dfsg1-0.2.dsc
 ee98534897ca2b24e15662193f318f13ca627bb3ee0d639e1964113edeb87acd 72384 
virtuoso-opensource_7.2.5.1+dfsg1-0.2.debian.tar.xz
 ec914550e69a9ee8bdec48f1d173f3a612d1d4a18d17aee4b24ef74b0bd05b87 22268 
virtuoso-opensource_7.2.5.1+dfsg1-0.2_source.buildinfo
Files:
 5d8d32c884a4ec180342c403c4436565 4050 database optional 
virtuoso-opensource_7.2.5.1+dfsg1-0.2.dsc
 9e7d07ceac438af9d09dc83cb9525af2 72384 database optional 
virtuoso-opensource_7.2.5.1+dfsg1-0.2.debian.tar.xz
 e8054d4f6d7467f7e6dc0d8104873ee5 22268 database optional 
virtuoso-opensource_7.2.5.1+dfsg1-0.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmFwib4QHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCAiQD/0QdThMu59FPVQsPpaWIRQQK4R3uEan+eKh
3/PhxmmtODYHa2qYraVuNhQQFy1GuqCmeLGUcoWcTjmg+3eqCo/ykCsWEjm8DW88
2TJPmj66qPTiHEZapN9ZXqINV1Z1eQj/429J33xIrAng46vbERcMhRIoFVxcodR1
QgTkPPhCZsWvMMsAbvToYp3NMxY/dmEDlIw0VNQtSd91dogNnHQepoTewNvD04pP
hJ5H8gu7FxAxEnE1FbGZEKPPaHcLku8km9Qb+xJxqqq3p3J2uggGBQobJI4Ivqqf
9C78LSKrmGcOeS1is6puOstKXhHDfbs1yB5AfVFIRCwW1yA3V8QLOXSzNUB5xC6Y
FYKHoiOUoCclCSdrZ4KxlJ7eN4tc4/ewvIQHJjXnuJHWXMxv/DGQMf9AMdiGOH4+
Yupqf1mIKUbABGf429pCdTBqUjDcI93nmW3XA0qv6AQDzk2yjM/1LgjPEZYNrk2z
77C5UmxXbUjPcYre/q+5VRpDbrQAzyDcYMgNqMum8AAq5H33BZgXnU3tQpxi9jiZ
FNF6J51D9rnRRbb4hlhHwr2KMtrLbPKjE7UKfXHBtIiOswW/31XxcoL++g7ElwIL
oU23aWfmd1cJcuD+MGZQjD0d3qHfacLLDeaHDjSMeebx6j8aWayc3gtTa+wYGewr
Rv330V7Klg==
=o+YB
-END PGP SIGNATURE End Message ---

Bug#993390: marked as done (virtuoso-opensource: FTBFS: Dkmarshal.c:50:11: fatal error: rpc/types.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 20 Oct 2021 21:49:59 +
with message-id 
and subject line Bug#993390: fixed in virtuoso-opensource 7.2.5.1+dfsg1-0.2
has caused the Debian Bug report #993390,
regarding virtuoso-opensource: FTBFS: Dkmarshal.c:50:11: fatal error: 
rpc/types.h: No such file or directory
to be marked as done.

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

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


-- 
993390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993390
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: virtuoso-opensource
Version: 7.2.5.1+dfsg1-0.1
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

| libtool: compile:  gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 
-fno-strict-aliasing -O2 -Wall -DNDEBUG -DPOINTER_64 
-I/<>/libsrc/Xml.new -DOPENSSL_NO_KRB5 -Dlinux -D_GNU_SOURCE 
-DFILE64 -D_LARGEFILE64_SOURCE -I../../libsrc -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -D_GNU_SOURCE -c Dkmem.c  -fPIC -DPIC -o 
.libs/libdksrv_la-Dkmem.o
| Dkmarshal.c:50:11: fatal error: rpc/types.h: No such file or directory
|50 | # include 
|   |   ^
| compilation terminated.
| make[5]: *** [Makefile:1169: libdksrv_la-Dkmarshal.lo] Error 1

https://buildd.debian.org/status/fetch.php?pkg=virtuoso-opensource&arch=arm64&ver=7.2.5.1%2Bdfsg1-0.1%2Bb1&stamp=1630424102&raw=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: virtuoso-opensource
Source-Version: 7.2.5.1+dfsg1-0.2
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated virtuoso-opensource 
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: Wed, 20 Oct 2021 23:11:44 +0200
Source: virtuoso-opensource
Architecture: source
Version: 7.2.5.1+dfsg1-0.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Andreas Beckmann 
Closes: 993390 993431
Changes:
 virtuoso-opensource (7.2.5.1+dfsg1-0.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix WBXML2 0.11 detection.  (Closes: #993431)
   * Use libtirpc-dev.  (Closes: #993390)
   * The bullseye toolchain defaults to linking with --as-needed.
   * Set Rules-Requires-Root: no.
   * Update Lintian overrides.
   * Drop NEWS from 2010.
Checksums-Sha1:
 270620dea7ba2585d42641d2f0a3f69384b198e5 4050 
virtuoso-opensource_7.2.5.1+dfsg1-0.2.dsc
 fdac53eac142649f42dd8c525fde115387f835ae 72384 
virtuoso-opensource_7.2.5.1+dfsg1-0.2.debian.tar.xz
 18e945e252c108f6e65c622b7e3733f9138ee2d7 22268 
virtuoso-opensource_7.2.5.1+dfsg1-0.2_source.buildinfo
Checksums-Sha256:
 3f9e03e995a9a909a6719dc91ce3b276ca43030e835b462ced4c6b8c4da08cf3 4050 
virtuoso-opensource_7.2.5.1+dfsg1-0.2.dsc
 ee98534897ca2b24e15662193f318f13ca627bb3ee0d639e1964113edeb87acd 72384 
virtuoso-opensource_7.2.5.1+dfsg1-0.2.debian.tar.xz
 ec914550e69a9ee8bdec48f1d173f3a612d1d4a18d17aee4b24ef74b0bd05b87 22268 
virtuoso-opensource_7.2.5.1+dfsg1-0.2_source.buildinfo
Files:
 5d8d32c884a4ec180342c403c4436565 4050 database optional 
virtuoso-opensource_7.2.5.1+dfsg1-0.2.dsc
 9e7d07ceac438af9d09dc83cb9525af2 72384 database optional 
virtuoso-opensource_7.2.5.1+dfsg1-0.2.debian.tar.xz
 e8054d4f6d7467f7e6dc0d8104873ee5 22268 database optional 
virtuoso-opensource_7.2.5.1+dfsg1-0.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmFwib4QHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCAiQD/0QdThMu59FPVQsPpaWIRQQK4R3uEan+eKh
3/PhxmmtODYHa2qYraVuNhQQFy1GuqCmeLGUcoWcTjmg+3eqCo/ykCsWEjm8DW88
2TJPmj66qPTiHEZapN9ZXqINV1Z1eQj/429J33xIrAng46vbERcMhRIoFVxcodR1
QgTkPPhCZsWvMMsAbvToYp3NMxY/dmEDlIw0VNQtSd91dogNnHQepoTewNvD04pP
hJ5H8gu7FxAxEnE1FbGZEKPPaHcLku8km9Qb+xJxqqq3p3J2uggGBQobJI4Ivqqf
9C78LSKrmGcOeS1is6puOstKXhHDfbs1yB5AfVFIRCwW1yA3V8QLOXSzNUB5xC6Y
FYKHoiOUoCclCSdrZ4KxlJ7eN4tc4/e

Bug#985932: marked as done (openstack-trove should not be included in Bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 20 Oct 2021 22:58:52 +0200
with message-id 
and subject line This can be closed
has caused the Debian Bug report #985932,
regarding openstack-trove should not be included in 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.)


-- 
985932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openstack-trove
Version: 1:13.0.0-1
Severity: serious

Hi,

I never really tried Trove myself, and therefore, I would prefer if it was not
part of Bullseye. It will still be available from the unofficial repository
of OpenStack (osbpo.debian.net, accessible with extrepo).

Cheers,

Thomas Goirand (zigo)
--- End Message ---
--- Begin Message ---
This can be closed--- End Message ---

Bug#996922: firefox exits with SIGFPE on startup (no user interaction)

[Bastian Germann]

Package: firefox
Version: 92.0-1
Severity: grave

Dear Maintainer,

   * What led up to the situation?

Starting firefox or firefox-esr (or even chromium). I guess it is caused by a 
common dependency only on i386.

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

No user interaction.

   * What was the outcome of this action?

The browser exits after showing a crashed tab panel with SIGFPE.

   * What outcome did you expect instead?

Running the browser normally.



-- Package-specific info:

Starting program: /usr/bin/firefox.real 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[New Thread 0xb77ffac0 (LWP 11257)]
[Thread 0xb77ffac0 (LWP 11257) exited]
[Detaching after fork from child process 11258]
[Detaching after fork from child process 11259]
[New Thread 0xab86aac0 (LWP 11260)]
[New Thread 0xa73f1ac0 (LWP 11261)]
[New Thread 0xa73b0ac0 (LWP 11262)]
[New Thread 0xa736fac0 (LWP 11263)]
[New Thread 0xa70ffac0 (LWP 11264)]
[New Thread 0xb77ffac0 (LWP 11265)]
[New Thread 0xa6effac0 (LWP 11266)]
[New Thread 0xa64ffac0 (LWP 11269)]
[Detaching after fork from child process 11270]
[New Thread 0xabdb2ac0 (LWP 11271)]
[New Thread 0xa66b8ac0 (LWP 11272)]
[New Thread 0xa732eac0 (LWP 11273)]
[New Thread 0xa6677ac0 (LWP 11274)]
[New Thread 0xa52ffac0 (LWP 11277)]
[New Thread 0xa5100ac0 (LWP 11278)]
[New Thread 0xa5cfeac0 (LWP 11279)]
[New Thread 0xa5cbdac0 (LWP 11280)]
[New Thread 0xa5c7cac0 (LWP 11281)]
[New Thread 0xa4ab9ac0 (LWP 11282)]
[Thread 0xa64ffac0 (LWP 11269) exited]
[Thread 0xa4ab9ac0 (LWP 11282) exited]
[New Thread 0xa4ab9ac0 (LWP 11283)]
[New Thread 0xa64ffac0 (LWP 11284)]
[New Thread 0xa4258ac0 (LWP 11285)]
[Thread 0xa64ffac0 (LWP 11284) exited]
[New Thread 0xa64ffac0 (LWP 11286)]
[Thread 0xa4258ac0 (LWP 11285) exited]
[Thread 0xa4ab9ac0 (LWP 11283) exited]
[Thread 0xa64ffac0 (LWP 11286) exited]
[New Thread 0xa64ffac0 (LWP 11287)]
[New Thread 0xa4ab9ac0 (LWP 11288)]
[New Thread 0xa4258ac0 (LWP 11289)]
[Thread 0xa4ab9ac0 (LWP 11288) exited]
[Thread 0xa4258ac0 (LWP 11289) exited]
[New Thread 0xa3a4aac0 (LWP 11290)]
[New Thread 0xa38ffac0 (LWP 11291)]
[New Thread 0xa4258ac0 (LWP 11292)]
[New Thread 0xa4ab9ac0 (LWP 11293)]
[New Thread 0xa36ffac0 (LWP 11294)]
[New Thread 0xa32ffac0 (LWP 11295)]
[New Thread 0xa38beac0 (LWP 11296)]
[New Thread 0xa386dac0 (LWP 11297)]
[New Thread 0xa2a4cac0 (LWP 11298)]
[New Thread 0xa23ffac0 (LWP 11299)]
[Thread 0xa66b8ac0 (LWP 11272) exited]
[New Thread 0xa2250ac0 (LWP 11300)]
[New Thread 0xa66b8ac0 (LWP 11301)]
[New Thread 0xa16ffac0 (LWP 11302)]
[New Thread 0xa16beac0 (LWP 11303)]
[New Thread 0xa167dac0 (LWP 11304)]
[New Thread 0xa163cac0 (LWP 11305)]
[New Thread 0xa15fbac0 (LWP 11306)]
[New Thread 0xa15baac0 (LWP 11307)]
[New Thread 0xa1579ac0 (LWP 11308)]
[New Thread 0xa13ffac0 (LWP 11309)]
[Thread 0xa13ffac0 (LWP 11309) exited]
[Thread 0xa5cfeac0 (LWP 11279) exited]
[New Thread 0xa13beac0 (LWP 11310)]
[New Thread 0xa137dac0 (LWP 11311)]
[New Thread 0xa0effac0 (LWP 11312)]
[Thread 0xa13beac0 (LWP 11310) exited]
[Thread 0xa137dac0 (LWP 11311) exited]
[Thread 0xa0effac0 (LWP 11312) exited]
[New Thread 0xa0effac0 (LWP 11313)]
[New Thread 0xa137dac0 (LWP 11314)]
[New Thread 0xa3827ac0 (LWP 11315)]
[New Thread 0xa04ffac0 (LWP 11316)]
[New Thread 0xa02feac0 (LWP 11317)]
[New Thread 0xa00fdac0 (LWP 11318)]
[New Thread 0x9fcffac0 (LWP 11319)]
[New Thread 0xa13beac0 (LWP 11320)]
[New Thread 0xa5cfeac0 (LWP 11321)]
[Detaching after fork from child process 11322]
[New Thread 0xa13ffac0 (LWP 11324)]
[New Thread 0xa0e55ac0 (LWP 11326)]
[New Thread 0xa07ffac0 (LWP 11327)]
[New Thread 0x9efffac0 (LWP 11339)]
[New Thread 0x9edfeac0 (LWP 11340)]
[New Thread 0xa07beac0 (LWP 11341)]
[New Thread 0xa077dac0 (LWP 11342)]
[New Thread 0x9e9ffac0 (LWP 11343)]
[New Thread 0x9fe88ac0 (LWP 11344)]
[New Thread 0x9fe47ac0 (LWP 11345)]
[Thread 0xa5cbdac0 (LWP 11280) exited]
[New Thread 0x98cffac0 (LWP 11346)]
[New Thread 0xa5cbdac0 (LWP 11347)]
[Detaching after fork from child process 11348]
[New Thread 0xa0ea5ac0 (LWP 11349)]
[New Thread 0x9e09bac0 (LWP 11358)]
[New Thread 0x9e05aac0 (LWP 11364)]
[New Thread 0x97891ac0 (LWP 11365)]
[New Thread 0x1ac0 (LWP 11366)]
[New Thread 0x99950ac0 (LWP 11367)]
[New Thread 0x97850ac0 (LWP 11373)]
[New Thread 0x9678bac0 (LWP 11374)]
[New Thread 0xa0e64ac0 (LWP 11375)]
[New Thread 0x95dffac0 (LWP 11376)]
[New Thread 0x95bfeac0 (LWP 11377)]
[New Thread 0x959fdac0 (LWP 11378)]
[Detaching after fork from child process 11379]
[New Thread 0x967ffac0 (LWP 11381)]
[New Thread 0x952ffac0 (LWP 11383)]
[New Thread 0x9674aac0 (LWP 11398)]
[New Thread 0x957fcac0 (LWP 11399)]
[New Thread 0x9eb94ac0 (LWP 11412)]
[Thread 0x967ffac0 (LWP 11381) exited]

###!!! [Parent][MessageChannel] Error: 
(msgtype=0x390145,name=PContent::Msg_AsyncMessage) Channel error: cannot 
send/recv

[Detaching after fork from child process 11414]
[New Thread 0x917ffac0 (LWP 11415)]
[Thread 0x91

Processed: your mail

[Debian Bug Tracking System]

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

> tag #996241 + fixed pending
Bug #996241 [glm] glm: FTBFS with GCC-11 (test-core_func_integer)
Added tag(s) fixed and pending.
>
End of message, stopping processing here.

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

Bug#996712: libcache-memcached-fast-perl: autopkgtest failure on armhf: Fetched all keys / Match results

[gregor herrmann]

On Sun, 17 Oct 2021 18:40:24 +0200, Paul Gevers wrote:

> You recently added an autopkgtest to your package
> libcache-memcached-fast-perl, great. However, it fails on armhf.
> Currently this failure is blocking the migration to testing [1]. Can you
> please investigate the situation and fix it?

I don't know what exacatly is going on, but I note that it now also
fails on amd64.

I was a bit surprised that the same tests pass during build but the
explanation is simple: They are skipped as no memcached is running …

Guess mode: Either the tests or the code are incompatible with the
current memcached version, or the tests are not supposed to be run
against a production memcached (not started by the package).
 

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Processed: Bug#996511 marked as pending in ruby-sprockets

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #996511 [src:ruby-sprockets] ruby-sprockets: FTBFS with ruby3.0: ERROR: 
Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 2, 
expected 1)
Added tag(s) pending.

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

Bug#996511: marked as pending in ruby-sprockets

[Lucas Kanashiro]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/ruby-team/ruby-sprockets/-/commit/7986b93bf9b454ed39ed89c212acacee0a79e948


Add patch to fix FTBFS against ruby3.0 (Closes: #996511)

To make this package build with ruby3.0 we also need a rebuilt version
of ruby-nokogiri against ruby3.0.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996511

Bug#996918: marked as done (hunspell: FTBFS: format not a string literal and no format arguments)

[Debian Bug Tracking System]

Your message dated Wed, 20 Oct 2021 19:04:48 +
with message-id 
and subject line Bug#996918: fixed in hunspell 1.7.0-4
has caused the Debian Bug report #996918,
regarding hunspell: FTBFS: format not a string literal and no format arguments
to be marked as done.

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

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


-- 
996918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996918
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hunspell
Version: 1.7.0-3
Severity: serious
Tags: ftbfs bookworm sid patch

Your package FTBFS in unstable, here is the relevant part of my build
log:

,
| g++ -DHAVE_CONFIG_H -I. -I../..  -I../../src/hunspell -I../../src/hunspell 
-I../../src/parsers -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-ffile-prefix-map=/usr/local/src/deb-src/hunspell/hunspell=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o munch.o 
munch.cxx
| hunspell.cxx: In function 'char* scanline(char*)':
| hunspell.cxx:584:9: error: format not a string literal and no format 
arguments [-Werror=format-security]
|   584 |   printw(message);
|   |   ~~^
`

This happened because ncurses added format attributes to several
functions, and dpkg-buildpackage defaults to -Werror=format-security.
For details about the ncurses change, see #993179.

I have attached a simple patch which could be added to the series in
debian/patches, but there are also a few warnings which might be worth
looking at.

From 91148a568c5994768e660ca5a968df16ae4a146c Mon Sep 17 00:00:00 2001
From: Sven Joachim 
Date: Wed, 20 Oct 2021 19:40:36 +0200
Subject: [PATCH] Fix string format error with recent ncurses

---
 src/tools/hunspell.cxx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/tools/hunspell.cxx b/src/tools/hunspell.cxx
index 690e34a..b165634 100644
--- a/src/tools/hunspell.cxx
+++ b/src/tools/hunspell.cxx
@@ -581,7 +581,7 @@ const char* basename(const char* s, char c) {
 #ifdef HAVE_CURSES_H
 char* scanline(char* message) {
   char input[INPUTLEN];
-  printw(message);
+  printw("%s", message);
   echo();
   getnstr(input, INPUTLEN);
   noecho();
--
2.33.0

--- End Message ---
--- Begin Message ---
Source: hunspell
Source-Version: 1.7.0-4
Done: Rene Engelhard 

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

Debian distribution maintenance software
pp.
Rene Engelhard  (supplier of updated hunspell 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: Wed, 20 Oct 2021 20:36:34 +0200
Source: hunspell
Architecture: source
Version: 1.7.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian LibreOffice Maintainers 
Changed-By: Rene Engelhard 
Closes: 996918
Changes:
 hunspell (1.7.0-4) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Remove constraints unnecessary since stretch:
 + libhunspell-dev: Drop versioned constraint on hunspell in Replaces.
 + hunspell-tools: Drop versioned constraint on hunspell in Replaces.
 .
   [ Mattia Rizzolo ]
   * Remove constraints unnecessary since quite a long time:
 + libmyspell-dev: Drop Conflicts/Replaces.
   * Bump d/watch to version=4 and use subst.
 .
   [ Rene Engelhard ]
   * debian/patches/Fix-string-format-error-with-recent-ncurses.diff:
 add patch from Sven Joachim; as name says (closes: #996918)
Checksums-Sha1:
 af326f3fd9efd2bc05921461317fcd06e4d24774 2257 hunspell_1.7.0-4.dsc
 52c489b98b52155872b11e1fb4e41550a13f5279 21952 hunspell_1.7.0-4.debian.tar.xz
 249cb9b040107c055fcea2d14a5d5b0d38a13eb3 6389 hunspell_1.7.0-4_source.buildinfo
Checksums-Sha256:
 5ac1010098cc6b0fca45a7d6126f699ff1993b7b5ad994a0c70cd244be5b9e43 2257 
hunspell_1.7.0-4.dsc
 c3630663baf70c6d1e6ffb6fe2a4ec5cd4325b753a44036c8d1b78d7cd46adf5 21952 
hunspell_1.7.0-4.debian.tar.xz
 5c8d9128221a9df52cb6a02b35de5af3671c07554a5165b65e580b4aa87108d3 6389 
hunspell_1.7.0-4_source.buildinfo
Files:
 16491d975e4cb3725895b8e4e75db057 2257 text optional hunspell_1.7.0-4.dsc
 4cd35b56dd427cc998f968f522db50ee 21952 text optional 
hunspell_1.7.0-4.debian.tar.xz
 420073b0f0bef1564f5

Bug#996918: marked as pending in hunspell

[Rene Engelhard]

Control: tag -1 pending

Hello,

Bug #996918 in hunspell 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/libreoffice-team/hunspell/-/commit/f6740f6572e4320d3a9a5efd31e12392bdc1536f


debian/patches/Fix-string-format-error-with-recent-ncurses.diff: add patch from 
Sven Joachim; as name says (closes: #996918)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996918

Processed: Bug#996918 marked as pending in hunspell

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #996918 [src:hunspell] hunspell: FTBFS: format not a string literal and no 
format arguments
Added tag(s) pending.

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

Bug#996711: marked as done (src:cglm: fails to migrate to testing for too long: FTBFS on i386 and s390x)

[Debian Bug Tracking System]

Your message dated Wed, 20 Oct 2021 18:03:31 +
with message-id 
and subject line Bug#996711: fixed in cglm 0.8.4-3
has caused the Debian Bug report #996711,
regarding src:cglm: fails to migrate to testing for too long: FTBFS on i386 and 
s390x
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.)


-- 
996711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996711
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cglm
Version: 0.7.9-1
Severity: serious
Tags: sid bookworm ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days as having a Release Critical bug in
testing [1]. Your package src:cglm has been trying to migrate for 64
days [2]. Hence, I am filing this bug. The current version FTBFS on i386
and s390x.

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

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

I have tagged this bug to only affect sid and bookworm, so it doesn't
affect (old-)stable.

Paul

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




OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: cglm
Source-Version: 0.8.4-3
Done: Leon Marz 

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

Debian distribution maintenance software
pp.
Leon Marz  (supplier of updated cglm 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: Wed, 20 Oct 2021 15:49:00 +0200
Source: cglm
Architecture: source
Version: 0.8.4-3
Distribution: unstable
Urgency: medium
Maintainer: Leon Marz 
Changed-By: Leon Marz 
Closes: 996711
Changes:
 cglm (0.8.4-3) unstable; urgency=medium
 .
   * Improve clamp_rounding.patch (Closes: #996711)
Checksums-Sha1:
 d5ab62efa8135a4d4fe4adabdd417ae08654f58b 1807 cglm_0.8.4-3.dsc
 fdb9ef3c6ea51fbfa9936082c897ccf977c55236 5596 cglm_0.8.4-3.debian.tar.xz
 af3c773dc121a27519ec4cf2d7e853e3e7d3f98c 6921 cglm_0.8.4-3_source.buildinfo
Checksums-Sha256:
 0feb46d82caa7f99414d596752444de02e91825d86b70818f8718d298bc2b918 1807 
cglm_0.8.4-3.dsc
 d20726358b7f7fc94de0b918bb7f0a81c678a5ab1d7ba4c218664f06aef66415 5596 
cglm_0.8.4-3.debian.tar.xz
 948138e668428b31f5e4203045a5ebdb71db05bb612e35b66917dc9acf82a096 6921 
cglm_0.8.4-3_source.buildinfo
Files:
 60e35ca494608b066d390336410c2775 1807 libs optional cglm_0.8.4-3.dsc
 df2ed0026e3fe6039d239501a88dbfef 5596 libs optional cglm_0.8.4-3.debian.tar.xz
 d7a1023a9545558ff309ef8b23312826 6921 libs optional 
cglm_0.8.4-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmFwV7cACgkQH1x6i0VW
QxREbgv/VNnZ+7HXd3pjNr8UCeHqJFNYKGS0rjoTWMWfJjEMAzp0nO8qpRGulb+l
Xg9tx41ceCmV3gFwLsUulfY1yMofggEfTa7M+Rwb7PureKYt5e91wmokMIcIliWj
UAx/S+lAgSpdL6KqF4lO4jbhHjmKP+zMUnkQEzQR3d+QOydC8B+h5bo8um6NV/D4
w3FwPg7xI9u/ZemGxSEoMV3lzTV04Ua7siWbEZJEWO62MuAlJaeq4WJCTOE8DK6a
czQ+iGGFuWZK0bZc5XLxX+5/wBQR4P5mk2f7a40UJANJQ8lgH1fYZlz9wunwfqhC
ioxkg4m/EoHOoLPy3J6CL+K7cKO47PTy+kqYMd7js/OvDtuX+i1vwz9N/MVOvMKS
wCXmhiqGDPEhQDnK3cLCYRVyU3Qx+8goUEm7NhwbxY+8AXIXDZKIdqRZpvf0r+Fz
NNS59c4KnX+ZkWC950s1qZ4yPcYUw0cnDpr2CihPqzGEx6aB/S3EsCiPLtIRNqaa
QmrdRVSE
=+Bzs
-END PGP SIGNATURE End Message ---

Bug#996918: hunspell: FTBFS: format not a string literal and no format arguments

[Sven Joachim]

Source: hunspell
Version: 1.7.0-3
Severity: serious
Tags: ftbfs bookworm sid patch

Your package FTBFS in unstable, here is the relevant part of my build
log:

,
| g++ -DHAVE_CONFIG_H -I. -I../..  -I../../src/hunspell -I../../src/hunspell 
-I../../src/parsers -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-ffile-prefix-map=/usr/local/src/deb-src/hunspell/hunspell=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o munch.o 
munch.cxx
| hunspell.cxx: In function 'char* scanline(char*)':
| hunspell.cxx:584:9: error: format not a string literal and no format 
arguments [-Werror=format-security]
|   584 |   printw(message);
|   |   ~~^
`

This happened because ncurses added format attributes to several
functions, and dpkg-buildpackage defaults to -Werror=format-security.
For details about the ncurses change, see #993179.

I have attached a simple patch which could be added to the series in
debian/patches, but there are also a few warnings which might be worth
looking at.

From 91148a568c5994768e660ca5a968df16ae4a146c Mon Sep 17 00:00:00 2001
From: Sven Joachim 
Date: Wed, 20 Oct 2021 19:40:36 +0200
Subject: [PATCH] Fix string format error with recent ncurses

---
 src/tools/hunspell.cxx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/tools/hunspell.cxx b/src/tools/hunspell.cxx
index 690e34a..b165634 100644
--- a/src/tools/hunspell.cxx
+++ b/src/tools/hunspell.cxx
@@ -581,7 +581,7 @@ const char* basename(const char* s, char c) {
 #ifdef HAVE_CURSES_H
 char* scanline(char* message) {
   char input[INPUTLEN];
-  printw(message);
+  printw("%s", message);
   echo();
   getnstr(input, INPUTLEN);
   noecho();
--
2.33.0

Bug#984212: marked as done (libvcflib: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Wed, 20 Oct 2021 17:03:47 +
with message-id 
and subject line Bug#984139: fixed in libvcflib 1.0.2+dfsg-3
has caused the Debian Bug report #984139,
regarding libvcflib: ftbfs with GCC-11
to be marked as done.

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

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


-- 
984139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984139
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libvcflib
Version: 1.0.2+dfsg-2
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

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

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

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

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/libvcflib_1.0.2+dfsg-2_unstable_gcc11.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

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

[...]
/usr/include/c++/11/bits/stl_algo.h:3449:5: note:   template argument 
deduction/substitution failed:
In file included from /<>/src/BedReader.h:21,
 from /<>/src/vcf2dag.cpp:11:
/<>/intervaltree/IntervalTree.h:271:103: note:   candidate expects 
1 argument, 0 provided
  271 |  
std::numeric_limits::min() }};
  | 
  ^
In file included from /usr/include/c++/11/algorithm:62,
 from /usr/include/smithwaterman/SmithWatermanGotoh.h:4,
 from /<>/src/Variant.h:30,
 from /<>/src/vcf2dag.cpp:10:
/usr/include/c++/11/bits/stl_algo.h:3455:5: note: candidate: ‘template _Tp std::min(std::initializer_list<_Tp>, _Compare)’
 3455 | min(initializer_list<_Tp> __l, _Compare __comp)
  | ^~~
/usr/include/c++/11/bits/stl_algo.h:3455:5: note:   template argument 
deduction/substitution failed:
In file included from /<>/src/BedReader.h:21,
 from /<>/src/vcf2dag.cpp:11:
/<>/intervaltree/IntervalTree.h:271:103: note:   candidate expects 
2 arguments, 0 provided
  271 |  
std::numeric_limits::min() }};
  | 
  ^
[ 12%] Linking CXX executable vcfsample2info
/usr/bin/cmake -E cmake_link_script CMakeFiles/vcfsample2info.dir/link.txt 
--verbose=1
/usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -std=c++0x -D_FILE_OFFSET_BITS=64 -Isrc -O3 -fopenmp 
-Wl,-z,relro -Wl,-z,now -rdynamic 
CMakeFiles/vcfsample2info.dir/src/vcfsample2info.cpp.o -o vcfsample2info  
-Wl,-rpath,/<>/obj-x86_64-linux-gnu: libvcflib.so.1 -ltabixpp 
-DGIT_VERSION=0.9.0 -lhts -lpthread -lz -llzma -lbz2 -lsmithwaterman -ldisorder 
-lfastahack -lssw -ltabixpp 
/<>/intervaltree/IntervalTree.h: In instantiation of 
‘std::pair > IntervalTree::is_valid() const [with Scalar = long unsigned int; Value = BedTarget*]’:
/<>/intervaltree/IntervalTree.h:115:13:   required from 
‘IntervalTree::IntervalTree(IntervalTree::interval_vector&&, std::size_t, std::size_t, std::size_t, Scalar, 
Scalar) [with Scalar = long unsigned int; Value = BedTarget*; 
IntervalTree::interval_vector = std::vector >; std::size_t = long unsigned int]’
/<>/src/BedReader.h:163:118:   required from here
/<>/intervaltree/In

Bug#984139: marked as done (freebayes: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Wed, 20 Oct 2021 17:03:47 +
with message-id 
and subject line Bug#984139: fixed in libvcflib 1.0.2+dfsg-3
has caused the Debian Bug report #984139,
regarding freebayes: ftbfs with GCC-11
to be marked as done.

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

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


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

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

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

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

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/freebayes_1.3.5-1_unstable_gcc11.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

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

[...]
/usr/include/vcflib/../intervaltree/IntervalTree.h:250:85: error: ‘::min’ has 
not been declared; did you mean ‘std::min’?
  250 |
std::numeric_limits::min() };
  | 
^~~
  | 
std::min
In file included from /usr/include/c++/11/algorithm:62,
 from ../src/AlleleParser.h:11,
 from ../src/AlleleParser.cpp:1:
/usr/include/c++/11/bits/stl_algo.h:3455:5: note: ‘std::min’ declared here
 3455 | min(initializer_list<_Tp> __l, _Compare __comp)
  | ^~~
In file included from ../src/BedReader.h:12,
 from ../src/AlleleParser.h:20,
 from ../src/AlleleParser.cpp:1:
/usr/include/vcflib/../intervaltree/IntervalTree.h: In member function 
‘std::pair > IntervalTree::is_valid() const’:
/usr/include/vcflib/../intervaltree/IntervalTree.h:270:75: error: 
‘numeric_limits’ is not a member of ‘std’
  270 | std::pair> result = {true, { 
std::numeric_limits::max(),
  | 
  ^~
/usr/include/vcflib/../intervaltree/IntervalTree.h:270:96: error: expected 
primary-expression before ‘>’ token
  270 | std::pair> result = {true, { 
std::numeric_limits::max(),
  | 
   ^
/usr/include/vcflib/../intervaltree/IntervalTree.h:270:99: error: ‘::max’ has 
not been declared; did you mean ‘std::max’?
  270 | std::pair> result = {true, { 
std::numeric_limits::max(),
  | 
  ^~~
  | 
  std::max
In file included from /usr/include/c++/11/algorithm:62,
 from ../src/AlleleParser.h:11,
 from ../src/AlleleParser.cpp:1:
/usr/include/c++/11/bits/stl_algo.h:3467:5: note: ‘std::max’ declared here
 3467 | max(initializer_list<_Tp> __l, _Compare __comp)
  | ^~~
In file included from ../src/BedReader.h:12,
 from ../src/AlleleParser.h:20,
 from ../src/AlleleParser.cpp:1:
/usr/include/vcflib/../intervaltree/IntervalTree.h:271:75: error: 
‘numeric_limits’ is not a member of ‘std’
  271 | 

Processed: Re: lamarc: ftbfs with GCC-11

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #984080 [src:lamarc] lamarc: ftbfs with GCC-11
Added tag(s) help.

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

Bug#984080: lamarc: ftbfs with GCC-11

[Andreas Tille]

Control: tags -1 help

Hi,

I was able to fix part of the compatibility issues[1] but now the build
stumbles upon:

...
g++ -DHAVE_CONFIG_H -I. -I./config   -Wdate-time -D_FORTIFY_SOURCE=2 
-DLAMARC_COMPILE_LINUX  -DNDEBUG  -Wall -Wextra -Wno-unused -I 
./config -I ./config -I ./src/bayeslike - I ./src/control -I ./src/conversion 
-I ./src/convErr -I ./src/convModel -I ./src/convParse -I ./src/convStrings -I 
./src/convUtil -I ./src/datalike -I ./src/force -I ./src/guiconv -I ./ 
src/guiutil -I ./src/lamarcmenus -I ./src/menu -I ./src/postlike -I 
./src/report -I ./src/tools -I ./src/tree -I ./src/ui_interface -I 
./src/ui_util -I ./src/ui_vars -I ./src/xml -I/usr/include/boost -I ./resources 
-DTIXML_USE_STL -g -O2 -ffile-prefix-map=/build/lamarc-2.1.10.1+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
src/datalike/lamarc-  phenotypes.o `test -f 'src/datalike/phenotypes.cpp' || 
echo './'`src/datalike/phenotypes.cpp
In file included from /usr/include/c++/11/set:60,
 from ./src/tools/rangex.h:26,
 from src/datalike/dlcalc.h:31,
 from src/datalike/locus.cpp:29:
/usr/include/c++/11/bits/stl_tree.h: In instantiation of 'static const _Key& 
std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, 
_Alloc>::_S_key(std::_Rb_tree<_Key, _Val, _KeyOfValue,  _Compare, 
_Alloc>::_Const_Link_type) [with _Key = std::pair; _Val = 
std::pair; _KeyOfValue = std::_Identity >;  _Compare = rangecmp; _Alloc = std::allocator >; std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, 
_Alloc>::_Const_Link_type = const std::_Rb_tree_node >*]':
/usr/include/c++/11/bits/stl_tree.h:2069:47:   required from 
'std::pair 
std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, _Alloc>::
_M_get_insert_unique_pos(const key_type&) [with _Key = std::pair; _Val = std::pair; _KeyOfValue = 
std::_Identity >; _Compare = rangecmp; _Alloc = 
std::allocator >; std::_Rb_tree<_Key, _Val, 
_KeyOfValue, _Compare, _Alloc>::key_type = std::pair]'
/usr/include/c++/11/bits/stl_tree.h:2122:4:   required from 
'std::pair, bool> std::_Rb_tree<_Key, _Val, 
_KeyOfValue, _Compare, _Alloc>:: _M_insert_unique(_Arg&&) 
[with _Arg = std::pair; _Key = std::pair; _Val = std::pair; _KeyOfValue = std::_Identity >; _Compare = rangecmp; _Alloc = 
std::allocator >]'
/usr/include/c++/11/bits/stl_set.h:521:25:   required from 'std::pair, _Compare, typename 
__gnu_cxx::__alloc_traits<_Allocator>::  rebind<_Key>::other>::const_iterator, 
bool> std::set<_Key, _Compare, _Alloc>::insert(std::set<_Key, _Compare, 
_Alloc>::value_type&&) [with _Key = std::pair; _Compare = 
rangecmp; _Alloc = std::allocator >; typename 
std::_Rb_tree<_Key, _Key, std::_Identity<_Tp>, _Compare, typename 
__gnu_cxx::__alloc_traits<_Allocator>::   rebind<_Key>::other>::const_iterator 
= std::_Rb_tree, std::pair, 
std::_Identity >, rangecmp, std::
allocator > >::const_iterator; typename 
__gnu_cxx::__alloc_traits<_Allocator>::rebind<_Key>::other = 
std::allocator >;typename 
__gnu_cxx::__alloc_traits<_Allocator>::rebind<_Key> = 
__gnu_cxx::__alloc_traits >, 
std::pair >::rebind >; 
typename _Allocator::value_type = std::pair; std::set<_Key, 
_Compare, _Alloc>::value_type = std::pair]'
src/datalike/locus.cpp:204:24:   required from here
/usr/include/c++/11/bits/stl_tree.h:770:15: error: static assertion failed: 
comparison object must be invocable as const
  770 | In file included from /usr/include/c++/11/set:60,
 from ./src/tools/rangex.h:26,
 from src/datalike/dlcalc.h:31,
/usr/include/c++/11/bits/stl_tree.h:770:15: note: 'std::is_invocable_v&, const std::pair&>' evaluates to false
make[1]: *** [Makefile:7499: src/datalike/lamarc-locus.o] Error 1


Any help is welcome

  Andreas.

[1] 
https://salsa.debian.org/med-team/lamarc/-/blob/master/debian/patches/throw_noexcept.patch

-- 
http://fam-tille.de

Bug#984106: marked as done (libgenome: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Wed, 20 Oct 2021 16:04:57 +
with message-id 
and subject line Bug#984106: fixed in libgenome 1.3.11+svn20110227.4616-4
has caused the Debian Bug report #984106,
regarding libgenome: ftbfs with GCC-11
to be marked as done.

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

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


-- 
984106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984106
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libgenome
Version: 1.3.11+svn20110227.4616-3
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

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

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

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

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/libgenome_1.3.11+svn20110227.4616-3_unstable_gcc11.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

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

[...]
 /bin/mkdir -p '/<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
 /usr/bin/install -c -m 644 libGenome.pc 
'/<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
make[3]: Leaving directory '/<>'
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
dh_install
# Call d-shlibmove to comply with library packaging guide
# mv debian/tmp/usr/include/*/* debian/tmp/usr/include/
d-shlibmove --commit \
--multiarch \
--devunversioned \
--exclude-la \
--movedev debian/tmp/usr/include/* usr/include \
--movedev "debian/tmp/usr/lib/*/pkgconfig/*.pc" 
usr/lib/x86_64-linux-gnu/pkgconfig \
debian/tmp/usr/lib/*/*.so
Library package automatic movement utility
set -e
install -d -m 755 debian/libgenome-dev/usr/lib/x86_64-linux-gnu
install -d -m 755 debian/libgenome0/usr/lib/x86_64-linux-gnu
mv debian/tmp/usr/lib/x86_64-linux-gnu/libGenome.a 
debian/libgenome-dev/usr/lib/x86_64-linux-gnu
mv debian/tmp/usr/lib/x86_64-linux-gnu/libGenome.so 
debian/libgenome-dev/usr/lib/x86_64-linux-gnu
mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libGenome.so.0 
debian/libgenome0/usr/lib/x86_64-linux-gnu
mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libGenome.so.0.1.3 
debian/libgenome0/usr/lib/x86_64-linux-gnu
PKGDEV=libgenome-dev
PKGSHL=libgenome0
install -d -m 755 debian/libgenome-dev/usr/include
mv debian/tmp/usr/include/libGenome debian/libgenome-dev/usr/include
install -d -m 755 debian/libgenome-dev/usr/lib/x86_64-linux-gnu/pkgconfig
mv debian/tmp/usr/lib/*/pkgconfig/*.pc 
debian/libgenome-dev/usr/lib/x86_64-linux-gnu/pkgconfig
find debian -name libGenome.la -delete
make[1]: Leaving directory '/<>'
   dh_installdocs
   dh_installchangelogs
   dh_perl
   dh_link
   dh_strip_nondeterminism
   dh_compress
   dh_fixperms
   dh_missing
   dh_dwz -a
   dh_strip -a
   dh_makeshlibs -a
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libgenome0/DEBIAN/symbols doesn't match 
completely debian/libgenome0.symbols.amd64
--- debian/libgenome0.symbols.amd64 (libgenome0_1.3.11+svn20110227.4616-3_amd64)
+++ dpkg-gensymbolstp7952   2021-03-01 21:07:22.362888236 +
@@ -630,7 +630,7 @@
  
_ZNSt6vectorIN6genome10gnLocationESaIS1_EE6insertEN9__gnu_cxx17__normal_iteratorIPKS1_S3_EERS6_@Base
 1.3.11+svn20110227.4616

Processed: gnome-pass-search-provider: diff for NMU version 0.0~20191115+da2db41-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 996714 + patch
Bug #996714 [src:gnome-pass-search-provider] gnome-pass-search-provider: fails 
to migrate to testing for too long
Added tag(s) patch.
> tags 996714 + pending
Bug #996714 [src:gnome-pass-search-provider] gnome-pass-search-provider: fails 
to migrate to testing for too long
Added tag(s) pending.

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

Bug#996714: gnome-pass-search-provider: diff for NMU version 0.0~20191115+da2db41-1.1

[Boyuan Yang]

Control: tags 996714 + patch
Control: tags 996714 + pending

Dear maintainer,

I've prepared an NMU for gnome-pass-search-provider (versioned as
0.0~20191115+da2db41-1.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru gnome-pass-search-provider-0.0~20191115+da2db41/debian/changelog
gnome-pass-search-provider-0.0~20191115+da2db41/debian/changelog
--- gnome-pass-search-provider-0.0~20191115+da2db41/debian/changelog2020-
03-20 14:46:32.0 -0400
+++ gnome-pass-search-provider-0.0~20191115+da2db41/debian/changelog2021-
10-20 11:45:31.0 -0400
@@ -1,3 +1,10 @@
+gnome-pass-search-provider (0.0~20191115+da2db41-1.1) unstable;
urgency=medium
+
+  * Non-maintainer upload.
+  * No change source-only upload. (Closes: #996714)
+
+ -- Boyuan Yang   Wed, 20 Oct 2021 11:45:31 -0400
+
 gnome-pass-search-provider (0.0~20191115+da2db41-1) unstable; urgency=medium
 
   * Initial release (Closes: #954347)


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

Processed: limit source to cmark, tagging 996887

[Debian Bug Tracking System]

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

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

> tags 996887 + pending
Bug #996887 [libcmark0.30.1] libcmark0.30.1: 0.30.2 bumps SONAME without 
changing package name
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#996906: klibc FTBFS on armhf: cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU

[Helmut Grohne]

Source: klibc
Version: 2.0.8-6.1
Severity: serious
Tags: ftbfs

klibc fails to build from source in unstable on armhf. I suppose this is
fallout from gcc-11.

Reproduced by reproducible builds:
https://tests.reproducible-builds.org/debian/rbuild/unstable/armhf/klibc_2.0.8-6.1.rbuild.log.gz
| /usr/bin/make all INSTALLROOT=debian/tmp ARCH=arm CONFIG_AEABI=y 
CPU_ARCH=armv7-a CPU_TUNE=cortex-a8 CONFIG_KLIBC_THUMB=y KBUILD_VERBOSE=1 
CONFIG_DEBUG_INFO=y
| make[2]: Entering directory '/build/1st/klibc-2.0.8'
| /usr/bin/make -f /build/1st/klibc-2.0.8/scripts/Kbuild.klibc obj=klcc
| rm -f klcc/klibc.config
| echo 'ARCH=arm' >> klcc/klibc.config
| echo 'ARCHDIR=arm' >> klcc/klibc.config
| echo 'CROSS=' >> klcc/klibc.config
| echo 'KCROSS=' >> klcc/klibc.config
| echo 'CC=gcc' >> klcc/klibc.config
| echo 'LD=ld' >> klcc/klibc.config
| echo 'REQFLAGS=-D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=32 
-fno-stack-protector -fwrapv -fno-PIE -fno-builtin-bcmp -fcommon -ggdb 
-fno-exceptions -mthumb -mabi=aapcs-linux -nostdinc -iwithprefix include 
-D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=32' >> klcc/klibc.config
| echo 'OPTFLAGS=-Os -march=armv7-a -mtune=cortex-a8' >> klcc/klibc.config
| echo 'LDFLAGS=--thumb-entry _start --build-id=sha1' >> klcc/klibc.config
| echo 'STRIP=strip' >> klcc/klibc.config
| echo 'STRIPFLAGS=-R .ARM.exidx --strip-all -R .comment -R .note' >> 
klcc/klibc.config
| echo 'EMAIN=--thumb-entry main' >> klcc/klibc.config
| echo 'BITSIZE=32' >> klcc/klibc.config
| echo 'VERSION=2.0.8' >> klcc/klibc.config
| echo 'prefix=/usr/lib/klibc' >> klcc/klibc.config
| echo 'bindir=/usr/lib/klibc/bin' >> klcc/klibc.config
| echo 'libdir=/usr/lib/klibc/lib' >> klcc/klibc.config
| echo 'includedir=/usr/lib/klibc/include' >> klcc/klibc.config
|   perl klcc/makeklcc.pl /build/1st/klibc-2.0.8/klcc/klcc.in klcc/klibc.config 
/usr/bin/perl > klcc/klcc || ( rm -f klcc/klcc ; exit 1 ) && chmod a+x klcc/klcc
| :
| /usr/bin/make -f /build/1st/klibc-2.0.8/scripts/Kbuild.klibc obj=.
| /usr/bin/make -rR -f /build/1st/klibc-2.0.8/scripts/Kbuild.klibc 
obj=scripts/basic
|   gcc -Wp,-MD,scripts/basic/.fixdep.d -Wall -Wstrict-prototypes -O2 
-fomit-frame-pointer   -o scripts/basic/fixdep scripts/basic/fixdep.c
| :
| /usr/bin/make -rR -f /build/1st/klibc-2.0.8/scripts/Kbuild.klibc obj=usr/klibc
|   gcc -Wp,-MD,usr/klibc/.__static_init.o.d  -nostdinc -iwithprefix include 
-I/build/1st/klibc-2.0.8/usr/include/arch/arm -Iusr/include/arch/arm 
-I/build/1st/klibc-2.0.8/usr/include/bits32 -Iusr/include/bits32 
-I/build/1st/klibc-2.0.8/usr/klibc/../include -Iusr/klibc/../include 
-I/build/1st/klibc-2.0.8/usr/include -Iusr/include 
-I/build/1st/klibc-2.0.8/linux/include -Ilinux/include -D__KLIBC__=2 
-D__KLIBC_MINOR__=0 -D_BITSIZE=32 -fno-stack-protector -fwrapv -fno-PIE 
-fno-builtin-bcmp -fcommon -ggdb -fno-exceptions -mthumb -mabi=aapcs-linux -Os 
-march=armv7-a -mtune=cortex-a8 -W -Wall -Wno-sign-compare 
-Wno-unused-parameter -c -o usr/klibc/__static_init.o usr/klibc/__static_init.c
| cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU
| make[4]: *** [/build/1st/klibc-2.0.8/scripts/Kbuild.klibc:261: 
usr/klibc/__static_init.o] Error 1
| make[3]: *** [/build/1st/klibc-2.0.8/./Kbuild:9: all] Error 2
| make[2]: *** [Makefile:121: klibc] Error 2
| make[2]: Leaving directory '/build/1st/klibc-2.0.8'
| make[1]: *** [debian/rules:51: override_dh_auto_build] Error 2
| make[1]: Leaving directory '/build/1st/klibc-2.0.8'
| make: *** [debian/rules:45: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Also seen by crossqa:
http://crossqa.debian.net/build/klibc_2.0.8-6.1_armhf_20211019164552.log

Helmut

Bug#996905: pms FTBFS: error: format not a string literal and no format arguments [-Werror=format-security]

[Helmut Grohne]

Source: pms
Version: 0.42-1
Severity: serious
Tags: ftbfs

pms fails to build from source, because ncurses added format string
annotations. A non-parallel build in unstable now ends as follows:

| g++ -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-DLOCALE_DIR=\""/usr/share/locale"\" -c -o display.o `test -f 'src/display.cpp' 
|| echo './'`src/display.cpp
| src/display.cpp: In function ‘void colprint(pms_window*, int, int, color*, 
const char*, ...)’:
| src/display.cpp:1703:40: error: format not a string literal and no format 
arguments [-Werror=format-security]
|  1703 | wprintw(w->h(), _(output.c_str()));
|   | ~~~^~~
| In file included from src/pms.h:46,
|  from src/display.cpp:26:
| src/display.cpp:1737:59: error: format not a string literal and no format 
arguments [-Werror=format-security]
|  1737 | wprintw(w->h(), _(buf));
|   |   ^~~
| src/i18n.h:31:22: note: in definition of macro ‘_’
|31 | #define _(x) gettext(x)
|   |  ^
| src/display.cpp:1745:59: error: format not a string literal and no format 
arguments [-Werror=format-security]
|  1745 | wprintw(w->h(), _(buf));
|   |   ^~~
| src/i18n.h:31:22: note: in definition of macro ‘_’
|31 | #define _(x) gettext(x)
|   |  ^
| src/display.cpp:1756:59: error: format not a string literal and no format 
arguments [-Werror=format-security]
|  1756 | wprintw(w->h(), _(buf));
|   |   ^~~
| src/i18n.h:31:22: note: in definition of macro ‘_’
|31 | #define _(x) gettext(x)
|   |  ^
| src/display.cpp:1790:32: error: format not a string literal and no format 
arguments [-Werror=format-security]
|  1790 | wprintw(w->h(), _(output.c_str()));
|   | ~~~^~~
| cc1plus: some warnings being treated as errors
| make[2]: *** [Makefile:470: display.o] Error 1
| make[2]: Leaving directory '/<>'
| make[1]: *** [Makefile:235: all] Error 2
| make[1]: Leaving directory '/<>'
| dh_auto_build: error: make -j1 returned exit code 2
| make: *** [debian/rules:4: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Helmut

Bug#994864: marked as done (nlohmann-json3: autopkgtest regression)

[Debian Bug Tracking System]

Your message dated Wed, 20 Oct 2021 14:53:41 +
with message-id 
and subject line Bug#994864: fixed in nlohmann-json3 3.10.4-1
has caused the Debian Bug report #994864,
regarding nlohmann-json3: autopkgtest regression
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.)


-- 
994864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994864
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nlohmann-json3
Version: 3.10.2-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

nlohmann-json3 is unable to migrate to testing due to failing
autopkgtests:
| autopkgtest [23:37:19]: test cmake-test:  - - - - - - - - - - results - - - - 
- - - - - -
| cmake-test   FAIL stderr: In file included from 
/tmp/autopkgtest-lxc.3j1h556o/downtmp/autopkgtest_tmp/test/thirdparty/doctest/doctest_compatibility.h:6,
| autopkgtest [23:37:20]: test cmake-test:  - - - - - - - - - - stderr - - - - 
- - - - - -
| In file included from 
/tmp/autopkgtest-lxc.3j1h556o/downtmp/autopkgtest_tmp/test/thirdparty/doctest/doctest_compatibility.h:6,
|  from 
/tmp/autopkgtest-lxc.3j1h556o/downtmp/autopkgtest_tmp/test/src/unit-items.cpp:30:
| 
/tmp/autopkgtest-lxc.3j1h556o/downtmp/autopkgtest_tmp/test/thirdparty/doctest/doctest.h:110:34:
 warning: unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|   110 | #define DOCTEST_PRAGMA_TO_STR(x) _Pragma(#x)
|   |  ^~~
| 
/tmp/autopkgtest-lxc.3j1h556o/downtmp/autopkgtest_tmp/test/thirdparty/doctest/doctest.h:112:41:
 note: in expansion of macro ‘DOCTEST_PRAGMA_TO_STR’
|   112 | #define DOCTEST_GCC_SUPPRESS_WARNING(w) DOCTEST_PRAGMA_TO_STR(GCC 
diagnostic ignored w)
|   | ^
| 
/tmp/autopkgtest-lxc.3j1h556o/downtmp/autopkgtest_tmp/test/src/unit-items.cpp:44:1:
 note: in expansion of macro ‘DOCTEST_GCC_SUPPRESS_WARNING’
|44 | DOCTEST_GCC_SUPPRESS_WARNING("-Wrange-loop-construct")
|   | ^~~~
| autopkgtest [23:37:20]:  summary
| cmake-test   FAIL stderr: In file included from 
/tmp/autopkgtest-lxc.3j1h556o/downtmp/autopkgtest_tmp/test/thirdparty/doctest/doctest_compatibility.h:6,

https://ci.debian.net/data/autopkgtest/testing/amd64/n/nlohmann-json3/15439612/log.gz

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: nlohmann-json3
Source-Version: 3.10.4-1
Done: Gianfranco Costamagna 

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated 
nlohmann-json3 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: Wed, 20 Oct 2021 16:38:01 +0200
Source: nlohmann-json3
Architecture: source
Version: 3.10.4-1
Distribution: unstable
Urgency: medium
Maintainer: Hubert Chathi 
Changed-By: Gianfranco Costamagna 
Closes: 994864
Changes:
 nlohmann-json3 (3.10.4-1) unstable; urgency=medium
 .
   * New upstream version 3.10.4
   * Bump std-version to 4.6.0
   * Allow-stderror for new doctest deprecation warning (Closes: #994864)
Checksums-Sha1:
 3dcd1a7278466523ddb243b63ace28878c3aeb65 2061 nlohmann-json3_3.10.4-1.dsc
 2ffa3306bff9c739b5823b76dda05186ac8d046a 7062443 
nlohmann-json3_3.10.4.orig.tar.gz
 c9388ca9a1c01dde6922e051430134ed9aa1e720 4980 
nlohmann-json3_3.10.4-1.debian.tar.xz
 e28368c7d76bfd9e4987e721c867e67636f64c11 11759 
nlohmann-json3_3.10.4-1_source.buildinfo
Checksums-Sha256:
 928725e5761224867aa53660ec6d439f96689f1f6ff5357d01d5c89c81a07e8f 2061 
nlohmann-json3_3.10.4-1.dsc
 1155fd1a83049767360e9a120c43c578145db3204d2b309eba49fbbedd0f4ed3 7062443 
nlohmann-json3_3.10.4.orig.tar.gz
 ad4353f484a718bd1cc93272b016608bd48fc0390ba07208f95c08298ff6a4fb 4980 
nlohmann-json3_3.10.4-1.debian.tar.xz
 98f454de99d817951332bfe7535db315dd2b313cd68d9fc6b27f8897e924ffdf 11759 
nlohmann-json3_3.10.4-1_source.buildinfo
Files:
 e331aa911ac7ef25220e2a73d51082da 2061 libs optional nlohmann-json3_3.10.4-1.dsc
 d1de947a7fe0030ce

Processed: update severity

[Debian Bug Tracking System]

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

> package nheko
Limiting to bugs with field 'package' containing at least one of 'nheko'
Limit currently set to 'package':'nheko'

> severity 981525 important
Bug #981525 {Done: Hubert Chathi } [nheko] nheko login 
crashes client, can't be used, in urgent need of a version update
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Processed: :(

[Debian Bug Tracking System]

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

> reopen 996711
Bug #996711 {Done: Leon Marz } [src:cglm] src:cglm: fails to 
migrate to testing for too long: FTBFS on i386 and s390x
'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 cglm/0.8.4-2.
> thanks
Stopping processing here.

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

Bug#996064: marked as done (gnome-shell-extension-impatience: does not declare compatibility with GNOME Shell 41)

[Debian Bug Tracking System]

Your message dated Wed, 20 Oct 2021 13:34:20 +
with message-id 
and subject line Bug#996064: fixed in gnome-shell-extension-impatience 
0.4.5+git20210930-db933e8-1
has caused the Debian Bug report #996064,
regarding gnome-shell-extension-impatience: does not declare compatibility with 
GNOME Shell 41
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.)


-- 
996064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996064
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-impatience
Version: 0.4.5+git20210412-e8e132f-1
Severity: normal
Tags: bookworm sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-41

The metadata.json for this extension doesn't declare compatibility with
GNOME 41. I don't know whether the actual code will need changes or not:
the conservative assumption is that it probably will (so please test).
gnome-shell 41 should be available in experimental soon.

In versions of GNOME Shell up to 3.38, metadata.json didn't matter much,
because validation of extensions' metadata against the installed Shell
version was disabled by default; but since GNOME 40 the default has changed
back to enabling the version check by default, in an effort to avoid
issues caused by outdated extensions remaining enabled. As a result,
GNOME Shell extensions in bookworm should probably have a dependency like:

Depends: gnome-shell (>= x), gnome-shell (<< y~)

where x and y are set according to metadata.json.
gnome-shell-extension-caffeine is a good example of this technique.

When we do the GNOME Shell 41 transition, hopefully soon, we will have
to either update this extension or remove it from testing. It would be
useful to get a fixed version into experimental.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-impatience
Source-Version: 0.4.5+git20210930-db933e8-1
Done: Jonathan Carter 

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

Debian distribution maintenance software
pp.
Jonathan Carter  (supplier of updated 
gnome-shell-extension-impatience 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: Wed, 20 Oct 2021 14:52:55 +0200
Source: gnome-shell-extension-impatience
Architecture: source
Version: 0.4.5+git20210930-db933e8-1
Distribution: unstable
Urgency: medium
Maintainer: Jonathan Carter 
Changed-By: Jonathan Carter 
Closes: 996064
Changes:
 gnome-shell-extension-impatience (0.4.5+git20210930-db933e8-1) unstable; 
urgency=medium
 .
   * New upstream snapshot (Closes: #996064)
   * Fix incorrect standards version (Set to 4.6.0)
Checksums-Sha1:
 a39902a2f11d558c8a14924c086ddb033f281f35 2316 
gnome-shell-extension-impatience_0.4.5+git20210930-db933e8-1.dsc
 e45a61e7f861da92822e9ea9ae853bc0675c0368 4379 
gnome-shell-extension-impatience_0.4.5+git20210930-db933e8.orig.tar.gz
 0afa95191d69bd8eaccb88b7db58aaf66763576b 2392 
gnome-shell-extension-impatience_0.4.5+git20210930-db933e8-1.debian.tar.xz
 b8e286519ab30a2fc39249823e025d8079c13c89 5973 
gnome-shell-extension-impatience_0.4.5+git20210930-db933e8-1_source.buildinfo
Checksums-Sha256:
 510f5c25fa45ad5498cf1aa4aaa33b3b90a25bf4853539b4e6980af7d6fb3aa9 2316 
gnome-shell-extension-impatience_0.4.5+git20210930-db933e8-1.dsc
 16c0026533d7c9378a133b2ef96e23d42ce123414a762fc263dd8d9d1e3985e4 4379 
gnome-shell-extension-impatience_0.4.5+git20210930-db933e8.orig.tar.gz
 0181b6025318b5d30dc44e86e14f10e327eabaaaf432fe6a37df6b6a12b1a8c4 2392 
gnome-shell-extension-impatience_0.4.5+git20210930-db933e8-1.debian.tar.xz
 84441f9df0e3e1cb6514c84e8fae2574834e7abd222a306bc82c4c6b2befc161 5973 
gnome-shell-extension-impatience_0.4.5+git20210930-db933e8-1_source.buildinfo
Files:
 37ccfa8d7c5cf40ca2ad1475a1fcf7c8 2316 gnome optional 
gnome-shell-extension-impatience_0.4.5+git20210930-db933e8-1.dsc
 e55cb0c09fb6d58137401a2f0e7767e5 4379 gnome optional 
gnome-shell-extension-impatience_0.4.5+git20210930-db933e8.orig.tar.gz
 e9a9770d58ae326646befb04d9dedae8 2392 gnome optio

Processed: closing 984097

[Debian Bug Tracking System]

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

> close 984097 1.0.16-1
Bug #984097 [src:libdfp] libdfp: ftbfs with GCC-11
Marked as fixed in versions libdfp/1.0.16-1.
Bug #984097 [src:libdfp] libdfp: ftbfs with GCC-11
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#984097: closing 984097

[Frédéric Bonnard]

close 984097 1.0.16-1
thanks

Bug#996711: marked as done (src:cglm: fails to migrate to testing for too long: FTBFS on i386 and s390x)

[Debian Bug Tracking System]

Your message dated Wed, 20 Oct 2021 12:48:43 +
with message-id 
and subject line Bug#996711: fixed in cglm 0.8.4-2
has caused the Debian Bug report #996711,
regarding src:cglm: fails to migrate to testing for too long: FTBFS on i386 and 
s390x
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.)


-- 
996711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996711
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cglm
Version: 0.7.9-1
Severity: serious
Tags: sid bookworm ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days as having a Release Critical bug in
testing [1]. Your package src:cglm has been trying to migrate for 64
days [2]. Hence, I am filing this bug. The current version FTBFS on i386
and s390x.

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

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

I have tagged this bug to only affect sid and bookworm, so it doesn't
affect (old-)stable.

Paul

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




OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: cglm
Source-Version: 0.8.4-2
Done: Leon Marz 

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

Debian distribution maintenance software
pp.
Leon Marz  (supplier of updated cglm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 19 Oct 2021 11:19:00 +0200
Source: cglm
Architecture: source
Version: 0.8.4-2
Distribution: unstable
Urgency: medium
Maintainer: Leon Marz 
Changed-By: Leon Marz 
Closes: 996711
Changes:
 cglm (0.8.4-2) unstable; urgency=medium
 .
   * Add clamp_rounding.patch (Closes: #996711)
Checksums-Sha1:
 9fed718bad69bd6ad63eb81307d399fd38420b16 1981 cglm_0.8.4-2.dsc
 084e53540a17aa7e41a0bd0146006f792d80f02d 5476 cglm_0.8.4-2.debian.tar.xz
Checksums-Sha256:
 31a914f781a76d9d25572514c0f9461134eda3140e61800c4b6b2203704b3a88 1981 
cglm_0.8.4-2.dsc
 85bc7734c398f08f0264e95c1d585dffecd8be95074f50857152b9f35f82e33c 5476 
cglm_0.8.4-2.debian.tar.xz
Files:
 df21568bfedaaef070c08d8a6fdf35db 1981 libs optional cglm_0.8.4-2.dsc
 1222698ea6e93c616d68d81ba26ce272 5476 libs optional cglm_0.8.4-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZaEt9P4xrWusTXauM1X01jtYIcwFAmFwDsQACgkQM1X01jtY
Icy8Bg/8D0IPHiMDYaWFtEo3DeJrzypikNOcIhYnwblpu3/T6bdxYY8vNY/3MRih
vBDVUGV0ODp0gUWz4bz3afchhtviclu/876lUoaV0f4lH6M4NU+vs4oVqYyRonMh
TnCKdBFQPVBlSaHl7jm370+v8POIWGb0SdAyKX5C3/Nu4RVCpnQC2gTxTl7vBim6
xbMKnoPR9xruhIoYpa8nS1GHpEDDdvDO344zAlVquYUzH81jEX6sXE/amPAkUl0v
OgqEUlV/PxGdl7kuj0RGGSw3YfCbhEb/kOZC47l0BCkHk8DayKrfJZvU0Rmss6fD
D/xcrQ1Rk8RFKgt1g8MSyeUhPUA/09NOy9o3GppUpht4V6K7+vrWN4fBjPudZx4E
72VzJSQZ/4tDMnsLE3vndgO7pvM0A2NZ4PqTMa2wnhak8wZ/ChU654Tv+nZNICPd
5kEsrDKC10EGJhBXwpK56LLnGhA/xb5pTgzgC7Hytl8D/UObmu1UrHw7HR1rT7xG
yNI84WDfsspEvEleOk7yp31cww26ToJH+2QSA/49hFod+bimnMMpuFVVz4TinYCA
zwEBv9Fk1xRSB5paOUv3PP52GxtuFoGa9zi9jjpHQvgwQgwae4zhg72oMTonRron
duJ+Cpll2XzdtamK/0mlCtJCqVFm0jBv13vW/PXP6OWVTMFhS0w=
=0atb
-END PGP SIGNATURE End Message ---

Bug#996045: marked as done (gnome-shell-extension-arc-menu: does not declare compatibility with GNOME Shell 41)

[Debian Bug Tracking System]

Your message dated Wed, 20 Oct 2021 12:34:00 +
with message-id 
and subject line Bug#996045: fixed in gnome-shell-extension-arc-menu 
49+forkv18-1
has caused the Debian Bug report #996045,
regarding gnome-shell-extension-arc-menu: does not declare compatibility with 
GNOME Shell 41
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.)


-- 
996045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996045
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-arc-menu
Version: 49-1
Severity: normal
Tags: bookworm sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-41

The metadata.json for this extension doesn't declare compatibility with
GNOME 41. I don't know whether the actual code will need changes or not:
the conservative assumption is that it probably will (so please test).
gnome-shell 41 should be available in experimental soon.

In versions of GNOME Shell up to 3.38, metadata.json didn't matter much,
because validation of extensions' metadata against the installed Shell
version was disabled by default; but since GNOME 40 the default has changed
back to enabling the version check by default, in an effort to avoid
issues caused by outdated extensions remaining enabled. As a result,
GNOME Shell extensions in bookworm should probably have a dependency like:

Depends: gnome-shell (>= x), gnome-shell (<< y~)

where x and y are set according to metadata.json.
gnome-shell-extension-caffeine is a good example of this technique.

When we do the GNOME Shell 41 transition, hopefully soon, we will have
to either update this extension or remove it from testing. It would be
useful to get a fixed version into experimental.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-arc-menu
Source-Version: 49+forkv18-1
Done: Jonathan Carter 

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

Debian distribution maintenance software
pp.
Jonathan Carter  (supplier of updated 
gnome-shell-extension-arc-menu package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 Sep 2021 10:44:14 +0200
Source: gnome-shell-extension-arc-menu
Architecture: source
Version: 49+forkv18-1
Distribution: unstable
Urgency: medium
Maintainer: Jonathan 
Changed-By: Jonathan Carter 
Closes: 983463 993182 996045
Changes:
 gnome-shell-extension-arc-menu (49+forkv18-1) unstable; urgency=medium
 .
   * Update standards version to 4.6.0
   * New upstream fork (Closes: #993182, #996045)
 - Update debian/install with new upstream name
   * Depend on minimum gnome-shell version 40
   * Update copyright years
   * Install schema in correct directory (Closes: #983463)
   * Update chmod paths in debian/rules
Checksums-Sha1:
 dcdf6c9d9e421800d416ea66f52afb488a132ffb 2206 
gnome-shell-extension-arc-menu_49+forkv18-1.dsc
 b4052f7c29dbb71976e6f56afe4420196536598d 476706 
gnome-shell-extension-arc-menu_49+forkv18.orig.tar.bz2
 441ad9665a2b2bf0dd41c754a5064418ca03d6e7 2360 
gnome-shell-extension-arc-menu_49+forkv18-1.debian.tar.xz
 34059ee7695a26e9ebb6b8799a7289e0c0996083 5905 
gnome-shell-extension-arc-menu_49+forkv18-1_source.buildinfo
Checksums-Sha256:
 2b28fbb77d83fc4938e9f84ac212c6b8a2fb99ec4ba3a10c0d998f72b53789c8 2206 
gnome-shell-extension-arc-menu_49+forkv18-1.dsc
 dbaca7a495230b337e59ceb82f799b3235b7b02db44033ab80a3578b6b704c82 476706 
gnome-shell-extension-arc-menu_49+forkv18.orig.tar.bz2
 5cef89c8c5fd63b21f5ab6e4fab0f6910ce073a499b10a0ea3b413e4f18f2195 2360 
gnome-shell-extension-arc-menu_49+forkv18-1.debian.tar.xz
 fa4a3fc9e94448cd5d426ff5c0f1267310c132a0e899912c7d34e0a2194d008f 5905 
gnome-shell-extension-arc-menu_49+forkv18-1_source.buildinfo
Files:
 17d4fceb52a351ea03a73b1ec6dedd6e 2206 gnome optional 
gnome-shell-extension-arc-menu_49+forkv18-1.dsc
 a19cf6a76aaa08de15e699ff44247c16 476706 gnome optional 
gnome-shell-extension-arc-menu_49+forkv18.orig.tar.bz2
 12da4b7496bd82c5aec6f8df49119ccd 2360 gnome optional 
gnome-shell-extension-arc-menu_4

Bug#993182: marked as done (gnome-shell-extension-arc-menu: does not declare compatibility with GNOME Shell 40)

[Debian Bug Tracking System]

Your message dated Wed, 20 Oct 2021 12:34:00 +
with message-id 
and subject line Bug#993182: fixed in gnome-shell-extension-arc-menu 
49+forkv18-1
has caused the Debian Bug report #993182,
regarding gnome-shell-extension-arc-menu: does not declare compatibility with 
GNOME Shell 40
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.)


-- 
993182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993182
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-arc-menu
Version: 49-1
Severity: important

The metadata.json for this extension doesn't declare compatibility with
GNOME 40.

In many versions of GNOME Shell this didn't matter much, because
validation of extensions' metadata against the installed Shell version
was disabled by default, but in GNOME 40 the default has changed back
to enabling the version check by default, in an effort to avoid issues
caused by outdated extensions remaining enabled.

When we do the GNOME 40 transition, hopefully soon, we will have to
either update this extension or remove it from testing. It would be
useful to get a fixed version into experimental.

Note that the upstream project seems to have been shut down since
GNOME 3.38, with a continuation under a different UUID at
.

Would you mind adding the GNOME team to Uploaders so we can "officially"
do team-uploads? I think that'd be useful for future transitions.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-arc-menu
Source-Version: 49+forkv18-1
Done: Jonathan Carter 

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

Debian distribution maintenance software
pp.
Jonathan Carter  (supplier of updated 
gnome-shell-extension-arc-menu package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 Sep 2021 10:44:14 +0200
Source: gnome-shell-extension-arc-menu
Architecture: source
Version: 49+forkv18-1
Distribution: unstable
Urgency: medium
Maintainer: Jonathan 
Changed-By: Jonathan Carter 
Closes: 983463 993182 996045
Changes:
 gnome-shell-extension-arc-menu (49+forkv18-1) unstable; urgency=medium
 .
   * Update standards version to 4.6.0
   * New upstream fork (Closes: #993182, #996045)
 - Update debian/install with new upstream name
   * Depend on minimum gnome-shell version 40
   * Update copyright years
   * Install schema in correct directory (Closes: #983463)
   * Update chmod paths in debian/rules
Checksums-Sha1:
 dcdf6c9d9e421800d416ea66f52afb488a132ffb 2206 
gnome-shell-extension-arc-menu_49+forkv18-1.dsc
 b4052f7c29dbb71976e6f56afe4420196536598d 476706 
gnome-shell-extension-arc-menu_49+forkv18.orig.tar.bz2
 441ad9665a2b2bf0dd41c754a5064418ca03d6e7 2360 
gnome-shell-extension-arc-menu_49+forkv18-1.debian.tar.xz
 34059ee7695a26e9ebb6b8799a7289e0c0996083 5905 
gnome-shell-extension-arc-menu_49+forkv18-1_source.buildinfo
Checksums-Sha256:
 2b28fbb77d83fc4938e9f84ac212c6b8a2fb99ec4ba3a10c0d998f72b53789c8 2206 
gnome-shell-extension-arc-menu_49+forkv18-1.dsc
 dbaca7a495230b337e59ceb82f799b3235b7b02db44033ab80a3578b6b704c82 476706 
gnome-shell-extension-arc-menu_49+forkv18.orig.tar.bz2
 5cef89c8c5fd63b21f5ab6e4fab0f6910ce073a499b10a0ea3b413e4f18f2195 2360 
gnome-shell-extension-arc-menu_49+forkv18-1.debian.tar.xz
 fa4a3fc9e94448cd5d426ff5c0f1267310c132a0e899912c7d34e0a2194d008f 5905 
gnome-shell-extension-arc-menu_49+forkv18-1_source.buildinfo
Files:
 17d4fceb52a351ea03a73b1ec6dedd6e 2206 gnome optional 
gnome-shell-extension-arc-menu_49+forkv18-1.dsc
 a19cf6a76aaa08de15e699ff44247c16 476706 gnome optional 
gnome-shell-extension-arc-menu_49+forkv18.orig.tar.bz2
 12da4b7496bd82c5aec6f8df49119ccd 2360 gnome optional 
gnome-shell-extension-arc-menu_49+forkv18-1.debian.tar.xz
 19545c7c04a9d05b413d9cbdc76449dc 5905 gnome optional 
gnome-shell-extension-arc-menu_49+forkv18-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEExyA8CpIGcL+U8AuxsB0acqyNyaEFAmFwCaUPHGpjY0BkZWJp
YW4ub3JnAAoJELAdGnKsjcmh7v0P

Bug#962650: libcamera: API and ABI appear to be changing without a SONAME bump

[Dorota Czaplejewicz]

On Sat, 16 Oct 2021 17:27:28 +0200 Dorota Czaplejewicz 
 wrote:
> Hi,
> 
> I'm interested in having libcamera in Debian. We want to use it in a 
> downstream distribution (PureOS).
> 
> Is there interest in some help in maintaining this package while it's 
> unstable?
> 
> Cheers,
> Dorota

I've added a merge request that packages the current version: 
https://salsa.debian.org/multimedia-team/libcamera/-/merge_requests/3

Cheers,
Dorota


pgposYkrtsD7D.pgp
Description: OpenPGP digital signature

Bug#996895: hypre: autopkgtest regression on armhf and i386

[Sebastian Ramacher]

Source: hypre
Version: 2.22.1-2
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

autopkgtest: WARNING: package libhypre-dev is not installed though it should be
autopkgtest: WARNING: package libhypre is not installed though it should be
autopkgtest: WARNING: package libhypre64-dev is not installed though it should 
be
autopkgtest: WARNING: package libhypre64 is not installed though it should be
autopkgtest: WARNING: package libhypre64m-dev is not installed though it should 
be
autopkgtest: WARNING: package libhypre64m is not installed though it should be
autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt 
pinning. Retrying with using all packages from unstable

The libhypre64* packages are not available on i386 and armhf.

See
https://ci.debian.net/data/autopkgtest/testing/i386/h/hypre/16035696/log.gz

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Processed: Re: Bug#996815: libfreetype6: upgrade from 2.10.4+dfsg-1 to 2.11.0+dfsg-1 changes terminal text rendering

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 rxvt-unicode 9.26-2
Bug #996815 [libfreetype6] libfreetype6: upgrade from 2.10.4+dfsg-1 to 
2.11.0+dfsg-1 changes terminal text rendering
Bug reassigned from package 'libfreetype6' to 'rxvt-unicode'.
No longer marked as found in versions freetype/2.11.0+dfsg-1.
Ignoring request to alter fixed versions of bug #996815 to the same values 
previously set
Bug #996815 [rxvt-unicode] libfreetype6: upgrade from 2.10.4+dfsg-1 to 
2.11.0+dfsg-1 changes terminal text rendering
Marked as found in versions rxvt-unicode/9.26-2.
> severity -1 normal
Bug #996815 [rxvt-unicode] libfreetype6: upgrade from 2.10.4+dfsg-1 to 
2.11.0+dfsg-1 changes terminal text rendering
Severity set to 'normal' from 'serious'
> tags -1 + patch
Bug #996815 [rxvt-unicode] libfreetype6: upgrade from 2.10.4+dfsg-1 to 
2.11.0+dfsg-1 changes terminal text rendering
Added tag(s) patch.

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

Bug#996887: libcmark0.30.1: 0.30.2 bumps SONAME without changing package name

[Sebastian Ramacher]

Package: libcmark0.30.1
Version: 0.30.2-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

$ objdump -x usr/lib/x86_64-linux-gnu/libcmark.so.0.30.2 | grep SONAME
  SONAME   libcmark.so.0.30.2

This change needs to be reflected in the package name.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#996885: Patch

[Rob Shearman]

Fix submitted via pull request:
https://salsa.debian.org/debian/grpc/-/merge_requests/7

Bug#996885: grpc: FTBS: third_party/protobuf/src - No such file or directory

[Rob Shearman]

Source: grpc
Version: 1.30.2-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: r...@graphiant.com

Dear Maintainer,

grpc fails to build from source from a clean directory:

  rob@graph-dev:~/grpc ((debian/1.30.2-3))$ git clean -xdf
  rob@graph-dev:~/grpc ((debian/1.30.2-3))$ gbp buildpackage -uc -us
  gbp:info: Performing the build
   dpkg-buildpackage -us -uc -ui -i -I
  dpkg-buildpackage: info: source package grpc
  dpkg-buildpackage: info: source version 1.30.2-3
  dpkg-buildpackage: info: source distribution unstable
  dpkg-buildpackage: info: source changed by Laszlo Boszormenyi (GCS)

   dpkg-source -i -I --before-build .
  dpkg-buildpackage: info: host architecture amd64
  dpkg-source: info: using patch list from debian/patches/series
  dpkg-source: info: applying unvendor-zlib.diff
  dpkg-source: info: applying add-wrap-memcpy-flags.diff
  dpkg-source: info: applying install_libdir.patch
  dpkg-source: info: applying unversion_sphinx.patch
  dpkg-source: info: applying no_embedded_abseil.patch
  dpkg-source: info: applying link_external_abseil.patch
  dpkg-source: info: applying no-embed-libs.patch
  dpkg-source: info: applying remove-missing-files-in-gemspec.patch
  dpkg-source: info: applying no-make-in-extconf.patch
  dpkg-source: info: applying use-system-grpc.patch
  dpkg-source: info: applying fix-protoc-path.patch
  dpkg-source: info: applying add_grpc_libdir.patch
  dpkg-source: info: applying unbreak_foreach.patch
  dpkg-source: info: applying 9e0b427893b65b220faf8a31a6afdc67f6f41364.patch
  dpkg-source: info: applying
16-member_variable_should_not_be_a_reference.patch
  dpkg-source: info: applying
17-fixing_a_member_var_to_not_be_a_reference.patch
   debian/rules clean
  dh clean --with=python3
 debian/rules override_dh_auto_clean
  make[1]: Entering directory '/home/rob/grpc'
  dh_auto_clean
make -j5 clean
  make[2]: Entering directory '/home/rob/grpc'
  rm -f -rf /home/rob/grpc/objs /home/rob/grpc/libs /home/rob/grpc/bins
/home/rob/grpc/gens cache.mk
  make[2]: Leaving directory '/home/rob/grpc'
  dh_auto_clean -O--buildsystem=pybuild
  I: pybuild base:232: python3.9 setup.py clean
  /usr/lib/python3/dist-packages/Cython/Compiler/Main.py:369: FutureWarning:
Cython directive 'language_level' not set, using 2 for now (Py2). This will
change in a later release! File:
/home/rob/grpc/src/python/grpcio/grpc/_cython/cygrpc.pxd
tree = Parsing.p_module(s, pxd, full_module_name)
  Compiling src/python/grpcio/grpc/_cython/cygrpc.pyx because it changed.
  [1/1] Cythonizing src/python/grpcio/grpc/_cython/cygrpc.pyx
  running clean
  removing '/home/rob/grpc/.pybuild/cpython3_3.9_grpcio/build' (and everything
under it)
  'python_build/bdist.linux-x86_64' does not exist -- can't clean it
  'python_build/scripts-3.9' does not exist -- can't clean it
  find /home/rob/grpc/src/python/grpcio/ -name \*.so -delete
  rm -f -r /home/rob/grpc/src/python/grpcio/grpcio.egg-info/ \
/home/rob/grpc/.eggs/
  rm -f \
/home/rob/grpc/src/python/grpcio/grpc/_cython/_credentials/roots.pem \
/home/rob/grpc/src/python/grpcio/grpc/_cython/cygrpc.cpp \
/home/rob/grpc/src/python/grpcio/grpc/_grpcio_metadata.py
  rm -f a.out
  make[1]: Leaving directory '/home/rob/grpc'
 dh_clean
   dpkg-source -i -I -b .
  dpkg-source: info: using source format '3.0 (quilt)'
  dpkg-source: info: building grpc using existing ./grpc_1.30.2.orig.tar.gz
  dpkg-source: info: using patch list from debian/patches/series
  dpkg-source: warning: ignoring deletion of file
src/python/grpcio/grpc/_grpcio_metadata.py, use --include-removal to override
  dpkg-source: info: building grpc in grpc_1.30.2-3.debian.tar.xz
  dpkg-source: info: building grpc in grpc_1.30.2-3.dsc
   debian/rules binary
  dh binary --with=python3
 dh_update_autotools_config
 dh_autoreconf
 debian/rules override_dh_auto_configure
  make[1]: Entering directory '/home/rob/grpc'
  dh_auto_configure
  dh_auto_configure -O--buildsystem=pybuild
  I: pybuild base:232: python3.9 setup.py config
  /usr/lib/python3/dist-packages/Cython/Compiler/Main.py:369: FutureWarning:
Cython directive 'language_level' not set, using 2 for now (Py2). This will
change in a later release! File:
/home/rob/grpc/src/python/grpcio/grpc/_cython/cygrpc.pxd
tree = Parsing.p_module(s, pxd, full_module_name)
  Compiling src/python/grpcio/grpc/_cython/cygrpc.pyx because it changed.
  [1/1] Cythonizing src/python/grpcio/grpc/_cython/cygrpc.pyx
  running config
  make[1]: Leaving directory '/home/rob/grpc'
 debian/rules override_dh_auto_build
  make[1]: Entering directory '/home/rob/grpc'
  # Fake included protobuf .proto files
  mkdir -p /home/rob/grpc/Ithird_party/protobuf/
  ln -s /usr/include /home/rob/grpc/third_party/protobuf/src
  ln: failed to create symbolic link '/home/rob/grpc/third_party/protobuf/src':
No such file or directory
  make[1]: *** [debian/rules:59: ov

Bug#996050: marked as done (gnome-shell-extension-dashtodock: does not declare compatibility with GNOME Shell 41)

[Debian Bug Tracking System]

Your message dated Wed, 20 Oct 2021 08:51:40 +
with message-id 
and subject line Bug#996050: fixed in gnome-shell-extension-dashtodock 70-1
has caused the Debian Bug report #996050,
regarding gnome-shell-extension-dashtodock: does not declare compatibility with 
GNOME Shell 41
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.)


-- 
996050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996050
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-dashtodock
Version: 69-1
Severity: normal
Tags: bookworm sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-41

The metadata.json for this extension doesn't declare compatibility with
GNOME 41. I don't know whether the actual code will need changes or not:
the conservative assumption is that it probably will (so please test).
gnome-shell 41 should be available in experimental soon.

In versions of GNOME Shell up to 3.38, metadata.json didn't matter much,
because validation of extensions' metadata against the installed Shell
version was disabled by default; but since GNOME 40 the default has changed
back to enabling the version check by default, in an effort to avoid
issues caused by outdated extensions remaining enabled. As a result,
GNOME Shell extensions in bookworm should probably have a dependency like:

Depends: gnome-shell (>= x), gnome-shell (<< y~)

where x and y are set according to metadata.json.
gnome-shell-extension-caffeine is a good example of this technique.

When we do the GNOME Shell 41 transition, hopefully soon, we will have
to either update this extension or remove it from testing. It would be
useful to get a fixed version into experimental.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-dashtodock
Source-Version: 70-1
Done: Jonathan Carter 

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

Debian distribution maintenance software
pp.
Jonathan Carter  (supplier of updated 
gnome-shell-extension-dashtodock package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 19 Oct 2021 20:17:56 +0200
Source: gnome-shell-extension-dashtodock
Architecture: source
Version: 70-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jonathan Carter 
Closes: 993184 996050
Changes:
 gnome-shell-extension-dashtodock (70-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #993184)
   * Refresh patch to clean translations
   * Add new build-dependency: sassc
   * Add patch to mark GNOME 41 as supported (Closes: #996050)
   * Add patch to compensate for AppIconMenu method name change
Checksums-Sha1:
 d119c170fb51967ea6cbf528814b6f9ce3d0b3fe 2240 
gnome-shell-extension-dashtodock_70-1.dsc
 396e8efa5d0171cffc7fead4da271ae2d63b9885 292243 
gnome-shell-extension-dashtodock_70.orig.tar.gz
 275ce332137e0461128e3a195fdb2f7fc0a1900a 4684 
gnome-shell-extension-dashtodock_70-1.debian.tar.xz
 e7e9991b333830fd29c021a22d93e5dd63931961 5881 
gnome-shell-extension-dashtodock_70-1_source.buildinfo
Checksums-Sha256:
 3227226999f34f131c039d8abc397b5451db3b10e4c11301718be97039d0cc64 2240 
gnome-shell-extension-dashtodock_70-1.dsc
 49cc0dd275243980a6f0dabfd5b31561a46b96a9028dd18ba24da65d6c3edf01 292243 
gnome-shell-extension-dashtodock_70.orig.tar.gz
 c47a923bfb6ec704739cd0a074a13fa407a6cfcac30ee160cf7c778f16f2df62 4684 
gnome-shell-extension-dashtodock_70-1.debian.tar.xz
 456766350932b91151aafc98abb2f1d308aeea143a4d5ec40fa963e94066da92 5881 
gnome-shell-extension-dashtodock_70-1_source.buildinfo
Files:
 fa13117843f83bd663f07bc207d70123 2240 gnome optional 
gnome-shell-extension-dashtodock_70-1.dsc
 07e30d400b57f1431189ea9ff659283e 292243 gnome optional 
gnome-shell-extension-dashtodock_70.orig.tar.gz
 b0446431ef0e175519f386fd8b771d22 4684 gnome optional 
gnome-shell-extension-dashtodock_70-1.debian.tar.xz
 730170be3d2a21d8103d9fcde7bea21d 5881 gnome optional 
gnome-shell-extension-dashtodock_70-1_source.buildinfo

Bug#993184: marked as done (gnome-shell-extension-dashtodock: not compatible with GNOME 40)

[Debian Bug Tracking System]

Your message dated Wed, 20 Oct 2021 08:51:40 +
with message-id 
and subject line Bug#993184: fixed in gnome-shell-extension-dashtodock 70-1
has caused the Debian Bug report #993184,
regarding gnome-shell-extension-dashtodock: not compatible with GNOME 40
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.)


-- 
993184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993184
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-dashtodock
Version: 69-1
Severity: important
Tags: upstream
Forwarded: https://github.com/micheleg/dash-to-dock/pull/1402

The metadata.json for this extension doesn't declare compatibility with
GNOME 40, and it seems the extension code itself is not compatible.

When we do the GNOME 40 transition, hopefully soon, we will have to
either update this extension or remove it from testing. It would be
useful to get a fixed version into experimental.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-dashtodock
Source-Version: 70-1
Done: Jonathan Carter 

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

Debian distribution maintenance software
pp.
Jonathan Carter  (supplier of updated 
gnome-shell-extension-dashtodock package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 19 Oct 2021 20:17:56 +0200
Source: gnome-shell-extension-dashtodock
Architecture: source
Version: 70-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jonathan Carter 
Closes: 993184 996050
Changes:
 gnome-shell-extension-dashtodock (70-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #993184)
   * Refresh patch to clean translations
   * Add new build-dependency: sassc
   * Add patch to mark GNOME 41 as supported (Closes: #996050)
   * Add patch to compensate for AppIconMenu method name change
Checksums-Sha1:
 d119c170fb51967ea6cbf528814b6f9ce3d0b3fe 2240 
gnome-shell-extension-dashtodock_70-1.dsc
 396e8efa5d0171cffc7fead4da271ae2d63b9885 292243 
gnome-shell-extension-dashtodock_70.orig.tar.gz
 275ce332137e0461128e3a195fdb2f7fc0a1900a 4684 
gnome-shell-extension-dashtodock_70-1.debian.tar.xz
 e7e9991b333830fd29c021a22d93e5dd63931961 5881 
gnome-shell-extension-dashtodock_70-1_source.buildinfo
Checksums-Sha256:
 3227226999f34f131c039d8abc397b5451db3b10e4c11301718be97039d0cc64 2240 
gnome-shell-extension-dashtodock_70-1.dsc
 49cc0dd275243980a6f0dabfd5b31561a46b96a9028dd18ba24da65d6c3edf01 292243 
gnome-shell-extension-dashtodock_70.orig.tar.gz
 c47a923bfb6ec704739cd0a074a13fa407a6cfcac30ee160cf7c778f16f2df62 4684 
gnome-shell-extension-dashtodock_70-1.debian.tar.xz
 456766350932b91151aafc98abb2f1d308aeea143a4d5ec40fa963e94066da92 5881 
gnome-shell-extension-dashtodock_70-1_source.buildinfo
Files:
 fa13117843f83bd663f07bc207d70123 2240 gnome optional 
gnome-shell-extension-dashtodock_70-1.dsc
 07e30d400b57f1431189ea9ff659283e 292243 gnome optional 
gnome-shell-extension-dashtodock_70.orig.tar.gz
 b0446431ef0e175519f386fd8b771d22 4684 gnome optional 
gnome-shell-extension-dashtodock_70-1.debian.tar.xz
 730170be3d2a21d8103d9fcde7bea21d 5881 gnome optional 
gnome-shell-extension-dashtodock_70-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEExyA8CpIGcL+U8AuxsB0acqyNyaEFAmFv1KYPHGpjY0BkZWJp
YW4ub3JnAAoJELAdGnKsjcmhswsQALDm1q7ytlB4zbvoqrNg8JW9BBmpbnuoP3RR
wHyfjEnXLIRPnQ49WsAue7OVBdm6P6mpgtLFMNS81Q6cdpiIDdu1hjmVdSO7y6I5
VzwVpOM/WxYRSNdD/bIgnmiTaQ+WNBkWyYOs94ZuclsCx5VqQFrLQNs2pjkKhLR5
aMuxehrMvX7AIDWtjEwaW2wAA8l2erPp1cEy8z3MHUBUn/X6UhxZ9Mrj3MibidxD
DS5Xm2rDTJE3gvH/RfOhpL6HbEjFZf6qyE4lzC2ytXMzRuxvVfSY1MsC/iZUh8NM
APAJfoyDuQAUIPja9nCuNRwuYWgp/do5h4MQVesj/os/BM+NZtXwfXTqM8FnB5Ni
TqLKd6kdq6PBVKnq+dn69TvQ/jfCxAm0I3bLwJoIhc0pIP8fnyRMSyXHuFJN/psu
i2HA8wFVKK4CAwFCaOzgUu2HBz45MIv1za0Hs1zNNTW0T5vm4JSvbOe0s4/PaBwV
H9kYC/J3CFGW4pt7amAUPu11gxYu9ds5HxR67zT23EnPfBEK0V4pJv2lkDJmW6iG
Fzy9PGY04E5reE5DQ/DVWHmsLxKoG0o2ag0AumjBpfUuyciIYul7OZAHLLdjl61D
hA+htAplByaiCY/tbKfRLbh1n3SxRgyfziVcCagv119

Bug#996049: marked as done (gnome-shell-extension-dash-to-panel: does not declare compatibility with GNOME Shell 41)

[Debian Bug Tracking System]

Your message dated Wed, 20 Oct 2021 08:33:39 +
with message-id 
and subject line Bug#996049: fixed in gnome-shell-extension-dash-to-panel 
43+git20210906-b7213be-1
has caused the Debian Bug report #996049,
regarding gnome-shell-extension-dash-to-panel: does not declare compatibility 
with GNOME Shell 41
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.)


-- 
996049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996049
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-dash-to-panel
Version: 43-2
Severity: normal
Tags: bookworm sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-41

The metadata.json for this extension doesn't declare compatibility with
GNOME 41. I don't know whether the actual code will need changes or not:
the conservative assumption is that it probably will (so please test).
gnome-shell 41 should be available in experimental soon.

In versions of GNOME Shell up to 3.38, metadata.json didn't matter much,
because validation of extensions' metadata against the installed Shell
version was disabled by default; but since GNOME 40 the default has changed
back to enabling the version check by default, in an effort to avoid
issues caused by outdated extensions remaining enabled. As a result,
GNOME Shell extensions in bookworm should probably have a dependency like:

Depends: gnome-shell (>= x), gnome-shell (<< y~)

where x and y are set according to metadata.json.
gnome-shell-extension-caffeine is a good example of this technique.

When we do the GNOME Shell 41 transition, hopefully soon, we will have
to either update this extension or remove it from testing. It would be
useful to get a fixed version into experimental.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-dash-to-panel
Source-Version: 43+git20210906-b7213be-1
Done: Jonathan Carter 

We believe that the bug you reported is fixed in the latest version of
gnome-shell-extension-dash-to-panel, 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 996...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonathan Carter  (supplier of updated 
gnome-shell-extension-dash-to-panel 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: Wed, 20 Oct 2021 10:09:02 +0200
Source: gnome-shell-extension-dash-to-panel
Architecture: source
Version: 43+git20210906-b7213be-1
Distribution: unstable
Urgency: medium
Maintainer: Jonathan Carter 
Changed-By: Jonathan Carter 
Closes: 996049
Changes:
 gnome-shell-extension-dash-to-panel (43+git20210906-b7213be-1) unstable; 
urgency=medium
 .
   * New upstream snapshot (Closes: #996049)
   * Fix standards version, set to 4.6.0
Checksums-Sha1:
 21beaa8982cd5c956f8933f4dd3a88078e2c4dba 2334 
gnome-shell-extension-dash-to-panel_43+git20210906-b7213be-1.dsc
 5b75a2a2043d9b465ea76c601efbc037db8620e0 21141138 
gnome-shell-extension-dash-to-panel_43+git20210906-b7213be.orig.tar.gz
 c4e67f3377a9714914c85fddb613e5c1a0178945 3152 
gnome-shell-extension-dash-to-panel_43+git20210906-b7213be-1.debian.tar.xz
 b1aa00ecc97ce15cf449a0019259d97d71ba4ab9 5990 
gnome-shell-extension-dash-to-panel_43+git20210906-b7213be-1_source.buildinfo
Checksums-Sha256:
 81dd4de1a2a81784cb20765b597055602cc53cf32f74ccb5614b08db2a2d50d1 2334 
gnome-shell-extension-dash-to-panel_43+git20210906-b7213be-1.dsc
 85fb091e65caf257d2d202890369383167c6f8afc47122d46e1d78127654ff3d 21141138 
gnome-shell-extension-dash-to-panel_43+git20210906-b7213be.orig.tar.gz
 92f404330836e6fb1a10a153edb34068fb54fd2ea43bf4661cbc8b431a070e41 3152 
gnome-shell-extension-dash-to-panel_43+git20210906-b7213be-1.debian.tar.xz
 81765aba1726ad87b6726758a4440ee1e20f855031633be87bc97d600ee2faf6 5990 
gnome-shell-extension-dash-to-panel_43+git20210906-b7213be-1_source.buildinfo
Files:
 fef66f5aeac1051bde6eff0d545abbf4 2334 gnome optional 
gnome-shell-extension-dash-to-panel_43+git20210906-b7213be-1.dsc
 68a7ecb864c22f47826432539635647a 21141138 gnome optional 
gnome-shell-extension-dash-to-panel_43+git20210906-b7213be.orig.tar.gz
 83a93f9dceb8f7e2b17fedbee0b8eb20 3152 gnome optional 
gnome

Processed: closing 970880

[Debian Bug Tracking System]

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

> close 970880 0.79.14+git20211010-1
Bug #970880 [certmonger] freeipa-server: FreeIPA server installation fails with 
Certificate issuance failed (CA_REJECTED)
Marked as fixed in versions certmonger/0.79.14+git20211010-1.
Bug #970880 [certmonger] freeipa-server: FreeIPA server installation fails with 
Certificate issuance failed (CA_REJECTED)
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#970880: closing 970880

[Timo Aaltonen]

close 970880 0.79.14+git20211010-1
thanks

So, as it turns out this bug was caused by certmonger still being
built against libcurl4-nss-dev, while the rest of the stack had moved to
openssl.. Many thanks to Spencer Olson for figuring it out!

The current stack on unstable seems to be able to pass ipaserver-install,
at least without bind9 and dnssec, but I'm sure there are some kinks left to
fix. Anyway, I wouldn't consider all of this backportable until it passes the
full test suite on Azure, and that's still WIP.

timo

Processed: reassign 970880 to certmonger

[Debian Bug Tracking System]

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

> reassign 970880 certmonger
Bug #970880 [freeipa-server] freeipa-server: FreeIPA server installation fails 
with Certificate issuance failed (CA_REJECTED)
Bug reassigned from package 'freeipa-server' to 'certmonger'.
No longer marked as found in versions freeipa/4.8.8-2.
Ignoring request to alter fixed versions of bug #970880 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#996878: python3-prelude: python3 import prelude throws an ImportError exception

[Francois Lesueur]

Package: python3-prelude
Version: 5.2.0-4
Severity: grave
Justification: renders package unusable


Dear Maintainer,

   * What led up to the situation?
Installing python3-prelude on a fresh bullseye, then importing
"prelude" in the python3 interpreter
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I tried to use python3-prelude from unstable with no luck
   * What was the outcome of this action?
Importing generates :
:~# python3
Python 3.9.2 (default, Feb 28 2021, 17:03:44) 
[GCC 10.2.1 20210110] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import prelude
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/prelude.py", line 15, in 
from _prelude import *
ImportError: 
/usr/lib/python3/dist-packages/_prelude.cpython-39-x86_64-linux-gnu.so: 
undefined symbol: PyIOBase_Type

   * What outcome did you expect instead?
I expected it to load prelude. It seems to also affect prewikka which
does this import (my first problem was related to prewikka, I digged it
to python3-prelude)

Cheers
François Lesueur


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

Kernel: Linux 5.10.0-9-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python3-prelude depends on:
ii  libc62.31-13+deb11u2
ii  libgcc-s110.2.1-6
ii  libprelude28 5.2.0-4
ii  libpreludecpp12  5.2.0-3+b1
ii  libstdc++6   10.2.1-6
ii  python3  3.9.2-3

python3-prelude recommends no packages.

python3-prelude suggests no packages.

-- no debconf information

Processed: novaclient is fixed

[Debian Bug Tracking System]

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

> fixed 986143 2:17.6.0-2
Bug #986143 {Done: Thomas Goirand } [python3-novaclient] 
python3-django breaks: python3-django-horizon << 3:18.3.3
Marked as fixed in versions python-novaclient/2:17.6.0-2.
>
End of message, stopping processing here.

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

Bug#996863: src:python-novaclient: fails to migrate to testing for too long: unresolved RC bug

[Thomas Goirand]

On 10/20/21 8:06 AM, Paul Gevers wrote:
>>> I'm not sure if the blocking bug is even a bug in bookworm. If I
>>> understand it correctly, the issue reported there was purely for buster
>>> to bullseye upgrades and can be ignored afterwards. FYI, the BTS
>>> considers the bug affecting unstable because the version of the package
>>> in unstable is not a descendant of the fixed version (judged by parsing
>>> the changelog).
>>
>> This looks like a correct analysis. So in fact, the only thing that
>> should be done is fix the BTS entry no? I'm not sure how...
> 
> Tell the BTS that the version in unstable is also fixed:
> https://www.debian.org/Bugs/server-control

Thanks for confirming it, as I wasn't sure.

>> IMO, that's not what's needed here. What's needed, is to tell the BTS
>> the package is working as expected, and should be migrating. IMO, the
>> bug you're opening is:
>> 1/ not following the rules (because 22 days instead of 60)
> 
> I don't agree, your package *is* out of sync for so long.

Oh ok. Though you pointed at the excuse page which showed 22 days, which
was kind of confusing then... :)

>> 2/ unfortunately not very helpful ...
> 
> I consider it the task of the maintainer to ensure his package migrates.
> That was what I tried to convey. In this case I spotted the likely root
> cause and I hope I taught you something in the process such that future
> uploads don't suffer from this.

Thanks for it, as it hopefully triggered the right fix.

Cheers,

Thomas Goirand (zigo)