Bug 280472 – app-portage/layman - repositories inaccessible behind firewall that only allows http

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Jonathan Manning 2009-08-05 16:11:32 UTC]

Over the last 6-12 months, many repos listed by 'layman -L' have converted from (svn and git over) http: to svn: or git: protocol.
As a result, I am no longer able to sync these at $WORK behind a restrictive firewall that only allows outbound http/https.
All repos on o.g.o are also available via http, so there is no reason these have to be accessed via non-http methods. 
Please consider a way to provide alternate (fallback?) urls, or a config option to force http in layman.

Fix would be either in layman or in  http://www.gentoo.org/proj/en/overlays/layman-global.txt (or both).

Examples for o.g.o:
s{svn://overlays.gentoo.org/}{http://overlays.gentoo.org/svn/}
s{git://git.overlays.gentoo.org/}{http://git.overlays.gentoo.org/gitroot/}

As a workaround, I'm maintaining my own user.xml file with converted versions of the repositories I use - however I'll have to manually maintain this list if these repos move.

[Comment 1 Gunnar Wrobel (RETIRED) 2009-10-12 14:52:50 UTC]

*** Bug 284187 has been marked as a duplicate of this bug. ***

[Comment 2 Sebastian Pipping 2009-12-29 12:06:55 UTC]

(In reply to comment #0)
> Please consider a way to provide alternate (fallback?) urls, or a config option
> to force http in layman.
> 
> Fix would be either in layman or in 
> http://www.gentoo.org/proj/en/overlays/layman-global.txt (or both).

The layman-global.txt part is done by now: The successor format "repositories.xml" supports alternative sources:

 <source type="git">git://git.overlays.gentoo.org/dev/alexxy.git</source>
 <source type="git">http://git.overlays.gentoo.org/gitroot/dev/alexxy.git</source>
 <source type="git">git+ssh://[e-mail]/dev/alexxy.git</source>

The next step needed is to have Layman look let you choose from that. I have an option --prefer-http in mind. Please let me know if you plan to hack on that yourself before I do. The layman Git repo is up on SourceForge: <http://sourceforge.net/projects/layman/>

[Comment 3 Sebastian Pipping 2010-01-13 02:16:59 UTC]

work in progress, stay tuned.

[Comment 4 Sebastian Pipping 2010-01-14 23:18:58 UTC]

I'm just doing some testing here with a firewall blocking outgoing connections to port 9418 for Git.  With that blocking rule enabled running

  git clone "git://git.overlays.gentoo.org/dev/dberkholz"

seems to never return.  With the new try-next-URI-until-success approach this will never get past the first URI.  Any ideas on how to force failure in such a case, i.e. to make Git abort when a firewall is blocking it?  (Killing the command after a timeout is a no-go to me.)

[Comment 5 Sebastian Pipping 2010-01-15 18:36:52 UTC]

layman-1.3.0_rc1 supporting try-next-URI-until-success is out now.
therefore this bug's original request has been filled - closing.  if you run into
trouble with it i would like you to open new bugs for it.

in any case i would like to hear how 1.3.0_rc1 is working for you.
please drop me a mail if you have a minute.