https://bugzilla.novell.com/show_bug.cgi?id=803316
https://bugzilla.novell.com/show_bug.cgi?id=803316#c9
--- Comment #9 from Michael Andres 2013-07-02 14:10:19 CEST ---
If you enter a URL in YAST, yast first tries to add this as a service
(probing for URL/repo/repoindex.xml).
If this fails yast tries to add it as repo
(probing for URL/repodata/repomd.xml (yum),
then URL/content (sustetags)).
This is similar to calling
zypper addservice URL ... || zypper addrepo URL ...
This is independent from the actual URL scheme (ftp, tftp, http, nfs, dir,
...).
For 'tftp' schema the underlying libzypp uses curl, so we basically call
curl -v tftp://viki.qa.suse.cz/opensuse/repo/repoindex.xml
if this returns file_not_found:
curl -v tftp://viki.qa.suse.cz/opensuse/repodata/repomd.xml
Unfortunately curl does not return file_not_found, but some other kind of
error. That's why probing aborts.
$ curl -v tftp://viki.qa.suse.cz/opensuse/repodata/repomd.xml
* About to connect() to viki.qa.suse.cz port 69 (#0)
* Trying 10.100.98.20...
* Failed to set TCP_KEEPIDLE on fd 3
* Failed to set TCP_KEEPINTVL on fd 3
* connected
* getpeername() failed with errno 107: Transport endpoint is not connected
I'm no expert for curl nor for tftp, but to me this looks like there is no tftp
service reachable at port 69.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.