Bug#1054477: marked as done (autorandr: install autorandr.service twice once dh_installsystemd installs to /usr)
Your message dated Sat, 18 Nov 2023 05:04:07 + with message-id and subject line Bug#1054477: fixed in autorandr 1.13.3-1 has caused the Debian Bug report #1054477, regarding autorandr: install autorandr.service twice once dh_installsystemd installs to /usr 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.) -- 1054477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054477 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: autorandr Version: 1.12.1-1.1 Severity: normal Tags: patch User: helm...@debian.org Usertags: dep17m2 We want to change dh_installsystemd such that it installs units below /usr in order to finalize the /usr-merge transition via DEP17. When doing so, autorandr happes to install the upstream unit (via dh_auto_install) below /lib and debian/autorand.service (via dh_installsystemd) below /usr/lib. Doing so is a policy violation and this bug will become release critical once I upload debhelper. I'm attaching a patch that disables the installation of the upstream unit. Once you go back to the upstream unit, please leave SYSTEMD_UNIT_DIR unset, because it'll then pick up the right value from pkgconfig and dh_installsystemd now supports generating maintainer scripts from both locations. Helmut diff -Nru autorandr-1.12.1/debian/changelog autorandr-1.12.1/debian/changelog --- autorandr-1.12.1/debian/changelog 2022-10-15 11:53:17.0 +0200 +++ autorandr-1.12.1/debian/changelog 2023-10-24 09:56:57.0 +0200 @@ -1,3 +1,10 @@ +autorandr (1.12.1-1.2) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Install systemd unit only once. (Closes: #-1) + + -- Helmut Grohne Tue, 24 Oct 2023 09:56:57 +0200 + autorandr (1.12.1-1.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru autorandr-1.12.1/debian/rules autorandr-1.12.1/debian/rules --- autorandr-1.12.1/debian/rules 2020-04-26 01:40:31.0 +0200 +++ autorandr-1.12.1/debian/rules 2023-10-24 09:56:57.0 +0200 @@ -5,13 +5,13 @@ override_dh_auto_build: dh_auto_build -- UDEV_RULES_DIR=/lib/udev/rules.d \ - SYSTEMD_UNIT_DIR=/lib/systemd/system \ + SYSTEMD_UNIT_DIR= \ BASH_COMPLETIONS_DIR=/usr/share/bash-completion/completions \ PM_SLEEPHOOKS_DIR=/etc/pm/sleep.d/ override_dh_auto_install: dh_auto_install -- UDEV_RULES_DIR=/lib/udev/rules.d \ - SYSTEMD_UNIT_DIR=/lib/systemd/system \ + SYSTEMD_UNIT_DIR= \ BASH_COMPLETIONS_DIR=/usr/share/bash-completion/completions \ PM_SLEEPHOOKS_DIR=/etc/pm/sleep.d/ install -D -m 755 contrib/pm-utils/40autorandr debian/autorandr/etc/pm/sleep.d/40autorandr --- End Message --- --- Begin Message --- Source: autorandr Source-Version: 1.13.3-1 Done: Don Armstrong We believe that the bug you reported is fixed in the latest version of autorandr, 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. Don Armstrong (supplier of updated autorandr 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, 27 Oct 2023 21:11:41 -0700 Source: autorandr Binary: autorandr Architecture: source all Version: 1.13.3-1 Distribution: unstable Urgency: medium Maintainer: Don Armstrong Changed-By: Don Armstrong Description: autorandr - Automatically select a display configuration for connected device Closes: 1054477 Changes: autorandr (1.13.3-1) unstable; urgency=medium . [ Debian Janitor] * Trim trailing whitespace. * Bump debhelper from old 12 to 13. * Set debhelper-compat version in Build-Depends. * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. * Use canonical URL in Vcs-Browser. * Update standards version to 4.6.1, no changes needed. . [ Don Armstrong ] * New upstream release * Install zsh completions * Use StartLimitIntervalSec again, as even oldoldstable has systemd >> 230 * Install things from contrib as examples * Add dependencies on pkgconf and systemd-dev so the u
Bug#1054971: marked as done (haskell-clash-ghc: FTBFS: unsatisfiable build-dependencies: libghc-clash-lib-dev (>= 1.6.6), libghc-clash-lib-dev (< 1.6.7), libghc-clash-lib-prof, libghc-clash-prelude-de
Your message dated Sat, 18 Nov 2023 03:34:12 + with message-id and subject line Bug#1054971: fixed in haskell-clash-ghc 1.8.1-1 has caused the Debian Bug report #1054971, regarding haskell-clash-ghc: FTBFS: unsatisfiable build-dependencies: libghc-clash-lib-dev (>= 1.6.6), libghc-clash-lib-dev (< 1.6.7), libghc-clash-lib-prof, libghc-clash-prelude-dev (>= 1.6.6), libghc-clash-prelude-dev (< 1.6.7), libghc-clash-prelude-prof, libghc-clash-lib-doc, libghc-clash-prelude-doc 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.) -- 1054971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-clash-ghc Version: 1.6.6-3 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-clash-lib-dev (>= > 1.6.6), libghc-clash-lib-dev (<< 1.6.7), libghc-clash-lib-prof, > libghc-clash-prelude-dev (>= 1.6.6), libghc-clash-prelude-dev (<< 1.6.7), > libghc-clash-prelude-prof, libghc-concurrent-supply-dev (>= 0.1.7), > libghc-concurrent-supply-dev (<< 0.2), libghc-concurrent-supply-prof, > libghc-data-binary-ieee754-dev (>= 0.4.4), libghc-data-binary-ieee754-dev (<< > 0.6), libghc-data-binary-ieee754-prof, libghc-extra-dev (>= 1.6), > libghc-extra-dev (<< 1.8), libghc-extra-prof, libghc-ghc-typelits-extra-dev > (>= 0.3.2), libghc-ghc-typelits-extra-dev (<< 0.5), > libghc-ghc-typelits-extra-prof, libghc-ghc-typelits-knownnat-dev (>= 0.6), > libghc-ghc-typelits-knownnat-dev (<< 0.8), libghc-ghc-typelits-knownnat-prof, > libghc-ghc-typelits-natnormalise-dev (>= 0.6), > libghc-ghc-typelits-natnormalise-dev (<< 0.8), > libghc-ghc-typelits-natnormalise-prof, libghc-hashable-dev (>= 1.1.2.3), > libghc-hashable-dev (<< 1.5), libghc-hashable-prof, libghc-lens-dev (>= > 4.10), libghc-lens-dev (<< 5.3), libghc-lens-prof, libghc-primitive-dev (>= > 0.5.0.1), libghc-primitive-dev (<< 1.0), libghc-primitive-prof, > libghc-reflection-dev (>= 2.1.2), libghc-reflection-dev (<< 3.0), > libghc-reflection-prof, libghc-split-dev (>= 0.2.3), libghc-split-dev (<< > 0.3), libghc-split-prof, libghc-uniplate-dev (>= 1.6.12), libghc-uniplate-dev > (<< 1.8), libghc-uniplate-prof, libghc-unordered-containers-dev (>= 0.2.1.0), > libghc-unordered-containers-dev (<< 0.3), libghc-unordered-containers-prof, > libghc-utf8-string-dev (>= 1.0.0.0), libghc-utf8-string-dev (<< 1.1.0.0), > libghc-utf8-string-prof, libghc-vector-dev (>= 0.11), libghc-vector-dev (<< > 1.0), libghc-vector-prof, build-essential, fakeroot, ghc-doc, > libghc-clash-lib-doc, libghc-clash-prelude-doc, libghc-concurrent-supply-doc, > libghc-data-binary-ieee754-doc, libghc-extra-doc, > libghc-ghc-typelits-extra-doc, libghc-ghc-typelits-knownnat-doc, > libghc-ghc-typelits-natnormalise-doc, libghc-hashable-doc, libghc-lens-doc, > libghc-primitive-doc, libghc-reflection-doc, libghc-split-doc, > libghc-uniplate-doc, libghc-unordered-containers-doc, libghc-utf8-string-doc, > libghc-vector-doc > Filtered Build-Depends: debhelper (>= 10), haskell-devscripts-minimal, cdbs, > ghc, ghc-prof, libghc-clash-lib-dev (>= 1.6.6), libghc-clash-lib-dev (<< > 1.6.7), libghc-clash-lib-prof, libghc-clash-prelude-dev (>= 1.6.6), > libghc-clash-prelude-dev (<< 1.6.7), libghc-clash-prelude-prof, > libghc-concurrent-supply-dev (>= 0.1.7), libghc-concurrent-supply-dev (<< > 0.2), libghc-concurrent-supply-prof, libghc-data-binary-ieee754-dev (>= > 0.4.4), libghc-data-binary-ieee754-dev (<< 0.6), > libghc-data-binary-ieee754-prof, libghc-extra-dev (>= 1.6), libghc-extra-dev > (<< 1.8), libghc-extra-prof, libghc-ghc-typelits-extra-dev (>= 0.3.2), > libghc-ghc-typelits-extra-dev (<< 0.5), libghc-ghc-typelits-extra-prof, > libghc-ghc-typelits-knownnat-dev (>= 0.6), libghc-ghc-typelits-knownnat-dev > (<< 0.8), libghc-ghc-typelits-knownnat-prof, > libghc-ghc-typelits-natnormalise-dev (>= 0.6), > libghc-ghc-typelits-natnormalise-dev (<< 0.8), > libghc-ghc-typelits-natnormalise-prof, libghc-ha
Bug#1054979: marked as done (haskell-clash-lib: FTBFS: unsatisfiable build-dependencies: libghc-clash-prelude-dev (>= 1.6.6), libghc-clash-prelude-dev (< 1.6.7), libghc-clash-prelude-prof, libghc-clas
Your message dated Sat, 18 Nov 2023 03:19:13 + with message-id and subject line Bug#1054979: fixed in haskell-clash-lib 1.8.1-1 has caused the Debian Bug report #1054979, regarding haskell-clash-lib: FTBFS: unsatisfiable build-dependencies: libghc-clash-prelude-dev (>= 1.6.6), libghc-clash-prelude-dev (< 1.6.7), libghc-clash-prelude-prof, libghc-clash-prelude-doc 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.) -- 1054979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054979 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-clash-lib Version: 1.6.6-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-aeson-dev (>= > 0.6.2.0), libghc-aeson-dev (<< 2.3), libghc-aeson-prof, > libghc-aeson-pretty-dev (>= 0.8), libghc-aeson-pretty-dev (<< 0.9), > libghc-aeson-pretty-prof, libghc-ansi-terminal-dev (>= 0.8.0.0), > libghc-ansi-terminal-dev (<< 0.12), libghc-ansi-terminal-prof, > libghc-async-dev (>= 2.2.0), libghc-async-dev (<< 2.3), libghc-async-prof, > libghc-attoparsec-dev (>= 0.10.4.0), libghc-attoparsec-dev (<< 0.15), > libghc-attoparsec-prof, libghc-base16-bytestring-dev (>= 0.1.1), > libghc-base16-bytestring-dev (<< 1.1), libghc-base16-bytestring-prof, > libghc-clash-prelude-dev (>= 1.6.6), libghc-clash-prelude-dev (<< 1.6.7), > libghc-clash-prelude-prof, libghc-concurrent-supply-dev (>= 0.1.7), > libghc-concurrent-supply-dev (<< 0.2), libghc-concurrent-supply-prof, > libghc-cryptohash-sha256-dev (>= 0.11), libghc-cryptohash-sha256-dev (<< > 0.12), libghc-cryptohash-sha256-prof, libghc-data-binary-ieee754-dev (>= > 0.4.4), libghc-data-binary-ieee754-dev (<< 0.6), > libghc-data-binary-ieee754-prof, libghc-data-default-dev (>= 0.7), > libghc-data-default-dev (<< 0.8), libghc-data-default-prof, libghc-dlist-dev > (>= 0.8), libghc-dlist-dev (<< 1.1), libghc-dlist-prof, libghc-extra-dev (>= > 1.6.17), libghc-extra-dev (<< 1.8), libghc-extra-prof, libghc-hashable-dev > (>= 1.2.1.0), libghc-hashable-dev (<< 1.5), libghc-hashable-prof, > libghc-src-meta-dev (>= 0.8), libghc-src-meta-dev (<< 0.9), > libghc-src-meta-prof, libghc-hint-dev (>= 0.7), libghc-hint-dev (<< 0.10), > libghc-hint-prof, libghc-interpolate-dev (>= 0.2.0), libghc-interpolate-dev > (<< 1.0), libghc-interpolate-prof, libghc-lens-dev (>= 4.10), libghc-lens-dev > (<< 5.3), libghc-lens-prof, libghc-ordered-containers-dev (>= 0.2), > libghc-ordered-containers-dev (<< 0.3), libghc-ordered-containers-prof, > libghc-pretty-show-dev (>= 1.9), libghc-pretty-show-dev (<< 2.0), > libghc-pretty-show-prof, libghc-prettyprinter-dev (>= 1.2.0.1), > libghc-prettyprinter-dev (<< 1.8), libghc-prettyprinter-prof, > libghc-primitive-dev (>= 0.5.0.1), libghc-primitive-dev (<< 1.0), > libghc-primitive-prof, libghc-quickcheck-text-dev, > libghc-quickcheck-text-prof, libghc-tasty-dev (>= 1.2), libghc-tasty-dev (<< > 1.5), libghc-tasty-prof, libghc-tasty-hunit-dev, libghc-tasty-hunit-prof, > libghc-tasty-quickcheck-dev, libghc-tasty-quickcheck-prof, > libghc-temporary-dev (>= 1.2.1), libghc-temporary-dev (<< 1.4), > libghc-temporary-prof, libghc-terminal-size-dev (>= 0.3), > libghc-terminal-size-dev (<< 0.4), libghc-terminal-size-prof, > libghc-trifecta-dev (>= 1.7.1.1), libghc-trifecta-dev (<< 2.2), > libghc-trifecta-prof, libghc-unordered-containers-dev (>= 0.2.3.3), > libghc-unordered-containers-dev (<< 0.3), libghc-unordered-containers-prof, > libghc-vector-dev (>= 0.11), libghc-vector-dev (<< 1.0), libghc-vector-prof, > libghc-vector-binary-instances-dev (>= 0.2.3.5), > libghc-vector-binary-instances-dev (<< 0.3), > libghc-vector-binary-instances-prof, libghc-yaml-dev (>= 0.11), > libghc-yaml-dev (<< 0.12), libghc-yaml-prof, libghc-glob-dev, > libghc-glob-prof, libghc-stringsearch-dev, libghc-stringsearch-prof, > build-essential, fakeroot, ghc-doc, libghc-aeson-doc, > libghc-aeson-pretty-doc, libghc-ansi-terminal-doc, libghc-async-doc, > libghc-attoparsec-doc, libghc-b
Processed: libervia-backend: start fails without pre-existing configuration
Processing commands for cont...@bugs.debian.org: > notfound 1056163 0.9.0~hg4144-1 Bug #1056163 [libervia-backend] libervia-backend: start fails without pre-existing configuration Ignoring request to alter found versions of bug #1056163 to the same values previously set > fixed 1056163 0.9.0~hg4144-1 Bug #1056163 [libervia-backend] libervia-backend: start fails without pre-existing configuration Marked as fixed in versions libervia-backend/0.9.0~hg4144-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1056163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056163 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1036255: marked as done (python3-onelogin-saml2: FTBFS in bookworm and above: AssertionError: "Invalid issuer in the Logout Request" does not match "Could not validate timestamp: expired. Check sy
Your message dated Sat, 18 Nov 2023 01:07:40 + with message-id and subject line Bug#1036255: fixed in python3-onelogin-saml2 1.12.0-3 has caused the Debian Bug report #1036255, regarding python3-onelogin-saml2: FTBFS in bookworm and above: AssertionError: "Invalid issuer in the Logout Request" does not match "Could not validate timestamp: expired. Check system clock.)" 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.) -- 1036255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036255 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python3-onelogin-saml2 Version: 1.12.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230517 ftbfs-bookworm Hi, During a rebuild of all packages in testing (bookworm), your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --with python3 --buildsystem=pybuild >dh_update_autotools_config -O--buildsystem=pybuild >dh_autoreconf -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild > I: pybuild base:240: python3.11 setup.py config > running config >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:240: /usr/bin/python3 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.11/build/onelogin > copying src/onelogin/__init__.py -> > /<>/.pybuild/cpython3_3.11/build/onelogin > creating /<>/.pybuild/cpython3_3.11/build/onelogin/saml2 > copying src/onelogin/saml2/xml_templates.py -> > /<>/.pybuild/cpython3_3.11/build/onelogin/saml2 > copying src/onelogin/saml2/constants.py -> > /<>/.pybuild/cpython3_3.11/build/onelogin/saml2 > copying src/onelogin/saml2/logout_request.py -> > /<>/.pybuild/cpython3_3.11/build/onelogin/saml2 > copying src/onelogin/saml2/logout_response.py -> > /<>/.pybuild/cpython3_3.11/build/onelogin/saml2 > copying src/onelogin/saml2/__init__.py -> > /<>/.pybuild/cpython3_3.11/build/onelogin/saml2 > copying src/onelogin/saml2/compat.py -> > /<>/.pybuild/cpython3_3.11/build/onelogin/saml2 > copying src/onelogin/saml2/response.py -> > /<>/.pybuild/cpython3_3.11/build/onelogin/saml2 > copying src/onelogin/saml2/settings.py -> > /<>/.pybuild/cpython3_3.11/build/onelogin/saml2 > copying src/onelogin/saml2/auth.py -> > /<>/.pybuild/cpython3_3.11/build/onelogin/saml2 > copying src/onelogin/saml2/idp_metadata_parser.py -> > /<>/.pybuild/cpython3_3.11/build/onelogin/saml2 > copying src/onelogin/saml2/authn_request.py -> > /<>/.pybuild/cpython3_3.11/build/onelogin/saml2 > copying src/onelogin/saml2/errors.py -> > /<>/.pybuild/cpython3_3.11/build/onelogin/saml2 > copying src/onelogin/saml2/xml_utils.py -> > /<>/.pybuild/cpython3_3.11/build/onelogin/saml2 > copying src/onelogin/saml2/utils.py -> > /<>/.pybuild/cpython3_3.11/build/onelogin/saml2 > copying src/onelogin/saml2/xmlparser.py -> > /<>/.pybuild/cpython3_3.11/build/onelogin/saml2 > copying src/onelogin/saml2/metadata.py -> > /<>/.pybuild/cpython3_3.11/build/onelogin/saml2 > running egg_info > creating src/python3_saml.egg-info > writing src/python3_saml.egg-info/PKG-INFO > writing dependency_links to src/python3_saml.egg-info/dependency_links.txt > writing requirements to src/python3_saml.egg-info/requires.txt > writing top-level names to src/python3_saml.egg-info/top_level.txt > writing manifest file 'src/python3_saml.egg-info/SOURCES.txt' > reading manifest file 'src/python3_saml.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > warning: no previously-included files matching '__pycache__' found under > directory '*' > warning: no previously-included files matching '*.py[co]' found under > directory '*' > adding license file 'LICENSE' > writing manifest file 'src/python3_saml.egg-info/SOURCES.txt' > /usr/lib/python3/dist-packages/setuptools/command/build_py.py:202: > SetuptoolsDeprecationWarning: Installing 'onelogin/saml2.schemas' as data > is deprecated, please list it in `packages`. > !! > > > > # Package would be ignored # > > Python recognizes 'onelogin/saml2.schemas' as an importable package, > but it is not listed in the `packages` configuration of setuptools. > > 'onelogin/saml2.schemas' has been automatically added to the distribution > only > because it may contain data files, but this behavior is likely to change > in future versions of setuptools (and therefore is considered deprecated). > > Please make sure that 'onelogin/saml2.schemas' is included as a package > by
Bug#1036255: python3-onelogin-saml2: FTBFS in testing: AssertionError: "Invalid issuer in the Logout Request" does not match "Could not validate timestamp: expired. Check system clock.)"
owner 1036255 ! thanks El 18/5/23 a las 20:36, Andrey Rakhmatullin escribió: https://github.com/SAML-Toolkits/python-saml/commit/a6a21109179571c9ca23f92e03017759741603c2 looks like a fix for this, though I haven't tested it. Thanks a lot for the hint. Yes, such commit was the beginning of the fix, but two additional commits after that one were also required. I plan to fix this in stable as well. Thanks.
Processed: Re: Bug#1036255: python3-onelogin-saml2: FTBFS in testing: AssertionError: "Invalid issuer in the Logout Request" does not match "Could not validate timestamp: expired. Check system clock.)
Processing commands for cont...@bugs.debian.org: > owner 1036255 ! Bug #1036255 [src:python3-onelogin-saml2] python3-onelogin-saml2: FTBFS in bookworm and above: AssertionError: "Invalid issuer in the Logout Request" does not match "Could not validate timestamp: expired. Check system clock.)" Owner recorded as Santiago Vila . > thanks Stopping processing here. Please contact me if you need assistance. -- 1036255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036255 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1036255 marked as pending in python3-onelogin-saml2
Processing control commands: > tag -1 pending Bug #1036255 [src:python3-onelogin-saml2] python3-onelogin-saml2: FTBFS in bookworm and above: AssertionError: "Invalid issuer in the Logout Request" does not match "Could not validate timestamp: expired. Check system clock.)" Added tag(s) pending. -- 1036255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036255 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1036255: marked as pending in python3-onelogin-saml2
Control: tag -1 pending Hello, Bug #1036255 in python3-onelogin-saml2 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python3-onelogin-saml2/-/commit/b451bb068aec04d48379c7db5a10b7e78ee19a09 Apply three upstream commits to fix expired test payloads. Closes: #1036255. (this message was generated automatically) -- Greetings https://bugs.debian.org/1036255
Bug#1056163: libervia-backend: start fails without pre-existing configuration
Package: libervia-backend Severity: serious Version: 0.9.0~hg3993-4 Tags: bookworm When there is no pre-existing configuration (`~/.local/share/libervia/`), starting `libervia-backend fg` fails with an exception: ``` File "/usr/share/libervia/sat/memory/migration/env.py", line 8, in from sat.memory import sqla_config ModuleNotFoundError: No module named 'sat' 2023-11-18T00:00:00+ /!\ Can't upgrade database (exit code 1) ```
Bug#1052724: u-boot: FTBFS: cc1: error: ‘-fcf-protection=full’ is not supported for this target
On 2023-09-26, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): ... >> cc1: error: ‘-fcf-protection=full’ is not supported for this target >> make[3]: *** [/<>/Makefile:1816: include/generated/env.in] >> Error 1 Because several of the qemu targets for the u-boot-qemu arch:all are cross-built, when dpkg-buildflags enabled the hardening=+branch feature by default, this broke some of the cross builds which do not support the resulting -fcf-protection=full feature added to the default compiler flags. I have disabled this feature in git for now, although a better fix might be preferred allowing this to be used on other targets where it did not cause an issue. live well, vagrant signature.asc Description: PGP signature
Processed: Bug#1052724 marked as pending in u-boot
Processing control commands: > tag -1 pending Bug #1052724 [src:u-boot] u-boot: FTBFS: cc1: error: ‘-fcf-protection=full’ is not supported for this target Added tag(s) pending. -- 1052724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052724 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052724: marked as pending in u-boot
Control: tag -1 pending Hello, Bug #1052724 in u-boot reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/u-boot/-/commit/8ecfe9557fcfd217c2df88f183a4c3b3144891eb debian/rules: Disable hardening branch feature to fix arch:all build. (Closes: #1052724) (this message was generated automatically) -- Greetings https://bugs.debian.org/1052724
Bug#1041999: marked as done (tgt: Drop glusterfs support for 32-bit architectures)
Your message dated Fri, 17 Nov 2023 22:24:54 + with message-id and subject line Bug#1041999: fixed in tgt 1:1.0.85-1.1 has caused the Debian Bug report #1041999, regarding tgt: Drop glusterfs support for 32-bit architectures 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.) -- 1041999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041999 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tgt Version: 1:1.0.85-1 Severity: important Hello, because of the bug #1039604 [0] I will drop glusterfs completly from non x64 architectures. You package has a reverse dependency on. So you should change your (build)-dependeny e.g. on libglusterfs-dev to: libglusterfs-dev [amd64 arm64 ppc64el ppc64 riscv64 mips64el s390x ia64 sparc64] In experimental with glusterfs 11.0-1 the !x64 support has been already dropped. I plan to upload it to unstable after the reverse dependencies are fixed. If you need help, please let me know :) [0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039604 -- System Information: Debian Release: 12.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-10-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: tgt Source-Version: 1:1.0.85-1.1 Done: Chris Hofstaedtler We believe that the bug you reported is fixed in the latest version of tgt, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1041...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Hofstaedtler (supplier of updated tgt package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 17 Nov 2023 22:35:38 +0100 Source: tgt Architecture: source Version: 1:1.0.85-1.1 Distribution: unstable Urgency: medium Maintainer: Apollon Oikonomopoulos Changed-By: Chris Hofstaedtler Closes: 1041999 Changes: tgt (1:1.0.85-1.1) unstable; urgency=medium . * Non-maintainer upload. . [ Michael Prokop ] * Build tgt-glusterfs only on 64bit architectures. Given glusterfs 11 restricted availability to 64bit architectures, stop building tgt-glusterfs on 32bit architectures. Limit Build-Depends: libglusterfs-dev too. Thanks to Patrick Matthäi (Closes: #1041999) Checksums-Sha1: a19bece0d3e73c8da2bea383efe65ae76850bf45 2252 tgt_1.0.85-1.1.dsc 3f1739f8cb0ab821c080622c39c313501f0a31d3 14228 tgt_1.0.85-1.1.debian.tar.xz 447126f50433bde8673a88bdf291c89bcd30fd29 8455 tgt_1.0.85-1.1_arm64.buildinfo Checksums-Sha256: 103c2356b5e3c746d36d93fbb76d8a83c900f4cd19d739b2aac33e51004232df 2252 tgt_1.0.85-1.1.dsc 15dd54b7342e757cc5b73a9d9d41d15d2f0435ab2449a370f1c42bf02d320c92 14228 tgt_1.0.85-1.1.debian.tar.xz edaf47e91afb2fa3b96946a47e19793d480a2f54990049f4601ecf2843f4a6a7 8455 tgt_1.0.85-1.1_arm64.buildinfo Files: 3f48575d5a53c28d4425086cd906f35d 2252 net optional tgt_1.0.85-1.1.dsc 4e3d9e0f4946149fc31ea8be12c4de5e 14228 net optional tgt_1.0.85-1.1.debian.tar.xz 872e399df27bdb6fe3d7e7915d291866 8455 net optional tgt_1.0.85-1.1_arm64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmVX4jUACgkQXBPW25MF LgO4Nw//cCcFSmrkEQyxwiDrnr4X2xfn7s/R3kN9oioOp/N2UiL0bXC9zqCQXBOh oTTPGKL77Zyf47BPbgYdKIIJ0NqoUrrmw/kmg5tBQPByeN3Qvgq/a8mqDTty7qDy 7mtLWMT9H7bqS744lbCKBqGy5X6N0Cmn5CuiWe3xlXeZmg0kS5Gf7unqshAjqzp7 1xg1J16sEg12QoPTmZkXeRxYURBsIvk2lxQ6wXXNi1NWfLF5XwtnqZjmLvLvZWFD qYlGNuIXm4WOQ9V4xTG8pXO30Dtij2qttmXpFwr96mYa652jEuD7jQZAxUlAqPkN Xn2mJINAcayAg4MdyfJQy3yBYbcQeM946QKbWUh+m6kbKC5HdkmPW5AVlc2LVc4+ CyfG+7sEYHgKVI051FoBSji3NYEGeQYZBx93V/xNzt3J16QXZIEE1y9YgskLXTEf pR25tbcbEr9DgB4PhkXS5vj+ZSpSzHaLeqjnwldoWj/M3esh0pVyE0Yte1L8t8r4 kuJiJzWGQYXaBiQwpE4JhGkgEMKyCrJL/KQCCAm9xM5/+w4X7/jQv4ANQUEHa2pH qE0NA++W3ijyMeh5ppUF7qubit68Fsg7f5anV8xpD8vU9G88Ked+kw4bLqGpFnG7 DttU+RN0vM6ZIZ6Rsx83h1lBILBksQHb15psp5QwFZdAa4sCI+8= =Ak23 -END PGP SIGNATURE End Mess
Bug#1054814: criu: FTBFS: make[2]: git: No such file or directory
Hi This should be fixed with 3.18 upstream, so instread of an isolated fix I'm rather going to do that anyway. Can hopefully tackle it soon over the next few days. Regards, Salvatore
Bug#1055492: appstream-generator: FTBFS with ldc 1.35
Package: appstream-generator Followup-For: Bug #1055492 X-Debbugs-Cc: witold.bary...@gmail.com FYI. The underlying issue was "fixed" in appstream-generator upstream and is part of 0.9.1 release from the last week. This was done by making rpmmd backend optional (one requiring std.xml which was removed from Phobos). Note however, that for 0.9.1 to compile, one might need to update some build depdencies. And make libappstream-dev/libappstream-compose-dev to be >= 1.0 After updating libappstream-dev and libappstream-compose-dev to 1.0 (in experimental), I was able to build appstream-generator 0.9.1+ without issues.
Bug#1051433: mysql-workbench: FTBFS: error: ‘int64_t’ has not been declared in ‘std’
Control: tags -1 patch
The attached patch resolves the build failure.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1diff -Nru mysql-workbench-8.0.32+dfsg/debian/changelog
mysql-workbench-8.0.32+dfsg/debian/changelog
--- mysql-workbench-8.0.32+dfsg/debian/changelog2023-03-22
04:10:41.0 +0100
+++ mysql-workbench-8.0.32+dfsg/debian/changelog2023-11-17
21:08:37.0 +0100
@@ -1,3 +1,11 @@
+mysql-workbench (8.0.32+dfsg-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Add patch to fix FTBFS with GCC 13.
+(closes: #1051433)
+
+ -- Bas Couwenberg Fri, 17 Nov 2023 21:08:37 +0100
+
mysql-workbench (8.0.32+dfsg-1) unstable; urgency=medium
* New upstream release.
diff -Nru mysql-workbench-8.0.32+dfsg/debian/patches/gcc-13.patch
mysql-workbench-8.0.32+dfsg/debian/patches/gcc-13.patch
--- mysql-workbench-8.0.32+dfsg/debian/patches/gcc-13.patch 1970-01-01
01:00:00.0 +0100
+++ mysql-workbench-8.0.32+dfsg/debian/patches/gcc-13.patch 2023-11-17
21:08:37.0 +0100
@@ -0,0 +1,69 @@
+Description: Include for int64_t.
+ Per https://gcc.gnu.org/gcc-13/porting_to.html
+Author: Bas Couwenberg
+
+--- a/library/base/base/util_functions.h
b/library/base/base/util_functions.h
+@@ -53,6 +53,8 @@
+ #define BASE_PATH_SEPARATOR_STR "/"
+ #endif
+
++#include
++
+ #define BASE_ORDPTR(value) ((void *)(unsigned long)(value))
+
+ // TODO: move Windows specific stuff to base.windows library.
+--- a/library/cdbc/src/driver_manager.h
b/library/cdbc/src/driver_manager.h
+@@ -33,6 +33,8 @@
+ #include "grts/structs.db.mgmt.h"
+ #include
+
++#include
++
+ namespace wb {
+ class SSHTunnel;
+ }
+--- a/library/base/base/string_utilities.h
b/library/base/base/string_utilities.h
+@@ -43,6 +43,8 @@
+ #include
+ #include
+
++#include
++
+ #define _(s) s // TODO: replace with localization code.
+
+ using std::int64_t;
+--- a/library/base/base/utf8string.h
b/library/base/base/utf8string.h
+@@ -30,6 +30,7 @@
+ #include
+ #include
+ #include
++#include
+
+ namespace base {
+ /**
+--- a/library/forms/mforms/treeview.h
b/library/forms/mforms/treeview.h
+@@ -25,6 +25,8 @@
+
+ #include
+
++#include
++
+ /**
+ * Implementation of a control class for a treeview control based on node
objects.
+ */
+--- a/backend/wbpublic/sqlide/sqlide_generics_private.h
b/backend/wbpublic/sqlide/sqlide_generics_private.h
+@@ -31,6 +31,8 @@
+ #include
+ #include
+
++#include
++
+ namespace sqlide {
+
+ using namespace sqlite;
diff -Nru mysql-workbench-8.0.32+dfsg/debian/patches/series
mysql-workbench-8.0.32+dfsg/debian/patches/series
--- mysql-workbench-8.0.32+dfsg/debian/patches/series 2021-05-31
14:24:05.0 +0200
+++ mysql-workbench-8.0.32+dfsg/debian/patches/series 2023-11-17
21:04:08.0 +0100
@@ -10,3 +10,4 @@
specify-char-signedness.patch
un-mysql.patch
#~wbcopytables-rpath.patch
+gcc-13.patch
diff -Nru mysql-workbench-8.0.32+dfsg/debian/rules
mysql-workbench-8.0.32+dfsg/debian/rules
--- mysql-workbench-8.0.32+dfsg/debian/rules2023-03-22 03:56:22.0
+0100
+++ mysql-workbench-8.0.32+dfsg/debian/rules2023-11-17 21:08:37.0
+0100
@@ -9,7 +9,7 @@
## "bindnow" causes run-time errors:
#export DEB_BUILD_MAINT_OPTIONS=hardening=+bindnow
-export DEB_CPPFLAGS_MAINT_APPEND= -Wno-error=deprecated-declarations
-Wno-error=maybe-uninitialized
+export DEB_CPPFLAGS_MAINT_APPEND= -Wno-error=deprecated-declarations
-Wno-error=maybe-uninitialized -Wno-error=c++20-compat
-Wno-error=overloaded-virtual=
# -Wno-error=deprecated-copy -Wno-error=format-overflow=
# -std=c++11
Processed: mysql-workbench: FTBFS: error: ‘int64_t’ has not been declared in ‘std’
Processing control commands: > tags -1 patch Bug #1051433 [src:mysql-workbench] mysql-workbench: FTBFS: error: ‘int64_t’ has not been declared in ‘std’ Added tag(s) patch. -- 1051433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051433 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1056153, severity of 1056153 is important, reassign 1056153 to src:linux, tagging 1056153
Processing commands for cont...@bugs.debian.org: > tags 1056153 - a11y Bug #1056153 [6.1.0-0.deb11.9-amd64] 6.1.0-0.deb11.9-amd64: Linux version 6.1.0-0.deb11.9-amd64 booting to black screen, but 6.1.0-0.deb11.7-amd64 works Warning: Unknown package '6.1.0-0.deb11.9-amd64' Removed tag(s) a11y. Warning: Unknown package '6.1.0-0.deb11.9-amd64' > severity 1056153 important Bug #1056153 [6.1.0-0.deb11.9-amd64] 6.1.0-0.deb11.9-amd64: Linux version 6.1.0-0.deb11.9-amd64 booting to black screen, but 6.1.0-0.deb11.7-amd64 works Warning: Unknown package '6.1.0-0.deb11.9-amd64' Severity set to 'important' from 'critical' Warning: Unknown package '6.1.0-0.deb11.9-amd64' > reassign 1056153 src:linux 6.1.27-1~bpo11+1 Bug #1056153 [6.1.0-0.deb11.9-amd64] 6.1.0-0.deb11.9-amd64: Linux version 6.1.0-0.deb11.9-amd64 booting to black screen, but 6.1.0-0.deb11.7-amd64 works Warning: Unknown package '6.1.0-0.deb11.9-amd64' Bug reassigned from package '6.1.0-0.deb11.9-amd64' to 'src:linux'. Ignoring request to alter found versions of bug #1056153 to the same values previously set Ignoring request to alter fixed versions of bug #1056153 to the same values previously set Bug #1056153 [src:linux] 6.1.0-0.deb11.9-amd64: Linux version 6.1.0-0.deb11.9-amd64 booting to black screen, but 6.1.0-0.deb11.7-amd64 works Marked as found in versions linux/6.1.27-1~bpo11+1. > # as upgraded kernel is not the most recent one > tags 1056153 + moreinfo Bug #1056153 [src:linux] 6.1.0-0.deb11.9-amd64: Linux version 6.1.0-0.deb11.9-amd64 booting to black screen, but 6.1.0-0.deb11.7-amd64 works Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 1056153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056153 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056153: 6.1.0-0.deb11.9-amd64: Linux version 6.1.0-0.deb11.9-amd64 booting to black screen, but 6.1.0-0.deb11.7-amd64 works
Package: 6.1.0-0.deb11.9-amd64 Version: Linux version 6.1.0-0.deb11.9-amd64 Severity: critical Tags: a11y Justification: breaks the whole system Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Upgrading to Kernel Linux 6.1.0-0.deb11.9-amd64 * What exactly did you do (or not do) that was effective (or ineffective)? Booting with Kernel Linux 6.1.0-0.deb11.7-amd64 still works and the system runs stable. I compared the kernel config files without finding any particular differences. I compared the boot log of both kernels without finding any particular differences, except this: Both boot logs shows this error: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 4: a6020408 mce: [Hardware Error]: TSC 0 ADDR fef13bc0 mce: [Hardware Error]: PROCESSOR 0:506ca TIME 1700060631 SOCKET 0 APIC 0 microcode 28 The board is brand new and has been replaced twice, always with the same error message. * What was the outcome of this action? I found no evidence of an error in the boot log or differences in the config file * What outcome did you expect instead? Helpful errors or config parameter *** End of the template - remove these template lines *** -- System Information: Debian Release: 11.8 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-0.deb11.7-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages 6.1.0-0.deb11.9-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.140 ii kmod28-1 ii linux-base 4.6 Versions of packages 6.1.0-0.deb11.9-amd64 recommends: ii apparmor 2.13.6-10 ii firmware-linux-free 20200122-1 Versions of packages 6.1.0-0.deb11.9-amd64 suggests: pn debian-kernel-handbook ii grub-pc 2.06-3~deb11u6 pn linux-doc-6.1
Bug#1054772: marked as done (python-crontab: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)
Your message dated Fri, 17 Nov 2023 20:44:51 +
with message-id
and subject line Bug#1054772: fixed in python-crontab 3.0.0-2
has caused the Debian Bug report #1054772,
regarding python-crontab: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.11 returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1054772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054772
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-crontab
Version: 3.0.0-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):
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:110: Building wheel for python3.11 with "build"
> module
> I: pybuild base:310: python3.11 -m build --skip-dependency-check
> --no-isolation --wheel --outdir
> /<>/.pybuild/cpython3_3.11_crontab
> * Building wheel...
> /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:265:
> UserWarning: Unknown distribution option: 'release'
> warnings.warn(msg)
> running bdist_wheel
> running build
> running build_py
> creating build
> creating build/lib
> copying crontab.py -> build/lib
> copying crontabs.py -> build/lib
> copying cronlog.py -> build/lib
> installing to build/bdist.linux-x86_64/wheel
> running install
> running install_lib
> creating build/bdist.linux-x86_64
> creating build/bdist.linux-x86_64/wheel
> copying build/lib/crontab.py -> build/bdist.linux-x86_64/wheel
> copying build/lib/cronlog.py -> build/bdist.linux-x86_64/wheel
> copying build/lib/crontabs.py -> build/bdist.linux-x86_64/wheel
> running install_egg_info
> running egg_info
> writing python_crontab.egg-info/PKG-INFO
> writing dependency_links to python_crontab.egg-info/dependency_links.txt
> writing requirements to python_crontab.egg-info/requires.txt
> writing top-level names to python_crontab.egg-info/top_level.txt
> writing manifest file 'python_crontab.egg-info/SOURCES.txt'
> reading manifest file 'python_crontab.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'COPYING'
> adding license file 'AUTHORS'
> writing manifest file 'python_crontab.egg-info/SOURCES.txt'
> Copying python_crontab.egg-info to
> build/bdist.linux-x86_64/wheel/python_crontab-3.0.0.egg-info
> running install_scripts
> creating build/bdist.linux-x86_64/wheel/python_crontab-3.0.0.dist-info/WHEEL
> creating
> '/<>/.pybuild/cpython3_3.11_crontab/.tmp-xnironfm/python_crontab-3.0.0-py3-none-any.whl'
> and adding 'build/bdist.linux-x86_64/wheel' to it
> adding 'cronlog.py'
> adding 'crontab.py'
> adding 'crontabs.py'
> adding 'python_crontab-3.0.0.dist-info/AUTHORS'
> adding 'python_crontab-3.0.0.dist-info/COPYING'
> adding 'python_crontab-3.0.0.dist-info/METADATA'
> adding 'python_crontab-3.0.0.dist-info/WHEEL'
> adding 'python_crontab-3.0.0.dist-info/top_level.txt'
> adding 'python_crontab-3.0.0.dist-info/RECORD'
> removing build/bdist.linux-x86_64/wheel
> Successfully built python_crontab-3.0.0-py3-none-any.whl
> I: pybuild plugin_pyproject:122: Unpacking wheel built for python3.11 with
> "installer" module
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:310: cd
> /<>/.pybuild/cpython3_3.11_crontab/build; python3.11 -m pytest
> tests
> = test session starts
> ==
> platform linux -- Python 3.11.6, pytest-7.4.3, pluggy-1.3.0
> rootdir: /<>/.pybuild/cpython3_3.11_crontab/build
> collected 176 items
>
> tests/test_compatibility.py s[
> 5%]
> tests/test_context.py . [
> 5%]
> tests/test_croniter.py . [
> 8%]
> tests/test_crontabs.py . [
> 11%]
> tests/test_description.py ss [
> 12%]
> tests/test_enums.py [
> 17%]
> tests/test_env.py ...[
> 23%]
> tests/test_equality.py [
> 25%]
> tests/test_every.py .
Bug#1055581: marked as done (libgeo-gdal-ffi-perl: FTBFS with GDAL 3.8.0)
Your message dated Fri, 17 Nov 2023 20:39:54 +
with message-id
and subject line Bug#1055581: fixed in libgeo-gdal-ffi-perl 0.1-4
has caused the Debian Bug report #1055581,
regarding libgeo-gdal-ffi-perl: FTBFS with GDAL 3.8.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1055581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055581
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgeo-gdal-ffi-perl
Version: 0.1-2
Severity: important
Tags: ftbfs
User: debian-...@lists.debian.org
Usertags: gdal-3.8
Dear Maintainer,
Your package FTBFS with GDAL 3.8.0 from experimental:
Cannot write feature at
/build/libgeo-gdal-ffi-perl-0.1/blib/lib/Geo/GDAL/FFI/Driver.pm line 49.
Geo::GDAL::FFI::Driver::Create(Geo::GDAL::FFI::Driver=SCALAR(0x557a150d4c40),
"/vsimem/test.tiff", 10) called at t/vsistdout.t line 63
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 2 just after 1.
t/vsistdout.t ..
The full buildlog is attached.
Kind Regards,
Bas
dpkg-checkbuilddeps: error: Unmet build dependencies: libffi-platypus-perl
libgdal-dev libpkgconfig-perl
[1;33mW: Unmet build-dependency in source[0m
dh clean
dh_clean
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building libgeo-gdal-ffi-perl using existing
./libgeo-gdal-ffi-perl_0.1.orig.tar.gz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: building libgeo-gdal-ffi-perl in
libgeo-gdal-ffi-perl_0.1-2.1.debian.tar.xz
dpkg-source: info: building libgeo-gdal-ffi-perl in
libgeo-gdal-ffi-perl_0.1-2.1.dsc
[0mI: Generating source changes file for original dsc[0m
dpkg-genchanges: info: not including original source code in upload
I: Copying COW directory
I: forking: rm -rf /var/cache/pbuilder/build/cow.2025006
I: forking: cp -al /var/cache/pbuilder/base-sid+rebuild.cow
/var/cache/pbuilder/build/cow.2025006
I: removed stale ilistfile /var/cache/pbuilder/build/cow.2025006/.ilist
I: forking: chroot /var/cache/pbuilder/build/cow.2025006 cowdancer-ilistcreate
/.ilist 'find . -xdev -path ./home -prune -o \( \( -type l -o -type f \) -a
-links +1 -print0 \) | xargs -0 stat --format '%d %i ''
I: Invoking pbuilder
I: forking: pbuilder build --debbuildopts --debbuildopts --buildplace
/var/cache/pbuilder/build/cow.2025006 --buildresult /var/cache/pbuilder/result/
--mirror http://ftp.nl.debian.org/debian/ --distribution sid --no-targz
--internal-chrootexec 'chroot /var/cache/pbuilder/build/cow.2025006 cow-shell'
/home/bas/tmp/debian/libgeo-gdal-ffi-perl_0.1-2.1.dsc
[0mI: Running in no-targz mode[0m
[0mI: pbuilder: network access will be disabled during build[0m
[0mI: Current time: Wed Nov 8 13:08:40 CET 2023[0m
[0mI: pbuilder-time-stamp: 1699445320[0m
[0mI: copying local configuration[0m
[1;33mW: --override-config is not set; not updating apt.conf Read the manpage
for details.[0m
[0mI: mounting /proc filesystem[0m
[0mI: mounting /sys filesystem[0m
[0mI: creating /{dev,run}/shm[0m
[0mI: mounting /dev/pts filesystem[0m
[0mI: redirecting /dev/ptmx to /dev/pts/ptmx[0m
[0mI: policy-rc.d already exists[0m
[0mI: Obtaining the cached apt archive contents[0m
[0mI: Copying source file[0m
[0mI: copying [/home/bas/tmp/debian/libgeo-gdal-ffi-perl_0.1-2.1.dsc][0m
[0mI: copying [/home/bas/tmp/debian/libgeo-gdal-ffi-perl_0.1.orig.tar.gz][0m
[0mI: copying
[/home/bas/tmp/debian/libgeo-gdal-ffi-perl_0.1-2.1.debian.tar.xz][0m
[0mI: Extracting source[0m
dpkg-source: warning: extracting unsigned source package
(libgeo-gdal-ffi-perl_0.1-2.1.dsc)
dpkg-source: info: extracting libgeo-gdal-ffi-perl in libgeo-gdal-ffi-perl-0.1
dpkg-source: info: unpacking libgeo-gdal-ffi-perl_0.1.orig.tar.gz
dpkg-source: info: unpacking libgeo-gdal-ffi-perl_0.1-2.1.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying geometry_pm-fix.patch
dpkg-source: info: applying prototypes-fix.patch
dpkg-source: info: applying platypus-declare-remove.patch
dpkg-source: info: applying gdal_so.patch
dpkg-source: info: applying test-fix.patch
dpkg-source: info: applying threads-fix.patch
[0mI: Not using root during the build.[0m
[0mI: Installing the build-deps[0m
-> Attempting to satisfy build-dependencies
-> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team
Description: Dummy package to satisfy dependencies with aptitude - created by
pbuilder
This package
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> found 1054546 3.1.4-1
Bug #1054546 {Done: Sebastian Andrzej Siewior }
[openssl] openssl: The engine interface seems to be broken.
Marked as found in versions openssl/3.1.4-1 and reopened.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1054546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054546
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Bug#1055581 marked as pending in libgeo-gdal-ffi-perl
Processing control commands: > tag -1 pending Bug #1055581 [src:libgeo-gdal-ffi-perl] libgeo-gdal-ffi-perl: FTBFS with GDAL 3.8.0 Added tag(s) pending. -- 1055581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055581 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1054772 marked as pending in python-crontab
Processing control commands:
> tag -1 pending
Bug #1054772 [src:python-crontab] python-crontab: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Added tag(s) pending.
--
1054772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054772
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1055581: marked as pending in libgeo-gdal-ffi-perl
Control: tag -1 pending Hello, Bug #1055581 in libgeo-gdal-ffi-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libgeo-gdal-ffi-perl/-/commit/0cffb84c3eff52c92938b1e9a4e134e4cededbfa Add patch to skip test that fails with GDAL 3.8.0. (closes: #1055581) (this message was generated automatically) -- Greetings https://bugs.debian.org/1055581
Bug#1054772: marked as pending in python-crontab
Control: tag -1 pending Hello, Bug #1054772 in python-crontab reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-crontab/-/commit/7f9a686cd02b825c7ca8e4469c9e4f9a02ae76da Add patch from upstream to fix test_19_frequency_at_month (Closes: #1054772). (this message was generated automatically) -- Greetings https://bugs.debian.org/1054772
Processed: block 1055891 with 1055581
Processing commands for cont...@bugs.debian.org: > block 1055891 with 1055581 Bug #1055891 [release.debian.org] transition: gdal 1055891 was blocked by: 1051433 1055891 was not blocking any bugs. Added blocking bug(s) of 1055891: 1055581 > thanks Stopping processing here. Please contact me if you need assistance. -- 1055891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055891 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reopening 1055581, severity of 1055581 is serious, tagging 1055581
Processing commands for cont...@bugs.debian.org:
> reopen 1055581
Bug #1055581 {Done: Bas Couwenberg }
[src:libgeo-gdal-ffi-perl] libgeo-gdal-ffi-perl: FTBFS with GDAL 3.8.0
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions libgeo-gdal-ffi-perl/0.1-3.
> severity 1055581 serious
Bug #1055581 [src:libgeo-gdal-ffi-perl] libgeo-gdal-ffi-perl: FTBFS with GDAL
3.8.0
Severity set to 'serious' from 'important'
> tags 1055581 - fixed-upstream
Bug #1055581 [src:libgeo-gdal-ffi-perl] libgeo-gdal-ffi-perl: FTBFS with GDAL
3.8.0
Removed tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1055581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055581
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1055922: rmatrix: ABI change in Matrix 1.6-2
On 14 November 2023 at 07:42, Dirk Eddelbuettel wrote: | | On 14 November 2023 at 12:26, Graham Inggs wrote: | | Hi Dirk | | | | On Tue, 14 Nov 2023 at 12:01, Dirk Eddelbuettel wrote: | | > Well that seems to be a) the wrong severity and b) the wrong package. | | | | Both are correct. We do not want rmatrix to migrate and break | | packages in testing. | | Doesn't 'normal' do that? I always get the shivers when I see 'serious' as I | fear that my package is at the risk of removal (which we of course Matrix | can't be 'really' given its systemic status from its "recommended" status | within R and very widespread use). | | | However, in this case, I only set the severity to match reality; | | rmatrix is already blocked from migrating due to the autopkgtest | | regressions. | | | | > We need to address the packages needing a rebuild. Mine (r-cran-lme4, | | > r-cran-rcppeigen). have been taken care of. | | | | Agreed, and rmatrix may need some new Breaks to allow the affected | | packages to migrate together. | | The issue is actually hugely problematic for CRAN and R Core, and there are | some discussions but no solutions. They do not have (formal) notions like | binary rebuild for parts where they distribute binaries, and no means of | reaching binary redistributors such as us. Oh well. At least it doesn't | happen often. | | Anyway. Now that you made it a bug I let you drive this. Upstream just made | an unrelated bugfix Matrix 1.6-3 which I just sent to unstable. There are two known failures left which the maintainer(s) do not want to fix. As I have fixed my dependents of package Matrix, I continue to find it unfair that I am being to an open bug requiring fixes via builds in other packages that are not mine. So I guess this bug will stay open 'forever' or until those packages get normal routine updates. Dirk | | Dirk | | -- | dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#1042646: dh-virtualenv: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx'
On Sun, Jul 30, 2023 at 08:22:59PM +0200, Lucas Nussbaum wrote:
> Source: dh-virtualenv
> Version: 1.2.2-1.3
> Severity: important
> Tags: ftbfs
> User: python-modules-t...@lists.alioth.debian.org
> Usertags: sphinx7.1
>
> Hi,
>
> dh-virtualenv fails to build with Sphinx 7.1 and docutils 0.20, both of which
> are currently available in experimental.
>
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > python3 setup.py build_sphinx
> > usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
> >or: setup.py --help [cmd1 cmd2 ...]
> >or: setup.py --help-commands
> >or: setup.py cmd --help
> >
> > error: invalid command 'build_sphinx'
> > make[1]: *** [debian/rules:28: override_dh_installdocs] Error 1
This bug resulted in dh-virtualenv being dropped from trixie.
The easy workaround is to drop the sphinx documentation.
The following debdiff makes the package build again:
dpkg-source: warning: extracting unsigned source package
(/home/uwe/debsrc/dh-virtualenv_1.2.2-1.4.dsc)
diff -Nru dh-virtualenv-1.2.2/debian/changelog
dh-virtualenv-1.2.2/debian/changelog
--- dh-virtualenv-1.2.2/debian/changelog2023-02-02 20:10:21.0
+0100
+++ dh-virtualenv-1.2.2/debian/changelog2023-11-17 19:40:18.0
+0100
@@ -1,3 +1,10 @@
+dh-virtualenv (1.2.2-1.4) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop Sphinx docs (Closes: #1042646)
+
+ -- Uwe Kleine-König Fri, 17 Nov 2023 19:40:18 +0100
+
dh-virtualenv (1.2.2-1.3) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru dh-virtualenv-1.2.2/debian/control dh-virtualenv-1.2.2/debian/control
--- dh-virtualenv-1.2.2/debian/control 2022-08-25 21:00:57.0 +0200
+++ dh-virtualenv-1.2.2/debian/control 2023-11-17 19:40:18.0 +0100
@@ -3,25 +3,16 @@
Priority: optional
Maintainer: Jyrki Pulliainen
Build-Depends: debhelper-compat (= 12), python3,
- python3-setuptools, python3-sphinx, python3-mock, dh-exec,
+ python3-setuptools, python3-mock, dh-exec,
dh-python, libjs-jquery, libjs-underscore,
-# python-sphinx-rtd-theme doesn't exist in distributions
-# predating Debian Jessie and Ubuntu Xenial. On these legacy
-# systems:
-# 1. Comment the dependency below.
-# 2. pip install sphinx_rtd_theme.
-# 3. Proceed with your build process (typically dpkg-build).
-# See https://github.com/spotify/dh-virtualenv/issues/230
- python3-sphinx-rtd-theme
Standards-Version: 4.5.0
Homepage: https://www.github.com/spotify/dh-virtualenv
Rules-Requires-Root: no
Package: dh-virtualenv
Architecture: all
-Depends: ${python3:Depends}, ${perl:Depends}, ${misc:Depends},
${sphinxdoc:Depends},
+Depends: ${python3:Depends}, ${perl:Depends}, ${misc:Depends},
virtualenv | python3-virtualenv (>= 1.7) | python${pyversion}-venv
-Built-Using: ${sphinxdoc:Built-Using}
Description: wrap and build Python packages using virtualenv
This package provides a dh sequencer that helps you to deploy your
virtualenv wrapped installation inside a Debian package.
diff -Nru dh-virtualenv-1.2.2/debian/rules dh-virtualenv-1.2.2/debian/rules
--- dh-virtualenv-1.2.2/debian/rules2022-08-25 21:00:57.0 +0200
+++ dh-virtualenv-1.2.2/debian/rules2023-11-17 19:39:38.0 +0100
@@ -22,9 +22,3 @@
override_dh_gencontrol:
dh_gencontrol -- -Vpyversion=$(PYTHON_VERSION)
-
-ifeq (,$(findstring nodoc, $(DEB_BUILD_OPTIONS)))
-override_dh_installdocs:
- python3 setup.py build_sphinx
- dh_installdocs doc/_build/html
-endif
I intend to nmu this package in a week from now with the above changes.
Best regards
Uwe
signature.asc
Description: PGP signature
Bug#1056147: midge possibly contains non-DFSG-free examples
Source: midge Version: 0.2.41-4 Severity: serious Justification: possible DFSG violation [Please do not Cc: me, as I’m “on the list,” so to say, and I prefer to reserve my inbox for private communication only. I’d have set up Mail-Followup-To:, but there doesn’t seem to be a way to make it point to the report being filed.] The source currently contains a number of covers/*.mg files that are, so far as I can tell, derivatives of songs for which there’re no indication of being out of copyright or ever released under a DFSG-compliant license. In particular, a cursory look at Wikipedia articles (below) do not seem to mention anything related to possible free culture status of the songs transcribed in paranoid.mg & wish_you_were_here.mg. http://en.wikipedia.org/wiki/Paranoid_(Black_Sabbath_album) http://en.wikipedia.org/wiki/Wish_You_Were_Here_(Pink_Floyd_song) I believe the source needs to be repackaged so to exclude the examples/covers/ directory entirely. -- FSF associate member #7257 np. The Last Refugee — Roger Waters
Bug#1056146: xsok possibly contains non-DFSG-free data files
Source: xsok
Version: 1.02-19
Severity: serious
Justification: possible DFSG violation
[Please do not Cc: me, as I’m “on the list,” so to say, and
I prefer to reserve my inbox for private communication only.
I’d have set up Mail-Followup-To:, but there doesn’t seem
to be a way to make it point to the report being filed.]
The xsok debian/copyright file seems to suggest that xsok
was created solely by Michael Bischoff:
$ tar --xz -xO -- debian/copyright < xsok_1.02-19.debian.tar.xz
This is Debian GNU/Linux's prepackaged version of xsok.
xsok was written by Michael Bischoff .
The upstream source was downloaded from
ftp://ftp.io.com/pub/mirror/FreeBSD/ports/distfiles/xsok-1.02-src.tar.gz
The current Debian maintainer is Peter Samuelson .
Much of the packaging work was done by previous Debian maintainers
Sven Rudolph and Joel Rosdahl.
Copyright (c) 1994 by Michael Bischoff (m...@mo.math.nat.tu-bs.de)
[GNU GPL 2+ notice follows.]
There’re two issues with this. First, xsok includes
doc/cyberbox.doc, authored by Doug Beeferman (I presume
lib/Cyberbox/ files are also derivatives rather than
original xsok work.) The .doc file (quoted below) appears
to allow verbatim redistribution of the respective game,
but there’s no indication that ‘modifications and derived
works’ are allowed (as DFSG requires) as well:
S O R T A F R E E W A R E N O T I C E
This game can be distributed freely and played free of charge. If you like
it, however, I wouldn't mind a small donation for the effort I put into
writing the program and (ughh!) in making the levels. I say "ughh!" because
making the levels was by far the more time-consuming of the two projects.
Neither is there any such indication on http://dougb.com/ .
(I intend to contact the author of Cyberbox shortly to comment
on this issue and (or) possibly re-release at least the
portions of xsok derived from the original game in DFSG-
compliant fashion.)
Worse still, the ‘screens’ (= maps, levels) included in
lib/Sokoban/ appear to mostly come from the original,
proprietary version(s) of Soko-Ban. Consider, e. g.:
http://web.archive.org/web/2023/https://www.mobygames.com/game/1715/soko-ban/
http://web.archive.org/web/20230407165659im_/https://cdn.mobygames.com/8e54fc3c-bee0-11ed-9c42-02420a000140.webp
http://web.archive.org/web/20230407165658im_/https://cdn.mobygames.com/0b7522d4-c204-11ed-ab6b-02420a000194.webp
The first Soko-Ban screen, identical to lib/Sokoban/screen.01 .
http://web.archive.org/web/20230407165658im_/https://cdn.mobygames.com/058c7f98-ab6b-11ed-aaf5-02420a00019c.webp
The second Soko-Ban screen, identical to lib/Sokoban/screen.02 .
Moreover, taking a look at an earlier curses-based implementation
of the game from [1], which (according to its README.v2, as
quoted below) borrows screens from ‘the PC-version’, we find
out that likely /all/ levels from 1 to 50 inclusive are taken
from other software, while several other levels (86‒88) are
derived from the same.
I’m not aware of any evidence to suggest that the original
Soko-Ban might be out of copyright or ever released as free
software, from whence I conclude it’s likely proprietary,
including the level designs.
The first thing I have to say is that I don't have the sources for SOKOBAN
under MS-DOS. I believe that this program is copyrighted. I took only the
idea and the screens of the PC-version.
[1] http://ibiblio.org/pub/linux/games/strategy/sokoban-src.tar.gz
bash$ diff -dbuF^\; -- \
<((tar -zxOv --wildcards -- \*/screen.\? < sokoban-src.tar.gz ; \
tar -zxOv --wildcards -- \*/screen.\?\? < sokoban-src.tar.gz) \
2>&1 | sed -e "s,^sokoban.*\\.,;LEVEL ,;") \
share/games/xsok/Sokoban.def | head -n23
--- /dev/fd/63
+++ share/games/xsok/Sokoban.def2019-01-05 12:10:54 +
@@ -1,3 +1,14 @@
+;WALLS
+12 f f ff 0 standard floor
+. 13 f f ff 4 target field
+#0 0 00 0 walls
+
+;OBJECTS
+@0 f 0101 2011 0 player
+$1 f 0100 02 1000 heavy box
+
+;MAXLEVEL 88
+;ATOP *$.
;LEVEL 1
#
# #
@@ -759,3 +770,521 @@ ;LEVEL 50
# ### ## #
# # ###
##
+;LEVEL 51
+#
--
FSF associate member #7257 http://am-1.org/~ivan/
Processed: bug 1056143 is forwarded to https://rt.cpan.org/Ticket/Display.html?id=150480
Processing commands for cont...@bugs.debian.org: > forwarded 1056143 https://rt.cpan.org/Ticket/Display.html?id=150480 Bug #1056143 [src:libeval-context-perl] libeval-context-perl: t/012_safe.t fails Set Bug forwarded-to-address to 'https://rt.cpan.org/Ticket/Display.html?id=150480'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1056143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056143 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056143: libeval-context-perl: t/012_safe.t fails
Source: libeval-context-perl
Version: 0.09.11-5
Severity: serious
Tags: ftbfs trixie sid
Justification: fails to build from source
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
As noted by ci.debian.net, t/012_safe.t started to fail recently:
# Failed test 'Test STDOUT'
# at t/012_safe.t line 127.
# got: '`- A = 1 [S1]
# '
# expected: '
# `- A = 1 [S1]
# '
# |- CURRENT_RUNNING_PACKAGE = TEST [S1]
# |- FILE = t/012_safe.t [S2]
# |- INTERACTION [H3]
# | |- DIE = CODE(0x5600b3ac9f50) [C4]
# | |- EVAL_DIE = CODE(0x5600b3aca058) [C5]
# | |- INFO = CODE(0x5600b3ac9ba8) [C6]
# | `- WARN = CODE(0x5600b2dc5f18) [C7]
# |- LATEST_CODE = #line 0 'Anonymous_called_at_t_012_safe.t:121'[\n]# Note:
evaluated PRE_CODE before running SAFE code[\n]=comment[\n][\n][\n]package TEST
;[\n]use Data::TreeDumper;[\n][\n][\n][\n]=cut[\n][\n]# PRE_CODE[\n][\n]#line 0
'Anonymous_called_at_t_012_safe.t:121'[\n]# CODE[\n]DumpTree({A => 1}) ;[\n]#
POST_CODE[\n][\n]#end of context 'Anonymous_called_at_t_012_safe.t:121'[\n]
[S8]
# |- LINE = 116 [S9]
# |- NAME = Anonymous [S10]
# |- PACKAGE = TEST [S11]
# |- REMOVE_PACKAGE_AFTER_EVAL = 1 [S12]
# `- SAFE (no elements) [H13]
# Looks like you failed 1 test of 22.
t/012_safe.t
ok 1 - unsafe code, using default safe
ok 2 - unsafe code
ok 3 - Invalid SAFE definition
ok 4 - PRE_SAFE_CODE error
ok 5 - PRE_SAFE_CODE
ok 6 - use strict by default
ok 7 - USE_STRICT
ok 8 - COMPARTMENT
ok 9 - first eval package
not ok 10 - Test STDOUT
ok 11 - sub pushed into safe context
ok 12 - new sub pushed into same safe context
ok 13 - access to persistent functionality
ok 14 - void context
ok 15 - right value in scalar context
ok 16 - scalar context
ok 17 - right value in array context
ok 18 - array context
ok 19 - die within a safe
ok 20 - right value in scalar context
ok 21 - croak within a safe
ok 22 - die within a safe while using Carp
1..22
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/22 subtests
Test Summary Report
- ---
t/012_safe.t (Wstat: 256 (exited 1) Tests: 22 Failed:
1)
Failed test: 10
Non-zero exit status: 1
Files=13, Tests=223, 2 wallclock secs ( 0.05 usr 0.01 sys + 1.29 cusr 0.17
csys = 1.52 CPU)
Result: FAIL
Cf. e.g.
https://ci.debian.net/packages/libe/libeval-context-perl/unstable/amd64/39667202/
As this is also run during building the package, it causes a build
failure.
Cheers,
gregor
-BEGIN PGP SIGNATURE-
iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmVXor5fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgb6mg/+PuZrDFpUes2CebybnDYOJN5qj/RsS4oTbrYN4aTrhc3KlzgQ8vd0kSV2
jDUyMphzX8veUaQe9X2ss6+VL/O/eLa9jtDCpl8infH9vV1q7EcYp21LL6lN0zq9
VZtVeIXN6m+BTqwT1oS/lBzpgtpm8HOFv4qjJocKkufck3speXE65pQe0zu78Fp0
pGG5DMdA4683IhM4oS7g/2G+vBviMldReApNm6FV9vcKOmmag8CqYwEk/AUb4Q7Z
QCiaBBGy/J3oLdiIAt+JdWe6pg44pd2t1pqct4E1s6snpoIo+vwdbp4+Nox0ioQK
mT+7Au/fF12duWSxYyVpeDsm86rN6zlB/czksFgFey4Vggk/FfmzOVH2PCtdgV1h
InfkW0E9j4xQjrAlPtIXHKdE5FikDr3iQoOj7qyEPwpyIScIpZFTtWqoNIvxxEU7
H841HbstKVWzhxFZBa+bmBtpGeCE6sVhwgdNXvetnfzFPajvM8y/A7wnxsO9KRI5
58wZSvKE1Y8cNFcJTX5oWC2FyvvGLZepMArHA75D6yFxaQaGBnEXMDgw5ELArT8r
aYhKOFnzQiq6+a+rKskujAlHdDivBBK+BpwnVCbO1EZ/JwA5jgTdZ9fKFVQbOEPc
i3bdaBjny8rJEgjRlYLfND/Zy6dKdxbUxZTaIbgInzqM/jFTrQI=
=eiGi
-END PGP SIGNATURE-
Bug#1056140: marked as done (debos: fails to build from source: cannot find package "github.com/alessio/shellescape")
Your message dated Fri, 17 Nov 2023 17:04:30 + with message-id and subject line Bug#1056140: fixed in debos 1.1.2-2 has caused the Debian Bug report #1056140, regarding debos: fails to build from source: cannot find package "github.com/alessio/shellescape" 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.) -- 1056140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056140 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: debos Version: 1.1.2-1 Severity: serious Tags: ftbfs X-Debbugs-CC: obba...@gmail.com Build log excerpt dh_auto_build cd obj-x86_64-linux-gnu && go install -trimpath -v -p 8 github.com/go-debos/debos github.com/go-debos/debos/actions github.com/go-debos/debos/cmd/debos src/github.com/go-debos/fakemachine/machine.go:10:2: cannot find package "github.com/alessio/shellescape" in any of: /usr/lib/go-1.21/src/github.com/alessio/shellescape (from $GOROOT) /<>/obj-x86_64-linux-gnu/src/github.com/alessio/shellescape (from $GOPATH) dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v -p 8 github.com/go-debos/debos github.com/go-debos/debos/actions github.com/go-debos/debos/cmd/debos returned exit code 1 Thank you, Jeremy Bícha --- End Message --- --- Begin Message --- Source: debos Source-Version: 1.1.2-2 Done: Christopher Obbard We believe that the bug you reported is fixed in the latest version of debos, 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 1056...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christopher Obbard (supplier of updated debos package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 17 Nov 2023 16:36:47 + Source: debos Architecture: source Version: 1.1.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Christopher Obbard Closes: 1056140 Changes: debos (1.1.2-2) unstable; urgency=medium . [ Christopher Obbard ] * Update obbardc's email address in Uploaders. * Add golang-github-alessio-shellescape-dev to Build-Depends. (Closes: #1056140) . [ Andreas Henriksson ] * Recommend fdisk * Recommend dosfstools for mkfs.vfat Checksums-Sha1: 3b3b2ba2a6b3d60c24b5556b9be356ab1bf1bbf3 2540 debos_1.1.2-2.dsc 05ef35b10309ce7bd6fddef1eba8dc8b11481bad 5124 debos_1.1.2-2.debian.tar.xz a47dc477081489dde2d9cd1597aecf49a61227f2 9688 debos_1.1.2-2_amd64.buildinfo Checksums-Sha256: b82686e40ae70ff7317586812917f2dc5b1bbe5b69c3aff32430b8c6d63bd22a 2540 debos_1.1.2-2.dsc c9c97222151cedc950dc7c0929636417ca9a0011089f528013604c1109d8e16c 5124 debos_1.1.2-2.debian.tar.xz cf7a9ae3d8bb086259ad083a75366f8270d836923733f7e8b43473eebdd7949b 9688 debos_1.1.2-2_amd64.buildinfo Files: 572049d4ad2798a6e95bc610980cc07c 2540 devel optional debos_1.1.2-2.dsc c6a433fdbf4fe143c8896d2434586a8f 5124 devel optional debos_1.1.2-2.debian.tar.xz 8ed38b7509fecb646394935c8b41da24 9688 devel optional debos_1.1.2-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEE8Yvci2wl+QqiPVF0Y03E8GhwRvgFAmVXl3wTHG9iYmFyZGNA ZGViaWFuLm9yZwAKCRBjTcTwaHBG+KJ0EACL90XWkyXPK9jKf5ouSmsOKvzrEeS2 8KFH5V1l5azjGEtRgwUeTf22YnCYg7y5RmFvX7UFK97cP9V1yAV1/OvZ1kLMn9hw WUvJ2AJnMelcvANmLaTOPqbWtZQecN4JdVdxuDR2u3Q2VYSI7uTiGubZ2leqdhwL 5UZvUjhflOpcFUIhInLa9Oz6mYXwq6/DJGKjtnv496ecWyJ3Q15vRzT2FqbiAIEH FZrH12OQQkFejExWQRjYxs3GywqLsUEFOH97apAEa20V1wuqAXY9QjMLZIqHC/BI iEgDsKg50HBzeZmC/YRB2ZtVJ5T8FOCjAXdBtFQTzyAMi1dQHjrDIkkL3Om4g3CP L3+C9/7ctwnuTsQglWqZf/CFUCVaOCFEpcDWPYmgReP9UOiUoC5KfjldjoA8Mqch z80SDYb3e9vYdf2pFSlbT9FJp8lZ7DLcv2ovJhu+5KJN2h2VQthVQ3MEg5pWfG6v OhaptesNUXXjbLcMRI5Jz+ILcE/mBRQUkrY9zmIb+s0nJtSlacQSIi505mw2Ktdg q1sprJvnQ2EO1tQcHlDLLFZblkGBpwX25g4HJ5iY8s4H0Q8mxVuljBSIEUxlEnxv svH7BBA3txGnaLYEhfm12pzWii0G057tAmDVmSpUmHoEQ+7EbSPOuyjGssrvMPE5 wv74Kbhai4EXlA== =922U -END PGP SIGNATURE End Message ---
Bug#1056140: marked as pending in debos
Control: tag -1 pending Hello, Bug #1056140 in debos reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/go-team/packages/debos/-/commit/0fd286374379752f86726b536d1135a45d9db4f5 Add golang-github-alessio-shellescape-dev to Build-Depends. Closes: #1056140 Signed-off-by: Christopher Obbard (this message was generated automatically) -- Greetings https://bugs.debian.org/1056140
Processed: Bug#1056140 marked as pending in debos
Processing control commands: > tag -1 pending Bug #1056140 [src:debos] debos: fails to build from source: cannot find package "github.com/alessio/shellescape" Added tag(s) pending. -- 1056140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056140 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1054686: marked as done (hera: FTBFS: tests_main.cpp:3:10: fatal error: catch2/catch.hpp: No such file or directory)
Your message dated Fri, 17 Nov 2023 16:37:55 + with message-id and subject line Bug#1054686: fixed in hera 1.0.0+dfsg-2 has caused the Debian Bug report #1054686, regarding hera: FTBFS: tests_main.cpp:3:10: fatal error: catch2/catch.hpp: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1054686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054686 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: hera Version: 1.0.0+dfsg-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): > /usr/bin/c++ -I/<>/bottleneck/include -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -std=c++11 -MD -MT > CMakeFiles/bottleneck_dist.dir/example/bottleneck_dist.cpp.o -MF > CMakeFiles/bottleneck_dist.dir/example/bottleneck_dist.cpp.o.d -o > CMakeFiles/bottleneck_dist.dir/example/bottleneck_dist.cpp.o -c > /<>/bottleneck/example/bottleneck_dist.cpp > /<>/bottleneck/tests/tests_main.cpp:3:10: fatal error: > catch2/catch.hpp: No such file or directory > 3 | #include > | ^~ > compilation terminated. > /<>/bottleneck/tests/test_hera_bottleneck.cpp:1:10: fatal error: > catch2/catch.hpp: No such file or directory > 1 | #include > | ^~ > compilation terminated. > make[4]: *** [CMakeFiles/bottleneck_test.dir/build.make:93: > CMakeFiles/bottleneck_test.dir/tests/test_hera_bottleneck.cpp.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/10/27/hera_1.0.0+dfsg-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&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20231027&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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: hera Source-Version: 1.0.0+dfsg-2 Done: Gard Spreemann We believe that the bug you reported is fixed in the latest version of hera, 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. Gard Spreemann (supplier of updated hera package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 17 Nov 2023 17:07:57 +0100 Source: hera Architecture: source Version: 1.0.0+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Gard Spreemann Changed-By: Gard Spreemann Closes: 1054686 Changes: hera (1.0.0+dfsg-2) unstable; urgency=medium . * Temporarily disable tests. (Closes: #1054686) * Standards-version 4.6.2. No changes needed. Checksums-Sha1: 89ce2f44f10c26d668e83ae25a52a40b4bcce7fe 1955 hera_1.0.0+dfsg-2.dsc dbf1687a3a1ab341a6ad0015bb504da82264f2bf 4728 hera_1.0.0+dfsg-2.debian.tar.xz febfa612fc52254e8d8420ba6f892204b9b56d04 6997 hera_1.0.0+dfsg-2_source.buildinfo Checksums-Sha256: e99226d3426e45facf77a884bc2eff93931054bc65e2295ad264e5bb08cece8a 1955 hera_1.0.0+dfsg-2.dsc 458c3c9f555d27147b83a119b3c086e41ce0f95fdfe29a178a8ccf0c125a9fdb 4728 hera_1.0.0+dfsg-2.debian.tar.xz 5108b006cc54a297b9605736a573be0c96cbe6d358efe4d448555ab78eb90e4c 6997 hera_1.0.0+dfsg-2_source.buildinfo Files: 73784232ed587ca3ed746048249bc003 1955 math optional hera_1.0.0+dfsg-2.dsc 87ee07efd42eca62608381f430702001 4728 math optional hera
Bug#1056139: marked as done (tracker.debian.org: Migration data stuck on or before 2023-11-14)
Your message dated Fri, 17 Nov 2023 15:53:49 + with message-id and subject line Re: Bug#1056139: tracker.debian.org: Migration data stuck on or before 2023-11-14 has caused the Debian Bug report #1056139, regarding tracker.debian.org: Migration data stuck on or before 2023-11-14 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.) -- 1056139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056139 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tracker.debian.org Severity: serious Dear tracker.d.o owners, as you probably have already noticed, the migration data for a lot of packages appears stuck in the past, probably on or before 2023-11-14. As an example, https://tracker.debian.org/pkg/multipath-tools shows "Too young, only 4 of 5 days old", but the package migrated on 2023-11-16: https://tracker.debian.org/news/1478834/multipath-tools-094-7-migrated-to-testing/ Thanks, Chris --- End Message --- --- Begin Message --- On Fri, Nov 17, 2023 at 04:01:05PM +0100, Chris Hofstaedtler wrote: > as you probably have already noticed, the migration data for a lot of > packages appears stuck in the past, probably on or before 2023-11-14. > > As an example, https://tracker.debian.org/pkg/multipath-tools shows "Too > young, only 4 of 5 days old", but the package migrated on 2023-11-16: > https://tracker.debian.org/news/1478834/multipath-tools-094-7-migrated-to-testing/ from #debian-qa today, times are CET: [14:12] Quick question: how much time does tracker.d.o take to update version information after uploading to unstable? [14:14] tracker.d.o is outdated for quite some packages i noticed today. news has the upload but not the rest [14:14] eg tracker.d.o/nom [14:14] /in-toto too [14:30] Yep. And hence the question :) [14:33] buxy: ^ [14:45] Looks like the cron task got stuck with its lock. I killed it, next run should fix everything. [15:25] buxy: thank you -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ We live in a world where teenagers get more and more desperate trying to convince adults to behave like grown ups. signature.asc Description: PGP signature --- End Message ---
Bug#1056140: debos: fails to build from source: cannot find package "github.com/alessio/shellescape"
Source: debos Version: 1.1.2-1 Severity: serious Tags: ftbfs X-Debbugs-CC: obba...@gmail.com Build log excerpt dh_auto_build cd obj-x86_64-linux-gnu && go install -trimpath -v -p 8 github.com/go-debos/debos github.com/go-debos/debos/actions github.com/go-debos/debos/cmd/debos src/github.com/go-debos/fakemachine/machine.go:10:2: cannot find package "github.com/alessio/shellescape" in any of: /usr/lib/go-1.21/src/github.com/alessio/shellescape (from $GOROOT) /<>/obj-x86_64-linux-gnu/src/github.com/alessio/shellescape (from $GOPATH) dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v -p 8 github.com/go-debos/debos github.com/go-debos/debos/actions github.com/go-debos/debos/cmd/debos returned exit code 1 Thank you, Jeremy Bícha
Bug#1056139: tracker.debian.org: Migration data stuck on or before 2023-11-14
Package: tracker.debian.org Severity: serious Dear tracker.d.o owners, as you probably have already noticed, the migration data for a lot of packages appears stuck in the past, probably on or before 2023-11-14. As an example, https://tracker.debian.org/pkg/multipath-tools shows "Too young, only 4 of 5 days old", but the package migrated on 2023-11-16: https://tracker.debian.org/news/1478834/multipath-tools-094-7-migrated-to-testing/ Thanks, Chris
Bug#1056059: dracut: systemd 255: dracut fails to boot due to lack of systemd-executor
Hi Thomas Am 17.11.23 um 10:12 schrieb Thomas Lange: I've already included the upstream patch to the git master branch of dracut on salsa. The next dracut release in Debian will include the fix. Great, thanks. I assume this version will be 059-5 ? OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: tagging 1042027
Processing commands for cont...@bugs.debian.org: > tags 1042027 + fixed-upstream Bug #1042027 [src:transmission] transmission: FTBFS: Utils.h:125:6: error: variable or field ‘gtr_priority_combo_init’ declared void Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1042027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042027 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1041519
Processing commands for cont...@bugs.debian.org: > tags 1041519 + patch Bug #1041519 [src:transmission] transmission: contains prebuilt javascript without source Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1041519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041519 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bookworm-pu: package intel-graphics-compiler/1.0.12504.6-1+deb12u1
Processing control commands:
> block 1055874 with -1
Bug #1055874 {Done: Santiago Vila }
[src:intel-graphics-compiler] intel-graphics-compiler: FTBFS in bookworm with
intel-vc-intrinsics-dev 0.11
1055874 was not blocked by any bugs.
1055874 was not blocking any bugs.
Added blocking bug(s) of 1055874: 1056136
--
1055874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055874
1056136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056136
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1054663: telegram-send: Fails to run
I've filed a request for python3-python-telegram-bot to update to the latest upstream: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054663 If that request is actioned, this bug could be closed by updating its dependencies to point to the newer version. Otherwise, we may need to revert telegram-send to a version that works with the older python-telegram-bot. Best regards, Dale Richards
Bug#1056132: skimage: FTBFS in testing and unstable
Source: skimage Version: 0.22.0-2 Severity: serious Tags: ftbfs Hi Maintainer As can be seen on reproducible builds [1], skimage currently FTBFS in testing and unstable. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://tests.reproducible-builds.org/debian/rb-pkg/skimage.html dumping search index in English (code: en)... done dumping object inventory... done Sphinx-Gallery successfully executed 118 out of 118 files subselected by: gallery_conf["filename_pattern"] = '/plot' gallery_conf["ignore_pattern"] = '__init__\\.py' after excluding 0 files that had previously been run (based on MD5). embedding documentation hyperlinks... /usr/lib/python3/dist-packages/sphinx_gallery/docs_resolv.py:145: RemovedInSphinx80Warning: Sphinx 8 will drop support for representing paths as strings. Use "pathlib.Path" or "os.fspath" instead. Extension error: Documentation options could not be found in index. make[2]: *** [Makefile:50: html] Error 2 make[2]: Leaving directory '/build/reproducible-path/skimage-0.22.0/doc' make[1]: *** [debian/rules:59: override_dh_installdocs-indep] Error 2 make[1]: Leaving directory '/build/reproducible-path/skimage-0.22.0' make: *** [debian/rules:31: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
Processed: Re: Bug#1002789: python-pycdlib: FTBFS: failed tests
Processing commands for cont...@bugs.debian.org: > severity 1002789 serious Bug #1002789 [src:python-pycdlib] python-pycdlib: FTBFS: failed tests Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1002789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002789 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1054533: nvme-stas: autopkgtest fails on all architectures
Although this issue appears as a regression in nvme-stas 2.3-1, it looks like it was already affecting the usability of the nvme-stas version in testing (i.e., 2.2.2-2) - outside of autopkgtests. Here with nvme-stas 2.2.2-2 (after configuring a controller in /etc/stas/stafd.conf): Nov 17 11:14:05 usable-whippet systemd[1]: Reloaded stafd.service - STorage Appliance Finder (STAF). Nov 17 11:14:07 usable-whippet stafd[1268]: Error reading mandatory Host NQN (see stasadm --help): [Errno 2] No such file or directory: '/etc/nvme/hostnqn' Nov 17 11:14:07 usable-whippet systemd[1]: stafd.service: Main process exited, code=exited, status=1/FAILURE Nov 17 11:14:07 usable-whippet systemd[1]: stafd.service: Failed with result 'exit-code'. To make the autopkgtest pass, I believe we can either: * add a Test-Depends on nvme-cli; or * running those commands as part of the autopkgtest: * mkdir --parents /etc/nvme * systemctl start stas-config@hostnqn * systemctl start stas-config@hostid That said, I suggest we look for a solution that also resolves the issue outside of autopkgtests. Would introducing a Depends on nvme-cli be a bad thing? Kind regards, Olivier
Bug#1037373: marked as done (geany-plugins: build-depends on transitional package libgdk-pixbuf2.0-dev)
Your message dated Fri, 17 Nov 2023 11:34:07 + with message-id and subject line Bug#1037373: fixed in geany-plugins 2.0-3 has caused the Debian Bug report #1037373, regarding geany-plugins: build-depends on transitional package libgdk-pixbuf2.0-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.) -- 1037373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037373 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: geany-plugins Version: 1.38+dfsg-2 Severity: important Tags: trixie sid User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: split-gdk-pixbuf This package Build-Depends on libgdk-pixbuf2.0-dev. In Debian 11, libgdk-pixbuf2.0-dev was split into two packages: - libgdk-pixbuf-2.0-dev contains the supported gdk-pixbuf-2.0 library - libgdk-pixbuf-xlib-2.0-dev contains the deprecated, unmaintained Xlib integration layer, gdk-pixbuf-xlib-2.0 If this package only requires functionality from gdk-pixbuf-2.0.pc and , please update the build-dependency to libgdk-pixbuf-2.0-dev. If it also requires the Xlib integration gdk-pixbuf-xlib-2.0.pc and (unlikely), then you can also build-depend on libgdk-pixbuf-xlib-2.0-dev until the package can be updated to remove that requirement. libgdk-pixbuf-2.0-dev was present in both Debian 11 and Debian 12, so it is not necessary to have a "| libgdk-pixbuf2.0-dev" alternative dependency, even for packages that are expected to be backported. We should remove the libgdk-pixbuf2.0-dev transitional package during the Debian 13 'trixie' cycle, so this bug is likely to become RC later. Thanks, smcv --- End Message --- --- Begin Message --- Source: geany-plugins Source-Version: 2.0-3 Done: Chow Loong Jin We believe that the bug you reported is fixed in the latest version of geany-plugins, 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 1037...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chow Loong Jin (supplier of updated geany-plugins package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 17 Nov 2023 19:16:10 +0800 Source: geany-plugins Built-For-Profiles: noudeb Architecture: source Version: 2.0-3 Distribution: unstable Urgency: medium Maintainer: Geany Packaging Team Changed-By: Chow Loong Jin Closes: 1037373 1041807 Changes: geany-plugins (2.0-3) unstable; urgency=medium . * Acknowledge NMU (1.38+dfsg-2.1), changes below: [ Bastian Germann ] * [86f9dae] Import Debian changes 1.38+dfsg-2.1 geany-plugins (1.38+dfsg-2.1) unstable; urgency=medium . * Non-maintainer upload * Drop unused Build-Depends: libwnck-dev (Closes: #1041807) * Move to Build-Depends: libgdk-pixbuf-2.0-dev (Closes: #1037373) Checksums-Sha1: 9154d128f2a110fb41f7cda261bfaf4a3f72b342 5947 geany-plugins_2.0-3.dsc 2385f7628e690666f3bcb2a465f4a3b009b8c927 25388 geany-plugins_2.0-3.debian.tar.xz ddbadda39b0c5be4480c57e335d8d38137968608 22455 geany-plugins_2.0-3_source.buildinfo Checksums-Sha256: c8b4cbc27db4f2983aa6f282af3855ecf51f3fe2ebf737de4daf7873298e096c 5947 geany-plugins_2.0-3.dsc 1784ca0ad0a5269f93ba3606700069dfdcd0685460de280413f7b5184410fee9 25388 geany-plugins_2.0-3.debian.tar.xz 94047f799b339834bf8992eaad602ea84f7ad9d55481252efa41b4241870f07a 22455 geany-plugins_2.0-3_source.buildinfo Files: 57d1524fdc17b6d02d16c1f7de90339a 5947 devel optional geany-plugins_2.0-3.dsc 06e620a7f7d3aa922de391e76d130ab2 25388 devel optional geany-plugins_2.0-3.debian.tar.xz e9a37f49970649bfa89979785758747a 22455 devel optional geany-plugins_2.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEEuDQnfs/9/dZ027Q+9UiW1iHUqEFAmVXS+4ACgkQ+9UiW1iH UqGo3w/8DlK9jATrqnzHOpM/beOj2+kKTDOPQiIWH5BThu4Wmw8sI18E391DvoOr FQAmd0uHvhnlUEZDw9o56FpVT6InChZ4qNz6jl5tYB7xyt4hsB+gZXUiAYIKv8C3 fIeZpzhb38dVVVK1C1nh4tGCnZkbsZDtUqF9hnQHAPAuEB7UOL5P0IZIlZexB8uc HC+guuFn3+a6g3ea0a2UmYwLktQetnI9KarZSDEc+YSV0h51TInFilLubIvnzN3j M9QQ6OfCD/BFmK06ongKzREmHRqp6W0gfvg3CIOzKwqu/RKtBDQ4ZvwTJJ5fDhkw GHAJ5NXFzcWKwdeCULJEmDiGy6rLBSd4KkVsvrSnnaitQzMBhkIsqwkrO7Gch2s/ AaZIJ1RK9P827vRBChyi6GiVRQ+w5iayyUrdZBt6DuWUqPdIo1LD1uMjtEd/iQBx +K6EI96pmys
Processed: Bug#976506 marked as pending in conda-package-handling
Processing control commands: > tag -1 pending Bug #976506 [src:conda-package-handling] conda-package-handling: FTBFS in bullseye (failing tests) Added tag(s) pending. -- 976506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976506 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976506: marked as pending in conda-package-handling
Control: tag -1 pending Hello, Bug #976506 in conda-package-handling reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/conda-package-handling/-/commit/a34e92000f8f15d8ad4a92412b0d6688ab33a673 Deactivate test once and for all. Closes: #976506. (this message was generated automatically) -- Greetings https://bugs.debian.org/976506
Processed: Re: Bug#1055874: intel-graphics-compiler: FTBFS in bookworm: Assertion `SupportedIntrinsics.find(CPU) != SupportedI, ntrinsics.end() && "Unknown Platform"' failed.
Processing control commands:
> fixed -1 1.0.13822.1-1
Bug #1055874 {Done: Santiago Vila }
[src:intel-graphics-compiler] intel-graphics-compiler: FTBFS in bookworm with
intel-vc-intrinsics-dev 0.11
Marked as fixed in versions intel-graphics-compiler/1.0.13822.1-1.
--
1055874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055874
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1055874: intel-graphics-compiler: FTBFS in bookworm: Assertion `SupportedIntrinsics.find(CPU) != SupportedI, ntrinsics.end() && "Unknown Platform"' failed.
Control: fixed -1 1.0.13822.1-1 Verified that building in current bookworm with intel-vc-intrinsics-dev> downgraded to 0.8.1 works fine, while it FTBFS with 0.11.0> (there were no intel-vc-intrinsics uploads between these two versions) rebuilding in bookworm the next version that was uploaded to experimental (1.0.13822.1-1) works fine ... trying to bisect ... there must be a commit fixing support with 0.11 somewhere ;-) git bisect start '--term-old' 'broken' '--term-new' 'fixed' # status: waiting for both good and bad commits # fixed: [f76f43110b8af770cc039002c66e06ef2177fdce] [Autobackout][FuncReg]Revert of change: 62aaffe74f152a909e2f5e4161f807b53cc87931 Performance improvements in reduce_group built-in instr git bisect fixed f76f43110b8af770cc039002c66e06ef2177fdce # status: waiting for good commit(s), bad commit known # fixed: [385f67c0b9a0eda6a65c56616e84bb2d612f82cf] Preinstalled SPIRV-Tools CMakeFile fix git bisect fixed 385f67c0b9a0eda6a65c56616e84bb2d612f82cf # status: waiting for good commit(s), bad commit known # broken: [7da96420a6c5be941b7710646a9f729b7760a9bc] Revert " Fix for metadata related with loops" git bisect broken 7da96420a6c5be941b7710646a9f729b7760a9bc # broken: [d03177fe331ee59ac41e359b918f9e01bdfe63d4] Disable split async pass when doing sync DispatchRays git bisect broken d03177fe331ee59ac41e359b918f9e01bdfe63d4 # broken: [aecb6ce6dceb775c536af536df102f41bd2f7082] Enhance sinpi/cospi optimization git bisect broken aecb6ce6dceb775c536af536df102f41bd2f7082 # fixed: [3154d022fa7e08e7ecfb71da2d72da3f9f01dbfd] [Autobackout][FuncReg]Revert of change: cef27a8c996ca53f558b42b891b6fbdc5339bbb2 Optimize vector constants, with same delta-offset git bisect fixed 3154d022fa7e08e7ecfb71da2d72da3f9f01dbfd # broken: [2ce23f16d6d81c7f1a98132c8ec711649dcc37b8] Remove unused code git bisect broken 2ce23f16d6d81c7f1a98132c8ec711649dcc37b8 # broken: [7d615d13b5da52c5728b11a1e3e317eb0e860887] Suppress ExeSize of block load/store sends if it exceeds SimdSize git bisect broken 7d615d13b5da52c5728b11a1e3e317eb0e860887 # fixed: [b2e1ee2538fee57774f66a789855f2f9d6801b98] Add option to enable AddressArithmeticSinking pass git bisect fixed b2e1ee2538fee57774f66a789855f2f9d6801b98 # fixed: [189f308793853f5a701201ec7a05cd81ef02a76b] ZEBIN: Fix printf for 32-bit applications git bisect fixed 189f308793853f5a701201ec7a05cd81ef02a76b # fixed: [d1761dfc3ca6b54bac0ee213389a65f84d2aa9b7] Explicitly cast pointers to `int` in BiFModule (LLVM 15) git bisect fixed d1761dfc3ca6b54bac0ee213389a65f84d2aa9b7 # fixed: [36be850a6d06135768b582f63bd03b059d8d] Fix spelling in IGC LIT checks to avoid LLVM 15 failures git bisect fixed 36be850a6d06135768b582f63bd03b059d8d # fixed: [916a01be779ad4280541fc1a83a98182c441569e] VC subtarget refactoring git bisect fixed 916a01be779ad4280541fc1a83a98182c441569e # first fixed commit: [916a01be779ad4280541fc1a83a98182c441569e] VC subtarget refactoring 916a01be779ad4280541fc1a83a98182c441569e is the first fixed commit commit 916a01be779ad4280541fc1a83a98182c441569e Author: Victor Mustya Date: Wed Nov 16 05:59:08 2022 + VC subtarget refactoring Refactor VC subtargets to reduce copy-paste .../cmake/supported_platforms_list.cmake | 34 +- .../igcdeps/src/TranslationInterface.cpp | 48 ++- IGC/VectorCompiler/lib/Driver/Driver.cpp | 7 + IGC/VectorCompiler/lib/GenXCodeGen/GenX.td | 361 - .../lib/GenXCodeGen/GenXCisaBuilder.cpp| 47 +-- .../lib/GenXCodeGen/GenXLowering.cpp | 2 +- .../lib/GenXCodeGen/GenXRegionUtils.cpp| 15 +- .../lib/GenXCodeGen/GenXSubtarget.cpp | 35 +- IGC/VectorCompiler/lib/GenXCodeGen/GenXSubtarget.h | 232 + IGC/VectorCompiler/lib/GenXCodeGen/GenXUtil.cpp| 2 +- IGC/VectorCompiler/utils/vcb/vcb.cpp | 4 +- 11 files changed, 414 insertions(+), 373 deletions(-) Trying to backport that ... I also needed to apply this commit while bisecting the older commits: commit 385f67c0b9a0eda6a65c56616e84bb2d612f82cf (tag: fix1) Author: Jakub Czarnecki Date: Thu Dec 15 12:07:06 2022 + Preinstalled SPIRV-Tools CMakeFile fix Corrected typos and missing characters from the SPIRV-Tools CMakeFile, added add_custom_target to allow marking preinstalled SPIRV-Tools as a target. Andreas
Bug#1055880: marked as done (kaidan missing two dependencies)
Your message dated Fri, 17 Nov 2023 09:19:11 + with message-id and subject line Bug#1055880: fixed in kaidan 0.9.1-2 has caused the Debian Bug report #1055880, regarding kaidan missing two dependencies 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.) -- 1055880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055880 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kaidan version: 0.9.1-1 severity: grave justification: fails to start Though fix is easy, missing dependencies are qml-module-org-kde-kquickimageeditor and qml-module-org-kde-kirigami-addons-labs-mobileform After installing these manually, kaidan starts as expected. --- End Message --- --- Begin Message --- Source: kaidan Source-Version: 0.9.1-2 Done: Pino Toscano We believe that the bug you reported is fixed in the latest version of kaidan, 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. Pino Toscano (supplier of updated kaidan package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 17 Nov 2023 09:42:00 +0100 Source: kaidan Architecture: source Version: 0.9.1-2 Distribution: unstable Urgency: medium Maintainer: Debian KDE Extras Team Changed-By: Pino Toscano Closes: 1055880 Changes: kaidan (0.9.1-2) unstable; urgency=medium . * Team upload. * Upload to unstable. * Add missing runtime dependencies: qml-module-org-kde-kirigami-addons-labs-mobileform, and qml-module-org-kde-kquickimageeditor. (Closes: #1055880) * Switch Vcs-* fields back to the 'master' packaging branch. Checksums-Sha1: c17d26ab78fca1c684ccfe02755f7f2ae2486692 2776 kaidan_0.9.1-2.dsc 2f0e2ae8b904e09f696038766288d4059eb053e4 17324 kaidan_0.9.1-2.debian.tar.xz 7d54d853dd8c270151a1dfe06d25795ff4b7d69f 18369 kaidan_0.9.1-2_source.buildinfo Checksums-Sha256: a5fb8eeafc879da9d51c7e6b87571f262c575f6ccab55ff1bced1836bc4de695 2776 kaidan_0.9.1-2.dsc e5a56a2abd4b103367a85d331ca416d3645372499bf390ba735203728eaa31ed 17324 kaidan_0.9.1-2.debian.tar.xz 0edb75b73f3a2e96720ff1280f1359d10cdc4587cd057bcb300a31f9d735dd35 18369 kaidan_0.9.1-2_source.buildinfo Files: 5a2a535cabd2a8a36978c2154c443b5b 2776 net optional kaidan_0.9.1-2.dsc 1f3b8673859d873cbe80d47d37f9b20c 17324 net optional kaidan_0.9.1-2.debian.tar.xz cc3c64e0ff98939349d68f4942e06d15 18369 net optional kaidan_0.9.1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAmVXJ5MACgkQLRkciEOx P00Uog/+NdEaiedV3i29bAbB9z+9TsYKr1ou0yrfShC5LairfemYHFa5D9FNGN1b rg6MGQYavLn+Z/pMilefsBkUefG3TOxifefgUnQx7ZgvfvkPygWWKIfEA12m+8I3 ioyp0v5Ed+f6Za91/nqYvUKrTjBCbYCPeyTxefvHg2Ohh8LTfmLbuTKcSOeRunoQ YfuiRWbzHEYQADvqZqXC2TNwCdLdZAY3yp8wk8PnBc1wTCOyQRnCn47qujn5ydN2 oJ2NB3ryAlm4/SIid+YbF1NCbsK56sDoAfjTFki11L3u5UoxHzj4+AboNlKx+p3B eg5gDTkZI+xvLtUDaVADZFQbvqH1/f/wQF3ODxYZyz5IaFf3P0qAXBRfZrUv36fH pQ7XVv4jFiE/29B+XYJj31nBDBB6mH9zP5TFvW8sRjB019M24NaJyFVWUF1Kr5UV 7Z843YEF+dC0gmdHdJp5QLZOCa3Rza+HUY+LR97imk3JMnrFvYRxfJ3Tv5FwFuaG yH1KRq5RLyU8YUcyc2ZkM+SCuEiSsI95e0KjvTP8EdZFKIew1qVaPdO53HEsihaj li6fSj5WPI/9cYp3PP7hlkZfYMAnCf7pnb3EAFaIgImPEznIn7lOMXA1rN8p1tkX NH2+vqKQaV5N7MWmHs9pfNnp2tgrJVQ4kwUuz1KZcoJxdJ0aIOs= =nT7u -END PGP SIGNATURE End Message ---
Bug#1056059: dracut: systemd 255: dracut fails to boot due to lack of systemd-executor
I've already included the upstream patch to the git master branch of dracut on salsa. The next dracut release in Debian will include the fix. -- regards Thomas
Bug#1056054: Reported upstream
I've opened a bug upstream in prrte. https://github.com/openpmix/prrte/issues/1849 -- Alastair McKinstry, GPG: 82383CE9165B347C787081A2CBE6BB4E5D9AD3A5 e: mckins...@debian.org, im: @alastair:mckinstry.ie
Bug#1056114: marked as done (parmed: attempts network access)
Your message dated Fri, 17 Nov 2023 08:38:52 + with message-id and subject line Bug#1056114: fixed in parmed 4.2.2+dfsg-2 has caused the Debian Bug report #1056114, regarding parmed: attempts network access 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.) -- 1056114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056114 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: parmed Version: 4.2.2+dfsg-1 Severity: important Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: python3.12 parmed ftbfs with Python 3.12 in the tests, although I'm also seeing some test failures with 3.11, which are not seen in the last Debian build. [...] 3.12 === short test summary info FAILED test/test_parmed_formats.py::TestPDBStructure::test_download - socket FAILED test/test_parmed_formats.py::TestPDBStructure::test_download_save - so... FAILED test/test_parmed_formats.py::TestCIFStructure::test_download - socket FAILED test/test_parmedtools_actions.py::TestAmoebaParmActions::test_delete_bond = 4 failed, 734 passed, 177 skipped, 1 xfailed, 11933 warnings in 241.42s (0:04:01) = E: pybuild pybuild:395: test: plugin distutils failed with: exit code=1: cd /<>/.pybuild/cpython3_3.12_parmed/build; python3.12 -m pytest test [...] 3.11 === short test summary info FAILED test/test_parmed_formats.py::TestPDBStructure::test_download - socket FAILED test/test_parmed_formats.py::TestPDBStructure::test_download_save - so... FAILED test/test_parmed_formats.py::TestCIFStructure::test_download - socket = 3 failed, 841 passed, 70 skipped, 1 xfailed, 1 xpassed, 12027 warnings in 314.67s (0:05:14) = E: pybuild pybuild:395: test: plugin distutils failed with: exit code=1: cd /<>/.pybuild/cpython3_3.11_parmed/build; python3.11 -m pytest test complete build log at https://launchpadlibrarian.net/696985247/buildlog_ubuntu-noble-amd64.parmed_4.2.2+dfsg-1_BUILDING.txt.gz --- End Message --- --- Begin Message --- Source: parmed Source-Version: 4.2.2+dfsg-2 Done: Andrius Merkys We believe that the bug you reported is fixed in the latest version of parmed, 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 1056...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrius Merkys (supplier of updated parmed package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 17 Nov 2023 02:44:20 -0500 Source: parmed Architecture: source Version: 4.2.2+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debichem Team Changed-By: Andrius Merkys Closes: 1056114 Changes: parmed (4.2.2+dfsg-2) unstable; urgency=medium . * Skip tests requiring network access (Closes: #1056114). Checksums-Sha1: 00b880c044c09ffb86f9c417529ed7e11beda711 2336 parmed_4.2.2+dfsg-2.dsc b241a477abfff43eedb1edef9f783bf6a61b1d37 7356 parmed_4.2.2+dfsg-2.debian.tar.xz dfc4cad2b1d107977b342724933bbcee7b4b6a19 8436 parmed_4.2.2+dfsg-2_source.buildinfo Checksums-Sha256: 0bb48cdfba8146d814de4a75d9ca467ae4c3402c93791f6e709ae2532ee04bf7 2336 parmed_4.2.2+dfsg-2.dsc 186a0e70de2950bb19b003d71d9d37ad36367ff0bede054e4bf5ea7eb970be85 7356 parmed_4.2.2+dfsg-2.debian.tar.xz dd3634bfb93576733bbfdd27c8a95ae19179eda4503a5f94bf04da84ab69ed5f 8436 parmed_4.2.2+dfsg-2_source.buildinfo Files: a78368602525fd606bc62643861c6cd6 2336 science optional parmed_4.2.2+dfsg-2.dsc 15cf03298bf8ec3476d9b5a0eb0dd014 7356 science optional parmed_4.2.2+dfsg-2.debian.tar.xz 7465b1adec286a72dc15e486514753be 8436 science optional parmed_4.2.2+dfsg-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEdyKS9veshfrgQdQe5fQ/nCc08ocFAmVXGjsSHG1lcmt5c0Bk ZWJpYW4ub3JnAAoJEOX0P5wnNPKHtKAP+waNHuCJE4iL7BcUAKvaNLJiCa0t5KRA c0alWLNT2+Mp2jq7hpmCN5r0zPIVQFksKlLGcWVWH4uc08DZo1oclfWuukhmCbTa E2hL4YmKQ6i80lD7QugdbZU81JqCcZG3cU0ZqCvLZ0jvVTmtwyhSQmSdw77cSso/ W12OIMOr9nch53CiENWfWX0czgEieDtuGnwpBwIyoj8jn1jfTZbnG3YT7pwcW0YE HvhgkZYdRpokn0oK1qqvD6Lu3Appu06eeTBSjGof0EEM0hYktcUnQk1sFO0qqMRl 5fXdqrSgC8zuXM5BtAtYB6V6G41bHKcTQ9cs3+EbHIkfptw+qSE/RbK5RSpeZdB
