From: Arne Fitzenreiter <Arne.Fitzenreiter@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: 2.13 development
Date: Thu, 06 Dec 2012 10:20:13 +0000 [thread overview]
Message-ID: <7d346bc122caaf904eafb293b4d13f0a@mail01.ipfire.org> (raw)
In-Reply-To: <CAEeb27CVK3ZkXW8wgVDyGThycce4zg0iJN5g0csYDFivQwyPjg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1531 bytes --]
On Wed, 5 Dec 2012 19:05:54 +0000, Chris Blackburn
<cblackburn36(a)gmail.com> wrote:
> Hi All,
>
> I have looked in what I thought were the usual places for these things
> but Ive not had much luck so far so I thought Id try here!
>
> I am currently trying out the IPFire 2.13 beta, so far I have to say
> its very good! A large improvement on the previous version, especially
> with regard to hardware support. However I have a couple of questions
> about the beta I hope you can help me with.
Hi, you try the testrelease, the beta1 is not released yet. It is
planned to
release it next weeks but i will wait for kernel 3.2.35 and IPFire 2.11
core65
before i can start to build it.
>
> 1) Is there some sort of changelog which lists what has been
> fixed/improved between beta versions? So I know if I have an issue
> whether it has been worked on between versions?
Yes. You can see all changes in the thirteen git branch.
http://git.ipfire.org/?p=ipfire-2.x.git;a=shortlog;h=refs/heads/thirteen
The number behind Development Build: thirteen/xxxxxxx are the first 7
digits of the
sha1 sum of the commit.
>
> 2) Is it possible to "upgrade" between the beta versions in the
> download page or does it require a complete re-install?
The most of the last changes are made on this updater. You can try it
by setting /opt/pakfire/db/core/mine back to 63 and reupdate with
pakfire update --force
pakfire upgrade -y
After this you have to wait until the system ask you for a reboot.
Don't reboot
before this message...
Arne
parent reply other threads:[~2012-12-06 10:20 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAEeb27CVK3ZkXW8wgVDyGThycce4zg0iJN5g0csYDFivQwyPjg@mail.gmail.com>]
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=7d346bc122caaf904eafb293b4d13f0a@mail01.ipfire.org \
--to=arne.fitzenreiter@ipfire.org \
--cc=development@lists.ipfire.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