On Fri, 2004-08-06 at 04:26, J.H.M. Dassen (Ray) wrote: > > > As with #263544, I've failed to reproduce this. Please provide a more > > > detailed recipe for reproducing the problem. Is the problem reproducible > > > if as the first step of upgrading to sarge you do "apt-get install apt"? > > > If so, does it help to set Dpkg::MaxArgBytes to a large value, say > > > 31000? > > > > Thanks Ray-- good call. Creating apt.conf with the above and upgrading > > apt before the dist-upgrade fixed the problem. > > Is it possible for you to retest this upgrade path? If so, it would be quite > useful to know whether a change of Dpkg::MaxArgBytes is really necessary, or > whether it's sufficient to just upgrade to sarge's apt first thing.
Simply upgrading apt is enough. To give some perspective, here is what is happening during the upgrade: 716 upgraded, 241 newly installed, 17 downgraded, 86 to remove and 2 not upgraded. I also did it without using apt-pinning in /etc/apt/preferences (ie so none were downgraded). This went fine too. Jamie -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
