Spec Name or Url: http://apt.kde-redhat.org/apt/kde-redhat/SPECS/k3b-extras.spec SRPM Name or Url: http://apt.kde-redhat.org/apt/kde-redhat/all/SRPMS.stable/k3b-extras-0.12.14-1.src.rpm Description: Free decoder/encoder plugins for k3b, including: musepack decoder (libmpcdec) sndfile decoder (libsndfile)
Can't connect to abouve URL
WORKSFORME. You can alternatively substitute kde-redhat.unl.edu for apt.kde-redhat.org. Does that help?
Rex, the apt.kde-redhat.org domain should be known for a long time as being unreachable for all (or nearly all) T-Com networks. And "very long" here means "many months or even years". And believe me, the rest of the net works flawlessly. http://apt.kde-redhat.org/ => http://129.93.181.6/ no problems. Look: $ host apt.kde-redhat.org Host apt.kde-redhat.org not found: 2(SERVFAIL) $ host -a kde.redhat.org Trying "kde.redhat.org" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4844 ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;kde.redhat.org. IN ANY ;; ANSWER SECTION: kde.redhat.org. 300 IN A 209.200.153.152 kde.redhat.org. 6000 IN NS ns2.sedoparking.com. kde.redhat.org. 6000 IN NS ns1.sedoparking.com. kde.redhat.org. 6000 IN SOA ns1.sedoparking.com. hostmaster.sedo.de. 2000013101 28800 7200 604800 86400 $ host apt.kde-redhat.org ns1.sedoparking.com Using domain server: Name: ns1.sedoparking.com Address: 217.160.95.94#53 Aliases: apt.kde-redhat.org has address 209.200.153.152 Using domain server: Name: ns1.sedoparking.com Address: 217.160.95.94#53 Aliases: Using domain server: Name: ns1.sedoparking.com Address: 217.160.95.94#53 Aliases: $ host apt.kde-redhat.org ns2.sedoparking.com Using domain server: Name: ns2.sedoparking.com Address: 217.160.141.42#53 Aliases: apt.kde-redhat.org has address 209.200.153.152 Using domain server: Name: ns2.sedoparking.com Address: 217.160.141.42#53 Aliases: Using domain server: Name: ns2.sedoparking.com Address: 217.160.141.42#53 Aliases: $ host apt.kde-redhat.org 209.200.153.152 ;; connection timed out; no servers could be reached
Thanks Michael, I had no idea the problem was that wide-spread. I've forwarded your comments to my DNS hosting provider.
* The "k3b >= 0.12.14" requirement is too much. "k3b >= 0.12" for the k3b 0.12 series would be acceptable. FC-4 still includes k3b-0.12.10 where this k3b-extras package _would_ install and work just fine. Whether the k3b soname versions are strict enough? Maybe. libk3bdevice's soname has not changed since k3b 0.11, though. * "BR taglib-devel libmusicbrainz-devel" not needed. Else: APPROVED
> Requires: k3b >= 0.12 agreed. > Extraneous BR: taglib-devel, libmusicbrainz-devel good point. Don't forget the we're including sndfile decoder (libsndfile) here which would (currently) conflict with a certain other pkg from that other must-not-be-named repo. (-:
Thanks, imported.