| View previous topic :: View next topic |
| Author |
Message |
Ant P.
Watchman
Joined: 18 Apr 2009
Posts: 6920
|
 Posted: Wed Oct 12, 2016 9:10 pm Post subject: |
 |
|
While the topic's active I'll repeat what I asked some time ago (one year? 2?):
Is the git tree properly secured for end users yet, or is webrsync-gpg still the only way to prevent MITM attacks? |
|
| Back to top |
|
 |
ExecutorElassus
Veteran
Joined: 11 Mar 2004
Posts: 1435
Location: Berlin, Germany
|
| Posted: Fri Oct 14, 2016 11:06 am Post subject: |
|
|
Update: I was mistaken, it was not fixed. I now get the same error again, about not having permission for FETCH_HEAD. But I can't find this directory in /var/portage/repos/.git, or anywhere else in the tree. What am I doing wrong here? Why do I keep losing permission, and where is this file supposed to be?
Cheers,
EE |
|
| Back to top |
|
|
firephoto
Veteran
Joined: 29 Oct 2003
Posts: 1612
Location: +48° 5' 23.40", -119° 48' 30.00"
|
| Posted: Mon Nov 21, 2016 7:50 pm Post subject: |
|
|
I see change logs disappeared from rsync in the last week. Is this permanent and making it necessary to change to git or is git still not ready for the users yet? Seems to be a lack of info on the subject of git sync'n as it relates to non developer use.
_________________
#gentoo-kde on freenode |
|
| Back to top |
|
|
desultory
Bodhisattva
Joined: 04 Nov 2005
Posts: 9410
|
| Posted: Tue Nov 22, 2016 4:52 am Post subject: |
|
|
| firephoto wrote: | | I see change logs disappeared from rsync in the last week. Is this permanent and making it necessary to change to git or is git still not ready for the users yet? Seems to be a lack of info on the subject of git sync'n as it relates to non developer use. |
It is permanent, so far as that sort of thing goes, but it is neither necessary to switch to using git based synching nor an indication that the git repositories or services are not ready for use, it is simply due to the change logs having been relocated to another rsync module, specifically rsync.gentoo.org::gentoo-repo-changelog. |
|
| Back to top |
|
|
firephoto
Veteran
Joined: 29 Oct 2003
Posts: 1612
Location: +48° 5' 23.40", -119° 48' 30.00"
|
| Posted: Tue Nov 22, 2016 5:56 am Post subject: |
|
|
| desultory wrote: | | It is permanent, so far as that sort of thing goes, but it is neither necessary to switch to using git based synching nor an indication that the git repositories or services are not ready for use, it is simply due to the change logs having been relocated to another rsync module, specifically rsync.gentoo.org::gentoo-repo-changelog. |
So until the new rsync module is available on the servers (doesn't seem to work) and with the changelogs gone from the portage tree, and not have a portage sync'd with git so no option to see the git commits locally, it leaves rsync people in the dark for a while. I surely can't be the only one checking out the changelogs. They were in the rss feeds from packages.g.o but since git those too have been gone which meant relying on equery for quick checks of changes from the system.
| Code: |
@ERROR: Unknown module 'gentoo-repo-changelog'
|
On the git sync being ready, there's no announcement of it and it was specifically stated there would be an announcement when it was ready for users, thus my comment about that.
| Quote: |
For users of our package repository, nothing changes: Updates continue to be available via the established mechanisms (rsync, webrsync, snapshots). Options to fetch the package tree via Git are to be announced later.
|
_________________
#gentoo-kde on freenode |
|
| Back to top |
|
|
desultory
Bodhisattva
Joined: 04 Nov 2005
Posts: 9410
|
| Posted: Wed Nov 23, 2016 5:00 am Post subject: |
|
|
| firephoto wrote: | So until the new rsync module is available on the servers (doesn't seem to work) and with the changelogs gone from the portage tree, and not have a portage sync'd with git so no option to see the git commits locally, it leaves rsync people in the dark for a while. I surely can't be the only one checking out the changelogs. They were in the rss feeds from packages.g.o but since git those too have been gone which meant relying on equery for quick checks of changes from the system.
| Code: |
@ERROR: Unknown module 'gentoo-repo-changelog'
|
|
| Code: | $ rsync rsync.gentoo.org::gentoo-repo-changelog
Welcome to quetzal.gentoo.org / rsync.gentoo.org
Server Address : 176.28.50.119, 2a01:488:67:1000:b01c:3277:0:1
Contact Name : mirror-admin@gentoo.org
Hardware : 4 x Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz, 16040MB RAM
Sponsor : Host Europe, Cologne, Germany, EU
Please note: common gentoo-netiquette says you should not sync more
than once a day. Users who abuse the rsync.gentoo.org rotation
may be added to a temporary ban list.
|
It continues from there with the canonical timestamp and directory information; in short, it works.
| firephoto wrote: | | On the git sync being ready, there's no announcement of it and it was specifically stated there would be an announcement when it was ready for users, thus my comment about that. |
Neither has much bearing on the other, unless the git repositories were down to the point that they could not be used to generate the rsync modules, hence my counterpoint. |
|
| Back to top |
|
|
firephoto
Veteran
Joined: 29 Oct 2003
Posts: 1612
Location: +48° 5' 23.40", -119° 48' 30.00"
|
| Posted: Wed Nov 23, 2016 7:38 am Post subject: |
|
|
| desultory wrote: | It continues from there with the canonical timestamp and directory information; in short, it works.
|
So it only works directly with rsync itself and not portage? I set it up for an overlay, set it up for the named module. Just errors out in different ways on the different servers.
| Code: |
# emaint sync -r changelogs
>>> Syncing repository 'changelogs' into '/usr/local/portage/changelogs'...
>>> Starting rsync with rsync://176.28.50.119/gentoo-repo-changelog...
>>> Checking server timestamp ...
rsync: link_stat "/metadata/timestamp.chk" (in gentoo-repo-changelog) failed: No such file or directory (2)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1650) [Receiver=3.1.2]
>>> Retrying...
>>> Starting retry 1 of 4 with rsync://81.91.253.252/gentoo-repo-changelog
>>> Checking server timestamp ...
rsync: link_stat "/metadata/timestamp.chk" (in gentoo-repo-changelog) failed: No such file or directory (2)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1650) [Receiver=3.1.2]
>>> Retrying...
>>> Starting retry 2 of 4 with rsync://91.186.30.235/gentoo-repo-changelog
>>> Checking server timestamp ...
rsync: link_stat "/metadata/timestamp.chk" (in gentoo-repo-changelog) failed: No such file or directory (2)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1650) [Receiver=3.1.2]
>>> Retrying...
>>> Starting retry 3 of 4 with rsync://[2a01:488:67:1000:b01c:3277:0:1]/gentoo-repo-changelog
>>> Checking server timestamp ...
rsync error: error in socket IO (code 10) at clientserver.c(125) [Receiver=3.1.2]
>>> Retrying...
>>> Starting retry 4 of 4 with rsync://[2a01:90:200:10::1a]/gentoo-repo-changelog
>>> Checking server timestamp ...
rsync error: error in socket IO (code 10) at clientserver.c(125) [Receiver=3.1.2]
>>> Retrying...
!!! Exhausted addresses for rsync.gentoo.org
q: Updating ebuild cache in /usr/local/portage/changelogs ...
q: Finished 0 entries in 0.000009 seconds
Action: sync for repo: changelogs, returned code = 1
|
| Code: |
emaint sync -r changelogs
>>> Syncing repository 'changelogs' into '/usr/local/portage/changelogs'...
>>> Starting rsync with rsync://129.21.171.98/gentoo-repo-changelog...
>>> Checking server timestamp ...
rsync: failed to connect to 129.21.171.98 (129.21.171.98): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(125) [Receiver=3.1.2]
>>> Retrying...
>>> Starting retry 1 of 14 with rsync://156.56.247.193/gentoo-repo-changelog
>>> Checking server timestamp ...
@ERROR: Unknown module 'gentoo-repo-changelog'
rsync error: error starting client-server protocol (code 5) at main.c(1648) [Receiver=3.1.2]
>>> Retrying...
>>> Starting retry 2 of 14 with rsync://208.70.246.16/gentoo-repo-changelog
>>> Checking server timestamp ...
@ERROR: Unknown module 'gentoo-repo-changelog'
rsync error: error starting client-server protocol (code 5) at main.c(1648) [Receiver=3.1.2]
>>> Retrying...
>>> Starting retry 3 of 14 with rsync://209.221.142.124/gentoo-repo-changelog
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(636) [Receiver=3.1.2]
>>> Retrying...
>>> Starting retry 4 of 14 with rsync://141.219.155.230/gentoo-repo-changelog
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(636) [Receiver=3.1.2]
>>> Retrying...
>>> Starting retry 5 of 14 with rsync://134.153.48.2/gentoo-repo-changelog
>>> Checking server timestamp ...
@ERROR: Unknown module 'gentoo-repo-changelog'
rsync error: error starting client-server protocol (code 5) at main.c(1648) [Receiver=3.1.2]
>>> Retrying...
>>> Starting retry 6 of 14 with rsync://134.161.116.17/gentoo-repo-changelog
>>> Checking server timestamp ...
@ERROR: Unknown module 'gentoo-repo-changelog'
rsync error: error starting client-server protocol (code 5) at main.c(1648) [Receiver=3.1.2]
>>> Retrying...
>>> Starting retry 7 of 14 with rsync://128.61.111.9/gentoo-repo-changelog
>>> Checking server timestamp ...
@ERROR: Unknown module 'gentoo-repo-changelog'
rsync error: error starting client-server protocol (code 5) at main.c(1648) [Receiver=3.1.2]
>>> Retrying...
>>> Starting retry 8 of 14 with rsync://208.100.4.53/gentoo-repo-changelog
>>> Checking server timestamp ...
@ERROR: Unknown module 'gentoo-repo-changelog'
rsync error: error starting client-server protocol (code 5) at main.c(1648) [Receiver=3.1.2]
>>> Retrying...
>>> Starting retry 9 of 14 with rsync://216.165.129.134/gentoo-repo-changelog
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(636) [Receiver=3.1.2]
>>> Retrying...
>>> Starting retry 10 of 14 with rsync://128.10.252.13/gentoo-repo-changelog
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(636) [Receiver=3.1.2]
>>> Retrying...
>>> Starting retry 11 of 14 with rsync://216.194.64.133/gentoo-repo-changelog
>>> Checking server timestamp ...
@ERROR: Unknown module 'gentoo-repo-changelog'
rsync error: error starting client-server protocol (code 5) at main.c(1648) [Receiver=3.1.2]
>>> Retrying...
>>> Starting retry 12 of 14 with rsync://[2607:f128:1:3::2]/gentoo-repo-changelog
>>> Checking server timestamp ...
rsync error: error in socket IO (code 10) at clientserver.c(125) [Receiver=3.1.2]
>>> Retrying...
>>> Starting retry 13 of 14 with rsync://[2001:5d8:11::13]/gentoo-repo-changelog
>>> Checking server timestamp ...
rsync error: error in socket IO (code 10) at clientserver.c(125) [Receiver=3.1.2]
>>> Retrying...
>>> Starting retry 14 of 14 with rsync://[2001:48a8:0:8:0:3:0:232]/gentoo-repo-changelog
>>> Checking server timestamp ...
rsync error: error in socket IO (code 10) at clientserver.c(125) [Receiver=3.1.2]
>>> Retrying...
!!! Exhausted addresses for rsync.namerica.gentoo.org
q: Updating ebuild cache in /usr/local/portage/changelogs ...
q: Finished 0 entries in 0.000009 seconds
Action: sync for repo: changelogs, returned code = 1
|
It seems broken with portage.. anyway, it's offtopic for the git update. Just my bad luck or expecting too much from the normal update process of portage.
_________________
#gentoo-kde on freenode |
|
| 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
|
|
Gentoo Chat
