From bwalton at opencsw.org Mon Dec 1 16:08:16 2008 From: bwalton at opencsw.org (Ben Walton) Date: Mon, 01 Dec 2008 10:08:16 -0500 Subject: [csw-maintainers] multiple sources, multiple urls? Message-ID: <1228143959-sup-746@ntdws12.chass.utoronto.ca> Hi All, I'll bang away on this myself, but in true 'lazyweb' fashion, I'll ask for advice also. What is the best way to handle GAR description for a package that requires multiple source files from multiple (different) locations? ...Do I just reference all of the required locations in MASTER_SITES and then put the different files in DISTFILES and have wget stumble across the required combos the first time (until they're GARchived)? Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From dam at opencsw.org Mon Dec 1 16:14:19 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 1 Dec 2008 16:14:19 +0100 Subject: [csw-maintainers] multiple sources, multiple urls? In-Reply-To: <1228143959-sup-746@ntdws12.chass.utoronto.ca> References: <1228143959-sup-746@ntdws12.chass.utoronto.ca> Message-ID: <61827A2B-2173-42F9-B565-93BD58CDD244@opencsw.org> Hi Ben, Am 01.12.2008 um 16:08 schrieb Ben Walton: > I'll bang away on this myself, but in true 'lazyweb' fashion, I'll ask > for advice also. What is the best way to handle GAR description for a > package that requires multiple source files from multiple (different) > locations? > > ...Do I just reference all of the required locations in MASTER_SITES > and then put the different files in DISTFILES and have wget stumble > across the required combos the first time (until they're GARchived)? Yes, currently that's the way to go. Better ideas welcome! Best regards -- Dago From skayser at opencsw.org Mon Dec 1 16:35:31 2008 From: skayser at opencsw.org (Sebastian Kayser) Date: Mon, 01 Dec 2008 16:35:31 +0100 Subject: [csw-maintainers] mGAR: UNCOMMITED in PSTAMP field? Message-ID: <49340443.1080807@opencsw.org> Hi, when using mGAR, what's the magic procedure to make the "UNCOMMITED" in the package PSTAMP field go away? Even when i commit all my package files, then checkout a pristine working copy and rebuild the package, the UNCOMMITED doesn't go away. 1) svn co https://gar.svn.sf.net/svnroot/gar/csw/mgar/pkg/synergy 2) cd synergy/trunk 3) gmake package 4) pkginfo has PSTAMP: skayser at build8x-r2401UNCOMMITTED-20081201153621 When i try to follow what is going on inside gar/gar.pkg.mk i see # Case 3+4: The directory belongs to a repository ifneq ($(shell $(SVN) status 2>/dev/null),) # Case 3: Not everything was committed properly _SVN_UNCOMMITTED = UNCOMMITTED endif And doing the "svn status" manually i get: ~/mgar/synergy/trunk$ svn status X gar Performing status on external item at 'gar' ~/mgar/synergy/trunk$ Do i have to do things differently? Sebastian From dam at opencsw.org Mon Dec 1 16:48:12 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 1 Dec 2008 16:48:12 +0100 Subject: [csw-maintainers] mGAR: UNCOMMITED in PSTAMP field? In-Reply-To: <49340443.1080807@opencsw.org> References: <49340443.1080807@opencsw.org> Message-ID: <417F236E-5CA8-4E70-8E33-C4DC69A7362D@opencsw.org> Hi Sebastian, Am 01.12.2008 um 16:35 schrieb Sebastian Kayser: > when using mGAR, what's the magic procedure to make the "UNCOMMITED" > in > the package PSTAMP field go away? 'svn status' must not show anything. That means you must add and commit all files to be in the repository and ignore or remove all the rest. The idea is to show that there may be stuff which avoids reproducing the package by checking out the indicated revision. > Even when i commit all my package files, then checkout a pristine > working copy and rebuild the package, the UNCOMMITED doesn't go away. > > 1) svn co https://gar.svn.sf.net/svnroot/gar/csw/mgar/pkg/synergy > 2) cd synergy/trunk > 3) gmake package > 4) pkginfo has > PSTAMP: skayser at build8x-r2401UNCOMMITTED-20081201153621 > > When i try to follow what is going on inside gar/gar.pkg.mk i see > > # Case 3+4: The directory belongs to a repository > ifneq ($(shell $(SVN) status 2>/dev/null),) > # Case 3: Not everything was committed properly > _SVN_UNCOMMITTED = UNCOMMITTED > endif > > And doing the "svn status" manually i get: > > ~/mgar/synergy/trunk$ svn status > X gar > > Performing status on external item at 'gar' > ~/mgar/synergy/trunk$ > > Do i have to do things differently? No. This is an error made by me during the transition to mGAR. The external reference should be ignored. However, just adding --ignore-externals doesn't fix this. I'll look into this. Thanks for pointing this out. Best regards -- Dago PS: I still have your list of questions here, I'll answer them soon. From phil at bolthole.com Mon Dec 1 17:17:29 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 1 Dec 2008 08:17:29 -0800 Subject: [csw-maintainers] mGAR: UNCOMMITED in PSTAMP field? In-Reply-To: <417F236E-5CA8-4E70-8E33-C4DC69A7362D@opencsw.org>; from dam@opencsw.org on Mon, Dec 01, 2008 at 04:48:12PM +0100 References: <49340443.1080807@opencsw.org> <417F236E-5CA8-4E70-8E33-C4DC69A7362D@opencsw.org> Message-ID: <20081201081729.A19866@bolthole.com> On Mon, Dec 01, 2008 at 04:48:12PM +0100, Dagobert Michelsen wrote: > Hi Sebastian, > > Am 01.12.2008 um 16:35 schrieb Sebastian Kayser: > > when using mGAR, what's the magic procedure to make the "UNCOMMITED" > > in > > the package PSTAMP field go away? > > 'svn status' must not show anything. That means you must add > and commit all files to be in the repository and ignore or remove > all the rest. The idea is to show that there may be stuff which > avoids reproducing the package by checking out the indicated > revision. > Seems appropriate for another little nudge for, "Hey, it would be really nice to have some kind of CSW wrapper that does all the svn stuff for you, rather than having to manually track that stuff down, and manually check it in blah blah..." :-} From skayser at opencsw.org Mon Dec 1 19:09:19 2008 From: skayser at opencsw.org (Sebastian Kayser) Date: Mon, 01 Dec 2008 19:09:19 +0100 Subject: [csw-maintainers] mGAR: UNCOMMITED in PSTAMP field? In-Reply-To: <20081201081729.A19866@bolthole.com> References: <49340443.1080807@opencsw.org> <417F236E-5CA8-4E70-8E33-C4DC69A7362D@opencsw.org> <20081201081729.A19866@bolthole.com> Message-ID: <4934284F.6090005@opencsw.org> Philip Brown wrote: > Seems appropriate for another little nudge for, "Hey, it would be really > nice to have some kind of CSW wrapper that does all the svn stuff for you, > rather than having to manually track that stuff down, and manually check it > in blah blah..." It is rather simple, but what i did to save me the "manually track that stuff down" part is a small bash function function mgar-get { svn co https://gar.svn.sf.net/svnroot/gar/csw/mgar/pkg/$1 } that i can call to check out a given package. This way i don't have to remember the SVN URL. Sebastian From phil at bolthole.com Mon Dec 1 19:16:44 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 1 Dec 2008 10:16:44 -0800 Subject: [csw-maintainers] mGAR: UNCOMMITED in PSTAMP field? In-Reply-To: <4934284F.6090005@opencsw.org>; from skayser@opencsw.org on Mon, Dec 01, 2008 at 07:09:19PM +0100 References: <49340443.1080807@opencsw.org> <417F236E-5CA8-4E70-8E33-C4DC69A7362D@opencsw.org> <20081201081729.A19866@bolthole.com> <4934284F.6090005@opencsw.org> Message-ID: <20081201101644.L19866@bolthole.com> On Mon, Dec 01, 2008 at 07:09:19PM +0100, Sebastian Kayser wrote: > Philip Brown wrote: > > Seems appropriate for another little nudge for, "Hey, it would be really > > nice to have some kind of CSW wrapper that does all the svn stuff for you, > > rather than having to manually track that stuff down, and manually check it > > in blah blah..." > > It is rather simple, but what i did to save me the "manually track that > stuff down" part is a small bash function > > function mgar-get { > svn co https://gar.svn.sf.net/svnroot/gar/csw/mgar/pkg/$1 > } > > that i can call to check out a given package. This way i don't have to > remember the SVN URL. > It's nice that you did that for you. but its kind of silly that all maintainers have to do that individually, isnt it? my point is that it would be more efficient, and nice to our maintainers, if we had some pre-written utils like that, as part of our cswutils package. (Until such time as we get some kind of standalone gar-for-csw package) (Wanna write some, Sebastian? :-) From skayser at opencsw.org Mon Dec 1 20:43:40 2008 From: skayser at opencsw.org (Sebastian Kayser) Date: Mon, 01 Dec 2008 20:43:40 +0100 Subject: [csw-maintainers] mGAR: UNCOMMITED in PSTAMP field? In-Reply-To: <20081201101644.L19866@bolthole.com> References: <49340443.1080807@opencsw.org> <417F236E-5CA8-4E70-8E33-C4DC69A7362D@opencsw.org> <20081201081729.A19866@bolthole.com> <4934284F.6090005@opencsw.org> <20081201101644.L19866@bolthole.com> Message-ID: <49343E6C.1000803@opencsw.org> Philip Brown wrote: > On Mon, Dec 01, 2008 at 07:09:19PM +0100, Sebastian Kayser wrote: >> Philip Brown wrote: >>> Seems appropriate for another little nudge for, "Hey, it would be really >>> nice to have some kind of CSW wrapper that does all the svn stuff for you, >>> rather than having to manually track that stuff down, and manually check it >>> in blah blah..." >> It is rather simple, but what i did to save me the "manually track that >> stuff down" part is a small bash function >> >> function mgar-get { >> svn co https://gar.svn.sf.net/svnroot/gar/csw/mgar/pkg/$1 >> } >> >> that i can call to check out a given package. This way i don't have to >> remember the SVN URL. >> > > It's nice that you did that for you. but its kind of silly that all > maintainers have to do that individually, isnt it? Yup :) > my point is that it would be more efficient, and nice to our maintainers, > if we had some pre-written utils like that, as part of our cswutils > package. (Until such time as we get some kind of standalone > gar-for-csw package) Fully understood. I should have added that i don't see a clever way to wrap the remaining svn commands (add, commit), yet. By "clever" i mean, in a way that actually saves work (and is somehow foolproof), rather than just giving two commands other names. So take the bash function as an idea on how to make things easier (more ideas anyone?). However, after having built and wrapped a package the traditional (export LD_*, CPP*, ./configure, make, *pkg) way and then with mGAR i feel that mGAR already is a very nice build platform. The ability alone for a new maintainer like me to see _exactly_ how others package their software is just great. So right now, after just getting starting, i don't really mind the couple of svn commands. :) > (Wanna write some, Sebastian? :-) Not yet. Would like to get my packages on the way first. Maybe the others have some input on this in the meantime. Sebastian From dam at opencsw.org Tue Dec 2 13:16:03 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 2 Dec 2008 13:16:03 +0100 Subject: [csw-maintainers] mGAR: UNCOMMITED in PSTAMP field? In-Reply-To: <49343E6C.1000803@opencsw.org> References: <49340443.1080807@opencsw.org> <417F236E-5CA8-4E70-8E33-C4DC69A7362D@opencsw.org> <20081201081729.A19866@bolthole.com> <4934284F.6090005@opencsw.org> <20081201101644.L19866@bolthole.com> <49343E6C.1000803@opencsw.org> Message-ID: <4EFAB965-4EC6-44FC-99D3-2D7D520AEBB6@opencsw.org> Hi, Am 01.12.2008 um 20:43 schrieb Sebastian Kayser: > Fully understood. I should have added that i don't see a clever way to > wrap the remaining svn commands (add, commit), yet. By "clever" i > mean, > in a way that actually saves work (and is somehow foolproof), rather > than just giving two commands other names. ... > So right now, after just getting starting, i don't really mind the > couple of svn commands. :) These are exactly the two reasons I see against doing it right now. We may see clearer when doing source packages and upstream delivery. Best regards -- Dago From dam at opencsw.org Tue Dec 2 13:23:15 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 2 Dec 2008 13:23:15 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> Message-ID: <8671613E-32CE-462C-9775-FD648520023B@opencsw.org> Hi, Am 29.11.2008 um 22:06 schrieb Dagobert Michelsen: > Am 29.11.2008 um 18:16 schrieb Trygve Laugst?l: >>> As you can see the packages are put in /local/hudson/gar/pkgs. >>> What I >>> would like to do now is to get Hudson to put all of those packages >>> to a >>> NFS share, run a job to create a catalog and then export that to our >>> consumers. > > Good idea! Linked to > Old packages are piling up there. Should all but the latest be deleted? Should the catalog list multiple versions like the SunFreeware catalog? Currently the catalog lists the oldest :-( Best regards -- Dago From bonivart at opencsw.org Tue Dec 2 14:01:54 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Tue, 2 Dec 2008 14:01:54 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <8671613E-32CE-462C-9775-FD648520023B@opencsw.org> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> <8671613E-32CE-462C-9775-FD648520023B@opencsw.org> Message-ID: <625385e30812020501u16197f2ud8ae7d78e3376454@mail.gmail.com> On Tue, Dec 2, 2008 at 1:23 PM, Dagobert Michelsen wrote: > Old packages are piling up there. Should all but the latest > be deleted? Should the catalog list multiple versions like > the SunFreeware catalog? Currently the catalog lists the > oldest :-( Wouldn't a simple solution be to remove all but the latest? That way the catalogs would be clean and the tools would work. -- /peter From dam at opencsw.org Tue Dec 2 18:24:48 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 2 Dec 2008 18:24:48 +0100 Subject: [csw-maintainers] Legacy GAR is now gone Message-ID: Hi, I just deleted the old trunk/, tags/ and branches/joyent/. If you still need anything please either use the web repository browser with or pull in old versions of your files with svn cp -r 2437 https://gar.svn.sf.net/svnroot/gar/csw/trunk/... (Revision 2437 was the last before the first deletion) Best regards and have fun with mGAR -- Dago From dam at opencsw.org Wed Dec 3 11:19:30 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 3 Dec 2008 11:19:30 +0100 Subject: [csw-maintainers] Addition to pkginfo for repository path Message-ID: <9138C0C6-B98D-437A-8D00-B923611474FD@opencsw.org> Hi, this has been discusses earlier, but I want to take up the thread again: IMHO it would be very useful to have a separate field in the pkginfo(4) of each package pointing to the exact repository path and version, e. g. CSW_REPOSITORY=https://gar.svn.sf.net/svnroot/gar/csw/mgar/pkg/autoconf/trunk at 2451 As packages will be build from multiple destinations with hudson this exact association will help in tracking bugs in specific versions. Feedback as always welcome. Best regards -- Dago From skayser at opencsw.org Wed Dec 3 13:36:09 2008 From: skayser at opencsw.org (Sebastian Kayser) Date: Wed, 03 Dec 2008 13:36:09 +0100 Subject: [csw-maintainers] Proper way to adopt / work on packages? Message-ID: <49367D39.1050704@opencsw.org> Hi, i am currently having a look at packages that are maintained by retired maintainers in order to adopt some of them. When i started working on pv [1] yesterday a question came to my mind: How do i know that no one else is putting effort in getting the same package up to date? I would like to avoid duplicated work. This goes along with another question: When should i commit package changes? I updated the pv build files and built the x86 package just fine. Then i committed the changes to SVN just to run into an upstream bug that shows up on SPARC only (working on it). What's the preferred way: Commit early so that ongoing work is visible to others? Or commit only after everything builds fine? Sebastian [1] http://opencsw.org/packages/pv From dam at opencsw.org Wed Dec 3 13:48:01 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 3 Dec 2008 13:48:01 +0100 Subject: [csw-maintainers] Proper way to adopt / work on packages? In-Reply-To: <49367D39.1050704@opencsw.org> References: <49367D39.1050704@opencsw.org> Message-ID: Hi Sebastian, Am 03.12.2008 um 13:36 schrieb Sebastian Kayser: > i am currently having a look at packages that are maintained by > retired > maintainers in order to adopt some of them. When i started working > on pv > [1] yesterday a question came to my mind: > > How do i know that no one else is putting effort in getting the same > package up to date? I would like to avoid duplicated work. You can post on maintainers@ and announce that you will take it over and start working on it. > This goes along with another question: When should i commit package > changes? I updated the pv build files and built the x86 package just > fine. Then i committed the changes to SVN just to run into an upstream > bug that shows up on SPARC only (working on it). > > What's the preferred way: Commit early so that ongoing work is visible > to others? Or commit only after everything builds fine? Commit early, commit often. An unfinished package description is better than no package description. Even when you don't finish it another maintainer may pick up your work later and continue with what you already did. Best regards -- Dago From dam at opencsw.org Wed Dec 3 13:49:34 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 3 Dec 2008 13:49:34 +0100 Subject: [csw-maintainers] mGAR: UNCOMMITED in PSTAMP field? In-Reply-To: <49340443.1080807@opencsw.org> References: <49340443.1080807@opencsw.org> Message-ID: <9FB489AE-960A-416B-916A-8F415612F520@opencsw.org> Hi Sebastian, Am 01.12.2008 um 16:35 schrieb Sebastian Kayser: > when using mGAR, what's the magic procedure to make the "UNCOMMITED" > in > the package PSTAMP field go away? > > Even when i commit all my package files, then checkout a pristine > working copy and rebuild the package, the UNCOMMITED doesn't go away. This issues should be fixed in mGAR v1 [2453]: Please test and let me know if you encounter any other issues. Best regards -- Dago From bwalton at opencsw.org Wed Dec 3 15:13:58 2008 From: bwalton at opencsw.org (Ben Walton) Date: Wed, 03 Dec 2008 09:13:58 -0500 Subject: [csw-maintainers] Addition to pkginfo for repository path In-Reply-To: <9138C0C6-B98D-437A-8D00-B923611474FD@opencsw.org> References: <9138C0C6-B98D-437A-8D00-B923611474FD@opencsw.org> Message-ID: <1228313513-sup-2912@ntdws12.chass.utoronto.ca> Excerpts from Dagobert Michelsen's message of Wed Dec 03 05:19:30 -0500 2008: Hi Dago, > CSW_REPOSITORY=https://gar.svn.sf.net/svnroot/gar/csw/mgar/pkg/autoconf/trunk at 2451 As long as this is automated, I'm all for it. If it requires any manual upkeep (eg: the revision id) on the part of the maintainer, it will quickly fall into disrepair[1], I feel. -Ben [1]: Mostly due to our wetware bugs, not intentional neglect. -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From phil at bolthole.com Wed Dec 3 15:51:13 2008 From: phil at bolthole.com (Philip Brown) Date: Wed, 3 Dec 2008 06:51:13 -0800 Subject: [csw-maintainers] Addition to pkginfo for repository path In-Reply-To: <9138C0C6-B98D-437A-8D00-B923611474FD@opencsw.org> References: <9138C0C6-B98D-437A-8D00-B923611474FD@opencsw.org> Message-ID: <20081203145113.GA60066@bolthole.com> On Wed, Dec 03, 2008 at 11:19:30AM +0100, Dagobert Michelsen wrote: > Hi, > > this has been discusses earlier, but I want to take up > the thread again: > IMHO it would be very useful to have a separate field in the > pkginfo(4) of each package pointing to the exact repository > path and version, useful for what additional purpose? seems to me that we already potentially have this information now, with the combination of: 1. modular gar, now makes it easy to automatically determine where in the tree a package comes from: (csw/mgar/pkg/{softwarename}) 2. the PSTAMP is supposed to automatically get the version information now already. So, this "additional information" field, would seem to me to be redundant information? From dam at opencsw.org Wed Dec 3 16:53:49 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 3 Dec 2008 16:53:49 +0100 Subject: [csw-maintainers] Addition to pkginfo for repository path In-Reply-To: <20081203145113.GA60066@bolthole.com> References: <9138C0C6-B98D-437A-8D00-B923611474FD@opencsw.org> <20081203145113.GA60066@bolthole.com> Message-ID: Hi Phil, Am 03.12.2008 um 15:51 schrieb Philip Brown: > useful for what additional purpose? To make clear from what location in the repository the package was built. > seems to me that we already potentially have this information now, > with the > combination of: > > 1. modular gar, now makes it easy to automatically determine where > in the tree a package comes from: > > (csw/mgar/pkg/{softwarename}) Partly. The location is csw/mgar/pkg/(cpan/|xfce/)?(trunk|tags/|branches/ 2. the PSTAMP is supposed to automatically get the version > information now > already. The revision, yes, but not the path. > So, this "additional information" field, would seem to me to be > redundant > information? As you see it is not. We may take out the revision from the PSTAMP and include CSW_REPOSITORY as it is a superset. Best regards -- Dago From phil at bolthole.com Wed Dec 3 18:10:30 2008 From: phil at bolthole.com (Philip Brown) Date: Wed, 3 Dec 2008 09:10:30 -0800 Subject: [csw-maintainers] Addition to pkginfo for repository path In-Reply-To: ; from dam@opencsw.org on Wed, Dec 03, 2008 at 04:53:49PM +0100 References: <9138C0C6-B98D-437A-8D00-B923611474FD@opencsw.org> <20081203145113.GA60066@bolthole.com> Message-ID: <20081203091030.A16758@bolthole.com> On Wed, Dec 03, 2008 at 04:53:49PM +0100, Dagobert Michelsen wrote: > > 1. modular gar, now makes it easy to automatically determine where > > in the tree a package comes from: > > > > (csw/mgar/pkg/{softwarename}) > > Partly. The location is > csw/mgar/pkg/(cpan/|xfce/)?(trunk|tags/|branches/ References: <9138C0C6-B98D-437A-8D00-B923611474FD@opencsw.org> <20081203145113.GA60066@bolthole.com> <20081203091030.A16758@bolthole.com> Message-ID: <51900830-E913-4814-82B1-E93E2B6CEF7E@opencsw.org> Hi Phil, Am 03.12.2008 um 18:10 schrieb Philip Brown: > On Wed, Dec 03, 2008 at 04:53:49PM +0100, Dagobert Michelsen wrote: >>> 1. modular gar, now makes it easy to automatically determine where >>> in the tree a package comes from: >>> >>> (csw/mgar/pkg/{softwarename}) >> >> Partly. The location is >> csw/mgar/pkg/(cpan/|xfce/)?(trunk|tags/|branches/ > Hmmmm... Intersting about the branches stuff. > That would make sense to have that info in there then. > Although seems like the "cpan/xfce" xstuff needs to be ...erm, what > is the > database term... "fully normalized"? :-) > ie: no subdirs: we need to have a 100% flat, uniform namespace for > nice clean auto-building, rather than 95%. I am unsure about this one. A normalized view is nice, but not with >700 entries. Subdirs may help here, but cpan/ alone has >380 entries. Trygve, from a Hudson point-of-view, do you have a preference for repository layout? Best regards -- Dago From dam at opencsw.org Wed Dec 3 20:26:09 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 3 Dec 2008 20:26:09 +0100 Subject: [csw-maintainers] Addition to pkginfo for repository path In-Reply-To: <1228313513-sup-2912@ntdws12.chass.utoronto.ca> References: <9138C0C6-B98D-437A-8D00-B923611474FD@opencsw.org> <1228313513-sup-2912@ntdws12.chass.utoronto.ca> Message-ID: <71BD2CAD-6283-4BCA-AF9F-697A4BEEDBF0@opencsw.org> Hi Ben, Am 03.12.2008 um 15:13 schrieb Ben Walton: > Excerpts from Dagobert Michelsen's message of Wed Dec 03 05:19:30 > -0500 2008: >> CSW_REPOSITORY=https://gar.svn.sf.net/svnroot/gar/csw/mgar/pkg/autoconf/trunk at 2451 > > As long as this is automated, I'm all for it. If it requires any > manual upkeep (eg: the revision id) on the part of the maintainer, it > will quickly fall into disrepair[1], I feel. Of course it will be included fully automated as it is now with PSTAMP :-) Best regards -- Dago From phil at bolthole.com Wed Dec 3 20:35:14 2008 From: phil at bolthole.com (Philip Brown) Date: Wed, 3 Dec 2008 11:35:14 -0800 Subject: [csw-maintainers] Addition to pkginfo for repository path In-Reply-To: <51900830-E913-4814-82B1-E93E2B6CEF7E@opencsw.org>; from dam@opencsw.org on Wed, Dec 03, 2008 at 08:22:29PM +0100 References: <9138C0C6-B98D-437A-8D00-B923611474FD@opencsw.org> <20081203145113.GA60066@bolthole.com> <20081203091030.A16758@bolthole.com> <51900830-E913-4814-82B1-E93E2B6CEF7E@opencsw.org> Message-ID: <20081203113514.F16758@bolthole.com> On Wed, Dec 03, 2008 at 08:22:29PM +0100, Dagobert Michelsen wrote: > I am unsure about this one. A normalized view is nice, but not > with >700 entries. Subdirs may help here, but cpan/ alone has > >380 entries. That is exactly why I suggested a few weeks ago, that you relayout to have {top}/{firstalpha}/software [eg: {top}/a/amanda/] instead of {top}/software because it would be more scalable over the long term, while still remaining consistant. You said at the time, "well, we can always redo later". Is "later" here now? ;-) From bwalton at opencsw.org Wed Dec 3 20:41:03 2008 From: bwalton at opencsw.org (Ben Walton) Date: Wed, 03 Dec 2008 14:41:03 -0500 Subject: [csw-maintainers] Addition to pkginfo for repository path In-Reply-To: <20081203113514.F16758@bolthole.com> References: <9138C0C6-B98D-437A-8D00-B923611474FD@opencsw.org> <20081203145113.GA60066@bolthole.com> <20081203091030.A16758@bolthole.com> <51900830-E913-4814-82B1-E93E2B6CEF7E@opencsw.org> <20081203113514.F16758@bolthole.com> Message-ID: <1228333178-sup-161@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Wed Dec 03 14:35:14 -0500 2008: > {top}/{firstalpha}/software > [eg: {top}/a/amanda/] If a reorg is going to happen, this gets a +1 from me. It would be nicer down the road... -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 235 bytes Desc: not available URL: From william at wbonnet.net Wed Dec 3 21:13:20 2008 From: william at wbonnet.net (William Bonnet) Date: Wed, 03 Dec 2008 21:13:20 +0100 Subject: [csw-maintainers] Addition to pkginfo for repository path In-Reply-To: <20081203113514.F16758@bolthole.com> References: <9138C0C6-B98D-437A-8D00-B923611474FD@opencsw.org> <20081203145113.GA60066@bolthole.com> <20081203091030.A16758@bolthole.com> <51900830-E913-4814-82B1-E93E2B6CEF7E@opencsw.org> <20081203113514.F16758@bolthole.com> Message-ID: <4936E860.40905@wbonnet.net> Hi > That is exactly why I suggested a few weeks ago, that you relayout > to have > > {top}/{firstalpha}/software > [eg: {top}/a/amanda/] > > instead of > > {top}/software > > because it would be more scalable over the long term, while still remaining > consistant. > This sounds good. Having a few hundred softwave at the same level is not really a good thing. > Is "later" here now? ;-) > The sooner the better :) We need to stabilize the gar tree Cheers -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.blastwave.org An OpenSolaris Community Site http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From trygvel at opencsw.org Wed Dec 3 21:29:33 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Wed, 03 Dec 2008 21:29:33 +0100 Subject: [csw-maintainers] Addition to pkginfo for repository path In-Reply-To: <51900830-E913-4814-82B1-E93E2B6CEF7E@opencsw.org> References: <9138C0C6-B98D-437A-8D00-B923611474FD@opencsw.org> <20081203145113.GA60066@bolthole.com> <20081203091030.A16758@bolthole.com> <51900830-E913-4814-82B1-E93E2B6CEF7E@opencsw.org> Message-ID: <4936EC2D.40505@opencsw.org> Dagobert Michelsen wrote: > Hi Phil, > > Am 03.12.2008 um 18:10 schrieb Philip Brown: >> On Wed, Dec 03, 2008 at 04:53:49PM +0100, Dagobert Michelsen wrote: >>>> 1. modular gar, now makes it easy to automatically determine where >>>> in the tree a package comes from: >>>> >>>> (csw/mgar/pkg/{softwarename}) >>> Partly. The location is >>> csw/mgar/pkg/(cpan/|xfce/)?(trunk|tags/|branches/> Hmmmm... Intersting about the branches stuff. >> That would make sense to have that info in there then. >> Although seems like the "cpan/xfce" xstuff needs to be ...erm, what >> is the >> database term... "fully normalized"? :-) >> ie: no subdirs: we need to have a 100% flat, uniform namespace for >> nice clean auto-building, rather than 95%. > > I am unsure about this one. A normalized view is nice, but not > with >700 entries. Subdirs may help here, but cpan/ alone has > >380 entries. Trygve, from a Hudson point-of-view, do you > have a preference for repository layout? No, Hudson really don't care. You give it an url, Hudson checks it out and build it. From iand at opencsw.org Wed Dec 3 21:40:52 2008 From: iand at opencsw.org (Ian Dickinson) Date: Wed, 03 Dec 2008 20:40:52 +0000 Subject: [csw-maintainers] GAR on buildfarm? Message-ID: <4936EED4.7040708@opencsw.org> I've been quiet for a while but now I'm about to wake up again :-) First thing I'd like to do is get my existing packages sorted out and into GAR. I assume the Getting Started with GAR doc is accurate, but I'll need to do this on a build farm somewhere - is this normal/allowed/whatever? After this, I'll look at picking up an orphan or two - I still plan to do net-snmp if no-one has done it by then. Ian From trygvel at opencsw.org Wed Dec 3 21:43:55 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Wed, 03 Dec 2008 21:43:55 +0100 Subject: [csw-maintainers] Addition to pkginfo for repository path In-Reply-To: <20081203113514.F16758@bolthole.com> References: <9138C0C6-B98D-437A-8D00-B923611474FD@opencsw.org> <20081203145113.GA60066@bolthole.com> <20081203091030.A16758@bolthole.com> <51900830-E913-4814-82B1-E93E2B6CEF7E@opencsw.org> <20081203113514.F16758@bolthole.com> Message-ID: <4936EF8B.8090108@opencsw.org> Philip Brown wrote: > On Wed, Dec 03, 2008 at 08:22:29PM +0100, Dagobert Michelsen wrote: >> I am unsure about this one. A normalized view is nice, but not >> with >700 entries. Subdirs may help here, but cpan/ alone has >> >380 entries. > > That is exactly why I suggested a few weeks ago, that you relayout > to have > > {top}/{firstalpha}/software > [eg: {top}/a/amanda/] > > instead of > > {top}/software > > because it would be more scalable over the long term, while still remaining > consistant. I don't see the big problem really. Subversion doesn't have a problem handling a couple of thousand entries (as an example see [1] with 879 packages). If you want to talk organization I wouldn't mind keeping the grouping that is already as I usually wouldn't care about cpan or xfce stuff (as I don't work on either of those). It is not unlikely that other people will re-use GAR to produce packages and that day they would most likely have their own "category". I say we structure the svn repository as we see fit and move stuff as categories get to big and merge when categories get too small. What Dago proposed should be implemented in any case as that will give us the possibility to change our minds later on without the risk of loosing any valuable data. [1]: https://pkgbuild.svn.sourceforge.net/svnroot/pkgbuild/spec-files-extra/trunk/ -- Trygve From trygvel at opencsw.org Wed Dec 3 21:47:20 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Wed, 03 Dec 2008 21:47:20 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <8671613E-32CE-462C-9775-FD648520023B@opencsw.org> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> <8671613E-32CE-462C-9775-FD648520023B@opencsw.org> Message-ID: <4936F058.1070703@opencsw.org> Dagobert Michelsen wrote: > Hi, > > Am 29.11.2008 um 22:06 schrieb Dagobert Michelsen: >> Am 29.11.2008 um 18:16 schrieb Trygve Laugst?l: >>>> As you can see the packages are put in /local/hudson/gar/pkgs. >>>> What I >>>> would like to do now is to get Hudson to put all of those packages >>>> to a >>>> NFS share, run a job to create a catalog and then export that to our >>>> consumers. >> Good idea! Linked to >> > > Old packages are piling up there. Should all but the latest > be deleted? Should the catalog list multiple versions like > the SunFreeware catalog? Currently the catalog lists the > oldest :-( Overall I would consider that a bug in both pkg-get and bldcat if they don't support multiple versions. I would expect pkg-get to select the latest, but allow me to override that with an exact version if I want to. I'm quite sure that is possible today with pkg-get, except that it will always prompt me to give an exact version. bldcat should be fixed to 1) select the latest version and 2) support multiple versions in the catalog. -- Trygve From trygvel at opencsw.org Wed Dec 3 21:48:42 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Wed, 03 Dec 2008 21:48:42 +0100 Subject: [csw-maintainers] Proper way to adopt / work on packages? In-Reply-To: References: <49367D39.1050704@opencsw.org> Message-ID: <4936F0AA.1020705@opencsw.org> Dagobert Michelsen wrote: > Hi Sebastian, > > Am 03.12.2008 um 13:36 schrieb Sebastian Kayser: >> i am currently having a look at packages that are maintained by >> retired >> maintainers in order to adopt some of them. When i started working >> on pv >> [1] yesterday a question came to my mind: >> >> How do i know that no one else is putting effort in getting the same >> package up to date? I would like to avoid duplicated work. > > You can post on maintainers@ and announce that you will take it over > and start working on it. > >> This goes along with another question: When should i commit package >> changes? I updated the pv build files and built the x86 package just >> fine. Then i committed the changes to SVN just to run into an upstream >> bug that shows up on SPARC only (working on it). >> >> What's the preferred way: Commit early so that ongoing work is visible >> to others? Or commit only after everything builds fine? > > Commit early, commit often. An unfinished package description > is better than no package description. Even when you don't > finish it another maintainer may pick up your work later > and continue with what you already did. This is where Hudson come in too. If you only have platform X boxes available and the code work I would commit and then get Hudson to build the packages on the other platform. -- Trygve From phil at bolthole.com Wed Dec 3 21:54:36 2008 From: phil at bolthole.com (Philip Brown) Date: Wed, 3 Dec 2008 12:54:36 -0800 Subject: [csw-maintainers] GAR on buildfarm? In-Reply-To: <4936EED4.7040708@opencsw.org>; from iand@opencsw.org on Wed, Dec 03, 2008 at 08:40:52PM +0000 References: <4936EED4.7040708@opencsw.org> Message-ID: <20081203125436.J16758@bolthole.com> On Wed, Dec 03, 2008 at 08:40:52PM +0000, Ian Dickinson wrote: > I've been quiet for a while but now I'm about to wake up again :-) > > First thing I'd like to do is get my existing packages sorted out and into > GAR. I assume the Getting Started with GAR doc is accurate, but I'll need to > do this on a build farm somewhere - is this normal/allowed/whatever? not really "needed"... you can "work on gar" from anywhere. it's hosted at sourceforge, after all > After this, I'll look at picking up an orphan or two - I still plan to do > net-snmp if no-one has done it by then. excellent! From bonivart at opencsw.org Wed Dec 3 22:04:27 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Wed, 3 Dec 2008 22:04:27 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <4936F058.1070703@opencsw.org> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> <8671613E-32CE-462C-9775-FD648520023B@opencsw.org> <4936F058.1070703@opencsw.org> Message-ID: <625385e30812031304r7a10f24ew201679db0ae76883@mail.gmail.com> On Wed, Dec 3, 2008 at 9:47 PM, Trygve Laugst?l wrote: > bldcat should be fixed to 1) select the latest version and 2) support > multiple versions in the catalog. For me this is a much larger issue than just changing bldcat. It's key to pkgutil that every entry in the catalog is unique so that a first match is enough. To make it support multiple versions wouldn't just make it a lot more complex but also much slower since the whole catalog must be parsed every time to make sure there's not another version present later in the catalog. Since we have always only supported the latest set of packages (in current and stable) I don't see why we would give away the simplicity. Why not do the same with testing, support the latest version of each package? I have tried to implement everything any one has asked for so far but this feels wrong to me. -- /peter From william at wbonnet.net Wed Dec 3 22:04:41 2008 From: william at wbonnet.net (William Bonnet) Date: Wed, 03 Dec 2008 22:04:41 +0100 Subject: [csw-maintainers] Proper way to adopt / work on packages? In-Reply-To: References: <49367D39.1050704@opencsw.org> Message-ID: <4936F469.9030900@wbonnet.net> Hi > You can post on maintainers@ and announce that you will take it over > and start working on it. > Maybe each maintainer could write on his wiki bio page his current work and packages. Giving a list of package he is working on ? > Commit early, commit often. An unfinished package description > is better than no package description. Even when you don't > finish it another maintainer may pick up your work later > and continue with what you already did. > Yes commit early, but take care to the syntax of the makefile. It is *prefered* that target check-upstream is working. This target is used to check for available updates of software sources. Actually there is almost no public documentation about this. I'll write some after Zurich. This target is croned each night to detect availability of updates. Maintainers will be notified by email. This is currently under test, and will be activated soon. Cheers, W. -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.blastwave.org An OpenSolaris Community Site http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From dam at opencsw.org Wed Dec 3 22:29:06 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 3 Dec 2008 22:29:06 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <625385e30812031304r7a10f24ew201679db0ae76883@mail.gmail.com> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> <8671613E-32CE-462C-9775-FD648520023B@opencsw.org> <4936F058.1070703@opencsw.org> <625385e30812031304r7a10f24ew201679db0ae76883@mail.gmail.com> Message-ID: <6BD97AD6-BBD8-4ECB-B353-33767E4164F7@opencsw.org> Hi Peter, Am 03.12.2008 um 22:04 schrieb Peter Bonivart: > For me this is a much larger issue than just changing bldcat. Especially we would need versioned dependencies which we don't have and which are *really* complicated to manage. At least I don't want multiple package versions. Best regards -- Dago From dam at opencsw.org Wed Dec 3 22:36:15 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 3 Dec 2008 22:36:15 +0100 Subject: [csw-maintainers] IMPORTANT: packages on the farm are synchronized now Message-ID: <4576E653-D109-4350-AF85-61221592106B@opencsw.org> Hi, I am now synchronizing up all packages from the farm with the current versions from the catalog. I hope it will not take longer than an hour. Best regards -- Dago From skayser at opencsw.org Wed Dec 3 22:46:37 2008 From: skayser at opencsw.org (Sebastian Kayser) Date: Wed, 03 Dec 2008 22:46:37 +0100 Subject: [csw-maintainers] GAR on buildfarm? In-Reply-To: <20081203125436.J16758@bolthole.com> References: <4936EED4.7040708@opencsw.org> <20081203125436.J16758@bolthole.com> Message-ID: <4936FE3D.9080106@opencsw.org> Philip Brown wrote: > On Wed, Dec 03, 2008 at 08:40:52PM +0000, Ian Dickinson wrote: >> I've been quiet for a while but now I'm about to wake up again :-) >> >> First thing I'd like to do is get my existing packages sorted out and into >> GAR. I assume the Getting Started with GAR doc is accurate, but I'll need to >> do this on a build farm somewhere - is this normal/allowed/whatever? > > not really "needed"... you can "work on gar" from anywhere. > it's hosted at sourceforge, after all I did kind of both. I first got myself aquainted with mGAR on the build farm (all the required applications are already in place and have the proper paths) and then setup a local build environment. I still use the build farm for the final package build, though. The Getting Started Guide is what i used for setting up my local environment. To get used to mGAR i pulled bits of information from "The GAR Tutorial" and "Packaging with mGAR" mostly. Sebastian From skayser at opencsw.org Wed Dec 3 22:55:02 2008 From: skayser at opencsw.org (Sebastian Kayser) Date: Wed, 03 Dec 2008 22:55:02 +0100 Subject: [csw-maintainers] Proper way to adopt / work on packages? In-Reply-To: References: <49367D39.1050704@opencsw.org> Message-ID: <49370036.7090102@opencsw.org> Dagobert Michelsen wrote: > Am 03.12.2008 um 13:36 schrieb Sebastian Kayser: >> i am currently having a look at packages that are maintained by >> retired >> maintainers in order to adopt some of them. When i started working >> on pv >> [1] yesterday a question came to my mind: >> >> How do i know that no one else is putting effort in getting the same >> package up to date? I would like to avoid duplicated work. > > You can post on maintainers@ and announce that you will take it over > and start working on it. Ok, will do, thanks. Another question regarding the "Retired" status. What's the difference between packages managed by a retired maintainer and orphaned packages? To me it feels the same. Do we have a page like [1] that shows all the packages that are either orphaned or managed by a retired maintainer? This way new maintainers like me could just have a look at that one to find some packages to take care of. Sebastian [1] http://opencsw.org/buglist/buglist.cgi From phil at bolthole.com Wed Dec 3 23:02:02 2008 From: phil at bolthole.com (Philip Brown) Date: Wed, 3 Dec 2008 14:02:02 -0800 Subject: [csw-maintainers] Proper way to adopt / work on packages? In-Reply-To: <49370036.7090102@opencsw.org>; from skayser@opencsw.org on Wed, Dec 03, 2008 at 10:55:02PM +0100 References: <49367D39.1050704@opencsw.org> <49370036.7090102@opencsw.org> Message-ID: <20081203140202.K16758@bolthole.com> On Wed, Dec 03, 2008 at 10:55:02PM +0100, Sebastian Kayser wrote: > Do we have a page like [1] that shows all the packages that are either > orphaned or managed by a retired maintainer? This way new maintainers > like me could just have a look at that one to find some packages to take > care of. The diference between orphaned, and retired, is subtle. "retired" has a soft implication of, "the maintainer is no longer active, but might answer questions if you are nice". "orphaned" indicates "the maintainer has dropped off the planet as far as we are concerned" From dam at opencsw.org Wed Dec 3 23:04:41 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 3 Dec 2008 23:04:41 +0100 Subject: [csw-maintainers] IMPORTANT: packages on the farm are synchronized now In-Reply-To: <4576E653-D109-4350-AF85-61221592106B@opencsw.org> References: <4576E653-D109-4350-AF85-61221592106B@opencsw.org> Message-ID: Hi, Am 03.12.2008 um 22:36 schrieb Dagobert Michelsen: > I am now synchronizing up all packages from the farm with > the current versions from the catalog. I hope it will > not take longer than an hour. The fixing is over. The following downrevs have been done: build8s# pkg-get -c |egrep -v 'Not|SAME' # (From site http://mirror/opencsw/current ) software localrev remoterev dbus 1.2.4,REV=2008.11.20 1.2.1,REV=2008.06.02 dbus_glib 0.76,REV=2008.11.20 0.74,REV=2008.06.02 dbus_glibdev 0.76,REV=2008.11.20 0.74,REV=2008.06.02 libcairo 1.8.2,REV=2008.11.19 1.4.10 libdbusdev 1.2.4,REV=2008.11.20 1.2.1,REV=2008.06.02 libxrender 0.9.4,REV=2008.11.19 0.8.3,REV=2004.03.31 render_dev 0.9.4,REV=2008.11.19 0.8,REV=2004.03.30 sqlite3 3.6.4,REV=2008.11.17 3.2.2,REV=2005.07.10 build8x# pkg-get -c |egrep -v 'Not|SAME' # (From site http://mirror/opencsw/current ) software localrev remoterev dbus 1.2.4,REV=2008.11.20 1.2.1,REV=2008.06.02 dbus_glib 0.76,REV=2008.11.20 0.74,REV=2008.06.02 dbus_glibdev 0.76,REV=2008.11.20 0.74,REV=2008.06.02 libcairo 1.8.2,REV=2008.11.19 1.4.10 libdbusdev 1.2.4,REV=2008.11.20 1.2.1,REV=2008.06.02 libxrender 0.9.4,REV=2008.11.19 0.8.3,REV=2004.03.31 render_dev 0.9.4,REV=2008.11.19 0.8,REV=2004.03.30 sqlite3 3.6.4,REV=2008.11.17 3.2.2,REV=2005.07.10 Let's see that we can get them released and I'll reinstall the new versions ASAP. Best regards -- Dago From trygvis at inamo.no Wed Dec 3 21:28:58 2008 From: trygvis at inamo.no (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Wed, 03 Dec 2008 21:28:58 +0100 Subject: [csw-maintainers] Addition to pkginfo for repository path In-Reply-To: <51900830-E913-4814-82B1-E93E2B6CEF7E@opencsw.org> References: <9138C0C6-B98D-437A-8D00-B923611474FD@opencsw.org> <20081203145113.GA60066@bolthole.com> <20081203091030.A16758@bolthole.com> <51900830-E913-4814-82B1-E93E2B6CEF7E@opencsw.org> Message-ID: <4936EC0A.8060104@inamo.no> Dagobert Michelsen wrote: > Hi Phil, > > Am 03.12.2008 um 18:10 schrieb Philip Brown: >> On Wed, Dec 03, 2008 at 04:53:49PM +0100, Dagobert Michelsen wrote: >>>> 1. modular gar, now makes it easy to automatically determine where >>>> in the tree a package comes from: >>>> >>>> (csw/mgar/pkg/{softwarename}) >>> Partly. The location is >>> csw/mgar/pkg/(cpan/|xfce/)?(trunk|tags/|branches/> Hmmmm... Intersting about the branches stuff. >> That would make sense to have that info in there then. >> Although seems like the "cpan/xfce" xstuff needs to be ...erm, what >> is the >> database term... "fully normalized"? :-) >> ie: no subdirs: we need to have a 100% flat, uniform namespace for >> nice clean auto-building, rather than 95%. > > I am unsure about this one. A normalized view is nice, but not > with >700 entries. Subdirs may help here, but cpan/ alone has > >380 entries. Trygve, from a Hudson point-of-view, do you > have a preference for repository layout? No, Hudson really don't care. You give it an url, Hudson checks it out and build it. -- Trygve From skayser at opencsw.org Thu Dec 4 00:56:11 2008 From: skayser at opencsw.org (Sebastian Kayser) Date: Thu, 04 Dec 2008 00:56:11 +0100 Subject: [csw-maintainers] mGAR: UNCOMMITED in PSTAMP field? In-Reply-To: <9FB489AE-960A-416B-916A-8F415612F520@opencsw.org> References: <49340443.1080807@opencsw.org> <9FB489AE-960A-416B-916A-8F415612F520@opencsw.org> Message-ID: <49371C9B.1020301@opencsw.org> Dagobert Michelsen wrote: > Am 01.12.2008 um 16:35 schrieb Sebastian Kayser: >> when using mGAR, what's the magic procedure to make the "UNCOMMITED" >> in >> the package PSTAMP field go away? >> >> Even when i commit all my package files, then checkout a pristine >> working copy and rebuild the package, the UNCOMMITED doesn't go away. > > This issues should be fixed in mGAR v1 [2453]: Works. Thanks! Sebastian From trygvel at opencsw.org Thu Dec 4 08:35:03 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Thu, 04 Dec 2008 08:35:03 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <625385e30812031304r7a10f24ew201679db0ae76883@mail.gmail.com> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> <8671613E-32CE-462C-9775-FD648520023B@opencsw.org> <4936F058.1070703@opencsw.org> <625385e30812031304r7a10f24ew201679db0ae76883@mail.gmail.com> Message-ID: <49378827.3090008@opencsw.org> Peter Bonivart wrote: > On Wed, Dec 3, 2008 at 9:47 PM, Trygve Laugst?l wrote: >> bldcat should be fixed to 1) select the latest version and 2) support >> multiple versions in the catalog. > > For me this is a much larger issue than just changing bldcat. It's key > to pkgutil that every entry in the catalog is unique so that a first > match is enough. To make it support multiple versions wouldn't just > make it a lot more complex but also much slower since the whole > catalog must be parsed every time to make sure there's not another > version present later in the catalog. > > Since we have always only supported the latest set of packages (in > current and stable) I don't see why we would give away the simplicity. > Why not do the same with testing, support the latest version of each > package? I only want this for the automatically built packages as the quality of the packages *might* vary, thus you need to roll back to the previous build. I think that this is an important part of the development process if you actually want to get non-maintainers to test the software. If they need to do lots of manual stuff, like wget'ing a file to get the previous build, they won't do it. In particular as it is today where the previous release is removed when a new one is installed. > I have tried to implement everything any one has asked for so far but > this feels wrong to me. Don't get me wrong, pkg-get and pkgutil are very useful tools, but I do hope this new concept can be supported. This process is also something that I'm going to push for at my client as Hudson build packages on every commit and the testers need to be able to roll up and down between versions. -- Trygve From dam at opencsw.org Thu Dec 4 08:57:48 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 4 Dec 2008 08:57:48 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <49378827.3090008@opencsw.org> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> <8671613E-32CE-462C-9775-FD648520023B@opencsw.org> <4936F058.1070703@opencsw.org> <625385e30812031304r7a10f24ew201679db0ae76883@mail.gmail.com> <49378827.3090008@opencsw.org> Message-ID: <26EC0516-DB3D-4677-8DE9-20A17BD4B1A6@opencsw.org> Hi Trygve, Am 04.12.2008 um 08:35 schrieb Trygve Laugst?l: > I think that this is an important part of the development process if > you > actually want to get non-maintainers to test the software. If they > need > to do lots of manual stuff, like wget'ing a file to get the previous > build, they won't do it. In particular as it is today where the > previous > release is removed when a new one is installed. How about adding one more dimension in the catalog: time. Then mirror.opencsw.org:/opencsw/ could look like this: current/ stable/ testing/ manually build packages restructured from /home/testing hudson/ REV=2008.12.12/ sparc/ 5.8/ / - might be older That means /home/hudson/packages holds all packages build by hudson in a flat structure and then a catalog-build-script makes hudson-subdirs for each day putting the packages in it. If a package is not rebuild on that day the latest version is used. Sounds good? Best regards -- Dago From dam at opencsw.org Thu Dec 4 09:11:14 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 4 Dec 2008 09:11:14 +0100 Subject: [csw-maintainers] Proper way to adopt / work on packages? In-Reply-To: <49370036.7090102@opencsw.org> References: <49367D39.1050704@opencsw.org> <49370036.7090102@opencsw.org> Message-ID: <15B80F3A-40B6-4678-9EDD-097642EE55B9@opencsw.org> Hi Sebastian, Am 03.12.2008 um 22:55 schrieb Sebastian Kayser: > Do we have a page like [1] that shows all the packages that are either > orphaned or managed by a retired maintainer? This way new maintainers > like me could just have a look at that one to find some packages to > take > care of. Not yet. The buglist lists packages that need care. This includes critical bugs and also version upgrade requests. William is working on a system which automatically checks for version upgrades and files bugs against the package. So the buglist will become even more important as it show which packages actually need care, just to be orphaned is not really an issue for a package which has no bugs and when there is no new version for 5 years. Best regards -- Dago From trygvel at opencsw.org Thu Dec 4 09:38:12 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Thu, 04 Dec 2008 09:38:12 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <26EC0516-DB3D-4677-8DE9-20A17BD4B1A6@opencsw.org> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> <8671613E-32CE-462C-9775-FD648520023B@opencsw.org> <4936F058.1070703@opencsw.org> <625385e30812031304r7a10f24ew201679db0ae76883@mail.gmail.com> <49378827.3090008@opencsw.org> <26EC0516-DB3D-4677-8DE9-20A17BD4B1A6@opencsw.org> Message-ID: <493796F4.60003@opencsw.org> Dagobert Michelsen wrote: > Hi Trygve, > > Am 04.12.2008 um 08:35 schrieb Trygve Laugst?l: >> I think that this is an important part of the development process if >> you >> actually want to get non-maintainers to test the software. If they >> need >> to do lots of manual stuff, like wget'ing a file to get the previous >> build, they won't do it. In particular as it is today where the >> previous >> release is removed when a new one is installed. > > How about adding one more dimension in the catalog: time. Then > mirror.opencsw.org:/opencsw/ could look like this: > > current/ > stable/ > testing/ manually build packages restructured from /home/testing > hudson/ > REV=2008.12.12/ > sparc/ > 5.8/ > / - might be older > > That means /home/hudson/packages holds all packages build by hudson in a > flat structure and then a catalog-build-script makes hudson-subdirs for > each day putting the packages in it. If a package is not rebuild on that > day the latest version is used. Sounds good? What is the gain? The package tools already have a strong concept of versions, why not support multiple versions at the same time? I'm all for backwards compatibility and all, but I really need a feature like this so I don't mind running my tools with a special flag (might be nice anyway as it indicates that I'm running development stuff). -- Trygve From phil at bolthole.com Thu Dec 4 18:13:19 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 4 Dec 2008 09:13:19 -0800 Subject: [csw-maintainers] Hudson In-Reply-To: <493796F4.60003@opencsw.org>; from trygvel@opencsw.org on Thu, Dec 04, 2008 at 09:38:12AM +0100 References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> <8671613E-32CE-462C-9775-FD648520023B@opencsw.org> <4936F058.1070703@opencsw.org> <625385e30812031304r7a10f24ew201679db0ae76883@mail.gmail.com> <49378827.3090008@opencsw.org> <26EC0516-DB3D-4677-8DE9-20A17BD4B1A6@opencsw.org> <493796F4.60003@opencsw.org> Message-ID: <20081204091318.T16758@bolthole.com> On Thu, Dec 04, 2008 at 09:38:12AM +0100, Trygve Laugst?l wrote: > What is the gain? The package tools already have a strong concept of > versions, why not support multiple versions at the same time? I'm all > for backwards compatibility and all, but I really need a feature like > this so I don't mind running my tools with a special flag (might be nice > anyway as it indicates that I'm running development stuff). Two things, just to hopefully bring people together on the same page: 1. no-one is proposing that our REGULAR trees (current, stable) have multiple versions. Just wanted to mention that as reassurance to some folks :-) 2. pkg-get already supports multiple versions to some degree. As mentioned previously, i believe it will prompt you for which one you want, though. As someone will probably not be initially aware that there even EXIST multiple versions (since normally, a big point of pkg-get is to INSULATE users from versions), I think that prompting is an important safty check. I might add an OPTION flag to pkg-get, to say "always pick latest", but I think the default behaviour will stay as "prompt if multiple versions" From Darin.Perusich at cognigencorp.com Thu Dec 4 18:28:18 2008 From: Darin.Perusich at cognigencorp.com (Darin Perusich) Date: Thu, 04 Dec 2008 12:28:18 -0500 Subject: [csw-maintainers] old blastwave home dirs Message-ID: <49381332.1000800@cognigencorp.com> Do we still have access to the blastwave home directories? I'd like to be able to get at all my old docs and crap. -- Darin Perusich Unix Systems Administrator Cognigen Corporation 395 Youngs Rd. Williamsville, NY 14221 Phone: 716-633-3463 Email: darinper at cognigencorp.com From phil at bolthole.com Thu Dec 4 18:36:21 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 4 Dec 2008 09:36:21 -0800 Subject: [csw-maintainers] old blastwave home dirs In-Reply-To: <49381332.1000800@cognigencorp.com>; from Darin.Perusich@cognigencorp.com on Thu, Dec 04, 2008 at 12:28:18PM -0500 References: <49381332.1000800@cognigencorp.com> Message-ID: <20081204093621.V16758@bolthole.com> On Thu, Dec 04, 2008 at 12:28:18PM -0500, Darin Perusich wrote: > Do we still have access to the blastwave home directories? I'd like to > be able to get at all my old docs and crap. > I'd say, after all Dennis's public slander about us "stealing" stuff, you should ask him for it. and if he refuses, publically call him out about him "stealing" stuff that is rightfully YOUR property. Even if he claims he has deleted it(which I doubt), he still has backups. From bwalton at opencsw.org Thu Dec 4 19:28:12 2008 From: bwalton at opencsw.org (Ben Walton) Date: Thu, 04 Dec 2008 13:28:12 -0500 Subject: [csw-maintainers] relatocatable packages and package scripts Message-ID: <1228414352-sup-4045@ntdws12.chass.utoronto.ca> Hi All, For the openjade project, I need to write a postinstall/preremove script pair to register/unregister the installed catalogs, using scripts provided by the sgmlcommon package. The install-catalog script creates an new file in /opt/csw/etc/sgml based on parameters passed in and then adds an entry to /opt/csw/etc/sgml/catalog to reference this new file. How would one handle PKG_INSTALL_ROOT in the face of something like this where the dependent script is unaware of the altered root environment? Do you simply do a case check against PKG_INSTALL_ROOT and alert the user to run the commands manually when the new environment is booted if the root isn't / or ''? Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From phil at bolthole.com Thu Dec 4 19:38:22 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 4 Dec 2008 10:38:22 -0800 Subject: [csw-maintainers] relatocatable packages and package scripts In-Reply-To: <1228414352-sup-4045@ntdws12.chass.utoronto.ca>; from bwalton@opencsw.org on Thu, Dec 04, 2008 at 01:28:12PM -0500 References: <1228414352-sup-4045@ntdws12.chass.utoronto.ca> Message-ID: <20081204103822.W16758@bolthole.com> On Thu, Dec 04, 2008 at 01:28:12PM -0500, Ben Walton wrote: > Hi All, > > For the openjade project, I need to write a postinstall/preremove > script pair to register/unregister the installed catalogs, using > scripts provided by the sgmlcommon package. The install-catalog > script creates an new file in /opt/csw/etc/sgml based on parameters > passed in and then adds an entry to /opt/csw/etc/sgml/catalog to > reference this new file. ok.... > > How would one handle PKG_INSTALL_ROOT in the face of something like > this where the dependent script is unaware of the altered root > environment? chroot $PKG_INSTALL_ROOT run/script/here From phil at bolthole.com Thu Dec 4 19:40:02 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 4 Dec 2008 10:40:02 -0800 Subject: [csw-maintainers] relatocatable packages and package scripts In-Reply-To: <1228414352-sup-4045@ntdws12.chass.utoronto.ca>; from bwalton@opencsw.org on Thu, Dec 04, 2008 at 01:28:12PM -0500 References: <1228414352-sup-4045@ntdws12.chass.utoronto.ca> Message-ID: <20081204104002.X16758@bolthole.com> Oh, fyi: for "relocatable packages" (ie: where you have a "BASEDIR" set) i believe that PKG_INSTALL_ROOT automatically gets $BASEDIR appended to it. Or, maybe it was that BASEDIR automatically gets PKG_INSTALL_ROOT prepended to it. somethin like that. So be extra careful. but it's doable. From bwalton at opencsw.org Thu Dec 4 19:47:19 2008 From: bwalton at opencsw.org (Ben Walton) Date: Thu, 04 Dec 2008 13:47:19 -0500 Subject: [csw-maintainers] relatocatable packages and package scripts In-Reply-To: <20081204103822.W16758@bolthole.com> References: <1228414352-sup-4045@ntdws12.chass.utoronto.ca> <20081204103822.W16758@bolthole.com> Message-ID: <1228416302-sup-1584@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Thu Dec 04 13:38:22 -0500 2008: > > How would one handle PKG_INSTALL_ROOT in the face of something like > > this where the dependent script is unaware of the altered root > > environment? > > chroot $PKG_INSTALL_ROOT run/script/here Ok, had considered that and dismissed it for some reason...I'll reread the BASEDIR vs PKG_INSTALL_ROOT documentation again. Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From bwalton at opencsw.org Thu Dec 4 20:59:29 2008 From: bwalton at opencsw.org (Ben Walton) Date: Thu, 04 Dec 2008 14:59:29 -0500 Subject: [csw-maintainers] relatocatable packages and package scripts In-Reply-To: <20081204104002.X16758@bolthole.com> References: <1228414352-sup-4045@ntdws12.chass.utoronto.ca> <20081204104002.X16758@bolthole.com> Message-ID: <1228420336-sup-4801@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Thu Dec 04 13:40:02 -0500 2008: > Oh, fyi: for "relocatable packages" > (ie: where you have a "BASEDIR" set) Ok, I had confused the terminology in my head. I was thinking that -R was relocatable, but that's not the proper Sun-blessed term for this. I'm not overriding BASEDIR, and it seems that GAR leaves it unset, (which sees it recorded in the post-install pkginfo as /). This seems sensible to me, as throwing relocation into the mix for many things would be in the 'cruel and unusual' category (eg: we've gone to great length to get paths into files through autoconf, etc...corrections to this thinking are welcome, of course). Are we ok to support PKG_INSTALL_ROOT and not worry about BASEDIR then, as far as CSW is concerned? > i believe that PKG_INSTALL_ROOT automatically gets $BASEDIR appended > to it. This is correct. Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From phil at bolthole.com Thu Dec 4 21:38:20 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 4 Dec 2008 12:38:20 -0800 Subject: [csw-maintainers] relatocatable packages and package scripts In-Reply-To: <1228420336-sup-4801@ntdws12.chass.utoronto.ca>; from bwalton@opencsw.org on Thu, Dec 04, 2008 at 02:59:29PM -0500 References: <1228414352-sup-4045@ntdws12.chass.utoronto.ca> <20081204104002.X16758@bolthole.com> <1228420336-sup-4801@ntdws12.chass.utoronto.ca> Message-ID: <20081204123820.C16758@bolthole.com> On Thu, Dec 04, 2008 at 02:59:29PM -0500, Ben Walton wrote: > > Ok, I had confused the terminology in my head. I was thinking that -R > was relocatable, but that's not the proper Sun-blessed term for > this. nope. seems like you are talking about "how do I handle a NON-RELOCATABLE (ie: not using BASEDIR) package, being called with 'pkgadd -R /some/thing mypkg' ?" > Are we ok to support PKG_INSTALL_ROOT and not worry about BASEDIR > then, as far as CSW is concerned? If your package doesnt use BASEDIR normally, then you dont have to worry about it. See other packages with postinstall scripts for more specific examples if you like. From bwalton at opencsw.org Thu Dec 4 21:44:41 2008 From: bwalton at opencsw.org (Ben Walton) Date: Thu, 04 Dec 2008 15:44:41 -0500 Subject: [csw-maintainers] relatocatable packages and package scripts In-Reply-To: <20081204123820.C16758@bolthole.com> References: <1228414352-sup-4045@ntdws12.chass.utoronto.ca> <20081204104002.X16758@bolthole.com> <1228420336-sup-4801@ntdws12.chass.utoronto.ca> <20081204123820.C16758@bolthole.com> Message-ID: <1228423377-sup-2956@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Thu Dec 04 15:38:20 -0500 2008: > On Thu, Dec 04, 2008 at 02:59:29PM -0500, Ben Walton wrote: > nope. seems like you are talking about > "how do I handle a NON-RELOCATABLE (ie: not using BASEDIR) package, being > called with 'pkgadd -R /some/thing mypkg' ?" Yes, exactly. > If your package doesnt use BASEDIR normally, then you dont have to worry > about it. Perfect. Is this a widely used feature at all? > See other packages with postinstall scripts for more specific examples if > you like. I was already referencing the exim package, as it's one that I use that I knew had scripts in play. Anyway, I think that as long as chroot is kosher, that I'm all set. Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From iand at opencsw.org Thu Dec 4 22:59:07 2008 From: iand at opencsw.org (Ian Dickinson) Date: Thu, 04 Dec 2008 21:59:07 +0000 Subject: [csw-maintainers] old blastwave home dirs In-Reply-To: <20081204093621.V16758@bolthole.com> References: <49381332.1000800@cognigencorp.com> <20081204093621.V16758@bolthole.com> Message-ID: <493852AB.8010007@opencsw.org> Philip Brown wrote: > On Thu, Dec 04, 2008 at 12:28:18PM -0500, Darin Perusich wrote: >> Do we still have access to the blastwave home directories? I'd like to >> be able to get at all my old docs and crap. > > I'd say, after all Dennis's public slander about us "stealing" stuff, you > should ask him for it. and if he refuses, publically call him out about him > "stealing" stuff that is rightfully YOUR property. > > Even if he claims he has deleted it(which I doubt), he still has backups. When I asked him for this (access, or a tarball), I got no response, yet he's still listing me as a maintainer. Don't get your hopes up. :-( Ian From phil at bolthole.com Thu Dec 4 23:20:15 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 4 Dec 2008 14:20:15 -0800 Subject: [csw-maintainers] old blastwave home dirs In-Reply-To: <493852AB.8010007@opencsw.org>; from iand@opencsw.org on Thu, Dec 04, 2008 at 09:59:07PM +0000 References: <49381332.1000800@cognigencorp.com> <20081204093621.V16758@bolthole.com> <493852AB.8010007@opencsw.org> Message-ID: <20081204142015.G16758@bolthole.com> On Thu, Dec 04, 2008 at 09:59:07PM +0000, Ian Dickinson wrote: > Philip Brown wrote: > > I'd say, after all Dennis's public slander about us "stealing" stuff, you > > should ask him for it. and if he refuses, publically call him out about him > > "stealing" stuff that is rightfully YOUR property. > > > > Even if he claims he has deleted it(which I doubt), he still has backups. > > When I asked him for this (access, or a tarball), I got no response, yet he's > still listing me as a maintainer. > > Don't get your hopes up. :-( post it on the opensolaris mailing list and mention how long it has been since you didnt get a response from him to his direct email. (presumably a reasonable period to wait is 3 days) betcha that will get a response. and/or corner him on the #blastwave irc channel on freenode.net and keep a chat log of your request. then post it publically if he doesnt comply within a few days. And then again, perhaps Dennis will "find out" about this, since we're discussing it here, and decide to be more reasonable, proactively. A reminder: Dennis does not "own" **ONE THING** that maintainers did, while they were doing things "on blastwave". A person's work -- their "intellectual property".... is *theirs*, unless they sign away their work, or there is an implicit contract of "work for hire". Dennis never paid anyone 1 cent for what they did. Therefore, there was no "hire" being done. Therefore, so-called "blastwave" packages, and any related scripts and documentation, remain the intellectual property of the individual maintainer. From dam at opencsw.org Fri Dec 5 08:01:28 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 5 Dec 2008 08:01:28 +0100 Subject: [csw-maintainers] Standard for package naming Message-ID: <22225B82-435C-4EDA-A841-7448D7CA5E63@opencsw.org> Hi, I wonder if there is a standard on package naming, because for development packages there is a wide variety of suffixes, both in catalog and package names: CSWapache2-devel apache2_devel - Apache 2.2 development support CSWbdb44-devel berkeleydb44_devel - BerkeleyDB 4.4 development support CSWkrb5libdev krb5_lib_dev - MIT Kerberos 5 developer libraries CSWlibdbusdev libdbusdev - DBus Message Bus System - development headers CSWneon-devel neon_devel - Neon HTTP and WebDAV development support CSWoldapdevel openldap_devel - OpenLDAP development support (oldapdevel) CSWossldevel openssl_devel - Openssl development support CSWrenderdev render_dev - fontconfig.org render development files There seems to be a majority for *-devel for package-names and *_devel for catalog names. However, for runtime packages this is not so good: CSWapache2rt apache2rt - Apache 2.2 runtime libraries CSWcurlrt curlrt - Library for common Internet protocols Runtime CSWgcc3corert gcc3corert - GNU C Compiler Run Time CSWgcc3g++rt gcc3g++rt - GNU C++ Compiler Run Time CSWgcc4corert gcc4corert - GNU C Compiler Run Time CSWgcc4g++rt gcc4g++rt - GNU C++ Compiler Run Time CSWlibtoolrt libtool_rt - Generic library support runtime libraries CSWmysql5rt mysql5rt - run-time libraries for mysql5 CSWoldaprt openldap_rt - OpenLDAP runtime libraries (oldaprt) CSWosslrt openssl_rt - Openssl runtime libraries CSWvimrt vimrt - vim shared runtime and documentation Package names *rt are named inconsistent to *-devel as before. Catalog names are mixed again, sometime *_rt, sometimes *rt. Personally I like *-devel, *-rt, *_devel and *_rt, but I really don't care what is chosen, but whatever we choose the package names should be adjust and bugs should be filed for renaming. Best regards -- Dago From phil at bolthole.com Fri Dec 5 15:10:37 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 5 Dec 2008 06:10:37 -0800 Subject: [csw-maintainers] Standard for package naming In-Reply-To: <22225B82-435C-4EDA-A841-7448D7CA5E63@opencsw.org> References: <22225B82-435C-4EDA-A841-7448D7CA5E63@opencsw.org> Message-ID: <20081205141036.GB98262@bolthole.com> On Fri, Dec 05, 2008 at 08:01:28AM +0100, Dagobert Michelsen wrote: > Personally I like *-devel, *-rt, *_devel and *_rt, i agree > don't care what is chosen, but whatever we choose the package > names should be adjust and bugs should be filed for renaming. I would disagree here. renaming packages (at least the CSWxxx names) is ugly, becuase of depandancies, and i would prefer they NOT be renamed. unless they havef zero dependancies. From trygvel at opencsw.org Fri Dec 5 17:04:42 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Fri, 05 Dec 2008 17:04:42 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <20081204091318.T16758@bolthole.com> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> <8671613E-32CE-462C-9775-FD648520023B@opencsw.org> <4936F058.1070703@opencsw.org> <625385e30812031304r7a10f24ew201679db0ae76883@mail.gmail.com> <49378827.3090008@opencsw.org> <26EC0516-DB3D-4677-8DE9-20A17BD4B1A6@opencsw.org> <493796F4.60003@opencsw.org> <20081204091318.T16758@bolthole.com> Message-ID: <4939511A.2060207@opencsw.org> Philip Brown wrote: > On Thu, Dec 04, 2008 at 09:38:12AM +0100, Trygve Laugst?l wrote: >> What is the gain? The package tools already have a strong concept of >> versions, why not support multiple versions at the same time? I'm all >> for backwards compatibility and all, but I really need a feature like >> this so I don't mind running my tools with a special flag (might be nice >> anyway as it indicates that I'm running development stuff). > > Two things, just to hopefully bring people together on the same page: > > 1. no-one is proposing that our REGULAR trees (current, stable) have > multiple versions. Just wanted to mention that as reassurance to some > folks :-) Right. > 2. pkg-get already supports multiple versions to some degree. > As mentioned previously, i believe it will prompt you for which one you > want, though. > > As someone will probably not be initially aware that there even > EXIST multiple versions (since normally, a big point of > pkg-get is to INSULATE users from versions), I think that prompting > is an important safty check. > > I might add an OPTION flag to pkg-get, to say "always pick latest", but > I think the default behaviour will stay as "prompt if multiple versions" I would like such an option :) -- Trygve From bwalton at opencsw.org Fri Dec 5 21:40:44 2008 From: bwalton at opencsw.org (Ben Walton) Date: Fri, 05 Dec 2008 15:40:44 -0500 Subject: [csw-maintainers] libxml2 question Message-ID: <1228509292-sup-5532@ntdws12.chass.utoronto.ca> Hi All, I'm packaging up docbook dtds and am using xmlcatalog to add entries to the system sgml catalog, so that they're reference-able by all tools looking at the global catalog. It seems though, that the libxml2-supplied xmlcatalog tool updates /etc/sgml/catalog instead of /opt/csw/etc/sgml/catalog. I'm not sure if this is a bug or not...should something like this look in the system /etc instead of the CSW etc? Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From pfelecan at opencsw.org Sun Dec 7 17:05:15 2008 From: pfelecan at opencsw.org (Peter FELECAN) Date: Sun, 07 Dec 2008 17:05:15 +0100 Subject: [csw-maintainers] IRL meeting Message-ID: When and how we'll be informed about what was discussed and decided at the meeting? -- Peter From dam at opencsw.org Sun Dec 7 17:09:48 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 7 Dec 2008 17:09:48 +0100 Subject: [csw-maintainers] libxml2 question In-Reply-To: <1228509292-sup-5532@ntdws12.chass.utoronto.ca> References: <1228509292-sup-5532@ntdws12.chass.utoronto.ca> Message-ID: Hi Ben, Am 05.12.2008 um 21:40 schrieb Ben Walton: > I'm packaging up docbook dtds and am using xmlcatalog to add entries > to the system sgml catalog, so that they're reference-able by all > tools looking at the global catalog. It seems though, that the > libxml2-supplied xmlcatalog tool updates /etc/sgml/catalog instead of > /opt/csw/etc/sgml/catalog. I'm not sure if this is a bug or > not...should something like this look in the system /etc instead of > the CSW etc? I really don't know. From my understanding there should be only one catalog on a system, but it may be a good idea to have a special catalog for OpenCSW without intefering with the system. If you want this changed please let me know what there needs to be changed in the GAR description of libxml2. Best regards -- Dago From bwalton at opencsw.org Mon Dec 8 01:25:45 2008 From: bwalton at opencsw.org (Ben Walton) Date: Sun, 07 Dec 2008 19:25:45 -0500 Subject: [csw-maintainers] libxml2 question In-Reply-To: References: <1228509292-sup-5532@ntdws12.chass.utoronto.ca> Message-ID: <1228695055-sup-6944@ntdws12.chass.utoronto.ca> Excerpts from Dagobert Michelsen's message of Sun Dec 07 11:09:48 -0500 2008: Hi Dago, > I really don't know. From my understanding there should be only > one catalog on a system, but it may be a good idea to have a > special catalog for OpenCSW without intefering with the system. > If you want this changed please let me know what there needs > to be changed in the GAR description of libxml2. Well, I'd like to agree with this, but I think that for sanity purposes we should separate the CSW xml/sgml catalog info into our own little universe for the same reason we roll our own (sometimes duplicate) versions of libraries, etc. Solaris 10 is providing some of this stuff already (including docbook v4.1 dtds) through one of the Gnome packages, while it doesn't exist on solaris 8 (and 9?)...The dtd package I'm putting together provides the same dtd as above in addition to many other versions. None of my systems with libxml2 have anything actually in the catalog presently, so this may not be something that has been leveraged yet, which would make the change simple. Knowing this for sure would help though. If there are packages using xmlcatalog to install references to various items, then a transition becomes trickier since install/uninstall scripts from those package most likely reference paths explicitly and would therefore be broken by any change of this nature. [Comments from packagers of things that depend on libxml2 are quite welcome here, assuming others agree that we should segregate our catalog info.] I'll have a look at the results of the package from your updated GAR description for libxml2...a cursory glance looks like it should be putting the in the proper (CSW) locations. Thoughts on the above anyone? Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From ihsan at opencsw.org Mon Dec 8 08:53:47 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Mon, 08 Dec 2008 08:53:47 +0100 Subject: [csw-maintainers] IRL meeting In-Reply-To: References: Message-ID: <493CD28B.1070001@opencsw.org> Good morning, Am 7.12.2008 17:05 Uhr, Peter FELECAN schrieb: > When and how we'll be informed about what was discussed and decided at > the meeting? I've put the bylaws of the OpenCSW Association online. http://wiki.opencsw.org/open-community-software-project-bylaws PDF: http://wiki.opencsw.org/local--files/open-community-software-project-bylaws/OpenCSW_bylaws.pdf Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From ihsan at opencsw.org Mon Dec 8 09:58:52 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Mon, 08 Dec 2008 09:58:52 +0100 Subject: [csw-maintainers] mailing list archive Message-ID: <493CE1CC.1070409@opencsw.org> Good morning, Gmane is providing an alternative, searchable, mailing list archive with an NNTP interface. The public OpenCSW mailing list are there archived as well. http://dir.gmane.org/search.php?match=opencsw Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From a.cervellin at acm.org Mon Dec 8 11:34:35 2008 From: a.cervellin at acm.org (Alessio) Date: Mon, 08 Dec 2008 11:34:35 +0100 Subject: [csw-maintainers] IRL meeting In-Reply-To: <493CD28B.1070001@opencsw.org> References: <493CD28B.1070001@opencsw.org> Message-ID: <493CF83B.9020708@acm.org> Ihsan Dogan wrote: > Good morning, > > Am 7.12.2008 17:05 Uhr, Peter FELECAN schrieb: >> When and how we'll be informed about what was discussed and decided at >> the meeting? > > I've put the bylaws of the OpenCSW Association online. > > http://wiki.opencsw.org/open-community-software-project-bylaws so, who are the members of the board now? From william at wbonnet.net Mon Dec 8 11:53:05 2008 From: william at wbonnet.net (William Bonnet) Date: Mon, 08 Dec 2008 11:53:05 +0100 Subject: [csw-maintainers] IRL meeting In-Reply-To: <493CF83B.9020708@acm.org> References: <493CD28B.1070001@opencsw.org> <493CF83B.9020708@acm.org> Message-ID: <493CFC91.2000108@wbonnet.net> Hi Alessio > so, who are the members of the board now? > Phil, Ishan and Dagobert cheers, From dam at opencsw.org Mon Dec 8 12:37:32 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 8 Dec 2008 12:37:32 +0100 Subject: [csw-maintainers] Summary of IRL Meeting Message-ID: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> Fellow maintainers, the meeting in Zurich is over and the results will hopefully bring the OpenCSW project for the good of the packaging community ahead. Sorry for this summary to be a bit late but I felt the time was best used for talking while the other maintainers were present and write the summary afterwards. Participants ------------ The following persons participated (in alphabetical order): - William Bonnet - Philip Brown - Ihsan Dogan - Sebastian Kayser - Dominique Laigle - Trygve Laugst?l - Alexander Maier - Dagobert Michelsen - Othmar Wigger After lots of discussions on Saturday on what the new incorporated society should be based on the bylaws where defined. The official name now is "Open Community Software Project (OpenCSW)". The Board --------- The elected board now contitutes of Philip Brown (President), Ihsan Dogan (Cashier) and me (Dagobert Michelsen) as Actuar. Feel free to contact the board about any issues at board at opencsw.org (Ihsan will set this up ASAP) Basically the board can then open a discussion on the maintainers list and make a decision based on the results of the discussion. The decision will be posted and a rationale explaining the decision will be given. Membership ---------- The participants of the meeting are the founding members. It is legally not possible to just grab people and make them members if they have not applied for membership. So every maintainer will get an email within the next few days asking if they want to apply for membership. A simple reply with "I want to apply for membership" is enough. The board will usually accept membership and will post about all membership applications. As is stated in the bylaws there is no membership fee. There will be a publicly readble mailing list where all members can post on at members@ Accepted members will be automatically added to that list. Sidenotes --------- There have been lots of discussions during the whole time about technical issues and the community in a non-formal way. The results from these discussions will trigger some more discussions on the mailing list in the next time. The following topics have not been finalized and are subject to more discussion: - One technical summercamp per year. Trygve offered to organize the first one in Oslo in summer 2009. There may be "bug squashing day", technical discussions among other fun things. - Design of a central directory server for easier setup of more build farms - Optimized GCC builds with GCC for sparc systems (GCCfss) - A next generation packaging tool from Trygve and William - Redesign of www.opencsw.org by William - A new catalog ("unstrict/") which allows packages for only one architecture or onle one Solaris version. This will be a superset of current/ - Peters' list (<>) is generally considered a Good Thing and the issues will be worked on - A GAR package for easier package building - There have been some pictures taken. A group pictures is at Best regards -- Dago From dam at opencsw.org Mon Dec 8 16:46:00 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 8 Dec 2008 16:46:00 +0100 Subject: [csw-maintainers] Standard for package naming In-Reply-To: <20081205141036.GB98262@bolthole.com> References: <22225B82-435C-4EDA-A841-7448D7CA5E63@opencsw.org> <20081205141036.GB98262@bolthole.com> Message-ID: <5977767A-27F8-459B-BF44-416934465B87@opencsw.org> Hi Phil, Am 05.12.2008 um 15:10 schrieb Philip Brown: > On Fri, Dec 05, 2008 at 08:01:28AM +0100, Dagobert Michelsen wrote: >> Personally I like *-devel, *-rt, *_devel and *_rt, > > i agree Could you please add this to the standards page? >> don't care what is chosen, but whatever we choose the package >> names should be adjust and bugs should be filed for renaming. > > I would disagree here. renaming packages (at least the CSWxxx names) > is > ugly, becuase of depandancies, and i would prefer they NOT be renamed. > unless they havef zero dependancies. We must clean up this mess at some time, even when intermediate packages must be used in the meantime. We'll look at these one at a time. Best regards -- Dago From phil at bolthole.com Mon Dec 8 18:44:06 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 8 Dec 2008 09:44:06 -0800 Subject: [csw-maintainers] Standard for package naming In-Reply-To: <5977767A-27F8-459B-BF44-416934465B87@opencsw.org> References: <22225B82-435C-4EDA-A841-7448D7CA5E63@opencsw.org> <20081205141036.GB98262@bolthole.com> <5977767A-27F8-459B-BF44-416934465B87@opencsw.org> Message-ID: <20081208174406.GA71096@bolthole.com> On Mon, Dec 08, 2008 at 04:46:00PM +0100, Dagobert Michelsen wrote: > Hi Phil, > > Am 05.12.2008 um 15:10 schrieb Philip Brown: > > On Fri, Dec 05, 2008 at 08:01:28AM +0100, Dagobert Michelsen wrote: > >> Personally I like *-devel, *-rt, *_devel and *_rt, > > > > i agree > > Could you please add this to the standards page? Hm.. .actually, I overly agreed on one part of that. I dont think that the "-" needs be mandatory for the PKG name. I think that CSWmysql4devel CSWmysql5devel CSWoldapdevel are perfectly readable and do not have to be redone to comply with some "new standard". So I would say CSWxxxdevel CSWxxxrt CSWxxxdoc should be the standard for PKG names. if you want to use dashes, you can, but it is not mandatory. (mostly because "devel" is long enough, without making it even longer by requiring "-" on top of it) Ok? From pfelecan at opencsw.org Mon Dec 8 20:03:54 2008 From: pfelecan at opencsw.org (Peter FELECAN) Date: Mon, 08 Dec 2008 20:03:54 +0100 Subject: [csw-maintainers] Summary of IRL Meeting In-Reply-To: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> (Dagobert Michelsen's message of "Mon\, 8 Dec 2008 12\:37\:32 +0100") References: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> Message-ID: Dagobert Michelsen writes: > - There have been some pictures taken. A group pictures is at > Nice. Can somebody put names under the photos for those that didn't have the opportunity to be there? TIA -- Peter From dam at opencsw.org Tue Dec 9 00:14:02 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 9 Dec 2008 00:14:02 +0100 Subject: [csw-maintainers] Summary of IRL Meeting In-Reply-To: References: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> Message-ID: <392323F5-EF0D-4DC4-BCB2-2EAAC80979AE@opencsw.org> Hi Peter, hi Othmar, Am 08.12.2008 um 20:03 schrieb Peter FELECAN: > Dagobert Michelsen writes: >> - There have been some pictures taken. A group pictures is at >> > > Nice. Can somebody put names under the photos for those that didn't > have the opportunity to be there? TIA Othmar, could you please set these? * Picture 1: On the group picture this is (left to right): - Alexander Maier - Trygve Laugst?l - Ihsan Dogan - Sebastian Kayser - Dagobert Michelsen - William Bonnet - Philip Brown - Dominique Laigle * Picture 2: Same * Picture 3: Philip Brown * Picture 4: left: - Trygve Laugst?l - Alexander Maier - Ihsan Dogan right: - William Bonnet - Dagobert Michelsen - Philip Brown - Dominique Laigle * Picture 5: (only right side) - William Bonnet - Dagobert MIchelsen - Philip Brown - Domoniqie Laigle * Picture 6: Pizza with ham and olives * Picture 7 - Trygve Laugst?l - Ihsan Dogan - Sebastian Kayser * Picture 8 - Alexander Maier - Trygve Laugst?l - Philip Brown - Sebastian Kayser * Picture 9: Trygve Laugst?l * Picture 10: Dagobert Michelsen * Picture 11: Ihsan Dogan * Picture 12: Philip Brown * Picture 13: Dominiqie Laigle * Picture 14: The new board - Ihsan Dogan - Dagobert Michelsen - Philip Brown Best regards -- Dago From dlaigle at opencsw.org Tue Dec 9 11:50:51 2008 From: dlaigle at opencsw.org (dlaigle) Date: Tue, 09 Dec 2008 11:50:51 +0100 Subject: [csw-maintainers] KDE on build machines In-Reply-To: <392323F5-EF0D-4DC4-BCB2-2EAAC80979AE@opencsw.org> References: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> <392323F5-EF0D-4DC4-BCB2-2EAAC80979AE@opencsw.org> Message-ID: <6227ac8cb62a6524ebc5c0e3980ce24d@localhost> Gents, WMay I know what exact versions of KDE have been installed on the building machines ? As incredible as it sounds, we miss the following prototype declaration in kio/netaccess.h "static KURL mostLocalURL(const KURL& url, QWidget* window);" although the function exists in the object libkio.so! This leads to horrible hack on the source of kdesdk/cervisia in order to build, and before filling a bug at KDE I need to now more about what we have currently. Thanks - Dominique From dam at opencsw.org Tue Dec 9 11:59:16 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 9 Dec 2008 11:59:16 +0100 Subject: [csw-maintainers] KDE on build machines In-Reply-To: <6227ac8cb62a6524ebc5c0e3980ce24d@localhost> References: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> <392323F5-EF0D-4DC4-BCB2-2EAAC80979AE@opencsw.org> <6227ac8cb62a6524ebc5c0e3980ce24d@localhost> Message-ID: Hi Dominique, Am 09.12.2008 um 11:50 schrieb dlaigle: > WMay I know what exact versions of KDE have been installed on the > building > machines ? > As incredible as it sounds, we miss the following prototype > declaration in > kio/netaccess.h > "static KURL mostLocalURL(const KURL& url, QWidget* window);" > although the function exists in the object libkio.so! > > This leads to horrible hack on the source of kdesdk/cervisia in > order to > build, and before filling a bug at KDE I need to now more about what > we > have currently. Looks like this: build8s% grep kio/netaccess.h /var/sadm/install/contents /opt/csw/kde-gcc/include/kio/netaccess.h f none 0644 root bin 21021 15804 1116850553 CSWkdelibsgcc build8s% pkginfo -l CSWkdelibsgcc PKGINST: CSWkdelibsgcc NAME: kdelibs_gcc - Base set of libraries needed by KDE programs (gcc3) CATEGORY: application ARCH: sparc VERSION: 3.4.2 VENDOR: http://www.kde.org packaged for CSW by Ken Mays PSTAMP: apollo20050909214115 INSTDATE: Sep 04 2008 22:09 HOTLINE: http://www.blastwave.org/bugtrak/ EMAIL: kenmays at blastwave.org STATUS: completely installed FILES: 5577 installed pathnames 89 shared pathnames 328 directories 307 executables 3 setuid/setgid executables 112423 blocks used (approx) Do we need a newer version of KDE? Best regards -- Dago From dam at opencsw.org Tue Dec 9 12:03:41 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 9 Dec 2008 12:03:41 +0100 Subject: [csw-maintainers] Update of bzip2 and clamav Message-ID: <91F5D112-4573-440C-9A79-FD0F0C83E2E8@opencsw.org> Hi, when working together with Peter on clamav I noticed > checking for bzlib.h... yes > checking for CVE-2008-1372... bugged > configure: WARNING: ****** bzip2 libraries are affected by the > CVE-2008-1372 bug > configure: WARNING: ****** We strongly suggest you to update to > bzip2 1.0.5. > configure: WARNING: ****** Please do not report stability problems > to the ClamAV developers! which seems to result in multiple compile errors. James: Can we release 1.0.5 to current so I can upgrade it on the farm? Peter: clamav doesn't seem to compile any more because of this error. Feel free to also have a look. I'll stop here for the moment and will pick up again when we are at merge phase exclusion. Best regards -- Dago From james at opencsw.org Tue Dec 9 15:31:53 2008 From: james at opencsw.org (James Lee) Date: Tue, 09 Dec 2008 14:31:53 GMT Subject: [csw-maintainers] Update of bzip2 and clamav In-Reply-To: <91F5D112-4573-440C-9A79-FD0F0C83E2E8@opencsw.org> References: <91F5D112-4573-440C-9A79-FD0F0C83E2E8@opencsw.org> Message-ID: <20081209.14315300.1742443868@gyor.oxdrove.co.uk> On 09/12/08, 11:03:41, Dagobert Michelsen wrote regarding [csw-maintainers] Update of bzip2 and clamav: > James: Can we release 1.0.5 to current so I can upgrade it on the farm? Give me a break. I built it on Sunday and I'm currently at work. It's needs burn in and test; you could help by testing it thoroughly. James. From phil at bolthole.com Tue Dec 9 18:13:48 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 9 Dec 2008 09:13:48 -0800 Subject: [csw-maintainers] KDE on build machines In-Reply-To: References: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> <392323F5-EF0D-4DC4-BCB2-2EAAC80979AE@opencsw.org> <6227ac8cb62a6524ebc5c0e3980ce24d@localhost> Message-ID: <20081209171348.GA35059@bolthole.com> On Tue, Dec 09, 2008 at 11:59:16AM +0100, Dagobert Michelsen wrote: > > Do we need a newer version of KDE? very very badly. our version: 3.4.2 latest version: 4.1.3 ? !! From phil at bolthole.com Tue Dec 9 18:14:44 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 9 Dec 2008 09:14:44 -0800 Subject: [csw-maintainers] KDE on build machines In-Reply-To: References: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> <392323F5-EF0D-4DC4-BCB2-2EAAC80979AE@opencsw.org> <6227ac8cb62a6524ebc5c0e3980ce24d@localhost> Message-ID: <20081209171444.GB35059@bolthole.com> On Tue, Dec 09, 2008 at 11:59:16AM +0100, Dagobert Michelsen wrote: > Do we need a newer version of KDE? PS: even on the "3 series", there is 3.5.10 released aug 2008 Seems like there is somewhat of a parallel stream of v3 compared to v4 kde. From bwalton at opencsw.org Tue Dec 9 18:23:00 2008 From: bwalton at opencsw.org (Ben Walton) Date: Tue, 09 Dec 2008 12:23:00 -0500 Subject: [csw-maintainers] KDE on build machines In-Reply-To: <20081209171444.GB35059@bolthole.com> References: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> <392323F5-EF0D-4DC4-BCB2-2EAAC80979AE@opencsw.org> <6227ac8cb62a6524ebc5c0e3980ce24d@localhost> <20081209171444.GB35059@bolthole.com> Message-ID: <1228843206-sup-7285@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Tue Dec 09 12:14:44 -0500 2008: > On Tue, Dec 09, 2008 at 11:59:16AM +0100, Dagobert Michelsen wrote: > > Do we need a newer version of KDE? > > even on the "3 series", there is 3.5.10 released aug 2008 Seems like > there is somewhat of a parallel stream of v3 compared to v4 kde. I'm a GNOME user myself, but various blogs, etc that I read track the KDE progress (mostly from a Debian packaging perspective). I'd suggest that if someone wants to roll up the current version in the 4 series that the current 3.X also be offered. If memory serves, the 4 stream won't reach feature parity with 3 until 4.2. There was a lot of drastic change that went into 4 and not all apps have caught up yet (since it's still somewhat a moving target). [This may be out of date, since I haven't seen anything for a few months now...] HTH. -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From skayser at opencsw.org Tue Dec 9 20:10:02 2008 From: skayser at opencsw.org (Sebastian Kayser) Date: Tue, 09 Dec 2008 20:10:02 +0100 Subject: [csw-maintainers] Summary of IRL Meeting In-Reply-To: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> References: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> Message-ID: <493EC28A.9020807@opencsw.org> Hi Dago, thanks for the summary. In case there are any related question i hope they are addressed to the maintainers list so that everyone gets a share of insight. Dagobert Michelsen wrote: > Membership > ---------- > > The participants of the meeting are the founding members. It is > legally not possible to just grab people and make them members if > they have not applied for membership. So every maintainer will > get an email within the next few days asking if they want to > apply for membership. A simple reply with "I want to apply for > membership" is enough. The board will usually accept membership > and will post about all membership applications. > As is stated in the bylaws there is no membership fee. Maybe one could add for the uninitiated that this whole membership thing is a side effect (or essential building block) of putting OpenCSW on the legal basis of an incorporated society. The ASF [1] is a prominent example for a similar approach. The membership status eventually leads to voting rights in general meetings according to rules which have yet to be defined (by William, was it?). So even though membership might have the initial connotation of something closed it is exactly the contrary. It is the foundation to move towards an open and community based decision model (call it project democracy if you want) that not only exists in our minds, but on paper also. > There will be a publicly readble mailing list where all members > can post on at members@ > Accepted members will be automatically added to that list. And members@ will not just be duplicate of maintainers@, because people can contribute to OpenCSW without being a maintainer (think web- or postmaster for example) and issues being discussed on members@ would naturally differ also. > Sidenotes > --------- > > There have been lots of discussions during the whole time about > technical issues and the community in a non-formal way. The > results from these discussions will trigger some more discussions > on the mailing list in the next time. Seems as if the dinner on Saturday evening generated a lot of ideas. Looking forward to the discussions. > The following topics have not been finalized and are subject > to more discussion: > > - Redesign of www.opencsw.org by William What's the ETA? :) > - One technical summercamp per year. Trygve offered to organize > the first one in Oslo in summer 2009. There may be "bug > squashing day", technical discussions among other fun things. Yeah, great idea! Oslo sounds promising, although i have to admit that i had hoped to get away with cheaper dinners than the one in Zurich next time we would meet ;) Sebastian [1] http://apache.org/foundation/ [2] http://wiki.blastwave.org/ From pfelecan at opencsw.org Tue Dec 9 20:13:16 2008 From: pfelecan at opencsw.org (Peter FELECAN) Date: Tue, 09 Dec 2008 20:13:16 +0100 Subject: [csw-maintainers] Summary of IRL Meeting In-Reply-To: <392323F5-EF0D-4DC4-BCB2-2EAAC80979AE@opencsw.org> (Dagobert Michelsen's message of "Tue\, 9 Dec 2008 00\:14\:02 +0100") References: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> <392323F5-EF0D-4DC4-BCB2-2EAAC80979AE@opencsw.org> Message-ID: Dagobert Michelsen writes: > Hi Peter, hi Othmar, > > Am 08.12.2008 um 20:03 schrieb Peter FELECAN: >> Dagobert Michelsen writes: >>> - There have been some pictures taken. A group pictures is at >>> >> >> Nice. Can somebody put names under the photos for those that didn't >> have the opportunity to be there? TIA > > Othmar, could you please set these? Thank you: now it's better: to have faces on names... -- Peter From dlaigle at opencsw.org Wed Dec 10 00:16:48 2008 From: dlaigle at opencsw.org (dlaigle) Date: Wed, 10 Dec 2008 00:16:48 +0100 Subject: [csw-maintainers] KDE on build machines In-Reply-To: <20081209171444.GB35059@bolthole.com> References: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> <392323F5-EF0D-4DC4-BCB2-2EAAC80979AE@opencsw.org> <6227ac8cb62a6524ebc5c0e3980ce24d@localhost> <20081209171444.GB35059@bolthole.com> Message-ID: <8d68f6f8059736d5b6af361a44762be1@localhost> On Tue, 9 Dec 2008 09:14:44 -0800, Philip Brown wrote: > On Tue, Dec 09, 2008 at 11:59:16AM +0100, Dagobert Michelsen wrote: >> Do we need a newer version of KDE? > > PS: > > even on the "3 series", there is 3.5.10 released aug 2008 > Seems like there is somewhat of a parallel stream of v3 compared to v4 kde. Exactly! 3.5.10 is still _THE_ stable release currently. As I proposed to Dago, I took the bill for the build of kde 3.5.10 with GCC3 for the package kde-gcc and I started as of today. This will allows me to release kdevelop 3.5.3. On the other hand, regarding KDE 4, I think it is worth to have kde 4 built with Sun Studio instead (over CSWQt). But I rather let this job to any other volunteer. - Dominique > > _______________________________________________ > maintainers mailing list > maintainers at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/maintainers > From phil at bolthole.com Wed Dec 10 01:56:02 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 9 Dec 2008 16:56:02 -0800 Subject: [csw-maintainers] KDE on build machines In-Reply-To: <8d68f6f8059736d5b6af361a44762be1@localhost> References: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> <392323F5-EF0D-4DC4-BCB2-2EAAC80979AE@opencsw.org> <6227ac8cb62a6524ebc5c0e3980ce24d@localhost> <20081209171444.GB35059@bolthole.com> <8d68f6f8059736d5b6af361a44762be1@localhost> Message-ID: <20081210005602.GB80722@bolthole.com> On Wed, Dec 10, 2008 at 12:16:48AM +0100, dlaigle wrote: > 3.5.3. On the other hand, regarding KDE 4, I think it is worth to have kde > 4 built with Sun Studio instead (over CSWQt). But I rather let this job to > any other volunteer. because, there is no guarantee that it WILL build easily :-} From skayser at opencsw.org Wed Dec 10 15:09:03 2008 From: skayser at opencsw.org (Sebastian Kayser) Date: Wed, 10 Dec 2008 15:09:03 +0100 Subject: [csw-maintainers] Hudson package catalog? Message-ID: <493FCD7F.6070201@opencsw.org> Hi, just wondering: What's the status for the Hudson-built packages [1] catalog? I just put a package in Hudson, built it and noticed that the catalogs [2,3] are out of sync with the actual packages. Sebastian [1] http://mirror.opencsw.org/opencsw/hudson/ [2] http://mirror.opencsw.org/opencsw/hudson/i386/5.8/catalog [3] http://mirror.opencsw.org/opencsw/hudson/sparc/5.8/catalog From bwalton at opencsw.org Wed Dec 10 15:45:13 2008 From: bwalton at opencsw.org (Ben Walton) Date: Wed, 10 Dec 2008 09:45:13 -0500 Subject: [csw-maintainers] update to libxml2 Message-ID: <1228919673-sup-1323@ntdws12.chass.utoronto.ca> Hi All, Dago was kind enough to roll an updated libxml2 package for me that places the xml and sgml catalogs in /opt/csw/etc instead of /etc. I'm going to need this installed on the buildfarm to proceed with building another package shortly (in addition to a few other things that rely on it). Is anyone out there with packages that depend on libxml2 concerned about this change? Nobody has piped up yet...If you make use of xmlcatalog to install, remove or otherwise manipulate catalogs (which would have been registered in /etc/xml/catalog or /etc/sgml/catalog previously), then you may want to consider the impact this change could have for you... I'm a single (I think) package dependency away from being able to build a git + gitdoc package, so the sooner I can get these packages signed off, released and installed on the buildfarm, the happier I'll be. That being said, I don't want to push for a change that will negatively impact others. Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From dam at opencsw.org Wed Dec 10 16:42:45 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 10 Dec 2008 16:42:45 +0100 Subject: [csw-maintainers] update to libxml2 In-Reply-To: <1228919673-sup-1323@ntdws12.chass.utoronto.ca> References: <1228919673-sup-1323@ntdws12.chass.utoronto.ca> Message-ID: <0F5A1188-DE10-4F83-921D-B0EB6BC2AA65@opencsw.org> Hi, Am 10.12.2008 um 15:45 schrieb Ben Walton: > Is anyone out there with packages that depend on libxml2 concerned > about this change? As this is a somewhat central package please some other maintainer check if it works. We can than release it to current/. Thanks! -- Dago From dam at opencsw.org Wed Dec 10 20:39:14 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 10 Dec 2008 20:39:14 +0100 Subject: [csw-maintainers] Hudson package catalog? In-Reply-To: <493FCD7F.6070201@opencsw.org> References: <493FCD7F.6070201@opencsw.org> Message-ID: <3061F111-75DA-4E77-AD63-34C4D0D34CA1@opencsw.org> Hi Sebastian, Am 10.12.2008 um 15:09 schrieb Sebastian Kayser: > just wondering: What's the status for the Hudson-built packages [1] > catalog? I just put a package in Hudson, built it and noticed that the > catalogs [2,3] are out of sync with the actual packages. Yes. It seems that the catalog was only build once. Trygve, can you rebuild the catalog when a new package arrives? Best regards -- Dago From bwalton at opencsw.org Wed Dec 10 21:45:48 2008 From: bwalton at opencsw.org (Ben Walton) Date: Wed, 10 Dec 2008 15:45:48 -0500 Subject: [csw-maintainers] update to libxml2 In-Reply-To: <0F5A1188-DE10-4F83-921D-B0EB6BC2AA65@opencsw.org> References: <1228919673-sup-1323@ntdws12.chass.utoronto.ca> <0F5A1188-DE10-4F83-921D-B0EB6BC2AA65@opencsw.org> Message-ID: <1228941400-sup-4840@ntdws12.chass.utoronto.ca> Excerpts from Dagobert Michelsen's message of Wed Dec 10 10:42:45 -0500 2008: > Am 10.12.2008 um 15:45 schrieb Ben Walton: > > Is anyone out there with packages that depend on libxml2 concerned > > about this change? > > As this is a somewhat central package please some other > maintainer check if it works. We can than release it to > current/. I've now tried it in combination with libxslt from current/stable and it produced proper output (docbook xml -> man page). This was in combination with the (not yet released) DTD and XSL stylesheet packages I've installed locally. I'm ready to build the last package before git... -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From william at wbonnet.net Wed Dec 10 21:01:11 2008 From: william at wbonnet.net (William Bonnet) Date: Wed, 10 Dec 2008 21:01:11 +0100 Subject: [csw-maintainers] Summary of IRL Meeting In-Reply-To: References: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> <392323F5-EF0D-4DC4-BCB2-2EAAC80979AE@opencsw.org> Message-ID: <49402007.2030204@wbonnet.net> Hi It's the first evening since the meeting i come back from office before "late in the evening". I finally have time to read the list. I would like to thank you all for having been in Zurich this week end. It has been a very pleasant time. Thank you all, and thank you very much Ihsan for organization cheers W. -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.blastwave.org An OpenSolaris Community Site http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From dam at opencsw.org Wed Dec 10 22:25:17 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 10 Dec 2008 22:25:17 +0100 Subject: [csw-maintainers] GCC for Sparc Systems (GCCfss) on buildfarm Message-ID: Hi, I installed GCC for Sparc Systems 4.2.0 and 4.2.1 on build10s. Unfortunately even the oldest available version 4.0.3 is not available for Solaris 8: I mailed the cooltools team for an older version available for Solaris 8. You can access the compilers at /opt/SUNWgccfss/4.2.x/ Feedback as always welcome! Dominique? ;-) Best regards -- Dago From trygvel at opencsw.org Thu Dec 11 08:58:44 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Thu, 11 Dec 2008 08:58:44 +0100 Subject: [csw-maintainers] Hudson package catalog? In-Reply-To: <3061F111-75DA-4E77-AD63-34C4D0D34CA1@opencsw.org> References: <493FCD7F.6070201@opencsw.org> <3061F111-75DA-4E77-AD63-34C4D0D34CA1@opencsw.org> Message-ID: <4940C834.3020501@opencsw.org> Dagobert Michelsen wrote: > Hi Sebastian, > > Am 10.12.2008 um 15:09 schrieb Sebastian Kayser: >> just wondering: What's the status for the Hudson-built packages [1] >> catalog? I just put a package in Hudson, built it and noticed that the >> catalogs [2,3] are out of sync with the actual packages. > > Yes. It seems that the catalog was only build once. > Trygve, can you rebuild the catalog when a new package arrives? It should have been built once per hour by the /var/opt/csw/hudson/bin/cron-update-catalog script, not sure why it is not running. I'll add some logging. -- Trygve From dam at opencsw.org Thu Dec 11 10:49:43 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 11 Dec 2008 10:49:43 +0100 Subject: [csw-maintainers] Update of bzip2 and clamav In-Reply-To: <20081209.14315300.1742443868@gyor.oxdrove.co.uk> References: <91F5D112-4573-440C-9A79-FD0F0C83E2E8@opencsw.org> <20081209.14315300.1742443868@gyor.oxdrove.co.uk> Message-ID: Hi James, Am 09.12.2008 um 15:31 schrieb James Lee: > On 09/12/08, 11:03:41, Dagobert Michelsen wrote > regarding > [csw-maintainers] Update of bzip2 and clamav: > >> James: Can we release 1.0.5 to current so I can upgrade it on the >> farm? > > Give me a break. I built it on Sunday and I'm currently at work. > > It's needs burn in and test; you could help by testing it thoroughly. Works great and you even made 64 bit :-) For me you can push it. Best regards -- Dago From dlaigle at opencsw.org Thu Dec 11 16:57:20 2008 From: dlaigle at opencsw.org (dlaigle) Date: Thu, 11 Dec 2008 16:57:20 +0100 Subject: [csw-maintainers] GCC for Sparc Systems (GCCfss) on buildfarm In-Reply-To: References: Message-ID: <5109d8d2989b38a4a119dbdc85568fa7@localhost> Don't worry: you'll get my feedback very soon :-) On Wed, 10 Dec 2008 22:25:17 +0100, Dagobert Michelsen wrote: > Hi, > > I installed GCC for Sparc Systems 4.2.0 and 4.2.1 on build10s. > Unfortunately even the oldest available version 4.0.3 is not > available for Solaris 8: > > I mailed the cooltools team for an older version available for > Solaris 8. > > You can access the compilers at > /opt/SUNWgccfss/4.2.x/ > > Feedback as always welcome! Dominique? ;-) > > > Best regards > > -- Dago > _______________________________________________ > maintainers mailing list > maintainers at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/maintainers > From bonivart at opencsw.org Thu Dec 11 16:58:00 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Thu, 11 Dec 2008 16:58:00 +0100 Subject: [csw-maintainers] /testing clamav 0.94.2 Message-ID: <625385e30812110758x668c1fa7v78b44530f9a628b5@mail.gmail.com> This package by Alex Moore was getting quite old (0.92.1,REV=2008.02.11), especially since it's security related. I use it myself for MailScanner so I tried to build it. No package has yet challenged me like this one and poor Dagobert had to suffer from constant calls for help. :-) I wanted to do it in GAR which is being upgraded to v2 and I was very keen on using several of the new features like the easy splitting of packages. I also wanted it to use CSWcswclassutils for SMF support and configuration file handling. I could simplify the old preinstall a lot and completely remove the postinstall thanks to the use of CSWcswclassutils. The init script for clamd is also redone quite a lot. I would like help to test this one since I assume it's relatively widely used and important to a user. I have done some tests on sparc/5.9 like running clamscan, starting clamd and running clamdscan, updating virus signatures with freshclam and so on. What I haven't tested at all (except for checking with ldd) is the clamav-milter so if someone can set that up a report would be great. Also test from i386 and 5.10 (use SMF) if you can. Just install, test what you can, remove and report back to me even if everything was successful, I need to hear that too. :-) Look for clamav and libclamav here: http://buildfarm.opencsw.org/testing.html By the way, I have updated the wiki page about CSWcswclassutils to include instructions on how to use it in GAR. Take a look. -- /peter From dam at opencsw.org Thu Dec 11 17:31:47 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 11 Dec 2008 17:31:47 +0100 Subject: [csw-maintainers] OpenCSW Prefix In-Reply-To: References: <343A2AE3-DFC1-4B14-911F-67161138B3B4@opencsw.org> <4DE07271-5CBD-4022-B736-9248070EB132@opencsw.org> Message-ID: <341E7640-CCD6-400A-BBC0-96868E62AB26@opencsw.org> Hi Gary, Am 11.12.2008 um 12:27 schrieb Gary Law: > To pick up on a thread we left alone pending the meeting, what was > the decision on a new prefix for opencsw? Or was this not discussed? The topic was not discussed due to shortage of time. There are many other issues to be addressed in addition to change of prefix like full relocatibility raised from Sebastian, source packages, make-world-capability etc. If you are willing to work on a customizable prefix in GAR you are very welcome to do so. mGAR v2 makes developer-versions per package even easier. Best regards -- Dago -------------- next part -------------- An HTML attachment was scrubbed... URL: From phil at bolthole.com Thu Dec 11 19:24:38 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 11 Dec 2008 10:24:38 -0800 Subject: [csw-maintainers] pkg-get 4.0 Message-ID: <20081211182438.GA33380@bolthole.com> hi folks, A request; if you use pkg-get, would you please try out the 4.0beta version and let me know any problems with it for you? I'd LIKE to make it the "current" default. but given the major rewrite, i'm leery about doing so without some feedback. and I havent gotten any yet. http://mirror.opencsw.org/testing/pkg_get-4.0,REV=2008.11.12.beta-SunOS5.8-all-CSW.pkg From bwalton at opencsw.org Thu Dec 11 20:10:55 2008 From: bwalton at opencsw.org (Ben Walton) Date: Thu, 11 Dec 2008 14:10:55 -0500 Subject: [csw-maintainers] openssl vs certs Message-ID: <1229022639-sup-2798@ntdws12.chass.utoronto.ca> Hi All, A package I'm working on has it's source hosted on a site that is https only (fedorahosted.org). The ssl cert there is signed by equifax (as evidenced using: openssl s_client -connect fedorahosted.org:443 -showcerts). It seems that the CSW openssl package doesn't provide the required certificate chain to verify it, which is causing wget to bail out (without extra options, anyway). As I've never built openssl, I don't know if this is a build omission or simply that the required files weren't manually collected, and distributed with the package...I'll open a bug for this issue if it actually is a bug. If it's intentional, let me know. [It looks like rhel provides the equifax cert(s) with openssl and debian/ubuntu via ca-certificates.] For reference, this can be verified via: /opt/csw/bin/wget https://fedorahosted.org/xmlto/export/1/xmlto-0.0.21.tar.bz2 Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From phil at bolthole.com Thu Dec 11 20:17:21 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 11 Dec 2008 11:17:21 -0800 Subject: [csw-maintainers] openssl vs certs In-Reply-To: <1229022639-sup-2798@ntdws12.chass.utoronto.ca> References: <1229022639-sup-2798@ntdws12.chass.utoronto.ca> Message-ID: <20081211191721.GE33380@bolthole.com> On Thu, Dec 11, 2008 at 02:10:55PM -0500, Ben Walton wrote: > As I've never built openssl, I don't know if this is a build omission > or simply that the required files weren't manually collected, and > distributed with the package... Sounds like the latter to me. But also sounds like it would be a useful step for "us" to do. [I'm not the openssl maintainer, thou!] From james at opencsw.org Thu Dec 11 20:53:08 2008 From: james at opencsw.org (James Lee) Date: Thu, 11 Dec 2008 19:53:08 GMT Subject: [csw-maintainers] Update of bzip2 and clamav In-Reply-To: References: <91F5D112-4573-440C-9A79-FD0F0C83E2E8@opencsw.org> <20081209.14315300.1742443868@gyor.oxdrove.co.uk> Message-ID: <20081211.19530800.3172256164@gyor.oxdrove.co.uk> On 11/12/08, 09:49:43, Dagobert Michelsen wrote regarding Re: [csw-maintainers] Update of bzip2 and clamav: > >> James: Can we release 1.0.5 to current so I can upgrade it on the > >> farm? > > It's needs burn in and test; you could help by testing it thoroughly. > Works great and you even made 64 bit :-) For me you can push it. I failed it! by trying to compile, sorry, a missing header file. REV 2008.12.11 in testing. It has 64 bit libs which is why I built it, that and I needed 1.0.5 for clamav too. It also has some amd64 binaries so runs >10% faster on compatible machines. Bzip2 is slow and needs help. James. From yann at pleiades.fr.eu.org Thu Dec 11 21:24:27 2008 From: yann at pleiades.fr.eu.org (Yann Rouillard) Date: Thu, 11 Dec 2008 21:24:27 +0100 Subject: [csw-maintainers] openssl vs certs In-Reply-To: <20081211191721.GE33380@bolthole.com> References: <1229022639-sup-2798@ntdws12.chass.utoronto.ca> <20081211191721.GE33380@bolthole.com> Message-ID: <494176FB.3060600@pleiades.fr.eu.org> Philip Brown a ?crit : > On Thu, Dec 11, 2008 at 02:10:55PM -0500, Ben Walton wrote: >> As I've never built openssl, I don't know if this is a build omission >> or simply that the required files weren't manually collected, and >> distributed with the package... > > Sounds like the latter to me. But also sounds like it would be a useful > step for "us" to do. The certificates provided in the openssl source have been completely removed since 0.9.8h. Quoting the changelog: "The OpenSSL project does not recommend any specific CA and does not have any policy with respect to including or excluding any CA. Therefore it does not make any sense to ship an arbitrary selection of root CA certificates with the OpenSSL software." I have kept the previously provided CA certificates in the opencsw package for compatibility purpose but never checked if all standard CA were present in that set. It would make more sense to create a ca-certificates package like Debian, I will work on this. Yann From bwalton at opencsw.org Thu Dec 11 21:30:32 2008 From: bwalton at opencsw.org (Ben Walton) Date: Thu, 11 Dec 2008 15:30:32 -0500 Subject: [csw-maintainers] openssl vs certs In-Reply-To: <494176FB.3060600@pleiades.fr.eu.org> References: <1229022639-sup-2798@ntdws12.chass.utoronto.ca> <20081211191721.GE33380@bolthole.com> <494176FB.3060600@pleiades.fr.eu.org> Message-ID: <1229027374-sup-7244@ntdws12.chass.utoronto.ca> Excerpts from Yann Rouillard's message of Thu Dec 11 15:24:27 -0500 2008: Hi Yann, > I have kept the previously provided CA certificates in the opencsw > package for compatibility purpose but never checked if all > standard CA were present in that set. Ok, that makes sense. > It would make more sense to create a ca-certificates package like > Debian, I will work on this. I agree that this is the best direction to take. Thanks! -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From dam at opencsw.org Thu Dec 11 22:11:19 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 11 Dec 2008 22:11:19 +0100 Subject: [csw-maintainers] Does someone has support for Sun Studio? Message-ID: Hi, we are having at least two candidates for bugs in Sun Studio: - one regular bug - one new bug occurring in 121017-17 and 121018-18 It would be greate if there was a volunteer to open a case and track it at Sun. Best regards -- Dago BTW: I removed the buggy patches from build8s and build8x. From phil at bolthole.com Thu Dec 11 22:14:52 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 11 Dec 2008 13:14:52 -0800 Subject: [csw-maintainers] openssl vs certs In-Reply-To: <494176FB.3060600@pleiades.fr.eu.org> References: <1229022639-sup-2798@ntdws12.chass.utoronto.ca> <20081211191721.GE33380@bolthole.com> <494176FB.3060600@pleiades.fr.eu.org> Message-ID: <20081211211452.GJ33380@bolthole.com> On Thu, Dec 11, 2008 at 09:24:27PM +0100, Yann Rouillard wrote: > .... > I have kept the previously provided CA certificates in the opencsw > package for compatibility purpose but never checked if all > standard CA were present in that set. > > It would make more sense to create a ca-certificates package like > Debian, I will work on this. for historical documentation purposes, would you mention why you believe it "makes more sense" to do this? I am presuming, "because it will be easier to update certs on-demand as needed", and/or "because more than one package can make use of it, even if it doesnt technically use "openssl" (such as GNUtls) From yann at pleiades.fr.eu.org Thu Dec 11 22:31:00 2008 From: yann at pleiades.fr.eu.org (Yann Rouillard) Date: Thu, 11 Dec 2008 22:31:00 +0100 Subject: [csw-maintainers] openssl vs certs In-Reply-To: <20081211211452.GJ33380@bolthole.com> References: <1229022639-sup-2798@ntdws12.chass.utoronto.ca> <20081211191721.GE33380@bolthole.com> <494176FB.3060600@pleiades.fr.eu.org> <20081211211452.GJ33380@bolthole.com> Message-ID: <49418694.5080803@pleiades.fr.eu.org> Philip Brown a ?crit : > On Thu, Dec 11, 2008 at 09:24:27PM +0100, Yann Rouillard wrote: > for historical documentation purposes, would you mention why you believe it > "makes more sense" to do this? > > I am presuming, "because it will be easier to update certs on-demand as > needed", and/or "because more than one package can make use of it, even if > it doesnt technically use "openssl" > (such as GNUtls) And you are presuming well. Yann From yann at pleiades.fr.eu.org Thu Dec 11 22:36:16 2008 From: yann at pleiades.fr.eu.org (Yann Rouillard) Date: Thu, 11 Dec 2008 22:36:16 +0100 Subject: [csw-maintainers] openssl vs certs In-Reply-To: <1229022639-sup-2798@ntdws12.chass.utoronto.ca> References: <1229022639-sup-2798@ntdws12.chass.utoronto.ca> Message-ID: <494187D0.1050607@pleiades.fr.eu.org> Hi Ben, Until ca-certificates is here, you can do: wget http://www.geotrust.com/resources/root_certificates/certificates/Equifax_Secure_Certificate_Authority.cer -O /opt/csw/ssl/certs/equifax.pem /opt/csw/bin/c_rehash /opt/csw/ssl/certs/ to have the certificates recognized by the ssl library. Yann Ben Walton a ?crit : > Hi All, > > A package I'm working on has it's source hosted on a site that is > https only (fedorahosted.org). The ssl cert there is signed by > equifax (as evidenced using: openssl s_client -connect > fedorahosted.org:443 -showcerts). It seems that the CSW openssl > package doesn't provide the required certificate chain to verify it, > which is causing wget to bail out (without extra options, anyway). > > As I've never built openssl, I don't know if this is a build omission > or simply that the required files weren't manually collected, and > distributed with the package...I'll open a bug for this issue if it > actually is a bug. If it's intentional, let me know. [It looks like > rhel provides the equifax cert(s) with openssl and debian/ubuntu via > ca-certificates.] > > For reference, this can be verified via: > /opt/csw/bin/wget https://fedorahosted.org/xmlto/export/1/xmlto-0.0.21.tar.bz2 > > Thanks > -Ben > > > ------------------------------------------------------------------------ > > _______________________________________________ > maintainers mailing list > maintainers at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/maintainers From bonivart at opencsw.org Fri Dec 12 09:53:17 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Fri, 12 Dec 2008 09:53:17 +0100 Subject: [csw-maintainers] [svn] DBD-SQLite upstream update notification In-Reply-To: <200812112312.mBBNCHQd011211@mirror.opencsw.org> References: <200812112312.mBBNCHQd011211@mirror.opencsw.org> Message-ID: <625385e30812120053x43e700e0u72d9d897e703afbc@mail.gmail.com> On Fri, Dec 12, 2008 at 12:12 AM, Upstream Package Watch wrote: > > Hello dear DBD-SQLite maintainer, > > The upstream notification job has detected the availability of new files for DBD-SQLite. > > The following upstream file(s): > DBD-SQLite-1.14.tar.gz Here something must have gone wrong as we already have 1.14..? http://www.opencsw.org/packages/pm_dbdsqlite -- /peter From william at wbonnet.net Fri Dec 12 10:11:32 2008 From: william at wbonnet.net (William Bonnet) Date: Fri, 12 Dec 2008 10:11:32 +0100 Subject: [csw-maintainers] [svn] DBD-SQLite upstream update notification In-Reply-To: <625385e30812120053x43e700e0u72d9d897e703afbc@mail.gmail.com> References: <200812112312.mBBNCHQd011211@mirror.opencsw.org> <625385e30812120053x43e700e0u72d9d897e703afbc@mail.gmail.com> Message-ID: <49422AC4.7050606@wbonnet.net> Hi Peter >> Hello dear DBD-SQLite maintainer, >> >> The upstream notification job has detected the availability of new files for DBD-SQLite. >> >> The following upstream file(s): >> DBD-SQLite-1.14.tar.gz >> > > Here something must have gone wrong as we already have 1.14..? > > http://www.opencsw.org/packages/pm_dbdsqlite > That's right version 1.14 is in the catalog, but GAR has only version 1.13 in the Makefile. The script is running using information from GAR, not from the catalog. This package is kind of a "special" case. I was expecting to have packages newer in GAR than in the catalog (ie package not yet released). Not packages newer in the catalog than in GAR. This case means package has been added to GAR, then a newer package has been released without using GAR. Which should not happen (IMHO). Can you please update the Makefile in GAR ? Then the script will not warn you until 1.15 Thanks in advance cheers, W. From bonivart at opencsw.org Fri Dec 12 10:29:03 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Fri, 12 Dec 2008 10:29:03 +0100 Subject: [csw-maintainers] [svn] DBD-SQLite upstream update notification In-Reply-To: <49422AC4.7050606@wbonnet.net> References: <200812112312.mBBNCHQd011211@mirror.opencsw.org> <625385e30812120053x43e700e0u72d9d897e703afbc@mail.gmail.com> <49422AC4.7050606@wbonnet.net> Message-ID: <625385e30812120129l7a427ceft8cfc63fac5e238fe@mail.gmail.com> On Fri, Dec 12, 2008 at 10:11 AM, William Bonnet wrote: > That's right version 1.14 is in the catalog, but GAR has only version > 1.13 in the Makefile. The script is running using information from GAR, > not from the catalog. This package is kind of a "special" case. I was > expecting to have packages newer in GAR than in the catalog (ie package > not yet released). Not packages newer in the catalog than in GAR. This > case means package has been added to GAR, then a newer package has been > released without using GAR. Which should not happen (IMHO). Sounds reasonable. I don't remember if I was tinkering with this package in GAR or maybe someone else did but the current one is built outside of GAR, that's correct. > Can you please update the Makefile in GAR ? Then the script will not > warn you until 1.15 Will do. :-) -- /peter From ihsan at opencsw.org Fri Dec 12 10:51:58 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Fri, 12 Dec 2008 10:51:58 +0100 Subject: [csw-maintainers] KDE on build machines In-Reply-To: <20081209171444.GB35059@bolthole.com> References: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> <392323F5-EF0D-4DC4-BCB2-2EAAC80979AE@opencsw.org> <6227ac8cb62a6524ebc5c0e3980ce24d@localhost> <20081209171444.GB35059@bolthole.com> Message-ID: <4942343E.4020207@opencsw.org> Am 9.12.2008 18:14 Uhr, Philip Brown schrieb: > even on the "3 series", there is 3.5.10 released aug 2008 > Seems like there is somewhat of a parallel stream of v3 compared to v4 kde. Because the first 4.0 release was not considered as a stable release for end users. Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From ihsan at opencsw.org Fri Dec 12 10:57:56 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Fri, 12 Dec 2008 10:57:56 +0100 Subject: [csw-maintainers] /testing clamav 0.94.2 In-Reply-To: <625385e30812110758x668c1fa7v78b44530f9a628b5@mail.gmail.com> References: <625385e30812110758x668c1fa7v78b44530f9a628b5@mail.gmail.com> Message-ID: <494235A4.8070700@opencsw.org> Am 11.12.2008 16:58 Uhr, Peter Bonivart schrieb: > By the way, I have updated the wiki page about CSWcswclassutils to > include instructions on how to use it in GAR. Take a look. Dago, could you mention the cswclassutils also on http://apps.sourceforge.net/mediawiki/gar/index.php?title=Main_Page ? Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From bonivart at opencsw.org Fri Dec 12 11:08:41 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Fri, 12 Dec 2008 11:08:41 +0100 Subject: [csw-maintainers] [svn] Text-Reform upstream update notification In-Reply-To: <200812120922.mBC9Mq7l024094@mirror.opencsw.org> References: <200812120922.mBC9Mq7l024094@mirror.opencsw.org> Message-ID: <625385e30812120208o66f7b8bboa71afd1d0ab051fd@mail.gmail.com> On Fri, Dec 12, 2008 at 10:22 AM, Upstream Package Watch wrote: > > Hello dear Text-Reform maintainer, > > The upstream notification job has detected the availability of new files for Text-Reform. > > The following upstream file(s): > Text-Reform-1.11.tar.gz How about this? In gar it's 1.12.2..? -- /peter From william at wbonnet.net Fri Dec 12 11:16:56 2008 From: william at wbonnet.net (William Bonnet) Date: Fri, 12 Dec 2008 11:16:56 +0100 Subject: [csw-maintainers] [svn] DBD-SQLite upstream update notification In-Reply-To: <625385e30812120129l7a427ceft8cfc63fac5e238fe@mail.gmail.com> References: <200812112312.mBBNCHQd011211@mirror.opencsw.org> <625385e30812120053x43e700e0u72d9d897e703afbc@mail.gmail.com> <49422AC4.7050606@wbonnet.net> <625385e30812120129l7a427ceft8cfc63fac5e238fe@mail.gmail.com> Message-ID: <49423A18.1000408@wbonnet.net> Thanks :) > On Fri, Dec 12, 2008 at 10:11 AM, William Bonnet wrote: > >> That's right version 1.14 is in the catalog, but GAR has only version >> 1.13 in the Makefile. The script is running using information from GAR, >> not from the catalog. This package is kind of a "special" case. I was >> expecting to have packages newer in GAR than in the catalog (ie package >> not yet released). Not packages newer in the catalog than in GAR. This >> case means package has been added to GAR, then a newer package has been >> released without using GAR. Which should not happen (IMHO). >> > > Sounds reasonable. I don't remember if I was tinkering with this > package in GAR or maybe someone else did but the current one is built > outside of GAR, that's correct. > > >> Can you please update the Makefile in GAR ? Then the script will not >> warn you until 1.15 >> > > Will do. :-) > > From william at wbonnet.net Fri Dec 12 11:29:24 2008 From: william at wbonnet.net (William Bonnet) Date: Fri, 12 Dec 2008 11:29:24 +0100 Subject: [csw-maintainers] [svn] Text-Reform upstream update notification In-Reply-To: <625385e30812120208o66f7b8bboa71afd1d0ab051fd@mail.gmail.com> References: <200812120922.mBC9Mq7l024094@mirror.opencsw.org> <625385e30812120208o66f7b8bboa71afd1d0ab051fd@mail.gmail.com> Message-ID: <49423D04.2050406@wbonnet.net> Hi Peter > On Fri, Dec 12, 2008 at 10:22 AM, Upstream Package Watch > wrote: > >> Hello dear Text-Reform maintainer, >> >> The upstream notification job has detected the availability of new files for Text-Reform. >> >> The following upstream file(s): >> Text-Reform-1.11.tar.gz >> > > How about this? In gar it's 1.12.2..? > This one is a nasty one :) They changed the way they name the file... If you have a look to the dir you'll see Text-Reform-1.08.readme 02-Apr-2003 22:27 1.0K Text-Reform-1.08.tar.gz 02-Apr-2003 22:34 18K Text-Reform-1.10.readme 09-Apr-2003 08:49 1.0K Text-Reform-1.10.tar.gz 09-Apr-2003 08:54 20K Text-Reform-1.11.readme 07-May-2003 09:43 1.1K Text-Reform-1.11.tar.gz 07-May-2003 09:46 20K Text-Reform-v1.12.2.meta 29-Sep-2007 19:10 383 Text-Reform-v1.12.2.readme 29-Sep-2007 19:10 697 Text-Reform-v1.12.2.tar.gz 29-Sep-2007 19:12 24K They added a 'v' between the name and the version. It's not your fault, the package is up to date. I'll try to fix the regexp. But this may happen again, and there is nothing i can do about this :( cheers W. From bonivart at opencsw.org Fri Dec 12 22:43:03 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Fri, 12 Dec 2008 22:43:03 +0100 Subject: [csw-maintainers] ClamAV - to include the (obsolete) signatures or not? Message-ID: <625385e30812121343s703126b2jdb11a09be2e2de0e@mail.gmail.com> I'm packaging ClamAV (please help test it, see link below) and I'm wondering what you think about including the virus signatures. The signature database files are about 18 MB if I remember correctly and doesn't compress much so the package becomes around 20 MB. From a security point of view it's not wise to use ClamAV with the included signatures since they are becoming more obsolete for every day passing since source release (November 26th). On the other hand you can't scan at all without a signature database and must start by downloading one with the freshclam command, which is really what everyone should do anyway. Should we provide a 20 MB package fully operational which needs updating or should we provide a 2 MB package which *must* be updated? If the second alternative, is it good enough to inform the user about this via the postinstall script for example? An automated run of freshclam will not work in most cases without some simple configuration which can't be guessed by me. A third alternative would be, like many Linux dists do, to separate the database to its own package but I only see that as viable option if I would constantly update that package which would be...stupid...when there's a perfect solution provided with ClamAV for that. If we make the signature package not a required dependency to main ClamAV users will miss it and we're no better off. http://buildfarm.opencsw.org/testing.html (look for clamav and libclamav) -- /peter From phil at bolthole.com Fri Dec 12 22:49:12 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 12 Dec 2008 13:49:12 -0800 Subject: [csw-maintainers] ClamAV - to include the (obsolete) signatures or not? In-Reply-To: <625385e30812121343s703126b2jdb11a09be2e2de0e@mail.gmail.com> References: <625385e30812121343s703126b2jdb11a09be2e2de0e@mail.gmail.com> Message-ID: <20081212214911.GI94990@bolthole.com> On Fri, Dec 12, 2008 at 10:43:03PM +0100, Peter Bonivart wrote: > .... > Should we provide a 20 MB package fully operational which needs > updating or should we provide a 2 MB package which *must* be updated? > > If the second alternative, is it good enough to inform the user about > this via the postinstall script for example? An automated run of > freshclam will not work in most cases without some simple > configuration which can't be guessed by me. how about you mention some of the problems hindering an automated run, and see if people here have ideas on how to overcome them? As a first shot: if the package is virtually useless without regular updates, then seems like you would want to have some kind of "out of date" check automatically built in, to be of maximum use to our users. If you have such a thing, then perhaps you might trigger that to always get called at "first run", and then also prompt for any missing information at that time? From bonivart at opencsw.org Fri Dec 12 23:13:05 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Fri, 12 Dec 2008 23:13:05 +0100 Subject: [csw-maintainers] ClamAV - to include the (obsolete) signatures or not? In-Reply-To: <20081212214911.GI94990@bolthole.com> References: <625385e30812121343s703126b2jdb11a09be2e2de0e@mail.gmail.com> <20081212214911.GI94990@bolthole.com> Message-ID: <625385e30812121413y597fb8c1v41746f8d12a28647@mail.gmail.com> On Fri, Dec 12, 2008 at 10:49 PM, Philip Brown wrote: > how about you mention some of the problems hindering an automated run, and > see if people here have ideas on how to overcome them? It's the usual stuff with mirror, proxy and so on. In most corporate environments a run of an unconfigured freshclam would just hang. > As a first shot: > > if the package is virtually useless without regular updates, then seems > like you would want to have some kind of "out of date" check automatically > built in, to be of maximum use to our users. The software already features this, warning about obsolete signatures at every scan for example. > If you have such a thing, then perhaps you might trigger that to always get > called at "first run", and then also prompt for any missing information at > that time? See above, ClamAV will surely let you know that you're lacking signatures. -- /peter From phil at bolthole.com Sat Dec 13 01:03:09 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 12 Dec 2008 16:03:09 -0800 Subject: [csw-maintainers] libiconv Message-ID: <20081213000309.GM94990@bolthole.com> fyi: i just updated iconv. beware :-) From phil at bolthole.com Sat Dec 13 01:04:13 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 12 Dec 2008 16:04:13 -0800 Subject: [csw-maintainers] ClamAV - to include the (obsolete) signatures or not? In-Reply-To: <625385e30812121413y597fb8c1v41746f8d12a28647@mail.gmail.com> References: <625385e30812121343s703126b2jdb11a09be2e2de0e@mail.gmail.com> <20081212214911.GI94990@bolthole.com> <625385e30812121413y597fb8c1v41746f8d12a28647@mail.gmail.com> Message-ID: <20081213000413.GN94990@bolthole.com> On Fri, Dec 12, 2008 at 11:13:05PM +0100, Peter Bonivart wrote: > On Fri, Dec 12, 2008 at 10:49 PM, Philip Brown wrote: > > how about you mention some of the problems hindering an automated run, and > > see if people here have ideas on how to overcome them? > > It's the usual stuff with mirror, proxy and so on. In most corporate > environments a run of an unconfigured freshclam would just hang. well... you have a place to look for that sort of thing, though. pkg-get or pkgutil configs. From bwalton at opencsw.org Sat Dec 13 02:11:37 2008 From: bwalton at opencsw.org (Ben Walton) Date: Fri, 12 Dec 2008 20:11:37 -0500 Subject: [csw-maintainers] policy on .la files? Message-ID: <1229130661-sup-7678@ntdws12.chass.utoronto.ca> Hi All, Is there a policy (or even a strong preference) on whether or not to ship the libtool .la files with a package? Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From james at opencsw.org Sat Dec 13 11:55:42 2008 From: james at opencsw.org (James Lee) Date: Sat, 13 Dec 2008 10:55:42 GMT Subject: [csw-maintainers] ClamAV - to include the (obsolete) signatures or not? In-Reply-To: <625385e30812121343s703126b2jdb11a09be2e2de0e@mail.gmail.com> References: <625385e30812121343s703126b2jdb11a09be2e2de0e@mail.gmail.com> Message-ID: <20081213.10554200.2999473139@gyor.oxdrove.co.uk> On 12/12/08, 21:43:03, Peter Bonivart wrote regarding [csw-maintainers] ClamAV - to include the (obsolete) signatures or not?: > I'm packaging ClamAV (please help test it, see link below) and I'm > wondering what you think about including the virus signatures. The > signature database files are about 18 MB if I remember correctly and > doesn't compress much so the package becomes around 20 MB. From a > security point of view it's not wise to use ClamAV with the included > signatures since they are becoming more obsolete for every day passing > since source release (November 26th). On the other hand you can't scan > at all without a signature database and must start by downloading one > with the freshclam command, which is really what everyone should do > anyway. > Should we provide a 20 MB package fully operational which needs > updating or should we provide a 2 MB package which *must* be updated? The latter, leave them out and force the use of freshclam. Any existing users doing update should have newer "main" and "daily" files than in the package so won't want the older ones in a package. > If the second alternative, is it good enough to inform the user about > this via the postinstall script for example? An automated run of > freshclam will not work in most cases without some simple > configuration which can't be guessed by me. Why doesn't a default install work? Freshclam will download the full files if it finds none, e.g. the first time. "DatabaseMirror db.local.clamav.net" should resolve to a suitable site, prove this by running "nslookup db.local.clamav.net" and it will show a list of places local to yourself. It's possible to add to crontab with postinstall (a new challenge to cswclassutils?) but maybe freshclam in daemon mode is better anyway, (variable time, control run level, control its stop and start). > A third alternative would be, like many Linux dists do, to separate > the database to its own package but I only see that as viable option > if I would constantly update that package which would > be...stupid...when there's a perfect solution provided with ClamAV for > that. Yes stupid! The perfect solution is clamav's freshclam. James. From bonivart at opencsw.org Sat Dec 13 12:28:13 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Sat, 13 Dec 2008 12:28:13 +0100 Subject: [csw-maintainers] ClamAV - to include the (obsolete) signatures or not? In-Reply-To: <20081213.10554200.2999473139@gyor.oxdrove.co.uk> References: <625385e30812121343s703126b2jdb11a09be2e2de0e@mail.gmail.com> <20081213.10554200.2999473139@gyor.oxdrove.co.uk> Message-ID: <625385e30812130328o7b20acf6l53ad92db7bceeff@mail.gmail.com> On Sat, Dec 13, 2008 at 11:55 AM, James Lee wrote: > "DatabaseMirror db.local.clamav.net" should resolve to a suitable site, > prove this by running "nslookup db.local.clamav.net" and it will > show a list of places local to yourself. The mirror is not a showstopper, that's correct, but the proxy settings may be in many (most?) environments. Trying to find those in wgetrc, pkg-get.conf or other files doesn't feel right. As far as I know freshclam doesn't pick up proxy settings from the environment, it wants it configured in freshclam.conf. It's also quite common not to have internet access at all but to set up a freshclam proxy to connect to. > It's possible to add to crontab with postinstall (a new challenge to > cswclassutils?) but maybe freshclam in daemon mode is better anyway, > (variable time, control run level, control its stop and start). The crontab idea is really cool! I have added that to the wiki page for cswclassutils as a possible future addition. http://wiki.opencsw.org/cswclassutils It would be simple to provide a start script for freshclam in the package and let cswclassutils set it up. Maybe I should do that anyway? However, it doesn't change the fact that a Clam package without the db's does not work out of the tin as someone said to me. It doesn't even handle it gracefully according to me. If you check your version you get an incomplete message returned which may not make you suspicious of anything wrong. If you try to scan it will complain about missing signatures but break with more weird info and none about how to fix it (run freshclam in most cases). Maybe it's not worth the trouble to save 15 MB of download with todays connections, web caches and local distribution and so on? I'm all for splitting packages to reduce bloat, especially now when it's real easy in GAR v2, but in this case it probably will cause problems for some users. -- /peter From dam at opencsw.org Sat Dec 13 13:26:28 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sat, 13 Dec 2008 13:26:28 +0100 Subject: [csw-maintainers] policy on .la files? In-Reply-To: <1229130661-sup-7678@ntdws12.chass.utoronto.ca> References: <1229130661-sup-7678@ntdws12.chass.utoronto.ca> Message-ID: Hi Ben, Am 13.12.2008 um 02:11 schrieb Ben Walton: > Is there a policy (or even a strong preference) on whether or not to > ship the libtool .la files with a package? The OpenCSW standard says to exclude .la files. I just had a lively discussion with Phil wheter to change that and include .la-files again. If you have hard technical facts why to include them I would be interested to hear them. Best regards -- Dago From bwalton at opencsw.org Sat Dec 13 13:37:39 2008 From: bwalton at opencsw.org (Ben Walton) Date: Sat, 13 Dec 2008 07:37:39 -0500 Subject: [csw-maintainers] policy on .la files? In-Reply-To: References: <1229130661-sup-7678@ntdws12.chass.utoronto.ca> Message-ID: <1229171325-sup-4398@ntdws12.chass.utoronto.ca> Excerpts from Dagobert Michelsen's message of Sat Dec 13 07:26:28 -0500 2008: Hi Dago, > The OpenCSW standard says to exclude .la files. I just had > a lively discussion with Phil wheter to change that and > include .la-files again. If you have hard technical facts > why to include them I would be interested to hear them. I don't have a preference either way really. I had simply noticed that some systems (rhel, debian, csw) seemed to include more .la files than others and was curious what others thought about it. AFAIK, the only real advantage to them is that it saves libtool having to go back to 'first principles' later on...Since this is all done at the packaging step though, I don't see it as a big deal. _Some_ users might be annoyed if they build things locally against CSW libs, as they might miss having that info handy...but then again, on modern systems...? [Speaking as someone that only just recently retired some sparc station 5's from active service! ] Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From dam at opencsw.org Sat Dec 13 13:54:16 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sat, 13 Dec 2008 13:54:16 +0100 Subject: [csw-maintainers] New catalog "unstrict" Message-ID: <4F18B3FA-F0C3-41CA-A77E-9DD9E9BBF135@opencsw.org> Hi, I want to pick up the thread on a more open catalog ("unstrict/" or "open/") which is a superset of current/ where it is not necessary to provide versions for all Solaris releases or sparc/x86. Being able to migrate freely between sparc and x86 and being able to upgrade Solaris versions for current/ I consider very important. The separate catalog should make clear that this strict policy is not valid when using the other catalog. That means "unstrict" contains all packages from current, but additional ones like cvsup, opera, tme etc. Best regards -- Dago From pfelecan at opencsw.org Sat Dec 13 15:54:20 2008 From: pfelecan at opencsw.org (Peter FELECAN) Date: Sat, 13 Dec 2008 15:54:20 +0100 Subject: [csw-maintainers] Summary of IRL Meeting In-Reply-To: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> (Dagobert Michelsen's message of "Mon\, 8 Dec 2008 12\:37\:32 +0100") References: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> Message-ID: Dagobert Michelsen writes: > Membership > ---------- > > The participants of the meeting are the founding members. It is > legally not possible to just grab people and make them members if > they have not applied for membership. So every maintainer will > get an email within the next few days asking if they want to > apply for membership. A simple reply with "I want to apply for > membership" is enough. The board will usually accept membership > and will post about all membership applications. Now, that I read the bylaws and have seen the photos, I'm still waiting for the above mentioned email. Or, maybe I'm no more a maintainer? Let me know. BTW, I don't see any mention of what was decided on the many points collected for discussion at http://wiki.opencsw.org/irl-meeting -- Peter From phil at bolthole.com Sat Dec 13 16:42:06 2008 From: phil at bolthole.com (Philip Brown) Date: Sat, 13 Dec 2008 07:42:06 -0800 Subject: [csw-maintainers] ClamAV - to include the (obsolete) signatures or not? In-Reply-To: <625385e30812130328o7b20acf6l53ad92db7bceeff@mail.gmail.com> References: <625385e30812121343s703126b2jdb11a09be2e2de0e@mail.gmail.com> <20081213.10554200.2999473139@gyor.oxdrove.co.uk> <625385e30812130328o7b20acf6l53ad92db7bceeff@mail.gmail.com> Message-ID: <20081213154206.GB77030@bolthole.com> On Sat, Dec 13, 2008 at 12:28:13PM +0100, Peter Bonivart wrote: > > Maybe it's not worth the trouble to save 15 MB of download with todays > connections, web caches and local distribution and so on? well, it still would be worth it in the general case. but for a package that by definition will be obsolete within a few weeks... not so much. From dam at opencsw.org Sat Dec 13 18:08:17 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sat, 13 Dec 2008 18:08:17 +0100 Subject: [csw-maintainers] Summary of IRL Meeting In-Reply-To: References: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> Message-ID: Hi Peter, Am 13.12.2008 um 15:54 schrieb Peter FELECAN: > Now, that I read the bylaws and have seen the photos, I'm still > waiting for the above mentioned email. Fist take my apologies that the email has not beed sent out yet. For a smooth membership invitation there need to be some changes to the mailinglists and aliases. It was a real busy week for Ihsan and he just hasn't time to do so. When this is finished hopefully this weekend the email will go out. > Or, maybe I'm no more a maintainer? Let me know. Of course you are :-) > BTW, I don't see any mention of what was decided on the many points > collected for discussion at http://wiki.opencsw.org/irl-meeting There are two reasons for this: One was lack of time as we felt it was more important to focus on a unified understanding of what the association should look like. The other was that it was not intended to decide on these things as the founding members don't "just decide" and that's it - the outcoming of these things will be after a hopefully lively discussions on the members list after all of you have been invited. The goal of the meeting was not the participants to become a new ruling class, but to open up for a more democratic process focused on the needs of active maintainers. Best regards -- Dago From pfelecan at opencsw.org Sat Dec 13 15:34:11 2008 From: pfelecan at opencsw.org (Peter FELECAN) Date: Sat, 13 Dec 2008 15:34:11 +0100 Subject: [csw-maintainers] policy on .la files? In-Reply-To: (Dagobert Michelsen's message of "Sat\, 13 Dec 2008 13\:26\:28 +0100") References: <1229130661-sup-7678@ntdws12.chass.utoronto.ca> Message-ID: Dagobert Michelsen writes: > Am 13.12.2008 um 02:11 schrieb Ben Walton: >> Is there a policy (or even a strong preference) on whether or not to >> ship the libtool .la files with a package? > > The OpenCSW standard says to exclude .la files. I just had > a lively discussion with Phil wheter to change that and > include .la-files again. If you have hard technical facts > why to include them I would be interested to hear them. It helps the libtool job, consequently I think that it's a good thing to include them. -- Peter From phil at bolthole.com Sat Dec 13 19:09:44 2008 From: phil at bolthole.com (Philip Brown) Date: Sat, 13 Dec 2008 10:09:44 -0800 Subject: [csw-maintainers] policy on .la files? In-Reply-To: References: <1229130661-sup-7678@ntdws12.chass.utoronto.ca> Message-ID: <20081213180944.GA84919@bolthole.com> On Sat, Dec 13, 2008 at 03:34:11PM +0100, Peter FELECAN wrote: > > The OpenCSW standard says to exclude .la files. I just had > > a lively discussion with Phil wheter to change that and > > include .la-files again. If you have hard technical facts > > why to include them I would be interested to hear them. > > It helps the libtool job, consequently I think that it's a good thing > to include them. it doesnt really help much. and sometimes, it even gets in the way. as a comparison, debian has technically banned them, although apparently some packages still have them. To put it another way: If a libtool file actually ADDED VALUE somehow, like adding some required compiler flags in, then by all means keep it. but otherwise, they just leave a mess From pfelecan at opencsw.org Sat Dec 13 19:24:25 2008 From: pfelecan at opencsw.org (Peter FELECAN) Date: Sat, 13 Dec 2008 19:24:25 +0100 Subject: [csw-maintainers] Summary of IRL Meeting In-Reply-To: (Dagobert Michelsen's message of "Sat\, 13 Dec 2008 18\:08\:17 +0100") References: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> Message-ID: Dagobert Michelsen writes: > Am 13.12.2008 um 15:54 schrieb Peter FELECAN: >> Now, that I read the bylaws and have seen the photos, I'm still >> waiting for the above mentioned email. > > Fist take my apologies that the email has not beed sent out yet. > For a smooth membership invitation there need to be some changes > to the mailinglists and aliases. It was a real busy week for Ihsan > and he just hasn't time to do so. When this is finished hopefully > this weekend the email will go out. Fine. >> BTW, I don't see any mention of what was decided on the many points >> collected for discussion at http://wiki.opencsw.org/irl-meeting > > There are two reasons for this: One was lack of time as we > felt it was more important to focus on a unified understanding > of what the association should look like. The other was that it > was not intended to decide on these things as the founding > members don't "just decide" and that's it - the outcoming > of these things will be after a hopefully lively discussions > on the members list after all of you have been invited. > The goal of the meeting was not the participants to become > a new ruling class, but to open up for a more democratic > process focused on the needs of active maintainers. Alright. Don't lose that list. I'm eager to see how democracy works. Thank you Dago for the answers, they are appreciated. -- Peter From james at opencsw.org Sun Dec 14 10:58:01 2008 From: james at opencsw.org (James Lee) Date: Sun, 14 Dec 2008 09:58:01 GMT Subject: [csw-maintainers] ClamAV - to include the (obsolete) signatures or not? In-Reply-To: <625385e30812130328o7b20acf6l53ad92db7bceeff@mail.gmail.com> References: <625385e30812121343s703126b2jdb11a09be2e2de0e@mail.gmail.com> <20081213.10554200.2999473139@gyor.oxdrove.co.uk> <625385e30812130328o7b20acf6l53ad92db7bceeff@mail.gmail.com> Message-ID: <20081214.9580100.668625779@gyor.oxdrove.co.uk> On 13/12/08, 11:28:13, Peter Bonivart wrote regarding Re: [csw-maintainers] ClamAV - to include the (obsolete) signatures or not?: > The mirror is not a showstopper, that's correct, but the proxy > settings may be in many (most?) environments. Trying to find those in > wgetrc, pkg-get.conf or other files doesn't feel right. As far as I > know freshclam doesn't pick up proxy settings from the environment, it > wants it configured in freshclam.conf. It's also quite common not to > have internet access at all but to set up a freshclam proxy to connect > to. I've missed something here because the idea of a mail server that doesn't have access to the internet is strange to me - especially one that is looking for viruses. I would think most environments would have transparent access to the internet and those who have set up their own proxies should know how to deal with the environment that they themselves create. > > It's possible to add to crontab with postinstall (a new challenge to > > cswclassutils?) but maybe freshclam in daemon mode is better anyway, > > (variable time, control run level, control its stop and start). > The crontab idea is really cool! I have added that to the wiki page > for cswclassutils as a possible future addition. > http://wiki.opencsw.org/cswclassutils > It would be simple to provide a start script for freshclam in the > package and let cswclassutils set it up. Maybe I should do that > anyway? If would be easier to set a the fetch intervals - done via freshclam.conf option not crontab edit and makes it less regular. James. From james at opencsw.org Sun Dec 14 11:00:34 2008 From: james at opencsw.org (James Lee) Date: Sun, 14 Dec 2008 10:00:34 GMT Subject: [csw-maintainers] New catalog "unstrict" In-Reply-To: <4F18B3FA-F0C3-41CA-A77E-9DD9E9BBF135@opencsw.org> References: <4F18B3FA-F0C3-41CA-A77E-9DD9E9BBF135@opencsw.org> Message-ID: <20081214.10003400.2052822375@gyor.oxdrove.co.uk> On 13/12/08, 12:54:16, Dagobert Michelsen wrote regarding [csw-maintainers] New catalog "unstrict": > I want to pick up the thread on a more open catalog > ("unstrict/" or "open/") which is a superset of current/ > where it is not necessary to provide versions for all > Solaris releases or sparc/x86. Being able to migrate > freely between sparc and x86 and being able to upgrade > Solaris versions for current/ I consider very important. > The separate catalog should make clear that this strict > policy is not valid when using the other catalog. That > means "unstrict" contains all packages from current, but > additional ones like cvsup, opera, tme etc. "unstrict" isn't a word, I guess "lenient" is the closest although perhaps "noncompliant" is what you mean. It's a slippery slope. The deal is that to share in the efforts of others one has to make the effort to support others perhaps in areas that are of no direct need to yourself. The indirect need is that your contribution become part of a wider entity that adds weight to your own contribution and the whole. Where there is a case for a particular package we should allow asymmetry. However there has to be a valid case, not just "it didn't compile first time". Example could be a tool to analyse Solaris 10 only features (zones, ZFS, dtrace) but take care that the depends don't knock out otherwise useful packages. James. From james at opencsw.org Sun Dec 14 11:01:26 2008 From: james at opencsw.org (James Lee) Date: Sun, 14 Dec 2008 10:01:26 GMT Subject: [csw-maintainers] ClamAV - to include the (obsolete) signatures or not? In-Reply-To: <20081213154206.GB77030@bolthole.com> References: <625385e30812121343s703126b2jdb11a09be2e2de0e@mail.gmail.com> <20081213.10554200.2999473139@gyor.oxdrove.co.uk> <625385e30812130328o7b20acf6l53ad92db7bceeff@mail.gmail.com> <20081213154206.GB77030@bolthole.com> Message-ID: <20081214.10012600.1379437586@gyor.oxdrove.co.uk> On 13/12/08, 15:42:06, Philip Brown wrote regarding Re: [csw-maintainers] ClamAV - to include the (obsolete) signatures or not?: > On Sat, Dec 13, 2008 at 12:28:13PM +0100, Peter Bonivart wrote: > > > > Maybe it's not worth the trouble to save 15 MB of download with todays > > connections, web caches and local distribution and so on? > well, it still would be worth it in the general case. but for a package > that by definition will be obsolete within a few weeks... not so much. It's superseded in hours and it's obsolescence is progressive thereafter. Having an up-to-date virus database is what clamav is about. James. From william at wbonnet.net Sun Dec 14 15:21:58 2008 From: william at wbonnet.net (William Bonnet) Date: Sun, 14 Dec 2008 15:21:58 +0100 Subject: [csw-maintainers] old blastwave home dirs In-Reply-To: <49381332.1000800@cognigencorp.com> References: <49381332.1000800@cognigencorp.com> Message-ID: <49451686.1060508@wbonnet.net> Hi Darin > Do we still have access to the blastwave home directories? I'd like to > be able to get at all my old docs and crap. I am reading some old mails... :) Did you retrieved your old home dir ? cheers W. -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.blastwave.org An OpenSolaris Community Site http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From phil at bolthole.com Sun Dec 14 17:21:44 2008 From: phil at bolthole.com (Philip Brown) Date: Sun, 14 Dec 2008 08:21:44 -0800 Subject: [csw-maintainers] New catalog "unstrict" In-Reply-To: <4F18B3FA-F0C3-41CA-A77E-9DD9E9BBF135@opencsw.org> References: <4F18B3FA-F0C3-41CA-A77E-9DD9E9BBF135@opencsw.org> Message-ID: <20081214162144.GA56807@bolthole.com> On Sat, Dec 13, 2008 at 01:54:16PM +0100, Dagobert Michelsen wrote: > means "unstrict" contains all packages from current, but > additional ones like cvsup, opera, tme etc. whats the problem with cvsup? i would think that conceptually it would be relatively simple, and run on anything From dam at opencsw.org Sun Dec 14 22:20:00 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 14 Dec 2008 22:20:00 +0100 Subject: [csw-maintainers] New catalog "unstrict" In-Reply-To: <20081214162144.GA56807@bolthole.com> References: <4F18B3FA-F0C3-41CA-A77E-9DD9E9BBF135@opencsw.org> <20081214162144.GA56807@bolthole.com> Message-ID: Hi Phil, Am 14.12.2008 um 17:21 schrieb Philip Brown: > On Sat, Dec 13, 2008 at 01:54:16PM +0100, Dagobert Michelsen wrote: >> means "unstrict" contains all packages from current, but >> additional ones like cvsup, opera, tme etc. > whats the problem with cvsup? It is difficult to build and impossible to build for x86. Am 19.11.2007 um 04:45 schrieb Philip Brown: > On Sun, Nov 18, 2007 at 10:53:29PM +0100, Dagobert Michelsen wrote: >> Additionally I would like to package CVSup, which is available for >> Sparc only, as Modula-3 (ezlm3) hasn't been ported to Solaris x86 >> yet. >> As it is a pain to build a package would definitely be useful, even >> for Sparc only. >> >> Are these two allowed? > > nope. sorry.. > > try porting ezlm3 :-D > > (I am shocked and horrified that such a popular program such as > CVSup, is not more > arch-neutral?!?! /gasps ) > > erm... from cvsup.org, it appears that modula3 is for "building" it? > but not for running it? > > > > another observation: ezlm3 is only ONE implementation. but any > modula-c > implementation will do. > > you might try poking at some of the other free ones, such as listed > on: > > http://www.thefreecountry.com/compilers/modula3.shtml > > (and then maybe make packages of the one that works? :-D ) Am 14.12.2008 um 17:21 schrieb Philip Brown: > whats the problem with cvsup? > i would think that conceptually it would be relatively simple, and > run on > anything Nope. Making the x86 version requires porting the compiler to another assembly backend. Making an ezlm3 (ez = Easy, SIC!) for packaging is quite hard, making the other Modula-3 implementations compile under Solaris is almost impossible. Or I am too dumb for it ;-) However, I would like to have a cvsup package as it is useful from time to time (e. g. mirroring OpenLDAPs CVS). Best regards -- Dago From dam at opencsw.org Sun Dec 14 22:23:47 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 14 Dec 2008 22:23:47 +0100 Subject: [csw-maintainers] New catalog "unstrict" In-Reply-To: <20081214.10003400.2052822375@gyor.oxdrove.co.uk> References: <4F18B3FA-F0C3-41CA-A77E-9DD9E9BBF135@opencsw.org> <20081214.10003400.2052822375@gyor.oxdrove.co.uk> Message-ID: Hi James, Am 14.12.2008 um 11:00 schrieb James Lee: > On 13/12/08, 12:54:16, Dagobert Michelsen wrote > regarding > [csw-maintainers] New catalog "unstrict": > >> I want to pick up the thread on a more open catalog >> ("unstrict/" or "open/") which is a superset of current/ >> where it is not necessary to provide versions for all >> Solaris releases or sparc/x86. Being able to migrate >> freely between sparc and x86 and being able to upgrade >> Solaris versions for current/ I consider very important. >> The separate catalog should make clear that this strict >> policy is not valid when using the other catalog. That >> means "unstrict" contains all packages from current, but >> additional ones like cvsup, opera, tme etc. > > "unstrict" isn't a word, I guess "lenient" is the closest although > perhaps "noncompliant" is what you mean. Someone said this term is used at some Linux distribution. Trygve? William? Sorry, can't remember. > It's a slippery slope. The deal is that to share in the efforts of > others one has to make the effort to support others perhaps in areas > that are of no direct need to yourself. The indirect need is that > your contribution become part of a wider entity that adds weight to > your own contribution and the whole. > > Where there is a case for a particular package we should allow > asymmetry. However there has to be a valid case, not just "it didn't > compile first time". Example could be a tool to analyse Solaris > 10 only features (zones, ZFS, dtrace) but take care that the depends > don't knock out otherwise useful packages. We already have dtracetoolkit. How about the vendor does not make a version (like Opera Solaris 8 x86, right?) or there is no assembly backend (like for CVsup Solaris x86). Theoretically this could be written, but is a much bigger work than tweaking flags or writing a couple-of-lines patch. Best regards -- Dago From phil at bolthole.com Sun Dec 14 22:54:32 2008 From: phil at bolthole.com (Philip Brown) Date: Sun, 14 Dec 2008 13:54:32 -0800 Subject: [csw-maintainers] modula3, cvsup Message-ID: <20081214215432.GA79803@bolthole.com> I would like to point out, after digging around the web a bit, reguarding cvsup and modula3, that: 1. Module3 is a dead, dead language :-) 2.http://en.wikipedia.org/wiki/CVSup references "csup" as "a rewrite of cvsup in C" http://www.mu.org/~mux/csup.html From dam at opencsw.org Sun Dec 14 22:58:05 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 14 Dec 2008 22:58:05 +0100 Subject: [csw-maintainers] modula3, cvsup In-Reply-To: <20081214215432.GA79803@bolthole.com> References: <20081214215432.GA79803@bolthole.com> Message-ID: <529594F9-1F6C-4BD1-B82E-A4A1A80CE746@opencsw.org> Hi Phil, Am 14.12.2008 um 22:54 schrieb Philip Brown: > 1. Module3 is a dead, dead language :-) Yes, I know. > 2.http://en.wikipedia.org/wiki/CVSup > references "csup" as "a rewrite of cvsup in C" > > http://www.mu.org/~mux/csup.html opencsw# more TODO ... MISSING FEATURES: ... - ... Solaris support would also be nice at some point. I'll give it a try anyway. Best regards -- Dago From bwalton at opencsw.org Mon Dec 15 02:44:26 2008 From: bwalton at opencsw.org (Ben Walton) Date: Sun, 14 Dec 2008 20:44:26 -0500 Subject: [csw-maintainers] New catalog "unstrict" In-Reply-To: References: <4F18B3FA-F0C3-41CA-A77E-9DD9E9BBF135@opencsw.org> <20081214.10003400.2052822375@gyor.oxdrove.co.uk> Message-ID: <1229305332-sup-6142@ntdws12.chass.utoronto.ca> Excerpts from Dagobert Michelsen's message of Sun Dec 14 16:23:47 -0500 2008: > We already have dtracetoolkit. How about the vendor does not make > a version (like Opera Solaris 8 x86, right?) or there is no > assembly backend (like for CVsup Solaris x86). Theoretically this > could be written, but is a much bigger work than tweaking flags > or writing a couple-of-lines patch. Does it have to be done centrally, or would extending the tools to handle multiple sources (ala apt/yum) be a better approach. That way, anyone that wanted to could publish a catalog and users/sites could pick and choose a superset of 'strict' CSW to meet their needs at their own discretion? This would take time, of course... Just thinking out loud. -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. From phil at bolthole.com Mon Dec 15 02:46:40 2008 From: phil at bolthole.com (Philip Brown) Date: Sun, 14 Dec 2008 17:46:40 -0800 Subject: [csw-maintainers] New catalog "unstrict" In-Reply-To: <1229305332-sup-6142@ntdws12.chass.utoronto.ca> References: <4F18B3FA-F0C3-41CA-A77E-9DD9E9BBF135@opencsw.org> <20081214.10003400.2052822375@gyor.oxdrove.co.uk> <1229305332-sup-6142@ntdws12.chass.utoronto.ca> Message-ID: <20081215014640.GB7986@bolthole.com> On Sun, Dec 14, 2008 at 08:44:26PM -0500, Ben Walton wrote: > > Does it have to be done centrally, or would extending the tools to > handle multiple sources (ala apt/yum) be a better approach. having multiple arbitrary source sites for packages is a support nightmare. That's why I explicitly chose to disallow that sort of thing in pkg-get. (besides from it being a programming nightmare :-) From bwalton at opencsw.org Mon Dec 15 02:53:05 2008 From: bwalton at opencsw.org (Ben Walton) Date: Sun, 14 Dec 2008 20:53:05 -0500 Subject: [csw-maintainers] New catalog "unstrict" In-Reply-To: <20081215014640.GB7986@bolthole.com> References: <4F18B3FA-F0C3-41CA-A77E-9DD9E9BBF135@opencsw.org> <20081214.10003400.2052822375@gyor.oxdrove.co.uk> <1229305332-sup-6142@ntdws12.chass.utoronto.ca> <20081215014640.GB7986@bolthole.com> Message-ID: <1229305724-sup-3665@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Sun Dec 14 20:46:40 -0500 2008: > having multiple arbitrary source sites for packages is a support > nightmare. That's why I explicitly chose to disallow that sort of > thing in pkg-get. Warranty void when using non-csw-blessed catalogs? > (besides from it being a programming nightmare :-) Certainly more difficult! I don't know if I like it either...just an idea. Ultimately, the more software we have packaged, the better off the project is as a whole. If some things are ridiculously difficult to package for all the standard targets, we should find a way to make them available so that they're still increasing the value of csw as a whole. -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. From phil at bolthole.com Mon Dec 15 03:01:24 2008 From: phil at bolthole.com (Philip Brown) Date: Sun, 14 Dec 2008 18:01:24 -0800 Subject: [csw-maintainers] New catalog "unstrict" In-Reply-To: <1229305724-sup-3665@ntdws12.chass.utoronto.ca> References: <4F18B3FA-F0C3-41CA-A77E-9DD9E9BBF135@opencsw.org> <20081214.10003400.2052822375@gyor.oxdrove.co.uk> <1229305332-sup-6142@ntdws12.chass.utoronto.ca> <20081215014640.GB7986@bolthole.com> <1229305724-sup-3665@ntdws12.chass.utoronto.ca> Message-ID: <20081215020124.GC7986@bolthole.com> On Sun, Dec 14, 2008 at 08:53:05PM -0500, Ben Walton wrote: > Ultimately, the more software we have packaged, the better off the > project is as a whole. not always universally true. We dont need the full scope of the 100+ free editors out there, for example ;-) From bwalton at opencsw.org Mon Dec 15 03:47:11 2008 From: bwalton at opencsw.org (Ben Walton) Date: Sun, 14 Dec 2008 21:47:11 -0500 Subject: [csw-maintainers] ruby help Message-ID: <1229309027-sup-6624@ntdws12.chass.utoronto.ca> Hi All, I set out to update Ruby to 1.8.7p72 shortly after the CERT advisories in the late summer. I have an updated GAR (not v2, yet) description that builds and packages the software, but I hit a speedbump with the documentation package. It seems that rdoc (as run by the install portion of the process*) is generating different results on sparc than it does on i386 (happens on both sol8 and sol10). I fired off a request for help to the ruby-core list, but got only a small request for more clarification. After providing this, I got no more info back... So, while the software is package-able, it currently requires either a) dropping a few files in the rubydoc package or b) architecture-specific rubydoc packages. Obviously both of these options stink! Is anyone out there able and willing to take a look at this and see if I'm doing something silly or whether there is indeed something wrong with the package under solaris? Incidentally, I did discover the following tidbit that, I suspect, puts solaris in the less than cared about realm as far as the ruby devs are typically concerned: http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/18257 Thanks -Ben * The GAR description builds this slightly differently than the ./configure; make; make install routine would, but doing it the 'stock' way sees the same results. -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. From phil at bolthole.com Mon Dec 15 03:53:57 2008 From: phil at bolthole.com (Philip Brown) Date: Sun, 14 Dec 2008 18:53:57 -0800 Subject: [csw-maintainers] ruby help In-Reply-To: <1229309027-sup-6624@ntdws12.chass.utoronto.ca> References: <1229309027-sup-6624@ntdws12.chass.utoronto.ca> Message-ID: <20081215025357.GG7986@bolthole.com> On Sun, Dec 14, 2008 at 09:47:11PM -0500, Ben Walton wrote: > > Hi All, > > I set out to update Ruby to 1.8.7p72 shortly after the CERT advisories > in the late summer. I have an updated GAR (not v2, yet) description > that builds and packages the software, but I hit a speedbump with the > documentation package. It seems that rdoc (as run by the install > portion of the process*) is generating different results on sparc than > it does on i386 (happens on both sol8 and sol10). Hey Ben, Did you ever confirm whether this was just a *DOCUMENTATION* difference, or whether the actual functionality was different, between sparc and x86? I dont remember you replying on that. From bwalton at opencsw.org Mon Dec 15 04:10:42 2008 From: bwalton at opencsw.org (Ben Walton) Date: Sun, 14 Dec 2008 22:10:42 -0500 Subject: [csw-maintainers] ruby help In-Reply-To: <20081215025357.GG7986@bolthole.com> References: <1229309027-sup-6624@ntdws12.chass.utoronto.ca> <20081215025357.GG7986@bolthole.com> Message-ID: <1229310317-sup-4789@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Sun Dec 14 21:53:57 -0500 2008: > Did you ever confirm whether this was just a *DOCUMENTATION* difference, or > whether the actual functionality was different, between sparc and x86? > I dont remember you replying on that. Well, as far as I've determined, the actual ruby package (and tcl/tk, but I don't play with that) is the same. The documentation differences are in extra files generated by rdoc from the source files (which would indicate extra/different info collected/collated). So supposedly, the input is identical, but the output differs. I've run a diff across the files generated on both architectures to verify that the files installed (where not binary) are identical. As best as I can tell, the _behaviour_ of rdoc differs on the two platforms, which to me indicates some odd little bug somewhere deep in the guts of it all (maybe in the rb_string or rb_hash somewhere?)... -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From phil at bolthole.com Mon Dec 15 04:17:25 2008 From: phil at bolthole.com (Philip Brown) Date: Sun, 14 Dec 2008 19:17:25 -0800 Subject: [csw-maintainers] ruby help In-Reply-To: <1229310317-sup-4789@ntdws12.chass.utoronto.ca> References: <1229309027-sup-6624@ntdws12.chass.utoronto.ca> <20081215025357.GG7986@bolthole.com> <1229310317-sup-4789@ntdws12.chass.utoronto.ca> Message-ID: <20081215031724.GA59357@bolthole.com> On Sun, Dec 14, 2008 at 10:10:42PM -0500, Ben Walton wrote: > Well, as far as I've determined, the actual ruby package (and tcl/tk, > but I don't play with that) is the same. The documentation > differences are in extra files generated by rdoc from the source files > (which would indicate extra/different info collected/collated). So > supposedly, the input is identical, but the output differs. > > I've run a diff across the files generated on both architectures to > verify that the files installed (where not binary) are identical. As > best as I can tell, the _behaviour_ of rdoc differs on the two > platforms, which to me indicates some odd little bug somewhere deep in > the guts of it all (maybe in the rb_string or rb_hash somewhere?)... oh. well, in that case, I'd say that it's fine to release, with a bug filed "oh by the way the documentation is a bit off, in these areas, we dont know why..." From phil at bolthole.com Mon Dec 15 04:26:06 2008 From: phil at bolthole.com (Philip Brown) Date: Sun, 14 Dec 2008 19:26:06 -0800 Subject: [csw-maintainers] ruby help In-Reply-To: <20081215031724.GA59357@bolthole.com> References: <1229309027-sup-6624@ntdws12.chass.utoronto.ca> <20081215025357.GG7986@bolthole.com> <1229310317-sup-4789@ntdws12.chass.utoronto.ca> <20081215031724.GA59357@bolthole.com> Message-ID: <20081215032606.GC59357@bolthole.com> On Sun, Dec 14, 2008 at 07:17:25PM -0800, Philip Brown wrote: > On Sun, Dec 14, 2008 at 10:10:42PM -0500, Ben Walton wrote: > > Well, as far as I've determined, the actual ruby package (and tcl/tk, > > but I don't play with that) is the same. The documentation > > differences are in extra files generated by rdoc from the source files > > (which would indicate extra/different info collected/collated). So > > supposedly, the input is identical, but the output differs. > > > > I've run a diff across the files generated on both architectures to > > verify that the files installed (where not binary) are identical. As > > best as I can tell, the _behaviour_ of rdoc differs on the two > > platforms, which to me indicates some odd little bug somewhere deep in > > the guts of it all (maybe in the rb_string or rb_hash somewhere?)... > > oh. > well, in that case, I'd say that it's fine to release, with a bug filed "oh > by the way the documentation is a bit off, in these areas, we dont > know why..." Hmm.. actually, the analysis above is a bit lacking. I think the more rigourous thing to do would be for you to explicitly mention some of the documentation differences/lackings, and then for someone who knows ruby, to explicitly run a test, "yes, these functions work ok on both platforms, even though they may not be documented on one of them". yes? From bwalton at opencsw.org Mon Dec 15 04:52:23 2008 From: bwalton at opencsw.org (Ben Walton) Date: Sun, 14 Dec 2008 22:52:23 -0500 Subject: [csw-maintainers] ruby help In-Reply-To: <20081215032606.GC59357@bolthole.com> References: <1229309027-sup-6624@ntdws12.chass.utoronto.ca> <20081215025357.GG7986@bolthole.com> <1229310317-sup-4789@ntdws12.chass.utoronto.ca> <20081215031724.GA59357@bolthole.com> <20081215032606.GC59357@bolthole.com> Message-ID: <1229312963-sup-1798@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Sun Dec 14 22:26:06 -0500 2008: > I think the more rigourous thing to do would be for you to explicitly > mention some of the documentation differences/lackings, and then for > someone who knows ruby, to explicitly run a test, "yes, these functions > work ok on both platforms, even though they may not be documented on one > of them". `make test` was identical on both platforms...not that it would test each and every possible function. This is the extra file generated when running rdoc almost identically to the way intended for a non-packaging run: $ diff i386.txt sparc.txt 1774d1773 < ./IRB/Context/_set_last_value-i.yaml [relative to share/doc/ruby...with a file list corrected for i386 vs sparc in the .so directory.] The results are similar when running it over the installed files, although with (if memory serves) about 4 files different. I'll dig through old mail to find that list (or regenerate the result). They're all in odd little corners though... -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From dam at opencsw.org Mon Dec 15 08:50:29 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 15 Dec 2008 08:50:29 +0100 Subject: [csw-maintainers] New catalog "unstrict" In-Reply-To: <20081215020124.GC7986@bolthole.com> References: <4F18B3FA-F0C3-41CA-A77E-9DD9E9BBF135@opencsw.org> <20081214.10003400.2052822375@gyor.oxdrove.co.uk> <1229305332-sup-6142@ntdws12.chass.utoronto.ca> <20081215014640.GB7986@bolthole.com> <1229305724-sup-3665@ntdws12.chass.utoronto.ca> <20081215020124.GC7986@bolthole.com> Message-ID: Hi, Am 15.12.2008 um 03:01 schrieb Philip Brown: > On Sun, Dec 14, 2008 at 08:53:05PM -0500, Ben Walton wrote: >> Ultimately, the more software we have packaged, the better off the >> project is as a whole. > > not always universally true. > We dont need the full scope of the 100+ free editors out there, for > example > ;-) So you would say having 10 editors is better than having 20? (All well maintained of course). But this is a theoretical example as we are not talking about hundred similar editors. We are talking about opera, maybe CVSup, maybe TME, maybe others. Best regards -- Dago From bonivart at opencsw.org Mon Dec 15 09:37:06 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Mon, 15 Dec 2008 09:37:06 +0100 Subject: [csw-maintainers] New catalog "unstrict" In-Reply-To: <1229305332-sup-6142@ntdws12.chass.utoronto.ca> References: <4F18B3FA-F0C3-41CA-A77E-9DD9E9BBF135@opencsw.org> <20081214.10003400.2052822375@gyor.oxdrove.co.uk> <1229305332-sup-6142@ntdws12.chass.utoronto.ca> Message-ID: <625385e30812150037l5a4b132ax32b03e90eb1ab552@mail.gmail.com> On Mon, Dec 15, 2008 at 2:44 AM, Ben Walton wrote: > Does it have to be done centrally, or would extending the tools to > handle multiple sources (ala apt/yum) be a better approach. That way, > anyone that wanted to could publish a catalog and users/sites could > pick and choose a superset of 'strict' CSW to meet their needs at > their own discretion? Pkgutil already contains all tools necessary to do that. You can create your own catalog for your own packages and use it in combination with an official mirror. http://pkgutil.wikidot.com/use-with-examples#toc6 -- /peter From phil at bolthole.com Mon Dec 15 15:17:16 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 15 Dec 2008 06:17:16 -0800 Subject: [csw-maintainers] New catalog "unstrict" In-Reply-To: References: <4F18B3FA-F0C3-41CA-A77E-9DD9E9BBF135@opencsw.org> <20081214.10003400.2052822375@gyor.oxdrove.co.uk> <1229305332-sup-6142@ntdws12.chass.utoronto.ca> <20081215014640.GB7986@bolthole.com> <1229305724-sup-3665@ntdws12.chass.utoronto.ca> <20081215020124.GC7986@bolthole.com> Message-ID: <20081215141716.GF37716@bolthole.com> On Mon, Dec 15, 2008 at 08:50:29AM +0100, Dagobert Michelsen wrote: > Hi, > > Am 15.12.2008 um 03:01 schrieb Philip Brown: > > not always universally true. > > We dont need the full scope of the 100+ free editors out there, for > > example > > ;-) > > So you would say having 10 editors is better than having 20? if it's "the best 10", then yes! > But this is a theoretical > example as we are not talking about hundred similar editors. > We are talking about opera, maybe CVSup, maybe TME, maybe others. opera, we might make an exception for. cvsup is a mess. no idea what tme is. From bonivart at opencsw.org Mon Dec 15 17:45:05 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Mon, 15 Dec 2008 17:45:05 +0100 Subject: [csw-maintainers] /testing pm_libwww, pm_modload and pm_modloadcond Message-ID: <625385e30812150845p3afd72aeoaebff322093e8fa7@mail.gmail.com> I have updated pm_libwww and pm_modloadcond because the upstream notification service told me to. :-) While updating pm_modloadcond it complained that pm_modload was only 0.10 while 0.11 was required so I updated it (one of Cory's packages) to the latest 0.12. Please test if you can. http://mirror.csw.baltic-online.de/testing/ -- /peter From phil at bolthole.com Mon Dec 15 18:05:29 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 15 Dec 2008 09:05:29 -0800 Subject: [csw-maintainers] /testing pm_libwww, pm_modload and pm_modloadcond In-Reply-To: <625385e30812150845p3afd72aeoaebff322093e8fa7@mail.gmail.com> References: <625385e30812150845p3afd72aeoaebff322093e8fa7@mail.gmail.com> Message-ID: <20081215170529.GE94217@bolthole.com> On Mon, Dec 15, 2008 at 05:45:05PM +0100, Peter Bonivart wrote: > I have updated pm_libwww and pm_modloadcond because the upstream > notification service told me to. :-) While updating pm_modloadcond it > complained that pm_modload was only 0.10 while 0.11 was required so I > updated it (one of Cory's packages) to the latest 0.12. > > Please test if you can. > > http://mirror.csw.baltic-online.de/testing/ http://mirror.opencsw.org/testing/ ? From william at wbonnet.net Mon Dec 15 20:51:01 2008 From: william at wbonnet.net (William Bonnet) Date: Mon, 15 Dec 2008 20:51:01 +0100 Subject: [csw-maintainers] /testing pm_libwww, pm_modload and pm_modloadcond In-Reply-To: <625385e30812150845p3afd72aeoaebff322093e8fa7@mail.gmail.com> References: <625385e30812150845p3afd72aeoaebff322093e8fa7@mail.gmail.com> Message-ID: <4946B525.9090407@wbonnet.net> Hi Peter > I have updated pm_libwww and pm_modloadcond because the upstream > notification service told me to. :-) Yeah ! it works :) Thanks Peter -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.blastwave.org An OpenSolaris Community Site http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From dam at opencsw.org Mon Dec 15 22:07:52 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 15 Dec 2008 22:07:52 +0100 Subject: [csw-maintainers] Invitation for OpenCSW membership References: <2AC8BBA4-1E45-440E-B064-E6C4929F8511@opencsw.org> Message-ID: Dear maintainer, on the 6th of December the Open Community Software (OpenCSW) Association was founded in Effretikon, Zurich to continue the packaging efforts already in progress. Unfortunately, it is legally not possible to automatically make all existing maintainers to members. We already know that you can maintain packages, and we wish you to continue doing so. At this time, it is neccessary to just have the formality of each person officially saying 'yes I wish to be a maintainer/member of the new OpenCSW association' The membership is not associated with any fees. You can read the bylaws at and An informal reply for application of membership is sufficient. Kind regards -- Dagobert Michelsen (secretary of the board) From wbonnet at opencsw.org Mon Dec 15 22:54:58 2008 From: wbonnet at opencsw.org (William Bonnet) Date: Mon, 15 Dec 2008 22:54:58 +0100 Subject: [csw-maintainers] Invitation for OpenCSW membership In-Reply-To: References: <2AC8BBA4-1E45-440E-B064-E6C4929F8511@opencsw.org> Message-ID: <4946D232.1000506@opencsw.org> Hi I do apply for membership cheers W. Dagobert Michelsen wrote: > Dear maintainer, > > on the 6th of December the Open Community Software (OpenCSW) > Association was founded in Effretikon, Zurich to continue the > packaging efforts already in progress. Unfortunately, it is > legally not possible to automatically make all existing > maintainers to members. > > We already know that you can maintain packages, and we wish > you to continue doing so. At this time, it is neccessary to > just have the formality of each person officially saying 'yes > I wish to be a maintainer/member of the new OpenCSW association' > The membership is not associated with any fees. You can read > the bylaws at > > and > > > > An informal reply for application of membership is sufficient. > > > Kind regards > > -- Dagobert Michelsen > (secretary of the board) > > > > _______________________________________________ > maintainers mailing list > maintainers at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/maintainers > > > -- William Bonnet http://www.wbonnet.net http://www.opencsw.org Community SoftWare for Solaris From ihsan at opencsw.org Mon Dec 15 22:57:30 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Mon, 15 Dec 2008 22:57:30 +0100 Subject: [csw-maintainers] Invitation for OpenCSW membership In-Reply-To: <4946D232.1000506@opencsw.org> References: <2AC8BBA4-1E45-440E-B064-E6C4929F8511@opencsw.org> <4946D232.1000506@opencsw.org> Message-ID: <4946D2CA.5030407@opencsw.org> Am 15.12.2008 22:54 Uhr, William Bonnet schrieb: > I do apply for membership You have been one of the founders, so you are already a member. :-) Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From william at wbonnet.net Mon Dec 15 23:07:29 2008 From: william at wbonnet.net (William Bonnet) Date: Mon, 15 Dec 2008 23:07:29 +0100 Subject: [csw-maintainers] Invitation for OpenCSW membership In-Reply-To: <4946D2CA.5030407@opencsw.org> References: <2AC8BBA4-1E45-440E-B064-E6C4929F8511@opencsw.org> <4946D232.1000506@opencsw.org> <4946D2CA.5030407@opencsw.org> Message-ID: <4946D521.5050104@wbonnet.net> Ihsan Dogan wrote: > Am 15.12.2008 22:54 Uhr, William Bonnet schrieb: > > >> I do apply for membership >> > > You have been one of the founders, so you are already a member. :-) > Yes but i was in the list of "named" people in the To field, not just included in the list. So i answered just in case ;) cheers -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.blastwave.org An OpenSolaris Community Site http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From trygvel at opencsw.org Tue Dec 16 16:05:06 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Tue, 16 Dec 2008 16:05:06 +0100 Subject: [csw-maintainers] IRC Message-ID: <4947C3A2.1030707@opencsw.org> Hello A few of us maintainers are regularly hanging out on IRC chatting on CSW, Solaris, life and everything else. Feel free to join us on freenode[1], the channel name is (drumroll...) #opencsw. OpenCSW has more than one useful IRC client: xchat [2] and irssi [3]. [1]: http://freenode.net/ [2]: http://opencsw.org/packages/xchat [3]: http://opencsw.org/packages/irssi -- Trygve From bwalton at opencsw.org Tue Dec 16 22:28:49 2008 From: bwalton at opencsw.org (Ben Walton) Date: Tue, 16 Dec 2008 16:28:49 -0500 Subject: [csw-maintainers] build requirements Message-ID: <1229462603-sup-6135@ntdws12.chass.utoronto.ca> Hi All, I now have a gar description for git that builds it but am seeing tests fail. So far, all failures are related to an implicit assumption that sed == gnu sed. Modifying the test files to call gsed seems to get things going. So, I have a few options: 1. Create a patch per 'bad' assumption (where bad == 'bad for me because it makes more work') 2. Add some autoconf magic, and alter the test harness to include the file generated by configure, thus allowing for a user specifiable $(sed) program. Submit this upstream. 3. Use PREREQUISITE_PKGS += CSWgnulinks and prepend /opt/csw/gnu to the GARPATH. I have my own opinion on which is the best going forward, but am curious as to what others think? Thoughts? Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From phil at bolthole.com Tue Dec 16 23:38:01 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 16 Dec 2008 14:38:01 -0800 Subject: [csw-maintainers] build requirements In-Reply-To: <1229462603-sup-6135@ntdws12.chass.utoronto.ca> References: <1229462603-sup-6135@ntdws12.chass.utoronto.ca> Message-ID: <20081216223801.GI5042@bolthole.com> On Tue, Dec 16, 2008 at 04:28:49PM -0500, Ben Walton wrote: > Hi All, > > I now have a gar description for git that builds it but am seeing > tests fail. So far, all failures are related to an implicit > assumption that sed == gnu sed. Modifying the test files to call gsed > seems to get things going. So, I have a few options: > > 1. Create a patch per 'bad' assumption (where bad == 'bad for me > because it makes more work') > 2. Add some autoconf magic, and alter the test harness to include the > file generated by configure, thus allowing for a user specifiable > $(sed) program. Submit this upstream. > 3. Use PREREQUISITE_PKGS += CSWgnulinks and prepend /opt/csw/gnu to > the GARPATH. > > I have my own opinion on which is the best going forward, but am > curious as to what others think? in this specific case... having looked at the configure file in question... i think it may be simplest and cleanest to go with option #3 for this. From bwalton at opencsw.org Wed Dec 17 01:37:24 2008 From: bwalton at opencsw.org (Ben Walton) Date: Tue, 16 Dec 2008 19:37:24 -0500 Subject: [csw-maintainers] build requirements In-Reply-To: <20081216223801.GI5042@bolthole.com> References: <1229462603-sup-6135@ntdws12.chass.utoronto.ca> <20081216223801.GI5042@bolthole.com> Message-ID: <1229474171-sup-6652@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Tue Dec 16 17:38:01 -0500 2008: > > 3. Use PREREQUISITE_PKGS += CSWgnulinks and prepend /opt/csw/gnu to > > the GARPATH. > > in this specific case... having looked at the configure file in question... > i think it may be simplest and cleanest to go with option #3 for this. This is my thinking also, as it is better insulation against future gnuisms, and with a package like this, they're bound to occur. Just wanted to spot check the logic. -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From trygvel at opencsw.org Wed Dec 17 01:51:58 2008 From: trygvel at opencsw.org (=?UTF-8?B?VHJ5Z3ZlIExhdWdzdMO4bA==?=) Date: Wed, 17 Dec 2008 01:51:58 +0100 Subject: [csw-maintainers] build requirements In-Reply-To: <1229462603-sup-6135@ntdws12.chass.utoronto.ca> References: <1229462603-sup-6135@ntdws12.chass.utoronto.ca> Message-ID: <49484D2E.2010908@opencsw.org> Ben Walton wrote: > Hi All, > > I now have a gar description for git that builds it but am seeing > tests fail. So far, all failures are related to an implicit > assumption that sed == gnu sed. Modifying the test files to call gsed > seems to get things going. So, I have a few options: > > 1. Create a patch per 'bad' assumption (where bad == 'bad for me > because it makes more work') > 2. Add some autoconf magic, and alter the test harness to include the > file generated by configure, thus allowing for a user specifiable > $(sed) program. Submit this upstream. > 3. Use PREREQUISITE_PKGS += CSWgnulinks and prepend /opt/csw/gnu to > the GARPATH. > > I have my own opinion on which is the best going forward, but am > curious as to what others think? Do me it sounds like do 1) first to get the package out and then work on 2) if git is a long-term useful package that we would like to release often to lower our maintenance cost. I assume that 3) would lead to requiring me having /opt/csw/gnu first in my path when using git and that is not going to happen. -- Trygve From bwalton at opencsw.org Wed Dec 17 01:57:29 2008 From: bwalton at opencsw.org (Ben Walton) Date: Tue, 16 Dec 2008 19:57:29 -0500 Subject: [csw-maintainers] build requirements In-Reply-To: <49484D2E.2010908@opencsw.org> References: <1229462603-sup-6135@ntdws12.chass.utoronto.ca> <49484D2E.2010908@opencsw.org> Message-ID: <1229475200-sup-6721@ntdws12.chass.utoronto.ca> Excerpts from Trygve Laugst?l's message of Tue Dec 16 19:51:58 -0500 2008: > I assume that 3) would lead to requiring me having /opt/csw/gnu first in > my path when using git and that is not going to happen. As far as I've seen at this point, it's simply the test scripts that are breaking without gnu sed. As this shouldn't impact the runtime requirements, I don't think there much worry of a permanent dependence on gnulinks. Option #2 seems like the more technically 'correct' thing to do until you consider that the primary development environment for git is a completely gnu userland. At some point, a gnu-ism would creep in again requiring more work on our part. Going with gnulinks seems like it's easier all around. If it ends up impacting dependencies, then I'll reconsider. I appreciate the feedback though! :) Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From trygvel at opencsw.org Wed Dec 17 02:13:54 2008 From: trygvel at opencsw.org (=?UTF-8?B?VHJ5Z3ZlIExhdWdzdMO4bA==?=) Date: Wed, 17 Dec 2008 02:13:54 +0100 Subject: [csw-maintainers] build requirements In-Reply-To: <1229475200-sup-6721@ntdws12.chass.utoronto.ca> References: <1229462603-sup-6135@ntdws12.chass.utoronto.ca> <49484D2E.2010908@opencsw.org> <1229475200-sup-6721@ntdws12.chass.utoronto.ca> Message-ID: <49485252.9010307@opencsw.org> Ben Walton wrote: > Excerpts from Trygve Laugst?l's message of Tue Dec 16 19:51:58 -0500 2008: >> I assume that 3) would lead to requiring me having /opt/csw/gnu first in >> my path when using git and that is not going to happen. > > As far as I've seen at this point, it's simply the test scripts that > are breaking without gnu sed. As this shouldn't impact the runtime > requirements, I don't think there much worry of a permanent dependence > on gnulinks. Then both 1) and 3) would be acceptable to me as they would both work for anyone trying to pick up the package at a later point. > Option #2 seems like the more technically 'correct' thing to do until > you consider that the primary development environment for git is a > completely gnu userland. At some point, a gnu-ism would creep in > again requiring more work on our part. Going with gnulinks seems like > it's easier all around. If it ends up impacting dependencies, then > I'll reconsider. That is a fair point and and I would say that it is up to you try to minimize the pain of maintaining a downstream build vs the paint of getting git work in a non-gnu environment. > I appreciate the feedback though! :) -- Trygve From bonivart at opencsw.org Wed Dec 17 18:15:18 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Wed, 17 Dec 2008 18:15:18 +0100 Subject: [csw-maintainers] /testing clamav 0.94.2 In-Reply-To: <625385e30812110758x668c1fa7v78b44530f9a628b5@mail.gmail.com> References: <625385e30812110758x668c1fa7v78b44530f9a628b5@mail.gmail.com> Message-ID: <625385e30812170915v413a634j8704d00d158a101a@mail.gmail.com> Sorry for top-posting. I have now tested the i386 packages also through VirtualBox (love it!) and it installs properly, can be managed via SMF and I can update the signatures and scan files. Everything I tested on sparc I can do on i386. I'm happy with it, if someone has any problems with it, please inform me quickly because I will drop it off for release tomorrow. /peter On Thu, Dec 11, 2008 at 4:58 PM, Peter Bonivart wrote: > This package by Alex Moore was getting quite old > (0.92.1,REV=2008.02.11), especially since it's security related. I use > it myself for MailScanner so I tried to build it. No package has yet > challenged me like this one and poor Dagobert had to suffer from > constant calls for help. :-) > > I wanted to do it in GAR which is being upgraded to v2 and I was very > keen on using several of the new features like the easy splitting of > packages. I also wanted it to use CSWcswclassutils for SMF support and > configuration file handling. I could simplify the old preinstall a lot > and completely remove the postinstall thanks to the use of > CSWcswclassutils. The init script for clamd is also redone quite a > lot. > > I would like help to test this one since I assume it's relatively > widely used and important to a user. I have done some tests on > sparc/5.9 like running clamscan, starting clamd and running clamdscan, > updating virus signatures with freshclam and so on. What I haven't > tested at all (except for checking with ldd) is the clamav-milter so > if someone can set that up a report would be great. Also test from > i386 and 5.10 (use SMF) if you can. Just install, test what you can, > remove and report back to me even if everything was successful, I need > to hear that too. :-) > > Look for clamav and libclamav here: http://buildfarm.opencsw.org/testing.html > > By the way, I have updated the wiki page about CSWcswclassutils to > include instructions on how to use it in GAR. Take a look. > > -- > /peter > -- /peter From bonivart at opencsw.org Wed Dec 17 18:41:49 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Wed, 17 Dec 2008 18:41:49 +0100 Subject: [csw-maintainers] /testing BIND 9.5.0-P2 Message-ID: <625385e30812170941l5c391483y3a98981cc160a73c@mail.gmail.com> I have built the latest BIND complete with SMF support via cswclassutils. I have also used GAR v2 to easily split the package into smaller parts. All this was requested by users but it was hard work before tools like cswclassutils and GAR v2 made it easy. BIND is now split like this: * bind - top level package containing server bits and docs * libbind - shared libs that all other bind packages need * bind_utils - the user binaries (dig, host, ?) * bind_devel - the stuff most people don't use :-) If you install bind you will get bind, libbind and bind_utils. If you install libbind you will just get libbind (and it's other deps of course). If you install bind_utils you will get bind_utils and libbind. Bind_devel will pull in all other bind packages. I have done some tests on i386/5.10 with SMF and it works as expected. Would be very bad if it was broken in any way though so please help test it and report back whether it works or not. -- /peter From dam at opencsw.org Wed Dec 17 20:06:52 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 17 Dec 2008 20:06:52 +0100 Subject: [csw-maintainers] build requirements In-Reply-To: <1229462603-sup-6135@ntdws12.chass.utoronto.ca> References: <1229462603-sup-6135@ntdws12.chass.utoronto.ca> Message-ID: <32FB4143-8534-4B1A-A071-30386F936947@opencsw.org> Hi Ben, Am 16.12.2008 um 22:28 schrieb Ben Walton: > I now have a gar description for git that builds it but am seeing > tests fail. So far, all failures are related to an implicit > assumption that sed == gnu sed. Modifying the test files to call gsed > seems to get things going. So, I have a few options: > > 1. Create a patch per 'bad' assumption (where bad == 'bad for me > because it makes more work') > 2. Add some autoconf magic, and alter the test harness to include the > file generated by configure, thus allowing for a user specifiable > $(sed) program. Submit this upstream. > 3. Use PREREQUISITE_PKGS += CSWgnulinks and prepend /opt/csw/gnu to > the GARPATH. The absolute best thing would be to check in configure if sed has the appropriate features and search through path for all sed or gsed. If it is only for tests I'd go with 3. Best regards -- Dago From dam at opencsw.org Wed Dec 17 20:35:10 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 17 Dec 2008 20:35:10 +0100 Subject: [csw-maintainers] Vacation from 20.12. to 27.12. Message-ID: <7D9305DF-8BF3-41C0-95B3-E99C9CE9D0CF@opencsw.org> Fellow maintainers, I will be away for some quality time with the family from 20. December to 27. December and there will only be a very limited internet connectivity available (if at all...). The bo- and go-buildfarms are co- administered by Ben Walton, so there is still someone available if anyone needs to install a package. Just make sure to mail to buildfarm at lists.opencsw.org instead of me ;-) Best regards and a merry christmas -- Dago From ihsan at opencsw.org Wed Dec 17 21:02:28 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Wed, 17 Dec 2008 21:02:28 +0100 Subject: [csw-maintainers] new PHP maintainer needed Message-ID: <49495AD4.8000806@opencsw.org> Hello, Cory left about a year ago. Because he had all his packages in Gar, I was able to build a new PHP package. Unfortunately I'm not the right person for this package and besides that, I don't have enough resources to maintain the PHP package. Therefore I would like to ask, if someone can take over this important package. Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From dam at opencsw.org Thu Dec 18 11:42:48 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 18 Dec 2008 11:42:48 +0100 Subject: [csw-maintainers] New members Message-ID: <06285DD2-98C4-4403-A104-495AE81F39AE@opencsw.org> Hi, the association welcomes the newly accepted members - Ben Walton - Chris Reece - Michael Gernoth - Murray Jensen - Peter Bonivart All of you have already contributed to the project in the past. Ben, Murray and Peter are already very active on the new OpenCSW to update their packages. Michael operates the master mirror and has still sabbatical on his maintained packages. Chris contributed with a non-trivial patch to pca as latest effort. Please keep in mind that being a maintainer is not only about fame and glory, but also about tedious work to make the packages as good as possible and remove bugs timely when discovered. Please check regularly at the bottom of your maintainer page if there are any open issues. If you have spare cycles please adopt an orphaned package and help bring the complete software stack to a 100% current state. But enough of morality: A very warm welcome! Your membership is tracked at There is now a new column with your dedication in the project. Please let me know on what are you working or are planning to work like "webpage", "maintainer", etc. Best regards -- Dago From phil at bolthole.com Thu Dec 18 18:32:46 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 18 Dec 2008 09:32:46 -0800 Subject: [csw-maintainers] build requirements In-Reply-To: <49484D2E.2010908@opencsw.org> References: <1229462603-sup-6135@ntdws12.chass.utoronto.ca> <49484D2E.2010908@opencsw.org> Message-ID: <20081218173245.GE54484@bolthole.com> On Wed, Dec 17, 2008 at 01:51:58AM +0100, Trygve Laugst??l wrote: > I assume that 3) would lead to requiring me having /opt/csw/gnu first in > my path when using git and that is not going to happen. I'll point out that, even though that is not the case for this PARTICULAR program... a potential way of solving this sort of thing, is to make the top-level binary be a wrapper script, that does something along the lines of export PATH=/opt/csw/gnu:$PATH exec $0 $* thus it would only affect the prorgram and its children, rather than the user's environment at large. From bwalton at opencsw.org Thu Dec 18 20:49:22 2008 From: bwalton at opencsw.org (Ben Walton) Date: Thu, 18 Dec 2008 14:49:22 -0500 Subject: [csw-maintainers] new PHP maintainer needed In-Reply-To: <49495AD4.8000806@opencsw.org> References: <49495AD4.8000806@opencsw.org> Message-ID: <1229629675-sup-9039@ntdws12.chass.utoronto.ca> Excerpts from Ihsan Dogan's message of Wed Dec 17 15:02:28 -0500 2008: > > Therefore I would like to ask, if someone can take over this important > package. Also, what is the plan for php4. As it's no longer supported upstream (even for security patches, I understand), what are we to do with it? http://www.php.net/downloads.php#v4 My feeling is that it should be dropped...php5 has been out long enough, apps have had time to get ported (where necessary), etc. What do others think? -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From phil at bolthole.com Thu Dec 18 21:09:50 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 18 Dec 2008 12:09:50 -0800 Subject: [csw-maintainers] new PHP maintainer needed In-Reply-To: <1229629675-sup-9039@ntdws12.chass.utoronto.ca> References: <49495AD4.8000806@opencsw.org> <1229629675-sup-9039@ntdws12.chass.utoronto.ca> Message-ID: <20081218200950.GH54484@bolthole.com> On Thu, Dec 18, 2008 at 02:49:22PM -0500, Ben Walton wrote: > Excerpts from Ihsan Dogan's message of Wed Dec 17 15:02:28 -0500 2008: > > > > > Therefore I would like to ask, if someone can take over this important > > package. > > Also, what is the plan for php4. As it's no longer supported upstream > (even for security patches, I understand), what are we to do with it? > > http://www.php.net/downloads.php#v4 Just leave it alone. it doesnt conflict with anything. if we had a generic "php" package, it should certainly be pointed to use php5 now. but we dont. so it's a moot point, in my opinion. I guess it might be nice if the two things that depend on it, dotproject and drupal, were updated to use php5 though. Now, back to the more important issue... Who would like to maintain php5? :-) From phil at bolthole.com Thu Dec 18 21:14:10 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 18 Dec 2008 12:14:10 -0800 Subject: [csw-maintainers] large project: pkagdd/pkgrm open source package? Message-ID: <20081218201410.GI54484@bolthole.com> So.... Sun has some "issues" with pkgadd and pkgrm... such as not fixing glaring bugs, like having a "pkgadd -G" flag, but no "pkgrm -G" flag. it would seem they have frozen out any changes; that is to say, not putting any further resources into it. but meanwhile, us folks out here still need to use it. Is there any brave soul out there, with a LOT of time on their hands, who might consider packaging up our own open-source versions of them, and potentially fixing missing features, such as the -G flag? While you were in the vicinity, you might also wish to fix things like the stupid "if not root, then bail out" limit, so that we can safely use pkgadd on a per-user area basis. Supposedly, most if not all of it has finally been opened now. From bwalton at opencsw.org Thu Dec 18 22:18:59 2008 From: bwalton at opencsw.org (Ben Walton) Date: Thu, 18 Dec 2008 16:18:59 -0500 Subject: [csw-maintainers] git in testing Message-ID: <1229634705-sup-2537@ntdws12.chass.utoronto.ca> Hi All, I've dropped the current build of the git* packages in /home/testing. Currently, these are built for solaris 10 on x86 (I don't have a good solaris 8 build environment yet and am waiting for the prequisite packages to be relased so I can do it on the buildfarm). As yet, I don't know if there are issues building on solaris 8 at all...time will tell. I've done successful clones of some repos (using the ssh transport) and both gitk and `git gui` fire up their respective tk windows and seem functional. I'm sure there are still some rough edges and there are some other little things that I'll clean up for my own tastes, but the basics should be in place. I'd appreciate feedback (positive or negative) on this if you're willing to take a poke at it. Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From trygvel at opencsw.org Thu Dec 18 23:11:23 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Thu, 18 Dec 2008 23:11:23 +0100 Subject: [csw-maintainers] build requirements In-Reply-To: <20081218173245.GE54484@bolthole.com> References: <1229462603-sup-6135@ntdws12.chass.utoronto.ca> <49484D2E.2010908@opencsw.org> <20081218173245.GE54484@bolthole.com> Message-ID: <494ACA8B.2040809@opencsw.org> Philip Brown wrote: > On Wed, Dec 17, 2008 at 01:51:58AM +0100, Trygve Laugst?l wrote: >> I assume that 3) would lead to requiring me having /opt/csw/gnu first in >> my path when using git and that is not going to happen. > > I'll point out that, even though that is not the case for this PARTICULAR > program... a potential way of solving this sort of thing, is to make the > top-level binary be a wrapper script, that does something along the > lines of > > export PATH=/opt/csw/gnu:$PATH > exec $0 $* > > thus it would only affect the prorgram and its children, rather than the > user's environment at large. That is indeed true, I've even done similar tricks myself before :) -- Trygve From trygvel at opencsw.org Thu Dec 18 23:13:41 2008 From: trygvel at opencsw.org (=?UTF-8?B?VHJ5Z3ZlIExhdWdzdMO4bA==?=) Date: Thu, 18 Dec 2008 23:13:41 +0100 Subject: [csw-maintainers] git in testing In-Reply-To: <1229634705-sup-2537@ntdws12.chass.utoronto.ca> References: <1229634705-sup-2537@ntdws12.chass.utoronto.ca> Message-ID: <494ACB15.4090107@opencsw.org> Ben Walton wrote: > Hi All, > > I've dropped the current build of the git* packages in /home/testing. > Currently, these are built for solaris 10 on x86 (I don't have a good > solaris 8 build environment yet and am waiting for the prequisite > packages to be relased so I can do it on the buildfarm). As yet, I > don't know if there are issues building on solaris 8 at all...time > will tell. I think you should add them to Hudson even if they're not accepted yet. If you want to I can add solaris10{x,s} builders so you (and the testers) can keep updated. > I've done successful clones of some repos (using the ssh transport) > and both gitk and `git gui` fire up their respective tk windows and > seem functional. > > I'm sure there are still some rough edges and there are some other > little things that I'll clean up for my own tastes, but the basics > should be in place. > > I'd appreciate feedback (positive or negative) on this if you're > willing to take a poke at it. -- Trygve From phil at bolthole.com Thu Dec 18 23:22:47 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 18 Dec 2008 14:22:47 -0800 Subject: [csw-maintainers] git in testing In-Reply-To: <494ACB15.4090107@opencsw.org> References: <1229634705-sup-2537@ntdws12.chass.utoronto.ca> <494ACB15.4090107@opencsw.org> Message-ID: <20081218222247.GJ54484@bolthole.com> On Thu, Dec 18, 2008 at 11:13:41PM +0100, Trygve Laugst??l wrote: > Ben Walton wrote: > > Hi All, > > > > I've dropped the current build of the git* packages in /home/testing. > > Currently, these are built for solaris 10 on x86 (I don't have a good > > solaris 8 build environment yet and am waiting for the prequisite > > packages to be relased so I can do it on the buildfarm). As yet, I > > don't know if there are issues building on solaris 8 at all...time > > will tell. > > I think you should add them to Hudson even if they're not accepted yet. This would be a very bad precedent. Conceptually, I would think it would be as bad as installing packages on the build machines that have not been accepted for release. Packages sometimes do not get accepted for release, because they SHOULD NOT BE released. This created a large amount of problems with certain packages last month. From dam at opencsw.org Fri Dec 19 00:17:24 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 19 Dec 2008 00:17:24 +0100 Subject: [csw-maintainers] git in testing In-Reply-To: <20081218222247.GJ54484@bolthole.com> References: <1229634705-sup-2537@ntdws12.chass.utoronto.ca> <494ACB15.4090107@opencsw.org> <20081218222247.GJ54484@bolthole.com> Message-ID: <3B2C76BD-C314-4C6E-9FD3-4EC5A45453B8@opencsw.org> Hi Phil, Am 18.12.2008 um 23:22 schrieb Philip Brown: > On Thu, Dec 18, 2008 at 11:13:41PM +0100, Trygve Laugst??l wrote: >> I think you should add them to Hudson even if they're not accepted >> yet. > > This would be a very bad precedent. Conceptually, I would think it > would be > as bad as installing packages on the build machines that have not been > accepted for release. Definitely not. It should be in Hudson when the directory is created. Having Hudson run jobs makes it easier to concentrate e. g. on sparc and let Hudson do x86. > Packages sometimes do not get accepted for release, because they > SHOULD NOT BE released. This created a large amount of problems > with certain packages last month. The output of Hudson is one step before testing. There is no damage using Hudson. Best regards -- Dago From phil at bolthole.com Fri Dec 19 00:26:39 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 18 Dec 2008 15:26:39 -0800 Subject: [csw-maintainers] git in testing In-Reply-To: <3B2C76BD-C314-4C6E-9FD3-4EC5A45453B8@opencsw.org> References: <1229634705-sup-2537@ntdws12.chass.utoronto.ca> <494ACB15.4090107@opencsw.org> <20081218222247.GJ54484@bolthole.com> <3B2C76BD-C314-4C6E-9FD3-4EC5A45453B8@opencsw.org> Message-ID: <20081218232639.GL54484@bolthole.com> On Fri, Dec 19, 2008 at 12:17:24AM +0100, Dagobert Michelsen wrote: > > Packages sometimes do not get accepted for release, because they > > SHOULD NOT BE released. This created a large amount of problems > > with certain packages last month. > > The output of Hudson is one step before testing. There is no > damage using Hudson. So, you are sayin that adding broken packages "in hudson", has zero possiblility to corrupt other packages "in hudson" then? BTW: It might be nice to have a beginner-level description of "this is hudson, what it does, and roughly how it works" page in the wiki or something, to help explain this stuff...? From dam at opencsw.org Fri Dec 19 00:30:39 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 19 Dec 2008 00:30:39 +0100 Subject: [csw-maintainers] git in testing In-Reply-To: <20081218232639.GL54484@bolthole.com> References: <1229634705-sup-2537@ntdws12.chass.utoronto.ca> <494ACB15.4090107@opencsw.org> <20081218222247.GJ54484@bolthole.com> <3B2C76BD-C314-4C6E-9FD3-4EC5A45453B8@opencsw.org> <20081218232639.GL54484@bolthole.com> Message-ID: Hi Phil, Am 19.12.2008 um 00:26 schrieb Philip Brown: > On Fri, Dec 19, 2008 at 12:17:24AM +0100, Dagobert Michelsen wrote: >>> Packages sometimes do not get accepted for release, because they >>> SHOULD NOT BE released. This created a large amount of problems >>> with certain packages last month. >> >> The output of Hudson is one step before testing. There is no >> damage using Hudson. > > So, you are sayin that adding broken packages "in hudson", has zero > possiblility to corrupt other packages "in hudson" then? Yes. There is no package installed. It is just "gmake package" on every commit and that's it. > BTW: It might be nice to have a beginner-level description of > "this is hudson, what it does, and roughly how it works" page in the > wiki > or something, to help explain this stuff...? That would help, yes. Maybe Trygve prepares something when we ask him extra nice? ;-) Best regards -- Dago From phil at bolthole.com Fri Dec 19 00:42:30 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 18 Dec 2008 15:42:30 -0800 Subject: [csw-maintainers] git in testing In-Reply-To: References: <1229634705-sup-2537@ntdws12.chass.utoronto.ca> <494ACB15.4090107@opencsw.org> <20081218222247.GJ54484@bolthole.com> <3B2C76BD-C314-4C6E-9FD3-4EC5A45453B8@opencsw.org> <20081218232639.GL54484@bolthole.com> Message-ID: <20081218234230.GO54484@bolthole.com> On Fri, Dec 19, 2008 at 12:30:39AM +0100, Dagobert Michelsen wrote: > >> The output of Hudson is one step before testing. There is no > >> damage using Hudson. > > > > So, you are sayin that adding broken packages "in hudson", has zero > > possiblility to corrupt other packages "in hudson" then? > > Yes. There is no package installed. It is just "gmake package" > on every commit and that's it. ?? but in what environment? unless it's a bottom-level library, it has to get what it "makes" against, from SOMEWHERE. does hudson, not get that stuff from other things "in hudson" ?? From bwalton at opencsw.org Fri Dec 19 01:54:02 2008 From: bwalton at opencsw.org (Ben Walton) Date: Thu, 18 Dec 2008 19:54:02 -0500 Subject: [csw-maintainers] git in testing In-Reply-To: <20081218234230.GO54484@bolthole.com> References: <1229634705-sup-2537@ntdws12.chass.utoronto.ca> <494ACB15.4090107@opencsw.org> <20081218222247.GJ54484@bolthole.com> <3B2C76BD-C314-4C6E-9FD3-4EC5A45453B8@opencsw.org> <20081218232639.GL54484@bolthole.com> <20081218234230.GO54484@bolthole.com> Message-ID: <1229647909-sup-9888@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Thu Dec 18 18:42:30 -0500 2008: > but in what environment? unless it's a bottom-level library, it has to get > what it "makes" against, from SOMEWHERE. does hudson, not get that stuff > from other things "in hudson" ?? You're right Phil, in that adding git to hudson would currently be useless since it can't use the dependencies that don't exist yet. For packages that do have all dependencies published, I don't see any harm in having hudson ensure they're continuing to build (think gar changes, etc)...Even if the package doesn't get better (more platforms, for example), hudson can make sure it doesn't get worse. -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From phil at bolthole.com Fri Dec 19 02:08:05 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 18 Dec 2008 17:08:05 -0800 Subject: [csw-maintainers] hudson (previously, git in testing) In-Reply-To: <1229647909-sup-9888@ntdws12.chass.utoronto.ca> References: <1229634705-sup-2537@ntdws12.chass.utoronto.ca> <494ACB15.4090107@opencsw.org> <20081218222247.GJ54484@bolthole.com> <3B2C76BD-C314-4C6E-9FD3-4EC5A45453B8@opencsw.org> <20081218232639.GL54484@bolthole.com> <20081218234230.GO54484@bolthole.com> <1229647909-sup-9888@ntdws12.chass.utoronto.ca> Message-ID: <20081219010805.GP54484@bolthole.com> On Thu, Dec 18, 2008 at 07:54:02PM -0500, Ben Walton wrote: > Excerpts from Philip Brown's message of Thu Dec 18 18:42:30 -0500 2008: > > but in what environment? unless it's a bottom-level library, it has to get > > what it "makes" against, from SOMEWHERE. does hudson, not get that stuff > > from other things "in hudson" ?? > > You're right Phil, in that adding git to hudson would currently be > useless since it can't use the dependencies that don't exist yet. For > packages that do have all dependencies published, I don't see any harm > in having hudson ensure they're continuing to build (think gar > changes, etc)...Even if the package doesn't get better (more > platforms, for example), hudson can make sure it doesn't get worse. > dependson what the purpose of hudson is. If it's just "play around and see if things build nicely", then great. If on the other hand, it is on the road to becoming "the official way to build packages before publication", as some people seem to wish, then there needs to be stricter rules about putting things into hudson, otherwise we risk massive corruption. From trygvel at opencsw.org Fri Dec 19 07:56:25 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Fri, 19 Dec 2008 07:56:25 +0100 Subject: [csw-maintainers] hudson (previously, git in testing) In-Reply-To: <20081219010805.GP54484@bolthole.com> References: <1229634705-sup-2537@ntdws12.chass.utoronto.ca> <494ACB15.4090107@opencsw.org> <20081218222247.GJ54484@bolthole.com> <3B2C76BD-C314-4C6E-9FD3-4EC5A45453B8@opencsw.org> <20081218232639.GL54484@bolthole.com> <20081218234230.GO54484@bolthole.com> <1229647909-sup-9888@ntdws12.chass.utoronto.ca> <20081219010805.GP54484@bolthole.com> Message-ID: <494B4599.3020008@opencsw.org> Philip Brown wrote: > On Thu, Dec 18, 2008 at 07:54:02PM -0500, Ben Walton wrote: >> Excerpts from Philip Brown's message of Thu Dec 18 18:42:30 -0500 2008: >>> but in what environment? unless it's a bottom-level library, it has to get >>> what it "makes" against, from SOMEWHERE. does hudson, not get that stuff >>> from other things "in hudson" ?? >> You're right Phil, in that adding git to hudson would currently be >> useless since it can't use the dependencies that don't exist yet. For >> packages that do have all dependencies published, I don't see any harm >> in having hudson ensure they're continuing to build (think gar >> changes, etc)...Even if the package doesn't get better (more >> platforms, for example), hudson can make sure it doesn't get worse. >> > > dependson what the purpose of hudson is. > If it's just "play around and see if things build nicely", then great. > > > If on the other hand, it is on the road to becoming > "the official way to build packages before publication", > as some people seem to wish, then there needs to be stricter rules about > putting things into hudson, otherwise we risk massive corruption. That is right, but right it is working in the first way. I would like to extend that way to automatically pkgrm/pkgadd the packages once they're done. I'd like to start the second way once we have some more experience with Hudson and GAR has the few glitches ironed out (and we have a lot of time to actually get the process going). -- Trygve From dam at opencsw.org Fri Dec 19 11:49:44 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 19 Dec 2008 11:49:44 +0100 Subject: [csw-maintainers] Batch takeover of orphaned Perl modules possible? Message-ID: <090B00FA-E4AF-4907-9A6B-9A0C70850CBF@opencsw.org> Hi, William, you could prepare a batch update of the version for all Perl modules for Alex Moore? He has quite some: Maybe Peter as Perl maintainer wants to take a look at them? ;-) Trygve, can we do this as first production test for Hudson? I am eager to automate the tedious Perl module packaging. I vaguely remember some guy posting a script to automate the Perl module packaging without GAR. Does anyone remember? Maybe we can integrate the dependency-extraction from Makefile.PL from it. Best regards and Merry Christmas -- Dago From Darin.Perusich at cognigencorp.com Fri Dec 19 14:37:05 2008 From: Darin.Perusich at cognigencorp.com (Darin Perusich) Date: Fri, 19 Dec 2008 08:37:05 -0500 Subject: [csw-maintainers] new PHP maintainer needed In-Reply-To: <20081218200950.GH54484@bolthole.com> References: <49495AD4.8000806@opencsw.org> <1229629675-sup-9039@ntdws12.chass.utoronto.ca> <20081218200950.GH54484@bolthole.com> Message-ID: <494BA381.4060207@cognigencorp.com> Philip Brown wrote: > On Thu, Dec 18, 2008 at 02:49:22PM -0500, Ben Walton wrote: >> Excerpts from Ihsan Dogan's message of Wed Dec 17 15:02:28 -0500 2008: >> >>> Therefore I would like to ask, if someone can take over this important >>> package. >> Also, what is the plan for php4. As it's no longer supported upstream >> (even for security patches, I understand), what are we to do with it? >> >> http://www.php.net/downloads.php#v4 > > Just leave it alone. it doesnt conflict with anything. > if we had a generic "php" package, it should certainly be pointed to use > php5 now. > but we dont. so it's a moot point, in my opinion. Why just leave it alone? While I don't believe I'm the right person to bring this up, given I'm not a very active maintain, this not abandoning old software is one of the short comings of how we release packages. There is no way to gracefully remove old packages from the release cycle. This could be easily accomplished if when we have a stable release it was moved out of the stable/unstable directory structure and into it's own little world of YYYY-MM/{i386/sparc}. If this was how we did the releases it was be trivial to say, As of stable release 2008-12 support for the php4, mysql4, etc. package is being dropped. Then is someone wanted to use those version they could point pkg-get at that repository. Given the current paradigm we can't really remove old stuff from the software tree because someone MIGHT be using it. > I guess it might be nice if the two things that depend on it, > dotproject and drupal, were updated to use php5 though. I believe that version of drupal doesn't support php5, or it supports only an early release. Another one of those instances where we're the dependency of an OLD package is forcing us to keep other old clutter within the software stack. > Now, back to the more important issue... > Who would like to maintain php5? :-) > -- Darin Perusich Unix Systems Administrator Cognigen Corporation 395 Youngs Rd. Williamsville, NY 14221 Phone: 716-633-3463 Email: darinper at cognigencorp.com From bonivart at opencsw.org Fri Dec 19 15:39:02 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Fri, 19 Dec 2008 15:39:02 +0100 Subject: [csw-maintainers] Batch takeover of orphaned Perl modules possible? In-Reply-To: <090B00FA-E4AF-4907-9A6B-9A0C70850CBF@opencsw.org> References: <090B00FA-E4AF-4907-9A6B-9A0C70850CBF@opencsw.org> Message-ID: <625385e30812190639l6b152d61r81fc45faaab88136@mail.gmail.com> On Fri, Dec 19, 2008 at 11:49 AM, Dagobert Michelsen wrote: > Hi, > > William, you could prepare a batch update of the version for > all Perl modules for Alex Moore? He has quite some: > > Maybe Peter as Perl maintainer wants to take a look at them? ;-) I have taken everything from Alex that I have an interest in. :-) If there's a few (<10) perl modules that are out of date I can take them, they are real easy to build. Maybe the update notification could e-mail the maintainer list when the maintainer is listed as retired? By the way, Sendmail is another package from Alex that is important. Luckily it's pretty current still. -- /peter From phil at bolthole.com Fri Dec 19 16:25:51 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 19 Dec 2008 07:25:51 -0800 Subject: [csw-maintainers] new PHP maintainer needed In-Reply-To: <494BA381.4060207@cognigencorp.com> References: <49495AD4.8000806@opencsw.org> <1229629675-sup-9039@ntdws12.chass.utoronto.ca> <20081218200950.GH54484@bolthole.com> <494BA381.4060207@cognigencorp.com> Message-ID: <20081219152551.GC46050@bolthole.com> On Fri, Dec 19, 2008 at 08:37:05AM -0500, Darin Perusich wrote: > >[Philip Brown wrote] > > I guess it might be nice if the two things that depend on [php4], > > dotproject and drupal, were updated to use php5 though. > > I believe that version of drupal doesn't support php5, or it supports > only an early release. Another one of those instances where we're the > dependency of an OLD package is forcing us to keep other old clutter > within the software stack. So, we cant even consider dropping php4, until drupal is updated. Ummm.... and who is the maintainer of our drupal package... "Darin Perusich". I find it ironic, that you are complaining about something, that you are the primary path to resolution for? :-} A side note: a quick trip to the drupal website, says that "Drupal works with PHP 4 & 5" From Darin.Perusich at cognigencorp.com Fri Dec 19 16:45:57 2008 From: Darin.Perusich at cognigencorp.com (Darin Perusich) Date: Fri, 19 Dec 2008 10:45:57 -0500 Subject: [csw-maintainers] new PHP maintainer needed In-Reply-To: <20081219152551.GC46050@bolthole.com> References: <49495AD4.8000806@opencsw.org> <1229629675-sup-9039@ntdws12.chass.utoronto.ca> <20081218200950.GH54484@bolthole.com> <494BA381.4060207@cognigencorp.com> <20081219152551.GC46050@bolthole.com> Message-ID: <494BC1B5.4070707@cognigencorp.com> Philip Brown wrote: > On Fri, Dec 19, 2008 at 08:37:05AM -0500, Darin Perusich wrote: >>> [Philip Brown wrote] >>> I guess it might be nice if the two things that depend on [php4], >>> dotproject and drupal, were updated to use php5 though. >> I believe that version of drupal doesn't support php5, or it supports >> only an early release. Another one of those instances where we're the >> dependency of an OLD package is forcing us to keep other old clutter >> within the software stack. > > So, we cant even consider dropping php4, until drupal is updated. > Don't forget Dotproject. > Ummm.... and who is the maintainer of our drupal package... > "Darin Perusich". > I wasn't aware it was my package, thanks for pointing that out. > I find it ironic, that you are complaining about something, that you are > the primary path to resolution for? :-} I wouldn't call it complaining, I'm merely pointing out something, again, that I feel is a deficiency. As the "primary path to resolution", I propose removing drupal from the repository. -- Darin Perusich Unix Systems Administrator Cognigen Corporation 395 Youngs Rd. Williamsville, NY 14221 Phone: 716-633-3463 Email: darinper at cognigencorp.com From phil at bolthole.com Fri Dec 19 16:52:06 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 19 Dec 2008 07:52:06 -0800 Subject: [csw-maintainers] new PHP maintainer needed In-Reply-To: <494BC1B5.4070707@cognigencorp.com> References: <49495AD4.8000806@opencsw.org> <1229629675-sup-9039@ntdws12.chass.utoronto.ca> <20081218200950.GH54484@bolthole.com> <494BA381.4060207@cognigencorp.com> <20081219152551.GC46050@bolthole.com> <494BC1B5.4070707@cognigencorp.com> Message-ID: <20081219155206.GB4156@bolthole.com> On Fri, Dec 19, 2008 at 10:45:57AM -0500, Darin Perusich wrote: > I wouldn't call it complaining, I'm merely pointing out something, > again, that I feel is a deficiency. > > As the "primary path to resolution", I propose removing drupal from the > repository. why would you not update the package? From Darin.Perusich at cognigencorp.com Fri Dec 19 17:22:12 2008 From: Darin.Perusich at cognigencorp.com (Darin Perusich) Date: Fri, 19 Dec 2008 11:22:12 -0500 Subject: [csw-maintainers] new PHP maintainer needed In-Reply-To: <20081219155206.GB4156@bolthole.com> References: <49495AD4.8000806@opencsw.org> <1229629675-sup-9039@ntdws12.chass.utoronto.ca> <20081218200950.GH54484@bolthole.com> <494BA381.4060207@cognigencorp.com> <20081219152551.GC46050@bolthole.com> <494BC1B5.4070707@cognigencorp.com> <20081219155206.GB4156@bolthole.com> Message-ID: <494BCA34.3060602@cognigencorp.com> Philip Brown wrote: > On Fri, Dec 19, 2008 at 10:45:57AM -0500, Darin Perusich wrote: >> I wouldn't call it complaining, I'm merely pointing out something, >> again, that I feel is a deficiency. >> >> As the "primary path to resolution", I propose removing drupal from the >> repository. > > why would you not update the package? > I am no longer running it on Solaris and don't want to be burdened with maintaining it. -- Darin Perusich Unix Systems Administrator Cognigen Corporation 395 Youngs Rd. Williamsville, NY 14221 Phone: 716-633-3463 Email: darinper at cognigencorp.com From phil at bolthole.com Fri Dec 19 18:00:44 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 19 Dec 2008 09:00:44 -0800 Subject: [csw-maintainers] new PHP maintainer needed In-Reply-To: <494BCA34.3060602@cognigencorp.com> References: <49495AD4.8000806@opencsw.org> <1229629675-sup-9039@ntdws12.chass.utoronto.ca> <20081218200950.GH54484@bolthole.com> <494BA381.4060207@cognigencorp.com> <20081219152551.GC46050@bolthole.com> <494BC1B5.4070707@cognigencorp.com> <20081219155206.GB4156@bolthole.com> <494BCA34.3060602@cognigencorp.com> Message-ID: <20081219170044.GA73995@bolthole.com> On Fri, Dec 19, 2008 at 11:22:12AM -0500, Darin Perusich wrote: > >> As the "primary path to resolution", I propose removing drupal from the > >> repository. > > > > why would you not update the package? > > > > I am no longer running it on Solaris and don't want to be burdened with > maintaining it. I suppose i could "orphan" the package, if you wished. What about your other packages? From Darin.Perusich at cognigencorp.com Fri Dec 19 19:02:15 2008 From: Darin.Perusich at cognigencorp.com (Darin Perusich) Date: Fri, 19 Dec 2008 13:02:15 -0500 Subject: [csw-maintainers] new PHP maintainer needed In-Reply-To: <20081219170044.GA73995@bolthole.com> References: <49495AD4.8000806@opencsw.org> <1229629675-sup-9039@ntdws12.chass.utoronto.ca> <20081218200950.GH54484@bolthole.com> <494BA381.4060207@cognigencorp.com> <20081219152551.GC46050@bolthole.com> <494BC1B5.4070707@cognigencorp.com> <20081219155206.GB4156@bolthole.com> <494BCA34.3060602@cognigencorp.com> <20081219170044.GA73995@bolthole.com> Message-ID: <494BE1A7.1090408@cognigencorp.com> Philip Brown wrote: > On Fri, Dec 19, 2008 at 11:22:12AM -0500, Darin Perusich wrote: >>>> As the "primary path to resolution", I propose removing drupal from the >>>> repository. >>> why would you not update the package? >>> >> I am no longer running it on Solaris and don't want to be burdened with >> maintaining it. > > I suppose i could "orphan" the package, if you wished. My preference would to remove it from the repository but given that someone, somewhere might be using it then orphan it. > What about your other packages? Are working fine and I am in no hurry to upgrade them, with the exception of Amanda which I'll update soon. -- Darin Perusich Unix Systems Administrator Cognigen Corporation 395 Youngs Rd. Williamsville, NY 14221 Phone: 716-633-3463 Email: darinper at cognigencorp.com From bwalton at opencsw.org Fri Dec 19 19:53:23 2008 From: bwalton at opencsw.org (Ben Walton) Date: Fri, 19 Dec 2008 13:53:23 -0500 Subject: [csw-maintainers] git in testing (solaris 8, sparc) In-Reply-To: <1229634705-sup-2537@ntdws12.chass.utoronto.ca> References: <1229634705-sup-2537@ntdws12.chass.utoronto.ca> Message-ID: <1229712619-sup-5245@ntdws12.chass.utoronto.ca> Hi All, There are now packages for git (solaris 8, sparc) in /home/testing [git*12.19*gz]. Same caveats as before...I'm sure there is some cleanup left in terms of the package part, but the actual delivered files seem to work. All tests (except expected failures) passed on this platform, which is a good sign. Feedback welcome. -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From phil at bolthole.com Sat Dec 20 19:35:01 2008 From: phil at bolthole.com (Philip Brown) Date: Sat, 20 Dec 2008 10:35:01 -0800 Subject: [csw-maintainers] need maintainer for mysql Message-ID: <20081220183501.GA51383@bolthole.com> btw: we badly need a maintainer for mysql. we need to upgrade from 5.0 to 5.1 any takers? From trygvel at opencsw.org Sun Dec 21 14:07:20 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Sun, 21 Dec 2008 14:07:20 +0100 Subject: [csw-maintainers] Catalog for /testing? Message-ID: <494E3F88.6020506@opencsw.org> Hei! Would it be possible to generate a catalog for the packages in testing? I'd love to be able to make sure that I always get the correct/updated set of dependencies when I want to try out some package. Right now I'd like to test Ben's git work, but as I've built a few of the packages myself I have some outdated packages and some missing. I would like to just do a pkg-get -c to find the outdated ones and/or just pkg-get -i git to get them all. -- Trygve From bonivart at opencsw.org Sun Dec 21 14:16:55 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Sun, 21 Dec 2008 14:16:55 +0100 Subject: [csw-maintainers] Catalog for /testing? In-Reply-To: <494E3F88.6020506@opencsw.org> References: <494E3F88.6020506@opencsw.org> Message-ID: <625385e30812210516w15df19d3g6f67abebcee31268@mail.gmail.com> On Sun, Dec 21, 2008 at 2:07 PM, Trygve Laugst?l wrote: > Hei! > > Would it be possible to generate a catalog for the packages in testing? > I'd love to be able to make sure that I always get the correct/updated > set of dependencies when I want to try out some package. > > Right now I'd like to test Ben's git work, but as I've built a few of > the packages myself I have some outdated packages and some missing. I > would like to just do a pkg-get -c to find the outdated ones and/or just > pkg-get -i git to get them all. Isn't this what you're looking for? http://buildfarm.opencsw.org/testing.html -- /peter From james at opencsw.org Sun Dec 21 14:36:05 2008 From: james at opencsw.org (James Lee) Date: Sun, 21 Dec 2008 13:36:05 GMT Subject: [csw-maintainers] Catalog for /testing? In-Reply-To: <494E3F88.6020506@opencsw.org> References: <494E3F88.6020506@opencsw.org> Message-ID: <20081221.13360500.1565619539@gyor.oxdrove.co.uk> On 21/12/08, 13:07:20, "Trygve Laugst?l" wrote regarding [csw-maintainers] Catalog for /testing?: > Would it be possible to generate a catalog for the packages in testing? It's possible but ill advised. The content of testing need not represent a coherent state from which general update makes sense. If it did it would be what unstable is. Select and download the packages you know you want to install and make your own catalog. James. From bwalton at opencsw.org Mon Dec 22 05:19:16 2008 From: bwalton at opencsw.org (Ben Walton) Date: Sun, 21 Dec 2008 23:19:16 -0500 Subject: [csw-maintainers] docbook, dependencies, what do we want...? Message-ID: <1229918644-sup-5016@ntdws12.chass.utoronto.ca> Hi All, Phil and I have been discussing this for the last few days and I thought I'd open it up to everyone else, as your input is likely valuable here. I've put together a docbook dtds package that provides xml and sgml dtd files for various versions of the docbook standard. At installation time, the xmlcatalog tool is used to 'register' the newly installed catalog files so that consumers of dtds can find them. This sets up a dependency on the libxml2 package (provider of xmlcatalog). As I modeled this package on the one found in rhel5, I also setup a dependency on openjade. This one is a little tenuous though, as the dependency is basically conditional on some other stylesheets having been installed on the system before the docbook dtds (which may be a legacy rpm issue and not valid anymore). The postinstall script looks for stylesheets and if it finds them, registers the dtds in the openjade catalogs. Phil doesn't like this and I'm not going to defend it either, as I was simply replicating faithfully the package stack in another platform to get to my ultimate goal (packaging git). I see a few options here to make this better: 1. Leave it as is, since there is a basis for doing this provided by at least one other distro (more when you look at rhel derivatives). 2. Drop the dependency but still do the postinstall things if both stylesheets _and_ openjade are detected. 3. Drop the dependency, remove this chunk of the postinstall script, which leaves it up to the user to do the registration if required/desired. After looking into it a bit more, and comparing how Debian's approach to compared with the Redhat approach I mimicked, I think I like option 3 the best. ...So, in our discussions, a few other things have come up that I think are worthy of a wider audience for discussion since these base packages may prove useful down the road for others. 1. Provide a more generic 'plugin' system for these packages to make option 2 above simpler. 2. Package something like: http://freshmeat.net/projects/dbsgmltoolbox/, which would provide a 'stack in a box' type approach to these tools. Having mulled this over for a few days since Phil proposed it, I'll lay out my opinions/thoughts on them and then let others whack the pinata. As for the 'plugin' system, I think that's more involved than we need to be. It doesn't seem that either Debian or Redhat do this. Although they have slightly different approaches, both Debian and Redhat rely on either their libxml2 package and/or their own catalog manipulation tools. Debian has much smarter machinery for doing this (via debhelper) and has made use of their stronger dependency system (eg: Suggests for optional dependencies), but overall they take a similar approach to Redhat for delivery. To me, this seems like an unnecessary moving part. With regard to the dbsgmltoolbox idea, I would suggest that bundling all those apps into packages is worthwhile iff there is a need for them. As it seems that the xmlto package is the first csw application that calls for full blown dtd/xsl/xml stuff, I don't see this need. I say don't build it until its needed (borrowing from the "you aren't going to need it" philosophy). So my questions to everyone are: 1. Does anyone see a need for more tools to register dtds and stylesheets? If so, should they be built now or when they're actually needed? 2. Does anyone have need for the type of tools provided with dbsgmltoolbox now? If so, I can package them up (since I opened this can of worms). I'm not about to spend time on something nobody is interested in though. 3. What does everyone think about the dependencies for the docbook dtd's package? I'd like to get this resolved asap so that docbook xsl can be released and then finally xmlto. Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From trygvel at opencsw.org Mon Dec 22 12:37:04 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Mon, 22 Dec 2008 12:37:04 +0100 Subject: [csw-maintainers] [Fwd: [csw-devel] SF.net SVN: gar:[2683] csw/mgar/gar/v2] Message-ID: <494F7BE0.7090303@opencsw.org> Hei! I've added some targets to gar [1] to make it easier to work with Subversion. Currently it support updating the package and updating gar. I'd like to get some feedback on the process that people are using when working with the source tree to create targets that match how people use it. Do an update of your gar/ directory and go "gmake scm-help" to get the overview (or just read further down in the email). [1]: only v2 for now until they're deemed useful for everyone. -- Trygve -------- Original Message -------- Subject: [csw-devel] SF.net SVN: gar:[2683] csw/mgar/gar/v2 Date: Mon, 22 Dec 2008 11:31:17 +0000 From: trygvis at users.sourceforge.net Reply-To: Developers list To: devel at lists.opencsw.org Revision: 2683 http://gar.svn.sourceforge.net/gar/?rev=2683&view=rev Author: trygvis Date: 2008-12-22 11:31:17 +0000 (Mon, 22 Dec 2008) Log Message: ----------- o Adding some targets to work with svn. Modified Paths: -------------- csw/mgar/gar/v2/gar.conf.mk Added Paths: ----------- csw/mgar/gar/v2/bin/svnignore csw/mgar/gar/v2/gar.svn.mk csw/mgar/gar/v2/scm-help Added: csw/mgar/gar/v2/bin/svnignore =================================================================== --- csw/mgar/gar/v2/bin/svnignore (rev 0) +++ csw/mgar/gar/v2/bin/svnignore 2008-12-22 11:31:17 UTC (rev 2683) @@ -0,0 +1,28 @@ +#!/bin/sh +# +# Copyright 2008-2009 OpenCSW +# +# Redistribution and/or use, with or without modification, is +# permitted. This software is without warranty of any kind. The +# author(s) shall not be liable in the event that use of the +# software causes damage. +# +# gar.svn.mk - Targets for working with svn + +# Read the comma separated ignores from stdin and merges it with any existing +# ignores set on the directory. + +ignores=`mktemp`-ignores +existing_ignores=`mktemp`-existing +new_ignores=`mktemp`-new + +while [ "$1" != "" ]; do + echo $1 >> $ignores + shift +done + +svn pg svn:ignore . > $existing_ignores +cat $ignores $existing_ignores | sort | uniq > $new_ignores +svn ps svn:ignore . -F $new_ignores + +rm -rf $ignores $existing_ignores $new_ignores Property changes on: csw/mgar/gar/v2/bin/svnignore ___________________________________________________________________ Added: svn:executable + * Modified: csw/mgar/gar/v2/gar.conf.mk =================================================================== --- csw/mgar/gar/v2/gar.conf.mk 2008-12-22 01:28:00 UTC (rev 2682) +++ csw/mgar/gar/v2/gar.conf.mk 2008-12-22 11:31:17 UTC (rev 2683) @@ -568,8 +568,7 @@ FILE_SITES = $(foreach DIR,$(FILEDIR) $(GARCHIVEPATH),file://$(DIR)/) # Extra libraries -EXTRA_LIBS = gar.pkg.mk gar.common.mk - +EXTRA_LIBS = gar.pkg.mk gar.common.mk gar.svn.mk ccenv: @echo " Compiler: $(GARCOMPILER)" @echo Added: csw/mgar/gar/v2/gar.svn.mk =================================================================== --- csw/mgar/gar/v2/gar.svn.mk (rev 0) +++ csw/mgar/gar/v2/gar.svn.mk 2008-12-22 11:31:17 UTC (rev 2683) @@ -0,0 +1,29 @@ +# vim: ft=make ts=4 sw=4 noet +# +# $Id$ +# +# Copyright 2008-2009 OpenCSW +# +# Redistribution and/or use, with or without modification, is +# permitted. This software is without warranty of any kind. The +# author(s) shall not be liable in the event that use of the +# software causes damage. +# +# gar.svn.mk - Targets for working with svn +# + +scm-help: + @cat $(GARDIR)/scm-help + +scm-update-all: scm-update-package scm-update-gar + +scm-update-package: + $(SVN) --ignore-externals up + +scm-update-gar: + cd $(GARDIR) && $(SVN) --ignore-externals up + +scm-update-ignores: + $(GARDIR)/bin/svnignore work cookies download + +.PHONY: scm-help scm-update-all scm-update-package scm-update-gar Added: csw/mgar/gar/v2/scm-help =================================================================== --- csw/mgar/gar/v2/scm-help (rev 0) +++ csw/mgar/gar/v2/scm-help 2008-12-22 11:31:17 UTC (rev 2683) @@ -0,0 +1,10 @@ +These are the available SCM targets + +scm-update-all: + Updates both the package files and the gar/ directory + +scm-update-package: + Updates the package files + +scm-update-gar: + Updates the contents of the gar/ directory This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. _______________________________________________ devel mailing list devel at lists.opencsw.org https://lists.opencsw.org/mailman/listinfo/devel From jgoerzen at opencsw.org Mon Dec 22 23:43:08 2008 From: jgoerzen at opencsw.org (Jake Goerzen) Date: Mon, 22 Dec 2008 14:43:08 -0800 Subject: [csw-maintainers] /testing pkg wesnoth 1.4.7 Message-ID: <315c02ae0812221443p1e9248c8q8eec3a804d85230c@mail.gmail.com> Hello all, I have successfully build the latest stable wesnoth package (version 1.4.7) and placed them into "testing" wesnoth-1.4.7,REV=2008.12.22-SunOS5.8-i386-CSW.pkg.gz wesnoth-1.4.7,REV=2008.12.22-SunOS5.8-sparc-CSW.pkg.gz These packages where build with Sun Studio 11 on Solaris 8. Earlier I was only able to build this software on Studio 12 on Solaris 10. I found that when compiling with Studio 12 the preproccessor could deal with spaces in -I defines but Studio 11 seems not able to do this? Anyway, once I figured out what was going on I simply removed the empty space in the Makefile and then resumed building. I'll will work on getting all this into mgar so that it will auto build. ATM 1.4.7 is in mgar but a few manual tweeks are needed to get it to build. Just in time for the Holidays. Please give these a try and let me know. Thanks Jake -------------- next part -------------- An HTML attachment was scrubbed... URL: From jgoerzen at opencsw.org Mon Dec 22 23:54:29 2008 From: jgoerzen at opencsw.org (Jake Goerzen) Date: Mon, 22 Dec 2008 14:54:29 -0800 Subject: [csw-maintainers] mgar: gmake pkgclean Message-ID: <315c02ae0812221454g211969d8u2041a352cf0a79fa@mail.gmail.com> Hi, When using the older GAR tree I was in the habit of doing gmake pkgclean to clean things up. Is there this make target in the mgar tree? Thanks, Jake -------------- next part -------------- An HTML attachment was scrubbed... URL: From bwalton at opencsw.org Tue Dec 23 00:42:22 2008 From: bwalton at opencsw.org (Ben Walton) Date: Mon, 22 Dec 2008 18:42:22 -0500 Subject: [csw-maintainers] mgar: gmake pkgclean In-Reply-To: <315c02ae0812221454g211969d8u2041a352cf0a79fa@mail.gmail.com> References: <315c02ae0812221454g211969d8u2041a352cf0a79fa@mail.gmail.com> Message-ID: <1229989248-sup-2558@ntdws12.chass.utoronto.ca> Excerpts from Jake Goerzen's message of Mon Dec 22 17:54:29 -0500 2008: Hi Jake, > When using the older GAR tree I was in the habit of doing gmake pkgclean > to clean things up. Is there this make target in the mgar tree? A simple `gmake clean` will do the trick now. -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From glaw at opencsw.org Tue Dec 23 00:56:16 2008 From: glaw at opencsw.org (Gary Law) Date: Mon, 22 Dec 2008 23:56:16 +0000 Subject: [csw-maintainers] docbook, dependencies, what do we want...? In-Reply-To: <1229918644-sup-5016@ntdws12.chass.utoronto.ca> References: <1229918644-sup-5016@ntdws12.chass.utoronto.ca> Message-ID: 2008/12/22 Ben Walton > > Hi All, > Hi Ben I've ported Docbook to Solaris before, and getting the toolchain up and running is a pig, so well done for volunteering to look at this. I'd go for the lowest maintenance option that delivers a working package. Given the 'fire and forget' principles of opencsw I'd suggest you take the 'it just works' option of dbsgmltoolbox failing that, go with with the openjade dependency. I don't like the 'register if it is there' option, it will give variable results based on what else is installed already, which I don't like. Just my 2p Gary -- Gary Law Email: garylaw at garylaw.net Chat googletalk/messenger: gary.law at gmail.com iChat/jabber/AIM: gary.law at mac.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From trygvel at opencsw.org Tue Dec 23 19:45:06 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Tue, 23 Dec 2008 19:45:06 +0100 Subject: [csw-maintainers] SPARC issues Message-ID: <495131B2.6010405@opencsw.org> Hei! I'm trying to build ghc[1] and while it work just fine on x86, I'm getting these issues when it is trying to build its libraries after the compiler itself has been bootstrapped: /usr/ccs/bin/as: "/tmp/ghc24757_0/ghc24757_0.split__1.s", line 22: error: cannot use v8plus instructions in a non-v8plus target binary /usr/ccs/bin/as: "/tmp/ghc24757_0/ghc24757_0.split__1.s", line 28: error: cannot use v8plus instructions in a non-v8plus target binary /usr/ccs/bin/as: "/tmp/ghc24757_0/ghc24757_0.split__1.s", line 41: error: cannot use v8plus instructions in a non-v8plus target binary /usr/ccs/bin/as: "/tmp/ghc24757_0/ghc24757_0.split__1.s", line 56: error: cannot use v8plus instructions in a non-v8plus target binary Anyone have a clue on what I can do? I've set ISA_DEFAULT_sparc = sparcv8plus in the Makefile, and I did get a "work/build-isa-sparcv8plus/" directory so I think at least GAR is trying to build binaries with the sparcv8plus instruction set. But it still didn't work. [1]: Glasgow Haskell Compiler -- Trygve From phil at bolthole.com Tue Dec 23 20:32:17 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 23 Dec 2008 11:32:17 -0800 Subject: [csw-maintainers] SPARC issues In-Reply-To: <495131B2.6010405@opencsw.org> References: <495131B2.6010405@opencsw.org> Message-ID: <20081223193217.GJ64455@bolthole.com> On Tue, Dec 23, 2008 at 07:45:06PM +0100, Trygve Laugst?l wrote: > Hei! > > I'm trying to build ghc[1] and while it work just fine on x86, I'm > getting these issues when it is trying to build its libraries after the > compiler itself has been bootstrapped: > > /usr/ccs/bin/as: "/tmp/ghc24757_0/ghc24757_0.split__1.s", line 22: > error: cannot use v8plus instructions in a non-v8plus target binary > /usr/ccs/bin/as: "/tmp/ghc24757_0/ghc24757_0.split__1.s", line 28: > error: cannot use v8plus instructions in a non-v8plus target binary > /usr/ccs/bin/as: "/tmp/ghc24757_0/ghc24757_0.split__1.s", line 41: > error: cannot use v8plus instructions in a non-v8plus target binary > /usr/ccs/bin/as: "/tmp/ghc24757_0/ghc24757_0.split__1.s", line 56: > error: cannot use v8plus instructions in a non-v8plus target binary > > Anyone have a clue on what I can do? you arent giving enough details on what is calling as. is cc calling it, or something else directly? From trygvel at opencsw.org Tue Dec 23 21:23:37 2008 From: trygvel at opencsw.org (=?UTF-8?B?VHJ5Z3ZlIExhdWdzdMO4bA==?=) Date: Tue, 23 Dec 2008 21:23:37 +0100 Subject: [csw-maintainers] SPARC issues In-Reply-To: <20081223193217.GJ64455@bolthole.com> References: <495131B2.6010405@opencsw.org> <20081223193217.GJ64455@bolthole.com> Message-ID: <495148C9.5020703@opencsw.org> Philip Brown wrote: > On Tue, Dec 23, 2008 at 07:45:06PM +0100, Trygve Laugst?l wrote: >> Hei! >> >> I'm trying to build ghc[1] and while it work just fine on x86, I'm >> getting these issues when it is trying to build its libraries after the >> compiler itself has been bootstrapped: >> >> /usr/ccs/bin/as: "/tmp/ghc24757_0/ghc24757_0.split__1.s", line 22: >> error: cannot use v8plus instructions in a non-v8plus target binary >> /usr/ccs/bin/as: "/tmp/ghc24757_0/ghc24757_0.split__1.s", line 28: >> error: cannot use v8plus instructions in a non-v8plus target binary >> /usr/ccs/bin/as: "/tmp/ghc24757_0/ghc24757_0.split__1.s", line 41: >> error: cannot use v8plus instructions in a non-v8plus target binary >> /usr/ccs/bin/as: "/tmp/ghc24757_0/ghc24757_0.split__1.s", line 56: >> error: cannot use v8plus instructions in a non-v8plus target binary >> >> Anyone have a clue on what I can do? > > you arent giving enough details on what is calling as. > is cc calling it, or something else directly? ghc is calling as (perhaps through gcc, not sure) while building its core libs: gmake[4]: Entering directory `/home/trygvis/dev/ghc/work/build-isa-sparcv8plus/ghc-6.8.3/libraries/base' ../../compiler/stage1/ghc-inplace -package-name base-3.0.2.0 -hide-all-packages -split-objs -i -idist/build/autogen -idist/build -i. -Idist/build -Iinclude -#include "HsBase.h" -odir dist/build -hidir dist/build -stubdir dist/build -package rts-1.0 -O -package-name base -XMagicHash -XExistentialQuantification -XRank2Types -XScopedTypeVariables -XUnboxedTuples -XForeignFunctionInterface -XUnliftedFFITypes -XDeriveDataTypeable -XGeneralizedNewtypeDeriving -XFlexibleInstances -XPatternSignatures -XStandaloneDeriving -XPatternGuards -XCPP -idist/build -H16m -O -O -Rghc-timing -fgenerics -c GHC/Err.lhs-boot -o dist/build/GHC/Err.o-boot -ohi dist/build/GHC/Err.hi-boot <> ../../compiler/stage1/ghc-inplace -package-name base-3.0.2.0 -hide-all-packages -split-objs -i -idist/build/autogen -idist/build -i. -Idist/build -Iinclude -#include "HsBase.h" -odir dist/build -hidir dist/build -stubdir dist/build -package rts-1.0 -O -package-name base -XMagicHash -XExistentialQuantification -XRank2Types -XScopedTypeVariables -XUnboxedTuples -XForeignFunctionInterface -XUnliftedFFITypes -XDeriveDataTypeable -XGeneralizedNewtypeDeriving -XFlexibleInstances -XPatternSignatures -XStandaloneDeriving -XPatternGuards -XCPP -idist/build -H16m -O -O -Rghc-timing -fgenerics -c GHC/Base.lhs -o dist/build/GHC/Base.o -ohi dist/build/GHC/Base.hi -- Trygve From phil at bolthole.com Tue Dec 23 21:40:23 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 23 Dec 2008 12:40:23 -0800 Subject: [csw-maintainers] SPARC issues In-Reply-To: <495148C9.5020703@opencsw.org> References: <495131B2.6010405@opencsw.org> <20081223193217.GJ64455@bolthole.com> <495148C9.5020703@opencsw.org> Message-ID: <20081223204023.GA97070@bolthole.com> On Tue, Dec 23, 2008 at 09:23:37PM +0100, Trygve Laugst??l wrote: > > you arent giving enough details on what is calling as. > > is cc calling it, or something else directly? > > ghc is calling as (perhaps through gcc, not sure) while building its > core libs: > gaaahhh... I suspect the most practical thing to do in this instance, is to use the gnu compiler chain. sigh. From trygvel at opencsw.org Tue Dec 23 23:33:39 2008 From: trygvel at opencsw.org (=?UTF-8?B?VHJ5Z3ZlIExhdWdzdMO4bA==?=) Date: Tue, 23 Dec 2008 23:33:39 +0100 Subject: [csw-maintainers] docbook, dependencies, what do we want...? In-Reply-To: References: <1229918644-sup-5016@ntdws12.chass.utoronto.ca> Message-ID: <49516743.1080405@opencsw.org> Gary Law wrote: > 2008/12/22 Ben Walton > > > > Hi All, > > > Hi Ben > > I've ported Docbook to Solaris before, and getting the toolchain up and > running is a pig, so well done for volunteering to look at this. I'd go > for the lowest maintenance option that delivers a working package. Given > the 'fire and forget' principles of opencsw I'd suggest you take the 'it > just works' option of dbsgmltoolbox > failing that, go with with > the openjade dependency. I don't like the 'register if it is there' > option, it will give variable results based on what else is installed > already, which I don't like. Ben; I'm not really sure what the overall implications of the choices really mean so I'd go for what Gary proposes here and tackle the problem later on if someone has the energy to go through it. -- Trygve From trygvel at opencsw.org Tue Dec 23 23:35:35 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Tue, 23 Dec 2008 23:35:35 +0100 Subject: [csw-maintainers] SPARC issues In-Reply-To: <20081223204023.GA97070@bolthole.com> References: <495131B2.6010405@opencsw.org> <20081223193217.GJ64455@bolthole.com> <495148C9.5020703@opencsw.org> <20081223204023.GA97070@bolthole.com> Message-ID: <495167B7.4020306@opencsw.org> Philip Brown wrote: > On Tue, Dec 23, 2008 at 09:23:37PM +0100, Trygve Laugst?l wrote: >>> you arent giving enough details on what is calling as. >>> is cc calling it, or something else directly? >> ghc is calling as (perhaps through gcc, not sure) while building its >> core libs: >> > > gaaahhh... > > I suspect the most practical thing to do in this instance, is to use > the gnu compiler chain. sigh. The odd thing though is that the error message in itself is meaningful, and I'm using /usr/bin/ld on my local box (which is x86) and that work just fine. -- Trygve From bwalton at opencsw.org Wed Dec 24 14:40:16 2008 From: bwalton at opencsw.org (Ben Walton) Date: Wed, 24 Dec 2008 08:40:16 -0500 Subject: [csw-maintainers] docbook, dependencies, what do we want...? In-Reply-To: References: <1229918644-sup-5016@ntdws12.chass.utoronto.ca> Message-ID: <1230125765-sup-445@ntdws12.chass.utoronto.ca> ...here's the path I've chosen, for anyone interested (and still reading mail this time of year): 1. I dropped the openjade dependency from docbook dtds and removed all notion of openjade from the postinstall script. 2. I'm planning to bundle up the docbook dsssl stylesheets in the new year. This package will depend on both openjade and docbook dtds. It will register the docbook dtd catalogs with openjade, as this is the point where all of the pieces become useful together. The dependencies here are pretty clean cut, so this should be a nicer solution overall. :) -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From phil at bolthole.com Sat Dec 27 18:05:45 2008 From: phil at bolthole.com (Philip Brown) Date: Sat, 27 Dec 2008 09:05:45 -0800 Subject: [csw-maintainers] vacation for a few days Message-ID: <20081227170544.GA39007@bolthole.com> fyi; I'm off on vacataion for a few days. if there are any "emergency" pacakge releases that come up, James can sign the catalog also. meanwhile, merry Christmas and a happy new Year to all ;-) From ihsan at opencsw.org Sun Dec 28 17:48:32 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Sun, 28 Dec 2008 17:48:32 +0100 Subject: [csw-maintainers] new gnupg package in testing Message-ID: <4957ADE0.3060503@opencsw.org> http://mirror.opencsw.org/testing/gnupg-1.4.9,REV=2008.12.28-SunOS5.8-i386-CSW.pkg.gz http://mirror.opencsw.org/testing/gnupg-1.4.9,REV=2008.12.28-SunOS5.8-sparc-CSW.pkg.gz -- ihsan at dogan.ch http://blog.dogan.ch/ From jgoerzen at opencsw.org Wed Dec 31 00:34:55 2008 From: jgoerzen at opencsw.org (Jake Goerzen) Date: Tue, 30 Dec 2008 15:34:55 -0800 Subject: [csw-maintainers] retiring Message-ID: <315c02ae0812301534u7dbca8f0je052d3151fb13ece@mail.gmail.com> Hello All, I have decided to retire from being a package maintainer. The following packages in /testing are my last work. Feel free to include those into unstable: http://mirror.opencsw.org/testing/freeciv-2.1.8,REV=2008.12.22-SunOS5.8-i386-CSW.pkg.gz http://mirror.opencsw.org/testing/freeciv-2.1.8,REV=2008.12.22-SunOS5.8-sparc-CSW.pkg.gz http://mirror.opencsw.org/testing/wesnoth-1.4.7,REV=2008.12.22-SunOS5.8-i386-CSW.pkg.gz http://mirror.opencsw.org/testing/wesnoth-1.4.7,REV=2008.12.22-SunOS5.8-sparc-CSW.pkg.gz Best wishes to you all Sincerely, Jake Goerzen -------------- next part -------------- An HTML attachment was scrubbed... URL: From bwalton at opencsw.org Mon Dec 1 16:08:16 2008 From: bwalton at opencsw.org (Ben Walton) Date: Mon, 01 Dec 2008 10:08:16 -0500 Subject: [csw-maintainers] multiple sources, multiple urls? Message-ID: <1228143959-sup-746@ntdws12.chass.utoronto.ca> Hi All, I'll bang away on this myself, but in true 'lazyweb' fashion, I'll ask for advice also. What is the best way to handle GAR description for a package that requires multiple source files from multiple (different) locations? ...Do I just reference all of the required locations in MASTER_SITES and then put the different files in DISTFILES and have wget stumble across the required combos the first time (until they're GARchived)? Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From dam at opencsw.org Mon Dec 1 16:14:19 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 1 Dec 2008 16:14:19 +0100 Subject: [csw-maintainers] multiple sources, multiple urls? In-Reply-To: <1228143959-sup-746@ntdws12.chass.utoronto.ca> References: <1228143959-sup-746@ntdws12.chass.utoronto.ca> Message-ID: <61827A2B-2173-42F9-B565-93BD58CDD244@opencsw.org> Hi Ben, Am 01.12.2008 um 16:08 schrieb Ben Walton: > I'll bang away on this myself, but in true 'lazyweb' fashion, I'll ask > for advice also. What is the best way to handle GAR description for a > package that requires multiple source files from multiple (different) > locations? > > ...Do I just reference all of the required locations in MASTER_SITES > and then put the different files in DISTFILES and have wget stumble > across the required combos the first time (until they're GARchived)? Yes, currently that's the way to go. Better ideas welcome! Best regards -- Dago From skayser at opencsw.org Mon Dec 1 16:35:31 2008 From: skayser at opencsw.org (Sebastian Kayser) Date: Mon, 01 Dec 2008 16:35:31 +0100 Subject: [csw-maintainers] mGAR: UNCOMMITED in PSTAMP field? Message-ID: <49340443.1080807@opencsw.org> Hi, when using mGAR, what's the magic procedure to make the "UNCOMMITED" in the package PSTAMP field go away? Even when i commit all my package files, then checkout a pristine working copy and rebuild the package, the UNCOMMITED doesn't go away. 1) svn co https://gar.svn.sf.net/svnroot/gar/csw/mgar/pkg/synergy 2) cd synergy/trunk 3) gmake package 4) pkginfo has PSTAMP: skayser at build8x-r2401UNCOMMITTED-20081201153621 When i try to follow what is going on inside gar/gar.pkg.mk i see # Case 3+4: The directory belongs to a repository ifneq ($(shell $(SVN) status 2>/dev/null),) # Case 3: Not everything was committed properly _SVN_UNCOMMITTED = UNCOMMITTED endif And doing the "svn status" manually i get: ~/mgar/synergy/trunk$ svn status X gar Performing status on external item at 'gar' ~/mgar/synergy/trunk$ Do i have to do things differently? Sebastian From dam at opencsw.org Mon Dec 1 16:48:12 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 1 Dec 2008 16:48:12 +0100 Subject: [csw-maintainers] mGAR: UNCOMMITED in PSTAMP field? In-Reply-To: <49340443.1080807@opencsw.org> References: <49340443.1080807@opencsw.org> Message-ID: <417F236E-5CA8-4E70-8E33-C4DC69A7362D@opencsw.org> Hi Sebastian, Am 01.12.2008 um 16:35 schrieb Sebastian Kayser: > when using mGAR, what's the magic procedure to make the "UNCOMMITED" > in > the package PSTAMP field go away? 'svn status' must not show anything. That means you must add and commit all files to be in the repository and ignore or remove all the rest. The idea is to show that there may be stuff which avoids reproducing the package by checking out the indicated revision. > Even when i commit all my package files, then checkout a pristine > working copy and rebuild the package, the UNCOMMITED doesn't go away. > > 1) svn co https://gar.svn.sf.net/svnroot/gar/csw/mgar/pkg/synergy > 2) cd synergy/trunk > 3) gmake package > 4) pkginfo has > PSTAMP: skayser at build8x-r2401UNCOMMITTED-20081201153621 > > When i try to follow what is going on inside gar/gar.pkg.mk i see > > # Case 3+4: The directory belongs to a repository > ifneq ($(shell $(SVN) status 2>/dev/null),) > # Case 3: Not everything was committed properly > _SVN_UNCOMMITTED = UNCOMMITTED > endif > > And doing the "svn status" manually i get: > > ~/mgar/synergy/trunk$ svn status > X gar > > Performing status on external item at 'gar' > ~/mgar/synergy/trunk$ > > Do i have to do things differently? No. This is an error made by me during the transition to mGAR. The external reference should be ignored. However, just adding --ignore-externals doesn't fix this. I'll look into this. Thanks for pointing this out. Best regards -- Dago PS: I still have your list of questions here, I'll answer them soon. From phil at bolthole.com Mon Dec 1 17:17:29 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 1 Dec 2008 08:17:29 -0800 Subject: [csw-maintainers] mGAR: UNCOMMITED in PSTAMP field? In-Reply-To: <417F236E-5CA8-4E70-8E33-C4DC69A7362D@opencsw.org>; from dam@opencsw.org on Mon, Dec 01, 2008 at 04:48:12PM +0100 References: <49340443.1080807@opencsw.org> <417F236E-5CA8-4E70-8E33-C4DC69A7362D@opencsw.org> Message-ID: <20081201081729.A19866@bolthole.com> On Mon, Dec 01, 2008 at 04:48:12PM +0100, Dagobert Michelsen wrote: > Hi Sebastian, > > Am 01.12.2008 um 16:35 schrieb Sebastian Kayser: > > when using mGAR, what's the magic procedure to make the "UNCOMMITED" > > in > > the package PSTAMP field go away? > > 'svn status' must not show anything. That means you must add > and commit all files to be in the repository and ignore or remove > all the rest. The idea is to show that there may be stuff which > avoids reproducing the package by checking out the indicated > revision. > Seems appropriate for another little nudge for, "Hey, it would be really nice to have some kind of CSW wrapper that does all the svn stuff for you, rather than having to manually track that stuff down, and manually check it in blah blah..." :-} From skayser at opencsw.org Mon Dec 1 19:09:19 2008 From: skayser at opencsw.org (Sebastian Kayser) Date: Mon, 01 Dec 2008 19:09:19 +0100 Subject: [csw-maintainers] mGAR: UNCOMMITED in PSTAMP field? In-Reply-To: <20081201081729.A19866@bolthole.com> References: <49340443.1080807@opencsw.org> <417F236E-5CA8-4E70-8E33-C4DC69A7362D@opencsw.org> <20081201081729.A19866@bolthole.com> Message-ID: <4934284F.6090005@opencsw.org> Philip Brown wrote: > Seems appropriate for another little nudge for, "Hey, it would be really > nice to have some kind of CSW wrapper that does all the svn stuff for you, > rather than having to manually track that stuff down, and manually check it > in blah blah..." It is rather simple, but what i did to save me the "manually track that stuff down" part is a small bash function function mgar-get { svn co https://gar.svn.sf.net/svnroot/gar/csw/mgar/pkg/$1 } that i can call to check out a given package. This way i don't have to remember the SVN URL. Sebastian From phil at bolthole.com Mon Dec 1 19:16:44 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 1 Dec 2008 10:16:44 -0800 Subject: [csw-maintainers] mGAR: UNCOMMITED in PSTAMP field? In-Reply-To: <4934284F.6090005@opencsw.org>; from skayser@opencsw.org on Mon, Dec 01, 2008 at 07:09:19PM +0100 References: <49340443.1080807@opencsw.org> <417F236E-5CA8-4E70-8E33-C4DC69A7362D@opencsw.org> <20081201081729.A19866@bolthole.com> <4934284F.6090005@opencsw.org> Message-ID: <20081201101644.L19866@bolthole.com> On Mon, Dec 01, 2008 at 07:09:19PM +0100, Sebastian Kayser wrote: > Philip Brown wrote: > > Seems appropriate for another little nudge for, "Hey, it would be really > > nice to have some kind of CSW wrapper that does all the svn stuff for you, > > rather than having to manually track that stuff down, and manually check it > > in blah blah..." > > It is rather simple, but what i did to save me the "manually track that > stuff down" part is a small bash function > > function mgar-get { > svn co https://gar.svn.sf.net/svnroot/gar/csw/mgar/pkg/$1 > } > > that i can call to check out a given package. This way i don't have to > remember the SVN URL. > It's nice that you did that for you. but its kind of silly that all maintainers have to do that individually, isnt it? my point is that it would be more efficient, and nice to our maintainers, if we had some pre-written utils like that, as part of our cswutils package. (Until such time as we get some kind of standalone gar-for-csw package) (Wanna write some, Sebastian? :-) From skayser at opencsw.org Mon Dec 1 20:43:40 2008 From: skayser at opencsw.org (Sebastian Kayser) Date: Mon, 01 Dec 2008 20:43:40 +0100 Subject: [csw-maintainers] mGAR: UNCOMMITED in PSTAMP field? In-Reply-To: <20081201101644.L19866@bolthole.com> References: <49340443.1080807@opencsw.org> <417F236E-5CA8-4E70-8E33-C4DC69A7362D@opencsw.org> <20081201081729.A19866@bolthole.com> <4934284F.6090005@opencsw.org> <20081201101644.L19866@bolthole.com> Message-ID: <49343E6C.1000803@opencsw.org> Philip Brown wrote: > On Mon, Dec 01, 2008 at 07:09:19PM +0100, Sebastian Kayser wrote: >> Philip Brown wrote: >>> Seems appropriate for another little nudge for, "Hey, it would be really >>> nice to have some kind of CSW wrapper that does all the svn stuff for you, >>> rather than having to manually track that stuff down, and manually check it >>> in blah blah..." >> It is rather simple, but what i did to save me the "manually track that >> stuff down" part is a small bash function >> >> function mgar-get { >> svn co https://gar.svn.sf.net/svnroot/gar/csw/mgar/pkg/$1 >> } >> >> that i can call to check out a given package. This way i don't have to >> remember the SVN URL. >> > > It's nice that you did that for you. but its kind of silly that all > maintainers have to do that individually, isnt it? Yup :) > my point is that it would be more efficient, and nice to our maintainers, > if we had some pre-written utils like that, as part of our cswutils > package. (Until such time as we get some kind of standalone > gar-for-csw package) Fully understood. I should have added that i don't see a clever way to wrap the remaining svn commands (add, commit), yet. By "clever" i mean, in a way that actually saves work (and is somehow foolproof), rather than just giving two commands other names. So take the bash function as an idea on how to make things easier (more ideas anyone?). However, after having built and wrapped a package the traditional (export LD_*, CPP*, ./configure, make, *pkg) way and then with mGAR i feel that mGAR already is a very nice build platform. The ability alone for a new maintainer like me to see _exactly_ how others package their software is just great. So right now, after just getting starting, i don't really mind the couple of svn commands. :) > (Wanna write some, Sebastian? :-) Not yet. Would like to get my packages on the way first. Maybe the others have some input on this in the meantime. Sebastian From dam at opencsw.org Tue Dec 2 13:16:03 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 2 Dec 2008 13:16:03 +0100 Subject: [csw-maintainers] mGAR: UNCOMMITED in PSTAMP field? In-Reply-To: <49343E6C.1000803@opencsw.org> References: <49340443.1080807@opencsw.org> <417F236E-5CA8-4E70-8E33-C4DC69A7362D@opencsw.org> <20081201081729.A19866@bolthole.com> <4934284F.6090005@opencsw.org> <20081201101644.L19866@bolthole.com> <49343E6C.1000803@opencsw.org> Message-ID: <4EFAB965-4EC6-44FC-99D3-2D7D520AEBB6@opencsw.org> Hi, Am 01.12.2008 um 20:43 schrieb Sebastian Kayser: > Fully understood. I should have added that i don't see a clever way to > wrap the remaining svn commands (add, commit), yet. By "clever" i > mean, > in a way that actually saves work (and is somehow foolproof), rather > than just giving two commands other names. ... > So right now, after just getting starting, i don't really mind the > couple of svn commands. :) These are exactly the two reasons I see against doing it right now. We may see clearer when doing source packages and upstream delivery. Best regards -- Dago From dam at opencsw.org Tue Dec 2 13:23:15 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 2 Dec 2008 13:23:15 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> Message-ID: <8671613E-32CE-462C-9775-FD648520023B@opencsw.org> Hi, Am 29.11.2008 um 22:06 schrieb Dagobert Michelsen: > Am 29.11.2008 um 18:16 schrieb Trygve Laugst?l: >>> As you can see the packages are put in /local/hudson/gar/pkgs. >>> What I >>> would like to do now is to get Hudson to put all of those packages >>> to a >>> NFS share, run a job to create a catalog and then export that to our >>> consumers. > > Good idea! Linked to > Old packages are piling up there. Should all but the latest be deleted? Should the catalog list multiple versions like the SunFreeware catalog? Currently the catalog lists the oldest :-( Best regards -- Dago From bonivart at opencsw.org Tue Dec 2 14:01:54 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Tue, 2 Dec 2008 14:01:54 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <8671613E-32CE-462C-9775-FD648520023B@opencsw.org> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> <8671613E-32CE-462C-9775-FD648520023B@opencsw.org> Message-ID: <625385e30812020501u16197f2ud8ae7d78e3376454@mail.gmail.com> On Tue, Dec 2, 2008 at 1:23 PM, Dagobert Michelsen wrote: > Old packages are piling up there. Should all but the latest > be deleted? Should the catalog list multiple versions like > the SunFreeware catalog? Currently the catalog lists the > oldest :-( Wouldn't a simple solution be to remove all but the latest? That way the catalogs would be clean and the tools would work. -- /peter From dam at opencsw.org Tue Dec 2 18:24:48 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 2 Dec 2008 18:24:48 +0100 Subject: [csw-maintainers] Legacy GAR is now gone Message-ID: Hi, I just deleted the old trunk/, tags/ and branches/joyent/. If you still need anything please either use the web repository browser with or pull in old versions of your files with svn cp -r 2437 https://gar.svn.sf.net/svnroot/gar/csw/trunk/... (Revision 2437 was the last before the first deletion) Best regards and have fun with mGAR -- Dago From dam at opencsw.org Wed Dec 3 11:19:30 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 3 Dec 2008 11:19:30 +0100 Subject: [csw-maintainers] Addition to pkginfo for repository path Message-ID: <9138C0C6-B98D-437A-8D00-B923611474FD@opencsw.org> Hi, this has been discusses earlier, but I want to take up the thread again: IMHO it would be very useful to have a separate field in the pkginfo(4) of each package pointing to the exact repository path and version, e. g. CSW_REPOSITORY=https://gar.svn.sf.net/svnroot/gar/csw/mgar/pkg/autoconf/trunk at 2451 As packages will be build from multiple destinations with hudson this exact association will help in tracking bugs in specific versions. Feedback as always welcome. Best regards -- Dago From skayser at opencsw.org Wed Dec 3 13:36:09 2008 From: skayser at opencsw.org (Sebastian Kayser) Date: Wed, 03 Dec 2008 13:36:09 +0100 Subject: [csw-maintainers] Proper way to adopt / work on packages? Message-ID: <49367D39.1050704@opencsw.org> Hi, i am currently having a look at packages that are maintained by retired maintainers in order to adopt some of them. When i started working on pv [1] yesterday a question came to my mind: How do i know that no one else is putting effort in getting the same package up to date? I would like to avoid duplicated work. This goes along with another question: When should i commit package changes? I updated the pv build files and built the x86 package just fine. Then i committed the changes to SVN just to run into an upstream bug that shows up on SPARC only (working on it). What's the preferred way: Commit early so that ongoing work is visible to others? Or commit only after everything builds fine? Sebastian [1] http://opencsw.org/packages/pv From dam at opencsw.org Wed Dec 3 13:48:01 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 3 Dec 2008 13:48:01 +0100 Subject: [csw-maintainers] Proper way to adopt / work on packages? In-Reply-To: <49367D39.1050704@opencsw.org> References: <49367D39.1050704@opencsw.org> Message-ID: Hi Sebastian, Am 03.12.2008 um 13:36 schrieb Sebastian Kayser: > i am currently having a look at packages that are maintained by > retired > maintainers in order to adopt some of them. When i started working > on pv > [1] yesterday a question came to my mind: > > How do i know that no one else is putting effort in getting the same > package up to date? I would like to avoid duplicated work. You can post on maintainers@ and announce that you will take it over and start working on it. > This goes along with another question: When should i commit package > changes? I updated the pv build files and built the x86 package just > fine. Then i committed the changes to SVN just to run into an upstream > bug that shows up on SPARC only (working on it). > > What's the preferred way: Commit early so that ongoing work is visible > to others? Or commit only after everything builds fine? Commit early, commit often. An unfinished package description is better than no package description. Even when you don't finish it another maintainer may pick up your work later and continue with what you already did. Best regards -- Dago From dam at opencsw.org Wed Dec 3 13:49:34 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 3 Dec 2008 13:49:34 +0100 Subject: [csw-maintainers] mGAR: UNCOMMITED in PSTAMP field? In-Reply-To: <49340443.1080807@opencsw.org> References: <49340443.1080807@opencsw.org> Message-ID: <9FB489AE-960A-416B-916A-8F415612F520@opencsw.org> Hi Sebastian, Am 01.12.2008 um 16:35 schrieb Sebastian Kayser: > when using mGAR, what's the magic procedure to make the "UNCOMMITED" > in > the package PSTAMP field go away? > > Even when i commit all my package files, then checkout a pristine > working copy and rebuild the package, the UNCOMMITED doesn't go away. This issues should be fixed in mGAR v1 [2453]: Please test and let me know if you encounter any other issues. Best regards -- Dago From bwalton at opencsw.org Wed Dec 3 15:13:58 2008 From: bwalton at opencsw.org (Ben Walton) Date: Wed, 03 Dec 2008 09:13:58 -0500 Subject: [csw-maintainers] Addition to pkginfo for repository path In-Reply-To: <9138C0C6-B98D-437A-8D00-B923611474FD@opencsw.org> References: <9138C0C6-B98D-437A-8D00-B923611474FD@opencsw.org> Message-ID: <1228313513-sup-2912@ntdws12.chass.utoronto.ca> Excerpts from Dagobert Michelsen's message of Wed Dec 03 05:19:30 -0500 2008: Hi Dago, > CSW_REPOSITORY=https://gar.svn.sf.net/svnroot/gar/csw/mgar/pkg/autoconf/trunk at 2451 As long as this is automated, I'm all for it. If it requires any manual upkeep (eg: the revision id) on the part of the maintainer, it will quickly fall into disrepair[1], I feel. -Ben [1]: Mostly due to our wetware bugs, not intentional neglect. -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From phil at bolthole.com Wed Dec 3 15:51:13 2008 From: phil at bolthole.com (Philip Brown) Date: Wed, 3 Dec 2008 06:51:13 -0800 Subject: [csw-maintainers] Addition to pkginfo for repository path In-Reply-To: <9138C0C6-B98D-437A-8D00-B923611474FD@opencsw.org> References: <9138C0C6-B98D-437A-8D00-B923611474FD@opencsw.org> Message-ID: <20081203145113.GA60066@bolthole.com> On Wed, Dec 03, 2008 at 11:19:30AM +0100, Dagobert Michelsen wrote: > Hi, > > this has been discusses earlier, but I want to take up > the thread again: > IMHO it would be very useful to have a separate field in the > pkginfo(4) of each package pointing to the exact repository > path and version, useful for what additional purpose? seems to me that we already potentially have this information now, with the combination of: 1. modular gar, now makes it easy to automatically determine where in the tree a package comes from: (csw/mgar/pkg/{softwarename}) 2. the PSTAMP is supposed to automatically get the version information now already. So, this "additional information" field, would seem to me to be redundant information? From dam at opencsw.org Wed Dec 3 16:53:49 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 3 Dec 2008 16:53:49 +0100 Subject: [csw-maintainers] Addition to pkginfo for repository path In-Reply-To: <20081203145113.GA60066@bolthole.com> References: <9138C0C6-B98D-437A-8D00-B923611474FD@opencsw.org> <20081203145113.GA60066@bolthole.com> Message-ID: Hi Phil, Am 03.12.2008 um 15:51 schrieb Philip Brown: > useful for what additional purpose? To make clear from what location in the repository the package was built. > seems to me that we already potentially have this information now, > with the > combination of: > > 1. modular gar, now makes it easy to automatically determine where > in the tree a package comes from: > > (csw/mgar/pkg/{softwarename}) Partly. The location is csw/mgar/pkg/(cpan/|xfce/)?(trunk|tags/|branches/ 2. the PSTAMP is supposed to automatically get the version > information now > already. The revision, yes, but not the path. > So, this "additional information" field, would seem to me to be > redundant > information? As you see it is not. We may take out the revision from the PSTAMP and include CSW_REPOSITORY as it is a superset. Best regards -- Dago From phil at bolthole.com Wed Dec 3 18:10:30 2008 From: phil at bolthole.com (Philip Brown) Date: Wed, 3 Dec 2008 09:10:30 -0800 Subject: [csw-maintainers] Addition to pkginfo for repository path In-Reply-To: ; from dam@opencsw.org on Wed, Dec 03, 2008 at 04:53:49PM +0100 References: <9138C0C6-B98D-437A-8D00-B923611474FD@opencsw.org> <20081203145113.GA60066@bolthole.com> Message-ID: <20081203091030.A16758@bolthole.com> On Wed, Dec 03, 2008 at 04:53:49PM +0100, Dagobert Michelsen wrote: > > 1. modular gar, now makes it easy to automatically determine where > > in the tree a package comes from: > > > > (csw/mgar/pkg/{softwarename}) > > Partly. The location is > csw/mgar/pkg/(cpan/|xfce/)?(trunk|tags/|branches/ References: <9138C0C6-B98D-437A-8D00-B923611474FD@opencsw.org> <20081203145113.GA60066@bolthole.com> <20081203091030.A16758@bolthole.com> Message-ID: <51900830-E913-4814-82B1-E93E2B6CEF7E@opencsw.org> Hi Phil, Am 03.12.2008 um 18:10 schrieb Philip Brown: > On Wed, Dec 03, 2008 at 04:53:49PM +0100, Dagobert Michelsen wrote: >>> 1. modular gar, now makes it easy to automatically determine where >>> in the tree a package comes from: >>> >>> (csw/mgar/pkg/{softwarename}) >> >> Partly. The location is >> csw/mgar/pkg/(cpan/|xfce/)?(trunk|tags/|branches/ > Hmmmm... Intersting about the branches stuff. > That would make sense to have that info in there then. > Although seems like the "cpan/xfce" xstuff needs to be ...erm, what > is the > database term... "fully normalized"? :-) > ie: no subdirs: we need to have a 100% flat, uniform namespace for > nice clean auto-building, rather than 95%. I am unsure about this one. A normalized view is nice, but not with >700 entries. Subdirs may help here, but cpan/ alone has >380 entries. Trygve, from a Hudson point-of-view, do you have a preference for repository layout? Best regards -- Dago From dam at opencsw.org Wed Dec 3 20:26:09 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 3 Dec 2008 20:26:09 +0100 Subject: [csw-maintainers] Addition to pkginfo for repository path In-Reply-To: <1228313513-sup-2912@ntdws12.chass.utoronto.ca> References: <9138C0C6-B98D-437A-8D00-B923611474FD@opencsw.org> <1228313513-sup-2912@ntdws12.chass.utoronto.ca> Message-ID: <71BD2CAD-6283-4BCA-AF9F-697A4BEEDBF0@opencsw.org> Hi Ben, Am 03.12.2008 um 15:13 schrieb Ben Walton: > Excerpts from Dagobert Michelsen's message of Wed Dec 03 05:19:30 > -0500 2008: >> CSW_REPOSITORY=https://gar.svn.sf.net/svnroot/gar/csw/mgar/pkg/autoconf/trunk at 2451 > > As long as this is automated, I'm all for it. If it requires any > manual upkeep (eg: the revision id) on the part of the maintainer, it > will quickly fall into disrepair[1], I feel. Of course it will be included fully automated as it is now with PSTAMP :-) Best regards -- Dago From phil at bolthole.com Wed Dec 3 20:35:14 2008 From: phil at bolthole.com (Philip Brown) Date: Wed, 3 Dec 2008 11:35:14 -0800 Subject: [csw-maintainers] Addition to pkginfo for repository path In-Reply-To: <51900830-E913-4814-82B1-E93E2B6CEF7E@opencsw.org>; from dam@opencsw.org on Wed, Dec 03, 2008 at 08:22:29PM +0100 References: <9138C0C6-B98D-437A-8D00-B923611474FD@opencsw.org> <20081203145113.GA60066@bolthole.com> <20081203091030.A16758@bolthole.com> <51900830-E913-4814-82B1-E93E2B6CEF7E@opencsw.org> Message-ID: <20081203113514.F16758@bolthole.com> On Wed, Dec 03, 2008 at 08:22:29PM +0100, Dagobert Michelsen wrote: > I am unsure about this one. A normalized view is nice, but not > with >700 entries. Subdirs may help here, but cpan/ alone has > >380 entries. That is exactly why I suggested a few weeks ago, that you relayout to have {top}/{firstalpha}/software [eg: {top}/a/amanda/] instead of {top}/software because it would be more scalable over the long term, while still remaining consistant. You said at the time, "well, we can always redo later". Is "later" here now? ;-) From bwalton at opencsw.org Wed Dec 3 20:41:03 2008 From: bwalton at opencsw.org (Ben Walton) Date: Wed, 03 Dec 2008 14:41:03 -0500 Subject: [csw-maintainers] Addition to pkginfo for repository path In-Reply-To: <20081203113514.F16758@bolthole.com> References: <9138C0C6-B98D-437A-8D00-B923611474FD@opencsw.org> <20081203145113.GA60066@bolthole.com> <20081203091030.A16758@bolthole.com> <51900830-E913-4814-82B1-E93E2B6CEF7E@opencsw.org> <20081203113514.F16758@bolthole.com> Message-ID: <1228333178-sup-161@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Wed Dec 03 14:35:14 -0500 2008: > {top}/{firstalpha}/software > [eg: {top}/a/amanda/] If a reorg is going to happen, this gets a +1 from me. It would be nicer down the road... -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 235 bytes Desc: not available URL: From william at wbonnet.net Wed Dec 3 21:13:20 2008 From: william at wbonnet.net (William Bonnet) Date: Wed, 03 Dec 2008 21:13:20 +0100 Subject: [csw-maintainers] Addition to pkginfo for repository path In-Reply-To: <20081203113514.F16758@bolthole.com> References: <9138C0C6-B98D-437A-8D00-B923611474FD@opencsw.org> <20081203145113.GA60066@bolthole.com> <20081203091030.A16758@bolthole.com> <51900830-E913-4814-82B1-E93E2B6CEF7E@opencsw.org> <20081203113514.F16758@bolthole.com> Message-ID: <4936E860.40905@wbonnet.net> Hi > That is exactly why I suggested a few weeks ago, that you relayout > to have > > {top}/{firstalpha}/software > [eg: {top}/a/amanda/] > > instead of > > {top}/software > > because it would be more scalable over the long term, while still remaining > consistant. > This sounds good. Having a few hundred softwave at the same level is not really a good thing. > Is "later" here now? ;-) > The sooner the better :) We need to stabilize the gar tree Cheers -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.blastwave.org An OpenSolaris Community Site http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From trygvel at opencsw.org Wed Dec 3 21:29:33 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Wed, 03 Dec 2008 21:29:33 +0100 Subject: [csw-maintainers] Addition to pkginfo for repository path In-Reply-To: <51900830-E913-4814-82B1-E93E2B6CEF7E@opencsw.org> References: <9138C0C6-B98D-437A-8D00-B923611474FD@opencsw.org> <20081203145113.GA60066@bolthole.com> <20081203091030.A16758@bolthole.com> <51900830-E913-4814-82B1-E93E2B6CEF7E@opencsw.org> Message-ID: <4936EC2D.40505@opencsw.org> Dagobert Michelsen wrote: > Hi Phil, > > Am 03.12.2008 um 18:10 schrieb Philip Brown: >> On Wed, Dec 03, 2008 at 04:53:49PM +0100, Dagobert Michelsen wrote: >>>> 1. modular gar, now makes it easy to automatically determine where >>>> in the tree a package comes from: >>>> >>>> (csw/mgar/pkg/{softwarename}) >>> Partly. The location is >>> csw/mgar/pkg/(cpan/|xfce/)?(trunk|tags/|branches/> Hmmmm... Intersting about the branches stuff. >> That would make sense to have that info in there then. >> Although seems like the "cpan/xfce" xstuff needs to be ...erm, what >> is the >> database term... "fully normalized"? :-) >> ie: no subdirs: we need to have a 100% flat, uniform namespace for >> nice clean auto-building, rather than 95%. > > I am unsure about this one. A normalized view is nice, but not > with >700 entries. Subdirs may help here, but cpan/ alone has > >380 entries. Trygve, from a Hudson point-of-view, do you > have a preference for repository layout? No, Hudson really don't care. You give it an url, Hudson checks it out and build it. From iand at opencsw.org Wed Dec 3 21:40:52 2008 From: iand at opencsw.org (Ian Dickinson) Date: Wed, 03 Dec 2008 20:40:52 +0000 Subject: [csw-maintainers] GAR on buildfarm? Message-ID: <4936EED4.7040708@opencsw.org> I've been quiet for a while but now I'm about to wake up again :-) First thing I'd like to do is get my existing packages sorted out and into GAR. I assume the Getting Started with GAR doc is accurate, but I'll need to do this on a build farm somewhere - is this normal/allowed/whatever? After this, I'll look at picking up an orphan or two - I still plan to do net-snmp if no-one has done it by then. Ian From trygvel at opencsw.org Wed Dec 3 21:43:55 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Wed, 03 Dec 2008 21:43:55 +0100 Subject: [csw-maintainers] Addition to pkginfo for repository path In-Reply-To: <20081203113514.F16758@bolthole.com> References: <9138C0C6-B98D-437A-8D00-B923611474FD@opencsw.org> <20081203145113.GA60066@bolthole.com> <20081203091030.A16758@bolthole.com> <51900830-E913-4814-82B1-E93E2B6CEF7E@opencsw.org> <20081203113514.F16758@bolthole.com> Message-ID: <4936EF8B.8090108@opencsw.org> Philip Brown wrote: > On Wed, Dec 03, 2008 at 08:22:29PM +0100, Dagobert Michelsen wrote: >> I am unsure about this one. A normalized view is nice, but not >> with >700 entries. Subdirs may help here, but cpan/ alone has >> >380 entries. > > That is exactly why I suggested a few weeks ago, that you relayout > to have > > {top}/{firstalpha}/software > [eg: {top}/a/amanda/] > > instead of > > {top}/software > > because it would be more scalable over the long term, while still remaining > consistant. I don't see the big problem really. Subversion doesn't have a problem handling a couple of thousand entries (as an example see [1] with 879 packages). If you want to talk organization I wouldn't mind keeping the grouping that is already as I usually wouldn't care about cpan or xfce stuff (as I don't work on either of those). It is not unlikely that other people will re-use GAR to produce packages and that day they would most likely have their own "category". I say we structure the svn repository as we see fit and move stuff as categories get to big and merge when categories get too small. What Dago proposed should be implemented in any case as that will give us the possibility to change our minds later on without the risk of loosing any valuable data. [1]: https://pkgbuild.svn.sourceforge.net/svnroot/pkgbuild/spec-files-extra/trunk/ -- Trygve From trygvel at opencsw.org Wed Dec 3 21:47:20 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Wed, 03 Dec 2008 21:47:20 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <8671613E-32CE-462C-9775-FD648520023B@opencsw.org> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> <8671613E-32CE-462C-9775-FD648520023B@opencsw.org> Message-ID: <4936F058.1070703@opencsw.org> Dagobert Michelsen wrote: > Hi, > > Am 29.11.2008 um 22:06 schrieb Dagobert Michelsen: >> Am 29.11.2008 um 18:16 schrieb Trygve Laugst?l: >>>> As you can see the packages are put in /local/hudson/gar/pkgs. >>>> What I >>>> would like to do now is to get Hudson to put all of those packages >>>> to a >>>> NFS share, run a job to create a catalog and then export that to our >>>> consumers. >> Good idea! Linked to >> > > Old packages are piling up there. Should all but the latest > be deleted? Should the catalog list multiple versions like > the SunFreeware catalog? Currently the catalog lists the > oldest :-( Overall I would consider that a bug in both pkg-get and bldcat if they don't support multiple versions. I would expect pkg-get to select the latest, but allow me to override that with an exact version if I want to. I'm quite sure that is possible today with pkg-get, except that it will always prompt me to give an exact version. bldcat should be fixed to 1) select the latest version and 2) support multiple versions in the catalog. -- Trygve From trygvel at opencsw.org Wed Dec 3 21:48:42 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Wed, 03 Dec 2008 21:48:42 +0100 Subject: [csw-maintainers] Proper way to adopt / work on packages? In-Reply-To: References: <49367D39.1050704@opencsw.org> Message-ID: <4936F0AA.1020705@opencsw.org> Dagobert Michelsen wrote: > Hi Sebastian, > > Am 03.12.2008 um 13:36 schrieb Sebastian Kayser: >> i am currently having a look at packages that are maintained by >> retired >> maintainers in order to adopt some of them. When i started working >> on pv >> [1] yesterday a question came to my mind: >> >> How do i know that no one else is putting effort in getting the same >> package up to date? I would like to avoid duplicated work. > > You can post on maintainers@ and announce that you will take it over > and start working on it. > >> This goes along with another question: When should i commit package >> changes? I updated the pv build files and built the x86 package just >> fine. Then i committed the changes to SVN just to run into an upstream >> bug that shows up on SPARC only (working on it). >> >> What's the preferred way: Commit early so that ongoing work is visible >> to others? Or commit only after everything builds fine? > > Commit early, commit often. An unfinished package description > is better than no package description. Even when you don't > finish it another maintainer may pick up your work later > and continue with what you already did. This is where Hudson come in too. If you only have platform X boxes available and the code work I would commit and then get Hudson to build the packages on the other platform. -- Trygve From phil at bolthole.com Wed Dec 3 21:54:36 2008 From: phil at bolthole.com (Philip Brown) Date: Wed, 3 Dec 2008 12:54:36 -0800 Subject: [csw-maintainers] GAR on buildfarm? In-Reply-To: <4936EED4.7040708@opencsw.org>; from iand@opencsw.org on Wed, Dec 03, 2008 at 08:40:52PM +0000 References: <4936EED4.7040708@opencsw.org> Message-ID: <20081203125436.J16758@bolthole.com> On Wed, Dec 03, 2008 at 08:40:52PM +0000, Ian Dickinson wrote: > I've been quiet for a while but now I'm about to wake up again :-) > > First thing I'd like to do is get my existing packages sorted out and into > GAR. I assume the Getting Started with GAR doc is accurate, but I'll need to > do this on a build farm somewhere - is this normal/allowed/whatever? not really "needed"... you can "work on gar" from anywhere. it's hosted at sourceforge, after all > After this, I'll look at picking up an orphan or two - I still plan to do > net-snmp if no-one has done it by then. excellent! From bonivart at opencsw.org Wed Dec 3 22:04:27 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Wed, 3 Dec 2008 22:04:27 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <4936F058.1070703@opencsw.org> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> <8671613E-32CE-462C-9775-FD648520023B@opencsw.org> <4936F058.1070703@opencsw.org> Message-ID: <625385e30812031304r7a10f24ew201679db0ae76883@mail.gmail.com> On Wed, Dec 3, 2008 at 9:47 PM, Trygve Laugst?l wrote: > bldcat should be fixed to 1) select the latest version and 2) support > multiple versions in the catalog. For me this is a much larger issue than just changing bldcat. It's key to pkgutil that every entry in the catalog is unique so that a first match is enough. To make it support multiple versions wouldn't just make it a lot more complex but also much slower since the whole catalog must be parsed every time to make sure there's not another version present later in the catalog. Since we have always only supported the latest set of packages (in current and stable) I don't see why we would give away the simplicity. Why not do the same with testing, support the latest version of each package? I have tried to implement everything any one has asked for so far but this feels wrong to me. -- /peter From william at wbonnet.net Wed Dec 3 22:04:41 2008 From: william at wbonnet.net (William Bonnet) Date: Wed, 03 Dec 2008 22:04:41 +0100 Subject: [csw-maintainers] Proper way to adopt / work on packages? In-Reply-To: References: <49367D39.1050704@opencsw.org> Message-ID: <4936F469.9030900@wbonnet.net> Hi > You can post on maintainers@ and announce that you will take it over > and start working on it. > Maybe each maintainer could write on his wiki bio page his current work and packages. Giving a list of package he is working on ? > Commit early, commit often. An unfinished package description > is better than no package description. Even when you don't > finish it another maintainer may pick up your work later > and continue with what you already did. > Yes commit early, but take care to the syntax of the makefile. It is *prefered* that target check-upstream is working. This target is used to check for available updates of software sources. Actually there is almost no public documentation about this. I'll write some after Zurich. This target is croned each night to detect availability of updates. Maintainers will be notified by email. This is currently under test, and will be activated soon. Cheers, W. -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.blastwave.org An OpenSolaris Community Site http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From dam at opencsw.org Wed Dec 3 22:29:06 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 3 Dec 2008 22:29:06 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <625385e30812031304r7a10f24ew201679db0ae76883@mail.gmail.com> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> <8671613E-32CE-462C-9775-FD648520023B@opencsw.org> <4936F058.1070703@opencsw.org> <625385e30812031304r7a10f24ew201679db0ae76883@mail.gmail.com> Message-ID: <6BD97AD6-BBD8-4ECB-B353-33767E4164F7@opencsw.org> Hi Peter, Am 03.12.2008 um 22:04 schrieb Peter Bonivart: > For me this is a much larger issue than just changing bldcat. Especially we would need versioned dependencies which we don't have and which are *really* complicated to manage. At least I don't want multiple package versions. Best regards -- Dago From dam at opencsw.org Wed Dec 3 22:36:15 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 3 Dec 2008 22:36:15 +0100 Subject: [csw-maintainers] IMPORTANT: packages on the farm are synchronized now Message-ID: <4576E653-D109-4350-AF85-61221592106B@opencsw.org> Hi, I am now synchronizing up all packages from the farm with the current versions from the catalog. I hope it will not take longer than an hour. Best regards -- Dago From skayser at opencsw.org Wed Dec 3 22:46:37 2008 From: skayser at opencsw.org (Sebastian Kayser) Date: Wed, 03 Dec 2008 22:46:37 +0100 Subject: [csw-maintainers] GAR on buildfarm? In-Reply-To: <20081203125436.J16758@bolthole.com> References: <4936EED4.7040708@opencsw.org> <20081203125436.J16758@bolthole.com> Message-ID: <4936FE3D.9080106@opencsw.org> Philip Brown wrote: > On Wed, Dec 03, 2008 at 08:40:52PM +0000, Ian Dickinson wrote: >> I've been quiet for a while but now I'm about to wake up again :-) >> >> First thing I'd like to do is get my existing packages sorted out and into >> GAR. I assume the Getting Started with GAR doc is accurate, but I'll need to >> do this on a build farm somewhere - is this normal/allowed/whatever? > > not really "needed"... you can "work on gar" from anywhere. > it's hosted at sourceforge, after all I did kind of both. I first got myself aquainted with mGAR on the build farm (all the required applications are already in place and have the proper paths) and then setup a local build environment. I still use the build farm for the final package build, though. The Getting Started Guide is what i used for setting up my local environment. To get used to mGAR i pulled bits of information from "The GAR Tutorial" and "Packaging with mGAR" mostly. Sebastian From skayser at opencsw.org Wed Dec 3 22:55:02 2008 From: skayser at opencsw.org (Sebastian Kayser) Date: Wed, 03 Dec 2008 22:55:02 +0100 Subject: [csw-maintainers] Proper way to adopt / work on packages? In-Reply-To: References: <49367D39.1050704@opencsw.org> Message-ID: <49370036.7090102@opencsw.org> Dagobert Michelsen wrote: > Am 03.12.2008 um 13:36 schrieb Sebastian Kayser: >> i am currently having a look at packages that are maintained by >> retired >> maintainers in order to adopt some of them. When i started working >> on pv >> [1] yesterday a question came to my mind: >> >> How do i know that no one else is putting effort in getting the same >> package up to date? I would like to avoid duplicated work. > > You can post on maintainers@ and announce that you will take it over > and start working on it. Ok, will do, thanks. Another question regarding the "Retired" status. What's the difference between packages managed by a retired maintainer and orphaned packages? To me it feels the same. Do we have a page like [1] that shows all the packages that are either orphaned or managed by a retired maintainer? This way new maintainers like me could just have a look at that one to find some packages to take care of. Sebastian [1] http://opencsw.org/buglist/buglist.cgi From phil at bolthole.com Wed Dec 3 23:02:02 2008 From: phil at bolthole.com (Philip Brown) Date: Wed, 3 Dec 2008 14:02:02 -0800 Subject: [csw-maintainers] Proper way to adopt / work on packages? In-Reply-To: <49370036.7090102@opencsw.org>; from skayser@opencsw.org on Wed, Dec 03, 2008 at 10:55:02PM +0100 References: <49367D39.1050704@opencsw.org> <49370036.7090102@opencsw.org> Message-ID: <20081203140202.K16758@bolthole.com> On Wed, Dec 03, 2008 at 10:55:02PM +0100, Sebastian Kayser wrote: > Do we have a page like [1] that shows all the packages that are either > orphaned or managed by a retired maintainer? This way new maintainers > like me could just have a look at that one to find some packages to take > care of. The diference between orphaned, and retired, is subtle. "retired" has a soft implication of, "the maintainer is no longer active, but might answer questions if you are nice". "orphaned" indicates "the maintainer has dropped off the planet as far as we are concerned" From dam at opencsw.org Wed Dec 3 23:04:41 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 3 Dec 2008 23:04:41 +0100 Subject: [csw-maintainers] IMPORTANT: packages on the farm are synchronized now In-Reply-To: <4576E653-D109-4350-AF85-61221592106B@opencsw.org> References: <4576E653-D109-4350-AF85-61221592106B@opencsw.org> Message-ID: Hi, Am 03.12.2008 um 22:36 schrieb Dagobert Michelsen: > I am now synchronizing up all packages from the farm with > the current versions from the catalog. I hope it will > not take longer than an hour. The fixing is over. The following downrevs have been done: build8s# pkg-get -c |egrep -v 'Not|SAME' # (From site http://mirror/opencsw/current ) software localrev remoterev dbus 1.2.4,REV=2008.11.20 1.2.1,REV=2008.06.02 dbus_glib 0.76,REV=2008.11.20 0.74,REV=2008.06.02 dbus_glibdev 0.76,REV=2008.11.20 0.74,REV=2008.06.02 libcairo 1.8.2,REV=2008.11.19 1.4.10 libdbusdev 1.2.4,REV=2008.11.20 1.2.1,REV=2008.06.02 libxrender 0.9.4,REV=2008.11.19 0.8.3,REV=2004.03.31 render_dev 0.9.4,REV=2008.11.19 0.8,REV=2004.03.30 sqlite3 3.6.4,REV=2008.11.17 3.2.2,REV=2005.07.10 build8x# pkg-get -c |egrep -v 'Not|SAME' # (From site http://mirror/opencsw/current ) software localrev remoterev dbus 1.2.4,REV=2008.11.20 1.2.1,REV=2008.06.02 dbus_glib 0.76,REV=2008.11.20 0.74,REV=2008.06.02 dbus_glibdev 0.76,REV=2008.11.20 0.74,REV=2008.06.02 libcairo 1.8.2,REV=2008.11.19 1.4.10 libdbusdev 1.2.4,REV=2008.11.20 1.2.1,REV=2008.06.02 libxrender 0.9.4,REV=2008.11.19 0.8.3,REV=2004.03.31 render_dev 0.9.4,REV=2008.11.19 0.8,REV=2004.03.30 sqlite3 3.6.4,REV=2008.11.17 3.2.2,REV=2005.07.10 Let's see that we can get them released and I'll reinstall the new versions ASAP. Best regards -- Dago From trygvis at inamo.no Wed Dec 3 21:28:58 2008 From: trygvis at inamo.no (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Wed, 03 Dec 2008 21:28:58 +0100 Subject: [csw-maintainers] Addition to pkginfo for repository path In-Reply-To: <51900830-E913-4814-82B1-E93E2B6CEF7E@opencsw.org> References: <9138C0C6-B98D-437A-8D00-B923611474FD@opencsw.org> <20081203145113.GA60066@bolthole.com> <20081203091030.A16758@bolthole.com> <51900830-E913-4814-82B1-E93E2B6CEF7E@opencsw.org> Message-ID: <4936EC0A.8060104@inamo.no> Dagobert Michelsen wrote: > Hi Phil, > > Am 03.12.2008 um 18:10 schrieb Philip Brown: >> On Wed, Dec 03, 2008 at 04:53:49PM +0100, Dagobert Michelsen wrote: >>>> 1. modular gar, now makes it easy to automatically determine where >>>> in the tree a package comes from: >>>> >>>> (csw/mgar/pkg/{softwarename}) >>> Partly. The location is >>> csw/mgar/pkg/(cpan/|xfce/)?(trunk|tags/|branches/> Hmmmm... Intersting about the branches stuff. >> That would make sense to have that info in there then. >> Although seems like the "cpan/xfce" xstuff needs to be ...erm, what >> is the >> database term... "fully normalized"? :-) >> ie: no subdirs: we need to have a 100% flat, uniform namespace for >> nice clean auto-building, rather than 95%. > > I am unsure about this one. A normalized view is nice, but not > with >700 entries. Subdirs may help here, but cpan/ alone has > >380 entries. Trygve, from a Hudson point-of-view, do you > have a preference for repository layout? No, Hudson really don't care. You give it an url, Hudson checks it out and build it. -- Trygve From skayser at opencsw.org Thu Dec 4 00:56:11 2008 From: skayser at opencsw.org (Sebastian Kayser) Date: Thu, 04 Dec 2008 00:56:11 +0100 Subject: [csw-maintainers] mGAR: UNCOMMITED in PSTAMP field? In-Reply-To: <9FB489AE-960A-416B-916A-8F415612F520@opencsw.org> References: <49340443.1080807@opencsw.org> <9FB489AE-960A-416B-916A-8F415612F520@opencsw.org> Message-ID: <49371C9B.1020301@opencsw.org> Dagobert Michelsen wrote: > Am 01.12.2008 um 16:35 schrieb Sebastian Kayser: >> when using mGAR, what's the magic procedure to make the "UNCOMMITED" >> in >> the package PSTAMP field go away? >> >> Even when i commit all my package files, then checkout a pristine >> working copy and rebuild the package, the UNCOMMITED doesn't go away. > > This issues should be fixed in mGAR v1 [2453]: Works. Thanks! Sebastian From trygvel at opencsw.org Thu Dec 4 08:35:03 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Thu, 04 Dec 2008 08:35:03 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <625385e30812031304r7a10f24ew201679db0ae76883@mail.gmail.com> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> <8671613E-32CE-462C-9775-FD648520023B@opencsw.org> <4936F058.1070703@opencsw.org> <625385e30812031304r7a10f24ew201679db0ae76883@mail.gmail.com> Message-ID: <49378827.3090008@opencsw.org> Peter Bonivart wrote: > On Wed, Dec 3, 2008 at 9:47 PM, Trygve Laugst?l wrote: >> bldcat should be fixed to 1) select the latest version and 2) support >> multiple versions in the catalog. > > For me this is a much larger issue than just changing bldcat. It's key > to pkgutil that every entry in the catalog is unique so that a first > match is enough. To make it support multiple versions wouldn't just > make it a lot more complex but also much slower since the whole > catalog must be parsed every time to make sure there's not another > version present later in the catalog. > > Since we have always only supported the latest set of packages (in > current and stable) I don't see why we would give away the simplicity. > Why not do the same with testing, support the latest version of each > package? I only want this for the automatically built packages as the quality of the packages *might* vary, thus you need to roll back to the previous build. I think that this is an important part of the development process if you actually want to get non-maintainers to test the software. If they need to do lots of manual stuff, like wget'ing a file to get the previous build, they won't do it. In particular as it is today where the previous release is removed when a new one is installed. > I have tried to implement everything any one has asked for so far but > this feels wrong to me. Don't get me wrong, pkg-get and pkgutil are very useful tools, but I do hope this new concept can be supported. This process is also something that I'm going to push for at my client as Hudson build packages on every commit and the testers need to be able to roll up and down between versions. -- Trygve From dam at opencsw.org Thu Dec 4 08:57:48 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 4 Dec 2008 08:57:48 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <49378827.3090008@opencsw.org> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> <8671613E-32CE-462C-9775-FD648520023B@opencsw.org> <4936F058.1070703@opencsw.org> <625385e30812031304r7a10f24ew201679db0ae76883@mail.gmail.com> <49378827.3090008@opencsw.org> Message-ID: <26EC0516-DB3D-4677-8DE9-20A17BD4B1A6@opencsw.org> Hi Trygve, Am 04.12.2008 um 08:35 schrieb Trygve Laugst?l: > I think that this is an important part of the development process if > you > actually want to get non-maintainers to test the software. If they > need > to do lots of manual stuff, like wget'ing a file to get the previous > build, they won't do it. In particular as it is today where the > previous > release is removed when a new one is installed. How about adding one more dimension in the catalog: time. Then mirror.opencsw.org:/opencsw/ could look like this: current/ stable/ testing/ manually build packages restructured from /home/testing hudson/ REV=2008.12.12/ sparc/ 5.8/ / - might be older That means /home/hudson/packages holds all packages build by hudson in a flat structure and then a catalog-build-script makes hudson-subdirs for each day putting the packages in it. If a package is not rebuild on that day the latest version is used. Sounds good? Best regards -- Dago From dam at opencsw.org Thu Dec 4 09:11:14 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 4 Dec 2008 09:11:14 +0100 Subject: [csw-maintainers] Proper way to adopt / work on packages? In-Reply-To: <49370036.7090102@opencsw.org> References: <49367D39.1050704@opencsw.org> <49370036.7090102@opencsw.org> Message-ID: <15B80F3A-40B6-4678-9EDD-097642EE55B9@opencsw.org> Hi Sebastian, Am 03.12.2008 um 22:55 schrieb Sebastian Kayser: > Do we have a page like [1] that shows all the packages that are either > orphaned or managed by a retired maintainer? This way new maintainers > like me could just have a look at that one to find some packages to > take > care of. Not yet. The buglist lists packages that need care. This includes critical bugs and also version upgrade requests. William is working on a system which automatically checks for version upgrades and files bugs against the package. So the buglist will become even more important as it show which packages actually need care, just to be orphaned is not really an issue for a package which has no bugs and when there is no new version for 5 years. Best regards -- Dago From trygvel at opencsw.org Thu Dec 4 09:38:12 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Thu, 04 Dec 2008 09:38:12 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <26EC0516-DB3D-4677-8DE9-20A17BD4B1A6@opencsw.org> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> <8671613E-32CE-462C-9775-FD648520023B@opencsw.org> <4936F058.1070703@opencsw.org> <625385e30812031304r7a10f24ew201679db0ae76883@mail.gmail.com> <49378827.3090008@opencsw.org> <26EC0516-DB3D-4677-8DE9-20A17BD4B1A6@opencsw.org> Message-ID: <493796F4.60003@opencsw.org> Dagobert Michelsen wrote: > Hi Trygve, > > Am 04.12.2008 um 08:35 schrieb Trygve Laugst?l: >> I think that this is an important part of the development process if >> you >> actually want to get non-maintainers to test the software. If they >> need >> to do lots of manual stuff, like wget'ing a file to get the previous >> build, they won't do it. In particular as it is today where the >> previous >> release is removed when a new one is installed. > > How about adding one more dimension in the catalog: time. Then > mirror.opencsw.org:/opencsw/ could look like this: > > current/ > stable/ > testing/ manually build packages restructured from /home/testing > hudson/ > REV=2008.12.12/ > sparc/ > 5.8/ > / - might be older > > That means /home/hudson/packages holds all packages build by hudson in a > flat structure and then a catalog-build-script makes hudson-subdirs for > each day putting the packages in it. If a package is not rebuild on that > day the latest version is used. Sounds good? What is the gain? The package tools already have a strong concept of versions, why not support multiple versions at the same time? I'm all for backwards compatibility and all, but I really need a feature like this so I don't mind running my tools with a special flag (might be nice anyway as it indicates that I'm running development stuff). -- Trygve From phil at bolthole.com Thu Dec 4 18:13:19 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 4 Dec 2008 09:13:19 -0800 Subject: [csw-maintainers] Hudson In-Reply-To: <493796F4.60003@opencsw.org>; from trygvel@opencsw.org on Thu, Dec 04, 2008 at 09:38:12AM +0100 References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> <8671613E-32CE-462C-9775-FD648520023B@opencsw.org> <4936F058.1070703@opencsw.org> <625385e30812031304r7a10f24ew201679db0ae76883@mail.gmail.com> <49378827.3090008@opencsw.org> <26EC0516-DB3D-4677-8DE9-20A17BD4B1A6@opencsw.org> <493796F4.60003@opencsw.org> Message-ID: <20081204091318.T16758@bolthole.com> On Thu, Dec 04, 2008 at 09:38:12AM +0100, Trygve Laugst?l wrote: > What is the gain? The package tools already have a strong concept of > versions, why not support multiple versions at the same time? I'm all > for backwards compatibility and all, but I really need a feature like > this so I don't mind running my tools with a special flag (might be nice > anyway as it indicates that I'm running development stuff). Two things, just to hopefully bring people together on the same page: 1. no-one is proposing that our REGULAR trees (current, stable) have multiple versions. Just wanted to mention that as reassurance to some folks :-) 2. pkg-get already supports multiple versions to some degree. As mentioned previously, i believe it will prompt you for which one you want, though. As someone will probably not be initially aware that there even EXIST multiple versions (since normally, a big point of pkg-get is to INSULATE users from versions), I think that prompting is an important safty check. I might add an OPTION flag to pkg-get, to say "always pick latest", but I think the default behaviour will stay as "prompt if multiple versions" From Darin.Perusich at cognigencorp.com Thu Dec 4 18:28:18 2008 From: Darin.Perusich at cognigencorp.com (Darin Perusich) Date: Thu, 04 Dec 2008 12:28:18 -0500 Subject: [csw-maintainers] old blastwave home dirs Message-ID: <49381332.1000800@cognigencorp.com> Do we still have access to the blastwave home directories? I'd like to be able to get at all my old docs and crap. -- Darin Perusich Unix Systems Administrator Cognigen Corporation 395 Youngs Rd. Williamsville, NY 14221 Phone: 716-633-3463 Email: darinper at cognigencorp.com From phil at bolthole.com Thu Dec 4 18:36:21 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 4 Dec 2008 09:36:21 -0800 Subject: [csw-maintainers] old blastwave home dirs In-Reply-To: <49381332.1000800@cognigencorp.com>; from Darin.Perusich@cognigencorp.com on Thu, Dec 04, 2008 at 12:28:18PM -0500 References: <49381332.1000800@cognigencorp.com> Message-ID: <20081204093621.V16758@bolthole.com> On Thu, Dec 04, 2008 at 12:28:18PM -0500, Darin Perusich wrote: > Do we still have access to the blastwave home directories? I'd like to > be able to get at all my old docs and crap. > I'd say, after all Dennis's public slander about us "stealing" stuff, you should ask him for it. and if he refuses, publically call him out about him "stealing" stuff that is rightfully YOUR property. Even if he claims he has deleted it(which I doubt), he still has backups. From bwalton at opencsw.org Thu Dec 4 19:28:12 2008 From: bwalton at opencsw.org (Ben Walton) Date: Thu, 04 Dec 2008 13:28:12 -0500 Subject: [csw-maintainers] relatocatable packages and package scripts Message-ID: <1228414352-sup-4045@ntdws12.chass.utoronto.ca> Hi All, For the openjade project, I need to write a postinstall/preremove script pair to register/unregister the installed catalogs, using scripts provided by the sgmlcommon package. The install-catalog script creates an new file in /opt/csw/etc/sgml based on parameters passed in and then adds an entry to /opt/csw/etc/sgml/catalog to reference this new file. How would one handle PKG_INSTALL_ROOT in the face of something like this where the dependent script is unaware of the altered root environment? Do you simply do a case check against PKG_INSTALL_ROOT and alert the user to run the commands manually when the new environment is booted if the root isn't / or ''? Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From phil at bolthole.com Thu Dec 4 19:38:22 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 4 Dec 2008 10:38:22 -0800 Subject: [csw-maintainers] relatocatable packages and package scripts In-Reply-To: <1228414352-sup-4045@ntdws12.chass.utoronto.ca>; from bwalton@opencsw.org on Thu, Dec 04, 2008 at 01:28:12PM -0500 References: <1228414352-sup-4045@ntdws12.chass.utoronto.ca> Message-ID: <20081204103822.W16758@bolthole.com> On Thu, Dec 04, 2008 at 01:28:12PM -0500, Ben Walton wrote: > Hi All, > > For the openjade project, I need to write a postinstall/preremove > script pair to register/unregister the installed catalogs, using > scripts provided by the sgmlcommon package. The install-catalog > script creates an new file in /opt/csw/etc/sgml based on parameters > passed in and then adds an entry to /opt/csw/etc/sgml/catalog to > reference this new file. ok.... > > How would one handle PKG_INSTALL_ROOT in the face of something like > this where the dependent script is unaware of the altered root > environment? chroot $PKG_INSTALL_ROOT run/script/here From phil at bolthole.com Thu Dec 4 19:40:02 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 4 Dec 2008 10:40:02 -0800 Subject: [csw-maintainers] relatocatable packages and package scripts In-Reply-To: <1228414352-sup-4045@ntdws12.chass.utoronto.ca>; from bwalton@opencsw.org on Thu, Dec 04, 2008 at 01:28:12PM -0500 References: <1228414352-sup-4045@ntdws12.chass.utoronto.ca> Message-ID: <20081204104002.X16758@bolthole.com> Oh, fyi: for "relocatable packages" (ie: where you have a "BASEDIR" set) i believe that PKG_INSTALL_ROOT automatically gets $BASEDIR appended to it. Or, maybe it was that BASEDIR automatically gets PKG_INSTALL_ROOT prepended to it. somethin like that. So be extra careful. but it's doable. From bwalton at opencsw.org Thu Dec 4 19:47:19 2008 From: bwalton at opencsw.org (Ben Walton) Date: Thu, 04 Dec 2008 13:47:19 -0500 Subject: [csw-maintainers] relatocatable packages and package scripts In-Reply-To: <20081204103822.W16758@bolthole.com> References: <1228414352-sup-4045@ntdws12.chass.utoronto.ca> <20081204103822.W16758@bolthole.com> Message-ID: <1228416302-sup-1584@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Thu Dec 04 13:38:22 -0500 2008: > > How would one handle PKG_INSTALL_ROOT in the face of something like > > this where the dependent script is unaware of the altered root > > environment? > > chroot $PKG_INSTALL_ROOT run/script/here Ok, had considered that and dismissed it for some reason...I'll reread the BASEDIR vs PKG_INSTALL_ROOT documentation again. Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From bwalton at opencsw.org Thu Dec 4 20:59:29 2008 From: bwalton at opencsw.org (Ben Walton) Date: Thu, 04 Dec 2008 14:59:29 -0500 Subject: [csw-maintainers] relatocatable packages and package scripts In-Reply-To: <20081204104002.X16758@bolthole.com> References: <1228414352-sup-4045@ntdws12.chass.utoronto.ca> <20081204104002.X16758@bolthole.com> Message-ID: <1228420336-sup-4801@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Thu Dec 04 13:40:02 -0500 2008: > Oh, fyi: for "relocatable packages" > (ie: where you have a "BASEDIR" set) Ok, I had confused the terminology in my head. I was thinking that -R was relocatable, but that's not the proper Sun-blessed term for this. I'm not overriding BASEDIR, and it seems that GAR leaves it unset, (which sees it recorded in the post-install pkginfo as /). This seems sensible to me, as throwing relocation into the mix for many things would be in the 'cruel and unusual' category (eg: we've gone to great length to get paths into files through autoconf, etc...corrections to this thinking are welcome, of course). Are we ok to support PKG_INSTALL_ROOT and not worry about BASEDIR then, as far as CSW is concerned? > i believe that PKG_INSTALL_ROOT automatically gets $BASEDIR appended > to it. This is correct. Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From phil at bolthole.com Thu Dec 4 21:38:20 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 4 Dec 2008 12:38:20 -0800 Subject: [csw-maintainers] relatocatable packages and package scripts In-Reply-To: <1228420336-sup-4801@ntdws12.chass.utoronto.ca>; from bwalton@opencsw.org on Thu, Dec 04, 2008 at 02:59:29PM -0500 References: <1228414352-sup-4045@ntdws12.chass.utoronto.ca> <20081204104002.X16758@bolthole.com> <1228420336-sup-4801@ntdws12.chass.utoronto.ca> Message-ID: <20081204123820.C16758@bolthole.com> On Thu, Dec 04, 2008 at 02:59:29PM -0500, Ben Walton wrote: > > Ok, I had confused the terminology in my head. I was thinking that -R > was relocatable, but that's not the proper Sun-blessed term for > this. nope. seems like you are talking about "how do I handle a NON-RELOCATABLE (ie: not using BASEDIR) package, being called with 'pkgadd -R /some/thing mypkg' ?" > Are we ok to support PKG_INSTALL_ROOT and not worry about BASEDIR > then, as far as CSW is concerned? If your package doesnt use BASEDIR normally, then you dont have to worry about it. See other packages with postinstall scripts for more specific examples if you like. From bwalton at opencsw.org Thu Dec 4 21:44:41 2008 From: bwalton at opencsw.org (Ben Walton) Date: Thu, 04 Dec 2008 15:44:41 -0500 Subject: [csw-maintainers] relatocatable packages and package scripts In-Reply-To: <20081204123820.C16758@bolthole.com> References: <1228414352-sup-4045@ntdws12.chass.utoronto.ca> <20081204104002.X16758@bolthole.com> <1228420336-sup-4801@ntdws12.chass.utoronto.ca> <20081204123820.C16758@bolthole.com> Message-ID: <1228423377-sup-2956@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Thu Dec 04 15:38:20 -0500 2008: > On Thu, Dec 04, 2008 at 02:59:29PM -0500, Ben Walton wrote: > nope. seems like you are talking about > "how do I handle a NON-RELOCATABLE (ie: not using BASEDIR) package, being > called with 'pkgadd -R /some/thing mypkg' ?" Yes, exactly. > If your package doesnt use BASEDIR normally, then you dont have to worry > about it. Perfect. Is this a widely used feature at all? > See other packages with postinstall scripts for more specific examples if > you like. I was already referencing the exim package, as it's one that I use that I knew had scripts in play. Anyway, I think that as long as chroot is kosher, that I'm all set. Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From iand at opencsw.org Thu Dec 4 22:59:07 2008 From: iand at opencsw.org (Ian Dickinson) Date: Thu, 04 Dec 2008 21:59:07 +0000 Subject: [csw-maintainers] old blastwave home dirs In-Reply-To: <20081204093621.V16758@bolthole.com> References: <49381332.1000800@cognigencorp.com> <20081204093621.V16758@bolthole.com> Message-ID: <493852AB.8010007@opencsw.org> Philip Brown wrote: > On Thu, Dec 04, 2008 at 12:28:18PM -0500, Darin Perusich wrote: >> Do we still have access to the blastwave home directories? I'd like to >> be able to get at all my old docs and crap. > > I'd say, after all Dennis's public slander about us "stealing" stuff, you > should ask him for it. and if he refuses, publically call him out about him > "stealing" stuff that is rightfully YOUR property. > > Even if he claims he has deleted it(which I doubt), he still has backups. When I asked him for this (access, or a tarball), I got no response, yet he's still listing me as a maintainer. Don't get your hopes up. :-( Ian From phil at bolthole.com Thu Dec 4 23:20:15 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 4 Dec 2008 14:20:15 -0800 Subject: [csw-maintainers] old blastwave home dirs In-Reply-To: <493852AB.8010007@opencsw.org>; from iand@opencsw.org on Thu, Dec 04, 2008 at 09:59:07PM +0000 References: <49381332.1000800@cognigencorp.com> <20081204093621.V16758@bolthole.com> <493852AB.8010007@opencsw.org> Message-ID: <20081204142015.G16758@bolthole.com> On Thu, Dec 04, 2008 at 09:59:07PM +0000, Ian Dickinson wrote: > Philip Brown wrote: > > I'd say, after all Dennis's public slander about us "stealing" stuff, you > > should ask him for it. and if he refuses, publically call him out about him > > "stealing" stuff that is rightfully YOUR property. > > > > Even if he claims he has deleted it(which I doubt), he still has backups. > > When I asked him for this (access, or a tarball), I got no response, yet he's > still listing me as a maintainer. > > Don't get your hopes up. :-( post it on the opensolaris mailing list and mention how long it has been since you didnt get a response from him to his direct email. (presumably a reasonable period to wait is 3 days) betcha that will get a response. and/or corner him on the #blastwave irc channel on freenode.net and keep a chat log of your request. then post it publically if he doesnt comply within a few days. And then again, perhaps Dennis will "find out" about this, since we're discussing it here, and decide to be more reasonable, proactively. A reminder: Dennis does not "own" **ONE THING** that maintainers did, while they were doing things "on blastwave". A person's work -- their "intellectual property".... is *theirs*, unless they sign away their work, or there is an implicit contract of "work for hire". Dennis never paid anyone 1 cent for what they did. Therefore, there was no "hire" being done. Therefore, so-called "blastwave" packages, and any related scripts and documentation, remain the intellectual property of the individual maintainer. From dam at opencsw.org Fri Dec 5 08:01:28 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 5 Dec 2008 08:01:28 +0100 Subject: [csw-maintainers] Standard for package naming Message-ID: <22225B82-435C-4EDA-A841-7448D7CA5E63@opencsw.org> Hi, I wonder if there is a standard on package naming, because for development packages there is a wide variety of suffixes, both in catalog and package names: CSWapache2-devel apache2_devel - Apache 2.2 development support CSWbdb44-devel berkeleydb44_devel - BerkeleyDB 4.4 development support CSWkrb5libdev krb5_lib_dev - MIT Kerberos 5 developer libraries CSWlibdbusdev libdbusdev - DBus Message Bus System - development headers CSWneon-devel neon_devel - Neon HTTP and WebDAV development support CSWoldapdevel openldap_devel - OpenLDAP development support (oldapdevel) CSWossldevel openssl_devel - Openssl development support CSWrenderdev render_dev - fontconfig.org render development files There seems to be a majority for *-devel for package-names and *_devel for catalog names. However, for runtime packages this is not so good: CSWapache2rt apache2rt - Apache 2.2 runtime libraries CSWcurlrt curlrt - Library for common Internet protocols Runtime CSWgcc3corert gcc3corert - GNU C Compiler Run Time CSWgcc3g++rt gcc3g++rt - GNU C++ Compiler Run Time CSWgcc4corert gcc4corert - GNU C Compiler Run Time CSWgcc4g++rt gcc4g++rt - GNU C++ Compiler Run Time CSWlibtoolrt libtool_rt - Generic library support runtime libraries CSWmysql5rt mysql5rt - run-time libraries for mysql5 CSWoldaprt openldap_rt - OpenLDAP runtime libraries (oldaprt) CSWosslrt openssl_rt - Openssl runtime libraries CSWvimrt vimrt - vim shared runtime and documentation Package names *rt are named inconsistent to *-devel as before. Catalog names are mixed again, sometime *_rt, sometimes *rt. Personally I like *-devel, *-rt, *_devel and *_rt, but I really don't care what is chosen, but whatever we choose the package names should be adjust and bugs should be filed for renaming. Best regards -- Dago From phil at bolthole.com Fri Dec 5 15:10:37 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 5 Dec 2008 06:10:37 -0800 Subject: [csw-maintainers] Standard for package naming In-Reply-To: <22225B82-435C-4EDA-A841-7448D7CA5E63@opencsw.org> References: <22225B82-435C-4EDA-A841-7448D7CA5E63@opencsw.org> Message-ID: <20081205141036.GB98262@bolthole.com> On Fri, Dec 05, 2008 at 08:01:28AM +0100, Dagobert Michelsen wrote: > Personally I like *-devel, *-rt, *_devel and *_rt, i agree > don't care what is chosen, but whatever we choose the package > names should be adjust and bugs should be filed for renaming. I would disagree here. renaming packages (at least the CSWxxx names) is ugly, becuase of depandancies, and i would prefer they NOT be renamed. unless they havef zero dependancies. From trygvel at opencsw.org Fri Dec 5 17:04:42 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Fri, 05 Dec 2008 17:04:42 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <20081204091318.T16758@bolthole.com> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> <8671613E-32CE-462C-9775-FD648520023B@opencsw.org> <4936F058.1070703@opencsw.org> <625385e30812031304r7a10f24ew201679db0ae76883@mail.gmail.com> <49378827.3090008@opencsw.org> <26EC0516-DB3D-4677-8DE9-20A17BD4B1A6@opencsw.org> <493796F4.60003@opencsw.org> <20081204091318.T16758@bolthole.com> Message-ID: <4939511A.2060207@opencsw.org> Philip Brown wrote: > On Thu, Dec 04, 2008 at 09:38:12AM +0100, Trygve Laugst?l wrote: >> What is the gain? The package tools already have a strong concept of >> versions, why not support multiple versions at the same time? I'm all >> for backwards compatibility and all, but I really need a feature like >> this so I don't mind running my tools with a special flag (might be nice >> anyway as it indicates that I'm running development stuff). > > Two things, just to hopefully bring people together on the same page: > > 1. no-one is proposing that our REGULAR trees (current, stable) have > multiple versions. Just wanted to mention that as reassurance to some > folks :-) Right. > 2. pkg-get already supports multiple versions to some degree. > As mentioned previously, i believe it will prompt you for which one you > want, though. > > As someone will probably not be initially aware that there even > EXIST multiple versions (since normally, a big point of > pkg-get is to INSULATE users from versions), I think that prompting > is an important safty check. > > I might add an OPTION flag to pkg-get, to say "always pick latest", but > I think the default behaviour will stay as "prompt if multiple versions" I would like such an option :) -- Trygve From bwalton at opencsw.org Fri Dec 5 21:40:44 2008 From: bwalton at opencsw.org (Ben Walton) Date: Fri, 05 Dec 2008 15:40:44 -0500 Subject: [csw-maintainers] libxml2 question Message-ID: <1228509292-sup-5532@ntdws12.chass.utoronto.ca> Hi All, I'm packaging up docbook dtds and am using xmlcatalog to add entries to the system sgml catalog, so that they're reference-able by all tools looking at the global catalog. It seems though, that the libxml2-supplied xmlcatalog tool updates /etc/sgml/catalog instead of /opt/csw/etc/sgml/catalog. I'm not sure if this is a bug or not...should something like this look in the system /etc instead of the CSW etc? Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From pfelecan at opencsw.org Sun Dec 7 17:05:15 2008 From: pfelecan at opencsw.org (Peter FELECAN) Date: Sun, 07 Dec 2008 17:05:15 +0100 Subject: [csw-maintainers] IRL meeting Message-ID: When and how we'll be informed about what was discussed and decided at the meeting? -- Peter From dam at opencsw.org Sun Dec 7 17:09:48 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 7 Dec 2008 17:09:48 +0100 Subject: [csw-maintainers] libxml2 question In-Reply-To: <1228509292-sup-5532@ntdws12.chass.utoronto.ca> References: <1228509292-sup-5532@ntdws12.chass.utoronto.ca> Message-ID: Hi Ben, Am 05.12.2008 um 21:40 schrieb Ben Walton: > I'm packaging up docbook dtds and am using xmlcatalog to add entries > to the system sgml catalog, so that they're reference-able by all > tools looking at the global catalog. It seems though, that the > libxml2-supplied xmlcatalog tool updates /etc/sgml/catalog instead of > /opt/csw/etc/sgml/catalog. I'm not sure if this is a bug or > not...should something like this look in the system /etc instead of > the CSW etc? I really don't know. From my understanding there should be only one catalog on a system, but it may be a good idea to have a special catalog for OpenCSW without intefering with the system. If you want this changed please let me know what there needs to be changed in the GAR description of libxml2. Best regards -- Dago From bwalton at opencsw.org Mon Dec 8 01:25:45 2008 From: bwalton at opencsw.org (Ben Walton) Date: Sun, 07 Dec 2008 19:25:45 -0500 Subject: [csw-maintainers] libxml2 question In-Reply-To: References: <1228509292-sup-5532@ntdws12.chass.utoronto.ca> Message-ID: <1228695055-sup-6944@ntdws12.chass.utoronto.ca> Excerpts from Dagobert Michelsen's message of Sun Dec 07 11:09:48 -0500 2008: Hi Dago, > I really don't know. From my understanding there should be only > one catalog on a system, but it may be a good idea to have a > special catalog for OpenCSW without intefering with the system. > If you want this changed please let me know what there needs > to be changed in the GAR description of libxml2. Well, I'd like to agree with this, but I think that for sanity purposes we should separate the CSW xml/sgml catalog info into our own little universe for the same reason we roll our own (sometimes duplicate) versions of libraries, etc. Solaris 10 is providing some of this stuff already (including docbook v4.1 dtds) through one of the Gnome packages, while it doesn't exist on solaris 8 (and 9?)...The dtd package I'm putting together provides the same dtd as above in addition to many other versions. None of my systems with libxml2 have anything actually in the catalog presently, so this may not be something that has been leveraged yet, which would make the change simple. Knowing this for sure would help though. If there are packages using xmlcatalog to install references to various items, then a transition becomes trickier since install/uninstall scripts from those package most likely reference paths explicitly and would therefore be broken by any change of this nature. [Comments from packagers of things that depend on libxml2 are quite welcome here, assuming others agree that we should segregate our catalog info.] I'll have a look at the results of the package from your updated GAR description for libxml2...a cursory glance looks like it should be putting the in the proper (CSW) locations. Thoughts on the above anyone? Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From ihsan at opencsw.org Mon Dec 8 08:53:47 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Mon, 08 Dec 2008 08:53:47 +0100 Subject: [csw-maintainers] IRL meeting In-Reply-To: References: Message-ID: <493CD28B.1070001@opencsw.org> Good morning, Am 7.12.2008 17:05 Uhr, Peter FELECAN schrieb: > When and how we'll be informed about what was discussed and decided at > the meeting? I've put the bylaws of the OpenCSW Association online. http://wiki.opencsw.org/open-community-software-project-bylaws PDF: http://wiki.opencsw.org/local--files/open-community-software-project-bylaws/OpenCSW_bylaws.pdf Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From ihsan at opencsw.org Mon Dec 8 09:58:52 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Mon, 08 Dec 2008 09:58:52 +0100 Subject: [csw-maintainers] mailing list archive Message-ID: <493CE1CC.1070409@opencsw.org> Good morning, Gmane is providing an alternative, searchable, mailing list archive with an NNTP interface. The public OpenCSW mailing list are there archived as well. http://dir.gmane.org/search.php?match=opencsw Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From a.cervellin at acm.org Mon Dec 8 11:34:35 2008 From: a.cervellin at acm.org (Alessio) Date: Mon, 08 Dec 2008 11:34:35 +0100 Subject: [csw-maintainers] IRL meeting In-Reply-To: <493CD28B.1070001@opencsw.org> References: <493CD28B.1070001@opencsw.org> Message-ID: <493CF83B.9020708@acm.org> Ihsan Dogan wrote: > Good morning, > > Am 7.12.2008 17:05 Uhr, Peter FELECAN schrieb: >> When and how we'll be informed about what was discussed and decided at >> the meeting? > > I've put the bylaws of the OpenCSW Association online. > > http://wiki.opencsw.org/open-community-software-project-bylaws so, who are the members of the board now? From william at wbonnet.net Mon Dec 8 11:53:05 2008 From: william at wbonnet.net (William Bonnet) Date: Mon, 08 Dec 2008 11:53:05 +0100 Subject: [csw-maintainers] IRL meeting In-Reply-To: <493CF83B.9020708@acm.org> References: <493CD28B.1070001@opencsw.org> <493CF83B.9020708@acm.org> Message-ID: <493CFC91.2000108@wbonnet.net> Hi Alessio > so, who are the members of the board now? > Phil, Ishan and Dagobert cheers, From dam at opencsw.org Mon Dec 8 12:37:32 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 8 Dec 2008 12:37:32 +0100 Subject: [csw-maintainers] Summary of IRL Meeting Message-ID: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> Fellow maintainers, the meeting in Zurich is over and the results will hopefully bring the OpenCSW project for the good of the packaging community ahead. Sorry for this summary to be a bit late but I felt the time was best used for talking while the other maintainers were present and write the summary afterwards. Participants ------------ The following persons participated (in alphabetical order): - William Bonnet - Philip Brown - Ihsan Dogan - Sebastian Kayser - Dominique Laigle - Trygve Laugst?l - Alexander Maier - Dagobert Michelsen - Othmar Wigger After lots of discussions on Saturday on what the new incorporated society should be based on the bylaws where defined. The official name now is "Open Community Software Project (OpenCSW)". The Board --------- The elected board now contitutes of Philip Brown (President), Ihsan Dogan (Cashier) and me (Dagobert Michelsen) as Actuar. Feel free to contact the board about any issues at board at opencsw.org (Ihsan will set this up ASAP) Basically the board can then open a discussion on the maintainers list and make a decision based on the results of the discussion. The decision will be posted and a rationale explaining the decision will be given. Membership ---------- The participants of the meeting are the founding members. It is legally not possible to just grab people and make them members if they have not applied for membership. So every maintainer will get an email within the next few days asking if they want to apply for membership. A simple reply with "I want to apply for membership" is enough. The board will usually accept membership and will post about all membership applications. As is stated in the bylaws there is no membership fee. There will be a publicly readble mailing list where all members can post on at members@ Accepted members will be automatically added to that list. Sidenotes --------- There have been lots of discussions during the whole time about technical issues and the community in a non-formal way. The results from these discussions will trigger some more discussions on the mailing list in the next time. The following topics have not been finalized and are subject to more discussion: - One technical summercamp per year. Trygve offered to organize the first one in Oslo in summer 2009. There may be "bug squashing day", technical discussions among other fun things. - Design of a central directory server for easier setup of more build farms - Optimized GCC builds with GCC for sparc systems (GCCfss) - A next generation packaging tool from Trygve and William - Redesign of www.opencsw.org by William - A new catalog ("unstrict/") which allows packages for only one architecture or onle one Solaris version. This will be a superset of current/ - Peters' list (<>) is generally considered a Good Thing and the issues will be worked on - A GAR package for easier package building - There have been some pictures taken. A group pictures is at Best regards -- Dago From dam at opencsw.org Mon Dec 8 16:46:00 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 8 Dec 2008 16:46:00 +0100 Subject: [csw-maintainers] Standard for package naming In-Reply-To: <20081205141036.GB98262@bolthole.com> References: <22225B82-435C-4EDA-A841-7448D7CA5E63@opencsw.org> <20081205141036.GB98262@bolthole.com> Message-ID: <5977767A-27F8-459B-BF44-416934465B87@opencsw.org> Hi Phil, Am 05.12.2008 um 15:10 schrieb Philip Brown: > On Fri, Dec 05, 2008 at 08:01:28AM +0100, Dagobert Michelsen wrote: >> Personally I like *-devel, *-rt, *_devel and *_rt, > > i agree Could you please add this to the standards page? >> don't care what is chosen, but whatever we choose the package >> names should be adjust and bugs should be filed for renaming. > > I would disagree here. renaming packages (at least the CSWxxx names) > is > ugly, becuase of depandancies, and i would prefer they NOT be renamed. > unless they havef zero dependancies. We must clean up this mess at some time, even when intermediate packages must be used in the meantime. We'll look at these one at a time. Best regards -- Dago From phil at bolthole.com Mon Dec 8 18:44:06 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 8 Dec 2008 09:44:06 -0800 Subject: [csw-maintainers] Standard for package naming In-Reply-To: <5977767A-27F8-459B-BF44-416934465B87@opencsw.org> References: <22225B82-435C-4EDA-A841-7448D7CA5E63@opencsw.org> <20081205141036.GB98262@bolthole.com> <5977767A-27F8-459B-BF44-416934465B87@opencsw.org> Message-ID: <20081208174406.GA71096@bolthole.com> On Mon, Dec 08, 2008 at 04:46:00PM +0100, Dagobert Michelsen wrote: > Hi Phil, > > Am 05.12.2008 um 15:10 schrieb Philip Brown: > > On Fri, Dec 05, 2008 at 08:01:28AM +0100, Dagobert Michelsen wrote: > >> Personally I like *-devel, *-rt, *_devel and *_rt, > > > > i agree > > Could you please add this to the standards page? Hm.. .actually, I overly agreed on one part of that. I dont think that the "-" needs be mandatory for the PKG name. I think that CSWmysql4devel CSWmysql5devel CSWoldapdevel are perfectly readable and do not have to be redone to comply with some "new standard". So I would say CSWxxxdevel CSWxxxrt CSWxxxdoc should be the standard for PKG names. if you want to use dashes, you can, but it is not mandatory. (mostly because "devel" is long enough, without making it even longer by requiring "-" on top of it) Ok? From pfelecan at opencsw.org Mon Dec 8 20:03:54 2008 From: pfelecan at opencsw.org (Peter FELECAN) Date: Mon, 08 Dec 2008 20:03:54 +0100 Subject: [csw-maintainers] Summary of IRL Meeting In-Reply-To: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> (Dagobert Michelsen's message of "Mon\, 8 Dec 2008 12\:37\:32 +0100") References: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> Message-ID: Dagobert Michelsen writes: > - There have been some pictures taken. A group pictures is at > Nice. Can somebody put names under the photos for those that didn't have the opportunity to be there? TIA -- Peter From dam at opencsw.org Tue Dec 9 00:14:02 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 9 Dec 2008 00:14:02 +0100 Subject: [csw-maintainers] Summary of IRL Meeting In-Reply-To: References: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> Message-ID: <392323F5-EF0D-4DC4-BCB2-2EAAC80979AE@opencsw.org> Hi Peter, hi Othmar, Am 08.12.2008 um 20:03 schrieb Peter FELECAN: > Dagobert Michelsen writes: >> - There have been some pictures taken. A group pictures is at >> > > Nice. Can somebody put names under the photos for those that didn't > have the opportunity to be there? TIA Othmar, could you please set these? * Picture 1: On the group picture this is (left to right): - Alexander Maier - Trygve Laugst?l - Ihsan Dogan - Sebastian Kayser - Dagobert Michelsen - William Bonnet - Philip Brown - Dominique Laigle * Picture 2: Same * Picture 3: Philip Brown * Picture 4: left: - Trygve Laugst?l - Alexander Maier - Ihsan Dogan right: - William Bonnet - Dagobert Michelsen - Philip Brown - Dominique Laigle * Picture 5: (only right side) - William Bonnet - Dagobert MIchelsen - Philip Brown - Domoniqie Laigle * Picture 6: Pizza with ham and olives * Picture 7 - Trygve Laugst?l - Ihsan Dogan - Sebastian Kayser * Picture 8 - Alexander Maier - Trygve Laugst?l - Philip Brown - Sebastian Kayser * Picture 9: Trygve Laugst?l * Picture 10: Dagobert Michelsen * Picture 11: Ihsan Dogan * Picture 12: Philip Brown * Picture 13: Dominiqie Laigle * Picture 14: The new board - Ihsan Dogan - Dagobert Michelsen - Philip Brown Best regards -- Dago From dlaigle at opencsw.org Tue Dec 9 11:50:51 2008 From: dlaigle at opencsw.org (dlaigle) Date: Tue, 09 Dec 2008 11:50:51 +0100 Subject: [csw-maintainers] KDE on build machines In-Reply-To: <392323F5-EF0D-4DC4-BCB2-2EAAC80979AE@opencsw.org> References: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> <392323F5-EF0D-4DC4-BCB2-2EAAC80979AE@opencsw.org> Message-ID: <6227ac8cb62a6524ebc5c0e3980ce24d@localhost> Gents, WMay I know what exact versions of KDE have been installed on the building machines ? As incredible as it sounds, we miss the following prototype declaration in kio/netaccess.h "static KURL mostLocalURL(const KURL& url, QWidget* window);" although the function exists in the object libkio.so! This leads to horrible hack on the source of kdesdk/cervisia in order to build, and before filling a bug at KDE I need to now more about what we have currently. Thanks - Dominique From dam at opencsw.org Tue Dec 9 11:59:16 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 9 Dec 2008 11:59:16 +0100 Subject: [csw-maintainers] KDE on build machines In-Reply-To: <6227ac8cb62a6524ebc5c0e3980ce24d@localhost> References: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> <392323F5-EF0D-4DC4-BCB2-2EAAC80979AE@opencsw.org> <6227ac8cb62a6524ebc5c0e3980ce24d@localhost> Message-ID: Hi Dominique, Am 09.12.2008 um 11:50 schrieb dlaigle: > WMay I know what exact versions of KDE have been installed on the > building > machines ? > As incredible as it sounds, we miss the following prototype > declaration in > kio/netaccess.h > "static KURL mostLocalURL(const KURL& url, QWidget* window);" > although the function exists in the object libkio.so! > > This leads to horrible hack on the source of kdesdk/cervisia in > order to > build, and before filling a bug at KDE I need to now more about what > we > have currently. Looks like this: build8s% grep kio/netaccess.h /var/sadm/install/contents /opt/csw/kde-gcc/include/kio/netaccess.h f none 0644 root bin 21021 15804 1116850553 CSWkdelibsgcc build8s% pkginfo -l CSWkdelibsgcc PKGINST: CSWkdelibsgcc NAME: kdelibs_gcc - Base set of libraries needed by KDE programs (gcc3) CATEGORY: application ARCH: sparc VERSION: 3.4.2 VENDOR: http://www.kde.org packaged for CSW by Ken Mays PSTAMP: apollo20050909214115 INSTDATE: Sep 04 2008 22:09 HOTLINE: http://www.blastwave.org/bugtrak/ EMAIL: kenmays at blastwave.org STATUS: completely installed FILES: 5577 installed pathnames 89 shared pathnames 328 directories 307 executables 3 setuid/setgid executables 112423 blocks used (approx) Do we need a newer version of KDE? Best regards -- Dago From dam at opencsw.org Tue Dec 9 12:03:41 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 9 Dec 2008 12:03:41 +0100 Subject: [csw-maintainers] Update of bzip2 and clamav Message-ID: <91F5D112-4573-440C-9A79-FD0F0C83E2E8@opencsw.org> Hi, when working together with Peter on clamav I noticed > checking for bzlib.h... yes > checking for CVE-2008-1372... bugged > configure: WARNING: ****** bzip2 libraries are affected by the > CVE-2008-1372 bug > configure: WARNING: ****** We strongly suggest you to update to > bzip2 1.0.5. > configure: WARNING: ****** Please do not report stability problems > to the ClamAV developers! which seems to result in multiple compile errors. James: Can we release 1.0.5 to current so I can upgrade it on the farm? Peter: clamav doesn't seem to compile any more because of this error. Feel free to also have a look. I'll stop here for the moment and will pick up again when we are at merge phase exclusion. Best regards -- Dago From james at opencsw.org Tue Dec 9 15:31:53 2008 From: james at opencsw.org (James Lee) Date: Tue, 09 Dec 2008 14:31:53 GMT Subject: [csw-maintainers] Update of bzip2 and clamav In-Reply-To: <91F5D112-4573-440C-9A79-FD0F0C83E2E8@opencsw.org> References: <91F5D112-4573-440C-9A79-FD0F0C83E2E8@opencsw.org> Message-ID: <20081209.14315300.1742443868@gyor.oxdrove.co.uk> On 09/12/08, 11:03:41, Dagobert Michelsen wrote regarding [csw-maintainers] Update of bzip2 and clamav: > James: Can we release 1.0.5 to current so I can upgrade it on the farm? Give me a break. I built it on Sunday and I'm currently at work. It's needs burn in and test; you could help by testing it thoroughly. James. From phil at bolthole.com Tue Dec 9 18:13:48 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 9 Dec 2008 09:13:48 -0800 Subject: [csw-maintainers] KDE on build machines In-Reply-To: References: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> <392323F5-EF0D-4DC4-BCB2-2EAAC80979AE@opencsw.org> <6227ac8cb62a6524ebc5c0e3980ce24d@localhost> Message-ID: <20081209171348.GA35059@bolthole.com> On Tue, Dec 09, 2008 at 11:59:16AM +0100, Dagobert Michelsen wrote: > > Do we need a newer version of KDE? very very badly. our version: 3.4.2 latest version: 4.1.3 ? !! From phil at bolthole.com Tue Dec 9 18:14:44 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 9 Dec 2008 09:14:44 -0800 Subject: [csw-maintainers] KDE on build machines In-Reply-To: References: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> <392323F5-EF0D-4DC4-BCB2-2EAAC80979AE@opencsw.org> <6227ac8cb62a6524ebc5c0e3980ce24d@localhost> Message-ID: <20081209171444.GB35059@bolthole.com> On Tue, Dec 09, 2008 at 11:59:16AM +0100, Dagobert Michelsen wrote: > Do we need a newer version of KDE? PS: even on the "3 series", there is 3.5.10 released aug 2008 Seems like there is somewhat of a parallel stream of v3 compared to v4 kde. From bwalton at opencsw.org Tue Dec 9 18:23:00 2008 From: bwalton at opencsw.org (Ben Walton) Date: Tue, 09 Dec 2008 12:23:00 -0500 Subject: [csw-maintainers] KDE on build machines In-Reply-To: <20081209171444.GB35059@bolthole.com> References: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> <392323F5-EF0D-4DC4-BCB2-2EAAC80979AE@opencsw.org> <6227ac8cb62a6524ebc5c0e3980ce24d@localhost> <20081209171444.GB35059@bolthole.com> Message-ID: <1228843206-sup-7285@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Tue Dec 09 12:14:44 -0500 2008: > On Tue, Dec 09, 2008 at 11:59:16AM +0100, Dagobert Michelsen wrote: > > Do we need a newer version of KDE? > > even on the "3 series", there is 3.5.10 released aug 2008 Seems like > there is somewhat of a parallel stream of v3 compared to v4 kde. I'm a GNOME user myself, but various blogs, etc that I read track the KDE progress (mostly from a Debian packaging perspective). I'd suggest that if someone wants to roll up the current version in the 4 series that the current 3.X also be offered. If memory serves, the 4 stream won't reach feature parity with 3 until 4.2. There was a lot of drastic change that went into 4 and not all apps have caught up yet (since it's still somewhat a moving target). [This may be out of date, since I haven't seen anything for a few months now...] HTH. -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From skayser at opencsw.org Tue Dec 9 20:10:02 2008 From: skayser at opencsw.org (Sebastian Kayser) Date: Tue, 09 Dec 2008 20:10:02 +0100 Subject: [csw-maintainers] Summary of IRL Meeting In-Reply-To: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> References: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> Message-ID: <493EC28A.9020807@opencsw.org> Hi Dago, thanks for the summary. In case there are any related question i hope they are addressed to the maintainers list so that everyone gets a share of insight. Dagobert Michelsen wrote: > Membership > ---------- > > The participants of the meeting are the founding members. It is > legally not possible to just grab people and make them members if > they have not applied for membership. So every maintainer will > get an email within the next few days asking if they want to > apply for membership. A simple reply with "I want to apply for > membership" is enough. The board will usually accept membership > and will post about all membership applications. > As is stated in the bylaws there is no membership fee. Maybe one could add for the uninitiated that this whole membership thing is a side effect (or essential building block) of putting OpenCSW on the legal basis of an incorporated society. The ASF [1] is a prominent example for a similar approach. The membership status eventually leads to voting rights in general meetings according to rules which have yet to be defined (by William, was it?). So even though membership might have the initial connotation of something closed it is exactly the contrary. It is the foundation to move towards an open and community based decision model (call it project democracy if you want) that not only exists in our minds, but on paper also. > There will be a publicly readble mailing list where all members > can post on at members@ > Accepted members will be automatically added to that list. And members@ will not just be duplicate of maintainers@, because people can contribute to OpenCSW without being a maintainer (think web- or postmaster for example) and issues being discussed on members@ would naturally differ also. > Sidenotes > --------- > > There have been lots of discussions during the whole time about > technical issues and the community in a non-formal way. The > results from these discussions will trigger some more discussions > on the mailing list in the next time. Seems as if the dinner on Saturday evening generated a lot of ideas. Looking forward to the discussions. > The following topics have not been finalized and are subject > to more discussion: > > - Redesign of www.opencsw.org by William What's the ETA? :) > - One technical summercamp per year. Trygve offered to organize > the first one in Oslo in summer 2009. There may be "bug > squashing day", technical discussions among other fun things. Yeah, great idea! Oslo sounds promising, although i have to admit that i had hoped to get away with cheaper dinners than the one in Zurich next time we would meet ;) Sebastian [1] http://apache.org/foundation/ [2] http://wiki.blastwave.org/ From pfelecan at opencsw.org Tue Dec 9 20:13:16 2008 From: pfelecan at opencsw.org (Peter FELECAN) Date: Tue, 09 Dec 2008 20:13:16 +0100 Subject: [csw-maintainers] Summary of IRL Meeting In-Reply-To: <392323F5-EF0D-4DC4-BCB2-2EAAC80979AE@opencsw.org> (Dagobert Michelsen's message of "Tue\, 9 Dec 2008 00\:14\:02 +0100") References: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> <392323F5-EF0D-4DC4-BCB2-2EAAC80979AE@opencsw.org> Message-ID: Dagobert Michelsen writes: > Hi Peter, hi Othmar, > > Am 08.12.2008 um 20:03 schrieb Peter FELECAN: >> Dagobert Michelsen writes: >>> - There have been some pictures taken. A group pictures is at >>> >> >> Nice. Can somebody put names under the photos for those that didn't >> have the opportunity to be there? TIA > > Othmar, could you please set these? Thank you: now it's better: to have faces on names... -- Peter From dlaigle at opencsw.org Wed Dec 10 00:16:48 2008 From: dlaigle at opencsw.org (dlaigle) Date: Wed, 10 Dec 2008 00:16:48 +0100 Subject: [csw-maintainers] KDE on build machines In-Reply-To: <20081209171444.GB35059@bolthole.com> References: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> <392323F5-EF0D-4DC4-BCB2-2EAAC80979AE@opencsw.org> <6227ac8cb62a6524ebc5c0e3980ce24d@localhost> <20081209171444.GB35059@bolthole.com> Message-ID: <8d68f6f8059736d5b6af361a44762be1@localhost> On Tue, 9 Dec 2008 09:14:44 -0800, Philip Brown wrote: > On Tue, Dec 09, 2008 at 11:59:16AM +0100, Dagobert Michelsen wrote: >> Do we need a newer version of KDE? > > PS: > > even on the "3 series", there is 3.5.10 released aug 2008 > Seems like there is somewhat of a parallel stream of v3 compared to v4 kde. Exactly! 3.5.10 is still _THE_ stable release currently. As I proposed to Dago, I took the bill for the build of kde 3.5.10 with GCC3 for the package kde-gcc and I started as of today. This will allows me to release kdevelop 3.5.3. On the other hand, regarding KDE 4, I think it is worth to have kde 4 built with Sun Studio instead (over CSWQt). But I rather let this job to any other volunteer. - Dominique > > _______________________________________________ > maintainers mailing list > maintainers at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/maintainers > From phil at bolthole.com Wed Dec 10 01:56:02 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 9 Dec 2008 16:56:02 -0800 Subject: [csw-maintainers] KDE on build machines In-Reply-To: <8d68f6f8059736d5b6af361a44762be1@localhost> References: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> <392323F5-EF0D-4DC4-BCB2-2EAAC80979AE@opencsw.org> <6227ac8cb62a6524ebc5c0e3980ce24d@localhost> <20081209171444.GB35059@bolthole.com> <8d68f6f8059736d5b6af361a44762be1@localhost> Message-ID: <20081210005602.GB80722@bolthole.com> On Wed, Dec 10, 2008 at 12:16:48AM +0100, dlaigle wrote: > 3.5.3. On the other hand, regarding KDE 4, I think it is worth to have kde > 4 built with Sun Studio instead (over CSWQt). But I rather let this job to > any other volunteer. because, there is no guarantee that it WILL build easily :-} From skayser at opencsw.org Wed Dec 10 15:09:03 2008 From: skayser at opencsw.org (Sebastian Kayser) Date: Wed, 10 Dec 2008 15:09:03 +0100 Subject: [csw-maintainers] Hudson package catalog? Message-ID: <493FCD7F.6070201@opencsw.org> Hi, just wondering: What's the status for the Hudson-built packages [1] catalog? I just put a package in Hudson, built it and noticed that the catalogs [2,3] are out of sync with the actual packages. Sebastian [1] http://mirror.opencsw.org/opencsw/hudson/ [2] http://mirror.opencsw.org/opencsw/hudson/i386/5.8/catalog [3] http://mirror.opencsw.org/opencsw/hudson/sparc/5.8/catalog From bwalton at opencsw.org Wed Dec 10 15:45:13 2008 From: bwalton at opencsw.org (Ben Walton) Date: Wed, 10 Dec 2008 09:45:13 -0500 Subject: [csw-maintainers] update to libxml2 Message-ID: <1228919673-sup-1323@ntdws12.chass.utoronto.ca> Hi All, Dago was kind enough to roll an updated libxml2 package for me that places the xml and sgml catalogs in /opt/csw/etc instead of /etc. I'm going to need this installed on the buildfarm to proceed with building another package shortly (in addition to a few other things that rely on it). Is anyone out there with packages that depend on libxml2 concerned about this change? Nobody has piped up yet...If you make use of xmlcatalog to install, remove or otherwise manipulate catalogs (which would have been registered in /etc/xml/catalog or /etc/sgml/catalog previously), then you may want to consider the impact this change could have for you... I'm a single (I think) package dependency away from being able to build a git + gitdoc package, so the sooner I can get these packages signed off, released and installed on the buildfarm, the happier I'll be. That being said, I don't want to push for a change that will negatively impact others. Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From dam at opencsw.org Wed Dec 10 16:42:45 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 10 Dec 2008 16:42:45 +0100 Subject: [csw-maintainers] update to libxml2 In-Reply-To: <1228919673-sup-1323@ntdws12.chass.utoronto.ca> References: <1228919673-sup-1323@ntdws12.chass.utoronto.ca> Message-ID: <0F5A1188-DE10-4F83-921D-B0EB6BC2AA65@opencsw.org> Hi, Am 10.12.2008 um 15:45 schrieb Ben Walton: > Is anyone out there with packages that depend on libxml2 concerned > about this change? As this is a somewhat central package please some other maintainer check if it works. We can than release it to current/. Thanks! -- Dago From dam at opencsw.org Wed Dec 10 20:39:14 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 10 Dec 2008 20:39:14 +0100 Subject: [csw-maintainers] Hudson package catalog? In-Reply-To: <493FCD7F.6070201@opencsw.org> References: <493FCD7F.6070201@opencsw.org> Message-ID: <3061F111-75DA-4E77-AD63-34C4D0D34CA1@opencsw.org> Hi Sebastian, Am 10.12.2008 um 15:09 schrieb Sebastian Kayser: > just wondering: What's the status for the Hudson-built packages [1] > catalog? I just put a package in Hudson, built it and noticed that the > catalogs [2,3] are out of sync with the actual packages. Yes. It seems that the catalog was only build once. Trygve, can you rebuild the catalog when a new package arrives? Best regards -- Dago From bwalton at opencsw.org Wed Dec 10 21:45:48 2008 From: bwalton at opencsw.org (Ben Walton) Date: Wed, 10 Dec 2008 15:45:48 -0500 Subject: [csw-maintainers] update to libxml2 In-Reply-To: <0F5A1188-DE10-4F83-921D-B0EB6BC2AA65@opencsw.org> References: <1228919673-sup-1323@ntdws12.chass.utoronto.ca> <0F5A1188-DE10-4F83-921D-B0EB6BC2AA65@opencsw.org> Message-ID: <1228941400-sup-4840@ntdws12.chass.utoronto.ca> Excerpts from Dagobert Michelsen's message of Wed Dec 10 10:42:45 -0500 2008: > Am 10.12.2008 um 15:45 schrieb Ben Walton: > > Is anyone out there with packages that depend on libxml2 concerned > > about this change? > > As this is a somewhat central package please some other > maintainer check if it works. We can than release it to > current/. I've now tried it in combination with libxslt from current/stable and it produced proper output (docbook xml -> man page). This was in combination with the (not yet released) DTD and XSL stylesheet packages I've installed locally. I'm ready to build the last package before git... -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From william at wbonnet.net Wed Dec 10 21:01:11 2008 From: william at wbonnet.net (William Bonnet) Date: Wed, 10 Dec 2008 21:01:11 +0100 Subject: [csw-maintainers] Summary of IRL Meeting In-Reply-To: References: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> <392323F5-EF0D-4DC4-BCB2-2EAAC80979AE@opencsw.org> Message-ID: <49402007.2030204@wbonnet.net> Hi It's the first evening since the meeting i come back from office before "late in the evening". I finally have time to read the list. I would like to thank you all for having been in Zurich this week end. It has been a very pleasant time. Thank you all, and thank you very much Ihsan for organization cheers W. -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.blastwave.org An OpenSolaris Community Site http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From dam at opencsw.org Wed Dec 10 22:25:17 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 10 Dec 2008 22:25:17 +0100 Subject: [csw-maintainers] GCC for Sparc Systems (GCCfss) on buildfarm Message-ID: Hi, I installed GCC for Sparc Systems 4.2.0 and 4.2.1 on build10s. Unfortunately even the oldest available version 4.0.3 is not available for Solaris 8: I mailed the cooltools team for an older version available for Solaris 8. You can access the compilers at /opt/SUNWgccfss/4.2.x/ Feedback as always welcome! Dominique? ;-) Best regards -- Dago From trygvel at opencsw.org Thu Dec 11 08:58:44 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Thu, 11 Dec 2008 08:58:44 +0100 Subject: [csw-maintainers] Hudson package catalog? In-Reply-To: <3061F111-75DA-4E77-AD63-34C4D0D34CA1@opencsw.org> References: <493FCD7F.6070201@opencsw.org> <3061F111-75DA-4E77-AD63-34C4D0D34CA1@opencsw.org> Message-ID: <4940C834.3020501@opencsw.org> Dagobert Michelsen wrote: > Hi Sebastian, > > Am 10.12.2008 um 15:09 schrieb Sebastian Kayser: >> just wondering: What's the status for the Hudson-built packages [1] >> catalog? I just put a package in Hudson, built it and noticed that the >> catalogs [2,3] are out of sync with the actual packages. > > Yes. It seems that the catalog was only build once. > Trygve, can you rebuild the catalog when a new package arrives? It should have been built once per hour by the /var/opt/csw/hudson/bin/cron-update-catalog script, not sure why it is not running. I'll add some logging. -- Trygve From dam at opencsw.org Thu Dec 11 10:49:43 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 11 Dec 2008 10:49:43 +0100 Subject: [csw-maintainers] Update of bzip2 and clamav In-Reply-To: <20081209.14315300.1742443868@gyor.oxdrove.co.uk> References: <91F5D112-4573-440C-9A79-FD0F0C83E2E8@opencsw.org> <20081209.14315300.1742443868@gyor.oxdrove.co.uk> Message-ID: Hi James, Am 09.12.2008 um 15:31 schrieb James Lee: > On 09/12/08, 11:03:41, Dagobert Michelsen wrote > regarding > [csw-maintainers] Update of bzip2 and clamav: > >> James: Can we release 1.0.5 to current so I can upgrade it on the >> farm? > > Give me a break. I built it on Sunday and I'm currently at work. > > It's needs burn in and test; you could help by testing it thoroughly. Works great and you even made 64 bit :-) For me you can push it. Best regards -- Dago From dlaigle at opencsw.org Thu Dec 11 16:57:20 2008 From: dlaigle at opencsw.org (dlaigle) Date: Thu, 11 Dec 2008 16:57:20 +0100 Subject: [csw-maintainers] GCC for Sparc Systems (GCCfss) on buildfarm In-Reply-To: References: Message-ID: <5109d8d2989b38a4a119dbdc85568fa7@localhost> Don't worry: you'll get my feedback very soon :-) On Wed, 10 Dec 2008 22:25:17 +0100, Dagobert Michelsen wrote: > Hi, > > I installed GCC for Sparc Systems 4.2.0 and 4.2.1 on build10s. > Unfortunately even the oldest available version 4.0.3 is not > available for Solaris 8: > > I mailed the cooltools team for an older version available for > Solaris 8. > > You can access the compilers at > /opt/SUNWgccfss/4.2.x/ > > Feedback as always welcome! Dominique? ;-) > > > Best regards > > -- Dago > _______________________________________________ > maintainers mailing list > maintainers at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/maintainers > From bonivart at opencsw.org Thu Dec 11 16:58:00 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Thu, 11 Dec 2008 16:58:00 +0100 Subject: [csw-maintainers] /testing clamav 0.94.2 Message-ID: <625385e30812110758x668c1fa7v78b44530f9a628b5@mail.gmail.com> This package by Alex Moore was getting quite old (0.92.1,REV=2008.02.11), especially since it's security related. I use it myself for MailScanner so I tried to build it. No package has yet challenged me like this one and poor Dagobert had to suffer from constant calls for help. :-) I wanted to do it in GAR which is being upgraded to v2 and I was very keen on using several of the new features like the easy splitting of packages. I also wanted it to use CSWcswclassutils for SMF support and configuration file handling. I could simplify the old preinstall a lot and completely remove the postinstall thanks to the use of CSWcswclassutils. The init script for clamd is also redone quite a lot. I would like help to test this one since I assume it's relatively widely used and important to a user. I have done some tests on sparc/5.9 like running clamscan, starting clamd and running clamdscan, updating virus signatures with freshclam and so on. What I haven't tested at all (except for checking with ldd) is the clamav-milter so if someone can set that up a report would be great. Also test from i386 and 5.10 (use SMF) if you can. Just install, test what you can, remove and report back to me even if everything was successful, I need to hear that too. :-) Look for clamav and libclamav here: http://buildfarm.opencsw.org/testing.html By the way, I have updated the wiki page about CSWcswclassutils to include instructions on how to use it in GAR. Take a look. -- /peter From dam at opencsw.org Thu Dec 11 17:31:47 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 11 Dec 2008 17:31:47 +0100 Subject: [csw-maintainers] OpenCSW Prefix In-Reply-To: References: <343A2AE3-DFC1-4B14-911F-67161138B3B4@opencsw.org> <4DE07271-5CBD-4022-B736-9248070EB132@opencsw.org> Message-ID: <341E7640-CCD6-400A-BBC0-96868E62AB26@opencsw.org> Hi Gary, Am 11.12.2008 um 12:27 schrieb Gary Law: > To pick up on a thread we left alone pending the meeting, what was > the decision on a new prefix for opencsw? Or was this not discussed? The topic was not discussed due to shortage of time. There are many other issues to be addressed in addition to change of prefix like full relocatibility raised from Sebastian, source packages, make-world-capability etc. If you are willing to work on a customizable prefix in GAR you are very welcome to do so. mGAR v2 makes developer-versions per package even easier. Best regards -- Dago -------------- next part -------------- An HTML attachment was scrubbed... URL: From phil at bolthole.com Thu Dec 11 19:24:38 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 11 Dec 2008 10:24:38 -0800 Subject: [csw-maintainers] pkg-get 4.0 Message-ID: <20081211182438.GA33380@bolthole.com> hi folks, A request; if you use pkg-get, would you please try out the 4.0beta version and let me know any problems with it for you? I'd LIKE to make it the "current" default. but given the major rewrite, i'm leery about doing so without some feedback. and I havent gotten any yet. http://mirror.opencsw.org/testing/pkg_get-4.0,REV=2008.11.12.beta-SunOS5.8-all-CSW.pkg From bwalton at opencsw.org Thu Dec 11 20:10:55 2008 From: bwalton at opencsw.org (Ben Walton) Date: Thu, 11 Dec 2008 14:10:55 -0500 Subject: [csw-maintainers] openssl vs certs Message-ID: <1229022639-sup-2798@ntdws12.chass.utoronto.ca> Hi All, A package I'm working on has it's source hosted on a site that is https only (fedorahosted.org). The ssl cert there is signed by equifax (as evidenced using: openssl s_client -connect fedorahosted.org:443 -showcerts). It seems that the CSW openssl package doesn't provide the required certificate chain to verify it, which is causing wget to bail out (without extra options, anyway). As I've never built openssl, I don't know if this is a build omission or simply that the required files weren't manually collected, and distributed with the package...I'll open a bug for this issue if it actually is a bug. If it's intentional, let me know. [It looks like rhel provides the equifax cert(s) with openssl and debian/ubuntu via ca-certificates.] For reference, this can be verified via: /opt/csw/bin/wget https://fedorahosted.org/xmlto/export/1/xmlto-0.0.21.tar.bz2 Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From phil at bolthole.com Thu Dec 11 20:17:21 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 11 Dec 2008 11:17:21 -0800 Subject: [csw-maintainers] openssl vs certs In-Reply-To: <1229022639-sup-2798@ntdws12.chass.utoronto.ca> References: <1229022639-sup-2798@ntdws12.chass.utoronto.ca> Message-ID: <20081211191721.GE33380@bolthole.com> On Thu, Dec 11, 2008 at 02:10:55PM -0500, Ben Walton wrote: > As I've never built openssl, I don't know if this is a build omission > or simply that the required files weren't manually collected, and > distributed with the package... Sounds like the latter to me. But also sounds like it would be a useful step for "us" to do. [I'm not the openssl maintainer, thou!] From james at opencsw.org Thu Dec 11 20:53:08 2008 From: james at opencsw.org (James Lee) Date: Thu, 11 Dec 2008 19:53:08 GMT Subject: [csw-maintainers] Update of bzip2 and clamav In-Reply-To: References: <91F5D112-4573-440C-9A79-FD0F0C83E2E8@opencsw.org> <20081209.14315300.1742443868@gyor.oxdrove.co.uk> Message-ID: <20081211.19530800.3172256164@gyor.oxdrove.co.uk> On 11/12/08, 09:49:43, Dagobert Michelsen wrote regarding Re: [csw-maintainers] Update of bzip2 and clamav: > >> James: Can we release 1.0.5 to current so I can upgrade it on the > >> farm? > > It's needs burn in and test; you could help by testing it thoroughly. > Works great and you even made 64 bit :-) For me you can push it. I failed it! by trying to compile, sorry, a missing header file. REV 2008.12.11 in testing. It has 64 bit libs which is why I built it, that and I needed 1.0.5 for clamav too. It also has some amd64 binaries so runs >10% faster on compatible machines. Bzip2 is slow and needs help. James. From yann at pleiades.fr.eu.org Thu Dec 11 21:24:27 2008 From: yann at pleiades.fr.eu.org (Yann Rouillard) Date: Thu, 11 Dec 2008 21:24:27 +0100 Subject: [csw-maintainers] openssl vs certs In-Reply-To: <20081211191721.GE33380@bolthole.com> References: <1229022639-sup-2798@ntdws12.chass.utoronto.ca> <20081211191721.GE33380@bolthole.com> Message-ID: <494176FB.3060600@pleiades.fr.eu.org> Philip Brown a ?crit : > On Thu, Dec 11, 2008 at 02:10:55PM -0500, Ben Walton wrote: >> As I've never built openssl, I don't know if this is a build omission >> or simply that the required files weren't manually collected, and >> distributed with the package... > > Sounds like the latter to me. But also sounds like it would be a useful > step for "us" to do. The certificates provided in the openssl source have been completely removed since 0.9.8h. Quoting the changelog: "The OpenSSL project does not recommend any specific CA and does not have any policy with respect to including or excluding any CA. Therefore it does not make any sense to ship an arbitrary selection of root CA certificates with the OpenSSL software." I have kept the previously provided CA certificates in the opencsw package for compatibility purpose but never checked if all standard CA were present in that set. It would make more sense to create a ca-certificates package like Debian, I will work on this. Yann From bwalton at opencsw.org Thu Dec 11 21:30:32 2008 From: bwalton at opencsw.org (Ben Walton) Date: Thu, 11 Dec 2008 15:30:32 -0500 Subject: [csw-maintainers] openssl vs certs In-Reply-To: <494176FB.3060600@pleiades.fr.eu.org> References: <1229022639-sup-2798@ntdws12.chass.utoronto.ca> <20081211191721.GE33380@bolthole.com> <494176FB.3060600@pleiades.fr.eu.org> Message-ID: <1229027374-sup-7244@ntdws12.chass.utoronto.ca> Excerpts from Yann Rouillard's message of Thu Dec 11 15:24:27 -0500 2008: Hi Yann, > I have kept the previously provided CA certificates in the opencsw > package for compatibility purpose but never checked if all > standard CA were present in that set. Ok, that makes sense. > It would make more sense to create a ca-certificates package like > Debian, I will work on this. I agree that this is the best direction to take. Thanks! -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From dam at opencsw.org Thu Dec 11 22:11:19 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 11 Dec 2008 22:11:19 +0100 Subject: [csw-maintainers] Does someone has support for Sun Studio? Message-ID: Hi, we are having at least two candidates for bugs in Sun Studio: - one regular bug - one new bug occurring in 121017-17 and 121018-18 It would be greate if there was a volunteer to open a case and track it at Sun. Best regards -- Dago BTW: I removed the buggy patches from build8s and build8x. From phil at bolthole.com Thu Dec 11 22:14:52 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 11 Dec 2008 13:14:52 -0800 Subject: [csw-maintainers] openssl vs certs In-Reply-To: <494176FB.3060600@pleiades.fr.eu.org> References: <1229022639-sup-2798@ntdws12.chass.utoronto.ca> <20081211191721.GE33380@bolthole.com> <494176FB.3060600@pleiades.fr.eu.org> Message-ID: <20081211211452.GJ33380@bolthole.com> On Thu, Dec 11, 2008 at 09:24:27PM +0100, Yann Rouillard wrote: > .... > I have kept the previously provided CA certificates in the opencsw > package for compatibility purpose but never checked if all > standard CA were present in that set. > > It would make more sense to create a ca-certificates package like > Debian, I will work on this. for historical documentation purposes, would you mention why you believe it "makes more sense" to do this? I am presuming, "because it will be easier to update certs on-demand as needed", and/or "because more than one package can make use of it, even if it doesnt technically use "openssl" (such as GNUtls) From yann at pleiades.fr.eu.org Thu Dec 11 22:31:00 2008 From: yann at pleiades.fr.eu.org (Yann Rouillard) Date: Thu, 11 Dec 2008 22:31:00 +0100 Subject: [csw-maintainers] openssl vs certs In-Reply-To: <20081211211452.GJ33380@bolthole.com> References: <1229022639-sup-2798@ntdws12.chass.utoronto.ca> <20081211191721.GE33380@bolthole.com> <494176FB.3060600@pleiades.fr.eu.org> <20081211211452.GJ33380@bolthole.com> Message-ID: <49418694.5080803@pleiades.fr.eu.org> Philip Brown a ?crit : > On Thu, Dec 11, 2008 at 09:24:27PM +0100, Yann Rouillard wrote: > for historical documentation purposes, would you mention why you believe it > "makes more sense" to do this? > > I am presuming, "because it will be easier to update certs on-demand as > needed", and/or "because more than one package can make use of it, even if > it doesnt technically use "openssl" > (such as GNUtls) And you are presuming well. Yann From yann at pleiades.fr.eu.org Thu Dec 11 22:36:16 2008 From: yann at pleiades.fr.eu.org (Yann Rouillard) Date: Thu, 11 Dec 2008 22:36:16 +0100 Subject: [csw-maintainers] openssl vs certs In-Reply-To: <1229022639-sup-2798@ntdws12.chass.utoronto.ca> References: <1229022639-sup-2798@ntdws12.chass.utoronto.ca> Message-ID: <494187D0.1050607@pleiades.fr.eu.org> Hi Ben, Until ca-certificates is here, you can do: wget http://www.geotrust.com/resources/root_certificates/certificates/Equifax_Secure_Certificate_Authority.cer -O /opt/csw/ssl/certs/equifax.pem /opt/csw/bin/c_rehash /opt/csw/ssl/certs/ to have the certificates recognized by the ssl library. Yann Ben Walton a ?crit : > Hi All, > > A package I'm working on has it's source hosted on a site that is > https only (fedorahosted.org). The ssl cert there is signed by > equifax (as evidenced using: openssl s_client -connect > fedorahosted.org:443 -showcerts). It seems that the CSW openssl > package doesn't provide the required certificate chain to verify it, > which is causing wget to bail out (without extra options, anyway). > > As I've never built openssl, I don't know if this is a build omission > or simply that the required files weren't manually collected, and > distributed with the package...I'll open a bug for this issue if it > actually is a bug. If it's intentional, let me know. [It looks like > rhel provides the equifax cert(s) with openssl and debian/ubuntu via > ca-certificates.] > > For reference, this can be verified via: > /opt/csw/bin/wget https://fedorahosted.org/xmlto/export/1/xmlto-0.0.21.tar.bz2 > > Thanks > -Ben > > > ------------------------------------------------------------------------ > > _______________________________________________ > maintainers mailing list > maintainers at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/maintainers From bonivart at opencsw.org Fri Dec 12 09:53:17 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Fri, 12 Dec 2008 09:53:17 +0100 Subject: [csw-maintainers] [svn] DBD-SQLite upstream update notification In-Reply-To: <200812112312.mBBNCHQd011211@mirror.opencsw.org> References: <200812112312.mBBNCHQd011211@mirror.opencsw.org> Message-ID: <625385e30812120053x43e700e0u72d9d897e703afbc@mail.gmail.com> On Fri, Dec 12, 2008 at 12:12 AM, Upstream Package Watch wrote: > > Hello dear DBD-SQLite maintainer, > > The upstream notification job has detected the availability of new files for DBD-SQLite. > > The following upstream file(s): > DBD-SQLite-1.14.tar.gz Here something must have gone wrong as we already have 1.14..? http://www.opencsw.org/packages/pm_dbdsqlite -- /peter From william at wbonnet.net Fri Dec 12 10:11:32 2008 From: william at wbonnet.net (William Bonnet) Date: Fri, 12 Dec 2008 10:11:32 +0100 Subject: [csw-maintainers] [svn] DBD-SQLite upstream update notification In-Reply-To: <625385e30812120053x43e700e0u72d9d897e703afbc@mail.gmail.com> References: <200812112312.mBBNCHQd011211@mirror.opencsw.org> <625385e30812120053x43e700e0u72d9d897e703afbc@mail.gmail.com> Message-ID: <49422AC4.7050606@wbonnet.net> Hi Peter >> Hello dear DBD-SQLite maintainer, >> >> The upstream notification job has detected the availability of new files for DBD-SQLite. >> >> The following upstream file(s): >> DBD-SQLite-1.14.tar.gz >> > > Here something must have gone wrong as we already have 1.14..? > > http://www.opencsw.org/packages/pm_dbdsqlite > That's right version 1.14 is in the catalog, but GAR has only version 1.13 in the Makefile. The script is running using information from GAR, not from the catalog. This package is kind of a "special" case. I was expecting to have packages newer in GAR than in the catalog (ie package not yet released). Not packages newer in the catalog than in GAR. This case means package has been added to GAR, then a newer package has been released without using GAR. Which should not happen (IMHO). Can you please update the Makefile in GAR ? Then the script will not warn you until 1.15 Thanks in advance cheers, W. From bonivart at opencsw.org Fri Dec 12 10:29:03 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Fri, 12 Dec 2008 10:29:03 +0100 Subject: [csw-maintainers] [svn] DBD-SQLite upstream update notification In-Reply-To: <49422AC4.7050606@wbonnet.net> References: <200812112312.mBBNCHQd011211@mirror.opencsw.org> <625385e30812120053x43e700e0u72d9d897e703afbc@mail.gmail.com> <49422AC4.7050606@wbonnet.net> Message-ID: <625385e30812120129l7a427ceft8cfc63fac5e238fe@mail.gmail.com> On Fri, Dec 12, 2008 at 10:11 AM, William Bonnet wrote: > That's right version 1.14 is in the catalog, but GAR has only version > 1.13 in the Makefile. The script is running using information from GAR, > not from the catalog. This package is kind of a "special" case. I was > expecting to have packages newer in GAR than in the catalog (ie package > not yet released). Not packages newer in the catalog than in GAR. This > case means package has been added to GAR, then a newer package has been > released without using GAR. Which should not happen (IMHO). Sounds reasonable. I don't remember if I was tinkering with this package in GAR or maybe someone else did but the current one is built outside of GAR, that's correct. > Can you please update the Makefile in GAR ? Then the script will not > warn you until 1.15 Will do. :-) -- /peter From ihsan at opencsw.org Fri Dec 12 10:51:58 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Fri, 12 Dec 2008 10:51:58 +0100 Subject: [csw-maintainers] KDE on build machines In-Reply-To: <20081209171444.GB35059@bolthole.com> References: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> <392323F5-EF0D-4DC4-BCB2-2EAAC80979AE@opencsw.org> <6227ac8cb62a6524ebc5c0e3980ce24d@localhost> <20081209171444.GB35059@bolthole.com> Message-ID: <4942343E.4020207@opencsw.org> Am 9.12.2008 18:14 Uhr, Philip Brown schrieb: > even on the "3 series", there is 3.5.10 released aug 2008 > Seems like there is somewhat of a parallel stream of v3 compared to v4 kde. Because the first 4.0 release was not considered as a stable release for end users. Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From ihsan at opencsw.org Fri Dec 12 10:57:56 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Fri, 12 Dec 2008 10:57:56 +0100 Subject: [csw-maintainers] /testing clamav 0.94.2 In-Reply-To: <625385e30812110758x668c1fa7v78b44530f9a628b5@mail.gmail.com> References: <625385e30812110758x668c1fa7v78b44530f9a628b5@mail.gmail.com> Message-ID: <494235A4.8070700@opencsw.org> Am 11.12.2008 16:58 Uhr, Peter Bonivart schrieb: > By the way, I have updated the wiki page about CSWcswclassutils to > include instructions on how to use it in GAR. Take a look. Dago, could you mention the cswclassutils also on http://apps.sourceforge.net/mediawiki/gar/index.php?title=Main_Page ? Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From bonivart at opencsw.org Fri Dec 12 11:08:41 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Fri, 12 Dec 2008 11:08:41 +0100 Subject: [csw-maintainers] [svn] Text-Reform upstream update notification In-Reply-To: <200812120922.mBC9Mq7l024094@mirror.opencsw.org> References: <200812120922.mBC9Mq7l024094@mirror.opencsw.org> Message-ID: <625385e30812120208o66f7b8bboa71afd1d0ab051fd@mail.gmail.com> On Fri, Dec 12, 2008 at 10:22 AM, Upstream Package Watch wrote: > > Hello dear Text-Reform maintainer, > > The upstream notification job has detected the availability of new files for Text-Reform. > > The following upstream file(s): > Text-Reform-1.11.tar.gz How about this? In gar it's 1.12.2..? -- /peter From william at wbonnet.net Fri Dec 12 11:16:56 2008 From: william at wbonnet.net (William Bonnet) Date: Fri, 12 Dec 2008 11:16:56 +0100 Subject: [csw-maintainers] [svn] DBD-SQLite upstream update notification In-Reply-To: <625385e30812120129l7a427ceft8cfc63fac5e238fe@mail.gmail.com> References: <200812112312.mBBNCHQd011211@mirror.opencsw.org> <625385e30812120053x43e700e0u72d9d897e703afbc@mail.gmail.com> <49422AC4.7050606@wbonnet.net> <625385e30812120129l7a427ceft8cfc63fac5e238fe@mail.gmail.com> Message-ID: <49423A18.1000408@wbonnet.net> Thanks :) > On Fri, Dec 12, 2008 at 10:11 AM, William Bonnet wrote: > >> That's right version 1.14 is in the catalog, but GAR has only version >> 1.13 in the Makefile. The script is running using information from GAR, >> not from the catalog. This package is kind of a "special" case. I was >> expecting to have packages newer in GAR than in the catalog (ie package >> not yet released). Not packages newer in the catalog than in GAR. This >> case means package has been added to GAR, then a newer package has been >> released without using GAR. Which should not happen (IMHO). >> > > Sounds reasonable. I don't remember if I was tinkering with this > package in GAR or maybe someone else did but the current one is built > outside of GAR, that's correct. > > >> Can you please update the Makefile in GAR ? Then the script will not >> warn you until 1.15 >> > > Will do. :-) > > From william at wbonnet.net Fri Dec 12 11:29:24 2008 From: william at wbonnet.net (William Bonnet) Date: Fri, 12 Dec 2008 11:29:24 +0100 Subject: [csw-maintainers] [svn] Text-Reform upstream update notification In-Reply-To: <625385e30812120208o66f7b8bboa71afd1d0ab051fd@mail.gmail.com> References: <200812120922.mBC9Mq7l024094@mirror.opencsw.org> <625385e30812120208o66f7b8bboa71afd1d0ab051fd@mail.gmail.com> Message-ID: <49423D04.2050406@wbonnet.net> Hi Peter > On Fri, Dec 12, 2008 at 10:22 AM, Upstream Package Watch > wrote: > >> Hello dear Text-Reform maintainer, >> >> The upstream notification job has detected the availability of new files for Text-Reform. >> >> The following upstream file(s): >> Text-Reform-1.11.tar.gz >> > > How about this? In gar it's 1.12.2..? > This one is a nasty one :) They changed the way they name the file... If you have a look to the dir you'll see Text-Reform-1.08.readme 02-Apr-2003 22:27 1.0K Text-Reform-1.08.tar.gz 02-Apr-2003 22:34 18K Text-Reform-1.10.readme 09-Apr-2003 08:49 1.0K Text-Reform-1.10.tar.gz 09-Apr-2003 08:54 20K Text-Reform-1.11.readme 07-May-2003 09:43 1.1K Text-Reform-1.11.tar.gz 07-May-2003 09:46 20K Text-Reform-v1.12.2.meta 29-Sep-2007 19:10 383 Text-Reform-v1.12.2.readme 29-Sep-2007 19:10 697 Text-Reform-v1.12.2.tar.gz 29-Sep-2007 19:12 24K They added a 'v' between the name and the version. It's not your fault, the package is up to date. I'll try to fix the regexp. But this may happen again, and there is nothing i can do about this :( cheers W. From bonivart at opencsw.org Fri Dec 12 22:43:03 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Fri, 12 Dec 2008 22:43:03 +0100 Subject: [csw-maintainers] ClamAV - to include the (obsolete) signatures or not? Message-ID: <625385e30812121343s703126b2jdb11a09be2e2de0e@mail.gmail.com> I'm packaging ClamAV (please help test it, see link below) and I'm wondering what you think about including the virus signatures. The signature database files are about 18 MB if I remember correctly and doesn't compress much so the package becomes around 20 MB. From a security point of view it's not wise to use ClamAV with the included signatures since they are becoming more obsolete for every day passing since source release (November 26th). On the other hand you can't scan at all without a signature database and must start by downloading one with the freshclam command, which is really what everyone should do anyway. Should we provide a 20 MB package fully operational which needs updating or should we provide a 2 MB package which *must* be updated? If the second alternative, is it good enough to inform the user about this via the postinstall script for example? An automated run of freshclam will not work in most cases without some simple configuration which can't be guessed by me. A third alternative would be, like many Linux dists do, to separate the database to its own package but I only see that as viable option if I would constantly update that package which would be...stupid...when there's a perfect solution provided with ClamAV for that. If we make the signature package not a required dependency to main ClamAV users will miss it and we're no better off. http://buildfarm.opencsw.org/testing.html (look for clamav and libclamav) -- /peter From phil at bolthole.com Fri Dec 12 22:49:12 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 12 Dec 2008 13:49:12 -0800 Subject: [csw-maintainers] ClamAV - to include the (obsolete) signatures or not? In-Reply-To: <625385e30812121343s703126b2jdb11a09be2e2de0e@mail.gmail.com> References: <625385e30812121343s703126b2jdb11a09be2e2de0e@mail.gmail.com> Message-ID: <20081212214911.GI94990@bolthole.com> On Fri, Dec 12, 2008 at 10:43:03PM +0100, Peter Bonivart wrote: > .... > Should we provide a 20 MB package fully operational which needs > updating or should we provide a 2 MB package which *must* be updated? > > If the second alternative, is it good enough to inform the user about > this via the postinstall script for example? An automated run of > freshclam will not work in most cases without some simple > configuration which can't be guessed by me. how about you mention some of the problems hindering an automated run, and see if people here have ideas on how to overcome them? As a first shot: if the package is virtually useless without regular updates, then seems like you would want to have some kind of "out of date" check automatically built in, to be of maximum use to our users. If you have such a thing, then perhaps you might trigger that to always get called at "first run", and then also prompt for any missing information at that time? From bonivart at opencsw.org Fri Dec 12 23:13:05 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Fri, 12 Dec 2008 23:13:05 +0100 Subject: [csw-maintainers] ClamAV - to include the (obsolete) signatures or not? In-Reply-To: <20081212214911.GI94990@bolthole.com> References: <625385e30812121343s703126b2jdb11a09be2e2de0e@mail.gmail.com> <20081212214911.GI94990@bolthole.com> Message-ID: <625385e30812121413y597fb8c1v41746f8d12a28647@mail.gmail.com> On Fri, Dec 12, 2008 at 10:49 PM, Philip Brown wrote: > how about you mention some of the problems hindering an automated run, and > see if people here have ideas on how to overcome them? It's the usual stuff with mirror, proxy and so on. In most corporate environments a run of an unconfigured freshclam would just hang. > As a first shot: > > if the package is virtually useless without regular updates, then seems > like you would want to have some kind of "out of date" check automatically > built in, to be of maximum use to our users. The software already features this, warning about obsolete signatures at every scan for example. > If you have such a thing, then perhaps you might trigger that to always get > called at "first run", and then also prompt for any missing information at > that time? See above, ClamAV will surely let you know that you're lacking signatures. -- /peter From phil at bolthole.com Sat Dec 13 01:03:09 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 12 Dec 2008 16:03:09 -0800 Subject: [csw-maintainers] libiconv Message-ID: <20081213000309.GM94990@bolthole.com> fyi: i just updated iconv. beware :-) From phil at bolthole.com Sat Dec 13 01:04:13 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 12 Dec 2008 16:04:13 -0800 Subject: [csw-maintainers] ClamAV - to include the (obsolete) signatures or not? In-Reply-To: <625385e30812121413y597fb8c1v41746f8d12a28647@mail.gmail.com> References: <625385e30812121343s703126b2jdb11a09be2e2de0e@mail.gmail.com> <20081212214911.GI94990@bolthole.com> <625385e30812121413y597fb8c1v41746f8d12a28647@mail.gmail.com> Message-ID: <20081213000413.GN94990@bolthole.com> On Fri, Dec 12, 2008 at 11:13:05PM +0100, Peter Bonivart wrote: > On Fri, Dec 12, 2008 at 10:49 PM, Philip Brown wrote: > > how about you mention some of the problems hindering an automated run, and > > see if people here have ideas on how to overcome them? > > It's the usual stuff with mirror, proxy and so on. In most corporate > environments a run of an unconfigured freshclam would just hang. well... you have a place to look for that sort of thing, though. pkg-get or pkgutil configs. From bwalton at opencsw.org Sat Dec 13 02:11:37 2008 From: bwalton at opencsw.org (Ben Walton) Date: Fri, 12 Dec 2008 20:11:37 -0500 Subject: [csw-maintainers] policy on .la files? Message-ID: <1229130661-sup-7678@ntdws12.chass.utoronto.ca> Hi All, Is there a policy (or even a strong preference) on whether or not to ship the libtool .la files with a package? Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From james at opencsw.org Sat Dec 13 11:55:42 2008 From: james at opencsw.org (James Lee) Date: Sat, 13 Dec 2008 10:55:42 GMT Subject: [csw-maintainers] ClamAV - to include the (obsolete) signatures or not? In-Reply-To: <625385e30812121343s703126b2jdb11a09be2e2de0e@mail.gmail.com> References: <625385e30812121343s703126b2jdb11a09be2e2de0e@mail.gmail.com> Message-ID: <20081213.10554200.2999473139@gyor.oxdrove.co.uk> On 12/12/08, 21:43:03, Peter Bonivart wrote regarding [csw-maintainers] ClamAV - to include the (obsolete) signatures or not?: > I'm packaging ClamAV (please help test it, see link below) and I'm > wondering what you think about including the virus signatures. The > signature database files are about 18 MB if I remember correctly and > doesn't compress much so the package becomes around 20 MB. From a > security point of view it's not wise to use ClamAV with the included > signatures since they are becoming more obsolete for every day passing > since source release (November 26th). On the other hand you can't scan > at all without a signature database and must start by downloading one > with the freshclam command, which is really what everyone should do > anyway. > Should we provide a 20 MB package fully operational which needs > updating or should we provide a 2 MB package which *must* be updated? The latter, leave them out and force the use of freshclam. Any existing users doing update should have newer "main" and "daily" files than in the package so won't want the older ones in a package. > If the second alternative, is it good enough to inform the user about > this via the postinstall script for example? An automated run of > freshclam will not work in most cases without some simple > configuration which can't be guessed by me. Why doesn't a default install work? Freshclam will download the full files if it finds none, e.g. the first time. "DatabaseMirror db.local.clamav.net" should resolve to a suitable site, prove this by running "nslookup db.local.clamav.net" and it will show a list of places local to yourself. It's possible to add to crontab with postinstall (a new challenge to cswclassutils?) but maybe freshclam in daemon mode is better anyway, (variable time, control run level, control its stop and start). > A third alternative would be, like many Linux dists do, to separate > the database to its own package but I only see that as viable option > if I would constantly update that package which would > be...stupid...when there's a perfect solution provided with ClamAV for > that. Yes stupid! The perfect solution is clamav's freshclam. James. From bonivart at opencsw.org Sat Dec 13 12:28:13 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Sat, 13 Dec 2008 12:28:13 +0100 Subject: [csw-maintainers] ClamAV - to include the (obsolete) signatures or not? In-Reply-To: <20081213.10554200.2999473139@gyor.oxdrove.co.uk> References: <625385e30812121343s703126b2jdb11a09be2e2de0e@mail.gmail.com> <20081213.10554200.2999473139@gyor.oxdrove.co.uk> Message-ID: <625385e30812130328o7b20acf6l53ad92db7bceeff@mail.gmail.com> On Sat, Dec 13, 2008 at 11:55 AM, James Lee wrote: > "DatabaseMirror db.local.clamav.net" should resolve to a suitable site, > prove this by running "nslookup db.local.clamav.net" and it will > show a list of places local to yourself. The mirror is not a showstopper, that's correct, but the proxy settings may be in many (most?) environments. Trying to find those in wgetrc, pkg-get.conf or other files doesn't feel right. As far as I know freshclam doesn't pick up proxy settings from the environment, it wants it configured in freshclam.conf. It's also quite common not to have internet access at all but to set up a freshclam proxy to connect to. > It's possible to add to crontab with postinstall (a new challenge to > cswclassutils?) but maybe freshclam in daemon mode is better anyway, > (variable time, control run level, control its stop and start). The crontab idea is really cool! I have added that to the wiki page for cswclassutils as a possible future addition. http://wiki.opencsw.org/cswclassutils It would be simple to provide a start script for freshclam in the package and let cswclassutils set it up. Maybe I should do that anyway? However, it doesn't change the fact that a Clam package without the db's does not work out of the tin as someone said to me. It doesn't even handle it gracefully according to me. If you check your version you get an incomplete message returned which may not make you suspicious of anything wrong. If you try to scan it will complain about missing signatures but break with more weird info and none about how to fix it (run freshclam in most cases). Maybe it's not worth the trouble to save 15 MB of download with todays connections, web caches and local distribution and so on? I'm all for splitting packages to reduce bloat, especially now when it's real easy in GAR v2, but in this case it probably will cause problems for some users. -- /peter From dam at opencsw.org Sat Dec 13 13:26:28 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sat, 13 Dec 2008 13:26:28 +0100 Subject: [csw-maintainers] policy on .la files? In-Reply-To: <1229130661-sup-7678@ntdws12.chass.utoronto.ca> References: <1229130661-sup-7678@ntdws12.chass.utoronto.ca> Message-ID: Hi Ben, Am 13.12.2008 um 02:11 schrieb Ben Walton: > Is there a policy (or even a strong preference) on whether or not to > ship the libtool .la files with a package? The OpenCSW standard says to exclude .la files. I just had a lively discussion with Phil wheter to change that and include .la-files again. If you have hard technical facts why to include them I would be interested to hear them. Best regards -- Dago From bwalton at opencsw.org Sat Dec 13 13:37:39 2008 From: bwalton at opencsw.org (Ben Walton) Date: Sat, 13 Dec 2008 07:37:39 -0500 Subject: [csw-maintainers] policy on .la files? In-Reply-To: References: <1229130661-sup-7678@ntdws12.chass.utoronto.ca> Message-ID: <1229171325-sup-4398@ntdws12.chass.utoronto.ca> Excerpts from Dagobert Michelsen's message of Sat Dec 13 07:26:28 -0500 2008: Hi Dago, > The OpenCSW standard says to exclude .la files. I just had > a lively discussion with Phil wheter to change that and > include .la-files again. If you have hard technical facts > why to include them I would be interested to hear them. I don't have a preference either way really. I had simply noticed that some systems (rhel, debian, csw) seemed to include more .la files than others and was curious what others thought about it. AFAIK, the only real advantage to them is that it saves libtool having to go back to 'first principles' later on...Since this is all done at the packaging step though, I don't see it as a big deal. _Some_ users might be annoyed if they build things locally against CSW libs, as they might miss having that info handy...but then again, on modern systems...? [Speaking as someone that only just recently retired some sparc station 5's from active service! ] Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From dam at opencsw.org Sat Dec 13 13:54:16 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sat, 13 Dec 2008 13:54:16 +0100 Subject: [csw-maintainers] New catalog "unstrict" Message-ID: <4F18B3FA-F0C3-41CA-A77E-9DD9E9BBF135@opencsw.org> Hi, I want to pick up the thread on a more open catalog ("unstrict/" or "open/") which is a superset of current/ where it is not necessary to provide versions for all Solaris releases or sparc/x86. Being able to migrate freely between sparc and x86 and being able to upgrade Solaris versions for current/ I consider very important. The separate catalog should make clear that this strict policy is not valid when using the other catalog. That means "unstrict" contains all packages from current, but additional ones like cvsup, opera, tme etc. Best regards -- Dago From pfelecan at opencsw.org Sat Dec 13 15:54:20 2008 From: pfelecan at opencsw.org (Peter FELECAN) Date: Sat, 13 Dec 2008 15:54:20 +0100 Subject: [csw-maintainers] Summary of IRL Meeting In-Reply-To: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> (Dagobert Michelsen's message of "Mon\, 8 Dec 2008 12\:37\:32 +0100") References: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> Message-ID: Dagobert Michelsen writes: > Membership > ---------- > > The participants of the meeting are the founding members. It is > legally not possible to just grab people and make them members if > they have not applied for membership. So every maintainer will > get an email within the next few days asking if they want to > apply for membership. A simple reply with "I want to apply for > membership" is enough. The board will usually accept membership > and will post about all membership applications. Now, that I read the bylaws and have seen the photos, I'm still waiting for the above mentioned email. Or, maybe I'm no more a maintainer? Let me know. BTW, I don't see any mention of what was decided on the many points collected for discussion at http://wiki.opencsw.org/irl-meeting -- Peter From phil at bolthole.com Sat Dec 13 16:42:06 2008 From: phil at bolthole.com (Philip Brown) Date: Sat, 13 Dec 2008 07:42:06 -0800 Subject: [csw-maintainers] ClamAV - to include the (obsolete) signatures or not? In-Reply-To: <625385e30812130328o7b20acf6l53ad92db7bceeff@mail.gmail.com> References: <625385e30812121343s703126b2jdb11a09be2e2de0e@mail.gmail.com> <20081213.10554200.2999473139@gyor.oxdrove.co.uk> <625385e30812130328o7b20acf6l53ad92db7bceeff@mail.gmail.com> Message-ID: <20081213154206.GB77030@bolthole.com> On Sat, Dec 13, 2008 at 12:28:13PM +0100, Peter Bonivart wrote: > > Maybe it's not worth the trouble to save 15 MB of download with todays > connections, web caches and local distribution and so on? well, it still would be worth it in the general case. but for a package that by definition will be obsolete within a few weeks... not so much. From dam at opencsw.org Sat Dec 13 18:08:17 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sat, 13 Dec 2008 18:08:17 +0100 Subject: [csw-maintainers] Summary of IRL Meeting In-Reply-To: References: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> Message-ID: Hi Peter, Am 13.12.2008 um 15:54 schrieb Peter FELECAN: > Now, that I read the bylaws and have seen the photos, I'm still > waiting for the above mentioned email. Fist take my apologies that the email has not beed sent out yet. For a smooth membership invitation there need to be some changes to the mailinglists and aliases. It was a real busy week for Ihsan and he just hasn't time to do so. When this is finished hopefully this weekend the email will go out. > Or, maybe I'm no more a maintainer? Let me know. Of course you are :-) > BTW, I don't see any mention of what was decided on the many points > collected for discussion at http://wiki.opencsw.org/irl-meeting There are two reasons for this: One was lack of time as we felt it was more important to focus on a unified understanding of what the association should look like. The other was that it was not intended to decide on these things as the founding members don't "just decide" and that's it - the outcoming of these things will be after a hopefully lively discussions on the members list after all of you have been invited. The goal of the meeting was not the participants to become a new ruling class, but to open up for a more democratic process focused on the needs of active maintainers. Best regards -- Dago From pfelecan at opencsw.org Sat Dec 13 15:34:11 2008 From: pfelecan at opencsw.org (Peter FELECAN) Date: Sat, 13 Dec 2008 15:34:11 +0100 Subject: [csw-maintainers] policy on .la files? In-Reply-To: (Dagobert Michelsen's message of "Sat\, 13 Dec 2008 13\:26\:28 +0100") References: <1229130661-sup-7678@ntdws12.chass.utoronto.ca> Message-ID: Dagobert Michelsen writes: > Am 13.12.2008 um 02:11 schrieb Ben Walton: >> Is there a policy (or even a strong preference) on whether or not to >> ship the libtool .la files with a package? > > The OpenCSW standard says to exclude .la files. I just had > a lively discussion with Phil wheter to change that and > include .la-files again. If you have hard technical facts > why to include them I would be interested to hear them. It helps the libtool job, consequently I think that it's a good thing to include them. -- Peter From phil at bolthole.com Sat Dec 13 19:09:44 2008 From: phil at bolthole.com (Philip Brown) Date: Sat, 13 Dec 2008 10:09:44 -0800 Subject: [csw-maintainers] policy on .la files? In-Reply-To: References: <1229130661-sup-7678@ntdws12.chass.utoronto.ca> Message-ID: <20081213180944.GA84919@bolthole.com> On Sat, Dec 13, 2008 at 03:34:11PM +0100, Peter FELECAN wrote: > > The OpenCSW standard says to exclude .la files. I just had > > a lively discussion with Phil wheter to change that and > > include .la-files again. If you have hard technical facts > > why to include them I would be interested to hear them. > > It helps the libtool job, consequently I think that it's a good thing > to include them. it doesnt really help much. and sometimes, it even gets in the way. as a comparison, debian has technically banned them, although apparently some packages still have them. To put it another way: If a libtool file actually ADDED VALUE somehow, like adding some required compiler flags in, then by all means keep it. but otherwise, they just leave a mess From pfelecan at opencsw.org Sat Dec 13 19:24:25 2008 From: pfelecan at opencsw.org (Peter FELECAN) Date: Sat, 13 Dec 2008 19:24:25 +0100 Subject: [csw-maintainers] Summary of IRL Meeting In-Reply-To: (Dagobert Michelsen's message of "Sat\, 13 Dec 2008 18\:08\:17 +0100") References: <66F16CEE-AEE1-4BF2-8EF7-99749698FD32@opencsw.org> Message-ID: Dagobert Michelsen writes: > Am 13.12.2008 um 15:54 schrieb Peter FELECAN: >> Now, that I read the bylaws and have seen the photos, I'm still >> waiting for the above mentioned email. > > Fist take my apologies that the email has not beed sent out yet. > For a smooth membership invitation there need to be some changes > to the mailinglists and aliases. It was a real busy week for Ihsan > and he just hasn't time to do so. When this is finished hopefully > this weekend the email will go out. Fine. >> BTW, I don't see any mention of what was decided on the many points >> collected for discussion at http://wiki.opencsw.org/irl-meeting > > There are two reasons for this: One was lack of time as we > felt it was more important to focus on a unified understanding > of what the association should look like. The other was that it > was not intended to decide on these things as the founding > members don't "just decide" and that's it - the outcoming > of these things will be after a hopefully lively discussions > on the members list after all of you have been invited. > The goal of the meeting was not the participants to become > a new ruling class, but to open up for a more democratic > process focused on the needs of active maintainers. Alright. Don't lose that list. I'm eager to see how democracy works. Thank you Dago for the answers, they are appreciated. -- Peter From james at opencsw.org Sun Dec 14 10:58:01 2008 From: james at opencsw.org (James Lee) Date: Sun, 14 Dec 2008 09:58:01 GMT Subject: [csw-maintainers] ClamAV - to include the (obsolete) signatures or not? In-Reply-To: <625385e30812130328o7b20acf6l53ad92db7bceeff@mail.gmail.com> References: <625385e30812121343s703126b2jdb11a09be2e2de0e@mail.gmail.com> <20081213.10554200.2999473139@gyor.oxdrove.co.uk> <625385e30812130328o7b20acf6l53ad92db7bceeff@mail.gmail.com> Message-ID: <20081214.9580100.668625779@gyor.oxdrove.co.uk> On 13/12/08, 11:28:13, Peter Bonivart wrote regarding Re: [csw-maintainers] ClamAV - to include the (obsolete) signatures or not?: > The mirror is not a showstopper, that's correct, but the proxy > settings may be in many (most?) environments. Trying to find those in > wgetrc, pkg-get.conf or other files doesn't feel right. As far as I > know freshclam doesn't pick up proxy settings from the environment, it > wants it configured in freshclam.conf. It's also quite common not to > have internet access at all but to set up a freshclam proxy to connect > to. I've missed something here because the idea of a mail server that doesn't have access to the internet is strange to me - especially one that is looking for viruses. I would think most environments would have transparent access to the internet and those who have set up their own proxies should know how to deal with the environment that they themselves create. > > It's possible to add to crontab with postinstall (a new challenge to > > cswclassutils?) but maybe freshclam in daemon mode is better anyway, > > (variable time, control run level, control its stop and start). > The crontab idea is really cool! I have added that to the wiki page > for cswclassutils as a possible future addition. > http://wiki.opencsw.org/cswclassutils > It would be simple to provide a start script for freshclam in the > package and let cswclassutils set it up. Maybe I should do that > anyway? If would be easier to set a the fetch intervals - done via freshclam.conf option not crontab edit and makes it less regular. James. From james at opencsw.org Sun Dec 14 11:00:34 2008 From: james at opencsw.org (James Lee) Date: Sun, 14 Dec 2008 10:00:34 GMT Subject: [csw-maintainers] New catalog "unstrict" In-Reply-To: <4F18B3FA-F0C3-41CA-A77E-9DD9E9BBF135@opencsw.org> References: <4F18B3FA-F0C3-41CA-A77E-9DD9E9BBF135@opencsw.org> Message-ID: <20081214.10003400.2052822375@gyor.oxdrove.co.uk> On 13/12/08, 12:54:16, Dagobert Michelsen wrote regarding [csw-maintainers] New catalog "unstrict": > I want to pick up the thread on a more open catalog > ("unstrict/" or "open/") which is a superset of current/ > where it is not necessary to provide versions for all > Solaris releases or sparc/x86. Being able to migrate > freely between sparc and x86 and being able to upgrade > Solaris versions for current/ I consider very important. > The separate catalog should make clear that this strict > policy is not valid when using the other catalog. That > means "unstrict" contains all packages from current, but > additional ones like cvsup, opera, tme etc. "unstrict" isn't a word, I guess "lenient" is the closest although perhaps "noncompliant" is what you mean. It's a slippery slope. The deal is that to share in the efforts of others one has to make the effort to support others perhaps in areas that are of no direct need to yourself. The indirect need is that your contribution become part of a wider entity that adds weight to your own contribution and the whole. Where there is a case for a particular package we should allow asymmetry. However there has to be a valid case, not just "it didn't compile first time". Example could be a tool to analyse Solaris 10 only features (zones, ZFS, dtrace) but take care that the depends don't knock out otherwise useful packages. James. From james at opencsw.org Sun Dec 14 11:01:26 2008 From: james at opencsw.org (James Lee) Date: Sun, 14 Dec 2008 10:01:26 GMT Subject: [csw-maintainers] ClamAV - to include the (obsolete) signatures or not? In-Reply-To: <20081213154206.GB77030@bolthole.com> References: <625385e30812121343s703126b2jdb11a09be2e2de0e@mail.gmail.com> <20081213.10554200.2999473139@gyor.oxdrove.co.uk> <625385e30812130328o7b20acf6l53ad92db7bceeff@mail.gmail.com> <20081213154206.GB77030@bolthole.com> Message-ID: <20081214.10012600.1379437586@gyor.oxdrove.co.uk> On 13/12/08, 15:42:06, Philip Brown wrote regarding Re: [csw-maintainers] ClamAV - to include the (obsolete) signatures or not?: > On Sat, Dec 13, 2008 at 12:28:13PM +0100, Peter Bonivart wrote: > > > > Maybe it's not worth the trouble to save 15 MB of download with todays > > connections, web caches and local distribution and so on? > well, it still would be worth it in the general case. but for a package > that by definition will be obsolete within a few weeks... not so much. It's superseded in hours and it's obsolescence is progressive thereafter. Having an up-to-date virus database is what clamav is about. James. From william at wbonnet.net Sun Dec 14 15:21:58 2008 From: william at wbonnet.net (William Bonnet) Date: Sun, 14 Dec 2008 15:21:58 +0100 Subject: [csw-maintainers] old blastwave home dirs In-Reply-To: <49381332.1000800@cognigencorp.com> References: <49381332.1000800@cognigencorp.com> Message-ID: <49451686.1060508@wbonnet.net> Hi Darin > Do we still have access to the blastwave home directories? I'd like to > be able to get at all my old docs and crap. I am reading some old mails... :) Did you retrieved your old home dir ? cheers W. -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.blastwave.org An OpenSolaris Community Site http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From phil at bolthole.com Sun Dec 14 17:21:44 2008 From: phil at bolthole.com (Philip Brown) Date: Sun, 14 Dec 2008 08:21:44 -0800 Subject: [csw-maintainers] New catalog "unstrict" In-Reply-To: <4F18B3FA-F0C3-41CA-A77E-9DD9E9BBF135@opencsw.org> References: <4F18B3FA-F0C3-41CA-A77E-9DD9E9BBF135@opencsw.org> Message-ID: <20081214162144.GA56807@bolthole.com> On Sat, Dec 13, 2008 at 01:54:16PM +0100, Dagobert Michelsen wrote: > means "unstrict" contains all packages from current, but > additional ones like cvsup, opera, tme etc. whats the problem with cvsup? i would think that conceptually it would be relatively simple, and run on anything From dam at opencsw.org Sun Dec 14 22:20:00 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 14 Dec 2008 22:20:00 +0100 Subject: [csw-maintainers] New catalog "unstrict" In-Reply-To: <20081214162144.GA56807@bolthole.com> References: <4F18B3FA-F0C3-41CA-A77E-9DD9E9BBF135@opencsw.org> <20081214162144.GA56807@bolthole.com> Message-ID: Hi Phil, Am 14.12.2008 um 17:21 schrieb Philip Brown: > On Sat, Dec 13, 2008 at 01:54:16PM +0100, Dagobert Michelsen wrote: >> means "unstrict" contains all packages from current, but >> additional ones like cvsup, opera, tme etc. > whats the problem with cvsup? It is difficult to build and impossible to build for x86. Am 19.11.2007 um 04:45 schrieb Philip Brown: > On Sun, Nov 18, 2007 at 10:53:29PM +0100, Dagobert Michelsen wrote: >> Additionally I would like to package CVSup, which is available for >> Sparc only, as Modula-3 (ezlm3) hasn't been ported to Solaris x86 >> yet. >> As it is a pain to build a package would definitely be useful, even >> for Sparc only. >> >> Are these two allowed? > > nope. sorry.. > > try porting ezlm3 :-D > > (I am shocked and horrified that such a popular program such as > CVSup, is not more > arch-neutral?!?! /gasps ) > > erm... from cvsup.org, it appears that modula3 is for "building" it? > but not for running it? > > > > another observation: ezlm3 is only ONE implementation. but any > modula-c > implementation will do. > > you might try poking at some of the other free ones, such as listed > on: > > http://www.thefreecountry.com/compilers/modula3.shtml > > (and then maybe make packages of the one that works? :-D ) Am 14.12.2008 um 17:21 schrieb Philip Brown: > whats the problem with cvsup? > i would think that conceptually it would be relatively simple, and > run on > anything Nope. Making the x86 version requires porting the compiler to another assembly backend. Making an ezlm3 (ez = Easy, SIC!) for packaging is quite hard, making the other Modula-3 implementations compile under Solaris is almost impossible. Or I am too dumb for it ;-) However, I would like to have a cvsup package as it is useful from time to time (e. g. mirroring OpenLDAPs CVS). Best regards -- Dago From dam at opencsw.org Sun Dec 14 22:23:47 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 14 Dec 2008 22:23:47 +0100 Subject: [csw-maintainers] New catalog "unstrict" In-Reply-To: <20081214.10003400.2052822375@gyor.oxdrove.co.uk> References: <4F18B3FA-F0C3-41CA-A77E-9DD9E9BBF135@opencsw.org> <20081214.10003400.2052822375@gyor.oxdrove.co.uk> Message-ID: Hi James, Am 14.12.2008 um 11:00 schrieb James Lee: > On 13/12/08, 12:54:16, Dagobert Michelsen wrote > regarding > [csw-maintainers] New catalog "unstrict": > >> I want to pick up the thread on a more open catalog >> ("unstrict/" or "open/") which is a superset of current/ >> where it is not necessary to provide versions for all >> Solaris releases or sparc/x86. Being able to migrate >> freely between sparc and x86 and being able to upgrade >> Solaris versions for current/ I consider very important. >> The separate catalog should make clear that this strict >> policy is not valid when using the other catalog. That >> means "unstrict" contains all packages from current, but >> additional ones like cvsup, opera, tme etc. > > "unstrict" isn't a word, I guess "lenient" is the closest although > perhaps "noncompliant" is what you mean. Someone said this term is used at some Linux distribution. Trygve? William? Sorry, can't remember. > It's a slippery slope. The deal is that to share in the efforts of > others one has to make the effort to support others perhaps in areas > that are of no direct need to yourself. The indirect need is that > your contribution become part of a wider entity that adds weight to > your own contribution and the whole. > > Where there is a case for a particular package we should allow > asymmetry. However there has to be a valid case, not just "it didn't > compile first time". Example could be a tool to analyse Solaris > 10 only features (zones, ZFS, dtrace) but take care that the depends > don't knock out otherwise useful packages. We already have dtracetoolkit. How about the vendor does not make a version (like Opera Solaris 8 x86, right?) or there is no assembly backend (like for CVsup Solaris x86). Theoretically this could be written, but is a much bigger work than tweaking flags or writing a couple-of-lines patch. Best regards -- Dago From phil at bolthole.com Sun Dec 14 22:54:32 2008 From: phil at bolthole.com (Philip Brown) Date: Sun, 14 Dec 2008 13:54:32 -0800 Subject: [csw-maintainers] modula3, cvsup Message-ID: <20081214215432.GA79803@bolthole.com> I would like to point out, after digging around the web a bit, reguarding cvsup and modula3, that: 1. Module3 is a dead, dead language :-) 2.http://en.wikipedia.org/wiki/CVSup references "csup" as "a rewrite of cvsup in C" http://www.mu.org/~mux/csup.html From dam at opencsw.org Sun Dec 14 22:58:05 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 14 Dec 2008 22:58:05 +0100 Subject: [csw-maintainers] modula3, cvsup In-Reply-To: <20081214215432.GA79803@bolthole.com> References: <20081214215432.GA79803@bolthole.com> Message-ID: <529594F9-1F6C-4BD1-B82E-A4A1A80CE746@opencsw.org> Hi Phil, Am 14.12.2008 um 22:54 schrieb Philip Brown: > 1. Module3 is a dead, dead language :-) Yes, I know. > 2.http://en.wikipedia.org/wiki/CVSup > references "csup" as "a rewrite of cvsup in C" > > http://www.mu.org/~mux/csup.html opencsw# more TODO ... MISSING FEATURES: ... - ... Solaris support would also be nice at some point. I'll give it a try anyway. Best regards -- Dago From bwalton at opencsw.org Mon Dec 15 02:44:26 2008 From: bwalton at opencsw.org (Ben Walton) Date: Sun, 14 Dec 2008 20:44:26 -0500 Subject: [csw-maintainers] New catalog "unstrict" In-Reply-To: References: <4F18B3FA-F0C3-41CA-A77E-9DD9E9BBF135@opencsw.org> <20081214.10003400.2052822375@gyor.oxdrove.co.uk> Message-ID: <1229305332-sup-6142@ntdws12.chass.utoronto.ca> Excerpts from Dagobert Michelsen's message of Sun Dec 14 16:23:47 -0500 2008: > We already have dtracetoolkit. How about the vendor does not make > a version (like Opera Solaris 8 x86, right?) or there is no > assembly backend (like for CVsup Solaris x86). Theoretically this > could be written, but is a much bigger work than tweaking flags > or writing a couple-of-lines patch. Does it have to be done centrally, or would extending the tools to handle multiple sources (ala apt/yum) be a better approach. That way, anyone that wanted to could publish a catalog and users/sites could pick and choose a superset of 'strict' CSW to meet their needs at their own discretion? This would take time, of course... Just thinking out loud. -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. From phil at bolthole.com Mon Dec 15 02:46:40 2008 From: phil at bolthole.com (Philip Brown) Date: Sun, 14 Dec 2008 17:46:40 -0800 Subject: [csw-maintainers] New catalog "unstrict" In-Reply-To: <1229305332-sup-6142@ntdws12.chass.utoronto.ca> References: <4F18B3FA-F0C3-41CA-A77E-9DD9E9BBF135@opencsw.org> <20081214.10003400.2052822375@gyor.oxdrove.co.uk> <1229305332-sup-6142@ntdws12.chass.utoronto.ca> Message-ID: <20081215014640.GB7986@bolthole.com> On Sun, Dec 14, 2008 at 08:44:26PM -0500, Ben Walton wrote: > > Does it have to be done centrally, or would extending the tools to > handle multiple sources (ala apt/yum) be a better approach. having multiple arbitrary source sites for packages is a support nightmare. That's why I explicitly chose to disallow that sort of thing in pkg-get. (besides from it being a programming nightmare :-) From bwalton at opencsw.org Mon Dec 15 02:53:05 2008 From: bwalton at opencsw.org (Ben Walton) Date: Sun, 14 Dec 2008 20:53:05 -0500 Subject: [csw-maintainers] New catalog "unstrict" In-Reply-To: <20081215014640.GB7986@bolthole.com> References: <4F18B3FA-F0C3-41CA-A77E-9DD9E9BBF135@opencsw.org> <20081214.10003400.2052822375@gyor.oxdrove.co.uk> <1229305332-sup-6142@ntdws12.chass.utoronto.ca> <20081215014640.GB7986@bolthole.com> Message-ID: <1229305724-sup-3665@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Sun Dec 14 20:46:40 -0500 2008: > having multiple arbitrary source sites for packages is a support > nightmare. That's why I explicitly chose to disallow that sort of > thing in pkg-get. Warranty void when using non-csw-blessed catalogs? > (besides from it being a programming nightmare :-) Certainly more difficult! I don't know if I like it either...just an idea. Ultimately, the more software we have packaged, the better off the project is as a whole. If some things are ridiculously difficult to package for all the standard targets, we should find a way to make them available so that they're still increasing the value of csw as a whole. -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. From phil at bolthole.com Mon Dec 15 03:01:24 2008 From: phil at bolthole.com (Philip Brown) Date: Sun, 14 Dec 2008 18:01:24 -0800 Subject: [csw-maintainers] New catalog "unstrict" In-Reply-To: <1229305724-sup-3665@ntdws12.chass.utoronto.ca> References: <4F18B3FA-F0C3-41CA-A77E-9DD9E9BBF135@opencsw.org> <20081214.10003400.2052822375@gyor.oxdrove.co.uk> <1229305332-sup-6142@ntdws12.chass.utoronto.ca> <20081215014640.GB7986@bolthole.com> <1229305724-sup-3665@ntdws12.chass.utoronto.ca> Message-ID: <20081215020124.GC7986@bolthole.com> On Sun, Dec 14, 2008 at 08:53:05PM -0500, Ben Walton wrote: > Ultimately, the more software we have packaged, the better off the > project is as a whole. not always universally true. We dont need the full scope of the 100+ free editors out there, for example ;-) From bwalton at opencsw.org Mon Dec 15 03:47:11 2008 From: bwalton at opencsw.org (Ben Walton) Date: Sun, 14 Dec 2008 21:47:11 -0500 Subject: [csw-maintainers] ruby help Message-ID: <1229309027-sup-6624@ntdws12.chass.utoronto.ca> Hi All, I set out to update Ruby to 1.8.7p72 shortly after the CERT advisories in the late summer. I have an updated GAR (not v2, yet) description that builds and packages the software, but I hit a speedbump with the documentation package. It seems that rdoc (as run by the install portion of the process*) is generating different results on sparc than it does on i386 (happens on both sol8 and sol10). I fired off a request for help to the ruby-core list, but got only a small request for more clarification. After providing this, I got no more info back... So, while the software is package-able, it currently requires either a) dropping a few files in the rubydoc package or b) architecture-specific rubydoc packages. Obviously both of these options stink! Is anyone out there able and willing to take a look at this and see if I'm doing something silly or whether there is indeed something wrong with the package under solaris? Incidentally, I did discover the following tidbit that, I suspect, puts solaris in the less than cared about realm as far as the ruby devs are typically concerned: http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/18257 Thanks -Ben * The GAR description builds this slightly differently than the ./configure; make; make install routine would, but doing it the 'stock' way sees the same results. -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. From phil at bolthole.com Mon Dec 15 03:53:57 2008 From: phil at bolthole.com (Philip Brown) Date: Sun, 14 Dec 2008 18:53:57 -0800 Subject: [csw-maintainers] ruby help In-Reply-To: <1229309027-sup-6624@ntdws12.chass.utoronto.ca> References: <1229309027-sup-6624@ntdws12.chass.utoronto.ca> Message-ID: <20081215025357.GG7986@bolthole.com> On Sun, Dec 14, 2008 at 09:47:11PM -0500, Ben Walton wrote: > > Hi All, > > I set out to update Ruby to 1.8.7p72 shortly after the CERT advisories > in the late summer. I have an updated GAR (not v2, yet) description > that builds and packages the software, but I hit a speedbump with the > documentation package. It seems that rdoc (as run by the install > portion of the process*) is generating different results on sparc than > it does on i386 (happens on both sol8 and sol10). Hey Ben, Did you ever confirm whether this was just a *DOCUMENTATION* difference, or whether the actual functionality was different, between sparc and x86? I dont remember you replying on that. From bwalton at opencsw.org Mon Dec 15 04:10:42 2008 From: bwalton at opencsw.org (Ben Walton) Date: Sun, 14 Dec 2008 22:10:42 -0500 Subject: [csw-maintainers] ruby help In-Reply-To: <20081215025357.GG7986@bolthole.com> References: <1229309027-sup-6624@ntdws12.chass.utoronto.ca> <20081215025357.GG7986@bolthole.com> Message-ID: <1229310317-sup-4789@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Sun Dec 14 21:53:57 -0500 2008: > Did you ever confirm whether this was just a *DOCUMENTATION* difference, or > whether the actual functionality was different, between sparc and x86? > I dont remember you replying on that. Well, as far as I've determined, the actual ruby package (and tcl/tk, but I don't play with that) is the same. The documentation differences are in extra files generated by rdoc from the source files (which would indicate extra/different info collected/collated). So supposedly, the input is identical, but the output differs. I've run a diff across the files generated on both architectures to verify that the files installed (where not binary) are identical. As best as I can tell, the _behaviour_ of rdoc differs on the two platforms, which to me indicates some odd little bug somewhere deep in the guts of it all (maybe in the rb_string or rb_hash somewhere?)... -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From phil at bolthole.com Mon Dec 15 04:17:25 2008 From: phil at bolthole.com (Philip Brown) Date: Sun, 14 Dec 2008 19:17:25 -0800 Subject: [csw-maintainers] ruby help In-Reply-To: <1229310317-sup-4789@ntdws12.chass.utoronto.ca> References: <1229309027-sup-6624@ntdws12.chass.utoronto.ca> <20081215025357.GG7986@bolthole.com> <1229310317-sup-4789@ntdws12.chass.utoronto.ca> Message-ID: <20081215031724.GA59357@bolthole.com> On Sun, Dec 14, 2008 at 10:10:42PM -0500, Ben Walton wrote: > Well, as far as I've determined, the actual ruby package (and tcl/tk, > but I don't play with that) is the same. The documentation > differences are in extra files generated by rdoc from the source files > (which would indicate extra/different info collected/collated). So > supposedly, the input is identical, but the output differs. > > I've run a diff across the files generated on both architectures to > verify that the files installed (where not binary) are identical. As > best as I can tell, the _behaviour_ of rdoc differs on the two > platforms, which to me indicates some odd little bug somewhere deep in > the guts of it all (maybe in the rb_string or rb_hash somewhere?)... oh. well, in that case, I'd say that it's fine to release, with a bug filed "oh by the way the documentation is a bit off, in these areas, we dont know why..." From phil at bolthole.com Mon Dec 15 04:26:06 2008 From: phil at bolthole.com (Philip Brown) Date: Sun, 14 Dec 2008 19:26:06 -0800 Subject: [csw-maintainers] ruby help In-Reply-To: <20081215031724.GA59357@bolthole.com> References: <1229309027-sup-6624@ntdws12.chass.utoronto.ca> <20081215025357.GG7986@bolthole.com> <1229310317-sup-4789@ntdws12.chass.utoronto.ca> <20081215031724.GA59357@bolthole.com> Message-ID: <20081215032606.GC59357@bolthole.com> On Sun, Dec 14, 2008 at 07:17:25PM -0800, Philip Brown wrote: > On Sun, Dec 14, 2008 at 10:10:42PM -0500, Ben Walton wrote: > > Well, as far as I've determined, the actual ruby package (and tcl/tk, > > but I don't play with that) is the same. The documentation > > differences are in extra files generated by rdoc from the source files > > (which would indicate extra/different info collected/collated). So > > supposedly, the input is identical, but the output differs. > > > > I've run a diff across the files generated on both architectures to > > verify that the files installed (where not binary) are identical. As > > best as I can tell, the _behaviour_ of rdoc differs on the two > > platforms, which to me indicates some odd little bug somewhere deep in > > the guts of it all (maybe in the rb_string or rb_hash somewhere?)... > > oh. > well, in that case, I'd say that it's fine to release, with a bug filed "oh > by the way the documentation is a bit off, in these areas, we dont > know why..." Hmm.. actually, the analysis above is a bit lacking. I think the more rigourous thing to do would be for you to explicitly mention some of the documentation differences/lackings, and then for someone who knows ruby, to explicitly run a test, "yes, these functions work ok on both platforms, even though they may not be documented on one of them". yes? From bwalton at opencsw.org Mon Dec 15 04:52:23 2008 From: bwalton at opencsw.org (Ben Walton) Date: Sun, 14 Dec 2008 22:52:23 -0500 Subject: [csw-maintainers] ruby help In-Reply-To: <20081215032606.GC59357@bolthole.com> References: <1229309027-sup-6624@ntdws12.chass.utoronto.ca> <20081215025357.GG7986@bolthole.com> <1229310317-sup-4789@ntdws12.chass.utoronto.ca> <20081215031724.GA59357@bolthole.com> <20081215032606.GC59357@bolthole.com> Message-ID: <1229312963-sup-1798@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Sun Dec 14 22:26:06 -0500 2008: > I think the more rigourous thing to do would be for you to explicitly > mention some of the documentation differences/lackings, and then for > someone who knows ruby, to explicitly run a test, "yes, these functions > work ok on both platforms, even though they may not be documented on one > of them". `make test` was identical on both platforms...not that it would test each and every possible function. This is the extra file generated when running rdoc almost identically to the way intended for a non-packaging run: $ diff i386.txt sparc.txt 1774d1773 < ./IRB/Context/_set_last_value-i.yaml [relative to share/doc/ruby...with a file list corrected for i386 vs sparc in the .so directory.] The results are similar when running it over the installed files, although with (if memory serves) about 4 files different. I'll dig through old mail to find that list (or regenerate the result). They're all in odd little corners though... -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From dam at opencsw.org Mon Dec 15 08:50:29 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 15 Dec 2008 08:50:29 +0100 Subject: [csw-maintainers] New catalog "unstrict" In-Reply-To: <20081215020124.GC7986@bolthole.com> References: <4F18B3FA-F0C3-41CA-A77E-9DD9E9BBF135@opencsw.org> <20081214.10003400.2052822375@gyor.oxdrove.co.uk> <1229305332-sup-6142@ntdws12.chass.utoronto.ca> <20081215014640.GB7986@bolthole.com> <1229305724-sup-3665@ntdws12.chass.utoronto.ca> <20081215020124.GC7986@bolthole.com> Message-ID: Hi, Am 15.12.2008 um 03:01 schrieb Philip Brown: > On Sun, Dec 14, 2008 at 08:53:05PM -0500, Ben Walton wrote: >> Ultimately, the more software we have packaged, the better off the >> project is as a whole. > > not always universally true. > We dont need the full scope of the 100+ free editors out there, for > example > ;-) So you would say having 10 editors is better than having 20? (All well maintained of course). But this is a theoretical example as we are not talking about hundred similar editors. We are talking about opera, maybe CVSup, maybe TME, maybe others. Best regards -- Dago From bonivart at opencsw.org Mon Dec 15 09:37:06 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Mon, 15 Dec 2008 09:37:06 +0100 Subject: [csw-maintainers] New catalog "unstrict" In-Reply-To: <1229305332-sup-6142@ntdws12.chass.utoronto.ca> References: <4F18B3FA-F0C3-41CA-A77E-9DD9E9BBF135@opencsw.org> <20081214.10003400.2052822375@gyor.oxdrove.co.uk> <1229305332-sup-6142@ntdws12.chass.utoronto.ca> Message-ID: <625385e30812150037l5a4b132ax32b03e90eb1ab552@mail.gmail.com> On Mon, Dec 15, 2008 at 2:44 AM, Ben Walton wrote: > Does it have to be done centrally, or would extending the tools to > handle multiple sources (ala apt/yum) be a better approach. That way, > anyone that wanted to could publish a catalog and users/sites could > pick and choose a superset of 'strict' CSW to meet their needs at > their own discretion? Pkgutil already contains all tools necessary to do that. You can create your own catalog for your own packages and use it in combination with an official mirror. http://pkgutil.wikidot.com/use-with-examples#toc6 -- /peter From phil at bolthole.com Mon Dec 15 15:17:16 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 15 Dec 2008 06:17:16 -0800 Subject: [csw-maintainers] New catalog "unstrict" In-Reply-To: References: <4F18B3FA-F0C3-41CA-A77E-9DD9E9BBF135@opencsw.org> <20081214.10003400.2052822375@gyor.oxdrove.co.uk> <1229305332-sup-6142@ntdws12.chass.utoronto.ca> <20081215014640.GB7986@bolthole.com> <1229305724-sup-3665@ntdws12.chass.utoronto.ca> <20081215020124.GC7986@bolthole.com> Message-ID: <20081215141716.GF37716@bolthole.com> On Mon, Dec 15, 2008 at 08:50:29AM +0100, Dagobert Michelsen wrote: > Hi, > > Am 15.12.2008 um 03:01 schrieb Philip Brown: > > not always universally true. > > We dont need the full scope of the 100+ free editors out there, for > > example > > ;-) > > So you would say having 10 editors is better than having 20? if it's "the best 10", then yes! > But this is a theoretical > example as we are not talking about hundred similar editors. > We are talking about opera, maybe CVSup, maybe TME, maybe others. opera, we might make an exception for. cvsup is a mess. no idea what tme is. From bonivart at opencsw.org Mon Dec 15 17:45:05 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Mon, 15 Dec 2008 17:45:05 +0100 Subject: [csw-maintainers] /testing pm_libwww, pm_modload and pm_modloadcond Message-ID: <625385e30812150845p3afd72aeoaebff322093e8fa7@mail.gmail.com> I have updated pm_libwww and pm_modloadcond because the upstream notification service told me to. :-) While updating pm_modloadcond it complained that pm_modload was only 0.10 while 0.11 was required so I updated it (one of Cory's packages) to the latest 0.12. Please test if you can. http://mirror.csw.baltic-online.de/testing/ -- /peter From phil at bolthole.com Mon Dec 15 18:05:29 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 15 Dec 2008 09:05:29 -0800 Subject: [csw-maintainers] /testing pm_libwww, pm_modload and pm_modloadcond In-Reply-To: <625385e30812150845p3afd72aeoaebff322093e8fa7@mail.gmail.com> References: <625385e30812150845p3afd72aeoaebff322093e8fa7@mail.gmail.com> Message-ID: <20081215170529.GE94217@bolthole.com> On Mon, Dec 15, 2008 at 05:45:05PM +0100, Peter Bonivart wrote: > I have updated pm_libwww and pm_modloadcond because the upstream > notification service told me to. :-) While updating pm_modloadcond it > complained that pm_modload was only 0.10 while 0.11 was required so I > updated it (one of Cory's packages) to the latest 0.12. > > Please test if you can. > > http://mirror.csw.baltic-online.de/testing/ http://mirror.opencsw.org/testing/ ? From william at wbonnet.net Mon Dec 15 20:51:01 2008 From: william at wbonnet.net (William Bonnet) Date: Mon, 15 Dec 2008 20:51:01 +0100 Subject: [csw-maintainers] /testing pm_libwww, pm_modload and pm_modloadcond In-Reply-To: <625385e30812150845p3afd72aeoaebff322093e8fa7@mail.gmail.com> References: <625385e30812150845p3afd72aeoaebff322093e8fa7@mail.gmail.com> Message-ID: <4946B525.9090407@wbonnet.net> Hi Peter > I have updated pm_libwww and pm_modloadcond because the upstream > notification service told me to. :-) Yeah ! it works :) Thanks Peter -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.blastwave.org An OpenSolaris Community Site http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From dam at opencsw.org Mon Dec 15 22:07:52 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 15 Dec 2008 22:07:52 +0100 Subject: [csw-maintainers] Invitation for OpenCSW membership References: <2AC8BBA4-1E45-440E-B064-E6C4929F8511@opencsw.org> Message-ID: Dear maintainer, on the 6th of December the Open Community Software (OpenCSW) Association was founded in Effretikon, Zurich to continue the packaging efforts already in progress. Unfortunately, it is legally not possible to automatically make all existing maintainers to members. We already know that you can maintain packages, and we wish you to continue doing so. At this time, it is neccessary to just have the formality of each person officially saying 'yes I wish to be a maintainer/member of the new OpenCSW association' The membership is not associated with any fees. You can read the bylaws at and An informal reply for application of membership is sufficient. Kind regards -- Dagobert Michelsen (secretary of the board) From wbonnet at opencsw.org Mon Dec 15 22:54:58 2008 From: wbonnet at opencsw.org (William Bonnet) Date: Mon, 15 Dec 2008 22:54:58 +0100 Subject: [csw-maintainers] Invitation for OpenCSW membership In-Reply-To: References: <2AC8BBA4-1E45-440E-B064-E6C4929F8511@opencsw.org> Message-ID: <4946D232.1000506@opencsw.org> Hi I do apply for membership cheers W. Dagobert Michelsen wrote: > Dear maintainer, > > on the 6th of December the Open Community Software (OpenCSW) > Association was founded in Effretikon, Zurich to continue the > packaging efforts already in progress. Unfortunately, it is > legally not possible to automatically make all existing > maintainers to members. > > We already know that you can maintain packages, and we wish > you to continue doing so. At this time, it is neccessary to > just have the formality of each person officially saying 'yes > I wish to be a maintainer/member of the new OpenCSW association' > The membership is not associated with any fees. You can read > the bylaws at > > and > > > > An informal reply for application of membership is sufficient. > > > Kind regards > > -- Dagobert Michelsen > (secretary of the board) > > > > _______________________________________________ > maintainers mailing list > maintainers at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/maintainers > > > -- William Bonnet http://www.wbonnet.net http://www.opencsw.org Community SoftWare for Solaris From ihsan at opencsw.org Mon Dec 15 22:57:30 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Mon, 15 Dec 2008 22:57:30 +0100 Subject: [csw-maintainers] Invitation for OpenCSW membership In-Reply-To: <4946D232.1000506@opencsw.org> References: <2AC8BBA4-1E45-440E-B064-E6C4929F8511@opencsw.org> <4946D232.1000506@opencsw.org> Message-ID: <4946D2CA.5030407@opencsw.org> Am 15.12.2008 22:54 Uhr, William Bonnet schrieb: > I do apply for membership You have been one of the founders, so you are already a member. :-) Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From william at wbonnet.net Mon Dec 15 23:07:29 2008 From: william at wbonnet.net (William Bonnet) Date: Mon, 15 Dec 2008 23:07:29 +0100 Subject: [csw-maintainers] Invitation for OpenCSW membership In-Reply-To: <4946D2CA.5030407@opencsw.org> References: <2AC8BBA4-1E45-440E-B064-E6C4929F8511@opencsw.org> <4946D232.1000506@opencsw.org> <4946D2CA.5030407@opencsw.org> Message-ID: <4946D521.5050104@wbonnet.net> Ihsan Dogan wrote: > Am 15.12.2008 22:54 Uhr, William Bonnet schrieb: > > >> I do apply for membership >> > > You have been one of the founders, so you are already a member. :-) > Yes but i was in the list of "named" people in the To field, not just included in the list. So i answered just in case ;) cheers -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.blastwave.org An OpenSolaris Community Site http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From trygvel at opencsw.org Tue Dec 16 16:05:06 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Tue, 16 Dec 2008 16:05:06 +0100 Subject: [csw-maintainers] IRC Message-ID: <4947C3A2.1030707@opencsw.org> Hello A few of us maintainers are regularly hanging out on IRC chatting on CSW, Solaris, life and everything else. Feel free to join us on freenode[1], the channel name is (drumroll...) #opencsw. OpenCSW has more than one useful IRC client: xchat [2] and irssi [3]. [1]: http://freenode.net/ [2]: http://opencsw.org/packages/xchat [3]: http://opencsw.org/packages/irssi -- Trygve From bwalton at opencsw.org Tue Dec 16 22:28:49 2008 From: bwalton at opencsw.org (Ben Walton) Date: Tue, 16 Dec 2008 16:28:49 -0500 Subject: [csw-maintainers] build requirements Message-ID: <1229462603-sup-6135@ntdws12.chass.utoronto.ca> Hi All, I now have a gar description for git that builds it but am seeing tests fail. So far, all failures are related to an implicit assumption that sed == gnu sed. Modifying the test files to call gsed seems to get things going. So, I have a few options: 1. Create a patch per 'bad' assumption (where bad == 'bad for me because it makes more work') 2. Add some autoconf magic, and alter the test harness to include the file generated by configure, thus allowing for a user specifiable $(sed) program. Submit this upstream. 3. Use PREREQUISITE_PKGS += CSWgnulinks and prepend /opt/csw/gnu to the GARPATH. I have my own opinion on which is the best going forward, but am curious as to what others think? Thoughts? Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From phil at bolthole.com Tue Dec 16 23:38:01 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 16 Dec 2008 14:38:01 -0800 Subject: [csw-maintainers] build requirements In-Reply-To: <1229462603-sup-6135@ntdws12.chass.utoronto.ca> References: <1229462603-sup-6135@ntdws12.chass.utoronto.ca> Message-ID: <20081216223801.GI5042@bolthole.com> On Tue, Dec 16, 2008 at 04:28:49PM -0500, Ben Walton wrote: > Hi All, > > I now have a gar description for git that builds it but am seeing > tests fail. So far, all failures are related to an implicit > assumption that sed == gnu sed. Modifying the test files to call gsed > seems to get things going. So, I have a few options: > > 1. Create a patch per 'bad' assumption (where bad == 'bad for me > because it makes more work') > 2. Add some autoconf magic, and alter the test harness to include the > file generated by configure, thus allowing for a user specifiable > $(sed) program. Submit this upstream. > 3. Use PREREQUISITE_PKGS += CSWgnulinks and prepend /opt/csw/gnu to > the GARPATH. > > I have my own opinion on which is the best going forward, but am > curious as to what others think? in this specific case... having looked at the configure file in question... i think it may be simplest and cleanest to go with option #3 for this. From bwalton at opencsw.org Wed Dec 17 01:37:24 2008 From: bwalton at opencsw.org (Ben Walton) Date: Tue, 16 Dec 2008 19:37:24 -0500 Subject: [csw-maintainers] build requirements In-Reply-To: <20081216223801.GI5042@bolthole.com> References: <1229462603-sup-6135@ntdws12.chass.utoronto.ca> <20081216223801.GI5042@bolthole.com> Message-ID: <1229474171-sup-6652@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Tue Dec 16 17:38:01 -0500 2008: > > 3. Use PREREQUISITE_PKGS += CSWgnulinks and prepend /opt/csw/gnu to > > the GARPATH. > > in this specific case... having looked at the configure file in question... > i think it may be simplest and cleanest to go with option #3 for this. This is my thinking also, as it is better insulation against future gnuisms, and with a package like this, they're bound to occur. Just wanted to spot check the logic. -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From trygvel at opencsw.org Wed Dec 17 01:51:58 2008 From: trygvel at opencsw.org (=?UTF-8?B?VHJ5Z3ZlIExhdWdzdMO4bA==?=) Date: Wed, 17 Dec 2008 01:51:58 +0100 Subject: [csw-maintainers] build requirements In-Reply-To: <1229462603-sup-6135@ntdws12.chass.utoronto.ca> References: <1229462603-sup-6135@ntdws12.chass.utoronto.ca> Message-ID: <49484D2E.2010908@opencsw.org> Ben Walton wrote: > Hi All, > > I now have a gar description for git that builds it but am seeing > tests fail. So far, all failures are related to an implicit > assumption that sed == gnu sed. Modifying the test files to call gsed > seems to get things going. So, I have a few options: > > 1. Create a patch per 'bad' assumption (where bad == 'bad for me > because it makes more work') > 2. Add some autoconf magic, and alter the test harness to include the > file generated by configure, thus allowing for a user specifiable > $(sed) program. Submit this upstream. > 3. Use PREREQUISITE_PKGS += CSWgnulinks and prepend /opt/csw/gnu to > the GARPATH. > > I have my own opinion on which is the best going forward, but am > curious as to what others think? Do me it sounds like do 1) first to get the package out and then work on 2) if git is a long-term useful package that we would like to release often to lower our maintenance cost. I assume that 3) would lead to requiring me having /opt/csw/gnu first in my path when using git and that is not going to happen. -- Trygve From bwalton at opencsw.org Wed Dec 17 01:57:29 2008 From: bwalton at opencsw.org (Ben Walton) Date: Tue, 16 Dec 2008 19:57:29 -0500 Subject: [csw-maintainers] build requirements In-Reply-To: <49484D2E.2010908@opencsw.org> References: <1229462603-sup-6135@ntdws12.chass.utoronto.ca> <49484D2E.2010908@opencsw.org> Message-ID: <1229475200-sup-6721@ntdws12.chass.utoronto.ca> Excerpts from Trygve Laugst?l's message of Tue Dec 16 19:51:58 -0500 2008: > I assume that 3) would lead to requiring me having /opt/csw/gnu first in > my path when using git and that is not going to happen. As far as I've seen at this point, it's simply the test scripts that are breaking without gnu sed. As this shouldn't impact the runtime requirements, I don't think there much worry of a permanent dependence on gnulinks. Option #2 seems like the more technically 'correct' thing to do until you consider that the primary development environment for git is a completely gnu userland. At some point, a gnu-ism would creep in again requiring more work on our part. Going with gnulinks seems like it's easier all around. If it ends up impacting dependencies, then I'll reconsider. I appreciate the feedback though! :) Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From trygvel at opencsw.org Wed Dec 17 02:13:54 2008 From: trygvel at opencsw.org (=?UTF-8?B?VHJ5Z3ZlIExhdWdzdMO4bA==?=) Date: Wed, 17 Dec 2008 02:13:54 +0100 Subject: [csw-maintainers] build requirements In-Reply-To: <1229475200-sup-6721@ntdws12.chass.utoronto.ca> References: <1229462603-sup-6135@ntdws12.chass.utoronto.ca> <49484D2E.2010908@opencsw.org> <1229475200-sup-6721@ntdws12.chass.utoronto.ca> Message-ID: <49485252.9010307@opencsw.org> Ben Walton wrote: > Excerpts from Trygve Laugst?l's message of Tue Dec 16 19:51:58 -0500 2008: >> I assume that 3) would lead to requiring me having /opt/csw/gnu first in >> my path when using git and that is not going to happen. > > As far as I've seen at this point, it's simply the test scripts that > are breaking without gnu sed. As this shouldn't impact the runtime > requirements, I don't think there much worry of a permanent dependence > on gnulinks. Then both 1) and 3) would be acceptable to me as they would both work for anyone trying to pick up the package at a later point. > Option #2 seems like the more technically 'correct' thing to do until > you consider that the primary development environment for git is a > completely gnu userland. At some point, a gnu-ism would creep in > again requiring more work on our part. Going with gnulinks seems like > it's easier all around. If it ends up impacting dependencies, then > I'll reconsider. That is a fair point and and I would say that it is up to you try to minimize the pain of maintaining a downstream build vs the paint of getting git work in a non-gnu environment. > I appreciate the feedback though! :) -- Trygve From bonivart at opencsw.org Wed Dec 17 18:15:18 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Wed, 17 Dec 2008 18:15:18 +0100 Subject: [csw-maintainers] /testing clamav 0.94.2 In-Reply-To: <625385e30812110758x668c1fa7v78b44530f9a628b5@mail.gmail.com> References: <625385e30812110758x668c1fa7v78b44530f9a628b5@mail.gmail.com> Message-ID: <625385e30812170915v413a634j8704d00d158a101a@mail.gmail.com> Sorry for top-posting. I have now tested the i386 packages also through VirtualBox (love it!) and it installs properly, can be managed via SMF and I can update the signatures and scan files. Everything I tested on sparc I can do on i386. I'm happy with it, if someone has any problems with it, please inform me quickly because I will drop it off for release tomorrow. /peter On Thu, Dec 11, 2008 at 4:58 PM, Peter Bonivart wrote: > This package by Alex Moore was getting quite old > (0.92.1,REV=2008.02.11), especially since it's security related. I use > it myself for MailScanner so I tried to build it. No package has yet > challenged me like this one and poor Dagobert had to suffer from > constant calls for help. :-) > > I wanted to do it in GAR which is being upgraded to v2 and I was very > keen on using several of the new features like the easy splitting of > packages. I also wanted it to use CSWcswclassutils for SMF support and > configuration file handling. I could simplify the old preinstall a lot > and completely remove the postinstall thanks to the use of > CSWcswclassutils. The init script for clamd is also redone quite a > lot. > > I would like help to test this one since I assume it's relatively > widely used and important to a user. I have done some tests on > sparc/5.9 like running clamscan, starting clamd and running clamdscan, > updating virus signatures with freshclam and so on. What I haven't > tested at all (except for checking with ldd) is the clamav-milter so > if someone can set that up a report would be great. Also test from > i386 and 5.10 (use SMF) if you can. Just install, test what you can, > remove and report back to me even if everything was successful, I need > to hear that too. :-) > > Look for clamav and libclamav here: http://buildfarm.opencsw.org/testing.html > > By the way, I have updated the wiki page about CSWcswclassutils to > include instructions on how to use it in GAR. Take a look. > > -- > /peter > -- /peter From bonivart at opencsw.org Wed Dec 17 18:41:49 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Wed, 17 Dec 2008 18:41:49 +0100 Subject: [csw-maintainers] /testing BIND 9.5.0-P2 Message-ID: <625385e30812170941l5c391483y3a98981cc160a73c@mail.gmail.com> I have built the latest BIND complete with SMF support via cswclassutils. I have also used GAR v2 to easily split the package into smaller parts. All this was requested by users but it was hard work before tools like cswclassutils and GAR v2 made it easy. BIND is now split like this: * bind - top level package containing server bits and docs * libbind - shared libs that all other bind packages need * bind_utils - the user binaries (dig, host, ?) * bind_devel - the stuff most people don't use :-) If you install bind you will get bind, libbind and bind_utils. If you install libbind you will just get libbind (and it's other deps of course). If you install bind_utils you will get bind_utils and libbind. Bind_devel will pull in all other bind packages. I have done some tests on i386/5.10 with SMF and it works as expected. Would be very bad if it was broken in any way though so please help test it and report back whether it works or not. -- /peter From dam at opencsw.org Wed Dec 17 20:06:52 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 17 Dec 2008 20:06:52 +0100 Subject: [csw-maintainers] build requirements In-Reply-To: <1229462603-sup-6135@ntdws12.chass.utoronto.ca> References: <1229462603-sup-6135@ntdws12.chass.utoronto.ca> Message-ID: <32FB4143-8534-4B1A-A071-30386F936947@opencsw.org> Hi Ben, Am 16.12.2008 um 22:28 schrieb Ben Walton: > I now have a gar description for git that builds it but am seeing > tests fail. So far, all failures are related to an implicit > assumption that sed == gnu sed. Modifying the test files to call gsed > seems to get things going. So, I have a few options: > > 1. Create a patch per 'bad' assumption (where bad == 'bad for me > because it makes more work') > 2. Add some autoconf magic, and alter the test harness to include the > file generated by configure, thus allowing for a user specifiable > $(sed) program. Submit this upstream. > 3. Use PREREQUISITE_PKGS += CSWgnulinks and prepend /opt/csw/gnu to > the GARPATH. The absolute best thing would be to check in configure if sed has the appropriate features and search through path for all sed or gsed. If it is only for tests I'd go with 3. Best regards -- Dago From dam at opencsw.org Wed Dec 17 20:35:10 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 17 Dec 2008 20:35:10 +0100 Subject: [csw-maintainers] Vacation from 20.12. to 27.12. Message-ID: <7D9305DF-8BF3-41C0-95B3-E99C9CE9D0CF@opencsw.org> Fellow maintainers, I will be away for some quality time with the family from 20. December to 27. December and there will only be a very limited internet connectivity available (if at all...). The bo- and go-buildfarms are co- administered by Ben Walton, so there is still someone available if anyone needs to install a package. Just make sure to mail to buildfarm at lists.opencsw.org instead of me ;-) Best regards and a merry christmas -- Dago From ihsan at opencsw.org Wed Dec 17 21:02:28 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Wed, 17 Dec 2008 21:02:28 +0100 Subject: [csw-maintainers] new PHP maintainer needed Message-ID: <49495AD4.8000806@opencsw.org> Hello, Cory left about a year ago. Because he had all his packages in Gar, I was able to build a new PHP package. Unfortunately I'm not the right person for this package and besides that, I don't have enough resources to maintain the PHP package. Therefore I would like to ask, if someone can take over this important package. Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From dam at opencsw.org Thu Dec 18 11:42:48 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 18 Dec 2008 11:42:48 +0100 Subject: [csw-maintainers] New members Message-ID: <06285DD2-98C4-4403-A104-495AE81F39AE@opencsw.org> Hi, the association welcomes the newly accepted members - Ben Walton - Chris Reece - Michael Gernoth - Murray Jensen - Peter Bonivart All of you have already contributed to the project in the past. Ben, Murray and Peter are already very active on the new OpenCSW to update their packages. Michael operates the master mirror and has still sabbatical on his maintained packages. Chris contributed with a non-trivial patch to pca as latest effort. Please keep in mind that being a maintainer is not only about fame and glory, but also about tedious work to make the packages as good as possible and remove bugs timely when discovered. Please check regularly at the bottom of your maintainer page if there are any open issues. If you have spare cycles please adopt an orphaned package and help bring the complete software stack to a 100% current state. But enough of morality: A very warm welcome! Your membership is tracked at There is now a new column with your dedication in the project. Please let me know on what are you working or are planning to work like "webpage", "maintainer", etc. Best regards -- Dago From phil at bolthole.com Thu Dec 18 18:32:46 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 18 Dec 2008 09:32:46 -0800 Subject: [csw-maintainers] build requirements In-Reply-To: <49484D2E.2010908@opencsw.org> References: <1229462603-sup-6135@ntdws12.chass.utoronto.ca> <49484D2E.2010908@opencsw.org> Message-ID: <20081218173245.GE54484@bolthole.com> On Wed, Dec 17, 2008 at 01:51:58AM +0100, Trygve Laugst??l wrote: > I assume that 3) would lead to requiring me having /opt/csw/gnu first in > my path when using git and that is not going to happen. I'll point out that, even though that is not the case for this PARTICULAR program... a potential way of solving this sort of thing, is to make the top-level binary be a wrapper script, that does something along the lines of export PATH=/opt/csw/gnu:$PATH exec $0 $* thus it would only affect the prorgram and its children, rather than the user's environment at large. From bwalton at opencsw.org Thu Dec 18 20:49:22 2008 From: bwalton at opencsw.org (Ben Walton) Date: Thu, 18 Dec 2008 14:49:22 -0500 Subject: [csw-maintainers] new PHP maintainer needed In-Reply-To: <49495AD4.8000806@opencsw.org> References: <49495AD4.8000806@opencsw.org> Message-ID: <1229629675-sup-9039@ntdws12.chass.utoronto.ca> Excerpts from Ihsan Dogan's message of Wed Dec 17 15:02:28 -0500 2008: > > Therefore I would like to ask, if someone can take over this important > package. Also, what is the plan for php4. As it's no longer supported upstream (even for security patches, I understand), what are we to do with it? http://www.php.net/downloads.php#v4 My feeling is that it should be dropped...php5 has been out long enough, apps have had time to get ported (where necessary), etc. What do others think? -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From phil at bolthole.com Thu Dec 18 21:09:50 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 18 Dec 2008 12:09:50 -0800 Subject: [csw-maintainers] new PHP maintainer needed In-Reply-To: <1229629675-sup-9039@ntdws12.chass.utoronto.ca> References: <49495AD4.8000806@opencsw.org> <1229629675-sup-9039@ntdws12.chass.utoronto.ca> Message-ID: <20081218200950.GH54484@bolthole.com> On Thu, Dec 18, 2008 at 02:49:22PM -0500, Ben Walton wrote: > Excerpts from Ihsan Dogan's message of Wed Dec 17 15:02:28 -0500 2008: > > > > > Therefore I would like to ask, if someone can take over this important > > package. > > Also, what is the plan for php4. As it's no longer supported upstream > (even for security patches, I understand), what are we to do with it? > > http://www.php.net/downloads.php#v4 Just leave it alone. it doesnt conflict with anything. if we had a generic "php" package, it should certainly be pointed to use php5 now. but we dont. so it's a moot point, in my opinion. I guess it might be nice if the two things that depend on it, dotproject and drupal, were updated to use php5 though. Now, back to the more important issue... Who would like to maintain php5? :-) From phil at bolthole.com Thu Dec 18 21:14:10 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 18 Dec 2008 12:14:10 -0800 Subject: [csw-maintainers] large project: pkagdd/pkgrm open source package? Message-ID: <20081218201410.GI54484@bolthole.com> So.... Sun has some "issues" with pkgadd and pkgrm... such as not fixing glaring bugs, like having a "pkgadd -G" flag, but no "pkgrm -G" flag. it would seem they have frozen out any changes; that is to say, not putting any further resources into it. but meanwhile, us folks out here still need to use it. Is there any brave soul out there, with a LOT of time on their hands, who might consider packaging up our own open-source versions of them, and potentially fixing missing features, such as the -G flag? While you were in the vicinity, you might also wish to fix things like the stupid "if not root, then bail out" limit, so that we can safely use pkgadd on a per-user area basis. Supposedly, most if not all of it has finally been opened now. From bwalton at opencsw.org Thu Dec 18 22:18:59 2008 From: bwalton at opencsw.org (Ben Walton) Date: Thu, 18 Dec 2008 16:18:59 -0500 Subject: [csw-maintainers] git in testing Message-ID: <1229634705-sup-2537@ntdws12.chass.utoronto.ca> Hi All, I've dropped the current build of the git* packages in /home/testing. Currently, these are built for solaris 10 on x86 (I don't have a good solaris 8 build environment yet and am waiting for the prequisite packages to be relased so I can do it on the buildfarm). As yet, I don't know if there are issues building on solaris 8 at all...time will tell. I've done successful clones of some repos (using the ssh transport) and both gitk and `git gui` fire up their respective tk windows and seem functional. I'm sure there are still some rough edges and there are some other little things that I'll clean up for my own tastes, but the basics should be in place. I'd appreciate feedback (positive or negative) on this if you're willing to take a poke at it. Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From trygvel at opencsw.org Thu Dec 18 23:11:23 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Thu, 18 Dec 2008 23:11:23 +0100 Subject: [csw-maintainers] build requirements In-Reply-To: <20081218173245.GE54484@bolthole.com> References: <1229462603-sup-6135@ntdws12.chass.utoronto.ca> <49484D2E.2010908@opencsw.org> <20081218173245.GE54484@bolthole.com> Message-ID: <494ACA8B.2040809@opencsw.org> Philip Brown wrote: > On Wed, Dec 17, 2008 at 01:51:58AM +0100, Trygve Laugst?l wrote: >> I assume that 3) would lead to requiring me having /opt/csw/gnu first in >> my path when using git and that is not going to happen. > > I'll point out that, even though that is not the case for this PARTICULAR > program... a potential way of solving this sort of thing, is to make the > top-level binary be a wrapper script, that does something along the > lines of > > export PATH=/opt/csw/gnu:$PATH > exec $0 $* > > thus it would only affect the prorgram and its children, rather than the > user's environment at large. That is indeed true, I've even done similar tricks myself before :) -- Trygve From trygvel at opencsw.org Thu Dec 18 23:13:41 2008 From: trygvel at opencsw.org (=?UTF-8?B?VHJ5Z3ZlIExhdWdzdMO4bA==?=) Date: Thu, 18 Dec 2008 23:13:41 +0100 Subject: [csw-maintainers] git in testing In-Reply-To: <1229634705-sup-2537@ntdws12.chass.utoronto.ca> References: <1229634705-sup-2537@ntdws12.chass.utoronto.ca> Message-ID: <494ACB15.4090107@opencsw.org> Ben Walton wrote: > Hi All, > > I've dropped the current build of the git* packages in /home/testing. > Currently, these are built for solaris 10 on x86 (I don't have a good > solaris 8 build environment yet and am waiting for the prequisite > packages to be relased so I can do it on the buildfarm). As yet, I > don't know if there are issues building on solaris 8 at all...time > will tell. I think you should add them to Hudson even if they're not accepted yet. If you want to I can add solaris10{x,s} builders so you (and the testers) can keep updated. > I've done successful clones of some repos (using the ssh transport) > and both gitk and `git gui` fire up their respective tk windows and > seem functional. > > I'm sure there are still some rough edges and there are some other > little things that I'll clean up for my own tastes, but the basics > should be in place. > > I'd appreciate feedback (positive or negative) on this if you're > willing to take a poke at it. -- Trygve From phil at bolthole.com Thu Dec 18 23:22:47 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 18 Dec 2008 14:22:47 -0800 Subject: [csw-maintainers] git in testing In-Reply-To: <494ACB15.4090107@opencsw.org> References: <1229634705-sup-2537@ntdws12.chass.utoronto.ca> <494ACB15.4090107@opencsw.org> Message-ID: <20081218222247.GJ54484@bolthole.com> On Thu, Dec 18, 2008 at 11:13:41PM +0100, Trygve Laugst??l wrote: > Ben Walton wrote: > > Hi All, > > > > I've dropped the current build of the git* packages in /home/testing. > > Currently, these are built for solaris 10 on x86 (I don't have a good > > solaris 8 build environment yet and am waiting for the prequisite > > packages to be relased so I can do it on the buildfarm). As yet, I > > don't know if there are issues building on solaris 8 at all...time > > will tell. > > I think you should add them to Hudson even if they're not accepted yet. This would be a very bad precedent. Conceptually, I would think it would be as bad as installing packages on the build machines that have not been accepted for release. Packages sometimes do not get accepted for release, because they SHOULD NOT BE released. This created a large amount of problems with certain packages last month. From dam at opencsw.org Fri Dec 19 00:17:24 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 19 Dec 2008 00:17:24 +0100 Subject: [csw-maintainers] git in testing In-Reply-To: <20081218222247.GJ54484@bolthole.com> References: <1229634705-sup-2537@ntdws12.chass.utoronto.ca> <494ACB15.4090107@opencsw.org> <20081218222247.GJ54484@bolthole.com> Message-ID: <3B2C76BD-C314-4C6E-9FD3-4EC5A45453B8@opencsw.org> Hi Phil, Am 18.12.2008 um 23:22 schrieb Philip Brown: > On Thu, Dec 18, 2008 at 11:13:41PM +0100, Trygve Laugst??l wrote: >> I think you should add them to Hudson even if they're not accepted >> yet. > > This would be a very bad precedent. Conceptually, I would think it > would be > as bad as installing packages on the build machines that have not been > accepted for release. Definitely not. It should be in Hudson when the directory is created. Having Hudson run jobs makes it easier to concentrate e. g. on sparc and let Hudson do x86. > Packages sometimes do not get accepted for release, because they > SHOULD NOT BE released. This created a large amount of problems > with certain packages last month. The output of Hudson is one step before testing. There is no damage using Hudson. Best regards -- Dago From phil at bolthole.com Fri Dec 19 00:26:39 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 18 Dec 2008 15:26:39 -0800 Subject: [csw-maintainers] git in testing In-Reply-To: <3B2C76BD-C314-4C6E-9FD3-4EC5A45453B8@opencsw.org> References: <1229634705-sup-2537@ntdws12.chass.utoronto.ca> <494ACB15.4090107@opencsw.org> <20081218222247.GJ54484@bolthole.com> <3B2C76BD-C314-4C6E-9FD3-4EC5A45453B8@opencsw.org> Message-ID: <20081218232639.GL54484@bolthole.com> On Fri, Dec 19, 2008 at 12:17:24AM +0100, Dagobert Michelsen wrote: > > Packages sometimes do not get accepted for release, because they > > SHOULD NOT BE released. This created a large amount of problems > > with certain packages last month. > > The output of Hudson is one step before testing. There is no > damage using Hudson. So, you are sayin that adding broken packages "in hudson", has zero possiblility to corrupt other packages "in hudson" then? BTW: It might be nice to have a beginner-level description of "this is hudson, what it does, and roughly how it works" page in the wiki or something, to help explain this stuff...? From dam at opencsw.org Fri Dec 19 00:30:39 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 19 Dec 2008 00:30:39 +0100 Subject: [csw-maintainers] git in testing In-Reply-To: <20081218232639.GL54484@bolthole.com> References: <1229634705-sup-2537@ntdws12.chass.utoronto.ca> <494ACB15.4090107@opencsw.org> <20081218222247.GJ54484@bolthole.com> <3B2C76BD-C314-4C6E-9FD3-4EC5A45453B8@opencsw.org> <20081218232639.GL54484@bolthole.com> Message-ID: Hi Phil, Am 19.12.2008 um 00:26 schrieb Philip Brown: > On Fri, Dec 19, 2008 at 12:17:24AM +0100, Dagobert Michelsen wrote: >>> Packages sometimes do not get accepted for release, because they >>> SHOULD NOT BE released. This created a large amount of problems >>> with certain packages last month. >> >> The output of Hudson is one step before testing. There is no >> damage using Hudson. > > So, you are sayin that adding broken packages "in hudson", has zero > possiblility to corrupt other packages "in hudson" then? Yes. There is no package installed. It is just "gmake package" on every commit and that's it. > BTW: It might be nice to have a beginner-level description of > "this is hudson, what it does, and roughly how it works" page in the > wiki > or something, to help explain this stuff...? That would help, yes. Maybe Trygve prepares something when we ask him extra nice? ;-) Best regards -- Dago From phil at bolthole.com Fri Dec 19 00:42:30 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 18 Dec 2008 15:42:30 -0800 Subject: [csw-maintainers] git in testing In-Reply-To: References: <1229634705-sup-2537@ntdws12.chass.utoronto.ca> <494ACB15.4090107@opencsw.org> <20081218222247.GJ54484@bolthole.com> <3B2C76BD-C314-4C6E-9FD3-4EC5A45453B8@opencsw.org> <20081218232639.GL54484@bolthole.com> Message-ID: <20081218234230.GO54484@bolthole.com> On Fri, Dec 19, 2008 at 12:30:39AM +0100, Dagobert Michelsen wrote: > >> The output of Hudson is one step before testing. There is no > >> damage using Hudson. > > > > So, you are sayin that adding broken packages "in hudson", has zero > > possiblility to corrupt other packages "in hudson" then? > > Yes. There is no package installed. It is just "gmake package" > on every commit and that's it. ?? but in what environment? unless it's a bottom-level library, it has to get what it "makes" against, from SOMEWHERE. does hudson, not get that stuff from other things "in hudson" ?? From bwalton at opencsw.org Fri Dec 19 01:54:02 2008 From: bwalton at opencsw.org (Ben Walton) Date: Thu, 18 Dec 2008 19:54:02 -0500 Subject: [csw-maintainers] git in testing In-Reply-To: <20081218234230.GO54484@bolthole.com> References: <1229634705-sup-2537@ntdws12.chass.utoronto.ca> <494ACB15.4090107@opencsw.org> <20081218222247.GJ54484@bolthole.com> <3B2C76BD-C314-4C6E-9FD3-4EC5A45453B8@opencsw.org> <20081218232639.GL54484@bolthole.com> <20081218234230.GO54484@bolthole.com> Message-ID: <1229647909-sup-9888@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Thu Dec 18 18:42:30 -0500 2008: > but in what environment? unless it's a bottom-level library, it has to get > what it "makes" against, from SOMEWHERE. does hudson, not get that stuff > from other things "in hudson" ?? You're right Phil, in that adding git to hudson would currently be useless since it can't use the dependencies that don't exist yet. For packages that do have all dependencies published, I don't see any harm in having hudson ensure they're continuing to build (think gar changes, etc)...Even if the package doesn't get better (more platforms, for example), hudson can make sure it doesn't get worse. -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From phil at bolthole.com Fri Dec 19 02:08:05 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 18 Dec 2008 17:08:05 -0800 Subject: [csw-maintainers] hudson (previously, git in testing) In-Reply-To: <1229647909-sup-9888@ntdws12.chass.utoronto.ca> References: <1229634705-sup-2537@ntdws12.chass.utoronto.ca> <494ACB15.4090107@opencsw.org> <20081218222247.GJ54484@bolthole.com> <3B2C76BD-C314-4C6E-9FD3-4EC5A45453B8@opencsw.org> <20081218232639.GL54484@bolthole.com> <20081218234230.GO54484@bolthole.com> <1229647909-sup-9888@ntdws12.chass.utoronto.ca> Message-ID: <20081219010805.GP54484@bolthole.com> On Thu, Dec 18, 2008 at 07:54:02PM -0500, Ben Walton wrote: > Excerpts from Philip Brown's message of Thu Dec 18 18:42:30 -0500 2008: > > but in what environment? unless it's a bottom-level library, it has to get > > what it "makes" against, from SOMEWHERE. does hudson, not get that stuff > > from other things "in hudson" ?? > > You're right Phil, in that adding git to hudson would currently be > useless since it can't use the dependencies that don't exist yet. For > packages that do have all dependencies published, I don't see any harm > in having hudson ensure they're continuing to build (think gar > changes, etc)...Even if the package doesn't get better (more > platforms, for example), hudson can make sure it doesn't get worse. > dependson what the purpose of hudson is. If it's just "play around and see if things build nicely", then great. If on the other hand, it is on the road to becoming "the official way to build packages before publication", as some people seem to wish, then there needs to be stricter rules about putting things into hudson, otherwise we risk massive corruption. From trygvel at opencsw.org Fri Dec 19 07:56:25 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Fri, 19 Dec 2008 07:56:25 +0100 Subject: [csw-maintainers] hudson (previously, git in testing) In-Reply-To: <20081219010805.GP54484@bolthole.com> References: <1229634705-sup-2537@ntdws12.chass.utoronto.ca> <494ACB15.4090107@opencsw.org> <20081218222247.GJ54484@bolthole.com> <3B2C76BD-C314-4C6E-9FD3-4EC5A45453B8@opencsw.org> <20081218232639.GL54484@bolthole.com> <20081218234230.GO54484@bolthole.com> <1229647909-sup-9888@ntdws12.chass.utoronto.ca> <20081219010805.GP54484@bolthole.com> Message-ID: <494B4599.3020008@opencsw.org> Philip Brown wrote: > On Thu, Dec 18, 2008 at 07:54:02PM -0500, Ben Walton wrote: >> Excerpts from Philip Brown's message of Thu Dec 18 18:42:30 -0500 2008: >>> but in what environment? unless it's a bottom-level library, it has to get >>> what it "makes" against, from SOMEWHERE. does hudson, not get that stuff >>> from other things "in hudson" ?? >> You're right Phil, in that adding git to hudson would currently be >> useless since it can't use the dependencies that don't exist yet. For >> packages that do have all dependencies published, I don't see any harm >> in having hudson ensure they're continuing to build (think gar >> changes, etc)...Even if the package doesn't get better (more >> platforms, for example), hudson can make sure it doesn't get worse. >> > > dependson what the purpose of hudson is. > If it's just "play around and see if things build nicely", then great. > > > If on the other hand, it is on the road to becoming > "the official way to build packages before publication", > as some people seem to wish, then there needs to be stricter rules about > putting things into hudson, otherwise we risk massive corruption. That is right, but right it is working in the first way. I would like to extend that way to automatically pkgrm/pkgadd the packages once they're done. I'd like to start the second way once we have some more experience with Hudson and GAR has the few glitches ironed out (and we have a lot of time to actually get the process going). -- Trygve From dam at opencsw.org Fri Dec 19 11:49:44 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 19 Dec 2008 11:49:44 +0100 Subject: [csw-maintainers] Batch takeover of orphaned Perl modules possible? Message-ID: <090B00FA-E4AF-4907-9A6B-9A0C70850CBF@opencsw.org> Hi, William, you could prepare a batch update of the version for all Perl modules for Alex Moore? He has quite some: Maybe Peter as Perl maintainer wants to take a look at them? ;-) Trygve, can we do this as first production test for Hudson? I am eager to automate the tedious Perl module packaging. I vaguely remember some guy posting a script to automate the Perl module packaging without GAR. Does anyone remember? Maybe we can integrate the dependency-extraction from Makefile.PL from it. Best regards and Merry Christmas -- Dago From Darin.Perusich at cognigencorp.com Fri Dec 19 14:37:05 2008 From: Darin.Perusich at cognigencorp.com (Darin Perusich) Date: Fri, 19 Dec 2008 08:37:05 -0500 Subject: [csw-maintainers] new PHP maintainer needed In-Reply-To: <20081218200950.GH54484@bolthole.com> References: <49495AD4.8000806@opencsw.org> <1229629675-sup-9039@ntdws12.chass.utoronto.ca> <20081218200950.GH54484@bolthole.com> Message-ID: <494BA381.4060207@cognigencorp.com> Philip Brown wrote: > On Thu, Dec 18, 2008 at 02:49:22PM -0500, Ben Walton wrote: >> Excerpts from Ihsan Dogan's message of Wed Dec 17 15:02:28 -0500 2008: >> >>> Therefore I would like to ask, if someone can take over this important >>> package. >> Also, what is the plan for php4. As it's no longer supported upstream >> (even for security patches, I understand), what are we to do with it? >> >> http://www.php.net/downloads.php#v4 > > Just leave it alone. it doesnt conflict with anything. > if we had a generic "php" package, it should certainly be pointed to use > php5 now. > but we dont. so it's a moot point, in my opinion. Why just leave it alone? While I don't believe I'm the right person to bring this up, given I'm not a very active maintain, this not abandoning old software is one of the short comings of how we release packages. There is no way to gracefully remove old packages from the release cycle. This could be easily accomplished if when we have a stable release it was moved out of the stable/unstable directory structure and into it's own little world of YYYY-MM/{i386/sparc}. If this was how we did the releases it was be trivial to say, As of stable release 2008-12 support for the php4, mysql4, etc. package is being dropped. Then is someone wanted to use those version they could point pkg-get at that repository. Given the current paradigm we can't really remove old stuff from the software tree because someone MIGHT be using it. > I guess it might be nice if the two things that depend on it, > dotproject and drupal, were updated to use php5 though. I believe that version of drupal doesn't support php5, or it supports only an early release. Another one of those instances where we're the dependency of an OLD package is forcing us to keep other old clutter within the software stack. > Now, back to the more important issue... > Who would like to maintain php5? :-) > -- Darin Perusich Unix Systems Administrator Cognigen Corporation 395 Youngs Rd. Williamsville, NY 14221 Phone: 716-633-3463 Email: darinper at cognigencorp.com From bonivart at opencsw.org Fri Dec 19 15:39:02 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Fri, 19 Dec 2008 15:39:02 +0100 Subject: [csw-maintainers] Batch takeover of orphaned Perl modules possible? In-Reply-To: <090B00FA-E4AF-4907-9A6B-9A0C70850CBF@opencsw.org> References: <090B00FA-E4AF-4907-9A6B-9A0C70850CBF@opencsw.org> Message-ID: <625385e30812190639l6b152d61r81fc45faaab88136@mail.gmail.com> On Fri, Dec 19, 2008 at 11:49 AM, Dagobert Michelsen wrote: > Hi, > > William, you could prepare a batch update of the version for > all Perl modules for Alex Moore? He has quite some: > > Maybe Peter as Perl maintainer wants to take a look at them? ;-) I have taken everything from Alex that I have an interest in. :-) If there's a few (<10) perl modules that are out of date I can take them, they are real easy to build. Maybe the update notification could e-mail the maintainer list when the maintainer is listed as retired? By the way, Sendmail is another package from Alex that is important. Luckily it's pretty current still. -- /peter From phil at bolthole.com Fri Dec 19 16:25:51 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 19 Dec 2008 07:25:51 -0800 Subject: [csw-maintainers] new PHP maintainer needed In-Reply-To: <494BA381.4060207@cognigencorp.com> References: <49495AD4.8000806@opencsw.org> <1229629675-sup-9039@ntdws12.chass.utoronto.ca> <20081218200950.GH54484@bolthole.com> <494BA381.4060207@cognigencorp.com> Message-ID: <20081219152551.GC46050@bolthole.com> On Fri, Dec 19, 2008 at 08:37:05AM -0500, Darin Perusich wrote: > >[Philip Brown wrote] > > I guess it might be nice if the two things that depend on [php4], > > dotproject and drupal, were updated to use php5 though. > > I believe that version of drupal doesn't support php5, or it supports > only an early release. Another one of those instances where we're the > dependency of an OLD package is forcing us to keep other old clutter > within the software stack. So, we cant even consider dropping php4, until drupal is updated. Ummm.... and who is the maintainer of our drupal package... "Darin Perusich". I find it ironic, that you are complaining about something, that you are the primary path to resolution for? :-} A side note: a quick trip to the drupal website, says that "Drupal works with PHP 4 & 5" From Darin.Perusich at cognigencorp.com Fri Dec 19 16:45:57 2008 From: Darin.Perusich at cognigencorp.com (Darin Perusich) Date: Fri, 19 Dec 2008 10:45:57 -0500 Subject: [csw-maintainers] new PHP maintainer needed In-Reply-To: <20081219152551.GC46050@bolthole.com> References: <49495AD4.8000806@opencsw.org> <1229629675-sup-9039@ntdws12.chass.utoronto.ca> <20081218200950.GH54484@bolthole.com> <494BA381.4060207@cognigencorp.com> <20081219152551.GC46050@bolthole.com> Message-ID: <494BC1B5.4070707@cognigencorp.com> Philip Brown wrote: > On Fri, Dec 19, 2008 at 08:37:05AM -0500, Darin Perusich wrote: >>> [Philip Brown wrote] >>> I guess it might be nice if the two things that depend on [php4], >>> dotproject and drupal, were updated to use php5 though. >> I believe that version of drupal doesn't support php5, or it supports >> only an early release. Another one of those instances where we're the >> dependency of an OLD package is forcing us to keep other old clutter >> within the software stack. > > So, we cant even consider dropping php4, until drupal is updated. > Don't forget Dotproject. > Ummm.... and who is the maintainer of our drupal package... > "Darin Perusich". > I wasn't aware it was my package, thanks for pointing that out. > I find it ironic, that you are complaining about something, that you are > the primary path to resolution for? :-} I wouldn't call it complaining, I'm merely pointing out something, again, that I feel is a deficiency. As the "primary path to resolution", I propose removing drupal from the repository. -- Darin Perusich Unix Systems Administrator Cognigen Corporation 395 Youngs Rd. Williamsville, NY 14221 Phone: 716-633-3463 Email: darinper at cognigencorp.com From phil at bolthole.com Fri Dec 19 16:52:06 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 19 Dec 2008 07:52:06 -0800 Subject: [csw-maintainers] new PHP maintainer needed In-Reply-To: <494BC1B5.4070707@cognigencorp.com> References: <49495AD4.8000806@opencsw.org> <1229629675-sup-9039@ntdws12.chass.utoronto.ca> <20081218200950.GH54484@bolthole.com> <494BA381.4060207@cognigencorp.com> <20081219152551.GC46050@bolthole.com> <494BC1B5.4070707@cognigencorp.com> Message-ID: <20081219155206.GB4156@bolthole.com> On Fri, Dec 19, 2008 at 10:45:57AM -0500, Darin Perusich wrote: > I wouldn't call it complaining, I'm merely pointing out something, > again, that I feel is a deficiency. > > As the "primary path to resolution", I propose removing drupal from the > repository. why would you not update the package? From Darin.Perusich at cognigencorp.com Fri Dec 19 17:22:12 2008 From: Darin.Perusich at cognigencorp.com (Darin Perusich) Date: Fri, 19 Dec 2008 11:22:12 -0500 Subject: [csw-maintainers] new PHP maintainer needed In-Reply-To: <20081219155206.GB4156@bolthole.com> References: <49495AD4.8000806@opencsw.org> <1229629675-sup-9039@ntdws12.chass.utoronto.ca> <20081218200950.GH54484@bolthole.com> <494BA381.4060207@cognigencorp.com> <20081219152551.GC46050@bolthole.com> <494BC1B5.4070707@cognigencorp.com> <20081219155206.GB4156@bolthole.com> Message-ID: <494BCA34.3060602@cognigencorp.com> Philip Brown wrote: > On Fri, Dec 19, 2008 at 10:45:57AM -0500, Darin Perusich wrote: >> I wouldn't call it complaining, I'm merely pointing out something, >> again, that I feel is a deficiency. >> >> As the "primary path to resolution", I propose removing drupal from the >> repository. > > why would you not update the package? > I am no longer running it on Solaris and don't want to be burdened with maintaining it. -- Darin Perusich Unix Systems Administrator Cognigen Corporation 395 Youngs Rd. Williamsville, NY 14221 Phone: 716-633-3463 Email: darinper at cognigencorp.com From phil at bolthole.com Fri Dec 19 18:00:44 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 19 Dec 2008 09:00:44 -0800 Subject: [csw-maintainers] new PHP maintainer needed In-Reply-To: <494BCA34.3060602@cognigencorp.com> References: <49495AD4.8000806@opencsw.org> <1229629675-sup-9039@ntdws12.chass.utoronto.ca> <20081218200950.GH54484@bolthole.com> <494BA381.4060207@cognigencorp.com> <20081219152551.GC46050@bolthole.com> <494BC1B5.4070707@cognigencorp.com> <20081219155206.GB4156@bolthole.com> <494BCA34.3060602@cognigencorp.com> Message-ID: <20081219170044.GA73995@bolthole.com> On Fri, Dec 19, 2008 at 11:22:12AM -0500, Darin Perusich wrote: > >> As the "primary path to resolution", I propose removing drupal from the > >> repository. > > > > why would you not update the package? > > > > I am no longer running it on Solaris and don't want to be burdened with > maintaining it. I suppose i could "orphan" the package, if you wished. What about your other packages? From Darin.Perusich at cognigencorp.com Fri Dec 19 19:02:15 2008 From: Darin.Perusich at cognigencorp.com (Darin Perusich) Date: Fri, 19 Dec 2008 13:02:15 -0500 Subject: [csw-maintainers] new PHP maintainer needed In-Reply-To: <20081219170044.GA73995@bolthole.com> References: <49495AD4.8000806@opencsw.org> <1229629675-sup-9039@ntdws12.chass.utoronto.ca> <20081218200950.GH54484@bolthole.com> <494BA381.4060207@cognigencorp.com> <20081219152551.GC46050@bolthole.com> <494BC1B5.4070707@cognigencorp.com> <20081219155206.GB4156@bolthole.com> <494BCA34.3060602@cognigencorp.com> <20081219170044.GA73995@bolthole.com> Message-ID: <494BE1A7.1090408@cognigencorp.com> Philip Brown wrote: > On Fri, Dec 19, 2008 at 11:22:12AM -0500, Darin Perusich wrote: >>>> As the "primary path to resolution", I propose removing drupal from the >>>> repository. >>> why would you not update the package? >>> >> I am no longer running it on Solaris and don't want to be burdened with >> maintaining it. > > I suppose i could "orphan" the package, if you wished. My preference would to remove it from the repository but given that someone, somewhere might be using it then orphan it. > What about your other packages? Are working fine and I am in no hurry to upgrade them, with the exception of Amanda which I'll update soon. -- Darin Perusich Unix Systems Administrator Cognigen Corporation 395 Youngs Rd. Williamsville, NY 14221 Phone: 716-633-3463 Email: darinper at cognigencorp.com From bwalton at opencsw.org Fri Dec 19 19:53:23 2008 From: bwalton at opencsw.org (Ben Walton) Date: Fri, 19 Dec 2008 13:53:23 -0500 Subject: [csw-maintainers] git in testing (solaris 8, sparc) In-Reply-To: <1229634705-sup-2537@ntdws12.chass.utoronto.ca> References: <1229634705-sup-2537@ntdws12.chass.utoronto.ca> Message-ID: <1229712619-sup-5245@ntdws12.chass.utoronto.ca> Hi All, There are now packages for git (solaris 8, sparc) in /home/testing [git*12.19*gz]. Same caveats as before...I'm sure there is some cleanup left in terms of the package part, but the actual delivered files seem to work. All tests (except expected failures) passed on this platform, which is a good sign. Feedback welcome. -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From phil at bolthole.com Sat Dec 20 19:35:01 2008 From: phil at bolthole.com (Philip Brown) Date: Sat, 20 Dec 2008 10:35:01 -0800 Subject: [csw-maintainers] need maintainer for mysql Message-ID: <20081220183501.GA51383@bolthole.com> btw: we badly need a maintainer for mysql. we need to upgrade from 5.0 to 5.1 any takers? From trygvel at opencsw.org Sun Dec 21 14:07:20 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Sun, 21 Dec 2008 14:07:20 +0100 Subject: [csw-maintainers] Catalog for /testing? Message-ID: <494E3F88.6020506@opencsw.org> Hei! Would it be possible to generate a catalog for the packages in testing? I'd love to be able to make sure that I always get the correct/updated set of dependencies when I want to try out some package. Right now I'd like to test Ben's git work, but as I've built a few of the packages myself I have some outdated packages and some missing. I would like to just do a pkg-get -c to find the outdated ones and/or just pkg-get -i git to get them all. -- Trygve From bonivart at opencsw.org Sun Dec 21 14:16:55 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Sun, 21 Dec 2008 14:16:55 +0100 Subject: [csw-maintainers] Catalog for /testing? In-Reply-To: <494E3F88.6020506@opencsw.org> References: <494E3F88.6020506@opencsw.org> Message-ID: <625385e30812210516w15df19d3g6f67abebcee31268@mail.gmail.com> On Sun, Dec 21, 2008 at 2:07 PM, Trygve Laugst?l wrote: > Hei! > > Would it be possible to generate a catalog for the packages in testing? > I'd love to be able to make sure that I always get the correct/updated > set of dependencies when I want to try out some package. > > Right now I'd like to test Ben's git work, but as I've built a few of > the packages myself I have some outdated packages and some missing. I > would like to just do a pkg-get -c to find the outdated ones and/or just > pkg-get -i git to get them all. Isn't this what you're looking for? http://buildfarm.opencsw.org/testing.html -- /peter From james at opencsw.org Sun Dec 21 14:36:05 2008 From: james at opencsw.org (James Lee) Date: Sun, 21 Dec 2008 13:36:05 GMT Subject: [csw-maintainers] Catalog for /testing? In-Reply-To: <494E3F88.6020506@opencsw.org> References: <494E3F88.6020506@opencsw.org> Message-ID: <20081221.13360500.1565619539@gyor.oxdrove.co.uk> On 21/12/08, 13:07:20, "Trygve Laugst?l" wrote regarding [csw-maintainers] Catalog for /testing?: > Would it be possible to generate a catalog for the packages in testing? It's possible but ill advised. The content of testing need not represent a coherent state from which general update makes sense. If it did it would be what unstable is. Select and download the packages you know you want to install and make your own catalog. James. From bwalton at opencsw.org Mon Dec 22 05:19:16 2008 From: bwalton at opencsw.org (Ben Walton) Date: Sun, 21 Dec 2008 23:19:16 -0500 Subject: [csw-maintainers] docbook, dependencies, what do we want...? Message-ID: <1229918644-sup-5016@ntdws12.chass.utoronto.ca> Hi All, Phil and I have been discussing this for the last few days and I thought I'd open it up to everyone else, as your input is likely valuable here. I've put together a docbook dtds package that provides xml and sgml dtd files for various versions of the docbook standard. At installation time, the xmlcatalog tool is used to 'register' the newly installed catalog files so that consumers of dtds can find them. This sets up a dependency on the libxml2 package (provider of xmlcatalog). As I modeled this package on the one found in rhel5, I also setup a dependency on openjade. This one is a little tenuous though, as the dependency is basically conditional on some other stylesheets having been installed on the system before the docbook dtds (which may be a legacy rpm issue and not valid anymore). The postinstall script looks for stylesheets and if it finds them, registers the dtds in the openjade catalogs. Phil doesn't like this and I'm not going to defend it either, as I was simply replicating faithfully the package stack in another platform to get to my ultimate goal (packaging git). I see a few options here to make this better: 1. Leave it as is, since there is a basis for doing this provided by at least one other distro (more when you look at rhel derivatives). 2. Drop the dependency but still do the postinstall things if both stylesheets _and_ openjade are detected. 3. Drop the dependency, remove this chunk of the postinstall script, which leaves it up to the user to do the registration if required/desired. After looking into it a bit more, and comparing how Debian's approach to compared with the Redhat approach I mimicked, I think I like option 3 the best. ...So, in our discussions, a few other things have come up that I think are worthy of a wider audience for discussion since these base packages may prove useful down the road for others. 1. Provide a more generic 'plugin' system for these packages to make option 2 above simpler. 2. Package something like: http://freshmeat.net/projects/dbsgmltoolbox/, which would provide a 'stack in a box' type approach to these tools. Having mulled this over for a few days since Phil proposed it, I'll lay out my opinions/thoughts on them and then let others whack the pinata. As for the 'plugin' system, I think that's more involved than we need to be. It doesn't seem that either Debian or Redhat do this. Although they have slightly different approaches, both Debian and Redhat rely on either their libxml2 package and/or their own catalog manipulation tools. Debian has much smarter machinery for doing this (via debhelper) and has made use of their stronger dependency system (eg: Suggests for optional dependencies), but overall they take a similar approach to Redhat for delivery. To me, this seems like an unnecessary moving part. With regard to the dbsgmltoolbox idea, I would suggest that bundling all those apps into packages is worthwhile iff there is a need for them. As it seems that the xmlto package is the first csw application that calls for full blown dtd/xsl/xml stuff, I don't see this need. I say don't build it until its needed (borrowing from the "you aren't going to need it" philosophy). So my questions to everyone are: 1. Does anyone see a need for more tools to register dtds and stylesheets? If so, should they be built now or when they're actually needed? 2. Does anyone have need for the type of tools provided with dbsgmltoolbox now? If so, I can package them up (since I opened this can of worms). I'm not about to spend time on something nobody is interested in though. 3. What does everyone think about the dependencies for the docbook dtd's package? I'd like to get this resolved asap so that docbook xsl can be released and then finally xmlto. Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From trygvel at opencsw.org Mon Dec 22 12:37:04 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Mon, 22 Dec 2008 12:37:04 +0100 Subject: [csw-maintainers] [Fwd: [csw-devel] SF.net SVN: gar:[2683] csw/mgar/gar/v2] Message-ID: <494F7BE0.7090303@opencsw.org> Hei! I've added some targets to gar [1] to make it easier to work with Subversion. Currently it support updating the package and updating gar. I'd like to get some feedback on the process that people are using when working with the source tree to create targets that match how people use it. Do an update of your gar/ directory and go "gmake scm-help" to get the overview (or just read further down in the email). [1]: only v2 for now until they're deemed useful for everyone. -- Trygve -------- Original Message -------- Subject: [csw-devel] SF.net SVN: gar:[2683] csw/mgar/gar/v2 Date: Mon, 22 Dec 2008 11:31:17 +0000 From: trygvis at users.sourceforge.net Reply-To: Developers list To: devel at lists.opencsw.org Revision: 2683 http://gar.svn.sourceforge.net/gar/?rev=2683&view=rev Author: trygvis Date: 2008-12-22 11:31:17 +0000 (Mon, 22 Dec 2008) Log Message: ----------- o Adding some targets to work with svn. Modified Paths: -------------- csw/mgar/gar/v2/gar.conf.mk Added Paths: ----------- csw/mgar/gar/v2/bin/svnignore csw/mgar/gar/v2/gar.svn.mk csw/mgar/gar/v2/scm-help Added: csw/mgar/gar/v2/bin/svnignore =================================================================== --- csw/mgar/gar/v2/bin/svnignore (rev 0) +++ csw/mgar/gar/v2/bin/svnignore 2008-12-22 11:31:17 UTC (rev 2683) @@ -0,0 +1,28 @@ +#!/bin/sh +# +# Copyright 2008-2009 OpenCSW +# +# Redistribution and/or use, with or without modification, is +# permitted. This software is without warranty of any kind. The +# author(s) shall not be liable in the event that use of the +# software causes damage. +# +# gar.svn.mk - Targets for working with svn + +# Read the comma separated ignores from stdin and merges it with any existing +# ignores set on the directory. + +ignores=`mktemp`-ignores +existing_ignores=`mktemp`-existing +new_ignores=`mktemp`-new + +while [ "$1" != "" ]; do + echo $1 >> $ignores + shift +done + +svn pg svn:ignore . > $existing_ignores +cat $ignores $existing_ignores | sort | uniq > $new_ignores +svn ps svn:ignore . -F $new_ignores + +rm -rf $ignores $existing_ignores $new_ignores Property changes on: csw/mgar/gar/v2/bin/svnignore ___________________________________________________________________ Added: svn:executable + * Modified: csw/mgar/gar/v2/gar.conf.mk =================================================================== --- csw/mgar/gar/v2/gar.conf.mk 2008-12-22 01:28:00 UTC (rev 2682) +++ csw/mgar/gar/v2/gar.conf.mk 2008-12-22 11:31:17 UTC (rev 2683) @@ -568,8 +568,7 @@ FILE_SITES = $(foreach DIR,$(FILEDIR) $(GARCHIVEPATH),file://$(DIR)/) # Extra libraries -EXTRA_LIBS = gar.pkg.mk gar.common.mk - +EXTRA_LIBS = gar.pkg.mk gar.common.mk gar.svn.mk ccenv: @echo " Compiler: $(GARCOMPILER)" @echo Added: csw/mgar/gar/v2/gar.svn.mk =================================================================== --- csw/mgar/gar/v2/gar.svn.mk (rev 0) +++ csw/mgar/gar/v2/gar.svn.mk 2008-12-22 11:31:17 UTC (rev 2683) @@ -0,0 +1,29 @@ +# vim: ft=make ts=4 sw=4 noet +# +# $Id$ +# +# Copyright 2008-2009 OpenCSW +# +# Redistribution and/or use, with or without modification, is +# permitted. This software is without warranty of any kind. The +# author(s) shall not be liable in the event that use of the +# software causes damage. +# +# gar.svn.mk - Targets for working with svn +# + +scm-help: + @cat $(GARDIR)/scm-help + +scm-update-all: scm-update-package scm-update-gar + +scm-update-package: + $(SVN) --ignore-externals up + +scm-update-gar: + cd $(GARDIR) && $(SVN) --ignore-externals up + +scm-update-ignores: + $(GARDIR)/bin/svnignore work cookies download + +.PHONY: scm-help scm-update-all scm-update-package scm-update-gar Added: csw/mgar/gar/v2/scm-help =================================================================== --- csw/mgar/gar/v2/scm-help (rev 0) +++ csw/mgar/gar/v2/scm-help 2008-12-22 11:31:17 UTC (rev 2683) @@ -0,0 +1,10 @@ +These are the available SCM targets + +scm-update-all: + Updates both the package files and the gar/ directory + +scm-update-package: + Updates the package files + +scm-update-gar: + Updates the contents of the gar/ directory This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. _______________________________________________ devel mailing list devel at lists.opencsw.org https://lists.opencsw.org/mailman/listinfo/devel From jgoerzen at opencsw.org Mon Dec 22 23:43:08 2008 From: jgoerzen at opencsw.org (Jake Goerzen) Date: Mon, 22 Dec 2008 14:43:08 -0800 Subject: [csw-maintainers] /testing pkg wesnoth 1.4.7 Message-ID: <315c02ae0812221443p1e9248c8q8eec3a804d85230c@mail.gmail.com> Hello all, I have successfully build the latest stable wesnoth package (version 1.4.7) and placed them into "testing" wesnoth-1.4.7,REV=2008.12.22-SunOS5.8-i386-CSW.pkg.gz wesnoth-1.4.7,REV=2008.12.22-SunOS5.8-sparc-CSW.pkg.gz These packages where build with Sun Studio 11 on Solaris 8. Earlier I was only able to build this software on Studio 12 on Solaris 10. I found that when compiling with Studio 12 the preproccessor could deal with spaces in -I defines but Studio 11 seems not able to do this? Anyway, once I figured out what was going on I simply removed the empty space in the Makefile and then resumed building. I'll will work on getting all this into mgar so that it will auto build. ATM 1.4.7 is in mgar but a few manual tweeks are needed to get it to build. Just in time for the Holidays. Please give these a try and let me know. Thanks Jake -------------- next part -------------- An HTML attachment was scrubbed... URL: From jgoerzen at opencsw.org Mon Dec 22 23:54:29 2008 From: jgoerzen at opencsw.org (Jake Goerzen) Date: Mon, 22 Dec 2008 14:54:29 -0800 Subject: [csw-maintainers] mgar: gmake pkgclean Message-ID: <315c02ae0812221454g211969d8u2041a352cf0a79fa@mail.gmail.com> Hi, When using the older GAR tree I was in the habit of doing gmake pkgclean to clean things up. Is there this make target in the mgar tree? Thanks, Jake -------------- next part -------------- An HTML attachment was scrubbed... URL: From bwalton at opencsw.org Tue Dec 23 00:42:22 2008 From: bwalton at opencsw.org (Ben Walton) Date: Mon, 22 Dec 2008 18:42:22 -0500 Subject: [csw-maintainers] mgar: gmake pkgclean In-Reply-To: <315c02ae0812221454g211969d8u2041a352cf0a79fa@mail.gmail.com> References: <315c02ae0812221454g211969d8u2041a352cf0a79fa@mail.gmail.com> Message-ID: <1229989248-sup-2558@ntdws12.chass.utoronto.ca> Excerpts from Jake Goerzen's message of Mon Dec 22 17:54:29 -0500 2008: Hi Jake, > When using the older GAR tree I was in the habit of doing gmake pkgclean > to clean things up. Is there this make target in the mgar tree? A simple `gmake clean` will do the trick now. -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From glaw at opencsw.org Tue Dec 23 00:56:16 2008 From: glaw at opencsw.org (Gary Law) Date: Mon, 22 Dec 2008 23:56:16 +0000 Subject: [csw-maintainers] docbook, dependencies, what do we want...? In-Reply-To: <1229918644-sup-5016@ntdws12.chass.utoronto.ca> References: <1229918644-sup-5016@ntdws12.chass.utoronto.ca> Message-ID: 2008/12/22 Ben Walton > > Hi All, > Hi Ben I've ported Docbook to Solaris before, and getting the toolchain up and running is a pig, so well done for volunteering to look at this. I'd go for the lowest maintenance option that delivers a working package. Given the 'fire and forget' principles of opencsw I'd suggest you take the 'it just works' option of dbsgmltoolbox failing that, go with with the openjade dependency. I don't like the 'register if it is there' option, it will give variable results based on what else is installed already, which I don't like. Just my 2p Gary -- Gary Law Email: garylaw at garylaw.net Chat googletalk/messenger: gary.law at gmail.com iChat/jabber/AIM: gary.law at mac.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From trygvel at opencsw.org Tue Dec 23 19:45:06 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Tue, 23 Dec 2008 19:45:06 +0100 Subject: [csw-maintainers] SPARC issues Message-ID: <495131B2.6010405@opencsw.org> Hei! I'm trying to build ghc[1] and while it work just fine on x86, I'm getting these issues when it is trying to build its libraries after the compiler itself has been bootstrapped: /usr/ccs/bin/as: "/tmp/ghc24757_0/ghc24757_0.split__1.s", line 22: error: cannot use v8plus instructions in a non-v8plus target binary /usr/ccs/bin/as: "/tmp/ghc24757_0/ghc24757_0.split__1.s", line 28: error: cannot use v8plus instructions in a non-v8plus target binary /usr/ccs/bin/as: "/tmp/ghc24757_0/ghc24757_0.split__1.s", line 41: error: cannot use v8plus instructions in a non-v8plus target binary /usr/ccs/bin/as: "/tmp/ghc24757_0/ghc24757_0.split__1.s", line 56: error: cannot use v8plus instructions in a non-v8plus target binary Anyone have a clue on what I can do? I've set ISA_DEFAULT_sparc = sparcv8plus in the Makefile, and I did get a "work/build-isa-sparcv8plus/" directory so I think at least GAR is trying to build binaries with the sparcv8plus instruction set. But it still didn't work. [1]: Glasgow Haskell Compiler -- Trygve From phil at bolthole.com Tue Dec 23 20:32:17 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 23 Dec 2008 11:32:17 -0800 Subject: [csw-maintainers] SPARC issues In-Reply-To: <495131B2.6010405@opencsw.org> References: <495131B2.6010405@opencsw.org> Message-ID: <20081223193217.GJ64455@bolthole.com> On Tue, Dec 23, 2008 at 07:45:06PM +0100, Trygve Laugst?l wrote: > Hei! > > I'm trying to build ghc[1] and while it work just fine on x86, I'm > getting these issues when it is trying to build its libraries after the > compiler itself has been bootstrapped: > > /usr/ccs/bin/as: "/tmp/ghc24757_0/ghc24757_0.split__1.s", line 22: > error: cannot use v8plus instructions in a non-v8plus target binary > /usr/ccs/bin/as: "/tmp/ghc24757_0/ghc24757_0.split__1.s", line 28: > error: cannot use v8plus instructions in a non-v8plus target binary > /usr/ccs/bin/as: "/tmp/ghc24757_0/ghc24757_0.split__1.s", line 41: > error: cannot use v8plus instructions in a non-v8plus target binary > /usr/ccs/bin/as: "/tmp/ghc24757_0/ghc24757_0.split__1.s", line 56: > error: cannot use v8plus instructions in a non-v8plus target binary > > Anyone have a clue on what I can do? you arent giving enough details on what is calling as. is cc calling it, or something else directly? From trygvel at opencsw.org Tue Dec 23 21:23:37 2008 From: trygvel at opencsw.org (=?UTF-8?B?VHJ5Z3ZlIExhdWdzdMO4bA==?=) Date: Tue, 23 Dec 2008 21:23:37 +0100 Subject: [csw-maintainers] SPARC issues In-Reply-To: <20081223193217.GJ64455@bolthole.com> References: <495131B2.6010405@opencsw.org> <20081223193217.GJ64455@bolthole.com> Message-ID: <495148C9.5020703@opencsw.org> Philip Brown wrote: > On Tue, Dec 23, 2008 at 07:45:06PM +0100, Trygve Laugst?l wrote: >> Hei! >> >> I'm trying to build ghc[1] and while it work just fine on x86, I'm >> getting these issues when it is trying to build its libraries after the >> compiler itself has been bootstrapped: >> >> /usr/ccs/bin/as: "/tmp/ghc24757_0/ghc24757_0.split__1.s", line 22: >> error: cannot use v8plus instructions in a non-v8plus target binary >> /usr/ccs/bin/as: "/tmp/ghc24757_0/ghc24757_0.split__1.s", line 28: >> error: cannot use v8plus instructions in a non-v8plus target binary >> /usr/ccs/bin/as: "/tmp/ghc24757_0/ghc24757_0.split__1.s", line 41: >> error: cannot use v8plus instructions in a non-v8plus target binary >> /usr/ccs/bin/as: "/tmp/ghc24757_0/ghc24757_0.split__1.s", line 56: >> error: cannot use v8plus instructions in a non-v8plus target binary >> >> Anyone have a clue on what I can do? > > you arent giving enough details on what is calling as. > is cc calling it, or something else directly? ghc is calling as (perhaps through gcc, not sure) while building its core libs: gmake[4]: Entering directory `/home/trygvis/dev/ghc/work/build-isa-sparcv8plus/ghc-6.8.3/libraries/base' ../../compiler/stage1/ghc-inplace -package-name base-3.0.2.0 -hide-all-packages -split-objs -i -idist/build/autogen -idist/build -i. -Idist/build -Iinclude -#include "HsBase.h" -odir dist/build -hidir dist/build -stubdir dist/build -package rts-1.0 -O -package-name base -XMagicHash -XExistentialQuantification -XRank2Types -XScopedTypeVariables -XUnboxedTuples -XForeignFunctionInterface -XUnliftedFFITypes -XDeriveDataTypeable -XGeneralizedNewtypeDeriving -XFlexibleInstances -XPatternSignatures -XStandaloneDeriving -XPatternGuards -XCPP -idist/build -H16m -O -O -Rghc-timing -fgenerics -c GHC/Err.lhs-boot -o dist/build/GHC/Err.o-boot -ohi dist/build/GHC/Err.hi-boot <> ../../compiler/stage1/ghc-inplace -package-name base-3.0.2.0 -hide-all-packages -split-objs -i -idist/build/autogen -idist/build -i. -Idist/build -Iinclude -#include "HsBase.h" -odir dist/build -hidir dist/build -stubdir dist/build -package rts-1.0 -O -package-name base -XMagicHash -XExistentialQuantification -XRank2Types -XScopedTypeVariables -XUnboxedTuples -XForeignFunctionInterface -XUnliftedFFITypes -XDeriveDataTypeable -XGeneralizedNewtypeDeriving -XFlexibleInstances -XPatternSignatures -XStandaloneDeriving -XPatternGuards -XCPP -idist/build -H16m -O -O -Rghc-timing -fgenerics -c GHC/Base.lhs -o dist/build/GHC/Base.o -ohi dist/build/GHC/Base.hi -- Trygve From phil at bolthole.com Tue Dec 23 21:40:23 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 23 Dec 2008 12:40:23 -0800 Subject: [csw-maintainers] SPARC issues In-Reply-To: <495148C9.5020703@opencsw.org> References: <495131B2.6010405@opencsw.org> <20081223193217.GJ64455@bolthole.com> <495148C9.5020703@opencsw.org> Message-ID: <20081223204023.GA97070@bolthole.com> On Tue, Dec 23, 2008 at 09:23:37PM +0100, Trygve Laugst??l wrote: > > you arent giving enough details on what is calling as. > > is cc calling it, or something else directly? > > ghc is calling as (perhaps through gcc, not sure) while building its > core libs: > gaaahhh... I suspect the most practical thing to do in this instance, is to use the gnu compiler chain. sigh. From trygvel at opencsw.org Tue Dec 23 23:33:39 2008 From: trygvel at opencsw.org (=?UTF-8?B?VHJ5Z3ZlIExhdWdzdMO4bA==?=) Date: Tue, 23 Dec 2008 23:33:39 +0100 Subject: [csw-maintainers] docbook, dependencies, what do we want...? In-Reply-To: References: <1229918644-sup-5016@ntdws12.chass.utoronto.ca> Message-ID: <49516743.1080405@opencsw.org> Gary Law wrote: > 2008/12/22 Ben Walton > > > > Hi All, > > > Hi Ben > > I've ported Docbook to Solaris before, and getting the toolchain up and > running is a pig, so well done for volunteering to look at this. I'd go > for the lowest maintenance option that delivers a working package. Given > the 'fire and forget' principles of opencsw I'd suggest you take the 'it > just works' option of dbsgmltoolbox > failing that, go with with > the openjade dependency. I don't like the 'register if it is there' > option, it will give variable results based on what else is installed > already, which I don't like. Ben; I'm not really sure what the overall implications of the choices really mean so I'd go for what Gary proposes here and tackle the problem later on if someone has the energy to go through it. -- Trygve From trygvel at opencsw.org Tue Dec 23 23:35:35 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Tue, 23 Dec 2008 23:35:35 +0100 Subject: [csw-maintainers] SPARC issues In-Reply-To: <20081223204023.GA97070@bolthole.com> References: <495131B2.6010405@opencsw.org> <20081223193217.GJ64455@bolthole.com> <495148C9.5020703@opencsw.org> <20081223204023.GA97070@bolthole.com> Message-ID: <495167B7.4020306@opencsw.org> Philip Brown wrote: > On Tue, Dec 23, 2008 at 09:23:37PM +0100, Trygve Laugst?l wrote: >>> you arent giving enough details on what is calling as. >>> is cc calling it, or something else directly? >> ghc is calling as (perhaps through gcc, not sure) while building its >> core libs: >> > > gaaahhh... > > I suspect the most practical thing to do in this instance, is to use > the gnu compiler chain. sigh. The odd thing though is that the error message in itself is meaningful, and I'm using /usr/bin/ld on my local box (which is x86) and that work just fine. -- Trygve From bwalton at opencsw.org Wed Dec 24 14:40:16 2008 From: bwalton at opencsw.org (Ben Walton) Date: Wed, 24 Dec 2008 08:40:16 -0500 Subject: [csw-maintainers] docbook, dependencies, what do we want...? In-Reply-To: References: <1229918644-sup-5016@ntdws12.chass.utoronto.ca> Message-ID: <1230125765-sup-445@ntdws12.chass.utoronto.ca> ...here's the path I've chosen, for anyone interested (and still reading mail this time of year): 1. I dropped the openjade dependency from docbook dtds and removed all notion of openjade from the postinstall script. 2. I'm planning to bundle up the docbook dsssl stylesheets in the new year. This package will depend on both openjade and docbook dtds. It will register the docbook dtd catalogs with openjade, as this is the point where all of the pieces become useful together. The dependencies here are pretty clean cut, so this should be a nicer solution overall. :) -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From phil at bolthole.com Sat Dec 27 18:05:45 2008 From: phil at bolthole.com (Philip Brown) Date: Sat, 27 Dec 2008 09:05:45 -0800 Subject: [csw-maintainers] vacation for a few days Message-ID: <20081227170544.GA39007@bolthole.com> fyi; I'm off on vacataion for a few days. if there are any "emergency" pacakge releases that come up, James can sign the catalog also. meanwhile, merry Christmas and a happy new Year to all ;-) From ihsan at opencsw.org Sun Dec 28 17:48:32 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Sun, 28 Dec 2008 17:48:32 +0100 Subject: [csw-maintainers] new gnupg package in testing Message-ID: <4957ADE0.3060503@opencsw.org> http://mirror.opencsw.org/testing/gnupg-1.4.9,REV=2008.12.28-SunOS5.8-i386-CSW.pkg.gz http://mirror.opencsw.org/testing/gnupg-1.4.9,REV=2008.12.28-SunOS5.8-sparc-CSW.pkg.gz -- ihsan at dogan.ch http://blog.dogan.ch/ From jgoerzen at opencsw.org Wed Dec 31 00:34:55 2008 From: jgoerzen at opencsw.org (Jake Goerzen) Date: Tue, 30 Dec 2008 15:34:55 -0800 Subject: [csw-maintainers] retiring Message-ID: <315c02ae0812301534u7dbca8f0je052d3151fb13ece@mail.gmail.com> Hello All, I have decided to retire from being a package maintainer. The following packages in /testing are my last work. Feel free to include those into unstable: http://mirror.opencsw.org/testing/freeciv-2.1.8,REV=2008.12.22-SunOS5.8-i386-CSW.pkg.gz http://mirror.opencsw.org/testing/freeciv-2.1.8,REV=2008.12.22-SunOS5.8-sparc-CSW.pkg.gz http://mirror.opencsw.org/testing/wesnoth-1.4.7,REV=2008.12.22-SunOS5.8-i386-CSW.pkg.gz http://mirror.opencsw.org/testing/wesnoth-1.4.7,REV=2008.12.22-SunOS5.8-sparc-CSW.pkg.gz Best wishes to you all Sincerely, Jake Goerzen -------------- next part -------------- An HTML attachment was scrubbed... URL: