4-06-03 10:55:47.0
+
@@ -1,3 +1,9 @@
+boost1.55 (1.55.0+dfsg-1+arm64) unreleased; urgency=medium
+
+ * Disable pch to avoid ICE
+
+ -- Peter Michael Green Tue, 03 Jun 2014 10:55:09 +
+
boost1.55 (1.55.0+dfsg-1) unstable; urgency=medium
* Convert debian/copyright to copyrigh
On 09/06/14 14:38, Dimitri John Ledkov wrote:
Actually, I think I couldn't reproduce it on a porter box, as it had a
newer kernel and everything worked just fine.
As a point of interest, which hardware/emulator was your build running
on and with which kernel
My test build without pch was with use
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 debian-bugs-dist-requ...
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Recently while working on a derivative distribution (raspbian) a bug was
discovered that breaks the freepascal compiler if it is built to use vfp
instructions (as our armhf package is) and i
Package: python-apsw
Version: 3.7.16.1-r1-1
Severity: normal
I am working on building a derivative of debian for the raspberry pi and similar
devices called raspbian. While building your package for raspbian jessie I ran
into the following error.
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwr
Package: installation-reports
Severity: normal
-- Package-specific info:
Boot method: CD
Image version: Debian 8.1.0 Jessie amd64 CD1 20150606-14:19
Date:
Machine: Self-built desktop based on haswell i5
I'm filing this report from rescue mode, i'll file a followup mail with more
hardware det
Package: installation-reports
Severity: normal
-- Package-specific info:
Boot method: SD card with isohybrid DVD image
Image version: Stretch weekly build DVD 1
Date:
Machine: Minnowboard Turbot MBT-2210
Partitions:
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborat
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.
https://github.com/golang/sys/com
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 debian-
ches/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
+
+Index: cqr
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]: *** [stamps/build-d-file-tango-core-tool
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
There were problems with using innoextract built with gcc-4.9 with a gcc-5
libstdc++6. As a result a breaks was added to libstdc++6 and innoextract was
binnmu'd.
However the binnmus on arm64
Severity 651626 important
thanks
>Your package failed to build on the kfreebsd-amd64 buildds:
kfreebsd-amd64 is no longer a release architecture, downgrading.
package: libqglviewer
version: 2.6.3+dfsg1-1
x-debbugs-cc: woo...@debian.org
libqglviewer FTBFS on armel and armhf, the qt4 and qt5 builds both fail
for different reasons. wookey asked me to take a look at it.
The qt4 build is suffering from qreal vs double issues. These were
fairly easy to p
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 -Wreturn-typ
Found 694876 1.17-1
Thanks
when building on a btrfs filesystem, tests in the build ob obnam fail like
this:
We saw very similar issues with 1.17-1 on the raspbian stretch
autobuilders (which use btrfs)
http://buildd.raspbian.org/status/fetch.php?pkg=obnam&arch=armhf&ver=1.17-1&stamp=144230072
Package: obnam
version: 1.17-1
We are seeing test failures with obnam on the raspbian autobuilders
(which use btrfs).
Having seen similar issues in the past i'm pretty sure this is a btrfs
related issue rather than an issue related to anything we changed in
raspbian. Specifically as I unders
package: lightspark
version: 0.7.2-6
severity: important
user: debian-...@lists.debian.org
usertags: arm64
[ 41%] Building CXX object src/CMakeFiles/spark.dir/scripting/abc.cpp.o
cd /«PKGBUILDDIR»/obj-aarch64-linux-gnu/src && /usr/bin/c++ -DAUDIO_BACKEND="\"pulse sdl\""
-DBOOST_MULTI_INDEX_DIS
package: umockdev
version: 0.8.8-1
severity: important
user:debian-...@lists.debian.org
usertags: arm64
/umockdev-record/testbed-all-empty: OK
**
ERROR:tests/test-umockdev-record.c:369:t_testbed_one: assertion failed
(serr == ""): ("calling: info\n" == "")
/bin/bash: line 1: 4522 Aborted
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package xfce4-battery-plugin
This update fixes the build on arm64 where the deprecated binary sysctl
interface is not available. It should be a no-op on architectures where
Package: installation-reports
Severity: normal
I installed debian on my cubox i4x4. As expected not all the memory was seen,
what I wasn't expecting was that my sata hard drive wasn't working after
install.
I am not 100% sure whether it was working during the installer or not. I think
it was but
package: ftp.debian.org
x-debbugs-cc: libgpgme11-...@packages.debian.org
The package libgpgme11-dev is no longer built by the gpgme1.0 source
package and the old binary is no longer installable due to a versioned
dependency on libgpgme11 .
The cruft report claims a bunch of dependencies will
/debian/patches/0010-xml-no-error.patch1970-01-01
00:00:00.0 +
+++ gazebo-7.3.0+dfsg/debian/patches/0010-xml-no-error.patch2016-08-27
16:02:33.0 +
@@ -0,0 +1,24 @@
+Description: Change XML_NO_ERROR to XML_SUCCESS (Closes: 835427)
+Author: Peter Michael Green
+Bug
I'm getting a bunch of "unnecessary qualification" issues:
The unnessacery qualifications issues are trivial to fix, just remove
unused_qualifications from the list of lints to deny in lib.rs
Unfortunately though, I was unable to get parsec-interface to build
with the new version of prost.
Luckily for you, upstream has already fixed this issue in the master Git
branch; I've linked the pull request above.
I've looked at that pull request, it doesn't seem relavent,
seems to relate to building the embedded copy of mbedtls,
while the debian package is patched to use system mbedtls.
I
Version: 0.6.0-1
> Please upgrasde to (or separately provide) newer branch v0.6.
Done
Please upgrade to, or separately provide, branch v0.24.
I've just uploaded ratatui 0.25 and tui-react 0.23 to experimental.
Can you prepare updates for btm and safe-vdash and tell me when
you are ready for uploads to unstable?
Package: rust-async-channel
Version: 2.3.1-4
One of the tests for rust-async-channel depends on
|librust-easy-parallel-3+std-dev
which does not exist. This is blocking migration to testing.
After looking at the Cargo.toml files I belive this should be changed to |
||librust-easy-parallel-3+def
41:04.0
+
@@ -1,3 +1,11 @@
+rust-if-watch (3.2.0-9.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Update versioning smol dev-dependency to match regular
+dependency.
+
+ -- Peter Michael Green Wed, 17 Jul 2024 18:41:04 +
+
rust-if-watch (3.2.0-9) unstable;
> Please upgrade to, or separately provide, sysinfo branch v0.30.
I've uploaded the new version of rust-sysinfo to experimental.
There are four reverse dependencies, btm, git-delta,
rust-process-viewer and rust-vergen.
rust-process-viewer and rust-vergen are rust-team packages:
rust-process
sinfo 0.30
+
+ -- Peter Michael Green Sat, 20 Jul 2024 13:03:30 +
+
git-delta (0.17.0-3) unstable; urgency=medium
* drop patch 2002_sysinfo,
diff -Nru git-delta-0.17.0/debian/patches/1002_sysinfo.patch
git-delta-0.17.0/debian/patches/1002_sysinfo.patch
--- git-delta-0.17.0/debi
Please upgrade to branch v0.23.
The trust dns project has renamed itself to hickory dns
and rust-hickory-resolver 0.24 has been packaged in
Debian as a new package.
Does that satisfy your requirements?
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://tests.reproducible-builds.org/debian/rb-pkg/trixie/amd64/r
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: btm
I'm currently in the process of preparing updates for crossterm
to 0.27 and ratatui to 0.23.
Btm's dependencies (both cargo and Debian) already allow the
new version of crossterm, but they don't allow the new version
of ratatui. I don't see anything too scary in the upstream
changel
Package: safe-vdash
I'm currently in the process of preparing updates for crossterm
to 0.27 and ratatui to 0.23.
save-vdash's cargo dependencies already allow the new
versions (indeed the new versions will allow patches to be
dropped) but the Debian dependencies currently do not.
After bumping t
Package: dwarf2sources
Version: 0.2.1-1
Tags: trixie, sid
I am currently preparing an update of rust-backtrace and related crates.
they have been uploaded to experimental and I hope to upload them
to unstable in the not too distant future.
backtrace 0.3.68 -> 0.3.69
addr2line 0.20.0 -> 0.21.0
fa
Package: dgit
(this bug report is a result of a question discussion in IANs tag2upload
talk at the cambridge miniconf 2023)
In the talk Ian made the following points
* the current Salsa approach leads to users accidentlly receiving
patches unapplied git trees
* In a later slide git.dgit.debi
Package: rust-wasmtime
Version: 10.0.1+dfsg-7
I currently working on an update of rust-backtrace and it's
dependencies, backtrace itself is not semver breaking, but
several of it's dependencies are.
backtrace 0.3.68 -> 0.3.69
addr2line 0.20.0 -> 0.21.0
fallible-iterator 0.2.0 -> 0.3.0
gimli 0.27
> Please update to (at least) newer upstream release v0.3.69.
Backtrace itself is not semver breaking, but some of it's dependencies
are.
backtrace 0.3.68 -> 0.3.69
addr2line 0.20.0 -> 0.21.0
fallible-iterator 0.2.0 -> 0.3.0
gimli 0.27.3 -> 0.28.1
object 0.31.1 -> 0.32.1
I've uploaded these to
git2 to 0.18 and bat to 0.24.
+
+ -- Peter Michael Green Sun, 03 Dec 2023 13:41:55 +
+
git-delta (0.16.5-3) unstable; urgency=medium
* mention unrelated but similarly named package and binary executable
diff -Nru git-delta-0.16.5/debian/control git-delta-0.16.5/debian/control
--- git-
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: sccache
Version: 0.7.4-3
I have been working on an update of rust-backtrace and it's
dependencies, backtrace itself is not semver breaking, but
several of it's dependencies are.
backtrace 0.3.68 -> 0.3.69
addr2line 0.20.0 -> 0.21.0
fallible-iterator 0.2.0 -> 0.3.0
gimli 0.27.3 -> 0.28.1
urrently
+ 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 +
+
el
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 t
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 pow
severity 1064708 important
Can you explain why you downgraded this bug? it looks rc to me
and is blocking the time_t transition.
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
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
0.98.2-3.1) 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
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 transit
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).
=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
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 (arme
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 ti
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 underg
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 erro
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 (arm
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.
Ub
+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
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
* ∙ ∙ libgtk-
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
un
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 architectures
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 tim
I am aware that v2 is already pending in experimental, but given the
pace of transitioning to a new branch, it is helpful to have the
rng.fill() function available faster, for packages to prepare for the
transition, which is then in more cases possible to handle by loosenig
crate depenency to ">=
+
+++ python-maturin-1.3.2/debian/changelog 2024-06-30 11:34:30.0
+
@@ -1,3 +1,10 @@
+python-maturin (1.3.2-2.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Relax cargo dependency on itertools
+
+ -- Peter Michael Green Sun, 30 Jun 2024 11:34:30 +
:21.0
+
@@ -1,3 +1,10 @@
+rust-criterion (0.5.1-3.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Relax itertools dependency.
+
+ -- Peter Michael Green Sat, 10 Feb 2024 04:34:21 +
+
rust-criterion (0.5.1-3) unstable; urgency=medium
* (build-)depend on package
-30 12:28:45.0
+
@@ -1,3 +1,10 @@
+rust-criterion-0.3 (0.3.6-8.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Relax itertools dependency.
+
+ -- Peter Michael Green Sun, 30 Jun 2024 12:28:45 +
+
rust-criterion-0.3 (0.3.6-8) unstable; urgency=medium
* update
Package: dgit
dget -d http://deb.debian.org/debian/pool/main/g/git/git_2.39.2-1.1.dsc
mkdir dgittest
cd dgittest
git init
dgit import-dsc ../git_2.39.2-1.1.dsc +workingbranch
results in.
Dgit metadata in .dsc: specified git info (debian)
dgit: import-dsc of .dsc with Dgit field, using git hash
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 hostn
16
+ 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
--- squeekbo
Please consider enabling feature socks now: Package rust-socks is now in Debian.
The socks feature of rust-reqwest depends on the tokio-socks crate, not the
socks
crate.
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: edos-uninstal
I've prepared an upload of verion 0.17 of pyo3 and built/tested breezy
with it. It built successfully the autopkgtest passed. Any objections if
I go ahead and update to this version?
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 sourc
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.
autopkg
Package: rust-debcargo
I've attached a patch which makes debcargo build with clap 4, debcargo
builds and it's cargo tests run succesfully, but I haven't actually done any
testing of the command line interface with this patch.
Fabian and I have agreed on irc that it probablly doesn't make sense t
Package: rust-wasmer-enumset
rust-wasmer-enumset and it's support crate rust-wasmer-enumset-derive
are a fork of the enumset/enumset-derive crates to fix a specific issue.
The issue has now been fixed in the enumset crates and the
wasmer-enumset crates are unmaintained
The only reverse-depen
Please upgrade to newer upstream branch v0.11.
The new version depends on rust-derive-builder-macro which is not
currently in Debian.
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 compl
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 onc
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
pload.
+
+ [ 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
reassign 1034723 rust-h2
thanks
The following vulnerability was published for rust-hyper.
CVE-2023-26964[0]:
|/An issue was discovered in hyper v0.13.7. h2-0.2.4 Stream stacking /|/occurs
when the H2 component processes HTTP2 RST_STREAM frames. As a /|/result, the
memory and CPU usage are hig
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 av
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 dis
Package: rust-hyper-rustls
Version: 0.24.1-2
Severity: minor
debian/tests/control in rust-hyper-rustls still refers to rustls 0.20,
even though
the package itself is now using rustls 0.21.
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 the
d build and 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
Package: rust-rustls-webpki
Version: 0.101.4-2
Severity serious
https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-rustls-webpki/37179484/log.gz
92s debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
'/usr/bin/cargo', '-Zavoid-dev-deps', 'test', '--verbose', '--ve
patch to bump rustix dependency.
+
+ -- Peter Michael Green Sun, 27 Aug 2023 19:54:23 +
+
rust-async-process (1.7.0-2) unstable; urgency=medium
* update dh-cargo fork;
diff -Nru rust-async-process-1.7.0/debian/control
rust-async-process-1.7.0/debian/control
--- rust-async-process-1.7.0/deb
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
--- sccache-0.5.4/
Reopen 1050113
thanks
Bumped the hint to 0.101.3-2.
Testing migration was unfortunately interrupted by a security bug.
then some follow-up issues with the new upstream version uploaded
to fix the security bug.
Can you update the hint to 0.101.4-4?
Package: rust-laurel
Version: 0.5.3-1
In the rust team we are working on upgrading rust-bindgen from 0.60 to
0.66, there are a few reasons for this. Firstly it's part of the
dependency stack
for the new version of rust-cargo. Secondly the version currently in sid
has a
compatibility issue with
On 03/09/2023 14:58, Peter Michael Green wrote:
The attatched debdiff,
Sorry, really attached nowdiff -Nru rust-laurel-0.5.3/debian/changelog rust-laurel-0.5.3/debian/changelog
--- rust-laurel-0.5.3/debian/changelog 2023-07-18 14:26:32.0 +
+++ rust-laurel-0.5.3/debian/changelog
-leptonica-sys (0.4.6-2.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Relax dependeny to allow bindgen 0.66.
+
+ -- Peter Michael Green Sun, 03 Sep 2023 14:19:09 +
+
rust-leptonica-sys (0.4.6-2) unstable; urgency=medium
* update DEP-3 patch headers
diff -Nru rust-lep
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.
1 - 100 of 237 matches
Mail list logo
