Bug#260146: apt-get update -m does not work anymore
On Sun, Jul 18, 2004 at 04:16:25PM -0700, Matt Zimmerman wrote:
> severity 260146 wishlist
> thanks
>
> On Sun, Jul 18, 2004 at 10:50:30PM +0200, Petr Vandrovec wrote:
>
> > since latest apt-get update my DSelect::UpdateOptions "-m" stopped
> > working, as for unknown reason apt-get update now ignores -m, and always
> > reports error code 100 when some package lists failed to download.
> >
> > I need this feature because not all sites I'm downloading packages from
> > are always up, and currently when this happens, apt internal
> > package list IS updated in such situation, but dselect's list is left
> > alone (which I think is broken itself), not knowing about new and updated
> > packages available.
> >
> > For now I've applied change below - which IMHO is correct thing to do
> > anyway, as both apt and dselect available package lists should be always
> > in sync as much as possible.
> >
> > If you'll apply something like patch below, then I can live without
> > update -m being resurrected. Otherwise please give me option to accept
> > only some downloaded package lists back.
>
> I do not think -m/--fix-missing has ever been applicable to apt-get update.
> As documented, it only applies to the downloading of packages (not package
> indexes).
It worked before last update. I noticed it only after some time as it is
triggered only when connection problems occur (I got offline and tried to
update from disk I move around).
I think that current behavior is unacceptable: package indexes are downloaded,
yet dselect still lists old versions, but if you run apt-get upgrade from
commandline dozens of packages are upgraded. Either throw away both
apt and dselect/dpkg indexes, or update both.
Thanks,
Petr Vandrovec
Reply to: