On Mon, Dec 2, 2019 at 7:04 PM Miro Hrončok wrote:
>
> On 03. 12. 19 0:54, Kevin Fenzi wrote:
> > On Tue, Dec 03, 2019 at 12:38:01AM +0100, Miro Hrončok wrote:
> >> On 02. 12. 19 23:09, Ken Dreyer wrote:
> >>> On Mon, Dec 2, 2019 at 11:47 AM Neal Gompa wrote:
>
> On Mon, Dec 2, 2019 at
On 03. 12. 19 0:54, Kevin Fenzi wrote:
On Tue, Dec 03, 2019 at 12:38:01AM +0100, Miro Hrončok wrote:
On 02. 12. 19 23:09, Ken Dreyer wrote:
On Mon, Dec 2, 2019 at 11:47 AM Neal Gompa wrote:
On Mon, Dec 2, 2019 at 1:34 PM Ken Dreyer wrote:
Hi folks,
In EPEL 7 we have some packages with
On Tue, Dec 03, 2019 at 12:38:01AM +0100, Miro Hrončok wrote:
> On 02. 12. 19 23:09, Ken Dreyer wrote:
> > On Mon, Dec 2, 2019 at 11:47 AM Neal Gompa wrote:
> > >
> > > On Mon, Dec 2, 2019 at 1:34 PM Ken Dreyer wrote:
> > > >
> > > > Hi folks,
> > > >
> > > > In EPEL 7 we have some packages
On 02. 12. 19 23:09, Ken Dreyer wrote:
On Mon, Dec 2, 2019 at 11:47 AM Neal Gompa wrote:
On Mon, Dec 2, 2019 at 1:34 PM Ken Dreyer wrote:
Hi folks,
In EPEL 7 we have some packages with "python34" and "python36"
prefixes in their names. I guess this is a consequence of using the
On Mon, Dec 2, 2019 at 11:47 AM Neal Gompa wrote:
>
> On Mon, Dec 2, 2019 at 1:34 PM Ken Dreyer wrote:
> >
> > Hi folks,
> >
> > In EPEL 7 we have some packages with "python34" and "python36"
> > prefixes in their names. I guess this is a consequence of using the
> > %{python3_pkgversion} macro
I believe the answer is "yes" ... to both.
As far as I know, there aren't any differences. Where there are
differences, we're trying to get rid of the differences.
Example is that the automatic python dependencies weren't turned on in
epel8. That should be fixed in a few days, so you should be
On Mon, Dec 2, 2019 at 1:34 PM Ken Dreyer wrote:
>
> Hi folks,
>
> In EPEL 7 we have some packages with "python34" and "python36"
> prefixes in their names. I guess this is a consequence of using the
> %{python3_pkgversion} macro over time.
>
> Now that RHEL 7 has Python 3.6, and we want to
Hi folks,
In EPEL 7 we have some packages with "python34" and "python36"
prefixes in their names. I guess this is a consequence of using the
%{python3_pkgversion} macro over time.
Now that RHEL 7 has Python 3.6, and we want to deprecate Python 3.4 in
EPEL 7, I'm wondering about this.
If I'm
There used to be some differences between Fedora and EPEL packaging guidelines,
which were explained in the docs [1].
I don't find any mention in that doc to EPEL8, does that mean there aren't any
differences or that the page isn't updated for EPEL8?
Mattia
[1]
