From owner-freebsd-ports@FreeBSD.ORG Tue Jul 22 17:43:46 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B9D6F545; Tue, 22 Jul 2014 17:43:46 +0000 (UTC) Received: from mail-yh0-x232.google.com (mail-yh0-x232.google.com [IPv6:2607:f8b0:4002:c01::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6E2E320B5; Tue, 22 Jul 2014 17:43:46 +0000 (UTC) Received: by mail-yh0-f50.google.com with SMTP id v1so5333828yhn.23 for ; Tue, 22 Jul 2014 10:43:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=Ulkiy1hgP6ufKh9w7DBUPNKg+iysb83kURwI6sekaDk=; b=vlyAXywAteD8tKFhUBg+IcSjG9aRIXYA2F7PqGw64G1ScWc2w/3ohc5g6+CWsFXB56 cxqzJfEJp40O1BORRzo88quzd2MJmVBetIwHguou1lQW2AIfZ/+xXhKUNXJciE0ND+66 FYQTnXyCMgrXG28REIltPa3ywQCUZzlsCtV235K57ZUwBlrDJ0BFz2Rv8bd88HEopsoy 0WgML0BqhPqlgTiwzQpfA9IWvPrq4DqlvZT0aYcwTeeARyPopsNAw8p1Dxq97efPTW69 MNkFeaEcGWUHBo2LmdlKXGHb0esk9PhXr6ciVfGmwcB2DL0sY/LNa4aVrji07BU/U0EG uSGA== MIME-Version: 1.0 X-Received: by 10.236.231.178 with SMTP id l48mr6622911yhq.143.1406051025589; Tue, 22 Jul 2014 10:43:45 -0700 (PDT) Sender: antoine.brodin.freebsd@gmail.com Received: by 10.170.164.197 with HTTP; Tue, 22 Jul 2014 10:43:45 -0700 (PDT) In-Reply-To: <53CE9AD6.6040201@gmx.de> References: <53CE846E.8090800@foobar.org> <53CE9AD6.6040201@gmx.de> Date: Tue, 22 Jul 2014 19:43:45 +0200 X-Google-Sender-Auth: BRC5jblEz4mKxCv2X-Cx6OSicnI Message-ID: Subject: Re: mass commit needed: python breakage in pkgng repo From: Antoine Brodin To: freebsd-ports Content-Type: text/plain; charset=UTF-8 Cc: "portmgr@freebsd.org Management Team" , Nick Hilliard X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jul 2014 17:43:46 -0000 On Tue, Jul 22, 2014 at 7:09 PM, olli hauer wrote: >>>>On 2014-07-22 17:34, Nick Hilliard wrote:> sysutils/py-salt has been broken for the last couple of weeks. The >>>>> resulting package didn't include the python egg info directory and as a >>>>> result, py-salt crashed on startup. There a PR in bugzilla for this: >>>>> >>>>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191986 >>>>> >>>>>>From what I can tell, this problem has been fixed by this commit: >>>>> >>>>> http://svnweb.freebsd.org/ports?view=revision&revision=362364 >>>>> >>>>> So py-salt will need to be rebuilt in the freebsd pkgng repo, but because >>>>> the fix was in bsd.python.mk, the port will need to have PORTREVISION >>>>> bumped in order to flush out the broken version from the pkgng repo. >>>>> >>>>> I've attached a list of other ports which may also be broken (i.e. ports >>>>> whose makefiles include the text USE_PYDISTUTILS but not >>>>> PYDISTUTILS_AUTOPLIST). Some of these ports may also need to rebuilt, but >>>>> without testing each one of them individually, it may not be be possible to >>>>> tell which. >>>>> >>>>> Could someone consider doing a mass commit to each of these ports to bump >>>>> PORTREVISION so that any potential breakage is flushed out of the pkg repos? >>>>> > > Sorry, my mobile has taken the discussion out of list ... > >>>>> isn't it easier to bump python instead ? >>>> yep sure would, but that will force a rebuild of ~2700 ports instead of 300. > >>> I suspect even more then the 2300 ports (depening ports also counting) but >>> this way really everything will be cached. >>> Dont know if the snap for weekly build was already taken if not it would be >>> an option >> >> tbh, i'm not familiar enough with the main repo build process + >> consequences to be able to assess how best to deal with this. >> > > Best to address this also to portmgr@ for decicission (added to CC) Hi, py-setuptools was updated on Wednesday 16th so all ports depending on it will be rebuilt during next bulk on the pkg builders. But I can still bump PORTREVISION on py-salt as for this specific port the missing egginfo is harmful? (for most other ports it's harmless) Cheers, Antoine