From: Federico Beffa <beffa@ieee.org>
To: david <david@altosw.be>, guile-user@gnu.org
Subject: Re: guile-2.0.11 installation on system with 2.0.5
Date: Tue, 16 Sep 2014 15:13:03 +0200 [thread overview]
Message-ID: <CAKrPhPNoM5VkADGcEBvNxPrujLuG+9J7n9KntO5AKnwetQp+zw@mail.gmail.com> (raw)
In-Reply-To: <CAKrPhPP8DQjBMUyh__--S5BRtoKGCiBz07TD+dreAfMfjv1NRQ@mail.gmail.com>
On Tue, Sep 16, 2014 at 1:09 PM, Federico Beffa <beffa@ieee.org> wrote:
> David Pirotte <david@altosw.be> writes:
>
>> Hello,
>>
>>> As far as I inderstand the Debian package manager mantains a package
>>> database. This is the place where it looks for installed packages. So,
>>> if I have a newer version of guile which is not installed through the
>>> package manager, the package manager will not know about it.
>>
>> even if you are locked in a debian stable, you can, and you should in the case of
>> guile really, install packages from testing, unstable and even experimental [which
>> is not recommended unless you know what you are doing of course].
>>
>> So:
>>
>> update your /etc/apt/sources.list, add a line with testing source
>> update you /etc/preferences
>>
>> Package: *
>> Pin: release a=stable
>> Pin-Priority: 800
>>
>> Package: guile
>> Pin: release a=testing
>> Pin-Priority: 600
>>
>> aptitude update
>> aptitude
>> search for the guile-2.0 package aptitude entry
>> press enter [Menu: Package -> information]
>> select and install the testing version [2.0.11+1-1 as of today]
>>
>> with that setting, aptitude|debian future updates will track and offer you to update
>> the installed guile-2.0 testing package, while keeping everything else on stable...
>> there are doc about that, duckduckgo for it...
>>
>
> You convinced me that I should be fine using guile from testing.
>
> I've added the following lines in sources.list:
>
> deb http://ftp.ch.debian.org/debian/ testing main
> deb-src http://ftp.ch.debian.org/debian/ testing main
>
> created /etc/apt/preferences.d/00-stable containing:
>
> Package: *
> Pin: release a=stable
> Pin-Priority: 800
>
> and created /etc/apt/preferences.d/20-guile containing:
>
> Package: guile
> Pin: release a=testing
> Pin-Priority: 600
>
> Now, before installing guile from testing, I wanted to check if I still
> get no updatable packages as a moment before doing the change:
>
> aptitude update
> aptitude full-upgrade
>
> This tells me that the package libxnvctrl0 can be update. If I remove
> the testing entry from sources.list, then I get no updates. So, something
> is coming in from testing.
>
> Am I doing something wrong?
>
> Regards,
> Fede
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
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:
$ 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".
Thanks for all the help!
Fede
next prev parent reply other threads:[~2014-09-16 13:13 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 [this message]
2014-09-16 18:16 ` David Pirotte
-- 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=CAKrPhPNoM5VkADGcEBvNxPrujLuG+9J7n9KntO5AKnwetQp+zw@mail.gmail.com \
--to=beffa@ieee.org \
--cc=david@altosw.be \
--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).