Re: [packages/openssl102: 432/432] - cloned from openssl branch v1.0.2 as openssl102 to make it parallel-installable with current 1.1.1

2018-10-01 Thread Jacek Konieczny 
On 01/10/2018 22.17, Elan Ruusamäe wrote:
> On 29/09/2018 02:37, adwol wrote:

> altho i prefer just to keep same package multiple versions installed:
> 
> 
> # rpm -q openssl
> openssl-1.0.2o-1.x86_64
> openssl-1.1.1-1.x86_64

This does not work well with upgrades (e.g. „upgrade *” in poldek gives
„multiple versions installed”). IMHO separate package with own name is
much cleaner.

For me it does not matter much if it is build from a different branch of
the same spec or from a separate repo, but as branches is how we do it
with kernel or php, then I guess it is the way to go.


Jacek
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en

Re: [packages/openssl102: 432/432] - cloned from openssl branch v1.0.2 as openssl102 to make it parallel-installable with current 1.1.1

2018-10-01 Thread Elan Ruusamäe 

On 29/09/2018 02:37, adwol wrote:


commit 9fc1b1b87b259e8a327c99835865e91a391efc9e
Author: Adam Osuchowski 
Date:   Sat Sep 29 00:55:56 2018 +0200

 - cloned from openssl branch v1.0.2 as openssl102 to make it 
parallel-installable with current 1.1.1 and newer

  openssl-man-namespace.patch |   6 +-
  openssl.spec => openssl102.spec | 158 
  2 files changed, 84 insertions(+), 80 deletions(-)
---
diff --git a/openssl.spec b/openssl102.spec


why not just update Name on openssl package branch?

altho i prefer just to keep same package multiple versions installed:


# rpm -q openssl
openssl-1.0.2o-1.x86_64
openssl-1.1.1-1.x86_64
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en

Re: glibc and ldconfig dependency loop

2018-10-01 Thread glen 



On 10/1/18 11:36 AM, Jacek Konieczny wrote:

 From my logs of (automated) building a fresh system in a chroot:



build   01-Oct-2018 09:25:17warning: LOOP:
build   01-Oct-2018 09:25:17warning: removing glibc-2.28-5.aos1.i686
"Requires(postun): /sbin/ldconfig" from tsort relations.
build   01-Oct-2018 09:25:17warning: removing ldconfig-2.28-5.aos1.i686
"Requires(auto): rtld(GNU_HASH)" from tsort relations.
[...]
build   01-Oct-2018 09:25:19glibc
##
build   01-Oct-2018 09:25:19/sbin/ldconfig: No such file or directory
build   01-Oct-2018 09:25:19error: %post(glibc-2.28-5.aos1.i686)
scriptlet failed, exit status 127
build   01-Oct-2018 09:25:19ldconfig
##

This causes whole poldek install command to fail.

Such loops make chroot installs or major updates unpredictable and when
glibc is installed before ldconfig, then its %post will fail. What is
worse, such loops can break installation order or other packages
installed in the batch.

Possible solutions:
– disable autogenerated dependency for ldconfig, to force installing it
before glibc
– include ldconfig in the main glibc package
– change glibc %post so it won't fail on ldconfig error. The easiest
one, will fix the glibc installation failure, but won't break the
dependency loop.

Any better ideas?


make ldconfig package skip rtld(GNU_HASH) dependency.
by building (linking?) it it differently; or just do rpm ignore magic?

also, before merging ldconfig to glibc package,
please find from git history why the split was made in first place.

$ rpm -q ldconfig --requires
ldconfig-6:2.27-3.x32
FHS
rtld(GNU_HASH)
uname(release) >= 3.4.0
rpmlib(PayloadIsLzma) <= 4.4.6-1
ldconfig-6:2.28-5.x86_64
FHS
rtld(GNU_HASH)
uname(release) >= 3.2.0
rpmlib(PayloadIsLzma) <= 4.4.6-1

➔ rpm -q --what-provides 'rtld(GNU_HASH)'
glibc-2.28-5.x86_64

➔ rpm -q ldconfig
ldconfig-2.27-3.x32
ldconfig-2.28-5.x86_64

➔

--
glen

___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en