Re: mesa libs issue

[Jack L.]

I cheated and just
pkg delete -f libglapi-17.0.3 libglesv2-17.0.3 libGL-17.0.3 gbm-17.0.3
libEGL-17.0.3
and portupgrade -fu all the pkgs it complained about after running pkg check -d

On Sun, May 14, 2017 at 3:56 PM, Jan Beich  wrote:
> Tatsuki Makino  writes:
>
>> Hello.
>> Does anyone reading this know how to upgrade more easily from below?
>>
>> #1. Collect mesa packages.
>> pkg version -L = | grep "?" | grep "17\.0\.3" | cut -w -f 1 > 
>> /tmp/mesa_pkg.txt
>>
>> #2. Collect the required origin that exists.
>> sh -c 'xargs pkg query %ro < /tmp/mesa_pkg.txt | sort -u | while read
>> o ; do [ -d "/usr/ports/$o" ] && echo "$o" ; done' > /tmp/mesa_req.txt
>>
>> #3. Forcibly delete mesa packages.
>> xargs pkg delete -f < /tmp/mesa_pkg.txt
>>
>> #4. Reinstall the required package.
>> xargs portmaster < /tmp/mesa_req.txt
>
> Maybe try the following:
>
>   $ pkg set -n dri:mesa-dri
>   $ pkg set -o graphics/dri:graphics/mesa-dri
>
>   $ pkg set -n libglapi:mesa-libs
>   $ pkg set -o graphics/libglapi:graphics/mesa-libs
>
>   $ pkg set -n libGL:mesa-libs
>   $ pkg set -o graphics/libGL:graphics/mesa-libs
>
>   $ pkg set -n gbm:mesa-libs
>   $ pkg set -o graphics/gbm:graphics/mesa-libs
>
>   $ pkg set -n libEGL:mesa-libs
>   $ pkg set -o graphics/libEGL:graphics/mesa-libs
>
>   $ pkg set -n libglesv2:mesa-libs
>   $ pkg set -o graphics/libglesv2:graphics/mesa-libs
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Which wine do I need?

[Thomas Mueller]

I see several different wine ports and would like to know which I need for 
amd64 and which I need for an i386 installation.

from David Naylor:

> On Saturday, 13 May 2017 08:16:55 Thomas Mueller wrote:
> > I see several different wine ports and would like to know which I need for
> > amd64 and which I need for an i386 installation.

> > I don't really want i386-wine as such, since I would install wine on i386
> > and could then mount this partition at /compat/i386 to run from amd64,
> > while retaining the ability to run from straight i386.

> This is effectively what i386-wine does: it bundles the required 32-bit
> libraries from a i386 host/environment and packages them such that they can
> run on an amd64 machine.

> > Am I correct that I would build wine (or wine-devel) on i386 and then
> > install wine or wine-devel on amd64?

> Correct, you should use the same port for both i386 and amd64, however if you
> are running Windows programs from /compat/i386 then there is no need to
> install wine on the amd64 host (unless you want to run 64-bit programs).

> > Am I better off doing this on FreeBSD 11-STABLE or on 12-HEAD?

> Normally CURRENT doesn't cause issues with wine, however STABLE will more,
> well, more stable.  I wouldn't base the decision of CURRENT/STABLE on whats
> best for Wine.  We do, however, need more people to test CURRENT.

My thought for building FreeBSD 11-STABLE for i386 is being better able to run 
wine from amd64, either HEAD or STABLE.

I think there might be problems using wine on i386 HEAD from 11-STABLE amd64?

Tom

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: mesa libs issue

[Jan Beich]

Tatsuki Makino  writes:

> Hello.
> Does anyone reading this know how to upgrade more easily from below?
>
> #1. Collect mesa packages.
> pkg version -L = | grep "?" | grep "17\.0\.3" | cut -w -f 1 > 
> /tmp/mesa_pkg.txt
>
> #2. Collect the required origin that exists.
> sh -c 'xargs pkg query %ro < /tmp/mesa_pkg.txt | sort -u | while read
> o ; do [ -d "/usr/ports/$o" ] && echo "$o" ; done' > /tmp/mesa_req.txt
>
> #3. Forcibly delete mesa packages.
> xargs pkg delete -f < /tmp/mesa_pkg.txt
>
> #4. Reinstall the required package.
> xargs portmaster < /tmp/mesa_req.txt

Maybe try the following:

  $ pkg set -n dri:mesa-dri
  $ pkg set -o graphics/dri:graphics/mesa-dri

  $ pkg set -n libglapi:mesa-libs
  $ pkg set -o graphics/libglapi:graphics/mesa-libs

  $ pkg set -n libGL:mesa-libs
  $ pkg set -o graphics/libGL:graphics/mesa-libs

  $ pkg set -n gbm:mesa-libs
  $ pkg set -o graphics/gbm:graphics/mesa-libs

  $ pkg set -n libEGL:mesa-libs
  $ pkg set -o graphics/libEGL:graphics/mesa-libs

  $ pkg set -n libglesv2:mesa-libs
  $ pkg set -o graphics/libglesv2:graphics/mesa-libs
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: mesa libs issue

[David Wolfskill]

On Sun, May 14, 2017 at 10:14:33PM +, Tatsuki Makino wrote:
> Hello.
> Does anyone reading this know how to upgrade more easily from below?
> 

What I would do:

pkg delete -f libEGL-17.0.3 libGL-17.0.3 libglesv2-17.0.3 gbm-17.0.3 
libglapi-17.0.3 dri-17.0.3,2
portmaster -d graphics/mesa-libs graphics/mesa-dri
portmaster -ad

(Second step inserted because I found that if that's not done,
portmaster may try to update (e.g.) x11-toolkits/gtk30 before the mesa
stuff, not find the libraries that were deleted by the first step, then
whine & die.)

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
Let's hope that the successor to this so-called POTUS will be an improvement.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


signature.asc
Description: PGP signature

RE: mesa libs issue

[Tatsuki Makino]

Hello.
Does anyone reading this know how to upgrade more easily from below?

#1. Collect mesa packages.
pkg version -L = | grep "?" | grep "17\.0\.3" | cut -w -f 1 > /tmp/mesa_pkg.txt

#2. Collect the required origin that exists.
sh -c 'xargs pkg query %ro < /tmp/mesa_pkg.txt | sort -u | while read o ; do [ 
-d "/usr/ports/$o" ] && echo "$o" ; done' > /tmp/mesa_req.txt

#3. Forcibly delete mesa packages.
xargs pkg delete -f < /tmp/mesa_pkg.txt

#4. Reinstall the required package.
xargs portmaster < /tmp/mesa_req.txt
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

FreeBSD Port: consul-0.8.3

[Douglas Thrift via freebsd-ports]

Hello,

It looks like the "consul members" command is showing "unknown" in the
build command for consul 0.8.3.
-- 
Douglas William Thrift

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Which wine do I need?

[David Naylor]

Hi

On Saturday, 13 May 2017 08:16:55 Thomas Mueller wrote:
> I see several different wine ports and would like to know which I need for
> amd64 and which I need for an i386 installation.
> 
> I don't really want i386-wine as such, since I would install wine on i386
> and could then mount this partition at /compat/i386 to run from amd64,
> while retaining the ability to run from straight i386.

This is effectively what i386-wine does: it bundles the required 32-bit 
libraries from a i386 host/environment and packages them such that they can 
run on an amd64 machine.

> Am I correct that I would build wine (or wine-devel) on i386 and then
> install wine or wine-devel on amd64?

Correct, you should use the same port for both i386 and amd64, however if you 
are running Windows programs from /compat/i386 then there is no need to 
install wine on the amd64 host (unless you want to run 64-bit programs).  

> Am I better off doing this on FreeBSD 11-STABLE or on 12-HEAD?

Normally CURRENT doesn't cause issues with wine, however STABLE will more, 
well, more stable.  I wouldn't base the decision of CURRENT/STABLE on whats 
best for Wine.  We do, however, need more people to test CURRENT.  

Regards

signature.asc
Description: This is a digitally signed message part.

Re: mesa libs issue

[Walter Schwarzenfeld]

If there was an update with portsnap, the will no libEGL port anymore - 
it is moved. But the package is still installed and must be removed.


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: mesa libs issue

[Baho Utot]

On 5/14/2017 8:03 AM, Walter Schwarzenfeld wrote:

> Your source ports are broken

No! It is only needed remove libEGL, libGL, libglapi, gbm and 
libgelsv2 and dri with pkg delete -f.


And recompile all ports of the output of

pkg info -r mesa-libs.



He did not have libEGL in his ports source

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Regression in devel/py(27)-configargparse 0.12

[j...@ohlste.in]

Hello,

This is a runtime dependency for py-certbot. Trying to check 
certificates I get the following error:


# certbot renew --dryrun
An unexpected error occurred:
AttributeError: 'tuple' object has no attribute 'add'
Please see the logfile 'certbot.log' for more details.

# cat certbot.log
Traceback (most recent call last):
  File "/usr/local/bin/certbot", line 11, in 
load_entry_point('certbot==0.13.0', 'console_scripts', 'certbot')()
  File "/usr/local/lib/python2.7/site-packages/certbot/main.py", line 
738, in main

args = cli.prepare_and_parse_args(plugins, cli_args)
  File "/usr/local/lib/python2.7/site-packages/certbot/cli.py", line 
1072, in prepare_and_parse_args

helpful.add_deprecated_argument("--agree-dev-preview", 0)
  File "/usr/local/lib/python2.7/site-packages/certbot/cli.py", line 
726, in add_deprecated_argument

self.parser.add_argument, argument_name, num_args)
  File "/usr/local/lib/python2.7/site-packages/certbot/util.py", line 
440, in add_deprecated_argument

configargparse.ACTION_TYPES_THAT_DONT_NEED_A_VALUE.add(ShowWarning)
AttributeError: 'tuple' object has no attribute 'add'


Reverting to 0.11 fixes the issue.

--
Jim Ohlstein
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: graphics/mesa-libs ... issues

[Walter Schwarzenfeld]

If a package mesa-libs exists in 
/usr/local/poudriere/data/packages/jailname/All/ simple remove it..


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

How should we name node-js ports ?

[Rodrigo Osorio]

Hi,

I have a bunch of nodejs ports to add, most of them as dependencies,
and I wonder if we can find a naming standard like adding  'node' or
'node-js' prefix in the name ; I personally prefer 'node'.

As a result a port who install the node package xxx will be named 'node-xxx'

Does it sounds good to you ?

Thanks for your time,

-- rodrigo


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Standard way to run test target in specific port

[José G . Juanino]

El domingo 14 de mayo a las 13:25:00 CEST, Mathieu Arnold escribió:

Le 14/05/2017 à 11:13, José G. Juanino a écrit :

Hello FreeBSD ports!

I am porting a backup software (bup backup), and the upstream Makefile
has a "test" target. I find useful to make a port knob to allow run
such test (disabled by default). What is the best way to accomplish
that task? Is there any doc or "best practique" to watch for?



You do:

TEST_TARGET=   test

and then, you simply run:

make test

from the ports directory. Do not add options knobs for it.


Thanks for your response, I will do so. 


Regards


--
José G. Juanino


signature.asc
Description: PGP signature

Re: mesa libs issue

[Walter Schwarzenfeld]

> Your source ports are broken

No! It is only needed remove libEGL, libGL, libglapi, gbm and libgelsv2 
and dri with pkg delete -f.


And recompile all ports of the output of

pkg info -r mesa-libs.


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: mesa libs issue

[Baho Utot]

On 5/14/2017 7:38 AM, The Doctor wrote:

On Sat, May 13, 2017 at 08:50:15PM -0400, Baho Utot wrote:


On 05/13/17 20:29, The Doctor wrote:

On Sat, May 13, 2017 at 08:13:14PM -0400, j...@ohlste.in wrote:

Hello,

On 05/13/2017 07:54 PM, The Doctor wrote:

> Compressing man pages (compress-man)
===>>> Starting check for runtime dependencies
===>>> Gathering dependency list for graphics/mesa-libs from ports
===>>> Dependency check complete for graphics/mesa-libs

===>>> All >> graphics/mesa-libs (1/2)

===>  Installing for mesa-libs-17.0.4
===>  Checking if mesa-libs already installed
===>   Registering installation for mesa-libs-17.0.4 as automatic
Installing mesa-libs-17.0.4...
pkg-static: mesa-libs-17.0.4 conflicts with libEGL-17.0.3 (installs files into 
the same place).  Problematic file: /usr/local/include/EGL/egl.h
*** Error code 70

Stop.
make[1]: stopped in /usr/ports/graphics/mesa-libs
*** Error code 1

Stop.
make: stopped in /usr/ports/graphics/mesa-libs

===>>> Installation of mesa-libs-17.0.4 (graphics/mesa-libs) failed
===>>> Aborting update

===>>> Update for graphics/mesa-libs failed
===>>> Aborting update


And crash goes the msea-libs complie.

Can someone explain this?

pkg-static: mesa-libs-17.0.4 conflicts with libEGL-17.0.3 (installs
files into the same place).  Problematic file: /usr/local/include/EGL/egl.h


There is no /usr/ports/graphics/EGL available.


/usr/ports/graphics/libEGL

ls /usr/ports/graphics/libEGL
ls: /usr/ports/graphics/libEGL: No such file or directory




Your source ports are broken

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: mesa libs issue

[The Doctor]

On Sat, May 13, 2017 at 07:15:10PM -0700, David Wolfskill wrote:
> On Sat, May 13, 2017 at 05:54:10PM -0600, The Doctor wrote:
> > 
> > ===>  Installing for mesa-libs-17.0.4
> > ===>  Checking if mesa-libs already installed
> > ===>   Registering installation for mesa-libs-17.0.4 as automatic
> > Installing mesa-libs-17.0.4...
> > pkg-static: mesa-libs-17.0.4 conflicts with libEGL-17.0.3 (installs files 
> > into the same place).  Problematic file: /usr/local/include/EGL/egl.h
> > *** Error code 70
> > 
> > Stop.
> > make[1]: stopped in /usr/ports/graphics/mesa-libs
> > *** Error code 1
> >  
> > 
> > And crash goes the msea-libs complie.
> 
> Well, no.  The compile was fine; it's the installation that choked.
> 
> > Can someone explain this?
> > 
> 
> I managed -- eventually! -- to get through this by iterating through:
> 
> * pkg which /usr/local/include/EGL/egl.h
>   This informed me that the file had been installed by libEGL-17.0.3.
> 
> * pkg delete -f libEGL-17.0.3
> 
> * (re-do the attempt to build/install graphics/mesa-libs; find that it
> now whines about something else... re-do "pkg which"; "pkg delete -f"
> that package; lather, rinse, repeat)
> 
> The short of it comes down to the equivalent of:
> 
> * pkg delete -f libEGL-17.0.3 libGL-17.0.3 libglesv2-17.0.3 gbm-17.0.3 
> libglapi-17.0.3
> 
> (after which point mesa-libs-17.0.4 installed OK).
> 
> * pkg delete -f dri-17.0.3,2 
> 
> (after which point mesa-dri-17.0.4 installed OK).
> 
> 
> Caveat: This was using portmaster.  My attempt to use poudriere to build
> graphics/mesa-libs failed rather completely, as I noted earlier.  (Ref.
> .)
> 
> Peace,
> david

Here is to following your instructions that should be in the UPDATING file.

> -- 
> David H. Wolfskillda...@catwhisker.org
> Let's hope that the successor to this so-called POTUS will be an improvement.
> 
> See http://www.catwhisker.org/~david/publickey.gpg for my public key.



-- 
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
UK Stop Theresa MAy MT V2 and Impotent Corbyn, Vote Farron and LDEm!!
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: mesa libs issue

[The Doctor]

On Sat, May 13, 2017 at 08:50:15PM -0400, Baho Utot wrote:
> 
> 
> On 05/13/17 20:29, The Doctor wrote:
> > On Sat, May 13, 2017 at 08:13:14PM -0400, j...@ohlste.in wrote:
> >> Hello,
> >>
> >> On 05/13/2017 07:54 PM, The Doctor wrote:
> >>> > Compressing man pages (compress-man)
> >>> ===>>> Starting check for runtime dependencies
> >>> ===>>> Gathering dependency list for graphics/mesa-libs from ports
> >>> ===>>> Dependency check complete for graphics/mesa-libs
> >>>
> >>> ===>>> All >> graphics/mesa-libs (1/2)
> >>>
> >>> ===>  Installing for mesa-libs-17.0.4
> >>> ===>  Checking if mesa-libs already installed
> >>> ===>   Registering installation for mesa-libs-17.0.4 as automatic
> >>> Installing mesa-libs-17.0.4...
> >>> pkg-static: mesa-libs-17.0.4 conflicts with libEGL-17.0.3 (installs files 
> >>> into the same place).  Problematic file: /usr/local/include/EGL/egl.h
> >>> *** Error code 70
> >>>
> >>> Stop.
> >>> make[1]: stopped in /usr/ports/graphics/mesa-libs
> >>> *** Error code 1
> >>>
> >>> Stop.
> >>> make: stopped in /usr/ports/graphics/mesa-libs
> >>>
> >>> ===>>> Installation of mesa-libs-17.0.4 (graphics/mesa-libs) failed
> >>> ===>>> Aborting update
> >>>
> >>> ===>>> Update for graphics/mesa-libs failed
> >>> ===>>> Aborting update
> >>>
> >>>
> >>> And crash goes the msea-libs complie.
> >>>
> >>> Can someone explain this?
> >>
> >>pkg-static: mesa-libs-17.0.4 conflicts with libEGL-17.0.3 (installs
> >> files into the same place).  Problematic file: /usr/local/include/EGL/egl.h
> >>
> > 
> > There is no /usr/ports/graphics/EGL available.
> 
> 
> /usr/ports/graphics/libEGL

ls /usr/ports/graphics/libEGL
ls: /usr/ports/graphics/libEGL: No such file or directory

> 
> 
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

-- 
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
UK Stop Theresa MAy MT V2 and Impotent Corbyn, Vote Farron and LDEm!!
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Standard way to run test target in specific port

[Mathieu Arnold]

Le 14/05/2017 à 11:13, José G. Juanino a écrit :
> Hello FreeBSD ports!
>
> I am porting a backup software (bup backup), and the upstream Makefile
> has a "test" target. I find useful to make a port knob to allow run
> such test (disabled by default). What is the best way to accomplish
> that task? Is there any doc or "best practique" to watch for?
>

You do:

TEST_TARGET=   test

and then, you simply run:

make test

from the ports directory. Do not add options knobs for it.


-- 
Mathieu Arnold




signature.asc
Description: OpenPGP digital signature

Re: Standard way to run test target in specific port

[José G . Juanino]

El domingo 14 de mayo a las 11:13:25 CEST, José G. Juanino escribió:

Hello FreeBSD ports!

I am porting a backup software (bup backup), and the upstream Makefile 
has a "test" target. I find useful to make a port knob to allow run 
such test (disabled by default). What is the best way to accomplish 
that task? Is there any doc or "best practique" to watch for?


I am thinking in write something like this:


RUNTEST_DESC=   Run test suite # knob

.

.if ${PORT_OPTIONS:MRUNTEST}
post-build:
  ${GMAKE} ${MAKE_ARGS} -C ${WRKDIR}/${PORTNAME}-${PORTVERSION} test
.endif


But it seems very contrived and ugly.


You can find the full shar file in 219174 (with no test target  
deployed).


Hi again, I will try to answer to myself ...

I have defined the "RUNTEST" knob in "OPTIONS_DEFINE" variable, and 
after:


RUNTEST_VARS=   TEST_TARGET=test

The last line enable the "do-test" target properly when the knob is set 
(see bsd.port.mk system Makefile)


But I do not know how to invoke automatically that target when user just 
run "make". Indeed I am thinking if really is a good idea to force the 
execution of "make test" by mean of the knob ... In some other ports I 
am seeing, this is enterelly optional. 


Regards


--
José G. Juanino
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Issue with pkg upgrade on diskless workstation

[BERTRAND Joël]

Mark Linimon a écrit :

I am running a powerpc64 machine diskless but only with some awful hacks.
I can make them available if need be, but I hope that someone else has a
better recommendation for you.

mcl



Before the last pkg binary upgrade, this workstation ran fine. What kind 
of hack do you use ?


Best regards,

JB
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

FreeBSD Port: audio/HVSC-Update

[babyg1980s--- via freebsd-ports]

Sent from my LG Mobile


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Standard way to run test target in specific port

[José G . Juanino]

Hello FreeBSD ports!

I am porting a backup software (bup backup), and the upstream Makefile 
has a "test" target. I find useful to make a port knob to allow run such 
test (disabled by default). What is the best way to accomplish that 
task? Is there any doc or "best practique" to watch for?


I am thinking in write something like this:


RUNTEST_DESC=   Run test suite # knob

.

.if ${PORT_OPTIONS:MRUNTEST}
post-build:
   ${GMAKE} ${MAKE_ARGS} -C ${WRKDIR}/${PORTNAME}-${PORTVERSION} test
.endif


But it seems very contrived and ugly.


You can find the full shar file in 219174 (with no test target  
deployed).



Thanks for your help!


--
José G. Juanino
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Issue with pkg upgrade on diskless workstation

[Mark Linimon]

I am running a powerpc64 machine diskless but only with some awful hacks.
I can make them available if need be, but I hope that someone else has a
better recommendation for you.

mcl
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Issue with pkg upgrade on diskless workstation

[BERTRAND Joël]

Hello,

	I'm trying to install a new software (xvnc) on a diskless workstation 
running FreeBSD 11. Server runs NetBSD 7.0.2 and this diskless 
workstation ran like a charm for a long time.


	pkg update was done (of course without error) and upgrade stalls (for 
several hours) :


root@pythagore:~ # pkg upgrade
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
Checking for upgrades (915 candidates):   2%

	pkg process takes 100% of CPU and there is no network activity. I 
haven't found any solution to achieve upgrade.


Any idea ?

Best regards,

JB
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"