arch-ppa icon indicating copy to clipboard operation
arch-ppa copied to clipboard

Build order issue for large metapackages

Open sjdrc opened this issue 8 years ago • 1 comments

I am using arch-ppa on a remote arch linux arm server to build packages for my nVidia Jetson TK1, also running arch linux arm.

I have run

./arch-ppa add ros-indigo-desktop-full ./arch-ppa build ros-indigo

I get this output

$ ./arch-ppa build ros-indigo-armv7h $ makechrootpkg -r /home/sebastien/ros-indigo/chroot -l ros-indigo-armv7h -- -Ai ==> Making package: ros-indigo-cpp-common 0.5.7-1 (Fri May 20 22:54:52 UTC 2016) ==> Retrieving sources... -> Found ros-indigo-cpp-common-0.5.7-0.tar.gz ==> Validating source files with sha256sums... ros-indigo-cpp-common-0.5.7-0.tar.gz ... Passed ==> Making package: ros-indigo-cpp-common 0.5.7-1 (Fri May 20 22:54:56 UTC 2016) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Installing missing dependencies... error: target not found: ros-build-tools error: target not found: ros-indigo-catkin ==> ERROR: 'pacman' failed to install missing dependencies. ==> ERROR: Build failed, check /home/sebastien/ros-indigo/chroot/ros-indigo-armv7h/build

ros-build-tools and ros-indigo-catkin both have folders in the src/ folder.

How does arch-ppa decide the order in which it builds packages?

sjdrc avatar May 20 '16 22:05 sjdrc

So I might have found a way around this by added two of the packages in the dependency chain first (ros-indigo-catkin and ros-build-tools), building, and then adding the full package ros-indigo-desktop-full.

Edit: jumped the gun, it fell over another dependency right after I posted that.

sjdrc avatar May 21 '16 00:05 sjdrc