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

Re: libcifpp transition

Op 4-2-2022 om 11:43 schreef Maarten L. Hekkelman:

I have never seen 'partial' status before. Maybe someone else could
comment on that. And density-fitness surely needs at least rebuilding,
Nilesh is right.

It took some time and effort, but I managed to get everything fixed and building correctly. But tortoize still is marked as partial in the libcifpp auto page. Libpdb-redo too, btw.

Almost everything is in testing now. That nice, that way it will be in Jammy as well.

The strange thing is, I can also not build tortoize in salsa in its CI environment. The error here is:

This job depends on other jobs with expired/erased artifacts: extract-source
Please refer to https://docs.gitlab.com/ee/ci/yaml/README.html#dependencies

According to tracker, tortoize is completely OK.

The problem became clear when I received a bug report, there was a hardcoded dependency on libcifpp1 in tortoize making it uninstallable.

Curious, none of the tools ever warned about this.

But at least I learned something new today.


Reply to: