Spec URL: https://corsepiu.fedorapeople.org/packages/perl-Path-Iter.spec SRPM URL: https://corsepiu.fedorapeople.org/packages/perl-Path-Iter-0.2-1.fc28.src.rpm Description: Iterate through the contents of a given path without having to build the entire list first. Fedora Account System Username: corsepiu
Source file is ok Summary is ok License is ok Description is ok URL and Source0 are ok All tests passed BuildRequires are ok $ rpm -qp --requires perl-Path-Iter-0.2-1.fc28.noarch.rpm | sort | uniq -c 1 perl(File::Spec) 1 perl(:MODULE_COMPAT_5.26.1) 1 perl(strict) 1 perl(warnings) 1 rpmlib(CompressedFileNames) <= 3.0.4-1 1 rpmlib(FileDigests) <= 4.6.0-1 1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 1 rpmlib(PayloadIsXz) <= 5.2-1 Binary requires are Ok. $ rpm -qp --provides perl-Path-Iter-0.2-1.fc28.noarch.rpm | sort | uniq -c 1 perl(Path::Iter) = 0.2 1 perl-Path-Iter = 0.2-1.fc28 Binary provides are Ok. $ rpmlint ./perl-Path-Iter* 2 packages and 1 specfiles checked; 0 errors, 0 warnings. Rpmlint is ok The package looks good. Approved
What am I supposed to do now? I can't find the old package import request form but found some links pointing to some tool called fedrepo-req, which apparently is of the same quality as most of Fedora in recent times (Read: miserable and rotten): # fedrepo-req perl-Path-Iter -t 1531380 Error: The "pagure_api_token" setting is not set in the "app" section. Please read https://pagure.io/fedrepo_req/blob/master/f/README.md.
Follow the "Configuration" section on the linked document. Basically Pagure does not use Kerberos (nor X.509 certificates or SSH keys). Instead it has it's own authentication system based on "API keys". Once you generate the API key in Pagure web interface and copy it into fedrepo-req configuration file, the fedrepo-req tool should work for another 3 months. I don't like it either.
(In reply to Petr Pisar from comment #3) > Follow the "Configuration" section on the linked document. > > Basically Pagure does not use Kerberos (nor X.509 certificates or SSH keys). > Instead it has it's own authentication system based on "API keys". Once you > generate the API key in Pagure web interface and copy it into fedrepo-req > configuration file, the fedrepo-req tool should work for another 3 months. Thanks for trying to help, but this all reads "Greek" to me and leaves me as clueless as before. > I don't like it either. Well, I am seriously tired of RHAT role in Fedora.
(1) Go to <https://pagure.io/settings>. (2) Click "Create new key" at the bottom of the page. (3) Check "Create a new ticket" in the form and click "Create". (4) Copy the newly created key (the long string not marked as Expired under neath) from the resulting <https://pagure.io/settings> web page into clipboard. (4) Create ~/.config/fedrepo_req/config.ini file and put this content there: [app] pagure_api_token = (5) Append the key from the clipboard on the last line of the file.
Oh boy, is usability part of RHAT's and Fedora's releng's vocabulary? I guess, no :( Several failed attempts with this crappy UI later, things finally seem to have succeeded: # fedrepo-req perl-Path-Iter -t 1531380 https://pagure.io/releng/fedora-scm-requests/issue/3868
One day later, ... no progress so far - What am I supposed to do now to get this package imported into Fedora's git?
Waiting. The requests are reviewed by a human being. Or you can complain on #fedora-releng FreeNode channel.
(fedrepo-req-admin): The Pagure repository was created at https://src.fedoraproject.org/rpms/perl-Path-Iter
(In reply to Petr Pisar from comment #8) > Waiting. The requests are reviewed by a human being. Or you can complain on > #fedora-releng FreeNode channel. Well, what you say means this new UI just a bunch of usability regressions without any advantages to the users, but to piss off contributors. We once had a GUI, now we have a clumsy and widely dysfunctional CLI. Who is the person, who is responsible for this mess? Life is too short to waste time with this UI and is a manifestation of the disrespect RHAT exposes against the community.
perl-Path-Iter-0.2-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-84434dcb8b
perl-Path-Iter-0.2-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2018-40494a72f3
Apparently bodhi integration of this fedrepo crap also is broken. Bodhi's package forms did not offer me the f26/f27 rpms. Instead, I had to manually enter them. Furthermore, as things appear to me https://admin.fedoraproject.org/pkgdb/api/bugzilla is not being updated anymore.
Since the official FAQ <https://fedoraproject.org/wiki/Infrastructure/WhatHappenedToPkgdb> was started by mprahl and the fedrepo-req package created by mprahl, I think he's responsible for the implementation.
perl-Path-Iter-0.2-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-40494a72f3
perl-Path-Iter-0.2-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-84434dcb8b
mprahl, provide usable documentation and fix your software, ASAP. Both are unusable and a shame for you, to say the least.
perl-Path-Iter-0.2-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.
perl-Path-Iter-0.2-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.