Re: Current state of dual repository packages.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 08/14/2017 08:31 AM, Paul Howarth wrote:
> On 2017-08-11 19:00, Stephen John Smoogen wrote:
>> I have opened 2 tickets in RELENG to have these packages
>> removed/blocked for EPEL.
>>
>> Packages which are newer in EPEL than RHEL-7.4
>>
>> https://pagure.io/releng/issue/6948
>>
>> Packages which are older in EPEL than RHEL-7.4 but exist in aarch64,
>> x86_64, ppc64, and ppc64le
>>
>> https://pagure.io/releng/issue/6950
>>
>> The remaining packages which are not in all architectures BUT are very
>> old (and may break other things). These need some sort of
>> update/rebuild I expect.
> 
> I took a look at the three I am maintainer of:
> 
>> perl-Crypt-PasswdMD5
> 
> This package is unchanged from the EPEL package, just rebuilt (apart from the
> EPEL package having a "0." release prefix to indicate that it's one of the
> limited arch packages). I don't really think anything needs to be done with this.
> 
>> python-crypto
> 
> This is basically a clone of the existing EPEL package, with conditionals
> added around the python3 package so it doesn't get built for RHEL, which
> doesn't have python3.x. Updating this to match the RHEL package would result
> in dropping the python3 support, so I think this should be left alone too.

Available Packages
python2-crypto.x86_64       2.6.1-13.el7   epel
python2-crypto.x86_64       2.6.1-15.el7   rhel-7-server-extras-rpms
python34-crypto.x86_64      2.6.1-13.el7   epel

If this is a "limited arch package", shouldn't the release have 0. prefix as well?

>> python-paramiko
> 
> This one has had a version bump to a major new version that uses a different
> crypto backend (python-cryptography rather than python-crypto). This one
> should be cloned into the epel7 branch, a "0." prepended to Release: and the
> python3 package enabled I think.

Available Packages
python-paramiko.noarch         2.1.1-2.el7   rhel-7-server-extras-rpms
python2-paramiko.noarch        1.16.1-2.el7  epel
python34-paramiko.noarch       1.16.1-2.el7  epel

I think you're correct.

-- 
Orion Poplawski
Technical Manager                          720-772-5637
NWRA, Boulder/CoRA Office             FAX: 303-415-9702
3380 Mitchell Lane                       orion@xxxxxxxx
Boulder, CO 80301                   http://www.nwra.com
_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Announce]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux