On Thu, 14 Nov 2013 15:57:40 -0800, Chris Stankevitz wrote:
True or false: The correct way to appease portage's error message below
is to add a bunch of ruby_targets_ruby20 use flags in
/etc/portage/package.use
False. These packages should already have this use flag set by default in
a
2013/11/15 Adam Carter adamcart...@gmail.com
Not an answer to your question, but yesterday ruby got pulled in by an
update to thin-provisioning-tools, which was required by lvm2.
It looks like ruby is only required for the tests of
sys-block/thin-provisioning-tools [1].
The new ebuild
Hi,
I have a local package dev-python/grin with
ESVN_REPO_URI=https://svn.enthought.com/svn/sandbox/grin/trunk/;
Since some time I get
Unpacking source...
* subversion check out start --
* repository: https://svn.enthought.com/svn/sandbox/grin/trunk
Error validating server certificate
On 15/11/13 13:22, Helmut Jarausch wrote:
Hi,
I have a local package dev-python/grin with
ESVN_REPO_URI=https://svn.enthought.com/svn/sandbox/grin/trunk/;
Since some time I get
Unpacking source...
* subversion check out start --
* repository:
On 2013-11-15 5:56 AM, Daniel Pielmeier bil...@gentoo.org wrote:
The new ebuild thin-provisioning-tools-0.2.8-r1 reflects this. So if you
update to this version and don't use FEATURES=test it should not pull
in ruby anymore.
I don't have FEATURES=test and it still wants to pull all the ruby
2013/11/15 Tanstaafl tansta...@libertytrek.org
On 2013-11-15 5:56 AM, Daniel Pielmeier bil...@gentoo.org wrote:
The new ebuild thin-provisioning-tools-0.2.8-r1 reflects this. So if you
update to this version and don't use FEATURES=test it should not pull
in ruby anymore.
I don't have
On Fri, Nov 15, 2013 at 5:33 AM, Tanstaafl tansta...@libertytrek.org wrote:
The new ebuild thin-provisioning-tools-0.2.8-r1 reflects this. So if you
update to this version and don't use FEATURES=test it should not pull
in ruby anymore.
I don't have FEATURES=test and it still wants to pull all
Chris Stankevitz schrieb am 15.11.2013 16:29:
On Fri, Nov 15, 2013 at 5:33 AM, Tanstaafl tansta...@libertytrek.org wrote:
The new ebuild thin-provisioning-tools-0.2.8-r1 reflects this. So if you
update to this version and don't use FEATURES=test it should not pull
in ruby anymore.
I don't
On Thu, Nov 14, 2013 at 11:15 PM, Hans de Graaff gra...@gentoo.org wrote:
False. These packages should already have this use flag set by default in
a vanilla Gentoo setup. Perhaps you masked something related to ruby
already?
Hans,
You are correct.
A year ago I added RUBY_TARGETS=ruby18
On 2013-11-14 3:32 PM, Alan McKinnon alan.mckin...@gmail.com wrote:
On 14/11/2013 18:16, Tanstaafl wrote:
I had changed the password to something simple for testing, and now,
after changing it back to my strong password, it fails with:
invalid SMTP AUTH configuration, trying unauthenticated
On 2013-11-15 5:56 AM, Daniel Pielmeier bil...@gentoo.org wrote:
2013/11/15 Adam Carter adamcart...@gmail.com
mailto:adamcart...@gmail.com
Not an answer to your question, but yesterday ruby got pulled in by
an update to thin-provisioning-tools, which was required by lvm2.
It looks like
On Fri, Nov 15, 2013 at 11:10 AM, Tanstaafl tansta...@libertytrek.org wrote:
Ok, so... is there or is there not a way to prevent ruby from being
installed?
Yes
I've tried adding -ruby and -test to package.mask for
thin-provisioning-tools, and even tried adding them to USE= in make.conf, to
On 2013-11-15 3:01 PM, Chris Stankevitz chrisstankev...@gmail.com wrote:
Follow these steps:
0. undo whatever you did
Already did...
1. emerge --sync
2. echo =sys-block/thin-provisioning-tools-0.2.8-r1 ~amd64
/etc/portage/package.keywords
3. update your system
Or, I could just echo
On 15/11/2013 23:58, Tanstaafl wrote:
On 2013-11-15 3:01 PM, Chris Stankevitz chrisstankev...@gmail.com wrote:
Follow these steps:
0. undo whatever you did
Already did...
1. emerge --sync
2. echo =sys-block/thin-provisioning-tools-0.2.8-r1 ~amd64
/etc/portage/package.keywords
3.
14 matches
Mail list logo
