Bug#1027538: herisvm: FTBFS: dh_auto_build: error: exec (for cmd: mkcmake PREFIX=/usr MANDIR=/usr/share/man INFODIR=/usr/share/info SYSCONFDIR=/etc STRIPFLAG= LIBDIR=/usr/lib/x86_64-linux-gnu LIBEXECD

Source: herisvm Version: 0.9.0-2 Followup-For: Bug #1027538 Hi Lucas, I have rebuild the package on my local pc, but it works: ``` ... Build Architecture: amd64 Build Type: full Build-Space: 584 Build-Time: 11 Distribution: unstable Host Architecture: amd64 Install-Time: 23 Job:

Processed: tagging 1027934

Processing commands for cont...@bugs.debian.org: > # https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027934#14 > tags 1027934 + patch Bug #1027934 [src:hugin] hugin: misses link_directories Bug #1028198 [src:hugin] hugin: Blocks transition to python-3.11 Added tag(s) patch. Added tag(s) patch.

Processed: severity of 1028370 is important

Processing commands for cont...@bugs.debian.org: > severity 1028370 important Bug #1028370 [clusterssh] Connection to server failed Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 1028370:

Bug#1028370: Connection to server failed

Le 10/01/2023 à 07:56, Stéphane Glondu a écrit : Today, cssh does not work: $ cssh a b c d Connection to server failed -- (version 11.0) Authorization required, but no authorization protocol specified at /usr/share/perl5/App/ClusterSSH/Window/Tk.pm line 57. I'm pretty sure it was working 3

Bug#1027367: marked as done (golang-github-jinzhu-gorm: FTBFS in bullseye (missing build-depends on tzdata))

Your message dated Tue, 10 Jan 2023 07:04:35 + with message-id and subject line Bug#1027367: fixed in golang-github-jinzhu-gorm 1.9.6-2 has caused the Debian Bug report #1027367, regarding golang-github-jinzhu-gorm: FTBFS in bullseye (missing build-depends on tzdata) to be marked as done.

Bug#1028371: bernhard: needs rebuilds on top of new protobuf

Source: bernhard Version: 0.2.6-3 Severity: serious Hello, your package is tied to a specific protobuf version, but doesn't declare any explicit dependency on it Now, the package fails to load due to pb.py not being rebuilt. python3 -c "import bernhard" Traceback (most recent call last):

Bug#1028370: Connection to server failed

Package: clusterssh Version: 4.16-4 Severity: grave Dear Maintainer, Today, cssh does not work: $ cssh a b c d Connection to server failed -- (version 11.0) Authorization required, but no authorization protocol specified at /usr/share/perl5/App/ClusterSSH/Window/Tk.pm line 57. I'm pretty sure

Bug#1027363: marked as done (golang-github-araddon-dateparse: FTBFS in bullseye (missing build-depends on tzdata))

Your message dated Tue, 10 Jan 2023 06:38:27 + with message-id and subject line Bug#1027363: fixed in golang-github-araddon-dateparse 0.0~git20210429.6b43995-3 has caused the Debian Bug report #1027363, regarding golang-github-araddon-dateparse: FTBFS in bullseye (missing build-depends on

Bug#1027971: marked as done (virtualbox : Depends: python3 (< 3.11) but 3.11.1-1 is installed)

Your message dated Tue, 10 Jan 2023 07:11:25 +0100 with message-id <26701277-5f05-8f4b-f363-c79bb49f1...@debian.org> and subject line Re: virtualbox : Depends: python3 (< 3.11) but 3.11.1-1 is installed has caused the Debian Bug report #1027971, regarding virtualbox : Depends: python3 (< 3.11)

Processed: Re: Bug#1027476 closed by Debian FTP Masters (reply to Georges Khaznadar ) (Bug#1027476: fixed in cron 3.0pl1-155)

Processing control commands: > reopen -1 Bug #1027476 {Done: Georges Khaznadar } [cron] cron: postrm script fails because expected dpkg-statoverride is not present 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to

Bug#1027476: closed by Debian FTP Masters (reply to Georges Khaznadar ) (Bug#1027476: fixed in cron 3.0pl1-155)

Control: reopen -1 Hi! Although I've not tested nor checked the affected code, the fix done to close this cannot possibly be correct, see below. :) On Mon, 2023-01-09 at 21:27:06 +, Debian Bug Tracking System wrote: > Date: Sun, 01 Jan 2023 07:12:58 -0500 > From: "Kevin P. Fleming" > To:

Bug#1012496: marked as done (inkscape: FTBFS on arm64, ppc64el, s390x)

Your message dated Tue, 10 Jan 2023 03:25:24 + with message-id and subject line Bug#1012496: fixed in inkscape 1.2.2-2 has caused the Debian Bug report #1012496, regarding inkscape: FTBFS on arm64, ppc64el, s390x to be marked as done. This means that you claim that the problem has been dealt

Bug#922396: QA

Hi all, I found this package during my QA analysis. Based on the discussion and some QA elements I think a FTP RM could be useful for this package unless someone intends to upload a new version some day. Does someone think we should keep this package? The fact that there is updates upstream

Processed: tagging 1028240

Processing commands for cont...@bugs.debian.org: > tags 1028240 + pending Bug #1028240 [src:poetry] poetry: FTBFS (requires internet access) Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1028240:

Bug#1021079: disable the ppc64el binary for now?

Hi! As the window for new packages to [re-]enter bookworm will close soon, and fixing vectorscan on ppc doesn't appear to be coming, what about disabling that arch for now? It is described as "in development", thus it's not surprising it's not working yet. It'd be shame for the package to miss

Bug#1028171: marked as done (freecad FTBFS with Python 3.11 as default version)

Your message dated Tue, 10 Jan 2023 00:08:28 + with message-id and subject line Bug#1028171: fixed in freecad 0.20.2+dfsg1-1 has caused the Debian Bug report #1028171, regarding freecad FTBFS with Python 3.11 as default version to be marked as done. This means that you claim that the problem

Bug#1027506: Status of mozillavpn in Debian

On 1/9/23 23:26, Sylvestre Ledru wrote: Le 08/01/2023 à 00:46, Richard B. Kreckel a écrit : 2) Based on mozillavpn_2.9.0-1.debian.tar.xz, apply some changes to debian/ directory:    a) -DBUILD_TESTING=OFF to dh_auto_configure argument in debian/rules (without it it FTBFS trying to run some

Bug#1023965: marked as done (pandas FTBFS with Python 3.11 as supported version)

Your message dated Mon, 09 Jan 2023 23:21:54 + with message-id and subject line Bug#1023965: fixed in pandas 1.5.2+dfsg-4 has caused the Debian Bug report #1023965, regarding pandas FTBFS with Python 3.11 as supported version to be marked as done. This means that you claim that the problem

Processed: tagging 1027206

Processing commands for cont...@bugs.debian.org: > tags 1027206 + ftbfs Bug #1027206 [src:qiskit-aer] qiskit-aer: autopkgtest fail with numpy/1.24.1 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1027206:

Processed: Re: Bug#1028356: procmail: Variable set with stdin pipe action fails leaving empty variable

Processing commands for cont...@bugs.debian.org: > forwarded 1028356 https://github.com/BuGlessRB/procmail/issues/5 Bug #1028356 [procmail] procmail: Variable set with stdin pipe action fails leaving empty variable Set Bug forwarded-to-address to

Bug#1028356: procmail: Variable set with stdin pipe action fails leaving empty variable

forwarded 1028356 https://github.com/BuGlessRB/procmail/issues/5 tags 1028356 + help thanks Hi. I've forwarded the bug by making a github issue from it. There is a full git history for procmail at github. If you feel brave enough you could try a git-bisect on the code to see where this bug was

Processed: fix email address

Processing commands for cont...@bugs.debian.org: > submitter 1028356 ! Bug #1028356 [procmail] procmail: Variable set with stdin pipe action fails leaving empty variable Changed Bug submitter to 'Bob Proulx ' from 'Bob Proulx '. > thanks Stopping processing here. Please contact me if you need

Bug#1028297: marked as done (python3-freezegun: ships a copy of python3-arrow: /usr/lib/python3/dist-packages/arrow/*.py)

Your message dated Mon, 09 Jan 2023 22:49:39 + with message-id and subject line Bug#1028297: fixed in freezegun 1.2.1+actually1.2.1-1 has caused the Debian Bug report #1028297, regarding python3-freezegun: ships a copy of python3-arrow: /usr/lib/python3/dist-packages/arrow/*.py to be marked

Bug#1028356: procmail: Variable set with stdin pipe action fails leaving empty variable

El 9/1/23 a las 23:13, Bob Proulx escribió: Unfortunately in 3.24 this functionality is broken. I see in the Testing migration "excuses" this "Too young, only 4 of 5 days old". Should severity be "important" in order to keep Testing from breaking? I've just set it to serious, which is the

Processed: severity

Processing commands for cont...@bugs.debian.org: > severity 1028356 serious Bug #1028356 [procmail] procmail: Variable set with stdin pipe action fails leaving empty variable Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#1028359: pygpu: fails to import in numpy 1.24

Package: python3-pygpu Version: 0.7.6-12 Severity: grave numpy 1.24 no longer has np.bool, which makes pygpu fail to import: pygpu/dtypes.py:74: in _fill_dtype_registry register_dtype(np.bool, ["ga_bool", "bool"]) numpy/__init__.py:284: in __getattr__ raise AttributeError("module {!r}

Bug#1027506: Status of mozillavpn in Debian

Le 08/01/2023 à 00:46, Richard B. Kreckel a écrit : 2) Based on mozillavpn_2.9.0-1.debian.tar.xz, apply some changes to debian/ directory:    a) -DBUILD_TESTING=OFF to dh_auto_configure argument in debian/rules (without it it FTBFS trying to run some tests and that is also in upstream's 

Bug#1027506: Status of mozillavpn in Debian

Le 08/01/2023 à 00:46, Richard B. Kreckel a écrit : 2) Based on mozillavpn_2.9.0-1.debian.tar.xz, apply some changes to debian/ directory:    a) -DBUILD_TESTING=OFF to dh_auto_configure argument in debian/rules (without it it FTBFS trying to run some tests and that is also in upstream's 

Processed: Re: libmaa: FTBFS: dh_auto_build: error: exec (for cmd: mkcmake PREFIX=/usr MANDIR=/usr/share/man INFODIR=/usr/share/info SYSCONFDIR=/etc STRIPFLAG= LIBDIR=/usr/lib/x86_64-linux-gnu LIBEXEC

Processing control commands: > severity -1 normal Bug #1027657 [src:libmaa] libmaa: FTBFS: dh_auto_build: error: exec (for cmd: mkcmake PREFIX=/usr MANDIR=/usr/share/man INFODIR=/usr/share/info SYSCONFDIR=/etc STRIPFLAG= LIBDIR=/usr/lib/x86_64-linux-gnu LIBEXECDIR=/usr/lib/x86_64-linux-gnu)

Bug#1027657: libmaa: FTBFS: dh_auto_build: error: exec (for cmd: mkcmake PREFIX=/usr MANDIR=/usr/share/man INFODIR=/usr/share/info SYSCONFDIR=/etc STRIPFLAG= LIBDIR=/usr/lib/x86_64-linux-gnu LIBEXECDI

Control: severity -1 normal Control: notfound -1 libmaa/1.4.7-1 Control: tags -1 - ftbfs On Mon, 9 Jan 2023 10:51:06 +0200 Peter Pentchev wrote: FTR, I think this was fixed by the upload of mk-configure/0.37.0-2, which actually installed the package files (including the mkcmake program). I

Bug#1026088: rdma-core: diff for NMU version 44.0-1.1

Control: tags 1026088 + patch Control: tags 1026088 + pending Dear maintainer, I've prepared an NMU for rdma-core (versioned as 44.0-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru rdma-core-44.0/debian/changelog

Bug#1028269: marked as done (mender-connect FTBFS: test failures)

Your message dated Mon, 9 Jan 2023 23:13:31 +0100 with message-id <20230109221331.mxuymgzo54iib...@fatal.se> and subject line Re: mender-connect FTBFS: test failures has caused the Debian Bug report #1028269, regarding mender-connect FTBFS: test failures to be marked as done. This means that you

Processed: rdma-core: diff for NMU version 44.0-1.1

Processing control commands: > tags 1026088 + patch Bug #1026088 [src:rdma-core] rdma-core: add mips64* to COHERENT_DMA_ARCHS Added tag(s) patch. > tags 1026088 + pending Bug #1026088 [src:rdma-core] rdma-core: add mips64* to COHERENT_DMA_ARCHS Added tag(s) pending. -- 1026088:

Bug#1028354: apbs fails with python3.11: "invalid mode rU"

Package: apbs Version: 3.4.1-4 Severity: grave Tags: patch Justification: renders package unusable User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu lunar ubuntu-patch apbs fails its autopkgtests with python3.11, revealing a bug in the software, because it uses a mode flag to open()

Bug#1027254: dask and pandas 1.5

(I meant to send that to the dask/pandas bug, which is #1025393, but both of them are potential reasons to update dask.) The intake issue is now https://github.com/dask/dask/issues/9813 (They're planning to fix it in intake rather than dask, but we might not be allowed to do that after the

Processed: Re: ulmo fails in pandas 1.4+

Processing control commands: > forwarded -1 https://github.com/ulmo-dev/ulmo/pull/214 Bug #1017573 [python3-ulmo] python3-ulmo: autopkgtest fail with pandas 1.4 Set Bug forwarded-to-address to 'https://github.com/ulmo-dev/ulmo/pull/214'. > severity -1 serious Bug #1017573 [python3-ulmo]

Bug#1028097: marked as done (mplcursors: remove Build-Depends: libopenblas0 (use libblas-dev instead))

Your message dated Mon, 09 Jan 2023 21:52:16 + with message-id and subject line Bug#1028097: fixed in mplcursors 0.5.2-2 has caused the Debian Bug report #1028097, regarding mplcursors: remove Build-Depends: libopenblas0 (use libblas-dev instead) to be marked as done. This means that you

Bug#1019781: dolphin-emu: Please transition to wxwidgets3.2

On Wed, Sep 14, 2022 at 03:42:14PM -0400, s...@techie.net wrote: > Please transition dolphin-emu from wxwidgets3.0 to wxwidgets3.2. I've been looking through the handful of packages which are still using wxwidgets3.0 with an eye to seeing if any can usefully be NMUed to help them reenter testing

Bug#956949: elektra build depends on cruft package swig3.0

Looks like newer versions can be built with swig 4. Please import a new version.

Bug#1028129: marked as done (securestring FTBFS: fatal error: Python.h: No such file or directory)

Your message dated Mon, 09 Jan 2023 21:33:11 + with message-id and subject line Bug#1028129: fixed in securestring 0.2-2 has caused the Debian Bug report #1028129, regarding securestring FTBFS: fatal error: Python.h: No such file or directory to be marked as done. This means that you claim

Bug#1026769: marked as done (rust-trust-dns-proto - uninstallable on architectures other than arm* and x86*)

Your message dated Mon, 09 Jan 2023 21:32:26 + with message-id and subject line Bug#1026769: fixed in rust-trust-dns-proto 0.22.0-2 has caused the Debian Bug report #1026769, regarding rust-trust-dns-proto - uninstallable on architectures other than arm* and x86* to be marked as done. This

Bug#1027476: marked as done (cron: postrm script fails because expected dpkg-statoverride is not present)

Your message dated Mon, 09 Jan 2023 21:24:40 + with message-id and subject line Bug#1027476: fixed in cron 3.0pl1-155 has caused the Debian Bug report #1027476, regarding cron: postrm script fails because expected dpkg-statoverride is not present to be marked as done. This means that you

Processed: zeroc-ice: diff for NMU version 3.7.8-1.1

Processing control commands: > tags 1027849 + pending Bug #1027849 [src:zeroc-ice] zeroc-ice FTBFS with Python 3.11 as default version Added tag(s) pending. -- 1027849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027849 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1027849: zeroc-ice: diff for NMU version 3.7.8-1.1

Control: tags 1027849 + pending Dear maintainer, I've prepared an NMU for zeroc-ice (versioned as 3.7.8-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru zeroc-ice-3.7.8/debian/changelog zeroc-ice-3.7.8/debian/changelog ---

Bug#1019799: marked as done (libalien-wxwidgets-perl: Please transition to wxwidgets3.2)

Your message dated Mon, 9 Jan 2023 15:58:01 -0500 (EST) with message-id and subject line Fixed by today's upload has caused the Debian Bug report #1019799, regarding libalien-wxwidgets-perl: Please transition to wxwidgets3.2 to be marked as done. This means that you claim that the problem has

Bug#1027227: marked as done (mdanalysis: autopkgtest fail with numpy/1.24.1)

Your message dated Mon, 09 Jan 2023 20:49:17 + with message-id and subject line Bug#1027227: fixed in mdanalysis 2.4.2+dfsg1-1 has caused the Debian Bug report #1027227, regarding mdanalysis: autopkgtest fail with numpy/1.24.1 to be marked as done. This means that you claim that the problem

Bug#1027398: marked as done (gavodachs: autopkgtest needs update for new version of python-cryptography: fails to install)

Your message dated Mon, 09 Jan 2023 20:42:30 + with message-id and subject line Bug#1027398: fixed in gavodachs 2.7+dfsg-2 has caused the Debian Bug report #1027398, regarding gavodachs: autopkgtest needs update for new version of python-cryptography: fails to install to be marked as done.

Bug#1027213: marked as done (gavodachs: autopkgtest fail with numpy/1.24.1)

Your message dated Mon, 09 Jan 2023 20:42:30 + with message-id and subject line Bug#1027213: fixed in gavodachs 2.7+dfsg-2 has caused the Debian Bug report #1027213, regarding gavodachs: autopkgtest fail with numpy/1.24.1 to be marked as done. This means that you claim that the problem has

Bug#1028303: marked as done (dracut-core: missing Breaks+Replaces: dracut-live (<< 059-2))

Your message dated Mon, 09 Jan 2023 20:41:26 + with message-id and subject line Bug#1028303: fixed in dracut 059-3 has caused the Debian Bug report #1028303, regarding dracut-core: missing Breaks+Replaces: dracut-live (<< 059-2) to be marked as done. This means that you claim that the

Bug#1028350: davmail: autopkgtest regression on arm64, armhf and ppc64el: Unable to store settings: /etc/davmail.properties (Permission denied)

Source: davmail Version: 6.0.1.3390-5 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of davmail the autopkgtest of davmail fails in testing when that autopkgtest is run with the binary packages of davmail from unstable on

Bug#1027193: marked as done (brian: autopkgtest fail with numpy/1.24.1)

Your message dated Mon, 09 Jan 2023 19:35:19 + with message-id and subject line Bug#1027193: fixed in brian 2.5.1-3 has caused the Debian Bug report #1027193, regarding brian: autopkgtest fail with numpy/1.24.1 to be marked as done. This means that you claim that the problem has been dealt

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

Processing control commands: > close -1 3.7.3-1 Bug #1028348 [src:r-cran-callr] src:r-cran-callr: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions r-cran-callr/3.7.3-1. Bug #1028348 [src:r-cran-callr] src:r-cran-callr: fails to migrate to testing for

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

Source: r-cran-callr Version: 3.7.2-1 Severity: serious Control: close -1 3.7.3-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60

Bug#1028303: dracut-core: missing Breaks+Replaces: dracut-live (<< 059-2)

On 09/01/2023 18.16, Thomas Lange wrote: Hi Andreas, should I replace the old Breaks+Replaces with the new ones, or add them? These are the current for dracut-core: Breaks: dracut-network (<< 057+157-2) Replaces: dracut-network (<< 057+157-2) Add them. Janitor will tell you once the old ones

Bug#1028023: marked as done (librepo FTBFS on MIPS)

On Mon, Jan 09, 2023 at 08:17:14PM +0200, Adrian Bunk wrote: > I "improved" it by also breaking the build on all other architectures... > :-( > The things that happen when trying to fix a problem you cannot reproduce. only those who do, do mistakes :) > Patch with the missing import added is

Bug#994108: gcc-9: do not release with bookworm

On Sat, 11 Sep 2021 23:33:44 +0200 Sebastian Ramacher wrote: With only odb left requring gcc-9 (#994104), let's remove gcc-9, gcc-9-cross and gcc-9-cross-ports from bookworm. This bug is here to keep gcc-9 out of bookworm once removed from there (unless removal from unstable happens sooner, of

Bug#1028346: php-horde-imap-client: fails on login: Return value of Horde_Imap_Client_Tokenize::current() must be an instance of mixed,

Package: php-horde-imap-client Version: 2.30.6-1 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, With php7.4-fpm, after updating to 2.30.6-1 users are unable to login. Login attempts generate the following error: HORDE: [imp] TypeError: Return value of

Bug#1028345: python3-sage: sagemath uninstallable due to python3-sage issues

Package: python3-sage Version: 9.5-4+b3 Severity: grave Justification: renders package unusable X-Debbugs-Cc: baronr...@gmail.com Dear Maintainer, python3-sage depends on python3 < 3.11, which conflicts with current python 3.11.1-1, and on libsingular4m2n1, which is unavailable. I therefore

Bug#1028023: marked as done (librepo FTBFS on MIPS)

On Mon, Jan 09, 2023 at 02:04:22PM +, Holger Levsen wrote: > control: reopen -1 > thanks > > librepo 1.14.5-2 still fails to build as 1.14.5-1 did, see > https://buildd.debian.org/status/package.php?p=librepo I "improved" it by also breaking the build on all other architectures... :-( The

Bug#1028297: python3-freezegun: ships a copy of python3-arrow: /usr/lib/python3/dist-packages/arrow/*.py

On Mon, Jan 09, 2023 at 11:59:42AM +0100, Andreas Beckmann wrote: > Package: python3-freezegun > Version: 1.2.1-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > during a test with piuparts I noticed your package failed to install > because it tries to overwrite

Bug#1028303: dracut-core: missing Breaks+Replaces: dracut-live (<< 059-2)

Hi Andreas, should I replace the old Breaks+Replaces with the new ones, or add them? These are the current for dracut-core: Breaks: dracut-network (<< 057+157-2) Replaces: dracut-network (<< 057+157-2) -- regards Thomas

Bug#1027254: dask and pandas 1.5

On Mon, 2023-01-09 at 08:00 +, Rebecca N. Palmer wrote: > To get the new upstream version to work, dask_sphinx-theme, dask and > dask.distributed all need to be updated, in that order.  Tests here: > https://launchpad.net/~rebecca-palmer/+archive/ubuntu/dask2022p12v2/+packages Ok thanks for

Bug#1019799: Proposed MBF: wxwidgets3.2 transition

On Sun, 08 Jan 2023 16:56:14 -0500, Scott Talbert wrote: > On Thu, 15 Sep 2022, gregor herrmann wrote: > > On Thu, 15 Sep 2022 15:13:24 -0400, Scott Talbert wrote: > > > Thanks for your work so far. I'll try to take a stab at it... > > Great, thank you! > > (The preliminary patch is in git: > >

Bug#1016963: Please test u-boot for rpi_4 rpi_4_32b

Hey, On Fri, 2023-01-06 at 16:36 +0100, Andreas Henriksson wrote: > On Tue, Jan 03, 2023 at 11:56:51PM +0100, Andreas Henriksson wrote: > > On Tue, Jan 03, 2023 at 11:46:31PM +0100, Andreas Henriksson wrote: > > > On Wed, Dec 28, 2022 at 04:11:04PM -0800, Vagrant Cascadian > > > wrote: > > > >

Bug#1028333: puppetserver: find an upgrade path from puppet-master

Package: puppetserver Severity: grave At the moment, this package doesn't acknowledge the existence of the puppet-master package at all. As such, if the two packages are installed on the same machines, important breakage is likely. A proper upgrade path should be found, to make the

Processed: severity of 1028324 is serious

Processing commands for cont...@bugs.debian.org: > severity 1028324 serious Bug #1028324 [src:cduce] RM: cduce -- RoQA, unmaintained, FTBFS, zero popcon Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1028324:

Bug#1028325: RM: myodbc -- RoQA, unmaintained, FTBFS since years

Source: myodbc Severity: serious Justification: QA User: tobi-rm-proposals@d.o Usertags: rm-proposal Dear Maintainer, - the package has currently 5 RC bugs and FTBFS on all architectures: #835166 [G| | ] [libmyodbc] libmyodbc: SIGFPE, Arithmetic exception in sqlchar_as_sqlwchar #868882 [G|

Bug#1023972: Python 3.11 for bookworm?

Hi Simon, On 2023-01-07 13:24, Simon McVittie wrote: On Sat, 07 Jan 2023 at 10:23:19 +0200, Andrius Merkys wrote: If I may, I would as well be grateful if someone could give a look at: #1023972 [src:python-ase] FTBFS with Python 3.11 due to pathlib.Path.__enter__() deprecation I have no idea

Bug#976506: Fix for bullseye

El 9/1/23 a las 16:25, Nilesh Patra escribió: I would make an upload proposal in the form of debdiff, but I'm unsure about backporting the fix in unstable to stable in this case, because I don't really understand it. I will not do it, it is not worth the effort. The package is functional, it

Bug#991067: reopen for bullseye

reopen 991067 found 991067 1.2-1 found 991067 1.2-4 fixed 991067 1.2-5 thanks Note: There is already a release.debian.org bug with a debdiff.

Processed: reopen for bullseye

Processing commands for cont...@bugs.debian.org: > reopen 991067 Bug #991067 {Done: Santiago Vila } [src:x4d-icons] x4d-icons FTBFS with imagemagick with the #987504 change 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may

Bug#1028323: RM: vdr-plugin-remoteosd -- RoQA, unmaintained, FTBFS, dead upstream, low popcon

Source: vdr-plugin-remoteosd Severity: serious Justification: QA User: tobi-rm-proposals@d.o Usertags: rm-proposal Dear Maintainer, - the package has currently 1 RC (FTBFS) bug on all architectures: #872495 [S|⛺| ] [src:vdr-plugin-remoteosd] vdr-plugin-remoteosd FTBFS with vdr 2.3.8 - It is

Bug#1028249: marked as done (warzone2100: Missing build dependency on libopus-dev)

Your message dated Mon, 09 Jan 2023 15:27:05 + with message-id and subject line Bug#1028249: fixed in warzone2100 4.3.3-2 has caused the Debian Bug report #1028249, regarding warzone2100: Missing build dependency on libopus-dev to be marked as done. This means that you claim that the problem

Bug#997183: marked as done (meterec: FTBFS: display.c:474:9: error: format not a string literal and no format arguments [-Werror=format-security])

Your message dated Mon, 09 Jan 2023 15:24:28 + with message-id and subject line Bug#997183: fixed in meterec 0.9.3-2 has caused the Debian Bug report #997183, regarding meterec: FTBFS: display.c:474:9: error: format not a string literal and no format arguments [-Werror=format-security] to be

Bug#1026719: marked as done (vmg: FTBFS: /usr/bin/ld.bfd: cannot find -latk-1.0: No such file or directory)

Your message dated Mon, 09 Jan 2023 15:23:53 + with message-id and subject line Bug#1026718: fixed in lazpaint 7.2.2-2 has caused the Debian Bug report #1026718, regarding vmg: FTBFS: /usr/bin/ld.bfd: cannot find -latk-1.0: No such file or directory to be marked as done. This means that you

Bug#976506: Fix for bullseye

On 9 January 2023 8:11:11 pm IST, Santiago Vila wrote: >reopen 976506 >found 976506 1.7.2-1 >found 976506 1.7.2-2 >fixed 976506 2.0.1-1 >thanks > >Hi. Please consider fixing this in stable as well, >as packages in stable must build in stable. > >If you have never done an upload for stable, the

Bug#1028321: RM: vdr-plugin-infosatepg -- RoQA, unmaintained, FTBFS, dead upstream, low popcon

Source: vdr-plugin-infosatepg Severity: serious Justification: QA User: tobi-rm-proposals@d.o Usertags: rm-proposal Dear Maintainer, - the package has currently 1 RC (FTBFS) bug on all architectures: #872487 [S|⛺| ] [src:vdr-plugin-infosatepg] vdr-plugin-infosatepg FTBFS with vdr 2.3.8 - It

Bug#1028166: marked as done (commons-configuration: Build-depends on NBS package about to FTBFS)

Your message dated Mon, 09 Jan 2023 15:20:19 + with message-id and subject line Bug#1028166: fixed in commons-configuration 1.10-6 has caused the Debian Bug report #1028166, regarding commons-configuration: Build-depends on NBS package about to FTBFS to be marked as done. This means that you

Bug#1028298: marked as done (juff-dev: missing Breaks+Replaces: juffed-dev (<< 0.10-89-g3690b60-6))

Your message dated Mon, 9 Jan 2023 23:16:31 +0800 with message-id and subject line juff-dev: missing Breaks+Replaces: juffed-dev (<< 0.10-89-g3690b60-6) has caused the Debian Bug report #1028298, regarding juff-dev: missing Breaks+Replaces: juffed-dev (<< 0.10-89-g3690b60-6) to be marked as

Processed: Bug#1023972 marked as pending in python-ase

Processing control commands: > tag -1 pending Bug #1023972 [src:python-ase] python-ase: FTBFS with Python 3.11 due to pathlib.Path.__enter__() deprecation Added tag(s) pending. -- 1023972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023972 Debian Bug Tracking System Contact

Bug#1027836: marked as done (planner,planner-data: both ship /usr/share/planner/images/gnome-planner.png)

Your message dated Mon, 09 Jan 2023 14:59:10 + with message-id and subject line Bug#1027836: fixed in planner 0.14.91-2 has caused the Debian Bug report #1027836, regarding planner,planner-data: both ship /usr/share/planner/images/gnome-planner.png to be marked as done. This means that you

Bug#1023972: marked as pending in python-ase

Control: tag -1 pending Hello, Bug #1023972 in python-ase 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:

Bug#1028169: marked as done (maven-reporting-impl: Build-depends on NBS package, will soon FTBS)

Your message dated Mon, 09 Jan 2023 14:57:07 + with message-id and subject line Bug#1028169: fixed in maven-reporting-impl 3.2.0-1 has caused the Debian Bug report #1028169, regarding maven-reporting-impl: Build-depends on NBS package, will soon FTBS to be marked as done. This means that you

Processed: Re: Bug#1028111: r-cran-clock: autopkgtest failure on 32bit

Processing control commands: > tags -1 upstream Bug #1028111 [src:r-cran-clock] r-cran-clock: autopkgtest failure on 32bit Added tag(s) upstream. > forwarded -1 https://github.com/r-lib/clock/issues/312 Bug #1028111 [src:r-cran-clock] r-cran-clock: autopkgtest failure on 32bit Set Bug

Bug#1028111: r-cran-clock: autopkgtest failure on 32bit

Control: tags -1 upstream Control: forwarded -1 https://github.com/r-lib/clock/issues/312 I've forwarded the issue to the upstream issue tracker. Kind regards Andreas. Am Sat, Jan 07, 2023 at 03:02:04AM +0200 schrieb Adrian Bunk: > Source: r-cran-clock > Version: 0.6.1-1 > Severity: serious

Bug#1028129: #1028129: securestring FTBFS: fatal error: Python.h: No such file or directory

Hi, Bo YU: thanks a lot for your recent work on securestring! Do you plan to upload it, or would you prefer me to handle that? (I have time to take care of it this week.) Bye, Joost

Processed: Fix for bullseye

Processing commands for cont...@bugs.debian.org: > reopen 976506 Bug #976506 {Done: Nilesh Patra } [src:conda-package-handling] conda-package-handling: FTBFS in bullseye (failing tests) 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared,

Bug#976506: Fix for bullseye

reopen 976506 found 976506 1.7.2-1 found 976506 1.7.2-2 fixed 976506 2.0.1-1 thanks Hi. Please consider fixing this in stable as well, as packages in stable must build in stable. If you have never done an upload for stable, the procedure is documented here:

Processed: limit source to gnustep-base, tagging 1028189

Processing commands for cont...@bugs.debian.org: > limit source gnustep-base Limiting to bugs with field 'source' containing at least one of 'gnustep-base' Limit currently set to 'source':'gnustep-base' > tags 1028189 + pending Bug #1028189 [src:gnustep-base] gnustep-base/1.28.1-2 should not

Processed: Re: Bug#1028023: marked as done (librepo FTBFS on MIPS)

Processing control commands: > reopen -1 Bug #1028023 [src:librepo] librepo FTBFS on MIPS Bug 1028023 is not marked as done; doing nothing. -- 1028023: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028023 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: voms-api-java: FTBFS in bullseye because of expired certificates

Processing commands for cont...@bugs.debian.org: > reopen 1021551 Bug #1021551 {Done: Mattias Ellert } [src:voms-api-java] FTBFS: 11 test failures '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

Processed: Re: Bug#1028023: marked as done (librepo FTBFS on MIPS)

Processing control commands: > reopen -1 Bug #1028023 {Done: Frédéric Pierret } [src:librepo] librepo FTBFS on MIPS '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

Bug#1021551: voms-api-java: FTBFS in bullseye because of expired certificates

reopen 1021551 retitle 1021551 voms-api-java: FTBFS in bullseye because of expired certificates in test suite found 1021551 3.3.2-1 found 1021551 3.3.2-3 fixed 1021551 3.3.2-4 tags 1021551 + ftbfs thanks Hi. I'm reopening because this problem also happens in bullseye, and packages in stable

Bug#1028023: marked as done (librepo FTBFS on MIPS)

control: reopen -1 thanks librepo 1.14.5-2 still fails to build as 1.14.5-1 did, see https://buildd.debian.org/status/package.php?p=librepo -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D

Processed: severity

Processing commands for cont...@bugs.debian.org: > severity 1026914 normal Bug #1026914 [arcanist] arcanist client improperly uploading files Severity set to 'normal' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 1026914:

Bug#1027175: marked as done (ceph: Missing adduser dependency for ceph-common and cephadm)

Your message dated Mon, 09 Jan 2023 13:54:11 + with message-id and subject line Bug#1027175: fixed in ceph 16.2.10+ds-5 has caused the Debian Bug report #1027175, regarding ceph: Missing adduser dependency for ceph-common and cephadm to be marked as done. This means that you claim that the

Processed: severity of 942501 is serious

Processing commands for cont...@bugs.debian.org: > severity 942501 serious Bug #942501 [src:milter-greylist] src:milter-greylist: please drop libbind-dev build dependency, it's not in use and libbind-dev is going away Severity set to 'serious' from 'important' > thanks Stopping processing here.

Bug#1011437: Should bind9-libs be shipped in bookworm?

> On 9. 1. 2023, at 14:50, Bernhard Schmidt wrote: > > Hi, > >>> not about src:bind9, building the bind9-libs binary package (yes, this is >>> totally confusing, even to Debian tooling) >> I though that had been already removed: >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011538

Processed: unarchive for bullseye

Processing commands for cont...@bugs.debian.org: > unarchive 1021551 Bug #1021551 {Done: Mattias Ellert } [src:voms-api-java] FTBFS: 11 test failures Unarchived Bug 1021551 > thanks Stopping processing here. Please contact me if you need assistance. -- 1021551:

Bug#1011437: Should bind9-libs be shipped in bookworm?

Hi, not about src:bind9, building the bind9-libs binary package (yes, this is totally confusing, even to Debian tooling) I though that had been already removed: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011538 But I

  1   2   >