|
Home > Archive > Debian Developers > January 2005 > circular dependencies and dist-upgrades sarge->woody
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
circular dependencies and dist-upgrades sarge->woody
|
|
| Henning Glawe 2005-01-29, 7:48 am |
| Moin,
I must have some supernatural powers to always attract the same bug: woodys
apt fed too short lists into dpkg and thus broke the configuration of
circular depending packages (Note: "dpkg --configure blah blubb", where blah
depends on blubb and blubb depends on blah works; if you try to run it on
each package seperately, it fails).
Sarge's apt works around this by increasing the list length fed into dpkg.
There is one case in which users can be bitten by this: when using apt-get
dist-upgrade to sarge, so when documenting the woody-sarge upgrade, it should
be at least mentioned that the user can run into this and should first
upgrade apt to solve this problem.
--
c u
henning
| |
| Steve Langasek 2005-01-29, 5:55 pm |
| On Sat, Jan 29, 2005 at 12:24:43PM +0100, Henning Glawe wrote:
> I must have some supernatural powers to always attract the same bug: woodys
> apt fed too short lists into dpkg and thus broke the configuration of
> circular depending packages (Note: "dpkg --configure blah blubb", where blah
> depends on blubb and blubb depends on blah works; if you try to run it on
> each package seperately, it fails).
> Sarge's apt works around this by increasing the list length fed into dpkg.
> There is one case in which users can be bitten by this: when using apt-get
> dist-upgrade to sarge, so when documenting the woody-sarge upgrade, it should
> be at least mentioned that the user can run into this and should first
> upgrade apt to solve this problem.
The release notes currently recommend to use aptitude, not apt-get, for
upgrading from woody to sarge. Do you know if this problem also occurs with
woody's aptitude?
Thanks,
--
Steve Langasek
postmodern programmer
| |
| Adam Heath 2005-01-29, 5:55 pm |
| On Sat, 29 Jan 2005, Steve Langasek wrote:
> On Sat, Jan 29, 2005 at 12:24:43PM +0100, Henning Glawe wrote:
>
>
>
> The release notes currently recommend to use aptitude, not apt-get, for
> upgrading from woody to sarge. Do you know if this problem also occurs with
> woody's aptitude?
Yes, it should, as it uses libapt-pkg to call dpkg.
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Henning Glawe 2005-01-29, 5:55 pm |
| On Sat, Jan 29, 2005 at 02:26:45PM -0800, Steve Langasek wrote:
>
> The release notes currently recommend to use aptitude, not apt-get, for
> upgrading from woody to sarge. Do you know if this problem also occurs with
> woody's aptitude?
I haven't been hit by it yet using aptitude (didn't run aptitude to upgradea
machine).
Quickly browsing through (current) aptitudes source:
download.cc, line 463 calls pkgDPkgPM::DoInstall
which in turn calls libaptpkg's pkgDPkgPM::Go, where the whole problem lives
(it splits dpkg command lines at 'hard' borders (MaxArgs); newer apt works around this
by increasing the command line length, so the probability to split a circular
dependency is lower, but not absent).
Conclusion: as a non-apt(itude)-expert, I think it would be possible to runinto
this problem (maybe someone with better apt(itude) knowledge should have a look
at this).
--
c u
henning
| |
| Martin Schulze 2005-01-31, 5:56 pm |
| Steve Langasek wrote:
>
> The release notes currently recommend to use aptitude, not apt-get, for
> upgrading from woody to sarge. Do you know if this problem also occurs with
> woody's aptitude?
It should most probably be pointed out in the release notes that
upgrading apt-get as first package will work fine as well, unless it
won't. We've had a similar requirement for a former release where
dpkg and/or apt-get needed to be updated first in order to make the
dist-upgrade happen fine.
Otherwise, it would be quite a regression that apt-get won't be
able to handle the dist-upgrade fine anymore.
Regards,
Joey
--
MIME - broken solution for a broken design. -- Ralf Baechle
Please always Cc to me when replying to me on the lists.
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Goswin von Brederlow 2005-01-31, 5:56 pm |
| Martin Schulze <joey@infodrom.org> writes:
> Steve Langasek wrote:
>
> It should most probably be pointed out in the release notes that
> upgrading apt-get as first package will work fine as well, unless it
> won't. We've had a similar requirement for a former release where
> dpkg and/or apt-get needed to be updated first in order to make the
> dist-upgrade happen fine.
>
> Otherwise, it would be quite a regression that apt-get won't be
> able to handle the dist-upgrade fine anymore.
>
> Regards,
>
> Joey
I wonder if this shouldn't be hardcoded into apt-get in some way.
How about this:
If any essential (or only apt + depends) packages are to be updated do
a run installing only the essential packages and their requirements
first. Then restart yourself adding a -y to the options.
This could be combined with a check if a lot of packages (say if it
has to break cycles into multiple dpkg calls) to avoid double runs on
day-to-day updates.
MfG
Goswin
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
|
|
|
|
|