Hi Maarten,
Sorry for dropping the ball on this.
On 2022-02-06 21:16, Maarten L. Hekkelman wrote:
> Op 4-2-2022 om 11:43 schreef Maarten L. Hekkelman:
>> 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
>
Hi Maarten,
On 2022-02-02 12:44, Maarten L. Hekkelman wrote:
> 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
On 2/2/22 4:14 PM, Maarten L. Hekkelman wrote:
OK, the transition for both has started, see [1]. But I wonder, what does the
status 'partial' mean? Is there something I should do?
Probably not, it is fine I guess. However, you should fix/rebuild
density-fitness since that is
showing up as bad
On 2 February 2022 4:14:02 pm IST, "Maarten L. Hekkelman"
wrote:
>OK, the transition for both has started, see [1]. But I wonder, what does the
>status 'partial' mean? Is there something I should do?
Probably not, it's fine I guess.
However you probably should fix/rebuild density-fitness, sin
Hi Maarten,
On 2022-01-31 15:13, Maarten L. Hekkelman wrote:
> Okay, finally had time to work on this.
>
> I patched the libcifpp many times but I now feel confident it should
> work. It builds on an experimental box (with i386 to make things more
> difficult). When I install the packages from th
"Maarten L. Hekkelman" writes:
> The Config file was no longer needed thanks to the switch to
> cmake. The API should be roughly the same.
It might have been helpful to leave a stub in place, perhaps with a
deprecation warning; AFAICT, there are only a few reverse dependencies,
but they all use
Hi Maarten,
On 2022-01-24 12:23, Maarten L. Hekkelman wrote:
> Op 16-01-2022 om 09:47 schreef Andrius Merkys:
>> libcifpp 2.0.4-1 has just been accepted to experimental (yay!). This
>> means now we have to carry out its transition [1] (libcifpp1 ->
>> libcifpp2).
>>
>> I see you have in the meanti
Hi Maarten,
libcifpp 2.0.4-1 has just been accepted to experimental (yay!). This
means now we have to carry out its transition [1] (libcifpp1 -> libcifpp2).
I see you have in the meantime released libcifpp with soversion of 3.
Thus instead of doing libcifpp1 -> libcifpp2 we may skip to libcifpp1
8 matches
Mail list logo
