Description of problem: Please rebuild barcode for EPEL 4, 5 and 6 Version-Release number of selected component (if applicable): barcode-0.98-15.fc15 Actual results: No barcode in EPEL 4, 5 and 6 Expected results: Package barcode in EPEL 4, 5 and 6 Additional info: Please let me know, when you're not interested in maintaining the package there.
Ping? May I get some feedback here, please?
Package Change Request ====================== Package Name: barcode New Branches: el4 el5 el6 Owners: rsc ixs As talked with Andreas (ixs) on FOSDEM, I'm going to take care of barcode on EPEL. Andreas will be co-maintainer, as he's the barcode maintainer at Fedora branches.
'rsc' is not a valid FAS account - please resubmit with that corrected.
Sorry & thanks Bill. Package Change Request ====================== Package Name: barcode New Branches: el4 el5 el6 Owners: robert ixs
Git done (by process-git-requests).
barcode-0.98-17.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/barcode-0.98-17.el6
barcode-0.98-17.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/barcode-0.98-17.el5
barcode-0.98-17.el4 has been submitted as an update for Fedora EPEL 4. https://admin.fedoraproject.org/updates/barcode-0.98-17.el4
barcode-0.98-17.el4 has been pushed to the Fedora EPEL 4 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update barcode'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/barcode-0.98-17.el4
barcode-0.98-17.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
barcode-0.98-17.el4 has been pushed to the Fedora EPEL 4 stable repository. If problems still persist, please make note of it in this bug report.
barcode-0.98-17.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.