From: "R. W. Rodolico" <rodo@dailydata.net>
To: development@lists.ipfire.org
Subject: Re: Failure attempting to enter 2.15 branch
Date: Tue, 01 Apr 2014 14:56:06 -0500 [thread overview]
Message-ID: <533B19D6.8030601@dailydata.net> (raw)
In-Reply-To: <40e4a075ba90187fc1d9d4cdb9dc6657@mail01.ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1882 bytes --]
Following is transcript. If I need to do a full install, I will, but it
will take a little while.
Rod
[root(a)dd-router ~]# cat /opt/pakfire/db/core/mine
75
[root(a)dd-router ~]# cat /opt/pakfire/etc/pakfire.conf
...
package Conf;
$version = "2.13.1";
#$version = "2.13";
$mainserver = "pakfire.ipfire.org";
...
[root(a)dd-router ~]# pakfire update --force
server-list.db 100.00% |=============================>| 312.00 B
packages_list.db 100.00% |=============================>| 3.31 KB
core-list.db 100.00% |=============================>| 248.00 B
[root(a)dd-router ~]# pakfire upgrade
CORE ERROR: No new upgrades available. You are on release 75.
On 04/01/2014 02:28 PM, Arne Fitzenreiter wrote:
> On 2014-04-01 20:33, R. W. Rodolico wrote:
>> Hi all,
>>
>> Sorry I've been out of pocket with some serious family issues and
>> haven't been testing.
>>
>> I tried to do testing by upgrading my office router from 2.13-75
>> following the instructions at
>> http://wiki.ipfire.org/en/configuration/ipfire/pakfire/testing. However,
>> this produced no changes.
>>
>> The instructions say to change the line in pakfire.conf to
>> $version = "2.13.1";
>> which I did, then did
>> pakfire update --force
>> Nothing happened.
> Nothing is not good. It should download the package lists as usual.
>
> After this
> pakfire upgrade
> should to install. (Or go to the webif page that should show the update
> now.)
>
>>
>> Question? Should that be 2.15.1?
> No. 2.15 is the testing tree at the moment. The 2.15.1 will added soon
> but not exist yet.
>
> Greetings,
> Arne
>
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
--
R. W. "Rod" Rodolico
Daily Data, Inc.
POB 140465
Dallas TX 75214-0465
http://www.dailydata.net
214.827.2170
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: rodo.vcf --]
[-- Type: text/x-vcard, Size: 233 bytes --]
begin:vcard
fn:R. W. Rodolico
n:Rodolico;R. W.
org:Daily Data, Inc.
adr:;;POB 140465;Dallas;TX;75214-0465;US
email;internet:rodo@dailydata.net
title:President
tel;work:214.827.2170
url:http://www.dailydata.net
version:2.1
end:vcard
next prev parent reply other threads:[~2014-04-01 19:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 18:33 R. W. Rodolico
2014-04-01 19:28 ` Arne Fitzenreiter
2014-04-01 19:56 ` R. W. Rodolico [this message]
2014-04-01 20:12 ` AW: " Benjamin Hahn
2014-04-01 20:25 ` R. W. Rodolico
2014-04-08 16:17 ` Great update! m.postman
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=533B19D6.8030601@dailydata.net \
--to=rodo@dailydata.net \
--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