Return-Path: X-Original-To: distix@pieni.net Delivered-To: distix@pieni.net Received: from yaffle.pepperfish.net (yaffle.pepperfish.net [88.99.213.221]) by pieni.net (Postfix) with ESMTPS id 4AF4C43090 for ; Mon, 2 Apr 2018 06:05:40 +0000 (UTC) Received: from platypus.pepperfish.net (unknown [10.112.101.20]) by yaffle.pepperfish.net (Postfix) with ESMTP id CD4CE417C7 for ; Mon, 2 Apr 2018 07:05:39 +0100 (BST) Received: from ip6-localhost.nat ([::1] helo=platypus.pepperfish.net) by platypus.pepperfish.net with esmtp (Exim 4.80 #2 (Debian)) id 1f2sb5-00030L-Oz; Mon, 02 Apr 2018 07:05:39 +0100 Received: from [10.112.101.21] (helo=mx3.pepperfish.net) by platypus.pepperfish.net with esmtps (Exim 4.80 #2 (Debian)) id 1f2sb4-000307-6L for ; Mon, 02 Apr 2018 07:05:38 +0100 Received: from mail.steve.org.uk ([176.9.183.102] helo=ssh.steve.org.uk) by mx3.pepperfish.net with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1f2sb2-0007yn-0C for ick-discuss@ick.liw.fi; Mon, 02 Apr 2018 07:05:38 +0100 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=steve.org.uk; s=20150726; h=References:In-Reply-To:Message-ID:Date:Subject: From:Cc:To:Resent-To:Resent-Message-ID:Resent-Date:Resent-From:Sender: Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Sender:Resent-Cc:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=JMsJEeOy4IxGf24JJ+D424q0ncB4wpwXBKXDYb3ZzHI=; b=ql4G/XPVNxz3cbTbeYX3C23uJQ gzUbBbeDLWHSoz/0JpLPZTNlB1MjTNEdIzCYALrksHuuzOhkjPTbEmgy7BfBIkLJl/K4zouw3+dzT 6a8B0Em81vDUkcOAf1Ge27lVsh8WY22w9e4Plvr1+J0TKL01WTRSiRdccDJNNm8JWeWE=; Received: from steve by ssh.steve.org.uk with local (Exim 4.89) (envelope-from ) id 1f2sau-0005Bs-Vg for ick-discuss@ick.liw.fi; Mon, 02 Apr 2018 06:05:29 +0000 Resent-From: Steve Kemp Resent-Date: Mon, 2 Apr 2018 06:05:28 +0000 Resent-Message-ID: <20180402060528.2aykbpvg4dfhr4vo@steve.org.uk> Resent-To: ick-discuss@ick.liw.fi To: ick-discuss@ick.liw.fi Cc: From: Steve Kemp Date: Sun, 01 Apr 2018 14:44:50 +0000 Message-ID: <1522593890.18807.1@ssh.steve.org.uk> In-Reply-To: <1522593545.2971.15.camel@liw.fi> References: <1522571699.2971.5.camel@liw.fi> <1522581877.10476.1@ssh.steve.org.uk> <1522593545.2971.15.camel@liw.fi> X-added-header: steve.org.uk X-Pepperfish-Transaction: 5283-2d25-b877-18c5 X-Spam-Score: 0.5 X-Spam-Score-int: 5 X-Spam-Bar: / X-Scanned-By: pepperfish.net, Mon, 02 Apr 2018 07:05:38 +0100 X-Spam-Report: Content analysis details: (0.5 points) pts rule name description ---- ---------------------- -------------------------------------------------- 2.5 PPF_GTLD_LONG Long gTLD, probably cheap throw-away domain -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0003] 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-ACL-Warn: message may be spam X-Scan-Signature: 0b3defc877126cf9a9969fd77535823e Subject: Re: What's needed before ick is ready for others to use? X-BeenThere: ick-discuss@ick.liw.fi X-Mailman-Version: 2.1.5 Precedence: list List-Id: discussions about the ick CI system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ick-discuss-bounces@ick.liw.fi Errors-To: ick-discuss-bounces@ick.liw.fi > The versions of cliapp (python-, python3-) on code.liw.fi work > simultanously for me. There's an older version in stretch that > conflicts with python3-cliapp from code.liw.fi, however. I think. > Haven't tested recently. That probably explains my situation, apart from an abortive effort earlier in the day I've been testing on stretch. > > The ansible role helps, but the random start-scripts in the top-level > > are a distraction. > > Which scripts do you mean? These two, mostly the latter: /run-debug /run-artifact-store-debug > > > > I suspect there is a security problem with the artifact server, but > > despite reading the architecture guide I'm missing the ability to > > confirm it. > > Er, yes, I think you're right. The paths should be sanitised. Thanks > for pointing that out, I will fix asap. No problem. If I thought it were widely used I'd have made more effort to confirm and notified privately. > I'm sorry you failed to get ick working, but I'm glad to hear you > tried. If you're willing to try again and tell me more about what > doesn't work, I would be most grateful. I'll keep going, it is an interesting project. Steve -- https://www.steve.org.uk/ _______________________________________________ ick-discuss mailing list ick-discuss@ick.liw.fi https://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/ick-discuss-ick.liw.fi