Closed dirk-thomas closed 9 years ago
The sync machine was longer running and had the previous version of debootstrap installed. I upgraded that package on the machine. This should fix the problem. Vivid was added in 0.7 http://changelogs.ubuntu.com/changelogs/pool/main/d/debootstrap/debootstrap_1.0.40~ubuntu0.7/changelog
# apt-get install debootstrap
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
debootstrap
1 upgraded, 0 newly installed, 0 to remove and 111 not upgraded.
Need to get 33.7 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://mirrors.liquidweb.com/ubuntu/ precise-updates/main debootstrap all 1.0.40~ubuntu0.7 [33.7 kB]
Fetched 33.7 kB in 0s (336 kB/s)
(Reading database ... 153556 files and directories currently installed.)
Preparing to replace debootstrap 1.0.40~ubuntu0.6 (using .../debootstrap_1.0.40~ubuntu0.7_all.deb) ...
Unpacking replacement debootstrap ...
Processing triggers for man-db ...
Setting up debootstrap (1.0.40~ubuntu0.7) ...
One example (of many cases) is http://jenkins.ros.org/job/ros-jade-rosgraph_binarydeb_vivid_i386/1/console
@tfoote Any idea why pbuilder / debootstrap fails? Retriggering usually solves the problem.