Custom Query (1145 matches)

Reported by broder, 14 years ago.

The rules for -development and the rules for auto-update conflict with each other.

auto-update assumes a world with apt repository semantics, where version numbers are monotonically increasing.

-development assumes a world where things can be arbitrarily broken, and where we don't have to fix them later, where there's no guarantee we won't scribble over your harddrive, and where version numbers are convenient labels that we can change and re-write as we please.

This does bad things when, say, I upload a package to -development specifically because I expect it to break things, and then auto-update goes and installs it on a bunch of workstations.

auto-update should refuse to run if -development is enabled, because there are simply no guarantees that the end result will be a sane one.

Reported by broder, 14 years ago.

On cluster machines, auto-update should set UCF_FORCE_CONFFNEW for the same reason we're passing --force-confnew.

Reported by jdreed, 12 years ago.

mkc says: jdreed@infinite-loop:~$ athinfo mkc update-status 1340340629|1346103369|warning|Failed to contact mirror(s):  http://dl.google.com/linux/chrome/deb/

Google's APT repo doesn't serve a directory listing. We should either restrict the check to our mirrors, or fetch Release, or just log a soft failure or something.