Overview

Request 880703 accepted

No description set
Loading...

Richard Brown's avatar

bind-libs is still required by ksh and installation-images


Josef Möllers's avatar

Please re-consider this fact, as since 9.15.3

[cleanup] Remove isc-config.sh script as the BIND 9 libraries are now purely internal. [GL #1123]


Fabian Vogt's avatar

Both of those can most likely be removed


Jan Engelhardt's avatar

took the leisure; rq 882323


Richard Brown's avatar

bind-libs is still required by ksh and installation-images


Fabian Vogt's avatar

The unversioned library links like %{_libdir}/libbind9.so are only used for development, but apparently all libraries are internal now. So those must not be installed.


Jan Engelhardt's avatar

Surely, if they "must not be installed", upstream could change their Makefile if they really meant it, innit? How scoped is their "internal" - within tarball, within a project (multiple tars)? Questions over questions…


Fabian Vogt's avatar

I wonder whether CFLAGS="... -fPIE ..." actually works properly because shared libraries must not be built with -fPIE.


Jan Engelhardt's avatar

It happens to work by accident because libtool injects its own -fPIC after user CFLAGS.


Richard Brown's avatar

Unignored: returned to active backlog.


Dominique Leuenberger's avatar

we will need a few things that still reference bind-libs or bind-devel:

for bind-libs:

for bind-devel:

bind no longer comes with a -devel package, and the libs are folded into the main package


Josef Möllers's avatar

I cannot find user cvoegel neither can I find "collected"!?!?


Dominique Leuenberger's avatar

that was supposed to be collectd - and the user is @cvoegl


Josef Möllers's avatar

At least ksh builds without bind-libs: [ 1454s] RPMS/x86_64/ksh-93vu-lp152.272.1.x86_64.rpm

As to collectd: 2 Tue Feb 23 16:29:31 UTC 2021 - Reinhard Max max@suse.com 3 4 - The bind plugin does not need bind-devel.

installation-images also BuildRequires bind-utils which now has the libraries, this should also work.

I've started a build of installation-images without the "BuildRequires bind-libs", but can't see the build log :-( At least "osc r" says openSUSE_Factory_standard x86_64 installation-images:openSUSE succeeded so, I gather, it's not "failed".


Dominique Leuenberger's avatar

That's pretty much what I was hoping for! Thankf for doing the tests (collected is indeed fixed by now; so ksh and installation-images are the two offenders left)


Dominique Leuenberger's avatar

Waiting for ksh and i-i fixes

Request History
Marcus Meissner's avatar

msmeissn created request


Factory Auto's avatar

factory-auto added opensuse-review-team as a reviewer

Please review sources


Factory Auto's avatar

factory-auto accepted review

Check script succeeded


Saul Goodman's avatar

licensedigger accepted review

ok


Jan Engelhardt's avatar

jengelh accepted review


Richard Brown's avatar

RBrownSUSE set openSUSE:Factory:Staging:I as a staging project

Being evaluated by staging project "openSUSE:Factory:Staging:I"


Richard Brown's avatar

RBrownSUSE accepted review

Picked "openSUSE:Factory:Staging:I"


Richard Brown's avatar

RBrownSUSE added factory-staging as a reviewer

Being evaluated by group "factory-staging"


Richard Brown's avatar

RBrownSUSE accepted review

Unstaged from project "openSUSE:Factory:Staging:I"


Richard Brown's avatar

RBrownSUSE set openSUSE:Factory:Staging:J as a staging project

Being evaluated by staging project "openSUSE:Factory:Staging:J"


Richard Brown's avatar

RBrownSUSE accepted review

Picked "openSUSE:Factory:Staging:J"


Richard Brown's avatar

RBrownSUSE accepted review

Staging Project openSUSE:Factory:Staging:J got accepted.


Richard Brown's avatar

RBrownSUSE approved review

Staging Project openSUSE:Factory:Staging:J got accepted.


Richard Brown's avatar

RBrownSUSE accepted request

Staging Project openSUSE:Factory:Staging:J got accepted.

openSUSE Build Service is sponsored by