From owner-freebsd-ports@freebsd.org Mon Feb 20 23:14:23 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A8693CE64BD for ; Mon, 20 Feb 2017 23:14:23 +0000 (UTC) (envelope-from dewaynegeraghty@gmail.com) Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6FB7D1012; Mon, 20 Feb 2017 23:14:23 +0000 (UTC) (envelope-from dewaynegeraghty@gmail.com) Received: by mail-it0-x22b.google.com with SMTP id 203so87429657ith.0; Mon, 20 Feb 2017 15:14:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=4zCdIEfFXJJmUkLXLkJPxoswHJBXwdPQUep2OUTRtXk=; b=UP10TrI52mIKj1sp0pdl8eNtHcSgATYeDt77r3iGcqwTppBqASiz8+mr/RRd8Q3cui mjs4W4ke2C6wGw9vtOX0OZHkH/vKdEd/dJDdIOzqPcQK/uy3ELqvZj4zP31NeT/jMNg4 jEufv6G4knVEQpjxnfzeKeT5wfaEdC3ruwjH5hNHhe2amkMCn6wQTdf5TuAUUGaEd7Ge C6F++oA/nPAY+AVna0Fwg1C/gUDEdOtHvcLjnFmVHrWvynU53FZXk0sN/tkWQzYNKdnK 3Fgv84m1kJ7i7QcJdYoc5yfLBzVT3t/1NRPge6mHjWYr0tijT6lLte3HAnQMw1RjDrRx 26cw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=4zCdIEfFXJJmUkLXLkJPxoswHJBXwdPQUep2OUTRtXk=; b=dK1C8NXwI/2qXhaK/WVsF0tfDscU/OM48ZiS0CmNkRIDI0tx3QzwK1AorE9Vwlcuzp mKpdNC1LZoACiKA/Ts/4EXBzJkYo+mNkAEl1TLU4DRtqVT7ctYyGCZM9UzaGUCnxsH9/ dmHZtqJivuDy1DbjPGKcFg9Kl8qzAeW2z0ix/ePdH97CRjl6PwVqDK5lgBY6CVpGhcTZ ThOViepr+bifsQnV2WiFaXvXeqRLl4agfmUow1icqZdJ/ukWbtj4W9r7fVH60/Pw4Ayz FcHBfigDG1Is6GoVoAgvvXSWqibkEd267V2xitGlfqlZIw7VrR2+aaJXS5jSEl2V9/Yo CNcQ== X-Gm-Message-State: AMke39l13eyetXgw9A8yq88buC0hR8b/a6CX7fdeButOJu/ar8tZWxOxKgQomuXVQFufkFYCm5mFxcliZbwFew== X-Received: by 10.107.48.143 with SMTP id w137mr655119iow.144.1487632462854; Mon, 20 Feb 2017 15:14:22 -0800 (PST) MIME-Version: 1.0 Received: by 10.79.29.130 with HTTP; Mon, 20 Feb 2017 15:13:52 -0800 (PST) In-Reply-To: <20170220204856.GA12261@doctor.nl2k.ab.ca> References: <20170220161109.GA40515@doctor.nl2k.ab.ca> <20170220175546.BA9BB48A1@freefall.freebsd.org> <20170220195729.GA5512@doctor.nl2k.ab.ca> <20170220204856.GA12261@doctor.nl2k.ab.ca> From: Dewayne Geraghty Date: Tue, 21 Feb 2017 10:13:52 +1100 Message-ID: Subject: Re: devel/libevent shopstopper To: The Doctor Cc: Kevin Oberman , Jan Beich , FreeBSD Ports ML Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Feb 2017 23:14:23 -0000 On 21 February 2017 at 07:48, The Doctor wrote: > On Mon, Feb 20, 2017 at 12:35:41PM -0800, Kevin Oberman wrote: > > On Mon, Feb 20, 2017 at 11:57 AM, The Doctor > > wrote: > > > > > On Mon, Feb 20, 2017 at 05:55:46PM +0000, Jan Beich wrote: > > > > The Doctor writes: > > > > > > > > > We have a big one!! > > > > > > > > > > Libevent compiles but does not install > > > > > > > > > > ===> Installing for libevent-2.1.8 > > > > > ===> Checking if libevent already installed > > > > > ===> Registering installation for libevent-2.1.8 as automatic > > > > > Installing libevent-2.1.8... > > > > > pkg-static: libevent-2.1.8 conflicts with libevent2-2.1.8 (installs > > > > > files into the same place). Problematic file: > > > > > /usr/local/bin/event_rpcgen.py > > > > > *** Error code 70 > > > > > > > > > > Stop. > > > > > make[1]: stopped in /usr/ports/devel/libevent > > > > > *** Error code 1 > > > > > > > > > > Stop. > > > > > make: stopped in /usr/ports/devel/libevent > > > > > > > > > > ===>>> Installation of libevent-2.1.8 (devel/libevent) failed > > > > > ===>>> Aborting update > > > > > > > > > > ===>>> Update for devel/libevent failed > > > > > ===>>> Aborting update > > > > > > > > How did you invoke the build? portmaster and portupgrade are > supposed to > > > > look into /usr/ports/MOVED before proceeding. If they don't then > you're > > > > probably treading the unsupported territory[1] or encountered a bug. > > > > > > My sequence is > > > > > > pkg update -f > > > portsnap fetch update > > > portmaster -a > > > > > > Am I doing something wrong? > > > > > > > If you are building from ports, I'm not clear on why you do 'pkg update > > -f', but it should not hurt. > > > > Before running "portmaster -a", you should run "portmster -o > devel/libevent > > devel/libevent2". > > > > Just looking quickly at portmaster, it appears to deal with deleted ports > > and ports moved to a different location in the tree, but it does not look > > to me like it handles renamed ports properly. If someone who is better at > > shell scripting than I am wants to look at the code after line 1100, > maybe > > this could either be fixed or added. > > Is this a portmaster issue? > > > -- > > Kevin Oberman, Part time kid herder and retired Network Engineer > > E-mail: rkoberman@gmail.com > > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > > -- > Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@ > nl2k.ab.ca > Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist > rising! > http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism > God is dead! Yahweh lives! Jesus his only begotten Son is the Risen > Saviour!! > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > Unlikely to be a portmaster issue. If you look inside /usr/ports/UPDATING you're find some useful references to the way that portmaster handles name changes and John's "portmaster -o" advice is correct; its easy to miss that point in the man page ;) Perhaps its just a timing issue but both libevent2 and libcheck name changed broke our overnight builds. Unfortunately we didn't realise that we had a dependency until databases/memcached barfed. So we need to check /usr/ports/UPDATING and MOVED against a previous build to minimise that liklihood and catch dependencies. Upside is that we've just completed testing of synth, and decided to move the development servers to it. A recent post (from Bapt@) reaffirmed that the changes to /usr/ports is likely to break portmaster and other tools due to flavour's same origin. So rather than continue to rely upon a previously advocated tool, which is well suited to our very narrow purpose, its time to move. For those interested in synth but skittish: 1. install synth; read the manual 2. synth configure which places the synth.ini file in /usr/local/etc/synth and for testing purposes try 3. synth just-build $category/$portname; Example: synth just-build devel/check devel/libevent ftp/curl 4. Examine your logs in /var/log/synth Particularly 00_last_results.log and 02_failure_list.log 5. Examine your new packages in /var/synth/live_packages/All Gotchas: if you have complex make.conf file that pulls in other files, you will need to concatenate them into the one make.conf. If you have home grown build systems like we do, that have used portmaster since around 2005, its a big deal to change. We're looking forward to this incremental change. And if you use jails extensively, synth runs happily in a jail too - but this was against John Marinos advice, however we have strict functional separation here.