[EPEL-devel] Re: Fedora EPEL 8 updates-testing report
On Sun, 2019-08-18 at 01:27 +, upda...@fedoraproject.org wrote:
> The following builds have been pushed to Fedora EPEL 8 updates-
> testing
>
>
> wxGTK3-3.0.4-10.el8.1
>
In spec changelog version is: Sat Aug 17 2019 Scott Talbert <
s...@techie.net> - 3.0.4-10.1
The '.1' should go before the %{?dist} tag in this case so to not
confuse as the outputted 'el8.1' does.
Regards
Phil
--
*** Playing the game for the games sake. ***
IRC: kathenas
Twitter: kathenasorg
Website: https://kathenas.org
signature.asc
Description: This is a digitally signed message part
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: EPEL 8 on RHEL 8.1 Beta
On Thu, 2019-08-01 at 13:23 -0400, Stephen John Smoogen wrote: > > > On Thu, 1 Aug 2019 at 06:31, Phil Wyett > wrote: > > On Thu, 2019-08-01 at 11:16 +0530, Thomas Stephen Lee wrote: > > > Hi, > > > > > > Trying to install EPEL 8 on RHEL 8.1 Beta. > > > > > > I did > > > > > > $ yum install > > > > > https://dl.fedoraproject.org/pub/epel/8/Everything/x86_64/Packages/e/epel-release-8-1.noarch.rpm > > > > > > and doing > > > > > > $ yum update > > > > > > gives the error > > > > > > failed to open: /var/cache/dnf/epel- > > > > > 7223eb0d0c06d046/repodata/78c05abe94a83354e9759eacd446d11a44df882d8 > > c4 > > > 5fbf74b147b09a7fd6c83-updateinfo.xml.zck > > > > > > Tried changing baseurl in /etc/yum.repos.d/epel.repo to > > > > > > https://dl.fedoraproject.org/pub/epel/8/Everything/x86_64 > > > > > > and > > > > > > https://dl.fedoraproject.org/pub/epel/testing/8/Everything/x86_64 > > > > > > both give the same error > > > > > > Kindly check. > > > > > > thanks > > > > > > -- > > > Lee > > > > Hi, > > > > I get errors also. > > > > I would also query why the EPEL-7 gpg key is in the package and a > > new > > one for 8 has not been used? > > > > OK i have gone over the keys and there is a new key for EPEL-8 and > the packages are being signed by that key. What errors were you > getting to say it was using the old one? > > > -- > Stephen J Smoogen. > I stated the EPEL-7 key was in the package. If you download the 'epel-release-8-1.noarch.rpm' and have a look in '/etc/pki/rpm-gpg/' you will find 'RPM-GPG-KEY-EPEL-7'. Either this is the 7 key or it is named wrongly. Regards Phil -- *** Playing the game for the games sake. *** IRC: kathenas Twitter: kathenasorg Website: https://kathenas.org signature.asc Description: This is a digitally signed message part ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: EPEL 8 on RHEL 8.1 Beta
On Thu, 2019-08-01 at 11:16 +0530, Thomas Stephen Lee wrote: > Hi, > > Trying to install EPEL 8 on RHEL 8.1 Beta. > > I did > > $ yum install > https://dl.fedoraproject.org/pub/epel/8/Everything/x86_64/Packages/e/epel-release-8-1.noarch.rpm > > and doing > > $ yum update > > gives the error > > failed to open: /var/cache/dnf/epel- > 7223eb0d0c06d046/repodata/78c05abe94a83354e9759eacd446d11a44df882d8c4 > 5fbf74b147b09a7fd6c83-updateinfo.xml.zck > > Tried changing baseurl in /etc/yum.repos.d/epel.repo to > > https://dl.fedoraproject.org/pub/epel/8/Everything/x86_64 > > and > > https://dl.fedoraproject.org/pub/epel/testing/8/Everything/x86_64 > > both give the same error > > Kindly check. > > thanks > > -- > Lee Hi, I get errors also. I would also query why the EPEL-7 gpg key is in the package and a new one for 8 has not been used? Regards Phil -- *** Playing the game for the games sake. *** IRC: kathenas Twitter: kathenasorg Website: https://kathenas.org signature.asc Description: This is a digitally signed message part ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: EPEL: Python34 moving to Python36
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 2019-04-02 at 07:18 -0700, Troy Dawson wrote: > On Wed, Mar 13, 2019 at 7:31 AM Stephen John Smoogen wrote: > > > > Over the last 5 days, Troy Dawson, Jeroen van Meeuwen, Carl W George, > > and several helpers have gotten nearly all of the python34 packages > > moves over to python36 in EPEL-7. They are being included in 6 Bodhi > > pushes because of a limitation in Bodhi for the text size of packages > > in an include. > > > > The current day for these package groups to move into EPEL regular is > > April 2nd. We would like to have all tests we find in the next week or > > so also added so that the updates can occur in a large group without > > too much breakage. > > > > > > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-f2d195dada > > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-9e9f81e581 > > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-0d62608bce > > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-5be892b745 > > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-0f4cca7837 > > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-ed3564d906 > > > > Please heavily test them by doing the following: > > Stage 1 Testing > > Install RHEL, CentOS, or Scientific Linux 7 onto a TEST system. > > Install or enable the EPEL repository for this system > > Install various packages you would normally use > > yum --enablerepo=epel-testing update > > Report problems to epel-devel@lists.fedoraproject.org > > Stage 2 Testing > > Check for any updated testing instructions on this blog or EPEL-devel list. > > Install RHEL, CentOS, or Scientific Linux 7 onto a TEST system. > > Install or enable the EPEL repository for this system > > yum install python34 > > yum --enablerepo=epel-testing update > > Report problems to epel-devel@lists.fedoraproject.org > > Stage 3 Testing > > Check for any updated testing instructions on this blog or EPEL-devel list. > > Install RHEL, CentOS, or Scientific Linux 7 onto a TEST system. > > Install or enable the EPEL repository for this system > > yum install python36 > > yum --enablerepo=epel-testing update > > Report problems to epel-devel@lists.fedoraproject.org > > This should cover the three most common scenarios. Other scenarios > > exist and will require some sort of intervention to work around. We > > will outline them as they come up. > > > > Many Many Thanks go to Troy, Jeroen, Carl, and the many people on the > > python team who made a copr and did many of the initial patches to > > make this possible. > > -- > > Stephen J Smoogen > > Thank you to everyone for all the feedback, testing, fixes and discussion. > I believe all of the blocking problems have been worked out and that > we are ready to push these to stable. > > I will be doing the push to stable in 4 hours. > If you have something you think is a blocker, please let me know before then. > > We have found that there were some packages left off the list of > packages to rebuild. This is not a blocker, but please let me know > and I will get them rebuilt and they will have their own smaller bodhi > update. > > Troy Dawson > ___ > epel-devel mailing list -- epel-devel@lists.fedoraproject.org > To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org Hi, Just performed migration from 34 to 36. After yum update to pull all packages and install, I proceeded to install 36 packages to match my current 34 install before removing 34 packages. The only issue in the whole process was the one below that required python34-pylint be removed before installing the 36 version. [philwyett@ks-kenobi ~]$ sudo yum install python36-pylint [sudo] password for philwyett: Loaded plugins: langpacks, product-id, search-disabled-repos, subscription- : manager Resolving Dependencies - --> Running transaction check - ---> Package python36-pylint.noarch 0:1.6.5-5.el7 will be installed - --> Processing Dependency: python36-setuptools for package: python36-pylint- 1.6.5-5.el7.noarch - --> Running transaction check - ---> Package python36-setuptools.noarch 0:39.2.0-3.el7 will be installed - --> Finished Dependency Resolution Dependencies Resolved PackageArch Version Repository Size Installing: python36-pylintnoarch1.6.5-5.el7 epel437 k Installing for dependencies: python36-setuptoolsnoarch39.2.0-3.el7epel631 k Transaction Summary
