Bug#906349: doublecmd: FTBFS in buster/sid (tries to write in /usr)
Hi Graham, On Mon, 2018-09-24 at 20:48 +0200, Graham Inggs wrote: > Hi Abou > > On 23 September 2018 at 22:44, Abou Al Montacir > wrote: > > I've reverted this in b9ccece9. However this means that Bug#898310 needs to > > be reopen. > > Thanks, I have a reassigned #906349 so it can be closed when lazarus > is uploaded. > Shall I go ahead with an upload, or do you wish to make more changes? Please go ahead and upload. I don't really have time for the moment to fix it correctly. -- Cheers, Abou Al Montacir signature.asc Description: This is a digitally signed message part
Bug#906349: doublecmd: FTBFS in buster/sid (tries to write in /usr)
Hi Abou On 23 September 2018 at 22:44, Abou Al Montacir wrote: > I've reverted this in b9ccece9. However this means that Bug#898310 needs to > be reopen. Thanks, I have a reassigned #906349 so it can be closed when lazarus is uploaded. Shall I go ahead with an upload, or do you wish to make more changes? Regards Graham
Bug#906349: [Pkg-pascal-devel] Bug#906349: doublecmd: FTBFS in buster/sid (tries to write in /usr)
Hi Graham, On Fri, 2018-09-21 at 15:40 +0200, Graham Inggs wrote: > Hi Abou > > On 27/08/2018 18:03, Abou Al Montacir wrote: > > Maybe we shall think more about this change. Removing the manually flag > > leads to > > a deeper question: Do we need to distribute LCL units in binary form if they > > will get recompiled anyway? > > Have you had any time to consider this? > > Both doublecmd and ddrescueview have been removed from testing now. I've reverted this in b9ccece9. However this means that Bug#898310 needs to be reopen. -- Cheers, Abou Al Montacir signature.asc Description: This is a digitally signed message part
Bug#906349: doublecmd: FTBFS in buster/sid (tries to write in /usr)
Hi Abou On 27/08/2018 18:03, Abou Al Montacir wrote: Maybe we shall think more about this change. Removing the manually flag leads to a deeper question: Do we need to distribute LCL units in binary form if they will get recompiled anyway? Have you had any time to consider this? Both doublecmd and ddrescueview have been removed from testing now. Regards Graham
Bug#906349: [Pkg-pascal-devel] Bug#906349: Bug#906349: Bug#906349: doublecmd: FTBFS in buster/sid (tries to write in /usr)
Hi Graham, On Thu, 2018-08-23 at 15:33 +0200, Graham Inggs wrote: > Hi Abou > > On 17/08/2018 18:37, Graham Inggs wrote: > > Abou, do you have an opinion on whether this is a bug in lazarus, or > > does the doublecmd packaging need to be fixed? I just returned back from vacation, let me check this. > The same problem occurs in ddrescueview, reported in #906458. Seems strange > I found it was introduced by the changes to debian/rules in this commit > 'Stop adding manually compiled flag from packages' [1]. That one was proposed to solve a lazarus IDE rebuild issue. I don't like it as I tend to think that units shall be compiled only once and not every time. However the way upstream sees Lazarus distribution is the opposite. I don't see a better way to fix it. > Both doublecmd and ddrescueview build successfully if lazarus-src is > added as a build-dependency. This means that we are missing some PPU/LPK files to be distributed or maybe we are trying to recompile some units and missing some include files. One needs to add -va and look carefully to the log file. > Is this change in behaviour intentional? Somewhat as it was fixing bug#898310 > Should I make these changes to doublecmd and ddrescueview, or is this a > bug in lazarus? Maybe we shall think more about this change. Removing the manually flag leads to a deeper question: Do we need to distribute LCL units in binary form if they will get recompiled anyway? > Regards > Graham > > > [1] > https://salsa.debian.org/pascal-team/lazarus/commit/eb89bf37af1b42215811c132fd > fc919f19126952 -- Cheers, Abou Al Montacir signature.asc Description: This is a digitally signed message part
Bug#906349: [Pkg-pascal-devel] Bug#906349: Bug#906349: doublecmd: FTBFS in buster/sid (tries to write in /usr)
Hi Abou On 17/08/2018 18:37, Graham Inggs wrote: Abou, do you have an opinion on whether this is a bug in lazarus, or does the doublecmd packaging need to be fixed? The same problem occurs in ddrescueview, reported in #906458. I found it was introduced by the changes to debian/rules in this commit 'Stop adding manually compiled flag from packages' [1]. Both doublecmd and ddrescueview build successfully if lazarus-src is added as a build-dependency. Is this change in behaviour intentional? Should I make these changes to doublecmd and ddrescueview, or is this a bug in lazarus? Regards Graham [1] https://salsa.debian.org/pascal-team/lazarus/commit/eb89bf37af1b42215811c132fdfc919f19126952
Bug#906349: [Pkg-pascal-devel] Bug#906349: doublecmd: FTBFS in buster/sid (tries to write in /usr)
Hi Santiago, Abou On 17 August 2018 at 13:19, Santiago Vila wrote: > I tried to build this package in buster but it failed: Thanks for the report! According to reproducible builds, doublecmd started to FTBFS in unstable on 2018-07-20 [1]. This was shortly after the upload of lazarus 1.8.4+dfsg-2. > If this is really a bug in one of the build-depends, please use reassign and > affects, > so that this is still visible in the BTS web page for this package. Abou, do you have an opinion on whether this is a bug in lazarus, or does the doublecmd packaging need to be fixed? Regards Graham [1] https://tests.reproducible-builds.org/debian/history/amd64/doublecmd.html
Bug#906349: doublecmd: FTBFS in buster/sid (tries to write in /usr)
Package: src:doublecmd Version: 0.8.3-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep dh_update_autotools_config -i dh_autoreconf -i create-stamp debian/debhelper-build-stamp fakeroot debian/rules binary-indep dh binary-indep dh_testroot -i dh_prep -i debian/rules override_dh_install make[1]: Entering directory '/<>' cd language ;\ if [ -f doublecmd.po ] ; then mv doublecmd.po doublecmd.en.po; fi ; # Remove convenience copy of Free Pascal Qt4 binding, use libqt4pas-dev instead rm -f plugins/wlx/WlxMplayer/src/qt4.pas # Build GTK2 version ./build.sh beta gtk2 CopySecondaryConfigFile /etc/lazarus/environmentoptions.xml -> /<>/tmphome/.lazarus/environmentoptions.xml Hint: (lazarus) [RunTool] /usr/bin/fpc "-iWTOTP" Hint: (lazarus) [RunTool] /usr/bin/fpc "-va" "compilertest.pas" Hint: (lazarus) source file missing of FCL 1.0.1: /usr/lib/lazarus/1.8.4/packager/registration/fcllaz.pas Hint: (lazarus) normal output directory of package FCL 1.0.1 is not writable: "/usr/lib/lazarus/1.8.4/packager/units/x86_64-linux/" TParsedCompilerOptions.SetOutputDirectoryOverride New=/<>/tmphome/.lazarus/lib/units/x86_64-linux Hint: (lazarus) Missing state file of FCL 1.0.1: /<>/tmphome/.lazarus/lib/units/x86_64-linux/FCL.compiled $55CF30A72139 $55CF30816E3B $55CF30D8BA98 $55CF30A05BB1 $55CF309FD9E2 $55CF309FCF2B $55CF309FD67F $55CF3081878D $55CF3081778C $55CF308173CC $55CF3081CDF5 $55CF3081FA8F $55CF3081620D Error: (lazbuild) Write error Write error: Unable to create file "/usr/lib/lazarus/1.8.4/packager/registration/fcllaz.pas" File: /usr/lib/lazarus/1.8.4/packager/registration/fcllaz.pas package main source file lazbuild is non interactive, aborting now. make[1]: *** [debian/rules:16: override_dh_install] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:9: binary-indep] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess returned exit status 2 The build was made with "dpkg-buildpackage -A" in my autobuilder. Most probably, it also fails here in reproducible builds: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/doublecmd.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.