Processed: fixed 1022957 in 525.147.05-7

2024-02-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 1022957 525.147.05-7 Bug #1022957 [nex] nex: /usr/bin/nex is already provided by the nvi package There is no source info for the package 'nex' at version '525.147.05-7' with architecture '' Unable to make a source version for version

Bug#1057549: crowdsec: FTBFS: FAIL: TestOneShot/permission_denied

2024-02-15 Thread Cyril Brulebois
Hi, Cyril Brulebois (2024-01-17): > Santiago Vila (2023-12-05): > > […] > > Thanks for the report. The relevant part didn't appear in the excerpt > so I'm quoting the full build log below: > > > === RUN TestOneShot/permission_denied > > file_test.go:234: > > Error Trace:

Processed: Retag some bugs

2024-02-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1063497 - patch + fixed-upstream bookworm Bug #1063497 [src:zfs-linux] zfs-dkms: Data loss bug in version in bookworm Removed tag(s) patch. Bug #1063497 [src:zfs-linux] zfs-dkms: Data loss bug in version in bookworm Added tag(s)

Processed: Re-assign conflicts bug to non-free participant

2024-02-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1063400 src:pgplot5 Bug #1063400 [src:plplot5] giza-dev: missing Conflicts: pgplot5t64 Warning: Unknown package 'src:plplot5' Bug reassigned from package 'src:plplot5' to 'src:pgplot5'. Ignoring request to alter found versions of bug

Processed: notfixed 1022957 in 525.147.05-7, fixed 1063362 in 525.147.05-7

2024-02-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfixed 1022957 525.147.05-7 Bug #1022957 [nex] nex: /usr/bin/nex is already provided by the nvi package There is no source info for the package 'nex' at version '525.147.05-7' with architecture '' Unable to make a source version for version

Bug#1063845: marked as done (unbound: Package 1.19.1 to fix CVE-2023-50387 and CVE-2023-50868)

2024-02-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Feb 2024 10:02:40 + with message-id and subject line Bug#1063845: fixed in unbound 1.13.1-1+deb11u2 has caused the Debian Bug report #1063845, regarding unbound: Package 1.19.1 to fix CVE-2023-50387 and CVE-2023-50868 to be marked as done. This means that you claim

Bug#1060961: marked as done (clapper: FTBFS: make: *** [debian/rules:6: binary] Error 25)

2024-02-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Feb 2024 11:00:31 +0100 with message-id <170799123103.3855153.12503207033974967424@localhost> and subject line Re: clapper: FTBFS: make: *** [debian/rules:6: binary] Error 25 has caused the Debian Bug report #1060961, regarding clapper: FTBFS: make: *** [debian/rules:6:

Bug#1060936: marked as done (udm: FTBFS: make[1]: *** [debian/rules:68: override_dh_auto_build] Error 2)

2024-02-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Feb 2024 13:05:11 +0200 with message-id and subject line udm: FTBFS: make[1]: *** [debian/rules:68: override_dh_auto_build] Error 2 has caused the Debian Bug report #1060936, regarding udm: FTBFS: make[1]: *** [debian/rules:68: override_dh_auto_build] Error 2 to be

Bug#1063922: libnfft3-long4 has an undeclared file conflict

2024-02-15 Thread Andreas Beckmann
Followup-For: Bug #1063922 This looks like you want Breaks+Replaces: libnfft3-long2 (>= 3.5) (Yes, really a >= relation, as the older versions are co-installable, only the versions that didn't do the required transition are the problem.) Andreas

Bug#1061024: marked as done (transgui: FTBFS: InitializeFppkg failed: Unable to create file "/sbuild-nonexistent/.config/fppkg.cfg": No such file or directory)

2024-02-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Feb 2024 13:04:16 +0200 with message-id and subject line transgui: FTBFS: InitializeFppkg failed: Unable to create file "/sbuild-nonexistent/.config/fppkg.cfg": No such file or directory has caused the Debian Bug report #1061024, regarding transgui: FTBFS:

Processed: Re-assign conflicts bug to non-free participant

2024-02-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1063400 src:plplot5 Bug #1063400 [giza-dev] giza-dev: missing Conflicts: pgplot5t64 Bug reassigned from package 'giza-dev' to 'src:plplot5'. Warning: Unknown package 'src:plplot5' Warning: Unknown package 'src:plplot5' No longer marked

Processed: Re-assign conflicts bug to non-free participant

2024-02-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1063400 pgplot5 5.2.2-19.6~exp1 Bug #1063400 [src:pgplot5] giza-dev: missing Conflicts: pgplot5t64 Bug reassigned from package 'src:pgplot5' to 'pgplot5'. Ignoring request to alter found versions of bug #1063400 to the same values

Bug#1063942: nginx: Violation of DFSG article 5

2024-02-15 Thread Anon
Source: nginx Version: 1.24.0-2 Severity: serious Tags: upstream Justification: Policy 2.1.5 Dear Maintainer, The company behind nginx fired half of their most senior programmers two years ago, due to the country in which they reside (Russia). This might be a violation of DFSG 5 (Debian Policy

Bug#1061341: marked as done (cyrus-common: identified for time_t transition but no ABI in shlibs)

2024-02-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Feb 2024 09:50:07 + with message-id and subject line Bug#1061341: fixed in cyrus-imapd 3.10.0~beta1-2 has caused the Debian Bug report #1061341, regarding cyrus-common: identified for time_t transition but no ABI in shlibs to be marked as done. This means that you

Bug#1063942: marked as done (nginx: Violation of DFSG article 5)

2024-02-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Feb 2024 10:31:03 + with message-id <20240215103103.ga1343...@tack.einval.com> and subject line Re: Bug#1063942: nginx: Violation of DFSG article 5 has caused the Debian Bug report #1063942, regarding nginx: Violation of DFSG article 5 to be marked as done. This

Bug#1056419: Spinx help needed

2024-02-15 Thread Dmitry Shachnev
Hi Andreas! On Thu, Feb 15, 2024 at 08:37:38AM +0100, Andreas Tille wrote: > Control: tags -1 pending > > Hi, > > I pushed fixes for #1056419 and #1058311 to Git and I think should be > fixed as well. The only remaining build problem is new and caused by > sphinx[1]: > > dh_sphinxdoc -i

Bug#1059040: marked as done (libxml2: ABI change? (undefined references))

2024-02-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Feb 2024 10:06:30 + with message-id and subject line Bug#1059040: fixed in libxml2 2.12.5+dfsg-0exp1 has caused the Debian Bug report #1059040, regarding libxml2: ABI change? (undefined references) to be marked as done. This means that you claim that the problem

Bug#1061341: marked as done (cyrus-common: identified for time_t transition but no ABI in shlibs)

2024-02-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Feb 2024 10:05:23 + with message-id and subject line Bug#1061341: fixed in cyrus-imapd 3.8.1-2 has caused the Debian Bug report #1061341, regarding cyrus-common: identified for time_t transition but no ABI in shlibs to be marked as done. This means that you claim

Bug#1061341: cyrus-common: identified for time_t transition but no ABI in shlibs

2024-02-15 Thread Yadd
I closed this issue because: - I dropped all bad .h files from install - I added ABI flags to build - cyrus-dev has no reverse dependencies If I'm wrong, please reopen this issue Cheers, Yadd

Bug#1063364: marked as done (nvidia-cuda-samples: autopkgtest needs update for new version of linux)

2024-02-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Feb 2024 13:17:27 +0100 with message-id <98a2b0d4-63a1-743c-3081-5e406c34b...@debian.org> and subject line Re: nvidia-cuda-samples: autopkgtest needs update for new version of linux has caused the Debian Bug report #1063364, regarding nvidia-cuda-samples: autopkgtest

Bug#1063879: marked as done (linux-image-6.1.0-18-amd64: nvidia-drivers 525.147.05 do not compile against linux-image 6.1.0-18)

2024-02-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Feb 2024 15:02:18 + with message-id and subject line Bug#1062932: fixed in nvidia-graphics-drivers-tesla 525.147.05-7~deb12u1 has caused the Debian Bug report #1062932, regarding linux-image-6.1.0-18-amd64: nvidia-drivers 525.147.05 do not compile against

Bug#1063362: marked as done (nvidia-graphics-drivers-tesla: autopkgtest needs update for new version of linux)

2024-02-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Feb 2024 15:02:18 + with message-id and subject line Bug#1063362: fixed in nvidia-graphics-drivers-tesla 525.147.05-7~deb12u1 has caused the Debian Bug report #1063362, regarding nvidia-graphics-drivers-tesla: autopkgtest needs update for new version of linux to

Bug#1063363: marked as done (nvidia-graphics-drivers: autopkgtest needs update for new version of linux)

2024-02-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Feb 2024 15:02:18 + with message-id and subject line Bug#1063363: fixed in nvidia-graphics-drivers-tesla 525.147.05-7~deb12u1 has caused the Debian Bug report #1063363, regarding nvidia-graphics-drivers: autopkgtest needs update for new version of linux to be

Bug#1058890: sedutil

2024-02-15 Thread Dr . André Desgualdo Pereira
New try: I recompiled sedutil after booting linux-image-6.1.0-18-amd64 (git clone --branch s3-sleep-support https://github.com/badicsalex/sedutil.git). It made no difference, i.e., I still can't get the machine to fully wake up. (sedutil compiled at linux-image-6.1.0-18-amd64 still works fine

Bug#1063668: marked as done (linux-image-6.1.0-18-amd64: Nvidia 525.147.05-4 issues)

2024-02-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Feb 2024 15:02:18 + with message-id and subject line Bug#1062932: fixed in nvidia-graphics-drivers-tesla 525.147.05-7~deb12u1 has caused the Debian Bug report #1062932, regarding linux-image-6.1.0-18-amd64: Nvidia 525.147.05-4 issues to be marked as done. This

Bug#1063717: marked as done (cuda-drivers: Build of module nvidia.ko fails)

2024-02-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Feb 2024 15:02:18 + with message-id and subject line Bug#1062932: fixed in nvidia-graphics-drivers-tesla 525.147.05-7~deb12u1 has caused the Debian Bug report #1062932, regarding cuda-drivers: Build of module nvidia.ko fails to be marked as done. This means that

Bug#1063689: marked as done (linux-image-6.1.0-18-amd64 not usable with NVIDIA GPU)

2024-02-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Feb 2024 15:02:18 + with message-id and subject line Bug#1062932: fixed in nvidia-graphics-drivers-tesla 525.147.05-7~deb12u1 has caused the Debian Bug report #1062932, regarding linux-image-6.1.0-18-amd64 not usable with NVIDIA GPU to be marked as done. This

Bug#1063729: marked as done (Kernel panic after update from Debian 12.4 to 12.5 in command line and reboot)

2024-02-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Feb 2024 15:02:18 + with message-id and subject line Bug#1062932: fixed in nvidia-graphics-drivers-tesla 525.147.05-7~deb12u1 has caused the Debian Bug report #1062932, regarding Kernel panic after update from Debian 12.4 to 12.5 in command line and reboot to be

Bug#1063713: marked as done (linux-image-6.1.0-18-amd64: apt fails to install the kernel version, reports problem with building modules)

2024-02-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Feb 2024 15:02:18 + with message-id and subject line Bug#1062932: fixed in nvidia-graphics-drivers-tesla 525.147.05-7~deb12u1 has caused the Debian Bug report #1062932, regarding linux-image-6.1.0-18-amd64: apt fails to install the kernel version, reports problem

Bug#1063864: src:mediawiki2latex: fails to migrate to testing for too long: not installable on armel, mips64el and s390x

2024-02-15 Thread Dirk Hünniger
Hi Georges, I forgot to metion that that the line 52 (chromium-sandbox) should be change in the same manner as line 51. So it should look like: chromium-sandbox [!armel !mips64el !s390x], Yours Dirk On 15.02.24 16:03, Paul Gevers wrote: Hi, On 15-02-2024 15:56, Dirk Hünniger wrote: So

Bug#1064003: src:cross-toolchain-base: unsatisfied build dependency in testing: linux-source-6.5 (>= 6.5.8)

2024-02-15 Thread Paul Gevers
Source: cross-toolchain-base Version: 68 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be

Bug#1064004: src:cross-toolchain-base-ports: unsatisfied build dependency in testing: linux-source-6.5 (>= 6.5.8)

2024-02-15 Thread Paul Gevers
Source: cross-toolchain-base-ports Version: 64 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't

Bug#1064006: src:user-mode-linux: unsatisfied build dependency in testing: linux-source-6.5

2024-02-15 Thread Paul Gevers
Source: user-mode-linux Version: 6.5um1 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be

Bug#1063864: src:mediawiki2latex: fails to migrate to testing for too long: not installable on armel, mips64el and s390x

2024-02-15 Thread Paul Gevers
Hi, On 15-02-2024 08:40, Dirk Hünniger wrote: So it still wants to build on s390x armel and mips64el. Possibly its not possible to drop support for an architecture that once was supported. This is not the solution *I* had in mind. I was thinking about just adding an architecture qualified

Bug#1061229: numpydoc: Failing autopkgtest

2024-02-15 Thread Paul Gevers
Control: found -1 1.5.0-1 Hi, On Sat, 20 Jan 2024 18:47:50 -0500 =?UTF-8?Q?Jeremy_B=C3=ADcha?= wrote: numpydoc's autopkgtest is failing. Matthias added a path to Ubuntu to mark it as expected fail, but without further explanation. I am attaching a version of his patch. The version in

Processed: Re: numpydoc: Failing autopkgtest

2024-02-15 Thread Debian Bug Tracking System
Processing control commands: > found -1 1.5.0-1 Bug #1061229 [src:numpydoc] numpydoc: Failing autopkgtest Marked as found in versions numpydoc/1.5.0-1. -- 1061229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061229 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1057093: marked as done (php-imagick's autopkg tests fail)

2024-02-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Feb 2024 16:44:45 +0100 with message-id and subject line Re: php-imagick's autopkg tests fail has caused the Debian Bug report #1057093, regarding php-imagick's autopkg tests fail to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1063370: vulkan-tools: Fails to build from source.

2024-02-15 Thread Diederik de Haas
Control: tag -1 upstream fixed-upstream On Tue, 06 Feb 2024 13:45:14 -0800 Elizabeth Loss-Cutler-Hull wrote: > Package: vulkan-tools > Version: 1.3.268.0+dfsg1-1 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > > In file

Processed: Re: vulkan-tools: Fails to build from source.

2024-02-15 Thread Debian Bug Tracking System
Processing control commands: > tag -1 upstream fixed-upstream Bug #1063370 [vulkan-tools] vulkan-tools: Fails to build from source. Added tag(s) upstream and fixed-upstream. -- 1063370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063370 Debian Bug Tracking System Contact

Bug#1063864: src:mediawiki2latex: fails to migrate to testing for too long: not installable on armel, mips64el and s390x

2024-02-15 Thread Dirk Hünniger
Hi, If I have the choice, I would go for the second solution. So tell the system to build on all architectures and remove the runtime dependency to chromium on s390x armel and mips64el . I think mediawiki2latex can still be used in a practical way even if chromium is not available. For many

Bug#1063864: src:mediawiki2latex: fails to migrate to testing for too long: not installable on armel, mips64el and s390x

2024-02-15 Thread Paul Gevers
Hi, On 15-02-2024 15:56, Dirk Hünniger wrote: So could you Paul please post some information on how to do that. Maybe an example. See [1] after the first example. Replace [2] with chromium [!armel !mips64el !s390x], Paul [1] https://www.debian.org/doc/debian-policy/ch-relationships.html

Bug#1063864: src:mediawiki2latex: fails to migrate to testing for too long: not installable on armel, mips64el and s390x

2024-02-15 Thread Dirk Hünniger
Hi Paul, Georges thanks a lot Paul for explanation on the syntax. Georges, could you please follow the instruction given below. Yours Dirk On 15.02.24 16:03, Paul Gevers wrote: Hi, On 15-02-2024 15:56, Dirk Hünniger wrote: So could you Paul please post some information on how to do that.

Bug#1063671: marked as done (FTBFS: 32 bit arm fail with undefined reference to `raise_func_trampoline')

2024-02-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Feb 2024 16:06:55 +0100 with message-id and subject line Re: FTBFS: 32 bit arm fail with undefined reference to `raise_func_trampoline' has caused the Debian Bug report #1063671, regarding FTBFS: 32 bit arm fail with undefined reference to `raise_func_trampoline' to

Bug#1060804: marked as done (hickle: failing tests with h5py 3.10)

2024-02-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Feb 2024 15:49:12 + with message-id and subject line Bug#1060804: fixed in hickle 5.0.2-8 has caused the Debian Bug report #1060804, regarding hickle: failing tests with h5py 3.10 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1061605: marked as done (scipy: tests skipped during build and autopkgtest not in sync)

2024-02-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Feb 2024 17:50:35 + with message-id and subject line Bug#1061605: fixed in scipy 1.11.4-1 has caused the Debian Bug report #1061605, regarding scipy: tests skipped during build and autopkgtest not in sync to be marked as done. This means that you claim that the

Bug#1050161: marked as done (libtins build against ip_address.h fails)

2024-02-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Feb 2024 19:00:13 + with message-id and subject line Bug#1050161: fixed in libtins 4.5-1 has caused the Debian Bug report #1050161, regarding libtins build against ip_address.h fails to be marked as done. This means that you claim that the problem has been dealt

Bug#1064020: ulfius: FTBFS on armel, armhf, i386: 3 - framework (Failed)

2024-02-15 Thread Sebastian Ramacher
Source: ulfius Version: 2.7.15-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=ulfius=i386=2.7.15-1%2Bb1=1707543312=0 Running suite(s): Ulfius

Bug#1064022: editorconfig-core: FTBFS on i386: error: Could not create output directory /<>/obj-i686-linux-gnu/doc/man

2024-02-15 Thread Sebastian Ramacher
Source: editorconfig-core Version: 0.12.6-0.1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=editorconfig-core=i386=0.12.6-0.1%2Bb1=1704501538=0 [ 35%]

Bug#1064021: gss: FTBFS on armhf: FAIL: krb5context

2024-02-15 Thread Sebastian Ramacher
Source: gss Version: 1.0.4-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=gss=armhf=1.0.4-1%2Bb1=1707506511=0 PASS: threadsafety.sh

Bug#1064023: cddlib: FTBFS on armhf: ! Text line contains an invalid character.

2024-02-15 Thread Sebastian Ramacher
Source: cddlib Version: 094m-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=cddlib=armhf=094m-1%2Bb1=1704482099=0 [13] [14]) [15] [16]

Bug#1057574: marked as done (lmfit-py: FTBFS: mportError: The `scipy` install you are using seems to be broken, (extension modules cannot be imported), please try reinstalling.)

2024-02-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Feb 2024 20:37:29 + with message-id and subject line Bug#1057574: fixed in lmfit-py 1.2.2-3 has caused the Debian Bug report #1057574, regarding lmfit-py: FTBFS: mportError: The `scipy` install you are using seems to be broken, (extension modules cannot be

Bug#1064019: stdgpu: FTBFS on armel: Build killed with signal TERM after 150 minutes of inactivity

2024-02-15 Thread Sebastian Ramacher
Source: stdgpu Version: 1.3.0+git20220507.32e0517-5 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org

Bug#1058311: marked as done (lmfit-py: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)

2024-02-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Feb 2024 20:37:29 + with message-id and subject line Bug#1058311: fixed in lmfit-py 1.2.2-3 has caused the Debian Bug report #1058311, regarding lmfit-py: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code

Bug#1063707: marked as done (liblua5.4-0: C++ library missing all "lua*" function symbols)

2024-02-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Feb 2024 20:37:38 + with message-id and subject line Bug#1063707: fixed in lua5.4 5.4.6-3 has caused the Debian Bug report #1063707, regarding liblua5.4-0: C++ library missing all "lua*" function symbols to be marked as done. This means that you claim that the

Bug#1056419: marked as done (lmfit-py's autopkg tests fail with Python 3.12)

2024-02-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Feb 2024 20:37:29 + with message-id and subject line Bug#1056419: fixed in lmfit-py 1.2.2-3 has caused the Debian Bug report #1056419, regarding lmfit-py's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that the problem has been

Bug#1064024: juce: FTBFS on mips64el: Failed to build juceaide

2024-02-15 Thread Sebastian Ramacher
Source: juce Version: 7.0.5+ds-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=juce=mips64el=7.0.5%2Bds-1%2Bb1=1707563052=0 CMake Error at

Bug#1062259: libcomps: NMU diff for 64-bit time_t transition

2024-02-15 Thread Holger Levsen
On Wed, Feb 14, 2024 at 10:31:21AM -0800, Steve Langasek wrote: > Well, these packages will be garbage collected from experimental upon the > next upload of a package to unstable or experimental with a higher version; which might happen next month or next year or in 2027... > so this is a low

Bug#1044079: augur: FTBFS with pandas 2.0

2024-02-15 Thread Andreas Tille
Control: tags -1 pending Hi, thanks a lot for this hint. Am Wed, Feb 14, 2024 at 10:36:05AM +0100 schrieb s3v: > I don't know if renaming is a drop-in replacement Me neither but I simply trust that its passing its test suite. Kind regards Andreas. -- http://fam-tille.de

Processed: Re: Bug#1044079: augur: FTBFS with pandas 2.0

2024-02-15 Thread Debian Bug Tracking System
Processing control commands: > tags -1 pending Bug #1044079 [src:augur] augur: FTBFS with pandas 2.0 Added tag(s) pending. -- 1044079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1044079 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1044079: marked as done (augur: FTBFS with pandas 2.0)

2024-02-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Feb 2024 18:34:11 + with message-id and subject line Bug#1044079: fixed in augur 24.1.0-1 has caused the Debian Bug report #1044079, regarding augur: FTBFS with pandas 2.0 to be marked as done. This means that you claim that the problem has been dealt with. If this

Processed: severity

2024-02-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1062010 important Bug #1062010 {Done: John Goerzen } [src:dar] dar: NMU diff for 64-bit time_t transition Severity set to 'important' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance.

Processed: tagging 1063530, tagging 1063654, tagging 1064021, tagging 1064022, tagging 1064023, tagging 1064024 ...

2024-02-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1063530 + sid trixie Bug #1063530 [src:node-undici] node-undici: FTBFS with nodejs 18.19.0+dfsg-6~deb12u1 Added tag(s) sid and trixie. > tags 1063654 + sid trixie Bug #1063654 {Done: Debian FTP Masters } [ruby-graphql-errors]

Processed: reassign 1063744 to wnpp, reassign 1061966 to src:audit, fixed 1061966 in 1:3.1.2-2.1~exp3 ...

2024-02-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1063744 wnpp Bug #1063744 {Done: Colin Watson } [alexvsbus] RFP: alexvsbus -- a platform runner game Warning: Unknown package 'alexvsbus' Bug reassigned from package 'alexvsbus' to 'wnpp'. Ignoring request to alter found versions of bug

Processed: Re: Bug#1063329: libselinux1t64: breaks system in upgrade from unstable

2024-02-15 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 seli...@vger.kernel.org Bug #1063329 [libselinux1t64] libselinux1t64: breaks system in upgrade from unstable Set Bug forwarded-to-address to 'seli...@vger.kernel.org'. -- 1063329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063329 Debian Bug

Bug#1063329: libselinux1t64: breaks system in upgrade from unstable

2024-02-15 Thread Steve Langasek
Control: forwarded -1 seli...@vger.kernel.org Patch now forwarded upstream for review. https://lore.kernel.org/selinux/zc6tzkpsyzric...@homer.dodds.net/T/#t On Wed, Feb 14, 2024 at 11:25:26PM -0800, Steve Langasek wrote: > On Wed, Feb 07, 2024 at 09:06:58AM +0100, Helmut Grohne wrote: > > On

Bug#1063833: marked as done (mpich: ftbfs in sid due to newer slurm-wlm)

2024-02-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Feb 2024 21:28:02 + with message-id and subject line Bug#1063833: fixed in mpich 4.1.2-3 has caused the Debian Bug report #1063833, regarding mpich: ftbfs in sid due to newer slurm-wlm to be marked as done. This means that you claim that the problem has been dealt

Processed: Re: Bug#1063527: einsteinpy: test_plotting fails to converge with scipy 1.11

2024-02-15 Thread Debian Bug Tracking System
Processing control commands: > severity 1063527 serious Bug #1063527 [src:einsteinpy] einsteinpy: test_plotting fails to converge with scipy 1.11 Severity set to 'serious' from 'important' -- 1063527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063527 Debian Bug Tracking System Contact

Processed: Re: scikit-learn: tests fail with scipy 1.10

2024-02-15 Thread Debian Bug Tracking System
Processing control commands: > severity 1029701 serious Bug #1029701 [scikit-learn] scikit-learn: tests fail with scipy 1.10 Severity set to 'serious' from 'normal' -- 1029701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029701 Debian Bug Tracking System Contact ow...@bugs.debian.org

Processed: Re: cloud-initramfs-growroot: missing dependencies in initramfs

2024-02-15 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #1037914 [cloud-initramfs-growroot] cloud-initramfs-growroot: missing dependencies in initramfs Added tag(s) patch. -- 1037914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037914 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#1037914: cloud-initramfs-growroot: missing dependencies in initramfs

2024-02-15 Thread Tiago Ilieve
Control: tags -1 patch Hi, I've managed to reproduce the original report after adding 'debug' to the kernel command line and checking "/run/initramfs/initramfs.debug"[1]. A patch was sent to the "cloud-team/cloud-initramfs-tools" Salsa repository[2]. Regards, Tiago. [1]:

Bug#1063491: python3-jedi: unvendoring python3-typeshed breaks other packages

2024-02-15 Thread Daniel Vacek
Package: python3-jedi Followup-For: Bug #1063491 X-Debbugs-Cc: neel...@gmail.com The 0.19.1+ds1-1 still depends on python3-typeshed. Is that correct? --nX -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture:

Bug#1064034: FTBFS: Expired test certificate

2024-02-15 Thread Ángel
Package: ruby3.1 Version: 3.1.2-8 Severity: serious Tags: ftbfs A build of ruby3.1 fails on the test stage, since multiple test/net/http/test_https.rb tests return > "ERROR OpenSSL::SSL::SSLError: SSL_accept returned=1 errno=0 peeraddr=(null) state=error: sslv3 alert certificate expired\n"