public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "R. W. Rodolico" <rodo@dailydata.net>
To: development@lists.ipfire.org
Subject: Re: router won't update
Date: Tue, 03 Sep 2013 16:37:21 -0500	[thread overview]
Message-ID: <assp.0958291510.52265691.1010201@dailydata.net> (raw)
In-Reply-To: <52265348.3010301@dailydata.net>

[-- Attachment #1: Type: text/plain, Size: 833 bytes --]

Never mind. I found Arne's post on planet.ipfire.org

echo 71 > /opt/pakfire/db/core/mine
pakfire upgrade

Thanks,

Rod

On 09/03/2013 04:23 PM, R. W. Rodolico wrote:
> Ok, I'm doing something wrong. There was a problem with 72 where a new
> ovpn client came back with a message "Invalid input for remote host/ip."
> I know this was fixed, but since I put my router into the testing tree,
> it did not update when 72 was released. So, now, I'm bit by that bug.
> 
> How do I tell IPFire to reload a version it has (72).
> 
> Thanks,
> 
> Rod
> 
> 
> 
> _______________________________________________
> 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


       reply	other threads:[~2013-09-03 21:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <52265348.3010301@dailydata.net>
2013-09-03 21:37 ` R. W. Rodolico [this message]
2013-09-03 21:23 R. W. Rodolico

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=assp.0958291510.52265691.1010201@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