Am 29.06.20 um 21:41 schrieb Tuomo Soini:
On Mon, 29 Jun 2020 17:32:58 +0200
Leon Fauster wrote:
For those that have an automated update process in place.
What steps are needed to revert this mistake?
"dnf distro-sync" after issue has been corrected. Issue has been fixed
but not applied
The following Fedora EPEL 6 Security updates need testing:
Age URL
13 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-be517af396
tcpreplay-4.3.3-1.el6
13 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-e982b1bb7c
php-horde-horde-5.2.23-1.el6
10
Hi,
* Have you downloaded the package over HTTPS?
I installed it using “dnf install epel-release”
* Results of rpm -V epel-release and rpm -qi epel-release
[root@katt-shanghai katt-server-install]# rpm -V epel-release
[root@katt-shanghai katt-server-install]# rpm -qi epel-release
Name
Policies don't mean mistakes won't happen.
A mistake happened and
A) We are trying to clean it up as soon as possible [1]
B) We are trying to work with mbs and infrastructure to make sure this
can't happen in the future.
I'm sorry this is so short on details, but I need to either write a
short
Hi Troy,
thank you for the pointer and sorry if my tone was a bit harsh.
I filed also https://bugzilla.redhat.com/show_bug.cgi?id=1851642 - is that
the right place?
Felix
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe
Hi Felix,
I wasn't offended by your tone. I felt the same way when I saw this on Friday.
Although dnf sees these as two different modules, since they have same
name and stream, dnf lumps them together. When that happens, dnf uses
the packages with the highest Name-Version-Release (NVR). In
On Monday, 29 June 2020 at 03:27, Wei, Catherine wrote:
> Thanks. I fixed this by changing the reposdir=/etc/yum.163.yum.repos.d
> to /etc/yum.repos.d/, then the epel repository can be found.
There are no such references in the epel-release package. Have you
downloaded the package over HTTPS? Can
Am 29.06.20 um 17:16 schrieb Troy Dawson:
Hi Felix,
I wasn't offended by your tone. I felt the same way when I saw this on Friday.
Although dnf sees these as two different modules, since they have same
name and stream, dnf lumps them together. When that happens, dnf uses
the packages with the
On Mon, 29 Jun 2020 17:32:58 +0200
Leon Fauster wrote:
>
> For those that have an automated update process in place.
> What steps are needed to revert this mistake?
"dnf distro-sync" after issue has been corrected. Issue has been fixed
but not applied yet. It only gets fixed after next module
