public inbox for gentoo-hardened@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sergei Trofimovich <slyfox@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: gentoo-hardened@lists.gentoo.org
Subject: [gentoo-hardened] Re: [gentoo-dev] profiles/features/64bit-native/package.use.mask contents redundancy
Date: Sat, 11 Feb 2012 22:41:36 +0300	[thread overview]
Message-ID: <20120211224136.6637e662@sf.home> (raw)
In-Reply-To: <20120211214848.75eea595@sf.home>

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

> > Looks like 'arch/amd64/no-multilib' profile inclusion is kept in
> > sync with 'features/64bit-native' one: [1]. Exception is
> > 'hardened/linux/amd64/no-multilib' profile. Looks like a bug.
> 
> Synced this bit with a fix:
> 
> |  11 Feb 2012; Sergei Trofimovich <slyfox@gentoo.org>
> |  hardened/linux/amd64/no-multilib/parent:
> |  Make hardened/linux/amd64/no-multilib include arch/amd64/no-multilib
> |  (http://archives.gentoo.org/gentoo-dev/msg_7c41ab6653426048c2e8b0f271637bf3.x
> |  ml).

And the change brought the breakage:

New profiles popped up:
| /usr/portage/profiles/arch/base
| /usr/portage/profiles/features/multilib
| /usr/portage/profiles/features/multilib/lib32

Likely because of double inclusion of some suspicious
parent profiles.

Reverted the change :[

-- 

  Sergei

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2012-02-11 19:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120211173807.4d1a47ae@sf.home>
2012-02-11 18:48 ` [gentoo-hardened] Re: [gentoo-dev] profiles/features/64bit-native/package.use.mask contents redundancy Sergei Trofimovich
2012-02-11 19:41   ` Sergei Trofimovich [this message]
2012-02-12 18:15     ` Sergei Trofimovich
     [not found]       ` <4F3823A4.7010008@gentoo.org>
2012-02-13 16:16         ` Sergei Trofimovich

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=20120211224136.6637e662@sf.home \
    --to=slyfox@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gentoo-hardened@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