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: Core 101
Date: Mon, 02 May 2016 18:33:49 -0500	[thread overview]
Message-ID: <5727E3DD.4070002@dailydata.net> (raw)
In-Reply-To: <1462222524.18591.10.camel@ipfire.org>

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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sorry, just saw that 101 was released. I thought I was going into
testing. After I got your reply, I saw our mirror was still syncing so
I realized what was going on.

Sorry I didn't test this one; been out of town.

Rod

On 05/02/2016 03:55 PM, Michael Tremer wrote:
> Hi,
> 
> this behavior is kind of normal since the mirrors are still 
> synchronizing.
> 
> Just keep running these commands until you find one that is up to 
> date.
> 
> Best, -Michael
> 
> On Mon, 2016-05-02 at 15:52 -0500, R. W. Rodolico wrote:
>> I just got back and saw there was a beta for Core 101. However, 
>> when I went to install it, it said there was no upgrade. I'm 
>> assuming I'm doing something wrong.
>> 
>> Note, it found that upgrades for samba and htop were available, 
>> but then complained it could not find samba. However, it did 
>> install it! Weird.
>> 
>> Anyway, do I need to set $version to 2.19-1 or something? 
>> pakfire.conf has $version = "2.19";
>> 
>> Rod
>> 
>> [root(a)xxxx pakfire]# pakfire update --force server-list.db 
>> 100.00% |=============================>|    1.15 KB 
>> packages_list.db     100.00% |=============================>| 
>> 3.17 KB meta-samba           100.00% 
>> |=============================>|   340.00 B meta-htop 100.00%
>> |=============================>|   322.00 B core-list.db 100.00%
>> |=============================>|   249.00 B [root(a)xxxx pakfire]#
>> pakfire upgrade CORE ERROR: No new upgrades available. You are on
>> release 100. Update: samba Version: 3.6.25 -> 3.6.25 Release: 60
>> -> 62
>> 
>> Update: htop Version: 1.0.3 -> 2.0.1 Release: 7 -> 8
>> 
>> PAKFIRE RESV: samba: Resolving dependencies... PAKFIRE RESV: 
>> samba: Dependency is already installed: cups PAKFIRE RESV:
>> samba: Dependency is already installed: krb5
>> 
>> PAKFIRE RESV: htop: Resolving dependencies...
>> 
>> 
>> PAKFIRE UPGR: We are going to install all packages listed above.
>>  PAKFIRE INFO: Is this okay? [y/N] y
>> 
>> 
>> 
>> 
>> 
>> DOWNLOAD ERROR: There was no chance to get the file 
>> "paks/samba-3.6.25-62.ipfire" from any available server. May be 
>> you should run "pakfire update" to get some new servers. PAKFIRE 
>> UPGR: samba: Decrypting...
>> 
>> 
>> 
>> samba-3.6.25-62.i... 100.00% |=============================>| 
>> 21.43 MB PAKFIRE UPGR: samba: Upgrading files and running 
>> post-upgrading scripts... PAKFIRE UPGR: samba: Finished.
>> 
>> PAKFIRE UPGR: htop: Decrypting... PAKFIRE UPGR: htop: Upgrading 
>> files and running post-upgrading scripts... PAKFIRE UPGR: htop: 
>> Finished.
>> 
>> 
>> DOWNLOAD ERROR: There was no chance to get the file 
>> "paks/samba-3.6.25-62.ipfire" from any available server. May be 
>> you should run "pakfire update" to get some new servers. PAKFIRE 
>> UPGR: samba: Decrypting...

- -- 
Rod Rodolico
Daily Data, Inc.
POB 140465
Dallas TX 75214-0465
214.827.2170
http://www.dailydata.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlcn490ACgkQuVY3UpYMlTSH0ACfbtbSQKMZIc8p/Kohx6w/wBNX
2dIAmwdAf60tVCIprxw+Hj6GQCPL+R4T
=viV7
-----END PGP SIGNATURE-----

  reply	other threads:[~2016-05-02 23:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-02 20:52 R. W. Rodolico
2016-05-02 20:55 ` Michael Tremer
2016-05-02 23:33   ` R. W. Rodolico [this message]
2016-05-03 10:31     ` Michael Tremer

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=5727E3DD.4070002@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