Bug 1249885 - Avrdude Package for EPEL 7 Does Not Exist
Summary: Avrdude Package for EPEL 7 Does Not Exist
Keywords:
Status: ASSIGNED
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: avrdude
Version: epel7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Hans Ulrich Niedermann
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-04 03:32 UTC by Sean Malloy
Modified: 2022-11-28 12:08 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Sean Malloy 2015-08-04 03:32:34 UTC
Description of problem:
A package for arvdude does not exist for EPEL 7.

Version-Release number of selected component (if applicable):
N/A

How reproducible:
Enabled EPEL 7 on a CentOS 7 machine. Try to install the avrdude package.

Steps to Reproduce:
1. rpm -i https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
2. yum install avrdude


Actual results:
Output from yum is "No package avrdude available"

Expected results:
The avrdude package is successfully installed.

Additional info:

Comment 1 Hans Ulrich Niedermann 2020-04-04 19:52:59 UTC
Someone would need to maintain EPEL branches, as I have no EL machines to test on.

Me just blindly going by the "if it compiles, it ships" motto for EPEL branches is not very helpful, especially as on EL the expectation is of much less breakage.

Comment 2 Harry Mallon 2020-05-15 14:33:18 UTC
AVRDude 5.11.1-4.el7 is availabel in EPEL7, this bug is old. However, there is no package available in EPEL 8.

It says here that giallu is the EPEL assignee for this?
https://src.fedoraproject.org/rpms/avrdude/branches?branchname=master

Comment 3 Hans Ulrich Niedermann 2022-01-18 15:24:40 UTC
FTR, as epel7 already exists, I have requested epel8 and epel9 for avrdude:

epel8: https://pagure.io/releng/fedora-scm-requests/issue/41075
epel9: https://pagure.io/releng/fedora-scm-requests/issue/41076

Comment 4 Harry Mallon 2022-09-27 15:10:37 UTC
Now that the branches exist would it be possible to kick off a build for EPEL9?

Comment 5 Hans Ulrich Niedermann 2022-09-28 21:47:42 UTC
Good point.

BTW, would the many years old 6.4 release be preferable for the new epel branches, or the 7.0 release from 2022-05?

Comment 6 Harry Mallon 2022-09-28 22:31:12 UTC
According to the GitHub and the download page on here (http://download.savannah.gnu.org/releases/avrdude/) release 6.4 was only from 16th Dec 2021, so it's not super old. I successfully used 6.4 earlier (having borrowed a binary rpm from Fedora 35 to use on CentOS-Stream 9), so that works for me. v7.0 adds support for a lot of new devices which is definately a plus. I guess it makes sense for Fedora to always be ahead (or equal) to EPEL, so if EPEL9 moved to v7.0 then Fedora might want upgrading too?

There are arguments for each version and I personally see both as good options, so I dont really mind. :)

Comment 7 Fedora Admin user for bugzilla script actions 2022-11-28 12:08:59 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.


Note You need to log in before you can comment on or make changes to this bug.