On Sat, Mar 13, 2010 at 08:40:32PM -0500, jhell wrote:
> Rather simple way to go about creating final packages and from some
> earlier emails to the list there was word of some directories not being
> included in final built packages due to empty directories or something
> like that so be carefu
On Sat, 13 Mar 2010 23:31, xorquewasp@ wrote:
'Lo,
On 2010-03-13 20:40:32, jhell wrote:
Not that this is a solution to your problem but it might be a possibility
for you to consider, but a couple years back I dropped using make
package(-recursive) and just scripted out making backup packages u
'Lo,
On 2010-03-13 20:40:32, jhell wrote:
> Not that this is a solution to your problem but it might be a possibility
> for you to consider, but a couple years back I dropped using make
> package(-recursive) and just scripted out making backup packages using
> something like the following.
I p
On Sat, 13 Mar 2010 02:52, xorquewasp@ wrote:
Have you tried just setting PORTSDIR and letting bsd.port.mk set the
rest of the paths with their defaults that are relative to PORTSDIR? If
that works, then we can start hunting for places that are not handling
absolute vs. relative paths correctly
On Sat, Mar 13, 2010 at 11:51 AM, Garrett Cooper wrote:
> On Fri, Mar 12, 2010 at 11:52 PM, wrote:
>>> Have you tried just setting PORTSDIR and letting bsd.port.mk set the
>>> rest of the paths with their defaults that are relative to PORTSDIR? If
>>> that works, then we can start hunting for p
On Fri, Mar 12, 2010 at 11:52 PM, wrote:
>> Have you tried just setting PORTSDIR and letting bsd.port.mk set the
>> rest of the paths with their defaults that are relative to PORTSDIR? If
>> that works, then we can start hunting for places that are not handling
>> absolute vs. relative paths cor
> Have you tried just setting PORTSDIR and letting bsd.port.mk set the
> rest of the paths with their defaults that are relative to PORTSDIR? If
> that works, then we can start hunting for places that are not handling
> absolute vs. relative paths correctly in bsd.port.mk.
Now, with only:
PORT
On 2010-03-12 22:36:54, Greg Larkin wrote:
> Hi xw,
>
> I noticed something strange here. How is WRKDIR (in this case
> "/var/ports/work/var/ports/tree/devel/eggdbus/work") defined? It looks
> like bsd.port.mk combined your WRKDIRPREFIX and PORTSDIR to create that
> path, but skimming the code,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
xorquew...@googlemail.com wrote:
[...]
> DISTDIR= /var/ports/distfiles
> PACKAGES= /var/ports/packages
> WRKDIRPREFIX= /var/ports/work
> PORTSDIR= /var/ports/tree
>
> jail# vi /etc/profile
> FTP_PASSIVE_MODE=yes
> HTTP_PROXY=10.1.3.3:
This is a complete lot of how to reproduce the various errors I've
seen with 'make package-recursive'. I've checked the pointyhat logs
and there are no errors logged for the packages involved here. There
seems to be a bug somewhere in ports. I've used inkscape as a scapegoat
here but the errors occ
'Lo.
As a test, I've now stripped nullfs out of the picture entirely. The
exact same problem still occurs:
Creating package /pkg/All/libgpg-error-1.7.tbz
Registering depends: gettext-0.17_1 libiconv-1.13.1_1.
Creating bzip'd tar ball in '/pkg/All/libgpg-error-1.7.tbz'
rmdir: /work/ports/security/
'Lo,
On 2010-03-05 09:47:11, jhell wrote:
> Adding on to this. There were reports in various cases dating back to ~1
> year with bad results, possible data loss, hard and soft dead locks when
> nullfs was used with ZFS. nullfs at one point that I do remember was not
> recommended to be used at all
On Fri, 5 Mar 2010 06:56, des@ wrote:
xorquew...@googlemail.com writes:
Is there any resolution for this problem?
I told you, zfs set mountpoint and ditch nullfs.
DES
Adding on to this. There were reports in various cases dating back to ~1
year with bad results, possible data loss, hard
xorquew...@googlemail.com writes:
> Is there any resolution for this problem?
I told you, zfs set mountpoint and ditch nullfs.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listin
So, anyway...
Is there any resolution for this problem?
I have quite a few packages I'd like to get built (just "custom"
enough that pre-built packages from FreeBSD mirrors won't suffice).
I have to admit to not being convinced that nullfs is at the root
of the problem... I have vague, confused
On 2010-03-02 11:00:45, Dag-Erling Smørgrav wrote:
> xorquew...@googlemail.com writes:
> > Basically, I have a ton of jails and each jail mounts a shared 'tmp',
>
> That's not a good idea, there are too many opportunities for conflicts
> (software that creates sockets and state directories with no
m...@coreland.ath.cx writes:
> Is it possible to define multiple mountpoints (to emulate what nullfs
> provides)?
Sorry, no.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
xorquew...@googlemail.com writes:
> Basically, I have a ton of jails and each jail mounts a shared 'tmp',
That's not a good idea, there are too many opportunities for conflicts
(software that creates sockets and state directories with non-randomized
names in /tmp) and might even allow a compromise
'Lo,
Here's the current state of '/work':
http://coreland.ath.cx/tmp/work.txt
On 2010-03-01 20:08:45, Dag-Erling Smørgrav wrote:
> That's begging the question... Clearly you're using nullfs because you
> need something done that you think nullfs can do for you. I'd like to
> know what that i
xorquew...@googlemail.com writes:
> Dag-Erling Smørgrav writes:
> > xorquew...@googlemail.com writes:
> > > There's certainly no parallel building going on, but /work is nullfs
> > > mounted (from ZFS). Could this cause the above?
> > Not sure. Why are you using nullfs?
> Basically because "I don
On 2010-03-01 15:10:16, Dag-Erling Smørgrav wrote:
> xorquew...@googlemail.com writes:
> > There's certainly no parallel building going on, but /work is nullfs
> > mounted (from ZFS). Could this cause the above?
>
> Not sure. Why are you using nullfs?
Basically because "I don't know any better".
On Mon, Mar 01, 2010 at 01:58:29PM +, xorquew...@googlemail.com wrote:
> On 2010-03-01 14:34:50, Dag-Erling Smørgrav wrote:
> > % fgrep 'Directory not empty' inkscape.txt
> > rmdir: /work/ports/devel/boost-libs/work: Directory not empty
> > ...
> > rmdir: /work/ports/x11-toolkits/pangomm/work:
xorquew...@googlemail.com writes:
> There's certainly no parallel building going on, but /work is nullfs
> mounted (from ZFS). Could this cause the above?
Not sure. Why are you using nullfs?
Can you show us the contents of those directories?
DES
--
Dag-Erling Smørgrav - d...@des.no
___
On 2010-03-01 14:34:50, Dag-Erling Smørgrav wrote:
> % fgrep 'Directory not empty' inkscape.txt
> rmdir: /work/ports/devel/boost-libs/work: Directory not empty
> rmdir: /work/ports/x11-toolkits/gtkmm24/work: Directory not empty
> rmdir: /work/ports/devel/boehm-gc/work: Directory not empty
> rmdir:
% fgrep 'Directory not empty' inkscape.txt
rmdir: /work/ports/devel/boost-libs/work: Directory not empty
rmdir: /work/ports/x11-toolkits/gtkmm24/work: Directory not empty
rmdir: /work/ports/devel/boehm-gc/work: Directory not empty
rmdir: /work/ports/math/gsl/work: Directory not empty
rmdir: /work/
On 2010-02-26 17:38:00, Greg Larkin wrote:
> Can you post a full log file of the process somewhere? The best way to
> capture it is with the commands:
'Lo,
I did actually send a log in response to DES' email but I sent the email
from the wrong account and it still awaits list moderation.
Here i
fwiw, the canonical way to find out if a port will package up in a
clean environment (choort, with dependencies all loaded via package)
is on http://pointyhat.freebsd.org/errorlogs/ , e.g.,
http://pointyhat.freebsd.org/errorlogs/i386-8-full/ .
http://portsmon.freebsd.org gives you lots of cross-re
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
xorquew...@googlemail.com wrote:
>> cd $port
>> make clean
>> make deinstall
>> make depends # just to be safe
>> make install
>> make package-recursive
>
> This apparently didn't solve the problem (same errors).
>
> I'm stumped.
>
> xw
Can
I also build my ports in a "jail" environment (only its not a really a
jail, just a chroot).
After I have built the ports I want, I create the packages using the
following little script. (My mail client will have mangled the script,
so take care when you copy and paste it, e.g. it needs to be
> cd $port
> make clean
> make deinstall
> make depends # just to be safe
> make install
> make package-recursive
This apparently didn't solve the problem (same errors).
I'm stumped.
xw
___
freebsd-hackers@freebsd.org mailing list
http://lists
'Lo,
On 2010-02-26 12:39:26, Greg Larkin wrote:
> "make package-recursive" calls "make package-noinstall" for all of the
> dependent ports. I'm assuming that means that the dependent packages
> all have to be installed first, so I would change your script like so:
>
> cd $port
> make clean
> mak
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
xorquew...@googlemail.com wrote:
> 'Lo.
>
> I've come up against an infuriating problem with ports. I don't even
> know what causes it, let alone how to solve it.
>
> Essentially, to stop already-installed software from polluting port
> builds, I bui
xorquew...@googlemail.com writes:
> tar: share/sgml/docbook/4.2/ChangeLog: Cannot stat: No such file or directory
> [...]
> tar: Error exit delayed from previous errors.
> pkg_create: make_dist: tar command failed with code 256
> Creating package /pkg/All/docbook-4.2.tbz
> Registering depends: iso8
'Lo.
I've come up against an infuriating problem with ports. I don't even
know what causes it, let alone how to solve it.
Essentially, to stop already-installed software from polluting port
builds, I build ports in a jail. I put a list of ports in a file and
use a trivial shell script to build th
34 matches
Mail list logo
