| View previous topic :: View next topic |
| Author |
Message |
Dr Croubie
Apprentice
Joined: 21 Nov 2006
Posts: 159
|
 Posted: Wed Apr 22, 2015 3:26 am Post subject: Sync is deprecated? |
 |
|
WTF?
| Code: | > emerge --sync -v
!!! SYNC setting found in make.conf.
This setting is Deprecated and no longer used. Please ensure your 'sync-type' and 'sync-uri' are set correctly in /etc/portage/repos.conf/gentoo.conf
>>> Syncing repository 'gentoo' into '/usr/portage'... |
Nothing about it in the news:
| Code: | > eselect news list
News items:
[1] 2009-04-18 Generation 1 Java Setup Deprecated
[2] 2012-05-21 Portage config-protect-if-modified default
[3] 2012-11-06 PYTHON_TARGETS deployment
[4] 2013-06-07 Portage preserve-libs default
[5] 2013-08-23 Language of messages in emerge logs and output
[6] 2013-09-27 Separate /usr on Linux requires initramfs
[7] 2014-03-16 Ruby 1.8 removal; Ruby 1.9/2.0 default
[8] 2014-06-15 GCC 4.8.3 defaults to -fstack-protector
[9] 2014-10-26 GCC 4.7 Introduced the New C++11 ABI
[10] 2014-11-07 Upgrade to udev >= 217 or eudev >= 2.1
[11] 2015-01-28 CPU_FLAGS_X86 introduction
[12] 2015-02-01 ffmpeg/libav conflict management: USE=libav
[13] 2015-03-28 True multilib support on amd64
[14] 2015-04-16 FFmpeg default |
I've done a Ctrl-F in the handbook for 'sync-type' and 'sync-uri' and found nothing.
It just keeps saying here in the handbook to use mirrorselect.
Just for shits'n'giggles, I installed mirrorselect and followed the instructions as per a new installation, nothing different to what it always does, adds the SYNC="rsync://rsync.au.gentoo.org/gentoo-portage" line to my make.conf.
Yet another undocumented update?
At least sync and portage still work in the usual way, for however long that lasts... |
|
| Back to top |
|
 |
dol-sen
Retired Dev
Joined: 30 Jun 2002
Posts: 2805
Location: Richmond, BC, Canada
|
| Posted: Wed Apr 22, 2015 3:43 am Post subject: |
|
|
No, it was not "UNDOCUMENTED" Quite the opposite. You are just failing to see it all.
| Code: | | [39] 2015-02-02 New portage plug-in sync system |
I don't know how you managed to NOT get it. If you had portage installed, you were suppose to get it.
here it is for you: | Code: | brian@big_daddy ~/Dev/git/portage $ eselect news read 39
2015-02-04-portage-sync-changes
Title New portage plug-in sync system
Author Brian Dolbec <dolsen@gentoo.org>
Posted 2015-02-02
Revision 1
There is a new plug-in sync system in >=sys-apps/portage-2.2.16.
This system will allow third party modules to be easily installed. Look
for a new layman plug-in sync module in layman's next release. Next is
a brief look at the changes. See the url [1] listed below for detailed
descriptions and usage.
Changes: /etc/portage/repos.conf/*
New setting for all repository types (needed):
auto-sync = yes/no, true/false # default if absent: yes/true
New for git sync-type: (applies to clone only)
sync-depth = n where n = {0,1,2,3,...} (optional, default = 1)
0 -- full history
1 -- shallow clone, only current state (default)
2,3,... number of history changes to download
New sync-type modules:
sync-type = svn # sync a subversion repository
sync-type = websync # Perform an emerge-webrsync operation
sync-type = laymanator # (if installed) runs a layman -s action
New native portage postsync hooks
/etc/portage/postsync.d/*
Runs hooks once, only after all repos have been synced.
/etc/portage/repo.postsync.d/*
Runs each script with three arguments:
repo name, sync-uri, location
Each script is run at the completion of every repo synced.
Migration:
Edit /etc/portage/repos.conf/*.conf files, add the auto-sync option
to each repository definition. Edit sync-type option to one of the
supported types {rsync, git, cvs, svn, websync, laymanator}.
[some-repo]
...
sync-type = rsync
auto-sync = yes
For an existing /etc/portage/repos.conf/layman.conf file:
1) change/add the sync-type
sync-type = laymanator
2) Ensure you have the correct layman version installed with
it's laymanator module also installed.
Alternate method:
Please see the wiki page url [1] for detailed instructions.
Primary control of all sync operations has been moved from emerge to
emaint. "emerge --sync" now just calls the emaint sync module with the
--auto option. The --auto option performs a sync on only those
repositories with the auto-sync setting not set to 'no' or 'false'. If
it is absent, then it will default to yes and "emerge --sync" will sync
the repository.
NOTE: As a result of the default auto-sync = True/Yes setting, commands
like "eix-sync", "esync -l", "emerge --sync && layman -S" will cause
many repositories to be synced multiple times in a row. Please edit
your configs or scripts to adjust for the new operation.
WARNING:
Due to the above default. For any repos that you EXPLICITLY do not
want to be synced. You MUST set "auto-sync = no"
The 'emaint sync' module operates similar to layman. It can sync
single or multiple repos. See "emaint --help" or for more details and
examples see the wiki page listed below [1].
Additional help and project API documentation can be found at:
[1] https://wiki.gentoo.org/wiki/Project:Portage/Sync
brian@big_daddy ~/Dev/git/portage $
|
Follow the link to the wiki and it's instructions.
As for mirrorselect. It is automagically using the old deprecated SYNC variable in make.conf because you don't have the /etc/portage/repos.conf/gentoo.conf file for it to use the new repos.conf style setting.
After you migrate to the repos.conf style, re-run mirrorselect and it will make it's change there.
You also missed the big forum thread here in this forum (Portage & Programming) where we debugged it all.
_________________
Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch... |
|
| Back to top |
|
|
Dr Croubie
Apprentice
Joined: 21 Nov 2006
Posts: 159
|
| Posted: Wed Apr 22, 2015 4:17 am Post subject: |
|
|
| dol-sen wrote: | No, it was not "UNDOCUMENTED" Quite the opposite. You are just failing to see it all.
| Code: | | [39] 2015-02-02 New portage plug-in sync system |
I don't know how you managed to NOT get it. If you had portage installed, you were suppose to get it.
|
Well, I don't know how it's not in my news list either, strange.
(I'm on hardened amd64 no-multilib, if that makes any difference as to how I get news delivered?)
| dol-sen wrote: | here it is for you: | Code: | brian@big_daddy ~/Dev/git/portage $ eselect news read 39
2015-02-04-portage-sync-changes
Title New portage plug-in sync system
Author Brian Dolbec <dolsen@gentoo.org>
Posted 2015-02-02
Revision 1
There is a new plug-in sync system in >=sys-apps/portage-2.2.16.
This system will allow third party modules to be easily installed. Look
for a new layman plug-in sync module in layman's next release. Next is
a brief look at the changes. See the url [1] listed below for detailed
descriptions and usage.
Changes: /etc/portage/repos.conf/*
New setting for all repository types (needed):
auto-sync = yes/no, true/false # default if absent: yes/true
New for git sync-type: (applies to clone only)
sync-depth = n where n = {0,1,2,3,...} (optional, default = 1)
0 -- full history
1 -- shallow clone, only current state (default)
2,3,... number of history changes to download
New sync-type modules:
sync-type = svn # sync a subversion repository
sync-type = websync # Perform an emerge-webrsync operation
sync-type = laymanator # (if installed) runs a layman -s action
New native portage postsync hooks
/etc/portage/postsync.d/*
Runs hooks once, only after all repos have been synced.
/etc/portage/repo.postsync.d/*
Runs each script with three arguments:
repo name, sync-uri, location
Each script is run at the completion of every repo synced.
Migration:
Edit /etc/portage/repos.conf/*.conf files, add the auto-sync option
to each repository definition. Edit sync-type option to one of the
supported types {rsync, git, cvs, svn, websync, laymanator}.
[some-repo]
...
sync-type = rsync
auto-sync = yes
For an existing /etc/portage/repos.conf/layman.conf file:
1) change/add the sync-type
sync-type = laymanator
2) Ensure you have the correct layman version installed with
it's laymanator module also installed.
Alternate method:
Please see the wiki page url [1] for detailed instructions.
Primary control of all sync operations has been moved from emerge to
emaint. "emerge --sync" now just calls the emaint sync module with the
--auto option. The --auto option performs a sync on only those
repositories with the auto-sync setting not set to 'no' or 'false'. If
it is absent, then it will default to yes and "emerge --sync" will sync
the repository.
NOTE: As a result of the default auto-sync = True/Yes setting, commands
like "eix-sync", "esync -l", "emerge --sync && layman -S" will cause
many repositories to be synced multiple times in a row. Please edit
your configs or scripts to adjust for the new operation.
WARNING:
Due to the above default. For any repos that you EXPLICITLY do not
want to be synced. You MUST set "auto-sync = no"
The 'emaint sync' module operates similar to layman. It can sync
single or multiple repos. See "emaint --help" or for more details and
examples see the wiki page listed below [1].
Additional help and project API documentation can be found at:
[1] https://wiki.gentoo.org/wiki/Project:Portage/Sync
brian@big_daddy ~/Dev/git/portage $ |
|
Thanks for the news, but I really don't understand much of that, the depth / postsync / git / hooks and all the double-negatives.
Does 'auto' mean it'll automatically sync when I'm online? Definitely don't want that, I want it to sync when I tell it to sync.
Or does 'auto' mean it'll just automatically choose the best settings for me?
I'll read through the wiki in a minute and see if that makes more sense to me.
| dol-sen wrote: | Follow the link to the wiki and its instructions.
As for mirrorselect. It is automagically using the old deprecated SYNC variable in make.conf because you don't have the /etc/portage/repos.conf/gentoo.conf file for it to use the new repos.conf style setting.
After you migrate to the repos.conf style, re-run mirrorselect and it will make it's change there. |
Actually, it's using make.conf because I'm following the instructions verbatim from the handbook:
| Code: | A second important setting is the SYNC setting in make.conf. This variable contains the rsync server to use when updating the portage tree (the collection of ebuilds and related files containing all the information portage needs to download and install software). Again, it is possible to manually enter a SYNC server, but mirrorselect can ease that operation considerably:
root #mirrorselect -i -r -o >> /mnt/gentoo/etc/portage/make.conf |
So what is the new line to use for mirrorselect? Just
mirrorselect -i -r -o >> /etc/portage/repos.conf/gentoo.conf ?
| dol-sen wrote: | | You also missed the big forum thread here in this forum (Portage & Programming) where we debugged it all. |
Well that I certainly did, I'm sure I'm not the only user who doesn't read these fora every day (/week/month/year).
Just like when /etc/make.conf moved to /etc/portage/make.conf, I only found out when portage complained one day. But at least that was a simple 'mv'
Actually, shouldn't these repos-directory files be made through etc-update?
I used to get a lot of etc-update stuff come through with 'config files need updating' every time I emerged somthing or even --synced, but I haven't heard a peep from it for months. Does etc-update still work? |
|
| Back to top |
|
|
dmpogo
Advocate
Joined: 02 Sep 2004
Posts: 3267
Location: Canada
|
| Posted: Wed Apr 22, 2015 7:01 am Post subject: |
|
|
| SYNC does not work as before. It is just portage update copied the content of your SYNC variable to where it now has to be |
|
| Back to top |
|
|
charles17
Advocate
Joined: 02 Mar 2008
Posts: 3664
|
| Posted: Wed Apr 22, 2015 7:16 am Post subject: |
|
|
| Dr Croubie wrote: | Actually, it's using make.conf because I'm following the instructions verbatim from the handbook:
| Code: | A second important setting is the SYNC setting in make.conf. This variable contains the rsync server to use when updating the portage tree (the collection of ebuilds and related files containing all the information portage needs to download and install software). Again, it is possible to manually enter a SYNC server, but mirrorselect can ease that operation considerably:
root #mirrorselect -i -r -o >> /mnt/gentoo/etc/portage/make.conf |
|
Handbook needs to be updated. |
|
| Back to top |
|
|
Dr Croubie
Apprentice
Joined: 21 Nov 2006
Posts: 159
|
| Posted: Wed Apr 22, 2015 9:42 pm Post subject: |
|
|
| charles17 wrote: | | Dr Croubie wrote: | Actually, it's using make.conf because I'm following the instructions verbatim from the handbook:
| Code: | A second important setting is the SYNC setting in make.conf. This variable contains the rsync server to use when updating the portage tree (the collection of ebuilds and related files containing all the information portage needs to download and install software). Again, it is possible to manually enter a SYNC server, but mirrorselect can ease that operation considerably:
root #mirrorselect -i -r -o >> /mnt/gentoo/etc/portage/make.conf |
|
Handbook needs to be updated. |
Thanks, that's kind of obvious. Considering that the handbook is THE source of information, I'd have thought that it would be the first to be updated, must have slipped through somehow.
But actually, the links from that bug don't work either.
I did as the Wiki said:
> mirrorselect -i -r -o > /etc/portage/repos.conf
and it just did the same as the line from the handbook, with the singular difference that now SYNC is in /etc/portage/repos.conf instead of make.conf.
I masked the SYNC line in make.conf, and now I get:
> emerge --sync -v
!!! Error while reading repo config file: File contains no section headers.
file: '/etc/portage/repos.conf', line: 1
'SYNC="rsync://rsync.au.gentoo.org/gentoo-portage"\n'
So scratch that, deleting repos.conf, and leaving SYNC line in make.conf for now.
Or is mirrorselect just not to be used anymore at all?
Without having to wait until all the documentation is updated, can someone please spell out, in english that a non-developer would understand, what exactly I'm meant to do? |
|
| Back to top |
|
|
dmpogo
Advocate
Joined: 02 Sep 2004
Posts: 3267
Location: Canada
|
| Posted: Wed Apr 22, 2015 9:53 pm Post subject: |
|
|
Well, mirrorselect tarball is from May 29th, 2014. I guess it was not still updated |
|
| Back to top |
|
|
Dr Croubie
Apprentice
Joined: 21 Nov 2006
Posts: 159
|
| Posted: Wed Apr 22, 2015 10:12 pm Post subject: |
|
|
Well now something's really borken.
I've gone back to how it was, with SYNC in make.conf, I just went to sync again and I got taken to Köln, and then again to Zurich.
I re-emerged portage, to see if
"portage update copied the content of your SYNC variable to where it now has to be"
but that didn't copy anything, because it's totally ignoring my old sync in make.conf.
Looks like I'll just have to not-update anything until this is fixed. Internet's slow enough in these parts without having to traipse halfway across the world to get it. |
|
| Back to top |
|
|
John R. Graham
Administrator
Joined: 08 Mar 2005
Posts: 10589
Location: Somewhere over Atlanta, Georgia
|
| Posted: Wed Apr 22, 2015 10:28 pm Post subject: |
|
|
Please post your current /etc/portage/repos.conf/gentoo.conf file and also the SYNC line from your /etc/portage/make.conf file.
- John
_________________
I can confirm that I have received between 0 and 499 National Security Letters. |
|
| Back to top |
|
|
Dr Croubie
Apprentice
Joined: 21 Nov 2006
Posts: 159
|
| Posted: Wed Apr 22, 2015 10:38 pm Post subject: |
|
|
| John R. Graham wrote: | Please post your current /etc/portage/repos.conf/gentoo.conf file and also the SYNC line from your /etc/portage/make.conf file.
- John |
> pwd
/etc/portage
> ls repos.conf
ls: cannot access repos.conf: No such file or directory
> ls
bin env make.conf.catalyst package.accept_keywords package.keywords package.unmask postsync.d repo.postsync.d
categories make.conf make.profile package.env package.mask package.use profile savedconfig
> grep SYNC make.conf
SYNC="rsync://rsync.au.gentoo.org/gentoo-portage" |
|
| Back to top |
|
|
Dr Croubie
Apprentice
Joined: 21 Nov 2006
Posts: 159
|
| Posted: Wed Apr 22, 2015 10:45 pm Post subject: |
|
|
ps, obviously I don't have an /etc/portage/repos.conf directory, I'm presuming that I should? (and as I asked earlier, isn't this the kind of thing that etc-update should force on me?)
I just re-emerged portage again, and here are the last few lines of the output:
| Code: | <snip>
--- replaced dir /usr/bin
--- replaced dir /usr
--- replaced obj /etc/portage/repo.postsync.d/example
--- replaced dir /etc/portage/repo.postsync.d
--- replaced dir /etc/portage
--- replaced obj /etc/logrotate.d/elog-save-summary
--- replaced dir /etc/logrotate.d
--- replaced obj /etc/etc-update.conf
--- replaced obj /etc/dispatch-conf.conf
--- replaced dir /etc
>>> Regenerating /etc/ld.so.cache...
>>> Original instance of package unmerged safely.
>>> sys-apps/portage-2.2.18 merged.
>>> Auto-cleaning packages...
<snip> |
So /etc/portage/repos.conf/ is not getting created from installing the new portage, should it? It's creating the repo.postsync.d directory, but not repos.conf?
(If reinstalling the latest portage over itself doesn't work, I'm almost thinking about blocking the recent portage, downgrading to the last version, getting rid of all this new fluff, unmask the new one, 'upgrade' again and see if that helps. Might that work?) |
|
| Back to top |
|
|
Jaglover
Watchman
Joined: 29 May 2005
Posts: 8291
Location: Saint Amant, Acadiana
|
| Posted: Wed Apr 22, 2015 10:49 pm Post subject: |
|
|
You can create one by hand, not sure how I got mine, but I do have one (all my boxes do), here it is:
| Code: | ~ $ cat /etc/portage/repos.conf/gentoo.conf
[DEFAULT]
main-repo = gentoo
[gentoo]
location = /usr/portage
sync-type = rsync
sync-uri = rsync://rsync.gentoo.org/gentoo-portage
|
_________________
My Gentoo installation notes.
Please learn how to denote units correctly! |
|
| Back to top |
|
|
Dr Croubie
Apprentice
Joined: 21 Nov 2006
Posts: 159
|
| Posted: Wed Apr 22, 2015 11:09 pm Post subject: |
|
|
| Jaglover wrote: | You can create one by hand, not sure how I got mine, but I do have one (all my boxes do), here it is:
| Code: | ~ $ cat /etc/portage/repos.conf/gentoo.conf
[DEFAULT]
main-repo = gentoo
[gentoo]
location = /usr/portage
sync-type = rsync
sync-uri = rsync://rsync.gentoo.org/gentoo-portage
|
|
Thanks, that's the kind of answer I needed.
I just copied that and masked the SYNC line in make.conf and it's stopped whingeing about deprecations:
| Code: | portage # cat repos.conf/gentoo.conf
[DEFAULT]
main-repo = gentoo
[gentoo]
location = /usr/portage
sync-type = rsync
sync-uri = rsync://rsync.au.gentoo.org/gentoo-portage |
Now my concern is, I have a layman overlay installed, to get cross-avr/gcc, binutils etc.
Is all of this going to bork overlays and such too?
I understand a crudload less about overlays, I just followed the instructions verbatim when I set it up.
That news article I didn't get posted at the top mentions layman, what does it mean for that?
At least it's working, but before I mark it as solved, to summarise:
- Where does the repos.conf directory come from, if not directly from upgrading portage?
- Doesn't / shouldn't etc-update handle this?
- What does 'auto' sync mean?
- Still not sure why I didn't get the news item, maybe that's why I also didn't get the repos.conf directory?
- So far I count 2 handbook articles (amd64/x86) and 1 wiki page (mirrorselect) needs updating, probably the mirrorselect package too if it's a year old.
- Anything else? |
|
| Back to top |
|
|
Dr Croubie
Apprentice
Joined: 21 Nov 2006
Posts: 159
|
| Posted: Wed Apr 22, 2015 11:35 pm Post subject: |
|
|
| Dr Croubie wrote: | | - Where does the repos.conf directory come from, if not directly from upgrading portage? |
Well, there's a saying I got on a fortune-cookie once, "no answer is also an answer".
| Code: | > equery b /etc/portage/repos.conf/gentoo.conf
* Searching for /etc/portage/repos.conf/gentoo.conf ...
> |
So repos.conf/gentoo.conf doesn't come from anywhere? |
|
| Back to top |
|
|
dol-sen
Retired Dev
Joined: 30 Jun 2002
Posts: 2805
Location: Richmond, BC, Canada
|
| Posted: Thu Apr 23, 2015 12:48 am Post subject: |
|
|
Sorry, I started updating/correcting the mirrorselect wiki page, but had to take my daughter somewhere. I see posts have been busy while I was gone.
Anyway, I admit I did not think to look for or update any mirrorslect documentation. I did now update this wiki page https://wiki.gentoo.org/wiki/Mirrorselect.
This is a user created & editable page, so if you find a typo or know how to improve it, you can. There are certainly more options available and may benefit from additional explanation.
I'll work on getting the Handbook updated as well.
_________________
Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch... |
|
| Back to top |
|
|
charles17
Advocate
Joined: 02 Mar 2008
Posts: 3664
|
| Posted: Thu Apr 23, 2015 6:27 am Post subject: |
|
|
| dol-sen wrote: | Sorry, I started updating/correcting the mirrorselect wiki page, but had to take my daughter somewhere. I see posts have been busy while I was gone.
Anyway, I admit I did not think to look for or update any mirrorslect documentation. I did now update this wiki page https://wiki.gentoo.org/wiki/Mirrorselect. |
Not respecting the fact that
So we could have either | Quote: | Find Gentoo rsync mirror:
root #mirrorselect -i -r -o >> /etc/portage/repos.conf |
or | Quote: | Find Gentoo rsync mirror:
root #mirrorselect -i -r -o >> /etc/portage/repos.conf/gentoo.conf |
|
|
| Back to top |
|
|
dol-sen
Retired Dev
Joined: 30 Jun 2002
Posts: 2805
Location: Richmond, BC, Canada
|
| Posted: Fri Apr 24, 2015 3:29 am Post subject: |
|
|
Actually, no, the -o option for mirrorselect is currently stuck creating the SYNC= variable in the make.conf file. It will not output the correct sync-uri variable.
I am starting to modify mirrorselect, removing the old make.conf SYNC setting.
Also, originally repos.conf was a file, then it was made a directory capable so other apps like layman could handle it's own file without risk of breaking the main gentoo repo.
Then the portage ebuild was changed to create the repos.conf/gentoo.conf file during install as part of the change migration.
So, we recommend you use repos.conf as a directory with gentoo.conf for the main repo, then layman creates and manages it's own layman.conf file there for overlays it installs. You can either edit gentoo.conf for adding a local overlay or add another file for your local overlay(s).
I'll make sure the documentation is updated accordingly.
_________________
Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch... |
|
| Back to top |
|
|
Maffblaster
Developer
Joined: 01 May 2007
Posts: 70
Location: Spokane, Washington, USA
|
| Posted: Fri Apr 24, 2015 7:03 am Post subject: |
|
|
So, to confirm, we should officially describe /etc/portage/repos.conf as a directory in the documentation? Will support for it being a file be deprecated?
_________________
Lets make Gentoo better together!
wiki: https://wiki.gentoo.org/wiki/User:Maffblaster
blog: http://dev.gentoo.org/~maffblaster/
Last edited by Maffblaster on Fri Apr 24, 2015 3:24 pm; edited 1 time in total |
|
| Back to top |
|
|
steveL
Watchman
Joined: 13 Sep 2006
Posts: 5153
Location: The Peanut Gallery
|
| Posted: Fri Apr 24, 2015 11:33 am Post subject: |
|
|
| Maffblaster wrote: | | Will support for it being a file be depreciated? |
Sorry to be pedantic, but the word you're looking for is: deprecated (no 'i'.)
Depreciation is the loss in value of a financial asset; deprecation is phasing something out (usually as obsolete.)
Returning you to your normal program.. ;) |
|
| Back to top |
|
|
Maffblaster
Developer
Joined: 01 May 2007
Posts: 70
Location: Spokane, Washington, USA
|
|
| Back to top |
|
|
steveL
Watchman
Joined: 13 Sep 2006
Posts: 5153
Location: The Peanut Gallery
|
| Posted: Sat Apr 25, 2015 12:42 pm Post subject: |
|
|
No worries :)
As to the question, there's no benefit to adding yet more code to special-case anything.
Leave it to the user to use whichever method is most appropriate for them, recommending a directory for this aspect in the handbook.
The alternative is to start trying to encode policy, instead of implementing mechanism; that never works out well in the longer-term. |
|
| Back to top |
|
|
Titou1384
n00b
Joined: 19 Oct 2014
Posts: 7
|
| Posted: Sun Apr 26, 2015 10:17 am Post subject: |
|
|
Hi,
First, thanks for this post, it made things much clearer for me.
Talking about the sync-type option, the news specify that the supported types are "rsync, git, cvs, svn, websync, laymanator"... But I cannot manage to get it working...
Here is my /etc/portage/repos.conf/gentoo.conf :
| Code: |
[DEFAULT]
main-repo = gentoo
[gentoo]
auto-sync = yes
location = /usr/portage
sync-type = websync
sync-uri = http://gentoo.mirrors.ovh.net/gentoo-distfiles/
|
And here is what I get when I call emerge :
| Code: |
root@bananapi # emerge
!!! Repository 'gentoo' has sync-type attribute set to unsupported value: 'websync'
|
What do you think about it ?
Thank you for your answers. |
|
| Back to top |
|
|
asturm
Developer
Joined: 05 Apr 2007
Posts: 8935
|
| Posted: Sun Apr 26, 2015 10:32 am Post subject: |
|
|
| Hmm, websync option works here... |
|
| Back to top |
|
|
Dr Croubie
Apprentice
Joined: 21 Nov 2006
Posts: 159
|
| Posted: Sun Apr 26, 2015 11:43 am Post subject: |
|
|
| Titou1384 wrote: | Hi,
First, thanks for this post, it made things much clearer for me.
Talking about the sync-type option, the news specify that the supported types are "rsync, git, cvs, svn, websync, laymanator"... But I cannot manage to get it working...
Here is my /etc/portage/repos.conf/gentoo.conf :
| Code: |
[DEFAULT]
main-repo = gentoo
[gentoo]
auto-sync = yes
location = /usr/portage
sync-type = websync
sync-uri = http://gentoo.mirrors.ovh.net/gentoo-distfiles/
|
And here is what I get when I call emerge :
| Code: |
root@bananapi # emerge
!!! Repository 'gentoo' has sync-type attribute set to unsupported value: 'websync'
|
What do you think about it ?
Thank you for your answers. |
At a guess, I'd say that you're trying to websync from a server that doesn't support websync.
Have you tried setting it to any other addresses to see if they work? |
|
| Back to top |
|
|
dol-sen
Retired Dev
Joined: 30 Jun 2002
Posts: 2805
Location: Richmond, BC, Canada
|
| Posted: Sun Apr 26, 2015 5:17 pm Post subject: |
|
|
| Code: | And here is what I get when I call emerge :
Code:
root@bananapi # emerge
!!! Repository 'gentoo' has sync-type attribute set to unsupported value: 'websync'
What do you think about it ?
|
What portage version is this. If it is portage-9999, then it is (correctly) renamed to "webrsync". Turns out for the 2.2.18 release I missed renaming one spot, so it was still websync. My testing showed it still worked, so I have not patched the release and -r1 bumped it. So >=portage-2.2.19 it will be "webrsync".
Also, the laymanator module was renamed (again due to popular demand) to laymansync.
_________________
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
|
|
Portage & Programming
