Hello,
The upstream has said they are not considering fixing this a priority,
thus unless someone from Debian side is willing to work on a patch,
prody will not make it to trixie.
Andrius
Hi again,
this is another ping about a decision what to do with psicode. Please
simply state whether it is worth fixing #1075399 of the current version
in Debian and I might spent some time into it. I simply want to know
whether it is worth keeping or whether its more sensible to remove it
and m
Processing control commands:
> tags 1070904 + patch
Bug #1070904 [src:bitlbee] bitlbee: Please use pkg-config instead of
libgcrypt-config to locate libgcrypt
Ignoring request to alter tags of bug #1070904 to the same tags previously set
> tags 1070904 + pending
Bug #1070904 [src:bitlbee] bitlbee:
Control: tags 1070904 + patch
Control: tags 1070904 + pending
Dear maintainer,
I've prepared an NMU for bitlbee (versioned as 3.6-1.5) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
Jochen
diff -Nru bitlbee-3.6/debian/changelog bitlbee-3.6/debi
This is a weird error. But pymatgen is successfully building now.
I guess the problem was in another package, and has been fixed.
When the new build passes debci and is ready to migrate to testing,
I'll close these bugs, unless there is any other news
to keep them open.
Drew
Your message dated Fri, 14 Feb 2025 08:24:29 +0100
with message-id
and subject line Re: Bug#1092982: FTBFS: sphinx-build segfaults
has caused the Debian Bug report #1092982,
regarding FTBFS: sphinx-build segfaults
to be marked as done.
This means that you claim that the problem has been dealt wit
Your message dated Fri, 14 Feb 2025 06:51:04 +
with message-id
and subject line Bug#1093845: fixed in glslang 15.1.0-2
has caused the Debian Bug report #1093845,
regarding glslang-dev: autopkgtest regression in unstable: libraries from
spirv.pc no longer sufficient to link a test program
to b
Philippe SWARTVAGHER kirjoitti 14.2.2025 klo 0.27:
Hello,
This bug prevents shaderc to migrate to testing, so I had a look.
It turns out upstream merged the content of the spirv library into the
glslang one, see
https://github.com/KhronosGroup/glslang/
commit/4f01996c9df0e2edb8823a8260066467c8
Your message dated Fri, 14 Feb 2025 05:22:07 +
with message-id
and subject line Bug#1094894: fixed in sight 24.1.0-2
has caused the Debian Bug report #1094894,
regarding sight: FTBFS with ITK 5.4
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Fri, 14 Feb 2025 03:50:29 +
with message-id
and subject line Bug#1089100: fixed in rust-yaxpeax-x86 2.0.0-1
has caused the Debian Bug report #1089100,
regarding rust-yaxpeax-x86: FTBFS, unsatisfiable dependency on
rust-yaxpeax-arch 0.2
to be marked as done.
This means that
Processing commands for cont...@bugs.debian.org:
> notfixed 1095902 debian/2.13.14-1
Bug #1095902 [lttng-modules-dkms] lttng-modules-dkms: module fails to build for
Linux 5.10.0-33-amd64: error: implicit declaration of function 'fcheck'
The source debian and version 2.13.14-1 do not appear to mat
Followup-For: Bug #1095902
Control: tag -1 patch
Control: fixed -1 debian/2.13.14-1
Attached are patches for bullseye and bookworm that adjust the
preprocessor condition in the same way as it was fixed upstream in
2.13.14.
Tested in bullseye/bookworm chroots with the bullseye kernel installed.
Processing control commands:
> tag -1 patch
Bug #1095902 [lttng-modules-dkms] lttng-modules-dkms: module fails to build for
Linux 5.10.0-33-amd64: error: implicit declaration of function 'fcheck'
Added tag(s) patch.
> fixed -1 debian/2.13.14-1
Bug #1095902 [lttng-modules-dkms] lttng-modules-dkms:
On Thu, Jun 13, 2024 at 03:26:52PM +0200, Jérémy Lal wrote:
> Package: lua-vips
> Version: 1.1.11-3
> Severity: serious
>...
You as maintainer can consider this serious enough for keeping the
package out of trixie, but in general this is not a release critical
bug since no old binaries exist on t
Your message dated Fri, 14 Feb 2025 01:34:13 +
with message-id
and subject line Bug#1092530: fixed in daemontools 1:0.76-13.1
has caused the Debian Bug report #1092530,
regarding daemontools: FTBFS: make[2]: *** [Makefile:168: hasshsgr.h] Error 1
to be marked as done.
This means that you clai
On Fri, 14 Feb 2025, Guillem Jover wrote:
>> >This bug does not count as RC just because Debian upload bureaucracy
>> >hasn't been performed yet.
>>
>> If packagers cannot rely on Policy to give correct information, what
>> *can* they rely on?
>
>This is not how Debian Policy has ever worked. By t
On Fri, 14 Feb 2025, Guillem Jover wrote:
>As was discovered in bug #1095746, this package misbuilds when calling
>for example «fakeroot debian/rules binary-arch» w/o first calling
>«debian/rules build-arch», which is a policy violation:
Yes. I noticed yesterday (or so… memory is a bit fuzzy) and
On Fri, 2025-02-14 at 01:02:26 +0100, Thorsten Glaser wrote:
> On Fri, 14 Feb 2025, Sean Whitton wrote:
> >Policy has to go through binary-NEW in order to be released. So there
>
> Technicalities.
Not really, no.
> >This bug does not count as RC just because Debian upload bureaucracy
> >hasn't
Source: openjdk-8
Source-Version: 8u442-ga-2
Severity: serious
Hi!
As was discovered in bug #1095746, this package misbuilds when calling
for example «fakeroot debian/rules binary-arch» w/o first calling
«debian/rules build-arch», which is a policy violation:
,---
"binary" (required), "bin
On Fri, 14 Feb 2025, Sean Whitton wrote:
>Policy has to go through binary-NEW in order to be released. So there
Technicalities.
>isn't a quick fix here.
Not looking for one. dpkg should revert this until then.
>This bug does not count as RC just because Debian upload bureaucracy
>hasn't been
Processing commands for cont...@bugs.debian.org:
> close 1091145
Bug #1091145 [src:camitk] camitk: FTBFS on arm64: build-dependency not
installable: libinsighttoolkit5-dev
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1091145: https://bugs.de
Package: homer-api
Version: 5.0.6+dfsg2-3.3
Severity: serious
kamailio (6.0.0-1) unstable; urgency=medium
...
* remove geoip modules
...
-- Victor Seva Tue, 11 Feb 2025 14:55:15 +0100
Processing commands for cont...@bugs.debian.org:
> close 1069199
Bug #1069199 [src:kamailio] kamailio: FTBFS:
/usr/include/absl/base/policy_checks.h:79:2: error: #error "C++ versions less
than C++14 are not supported."
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if y
Your message dated Thu, 13 Feb 2025 23:50:38 +
with message-id
and subject line Bug#1095215: fixed in silx 2.2.0+dfsg-1
has caused the Debian Bug report #1095215,
regarding python3-silx: uninstallable with the current version of python3-numpy
to be marked as done.
This means that you claim th
Hello,
On Thu 13 Feb 2025 at 11:57pm +01, Thorsten Glaser wrote:
> severity 1095791 serious
> thanks
>
> On Thu, 13 Feb 2025, Guillem Jover wrote:
>
>>> >From what I can tell from other mails, I believe the package in
>>> question is openjdk-8 (unstable only); see bug #1095746.
>>
>>Ah, thanks fo
Your message dated Thu, 13 Feb 2025 23:05:51 +
with message-id
and subject line Bug#1074978: fixed in gaviotatb 0.4-2.2
has caused the Debian Bug report #1074978,
regarding gaviotatb: ftbfs with GCC-14
to be marked as done.
This means that you claim that the problem has been dealt with.
If th
Your message dated Thu, 13 Feb 2025 23:05:34 +
with message-id
and subject line Bug#1092479: fixed in botch 0.24-6
has caused the Debian Bug report #1092479,
regarding botch: FTBFS with OCaml 5.3.0 (make[2]: *** [Makefile:278: test-man]
Error 1)
to be marked as done.
This means that you clai
Processing commands for cont...@bugs.debian.org:
> notfound 1093745 pinfo/0.6.13-1.3
Bug #1093745 {Done: Hilko Bengen } [pinfo,python3-plaso]
pinfo and python3-plaso have an undeclared file conflict on /usr/bin/pinfo
No longer marked as found in versions pinfo/0.6.13-1.3.
> --
Stopping processing
Your message dated Thu, 13 Feb 2025 23:05:34 +
with message-id
and subject line Bug#1092479: fixed in botch 0.24-6
has caused the Debian Bug report #1092479,
regarding botch: FTBFS in sid
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Processing commands for cont...@bugs.debian.org:
> severity 1095791 serious
Bug #1095791 [src:dpkg] dpkg: incompatible and Policy-violating R³ default
change breaks packages’ builds
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistanc
Source: emscripten
Followup-For: Bug #1081967
Hi,
I have binaryen 120, emscripten 3.1.69 built and ready to be
uploaded to unstable.
wabt, node-webfont, node-inwasm can be rebuilt with them.
I'm planing to move emscripten to pkg-javascript-devel team.
-- System Information:
Debian Release: tri
Hello,
This bug prevents shaderc to migrate to testing, so I had a look.
It turns out upstream merged the content of the spirv library into the
glslang one, see
https://github.com/KhronosGroup/glslang/commit/4f01996c9df0e2edb8823a8260066467c828a341
and the changelog entry:
https://github.com/Khr
I am uploading a NMU to fix this.
Please find the debdiff attached.
gaviotatb_0.4-2.2.debdiff
Description: Binary data
Your message dated Thu, 13 Feb 2025 22:12:08 +
with message-id
and subject line Bug#1091607: fixed in ruby-image-processing 1.14.0-1
has caused the Debian Bug report #1091607,
regarding ruby-image-processing: FTBFS: ERROR: Test "ruby3.1" failed:
Vips::Error: addalpha: no property named `?'
Good day,
Salvatore Bonaccorso, on 2025-02-12:
> Thanks a lot for your work, and for providing this status update. Then
> I suggest that we do not not ignore the remaining CVEs and you can
> address this equally trough the point release.
Sounds good, I opened #1095072 to discuss the integration.
On Thu, Feb 13, 2025 at 05:26:36PM +0100, Agustin Martin wrote:
> On Wed, Feb 12, 2025 at 09:26:37PM +0100, Marcin Owsiany wrote:
> >
> > Attached is my original (-a) PPD file and the modified one (-b, which works
> > for me). Turns out the changes are the same as in the diff attached earlied
> >
Your message dated Thu, 13 Feb 2025 20:36:20 +0100
with message-id <173947538030.2664089.8706501654255655...@cairon.jones.dk>
and subject line Re: Bug#1095907: ell: fails to build because of test failures
has caused the Debian Bug report #1095907,
regarding ell: fails to build because of test failu
Your message dated Thu, 13 Feb 2025 19:19:45 +
with message-id
and subject line Bug#1067913: fixed in linssid 3.6-9
has caused the Debian Bug report #1067913,
regarding FTBFS: error: cannot convert ‘long int*’ to ‘const time_t*’ {aka
‘const long long int*’}
to be marked as done.
This means t
Processing commands for cont...@bugs.debian.org:
> fixed 1095342 ldc/1:1.40.0-5
Bug #1095342 [src:dub] dub: FTBFS: Error: Error executing /usr/bin/ldc2: Aborted
Marked as fixed in versions ldc/1:1.40.0-5.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1095342: ht
Your message dated Thu, 13 Feb 2025 18:38:57 +
with message-id
and subject line Bug#1084319: fixed in plover 4.0.0~rc5-0.1
has caused the Debian Bug report #1084319,
regarding plover: FTBFS: failing tests
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Thu, 13 Feb 2025 18:38:45 +
with message-id
and subject line Bug#1091943: fixed in onionshare 2.6.2-5
has caused the Debian Bug report #1091943,
regarding onionshare: FTBFS: E ModuleNotFoundError: No module named 'colorama'
to be marked as done.
This means that you claim
Your message dated Thu, 13 Feb 2025 18:35:37 +
with message-id
and subject line Bug#1095343: fixed in extra-data 1.19.0-1
has caused the Debian Bug report #1095343,
regarding extra-data: FTBFS: E AttributeError: module 'numpy' has no
attribute 'AxisError'
to be marked as done.
This mea
Quoting Stéphane Glondu (2025-02-13 14:51:00)
> > Maybe you have an idea what could've triggered this?
> Yes: the new version of ocaml-atd.
>
> You have to replace "-package atdgen" by "-package atdgen-runtime".
thank you, that did the trick! botch now builds again. I'm uploading later
today afte
Hi David,
Am Thu, Feb 13, 2025 at 06:55:50PM +0100 schrieb David Prévot:
> > […] Does it make sense to upload
> > the content of the Git repository[2] or is it better to ask for removal
> > at all? Any other suggestions?
> I raised this bug report pretty late in the release cycle, and the package
Your message dated Thu, 13 Feb 2025 19:23:39 +0100
with message-id <173947101940.2664089.657246392610144...@cairon.jones.dk>
and subject line Re: Bug#1093537: notify-rust: Upcoming zbus update
has caused the Debian Bug report #1093537,
regarding notify-rust: Upcoming zbus update
to be marked as don
Your message dated Thu, 13 Feb 2025 18:22:25 +
with message-id
and subject line Bug#1095793: fixed in gpyfft 0.7.1-3
has caused the Debian Bug report #1095793,
regarding gpyfft: FTBFS with numpy 2.x
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Processing commands for cont...@bugs.debian.org:
> tags 1093819 + pending
Bug #1093819 [src:vim-command-t] vim-command-t: FTBFS with ruby3.3
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1093819: https://bugs.debian.org/cgi-bin/bugreport.cg
Processing control commands:
> tag -1 pending
Bug #1095343 [src:extra-data] extra-data: FTBFS: E AttributeError: module
'numpy' has no attribute 'AxisError'
Added tag(s) pending.
--
1095343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1095343
Debian Bug Tracking System
Contact ow...
Control: tag -1 pending
Hello,
Bug #1095343 in extra-data 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/extra-data/-/commit/d785e3565b34d
Hi Andreas,
On 13/02/2025 11:40, Andreas Tille wrote:
[…] Does it make sense to upload
the content of the Git repository[2] or is it better to ask for removal
at all? Any other suggestions?
I raised this bug report pretty late in the release cycle, and the
package is not yet removed from test
Package: wlmaker
Version: 0.4.1-2
Severity: grave
Attempt was made from a terminal within a wmaker session:
$ wlmaker
2025-02-13 19:31:34.942 (INFO) src/config.c:326 Failed
bs_file_resolve_path(~/.wlmaker.plist, 0x7ffce51edad0): errno(2): No such file
or directory
2025-02-13 19:31:34.942 (INFO)
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:nml
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:dub
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting
Source: phrog
Version: 0.44.1-1
Severity: serious
Tags: ftbfs sid
X-Debbugs-CC: aferra...@debian.org, werdah...@debian.org
rust-zbus 5 was uploaded to Unstable today. phrog needs to be updated
to build against this version.
Thank you,
Jeremy Bícha
Your message dated Thu, 13 Feb 2025 16:33:37 +
with message-id
and subject line Bug#1092423: fixed in gecode-snapshot 6.2.0+git20240207-2
has caused the Debian Bug report #1092423,
regarding gecode-snapshot: FTBFS: make[1]: *** No rule to make target
'ChangeLog'. Stop.
to be marked as done.
On Wed, Feb 12, 2025 at 09:26:37PM +0100, Marcin Owsiany wrote:
> śr., 12 lut 2025 o 13:25 Marcin Owsiany napisał(a):
>
> > I can attach the file as I'm using it now later today, if that's helpful.
> >
>
> Attached is my original (-a) PPD file and the modified one (-b, which works
> for me). Tur
Source: ell
Version: 0.73-1
Severity: serious
Tags: ftbfs sid
X-Debbugs-CC: d...@jones.dk
Today's ell upload failed to build.
https://buildd.debian.org/status/package.php?p=ell
--
Build log excerpt
--
FAIL: unit/test-hwdb
test-hwdb:
Your message dated Thu, 13 Feb 2025 15:59:18 +
with message-id
and subject line Bug#1094111: fixed in rust-glycin-utils 3.0.0~beta-2
has caused the Debian Bug report #1094111,
regarding rust-glycin-utils: FTBFS: unsatisfiable build-dependencies:
librust-gufo-common-0.2+default-dev, librust-gu
Your message dated Thu, 13 Feb 2025 17:09:12 +0100
with message-id
and subject line Close migration blocker bugs
has caused the Debian Bug report #1093251,
regarding texlive-lang: Migration blocker
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is no
Your message dated Thu, 13 Feb 2025 17:09:12 +0100
with message-id
and subject line Close migration blocker bugs
has caused the Debian Bug report #1093732,
regarding texlive-base: Should not migrate to testing
to be marked as done.
This means that you claim that the problem has been dealt with.
I
Your message dated Thu, 13 Feb 2025 17:09:12 +0100
with message-id
and subject line Close migration blocker bugs
has caused the Debian Bug report #1093247,
regarding texlive-extra: Migration blocker
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is n
Processing control commands:
> severity -1 serious
Bug #1093690 [src:netavark] netavark: Upcoming update of zbus to v5
Severity set to 'serious' from 'normal'
--
1093690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093690
Debian Bug Tracking System
Contact ow...@bugs.debian.org with probl
Your message dated Thu, 13 Feb 2025 15:56:28 +
with message-id
and subject line Bug#1081185: fixed in gnome-authenticator 4.5.0-2
has caused the Debian Bug report #1081185,
regarding gnome-authenticator: Upgrading from oldstable to unstable breaks
application
to be marked as done.
This means
Your message dated Thu, 13 Feb 2025 15:56:28 +
with message-id
and subject line Bug#1091937: fixed in gnome-authenticator 4.5.0-2
has caused the Debian Bug report #1091937,
regarding gnome-authenticator: FTBFS: error: failed to select a version for the
requirement `rust-argon2 = "^1"`
to be m
Source: gmsh
Followup-For: Bug #1095345
Hi Santiago,
thanks for the report.
I hopefully fixed this in 4.13.1+ds1-5, although I am not fully convinced that
it is the right approach.
>From
>https://gitlab.onelab.info/gmsh/gmsh/-/commit/08c1d41ba72c6506aa72b95c868cc40b5e0b4cd0
and from the logic
Your message dated Thu, 13 Feb 2025 15:13:36 +
with message-id
and subject line Bug#1095345: fixed in gmsh 4.13.1+ds1-5
has caused the Debian Bug report #1095345,
regarding gmsh: FTBFS: /usr/bin/ld: libgmsh.so.4.13.1: undefined reference to
`dtrsv_'
to be marked as done.
This means that you
Processing control commands:
> severity -1 important
Bug #1091435 [src:percona-toolkit] percona-toolkit: CVE-2024-7701
Severity set to 'important' from 'grave'
--
1091435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1091435
Debian Bug Tracking System
Contact ow...@bugs.debian.org with prob
Control: severity -1 important
Hi,
On 2024-12-26 09:15, Salvatore Bonaccorso wrote:
> Source: percona-toolkit
[…]
> CVE-2024-7701[0]:
> | Use of Password Hash With Insufficient Computational Effort
> | vulnerability in percona percona-toolkit allows Encryption Brute
> | Forcing.This issue affects
Package: lttng-modules-dkms
Version: 2.12.5-1+deb11u1
Severity: serious
Control: found -1 2.13.9-1
Hi,
the bullseye kernel at some point seems to have enabled
-Werror=implicit-function-declaration, causing the module to now fail to
build:
DKMS make.log for lttng-modules-2.12.5 for kernel 5.10.0-
Processing control commands:
> found -1 2.13.9-1
Bug #1095902 [lttng-modules-dkms] lttng-modules-dkms: module fails to build for
Linux 5.10.0-33-amd64: error: implicit declaration of function 'fcheck'
Marked as found in versions lttng-modules/2.13.9-1.
--
1095902: https://bugs.debian.org/cgi-bi
Processing control commands:
> severity -1 grave
Bug #856440 [yabar] yabar: Crashes through regular system use
Severity set to 'grave' from 'important'
--
856440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856440
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> severity -1 serious
Bug #1093537 [src:rust-notify-rust] notify-rust: Upcoming zbus update
Severity set to 'serious' from 'normal'
--
1093537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with pro
Hi Johannes,
Le 13/02/2025 à 11:44, Johannes Schauer Marin Rodrigues a écrit :
while working on the fix for this (which involves adapting a regex for the
argparse output of python 3.13, see #1092479) I ran into a different FTBFS
yesterday:
+ ocamlfind ocamlc -c -w +a-4-9-24 -package dose3 -pack
Package: python-libcst
Version: 1.4.0-1.1
Severity: serious
Tags: patch
python-libcst's Cargo.toml asks for version 1.x of the thiserror
crate. Currently Debian has two versions of the crates, version
1.x in the librust-thiserror-1-dev package and version 2.x in
the librust-thiserror-dev package.
Source: notification-position-reloaded
Version: 0.0~git20241003.720f7e2-2
Severity: serious
Tags: trixie sid upstream
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-48
The Debian GNOME team is intending to include GNOME Shell 48 in
Trixie. Currently, GNOME Shell 48 Beta
Your message dated Thu, 13 Feb 2025 12:23:22 +
with message-id
and subject line Bug#1093414: fixed in postgresql-17 17.3-1
has caused the Debian Bug report #1093414,
regarding postgresql-17: FTBFS:
./build/./build/conftest.c:62:(.text.startup+0x9): undefined reference to
`setproctitle'
to be
Your message dated Thu, 13 Feb 2025 12:23:22 +
with message-id
and subject line Bug#1093414: fixed in postgresql-17 17.3-1
has caused the Debian Bug report #1093414,
regarding postgresql-17: FTBFS/autopkgtest failure with tzdata 2025a due to
minor changes of historical data
to be marked as do
Control: tag -1 pending
Hello,
Bug #1093414 in postgresql 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/postgresql/postgresql/-/commit/44b6eee5b2a155ef77d40c6
Processing control commands:
> tag -1 pending
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:(.text.startup+0x9): undefined re
Package: pyvkfft-cuda
Version: 2024.1.4+ds1-6
Severity: serious
Hi,
pyvkfft-cuda needs a rebuild for the numpy transition, to pick up a dependency
on the new abi, bpython3-numpy2-abi0.
Cheers,
Emilio
Control: fixed -1 ruby-actionpack/2:6.1.7.3+dfsg-9
fixed in src:rails
Processing control commands:
> fixed -1 ruby-actionpack/2:6.1.7.3+dfsg-9
Bug #1094536 [src:ruby-factory-bot-rails] ruby-factory-bot-rails: FTBFS: ERROR:
Test "ruby3.3" failed: cannot load such file -- rack/session/abstract/id
The source ruby-actionpack and version 2:6.1.7.3+dfsg-9 do not appear t
Your message dated Thu, 13 Feb 2025 16:57:08 +0530
with message-id <3ba0a6c9-9dc0-45c1-a5f9-cfda62b1e...@debian.org>
and subject line this is fixed in ruby-actionpack
has caused the Debian Bug report #1094536,
regarding ruby-factory-bot-rails: FTBFS: ERROR: Test "ruby3.3" failed: cannot
load such
Followup-For: Bug #1076456
Control: found -1 2.6-4
That is an incorrect constraint:
#if LINUX_VERSION_CODE >= KERNEL_VERSION(5,12,0) || LINUX_VERSION_CODE >=
KERNEL_VERSION(5,10,220)
you probably want
#if (LINUX_VERSION_CODE >= KERNEL_VERSION(5,12,0)) || \
((LINUX_VERSION_CODE >= KER
Processing control commands:
> found -1 2.6-4
Bug #1076456 [iptables-netflow-dkms] iptables-netflow-dkms: No more builds on
Debian 11 Bullseye since kernel linux-image-5.10.0-31-amd64 (5.10.221-1) due to
"unexport find_module" kernel backport from 5.12
Marked as found in versions iptables-netflo
Hi Stephane,
On Wed, 15 Jan 2025 09:29:36 + Stephane Glondu wrote:
> Your package FTBFS with OCaml 5.3.0 for the following reason:
>
> make[2]: *** [Makefile:278: test-man] Error 1
>
> A full log is available at:
>
>
> http://ocaml.debian.net/transitions/20250111/ocaml-5.3.0/pool/botc
Hi David,
yesterday the package came up as a candidate for the Bug of the Day[1].
Since at first sight I have only seen bug #822899 and the popcon *votes*
of 45 (which is more than a couple of other packages we salvaged) I've
created a repository for the package[2] and pushed an (admittedly very
s
Processing commands for cont...@bugs.debian.org:
> tag 1086028 + patch
Bug #1086028 [src:linux] loupe: FTBFS on mips64el: failed to acquire jobserver
token: Bad address (os error 14)
Bug #1087809 [src:linux] cargo: [mipsel64] failed to acquire jobserver
token/Bad address (os error 14)
Bug #10932
tag 1086028 + patch
tag 1087809 + patch
tag 1093200 + patch
thanks
Hi!
I've finally managed to reproduce this EFAULT in QEMU (using an
Erlang-based script which is shipped in the wings3d source package):
1) I've installed Debian bookworm for mips64el in qemu-system-mips64el
virtual machine (vers
Source: ruby-sprockets-rails
Version: 3.5.2-2
Severity: serious
Justification: autopkgtest failure
Tags: trixie sid ftbfs
User: debian-r...@lists.debian.org
Usertags: rails7
Hi,
We are about to upload rails 7 to unstable, as we are targetting to have rails
7 being released with Trixie.
After the
Source: ruby-with-advisory-lock
Version: 5.1.0-2
Severity: serious
Justification: autopkgtest failure
Tags: trixie sid ftbfs
User: debian-r...@lists.debian.org
Usertags: rails7
Hi,
We are about to upload rails 7 to unstable, as we are targetting to have rails
7 being released with Trixie.
After
Source: ruby-rspec-rails
Version: 6.1.5-2
Severity: serious
Justification: autopkgtest failure
Tags: trixie sid ftbfs
User: debian-r...@lists.debian.org
Usertags: rails7
Hi,
We are about to upload rails 7 to unstable, as we are targetting to have rails
7 being released with Trixie.
After the las
Source: ruby-rabl-rails
Version: 0.6.2-2
Severity: serious
Justification: autopkgtest failure
Tags: trixie sid ftbfs
User: debian-r...@lists.debian.org
Usertags: rails7
Hi,
We are about to upload rails 7 to unstable, as we are targetting to have rails
7 being released with Trixie.
After the last
Source: ruby-invisible-captcha
Version: 2.1.0-1
Severity: serious
Justification: autopkgtest failure
Tags: trixie sid ftbfs
User: debian-r...@lists.debian.org
Usertags: rails7
Hi,
We are about to upload rails 7 to unstable, as we are targetting to have rails
7 being released with Trixie.
After t
Source: ruby-has-scope
Version: 0.8.0-1
Severity: serious
Justification: autopkgtest failure
Tags: trixie sid ftbfs
User: debian-r...@lists.debian.org
Usertags: rails7
Hi,
We are about to upload rails 7 to unstable, as we are targetting to have rails
7 being released with Trixie.
After the last
Source: ruby-activerecord-import
Version: 1.5.0-1
Severity: serious
Justification: autopkgtest failure
Tags: trixie sid ftbfs
User: debian-r...@lists.debian.org
Usertags: rails7
Hi,
We are about to upload rails 7 to unstable, as we are targetting to have rails
7 being released with Trixie.
After
Source: ruby-devise
Version: 4.9.3-1
Severity: serious
Justification: autopkgtest failure
Tags: trixie sid ftbfs
User: debian-r...@lists.debian.org
Usertags: rails7
Hi,
We are about to upload rails 7 to unstable, as we are targetting to have rails
7 being released with Trixie.
After the last upl
Source: ruby-factory-bot-rails
Version: 6.4.2-1
Severity: serious
Justification: autopkgtest failure
Tags: trixie sid ftbfs
User: debian-r...@lists.debian.org
Usertags: rails7
Hi,
We are about to upload rails 7 to unstable, as we are targetting to have rails
7 being released with Trixie.
After t
Source: ruby-ammeter
Version: 1.1.7-1
Severity: serious
Justification: autopkgtest failure
Tags: trixie sid ftbfs
User: debian-r...@lists.debian.org
Usertags: rails7
Hi,
We are about to upload rails 7 to unstable, as we are targetting to have rails
7 being released with Trixie.
After the last up
Source: ruby-acts-as-taggable-on
Version: 10.0.0-2
Severity: serious
Justification: autopkgtest failure
Tags: trixie sid ftbfs
User: debian-r...@lists.debian.org
Usertags: rails7
Hi,
We are about to upload rails 7 to unstable, as we are targetting to have rails
7 being released with Trixie.
Afte
1 - 100 of 111 matches
Mail list logo
