[Piuparts-devel] satpy migration to testing blocked by piuparts

[Holger Levsen]

On Sat, Aug 13, 2022 at 08:05:10PM +0200, Antonio Valentino wrote:
> Dear piuparts developers,
> the migration of satpy [1] to testing is blocked due to piuparts regression.
> 
> Looking at [2] and [3] it seems to me that the problem is not related to
> satpy itself.
> Am I missing something?

I think you are correct, it seems this is the root cause for the piuparts
failure:

2m6.0s ERROR: installs objects over existing directory symlinks:
  /usr/lib/x86_64-linux-gnu/fortran/gfortran-11/libfodc.so (libodc-dev:amd64) != /usr/lib/x86_64-linux-gnu/fortran/gfortran-mod-15/libfodc.so (?)
    /usr/lib/x86_64-linux-gnu/fortran/gfortran-11 -> /usr/lib/x86_64-linux-gnu/fortran/gfortran-mod-15

(from
https://piuparts.debian.org/sid/fail/python3-satpy_0.37.0-2.log
)

> What should I do to unblock the satpy migration?

the easiest is: wait, until the above issue is fixed by someone
else. piuparts.d.o retries failed packages frequently.

your other option is to activly contribute to getting the above
issue fixed. :)


-- 
cheers,
	Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

All data, over time, approaches deleted, or public. (@quinnnorton)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/piuparts-devel/attachments/20220815/6d80a020/attachment.sig>