I have filed bug 1709603 to track my request of having "apt update"
called automatically, as really it's independent of Scott's request for
--is-necessary here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
ht
> IMHO, in the use case for "apt install", "apt update" should be
considered an implementation detail and the user shouldn't need to call
it directly. "apt install" should just do the right thing.
Here's basically the same opinion with some commentary from others:
https://twitter.com/chr1sa/status
On Thu, Jul 06, 2017 at 01:32:00PM -, Julian Andres Klode wrote:
> I think automatic updating on old caches is not really the best idea,
> because it will always happen when you expect it the least. Or maybe you
> do in fact want the old one.
>From the perspective of users, I absolutely disagr
I think automatic updating on old caches is not really the best idea,
because it will always happen when you expect it the least. Or maybe you
do in fact want the old one.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apt (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/
IMHO, in the use case for "apt install", "apt update" should be
considered an implementation detail and the user shouldn't need to call
it directly. "apt install" should just do the right thing. The same
applies to "apt-cache search", etc. It's seems quite tedious and
unnecessary to have to run bot
$ echo "now: $(TZ=GMT date)"; wget -S -q
http://azure.archive.ubuntu.com/ubuntu/dists/vivid/Release -O /dev/null
now: Fri Apr 3 14:37:31 GMT 2015
HTTP/1.1 200 OK
Date: Fri, 03 Apr 2015 14:37:31 GMT
Server: Apache/2.2.22 (Ubuntu)
Last-Modified: Fri, 03 Apr 2015 14:28:00 GMT
ETag: "34f32-
ähm, did you realize that "Expires" is the exact time of your request
(compare "Date") in your example? (See also the HTTP1.1 spec which will
tell you that 'Expires' doesn't really mean what you think it does, so
that the value it has is actually 'okay').
APT is using If-Modified-Since in its requ
Just realized, that ideally 'apt-get update' would respect headers that were
put in place by the source.
$ wget -S -q http://azure.archive.ubuntu.com/ubuntu/dists/vivid/Release -O
/dev/null
HTTP/1.1 200 OK
Date: Tue, 31 Mar 2015 13:32:55 GMT
Server: Apache/2.2.22 (Ubuntu)
Last-Modified: T
9 matches
Mail list logo