On Mon, 10 Dec 2012, Sergei Trofimovich wrote:
gentoo-x86/profiles/updates $ LANG=C ls -1 --sort=time
[long list omitted]
old entries are done in different context (comparing to 2012):
- some packages change names 2 or 3 times
- slots have different meaning
moreover:
- if you set
Due to limited time and resources these packages are up for grabs:
- app-shells/shish
- dev-db/mysqltuner
- dev-libs/dietlibc
- dev-libs/gecode
- net-analyzer/bwm-ng
- net-analyzer/nagios-check_mysql_health
These packages have been reduced to herd maintainers:
- media-libs/libraw
-
On 12/10/2012 12:10 AM, Paweł Hajdan, Jr. wrote:
I propose that we say, once a year, schedule a tree-cleaning of old
updates files. These updates files could be added to a tarball made
available for download. That way if they are needed to update a system
older than what the main tree has
Greg KH schrieb:
On Mon, Dec 10, 2012 at 12:21:29AM +0100, Chí-Thanh Christopher Nguyễn wrote:
Greg KH schrieb:
No, all we need is to enable EFI stub support in the kernel, and
integrate the initramfs using CONFIG_INITRAMFS_SOURCE and place it in
some location where UEFI looks for it
On Mon, Dec 10, 2012 at 2:52 AM, Rich Freeman ri...@gentoo.org wrote:
I really would like Gentoo to support a self-signed secure boot
framework (obviously this would be for after the system is installed).
https://bugs.gentoo.org/show_bug.cgi?id=444830
You can see how such framework works by
On Sat, Dec 08, 2012 at 11:57:13PM -0500, Fernando Reyes wrote
iirc the minimal install CD ISO is capable of booting from a USB device or
any removable media by just running the following commands.
# isohybrid image.ISO
# did if=image.ISO of=/dev/sdb bs=8192k
sdb being your removable
On Sun, Dec 09, 2012 at 06:37:56PM -0800, Greg KH wrote
Not necessarily, as I'm finding out with real hardware. My only options
on the box I have is to either zero out all keys, or specifically tell
the BIOS what binary to run (doesn't need to be signed, and can not be
changed after telling
On Mon, Dec 10, 2012 at 10:31:25AM -0500, Walter Dnes wrote:
On Sun, Dec 09, 2012 at 06:37:56PM -0800, Greg KH wrote
Not necessarily, as I'm finding out with real hardware. My only options
on the box I have is to either zero out all keys, or specifically tell
the BIOS what binary to run
On Mon, Dec 10, 2012 at 8:36 PM, Greg KH gre...@gentoo.org wrote:
Matthew's frontend shim code is nice and tiny, but the one I am
referring to provides the ability to enroll your own keys in the BIOS,
which shim does not.
I just tried shim in OVMF, and it provides an interface to enroll keys
/
Hello,
I think we're mostly aware what the use and benefits
of the *use.stable.mask files are.
They would be at least really useful in Python ebuilds, where we
have to either:
a) forcedly stabilize a particular Python implementation (like pypy),
b) don't support it all,
c) or just keep two
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/12/12 04:27 PM, Michał Górny wrote:
Hello,
I think we're mostly aware what the use and benefits of the
*use.stable.mask files are.
They would be at least really useful in Python ebuilds, where we
have to either:
a) forcedly
On Mon, 10 Dec 2012 21:01:34 -0500
Ian Stakenvicius a...@gentoo.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/12/12 04:27 PM, Michał Górny wrote:
Hello,
I think we're mostly aware what the use and benefits of the
*use.stable.mask files are.
They would be at
On 12/10/2012 01:27 PM, Michał Górny wrote:
1) duplicate most of the major profiles. Make an EAPI 5-enabled wrapper
profiles which will provide the *use.stable.mask files. Require users
to migrate to those profiles after getting an EAPI 5 capable package
manager (how?). Possibly mask the
13 matches
Mail list logo
