> Hi
>
> Is anybody else experiencing problems svn up'ing? i get "svn: Connection
> closed unexpectedly" all the time.

I am behind a proxy too. I don't know of any limitations on the number of
upgraders, but I have probably never tried to run more than one upgrade at
the same time.

I checked the console log from my most recent bootstrapping exercise,
there were indeed two "svn: Connection closed unexpectedly" messages.
Because of the proxy I have wrapped the "emerge --sync" in a script that
inserts proxy parameters into the ~/.subversion/servers file and retries;
apparently the script failed due to its retry count reaching the limit. I
will refine the wrapper script so that this does not passed undetected in
the future.

--Rabbe


--
gentoo-alt@lists.gentoo.org mailing list

Duft Markus <mailto:Markus.Duft@salomon.at> wrote:
> Hi
>
> Is anybody else experiencing problems svn up'ing? i get "svn:
> Connection closed unexpectedly" all the time.

hah, seems that switching the svn checkout to https workes around this
for now: "svn switch --relocate
svn://overlays.gentoo.org/proj/alt/trunk/prefix-overlay
https://overlays.gentoo.org/svn/proj/alt/trunk/prefix-overlay". Now i
can update again without any problems.

>
> Also something i have noticed before: we're behind a proxy, and it
> seems that only one at a time can update (if it works...), all others
> get that "svn: Connection closed unexpectedly" message too. Can this
> have something to do with the server, or is it more probably a company
> network setup problem?

it seems that the switch to https also solved this problem. i don't know
why the portage ebuild says that only devs should switch there (i'm just
about to become a dev....), is there any obvious reason i'm missing?

>
> Cheers, Markus

--
gentoo-alt@lists.gentoo.org mailing list

On 07-04-2008 14:45:39 +0200, Duft Markus wrote:
> Duft Markus <mailto:Markus.Duft@salomon.at> wrote:
> > Hi
> >
> > Is anybody else experiencing problems svn up'ing? i get "svn:
> > Connection closed unexpectedly" all the time.
>
> hah, seems that switching the svn checkout to https workes around this
> for now: "svn switch --relocate
> svn://overlays.gentoo.org/proj/alt/trunk/prefix-overlay
> https://overlays.gentoo.org/svn/proj/alt/trunk/prefix-overlay". Now i
> can update again without any problems.
>
> >
> > Also something i have noticed before: we're behind a proxy, and it
> > seems that only one at a time can update (if it works...), all others
> > get that "svn: Connection closed unexpectedly" message too. Can this
> > have something to do with the server, or is it more probably a company
> > network setup problem?
>
> it seems that the switch to https also solved this problem. i don't know
> why the portage ebuild says that only devs should switch there (i'm just
> about to become a dev....), is there any obvious reason i'm missing?

infra--




--
Fabian Groffen
Gentoo on a different level
--
gentoo-alt@lists.gentoo.org mailing list

> Duft Markus <mailto:Markus.Duft@salomon.at> wrote:
>> Hi
>>
>> Is anybody else experiencing problems svn up'ing? i get "svn:
>> Connection closed unexpectedly" all the time.
>
> hah, seems that switching the svn checkout to https workes around this
> for now: "svn switch --relocate
> svn://overlays.gentoo.org/proj/alt/trunk/prefix-overlay
> https://overlays.gentoo.org/svn/proj/alt/trunk/prefix-overlay". Now i
> can update again without any problems.
>
>>
>> Also something i have noticed before: we're behind a proxy, and it
>> seems that only one at a time can update (if it works...), all others
>> get that "svn: Connection closed unexpectedly" message too. Can this
>> have something to do with the server, or is it more probably a company
>> network setup problem?
>
> it seems that the switch to https also solved this problem. i don't know
> why the portage ebuild says that only devs should switch there (i'm just
> about to become a dev....), is there any obvious reason i'm missing?

The "svn switch" trick worked for me too.

--Rabbe Fogelholm

--
gentoo-alt@lists.gentoo.org mailing list