Package: nfs-common
Version: 1:2.8.2-2~exp1
Severity: serious
Justification: file loss in upgrade scenario
Tags: patch
User: helm...@debian.org
Usertags: dep17p1
Hi Salvatore,
thanks for raising nfs-common ahead of upload and going via
experimental. Indeed, dumat flags
/usr/lib/systemd/system/nfs
Hi Reinhard,
On Tue, 2025-02-04 at 13:40 +0100, Reinhard Karcher wrote:
> Package: fp-compiler-3.2.2
> Version: 3.2.2+dfsg-43
> Severity: serious
> Justification: unnown
>
> Dear Maintainer,
>
> Upgrade to version 3.2.2+dfsg-43 from -40 produced compilation errors.
>
> I used the lazarus comman
Your message dated Wed, 05 Feb 2025 07:20:27 +
with message-id
and subject line Bug#1091024: fixed in dojo 1.17.3+dfsg1-1
has caused the Debian Bug report #1091024,
regarding rhino breaks dojo autopkgtest
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Hi Paul Gevers,
I just received the bug list notification; please allow me some time to look
over it. Meanwhile, could you please offer any more information, such as logs
or reproduction steps?
Thanks,
Gayathri.
Processing control commands:
> tag -1 pending
Bug #1091024 [src:dojo] rhino breaks dojo autopkgtest
Added tag(s) pending.
--
1091024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1091024
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #1091024 in dojo reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/js-team/dojo/-/commit/5ad46dd265931d6b308b1e91adba8434533ce8
Processing control commands:
> reassign -1 src:dojo 1.17.2+dfsg1-2.1
Bug #1091024 [src:rhino, src:dojo] rhino breaks dojo autopkgtest
Bug reassigned from package 'src:rhino, src:dojo' to 'src:dojo'.
No longer marked as found in versions dojo/1.17.2+dfsg1-2.1 and rhino/1.7.15-1.
Ignoring request to
user: debian-s...@lists.debian.org
usertags: s390x
thanks
Hi,
Maybe the s390x porters can help? I have the suspicion that there is
endianess involved in the autopkgtest failure of dnspython. dnspython is
key package.
Original message for context in full below.
Paul
On Thu, 2 Jan 2025 21:37
Processing control commands:
> severity -1 important
Bug #1093118 [src:ruby-redis] ruby-redis: causes autopkgtest regressions for
ruby-fakeredis
Severity set to 'important' from 'serious'
--
1093118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093118
Debian Bug Tracking System
Contact ow
Control: severity -1 important
Hi,
On Wed, 15 Jan 2025 11:27:43 +0100 Emilio Pozuelo Monfort
wrote:
Your package is causing autopkgtest regressions on ruby-fakeredis [1],
preventing it from migrating to testing. If the issue is in
ruby-fakeredis, then feel free to add the necessary informatio
Control: tags -1 moreinfo
Control: block -1 by 512231
Thanks
Hi,
since bug #512231 was fixed upstream pretty quickly after a Git issue
was opened I'm positive that the issue will be solved quickly in Debian.
Kind regards
Andreas.
--
https://fam-tille.de
Control: reassign -1 src:dojo 1.17.2+dfsg1-2.1
Control: affects -1 src:rhino
Hi,
On Wed, 22 Jan 2025 21:54:31 +0100 Adrien Nader wrote:
After some trial and error, I found out that if dojo is rebuilt, the
tests pass. I don't know what changed in rhino and the upstream
changelog for the new ver
Package: python3-meshplex
Followup-For: Bug #1094984
Control: tags -1 ftbfs
Control: block -1 by 1094985
The bug is effectively in meshio, meshplex is simply accessing a mesh
returned by meshio.
The problem is that the 2D cell type ("triangle") has no dtype
attached to the cell array. Evidently
Processing control commands:
> tags -1 ftbfs
Bug #1094984 [src:python-meshplex] python-meshplex: FTBFS with numpy 2.x
Ignoring request to alter tags of bug #1094984 to the same tags previously set
> block -1 by 1094985
Bug #1094984 [src:python-meshplex] python-meshplex: FTBFS with numpy 2.x
109498
Processing control commands:
> tags -1 moreinfo
Bug #1095129 [src:chewmail] chewmail: Should chewmail be removed from unstable?
Added tag(s) moreinfo.
> block -1 by 512231
Bug #1095129 [src:chewmail] chewmail: Should chewmail be removed from unstable?
1095129 was not blocked by any bugs.
1095129 w
Processing control commands:
> tags -1 pending
Bug #512231 [chewmail] If all mail is archived, it deletes the source mailbox
before being done writing the archive files
Added tag(s) pending.
> tags -1 fixed-upstream
Bug #512231 [chewmail] If all mail is archived, it deletes the source mailbox
be
Control: tags -1 pending
Control: tags -1 fixed-upstream
Thanks
Hi Eric,
thanks a lot for fixing this bug upstream[1].
I would volunteer to move the package to Salsa in the debian/ team and
upload the fix as team upload in case this might help you. Please let
me know what you think.
In case it
On Tuesday, February 4, 2025 2:41:57 PM MST Soren Stoutner wrote:
> > Regarding redmine, #1094049 was fixed in 5.1.3+ds-6, but now there's
> > #1095148 (related to the nokogiri update). So it would still be better
> > to remove redmine from testing for now (together with its reverse
> > dependencie
I'm not convinced this is critical, but it is some varient of RC.
Proposed solution is to rebase the hurd patch (gbp pq import; git rebase
-i; edit the commit) to modify the top level meson.build to include the
header test.
Then gbp pq export and commit the modified patches.
If someone gets to t
Hello Hilmar,
Statically linked luametatex solves the issue:
$ sudo apt-get install context
...
Running mktexlsr. This may take some time... done.
Running mtxrun --generate. This may take some time... done.
Running updmap-sys. This may take some time... done.
Running mktexlsr /var/lib/texmf ... do
Package: libpam0g
Version: 1.7.0-2
Severity: critical
Upstream removed the check for the sys/fsuid.h header, which means
HAVE_SYS_FSUID_H is never defined anymore. The debian hurd_no_setfsuid
patch now always uses the fallback code, and pam_modutil_regain_priv now
fails with a:
pam_modutil_rega
Processing control commands:
> affects -1 src:at-spi2-core
Bug #1095192 [src:rust-atk-sys-0.18] rust-atk-sys-0.18: autopkgtest failing
with at-spi2-core 2.55.2
Added indication that 1095192 affects src:at-spi2-core
--
1095192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1095192
Debian Bug
Source: rust-atk-sys-0.18
Version: 0.18.0-1
Severity: serious
X-Debbugs-CC: aferra...@debian.org
Control: affects -1 src:at-spi2-core
The autopkgtests for rust-atk-sys-0.18 are failing with at-spi2-core
2.55.2 currently in Unstable. rust-atk-sys-0.18 does not fail to build
from source though.
I r
Source: rust-glib-0.18
Version: 0.18.5-3
Severity: serious
Tags: ftbfs sid trixie
X-Debbugs-CC: aferra...@debian.org
rust-gio-0.18 fails to build with glib 2.83 which is now in Unstable.
It looks like you might only need to extend
Cargo.toml-add-missing-features.patch/
for v2_84
Build log excerp
Source: rust-gio-0.18
Version: 0.18.4-2
Severity: serious
Tags: ftbfs sid trixie
X-Debbugs-CC: aferra...@debian.org
rust-gio-0.18 fails to build with glib 2.83 which is now in Unstable.
It looks like you only need to extend
0001-Cargo.toml-add-missing-features.patch
for v2_84
Build log excerpt
=
Processing control commands:
> fixed -1 6.0.0-1
Bug #1088864 {Done: Stuart Prescott } [src:sasview] FTBFS:
ImportError: cannot import name 'trapz' from 'scipy.integrate'
The source 'sasview' and version '6.0.0-1' do not appear to match any binary
packages
Marked as fixed in versions sasview/6.0.
Control: fixed -1 6.0.0-1
The patch for 5.0.6-5 was backported from upstream 6.0.0; marking the
6.x branch that is now in unstable as also having this bug fixed.
--
Stuart Prescott http://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@deb
Processing commands for cont...@bugs.debian.org:
> fixed 1092699 7.0.5-1
Bug #1092699 [src:ruby-puppetlabs-spec-helper] ruby-puppetlabs-spec-helper:
FTBFS with ruby3.3: ERROR: Test "ruby3.3" failed: Failure/Error: require
'puppet-syntax/tasks/puppet-syntax'
Marked as fixed in versions ruby-puppe
Your message dated Tue, 4 Feb 2025 23:06:11 +
with message-id
and subject line Re: [DRE-maint] Bug#1092699: ruby-puppetlabs-spec-helper:
FTBFS with ruby3.3: ERROR: Test "ruby3.3" failed: Failure/Error: require
'puppet-syntax/tasks/puppet-syntax'
has caused the Debian Bug report #1092699,
reg
Your message dated Tue, 04 Feb 2025 22:54:04 +
with message-id
and subject line Bug#1094312: fixed in paje.app 1.98-2
has caused the Debian Bug report #1094312,
regarding paje.app: FTBFS with the GNUstep multiarch layout: hard codes path in
debian/rules
to be marked as done.
This means that
Hi,
Le 04/02/2025 à 16:58, Yavor Doganov a écrit :
Vincent Danjean wrote:
Do you think it would be better to move the git repo to the
gnustep-team group? Or do I put it in the plain debian group?
This entirely depends on you; you are the maintainer. You are welcome
to join the GNUstep tea
Your message dated Tue, 4 Feb 2025 22:32:17 +
with message-id
and subject line Re: [DRE-maint] Bug#1092698: ruby-puppet-syntax: FTBFS with
ruby3.3: ERROR: Test "ruby3.3" failed:
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1477:in `rescue in block in
activate_dependencies': Could not
Your message dated Tue, 04 Feb 2025 22:33:22 +
with message-id
and subject line Bug#1094556: fixed in yard 0.9.37-1
has caused the Debian Bug report #1094556,
regarding yard: FTBFS: ERROR: Test "ruby3.3" failed:cannot load such
file -- rack/server
to be marked as done.
This means tha
Processing commands for cont...@bugs.debian.org:
> fixed 1092698 4.1.1-1
Bug #1092698 [src:ruby-puppet-syntax] ruby-puppet-syntax: FTBFS with ruby3.3:
ERROR: Test "ruby3.3" failed:
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1477:in `rescue in block in
activate_dependencies': Could not
Your message dated Tue, 04 Feb 2025 22:05:10 +
with message-id
and subject line Bug#1085090: fixed in cura 5.0.0-5
has caused the Debian Bug report #1085090,
regarding "KeyError: material_name" crash on cura startup
to be marked as done.
This means that you claim that the problem has been dea
Your message dated Tue, 04 Feb 2025 22:05:10 +
with message-id
and subject line Bug#1076871: fixed in cura 5.0.0-5
has caused the Debian Bug report #1076871,
regarding cura: FTBFS: AttributeError: 'called_with' is not a valid assertion.
Use a spec for the mock if 'called_with' is meant to be
On Tuesday, February 4, 2025 6:18:04 AM MST Lucas Nussbaum wrote:
> On 31/01/25 at 07:05 -0300, Lucas Kanashiro wrote:
> > Could we also remove redmine from testing for now? We have this RC bug:
> > #1094049.
> >
> > It is right now blocked by the ruby-rack 3 transition, which should take
> > some
Your message dated Tue, 04 Feb 2025 21:35:07 +
with message-id
and subject line Bug#1092471: fixed in pyqso 1.1.0-8
has caused the Debian Bug report #1092471,
regarding pyqso: Type Error: takes 2 positional arguments but 3 were given
to be marked as done.
This means that you claim that the pr
Source: pcs
Version: 0.11.7-2
Severity: serious
Hi,
See https://ci.debian.net/packages/p/pcs/
It fails with:
test setup: test run
113s autopkgtest [13:34:07]: test setup: [---
113s Warning: Unable to read the known-hosts file: No such file or directory:
'/var/lib/pcsd/known
Control: tags -1 + confirmed
Control: retitle -1 python-mne: FTBFS: NumPy 2.0 AttributeError and other issues
The original error looks to have gone away when #1092354
affecting python3-vtk9 has been resolved:
> mne/commands/tests/test_commands.py::test_sys_info Fatal Python error:
> Segmentation
Processing control commands:
> tags -1 + confirmed
Bug #1093353 [src:python-mne] python-mne: FTBFS: Segmentation fault
Added tag(s) confirmed.
> retitle -1 python-mne: FTBFS: NumPy 2.0 AttributeError and other issues
Bug #1093353 [src:python-mne] python-mne: FTBFS: Segmentation fault
Changed Bug t
Source: pcs
Version: 0.11.7-2
Severity: serious
Hi
The first test failure is:
===
Failure: test_parse_empty(TestCfgKnownHosts)
/build/reproducible-path/pcs-0.11.7/pcsd/test/test_config.rb:687:in
`assert_empty_data'
/bui
Processing commands for cont...@bugs.debian.org:
> forcemerge 1093414 1094052
Bug #1093414 [src:postgresql-17] postgresql-17: FTBFS/autopkgtest failure with
tzdata 2025a due to minor changes of historical data
Bug #1094052 [src:postgresql-17] postgresql-17: FTBFS:
./build/./build/conftest.c:62:(
Processing commands for cont...@bugs.debian.org:
> tags 1093414 + fixed-upstream
Bug #1093414 [src:postgresql-17] postgresql-17: FTBFS/autopkgtest failure with
tzdata 2025a due to minor changes of historical data
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me i
Processing commands for cont...@bugs.debian.org:
> fixed 1078621 1.2.1-3
Bug #1078621 [src:golang-refraction-networking-utls]
golang-refraction-networking-utls: FTBFS in bookworm and trixie because of
expired certificate
The source 'golang-refraction-networking-utls' and version '1.2.1-3' do not
Your message dated Tue, 04 Feb 2025 19:20:15 +
with message-id
and subject line Bug#1092386: fixed in golang-refraction-networking-utls 1.2.1-3
has caused the Debian Bug report #1092386,
regarding golang-refraction-networking-utls: FTBFS: dh_auto_test: error: cd
obj-x86_64-linux-gnu && go tes
Processing control commands:
> tag -1 pending
Bug #1092386 [src:golang-refraction-networking-utls]
golang-refraction-networking-utls: FTBFS: dh_auto_test: error: cd
obj-x86_64-linux-gnu && go test -vet=off -v -p 8 -short
github.com/refraction-networking/utls github.com/refraction-networking/utl
Control: tag -1 pending
Hello,
Bug #1092386 in golang-refraction-networking-utls reported by you has been
fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/go-team/packages/golang-refrac
Processing control commands:
> severity -1 important
Bug #1094844 [src:gtk4] gtk4: 4.17.3 fails to build on armel & armhf:
memorytexture & scaling test failures
Severity set to 'important' from 'serious'
> unblock 1094845 by -1
Bug #1094845 [src:gtk4] gtk4: Upload 4.17/4.18 to Unstable
1094845 wa
Processing control commands:
> forwarded -1 https://bugs.launchpad.net/hplip/+bug/2097381
Bug #1085142 [printer-driver-hpcups] Produces PPD files with invalid hash
character in size names.
Set Bug forwarded-to-address to 'https://bugs.launchpad.net/hplip/+bug/2097381'.
--
1085142: https://bugs.
Control: forwarded -1 https://bugs.launchpad.net/hplip/+bug/2097381
On Tue, Jan 28, 2025 at 11:30:18PM +0100, Agustin Martin wrote:
> [resending to hplip 1085142, where it was supposed to go, instead of cups]
>
> On Tue, Oct 15, 2024 at 01:46:55PM +0200, Marcin Owsiany wrote:
> > I reported this
Control: severity -1 important
Control: unblock 1094845 by -1
Control: user debian-...@lists.debian.org
Control: usertags -1 armel
This build failure was a result of a packaging change where we now
install mesa-vulkan-drivers which enabled running additional tests.
Since there is no regression her
Control: tag -1 pending
Hello,
Bug #1094844 in gtk4 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/gnome-team/gtk4/-/commit/77aeaeef450357ba98601ca87dca9c0df17
Processing control commands:
> tag -1 pending
Bug #1094844 [src:gtk4] gtk4: 4.17.3 fails to build on armel & armhf:
memorytexture & scaling test failures
Added tag(s) pending.
--
1094844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1094844
Debian Bug Tracking System
Contact ow...@bugs.deb
Your message dated Tue, 04 Feb 2025 16:06:54 +
with message-id
and subject line Bug#1075227: fixed in linuxtv-dvb-apps 1.1.1+rev1500-2
has caused the Debian Bug report #1075227,
regarding linuxtv-dvb-apps: ftbfs with GCC-14
to be marked as done.
This means that you claim that the problem has
Vincent Danjean wrote:
> Do you think it would be better to move the git repo to the
> gnustep-team group? Or do I put it in the plain debian group?
This entirely depends on you; you are the maintainer. You are welcome
to join the GNUstep team even if you don't have interest in other
GNUstep pac
Hi,
On Tue, 2025-02-04 at 13:23 +, Peter B wrote:
> On 04/02/2025 12:40, Reinhard Karcher wrote:
> > Package: fp-compiler-3.2.2
> > Version: 3.2.2+dfsg-43
> > Severity: serious
> > Justification: unnown
> >
> > Dear Maintainer,
> >
> > Upgrade to version 3.2.2+dfsg-43 from -40 produced compi
Your message dated Tue, 04 Feb 2025 15:44:38 +
with message-id
and subject line Bug#1095004: fixed in lomiri-online-accounts-plugins 0.19-1
has caused the Debian Bug report #1095004,
regarding lomiri-online-accounts-plugins: Unsatisfiable Depends:
libaccount-plugin-generic-oauth
to be marked
On Tue, 04 Feb 2025 09:19:40 +, Debian FTP Masters wrote:
> Closes: 1095114
> Changes:
> libconfig-model-dpkg-perl (3.010) unstable; urgency=medium
> .
>* Remove failing test, which is no longer needed (Closes: 1095114)
Merci !
Cheers,
gregor
--
.''`. https://info.comodo.priv.at -
Your message dated Tue, 04 Feb 2025 15:06:10 +
with message-id
and subject line Bug#1093726: fixed in qviaggiatreno 2013.7.3-13
has caused the Debian Bug report #1093726,
regarding qviaggiatreno: Depends on QtWebKit
to be marked as done.
This means that you claim that the problem has been dea
Le 04/02/2025 à 15:32, Yavor Doganov a écrit :
Vincent Danjean wrote:
I will upload the package with a refresh (move package to salsa, ...)
I will include your patch, thanks
That's great, thanks!
I deleted the package from mentors.d.n and also closed the bug I filed
against the sponsorship-re
Processing control commands:
> tags -1 unreproducible
Bug #1094115 [src:check-postgres] check-postgres: FTBFS: make[1]: ***
[debian/rules:19: override_dh_auto_test] Error 1
Added tag(s) unreproducible.
--
1094115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1094115
Debian Bug Tracking Sys
Control: tags -1 unreproducible
Re: Lucas Nussbaum
> > # Failed test 'Action 'autovac_freeze' self-identifies correctly'
> > # at t/02_autovac_freeze.t line 40.
> > # 'uid=65534 topuid=10 euid=104 path='/tmp' at
> > /usr/lib/x86_64-linux-gnu/perl-base/File/Temp.pm line 686.
Vincent Danjean wrote:
> I will upload the package with a refresh (move package to salsa, ...)
> I will include your patch, thanks
That's great, thanks!
I deleted the package from mentors.d.n and also closed the bug I filed
against the sponsorship-requests pseudo package (#1095154) so consider
it
Processing control commands:
> tags -1 + patch
Bug #1094373 [src:pyferret] pyferret: FTBFS with numpy 2.x
Added tag(s) patch.
--
1094373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1094373
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + patch
The build system is looking at the old (numpy 1.x) location for the
include files. The attached patch asks numpy directly where its include
file is located and so is portable across versions and installation
methods. An alternative is to use `/usr/bin/numpy-config --c
Le 04/02/2025 à 14:26, Yavor Doganov a écrit :
Control: tags -1 + pending
I've prepared an NMU for paje.app (versioned as 1.98-1.3). The diff
is attached to this message.
It will be uploaded as soon as I find a sponsor.
I will upload the package with a refresh (move package to salsa, ...)
I w
Control: tags -1 + pending
I've prepared an NMU for paje.app (versioned as 1.98-1.3). The diff
is attached to this message.
It will be uploaded as soon as I find a sponsor.
diff -Nru paje.app-1.98/debian/changelog paje.app-1.98/debian/changelog
--- paje.app-1.98/debian/changelog 2024-08-30 09:36:
Processing control commands:
> tags -1 + pending
Bug #1094312 [src:paje.app] paje.app: FTBFS with the GNUstep multiarch layout:
hard codes path in debian/rules
Added tag(s) pending.
--
1094312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1094312
Debian Bug Tracking System
Contact ow...@bu
On 04/02/2025 12:40, Reinhard Karcher wrote:
Package: fp-compiler-3.2.2
Version: 3.2.2+dfsg-43
Severity: serious
Justification: unnown
Dear Maintainer,
Upgrade to version 3.2.2+dfsg-43 from -40 produced compilation errors.
I used the lazarus command compilation. The compilation aborted with
th
Your message dated Tue, 04 Feb 2025 13:20:32 +
with message-id
and subject line Bug#1094118: fixed in ruby-childprocess 4.1.0-3
has caused the Debian Bug report #1094118,
regarding ruby-childprocess: FTBFS: ERROR: Test "ruby3.3" failed: cannot load
such file -- rubygems/mock_gem_ui
to be ma
Control: block -1 by 1094881
On 02.02.25 Kip Warner (k...@thevertigo.com) wrote:
> On Sat, 2025-02-01 at 23:54 +0100, Hilmar Preuße wrote:
Hello,
> > My one was just a a try too. The luametatex package (as it is) is now
> > in the Debian archive for about 0,5 years and seems to be working. I
> >
Processing control commands:
> block -1 by 1094881
Bug #1094898 [context] context: mtxrun running fails
1094898 was not blocked by any bugs.
1094898 was not blocking any bugs.
Added blocking bug(s) of 1094898: 1094881
--
1094898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1094898
Debian B
Dear Maintainer,
After Build-Depending on dh-sequence-numpy, I get this error during build:
[...]
==
ERROR: test_nan (tests.fastcluster_test.test_nan)
--
Traceba
Your message dated Tue, 04 Feb 2025 13:04:46 +
with message-id
and subject line Bug#1094003: fixed in gworkspace 1.0.0-5
has caused the Debian Bug report #1094003,
regarding gworkspace: FTBFS with the GNUstep multiarch layout: configure error
to be marked as done.
This means that you claim th
Your message dated Tue, 04 Feb 2025 13:04:31 +
with message-id
and subject line Bug#1094001: fixed in gnustep-dl2 0.12.0+git20171224-4
has caused the Debian Bug report #1094001,
regarding gnustep-dl2: FTBFS with the GNUstep multiarch layout: /usr/bin/ld:
cannot find -lTrading: No such file or
Package: fp-compiler-3.2.2
Version: 3.2.2+dfsg-43
Severity: serious
Justification: unnown
Dear Maintainer,
Upgrade to version 3.2.2+dfsg-43 from -40 produced compilation errors.
I used the lazarus command compilation. The compilation aborted with
the following messassages:
Kompiliere Package fre
Your message dated Tue, 04 Feb 2025 12:13:25 +
with message-id
and subject line Bug#1077429: fixed in yad 0.40.0-1.1
has caused the Debian Bug report #1077429,
regarding yad: FTBFS: main.c:673:73: error: passing argument 2 of
‘gtk_style_context_add_provider’ from incompatible pointer type
[-
Your message dated Tue, 04 Feb 2025 12:13:25 +
with message-id
and subject line Bug#1075695: fixed in yad 0.40.0-1.1
has caused the Debian Bug report #1075695,
regarding yad: ftbfs with GCC-14
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Tue, 4 Feb 2025 12:59:59 +0100
with message-id
and subject line Re: Bug#1094049: redmine: FTBFS: make[1]: ***
[debian/rules:20: override_dh_auto_configure] Error 18
has caused the Debian Bug report #1094049,
regarding redmine: FTBFS: make[1]: *** [debian/rules:20:
override_dh_
Source: redmine
Version: 5.1.3+ds-6
Severity: serious
Hi,
> dh binary --with ruby
>dh_update_autotools_config
>dh_autoreconf
>debian/rules override_dh_auto_configure
> make[1]: Entering directory '/build/reproducible-path/redmine-5.1.3+ds'
> ./debian/check-locales
> bundle install --l
Your message dated Tue, 04 Feb 2025 11:06:30 +
with message-id
and subject line Bug#1095093: fixed in sasdata 0.9.0-3
has caused the Debian Bug report #1095093,
regarding sasdata: autopkgtests fail with numpy 2.x
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 04 Feb 2025 11:06:43 +
with message-id
and subject line Bug#1095094: fixed in sasmodels 1.0.8-2
has caused the Debian Bug report #1095094,
regarding sasmodels: autopkgtests fail with numpy 2.x
to be marked as done.
This means that you claim that the problem has been de
Package: jmeter
Version: 2.13-5
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: y...@debian.org
Hi,
I just install jmeter. It is unable to start:
$ jmeter
An error occurred: java.net.spi.InetAddressResolverProvider: Provider
org.xbill.DNS.spi.DnsjavaInetAddressResolverProv
Your message dated Tue, 4 Feb 2025 21:48:33 +1100
with message-id <7d8ab523-c8ab-4707-b265-c1dae75d8...@debian.org>
and subject line Re: Bug#1095095: sasview: autopkgtests fail with numpy 2.x
has caused the Debian Bug report #1095095,
regarding sasview: autopkgtests fail with numpy 2.x
to be marked
Processing commands for cont...@bugs.debian.org:
> block 1094637 with 1095055
Bug #1094637 [uwsgi-plugin-ruby] Rack plugin not compatible with Rack 3
1094637 was not blocked by any bugs.
1094637 was not blocking any bugs.
Added blocking bug(s) of 1094637: 1095055
> thanks
Stopping processing here.
Processing commands for cont...@bugs.debian.org:
> forwarded 1091947
> https://github.com/click-contrib/click-option-group/issues/65
Bug #1091947 [src:python-click-option-group] python-click-option-group: FTBFS:
FAILED tests/test_click_option_group.py::test_missing_group_decl_first_api
Set Bug f
Your message dated Tue, 04 Feb 2025 10:34:09 +
with message-id
and subject line Bug#1095019: fixed in dask 2024.12.1+dfsg-2
has caused the Debian Bug report #1095019,
regarding dask: autopkgtest failures with numpy 2.x
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 04 Feb 2025 10:20:40 +
with message-id
and subject line Bug#1094700: fixed in openmm 8.1.2+dfsg-3
has caused the Debian Bug report #1094700,
regarding openmm: FTBFS with numpy 2.x: error: cannot convert ‘PyObject*’ {aka
‘_object*’} to ‘const PyArrayObject*’ {aka ‘const
Processing control commands:
> tag -1 pending
Bug #1095019 [src:dask] dask: autopkgtest failures with numpy 2.x
Added tag(s) pending.
--
1095019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1095019
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #1095019 in dask reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/python-team/packages/dask/-/commit/28c21fd1a6cd52ebd6308f47e
Processing commands for cont...@bugs.debian.org:
> found 1094637 2.0.28+1+0.0.2
Bug #1094637 {Done: Jonas Smedegaard } [uwsgi-plugin-ruby] Rack
plugin not compatible with Rack 3
Did not alter found versions and reopened.
> thanks
Stopping processing here.
Please contact me if you need assistance
Your message dated Tue, 04 Feb 2025 09:50:10 +
with message-id
and subject line Bug#1092703: fixed in ruby-roo 2.10.0-2
has caused the Debian Bug report #1092703,
regarding ruby-roo: FTBFS with ruby3.3: ERROR: Test "ruby3.3" failed:
Failure/Error: expect(subject.instance_variables).to_no
Your message dated Tue, 04 Feb 2025 09:50:21 +
with message-id
and subject line Bug#1094051: fixed in thin-provisioning-tools 1.1.0-3
has caused the Debian Bug report #1094051,
regarding thin-provisioning-tools: FTBFS: dh_auto_test: error:
/usr/share/cargo/bin/cargo build returned exit code 1
Your message dated Tue, 04 Feb 2025 09:49:03 +
with message-id
and subject line Bug#1077766: fixed in certmonger 0.79.20-1
has caused the Debian Bug report #1077766,
regarding certmonger FTBFS with gcc 14
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing commands for cont...@bugs.debian.org:
> reassign 1094637 uwsgi-plugin-ruby 2.0.28+1+0.0.2
Bug #1094637 {Done: Jonas Smedegaard } [src:uwsgi-plugin-ruby]
Rack plugin not compatible with Rack 3
Bug reassigned from package 'src:uwsgi-plugin-ruby' to 'uwsgi-plugin-ruby'.
No longer marked a
On Sun, Feb 02, 2025 at 11:40:35PM +0500, Andrey Rakhmatullin wrote:
> https://ci.debian.net/packages/d/dask/testing/amd64/57321986/
>
> E AttributeError: module 'numpy' has no attribute 'product'
Apparently fixed upstream by removing the test along with the legacy
DataFrame implementation,
Your message dated Tue, 04 Feb 2025 09:19:40 +
with message-id
and subject line Bug#1095114: fixed in libconfig-model-dpkg-perl 3.010
has caused the Debian Bug report #1095114,
regarding libconfig-model-dpkg-perl: FTBFS: test failure with YAML::PP 0.38.1
to be marked as done.
This means that
Your message dated Tue, 04 Feb 2025 08:58:28 +
with message-id
and subject line Bug#1093357: fixed in seqan3 3.4.0~rc.3+ds-1
has caused the Debian Bug report #1093357,
regarding seqan3: FTBFS: The following tests FAILED: 8356 -
utility/views/enforce_random_access_test::enforce_random_access_t
Hi!
On Wed, Jan 29, 2025 at 10:45 PM Uwe Kleine-König wrote:
>
> Hello,
>
> I agree this looks like the kernel is at least involved in this problem.
> Is someone able to do a bisect to help the kernel team to pinpoint the
> issue?
>
> Or does someone has a reproducer that also works for someone w
1 - 100 of 102 matches
Mail list logo
