Bug#1003627: [Pkg-pascal-devel] Bug#1003627: fpc: autopkgtest regression on ppc64el:

2022-01-13 Thread David Bannon
I wonder if this relates to the hardening issue ? Hardening on PPC63le with FPC is not currently working, it makes a non viable binary. https://gitlab.com/freepascal.org/fpc/source/-/issues/39451 Davo On Wed, 2022-01-12 at 21:14 +0100, Paul Gevers wrote: > Source: fpc > Version:

Bug#997942: tomboy-ng: FTBFS with fpc 3.2.2

2021-11-10 Thread David Bannon
On Tue, 2021-11-09 at 22:56 +1100, David Bannon wrote: > No, sorry, I cannot do a sensible test of my app using FPC and/or > Lazarus from sid. > > I can install FPC3.2.2 from Sid by using priorities. > > But the Lazarus in Sid is non functional, blocked, because of an > i

Bug#997942: tomboy-ng: FTBFS with fpc 3.2.2

2021-11-09 Thread David Bannon
they have different names. Davo On Mon, 2021-11-08 at 13:03 +0200, Graham Inggs wrote: > Hi David > > Apologies for the delayed response. > > On Sat, 30 Oct 2021 at 06:57, David Bannon > wrote: > > Thanks Graham. I noticed the same problem myself a few days ago. > > It

Bug#997942: tomboy-ng: FTBFS with fpc 3.2.2

2021-11-08 Thread David Bannon
the pending autoremoval. Excellent. I may well be ready to act before the (25th) removal date anyway. The build test then wait for the Spanish translation... Philipp Huebner, my sponsor, tells me I can close this bug with an upload of the new version, so thats nice and tidy. > On Sun, 7 Nov

Bug#997942: tomboy-ng: FTBFS with fpc 3.2.2

2021-11-06 Thread David Bannon
I was advised a week ago that the app I maintain is not building in unstable as the compiler (fpc) has been updated. However, Testing still has the 'older' compiler and it builds fine with that. How do I test my build against tools only available in sid ? Background - --- tomboy-ng is

Bug#997942: tomboy-ng: FTBFS with fpc 3.2.2

2021-10-29 Thread David Bannon
On Wed, 2021-10-27 at 14:11 +0200, Graham Inggs wrote: > Source: tomboy-ng > Version: 0.32-2 > Severity: serious > Tags: ftbfs bookworm sid Thanks Graham. I noticed the same problem myself a few days ago. Its a very simple fix but as I am very close to releasing a new version anyway, maybe we can