From baggins at pld-linux.org  Tue Jan  1 14:31:18 2019
From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=)
Date: Tue, 1 Jan 2019 22:31:18 +0900
Subject: PLD Th 2018 snapshot released
Message-ID: <20190101133117.GA31875@tachikoma>

2018 snapshot of PLD/Linux Th has been released. It is available on
ftp://ftp.pld-linux.org/dists/th/2018/PLD/ and as poldek sources th-2018.

The main highlights of this release are:

    kernels 4.4.169, 4.9.148, 4.14.91 and 4.19.13 (4.4 and 4.9 have vserver enabled)
    GCC 8.2.0
    LLVM 7.0.1
    glibc 2.28
    Python 2.7.15 and 3.7.1
    PHP 5.2, 5.3, 5.4, 5.5, 5.6, 7.0, 7.1, 7.2.13 and 7.3.0
    Perl 5.28.1
    Ruby 2.4.4
    libreoffice 6.1.4.2
    GNOME 3.28
    KDE5 Frameworks 5.48, Plasma 5.11.2
    MATE Desktop Environment 1.20

-- 
Jan R?korajski                    | PLD/Linux
SysAdm | baggins<at>pld-linux.org | http://www.pld-linux.org/


From jajcus at jajcus.net  Wed Jan  2 14:44:11 2019
From: jajcus at jajcus.net (Jacek Konieczny)
Date: Wed, 2 Jan 2019 14:44:11 +0100
Subject: PLD New Rescue Th-2018 1.6
Message-ID: <9964ef20-c9f1-c42b-3a06-57122d889c0f@jajcus.net>

Hi,

I have just made the new release of PLD New Rescue boot disk image. It
is based on the latest Th snapshot and includes a few improvements since
the last PLD NR release, though nothing major.

https://github.com/Jajcus/pld-new-rescue/releases/tag/th2018-1.6

Please let me know if it works for you on various systems and use cases,
I did only some basic testing.

Greets,
Jacek


From glen at pld-linux.org  Mon Jan  7 16:49:18 2019
From: glen at pld-linux.org (glen)
Date: Mon, 7 Jan 2019 17:49:18 +0200
Subject: mysql package missing
Message-ID: <816151c1-1e40-f05d-f535-347f04bd5e34@pld-linux.org>

can't find mysql client package:

 ?? error: mysql-client: no such package

i don't see any dropping or deprecation notice: https://www.pld-linux.org/


-- 
glen



From baggins at pld-linux.org  Mon Jan  7 20:12:10 2019
From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=)
Date: Tue, 8 Jan 2019 04:12:10 +0900
Subject: mysql package missing
In-Reply-To: <816151c1-1e40-f05d-f535-347f04bd5e34@pld-linux.org>
References: <816151c1-1e40-f05d-f535-347f04bd5e34@pld-linux.org>
Message-ID: <20190107191210.GA19467@tachikoma.lan>

On Mon, 07 Jan 2019, glen wrote:

> can't find mysql client package:
> 
>  ?? error: mysql-client: no such package
> 
> i don't see any dropping or deprecation notice: https://www.pld-linux.org/

Huh?

poldek:/all-avail> ls mysql-client
mysql-client-5.7.24-2.x86_64
1 package

poldek:/all-avail> get mysql-client
Retrieving th::mysql-client-5.7.24-2.x86_64.rpm...
.............................. 100.0% [1.2M (1.2M/s)]


-- 
Jan R?korajski                    | PLD/Linux
SysAdm | baggins<at>pld-linux.org | http://www.pld-linux.org/


From glen at delfi.ee  Mon Jan  7 20:50:49 2019
From: glen at delfi.ee (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=)
Date: Mon, 7 Jan 2019 21:50:49 +0200
Subject: mysql package missing
In-Reply-To: <20190107191210.GA19467@tachikoma.lan>
References: <816151c1-1e40-f05d-f535-347f04bd5e34@pld-linux.org>
 <20190107191210.GA19467@tachikoma.lan>
Message-ID: <d0729cb6-3317-3323-ca7d-7cf9a582d436@delfi.ee>


On 07/01/2019 21:12, Jan R?korajski wrote:
> On Mon, 07 Jan 2019, glen wrote:
>
>> can't find mysql client package:
>>
>>   ?? error: mysql-client: no such package
>>
>> i don't see any dropping or deprecation notice: https://www.pld-linux.org/
> Huh?
>
> poldek:/all-avail> ls mysql-client
> mysql-client-5.7.24-2.x86_64
> 1 package
>
> poldek:/all-avail> get mysql-client
> Retrieving th::mysql-client-5.7.24-2.x86_64.rpm...
> .............................. 100.0% [1.2M (1.2M/s)]

local mirror sync error :/

sync got broken due no permission to create snap dirs and snap dir was 
not blacklisted... typical 1 jan problems :)





From glen at delfi.ee  Mon Jan  7 20:51:41 2019
From: glen at delfi.ee (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=)
Date: Mon, 7 Jan 2019 21:51:41 +0200
Subject: ntpd autoops error
Message-ID: <15cf5cc1-d8a9-b5fc-0ea6-5dd9ef3471cd@delfi.ee>

can not find any package whose version matches "42" or "41"....

```
Stopping ntpd service..............................................[ DONE ]
Starting ntpd service..............................................[ FAIL ]
Automated Options Processing Error!
 ??????? /usr/sbin/ntpd called AutoOpts function with structure version 
42:0:1.
 ??????? This exceeds the compiled library version:? 41:1:16
(AutoOpts bug):? optionProcess() was called with invalid data.
```



From adamg at pld-linux.org  Mon Jan 21 08:36:31 2019
From: adamg at pld-linux.org (Adam Golebiowski)
Date: Mon, 21 Jan 2019 08:36:31 +0100
Subject: srcbuilder expired cert
Message-ID: <20190121073631.GA32616@adamg.eu>

Hi,

seems like ssl cert for srcbuilder expired:

[adamg at adamg ~]$ openssl s_client --connect srcbuilder.pld-linux.org:1235
(...)
depth=0 CN = srcbuilder.pld-linux.org
verify error:num=10:certificate has expired
notAfter=Jan 20 23:42:15 2019 GMT
(...)
[adamg at adamg ~]$





From arekm at maven.pl  Mon Jan 21 13:46:17 2019
From: arekm at maven.pl (=?UTF-8?Q?Arkadiusz_Mi=c5=9bkiewicz?=)
Date: Mon, 21 Jan 2019 13:46:17 +0100
Subject: srcbuilder expired cert
In-Reply-To: <20190121073631.GA32616@adamg.eu>
References: <20190121073631.GA32616@adamg.eu>
Message-ID: <c196c985-cfa4-91c4-d4c1-eb8d310746da@maven.pl>

On 21/01/2019 08:36, Adam Golebiowski wrote:
> Hi,
> 
> seems like ssl cert for srcbuilder expired:
> 
> [adamg at adamg ~]$ openssl s_client --connect srcbuilder.pld-linux.org:1235
> (...)
> depth=0 CN = srcbuilder.pld-linux.org
> verify error:num=10:certificate has expired
> notAfter=Jan 20 23:42:15 2019 GMT
> (...)
> [adamg at adamg ~]$

Fixed.


-- 
Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org )


From arekm at maven.pl  Fri Jan 25 19:13:57 2019
From: arekm at maven.pl (=?UTF-8?Q?Arkadiusz_Mi=c5=9bkiewicz?=)
Date: Fri, 25 Jan 2019 19:13:57 +0100
Subject: [packages/postgrey] - migrate configuration to /etc/postfix
In-Reply-To: <d545a6c3390ab2ebc284896499594a8d46ec94a1_refs_heads_master@pld-linux.org>
References: <471cfb40376db9c910b472e4d5b7fba28855fa40_refs_heads_master@pld-linux.org>
 <d545a6c3390ab2ebc284896499594a8d46ec94a1_refs_heads_master@pld-linux.org>
Message-ID: <453c71b8-ebf2-e592-baaa-f2ec3a9684ff@maven.pl>

On 25/01/2019 18:54, hawk wrote:
> commit d545a6c3390ab2ebc284896499594a8d46ec94a1
> Author: Marcin Krol <hawk at tld-linux.org>
> Date:   Fri Jan 25 18:53:51 2019 +0100
> 
>     - migrate configuration to /etc/postfix

/etc/mail was a bad idea, so such migration in all MTAs and tools is
welcome :)

-- 
Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org )


From jajcus at jajcus.net  Fri Jan 25 19:32:10 2019
From: jajcus at jajcus.net (Jacek Konieczny)
Date: Fri, 25 Jan 2019 19:32:10 +0100
Subject: [packages/postgrey] - migrate configuration to /etc/postfix
In-Reply-To: <453c71b8-ebf2-e592-baaa-f2ec3a9684ff@maven.pl>
References: <471cfb40376db9c910b472e4d5b7fba28855fa40_refs_heads_master@pld-linux.org>
 <d545a6c3390ab2ebc284896499594a8d46ec94a1_refs_heads_master@pld-linux.org>
 <453c71b8-ebf2-e592-baaa-f2ec3a9684ff@maven.pl>
Message-ID: <06b96a37-6410-3030-d825-d2e9f115ec68@jajcus.net>

On 25/01/2019 19.13, Arkadiusz Mi?kiewicz wrote:
> On 25/01/2019 18:54, hawk wrote:
>> commit d545a6c3390ab2ebc284896499594a8d46ec94a1
>> Author: Marcin Krol <hawk at tld-linux.org>
>> Date:   Fri Jan 25 18:53:51 2019 +0100
>>
>>     - migrate configuration to /etc/postfix
> 
> /etc/mail was a bad idea, so such migration in all MTAs and tools is
> welcome :)

yes! :-)




From hawk at pld-linux.org  Fri Jan 25 21:14:10 2019
From: hawk at pld-linux.org (Marcin Krol)
Date: Fri, 25 Jan 2019 21:14:10 +0100
Subject: [packages/postgrey] - migrate configuration to /etc/postfix
In-Reply-To: <453c71b8-ebf2-e592-baaa-f2ec3a9684ff@maven.pl>
References: <471cfb40376db9c910b472e4d5b7fba28855fa40_refs_heads_master@pld-linux.org>
 <d545a6c3390ab2ebc284896499594a8d46ec94a1_refs_heads_master@pld-linux.org>
 <453c71b8-ebf2-e592-baaa-f2ec3a9684ff@maven.pl>
Message-ID: <5C4B6E12.2080602@pld-linux.org>

> /etc/mail was a bad idea, so such migration in all MTAs and tools is
> welcome :)

Except sendmail where /etc/mail seems to be "worldwide" default.

/etc/ftpd is next to go in TLD.

About merging back such changes...

1) I don't use PLD at all so I have no way to test changes in real 
environment and to be honest I have no time to setup some VMs just for 
testing. Also some packages in PLD simply don't exist in TLD so I won't 
update/migrate them.

2) There is no systemd in TLD. I won't touch any systemd or related 
stuff like in init/triggers/pre/post etc. I simply have no way to test 
these things.

3) In TLD I don't have to worry if some upgrade breaks things between 
distro releases as long as online docs say how to deal with it.

So... If above is fine for PLD I can merge some changes. If above is not 
fine then I guess I'm out, but of course someone may selectively merge 
things back from TLD git.

M.

P.S. For same reasons I'm not merging back some other changes, ie. 
versioned PostgreSQL allowing parallel install of multiple versions (in 
which I have yet to move configs to /etc BTW) and newer versions of some 
packages.



From mike at altlinux.org  Sat Jan 26 12:13:27 2019
From: mike at altlinux.org (Michael Shigorin)
Date: Sat, 26 Jan 2019 14:13:27 +0300
Subject: [packages/postgrey] - migrate configuration to /etc/postfix
In-Reply-To: <5C4B6E12.2080602@pld-linux.org>
References: <471cfb40376db9c910b472e4d5b7fba28855fa40_refs_heads_master@pld-linux.org>
 <d545a6c3390ab2ebc284896499594a8d46ec94a1_refs_heads_master@pld-linux.org>
 <453c71b8-ebf2-e592-baaa-f2ec3a9684ff@maven.pl>
 <5C4B6E12.2080602@pld-linux.org>
Message-ID: <20190126111327.GE5406@imap.altlinux.org>

On Fri, Jan 25, 2019 at 09:14:10PM +0100, Marcin Krol wrote:
> P.S. For same reasons I'm not merging back some other changes,
> ie.  versioned PostgreSQL allowing parallel install of multiple
> versions (in which I have yet to move configs to /etc BTW) and
> newer versions of some packages.

In ALT, we've moved exactly towards multiple versions so that
people switch (and dump/restore) between them when they know it,
and not after an overlooked line in dist-upgrade's output...
(when it's too late to use the upgraded "dumper" for that)

-- 
?---- WBR, Michael Shigorin / http://altlinux.org
??------ http://opennet.ru / http://anna-news.info


From hawk at pld-linux.org  Sat Jan 26 17:30:08 2019
From: hawk at pld-linux.org (Marcin Krol)
Date: Sat, 26 Jan 2019 17:30:08 +0100
Subject: [packages/postgrey] - migrate configuration to /etc/postfix
In-Reply-To: <20190126111327.GE5406@imap.altlinux.org>
References: <471cfb40376db9c910b472e4d5b7fba28855fa40_refs_heads_master@pld-linux.org>
 <d545a6c3390ab2ebc284896499594a8d46ec94a1_refs_heads_master@pld-linux.org>
 <453c71b8-ebf2-e592-baaa-f2ec3a9684ff@maven.pl>
 <5C4B6E12.2080602@pld-linux.org> <20190126111327.GE5406@imap.altlinux.org>
Message-ID: <5C4C8B10.1050708@pld-linux.org>

> In ALT, we've moved exactly towards multiple versions so that
> people switch (and dump/restore) between them when they know it,
> and not after an overlooked line in dist-upgrade's output...
> (when it's too late to use the upgraded "dumper" for that)

With multiple versions installed it is easier to switch using pg_upgrade 
rather than dump/restore not to mention that running several versions at 
once gives way more flexibility for both admins and software developers.

M.



From adamg at pld-linux.org  Tue Jan 29 08:53:26 2019
From: adamg at pld-linux.org (Adam Golebiowski)
Date: Tue, 29 Jan 2019 08:53:26 +0100
Subject: Fwd: upgrade failed OK: libxcrypt.spec
Message-ID: <20190129075326.GA15788@adamg.eu>


> --- libxcrypt.spec:HEAD:
> cannot remove pam because it's required by util-linux, that is crucial

what's the proper way to work with builders here?


From baggins at pld-linux.org  Tue Jan 29 13:53:33 2019
From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=)
Date: Tue, 29 Jan 2019 13:53:33 +0100
Subject: Fwd: upgrade failed OK: libxcrypt.spec
In-Reply-To: <20190129075326.GA15788@adamg.eu>
References: <20190129075326.GA15788@adamg.eu>
Message-ID: <20190129125332.GA6709@starbug.lan>

On Tue, 29 Jan 2019, Adam Golebiowski wrote:

> 
> > --- libxcrypt.spec:HEAD:
> > cannot remove pam because it's required by util-linux, that is crucial
> 
> what's the proper way to work with builders here?

make-request -r -c '
poldek --up ;
poldek -iv libxcrypt-NEW_VERSION (--force may be needed) ;
poldek -uGv libxcrypt-devel
'

Rebuild packages, and then remove old version from builders
make-request -r -c 'poldek -ev --noask libxcrypt-OLD_VERSION'


-- 
Jan R?korajski                    | PLD/Linux
SysAdm | baggins<at>pld-linux.org | http://www.pld-linux.org/


From adamg at pld-linux.org  Wed Jan 30 09:02:47 2019
From: adamg at pld-linux.org (Adam Golebiowski)
Date: Wed, 30 Jan 2019 09:02:47 +0100
Subject: Fwd: upgrade failed OK: libxcrypt.spec
In-Reply-To: <20190129125332.GA6709@starbug.lan>
References: <20190129075326.GA15788@adamg.eu>
 <20190129125332.GA6709@starbug.lan>
Message-ID: <20190130080247.GA13265@adamg.eu>

On Tue, Jan 29, 2019 at 01:53:33PM +0100, Jan R?korajski wrote:
> On Tue, 29 Jan 2019, Adam Golebiowski wrote:
> 
> > 
> > > --- libxcrypt.spec:HEAD:
> > > cannot remove pam because it's required by util-linux, that is crucial
> > 
> > what's the proper way to work with builders here?
> 
> make-request -r -c '
> poldek --up ;
> poldek -iv libxcrypt-NEW_VERSION (--force may be needed) ;
> poldek -uGv libxcrypt-devel
> '
> 
> Rebuild packages, and then remove old version from builders
> make-request -r -c 'poldek -ev --noask libxcrypt-OLD_VERSION'

thx, that helped


From qboosh at pld-linux.org  Wed Jan 30 20:44:42 2019
From: qboosh at pld-linux.org (Jakub Bogusz)
Date: Wed, 30 Jan 2019 20:44:42 +0100
Subject: [packages/librsvg] - updated dependencies;
 librsvg since 2.42 is partially in rust (what with th-x32?)
In-Reply-To: <fc65f7f1cf360e29b7e44b9835dece9805ad9dbc_refs_heads_master@pld-linux.org>
References: <775f4438b11ae12c8700fcab3790c5a384605f95_refs_heads_master@pld-linux.org>
 <fc65f7f1cf360e29b7e44b9835dece9805ad9dbc_refs_heads_master@pld-linux.org>
Message-ID: <20190130194442.GA4682@mail>

On Wed, Jan 30, 2019 at 08:20:00PM +0100, qboosh wrote:
> commit fc65f7f1cf360e29b7e44b9835dece9805ad9dbc
> Author: Jakub Bogusz <qboosh at pld-linux.org>
> Date:   Wed Jan 30 20:25:13 2019 +0100
> 
>     - updated dependencies; librsvg since 2.42 is partially in rust (what with th-x32?)

According to rust project site, code generation and std lib is supported
on x32, but there is no rustc hosted on x32 system - I assume that x86_64
rustc must be used...


-- 
Jakub Bogusz    http://qboosh.pl/


From baggins at pld-linux.org  Wed Jan 30 21:05:10 2019
From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=)
Date: Wed, 30 Jan 2019 21:05:10 +0100
Subject: [packages/librsvg] - updated dependencies; librsvg since 2.42 is
 partially in rust (what with th-x32?)
In-Reply-To: <20190130194442.GA4682@mail>
References: <775f4438b11ae12c8700fcab3790c5a384605f95_refs_heads_master@pld-linux.org>
 <fc65f7f1cf360e29b7e44b9835dece9805ad9dbc_refs_heads_master@pld-linux.org>
 <20190130194442.GA4682@mail>
Message-ID: <20190130200510.GB19467@tachikoma.lan>

On Wed, 30 Jan 2019, Jakub Bogusz wrote:

> On Wed, Jan 30, 2019 at 08:20:00PM +0100, qboosh wrote:
> > commit fc65f7f1cf360e29b7e44b9835dece9805ad9dbc
> > Author: Jakub Bogusz <qboosh at pld-linux.org>
> > Date:   Wed Jan 30 20:25:13 2019 +0100
> > 
> >     - updated dependencies; librsvg since 2.42 is partially in rust (what with th-x32?)
> 
> According to rust project site, code generation and std lib is supported
> on x32, but there is no rustc hosted on x32 system - I assume that x86_64
> rustc must be used...

1. librsvg-c for x32? https://lwn.net/Articles/771355/
2. get rust functional on x32 (I'm fine with x86_64 runtime and x32 stdlib)
3. drop x32 possibly? https://lwn.net/Articles/774734/

-- 
Jan R?korajski                    | PLD/Linux
SysAdm | baggins<at>pld-linux.org | http://www.pld-linux.org/


From arekm at maven.pl  Thu Jan 31 06:30:59 2019
From: arekm at maven.pl (=?UTF-8?Q?Arkadiusz_Mi=c5=9bkiewicz?=)
Date: Thu, 31 Jan 2019 06:30:59 +0100
Subject: is anyone using x32? was Re: [packages/librsvg] - updated
 dependencies; librsvg since 2.42 is partially in rust (what with th-x32?)
In-Reply-To: <20190130200510.GB19467@tachikoma.lan>
References: <775f4438b11ae12c8700fcab3790c5a384605f95_refs_heads_master@pld-linux.org>
 <fc65f7f1cf360e29b7e44b9835dece9805ad9dbc_refs_heads_master@pld-linux.org>
 <20190130194442.GA4682@mail> <20190130200510.GB19467@tachikoma.lan>
Message-ID: <cf74d0d0-9520-91d1-b7f1-72609d07651f@maven.pl>

On 30/01/2019 21:05, Jan R?korajski wrote:

> 3. drop x32 possibly? https://lwn.net/Articles/774734/


Is anyone using x32 here? Speak up.


(just to be clear x32 != i686)
-- 
Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org )


From glen at delfi.ee  Thu Jan 31 08:00:53 2019
From: glen at delfi.ee (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=)
Date: Thu, 31 Jan 2019 09:00:53 +0200
Subject: is anyone using x32? was Re: [packages/librsvg] - updated
 dependencies; librsvg since 2.42 is partially in rust (what with th-x32?)
In-Reply-To: <cf74d0d0-9520-91d1-b7f1-72609d07651f@maven.pl>
References: <775f4438b11ae12c8700fcab3790c5a384605f95_refs_heads_master@pld-linux.org>
 <fc65f7f1cf360e29b7e44b9835dece9805ad9dbc_refs_heads_master@pld-linux.org>
 <20190130194442.GA4682@mail> <20190130200510.GB19467@tachikoma.lan>
 <cf74d0d0-9520-91d1-b7f1-72609d07651f@maven.pl>
Message-ID: <312e42ad-ecc6-8632-d763-59e8708440f5@delfi.ee>

On 31/01/2019 07:30, Arkadiusz Mi?kiewicz wrote:

> On 30/01/2019 21:05, Jan R?korajski wrote:
>
>> 3. drop x32 possibly?https://lwn.net/Articles/774734/
> Is anyone using x32 here? Speak up.
>
>
> (just to be clear x32 != i686)


nope. did not even manage to build clean chroot, as that time not all 
deps were present.



From arekm at maven.pl  Thu Jan 31 09:05:29 2019
From: arekm at maven.pl (=?UTF-8?Q?Arkadiusz_Mi=c5=9bkiewicz?=)
Date: Thu, 31 Jan 2019 09:05:29 +0100
Subject: stop libidn2 rebuild
Message-ID: <d858f0a9-c1c9-0c1e-d336-2220c2b32be2@maven.pl>


Hello.

Please stop rebuilding with new libidn2.

Upstream reverted so name change:

https://gitlab.com/libidn/libidn2/commit/5abf7ec12e93613a074f7d3ed5c3a2550533ad0f

-- 
Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org )


From adamg at pld-linux.org  Thu Jan 31 11:14:43 2019
From: adamg at pld-linux.org (Adam Golebiowski)
Date: Thu, 31 Jan 2019 11:14:43 +0100
Subject: is anyone using x32? was Re: [packages/librsvg] - updated
 dependencies; librsvg since 2.42 is partially in rust (what with th-x32?)
In-Reply-To: <cf74d0d0-9520-91d1-b7f1-72609d07651f@maven.pl>
References: <775f4438b11ae12c8700fcab3790c5a384605f95_refs_heads_master@pld-linux.org>
 <fc65f7f1cf360e29b7e44b9835dece9805ad9dbc_refs_heads_master@pld-linux.org>
 <20190130194442.GA4682@mail> <20190130200510.GB19467@tachikoma.lan>
 <cf74d0d0-9520-91d1-b7f1-72609d07651f@maven.pl>
Message-ID: <20190131101443.GA18617@adamg.eu>

On Thu, Jan 31, 2019 at 06:30:59AM +0100, Arkadiusz Mi?kiewicz wrote:
> On 30/01/2019 21:05, Jan R?korajski wrote:
> 
> > 3. drop x32 possibly? https://lwn.net/Articles/774734/
> 
> 
> Is anyone using x32 here? Speak up.
> 
> 
> (just to be clear x32 != i686)

nope, i686/x86_64 only.


From glen at delfi.ee  Thu Jan 31 21:34:27 2019
From: glen at delfi.ee (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=)
Date: Thu, 31 Jan 2019 22:34:27 +0200
Subject: python3 only packages
Message-ID: <bfd81b87-03f3-d1fc-682c-3e1444df6aed@delfi.ee>

what should be .spec named?


python3-foo.spec?

python-foo.spec?



```
[~/rpm/packages/google-chrome(71.0.3578.98) (master)?] ? pip2 install repomd
Collecting repomd
 ? Could not find a version that satisfies the requirement repomd (from 
versions: )
No matching distribution found for repomd

[~/rpm/packages/google-chrome(71.0.3578.98) (master)?] ? pip3 install repomd
Collecting repomd
 ? Downloading 
https://files.pythonhosted.org/packages/1f/52/4c448b477f0e9f55b613063bbc49fa326dc277ae7577c836ae8dedd8bcc4/repomd-0.1.0-py3-none-any.whl
Requirement already satisfied: lxml in 
/usr/lib64/python3.7/site-packages (from repomd) (4.2.5)
Installing collected packages: repomd
Could not install packages due to an EnvironmentError: [Errno 13] 
Permission denied: '/usr/local/lib64/python3.7'
Consider using the `--user` option or check the permissions.

[~/rpm/packages/google-chrome(71.0.3578.98) (master)?] ?

```



From arekm at maven.pl  Thu Jan 31 22:57:09 2019
From: arekm at maven.pl (=?UTF-8?Q?Arkadiusz_Mi=c5=9bkiewicz?=)
Date: Thu, 31 Jan 2019 22:57:09 +0100
Subject: python3 only packages
In-Reply-To: <bfd81b87-03f3-d1fc-682c-3e1444df6aed@delfi.ee>
References: <bfd81b87-03f3-d1fc-682c-3e1444df6aed@delfi.ee>
Message-ID: <d4f1ea3a-c327-d590-6ff7-b0f00c7e8f64@maven.pl>

On 31/01/2019 21:34, Elan Ruusam?e wrote:
> what should be .spec named?
> 
> 
> python3-foo.spec?
> 
> python-foo.spec?

I would go with python-foo.spec with python2 bcond disabled for
standalone packages (in case if it gets python2 support somehow).

If you are sure that it won't get python2 support then python3-foo.spec
is fine (we have such packages afaik).


-- 
Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org )