Bug#1003627: [Pkg-pascal-devel] Bug#1003627: fpc: autopkgtest regression on ppc64el:
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: 3.2.2+dfsg-5 > X-Debbugs-CC: debian...@lists.debian.org > Severity: serious > User: debian...@lists.debian.org > Usertags: regression > > Dear maintainer(s), > > With a recent upload of fpc the autopkgtest of fpc fails in testing > when > that autopkgtest is run with the binary packages of fpc from unstable > on > ppc64el. It passes when run with only packages from testing. In > tabular > form: > > passfail > fpcfrom testing3.2.2+dfsg-5 > all others from testingfrom testing > > I copied some of the output at the bottom of this report. > > Currently this regression is blocking the migration to testing [1]. > Can > you please investigate the situation and fix it? > > More information about this bug and the reason for filing it can be > found on > https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation > > Paul > > [1] https://qa.debian.org/excuses.php?package=fpc > > https://ci.debian.net/data/autopkgtest/testing/ppc64el/f/fpc/18260761/log.gz > > Total = 7734 (55:7679) > Total number of compilations = 4753 (17:4736) > Successfully compiled = 3605 > Successfully failed = 1131 > Compilation failures = 14 > Compilation that did not fail while they should = 3 > Total number of runs = 2981 (38:2943) > Successful runs = 2943 > Failed runs = 38 > Number units compiled = 152 > Number program that should not be run = 468 > Number of skipped tests = 632 > Number of skipped graph tests = 10 > Number of skipped interactive tests = 31 > Number of skipped known bug tests = 7 > Number of skipped tests for other versions = 5 > Number of skipped tests for other cpus = 397 > Number of skipped tests for other targets = 182 > make: Leaving directory > '/tmp/autopkgtest-lxc.ims6woux/downtmp/build.IH3/src/fpcsrc/tests' > Let's save some of the output > Compare the new results with known results if we have them > > Difference between expected failures and current failures: > --- debian/tests/ref_fail_powerpc64-linux 2021-12-30 > 13:48:26.0 > + > +++ fpcsrc/tests/output/powerpc64-linux/faillist 2022-01-12 > 08:26:51.116689429 + > @@ -39,6 +39,7 @@ > webtbs/tw3157 > webtbs/tw36179 > webtbs/tw36863 > +webtbs/tw36934a > webtbs/tw3930 > webtbs/tw3964b > webtbs/tw4809 > > Checking (and fail if so) for new failures: > Unexpected failures > autopkgtest [08:26:51]: test run-upstream-testsuite > > ___ > Pkg-pascal-devel mailing list > pkg-pascal-de...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-pascal-devel
Bug#997942: tomboy-ng: FTBFS with fpc 3.2.2
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 > issue OK, I have made this work. Instead of cherry picking just fpc and lazarus from Sid, I 'updated' my whole Testing (VM) install to Sid and that worked as expected. Tests all passed, I will push it up, as a new release (closing this ticket) as soon as I get a fresh Spanish translation. My translator is sometimes out of direct contact so not sure how long that will be. Davo
Bug#997942: tomboy-ng: FTBFS with fpc 3.2.2
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 issue about "diversions". So, falling back to using Testing's Lazarus, I find it insists on installing FPC3.2.0. It should not, Lazarus 2.0.10 is fine with FPC3.2.2, I just tested in on my system. So, that leaves me with a partially overwritten FPC3.2.2. Yes it built and makes a nice SRC package but I cannot be sure it has not used FPC3.2.0 components so the test is not absolute. So, I will have to wait until the Lazarus on Sid issue is resolved. And Lazarus 2.2.0 cannot be far way. It has a fix (I wrote) for the problem affecting Gnome Desktops caused when Debian dropped libappindicator3 in favour of libayatana-appindicator3 apparently without considering that 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. > > Its a > > very simple fix but as I am very close to releasing a new version > > anyway, maybe we can wait until them ? > > Sure, there's no reason to rush a fix now. Replying to this bug will > delay the pending autoremoval. > > On Sun, 7 Nov 2021 at 02:41, David Bannon > wrote: > > 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 ? > > Development of Debian takes place in unstable (aka sid), and if you > uploaded a new version of tomboy-ng to the archive, it would be built > against all of the packages in unstable. It is possible to install > individual packages from unstable on a testing system [1]. Take care > to set priorities [2] so that you don't end up with all of the > packages from unstable, unless you like living on the edge. > > I suggest subscribing to the Debian Pascal Packaging Team's mailing > list [3], to keep up to date with FPC and Lazarus packaging > developments. You are also welcome to join the team and you will > have > no shortage of sponsors for your uploads. > > Regards > Graham > > > [1] https://wiki.debian.org/DebianUnstable > [2] https://wiki.debian.org/AptConfiguration > [3] > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-pascal-devel
Bug#997942: tomboy-ng: FTBFS with fpc 3.2.2
Ahh, thanks Graham, On Mon, 2021-11-08 at 13:03 +0200, Graham Inggs wrote: > > > very simple fix but as I am very close to releasing a new version > > anyway, maybe we can wait until them ? > > Sure, there's no reason to rush a fix now. Replying to this bug will > delay 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 2021 at 02:41, David Bannon > > > that. How do I test my build against tools only available in sid ? > > > ...It is possible to install > individual packages from unstable on a testing system [1]. Indeed, I have just tried that, found it does what I need. I will build a Testing VM that can build packages, force sid's FPC (and maybe Lazarus) and test my build there. I expect it will be fine but will be happier if I can be sure. > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-pascal-devel OK, I have subscribed. I will find it interesting, if I can be useful, that would be good too. Davo
Bug#997942: tomboy-ng: FTBFS with fpc 3.2.2
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 built using Free Pascal Compiler and Lazarus. Testing has FPC3.2.0 but apparently sid has FPC3.2.2. Obviously, I can get (have already got) FPC direct from its source but I have found the need to test, for Debian, using Debian supplied tools. I obtained my Testing from https://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/, its dated 1st November. Should I be using something else ? My fix is trivial, my scripts (stupidly) includes a test that accepts only FPC 3.2.0. But I would prefer to update the release anyway, the version of tomboy- ng in Bullseye has issues that flowed from Debian's decision to drop libappindicator3 in favour of libayana (and, not surprisingly, they have different file names!). Davo 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 > > Hi Maintainer > > tomboy-ng fails to build from source since fpc 3.2.2 was uploaded to > unstable. I've copied what I hope is the relevant part of the log > below. > > Regards > Graham > > > make[1]: Entering directory '/build/1st/tomboy-ng-0.32' > == We have compiled [tomboy-ng] > == $BIN_DIR is [/usr/bin] > bash ./buildit.bash > /usr/bin/which: this version of `which' is deprecated; use `command > -v' in scripts instead. > /usr/bin/which: this version of `which' is deprecated; use `command > -v' in scripts instead. > Compiler reported [3.2.2] > Unclear about your compiler, maybe edit script to support new one, > exiting ... > make[1]: *** [Makefile:36: tomboy-ngx86_64] Error 1
Bug#997942: tomboy-ng: FTBFS with fpc 3.2.2
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 wait until them ? I am waiting on an upstream fix to kcontrols that appears to have some issues depending on locale. Due to Debian dropping libappindicator3 and replacing it with libayatana (and the name change), the current version of tomboy-ng in debian is not a good solution anyway. And the new one is bigger and better ! ;-) Davo > > Hi Maintainer > > tomboy-ng fails to build from source since fpc 3.2.2 was uploaded to > unstable. I've copied what I hope is the relevant part of the log > below. > > Regards > Graham > > > make[1]: Entering directory '/build/1st/tomboy-ng-0.32' > == We have compiled [tomboy-ng] > == $BIN_DIR is [/usr/bin] > bash ./buildit.bash > /usr/bin/which: this version of `which' is deprecated; use `command > -v' in scripts instead. > /usr/bin/which: this version of `which' is deprecated; use `command > -v' in scripts instead. > Compiler reported [3.2.2] > Unclear about your compiler, maybe edit script to support new one, > exiting ... > make[1]: *** [Makefile:36: tomboy-ngx86_64] Error 1
