From: Beso <givemesugarr@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] amd64codecs masked
Date: Sun, 9 Nov 2008 11:18:28 +0000 [thread overview]
Message-ID: <d257c3560811090318m731b71cch1eb75705546ebb32@mail.gmail.com> (raw)
In-Reply-To: <20081108233742.6e86e0b9@ilievnet.com>
2008/11/8 Daniel Iliev <daniel.iliev@gmail.com>:
> On Fri, 7 Nov 2008 10:57:42 +0100
> Beso <givemesugarr@gmail.com> wrote:
>
>> 2008/11/7 Daniel Iliev <daniel.iliev@gmail.com>:
>> >
>> > Hi, guys
>> >
>> > Recently, after "emerge --sync && emerge -DuN world" portage
>> > started to show me warning that amd64codes is masked by Mr Steve
>> > Dibb for security reasons [1].
>> >
>> > Yes, I have amd64codes installed as dependency of mplayer [2], but
>> > I'm pleased with my system now and I don't want to damage mplayer by
>> > uninstalling those codecs. On the other hand, of course, I don't
>> > want to have problematic packages installed. What should I do in
>> > this case?
>> >
>> >
>
> [snip]
>
>>
>> the bug doesn't really seems very bad from the bug descrition. you
>> could just manually unmask the package as i did. the alternative is to
>> use -real and to not compile any realcodecs but you won't be able to
>> play wmv and rm files anymore. if you don't have that sort of files
>> you could just use -real and remove the amd64codecs.
>
>
> Thanks for the reply.
> I hate to unmask packages, because I forget to clean the entries
> when they become obsolete. It seems I'll make an exception this
> time.
>
just unmask the full version with
=media-libs/amd64codecs-20071007
--
dott. ing. beso
next prev parent reply other threads:[~2008-11-09 11:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 8:36 [gentoo-amd64] amd64codecs masked Daniel Iliev
2008-11-07 9:57 ` Beso
2008-11-08 21:37 ` Daniel Iliev
2008-11-09 11:18 ` Beso [this message]
2008-11-12 0:11 ` Matthias Bethke
2008-11-08 22:03 ` Christoph Mende
2008-11-09 22:50 ` [gentoo-amd64] [kind of solved] " Daniel Iliev
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=d257c3560811090318m731b71cch1eb75705546ebb32@mail.gmail.com \
--to=givemesugarr@gmail.com \
--cc=gentoo-amd64@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