Glade3 :: small revision bump

2009-02-17 Thread Jason Beaudoin 
..just a small revision bump, picking up a few bug fixes.


Regards,

~jason


Index: Makefile
===
RCS file: /cvs/ports/devel/glade3/Makefile,v
retrieving revision 1.5
diff -u -p -r1.5 Makefile
--- Makefile20 Jan 2009 23:15:39 -  1.5
+++ Makefile18 Feb 2009 03:58:44 -
@@ -2,9 +2,9 @@

 COMMENT=   user interface builder for the GTK2+ toolkit

-GNOME_VERSION =3.5.4
+GNOME_VERSION =3.5.7
 GNOME_PROJECT =glade3
-PKGNAME=   ${DISTNAME}p0
+PKGNAME=   ${DISTNAME}

 CATEGORIES =   devel
 SHARED_LIBS +=  gladeui-10.0  # .8.0
Index: distinfo
===
RCS file: /cvs/ports/devel/glade3/distinfo,v
retrieving revision 1.2
diff -u -p -r1.2 distinfo
--- distinfo14 Jan 2009 22:54:52 -  1.2
+++ distinfo18 Feb 2009 03:58:44 -
@@ -1,5 +1,5 @@
-MD5 (glade3-3.5.4.tar.bz2) = r7CdJQLCzLt82J6pb5rExw==
-RMD160 (glade3-3.5.4.tar.bz2) = 4Jnxp84gqNsdzP9PVdpg3vnjSKo=
-SHA1 (glade3-3.5.4.tar.bz2) = +GkALGr1DsrApNvm/kyPEeVsJdg=
-SHA256 (glade3-3.5.4.tar.bz2) =
NffGFJIe2koHHPWqdnQ1GqBbwmgscUTXyPvZ9CAq41o=
-SIZE (glade3-3.5.4.tar.bz2) = 1980344
+MD5 (glade3-3.5.7.tar.bz2) = OB4pDUpq59akH+FrBvFbsw==
+RMD160 (glade3-3.5.7.tar.bz2) = Q3HuCRserRCEZ2Xj05x4rU0y+E8=
+SHA1 (glade3-3.5.7.tar.bz2) = LixvzvGO2aDmvmlM+YqocdyP1i8=
+SHA256 (glade3-3.5.7.tar.bz2) =
ePS5IldJrxTmFCRyVaD3u9mi2a4rSsjzIO0KDzxcyXI=
+SIZE (glade3-3.5.7.tar.bz2) = 2021224

Re: sndio backend requests

2008-12-31 Thread Jason Beaudoin 
On Fri, Dec 26, 2008 at 5:41 AM, Jacob Meuser jake...@sdf.lonestar.orgwrote:


 request lines are open.  what ports do y'all want sndio backends
 for?

 iirc, ajacoutot said something about libcanberra, and the ports
 listed here: http://jakemsr.trancell.org/libsndio.html in the
 works.

 what else?


mplayer?

~Jason

Re: usr/ports as a symlink?

2008-12-24 Thread Jason Beaudoin 
--
401.837.8417
jasonbeaud...@gmail.com


On Sun, Dec 14, 2008 at 5:25 PM, Jacob Meuser jake...@sdf.lonestar.orgwrote:

 On Sun, Dec 14, 2008 at 05:39:21PM +0100, Pierre Riteau wrote:

  This seems to be fixed by rev. 1.61 of PackageRepository.pm.
  Thank you Marc.
 
  Jason, Jacob, can you confirm?

 yes, it seems to have fixed the problems I was having.


I'm all good here too, awesome   : )


Regards,
~Jason

Re: usr/ports as a symlink?

2008-12-02 Thread Jason Beaudoin 
On Tue, Dec 2, 2008 at 12:01 AM, Jacob Meuser [EMAIL PROTECTED] wrote:
 On Mon, Dec 01, 2008 at 11:52:23PM -0500, Jason Beaudoin wrote:
 On Mon, Dec 1, 2008 at 11:26 PM, Jacob Meuser [EMAIL PROTECTED] wrote:
  On Mon, Dec 01, 2008 at 10:46:19PM -0500, Jason Beaudoin wrote:
  On Mon, Dec 1, 2008 at 8:40 AM, RD Thrush [EMAIL PROTECTED] wrote:
   j == Jason Beaudoin [EMAIL PROTECTED] writes:
   j [ ... snip ... ]
  
   j so my question: have other folks run into the 0 byte package behavior
   j before, or are there others with /usr/ports as a symlink but without
   j any other problems?
  
   j I understand that I can remove the FETCH_PACKAGES flag and this will
   j circumvent the problem, but circumvention isn't resolution; I am
   j curious if I am doing something wrong, of if something really is
   j broken.
  
   I've symlinked /usr/ports for years and haven't noticed any related
   problems building ports for i386 and amd64.  I don't use
   FETCH_PACKAGES so can't comment about that.
 
 
  mmm, tobais pointed out we should just use PORTSDIR in etc/mk.conf.
 
 
  I've had /usr/ports as a symlink for years too.  I started noticing
  the 0 byte packages fairly recently.  figured it was transient.
 
  if it's now true that using a symlink for PORTSDIR is a problem,
  it needs to be documented somethere.


 to be clear, my tests with a symlinked usr/ports was also with
 FETCH_PACKAGES=Yes.

 I've been following the thread.  I never figured out what sequence
 of events lead to the 0 byte packages though.

running a `make package` on a port that has an available package on
your favorite ftp/http mirror (give in $PKG_PATH, not specified in
etc/mk.conf (I still want to test that minor difference). read the
last few messages for more information.

snip

Regards,
~Jason

Re: usr/ports as a symlink?

2008-12-02 Thread Jason Beaudoin 
On Tue, Dec 2, 2008 at 11:34 AM, Marc Espie [EMAIL PROTECTED] wrote:
 On Tue, Dec 02, 2008 at 04:26:26AM +, Jacob Meuser wrote:
 I've had /usr/ports as a symlink for years too.  I started noticing
 the 0 byte packages fairly recently.  figured it was transient.

 if it's now true that using a symlink for PORTSDIR is a problem,
 it needs to be documented somethere.

 No, it needs to error out in a sensible way, like not creating 0 bytes
 packages, but displaying an error message.

 I haven't noticed anything, I surmised it's probably tied to the recent (?)
 work to uniformize pkgpaths... I'll test it at some point.



I will gladly run test cases for you if

Re: usr/ports as a symlink?

2008-12-02 Thread Jason Beaudoin 
On Tue, Dec 2, 2008 at 11:34 AM, Marc Espie [EMAIL PROTECTED] wrote:
 On Tue, Dec 02, 2008 at 04:26:26AM +, Jacob Meuser wrote:
 I've had /usr/ports as a symlink for years too.  I started noticing
 the 0 byte packages fairly recently.  figured it was transient.

 if it's now true that using a symlink for PORTSDIR is a problem,
 it needs to be documented somethere.

 No, it needs to error out in a sensible way, like not creating 0 bytes
 packages, but displaying an error message.

 I haven't noticed anything, I surmised it's probably tied to the recent (?)
 work to uniformize pkgpaths... I'll test it at some point.


apologies for the last (rogue) message, thank gmail. I was just
acknowledging that I am willing to run tests for you .

regards,
~Jason

Re: usr/ports as a symlink?

2008-12-01 Thread Jason Beaudoin 
 snip 


 I understand that I can remove the FETCH_PACKAGES flag and this will
 circumvent the problem, but circumvention isn't resolution; I am
 curious if I am doing something wrong, of if something really is
 broken.


 thanks for the time,
 ~Jason


 [1] http://marc.info/?l=openbsd-portsm=122672174517068w=4



 Set PORTSDIR in mk.conf(5). Note that eg. for BSDSRCDIR it talks about
 the real path.

 If you want to know why this is important, try:
 cd /some/symlink
 pwd
 /bin/pwd

 Most shells fake that cd something  cd .. gets you back into the
 original directory, giving the illusion that symlinks are somehow
 transparent. They are not, in fact, symlinks suck...


ah yes, you are correct but this still doesn't cover the second case
(building inside a chroot environment)

I detailed my process in the last thread [1].


thanks,
~Jason

[1] http://marc.info/?l=openbsd-portsm=99867604230539w=3

Re: usr/ports as a symlink?

2008-12-01 Thread Jason Beaudoin 
On Mon, Dec 1, 2008 at 8:40 AM, RD Thrush [EMAIL PROTECTED] wrote:
 j == Jason Beaudoin [EMAIL PROTECTED] writes:
 j [ ... snip ... ]

 j so my question: have other folks run into the 0 byte package behavior
 j before, or are there others with /usr/ports as a symlink but without
 j any other problems?

 j I understand that I can remove the FETCH_PACKAGES flag and this will
 j circumvent the problem, but circumvention isn't resolution; I am
 j curious if I am doing something wrong, of if something really is
 j broken.

 I've symlinked /usr/ports for years and haven't noticed any related
 problems building ports for i386 and amd64.  I don't use
 FETCH_PACKAGES so can't comment about that.


mmm, tobais pointed out we should just use PORTSDIR in etc/mk.conf.


 Here's a snippet from one machine.
 x2:build/packages 420ll /usr/ports
 lrwx--  1 root  wheel  28 Nov 12  2007 /usr/ports - 
 ../pub/OpenBSD/current/ports
 x2:build/packages 421grep ports /etc/mk.conf
 WRKOBJDIR=/usr/obj/${MACHINE_ARCH}/ports
 PKG_TMPDIR=/usr/obj/${MACHINE_ARCH}/ports/tmp
 PLIST_DB=/usr/obj/${MACHINE_ARCH}/ports/plist_db
 LOCKDIR=/usr/obj/${MACHINE_ARCH}/ports/locks

 Regards, Bob


thanks!

the chroot is still a mystery.


regards,
~Jason

Re: usr/ports as a symlink?

2008-12-01 Thread Jason Beaudoin 
On Mon, Dec 1, 2008 at 11:26 PM, Jacob Meuser [EMAIL PROTECTED] wrote:
 On Mon, Dec 01, 2008 at 10:46:19PM -0500, Jason Beaudoin wrote:
 On Mon, Dec 1, 2008 at 8:40 AM, RD Thrush [EMAIL PROTECTED] wrote:
  j == Jason Beaudoin [EMAIL PROTECTED] writes:
  j [ ... snip ... ]
 
  j so my question: have other folks run into the 0 byte package behavior
  j before, or are there others with /usr/ports as a symlink but without
  j any other problems?
 
  j I understand that I can remove the FETCH_PACKAGES flag and this will
  j circumvent the problem, but circumvention isn't resolution; I am
  j curious if I am doing something wrong, of if something really is
  j broken.
 
  I've symlinked /usr/ports for years and haven't noticed any related
  problems building ports for i386 and amd64.  I don't use
  FETCH_PACKAGES so can't comment about that.


 mmm, tobais pointed out we should just use PORTSDIR in etc/mk.conf.


 I've had /usr/ports as a symlink for years too.  I started noticing
 the 0 byte packages fairly recently.  figured it was transient.

 if it's now true that using a symlink for PORTSDIR is a problem,
 it needs to be documented somethere.


to be clear, my tests with a symlinked usr/ports was also with
FETCH_PACKAGES=Yes.

but yes, 0 byte packages are odd.

 --
 [EMAIL PROTECTED]
 SDF Public Access UNIX System - http://sdf.lonestar.org




~Jason

usr/ports as a symlink?

2008-11-30 Thread Jason Beaudoin 
Ports,

I am running into some odd behavior when building ports, whereby some
ports build fine, while others result in 0 byte packages in my local
repository. I believe the problem ports are ones that have packages
available on the ftp mirrors as well (retrieved using FETCH_PACKAGES).
As a problem, this will then usually surface when attempting to
pkg_add the 0 byte package, specifically when the port is needed as a
build dependency of a port that I am installing. More information
about the problem where this surfaced can be found in a previous post:
[1]

In my testing, the 0 byte package issue results in two of three cases, either:
 - /usr/ports is a symlink to another directory (which I have heard is
supposed to work, maybe this is not the case)
 - or when building ports from inside a chroot environment.
Elderley.net has an ssh-chroot setup for a special ports user, I don't
know if the two chroot's are different.

(the third case is building ports with a standard /usr/ports, no
symlink, no chroot)

so my question: have other folks run into the 0 byte package behavior
before, or are there others with /usr/ports as a symlink but without
any other problems?

I understand that I can remove the FETCH_PACKAGES flag and this will
circumvent the problem, but circumvention isn't resolution; I am
curious if I am doing something wrong, of if something really is
broken.


thanks for the time,
~Jason


[1] http://marc.info/?l=openbsd-portsm=122672174517068w=4

Re: pkg_add can't find target depend package during bulk make package

2008-11-30 Thread Jason Beaudoin 
 snip 


 thanks for the references. viq pointed me towards dpb earlier today, I
 still need to read into how it functions. My only outstanding question
 is if it accepts a list of packages to build, or simply builds
 everything.

 It can accept a SUBDIRLIST, see the comments in the file itself.


for completeness, the root of the original issue - pkg_add not being
able to install the package - was due to the packages being 0 bytes in
size. I am now trying to figure out *why* they were broken [1], which
seems to be connected to either symlinking /usr/ports or building
ports inside a chroot environment.


regards,
~Jason


[1] http://marc.info/?l=openbsd-portsm=122809247327274w=4

Re: pkg_add can't find target depend package during bulk make package

2008-11-18 Thread Jason Beaudoin 
On Sat, Nov 15, 2008 at 5:07 AM, Stuart Henderson [EMAIL PROTECTED] wrote:
 On 2008/11/15 10:05, Stuart Henderson wrote:
 On 2008/11/14 22:58, Jason Beaudoin wrote:
  I've bulk built a number of packages over the last week, and I often
  run into the situation where building a package requires a dependency
  (that ends up either being built or found on a mirror), but when make
  tries to pkg_add the dependency, pkg_add fails saying it can't find
  the target package.

 I think you need to figure out what you're doing that's different
 to everyone else.

that's what I'm trying for :)

here is some more info and context.. first of all, this is occuring in
the middle of a bulk package build running the command:

  cd /usr/ports;
  make BULK=yes REFETCH=true REPORT_PROBLEMS=true
SUBDIRLIST=/root/pkg_list.txt package;

and here is my mk.conf:

  (chroot) # cat /etc/mk.conf
  ACCEPT_JRL_LICENSE=Yes  # to build jdk for openoffice
  FETCH_PACKAGES=yes

  # keeping the tree clean..
  WRKOBJDIR=/usr/obj/ports/


 Is your ports tree clean and up-to-date?

after my initial message to the list, I wiped the ports tree,
retested, then wiped the entire chroot last night. Continuing this
morning, I hit the same fatal error with the jpeg package.

I have done some more testing and confirmed a few more odditites about
this, maybe someone can shed some light where I have gone astray.


  Can't find /usr/ports/packages/i386/all/glib2-2.18.2.tgz

 No wonder this fails, the package is called glib-2.18.2.tgz...

to clarify, this particular error came from the bulk build, when it
tried to pkg_add glib2 itself.. this isn't me.

--

the problem seems to surface with packages that exist on mirrors, and
don't need to  be built locally, the following example shows this
(clean chroot and ports tree - it just happens to be glib2 again):

  === Returning to build of glib2-2.18.2
  ===  glib2-2.18.2 depends on: pcre-=7.2 - found
  ===  glib2-2.18.2 depends on: gettext-=0.17 - found
  ===  glib2-2.18.2 depends on: gmake-* - found
  ===  glib2-2.18.2 depends on: libtool-* - found
  ===  glib2-2.18.2 depends on: bzip2-* - found
  ===  Verifying specs: intl.=4 iconv.=4 pcre c
  ===  found intl.4.0 iconv.5.0 pcre.2.2 c.49.0
  ===  Installing glib2-2.18.2 from /usr/ports/packages/i386/all/
  Can't find /usr/ports/packages/i386/all/glib2-2.18.2.tgz
  /usr/sbin/pkg_add: /usr/ports/packages/i386/all/glib2-2.18.2.tgz:Fatal error
  *** Error code 1

  Stop in /usr/ports/devel/glib2 (line 1452 of
/usr/ports/infrastructure/mk/bsd.port.mk).
  *** Error code 1

interjection
so pkg_add /usr/ports/packages/i386/all/glib2-2.18.2.tgz attempted
to install glib2  during the bulk build, though pkg_add failed.
/interjection


  Stop in /usr/ports/devel/libIDL (line 1601 of
/usr/ports/infrastructure/mk/bsd.port.mk).
  *** Error code 1

snip redundant error

  Stop in /usr/ports/devel/ORBit2 (line 1964 of
/usr/ports/infrastructure/mk/bsd.port.mk).
  === Exiting devel/ORBit2 with an error
  *** Error code 1
  Stop in /usr/ports (line 124 of
/usr/ports/infrastructure/mk/bsd.port.subdir.mk).

-
ok, so let us attempt the pkg_add ourselves:

  (chroot) # pkg_add /usr/ports/packages/i386/all/glib2-2.18.2.tgz
  Can't find /usr/ports/packages/i386/all/glib2-2.18.2.tgz
  /usr/sbin/pkg_add: /usr/ports/packages/i386/all/glib2-2.18.2.tgz:Fatal error

-
let's try another package that is in the $PKG_PATH:

  (chroot) # pkg_add /usr/ports/packages/i386/all/python-2.5.2p7.tgz
  Can't find /usr/ports/packages/i386/all/python-2.5.2p7.tgz
  /usr/sbin/pkg_add: /usr/ports/packages/i386/all/python-2.5.2p7.tgz:Fatal error


ok, let's try the package name, not full path:

  (chroot) # pkg_add glib2
  Error from 
ftp://ftp3.usa.openbsd.org//pub/OpenBSD/snapshots/i386/glib2-2.18.2.tgz:
  550 glib2-2.18.2.tgz: No such file or directory.
  glib2-2.18.2: complete

-
so it appears that glib2-2.18.2.tgz from the local repository was not
used, but rather my third PKG_PATH location:

export 
PKG_PATH=/usr/ports/packages/i386/all/:ftp://ftp3.usa.openbsd.org/pub/OpenBSD/snapshots/i386/:ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/packages/i386/;

let's verify this by changing the PKG_PATH to include only the local
repository, even though glib2 was already installed, pkg_add needs to
find the package first:

  (chroot) # export PKG_PATH=/usr/ports/packages/i386/all/
  (chroot) # pkg_add glib2
  Can't find glib2-2.18.2
  /usr/sbin/pkg_add: glib2-2.18.2:Fatal error

-
so now that glib2 has been installed, and we seem to have a problem
with using packages copied to the local repository from ftp (but ftp
pkg_add's fine), I continue with the bulk build.. we will see if
things break again:

  === Returning to build of enchant-1.4.0p1
  ===  enchant-1.4.0p1 depends on: aspell-* - found
  ===  enchant-1.4.0p1 depends on: dbus-glib-* - not found
  ===  Verifying install for dbus-glib-* in x11/dbus-glib

Re: pkg_add can't find target depend package during bulk make package

2008-11-18 Thread Jason Beaudoin 
Just an update, and some added info..


 alright.. let's retry the bulk build.. it continues past dbus, but
 dies again at dbus-glib. after installing dbus-glib from the ftp
 package.. the bulk build continues.

 the example I've included here is from my work yesterday (with a clean
 ports tree, but the same chroot). As mentioned before, I created a
 clean chroot and ports tree last night, which I have since tested the
 bulk build on, running into the same issue. I started a bulk build on
 my laptop (with a clean -current ports tree) this morning. It hasn't
 crapped out yet, but we'll see what happens.

 what is going wrong here, or where am I going wrong?
 I can post my full prep/chroot/bulk-build process, if that is of
 interest please let me know.


so my laptop is running through the build just fine (all day). the
chroot'ed build is not, so I thought I would share my chroot process:


# here are the steps I take in preparing
# the chroot for bulk building packages.

# get the latest snapshot install sets:

  cd /exports/OpenBSD/snapshots/
  export $FTPROOT=ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/;
  ftp $FTPROOT/i386/*.tgz

---
# zero-out the old partition and mount:

  newfs wd0i
  export CHROOT=/mnt/rover
  mount /dev/wd0i $CHROOT

---
# extract the install-sets:
# (still in .../snapshots/)

  for i in `ls *.tgz`:
do;
tar xzpf $i -C $CHROOT;
done;

---
# copy over a few other files:

  cp /etc/{localtime,resolv.conf} /root/chroot/mk.conf $CHROOT/etc/
  cp /root/chroot/IN_CHROOT $CHROOT/

---
# create device nodes:

  cd $CHROOT/dev  ./MAKEDEV all

---
# get, extract and cvsup the snapshots ports tar.gz:

  cd /exports/OpenBSD/release_tar/
  tar xzpf ports.tar.gz -C $CHROOT/usr/
  cd $CHROOT/usr/ports
  export $CVSROOT=[EMAIL PROTECTED]:/cvs
  cvs -d $CVSROOT up -dP

---
# what does mk.conf look like?

  cat $CHROOT/etc/mk.conf
ACCEPT_JRL_LICENSE=Yes  # to build jdk for openoffice
FETCH_PACKAGES=yes  # get a pkg before building

WRKOBJDIR=/usr/obj/ports/   # keeping the tree clean..

#FETCH_CMD=wget  # use wget for fetch
#PLIST=${PORTSDIR}/plist/# pkg_create saves plists here..
#USE_SYSTRACE=Yes# keeping us safe..

---
# enter the chroot:

  chroot $CHROOT /bin/ksh -l
  ldconfig /usr/lib /usr/local/lib/ /usr/X11R6/lib/

---
# what is our bulk build cmd like?
# (from root's .profile)

  alias bulk_pkg=cd /usr/ports/; make BULK=yes REPORT_PROBLEMS=true \
  REFETCH=true SUBDIRLIST=/root/package_list.txt package

Re: pkg_add can't find target depend package during bulk make package

2008-11-18 Thread Jason Beaudoin 
On Tue, Nov 18, 2008 at 5:16 PM, Stuart Henderson [EMAIL PROTECTED] wrote:
 On 2008/11/18 09:09, Jason Beaudoin wrote:
   FETCH_PACKAGES=yes

 this doesn't make much sense for a bulk build. you're building
 packages yourself, why would you want to use packages from,
 in all likelihood, 5+ days ago to fulfil dependencies? some of
 them won't even match the ports tree or your base OS libraries.

indeed, I understand that this was an option. though FETCH_PACKAGES
can be handy for some packages.

but either way, that error still doesn't make sense, given that things
are working on my laptop, I've got to be goofing something up.

 export 
 PKG_PATH=/usr/ports/packages/i386/all/:ftp://ftp3.usa.openbsd.org/pub/OpenBSD/snapshots/i386/:ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/packages/i386/;

 listing just one entry here usually makes things much simpler.
 but see above..

 for mk.conf, you may also want ACCEPT_GRAPHVIZ_LICENSE=Yes.
 also look into /usr/ports/infrastructure/build/dpb, it's the
 easiest way to do a bulk build (and, if you're running MP,
 makes better use of your CPUs).

thanks for the references. viq pointed me towards dpb earlier today, I
still need to read into how it functions. My only outstanding question
is if it accepts a list of packages to build, or simply builds
everything.

thanks for your help :)


regards,
~jason

pkg_add errors: uninitialized value

2008-11-14 Thread Jason Beaudoin 
hiya folks,


recently, I reconfigured my ports/packages use such that my
workstation bulk builds unavailable packages (or ones that need to be
rebuilt) for several other systems, exporting /usr/ports. This is done
within a chroot to keep my workstation (relatively) free from the
clutter that would ensue from building for multiple systems. Given
that there was a bit of trial and error through this process, I
believe the errors I am seeing from pkg_add will disappear once I wipe
ports/packages and start fresh, but I am here more out of curiosity to
better understand what went wrong.

when attempting to pkg_add various packages on my laptop, using
/usr/ports (and /usr/ports/packages) exported from my build system, I
often run into the following errors:

ion# pkg_add -i librsvg
Ambiguous: choose package for librsvg
 0: None
 1: librsvg-2.20.0p3
 2: librsvg-2.20.0p3-no_gnome
Your choice: 2
Use of uninitialized value $j in hash element at /usr/sbin/pkg_add line 59.
Use of uninitialized value $j in hash element at /usr/sbin/pkg_add line 59.
Use of uninitialized value $pkg in hash element at /usr/sbin/pkg_add line 82.
Can't call method plist on unblessed reference at /usr/sbin/pkg_add line 764.


I say often, because the uninitialized value $j in hash element
error really only occurs when trying to pkg_add a gnome-related
package.

what's going on here?


thanks, and regards,
~Jason

pkg_add can't find target depend package during bulk make package

2008-11-14 Thread Jason Beaudoin 
ports!

I've bulk built a number of packages over the last week, and I often
run into the situation where building a package requires a dependency
(that ends up either being built or found on a mirror), but when make
tries to pkg_add the dependency, pkg_add fails saying it can't find
the target package. In testing pkg_add out myself, I experience the
same error when I run pkg_add with the full path of the package just
created (either grabbed from a mirror or built locally), though all is
fine if I use the package's basename (and not full path). pkg_add is
also fine to use the full path to the package if the package was not
the dependency make just attempted to pkg_add see the following
example with xfe):

 (chroot) # lls /usr/ports/packages/i386/all/xfe-1.19.2.tgz
-rw-r--r--  1 root  wheel   2.0M Nov  8 10:10
/usr/ports/packages/i386/all/xfe-1.19.2.tgz
(chroot) # pkg_add fox
fox-1.6.28: complete
(chroot) # pkg_add  /usr/ports/packages/i386/all/xfe-1.19.2.tgz
xfe-1.19.2: complete

here is the last chunk of the bulk package build, including where
pkg_add fails, then my attempts to manually pkg_add the newly
available dependency:

=== Returning to build of glib2-2.18.2
===  glib2-2.18.2 depends on: pcre-=7.2 - found
===  glib2-2.18.2 depends on: gettext-=0.17 - found
===  glib2-2.18.2 depends on: gmake-* - found
===  glib2-2.18.2 depends on: libtool-* - found
===  glib2-2.18.2 depends on: bzip2-* - found
===  Verifying specs: intl.=4 iconv.=4 pcre c
===  found intl.4.0 iconv.5.0 pcre.2.2 c.49.0
===  Installing glib2-2.18.2 from /usr/ports/packages/i386/all/
Can't find /usr/ports/packages/i386/all/glib2-2.18.2.tgz
/usr/sbin/pkg_add: /usr/ports/packages/i386/all/glib2-2.18.2.tgz:Fatal error
*** Error code 1

Stop in /usr/ports/devel/glib2 (line 1452 of
/usr/ports/infrastructure/mk/bsd.port.mk).
*** Error code 1

Stop in /usr/ports/devel/desktop-file-utils (line 1601 of
/usr/ports/infrastructure/mk/bsd.port.mk).
*** Error code 1

Stop in /usr/ports/devel/desktop-file-utils (line 1998 of
/usr/ports/infrastructure/mk/bsd.port.mk).
*** Error code 1

Stop in /usr/ports/devel/desktop-file-utils (line 1424 of
/usr/ports/infrastructure/mk/bsd.port.mk).
*** Error code 1

Stop in /usr/ports/devel/desktop-file-utils (line 1424 of
/usr/ports/infrastructure/mk/bsd.port.mk).
*** Error code 1

Stop in /usr/ports/devel/desktop-file-utils (line 1961 of
/usr/ports/infrastructure/mk/bsd.port.mk).
*** Error code 1

Stop in /usr/ports/devel/desktop-file-utils (line 1452 of
/usr/ports/infrastructure/mk/bsd.port.mk).
*** Error code 1

Stop in /usr/ports/print/cups (line 1601 of
/usr/ports/infrastructure/mk/bsd.port.mk).
*** Error code 1

Stop in /usr/ports/editors/abiword (line 1998 of
/usr/ports/infrastructure/mk/bsd.port.mk).
*** Error code 1

Stop in /usr/ports/editors/abiword (line 1424 of
/usr/ports/infrastructure/mk/bsd.port.mk).
*** Error code 1

Stop in /usr/ports/editors/abiword (line 1424 of
/usr/ports/infrastructure/mk/bsd.port.mk).
*** Error code 1

Stop in /usr/ports/editors/abiword (line 1964 of
/usr/ports/infrastructure/mk/bsd.port.mk).
=== Exiting editors/abiword with an error
*** Error code 1

Stop in /usr/ports (line 124 of
/usr/ports/infrastructure/mk/bsd.port.subdir.mk).
(chroot) # pkg_add /usr/ports/packages/i386/all/glib2-2.18.2.tgz
Can't find /usr/ports/packages/i386/all/glib2-2.18.2.tgz
/usr/sbin/pkg_add: /usr/ports/packages/i386/all/glib2-2.18.2.tgz:Fatal error
(chroot) # pkg_add glib2
glib2-2.18.2: complete


I have experienced this same behaviour on both my snapshots
workstation from last week, and more recently from inside my chroot
bulk build environment based off a snapshot from yesterday (the 13th).

please let me know if there is more information I may provide.


best,
~Jason

Re: Glade3, anyone using/interested in a port?

2008-11-12 Thread Jason Beaudoin 
On Tue, Nov 11, 2008 at 6:07 PM, Jasper Lievisse Adriaanse
[EMAIL PROTECTED] wrote:
 On Mon, Nov 10, 2008 at 12:01:48PM -0500, Jason Beaudoin wrote:
 Re Jasper's additions/cleanup:

  DESCR should be in pkg/ and not in the top level directory.

 right, my mistake

  further, i've cleaned up the port a fair bit, and the attached version
  is what i intend to commit.

 great! I have a couple questions/comments, in an attempt at better
 understanding the process. I'd like to continue finding ways to
 contribute, I hope you don't mind my inquisitive nature here  :)

  some things i've changed:
  - updated the port to the latest version

 I used the 3.4 series as I understand that the 3.5 (odd) series is the
 unstable track in glade's development:
 http://glade.gnome.org/todo.html

 It was also my understanding that, when given the opportunity, using
 the stable release was OpenBSD port's preferred route.
 yep, but 3.5 is considered mature enough.

  - added missing dependencies (gnome-doc-utils, desktop-file-utils, yelp)

 is the dependency for desktop-file-utils pulled in with: DESKTOP_FILES
 = Yes ?
 indeed, please see x11/gnome/gnome.port.mk

  - added missing PLIST goo (@exec/@unexec)

 are you referring to the last few lines of the PLIST file? I'm
 perplexed how I missed this, is there somewhere in the documentation
 that discusses this?
 those lines indeed, and it's not fully documented (shame on me).

  - start the shared library version at 0.0

 is the convention that the first number is openbsd's (internal)
 sharelib version, and the version given within the comment is external
 to the project, glade in this case?
 the convention for new libraries is to start at 0.0, no matter the
 version of the upstream project. later bumps go according to the rules
 layed out in the docs.

  - actually make use of gnome.port.mk

 I missed details about this, how is this done?
 coming soon to a port-modules(5) on a mirror near you!
 (for now, just use other ports as a reference.)

  - no need for the AUTO*_VERSION variables
  - add a missing configure argument (we take care of this with @exec in
   PLIST)

 this confuses me..

 scrollkeeper is noted as build/run dependencies, though there is the
 --disable-scrollkeeper configure argument, and calls to exec in the
 PLIST. if you feel up to the task and have time to explain, I'm
 curious how this all works and what I'm missing.
 the configure argument (--disable-scrollkeeper) is to make sure the
 build process doesn't try to build the scrollkeeper catalog during
 install. as this will generate a whole bunch of files into /var (, which
 will also trip systrace).
 it's just easier to execute the command ourselves at the end of the
 installation/removal (@exec/@unexec) and be able to control it.

snip

thanks for all the explanations :)

cheers!
~Jason

Re: Glade3, anyone using/interested in a port?

2008-11-10 Thread Jason Beaudoin 
Re Jasper's additions/cleanup:

 DESCR should be in pkg/ and not in the top level directory.

right, my mistake

 further, i've cleaned up the port a fair bit, and the attached version
 is what i intend to commit.

great! I have a couple questions/comments, in an attempt at better
understanding the process. I'd like to continue finding ways to
contribute, I hope you don't mind my inquisitive nature here  :)

 some things i've changed:
 - updated the port to the latest version

I used the 3.4 series as I understand that the 3.5 (odd) series is the
unstable track in glade's development:
http://glade.gnome.org/todo.html

It was also my understanding that, when given the opportunity, using
the stable release was OpenBSD port's preferred route.

 - added missing dependencies (gnome-doc-utils, desktop-file-utils, yelp)

is the dependency for desktop-file-utils pulled in with: DESKTOP_FILES
= Yes ?

 - added missing PLIST goo (@exec/@unexec)

are you referring to the last few lines of the PLIST file? I'm
perplexed how I missed this, is there somewhere in the documentation
that discusses this?

 - start the shared library version at 0.0

is the convention that the first number is openbsd's (internal)
sharelib version, and the version given within the comment is external
to the project, glade in this case?

 - actually make use of gnome.port.mk

I missed details about this, how is this done?

 - no need for the AUTO*_VERSION variables
 - add a missing configure argument (we take care of this with @exec in
  PLIST)

this confuses me..

scrollkeeper is noted as build/run dependencies, though there is the
--disable-scrollkeeper configure argument, and calls to exec in the
PLIST. if you feel up to the task and have time to explain, I'm
curious how this all works and what I'm missing.

 - and some more minor cleaning.

thanks! I ran though the make steps to build and test-run the package,
all went well.

 comments/oks?

 cheers,
 jasper

 --
 Intelligence should guide our actions, but in harmony with the
  texture of the situation at hand
-- Francisco Varela


Regards,
~Jason

Re: Glade3, anyone using/interested in a port?

2008-11-09 Thread Jason Beaudoin 
good morning!


an update, some progress, and a request for help:
 - I've attached my port-in-progress, along with some text files that
I've referenced/used in figuring this out (found under the ref
directory), and the Makefile is at the end of this email.
 - all of the resources I've been pointed towards or found myself
(openbsd papers, the ports developer documentation, etc) have been
tremendously helpful, answering all of my questions thus far, the only
difficulty being dependency resolution.
 - to resolve glade's dependencies, I have used several references,
and here is what I have so far:
 - glade's own documentation mentions libxml2 and libglade as
runtime dependencies
 - netbsd's glade3 port has a few buildlinks mainly: gtk2,
libxml2, hicolor-icon-theme, desktop-file-utils, libbonobui, and
libgnomeui
 - the port-in-progress Jasper provided, also notes
textproc/scrollkeeper as a build/run-time dependency

 - I don't really have a specific problem right now, but I know that
my Makefile isn't quite working correctly, which I believe stems from
having the correct dependencies (but I'm not sure).

Current state:
 - I captured the contents of libs.txt during a run of make build.
This helps to show what the configure script found, stuck in glade's
Makefile, and is now set to be built during make build, but I also
expect that this helps determine the WANTLIB list.. is this a valid
assumption?
 - I believe make configure works fine (output is included:
make_configure.log)
 - make build *seems* to work, but I'm skeptical because of the
issues that arise later, and because I still have the MODULES lines
commented out (the make build output is included as well:
make_build.log). I also don't really trust all of the DEPENDS lines
being complete.
 - I have commented out the MODULES line because when it is present, I
get a lot of the following when running make build (as well as some
stuff about line 54):

/usr/ports/infrastructure/mk/modules.port.mk, line 41: Missing
dependency operator
/usr/ports/infrastructure/mk/modules.port.mk, line 42: Could not
find /usr/ports/infrastructure/mk/\ .port.mk
/usr/ports/infrastructure/mk/modules.port.mk, line 41: warning:
Missing closing parenthesis for exists()
/usr/ports/infrastructure/mk/modules.port.mk, line 41: Malformed
conditional (exists(${PORTSDIR}/infrastructure/mk/\ .port.mk))
/usr/ports/infrastructure/mk/modules.port.mk, line 41: Missing
dependency operator
/usr/ports/infrastructure/mk/modules.port.mk, line 42: Could not
find /usr/ports/infrastructure/mk/\ .port.mk
/usr/ports/infrastructure/mk/modules.port.mk, line 41: warning:
Missing closing parenthesis for exists()
/usr/ports/infrastructure/mk/modules.port.mk, line 41: Malformed
conditional (exists(${PORTSDIR}/infrastructure/mk/\ .port.mk))
/usr/ports/infrastructure/mk/modules.port.mk, line 41: Missing
dependency operator
/usr/ports/infrastructure/mk/modules.port.mk, line 42: Could not
find /usr/ports/infrastructure/mk/\ .port.mk


- I am currently a little confused by the output of the depends check
with make port-lib-depends-check. The output can be seen in
ref/make_port-lib-depends-check.log. What I've determined is this:
 - It appears WANTLIBS has entries glade3 doens't need, I'm
guessing this from the Bogus WANTLIB lines in the output. I simply
copy/pasted the WANTLIB line from the port-in-progress Jasper
provided, as I'm not sure how to determine these with accuracy.
 - there are a few other libraries needed, as shown by: WANTLIB
+= Xcomposite Xdamage iconv intl pcre pixman-1

am I understanding this output correctly?


- make package doesn't work, showing that I've screwed up further back
along the line:

# make package
===  Looking for glade3-3.4.5.tgz in $PKG_PATH - not found
*** Error code 1

Stop in /mnt/neptune/Development/OpenBSD/ports/devel/glade3-me (line
1416 of /usr/ports/infrastructure/mk/bsd.port.mk).
`/usr/obj/ports//glade3-3.4.5/fake-i386/.fake_done' is up to date.
===  Building package for glade3-3.4.5
Create /usr/ports/packages/i386/all/glade3-3.4.5.tgz
can't open /mnt/neptune/Development/OpenBSD/ports/devel/glade3-me/pkg/DESCR
at /usr/libdata/perl5/OpenBSD/Subst.pm line 85.
===  Cleaning for glade3-3.4.5
rm -f /usr/ports/packages/i386/all/glade3-3.4.5.tgz
/usr/ports/packages/i386/ftp/glade3-3.4.5.tgz
/usr/ports/packages/i386/cdrom/glade3-3.4.5.tgz
*** Error code 1

Stop in /mnt/neptune/Development/OpenBSD/ports/devel/glade3-me (line
1424 of /usr/ports/infrastructure/mk/bsd.port.mk).
*** Error code 1

Stop in /mnt/neptune/Development/OpenBSD/ports/devel/glade3-me (line
1424 of /usr/ports/infrastructure/mk/bsd.port.mk).
*** Error code 1

Stop in /mnt/neptune/Development/OpenBSD/ports/devel/glade3-me (line
1964 of /usr/ports/infrastructure/mk/bsd.port.mk).
# cat DESCR
Glade is a free user interface builder for GTK+ released under the GNU
General Public License (GPL).  (GTK+, which stands for the Gimp ToolKit,
is a library for creating graphical user interfaces for the X

Re: Glade3, anyone using/interested in a port?

2008-11-06 Thread Jason Beaudoin 
On Thu, Nov 6, 2008 at 6:38 AM, Thomas Pfaff [EMAIL PROTECTED] wrote:
 On Wed, 5 Nov 2008 21:44:07 -0500
 Jason Beaudoin [EMAIL PROTECTED] wrote:

 Hey folks!

 I'm interested in using glade3 on openbsd [...]

 So am I.  I started working on a port a while back, but I lacked the
 time to complete it (or even get it working).  If you decide to start
 working on a port, I'm definitely willing to test it on my systems
 and, if time permits, help make it work properly.

 Thomas


Thank you, everyone, for all the pointers, starter hints and support!

I shall take the port in progress that Jasper provided, and keep
things rolling. I am currently unemployed (but hopefully that will
change after my interviews today and tomorrow!), so projects like this
have been great, and I expect to have something ready for comments and
clean up later today. Thanks again!


~Jason

Glade3, anyone using/interested in a port?

2008-11-05 Thread Jason Beaudoin 
Hey folks!

I'm interested in using glade3 on openbsd, but noticed that there was
no current glade port available. It appears that there once was, long,
long ago, but no longer. Several questions resulted:

 . does anyone have a (working or not) port of glade3 for OpenBSD that
you've used, or were hacking on?
 . if not, is there any interest in having one added to the tree? (or
rather, is there anything preventing this, licensing or otherwise?)
 . what happened to the port for the older versions of glade, I don't
seem to have a devel/glade in my tree, though there have been recent
(last 2 months) changes noted in ports-cvs.. am I just being
incompetent in my port-finding skills?
 . If this older port exists, I'm assuming a new maintainer wouldn't hurt?

either way, I'll take a stab at getting a port together, and maybe
have something for you all to pick apart sometime soon.


thanks,

~Jason

Re: Glade3, anyone using/interested in a port?

2008-11-05 Thread Jason Beaudoin 
snip

 there are devel/libglade and devel/libglade2

 Regards,
 Markus


devel/libglade2 is a runtime dependency, I'm talking about devel/glade
(the GTK+2 interface builder). I found that NetBSD has glade3 in
pkgsrc, but I quickly gave up on trying to understand their framework.
I'm in the process (and slowly making progress) at building my first
port here.

while the ports checklist has been helpful, there isn't much out there
about getting the build process to work when it fails on you. Should I
be looking in bsd.port.mk for more information? (I am currently having
trouble getting ports to run the configure script and generate a
Makefile for gmake.)


thanks!
~Jason