Bug#1065702: krb5-kdc: uninstallable due to hard-coded dependency on libverto-libev1 | libverto-libevent1,

2024-03-08 Thread Steve Langasek
Package: krb5-kdc Version: 1.20.1-5.1 Severity: serious User: debian-...@lists.debian.org Usertag: time-t Hi Sam, I've run into a problem with openldap not being bootstrappable for the time_t transition because it build-depends on krb5-kdc, and krb5-kdc is uninstallable on arm* because of a

Bug#1065634: marked as done (wv: /usr/share/doc wv is a dangling symlink)

2024-03-08 Thread Debian Bug Tracking System
Your message dated Sat, 09 Mar 2024 07:04:43 + with message-id and subject line Bug#1065634: fixed in wv 1.2.9-7 has caused the Debian Bug report #1065634, regarding wv: /usr/share/doc wv is a dangling symlink to be marked as done. This means that you claim that the problem has been dealt

Bug#1065634: wv: /usr/share/doc wv is a dangling symlink

2024-03-08 Thread Steve Langasek
On Thu, Mar 07, 2024 at 08:00:34PM +0100, Sven Joachim wrote: > On 2024-03-07 18:49 +0100, Sven Joachim wrote: > > > Package: wv > > Version: 1.2.9-6.1 > > Severity: serious > > X-Debbugs-Cc: Sven Joachim , Steve Langasek > > > > > > After renaming the libwv-1.2-4 library package to

Bug#1065633: marked as done (openldap: FTBFS on hppa - implicit declaration of function ‘kadm5_s_init_with_password_ctx’)

2024-03-08 Thread Debian Bug Tracking System
Your message dated Sat, 09 Mar 2024 06:49:25 + with message-id and subject line Bug#1065633: fixed in openldap 2.5.16+dfsg-1 has caused the Debian Bug report #1065633, regarding openldap: FTBFS on hppa - implicit declaration of function ‘kadm5_s_init_with_password_ctx’ to be marked as done.

Processed: Re: Fwd: E: unsupported command: poweroff.no-molly-guard

2024-03-08 Thread Debian Bug Tracking System
Processing control commands: > forcemerge 1059691 -1 Bug #1059691 [molly-guard] molly-guard: impossible reboot Bug #1059861 [molly-guard] molly-guard: Poweroff doesnt' work anymore Bug #1065696 [molly-guard] E: unsupported command: poweroff.no-molly-guard Severity set to 'important' from 'grave'

Bug#1065696: Fwd: E: unsupported command: poweroff.no-molly-guard

2024-03-08 Thread Helmut Grohne
Control: forcemerge 1059691 -1 On Fri, Mar 08, 2024 at 09:37:05PM -0800, Francois Marier wrote: > Hi Helmut, > > This looks like an unexpected edge case from the recent usr-merge changes: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065696 > > It sounds like a system using

Bug#1065700: mysql-8.0: ftbfs with 64-bit time_t on 32-bit archs

2024-03-08 Thread Steve Langasek
Package: mysql-8.0 Version: 8.0.36-2 Severity: serious Tags: patch Justification: ftbfs User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble ubuntu-patch Dear maintainers, With the switch to 64-bit time_t on 32-bit archs, mysql-8.0 now fails to build from source because of a test

Bug#1065696: Fwd: E: unsupported command: poweroff.no-molly-guard

2024-03-08 Thread Francois Marier
Hi Helmut, This looks like an unexpected edge case from the recent usr-merge changes: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065696 It sounds like a system using sysvinit, instead of systemd, which was recently upgraded using usrmerge. Francois -- https://fmarier.org/

Bug#1065633: openldap: FTBFS on hppa - implicit declaration of function 'kadm5_s_init_with_password_ctx'

2024-03-08 Thread Steve Langasek
On Fri, Mar 08, 2024 at 08:04:59PM -0800, Ryan Tandy wrote: > > This does fix the build failure. I was about to push such a change to the > > repo and do a maintainer upload, since I've never been removed from the > > uploaders field after all these years ;) Do you want me to do this, or > >

Bug#1065633: openldap: FTBFS on hppa - implicit declaration of function 'kadm5_s_init_with_password_ctx'

2024-03-08 Thread Ryan Tandy
On Fri, Mar 08, 2024 at 07:33:59PM -0800, Steve Langasek wrote: This bug is also reproducible on the armel and armhf release archs as a result of the time_t transition, so bumping this to serious. ACK. This does fix the build failure. I was about to push such a change to the repo and do a

Bug#1065696: E: unsupported command: poweroff.no-molly-guard

2024-03-08 Thread Thorsten Glaser
Package: molly-guard Version: 0.8.3 Severity: grave Justification: renders package unusable Severity chosen both because this makes the package unusable (I will have to remove it now) and because it breaks the whole system (boot). root@aranym:/var/cache/apt/archives # poweroff W: molly-guard:

Processed: Re: Bug#1065633: openldap: FTBFS on hppa - implicit declaration of function 'kadm5_s_init_with_password_ctx'

2024-03-08 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1065633 [src:openldap] openldap: FTBFS on hppa - implicit declaration of function ‘kadm5_s_init_with_password_ctx’ Severity set to 'serious' from 'important' -- 1065633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065633 Debian Bug

Processed: bug 1064764 is forwarded to https://github.com/jpvanhal/flask-basicauth/issues/32

2024-03-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1064764 https://github.com/jpvanhal/flask-basicauth/issues/32 Bug #1064764 [src:flask-basicauth] flask-basicauth: FTBFS: AssertionError: b'' != b'This view always requires authentication.' Set Bug forwarded-to-address to

Bug#1065373: marked as done (fix heimdal build with abi=time64)

2024-03-08 Thread Debian Bug Tracking System
Your message dated Sat, 09 Mar 2024 01:04:42 + with message-id and subject line Bug#1065373: fixed in heimdal 7.8.git20221117.28daf24+dfsg-5 has caused the Debian Bug report #1065373, regarding fix heimdal build with abi=time64 to be marked as done. This means that you claim that the problem

Bug#1055852: marked as done (frr: CVE-2023-38407 CVE-2023-41361 CVE-2023-46752 CVE-2023-46753 CVE-2023-47234 CVE-2023-47235)

2024-03-08 Thread Debian Bug Tracking System
Your message dated Sat, 09 Mar 2024 00:04:55 + with message-id and subject line Bug#1055852: fixed in frr 9.1-0.1 has caused the Debian Bug report #1055852, regarding frr: CVE-2023-38407 CVE-2023-41361 CVE-2023-46752 CVE-2023-46753 CVE-2023-47234 CVE-2023-47235 to be marked as done. This

Bug#1058132: marked as done (python-mitogen: FTBFS: ModuleNotFoundError: No module named 'imp')

2024-03-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Mar 2024 22:40:30 + with message-id and subject line Bug#1058132: fixed in python-mitogen 0.3.4-3 has caused the Debian Bug report #1058132, regarding python-mitogen: FTBFS: ModuleNotFoundError: No module named 'imp' to be marked as done. This means that you claim

Bug#1061755: marked as done (python-mitogen ftbfs with Python 3.12 as default)

2024-03-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Mar 2024 22:40:30 + with message-id and subject line Bug#1061755: fixed in python-mitogen 0.3.4-3 has caused the Debian Bug report #1061755, regarding python-mitogen ftbfs with Python 3.12 as default to be marked as done. This means that you claim that the problem

Bug#1065654: mesa ftbfs with time_t64

2024-03-08 Thread Fabio Pedretti
Il Ven 8 Mar 2024, 11:21 Matthias Klose ha scritto: > On 08.03.24 11:00, Fabio Pedretti wrote: > > Already fixed upstream, the patch will be included since 24.0.3 (will > > be released in 5 days): > > >

Processed: Bug#1058132 marked as pending in python-mitogen

2024-03-08 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1058132 [src:python-mitogen] python-mitogen: FTBFS: ModuleNotFoundError: No module named 'imp' Added tag(s) pending. -- 1058132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058132 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#1058132: marked as pending in python-mitogen

2024-03-08 Thread Stefano Rivera
Control: tag -1 pending Hello, Bug #1058132 in python-mitogen 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#1062491: marked as done (knot: NMU diff for 64-bit time_t transition)

2024-03-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Mar 2024 22:20:32 + with message-id and subject line Bug#1062491: fixed in knot 3.3.5-1.1 has caused the Debian Bug report #1062491, regarding knot: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been

Bug#1065489: marked as done (mongo-c-driver: FTBFS on armhf: format ‘%ld’ expects argument of type ‘long int’, but argument 4 has type ‘__suseconds64_t’ {aka ‘long long int’})

2024-03-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Mar 2024 19:50:47 + with message-id and subject line Bug#1065489: fixed in mongo-c-driver 1.26.1-1 has caused the Debian Bug report #1065489, regarding mongo-c-driver: FTBFS on armhf: format ‘%ld’ expects argument of type ‘long int’, but argument 4 has type

Bug#1063752: [Debichem-devel] Bug#1063752: custodian: Inappriate maintainer address

2024-03-08 Thread Michael Banck
Hi, On Tue, Feb 13, 2024 at 11:24:15AM +0100, Drew Parsons wrote: > Source: custodian > Followup-For: Bug #1063752 > X-Debbugs-Cc: Debichem Team > Control: reassign 1063752 lists.debian.org > Control: affects 1063752 src:custodian > > Scott Kitterman reported that lists.alioth.debian.org is

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

2024-03-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Mar 2024 18:06:11 + with message-id and subject line Bug#1064736: fixed in urlwatch 2.28-2 has caused the Debian Bug report #1064736, regarding urlwatch: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code

Bug#1065548: marked as done (octave-statistics: binary-any FTBFS)

2024-03-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Mar 2024 18:05:25 + with message-id and subject line Bug#1065548: fixed in octave-statistics 1.6.4-3 has caused the Debian Bug report #1065548, regarding octave-statistics: binary-any FTBFS to be marked as done. This means that you claim that the problem has been

Processed: Bug#1065548 marked as pending in octave-statistics

2024-03-08 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1065548 [src:octave-statistics] octave-statistics: binary-any FTBFS Added tag(s) pending. -- 1065548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065548 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1065548: marked as pending in octave-statistics

2024-03-08 Thread Rafael Laboissière
Control: tag -1 pending Hello, Bug #1065548 in octave-statistics 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#1065585: linux-headers-6.7.7-amd64: Depends: linux-compiler-gcc-13-x86 -> linux-image-6.7.7-amd64, gcc-13 => uninstallable on x32

2024-03-08 Thread Bastian Blank
Control: severity -1 minor > Because this is an x32 host. x32 is multi-arch kernel only architecture. Debian still don't have proper support for multi-arch for compilers. Just use amd64. Bastian -- Bones: "The man's DEAD, Jim!"

Processed: Re: Bug#1065585: linux-headers-6.7.7-amd64: Depends: linux-compiler-gcc-13-x86 -> linux-image-6.7.7-amd64, gcc-13 => uninstallable on x32

2024-03-08 Thread Debian Bug Tracking System
Processing control commands: > severity -1 minor Bug #1065585 [src:linux] linux-headers-6.7.7-amd64: Depends: linux-compiler-gcc-13-x86 -> linux-image-6.7.7-amd64, gcc-13 => uninstallable on x32 Severity set to 'minor' from 'grave' -- 1065585:

Bug#1065477: marked as done (owncloud-client: Uploads to unstable must have a higher version than present in unstable.)

2024-03-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Mar 2024 18:21:20 +0100 with message-id <87bk7o63k2@daath.cgg.com> and subject line Re: [Pkg-owncloud-maintainers] Bug#1065477: owncloud-client: Uploads to unstable must have a higher version than present in unstable. has caused the Debian Bug report #1065477,

Bug#1060318: This is a regression: it used to pass with PoCL3.1

2024-03-08 Thread Jerome Kieffer
Platform Name Portable Computing Language Platform Vendor The pocl project Platform VersionOpenCL 3.0 PoCL 3.1+debian Linux, None+Asserts, RELOC, SPIR, LLVM 15.0.6, SLEEF, DISTRO, POCL_DEBUG

Processed: severity of 1061102 is important

2024-03-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1061102 important Bug #1061102 [librust-tikv-jemalloc-sys-dev] librust-tikv-jemalloc-sys-dev: fails to compile without xsltproc Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need

Bug#1065666: Compiz 0.8.18 appears to be broken in testing

2024-03-08 Thread James Bielefeldt
Not sure if this helps, but I keep package lists of each build. Here is a diff of 2/24 build (works) vs 3/24 (broken). https://spins.tuxfamily.org/package-list-diff.txt I dont know if any changes would break compiz, but at least its more info. Jim On 3/6/24 11:25, Steve Langasek wrote: On

Bug#1065666: Compiz 0.8.18 appears to be broken in testing

2024-03-08 Thread James Bielefeldt
Hi This address is listed as a maintainer on the Compiz package search page. 0.8.18 black screens on boot after a recent update when building a iso with livebuild. I have been building the xfce-Compiz iso for about 4 months without issue. The xfce (testing amd64) iso is built without errors, but

Bug#1065666: Compiz 0.8.18 appears to be broken in testing

2024-03-08 Thread Colomban Wendling
Hello James, Unfortunately I can't test this for the moment, but: Le 06/03/2024 à 15:03, James Bielefeldt a écrit : This address is listed as a maintainer on the Compiz package search page. 0.8.18 black screens on boot after a recent update when building a iso with livebuild. I have been

Bug#1065666: Compiz 0.8.18 appears to be broken in testing

2024-03-08 Thread Colomban Wendling
Le 06/03/2024 à 16:59, James Bielefeldt a écrit : I am using testing. I create Debian spins that are rolling release based on testing. it's the same package in standard testing and unstable to my knowledge. Unstable recently got 2:0.8.18-5.1 -- yet as Steve said, it should not affect

Bug#1065666: Compiz 0.8.18 appears to be broken in testing

2024-03-08 Thread Colomban Wendling
Le 06/03/2024 à 17:31, Steve Langasek a écrit : On Wed, Mar 06, 2024 at 03:46:41PM +0100, Colomban Wendling wrote: Anyway, I'm CCing Steve (who did the unstable NMU) and Samuel in case they have extra clues. The only change in the NMU was to rename the libdecoration0 package to

Bug#1065666: Compiz 0.8.18 appears to be broken in testing

2024-03-08 Thread Steve Langasek
On Wed, Mar 06, 2024 at 06:19:48PM +0100, Colomban Wendling wrote: > Le 06/03/2024 à 17:31, Steve Langasek a écrit : > > On Wed, Mar 06, 2024 at 03:46:41PM +0100, Colomban Wendling wrote: > > > Anyway, I'm CCing Steve (who did the unstable NMU) and Samuel in case they > > > have extra clues. > >

Bug#1065666: Compiz 0.8.18 appears to be broken in testing

2024-03-08 Thread Steve Langasek
On Wed, Mar 06, 2024 at 03:46:41PM +0100, Colomban Wendling wrote: > Anyway, I'm CCing Steve (who did the unstable NMU) and Samuel in case they > have extra clues. The only change in the NMU was to rename the libdecoration0 package to libdecoration0t64 for the 64-bit time_t transition. Unless

Processed: fix ftbfs bug metadata

2024-03-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # reassign from binary to source > reassign 1065214 src:iproute2 Bug #1065214 [iproute2] iproute2: recent libc6-dev change causes the RPC support to be dropped Bug reassigned from package 'iproute2' to 'src:iproute2'. No longer marked as found

Bug#1065666: mesa: Upgrading to mesa from testing breaks compiz

2024-03-08 Thread Samuel Thibault
Source: mesa Version: 23.3.5-1 Severity: serious Tags: a11y Justification: breaks compiz Hello, When upgrading mesa to the version from testing, compiz does not start any more. I tried both upgrading only mesa (and deps), as well as mesa and the rest of the system, with the same result. compiz

Bug#1053195: marked as done (Please remove librados-dev build-depends on all 32 bits arch)

2024-03-08 Thread Debian Bug Tracking System
Your message dated Fri, 8 Mar 2024 15:58:36 +0100 with message-id <387c5292-0471-4d8b-9de8-b4fbb8aed...@uni-mainz.de> and subject line Re: Bug#1053195: Please remove librados-dev build-depends on all 32 bits arch has caused the Debian Bug report #1053195, regarding Please remove librados-dev

Bug#1060318: silx: autopkgtest failure with Python 3.12

2024-03-08 Thread PICCA Frederic-Emmanuel
In order to reproduce the bug, install python3-silx 2.0.0+dfsg-1 python3-pytest-xvfb pocl-opencl-icd then $ pytest --pyargs silx.image.test.test_medianfilter -v === test session starts

Bug#1065183: marked as done (python-fsquota: missing build-dep on libtirpc-dev)

2024-03-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Mar 2024 13:59:15 + with message-id and subject line Bug#1065183: fixed in python-fsquota 0.1.0+dfsg1-5 has caused the Debian Bug report #1065183, regarding python-fsquota: missing build-dep on libtirpc-dev to be marked as done. This means that you claim that the

Processed: Bug#1065183 marked as pending in python-fsquota

2024-03-08 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1065183 [src:python-fsquota] python-fsquota: missing build-dep on libtirpc-dev Added tag(s) pending. -- 1065183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1065183: marked as pending in python-fsquota

2024-03-08 Thread Philipp Huebner
Control: tag -1 pending Hello, Bug #1065183 in python-fsquota 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#1065464: marked as done (tracker: 3.7 failing autopkgtest)

2024-03-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Mar 2024 13:27:58 + with message-id and subject line Bug#1065464: fixed in tracker 3.7~rc-3 has caused the Debian Bug report #1065464, regarding tracker: 3.7 failing autopkgtest to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1061464: marked as done (tracker FTBFS with nocheck profile: ../meson.build:99:26: ERROR: python3 is missing modules: gi)

2024-03-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Mar 2024 13:27:58 + with message-id and subject line Bug#1061464: fixed in tracker 3.7~rc-3 has caused the Debian Bug report #1061464, regarding tracker FTBFS with nocheck profile: ../meson.build:99:26: ERROR: python3 is missing modules: gi to be marked as done.

Bug#1035903: marked as done (tracker: datetime build tests failing on 32-bit)

2024-03-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Mar 2024 13:27:58 + with message-id and subject line Bug#1035903: fixed in tracker 3.7~rc-3 has caused the Debian Bug report #1035903, regarding tracker: datetime build tests failing on 32-bit to be marked as done. This means that you claim that the problem has

Bug#1065460: uwsgi: the package fails to build from source due to missing 'plugins/rack_ruby32'

2024-03-08 Thread Alexandre Rossi
Hi, > The package fails to build in sid chroot with the following error: > > -- > *** uWSGI building and linking plugin plugins/rack_ruby32 *** > Error: unable to find directory 'plugins/rack_ruby32' > make: *** [debian/rules:429: debian/stamp-uwsgi-plugin-rack-ruby3.2] Error 1 >

Processed: Bug#1061464 marked as pending in tracker

2024-03-08 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1061464 [src:tracker] tracker FTBFS with nocheck profile: ../meson.build:99:26: ERROR: python3 is missing modules: gi Added tag(s) pending. -- 1061464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061464 Debian Bug Tracking System

Bug#1061464: marked as pending in tracker

2024-03-08 Thread Jeremy Bicha
Control: tag -1 pending Hello, Bug #1061464 in tracker 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#1056429: marked as done (mystic's autopkg tests fail with Python 3.12)

2024-03-08 Thread Debian Bug Tracking System
Your message dated Fri, 8 Mar 2024 11:57:44 + with message-id and subject line Re: Bug#1056429: mystic's autopkg tests fail with Python 3.12 has caused the Debian Bug report #1056429, regarding mystic's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that

Bug#1065662: FTBFS: error: aborting due to unexpected upstream changes

2024-03-08 Thread Jérémy Lal
Source: ipywidgets Version: 8.1.1-4 Severity: serious Tags: ftbfs Justification: fails to build from source Rebuilding https://deb.debian.org/debian/pool/main/i/ipywidgets/ipywidgets_8.1.1-4.dsc in a clean sid chroot fails with error: aborting due to unexpected upstream changes -- System

Bug#1064697: flask-babelex: FTBFS: ImportError: cannot import name '_request_ctx_stack' from 'flask' (/usr/lib/python3/dist-packages/flask/__init__.py)

2024-03-08 Thread Colin Watson
On Sun, Feb 25, 2024 at 08:37:09PM +0100, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. [...] > > == > > ERROR: flask_babelex (unittest.loader._FailedTest.flask_babelex)

Bug#1064773: marked as done (chemicaltagger: FTBFS: [ERROR] Plugin org.antlr:antlr4-maven-plugin:4.7.2 or one of its dependencies could not be resolved: Cannot access central (https://repo.maven.apach

2024-03-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Mar 2024 11:04:11 + with message-id and subject line Bug#1064773: fixed in chemicaltagger 1.6.2-3 has caused the Debian Bug report #1064773, regarding chemicaltagger: FTBFS: [ERROR] Plugin org.antlr:antlr4-maven-plugin:4.7.2 or one of its dependencies could not be

Bug#1042679: quark-sphinx-theme: FTBFS with Sphinx 7.1, docutils 0.20: AssertionError: no elements

2024-03-08 Thread Colin Watson
On Sun, Jul 30, 2023 at 08:29:35PM +0200, Lucas Nussbaum wrote: > quark-sphinx-theme fails to build with Sphinx 7.1 and docutils 0.20, both of > which > are currently available in experimental. A new upstream version 0.6.0 has been sitting in git since 2022, so I wondered whether it fixed this.

Bug#1035516: php-smbclient broke with samba 4.17.5

2024-03-08 Thread Daniel Scharon
Dear maintainers, On Thu, 04 May 2023 16:23:10 +0200 Alan Krempler wrote: > Package: php-smbclient > Version: 1.0.6-8 > Severity: grave > Justification: renders package unusable > > php-smbclient does not work with samba versions 4.17.5 and above: >

Bug#1065654: mesa ftbfs with time_t64

2024-03-08 Thread Matthias Klose
On 08.03.24 11:00, Fabio Pedretti wrote: Already fixed upstream, the patch will be included since 24.0.3 (will be released in 5 days): https://cgit.freedesktop.org/mesa/mesa/commit/?h=staging/24.0=8ea039019761ecc25d49f075aef50de6e81db854 no, that commit is only fixing one occurrence. Il

Bug#1065654: mesa ftbfs with time_t64

2024-03-08 Thread Fabio Pedretti
Already fixed upstream, the patch will be included since 24.0.3 (will be released in 5 days): https://cgit.freedesktop.org/mesa/mesa/commit/?h=staging/24.0=8ea039019761ecc25d49f075aef50de6e81db854 Il giorno ven 8 mar 2024 alle ore 10:27 Matthias Klose ha scritto: > > Package: src:mesa >

Bug#1065654: mesa ftbfs with time_t64

2024-03-08 Thread Matthias Klose
Package: src:mesa Version: 24.0.2-1 Severity: serious Tags: sid trixie patch mesa ftbfs with time_t64, patch attached. I didn't check if the _TIMET_BITS are used in the affected files. There's also a bug in the profile support. WINE cannot be built without LLVM, and therefore should be

Bug#1065501: marked as done (qgis FTBFS: FAILED: src/crssync/CMakeFiles/synccrsdb)

2024-03-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Mar 2024 08:51:12 + with message-id and subject line Bug#1065501: fixed in qgis 3.34.4+dfsg-4 has caused the Debian Bug report #1065501, regarding qgis FTBFS: FAILED: src/crssync/CMakeFiles/synccrsdb to be marked as done. This means that you claim that the problem

Bug#1065373: fix heimdal build with abi=time64

2024-03-08 Thread Steve Langasek
Control: tags -1 -experimental Since heimdal failing to build from source has a significant impact on rebootstrapping the archive on 32-bit archs, I am going ahead and uploading a 0-day NMU for this issue with the patch provided by Matthias. Thanks, -- Steve Langasek Give me a

Processed: Re: fix heimdal build with abi=time64

2024-03-08 Thread Debian Bug Tracking System
Processing control commands: > tags -1 -experimental Bug #1065373 [src:heimdal] fix heimdal build with abi=time64 Removed tag(s) experimental. -- 1065373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065373 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems