Source: xfsprogs
Version: 6.6.0-1
Severity: normal
Tags: patch
User: debian-...@lists.debian.org
Usertags: pac-bti
Hi,
Pointer Authentication (PAC) and Branch Target Identification (BTI) are
two security features available on arm64. [1]
Please consider building xfsprogs with PAC/BTI support
+debian/debian/changelog 2024-02-28 10:55:16.0
+0100
@@ -1,3 +1,10 @@
+cdparanoia (3.10.2+debian-15) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Build with hardening flags, except for format.
+
+ -- Emanuele Rocca Mon, 06 May 2024 17:42:04 +0200
+
cdparanoia (3.10.2
:54.0 +0100
@@ -1,3 +1,11 @@
+apg (2.2.3.dfsg.1-5.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix dpkg-buildflags invocation in debian/patches/Makefile to properly set
+CFLAGS and LDFLAGS.
+
+ -- Emanuele Rocca Mon, 06 May 2024 17:40:04 +0200
+
apg (2.2.3.dfsg.1-5
On 2023-12-31 10:32, Matthias Klose wrote:
> please also check
>
> - that a cross compiler with this patch has these enabled
>
> - that a cross build of gcc-13 targeting arm64 with this
>patch has these enabled
There have been a few gcc-12 and gcc-13 updates since I initially sent my
Control: retitle -1 gcc-13 FTCBFS: nvptx does not cross compile
On 2024-01-06 01:10, Matthias Klose wrote:
> no, the target is always nvptx-unknown-none.
Ack, but in order to cross build nvptx we probably have to set build and
host? I tried cross building gcc 13.2.0-23 on a x86 system with:
angelog 2024-03-12 12:14:12.0 +0100
+++ cfengine3-3.21.4/debian/changelog 2024-04-18 11:32:38.0 +0200
@@ -1,3 +1,10 @@
+cfengine3 (3.21.4-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * d/patches/time-t-long-long.patch: coerce time_t to long long (closes: #1068665)
+
+ -- Eman
Hi Roland,
On 2024-03-05 03:15, Roland Mas wrote:
> close 1063631 5.0.0.3381-2
The version of hkl currently in unstable, 5.0.0.3381-1, fails to build.
Would it be possible to upload 5.0.0.3381-2 to unstable?
Emanuele
@ -1,3 +1,11 @@
+amberol (0.10.3-2.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Update build dependencies: librust-lofty-0.18-dev,
+librust-mpris-server-0.7-dev. (Closes: #1064531)
+
+ -- Emanuele Rocca Fri, 12 Apr 2024 12:23:35 +0200
+
amberol (0.10.3-2) unstable; u
Hello Sebastian and Andreas,
On 2024-02-15 09:14, Sebastian Ramacher wrote:
> On 2024-02-15 08:30:37 +0100, Andreas Tille wrote:
> > the package builds nicely in my local pbuilder, in Salsa CI as well as
> > in the autobuilders. Thus I'm tagging the bug moreinfo and set severity
> > to
+0200
@@ -1,3 +1,10 @@
+mathgl (8.0.1-8) unstable; urgency=medium
+
+ * Build-depend on python3-all to ensure all supported python versions are
+installed when running debian/tests/run-tests. (Closes: #1067367)
+
+ -- Emanuele Rocca Thu, 11 Apr 2024 15:00:39 +0200
+
mathgl (8.0.1-7) un
; urgency=medium
+
+ * d/patches/arm64-use-acl.patch: Use Arm Compute Library on arm64.
+ * d/patches/acl-no-core.patch: Do not search for obsolete library
+libarm_compute_core.
+
+ -- Emanuele Rocca Wed, 10 Apr 2024 10:44:19 +0200
+
onednn (3.1.1-2) unstable; urgency=medium
* Upload
.
+ * Apply upstream patch to fix FTBFS on armhf/armel (Closes: #1067829)
+
+ -- Emanuele Rocca Thu, 28 Mar 2024 16:56:19 +0100
+
nfs-utils (1:2.6.4-3) unstable; urgency=medium
[ Salvatore Bonaccorso ]
diff -Nru nfs-utils-2.6.4/debian/patches/flushtime-long-long-int.patch nfs-utils-
Hi Aurelien and Michael,
On 2024-03-21 08:54, Aurelien Jarno wrote:
> On 2024-03-19 11:54, Emanuele Rocca wrote:
> > diff -Nru dcmtk-3.6.7/debian/control dcmtk-3.6.7/debian/control
> > --- dcmtk-3.6.7/debian/control 2024-02-28 02:17:02.0 +0100
> > +++ dcmtk
, temporarily drop the subversion and libsvn-perl
+build-deps. The packages are currently not installable on those arches due
+to the ongoing t64 transition and are only needed by git-svn.
+
+ -- Emanuele Rocca Wed, 20 Mar 2024 09:10:32 +0100
+
git (1:2.43.0-1) unstable; urgency=low
Hi Andreas,
On 2024-03-19 10:40, Andreas Tille wrote:
> Since you all pinged that bug we now have another 4 weeks of time before
> anything gets removed from testing. So we just need to bear the noise
> from testing removal warnings of quite some packages (which I'd love to
> get rid of thus
#1060104.
+ * Do not build-depend on graphviz on armhf and armel. The package is
+currently not installable on those arches due to the ongoing t64
+transition.
+
+ -- Emanuele Rocca Tue, 19 Mar 2024 11:08:29 +0100
+
dcmtk (3.6.7-9.1) unstable; urgency=medium
* Non-maintainer upload
Hi,
On 2024-03-19 06:24, Sébastien Jodogne wrote:
> Because of bug #1060104, a large majority of the packages related to
> medical imaging have just disappeared from Debian Unstable.
>
> But, if I correctly understand #1060104, it is specific to one single
> platform (armel).
Indeed, and
Source: rustc
Version: 1.70.0+dfsg1-6
Severity: minor
Hi!
While looking at the rustc build-deps still missing due to the time64
transition, I noticed that rustc build depends on cmake | cmake3. The
latter does not exist, so it should be removed.
Thanks,
Emanuele
On 2024-03-13 02:08, Emanuele Rocca wrote:
> When it comes to actually satisfying build-depends properly it seems
> that as of right now the missing ones are libcurl4-gnutls-dev and
> libgit2-dev.
Cargo is now done. With libcurl4-gnutls-dev and libgit2-dev available I
could bootstrap it
On 2024-03-16 04:21, Emanuele Rocca wrote:
> With libcurl3t64-gnutls cargo can now be rebootstrapped on armhf
And on armel too. Fixed armhf/armel packages uploaded.
> Fabian: it seems that cargo's build-depend on git can be dropped? The
> package builds fine without, tests included.
Hi!
On 2024-03-16 02:29, Simon McVittie wrote:
> On Thu, 14 Mar 2024 at 22:03:57 -0700, Otto Kekäläinen wrote:
> > For example curl isn't building on armel/armhf now and numerous packages
> > that
> > depend of curl are not building on armel/armhf.
>
> I believe a maintainer upload or NMU of
Hi!
On 2024-03-12 10:46, Simon McVittie wrote:
> I think this change might be a pragmatic way to shorten the critical
> path for the time64 transition.
The patch works fine indeed, and stunnel4 can be built successfully on
armhf with it. I agree that it should be applied.
It seems however that
Hi,
On 2024-03-12 05:55, Emanuele Rocca wrote:
> I did manage to get cargo to build in a armhf chroot by manually
> installing the various deps
When it comes to actually satisfying build-depends properly it seems
that as of right now the missing ones are libcurl4-gnutls-dev and
libgit2-dev
[ debian-rust added to CC ]
Hi,
On 2024-03-12 11:03, Simon McVittie wrote:
> In the medium term, cargo needs re-bootstrapping on the affected
> architectures (armel and armhf, plus a bunch of -ports architectures
> where as far as I can see cargo was never available in the past) -
> that's
Source: grok
Version: 1.20110708.1-7.1
Severity: serious
Tags: ftbfs
User: debian-...@lists.debian.org
Usertags: time-t
Hi,
grok fails to build from source if -Werror=implicit-function-declaration
is on. The flag was added to the default ones on armhf and armel to help
with the ongoing time64
Source: fakeroot
Version: 1.34-1
Severity: serious
Tags: ftbfs
User: debian-...@lists.debian.org
Usertags: time-t
Hi,
fakeroot fails to build on armhf and armel when compiled with the time64
flags:
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64
Source: mongo-c-driver
Version: 1.26.0-1.1
Severity: serious
Tags: ftbfs
User: debian-...@lists.debian.org
Usertags: time-t
Dear Maintainer,
mongo-c-driver fails to build from source on armhf. The failure may be
explained with the build flags introduced for the time64 migration,
which are on by
Hi Michael,
On 2024-03-01 09:13, Michael Tokarev wrote:
> This has nothing to do with time64.
Yes and no. :-)
> The prob here is -Werror=implicit-function-declaration
>
> Where that flag is coming from?
Source: udns
Version: 0.4-1.1
Severity: serious
Tags: ftbfs
User: debian-de...@lists.debian.org
Usertags: time64
Dear Maintainer,
udns fails to build on both armhf and armel with the time64 build flags, which
are on by default. It builds fine without.
Specifically, the following flags cause a
Source: google-perftools
Version: 2.15-1.1
Severity: serious
Tags: ftbfs
User: debian-...@lists.debian.org
Usertag: time64
Dear Maintainer,
google-perftools fails to build from source when building with -D_TIME_BITS=64
on armhf and armel with the following error:
src/mmap_hook.cc:309:31: error:
On 2024-03-01 10:28, Emanuele Rocca wrote:
> /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed
> only with _FILE_OFFSET_BITS=64"
>26 | # error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"
> | ^
The build
Source: v4l-utils
Version: 1.26.1-3.1
Severity: serious
Tags: ftbfs
User: debian-...@lists.debian.org
Usertag: time64
Dear Maintainer,
v4l-utils fails to build from source on armhf and armel with the
following error:
In file included from /usr/include/features.h:393,
from
Hi Matthias,
On 2023-11-28 05:00, Emanuele Rocca wrote:
> Let me know if this is what you were looking for.
Both #1055711 and #1057469 have been open for several months now, and
they are blocking progress on enabling BTI in Debian (and Ubuntu). See
https://wiki.debian.org/ToolChain/PAC
On 2024-02-27 04:39, Emanuele Rocca wrote:
> Whilst trying to figure out why a rebuild of firebird3.0 on arm64 does
> not fully enable BTI [1]
And the mysterious link is:
[1] https://wiki.debian.org/ToolChain/PACBTI
d3.0 (3.0.11.33703.ds4-2.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Do not override CXXFLAGS on arm64. (Closes: #-1)
+
+ -- Emanuele Rocca Tue, 27 Feb 2024 16:31:04 +0100
+
firebird3.0 (3.0.11.33703.ds4-2) unstable; urgency=medium
* Bump policy-compliance version to 4.6.2
+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:
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.
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
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
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
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: 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:
===
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
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
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...
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
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:
.
+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/debian/rules 2023-09-29
Source: gcc-14
Version: 14-20240201-2
Severity: serious
Tags: sid ftbfs
User: debian-...@lists.debian.org
Usertags: arm64
gcc-14 currently FTBFS on arm64 due to an upstream regression. Last known
working version was 20240131.
during GIMPLE pass: widening_mul
../../src/gcc/value-range-storage.cc:
Hi,
On 2022-07-26 12:07, Dmitry Shachnev wrote:
> (sid_armel-dchroot)mitya57@amdahl:~$ gcc -fsanitize=address test.c
> /usr/bin/ld: /usr/lib/gcc/arm-linux-gnueabi/12/libasan.so: undefined
> reference to `__atomic_store_8'
> /usr/bin/ld: /usr/lib/gcc/arm-linux-gnueabi/12/libasan.so: undefined
>
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
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))
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
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
>
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/contr
@@ -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
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
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
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
Source: kbtin
Version: 2.1-2
Severity: serious
Tags: patch
User: debian-...@lists.debian.org
Usertags: 32bit-stackclash
Hi,
kbtin currently fails to build from source on armhf. The failure is due
to an incompatibility between valgrind and stack-clash-protection on
32bit arm reported upstream at:
Hi Rafael,
as a workaround for this issue, you could disable stack-clash-protection
when building for armhf. The following snippet in debian/rules should do
the trick:
ifeq ($(DEB_TARGET_ARCH),armhf)
DEB_BUILD_MAINT_OPTIONS = hardening=+all,-stackclash
else
DEB_BUILD_MAINT_OPTIONS =
Source: jtdx
Version: 2.2.159-1
Severity: serious
Tags: ftbfs, patch
User: debian-...@lists.debian.org
Usertags: 32bit-stackclash
Dear Maintainer,
jtdx currently fails to build from source on armel. To address the
immediate issue, please disable stack-clash-protection with the
following snippet
Hi Mathieu,
On 2024-01-14 11:24, Mathieu Malaterre wrote:
> On Sat, Jan 13, 2024 at 9:42 PM Emanuele Rocca wrote:
> > We should downgrade the severity to minor once the fix enters unstable, but
> > keep the bug open as this seems to be an interesting case of
> > s
Control: user -1 debian-...@lists.debian.org
Control: usertag -1 + 32bit-stackclash
Hi,
On Fri, Jan 05, 2024 at 11:45:28PM +0100, Sebastian Ramacher wrote:
> /tmp/ccm0eYhx.s: Assembler messages:
> /tmp/ccm0eYhx.s:537: Error: bad immediate value for offset (4100)
This is caused by
Source: dumpasn1
Version: 20210212-3
Severity: serious
Tags: patch
User: debian-...@lists.debian.org
Usertags: 32bit-stackclash
Hi,
dumpasn1 currently fails to build from source on armhf. The failure is due to
an incompatibility between valgrind and stack-clash-protection on 32bit arm
reported
Source: abinit
Version: 9.10.4-2
Severity: serious
Tags: patch
User: debian-...@lists.debian.org
Usertags: 32bit-stackclash
Dear Maintainer,
abinit currently fails to build from source on armhf. To address the immediate
issue, please disable stack-clash-protection with the following snippet in
On Tue, Nov 28, 2023 at 02:29:28PM +0100, Emanuele Rocca wrote:
> The file qcom/sc8280xp/LENOVO/21BX/audioreach-tplg.bin and its symlink
> qcom/sc8280xp/SC8280XP-LENOVO-X13S-tplg.bin are needed by the Lenovo
> Thinkpad X13s. Please consider adding them to firmware-qcom-soc.
>
Hi Julian!
On 2024-01-12 01:47, Julian Andres Klode wrote:
> Either way, these are harmless
I'm not saying they're harmful, what I'm saying is:
1) the errors you see on armhf when building apt without
stack-clash-protection are the same valgrind reports on amd64 as
well. Hence, you could
Hi Julian,
On 2024-01-11 05:46, Julian Andres Klode wrote:
> And there aren't any hard errors. We could zero initialize
> those or add supressions to make things look nicer I suppose.
Mmmh no, they are all actual errors as far as valgrind is concerned.
The thing is, you're running valgrind
Hi Julian,
On 2024-01-08 10:28, Julian Andres Klode wrote:
> (in Ubuntu we have partially recovered by disabling stack clash
> protection but it crashes on invalid writes there, I suppose we need
> to rebuild some more apt dependencies without the flag...).
The 'invalid writes' issue seems
I've added more context to https://bugs.debian.org/1059352#38, but just to have
some info here too this is the error:
722s ==221367== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
722s ==221367== Using Valgrind-3.20.0 and LibVEX; rerun with -h for copyright
info
722s ==221367==
Control: retitle -1 valgrind: Access not within mapped region on armhf
Hello Paul and Julian,
On 2023-12-24 07:31, Paul Gevers wrote:
> On 23-12-2023 20:40, Julian Andres Klode wrote:
> > the logs for well known bugs so that you don't end up filing bugs
> > against every package broken by
Hi Matthias,
On 2023-12-31 10:32, Matthias Klose wrote:
> please also check
>
> - that a cross compiler with this patch has these enabled
>
> - that a cross build of gcc-13 targeting arm64 with this
>patch has these enabled
Very good point, indeed the original patch I sent did not
Source: gcc-13
Version: 13.2.0-9
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
X-Debbugs-CC: debian-cr...@lists.debian.org
Hi,
cross-building the native compiler (build_type = cross-build-native)
fails due to (1) an issue with m2, and (2) nvptx being confused about
the host/target system.
Hi!
On 2023-10-11 11:08, Raphaël Hertzog wrote:
> it would be nice if sbuild supported the --env=VAR=VALUE command line
> option like autopkgtest:
>
>--env=VAR=value
> Set arbitrary environment variable in the build and test.
> Can be specified multiple times.
As
Hi Steve and Helmut,
On 2024-01-02 05:30, Steve McIntyre wrote:
> Already fixed in git, along with another usr-merge issue I found. The
> next regular build should be fine.
It is. Thank you!
$ curl -s
Package: debian-cd
Version: 3.2.1
Severity: important
Dear Maintainer,
quite a few firmware packages are missing from today's debian-installer
ISOs. Among the missing ones: firmware-atheros, firmware-realtek, and
many others. Some firmware packages such as firmware-ath9k-htc and
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
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
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
Package: gcc-12
Version: 12.3.0-12
X-Debbugs-Cc: debian-...@lists.debian.org, debian-gl...@lists.debian.org
Dear Maintainer,
PAC/BTI is a useful Arm security feature, see this recent presentation
at the Cambridge Mini Debconf for all details: [0]
In order to properly support PAC/BTI in Debian
Hi John,
On 2023-12-04 09:48, John Vincent wrote:
> I tested today's daily installer (2023-12-04 10:14) but the changes
> are seeming to be not included in this installer.
Indeed, 6.6.3-1~exp1 is in experimental. The changes will be included in
the daily installer build once the relevant kernel
Source: lighttpd
Version: 1.4.73-1
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-specific, and the
Control: retitle -1 systemtap: FTBFS with g++-13 on i386, ppc64el, riscv64
On 2023-12-01 04:53, Emanuele Rocca wrote:
> In constructor ‘symresolution_info::symresolution_info(systemtap_session&,
> bool)’,
> inlined from ‘int semantic_pass_symbols(systemtap_session&)’ at
>
Package: systemtap
Version: 5.0-1
Severity: serious
g++ -DHAVE_CONFIG_H -I. -DBINDIR='"/usr/bin"' -DSYSCONFDIR='"/etc"'
-DPKGDATADIR='"/usr/share/systemtap"' -DPKGLIBDIR='"/usr/lib/systemtap"'
-DLOCALEDIR='"/usr/share/locale"' -DDOCDIR='"/usr/share/doc/systemtap"'
-DPYEXECDIR='""'
ses: #1055711)
+
+ -- Emanuele Rocca Mon, 27 Nov 2023 17:22:11 +0100
+
gcc-13 (13.2.0-7) unstable; urgency=medium
* Update to git 20231124 from the gcc-13 branch.
diff -Nru gcc-13-13.2.0/debian/rules2 gcc-13-13.2.0/debian/rules2
--- gcc-13-13.2.0/debian/rules2 2023-10-24 14:39:05.0 +0
Package: firmware-qcom-soc
Version: 20230515-3
Severity: wishlist
Dear Maintainer,
The file qcom/sc8280xp/LENOVO/21BX/audioreach-tplg.bin and its symlink
qcom/sc8280xp/SC8280XP-LENOVO-X13S-tplg.bin are needed by the Lenovo
Thinkpad X13s. Please consider adding them to firmware-qcom-soc.
File:
Package: firmware-atheros
Version: 20230515-3
Severity: wishlist
Dear Maintainer,
The files qca/hpbtfw21.tlv and qca/hpnv21.bin are needed by the Lenovo
Thinkpad X13s. Please consider adding them to firmware-atheros.
Thanks,
Emanuele
Package: bumps-private-libs
Severity: wishlist
User: debian-...@lists.debian.org
Usertags: arm64
Hi!
bumps-private-libs builds fine on arm64. Please add arm64 to the
Architecture field in debian/control.
Thanks,
Emanuele
Hi Rafael,
On 2023-11-16 08:42, Rafael Laboissière wrote:
> Control: forwarded -1 https://sourceforge.net/p/plplot/bugs/206/
>
> * Rafael Laboissière [2023-11-16 07:51]:
>
> > My guess is that the bug is in PLplot and not in gfortran, but this is
> > just a guess. I will eventually inform the
Hello Rafael!
On 2023-11-15 06:47, Rafael Laboissière wrote:
> Does this mean that the origin of the bug is upstream or that it still may
> be a bug in gfortran?
At this point we know for sure that the issue is not armhf-specific, and
also that it is not caused by stack-clash-protection. On the
Hi!
On 2023-11-09 05:11, Rafael Laboissière wrote:
> The Fortran example x09f.f90, which is exercised during the building of
> plplot, now fails on armhf, due to the use of the compiler option
> -fstack-clash-protection.
The problem seems unrelated to stach-clash-protection I think, enabling
the
Hi Rafael,
On 2023-11-13 05:13, Rafael Laboissière wrote:
> The attached file bug-1055750.tgz contains a minimal code that
> triggers the bug on an armhf system
Thanks! For the record I can reproduce the issue in a armhf chroot, but
*not* on armel and arm64. The only thing to change in the
Package: gcc-13
Version: 13.2.0-6
Severity: normal
Dear Maintainer,
On arm64 dpkg-dev adds -mbranch-protection=standard to the default build
flags since version 1.22.0. However, the flag is not used in Debian and
Ubuntu when building GCC. This means that the feature does not work as
intended
Hi Roland!
On 2023-11-08 06:50, Roland Clobus wrote:
> I've run the commands that you have provided, and am unable to reproduce
> your case.
>
> lb config --distribution sid --updates false --archive-areas 'main
> non-free-firmware' --bootloaders grub-efi
> echo live-task-lxde >
On 2023-10-04 03:10, Emanuele Rocca wrote:
> P: Begin unmounting /sys...
> umount: /tmp/sid-image/chroot/sys: target is busy.
> E: An unexpected failure occurred, exiting...
The reason why /sys is busy is that efivarfs is mounted under
/sys/firmware/efi/efivars.
It seems that efiv
Hi Salvatore,
On 2023-11-04 09:57, Salvatore Bonaccorso wrote:
> I'm not sure this is really that urgent, 6.5.10 will be EOL upstream
> at some point and in master branch Bastian et all are prearing the 6.6
> based once. After an extra round in experimental I would expect it
> will now not take
Hi!
On 2023-10-05 10:05, John wrote:
> CONFIG_ARCH_R9A07G054=y
> CONFIG_ARCH_R9A07G043=y
> CONFIG_ARCH_R9A09G011=y
The changes have been merged into master some time ago already:
https://salsa.debian.org/kernel-team/linux/-/merge_requests/867
Salvatore: what is the best way to ensure this makes
2023-10-09 11:45:48.0 +0200
@@ -1,3 +1,9 @@
+gcc-12 (12.2.0-14+deb12u1) bookworm; urgency=medium
+
+ * Fix -fstack-protector handling of overflows on AArch64 (CVE-2023-4039).
+
+ -- Emanuele Rocca Mon, 09 Oct 2023 11:45:48 +0200
+
gcc-12 (12.2.0-14) unstable; urgency=medium
Hi Dmitry!
On 2023-10-31 02:17, Dmitry Baryshkov wrote:
> BTW, Emanuele, are you by chance responsible for the X13s wiki page?
I started it, but most of the useful content has been provided by
someone else. :-)
See https://wiki.debian.org/InstallingDebianOn/Thinkpad/X13s?action=info
> There
1 - 100 of 402 matches
Mail list logo
