* IPFire 3.x packfire
@ 2013-02-26 22:53 Thomas Ebert
2013-02-27 15:14 ` Michael Tremer
0 siblings, 1 reply; 14+ messages in thread
From: Thomas Ebert @ 2013-02-26 22:53 UTC (permalink / raw)
To: development
[-- Attachment #1: Type: text/plain, Size: 1907 bytes --]
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
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: IPFire 3.x packfire
2013-02-26 22:53 IPFire 3.x packfire Thomas Ebert
@ 2013-02-27 15:14 ` Michael Tremer
2013-02-27 15:22 ` Thomas Ebert
0 siblings, 1 reply; 14+ messages in thread
From: Michael Tremer @ 2013-02-27 15:14 UTC (permalink / raw)
To: development
[-- Attachment #1: Type: text/plain, Size: 2771 bytes --]
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
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: IPFire 3.x packfire
2013-02-27 15:14 ` Michael Tremer
@ 2013-02-27 15:22 ` Thomas Ebert
2013-02-27 15:32 ` Michael Tremer
0 siblings, 1 reply; 14+ messages in thread
From: Thomas Ebert @ 2013-02-27 15:22 UTC (permalink / raw)
To: development
[-- 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
>
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: IPFire 3.x packfire
2013-02-27 15:22 ` Thomas Ebert
@ 2013-02-27 15:32 ` Michael Tremer
2013-02-27 15:37 ` Thomas Ebert
0 siblings, 1 reply; 14+ messages in thread
From: Michael Tremer @ 2013-02-27 15:32 UTC (permalink / raw)
To: development
[-- Attachment #1: Type: text/plain, Size: 3902 bytes --]
Well, according to the changelog,
https://pakfire.ipfire.org/package/pakfire/changelog
version 0.9.23 should support the new package format.
Could you please check which release is installed by running:
pakfire info pakfire
Thanks.
Michael
On Wed, 2013-02-27 at 16:22 +0100, Thomas Ebert wrote:
> 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
> >
>
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: IPFire 3.x packfire
2013-02-27 15:32 ` Michael Tremer
@ 2013-02-27 15:37 ` Thomas Ebert
2013-02-27 15:52 ` Michael Tremer
0 siblings, 1 reply; 14+ messages in thread
From: Thomas Ebert @ 2013-02-27 15:37 UTC (permalink / raw)
To: development
[-- Attachment #1: Type: text/plain, Size: 1213 bytes --]
Here is the complete output:
stable: package database | 2.0 MB 00:00 ...
Loading installed packages Time: 00:00:18
Name : pakfire
Arch : i686
Version : 0.9.23
Release : 4.ip3
Size : 20
Repo : @system
Summary : Package installer/updater.
Groups : Base System/Packaging
URL : None
License : GPLv3+
Description : Pakfire optains package lists from the mirrors and can install
: and update packages.
Name : pakfire
Arch : i686
Version : 0.9.24
Release : 2.ip3
Size : 20
Repo : stable
Summary : Package installer/updater.
Groups : Base System/Packaging
URL : http://www.ipfire.org/
License : GPLv3+
Description : Pakfire optains package lists from the mirrors and can install
: and update packages.
Name : pakfire
Arch : i686
Version : 0.9.24
Release : 3.ip3
Size : 20
Repo : stable
Summary : Package installer/updater.
Groups : Base System/Packaging
URL : http://www.ipfire.org/
License : GPLv3+
Description : Pakfire optains package lists from the mirrors and can install
: and update packages.
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: IPFire 3.x packfire
2013-02-27 15:37 ` Thomas Ebert
@ 2013-02-27 15:52 ` Michael Tremer
2013-02-27 16:04 ` Thomas Ebert
0 siblings, 1 reply; 14+ messages in thread
From: Michael Tremer @ 2013-02-27 15:52 UTC (permalink / raw)
To: development
[-- Attachment #1: Type: text/plain, Size: 1748 bytes --]
Please try to install pakfire-0.9.24-1.ip3 first and then go ahead.
# pakfire install "pakfire=0.9.24-1.ip3"
# pakfire update pakfire
# pakfire update
It may take a while until the package appears in the repository.
Michael
On Wed, 2013-02-27 at 16:37 +0100, Thomas Ebert wrote:
> Here is the complete output:
>
> stable: package database | 2.0 MB 00:00 ...
> Loading installed packages Time: 00:00:18
> Name : pakfire
> Arch : i686
> Version : 0.9.23
> Release : 4.ip3
> Size : 20
> Repo : @system
> Summary : Package installer/updater.
> Groups : Base System/Packaging
> URL : None
> License : GPLv3+
> Description : Pakfire optains package lists from the mirrors and can install
> : and update packages.
>
> Name : pakfire
> Arch : i686
> Version : 0.9.24
> Release : 2.ip3
> Size : 20
> Repo : stable
> Summary : Package installer/updater.
> Groups : Base System/Packaging
> URL : http://www.ipfire.org/
> License : GPLv3+
> Description : Pakfire optains package lists from the mirrors and can install
> : and update packages.
>
> Name : pakfire
> Arch : i686
> Version : 0.9.24
> Release : 3.ip3
> Size : 20
> Repo : stable
> Summary : Package installer/updater.
> Groups : Base System/Packaging
> URL : http://www.ipfire.org/
> License : GPLv3+
> Description : Pakfire optains package lists from the mirrors and can install
> : and update packages.
>
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: IPFire 3.x packfire
2013-02-27 15:52 ` Michael Tremer
@ 2013-02-27 16:04 ` Thomas Ebert
2013-02-27 16:05 ` Michael Tremer
0 siblings, 1 reply; 14+ messages in thread
From: Thomas Ebert @ 2013-02-27 16:04 UTC (permalink / raw)
To: development
[-- Attachment #1: Type: text/plain, Size: 1419 bytes --]
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
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: IPFire 3.x packfire
2013-02-27 16:04 ` Thomas Ebert
@ 2013-02-27 16:05 ` Michael Tremer
2013-02-27 16:13 ` Thomas Ebert
0 siblings, 1 reply; 14+ messages in thread
From: Michael Tremer @ 2013-02-27 16:05 UTC (permalink / raw)
To: development
[-- Attachment #1: Type: text/plain, Size: 1791 bytes --]
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
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: IPFire 3.x packfire
2013-02-27 16:05 ` Michael Tremer
@ 2013-02-27 16:13 ` Thomas Ebert
0 siblings, 0 replies; 14+ messages in thread
From: Thomas Ebert @ 2013-02-27 16:13 UTC (permalink / raw)
To: development
[-- 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
>
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: IPFire 3.x packfire
[not found] <5139A3B7.5070503@gmx.de>
@ 2013-03-08 9:00 ` Michael Tremer
0 siblings, 0 replies; 14+ messages in thread
From: Michael Tremer @ 2013-03-08 9:00 UTC (permalink / raw)
To: development
[-- Attachment #1: Type: text/plain, Size: 2779 bytes --]
Okay, then we don't have an error in the code base.
I tried to clarify what happens in a couple of sentences on which I was
not quite successful:
http://wiki.ipfire.org/devel/pakfire/architecture#clean_build_environments
Maybe some else can improve that?
-Michael
On Fri, 2013-03-08 at 09:39 +0100, Thomas Ebert wrote:
> Tnanks for the explanation Michael.
>
> As i mentioned before, that pakfire3 doesn't re-download the packages.
> ... they are not deleted!
>
> I missunderstood the output.
>
> Regards Thomas
>
>
> Am 08.03.2013 00:00, schrieb Michael Tremer:
> > Yes, the build environment is cleaned up after every build. This is
> > intentional, so you start every build in a clean environment and don't
> > get caught up in any errors.
> >
> > However, the downloaded package files are never deleted.
> >
> > Are you sure you see a re-download or just the extraction?
> >
> > -Michael
> >
> > On Thu, 2013-03-07 at 18:38 +0100, Thomas Ebert wrote:
> >> Hello out there.
> >>
> >> I know most of you are very busy at the moment, but could anybody of you
> >> provide an answer of my question?
> >> ... Is it normal that the build environment is cleaned everytime if you
> >> exit from it and start the command "pakfire-builder shell"?
> >>
> >> Regards
> >> Thomas
> >>
> >> Am 01.03.2013 13:43, schrieb Thomas Ebert:
> >>> Sorry. I missunderstood the output. Packfire is using local packages
> >>> as you described. But what about the build chroot environment. Is it
> >>> normal that the build environment is cleaned everytime if you exit
> >>> from it and start the command "pakfire-builder shell".
> >>>
> >>> Here is the paste from my shell: http://pastebin.com/fKn3UECQ
> >>>
> >>> This is my configuration /etc/pakfire/builder.conf
> >>>
> >>> [logger]
> >>>
> >>> # Use a different log file for the builder stuff.
> >>> file = /var/log/pakfire-builder.log
> >>>
> >>> [builder]
> >>> # Select the distribution to build for.
> >>> distro = ipfire3
> >>>
> >>> # Use ccache in order to build rebuilds in less time.
> >>> use_ccache = true
> >>>
> >>> # Use icecream in order to speed up builds.
> >>> use_icecream = false
> >>>
> >>> # Create build environments in a tmpfs.
> >>> # This requires a lot of RAM.
> >>> # Only enable if you know what your are doing.
> >>> #use_tmpfs = false
> >>>
> >>> # Create loop devices in build environment.
> >>> #use_loop_devices = true
> >>>
> >>> Regards
> >> _______________________________________________
> >> 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
> >
>
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: IPFire 3.x packfire
2013-03-07 17:38 ` Thomas Ebert
@ 2013-03-07 23:00 ` Michael Tremer
0 siblings, 0 replies; 14+ messages in thread
From: Michael Tremer @ 2013-03-07 23:00 UTC (permalink / raw)
To: development
[-- Attachment #1: Type: text/plain, Size: 1883 bytes --]
Yes, the build environment is cleaned up after every build. This is
intentional, so you start every build in a clean environment and don't
get caught up in any errors.
However, the downloaded package files are never deleted.
Are you sure you see a re-download or just the extraction?
-Michael
On Thu, 2013-03-07 at 18:38 +0100, Thomas Ebert wrote:
> Hello out there.
>
> I know most of you are very busy at the moment, but could anybody of you
> provide an answer of my question?
> ... Is it normal that the build environment is cleaned everytime if you
> exit from it and start the command "pakfire-builder shell"?
>
> Regards
> Thomas
>
> Am 01.03.2013 13:43, schrieb Thomas Ebert:
> > Sorry. I missunderstood the output. Packfire is using local packages
> > as you described. But what about the build chroot environment. Is it
> > normal that the build environment is cleaned everytime if you exit
> > from it and start the command "pakfire-builder shell".
> >
> > Here is the paste from my shell: http://pastebin.com/fKn3UECQ
> >
> > This is my configuration /etc/pakfire/builder.conf
> >
> > [logger]
> >
> > # Use a different log file for the builder stuff.
> > file = /var/log/pakfire-builder.log
> >
> > [builder]
> > # Select the distribution to build for.
> > distro = ipfire3
> >
> > # Use ccache in order to build rebuilds in less time.
> > use_ccache = true
> >
> > # Use icecream in order to speed up builds.
> > use_icecream = false
> >
> > # Create build environments in a tmpfs.
> > # This requires a lot of RAM.
> > # Only enable if you know what your are doing.
> > #use_tmpfs = false
> >
> > # Create loop devices in build environment.
> > #use_loop_devices = true
> >
> > Regards
>
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: IPFire 3.x packfire
2013-03-01 12:43 ` Thomas Ebert
@ 2013-03-07 17:38 ` Thomas Ebert
2013-03-07 23:00 ` Michael Tremer
0 siblings, 1 reply; 14+ messages in thread
From: Thomas Ebert @ 2013-03-07 17:38 UTC (permalink / raw)
To: development
[-- Attachment #1: Type: text/plain, Size: 1274 bytes --]
Hello out there.
I know most of you are very busy at the moment, but could anybody of you
provide an answer of my question?
... Is it normal that the build environment is cleaned everytime if you
exit from it and start the command "pakfire-builder shell"?
Regards
Thomas
Am 01.03.2013 13:43, schrieb Thomas Ebert:
> Sorry. I missunderstood the output. Packfire is using local packages
> as you described. But what about the build chroot environment. Is it
> normal that the build environment is cleaned everytime if you exit
> from it and start the command "pakfire-builder shell".
>
> Here is the paste from my shell: http://pastebin.com/fKn3UECQ
>
> This is my configuration /etc/pakfire/builder.conf
>
> [logger]
>
> # Use a different log file for the builder stuff.
> file = /var/log/pakfire-builder.log
>
> [builder]
> # Select the distribution to build for.
> distro = ipfire3
>
> # Use ccache in order to build rebuilds in less time.
> use_ccache = true
>
> # Use icecream in order to speed up builds.
> use_icecream = false
>
> # Create build environments in a tmpfs.
> # This requires a lot of RAM.
> # Only enable if you know what your are doing.
> #use_tmpfs = false
>
> # Create loop devices in build environment.
> #use_loop_devices = true
>
> Regards
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: IPFire 3.x packfire
2013-03-01 12:06 ` Michael Tremer
@ 2013-03-01 12:43 ` Thomas Ebert
2013-03-07 17:38 ` Thomas Ebert
0 siblings, 1 reply; 14+ messages in thread
From: Thomas Ebert @ 2013-03-01 12:43 UTC (permalink / raw)
To: development
[-- Attachment #1: Type: text/plain, Size: 898 bytes --]
Sorry. I missunderstood the output. Packfire is using local packages as
you described. But what about the build chroot environment. Is it normal
that the build environment is cleaned everytime if you exit from it and
start the command "pakfire-builder shell".
Here is the paste from my shell: http://pastebin.com/fKn3UECQ
This is my configuration /etc/pakfire/builder.conf
[logger]
# Use a different log file for the builder stuff.
file = /var/log/pakfire-builder.log
[builder]
# Select the distribution to build for.
distro = ipfire3
# Use ccache in order to build rebuilds in less time.
use_ccache = true
# Use icecream in order to speed up builds.
use_icecream = false
# Create build environments in a tmpfs.
# This requires a lot of RAM.
# Only enable if you know what your are doing.
#use_tmpfs = false
# Create loop devices in build environment.
#use_loop_devices = true
Regards
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: IPFire 3.x packfire
[not found] <512FDB9A.1060009@gmx.de>
@ 2013-03-01 12:06 ` Michael Tremer
2013-03-01 12:43 ` Thomas Ebert
0 siblings, 1 reply; 14+ messages in thread
From: Michael Tremer @ 2013-03-01 12:06 UTC (permalink / raw)
To: development
[-- Attachment #1: Type: text/plain, Size: 2965 bytes --]
The content of /var/cache/pakfire should be:
[root(a)rice-oxley pakfire]# pwd
/var/cache/pakfire
[root(a)rice-oxley pakfire]# ll
total 68
drwxr-xr-x. 19 root root 4096 Dec 8 2011 ccache
drwxr-xr-x 259 root root 4096 Feb 12 19:43 downloads
drwxr-xr-x. 6 root root 4096 Feb 20 2012 repos
drwxr-xr-x. 3 root root 49152 Feb 24 11:45 sources
The download directory contains the following:
[root(a)rice-oxley pakfire]# tree downloads/ | head
downloads/
├── 00
│ ├── 12c06bfdca3fa5454e4f6c3fc07a5b21e2a0e3
│ │ └── gcc-c++-4.7.2-2.ip3.i686.pfm
│ ├── 4ac3f83e78944c4df70f0319fafc650f7bc9a4
│ │ └── perl-Test-Harness-3.23-11.ip3.noarch.pfm
│ ├── 6e4f8ee4f82665e052b9d08d28410870c34794
│ │ └── cpp-4.7.2-2.ip3.i686.pfm
│ ├── aaf07ddbf21bdc95dca317881b7351577b653b
│ │ └── perl-Digest-1.16-11.ip3.noarch.pfm
There is absolutely no code that cleans up the download directory on the
builders.
Michael
On Thu, 2013-02-28 at 23:35 +0100, Thomas Ebert wrote:
> Then is something wrong with my installation:
>
> [root(a)ipfire cache]# find . -name \.gz
> [root(a)ipfire cache]# find . -name \*.gz
> ./man/cat8/network-zone.8.gz
> ./pakfire/sources/lldpd-0.5.4.tar.gz
> ./pakfire/sources/lldpd-0.7.1.tar.gz
> [root(a)ipfire cache]# find . -name \*.bz2
> [root(a)ipfire cache]#
>
> You see the only packages which are in there is the lldpd package which
> first is from the packfire server and the second i manually downloaded?
>
> What files or command output can i provide to trigger the problem?
>
> Am 28.02.2013 23:24, schrieb Michael Tremer:
> > Hi,
> >
> > On Thu, 2013-02-28 at 22:47 +0100, Thomas Ebert wrote:
> >> I've the following problem. Everytime i want to make a package the
> >> script is entirely downloading all needed software for pakfire-builder
> >> again.
> >>
> >> Example: pakfire-builder shell
> >> ...
> >> Installing: 105 packages
> >> Installed size: 391M
> >> ...
> >>
> >> Then i'm leaving the shell and enter the command again. Then he is again
> >> downloading and installing all files with dependencies.
> >>
> >> Is it normal? That's cost much of bandwith and installation time in my
> >> virtual machine.
> > This is not normal. Repository metadata get updated when they are older
> > than 10 minutes and the package database will be downloaded when ever it
> > has changed.
> >
> > Packages will be stored in /var/cache/pakfire and of course they will be
> > reused. Maybe you have a look into that directory and check your time
> > (signatures)?
> >
> > Michael
> >
> > _______________________________________________
> > 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
^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2013-03-08 9:00 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-02-26 22:53 IPFire 3.x packfire 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
[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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox