Bug#1042252: warning: cannot select font 'C'

[M Hickford]

If it helps, I opened a pandoc issue about the groff "warning: cannot
select font 'C'" https://github.com/jgm/pandoc/issues/9020

Bug#999946: [Syslog-ng-maintainers] Bug#999946: patch for pcre transition

[Attila Szalay]

I'll upload a new version tomorrow.

On Thu, 24 Aug 2023, 20:03 Helmut Grohne,  wrote:

> Control: tags -1 + patch
>
> Hi,
>
> thanks for updating syslog-ng to a new upstream release. This new
> release no longer supports building with pcre3. The build dependency
> closure happens (by chance) to also include libpcre2-dev, which is the
> reason that your build didn't fail. The only missing piece to finally
> closing the pcre transition bug is swapping out the direct build
> dependency. I'm attaching a patch for doing so.
>
> Would you rather take care of this yourself or do you appreciate me
> uploading it via the NMU procedure?
>
> Fixing this bug is required to make syslog-ng migrate to trixie.
>
> Helmut
> ___
> Syslog-ng-maintainers mailing list
> syslog-ng-maintain...@alioth-lists.debian.net
>
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/syslog-ng-maintainers
>

Bug#1042247: marked as done (nitime: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2023 21:04:51 +
with message-id 
and subject line Bug#1042247: fixed in nitime 0.10.1-1
has caused the Debian Bug report #1042247,
regarding nitime: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i 
python{version} -p 3.11 returned exit code 13
to be marked as done.

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

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


-- 
1042247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042247
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nitime
Version: 0.9-5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py config 
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build 
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11/build; 
> python3.11 -m pytest 
> = test session starts 
> ==
> platform linux -- Python 3.11.4, pytest-7.4.0, pluggy-1.2.0
> rootdir: /<>
> collected 123 items
> 
> nitime/algorithms/tests/test_autoregressive.py . [  
> 4%]
> nitime/algorithms/tests/test_coherence.py ..s[ 
> 16%]
> nitime/algorithms/tests/test_correlation.py .[ 
> 17%]
> nitime/algorithms/tests/test_entropy.py .[ 
> 21%]
> nitime/algorithms/tests/test_event_related.py .  [ 
> 21%]
> nitime/algorithms/tests/test_spectral.py [ 
> 34%]
> nitime/analysis/tests/test_base.py . [ 
> 35%]
> nitime/analysis/tests/test_coherence.py ..   [ 
> 40%]
> nitime/analysis/tests/test_correlation.py .  [ 
> 41%]
> nitime/analysis/tests/test_granger.py .. [ 
> 43%]
> nitime/analysis/tests/test_snr.py .  [ 
> 43%]
> nitime/fmri/tests/test_io.py F   [ 
> 44%]
> nitime/tests/test_algorithms.py  [ 
> 51%]
> nitime/tests/test_analysis.py ...[ 
> 56%]
> nitime/tests/test_descriptors.py .   [ 
> 57%]
> nitime/tests/test_lazy.py .. [ 
> 59%]
> nitime/tests/test_timeseries.py  [ 
> 88%]
> nitime/tests/test_utils.py ...   [ 
> 97%]
> nitime/tests/test_viz.py ... 
> [100%]
> 
> === FAILURES 
> ===
> __ test_time_series_from_file 
> __
> 
> @pytest.mark.skipif(no_nibabel, reason=no_nibabel_msg)
> def test_time_series_from_file():
> 
> """Testing reading of data from nifti files, using nibabel"""
> 
> TR = 1.35
> ts_ff = io.time_series_from_file
> 
> #File names:
> fmri_file1 = os.path.join(data_path,'fmri1.nii.gz')
> fmri_file2 = os.path.join(data_path,'fmri2.nii.gz')
> 
> #Spatial coordinates into the volumes:
> coords1 = np.array([[5,5,5,5],[5,5,5,5],[1,2,3,4]])
> coords2 = np.array([[6,6,6,6],[6,6,6,6],[3,4,5,6]])
> 
> #No averaging, no normalization:
> >   t1 = ts_ff([fmri_file1,fmri_file2],[coords1,coords2],TR)
> 
> nitime/fmri/tests/test_io.py:43: 
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> nitime/fmri/io.py:121: in time_series_from_file
> data = im.get_data()
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> 
> args = (,), kwargs = {}
> 
> @functools.wraps(func)
> def deprecated_func(*args: P.args, **kwargs: P.kwargs) -> T:
> if until and self.is_bad_version(until):
> >   raise exception(message)
> E   nibabel.deprecator.ExpiredDeprecationError: get_data() is 
> deprecated in favor of get_fdata(), which has a more predictable return type. 
> To 

Bug#1050462: gtg: crashes on startup often

[Antonio Terceiro]

Package: gtg
Version: 0.6-4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

gtg crashes on startup very often.

~$ gtg
2023-08-24 14:38:12,928 - WARNING - adaptive_button:do_forall:279 - Got error 
in for but it should've stay valid: AttributeError("'AdaptiveFittingWidget' 
object has no attribute '_children'")
~$ gtg
2023-08-24 14:38:17,288 - WARNING - adaptive_button:do_forall:279 - Got error 
in for but it should've stay valid: AttributeError("'AdaptiveFittingWidget' 
object has no attribute '_children'")
~$ gtg
Segmentation fault
~[139]$ gtg
2023-08-24 14:38:25,240 - WARNING - adaptive_button:do_forall:279 - Got error 
in for but it should've stay valid: AttributeError("'AdaptiveFittingWidget' 
object has no attribute '_children'")
~$ gtg
Segmentation fault
~[139]$ gtg
Segmentation fault
~[139]$ gtg
2023-08-24 14:38:40,377 - WARNING - adaptive_button:do_forall:279 - Got error 
in for but it should've stay valid: AttributeError("'AdaptiveFittingWidget' 
object has no attribute '_children'")

I can reproduce this issue:

- on both arm64 and amd64 systems, running testing;
- with or without wiping out ~/.local/share/gtg/ before each attempt at
  starting it.

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (900, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: arm64 (aarch64)

Kernel: Linux 6.5.0-0-arm64 (SMP w/32 CPU threads)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gtg depends on:
ii  gir1.2-gtk-3.0 [gir1.2-gdk-3.0]  3.24.38-2
ii  gir1.2-gtksource-4   4.8.4-4
ii  gir1.2-pango-1.0 1.51.0+ds-2
ii  gir1.2-secret-1  0.21.0-1
ii  pdftk-java   3.3.3-1
ii  python3  3.11.4-5+b1
ii  python3-caldav   0.11.0-1
ii  python3-cheetah  3.3.2-1
ii  python3-gi   3.44.1-2
ii  python3-gi-cairo 3.44.1-2
ii  python3-liblarch 3.2.0-3
ii  python3-lxml 4.9.3-1
ii  texlive-extra-utils  2022.20230122-4
ii  texlive-latex-base   2022.20230122-3

gtg recommends no packages.

gtg suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Processed: severity

[Debian Bug Tracking System]

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

> severity 1050372 normal
Bug #1050372 [ftp.debian.org] RM: prooftree -- RoQA; depends on gtk2; no human 
uploader; unmaintained upstream; low popcon
Severity set to 'normal' from 'serious'
> severity 1050369 normal
Bug #1050369 [ftp.debian.org] RM: freetennis -- RoQA; dead upstream; depends on 
gtk2
Severity set to 'normal' from 'serious'
>
End of message, stopping processing here.

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

Processed: tags patch

[Debian Bug Tracking System]

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

> tags 1050459 patch
Bug #1050459 [elpa-buttercup] elpa-buttercup: FTBFS with Emacs 29.1
Added tag(s) patch.
> thanks
Stopping processing here.

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

Processed: patch for pcre transition

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #46 [src:syslog-ng] syslog-ng: depends on obsolete pcre3 library
Added tag(s) patch.

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

Bug#999946: patch for pcre transition

[Helmut Grohne]

Control: tags -1 + patch

Hi,

thanks for updating syslog-ng to a new upstream release. This new
release no longer supports building with pcre3. The build dependency
closure happens (by chance) to also include libpcre2-dev, which is the
reason that your build didn't fail. The only missing piece to finally
closing the pcre transition bug is swapping out the direct build
dependency. I'm attaching a patch for doing so.

Would you rather take care of this yourself or do you appreciate me
uploading it via the NMU procedure?

Fixing this bug is required to make syslog-ng migrate to trixie.

Helmut
diff --minimal -Nru syslog-ng-4.3.1/debian/changelog 
syslog-ng-4.3.1/debian/changelog
--- syslog-ng-4.3.1/debian/changelog2023-08-20 17:51:02.0 +0200
+++ syslog-ng-4.3.1/debian/changelog2023-08-24 20:39:02.0 +0200
@@ -1,3 +1,10 @@
+syslog-ng (4.3.1-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Switch from pcre3 to pcre2. (Closes: #46)
+
+ -- Helmut Grohne   Thu, 24 Aug 2023 20:39:02 +0200
+
 syslog-ng (4.3.1-1) unstable; urgency=medium
 
   [ Attila Szalay ]
diff --minimal -Nru syslog-ng-4.3.1/debian/control 
syslog-ng-4.3.1/debian/control
--- syslog-ng-4.3.1/debian/control  2023-08-20 17:51:02.0 +0200
+++ syslog-ng-4.3.1/debian/control  2023-08-24 20:39:01.0 +0200
@@ -20,7 +20,7 @@
libbson-dev,
libjson-c-dev | libjson0-dev,
libwrap0-dev,
-   libpcre3-dev,
+   libpcre2-dev,
libcap-dev [linux-any],
libsystemd-dev [linux-any],
libhiredis-dev,

Bug#1050459: elpa-buttercup: FTBFS with Emacs 29.1

[Xiyue Deng]

Package: elpa-buttercup
Version: 1.26-4
Severity: serious
X-Debbugs-Cc: none, Xiyue Deng 

Currently elpa-buttercup is incompatible with Emacs 29.1.  As this is a
testing library used by other packages, it indirectly breaks them on
Emacs 29.1 as well.  I have a WIP merge request[1] that sync it to the
latest version that fixes this.

[1] https://salsa.debian.org/emacsen-team/emacs-buttercup/-/merge_requests/1


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

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

Versions of packages elpa-buttercup depends on:
ii  dh-elpa-helper 2.0.16
ii  emacs  1:28.2+1-15
ii  emacs-gtk [emacs]  1:28.2+1-15
ii  emacsen-common 3.0.5

elpa-buttercup recommends no packages.

elpa-buttercup suggests no packages.

-- no debconf information

Bug#1041571: marked as done (gnome-shell-extension-flypie: needs update for GNOME Shell 44)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2023 18:20:46 +
with message-id 
and subject line Bug#1041571: fixed in gnome-shell-extension-flypie 21-2
has caused the Debian Bug report #1041571,
regarding gnome-shell-extension-flypie: needs update for GNOME Shell 44
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.)


-- 
1041571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041571
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-flypie
Version: 21-1
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-44

This extension has not been checked for compatibility with GNOME Shell
44. Depending how compatible it is, it will either need an update to
its metadata.json and debian/control to declare compatibility with the
new version, or code changes to adapt it to the new Shell version.

If not updated, it will have to be removed from testing for the GNOME
Shell 44 transition (I don't know when that will be). This bug will be
raised to serious severity when the transition is ready to go ahead.

If a new upstream version is compatible with Shell 44 but not 43,
please upload to experimental for now.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-flypie
Source-Version: 21-2
Done: Mo Zhou 

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

Debian distribution maintenance software
pp.
Mo Zhou  (supplier of updated gnome-shell-extension-flypie 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 24 Aug 2023 14:03:20 -0400
Source: gnome-shell-extension-flypie
Architecture: source
Version: 21-2
Distribution: unstable
Urgency: medium
Maintainer: Mo Zhou 
Changed-By: Mo Zhou 
Closes: 1041571
Changes:
 gnome-shell-extension-flypie (21-2) unstable; urgency=medium
 .
   * Mark gnome-shell 44 as already supported. (Closes: #1041571).
 Thanks to Simon McVittie!
Checksums-Sha1:
 4a037d76a600f6de380308ebd737cd59bf57d3c4 2073 
gnome-shell-extension-flypie_21-2.dsc
 4095f6420a0c64203e451f74a6cee2ba331d1862 5352 
gnome-shell-extension-flypie_21-2.debian.tar.xz
 af24fdbcd6034b702230a035f4cfa2f1b57fd58a 6777 
gnome-shell-extension-flypie_21-2_source.buildinfo
Checksums-Sha256:
 5c5e05e563cc1925a73d908e13836dbd9cd4bedeacc6ddaa4463d136fae217c0 2073 
gnome-shell-extension-flypie_21-2.dsc
 1299b8fc6b59e838443221436c774e8061b521c08e55ca02a64147685474bce6 5352 
gnome-shell-extension-flypie_21-2.debian.tar.xz
 4eab5dd91fe094880681aa6eb604e39c41d544e2ad304d2073f64928ba1aea2b 6777 
gnome-shell-extension-flypie_21-2_source.buildinfo
Files:
 8ce4124c8497eff640437e70b9bae236 2073 gnome optional 
gnome-shell-extension-flypie_21-2.dsc
 86b636b272cfd6680b3c68f7f64d95f8 5352 gnome optional 
gnome-shell-extension-flypie_21-2.debian.tar.xz
 b89c676499db9d1615765f65b1da5c47 6777 gnome optional 
gnome-shell-extension-flypie_21-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEY4vHXsHlxYkGfjXeYmRes19oaooFAmTnm48RHGx1bWluQGRl
Ymlhbi5vcmcACgkQYmRes19oaooxnw/+N6sPD1bOfw9yx8ImgHN0JWq+CH+d1Cd8
j7ggVajNV1DlYiFhtg11JfDIl1yhg5iVm4OwIkSJvO+idawtM+lg6kRGRwzJEoFa
aN+2e+a38co6Al3WA3Uble3UKMW6W8ns2entONLBZfhDS5YGeWJw8kPdZtdZA6xL
w0QF1x3VYLOoezb3FoSzPMT96AMLRY37gZzhVpAGblq351tLFw0wKCO9FLbKLNfs
FQQ8Y2SNSQbWD+3AuKMLp+gIIK6GkEgrLm64fJQlL0B2+rxZrxh64+CEHp7swInc
uOW1iZbrQfVYnvaHRo7fI1QYcTpZdNkBKq8iuNR0YPMret9ZHrmp/XYryVs48h4T
5LxpoE1B2kTJlPtfUQc321EF4Xbb9DUMdYlq0jRjneXVlOyOltTW24aCE/PMBFd7
Zdhz10CnLRDmXw/Wo14wNxSRbbVRGqnrePBQh8VXLbEBdH3Gf1Eot6KZoBQSoAWZ
n8hQbuUgeRE8nbFWym2mxTcfVEAF9rR58mrwNFWPS/A+JsZhKwOJFkOkF7HcTkNL
WD9UAOOdenx1P+7cqTWlqAdxJHESdPp2RS5khdrI6GqyS8pyLO+7KWqRla97De2T
5GCUctHy4+rSmhWxR1W3bMYe3WsrCNlnCeAJvDJPteK13eXHwxgOGA+iN6hxEfY2
9/VUooOLG2U=
=XIaU
-END PGP SIGNATURE End Message ---

Bug#1050363: marked as done (flit ftbfs in unstable)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2023 17:35:31 +
with message-id 
and subject line Bug#1050363: fixed in flit 3.9.0-2
has caused the Debian Bug report #1050363,
regarding flit ftbfs in unstable
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.)


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

Package: src:flit
Version: 3.9.0-1
Severity: serious
Tags: sid trixie

flit ftbfs in unstable,

[...]
__ test_sdist __

rel_path = 'README.rst', proj_dir = PosixPath('.'), guess_mimetype = True

def description_from_file(rel_path: str, proj_dir: Path, 
guess_mimetype=True):
if osp.isabs(rel_path):
raise ConfigError("Readme path must be relative")

desc_path = proj_dir / rel_path
try:
>   with desc_path.open('r', encoding='utf-8') as f:

flit_core/config.py:281:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = PosixPath('README.rst'), mode = 'r', buffering = -1, encoding = 'utf-8'
errors = None, newline = None

def open(self, mode='r', buffering=-1, encoding=None,
 errors=None, newline=None):
"""
Open the file pointed by this path and return a file object, as
the built-in open() function does.
"""
if "b" not in mode:
encoding = io.text_encoding(encoding)
>   return io.open(self, mode, buffering, encoding, errors, newline)
E   FileNotFoundError: [Errno 2] No such file or directory: 'README.rst'

/usr/lib/python3.11/pathlib.py:1045: FileNotFoundError

During handling of the above exception, another exception occurred:

tmp_path = '/tmp/pytest-of-buildd/pytest-0/test_sdist0', cwd_project = None

def test_sdist(tmp_path, cwd_project):
tmp_path = str(tmp_path)
>   filename = buildapi.build_sdist(tmp_path)

flit_core/tests/test_build_thyself.py:51:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
flit_core/buildapi.py:82: in build_sdist
path = SdistBuilder.from_ini_path(pyproj_toml).build(Path(sdist_directory))
flit_core/sdist.py:90: in from_ini_path
ini_info = read_flit_config(ini_path)
flit_core/config.py:79: in read_flit_config
return prep_toml_config(d, path)
flit_core/config.py:106: in prep_toml_config
loaded_cfg = read_pep621_metadata(d['project'], path)
flit_core/config.py:454: in read_pep621_metadata
desc_content, mimetype = description_from_file(readme, path.parent)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

rel_path = 'README.rst', proj_dir = PosixPath('.'), guess_mimetype = True

def description_from_file(rel_path: str, proj_dir: Path, 
guess_mimetype=True):
if osp.isabs(rel_path):
raise ConfigError("Readme path must be relative")

desc_path = proj_dir / rel_path
try:
with desc_path.open('r', encoding='utf-8') as f:
raw_desc = f.read()
except IOError as e:
if e.errno == errno.ENOENT:
>   raise ConfigError(
"Description file {} does not exist".format(desc_path)
)
E   flit_core.config.ConfigError: Description file README.rst does 
not exist


flit_core/config.py:285: ConfigError
=== short test summary info 
FAILED flit_core/tests/test_build_thyself.py::test_prepare_metadata - flit_co...
FAILED flit_core/tests/test_build_thyself.py::test_wheel - flit_core.config.C...
FAILED flit_core/tests/test_build_thyself.py::test_sdist - flit_core.config.C...
= 3 failed, 87 passed in 0.38s =
--- End Message ---
--- Begin Message ---
Source: flit
Source-Version: 3.9.0-2
Done: Stefano Rivera 

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

Debian distribution maintenance software
pp.
Stefano Rivera  (supplier of updated flit package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing 

Bug#1050077: marked as done (gtk4: 4.12 regression: FTBFS on mips(64)el: multiple test failures)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2023 17:06:41 +
with message-id 
and subject line Bug#1050077: fixed in gtk4 4.12.0+ds-4
has caused the Debian Bug report #1050077,
regarding gtk4: 4.12 regression: FTBFS on mips(64)el: multiple test failures
to be marked as done.

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

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


-- 
1050077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gtk4
Version: 4.12.0+ds-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: debian-m...@lists.debian.org
User: debian-m...@lists.debian.org
Usertags: mips64el mipsel

gtk4 4.12.0 in experimental has test failures on multiple buildds.
Of those, mips64el and mipsel seem to have the same failure mode:
failure mode:

  72/1464 gtk:gsk+gsk-compare+gsk-gl+gsk-compare-gl+gsk-compare-flipped-gl / gl 
border-one-rounded flipped   FAIL   
  5.47s   exit status 1
 315/1464 gtk:gsk+gsk-compare+gsk-gl+gsk-compare-gl / gl opacity-overdraw   
 FAIL   
  4.89s   exit status 1
 316/1464 gtk:gsk+gsk-compare+gsk-gl+gsk-compare-gl+gsk-compare-flipped-gl / gl 
opacity-overdraw flipped FAIL   
  4.94s   exit status 1
 317/1464 gtk:gsk+gsk-compare+gsk-gl+gsk-compare-gl+gsk-compare-repeated-gl / 
gl opacity-overdraw repeated   FAIL 
5.05s   exit status 1
 318/1464 gtk:gsk+gsk-compare+gsk-gl+gsk-compare-gl+gsk-compare-rotated-gl / gl 
opacity-overdraw rotated FAIL   
  4.95s   exit status 1
 319/1464 gtk:gsk+gsk-compare+gsk-gl+gsk-compare-gl+gsk-compare-masked-gl / gl 
opacity-overdraw masked   FAIL  
   5.02s   exit status 1
1406/1464 gtk:reftest / reftest label-sizing.ui 
 FAIL   
 19.29s   0/1 subtests passed
1422/1464 gtk:reftest / reftest opacity.ui  
 FAIL   
  6.79s   0/1 subtests passed

These are "reftests", which work by rendering the same image in two
different ways and then doing a pixel-by-pixel comparison. Because
Debian buildds do not give us a way to capture test artifacts, the images
are output into the log with uuencode, for example these:

begin-base64 644 testsuite/gsk/compare/opacity-overdraw.png
iVBORw0KGgoNSUhEUgAAAB4eCAY7MK6iRklEQVRIie3WMQ4AIAxCUWo8uDev
B7BjYwc+I8tLmAgpjwayJlDgr9lVmYpWJJRP5zc1MDAwMDAwsDFcfq7qI3XHb2o/+AJ0lQS/vZJx
GQBJRU5ErkJggg==


begin-base64 644 
debian/build/deb/testsuite/gsk/compare/gl/x11/opacity-overdraw.out.png
iVBORw0KGgoNSUhEUgAAAB4eCAY7MK6iS0lEQVRIie3WMQ4AIAhD0aIe3Isb
vACDA5GB35HlJWWpSb5VkFGBAn/Nio5HlopM+Rv8o4Z+PwYGBgYGBgauh8PpY8FGyk6/qvvBF6Er
BMOKG8HLAElFTkSuQmCC


begin-base64 644 
debian/build/deb/testsuite/gsk/compare/gl/x11/opacity-overdraw.diff.png
iVBORw0KGgoNSUhEUgAAAB4eCAY7MK6iKklEQVRIie3NoQEAIAzEwGdvZPeG
BUBR3J2MSQKfjFOsZHVO5uUDAAC82WlIAgJv9eZaAElFTkSuQmCC


The way these work is that they are output in sets of three: a reference
image, an actual output, and an artifically-enhanced diff image to
highlight what the difference is. See #1024391, #993550, #1003348 for
previous examples of architecture-specific rendering differences (#1024391
was not on mips*, but has details of how to run individual tests which
might be useful, while the other two were on mips*el).

I haven't reconstructed the actual images for a visual comparison yet.
If the mis-rendering doesn't seem release-critically bad then we'll work
around this by ignoring those particular test failures on mips*el.

mips*el are the only architectures where we are using the softpipe GL
driver (because llvmpipe appears to be otherwise broken there) so that is a
possible root cause.

Having to investigate and work around failing tests in GL-dependent
packages on mips*el is becoming a significant time sink for the GNOME team,
so I would appreciate it if mips porters could fix its llvmpipe so that it
can be back in the same situation as every other release architecture.

smcv
--- End Message ---
--- Begin Message ---
Source: gtk4
Source-Version: 4.12.0+ds-4
Done: Simon 

Bug#1050288: nsis 3.08-3 (bookworm) generates bogus relocation information (regression)

[Christian Franke]

A manual download of nsis{-common}-3.09-1 from debian testing and 'dpgk 
--install --force-all' succeeded and makensis works then. With this 
version, the problem does not occur.


A backport of this version to bookworm should fix the problem.

Processed: Bug#1050363 marked as pending in flit

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1050363 [src:flit] flit ftbfs in unstable
Added tag(s) pending.

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

Bug#1050363: marked as pending in flit

[Stefano Rivera]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/flit/-/commit/c1e043d301493c47fe58ff579e80f5889f68d19e


Make README.rst and LICENSE available to build-time tests. (Closes: #1050363)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1050363

Bug#1050439: Requires Sphinx >= v6.0 while unstable has v5.3

[Faidon Liambotis]

Source: furo
Version: 2023.08.19+dfsg-1
Severity: grave

furo 2023.08.19+dfsg-1 requires Sphinx v6.0:
  $ grep -r 'require_sphinx(' /usr/lib/python3/dist-packages/furo
  /usr/lib/python3/dist-packages/furo/__init__.py:app.require_sphinx("6.0")

However:
  $ rmadison -s unstable python3-sphinx
  python3-sphinx | 5.3.0-7   | unstable   | all

This makes furo unusable:
  $ python3 -m sphinx -N -bhtml docs/ build/html
  Running Sphinx v5.3.0
  making output directory... done
  
  Sphinx version error:
  The furo extension used by this project needs at least Sphinx v6.0; it 
therefore cannot be built with this version.

...and breaks unrelated packages build-depending on it. I encountered
this while trying to upload a new version of tox. I'd expect the same
for the 29 packages Build-Depending on furo.

I don't know what to do at this point -- it's perhaps worth checking
with the Sphinx maintainer to see if they intend to upload a newer
version of Sphinx in the coming (very few) days, as 7.1 is already
staged in experimental.

Otherwise, backing out the commits that require the version bump, or the
version altogether, ASAP seems necessary given the impact crater.

In any case, I'd strongly suggest adding some kind of test (either at
build-time, or autopkgtests, ideally both) to avoid this kind of thing
from accidentally happening again. We're humans and bound to miss
something like that over time, so adding safeguards seems prudent :)

Regards,
Faidon

Bug#1025552: marked as done (calamares: dependency on transitional policykit-1 package)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2023 15:34:24 +
with message-id 
and subject line Bug#1025552: fixed in calamares 3.3.0~alpha2-1
has caused the Debian Bug report #1025552,
regarding calamares: dependency on transitional policykit-1 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.)


-- 
1025552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025552
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: calamares
Version: 3.2.61-1
Severity: normal
User: pkg-utopia-maintain...@lists.alioth.debian.org
Usertags: policykit-1
Control: block 1025540 by -1

This package has a Depends and/or Build-Depends on the transitional
package policykit-1, which has been separated into polkitd, pkexec and
(deprecated) polkitd-pkla packages.

If this package communicates with polkitd via D-Bus, please represent that
as a Depends, Recommends or Suggests on polkitd, whichever is appropriate
for the strength of the requirement.

If this package runs /usr/bin/pkexec, please represent that as a Depends,
Recommends or Suggests on pkexec, whichever is appropriate for the strength
of the requirement.

If this package requires polkit at build-time (usually for the gettext
extensions polkit.its and polkit.loc), please build-depend on both
libpolkit-gobject-1-dev and polkitd, even if the package does not
actually depend on libpolkit-gobject-1 at runtime. This is because
the gettext extensions are currently in polkitd, but might be moved to
libpolkit-gobject-1-dev in future (see #955204). pkexec is usually not
required at build-time.

For packages that are expected to be backported to bullseye, it's OK to
use an alternative dependency: polkitd | policykit-1 and/or
pkexec | policykit-1.

This is part of a mass bug filing, see
.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: calamares
Source-Version: 3.3.0~alpha2-1
Done: Jonathan Carter 

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

Debian distribution maintenance software
pp.
Jonathan Carter  (supplier of updated calamares 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, 10 Jul 2023 21:37:16 +0200
Source: calamares
Architecture: source
Version: 3.3.0~alpha2-1
Distribution: unstable
Urgency: medium
Maintainer: Jonathan Carter 
Changed-By: Jonathan Carter 
Closes: 1025552
Changes:
 calamares (3.3.0~alpha2-1) unstable; urgency=medium
 .
   * Upload to unstable
   * Update standards version to 4.6.2
   * Replace policykit-1 dependency with pkexec (Closes: #1025552)
Checksums-Sha1:
 f71b491d4665861e28fd2c82f03b0cd24df748d7 2561 calamares_3.3.0~alpha2-1.dsc
 386a393d6baf1f797dbaf88a57fa6235fdae7a8e 4223898 
calamares_3.3.0~alpha2.orig.tar.gz
 d731b750830174292c4c192d38870b67e3ce07bb 8844 
calamares_3.3.0~alpha2-1.debian.tar.xz
 638fbac883edea446458ce1eb92f35e7ebdc04a0 21733 
calamares_3.3.0~alpha2-1_source.buildinfo
Checksums-Sha256:
 d6c369bac5bf45854ddf72449584e126b8a818622c67dd5d27926b3484195aa0 2561 
calamares_3.3.0~alpha2-1.dsc
 3f75583f3151bcdf869ea19efae07a6523e16b6b77c9e055a391d329d78ceb55 4223898 
calamares_3.3.0~alpha2.orig.tar.gz
 248586b65d9eb94c2413cd13af3f9b7cf67d4de06d432b5e0cb36deed6501cc8 8844 
calamares_3.3.0~alpha2-1.debian.tar.xz
 0872b3b59f912a9b83cd61ab15704a58eabe6a7ba7e27483483389a81101738e 21733 
calamares_3.3.0~alpha2-1_source.buildinfo
Files:
 a679487621589b96fadc4729eb11f133 2561 utils optional 
calamares_3.3.0~alpha2-1.dsc
 663490e960a4f2a47922deaf55630619 4223898 utils optional 
calamares_3.3.0~alpha2.orig.tar.gz
 dd5f342b3a815099f4af00696e198c98 8844 utils optional 
calamares_3.3.0~alpha2-1.debian.tar.xz
 f3a4d15124e83fe2570293a4ffc1fa87 21733 utils optional 
calamares_3.3.0~alpha2-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEExyA8CpIGcL+U8AuxsB0acqyNyaEFAmTnb0wPHGpjY0BkZWJp
YW4ub3JnAAoJELAdGnKsjcmhhGMQAKFY9Vq83EoBz+sNDNTlsCyIqKVyRqdvQAoB
hsaYaB1N5tGr/4zS/iBB5zWppHz3XyJOzvRiVAJ3Dv66O2bAptUmoGmt4BYSec9R

Bug#1050432: rpy2: FTBFS on mips64el

[Paul Gevers]

Hi Dirk, mips-porters,

On 24-08-2023 17:25, Dirk Eddelbuettel wrote:

Paul: While I have you here, and as all those failures are on _complex_, is
there a known issue with mips64el or a specific compiler switch that may be
needed?  rpy2 is fairly widely used but also 'glue' around other Python
libraries, are any others affected?


I don't know. I guess we should ask the mips* porters (done so by 
putting them in TO).


Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1050432: rpy2: FTBFS on mips64el

[Dirk Eddelbuettel]

Paul,

Thanks for the hint. I was aware and had been meaning to bring this up with
Laurent (upstream, now CCed).

Laurent: I should have access to a 'porterbox' running mips64el if you have
an idea about what may be going on here / have a branch to test.

Paul: While I have you here, and as all those failures are on _complex_, is
there a known issue with mips64el or a specific compiler switch that may be
needed?  rpy2 is fairly widely used but also 'glue' around other Python
libraries, are any others affected?

Dirk

On 24 August 2023 at 16:59, Paul Gevers wrote:
| Source: rpy2
| Version: 3.5.13-1
| Severity: serious
| Tags: ftbfs
| Justification: FTBFS
| 
| Dear maintainer,
| 
| Since the upload version 3.5.13-1, rpy2 has been failing to build on
| mips64el, which is blocking migration to testing.
| 
| https://buildd.debian.org/status/logs.php?pkg=rpy2=mips64el
| 
| === short test summary info 

| FAILED rpy2/tests/rinterface/test_na.py::test_R_to_NAComplex - assert False
| FAILED rpy2/tests/rinterface/test_vector_complex.py::test_init_from_seqr - 
as...
| FAILED rpy2/tests/rinterface/test_vector_complex.py::test_getitem - assert 
(-...
| FAILED rpy2/tests/rinterface/test_vector_complex.py::test_setitem - assert 
(-...
| FAILED rpy2/tests/rinterface/test_vector_complex.py::test_getslice - assert 
(...
| FAILED rpy2/tests/rinterface/test_vector_complex.py::test_getslice_negative
| FAILED rpy2/tests/rinterface/test_vector_complex.py::test_setslice - assert 
(...
| FAILED rpy2/tests/rinterface/test_vector_complex.py::test_setslice_negative
| FAILED rpy2/tests/rinterface/test_vector_complex.py::test_index - 
ValueError:...
| FAILED 
rpy2/tests/robjects/test_conversion_numpy.py::TestNumpyConversions::test_vector_complex
| 
| Paul
| 
| -- System Information: Debian Release: trixie/sid APT prefers testing
| APT policy: (990, 'testing') Architecture: amd64 (x86_64)
| 
| Kernel: Linux 6.4.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
| Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
| Shell: /bin/sh linked to /usr/bin/dash
| Init: systemd (via /run/systemd/system)
| LSM: AppArmor: enabled

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1050436: upower: autopkgtest regression on i386: excessive precision?

[Paul Gevers]

Source: upower 1.90.2-4
Severity: serious
Tags: sid trixie
X-Debbugs-CC: b...@debian.org
User: debian...@lists.debian.org
Usertags: regression
Control: affects -1 src:libgudev

Dear maintainer(s),

With a recent upload of upower, the autopkgtest of upower fails on i386 
in testing when that autopkgtest is run with the binary packages of 
upower and libgudev from unstable. It passes when run with only packages 
from testing. In tabular form:


   passfail
libgudev   from testing238-2
upower from testing1.90.2-4
all others from testingfrom testing

I copied some of the output at the bottom of this report. Looking at the 
error this *seems* to me the result of the excessive precision of i386, 
but I hope the i386 porter (in XDCC) can shed his light on that too.


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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/i386/u/upower/37102682/log.gz

208s ==
208s FAIL: test_battery_energy_charge_mixed 
(__main__.Tests.test_battery_energy_charge_mixed)

208s battery which reports both current charge and energy
208s --
208s Traceback (most recent call last):
208s   File "/usr/libexec/upower/integration-test.py", line 887, in 
test_battery_energy_charge_mixed
208s self.assertEqual(self.get_dbus_dev_property(bat0_up, 
'Percentage'), 40.0)

208s AssertionError: 40.01 != 40.0


OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: upower: autopkgtest regression on i386: excessive precision?

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:libgudev
Bug #1050436 [src:upower 1.90.2-4] upower: autopkgtest regression on i386: 
excessive precision?
Warning: Unknown package '1.90.2-4'
Added indication that 1050436 affects src:libgudev
Warning: Unknown package '1.90.2-4'

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

Processed: src:r-cran-stars: fails to migrate to testing for too long: autopkgtest regression

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.6-2-1
Bug #1050434 [src:r-cran-stars] src:r-cran-stars: fails to migrate to testing 
for too long: autopkgtest regression
Marked as fixed in versions r-cran-stars/0.6-2-1.
Bug #1050434 [src:r-cran-stars] src:r-cran-stars: fails to migrate to testing 
for too long: autopkgtest regression
Marked Bug as done

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

Processed: Re: Bug#1050431: binutils-mipsen: FTBFS on all architectures

[Debian Bug Tracking System]

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

> block 1050431 by 1049455
Bug #1050431 [src:binutils-mipsen] binutils-mipsen: FTBFS on all architectures
1050431 was not blocked by any bugs.
1050431 was blocking: 1040626
Added blocking bug(s) of 1050431: 1049455
> thanks
Stopping processing here.

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

Bug#1050434: src:r-cran-stars: fails to migrate to testing for too long: autopkgtest regression

[Paul Gevers]

Source: r-cran-stars
Version: 0.6-1-1
Severity: serious
Control: close -1 0.6-2-1
Tags: sid trixie
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 30 days as having a Release Critical bug in 
testing [1]. Your package src:r-cran-stars has been trying to migrate 
for 34 days [2]. Hence, I am filing this bug. The version in unstable 
fails its own autopkgtest.


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


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


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=r-cran-stars



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:sqlgrey: fails to migrate to testing for too long

[Debian Bug Tracking System]

Processing control commands:

> close -1 1:1.8.0-5
Bug #1050433 [src:sqlgrey] src:sqlgrey: fails to migrate to testing for too long
Marked as fixed in versions sqlgrey/1:1.8.0-5.
Bug #1050433 [src:sqlgrey] src:sqlgrey: fails to migrate to testing for too long
Marked Bug as done

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

Bug#1050433: src:sqlgrey: fails to migrate to testing for too long

[Paul Gevers]

Source: sqlgrey
Version: 1:1.8.0-4
Severity: serious
Control: close -1 1:1.8.0-5
Tags: sid trixie pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

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


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


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


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=sqlgrey



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1050432: rpy2: FTBFS on mips64el

[Paul Gevers]

Source: rpy2
Version: 3.5.13-1
Severity: serious
Tags: ftbfs
Justification: FTBFS

Dear maintainer,

Since the upload version 3.5.13-1, rpy2 has been failing to build on
mips64el, which is blocking migration to testing.

https://buildd.debian.org/status/logs.php?pkg=rpy2=mips64el

=== short test summary info 
FAILED rpy2/tests/rinterface/test_na.py::test_R_to_NAComplex - assert False
FAILED rpy2/tests/rinterface/test_vector_complex.py::test_init_from_seqr - as...
FAILED rpy2/tests/rinterface/test_vector_complex.py::test_getitem - assert (-...
FAILED rpy2/tests/rinterface/test_vector_complex.py::test_setitem - assert (-...
FAILED rpy2/tests/rinterface/test_vector_complex.py::test_getslice - assert (...
FAILED rpy2/tests/rinterface/test_vector_complex.py::test_getslice_negative
FAILED rpy2/tests/rinterface/test_vector_complex.py::test_setslice - assert (...
FAILED rpy2/tests/rinterface/test_vector_complex.py::test_setslice_negative
FAILED rpy2/tests/rinterface/test_vector_complex.py::test_index - ValueError:...
FAILED 
rpy2/tests/robjects/test_conversion_numpy.py::TestNumpyConversions::test_vector_complex

Paul

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

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

Bug#1050431: binutils-mipsen: FTBFS on all architectures

[YunQiang Su]

Paul Gevers  于2023年8月24日周四 22:51写道：
>
> Source: binutils-mipsen
> Version: 10+c4
> Severity: serious
> Tags: ftbfs
> Justification: FTBFS
> Control: block 1040626 by -1
>
> Dear maintainer,
>
> The latest upload of binutils-mipsen failed to build from source on
> all architectures. Apart from this being an issue by itself, it's also
> blocking progress in other RC bugs.
>
> https://buildd.debian.org/status/package.php?p=binutils-mipsen=10

It is blocked by
#1049455 - Binutils: mips-gold patch was refreshed incorrectly
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049455

I am also working on it upstream:
[PATCH v3 1/2] Gold/MIPS: Improve MIPS support in configure.tgt (sourceware.org)
https://sourceware.org/pipermail/binutils/2023-August/129118.html

>
> Paul
>
> -- System Information:
> Debian Release: trixie/sid
>   APT prefers testing
>   APT policy: (990, 'testing')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 6.4.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_US:en
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled



-- 
YunQiang Su

Bug#1040521: tpm2-tss: FTBFS (test failures)

[Paul Gevers]

Hi Paul,

On Sun, 6 Aug 2023 05:59:48 +0800 "Ying-Chun Liu (PaulLiu)" 
 wrote:

But there are 3 more test that needed to be fixed.
1. test/unit/fapi-eventlog
2. test/unit/tcti-spi-helper
3. test/unit/fapi-ima-eventlog

I'll find some time to fix the rest of the failure and do a single upload that fixes every s390x 
test failure.


If you think (or have reason to hope) that the issue is *only* in the 
tests itself (and the built binaries might actually be OK), than it's 
also an option to *temporarily* disable these tests on big endian systems.


Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: binutils-mipsen: FTBFS on all architectures

[Debian Bug Tracking System]

Processing control commands:

> block 1040626 by -1
Bug #1040626 [src:gcc-13-cross-mipsen] gcc-13-cross-mipsen ftbfs in unstable
1040626 was not blocked by any bugs.
1040626 was not blocking any bugs.
Added blocking bug(s) of 1040626: 1050431

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

Bug#1050431: binutils-mipsen: FTBFS on all architectures

[Paul Gevers]

Source: binutils-mipsen
Version: 10+c4
Severity: serious
Tags: ftbfs
Justification: FTBFS
Control: block 1040626 by -1

Dear maintainer,

The latest upload of binutils-mipsen failed to build from source on
all architectures. Apart from this being an issue by itself, it's also
blocking progress in other RC bugs.

https://buildd.debian.org/status/package.php?p=binutils-mipsen=10

Paul

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

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

Bug#1037867: marked as done (stressapptest: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2023 14:44:19 +
with message-id 
and subject line Bug#1037867: fixed in stressapptest 1.0.9-1
has caused the Debian Bug report #1037867,
regarding stressapptest: ftbfs with GCC-13
to be marked as done.

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

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


-- 
1037867: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037867
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:stressapptest
Version: 1.0.6-2.2
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

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

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/stressapptest_1.0.6-2.2_unstable_gccexp.log
The last lines of the build log are at the end of this report.

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

[...]
checking for strtoull... yes
checking for mmap64... yes
checking for posix_memalign... yes
checking for rand_r... yes
checking for sched_getaffinity... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating src/stressapptest_config.h
config.status: executing depfiles commands
   dh_auto_build
dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 9 
in use)
make -j1
make[1]: Entering directory '/<>'
Making all in src
make[2]: Entering directory '/<>/src'
make  all-am
make[3]: Entering directory '/<>/src'
g++ -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DCHECKOPTS -Wreturn-type -Wunused -Wuninitialized 
-Wall -Wno-psabi -O3 -funroll-all-loops  -funroll-loops -DNDEBUG -c -o main.o 
main.cc
g++ -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DCHECKOPTS -Wreturn-type -Wunused -Wuninitialized 
-Wall -Wno-psabi -O3 -funroll-all-loops  -funroll-loops -DNDEBUG -c -o os.o 
os.cc
os.cc: In member function ‘virtual uint64 OsLayer::VirtualToPhysical(void*)’:
os.cc:133:19: error: ‘uintptr_t’ was not declared in this scope
  133 |   off64_t off = ((uintptr_t)vaddr) / getpagesize() * 8;
  |   ^
os.cc:51:1: note: ‘std::uintptr_t’ is defined in header ‘’; did you 
forget to ‘#include ’?
   50 | #include "error_diag.h"
  +++ |+#include 
   51 | 
os.cc:133:29: error: expected ‘)’ before ‘vaddr’
  133 |   off64_t off = ((uintptr_t)vaddr) / getpagesize() * 8;
  | ~   ^
  | )
os.cc:153:30: error: expected ‘)’ before ‘vaddr’
  153 |   return frame | ((uintptr_t)vaddr & ((1LL << shift) - 1));
  |  ~   ^
  |  )
os.cc: In member function ‘virtual bool OsLayer::AllocateTestMem(int64, 
uint64)’:
os.cc:509:36: warning: passing NULL to non-pointer argument 3 of ‘void* 
shmat(int, const void*, int)’ [-Wconversion-null]
  509 |   shmaddr = shmat(shmid, NULL, NULL);
  |^~~~
In file included from os.cc:36:
/usr/include/x86_64-linux-gnu/sys/shm.h:65:61: note:   declared here
   65 | extern void *shmat (int __shmid, const void *__shmaddr, int __shmflg)
  | ^~~~
os.cc:566:38: warning: passing NULL to non-pointer argument 6 of ‘void* 
mmap64(void*, size_t, int, int, int, __off64_t)’ [-Wconversion-null]
  566 |  shm_object, NULL);
  |  ^~~~
In file included from os.cc:30:

Bug#1038865: accountsservice FTBFS: FAIL: test_languages (__main__.Tests.test_languages)

[Paul Gevers]

Hi,

On Thu, 22 Jun 2023 11:47:53 +0300 Adrian Bunk  wrote:

https://buildd.debian.org/status/logs.php?pkg=accountsservice=23.13.9-1
(m68k and sh4 are building with nocheck)


I don't particularly like pinging bugs, but this issue is blocking 
progress. Unfortunately accountsservice is a key package so can't easily 
be removed from testing.


I note that the package in Ubuntu seems to have received two more 
uploads on top of the version in unstable. Maybe a patch is to be found 
in their changes.


Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: Reassign and raise severity

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 pronterface
Bug #1050157 [printrun] printrun: broken 3D view due to pyglet 2+
Bug reassigned from package 'printrun' to 'pronterface'.
No longer marked as found in versions printrun/2.0.1-1.
Ignoring request to alter fixed versions of bug #1050157 to the same values 
previously set
> affects -1 plater
Bug #1050157 [pronterface] printrun: broken 3D view due to pyglet 2+
Added indication that 1050157 affects plater
> severity -1 serious
Bug #1050157 [pronterface] printrun: broken 3D view due to pyglet 2+
Severity set to 'serious' from 'important'
> forwarded -1 https://github.com/kliment/Printrun/issues/1291
Bug #1050157 [pronterface] printrun: broken 3D view due to pyglet 2+
Set Bug forwarded-to-address to 
'https://github.com/kliment/Printrun/issues/1291'.
> tags 1050166 - moreinfo
Bug #1050166 [release.debian.org] RM: printrun/2.0.1-1
Removed tag(s) moreinfo.

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

Processed: musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL'

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:mksh
Bug #1050429 [musl-tools] musl: unusable on mipsel, mips64el: 
mipsel-linux-gnu-gcc: unrecognised command-line option '-EL'
Added indication that 1050429 affects src:mksh

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

Bug#1050429: musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL'

[Thorsten Glaser]

Package: musl-tools
Version: 1.2.3-1
Severity: serious
Justification: unusable on release architectures
X-Debbugs-Cc: t...@mirbsd.de, debian-...@lists.debian.org
Control: affects -1 src:mksh

Unsure if it’s musl or gcc-13_13.2.0-2 but building a simple
test program fails on both mips64el and mipsel:

$ musl-gcc […] -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -static  conftest.c
mipsel-linux-gnu-gcc: error: unrecognized command-line option '-EL'

If doing 'gcc -v' (normal gcc, not musl-gcc wrapper) the -EL shows up in:

COLLECT_GCC_OPTIONS='-g' '-O2' '-ffile-prefix-map=/<>=.' 
'-fstack-protector-strong' '-Wformat=1' '-Werror=format-security' '-Wall' 
'-Wextra' '-I' '.' '-I' '../..' '-Wdate-time' '-D' '_FORTIFY_SOURCE=2' '-D' 
'MKSH_EARLY_LOCALE_TRACKING' '-D' 'KSH_VERSIONNAME_VENDOR_EXT=" +Debian"' '-D' 
'MKSH_BUILDMEAT' '-D' 'MKSH_BUILDSH=1' '-D' '_GNU_SOURCE' '-D' 
'SETUID_CAN_FAIL_WITH_EAGAIN=1' '-v' '-march=mips32r2' '-mfpxx' '-mllsc' 
'-mno-lxc1-sxc1' '-mno-madd4' '-mips32r2' '-EL' '-mabi=32' '-dumpdir' 'a-'

musl-gcc uses mipsel-linux-gnu-gcc (or mips64el-linux-gnuabi64-gcc)
instead of gcc, but it’s still Debian 13.2.0-2 according to --version.

Processed: 1037867 forwarded

[Debian Bug Tracking System]

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

> forwarded 1037867 https://github.com/stressapptest/stressapptest/pull/112
Bug #1037867 [src:stressapptest] stressapptest: ftbfs with GCC-13
Set Bug forwarded-to-address to 
'https://github.com/stressapptest/stressapptest/pull/112'.
> tag 1037867 upstream
Bug #1037867 [src:stressapptest] stressapptest: ftbfs with GCC-13
Added tag(s) upstream.
>
End of message, stopping processing here.

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

Bug#1042889: vm: autopkgtest fails against Emacs 29.1

[Sean Whitton]

Hello,

On Mon 14 Aug 2023 at 10:47am +01, Ian Jackson wrote:

> Sean Whitton writes ("Bug#1042889: vm: autopkgtest fails against Emacs 29.1"):
>> vm's autopkgtest fails with Emacs 29.1, which latter is now in sid.
>>
>> https://ci.debian.net/packages/v/vm/testing/amd64/
>
> The regression was indeed caused solely by upstream renaming the
> variable that disables byte compilation, from
> native-comp-deferred-compilation-deny-list
> to
> native-comp-jit-compilation-deny-list
>
> ISTM that making that change without also honouring the old setting
> was an obviously bad idea.  Upstream set us up for this failure.
> Anyway, I have fixed this issue in vm, by handling both variables.
> I expect the new vm package to migrate quickly.

Usually there's an alias added when variable names are obsoleted.

Thank you for the fix.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Processed: progress-linux-gnome-desktop: Unsatisfiable dependencies after GNOME Shell 44 transition

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 1041575
Bug #1050424 [progress-linux-gnome-desktop] progress-linux-gnome-desktop: 
Unsatisfiable dependencies after GNOME Shell 44 transition
1050424 was not blocked by any bugs.
1050424 was not blocking any bugs.
Added blocking bug(s) of 1050424: 1041575
> block -1 by 1050421
Bug #1050424 [progress-linux-gnome-desktop] progress-linux-gnome-desktop: 
Unsatisfiable dependencies after GNOME Shell 44 transition
1050424 was blocked by: 1041575
1050424 was not blocking any bugs.
Added blocking bug(s) of 1050424: 1050421

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

Bug#1050424: progress-linux-gnome-desktop: Unsatisfiable dependencies after GNOME Shell 44 transition

[Jeremy Bícha]

Package: progress-linux-gnome-desktop
Severity: serious
Version: 20221002-9
Tags: trixie sid
Control: block -1 by 1041575
Control: block -1 by 1050421

progress-linux-gnome-desktop depends on
gnome-shell-extension-impatience and
gnome-shell-extension-no-annoyance but those extensions, as packaged
in Debian, are not compatible with GNOME Shell 44 and will be removed
from Testing.

That means that progress-linux-metapackages will be unable to migrate
to Testing until it drops those dependencies or the extensions are
made compatible with GNOME Shell 44.

Thank you,
Jeremy Bícha

Processed: Re: bfh-gnome-desktop: Unsatisfiable dependencies after GNOME Shell 44 transition

[Debian Bug Tracking System]

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

> block 1050422 by 1041575
Bug #1050422 [bfh-gnome-desktop] bfh-gnome-desktop: Unsatisfiable dependencies 
after GNOME Shell 44 transition
1050422 was blocked by: 1050421
1050422 was not blocking any bugs.
Added blocking bug(s) of 1050422: 1041575
>
End of message, stopping processing here.

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

Bug#1050313: kde-spectacle: crash because of missing dependencies

[Lisandro Damián Nicanor Pérez Meyer]

El martes, 22 de agosto de 2023 20:34:09 -03 Alexandre Detiste escribió:
> Package: kde-spectacle
> Version: 23.04.2-2
> Severity: important
> 
> 
> specatecle needs "libqt5quickshapes5" & "qml-module-qtquick-shapes" installed.
> 
> without these it will crash:

This boils down to only the QML module.



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

Processed (with 1 error): bfh-gnome-desktop: Unsatisfiable dependencies after GNOME Shell 44 transition

[Debian Bug Tracking System]

Processing control commands:

> blocks -1 by 1041575
Unknown command or malformed arguments to command.

> block -1 by 1050421
Bug #1050422 [bfh-gnome-desktop] bfh-gnome-desktop: Unsatisfiable dependencies 
after GNOME Shell 44 transition
1050422 was not blocked by any bugs.
1050422 was not blocking any bugs.
Added blocking bug(s) of 1050422: 1050421

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

Bug#1050422: bfh-gnome-desktop: Unsatisfiable dependencies after GNOME Shell 44 transition

[Jeremy Bícha]

Package: bfh-gnome-desktop
Severity: serious
Version: 20211009-20
Tags: trixie sid
Control: blocks -1 by 1041575
Control: block -1 by 1050421

bfh-gnome-desktop depends on gnome-shell-extension-impatience and
gnome-shell-extension-no-annoyance but those extensions, as packaged
in Debian, are not compatible with GNOME Shell 44 and will be removed
from Testing.

That means that bfh-metapackages will also be removed from Testing
until it drops those dependencies or the extensions are made
compatible with GNOME Shell 44.

Thank you,
Jeremy Bícha

Bug#1050421: gnome-shell-extension-no-annoyance: needs update for GNOME Shell 44

[Jeremy Bícha]

Package: gnome-shell-extension-no-annoyance
Version: 0+20220925-c6804a4-3
Severity: serious
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-44
Control: forwarded -1 https://github.com/sindex/no-annoyance/issues/11

This extension has not been checked for compatibility with GNOME Shell
44. Depending how compatible it is, it will either need an update to
its metadata.json and debian/control to declare compatibility with the
new version, or code changes to adapt it to the new Shell version.

Because GNOME Shell 44 is migrating to Testing, this extension will
have to be removed from testing for the GNOME Shell 44 transition now.

Please see the upstream bug report which suggests a possible path
forward for this extension.

Also, please do like other GNOME Shell extensions and add strict upper
and lower Depends against gnome-shell versions the package is
compatible with according to its metadata.json. That would allow users
to automatically see that installing a new GNOME Shell version
(perhaps from experimental) would break their packaged extensions that
aren't yet compatible. For instance, this matches the current
metadata.json:

gnome-shell (>= 40~),
gnome-shell (<< 44~),

Thank you,
Jeremy Bícha

Processed: gnome-shell-extension-no-annoyance: needs update for GNOME Shell 44

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/sindex/no-annoyance/issues/11
Bug #1050421 [gnome-shell-extension-no-annoyance] 
gnome-shell-extension-no-annoyance: needs update for GNOME Shell 44
Set Bug forwarded-to-address to 
'https://github.com/sindex/no-annoyance/issues/11'.

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

Bug#992341: marked as done (bird2: does not properly take over from bird package)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2023 13:46:10 +0200
with message-id 
and subject line Bug#992341
has caused the Debian Bug report #992341,
regarding bird2: does not properly take over from bird 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.)


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

Package: bird2
Severity: important
Version: 2.0.4-1

Hi,

When bird2 supersedes bird it does not properly take over the 
configuration file /etc/bird/bird.conf in ucf. When the bird package is 
purged, it results in the following situation:


# aptitude search '~c'
c   bird - Internet Routing Daemon 



# apt policy bird bird2
bird:
  Installed: (none)
  Candidate: 1.6.8-2.1
  Version table:
 1.6.8-2.1 500
500 http://mirror.bytemark.co.uk/debian bullseye/main amd64 
Packages

 1.6.6-1+deb10u1 -1
100 /var/lib/dpkg/status
bird2:
  Installed: 2.0.7-4.1
  Candidate: 2.0.7-4.1
  Version table:
 *** 2.0.7-4.1 500
500 http://mirror.bytemark.co.uk/debian bullseye/main amd64 
Packages

100 /var/lib/dpkg/status
# apt purge bird
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
  bird*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
(Reading database ... 86367 files and directories currently installed.)
Purging configuration files for bird (1.6.6-1+deb10u1) ...
ucfr: Association belongs to bird2, not bird
ucfr: Aborting
dpkg: error processing package bird (--purge):
 installed bird package post-removal script subprocess returned error 
exit status 5

Errors were encountered while processing:
 bird
E: Sub-process /usr/bin/dpkg returned an error code (1)

But the postrm for bird has already removed the configuration file:

# ls /etc/bird/
envvars  local.conf

so now bird2 fails to start and the configuration is lost (yay backups).


--
Jonathan Wiltshire

Red Hat Certified Engineer (#170-281-083)

Tiger Computing Ltd
ISO27001:2017 Certified

Tel: 01600 483 484
Web: http://www.tiger-computing.co.uk

Registered in England. Company number: 3389961
Registered address: Woodlands, Staunton,
 Coleford, GL16 8NU
--- End Message ---
--- Begin Message ---

Version: 2.0.7-4.1


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

Processed: Re: Bug#1042246: gdcm: FTBFS: make[1]: *** [debian/rules:107: override_dh_auto_configure] Error 2

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1042246 [src:gdcm] gdcm: FTBFS: make[1]: *** [debian/rules:107: 
override_dh_auto_configure] Error 2
Added tag(s) patch.

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

Bug#1042246: gdcm: FTBFS: make[1]: *** [debian/rules:107: override_dh_auto_configure] Error 2

[Mathieu Malaterre]

Control: tags -1 patch

On Wed, Jul 26, 2023 at 10:30 PM Lucas Nussbaum  wrote:
 [...]
> > CMake Error at 
> > /usr/share/cmake-3.27/Modules/FindPackageHandleStandardArgs.cmake:230 
> > (message):
> >   Could NOT find EXPAT (missing: EXPAT_LIBRARY) (found version "2.5.0")
> > Call Stack (most recent call first):

I'll upload a quick hack ASAP (*). But there is something
fundamentally wrong with the find_package + expat mechanism. Possibly
in cmake itself...

2cts

(*)
% git diff
diff --git a/debian/rules b/debian/rules
index 32ab32e..bfb08fc 100755
--- a/debian/rules
+++ b/debian/rules
@@ -77,6 +77,7 @@ CMAKE_EXTRA_FLAGS += -DCMAKE_SKIP_RPATH=ON \
-DGDCM_USE_PVRG:BOOL=ON \
-DGDCM_USE_SYSTEM_PVRG:BOOL=ON \
-DGMCS_EXECUTABLE:FILEPATH=/usr/bin/mono-csc \
+
-DEXPAT_LIBRARY:FILEPATH=/usr/lib/$(DEB_HOST_MULTIARCH)/libexpat.so \
-DGDCM_BUILD_TESTING:BOOL=OFF \
-DGDCM_USE_SYSTEM_EXPAT:BOOL=ON \
-DGDCM_USE_SYSTEM_UUID:BOOL=ON \

Bug#1033100: marked as done (Please update gnome-shell-extension-dashtodock to 79)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2023 10:50:29 +
with message-id 
and subject line Bug#1041568: fixed in gnome-shell-extension-dashtodock 87-1
has caused the Debian Bug report #1041568,
regarding Please update gnome-shell-extension-dashtodock to 79
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.)


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

Package: gnome-shell-extension-dashtodock

Hello,

Please update gnome-shell-extension-dashtodock to 79.

I also sent a pull request upstream to update the German translation 
after the 79 release.


https://github.com/micheleg/dash-to-dock/pull/1963

If possible, please cherry-pick that commit to Debian with the 79 release.

Best,
Amr
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-dashtodock
Source-Version: 87-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 1041...@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: Thu, 24 Aug 2023 12:30:21 +0200
Source: gnome-shell-extension-dashtodock
Architecture: source
Version: 87-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jonathan Carter 
Closes: 1033100 1041568
Changes:
 gnome-shell-extension-dashtodock (87-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #1033100, #1041568)
   * Update gnome-shell dependency to include gnome-shell 45
   * OVerride tests that seem a bit flaky
Checksums-Sha1:
 00dfb8756a944a770dea7c2384c837d46ef161de 2312 
gnome-shell-extension-dashtodock_87-1.dsc
 0ff26a5a8a2d96099f2b19d8d1a841bf702ea97f 328086 
gnome-shell-extension-dashtodock_87.orig.tar.gz
 8c780cae36ea90fa41a2f0ec7c98e57883451914 4792 
gnome-shell-extension-dashtodock_87-1.debian.tar.xz
 ec1e1e07b9527089b18d6e06785f8ed7924d7495 5837 
gnome-shell-extension-dashtodock_87-1_source.buildinfo
Checksums-Sha256:
 5f59ce05d17cb924d92d3da7b40f048d6fb67c5181e8e8a1abf1b53a4b4e2926 2312 
gnome-shell-extension-dashtodock_87-1.dsc
 67948c005ec0024d9953115240f44528771e594f6541b36c24a18f87947c0615 328086 
gnome-shell-extension-dashtodock_87.orig.tar.gz
 65dc1a3872b3b95ac8f03475d1ee4cd410951a715b5e0bf082ae9158fb0538d9 4792 
gnome-shell-extension-dashtodock_87-1.debian.tar.xz
 74f7b4377ba64eb1d85660c14644675f60d2a286cdce345c42ad0bffbc2434dd 5837 
gnome-shell-extension-dashtodock_87-1_source.buildinfo
Files:
 6c837fc518f7ff099c86f1729a070c15 2312 gnome optional 
gnome-shell-extension-dashtodock_87-1.dsc
 013926872f556de9d1e5e49f5ea2581e 328086 gnome optional 
gnome-shell-extension-dashtodock_87.orig.tar.gz
 ae513fa88eb09de71c76129b768409e9 4792 gnome optional 
gnome-shell-extension-dashtodock_87-1.debian.tar.xz
 ae54a89e63b7a5e02729f4f0dd473df3 5837 gnome optional 
gnome-shell-extension-dashtodock_87-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEExyA8CpIGcL+U8AuxsB0acqyNyaEFAmTnMr8SHGpjYXJ0ZXJA
bGludXguY29tAAoJELAdGnKsjcmhAxcP/jlcyALEdiJtiF0GxGZDTdLcLoDZwE+f
54sIP3FLN7/IgeQ4VA6O9XCLImFVuhPYI6xITk1xwO+sCqcytxBBfeCVE4MTS4Px
hAQf1wvUkNbjPqw4PkWCPSUv9UvzXD2JLQ/1PcTSQxHAmclaFjz7/Ppq0awYPhCX
PY7bDnh0rRdON+muogr5XCeAgGwrMttScvth5O7ZKN1d3QrCtJVe7qsj8hl1upN1
AkL+XGyZ+FYm+R2LsoJFSvFI53x/iERsgiM12XspsuA75qd4WYLZ8wrgluZF2v/3
oNn1hpFVWsUuAoJcS13C4xzG7AtCfI3jLS4jibcokaA1n76d+ys/E1RTTeDuQGaH
i/48F+JD6TmRnqG+KRm9r3DUZCp7sq60GK+ZAMqrARcIVQ5R8N2VoMZFd2t3RrAR
uvlX+JU5JdTQUOG14yfq9jq++fKoJn9pAxQLILalbYsK5YfDDWOO2rU4TAiKzxC5
dJttpiMAjJfjWATir1lZev+kyZWKo6LThJBhuwNCkfmnrILuaUS7XjPcl07jhSQI
bI8ygtmXrbRuWA9NZFOjjAppshAIUH5QYDnmRGqgUAvg4HqFxnskjy/vcsh/2J9J
/0c9BD8yXpYnP/9FRTYiW2rc0MLMJidLBjHOZb4Zqo5eUL+xMva8nK+PTFtryO/T
Kda+vEcOE6Ji
=S5ez
-END PGP SIGNATURE End Message ---

Bug#1041568: marked as done (gnome-shell-extension-dashtodock: needs update for GNOME Shell 44)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2023 10:50:29 +
with message-id 
and subject line Bug#1041568: fixed in gnome-shell-extension-dashtodock 87-1
has caused the Debian Bug report #1041568,
regarding gnome-shell-extension-dashtodock: needs update for GNOME Shell 44
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.)


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

This extension has not been checked for compatibility with GNOME Shell
44. Depending how compatible it is, it will either need an update to
its metadata.json and debian/control to declare compatibility with the
new version, or code changes to adapt it to the new Shell version.

If not updated, it will have to be removed from testing for the GNOME
Shell 44 transition (I don't know when that will be). This bug will be
raised to serious severity when the transition is ready to go ahead.

If a new upstream version is compatible with Shell 44 but not 43,
please upload to experimental for now.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-dashtodock
Source-Version: 87-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 1041...@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: Thu, 24 Aug 2023 12:30:21 +0200
Source: gnome-shell-extension-dashtodock
Architecture: source
Version: 87-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jonathan Carter 
Closes: 1033100 1041568
Changes:
 gnome-shell-extension-dashtodock (87-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #1033100, #1041568)
   * Update gnome-shell dependency to include gnome-shell 45
   * OVerride tests that seem a bit flaky
Checksums-Sha1:
 00dfb8756a944a770dea7c2384c837d46ef161de 2312 
gnome-shell-extension-dashtodock_87-1.dsc
 0ff26a5a8a2d96099f2b19d8d1a841bf702ea97f 328086 
gnome-shell-extension-dashtodock_87.orig.tar.gz
 8c780cae36ea90fa41a2f0ec7c98e57883451914 4792 
gnome-shell-extension-dashtodock_87-1.debian.tar.xz
 ec1e1e07b9527089b18d6e06785f8ed7924d7495 5837 
gnome-shell-extension-dashtodock_87-1_source.buildinfo
Checksums-Sha256:
 5f59ce05d17cb924d92d3da7b40f048d6fb67c5181e8e8a1abf1b53a4b4e2926 2312 
gnome-shell-extension-dashtodock_87-1.dsc
 67948c005ec0024d9953115240f44528771e594f6541b36c24a18f87947c0615 328086 
gnome-shell-extension-dashtodock_87.orig.tar.gz
 65dc1a3872b3b95ac8f03475d1ee4cd410951a715b5e0bf082ae9158fb0538d9 4792 
gnome-shell-extension-dashtodock_87-1.debian.tar.xz
 74f7b4377ba64eb1d85660c14644675f60d2a286cdce345c42ad0bffbc2434dd 5837 
gnome-shell-extension-dashtodock_87-1_source.buildinfo
Files:
 6c837fc518f7ff099c86f1729a070c15 2312 gnome optional 
gnome-shell-extension-dashtodock_87-1.dsc
 013926872f556de9d1e5e49f5ea2581e 328086 gnome optional 
gnome-shell-extension-dashtodock_87.orig.tar.gz
 ae513fa88eb09de71c76129b768409e9 4792 gnome optional 
gnome-shell-extension-dashtodock_87-1.debian.tar.xz
 ae54a89e63b7a5e02729f4f0dd473df3 5837 gnome optional 
gnome-shell-extension-dashtodock_87-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEExyA8CpIGcL+U8AuxsB0acqyNyaEFAmTnMr8SHGpjYXJ0ZXJA
bGludXguY29tAAoJELAdGnKsjcmhAxcP/jlcyALEdiJtiF0GxGZDTdLcLoDZwE+f
54sIP3FLN7/IgeQ4VA6O9XCLImFVuhPYI6xITk1xwO+sCqcytxBBfeCVE4MTS4Px
hAQf1wvUkNbjPqw4PkWCPSUv9UvzXD2JLQ/1PcTSQxHAmclaFjz7/Ppq0awYPhCX
PY7bDnh0rRdON+muogr5XCeAgGwrMttScvth5O7ZKN1d3QrCtJVe7qsj8hl1upN1
AkL+XGyZ+FYm+R2LsoJFSvFI53x/iERsgiM12XspsuA75qd4WYLZ8wrgluZF2v/3
oNn1hpFVWsUuAoJcS13C4xzG7AtCfI3jLS4jibcokaA1n76d+ys/E1RTTeDuQGaH
i/48F+JD6TmRnqG+KRm9r3DUZCp7sq60GK+ZAMqrARcIVQ5R8N2VoMZFd2t3RrAR

Bug#1033100: marked as done (Please update gnome-shell-extension-dashtodock to 79)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2023 10:50:29 +
with message-id 
and subject line Bug#1033100: fixed in gnome-shell-extension-dashtodock 87-1
has caused the Debian Bug report #1033100,
regarding Please update gnome-shell-extension-dashtodock to 79
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.)


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

Package: gnome-shell-extension-dashtodock

Hello,

Please update gnome-shell-extension-dashtodock to 79.

I also sent a pull request upstream to update the German translation 
after the 79 release.


https://github.com/micheleg/dash-to-dock/pull/1963

If possible, please cherry-pick that commit to Debian with the 79 release.

Best,
Amr
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-dashtodock
Source-Version: 87-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 1033...@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: Thu, 24 Aug 2023 12:30:21 +0200
Source: gnome-shell-extension-dashtodock
Architecture: source
Version: 87-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jonathan Carter 
Closes: 1033100 1041568
Changes:
 gnome-shell-extension-dashtodock (87-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #1033100, #1041568)
   * Update gnome-shell dependency to include gnome-shell 45
   * OVerride tests that seem a bit flaky
Checksums-Sha1:
 00dfb8756a944a770dea7c2384c837d46ef161de 2312 
gnome-shell-extension-dashtodock_87-1.dsc
 0ff26a5a8a2d96099f2b19d8d1a841bf702ea97f 328086 
gnome-shell-extension-dashtodock_87.orig.tar.gz
 8c780cae36ea90fa41a2f0ec7c98e57883451914 4792 
gnome-shell-extension-dashtodock_87-1.debian.tar.xz
 ec1e1e07b9527089b18d6e06785f8ed7924d7495 5837 
gnome-shell-extension-dashtodock_87-1_source.buildinfo
Checksums-Sha256:
 5f59ce05d17cb924d92d3da7b40f048d6fb67c5181e8e8a1abf1b53a4b4e2926 2312 
gnome-shell-extension-dashtodock_87-1.dsc
 67948c005ec0024d9953115240f44528771e594f6541b36c24a18f87947c0615 328086 
gnome-shell-extension-dashtodock_87.orig.tar.gz
 65dc1a3872b3b95ac8f03475d1ee4cd410951a715b5e0bf082ae9158fb0538d9 4792 
gnome-shell-extension-dashtodock_87-1.debian.tar.xz
 74f7b4377ba64eb1d85660c14644675f60d2a286cdce345c42ad0bffbc2434dd 5837 
gnome-shell-extension-dashtodock_87-1_source.buildinfo
Files:
 6c837fc518f7ff099c86f1729a070c15 2312 gnome optional 
gnome-shell-extension-dashtodock_87-1.dsc
 013926872f556de9d1e5e49f5ea2581e 328086 gnome optional 
gnome-shell-extension-dashtodock_87.orig.tar.gz
 ae513fa88eb09de71c76129b768409e9 4792 gnome optional 
gnome-shell-extension-dashtodock_87-1.debian.tar.xz
 ae54a89e63b7a5e02729f4f0dd473df3 5837 gnome optional 
gnome-shell-extension-dashtodock_87-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEExyA8CpIGcL+U8AuxsB0acqyNyaEFAmTnMr8SHGpjYXJ0ZXJA
bGludXguY29tAAoJELAdGnKsjcmhAxcP/jlcyALEdiJtiF0GxGZDTdLcLoDZwE+f
54sIP3FLN7/IgeQ4VA6O9XCLImFVuhPYI6xITk1xwO+sCqcytxBBfeCVE4MTS4Px
hAQf1wvUkNbjPqw4PkWCPSUv9UvzXD2JLQ/1PcTSQxHAmclaFjz7/Ppq0awYPhCX
PY7bDnh0rRdON+muogr5XCeAgGwrMttScvth5O7ZKN1d3QrCtJVe7qsj8hl1upN1
AkL+XGyZ+FYm+R2LsoJFSvFI53x/iERsgiM12XspsuA75qd4WYLZ8wrgluZF2v/3
oNn1hpFVWsUuAoJcS13C4xzG7AtCfI3jLS4jibcokaA1n76d+ys/E1RTTeDuQGaH
i/48F+JD6TmRnqG+KRm9r3DUZCp7sq60GK+ZAMqrARcIVQ5R8N2VoMZFd2t3RrAR
uvlX+JU5JdTQUOG14yfq9jq++fKoJn9pAxQLILalbYsK5YfDDWOO2rU4TAiKzxC5
dJttpiMAjJfjWATir1lZev+kyZWKo6LThJBhuwNCkfmnrILuaUS7XjPcl07jhSQI
bI8ygtmXrbRuWA9NZFOjjAppshAIUH5QYDnmRGqgUAvg4HqFxnskjy/vcsh/2J9J
/0c9BD8yXpYnP/9FRTYiW2rc0MLMJidLBjHOZb4Zqo5eUL+xMva8nK+PTFtryO/T
Kda+vEcOE6Ji
=S5ez
-END PGP SIGNATURE End Message ---

Bug#1041568: marked as done (gnome-shell-extension-dashtodock: needs update for GNOME Shell 44)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2023 10:50:29 +
with message-id 
and subject line Bug#1033100: fixed in gnome-shell-extension-dashtodock 87-1
has caused the Debian Bug report #1033100,
regarding gnome-shell-extension-dashtodock: needs update for GNOME Shell 44
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.)


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

This extension has not been checked for compatibility with GNOME Shell
44. Depending how compatible it is, it will either need an update to
its metadata.json and debian/control to declare compatibility with the
new version, or code changes to adapt it to the new Shell version.

If not updated, it will have to be removed from testing for the GNOME
Shell 44 transition (I don't know when that will be). This bug will be
raised to serious severity when the transition is ready to go ahead.

If a new upstream version is compatible with Shell 44 but not 43,
please upload to experimental for now.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-dashtodock
Source-Version: 87-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 1033...@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: Thu, 24 Aug 2023 12:30:21 +0200
Source: gnome-shell-extension-dashtodock
Architecture: source
Version: 87-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jonathan Carter 
Closes: 1033100 1041568
Changes:
 gnome-shell-extension-dashtodock (87-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #1033100, #1041568)
   * Update gnome-shell dependency to include gnome-shell 45
   * OVerride tests that seem a bit flaky
Checksums-Sha1:
 00dfb8756a944a770dea7c2384c837d46ef161de 2312 
gnome-shell-extension-dashtodock_87-1.dsc
 0ff26a5a8a2d96099f2b19d8d1a841bf702ea97f 328086 
gnome-shell-extension-dashtodock_87.orig.tar.gz
 8c780cae36ea90fa41a2f0ec7c98e57883451914 4792 
gnome-shell-extension-dashtodock_87-1.debian.tar.xz
 ec1e1e07b9527089b18d6e06785f8ed7924d7495 5837 
gnome-shell-extension-dashtodock_87-1_source.buildinfo
Checksums-Sha256:
 5f59ce05d17cb924d92d3da7b40f048d6fb67c5181e8e8a1abf1b53a4b4e2926 2312 
gnome-shell-extension-dashtodock_87-1.dsc
 67948c005ec0024d9953115240f44528771e594f6541b36c24a18f87947c0615 328086 
gnome-shell-extension-dashtodock_87.orig.tar.gz
 65dc1a3872b3b95ac8f03475d1ee4cd410951a715b5e0bf082ae9158fb0538d9 4792 
gnome-shell-extension-dashtodock_87-1.debian.tar.xz
 74f7b4377ba64eb1d85660c14644675f60d2a286cdce345c42ad0bffbc2434dd 5837 
gnome-shell-extension-dashtodock_87-1_source.buildinfo
Files:
 6c837fc518f7ff099c86f1729a070c15 2312 gnome optional 
gnome-shell-extension-dashtodock_87-1.dsc
 013926872f556de9d1e5e49f5ea2581e 328086 gnome optional 
gnome-shell-extension-dashtodock_87.orig.tar.gz
 ae513fa88eb09de71c76129b768409e9 4792 gnome optional 
gnome-shell-extension-dashtodock_87-1.debian.tar.xz
 ae54a89e63b7a5e02729f4f0dd473df3 5837 gnome optional 
gnome-shell-extension-dashtodock_87-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEExyA8CpIGcL+U8AuxsB0acqyNyaEFAmTnMr8SHGpjYXJ0ZXJA
bGludXguY29tAAoJELAdGnKsjcmhAxcP/jlcyALEdiJtiF0GxGZDTdLcLoDZwE+f
54sIP3FLN7/IgeQ4VA6O9XCLImFVuhPYI6xITk1xwO+sCqcytxBBfeCVE4MTS4Px
hAQf1wvUkNbjPqw4PkWCPSUv9UvzXD2JLQ/1PcTSQxHAmclaFjz7/Ppq0awYPhCX
PY7bDnh0rRdON+muogr5XCeAgGwrMttScvth5O7ZKN1d3QrCtJVe7qsj8hl1upN1
AkL+XGyZ+FYm+R2LsoJFSvFI53x/iERsgiM12XspsuA75qd4WYLZ8wrgluZF2v/3
oNn1hpFVWsUuAoJcS13C4xzG7AtCfI3jLS4jibcokaA1n76d+ys/E1RTTeDuQGaH
i/48F+JD6TmRnqG+KRm9r3DUZCp7sq60GK+ZAMqrARcIVQ5R8N2VoMZFd2t3RrAR

Processed: reassign 1050369 to ftp.debian.org

[Debian Bug Tracking System]

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

> reassign 1050369 ftp.debian.org
Bug #1050369 [src:freetennis] RM: freetennis -- RoQA; dead upstream; depends on 
gtk2
Bug reassigned from package 'src:freetennis' to 'ftp.debian.org'.
Ignoring request to alter found versions of bug #1050369 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1050369 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: reassign 1050372 to ftp.debian.org

[Debian Bug Tracking System]

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

> reassign 1050372 ftp.debian.org
Bug #1050372 [src:prooftree] RM: prooftree -- RoQA; depends on gtk2; no human 
uploader; unmaintained upstream; low popcon
Bug reassigned from package 'src:prooftree' to 'ftp.debian.org'.
Ignoring request to alter found versions of bug #1050372 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1050372 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#1042116: marked as done (libstatgen: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2023 10:20:43 +
with message-id 
and subject line Bug#1042116: fixed in libstatgen 1.0.15-7
has caused the Debian Bug report #1042116,
regarding libstatgen: FTBFS: dpkg-gensymbols: error: some symbols or patterns 
disappeared in the symbols file: see diff output below
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.)


-- 
1042116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042116
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libstatgen
Version: 1.0.15-6
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mkdir -p debian/libstatgen-dev/usr/include/libStatGen/
> cp -L include/* debian/libstatgen-dev/usr/include/libStatGen/
> ln -s libStatGen.so.1 libStatGen.so
> d-shlibmove --commit \
> --multiarch \
> --devunversioned \
> --exclude-a \
> libStatGen.so
> Library package automatic movement utility
> set -e
> install -d -m 755 debian/libstatgen-dev/usr/lib/x86_64-linux-gnu
> install -d -m 755 debian/libstatgen1/usr/lib/x86_64-linux-gnu
> mv ./libStatGen.la debian/libstatgen-dev/usr/lib/x86_64-linux-gnu || true
> mv ./libStatGen.so debian/libstatgen-dev/usr/lib/x86_64-linux-gnu
> mv /<>/libStatGen.so.1 
> debian/libstatgen1/usr/lib/x86_64-linux-gnu
> PKGDEV=libstatgen-dev
> PKGSHL=libstatgen1
> mv: cannot stat './libStatGen.la': No such file or directory
> make[1]: Leaving directory '/<>'
>dh_installdocs -O--no-parallel
>dh_installchangelogs -O--no-parallel
>dh_installsystemduser -O--no-parallel
>dh_perl -O--no-parallel
>dh_link -O--no-parallel
>dh_strip_nondeterminism -O--no-parallel
>dh_compress -O--no-parallel
>dh_fixperms -O--no-parallel
>dh_missing -O--no-parallel
>dh_dwz -a -O--no-parallel
>dh_strip -a -O--no-parallel
>dh_makeshlibs -a -O--no-parallel
> 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/libstatgen1/DEBIAN/symbols doesn't match 
> completely debian/libstatgen1.symbols
> --- debian/libstatgen1.symbols (libstatgen1_1.0.15-6_amd64)
> +++ dpkg-gensymbolsnCVnIJ 2023-07-26 19:18:57.912175612 +
> @@ -1638,35 +1638,47 @@
>   
> _ZNKSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_St9_IdentityIS5_ESt4lessIS5_ESaIS5_EE4findERKS5_@Base
>  1.0.14
>   
> _ZNSt10_HashtableINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_SaIS5_ENSt8__detail9_IdentityESt8equal_toIS5_ESt4hashIS5_ENS7_18_Mod_range_hashingENS7_20_Default_ranged_hashENS7_20_Prime_rehash_policyENS7_17_Hashtable_traitsILb1ELb1ELb14findERKS5_@Base
>  1.0.15
>   
> _ZNSt10_HashtableINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_SaIS5_ENSt8__detail9_IdentityESt8equal_toIS5_ESt4hashIS5_ENS7_18_Mod_range_hashingENS7_20_Default_ranged_hashENS7_20_Prime_rehash_policyENS7_17_Hashtable_traitsILb1ELb1ELb19_M_rehashEmRKm@Base
>  1.0.15
> + 
> _ZNSt10_HashtableINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_SaIS5_ENSt8__detail9_IdentityESt8equal_toIS5_ESt4hashIS5_ENS7_18_Mod_range_hashingENS7_20_Default_ranged_hashENS7_20_Prime_rehash_policyENS7_17_Hashtable_traitsILb1ELb1ELb1D1Ev@Base
>  1.0.15-6
> + 
> _ZNSt10_HashtableINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_SaIS5_ENSt8__detail9_IdentityESt8equal_toIS5_ESt4hashIS5_ENS7_18_Mod_range_hashingENS7_20_Default_ranged_hashENS7_20_Prime_rehash_policyENS7_17_Hashtable_traitsILb1ELb1ELb1D2Ev@Base
>  1.0.15-6
>   _ZNSt12_Destroy_auxILb0EE9__destroyIP6StringEEvT_S4_@Base 1.0.14
>   _ZNSt12_Destroy_auxILb0EE9__destroyIPN9IndexBase9ReferenceEEEvT_S5_@Base 
> 1.0.14
> - _ZNSt12_Vector_baseIN5Cigar13CigarOperatorESaIS1_EED1Ev@Base 1.0.14
> - _ZNSt12_Vector_baseIN5Cigar13CigarOperatorESaIS1_EED2Ev@Base 1.0.14
> - _ZNSt12_Vector_baseIP15SamHeaderRecordSaIS1_EED1Ev@Base 1.0.14
> - _ZNSt12_Vector_baseIP15SamHeaderRecordSaIS1_EED2Ev@Base 1.0.14
> - _ZNSt12_Vector_baseIcSaIcEED1Ev@Base 1.0.14
> - _ZNSt12_Vector_baseIcSaIcEED2Ev@Base 1.0.14
> - _ZNSt12_Vector_baseIfSaIfEED1Ev@Base 1.0.14
> - _ZNSt12_Vector_baseIfSaIfEED2Ev@Base 1.0.14
> - _ZNSt12_Vector_baseIiSaIiEED1Ev@Base 1.0.14
> - _ZNSt12_Vector_baseIiSaIiEED2Ev@Base 1.0.14
> +#MISSING: 

Bug#1050168: marked as done (FTBFS: test_no_local_cert: tlsv13 alert certificate required)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2023 09:53:12 +
with message-id 
and subject line Bug#1050168: fixed in kxd 0.15-4.1
has caused the Debian Bug report #1050168,
regarding FTBFS: test_no_local_cert: tlsv13 alert certificate required
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.)


-- 
1050168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050168
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kxd
Version: 0.15-4
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: albert...@blitiri.com.ar, z...@debian.org

I'm not sure if it's related to golang-defaults -> golang-1.21 recently.

tests/run_tests -b
...F
Stderr:
/usr/lib/python3.11/unittest/case.py:622: ResourceWarning: unclosed 

  with outcome.testPartExecutor(self):
..
==
FAIL: test_no_local_cert (__main__.TrickyRequests.test_no_local_cert)
No local certificate.
--
Traceback (most recent call last):
  File "/<>/tests/run_tests", line 357, in test_no_local_cert
conn.getresponse()
  File "/usr/lib/python3.11/http/client.py", line 1378, in getresponse
response.begin()
  File "/usr/lib/python3.11/http/client.py", line 318, in begin
version, status, reason = self._read_status()
  ^^^
  File "/usr/lib/python3.11/http/client.py", line 279, in _read_status
line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1")
   ^^
  File "/usr/lib/python3.11/socket.py", line 706, in readinto
return self._sock.recv_into(b)
   ^^^
  File "/usr/lib/python3.11/ssl.py", line 1278, in recv_into
return self.read(nbytes, buffer)
   ^
  File "/usr/lib/python3.11/ssl.py", line 1134, in read
return self._sslobj.read(len, buffer)
   ^^
ssl.SSLError: [SSL: TLSV13_ALERT_CERTIFICATE_REQUIRED] tlsv13 alert certificate 
required (_ssl.c:2576)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/<>/tests/run_tests", line 360, in test_no_local_cert
self.assertEqual(err.reason, "SSLV3_ALERT_BAD_CERTIFICATE")
AssertionError: 'TLSV13_ALERT_CERTIFICATE_REQUIRED' != 
'SSLV3_ALERT_BAD_CERTIFICATE'
- TLSV13_ALERT_CERTIFICATE_REQUIRED
+ SSLV3_ALERT_BAD_CERTIFICATE


Stdout:
Launching server:  /<>/out/kxd 
--data_dir=/tmp/kxdtest-y_lm39pn/config-server-u2ol6sph/data 
--key=/tmp/kxdtest-y_lm39pn/config-server-u2ol6sph/key.pem 
--cert=/tmp/kxdtest-y_lm39pn/config-server-u2ol6sph/cert.pem 
--logfile=/tmp/kxdtest-y_lm39pn/config-server-u2ol6sph/log 
--hook=/tmp/kxdtest-y_lm39pn/config-server-u2ol6sph/hook

--
Ran 10 tests in 3.009s

FAILED (failures=1)
--- End Message ---
--- Begin Message ---
Source: kxd
Source-Version: 0.15-4.1
Done: Shengjing Zhu 

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

Debian distribution maintenance software
pp.
Shengjing Zhu  (supplier of updated kxd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 24 Aug 2023 17:15:52 +0800
Source: kxd
Architecture: source
Version: 0.15-4.1
Distribution: unstable
Urgency: medium
Maintainer: Maximiliano Curia 
Changed-By: Shengjing Zhu 
Closes: 1050168
Changes:
 kxd (0.15-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
 .
   [ Shengjing Zhu ]
   * Backport patch to fix FTBFS (Closes: #1050168)
Checksums-Sha1:
 7b91785cf0fcf9b1e3d28dbc367e6767811c69a2 1332 kxd_0.15-4.1.dsc
 ef1eb0c70a950b4c4dff1668251a7d0d9cf265c7 5660 kxd_0.15-4.1.debian.tar.xz
 dd68195bd44f526b6d8568d8d590e95d20025b1c 6322 kxd_0.15-4.1_amd64.buildinfo
Checksums-Sha256:
 798c49a9ef425ffd2d4715dcb3692f28d2359f6ba3eccb50aded6c145c5e49c7 1332 
kxd_0.15-4.1.dsc
 

Bug#1050096: virtualbox-dkms: Does not build on 6.4.0-3-amd64

[Jens Yllman]

When I do this change virtualbox-dkms is compiles fine. But now the 
kernel from 6.4.0-3 will not boot. It gets stuck early in the boot process.


So I have to boot into the older, 6.4.0-2 that still is on my system.

Jens

Bug#1050168: FTBFS: test_no_local_cert: tlsv13 alert certificate required

[Shengjing Zhu]

Hi,

On Thu, Aug 24, 2023 at 5:38 AM Alberto Bertogli
 wrote:
>
> On Mon, Aug 21, 2023 at 05:32:53PM +0800, Shengjing Zhu wrote:
> >Source: kxd
> >Version: 0.15-4
> >Severity: serious
> >Tags: ftbfs
> >X-Debbugs-Cc: albert...@blitiri.com.ar, z...@debian.org
> >
> >I'm not sure if it's related to golang-defaults -> golang-1.21 recently.
> >
> [...]
> >Traceback (most recent call last):
> >  File "/<>/tests/run_tests", line 360, in test_no_local_cert
> >self.assertEqual(err.reason, "SSLV3_ALERT_BAD_CERTIFICATE")
> >AssertionError: 'TLSV13_ALERT_CERTIFICATE_REQUIRED' != 
> >'SSLV3_ALERT_BAD_CERTIFICATE'
> >- TLSV13_ALERT_CERTIFICATE_REQUIRED
> >+ SSLV3_ALERT_BAD_CERTIFICATE
>
> Thanks for filing this!
>
> Yeah I think it's likely, this looks like a more specific and accurate
> error is now reported in this case, either due to the Go TLS library, or
> OpenSSL (which the tests use because they're written in Python).
>
> I have a patch in the `next` branch that should update the test
> accordingly:
>
> https://blitiri.com.ar/git/r/kxd/c/ca7d96cc6088cddbdd9904cc8de8192b417a9340/
>
> https://blitiri.com.ar/git/r/kxd/c/ca7d96cc6088cddbdd9904cc8de8192b417a9340.patch
>
> Would you mind giving it a try? It should solve the problem.
>

I have uploaded the patch in kxd/0.15-4.1.

BTW I see this package doesn't have the Built-Using field (or
Static-Built-Using more correctly) to track the embedded Go toolchain
version, although it has `Built-Using: ${misc:Built-Using}` in
debian/control file. Would you like to improve that a bit?

-- 
Shengjing Zhu

Bug#1050096: virtualbox-dkms: Does not build on 6.4.0-3-amd64

[Laurent Cheylus]

Package: virtualbox-dkms
Followup-For: Bug #1050096

Hi,

I confirm that this bug is solved with the fix of Jonas Andradas
:

In /usr/src/virtualbox-7.0.10/vboxnetflt/linux/VBoxNetFlt-linux.c

on line 50, changing the value from:

#if RTLNX_VER_MIN(6,5,0)

to:

#if RTLNX_VER_MIN(6,4,0)

Build OK on Debian/testing with linux-image-6.4.0-3-amd64 package (kernel
version 6.4.11-1).


regards, Laurent

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

Kernel: Linux 6.4.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages virtualbox-dkms depends on:
ii  dkms  3.0.11-3

Versions of packages virtualbox-dkms recommends:
ii  virtualbox  7.0.10-dfsg-2

virtualbox-dkms suggests no packages.

-- no debconf information

-- debsums errors found:
debsums: changed file 
/usr/src/virtualbox-7.0.10/vboxnetflt/linux/VBoxNetFlt-linux.c (from 
virtualbox-dkms package)

Bug#1050298: marked as done (rust-rustls-webpki: RUSTSEC-2023-0053)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2023 08:59:45 +
with message-id 
and subject line Bug#1050298: fixed in rust-rustls-webpki 0.101.4-1
has caused the Debian Bug report #1050298,
regarding rust-rustls-webpki: RUSTSEC-2023-0053
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.)


-- 
1050298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050298
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-rustls-webpki
Version: 0.101.3-2
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi

Please see https://rustsec.org/advisories/RUSTSEC-2023-0053.html .

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: rust-rustls-webpki
Source-Version: 0.101.4-1
Done: Jonas Smedegaard 

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated rust-rustls-webpki 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 24 Aug 2023 10:06:53 +0200
Source: rust-rustls-webpki
Architecture: source
Version: 0.101.4-1
Distribution: unstable
Urgency: high
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Closes: 1050298
Changes:
 rust-rustls-webpki (0.101.4-1) unstable; urgency=high
 .
   * bump project version in virtual packages and autopkgtests;
 closes: bug#1050298, thanks to Salvatore Bonaccorso;
 RUSTSEC-2023-0053
   * unfuzz patches
   * set urgency=high due to security bugfix
Checksums-Sha1:
 1e931ab515bb1919677adf240f201fa6d3593c7f 2576 rust-rustls-webpki_0.101.4-1.dsc
 81908016a9e48a1b80ae9b812254931b89fff099 387696 
rust-rustls-webpki_0.101.4.orig.tar.gz
 2df1405eeed839aa01aca375c32bfe17e3aa5e60 15084 
rust-rustls-webpki_0.101.4-1.debian.tar.xz
 0a91a27422e1c082a82531817f0c1fcb5376e24a 11402 
rust-rustls-webpki_0.101.4-1_amd64.buildinfo
Checksums-Sha256:
 07df2069953fb5350bed27743cf5ce07e5407e422a6dd9f7f799d732a45a93e0 2576 
rust-rustls-webpki_0.101.4-1.dsc
 553dcbff4472f198cf2d5059e63c5d867fb0f1bf44c340c62905351b0767b2a7 387696 
rust-rustls-webpki_0.101.4.orig.tar.gz
 06f3237916a39f044aabaca69979a40f54febace64b8d3eb9fea08ca9d0ba40d 15084 
rust-rustls-webpki_0.101.4-1.debian.tar.xz
 70b869d3674cd84facaef8f27bcb90209465fb06ea56400737c95b77b87f36e2 11402 
rust-rustls-webpki_0.101.4-1_amd64.buildinfo
Files:
 46ff5a5b49dcc522ad8f2342a5309d3f 2576 rust optional 
rust-rustls-webpki_0.101.4-1.dsc
 47ab7fca51a1ec919bdddbbb70be787e 387696 rust optional 
rust-rustls-webpki_0.101.4.orig.tar.gz
 80bc6f3bf045ff16e57e2a12640663eb 15084 rust optional 
rust-rustls-webpki_0.101.4-1.debian.tar.xz
 5424b4bc65f6c2c610ebe19b52329a8b 11402 rust optional 
rust-rustls-webpki_0.101.4-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmTnEKYACgkQLHwxRsGg
ASHQSA//Qr5RCtjmdPNVBtW5D+F6X0bj6PbUoOXfMVx902GEGMNNdDXT2XBzklzr
6pYfQeloHXo+FGNLfOVORP048TmT21kqe2GtseeAm1qNrlCPOecXHRyFALDw3D4C
1tg/o4aZQPJyKBGKzQstYh8DaYvShCLUAVqh/pTk8s7XZK4G1NOlcrvlbZUIdVaf
V3e0hN2XkceArTTTbU38eDORTXr1fwh1SdaeHGuO0E+8vYHQQrwEalt5KjAXfqlS
2ac51JxwMwj28wYH938np69H0JQck41kEsbhZGzM1UD2ugnwWEJp96gmzyLeMja6
u2imB+v6yZve9WDBw95Ayl0b5zyT7bsIiC5ZI+vb+/ynbgmcQJMGqZ67CwrVOUvw
nQ4tAcLK3Jdld2Z8Sy1fg7b8ewLacqdul6wf1rHRFcVP+ZlgEShKQAgcTzxQIIcv
d7BbDDA85Rj/jqK8grpU/wWvz8746A2apgXdNyEYTIaApnex7vWD0e3Z/c95XQr9
3p3bTKZb10yuqakMjLhM2qpTDNqwwjYmS1yuRmjvDKRfGLqRlwrt/ffFDjsaLr4o
kfVf3UaCS6AxaThoXPZs0xUoBY3lBnMl4nwBNt2/Ij8s1qvNJQXYB0bHXyDV7Nes
mjIvjpetAzy6mnqQJpyFxOHAy3RMIu/BNtKRCflZBNKvG4QoOlM=
=wo/l
-END PGP SIGNATURE End Message ---

Bug#1050288: nsis 3.08-3 (bookworm) generates bogus relocation information (regression)

[Christian Franke]

Severity of this bug promoted to 'grave' because further tests show that 
generated installers may not work at all:


Testcase:

$ cat /etc/debian_version
12.1

$ makensis -VERSION
v3.08-3

$ cat test.nsi
RequestExecutionLevel user
Section "Test"
  MessageBox MB_OK "Hello, World!"
SectionEnd

$ makensis test.nsi
...

$ objdump -p test-debian.exe >/dev/null
BFD: error: test-debian.exe(.reloc) is too large (0x8e4 bytes)


If test.exe is started on a Windows machine, CreateProcess() fails with 
GetLastError()==193 (ERROR_BAD_EXE_FORMAT).


The same installer built with upstream NSIS 3.09 on Windows is much 
smaller and works:


-rwxr-xr-x 1 ... 94699 Aug 24 09:45 test.exe
-rwxr-xr-x 1 ... 38886 Aug 24 09:43 test-built-on-windows.exe

Processed: Re: nsis 3.08-3 (bookworm) generates bogus relocation information (regression)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #1050288 [nsis] nsis 3.08-3 (bookworm) generates bogus relocation 
information (regression)
Severity set to 'grave' from 'important'

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

Bug#1050407: tycho: build-depends on obsolete libeclipse-osgi-util-java

[Ralf Treinen]

Source: tycho
Version: 1.6.0-3
Severity: serious
Tags: ftbfs

Hi,

tycho build-depends on libeclipse-osgi-util-java which only exists in
oldstable (and older).

-Ralf.

Bug#1050404: flycheck: keep flycheck out of testing

[Sean Whitton]

Source: flycheck
Severity: serious

flycheck is unmaintained and its fragile autopkgtest keeps stopping more
important things from migrating to testing.  Let's keep it out of testing for 
now.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#1050402: aws-shell: build-depends on obsolete version of awscli

[Ralf Treinen]

Source: aws-shell
Tags: ftbfs
Version: 0.2.1-1
Severity: serious

Hi, aws-shell build-depends on awscli (<< 2.0.0). However, the current
version of awscli in sid is 2.12.0-1.

-Ralf.

Processed: limit source to dahdi-linux, tagging 592745, tagging 1042747

[Debian Bug Tracking System]

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

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

> tags 592745 + pending
Bug #592745 [dahdi-source] dahdi-source: wcfxo fails to initialize card
Added tag(s) pending.
> tags 1042747 + pending
Bug #1042747 [dahdi-dkms] dahdi-dkms: dkms.conf still lists removed pciradio.ko
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1050401: wasm builds fail with -march= and -mfpu flags set for the host

[Matthias Klose]

Package: src:llvm-toolchain-17
Version: 17.0.0~+rc3-1~exp1
Severity: serious
Tags: sid trixie

the wasm builds fail on architectures with -march= and -mfpu flags set for the 
host, like armhf, and probably armel.  This used to work in LLVM 16.


I assume this is an upstream issue (confusing the host and the target), but here 
is one way to work-around it, to remove these flags from the flag settings. 
Another possibility could be to disable the wasm builds on these architectures.


patch for the work around is attached.


[...]
FAILED: CMakeFiles/cmTC_31967.dir/testCCompiler.c.obj
"/<>/build-llvm/tools/clang/stage2-bins/bin/clang" 
--target=wasm32-unknown-unknown   -O2 -DNDEBUG -g1 -fstack-protector-strong
 -Wformat -Werror=format-security -Wno-unused-command-line-argument 
-march=armv7-a -mfpu=vfpv3-d16 -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MT CMak
eFiles/cmTC_31967.dir/testCCompiler.c.obj -MF 
CMakeFiles/cmTC_31967.dir/testCCompiler.c.obj.d -o 
CMakeFiles/cmTC_31967.dir/testCCompiler.c.obj
-c 
'/<>/build-wasm/compiler-rt-wasm32/CMakeFiles/CMakeScratch/TryCompile-X7CN7p/testCCompiler.c'

clang: error: unsupported option '-march=' for target 
'wasm32-unknown-unknown'
clang: error: unsupported option '-mfpu=' for target 
'wasm32-unknown-unknown'
ninja: build stopped: subcommand failed.





  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  CMakeLists.txt:9 (project)


-- Configuring incomplete, errors occurred!
make[1]: *** [debian/rules:815: build-wasm/compiler-rt-wasm32] Error 1  * Don't pass -march= and -mcpu= flags to the wasm builds.
 
diff -Nru llvm-toolchain-17-17.0.0~+rc2/debian/rules llvm-toolchain-17-17.0.0~+rc2/debian/rules
--- llvm-toolchain-17-17.0.0~+rc2/debian/rules	2023-08-15 21:25:12.0 +0200
+++ llvm-toolchain-17-17.0.0~+rc2/debian/rules	2023-08-23 17:26:07.0 +0200
@@ -821,8 +821,8 @@
 		-DCMAKE_ASM_COMPILER_TARGET=$(cpu)-unknown-unknown \
 		-DCMAKE_C_COMPILER=$(STAGE_2_BIN_DIR)/clang \
 		-DCMAKE_CXX_COMPILER=$(STAGE_2_BIN_DIR)/clang++ \
-		-DCMAKE_C_FLAGS="$(opt_flags) $(STAGE_2_CFLAGS)" \
-		-DCMAKE_CXX_FLAGS="$(opt_flags) $(STAGE_2_CXXFLAGS)" \
+		-DCMAKE_C_FLAGS="$(opt_flags) $(filter-out -march=%, $(filter-out -mfpu=%, $(STAGE_2_CFLAGS)))" \
+		-DCMAKE_CXX_FLAGS="$(opt_flags) $(filter-out -march=%, $(filter-out -mfpu=%, $(STAGE_2_CXXFLAGS)))" \
 		-DCMAKE_SHARED_LINKER_FLAGS="$(STAGE_2_LDFLAGS) -L$(STAGE_2_LIB_DIR)" \
 		-DCMAKE_MODULE_LINKER_FLAGS="$(STAGE_2_LDFLAGS) -L$(STAGE_2_LIB_DIR)" \
 		-DCMAKE_EXE_LINKER_FLAGS="$(STAGE_2_LDFLAGS) -L$(STAGE_2_LIB_DIR)" \
@@ -885,8 +885,8 @@
 		-DCMAKE_CXX_COMPILER=$(STAGE_2_BIN_DIR)/clang++ \
 		-DCMAKE_AR=$(STAGE_2_BIN_DIR)/llvm-ar \
 		-DCMAKE_RANLIB=$(STAGE_2_BIN_DIR)/llvm-ranlib \
-		-DCMAKE_C_FLAGS="$(opt_flags) $(STAGE_2_CFLAGS) -fno-stack-protector" \
-		-DCMAKE_CXX_FLAGS="$(opt_flags) $(STAGE_2_CXXFLAGS) -fno-stack-protector" \
+		-DCMAKE_C_FLAGS="$(opt_flags) $(filter-out -march=%, $(filter-out -mfpu=%, $(STAGE_2_CFLAGS))) -fno-stack-protector" \
+		-DCMAKE_CXX_FLAGS="$(opt_flags) $(filter-out -march=%, $(filter-out -mfpu=%, $(STAGE_2_CXXFLAGS))) -fno-stack-protector" \
 		-DCMAKE_SHARED_LINKER_FLAGS="$(LDFLAGS) -L$(STAGE_2_LIB_DIR)" \
 		-DCMAKE_MODULE_LINKER_FLAGS="$(LDFLAGS) -L$(STAGE_2_LIB_DIR)" \
 		-DCMAKE_EXE_LINKER_FLAGS="$(LDFLAGS) -L$(STAGE_2_LIB_DIR)" \

Processed: found 1024889 in 1.1~alpha19-6

[Debian Bug Tracking System]

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

> found 1024889 1.1~alpha19-6
Bug #1024889 [src:pplacer] pplacer: build-depends on dropped package
Marked as found in versions pplacer/1.1~alpha19-6.
> thanks
Stopping processing here.

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

Processed: reassign 1024889 to src:pplacer

[Debian Bug Tracking System]

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

> reassign 1024889 src:pplacer
Bug #1024889 [pplacer] pplacer: build-depedends on dropped package.
Bug reassigned from package 'pplacer' to 'src:pplacer'.
No longer marked as found in versions pplacer/1.1~alpha19-6.
Ignoring request to alter fixed versions of bug #1024889 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: retitle 1024889 to pplacer: build-depends on dropped package

[Debian Bug Tracking System]

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

> retitle 1024889 pplacer: build-depends on dropped package
Bug #1024889 [src:pplacer] pplacer: build-depedends on dropped package.
Changed Bug title to 'pplacer: build-depends on dropped package' from 'pplacer: 
build-depedends on dropped package.'.
> thanks
Stopping processing here.

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

Bug#1050400: aws-checksums: build-depends on non-existing libaws-c-common-dev

[Ralf Treinen]

Source: aws-checksums
Severity: serious
Tags: ftbfs
Version: 0.1.13-1

Hi, aws-checksums build-depends on libaws-c-common-dev which does not
exist anywhere in the archive. This is the case since 2022-11-10.

-Ralf.

Bug#1050361: RM: mangler -- RoQA; dead upstream; depends on gtk2

[Vincent Cheng]

Control: severity -1 important

On Wed, Aug 23, 2023 at 9:54 AM Bastian Germann  wrote:
>
> Source: mangler
> Severity: serious
> Version: 1.2.5-5
>
> mangler does not seem to be used a lot and is dead upstream. I doubt
> that Ventrilo is still a thing nowadays.
>
> I intend to file a RM bug.
> If you have any reasons to keep it in Debian please voice them here.
> To get people's attention, I am filing as a serious bug and will
> reassign to the FTP team when the package is autoremoved from testing.

AFAIK mangler is the only Ventrilo client packaged in Debian, so I'd
like to keep this package around until gtk2 removal is imminent (i.e.
#947713 is set to severity serious). I see no reason to remove this
package prematurely until that happens. I'll keep the package on life
support in the meantime.

Regards,
Vincent

Processed: Re: Bug#1050361: RM: mangler -- RoQA; dead upstream; depends on gtk2

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1050361 [src:mangler] RM: mangler -- RoQA; dead upstream; depends on gtk2
Severity set to 'important' from 'serious'

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