[Pkg-pascal-devel] checksum errors on lazarus builds

[Abou Al Montacir]

Hi Paul,

On Mon, 2025-02-10 at 21:26 +0100, Paul Gevers wrote:
> Hi,
> 
> On 10-02-2025 21:20, Abou Al Montacir wrote:
> > I'm just curious, how does it decide the relationship between CGE, 
> > Lazarus and FPC?
> > Is there some document on how this works?
> > Does it take into account Static-Built-Using flag?
> 
> 
> It looks at all standard package relations (like used by apt) that exist 
> between the packages that are to be tested and the one that needs to 
> migrate. If any relation between the package that needs to migrate 
> requires the other package to also come from unstable, it will be added.
> 
> "Documentation" is here:
> https://salsa.debian.org/release-team/britney2/-/blob/master/britney2/policies/autopkgtest.py?ref_type=heads#L800

If I understand it well, this is using packages and not sources.
Then I need to declare the breaks on all FPC packages for all packages of CGE
and Lazarus? That is maybe too much.

Is it possible to declare only breaks on fp-units-rtl-3.2.2 that breaks let's
say fp-units-lcl-3.8? Will that be enough?

If not, then will it be possible maybe to force FPC into testing after tomorrow
(5th day)?
-- 
Cheers,
Abou Al Montacir


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-pascal-devel/attachments/20250210/2e72fc82/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-pascal-devel/attachments/20250210/2e72fc82/attachment.sig>