Ubuntu
mach package

mach 0.9.1-3.1ubuntu1 source package in Ubuntu

Changelog

mach (0.9.1-3.1ubuntu1) raring; urgency=low

  * Backported change from upstream version 1.0.2 to check setreuid(),
    fixing FTBFS.
 -- Daniel T Chen <email address hidden>   Mon, 01 Apr 2013 12:49:49 -0400

Upload details

Uploaded by:
Daniel T Chen
Uploaded to:
Raring
Original maintainer:
Ubuntu Developers
Architectures:
any
Section:
admin
Urgency:
Low Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Trusty release universe admin

Downloads

File Size SHA-256 Checksum
mach_0.9.1.orig.tar.gz 408.4 KiB 993b59c1cdd90feff3e25938b744d1e8764a88e3b7d82144eb1500e0f6a79f0d
mach_0.9.1-3.1ubuntu1.diff.gz 6.7 KiB 7854525f75175d8b5f822ae3c854ced671740bcb294c1c8ecbbcc6e64f6229dd
mach_0.9.1-3.1ubuntu1.dsc 1.5 KiB 7834774e89ceebfb131604786fdabb3e4f8af40b4d8c61ccf922017eb3a6577a

Available diffs

View changes file

Binary packages built by this source

mach: make a chroot of a rpm-based distribution

 mach allows you to set up clean roots from scratch for any distribution or
 distribution variation supported.
 .
 This clean build root can be used for several goals:
  - making clean packages
  - set up chroots for services to run it
  - make disk images of clean roots (for example for UML)
 .
 Currently, mach works for rpm-based distributions that can work with apt
 for rpm.
 .
 Included at this moment is the necessary information to set up:
  - Fedora 1, 2, 3, 4, 5, 6, and development
  - Red Hat 7.0, 7.1, 7.2, 7.3, 8, and 9
  - CentOS 4
  - Dave/Dina
  - Conectiva 9
  - SuSE 8.1, 8.2, and 9.0
  - Yellowdog 2.3, and 3.0
 .
 Some handy features of mach include:
  - "caching" of downloaded packages using the build hosts's apt
    the build root
  - ensures clean packages by reverting to the base set of build packages
  - uses apt to resolve dependencies
  - parsing of BuildRequires to install necessary packages for building
  - build ordering when doing multiple builds
  - support for flavours of distribution
  - multiple build roots
  - locking of buildroot to avoid concurrent builds
  - optional signing of built packages