Never mind. This worked: git clone git://
> On Tue, May 6, 2014 at 1:27 PM, Juerg Haefliger <email@example.com
>> Hi Charles,
>> On Tue, May 6, 2014 at 12:42 PM, Charles Plessy <firstname.lastname@example.org
>> > Le Wed, Apr 23, 2014 at 04:17:03PM +0900, Charles Plessy a écrit :
>> > >
>> > > By the way, I have not yet uploaded cloud-init 7.5, since I still have problems
>> > > with the regression tests failing in a minimal environment. Suggestions are
>> > > welcome.
>> > Hello everybody,
>> > cloud-init is still not uploaded as I do not know how to solve the problem.
>> Thanks for the reminder. I wanted to take a look but forgot. Will spend some cycles on it today.
>> > This said, it is an architecture-independant package, and I sometimes wonder if
>> > the Ubuntu version of it is built in a chroot or on the developer's machine.
>> > What I can do is to upload cloud-init after building on my machine outside a
>> > chroot. Another possibility would be to build it in a chroot after disabling
>> > regression tests.
>> > Does anybody has a better solution ?
If so, what you can do is to exclude the smartOS tests until we get them fixed upstream. Something like the following:
diff --git a/debian/rules b/debian/rules
index 043615d..c292c09 100755
@@ -10,7 +10,7 @@ override_dh_install:
ifeq (,$(findstring nocheck, $(DEB_BUILD_OPTIONS)))
- $(MAKE) test
+ $(MAKE) test noseopts='--exclude=test_smartos'