Re: Large builds with poudriere

[Fernando Apesteguía]

El jue., 20 may. 2021 14:45, Alexis Praga  escribió:

>
> Hi guys,
>
> I've recently been using poudriere to test news ports but this resulted in
> building two large ports, namely:
> - devel/llvm [1]
> - lang/rust [2]
>
> Now, lang/rust takes 2 hourse to compile. So testing for 13.0, 12.2 and
> 11.4 means around 6 hours in total, a lot of time for my desktop
> computer. Especially if the dependencies are upgraded later on.
>
> Do you have any tips to deal with such long build time ? Apart from
> have a dedicated server :)
>

Patience :-)

Package seeding in poudriere is a long awaited feature.


> Thanks,
>
>
> [1] For https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233010
> [2] For https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255233
>
> --
> Alexis Praga
> ___
> 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"

Re: Proposal of new port www/owncast

[Fernando Apesteguía]

On Tue, Apr 27, 2021 at 11:23 AM CTS - FreeBSD Team
 wrote:
>
> Hello!
>
> I just created my first FreeBSD port for the small self-hostable
> streaming server https://owncast.online written in Go.
>
> On my own poudriere package build server it build fine for FreeBSD 11
> and 12 (amd64). It installs fine and even runs afterwards.
>
> How am i supposed to go on from here? Should i just open an issue in
> the bugtracker with the patch and have a discussion there or is it
> better to present it here first and have the discussion about it here
> on this list?

You can either open a review in Phabricator: reviews.freebsd.org/
or create a PR in bugzilla: https://bugs.freebsd.org/bugzilla/

Cheers

>
> Bye
> --
> Markus Mann, CTS - FreeBSD Team
> WWW: https://cts-solutions.at/
> ___
> 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"

Re: Maintainership of cwm

[Fernando Apesteguía]

On Wed, Mar 24, 2021 at 7:26 AM Emil Engler  wrote:
>
> Hello freebsd-ports,
> I recently switched to FreeBSD as my daily driver after using OpenBSD with cwm
> for a bit over 6 months now. After installing cwm I got the notice that it is
> currently unmaintained and is looking for one so here I am :^)
> Unfortunately I have no prior experience with maintaining ports but I am
> willing to learn. Also the fact that cwm only updates every 6 months (Leah
> Neukirchens port even less) makes it probably easier maintaining due to the
> slow but steady update frequency.

Hi Emil,

Thanks for stepping up. Would you mind opening a PR[1] for that?

Cheers.

[1] https://bugs.freebsd.org/bugzilla/
>
> For questions feel free to reach back to me!
>
> P.S: I've been using *BSD systems, mostly OpenBSD, since mid-2019. As
> a Hobby C developer I am also familiar with the *BSD C library to some degree.
>
> Cheers,
> Emil Engler
> ___
> 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"

Re: Include commit 564133 in 2021Q1

[Fernando Apesteguía]

On Tue, Feb 16, 2021 at 1:33 PM Joachim Werner via freebsd-ports <
freebsd-ports@freebsd.org> wrote:

> Hello,
>
> I'm the port maintainer for games/bsdgames. Recently there were build
> errors because of the deprecated use of NO_WERROR, but a fix was
> committed in 564133.
> Unfortunately too late to make it into 2021Q1, which is why I keep
> getting pkg-fallout messages...
>
> Could someone please update 2021Q1 to include the commit?
> Thank you!
>

Done.

Thanks!


>
> Joachim
>
> ___
> 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"

Re: Erroneous lines in /usr/ports/MOVED

[Fernando Apesteguía]

On Fri, Feb 5, 2021 at 11:33 AM Milan Obuch  wrote:

> On Fri, 5 Feb 2021 09:59:46 +0100, Fernando Apesteguía
>  wrote:
>
> > On Thu, Feb 4, 2021 at 11:36 PM Milan Obuch 
> > wrote:
> >
> > > After updating ports tree now portmaster bails out on old gstreamer
> > > ports, now moved to gstreamer1 ones. I found there are some errors
> > > in MOVED file, which, at least for me, could be fixed using patch in
> > > attachment.
> > >
> >
> > Done in https://svnweb.freebsd.org/changeset/ports/564092
> >
> > Thanks!
> >
> >
> > >
> > > Maybe my fix is not the best, so I leave it for more experienced
> > > ones... but this is what worked for me.
> > >
> > > Regards,
> > > Milan
> > >
> >
>
> I did a bit more checks after I noticed there are similar errors on
> other gstreamer ports moved onto gstreamer1 ones.
>
> Please review (and possibly commit) patch in attachment.
>
> I did not notice them earlier because at the moment I was interested
> just in quick fix for what I have installed locally.
>

OK, I reviewed all gstreamer entries and they should be fixed now (
https://svnweb.freebsd.org/changeset/ports/564108)

Thanks again!


>
> Regards,
> Milan
>
___
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: Erroneous lines in /usr/ports/MOVED

[Fernando Apesteguía]

On Thu, Feb 4, 2021 at 11:36 PM Milan Obuch  wrote:

> After updating ports tree now portmaster bails out on old gstreamer
> ports, now moved to gstreamer1 ones. I found there are some errors in
> MOVED file, which, at least for me, could be fixed using patch in
> attachment.
>

Done in https://svnweb.freebsd.org/changeset/ports/564092

Thanks!


>
> Maybe my fix is not the best, so I leave it for more experienced
> ones... but this is what worked for me.
>
> Regards,
> Milan
> ___
> 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"

Re: graphics/openimageio fails to build

[Fernando Apesteguía]

On Thu, Jan 14, 2021 at 10:53 AM Fernando Apesteguía <
fernando.apesteg...@gmail.com> wrote:

>
>
> On Thu, Jan 14, 2021 at 10:48 AM Shane Ambler 
> wrote:
>
>> On 14/1/21 8:16 am, Torfinn Ingolfsen wrote:
>> > like so:
>> > FAILED:
>> src/libOpenImageIO/CMakeFiles/OpenImageIO.dir/__/jpeg2000.imageio/jpeg2000input.cpp.o
>> ...
>> > fatal error: too many errors emitted, stopping now [-ferror-limit=]
>> > 20 errors generated.
>> ...
>> > ports tree updated today. This on
>> > root@kg-core2# uname -a
>> > FreeBSD kg-core2.kg4.no 11.4-RELEASE-p5 FreeBSD 11.4-RELEASE-p5 #0:
>> > Tue Dec  1 11:46:55 UTC 2020
>> > r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64
>> >
>> > Any more info I can provide?
>> >
>>
>> I haven't run test builds for a while, I will look into it.
>>
>> Do you need openjpeg support? Normal jpeg support is always on, the
>> option for OPENJPEG is a separate library for jpeg2000 support.
>>
>
> I'm build testing right now. 27 packages to go. Mind you my poudriere jail
> is 11.4-RELEASE-p6 amd64. Ports updated today 2021-01-14 07:29:40.
>

It built successfully in poudriere with default options. I see this in the
log:

CMake Warning at src/jpeg2000.imageio/CMakeLists.txt:11 (message):
  Jpeg-2000 plugin will not be built

Are you building in a clean environment?

Cheers.


>
>>
>>
>> --
>> FreeBSD - the place to B...Software Developing
>>
>> Shane Ambler
>>
>> ___
>> 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"

Re: graphics/openimageio fails to build

[Fernando Apesteguía]

On Thu, Jan 14, 2021 at 10:48 AM Shane Ambler  wrote:

> On 14/1/21 8:16 am, Torfinn Ingolfsen wrote:
> > like so:
> > FAILED:
> src/libOpenImageIO/CMakeFiles/OpenImageIO.dir/__/jpeg2000.imageio/jpeg2000input.cpp.o
> ...
> > fatal error: too many errors emitted, stopping now [-ferror-limit=]
> > 20 errors generated.
> ...
> > ports tree updated today. This on
> > root@kg-core2# uname -a
> > FreeBSD kg-core2.kg4.no 11.4-RELEASE-p5 FreeBSD 11.4-RELEASE-p5 #0:
> > Tue Dec  1 11:46:55 UTC 2020
> > r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64
> >
> > Any more info I can provide?
> >
>
> I haven't run test builds for a while, I will look into it.
>
> Do you need openjpeg support? Normal jpeg support is always on, the
> option for OPENJPEG is a separate library for jpeg2000 support.
>

I'm build testing right now. 27 packages to go. Mind you my poudriere jail
is 11.4-RELEASE-p6 amd64. Ports updated today 2021-01-14 07:29:40.


>
>
> --
> FreeBSD - the place to B...Software Developing
>
> Shane Ambler
>
> ___
> 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"

Re: gmake can't find GNUmakefile, only Makefile?

[Fernando Apesteguía]

On Mon, Jan 4, 2021 at 1:45 PM Nuno Teixeira  wrote:

> Hello,
>
> I'm porting a c'++ program that  depends on gmake.
>
> upstream uses GNUmakefile instead of Makefile name.
>

Try:

MAKEFILE=  GNUmakefile


> Thats strange that gmake sees GNUmakefile when doing gmake in work/port but
> port itself fails with:
>
> ---
> gmake[2]: Entering directory
> '/usr/home/nunotex/Work/ports/cxxmatrix/work/port'
> gmake[2]: Makefile: No such file or directory
> gmake[2]: *** No rule to make target 'Makefile'.  Stop.
> gmake[2]: Leaving directory
> '/usr/home/nunotex/Work/ports/cxxmatrix/work/port'
> ===> Compilation failed unexpectedly.
> ---
>
> How do I tell gmake to find it?,
>
> Thanks,
>
> Nuno Teixeira
> ___
> 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"

Re: archivers/makeself adopted/updated!

[Fernando Apesteguía]

On Sat, Oct 24, 2020 at 3:20 PM Nuno Teixeira  wrote:

> Hello,
>
> A very nice program that was not updated for years.
>
> Please take a look at 250577
> 
>
> Thanks,
>

Done.

Thanks!

>
> Nuno Teixeira
> ___
> 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"

Re: Help with go based port (invalid flag in pkg-config --libs: -D_THREAD_SAFE )

[Fernando Apesteguía]

El mié., 23 sept. 2020 21:49, Matthias Fechner 
escribió:

> Dear all,
>
> I currently package a new gitaly version which is required for gitlab-ce
> 13.4.0.
>
> The current version I have now can be found here:
> https://gitlab.fechner.net/mfechner/Gitlab/-/tree/13.4/devel/gitaly
>
> But for this port there are a lot of upstream changes which causes now
> some problems compiling it.
>
> It seems that a new go dependency is added that requires libgit2 as a
> dependency.
>
> I used the following command to better see the error message:
> poudriere testport -p gitlab -j 121amd64 -i devel/gitaly
>
> In the shell I executed then:
> cd
>
> /wrkdirs/usr/ports/devel/gitaly/work/gitaly-cf359cb573106371a6026bd85c3145caabf8c06b-cf359cb573106371a6026bd85c3145caabf8c06b/
> gmake
>
> And then a tried the following:
> cd /root/go/pkg/mod/github.com/libgit2/git2go/v30@v30.0.5
> pkg-config --cflags --static -- libgit2
> pkg-config --libs --static -- libgit2
> go build github.com/libgit2/git2go/v30: invalid flag in pkg-config
> --libs: -D_THREAD_SAFE
>
> I think the problem is somehow related to the output of:
> pkg-config --libs --static -- libgit
>
> which shows:
> -L/usr/local/lib -lgit2 -lrt -pthread -lz -L/usr/local/lib -lssh2
> -L/usr/local/lib -lssl -L/usr/local/lib -pthread -lcrypto -pthread
> -lpcre -D_THREAD_SAFE -pthread
>
> The error message I was able to found in the log:
> go build github.com/libgit2/git2go/v30: invalid flag in pkg-config
> --libs: -D_THREAD_SAFE
>
> The full log is here:
>
> https://pkg.fechner.net/data/121amd64-gitlab/2020-09-23_11h17m24s/logs/errors/gitaly-13.4.0.log
>
> The log is really hard to read, as go executed several compiles at once.
>
> I tried to limit it to one thread using:
> GO_BUILDFLAGS+= "-x -p 1"
>
> but this does not work.
>
> I tried to add compiler:c11 to the use flags, but this does not help (it
> seems that pkgconfig is for sure required).
> It would be really great if someone could help me, fixing this problem
> so I can release the next gitlab-ce 13.4 upgrade.
>
> Thanks a lot.
>

I found this:

https://fipress.org/knowledge/invalid-flags-in-cgo-ldflags-pkg-config-or-invalid-flag-in-pkg-config

HTH


>
> Gruß
> Matthias
>
> --
>
> "Programming today is a race between software engineers striving to
> build bigger and better idiot-proof programs, and the universe trying to
> produce bigger and better idiots. So far, the universe is winning." --
> Rich Cook
>
>
> ___
> 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"

Re: games/devilutionx update: please commit

[Fernando Apesteguía]

On Tue, Mar 24, 2020 at 5:42 PM Nuno Teixeira  wrote:
>
> Hello,
>
> Could a commiter please look at 244722
> 
> (games/devilutionx update) and 244399
>  (games/cursive
> adoption)?

Done.

Thanks!
>
> Thanks,
>
> Nuno Teixeira
> ___
> 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"

Re: Should 'Reported by' reflect who/which system reported the port to be out-of-date?

[Fernando Apesteguía]

El sáb., 7 mar. 2020 21:50, Yuri  escribió:

> I got a feedback that such use of 'Reported by' might be incorrect.
>
>
> Opinions?
>

I don't know if it is incorrect, but I often use "Reported by: portscout".
Never had negative feedback.

Cheers


>
> Yuri
>
> ___
> 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"

Re: math/octave-forge-audio port

[Fernando Apesteguía]

On Sun, Jan 19, 2020 at 10:57 PM Montgomery-Smith, Stephen
 wrote:
>
> I am the maintainer of the math/octave-forge-audio port.  I am getting
> multiple reports of build errors from pkg-fallout@.  But I am unable to
> reproduce these errors.  Configure claims it cannot find RTMIDI.  But it
> does preinstall the audio/rtmidi port from packages before it tries to
> build octave-forge-audio.
>
> What are other people's experiences with this port?  I should add it
> only came operational very recently.
>
> If anyone else if having the same build error, can they send me their
> copy of config.log, which can be found in work/audio-2.0.0/src?

Try USES=pkgconfig

Cheers
>
> Thanks, Stephen
> ___
> 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"

Re: [multimedia/audacious-plugins] Fix playback at wrong tonality

[Fernando Apesteguía]

On Tue, Dec 31, 2019 at 5:25 AM  wrote:
>
>
> Howdy!
>
>  [CC'ing one of audacious developers whose email I was able to find, as
>   this really is an upstream issue]

Hi there!

Thanks for the heads up. Would you mind opening a PR[1]? Also,
ideally, this would be fixed upstream :-)

[1] https://bugs.freebsd.org/bugzilla/

>
>  I noticed that on a certain USB audio device that I have, audacious would
>  play songs too fast when the sound device is in BITPERFECT mode, while
>  mpv, for example, plays them at correct speed.
>
>  Turns out that this device supports only one samplerate (48.0 ksps), but
>  audacious fails to detect that, and plays the 44.1 ksps song anyway,
>  resulting in playback that is almost 9% too fast.
>
>  The attached patch for OSS4 plugin fixes that. Please review.
>  The 3% figure was chosen more or less arbitrarily, based on a random
>  Internet article [0].
>
>  Also, I would like to request the port maintainer to add a DBUS option,
>  enabling to compile the player and its plugins without Linux's dbus
>  dependency ("--disable-dbus" configure option does the trick, though
>  stops `audtool` from building as well).
>
> [0] https://cecm.sitehost.iu.edu/etext/acoustics/chapter1_pitch.shtml
>
> --
> [SorAlx]  ridin' VN2000 Classic LT
___
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: multimedia/shotcut

[Fernando Apesteguía]

On Wed, Nov 20, 2019 at 12:16 AM Andrew Johnson 
wrote:
>
> System: FreeBSD 12.1-STABLE r354452 GENERIC  amd64
> Ports: cur

It runs fine in 12.1-RELEASE:

https://www.dropbox.com/s/l9aumwz3hzz3q9t/screenshot.png?dl=0

Would it be possible to see a backtrace of the generated core?

>
> Symptom: Segmentation fault
>
> (gdb)
> (gdb) core shotcut.core
> [New LWP 101419]
> [New LWP 100883]
> [New LWP 101488]
> [New LWP 101489]
> [New LWP 101490]
> [New LWP 101491]
> [New LWP 101492]
> [New LWP 101493]
> [New LWP 101494]
> [New LWP 101495]
> Core was generated by `shotcut'.
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  0x0008006a6ab1 in ?? ()
> [Current thread is 1 (LWP 101419)]
>
>
> % shotcut
> Gtk-Message: 09:59:25.944: Failed to load module "appmenu-gtk-module"
> [Info   ]  Starting Shotcut version 19.10.20
> [Info   ]  Linux version
> [Info   ]  number of logical cores = 12
> [Info   ]  locale = QLocale(C, Default,
> Default)
> [Info   ]  install dir = "/usr/local/bin"
> [Info   ]  device pixel ratio = 1
> [Debug  ]  language "C"
> [Debug  ]  deinterlacer "onefield"
> [Debug  ]  external monitor ""
> [Debug  ]  GPU processing false
> [Debug  ]  interpolation "bilinear"
> [Debug  ]  video mode "atsc_720p_50"
> [Debug  ]  realtime true
> [Debug  ]  audio channels 1
> [Debug  ]  begin
> [Debug  ]  end
> [Debug  ]  begin
> [Info   ]  OpenGL context version 4 5
> [Debug  ]  begin
> [Warning]  mlt_repository_init: failed to dlopen
> /usr/local/lib/mlt/libmltavformat.so  (/usr/local/lib/libflite_cmu_us_a
> wb.so.1: Undefined symbol "usenglish_init")
> [Info   ]  decimal point .
> [Debug  ]  end
> [Debug  ]  begin
> [Debug  ]  end
> [Debug  ]  begin
> Shared object "libDeckLinkAPI.so" not found, required by "shotcut"
> [Warning]  [ 0x8078eba10] The DeckLink drivers not installed.
> [Debug  ]  end
> [Debug  ]  begin
> [Debug  ]  1
> [Debug  ]  1
> [Debug  ]  end
> [Debug  ]  begin
> [Debug  ]  "atsc_720p_50"
> [Debug  ]  setting to profile
> "atsc_720p_50"
> [Debug  ]  1
> [Debug  ]  1
> [Debug  ]  end
> [Debug  ]  begin
> [Debug  ]  begin true
> [Debug  ]  end
> [Debug  ]  begin
> [Debug  ]  end
> [Debug  ]  begin
> [Debug  ]  end
> [Debug  ]  begin true
> [Debug  ]  end
> [Debug  ]  begin
> [Debug  ]  end
> [Debug  ]  begin
> [Debug  ]  end
> [Debug  ]  begin true
> [Debug  ]  end
> [Debug  ]  begin
> [Debug  ]  end
> [Debug  ]  begin
> [Debug  ]  end
> [Debug  ]  begin true
> [Debug  ]  end
> [Debug  ]  begin
> [Debug  ]  end
> [Debug  ]  begin
> [Debug  ]  end
> [Debug  ]  begin true
> [Debug  ]  end
> [Debug  ]  begin
> [Debug  ]  end
> [Debug  ]  begin
> [Debug  ]  end
> [Debug  ]  begin true
> [Debug  ]  end
> [Debug  ]  begin
> [Debug  ]  end
> [Debug  ]  begin
> [Debug  ]  end
> [Debug  ]  end
> [Debug  ]  begin
> [Debug  ]  end
> [Debug  ]  begin
> [Debug  ]  end
> [Debug  ]  begin
> [Debug  ]  end
> [Debug  ]  begin
> [Debug  ]  end
> [Debug  ]  begin
> [Debug  ]  end
> [Debug  ]  begin
> Segmentation fault (core dumped)
>
> ___
> 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"

Re: [package - head-i386-default][graphics/hugin] Failed for hugin-2019.0.0_1 in build

[Fernando Apesteguía]

El sáb., 20 abr. 2019 10:27, Kubilay Kocak  escribió:

> On 20/04/2019 6:15 pm, Greg 'groggy' Lehey wrote:
> > I've received a number of these messages.  Based on the fact that they
> > seem to be a jail mismatch, I assume that this has nothing to do with
> > the port itself.  Can somebody confirm or deny this?  If I need to do
> > something, please explain.
> >
> > Greg
> >
> > On Friday, 19 April 2019 at  7:16:33 +, pkg-fall...@freebsd.org
> wrote:
> >> You are receiving this mail as a port that you maintain
> >> is failing to build on the FreeBSD package build server.
> >> Please investigate the failure and submit a PR to fix
> >> build.
> >>
> >> Maintainer: g...@freebsd.org
> >> Last committer: jbe...@freebsd.org
> >> Ident:  $FreeBSD: head/graphics/hugin/Makefile 498698
> 2019-04-12 06:36:31Z jbeich $
> >> Log URL:
> http://beefy11.nyi.freebsd.org/data/head-i386-default/p499228_s346255/logs/hugin-2019.0.0_1.log
> >> Build URL:
> http://beefy11.nyi.freebsd.org/build.html?mastername=head-i386-default=p499228_s346255
> >> Log:
> >>
> >> =>> Building graphics/hugin
> >> build started at Fri Apr 19 06:55:36 UTC 2019
> >> port directory: /usr/ports/graphics/hugin
> >> package name: hugin-2019.0.0_1
> >> building for: FreeBSD head-i386-default-job-02 13.0-CURRENT FreeBSD
> 13.0-CURRENT 1300018 i386
> >> maintained by: g...@freebsd.org
> >> Makefile ident:  $FreeBSD: head/graphics/hugin/Makefile 498698
> 2019-04-12 06:36:31Z jbeich $
> >> Poudriere version: 3.2.8-3-g02cc9753
> >> Host OSVERSION: 139
> >> Jail OSVERSION: 1300018
> >> Job Id: 02
> >>
> >> !!! Jail is newer than host. (Jail: 1300018, Host: 139) !!!
> >> !!! This is not supported. !!!
> >> !!! Host kernel must be same or newer than jail. !!!
> >> !!! Expect build failures. !!!
> >
>
> The actual failure is at the bottom of the log link referenced in the
> email:
>
> ld: error: src/hugin_base/libhuginbase.so.0.0: undefined reference to
> __atomic_load
>

Same error for cad/openvsp since some days ago. I tried to reproduce it in
a i386 vm on a 64 bit host but it didn't happen, so I assume this only
happens on a real i386 system.

Adding -latomic might help


> ___
> 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"

CFT japanese/man on arm and mips

[Fernando Apesteguía]

Hi there,

This patch[1] seems to fix the build problem of japanese/man. I
already tested in i386 and amd64, but can any in the list test in the
following platforms?

aarch64
armv6
armv7
mips

Thanks!

[1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235058
___
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: net-mgmt/ocsinventory-ng

[Fernando Apesteguía]

On Sat, Aug 11, 2018 at 1:15 AM Kurt Buff  wrote:
>
> I used it about 6-8 years ago, and it was pretty good then, but we
> moved on to commercial alternatives as a management decision.
>
> No idea if it's gotten better or worse since.
>
> Kurt
>
> On Fri, Aug 10, 2018 at 5:59 AM, Andrea Venturoli  wrote:
> > Hello.
> >
> > Is anyone using this software on FreeBSD?
> > The port is at 2.1.2, while 2.5 is out, so I guess it's unmantained.
> >
> > Is someone working on this?

Would you give this one a try?

https://people.freebsd.org/~fernape/patches/ocsinventory.svndiff

It builds on {10.4,11.1}{amd64,i386} and 12i386. Didn't test in other
combinations.

It's a bit difficult for me to test it at the moment.

> >
> > Do you have any alternative to suggest?
> >
> > I'm mainly interested in some inventoring the networks of my customers
> > (mainly PCs and Macs, with hardware data, serial numbers and installed
> > software); I've used OCS in the past and it's more or less what I'm looking
> > for.
> > The simpler, the better; GUI is not a requirement, as long as it stores data
> > in some sort of DB. Synchronous commands would be a big bonus.
> >
> >  bye & Thanks
> > av.
> > ___
> > 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"
___
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: has a framework change broken sysutils/google-compute-engine-oslogin?

[Fernando Apesteguía]

On Wed, Aug 8, 2018 at 7:40 AM Julian Elischer  wrote:
>
> On 8/8/18 1:02 pm, Julian Elischer wrote:
> > It says it can not find the file curl/curl.h which IS PRESENT as
> > /usr/local/include/curl/curl.h
> >
> > There are Makefile BROKEN annotations for this error in mips etc but
> > I'm seeing it now on amd64.
> >
> > I would think that all ports should have /usr/local/include in their
> > Include list but maybe not?
> >
> > is this something that is supplied by the framework?
> >
> >
> > ports tree checked out from a week ago and today... same issue.
> >
> >
> > there is no /usr/local/include in the failing command line...
> >
> > gmake[1]: Entering directory
> > '/usr/ports/sysutils/google-compute-engine-oslogin/work/compute-image-packages-20180611/google_compute_engine_oslogin'
> > g++ -O2 -pipe  -fstack-protector  -fPIC -I/usr/local/include/json-c
> > -c utils/oslogin_utils.cc -o utils/oslogin_utils.o
> > utils/oslogin_utils.cc:16:23: error: curl/curl.h: No such file or
> > directory
> >
> >
> > I'm guessing there should be but who's responsibility is it to put
> > it there?
>
> I got past it by adding (temporarily) the following to make.conf
>
> for some faiign g++ commands
> CFLAGS+-I /usr/local/include
>
> and for others
> LDFLAGS+=-L/usr/local/lib -I /usr/local/include
>
> but that stinks
>
> better suggestions welcome..

Is this what you are looking for?

USES=localbase

https://www.freebsd.org/doc/en/books/porters-handbook/uses-localbase.html

>
> >
> > (and where/how?)
> >
> >
> > Julian
> >
> >
> >
> > ___
> > 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"
___
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"

USE_WX for 3.1

[Fernando Apesteguía]

Hi,

We recently added x11-toolkits/wxgtk31 but we don't have support for
USE_WX=3.1 yet (maybe related to that we don't have
x11-toolkits/py-wxPython31)

Are there any plans to add support for this?

Thanks!
___
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: mysql80-client failes on FreeBSD 11.2 RC3

[Fernando Apesteguía]

El vie., 22 jun. 2018 13:50, Johan Hendriks 
escribió:

> hello all,
> I can not build mysql80-client on FreeBSD 11.2-RC3
> it errors out at the patch stage.
>

There's already a PR about it:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228788

Cheers


> root@mailstore01:/usr/ports/databases/mysql80-client # make
> ===>  License GPLv2 accepted by the user
> ===>   mysql80-client-8.0.11 depends on file: /usr/local/sbin/pkg - found
> ===> Fetching all distfiles required by mysql80-client-8.0.11 for building
> ===>  Extracting for mysql80-client-8.0.11
> => SHA256 Checksum OK for mysql-boost-8.0.11.tar.gz.
> /usr/ports/databases/mysql80-client/work/mysql-8.0.11/sql/sql_hints.yy.cc
> /usr/ports/databases/mysql80-client/work/mysql-8.0.11/sql/sql_hints.yy.h
> ===>  Patching for mysql80-client-8.0.11
> ===>  Applying FreeBSD patches for mysql80-client-8.0.11
> 1 out of 3 hunks failed--saving rejects to utilities/CMakeLists.txt.rej
> => FreeBSD patch patch-utilities_CMakeLists.txt failed to apply cleanly.
> => Patch(es)  patch-CMakeLists.txt patch-client_CMakeLists.txt
> patch-cmake_os_DragonFly.cmake patch-cmake_ssl.cmake
> patch-cmd-line-utils_libedit_chartype.h
> patch-cmd-line-utils_libedit_vi.c patch-include_CMakeLists.txt
> patch-include_my__compare.h patch-include_myisam.h
> patch-libmysql_CMakeLists.txt patch-man_CMakeLists.txt
> patch-mysys__ssl_my__default.cc patch-mysys__ssl_my__md5.cc
> patch-plugin_x_client_xconnection__impl.cc patch-scripts_CMakeLists.txt
> patch-share_CMakeLists.txt patch-sql-common_client.cc
> patch-sql_auth_sha2__password__common.cc patch-sql_mysqld.cc
> patch-sql_sys__vars.cc patch-storage_myisam_mi__dynrec.cc
> patch-support-files_CMakeLists.txt applied cleanly.
> *** Error code 1
>
> Stop.
> make: stopped in /usr/ports/databases/mysql80-client
> root@mailstore01:/usr/ports/databases/mysql80-client #
>
> The file utilities/CMakeLists.txt.rej contains the following
>
> @@ -87,4 +88,5 @@
>  ENDIF()
>
> +IF(FALSE)
>  MYSQL_ADD_EXECUTABLE(my_print_defaults my_print_defaults.c)
>  TARGET_LINK_LIBRARIES(my_print_defaults  mysys mysys_ssl)
>
> regards
> Johan
>
> ___
> 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"

Re: leptonica update

[Fernando Apesteguía]

On Sun, Jun 3, 2018 at 12:22 AM, Walter Schwarzenfeld
 wrote:
> Yes, I was wrong:
>
> The CONFLICTS_BUILD in leptonica means it would pick up the wrong
> "openjpeg.h" if openjpeg15 is installed.

Yes, that's basically the reason. Sorry if this caused any trouble.
Maybe an entry in UPDATING was in order.

>
>
> ___
> 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"

undefined reference to __atomic_compare_exchange

[Fernando Apesteguía]

Hi,

I'm trying to update a port (lang/ponyc), but it fails in different
combinations of FreeBSD versions and architectures. For instance:

10.4 amd64: FAIL
10.4 i386: FAIL
11.1 amd64: OK
11.1 i386: FAIL
12.1 i386: FAIL

The error is always:

build/release/libponyrt.a(pool.o): In function `pool_get':
src/libponyrt/mem/pool.c:(.text+0xbb): undefined reference to
`__atomic_compare_exchange'
build/release/libponyrt.a(pool.o): In function `ponyint_pool_free':
src/libponyrt/mem/pool.c:(.text+0x221): undefined reference to
`__atomic_compare_exchange'
src/libponyrt/mem/pool.c:(.text+0x26f): undefined reference to
`__atomic_compare_exchange'
build/release/libponyrt.a(pool.o): In function `ponyint_pool_thread_cleanup':
src/libponyrt/mem/pool.c:(.text+0x7ef): undefined reference to
`__atomic_compare_exchange'
src/libponyrt/mem/pool.c:(.text+0x8c0): undefined reference to
`__atomic_compare_exchange'
build/release/libponyrt.a(pool.o):src/libponyrt/mem/pool.c:(.text+0x900):
more undefined references to `__atomic_compare_exchange' follow
c++: error: linker command failed with exit code 1 (use -v to see invocation)
gmake[1]: *** [Makefile:817: build/release/libponyrt.tests] Error 1
gmake[1]: *** Waiting for unfinished jobs
build/release/libponyrt.a(pool.o): In function `pool_get':
src/libponyrt/mem/pool.c:(.text+0xbb): undefined reference to
`__atomic_compare_exchange'
build/release/libponyrt.a(pool.o): In function `ponyint_pool_free':
src/libponyrt/mem/pool.c:(.text+0x221): undefined reference to
`__atomic_compare_exchange'
src/libponyrt/mem/pool.c:(.text+0x26f): undefined reference to
`__atomic_compare_exchange'
build/release/libponyrt.a(pool.o): In function `ponyint_pool_thread_cleanup':
src/libponyrt/mem/pool.c:(.text+0x7ef): undefined reference to
`__atomic_compare_exchange'
src/libponyrt/mem/pool.c:(.text+0x8c0): undefined reference to
`__atomic_compare_exchange'
build/release/libponyrt.a(pool.o):src/libponyrt/mem/pool.c:(.text+0x900):
more undefined references to `__atomic_compare_exchange' follow
c++: error: linker command failed with exit code 1 (use -v to see invocation)
gmake[1]: *** [Makefile:817: build/release/ponyc] Error 1
build/release/libponyrt.a(mpmcq.o): In function `ponyint_mpmcq_pop':
src/libponyrt/sched/mpmcq.c:(.text+0x150): undefined reference to
`__atomic_compare_exchange'
build/release/libponyrt.a(pool.o): In function `pool_get':
src/libponyrt/mem/pool.c:(.text+0xbb): undefined reference to
`__atomic_compare_exchange'
build/release/libponyrt.a(pool.o): In function `ponyint_pool_free':
src/libponyrt/mem/pool.c:(.text+0x221): undefined reference to
`__atomic_compare_exchange'
src/libponyrt/mem/pool.c:(.text+0x26f): undefined reference to
`__atomic_compare_exchange'
build/release/libponyrt.a(pool.o): In function `ponyint_pool_thread_cleanup':
src/libponyrt/mem/pool.c:(.text+0x7ef): undefined reference to
`__atomic_compare_exchange'
build/release/libponyrt.a(pool.o):src/libponyrt/mem/pool.c:(.text+0x8c0):
more undefined references to `__atomic_compare_exchange' follow
c++: error: linker command failed with exit code 1 (use -v to see invocation)
gmake[1]: *** [Makefile:817: build/release/libponyc.tests] Error 1
gmake[1]: Leaving directory '/wrkdirs/usr/ports/lang/ponyc/work/ponyc-0.22.2'
===> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
the maintainer.
*** Error code 1

I saw a somewhat related bug
(https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216745) but as far
as I understand, it is fixed now.

The port compiles with LLVM5.

What am I missing here?

Thanks in advance!
___
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: Why no `operator delete(void*, unsigned int)' on 10 i386?

[Fernando Apesteguía]

El 19 feb. 2018 7:17, "Yuri"  escribió:

I have one port failing on 10 i386 like this:

> undefined reference to `operator delete(void*, unsigned int)'

11 amd64, 12 i386, 12 amd64 work fine.


What might be a problem?


Those are sized operators from c++14. Have you tried to compile with:
-std=gnu++11?

I had a similar problem. This might help:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219484


Cheers



Thanks,

Yuri


___
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"

Re: PR looking for committer

[Fernando Apesteguía]

On Thu, Feb 1, 2018 at 6:38 PM, Fernando Apesteguía
<fernando.apesteg...@gmail.com> wrote:
> Hi,
>
> Can a committer have a look at this PR?:

Sorry, premature send.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225538

It fixes the build of cad/stepcode in CURRENT.

Thanks.
___
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"

PR looking for committer

[Fernando Apesteguía]

Hi,

Can a committer have a look at this PR?:
___
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"

PR looking for committer

[Fernando Apesteguía]

Can a committer have a look at this devel/visualparadigm PR?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223888

Thanks in advance.
___
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: Flavors *COMPLETELY* break the port system (synth and poudriere are useless)

[Fernando Apesteguía]

El 7 dic. 2017 12:00, "Jan Bramkamp"  escribió:

On 06.12.17 23:23, Dave Horsfall wrote:

> On Wed, 6 Dec 2017, Jan Bramkamp wrote:
>
> Synth and poudriere are parallel build tools and as such are very taxing
>> on the system. I suspect your system is unstable under such load, because
>> of a configuration error or unreliable hardware. One such configuration
>> error that bit me is tmpfs mounted without size limitation. Without size
>> limits it can exhaust RAM + swap and crash the system. Limit the sum of all
>> your tmpfs mounts to significantly less than RAM + swap.
>>
>
> What happens then?  Does the build process merely crash instead?  I ask
> because my minimal system (all I can afford on my "income") has 512MB
> memory (all it will take) ad 1GB swap; building Ruby etc kills it, so I use
> packages in that case i.e. no customisation if I wanted it.
>

In that case I wouldn't use tmpfs at all. One conceptual difference between
the old portmaster/portupgrade tools and the newer tools like poudriere and
synth is that the old tools try to minimize rebuilds by modifying the live
system. This can break the system if the upgrade fails and will leave it
inconsistent while the upgrade runs. Also some ports misbehave and interact
with installed software they didn't list as dependency if it is installed.
For these reasons the new tools create jail/chroot environments to build
ports in a clean environment. Poudriere is designed around ZFS features
(snapshots and cloning). Those can be emulated with UFS and overlay file
systems, but Poudriere works best on a big ZFS based system with enough RAM
to keep the build dirs in tmpfs (e.g. 8GB RAM per parallel builder and one
builder per CPU core/thread). You can configure poudriere to use a single
builder and UFS, but it will be a slow process.

Synth reduces that overhead somewhat by reusing the host system. Its focus
is more on keeping a single system up to date instead of compiling sets of
ports to custom repos for other systems and the curses UI is a nice touch.
Also synth can try to avoid building ports by prefetching packages from an
upstream repo.


Can poudriere prefetch packages too?


To be honest few FreeBSD devs still care about self hosting FreeBSD on such
tiny systems (0.5GB RAM, 1-2 cores). There are devs interested on
optimizing FreeBSD for small embedded systems but you aren't expected to
rebuild FreeBSD from source on a wireless access point or dedicated
firewall appliance. If you have to compile and value your time get adequate
hardware. Old 2U dual sockets servers may burn a lot of power but are quite
cheap and you don't have to run a compile server 24/7.

___
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"

PR looking for committer

[Fernando Apesteguía]

Hi,

Can a committer have a look at this? It blocks another port update

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222001

Thanks!
___
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: PR looking for committer

[Fernando Apesteguía]

El 29 ago. 2017 21:36, "Kurt Jaeger"  escribió:

Hi!

> Can a committer have a look at this?
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221835

It hit the tree, thanks!


Thank you.

Could you (or any other committer) also have a look at the PR blocked by
this one?


--
p...@opsec.eu+49 171 3101372 3 years to
go !
___
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"

PR looking for committer

[Fernando Apesteguía]

Hi,

Can a committer have a look at this?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221835

Thanks
___
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: Conditional patch

[Fernando Apesteguía]

El 28 ago. 2017 11:09, "Mathieu Arnold"  escribió:

Le 27/08/2017 à 19:33, Kurt Jaeger a écrit :
> Hi!
>
>> Is it possible to apply a patch in files/ conditionally? I can't find
>> this information in the handbook.
> There's EXTRA_PATCHES, search in devel/*/Makefile for examples
> on how to use them.
>

There is away to fast reference to EXTRA_PATCH in the PATCHFILES
section, I'll write an additional sub-section in the Patching section.


That'd be useful, thanks



--
Mathieu Arnold
___
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: Conditional patch

[Fernando Apesteguía]

On Sun, Aug 27, 2017 at 7:33 PM, Kurt Jaeger  wrote:
> Hi!
>
>> Is it possible to apply a patch in files/ conditionally? I can't find
>> this information in the handbook.
>
> There's EXTRA_PATCHES, search in devel/*/Makefile for examples
> on how to use them.

Got it.

Thanks!

>
> --
> p...@opsec.eu+49 171 3101372 3 years to 
> go !
___
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"

Conditional patch

[Fernando Apesteguía]

Hi,

Is it possible to apply a patch in files/ conditionally? I can't find
this information in the handbook.

Thanks in advance.
___
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: Minor bug in pkg?

[Fernando Apesteguía]

El 6 ago. 2017 9:43, "Grzegorz Junka"  escribió:

Shouldn't pkg be incrementing the first number when installing/upgrading
packages?

[1/247] Reinstalling blender-2.78c_3...
Extracting blender-2.78c_3: 100%
[1/247] Reinstalling abiword-3.0.1_5...
Extracting abiword-3.0.1_5: 100%
[1/247] Upgrading R from 3.4.0_2 to 3.4.1_4...
Extracting R-3.4.1_4: 100%
[1/247] Upgrading GraphicsMagick from 1.3.25_3,1 to 1.3.26,1...
Extracting GraphicsMagick-1.3.26,1: 100%


Not really. It depends on the version of the software itself (and the
versioning scheme it uses[1]) and the version of the port itself.

In your example two packages are reinstalled so no increase in any number
takes place. In the two upgrades the third number is updated. That's
perfectly normal.

[1] https://en.m.wikipedia.org/wiki/Software_versioning



___
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"

PR looking for committer

[Fernando Apesteguía]

Hi,

Can a committer have a look at this?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221187


Thanks!
___
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"

PR needs care

[Fernando Apesteguía]

Hi,

Can a committer have a look at this?:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220951

Thanks!
___
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"

PR looking for committer

[Fernando Apesteguía]

Hi,

Can a committer have a look at this?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220360

Thanks
___
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"

PR needs care

[Fernando Apesteguía]

Hi,

Can anyone have a look at this?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220212

Thanks in advance.
___
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: [RFC] Why FreeBSD ports should have branches by OS version

[Fernando Apesteguía]

El 22 jun. 2017 14:15, "David Demelier"  escribió:

Hello,

Today I've upgraded one of my personal FreeBSD servers. It's running
FreeBSD 11.0 for a while.

While I use quarterly ports branches, I usually update my ports tree
before installing a new service and I faced some troubles:

www/node was updated from 6.x to 7.x: unfortunately my etherpad
instance is not compatible with 7.x. I needed to install www/node6.

devel/mercurial was updated to 4.2: redmine has a small issue making
repository browsing unavailable. I temporarily downgraded Mercurial to
4.0.

I think the current process of having rolling-releases packages makes
unpredictable upgrades as we have to manually check if the upgrade
will be fine or not. When a user installs FreeBSD 11.0 on its system,
it probably expects that everything will work fine until a next major
upgrade like 12.0. That's why I think we really should implement
branches for a specific FreeBSD version.

When FreeBSD 12.0 is released, we should create a ports branch that
will contains only fixes (such as security advisories, crash fixes and
such). No minor or major upgrades until a new 13.0 version is
released. This is the only way to make safe upgrades.

If user think that a software is too old (since we have long delay
between major releases) it can still use the default tree at its own
risks.

Additional benefits of having a ports tree by version: you don't need
to have conditionals in ports Makefiles (how many ports check for
FreeBSD version? a lot).

Any comments are appreciated.

Regards,


CMIIW but when similar approaches come up, one of the reasons to not do it
is man power.


--
Demelier David
___
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"

PR looking for committer

[Fernando Apesteguía]

Hi,

Can a committer have a look at this PR:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216616

Thanks in advance.
___
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"

pkg install avrdude wants to deinstall firefox

[Fernando Apesteguía]

Hi,

I'm running FreeBSD 11.0-RELEASE-p2. When I try to install avrdude, I get this:

$ pkg install avrdude

Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
All repositories are up-to-date.
The following 9 package(s) will be affected (of 0 checked):

Installed packages to be REMOVED:
firefox-50.1.0_3,1

New packages to be INSTALLED:
avrdude: 6.3
libftdi1: 1.3_2
boost-libs: 1.63.0_1
libconfuse: 2.7_2

Installed packages to be UPGRADED:
icu: 57.1,1 -> 58.2,1
harfbuzz: 1.3.4 -> 1.4.1
texlive-base: 20150521_13 -> 20150521_14
qt5-core: 5.6.1_1 -> 5.6.2_1

Number of packages to be removed: 1
Number of packages to be installed: 4
Number of packages to be upgraded: 4

The process will require 21 MiB more space.
25 MiB to be downloaded.

Why is this operation trying to remove firefox?
___
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: Help with C++, gcc4.9 and libstdc++

[Fernando Apesteguía]

On Tue, Nov 29, 2016 at 9:28 PM, Fernando Apesteguía
<fernando.apesteg...@gmail.com> wrote:
> El 29 nov. 2016 18:58, "Rainer Hurling" <rhur...@gwdg.de> escribió:
>>
>> Hi Fernando,
>>
>> Am 29.11.2016 um 17:50 schrieb Fernando Apesteguía:
>> > I maintain a port written mostly in C++ (cad/openvsp).
>> >
>> > This port used to compile fine in 11 and 10.x in both i386 and amd64.
>> > Since Nov 22nd I'm receiving a pkg-fallout for this port in 10.1. The
>> > port fails with this message:
>> >
>> > undefined reference to `__cxa_throw_bad_array_new_length'
>> >
>> > I assume the source of the problem is defaulting to gcc 4.9 in the
>> > ports and it seems to be related to libstdc++
>> >
>> > I use USES=compiler:gcc-c++11-lib in the Makefile since some c++11
>> > features are required. Any idea of why this could be failing to link?.
>> > What puzzles me is that it compiles fine with gcc 4.9 in 10.2.
>> >
>> > Thanks in advance.

Until that time comes, I would like to send an update but I'm having
some problems with it. I need a c++11 lib but I need gcc < 4.9 for the
port to compile on 10.1 (in < 10.x it doesn't build due to the lack of
certain math functions and in > 10.2 it compiles nicely). I've been
playing around with USE_GCC = 4.8 to no luck.

How can I specify both, gcc 4.8 specifically and still getting all the
work behing the gcc-c++11-lib ARG?

Thanks in advance.

>>
>> this also happens with a few other ports, and is described in
>>
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214863
>>
>> As far, as I understand, a patch with a workaround will be committed in
>> the next time.
>
> Thanks for the info!
>
>>
>> HTH,
>> Rainer
___
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: Help with C++, gcc4.9 and libstdc++

[Fernando Apesteguía]

El 29 nov. 2016 18:58, "Rainer Hurling" <rhur...@gwdg.de> escribió:
>
> Hi Fernando,
>
> Am 29.11.2016 um 17:50 schrieb Fernando Apesteguía:
> > I maintain a port written mostly in C++ (cad/openvsp).
> >
> > This port used to compile fine in 11 and 10.x in both i386 and amd64.
> > Since Nov 22nd I'm receiving a pkg-fallout for this port in 10.1. The
> > port fails with this message:
> >
> > undefined reference to `__cxa_throw_bad_array_new_length'
> >
> > I assume the source of the problem is defaulting to gcc 4.9 in the
> > ports and it seems to be related to libstdc++
> >
> > I use USES=compiler:gcc-c++11-lib in the Makefile since some c++11
> > features are required. Any idea of why this could be failing to link?.
> > What puzzles me is that it compiles fine with gcc 4.9 in 10.2.
> >
> > Thanks in advance.
>
> this also happens with a few other ports, and is described in
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214863
>
> As far, as I understand, a patch with a workaround will be committed in
> the next time.

Thanks for the info!

>
> HTH,
> Rainer
___
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"

Help with C++, gcc4.9 and libstdc++

[Fernando Apesteguía]

I maintain a port written mostly in C++ (cad/openvsp).

This port used to compile fine in 11 and 10.x in both i386 and amd64.
Since Nov 22nd I'm receiving a pkg-fallout for this port in 10.1. The
port fails with this message:

undefined reference to `__cxa_throw_bad_array_new_length'

I assume the source of the problem is defaulting to gcc 4.9 in the
ports and it seems to be related to libstdc++

I use USES=compiler:gcc-c++11-lib in the Makefile since some c++11
features are required. Any idea of why this could be failing to link?.
What puzzles me is that it compiles fine with gcc 4.9 in 10.2.

Thanks in advance.
___
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"

exp-runs information

[Fernando Apesteguía]

Hi all,

Where can I find information about exp-runs? Specifically when they
should be run, and how to proceed in case something breaks. What's the
policy in this regard? There's nothing in the porter's handbook and I
could only find a few bits of information scattered in the web.

Thanks!
___
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"

PR looking for committer

[Fernando Apesteguía]

Hi,

Can a committer have a look at this?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214362

Thanks in advance.
___
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"

PR looking for committer

[Fernando Apesteguía]

Can a committer have a look at this?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212951

Thank you!
___
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"

PR looking for committer

[Fernando Apesteguía]

Hi,

Can a committer have a look at this simple update?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211783

Thanks!
___
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"

PR looking for committer

[Fernando Apesteguía]

Hi all,

Can a committer please have a look at this:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211372

Thanks in advance.
___
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: net-im/jitsi fails in actual head in staging phase in poudriere

[Fernando Apesteguía]

On Sun, Jul 17, 2016 at 12:08 PM, Matthias Apitz  wrote:
>
> The subject says it all; the relevant part of the log is:
>
>
> >> Building net-im/jitsi
> build started at Sun Jul 17 11:55:40 CEST 2016
> port directory: /usr/ports/net-im/jitsi
> building for: FreeBSD freebsd-r302904-ports-20160716-job-04 12.0-CURRENT 
> FreeBSD 12.0-CURRENT r302930 amd64
> maintained by: tza...@it.teithe.gr
> Makefile ident:  $FreeBSD: head/net-im/jitsi/Makefile 399134 2015-10-12 
> 14:25:50Z swills $
> Poudriere version: 3.2-pre
> Host OSVERSION: 121
> Jail OSVERSION: 121
>
> ---Begin Environment---
> SHELL=/bin/csh
> UNAME_v=FreeBSD 12.0-CURRENT r302930
> UNAME_r=12.0-CURRENT
> BLOCKSIZE=K
> MAIL=/var/mail/root
> STATUS=1
> OPSYS=FreeBSD
> ARCH=amd64
> SAVED_TERM=xterm
> MASTERMNT=/usr/local/poudriere/data/.m/freebsd-r302904-ports-20160716/ref
> FORCE_PACKAGE=yes
> PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin
> _JAVA_VERSION_LIST_REGEXP=1.6\|1.7\|1.8\|1.6+\|1.7+\|1.8+
> POUDRIERE_BUILD_TYPE=bulk
> PKGNAME=jitsi-2.8.5426
> OSREL=12.0
> _OSRELEASE=12.0-CURRENT
> PYTHONBASE=/usr/local
> JAVA_OPTS=-XX:-UseCompressedClassPointers -Xms512m -Xmx2048m
> OLDPWD=/
> _SMP_CPUS=4
> PWD=/usr/local/poudriere/data/.m/freebsd-r302904-ports-20160716/ref/.p/pool
> HAVE_COMPAT_IA32_KERN=YES LINUX_OSRELEASE=2.6.16
> MASTERNAME=freebsd-r302904-ports-20160716
> SCRIPTPREFIX=/usr/local/share/poudriere
> _JAVA_VENDOR_LIST_REGEXP=openjdk\|oracle\|sun
> USER=root
> HOME=/root
> POUDRIERE_VERSION=3.2-pre
> SCRIPTPATH=/usr/local/share/poudriere/bulk.sh
> CONFIGURE_MAX_CMD_LEN=262144
> LIBEXECPREFIX=/usr/local/libexec/poudriere
> LOCALBASE=/usr/local
> PACKAGE_BUILDING=yes
> MAVEN_OPTS=-Xmx1024m -XX:MaxPermSize=256m
> _JAVA_OS_LIST_REGEXP=native\|linux
> OSVERSION=121
> ---End Environment---
>
> ---Begin OPTIONS List---
> ---End OPTIONS List---
>
> --CONFIGURE_ARGS--
>
> --End CONFIGURE_ARGS--
>
> --CONFIGURE_ENV--
> XDG_DATA_HOME=/wrkdirs/usr/ports/net-im/jitsi/work  
> XDG_CONFIG_HOME=/wrkdirs/usr/ports/net-im/jitsi/work  
> HOME=/wrkdirs/usr/ports/net-im/jitsi/work TMPDIR="/tmp" SHELL=/bin/sh 
> CONFIG_SHELL=/bin/sh
> --End CONFIGURE_ENV--
>
> --MAKE_ENV--
> JAVA_HOME=/usr/local/openjdk8 
> XDG_DATA_HOME=/wrkdirs/usr/ports/net-im/jitsi/work  
> XDG_CONFIG_HOME=/wrkdirs/usr/ports/net-im/jitsi/work  
> HOME=/wrkdirs/usr/ports/net-im/jitsi/work TMPDIR="/tmp" NO_PIE=yes 
> MK_DEBUG_FILES=no MK_KERNEL_SYMBOLS=no SHELL=/bin/sh NO_LINT=YES 
> PREFIX=/usr/local  LOCALBASE=/usr/local  LIBDIR="/usr/lib"  CC="clang" 
> CFLAGS="-O2 -pipe  -fstack-protector -fno-strict-aliasing"  CPP="clang-cpp" 
> CPPFLAGS=""  LDFLAGS=" -fstack-protector" LIBS=""  CXX="clang++" 
> CXXFLAGS="-O2 -pipe -fstack-protector -fno-strict-aliasing "  
> MANPREFIX="/usr/local" BSD_INSTALL_PROGRAM="install  -s -m 555"  
> BSD_INSTALL_LIB="install  -s -m 444"  BSD_INSTALL_SCRIPT="install  -m 555"  
> BSD_INSTALL_DATA="install  -m 0644"  BSD_INSTALL_MAN="install  -m 444"
> --End MAKE_ENV--
>
> --PLIST_SUB--
> JAVASHAREDIR="share/java"
> JAVAJARDIR="share/java/classes"
> OSREL=12.0
> PREFIX=%D
> LOCALBASE=/usr/local
> RESETPREFIX=/usr/local
> PORTDOCS=""
> PORTEXAMPLES=""
> LIB32DIR=lib
> DOCSDIR="share/doc/jitsi"
> EXAMPLESDIR="share/examples/jitsi"
> DATADIR="share/jitsi"
> WWWDIR="www/jitsi"
> ETCDIR="etc/jitsi"
> --End PLIST_SUB--
>
> --SUB_LIST--
> JAVASHAREDIR="/usr/local/share/java"
> JAVAJARDIR="/usr/local/share/java/classes"
> JAVALIBDIR="/usr/local/share/java/classes"
> PREFIX=/usr/local
> LOCALBASE=/usr/local
> DATADIR=/usr/local/share/jitsi
> DOCSDIR=/usr/local/share/doc/jitsi
> EXAMPLESDIR=/usr/local/share/examples/jitsi
> WWWDIR=/usr/local/www/jitsi
> ETCDIR=/usr/local/etc/jitsi
> --End SUB_LIST--
>
> ---Begin make.conf---
> USE_PACKAGE_DEPENDS=yes
> BATCH=yes
> WRKDIRPREFIX=/wrkdirs
> PORTSDIR=/usr/ports
> PACKAGES=/packages
> DISTDIR=/distfiles
>  /usr/local/etc/poudriere.d/freebsd-r302904-make.conf 
> WITH_PKGNG=yes   # Only required for versions before 10.0
> CC=clang # Highly recommended over GCC,
> CXX=clang++  # but only needed for 8.X and 9.X
> CPP=clang-cpp# since it's the default in 10.0
> MASTER_SITE_BACKUP?= \
> http://ftp2.us.freebsd.org/pub/FreeBSD/ports/distfiles/${DIST_SUBDIR/}
> #
> WITHOUT_HAL=yes
> # CFLAGS=""
> #
> # NO_IGNORE=yes
> # From: Chris Rees 
> # CC: freebsd-ports@freebsd.org
> # Date: Sat, 23 Aug 2014 14:19:24 +0100
> # better is:
> DISABLE_LICENSES=yes
> #
> #
> # added 20130612 guru
> # CPUTYPE?=pentium3
> SENDMAIL_CFLAGS=-I/usr/local/include/sasl -DSASL
> SENDMAIL_LDFLAGS=-L/usr/local/lib
> SENDMAIL_LDADD=-lsasl2
> #
> # not used until now:
> # FETCH_BEFORE_ARGS=-p4 -T 10
> # OPTIONS_UNSET= DEBUG HELP STATIC GNUTLS DOCS EXAMPLES IPV6 \
> #MANPAGES PTH IDN LIBIDN NLS DBUS SOUND ALSA PULSEAUDIO \
> #DOCBOOK CUPS TESTS HTMLDOCS BONJOUR GSSAPI APIDOCS
> #
> ### MAVEN_OPTS='-Xmx1024m 

Re: QA script error (libc++)

[Fernando Apesteguía]

On Sat, Jun 25, 2016 at 7:50 PM, Ben Woods <woods...@gmail.com> wrote:
> On Saturday, 25 June 2016, Fernando Apesteguía
>>
>> Also portlint doesn't seem to be in sync with
>> the new stuff in ports. In my case it complains about the TIMESTAMP
>> new line in distinfo and the directories not found in the ports
>> collection (due to the removal of ${PORTSDIR} while defining the
>> dependencies).
>>
>> Thanks!
>>
>> > --
>> > Th. Thomas.
>
>
> If you update your version of portlint to 2.17.2 it can handle both of those
> things.
> http://www.freshports.org/ports-mgmt/portlint

I missed that because I sticked to the the quaterly branch in pkg.

Thanks!

>
> Regards,
> Ben
>
>
> --
>
> --
> From: Benjamin Woods
> woods...@gmail.com
___
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: QA script error (libc++)

[Fernando Apesteguía]

On Sat, Jun 25, 2016 at 10:23 AM, Thierry Thomas <thie...@freebsd.org> wrote:
> Hello,
>
> Le ven 24 jui 16 à  8:16:26 +0200, Fernando Apesteguía 
> <fernando.apesteg...@gmail.com>
>  écrivait :
>> One of my ports is written in C++. It links agains libc++ that is in
>> base (/usr/src/contrib/libc++). The port still builds fine and works
>> but the QA scripts show an error complaining about the executable
>> being linked to libc++ without the library being listed as an actual
>> dependency and it suggests to add the following line to the Makefile:
>>
>> LIB_DEPENDS+=libc++.so:devel/libc++
>
> Same here for my port graphics/cimg. I guess that QA script is not yet
> ready, and ATM it's safer to ignore its advices.

That's my thought too. Also portlint doesn't seem to be in sync with
the new stuff in ports. In my case it complains about the TIMESTAMP
new line in distinfo and the directories not found in the ports
collection (due to the removal of ${PORTSDIR} while defining the
dependencies).

Thanks!

> --
> Th. Thomas.
___
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"

QA script error (libc++)

[Fernando Apesteguía]

One of my ports is written in C++. It links agains libc++ that is in
base (/usr/src/contrib/libc++). The port still builds fine and works
but the QA scripts show an error complaining about the executable
being linked to libc++ without the library being listed as an actual
dependency and it suggests to add the following line to the Makefile:

LIB_DEPENDS+=libc++.so:devel/libc++

Is this strictly necessary? Would something like this be acceptable?:

.if !exists(/usr/lib/libc++.so)
...
LIB_DEPENDS+=libc++.so:devel/libc++
...
.endif

Note: the port does not compile on FreeBSD < 10.x

Thanks in advance.
___
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: PRs that need care

[Fernando Apesteguía]

El 16/6/2016 3:09, "Kurt Jaeger"  escribió:
>
> Hi!
>
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210046
>
> Done.
>
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210214
>
> Testbuilding.
>
> Please, do no longer attach poudriere logs to PRs, just mention
> that you've done them, the architectures and the results. The
> attachments clutter the PR databases and there's consensus that this
> is a bit too much.

Will do.

Thanks!

>
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210241
>
> Testbuilding.
>
> --
> p...@opsec.eu+49 171 3101372 4 years to
go !
___
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"

PRs that need care

[Fernando Apesteguía]

Hi there,

Any committer that can have a look at these?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210046
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210214
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210241

Thanks in advance.
___
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"

PR needs care

[Fernando Apesteguía]

Hi,

Could a committer please have a look at this PR?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209872

Thanks in advance.
___
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: Poudriere question

[Fernando Apesteguía]

El 9/5/2016 20:15, "Kurt Jaeger"  escribió:
>
> Hi!
>
> > Is it safe to use different invocations of poudriere concurrently for
> > different jails but using the same ports collection?
>
> Yes.

Terrific, thanks!

>
> --
> p...@opsec.eu+49 171 3101372 4 years to
go !
___
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"

Poudriere question

[Fernando Apesteguía]

Hi all,

Is it safe to use different invocations of poudriere concurrently for
different jails but using the same ports collection?

Thanks
___
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: Is redports.org back?

[Fernando Apesteguía]

On Fri, Apr 22, 2016 at 5:49 PM, Kurt Jaeger  wrote:
> Hi!
>
>> I noticed that there is an apparently functional redports.org site
>> again. Is it functional?
>
> Interesting find, thanks! No, it does not look yet functional.

Damn it! I was starting to cry of happiness. I hope it's back soon :)

>
>> All I get is a "No authenticated" message when I try to log in.
>
> --
> p...@opsec.eu+49 171 3101372 4 years to 
> go !
___
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"

Is redports.org back?

[Fernando Apesteguía]

Hi,

I noticed that there is an apparently functional redports.org site
again. Is it functional? All I get is a "No authenticated" message
when I try to log in.

Cheers.
___
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"

Looking committer for PR

[Fernando Apesteguía]

Hi,

Can a committer have a look at this PR?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207114

Thanks!
___
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: Welcome miwi back to the portmgr team!

[Fernando Apesteguía]

On Wed, Jan 20, 2016 at 2:13 PM,   wrote:
> Welcome back & thanks for PHP, hoping it will go to port tree soon :D

Good news indeed!

>
> 20 janvier 2016 14:06 "Kubilay Kocak"  a écrit:
>> On 20/01/2016 11:47 PM, Frederic Culot wrote:
>>
>>> The FreeBSD Ports Management team is pleased to welcome back Martin
>>> Wilke, aka miwi@, to it's ranks.
>>>
>>> As everyone knows, Martin is the developer who contributed the largest
>>> number of commits to the ports tree: more than 20,000 commits since
>>> 2006! In November 2014, Martin decided to step down from duties at
>>> FreeBSD in order to save time for both his growing family and real job.
>>>
>>> Luckily for us, Martin has more time now for FreeBSD, so please join me
>>> in welcoming miwi@ back to the portmgr team.
>>>
>>> Frederic
>>> on behalf of portmgr@
>>
>> \o/
>> ___
>> 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"
___
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"

PR

[Fernando Apesteguía]

Hi,

Please, can anyone take this PR?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206294

Thanks in advance.
___
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: PR

[Fernando Apesteguía]

On Tue, Jan 19, 2016 at 2:32 PM, Fernando Apesteguía
<fernando.apesteg...@gmail.com> wrote:
> Hi,
>
> Please, can anyone take this PR?
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206294
>
> Thanks in advance.

And... that was fast!

Thanks!
___
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: pkg-fallout mails

[Fernando Apesteguía]

On Wed, Nov 18, 2015 at 11:46 AM, Fernando Apesteguía
<fernando.apesteg...@gmail.com> wrote:
> On Wed, Nov 18, 2015 at 11:14 AM, Matthew Seaman <matt...@freebsd.org> wrote:
>> On 2015/11/18 07:04, Fernando Apesteguía wrote:
>>> !!! Jail is newer than host. (Jail: 1100090, Host: 1100085) !!!
>>> !!! This is not supported. !!!
>>> !!! Host kernel must be same or newer than jail. !!!
>>> !!! Expect build failures. !!!
>>>
>>>
>>> Can anyone please say if this is expected? Is anyone running
>>> tests/changing things in the ports building infrastructure? I could
>>> just ignore the mails, but I never received so many of these before.
>>
>> This warning appears on pretty much all pkg-fallout e-mails for HEAD.
>> It is a red-herring, and has nothing at all to do with why the e-mail is
>> being sent.  It's just a warning: the host and jail versions are
>> sufficiently close there is no actual conflict between the system kernel
>> and the jail's userland even though that userland is more recent.
>
> Thanks for the explanation!
>
>>
>> The problem that is causing builds to fail in the pkg cluster will
>> appear towards the *end* of the build log included in the e-mail.  If
>> you're getting these e-mails then the affected port is failing to build
>> on at least one of the supported environments where it is expected to
>> work.  As port maintainer, you are meant to look into those build
>> failures and preferably fix them; not just ignore the e-mails.  If you
>> don't understand why this port is failing to build, then there are any
>> number of people here who will be happy to assist.
>
> I was just trying to understand why that port that hasn't been updated
> in a while was suddenly failing to build... and well... the "Expect
> build failures" was kind of an explanation :)
>
> I'll have a look at it as soon as I can.

Is there any way to know when the last successful build was? The first
one that failed was on 07-Nov-2015. I would like to cross check the
changes in CURRENT to see if there were any clang/libc++ changes. I
face the same problems trying to update cad/openvsp to 3.x. I get
funny compilation error from clang that I don't fully understand.

Thanks

>
> Cheers.
>
>>
>> Cheers,
>>
>> Matthew
>>
>>
>>
>>
___
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: pkg-fallout mails

[Fernando Apesteguía]

On Wed, Nov 18, 2015 at 11:14 AM, Matthew Seaman <matt...@freebsd.org> wrote:
> On 2015/11/18 07:04, Fernando Apesteguía wrote:
>> !!! Jail is newer than host. (Jail: 1100090, Host: 1100085) !!!
>> !!! This is not supported. !!!
>> !!! Host kernel must be same or newer than jail. !!!
>> !!! Expect build failures. !!!
>>
>>
>> Can anyone please say if this is expected? Is anyone running
>> tests/changing things in the ports building infrastructure? I could
>> just ignore the mails, but I never received so many of these before.
>
> This warning appears on pretty much all pkg-fallout e-mails for HEAD.
> It is a red-herring, and has nothing at all to do with why the e-mail is
> being sent.  It's just a warning: the host and jail versions are
> sufficiently close there is no actual conflict between the system kernel
> and the jail's userland even though that userland is more recent.

Thanks for the explanation!

>
> The problem that is causing builds to fail in the pkg cluster will
> appear towards the *end* of the build log included in the e-mail.  If
> you're getting these e-mails then the affected port is failing to build
> on at least one of the supported environments where it is expected to
> work.  As port maintainer, you are meant to look into those build
> failures and preferably fix them; not just ignore the e-mails.  If you
> don't understand why this port is failing to build, then there are any
> number of people here who will be happy to assist.

I was just trying to understand why that port that hasn't been updated
in a while was suddenly failing to build... and well... the "Expect
build failures" was kind of an explanation :)

I'll have a look at it as soon as I can.

Cheers.

>
> Cheers,
>
> Matthew
>
>
>
>
___
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: pkg-fallout mails

[Fernando Apesteguía]

On Fri, Nov 13, 2015 at 8:14 AM, Fernando Apesteguía
<fernando.apesteg...@gmail.com> wrote:
> Hi,
>
> Since the last week (aprox), I keep receiving pkg-fallout mails for
> cad/openvsp, all of them with the following warning:
>
> !!! Jail is newer than host. (Jail: 1100089, Host: 1100079) !!!
> !!! This is not supported. !!!
> !!! Host kernel must be same or newer than jail. !!!
> !!! Expect build failures. !!!
>
> In the past, when I received one isolated mail, I just ignored it, but
> I'm receiving them more often now. Something we can do about this?

Another mail:

You are receiving this mail as a port that you maintain
is failing to build on the FreeBSD package build server.
Please investigate the failure and submit a PR to fix
build.

Maintainer: fernando.apesteg...@gmail.com
Last committer: rak...@freebsd.org
Ident:  $FreeBSD: head/cad/openvsp/Makefile 395630 2015-08-30
17:41:23Z rakuco $
Log URL:
http://beefy3.nyi.freebsd.org/data/head-i386-default/p401796_s290807/logs/openvsp-2.3.0_4.log
Build URL:
http://beefy3.nyi.freebsd.org/build.html?mastername=head-i386-default=p401796_s290807
Log:

>> Building cad/openvsp
build started at Wed Nov 18 06:46:05 UTC 2015
port directory: /usr/ports/cad/openvsp
building for: FreeBSD head-i386-default-job-12 11.0-CURRENT FreeBSD
11.0-CURRENT r290807 i386
maintained by: fernando.apesteg...@gmail.com
Makefile ident:  $FreeBSD: head/cad/openvsp/Makefile 395630
2015-08-30 17:41:23Z rakuco $
Poudriere version: 3.1.9
Host OSVERSION: 1100085
Jail OSVERSION: 1100090




!!! Jail is newer than host. (Jail: 1100090, Host: 1100085) !!!
!!! This is not supported. !!!
!!! Host kernel must be same or newer than jail. !!!
!!! Expect build failures. !!!


Can anyone please say if this is expected? Is anyone running
tests/changing things in the ports building infrastructure? I could
just ignore the mails, but I never received so many of these before.

Thanks.

>
> Chees.
___
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"

PR needs care :)

[Fernando Apesteguía]

Can a committer have a look at this one:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204403

Thanks!
___
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: PR needs care :)

[Fernando Apesteguía]

On Fri, Nov 13, 2015 at 7:43 PM, Kurt Jaeger  wrote:
> Hi!
>
>> > > Can a committer have a look at this one:
>> > >
>> > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204403
> [...]
>
> Done.
>
>> There's a newer version with 20151102 in the DISTNAME.
>>
>> See for a new patch-v2:
>
> I assumed an update to the DISTNAME was what you intended.

Hi,

Sorry that I couldn't answer earlier.

Yes, that was my intention. Thanks for the fix!

>
> --
> p...@opsec.eu+49 171 3101372 5 years to 
> go !
___
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"

pkg-fallout mails

[Fernando Apesteguía]

Hi,

Since the last week (aprox), I keep receiving pkg-fallout mails for
cad/openvsp, all of them with the following warning:

!!! Jail is newer than host. (Jail: 1100089, Host: 1100079) !!!
!!! This is not supported. !!!
!!! Host kernel must be same or newer than jail. !!!
!!! Expect build failures. !!!

In the past, when I received one isolated mail, I just ignored it, but
I'm receiving them more often now. Something we can do about this?

Chees.
___
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: Looking for a committer

[Fernando Apesteguía]

On Wed, Sep 9, 2015 at 8:35 PM, Kurt Jaeger  wrote:
> Hi!
>
>> > It fails to fetch ? Any ideas ?
>>
>> I suppose it's because they released the new version (20150902) and
>> removed the old one.
>
> If this is all, I've changed and started the make makesum.
> 250 MB distfile...
>
>> This project has a funny record of doing things
>> like that, re-rolling releases so the checksum fails, etc...
>>
>> I'll update the patch and be back to you.
>
> If only the MMDD changed, I can handle it.

That seems to be the case. The pkg-plist doesn't change either.
Successfully built for {9.3,10.2}amd64

I updated the PR.

>
> --
> p...@opsec.eu+49 171 3101372 5 years to 
> go !
___
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"

Looking for a committer

[Fernando Apesteguía]

Please, can a committer have a look at this?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202752

Thanks in advance.
___
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: Looking for a committer

[Fernando Apesteguía]

On Wed, Sep 9, 2015 at 8:21 PM, Kurt Jaeger  wrote:
> Hi!
>
>> Please, can a committer have a look at this?
>>
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202752
>
> It fails to fetch ? Any ideas ?

I suppose it's because they released the new version (20150902) and
removed the old one. This project has a funny record of doing things
like that, re-rolling releases so the checksum fails, etc...

I'll update the patch and be back to you.

Thanks!

>
> ===>   visualparadigm-12.2.20150820 depends on file: /usr/local/sbin/pkg - 
> found
> => Visual_Paradigm_CE_12_2_20150820_Unix_InstallFree.tar.gz doesn't seem to 
> exist in /usr/ports/distfiles/.
> => Attempting to fetch 
> http://eu6.visual-paradigm.com/visual-paradigm/vpce12.2/20150820/Visual_Paradigm_CE_12_2_20150820_Unix_InstallFree.tar.gz
> fetch: 
> http://eu6.visual-paradigm.com/visual-paradigm/vpce12.2/20150820/Visual_Paradigm_CE_12_2_20150820_Unix_InstallFree.tar.gz:
>  Not Found
> => Attempting to fetch 
> http://distcache.FreeBSD.org/ports-distfiles/Visual_Paradigm_CE_12_2_20150820_Unix_InstallFree.tar.gz
> fetch: 
> http://distcache.FreeBSD.org/ports-distfiles/Visual_Paradigm_CE_12_2_20150820_Unix_InstallFree.tar.gz:
>  Not Found
>
> --
> p...@opsec.eu+49 171 3101372 5 years to 
> go !
___
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: Looking for a committer

[Fernando Apesteguía]

El 09/09/2015 21:52, "Kurt Jaeger"  escribió:
>
> Hi!
>
> > That seems to be the case. The pkg-plist doesn't change either.
> > Successfully built for {9.3,10.2}amd64
> >
> > I updated the PR.
>
> Test-builds done on cur 93a 10a 10i.
>
> Committed, thanks.

Thanks!

>
> --
> p...@opsec.eu+49 171 3101372 5 years to
go !
___
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: distfiles directory in poudriere

[Fernando Apesteguía]

El 28/08/2015 23:32, Mathieu Arnold m...@freebsd.org escribió:



 +--On 28 août 2015 23:25:59 +0200 Fernando Apesteguía
 fernando.apesteg...@gmail.com wrote:
 | One of my ports depends on linux-oracle-jdk8 that must be downloaded
 | by hand and place it in the distfiles directory before re-running
 | 'make install' (license constraints).
 |
 | If I'm going to test my port with poudriere, where should I place the
 | distribution file?

 In the directory defined by DISTFILES_CACHE.

And that makes a lot of sense :)

Thanks!


 --
 Mathieu Arnold
___
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

distfiles directory in poudriere

[Fernando Apesteguía]

One of my ports depends on linux-oracle-jdk8 that must be downloaded
by hand and place it in the distfiles directory before re-running
'make install' (license constraints).

If I'm going to test my port with poudriere, where should I place the
distribution file?

Thanks in advance
___
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: NEW PORT for librdkafka

[Fernando Apesteguía]

El 07/07/2015 15:14, xoan carlos via freebsd-ports 
freebsd-ports@freebsd.org escribió:

 Hi im trying to create and submit a NEW PORT for librdkafka. It compiles
ok but it get installed in the stage directory
(/usr/ports/devel/librdkafka/work/stage/usr/local/lib)  and not in
/usr/local/lib. Any idea what additional step is needed to install it in
the right directory instead of the jail environment?
 the makefile is as simple as
 # $FreeBSD$
 PORTNAME=   librdkafkaPORTVERSION=0.8.6CATEGORIES= devel
 MAINTAINER= youremail@example.comCOMMENT=librdkafka
 USE_GITHUB= yesGH_ACCOUNT= edenhillGH_PROJECT=
librdkafkaGH_TAGNAME= 25d8791
 USES=   gmakeUSE_LDCONFIG=   yesGNU_CONFIGURE=  yes
 post-install:@${STRIP_CMD}
${STAGEDIR}${PREFIX}/lib/lib*.so.include bsd.port.mk

It should install under the staging directory during development. After
that, the ports infrastructure will check that everything installed in the
appropriate paths.

I recommend to use poudriere and/or port test (part of porttools) to check
that everything is fine.

Regards.

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

Re: pkg 1.5.0 is out

[Fernando Apesteguía]

El 14/04/2015 22:19, Mikhail Tsatsenko m.tsatse...@gmail.com escribió:

 2015-04-14 23:05 GMT+03:00 Baptiste Daroussin b...@freebsd.org:
  Hi all,
 Hi,
 thanks for your great work!

+1

 
  Final pkg 1.5.0 has been released.
 
  What happened since pkg 1.4.0:
  - Initial provides/requires support
  - Lots of new regression tests have been added
  - Initial support for OS X
  - Initial support for NetBSD/EdgeBSD
  - Update most of the bundled third party software has been updated to
their
latest version
  - Improve the messages reported by pkg
  - Properly support file flags
  - Implement argument support for custom keywords
  - Extend setting credential via plist to allow to set file flags
  - Make credential syntax via plist more flexible allow to only defines
the first
  - pkg updating now supports case insensitive matching
  - pkg create now support a verbose mode
  - Add an option to change the default on question, until now the
default answer
was No with that option set it would be Yes
  - Lots of fixes to pkg audit -r
  - Global memory usage reduction and speed up
  - Improvements and cleanup on pkg alias
  - pkg annotate --show --all has been fixed
  - Make pkg.h C++ friendly
  - Lots of improvements in the solver
  - Lots of fixes on 32 bits platforms
  - Add support for: pkg create -M ./plop.ucl -p ./plop.plist
  - New pkg -r rootdir that will install in the given rootdir without
chrooting
  - Export PKG_ROOTDIR to scripts allow to make them as portable as
possible
  - Stop trying to remove all installed package with the argument of pkg
delete is
a local file
  - Be more explicit about why the solver it going to reinstall, remove
or upgrade
(when possible)
  - Plenty of bug fixes
  - Plenty of new bugs
  - pkg shlibs now support -q
  - pkg lock gained a new --has-locked-packages option
  - pkg now resumes fetch if possible
  - CONSERVATIVE_UPGRADE is now on by default
  - pkg alias now have a -l argument to list aliases
  - A sample pkg.conf is now installed with a bunch of aliases set by
default
  - Fix the backup script to properly export an sql which will be
importable via
pkg shell and/or sqlite out of box
 
  I would like to thank anyone that has been contributing to pkg to make
this
  release happen (via code, bug report, feature request, testing and
documentation)
 
  For pkg 1.6.0 among other things and depending on the time, here is
what we do
  plan to work on:
  - Safe cherry-picking of upgrades (aka: pkg upgrade something)
  - New context dependant messages:
* messages that only appears during upgrades
* messages that only appears on deinstall
* messages that only appears on install
  - Extend provides/requires to support flexible dependencies
  - Linux package backend (?)
  - Allow multiple versions of a given package in a repo
  - Add more regression tests
  - Improve documentation
  - please add here you personal ideas
 
  Best regards,
  Bapt



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

Re: MooseFS Ports for versions 2.0 and 3.0

[Fernando Apesteguía]

El 09/04/2015 15:00, Piotr Robert Konopelko piotr.konope...@moosefs.com
escribió:

 Dear FreeBSD Ports team,

 On FreeBSD Ports site only ports for MooseFS 1.6.27-5 are available:
 https://www.freebsd.org/cgi/ports.cgi?query=moosefsstype=all[1]

 Longer than a half year ago MooseFS 2.0 has been released and few days
ago - MooseFS
 3.0.

 We would like to inform, that we have prepared ports for MooseFS versions
2.0 and 3.0.

 How is the way to upgrade them in FreeBSD ports tree?

You can start here:

https://bugs.freebsd.org/bugzilla/

And file a request

 Is there a possibility to make our team the maintainer of the MooseFS
FreeBSD Ports?

Since ports@ is the current maintainer, you could file another request and
see if they are willing to drop mantainership in your favor or ask here :)



 --
 Best regards,
 Piotr Robert Konopelko
 *MooseFS Technical Support Engineer* | moosefs.com[2]


 
 [1] https://www.freebsd.org/cgi/ports.cgi?query=moosefsstype=all
 [2] http://moosefs.com
 ___
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Hotfix and unbreak update that need to be commited

[Fernando Apesteguía]

On Sat, Feb 7, 2015 at 6:23 PM, Antoine Brodin anto...@freebsd.org wrote:
 On Sat, Feb 7, 2015 at 5:12 PM, Kurt Jaeger li...@opsec.eu wrote:
 Hi!

  jbeich suggests in

  https://lists.freebsd.org/pipermail/svn-ports-all/2015-February/084775.html

  that you improve the patch using SRC_BASE and test if SRC_BASE
  is available. Can you submit this and send me the PR ? I'll get it
  committed.

 Done:

 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197394

 Committed, thanks!

 I fixed the check but this still looks wrong,  why doesn't the port
 link dynamically against zlib?
 If there is a vulnerability in zlib, the port won't be fixed by a zlib update.

I'll have a look at it when I can.

Cheers.


 Cheers,

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

Re: Hotfix and unbreak update that need to be commited

[Fernando Apesteguía]

El 07/02/2015 08:19, Kurt Jaeger li...@opsec.eu escribió:

 Hi!

And if the commiter is kind enough to take care of
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197135 that
updates
  
   Done.

 jbeich suggests in


https://lists.freebsd.org/pipermail/svn-ports-all/2015-February/084775.html

 that you improve the patch using SRC_BASE and test if SRC_BASE
 is available. Can you submit this and send me the PR ? I'll get it
committed.


I'm away from my computer for some time, but I'll do it and cone back to
you soon.

Cheers

 --
 p...@opsec.eu+49 171 3101372 5 years to
go !
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Hotfix and unbreak update that need to be commited

[Fernando Apesteguía]

El 07/02/2015 12:38, Kurt Jaeger li...@opsec.eu escribió:

 Hi!

   Could any commiter take care of
   https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197378
   that updates devel/visualparadigm with a hotfix just released by the
   upstream project?
 
  I'm testing it right now.

 It's committed.

Thanks!


 --
 p...@opsec.eu+49 171 3101372 5 years to
go !
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Hotfix and unbreak update that need to be commited

[Fernando Apesteguía]

Could any commiter take care of
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197378
that updates devel/visualparadigm with a hotfix just released by the
upstream project?

Please note that there was a previous yet-to-be-commited bug report
(https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197108) that is
subdued by the one above.

And if the commiter is kind enough to take care of
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197135 that updates
graphics/opennurbs since it seems to break cad/qcad
(https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=187506) due to a
nasty zlib miss interaction, it would be really appreciated :)

Thanks in advance.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Hotfix and unbreak update that need to be commited

[Fernando Apesteguía]

El 06/02/2015 21:38, Kurt Jaeger li...@opsec.eu escribió:

 Hi!

  Could any commiter take care of
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197378
  that updates devel/visualparadigm with a hotfix just released by the
  upstream project?

 I'm testing it right now.

  Please note that there was a previous yet-to-be-commited bug report
  (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197108) that is
  subdued by the one above.

 So I've closed that older PR as it's superseded by the newer PR.

  And if the commiter is kind enough to take care of
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197135 that updates

 Done.

  graphics/opennurbs since it seems to break cad/qcad
  (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=187506) due to a
  nasty zlib miss interaction, it would be really appreciated :)

 Closed 187506 as resolved. I did not do run-tests, as I have no
 pratical experience with those programs, but if its broken,
 please open a new PR.

Ok. Thanks!


 --
 p...@opsec.eu+49 171 3101372 5 years to
go !
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Commit needed pkg-fallout related

[Fernando Apesteguía]

Hi,

Could someone please commit bug 195752?

I keep receiving pkg-fallout related emails.

Thanks in advance.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Commit needed pkg-fallout related

[Fernando Apesteguía]

El 15/01/2015 18:59, Baptiste Daroussin b...@freebsd.org escribió:

 On Thu, Jan 15, 2015 at 06:46:03PM +0100, Fernando Apesteguía wrote:
  Hi,
 
  Could someone please commit bug 195752?
 
  I keep receiving pkg-fallout related emails.
 
  Thanks in advance.

 Done sorry for delay.

No worries. Thanks!


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

Re: bugzilla Error 503 Service Unavailable

[Fernando Apesteguía]

El 12/01/2015 21:12, Kurt Jaeger li...@opsec.eu escribió:

 Hi!

  Not sure who to alert to this:
 
  https://bugs.freebsd.org/bugzilla/
 
  Error 503 Service Unavailable
 
  Backend status: Service Unavailable

 Bugzilla is back -- 53 lost PRs have been re-created as best as can be
 done.

 There are updates to PRs missing, both to those 53, and to others.

 gavin@ is trying to fix those he finds more info about, but if you are
 aware of a PR you have updated since 2015-01-07 16:07:14 UTC it would be
 greatly appreciated if you could make the update again.

Thanks for taking bugzilla back online!


 --
 p...@opsec.eu+49 171 3101372 5 years to
go !
 ___
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

compiler:c++11-lib option

[Fernando Apesteguía]

Hi,

I'm having some troubles making graphics/code-eli to compile on
anything below 10.0-RELEASE. The port uses some c++11 functions
(std::cbrt) so I put this line in the Makefile:

USES=   compiler:c++11-lib

However, when I try to compile the port in 9.3, it complains about
cstdlib not being found.

Am I using the option in correctly? What is the expected behavior for
a port that specifies that option in anything below 10?

Thanks in advance.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

QSerialPort

[Fernando Apesteguía]

Hi,

It seems I can't find QSerialPort in the ports collections. It's been
in Qt since 5.1[1] and in ports we have 5.2.1.

However, if I run this:

find ./ -name pkg-plist -exec grep -i qserialport {} \;

the file is not found.

What am I missing?

Thanks in advance.

[1] http://qt-project.org/doc/qt-5/qserialport.html
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Redports and leftovers calculation

[Fernando Apesteguía]

Hi,

While working on a new port, my builds report leftovers as if I'm
wiping out /usr/local on package removal:

https://redports.org//~fernape/20140927175500-61315-248739/code-eli-0.3.6_1.log

However, in my local poudriere, no errors are reported (DEVELOPER=y in
make.conf). To double check, I scheduled a couple of ports that hasn't
changed for some time now and they also report leftover errors in 8.4,
9.3 and 10.0 on both 386 and amd64:

https://redports.org/~fernape/20140927222153-93684-248759/converseen-0.8.3.log
https://redports.org/~fernape/20140927222153-93684-248761/converseen-0.8.3.log
https://redports.org/~fernape/20140927222153-93684-248763/converseen-0.8.3.log
https://redports.org/~fernape/20140927222131-06702-248753/visualparadigm-11.1.log
https://redports.org/~fernape/20140927222131-06702-248755/visualparadigm-11.1.log
https://redports.org/~fernape/20140927222131-06702-248757/visualparadigm-11.1.log

and other weird errors too:

https://redports.org/~fernape/20140928122044-85175-248808/.txz.log

Can anyone please confirm these?

Thanks in advance.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Redports and leftovers calculation

[Fernando Apesteguía]

El 28/09/2014 14:45, A.J. 'Fonz' van Werven free...@skysmurf.nl
escribió:

 Fernando Apestegu??a wrote:

  While working on a new port, my builds report leftovers as if I'm
  wiping out /usr/local on package removal:
 [snip]
  Can anyone please confirm these?

 It's a known problem. The main suspicion is that the recent changes to
 ports-mgmt/pkg have broken Tinderbox, which in turn is what drives
 Redports.

If it is known, it would be nice to have an entry in redport's blog.


 AvW

 --
 Imbibo, ergo sum.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Redports and leftovers calculation

[Fernando Apesteguía]

El 28/09/2014 22:31, Bryan Drewery bdrew...@freebsd.org escribió:

 On 9/28/2014 7:42 AM, Fernando Apesteguía wrote:
  Hi,
 
  While working on a new port, my builds report leftovers as if I'm
  wiping out /usr/local on package removal:
 
 
https://redports.org//~fernape/20140927175500-61315-248739/code-eli-0.3.6_1.log

 Yes. The truth is that Tinderbox (which Redports uses) has been wrong
 about QA since at least April 2014. The recent Pkg changes have only
 made it a little more obvious.

 Someone really needs to fix Tinderbox. The list of work is here:
 https://people.freebsd.org/~bdrewery/tinderbox-work.txt

 I suggest people stop using Redports for QA. It is only useful for
 checking if it builds - not if it packages or has plist/QA issues.

Thanks for the info.

Just in case someone misses this thread, a note in the blog would be really
useful, I think.


 --
 Regards,
 Bryan Drewery

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

Re: On Docs option and custom build target

[Fernando Apesteguía]

El 26/09/2014 08:40, Mathieu Arnold m...@freebsd.org escribió:

 +--On 23 septembre 2014 23:23:31 +0200 Fernando Apesteguía
 fernando.apesteg...@gmail.com wrote:
 |
 | do-build:
 | @cd ${BUILD_WRKSRC}/  ${MAKE}
 | .if ${PORT_OPTIONS:MDOCS}
 | @cd ${BUILD_WRKSRC}/  ${MAKE_CMD} doc
 | .endif
 |

 That should be:

 ALL_TARGET= all
 DOCS_ALL_TARGET=doc

 And then you don't need to include port.options.mk.

 As explained in
 
https://www.freebsd.org/doc/en/books/porters-handbook/makefile-options.html#options-variables



Changed. Thanks!

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

Re: On Docs option and custom build target

[Fernando Apesteguía]

On Thu, Sep 25, 2014 at 12:06 PM, Tijl Coosemans t...@freebsd.org wrote:
 On Wed, 24 Sep 2014 23:54:19 +0200 Fernando Apesteguía 
 fernando.apesteg...@gmail.com wrote:
 On Wed, Sep 24, 2014 at 8:52 PM, Tijl Coosemans t...@freebsd.org wrote:
 On Tue, 23 Sep 2014 23:23:31 +0200 Fernando Apesteguía 
 fernando.apesteg...@gmail.com wrote:
 I have a Makefile for an application that provides both examples and
 documentation. I created the two options in the Makefile (both enabled
 by default).
 The package doesn't provide any flags stock like --with-docs or
 --with-examples, so I have a custom target like this:

 do-build:
 @cd ${BUILD_WRKSRC}/  ${MAKE}
 .if ${PORT_OPTIONS:MDOCS}
 @cd ${BUILD_WRKSRC}/  ${MAKE_CMD} doc
 .endif

 You don't have to override do-build like this.  You can build the
 documentation from a post-build target.

 Thanks. Changed.

 However, when I try to run this in poudriere, I get the following error:

 make[1]: don't know how to make doc. Stop

 make[1]: stopped in /wrkdirs/usr/ports/graphics/code-eli/work/.build
 *** Error code 2

 Does the makefile in BUILD_WRKSRC actually have a doc target?  Is doc
 a subdirectory maybe?

 Yes it does.

 In fact, with port test builds fine with the same code (change
 directory and ${MAKE} doc). There is a doc.dir subdirectory in
 BUILD_WRKSRC/CMakeFiles. The doc target basically gets a Doxygen
 configuration file and runs doxygen on the whole library code.

 Poudriere tests the port in a clean environment so check the build log
 to see if any dependencies (like doxygen) are missing.

That's it!

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

Re: On Docs option and custom build target

[Fernando Apesteguía]

On Wed, Sep 24, 2014 at 8:52 PM, Tijl Coosemans t...@freebsd.org wrote:
 On Tue, 23 Sep 2014 23:23:31 +0200 Fernando Apesteguía 
 fernando.apesteg...@gmail.com wrote:
 I have a Makefile for an application that provides both examples and
 documentation. I created the two options in the Makefile (both enabled
 by default).
 The package doesn't provide any flags stock like --with-docs or
 --with-examples, so I have a custom target like this:

 do-build:
 @cd ${BUILD_WRKSRC}/  ${MAKE}
 .if ${PORT_OPTIONS:MDOCS}
 @cd ${BUILD_WRKSRC}/  ${MAKE_CMD} doc
 .endif

 You don't have to override do-build like this.  You can build the
 documentation from a post-build target.

Thanks. Changed.


 However, when I try to run this in poudriere, I get the following error:

 make[1]: don't know how to make doc. Stop

 make[1]: stopped in /wrkdirs/usr/ports/graphics/code-eli/work/.build
 *** Error code 2

 Does the makefile in BUILD_WRKSRC actually have a doc target?  Is doc
 a subdirectory maybe?

Yes it does.

In fact, with port test builds fine with the same code (change
directory and ${MAKE} doc). There is a doc.dir subdirectory in
BUILD_WRKSRC/CMakeFiles. The doc target basically gets a Doxygen
configuration file and runs doxygen on the whole library code.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

On Docs option and custom build target

[Fernando Apesteguía]

Hi,

I have a Makefile for an application that provides both examples and
documentation. I created the two options in the Makefile (both enabled
by default).
The package doesn't provide any flags stock like --with-docs or
--with-examples, so I have a custom target like this:

do-build:
@cd ${BUILD_WRKSRC}/  ${MAKE}
.if ${PORT_OPTIONS:MDOCS}
@cd ${BUILD_WRKSRC}/  ${MAKE_CMD} doc
.endif

(Just FYI, the enabling/disabling of the examples is done in the
post-patch target by modifying a CMakeList.txt...)

I tried the four combinations of the options through port test and
everything went fine.

However, when I try to run this in poudriere, I get the following error:

make[1]: don't know how to make doc. Stop

make[1]: stopped in /wrkdirs/usr/ports/graphics/code-eli/work/.build
*** Error code 2

Since it builds the normal package, and it tries to execute make doc,
it was able to change the directory to BUILD_WRKSRC.

I assume I'm doing something fundamentally wrong, but I can't figure
out what it is.

Any help is appreciated.

Thanks in advance.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Place of LICENSE_FILE in Makefile

[Fernando Apesteguía]

El 19/09/2014 21:10, Brooks Davis bro...@freebsd.org escribió:

 On Fri, Sep 19, 2014 at 08:35:36PM +0200, Fernando Apestegu?a wrote:
  Hi,
 
  I'm facing a situation with a new Makefile.
  I want to set LICENSE_FILE to the location of the license file of the
  distribution. The file is located under ${WRKSRC} that has been set to
  ${WRKDIR}/${GH_ACCOUNT}-${GH_PROJECT}-${GH_COMMIT}
 
  If I use LICENSE_FILE _after_ setting WRKSRC, I get an error from
  portlint. Also, all the GH_* variables need to be set before I can use
  them to point LICENSE_FILE to the proper path, so... in which order
  should I define these variables so portlint doesn't complain?

 It should not matter that the variable are not yet defined.  Variables
 are expanded at point of use not point of assignment.

Ok, thanks!


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

Place of LICENSE_FILE in Makefile

[Fernando Apesteguía]

Hi,

I'm facing a situation with a new Makefile.
I want to set LICENSE_FILE to the location of the license file of the
distribution. The file is located under ${WRKSRC} that has been set to
${WRKDIR}/${GH_ACCOUNT}-${GH_PROJECT}-${GH_COMMIT}

If I use LICENSE_FILE _after_ setting WRKSRC, I get an error from
portlint. Also, all the GH_* variables need to be set before I can use
them to point LICENSE_FILE to the proper path, so... in which order
should I define these variables so portlint doesn't complain?

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