Re: How to see errors with poudriere?
On Fri, Mar 22, 2013 at 2:11 PM, John Marino wrote: > I wouldn't be so quick to blame poudriere. > I'm not interested in "blaming" anyone... it is probably a config problem. I simply asked how to get the error output for a port built inside poudriere. And this: > e.g. look in /usr/local/poudriere/data/**logs/ > was the answer. 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: How to see errors with poudriere?
2013/3/22 J David > We are rapidly converting all of our ports-building infrastructure to > poudriere, which is a fantastic tool and has been a huge improvement for > us. > > However, I do run across the occasional stubborn ports that refuse to build > (example: lang/ghc) under poudriere, and I'm not sure how to debug this. > > I am pretty sure this is possible/easy and I'm just being stupid. If > anyone would mind giving me a shove in the right direction, I would really > appreciate it. > > You just should edit poudriere.conf to enable problem's storing SAVE_WRKDIR=yes # Choose the default format for the workdir packing: could be tar,tgz,tbz,txz # default is tbz # WRKDIR_ARCHIVE_FORMAT=tbz If that's not enough, there is something really wrong with port :) 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" > -- Regards, Alexander Yerenkow ___ 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: How to see errors with poudriere?
On 3/22/2013 18:51, J David wrote: We are rapidly converting all of our ports-building infrastructure to poudriere, which is a fantastic tool and has been a huge improvement for us. However, I do run across the occasional stubborn ports that refuse to build (example: lang/ghc) under poudriere, and I'm not sure how to debug this. I am pretty sure this is possible/easy and I'm just being stupid. If anyone would mind giving me a shove in the right direction, I would really appreciate it. I wouldn't be so quick to blame poudriere. There are many ports that won't build in poudriere due to problems with the port makefiles. In fact, I've only seen one legitimate case of a port that was fine but poudriere erroneously didn't build it. The rest were problems that poudriere flagged. You have to look at the log and see what the problem is, then report the problem via PR. e.g. look in /usr/local/poudriere/data/logs/ John ___ 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"
How to see errors with poudriere?
We are rapidly converting all of our ports-building infrastructure to poudriere, which is a fantastic tool and has been a huge improvement for us. However, I do run across the occasional stubborn ports that refuse to build (example: lang/ghc) under poudriere, and I'm not sure how to debug this. I am pretty sure this is possible/easy and I'm just being stupid. If anyone would mind giving me a shove in the right direction, I would really appreciate 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"
