On 09. 10. 19 21:23, Nico Kadel-Garcia wrote:
I'm not happy that RHEL upstream selected to use "python3" instead of
"python36" as the package name for their release of Python 3.6. Like
modularity, it's solving one problem but generating others.
All RHEL python3 packages also provide their
On 10. 10. 19 2:11, Nico Kadel-Garcia wrote:
On Wed, Oct 9, 2019 at 6:24 PM Miro Hrončok wrote:
On 09. 10. 19 21:23, Nico Kadel-Garcia wrote:
On Oct 9, 2019, at 8:03 AM, Miro Hrončok wrote:
On 09. 10. 19 13:47, Nico Kadel-Garcia wrote:
It's going to be a while before EPEL gets all of
On Wed, Oct 9, 2019 at 6:24 PM Miro Hrončok wrote:
>
> On 09. 10. 19 21:23, Nico Kadel-Garcia wrote:
> >> On Oct 9, 2019, at 8:03 AM, Miro Hrončok wrote:
> >>> On 09. 10. 19 13:47, Nico Kadel-Garcia wrote:
> >>> It's going to be a while before EPEL gets all of the "python36"
> >>> labeled
On 09. 10. 19 21:23, Nico Kadel-Garcia wrote:
On Oct 9, 2019, at 8:03 AM, Miro Hrončok wrote:
On 09. 10. 19 13:47, Nico Kadel-Garcia wrote:
It's going to be a while before EPEL gets all of the "python36"
labeled packages rebuilt to say "Provides: python3-module" as well as
"Provides:
On Wed, 9 Oct 2019 at 15:24, Nico Kadel-Garcia wrote:
>
>
>
> > On Oct 9, 2019, at 8:03 AM, Miro Hrončok wrote:
> >
> >> On 09. 10. 19 13:47, Nico Kadel-Garcia wrote:
> >> It's going to be a while before EPEL gets all of the "python36"
> >> labeled packages rebuilt to say "Provides:
> On Oct 9, 2019, at 8:03 AM, Miro Hrončok wrote:
>
>> On 09. 10. 19 13:47, Nico Kadel-Garcia wrote:
>> It's going to be a while before EPEL gets all of the "python36"
>> labeled packages rebuilt to say "Provides: python3-module" as well as
>> "Provides: python36-module" for complete
On 09. 10. 19 13:47, Nico Kadel-Garcia wrote:
It's going to be a while before EPEL gets all of the "python36"
labeled packages rebuilt to say "Provides: python3-module" as well as
"Provides: python36-module" for complete consistency with the altered
name used by RHEL. The epel-rpm-macros
On Wed, Oct 9, 2019 at 5:33 AM Miro Hrončok wrote:
>
> On 09. 10. 19 4:34, Nico Kadel-Garcia wrote:
> > On Tue, Oct 8, 2019 at 1:56 PM Irina Boverman wrote:
> >>
> >> Using "BuildRequires: python%{python3_pkgversion}-devel" results in this
> >> error:
> >>
> >> fedpkg scratch-build
> >> DEBUG
On 09. 10. 19 4:34, Nico Kadel-Garcia wrote:
On Tue, Oct 8, 2019 at 1:56 PM Irina Boverman wrote:
Using "BuildRequires: python%{python3_pkgversion}-devel" results in this error:
fedpkg scratch-build
DEBUG util.py:593: No matching package to install: 'python36-devel'
A lot of Fedora .spec
On Tue, Oct 8, 2019 at 1:56 PM Irina Boverman wrote:
>
> Using "BuildRequires: python%{python3_pkgversion}-devel" results in this
> error:
>
> fedpkg scratch-build
> DEBUG util.py:593: No matching package to install: 'python36-devel'
A lot of Fedora .spec files use "python3-devel" and various
On 09. 10. 19 0:27, Stephen John Smoogen wrote:
On Tue, 8 Oct 2019 at 15:49, Irina Boverman wrote:
Ok, how will I know what test results are?
On Tue, Oct 8, 2019 at 2:56 PM Kevin Fenzi wrote:
On Tue, Oct 08, 2019 at 07:54:37PM +0200, Miro Hrončok wrote:
On 08. 10. 19 18:48, Irina
On Tue, Oct 08, 2019 at 12:58:21PM -0700, Kevin Fenzi wrote:
> On Tue, Oct 08, 2019 at 03:48:35PM -0400, Irina Boverman wrote:
> > Ok, how will I know what test results are?
>
> We will be sure to share them back here to devel and epel-devel lists.
And... smooge and I just tested this. Sadly it
On Tue, Oct 08, 2019 at 12:58:21PM -0700, Kevin Fenzi wrote:
> On Tue, Oct 08, 2019 at 03:48:35PM -0400, Irina Boverman wrote:
> > Ok, how will I know what test results are?
>
> We will be sure to share them back here to devel and epel-devel lists.
And... smooge and I just tested this. Sadly it
On Tue, 8 Oct 2019 at 15:49, Irina Boverman wrote:
>
> Ok, how will I know what test results are?
>
> On Tue, Oct 8, 2019 at 2:56 PM Kevin Fenzi wrote:
>>
>> On Tue, Oct 08, 2019 at 07:54:37PM +0200, Miro Hrončok wrote:
>> > On 08. 10. 19 18:48, Irina Boverman wrote:
>> > > My build (qpid-proton
On Tue, 8 Oct 2019 at 15:49, Irina Boverman wrote:
>
> Ok, how will I know what test results are?
>
> On Tue, Oct 8, 2019 at 2:56 PM Kevin Fenzi wrote:
>>
>> On Tue, Oct 08, 2019 at 07:54:37PM +0200, Miro Hrončok wrote:
>> > On 08. 10. 19 18:48, Irina Boverman wrote:
>> > > My build (qpid-proton
On Tue, Oct 08, 2019 at 03:48:35PM -0400, Irina Boverman wrote:
> Ok, how will I know what test results are?
We will be sure to share them back here to devel and epel-devel lists.
kevin
--
>
> On Tue, Oct 8, 2019 at 2:56 PM Kevin Fenzi wrote:
>
> > On Tue, Oct 08, 2019 at 07:54:37PM +0200,
On Tue, Oct 08, 2019 at 03:48:35PM -0400, Irina Boverman wrote:
> Ok, how will I know what test results are?
We will be sure to share them back here to devel and epel-devel lists.
kevin
--
>
> On Tue, Oct 8, 2019 at 2:56 PM Kevin Fenzi wrote:
>
> > On Tue, Oct 08, 2019 at 07:54:37PM +0200,
Ok, how will I know what test results are?
On Tue, Oct 8, 2019 at 2:56 PM Kevin Fenzi wrote:
> On Tue, Oct 08, 2019 at 07:54:37PM +0200, Miro Hrončok wrote:
> > On 08. 10. 19 18:48, Irina Boverman wrote:
> > > My build (qpid-proton package) cannot find pythin36-devel package, I
> > > also tried
On Tue, Oct 08, 2019 at 07:54:37PM +0200, Miro Hrončok wrote:
> On 08. 10. 19 18:48, Irina Boverman wrote:
> > My build (qpid-proton package) cannot find pythin36-devel package, I
> > also tried python3-devel (also not found). It appears python36 was
> > removed from EPEL 7 recently.
>
> Yes it
On Tue, Oct 08, 2019 at 07:54:37PM +0200, Miro Hrončok wrote:
> On 08. 10. 19 18:48, Irina Boverman wrote:
> > My build (qpid-proton package) cannot find pythin36-devel package, I
> > also tried python3-devel (also not found). It appears python36 was
> > removed from EPEL 7 recently.
>
> Yes it
Using "BuildRequires: python%{python3_pkgversion}-devel" results in this
error:
fedpkg scratch-build
DEBUG util.py:593: No matching package to install: 'python36-devel'
On Tue, Oct 8, 2019 at 1:43 PM Sérgio Basto wrote:
> Now python 3.6 is shipped by RHEL 7.7 or Centos 7.7, the rules of
On 08. 10. 19 18:48, Irina Boverman wrote:
My build (qpid-proton package) cannot find pythin36-devel package, I also tried
python3-devel (also not found). It appears python36 was removed from EPEL 7
recently.
Yes it was, as it was added to RHEL 7.7.
The error is:
Now python 3.6 is shipped by RHEL 7.7 or Centos 7.7, the rules
of [1] still valid so you should (or must ) use [2]
[2]BuildRequires: python%{python3_pkgversion}-devel
[1] https://fedoraproject.org/wiki/User:Bkabrda/EPEL7_Python3
On Tue, 2019-10-08 at 12:48 -0400, Irina Boverman wrote:
> My
My build (qpid-proton package) cannot find pythin36-devel package, I also
tried python3-devel (also not found). It appears python36 was removed from
EPEL 7 recently.
Is this still relevant:
https://fedoraproject.org/wiki/User:Bkabrda/EPEL7_Python3?
Is this a temporary issue with getting python3
24 matches
Mail list logo
