public inbox for gentoo-science@lists.gentoo.org
 help / color / mirror / Atom feed
From: Christopher Schwan <cschwan@students.uni-mainz.de>
To: <gentoo-science@lists.gentoo.org>
Subject: Re: [gentoo-science] [sage-on-gentoo] Sage-4.5.2 build problem and a "run-time" errors.
Date: Wed, 18 Aug 2010 08:31:11 +0200	[thread overview]
Message-ID: <201008180831.11158.cschwan@students.uni-mainz.de> (raw)
In-Reply-To: <20100818083311.f2671421.v_2e@ukr.net>

Hi,

On Wednesday 18 August 2010 07:33:11 v_2e@ukr.net wrote:
> Hello!
> 
> On Wed, 11 Aug 2010 09:46:07 +0200
> 
> Christopher Schwan <cschwan@students.uni-mainz.de> wrote:
> > On Wednesday 11 August 2010 08:18:47 v_2e@ukr.net wrote:
> > > First of all, sage-baselayout-4.5.2 blocks sage-4.5.2, but if I delete
> > > the "DEPEND="!!<sci-mathematics/sage-4.5.2"" line from
> > > /var/lib/layman/sage-on-gentoo/sci-mathematics/sage-baselayout/sage-bas
> > > elay out-4.5.2.ebuild file, I can emerge it.
> > 
> > That blocker means that you should remove sage-4.5.1 (its blocking 4.5.1,
> > not 4.5.2!) first and then perform the upgrade - thats because I have
> > put the .desktop file from sage into sage-baselayout. Without this
> > blocker there would be file collisions.
> 
>   Well, this string in "sage-baselayout-4.5.2.ebuild" continues to
> block sage-4.5.2
> I thought, maybe one of the exclamation marks is unneeded there? I
> tried to delete one of them (getting the string like this instead:
> DEPEND="!<sci-mathematics/sage-4.5.2") and the emerge process went
> fine. And Sage works fine for now also.
>   Hope, I'm not saying nonsense and hope, this helps. :)

Thats _really_ strange, but one exclamation mark should work, too. I have fixed 
that in my recent commit, but still would like to know why it doesnt work with 
two exclamation marks. Can you send me your emerge output which contains the 
blocker message ? Anyway, with 4.5.3 I am going to remove the blockers so we 
do not have to worry about them ;)

Thank you for investigating on this!

> 
> Regards,
> Vladimir
> -----
>  <v_2e@ukr.net>

Cheers,

Christopher



  reply	other threads:[~2010-08-18  6:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-11  6:18 [gentoo-science] [sage-on-gentoo] Sage-4.5.2 build problem and a "run-time" errors v_2e
2010-08-11  7:46 ` Christopher Schwan
2010-08-11 12:55   ` v_2e
2010-08-11 16:03     ` Christopher Schwan
2010-08-11 17:05       ` [gentoo-science] How to unsubscribe Stefanbienert
2010-08-11 18:08       ` [gentoo-science] [sage-on-gentoo] Sage-4.5.2 build problem and a "run-time" errors v_2e
2010-08-12  8:35         ` Christopher Schwan
2010-08-12 19:02           ` v_2e
2010-08-12 20:06             ` [gentoo-science] How to unsubscribe? Stefanbienert
2010-08-12 20:34             ` [gentoo-science] [sage-on-gentoo] Sage-4.5.2 build problem and a "run-time" errors Christopher Schwan
2010-08-18  5:33   ` v_2e
2010-08-18  6:31     ` Christopher Schwan [this message]
2010-08-18 15:42       ` v_2e
2010-08-18 23:11     ` [gentoo-science] Still trying to unsubscribe Stefanbienert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201008180831.11158.cschwan@students.uni-mainz.de \
    --to=cschwan@students.uni-mainz.de \
    --cc=gentoo-science@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox