On 10/04/2025 22:17, Hefee wrote:
Hey,
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.
b
Hey,
> 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.
break alone is very rare. in mos
On 09/04/2025 21:44, Pierre-Elliott Bécue wrote:
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.
Hi Pie
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 di
Peter Blackman 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 Repl
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)
I tried again this morning, and it seems the breaks/replaces
in the lib
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 dif
Pierre-Elliott Bécue wrote on 04/04/2025 at 13:50:27+0200:
> De : Peter Blackman
> À : Pierre-Elliott Bécue ; Hefee
> Cc : 1101...@bugs.debian.org
> Date : 4 avr. 2025 13:49:34
> Objet : Re: kdsingleapplication
>
>> Hi Pierre, Hefee,
>>
>> kdsingleapplication is ready for upload to unstable,
>
De : Peter Blackman
À : Pierre-Elliott Bécue ; Hefee
Cc : 1101...@bugs.debian.org
Date : 4 avr. 2025 13:49:34
Objet : Re: kdsingleapplication
> Hi Pierre, Hefee,
>
> kdsingleapplication is ready for upload to unstable,
> but I don't have the rights to do it myself.
>
> It seems the ABI was not
Hi Pierre, Hefee,
kdsingleapplication is ready for upload to unstable,
but I don't have the rights to do it myself.
It seems the ABI was not changed (although upstream bumped the SONAME) (#1)
so there is no need for a transition!
This means we can still avoid introducing the SSH issue into Trixi
10 matches
Mail list logo
