Tag Info

Hot answers tagged

21

sbuild and pbuilder have developed over the years to have nearly identical functionality, and as features are added to either, they tend to be quickly adopted by the other. As Debian packaging is a policy-driven format, it is a significant aid in determining whether a given build issue is a bug in the implementation of the builder or a problem with the ...


12

It's always dangerous to disagree with Emmet, so let me start off by acknowledging that his answer is probably more correct. However, I personally find pbuilder more user-friendly and more performant out of the box. If you are on Ubuntu 12.10 or later, be sure to install the excellent pbuilder-scripts, which are a set of extremely friendly wrappers around ...


6

Yes, copied from: pbuilder. It is possible to use user-mode-linux by invoking pbuilder-user-mode-linux instead of pbuilder. pbuilder-user-mode-linux doesn't require root privileges, and it uses the copy-on-write (COW) disk access method of User-mode-linux which typically makes it much faster than the traditional pbuilder. User-mode-linux is a somewhat less ...


5

You can stick them in a simple repo created with dpkg-scanpackages and make that available via apache. Then update pbuilder's apt config to use your repo.


4

This can be done a few ways. As mentioned by adol, the Ubuntu wiki has a nice example of how to do this by creating a local repository with mini-dinstall and adding that to your pbuilder config. Dennis' answer about using dpkg-scanpackages works as well. I've been doing this recently with apt-ftparchive. I like this approach since I find it very light ...


4

If you could be more specific about the problems you are facing, I might be able to give you a better answer. You might want to look as the pbuilder-dist script in the ubuntu-dev-tools package. It greatly helps with managing multiple pbuilders for different target environments. As an example, to create a Karmic pbuilder run: pbuilder-dist karmic create ...


4

Lintian can be run inside cowbuilder or pbuilder using hooks. Several examples are available in /usr/share/doc/pbuilder/examples/ Just copy the hook you want to a directory: mkdir ~/pbuilderhooks cp /usr/share/doc/pbuilder/examples/B90lintian $HOME/pbuilderhooks Then tell pbuilder to use the hooks in that directory: echo "HOOKDIR=$HOME/pbuilderhooks/" ...


4

Try adding the following to your ~/.pbuilderrc: COMPONENTS="main universe multiverse restricted" or, as SunSparc suggested, enter the command as follows: COMPONENTS="main universe multiverse restricted" cowbuilder --create --distribution lucid cowbuilder is in the universe component for lucid. I don't see the create operation trying to access universe in ...


4

I've used a tmpfs for pbuilder before, and done some benchmarks against ext4. With 4GB of ram it ended up being between 30%-100% faster on the tmpfs for most packages, up to packages as big as Xorg. You'll want to bind-mount /var/cache/apt/archives in order to get your package cache available in the chroot. You can get a more efficient build with sbuild ...


4

In order to get it fixed I had to install: sudo apt-get install debian-archive-keyring And then create the chroot with sudo DIST=sid ARCH=i386 pbuilder create --debootstrapopts \ --keyring=/usr/share/keyrings/debian-archive-keyring.gpg


3

The answer is that you don't. pbuilder takes the source package and builds binaries. It also can take the source code without a source package built and create the binaries that you would either host yourself or add to your own debian repository systems to host on your own. That's not what you need for a PPA. What you want to do, and what I strongly ...


3

You first need to create a pbuilder instance locally. To do that, run the command: pbuilder-dist precise create This will create the .pbuilderrc and the ~/pbuilder/precise-base.tgz that you are missing. After that, you can build your .dsc as normal: pbuilder-dist precise build ../gedit_3.1.1-0ubuntu4.dsc


3

The critical error message (below) baffled me for a little bit until I walked through exactly what cowbuilder (and the underlying pbuilder tool) are trying to do. Package cowdancer is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source It is a ...


2

pbuilder is used to build binary packages from a source package. PPAs also build binary packages from source packages. Simply dput the source.changes file that you created when you also created the <package>_<version>.dsc file. One of the main points in using pbuilder is to locally mimic the clean chroot environment that is used to build the ...


2

Keep in mind that hardlinks can't work across filesystems. I think using tmpfs would be bad.


2

Like this: $ sudo pbuilder --login --save-after-login # echo 'Acquire::http { Proxy "http://servername:3142"; };' > /etc/apt/apt.conf.d/02proxy # exit $ Alternatively, you could use the --execute option: $ sudo pbuilder --execute /tmp/setup-apt-proxy.sh ... where /tmp/setup-apt-proxy.sh contains commands to create /etc/apt/apt.conf.d/02proxy.


1

If you set export http_proxy=http://your-proxy:8080/ in ~/.pbuilderrc it will use that proxy for the package downloads. I just tried it on my setup, and it worked. As best I could tell from the internet traffic, I didn't have to download anything while running pbuilder create. The nice thing is that this way also works when you are creating the tarball, ...


1

I wasn't able to configure changeroots that worked for this, so I've been using a lucid vm alongside my karmic vm, building on either as needed.


1

Actually, there is a section in the git-buildpackage documentation matching your use case. Basically, the difference is that, when importing a new release into your debian branch, you will merge modifications from a tag corresponding to the new release of your software instead of a tarball. As no tarball is involved, there is no need to use git-import-orig. ...


1

Looking at the source for /usr/share/gdebi/GDebi/GDebiCli.py we see that the pbuilder-dist script is dying when gdebi tries to exec dpkg. As it happens, we can get the strange OSError: [Errno 2] No such file or directory when trying to exec a 32-bit executable on a 64-bit system without libc6:i386 installed. Investigating further into ...


1

With Ubuntu 12.04 Precise you might want to check the comment #18 at https://bugs.launchpad.net/ubuntu/+source/pbuilder/+bug/599695 In short: The key ID 8B48AD6246925553 in the error message is for Debian 7.0 Wheezy, so... ... find the corresponding key 46925553 from ...



Only top voted, non community-wiki answers of a minimum length are eligible