Hi,
On 2023-11-25 12:37, Wookey wrote:
> For debian we'll keep an eye on it, do a belated rebuild to see how
> much of a problem we really have, and then decide if we should revert
> it too until some stuff if fixed.
I now finally have some data to share. In total, out of the whole Debian
archive
On Thu, Nov 23, 2023 at 10:45:33AM +0100, Matthias Klose wrote:
> Hi,
>
> it looks like enabling this flag on armel/armhf is a little bit premature.
>
> Apparently it's not completely supported upstream, and might cause
> regressions, according to
> https://bugzilla.redhat.com/show_bug.cgi?id=152
Hi,
On 2023-11-24 10:50, Matthias Klose wrote:
> A major problem will be valgrind stopping to work, causing issues in the
> test suites of other packages.
>
> Also after rebuilding libxml2, libarchive, gnutls28, libselinux without this
> flag on armhf, issues go away again.
FTR there is no issue
Hi Matthias,
On 2023-11-24 10:50, Matthias Klose wrote:
> On 24.11.23 07:19, Emanuele Rocca wrote:
> > In case there are any bugs, which is of course possible, please file
> > them and add debian-arm@ to X-Debbugs-CC.
>
> No, I will not do that. Sorry, but the task of the porters it NOT to put
>
On Fri, Nov 24, 2023 at 01:34:21AM +0100, Guillem Jover wrote:
> > Is that a feature that the Debian ARM32 porters and the security team really
> > want to support actively, despite the missing upstream support?
>
> According to https://bugs.debian.org/918914#73 there were no pending
> toolchain i
On 2023-11-24 01:34 +0100, Guillem Jover wrote:
> On Thu, 2023-11-23 at 10:45:33 +0100, Matthias Klose wrote:
> > it looks like enabling this flag on armel/armhf is a little bit premature.
> > In Ubuntu, people tracked down segfaults due to this change in at least
> > valgrind and gnutls, maybe mo
Hi,
Short introduction: I work at Canonical in the Foundations team and made
changes in gnutls which is one of the packages that first
encountered/caused issues which then started blocking various migrations
and changes.
On Fri, Nov 24, 2023, Matthias Klose wrote:
> On 24.11.23 07:19, Emanuele Ro
* Emanuele Rocca:
> Hello!
>
> On 2023-11-24 01:34, Guillem Jover wrote:
>> According to https://bugs.debian.org/918914#73 there were no pending
>> toolchain issues related to this.
>
> That is correct. The GCC maintainers at Arm confirm that
> stack-clash-protection is supported on 32 bit too.
J
On 24.11.23 07:19, Emanuele Rocca wrote:
Hello!
On 2023-11-24 01:34, Guillem Jover wrote:
According to https://bugs.debian.org/918914#73 there were no pending
toolchain issues related to this.
That is correct. The GCC maintainers at Arm confirm that
stack-clash-protection is supported on 32 b
Hello!
On 2023-11-24 01:34, Guillem Jover wrote:
> According to https://bugs.debian.org/918914#73 there were no pending
> toolchain issues related to this.
That is correct. The GCC maintainers at Arm confirm that
stack-clash-protection is supported on 32 bit too.
In case there are any bugs, whic
Hi!
On Thu, 2023-11-23 at 10:45:33 +0100, Matthias Klose wrote:
> it looks like enabling this flag on armel/armhf is a little bit premature.
>
> Apparently it's not completely supported upstream, and might cause
> regressions, according to
> https://bugzilla.redhat.com/show_bug.cgi?id=1522678
I
Hi,
it looks like enabling this flag on armel/armhf is a little bit premature.
Apparently it's not completely supported upstream, and might cause
regressions, according to
https://bugzilla.redhat.com/show_bug.cgi?id=1522678
Is that a feature that the Debian ARM32 porters and the security team
12 matches
Mail list logo