https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260399
Li-Wen Hsu changed:
What|Removed |Added
Assignee|ko...@freebsd.org |b...@freebsd.org
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260399
Julian Noble changed:
What|Removed |Added
CC||jul...@precisium.com.au
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260399
--- Comment #12 from Colin Percival ---
Don't worry about portsnap vs. freebsd-update -- it's basically the same code.
If HTTP requests are getting mangled that's a very clear sign as to where the
problem is. A couple questions about that
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260399
--- Comment #11 from Some Signup ---
My apologies: please note, my last post referred to freebsd-update when on that
occasion I was using portsnap. But I often see the same end result of failed
downloads when using freebsd-update - the symp
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260399
--- Comment #10 from Colin Percival ---
Some quick notes -- sorry, juggling a bunch of stuff right now and won't have
time to debug this properly until later:
1. Getting 404 errors in response to /bp/ requests is normal and harmless.
Port
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260399
--- Comment #9 from Some Signup ---
My apologies for the delay in trying to update my machines. It's such a pain
that I put it off until I can't put it off any longer.
If I run freebsd-update with --debug I get to see thousands of errors
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260399
--- Comment #8 from Graham Perrin ---
(In reply to Some Signup from comment #7)
> … download … patches again. …
Subscribe to bug 257247.
Then this bug 260399 might properly focus on failure to download.
--
You are receiving this mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260399
--- Comment #7 from Some Signup ---
I can run this with --debug.
But there is still no comment on feedback about why it needs to download 7000
patches again. I simply do not believe that that many files are broken during a
download.
--
Y
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260399
--- Comment #6 from Colin Percival ---
Running with --debug would help.
It would also be very useful to know something about the network. I've seen
problems like this with broken "transparent" HTTP proxies.
--
You are receiving this mai
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260399
Kubilay Kocak changed:
What|Removed |Added
Flags|maintainer-feedback?(somesi |maintainer-feedback?(cperci
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260399
--- Comment #4 from Some Signup ---
> Wonder whether particular mirrors are contributory to difficulty.
I don't think so. There are bug reports and posts in various forums from people
all over the place. I doubt they are all hitting the on
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260399
Graham Perrin changed:
What|Removed |Added
CC||grahamper...@gmail.com
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260399
--- Comment #2 from Some Signup ---
It's not related to a version of FreeBSD. It's related solely to freebsd-update
itself (and portsnap).
The simple fact is freebsd-update is not a reliable tool. I am willing to bet
that if I wrote a dead
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260399
Kubilay Kocak changed:
What|Removed |Added
Assignee|b...@freebsd.org|ko...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260399
Kubilay Kocak changed:
What|Removed |Added
CC||somesig...@icloud.com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260399
Kubilay Kocak changed:
What|Removed |Added
Keywords||needs-qa
Status|New
16 matches
Mail list logo
