From: David Pirotte <david@altosw.be>
To: Federico Beffa <beffa@ieee.org>
Cc: guile-user@gnu.org
Subject: Re: guile-2.0.11 installation on system with 2.0.5
Date: Tue, 16 Sep 2014 15:16:34 -0300 [thread overview]
Message-ID: <20140916151634.361d9a1a@capac> (raw)
In-Reply-To: <CAKrPhPNoM5VkADGcEBvNxPrujLuG+9J7n9KntO5AKnwetQp+zw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2200 bytes --]
Hello,
> ...
> OK, I've found out by using "apt-cache policy package-name": I need to
> lower the default priorities of packages from testing other than guile
> with
>
> Package: *
> Pin: release o=Debian
> Pin-Priority: 10
good to know, tx!
> Now I do not get other packages with "aptitude full-upgrade", but if I
> pull in guile-2.0 from testing it wants to change several other
> libraries:
yes, this is to be expected indeed, as guile-2.0-libs, in testing, depends on
libgc1c2 >= 7.2d, which triggers a series of dependency updates.
i am actually _very_ surprised that this would not be the case when manually
installing guile-2.0.11: I thought configure would not let you install unless ....
note also that guile-2.0-dev is not required, not sure it is the 'full-upgrade'
terribly scary beast that triggered that?
> $ sudo aptitude -t testing full-upgrade guile-2.0
> The following NEW packages will be installed:
> libffi6{a}
> The following packages will be upgraded:
> guile-2.0 guile-2.0-libs libc6 libgc1c2 libgssapi-krb5-2
> libk5crypto3 libkeyutils1
> libkrb5-3 libkrb5support0 libtirpc1 locales nfs-common
> 12 packages upgraded, 1 newly installed, 0 to remove and 1353 not upgraded.
> Need to get 12.1 MB of archives. After unpacking 2,553 kB will be used.
> The following packages have unmet dependencies:
> krb5-user : Depends: libkrb5-3 (= 1.10.1+dfsg-5+deb7u2) but
> 1.12.1+dfsg-9 is to be installed.
> libgc-dev : Depends: libgc1c2 (= 1:7.1-9.1) but 1:7.2d-6.3 is to be installed.
> libc6-i386 : Depends: libc6 (= 2.13-38+deb7u4) but 2.19-11 is to be installed.
> guile-2.0-dev : Depends: guile-2.0 (= 2.0.5+1-3) but 2.0.11+1-1 is to
> be installed.
> libc6-dev : Depends: libc6 (= 2.13-38+deb7u4) but 2.19-11 is to be installed.
> libc-dev-bin : Depends: libc6 (< 2.14) but 2.19-11 is to be installed.
>
> I think I will just install guile 2.0.11 "manually".
It should request you to update libgc1c2 as well, and actually constraints might even
be stronger [when the tarball is >=, in version, to the 1 used by debian pkg
maintainer]?
Hum, mark, ludovic, am I wrong here?
Cheers,
David
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 173 bytes --]
next prev parent reply other threads:[~2014-09-16 18:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 11:09 guile-2.0.11 installation on system with 2.0.5 Federico Beffa
2014-09-16 13:13 ` Federico Beffa
2014-09-16 18:16 ` David Pirotte [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-09-15 16:46 Federico Beffa
2014-09-15 17:33 ` David Pirotte
2014-09-15 11:46 Federico Beffa
2014-09-15 15:00 ` Chris Vine
2014-09-16 16:26 ` Mark H Weaver
2014-09-14 15:42 Federico Beffa
2014-09-14 23:07 ` Chris Vine
2014-09-15 7:50 ` Ludovic Courtès
2014-09-14 15:37 Federico Beffa
2014-09-15 1:16 ` mhw
2014-09-15 9:49 ` Neil Jerram
2014-09-15 10:22 ` Federico Beffa
2014-09-15 10:44 ` Chris Vine
2014-09-15 14:15 ` Mark H Weaver
2014-09-15 10:27 ` Chris Vine
2014-09-14 8:02 Federico Beffa
2014-09-13 12:52 Federico Beffa
2014-09-14 1:17 ` Vernon Oberholzer
2014-09-14 14:32 ` Neil Jerram
2014-09-14 14:33 ` Ludovic Courtès
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140916151634.361d9a1a@capac \
--to=david@altosw.be \
--cc=beffa@ieee.org \
--cc=guile-user@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).