From: Christian Neukirchen <chneuk...@gmail.com>
To: "Stefan Mühlinghaus" <"master..."@googlemail.com>
Cc: voidlinux <void...@googlegroups.com>, use...@gmail.com
Subject: Re: Enelightenment .29.5_4 causes seg faults
Date: Fri, 24 Jul 2015 15:11:56 +0200 [thread overview]
Message-ID: <87380dn1ib.fsf@gmail.com> (raw)
In-Reply-To: <57b48d4b-d69a-45c4-970c-a0126523ca33@googlegroups.com> ("Stefan \=\?utf-8\?Q\?M\=C3\=BChlinghaus\=22's\?\= message of "Fri, 24 Jul 2015 00:04:12 -0700 (PDT)")
Stefan Mühlinghaus <master...@googlemail.com> writes:
> Please keep in mind that all work on void is done by volunteers, some of
> which are maintaining hundrets and even thousands of packages. In that
> regard it is impossible to extensively test every new version of every
> package, especially if the maintainers are not actively using them
> themselfs. When you encounter a problem like this please report it here
> (like you did) or in the GitHub issue tracker
> <https://github.com/voidlinux/void-packages/issues>.
>
> As for downgrading, the process is a little fiddly. I usually create a
> temporary repository, add the older package from the xbps package cache to
> it and that use that repository to force-downgrade the currenty installed
> package. Something like this:
>
> mkdir /tmp/repo
> cp /var/cache/xbps/<packagefilename>.xbps* /tmp/repo/
> cd /tmp/repo
> xbps-rindex -a <packagefilename>.xbps
> xbps-install --repository=/tmp/repo -f <package>
xbps-install xtools
xdowngrade /var/cache/xbps/$file.xbps
:)
--
Christian Neukirchen <chneuk...@gmail.com> http://chneukirchen.org
prev parent reply other threads:[~2015-07-24 13:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 21:19 Userx Xbw
2015-07-24 7:04 ` Stefan Mühlinghaus
2015-07-24 13:11 ` Christian Neukirchen [this message]
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=87380dn1ib.fsf@gmail.com \
--to="chneuk..."@gmail.com \
--cc="master..."@googlemail.com \
--cc="use..."@gmail.com \
--cc="void..."@googlegroups.com \
/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 NNTP newsgroup(s).