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-dist-requ...@lists.debian.org
with a subject of
package: ftp.debian.org
severity: normal
Please remove the binary packages fp-compiler-2.4.2, fp-docs-2.4.2,
fp-ide-2.4.2, fp-units-base-2.4.2, fp-units-db-2.4.2,
fp-units-fcl-2.4.2, fp-units-fv-2.4.2, fp-units-gfx-2.4.2,
fp-units-gnome1-2.4.2, fp-units-gtk-2.4.2, fp-units-gtk2-2.4.2,
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
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
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
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
+arm64) unreleased; urgency=medium
+
+ * Disable pch to avoid ICE
+
+ -- Peter Michael Green plugw...@debian.org Tue, 03 Jun 2014 10:55:09 +
+
boost1.55 (1.55.0+dfsg-1) unstable; urgency=medium
* Convert debian/copyright to copyright-format 1.0.
diff -Nru boost1.55-1.55.0+dfsg/debian
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
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\
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
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=armhf=1.17-1=1442300722
ERROR: In
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
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
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: 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
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
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.
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
--- 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: 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
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
Package: mpb
Version: 1.7.0-3
While checking why meep wasn't migrating to testing I discovered it had
an unsatisfiable dependency on mpb-dev.
It seems that when the architecture list for mpb was set back to "any"
the architecuture lists for other binary packages were not updated. I am
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.
severity 936630 serious
thanks
gnumed-client depends on the python-hl7 binary package which has already
been dropped by the python-hl7 source package.
Package: stdx-allocator
Version: 3.0.1-2
Tags: bullseye, sid
stdx-allocator failed to build when binnmu'd for the ldc transition.
dh_auto_test -a
cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja test
[0/1] Running all tests.
1/1 stdx-allocator-test
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.
tags 976870 +fixed-upstream
tags 976871 +fixed-upstream
thanks
I don't think these packages are fit for release in their current state
The issue is that the code works with the current version of rustc's
standard library, but is likely to be broken by future versions of
rustc. Since rustc is
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: pulseaudio
Version: 15.0+dfsg1-2
The new version of pulseaudio failed to build when we pulled it into
raspbian bookworm-staging.
Run-time dependency check found: YES 0.15.2
Configuring doxygen.conf using configuration
Program doxygen found: NO
Checking reproducible builds shows
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.
BTW Bastain, mails sent to n...@bugs.debian.org don't get automatically
sent to bug submitters.
Bastian Germann Wrote:
Which team is that? I see Adrien Cunin as maintainer.
Good question!
It seems like for nearly two years, all of the uploads to filezilla and
libfilezilla have been "team
Package: rust-nom
x-debbugs-cc: g...@rxv.cc, ni...@tsipinakis.com
I updated sniffglue to 0.14.0 when trying to unblock some semver
transitions.
Since I did not want to further increase the tangle of transitions I
patched it to
work with the versions of crates currently in Debian. Unfortunately
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
severity 1000892 serious
thanks
As part of the effort to limit the number of llvm packages in the
archive, please upgrade to -13 (or -12).
It has:
llvm-9-dev [armel armhf], libclang-9-dev [armel armhf], clang-9 [armel
armhf], clang-format-9 [armel armhf],
llvm-toolchain-9 has now been
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
Package: plfit
Severity: important
x-debbugs-cc: igr...@packages.debian.org
tags: ftbfs
plfit FTBFS on s390x with test failures.
2: Test command: /<>/_BUILD_SHARED/test/test_continuous
2: Test timeout computed to be: 1000
1: ./test/test_discrete.c:39 : expected -9155.62809000, got
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
Source: wine
Version: 6.0.2~repack-3
Between the version of wine in testing and the version in unstable the
file l_intl.nls
was moved from the "libwine" package to the wine package. This is
causing failures
in tests that install the "wine32" and/or "wine64" packages but do not
install the
+
+ * 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
Package: ftp.debian.org
The latest upload of twisted dropped the (arch any) python3-twisted-bin
and python3-twisted-bin-dbg packages, while retaining the (arch all)
python3-twisted and twisted-cod packages.
The new version of python3-twisted is listed on Packages.debian.org and in
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.
Package: foot
Version: 1.11.0-1
Tags: ftbfs
The arch all build of foot failed, this is preventing the new version
from migrating to
testing, which is needed to complete the fcft transition.
dh_missing -i
dh_missing: warning: usr/share/zsh/site-functions/_foot exists in debian/tmp
but is
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: ftp.debian.org
The rust-clap source package no longer builds librust-clap+ansi-term-dev
librust-clap+term-size-dev librust-clap+vec-map-dev and
librust-clap+yaml-dev . The cruft packages are uninstallable because they
depend on an exact version of librust-clap-dev.
The cruft report
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
) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Switch to rand 0.8.
+
+ -- Peter Michael Green Sun, 23 Jan 2022 14:28:08 +
+
newsboat (2.21-1) unstable; urgency=medium
* New upstream version 2.21
diff -Nru newsboat-2.21/debian/control newsboat-2.21/debian/control
--- newsboat
Package: git-buildpackage
Version: 0.9.25
gbp buildpackage was failing silently (with a return value of 1 but no
error message)
when I tried to build cargo. After adding a bunch of additional debug
prints I tracked
it down to the following exception handler in buildpackage.py
except
-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-leptonica-sys
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
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: 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 would be nice to remove rust-arrayvec-0.5 to only have one version of
rust-arrayvec in Debian.
We can patch out the arrayvec feature in zvariant-derive-2 to unblock this.
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-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-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
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',
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/debian/control 2023
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
Package: rust-h2
Version: 0.1.26-1
X-debbugs-cc: d...@jones.dk
I noticed that Jonas had set a number of bugs about broken rust packages as
blockers of 900928, so I decided to take a look at some of them. I fixed up
bytemuck, image and related packages.
I then started looking at reqwest which
Please upgrade addr2line to a newer release - preferably v0.17.0 but
possibly v0.13.0 (in experimental since more than 5 months) is adequate.
Unfortunately it seems addr2line, gimli, object and some other packages
are fairly closely tied together. I don't think updating them
individually is
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
There seems to be a group of 4 closely related packages, zbus,
zbus-macros, zvariant and zvariant-derive which
should probably be upgraded in lockstep.
2.x (3.x for zvariant) is a semver break, so reverse dependencies need
to be investigated.
rust-ashpd - fixed upstream, upstream fix
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
I just uploaded new package rust-common-failures now sitting in NEW, but
then realized that rust-failure which it depends on is removed from
Debian (see bug#973298).
Please drop rust-common-failures from NEW queue - it is useless.
This is not entirely correct, rust-failure was indeed removed
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.
Package: vk3d
version: 1.2-13
vk3d's build-dependencies are unsatisfible on most architectures,
because debian/control was not updated to reflect the new version number.
reassign 1014663 vkd3d 1.2-13
thanks
vk3d's build-dependencies are unsatisfible on most architectures,
because debian/control was not updated to reflect the new version number.
Sorry messed up the package name, it's vkd3d not vk3d
reopen 1013869
thanks.
the (to me, at least) relatively cryptic changelog entry
Sorry if the changelog wasn't clear. I was building a stack of patches
with the expectation that some of them would be removed later.
reqwest upstream offers several options for tls.
native-tls/default-tls
On 26/06/2022 18:40, Jonas Smedegaard wrote:
Quoting Peter Michael Green (2022-06-26 19:01:04)
To enable rustls support with native or manual roots two crates which
are not in Debian, tokio-rustls and hyper-rustls. For tokio-rustls
Alexander Kjäll prepared a package, which I have just
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
Please upgrade to upstream release v0.99.17.
I made a start on updating this, but the new upstream version adds a
dependency on the convert-case
crate which is not in Debian currently. The dependency is "optional",
but it's part of the "default"
feature selection, so i'm not particularly
1 - 100 of 185 matches
Mail list logo
