Re: [gentoo-user] Will emerge-webrsyc work in the future?
On Wed, 12 Aug 2015 06:47:30 -0400 Rich Freeman ri...@gentoo.org wrote: On Wed, Aug 12, 2015 at 4:01 AM, gevisz gev...@gmail.com wrote: Already for the third day, emerge-webrsyc says me that my current local timestamp is possibly identical to the * timestamp of the latest snapshot, so I began to worry if this way of syncing my portage tree still works and will work in the future. https://infra-status.gentoo.org/notice/20150808-git Update (2015-08-11) Syncing issues are still being worked on. Some services depending on the package repository are also still pending to be adapted (packages.gentoo.org, snapshots). (emerge-webrsync uses the snapshots I believe) As far as I'm aware there are no current plans to make emerge-webrsync stop working. Ok, thank you for the information.
Re: [gentoo-user] Will emerge-webrsyc work in the future?
On Wed, 12 Aug 2015 11:25:09 +0300 Alon Bar-Lev alo...@gentoo.org wrote: On 12 August 2015 at 11:20, gevisz gev...@gmail.com wrote: 2015-08-12 11:10 GMT+03:00 Alon Bar-Lev alo...@gentoo.org: I am waiting as well... :) In the meantime, please do not use this script directly any more. Why? What is the shotcomings of using that script directly? I hope that in time it will be removed in favour of the new repo mechanism. Create: /etc/portage/repos.conf/gentoo.conf I do have such a file, but there stands: [DEFAULT] main-repo = gentoo [gentoo] location = /usr/portage auto-sync = no sync-type = rsync modify this^ to webrsync Yes, this part of the job is clear. sync-uri = rsync://rsync.gentoo.org/gentoo-portage remove this^ But here, I am afraid that I should put something else instead, not just delete the line. Not exactly what I want. :) --- [DEFAULT] main-repo = gentoo [gentoo] location = /usr/portage sync-type = webrsync --- Then use: # emerge --sync and ^ On 12 August 2015 at 11:01, gevisz gev...@gmail.com wrote: Already for the third day, emerge-webrsyc says me that my current local timestamp is possibly identical to the * timestamp of the latest snapshot, so I began to worry if this way of syncing my portage tree still works and will work in the future. # emerge-webrsync Fetching most recent snapshot ... Trying to retrieve 20150811 snapshot from http://mirror.netcologne.de/gentoo ... Fetching file portage-20150811.tar.xz.md5sum ... Fetching file portage-20150811.tar.bz2.md5sum ... Fetching file portage-20150811.tar.gz.md5sum ... Trying to retrieve 20150811 snapshot from http://de-mirror.org/gentoo ... Fetching file portage-20150811.tar.xz.md5sum ... Fetching file portage-20150811.tar.bz2.md5sum ... Fetching file portage-20150811.tar.gz.md5sum ... 20150811 snapshot was not found Trying to retrieve 20150810 snapshot from http://mirror.netcologne.de/gentoo ... Fetching file portage-20150810.tar.xz.md5sum ... Fetching file portage-20150810.tar.bz2.md5sum ... Fetching file portage-20150810.tar.gz.md5sum ... Trying to retrieve 20150810 snapshot from http://de-mirror.org/gentoo ... Fetching file portage-20150810.tar.xz.md5sum ... Fetching file portage-20150810.tar.bz2.md5sum ... Fetching file portage-20150810.tar.gz.md5sum ... 20150810 snapshot was not found Trying to retrieve 20150809 snapshot from http://mirror.netcologne.de/gentoo ... Fetching file portage-20150809.tar.xz.md5sum ... Fetching file portage-20150809.tar.bz2.md5sum ... Fetching file portage-20150809.tar.gz.md5sum ... Trying to retrieve 20150809 snapshot from http://de-mirror.org/gentoo ... Fetching file portage-20150809.tar.xz.md5sum ... Fetching file portage-20150809.tar.bz2.md5sum ... Fetching file portage-20150809.tar.gz.md5sum ... 20150809 snapshot was not found * Latest snapshot date: 20150808 * * Approximate snapshot timestamp: 1439081100 *Current local timestamp: 1439080501 * * The current local timestamp is possibly identical to the * timestamp of the latest snapshot. In order to force sync, use * the --revert option or remove the timestamp file located at * '/usr/portage/metadata/timestamp.x'.
[gentoo-user] Will emerge-webrsyc work in the future?
Already for the third day, emerge-webrsyc says me that my current local timestamp is possibly identical to the * timestamp of the latest snapshot, so I began to worry if this way of syncing my portage tree still works and will work in the future. # emerge-webrsync Fetching most recent snapshot ... Trying to retrieve 20150811 snapshot from http://mirror.netcologne.de/gentoo ... Fetching file portage-20150811.tar.xz.md5sum ... Fetching file portage-20150811.tar.bz2.md5sum ... Fetching file portage-20150811.tar.gz.md5sum ... Trying to retrieve 20150811 snapshot from http://de-mirror.org/gentoo ... Fetching file portage-20150811.tar.xz.md5sum ... Fetching file portage-20150811.tar.bz2.md5sum ... Fetching file portage-20150811.tar.gz.md5sum ... 20150811 snapshot was not found Trying to retrieve 20150810 snapshot from http://mirror.netcologne.de/gentoo ... Fetching file portage-20150810.tar.xz.md5sum ... Fetching file portage-20150810.tar.bz2.md5sum ... Fetching file portage-20150810.tar.gz.md5sum ... Trying to retrieve 20150810 snapshot from http://de-mirror.org/gentoo ... Fetching file portage-20150810.tar.xz.md5sum ... Fetching file portage-20150810.tar.bz2.md5sum ... Fetching file portage-20150810.tar.gz.md5sum ... 20150810 snapshot was not found Trying to retrieve 20150809 snapshot from http://mirror.netcologne.de/gentoo ... Fetching file portage-20150809.tar.xz.md5sum ... Fetching file portage-20150809.tar.bz2.md5sum ... Fetching file portage-20150809.tar.gz.md5sum ... Trying to retrieve 20150809 snapshot from http://de-mirror.org/gentoo ... Fetching file portage-20150809.tar.xz.md5sum ... Fetching file portage-20150809.tar.bz2.md5sum ... Fetching file portage-20150809.tar.gz.md5sum ... 20150809 snapshot was not found * Latest snapshot date: 20150808 * * Approximate snapshot timestamp: 1439081100 *Current local timestamp: 1439080501 * * The current local timestamp is possibly identical to the * timestamp of the latest snapshot. In order to force sync, use * the --revert option or remove the timestamp file located at * '/usr/portage/metadata/timestamp.x'.
Re: [gentoo-user] Will emerge-webrsyc work in the future?
On 12 August 2015 at 11:20, gevisz gev...@gmail.com wrote: 2015-08-12 11:10 GMT+03:00 Alon Bar-Lev alo...@gentoo.org: I am waiting as well... :) In the meantime, please do not use this script directly any more. Why? What is the shotcomings of using that script directly? I hope that in time it will be removed in favour of the new repo mechanism. Create: /etc/portage/repos.conf/gentoo.conf I do have such a file, but there stands: [DEFAULT] main-repo = gentoo [gentoo] location = /usr/portage auto-sync = no sync-type = rsync modify this^ to webrsync sync-uri = rsync://rsync.gentoo.org/gentoo-portage remove this^ Not exactly what I want. :) --- [DEFAULT] main-repo = gentoo [gentoo] location = /usr/portage sync-type = webrsync --- Then use: # emerge --sync and ^ On 12 August 2015 at 11:01, gevisz gev...@gmail.com wrote: Already for the third day, emerge-webrsyc says me that my current local timestamp is possibly identical to the * timestamp of the latest snapshot, so I began to worry if this way of syncing my portage tree still works and will work in the future. # emerge-webrsync Fetching most recent snapshot ... Trying to retrieve 20150811 snapshot from http://mirror.netcologne.de/gentoo ... Fetching file portage-20150811.tar.xz.md5sum ... Fetching file portage-20150811.tar.bz2.md5sum ... Fetching file portage-20150811.tar.gz.md5sum ... Trying to retrieve 20150811 snapshot from http://de-mirror.org/gentoo ... Fetching file portage-20150811.tar.xz.md5sum ... Fetching file portage-20150811.tar.bz2.md5sum ... Fetching file portage-20150811.tar.gz.md5sum ... 20150811 snapshot was not found Trying to retrieve 20150810 snapshot from http://mirror.netcologne.de/gentoo ... Fetching file portage-20150810.tar.xz.md5sum ... Fetching file portage-20150810.tar.bz2.md5sum ... Fetching file portage-20150810.tar.gz.md5sum ... Trying to retrieve 20150810 snapshot from http://de-mirror.org/gentoo ... Fetching file portage-20150810.tar.xz.md5sum ... Fetching file portage-20150810.tar.bz2.md5sum ... Fetching file portage-20150810.tar.gz.md5sum ... 20150810 snapshot was not found Trying to retrieve 20150809 snapshot from http://mirror.netcologne.de/gentoo ... Fetching file portage-20150809.tar.xz.md5sum ... Fetching file portage-20150809.tar.bz2.md5sum ... Fetching file portage-20150809.tar.gz.md5sum ... Trying to retrieve 20150809 snapshot from http://de-mirror.org/gentoo ... Fetching file portage-20150809.tar.xz.md5sum ... Fetching file portage-20150809.tar.bz2.md5sum ... Fetching file portage-20150809.tar.gz.md5sum ... 20150809 snapshot was not found * Latest snapshot date: 20150808 * * Approximate snapshot timestamp: 1439081100 *Current local timestamp: 1439080501 * * The current local timestamp is possibly identical to the * timestamp of the latest snapshot. In order to force sync, use * the --revert option or remove the timestamp file located at * '/usr/portage/metadata/timestamp.x'.
Re: [gentoo-user] Will emerge-webrsyc work in the future?
I am waiting as well... :) In the meantime, please do not use this script directly any more. Create: /etc/portage/repos.conf/gentoo.conf --- [DEFAULT] main-repo = gentoo [gentoo] location = /usr/portage sync-type = webrsync --- Then use: # emerge --sync On 12 August 2015 at 11:01, gevisz gev...@gmail.com wrote: Already for the third day, emerge-webrsyc says me that my current local timestamp is possibly identical to the * timestamp of the latest snapshot, so I began to worry if this way of syncing my portage tree still works and will work in the future. # emerge-webrsync Fetching most recent snapshot ... Trying to retrieve 20150811 snapshot from http://mirror.netcologne.de/gentoo ... Fetching file portage-20150811.tar.xz.md5sum ... Fetching file portage-20150811.tar.bz2.md5sum ... Fetching file portage-20150811.tar.gz.md5sum ... Trying to retrieve 20150811 snapshot from http://de-mirror.org/gentoo ... Fetching file portage-20150811.tar.xz.md5sum ... Fetching file portage-20150811.tar.bz2.md5sum ... Fetching file portage-20150811.tar.gz.md5sum ... 20150811 snapshot was not found Trying to retrieve 20150810 snapshot from http://mirror.netcologne.de/gentoo ... Fetching file portage-20150810.tar.xz.md5sum ... Fetching file portage-20150810.tar.bz2.md5sum ... Fetching file portage-20150810.tar.gz.md5sum ... Trying to retrieve 20150810 snapshot from http://de-mirror.org/gentoo ... Fetching file portage-20150810.tar.xz.md5sum ... Fetching file portage-20150810.tar.bz2.md5sum ... Fetching file portage-20150810.tar.gz.md5sum ... 20150810 snapshot was not found Trying to retrieve 20150809 snapshot from http://mirror.netcologne.de/gentoo ... Fetching file portage-20150809.tar.xz.md5sum ... Fetching file portage-20150809.tar.bz2.md5sum ... Fetching file portage-20150809.tar.gz.md5sum ... Trying to retrieve 20150809 snapshot from http://de-mirror.org/gentoo ... Fetching file portage-20150809.tar.xz.md5sum ... Fetching file portage-20150809.tar.bz2.md5sum ... Fetching file portage-20150809.tar.gz.md5sum ... 20150809 snapshot was not found * Latest snapshot date: 20150808 * * Approximate snapshot timestamp: 1439081100 *Current local timestamp: 1439080501 * * The current local timestamp is possibly identical to the * timestamp of the latest snapshot. In order to force sync, use * the --revert option or remove the timestamp file located at * '/usr/portage/metadata/timestamp.x'.
Re: [gentoo-user] Will emerge-webrsyc work in the future?
2015-08-12 11:10 GMT+03:00 Alon Bar-Lev alo...@gentoo.org: I am waiting as well... :) In the meantime, please do not use this script directly any more. Why? What is the shotcomings of using that script directly? Create: /etc/portage/repos.conf/gentoo.conf I do have such a file, but there stands: [DEFAULT] main-repo = gentoo [gentoo] location = /usr/portage auto-sync = no sync-type = rsync sync-uri = rsync://rsync.gentoo.org/gentoo-portage Not exactly what I want. :) --- [DEFAULT] main-repo = gentoo [gentoo] location = /usr/portage sync-type = webrsync --- Then use: # emerge --sync On 12 August 2015 at 11:01, gevisz gev...@gmail.com wrote: Already for the third day, emerge-webrsyc says me that my current local timestamp is possibly identical to the * timestamp of the latest snapshot, so I began to worry if this way of syncing my portage tree still works and will work in the future. # emerge-webrsync Fetching most recent snapshot ... Trying to retrieve 20150811 snapshot from http://mirror.netcologne.de/gentoo ... Fetching file portage-20150811.tar.xz.md5sum ... Fetching file portage-20150811.tar.bz2.md5sum ... Fetching file portage-20150811.tar.gz.md5sum ... Trying to retrieve 20150811 snapshot from http://de-mirror.org/gentoo ... Fetching file portage-20150811.tar.xz.md5sum ... Fetching file portage-20150811.tar.bz2.md5sum ... Fetching file portage-20150811.tar.gz.md5sum ... 20150811 snapshot was not found Trying to retrieve 20150810 snapshot from http://mirror.netcologne.de/gentoo ... Fetching file portage-20150810.tar.xz.md5sum ... Fetching file portage-20150810.tar.bz2.md5sum ... Fetching file portage-20150810.tar.gz.md5sum ... Trying to retrieve 20150810 snapshot from http://de-mirror.org/gentoo ... Fetching file portage-20150810.tar.xz.md5sum ... Fetching file portage-20150810.tar.bz2.md5sum ... Fetching file portage-20150810.tar.gz.md5sum ... 20150810 snapshot was not found Trying to retrieve 20150809 snapshot from http://mirror.netcologne.de/gentoo ... Fetching file portage-20150809.tar.xz.md5sum ... Fetching file portage-20150809.tar.bz2.md5sum ... Fetching file portage-20150809.tar.gz.md5sum ... Trying to retrieve 20150809 snapshot from http://de-mirror.org/gentoo ... Fetching file portage-20150809.tar.xz.md5sum ... Fetching file portage-20150809.tar.bz2.md5sum ... Fetching file portage-20150809.tar.gz.md5sum ... 20150809 snapshot was not found * Latest snapshot date: 20150808 * * Approximate snapshot timestamp: 1439081100 *Current local timestamp: 1439080501 * * The current local timestamp is possibly identical to the * timestamp of the latest snapshot. In order to force sync, use * the --revert option or remove the timestamp file located at * '/usr/portage/metadata/timestamp.x'.
Re: [gentoo-user] Will emerge-webrsyc work in the future?
On Wed, Aug 12, 2015 at 4:01 AM, gevisz gev...@gmail.com wrote: Already for the third day, emerge-webrsyc says me that my current local timestamp is possibly identical to the * timestamp of the latest snapshot, so I began to worry if this way of syncing my portage tree still works and will work in the future. https://infra-status.gentoo.org/notice/20150808-git Update (2015-08-11) Syncing issues are still being worked on. Some services depending on the package repository are also still pending to be adapted (packages.gentoo.org, snapshots). (emerge-webrsync uses the snapshots I believe) As far as I'm aware there are no current plans to make emerge-webrsync stop working. -- Rich
