[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Fwd: Bug#745587: base: Cloud AWS EC2 Image will not reply to packets received on additional network interface (ENI)



Upstream bug report: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1316597


On Tue, May 6, 2014 at 2:59 PM, Juerg Haefliger <juergh@gmail.com> wrote:
>
>
>
>
> On Tue, May 6, 2014 at 1:53 PM, Juerg Haefliger <juergh@gmail.com> wrote:
> >
> > Remind me again how to recreate the problem.
> >
> > I'm trying to clone from https://alioth.debian.org/anonscm/git/collab-maint/cloud-init.git/ but:
> > $ git clone https://alioth.debian.org/anonscm/git/collab-maint/cloud-init.git
> > Cloning into 'cloud-init'...
> > fatal: repository 'https://alioth.debian.org/anonscm/git/collab-maint/cloud-init.git/' not found
>
> Never mind. This worked: git clone git://anonscm.debian.org/collab-maint/cloud-init.git
>
>
>
> > On Tue, May 6, 2014 at 1:27 PM, Juerg Haefliger <juergh@gmail.com> wrote:
> >>
> >> Hi Charles,
> >>
> >>
> >>
> >> On Tue, May 6, 2014 at 12:42 PM, Charles Plessy <plessy@debian.org> wrote:
> >> >
> >> > 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.
> >>
> >> ...Juerg
> >>
> >>
> >>
> >> > 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 ?
>
> Assuming this is the problem: https://lists.debian.org/debian-cloud/2014/02/msg00003.html
>
> 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
> --- a/debian/rules
> +++ b/debian/rules
> @@ -10,7 +10,7 @@ override_dh_install:
>  ifeq (,$(findstring nocheck, $(DEB_BUILD_OPTIONS)))
>  override_dh_auto_test:
>         dh_auto_test
> -       $(MAKE) test
> +       $(MAKE) test noseopts='--exclude=test_smartos'
>  endif
>  
>  override_dh_installinit:
>
>
> ...Juerg
>
>
>
>
> >> > Have a nice day,
> >> >
> >> > --
> >> > Charles Plessy
> >> > Debian Med packaging team,
> >> > http://www.debian.org/devel/debian-med
> >> > Tsurumi, Kanagawa, Japan
> >> >
> >> >
> >> > --
> >> > To UNSUBSCRIBE, email to debian-cloud-request@lists.debian.org
> >> > with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> >> > Archive: 20140506104226.GB21325@falafel.plessy.net">https://lists.debian.org/20140506104226.GB21325@falafel.plessy.net
> >> >
> >
> >


Reply to: