Re: devel/libcheck

On 02/06, Rainer Hurling wrote: > > Perhaps, this is something for UPDATING? > > > > No, UPDATING is for things humans need to do. portmaster should be able > > to figure this out from MOVED (which is mostly meant for machines). > > Of course, I know this about UPDATING. > > In this case wit

Re: devel/libcheck

Hi René, Am 06.02.2017 um 09:51 schrieb René Ladan: > 2017-02-06 9:18 GMT+01:00 Rainer Hurling >: > > Am 06.02.2017 um 07:29 schrieb Kurt Jaeger: > > Hi! > > > >> I just went to update my ports today on a machine, and there was a > >> conflict between

Re: devel/libcheck

2017-02-06 9:18 GMT+01:00 Rainer Hurling : > Am 06.02.2017 um 07:29 schrieb Kurt Jaeger: > > Hi! > > > >> I just went to update my ports today on a machine, and there was a > >> conflict between devel/check and devel/libcheck. > > > > It's more that libcheck was moved to check. > > > > According t

Re: devel/libcheck

Am 06.02.2017 um 07:29 schrieb Kurt Jaeger: > Hi! > >> I just went to update my ports today on a machine, and there was a >> conflict between devel/check and devel/libcheck. > > It's more that libcheck was moved to check. > > According to /usr/ports/MOVED: > > devel/libcheck|devel/check|2017-0

Re: devel/libcheck

Hi! > I just went to update my ports today on a machine, and there was a > conflict between devel/check and devel/libcheck. It's more that libcheck was moved to check. According to /usr/ports/MOVED: devel/libcheck|devel/check|2017-02-05|Rename to match upstream naming -- p...@opsec.eu

Re: devel/libcheck - fails: mtree

On Tue, Nov 04, 2008 at 07:07:24AM +0200, [EMAIL PROTECTED] wrote: > Hi, > > > The build which triggered this email is done under tinderbox-2.4.3, on > 7-STABLE on amd64, with tinderd_flags="-nullfs -plistcheck -onceonly" > and ccache support, with the "official" up-to-date Ports Tree, with the