On 25/02 03:29, Sandro Tosi wrote:
> Emanuele, pytest-localserver has been orphaned, so you can go ahead
> and upload it if you want
Done.
> (and i dont think it's appropriate anymore to use the DPMT git repo, i
> guess you can move it to the debian/ namespace)
Also done, thanks Sandro.
On 10/02 09:47, Matthias Klose wrote:
> ruby-http ftbfs for 2.5, but not for 2.3 in unstable:
Note that the bug is not reproducible with ruby-http 3.3.0-2 as tests
have been disabled:
https://salsa.debian.org/ruby-team/ruby-http/commit/728a3fbcc7c59ebb14cb55aa9f084b910d666971
https://salsa.debian
Hi Svante,
On 09/09 03:34, Svante Signell wrote:
> Currently systemtap FTBFS on GNU/Hurd and GNU/kFreeBSD-any due to
> several linux-specific includes in some .cxx-files and usage of
> PATH_MAX, which does not exist on GNU/Hurd. Additionally, for non-linux
> architectures only systemtap-common, s
Hi Anton,
On 13/05 03:16, Anton Zinoviev wrote:
> On Wed, May 13, 2020 at 01:16:32PM +0200, Jochen Sprickerhof wrote:
> > Severity: grave
> > Justification: renders package unusable
>
> Well, the package is not unusable. It is usable by all X programs which
> do not rely on fontconfig.
It migh
Package: systemtap
Version: 4.3-2
Severity: grave
With linux-image-5.8.0-3-amd64 version 5.8.14-1, stap fails as follows:
$ sudo stap -e 'probe oneshot { println("hello world") }'
[...]
/usr/share/systemtap/runtime/linux/access_process_vm.h: In function
‘__access_process_vm_’:
/usr/share/systemt
Package: bpftrace
Version: 0.11.3-3
Severity: grave
Justification: renders package unusable
Any attempt of running bpftrace programs fails on my sid workstation:
$ sudo bpftrace -e 'kprobe:do_nanosleep { printf("PID %d sleeping\n", pid); }'
Two passes with the same argument (-tti) attempted to
Note that the failure is due to stapbpf/Makefile.am trying to add the
stapusr group, and the systemtap Debian package does that in
systemtap-runtime's postinst script already.
Perhaps it would make sense to patch stapbpf/Makefile.am to get rid of
install-exec-hook, and add a dpkg-statoverride call
Hi,
On 04/08 05:50, Otto Kekäläinen wrote:
> There is however work now being done by Emmanuel Rocca at
> https://salsa.debian.org/debian/dstat/commits/master
>
> I have adopted rdiff-backup now, so I don't have interest in taking on any
> new packages atm, so please Emmanuel continue the good wor
Package: nvidia-legacy-390xx-kernel-dkms
Version: 390.144-1
Severity: normal
Tags: patch
Hi,
today I've upgraded to linux-image-5.14.0-1-amd64-unsigned, and
nvidia-legacy-390xx-kernel-dkms failed to build with the following
error:
/var/lib/dkms/nvidia-legacy-390xx/390.144/build/nvidia/os-interf
Package: wnpp
Severity: wishlist
Owner: Emanuele Rocca
* Package name: prometheus-trafficserver-exporter
Version : 0.0.2
Upstream Author : Greg Dallavalle
* URL : https://github.com/gdvalle/trafficserver_exporter
* License : Apache-2.0
Programming Lang
Hi Timo,
On 15/08 12:02, Timo Juhani Lindfors wrote:
> just a status update, the following combination still crashes:
>
> systemtap 2.3-1
> linux-image-3.10-2-amd64 3.10.5-1
Running mmap-trace.stp on sid for a few minutes I could not reproduce
the bug.
systemtap 4.2-3
linux-image-5.4.0-4-amd6
Hi,
On 29/05 04:27, Vagrant Cascadian wrote:
> The generated PDF files included in the systemtap-doc package include
> dates based on the build time, which breaks reproducible builds.
>
> The attached patch enables use of SOURCE_DATE_EPOCH, by setting
> FORCE_SOURCE_DATE=1, which texlive requires
Package: live-manual-pdf
Version: 2:20151217.2
Severity: important
Dear Maintainer,
All files under /usr/share/doc/live-manual/pdf/ seem to be broken.
Screenshot of `evince
/usr/share/doc/live-manual/pdf/live-manual.portrait.en.a4.pdf.gz`
attached.
I've also tried decompressing the file to rul
Package: live-build
Version: 1:20230502
Severity: normal
Dear Maintainer,
Building a live image with `lb build` fails towards the end with the
following error:
P: Begin unmounting /sys...
umount: /tmp/sid-image/chroot/sys: target is busy.
E: An unexpected failure occurred, exiting...
The iss
Source: sane-backends
Version: 1.2.1-6
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
X-Debbugs-CC: debian-cr...@lists.debian.org
Dear Maintainer,
some compiler flags are architecture specific and should not leak when
cross-building.
As an example, -fcf-protection is x86-specif
Hi,
On 2023-12-04 03:10, Ben Hutchings wrote:
> The D and W flags mean there were prior BUG and WARN errors logged.
> Please send those as well.
Here is the very first warning:
Nov 30 17:16:45 ci-worker-armhf-03 kernel: WARNING: CPU: 10 PID: 1592 at
fs/dcache.c:365 dentry_free+0x98/0xd0
Hi Simon,
On 2023-12-07 08:39, Simon Josefsson wrote:
> During debci autopkgtest of a new version of libgssglue on i386 I got
> a failure like this, which is fatal and execution halts.
>
> 117s vex x86->IR: unhandled instruction bytes: 0x2E 0x8D 0xB4 0x26
The problem can be reproduced with valgr
Package: src:armnn
Version: 20.08-13
Severity: serious
armnn 20.08-13 seems to compile correctly on i386, but then FTBFS due to
the following test failures:
Running 430 test cases...
./src/armnn/test/ModelAccuracyCheckerTest.cpp(103): [1;31;49merror: in
"ModelAccuracyCheckerTest/TestFloat32Outp
Note that since the upload of 20.08-13 the package now fails to build for
different reasons on i386 vs arm64/armhf.
I've opened https://bugs.debian.org/1042942 for i386.
On arm64/armhf the bug seems to be due to a missing include in
core/utils/misc/Utility.h from libarm-compute-dev.
[ 2%] Build
Hi Matthias,
On 2024-01-23 09:01, Matthias Klose wrote:
> This is a long standing, re-occurring issue which never has been
> forwarded and committed by the armel ports to GCC upstream.
You seem to be aware of previous occurrences of this issue. Please share
the details you have available such as
Package: valgrind
Version: 1:3.20.0-2.1
Severity: important
User: debian-...@lists.debian.org
Usertags: 32bit-stackclash
Tags: upstream
On armhf, valgrind dies with a SIGSEGV when checking certain programs
built with either -fstack-clash-protection or -fstack-check.
The following example is a rep
now that #1057693 is fixed.
+
+ -- Emanuele Rocca Thu, 25 Jan 2024 12:29:55 +0100
+
libgssglue (0.8-2) unstable; urgency=medium
* Disable valgrind in i386 due to #1057693.
diff -Nru libgssglue-0.8/debian/tests/control libgssglue-0.8/debian/tests/control
--- libgssglue-0.8/debian/tests
@@ -1,3 +1,11 @@
+libvorbis (1.3.7-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Disable test-coupling-segfault on armhf due to valgrind bug #1061496.
+(Closes: #XXX)
+
+ -- Emanuele Rocca Thu, 25 Jan 2024 16:25:09 +0100
+
libvorbis (1.3.7-1) unstable; urgency=medium
load.
+ * Don't run autopkgtests on armhf due to valgrind bug #1061496. (Closes: #XXX)
+
+ -- Emanuele Rocca Fri, 26 Jan 2024 11:02:37 +0100
+
sndfile-tools (1.5-2) unstable; urgency=medium
[ Debian Janitor ]
diff -Nru sndfile-tools-1.5/debian/tests/control sndfile-tools-1.5/debian/tests/
Hi Luca,
On 2024-01-29 01:33, Luca Boccassi wrote:
> This causes systemd to FTBFS on armel since the new upload of
> libatomic-14. No other architecture is affected.
>
> cc -o systemd-cryptsetup
> systemd-cryptsetup.p/src_cryptsetup_cryptsetup-keyfile.c.o
> systemd-cryptsetup.p/src_cryptsetup_
40127/debian/changelog
--- gcc-14-14-20240127/debian/changelog 2024-01-27 09:51:04.0 +0100
+++ gcc-14-14-20240127/debian/changelog 2024-01-29 19:55:54.0 +0100
@@ -1,3 +1,9 @@
+gcc-14 (14-20240127-1.1) unstable; urgency=medium
+
+ * Add upstream patch libatomic-armel.diff.
+
+ -- Em
On 2024-01-29 09:04, Luca Boccassi wrote:
> Guess that doesn't solve it them, as it's the same problem, the meson
> build tests are failing, all of these should be 'YES':
Upstream proposed two patches though, the one I tried is:
libatomic_la_LIBADD += $(addsuffix _8_2_.lo,$(SIZEOBJS))
+libatomic
Control: tags -1 patch
On 2024-01-29 10:23, Emanuele Rocca wrote:
> Upstream proposed two patches though, the one I tried is:
>
> libatomic_la_LIBADD += $(addsuffix _8_2_.lo,$(SIZEOBJS))
> +libatomic_la_LIBADD += tas_1_2_.lo
The problem was not the patch, but the fact that it did
specific build flags.
+ Closes: -1.
+
+ -- Emanuele Rocca Tue, 06 Feb 2024 20:23:38 +0100
+
gdb-mingw-w64 (13) unstable; urgency=medium
* Switch from the obsolete libncurses5-dev build-dependency to
diff -Nru gdb-mingw-w64-13/debian/rules gdb-mingw-w64-13+nmu1/debian/rules
--- gdb-mingw-w64-13/deb
Hi,
On 2024-02-04 08:47, Paul Gevers wrote:
> With a recent upload of gcc-defaults the autopkgtest of mosquitto fails in
> testing when that autopkgtest is run with the binary packages of
> gcc-defaults from unstable on armel. It passes when run with only packages
> from testing. In tabular form:
Source: libcap-ng
Version: 0.8.4-1
Severity: serious
Tags: sid trixie ftbfs
Hi,
libcap-ng currently FTBFS with the following error:
make[6]: Entering directory '/<>/build-py3.11/bindings/python3'
cat /usr/include/linux/capability.h | grep '^#define CAP' | grep -v '[()]' >
caps.h
cat ../../../s
Source: console-setup
Version: 1.224
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Tags: sid trixie ftbfs
Dear Maintainer,
console-setup 1.224 fails to build from source with the following error:
Dumping the encoded keymaps for pc105...
WARN
Source: psmisc
Version: 23.6-2
Dear Maintainer,
psmisc 23.6-2 fails to build from source with sbuild in a schroot on at least
amd64 and arm64 with the following error:
Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /usr/share/d
Source: lsof
Version: 4.95.0-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Tags: sid trixie ftbfs
Dear Maintainer,
lsof currently fails to build from source on amd64 and arm64 with the following
error:
Optional tests:
LTbigf ... OK
LTdnl
Source: pycurl
Version: 7.45.2-7
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Tags: sid trixie ftbfs
Dear Maintainer,
pycurl currently fails to build from source on amd64 and arm64 with the
following error:
=== F
Hi,
On 2024-02-08 02:06, Colin Watson wrote:
> On Wed, Feb 07, 2024 at 11:13:01PM +0100, Holger Wansing wrote:
> > Am 7. Februar 2024 21:55:05 MEZ schrieb Emanuele Rocca :
> > >Perhaps this is related to the fact that 1.224 dropped the binary
> > >package console-s
Source: glibc
Version: 2.37-15
Severity: wishlist
Tags: patch
User: debian-...@lists.debian.org
Usertags: arm64
Control: block -1 by 1057469
Hi,
As discussed on the debian-glibc mailing list [1], please consider
building glibc on arm64 with -mbranch-protection=standard to enable
support for the P
Package: bpftrace
Version: 0.20.1-1
Severity: important
Hi,
bpftrace in sid fails to find individual uprobes, but strangely manages
to find them if using a wildcard. The uprobe then seems to behave as
expected, it can print arguments and such.
root@testvm:~# bpftrace -e 'uprobe:/bin/ls:format_u
Hi Petter,
On 2024-02-10 06:04, Petter Reinholdtsen wrote:
> This issue cause a failing autopkgtest with libvorbis. I would much
> prefer a fix in valgrind instead of disabling a autopkgtest check.
As an alternative to disabling the test, you could consider disabling
stack-clash-protection on ar
On 2024-02-12 09:43, Craig Small wrote:
> Upstream fix is
> https://gitlab.com/psmisc/psmisc/-/commit/8fa115138f79f807d2f07e578f9a40c38c228c0b
> If you can confirm it is the same issue then I've got the fix.
That's it, the above patch fixes the issue here.
+0200
+++ xfsprogs-6.5.0/debian/changelog 2024-02-12 16:09:51.0 +0100
@@ -1,3 +1,10 @@
+xfsprogs (6.5.0-1.1) UNRELEASED; urgency=medium
+
+ * Increase build verbosity, and add support for the "terse"
+DEB_BUILD_OPTIONS tag.
+
+ -- Emanuele Rocca Mon, 12 Feb 2024 16:09:
Hi Simon,
On 2024-09-24 09:16, Simon McVittie wrote:
> In a recent upload this failed on armhf, and only armhf: the actual
> tests appear to have all succeeded, but then xvfb-run exited with status
> 1 anyway. I am able to reproduce this on the armhf porterbox amdahl.
>
> A simplified reproducer
401 - 442 of 442 matches
Mail list logo
