tags 548036 +patch sid squeeze
thanks
This bug affects sid and squeeze it does not affect lenny.
adding export CFLAGS += -D_FILE_OFFSET_BITS=64 below the endif line in
debian/rules will fix it.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of
Package: atril
Severity: serious
Tags: patch
atril depends on the obsolete transitional package libtiff4-dev which
has been removed in the latest version of the tiff source package.
The fix is trivial and obvious, change the build-dependency to libtiff-dev
--
To UNSUBSCRIBE, email to
This bug is due to an API change appeared in
OCamlgraph 1.8.4 and then reverted
back in 1.8.5. OCamlgraph 1.8.3 (present
testing's version) is not affected.
Am I correct in thinking that means that the binnmus for dose3 should
be given back?
--
To UNSUBSCRIBE, email to
Severity 651626 important
thanks
>Your package failed to build on the kfreebsd-amd64 buildds:
kfreebsd-amd64 is no longer a release architecture, downgrading.
Note that the experimental package is failing with a different error:
gcc -I/«BUILDDIR»/clisp-2.49+hg.2015.05.31/src
-I/«BUILDDIR»/clisp-2.49+hg.2015.05.31/debian/build/gllib
-I/«BUILDDIR»/clisp-2.49+hg.2015.05.31/src/gllib -falign-functions=4 -W
-Wswitch -Wcomment -Wpointer-arith
/debian/patches/makefile-no-lazbuild1970-01-01
00:00:00.0 +
+++ cqrlog-1.9.0/debian/patches/makefile-no-lazbuild2015-08-30
13:56:31.0 +
@@ -0,0 +1,20 @@
+Description: Avoid using lazbuild for now as it's broken on arm* in sid.
+Author: Peter Michael Green plugw
reopen 794498
thanks
Testing now shows the build-depends are installable but trying to
actually build the package gives
make[3]: /usr/bin/ldc: Command not found
Makefile:109: recipe for target
'stamps/build-d-file-tango-core-tools-LinuxStackTrace.d' failed
make[3]: ***
Package: golang-1.6
Severity: serious
consul failed to build on arm64 with
src/golang.org/x/sys/unix/zsyscall_linux_arm64.go:57: undefined: SYS_POLL
Googling this error finds https://github.com/golang/go/issues/16052
which links to a commit fixing the issue.
--- gazebo-7.3.0+dfsg/debian/changelog 2016-07-21 15:33:10.0 +
+++ gazebo-7.3.0+dfsg/debian/changelog 2016-08-27 16:02:33.0 +
@@ -1,3 +1,9 @@
+gazebo (7.3.0+dfsg-2+rpi1) stretch-staging; urgency=medium
+
+ * Change XML_NO_ERROR to XML_SUCCESS (Closes: 835427)
+
+ -- Peter Michael
package: node-regexpu-core
version: 4.4.0+ds-1
severity: serious
node-regexpu-core build-depends on node-unicode-11.0.0 which is no
longer built by source package node-unicode-data. It appears to have
been replaced by node-unicode-12.0.0
package: node-regenerate-unicode-properties
version: 7.0.0+ds-1
severity: serious
node-regenerate-unicode-properties build-depends on node-unicode-11.0.0
which is no longer built by source package node-unicode-data. It appears
to have been replaced by node-unicode-12.0.0
package: acorn
version: 5.5.3+ds3-2
severity: serious
acorn build-depends on node-unicode-11.0.0 which is no longer built by
source package node-unicode-data. It appears to have been replaced by
node-unicode-12.0.0
Package: firefox-esr
Version: 60.8.0esr-1
Severity: serious
x-debbugs-cc: pkg-rust-maintain...@alioth-lists.debian.net
While trying to update firefox-esr in raspbian bullseye I ran into a
"failed to open: /sbuild-nonexistent/.cargo/.package-cache" error. The
failure also shows up on the
Package: mini-buildd
Version: 1.0.41
Severity: serious
python-mini-buildd depends on and the mini-buildd source package
build-depends on the python-django-registration binary package which is
no longer built by the python-django-registration source package.
I notice this already seems to be
Package: python-tuskarclient
Severity: serious
Version: 0.1.18-1
Tags: bullseye, sid
python-tuskarclient depends on the python-cliff, python-keystoneclient,
python-openstackclient and python-stevedore binary packages which are no
longer built by the corresponding source packages.
If this is
Package: python-os-net-config
Version: 0.1.0-1
Severity: serious
Tags: bullseye, sid
python-os-net-config (build-)depends on the python-oslo.config binary
package which is no longer built by the corresponding source package.
I see no reverse-depends, should this package simply be removed?
package: libgeotiff\
version: 1.5.1-1
severity: serious
tags: bullseye
Hi, libgeotiff just failed to build in raspbian bullseye with the
following message.
Running ../test/testlistgeo using ../bin/listgeo:
package: vmtk
severity: serious
version: 1.3+dfsg-2.3
vmtk build-depends on libvtk6-java which is no longer built by the vtk6
source package.
Package: oz
Version: 0.16.0-2
Severity: serious
Tags: bullseye, sid
oz depends on the python-monotonic binary package which is no longer
built by the python-monotonic source package.
Package: python-os-cloud-config
Severity: serious
Tags: bullseye, sid
python-os-cloud-config depends on a number of binary packages that are
no longer built by their corresponding source packages, including
python-glanceclient
python-ironicclient
python-keystoneclient
python-neutronclient
Package: lua-geoip
Version: 0.1.2+git20160613-3
Severity: serious
Tags: bullseye, sid
lua-geoip depends on geoip-database-extra which is no longer built by
the geoip-database source package.
Package: d-shlibs
Version: 0.85
Severity: serious
The release team have decreed that binaries not built on buildds can no
longer migrate to testing. Please make a source only upload so the fix
for 932632 can migrate to testing.
Looking at
https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-rand/9312542/log.gz
It looks like the packed_simd feature test passes with unstable's
version of rust-packed-simd
but the all features test is still failing with
error[E0433]: failed to resolve: use of undeclared crate
Package: chromium
Version: 93.0.4577.82-1
Severity: serious
chromium build-depends on python-jinja2 which is no longer built by the
jinja2 source package.
It is still present in unstable as a cruft package but is completely
gone from testing.
reopen 1002164
thanks
On 21/12/2021 20:27, plugwash wrote:
The more immediate fix, which I have just uploaded as rust-signal-hook
0.1.13-3 is to do what upstream did in signal-hook 0.1.17 and use a caret
dependency instead of a tilde dependency on signal-hook-registry.
Signal-hook 0.3 has now
Package: scipy
Version: 1.7.1-2
Severity: serious
scipy build-depends on python3-pybind11 (<< 2.8) but testing and unstable
have version 2.8.1-3
Package: pyopencl
Tags: bookworm
Severity: serious
Justification: rc policy - "Packages must be buildable within the same
release"
pyopencl build-depends on pocl-opencl-icd which is no longer in testing.
Package: crystal
Version: 1.2.1+dfsg-6
Severity: serious
Justification: rc policy - "Packages must be buildable within the same
release"
crystal build-depends on libllvm9 or libllvm8, neither of these packages are
available in testing anymore. Please investigate migration to a newer
version
Package: azure-cli
Version: 2.31.0-1
Severity: serious
azure-cli build-depends on pylint3 which is no longer built by the pylint
source package, it is still present in unstable as a cruft package, but is
completely gone from testing.
Since the package was previously an empty (other than
Package: php-oscarotero-gettext
Version: 4.8.2-6
Severity: serious
Justification: rc policy - "Packages must be buildable within the same release"
php-oscarotero-gettext build-depends on the php-illuminate-database binary
package,
which is built by the php-laravel-framework source package which
Source: python-igraph
Version: 0.9.8-1
Severity: serious
Justification: rc policy - packages must be buildable within the same
release
python-igraph build-depends on libigraph-dev which was recently removed on
s390x. So the package's build-depends are no longer satisfiable on that
+
+ * Apply workaround for ruby gtk2/openssl conflict.
+ * Fix tests with ruby 3.0.
+
+ -- Peter Michael Green Sat, 05 Mar 2022 19:11:29
+
+
origami-pdf (2.0.0-1) unstable; urgency=medium
* New upstream release
diff -Nru origami-pdf-2.0.0/debian/patches/gtk2-openssl-workaround.patch
n 32-bit
+architectures.
+
+ -- Peter Michael Green Sun, 27 Feb 2022 07:27:00 +
+
dask (2022.01.0+dfsg-1) unstable; urgency=medium
* New upstream release
diff -Nru dask-2022.01.0+dfsg/debian/patches/series
dask-2022.01.0+dfsg/debian/patches/series
--- dask-2022.01.0+dfsg/debian/patches/series 20
Package: sphinx-remove-toctrees
Version: 0.0.3-1
Severity: serious
The release team have decreed that only binaries build on the buildd network
can migrate to testing, please make a source-only upload so your package can
migrate.
Tags 1006141 +patch
thanks
This was fixed in ubuntu a few months ago by adding ".fpu vfp" to the
assembler file in question.
(within the block of code that is only used on systems with the hard
float ABI).
https://patches.ubuntu.com/s/supertuxkart/supertuxkart_1.3+dfsg1-2ubuntu1.patch
I
During a rebuild of all packages in sid, your package failed to build
on amd64.
I'm no expert on this particular package, but this looks to me like it
is not actually caused by a problem in python-sparse, but is instead a
symptom of python3-numba not being built against python 3.10 due to
Package: android-platform-system-core
Version: 1:10.0.0+r36-9
Severity: serious
The android-platform-system-core source package builds the adb and fastboot
binary packages which are also built (with a higher version number) by
android-platform-tools, I belive this is what lead to the rejection
is some code in rust-atk that translates it to an enum
the corresponding enum value doesn't seem to actually be used for
anything.
Author: Peter Michael Green
--- rust-atk-sys-0.14.0.orig/tests/abi.rs
+++ rust-atk-sys-0.14.0/tests/abi.rs
@@ -134,6 +134,14 @@ fn cross_validate_constants_with_c
Package: precious
Version: 0.1.3-2
Severity: serious
The upstream of the rust which crate dropped the optional dependency on
the rust failure crate. As a result of this the rust-which source
package no longer
builds a librust-which+failure-dev package.
The librust-which+failure-dev binary
Package: rust-csv
Version: 1.1.5-2
Severity: serious
rust-csv's autopkgtest is failing, which is blocking it's migration to
testing.
--- cookbook_read_basic stdout
thread 'cookbook_read_basic' panicked at 'command spawns successfully: Os { code: 2,
kind: NotFound, message: "No such
On 31/08/2023 08:50, Jonas Smedegaard wrote:
, but it is a risky game,
Letting stuff fall ever more out of date is also a risky game as
it tends to mean stuff gets even more intertwined when we
do finally try to update it and if the version of rust-cargo used
by debcargo gets too far out
Package: sccache
Version: 0.5.4-11
Severity: serious
Tags: patch
I just updated addr2line to version 0.20.0, sccache builds succesfully
with the new version after bumping the dependency.
Debdiff attatched.
diff -Nru sccache-0.5.4/debian/changelog sccache-0.5.4/debian/changelog
---
It has no reverse dependencies and is one of the last things keeping
rust-time-0.1 in Debian.
Not speaking for or against removal, but updating it to the latest
version would get rid of the dependency on time 0.1.
Package: rust-leptonica-plumbing
Version: 1.0.1-4
Severity: serious
https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-leptonica-plumbing/36970458/log.gz
118s The following packages have unmet dependencies:
118s autopkgtest-satdep : Depends: librust-leptonica-plumbing-1.0+default-dev
Package: rust-wasmer-enumset-derive
Version: 0.5.0-2
Severity: serious
Tags: trixie, sid
rust-wasmer-enumset-derive and it's reverse dependency
rust-wasmer-enumset are an abandoned fork of rust-enumset-dervive and
rust-enumset, no applications use them anymore so there is no reason to
keep
d test dependencies on librust-rcgen-0.11+default-dev (>=
0.11.1-2)
+
+ -- Peter Michael Green Fri, 25 Aug 2023 18:57:05 +
+
rust-rustls-webpki (0.101.4-1) unstable; urgency=high
* bump project version in virtual packages and autopkgtests;
diff -Nru rust-rustls-webpki-0.101.4/d
I took a look at updating rust-gstreamer to 0.17.4 (this is not the
latest version, but it is the version corresponding to the current rust
gtk stack in Debian) and hence solving the dependency issues with the
current package. There were two unsatisfied dependencies: muldiv 1.x and
pretty-hex
Package: elan
Version: 1.3.1-3
Severity: serious
Tags: patch
A number of rust crates have been updated recently, as a result your
package no longer builds, I have updated the patches to relax the
dependencies and was able to succesfully build the package, I have not
tested it beyond that.
The rust-zstd package has both a dependency and a build-dependency on
librust-zstd-safe-2.0.3+experimental-dev, which does not exist anywhere in
Debian. Presumably it would be built by a rust-zstd-safe package, but no
such package exists, including in the Debian NEW queue.
Specifically looking
Package: rust-hdrhistogram
Version: 7.5.0-1
Severity: serious
I recently updated the hdrhistogram package and as part of that I
resolved the issues that were blocking the tests from running on as
autopkgtests.
Unfortunately when running the autopkgtests on i386 two tests failed, I
can also
Package: deepin-movie
Version: 5.7.15-3
Severity: serious
The deepin-movie-reborn source package was recently binnmu'd for the
ffmpeg transtion,
unfortunately though the resulting binary packages still depend on the
old libav* packages.
reopen 1012221
thanks
On 02/06/2022 13:29, Sylvestre Ledru wrote:
4. Remove the stdweb features in instant and parking-lot and allow
stdweb to be removed from testing.
I think I implemented this solution.
Thanks,
That solves the issue for instant, parking-lot and their reverse
dependencies on gettext-sys, gettext-rs and proptest crates.
+(Closes: #1011620, #1013539)
+
+ -- Peter Michael Green Sat, 16 Jul 2022 19:13:03 +
+
newsboat (2.21-1.2) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru newsboat-2.21/debian/control newsboat-2.21/debian/control
On 01/05/2022 14:00, Fabian Grünbichler wrote:
currently progress is blocked on
- itoa/serde_json transition (anybody working actively on that?)
I just uploaded the new itoa to experimental and took a quick look
through the reverse dependencies.
rust-cssparser - already broken and not in
Package: golang-gopkg-libgit2-git2go.v31
Version: 31.4.3-4
Severity: serious
The autopkgtest for golang-gopkg-libgit2-git2go.v31 is failing with
libgit2 1.3
and hence blocking the transition.
I have written a merge request [1] to fix FTBFS on all platforms. Tested on my
dev machine on amd64 and riscv64. If more helps are needed, please let me know.
Thanks for the patch,
Was this patch just a result of general QA activity or is there some
program you are trying to package?
We can
Package: rust-ahash
Version: 0.7.6-4
Severity: serious
The autopkgtest of rust-ahash is failing
https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-ahash/25673987/log.gz
Testing aeshash/u8
thread 'main' panicked at 'aes must be enabled', tests/bench.rs:20:5
stack backtrace:
0:
Package: rust-smol
Version: 1.2.5-2
Severity: serious
rust-smol build-depends on librust-nix-0.24+default-dev but the nix
crate in debian testing/unstable is now at 0.25
There is a new upstream version of petgraph that uses the new version of
fixedbitset, I suspect the most sensible way to fix this bug is
uploading it and it has been prepared in debcargo-conf (initially
byBlair Noctis with some further tweaking by myself)
However before I upload it, I wanted
Package: rust-coreutils
Version: 0.0.15-1
Severity: serious
cargo build --features "arch base32 base64 basename basenc cat chcon
chgrp chmod chown chroot cksum comm cp csplit cut date dd df dir
dircolors dirname du echo env expand expr factor false fmt fold groups
hashsum head hostid
To clarify the situation for people stumbling across this bug.
The issue in cereal was fixed, however slic3r-prusa still FTBFS because of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021566
Package: ruby-aruba
Version: 2.1.0-1
Severity: serious
Justification: rc policy - "Packages must be buildable within the same release"
User:debian...@lists.debian.org
Usertags: edos-uninstallable
ruby-aruba build-depends on rubocop (<< 1.0) but bookworm and sid have version
1.39.0+dfsg-1
-maintainer upload.
+ * Depend on librust-zip-0.6-dev instead of rust-zip-0.5-dev
+
+ -- Peter Michael Green Wed, 28 Dec 2022 16:57:19 +
+
sccache (0.4.0~~pre1-1) unstable; urgency=medium
[ upstream ]
diff -Nru sccache-0.4.0~~pre1/debian/control sccache-0.4.0~~pre1/debian/control
--- sccache
Source: commons-vfs
Version: 2.1-2
Tags: bookworm, sid
Severity: serious
Justification: rc policy - "packages must be buildable within the same
release"
User: debian...@lists.debian.org
Usertags: edos-uninstallable
commons-vfs build-depends on libcommons-net-java-doc which
is no longer built
Package: cctbx
Version: 2022.9+ds2+~3.11.2+ds1-5
Severity: serious
Despite the fix uploaded for bug 1024859 the cctbx autopkgtest is still
failing
and preventing the package from migrating to testing.
Testing cctbx with python3.10:
Sorry: Please run this program in an empty directory.
Package: obantoo
Version: 2.1.12+ds1-3
Severity: serious
Justification: rc policy - "packages must be buildable within the same
release"
User: debian...@lists.debian.org
Usertags: edos-uninstallable
obantoo build-depends on libitext5-java-doc which is no longer built
by the libitext5-java
Package: pplacer
version: 1.1~alpha19-6
Severity: serious
Justification: rc policy: "packages must be buildable within the same
release"
pplacer build-depends on libmcl-ocaml-dev which is no longer built by the
mcl source package. It is still present in unstable as a cruft package, but
is
Package: ntcard
Version: 1.2.2+dfsg-4
Severity: serious
ntcard build-depends on libnthash-dev which is no longer available on
32-bit architectures.
There are in general 3 potential soloutions for this (in roughly
descending order of preference)
1. Fix your build-dependencies so they are
Package: pushpin
Version: 1.36.0-1
Severity: serious
The new version of pushpin added a dependency on jsonwebtoken,
unfortunately jsonwebtoken depends in ring, which is only available
on x86* and arm*. There is work upstream to make ring more
portable but it seems unlikely to feature in a stable
.
+
+ [ Jochen Sprickerhof ]
+ * Add patch to fix FTBFS on i386.
+Thanks to Adrian Bunk (Closes: 1004869)
+ * Use execute_after_ in d/rules
+ * Set R³ in d/control
+
+ -- Peter Michael Green Sun, 19 Feb 2023 00:50:57 +
+
python-xarray (2023.01.0-1) unstable; urgency=medium
* Mew
On 23/04/2023 21:07, Paul Gevers wrote:
Can you point to a discussion where we might draw the conclusion that
this is common practice or consensus? I *personally* [no hats on] find
that distinction a bit weird although I can see how we would come to
it and also why.
No, I can't point to a
On 23/04/2023 19:19, Paul Gevers wrote:
I claim this is wrong. Would python3-sage one day build on more
architectures, this list would need manual updating. Instead of
hard-coding the list, it's better to ensure the build doesn't happen
or fails on architectures where python3-sage is not
On 09/02/2023 23:43, Michele Martone wrote:
On 20230209@17:50, Peter Green wrote:
Package: librsb
Version: 1.3.0.2+dfsg-1
Tags: bookworm, sid
Severity: serious
Justification: rc policy - "packages must be buildable within the same release"
User: debian...@lists.debian.org
Usertags:
As subject says, this package depends on librust-heapless-0.7-dev which
is missing, rendering the package impossible to install.
I don't see any such dependency, was this a typo.
It does however seem to depend on librust-defmt-0.3+default-dev,
rust-defmt hasn't been uploaded yet, but it seems
Version: 0.12.0-1
rust-derive-builder has now been updated to match rust-derive-builder-core.
/changelog 2023-02-03 13:57:58.0 +
+++ rust-rustls-0.20.8/debian/changelog 2023-06-18 01:01:18.0 +
@@ -1,3 +1,10 @@
+rust-rustls (0.20.8-4.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Bump base64 dev-dependency to 0.21.
+
+ -- Peter Michael Green Sun, 18 Jun 2023
of librust-pyo3-dev.
+ * Apply adjusted upstream patch for py03 0.19 and bump
+dependencies accordingly.
+
+ -- Peter Michael Green Sun, 25 Jun 2023 00:58:26 +
+
python-cryptography (38.0.4-3) unstable; urgency=medium
[ Salvatore Bonaccorso ]
diff -Nru python-cryptography-38.0.4/de
Package: php-doctrine-cache
Version: 2.2.0-1
Severity: serious
Tags: trixie, sid
php-doctrine-cache build-depends on php-nrk-predis which
was a transitional dummy package in bookworm and no
longer exists in trixie or sid.
Presumablly the build-dependency should be changed to
php-predis.
will break builds with older versions of the rust gtk stack.
+
+ -- Peter Michael Green Wed, 28 Jun 2023 18:54:50 +
+
squeekboard (1.22.0-2) unstable; urgency=medium
* Release to unstable
diff -Nru squeekboard-1.22.0/debian/control squeekboard-1.22.0/debian/control
--- squeekboard-1.22.0
has multiple versions of toml and the previous dependency could be
+ satisfied by the wrong one.
++ Add a Debian dependency on "dirs" crate (which appeard to simply be
+ missing before.
+
+ -- Peter Michael Green Mon, 01 Jan 2024 18:34:48 +
+
elan (3.0.0-1) un
Package: rust-ahash
Version: 0.8.5-4
Severity: serious
Thanks for uploading my autopkgtest fixes, the tests now pass on most
architectures.
Unfortunately they still fail on s390x.
290s operations::test::test_add_length stdout
290s thread 'operations::test::test_add_length' panicked
Package: rust-ripasso-cursive
Version: 0.6.1-1
Severity: serious
Tags: trixie, sid
It appears, that despite the version number indicating a compatible
release, that the new
version of ripasso broke the build of ripasso-cursive.
On 19/11/2023 12:14, Peter Michael Green wrote:
Package: rust-ripasso-cursive
Version: 0.6.1-1
Severity: serious
Tags: trixie, sid
It appears, that despite the version number indicating a compatible
release, that the new
version of ripasso broke the build of ripasso-cursive.
https
Package: gtk4
Version: 4.12.5+dfsg-6
Severity: serious
According to britney, gtk4's udebs are uninstallable.
* ∙ ∙ libgtk-4-1-udeb/amd64 has unsatisfiable dependency
* ∙ ∙ libgtk-4-1-udeb/arm64 has unsatisfiable dependency
* ∙ ∙ libgtk-4-1-udeb/i386 has unsatisfiable dependency
* ∙ ∙
Package: python-cryptography
Version: 41.0.7-5
Severity: serious
x-debbugs-cc: eam...@debian.org, kapo...@melix.org
python-cryptography build-depends on python3-cryptography-vectors (<<
41.0.8~)
but unstable has version 42.0.5-1
If you need rust package updates to fix this issue, please tell
Package: aqemu
Version: 0.9.2-3
Severity: serious
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, aqemu still
depends on libqt5dbus5. As a result it is uninstallable on
architectures that are undergoing the time64 transition
(armel, armhf and some
Package: chatty
Version: 0.8.2-1
Severity: serious
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, chatty depends
on both libpurple0 and libpurple0t64. As a
result it is uninstallable on architectures that are undergoing
the time64 transition
=medium
+
+ * Non-maintainer upload.
+ * Add missing function declarations.
+ * Fix clean target.
+
+ -- Peter Michael Green Tue, 02 Apr 2024 04:43:46 +
+
librnd (4.1.1-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru librnd-4.1.1/debian/patches/add-missing-function
) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Add declarations for functions to fix implicit function declaration
+errors.
+
+ -- Peter Michael Green Tue, 02 Apr 2024 02:51:30 +
+
gtk2-engines-murrine (0.98.2-3) unstable; urgency=medium
[ Mike Gabriel ]
diff -Nru
gtk2
Package: comet-ms
Version: 2019015+cleaned1-4
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, comet-ms depends
on both libmstoolkit82 and libmstoolkit82t64. As a
result it is uninstallable on architectures that are undergoing
the
Package: atomes
Version: 1.1.12+repack-2
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, atomes depends
on both libgtk-3-0t64 and .libgtk-3-0t64 As a
result it is uninstallable on architectures that are undergoing
the time64
Package: cyrus-imapd
Version: 3.8.2-1
Severity: serious
User: debian-...@lists.debian.org
Usertag: time-t
cyrus-imapd is failing to build on the architectures affected by the
time_t transition (armel, armhf, several debian-ports architectures)
with the following error.
unit: fatal(Internal
Package: libappmenu-gtk3-parser0
Version: 0.7.6-2.1
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, libappmenu-gtk3-parser0
depends on both libgtk3-0 and libgtk3-0t64. As a
result it is uninstallable on architectures that are
Package: deepin-movie
Version: 5.10.8-2
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, deepin-movie
still depends on libqt5concurrent5. As a
result it is uninstallable on architectures that are undergoing
the time64 transition
Package: libtrantor1
Version: 1.5.12+ds-1
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
libtrantor1 was recently binnmu'd for the time_t transition,
however, despite the binnmu, it still depends on the old libssl3
because said dependency is hardcoded in the source package.
Package: spice-client-gtk
Version: 0.42-2
Severity: grave
Tags: trixie, sid
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition,
spice-client-gtk still depends on libusbredirhost1 and libusbredirparser1,
rather than the t64 versions of those libraries.
Package: ruby-xapian
Version: 1.4.22-1
Severity: grave
Tags: trixie, sid
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, ruby-xapian
still depends on libruby3.1 rather than libruby3.1t64.
As a result it is uninstallable on architectures that are
Package: swtpm-libs
Version: 0.7.1-1.3
Severity: grave
Tags: trixie, sid
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, swtpm-libs still depends
on libglib2.0-0 rather than libglib2.0-0t64. As a result swtpm-tools
is uninstallable on
Package: tfortune
Version: 1.0.1-1
Tags: trixie, sid
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, tfortune
depends on both liblopsub1 and liblopsub1t64. As a
result it is uninstallable on architectures that are undergoing
the
1 - 100 of 101 matches
Mail list logo
