Re: Bug#137019: debconf: apt can't dist-upgrade properly from potato with debconf-tiny installed

[Colin Watson <cjwatson@debian.org>]

On Wed, Mar 06, 2002 at 11:45:06AM -0500, Joey Hess wrote:
> Colin Watson wrote:
> > debconf (>= 1.0) is fine - I picked Source-Version for no particularly
> > good reason (possibly because I was thinking that debconf would have to
> > be changed anyway to version the conflicts). Actually, experimenting,
> > all I need to do is add a debconf-tiny package which doesn't provide
> > debconf and has no other interesting characteristics, and it works.
> > Depending on a newer-than-potato version of debconf is just an insurance
> > policy.
> 
> Ok, in incoming or wherever new packages go these days. Please let me
> know if it doesn't work.

Thanks!

> You mentioned earlier that you thought debconf needed to not conflict
> with the new debconf-tiny. Is that still your thinking? I'm not sure
> from the paragraph above.

If the conflict stays, the new debconf-tiny will be uninstallable ...
sorry, re-reading my paragraph above I realize it was unclear.

I just tried it out (inserting the metadata from the new debconf-tiny
package into my local Packages file without changing the current
unversioned conflicts in debconf), and the effect in my case was that
apt decided to hold back the old debconf-tiny and not install debconf in
its place - so yes, versioning the conflicts seems to be necessary.

[root@arborlon /]# apt-get -o Debug::pkgProblemResolver=1 dist-upgrade
Reading Package Lists... Done
Building Dependency Tree... Done
Calculating Upgrade... Starting
Starting 2
Package debconf has broken dep on debconf-tiny
  Considering debconf-tiny -1 as a solution to debconf 69
  Considering debconf-tiny -1 as a solution to debconf 69
Package console-common has broken dep on debconf
  Considering debconf 69 as a solution to console-common 14
  Holding Back console-common rather than change debconf
[...]
Package fbset has broken dep on debconf
  Considering debconf 69 as a solution to fbset 0
  Holding Back fbset rather than change debconf
Package debconf-tiny has broken dep on debconf
  Considering debconf 69 as a solution to debconf-tiny -1
  Holding Back debconf-tiny rather than change debconf
Package groff-base has broken dep on groff
  Considering groff 5 as a solution to groff-base 10
  Fixing groff-base via remove of groff
[...]
Done
The following packages will be REMOVED:
  base-config console-tools groff locales man-db 
The following NEW packages will be installed:
  autoconf2.13 autotools-dev cpp-2.95 emacsen-common g++-2.95 gcc-2.95
  groff-base html2text ifupdown klogd libcap1 libdb3 libldap2 libpcap0
  libpcre3 libsasl7 libstdc++2.10-glibc2.2 net-tools netkit-inetd netkit-ping
  perl perl-modules 
The following packages have been kept back
  console-data debconf-tiny debhelper libpaperg lilo netbase vim 

When I made debconf conflict with debconf-tiny (<< 1.0), I got:

[root@arborlon /]# apt-get -o Debug::pkgProblemResolver=1 dist-upgrade
Reading Package Lists... Done
Building Dependency Tree... Done
Calculating Upgrade... Starting
Starting 2
Package vim has broken dep on vim-rt
  Considering vim-rt 0 as a solution to vim 0
  Holding Back vim rather than change vim-rt
 Try to Re-Instate vim
Done
Done
The following NEW packages will be installed:
  autoconf2.13 autotools-dev console-common cpp-2.95 debconf debconf-utils
  emacsen-common g++-2.95 gcc-2.95 groff-base html2text ifupdown ipchains
  klogd libcap1 libdb3 libldap2 libpcap0 libpcre3 libsasl7
  libstdc++2.10-glibc2.2 net-tools netkit-inetd netkit-ping perl perl-modules 
The following packages have been kept back
  vim 

-- 
Colin Watson                                  [cjwatson@flatline.org.uk]