Open ghost opened 8 years ago
I can also point the used names to another mirror, if you provide me with the correct IP addresses for each name. (e.g. pkgs.sw.be and apt.sw.be).
@dagwieers can you provide me the auth-ids?
is it possible to setup a wiki page on https://github.com/repoforge/rpms to give a play by play of the status of rpmforge repo and it's domain/mirror transition and plans ?
@davidhrbac I wish I knew how.
@centminmod see #377
@dagwieers can you send me the zones by email?
@madeline-everett I see no point of having another mirror. We have the mirror infra up and running. Mirror are not the issue. See http://mirror-status.repoforge.org/
@dagwieers you must request the auth-ids at the current domain registrar - see https://www.openprovider.com/services/domain-transfer/
Except many of the mirrors actually don't have any of the content, which is rather annoying when they are all green on http://mirror-status.repoforge.org/ I found for example that http://ftp.surfsara.nl/pub/dag/ is one that does have the content, but it wasn't marked as a working/loaded mirror, so yeah..
@davidhrbac @dagwieers Will http://repository.it4i.cz/mirrors/repoforge/redhat/el7/en/x86_64/rpmforge/RPMS/rpmforge-release-0.5.3-1.el7.rf.x86_64.rpm work on CentOS 7 x86 32 bit? Asking because originally wasn't rpmforge package a noarch package? So I'd guess it ought to work on 32 bit no issues but must double check with you.
@dagwieers https://www.openprovider.com/services/domain-management/ When you scroll to the bottom of the page, you can click on "Access your control panel". Somewhere in there it will tell you an Auth-Code per each domain name, which you can email privately to @davidhrbac gmail: deroceros@gmail.com
@jult yes, you can see a lot of mirrors down or out of sync. We have notified all the mirror admins to resync and accept the new tree. I hade removed a bunch of them last two months. Anyway, there is a script to parse all the mirrors and propagate only the OK ones to end-users. You can see mirrorlists here - http://mirrorlist.repoforge.org/ We do it so for many years.
@chris001 well not sure. I guess there are references to x86_64 within the files. No, we have separate packages for the archs. What is the purpose of 32bit? I guess RHEL7/C7 are only 64bit?
Read the whole thread, and my understanding that someone is taking over reproforge/rpmforge and blowing new life into it? So it's safe to use, is in this location will get package updates?
@f33dm3bits Yes @dagwieers agreed to transfer the domain repoforge.org to @davidhrbac who has volunteered to be the new responsible maintainer of repoforge.org. As soon as Dag will transfer the domain to David, if David needs to update the infrastructure in a way which breaks the existing rpmforge-release package, then rpmforge-release package would be updated so it works again.
For people coming here and not sure what to use:
This is the command to install the new repo
rpm -Uvh http://repository.it4i.cz/mirrors/repoforge/redhat/el$RELEASE/en/$BASEARCH/rpmforge/RPMS/$(curl -s http://repository.it4i.cz/mirrors/repoforge/redhat/el$RELEASE/en/$BASEARCH/rpmforge/RPMS/ | grep rpmforge-release | grep $BASEARCH | grep el$RELEASE | sort | tail -n1 | sed 's%.*>\(rpmforge\-release\-.*.rpm\)<.*%\1%')
To help explain this:
$RELEASE
= 6 or 7 respectively to the CentOS version
$BASEARCH
= x86_64 or i386
e.g. CentOS 6 x86_64:
rpm -Uvh http://repository.it4i.cz/mirrors/repoforge/redhat/el6/en/x86_64/rpmforge/RPMS/$(curl -s http://repository.it4i.cz/mirrors/repoforge/redhat/el6/en/x86_64/rpmforge/RPMS/ | grep rpmforge-release | grep x86_64 | grep el6 | sort | tail -n1 | sed 's%.*>\(rpmforge\-release\-.*.rpm\)<.*%\1%')
@jpSimkins
Retrieving http://repository.it4i.cz/mirrors/repoforge/redhat/el7/en/i386/rpmforge/RPMS/
curl: (22) The requested URL returned error: 404 Not Found
error: skipping http://repository.it4i.cz/mirrors/repoforge/redhat/el7/en/i386/rpmforge/RPMS/ - transfer failed
@dagwieers I have to shutdown box which is running mirror-status.repoforge.org. I have prepared a new server rumcaj.fr.pudu.cz. I need to have access to DNS. Will you transfer the domain to the project?
@davidhrbac Do you mean http://rf-mirror-status.pudu.cz/ ( http://rumcajs.pi.pudu.cz )
@dagwieers A possible solution to this impasse about the domain. If you don't want to transfer the domain to the project, could you at least add a CNAME record to the repoforge.org DNS which point mirror-status.repoforge.org. CNAME rf-mirror-status.pudu.cz.
. And any other subdomains which David needs to have their CNAME pointed to the new servers subdomains.
@chris we had it already, I had not realised the CNAME chain. Anyway we need to control repoforge.org domain.
I'm going to switch mirror-status to new server tomorrow.
@chris001 new server is running the test phase #377
Hi David, just wanted to chime in: you'll have better luck getting the domain transferred if you write Dag a normal personal email (you can CC me if you want). I think he's filtering GitHub notifications, so he's unlikely to see what you wrote here... until some point where he gets to processing the notifications, which might as well take years to come :-/
@zyv Yury - did as suggested, thanks.
Indeed, I get so many GitHub notifications most are filtered out.
For the domain transfer I don't know exactly what is needed as I don't manage them myself. (I also don't have a web-interface to manage them.)
I will have to ask my registrar something, so what do you need exactly ?
Do you want me to transfer it to http://www.openprovider.com/ ?
The links on that website don't work: https://www.openprovider.com/services/domain-transfer/
@dagwieers the domain is already registered with OpenProvider, I guess. What registrar does read the domain invoice?
‹hrb33-toshiba› 13:37 $ whois repoforge.org
Domain Name: REPOFORGE.ORG
Domain ID: D157975495-LROR
WHOIS Server:
Referral URL: http://www.openprovider.com
Updated Date: 2017-01-04T17:48:24Z
Creation Date: 2010-01-04T17:56:08Z
Registry Expiry Date: 2018-01-04T17:56:08Z
Sponsoring Registrar: Hosting Concepts B.V. d/b/a Openprovider
Sponsoring Registrar IANA ID: 1647
Domain Status: ok https://icann.org/epp#ok
Registrant ID: DW003597-BE-5496
Registrant Name: Dag Wieers
Registrant Organization: Dagit BVBA
Registrant Street: Wanstraat 22
Registrant City: Lommel
Registrant State/Province:
Registrant Postal Code: 3920
Registrant Country: BE
Registrant Phone: +32.478436299
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: dag@wieers.com
Admin ID: DW003597-BE-5496
Admin Name: Dag Wieers
Admin Organization: Dagit BVBA
Admin Street: Wanstraat 22
Admin City: Lommel
Admin State/Province:
Admin Postal Code: 3920
Admin Country: BE
Admin Phone: +32.478436299
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: dag@wieers.com
Tech ID: DW003597-BE-5496
Tech Name: Dag Wieers
Tech Organization: Dagit BVBA
Tech Street: Wanstraat 22
Tech City: Lommel
Tech State/Province:
Tech Postal Code: 3920
Tech Country: BE
Tech Phone: +32.478436299
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: dag@wieers.com
Name Server: NS2.3TI.BE
Name Server: NS1.3TI.BE
DNSSEC: unsigned
>>> Last update of WHOIS database: 2017-01-13T19:02:58Z <<<
For more information on Whois status codes, please visit https://icann.org/epp
Access to Public Interest Registry WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the Public Interest Registry registry database. The data in this record is provided by Public Interest Registry for informational purposes only, and Public Interest Registry does not guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to(a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Afilias except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. Public Interest Registry reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.
@chris001 I offered to change the domain settings, but I was asked to transfer the domain instead. Never heard back. Changing DNS is easier because I can do that myself. Tell me what you need, and that's don't right away.
It's a local company in Leuven. I sent them a mail just now to ask the needed stuff to transfer the domain to someone else.
@dagwieers we do not need to change pkgs.sw.be and apt.sw.be records anymore. We have reliable mirror infra running for many years. We need to manage repoforge.org ourselves so we can continue with the project transition.
I see this:
@dagwieers can you send me the zones by email?
Here they are:
$ORIGIN .
$TTL 86400 ; 1 day
repoforge.org IN SOA ns1.3ti.be. admin.3ti.be. (
2017011403 ; serial
10800 ; refresh (3 hours)
3600 ; retry (1 hour)
1814400 ; expire (3 weeks)
1800 ; minimum (30 minutes)
)
NS ns1.3ti.be.
NS ns2.3ti.be.
A 192.30.252.153
A 192.30.252.154
MX 10 mail.3ti.be.
MX 20 mx2.3ti.be.
MX 20 mx3.3ti.be.
TXT "v=spf1 a mx ptr include:3ti.be -all"
$ORIGIN repoforge.org.
lists A 148.251.123.139
medusa A 78.46.17.219
AAAA 2a01:4f8:201:20f0::2
mirror-status CNAME rf-mirror-status.pudu.cz.
mirrorlist CNAME repoforge.github.io.
pkgs A 78.46.17.228
rsync A 78.46.17.228
tree A 78.46.17.228
vault A 78.46.17.228
www CNAME repoforge.org.
$ORIGIN .
$TTL 86400 ; 1 day
repoforge.com IN SOA ns1.3ti.be. admin.3ti.be. (
2017011403 ; serial
10800 ; refresh (3 hours)
3600 ; retry (1 hour)
1814400 ; expire (3 weeks)
1800 ; minimum (30 minutes)
)
NS ns1.3ti.be.
NS ns2.3ti.be.
MX 10 mail.3ti.be.
MX 20 mx2.3ti.be.
MX 20 mx3.3ti.be.
TXT "v=spf1 a mx ptr include:3ti.be -all"
$ORIGIN repoforge.com.
www CNAME repoforge.net.
$ORIGIN .
$TTL 86400 ; 1 day
repoforge.net IN SOA ns1.3ti.be. admin.3ti.be. (
2017011403 ; serial
10800 ; refresh (3 hours)
3600 ; retry (1 hour)
1814400 ; expire (3 weeks)
1800 ; minimum (30 minutes)
)
NS ns1.3ti.be.
NS ns2.3ti.be.
A 78.46.17.228
MX 10 mail.3ti.be.
MX 20 mx2.3ti.be.
MX 20 mx3.3ti.be.
TXT "v=spf1 a mx ptr include:3ti.be -all"
$ORIGIN repoforge.net.
www CNAME repoforge.net.
@dagwieers I can migrate domain I just need domain AUTH-ID. Then I can manage it. DNS zone dump would be fine because AXFR transfer is not allowed from outside.
@dagwieers sorry you already did
@davidhrbac Right, but if you had provided me with the information to change the records, everything would have continued to work. Your insistence on having the domain, and the fact you communicate via a web-page I do not read, does not help your cause. But that is your decision.
From the communication I read on these pages it appears I am not willing to transfer the domain or help, which is not the case. I simply was not aware this was relevant. I offered to package an RPM with someone else's key many times the past years (both publicly as well as privately to you) and never received a mail. I made plans to renew the project, but they always died down. So at some point I lose interest if other people don't show interest either. I would have stopped paying for the domains if it wasn't for the fact that I don't want someone else to use the domains to fake the project and trick people into installing packages with rogue software or whatever.
@dagwieers records were not the issue. Mirrors are OK. Master mirror is here http://repository.it4i.cz/mirrors/repoforge/. I can't point external domains to this server...
Would it help to switch to email?
Yes :-)
DNS AUTH ID is requested from registrar. I don't expect an answer before Monday because the company is closed during the weekend.
(PS I was referring to rsync.repoforge.org, pkgs.repforge.org and tree.repoforge.org, those I can fix ASAP by changing DNS)
OK, let's move to email. AUTH-ID would be nice.
A faster alternative solution to transferring the domain ownership (which takes several days), is simply to list @davidhrbac 's DNS servers (I hope you run some dns servers David) as the authoritative nameservers (NS) in the domain. As @dagwieers mentioned above, It only takes a minute to make this change, and maybe a then wait some hours to propagate the news out on the internet. This way David could administer the DNS servers, Dag retains ownership of the domains, this is everything which would be needed for David to do anything with he needs in the DNS by himself...
AUTH-ID codes have been communicated to @davidhrbac by email.
@davidhrbac Please initiate the transfer promptly as these domains are under constant attack.
@dagwieers working on it, thanks
Transfer is approved. Good luck !
All the three transfers are still having the tag 'being processed' at domain registrar web.
I've been informed that the transfer of generic domain takes up to 10 days.
domains repoforge.{com,net} have been transferred to a new registrar. We still need to transfer repoforge.org domain.
Any word on the progress on getting everything running again. Why it was stopped to begin with is beyond me since C6 relies heavily on it. Out dated or not it is still useful. Some programs require the older packages.
@danielllp Mirrors seem to be up and running. http://mirror-status.repoforge.org/
Sorry guys, I'm a newbie on linux. I centos 6.9 x86_64. I receive this error after yum update: http://apt.sw.be/redhat/el6/en/x86_64/dag/repodata/repomd.xml: [Errno 14] PYCURL ERROR 6 - "Couldn't resolve host 'apt.sw.be'" Trying other mirror. Error: Cannot retrieve repository metadata (repomd.xml) for repository: dag. Please verify its path and try again
reading your post might fit this solution --> rpm -Uvh http://repository.it4i.cz/mirrors/repoforge/redhat/el6/en/x86_64/rpmforge/RPMS/$(curl -s http://repository.it4i.cz/mirrors/repoforge/redhat/el6/en/x86_64/rpmforge/RPMS/ | grep rpmforge-release | grep x86_64 | grep el6 | sort | tail -n1 | sed 's%.>(rpmforge-release-..rpm)<.*%\1%')
Should I run this command to solve the problem? thank you 👍 5
@danielllp status update - we have finally managed to transfer ownership of all Repoforge domains.
Now we have to decide what to do next. We know that we need to distribute a new signing key. The easiest solution is to provide a new rpm-forge release package. Unfortunately we have no access to the old key. So we have to distribute a new key to end-user. Investigating the best scenario...
@kelta what does return rpm -qa | grep release
@davidhrbac I think there is a procedure for smoothly adding your key, without disrupting anything. Such as, I think, if @dagwieers were to add your public key to the rpm-forge release package, along with his public key, and produce a new release with both your public keys in it, then it should work, any packages signed by you should be acceptable to the end users. Dag could you confirm this would work smoothly as an automatic yum update to the end-user's rpm-forge package, without any added effort by the end users to manually install any type of special exceptional package from a manually entered url?
The repo & all the mirrors are presently inaccessible. The Centos wiki has flagged repoforge as a dead project. Any plans of reversing this? Too much important software here to lose it.