From: Thomas Ebert <th.ebert@gmx.de>
To: development@lists.ipfire.org
Subject: Re: IPFire 3.x packfire
Date: Wed, 27 Feb 2013 17:13:30 +0100 [thread overview]
Message-ID: <512E30AA.7040608@gmx.de> (raw)
In-Reply-To: <1361981120.28061.384.camel@rice-oxley.tremer.info>
[-- Attachment #1: Type: text/plain, Size: 2142 bytes --]
FYI.
All is working now.
Thanks
Am 27.02.2013 17:05, schrieb Michael Tremer:
> You'll have to disable signature checking in /etc/pakfire/general.conf.
>
> On Wed, 2013-02-27 at 17:04 +0100, Thomas Ebert wrote:
>> Must i wait a little bit more? Because i got a signature error
>>
>> [root(a)ipfire ~]# pakfire install "pakfire=0.9.24-1.ip3"
>> stable: package database | 2.0 MB 00:00 ...
>> Loading installed packages Time: 00:00:17
>>
>> ================================================================================
>> Package Arch Version Repository Size
>> ================================================================================
>> Updating:
>> pakfire i686 0.9.24-1.ip3 stable 20
>> pakfire-common i686 0.9.24-1.ip3 stable 310
>>
>> Transaction Summary
>> ================================================================================
>> Updating: 2 packages
>> Total download size: 330
>> Installed size: 2k
>>
>> Is this okay? [y/N] y
>>
>> Downloading packages:
>> (1/2): pakfire-0.9.24-1.ip3.i686.pfm | 40 kB 00:00 ...
>> (2/2): pakfire-common-0.9.24-1.ip3.i686.pfm | 620 kB 00:00 ...
>> -------------------------------------------------------------------------------------------------------------------------------------------------------------
>> 850 B/s | 330 B 00:00
>>
>> Verifying signatures... Time: 00:00:00
>>
>> An error has occured when running Pakfire.
>>
>> Error message:
>> SignatureError: An unhandled error occured.
>>
>> Further description:
>> pakfire-common-0.9.23-4.ip3.i686 has got no signatures
>> pakfire-0.9.23-4.ip3.i686 has got no signatures
>>
>>
>> _______________________________________________
>> Development mailing list
>> Development(a)lists.ipfire.org
>> http://lists.ipfire.org/mailman/listinfo/development
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
>
next prev parent reply other threads:[~2013-02-27 16:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 22:53 Thomas Ebert
2013-02-27 15:14 ` Michael Tremer
2013-02-27 15:22 ` Thomas Ebert
2013-02-27 15:32 ` Michael Tremer
2013-02-27 15:37 ` Thomas Ebert
2013-02-27 15:52 ` Michael Tremer
2013-02-27 16:04 ` Thomas Ebert
2013-02-27 16:05 ` Michael Tremer
2013-02-27 16:13 ` Thomas Ebert [this message]
[not found] <512FDB9A.1060009@gmx.de>
2013-03-01 12:06 ` Michael Tremer
2013-03-01 12:43 ` Thomas Ebert
2013-03-07 17:38 ` Thomas Ebert
2013-03-07 23:00 ` Michael Tremer
[not found] <5139A3B7.5070503@gmx.de>
2013-03-08 9:00 ` 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=512E30AA.7040608@gmx.de \
--to=th.ebert@gmx.de \
--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