[EPEL-devel] Following update policy for dnscrypt-proxy
Hello Some user requested an update from dnscrypt-proxy 1 to dnscrypt-proxy 2, which is totally incompatible and not even programmed in the same language. As far as I understand, such update is frowned upon as it would break existinq installations. Shall I then create a dnscrypt-proxy2 package specifically for EPEL7? Best regards, Robert-André ___ 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 7 - Packages that won't install - Pass 1
On Wednesday, 9 October 2019 23:22:11 CEST Troy Dawson wrote: > * golang-*-devel (Not really broken, you should never need to install these) > ** I will not file bugzilla's on these. These -devel packages are only > used for rpm making. > golang-github-aws-aws-sdk-go-devel > golang-github-coreos-go-log-devel > golang-github-goraft-raft-devel > golang-github-rackspace-gophercloud-devel > golang-github-spacemonkeygo-spacelog-devel > golang-golangorg-oauth2-devel > golang-google-golangorg-cloud-devel Eh, who's taking care of the Golang stack in RHEL8? These are old packages, it would have been better to use the stack we rebuilt in F31 which is known to be working and up to date. Anything before is probably broken. ___ 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: Python 3.6: RHEL 7.7 vs. CentOS 7.6 EPEL7 retirement problem
On Saturday, 10 August 2019 21:23:55 CEST Miro Hrončok wrote: > While I really tried to do my best, it seems that I broke CentOS by retiring > python36. Should it be unretired? Or is it reasonable to say: Please wait > for CentOS 7.7? > How long would that wait be? ___ 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: Missing python-rpm-macros>3.30 on EPEL7 ppc64le
The package are correctly retired, but the ones from RHEL are not available, which breaks building for EPEL7: https://kojipkgs.fedoraproject.org//work/tasks/9826/36909826/mock_output.log Error: Package: epel-rpm-macros-7-20.noarch (build) Requires: python-srpm-macros Error: Package: epel-rpm-macros-7-20.noarch (build) Requires: python2-rpm-macros You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Error: Package: epel-rpm-macros-7-20.noarch (build) Requires: python-rpm-macros Does something need to be one Koji side? ___ 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
