Re: [gentoo-dev] grub:2 keywords
Mike Gilbert flop...@gentoo.org writes: My main concern is that many people probably have sys-boot/grub in @world. How about a news item advising people to put sys-boot/grub:0 in their world file to retain grub:0? If grub:2 is made visible, portage will install it, and will remove grub-0.97 on the next depclean. This could be a little confusing, but should not cause any immediate damage since the copy of grub-0.97 installed in the MBR and /boot would remain intact. Is this worthy of a news item? Or I just blog about it? pgpGRtgZ6kn8y.pgp Description: PGP signature
Re: [gentoo-dev] grub:2 keywords
On Mon, 25 Jun 2012 01:35:19 -0400 Richard Yao r...@gentoo.org wrote: On 06/25/2012 12:15 AM, Mike Gilbert wrote: An official release of grub-2.00 should be coming pretty soon. I would like to keyword this for ~amd64 and ~x86 shortly after it hits the tree. I don't do much work on base system packages, so I would like some advice on how to make this as smooth as possible. My main concern is that many people probably have sys-boot/grub in @world. If grub:2 is made visible, portage will install it, and will remove grub-0.97 on the next depclean. This could be a little confusing, but should not cause any immediate damage since the copy of grub-0.97 installed in the MBR and /boot would remain intact. Is this worthy of a news item? Or I just blog about it? Anything else I need to think about here? Note: The Gentoo Documentation Project has indicated that they do not want to add anything to the handbook until we are somewhat close to stabilizing grub:2. That's at least a couple months away. I think it would be best to move sys-boot/grub:2 to sys-boot/grub2. That should avoid confusion. If our plan is to replace grub1 with grub2 at some point, that seems incorrect. In other words, if grub2 is 'natural progress' from grub1. -- Best regards, Michał Górny signature.asc Description: PGP signature
[gentoo-dev] bug XXXXXX sys-libs/tdb fail check for building library support
neither stable tdb-1.2.9 nor tdb-1.2.10 install any shared library when build with distcc, because of a failing chech @ configure time Checking for building library support: not found setting MAKEOPTS=-j1 does not suffice FEATURES=-distcc is needed FYI the check is inside buildtools/wafsamba/samba_conftests.py def CHECK_LIBRARY_SUPPORT(conf, rpath=False, version_script=False, msg=None): bld.compile() except with a file not found Portage 2.2.0_alpha111 (default/linux/amd64/10.0, gcc-4.6.3, glibc-2.15-r2, 3.4.1-vs2.3.3.4 x86_64) = System uname: Linux-3.4.1-vs2.3.3.4-x86_64-Intel-R-_Core-TM-_i7-2600_CPU_@_3.40GHz-with-gentoo-2.1 Timestamp of tree: Sun, 24 Jun 2012 19:30:01 + distcc 3.1 x86_64-pc-linux-gnu [enabled] ccache version 3.1.7 [disabled] app-shells/bash: 4.2_p20 dev-java/java-config: 2.1.11-r3 dev-lang/python: 2.7.3-r2 dev-util/ccache: 3.1.7 dev-util/cmake: 2.8.7-r5 dev-util/pkgconfig: 0.26 sys-apps/baselayout: 2.1-r1 sys-apps/openrc: 0.10.3 sys-apps/sandbox: 2.5 sys-devel/autoconf: 2.13, 2.68 sys-devel/automake: 1.10.3, 1.11.1 sys-devel/binutils: 2.22-r1 sys-devel/gcc:4.5.3-r2, 4.6.3, 4.7.1 sys-devel/gcc-config: 1.7.3 sys-devel/libtool:2.4-r1 sys-devel/make: 3.82-r1 sys-kernel/linux-headers: 3.4 (virtual/os-headers) sys-libs/glibc: 2.15-r2 Repositories: gentoo vivovl mysql ACCEPT_KEYWORDS=amd64 ACCEPT_LICENSE=* CBUILD=x86_64-pc-linux-gnu CFLAGS=-O2 -march=corei7-avx -pipe -frecord-gcc-switches -mno-movbe -mno-abm -mno-lwp -mno-fma -mno-fma4 -mno-xop -mno-bmi -mno-tbm --param l1-cache-size=32 --param l1-cache-line-size=64 --param l2-cache-size=8192 -mtune=corei7-avx -fgcse-after-reload -fpredictive-commoning -ftree-vectorize -funswitch-loops -fgraphite-identity -floop-block -floop-interchange -floop-strip-mine -ggdb -gdwarf-4 -fvar-tracking-assignments CHOST=x86_64-pc-linux-gnu CONFIG_PROTECT=/etc /usr/share/config /usr/share/gnupg/qualified.txt /usr/share/openvpn/easy-rsa /usr/share/themes/oxygen-gtk/gtk-2.0 CONFIG_PROTECT_MASK=/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/php/apache2-php5.3/ext-active/ /etc/php/cgi-php5.3/ext-active/ /etc/php/cli-php5.3/ext-active/ /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c CXXFLAGS=-O2 -march=corei7-avx -pipe -frecord-gcc-switches -mno-movbe -mno-abm -mno-lwp -mno-fma -mno-fma4 -mno-xop -mno-bmi -mno-tbm --param l1-cache-size=32 --param l1-cache-line-size=64 --param l2-cache-size=8192 -mtune=corei7-avx -fgcse-after-reload -fpredictive-commoning -ftree-vectorize -funswitch-loops -fgraphite-identity -floop-block -floop-interchange -floop-strip-mine -ggdb -gdwarf-4 -fvar-tracking-assignments -fvisibility-inlines-hidden DISTDIR=/g/distfiles EMERGE_DEFAULT_OPTS=--ask-enter-invalid --quiet-build=y FCFLAGS=-O2 -pipe FEATURES=assume-digests binpkg-logs buildpkg compress-build-logs compressdebug config-protect-if-modified distcc distlocks ebuild-locks fail-clean fixlafiles installsources metadata-transfer news noinfo notitles parallel-fetch parallel-install parse-eapi-ebuild-head sandbox sfperms splitdebug strict test-fail-continue unknown-features-warn unmerge-logs unmerge-orphans xattr FFLAGS=-O2 -pipe GENTOO_MIRRORS=http://mirror.netcologne.de/gentoo/ http://mirror.ovh.net/gentoo-distfiles/ http://mirror.switch.ch/ftp/mirror/gentoo/ http://gentoo.lagis.at/ http://mirror.qubenet.net/mirror/gentoo/; INSTALL_MASK=/usr/lib64/libogrove.la /usr/lib64/libospgrove.la /usr/lib64/libostyle.la /usr/lib64/vlc/plugins/codec/libdirac_plugin.la /usr/lib64/vlc/plugins/demux/libdirac_plugin.la /bin/systemd /bin/systemctl /usr/lib64/elektra/libelektra-filesys.la /usr/lib64/elektra/libelektra-hosts.la /usr/lib64/elektra/libelektra-ini.la /usr/lib64/elektra/libelektra-passwd.la /usr/lib64/libelektra-cpp.la /usr/lib64/libelektra.la /usr/lib64/libelektratools.la LDFLAGS=-Wl,-O1 -Wl,--as-needed -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -Wl,--sort-common -Wl,--no-copy-dt-needed-entries -Wl,--build-id LINGUAS=it MAKEOPTS=-j36 PKGDIR=/g/packages PORTAGE_COMPRESS=lzma PORTAGE_CONFIGROOT=/ PORTAGE_RSYNC_OPTS=--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages PORTAGE_TMPDIR=/var/tmp PORTDIR=/g/portage PORTDIR_OVERLAY=/g/ovl/tmp /g/ovl/mysql SYNC=rsync://rsync.gentoo.org/gentoo-portage USE=acl amd64 avx berkdb bzip2 caps cli cracklib crypt cups cxx dbus dri fortran gdbm gpm iconv ipv6 modules mudflap multilib ncurses nls nptl opencl opengl openmp pam pcre pppd qt3support readline semantic-desktop session sse sse2 sse3 sse4_1 ssl ssse3 static-libs svg tcpd unicode xattr xorg zlib ALSA_CARDS=ali5451
Re: [gentoo-dev] bug XXXXXX sys-libs/tdb fail check for building library support
Open a bug at http://bugs.gentoo.org/ instead of mailing here. Yeah, I know bugzilla is down but it's only temporary. - Samuli On 06/25/2012 02:54 PM, Francesco Riosa wrote: neither stable tdb-1.2.9 nor tdb-1.2.10 install any shared library when build with distcc, because of a failing chech @ configure time Checking for building library support: not found setting MAKEOPTS=-j1 does not suffice FEATURES=-distcc is needed FYI the check is inside buildtools/wafsamba/samba_conftests.py def CHECK_LIBRARY_SUPPORT(conf, rpath=False, version_script=False, msg=None): bld.compile() except with a file not found Portage 2.2.0_alpha111 (default/linux/amd64/10.0, gcc-4.6.3, glibc-2.15-r2, 3.4.1-vs2.3.3.4 x86_64) = System uname: Linux-3.4.1-vs2.3.3.4-x86_64-Intel-R-_Core-TM-_i7-2600_CPU_@_3.40GHz-with-gentoo-2.1 Timestamp of tree: Sun, 24 Jun 2012 19:30:01 + distcc 3.1 x86_64-pc-linux-gnu [enabled] ccache version 3.1.7 [disabled] app-shells/bash: 4.2_p20 dev-java/java-config: 2.1.11-r3 dev-lang/python: 2.7.3-r2 dev-util/ccache: 3.1.7 dev-util/cmake: 2.8.7-r5 dev-util/pkgconfig: 0.26 sys-apps/baselayout: 2.1-r1 sys-apps/openrc: 0.10.3 sys-apps/sandbox: 2.5 sys-devel/autoconf: 2.13, 2.68 sys-devel/automake: 1.10.3, 1.11.1 sys-devel/binutils: 2.22-r1 sys-devel/gcc:4.5.3-r2, 4.6.3, 4.7.1 sys-devel/gcc-config: 1.7.3 sys-devel/libtool:2.4-r1 sys-devel/make: 3.82-r1 sys-kernel/linux-headers: 3.4 (virtual/os-headers) sys-libs/glibc: 2.15-r2 Repositories: gentoo vivovl mysql ACCEPT_KEYWORDS=amd64 ACCEPT_LICENSE=* CBUILD=x86_64-pc-linux-gnu CFLAGS=-O2 -march=corei7-avx -pipe -frecord-gcc-switches -mno-movbe -mno-abm -mno-lwp -mno-fma -mno-fma4 -mno-xop -mno-bmi -mno-tbm --param l1-cache-size=32 --param l1-cache-line-size=64 --param l2-cache-size=8192 -mtune=corei7-avx -fgcse-after-reload -fpredictive-commoning -ftree-vectorize -funswitch-loops -fgraphite-identity -floop-block -floop-interchange -floop-strip-mine -ggdb -gdwarf-4 -fvar-tracking-assignments CHOST=x86_64-pc-linux-gnu CONFIG_PROTECT=/etc /usr/share/config /usr/share/gnupg/qualified.txt /usr/share/openvpn/easy-rsa /usr/share/themes/oxygen-gtk/gtk-2.0 CONFIG_PROTECT_MASK=/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/php/apache2-php5.3/ext-active/ /etc/php/cgi-php5.3/ext-active/ /etc/php/cli-php5.3/ext-active/ /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c CXXFLAGS=-O2 -march=corei7-avx -pipe -frecord-gcc-switches -mno-movbe -mno-abm -mno-lwp -mno-fma -mno-fma4 -mno-xop -mno-bmi -mno-tbm --param l1-cache-size=32 --param l1-cache-line-size=64 --param l2-cache-size=8192 -mtune=corei7-avx -fgcse-after-reload -fpredictive-commoning -ftree-vectorize -funswitch-loops -fgraphite-identity -floop-block -floop-interchange -floop-strip-mine -ggdb -gdwarf-4 -fvar-tracking-assignments -fvisibility-inlines-hidden DISTDIR=/g/distfiles EMERGE_DEFAULT_OPTS=--ask-enter-invalid --quiet-build=y FCFLAGS=-O2 -pipe FEATURES=assume-digests binpkg-logs buildpkg compress-build-logs compressdebug config-protect-if-modified distcc distlocks ebuild-locks fail-clean fixlafiles installsources metadata-transfer news noinfo notitles parallel-fetch parallel-install parse-eapi-ebuild-head sandbox sfperms splitdebug strict test-fail-continue unknown-features-warn unmerge-logs unmerge-orphans xattr FFLAGS=-O2 -pipe GENTOO_MIRRORS=http://mirror.netcologne.de/gentoo/ http://mirror.ovh.net/gentoo-distfiles/ http://mirror.switch.ch/ftp/mirror/gentoo/ http://gentoo.lagis.at/ http://mirror.qubenet.net/mirror/gentoo/; INSTALL_MASK=/usr/lib64/libogrove.la /usr/lib64/libospgrove.la /usr/lib64/libostyle.la /usr/lib64/vlc/plugins/codec/libdirac_plugin.la /usr/lib64/vlc/plugins/demux/libdirac_plugin.la /bin/systemd /bin/systemctl /usr/lib64/elektra/libelektra-filesys.la /usr/lib64/elektra/libelektra-hosts.la /usr/lib64/elektra/libelektra-ini.la /usr/lib64/elektra/libelektra-passwd.la /usr/lib64/libelektra-cpp.la /usr/lib64/libelektra.la /usr/lib64/libelektratools.la LDFLAGS=-Wl,-O1 -Wl,--as-needed -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -Wl,--sort-common -Wl,--no-copy-dt-needed-entries -Wl,--build-id LINGUAS=it MAKEOPTS=-j36 PKGDIR=/g/packages PORTAGE_COMPRESS=lzma PORTAGE_CONFIGROOT=/ PORTAGE_RSYNC_OPTS=--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages PORTAGE_TMPDIR=/var/tmp PORTDIR=/g/portage PORTDIR_OVERLAY=/g/ovl/tmp /g/ovl/mysql SYNC=rsync://rsync.gentoo.org/gentoo-portage USE=acl amd64 avx berkdb bzip2 caps cli cracklib crypt cups cxx dbus dri fortran gdbm gpm iconv ipv6 modules mudflap multilib ncurses nls
[gentoo-dev] Lastrite: x11-misc/transset-df (replaced by x11-apps/transset)
# Samuli Suominen ssuomi...@gentoo.org (25 Jun 2012) # Replaced by the new 1.0.0 release of x11-apps/transset. # Removal in 30 days. x11-misc/transset-df
Re: [gentoo-dev] grub:2 keywords
On Sun, Jun 24, 2012 at 11:15 PM, Mike Gilbert flop...@gentoo.org wrote: An official release of grub-2.00 should be coming pretty soon. I would like to keyword this for ~amd64 and ~x86 shortly after it hits the tree. I don't do much work on base system packages, so I would like some advice on how to make this as smooth as possible. My main concern is that many people probably have sys-boot/grub in @world. If grub:2 is made visible, portage will install it, and will remove grub-0.97 on the next depclean. This could be a little confusing, but should not cause any immediate damage since the copy of grub-0.97 installed in the MBR and /boot would remain intact. Is this worthy of a news item? Or I just blog about it? Anything else I need to think about here? Note: The Gentoo Documentation Project has indicated that they do not want to add anything to the handbook until we are somewhat close to stabilizing grub:2. That's at least a couple months away. Mike, Since Grub Legacy and Grub 2 are slotted, Portage won't remove the older version. Even if it removes the older one, everything necessary is installed into /boot and the MBR already. The best route forward would be to instruct people to use grub2-install (but whatever the flag is to prevent MBR installation). Have people generate their grub.cfg with grub2-mkconfig and then put a chain loader into the Grub Legacy configs so that they can test Grub 2 and then once they test it tell them to install Grub 2 into the MBR and remove Grub Legacy. I'll gladly work with you on this. IMHO, it might be a good plan to unmask and ~arch one of the release candidates with an aim to get Grub 2.0.0 fully released with docs. -- Doug Goldstein
Re: [gentoo-dev] grub:2 keywords
On Mon, Jun 25, 2012 at 11:19 AM, Doug Goldstein car...@gentoo.org wrote: Since Grub Legacy and Grub 2 are slotted, Portage won't remove the older version. Even if it removes the older one, everything necessary is installed into /boot and the MBR already. Portage will remove the older slot the next time the user runs emerge --depclean unless sys-boot/grub:0 is added to the world file. I'm looking for a good way to communicate this to the user. How about this: For ~arch, we do an ewarn in pkg_postinst if grub:0 is installed. For stable, we do a news item. The best route forward would be to instruct people to use grub2-install (but whatever the flag is to prevent MBR installation). Have people generate their grub.cfg with grub2-mkconfig and then put a chain loader into the Grub Legacy configs so that they can test Grub 2 and then once they test it tell them to install Grub 2 into the MBR and remove Grub Legacy. Yeah, I vaguely remember trying this when I first installed grub:2. You can prevent the MBR installation by stubbing out the grub-setup call. For example: grub2-install --grub-setup=/bin/true /dev/sda You would then load /boot/grub2/i386-pc/core.img just like a Linux kernel from menu.lst. If you (or anyone) wants to test and verify that this actually works, that would be great. I'll gladly work with you on this. IMHO, it might be a good plan to unmask and ~arch one of the release candidates with an aim to get Grub 2.0.0 fully released with docs. That sounds like a good idea.
Re: [gentoo-dev] grub:2 keywords
On Mon, 25 Jun 2012 00:15:59 -0400 Mike Gilbert flop...@gentoo.org wrote: An official release of grub-2.00 should be coming pretty soon. I would like to keyword this for ~amd64 and ~x86 shortly after it hits the tree. I don't do much work on base system packages, so I would like some advice on how to make this as smooth as possible. My main concern is that many people probably have sys-boot/grub in @world. If grub:2 is made visible, portage will install it, and will remove grub-0.97 on the next depclean. This could be a little confusing, but should not cause any immediate damage since the copy of grub-0.97 installed in the MBR and /boot would remain intact. Is this worthy of a news item? Or I just blog about it? Anything else I need to think about here? Note: The Gentoo Documentation Project has indicated that they do not want to add anything to the handbook until we are somewhat close to stabilizing grub:2. That's at least a couple months away. I guess you could prepare some docs already, and put them e.g. on the Wiki. Then it would be a really good idea to release a news item and point users to those information and inform them about possible choices. -- Best regards, Michał Górny signature.asc Description: PGP signature
Re: [gentoo-dev] grub:2 keywords
On Mon, Jun 25, 2012 at 1:02 PM, Michał Górny mgo...@gentoo.org wrote: On Mon, 25 Jun 2012 00:15:59 -0400 Mike Gilbert flop...@gentoo.org wrote: An official release of grub-2.00 should be coming pretty soon. I would like to keyword this for ~amd64 and ~x86 shortly after it hits the tree. I don't do much work on base system packages, so I would like some advice on how to make this as smooth as possible. My main concern is that many people probably have sys-boot/grub in @world. If grub:2 is made visible, portage will install it, and will remove grub-0.97 on the next depclean. This could be a little confusing, but should not cause any immediate damage since the copy of grub-0.97 installed in the MBR and /boot would remain intact. Is this worthy of a news item? Or I just blog about it? Anything else I need to think about here? Note: The Gentoo Documentation Project has indicated that they do not want to add anything to the handbook until we are somewhat close to stabilizing grub:2. That's at least a couple months away. I guess you could prepare some docs already, and put them e.g. on the Wiki. Then it would be a really good idea to release a news item and point users to those information and inform them about possible choices. There is already an elog message referring users to the wiki: http://wiki.gentoo.org/wiki/GRUB2_Quick_Start
Re: [gentoo-dev] About forcing rebuilds of other packages issue
On 06/25/2012 06:03 AM, Ian Stakenvicius wrote: On 23/06/12 08:42 PM, Zac Medico wrote: On 06/10/2012 11:18 AM, Zac Medico wrote: On 06/10/2012 05:25 AM, Ciaran McCreesh wrote: On Sat, 09 Jun 2012 13:55:53 -0700 Zac Medico zmed...@gentoo.org wrote: A dependency atom will have optional SLOT and ABI_SLOT parts. Using the dbus-glib depedency on glib:2 as an example [1], the dbus-glib dependency will be expressed with an atom such as dev-libs/glib:2:= and the package manager will translate that atom to dev-libs/glib:2:=2.32 at build time. So, ':' is always used to distinguish SLOT deps, and ':=' is always used to distinguish ABI_SLOT deps. Is that syntax good? Here's a nicer syntax: no ABI_SLOT variable, and SLOT=2/2.32. Then you can do explicit :2/2.32 dependencies if you like, or :2 (which would match SLOT=2 or SLOT=2/anything), or :2= (which gets rewritten to :2/2.32=) or :2*. If an ebuild does SLOT=2, it's treated as 2/2. Yes, I prefer your syntax. In portage-2.1.11.1 and 2.2.0_alpha112 I’ve added support for EAPI “4-slot-abi”: http://blogs.gentoo.org/zmedico/2012/06/23/automatic-rebuilds-with-experimental-eapi-4-slot-abi/ Does anyone have a fork of the tree that's being converted to test this new functionality? If so I'd like to sign up. That would be nice to have, but I haven't heard of anyone doing it yet. -- Thanks, Zac
[gentoo-dev] Re: grub:2 keywords
Mike Gilbert posted on Mon, 25 Jun 2012 12:56:25 -0400 as excerpted: On Mon, Jun 25, 2012 at 11:19 AM, Doug Goldstein car...@gentoo.org wrote: Since Grub Legacy and Grub 2 are slotted, Portage won't remove the older version. Even if it removes the older one, everything necessary is installed into /boot and the MBR already. Portage will remove the older slot the next time the user runs emerge --depclean unless sys-boot/grub:0 is added to the world file. I'm looking for a good way to communicate this to the user. How about this: For ~arch, we do an ewarn in pkg_postinst if grub:0 is installed. For stable, we do a news item. Here's a bit of a different idea: Changing the bootloader is really a profile level change. If appropriate grub2-defaulted new profiles are created, and the old ones set to specify grub:0 as their default bootloader and then deprecated, this will automatically both provide the appropriate upgrade preparation required hint, and allow users to upgrade on their own schedule during the usual profile deprecation period. Additionally, if there are continued issues with gcc building the old grub, etc (as was complicating the gcc-4.6 upgrade), the old profile can be set to mask new gcc, as well, thus providing additional encouragement to upgrade for the new gcc, and allowing people to deal with that upgrade at the same time, with their profile switch. As such, supporting the old profiles during the deprecation period shouldn't be too bad, since slots, version-ranges, etc, can be nailed down as necessary, and people will automatically be prepared to deal with a bit of churn as they do their profile upgrade. Thinking back, that probably would have been the best way to handle the baselayout-2/openrc upgrade as well, but that's rather behind us, now. -- Duncan - List replies preferred. No HTML msgs. Every nonfree program has a lord, a master -- and if you use the program, he is your master. Richard Stallman
Re: [gentoo-dev] Re: grub:2 keywords
On Mon, Jun 25, 2012 at 10:43 PM, Duncan 1i5t5.dun...@cox.net wrote: Mike Gilbert posted on Mon, 25 Jun 2012 12:56:25 -0400 as excerpted: On Mon, Jun 25, 2012 at 11:19 AM, Doug Goldstein car...@gentoo.org wrote: Since Grub Legacy and Grub 2 are slotted, Portage won't remove the older version. Even if it removes the older one, everything necessary is installed into /boot and the MBR already. Portage will remove the older slot the next time the user runs emerge --depclean unless sys-boot/grub:0 is added to the world file. I'm looking for a good way to communicate this to the user. How about this: For ~arch, we do an ewarn in pkg_postinst if grub:0 is installed. For stable, we do a news item. Here's a bit of a different idea: Changing the bootloader is really a profile level change. If appropriate grub2-defaulted new profiles are created, and the old ones set to specify grub:0 as their default bootloader and then deprecated, this will automatically both provide the appropriate upgrade preparation required hint, and allow users to upgrade on their own schedule during the usual profile deprecation period. Profiles do not set a default bootloader so I have no idea what you are talking about. Installing grub:2 does not replace grub:0 until the user actually runs grub2-install, so you can already upgrade on your own schedule.
[gentoo-dev] New herd: app-doc
I'm not sure if you're supposed to announce these things or not, so here goes. The app-doc herd will maintain packages in app-doc/ that don't otherwise have a maintainer. Most of this stuff is either static or updated infrequently by script, but if you're interested feel free to join. Because the majority of these packages consist of simple text and examples installed to /usr/share/doc I'd like to continue the practise of handling keywording/stabilization ourselves. Thanks. -- fonts, gcc-porting toolchain, wxwidgets @ gentoo.org signature.asc Description: PGP signature
Re: [gentoo-dev] Re: grub:2 keywords
On Tue, 26 Jun 2012 02:43:47 + (UTC) Duncan 1i5t5.dun...@cox.net wrote: Mike Gilbert posted on Mon, 25 Jun 2012 12:56:25 -0400 as excerpted: On Mon, Jun 25, 2012 at 11:19 AM, Doug Goldstein car...@gentoo.org wrote: Since Grub Legacy and Grub 2 are slotted, Portage won't remove the older version. Even if it removes the older one, everything necessary is installed into /boot and the MBR already. Portage will remove the older slot the next time the user runs emerge --depclean unless sys-boot/grub:0 is added to the world file. I'm looking for a good way to communicate this to the user. How about this: For ~arch, we do an ewarn in pkg_postinst if grub:0 is installed. For stable, we do a news item. Here's a bit of a different idea: Changing the bootloader is really a profile level change. If appropriate grub2-defaulted new profiles are created, and the old ones set to specify grub:0 as their default bootloader and then deprecated, this will automatically both provide the appropriate upgrade preparation required hint, and allow users to upgrade on their own schedule during the usual profile deprecation period. No-no-no. I don't want profiles suddenly installing grub on my system. -- Best regards, Michał Górny signature.asc Description: PGP signature
[gentoo-dev] Re: grub:2 keywords
Mike Gilbert posted on Mon, 25 Jun 2012 23:13:09 -0400 as excerpted: Profiles do not set a default bootloader so I have no idea what you are talking about. I could have sworn there was a virtual/bootloader or some such, that was a part of @system and that thus would have likely had a default in the profiles packages file, but either there was but it's long gone, or I'm mis-remembering entirely. So, ummm... interesting idea, but never mind! -- Duncan - List replies preferred. No HTML msgs. Every nonfree program has a lord, a master -- and if you use the program, he is your master. Richard Stallman
[gentoo-dev] Re: -Werror unwanted?
On Mon, 14 May 2012 19:58:13 +0100 Markos Chandras hwoar...@gentoo.org wrote: On 05/14/2012 06:03 PM, hasufell wrote: So, I will file a documentation bug unless someone can point me in the right direction. I didn't find a reference to that issue. Open a bug, write a devmanual patch and I will be happy to apply it FWIW I started a compiler flag policy / best-practice guide a while back. One of these years I'll get around to actually writing it. :p -- fonts, gcc-porting toolchain, wxwidgets @ gentoo.org signature.asc Description: PGP signature
[gentoo-dev] Re: -Werror unwanted?
Ryan Hill posted on Mon, 25 Jun 2012 22:57:30 -0600 as excerpted: On Mon, 14 May 2012 19:58:13 +0100 Markos Chandras hwoar...@gentoo.org wrote: On 05/14/2012 06:03 PM, hasufell wrote: So, I will file a documentation bug unless someone can point me in the right direction. I didn't find a reference to that issue. Open a bug, write a devmanual patch and I will be happy to apply it FWIW I started a compiler flag policy / best-practice guide a while back. One of these years I'll get around to actually writing it. :p FWIW, flameeyes' blog has a lot of this sort of content, and with his autotools mythbuster and similar content as well, I gather there's at least some upstream eyes following it. So that's a bit of a start for anyone looking for such information right now, as well as reasonable research for anyone else considering writing such a guide who might want some other references or quote-worthy material. I believe he has specifically covered -Werror too. I know he mentioned it (with a link to /something/, of his or not I didn't check) in a recent entry. -- Duncan - List replies preferred. No HTML msgs. Every nonfree program has a lord, a master -- and if you use the program, he is your master. Richard Stallman
[gentoo-dev] Last rites: dev-ruby/Ruby-MemCache
# Hans de Graaff gra...@gentoo.org (26 Jun 2012) # Dead upstream. QA problems in ebuild. Still uses old # ruby.eclass. Use dev-ruby/memcache-client instead. # Masked for removal in 30 days. dev-ruby/Ruby-MemCache signature.asc Description: This is a digitally signed message part
