Package: pesign
Version: 116-7
While working on the time64 transition in raspbian, I discovered pesign failing
to build with a linker error.
cc -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/build/reproducible-path/pesign-116=. -fstack-protector-strong
on libext2fs-dev.
+
+ -- Peter Michael Green Wed, 12 Jun 2024 11:42:41
+
+
btrfs-progs (6.6.3-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru btrfs-progs-6.6.3/debian/control btrfs-progs-6.6.3/debian/control
--- btrfs-progs-6.6.3/debian/control2024-02-28 05:21
Package: lime
Version: 5.2.0+dfsg-3
Severity: serious
Justification: rc policy - "packages must be buildable within the same release"
User: debian...@lists.debian.org
Usertags: edos-uninstallable
lime build-depends on boost1.74, which is no longer in testing. It seems that
lime was removed from
Package: beast-mcmc
Version: 1.10.4+dfsg-5
Severity: serious
x-debbugs-cc: r-cran-rj...@packages.debian.org
beast-mcmc build-depends on r-cran-rjava, which is no longer available
on i386. It appears that the package failed to build, and the old
binaries were then removed.
Package: guestfs-tools
Version: 1.52.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: edos-uninstallable
guestfs-tools on armel build-depends on linux-image-marvell:armel |
linux-image-versatile:armel
neither of which is available anymore.
It looks like the only kernel now
+
+ * Non-maintainer upload.
+ * Relax dependency on itertools.
+
+ -- Peter Michael Green Fri, 31 May 2024 03:20:52 +
+
precious (0.6.0-5) unstable; urgency=medium
* update patch 2001_indexmap to relax dependency;
diff -Nru precious-0.6.0/debian/control precious-0.6.0/debian/control
upload.
+ * Bump itertools dependency to 0.12.
+
+ -- Peter Michael Green Fri, 31 May 2024 02:36:38 +
+
git-delta (0.17.0-1) unstable; urgency=medium
[ upstream ]
diff -Nru git-delta-0.17.0/debian/control git-delta-0.17.0/debian/control
--- git-delta-0.17.0/debian/control 2024-04-02 09
-05-31 01:59:04.0 +
@@ -1,3 +1,10 @@
+btm (0.9.6-6.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Relax itertools dependency to allow 0.12.
+
+ -- Peter Michael Green Fri, 31 May 2024 01:59:04 +
+
btm (0.9.6-6) unstable; urgency=medium
* update copyright info
on zstd crate.
+
+ -- Peter Michael Green Fri, 31 May 2024 01:25:52 +
+
elan (3.1.1-1) unstable; urgency=medium
* Import new upstream version (3.1.1)
diff -Nru elan-3.1.1/debian/control elan-3.1.1/debian/control
--- elan-3.1.1/debian/control 2024-05-03 19:04:30.0 +
Please upgrade (or separately package) newer upstream branch v0.8.
I presume this was meant to say 8.x, rather than 0.8
It seems version 8 of der-parser depends on two crates that
are not currently in debian. asn1-rs and displaydoc.
+1,10 @@
+389-ds-base (3.0.2+dfsg1-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Relax cargo dependency on lru
+
+ -- Peter Michael Green Mon, 27 May 2024 07:44:54 +
+
389-ds-base (3.0.2+dfsg1-1) experimental; urgency=medium
* New upstream release.
diff -Nru 389-ds-base
I tried updating inotify and applying the upstream patch to make notify
use the new version of inotify, but after doing so I got a bunch
of test failures when building python-watchfiles.
quick-xml to 0.31
+
+ -- Peter Michael Green Sat, 25 May 2024 11:17:53 +
+
rust-rio (0.8.3-3) unstable; urgency=medium
* update dh-cargo fork;
diff -Nru rust-rio-0.8.3/debian/control rust-rio-0.8.3/debian/control
--- rust-rio-0.8.3/debian/control 2023-06-20 18:36:23.0 +
Package: rust-laurel
Version: 0.6.2-1
Severity: serious
rust-laurel's autopkgtest fails on s390x. I belive the patch
skip-parse_syslog-on-big-endian.patch should be reinstated
but I do not want to get into a revert war with the
maintainer.
So I feel I need to lay out, in more detail than
is
angelog 2024-03-18 05:44:43.0 +
+++ rust-ahash-0.8.11/debian/changelog 2024-05-17 03:52:01.0 +
@@ -1,3 +1,10 @@
+rust-ahash (0.8.11-2.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Allow all 0.14.x versions of rust-hashbrown.
+
+ -- Peter Michael Green
2024-05-16 08:34:24.0 +
@@ -1,3 +1,10 @@
+rust-roadmap (0.6.0-2.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Bump serde-yaml to 0.9
+
+ -- Peter Michael Green Thu, 16 May 2024 08:34:24 +
+
rust-roadmap (0.6.0-2) unstable; urgency=medium
* update copyright
Package: ftp.debian.org
Please remove the cruft binary packages librust-bindgen+clap-dev
librust-bindgen+default-dev librust-bindgen+env-logger-dev
librust-bindgen+log-dev librust-bindgen+logging-dev librust-bindgen+runtime-dev
librust-bindgen+static-dev librust-bindgen+which-dev
These
I got the following error when trying the same thing.
I have no idea why, since the ioctl_write_ptr and ioctl_read macros are
still supposed to be around. I can't spot any relevant change in nix
that would cause this to happen. Help would be appreciated.
The relavent change is.
All Cargo
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
* ∙ ∙
On 04/03/2024 23:24, Peter Green wrote:
Package: rust-smol
I am currently preparing to update the rust-nix pacakge to version 0.27.
The smol crate has a dev-dependency on the nix crate, which the Debian
packaging translates to build and autopkgtest dependencies. After
relaxing the dependencies
:20.0 +
@@ -1,3 +1,11 @@
+netavark (1.4.0-4.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Apply upstream patch for new version of rust-nix (Closes: #1064580)
+ * Relax cargo dependency on sysctl crate (Closes: #1069350)
+
+ -- Peter Michael Green Thu, 02 May 2024 17:08:20
.
+
+ -- Peter Michael Green Thu, 02 May 2024 16:30:23 +
+
greetd (0.9.0-6) unstable; urgency=medium
* Relax dependency on rpassword (Closes: #1057931).
diff -Nru greetd-0.9.0/debian/control greetd-0.9.0/debian/control
--- greetd-0.9.0/debian/control 2023-12-21 14:17:58.0 +
to support 0.27 and explicitly enable
+required features, since nix no longer enables any features by default.
+(Closes: #1064479)
+
+ -- Peter Michael Green Thu, 02 May 2024 16:14:54 +
+
aardvark-dns (1.4.0-5) unstable; urgency=medium
* Build against clap version 4, Closes: #1040876
if I get no response I will likely NMU this when the
new rust-nix is uploaded to unstable.
I have now uploaded rust-nix to unstable and uploaded
the nmu for this package.
Final debdiff is attatched.
pyo3 crate (Closes: #106435)
+ * Add missing build-dependency on librust-pyo3-file-dev
+ * Fix build with newer versions of rust-breezyshim.
+
+ -- Peter Michael Green Sat, 27 Apr 2024 11:28:42 +
+
lintian-brush (0.152) unstable; urgency=medium
* Fix compatibility with newer rust crates. Closes:
Unsatisfiable build-dependency on librust-heck-0.5+default-dev
There seems to be an error here. the version of librust-prost-dev in sid
(build-)depends on librust-heck-0.4+default-dev.
The version in experimental does depend on librust-heck-0.5+default-dev
as it's first choice, but that's
Package: rust-multihash-derive-impl
Version: 0.7.0-1
Severity: serious
rust-synstructure was recently updated to version 0.13.1
I tried bumping the dependency but that caused failures due to
mismatched versions of syn. Bumping the dependency on syn as well
resulted in.
error[E0609]: no field
Package: rust-failure-derive
Version: 0.1
Tags: trixie, sid
Severity: serious
rust-synstructure was recently updated to version 0.13.1
I tried bumping the dependency but that caused failures due to
mismatched versions of syn. Bumping the dependency on syn as well
resulted in.
error[E0433]:
Package: rust-abscissa-derive
Version: 0.7.0-1
Severity: serious
rust-synstructure was recently updated to version 0.13.1
I tried bumping the dependency but that caused failures due to
mismatched versions of syn. Bumping the dependency on syn as well
resulted in.
error[E0432]: unresolved
Looking at the changelog, I see
Build with --as-needed.
I suspect this is responsible for the build failure on armel
On 23/04/2024 15:52, Arnaud Ferraris wrote:
Hi,
On Thu, 27 Jul 2023 20:19:19 +0100 Peter Green wrote:
> squeekboard - not investigated yet.
Tests fail after bumping dependency.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042405
I've just uploaded the new version of squeekbo
On 14/04/2024 20:21, Yves-Alexis Perez wrote:
On Sat, 2024-04-13 at 16:11 +0100, Peter Green wrote:
>> Hi, thanks for the patch. It looks a bit strong though, undefining stuff
>> like
>> that unconditionally. Do you have pointers to the Ubuntu bug or something?
>> I've lo
Package: libvdeplug-slirp
Version: 0.1.0-2
Tags: trixie, sid
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, libvdeplug-slirp
still depends on the pre-time64 libraries libvdeplug2 and
libvdeslirp0. It also depends on
kalzium needs to be rebuilt for the time64 transition, but it has had
a FTBFS bug with no maintainer response for 4 months. The only reverse
dependencies seem to be a number of metapackages.
In particular, the kdeedu package is a key package and has a hard
dependency on kalzium. This means that
Hi, thanks for the patch. It looks a bit strong though, undefining stuff like
that unconditionally. Do you have pointers to the Ubuntu bug or something?
I've looked at upstream commits and issues and couldn't see anything there.
My understanding of the issue.
In glibc _FILE_OFFSET_BITS=64 is
-maintainer upload.
+ * Fix installation of cupshelpers module with Python 3.12. Patch taken from
+Ubuntu 1.5.18-1ubuntu6 upload by Till Kamppeter (Closes: #1054795).
+
+ -- Peter Michael Green Fri, 12 Apr 2024 23:24:56 +
+
system-config-printer (1.5.18-1) unstable; urgency=medium
to override system settings.
+
+ I suspect that unsetting _FILE_OFFSET_BITS is unnessacery in general and the
+ line could be completely removed. However to minimise the risk of regressions
+ I instead used an ifndef gaurd
+Author: Peter Michael Green
+Bug-Debian: https://bugs.debian.org/1068159
+
+---
block 1036884 by 1066134
tags 1066134 +patch
thanks
Hi.
The build failure of ppp in unstable is a blocker for the time_t
transition, since ppp needs to be rebuilt against the new versions
of libpcap and openssl. The version in experimental seems to build fine.
Can you fix this, either by
Package: haskell-hourglass
Version: 0.2.15-5
Severity: serious
User: debian-...@lists.debian.org
Usertag: time-t
The recent binnmus of haskell-hourglass on armel and armhf
failed to build with test failures.
calendar: FAIL
*** Failed!
Ubuntu has made a couple of changes that look like they may relate to this
issue.
Changelog for version 1.5.18-1ubuntu6 says
"Fix installation of cupshelpers module with Python 3.12."
Changelog for version 1.5.18-1ubuntu7 says
"Drop build dependency on python3-distutils."
Diffs are
Package: urfkill
Version: 0.5.0-7.1
Tags: trixie, sid
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, urfkill
depends on both libglib2.0-0 and libglib2.0-0t64. As a
result it is uninstallable on architectures that are undergoing
Package: tpm2-initramfs-tool
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, tpm2-initramfs-tool
depends on both libtss2-esys-3.0.2-0 and libtss2-esys-3.0.2-0t64. As a
result it is uninstallable
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
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: 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: 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: samba-dsdb-modules
Version: 2:4.19.5+dfsg-4
Tags: trixie, sid
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, samba-dsdb-modules
depends on both libgpgme11 and libgpgme11t64. As a
result it is uninstallable on
Package: riseup-vpn
Version: 0.21.11+ds1-5
Tags: trixie, sid
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, riseup-vpn
depends on both libqt5widgets5 and libqt5widgets5t64. As a
result it is uninstallable on architectures that are
Package: reapr
Version: 1.0.18+dfsg-5
Tags: trixie, sid
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, reapr
depends on both libtabixpp0 and libtabixpp0t64. As a
result it is uninstallable on architectures that are undergoing
the
Package: rakarrack
Version: 0.6.1-8
Tags: trixie, sid
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, rakarrack
depends on both libasound2 and libasound2t64. As a
result it is uninstallable on architectures that are undergoing
the
Package: libqt5-ukui-style1
Version: 1.0.8-1
Tags: trixie, sid
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, libqt5-ukui-style1
depends on both libqt5widgets5 and libqt5widgets5. As a
result it is uninstallable on architectures
Package: populations
Version: 1.2.33+svn0120106+dfsg-6
Severity: grave
Tags: trixie, sid
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition,
populations still depends on libqt5xml5,
rather than libqt5xml5t64. As a result it is uninstallable on
Package: pidgin-gnome-keyring
Version: 2.0-2
Severity: grave
Tags: trixie, sid
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition,
obs-advanced-scene-switcher still depends on libpurple0,
rather than libpurple0t64. As a result it is uninstallable on
Package: perdition
Version: 2.2-3.3
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, perdition
depends on both libvanessa-socket2 and libvanessa-socket2.
As a result it is uninstallable.
Interesting in this case, the
Package: obs-advances-scene-switcher
Version: 1.23.1-2
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition,
obs-advanced-scene-switcher still depends on libcurl4,
rather than libcurl4t64. As a result it is uninstallable on
architectures
/gfp_xdr.c to fix
+implicit declaration error.
+
+ -- Peter Michael Green Thu, 04 Apr 2024 04:41:24 +
+
gfarm (2.7.20+dfsg-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru gfarm-2.7.20+dfsg/debian/patches/missing-feature-test-macros.patch
gfarm-2.7.20+dfsg/debian/patch
Package: mariadb-plugin-s3
Version: 1:10.11.7-3
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, mariadb-plugin-s3
depends on both libcurl4 and libcurl4t64. As a
result it is uninstallable on architectures that are undergoing
the
Package: mariadb-plugin-hashicorp-key-management
Version: 1:10.11.7-3
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition,
mariadb-plugin-hashicorp-key-management
depends on both libcurl4 and libcurl4t64. As a
result it is
Package: lua-lxc
Version: 1:3.0.2-2
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, lua-lxc
depends on both liblxc1 and libliblxc1t64. As a
result it is uninstallable on architectures that are undergoing
the time64 transition
Package: ltrsift
Version: 1.0.2-9
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, ltrsift
depends on both libgenometools0 and libgenometools0t64. As a
result it is uninstallable on architectures that are undergoing
the time64
Package: lomiri-filemanager-app
Version: 1.0.4+dfsg-1
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, lomiri-filemanager-app
depends on both libsmbclient and libsmbclient0. As a
result it is uninstallable on architectures that are
Package: lomiri-system-settings
Version: 1.1.0-2
Severity: grave
lomiri-system-settings depends on lomiri-system-settings-security-privacy, which
is not availble on armel, armhf or mips64el.
The reason, or at least one reason, it is not available is because
Package: qml-module-lomiri-components-extrasVersion: 0.10.0-5
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition,
qml-module-lomiri-components-extras
depends on both libqt5printsupport5 and libqt5printsupport5t64. As a
result it is
Package: indi-apogee
Version: 0.10.0-5
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, indi-apogee depends
on both libapogee3 and libapogee3t64. As a
result it is uninstallable on architectures that are undergoing
the time64
Package: gpa
Version: 0.10.0-5
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, gpa depends
on both libgpgme11 and libgpg11t64. As a
result it is uninstallable on architectures that are undergoing
the time64 transition (armel, armhf
Package: gir1.2-keybinder-0.0
Version: 0.3.1-2.3
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
libkeybinder0 has been renamed to libkeybinder0t64, however gir1.2keybinder0.0
still depends on the former on most architectures. As a result it is
uninstallable on architectures
Also, the bootstrapping procedure is only required when icmake isn't avaialble
yet. For the construction of the bobcat library icmake 11.01.02-1 is required,
and icmake.01.02-1 needs libbobcat-dev >= 5.07.00, which is available since
bullseye (oldstable).
So maybe you can also provide some info
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: 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: 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: 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: 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
severity 1067391 serious
thanks
After rebuilding for the time64 transition, bitlbee-facebook depends on
both libglib2.0-0 and libglib2.0-0t64. As a result it is uninstallable on
architectures affected by the time64 transition (armel, armhf and
several unofficial ports).
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
) 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: 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
severity 966249 serious
thanks
That's actually an issue with GDC, it only supports a really old
standard library version currently (will be resolved with GDC 11,
apparently), and supporting multiple standard library versions is a
massive pain. I lowered the issue priority to wishlist, since GDC
severity 1064708 important
Can you explain why you downgraded this bug? it looks rc to me
and is blocking the time_t transition.
It looks like there are two separate issues here.
arm64, ppc64el, riscv64, s390x and ppc64el are failing because
the c type char is unsigned on those platforms, which means the
rust type c_char is an alias for u8 instead of i8. Probably just
needs some casts adjusting.
armel, armhf, i386 and
Package: aegean
Version: 0.16.0+dfsg-3
Severity: serious
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, aegen depends
on both libgenometools0t64 and libgenometools0. As a
result it is uninstallable on architectures that are undergoing
the time64
Package: qtwebengine-opensource-src
Version: 5.15.15+dfsg-2
Severity: serious
qtwebengine-opensource-src failed to build on armhf when binnmu'd for the time_t
transition due to symbol changes.
(qtwebengine does not support any of the other architectures affected by
the time64 transition.
grep
Package: atril
Version: 1.26.2-2
Severity: serious
The latest version of atril depends on both libatrildocument3 and
libatrildocument3t64. As a result it is uninstallable on
architectures that are undergoing the time64 transition
(armel, armhf and some debian-ports archictures).
Package: rust-coreutils
Version: 0.0.24-2
Severity: serious
rust-coreutils FTBFS with the new version of rust-uutils-term-grid.
The Debian build-dependency allows the new version, but the Cargo
dependency does not.
After bumping the cargo dependency, the code fails to build with a
bunch of
git failed to build when binnmu'd for the time64 transition and also
in lucas's test build a few days earlier. This was filed as bug 1066794.
Andrey Rakhmatullin responded to the bug report saying he was unable to
reproduce the failure. Michael Hudson replied with a post suggesting
that the
On 17/03/2024 13:01, Jérémy Lal wrote:
The last missing piece seems to be version >= 3 of
https://tracker.debian.org/pkg/rust-pem
I've uploaded this to experimental, please tell me when you are ready for it
to be uploaded to unstable.
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
severity 1066972 important
thanks
Indeed, there is no librust-rfc2047-decoder-0.2+default-dev package.
librust-rfc2047-decoder-0.2+default-dev is a virtual package provided
by librust-rfc2047-decoder-dev which is built from the
rust-rfc2047-decoder source package.
Following the dependency
tainer upload.
+ * Fix FTBFS with "type annotation needed" error on i386.
+
+ -- Peter Michael Green Thu, 14 Mar 2024 16:10:58 +
+
railway-gtk (2.4.0-1) unstable; urgency=medium
* New upstream release
diff -Nru railway-gtk-2.4.0/debian/patches/add-type-annotation.patch
rai
rust-symphonia-core appears to FTBFS from an i386 sbuild chroot with a
test 'units::tests::verify_timebase' panicking
units::tests::verify_timebase stdout
thread 'units::tests::verify_timebase' panicked at 'assertion failed:
`(left == right)`
left: `4503599627370496`,
right:
preliminary analysis
upstream changelog doesn't look too scary, no obvious breakage there.
rdeps:
0123456789001234567890012345678900123456789001234567890012345678900123456789001234567890
oxigraph (librust-sparesults-dev):
jonas package, upstream version in Debian uses 0.30, upstream did
I partially started to patch gtk3-rs to use the newer glib from
experimental. However, this is not really supported and I'd rather
remove it now that it's EOL. For qwertone we can employ partial
vendoring; this will also need to be done for squeekboard (in progress).
I'd appreciate if you agree
The armhf build complains about Extra-Depends: dpkg-dev (>= 1.22.5),
gcc-13 (>= 13.2.0-16.1), libssl-dev (>= 3.1.5-1.1), but I checked and
all of these exists in armhf, so not sure what is going on.
There is a little more information further down the page.
cargo build-depends on:
- cargo:armel
On 07/03/2024 19:43, Peter Green wrote:
In raspbian, I removed the reference from misfortune.cabel, removed the
build-dependencies on libghc-regex-pcre* and also (for unrelated reasons)
removed the build-dependency on ghc-doc. After doing so I was able to
successfully build the package.
Scratch
Can you please investigate the situation and figure out how to resolve
it?
I'm no haskell expert, but to me the dependency looks vestigal. Grepping
the source tree for "pcre" finds a mention in the misfortune.cabal
file but no mentions in the actual code, and there are no corresponding
binary
I have built the rust-polling successfully in my local loong64
environment, without modifications required.
Make sure you are not using DEB_BUILD_OPTIONS=nocheck
since rust crates don't have stable ABIs and cargo doesn't support
pre-built rust crates, librust* packages contain source code
+1,10 @@
+rust-smol (1.3.0-5.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Allow building with nix 0.27.
+
+ -- Peter Michael Green Mon, 04 Mar 2024 23:06:03 +
+
rust-smol (1.3.0-5) unstable; urgency=medium
* add patches 2001_async_* to accept older crates;
diff -Nru
Package: debian-dvd-1
Version: 12.5.0
Severity: normal
Tags: l10n
X-Debbugs-Cc: usergr...@users.osdn.me
Dear Maintainer,
To enable Japanese input using anthy and uim,
uim-anthy package is neccessary for Debian-DVD-1 installation media.
Without it, we need to downlowd that package via internet.
t;user" feature.
+
+ -- Peter Michael Green Sat, 24 Feb 2024 13:29:45 +
+
nsncd (1.4.1-2) unstable; urgency=medium
* debian: Delete README.source.
diff -Nru nsncd-1.4.1/debian/patches/nix-0.27.patch
nsncd-1.4.1/debian/patches/nix-0.27.patch
--- nsncd-1.4.1/debian/patches/nix-0.27.patc
1 - 100 of 3360 matches
Mail list logo
