From: Mauro Faccenda <faccenda@gmx.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] libgsf weirdness...
Date: Mon, 18 Jul 2005 12:34:27 -0300 [thread overview]
Message-ID: <42DBCC03.2010703@gmx.net> (raw)
In-Reply-To: <200507180914.10940.dmitry@athabascau.ca>
Dmitry S. Makovey wrote:
> For past couple of weeks as I was doing emerge --sync and emerge -uDNp
> I've noticed that libgsf has "jumping" versions. That is one week
> it's 1.12.0 another 1.10.0 and it swings from one to another. Does
> anybody know what might trigger this behavior?
>
This is because gnumeric REQUIRES =1.10.0... and when you do a -uD it
will be upgraded.
You should keep using -uNp instead of -uDNp ;)
[]'s
Mauro
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-18 15:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-18 15:14 [gentoo-user] libgsf weirdness Dmitry S. Makovey
2005-07-18 15:34 ` Mauro Faccenda [this message]
2005-07-18 16:37 ` Dmitry S. Makovey
2005-07-18 17:23 ` Tero Grundström
2005-07-18 19:37 ` Dmitry S. Makovey
2005-07-18 15:40 ` Rumen Yotov
2005-07-18 18:21 ` Zac Medico
2005-07-18 19:37 ` Tero Grundström
2005-07-18 19:57 ` Zac Medico
2005-07-18 19:39 ` Dmitry S. Makovey
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=42DBCC03.2010703@gmx.net \
--to=faccenda@gmx.net \
--cc=gentoo-user@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