| Stephen Gran on 25 Dec 2003 22:44:02 -0500 |
|
On Thu, Dec 25, 2003 at 09:59:21PM -0500, Jeff Abrahamson said: > BTW, I did an upgrade, didn't solve the problem, so I started doing > apt-get install on individual things. First one caused a glibc > upgrade. When that was done, everything else was happy to upgrade. > > Weird only that the dependency graph couldn't get around that. As another Debian maintainer, Andrew Suffield, frequently says, "dpkg sucks. It just sucks slightly less than other systems." glibc major-version upgrades are probably the hardest dependency graph to throw at dpkg, so that's where it performs most poorly. I recommend filing a bug report on the package 'upgrade-reports', detailing your experiences - this is clearly somthing that's going to happen frequently in the woody to sarge upgrade process, so it should go in the release notes. Letting them know is the best way to get it in. BTW, I don't know how often you file bugs, but `reportbug -M upgrade-reports` will let you file the bug from the comfort of mutt, after checking for other open bug reports, so that you know you're not filing a duplicate. Sweet. -- -------------------------------------------------------------------------- | Stephen Gran | <Diziet> Fuck, I can't compile the damn | | steve@lobefin.net | thing and I wrote it ! | | http://www.lobefin.net/~steve | | -------------------------------------------------------------------------- Attachment:
pgpSMYyBM0X1M.pgp
|
|