Re: libcifpp transition
- To: debian-med@lists.debian.org
- Subject: Re: libcifpp transition
- From: "Maarten L. Hekkelman" <maarten@hekkelman.com>
- Date: Wed, 2 Feb 2022 11:44:02 +0100
- Message-id: <[🔎] 8aa0bd19-b34b-c8a2-c55e-721cb05ee900@hekkelman.com>
- In-reply-to: <4303a2a9-88c6-09ca-f223-8c5b5ec6c72a@debian.org>
- References: <3efd4080-6e5f-7dea-7f14-2009434a4882@debian.org> <41fa501d-e79f-7abb-f7b4-56ce4ce24350@hekkelman.com> <d4e6cae5-8829-b548-dfce-e016d9cf03a8@debian.org> <385bae0f-a479-5db4-2597-4c401c8bb13a@hekkelman.com> <4303a2a9-88c6-09ca-f223-8c5b5ec6c72a@debian.org>
Hi Andrius,
Op 31-01-2022 om 14:49 schreef Andrius Merkys:
This is purely informational. It says you probably should not attempt
transitioning libcifpp and libpdb-redo at the same time.
Hmmm, that didn't work, had to update both to make this work.
Anyway, now someone needs to file that bug to ask for a time slot. Who
is supposed to do that? Is that me? Or does anyone else volunteer?
It would be great if you could do that. You may use my recent openmm
transition bug report [1] as a template. What is important in libcifpp
case is to tell that you are planning to patch the new libcifpp to make
it backwards-compatible with the old libcifpp.
OK, the transition for both has started, see [1]. But I wonder, what
does the status 'partial' mean? Is there something I should do?
[1] https://release.debian.org/transitions/html/auto-libcifpp.html
Best regards,
-maarten
Reply to: