Re: emulators/wine-devel fails on FreeBSD 10.0-STABLE i386 on emulators/dosbox
from Tom Carrick: Sorry for the delay, I've been away, and forgot to get back to you when I returned. I'm aware of the issue, here is a link to the ticket (with a possible fix): https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191630 The port is quite old (dosbox releases are very infrequent lately despite active development) so it won't use your updated SDL. If you want to make a patch for the port to allow newer versions of SDL, I'd be happy to accept it, though I'd appreciate if you waited until the current issue is fixed. I remembered this inquiry about failed DOSBox in the back of my mind but had practically given up on getting a reply. Better late than never! You don't have to quote my entire message twice (second time being in HTML quoted-printable). I noticed upstream that DOSBox releases were very infrequent. I'll check your link when I get to a better interface, am now in a console (NetBSD-current DRMKMS, looks identical to FreeBSD-current vt after returning from X, but X here won't start, and no mouse copy-and-paste, but working Ethernet unlike FreeBSD). I need to look at the Porter's Handbook (long overdue for that!), see how to use SDL2. Maybe wait for DOSBox fix, if it doesn't take too long, but it stopped me from building Wine. Tom ___ 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: problem upgrading ejabberd
On Thu, 31 Jul 2014 16:01:47 +0200
Marko Cupać marko.cu...@mimar.rs wrote:
Hi,
I have problem updating ejabberd-14.05 to ejabberd-14.07 with
portmaster on FreeBSD 9.2-RELEASE-p10 amd64.
I am mounting ports dir from another server (partial output of mount
command):
nfs01.example.com:/usr/ports on /usr/ports (nfs, read-only)
nfs01.example.com:/usr/ports/distfiles on /usr/ports/distfiles (nfs)
nfs01.example.com:/usr/ports/packages on /usr/ports/packages (nfs)
This is in my make.conf:
WITH_PKGNG=yes
WRKDIRPREFIX=/tmp
WITH_OPENSSL_PORT=yes
Here's the error:
=== Building for ejabberd-14.07
rm -rf deps/.got
rm -rf deps/.built
/usr/local/lib/erlang/bin/escript rebar get-deps : deps/.got
ERROR: Failed to extract name
from
/tmp/usr/ports/net-im/ejabberd/work/ejabberd-14.07/deps/lhttpc/src/lhttpc.app.src:
{27, file_io_server, invalid_unicode}
gmake: *** [deps/.got] Error 1
=== Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the
failure to the maintainer.
*** [do-build] Error code 1
Stop in /usr/ports/net-im/ejabberd.
*** [build] Error code 1
Stop in /usr/ports/net-im/ejabberd.
=== make build failed for net-im/ejabberd
=== Aborting update
=== You can restart from the point of failure with this command
line: portmaster flags net-im/ejabberd
I managed to build it after disabling HTTP option.
--
Marko Cupać
___
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
Any users of www/mod_auth_form
Hello @all, currently being the maintainer of www/mod_auth_form I'm asking if some1 is using it. The upstream site is gone, the developer seems unavailable too so the source code isn't under active development too. I still have the source and can over-take hosting, still there won't be any security related fixes (and there may be some, or maybe not). The port isn't currently staged, which would be no problem to fix - though the module isn't compatible with Apache 2.4.x (and upwards). So if there's no active user interest, maybe it would be better to remove the port to prevent users from installing (potentially unsafe) software used for handling authentication / protection of websites. 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
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ math/atlas-devel| 3.9.11 | 3.11.29 +-+ net-mgmt/pandorafms_agent | 4.0.1 | 5.1-140808 +-+ net-mgmt/pandorafms_console | 4.0.1 | 5.1-140808 +-+ net-mgmt/pandorafms_server | 4.0.1 | 5.1-140808 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt 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: Apache 24 + mod_perl
Hmmm... well, it looks like you need to update the procedures from RedHat which build the mod_perl. I don't think you can build a FreeBSD port on a Linux system, although stranger things have happened. On 08/06/14 19:43, Jie Gao wrote: The patch, or rather the patching itself, does not work with a box of Red Hat Enterprise Linux Server release 6.5 for me here. Regards, Jie * Patrick Powell papow...@astart.com wrote: Date: Wed, 6 Aug 2014 17:27:15 -0700 From: Patrick Powell papow...@astart.com To: olli hauer oha...@gmx.de CC: Steve Hay steve.m@googlemail.com, Kurt Jaeger li...@opsec.eu, po...@freebsd.org, modp...@perl.apache.org modp...@perl.apache.org Subject: Re: Apache 24 + mod_perl User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130714 Thunderbird/17.0.7 On 08/06/14 14:34, olli hauer wrote: On 2014-08-06 22:45, Patrick Powell wrote: On 08/06/14 00:19, Steve Hay wrote: On 3 August 2014 22:13, Patrick Powell papow...@astart.com wrote: On 08/03/14 08:25, olli hauer wrote: On 2014-08-01 23:34, Kurt Jaeger wrote: Hi! Question: when will mod_perl be available for Apache 24? There's a PR where people are discussing this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191471 This PR needs more testers etc. I've updated the PR with a patch against the latest mod_perl trunk revision (r1602105). The patch against the port can be grabbed from here or from our bugzilla http://people.freebsd.org/~ohauer/diffs/apache/mod_perl2-2.0.8_apache24.diff Please test *at own risk*, and report issues to upstream and here so we can integrate fresh upstream fixes and update the port. The first proposed patch will allows the port to build but I have to many concerns for integrating this simple fix into the tree. I don't believe the first patch on the PR will work right else it would take the upstream dev. work and time for mod_perl2 at absurdI -um ... I have taken a slightly different approach, using the mod_perl2 SVN /httpd24 branch as the starting point. The httpd24 branch is obselete. It was used for the initial development of httpd-2.4 support, but was superseded by httpd24threading, and since then everything from both branches has been merged back to trunk. The current trunk is largely ready for a 2.0.9 release supporting httpd-2.4, pending some more testing and fixes as necessary. I tried using the trunk a couple of days ago and it did not compile. Just to make sure that I am using the right SVN respository and branch, what is the URL of the trunk SVN repository? I am more than happy to try testing mod_perl. Hm, with the following patch applied to www/mod_perl2 it builds fine for me on FreeBSD 8.4 / 10.0 (amd64) an apache-2.4.10 http://people.freebsd.org/~ohauer/diffs/apache/mod_perl2-2.0.8_apache24.diff The patch does some adjustments in the port / pkg-plist and fetches a complete archive containing all patches so the sources are the same as the upstream (r1602105) trunk/httpd24threade branch. After applying the patch and using the command `make patch' it is easy to compare the sources against upstream sources (check out before) http://svn.apache.org/repos/asf/perl/modperl/branches/httpd24threading http://svn.apache.org/repos/asf/perl/modperl/trunk Easiest way to apply the patch against the unmodified port: $ cd www/mod_perl2 $ fetch http://people.freebsd.org/~ohauer/diffs/apache/mod_perl2-2.0.8_apache24.diff $ patch -p1 mod_perl2-2.0.8_apache24.diff PS: I've updated the patch because it needs some additional handling for pkg-plist if build against apache-2.2.x (Provider.pm/Provider.so) I tried your procedure (see above). The patch applied, I was able to compile the mod_perl, and 'make test' ran and it passed all of the critical tests. I then ran some more of my tests for the functionality it used. These passed. I would say that unless somebody else comes up with a problem that I would use this as a baseline for distribution/installation. That is, I would put up the modified Makefile, with a warning, but would allow people to make/install it by specifying an option such as make IGNORE_WARNING=yes Of course, the FreeBSD Ports team may have different views on this... but until the upstream mod_perl team puts out mod_perl-2.0.9 officially I think that this is the best we can do. Also, some more testers will be able to try it out and report any problems ___ 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
pkg 1.3.5.1 - Assertion failed
I am setting up a new system which needs KDE. Note that
I set up a similar system a couple of weeks ago using the new_xorg
repository and the installation worked fine (OK, as well
as an installation on a new OS, new system, new Video Card,
and a set of new applications works). When I try to repeat
this I now get following error:
# pkg install x11/kde4
Updating repository catalogue
FreeBSD repository is up-to-date
FreeBSD_new_xorg repository is up-to-date
All repositories are up-to-date
Assertion failed: (var == elt-var), function pkg_solve_sat_problem,
file pkg_solv
e.c, line 508.
Child process pid=1384 terminated abnormally: Abort trap: 6
Setup: FreeBSD 9.3-Release, amd 64
pkg: pkg-1.3.5.1
Repositories:
/etc/pkg/FreeBSD.conf:
# $FreeBSD: releng/9.3/etc/pkg/FreeBSD.conf 263939 2014-03-30 15:30:33Z
bdrewery $
#
# To disable this repository, instead of modifying or removing this file,
# create a /usr/local/etc/pkg/repos/FreeBSD.conf file:
#
# mkdir -p /usr/local/etc/pkg/repos
# echo FreeBSD: { enabled: no } /usr/local/etc/pkg/repos/FreeBSD.conf
#
FreeBSD: {
url: pkg+http://pkg.FreeBSD.org/${ABI}/latest;,
mirror_type: srv,
signature_type: fingerprints,
fingerprints: /usr/share/keys/pkg,
enabled: yes
}
/usr/local/etc/pkg/repos/FreeBSD.conf:
FreeBSD: {
url: pkg+http://pkg.FreeBSD.org/${ABI}/latest;,
mirror_type: srv,
enabled: yes
}
/usr/local/etc/pkg/repos/FreeBSD_new_xort.conf:
# /usr/local/etc/pkg/repos/FreeBSD_new_xorg.conf
# It is still required to have /etc/pkg/FreeBSD.conf installed and enabled.
# If that file is missing or if /usr/share/keys/pkg is missing see:
# http://www.freebsd.org/security/advisories/FreeBSD-EN-14:03.pkg.asc
FreeBSD_new_xorg: {
url: pkg+http://pkg.FreeBSD.org/${ABI}/new_xorg;,
mirror_type: srv,
signature_type: fingerprints,
fingerprints: /usr/share/keys/pkg,
enabled: yes
}
___
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
poudriere: setting up jail failes
Hello, I'm setting up a jail with poudriere(8) to compile my ports; after some hours it is crashing with: # poudriere jail -c -j freebsd-head -m svn+http -v head ; date ... Making hierarchy -- cd /usr/local/poudriere/jails/freebsd-head/usr/src; make -f Makefile.inc1 LOCAL_MTREE= hierarchy cd /usr/local/poudriere/jails/freebsd-head/usr/src/etc PATH=/usr/obj/usr/local/poudriere/jails/freebsd-head/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/local/poudriere/jails/freebsd-head/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/local/poudriere/jails/freebsd-head/usr/src/tmp/legacy/usr/games:/usr/obj/usr/local/poudriere/jails/freebsd-head/usr/src/tmp/legacy/bin:/usr/obj/usr/local/poudriere/jails/freebsd-head/usr/src/tmp/usr/sbin:/usr/obj/usr/local/poudriere/jails/freebsd-head/usr/src/tmp/usr/bin:/usr/obj/usr/local/poudriere/jails/freebsd-head/usr/src/tmp/usr/games:/usr/obj/usr/local/poudriere/jails/freebsd-head/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/local/poudriere/jails/freebsd-head/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/local/poudriere/jails/freebsd-head/usr/src/tmp/legacy/usr/games:/usr/obj/usr/local/poudriere/jails/freebsd-head/usr/src/tmp/legacy/bin:/usr/obj/usr/local/poudriere/jails/freebsd-head/usr/src/tmp/usr/sbin:/usr/obj/usr/local/poudriere/jails/freebsd-head/usr/src/tmp/usr/bin:/usr/obj/usr/local/poudriere/jails/freebsd-head/usr /src/tmp/usr/games:/tmp/install.l1aks4sC make LOCAL_MTREE= distrib-dirs mtree -N /usr/local/poudriere/jails/freebsd-head/usr/src/etc -deU -f /usr/local/poudriere/jails/freebsd-head/usr/src/etc/mtree/BSD.root.dist -p /usr/local/poudriere/jails/freebsd-head/ mtree: illegal option -- N usage: mtree [-LPUcdeinqruxw] [-f spec] [-f spec] [-K key] [-k key] [-p path] [-s seed] [-X excludes] *** Error code 1 Stop. make[4]: stopped in /usr/local/poudriere/jails/freebsd-head/usr/src/etc *** Error code 1 ... make: stopped in /usr/local/poudriere/jails/freebsd-head/usr/src Error: Failed to 'make installworld' Error while creating jail, cleaning up. Removing freebsd-head jail... done The host where poudriere is running is: # uname -a FreeBSD vm-tiny-r255948 10.0-ALPHA4 FreeBSD 10.0-ALPHA4 #1: Fri Oct 18 12:10:57 CEST 2013 g...@aurora.sisis.de:/usr/obj/usr/src/sys/GENERIC i386 i.e. a CURRENT from Oct 2013 (r255948). Does this mean I should update the host where poudriere is running before? Thanks matthias -- Matthias Apitz | /\ ASCII Ribbon Campaign: E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X- No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards | en.wikipedia.org/wiki/ASCII_Ribbon_Campaign ___ 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
HELLO
GREETINGS MY FRIEND. MY NAME IS (MISS. FATIN ABDUL) AM FROM KUWAIT,BEAUTIFUL, YOUNG GIRL, WITH FAITHFUL, LOVING, TENDER, SIMPLE-MINDED PERSON, OBEDIENT, LOYAL, HONEST, CARING, LOVELY, UNDERSTANDABLE,SINCERE, RELIABLE I AM SERIOUSLY LOOKING FOR A PARTNER I WANT TO INVEST IN YOUR COUNTRY UNDER YOUR CONTROL AS MY BUSINESS MANAGER AND I NEED YOUR COLLABORATION IN A PARTNERSHIP BUSINESS IN YOUR COUNTRY. FOR MORE DETAILS PLEASE WRITE ME THROUGH PERSONAL EMAIL AT (fatin_abdulmoham...@outlook.com ) YOURS FAITHFUL MISS. FATIN ABDUL ___ 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: poudriere: setting up jail failes
On 8/8/2014 11:46 AM, Matthias Apitz wrote: Hello, I'm setting up a jail with poudriere(8) to compile my ports; after some hours it is crashing with: # poudriere jail -c -j freebsd-head -m svn+http -v head ; date [...] mtree: illegal option -- N usage: mtree [-LPUcdeinqruxw] [-f spec] [-f spec] [-K key] [-k key] [-p path] [-s seed] [-X excludes] *** Error code 1 [...] The host where poudriere is running is: # uname -a FreeBSD vm-tiny-r255948 10.0-ALPHA4 FreeBSD 10.0-ALPHA4 #1: Fri Oct 18 12:10:57 CEST 2013 g...@aurora.sisis.de:/usr/obj/usr/src/sys/GENERIC i386 i.e. a CURRENT from Oct 2013 (r255948). Does this mean I should update the host where poudriere is running before? Yes. For you it is fixed in stable/10 r257460 (which was in before 10.0 release) which added -N to mtree. There was a lot of polish at the end of 10.0 so you should probably upgrade to at least 10.0 either way. It could be that older releases building 10 and head for Poudriere may be an issue still. I'll have to test more. Specifically the call of 'make distrib-dirs DB_FROM_SRC=1' seemingly not using the itools version of mtree. Also note that running a head jail on a 10.0 system is not really supported. You may run into many weird issues building packages. It's supported to have your host be newer than the jails but not the other way around. Regards, Bryan Drewery signature.asc Description: OpenPGP digital signature
Re: poudriere: setting up jail failes
El día Friday, August 08, 2014 a las 07:12:15PM +0200, Kurt Jaeger escribió: Hi! The host where poudriere is running is: # uname -a FreeBSD vm-tiny-r255948 10.0-ALPHA4 FreeBSD 10.0-ALPHA4 #1: Fri Oct 18 12:10:57 CEST 2013 g...@aurora.sisis.de:/usr/obj/usr/src/sys/GENERIC i386 i.e. a CURRENT from Oct 2013 (r255948). Does this mean I should update the host where poudriere is running before? Yes. Go for 10.0-REL p7, then retry. Can you explain, why? If one looks at the code which is executed in the jail, it looks like this (for better readability I have changed the colons ':' in the PATH by newlines): PATH=/usr/obj/usr/local/poudriere/jails/freebsd-head/usr/src/tmp/legacy/usr/sbin /usr/obj/usr/local/poudriere/jails/freebsd-head/usr/src/tmp/legacy/usr/bin /usr/obj/usr/local/poudriere/jails/freebsd-head/usr/src/tmp/legacy/usr/games /usr/obj/usr/local/poudriere/jails/freebsd-head/usr/src/tmp/legacy/bin /usr/obj/usr/local/poudriere/jails/freebsd-head/usr/src/tmp/usr/sbin /usr/obj/usr/local/poudriere/jails/freebsd-head/usr/src/tmp/usr/bin /usr/obj/usr/local/poudriere/jails/freebsd-head/usr/src/tmp/usr/games /usr/obj/usr/local/poudriere/jails/freebsd-head/usr/src/tmp/legacy/usr/sbin /usr/obj/usr/local/poudriere/jails/freebsd-head/usr/src/tmp/legacy/usr/bin /usr/obj/usr/local/poudriere/jails/freebsd-head/usr/src/tmp/legacy/usr/games /usr/obj/usr/local/poudriere/jails/freebsd-head/usr/src/tmp/legacy/bin /usr/obj/usr/local/poudriere/jails/freebsd-head/usr/src/tmp/usr/sbin /usr/obj/usr/local/poudriere/jails/freebsd-head/usr/src/tmp/usr/bin /usr/obj/usr/local/poudriere/jails/freebsd-head/usr/src/tmp/usr/games /tmp/install.l1aks4sC make LOCAL_MTREE= distrib-dirs mtree -N /usr/local/poudriere/jails/freebsd-head/usr/src/etc -deU -f /usr/local/poudriere/jails/freebsd-head/usr/src/etc/mtree/BSD.root.dist -p /usr/local/poudriere/jails/freebsd-head/ mtree: illegal option -- N usage: mtree [-LPUcdeinqruxw] [-f spec] [-f spec] [-K key] [-k key] [-p path] [-s seed] [-X excludes] *** Error code 1 i.e. the tool 'mtree' is run from a hardcoded PATH from inside the jail which was just compiled. Why the 'mtree' from a Makefile in CURRENT is called with the -N flag, or why the 'mtree' from CURRENT does not understand the -N flag? I do not have a SVN checked out CURRENT to look into at the moment, but I think either the Makefile or mtree is broken in CURRENT. And, btw., why is poudriere removing all the jail when an error occures? Wouldn't it be better to let it there to have a look into and remove it on the next run? -- 6 years to go ! 6 years to go to where or what? Thanks matthias -- Matthias Apitz | /\ ASCII Ribbon Campaign: E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X- No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards | en.wikipedia.org/wiki/ASCII_Ribbon_Campaign ___ 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: poudriere: setting up jail failes
Hi! i.e. a CURRENT from Oct 2013 (r255948). Does this mean I should update the host where poudriere is running before? Yes. Go for 10.0-REL p7, then retry. Can you explain, why? bdrewery@ knows much more about it than I do 8-) I only know that it helps to use a recent system if one tries to debug issues 8-} And: It takes time for others to help if one tries to use some -ALPHA to do recent things... -- p...@opsec.eu+49 171 3101372 6 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: poudriere: setting up jail failes
El día Friday, August 08, 2014 a las 01:43:51PM -0500, Bryan Drewery escribió: Yes. For you it is fixed in stable/10 r257460 (which was in before 10.0 release) which added -N to mtree. There was a lot of polish at the end of 10.0 so you should probably upgrade to at least 10.0 either way. It could be that older releases building 10 and head for Poudriere may be an issue still. I'll have to test more. Specifically the call of 'make distrib-dirs DB_FROM_SRC=1' seemingly not using the itools version of mtree. This is perhaps the problem. Also note that running a head jail on a 10.0 system is not really supported. You may run into many weird issues building packages. It's supported to have your host be newer than the jails but not the other way around. Hmm? The poudriere has the '-m svn' flag for creating jails. If one uses this flag, the jail will always be newer than the host. If this is an issue (which I do not understand if things are done in a jail, using the toolchain of the jail) then this flag should be deleted from poudriere, IMHO. Thanks matthias -- Matthias Apitz | /\ ASCII Ribbon Campaign: E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X- No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards | en.wikipedia.org/wiki/ASCII_Ribbon_Campaign ___ 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: poudriere: setting up jail failes
On 8/8/2014 2:11 PM, Matthias Apitz wrote: El día Friday, August 08, 2014 a las 01:43:51PM -0500, Bryan Drewery escribió: Yes. For you it is fixed in stable/10 r257460 (which was in before 10.0 release) which added -N to mtree. There was a lot of polish at the end of 10.0 so you should probably upgrade to at least 10.0 either way. It could be that older releases building 10 and head for Poudriere may be an issue still. I'll have to test more. Specifically the call of 'make distrib-dirs DB_FROM_SRC=1' seemingly not using the itools version of mtree. This is perhaps the problem. Also note that running a head jail on a 10.0 system is not really supported. You may run into many weird issues building packages. It's supported to have your host be newer than the jails but not the other way around. Hmm? The poudriere has the '-m svn' flag for creating jails. If one uses this flag, the jail will always be newer than the host. If this is an issue (which I do not understand if things are done in a jail, using the toolchain of the jail) then this flag should be deleted from poudriere, IMHO. Thanks matthias The use of -v head from a 10.0 system is the issue. Once you start a build poudriere yells loudly that it is not supported. Major release jumps are not supported. You can usually get away with a head host using a head jail that is a few weeks newer as long as KBI does not change. Doing major releases though can get into trouble with unknown syscalls and different sized structs and capabilities. FreeBSD only tries to be backwards-compatible with its interfaces (among major releases), not guaranteed to be forward or even backwards compatible with head from yesterday. -- Regards, Bryan Drewery signature.asc Description: OpenPGP digital signature
Re: poudriere: setting up jail failes
On 8/8/2014 1:57 PM, Matthias Apitz wrote: And, btw., why is poudriere removing all the jail when an error occures? Wouldn't it be better to let it there to have a look into and remove it on the next run? Yes I agree this should probably change. I'll evaluate it after the 3.1 release which is the major focus right now. The jail command has a lot of issues with building and error handling. -- Regards, Bryan Drewery signature.asc Description: OpenPGP digital signature
Re: poudriere: setting up jail failes
El día Friday, August 08, 2014 a las 02:24:18PM -0500, Bryan Drewery escribió: The use of -v head from a 10.0 system is the issue. Once you start a build poudriere yells loudly that it is not supported. Major release jumps are not supported. You can usually get away with a head host using a head jail that is a few weeks newer as long as KBI does not change. ... OK, thanks. I will update the host to head and try again. Btw: I did not saw any loud yells of poudriere. Maybe, because I went away from the desk when poudriere was doing the SVN checkout and when I came back it was already nicely compiling. Maybe it should ask a question like: Do your really want that new jail on your old system? And wait for the answer :-) Thanks for your time. matthias -- Matthias Apitz | /\ ASCII Ribbon Campaign: E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X- No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards | en.wikipedia.org/wiki/ASCII_Ribbon_Campaign ___ 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: poudriere: setting up jail failes
On 8/8/2014 2:42 PM, Matthias Apitz wrote: El día Friday, August 08, 2014 a las 02:24:18PM -0500, Bryan Drewery escribió: The use of -v head from a 10.0 system is the issue. Once you start a build poudriere yells loudly that it is not supported. Major release jumps are not supported. You can usually get away with a head host using a head jail that is a few weeks newer as long as KBI does not change. ... OK, thanks. I will update the host to head and try again. Btw: I did not saw any loud yells of poudriere. Maybe, because I went away from the desk when poudriere was doing the SVN checkout and when I came back it was already nicely compiling. Maybe it should ask a question like: Do your really want that new jail on your old system? And wait for the answer :-) Thanks for your time. matthias Only in 'bulk', not 'jail'. There's also a securelevel blocker in 'bulk' that is not in 'jail'. Some of these need to move to 'jail' to warn earlier, yes. -- Regards, Bryan Drewery signature.asc Description: OpenPGP digital signature
Re: poudriere: setting up jail failes
On 08/08/14 12:27, Bryan Drewery wrote:
On 8/8/2014 1:57 PM, Matthias Apitz wrote:
And, btw., why is poudriere removing all the jail when an error occures?
Wouldn't it be better to let it there to have a look into and remove it
on the next run?
Yes I agree this should probably change. I'll evaluate it after the 3.1
release which is the major focus right now. The jail command has a lot
of issues with building and error handling.
Since I haven't heard anybody else complain I've not looked into this
further, but just in case... I can always build ports the first time
after a boot, but the second time it fails with the below commented out
statements, even though AFAICT the previous successful run
shutdown cleanly. This is on recent currents with nightly updated
ports (including poudriere).
(BTW poudriere on an 8-core machine running on a zfs SSD is
FANTASTIC! This needs to be applied to the world... Thank you
very much. A big reason I went to debian 14 years ago was for
the joy of binary packages. Now openoffice, thunderbird, who
cares.)
Anyway, haven't had a single problem with the following kludge:
rcarter@terpsichore diff -u ports.sh.orig ports.sh
--- ports.sh.orig 2014-07-27 09:39:19.182960646 -0700
+++ ports.sh2014-08-06 13:58:23.510929452 -0700
@@ -199,8 +199,8 @@
porttree_exists ${PTNAME} || err 2 No such ports tree ${PTNAME}
PTMNT=$(pget ${PTNAME} mnt)
[ -d ${PTMNT}/ports ] PORTSMNT=${PTMNT}/ports
- /sbin/mount -t nullfs | /usr/bin/grep -q ${PORTSMNT:-${PTMNT}}
on \
-err 1 Ports tree \${PTNAME}\ is currently mounted
and being used.
+# /sbin/mount -t nullfs | /usr/bin/grep -q ${PORTSMNT:-${PTMNT}}
on \
+# err 1 Ports tree \${PTNAME}\ is currently mounted
and being used.
msg_n Deleting portstree \${PTNAME}\
destroyfs ${PTMNT} ports
rm -rf ${POUDRIERED}/ports/${PTNAME} || :
@@ -212,8 +212,8 @@
METHOD=$(pget ${PTNAME} method)
PTMNT=$(pget ${PTNAME} mnt)
[ -d ${PTMNT}/ports ] PORTSMNT=${PTMNT}/ports
- /sbin/mount -t nullfs | /usr/bin/grep -q ${PORTSMNT:-${PTMNT}}
on \
-err 1 Ports tree \${PTNAME}\ is currently mounted
and being used.
+# /sbin/mount -t nullfs | /usr/bin/grep -q ${PORTSMNT:-${PTMNT}}
on \
+# err 1 Ports tree \${PTNAME}\ is currently mounted
and being used.
msg Updating portstree \${PTNAME}\
if [ -z ${METHOD} -o ${METHOD} = - ]; then
METHOD=portsnap
___
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: Any users of www/mod_auth_form
On 08/08/2014 19:49, Tommy Scheunemann wrote: currently being the maintainer of www/mod_auth_form I'm asking if some1 is using it. The upstream site is gone, the developer seems unavailable too so the source code isn't under active development too. I don't use it but I recently upgraded a couple of servers from 2.2 to 2.4 and noticed that there is a mod_auth_form module included in 2.4. Is this the same thing? If so, perhaps that's why maintenance of a separate module died. http://httpd.apache.org/docs/trunk/new_features_2_4.html -- John Marshall signature.asc Description: OpenPGP digital signature
Re: Does pkg automatically download INDEX?
On 08/04/14 07:28, David Wolfskill wrote: On Mon, Aug 04, 2014 at 07:09:33AM -0400, Naram Qashat wrote: On 08/03/14 22:14, David Wolfskill wrote: On Sun, Aug 03, 2014 at 10:10:27PM -0400, Naram Qashat wrote: ... If there is a way to find out when any process is attempting to modify a file, that would probably help me narrow it down, but I'm not aware of anything that can do that, ... Well, chflags schg /usr/ports/INDEX* would *prevent* the modification ... This was a really good suggestion. Glad to help. :-) Peace, david OK, so while no programs have whined or complained, I get the feeling that something on my system is running portsnap without my knowledge. When I had set the schg flag on INDEX-9, an INDEX-9.bz2 file came up. I set the schg flag on that as well, and now I notice there are a bunch of files called .fetch.??.INDEX-9.bz2 (where ?? is a random string), as well as a file called .portsnap.INDEX. As far as I know, I don't have anything configured to run portsnap, but is there something that defaults to running portsnap occasionally? I couldn't find anything that would do that. Thanks, Naram Qashat ___ 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
