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

Re: The future (or non-future) of ia32-libs

Luk Claes <luk@debian.org> writes:

> On 06/22/2012 04:31 PM, Roger Leigh wrote:
>> On Fri, Jun 22, 2012 at 09:32:15PM +0800, Thomas Goirand wrote:
>>> On 06/22/2012 05:34 PM, Goswin von Brederlow wrote:
>>>> Step 1: upgrade/dist-upgrade with ia32-libs (wine, ...) held back
>>>> Step 2: dpkg --add-architecture i386 && apt-get update
>>>> Step 3: dist-upgrade (ia32-libs, wine, ... is now installable)
>>> May I suggest that upon upgrade, we have a debconf message telling
>>> about it? We could add this in base-files or any essential package,
>>> probably one with some debconf messages already in would be a better
>>> pick. Instructions would show, IF ia32-libs old version is currently
>>> installed
>>> AND the --add-architecture i386 hasn't bee done.
>>> I know we have release notes, but some don't know about them or would
>>> simply not read them. A debconf message seem really appropriate IMO.
>> Could we not introduce the concept of an "upgrade script" into
>> apt-get which could be downloaded when you run "apt-get update" and
>> then run during a dist-upgrade?  This could handle automation of
>> any "housekeeping" during the upgrade which would otherwise require
>> manual work detailed in the release notes.
> Hmm, I'm not a fan of upgrade scripts at all. Either it's easy enough to
> automate in maintainerscripts or it should get careful review for the
> context in which it will be applied IMHO (which means the sysadmin can
> run the shipped script manually).

Maybe you shouldn't think of this as a script. Rather think of it as
hints for apt/aptitude to do a dist-upgrade in multiple steps. As you
say the maintainer scripts should do the right thing already. So it is
just a matter of splitting up the package list into smaller chunks so the
upgrade process doesn't explode with a few extra actions inbetween

For ia32-libs the extra action would be "dpkg --add-architecture
i386". For the kernel/udev the action might be "reboot". Little things
like that. :)))

In general the upgrade "script" could consist of lists of white/black
lists of package to be processed in each step and debconf messages being
displayed between steps prompting the user to do certain things before

Each time dist-upgrade-by-script is run apt-get would skip all the steps
that produce no change and continue from the first one that does (in
case it was aborted or reboot was needed).

Just an idea. Not that I think this could be done before the freeze.


Reply to: