Re: fwupdate is marked for autoremoval from testing
On Tue, Oct 01, 2019 at 10:09:51PM +0000, Mario.Limonciello@dell.com wrote:
>> From: Steve McIntyre <steve@einval.com>
...
>> It still won't fix things AFAICS. What I think we need to do is:
>>
>> 1. In fwupd, add Provides/Replaces, plus Conflicts: against the older
>> versions of fwupdate-*-signed. That will tell apt to upgrade
>> cleanly and thereby switch to fwupd instead. See
>> https://www.debian.org/doc/manuals/developers-
>> reference/ch05.html#s5.9.3
>
>OK. I'ved pushed this to salsa. Can you review and make sure I didn't mess it up?
>Feel free to upload if you think it looks good, otherwise I'll wait for your confirmation.
I think it looks OK. Does it DTRT if you upgrade from a Buster machine
with fwupdate installed?
>> I can see that you've added a Breaks: for the -template packages,
>> but I don't see that helping here. No actual users will ever
>> install the -template packages, they're just for the buildds to
>> use.
>
>Do you think we need to add Breaks to fwupdate-*-signed too then on a fwupdate
>12-8, or will that just complicate thing?
Nah, Breaks doesn't really do anything for us here.
>> 2. Stop building the various fwupdate binary packages (already done)
>>
>> 3. File removal bugs (against ftp.d.o) for the existing
>> fwupdate-*-signed source packages in unstable. That will pull them
>> out from unstable, and that will propagate to testing too.
>>
>> How does that sound? Once we're all done there, we can talk to
>> ftpmaster about removing fwupdate from the special list of allowed
>> -signed packages, but that's not a priority.
>>
>
>Sounds good to me.
\o/
--
Steve McIntyre, Cambridge, UK. steve@einval.com
You lock the door
And throw away the key
There's someone in my head but it's not me
Reply to: