On Mon, Sep 11, 2023 at 01:20:53AM +0300, Adrian Bunk wrote:
> Package: cmake
> Version: 3.26.4-4
> Severity: normal
> Tags: ftbfs
> X-Debbugs-Cc: debian-alpha@lists.debian.org
>
> Many (> 50) have been FTBFS on alpha recently due to
> cmake not finding libraries.
>.
Hi,
liburing is Not-For-Us on Alpha since 2022, and if I saw it correctly
imago was recently twice killed by bfs (which now uses io_uring).
Recent kernels do contain io_uring fixes (e.g. in 5.10.186),
which might or might not be related.
Blacklisting liburing and packages build depending on it
On Fri, Nov 24, 2023 at 01:53:04AM +0100, Guillem Jover wrote:
> Hi!
Hi Guillem!
Apologies for not replying to these emails earlier.
> On Tue, 2023-10-31 at 10:52:40 +0100, Guillem Jover wrote:
>...
> > If PIE (via specs files) appears to work on x32, and changing the
> > defaults in gcc is too
On Fri, Oct 20, 2023 at 07:03:41AM +0100, Julian Gilbey wrote:
> Hi!
>
> I'm completely out of my depth on this one, and I wonder whether
> anyone might be able to help.
>
> I have just updated pydevd from 2.9.6+ds-1, uploaded 2023-06-23, to
> version 2.10.0+ds-1. But the build of the cython
On Tue, Jul 04, 2023 at 09:23:43AM +0200, Guillem Jover wrote:
> On Sun, Jul 02, 2023 at 12:02:46AM +0300, Adrian Bunk wrote:
> >...
> > Linking a package with hardening=+all against a static library
> > from a package not using hardening=+all cannot work on the
>
On Fri, Sep 15, 2023 at 08:57:15PM +0200, Timo Röhling wrote:
> Hi Adrian,
Hi Timo,
thanks for taking a look (and sorry for the late reply).
> On Mon, 11 Sep 2023 01:20:53 +0300 Adrian Bunk wrote:
> > 1. The problem is about not finding a library,
> > it happens in many
Package: cmake
Version: 3.26.4-4
Severity: normal
Tags: ftbfs
X-Debbugs-Cc: debian-alpha@lists.debian.org
Many (> 50) have been FTBFS on alpha recently due to
cmake not finding libraries.
This bug is sent against cmake with Cc to the debian-alpha
list to document and track this issue.
On Mon, Jul 03, 2023 at 09:31:29PM +0200, Rene Engelhard wrote:
> Hi,
>
> Am 25.06.23 um 13:37 schrieb Rene Engelhard:
> > > what about the
> > > following:
> > > - make all test failures fatal on a*64 (since upstream tests these), and
> > > - make smoketest failures fatal on all architectures
On Tue, Jul 04, 2023 at 09:23:43AM +0200, Guillem Jover wrote:
> Hi!
Hi Guillem!
> On Sun, 2023-07-02 at 00:02:46 +0300, Adrian Bunk wrote:
>...
> > There are some problems with this:
> >
> > 1. PIE should either be default or not be used
> >
> > I susp
Package: dpkg-dev
Version: 1.21.22
Severity: normal
X-Debbugs-Cc: debian-alpha@lists.debian.org, debian-i...@lists.debian.org
[ Cc set to debian-alpha@ and debian-ia64@ since they are most affected ]
Since stretch all release architectures are using PIE by default,
and all future release
On Tue, Jun 20, 2023 at 05:52:44AM +0200, Rene Engelhard wrote:
> Hi,
>
> Am 19.06.23 um 23:29 schrieb Rene Engelhard:
> > > The pragmatic option would be to run only a smoketest for build success
> > > on architectures not tested by upstream.
> >
> > And have Format->Character in Impress crash
On Mon, Jun 19, 2023 at 11:29:34PM +0200, Rene Engelhard wrote:
>...
> Am 19.06.23 um 23:19 schrieb Adrian Bunk:
>...
> > For such a complex package I would expect 32bit breakage in every
> > release if upstream no longer tests on 32bit.
> Indeed, though at least for 32bit
On Sun, Jun 18, 2023 at 09:31:05AM +0200, Rene Engelhard wrote:
>...
> I won't be of much help here unfortunately, except
> maybe testing patches, but then again there's porterboxes
>...
You are the only one who could realistically debug many of these.
E.g. on armel it says:
Fatal exception:
On Sun, Dec 06, 2020 at 01:03:17PM +0100, Matthias Klose wrote:
> On 12/1/20 5:02 AM, YunQiang Su wrote:
> > I am sorry for the later response.
> >Hi,
> >
> > I am an active porter for the following architectures and I intend
> > to continue this for the lifetime of the Bullseye release
On Sun, Dec 06, 2020 at 01:03:17PM +0100, Matthias Klose wrote:
> On 12/1/20 5:02 AM, YunQiang Su wrote:
> > I am sorry for the later response.
> >Hi,
> >
> > I am an active porter for the following architectures and I intend
> > to continue this for the lifetime of the Bullseye release
On Thu, Nov 24, 2016 at 04:35:28PM +0100, Guillem Jover wrote:
>...
> On Thu, 2016-11-24 at 14:52:33 +, Thorsten Glaser wrote:
>...
> > Worse, they break *differently* on whether…
> >
> > >Precisely to make the behavior consistent on all architectures, dpkg
> > >enables PIE (conditionally if
[ fullquote adding -ports, for people not following -release or -devel ]
On Fri, Oct 07, 2016 at 06:35:07PM +0100, Jonathan Wiltshire wrote:
> Hi,
>
> I am arranging the final architecture qualification meeting for Stretch.
> This is primarily of interest to the release team, but I will also
On Wed, 14 Mar 2001, T. Weyergraf wrote:
...
Depending on what specific aspects of the machine's wordsize you need, you
can go as
straight as checking if __WORDSIZE is set to 32 or 64, or as controlled as
checking if
...
Thanks! That's exactly what I was looking for.
Regards,
Thomas
cu
Hi,
I'm lookking for my package tmview for a C solution to determine whether
an architecture is 32 or 64 bit.
The current code is:
-- snip --
#define BMLONG32 /* for architectures where long int has 32bits,
e.g. i386 */
/* #define BMLONG64 *//* for
19 matches
Mail list logo
