[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Renaming packages: maintscripts

On 02.09.2012 21:21, Salvatore Bonaccorso wrote:
>> Basically I want to ensure that if one installs package B to
>> a system with A installed, A should be upgraded to A' at the
>> same time.  This works when upgrading A to A' (satisfying A'
>> dependency and installing B), but does not work when installing
>> B alone when A is installed.
>> Only this way it is possible to work around old maintscripts
>> in the renamed package.
>> But I don't see a way to satisfy this.  Something I didn't think
>> of ?
> I see in the paragraph above you talk about Breaks. Do you also have
> an according Replaces in place? See [1] and [2].
>  [1]: http://wiki.debian.org/Renaming_a_Package
>  [2]: http://www.debian.org/doc/debian-policy/ch-relationships.html#s7.6.1
> Does this helps?

The current issue I have is #686146, the talk is about autofs5 => autofs
rename.  The OP of #686146 installed new autofs ("B" above), and his
system now have

   ii  autofs            5.0.6-2
   pc  autofs5           5.0.4-3.2+b1

Autofs is new package.  Its control info:

Package: autofs
Architecture: any
Pre-Depends: ${misc:Pre-Depends}
Depends: ${shlibs:Depends}, ${misc:Depends}, ucf
Provides: autofs5
Breaks: autofs5 (<< 5.0.6-1~)
Replaces: autofs5 (<< 5.0.6-1~)

So it both replaces and breaks old autofs5.

But the OP system does not have old autofs5 package installed,
only the config files from it, and the maintscripts.  Which is
exactly the problem.

I want to ensure that if old autofs5 is installed, installing
new autofs should pull new autofs5 TOO.

The only way currently I see to do it is to declare autofs
as DEPENDING on autofs5.  This is obviously ugly, but it will
save from this very situation, and I don't see any other way.
Is there?



Reply to: