From: Tonton <tonton@riseup.net>
To: cdelia@dc.uba.ar
Cc: help-guix@gnu.org
Subject: Re: rolling back only a single package
Date: Fri, 28 Dec 2018 12:35:47 +0100 [thread overview]
Message-ID: <20181228123547.05bd8f6d@merlin.browniehive.net> (raw)
In-Reply-To: <09ccab6e031dddc448863c812f400e0a@dc.uba.ar>
Hello, and welcome :)
For packages where multiple versions are defined you can choose with
packagename@version e.g. guile@1.8.8 for the oldest guile on my system. A
simple way to see the versions is with the 'guix package --show=packagename'
flag. e.g. 'guix package --show=guile' will give you an entry per guile
version available.
It seems you are looking for a version of a package where the previous
definition was not kept on upgrade. Most likely because guix so far has not
kept old versions of leaf packages (i.e. packages with no dependencies);
which is why guile and python have several versions but xmobar has none.
I think the choice to not keep old definitions is to ease maintenance. But
this might be a valid discussion to have as we move towards 1.0. Maybe we
should have a policy of keeping one old version when we upgrade, as a kind of
fallback.
It occurs to me that maybe this is not a problem because of functional/purity
aspect of guix, and the package just needs a better definition? idk.
As a quick fix for xmobar I see it was updated to 0.28 in commit
ccd4fd3f2a614996bff5436cc22e4715a7eb1f31 and only two lines were changed. I
would create a file ~/my-guix-pakcages/my-xmobar.scm and put the following in
it:
-------------------------------------------------------------------------------------------------
(define-module (my-xmobar) ;; The name "my-xmobar" have to be
;; the same as the filename
#:use-module (guix packages)
#:use-module (guix download)
#:use-module (gnu packages)
#:use-module (gnu packages wm))
(define-public my-xmobar
(package
(inherit xmobar)
(name "xmobar")
(version "0.27")
(source (origin
(method url-fetch)
(uri (string-append "mirror://hackage/package/xmobar/"
name "-" version ".tar.gz"))
(sha256
(base32
"0agx490q6sbmv3vfq33ys8dsrgwizj3bmha4i1pkxz5wp5q8cx3l"))))))
-------------------------------------------------------------------------------------------------
Then add the file to your shells $GUIX_PACKAGE_PATH like
'export GUIX_PACKAGE_PATH=~/my-guix-pakcages/:$GUIX_PACKAGE_PATH'
in your .profile or similar. Open a new shell and run:
guix package -i xmobar@0.27
Hope that helps. :)
Tonton
On Thu, 27 Dec 2018 16:52:23 -0300
cdelia@dc.uba.ar wrote:
> Hi,
>
> I upgraded guix a couple of days ago, installed some things and now I
> found that xmobar just keeps segfaulting.
>
> Switching to specific generation it's really cool, but in this case
> would "uninstall" all the software that it's between the
> update-generation and the current one.
>
> So, there is any way to just downgrade a single package (resolving it
> dependencies) with out doing a full switch?
>
> I guess this it's connected to
> https://lists.gnu.org/archive/html/help-guix/2016-08/msg00028.html
>
> And I could also switch and then manually re install. But maybe there is
> a standard or automatic way to do it.
>
> Thanks!
>
next prev parent reply other threads:[~2018-12-28 11:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-27 19:52 rolling back only a single package cdelia
2018-12-28 7:55 ` Pierre Neidhardt
[not found] ` <7bbd5b5a38121bf9a70c1fbe095c39b8@dc.uba.ar>
2018-12-28 22:19 ` cdelia
2018-12-28 11:35 ` Tonton [this message]
2018-12-30 22:57 ` cdelia
2018-12-31 15:17 ` Tonton
2018-12-28 13:34 ` Björn Höfling
2018-12-28 14:49 ` Ricardo Wurmus
2018-12-31 7:11 ` cdelia
2018-12-31 8:23 ` Ricardo Wurmus
2018-12-30 23:37 ` cdelia
2018-12-31 0:59 ` cdelia
[not found] ` <45406B3B-5E5F-4444-9679-A5DB43D9AE50@pretty.Easy.privacy>
2018-12-28 22:15 ` cdelia
2018-12-29 18:35 ` swedebugia
2018-12-30 22:40 ` Catriel Omar D'Elía
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181228123547.05bd8f6d@merlin.browniehive.net \
--to=tonton@riseup.net \
--cc=cdelia@dc.uba.ar \
--cc=help-guix@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).