When using new portage configuration layout related to repositories: /etc/portage/repos.d/*.conf instead of /etc/portage/make.conf when one set the sync-type to websync the following sync-uri attribute is ignored. Both "emerge-webrsync" and "emaint sync -a" still using old GENTOO_MIRRORS variable from make.conf instead of "sync-uri" from repos.d directory. I dont know if it works as designed or if it's a bug, but I think/hope the newly announced way of configuring the repositories sync is meant to keep all relevant configuration on one place and I don't see why websync should be an exception.
(In reply to Maros Zubko from comment #0) > When using new portage configuration layout related to repositories: > > /etc/portage/repos.d/*.conf instead of /etc/portage/make.conf The news item refers to /etc/portage/repos.conf/* (not /etc/portage/repos.d/*.conf). > when one set the sync-type to websync the following sync-uri attribute is > ignored. Maybe the problem is simply that you have your files in the wrong directory?
I put mistakenly wrong directory name in the Bug description, but in reality I'm using for sure /etc/portage/repos.conf/gentoo.conf file. "sync-type" directive is taked into consideration correctly when I use "emaint sync", but "sync-uri" placed in the same file is ignored when "sync-type = websync". On the other hand when using "sync-type = rsync", then "sync-uri" is used correctly.
with sync-type = websync or webrsync, it is still using the original emerge-webrsync command. It uses the mirror system which is configured in make.conf, so, yes, it does ignore the sync-uri so far. If you recall or look at the instructions for the emerge-webrsync setup. It states to leave the sync-type and sync-uri fields empty. To use it with teh webrsync module, you of course must fill in sync-type. The future plan is to re-write the emerge-webrsync command into a native python sync module. Currently it is just a wrapper which runs the emerge-webrsync command.
