Peter Blackman <[email protected]> wrote on 10/04/2025 at 00:25:27+0200:
> On 09/04/2025 21:44, Pierre-Elliott Bécue wrote: > >> Hey, >> I have a problem with your control file: >> First the Breaks+Replaces on the -dev pkg seems unwarranted. Can you >> explain me what are you trying to do with it? >> Second the Replaces+Conflicts on the lib itself for >> itself. Theoretically, two different versions of the same package can't >> be installed concurrently (except multi-arch, but the conflicts+replaces >> is only valid per arch. It seems useless. >> Also, if it's to be useful, a versioned conflicts means you want to >> use >> replaces. >> Can you help me see what you want to achieve? >> Bests, > > Hi Pierre, > > I could not get piuparts to work with anything less > regarding Breaks/Conflicts/Replaces. > > You can see the history and the pipeline/piuparts > fails in the recent commits. > (A piuparts failure will prevent migration of course) > > > There is no problem with manual upgrading, if the library > is upgraded first, but it seems piuparts tries to upgrade > the dev package first, which fails because of file conflict. > (The cmake files were moved to the dev package in version 1.1. > The lib package should only contain the .so files) Ah, I see I missed your moving of the cmake files to the dev package. Sorry, they should have been there all the time, I screwed up in 2022 I guess. So, here you just need the Breaks: field in the -dev package and that's all. Conflicts is for permanent stuff, it should generally not be versioned. Here it's just file moving, so a breaks is enough. And no replaces, as -dev does not replace the lib. I see you've committed something, I did an additionnal commit. Tell me if that's fine with you. Bests, -- PEB
signature.asc
Description: PGP signature
