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 serious pain more than once, but > it can be a pain to keep up with the updates sometimes... > > 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... You could write a script that runs emerge -ublah @world, parses the output and then checks the timestamps of the ebuilds. It could then filter packages based on the age of the ebuild, instead of showing a date and letting you do the work. -- Neil Bothwick All things being equal, fat people use more soap. signature.asc Description: PGP signature
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. Could be nice to have such info. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJTR/fuAAoJEK64IL1uI2haKwUH/i9soO5yNcsP9iARgbrkP/0D jmZPVzdqgN2K4WwSE8ZPgCNdBNuAYwI+nFe/mjcQp7wp+CQXnOyRPrKgSQUiDjxn rDonCGqVmE15fQDAYJdapUxcsfCeuc3VUB1tA/j9A8XeTHqu5FO2hsMs0RcTsxv/ 4PDI8hSbB64Ol1n4lDgaoP65gUFy54C6w611LBE8y/fj0+bwlfrUZFk+Cn+l+ekZ hap8+sCR2pZVTuAc9vbQ/cc0J6C9+DDA+fQNLhGoa8P+pX9U2cbgsVwDHCNnhpRV CxgnTAtFDxf0vDJZk4Xi9l9/Ny8FcIPs54W+wOYCycA5X4UxPZKi4l5hl54kSKM= =W/uy -END PGP SIGNATURE-
[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 saved me some serious pain more than once, but it can be a pain to keep up with the updates sometimes... 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... ie, instead of: myhost : Fri Apr 11, 07:45:44 : ~ # emerge -pvuDN world These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] media-libs/libpng-1.6.10:0/16 [1.6.8:0/16] USE="-apng (-neon) -static-libs" ABI_X86="(64) (-32) (-x32)" 878 kB Total: 1 package (1 upgrade), Size of downloads: 878 kB myhost : Fri Apr 11, 09:08:03 : ~ # something like: myhost : Fri Apr 11, 07:45:44 : ~ # emerge -pvuDN world These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] media-libs/libpng-1.6.10:0/16 [1.6.8:0/16, released 4/11/14 at 13:11 am] USE="-apng (-neon) -static-libs" ABI_X86="(64) (-32) (-x32)" 878 kB Total: 1 package (1 upgrade), Size of downloads: 878 kB myhost : Fri Apr 11, 09:08:03 : ~ # Of course I don't care exactly where or how the date/time is displayed, just that it is there... So... is this feasible (without a lot of hard work)? Thanks, Charles
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 -- ,, SUPPORT ___//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT`-O--O---' purslowatchassdotutorontodotca
