Date: Tue, 5 Apr 2016 16:03:11 +0000 From: Brad Davis <brd@FreeBSD.org> To: Matthew Seaman <matthew@FreeBSD.org> Cc: freebsd-pkg@freebsd.org Subject: Re: FreeBSD Port: ports-mgmt/pkg Message-ID: <20160405160311.GB1875@corpmail.liquidneon.com> In-Reply-To: <5703E001.5020007@FreeBSD.org> References: <CAKw-smCs2YycijBzAbwKypCtyCikL3k9kDVbSLZSOTUOh7D25g@mail.gmail.com> <20160405034626.GA1875@corpmail.liquidneon.com> <CAKw-smDu9%2BDu1rLYPQb1G09aqODY_oc%2BXq29qCQT%2B12P-K=bPA@mail.gmail.com> <5703E001.5020007@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 05, 2016 at 04:55:45PM +0100, Matthew Seaman wrote: > On 2016/04/05 11:28, Zsolt Ero wrote: > > I don't know how those tools internally check the state of packages, > > but anyone who self manages a server usually writes a long line of > > "pkg install -y pkg1 pkg2 pkg3" in a script. I would think that 99% of > > server deployment scripts are structured like this. > > > > Those lines are used in the sense of "make sure that pkg1, pkg2 and > > pkg3 are all installed after this command". Now the new change totally > > breaks this behaviour. > > > > Also, it breaks convention with known package managers from OS X or > > the linux world, where ... install is usually used as "make sure that > > ... is installed". > > > > Even if FreeBSD believes that such a huge change is somehow justified > > at a minor point release, it should be clearly communicated with the > > community. I would strongly recommend going back to the pre-1.7 way of > > "make sure that ... is installed" behaviour. > > > > Since this is such a fresh change, I believe there will be many more > > user reports coming in from broken install scripts soon. > > Just a 'me too': > > ==> sys-app-1: Error: Execution of '/usr/local/sbin/pkg install -qy > nagios-plugins' returned 70: > ==> sys-app-1: Error: > /Stage[main]/Nrpe::Install/Package[nagios-plugins]/ensure: change from > absent to present failed: Execution of '/usr/local/sbin/pkg install -qy > nagios-plugins' returned 70: > > Puppet gets all confused now when it tries to install something that's > already installed. I'd much prefer it if the exit code in that > situation was 'success.' Can I see the relevent section of your puppet manifest? Regards, Brad Davis
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160405160311.GB1875>