Hi Andreas,
Le dimanche 20 janvier 2013 à 16:20 +0100, Andreas K. Huettel a écrit :
> So, a thread like "Should we enable useflag Z by default" would then include
> "Please discuss here, vote on ..." with a link to the count page (updated via
> cron every 1h). On login to ..., a message similar t
Hello Christian,
it looks like you accidentally choose the latest stable version 0.34 for
removal instead of the older 0.33 [1].
I assume this happened in error and I revert the commit.
(The 0.33 version downgrade does not build)
This is reported as [2], too.
Bye,
Michael
[1] https://bugs
Am Sonntag, 20. Januar 2013, 18:16:32 schrieb Chí-Thanh Christopher Nguyễn:
> Mike Frysinger schrieb:
> > On Sunday 20 January 2013 10:54:55 Chí-Thanh Christopher Nguyễn wrote:
> >> Yes, I mentioned this in another post already. We can use EAPI=1 IUSE
> >> defaults instead. But this will not change
On Sun, 20 Jan 2013 10:08:27 -0800
""Paweł Hajdan, Jr."" wrote:
> On 1/20/13 1:46 AM, Luca Barbato wrote:
> > On 19/01/13 20:10, "Paweł Hajdan, Jr." wrote:
> >> have a way to more simply exclude code that requires CODEC_ID_OPUS.
> >
> > Exclude in chrome or in libavcodec?
> >
> > The latter is
On Mon, Jan 21, 2013 at 1:25 AM, Robin H. Johnson wrote:
> The attached list notes all of the packages that were added or removed
> from the tree, for the week ending 2013-01-20 23h59 UTC.
How about sending those mails to gentoo-dev-announce only?
Theo
On Sun, 20 Jan 2013 20:11:31 +0100
Michał Górny wrote:
> Hello,
>
> There is a fair interest in multilib and while still early, it would
> be a good moment to decide on how USE flags to use for it.
>
> The current attempts are mostly using USE=multilib which is not really
> expressive and poor.
On Sun, 20 Jan 2013 23:33:39 +0100
Michał Górny wrote:
[...]
> > Do you plan to keep precise depends for packages?
> > like glibc[abi_x32]/gcc[abi_x32] for all libraries requesting x32.
>
> Yes. ${MULTILIB_USEDEP} is for that (it currently evaluates
> to 'multilib?').
In that very precise case
On Thu, Jan 17, 2013 at 9:51 AM, Ian Stakenvicius wrote:
> On 16/01/13 09:55 PM, Rich Freeman wrote:
>> SUBSYSTEM=="tty", DRIVERS=="pl2303", KERNELS=="4-1:1.0",
>> KERNEL=="ttyUSB*", SYMLINK="mythser/rca1"
>>
>> I'm not sure if rules are additive - if these symlinks would show
>> up in addition to
On Mon, Jan 21, 2013 at 2:46 AM, Hans de Graaff wrote:
> Setting the option in the profile tells me: "Here's this option you can
> play with, and we think you might need it. Or not."
>
> Setting the option in the ebuild tells me: "You know, we are nice and
> give you this option, but really you sh
Long story short, PMS, portage, havoc and that stuff.
There's currently one in-tree eclass consumer and I have bumped it
to EAPI=5 (from 4) already.
---
eclass/autotools-multilib.eclass | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/eclass/autotools-multilib.eclass b/eclas
Due to use.force and magic like that, non-EAPI-5 deps would be assumed
to have USE=multilib otherwise.
---
eclass/autotools-multilib.eclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/eclass/autotools-multilib.eclass b/eclass/autotools-multilib.eclass
index b4af121..dbf2ad
On Sun, Jan 20, 2013 at 11:27 PM, Ben de Groot wrote:
> On 21 January 2013 12:16, Peter Stuge wrote:
> > Panagiotis Christopoulos wrote:
> >> I don't build server machines every day, others do and it would be
> >> much appreciated if they could respond here.
> >
> > I build catalyst stage4s. Any
On Mon, 21 Jan 2013 10:27:30 -0300
Alexis Ballier wrote:
> > To be honest, I don't know if there's other way to hide USE flags than
> > using USE_EXPAND_HIDDEN. If we want to use that, we'd have to split
> > the flags per-arch, i.e. have:
> >
> > MULTILIB_AMD64="abi1 abi2 abi3"
> > MULTILIB_
Dne St 16. ledna 2013 17:09:07, Alexis Ballier napsal(a):
> On Wed, 16 Jan 2013 12:40:02 + (UTC)
>
> "Tomas Chvatal (scarabeus)" wrote:
> > scarabeus13/01/16 12:40:02
> >
> > Modified: ChangeLog
> > Added:ffmpeg-9.ebuild
> > Removed: ffmpeg-
Dne So 12. ledna 2013 14:49:52, Paweł Hajdan, Jr. napsal(a):
> Please review attached automatically generated stabilization candidates
> for January.
>
> I don't want to annoy people with automatically filed bugs, and at the
> same time I also received lots of positive feedback about the effort to
On 1/21/2013 02:01, Ralph Sennhauser wrote:
On Mon, 21 Jan 2013 13:27:18 +0800
Ben de Groot wrote:
On 21 January 2013 12:16, Peter Stuge wrote:
Panagiotis Christopoulos wrote:
I don't build server machines every day, others do and it would be
much appreciated if they could respond here.
I
On Mon, Jan 21, 2013 at 12:51 PM, Dustin C. Hatch wrote:
> The package defaults have gotten out of hand, in my opinion. I use
> default/linux/amd64/10.0 on all my machines and my /etc/portage/package.use
> directories have dozens of -flag entries for packages with ridiculous
> defaults, and almost
This can be useful when, for example, doc contents are modified. You can
then rely on using REPLACING_VERSIONS in your ebuild to print messages
when people updates from versions using old docs
Patch to review attached
--- readme.gentoo.eclass 2013-01-20 12:42:30.0 +0100
+++ /usr/portage/e
# Samuli Suominen (22 Jan 2012)
# Remove coldplug, hotplug and hotplug-base in 30 days wrt bug #145809
sys-apps/ezusb2131
sys-apps/hotplug
sys-apps/hotplug-base
sys-apps/coldplug
On Mon, Jan 21, 2013 at 11:51:54AM -0600, Dustin C. Hatch wrote
> The package defaults have gotten out of hand, in my opinion. I use
> default/linux/amd64/10.0 on all my machines and my
> /etc/portage/package.use directories have dozens of -flag entries for
> packages with ridiculous defaults,
On Sat, 19 Jan 2013 00:02:05 +
Ciaran McCreesh wrote:
> On Fri, 18 Jan 2013 23:58:22 +
> "Aaron W. Swenson" wrote:
> > ++ If the base profile is to become our server profile, it should not
> > have graphics related USE flags enabled.
>
> ...but that's not how USE flags work. It doesn't
On Mon, Jan 21, 2013 at 02:28:47PM -0500, Rich Freeman wrote
> On Mon, Jan 21, 2013 at 12:51 PM, Dustin C. Hatch
> wrote:
> > The package defaults have gotten out of hand, in my opinion. I use
> > default/linux/amd64/10.0 on all my machines and my /etc/portage/package.use
> > directories have doz
I'm raising this patch because of the recent spate of bugs with the
latest udev that now fails to boot your system if CONFIG_DEVTMPFS is
not available in your kernel.
Bugs: 408947, 409393, 437320, 453074
CONFIG_CHECK has not been fatal for some years now, because there turned
out to be some
On 01/21/2013 10:38 PM, Robin H. Johnson wrote:
> I'm raising this patch because of the recent spate of bugs with the
> latest udev that now fails to boot your system if CONFIG_DEVTMPFS is
> not available in your kernel.
>
> Bugs: 408947, 409393, 437320, 453074
>
> CONFIG_CHECK has not been fa
On 01/21/2013 07:45 PM, Mike Gilbert wrote:
> My suspicion is that portage's environment save/restore process will
> overwrite any setting I attempt to make on the destination host.
If necessary, you can use /etc/portage/bashrc to override
CONFIG_CHECK_FATAL for binary packages. Something like thi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/21/2013 10:56 PM, Zac Medico wrote:
> On 01/21/2013 07:45 PM, Mike Gilbert wrote:
>> My suspicion is that portage's environment save/restore process will
>> overwrite any setting I attempt to make on the destination host.
>
> If necessary, you c
On 01/21/2013 08:10 PM, Rick "Zero_Chaos" Farina wrote:
> On 01/21/2013 10:56 PM, Zac Medico wrote:
>> On 01/21/2013 07:45 PM, Mike Gilbert wrote:
>>> My suspicion is that portage's environment save/restore process will
>>> overwrite any setting I attempt to make on the destination host.
>
>> If n
On 01/21/2013 10:38 PM, Robin H. Johnson wrote:
> CONFIG_CHECK has not been fatal for some years now, because there turned
> out to be some cases where it cannot detect what the system really has
> [1], or what is returned is wrong [2].
>
> However, while this is has been superb in helping those c
Hans de Graaff posted on Mon, 21 Jan 2013 08:46:59 +0100 as excerpted:
> On Sun, 2013-01-20 at 18:03 +0100, Chí-Thanh Christopher Nguyễn wrote:
>
>> We can either set it in the base profile, then there is no need for
>> IUSE="+dri". Or we can set it in every single ebuild that has the dri
>> flag
22.01.2013 08:23, Mike Gilbert wrote:
> I guess this change is ok, given that I can opt-out fairly easily. Zac's
> workaround for binary packages makes me feel better too.
I am curious, can not this check be added to eclass? Or eclass does not
know about type of merged package?
--
Best regards,
Sergey Popov posted on Tue, 22 Jan 2013 10:22:34 +0400 as excerpted:
> 22.01.2013 08:23, Mike Gilbert wrote:
>> I guess this change is ok, given that I can opt-out fairly easily.
>> Zac's workaround for binary packages makes me feel better too.
>
> I am curious, can not this check be added to ecl
2013/1/21 Pacho Ramos :
> This can be useful when, for example, doc contents are modified. You can
> then rely on using REPLACING_VERSIONS in your ebuild to print messages
> when people updates from versions using old docs
>
> Patch to review attached
>
Would'nt be better to just set some variable
On 22 January 2013 03:28, Rich Freeman wrote:
> On Mon, Jan 21, 2013 at 12:51 PM, Dustin C. Hatch
> wrote:
>> The package defaults have gotten out of hand, in my opinion. I use
>> default/linux/amd64/10.0 on all my machines and my /etc/portage/package.use
>> directories have dozens of -flag entr
On 22 January 2013 10:36, Walter Dnes wrote:
> I think we may have to admit that "one size does not fit all". There
> are just too many individual scenarios. A truly minimal build should be
> sufficient to boot to a text console, and have networking and portage to
> be able to build further up
34 matches
Mail list logo