On Thu, Oct 17, 2019 at 11:38:42AM -0400, rhkra...@gmail.com wrote:
> On Thursday, October 17, 2019 05:25:46 AM to...@tuxteam.de wrote:
> > On Thu, Oct 17, 2019 at 11:08:34AM +0200, to...@tuxteam.de wrote:
> >
> > [...]
> >
> > > [1] https://news.ycombinator.com/item?id=19507225
> >
> > Sorry.
On Thursday, October 17, 2019 05:25:46 AM to...@tuxteam.de wrote:
> On Thu, Oct 17, 2019 at 11:08:34AM +0200, to...@tuxteam.de wrote:
>
> [...]
>
> > [1] https://news.ycombinator.com/item?id=19507225
>
> Sorry. That link forces you through Twitter. Here are better
> ones:
>
>
Art Sackett wrote:
>
> > As for transparent proxies, etc. what I've got here is
>
> ... egg on my face. Never mind...
We've all been there.
Please tell us what, exactly, for the benefit of the archives
and future searchers.
-dsr-
> As for transparent proxies, etc. what I've got here is
... egg on my face. Never mind...
--
Art Sackett
http://www.artsackett.com/
Quoting Art Sackett (2019-10-17 16:01:54)
> On Thu, Oct 17, 2019 at 08:54:36AM -, Curt wrote:
>
> > By what mental procedure did you arrive at that workaround?
>
> I was able to retrieve the various InRelease files with any web
> browser and with wget, but I was not able to do so with apt.
On Thu, Oct 17, 2019 at 08:54:36AM -, Curt wrote:
> By what mental procedure did you arrive at that workaround?
I was able to retrieve the various InRelease files with any web browser
and with wget, but I was not able to do so with apt. So, I cranked up
tcpdump and grabbed one of those files
On Thu, Oct 17, 2019 at 12:15:21PM -, Curt wrote:
[...]
> Still, I don't get why a Debian apt repository would require some recent
> browser user agent string to permit ingress; something seems to be
> missing from this picture.
Definitely. My bet at the moment is on a (ISP?) transparent
On Thu, Oct 17, 2019 at 12:15:21PM -, Curt wrote:
> On 2019-10-17, wrote:
[...]
> > IMO this sounds a bit too harsh [...]
> I didn't mean it to be harsh, sorry. I only meant that that bug is the
> OP's bug report concerning the very bug in this thread and not
> some reference to a known
On 2019-10-17, wrote:
>
>
>> > This is Debian bug #942478:
>> This is you and your bug.
>
> IMO this sounds a bit too harsh. The OP seems to be seeing this
> behaviour -- perhaps it's not an apt (or a Debian mirror) problem,
> but it'd be nice to know...
I didn't mean it to be harsh, sorry. I
On 2019-10-17 09:54, Curt wrote:
On 2019-10-16, Art Sackett wrote:
For any who've found this thread by searching for the problem they're
having, the workaround is to create the file
/etc/apt/apt.conf.d/99useragent and populate it with:
Acquire
{
http::User-Agent "Mozilla/5.0 (X11; Linux
On Thu, Oct 17, 2019 at 11:08:34AM +0200, to...@tuxteam.de wrote:
[...]
> [1] https://news.ycombinator.com/item?id=19507225
Sorry. That link forces you through Twitter. Here are better
ones:
https://old.lwn.net/Articles/784758/
On Thu, Oct 17, 2019 at 08:54:36AM -, Curt wrote:
> On 2019-10-16, Art Sackett wrote:
> > For any who've found this thread by searching for the problem they're
> > having, the workaround is to create the file
> > /etc/apt/apt.conf.d/99useragent and populate it with:
> >
> > Acquire
> > {
> >
On 2019-10-16, Art Sackett wrote:
> For any who've found this thread by searching for the problem they're
> having, the workaround is to create the file
> /etc/apt/apt.conf.d/99useragent and populate it with:
>
> Acquire
> {
> http::User-Agent "Mozilla/5.0 (X11; Linux x86_64; rv:60.0)
On Wed, Oct 16, 2019 at 05:55:55PM -0600, Art Sackett wrote:
> For any who've found this thread by searching for the problem they're
> having, the workaround is to create the file
> /etc/apt/apt.conf.d/99useragent and populate it with:
>
> Acquire
> {
> http::User-Agent "Mozilla/5.0 (X11; Linux
On Wed, 16 Oct 2019 17:55:55 -0600
Art Sackett wrote:
> For any who've found this thread by searching for the problem they're
> having, the workaround is to create the file
> /etc/apt/apt.conf.d/99useragent and populate it with:
>
> Acquire
> {
> http::User-Agent "Mozilla/5.0 (X11; Linux
For any who've found this thread by searching for the problem they're
having, the workaround is to create the file
/etc/apt/apt.conf.d/99useragent and populate it with:
Acquire
{
http::User-Agent "Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
Firefox/60.0";
};
This changes apt's
Greetings:
I've been seeing 'apt update' failures since yesterday:
# apt update
Err:1 http://ftp.us.debian.org/debian stable InRelease
Connection failed [IP: 128.61.240.89 80]
Err:2 http://security.debian.org/debian-security buster/updates InRelease
Connection failed [IP:
17 matches
Mail list logo