On Mon, May 21, 2012 at 4:55 PM, Mark Knecht <markkne...@gmail.com> wrote: > On Mon, May 21, 2012 at 8:04 AM, Markos Chandras <hwoar...@gentoo.org> wrote: >> On Mon, May 21, 2012 at 3:46 PM, Mark Knecht <markkne...@gmail.com> wrote: >>> I love my Gentoo-devs, but what is the train of thought here? >>> skype-2.2.0.35-r1 was ~amd64 yesterday. It's installed and working >>> fine. Today 2.2.0.35-r99 is ~amd64, which is perfectly fine, but >>> they've completely removed -r1 and now I'm required to unmask >>> emulation packages that only came out today? That doesn't seem quite >>> right... >>> >>> Why did they completely get rid of -r1? That should stick around for a >>> little while after -r99 becomes ~amd64, shouldn't it? >>> >>> - Mark > <SNIP> >> >> -r1 had a security problem. You should unmask the emulation packages >> and continue the update process. Look at the ChangeLog so see what >> changed. Both versions are ~amd64 so I don't understand your complain >> about keeping -r1 in the tree for a while. >> >> Markos >> > > Thanks Markos. That's likely what I'll do, although the alternative > I'm looking at for now is possibly getting -r1 from an overlay. > > I didn't think I was _complaining_. I was just asking what the train > of thought was that leads them to do this sort of thing. Everything in > the world has a security problem. We know they are either found or not > found. Unmasking 8 emulation libraries that have _yesterdays_ date in > their names, and therefore makes them quite new, may: > > 1) Create more security problems > > 2) Create issues with other programs that use the libraries. > > Anyway, thanks for the response. I'll either unmask or use an overlay. > > Cheers, > Mark >
Well, based on my experience, the emul-* packages are rather safe to use so it should not be a problem to unmask them. Otherwise, you can always grab -r1 from http://sources.gentoo.org and keep it in a local overlay Markos
