Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id E8966431FB6 for ; Fri, 16 May 2014 04:12:08 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.7 X-Spam-Level: X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kQrbgEv4URWM for ; Fri, 16 May 2014 04:12:04 -0700 (PDT) Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com [209.85.212.174]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id 066AF431FAE for ; Fri, 16 May 2014 04:12:03 -0700 (PDT) Received: by mail-wi0-f174.google.com with SMTP id r20so755219wiv.7 for ; Fri, 16 May 2014 04:12:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:subject:in-reply-to:references:user-agent :from:date:message-id:mime-version:content-type; bh=DPtk+C9p7iqFmL0jvVQzZekDrMQBWWt6wunnB4VZYmo=; b=foHgQhuzkVHZoeztnhrxR9e8omOmO9pKpYK0Fs3EoEWmaCTPmNUUA9AGV+2PP3BRlp dHJNFuWl0vQp8JBRt2Pd0rRF8/YVAxDVzx4c2PVoFPF+DrlhQCAeZwR6E3DrA+W7jJz6 soQ5rWo7v3GPBGozB1n0SOczjkNq852vKCn4o8cqlRnexpmMj6Fd7I7rnUmLfbFNLioi hlKHrsLz34aLYJ9ut8iiB22WhPVQBE1KtiqR4VZecConkQJJeoD7hJFHo1ljN69xkjnT EvZLVxSBail4IbeMzj5gHfCWpZoyDndVxTBau9nlv1MvP+mlGu4KEb8MoFr/Kqf09Bp2 N+zA== X-Gm-Message-State: ALoCoQlzuSQgvDAB6ZwmBddJVXs/5Of/wkzeHHyO/Oqh6dgGm95Q6BXEUQcUyEoQoJtuvf+SwYAT X-Received: by 10.180.12.238 with SMTP id b14mr13438005wic.16.1400238722325; Fri, 16 May 2014 04:12:02 -0700 (PDT) Received: from localhost ([2a01:348:1a2:1:a288:b4ff:fe8a:77d8]) by mx.google.com with ESMTPSA id ho2sm2800973wib.15.2014.05.16.04.12.00 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 16 May 2014 04:12:00 -0700 (PDT) To: Wael Nasreddine , notmuch@notmuchmail.org Subject: Re: [PATCH v2] Enable Travis-CI as a backup continuous integration service. In-Reply-To: References: <1400108004-26955-1-git-send-email-wael.nasreddine@gmail.com> <1400108004-26955-2-git-send-email-wael.nasreddine@gmail.com> User-Agent: Notmuch/0.18 (http://notmuchmail.org) Emacs/24.3.1 (x86_64-pc-linux-gnu) From: David Edmondson Date: Fri, 16 May 2014 12:11:52 +0100 Message-ID: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2014 11:12:09 -0000 --=-=-= Content-Type: text/plain On Thu, May 15 2014, Wael Nasreddine wrote: > It is fragile, but unfortunately there's no way (As far as I know) > around this problem. Travis-CI is currently running Ubuntu Precise > (12.04) and they have plans to update to Trusty[0] but it's going to take > them some time. Please forgive my ignorance. What is the place from which you are grabbing these packages? It doesn't seem to be part of the Ubuntu repositories. Is there no backports or security-updates repository for Ubuntu 12.04? I'm really asking whether there is a way to use the standard Ubuntu repositories to get the packages rather than downloading them directly. >> - What happens when those are no longer the right version numbers? > I can host the files in a Github repository if that would work better? I > am not very concerned about security in this case because Travis runs in > an isolated disposable VM created for the build and destroyed > afterwards. I have no strong preference. If they aren't coming from the standard repositories then it's all just slightly different versions of bad :-) >> - What happens when those versions are already provided by the standard >> repository? > > When #2046[0] is fixed by the Travis-CI team, our travis.yml will be > updated to work accordingly. Presume that you have lost interest in notmuch. How will we know that this has happened? >> - What happens if travis runs start happening on (say) an arm64 machine? > > Travis is currently running amd64[1] and I don't think they have plans > to change that, in fact I heard that they have plans to support more > architectures configurable in .travis.yml Your two statements seem contradictory here. >> I realise that you might answer "I will keep this up to date", but we >> have to worry about what happens if you lose interest and wander away. > > Absolutely, I understand your point and no one can guarantee > maintainer-ship. I can modify my patch and add documentation (comments > in the yaml file) about what each flag does, where can you documentation > about it and of course details about the hack. Would that be helpful? Comments explaining the need to grab the packages directly would be the absolute minimum requirement, I think. Include a pointer to the travis issue that you mentioned. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iKYEARECAGYFAlN18nhfFIAAAAAALgAoaXNzdWVyLWZwckBub3RhdGlvbnMub3Bl bnBncC5maWZ0aGhvcnNlbWFuLm5ldDc1M0Y5NDJDMEExNjc3MDE4OURGMUYyMDY5 RUNEMEFCRjA0OTY1MTYACgkQaezQq/BJZRbmWwCfeHJ1lc20hYbQcEyFwuSxgGXf xi4AnRjeYXiADpkNC4sJMQhLhgHCaq8g =dMs9 -----END PGP SIGNATURE----- --=-=-=--