Package: swi-prolog
Version: 9.0.4+dfsg-3.1
Severity: grave
Tags: trixie, sid
User: debian-...@lists.debian.org
Usertag: time-t
It looks like the adjustments for the time64 transition in the
9.0.4+dfsg-3.1
NMU were incomplete. Resulting in unsatisfiable dependencies on armel
and armhf at least
tags 1064612 +patch
thanks
rust-ahash is unable to migrate to Testing because its autopkgtests are failing:
A debdiff fixing this issue is attatched.
diff -Nru rust-ahash-0.8.9/debian/changelog rust-ahash-0.8.9/debian/changelog
--- rust-ahash-0.8.9/debian/changelog 2024-02-23 07:28:35.00
Hell All, I have just made singular independent from brial
Thanks for dealing with that part of the issue.
Otherwise it must be keep in mind that Sage is mostly umbrella software.
That means that the dependency of brian on sage material is odd.
odd as it may be, it seems the dependency of pyt
On 27/06/2022 01:15, Jonas Smedegaard wrote:
Thanks for clarifying.
I consider it a *horrific* bug that an interface is explicitly
advertised as available, linking against it succeeds, yet it is
non-functional.
In my opinion this renders the whole package unsuitable for release, and
I hereby
The rust gtk stack is now installable again, but it looks like qwertone
needs some work to build with
the new version of the stack.
It looks like upstream has updated the code for 0.14 but attempting to
grab the upstream commit and
apply it as a patch resulted in a bunch of hunks failling, so i
This appears to be fixed by version 1.6.1-1 in experimental? is there
any blocker for uploading it to unstable?
I started looking into this bug and trying to gauge it's impact.
In particular what if-any applications in Debian actually use the broken
code.
First I tried to use codesearch to search for insert_many but I got way
too many
false-positives. So I tried a different approach. I did however notic
Package: rust-lazycell
Version: 1.3.0-1
Severity: serious
The upload of rust-lazycell 1.3.0-1 introduced three new binary
packages, two of which are currently
uninstallable. This is preventing the package from migrating to testing
which is annoying the release
team (see: https://bugs.debian.or
tags 978219 +fixed-upstream
thanks
The immediate cause of this bug, is the addition of
-DQT_NO_CAST_FROM_ASCII to the compiler flags.
Doing some grepping, this appears like it was caused by the update of
lxqt-buildtools, and appears
to be intentional rather than a leak.
Doing some digging in
hanges at https://github.com/plugwash/libm
<https://github.com/plugwash/libm> and also posted about them upstream
at https://github.com/rust-lang/libm/issues/243
I may or may not add these changes to the Debian package later.
Package: xfce4-verve-plugin
Version: 2.0.0-1
Severity: serious
Tags: bullseye, sid
xfce4-verve-plugin build-depends on libexo-1-dev which is no longer
built by the exo source package,
it is still present in unstable as a cruft package, but is completely
gone from testing.
Package: xfce4-mpc-plugin
Version: 0.5.2-1
Severity: serious
Tags: bullseye, sid
xfce4-mpc-plugin build-depends on libexo-1-dev which is no longer built
by the exo source package,
it is still present in unstable as a cruft package, but is completely
gone from testing.
Package: xfce4-indicator-plugin
Version: 2.3.4-2
Severity: serious
Tags: bullseye, sid
xfce4-indictor-plugin build-depends on libexo-1-dev which is no longer
built by the exo source package,
it is still present in unstable as a cruft package, but is completely
gone from testing.
Package: bedtools
Version: 2.29.2+dfsg-4
Severity: serious
The autopkgtests for bedtools are failing on all tested architectures
(though they are "not a regression" on i386 and armhf). When I look at
the amd64 failure logs, the failures all seem to be missing "../htsutil"
Testing bedtools ba
tags 971018 +patch
thanks
I did some testing on the porterbox, which showed optimizing for size is
enough to make things build on mipsel.
Debdiff attached, no intent to NMU.
diff -Nru libgnatcoll-db-21.0.0/debian/changelog
libgnatcoll-db-21.0.0/debian/changelog
--- libgnatcoll-db-21.0.0/debi
package: ledger2beancount
version: 1.8-1
severity: serious
ledger recently migrated to python 3 (forced by boost dropping python 2
support), this has broken the ledger2beancount autopkgtest and this is
blocking ledger from migrating to testing.
autopkgtest [19:31:06]: test testsuite: - - -
Package: virtualenvwrapper
Severity: serious
Version: 4.3.1-2
Tags: bullseye, sid
virtualenvwapper depends on python-stevedore which is no longer built by
the stevedore source package.
tags 933348 +bullseye,sid
found 933348 1.2.0-1
thanks
This bug also affects testing.
package: caml-crush
tags: buster,sid
severity: serious
x-debbugs-cc: debian-ocaml-ma...@lists.debian.org
caml-crush build-depends on ocaml-native-compilers. In stretch this was
a real package. In buster it is a virtual package provided by ocaml-base
on most architectures, but does not seem to e
tags 905035 +patch
thanks
After some searching around and following links from the gentoo
bugtracker I found a patch for this. I applied it to the package and was
able to get a succesful build in raspbian buster.
A debdiff can be found at
http://debdiffs.raspbian.org/main/libk/libkf5kdcraw/l
Control: tag -1 pending
Hello,
Bug #895469 in openjfx 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/java-team/openjfx/commit/ee1b27a562c3fd384b7bfc2883e4add6
21 matches
Mail list logo
