Re: Is there a way to preserve pbuilder chroot environment?

Can you elaborate a bit on what you mean by having to build a package multiple times before it builds successfully? With pbuilder, your package should be able to be built with a single invocation of pbuilder (given a .dsc) or pdebuild (when unpacked). Anything more than that and the

Re: Is there a way to preserve pbuilder chroot environment?

Pbuilder also supports that using hooks, e.g.: # ln -s /usr/share/doc/pbuilder/examples/C10shell /var/cache/pbuilder/hooks/C10shell ...and the next time your build fails, pbuilder will dump you in the chroot with a shell. I checked this solution, but I'm wondering how to resume pbuilder

Is there a way to preserve pbuilder chroot environment?

I'm new to building packages by using pbuilder tool, and I have to build a package multiple times before it builds successfully, or in the way I prefer. The most annoying part ot this is installation of dependencies -- each time I build a package, it has to install the same dependencies over and

Re: Is there a way to preserve pbuilder chroot environment?

You're right. The better way is to use cowbuilder instead of pbuilder. The first is a wrapper around the latter. Thanks for the hint. signature.asc Description: PGP signature

Re: Is there a way to preserve pbuilder chroot environment?

You shouldn't try to preserve the environment, every time you build stuff you should have a clean installation. I know, but when I work with the same package, I think there's no point in installing the same dependencies over and over. I could save the chroot, and when I finish playing with the

Re: Ccache size for pbuilder

Thanks. signature.asc Description: PGP signature

Ccache size for pbuilder

In pbuilder's config file there's an option: CCACHEDIR=/var/cache/pbuilder/ccache But there's no option as to size of the cache, the one you can see via ccache -s. What is the cache size of the chroot environment? Is there a way to set this parameter somehow? signature.asc Description: PGP