[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Why doesn't nifticlib migrate?



Hi Steven,

On 20-12-2020 20:32, Steven Robbins wrote:
> The excuses page says it is good to go, but it hasn't migrated despite being 7 
> days past the required 5 days.  What's up?
> 
> 
> Excuse for nifticlib
> Migration status for nifticlib (2.0.0+git186-g84740c2-1 to 3.0.1-4): Will 
> attempt migration (Any information below is purely informational)
> Additional info:
> Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nifticlib.html
> 12 days old (needed 5 days)
> Excuses generated Sun Dec 20 18:08:20 2020

Our migration software has two phases [1]. The excuses are the result of
the first phase. The package is blocked due to the results of the second
phase. The output of that can be seen at [2], which includes:
trying: nifticlib gifticlib
skipped: nifticlib gifticlib (1, 2, 57)
    got: 29+0: a-5:a-23:a-0:a-0:i-0:m-0:m-0:p-0:s-1
    * amd64: libcamitk-dev, libinsighttoolkit4-dev, libotb-dev, libsight-dev
    - splitting the component into single items and retrying them
trying: gifticlib
skipped: gifticlib (1, 2, 58)
    got: 28+0: a-4:a-23:a-0:a-0:i-0:m-0:m-0:p-0:s-1
    * amd64: gifti-bin, libgiftiio-dev, libgiftiio0
trying: nifticlib
skipped: nifticlib (1, 3, 57)
    got: 30+0: a-6:a-23:a-0:a-0:i-0:m-0:m-0:p-0:s-1
    * amd64: libcamitk-dev, libgiftiio-dev, libinsighttoolkit4-dev,
libotb-dev, libsight-dev

This means that upgrading nifticlib (alone) would make libcamitk-dev,
libgiftiio-dev, libinsighttoolkit4-dev, libotb-dev, libsight-dev not
installable (at least on amd64).

Unfortunately, I fail to quickly spot how libcamitk-dev becomes
not-installable (it seems to already be not-installable to me).

Paul

[1] https://release.debian.org/doc/britney/short-intro-to-migrations.html
[2] https://release.debian.org/britney/update_output.txt.gz

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


Reply to: