Re: [gentoo-user] Show ebuild date/time in emerge --pretend output

On Fri, 11 Apr 2014 09:30:43 -0400, Tanstaafl wrote: > One of the things I do to minimize getting bit by newly released buggy > ebuilds is to wait a few days after a new update is available before > updating... Isn't that what the stable tree is for? > This works well, and has saved me some s

Re: [gentoo-user] Show ebuild date/time in emerge --pretend output

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 04/11/14 17:30, Tanstaafl wrote: > What would be really helpful would be if the emerge --pretend > output could show the date (and time?) that the new ebuild was made > available... I thought of something like this, but in emerge --search summary

[gentoo-user] Show ebuild date/time in emerge --pretend output

Hi all, I'm wondering if this is even feasible before I go open a bug/enhancement request for portage for this... One of the things I do to minimize getting bit by newly released buggy ebuilds is to wait a few days after a new update is available before updating... This works well, and has

Re: [gentoo-user] Re: 'Heartbleed' bug

140410 walt wrote: > Anyone here really understand the underlying principles? There's an excellent description of the bug + the fix here : http://blog.cryptographyengineering.com/2014/04/attack-of-week-openssl-heartbleed.html -- ,,