Bug#661721: marked as done (intersect with installed packages)

2025-04-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Apr 2025 13:22:56 + with message-id and subject line Bug#1100760: Removed package(s) from unstable has caused the Debian Bug report #661721, regarding intersect with installed packages to be marked as done. This means that you claim that the problem has been dealt

Bug#889794: marked as done (elpa-cider: should inject dependencies from Debian packages)

2025-03-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Mar 2025 18:45:36 + with message-id and subject line Bug#1100371: Removed package(s) from unstable has caused the Debian Bug report #889794, regarding elpa-cider: should inject dependencies from Debian packages to be marked as done. This means that you claim that

Question about CVE fix backport to bullseye and bookworm packages

2025-03-05 Thread Jennard Dy
Hello, I am wondering if the following CVEs fixed in trixie would ever be backported to future releases of bullseye and bookworm: https://security-tracker.debian.org/tracker/CVE-2024-38541 https://security-tracker.debian.org/tracker/CVE-2024-38564 https://security-tracker.debian.org/tracker/CVE-2

Re: chroot-debianizer - Tool that automates routine work with Debian packages.

2025-02-13 Thread Richard Lewis
Kirill Rekhov writes: > I wrote a script called chroot-debianizer that automates routine tasks related > to Debian package management. This tool is designed to facilitate a clean and > isolated package building process in chroot environments specifically for the > amd64 architecture. There are a

Re: chroot-debianizer - Tool that automates routine work with Debian packages.

2025-02-12 Thread Soren Stoutner
On Wednesday, February 12, 2025 10:51:13 AM MST Raphael Hertzog wrote: > That sounds like what the "debian_pipeline" workflow can do in > https://debusine.debian.net, except that it is able to do it on multiple > architectures and also run reverse dependencies autopkgtest (however it > doesn't supp

Re: chroot-debianizer - Tool that automates routine work with Debian packages.

2025-02-12 Thread Raphael Hertzog
Hi, On Tue, 11 Feb 2025, Kirill Rekhov wrote: > I wrote a script called chroot-debianizer that automates routine tasks related > to Debian package management. This tool is designed to facilitate a clean and > isolated package building process in chroot environments specifically for the > amd64 arc

chroot-debianizer - Tool that automates routine work with Debian packages.

2025-02-11 Thread Kirill Rekhov
Hi, Dear Debian Engineers. I hope this message finds you well. Sorry for advertising my small project. I use this script often when working with Debian packages. I wrote a script called chroot-debianizer that automates routine tasks related to Debian package management. This tool is designed to

Bug#883777: marked as done (multistrap: preinst runs after packages are unpacked)

2025-01-24 Thread Debian Bug Tracking System
Your message dated Fri, 24 Jan 2025 16:20:10 + with message-id and subject line Bug#1093962: Removed package(s) from unstable has caused the Debian Bug report #883777, regarding multistrap: preinst runs after packages are unpacked to be marked as done. This means that you claim that the

Processed: Re: [various packages]: FTBFS: Package 'lcms2', required by 'wlroots-0.18', not found

2025-01-02 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 libwlroots-0.18-dev 0.18.2-1 Bug #1091956 [src:wayfire] wayfire: FTBFS: Package 'lcms2', required by 'wlroots-0.18', not found Bug reassigned from package 'src:wayfire' to 'libwlroots-0.18-dev'. No longer marked as found in versions wayfire/0.9.0-5. Igno

Processed: Re: [various packages]: FTBFS: Package 'lcms2', required by 'wlroots-0.18', not found

2025-01-02 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 libwlroots-0.18-dev 0.18.2-1 Bug #1091957 [src:wf-shell] wf-shell: FTBFS: Package 'lcms2', required by 'wlroots-0.18', not found Bug reassigned from package 'src:wf-shell' to 'libwlroots-0.18-dev'. No longer marked as found in versions wf-shell/0.9.0+ds-

Processed: Re: [various packages]: FTBFS: Package 'lcms2', required by 'wlroots-0.18', not found

2025-01-02 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 libwlroots-0.18-dev 0.18.2-1 Bug #1091955 [src:wayfire-shadows] wayfire-shadows: FTBFS: Package 'lcms2', required by 'wlroots-0.18', not found Bug reassigned from package 'src:wayfire-shadows' to 'libwlroots-0.18-dev'. No longer marked as found in versio

Bug#1091955: [various packages]: FTBFS: Package 'lcms2', required by 'wlroots-0.18', not found

2025-01-02 Thread Simon McVittie
Control: reassign -1 libwlroots-0.18-dev 0.18.2-1 Control: forcemerge 1091934 -1 On Thu, 02 Jan 2025 at 18:45:41 +, Simon McVittie wrote: > On Thu, 02 Jan 2025 at 18:09:04 +, Santiago Vila wrote: > > During a rebuild of all packages in unstable, [gamescope] failed to build: >

Bug#1058684: marked as done (Packages zfs-dkms and zfs-fuse are mutually problematic)

2024-12-13 Thread Debian Bug Tracking System
Your message dated Fri, 13 Dec 2024 09:01:26 + with message-id and subject line Bug#1058684: fixed in zfs-linux 2.2.7-1 has caused the Debian Bug report #1058684, regarding Packages zfs-dkms and zfs-fuse are mutually problematic to be marked as done. This means that you claim that the

Bug#1049515: marked as done (libapache-mod-musicindex: Fails to build binary packages again after successful build)

2024-12-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Dec 2024 13:49:39 + with message-id and subject line Bug#1049515: fixed in libapache-mod-musicindex 1.4.1-4 has caused the Debian Bug report #1049515, regarding libapache-mod-musicindex: Fails to build binary packages again after successful build to be marked as

Bug#878858: marked as done (please drop transitional packages libfilesystem-ruby, libfilesystem-ruby1.8 and libfilesystem-ruby1.9.1)

2024-11-28 Thread Debian Bug Tracking System
Your message dated Thu, 28 Nov 2024 18:27:00 + with message-id and subject line Bug#1087388: Removed package(s) from unstable has caused the Debian Bug report #878858, regarding please drop transitional packages libfilesystem-ruby, libfilesystem-ruby1.8 and libfilesystem-ruby1.9.1 to be

Bug#1017816: marked as done (golang-github-bsm-pool: Flaky test on i386, blocking other packages migration)

2024-11-26 Thread Debian Bug Tracking System
Your message dated Tue, 26 Nov 2024 23:53:59 + with message-id and subject line Bug#1017816: fixed in golang-github-bsm-pool 0.8.0-7 has caused the Debian Bug report #1017816, regarding golang-github-bsm-pool: Flaky test on i386, blocking other packages migration to be marked as done. This

Bug#1017816: golang-github-bsm-pool: Flaky test on i386, blocking other packages migration

2024-11-21 Thread Santiago Vila
forwarded 1017816 https://github.com/bsm/pool/issues/4 thanks Hello. I've just forwarded this upstream, but maybe we should go ahead and remove the package. It used to be a (build-)dependency for gitea, but gitea does not exist anymore. Thanks.

Processed: golang-github-bsm-pool: Flaky test on i386, blocking other packages migration

2024-11-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1017816 https://github.com/bsm/pool/issues/4 Bug #1017816 [src:golang-github-bsm-pool] golang-github-bsm-pool: Flaky test on i386, blocking other packages migration Set Bug forwarded-to-address to 'https://github.com/bsm/pool/

Bug#530676: marked as done (giggle: Shared libraries and headers should be split into packages)

2024-11-11 Thread Debian Bug Tracking System
Your message dated Mon, 11 Nov 2024 17:00:47 + with message-id and subject line Bug#1084750: Removed package(s) from unstable has caused the Debian Bug report #530676, regarding giggle: Shared libraries and headers should be split into packages to be marked as done. This means that you claim

Bug#1049659: marked as done (catdvi: Fails to build binary packages again after successful build)

2024-11-05 Thread Debian Bug Tracking System
Your message dated Tue, 05 Nov 2024 22:19:07 + with message-id and subject line Bug#1049659: fixed in catdvi 0.14-16 has caused the Debian Bug report #1049659, regarding catdvi: Fails to build binary packages again after successful build to be marked as done. This means that you claim that

Bug#1049729: marked as done (cal3d: Fails to build binary packages again after successful build)

2024-10-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Oct 2024 06:48:59 + with message-id and subject line Bug#1049729: fixed in cal3d 0.11.0-10 has caused the Debian Bug report #1049729, regarding cal3d: Fails to build binary packages again after successful build to be marked as done. This means that you claim that

Bug#1084016: Migrating away from pkg_resources is difficult for namespace packages

2024-10-04 Thread Matthias Klose
_init__.py (with unimportant variations): __import__('pkg_resources').declare_namespace(__name__) As https://packaging.python.org/en/latest/guides/packaging-namespace-packages/#pkg-resources-style-namespace-packages says: If you are creating a new distribution within an existing

Bug#1084010: Migrating away from pkg_resources is difficult for namespace packages

2024-10-04 Thread Colin Watson
variations): __import__('pkg_resources').declare_namespace(__name__) As https://packaging.python.org/en/latest/guides/packaging-namespace-packages/#pkg-resources-style-namespace-packages says: If you are creating a new distribution within an existing namespace package that uses this method t

Bug#911821: marked as done (Build shared library packages)

2024-08-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 Aug 2024 12:42:10 +0200 with message-id and subject line Build shared library packages has caused the Debian Bug report #911821, regarding Build shared library packages to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#1049554: marked as done (aspic: Fails to build binary packages again after successful build)

2024-05-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 May 2024 09:49:16 + with message-id and subject line Bug#1049554: fixed in aspic 2.00+dfsg-3 has caused the Debian Bug report #1049554, regarding aspic: Fails to build binary packages again after successful build to be marked as done. This means that you claim that

Bug#1049680: marked as done (freedink-dfarc: Fails to build binary packages again after successful build)

2024-05-09 Thread Debian Bug Tracking System
Your message dated Thu, 09 May 2024 07:19:02 + with message-id and subject line Bug#1049680: fixed in freedink-dfarc 3.14-7 has caused the Debian Bug report #1049680, regarding freedink-dfarc: Fails to build binary packages again after successful build to be marked as done. This means that

Bug#1049680: freedink-dfarc: Fails to build binary packages again after successful build

2024-05-01 Thread Petter Reinholdtsen
I had a look at this issue, and the cause is in src/Makefile.am, which intentionally list several files both in both dfarc_SOURCES and BUILT_SOURCES. The problematic files are generated but stored in the tarball to save a build dependencuy (wxglade). I am not sure how to avoid this problem, and l

Bug#1049841: marked as done (propellor: Fails to build binary packages again after successful build)

2024-04-16 Thread Debian Bug Tracking System
Your message dated Tue, 16 Apr 2024 17:35:28 + with message-id and subject line Bug#1049841: fixed in propellor 5.17-1 has caused the Debian Bug report #1049841, regarding propellor: Fails to build binary packages again after successful build to be marked as done. This means that you claim

Bug#1049648: marked as done (tk707: Fails to build binary packages again after successful build)

2024-04-10 Thread Debian Bug Tracking System
Your message dated Wed, 10 Apr 2024 16:36:15 + with message-id and subject line Bug#1068156: Removed package(s) from unstable has caused the Debian Bug report #1049648, regarding tk707: Fails to build binary packages again after successful build to be marked as done. This means that you

Bug#1065703: marked as done (t64 transition broke build of other packages)

2024-03-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Mar 2024 11:15:40 + with message-id and subject line Bug#1065703: fixed in libident 0.32-3 has caused the Debian Bug report #1065703, regarding t64 transition broke build of other packages to be marked as done. This means that you claim that the problem has been

Bug#1065703: t64 transition broke build of other packages

2024-03-09 Thread Christoph Biedl
against those packages, severity serious. This is at least about: efingerd: #1065100 (maintainer Cc'ed) ngircd: #1065101 (maintained by yours truly) If those test rebuilds had been done, the following error could not have been overseen (for efingerd, likewise n

Bug#1049477: marked as done (nxcl: Fails to build binary packages again after successful build)

2024-01-18 Thread Debian Bug Tracking System
Your message dated Thu, 18 Jan 2024 17:08:18 + with message-id and subject line Bug#1060855: Removed package(s) from unstable has caused the Debian Bug report #1049477, regarding nxcl: Fails to build binary packages again after successful build to be marked as done. This means that you claim

Bug#1058684: Packages zfs-dkms and zfs-fuse are mutually problematic

2023-12-14 Thread Michael Kjörling
the packages so as to make installing both the OpenZFS and ZFS-FUSE implementations on the same system difficult, possibly by adding mutual Breaks: to the packages in question. NOTE: This bug report probably applies equally to both zfs-dkms AND zfs-fuse; however, I don't see any simply way to

Bug#1049736: marked as done (gxmessage: Fails to build binary packages again after successful build)

2023-11-30 Thread Debian Bug Tracking System
Your message dated Fri, 01 Dec 2023 01:19:08 + with message-id and subject line Bug#1049736: fixed in gxmessage 3.4.3-2 has caused the Debian Bug report #1049736, regarding gxmessage: Fails to build binary packages again after successful build to be marked as done. This means that you claim

Bug#1049720: marked as done (gtick: Fails to build binary packages again after successful build)

2023-11-30 Thread Debian Bug Tracking System
Your message dated Thu, 30 Nov 2023 18:57:45 + with message-id and subject line Bug#1054406: Removed package(s) from unstable has caused the Debian Bug report #1049720, regarding gtick: Fails to build binary packages again after successful build to be marked as done. This means that you

Bug#760099: marked as done (apt-listchanges: Incorrectly assumes that binary packages from the same source share NEWS files)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:07 + with message-id and subject line Bug#383803: fixed in apt-listchanges 4.0 has caused the Debian Bug report #383803, regarding apt-listchanges: Incorrectly assumes that binary packages from the same source share NEWS files to be marked as done

Bug#478188: marked as done (apt-listchanges: Please provide option to set all installed packages as seen)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:07 + with message-id and subject line Bug#478188: fixed in apt-listchanges 4.0 has caused the Debian Bug report #478188, regarding apt-listchanges: Please provide option to set all installed packages as seen to be marked as done. This means that you

Bug#383803: marked as done (apt-listchanges: mishandles different NEWS.Debian files in different binary packages built from the same source)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:07 + with message-id and subject line Bug#383803: fixed in apt-listchanges 4.0 has caused the Debian Bug report #383803, regarding apt-listchanges: mishandles different NEWS.Debian files in different binary packages built from the same source to be

Bug#369051: marked as done (apt-listchanges: provide searchable string between packages and possibly preload search string)

2023-10-02 Thread Debian Bug Tracking System
Your message dated Mon, 2 Oct 2023 21:34:28 -0400 with message-id <62ca9509-8540-459f-9e45-0e9d2f175...@kamens.us> and subject line Re: apt-listchanges: provide searchable string between packages and possibly preload search string has caused the Debian Bug report #369051, regardi

Bug#770542: marked as done (debdry: add support for Java packages with javahelper/maven-debian-helper/mh_make)

2023-09-26 Thread Debian Bug Tracking System
Your message dated Tue, 26 Sep 2023 16:31:53 + with message-id and subject line Bug#1051718: Removed package(s) from unstable has caused the Debian Bug report #770542, regarding debdry: add support for Java packages with javahelper/maven-debian-helper/mh_make to be marked as done. This

Bug#1040322: marked as done (debdry: should not ship test data in /usr/lib/python3/dist-packages/control)

2023-09-26 Thread Debian Bug Tracking System
Your message dated Tue, 26 Sep 2023 16:31:53 + with message-id and subject line Bug#1051718: Removed package(s) from unstable has caused the Debian Bug report #1040322, regarding debdry: should not ship test data in /usr/lib/python3/dist-packages/control to be marked as done. This means

Bug#962078: apt-listchanges: feature request: combine identical changelog entries from multiple packages

2023-09-25 Thread Jonathan Kamens
I have a fix pending which merges changelog entries which are _entirely_ identical, which I implemented as part of addressing bug #383803, but I gather that fix won't work here. If I'm understanding correctly, the issue discussed here is the content of the changelog entry being identical but th

Bug#926175: marked as done (apt-listchanges: only a single changelog is shown when multiple packages are updated)

2023-09-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Sep 2023 09:05:43 -0400 with message-id <8b18cd22-e48a-4d0d-a36a-621132fb4...@kamens.us> and subject line Re: tag moreinfo 926175 has caused the Debian Bug report #926175, regarding apt-listchanges: only a single changelog is shown when multiple packages are upda

Processed: Re: (many packages): build-depends on transitional package libgdk-pixbuf2.0-dev

2023-09-14 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1037374 [src:giggle] giggle: build-depends on transitional package libgdk-pixbuf2.0-dev Severity set to 'serious' from 'important' -- 1037374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037374 Debian Bug Tracking System Contact ow.

Bug#1049654: marked as done (oxygencursors: Fails to build binary packages again after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 13:22:00 + with message-id and subject line Bug#1049654: fixed in oxygencursors 0.0.2012-06-kde4.8-5 has caused the Debian Bug report #1049654, regarding oxygencursors: Fails to build binary packages again after successful build to be marked as done. This

Bug#1049849: wxedid: Fails to build binary packages again after successful build

2023-08-16 Thread Lucas Nussbaum
Source: wxedid Version: 0.0.21-4 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to do build a binary-only build (not source) after a successful

Bug#1049841: propellor: Fails to build binary packages again after successful build

2023-08-16 Thread Lucas Nussbaum
sion} unused, but is defined > # only call dh_scour for packages in main > if grep -q '^Component:[[:space:]]*main' /CurrentlyBuilding 2>/dev/null; then > dh_scour -plibghc-propellor-doc ; fi > dh_md5sums -plibghc-propellor-doc > dh_builddeb -plibghc-propellor-doc > dpkg-de

Bug#1049755: ap-utils: Fails to build binary packages again after successful build

2023-08-16 Thread Lucas Nussbaum
Source: ap-utils Version: 1.5-5 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to do build a binary-only build (not source) after a successful b

Bug#1049736: gxmessage: Fails to build binary packages again after successful build

2023-08-16 Thread Lucas Nussbaum
Source: gxmessage Version: 3.4.3-1 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to do build a binary-only build (not source) after a successfu

Bug#1049729: cal3d: Fails to build binary packages again after successful build

2023-08-16 Thread Lucas Nussbaum
Source: cal3d Version: 0.11.0-8 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to do build a binary-only build (not source) after a successful b

Bug#1049718: eigenbase-farrago: Fails to build binary packages again after successful build

2023-08-16 Thread Lucas Nussbaum
Source: eigenbase-farrago Version: 0.9.0-3 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to do build a binary-only build (not source) after a s

Bug#1049720: gtick: Fails to build binary packages again after successful build

2023-08-16 Thread Lucas Nussbaum
Source: gtick Version: 0.5.5-3 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to do build a binary-only build (not source) after a successful bu

Bug#1049680: freedink-dfarc: Fails to build binary packages again after successful build

2023-08-16 Thread Lucas Nussbaum
Source: freedink-dfarc Version: 3.14-5 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to do build a binary-only build (not source) after a succe

Bug#1049659: catdvi: Fails to build binary packages again after successful build

2023-08-16 Thread Lucas Nussbaum
Source: catdvi Version: 0.14-14 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to do build a binary-only build (not source) after a successful b

Bug#1049654: oxygencursors: Fails to build binary packages again after successful build

2023-08-16 Thread Lucas Nussbaum
Source: oxygencursors Version: 0.0.2012-06-kde4.8-4 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to do build a binary-only build (not source)

Bug#1049648: tk707: Fails to build binary packages again after successful build

2023-08-16 Thread Lucas Nussbaum
Source: tk707 Version: 0.8-2 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to do build a binary-only build (not source) after a successful buil

Bug#1049554: aspic: Fails to build binary packages again after successful build

2023-08-16 Thread Lucas Nussbaum
Source: aspic Version: 2.00+dfsg-2 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to do build a binary-only build (not source) after a successfu

Bug#1049537: libpgf: Fails to build binary packages again after successful build

2023-08-16 Thread Lucas Nussbaum
Source: libpgf Version: 7.21.7+ds-2 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to do build a binary-only build (not source) after a successf

Bug#1049515: libapache-mod-musicindex: Fails to build binary packages again after successful build

2023-08-16 Thread Lucas Nussbaum
Source: libapache-mod-musicindex Version: 1.4.1-3.1 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to do build a binary-only build (not source)

Bug#1049492: libquvi-scripts: Fails to build binary packages again after successful build

2023-08-16 Thread Lucas Nussbaum
Source: libquvi-scripts Version: 0.9.20131130-3 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to do build a binary-only build (not source) afte

Bug#1049477: nxcl: Fails to build binary packages again after successful build

2023-08-16 Thread Lucas Nussbaum
Source: nxcl Version: 0.9-4 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to do build a binary-only build (not source) after a successful build

Bug#1042467: sysv-rc-conf: from bullseye want to uninstall many packages without dependency when trying upgrading it

2023-07-28 Thread Jiff
synaptic I tried to upgrade it but it ranted throwing a long list of packages it wanted to uninstall, such as colord, gparted, haruna, gufw, etc, however when I check those 4 they have been upgraded correctly and moreover do not show any dependency with sysv-rc-conf ! * What was the outcome of this

Processed: python3-sphinx-bootstrap-theme: provide versioned virtual packages for the versioned components included

2023-07-06 Thread Debian Bug Tracking System
Processing control commands: > block 1040468 with -1 Bug #1040468 [kytos-sphinx-theme] kytos-sphinx-theme: broken symlink: /usr/share/kytos_sphinx_theme/kytos/static/bootstrap -> ../../../../lib/python3/dist-packages/sphinx_bootstrap_theme/bootstrap/static/bootstrap-3.3.7 1040468 w

Bug#1040468: kytos-sphinx-theme: broken symlink: /usr/share/kytos_sphinx_theme/kytos/static/bootstrap -> ../../../../lib/python3/dist-packages/sphinx_bootstrap_theme/bootstrap/static/bootstrap-3.3.7

2023-07-06 Thread Andreas Beckmann
/static/bootstrap -> ../../../../lib/python3/dist-packages/sphinx_bootstrap_theme/bootstrap/static/bootstrap-3.3.7 (kytos-sphinx-theme-common) Current python3-sphinx-bootstrap-theme ships bootstrap-2.3.2 and bootstrap-3.4.1 cheers, Andreas

Bug#1040322: debdry: should not ship test data in /usr/lib/python3/dist-packages/control

2023-07-04 Thread Helmut Grohne
Package: debdry Version: 0.2.2-1 Severity: serious debdry creates a control file in its test suite. This file happens to get installed into /usr/lib/python3/dist-packages/control and this happens to cause an undeclared file conflict with python3-kombu. I'm filing this with debdry, becau

Bug#878688: marked as done (please drop transitional packages liblua5.1-bitop0 and liblua5.1-bitop-dev)

2023-01-27 Thread Debian Bug Tracking System
Your message dated Fri, 27 Jan 2023 13:19:36 + with message-id and subject line Bug#878688: fixed in lua-bitop 1.0.2-7 has caused the Debian Bug report #878688, regarding please drop transitional packages liblua5.1-bitop0 and liblua5.1-bitop-dev to be marked as done. This means that you

Bug#569831: marked as done (debget: doesn't handle 1:N source:binary packages)

2022-12-20 Thread Debian Bug Tracking System
Your message dated Tue, 20 Dec 2022 16:04:26 + with message-id and subject line Bug#1026457: Removed package(s) from unstable has caused the Debian Bug report #569831, regarding debget: doesn't handle 1:N source:binary packages to be marked as done. This means that you claim that the pr

Bug#1023273: Breaks packages like ocrmypdf

2022-11-01 Thread Klaus Ethgen
/bin/dash Init: sysvinit (via /sbin/init) Versions of packages ghostscript depends on: ii libc62.35-4 ii libgs10 10.0.0~dfsg-6 ghostscript recommends no packages. Versions of packages ghostscript suggests: ii ghostscript-x 10.0.0~dfsg-6 -- no debconf

Bug#1017816: golang-github-bsm-pool: Flaky test on i386, blocking other packages migration

2022-08-20 Thread Shengjing Zhu
Source: golang-github-bsm-pool Version: 0.8.0-6 Severity: serious Tags: ftbfs X-Debbugs-Cc: z...@debian.org https://ci.debian.net/user/britney/jobs?package=golang-github-bsm-pool&suite[]=testing&arch[]=i386 https://ci.debian.net/packages/g/golang-github-bsm-pool/testing/i386/ The test

Bug#1013477: marked as done (python-restless: FTBFS: ImportError: cannot import name 'url' from 'django.conf.urls' (/usr/lib/python3/dist-packages/django/conf/urls/__init__.py))

2022-07-02 Thread Debian Bug Tracking System
usr/lib/python3/dist-packages/django/conf/urls/__init__.py) 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 admin

Bug#1013477: python-restless: FTBFS: ImportError: cannot import name 'url' from 'django.conf.urls' (/usr/lib/python3/dist-packages/django/conf/urls/__init__.py)

2022-06-24 Thread Lucas Nussbaum
Source: python-restless Version: 2.2.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220624 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > mak

Processed: Re: Cannot install without wiping other packages

2022-04-26 Thread Debian Bug Tracking System
Processing control commands: > tags 966223 +unreproducible Bug #966223 [unar] Cannot install without wiping other packages Added tag(s) unreproducible. > notfound 966223 1.10.1-2 Bug #966223 [unar] Cannot install without wiping other packages No longer marked as found in versions unar/1.

Bug#966223: Cannot install without wiping other packages

2022-04-26 Thread Boyuan Yang
Sid. Thanks, Boyuan Yang On Sat, 25 Jul 2020 05:51:34 +0800 =?utf-8?B?56mN5Li55bC8?= Dan Jacobson wrote: > Package: unar > Version: 1.10.1-2+b6 > > With sid: > # aptitude install unar > The following NEW packages will be installed: >   unar{b} (D: gnustep-base-runtime, D: l

Bug#1001952: Acknowledgement (FileNotFoundError: [Errno 2] No such file or directory: '/usr/lib/python3/dist-packages/cdist/preos')

2021-12-19 Thread Allan Wind
Not sure why I didn't try the suggestion out before file the bug: sudo mkdir /usr/lib/python3/dist-packages/cdist/preos sudo chmod 755 !$ $ cdist preos Available PreOS-es: $

Bug#1001952: FileNotFoundError: [Errno 2] No such file or directory: '/usr/lib/python3/dist-packages/cdist/preos'

2021-12-19 Thread Allan Wind
:]) File "/usr/lib/python3/dist-packages/cdist/preos.py", line 111, in commandline cls.preoses = find_preoses() File "/usr/lib/python3/dist-packages/cdist/preos.py", line 62, in find_preoses for preos in find_preos_plugins(): File "/usr/lib/python3/dist-packages/cdi

Bug#994305: marked as done (libkdtree++: Removal of the python3-*-dbg packages in sid/bookworm)

2021-11-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 19:04:22 + with message-id and subject line Bug#994305: fixed in libkdtree++ 0.7.1+git20101123-6 has caused the Debian Bug report #994305, regarding libkdtree++: Removal of the python3-*-dbg packages in sid/bookworm to be marked as done. This means that

Bug#994350: marked as done (python-djvulibre: Removal of the python3-*-dbg packages in sid/bookworm)

2021-09-20 Thread Debian Bug Tracking System
Your message dated Tue, 21 Sep 2021 00:35:11 + with message-id and subject line Bug#994350: fixed in python-djvulibre 0.8.7-1 has caused the Debian Bug report #994350, regarding python-djvulibre: Removal of the python3-*-dbg packages in sid/bookworm to be marked as done. This means that you

Bug#994347: marked as done (python-bsddb3: Removal of the python3-*-dbg packages in sid/bookworm)

2021-09-15 Thread Debian Bug Tracking System
Your message dated Wed, 15 Sep 2021 12:19:49 + with message-id and subject line Bug#994347: fixed in python-bsddb3 6.2.9-2 has caused the Debian Bug report #994347, regarding python-bsddb3: Removal of the python3-*-dbg packages in sid/bookworm to be marked as done. This means that you claim

Bug#994350: python-djvulibre: Removal of the python3-*-dbg packages in sid/bookworm

2021-09-15 Thread Matthias Klose
Package: src:python-djvulibre Version: 0.8.4-3 Severity: serious Tags: sid bookworm User: debian-pyt...@lists.debian.org Usertags: pydbg-removal Python 3.8 upstream now has a common ABI for normal and debug extension builds, so we can drop the python3-*-dbg packages. Details at https

Bug#994347: python-bsddb3: Removal of the python3-*-dbg packages in sid/bookworm

2021-09-15 Thread Matthias Klose
Package: src:python-bsddb3 Version: 6.2.9-1 Severity: serious Tags: sid bookworm User: debian-pyt...@lists.debian.org Usertags: pydbg-removal Python 3.8 upstream now has a common ABI for normal and debug extension builds, so we can drop the python3-*-dbg packages. Details at https

Bug#994305: libkdtree++: Removal of the python3-*-dbg packages in sid/bookworm

2021-09-15 Thread Matthias Klose
Package: src:libkdtree++ Version: 0.7.1+git20101123-5 Severity: serious Tags: sid bookworm User: debian-pyt...@lists.debian.org Usertags: pydbg-removal Python 3.8 upstream now has a common ABI for normal and debug extension builds, so we can drop the python3-*-dbg packages. Details at https

Bug#992188: marked as done (alien: Fails to create packages that place files in /usr/local)

2021-08-21 Thread Debian Bug Tracking System
Your message dated Sun, 22 Aug 2021 05:48:32 + with message-id and subject line Bug#992188: fixed in alien 8.95.5 has caused the Debian Bug report #992188, regarding alien: Fails to create packages that place files in /usr/local to be marked as done. This means that you claim that the

Bug#992188: alien: Fails to create packages that place files in /usr/local

2021-08-15 Thread Rob N
Package: alien Version: 8.95.4 Severity: normal X-Debbugs-Cc: r...@despairlabs.com Dear Maintainer, Severity: normal Dear Maintainer, We build a number of local packages installing to /usr/local in a chroot, creating a tarball, then running alien to produce a .deb file. Since bullseye

Bug#891893: marked as done (jtb: groupId change in jtb-1.4.12-1 causes other packages to FTBFS)

2021-07-16 Thread Debian Bug Tracking System
Your message dated Fri, 16 Jul 2021 23:24:51 + with message-id and subject line RE: BAQ has caused the Debian Bug report #891893, regarding jtb: groupId change in jtb-1.4.12-1 causes other packages to FTBFS to be marked as done. This means that you claim that the problem has been dealt with

Bug#824168: apt-listchanges: Should not display news for libraries and other packages that the user does not care about

2021-07-03 Thread Jonas Smedegaard
A somewhat related issue is that libraries installed by debian-installer is marked as manually-installed - see bug#742977 - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep pr

Bug#926175: apt-listchanges: only a single changelog is shown when multiple packages are updated

2021-06-27 Thread Brian Thompson
Every unexpected behavior is a potential bug. We shouldn't close this bug yet. Nicholas, are you still seeing this behavior? -- Best regards, Brian T signature.asc Description: PGP signature

Bug#985808: marked as done (alien: cannot convert aarch64 rpm packages to arm64 deb packages (patch included))

2021-04-07 Thread Debian Bug Tracking System
Your message dated Wed, 07 Apr 2021 20:18:48 + with message-id and subject line Bug#985808: fixed in alien 8.95.4 has caused the Debian Bug report #985808, regarding alien: cannot convert aarch64 rpm packages to arm64 deb packages (patch included) to be marked as done. This means that you

Bug#985808: alien: cannot convert aarch64 rpm packages to arm64 deb packages (patch included)

2021-03-23 Thread David Dick
amd64 Kernel: Linux 5.8.0-1025-aws (SMP w/16 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages alien depends on: ii cpio 2.13+dfsg-

Bug#959636: marked as done (zope.i18nmessageid: FTBFS: ImportError: cannot import name 'Feature' from 'setuptools' (/usr/lib/python3/dist-packages/setuptools/__init__.py))

2020-05-18 Thread Debian Bug Tracking System
usr/lib/python3/dist-packages/setuptools/__init__.py) 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 admin

Bug#959633: marked as done (zope.proxy: FTBFS: ImportError: cannot import name 'Feature' from 'setuptools' (/usr/lib/python3/dist-packages/setuptools/__init__.py))

2020-05-11 Thread Debian Bug Tracking System
ls' (/usr/lib/python3/dist-packages/setuptools/__init__.py) 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 sys

Bug#959633: zope.proxy: FTBFS: ImportError: cannot import name 'Feature' from 'setuptools' (/usr/lib/python3/dist-packages/setuptools/__init__.py)

2020-05-03 Thread Lucas Nussbaum
Source: zope.proxy Version: 4.3.3-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200501 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpack

Bug#959636: zope.i18nmessageid: FTBFS: ImportError: cannot import name 'Feature' from 'setuptools' (/usr/lib/python3/dist-packages/setuptools/__init__.py)

2020-05-03 Thread Lucas Nussbaum
Source: zope.i18nmessageid Version: 5.0.0-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200501 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > fakeroot debian/ru

Bug#959555: zope.interface: FTBFS: ImportError: cannot import name 'Feature' from 'setuptools' (/usr/lib/python3/dist-packages/setuptools/__init__.py)

2020-05-03 Thread Lucas Nussbaum
Source: zope.interface Version: 4.7.1-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200501 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > fakeroot debian/rules cl

Debian, to maint/upl of packages with fatal binaries error. (was send to wrong address)

2020-04-23 Thread Ben Tris
Hello, To package maintainer and/or uploader from Sorted out package(s) with this fatal testing migrations issue(s) Not built on buildd: arch X binaries uploaded by X and/or Not built on buildd: arch all binaries uploaded by X, a new source-only upload is needed to allow migration https://tracke

Debian, to maint/upl of packages with fatal binaries error.

2020-04-22 Thread Ben Tris
Hello, To package maintainer and or uploader(s) from Sorted out packages with this fatal testing migrations issue(s) Not built on buildd: arch X binaries uploaded by X and/or Not built on buildd: arch all binaries uploaded by X, a new source-only upload is needed to allow migration https

Processed: QA-maintained packages are not more problematic than others

2020-01-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 936358 normal Bug #936358 [src:cwiid] cwiid: Python2 removal in sid/bullseye Bug #942981 [src:cwiid] cwiid: Python2 removal in sid/bullseye Severity set to 'normal' from 'serious' Severity set to 'normal' from 'serious' > severity 938473

Processed (with 2 errors): Debian QA team will not maintain python2 packages

2019-12-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # Debian QA team does not have capacity to port python2 packages or > maintain them Unknown command or malformed arguments to command. > # bumping to RC packages with python2 removal bugs from this query > # > https://bugs.deb

Bug#936189: Packages depending on python-testtools are now RC: is bzr still a thing?

2019-09-15 Thread Thomas Goirand
he rdeps before > dropping packages, at least evaluating if breaking things is alrightif > he really likes to break packages :/ You mean check *better*. Because I do carefully check each time, as much as I can, but in this occurrence, it looks like I didn't check well enough. Mistakes unfort

Processed: Severity: serious for Py2 only packages depending on testtools

2019-09-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity #936189 serious Bug #936189 [src:bcfg2] bcfg2: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity #937165 serious Bug #937165 [src:nss-pam-ldapd] nss-pam-ldapd: Python2 removal in sid/bullseye Severity set

Bug#929850: marked as done (buildd.debian.org: possible conflict between the "dhelp" package and the KDE packages on debian buster)

2019-06-24 Thread Debian Bug Tracking System
Your message dated Mon, 24 Jun 2019 23:48:42 + with message-id and subject line Bug#929850: fixed in dhelp 0.6.26 has caused the Debian Bug report #929850, regarding buildd.debian.org: possible conflict between the "dhelp" package and the KDE packages on debian buster to be mark

  1   2   3   4   5   6   7   >