public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev-announce@lists.gentoo.org, gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] keywording ~sys-libs/glibc-2.26
Date: Sat, 11 Nov 2017 17:49:37 +0100	[thread overview]
Message-ID: <1545404.MWRFALAhJB@porto> (raw)

[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]

Hi all, 

in the next days I'll likely re-add keywords to glibc-2.26. So, if you haven't 
fixed your package for build failures yet, now would be the time. 

The tracker is https://bugs.gentoo.org/show_bug.cgi?id=glibc-2.26 with 
appropriate subtrackers.

1) Your package needs RPC (and already now fails to build with sys-libs/
glibc[-rpc]). 

See https://wiki.gentoo.org/wiki/Project:Toolchain/RPC_implementation for a 
detailed guide.

2) Your package uses NIS/YP functionality, and builds against / links to 
libnsl. 

Add a dependeny (DEPEND and RDEPEND):
  net-libs/libnsl:0=

You can already safely do this now ( =net-libs/libnsl-0 is a dummy, stable on 
all arches, installs no files, depends on <sys-libs/glibc-2.26 ), and as an 
additional bonus will get the subslot rebuild automagically once libnsl is 
updated. 

(The unbundled libnsl has increased soversion, libnsl.so.2. glibc will keep 
installing libnsl.so.1 as compatibility library for binary packages, but 
without headers etc.)

3) Your package needs internal data structures and fails with undefined types.

Ping me. Most likely problem and fix are already known.

Cheers, 
Andreas

-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer 
(council, toolchain, perl, libreoffice, comrel)

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2017-11-11 16:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-11 16:49 Andreas K. Huettel [this message]
2017-11-12 14:21 ` [gentoo-dev] keywording ~sys-libs/glibc-2.26 Andreas K. Huettel
2017-11-12 19:53 ` Joshua Kinard
2017-11-12 20:32   ` Andreas K. Huettel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1545404.MWRFALAhJB@porto \
    --to=dilfridge@gentoo.org \
    --cc=gentoo-dev-announce@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox