View previous topic :: View next topic |
Author |
Message |
ONEEYEMAN Advocate

Joined: 01 Mar 2005 Posts: 3681
|
Posted: Sun Dec 20, 2015 9:07 pm Post subject: GitHub issue with Layman |
|
|
Hi,
Could someone please explain this?
Code: |
IgorDellGentoo igor # layman -a rainyday
* Adding overlay,...
* Warning: an installed db file was not found at: ['/var/lib/layman/installed.xml']
* Running Git... # ( cd /var/lib/layman && /usr/bin/git clone git://github.com/iegor/rainyday.git /var/lib/layman/rainyday )
Cloning into '/var/lib/layman/rainyday'...
fatal: unable to connect to github.com:
github.com[0: 192.30.252.129]: errno=Connection timed out
* Failure result returned from Git
* Running Git... # ( cd /var/lib/layman/rainyday && /usr/bin/git config user.name "layman" )
* [Errno 2] No such file or directory: '/var/lib/layman/rainyday'
* Adding repository "rainyday" failed!
* Warning: an installed db file was not found at: ['/var/lib/layman/installed.xml']
* CLI: Errors occurred processing action add
* Adding repository "rainyday" failed!
IgorDellGentoo igor # ping -c 3 github.com
PING github.com (192.30.252.130) 56(84) bytes of data.
--- github.com ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 1999ms
IgorDellGentoo igor # cd wxWidgets
IgorDellGentoo wxWidgets # git pull
remote: Counting objects: 874, done.
remote: Compressing objects: 100% (24/24), done.
remote: Total 874 (delta 608), reused 596 (delta 596), pack-reused 254
Receiving objects: 100% (874/874), 276.74 KiB | 0 bytes/s, done.
Resolving deltas: 100% (671/671), completed with 294 local objects.
From https://github.com/wxWidgets/wxWidgets
363492e..5524cec master -> origin/master
80ceca1..8cea217 WX_3_0_BRANCH -> origin/WX_3_0_BRANCH
|
Thank you. |
|
Back to top |
|
 |
ONEEYEMAN Advocate

Joined: 01 Mar 2005 Posts: 3681
|
Posted: Tue Dec 22, 2015 10:13 pm Post subject: |
|
|
Anyone?
Thank you. |
|
Back to top |
|
 |
Ant P. Watchman

Joined: 18 Apr 2009 Posts: 6920
|
Posted: Wed Dec 23, 2015 12:05 am Post subject: |
|
|
layman is using git protocol, the one that works is using https. Are you behind a broken firewall maybe? |
|
Back to top |
|
 |
ONEEYEMAN Advocate

Joined: 01 Mar 2005 Posts: 3681
|
Posted: Wed Dec 23, 2015 5:28 am Post subject: |
|
|
Hi, Ant.P
I checked and my modem+router firewall is set up for the "Highest" security settings.
I was able to open port 9148 and 22 which are used by git protocol, however, I still receive "Connection timed out" message.
Also, I do wonder how to check if I have a firewall running? I'm sure I'm not, but just in case...
Thank you. |
|
Back to top |
|
 |
quilosaq Veteran

Joined: 22 Dec 2009 Posts: 1575
|
Posted: Thu Dec 24, 2015 2:42 am Post subject: |
|
|
ONEEYEMAN wrote: | I was able to open port 9148... | I think that the git protocol uses the 9418 port on server. Not 9148. |
|
Back to top |
|
 |
ONEEYEMAN Advocate

Joined: 01 Mar 2005 Posts: 3681
|
Posted: Thu Dec 24, 2015 4:04 am Post subject: |
|
|
Hi, quilosaq,
I just rechecked and the port opened is 9418. That is my mistake/typo.
Thank you. |
|
Back to top |
|
 |
quilosaq Veteran

Joined: 22 Dec 2009 Posts: 1575
|
Posted: Thu Dec 24, 2015 2:01 pm Post subject: |
|
|
Check if you can clone the repo manualy:
Code: | mkdir /tmp/foo && cd /tmp/foo && /usr/bin/git clone git://github.com/iegor/rainyday.git |
if it does not work try this:
Code: | mkdir /tmp/foo01 && cd /tmp/foo01 && /usr/bin/git clone https://github.com/iegor/rainyday.git |
|
|
Back to top |
|
 |
DONAHUE Watchman


Joined: 09 Dec 2006 Posts: 7651 Location: Goose Creek SC
|
Posted: Thu Dec 24, 2015 4:38 pm Post subject: |
|
|
Quote: | layman -a rainyday
ping -c3 github.om
ping -c3 192.30.252.129 | All work without problems for me. Quote: | Warning: an installed db file was not found at: ['/var/lib/layman/installed.xml'] | suggests layman installation/configuration problems. I would manually create the empty file:/var/lib/layman/installed.xml and try the command again. https://wiki.gentoo.org/wiki/Layman refers. Quote: | github.com[0: 192.30.252.129]: errno=Connection timed out
--- github.com ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 1999ms | Suggest you had no internet connection or no dns service or a firewall or proxy was blocking git and ping protocols at the time. _________________ Defund the FCC. |
|
Back to top |
|
 |
ONEEYEMAN Advocate

Joined: 01 Mar 2005 Posts: 3681
|
Posted: Thu Dec 24, 2015 11:51 pm Post subject: |
|
|
quilosaq wrote: |
Check if you can clone the repo manualy:
Code: |
mkdir /tmp/foo && cd /tmp/foo && /usr/bin/git clone git://github.com/iegor/rainyday.git
|
|
This didn't work, however,
quilosaq wrote: |
if it does not work try this:
Code: |
mkdir /tmp/foo01 && cd /tmp/foo01 && /usr/bin/git clone https://github.com/iegor/rainyday.git
|
|
this worked.
So, can I reconfigure layman to include http access?
Thank you. |
|
Back to top |
|
 |
dol-sen Retired Dev


Joined: 30 Jun 2002 Posts: 2805 Location: Richmond, BC, Canada
|
Posted: Fri Dec 25, 2015 1:06 am Post subject: |
|
|
Layman will first try the git:// url, then an https:// one, etc.. until one works. That is provided the overlay definition included all the variations github is capable of, if not you can create a new definition using layman-overlay-maker to create a new definition with all the protocols gitkub supports. It will include them all automatically for github, gentoo, and I think gitorious.
Also, if it does not have the other protocol urls, please file a bug with teh overlays team to update it with them.
You might want to re-sort the protocol order and put the https one first for yourself. If not, it should cyle through all listed urls until one works before giving up. After that it will keep re-using that same one unless that url is removed from the list. _________________ Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch... |
|
Back to top |
|
 |
ONEEYEMAN Advocate

Joined: 01 Mar 2005 Posts: 3681
|
Posted: Fri Dec 25, 2015 1:52 am Post subject: |
|
|
dol-sen,
dol-sen wrote: |
Layman will first try the git:// url, then an https:// one, etc.. until one works. That is provided the overlay definition included all the variations github is capable of, if not you can create a new definition using layman-overlay-maker to create a new definition with all the protocols gitkub supports. It will include them all automatically for github, gentoo, and I think gitorious.
Also, if it does not have the other protocol urls, please file a bug with teh overlays team to update it with them.
|
Could you tell me how to do that? And where do I check for missing protocol?
dol-sen wrote: |
You might want to re-sort the protocol order and put the https one first for yourself. If not, it should cyle through all listed urls until one works before giving up. After that it will keep re-using that same one unless that url is removed from the list.
|
I presume this is somewhere in the layman configuration file?
Thank you. |
|
Back to top |
|
 |
dol-sen Retired Dev


Joined: 30 Jun 2002 Posts: 2805 Location: Richmond, BC, Canada
|
Posted: Fri Dec 25, 2015 4:54 pm Post subject: |
|
|
Quote: | And where do I check for missing protocol? |
layman (-i|--info) (ALL|OVERLAY)
Quote: | Could you tell me how to do that? |
Code: | $ layman-overlay-maker -h
* Warning: an installed db file was not found at: ['/var/lib/layman/cache_930c3ed4a5f89f74fd810585751a06e3.xml']
usage: layman-overlay-maker [-h] [-l] [-n]
[-s SET_AUTOCOMPLETE [SET_AUTOCOMPLETE ...]] [-S]
[-V]
Layman's utility script to create overlay definitions.
optional arguments:
-h, --help show this help message and exit
-l, --list-autocomplete
Lists all available mirrors supported for information
auto-completion
-n, --no-extra Don't add any extra overlay info, just the bare
minimum requirements
-s SET_AUTOCOMPLETE [SET_AUTOCOMPLETE ...], --set-autocomplete SET_AUTOCOMPLETE [SET_AUTOCOMPLETE ...]
Enables auto-completion support for the selected
mirror. Specify "ALL" to enable support for all
available mirrors
-S, --sudo Bypass checks to see if an overlay name being inputted
is already being used and choose the installation dir
for the XML
-V, --version show program's version number and exit
brian@professor-x ~/Dev/git/catalyst $
|
Basically, you just run it and answer the questions. It then creates a proper xml definition for you. And yes, it will add all supported urls' with just the one url input.
Quote: | I presume this is somewhere in the layman configuration file? |
No, but close. /etc/layman/overlays is where you would put definition files for overlays not in the repostitories list.
Just load up the file in an editor and re-arrange the sources putting the https:// url first. If you don't it will just try the first one, when it fails it will try the next,... _________________ Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch... |
|
Back to top |
|
 |
ONEEYEMAN Advocate

Joined: 01 Mar 2005 Posts: 3681
|
Posted: Fri Dec 25, 2015 6:01 pm Post subject: |
|
|
dol-sen.
dol-sen wrote: |
Quote: |
And where do I check for missing protocol?
|
layman (-i|--info) (ALL|OVERLAY)
|
Code: |
igor@IgorDellGentoo /tmp/foo01 $ layman -i rainyday
* rainyday
* ~~~~~~~~
* Source : git://github.com/iegor/rainyday.git
* Contact : Iegor <rmtdev@gmail.com>
* Type : Git; Priority: 50
* Quality : experimental
*
* Description:
* Iegor's ebuilds
*
* Link:
* https://github.com/iegor/rainyday
*
* Feed:
* https://github.com/iegor/rainyday/commits/master.atom
*
|
I don't understand - it looks like the overlay link refers to http protocol...
dol-sen wrote: |
Quote: |
Could you tell me how to do that?
|
Code: |
$ layman-overlay-maker -h
* Warning: an installed db file was not found at: ['/var/lib/layman/cache_930c3ed4a5f89f74fd810585751a06e3.xml']
usage: layman-overlay-maker [-h] [-l] [-n]
[-s SET_AUTOCOMPLETE [SET_AUTOCOMPLETE ...]] [-S]
[-V]
Layman's utility script to create overlay definitions.
optional arguments:
-h, --help show this help message and exit
-l, --list-autocomplete
Lists all available mirrors supported for information
auto-completion
-n, --no-extra Don't add any extra overlay info, just the bare
minimum requirements
-s SET_AUTOCOMPLETE [SET_AUTOCOMPLETE ...], --set-autocomplete SET_AUTOCOMPLETE [SET_AUTOCOMPLETE ...]
Enables auto-completion support for the selected
mirror. Specify "ALL" to enable support for all
available mirrors
-S, --sudo Bypass checks to see if an overlay name being inputted
is already being used and choose the installation dir
for the XML
-V, --version show program's version number and exit
brian@professor-x ~/Dev/git/catalyst $
|
Basically, you just run it and answer the questions. It then creates a proper xml definition for you. And yes, it will add all supported urls' with just the one url input.
Quote: |
I presume this is somewhere in the layman configuration file?
|
No, but close. /etc/layman/overlays is where you would put definition files for overlays not in the repostitories list.
Just load up the file in an editor and re-arrange the sources putting the https:// url first. If you don't it will just try the first one, when it fails it will try the next,...
|
I will run that command and/or change the configuration after you explain the issue with the URL.
Thank you. |
|
Back to top |
|
 |
dol-sen Retired Dev


Joined: 30 Jun 2002 Posts: 2805 Location: Richmond, BC, Canada
|
Posted: Sat Dec 26, 2015 4:17 am Post subject: |
|
|
I can't explain it other than to say, check your layman.cfg file for any proxy settings, also check your environment for them. Layman will grab proxy settings from the environment if they exist.
This has happened a couple times to people over the years, but it isn't due to layman that I've been able to find or others able to prove. It works for 99.8% of all users (guesstimate) _________________ Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch... |
|
Back to top |
|
 |
ONEEYEMAN Advocate

Joined: 01 Mar 2005 Posts: 3681
|
Posted: Sat Dec 26, 2015 5:00 am Post subject: |
|
|
Hi, doi-sen,
Here is my /etc/;ayman/layman.cfg. See anything wrong here?
Code: |
[MAIN]
#-----------------------------------------------------------
# Defines the directory where overlays should be installed
storage : /var/lib/layman
#-----------------------------------------------------------
# Remote overlay lists will be stored here
# layman will append _md5(url).xml to each filename
cache : %(storage)s/cache
#-----------------------------------------------------------
# The list of locally installed overlays
installed: %(storage)s/installed.xml
# This has been renamed from the following
# old name : value use it for updating to new one above
# local_list: %(storage)s/overlays.xml
# either rename the overlays.xml file to installed.xml
# or edit the value above to the current name of your
# installed overlay(s) file.
#-----------------------------------------------------------
# Path to the make.conf file that should be modified by
# layman
make_conf : %(storage)s/make.conf
# Repository config types used by layman
# (repos.conf, make.conf)
conf_type : make.conf
#-----------------------------------------------------------
# URLs of the remote lists of overlays (one per line) or
# local overlay definitions
#
#overlays : http://www.gentoo.org/proj/en/overlays/repositories.xml
# http://dev.gentoo.org/~wrobel/layman/global-overlays.xml
# http://mydomain.org/my-layman-list.xml
# file:///var/lib/layman/my-list.xml
overlays : http://www.gentoo.org/proj/en/overlays/repositories.xml
#-----------------------------------------------------------
# The directory to scan for xml overlay definition files to include
# in the list of available overlays. They are automatically added to the
# "overlays" parameter above. Use either method, but do not add the same
# definition in both.
#
#overlay_defs : /etc/layman/overlays
#-----------------------------------------------------------
# Proxy support
# If unset, layman will use the http_proxy environment variable.
#
#proxy : http://[user:pass@]www.my-proxy.org:3128
#-----------------------------------------------------------
# Strict checking of overlay definitions
#
# The nocheck option is a bit confusing, for historical reasons.
# Hopefully this description eases the double negation trouble:
#
# nocheck : yes
# - Accepts complete overlay entries without warnings
# - Lists overlays of type foo (say Git) even with no foo installed
#
# nocheck : no
# - Checks overlay entries for missing description or contact
# information and issue warnings as needed
# - Hides overlays of type foo (say Git) if foo not not installed
#
nocheck : yes
#-----------------------------------------------------------
# Umask settings
#
# layman should usually work with a umask of 0022. You should
# only change this setting if you are absolutely certain that
# you know what you are doing.
#
#umask : 0022
#-----------------------------------------------------------
# News reporting settings
#
# This is for when layman is adding/syncing overlays.
# It is required for GLEP 42.
# Currently there are 3 possible values:
# portage, pkgcore, custom
#
# portage: uses portage to report news only from overlay(s) in
# versions >=2.2.0_alpha72 or >=2.1.10.32
# or all repositories (including gentoo) for older portage versions.
# pkgcore: does not yet support glep 42, no news is reported
# custom: requires that you provide a suitable python function
# to 'custom_news_func' using the api's config.set_option()
# or define the python package to import it from in custom_news_pkg
news_reporter: portage
#-----------------------------------------------------------
# News reporting custom function setting
#
# the pkg name that contains the layman_news_function()
# for it to import and use. It must be found in PYTHONPATH
#custom_news_pkg :
#-----------------------------------------------------------
# Command overrides
#
# You can have commands point to either a binary at a different
# location, e.g.
#
# /home/you/local/bin/git
#
# or just the command, e.g.
#
# git
#
# to use PATH-based resolution of the binary to call.
#
#bzr_command : /usr/bin/bzr
#cvs_command : /usr/bin/cvs
#darcs_command : /usr/bin/darcs
#git_command : /usr/bin/git
#mercurial_command : /usr/bin/hg
#rsync_command : /usr/bin/rsync
#svn_command : /usr/bin/svn
#tar_command : /bin/tar
#g-common_command : /usr/bin/g-common
#-----------------------------------------------------------
# Command additional options
#
# These commnad options will be added to the above commands
# when the overlay is added or synced.
#
# note: there are some options hardcoded in the backend
# scripts already. All VCS types listed here are
# for general consistency. Options may not be available
# or recommended for all VCS types and/or add/sync operations.
# Any options defined here are deemed:
# "Use at your own risk"
# and are not supported.
#
# eg:
# svn_addopts : --config-option=config:miscellany:use-commit-times=yes
#
#bzr_addopts :
#bzr_syncopts :
#cvs_addopts :
#cvs_syncopts :
#darcs_addopts :
#darcs_syncopts :
#git_addopts :
#git_syncopts :
#mercurial_addopts :
#mercurial_syncopts :
#rsync_syncopts :
#svn_addopts :
#svn_syncopts :
#g-common_generateopts :
#g-common_syncopts :
#-----------------------------------------------------------
# Per VCS Post Sync/Add hooks
#
# The listed commands will be run after every add/sync operation.
# All on one line If the repo path is needed, use a %cwd= in
# where you want the path substituted in. It will be detected
# and replaced with the correct path.
#
# eg: git_postsync : git-set-file-times
# eg: git_postsync : git-set-file-times %cwd=
# eg: git_postsync : git-set-file-times path=%cwd=
#
#bzr_postsync :
#cvs_postsync :
#darcs_postsync :
#git_postsync :
#mercurial_postsync :
#rsync_postsync :
#svn_postsync :
#tar_postsync :
#g-common_postsync :
#-----------------------------------------------------------
# Layman user info
#
# The user name and email to use when adding new repos
#
#git_user : layman
#git_email : layman@localhost
|
Thank you. |
|
Back to top |
|
 |
dol-sen Retired Dev


Joined: 30 Jun 2002 Posts: 2805 Location: Richmond, BC, Canada
|
Posted: Sat Dec 26, 2015 4:49 pm Post subject: |
|
|
No, your config looks fine.
What about as root: _________________ Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch... |
|
Back to top |
|
 |
ONEEYEMAN Advocate

Joined: 01 Mar 2005 Posts: 3681
|
Posted: Sat Dec 26, 2015 4:54 pm Post subject: |
|
|
dol-sen,
dol-sen wrote: |
No, your config looks fine.
What about as root:
|
Yeilds nothing.
Code: |
IgorDellGentoo / # whoami
root
IgorDellGentoo / # env | grep HTTP
IgorDellGentoo / #
|
Thank you. |
|
Back to top |
|
 |
quilosaq Veteran

Joined: 22 Dec 2009 Posts: 1575
|
Posted: Sat Dec 26, 2015 11:36 pm Post subject: |
|
|
ONEEYEMAN,
You have 2 ways to solve the issue:
1.- Work to get that your firewall allows trafic for the git protocol (outgoing to port 9418 in destination). This is the best solution.
2.- Make a configuration file for the rainyday repository with the source parameter using https protocol instead of git protocol. To do this copy this lines in the file Code: | /etc/layman/overlays/rainyday.xml | :
Code: | <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE repositories SYSTEM "http://www.gentoo.org/dtd/repositories.dtd">
<repositories xmlns="" version="1.0">
<repo quality="experimental" status="unofficial">
<name>rainyday</name>
<description lang="en"><![CDATA[Iegor's ebuilds]]></description>
<homepage>https://github.com/iegor/rainyday</homepage>
<owner type="person">
<email>rmtdev@gmail.com</email>
<name>Iegor</name>
</owner>
<!-- next line is changed
<source type="git">git://github.com/iegor/rainyday.git</source>
-->
<source type="git">https://github.com/iegor/rainyday.git</source>
<feed>https://github.com/iegor/rainyday/commits/master.atom</feed>
</repo>
<!-- vim:se et sw=2 ts=2 sts=2 :-->
</repositories> |
Then do it:
Code: | (root)# layman-updater
(root)# layman -a rainyday |
This solution is only a patch.
EDIT: git port is 9418 instead of 8418.
Last edited by quilosaq on Sun Dec 27, 2015 12:13 am; edited 1 time in total |
|
Back to top |
|
 |
ONEEYEMAN Advocate

Joined: 01 Mar 2005 Posts: 3681
|
Posted: Sat Dec 26, 2015 11:51 pm Post subject: |
|
|
quilosaq,
quilosaq wrote: |
ONEEYEMAN,
You have 2 ways to solve the issue:
1.- Work to get that your firewall allows trafic for the git protocol (outgoing to port 8418 in destination). This is the best solution.
|
Well, my modem/router already allows the traffic on the 8418. Here is the snapshot for the "Port Forwarding":
Quote: |
Port Forwarding + ADD SERVICE
Service Name Type Start Port End Port Server IP Server IPv6 Active
GIT Service TCP 9418 9418 192.168.1.2 2601:140:4001:a8d3:222:5fff:fece:664a Edit x
SSH TCP/UDP 22 22 192.168.1.2 2601:140:4001:a8d3:222:5fff:fece:664a Edit x
|
BTW, the GIT protocol is on port 9418 not 8418.
quilosaq wrote: |
2.- Make a configuration file for the rainyday repository with the source parameter using https protocol instead of git protocol. To do this copy this lines in the file Code: | /etc/layman/overlays/rainyday.xml | :
Code: | <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE repositories SYSTEM "http://www.gentoo.org/dtd/repositories.dtd">
<repositories xmlns="" version="1.0">
<repo quality="experimental" status="unofficial">
<name>rainyday</name>
<description lang="en"><![CDATA[Iegor's ebuilds]]></description>
<homepage>https://github.com/iegor/rainyday</homepage>
<owner type="person">
<email>rmtdev@gmail.com</email>
<name>Iegor</name>
</owner>
<!-- next line is changed
<source type="git">git://github.com/iegor/rainyday.git</source>
-->
<source type="git">https://github.com/iegor/rainyday.git</source>
<feed>https://github.com/iegor/rainyday/commits/master.atom</feed>
</repo>
<!-- vim:se et sw=2 ts=2 sts=2 :-->
</repositories> |
Then do it:
Code: |
(root)# layman-updater
(root)# layman -a rainyday
|
This solution is only a patch.
|
Well, it looks like everything else fails, so I may as well do this...
Unless you have some other idea of how to permanently fix this.
Thank you. |
|
Back to top |
|
 |
quilosaq Veteran

Joined: 22 Dec 2009 Posts: 1575
|
Posted: Sun Dec 27, 2015 12:33 am Post subject: |
|
|
Quote: | Port Forwarding + ADD SERVICE
Service Name Type Start Port End Port Server IP Server IPv6 Active |
Port forwarding is for incoming trafic not outgoing. |
|
Back to top |
|
 |
dol-sen Retired Dev


Joined: 30 Jun 2002 Posts: 2805 Location: Richmond, BC, Canada
|
Posted: Sun Dec 27, 2015 7:34 am Post subject: |
|
|
By the way. Your internet service provider may be blocking the normal git port, so it may not be your firewall, but theirs. What ports are open or closed varies between service providers.
So contact them to find out, complain your unable to connect. They may open it for you, who knows. If they do have it closed, they may not open it stating some vulnerability they are protecting you from, mumbo jumbo... _________________ Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch... |
|
Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|