From carles at pina.cat Mon Apr 20 22:05:08 2026 From: carles at pina.cat (Carles Pina i Estany) Date: Mon, 20 Apr 2026 21:05:08 +0000 Subject: [Pkg-pascal-devel] Bug#1134499: fp-units-multimedia-3.2.2: recommends libdts-dev which is not in unstable Message-ID: Subject: fp-units-multimedia-3.2.2: recommends libdts-dev which is not in unstable Package: fp-units-multimedia-3.2.2 Version: 3.2.2+dfsg-49 Usertags: package-relations package-relations-recommends Severity: wishlist Dear maintainer(s), I noticed that package fp-units-multimedia-3.2.2 recommends libdts-dev, which is currently not available in unstable. As far as I can say (because of 404 not found in https://tracker.debian.org/pkg/libdts-dev ): this package has never been in Debian. Because of https://www.ubuntuupdates.org/package/core/focal/universe/base/libdts-dev I think that perhaps it should be changed to libdca? Note that I am not familiar with these packages! Would it make sense to remove or update it? Thank you for your time, PS[0]: I am developing a tool to detect such issues: https://salsa.debian.org/carlespina/check-relations . Reports are manually reviewed before submission. If you would prefer not to receive such reports (for specific packages, all of your maintained packages, etc.), please let me know. Any other feedback is welcomed as well. PS[1]: more information available in https://salsa.debian.org/carlespina/check-relations/-/blob/main/README.md and https://salsa.debian.org/carlespina/check-relations/-/blob/main/docs/bug-report-extra-info.md -- Carles Pina i Estany https://carles.pina.cat | carles at pina.cat | cpina at debian.org -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From carles at pina.cat Mon Apr 20 22:08:48 2026 From: carles at pina.cat (Carles Pina i Estany) Date: Mon, 20 Apr 2026 21:08:48 +0000 Subject: [Pkg-pascal-devel] Bug#1134501: fp-units-win-multimedia-3.2.2: recommends libdts-dev which is not in unstable Message-ID: Subject: fp-units-win-multimedia-3.2.2: recommends libdts-dev which is not in unstable Package: fp-units-win-multimedia-3.2.2 Version: 3.2.2+dfsg-46 Usertags: package-relations package-relations-recommends Severity: wishlist Dear maintainer(s), I noticed that package fp-units-win-multimedia-3.2.2 recommends libdts-dev, which is currently not available in unstable. This is a similar case to #1134499 (so I will not repeat the explanation here). -- Carles Pina i Estany https://carles.pina.cat | carles at pina.cat | cpina at debian.org -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From fabstz-it at yahoo.fr Sat Apr 25 08:05:14 2026 From: fabstz-it at yahoo.fr (Fab Stz) Date: Sat, 25 Apr 2026 09:05:14 +0200 Subject: [Pkg-pascal-devel] wattsi - how to fix lintian error "statically-linked-binary" In-Reply-To: <2343366.VsPgYW4pTa@debian> References: <2343366.VsPgYW4pTa@debian> Message-ID: <3839748.cLl3JjQhRp@debian> Hello, Could someone of the pascal team please answer to my packaging question below? Regards Fab Le dimanche 12 avril 2026, 11:51:16 heure d??t? d?Europe centrale Fab Stz a ?crit : > Dear team, > > I'm trying to package "wattsi" but lintian complains that the binary is statically linked: > > E: wattsi: statically-linked-binary [usr/bin/wattsi] > > I'm struggling at making it dynamically linked. > > I've also seen that a few packages that are already in the archive have this error and have been accepted: > https://udd.debian.org/lintian/?email1=&email2=&email3=&packages=&all_packages=on&ignpackages=&format=html<_error=on<_warning=on&lintian_tag=statically-linked-binary#all > > Any clue? Is this something well known for pascal based sources? Can it pass NEW even with this "statically-linked-binary" error? > > Repo: https://salsa.debian.org/bastif/wattsi/ > > Please keep me in copy of your reply. > > BTW, if you believe the package is in good shape, would you sponsor it? > > Regards > Fab From elbrus at debian.org Sat Apr 25 13:15:14 2026 From: elbrus at debian.org (Paul Gevers) Date: Sat, 25 Apr 2026 14:15:14 +0200 Subject: [Pkg-pascal-devel] wattsi - how to fix lintian error "statically-linked-binary" In-Reply-To: <3839748.cLl3JjQhRp@debian> References: <2343366.VsPgYW4pTa@debian> <3839748.cLl3JjQhRp@debian> Message-ID: Hi Fab, On 4/25/26 09:05, Fab Stz wrote: > Le dimanche 12 avril 2026, 11:51:16 heure d??t? d?Europe centrale Fab Stz a ?crit : >> I'm struggling at making it dynamically linked. >> Any clue? Is this something well known for pascal based sources? Can it pass NEW even with this "statically-linked-binary" error? fpc and pasdoc are also showing these messages. I recall having looked into it a long time and I remember in the FreePascal world linking dynamically isn't (or wasn't) trivial. I've seen hints it might be better now, but haven't looked at FreePascal for a while now. Paul -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 585 bytes Desc: OpenPGP digital signature URL: From elbrus at debian.org Sat Apr 25 13:17:05 2026 From: elbrus at debian.org (Paul Gevers) Date: Sat, 25 Apr 2026 14:17:05 +0200 Subject: [Pkg-pascal-devel] wattsi - how to fix lintian error "statically-linked-binary" In-Reply-To: References: <2343366.VsPgYW4pTa@debian> <3839748.cLl3JjQhRp@debian> Message-ID: <3c445d90-353d-45f3-9eac-d35bea6b8560@debian.org> Hi On 4/25/26 14:15, Paul Gevers wrote: > fpc and pasdoc are also showing these messages. I recall having looked > into it a long time and I remember in the FreePascal world linking > dynamically isn't (or wasn't) trivial. I've seen hints it might be > better now, but haven't looked at FreePascal for a while now. And this discussion might be very relevant: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069256#35 Paul -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 585 bytes Desc: OpenPGP digital signature URL: From peter at pblackman.plus.com Sat Apr 25 14:53:56 2026 From: peter at pblackman.plus.com (Peter Blackman) Date: Sat, 25 Apr 2026 14:53:56 +0100 Subject: [Pkg-pascal-devel] wattsi - how to fix lintian error "statically-linked-binary" In-Reply-To: <3839748.cLl3JjQhRp@debian> References: <2343366.VsPgYW4pTa@debian> <3839748.cLl3JjQhRp@debian> Message-ID: On 25/04/2026 08:05, Fab Stz wrote: > Hello, > > Could someone of the pascal team please answer to my packaging question below? > > Regards > Fab > > Le dimanche 12 avril 2026, 11:51:16 heure d??t? d?Europe centrale Fab Stz a ?crit : >> Dear team, >> >> I'm trying to package "wattsi" but lintian complains that the binary is statically linked: >> >> E: wattsi: statically-linked-binary [usr/bin/wattsi] >> >> I'm struggling at making it dynamically linked. >> Hi Fab, The build log from your Salsa pipeline contains several lines such as "settings.inc(43,4) Note: DWARF debug information cannot be used with smart linking on this target, switching to static linking" Does smart linking really make a significant difference to the exe size? If not, suggest drop it. (I fixed a similar issue on one of my packages by switching debug info to -gw4) Regards, Peter From peter at pblackman.plus.com Sat Apr 25 14:53:56 2026 From: peter at pblackman.plus.com (Peter Blackman) Date: Sat, 25 Apr 2026 14:53:56 +0100 Subject: [Pkg-pascal-devel] wattsi - how to fix lintian error "statically-linked-binary" In-Reply-To: <3839748.cLl3JjQhRp@debian> References: <2343366.VsPgYW4pTa@debian> <3839748.cLl3JjQhRp@debian> Message-ID: On 25/04/2026 08:05, Fab Stz wrote: > Hello, > > Could someone of the pascal team please answer to my packaging question below? > > Regards > Fab > > Le dimanche 12 avril 2026, 11:51:16 heure d??t? d?Europe centrale Fab Stz a ?crit : >> Dear team, >> >> I'm trying to package "wattsi" but lintian complains that the binary is statically linked: >> >> E: wattsi: statically-linked-binary [usr/bin/wattsi] >> >> I'm struggling at making it dynamically linked. >> Hi Fab, The build log from your Salsa pipeline contains several lines such as "settings.inc(43,4) Note: DWARF debug information cannot be used with smart linking on this target, switching to static linking" Does smart linking really make a significant difference to the exe size? If not, suggest drop it. (I fixed a similar issue on one of my packages by switching debug info to -gw4) Regards, Peter From peter at pblackman.plus.com Sat Apr 25 15:02:58 2026 From: peter at pblackman.plus.com (Peter Blackman) Date: Sat, 25 Apr 2026 15:02:58 +0100 Subject: [Pkg-pascal-devel] wattsi - how to fix lintian error "statically-linked-binary" In-Reply-To: <3839748.cLl3JjQhRp@debian> References: <2343366.VsPgYW4pTa@debian> <3839748.cLl3JjQhRp@debian> Message-ID: On 25/04/2026 08:05, Fab Stz wrote: >> >> BTW, if you believe the package is in good shape, would you sponsor it? >> I suggest upload the package to Mentors and raise an RFS. https://mentors.debian.net/sponsors/rfs-howto/ From peter at pblackman.plus.com Sat Apr 25 15:02:58 2026 From: peter at pblackman.plus.com (Peter Blackman) Date: Sat, 25 Apr 2026 15:02:58 +0100 Subject: [Pkg-pascal-devel] wattsi - how to fix lintian error "statically-linked-binary" In-Reply-To: <3839748.cLl3JjQhRp@debian> References: <2343366.VsPgYW4pTa@debian> <3839748.cLl3JjQhRp@debian> Message-ID: On 25/04/2026 08:05, Fab Stz wrote: >> >> BTW, if you believe the package is in good shape, would you sponsor it? >> I suggest upload the package to Mentors and raise an RFS. https://mentors.debian.net/sponsors/rfs-howto/ From fabstz-it at yahoo.fr Sat Apr 25 16:56:23 2026 From: fabstz-it at yahoo.fr (Fab Stz) Date: Sat, 25 Apr 2026 17:56:23 +0200 Subject: [Pkg-pascal-devel] wattsi - how to fix lintian error "statically-linked-binary" In-Reply-To: References: <2343366.VsPgYW4pTa@debian> <3839748.cLl3JjQhRp@debian> Message-ID: <5470034.a9HWlOh95j@debian> Hi Paul & Peter, Thanks for your replies. Le samedi 25 avril 2026, 16:02:58 heure d??t? d?Europe centrale Peter Blackman a ?crit : > On 25/04/2026 08:05, Fab Stz wrote: > > >> > >> BTW, if you believe the package is in good shape, would you sponsor it? > >> > > > I suggest upload the package to Mentors and raise an RFS. > https://mentors.debian.net/sponsors/rfs-howto/ Actually, almost none of my packages (if there was even one) got sponsored through mentors, so I abandoned this strategy a long time ago. Direct contact of the relevant teams worked actually much better for me. I'll have a look at your suggestion. Until now, I tried a lot of approaches and none worked. Since I have no knowledge on pascal I asked for AI assistance without more success. Whenever I change any argument, there is another problem that arises, and the way the package is built upstream is very strange (mutliple passes, maybe for optimization purposes?). I fear there is no way to get around that static linking for pascal packages given that other pascal packages have that as well. Regards Fab From fabstz-it at yahoo.fr Sat Apr 25 16:56:23 2026 From: fabstz-it at yahoo.fr (Fab Stz) Date: Sat, 25 Apr 2026 17:56:23 +0200 Subject: [Pkg-pascal-devel] wattsi - how to fix lintian error "statically-linked-binary" In-Reply-To: References: <2343366.VsPgYW4pTa@debian> <3839748.cLl3JjQhRp@debian> Message-ID: <5470034.a9HWlOh95j@debian> Hi Paul & Peter, Thanks for your replies. Le samedi 25 avril 2026, 16:02:58 heure d??t? d?Europe centrale Peter Blackman a ?crit : > On 25/04/2026 08:05, Fab Stz wrote: > > >> > >> BTW, if you believe the package is in good shape, would you sponsor it? > >> > > > I suggest upload the package to Mentors and raise an RFS. > https://mentors.debian.net/sponsors/rfs-howto/ Actually, almost none of my packages (if there was even one) got sponsored through mentors, so I abandoned this strategy a long time ago. Direct contact of the relevant teams worked actually much better for me. I'll have a look at your suggestion. Until now, I tried a lot of approaches and none worked. Since I have no knowledge on pascal I asked for AI assistance without more success. Whenever I change any argument, there is another problem that arises, and the way the package is built upstream is very strange (mutliple passes, maybe for optimization purposes?). I fear there is no way to get around that static linking for pascal packages given that other pascal packages have that as well. Regards Fab From fabstz-it at yahoo.fr Sun Apr 26 08:31:07 2026 From: fabstz-it at yahoo.fr (Fab Stz) Date: Sun, 26 Apr 2026 09:31:07 +0200 Subject: [Pkg-pascal-devel] wattsi - how to fix lintian error "statically-linked-binary" In-Reply-To: References: <2343366.VsPgYW4pTa@debian> <3839748.cLl3JjQhRp@debian> Message-ID: <5887591.tWeucmBOSa@debian> Dear Peter, > The build log from your Salsa pipeline contains several lines such as > > "settings.inc(43,4) Note: DWARF debug information cannot be used with smart linking on this target, switching to static linking" > > > Does smart linking really make a significant difference to the exe size? > If not, suggest drop it. With "-XX" (smart linking), size is 2.6M (1.3M after strip) Without it size is 4.1M (2.1M after strip) With "-XD" (dynamic linking), size is 4.1M (2.1M after strip), but the binary is still not dynamically linked. Same when using "-XD -Xc" Would you consider that a significant change in binary size justifying to keep smart linking enabled? As per the "stacially linked" issue: With "-XD -k-shared", or "-XD -k-shared -k-Bdynamic" build fails: Executing "/usr/bin/ld.bfd" with command line "-b elf64-x86-64 -m elf_x86_64 -shared -L. -o ../bin/wattsi -T ../bin/link837833.res -e _start" /usr/bin/x86_64-linux-gnu-ld.bfd: ../bin/../bin/wattsi.o: relocation R_X86_64_32S against symbol `RTTI_$P$WATTSI_$$_def0000007A' can not be used when making a shared object; recompile with -fPIC /usr/bin/x86_64-linux-gnu-ld.bfd: failed to set dynamic section sizes: bad value Same as above, but with "-fPIC" -> "-XD -k-shared -k-Bdynamic -fPIC" also fails, but because of a external resource Executing "/usr/bin/ld.bfd" with command line "-b elf64-x86-64 -m elf_x86_64 -shared -Bdynamic -L. -o ../bin/wattsi -T ../bin/link837979.res -e _start" /usr/bin/x86_64-linux-gnu-ld.bfd: /usr/lib/x86_64-linux-gnu/fpc/3.2.2/units/x86_64-linux/rtl/si_prc.o: warning: relocation against `SI_PRC_$$__FPC_PROC_START' in read-only section `.text.n_si_prc_$$__fpc_dynamic_proc_start' /usr/bin/x86_64-linux-gnu-ld.bfd: /usr/lib/x86_64-linux-gnu/fpc/3.2.2/units/x86_64-linux/rtl/si_prc.o: relocation R_X86_64_PC32 against symbol `FPC_SysEntry' can not be used when making a shared object; recompile with -fPIC /usr/bin/x86_64-linux-gnu-ld.bfd: final link failed: bad value With "-XD -k-shared -k-Bsymbolic" it is dynamically linked accoring to `file wattsi`, but statically linked according to `ldd wattsi`. Also, wattsi segfaults at invocation... My feeling when I see "/usr/lib/x86_64-linux-gnu/fpc/3.2.2/units/x86_64-linux/rtl/si_prc.o" is that there is now way to avoid that "statically-linked-binary" "issue". > (I fixed a similar issue on one of my packages by switching debug info to -gw4) Thanks! That permitted to remove that DWARF notice. The repo now includes that change. Fab From peter at pblackman.plus.com Sun Apr 26 22:50:36 2026 From: peter at pblackman.plus.com (Peter Blackman) Date: Sun, 26 Apr 2026 22:50:36 +0100 Subject: [Pkg-pascal-devel] lcl-4.4: recommends lazarus-src-4.4 which is not in unstable In-Reply-To: References: Message-ID: <7ac35f72-ff23-4ce2-9af2-9e1279d2f0fe@pblackman.plus.com> On 26/04/2026 22:29, Carles Pina i Estany wrote: > > Subject: lcl-4.4: recommends lazarus-src-4.4 which is not in unstable > Package: lcl-4.4 > Version: 4.4+dfsg-4 > Usertags: package-relations package-relations-recommends > Severity: wishlist > > Dear maintainer(s), > > I noticed that package lcl-4.4 recommends lazarus-src-4.4, which is > currently not available in unstable. Package lcl-4.4 is not (any more) in unstable either! > > I see the binary packages lazarus-src and lazarus-src-4.6. Perhaps one > of that should be recommended instead? **!!? If you would prefer not to receive > such reports (for specific packages, all of your maintained packages, > etc.), please let me know.> Prefer to opt out thank-you. Any other feedback is welcomed as well. Please use reportbug, and check that packages are actually still in unstable before filing bugs against them. Cheers, Peter B P.S. Please close this "bug".