I have following log using pbuilder: user@comp:~/PROSTOR/pkg-csp$ sudo pbuilder create --configfile /tmp/lastrc --buildplace /var/cache/pbuilder/alse47-arm64/alse47-arm64.cow --mirror https://dl.astralinux.ru/astra/stable/4.7_arm/repository-main --distribution 4.7_arm --no-targz --extrapackages 'cowdancer pbuilder fakeroot quilt python devscripts eatmydata procps locales cowdancer' [sudo] password for user: W: /root/.pbuilderrc does not exist perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LC_ALL = (unset), LC_ADDRESS = "en_US.UTF-8", LC_NAME = "en_US.UTF-8", LC_MONETARY = "en_US.UTF-8", LC_PAPER = "en_US.UTF-8", LC_IDENTIFICATION = "en_US.UTF-8", LC_TELEPHONE = "en_US.UTF-8", LC_MEASUREMENT = "en_US.UTF-8", LC_TIME = "en_US.UTF-8", LC_NUMERIC = "en_US.UTF-8", LANG = "ru_RU.UTF-8" are supported and installed on your system. perl: warning: Falling back to a fallback locale ("ru_RU.UTF-8"). E: Directory /var/cache/pbuilder/alse47-arm64/alse47-arm64.cow does not exist here is /tmp/lastrc https://gist.github.com/iva-nova-e-katerina/46b9e5ae4cbb55a3ec45d5327e22c0b3 what am I doing wrong?

I'm using pbuilder to build my binary package for Debian. pbuilder creates a chroot environment, installs all the packages declared as required for the build, and then builds the binary .deb packages inside this chroot. I already have my .spec file. I can build it. However, I have several versions of my project to build, and each have different requirements for some packages they depend on. Therefore I have to install/uninstall these dependent packages depending on which version of my project I want to build (error prone). I also cannot build in parallel if requirements are different and are supposed to be installed on the main filesystem. I'm looking for the same kind of tool as pbuilder to build my binary .rpm packages. - I've found an antique mach tool which looks abandoned. - I've found rinse but it only does the bootstrap part. - Also yum-builddep installs on the whole system, not a chroot. Anyone knows a tool like pbuilder that resolves the dependencies and then builds an RPM inside a chroot?

debuild has an option --lintian-opts that allows to pass options to lintian. How can I pass options to lintian from pdebuild?

I am trying to create pbuilder. When I do sudo create pbuilder, I get following error: E: Failed getting release file http://security.debian.org/debian-security/dists/sid/Release E: debootstrap failed Infact http://security.debian.org/debian-security/dists/sid/Release is not accessible. How can I configure a valid source link?

I was running cowbuilder --update and got the following - $ sudo cowbuilder --update [sudo] password for shirish: I: Copying COW directory I: forking: rm -rf /var/cache/pbuilder/build/cow.12496 I: forking: cp -al /var/cache/pbuilder/sid-amd64/base.cow /var/cache/pbuilder/build/cow.12496 I: removed stale ilistfile /var/cache/pbuilder/build/cow.12496/.ilist I: Invoking pbuilder I: forking: pbuilder update --buildplace /var/cache/pbuilder/build/cow.12496 --mirror http://deb.debian.org/debian/ --distribution sid --no-targz --internal-chrootexec 'chroot /var/cache/pbuilder/build/cow.12496 cow-shell' I: Running in no-targz mode I: Current time: Sun Sep 2 01:16:22 IST 2018 I: pbuilder-time-stamp: 1535831182 I: copying local configuration W: --override-config is not set; not updating apt.conf Read the manpage for details. I: mounting /proc filesystem I: mounting /sys filesystem I: creating /{dev,run}/shm I: mounting /dev/pts filesystem I: redirecting /dev/ptmx to /dev/pts/ptmx I: policy-rc.d already exists I: Refreshing the base.tgz I: upgrading packages Get:1 http://cdn-fastly.deb.debian.org/debian sid InRelease [233 kB] Get:2 http://cdn-fastly.deb.debian.org/debian sid/main amd64 Packages.diff/Index [27.9 kB] Get:3 http://cdn-fastly.deb.debian.org/debian sid/main amd64 Packages 2018-09-01-1408.47.pdiff [11.0 kB] Get:3 http://cdn-fastly.deb.debian.org/debian sid/main amd64 Packages 2018-09-01-1408.47.pdiff [11.0 kB] Fetched 272 kB in 3s (97.6 kB/s) Reading package lists... I: Obtaining the cached apt archive contents Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... The following packages will be upgraded: libidn2-0 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 76.4 kB of archives. After this operation, 120 kB of additional disk space will be used. Get:1 http://cdn-fastly.deb.debian.org/debian sid/main amd64 libidn2-0 amd64 2.0.5-1 [76.4 kB] Fetched 76.4 kB in 1s (79.8 kB/s) debconf: delaying package configuration, since apt-utils is not installed (Reading database ... 11986 files and directories currently installed.) Preparing to unpack .../libidn2-0_2.0.5-1_amd64.deb ... Unpacking libidn2-0:amd64 (2.0.5-1) over (2.0.4-2.2) ... Setting up libidn2-0:amd64 (2.0.5-1) ... Processing triggers for libc-bin (2.27-5) ... Reading package lists... Building dependency tree... Reading state information... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Reading package lists... Building dependency tree... Reading state information... aptitude is already the newest version (0.8.10-9). build-essential is already the newest version (12.5). dpkg-dev is already the newest version (1.19.0.5). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. I: Copying back the cached apt archive contents I: new cache content 'libidn2-0_2.0.5-1_amd64.deb' added I: unmounting dev/ptmx filesystem I: unmounting dev/pts filesystem I: unmounting dev/shm filesystem I: unmounting proc filesystem I: unmounting sys filesystem I: removing cowbuilder working copy I: Moving work directory [/var/cache/pbuilder/build/cow.12496] to final location [/var/cache/pbuilder/sid-amd64/base.cow] and cleaning up old copy I: forking: rm -rf /var/cache/pbuilder/build/cow.12496-12496-tmp Now in /var/cache/pbuilder I get the following directories - /var/cache/pbuilder$ ls aptcache build result sid-amd64 Now from little I understand aptcache has the .deb packages that may be needed, build is where a package is being built, result is when there are successfully built packages and sid-amd64 where the base.cow or the minimal Debian distribution which needs those packages for package building are there. IIUC, then both aptcache and base.cow will fatten over time as new packages are being built. Am I correct in this understanding ? If yes, how do I go about adding apt-utils in aptcache as well as the base.cow ? See this line from the action shared before - debconf: delaying package configuration, since apt-utils is not installed. Update - 02/09/18 - I tried the following - $ sudo pbuilder --autocleanaptcache pbuilder - a personal builder Copyright 2001-2007 Junichi Uekawa Distributed under GNU Public License version 2 or later pbuilder [operation] [pbuilder-options] pdebuild [pdebuild-options] -- [pbuilder-options] ........ For some reason it seems the command does not work, either I spelled it wrongly or it needs the explicit path for the command to work. Before that I did try $cowbuilder ----autocleanaptcache but even that didn't get anything. At the end I had to go with - $ sudo pbuilder clean I: Cleaning [/var/cache/pbuilder/build] I: removing directory /var/cache/pbuilder/build and its subdirectories I: Cleaning [/var/cache/pbuilder/aptcache/] shirish@debian:~$ cd /var/cache/pbuilder/aptcache/

This is what my existing ~/.pbuilderrc is which is symlinked to ~/root/.pbuilderrc $ cat ~/.pbuilderrc BASEPATH="/var/cache/pbuilder/sid-amd64/base.cow" DISTRIBUTION="sid" MIRRORSITE="http://deb.debian.org/debian/ " # Enable build log PKGNAME_LOGFILE="yes" while I am understanding how cowbuilder and pbuilder works, is it possible to have a log file which shows how the build happened even after the build is successfully created. Update - I am using cowbuilder and don't see any way to have detailed logs to keep after a run happens.

I want pbuilder on debian to create a chrooted env, install build dependencies, build a package and then launch a shell and let me analyze the build directory. For example, if I run: sudo pbuilder --build snacc_1.3.1-5.dsc there's a file: /var/cache/pbuilder/build/20352/tmp/buildd/snacc-1.3.1/compiler/back-ends/c-gen/util.c It gets deleted after. mock for rhel has the option --no-clean-after. Can't find a similar option in pbuild. There's --preserve-buildplace, but it does something else.

I'm updating a debian package and I need to call an external build dependency which is actually a toolchain. It doesn't have a deb package so I can't provide Build-Depends. I've chosen to include it in the source archive instead, and am calling ndk-build which then calls various tools e.g. arm-linux-androideabi-gcc which reside in a toolchains folder within the bundle. When I reference this in debian/rules: override_dh_auto_build-arch I am using $(CURDIR) which resolves to /build/pkgname-1.0. It succeeds when running fakeroot debian/rules build, but not when I run the whole process using pdebuild. I get the following output when building for i386: make: Entering directory '/build/pkgname-1.0' NDK_PROJECT_PATH=/build/pkgname-1.0/android/ /build/pkgname-1.0/android-ndk-r12/ndk-build make: Entering directory '/build/pkgname-1.0' [armeabi-v7a] Compile thumb : dpfp <= dpfp.c make: /build/pkgname-1.0/android-ndk-r12/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86/bin/arm-linux-androideabi-gcc: Command not found /build/pkgname-1.0/android-ndk-r12/build/core/build-binary.mk:472: recipe for target '/build/pkgname-1.0/android//obj/local/armeabi-v7a/objs/dpfp/__/__/examples/dpfp.o' failed make: *** [/build/pkgname-1.0/android//obj/local/armeabi-v7a/objs/dpfp/__/__/examples/dpfp.o] Error 127 make: Leaving directory '/build/pkgname-1.0' Is this a chroot pathing issue? The files definitely exist in the folder shown as I have added ls -R when troubleshooting and I can see: /build/pkgname-1.0/android-ndk-r12/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86/bin: arm-linux-androideabi-gcc I've tried adding the folder to PATH, calling sh ndk-build, explicitly moving the bundle folder to $(CURDIR) but nothing seems to work.

We run an automated build system using pbuilder-dist. We use it to build our open source project [Snap Websites](https://sourceforge.net/p/snapcpp/code/ci/master/tree/) to produce nightly builds. Currently we are building against Ubuntu "trusty." The issue we face is that periodically the packages in Ubuntu are updated and our chroot environment needs to be updated. In short, we want to run commands from cron within the chroot like so: # apt-get update # apt-get upgrade # apt-get autoremove However, I don't see a way to do this. Yes there are pbuilder hooks, but I don't see a way to do this from a cron script: # pbuilder-dist trusty login --save-after-login ...and then feed it commands like above. Any ideas? I've looked at the documentation for pbuilder but I don't see a clean and obvious way, so I thought I'd ask here.