Date: Thu, 03 Jan 2013 09:52:24 -0600 From: Larry Rosenman <ler@lerctr.org> To: <rm@freebsd.org> Cc: freebsd-ports-bugs@freebsd.org, rm@freebsd.org, dan@langille.org Subject: Re: ports/172600: [PKGNG]sysutils/bacula-client & sysutils/bacula-server conflict and shouldn't Message-ID: <b9ab1d9a6481192685a164a194017da6@webmail.lerctr.org> In-Reply-To: <201301031245.r03Cj8fm045924@freefall.freebsd.org> References: <201301031245.r03Cj8fm045924@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2013-01-03 06:45, rm@FreeBSD.org wrote: > Synopsis: [PKGNG]sysutils/bacula-client & sysutils/bacula-server > conflict and shouldn't > > State-Changed-From-To: feedback->open > State-Changed-By: rm > State-Changed-When: Thu Jan 3 12:45:08 UTC 2013 > State-Changed-Why: > Hello Larry. Does it still the case after recent bacula-ports > changes? > Could you please verify and report back? Thanks. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=172600 ===> Running ldconfig /sbin/ldconfig -m /usr/local/lib ===> Registering installation for bacula-client-5.2.12 Installing bacula-client-5.2.12...pkg: bacula-client-5.2.12 conflicts with bacula-server-5.2.12 (installs files into the same place). Problematic file: /usr/local/man/man8/bacula-fd.8.gz *** [fake-pkg] Error code 70 Stop in /usr/ports/sysutils/bacula-client. *** [install] Error code 1 Stop in /usr/ports/sysutils/bacula-client. ===>>> Installation of bacula-client-5.2.12 (sysutils/bacula-client) failed ===>>> Aborting update Terminated ===>>> You can restart from the point of failure with this command line: portmaster <flags> sysutils/bacula-client # svn info Path: . Working Copy Root Path: /usr/ports URL: svn://svn.freebsd.org/ports/head Repository Root: svn://svn.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 309892 Node Kind: directory Schedule: normal Last Changed Author: rm Last Changed Rev: 309892 Last Changed Date: 2013-01-03 09:46:33 -0600 (Thu, 03 Jan 2013) # Yes, it still seems to be broken, there is a pending PR to fix it, but AFAIK it has NOT been committed yet.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b9ab1d9a6481192685a164a194017da6>