Bug#1022343: [Pkg-pascal-devel] Bug#1022343: view3dscene: FTBFS: view3dscene.lpr(63, 17) Fatal: Can't find unit CastleCubeMaps used by view3dscene

2022-10-23 Thread Michalis Kamburelis
The new CGE (Castle Game Engine) indeed broke compatibility in this regard: the unit has been renamed CastleCubeMaps->CastleInternalCubeMaps . There are likely other small incompatibilities -- view3dscene in general "exercises" a lot of obscure CGE API (where we don't care much about backward

Bug#954676: [Pkg-pascal-devel] Bug#954676: pasdoc: FTBFS: dh_installman: error: Could not determine section for ./pasdoc.1

2020-03-30 Thread Michalis Kamburelis
Paul Gevers napisaƂ(a): > > Hi Michalis, > > On 30-03-2020 14:11, Michalis Kamburelis wrote: > > Do we know what the message "Could not determine section for" means, > > or how to investigate it? I mean, this manpage should go to section 1 > > (&

Bug#954676: [Pkg-pascal-devel] Bug#954676: pasdoc: FTBFS: dh_installman: error: Could not determine section for ./pasdoc.1

2020-03-30 Thread Michalis Kamburelis
The PasDoc manpage in Debian is done using help2man --output=pasdoc.1 --name="documentation tool for Pascal source code" \ --no-info bin/pasdoc Do we know what the message "Could not determine section for" means, or how to investigate it? I mean, this manpage should go to section 1 ("User

Bug#887967: [Pkg-pascal-devel] Bug#887967 closed by Abou Al Montacir <abou.almonta...@sfr.fr> (Bug#887967: fixed in fpc 3.0.4+dfsg-14)

2018-03-07 Thread Michalis Kamburelis
"2018-03-07 16:46 GMT+01:00 Graham Inggs : > On Tue, 23 Jan 2018 08:46:09 +0200 Adrian Bunk wrote: >> >> This problem is unfortunately still present with fpc 3.0.4+dfsg-14: >> >> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/transgui.html >

Bug#887575: [Pkg-pascal-devel] Bug#887575: Bug#887575: Bug#887575: Bug#887575: castle-game-engine FTBFS with fpc 3.0.4

2018-01-19 Thread Michalis Kamburelis
2018-01-19 9:23 GMT+01:00 Abou Al Montacir : > To be clear: It's not just a matter of having correct /etc/fpc.cfg -- > the fpmake also needs to know the root location of FPC units. (You > would have to ask fpmake authors why they did it like this.) But that > is why we have

Bug#887575: [Pkg-pascal-devel] Bug#887575: Bug#887575: Bug#887575: castle-game-engine FTBFS with fpc 3.0.4

2018-01-18 Thread Michalis Kamburelis
2018-01-18 20:56 GMT+01:00 Michalis Kamburelis <michalis.ka...@gmail.com>: > So, we should get to the point where CGE (or any other package > using fpmake) can be compiled by simple > > ~~~ > unset FPCDIR > fpc fpmake.pp > ./fpmake # without any additional options like

Bug#887575: [Pkg-pascal-devel] Bug#887575: Bug#887575: castle-game-engine FTBFS with fpc 3.0.4

2018-01-18 Thread Michalis Kamburelis
2018-01-18 14:44 GMT+01:00 Abou Al Montacir : > Doing > > ./fpmake --globalunitdir="/usr/lib/fpc/3.0.4" > > Why do we need this? FPC should use the /etc/fpc.cfg to get this, why do we > need to explicitly pass this? > Hi Abou, I think you're very right here -- the

Bug#887575: castle-game-engine FTBFS with fpc 3.0.4

2018-01-17 Thread Michalis Kamburelis
The problem is caused by the different directories used by new FPC 3.0.4 packages (compared to previous versions of FPC in Debian). Doing ./fpmake --globalunitdir="/usr/lib/fpc/3.0.4" doesn't work, since /usr/lib/fpc/3.0.4 does not exist. This works: ./fpmake

Bug#813718: Patch in the MRIcron FTBFS bug

2017-01-14 Thread Michalis Kamburelis
2017-01-14 16:54 GMT+01:00 Andreas Tille : > Hi Adrian, > > On Fri, Jan 13, 2017 at 05:29:01PM +0200, Adrian Bunk wrote: >> I saw you were just working on the MRIcron package. >> >> Can you take a look at the patch in >>

Bug#820708: CGE and view3dscene tested with libpng 1.6

2016-04-16 Thread Michalis Kamburelis
Hi, Quick test showed that Castle Game Engine and view3dscene work OK with libpng 1.6. Various testing images (with colors encoded in different ways), as well as deliberately wrong images, are handled correctly. Tested with libpng16-16 in current Debian testing (1.6.21-2). The necessary change

Bug#820708: [Pkg-pascal-devel] Bug#820708: castle-game-engine: hardcoded libpng12 dependency

2016-04-11 Thread Michalis Kamburelis
> Source: castle-game-engine > Version: 5.2.0-2 > Severity: serious > Justification: libpng1.6 transition > > Dear maintainer, > > in the discussion in #820566 it surfaced that castle-game-engine has a > hardcoded > dependency on libpng12. > > After the completion of the tlibpng 1.6 transition,

Bug#820566: [Pkg-pascal-devel] Bug#820566: Bug#820566: view3dscene: please stop depending on libpng12-0

2016-04-11 Thread Michalis Kamburelis
> @Michalis, does view3dscene work with libpng16, or do you first need to > port view3dscene to that API? If so, we better just drop the dependency > for now. Hi, I'm not sure what is the dependency ldd detects. It seems that something (possibly some unit inside FPC RTL?) uses the PNG unit

Bug#813718: [Pkg-pascal-devel] Bug#813718: mricron: FTBFS: dialogsx.pas(77, 14) Error: (4054) Illegal type conversion: "TMsgDlgButtons" to "TMsgDlgButtons"

2016-02-06 Thread Michalis Kamburelis
> Short story: the patch is attached, it should help:) Better take this patch version (spaces, not tabs:). Michalis --- common/dialogsx.pas.orig 2016-02-06 15:20:36.0 +0100 +++ common/dialogsx.pas 2016-02-06 15:43:30.0 +0100 @@ -66,6 +66,36 @@ end; {$ENDIF} +{ Convert our

Bug#813718: [Pkg-pascal-devel] Bug#813718: mricron: FTBFS: dialogsx.pas(77, 14) Error: (4054) Illegal type conversion: "TMsgDlgButtons" to "TMsgDlgButtons"

2016-02-06 Thread Michalis Kamburelis
> I can't see where the dialogs unit is getting the TMsgDlgButtons method > or function or procedure or whatever it is called in Pascal from. Short story: the patch is attached, it should help:) Longer explanation: 1. TMsgDlgButtons is a "type". It's a set (which is like a type-safe bitfield in

Bug#806488: [Pkg-pascal-devel] Bug#806488: view3dscene: FTBFS: v3dsceneraytrace.pas Error: Identifier not found "TImageFormat"

2015-11-28 Thread Michalis Kamburelis
Paul Gevers wrote: > This makes me wonder, does fpc have any reasonable symbols > tracking mechanism? I guess it does (at least in ppu files), so > should we extend the Debian tooling dh_makeshlibs/dh_shlibsdeps to > be able to handle the fpc situation? ppu files indeed hold the 100% information

Bug#806488: [Pkg-pascal-devel] Bug#806488: view3dscene: FTBFS: v3dsceneraytrace.pas Error: Identifier not found "TImageFormat"

2015-11-27 Thread Michalis Kamburelis
Chris West (Faux) wrote: > mkdir -p /view3dscene-3.15.0/debian/tmp/usr/lib/view3dscene/3.15.0 > fpc -k"-z relro" -dRELEASE -Mobjfpc -Sh -Ci -Sm -Sc -Sg -Si -O2 -Xs > -FU/view3dscene-3.15.0/debian/tmp/usr/lib/view3dscene/3.15.0 > -FE/view3dscene-3.15.0/debian/tmp/usr/bin >

Bug#750340: Recompilation of CastleStringUtils

2014-06-07 Thread Michalis Kamburelis
In case of recursive unit dependencies, FPC sometimes wants to recompile the units even though nothing changed. See e.g. http://bugs.freepascal.org/view.php?id=12223 . Possibly this is the reason of problems mentioned here. As Castle Game Engine sources are not available anymore (only the

Bug#578212: docbookwiki: Function named GoTo conflicts with PHP 5.3

2010-04-17 Thread Michalis Kamburelis
Package: docbookwiki Version: 0.9.1cvs-12 Severity: grave Justification: renders package unusable DocBookWiki uses php function named GoTo (defined in /usr/share/docbookwiki/web_app/class.WebApp.php line 125, used all over the place). This is a problem, since php 5.3 introduces goto construct