Re: Keeping -CURRENT up to date with Poudriere

[Ben Lavery-Griffiths]

Thanks very much,

I’ll look into doing similar.

Thanks again,
Ben

> On 18 Jun 2017, at 20:56, Ultima <ultima1...@gmail.com> wrote:
> 
> Poudriere will update based on how it initially was created
> unless it was modified in 
> /usr/local/etc/poudriere.d/jails/$JAIL/method. For the
> -STABLE and -CURRENT branch, It *may* somehow be
> obtained another way, but usually it has to be compiled
> from the respected branch. So it needs to be manually
> compiled in /usr/src before doing a poudriere update.
> 
> The way I handle multiple branches is adding adding
> multiple in /usr/src, eg /usr/src/head, /usr/src/11-stable,
> then setting the src in that directory with obj in it as well.
> 
> /usr/src/head/src and obj /usr/src/head/obj the method
> will need to be set to src=/usr/src/head/src and object
> export MAKEOBJDIRPREFIX=/usr/src/head/obj in the
> ${JAIL}-poudriere.conf.
> 
> I also make a dataset for each target branch so it can
> be zfs send/received.
> 
> 
> I hope this helps
> Ultima
> 
> On Sun, Jun 18, 2017 at 9:49 AM, Ben Lavery-Griffiths 
> <ben.lav...@hashbang0.com <mailto:ben.lav...@hashbang0.com>> wrote:
> Hi all,
> 
> I’ve got a 12.0-CURRENT Poudriere jail for ports testing.  Am I right in 
> thinking that when Poudriere updates a jail it uses freebsd-update?  In which 
> case, -STABLE and -CURRENT jails can’t be updated - correct?
> 
> In this case, if I want to get the latest -STABLE or -CURRENT snapshot, will 
> I need to recreate my jail?  Or can Poudriere do it a different way?
> 
> Currently when I try to update I get this:
> 
> > [00:00:00] >> Upgrading using ftp
> > /etc/resolv.conf -> /poudriere/jails/12Ci386/etc/resolv.conf
> > mount: /poudriere/jails/12Ci386/compat: No such file or directory
> > Bad system call (core dumped)
> > 12.0-CURRENT
> > [00:00:01] >> Recording filesystem state for clean… done
> 
> 
> Many thanks,
> Ben
> ___
> freebsd-ports@freebsd.org <mailto:freebsd-ports@freebsd.org> mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports 
> <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org 
> <mailto: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"

Keeping -CURRENT up to date with Poudriere

[Ben Lavery-Griffiths]

Hi all,

I’ve got a 12.0-CURRENT Poudriere jail for ports testing.  Am I right in 
thinking that when Poudriere updates a jail it uses freebsd-update?  In which 
case, -STABLE and -CURRENT jails can’t be updated - correct?

In this case, if I want to get the latest -STABLE or -CURRENT snapshot, will I 
need to recreate my jail?  Or can Poudriere do it a different way?

Currently when I try to update I get this:

> [00:00:00] >> Upgrading using ftp
> /etc/resolv.conf -> /poudriere/jails/12Ci386/etc/resolv.conf
> mount: /poudriere/jails/12Ci386/compat: No such file or directory
> Bad system call (core dumped)
> 12.0-CURRENT
> [00:00:01] >> Recording filesystem state for clean… done


Many thanks,
Ben
___
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"

Upgraded

[Ben Lavery]

Afternoon all,

I've just updated a port I maintain (gohugo) for the first time. I've made 
changes to the Makefile, distinfo and pkg-plist files, then made an svn diff 
and attached that to a bug 
(https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213309 
).  Do I now just 
wait for a committer to review and feedback/commit?  Or should I be asking for 
someone to look at it?  Appreciate this might work like asking for it, but 
wanted to know the procedure from here.

Many thanks,
Ben
___
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: codecvt and libc++ on FreeBSD 9.x

[Ben Lavery]

On 09/01/16 20:59, Michelle Sullivan wrote:

Ben Lavery wrote:



On the submission
(https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212278) CPM has
said of the issue "Second it seems that codecvt is missing, so it
needs libc++ support" - but I'm not sure how to add this.  I've tried
adding the following which I found in multiple threads on the forums,
but to no avail:

CC=clang
CXX=clang++
CPP=clang-cpp
WITH_LIBCPLUSPLUS=yes

I *think* this is because clang is too old on FreeBSD 9.3?  But I'm
not sure if I can/should reference a newer version from ports (and how
to go about this in the proper way), and how to make this apply to
FreeBSD 9.x only as it works fine "as is" on FreeBSD 10.


Did you go with the base compiler or use the clang in ports?

You might want to do that - you can also probably use GCC which is also
available in ports.

Regards,

Michelle


Yes I did am using the base compiler, I know I can do a "BUILD_DEPENDS" 
to ensure a port (e.g. lang/clang35 would do, I think) is available at 
build time, but I'm unsure:

a) if that will indeed solve my issue
b) how to ensure this doesn't affect FreeBSD 10 and above builds - if 
there some kind of ".if FreeBSd 9"?
c) how to ensure cmake uses the ports version of clang rather than base 
- would I modify the variables I mentioned in my original post?


Many thanks,
Ben

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

codecvt and libc++ on FreeBSD 9.x

[Ben Lavery]

Good evening all,

Fairly new to porting and I've tried porting what I thought would be a 
trivial program, bunnysay.  Written in C++ I've patched the code to work 
on FreeBSD 10, however it doesn't work on FreeBSD 9 because I've 
included codecvt.


It fails with the following error and I'm feeling a little out of my depth:

===>  Building for bunnysay-1.0
[ 50%] Building CXX object CMakeFiles/bunnysay.dir/src/BunnySay.cpp.o
In file included from 
/root/bunnysay/work/bunnysay-1.0/src/BunnySay.cpp:22:0:
/root/bunnysay/work/bunnysay-1.0/src/BunnySay.h:33:19: fatal error: 
codecvt: No such file or directory

 #include 
   ^
compilation terminated.
*** [CMakeFiles/bunnysay.dir/src/BunnySay.cpp.o] Error code 1
1 error
*** [CMakeFiles/bunnysay.dir/all] Error code 2
1 error
*** [all] Error code 2
1 error
*** [do-build] Error code 2

Stop in /root/bunnysay.



On the submission 
(https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212278) CPM has said 
of the issue "Second it seems that codecvt is missing, so it needs 
libc++ support" - but I'm not sure how to add this.  I've tried adding 
the following which I found in multiple threads on the forums, but to no 
avail:


CC=clang
CXX=clang++
CPP=clang-cpp
WITH_LIBCPLUSPLUS=yes

I *think* this is because clang is too old on FreeBSD 9.3?  But I'm not 
sure if I can/should reference a newer version from ports (and how to go 
about this in the proper way), and how to make this apply to FreeBSD 9.x 
only as it works fine "as is" on FreeBSD 10.


Many thanks for any advice and words of wisdom.

Ben

___
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: Restricted character set for Github repo names?

[Ben Lavery]

Thanks Jan,

For some reason it didn't like the GH_TUPLE - although it didn't
complain the tar.gz wasn't fetched...

I renamed the :group as you suggested, make(1) is happy and the
files are fetched!

Thanks again,
Ben

On 07/14/16 07:43, Jan Beich wrote:
> Ben Lavery <ben.lav...@hashbang0.com> writes:
> 
>> Hello all,
>>
>> This is my first port, I’m trying to port http://gohugo.io so I may have 
>> missed something.
>>
>> I’ve got my Makefile (copy:
>> https://manaha.co.uk/logsnstuff/gohugo_Makefile_WIP_broken ) but on
>> 10.3 it fails with the following:
>>
>>> _MASTER_SITES_go-md2man=https://codeload.github.com/cpuguy83/go-md2man/tar.gz/2724a9c?dummy=/:
>>> not found
>>> *** Error code 127
> 
> Try using :group names that're also valid as part of sh(1) variables.
> 
>   GH_ACCOUNT= ... cpuguy83:go-md2man
>   GH_PROJECT= ... go-md2man:go-md2man
>   GH_TAGNAME= ... 2724a9c:go-md2man
> 
> replace with
> 
>   GH_ACCOUNT= ... cpuguy83:go_md2man
>   GH_PROJECT= ... go-md2man:go_md2man
>   GH_TAGNAME= ... 2724a9c:go_md2man
> 
> or
> 
>   GH_TUPLE=   ... cpuguy83:go-md2man:2724a9c:go_md2man
> 
> also see https://svnweb.freebsd.org/changeset/ports/417113
> 

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

Restricted character set for Github repo names?

[Ben Lavery]

Hello all,

This is my first port, I’m trying to port http://gohugo.io so I may have missed 
something.

I’ve got my Makefile (copy: 
https://manaha.co.uk/logsnstuff/gohugo_Makefile_WIP_broken ) but on 10.3 it 
fails with the following:

> _MASTER_SITES_go-md2man=https://codeload.github.com/cpuguy83/go-md2man/tar.gz/2724a9c?dummy=/:
>  not found
> *** Error code 127


When I tried it on an 11-BETA VM and looked at all errors I got the following:

> + echo 'The 
> https://codeload.github.com/cpuguy83/go-md2man/tar.gz/2724a9c?dummy=/:go-md2man
>  MASTER_SITES line has'
> The 
> https://codeload.github.com/cpuguy83/go-md2man/tar.gz/2724a9c?dummy=/:go-md2man
>  MASTER_SITES line has
> echo "a group with invalid characters, only use [a-zA-Z0-9_]"
> Execute: 'echo "a group with invalid characters, only use [a-zA-Z0-9_]”'



I then forked the repository to my own Github account and removed the hyphen 
from the repo name.  Modifying my Makefile (copy: 
https://manaha.co.uk/logsnstuff/gohugo_Makefile_WIP ) it now downloads the 
repository without an issue.

Is this expected behaviour?  Is it like this for a specific reason?

Kind regards,
Ben


signature.asc
Description: Message signed with OpenPGP using GPGMail