From: Thomas Ebert <th.ebert@gmx.de>
To: development@lists.ipfire.org
Subject: Re: IPFire 3.x packfire
Date: Wed, 27 Feb 2013 16:22:24 +0100 [thread overview]
Message-ID: <512E24B0.5060007@gmx.de> (raw)
In-Reply-To: <1361978078.28061.370.camel@rice-oxley.tremer.info>
[-- Attachment #1: Type: text/plain, Size: 3250 bytes --]
Hi Michael,
[root(a)ipfire ~]# pakfire --version
pakfire 0.9.23
is this the information you needed or do you need some more files or
outputs.
regards
Thomas
Am 27.02.2013 16:14, schrieb Michael Tremer:
> Hi,
>
> this not really a bug, but we should possible print a more understable
> error message: Basically this says that the version of pakfire does not
> support the latest package format.
>
> Could you please provide me the version of pakfire you have currently
> installed on your system? I will push an older version so you can update
> to that first and then move to the latest one.
>
> @Stevee: We should update the image, because I do not want to have such
> old versions of some packages lying around in the stable repositories!
>
> Michael
>
> On Tue, 2013-02-26 at 23:53 +0100, Thomas Ebert wrote:
>> I've tried to use this image:
>> http://people.ipfire.org/~stevee/IPFire_3.x/VM-Images/20121006/i686/ipfire-3.x-i686-20121006.img.xz
>>
>> But i get the following error while trying these commands:
>> pakfire install pakfire-builder
>> pakfire update
>>
>> Loading installed packages Time: 00:00:17
>> Traceback (most recent call last):
>> File "/bin/pakfire", line 61, in <module>
>> cli.run()
>> File "/usr/lib/python2.7/site-packages/pakfire/cli.py", line 286, in run
>> return func()
>> File "/usr/lib/python2.7/site-packages/pakfire/cli.py", line 306, in
>> handle_update
>> **args)
>> File "/usr/lib/python2.7/site-packages/pakfire/api.py", line 53, in
>> update
>> allow_vendorchange=allow_vendorchange,
>> allow_archchange=allow_archchange)
>> File "/usr/lib/python2.7/site-packages/pakfire/base.py", line 501, in
>> update
>> t = solver.transaction
>> File "/usr/lib/python2.7/site-packages/pakfire/satsolver.py", line
>> 184, in transaction
>> transaction.Transaction.from_solver(self.pakfire, self)
>> File "/usr/lib/python2.7/site-packages/pakfire/transaction.py", line
>> 235, in from_solver
>> transaction.add(action_name, pkg)
>> File "/usr/lib/python2.7/site-packages/pakfire/transaction.py", line
>> 256, in add
>> action = cls(self.pakfire, pkg)
>> File "/usr/lib/python2.7/site-packages/pakfire/actions.py", line 42,
>> in __init__
>> binary_package = self.pkg.get_from_cache()
>> File "/usr/lib/python2.7/site-packages/pakfire/packages/solv.py",
>> line 240, in get_from_cache
>> return file.BinaryPackage(self.pakfire, self.repo, path)
>> File "/usr/lib/python2.7/site-packages/pakfire/packages/file.py",
>> line 143, in __init__
>> self.check()
>> File "/usr/lib/python2.7/site-packages/pakfire/packages/file.py",
>> line 169, in check
>> assert self.format in PACKAGE_FORMATS_SUPPORTED, self.format
>> AssertionError: 5
>>
>> If needed, i can put logfiles here
>> _______________________________________________
>> 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 15:22 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 [this message]
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
[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=512E24B0.5060007@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