- Package:
- fp-units-rtl
- Source:
- fpc
- Description:
- Free Pascal - runtime libraries dependency package
- Submitter:
- Adrian Bunk
- Date:
- 2025-01-19 00:00:02 UTC
- Severity:
- important
- Tags:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/winff.html ... (10028) Recompiling Interfaces, checksum changed for /usr/lib/x86_64-linux-gnu/fpc/3.2.2/units/x86_64-linux/rtl/system.ppu /build/1st/winff-1.5.5/winff.lpr(26,3) Fatal: (10022) Can't find unit Interfaces used by winff Fatal: (1018) Compilation aborted Error: /usr/bin/ppcx64 returned an error exitcode Error: (lazarus) Compile Project, Target: winff: stopped with exit code 1 Error: (lazbuild) failed compiling of project /build/1st/winff-1.5.5/winff.lpi make[1]: *** [debian/rules:16: override_dh_auto_build-arch] Error 2
Hi, A retry worked. It seems to me that the failure was due to lazarus not having been rebuild against the latest fpc in the archive. But in Debian I'd expect package relations to embed the knowledge to prevent this from happening. Similar to the discussion in bug 997940 about src:castle-game-engine. Paul
Hi Paul More exactly, because the installed lcl-units-* were not build using the installed FPC. This is generally the case except when FPC get upgraded to a new version, which is generally a transitory situation for a very short time. It is not exactly the same. Lazarus is an IDE + framework (LCL). The IDE itself can work with whatever FPC version and with many LCL versions. So in principle, one can install the IDE and have a custom FPC + LCL. One problem here is that the LCL is packaged with the IDE, and this is a issue from upstream not separating the IDE development from the framework development. I don't like the idea to enforce the dependency because in principle, the same instance of Lazarus IDE can work with FPC-2.2.0 and FPC-2.2.2 which allows a developer to have time to migrate his application broken by a FPC or LCL upgrade wile using the last IDE. I personally use this feature for a SW that is tightly linked to LCL and thus using a new Lazarus with an old LCL until upgrade is done.
Hi Abou, I forgot how we do that then, but how do we guarantee that the period is short? Does it show up on the Release Team transition trackers [1] somehow? Or do we have to always remember to ask for a rebuild of lazarus ourselves (if we don't have a reason to upload a new version of lazarus)? Paul [1] https://release.debian.org/transitions/
Hi Paul, I'm not very familiar with transitions, but we used to ask for a rebuild of Lazarus and other libs (CGE, ...) if this happens. Of course if we can make this automatic, then this is even better. Do you have any idea in mind?
Hi All, After thinking more about this issue, I don't consider this a valid bug against Lazarus. The real issue is that FPC does not have a mean, today, to automatically trigger a rebuild of all source packages that supply units. This is the same for CGE, and other Pascal libraries. So I'm closing this ticket and will open a ticket for FPC to force rebuilding Pascal libraries.
Control: reassign -1 fp-units-rtl
The build of winff depends on lc-utils which depend on fpc-abi-3.2 that is a virtual package provided by fp-units-rtl-3.2 (3.2.0) As I can not access the build log anymore, I can only make suppositions. And I suppose that what happened at that time was that fp-units-rtl-3.2 was pulled as 3.2.2 due to the the compiler itself was pulled as fp-compiler-3.2 (3.2.2) and the compiler have a strict dependency (= 3.2.2) on the rtl packages. So, even if what happened was not the above supposition, we see that the fpc-abi is not carrying enough information on the version. I would recommend that it gets an additional digit or two to solve this issue and other similar issues. I would recommend then to make the fpc-abi be fpc-abi-3.2.2 for now, and if happen to patch RTL units so that we change interface, then we use fpc-abi- 3.2.2-n with n: Integer > 0. What do you think?
Let's assume any FP unit is shipped in a package named fp-units-some-package- name. Let's assume package fp-units-foo was changed and uploaded to unstable. Let's assume package fp-units-bar depends directly or indirectly on fp-units- foo, then fp-units-bar needs to be rebuilt after every upload of fp-units-foo that changes interfaces checksum stored in the ppu files. By depends directly we mean: fp-units-bar has fp-units-foo in its Build-Depends stanza. By depends indirectly we mean: fp-units-bar has a package that depends directly or indirectly on fp-units-bar. Please note that if fp-units-bar build depends on fp-units-foo, then it is likely that it will depend on it, unless fp-units-bar is build together with other set of fp-units-* packages that depend on fp-units-foo (like the case of Lazarus and FPC fp-units-* packages). So now we need to implement this logic in a script that can be used by the release team or whatever bot that can trigger automatic rebuilds of fp-units-* packages. For sake of simplicity, we ca assume that any new upload of fp-units-foo will break the interface which will cause higher load on building, but simpler logic to be implemented.
Hi Abou, The Release Team has tools in place to notify them if rebuilds are needed by looking at upper limits of Depends that are no longer satisfied. They show up as "auto-upperlimit-<pkg>" on the transitions page [1]. If that <pkg> has "abi" in the name, it will be clear that a rebuild is needed. All the rebuilds are manually scheduled, but that's OK. As long as the Release Team is aware via such a mechanism, it will be taken care of. The other auto-<pkg> items show up if a binary package disappears from the library section of the archive and another one shows up. This is how c transitions happen, because it's near required that a library binary package matches its SONAME, so when that's bumped (indicating a transition) the package name has to be updated too. Maybe we should move the fp-units-$bar packages to the library section too and embed the ABI version into the package name. Paul [1] https://release.debian.org/transitions/
Hi Paul, I like that idea. Let's go that way. For FPC, libraries are already carrying the ABI in their names. We only need to change them from section devel to section lib, but maybe we can convince release team to change a bit their script and check also for fp-units-* pattern in section devel. I don't think fp-unit-* make sense in the lib section. For Lazarus, it used to be that way too, but was simplified to carry the upstream main version. We may revert to old way or implement a new and better way to do that. -- Cheers, Abou Al Montacir
Hi Paul, I went again though this ticket and changed a bit my mind ... I think that the best place for fp-units-*is libdevel as they are very similar to the foo-dev packages. what do you think? Will this solve the issue with regards to the release team script, or it handle only lib section in that particular way?
Hi Abou, Ack. The Release Team scripts don't care about the section, they look at installability. But if we compare the units to C libraries, we normally asks library maintainers to *not* version the dev packages, because then all reverse build dependencies need an update when the SONAME gets bumped, making the transition process very labor-some. What we want to achieve here is a way to ensure packages are rebuild (semi) automatically when the units require it. But we *also* want to come up with a way that doesn't require changes in the reverse dependencies at the same time. Consider also that adding new binary packages require a trip through NEW. Would it make sense that every unit provides a virtual abi package, which get embedded in the dependencies during build time, such that when a unit bumps the virtual abi, the release team tools notice and rebuilds can be triggered? Or is that what we already more or less do? Paul
Hi Paul, We already have fpc-abi-x.y.z that handle this. However the problem of fpc-abi-* is that it does not carry a patch indicator. So one way to fix this is that if we change any interface, we should bump its version. Today we define it as fpc-abi-3.2.2. We can add a number like fpc-abi-3.2.2+p1, +p2, ... This way each time we change an interface of any unit we bump the patch number. However, this will solve only the problem for FPC, but not for LCL or any other units supplied by other projects (like CGE). So maybe the solution would be to make the units dependency strict. I meant id fp-units-foo build depends on fp-unit-bar then it should depend on it strictly. And any rebuild of fp-units-bar shall trigger rebuild of fp-units-foo.
Hi, This sounds very aggressive as I think most of the time it's unneeded. As a release manager I prefer an *almost* good situation over a much overly strict situation. Maybe autopkgtests can help? If we block migration in situation where the rebuild should have happened, we're good. Paul
Setting the 'Static-Built-Using' field in the control files of packages built with fpc should fix this. Cheers, Peter
Control: reassign -1 winff Control: retitle -1 Winff should declare Static-Built-Using in debian/control file As per the agreement about using 'Static-Built-Using' field by packages compiling with FPC, I reassign this ticket to winff so that maintainer can add the field and close this ticket.
Hi, 1) don't other packages need this too? Stuff from src:lazarus and src:castle-game-engine? 2) this doesn't automatically show up on the Release Team radar, so this still doesn't trigger rebuilds when needed (it does mean that the package gets rebuild before a Debian release, but that's not enough). Paul
Oops, I meant to update my comment on that after further investigation!
I had assumed incorrectly, that use of the 'Static-Built-Using' field
would achieve the automatic rebuilds we were looking for.
However, on drilling into the detail of #1069256 [1]
I find
"including an "exactly equal" ("=") version
relation on the version that was used to build"
ISTM that the "exactly equal" version equality of the dependency cannot
itself cause the package
to be rebuilt, as the package will now FTBFS because the exact version
of the dependency will no longer be available.
The package will need updating to change the dependency version.
Slightly more work than just
a rebuild, and manual intervention is still needed.
While I can now see this bug was originally against winff (it was
against FPC when I commented)
surely the underlying issue of checksums was due to fpc being updated
without a rebuild of Lazarus?
Does any know for sure what causes these checksums to change?
(The latest debian version of fpc does not seem to cause a problem))
Cheers,
Peter
[1][ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069256
Hi, The version should be calculated during the build, such that a rebuild will update it and it will always be in sync. This is a field of a binary, not of the source. (It's not a Depends, it's a new field). That would be a PITA and wrong. I think so. fp-fix-timestamps (which is a Debian helper to get reproducible FreePascal packages in Debian, even if we patch upstream source) is made to ease it a bit. https://wiki.debian.org/ReproducibleBuilds/TimestampsInPPUGeneratedByFP has more info. Paul
Hi so the package name only goes into the source, and then the package name plus version gets into the binary? I get that, but the value of the field must be a build depends for it to be "Built-Using" But surely, timestamps &b checksums are different things? Anyway, my understanding is the issue relates to packages that ship ppu files, which would be lazarus & cge. @Abou, I can't see any purpose in having this bug assigned to winff, as winff does not provide or consume any ppus from other packages. I'm thinking adding to the workflow notes for fpc https://salsa.debian.org/pascal-team/fpc/-/wikis/Debian%20FPC%20Packaging something like... "After an upload of fpc, check that lazarus builds, and if there are checksum errors, giveback or upload a new version of lazarus. Also check that castle-model-viewer builds, and if there are checksum errors, giveback or upload a new version of castle-game-engine. Regards, Peter
Hi Paul, I'm thinking now, that src:lazarus and src:castle-model-viewer are the only packages that would benefit in any way. Bit is it still worth doing? Its easy enough. Regards, Peter
Hi, Yes, because the Release Team tooling might be improved in this regard in the (near-ish) future. Paul
Hi, Yes. Paul
Hi, I think only libraries will be affected by a rebuild requirement. This means lazarus (lcl part), libqt*pas, and castle game engine. The castle model viewer is a tool, not a library.
Hi, One point, if there is a security fix, then we need to build winff, and all FPC compiled tools. Of course there will be no FTBFS in this case, but it is an important feature of the tag 'Static-Built-Using'
Agreed. I meant to say castle-game-engine, not castle-game-viewer Thanks for correcting.
Hi All,
Here is my understand on how this should work:
First we should patch fpc-depends to generate a substitution variable let's say
as fommows:
diff --git a/debian/fpc-depends.in b/debian/fpc-depends.in
index ddc3c348..04de6033 100755
--- a/debian/fpc-depends.in
+++ b/debian/fpc-depends.in
@@ -47,6 +47,7 @@ init ();
foreach my $package (@{$dh{DOPACKAGES}}) {
delsubstvar($package, "fpc-abi:Depends");
addsubstvar($package, "fpc-abi:Depends", "fpc-abi-${VERSION}");
+ addsubstvar($package, "fpc:Static-Built-Using", "fpc (= ${DEB_VERSION})");
}
=head1 SEE ALSO
The inside CGE we add the filed, lets say as follow:
diff --git a/debian/control b/debian/control
index 2ced4249..b9b1ad99 100644
--- a/debian/control
+++ b/debian/control
@@ -38,7 +38,7 @@ Rules-Requires-Root: no
Package: fp-units-castle-game-engine
Architecture: any
-Static-Built-Using: fpc
+Static-Built-Using: ${fpc:Static-Built-Using}
Depends:
${fpc-abi:Depends},
${misc:Depends},
diff --git a/debian/rules b/debian/rules
index 28aaa45f..d0107ae2 100755
--- a/debian/rules
+++ b/debian/rules
@@ -146,6 +146,7 @@ override_dh_auto_install-arch:
${CP} debian/castle-game-engine.cfg ${CFG_DIR}/castle-game-engine
# Perform cleanup
find ${INSTALL_DIR} -empty -delete
+ fpc-depends
override_dh_auto_build-indep: prepare-source install-source
@echo "--- Building Documentation"
This way, the dependency on FPC is added dynamically upon the build.
Please let me know what do you think?
Hi Abou That looks reasonable from here. By the way, should lazarus do something similar? In my understanding all binaries build by fpc or lazarus get statically stuff linked in, so indeed everything in the FreePascal ecosystem should do this, right? Paul
Hi Paul, Yes indeed, but I see it very heavy to have laz-depends and cge-depends. I think we need fpc-depends to be renamed dh_fpc and be a bit more intelligent, don't you?
We believe that the bug you reported is fixed in the latest version of
fpc, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 997948@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Abou Al Montacir <abou.almontacir@sfr.fr> (supplier of updated fpc package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Sun, 19 Jan 2025 00:05:12 +0100
Source: fpc
Binary: fp-compiler fp-compiler-3.2.2 fp-docs fp-docs-3.2.2 fp-ide fp-ide-3.2.2 fp-units-base fp-units-base-3.2.2 fp-units-db fp-units-db-3.2.2 fp-units-fcl fp-units-fcl-3.2.2 fp-units-fv fp-units-fv-3.2.2 fp-units-gfx fp-units-gfx-3.2.2 fp-units-gtk2 fp-units-gtk2-3.2.2 fp-units-math fp-units-math-3.2.2 fp-units-misc fp-units-misc-3.2.2 fp-units-multimedia fp-units-multimedia-3.2.2 fp-units-net fp-units-net-3.2.2 fp-units-rtl fp-units-rtl-3.2.2 fp-units-wasm fp-units-wasm-3.2.2 fp-utils fp-utils-3.2.2 fpc fpc-3.2.2 fpc-source fpc-source-3.2.2
Architecture: source amd64 all
Version: 3.2.2+dfsg-37
Distribution: unstable
Urgency: medium
Maintainer: Pascal Packaging Team <pkg-pascal-devel@lists.alioth.debian.org>
Changed-By: Abou Al Montacir <abou.almontacir@sfr.fr>
Description:
fp-compiler - Free Pascal - compiler dependency package
fp-compiler-3.2.2 - Free Pascal - compiler
fp-docs - Free Pascal - documentation dependency package
fp-docs-3.2.2 - Free Pascal - documentation
fp-ide - Free Pascal - IDE dependency package
fp-ide-3.2.2 - Free Pascal - IDE
fp-units-base - Free Pascal - base units dependency package
fp-units-base-3.2.2 - Free Pascal - base units
fp-units-db - Free Pascal - database-library units dependency package
fp-units-db-3.2.2 - Free Pascal - database-library units
fp-units-fcl - Free Pascal - Free Component Library dependency package
fp-units-fcl-3.2.2 - Free Pascal - Free Component Library
fp-units-fv - Free Pascal - Free Vision units dependency package
fp-units-fv-3.2.2 - Free Pascal - Free Vision units
fp-units-gfx - Free Pascal - graphics-library units dependency package
fp-units-gfx-3.2.2 - Free Pascal - graphics-library units
fp-units-gtk2 - Free Pascal - GTK+ 2.x units dependency package
fp-units-gtk2-3.2.2 - Free Pascal - GTK+ 2.x units
fp-units-math - Free Pascal - math units dependency package
fp-units-math-3.2.2 - Free Pascal - math units
fp-units-misc - Free Pascal - miscellaneous units dependency package
fp-units-misc-3.2.2 - Free Pascal - miscellaneous units
fp-units-multimedia - Free Pascal - multimedia units dependency package
fp-units-multimedia-3.2.2 - Free Pascal - multimedia units
fp-units-net - Free Pascal - networking units dependency package
fp-units-net-3.2.2 - Free Pascal - networking units
fp-units-rtl - Free Pascal - runtime libraries dependency package
fp-units-rtl-3.2.2 - Free Pascal - runtime libraries
fp-units-wasm - Free Pascal - Web assembly support units dependency package
fp-units-wasm-3.2.2 - Free Pascal - Web assembly support units
fp-utils - Free Pascal - utilities dependency package
fp-utils-3.2.2 - Free Pascal - utilities
fpc - Free Pascal - SDK suite dependency package
fpc-3.2.2 - Free Pascal - SDK-3.2.2 suite
fpc-source - Free Pascal - SDK source code dependency package
fpc-source-3.2.2 - Free Pascal - SDK source code
Closes: 997948
Changes:
fpc (3.2.2+dfsg-37) unstable; urgency=medium
.
* Fixed build of architecture independent packages on sid.
* Added support for ${fpc:Static-Built-using} in fpc-depnds.
(Closes: Bug#997948)
Checksums-Sha1:
27d9779d8c9585d1c67055197959871891355192 3925 fpc_3.2.2+dfsg-37.dsc
1cc4bded5346ba63de56e06623742493874c7145 132312 fpc_3.2.2+dfsg-37.debian.tar.xz
364c39a6b4fa119473b8cf54c5fe1d8bec8b5c20 2044532 fp-compiler-3.2.2_3.2.2+dfsg-37_amd64.deb
bed7e086c4f1c0369539409a36e992f01c7cad70 28664 fp-compiler_3.2.2+dfsg-37_amd64.deb
07286d11a0b8e892b7b1929c6dd4b96115a79dc7 2799968 fp-docs-3.2.2_3.2.2+dfsg-37_all.deb
b2e964b385d4405fd2bb4b362a304e540b50c40b 28560 fp-docs_3.2.2+dfsg-37_all.deb
360a83d2240252fb5caf41851b66de0395cd1639 1369436 fp-ide-3.2.2_3.2.2+dfsg-37_amd64.deb
1632103faddf8aa493f7bd74501775aa70f5d255 28692 fp-ide_3.2.2+dfsg-37_all.deb
d9ca9a15e12edad5ab1cda52540be0dae2b37ac0 1201916 fp-units-base-3.2.2_3.2.2+dfsg-37_amd64.deb
4eb2652d258b0dacb99236f34ff629b374bedbb1 28628 fp-units-base_3.2.2+dfsg-37_amd64.deb
abbbcc84660699cfe8caa26c3c65ed28499eac45 2717404 fp-units-db-3.2.2_3.2.2+dfsg-37_amd64.deb
527d807f6657a7de5ead367cc49b8ac75a606e63 28604 fp-units-db_3.2.2+dfsg-37_amd64.deb
4d0c7452e928d5b1a3e650ddd35a153857344d9e 7373240 fp-units-fcl-3.2.2_3.2.2+dfsg-37_amd64.deb
1407cefb764e79ffaa8d5138eca28a89441b4858 28568 fp-units-fcl_3.2.2+dfsg-37_amd64.deb
a8f15d620e2df739962147a85f5119fb0e308c73 358712 fp-units-fv-3.2.2_3.2.2+dfsg-37_amd64.deb
c8797ce9426a2ce1c81c240ed2bd039357843329 28584 fp-units-fv_3.2.2+dfsg-37_amd64.deb
ab9cf8534cde29f6ae39d57a7bf9676b68a26182 1158304 fp-units-gfx-3.2.2_3.2.2+dfsg-37_amd64.deb
a70149564d9267fe93b00b3ff14fd4139b5675da 28680 fp-units-gfx_3.2.2+dfsg-37_amd64.deb
e2c590856a2f5b7e9ebbf6d7ea861b3226120ad3 1080256 fp-units-gtk2-3.2.2_3.2.2+dfsg-37_amd64.deb
3c6db7a0ca292200e3eca97c42c52e5075c18d33 28592 fp-units-gtk2_3.2.2+dfsg-37_amd64.deb
6384bf196b0ac647303d9a3c65adba20ca2140e5 358336 fp-units-math-3.2.2_3.2.2+dfsg-37_amd64.deb
0a1b39aea9c3590aa523d95438ae015358655ed9 28748 fp-units-math_3.2.2+dfsg-37_amd64.deb
a932d098b340e88ee10f7394deb0dff32724789e 1503040 fp-units-misc-3.2.2_3.2.2+dfsg-37_amd64.deb
8609745523872c7fa3deda7f3117a91274aa2c6d 28640 fp-units-misc_3.2.2+dfsg-37_amd64.deb
5a7a61cca2a101fa76e52fcfbc1eca074a0be5cf 236360 fp-units-multimedia-3.2.2_3.2.2+dfsg-37_amd64.deb
cba32af85c79170682176449f7a59d07e3f62329 28620 fp-units-multimedia_3.2.2+dfsg-37_amd64.deb
41a92c80f29b58e4df60ba89f96030bc95a4e3d8 8085552 fp-units-net-3.2.2_3.2.2+dfsg-37_amd64.deb
e57079a41ada88eb65473e7352a7d8f145b925c9 28616 fp-units-net_3.2.2+dfsg-37_amd64.deb
7ea0d837ca764ea8db9fdabd7103a1c547c5e9be 6866704 fp-units-rtl-3.2.2_3.2.2+dfsg-37_amd64.deb
8a831fa4b65bf1a805b2cd7f99577db666988a1b 28568 fp-units-rtl_3.2.2+dfsg-37_amd64.deb
52276cc37f76c0274fed364abd1320b8b812f422 785052 fp-units-wasm-3.2.2_3.2.2+dfsg-37_amd64.deb
760f9ded3ee040451508f59a1f9829568d415686 28448 fp-units-wasm_3.2.2+dfsg-37_amd64.deb
c64bfa42cd87b2ecd6c7656fc2e367a73845fc40 5211864 fp-utils-3.2.2_3.2.2+dfsg-37_amd64.deb
c4d099bfd26986feb33ec815f536110674f0c809 31152 fp-utils_3.2.2+dfsg-37_all.deb
bf9aefcc4cf295917850cd0b06a692d561f66076 29228 fpc-3.2.2_3.2.2+dfsg-37_all.deb
7fa758d13d59c1b4fdcfc29467f56ec4b5725a70 19787736 fpc-source-3.2.2_3.2.2+dfsg-37_all.deb
3de8cedcb0eb2c3d045542ee641304d3a5b75ab8 28668 fpc-source_3.2.2+dfsg-37_all.deb
b4a2efa20803e904f0756110a0f0990667387fbe 28696 fpc_3.2.2+dfsg-37_all.deb
ee8f5384cfd05942ecac0ae4104f424de25db66b 19602 fpc_3.2.2+dfsg-37_amd64.buildinfo
Checksums-Sha256:
881f6afa94a92ef6755d3fdc6d4f0a0ae8fa81171c58b121d3f6bd22bea3a158 3925 fpc_3.2.2+dfsg-37.dsc
3b8fbb238646c39f7351a485e3e7ca2d778fdd9142d3c970fa25ccc33ba5bac2 132312 fpc_3.2.2+dfsg-37.debian.tar.xz
c8a4279b062d1d9eac0d310650634be23f551169d9630753ce83be3ce7aebded 2044532 fp-compiler-3.2.2_3.2.2+dfsg-37_amd64.deb
4ad6b9af8edc18818981db0cdf72b54e99ed021d3eebf498d7e9519686ddbbf8 28664 fp-compiler_3.2.2+dfsg-37_amd64.deb
3dc5a3a9d962c77cd124edc61521832cc2d8d78633e09e7bad236b4e9fc2c399 2799968 fp-docs-3.2.2_3.2.2+dfsg-37_all.deb
cdd2355e2c2de4856e25dbd4bfc9203c00c70d12637b665d582ce11f35ad0590 28560 fp-docs_3.2.2+dfsg-37_all.deb
87faac247c5404af80ebc756f1742ae0e71986fe02308862c954a21ea76df00d 1369436 fp-ide-3.2.2_3.2.2+dfsg-37_amd64.deb
29dbb187cddae94abb28ab03f7adb37421ba5f664a9e7c186894ce2314fdcd9f 28692 fp-ide_3.2.2+dfsg-37_all.deb
ddb499a241bc9984e4b4a480135d457dc9ba1b2981364eff7dfe6b9d75597f9d 1201916 fp-units-base-3.2.2_3.2.2+dfsg-37_amd64.deb
553c9788b119d7733d2eb258d604ce99713e1eb51ffe1c81e9dd5320e6adcf9b 28628 fp-units-base_3.2.2+dfsg-37_amd64.deb
d1c9d95ad5327d9c04c67fcdee6a20b04fc67720c4b00954f59673ca39feae1b 2717404 fp-units-db-3.2.2_3.2.2+dfsg-37_amd64.deb
f5982279c967c5e05ae5ded391d11a46820ab8260056407bf43d2350fb98fb60 28604 fp-units-db_3.2.2+dfsg-37_amd64.deb
6016377624006ea4ae7a364d7cb4295d418294ff371d30032a241a6445f20d94 7373240 fp-units-fcl-3.2.2_3.2.2+dfsg-37_amd64.deb
15a8585e8de73aae90f22d484ddcd72ffb2c16034817b66f8abb17d722e40f39 28568 fp-units-fcl_3.2.2+dfsg-37_amd64.deb
338f0949b4f608c6adb90c888854fd40ac7b6a312f1eeb295c32ff3cc28da26f 358712 fp-units-fv-3.2.2_3.2.2+dfsg-37_amd64.deb
53c9c25b688cbe0687d73d6955e51d7978b98d09c2612b7310f79c9af33ec977 28584 fp-units-fv_3.2.2+dfsg-37_amd64.deb
a27fa1847884a13bb84c4177c693186d1f099bb40fb0c753a086f1905b229915 1158304 fp-units-gfx-3.2.2_3.2.2+dfsg-37_amd64.deb
d64f7ae37a4252b35eaf5910408f3d046d588545450a96e98c0c763b376b42b2 28680 fp-units-gfx_3.2.2+dfsg-37_amd64.deb
368c2413a529e7e89a67426d2486b61012a73f98127645ac70e7e1f27e60d701 1080256 fp-units-gtk2-3.2.2_3.2.2+dfsg-37_amd64.deb
4ec8de0053d28c81688bcb94c7351d99cc706f04c15cea5aeaf73c8edf7f2699 28592 fp-units-gtk2_3.2.2+dfsg-37_amd64.deb
cfc755eac62e644fdf4b0334bcd6e4127a70e7190f8b99de2a8caea112608d88 358336 fp-units-math-3.2.2_3.2.2+dfsg-37_amd64.deb
a95934e57268bcc91abffdf3a2caf1957556816a694d17151efc202c23ed424a 28748 fp-units-math_3.2.2+dfsg-37_amd64.deb
e200e04df4ddd50108ae881183f96519a79ce957c3042c2682a397d24deb6d1c 1503040 fp-units-misc-3.2.2_3.2.2+dfsg-37_amd64.deb
a8a54a4439be55b8a1fa13d3adc9096d972783cce0ff642051d882a5ff5231f6 28640 fp-units-misc_3.2.2+dfsg-37_amd64.deb
7cca32b8e8f67daf358d763849fcc4d20aae2687716e51d33d72db3edf25af98 236360 fp-units-multimedia-3.2.2_3.2.2+dfsg-37_amd64.deb
32a3f2b627afe5668b0fe0b6cefd929bd8388c17a9d152846954ae92eeb907db 28620 fp-units-multimedia_3.2.2+dfsg-37_amd64.deb
bcd3159d60daee995dece47ab1cd56bc1932ba1e908a458e3f025257c7e64d17 8085552 fp-units-net-3.2.2_3.2.2+dfsg-37_amd64.deb
067048d92d8e0374dea1ad258e379be9631b14377d2e5be88e42d04abaf48440 28616 fp-units-net_3.2.2+dfsg-37_amd64.deb
47a114dadb3ca2a7076612bf74ca82ab7af6d1535a62ea58caca322b26d9c8b0 6866704 fp-units-rtl-3.2.2_3.2.2+dfsg-37_amd64.deb
47fb2a3f1518c2087b5f646edfb537aaa640dc28bfe62bcd87d4da3eed5aa2e0 28568 fp-units-rtl_3.2.2+dfsg-37_amd64.deb
e5bf3b80977eafa005ec949e042648b2c664a4ea66038bf47072d6b3f622879f 785052 fp-units-wasm-3.2.2_3.2.2+dfsg-37_amd64.deb
ed1f9400f1f0a66f8a37dbfcdd639b294af4e664b6ca22a2f03d447c2b1d62d2 28448 fp-units-wasm_3.2.2+dfsg-37_amd64.deb
78d71008c9d438039ae14c9b47a2b09e6f95bd2268638f365e1092b053f22c34 5211864 fp-utils-3.2.2_3.2.2+dfsg-37_amd64.deb
e91ff0d04dc4ff4000cbc2b1043681849b70aefdf06494e3fb36d648733b1240 31152 fp-utils_3.2.2+dfsg-37_all.deb
56404b8cac8bd8f2cfd8420e43f15e19df8f138f5c1734bc3aa13f4fd0cff1f6 29228 fpc-3.2.2_3.2.2+dfsg-37_all.deb
1d843906cae824167f9d1048bf38e5a651846bf084f74945aff618f7f993867c 19787736 fpc-source-3.2.2_3.2.2+dfsg-37_all.deb
abbfe6080f46a6bf10eba5d39dc81c9c311f2a631be1279fa8b124feedec9014 28668 fpc-source_3.2.2+dfsg-37_all.deb
a0128064f3f3a50b5a78ff7f34c49c526aaa03dea89cc702b0784c46648a87c4 28696 fpc_3.2.2+dfsg-37_all.deb
53a9737578766afffd64ea410ce47fea5791c7134e9fae6d35a8b6d7a44bd650 19602 fpc_3.2.2+dfsg-37_amd64.buildinfo
Files:
e5c4befc839c174337a62b7a37b10d35 3925 devel optional fpc_3.2.2+dfsg-37.dsc
bb970255320d721fc259a5a5e3e1f8b4 132312 devel optional fpc_3.2.2+dfsg-37.debian.tar.xz
4c21846666be2c8decdd1023c37126a8 2044532 devel optional fp-compiler-3.2.2_3.2.2+dfsg-37_amd64.deb
60e90296c7125ca693282833c5ede9b4 28664 devel optional fp-compiler_3.2.2+dfsg-37_amd64.deb
76dfe24ec35c999c90e629baa9f454ee 2799968 doc optional fp-docs-3.2.2_3.2.2+dfsg-37_all.deb
7395b5107196a8486c90a1caf14d41a6 28560 doc optional fp-docs_3.2.2+dfsg-37_all.deb
943f9491d42e68c757e2c1904abb745e 1369436 devel optional fp-ide-3.2.2_3.2.2+dfsg-37_amd64.deb
694364dd24c501a882968b825c39c192 28692 devel optional fp-ide_3.2.2+dfsg-37_all.deb
be3120226c24542a0aa07f54bc0dc2ea 1201916 devel optional fp-units-base-3.2.2_3.2.2+dfsg-37_amd64.deb
ac70a0f3e0c66138eb61830d2e22b0f5 28628 devel optional fp-units-base_3.2.2+dfsg-37_amd64.deb
0e116eca5daffddb58246c26599e6d7a 2717404 devel optional fp-units-db-3.2.2_3.2.2+dfsg-37_amd64.deb
f8cfde9d2e0f935bef5754dda03984ea 28604 devel optional fp-units-db_3.2.2+dfsg-37_amd64.deb
35747e13a966cc2505e6c37a84140252 7373240 devel optional fp-units-fcl-3.2.2_3.2.2+dfsg-37_amd64.deb
5bff9328181581de33b9bab439100e6d 28568 devel optional fp-units-fcl_3.2.2+dfsg-37_amd64.deb
9b9c7e0c09f919f4bc68a6e13d38ee12 358712 devel optional fp-units-fv-3.2.2_3.2.2+dfsg-37_amd64.deb
fd7091502b051fa39814416f8c4d78f4 28584 devel optional fp-units-fv_3.2.2+dfsg-37_amd64.deb
c2591ae0a70d22fc7db9157fef407f65 1158304 devel optional fp-units-gfx-3.2.2_3.2.2+dfsg-37_amd64.deb
ba19bf34b6315259da948e00f76d812c 28680 devel optional fp-units-gfx_3.2.2+dfsg-37_amd64.deb
5eee643c8425c2310e71739a7c10044e 1080256 devel optional fp-units-gtk2-3.2.2_3.2.2+dfsg-37_amd64.deb
02b4a648ed605bf2d62ff080d0093639 28592 devel optional fp-units-gtk2_3.2.2+dfsg-37_amd64.deb
74a86bec5a66c1f5a381d159e9e8eb88 358336 devel optional fp-units-math-3.2.2_3.2.2+dfsg-37_amd64.deb
37d0ec3bed9004e8e06110137fec0831 28748 devel optional fp-units-math_3.2.2+dfsg-37_amd64.deb
5f6d04335c4d30020e3ed41e47b3605f 1503040 devel optional fp-units-misc-3.2.2_3.2.2+dfsg-37_amd64.deb
19466c75606ed27a35ef6eb8ecc3297a 28640 devel optional fp-units-misc_3.2.2+dfsg-37_amd64.deb
9bb5996e1f8fc81af70462f1b0330b23 236360 devel optional fp-units-multimedia-3.2.2_3.2.2+dfsg-37_amd64.deb
d45cd0a9c76613ebc6de365c7913349a 28620 devel optional fp-units-multimedia_3.2.2+dfsg-37_amd64.deb
cb462b6957acbe16ca2e73b61b91b9b3 8085552 devel optional fp-units-net-3.2.2_3.2.2+dfsg-37_amd64.deb
03586a208f142be8e0f0b28559b4f069 28616 devel optional fp-units-net_3.2.2+dfsg-37_amd64.deb
f22f21ea2d74f6f1333d5108d333f049 6866704 devel optional fp-units-rtl-3.2.2_3.2.2+dfsg-37_amd64.deb
ff4334921bd7528608ec480e0f81f65c 28568 devel optional fp-units-rtl_3.2.2+dfsg-37_amd64.deb
9160e5a16d1239870cf1816c43babd59 785052 devel optional fp-units-wasm-3.2.2_3.2.2+dfsg-37_amd64.deb
5d5e6ef992ec23e0531bcf6e1f4b486d 28448 devel optional fp-units-wasm_3.2.2+dfsg-37_amd64.deb
7e2de8943b9dee9daa53ee3c8b9be9ca 5211864 devel optional fp-utils-3.2.2_3.2.2+dfsg-37_amd64.deb
d60542807c784e11d575852ba3eda0c9 31152 devel optional fp-utils_3.2.2+dfsg-37_all.deb
daa90d7a65de184ec2dbb4937bca8100 29228 devel optional fpc-3.2.2_3.2.2+dfsg-37_all.deb
a6ba17a257e2dcccda26625fe493e7c1 19787736 devel optional fpc-source-3.2.2_3.2.2+dfsg-37_all.deb
443e00bc6f7187d28ab7045251735e4f 28668 devel optional fpc-source_3.2.2+dfsg-37_all.deb
54e8e463b4115a1025e17c4044784c93 28696 devel optional fpc_3.2.2+dfsg-37_all.deb
28b73fe2fd8f68933ade8c5a8071bba1 19602 devel optional fpc_3.2.2+dfsg-37_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iI0EAREKADUWIQS69sZENhB4UNQicQazJVxtVYeNjAUCZ4w6ZRccYWJvdS5hbG1v
bnRhY2lyQHNmci5mcgAKCRCzJVxtVYeNjPEoAPoD+/WlpjlbDMgVojPWvFJ+eJAc
PevP41JWMXEae2BeGAD+I0mUrPbSlDB1E7kEv82cWvaaEd1aHs5X41N6hN845ac=
=71gH
-----END PGP SIGNATURE-----